Q: Which Java version is needed to run WoPeD?
A: On all supported platforms, WoPeD requires Java 11 or higher to be launched.
Q: Does WoPeD support place/transition nets?
A: Yes. WoPeD can edit, analyze and simulate regular place/transition nets. The editor supports also other net classes but by restricting yourself to plain nets (and just ignoring all workflow-net-based extensions), WoPeD can serve as a normal Petri net tool.
Q: Does WoPeD support high level nets?
A: No. WoPeD currently does not support high level nets like predicate/transition or colored Petri nets.
Q: Does WoPeD support workflow nets?
A: Yes. WoPeD supports all features defined by Wil van der Aalst in his book on Workflow Management. This includes control flow elements (operators, triggers), algorithms to check soundness and other structural and behavioral correctness properties, as well as extensions needed for quantitative analysis like resource modeling (roles and groups), service times, arrival rate and other performance-related parameters.
Q: Does WoPeD support arc weights?
A: Yes. Arc weights can be specified via the arc property dialog. However, most of the analysis algorithms will not be applicable to models with arc weights > 1.
Q: Does WoPeD support hierarchical nets?
A: Yes. WoPeD does support subprocesses which can be defined behind a special transition (= subprocess symbol). However, subprocess usage is only supported in the “single-entry-single-exit” mode, i. e. a subprocess transition (and thus also the subprocess itself) must have exactly one input place and exactly one output place. This restricts the modeling power but guarantees that all correctness proofs (e. g. soundness or workflow net property) can be applied using hierarchy-based preservation rules.
Q: Which languages does WoPeD support?
A: WoPeD currently supports English and German. However, if you feel motivated to add support for your own mother tongue, please contact the WoPeD team.
Q: Which import and export formats does WoPeD support?
A: WoPeD supports import and export of PNML as specified in the official standard. WoPeD adds “toolspecific” information which will be ignored by other tools. The same happens the other way round. So far it is known that WoPeD can import PNML files from ProM, Pipe2 and ePNK, presumably more. Apart from this, WoPeD can export nets to TPN (Woflan‘s native format) and to several graphical formats (PNG, GIF, JPG). In an upcoming version, it is intended that WoPeD is able to transparently load and save process descriptions stored within an AProMoRe repository.
Q: How to fix problems with launching the WoPeD installer on Windows (error message “This application was configured to use a bundled Java Runtime Environment but the runtime is missing or corrupted”)?
A: The Windows WoPeD installer consist of a JAR file wrapped into an EXE file. In order to run this EXE, an existing Java Runtime is required with an environment variable JAVA_HOME pointing to the folder where Java was installed. Some Java distributions (in particular recent Oracle Java versions) do not set JAVA_HOME automatically. Lookup here how to fix this manually.