System Overview - Metasys - LIT-12011942 - Software Application - ODS Server - 10.1

Metasys Open Data Server Help

Product name
ODS Server
Document type
User Guide
Document number
Revision date

The major components of the Metasys system are:

Open Data Server (ODS): The ODS is a BTL-Listed BACnet Operator Workstation that conforms to the B-OWS profile and is BTL-Certified in Europe. To differentiate between the user interface of an ODS and ADS or OAS, the ODS UI window and minimized icon have green shading. Three ODS configurations are available: BACnet Workstation, Site Manager Workstation, or a combination of both.

The BACnet Workstation is a computer with an operator UI that you use to monitor and control the Metasys or general BACnet system at your facility. In this configuration, BACnet communication occurs directly between the ODS and the networked BACnet devices. BACnet integration maps in NxEs to the ODS. NxEs are treated the same as BACnet devices. The BACnet Workstation does not serve as a Site Director.

The Site Manager Workstation is a computer with an operator UI you use to monitor and control the Metasys system at your facility. In this configuration, web services communicate to the supervisory devices. The BACnet integration allows communication with BACnet devices. The ODS serves as the Site Director.

In the combined configuration, the ODS serves as a Site Manager Workstation and a BACnet Workstation. In this configuration, the NAE reports to the ODS as its Site Director and BACnet devices can be directly mapped to the ODS through the BACnet integration.

Network Engine: The network engine is a family of devices that supervise lower-level field controllers over the Metasys BAS. Network engines include the Network Automation Engines (NAEs), Network Integration Engines (NIEs), Network Control Engines (NCEs), Series of Network Controllers (SNCs), and Series of Network Engines (SNEs):

  • The NAE and SNE are Ethernet-based supervisory engines that monitor and supervise networks of field-level building automation devices that typically control HVAC equipment, lighting, security, fire, and building access. The features of NAEs and SNEs include alarm and event management, trending, archiving, energy management, scheduling, and password protection through their embedded Site Management Portal. Different models and options support various communications protocols, including BACnet® over IP, BACnet MS/TP, Johnson Controls® N2 Bus, LonWorks, Modbus®, M-Bus, and KNX. The NAE55 and SNE2200 Series support a comprehensive set of supervisory features and functions for large facilities and technically advanced buildings and complexes. The NAE35, NAE45, SNE1050, and SNE1100 Series support the same features and functions of the NAE55 and SNE2200 engines, but are designed for smaller buildings (or small areas of larger buildings) and enable the wider distribution of supervisory functions in larger facilities. Lastly, the NAE85 supports large BACnet/IP integrations with over 10,000 objects.
  • The secure NAE-S is a hardened, secure version of the standard Network Automation Engine (NAE) 55 supervisory engine that uses embedded encryption technology to protect and secure the building management system at the endpoint. The engine meets the Federal Information Processing Standard (FIPS 140-2), Security Level 2, that specifies the use of a cryptographic module and a tamper-proof housing. The engine is also Common Criteria certified.
  • The NCE and SNC combine the network supervisor capabilities and IP network connectivity of a network engine with the Input/Output (I/O) point connectivity and direct digital control capabilities of a field controller. The NCE and SNC are a cost-effective solution designed for central plants and large built-up air handler applications. All NCE and SNC models include IP Ethernet network connectivity, the Site Management Portal, and the network supervisory functions featured on network automation engines. The NCE and SNC support a wide variety of building networks such as BACnet/IP, BACnet MS/TP, Johnson Controls N2 Bus, LonWorks, Modbus, M-Bus, and KNX.
  • The NIEx5 is an Ethernet-based, supervisory engine for integration of Metasys N1 Networks. The NIEx5, which includes the NIE55 and NIE85, is a specialized version of the NAE and is designed to provide for the migration of existing N1 networks into the Metasys system. The NIEx5 has the same Site Management Portal as the NAE. Unlike the NAE, the NIEx5 does not support integration of BACnet MS/TP or BACnet/IP, N2, and LonWorks networks. Two models of the NIEx5 are available. The NIE55 supports smaller N1 networks, while the NIE85 supports larger N1 integrations. The NIE55 and NIE85 engines were retired at Metasys system Release 9.0.
  • The NIEx9 is an Ethernet-based, supervisory engine for integration of building control devices that communicate over the Modbus®, MBus, or KNX protocol. The NIEx9 also communicates over the BACnet MS/TP, BACnet/IP, N2, or LonWorks networks. This specialized version of the NIE is designed to provide for the migration of these existing third-party networks into the current generation Metasys system. The NIEx9 provides the same Site Management Portal UI as the NAE or NIE. Several models are available: NIE29, NIE39, NIE49, NIE59, and NIE89. The NIE29, NIE39, and NIE49 engines were retired at Metasys system Release 9.0.7.

SCT: You can use the System Configuration Tool in all phases of engineering, installing, and commissioning of devices that make up the Metasys system. You can use the SCT offline to create archive databases that can be downloaded to an Engine or Server. You can also use the SCT to upload and archive databases that were created or edited online from an Engine or Server. With the SCT, you can view and configure multiple sites in one archive.

SCT no longer requires the Site Director to be of an equivalent release version as the tool. You can use the SCT also to maintain a variety of engines from Release 5.2 and later. The Site Director must now be at an equivalent or greater release version than the highest versioned engine. For example, if you have a 10.1 engine and an 8.0 engine in the archive, the Site Director needs to be at Release 10.1 or later.

The SCT has the same look and feel as the Engine and Server Site Management Portal.

Metasys system configuration requires that you define a single device as the Site Director. The Site Director device may be a network engine or server, and its primary role is to coordinate multiple-user access from the web browser to the network. If a Metasys server exists in the system, it is defined as the Site Director automatically. When communicating directly to Metasys servers or network engines, you are in the online mode.

Note: In order to use HTTPS communications between Metasys Site Management Portal (SMP) and SCT, you must have SCT Release 11.1 or later, SMP Release 8.1 or later, and the latest version of Launcher installed.