The PPC model type forms the link between ARIS and Microsoft Project. ARIS Architect can represent the operational sequence of functions in the sense of a business process by means of event-driven process chains (EPCs). However, this abstract level is insufficient for the capacity and time planning purposes of a project. Instead, actual event instances and tasks must be examined and specified. The PPC meets this requirement by providing its own object type at occurrence level instead of using the Event and Function object types.

Previously, it was possible to automatically create PPCs from EPCs with the help of the former interface between ARIS and Microsoft Project. The current interface between ARIS Architect and MS Project 2000 no longer refers back to the PPC. Today, this model type only plays a minor role and is essentially used to display former models.

An event instance is an event that occurs in a specific process instance. The event instance can be evaluated, i.e., it is possible to determine whether it is true or false.

A task is a function that occurs in a specific process instance. A unique start and end time, as well as other required attributes can be assigned to it.

Project structural items (tasks, event instances, rules, and connections) serve to represent the chronological-logical operational sequence of a project. The PPC also contains the Internal person/External person, Operating resource, and General resource resource objects. They are aimed at date and capacity planning.

A general resource is a resource that is not described in detail and is not necessarily a person or an operating resource. A general resource serves to run procedures.

Furthermore, cluster instances may be used to specify tasks in more detail within the PPC.

A cluster instance is an instantiation of the 'Cluster/Data model' object. It represents a logical view of multiple data objects or structures.

The PPC uses cluster instances to represent the relationship between tasks and data. The Cluster instance object type can be assigned a model of the Information carrier diagram type (see requirements definition of the data view). Thereby, it is possible to illustrate on which information carrier the data are stored.

The figure below illustrates an example of a project process chain created by converting an EPC.

The XOR rule in the example indicates that branches occurred at this position in the converted EPC. These branches are interpreted as alternative paths for the project and must be uniquely specified.

The PPC model type can also be modeled directly in ARIS Architect.