Repositories - Metasys - LIT-1201645 - MS-ADSxxx-x - MS-ADXxxx-x - Server - ADS Server - ADX Server - 12.0

ADS/ADX Commissioning Guide

Product
Building Automation Systems > Databases and Data Servers > ADS Server
Building Automation Systems > Application Servers > ADX Server
Document type
Commissioning Guide
Document number
LIT-1201645
Version
12.0
Revision date
2022-09-22
Product status
Active
Important: The ADS Repositories attribute in the engine or server determines where the device sends historical information. The Default ADS Repositories attribute in the Site object defines where historical data is stored. By default, these repository attributes are blank. Be sure to enter the address or name of your repository device (typically the Site Director) in these attributes to ensure that you do not lose historical data. For the Site Director itself, leave the ADS Repositories attribute blank if the Site Director also serves as the repository. The Default ADS Repositories attribute defines the location of the ADS repository for all devices on the site that do not have the ADS Repositories attribute defined on their own. The ADS Repositories attribute, once defined on a network engine, overwrites the Default ADS Repositories attribute of the site for that engine.

Three new SQL databases: MetasysValue, MetasysFault, and MetasysFaultTriage were introduced at Metasys Release 11.0. To activate the databases, license the associated Metasys features. These include, Potential Problem Areas, Fault Detection, and Fault Triage. The MetasysValue and MetasysFault databases self-maintain and store a rolling seven days’ worth of data. These databases are not monitored or managed by Metasys Database Manager.

A repository provides long-term storage for historical data. Typically, the ADS/ADX configured as the Site Director also provides the individual repositories for trend data, event messages, audit messages, annotations, reporting, spaces authorization, potential problem areas, fault detection, and fault triage data. Individual repositories may reside in the SQL Server database. For a split ADX, the repositories are on the database server where the SQL Server software is installed. You can install a split ADX where the database server computer stores all historical data.

Note: The ADS-Lite cannot be a Site Director for other ADS or ADX servers.

The following table lists the ADS/ADX repositories, the corresponding online Metasys SMP Help (LIT-1201793) or Metasys UI Help (LIT-12011953) topic, and the corresponding file name. The next sections describe the repositories in more detail and suggest ways to optimize the repositories.

Table 1. ADS/ADX Repositories

Repository

Refer To

Database File Name on the ADS/ADX Computer

Trends

Trend Extensions in the Metasys SMP Help (LIT-1201793)

JCIHistorianDB

Audits

Audit Trail in the Metasys SMP Help (LIT-1201793)

JCIAuditTrails

Events

Alarm and Event Management in the Metasys SMP Help (LIT-1201793)

JCIEvents

Annotation
Note: Metasys UI does not use this database.

Annotating Objects/Items in the Metasys SMP Help (LIT-1201793)

JCIItemAnnotation

Reporting

Advanced Reporting in the Metasys SMP Help (LIT-1201793)

MetasysReporting

Metasys UI Reporting

Reporting: Trend Widget and Custom Trend Viewer in the Metasys UI Help (LIT-12011953)

JCIReportingDB

Spaces Authorization

User Authorization and Dashboard Manager in the Metasys UI Help (LIT-12011953).

SpacesAuthorization

Potential problem areas

Potential problem areas section in the Metasys UI Help (LIT-12011953)

MetasysValue

Fault detection

Potential problem areas section in the Metasys UI Help (LIT-12011953)

MetasysFault

Fault triage

Potential problem areas section in the Metasys UI Help (LIT-12011953)

MetasysFaultTriage