Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Commissioning dialogues are used to commission and decommission Control Loop Type definitions and to set the values of Common Parameters.

Commissioning a Control Loop Type is a three-step process

  1. The Control Loop Type must be created, that is the Control Loop Type definition must be loaded and stored in the database. This step may be carried out over the REST interface or using SDC distribution.
  2. The Common Properties of the Control Loop 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 Control Loop Type is primed.
  3. The Control Loop Type Definition and the Common Property values must be primed, that is sent to the concerned participants. Once a Control Loop Type is primed, its Common Property values can no longer be changed. To change Common Properties on a primed Control Loop Type, all instances of the Control Loop Type must be removed and the Control Loop Type must be de-primed.

1.1 Commissioning a Control Loop Type Definition using the CLAMP GUI

...

1.4 Priming a Control Loop Type Definition on Participants

The Priming operation sends Control Loop Type definitions and common property values to participants. Once a Control Loop Type definition is primed, its property values can on longer be changed until it is de-primed.

1.5 De-Prime a Control Loop Type Definition on Participants

...