...
| draw.io Diagram | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
The The Design Time Catalogue contains the the metadata primitives for composition of control loops. As shown in the figure above, the Design time component provides a system where Control Loops can be designed and defined in metadata. This means that a Control Loop can have any arbitrary structure and the Control Loop developers can use whatever analytic, policy, or control primitives they like to implement their Control Loop. At deployment time, the user parameterises the Control Loop and deploys it. A design time catalogue is created. This catalogue contains the primitive metadata for any components that can be used to compose a Control Loop. A Control Loop SDK is used to compose a Control Loop by aggregating the metadata for the components chosen to be used in a Control Loop and by constructing the references between the components.
...
This section defines Deployment/CRUD Operations that can be performed on ControlLoops.
A Client, in this case CLAMP, can perform CRUD operations or can deploy ControlLoops from DesignTime to RunTime Catalogue Database.
DesignTime/RunTime Catalogue Database stores ControlLoop definitions, CRUD operations on database supported by REST Endpoints like Get, Delete, Create allowing selection of a particular ControlLoop to be addressed, below sequence diag diagram will help you understand flow how a client(Clamp) application can initiate Rest call for performing different operations on Database.
...
The deployment of ControlLoops definition from DesignTime to RunTime Catalogue Database can we achived using deploy Rest Endpoint, in this process when a rest request is initiated from a client(Clamp) the CL_Instance_Control Service take cares of fetching ControlLoops metadata from DesignTime and creates in RunTime Catalogue Database, Deploy API ControlLoop Sequence diag diagram will help you understand the flow.
...