Typical use scenarios for the BPM-Converter are:

• Use of different modelling tools
  Especially in larger companies, different modelling tools are often in use. This can have historical reasons, as the tools used often have different functionalities for special purposes (e.g., SOX, activity-based costing, quality management, software development). In most cases, the modellers know their tool well and have developed specific approaches for their areas of expertise. With the help of the BPM-Converter, the newly provided models can be transferred consistently to the other tools, so that in all tools the same contents exist.
• Use of lightweight tools for specialized departments
  Very extensive and efficient modelling suites like ARIS or Casewise are often complicated and laborious to learn. Hence, they are used mostly by modelling experts. Employees of specialized divisions or consultants, who rarely create process models, prefer easy, graphically oriented tools like Visio or iGrafx Flowcharter. With the BPM- Converter such models can be converted into a modelling suite and be brought together with other models and be standardized there by modelling experts. Then, the resulting comprehensive models are transformed again and made available for the lightweight tools. If the Visio-based BPM-Designer is used, one can be sure, that the Visio modellers are working with methods that are compliant to the modelling suite being used.
• Migration from process models
  With the introduction of new process modelling tools, it is desirable to transfer the available process models into the new tool. These models are often structured differently and do not correspond to a modelling method. The BPM-Converter can transform the contents of such models and transfer them into the new tool. The production of the transformation rules necessary for this is supported by the analysis component of the BPM-Administrator.
• Support of the heterogeneous system environment of process execution
  In most cases, processes do not completely execute in a system. Also, with the use of workflow or business process management systems, the controlling flow sometimes changes in another system, or manual steps are included in the process. In such cases, it is not enough if a single system possesses a process definition. To be able to manage the whole process, a complete model is required in an independent modelling tool. Then, the single partial processes are converted with the help of the BPM-Converter into the notations and formats of the systems involved in each case.
• Conversion of Business Process Models to software models
  For the conversion of economically oriented business process models, a transformation of these models is necessary into software for the process support, on the one hand directly workable models (e.g., BPEL), on the other hand, models for software development (e.g., UML). The BPM-Converter carries out a transformation between the involved notations and tools.