Trend Historian
Canary Labs' high-speed data solution is fully compliant with the OPC Historical Data Access (HDA) specification making integration with your existing PLC's, Scada systems, HMI software or DCS systems seamless.
The Trend Historian has been proven effective for applications ranging from 100 tags to well over 100,000 tags, demonstrating scalability without the need for excessive computing hardware, unlike most Historians commercially available.
Canary Labs delivers the highest level of analysis on historical data, as Trend Historian does not leverage compression algorithms to improve performance. With Canary Labs, our clients get the ability to log in excess of 700,000 updates per second, with the smallest hardware footprint, and industry leading performance.
Trend Historian Administrator
The Trend Historian Administrator tool is used to configure and monitor the Trend Historian server. It can be connected to either a local or remote Trend Historian allowing a user to monitor and configure all Trend Historians from a single location. The Historian Administrator is organized into 6 different components; general administration, dataset management, client administration, performance management, Audit administration, and detail analysis.
Through the various components of the Historian Administrator, operators have complete control over the configuration and event management specific to the Trend Historian application. This level of access ensures optimal performance and a complete audit trail of all activities.
Canary Logger
The Canary Logger enables operators to pull in data from any OPC Data Access interface. OPC is the most prevalent standard in the industry with over 400 participating organizations ensures Canary Logger can interface with almost any commercially use application today.
Logging to a centralized Network Server
In a distributed network application, The Canary Logger service can setup to run on various data collection machines and then push the historical data back to a centralized network server for storage.
Logger Service Cache and Forward

When the Canary Logger Service is logging to a remote Historian Service and the connection is lost for a period of time, the Logger will start caching the trend data in memory. It will then automatically try to re-establish the connection back to the Trend Historian Service. If it fails to make the reconnection, it will retry once every minute. When a successful connection is made, it will send the data that has been cached. The amount of trend data that can be cached in memory depends on the number of tags and the physical memory in the logger PC. This feature protects the integrity of the trend data, should a short-term communication failure occur.
Tag Configuration

When defining the tags whose data will be collected from an OPC server and logged into the Trend Historian, the user will create a logging group. This group defines a set of tags that will be collected from an OPC server at a defined frequency. Tags can easily be added to a group by a simple click. A list of available tags in the OPC server is presented in a dialog box, where the user can select the tags to be added into the group.
