Business Process Incubator

Convert a Microsoft Visio file to a BPMN 2.0 file

Convert a Microsoft Visio file to a BPMN 2.0 file

Community:
Contributor Trisotech
Last Updated Mon, February 8, 2010
Version 1.0
Input Microsoft Visio
Output BPMN 2.0
Premium Member Unlimited
Basic Member Limited



Documentation





1 2 3 4 5

Description

Tags

Ratings

 
  • This service imports any visio file by mapping the visio shapes in your drawing to BPMN shapes. You will experience varying level of success in the mapping depending on the shapes you have used in your drawing. For optimal results, you can use the Trisotech BPMN Modeler for Visio.
    Processing Assumptions
    • BPMN shape detection is best guessed from the shapes in your drawing, unless it is part of Trisotech BPMN Modeler for Visio, Microsoft BPMN stencil, Microsoft EPC stencil or ITP Commerce.
      (The structure of other 3rd party shape vendor is unknown)
    • Unrecognized shapes are mapped to tasks or sequence flows.
    • One Workflow Process is created for each page having content in the Visio document with the following exceptions: If a page contains Choreograph elements, then a Choreography is created to hold its elements. If a page contains more than one pool with content, then one Workflow Process by pool is created. If matching link event can be found between pages and if those link events are in no pool or in a pool with the same name, then they are considered to be the same process and their parent pool are considered to be the same pool.
    • One pool with invisible border is created for process having nodes that are not contained by a pool if that process is part of collaboration.
    • Black box pools having the same name and the same multi-instance value on different pages are considered to be the same pool.
    • At most one collaboration is created by Visio file.
      (There's no explicit way to distinguish collaboration)
    • Elements are considered to be inside a container if their center is inside of it.
    • Intermediate events found on the border of a sub-process or task are considered attached to it if their middle point is on the parent's borders.
    • Only attached intermediate events can be non-interrupting
      (This follows BPMN 2.0 specification)
    • When an artifact is linked to elements in one process only, it is placed in that Process definition. When it has no link or is linked to multiple processes, it is saved into the Collaboration element.
    • To be transferred, DataAssocation must be between a DataObject, a DataStore, a DataInput or a DataOutput and an activity.
      (This way, the association direction (input or output) can be determined and it can be saved in the proper flow node)

  • Use commas to separate tags.


    Other members marked this item with these tags:
  • How do you rate this item ?
    1 2 3 4 5

    Other members rated this item as follows:
    Rated by Luis (Posted on 12/16/10)
    Rated by Mélanie (Posted on 10/21/10)