...

1. Participant Registration. This capability allows participants to register and deregister with CLAMP. The post condition for an execution of this capability is that a participant is available for participation in a control loop.
2. Control Loop Commissioning. This capability allows version controlled Control Loops to be taken from the Control Loop Design Time Catalogue and be placed in the Control Loop Run Time Catalogue. It also allows configuration of parameters that apply to the Control Loop Type, that is parameters that will apply to all control loop instances. Further, it allows control loop types to be commissioned on participants. Data that applies to all instances of a control loop type on a participant is sent to a participant. The participant can then take whatever actions it need to do to support the control loop type in question. The post condition for an execution of this capability is that the Control Loop definition is in the Control Loop Run Time Catalogue and all participants in this control loop type are commissioned, that is they are prepared to run instances of this control loop type.
3. Control Instantiation. This capability allows an instance of a control loop to be created. The control loop instance can The control loop definition is read from the Control Loop Run Time Catalogue and values are assigned to the parameters defined for the control loop. The control loop instance is created by instantiating the control loop instance parts in each participant by sending each participant its metadata. Once the control loop is instantiated on each participant, the Control Loop instance is marked as instantiated in the Control Loop Run Time Catalogue. The post condition for an execution of this capability is that the Control Loop instance is running on participants and is processing events.
4. Control Loop Monitoring. This capability allows control loops to be monitored. Users can check the status of a control loop instances and the status of each participant in a control loop instance. Control loop participants report their overall status and domain status periodically to CLAMP. Clamp aggregates these status reports into an aggregated control loop instance status record, which is available for monitoring. The post condition for an execution of this capability is that control loop instances are being monitored.

Once a control loop definition has been commissioned, instances of the control loop can be created, updated, and deleted. The system manages the lifecycle of control loops following the state transition diagram below.

1: Overall Architecture

The diagram below shows an overview of the architecture of TOSCA based Control Loop management.

...