EPC-Document

Events are a expression of status changes within an EPC process model. You may wish to consider your modeling style to express the document object as either an input or an output of a proceeding function.

1. Consider, if the EPC is the right model type to make the connection from document to document. The EPC is typically focused on the process steps, which carry more or less "satellite" objects connected to them. If you want to model relationships between documents, another model type might be more adequate. Keep models small and simple for the reader. Most of the time they are human.

2. Have you checked, which method filter you are using for your database? The method filter is THE tool to configure your modelling method. It defines which connection types are available between which symbols in which model types, which attributes are available for each connection type, object type, and model type, and more. Before any modelling effort:

• Define the goals of your modelling,
• decide on the concepts and their relations that are relevant to your model
• then, map the concepts to ARIS symbols and connection types, invent new symbols if deemed useful to differentiate similar concepts (ARIS has already got plenty of symbol types per object type, but sometimes you find another concept to model)
• Identify, which ARIS model types can depict those relationships together
• find owners for each model type, so the model type should be suitable for the owner's area of responsibility
• candidates for owners are the stakeholders, that formulated the goals of modelling (see above)
• LAST but not least create the method filter, that suits your needs.
• if necessary, adapt the standard method with elements not provided out-of-the-box

Also a good tool: Instead of creating a model type "from scratch", you can "derive" a model type from an existing model type, that "almost" suits your needs (e.g. the EPC). This is the only way to get other than the standard layout tool for your custom model type.