You can use a System Model to organize a Citect SCADA project in a way that reflects the physical production system. This will simplify the configuration of a project, and deliver inherent logic when the project is executed at runtime.
You can build a System Model into a project through equipment definitions and tags.
Equipment facilitates the creation of an object-oriented System Model in a Citect SCADA project. This allows you to logically reference production system hardware based on its location in an equipment hierarchy.
Equipment definitions use dot notation to indicate levels within this hierarchy. For example, the equipment name "Plant.Mixer.Line1.Pump" refers to the current selection in the following equipment hierarchy:
Each piece of equipment become a parent to the tags that are associated with it. At runtime, the hierarchy can be used to search and display information in a way that is logically aligned with your System Model.
In a Citect SCADA project, you use tags to label the inputs and outputs on your production system hardware. They can include variables, trends, alarms, accumulators, and so on.
A structured tag naming strategy that logically reflects geographical areas or processes within a plant is an example of a way you can use tags to implement a simple System Model. This type of approach means the purpose of each tag is inherently clear through its name.
To configure tags and equipment in a Citect SCADA project, you use the System Model activity in Citect Studio.
See Also
Published June 2018