Page History

...

1. Control Loop Commissioning. This capability allows version controlled Control Loop Type definitions to be taken from the Control Loop Design Time Catalogue and be placed in the Commissioned Control Loop Inventory. It also allows the values of Common Property Types that apply to all instances of a Control Loop Type to be set. Further, the Control Loop Type is primed on all concerned participants. The post condition for an execution of this capability is that the Control Loop Type definition is in the Commissioned Control Loop Inventory and the Control Loop Type is primed on concerned participants.
2. Control Loop Instance Life Cycle Management.  This capability allows a Control Loop Instance to have its life cycle managed.
   
   1. Control Loop Instance Creation: This capability allows a Control Loop Instance to be created. The Control Loop Type definition is read from the Commissioned Control Loop Inventory and values are assigned to the Instance Specific Property Types defined for instances of the Control Loop Type in the same manner as the existing CLAMP client does. A Control Loop Instance that has been created but has not yet been instantiated on participants is in state UNINITIALIZED. In this state, the Instance Specific Property Type values can be revised and updated as often as the user requires. The post condition for an execution of this capability is that the Control Loop instance is created in the Instantiated Control Loop Inventory but has not been instantiated on Participants.
   2. Control Loop Instance Update on Participants: Once the user is happy with the property values, the Control Loop Instance is updated on participants and the Control Loop Elements for this Control Loop Instance are initialized or updated by participants using the control loop metadata. The post condition for an execution of this capability is that the Control Loop instance is updated on Participants.
   3. Control Loop State Change: The user can now order the participants to change the state of the Control Loop Instance. If the Control Loop is set to state RUNNING, each participant begins accepting and processing control loop events and the Control Loop Instance is set to state RUNNING in the Instantiated Control Loop inventory. The post condition for an execution of this capability is that the Control Loop instance state is changed on participants.
   4. Control Loop Instance Monitoring. This capability allows Control Loop Instances to be monitored. Users can check the status of Participants, Control Loop Instances, and Control Loop Elements. Participants report their overall status and the status of Control Loop Elements they are running 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.
   5. Control Loop Instance Supervision. This capability allows Control Loop Instances to be supervised. The CLAMP runtime expects participants to report on Control Loop Elements periodically. The CLAMP runtime checks that periodic reports are received and that each Control Loop Element is in the state it should be in. If reports are missed or if a Control Loop Element is in an incorrect state, remedial action is taken and notifications are issued. The post condition for an execution of this capability is that Control Loop Instances are being supervised by the CLAMP runtime.
   6. Control Loop Instance Removal from Participants: A user can order the removal of a Control Loop Instance from participants. The post condition for an execution of this capability is that the Control Loop instance is removed from Participants.
   7. Control Loop Instance Deletion: A user can order the removal of a Control Loop Instance from the CLAMP runtime. Control Loop Instances that are instantiated on participants cannot be removed from the CLAMP runtime. The post condition for an execution of this capability is that the Control Loop instance is removed from Instantiated Control Loop Inventory.
3. Control Loop Decommissioning. This capability allows version controlled Control Loop Type definitions to be removed from the Commissioned Control Loop Inventory. A Control Loop Definition that has instances in the Instantiated Control Loop Inventory cannot be removed. The post condition for an execution of this capability is that the Control Loop Type definition removed from the Commissioned Control Loop Inventory.

2.1 Control Loop Instance States

...