ACM States

Automation Composition Management manages a number of states of various types to manage the lifecycle of compositions. Those states are described here. Please also see the ACM System Level Dialogues page to see the system dialogues that change states and how states interrelate in detail. Please also see ITU Recommendation X.731, which is reflected in the states of AC Element Instances.

Participant State

Participant states are NOT managed by ACM but the state of a participant is recorded and supervised by ACM.

Automation Composition Type State

The states that an Automation Composition Type can have, are shown in the diagram below.

Automation Composition Element Type State

The states that an Automation Composition Element Type can have on ACM Runtime are shown in the diagram below.

The states that an Automation Composition Element Type can have on a Participant are shown in the diagram below.

The states diagram below, shows the fail and timeout scenario. In that diagram the state is presented using this combination [ Composition Element Type State : Composition Type State : StateChangeResult ].

Automation Composition Instance State

The states that an Automation Composition Instance can have are shown in the diagram below.

Automation Composition Element Instance State

The states that an Automation Composition Element Instance can have on ACM Runtime are shown in the diagram below.

The states that an Automation Composition Element Instance can have on a Participant are shown in the diagram below.

Automation Composition State with fail and timeout

The states that an Automation Composition Element Instance can have for each flow, are shown in the diagrams below. For each diagram the state is presented using this combination [ Instance Element State : Instance State : StateChangeResult ].

Deploy

Update

Migrate

Delete

End of Document