In Niagara, a data log is referred to as a history. Histories are ordered collections of timestamped records. A single “history” is a collection of specific data values from a component within any station - local or remote. Histories are organized by their source station (device), as shown in Figure 125.
The following topics are relevant to understanding histories:
History Services
The History Service, the Audit History service and the Log History service provide support for logging data in a Niagara station. In order to provide database support for histories in a Niagara station, the station must contain the History Service. Refer to About the history service for details about the History Service. Refer to About the audit history service and About the log history service for information about those services.
History ORD scheme
Once you have a history service running, you can access histories that you create in the database using the “history” ORD scheme. The unique history scheme name “history” and each unique history ID provide identification for the individual histories. All history collections are identified by this unique id. For information
on using the ORD scheme to access individual histories, refer to About ORDs.
History space
History space provides a means for viewing and working with histories in the history database. History space is visually represented in Workbench as a node in the nav tree and may be accessed by using the nav tree or by using the Open ORD dialog box. Views on the History space include the following: History Chart Builder, Database Maintenance, Nav Container View. For more information about history space and history space views, refer to Types of history space views.
History views
History views present history information in various formats for both analysis and editing. Refer to Types of history views.
History logging process
Using histories involves a process of collecting, storing and archiving data. You can configure the history collection process to collect the data that you need and store the history records where you want them - locally or remotely. This process is described in more detail in About the history process.
History Configuration
History configuration includes working with parameters such as ID, history source, timezone, record type, and more. For more details on configuration, refer to Configure history extensions.
History data editing
You can edit and filter the history data in workbench using the history editor view (described in About the history editor view). The editing process is described in more detail in About editing history data.
History Grouping
Starting with AX-3.5, this component allows you to use history properties to provide custom organization and display of history space contents. See About history grouping for more details.
History Nav Shortcuts
Available starting with AX-3.5, history nav shortcuts
provide convenience navigation links to histories. See About history nav shortcuts for more details.
Copyright © 2000-2016 Tridium Inc. All rights reserved.