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.
| PlantUML Macro |
|---|
@startuml [*] --> ONLINE: Register ONLINE --> ONLINE: Heartbeat ONLINE --> OFFLINE: Timeout OFFLINE --> ONLINE: Heartbeat ONLINE --> [*]: Deregister OFFLINE --> [*]: Deregister @enduml |
Automation Composition Type State
The states that an Automation Composition Type can have are shown in the diagram below.
| PlantUML Macro |
|---|
@startuml [*] --> COMMISSIONED: Commission COMMISSIONED --> [*]: Decommission COMMISSIONED --> PRIMING: Prime PRIMED --> PRIMING: Prime PRIMING --> PRIMED: AC Element Types\nall PRIMED PRIMING --> DEPRIMING: Deprime PRIMED --> DEPRIMING: Deprime DEPRIMING --> COMMISSIONED: AC Element Types\nall DEPRIMED @enduml |
Automation Composition Element Type State
The states that an Automation Composition Element Type can have on ACM Runtime are shown in the diagram below.
| PlantUML Macro |
|---|
@startuml [*] --> COMMISSIONED: Commission COMMISSIONED --> [*]: Decommission COMMISSIONED --> PRIMING: Prime PRIMED --> PRIMING: Prime PRIMING --> PRIMED: AC Element Type Primed\nresponse from Participant PRIMING --> DEPRIMING: Deprime PRIMED --> DEPRIMING: Deprime DEPRIMING --> COMMISSIONED: AC Element Type Deprimed\nresponse from Participant @enduml |
The states that an Automation Composition Element Type can have on a Participant are shown in the diagram below.
| PlantUML Macro |
|---|
@startuml [*] --> PRIMED: Prime from\nACM Runtime PRIMED --> PRIMED: Prime from ACM Runtime PRIMED --> [*]: Deprime from\nACM Runtime @enduml |
Automation Composition Instance State
The states that an Automation Composition Instance can have are shown in the diagram below.
| PlantUML Macro |
|---|
@startuml
[*] --> UNDEPLOYED: Create
UNDEPLOYED --> [*]: Delete
UNDEPLOYED --> DEPLOYING: Deploy
DEPLOYING --> DEPLOYED: AC Element Instances\nall DEPLOYED
DEPLOYING --> UNDEPLOYING: Undeploy
DEPLOYED --> UNDEPLOYING: Undeploy
UNDEPLOYING --> UNDEPLOYED: AC Element Types\nall UNDEPLOYED
state DEPLOYED {
[*] --> LOCKED: Deploy
LOCKED --> [*]: Undeploy
LOCKED --> UNLOCKING: Unlock
UNLOCKING --> UNLOCKED: AC Element Types\nall UNLOCKED
UNLOCKED --> LOCKING: Lock
UNLOCKING --> LOCKING: Lock
LOCKING --> LOCKED: AC Element Types\nall LOCKED
}
@enduml |
Automation Composition Element Instance State
The states that an Automation Composition Element Instance can have on ACM Runtime are shown in the diagram below.
| PlantUML Macro |
|---|
@startuml
[*] --> UNDEPLOYED: Create
UNDEPLOYED --> [*]: Delete
UNDEPLOYED --> DEPLOYING: Deploy
DEPLOYING --> DEPLOYED: AC Element\nInstance DEPLOYED
DEPLOYING --> UNDEPLOYING: Undeploy
DEPLOYED --> UNDEPLOYING: Undeploy
UNDEPLOYING --> UNDEPLOYED: AC Element\nInstance UNDEPLOYED
state DEPLOYED {
[*] --> LOCKED: Deploy
LOCKED --> [*]: Undeploy
LOCKED --> UNLOCKING: Unlock
UNLOCKING --> UNLOCKED: AC Element\nInstance UNLOCKED
UNLOCKED --> LOCKING: Lock
UNLOCKING --> LOCKING: Lock
LOCKING --> LOCKED: AC Element\nInstance LOCKED
}
@enduml |
The states that an Automation Composition Element Instance can have on a Participant are shown in the diagram below.
| PlantUML Macro |
|---|
@startuml
[*] --> DEPLOYED: Deploy from ACM Runtime
DEPLOYED --> [*]: Undeploy from ACM Runtime
state DEPLOYED {
[*] --> LOCKED: Deploy
LOCKED --> [*]: Undeploy from\nACM Runtime
LOCKED --> UNLOCKED: Unlock from\nACM Runtime
UNLOCKED --> LOCKED: Lock from\nACM Runtime
}
@enduml |