Metasys UI uses for repositories - Metasys - LIT-12012115 - Server - Metasys UI - 11.0

Metasys UI Technical Bulletin
Product
Building Automation Systems > Graphics and Interfaces > Metasys UI
Document type
Technical Bulletin
Document number
LIT-12012115
Version
11.0
Revision date
2020-10-30
Product status
Active

The following table lists the corresponding features of the Metasys UI that use the repository databases.

Table 1. Metasys UI uses for repositories

Repository

Metasys UI feature

Database

Trends

Reporting data that displays in the Trend widget and the Custom Trend viewer; syncs with the JCIReportingDB repository at installation and then once in every 24-hour period

JCIHistorianDB

Audits

Audit data for user and system commands and user annotations on commands that display in the Equipment Activity widget and System Activity.

JCIAuditTrails

Events

Alarm data, event message annotations, and user annotations on alarm events that display in the Equipment Activity widget, Alarm Panel, Alarm Manager, and Alarm Monitor

JCIEvents

Reporting

Reporting data that displays in the Trend widget and Custom Trend viewer

JCIReportingDB

Spaces Authorization

User permissions data for Spaces and Custom Dashboard settings

SpacesAuthorization

Potential Problem Areas

Point data that displays in the Points tab of the Potential Problem Areas widget. The database self-maintains and stores a rolling seven days' worth of data.

MetasysValue

Note: You need to license the Potential Problem Areas Points on an OAS to activate the MetasysValue database.

Fault Detection

Fault data that displays in the Faults tab of the Potential Problem Areas widget. The database self-maintains and stores a rolling seven days' worth of data.
MetasysFault
Note: You need to license the Fault Detection feature to activate the MetasysFault database.

Fault Triage

Fault Triage data that displays in the Fault Triage feature.

MetasysFaultTriage
Note: You need to license the Fault Triage feature to activate the MetasysFaultTriage database.

At installation time, the JCIHistorianDB synchronizes with the JCIReportingDB. This initial synchronization can take several hours. The average synchronization takes an hour per 5 to 10 GB. While the synchronization takes place, the Metasys UI Trend widget is available, but the historical trend data may not appear until the synchronization is complete.

The Metasys UI does not support annotations on objects, such as an engine, controller, or points.