MDG BPSim Execution Engine
The Business Process Simulator provides unprecedented flexibility to configure and control the assignment of simulation parameters from different perspectives, including control, time and resources. Automate every aspect of the execution, from the date and time at which the process takes effect through to the number of times the scenario as a whole will be repeated in an execution cycle.
Understand how factors such as task duration or resource management may impact your underlying business model. Monitor a range of variables and observe how changes impact the success of the underlying business model.
Each simulation configuration can be saved as a separate artifact. Enterprise Architect can highlight variances between reports, making it easier to draw conclusions and make decisions. Solve real world problems, identify bottlenecks, enhance resource allocation, improve scheduling and improve business outcomes before committing funds to a project.
Charts and Graphs
Enterprise Architect uses charts and graphs to help visualize the results of various simulations. Report data can become input for a chart element. Compare and contrast the results from a base simulation and subsequent experiments.
Stakeholders can easily draw conclusions from the corresponding charts. Visualize data from multiple report sources and customize the appearance to meet your individual needs. Charts and graphs help aid decision making and can bring your data to life.
MDG BPSim Execution Engine:
Available in both Standard and
MDG BPSim Execution Engine Changes between 1.0.1 to 1.1.2
- 1.1.2 Support Property Parameters and Xpath 1.0 language as Expression format for Parameters (Recommended); with the language setting to Xpath 1.0 for simulation, no vendor extension Java code needs to be generated and JDK is not required to install.
- Java language is still supported for simulation in EA13 and BPSim 1.1.2.
- (However, we suggest to use 1.1.2 for EA13 and 1.0.1 for EA12.1)
- 1.1.2 support Specify Property Parameter's type explicitly on the configuration dialog
- 1.1.2 added support for the BPSim Unit Cost parameter and result request. The unit cost parameter is supported by all tasks (send, receive, task, service, user), processes, resources, call activities calling both process and globalTasks.
- 1.1.2 added support for the BPSim Fixed Cost parameter and result request. The fixed cost parameter is supported by all tasks (send, receive, task, service, user), processes, resources, call activities calling both process and globalTasks.
Bug fixes from 1.0.1 to 1.1.2
- Error connecting Link Event with the target attribute set. This has now changed so that if the event target link fails it falls back to linking using element name matching.
- The Merge parallel gateway causes the Event Sub Process to stop working.
- The Error StartEvent in an Event Sub-Process cannot be triggered if default boundary error intermediate event is created.
- L-SIM does not read the <association> element from a BPMN xml file when creating a link from a boundary compensation intermediate event to the compensation activity.
Maximise your potential with a variety of resources below:
|Enterprise Architect User Guide:|
|-||Business Engineering: Business Modeling Overview|
|-||Business Process Simulation: Introduction to BPSim|
|-||Working in BPSim: Process Models, Simulation Artifacts and Configuration|
|-||Business Process Simulation: The BPSim Control Perspective|
|-||Business Process Simulation: The BPSim Resource Perspective|
|-||Business Process Simulation: The BPSim Time Perspective|
|-||Business Process Simulation: Compare BPSim Configurations|
|-||Business Process Simulation: Export a BPSim Configuration|
|-||MDG BPSim Walkthrough Video (YouTube): Business Process Simulation with Enterprise Architect|
|-||Webinar Recording: Business Process Modeling Notation with Enterprise Architect|
|-||Webinar Recording: BPMN Enhancements in Enterprise Architect|
|-||Tutorial: BPEL - A Step by Step Guide|
|-||BPSim.org Resources: External Link to BPSim 1.0 Specification, XML Schema and Guides|
All other products or company names mentioned are used for identification purposes only, and may be trademarks of their respective owners.