Plan Fragment

A plan fragment is an abstraction of a Process Component that contains configuration information that Orchestrator requires to handle errors and SLA notifications. Plan fragments are optional. If no plan fragment is defined for a particular Process Component then Orchestrator uses engine defaults to handle errors and no SLA notifications occurs.

During the evolution of a system it might be necessary to deploy multiple versions of a Process Component simultaneously. To support this plan fragments might be versioned. The relationship between plan fragments, versions, and process components is shown in the following diagram:

Plan Fragment and Process Component Logical Components

Plan Fragment and Process Component Logical Components

In this example plan fragment PC_1000 describes Process Component PC_1000. This Process Component might be invoked by a plan item by using different versions. Therefore plan fragment PC_1000 has Version 1 that maps the Process Component of the same version. The base plan fragment always defines the currently active Process Component version.

Note: The jeopardy detection and rules for consequential action are not applied for any execution containing process component mapping with no valid plan fragment model.