To get started, you need a station with a tag dictionary that defines tags, tag groups and relations) and a hierarchical tree structure for devices and points.
Applying dictionary tags to the components in the station’s hierarchy creates a data model.
Applying tags and configuring properties answer the significant questions: what? where? how far back? and which?
History file or real-time value (identified by a Value Ord) to use. If multiple values are involved, the Px properties identify which node to search for multiple instances of a given
data source.Time Range property defines how far back in time to go when collecting data. Properties define how to represent output (the roll up
of history using an interval or the aggregation of multiple current and historical values), and how to calculate values (sum,
average, etc.)Once all properties and nodes are configured, request results are available as needed in Px views and through the use of
Parent and child nodes arranged in a hierarchal tree comprise the primary organizational unit of the data model. Nodes can contain other nodes. They may represent geographical locations, groups of buildings, individual buildings, types of systems, types of tenants, devices, and so forth. Generally, they represent tangible things in the data model.
Proxy nodes in a Supervisor station imitate nodes in a remote station. Their input values mirror the input device values contained in the remote station.
You assign tags to nodes. Tags identify types of nodes. For example, your application may include many buildings, each with a unique name. When you tag each structure with the “building” tag, formulas or diagnostics can easily find all of them.