| aggregation | The process of combining multiple pieces of the same type of data into a single value (sum, average, maximum, minimum, median, etc.) Each piece of information comes from a different data source. The request for the specific type of data starts at a specific node and travels down the data model tree aggregating all sources (points) tagged with the search argument tag. |
| 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. |
| analytics | The discovery and presentation of meaningful patterns in data. Analytics rely on the simultaneous application of statistics and computer programming to quantify performance, communicating the results on graphs and charts, as well as using results to control devices. |
| COV or Cov | Change-of-Value. Characterizes the option to track data based on when a value changes rather than at a consistent interval, such as every minute, 15 minutes, etc. |
| data definition, definition | Defines the type of information a request is looking for, such as real energy, zone temperature, air flow quantity, set point, phase A amperage, phase B amperage. Definitions are related to tags in that the definition Id is the tag name space and name used to search the database. |
| data model | A hierarchical tree structure that organizes points based on the usage or reporting of information rather than on the drivers
required to manage physical devices. A typical
|
| 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. |
| origin entity | The object in a hierarchy from which a search begins. |
| request | The query for input data that seeks either a point’s current or historical value. |
| rollup | The process of combining historical data for a single data source into one value (sum, maximum, minimum, average, etc.). |
| 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. |
| trend | The result of analyzing historical data collected by the system. A trend involves rolling up data into meaningful intervals. |