Priming The CLAMP Automation Composition Runtime Lifecycle Management uses the following system-level dialogues. These dialogues enable the CLAMP runtime capabilities described in Section 2 of TOSCA Defined Automation Compositions: Architecture and Design. Design Time dialogues will be described in future releases of the system.
1 Dialogues on Participants
1.1 Participant Registration
Participant Registration is performed by a Participant when it starts up. It registers its ID and the ACM Element Types it supports with the ACM runtime.
| PlantUML Macro |
|---|
@startuml
participant Participant
participant ACM_Runtime
database ACM_Database
Participant -> ACM_Runtime: [ASYNC] Register
ACM_Runtime -> ACM_Database: [ASYNC] Create or Update Participant Registration\nand store supported ACM element types
Participant <- ACM_Runtime: Registration Accepted
@enduml |
1.2 Participant Deregistration
Participant Deregistration is performed by a Participant when it shuts down. It deregisters its ID and type with the ACM runtime.
The participant should already have cleared down all its ACM Element instances and set their states to UNINITIALIZED.
| PlantUML Macro |
|---|
@startuml
participant Participant
participant ACM_Runtime
database ACM_Database
Participant -> Participant: Uninitialize all ACM Element Instances running on Participant\n(See Instantiation Dialogues)
activate Participant
deactivate Participant
ACM_Runtime -> ACM_Database: Delete Participant Registration
Participant <- ACM_Runtime: [ASYNC] Deregistration Accepted
@enduml |
1.3 Participant Supervision
Participant Supervision is performed periodically between participants and the ACM runtime server to ensure that registered participants are available over time. Participants send a heartbeat message to the ACM runtime at a configured interval.
| PlantUML Macro |
|---|
@startuml
participant Participant
participant ACM_Runtime
database ACM_Database
loop Every Participant Supervision Interval
Participant -> ACM_Runtime: Heartbeat message
ACM_Runtime -> ACM_Database: Update Participant Heartbeat data
end
@enduml |
The ACM runtime regularly checks the heartbeat reports from participants and takes action of participants time out. If a heartbeat message is not received for a participant in the Timeout Interval, the participant is marked as timed out and its ACM element instances are informed.
| PlantUML Macro |
|---|
@startuml
participant ACM_Runtime
database ACM_Database
loop Every ACM_Runtime Supervision Interval
loop Over all Participants
ACM_Runtime -> Database: Read Participant Heartbeat Information
alt Participant Heartbeat not received in Timeout Interval
ACM_Runtime -> ACM_Runtime: Inform all ACM Element Instances\nrunning on Participant of Timeout\n(See Instantiation Dialogues)
activate ACM_Runtime
deactivate ACM_Runtime
end
end
end
@enduml |
The information on participants is available over a REST endpoint.
| PlantUML Macro |
|---|
@startuml
participant REST
participant ACM_Runtime
database ACM_Database
REST -> ACM_Runtime: Get Participant Information
ACM_Runtime -> ACM_Database: Read Participant Data
REST <- ACM_Runtime: Return Participant Information including\nsupported ACM Element Types and Heartbeat Information
@enduml |
2 Dialogues on Automation Composition Types
Commissioning dialogues are used to commission and decommission Automation Composition Types and to set the values of Common Parameters. The values of common parameters are included in the TOSCA YAML file that defines the full Automation Composition Type.
2.1 Commissioning an Automation Composition Type
Create on a POST and update on a PUT.
| PlantUML Macro |
|---|
@startuml
participant REST
participant ACM_Runtime
database ACM_Database
REST -> ACM_Runtime: Commission Automation Composition Type
alt Automation Composition Type exists and has Instances
ACM_Runtime -> REST: Automation Composition Type Commissioning Failed
else
ACM_Runtime -> ACM_Database: Create and Store Automation Composition Type
ACM_Runtime -> REST: Automation Composition Type Commissioned
end
@enduml |
2.2 Commissioning an Automation Composition Type using SDC
| PlantUML Macro |
|---|
@startuml
participant SDC
participant Policy_Distribution
participant ACM_Runtime
SDC -> Policy_Distribution: [ASYNC] CSAR containing Automation Composition Type Definition
Policy_Distribution -> ACM_Runtime: Commission Automation Composition Type\n(See Commissioning Sequence Diagram)
Policy_Distribution <- ACM_Runtime: Result of Commissioning
Policy_Distribution -> SDC: [ASYNC] Return result of Deployment
@enduml |
2.3 Decommissioning an Automation Composition Type Definition
| PlantUML Macro |
|---|
@startuml
participant REST
participant ACM_Runtime
database ACM_Database
REST -> ACM_Runtime: Decommission Automation Composition Type
alt Automation Composition Type has Instances
ACM_Runtime -> REST: Automation Composition Type Decommissioning Failed
else
ACM_Runtime -> ACM_Database: Delete Automation Composition Type
ACM_Runtime -> REST: Automation Composition Type Decommissioned
end
@enduml |
2.4 Prime an Automation Composition Type Definition on Participants
The Priming operation sends Automation Composition Types and common property values to participants for each Automation Composition Element Type in the Automation Composition Type. A participant should respond for each Automation Composition Element Type, thus causing the full Automation Composition Type to become primed. Note that if more than one participant can support an Automation Composition Element Type the ACM Runtime uses the participant in the first response it receives for that Automation Composition Element Type.
| PlantUML Macro |
|---|
@startuml
participant REST
participant ACM_Runtime
participant Participant
database ACM_Database
== Priming REST Request ==
REST -> ACM_Runtime: Prime Automation Composition Type
ACM_Runtime -> ACM_Database: Read Automation Composition Type
ACM_Runtime -> Participant: [ASYNC] Send Priming Request to all Participants\nwith Automation Composition Type Definition
REST <- ACM_Runtime: Priming of Automation Composition Type Ordered
== Each Participant ==
ACM_Runtime -> Participant: [ASYNC] Receive Priming Request with Automation Composition Type Definition
loop Over all Automation Composition Element Type Definitions\nin Automation Composition Type Definition
alt Automation Composition Element Type supported by Participant
Participant -> Participant: Save Automation Composition Element Type details on this Participant
ACM_Runtime <- Participant: [ASYNC] Send Priming Response claiming Automation Composition Element Type
alt Automation Composition Element Type already Primed
note right of Participant
Ignore Priming Response
end note
else
ACM_Runtime -> ACM_Database: Record Participant for Automation Composition Element Type\nand set Element Type as Primed
end
else
note right of Participant
Ignore Priming Request
end note
end
end |
2.5 Get Automation Composition Types
This dialogue allows an Automation Composition Type to be read.
| PlantUML Macro |
|---|
@startuml
participant REST
participant ACM_Runtime
database ACM_Database
REST -> ACM_Runtime: Get Automation Composition Type Information
ACM_Runtime -> ACM_Database: Read Automation Composition Type Information
ACM_Runtime -> REST: Respond with Automation Composition information\nincluding ACM Element Type information and Priming Status
@enduml |
| Warning |
|---|
PAGE UPDATED TO HERE. |
3. Instantiation Dialogues
Instantiation dialogues are used to create, set parameters on, instantiate, update, and remove Automation Composition instances.
3.1 Creating an Automation Composition Instance
| PlantUML Macro |
|---|
@startuml
participant REST
participant CLAMP_Runtime
database ACM_Database
REST -> CLAMP_Runtime: [REST] Read Automation Composition Type Definitions
CLAMP_Runtime -> ACM_Database: Read Automation Composition Type Definitions
CLAMP_Runtime -> REST: [REST] Type Definitions returned
REST -> REST: Select Automation Composition Type Definition to use to create Automation Composition Instance
REST -> CLAMP_Runtime: [REST] Fetch GUI fields for Instance Specific Parameter Definitions
CLAMP_Runtime -> ACM_Database: Read Automation Composition Type Definition
CLAMP_Runtime -> CLAMP_Runtime: Generate fields for Instance Specific Parameters for GUI
CLAMP_Runtime -> REST: [REST] Return GUI fields Instance Specific Parameter Definitions
REST -> REST: Render UI for Instance Specific Parameters REST -> REST: Get values for Instance Specific Parameters from user REST -> CLAMP_Runtime: [REST] Request Creation of Automation Composition Instance
CLAMP_Runtime -> CLAMP_Runtime: Create Automation Composition Instance
CLAMP_Runtime -> ACM_Database: Store First Version of Automation Composition Instance
CLAMP_Runtime -> REST: [REST] Automation Composition Instance Updated
@enduml |
Note that this dialogue creates the Automation Composition Instance in the Instantiated Automation Composition Inventory. The instance is sent to the participants using the process described in the dialogue in Section 2.3.
3.2 Updating Instance Specific Parameters on an Automation Composition Instance
| PlantUML Macro |
|---|
@startuml
participant REST participant CLAMP_Runtime
database ACM_Database REST -> CLAMP_Runtime: [REST] Read Automation Composition Instances
CLAMP_Runtime -> ACM_Database: Read Automation Composition Instances
CLAMP_Runtime -> REST: [REST] Automation Composition Instances returned REST -> REST: Select Automation Composition Instance on which to Update Parameters REST -> REST: Step version of Automation Composition Instance as Major/Minor/Patch REST -> CLAMP_Runtime: [REST] Fetch GUI fields for Instance Specific Parameter Definitions
CLAMP_Runtime -> ACM_Database: Read Automation Composition Type Definition
CLAMP_Runtime -> CLAMP_Runtime: Generate fields for Instance Specific Parameters for GUI
CLAMP_Runtime -> REST: [REST] Return GUI fields Instance Specific Parameter Definitions REST -> REST: Render UI for Instance Specific Parameters REST -> REST: Get values for Instance Specific Parameters from user REST -> CLAMP_Runtime: [REST] Request Update of Automation Composition Instance
CLAMP_Runtime -> CLAMP_Runtime: Update Automation Composition Instance
CLAMP_Runtime -> ACM_Database: Store New Version of Automation Composition Instance
CLAMP_Runtime -> REST: [REST] Automation Composition Instance Updated
@enduml |
3.3 Updating an Automation Composition Instance with a Configuration on Participants
| PlantUML Macro |
|---|
@startuml
participant REST participant CLAMP_Runtime
participant Participant
database ACM_Database REST -> CLAMP_Runtime: [REST] Read all configuration versions of Automation Composition Instance
CLAMP_Runtime -> ACM_Database: Read all configuration versions of Automation Composition Instance
CLAMP_Runtime -> REST: [REST] All configuration versions of Automation Composition Instance returned REST -> REST: Select configuration version of Automation Composition Instance for Instantiation Participants REST -> CLAMP_Runtime: [REST] Instantiate selected configuration version of Automation Composition Instance on Participants
alt Selected configuration version of Automation Composition Instance not instantiated on Participants
CLAMP_Runtime -> ACM_Database: Read configuration version of Automation Composition Instance
CLAMP_Runtime -> Participants: [DMaaP] Update Participants with configuration version of Automation Composition Instance
CLAMP_Runtime -> REST: [REST] Instantiation of configuration version of Automation Composition Instance ordered on participants
else Selected configuration version of Automation Composition Instance instantiated on Participants
CLAMP_Runtime -> REST: [REST] configuration version of Automation Composition Instance already instantiated on participants
end
== Participant Responses ==
Participants -> CLAMP_Runtime: [DMaaP] Result of update of configuration version of Automation Composition Instance on participant
CLAMP_Runtime -> ACM_Database: Store result of update of configuration version of Automation Composition Instance on participant
== Supervision ==
loop forever
CLAMP_Runtime -> ACM_Database: Read Automation Composition Instances
loop over each Automation Composition Instance
alt Automation Composition Instance configuration version update underway on participants
CLAMP_Runtime -> ACM_Database: read result of Automation Composition updates from participants
alt Updates completed on all participants
CLAMP_Runtime -> ACM_Database: set configuration version of Automation Composition Instance as Instantiated on Participants
CLAMP_Runtime -> ACM_Database: set overall configuration version of Automation Composition Instance state as Instantiated
else Updates not completed
alt Instantiation of Automation Composition Instance on participants timed out
CLAMP_Runtime -> ACM_Database: set configuration version Automation Composition Instance Instantiation as timed out on Participants
CLAMP_Runtime -> CLAMP_Runtime: Log error
else Wait for updates to complete
end
end
else Automation Composition Instance configuration version update on participants not underway
end
end
end
@enduml |
3.4 Changing the state of an Automation Composition Instance on Participants
| PlantUML Macro |
|---|
@startuml
participant REST participant CLAMP_Runtime
participant Participant
database ACM_Database REST -> CLAMP_Runtime: [REST] Read all Instantiated Automation Composition Instances
CLAMP_Runtime -> ACM_Database: Read all Instantiated Automation Composition Instances
CLAMP_Runtime -> REST: [REST] All Instantiated Automation Composition Instances returned REST -> REST: Select Automation Composition Instance on which to change state and specify new state REST -> CLAMP_Runtime: [REST] Change state of selected Automation Composition Instance on Participants
alt Selected Automation Composition Instance instantiated on Participants
CLAMP_Runtime -> Participants: [DMaaP] Request change of state of Automation Composition Instance
CLAMP_Runtime -> REST: [REST] Change of state of Automation Composition Instance ordered on participants
else Selected Automation Composition Instance not instantiated on Participants
CLAMP_Runtime -> REST: [REST] Automation Composition Instance not instantiated on participants
end
== Participant Responses ==
Participants -> CLAMP_Runtime: [DMaaP] Result of State Change of Automation Composition Instance on participant
CLAMP_Runtime -> ACM_Database: Store result of State Change of Automation Composition Instance on participant
== Supervision ==
loop forever
CLAMP_Runtime -> ACM_Database: Read Automation Composition Instances
loop over each Automation Composition Instance
alt Automation Composition Instance State Change underway on participants
CLAMP_Runtime -> ACM_Database: read result of Automation Composition State Change from participants
alt Updates completed on all participants
CLAMP_Runtime -> ACM_Database: set Automation Composition Instance state as changed on Participants
CLAMP_Runtime -> ACM_Database: set overall Automation Composition Instance state as changed
else Updates not completed
alt Automation Composition Instance State Change on participants timed out
CLAMP_Runtime -> ACM_Database: set Automation Composition State Change as timed out on Participants
CLAMP_Runtime -> CLAMP_Runtime: Log error
else Wait for updates to complete
end
end
else Automation Composition Instance State Change on participants not underway
end
end
end
@enduml |
3.5 De-instantiating an Automation Composition Instance from Participants
| PlantUML Macro |
|---|
@startuml
participant REST participant CLAMP_Runtime
participant Participant
database ACM_Database REST -> CLAMP_Runtime: [REST] Read all Instantiated Automation Composition Instances
CLAMP_Runtime -> ACM_Database: Read all Instantiated Automation Composition Instances
CLAMP_Runtime -> REST: [REST] All Instantiated Automation Composition Instances returned REST -> REST: Select Automation Composition Instance to de-instantiate REST -> CLAMP_Runtime: [REST] De-instantiate selected Automation Composition Instance on Participants
alt Selected Automation Composition Instance instantiated on Participants
CLAMP_Runtime -> Participants: [DMaaP] Update Participants to remove Automation Composition Instance
CLAMP_Runtime -> REST: [REST] De-instantiation of Automation Composition Instance ordered on participants
else Selected Automation Composition Instance not instantiated on Participants
CLAMP_Runtime -> REST: [REST] Automation Composition Instance not instantiated on participants
end
== Participant Responses ==
Participants -> CLAMP_Runtime: [DMaaP] Result of update of Automation Composition Instance on participant
CLAMP_Runtime -> ACM_Database: Store result of update of Automation Composition Instance on participant
== Supervision ==
loop forever
CLAMP_Runtime -> ACM_Database: Read Automation Composition Instances
loop over each Automation Composition Instance
alt Automation Composition Instance de-instantiation update underway on participants
CLAMP_Runtime -> ACM_Database: read result of Automation Composition updates from participants
alt Updates completed on all participants
CLAMP_Runtime -> ACM_Database: set Automation Composition Instance as de-instantiated on Participants
CLAMP_Runtime -> ACM_Database: set overall Automation Composition Instance as de-instantiated
else Updates not completed
alt Automation Composition Instance de-instantiation Update timed out on participants
CLAMP_Runtime -> ACM_Database: set Automation Composition Instance de-instantiation as timed out on Participants
CLAMP_Runtime -> CLAMP_Runtime: Log error
else Wait for updates to complete
end
end
else Automation Composition Instance de-instantiation update on participants not underway
end
end
@enduml |
3.6 Deleting an Automation Composition Instance
| PlantUML Macro |
|---|
@startuml
participant REST participant CLAMP_Runtime
database ACM_Database REST -> CLAMP_Runtime: [REST] Read all Automation Composition Instances
CLAMP_Runtime -> ACM_Database: Read all Automation Composition Instances
CLAMP_Runtime -> REST: [REST] All Automation Composition Instances returned REST -> REST: Select Automation Composition Instance to delete REST -> CLAMP_Runtime: [REST] Delete selected Automation Composition Instance
alt Selected Automation Composition Instance exists
CLAMP_Runtime -> ACM_Database: Delete Automation Composition instance
CLAMP_Runtime -> REST: [REST] Automation Composition Instance deleted
else Selected Automation Composition Instance does not exist
CLAMP_Runtime -> REST: [REST] Automation Composition Instance does not exist
end
@enduml |
3.7 Reading Automation Composition Instances
| PlantUML Macro |
|---|
@startuml
participant REST participant CLAMP_Runtime
database ACM_Database REST -> CLAMP_Runtime: [REST] Read all Automation Composition Instances
CLAMP_Runtime -> ACM_Database: Read all Automation Composition Instances
CLAMP_Runtime -> REST: [REST] All Automation Composition Instances returned
@enduml |
3. Monitoring Dialogues
Monitoring dialogues are used to monitor and read statistics on Automation Composition Instances.
| PlantUML Macro |
|---|
@startuml
participant CLAMP_Runtime
participant Participant
database ACM_Database
Participant -> CLAMP_Runtime: [DMaaP] Participant and Automation Composition Element Monitoring and Statistics report
CLAMP_Runtime -> ACM_Database: Store Participant and Automation Composition Element Monitoring and Statistics report
alt Fault reported on Participant
CLAMP_Runtime -> CLAMP_Runtime: log fault on Participant
CLAMP_Runtime -> ACM_Database: Record fault on Participant
end
loop Over all Automation Composition Elements in Participant Report
alt Fault reported on Automation Composition Element
CLAMP_Runtime -> CLAMP_Runtime: log fault on Automation Composition Element and Automation Composition CLAMP_Runtime -> ACM_Database: Record fault on Automation Composition Element and Automation Composition end
end
@enduml |
| PlantUML Macro |
|---|
@startuml
participant REST participant CLAMP_Runtime
database ACM_Database
== Overview of all Automation Composition Instances == REST -> CLAMP_Runtime: [REST] Read all Automation Composition Instances
CLAMP_Runtime -> ACM_Database: Read all Automation Composition Instances
CLAMP_Runtime -> REST: [REST] All Automation Composition Instances returned REST -> REST: Display overview of status of all Automation Composition Instances
== Details of a Automation Composition Instance == REST -> CLAMP_Runtime: [REST] Read Automation Composition Elements for Automation Composition Instance
CLAMP_Runtime -> ACM_Database: Read Automation Composition Elements for Automation Composition Instance
CLAMP_Runtime -> REST: [REST] Automation Composition Elements returned REST -> REST: Display status of Automation Composition Elements in Automation Composition Instance
== Overview of all Participants == REST -> CLAMP_Runtime: [REST] Read all participants
CLAMP_Runtime -> ACM_Database: Read all participants
CLAMP_Runtime -> REST: [REST] All participants returned REST -> REST: Display overview of status of all participants
== Details of a Participant == REST -> CLAMP_Runtime: [REST] Read Automation Composition Elements for Participant
CLAMP_Runtime -> ACM_Database: Read Automation Composition Elements for Participant
CLAMP_Runtime -> REST: [REST] Automation Composition Elements returned REST -> REST: Display status of Automation Composition Elements in Participant
== Filtered Monitoring == REST -> REST: Set filter for Automation Composition Instances, Automation Composition Elements, and Participants REST -> CLAMP_Runtime: [REST] Read Automation Composition Elements that match filter
CLAMP_Runtime -> ACM_Database: Read Automation Composition Elements that match filter
CLAMP_Runtime -> REST: [REST] Automation Composition Elements that match filter returned REST -> REST: Display status of Automation Composition Elements that match filter
@enduml |
3.2 Viewing of Statistics
| PlantUML Macro |
|---|
@startuml
participant REST participant CLAMP_Runtime
database ACM_Database
== Statistics of all Automation Composition Instances == REST -> CLAMP_Runtime: [REST] Read summary statistics for all Automation Composition Instances
CLAMP_Runtime -> ACM_Database: Compile summary statistics for all Automation Composition Instances
CLAMP_Runtime -> REST: [REST] Summary statistics for all Automation Composition Instances returned REST -> REST: Display summary statistics for all Automation Composition Instances
== Statistics of a Automation Composition Instance == REST -> CLAMP_Runtime: [REST] Read statistics for Automation Composition Elements for Automation Composition Instance
CLAMP_Runtime -> ACM_Database: Compile statistics for Automation Composition Elements for Automation Composition Instance
CLAMP_Runtime -> REST: [REST] Statistics for Automation Composition Elements returned REST -> REST: Display statistics for Automation Composition Elements in Automation Composition Instance
== Statistics of all Participants == REST -> CLAMP_Runtime: [REST] Read summary statistics for all Automation Composition Instances
CLAMP_Runtime -> ACM_Database: Compile summary statistics for all Automation Composition Instances
CLAMP_Runtime -> REST: [REST] Summary statistics for all Automation Composition Instances returned REST -> REST: Display summary statistics for all Automation Composition Instances
== Statistics of a Participant == REST -> CLAMP_Runtime: [REST] Read statistics for Automation Composition Elements for Participant
CLAMP_Runtime -> ACM_Database: Read statistics for Automation Composition Elements for Participant
CLAMP_Runtime -> REST: [REST] Statistics for Automation Composition Elements returned REST -> REST: Display statistics for Automation Composition Elements in Participant
== Filtered Statistics == REST -> REST: Set filter for Automation Composition Instances, Automation Composition Elements, and Participants REST -> CLAMP_Runtime: [REST] Read statistics for Automation Composition Elements that match filter
CLAMP_Runtime -> ACM_Database: Read statistics for Automation Composition Elements that match filter
CLAMP_Runtime -> REST: [REST] Statistics for Automation Composition Elements that match filter returned REST -> REST: Display statistics for Automation Composition Elements that match filter
@enduml |
3.3 Statistics Housekeeping
| PlantUML Macro |
|---|
@startuml
participant CLAMP_Runtime
database ACM_Database
== Automation Composition Instance Statistics ==
loop forever
CLAMP_Runtime -> ACM_Database: Read Automation Composition Instance Statistics
CLAMP_Runtime -> CLAMP_Runtime: Summarise Automation Composition Instance Statistics
CLAMP_Runtime -> ACM_Database: Store summarised Automation Composition Instance Statistics
CLAMP_Runtime -> ACM_Database: Delete Automation Composition Instance Statistics on which retention period has expired
end
== Participant Statistics ==
loop forever
CLAMP_Runtime -> ACM_Database: Read Participant Statistics
CLAMP_Runtime -> CLAMP_Runtime: Summarise Participant Statistics
CLAMP_Runtime -> ACM_Database: Store summarised Participant Statistics
CLAMP_Runtime -> ACM_Database: Delete Participant Statistics on which retention period has expired
end
@enduml |
4. Supervision Dialogues
Supervision dialogues are used to check the state of Automation Composition Instances and Participants.
4.1 Supervise Participants
| PlantUML Macro |
|---|
@startuml
participant CLAMP_Runtime
database ACM_Database
loop forever
CLAMP_Runtime -> ACM_Database: Read Participants
loop Over each Participant
alt Participant has not reported in last reporting window
CLAMP_Runtime -> CLAMP_Runtime: Log Participant as having missed a report
CLAMP_Runtime -> ACM_Database: Increment missed report counter on Participant
alt Participant has exceeded alarm threshold on missed report counter
CLAMP_Runtime -> CLAMP_Runtime: Raise a Participant Offline alarm on participant
CLAMP_Runtime -> ACM_Database: Mark participant as being offline
end
else Participant has reported in last reporting window
CLAMP_Runtime -> ACM_Database: Clear missed report counter on Participant
alt Participant marked as being offline
CLAMP_Runtime -> CLAMP_Runtime: Clear Participant Offline alarm on participant
CLAMP_Runtime -> ACM_Database: Mark participant as being online
end
end
end
end
@enduml |
4.2 Supervise Automation Compositions
| PlantUML Macro |
|---|
@startuml
participant CLAMP_Runtime
database ACM_Database
loop forever
CLAMP_Runtime -> ACM_Database: Read Automation Composition Instances
loop Over each Automation Composition Instance
loop Over each Automation Composition Element
alt Automation Composition Element has not reported in last reporting window
CLAMP_Runtime -> CLAMP_Runtime: Log Automation Composition Element as having missed a report
CLAMP_Runtime -> ACM_Database: Increment missed report counter on Automation Composition Element
else Automation Composition Element has reported in last reporting window
CLAMP_Runtime -> ACM_Database: Clear missed report counter on Automation Composition Element
end
alt Automation Composition Element in incorrect state in last reporting window
CLAMP_Runtime -> CLAMP_Runtime: Log Automation Composition Element as being in incorrect state
CLAMP_Runtime -> ACM_Database: Record Automation Composition Element as being in incorrect state
else Automation Composition Element not in incorrect state in last reporting window
alt Automation Composition Element was in incorrect state on previous report
CLAMP_Runtime -> CLAMP_Runtime: Log Automation Composition Element as being in correct state
CLAMP_Runtime -> ACM_Database: Record Automation Composition Element as being in correct state
end
end
alt Automation Composition Element reported fault in last reporting window
CLAMP_Runtime -> CLAMP_Runtime: Log Automation Composition Element as being faulty
CLAMP_Runtime -> ACM_Database: Record Automation Composition Element as being faulty
else Automation Composition Element did not report fault in last reporting window
alt Automation Composition Element reported fault on previous report
CLAMP_Runtime -> CLAMP_Runtime: Log Automation Composition Element fault as cleared
CLAMP_Runtime -> ACM_Database: Mark fault Automation Composition Element as being cleared
end
end
end
alt Automation Composition Element in Automation Composition Instance has exceeded alarm threshold on missed report counter
CLAMP_Runtime -> CLAMP_Runtime: Raise a Automation Composition Offline alarm on Automation Composition Instance
CLAMP_Runtime -> ACM_Database: Mark Automation Composition Instance as being offline
else No Automation Composition Element in Automation Composition Instance has exceeded alarm threshold on missed report counter
alt Automation Composition Instance marked as being offline
CLAMP_Runtime -> CLAMP_Runtime: Clear Automation Composition Instance Offline alarm on Automation Composition
CLAMP_Runtime -> ACM_Database: Mark Automation Composition Instance as being online
end
end
alt Automation Composition Element in Automation Composition Instance in incorrect state in last reporting window
CLAMP_Runtime -> CLAMP_Runtime: Log Automation Composition Instance as being in incorrect state
CLAMP_Runtime -> ACM_Database: Record Automation Composition Instance as being in incorrect state
alt Automation Composition Element in Automation Composition Instance has exceeded alarm threshold on incorrect state reports
CLAMP_Runtime -> CLAMP_Runtime: Raise a Automation Composition Instance in Incorrect State alarm on Automation Composition Instance
CLAMP_Runtime -> ACM_Database: Mark Automation Composition Instance as being in an incorrect state
end
else No Automation Composition Element in incorrect state in last reporting window
alt Automation Composition Element in Automation Composition Instance was in incorrect state on previous report
CLAMP_Runtime -> CLAMP_Runtime: Log Automation Composition Instance as being in correct state
CLAMP_Runtime -> ACM_Database: Record Automation Composition Instance as being in correct state
alt Automation Composition Instance in Incorrect State alarm raised on Automation Composition Instance
CLAMP_Runtime -> CLAMP_Runtime: Clear Automation Composition Instance in Incorrect State alarm on Automation Composition Instance
end
end
end
alt Automation Composition Element in Automation Composition Instance reported a fault in last reporting window
CLAMP_Runtime -> CLAMP_Runtime: Log Automation Composition Instance as being faulty
CLAMP_Runtime -> ACM_Database: Record Automation Composition Instance as being faulty
alt Automation Composition Element in Automation Composition Instance has exceeded alarm threshold on faulty reports
CLAMP_Runtime -> CLAMP_Runtime: Raise a Automation Composition Instance Faulty alarm on Automation Composition Instance
end
else No Automation Composition Element faulty in last reporting window
alt Automation Composition Element in Automation Composition Instance was faulty on previous report
CLAMP_Runtime -> CLAMP_Runtime: Log Automation Composition Instance as being fault free
CLAMP_Runtime -> ACM_Database: Record Automation Composition Instance as being fault free
alt Automation Composition Instance Faulty alarm raised on Automation Composition Instance
CLAMP_Runtime -> CLAMP_Runtime: Clear Automation Composition Instance Faulty alarm on Automation Composition Instance
end
end
end
end
end
@enduml |
