Open Application Server (OAS) - Metasys - LIT-12011832 - General System Information - Metasys System - 12.0

Metasys System Configuration Guide
Brand
Metasys
Product name
Metasys System
Document type
Configuration Guide
Document number
LIT-12011832
Version
12.0
Revision date
2024-03-25
Product status
Active
Language
English

The OAS combines many of the functions of a Network Engine with a Metasys Server into a single piece of software with optional add-on features that can be hosted on a virtual machine with required specifications or can be purchased as a turnkey offering, where Johnson Controls provides hardware with software already installed on it.

There are two licensing options available for the OAS, the OAS Minimum (M4-OASMIN-0) and the OAS Standard (M4-OASSTD-0). The OAS Minimum is a variant of the OAS offering whose capabilities are license-limited. The OAS Minimum cannot supervise child network engines unless a migration license (M4-OASSTD-8) is purchased. The OAS Minimum is offered at a lower price point than the OAS Standard. This provides an affordable Server option for smaller or less complex projects. For more information about the OAS versions, see the following table:
Table 1. OAS versions
Features OAS Minimum OAS Standard
     
Supports Metasys UI Yes Yes
Supports engines No Two
Can license add-ons
Note: Fault Detection and Fault Triage are not supported on the turnkey solution.
 Yes Yes
Direct support for field devices 200 200
Supports SMP Yes Yes
Note: Do not install SCT or CCT on the OAS Turnkey computer. If you need SCT or CCT for commissioning the job site, install the tools on a different computer with network accessibility to the OAS. However, if you host the OAS on a virtual machine (VM), you can install SCT and CCT on the same VM as the OAS software.

As a Site Director, the OAS Standard supports up to two supervisory devices, 200 field devices, and 20,000 objects using BACnet/IP and Remote Field Bus integrations. The OAS supports integration with the following devices and systems: C•CURE-victor, Modbus, M-Bus, KNX, and OPC Unified Architecture (UA).

The maximum number of supported simultaneous vendor integrations on an OAS is 8. The following table provides more information about the available integrations, whereby the limits relate to standard protocol drivers only.
Table 2. Vendor integration types and numbers
Vendor integration type Maximum number of supported simultaneous integrations (standard protocol drivers)
Modbus (TCP or RS-485) 4
M-Bus 4
KNX 2
C•CURE-victor 1
OPC Unified Architecture (UA) 1
Zettler Not supported. Zettler requires a serial connection. Serial connection is not supported on the OAS and the Zettler driver is not included in the OAS platform. The Zettler driver is included only in engines with Linux-based platforms.

The OAS provides database software options for archiving licensed historical data using the Microsoft® SQL Server software database, and it enables secure communication to a range of Network Engines, including the NAEs, NCEs, SNEs, and SNCs. The OAS is compatible with both Metasys UI and Site Management Portal (SMP). You can configure the OAS through the System Configuration Tool (SCT).

The following table provides a summary of the OAS Standard capabilities:
Table 3. OAS Standard capabilities
ADS-type capabilities Network Engine-type capabilities
Supports supervising up to two network engines (SNE, SNC, NAE, or NCE Series). Supports supervising up to 200 field devices directly or 20,000 objects, using BACnet/IP and Remote Field Bus integrations.
Provides the Metasys UI, an intuitive, well-organized, mobile-friendly user interface. Provides supervisory capabilities such as scheduling, alarming, trending, data sharing, interlocking, and logic for system-wide control and coordination.
Optionally (with add-on licenses) provides long term archival of historical data, trends, alarms, and events.  
Figure 1. OAS system diagram