| alert | A warning regarding a condition identified by a
|
| algorithm | A formula that uses real-time values, historical trend data, and the results of calculations made by other algorithms to analyze data collected by the system. |
| direct tag/relation | A tag or relationship that has been manually associated with an entity. |
| implied tag/relation | A tag or relationship tag automatically assigned by the system to an entity. |
| request | The query for input data that seeks either a point’s current or historical value. |
| scope | In programming, the range within a program’s source code within which an element name is recognized without qualification. Variable definitions are not limited to the beginning of a block of code, however, they must be declared before they can be used. In Niagara, the scope of an action applies to the selected components. The component tree is hierarchical. If you delete or move a component that contains other components, you are deleting or moving all items that are contained in that container component (its scope). |
| tag | A piece of semantic information (metadata) associated with a device or point (entity) for the purpose of filtering or grouping
entities. Tags identify the purpose of the component or point and its relationship to other entities. For example, you may
wish to view only data collected from meters located in maintenance buildings as opposed to those located in office buildings
or schools. For this grouping to work, the metering device in each maintenance building includes a tag that associates the
meter with all the other maintenance buildings in your system.
Controllers are associated with Supervisors based on tags; searching is done based on tags. Tags are contained in tag dictionaries. Each tag dictionary is referenced by a unique namespace. |