Modeling the process fragment definitions

First of all, generate a model assignment for all functions of the overall process in the group, which is to contain the fragment definition. The identifier of the assigned model (process fragment definition) specifies the name of the fragment definition. Next copy all events, which adjoin a function in the procedural logic, into the model which is assigned to the function.

Observe the following guidelines when modeling the fragments, regardless of whether you are using an overall process or creating the fragments without an overall process.

Modeling guidelines for fragment definition

Use the special PPM method filter FragmentXML_ARISToolSet_Filter.amc from the directory <PPM installation directory>\ppmmashzone\server\bin\agentLocalRepo\.unpacked\ppm-client-run-prod-<version>-runnable.zip\ppm\ctk\ARIS. This limits the number of modeling elements to the permissible object and connection types and thus makes modeling easier.

If you are using an overall process, when modeling the fragments generate occurrence copies of the objects in the overall process.

You can also specify free attributes for all objects and connections. These are written to the corresponding objects or connections in the fragment definition file as fixed PPM attribute/value combinations of the TEXT type. The list must be specified in ascending order starting with User attribute text 1 and is evaluated as far as the first non-specified attribute. Format: <Attribute key>#<Attribute value>. The separator # must not appear in the attribute key or in the attribute value.

Example

For the New customer order to be created event, the following free attributes are specified:

tr_xml_free_attr

In the file extract below from the fragment definition file created, the transferred free attributes are shown in bold.

...

<node id="EVT_NEWCUSTORD2BE_CREATED" type="OT_EVT">

<attribute type="AT_OBJNAME">New customer order to be created</attribute>

<attribute type="AT_OBJNAME_INTERN">EVT_NEWCUSTORD2BE_CREATED</attribute>

<attribute type="AT_PLANT_NAME">Duesseldorf</attribute>

<attribute type="AT_PLANT_ID">00123</attribute>

<attribute type="AT_CUST_ID">456777</attribute>

<attribute type="AT_CUST_NAME">Mayer</attribute>

</node>

...

Source object

Target object

ARIS connection type

Event

Function

activates

Event

Rule

is evaluated by

Function

Event

creates

Function

Rule

leads to

Function

Function

is predecessor of

Rule

Event

leads to

Rule

Function

activates

Rule

Rule

links

The illustration below shows a properly modeled process fragment with additional free attributes specified for objects and a connection:

tr_xml_free_attr_2

ARIS Report generates the following fragment definition file:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE graphlist SYSTEM "graph.dtd">

<graphlist>

<graph id="FRG_NEWCUST_ORD">

<node id="EVT_NEWCUSTORD2BE_CREATED" type="OT_EVT">

<attribute type="AT_OBJNAME">New customer order to be created</attribute>

<attribute type="AT_OBJNAME_INTERN">EVT_NEWCUSTORD2BE_CREATED</attribute>

<attribute type="AT_PLANT_NAME">Duesseldorf</attribute>

<attribute type="AT_PLANT_ID">00123</attribute>

<attribute type="AT_CUST_ID">456777</attribute>

<attribute type="AT_CUST_NAME">Mayer</attribute>

</node>

<node id="FCT_CREATE_NEWCUSTORD" type="OT_FUNC">

<attribute type="AT_OBJNAME">Create new customer order</attribute>

<attribute type="AT_OBJNAME_INTERN">FCT_CREATE_NEWCUSTORD</attribute>

</node>

<node id="OT_RULE_AND" type="OT_RULEAND">

<attribute type="AT_OBJNAME_INTERN">OT_RULE_AND</attribute>

<attribute type="AT_SAP_ID">455455</attribute>

</node>

<node id="FCT_REC_NEWCUSTDAT" type="OT_FUNC">

<attribute type="AT_OBJNAME">Enter new customer data</attribute>

<attribute type="AT_OBJNAME_INTERN">FCT_REC_NEWCUSTDAT</attribute>

<attribute type="AT_CUST_ID">456777</attribute>

<attribute type="AT_CUST_NAME">Mayer</attribute>

</node>

<node id="OT_RULE_AND" type="OT_RULEAND">

<attribute type="AT_OBJNAME_INTERN">OT_RULE_AND</attribute>

</node>

<node id="EVT_NEWCUSTORD_CREATED" type="OT_EVT">

<attribute type="AT_OBJNAME">New customer order created</attribute>

<attribute type="AT_OBJNAME_INTERN">EVT_NEWCUSTORD_CREATED</attribute>

</node>

<edge type="CXN_FOLLOWS" source="FCT_REC_NEWCUSTDAT" target="OT_RULE_AND">

<attribute type="AT_ID">123123</attribute>

</edge>

<edge type="CXN_FOLLOWS" source="EVT_NEWCUSTORD2BE_CREATED"

target="OT_RULE_AND"/>

<edge type="CXN_FOLLOWS" source="OT_RULE_AND" target="FCT_REC_NEWCUSTDAT"/>

<edge type="CXN_FOLLOWS" source="OT_RULE_AND"

target="EVT_NEWCUSTORD_CREATED"/>

<edge type="CXN_FOLLOWS" source="FCT_CREATE_NEWCUSTORD"

target="OT_RULE_AND"/>

<edge type="CXN_FOLLOWS" source="OT_RULE_AND"

target="FCT_CREATE_NEWCUSTORD"/>

</graph>

</graphlist>

Overview of process fragment modeling guidelines

ARIS element

ARIS attribute

PPM fragment definition

EPC
(fragment model)

Name

graph id of the definition graph created

Function

Name

AT_OBJNAME

 

Identifier

AT_OBJNAME_INTERN

Event

Name

AT_OBJNAME

 

Identifier

AT_OBJNAME_INTERN

Rule

Identifier

AT_OBJNAME_INTERN

Free attributes

User attribute text <x>
x = Integer from 1 - 37

PPM attribute of TEXT type including value for objects or connections)