Representing resources in petri net models: Hardwiring or soft-coding?

Abstract

This paper presents an interesting design problem in developing a new tool for discrete-event dynamic systems (DEDS). A new tool known as GPenSIM was developed for modeling and simulation of DEDS; GPenSIM is based on Petri Nets. The design issue this paper talks about is whether to represent resources in DEDS hardwired as a part of the Petri net structure (which is the widespread practice) or to soft code as common variables in the program code. This paper shows that soft coding resources give benefits such as simpler and skinny models. _________________________________________________________________________________________________________________________

Performance Evaluation of Discrete Event Systems with GPenSIM

“…The Background of AOPN AOPN was introduced as "Petri Net Interpreted for Scheduling (PNS)" in earlier works, e.g., [16,17]. AOPN can be considered as a natural extension to Process-Oriented Petri Nets (POPN) and Resource-Oriented Petri Net (ROPN) [18,19].…”

“…However, one of the disadvantages of the POPN models is that they can be large. This is because all the resources and all their connections with the other elements in the system are shown in the model, causing an extra-large number of places, transitions, and arcs [16][17][18][19]. Another disadvantage of POPN is that they are prone to deadlocks.…”

Modeling Resource Management Problems with Activity-Oriented Petri Nets

“…AOPN methodology is already presented in two preliminary papers [11][12]. The aim of this paper is to show the benefits of AOPN through a detailed case study; in order to achieve this aim, this paper is written in a tutorial style, starting with the case study problem early in the following section, and solving it step-by-step throughout the paper.…”