...
- The Automation Composition Type must be created, that is the Automation Composition Type definition must be loaded and stored in the database. This step may be carried out over the REST interface or using SDC distribution.
- The Common Properties of the Automation Composition type must be assigned values and those values must be stored in the database. This step is optional only if all mandatory common properties have default values. The Common Property values may be set and amended over and over again in multiple sessions until the Automation Composition Type is primed.
- The Automation Composition Type Definition and the Common Property values must be primed, which is sent to the concerned participants. Once an Automation Composition Type is primed, its Common Property values can no longer be changed. To change Common Properties on a primed Automation Composition Type, all instances of the Automation Composition Type must be removed and the Automation Composition Type must be de-primed.
1.1 Commissioning an Automation Composition Type Definition using the
...
ACM REST Interface
This dialogue corresponds to a "File→Import" menu on the CLAMP GUI. The documentation of future releases of the system will describe how the Design Time functionality interacts with the Runtime commissioning API.
PlantUML Macro |
---|
@startuml participant CLAMP_GUI participant CLAMP_Runtime database Commissioned_ACM_Inventory CLAMP_GUI -> CLAMP_Runtime: [REST] Commission Automation Composition Type Definition CLAMPACM_Runtime -> Commissioned_ACM_Inventory: Store Automation Composition Type Definition CLAMPACM_Runtime -> CLAMP_GUI: [REST]REST: Type Definition Commissioned @enduml |
...