Metasys System Configuration Guide: Building Technologies & Solutions 2021-01-12 LIT-12011832 Release 11.0

Metasys System Configuration Guide
Building Technologies & Solutions LIT-12011832

www.johnsoncontrols.com
2021-01-12 Release 11.0
2 Metasys System Configuration Guide
Contents
Metasys System Configuration Guide introduction................................................................................... 7
Contents
Summary of changes.......................................................................................................................... 7
Metasys system.............................................................................................................................................. 8
Equipment Controllers........................................................................................................................ 9
CG/CV Equipment Controller family........................................................................................................ 9
Advanced Application Field Equipment Controller (FAC).................................................................... 11
Field Equipment Controllers (FEC)......................................................................................................... 11
FEC Field Equipment Controller family comparison............................................................................ 12
VMA VAV Modular Assembly Series....................................................................................................... 12
Expansion input and output (I/O) modules......................................................................................... 13
Wireless solutions.................................................................................................................................... 14
Controller Configuration Tool (CCT)................................................................................................ 15
TEC3x00 Series Networked Thermostat Controllers..................................................................... 16
Network Engines............................................................................................................................... 16
SNE Series Network Engines.................................................................................................................. 18
SNC Series Network Control Engines.................................................................................................... 21
NAE............................................................................................................................................................ 24
NCE............................................................................................................................................................. 25
Network Engine Comparison................................................................................................................. 25
Servers................................................................................................................................................ 27
ADS and ADS-Lite..................................................................................................................................... 27
Server comparison................................................................................................................................... 28
ADX............................................................................................................................................................. 29
OAS............................................................................................................................................................ 31
ODS............................................................................................................................................................ 32
LCS............................................................................................................................................................. 33
User Interface.................................................................................................................................... 33
Tools.................................................................................................................................................... 34
Launcher................................................................................................................................................... 34
System Configuration Tool (SCT)........................................................................................................... 34
System Configuration Tool Pro (SCT Pro)............................................................................................. 36
Metasys Database Manager................................................................................................................... 37
VMD Generator Express (VGE Tool)....................................................................................................... 37
NIEx9 Driver Manager Tool..................................................................................................................... 37
Metasys system capabilities............................................................................................................. 37
Site Director.............................................................................................................................................. 37
Time management................................................................................................................................... 37
System navigation.................................................................................................................................... 38
Monitoring and commanding................................................................................................................ 38
Preferences............................................................................................................................................... 38
Alarm and event management.............................................................................................................. 39
Encrypted communication...................................................................................................................... 39
Metasys System Configuration Guide 3

Destination Delivery Agents (DDA)........................................................................................................ 40
Syslog DDA................................................................................................................................................ 41
Encrypted email........................................................................................................................................ 41
Scheduling................................................................................................................................................ 41
Historical Data Management (Trend).................................................................................................... 41
System security........................................................................................................................................ 42
Logic Connector Tool (LCT)..................................................................................................................... 44
Interlock object........................................................................................................................................ 44
Optimal Start............................................................................................................................................ 44
Demand Limiting and Load Rolling....................................................................................................... 45
Audit Trails (Transaction Data Management)...................................................................................... 45
System diagnostics and serviceability................................................................................................... 45
Metasys for Validated Environments..................................................................................................... 45
UL 864 10th Edition UUKL and ORD-C100-13UUKLC Smoke Control Listing.................................... 46
Federal Information Processing Standard (FIPS) 140-2 Level 1 compliance.................................... 47
Active Directory Federation Service (ADFS) two-factor authentication............................................. 47
Reporting capabilities....................................................................................................................... 48
Metasys Export Utility Software............................................................................................................. 48
Metasys Advanced Reporting System................................................................................................... 48
Energy Essentials..................................................................................................................................... 48
Metasys graphics options................................................................................................................. 48
Metasys UI Graphics................................................................................................................................ 48
Standard Graphics................................................................................................................................... 49
Integrations........................................................................................................................................ 50
BACnet/IP integration............................................................................................................................. 50
MS/TP communications bus................................................................................................................... 50
N2 field bus............................................................................................................................................... 50
N1 integration (Release 9.0 or earlier).................................................................................................. 50
LonWorks.................................................................................................................................................. 50
Modbus..................................................................................................................................................... 50
M-Bus......................................................................................................................................................... 51
KNX............................................................................................................................................................ 51
C CURE 9000 Access Control................................................................................................................... 51
victor Video Management....................................................................................................................... 51
Simplex Fire system................................................................................................................................. 51
Cree and Molex lighting systems........................................................................................................... 51
Zettler Fire Panels.................................................................................................................................... 51
OPC Unified Architecture (UA)............................................................................................................... 52
Metasys system revision compatibility overview........................................................................... 52
General compatibility information for customer job sites................................................................. 52
Compatibility rules for CCT and field controller revisions.................................................................. 52
Output Controller module upgrades..................................................................................................... 53
Working with SCT Release 11.x or later at Metasys Release 8.x and later........................................ 54
Equipment controller wireless integrations......................................................................................... 54

WNC1800/ZFR182x Pro Series Wireless Field Bus System.................................................................. 54
LCS85 compatibility.................................................................................................................................. 54
Metasys system configuration examples....................................................................................... 54
Multiple network engine system configuration with one network engine designated
as the Site Director................................................................................................................................... 54
Open Application Server (OAS) system configuration........................................................................ 55
Metasys Server Site Director with multiple network engines system configuration....................... 56
Metasys Server Site Director and secure NAE-S with unencrypted NAEs......................................... 56
ADX unified or split configuration......................................................................................................... 57
Unified and split ADX with dual network cards.................................................................................... 59
Large ADX site configuration.................................................................................................................. 60
ODS workstation configurations............................................................................................................ 60
BACnet/IP network system configuration............................................................................................ 62
Third-party network integration............................................................................................................ 63
Wireless Metasys system configurations.............................................................................................. 64
Smoke Control application configuration............................................................................................. 64
Performance guidelines and limitations........................................................................................ 65
Advanced Security Enabled attribute.................................................................................................... 65
Site Director limitations and recommendations.................................................................................. 65
Network engine hardware limitations.................................................................................................. 69
Alarm and trending performance guidelines....................................................................................... 71
MS/TP performance guidelines.............................................................................................................. 71
SCT limitations.......................................................................................................................................... 72
Equipment controller integration considerations............................................................................... 72
Transfer to device (download) limitations............................................................................................ 73
Technical specifications and requirements.............................................................................................. 74
Hardware configuration requirements........................................................................................... 74
Client computer requirements for UI client devices..................................................................... 75
Application and Data Server (ADS) system requirements............................................................ 78
Extended Application and Data Server system requirements (Unified 10 or 25
User ADX).................................................................................................................................. 80
Extended Application and Data Server system requirements (Split 10 or 25 User
ADX)........................................................................................................................................... 84
Extended Application and Data Server system requirements (Unified 50 or 100
User ADX).................................................................................................................................. 88
Extended Application and Data Server system requirements (Split 50 or 100 User
ADX)........................................................................................................................................... 92
OAS technical specifications............................................................................................................. 97
Application and Data Server-Lite system requirements............................................................. 101
SCT Technical Specifications........................................................................................................... 103
CCT technical specifications........................................................................................................... 105
SNC technical specifications........................................................................................................... 106
SNE technical specifications........................................................................................................... 110
LCS85 technical specifications....................................................................................................... 112

Technical specifications - NCE25, NAE35, and NAE45 models.................................................... 114
Technical specifications.................................................................................................................. 118
Metasys system related documentation................................................................................................. 121
Product warranty....................................................................................................................................... 124
Software terms........................................................................................................................................... 124
Patents......................................................................................................................................................... 125
Contact information................................................................................................................................... 125

Metasys System Configuration Guide introduction
This document introduces the components and capabilities of the Metasys system. It also describes
how the system operates and provides an overview of the various configurations.
For a list of Metasys system related documentation, see Table 50 at the end of this document.
Summary of changes
The following information is new or revised:
• Added information about OPC Unified Architecture (UA), a new integration at Release 11.0.
• Added information about Federal Information Processing Standard (FIPS) 140-2 Level 1
compliance, a new feature at Release 11.0.
• Added information about Active Directory Federation Service (ADFS) two-factor authentication,
a new feature at Release 11.0.
• Updated information about CG/CV Equipment Controller family.
• Updated information about SNE Series Network Engines and SNC Series Network Control
Engines.
• Updated Server comparison and OAS to reflect Release feature updates.
• Updated Metasys UI Release feature updates.
• Updated CCT Release feature updates.
• Updated SCT and SCT Pro Release feature updates.
• Updated Technical Specifications.
- Added support for Windows Server 2019, SQL Server 2019 Express, and SQL Server 2019.
- Updated information about Windows Server 2016, SQL Server 2017 Express, SQL Server
2017, SQL Server 2016 Express, SQL Server 2016, SQL Server 2014 Express, and SQL Server
2014.
- Removed support for Windows Server 2012, Windows Server 2012 R2, SQL Server 2012
Express, and SQL Server 2012.
• Updated Network engine hardware limitations and Alarm and trending performance
guidelines to include information about OAS.
• Updated Related Documentation.
• Removed references to Remote Authentication Dial-In User Service (RADIUS), because this is
no longer supported at Release 11.0.
• Removed references to Advanced Graphics Application, because the purchase of the Advanced
Graphics Application for new sites (MS-ADVGRF-0) and for upgrading sites (MS-ADVGRF-6) is
no longer allowed.
• Removed references to Graphics+, because the purchase of Graphics+ Generation Tool for new
sites (MS-GGT-0) is no longer allowed, and the ability to save Graphics+ graphics directly to the
Server is not supported at 11.0.
• Metasys supports ODS at Release 10.1, but it is not upgradable to Release 11.0.

Metasys system
The Metasys system is a network-based building automation system that operates multiple pieces
of mechanical and electrical equipment found in commercial buildings. The system consists of a
wide variety of hardware and software components. You can apply these components in several
configurations to meet the scale and scope of the customer's building automation needs. This
guide describes the capabilities of each Metasys component, as well as the capabilities of the entire
system. This guide also lists examples of how you can integrate and apply the various Metasys
components to create specific building automation system configurations.
A Metasys site comprises one or more Metasys devices on a continuously connected IP network.
A site’s primary network consists of one or more engines. The engines also provide the Site
Management Portal UI. You can configure the primary network and monitor the users of all
devices on the network with the Site Management Portal UI. The engine types are SNE Series of
Network Engines, which succeed the Network Automation Engines (NAEs); Network Integration
Engines (NIEs); SNC Series of Network Control Engines, which succeed the Network Control Engines
(NCEs); or LonWorks® Control Servers (LCSs). These engines are described in further detail in this
document.
A site can optionally have one or more Metasys servers—computer-based devices that add long-
term data storage and support for larger Metasys networks. Metasys server products include
Application and Data Servers (ADS), ADS-Lite (available only in specific markets), Extended
Application and Data Servers (ADX), Open Application Server (OAS), and BACnet® Open Data
Servers (ODS), which are described in further detail in this document. Metasys servers provide the
same Site Management Portal UI as the engines. Additionally, the Metasys UI is installed with the
Metasys server software, with the exception of ODS, which does not include the Metasys UI. The
latest available version of the ODS is Release 10.1. The ODS is not available for upgrade to Metasys
Release 11.0.
Each Metasys site has one device (engine or server) that is designated as the Site Director. Typically,
the Site Director is the single point of access for all Site Management Portal UI users because the
Site Director includes a view of all Metasys devices on the site. If a server is connected to a site, you
must designate the server as the Site Director. For more information, see Site Director.
Figure 1 shows an example Metasys system configuration. The Metasys system configuration
examples section shows a variety of configuration examples.
Figure 1: Example Metasys System Configuration

Equipment Controllers
Metasys includes several model series of equipment controllers, including General Purpose
Application Controllers (CGMs), VAV Box Controllers (CVMs), Advanced Application Field Equipment
Controllers (FACs), Field Equipment Controllers (FECs), Variable Air Volume Modular Assembly
(VMAs), and Input/Output Modules (IOMs). These devices provide direct, operational control over
HVAC and other mechanical and electrical equipment and are typically networked together and
supervised by network engines. The BACnet® family of controllers is tested by an independent
BACnet Testing Lab. A complete listing of the tested Johnson Controls® BACnet devices is available
at the following link: http://www.bacnetinternational.net/btl/index.php?m=15
CG/CV Equipment Controller family

The CG/CV equipment controller family was first introduced at Metasys 10.0. At Release 11.0, we are
expanding this next-generation equipment controller family to include another general purpose
application equipment controller model, a VAV Box Controller model with position feedback,
and three new I/O expansion modules. This next-generation of equipment controllers feature
modernized packaging and styling, removable screw terminal blocks, three rotary dial switches for
setting the MS/TP address, background file transfer, and more.
Additionally, new features introduced at Release 11.0 include factory-loaded, field-selectable
applications in CVM controllers offering an alternative streamlined configuration workflow; a
generic SA Bus object to enable a more nimble integration of approved BACnet MS/TP end devices
on the SA Bus; SA Bus provisioning to streamline upgrade workflows; and support for BACnet
Protocol Revision 18 for interoperability with third-party BACnet devices.
For more information about CG/CV equipment controller family features and benefits refer to
Metasys CG, CV Equipment Controllers and XPM Expansion Modules Product Bulletin (LIT-12013105).
Figure 2: General Purpose Application Controllers (CGM) and VAV Box Controllers (CVM)

Table 1: CGM and CVM controllers details
M4-CGM04060-0 M4-CGM09090-0 M4-CVM03050-0 M4-CVM03050-0P
Description General Purpose General Purpose VAV Box Controller VAV Box Controller with
Application Controller Application Controller position feedback
Inputs and Outputs 10 total: 18 total: 8 total: 8 total:
• 3 Universal Inputs • 7 UIs • 3 UIs • 3 UIs
(UIs) • 2 BIs • 2 COs • 2 COs
• 1 Binary Input (BI) • 4 COs • 3 BOs • 3 BOs
• 4 Configurable • 3 BOs • Integral actuator • Integral actuator
Outputs (COs) • 2 Analog Outputs • Integral DPT • Integral DPT
• 2 Binary Outputs (AOs) • Integral
(BO) potentiometer
to sense actual
VAV box damper
position
Expandable through Yes
SA Bus
Onboard Real Time Yes
Clock
Communication • FC Bus (BACnet MS/TP)
Protocols • N2 (software switchable)
• Zigbee for ZFR Pro Wireless Field Bus (add on modules)
Figure 3: Expansion I/O modules
Table 2: New expansion I/O modules

Model number M4-XPM04060-0 M4-XPM09090-0 M4-XPM18000-0
Description Expansion I/O module
Inputs and Outputs 10 total: 18 total: 18 BIs
• 3 UIs • 7 UIs
• 1 BI • 2 BIs
• 4 COs • 4 COs
• 2 BOs • 3 BOs
• 2 AOs
Field Bus Networking • FC Bus (BACnet MS/TP)
• SA Bus

Advanced Application Field Equipment Controller (FAC)
FAC Series Controllers support selectable BACnet or N2 field bus networking protocols. FAC Series
Controllers feature an integral real-time clock and support time-based tasks, which lets these
field controllers monitor and control schedules, calendars, alarms, and trends. FACs can continue
time-based control and monitoring when offline for extended periods of time from a Metasys
system network. FAC Series Controllers can also operate as stand-alone controllers in applications
that do not require a network engine or for network applications where it is preferred to have
the scheduling, alarming, and trending performed locally in the field controllers. The FAC2612
controller features line-voltage relay outputs, making this controller well suited for use in terminal
units. The FAC2612-2 model uses a line-voltage power supply, eliminating the need for a 24 VAC
transformer in line-voltage applications. A full range of FAC and FEC models combined with IOM
models can apply to a wide variety of mechanical and electrical equipment control applications
ranging from simple fan coil or heat pump control to advanced central plant management.
The FAC3611-0 and FAC3613-0 models include a fast persistence feature that facilitates data values
to be held at a configurable value, up to once per second. Persistence refers to how often samples
of data are stored locally. The fast persistence feature ensures that in the event of a problem,
such as a loss of power, you can retrieve up to the rate that the data is persisted, minimizing
the potential loss of data. When power is restored, previously persisted data, up to the rate of
persistence, is still available and accessible. In the case of persistence configured for once per
second, you risk losing only one second of data. Persisting data is essential for situations that
require greater data accuracy and may include certain methods of utility data collection and billing.
Attributes you can persist in the FAC3611-0 and FAC3613-0 include Counter Input Present Value
Attributes, Binary Input, Binary Output, Binary Value COS Counts, Active Time Attributes, and PID/
PRAC tuning parameters.
Some controller models operate on BACnet/IP networks and integrate into Johnson Controls'
and third-party systems. For example, the FAC4911 BACnet/IP model is BTL-listed as an Advanced
Application Controller. This model has an integral real-time clock for scheduling, alarming and
trending, and facilitates star and daisy chain network wiring topologies. Starting at Release 10.0,
Media Redundancy Protocol (MRP) ring-enabled support is available for the Metasys IP FAC4911
and IP VMA1930 controllers, which are connected by Cisco® technology. The controllers can be
configured in a ring network and continue to communicate even if one controller or network
segment within the ring network stops communicating. This provides network reliability by
mitigating a single point of failure in the IP/Ethernet network wiring.
Field Equipment Controllers (FEC)

FEC Series products support selectable BACnet or N2 field bus networking protocols. The FEC
family includes multiple models featuring a variety of total number and types of input and output
interfaces. FECs feature 32-bit microprocessor architecture, patented continuous tuning adaptive
control, and peer-to-peer communications, and they are available with an optional built-in LCD
screen local UI. A full range of FEC models combined with IOM models can apply to a wide variety
of mechanical and electrical equipment control applications ranging from simple fan coil or heat
pump control to advanced central plant management. The FEC Series controllers support wireless
communications using the ZigBee® Field Router (ZFR) Series accessories.

FEC Field Equipment Controller family comparison
Table 3: Field Equipment Controller family comparison
Advanced Application Variable Air
Field Equipment
Field Equipment Volume Modular
Controllers (FECs)
Controllers (FACs) Assemblies (VMAs)
Typical applications Controlling: Controlling: Controlling:
• Pressure
• Rooftop Units • Equipment that requires
independent
• Heat Pumps local scheduling,
VAV boxes
alarming, and trending
• Unit Ventilators • Pressure
• Air Handling Equipment
• Air Handling dependent VAV
Equipment • Central Plant Equipment boxes
• Central Plant • Zone Dampers
Equipment
• Exhaust Fans
• Supplemental
Heating
Equipment
Processor 32-bit 32-bit 32-bit
Onboard real time No Yes Yes - on IP VMA1930
clock model only
Communication • BACnet MS/ • BACnet MS/TP (B-AAC) • BACnet MS/
protocol TP (B-ASC) or N2 (field switchable) TP (B-ASC)
or N2 (field • BACnet/IP (B-AAC) or N2 (field
switchable) (model IP FAC4911 only) switchable)
• ZigBee Wireless • ZigBee Wireless (with an • BACnet/IP (B-
(with an add-on add-on module) AAC): (model IP
module) VMA1930 only)
• ZigBee Wireless
(with an add-on
module)
Expandable through Yes Yes Yes
SA bus
Programmable Yes Yes Yes
control logic
Programming tool CCT CCT CCT
Commissioning tool CCT, MAP CCT, MAP CCT, MAP
VMA VAV Modular Assembly Series

VMA16 (16-bit) VAV Modular Assembly
VMA16 (16-bit) VAV Modular Assembly controllers are programmable BACnet application specific
controllers with RS-485 MS/TP communications. VMA controllers feature an integral 4 N•m damper
actuator and Differential Pressure Transducer (DPT) with models for cooling only or cooling
with reheat applications and fan control. The differential pressure sensor in the VMA16 (16-bit)
controllers provides consistent flow readings with minimal drift and requires minimal auto-zero

calibration. There are no filters to change, which helps to ensure very close tolerance to published
accuracy. The VMA16 (16-bit) controllers can be configured for single-duct, dual-duct, and supply/
exhaust applications. Note that some of these applications may require an additional actuator
and DPT. VMA16 (16-bit) controllers support NS and WRZ Series Communicating Network Sensors
for temperature sensing, fan override, and occupancy override control. The VMA16 (16-bit) Series
Controllers support wireless communications using the ZFR Series accessories.
VMA16 (32-bit) controllers are programmable digital controllers tailored for VAV box applications
that can be switched between BACnet MS/TP and N2 Communications protocols. When they are
used as MS/TP devices, they communicate via the BACnet MS/TP protocol. In N2 mode, they can be
used to modernize sites with legacy Johnson Controls controllers.
The VMA16 (32-bit) controllers feature an integral digital pressure sensor, an integral damper
actuator, and a 32-bit microprocessor. The controllers' small package size facilitates quick field
installation and efficient use of space, while not compromising high-tech control performance.
VMA models are available without the integral differential pressure sensor, making them a more
affordable choice for commercial zoning or pressure-dependent VAV box control applications.
VMA16 models are also available without the integral actuator, allowing a separate actuator to be
used for VAV box control applications where a higher torque actuator or an actuator with position
feedback would be more appropriate. The VMA16 (32-bit) controllers connect easily to the NS
Series Network Sensors for zone and discharge air temperature sensing. These features make
the VMA16 (32-bit) the product of choice for VAV box control. The wide variety of network sensor
models provides options for measuring and displaying zone temperature, occupancy detection,
duct temperature, zone humidity, carbon dioxide (CO2) level, setpoint adjustments, VAV box fan
speed, and discharge air temperatures.
VMA18 controllers are very similar to the VMA16 (32-bit) programmable VAV box controllers,
but include additional features that make them well-suited for replacing legacy VMA1400 Series
controllers. VMA18 controllers have an 8-pin TSTAT port intended for use with the TE-7xxx Series
non-communicating sensors. The VMA18 controllers also include cable adapters to provide options
for reusing or replacing the sensor formerly used with the VMA14xx Series.
VMA1930 VAV Modular Assembly
The IP VMA1930 models operate on BACnet/IP networks and integrate into Johnson Controls'
and third-party systems. The IP VMA1930 has an integral actuator, integral DPT, and eight I/O
points. The IP VMA1930 is BTL-listed as an Advanced Application Controller, has a real-time clock
for scheduling, alarming and trending, and facilitates star or daisy chain network wiring topologies.
Starting at Release 10.0, Media Redundancy Protocol (MRP) ring-enabled support is available for
the Metasys IP VMA1930 and IP FAC4911 controllers, which are connected by Cisco® technology. The
controllers can be configured in a ring network and continue to communicate even if one controller
or network segment within the ring network stops communicating. This provides network reliability
by mitigating a single point of failure in the IP/Ethernet network wiring.
Expansion input and output (I/O) modules

IOM controllers
The IOM controllers are expansion input and output modules with integral RS-485 MS/TP
communications. IOMs can serve in one of two capacities, depending on where they are installed in
the Metasys system. When installed on the SA Bus of a CGM, CVM, FAC, FEC, or VMA controller, the
IOMs expand the point count of these controllers. When installed on the FC Bus, the IOMs support
monitoring and control from an NAE or NCE as I/O point multiplexors. The point multiplexor can
also be useful for sharing points between other field controllers on the FC Bus using peer-to-
peer connectivity. A full range of CGM, CVM, FAC, FEC and VMA models combined with the IOM

models can be applied to a wide variety of mechanical and electrical equipment control applications
ranging from simple fan coil or heat pump control to advanced central plant management.
M4-XPM series expansion I/O modules
The M4-XPM series input/output (I/O) expansion modules are part of the Metasys system CG,
CV Equipment Controller family and can serve in one of two capacities depending on where they
are installed in the Metasys system. When installed on the Sensor/Actuator (SA) Bus of a Metasys
equipment controller, an XPM expands the input and output interfaces that can be used with
that equipment controller. When installed on the Field Controller (FC) Bus of a Metasys network
engine, an XPM can be used as I/O point multiplexors to support monitoring and control from a
Metasys network engine. The point multiplexor can also be useful for sharing points between other
equipment controllers on the FC Bus using peer-to-peer connectivity.
XPMs operate on an RS-485 BACnet MS/TP Bus and are BACnet Testing Laboratory (BTL) listed and
certified to the BACnet Smart Actuator (B-SA) profile.
Compatibility:
XPM series expansion modules can be connected to the SA Bus of the following equipment
controller device types:
• CG series General Purpose Application Equipment Controllers

• CV series VAV Box Controllers
• FAC series Advanced Application Field Equipment Controllers
• FEC series Field Equipment Controllers
• VMA16, VMA18, and VMA19 series VAV Box Controllers
• SNC series Network Control Engines
• NCE series Network Control Engines
Note: XPM series expansion modules may coexist on the SA Bus with IOM series input/output
expansion modules.
XPM series expansion modules can be connected to the FC bus of the following network engine
types:
• SNE series Network Engines

• SNC series Network Control Engines
• NAE35, NIE39, NAE45, NAE49, NAE55, and NAE59 series Network Automation and Integration
Engines
• NCE25 and NIE29 series Network Control Engines
Note: XPM series modules may coexist on the FC Bus with IOM series input/output expansion
modules.
For more information about the M4-XPM series, refer to the M4-XPM Expansion Modules Catalog
Page (LIT-1901145).
Wireless solutions
Several wireless Metasys solutions are available for integrating wireless connectivity in desired
portions of a Metasys network. These solutions provide wireless communication between
controllers, thermostat controllers, coordinators, routers, and room sensors.
• ZFR181x Series Wireless Field Bus System

• WNC1800/ZFR182x Pro Series Wireless Field Bus with Wireless TEC3000 Series Thermostats
• WRS Series Many-to-One Wireless Room Temperature Sensing System
• WRZ-7860 One-to-One Wireless Room Temperature Sensing System
• TE-7800 Series One-to-One Wireless Room Temperature Sensing System
These wireless solutions reduce costs by minimizing wiring, provide application mobility and
flexibility, and simplify the challenges of difficult or cost-prohibitive installations or renovations. The
wireless solutions can coexist with each other, and with hard-wired Metasys solutions.
Controller Configuration Tool (CCT)

You can use the Controller Configuration Tool (CCT) to configure, simulate, commission, and
transfer application files to the following:
• Advanced Application Field Equipment Controllers (FACs)

• Advanced Application Programmable Controllers (PCAs)
• Expansion Input/Output Modules (PCXs)
• Field Equipment Controllers (FECs)
• General Purpose Application Controllers (CGMs)
• General Purpose Programmable Controllers (PCGs)
• Input/Output Modules (IOMs)
• Programmable Variable Air Volume Box Controllers (PCVs)
• SNC Series Controllers
• Variable Air Volume Controllers (VAVs)
• Variable Air Volume Modular Assembly Controllers (VMAs)
• Variable Air Volume Terminal Equipment Controllers (CVMs)
• Expansion Modules (XPMs)
CCT operates in the following three modes that provide key functionality for your system:
• Use the Configuration mode to select mechanical and control logic options for typical air
handling, terminal unit, central plant, and VAV box mechanical systems. You can customize the
standard logic provided by the system selection process to meet your specialized control logic
requirements.
• Use the Simulation mode to review the application logic as if you were commissioning the
system. You can make adjustments to setpoints, inputs, or sensors during a simulation session
to validate the logic before assigning the configuration to a specific controller. A simulation
debugging console is also available to setup break points that pause the simulation session
based on criteria that you set up. While viewing a simulation session, transitions taking place
in the logic are highlighted for a few seconds to help you quickly identify where the changes
occur.
• Use the Commissioning mode to connect to a device and view actual data from that device.
You can use this mode to monitor your device and set offsets, COVs, and polarity in addition to
other parameter and detail changes.
For VAV applications, CCT includes an optional box flow test to automatically exercise all the VAV
boxes to ensure correct mechanical installation and correct configuration of the key flow setup
parameters.

The ZFR Checkout Tool (ZCT) is available to validate the wireless connectivity and health of your
wireless mesh network. Refer to the ZFR Checkout Tool Help (LIT-12012292) for details.
Controller Application Files (CAFs) can be transferred and commissioned to a device through a wide
variety of connection interfaces including: NxE Passthru, MAP 4.2+ / BACnet® router, ZigBee® and
Direct Ethernet.
For information about upgrading or installing CCT, refer to the CCT Installation Instructions
(LIT-12011529).
For a list of updated features and benefits available at CCT Release 14.0, refer to the Controller
Configuration Tool (CCT) Catalog Page (LIT-1900386).
TEC3x00 Series Networked Thermostat Controllers

The TEC3x00 Series Thermostat Controllers are configurable, application-specific controllers with
embedded sensors. TEC3x00s are housed in enclosures suitable for mounting on a wall in an
occupied space, and each model features an intuitive user interface with backlit display that makes
setup and operation quick and easy.
Depending on the model and configuration options you select, TEC3x00s provide on/off, floating,
and proportional control of:
• local hydronic reheat valves

• pressure-dependent VAV equipment with or without local reheat
• two- or four-pipe fan coils
• cabinet unit heaters
• other zoning equipment using an on/off, floating, or 0 to 10 VDC proportional control input
• single- or two-stage unitary rooftop units (RTUs) and heat pumps, with or without economizers
The TEC3600 series models feature field-selectable BACnet MS/TP or N2 communication capability,
enabling supervisory control from a Metasys network engine or communication to third-party
BAS devices. The TEC3000 series models feature ZFRPro compatible wireless communication
capabilities, enabling supervisory control from a Metasys network engine through a Wireless
Network coordinator.
Network Engines
Network engines perform a key role in the Metasys system architecture. These network engines
provide network management and system-wide control coordination over one or more networks of
equipment controllers, including the following Metasys field controllers:
• General Purpose Application MS/TP Controllers (CGMs)
• VAV Box Equipment MS/TP Controllers (CVMs)

• Field Equipment Controllers (FECs) and Advanced Application Field Equipment Controllers
(FACs)
• Variable Air Volume Modular Assembly (VMA) Controllers
• Terminal Equipment Controllers (TECs)
• LN series equipment controllers
• Legacy Metasys controllers, such as Unitary (UNT) controllers, Variable Air Volume Assembly
(VMA14xx) controllers, and DX-9100 controllers
• Third-party equipment controllers
The network engines can be networked together for scaling up on large projects, and they can be
networked with an ADS, ADX, or OAS for additional functionality and site unification.
Network engines provide building control scheduling, alarm and event management, energy
management, data exchange, historical data storage and management, and custom control
logic. Network engines include an embedded user interface called the Site Management Portal
(SMP). Users access the SMP for system navigation and operation using web browser connections.
Network engines are secured from unauthorized access using password protection and permission
access control as well as IT security best practices.
In addition to providing general comprehensive equipment monitoring and control, network
engines also offer specialized capabilities by series, model, and software release to meet a variety
of application requirements. The network engines are identified by three types:
Small-capacity engines
• Network Automation Engines: NAE35 and NAE45

• SNE Series of Network Engines: SNE1050x and SNE1100x
Note: The SNE1050x model succeeds the NAE35 model and the SNE1100x model succeeds
the NAE45 model of engines.
• Network Control Engine: NCE25
• SNC Series of Network Control Engines: SNC25150-0, SNC25151-0, SNC25151-0H, SNC16120-0,
SNC16121-0, SNC16121-0H
Note: The SNC models succeed the NCE25 models of engines.
Large-capacity engines
• Network Automation Engine: NAE55

• SNE Series of Network Engines: SNE2200x
Note: The SNE2200x succeeds the NAE55 model of engines.
Software-only engines
• Network Automation Engine: NAE85
NAEs provide network supervisor capabilities and IP network connectivity. NCEs also provide
network supervisor capabilities and IP network connectivity, but also feature the I/O point
connectivity and direct digital control capabilities of an FEC. NIEs are variants of NAEs and NCEs that
include legacy and third-party device integration capabilities.

SNE Series Network Engines
At Release 11.0, we are introducing updated SNE series network engine models, which feature an
updated main circuit board with improved design configured for future capabilities.
Also starting at Release 11.0, SNE models are FIPS 140-2 Level 1 certified. FIPS 140-2 is a U.S.
government cyber security standard used to approve cryptographic modules and algorithms used
for encryption. FIPS 140-2 is included by default in SNEs that have Release 11.0 software.
Figure 4: SNE series network engines
The following table outlines the SNE models in more detail.
Table 4: SNE series network engine details

Features SNE22000 SNE11000 SNE10500 SNE110L0
SNE22001 SNE11001 SNE10501 SNE110L1
1
1
Succeeds NAE55 Series NAE45 Series NAE35 Series NAE45-Lite
Communication • 1 Ethernet port • 1 Ethernet port
interfaces • 2 RS-485 ports • 1 RS-485 port
2 2
• 2 USB ports • 2 USB ports
2
Maximum allowed 600 150 60 110
devices across all
integrations. For
example, MS/TP
+IP. Includes VND
integrations and
devices brought in
through routers.
BACnet/IP 1 1 1 1
maximum trunks
BACnet/IP 200 100 50 10
maximum devices
per trunk
BACnet MS/TP 2 1 1 1
maximum trunks
BACnet MS/TP 100 100 50 100
maximum devices
per trunk

SNE22001 SNE11001 SNE10501 SNE110L1
1
1
maximum devices
per trunk (with 3rd
party)
N2 maximum 2 1 1 N/A
trunks
Mapped N2 devices 100 100 50 N/A
per trunk
LonWorks 1 1 1 0
maximum trunks
LonWorks 255 127 127 0
maximum devices
Remote Field Bus 6 3 3 N/A
maximum trunks
maximum Johnson
Controls Devices
per bus
maximum devices
per bus (with 3rd
party devices)
Maximum objects 5000 2500 2500 2500
in device
3
3
Supported type of • ADS • ADS • ADS ADS-Lite-A only
parent server • ADX • ADX • ADX
• OAS • ADS-Lite-E • ADS-Lite-E
• OAS • OAS

SNE22001 SNE11001 SNE10501 SNE110L1
1
1
Supported • BACnet/IP
integrations - Simplex® Fire Alarm Control Unit (FACU)
- Cree® SmartCast® Lighting Control
- Molex® Lighting Control
• BACnet MS/TP Field Controller (FC) Bus

• N2 Bus
Note: The M4-SNE110Lx-0 model does not support the N2 Bus.
• LonWorks® (requires USB to LON adapter)
Note: The M4-SNE110Lx-0 model does not support the LonWorks
network interface.
• Modbus: Modbus TCP/IP on Ethernet and Modbus Remote Terminal
Unit on RS-485
• KNX IP
• M-Bus
• Tyco® C•CURE® 9000 and victor® Video Management
• Zettler® Fire Panel
• OPC Unified Architecture (UA)
Operating System Wind River® Linux LTS 17 (LTS=long-term support)
Microprocessor NXP i.MX6 DualLite processor
Memory Flash 2GB of DDR3 RAM and 16 GB of eMMC Flash
User Interface Site Management Portal (SMP)
1 These models are intended for use with the ADS-Lite-A servers (only) in Australia, China, Hong Kong, India, Indonesia,
Japan, Korea, Malaysia, New Zealand, Philippines, Singapore, Taiwan, Thailand, Vietnam, and select branches within
regions of Africa and the Middle East.
2 Only the supported USB integration adapters function with the SNE. Other integration adapters that are not supported
cannot function with the SNE.
3 Suggested object limit for performance considerations.
The SNE models introduced at Release 11.0 are direct replacements of the models launched at
Release 10.1. The following table outlines this in more detail.

Table 5: New SNE models
Model number Succeeds Directly replaces
M4-SNE10501-0 MS-NAE3510-2 M4-SNE10500-0
MS-NAE3514-2
1
MS-NAE3520-2
1
MS-NIE3910-2
M4-SNE11001-0 MS-NAE4510-2 M4-SNE11000-0
1
MS-NAE4520-2
MS-NIE4910-2
M4-SNE110L1-0
2
MS-NAE451L-2
2
M4-SNE110L0-0
2
M4-SNE22001-0 MS-NAE5510-3 M4-SNE22000-0
1
MS-NAE5520-3
MS-NAE5960-3
1 Also requires USB-to-LON Adapter (ACC-USBLON-0).
2 SNE110L and NAE451L are restricted to select global regions.
SNC Series Network Control Engines

The Metasys SNC series network control engine is a hybrid offering that provides both supervisory
and equipment control in a unified offering. They provide network management and system-wide
control coordination over one or more networks of equipment controllers, including the following
Metasys equipment controllers:
• CGM series general purpose application equipment controllers

• CVM series VAV box controllers
• FAC and FEC series field equipment controllers
• VMA series VAV box controllers
• TEC series terminal equipment controllers
• LN series equipment controllers
• Third-party equipment controllers
In addition to providing supervisory control capabilities, the SNC series network control engines
also feature onboard input and output interfaces (I/O) and programmable logic to provide direct
control over HVAC and other building system equipment.
Figure 5: SNC series network control engines

At Release 11.0, we are introducing new models of the SNC series network control engines, which
feature an onboard display and keypad. The 2.4 in. display with 320 x 240 resolution provides
local user interface capabilities. This provides end customers with the ability to quickly and clearly
monitor equipment status, view alarms, see trends, issue overrides, and change setpoints and
parameters.
In addition, we updated SNC models to include a second Ethernet port at Release 11.0. The updated
models contain two Ethernet ports that support daisy-chain IP networking topology. This provides
system designers with the installation flexibility and reduced installation costs of daisy-chain
network topology for IP controller installations.
Also starting at Release 11.0, SNC models are FIPS 140-2 Level 1 certified. FIPS 140-2 is a U.S.
government cyber security standard used to approve cryptographic modules and algorithms used
for encryption. FIPS 140-2 is included by default in SNCs that have Release 11.0 software.
The following table outlines the SNC models in more detail.
Table 6: SNC series Network Control Engines details

Features SNC25150-0 SNC25150-04 SNC16120-0 SNC16120-04
SNC25151-0 SNC25151-04 SNC16121-0 SNC16121-04
SNC25151-0H SNC25151-04H SNC16121-0H SNC16121-04H
Succeeds NCE25 Series NCE2500 NCE25 Series NCE2500
Onboard inputs and • 40 total onboard I/O: 14 UI, 11 • 28 total onboard I/O: 10 UI, 6 BI,
outputs BI, 4 CO, 4 AO, 7 BO 4 CO, 4 AO, 4 BO
• Supports SA Bus expansion • Supports SA Bus expansion
Communication • 1 Ethernet port: SNC25150-0, SNC25150-4, SNC16120-0, SNC16120-04
interfaces • 2 Ethernet port: SNC25151-0, SNC25151-0H, SNC25151-04,
SNC25151-04H, SNC16121-0, SNC16121-0H, SNC16121-04,
SNC16121-04H
• 1 RS-485 port
1
• 2 USB ports for connecting external integration adapters 1
Maximum allowed 96 4 60 4
devices across all
integrations. For
example, MS/TP
+IP. Includes VND
integrations and
devices brought in
through routers.
BACnet/IP 1 1 1 1
maximum trunks
BACnet/IP 50 4 50 4
maximum devices
per trunk
maximum trunks

SNC25151-0 SNC25151-04 SNC16121-0 SNC16121-04
maximum devices
per trunk
maximum devices
per trunk (with 3rd
party)
N2 maximum 1 1 1 1
trunks
Mapped N2 devices 50 4 50 4
per trunk
LON maximum 64 4 64 4
devices per trunk
LON maximum 1 1 1 1
trunks
Remote Field Bus 3 0 3 0
maximum trunks
2
2
maximum Johnson
Controls Devices
per bus
maximum devices
per bus (with 3rd
party devices)
Maximum objects 2500 2500 2500 2500
in device
3
3
Supported type of • ADS
parent server • ADX
• ADS-Lite-E
• OAS
• ODS

SNC25151-0 SNC25151-04 SNC16121-0 SNC16121-04
Supported • BACnet/IP
integration drivers - Simplex® Fire Alarm Control Unit (FACU)
- Cree® SmartCast® Lighting Control
- Molex® Lighting Control
• BACnet MS/TP
• N2 Bus
• LonWorks® (requires USB to LON adapter)
• Modbus: Modbus TCP/IP on Ethernet and Modbus Remote Terminal
Unit on RS-485
• KNX IP
• M-Bus
• Tyco® C•CURE® 9000 and victor® Video Management
• Zettler® Fire Panel
• OPC UA
Microprocessor NXP i.MX6 DualLite processor
Memory 2 GB of DDR3 RAM and 16 GB of eMMC Flash
User Interface Site Management Portal (SMP)
1 Only the supported USB integration adapters function with the SNC. Other integration adapters that are not supported
cannot function with the SNC.
2 The SNC requires Release 11.0 or higher to support the Remote Field Bus integration.
3 Suggested object limit for performance considerations.
Note: Servers must be equal to or at a higher Metasys Release than their child engines,
including the SNCs. The ODS can parent SNCs, but only if the SNCs are at Release 10.1, because
the latest available version of the ODS is Release 10.1.
NAE
The NAE is available in many different models with options to support various communications
protocols including BACnet over IP, BACnet® MS/TP, N2 Bus, N2 over Ethernet, and LonWorks®
protocol. Built-in support for third-party protocols, including Modbus, M-Bus, KNX, Tyco C•CURE
9000/victor, and OPC UA is also included. The following models are available:
• The NAE55 Series supports a comprehensive set of supervisory control features and functions
for large facilities and technically advanced buildings and complexes.
• The NAE-S (MS-NAE551S-x) is a secure NAE55 with increased security features—embedded
encryption technology under a securely fastened enclosure 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 NAE35 and NAE45 Series extend the power of the NAE to the smaller buildings (or small
areas of larger buildings) and enable the wider distribution of supervisory control functions in
larger facilities.

• The NAE45-Lite, available only in specific markets, is a functionally limited NAE45 that you
cannot use as a Site Director and functions only with a corresponding ADS-Lite.
Note: The NAE45-Lite engine does not support the Remote Field bus.
• The NAE85 supports large BACnet/IP integrations.
Note: Starting at Release 10.1, the SNE Series of Network Engines succeed the NAE Series
Network Engine family. For more information about the SNE see SNE Series Network Engines.
NCE
The NCE provides support for the same communications protocols as the NAE, but also offers
the Input/Output (I/O) point connectivity and direct digital control capabilities of a Metasys
Field Equipment Controller (FEC). The NCE provides a cost-effective solution designed for central
plants and large built-up air handler applications. All NCE models provide IP Ethernet network
connectivity, the Site Management Portal UI, and the network supervisory control functions
featured on network automation engines. Depending on the model and software release, an
NCE supports either a BACnet MS/TP Bus, an N2 Bus, or a LonWorks network trunk. The NCE also
provides built-in support for third-party protocols, including Modbus, M-Bus, and KNX.
Note: Starting at Release 10.1, the SNC Series Network Controllers succeed the NCE Series
of the Network Control Engine family. For more information about the SNC see SNC Series
Network Control Engines.
Network Engine Comparison

Table 7: Network Engine Release support comparison
Model Release 9.0 Release 9.0.7 Release 10.0 Release 10.1 Release 11.0
or 9.0.8 patch
NCE25 X X
1
Succeeded by SNC models, but
1
NCE25 continues to ship out of
factory at Release 9.0.7.
NAE35, NAE45 X X
2
The SNE1050x succeeds the
2
NAE35 series and the SNE1100x
succeeds the NAE45 series,
but NAE35 and NAE45 series
continue to ship out of factory
at Release 9.0.7.
NAE55 X X
3
X
4
X
5
3
4
5
NAE85 X X X X
NIE29, NIE39, X X
6
Discontinued Discontinued
6
NIE49
NIE59 X X X X
Important: All NIEx9 models have been
discontinued from manufacture, because
starting at 9.0.7 and 10.0, NAE models
include the integration functionality of the
NIE. Existing NIE59s can be field-upgraded
to 10.0, 10.1, and 11.0, respectively.

Table 7: Network Engine Release support comparison
Model Release 9.0 Release 9.0.7 Release 10.0 Release 10.1 Release 11.0
or 9.0.8 patch
NIE89 X X X X
Important: All NIEx9 models have been
discontinued from manufacture, because
starting at 9.0.7 and 10.0, NAE models
include the integration functionality of the
NIE. Existing NIE89s can be field-upgraded
to 10.0, 10.1, and 11.0, respectively.
NIE55, NIE85 X
SNE X X
SNC X X
1 Only NCE25xx-0 is available to upgrade to Metasys 9.0.7 or 9.0.8 with Linux OS.
2 Only NAE35xx-2 and NAE45xx-2 are available to upgrade to Metasys 9.0.7 or 9.0.8 with Linux OS.
3 Only NAE55xx-2 and NAE55xx-3 are available to upgrade to Metasys 10.0 with Linux OS.
6 Only NIE29xx-0s, NIE39xx-2, and NIE49xx-2 are available to upgrade to Metasys 9.0.7 or 9.0.8 with Linux OS.
Table 8: Network Engine integrations available by Metasys Release

Release
Release Release Release
Integration Release 9.0 9.0.7 or
10.0 10.1 11.0
9.0.8 patch
BACnet/IP X X X X X
BACnet MS/TP X X X X X
Legacy N1 LAN X
1 2
Legacy N2 Bus X X X X 1
X
2
3 4
LonWorks X X X X
3
4
Modbus RTU and TCP X X X X X
KNX IP X X X X X
M-Bus Serial and IP X X X X X
C·CURE 9000 and victor X X X
Simplex Fire (secondary
X X X
monitoring only)
Preferred Vendor Lighting
X X X
Systems
Zettler Fire Panel X X
OPC Unified Architecture
X
(OPC UA)
Wireless Supervisor X
1 The M4-SNE110L0-0 model does not support the N2 Bus.
2 The M4-SNE110L1-0 model does not support the N2 Bus.
3 The M4-SNE110L0-0 model does not support LonWorks.
4 The M4-SNE110L1-0 model does not support LonWorks.

Servers
ADS and ADS-Lite
The ADS is a Metasys server running on a computer that has a supported Microsoft® Windows®
operating system and two specific components. The first component is the relational database
management system using a supported edition of Microsoft SQL Server® Express software to
store collected trend data, audit trail messages, and alarm and event messages with operator
annotations. The second component is the web server software that provides SMP UI and Metasys
UI access to data and routes commands to the Metasys system.
The ADS also:
• supports a greater number of engines as a Site Director than an engine supports

• supports multiple, simultaneous international languages at the user interfaces
• allows a greater number of simultaneous users than is supported by an engine
• provides added storage for memory-intensive Metasys features, such as User Graphics
ADS also supports FIPS 140-2 Level 1 compliance and ADFS two-factor authentication starting
at Release 11.0, to help prevent unauthorized access to systems and data, which, if not prevented,
could result in financial and reputational loss, system disruption, and other negative consequences.
Note: ADFS is available only if you are running the Metasys UI.
The ADS-Lite is a specialized offering that enforces specific localized market connection limitations
to other Metasys devices such as ADSs and engines.

Server comparison
The Metasys Server software family includes variants with different feature sets to meet a variety of
different applications.
Table 9: Metasys Server Family Comparison
Feature Application and Data Extended Application Open Application Server Open Data Server (ODS)
Server (ADS) and Data Server (ADX) (OAS)
Host Platform Desktop computer Server platform: Turnkey and virtual Desktop computer
platform: • Microsoft® Windows desktop platform (virtual platform:
• Microsoft Server® operating machine (VM)): • Microsoft
Windows® system • Microsoft Windows®
operating system • Microsoft SQL Windows® operating system
• Microsoft SQL Server database operating system • Microsoft SQL
Server Express • Microsoft SQL Server Express
database Server Express database
• Open Database database • Open Database
Connectivity • Open Database Connectivity
(ODBC) Connectivity (ODBC) compliant
compliant (ODBC) compliant database package
database database package
package Server platform:
Virtual server platform • Microsoft®
(VM): Windows Server®
• Microsoft® operating system
Windows Server® • Microsoft SQL
operating system Server database
• Microsoft SQL
Server database
Supported Up to 5 users Up to 10, 25, 50, or 100 Up to 5 users Up to 5 users
Simultaneous users (license specific)
Users
Network Engine Up to 14 engines Up to 1,000 engines OASMIN: 0 engines The ODS can serve as the
Management Note: support for OASSTD: up to 2 engines Site Director for up to
engines varies 14 network engines on
depending on size of a desktop platform and
server hardware 100 network engines on
a server platform.
Archival of Manual, scheduled, or Manual, scheduled, or Manual, scheduled, or Manual, scheduled, or
Historical Data automatic automatic automatic automatic
Note: This
feature requires
the Metasys
Historical Data
Add-on license,
which needs to
be purchased
separately.
User Interface Metasys UI Metasys UI Metasys UI SMP
SMP SMP SMP
Supports Export Yes Yes No Yes
Utility
Supports Metasys No Yes No Yes
Advanced
Reporting
Supports Energy No Yes No Yes
Essentials

Table 9: Metasys Server Family Comparison
Feature Application and Data Extended Application Open Application Server Open Data Server (ODS)
Server (ADS) and Data Server (ADX) (OAS)
Support for Split No Yes No No
Configuration
Supports Metasys No Yes No No
for Validated
Environments
(MVE)
Five Years of Yes Yes Yes No
Historical Data in Note: This
Metasys UI feature requires
the Metasys
Historical Data
Add-on license,
which needs to
be purchased
separately.
Metasys Database Yes Yes Yes Yes
Manager
Support for Fault Yes Yes Yes No
Detection and Fault Note: At a
Triage features minimum, you
require 8GB of RAM
and four virtual
cores to support
the Fault Detection
and Fault Triage
features on an OAS.
Note: The latest available version of the ODS is Release 10.1. The ODS is not available for
upgrade to Metasys Release 11.0.
For more information, refer to the Application and Data Server (ADS) and Extended Application and
Data Server (ADX) Product Bulletin (LIT-1201525) and to Open Application Server (OAS) Product Bulletin
(LIT-12013309).
ADX
The ADX is a version of the ADS with extended capabilities for historical data archiving that expand
the multi-user web access capabilities of the system. The ADX supports the relational database
management system that uses a supported edition of Microsoft SQL Server software to store
collected trend data, audit trail messages, and alarm and event messages with user annotations.
This relational database also stores configuration information for site security, trend studies, and
other features. The ADX supports the Metasys Advanced Reporting System, which has a web-
based reporting interface and standard report sets. The users can review the alarm and trend
configuration of their site, run summary and detail reports to monitor alarm and event information,
view offline information, combine alarm and audit information in a single report, and aggregate
trend data at a summary or detailed level. An ADX can also support the optional Energy Essentials
reporting feature, which is an extension of the Metasys Advanced Reporting System.
If the ADX software with its accompanying SQL Server database software is installed on one
computer, it is known as a Unified ADX. If the SQL Server software is located on a different
computer, it is known as a Split ADX.
You can install the ADX in a split configuration with the ADX software/SMP UI/Metasys UI on one
computer (the web/application server computer) and the historical trend, audit, and event data
on another computer (the database server) running Microsoft SQL Server software. The System
Configuration Tool (SCT) software, which is used to generate, back up, and restore the network

database offline, is installed on a separate computer in split configuration. The Metasys Advanced
Reporting System is also available in a split configuration, if the SQL Server database components
are installed on the database server and the SQL Server Reporting Services are installed on the
web/application server. In a split configuration, you can place your database server behind a
firewall for an added layer of data protection.
ADX also supports FIPS 140-2 Level 1 compliance and ADFS two-factor authentication starting
ADS/ADX concurrent users

Use the following table to help you determine which ADS/ADX user product that you need to order.
The table provides examples of the total number of supported users who can be simultaneously
logged on the SMP and Metasys UI.
Table 10: Examples of ADS/ADX/ADS-Lite concurrent users
Examples of ADS/ADX concurrent users
ADS/ADX type
SMP UI Metasys UI
0 5
5-user ADS/ADS-Lite 2 3
5 0
0 25
5 20
10-user ADX
8 17
10 15
0 25
10 15
25-user ADX
20 5
25 0
0 50
10 40
50-user ADX
25 25
50 0
5 50
10 50
25 50
100-user ADX
50 50
75 25
100 0
For example, as shown in Table 10, with a 5-user ADS or ADS-Lite, 5 Metasys UI users are supported
if no SMP users are logged in, or 3 Metasys UI users are supported if 2 SMP users are logged in.
Similarly, with a 50-user ADX, 50 Metasys UI users are supported if no SMP users are logged in,
or 40 Metasys UI users are supported if 10 SMP users are logged in. The only Metasys UI user
restriction applies to a 100-user ADX: no more than 50 Metasys UI users are supported, regardless
of the number of SMP users.

OAS
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.
Starting at Release 11.0, 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:
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: Tyco C-Cure-victor, Modbus, M-Bus, and KNX, OPC Unified
Architecture (UA).
The maximum number of supported simultaneous vendor integrations on an OAS is 16. The
following table provides more information about the available integrations, whereby the limits
relate to standard protocol drivers only.
Table 11: 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
Tyco 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.
OAS also supports FIPS 140-2 Level 1 compliance and ADFS two-factor authentication starting
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. OAS is compatible with both Metasys
UI and Site Management Portal (SMP), and can be configured through the System Configuration
Tool (SCT).
The following table provides a summary of the OAS Standard capabilities:

Table 12: OAS Standard capabilities
ADS-type capabilities Network Engine-type capabilities
Supports supervising up to 200 field devices
Supports supervising up to two network engines
directly or 20,000 objects, using BACnet/IP and
(SNE, SNC, NAE, or NCE Series).
Remote Field Bus integrations.
Provides supervisory capabilities such as
Provides the Metasys User Interface (UI), an
scheduling, alarming, trending, data sharing,
intuitive, well-organized, mobile-friendly user
interlocking, and logic for system-wide control
interface.
and coordination.
Optionally (with add-on licenses) provides long
term archival of historical data, trends, alarms,
and events.
Figure 6: OAS system diagram
ODS
The Metasys Open Data Server (ODS) is a BACnet Testing Laboratories® (BTL) Listed BACnet®
Operator Workstation (OWS). At Release 10.1, ODS is at Protocol Revision 15. It conforms to the B-
OWS profile. The ODS supports up to 25,000 local objects and up to five users. You can configure
the ODS as a BACnet Workstation, as a Site Manager Workstation, or as a Combined Workstation.
In the BACnet Workstation configuration, the ODS uses the BACnet protocol to communicate with
networked BACnet devices. BACnet integration maps NxEs, Field Equipment Controller (FEC)-
family devices, and BACnet devices into the ODS. NxEs and FEC-family devices are treated the same
as BACnet devices. This configuration is best for the customer who requires a BACnet operator
workstation using standard BACnet messages. BACnet features are emphasized, and viewable
object capacity is limited to 25,000 objects.
In the Site Manager Workstation configuration, the ODS acts similarly to an Application and Data
Server/Extended Application and Data Server (ADS/ADX) and uses web services to communicate
with the NxE network engines. Other BACnet devices are mapped into the Metasys system through
the NxE using BACnet integration. The Site Manager Workstation configuration is best when
features and capability (for example, object capacity and performance) are more important to
the customer than strict use of standard BACnet services. The ODS provides all advanced Metasys

system features, and the viewable object capacity includes all of the objects from all of the network
engines reporting to the Site Manager Workstation. In this configuration, the ODS can serve as the
Site Director for up to 100 NxE network engines. In addition, you can connect Johnson Controls® IP
controllers, Johnson Controls MS/TP controllers, and BACnet MS/TP devices over a remote field bus
with the use of a BACnet/IP-to-MS/TP router.
In the combined configuration of BACnet Workstation and Site Manager Workstation, the strengths
of both configurations are combined to deliver an optimal solution to the customer. NxE network
engines can use the ODS as a Site Director and communicate with the ODS using web services,
allowing extended object capacity and advanced Metasys system features. In addition, the ODS can
directly access BACnet devices and FEC-family devices using the BACnet integration capability of
the ODS. This configuration is best for the customer who values features and capability, and also
needs the functionality of a BACnet operator workstation for BACnet devices not associated with a
Metasys engine. In this way, operator monitoring and control is extended to BACnet devices outside
of the control of a Metasys engine.
LCS
The LCS85 is a computer-based server that is used to communicate with LonWorks devices
over an IP network. The LonWorks field devices are normally connected to an IP router. In this
arrangement, the Metasys system is used in a flat LonWorks configuration.
User Interface
Two variations of the user interface are available: Metasys UI and Site Management Portal (SMP).
The Metasys UI provides a simple location-based navigation approach to finding information,
including the ability to search for any location by name and to bookmark a location in the browser.
All data displayed in the Metasys UI is organized in a dashboard format, presenting to you the
complete story of what is happening within a space, equipment, or central plant. You can access
the Metasys UI from any type of client device with any screen size. The Metasys UI includes features
ideal for efficient building operations.
At Release 11.0, the following features are introduced:
• Fault Detection—identifies and lists building system-related faults in order of severity to

help operators quickly fix issues and avoid equipment failure, energy waste, and comfort
complaints.
• Fault Triage—an add-on to Fault Detection, it provides fault duration and occurrence
information and corrective action recommendations to improve fault prioritization and assist
less experienced building operators with problem solving.
• Show Involvement—identifies from one screen what an object is serving and what serves
it, provides real-time values on each connection point and distinguishes between operator
commands and references; helps operators quickly identify root cause issues.
• Send Announcement—provides ability to send announcements to select users through email,
login banner and homepage banner so Metasys operators can easily share critical information
and collaborate, right from within Metasys.
• Add/Delete/Configure Objects—provides the ability to add, delete, and configure objects
from directly within Metasys and creates a familiar experience for legacy SMP users.
For a comprehensive list of Metasys UI features refer to the Metasys UI Technical Bulletin
(LIT-12012115). For further details about individual features refer to the Metasys UI Help
(LIT-12011953).
The Metasys SMP provides real-time and historical data views, extensive alarm management
capabilities, and system configuration functions for system administrators or dedicated building
operators. The SMP transforms the raw data from the site and organizes it into a comprehensive

set of information management tools and reports. You can access this portal using the Launcher
through an Internet or intranet connection to a Metasys server or engine. The SMP has all the
features one expects from a traditional workstation, including:
• pop-up alarm windows

• navigation tree—you can create multiple custom trees to best represent the logical layout of
the facility
• dynamic graphics of systems and floor plans that you can zoom in on to show fine details
• multiple display areas you can size and control individually
• global search function and sorting capability that help you find system information within
seconds
• the entire user manual available in the Help system
Information Management is an inherent capability of the overall user experience and reporting
capabilities. Whether you are logged in to the SMP UI running online reports, using the Metasys
Advanced Reporting System, or retrieving data from an engine with the Export Utility, you are
transforming the data collected by the system into information you can use to manage your site.
Tools
Launcher
The Launcher is a software application that lets you use the SMP or SCT to access the Metasys
system, server or network engine on the building network, regardless of its software version. Key
features of the Launcher include:
• Installation of a separate folder to store the Metasys release software on your hard disk. This
practice provides for an isolated, private version of the Java® Runtime Engine (also referred
to as Java Runtime Environment [JRE] ) required to run Metasys software. If you have installed
multiple releases of Metasys software, a separate folder is created for each. The JRE folder
separation strategy allows for independence from the public Java Runtime Engine.
• Support for launching any version of the SMP user interface or SCT. All Metasys server types
and network engine types are supported.
Note: For Release 5.2 or earlier, the specific Java Runtime Environment particular to the
SMP or SCT software release is still required on the client computer.
• Support for launching any website, including Metasys software products, such as Metasys UI,
Metasys UI Offline, SCT Pro, and the Metasys Advanced Reporting System, as well as popular
websites such as the Google® website.
• Option for restricting communication with only secure Metasys servers and network engines.
Contact your local Johnson Controls® representative for access to the Launcher software.
System Configuration Tool (SCT)

The System Configuration Tool (SCT) supports the engineering, installation, and commissioning of
your building automation system. The SCT application enables fast offline generation and Metasys
UI configuration of the complete site, including point naming; integration of N1, N2, BACnet®, and
LonWorks® networks; integration of Modbus, M-Bus, and KNX third-party protocols; integration
of local and remote MS/TP devices; definition of tailored summaries and user views; the creation
of custom control logic using a graphical user interface; and integration of building systems such
as C•CURE 9000 access control, victor video management, Simplex® fire, Zettler® fire, connected
lighting systems from preferred vendors, and OPC UA. SCT offers productivity features that includes

the migration of supervisory devices and the mass creation of equipment, spaces, and serving
relationships.
You can use SCT or System Configuration Tool Pro (SCT Pro) to manage a mixed release site of
devices at Release 5.2 and later that include the SNE, SNC, Network Automation Engine (NAE),
Network Control Engine (NCE), Network Integration Engine (NIE), Application and Data Server/
Extended Application and Data Server (ADS/ADX), Open Application Servers (OAS), Open Data
Server (ODS), and the Metasys UI. To keep the archive database current, you can schedule regular
uploads from the devices on the site.
SCT has a one-click installation. The SCT installer installs the required software prerequisites, such
as Internet Information Services (IIS) and Microsoft® .NET Framework 4.6.1. If no SQL Server® is
present, the SCT installer installs SQL Server 2014 Express software.
The SCT installation includes additional applications. You can use the Metasys UI Offline software
to configure Metasys UI graphics and the display of data without a live connection to devices. You
can use the Software Manager to manage licenses for Johnson Controls® software and features.
For example, you can apply or remove licenses for the SCT software and field controller packages.
IT Security Commitment
Metasys uses secure HTTP with Transport Layer Security (TLS) 1.2 between the SCT computer, all
Metasys servers, and network engines that are upgraded to Metasys Release 9.0 and later. The
encrypted HTTPS communications apply to the Metasys servers, Metasys UI, network engines,
and SCT. This ensures that unauthorized users and computer hackers cannot view the contents of
communications sent between Metasys equipment. By default, self-signed certificates are installed
on supported products, with the option of configuring trusted certificates configured by an internal
IT department or a Certificate Authority. To indicate the active security level (trusted, self-signed,
or untrusted), three small security shield icons appear on the SCT login screens and on the SCT UI
screens.
Johnson Controls continues to enhance the security of Metasys with the addition of signed
resource files, and the pairing of supervisory devices with the site director to ensure encrypted
communication.
The following table outlines the recent history of SCT, Metasys Server, and NAE Update Tool
releases:
Table 13: SCT, Metasys Server, and NAE Update Tool releases
Release Date SCT Metasys Server NAE Update Tool
October 2015 Release 7.0 Release 7.0 Release 7.0
September 2016 Release 11.0 Release 8.0 Release 11.0
February 2017 Release 11.1 Release 8.1 Release 11.1
August 2017 Release 12.0 Release 9.0 Release 12.0
December 2018 Release 13.0 Release 10.0 Release 13.0
October 2019 Release 13.2 Release 10.1 Release 13.2
The NAE Update Tool
continues to be a
component of the SCT
October 2020 Release 14.0 Release 11.0 install. However, we
encourage you to work
with SCT Pro instead of
the NAE Update Tool.
For a list of updated features and benefits available at SCT Release 14.0, refer to the System
Configuration Tool Catalog Page (LIT-1900198).

System Configuration Tool Pro (SCT Pro)
SCT Pro is the next generation interface for SCT. It provides significantly streamlined workflows,
and greatly simplifies tasks that were previously time consuming or cumbersome. For example, you
can use SCT Pro to maintain healthy backup practices for a site, such as setting up backups to occur
automatically on a recurring schedule.
When you install the SCT, you also have access to the SCT Pro web application. You can launch
the HTML user interface from SCT or from a URL on any client device type (workstation, tablet, or
phone).
SCT Pro currently includes a subset of the features that are available in the SCT. With each release,
features from the SCT are incorporated into SCT Pro and optimized to significantly streamline
workflows and simplify tasks. For example, SCT Pro features a single, automated process to
upgrade network engines. SCT Pro also includes features that are not available in the SCT. For a
summary of the main differences between SCT and SCT Pro, refer to the System Configuration Tool
Catalog Page (LIT-1900198).
SCT and SCT Pro use the same databases and share the same job scheduling system, named the
Action Queue. Therefore, you can use the SCT and SCT Pro interchangeably and select the most
appropriate application for the current task.
Use SCT Pro to complete any of the following tasks:
• Provision a new network engine

• Upload and download a site
• Perform a backup of a site
• Schedule automatic recurring backups
• Restore a site from a backup
• Upgrade a device
• Discover devices on the same subnet as the SCT Pro server
The following table describes which specific tools and capabilities are most appropriate for each
type of network engine:
Table 14: Network Engine Reimaging Tools
Tools to use NAE35, NAE35, NAE55 NAE55 NAE55 SNE, SNC SNE, SNC
NAE45, NAE45,
NCE25, NCE25
NAE55
Release Release Release Release Release Release Release
9.0 9.0.7 10.0 10.1 11.0 10.1 11.0
Windows or 9.0.8 Linux Linux Linux Linux Linux
Linux
1
NAE Update Tool X X X X X — —
1
SCT 14.0 X — X X X X X
SCT Pro 14.0 X X X X X X X
1 The NAE Update Tool continues to be a component of the SCT install. However, we encourage you to work with SCT Pro
instead of the NAE Update Tool.
For a guided tour of features on a particular page in SCT Pro, click on your account name in the
upper-right corner of the SCT Pro window, and then click Tour.
For more information about SCT Pro, refer to SCT Pro Help (LIT-12013035).

Metasys Database Manager
The Metasys Database Manager provides both database management and database monitoring
functions, handled in two separate windows. Database management includes summarized
information on and methods for backing up, purging, and restoring Metasys system trend, alarm
(event), and audit databases. An ADS Rename function is also available that is most useful if you
are moving Metasys databases to a new computer. Monitoring includes an indication of database
status compared to three levels of defined database sizes.
VMD Generator Express (VGE Tool)

The VMD Generator Express (VGE) tool allows you to view, create, and modify the vendor model
definition (VMD) files required by third-party integrations on the NIEx9. Both the TCP/IP and
Remote Terminal Unit (RTU) formats are supported.
The VGE tool incorporates a version tracking system that stores data and comments every time you
create or modify a file. The tool allows generic modeling for standard integrations, meters, chillers,
and air handling units (AHUs).
NIEx9 Driver Manager Tool

The NIEx9 Driver Manager tool allows you to upload driver and license files related to the Network
Engine custom integration solutions. The primary use of this tool is to manage the backup and
restoration of network engine files before device re-imaging with SCT or the NAE/NIE Update Tool.
Once the NIEx9 files are backed up, you can use the tool to restore these files after the network
engine is re-imaged.
Note: The tool is only used with network engines at Release 9.0 or earlier. Newer network
engines use the Linux operating system that have licensed integrations built into the image.
Metasys system capabilities

Site Director
When users access any engine or server directly through a web browser, only the information local
to that device is accessible. To make all information in the facility accessible from a single point,
the Metasys system uses a Site Director. The Site Director is the device designated to maintain
the site information, including the logical organization of data about your facility, user password
administrative information, and overall master time and date. This function resides in an engine
or, on large installations, a server. For networks that do not have a server, one of the engines is
designated as the Site Director. When one or more servers are part of the network, one server must
be designated as the Site Director. The Site Director provides a uniform point of entry and supports
functions such as user login, user administration, time synchronization, and traffic management.
Consider a server as the Site Director if you require:
• support of multiple international languages

• repository for trend and alarm data and operator transactions, along with annotations for MVE
systems
• a greater number of simultaneous users than an engine allows
Time management
The time and date used by all devices connected to a site are synchronized automatically,
preventing errors from manual time entry and clocks that become inaccurate over time. Network-
wide time management ensures that scheduling, trending, audit trailing, data collecting, time-
stamping of alarms, and other functions requiring accurate time management use the same time
and date consistently for all system operations. Because the Site Director is the master time keeper

for all engines and servers on a single site, all of these devices are assumed to use the same time
zone for all time-rated functions.
For network-wide time synchronization, the engine or server acting as Site Director is the time
server for the entire site. All other devices are time clients because they receive the time from
the Site Director. The Site Director can be configured to use three different methods of time
synchronization: Unicast Simple Network Time Protocol (SNTP) (also known as Microsoft Windows
time synch), Multicast SNTP, or BACnet time synch. The Site Director can also be configured to
synch its time from an external website.
New multi-time zone enhancements allow you to schedule events using local machine time
management instead of calculating the Site Director time in relation to the device hosted in a
different time zone.
System navigation
The Metasys UI supports navigation in the form of spaces and equipment relationships. A space is
the physical location or area that is served by a piece of equipment. Equipment is the broad term
used to describe the physical controllers and devices that make your building run. These controllers
and devices include boilers, chillers, air handling units, lights, meters, security, and anything else
used to maintain your building's environment. Equipment can serve spaces and other equipment.
A Metasys system administrator can create spaces and equipment and define the relationship
between them in SCT.
The Building Network tree in Metasys UI provides access to objects using an alternative navigation
tree to the Spaces tree. The Building Network organizes objects according to the Metasys object
hierarchy, similar to the All Items tree in the SMP. The Building Network tree supports the Detail
widget, which supports the Focus view, Network view, and Diagnostic view, the Summary view
widget, Equipment Relationships widget, and Trend widget depending on the object selected.
Objects listed in the Building Network tree are identified by name and by icon and display Global
Status indicators.
Note: The Building Network tree order is inherited from the SMP All Items tree with minor
exceptions. For example, extension objects appear in the All Items tree in the Metasys UI,
whereas they do not appear in the All Items tree in SMP. To reorganize the order, use the All
Items tree organizer in SMP.
The SMP UI supports user-customized system navigation schemes in the form of User Views,
a hierarchical method of organizing and displaying some or all of the items within a system. A
Metasys system administrator can limit a user’s access to the Metasys system by creating User
Views and assigning them to specific users. User Views provide organizational structure and data
filtering for the information displayed in the Metasys Advanced Reporting System UI.
Monitoring and commanding

Monitoring and commanding allows you to efficiently navigate through items associated with your
building operations as well as view, analyze, and modify these items. After creating items with
wizards, use these features to:
• access, view, and modify item data
• send commands to items
• run reports to analyze item information
Preferences
The Metasys system provides customized preferences for the Metasys user interfaces. The
preferences allow you to configure how the user interfaces behave, including the sounds and
colors, the startup views, alarm priorities, and links from within the user interfaces to external
applications. Preferences are divided into two categories: system preferences and user preferences.

System preferences apply to all users who log in to the site or device and affect the performance
and operation of the system. User preferences apply to a specific Metasys system user and define
how information is displayed in the user interfaces. User preferences do not affect the operation of
the system.
Alarm and event management

The alarm and event feature provides event management for the system. Users can configure the
routing of event messages to destinations such as the server for permanent storage. The Metasys
Site Management Portal UI features a pop-up alarms window, which alerts the operator to potential
problems whenever the operator is logged in to the system; and an event viewer, which provides
for greater analysis or a history of alarms and events in the system.
Note: To ensure proper pop-up alarm functionality, always use the Desktop mode for Windows
10 and Windows 8.1.
Users can configure alarms and events with the Metasys system, using either a Metasys alarm
extension or a BACnet alarm (intrinsic or algorithmic). Metasys alarm extensions generally
provide more feature capability and ease of setup, whereas the BACnet alarms provide better
interoperability with other BACnet systems.
Users can also view and take action on alarms that occur in the Metasys system with the Alarm
Manager and the Alarm Monitor in the Metasys UI. The Alarm Manager and Alarm Monitor display
all alarms pending acknowledgment and discarding. Users can access the Alarm Manager when
they are logged in to the Metasys UI, and they can access the Alarm Monitor when they are not
logged in to the Metasys UI. Users can access both the Alarm Manager and the Alarm Monitor
on computer and tablet platforms. To manage alarms on phone platforms, users can access the
Metasys UI Alarms list. The Alarms list displays alarms that have occurred for points mapped and
unmapped to Metasys UI equipment. You can see the top 100 alarms in the Alarms list. The listed
alarms include the latest occurrences, and alarms that were acknowledged, as indicated by a green
tick mark.
The Equipment Activity widget in the Metasys UI also displays alarms and user changes made
during a time range of up to one year within the last five years for a selected piece of equipment.
Note: An event is a notification of a status change in the Metasys system. An alarm occurs
when a value defined in an engine goes outside of a user-defined range, changes to a user-
defined contact condition, or fails to respond to a command within a user-specified time. When
an alarm occurs, an event is generated. Events can be generated by any Metasys platform. For
example, if the NAE detects that a network node is offline, it can generate an event. If an error
occurs in the server platform, an event can also be generated. Once an event is generated, it
is stored in an Event Repository file located on the device that generated the event. Users can
retrieve and examine events stored in the Event Repository.
Encrypted communication
All Metasys Server based devices (ADS, ADX, OAS, and ODS) and network engines are installed
with and operate in a secure mode using self-signed certificates. Self-signed certificates improve
system security by providing a secure, encrypted connection to the Metasys web server. All data
on the network occurs over an https connection using TLS 1.2 that cannot be read by a third-party
application. When you use a self-signed certificate, the Metasys web server is in effect saying,
"don't worry, I am who I say I am. You can trust me." Employing self-signed certificates has no cost.
If the customer wants a higher level of security, they can replace self-signed certificates that are
installed on the Metasys server and network engines with a certificate issued by a Certificate
Authority (CA). These trusted certificates can be generated by the customer's internal IT
department or be purchased from a CA such as Verisign or GoDaddy. When you use a trusted
certificate, the Metasys web server is in effect saying, "Trust me - the CA agrees I am who I say I
am."

The steps for installing trusted certificates on a Metasys server are covered in the respective
installation documents: Metasys Server Installation and Upgrade Instructions (LIT-12012162) or Open
Application Server (OAS) Installation Guide (LIT-12013222). The steps for installing trusted certificates
on network engines are described in Metasys SCT Help (LIT-12011964).
When deploying certificates, keep the following in mind:
• The steps for setting up trusted certificates can be complicated. Ask the customer's IT
department for assistance.
• Secure and encrypted communication has the greatest importance between the Site Director
and a client logging in to the Site Director from the Metasys SMP. In many cases, the most
practical choice is to install a trusted certificate at the Site Director (ADS, ADX, OAS, or ODS)
and a self-signed certificates on each network engine that is upgraded to Release 8.1 or later.
If the Site Director is a network engine, you might want to install a trusted certificate on just
the Site Director NAE and self-signed certificates on its child devices.
• The name of the network engine within the SCT archive and the subject common name (or
hostname associated with certificate) within the certificate must match exactly for a certificate
to be imported and bound to IIS.
• Some certificate authorities may require the subject common name (or hostname associated
with certificate) within the certificate to include a domain name. If you are implementing
certificate management on an existing Metasys system, adding a trusted certificate may
require you to add a domain name to the original host name of a server or engine. This action
requires you to rename all data in the Metasys historical databases. This renaming operation
requires intensive database operations that significantly prolong a system upgrade. Therefore,
be sure to allocate extra time if you are renaming historical data as part of an upgrade to
Metasys Release 11.0.
Destination Delivery Agents (DDA)

DDAs are the method used for routing and delivering Metasys alarm extension event messages to
destinations such as printers, email, and Network Management systems.
Site Management Portal (SMP) management of Server DDAs was removed at Release 10.1.
Management of Server DDAs is available with the Remote Notifications feature in Metasys UI only.
However, SMP management of Server DDAs is still available for Metasys for Validated Environments
(MVE) sites and for ODS sites.
The Metasys system uses an Email DDA, Syslog DDA, Printer DDA, and Simple Network
Management Protocol (SNMP) DDA. The email DDA supports standard Simple Mail Transfer
Protocol (SMTP), Post Office Protocol (POP), and Internet Message Access Protocol (IMAP). The
Metasys Server can use any of these DDAs, but a network engine at Release 9.0.7 or later can only
use the Email DDA, Syslog DDA, and SNMP DDA.
SNMP provides IP standard SNMP functionality in the Metasys system, enabling network
administrators to manage Metasys network performance, find and resolve Metasys system-related
issues, and plan for future growth of the Metasys system. SNMP functionality uses standard SNMP
Versions 1, 2C, and 3 (excluding SNMP encryption and authentication support). The Metasys system
allows delivery of unsecured SNMP traps for Metasys alarm events from all engines and servers
to the facility owner’s Network Management System (NMS), and allows the NMS to execute SNMP
Gets against engines. This version of SNMP support does not include the SNMP set commands.
Johnson Controls has developed a downloadable custom dynamic Management Information
Base (MIB) that allows the NMS to monitor Metasys point objects, display attributes, and control
sequence objects. The MIB is constructed to accurately reflect the additions and deletions of objects
in the network engines as the changes occur. The custom MIB defines explicit traps and associated

attributes that align with Metasys alarm messages, making data correlation (parsing/sorting) at the
NMS straightforward and seamless.
Syslog DDA
The Metasys system provides the optional capability of sending its configured audit log entries
and alarm notifications to an external, industry-standard Syslog server, conforming to Internet
published RFC 3164. The Syslog option provides positive indication of each field possible in the
Metasys event and audit entries, replacing any blank field with the single character dash (-).
Individual fields of each Metasys message are sent to the Syslog server separated by the vertical
bar symbol (|), ensuring the integrity of all data sent to the Syslog server.
After the Syslog DDA is configured, all messages sent to the local ADS Repository are also sent
immediately to the configured Syslog server. You can apply forensic analysis on the consolidation of
all electronic audit and event information at the Syslog server.
Encrypted email
Metasys software features an email encryption capability that encrypts user names and passwords
as they are entered into the SMP UI. Embedded and server machines can thereby send emails
to email servers over a secure channel (secure socket layer [SSL]). The entire email payload
is encrypted, and allows Metasys software to communicate to email servers that require SSL
connections.
Users can configure email encryption with no authentication required, including SMTP
authentication, and POP-Before-SMTP authentication.
Scheduling
Scheduling provides a graphical user interface that illustrates when events are scheduled to occur.
Scheduling automates routine functions, such as transferring a room from occupied mode to
unoccupied mode for heating and cooling needs, and energy optimization. Each schedule consists
of a weekly schedule, an exception schedule, a list of items in the schedule, and an effective period.
Exception schedules take precedence over the daily schedule only for their configured length
and then return the schedule to its typical weekly schedule. Exceptions can include references to
Calendars that can, for example, reflect a holiday schedule for the entire facility or show selected
tenant spaces in the building. Another view within the schedule, called Today’s Schedule, shows the
current day’s schedule including how each exception schedule affects the current day’s schedule.
A multi-time zone feature is available that allows the definition of schedules across different time
zone. You can program schedules based on device time zones instead of converting the time to
correlate to the Site Director's time zone.
Historical Data Management (Trend)

Users can collect, store, and view historical samples of object data with the Metasys Historical Data
Management capability. With the information generated by this feature, you can manage energy
usage, prove compliance to standards, and diagnose problems in your facility.
Each engine has a local buffer where it stores trend samples. Users can configure the size of this
buffer, in a number of samples. If a server exists on the site, you can send the trend samples to its
database. This database supports backup, restore, and archival of data to long-term storage. You
can display trend data as a graph or table of values on the SMP UI. The Trend widget in the Metasys
UI displays more recent historical data as a graph. Users can also copy trend data to the browser
computer’s clipboard, and thereby transfer the data to spreadsheets, databases, and Microsoft
Word documents.
The SMP UI makes it easier to detect system-level performance by displaying multiple trends on
a single graph or table. You can either predefine multiple trends in a trend study or dynamically
select various point trends to display on a single graph using the Trend Viewer or the Trend widget

in the Metasys UI. The Site Management Portal UI also offers information on the rate of events, rate
of samples, and number of samples that are lost. Refer to the Metasys SMP Help (LIT-1201793).
System security
User accounts control user access to the Metasys system. An account defines which portions of the
Metasys data a user can access (for example, all HVAC data or all lighting data from a particular
area of the building) and which functions the user can perform on that data, from view-only access
to configuring new databases. The Metasys system provides the ability to divide the data into 13
pre-defined categories (including HVAC, Fire, and Security), plus 150 additional custom categories;
and has 10 different levels of user functionality.
Users can further limit user accounts to operate only at specified times on specified days of the
week. The System Administrator creates all account settings.
Each account can also have associated preferences, such as which graphic or trend to display when
a user logs in to the SMP UI, or which User Views appear in the Navigation Tree.
The SMP and Metasys UI can use Microsoft Active Directory® accounts.
The User Management feature facilitates the creation and management of users and their roles,
category-based permissions, and privileges directly in Metasys UI Online, without the need to
install software on client machines. Administrators can create and manage user details for Active
Directory and Metasys local users. This feature is also available in the Metasys Site Management
Portal (SMP), but over time it will be available in Metasys UI Online only.
Users can assign user access permissions to specific spaces and the equipment serving those
spaces with the Metasys UI Space Authorization. Users can thereby segment user access by physical
space within the building or campus.
In addition to making it easier for system administrators to manage Metasys account access,
Microsoft Active Directory® including ADFS also provides the ability to use Single Sign-On to access
the Metasys system, through the Site Management Portal UI, together with other supported
applications on the enterprise network.
The Audit Log records all user activities, and the System Administrator can thereby monitor user
actions.
User names and passwords are obscured at login for local and Active Directory accounts. After
login, user names are partially obscured on the SMP or SCT UI window (for example, JohnSmith
appears as Joh***).
The following table lists the password rules enforced by the Metasys system user's language locale
setting.

Table 15: Metasys system password rules
Supported language Enforced password rules
locale
• The password must include a minimum of 8 characters and a
maximum of 50 characters.
• The password cannot include spaces or include a word or
phrase that is in the Blocked Words list.
• The password and the user name cannot share the same three
consecutive characters.
English (en_us) • The password must meet the four following conditions:
- Include at least one number (0–9)
- Include at least one special character (-, ., @, #, !, ?, $, %)
Note: Only the special characters listed above can be
used; all other special characters are invalid.
- Include at least one uppercase character
- Include at least one lowercase character
Czech (cs_cz)
German (de_de) • The password cannot include spaces or include a word or
Spanish (es_es) phrase that is in the Blocked Words list.
French (fr_fr)
• The password and the username cannot share the same three
Hungarian (hu_hu)
Italian (it_it) consecutive characters.
Norwegian (nb_no) • The password must meet three of the following conditions:
Dutch (nl_nl) - Include at least one number (0–9)
Polish (pl_pl)
Portuguese (Brazilian) - Include at least one special character (-, ., @, #, !, ?, $, %)
(pt_br) - Include at least one uppercase character
Russian (ru_ru) - Include at least one lowercase character
Swedish (sv_se) - Include at least one Unicode character that is categorized
Turkish (tr_tr)
as an alphabetic character but is not uppercase or
lowercase

Table 15: Metasys system password rules
Supported language Enforced password rules
locale
• The password cannot include spaces or include a word or
phrase that is in the Blocked Words list.
• The password and the user name cannot share the same three
consecutive characters.
Chinese Simplified (zh_cn)
Chinese Traditional (zh_tw) • The password must meet two of the following conditions:
Japanese (ja_jp) - Include at least one number (0–9)
Korean (ko_kr)
- Include at least one special character (-, ., @, #, !, ?, $, %)
- Include at least one uppercase character
- Include at least one lowercase character
- Include at least one Unicode character that is categorized
as an alphabetic character but is not uppercase or
lowercase
Refer to the Account Policy Tab section in the Security Administrator System Technical Bulletin
(LIT-1201528) for further information about how passwords are used by the user account, the
account lockout policy and the inactive session policy.
Logic Connector Tool (LCT)

Use the Logic Connector Tool (LCT) to create custom application programs that execute in any
engine. The programs are created using a drag-and-drop editor. The programmer can connect
real-time point data in the engine with logic blocks that perform mathematical, logical, and various
specialized control functions. You can create, edit, and view LCT programs online through the
Metasys Site Management Portal UI, or offline using the SCT. When you view the finished programs
through the SCT, you can simulate them to verify proper operation before you download them to
the engine.
Interlock object
The Interlock object provides a means to establish conditional control over one or more other
objects. It consists of an If conditional statement, True command statements, and False command
statements. Through these statements, the user specifies a set of conditional checks (using one or
more points) for which a series of commands is used to control a collection of one or more other
objects.
Optimal Start
Optimal Start automatically determines the correct time to start HVAC systems to ensure the facility
is ready for occupants at the scheduled time. It adjusts to seasonal variations and minimizes the
energy used.
The generic standard object screens handle the Optimal Start/Stop object configuration and focus
views. The object defines views for configuration and focus, and the generic screens interpret the
views to display the proper fields to the users. Users do not need custom screens or handlers.

Demand Limiting and Load Rolling
The Demand Limiting (DL) feature reduces utility bills by limiting peak energy usage. DL electively
turns off (sheds) equipment, such as fans and lights, or adjusts setpoints to limit energy use during
peak times.
The Load Rolling (LR) feature helps save money by reducing overall energy consumption. LR acts
continuously to maintain a specified energy reduction by shedding unnecessary loads. A facility can
implement either one or both of these features.
Audit Trails (Transaction Data Management)

The Audit Trail feature records events generated either by user actions or system activity. Examples
of user actions include logging in to the Site Management Portal UI or issuing commands to a
point. Examples of system activity include device restart initialization settings or internal security
changes. An audit message consists of the information that describes a significant event on the
building automation system (BAS). For each significant event, a new audit message is generated
and appears in the Audit Viewer.
Once an event is sent to the Audit Trails subsystem, an audit message is generated and stored in an
Audit Repository file located on the server or engine that detected the condition.
Users can forward audit messages from the Local Audit Repository to a user-specified ADS Audit
Repository for permanent storage on a server (ADS/ADX), based on user-defined rules.
Starting at Release 11.0, users can view audits in the System Activity feature in Metasys UI. System
Activity is a system-level audit log that provides a time line view of all audits that have occurred
across an enterprise.
Users can also view audit messages in the Audit Viewer of the SMP UI. Once a user logs in to the
Site Director, the user can view all audit messages from the server or any device that contains a
Local Audit Repository. When a user directly logs into a device not designated as the Site Director,
the user can only view audit messages in that device’s Local Audit Repository. Any audit messages
generated on a server are placed directly into the ADS/ADX Audit Repository.
Users can also view user changes made within the last seven days for a selected piece of equipment
in the Equipment Activity Widget of the Metasys UI. Users can also discard user changes in this
widget.
System diagnostics and serviceability

The engine collects and stores diagnostic data. The Diagnostic view of the engine device retrieves
and displays diagnostic data related to communications, internal component performance, and
other areas.
Metasys for Validated Environments

Metasys for Validated Environments (MVE), extended architecture is a feature designed for facilities
that require regulatory compliance for their environmental systems. MVE software is installed on
Metasys ADX, which provides the ability to configure supervisory engines as validated devices. The
following table lists the existing upgradeable MVE Release 10.1 validated engines as well as the
Release 11.0 MVE supported validated engines:
Table 16: MVE validated engines
Release 10.1 Release 11.0
MS-NAE5510-2 MS-NAE5510-2
MS-NAE5510-3 MS-NAE5510-3
M4-SNE22000-0 M4-SNE22001-0
M4-SNC25150-0 M4-SNC25151-0

Table 16: MVE validated engines
Release 10.1 Release 11.0
M4-SNC25150-04 M4-SNC25151-04
M4-SNC16120-0 M4-SNC16121-0
M4-SNC16120-04 M4-SNC16121-04
Important:
All validated engines have to be at the same release as the validated site director. For example,
if the validated engines are at 11.0, the validated site director also needs to be at 11.0.
However, you can have non-validated engines at a previous release (11.0 or earlier). Refer to
Metasys for Validated Environments Extended Architecture Catalog Page (LIT-1900466) for further
information about validated engines.
MVE is not supported on a BACnet ODS Workstation and it is not supported on an OAS.
MVE is specifically designed to help customers address United States Food and Drug Administration
(USFDA) Title 21, Code of Federal Regulation (CFR) Part 11 compliance. MVE is also compliant with
other similar agencies around the world that deal with electronic records and electronic signature
requirements, such as Annex 11 of the European Union Good Manufacturing Practice (EU GMP)
regulations (European Medicines Agency [EMEA] 1998).
The ADX with MVE software provides secure data management and reporting capabilities, traceable
electronic records and signatures, and time-stamped audit trails for facilities subject to Part 11
compliance. It manages and protects the long-term storage of trend data, audit data, event/
alarm messages, annotations, and system configuration data. In addition, complex passwords and
message encryption secure the system from unauthorized access and data tampering.
UL 864 10th Edition UUKL and ORD-C100-13UUKLC Smoke Control Listing

Components of the Metasys system running Release 8.1 software are Underwriter Laboratories
(UL) 864UUKL/ORD-C100-13 UUKLC 10th Edition Smoke Control Listed. In applications requiring
smoke control, this offering provides the protection of a UL 864UUKL listed smoke control system
that has a lower installed cost and leverages the operational efficiencies of using a single system
to provide HVAC and Fire Alarm smoke control. Earlier versions of the Metasys system also support
UL 864UUKL 8th and 9th Editions. Many controllers and equipment that was qualified for these
earlier editions have been brought forward for use in the 10th Edition. Also, if different editions of
UL 864 must coexist in the same building, an Ethernet switch must be installed to isolate each UL
864 Edition.
The Metasys Smoke Control System consists of a set of hardware and software components
specifically UL 864 10thEdition UUKL/ORD-C100-13 UUKLC smoke control listed. The listing applies
to an indoor, dry environment only, where each Air Handling Unit (AHU) is located in an indoor,
air-conditioned mechanical space. This listing also applies to an application where a Rooftop Unit
(RTU) is located outside but the smoke control panel servicing the RTU is mounted in an indoor,
conditioned mechanical space, with conduit wire runs to the RTU. However, this listing does not
support applications where smoke control equipment is mounted in the RTU itself, or where
equipment is exposed to a damp or wet environment. Lastly, the 10th Edition listing is intended for
building systems in United States and Canada.
The smoke control applications are performed with an NAE and Johnson Controls MS/TP and N2
bus field controllers. The Metasys product code numbers with a dash U suffix indicate that they are
for the Metasys Release 8.1 UL 864 UUKL/ORD-C100-13 UUKLC smoke control. Also, specific SCT and
CCT software releases are spelled out in the listing. For details, refer to the Metasys System UL 864
10th Edition UUKL/ORD-C100-13 UUKLC Smoke Control System Technical Bulletin (LIT-12012487).
The smoke control offering provides a configurable yet straightforward application for receiving
fire alarm signals, and it has the ability to control fans and dampers in a prescribed manner based

on prioritized smoke control schemes. Smoke Control systems can also be activated automatically
from a firefighter's smoke control station (FSCS). The FSCS enables a firefighter to execute real-
time control from the FSCS panel. Automation Displays, Incorporated (ADI) has a UL/ULc Listed
Firefighter's Smoke Control Station (FSCS) that integrates with the Metasys UL 864 10th Edition
UUKL/ORD-C100-13UUKLC Smoke Control Listed Metasys Release 8.1 system. The UL/cUL 864
standard requires that one FSCS be included as part of the listed smoke control system.
Note: The Authority Having Jurisdiction (AHJ) must approve the graphics on the FSCS panel
as well as the location in a secured part of the building. Refer to the specific building codes
or standards that often contain specifics about the FSCS. For more information, refer to the
Metasys System UL 864 10th Edition UUKL/ORD-C100-13 UUKLC Smoke Control System Technical
Bulletin (LIT-12012487).
Federal Information Processing Standard (FIPS) 140-2 Level 1 compliance

FIPS 140-2 is a U.S. government cyber security standard used to approve cryptographic modules
and algorithms used for encryption. Two Metasys component types have been updated at Release
11.0 to include FIPS 140-2 certification or compliance; however, they have been implemented
differently as shown below:
• Network engines: FIPS 140-2 Level 1 compliance is included by default in all SNE, SNC, and
NAE55xx-2/-3 series network engines that have Release 11.0 software and is an optional
feature that can be purchased separately and added onto NAE85/LCS85 series network
engines. FIPS 140-2 Level 1 compliance is certified for SNE and SNC series network engines.
• Metasys Application Servers (ADS, ADX, and OAS): FIPS 140-2 Level 1 compliance is an
optional feature that can be purchased separately and added on to Metasys Server offerings at
Release 11.0.
In addition, FIPS 140-2 enhancements result in the following mixed site compatibility behaviors that
need to be understood to prevent field misunderstanding and rework.
Table 17: FIPS 140-2 impact on mixed-site communication behaviors
Communication Site Director type and FIPS 140-2 status
behavior Network Engine Metasys Server or Metasys Server
at Release 11.0. NAE85/LCS85 at at Release 11.0
FIPS 140-2 is Release 11.0, and or NAE85/LCS85,
included by default. FIPS 140-2 is added. but FIPS 140-2
is not added.
Can communicate with
child network engines
at Release 10.1 or No No Yes
earlier (FIPS 140-2 not
available)
Can communicate with
child network engines
Yes Yes Yes
at Release 11.0 (FIPS
140-2 is default)
Active Directory Federation Service (ADFS) two-factor authentication

ADFS integration with two-factor authentication is an add-on, licensed feature to add support for
Metasys using ADFS, a single sign-on solution developed by Microsoft®. ADFS can then, in turn, be
used to provide two-factor authentication for access to Metasys. ADFS helps prevent unauthorized

access to Metasys, which, if not prevented, could result in data, financial, and reputational loss,
system disruption, and other negative consequences.
Note: ADFS is available in Metasys UI only. The ADFS single sign-on and two-factor
authentication are configured on the customer's ADFS system.
Reporting capabilities
Metasys Export Utility Software
The Metasys Export Utility software provides facility managers with the ability to easily build custom
reports using historical data from the Metasys system. This data can be used to manage daily
building operations. The Metasys Export Utility software extracts historical trends, alarms, and audit
data from an engine or server. Users can collect data desired by the operator for analysis from the
system and store it in up to six different formats, including Microsoft Word® or Microsoft Excel®
files. In addition, the scheduling feature retrieves and saves data based upon user-configurable
time intervals.
The Metasys Export Utility provides the user with the ability to create runtime studies and discover
root cause analysis of system changes and mechanical equipment failures. Users can also collect
trended runtime data for use by a computerized maintenance management system (CMMS) to
schedule mechanical maintenance of HVAC systems.
Metasys Advanced Reporting System

The Metasys Advanced Reporting System is a standard capability of all ADXs and ODSs when using
supported SQL Server software, with SQL Server Reporting Services (SSRS) installed. The web-based
reporting interface provides standard report sets. Users can thereby review the alarm and trend
configuration of their site, run summary and detail reports to monitor alarm and event information,
view offline information, combine alarm and audit information in a single report, and provide
summary and detailed trend aggregations. The site’s All Items or User View navigation tree filters
the report information. Users can customize the date range and data type desired for each report.
Once a report is created in the user interface, users can export the data into common applications,
such as Microsoft Excel® spreadsheet or Adobe® PDF formats.
For information about the reporting capabilities offered by the Metasys UI, refer to Metasys UI Help
(LIT-12011953).
Energy Essentials
Energy Essentials is an optional software feature that can be added to the Metasys Advanced
Reporting System. It offers seven types of energy reports that provide a high-level view of
normalized energy use across your site, and presents your daily electrical demand graphically.
Note: The release number of Energy Essentials must match the release number of the ADX
or ODS, and Metasys Advanced Reporting System software installed on the same computer.
Metasys Advanced Reporting and Energy Essentials support installation on a computer with
SQL Server 2017, SQL Server 2016, and SQL Server 2014 software.
Metasys graphics options

Metasys UI Graphics
Metasys UI allows Metasys system designers to efficiently create, edit, and manage graphics in
either Metasys UI or Metasys UI Offline. The Graphics Manager and Graphics Editor do not require
any additional software. System designers can immediately validate graphics created within the
Metasys UI. Included is a full library of symbols and templates that provide photo-realistic images

of equipment, systems, and floor plans as a starting point for system designers who do not have
the time or expertise to create graphics from scratch.
To ensure optimal performance of the graphics created in the Metasys UI, follow the
recommendations in the table below.
Table 18: Recommended maximum selections
Item or element Recommendations Notes
Number of elements 0–125 An element is any shape, symbol, or image
(shapes, symbols, or that is added to the graphic.
images)
Number of bound 0–200 We recommend that you have no more
Metasys points than 200 bound Metasys points on a single
graphic unless you are using a Status
Summary element.
Number of status 0–6 This limit allows for 50 bound Metasys
summaries points per Status Summary with a
recommended maximum of six Status
Summaries on a graphic. The limit results in
300 points whose statuses are summarized
using only five elements (not 300 elements).
This Status Summary exception contrasts
the bound Metasys point recommendation
of 200 maximum, because not all bound
values appear in the graphic.
Number of images 0–5 An image is any image file that is added to
the Graphic Canvas.
Note: We recommend that images
have a maximum size of 1,600 pixels
(height) by 1,200 pixels (width)
and 1 MB in file size. Exceeding the
recommended dimension size may
cause significant delays in load times.
Number of animations 0–50 This number applies to animations that
are actively running at the same time (for
example, a supply fan and a return fan).
Standard Graphics
Standard Graphics is the default Metasys graphics package used to design equipment and floor
plan graphics in scalable vector based format. The package comprises of two components, Graphics
Stencil Library (GSL) and User Graphics Tool (UGT).
GSL is a set of Visio Stencils, Templates, and add-ons (including Gzip, a compression utility), used
with Microsoft® Visio® Professional 2002 to create graphics for use in your Metasys system. The
graphic files created are imported in the User Graphics Tool (UGT), which has the ability to accept
a wide variety of image formats such as SVGs, SVGZs, or JPG files for background images which can
represent buildings, floor plans, mechanical equipment, and any other image that represents the
location or function of the equipment in the graphic. Within UGT, users can bind their graphics to
Metasys objects. Users can view Standard Graphics on the SMP user interface.

Integrations
BACnet/IP integration
BACnet/IP integration is possible with two Metasys equipment controllers, namely the FAC4911
controller and the VMA1930 controller. These controllers communicate on Ethernet IP networks and
support increased network performance, enabling faster access to data and faster troubleshooting.
Metasys BACnet/IP field controllers may be connected to your building automation network in
two ways. You can connect them as daisy-chained devices or as part of a star type network, which
is also called home run. You can also network the FAC4911 and VMA1930 controllers, which are
connected by Cisco® technology, in a ring Ethernet topology, which provides network reliability by
mitigating a single point of failure in the IP/Ethernet network. Most networks use combinations
of these topologies. For details, refer to the Metasys IP Networks for BACnet/IP Configuration Guide
Technical Bulletin (LIT-12012458).
BACnet/IP is also used to integrate the Simplex Fire System and lighting systems from preferred
partners into the Metasys system. For more information about these integrations, see Simplex Fire
system and Cree and Molex lighting systems, respectively.
MS/TP communications bus

The MS/TP bus is a local or remote network that connects network engines and equipment
controllers using the BACnet MS/TP protocol. Two tiers of MS/TP buses exist in the Metasys system
architecture. The Field Controller (FC) bus consists of BACnet controllers and point interfaces
supervised by a network engine. The Sensor Actuator (SA) bus consists of point interfaces and
networked sensors supervised by an equipment controller. To communicate with equipment
controllers on a remote MS/TP bus, you need a BACnet/IP to BACnet MS/TP router connected to
the building's IP network. The ODS Workstation is also compatible with the remote MS/TP bus. For
details, refer to the MS/TP Communications Bus Technical Bulletin (LIT-12011034).
N2 field bus
The N2 field bus is a local network that links controllers and point interfaces to some network
engines. The N2 bus uses a MS/TP protocol, in which the supervisory device (the network engine)
initiates the communication with the N2 bus devices.
N1 integration (Release 9.0 or earlier)

The N1 integration enables select models of network engines (NIE55, NIE85) to map point objects
of all or selected Network Control Module (NCM) devices on one or multiple existing Ethernet
N1 networks. The NIE to which an N1 object is mapped provides alarm and event management,
trending, energy management, and scheduling capabilities.
Note: Support for N1 integration ends at Release 9.0.
LonWorks
The LonWorks network is a local operating network that was developed by Echelon Corporation.
The network is built around the Neuron chip, a microprocessor that combines three CPUs into
one chip. The LonWorks network uses the LonTalk® protocol, a software language for field device
communication. This protocol uses the Open Systems Interconnect (OSI) reference model and
features all seven communication layers for interoperability among control devices.
Modbus
Modbus is one of the most common communication protocols used in the industry. It is openly
published and royalty-free, making it relatively easy to deploy for an industrial network. Modbus
transmits raw bits, or words without placing many restrictions on vendors. Metasys Network
engines support both Modbus RTU (RS-485, RS-232) and Modbus TCP/IP connectivity. The OAS uses

the default network interface and supports Modbus TCP/IP only. For more information, refer to the
Network Engine Commissioning for Modbus Vendor Integration Application Note (LIT-12013150).
M-Bus
M-Bus (Meter Bus) is a European standard (EN 13757-3) that applies to heat and electric meters.
These meters measure the heat absorbed or released by an energy-conveying liquid in a heat-
exchange circuit. An M-Bus level converter is necessary for an M-Bus integration. The converter
connects a network engine to an M-Bus network.
KNX
Use the KNX Bus to control lighting, blinds and shutters, heating, and attendance systems. KNX
(KONNEX) was created out of the EIB (European Installation Bus), BatiBUS, and EHS (European
Home System) protocols. You need a KNX IP Gateway to connect a network engine to a KNX
network.
C CURE 9000 Access Control

A vendor (VND) integration driver adds the ability for the Metasys system to provide data from the
C CURE 9000 Access Control system. You can use this data within Metasys to automate building
conditions when triggered by security badge and door events.
victor Video Management

A VND (Vendor) Integration driver adds the ability for the Metasys system to provide data from
victor Video Management systems. You can use this data within Metasys to automate building
conditions when triggered by events captured from video analytics.
Simplex Fire system

The Simplex Fire system includes a BACnet/IP integration, which facilitates the integration with
Metasys. The Metasys system serves as a secondary fire monitoring system that can alert more
people and automate building conditions when triggered by a fire event. The Metasys toolset is
enhanced to simplify the workflow for integrating a Simplex Fire system:
• The process of creating the Metasys Network, Equipment and Space integrations for SIMPLEX
Fire Panels is automated through an updated Mass Change Tool utility in SCT.
• There is a better representation of mapped fire system data in Metasys.
• The Metasys UI provides a detailed view of the fire system components, and the exact location
of the fire on the building and floor plan maps.
Cree and Molex lighting systems

Cree and Molex LED lighting and sensor networks are tightly integrated with Metasys. With this
integration, you can easily control the lights of an entire building, and you can automate lighting
adjustments to achieve healthy and efficient lighting conditions. You can coordinate lighting
behavior for signaling to occupants regarding critical scenarios in a building, such as fire, intruder
alert, lock-down, and code blue events.
Zettler Fire Panels

You can commission a Network Automation Engine (NAE), an SNE, or an SNC as a Vendor
Integration for use with Zettler fire panels, which integrates data sourced from Zettler Fire
Detection System into Metasys:
• Enables Metasys to automate building conditions when triggered by a fire event.

• Helps consolidate user experiences for building operators by enabling them to view fire
equipment, trouble points and status from Zettler Fire Detection System within Metasys UI.
• Enables Metasys to serve as a secondary fire notification system, alerting more occupants in
the event of a fire.
OPC Unified Architecture (UA)

OPC Unified Architecture (UA) is a machine-to-machine communication protocol popular with
industrial automation and process control type devices. At Release 11.0, network engines are
enhanced with an OPC UA integration driver. This new OPC UA integration driver enables Metasys
to monitor, command, schedule, alarm, trend, interlock, and share data with OPC UA devices.
This enhancement enables Metasys to provide integrated automation solutions for buildings and
market segments like Data Centers, manufacturing facilities, and others where OPC UA type devices
are popular.
Metasys system revision compatibility overview

This section describes high-level revision-to-revision compatibility scenarios for customer job sites
when you upgrade to Metasys Release 11.0. This section also contains some information about
previous release revision compatibility for existing sites that are at a previous release.
General compatibility information for customer job sites

SCT allows you to maintain Release 5.2, 6.x, 7.x, 8.x, 9.0, 10.0, 10.1, and 11.0 engines in the site's
archive.
The Site Director must be at an equal or higher revision to all the other servers and engines
on a site. The Product Development Test Lab validates the latest revisions of a Site Director with a
mix of Engines three revisions back. At Release 11.0, this includes Releases 10.1, 10.0, and 9.0.7.
The SCT no longer requires the same revision as the Site Director when integrated with the ADS/
ADX. If you install the ODS software, your SCT must be at Release 6.5 or later.
For sites installed with the Metasys UI, the Site Director server must be at Metasys Release 7.0 or
later. Sites using the Rapid Archive Creation feature of SCT 11.0 or later to quickly configure their
Metasys UI require the Site Director server to be at Release 8.0 or later.
Starting at Release 4.1, MS-NxE55-0 Engines can no longer be upgraded beyond Release 4.0. Sites
with -0 NxE55s upgraded to Release 4.0 are tested to coexist with the latest revision Site Director.
It may not be possible to edit Graphics or Logic Connector tool (LCT) processes in an Engine at
Revision 2.2 or earlier from a Site Director at Revision 3.0 or later. This is because the Scalable
Vector Graphic (SVG) rendering program was changed after Release 2.2. As a workaround, log in to
the Engine directly to make these edits.
Compatibility rules for CCT and field controller revisions

All revision-to-revision upgrade combinations for equipment controller/CCT applications are tested
in the Product Development Test Labs.
Starting at CCT Release 10.1, CCT is used to configure, simulate, and commission FACs, FECs,
VMA16s, and VMA18s on an N2 Bus. With CCT 10.1 or greater, you can open and commission an
application created with an earlier revision of CCT.
Equipment controllers running different firmware revisions can be mixed and matched on any
Engine with MS/TP Integration. This means that Release 5.3 based equipment controllers can be
added to a Release 4.0 NxE's MS/TP Integration. The only risk is that some enumerations that
were created in the 5.1 .caf may not display properly in the engineering view for the equipment
controller.

The CCT upgrade process works between major and minor revision levels (for example, CCT Release
10.0 to 10.1). CCT applications created during Alpha and Beta site releases (for example, 3.0.22 to
3.0.25) do not automatically upgrade.
The .caf files created by CCT are independent of the version of SQL Server (for example, a .caf file
created on a customer's machine running SQL Express) can be opened on a Branch laptop using
Microsoft SQL Server Data Engine (MSDE).
The DIS17 display was added at Release 3.0. To incorporate a display into an FEC installed at a
release prior to 3.0, you must:
• upgrade the .caf file to the current release

• open the display configuration application within CCT and select the desired points to display
• download main and boot code, then download the upgraded .caf file
Output Controller module upgrades

• Starting at Release 5.0, an Adaptive Tuning Reset Network Input was added. This feature is
created and connected only if you re-run System Selection. During the upgrade process, the
interface to the PID is created but is not connected.
• Starting at Release 5.0, the Adaptive Tuning logic is disabled when the Output point associated
with the Output Controller is overridden. This feature is created and connected only if you re-
run System Selection.
• Starting a Release 5.1, the following feature updates were made to all Output Controllers:
- General PID Process ID updates have been made to key tuning parameters and timer
settings per control loop type. These changes are updated from either an upgrade or
system selection.
- Fast Switching logic that bypasses saturation timers when zones need to quickly
transition from heating to cooling (for example, load changes in the space or setpoint
changes). This logic is only created from system selection.
- A new Lead Compensator block is automatically integrated into output controller
modules for zone control loops on water valves. This block acts as like an anticipator and
reduces the impact of the non-linearity of typical ball or globe valves. This is only created
from system selection.
- Updates to the default timer settings on Multi-Stage Controller (MSC) modules that
reduce cycling of stages while maintaining setpoint in both the occupied or unoccupied
modes. These timer settings are updated during system selection or manual updates of
the unoccupied duration timer.
• Starting at Release 5.1, updates to Output Controller Modules that contain PID and PID
preprocessor blocks are made even when the module has been user modified:
- Output Controllers utilized with Proportional Outputs are fully upgraded with the latest
logic and all the necessary internal connections.
- Output Controllers utilized with Staged/MSC Outputs are upgraded with the latest
primitives but the connections between the blocks are not made. Instead, the PID
primitive uses the default tuning parameters.
• Starting at Release 5.1, four exponentially weighted moving average (EWMA) parameters are
added automatically exposed during system selection to all the Output Controllers doing Zone
Control (VAV Boxes, Fan Coils, Unit Vents, and Heat Pumps).

Working with SCT Release 11.x or later at Metasys Release 8.x and later
SCT Release 11.x or later features new functionality to save time by simplifying the configuration
process for sites using the Metasys UI. SCT's most valuable enhancement, Rapid Archive Creation,
uses controller application files and templates to efficiently build site archives in a fraction of the
time from previous releases.
In addition to Rapid Archive Creation, SCT now permits spaces and equipment-only downloads and
auto-discovery of serving relationships for Metasys UI. The Downloading Only Metasys UI Spaces
and Equipment options allows sites to download Metasys UI spaces and equipment information
to your Release 7.0 or later server class device (ADS, ADX, or ADS-Lite) through the Manage Archive
Wizard. This new download feature is not intended to replace a full download to your server;
instead it offers a specific and simplified download for Metasys UI Offline configuration.
Auto-Discovery of Serving Relationships uses a matching algorithm to automatically populate
Serving and Served By columns in the Equipment Discovery window. Enhancements to the Find
and Replace functionality allow you increased control over Equipment Name and Equipment
Descriptions to aid in more accurate auto-discovery matches.
Equipment controller wireless integrations

The Wireless ZFR181x Series System was introduced at Metasys Release 4.0.
• Wireless coordinators need to be at an equal or higher revision level than the controllers
associated with it.
• Within a wireless mesh, a mix of revisions of wireless pairs is allowed.
• Each wireless controller and associated wireless router need to be at the same release. CCT
automatically syncs release revisions between a controller and its associated router.
• Release 4.0 controllers are not compatible with 4.1 or later wireless routers and need to be
updated before connecting the wireless router.
WNC1800/ZFR182x Pro Series Wireless Field Bus System

The WNC1800/ZFR182x Pro Series Wireless Field Bus System was introduced at Metasys Release 8.1.
The WNC1800/ZFR182x Pro Series Wireless Field Bus System uses different wireless coordinators,
routers, and repeaters than the ZFR1810 Series Wireless Field Bus System. You cannot intermix
WNC/ZFR Pro Series and older ZFR1810 Series wireless devices on the same wireless PAN. However,
you can intermix WNC/ZFR Pro and older ZFR1810 devices on separate PANs using separate
coordinators.
LCS85 compatibility
There are no known issues with the integration of the LCS85 to a Metasys Release 11.0 site.
Metasys system configuration examples

Multiple network engine system configuration with one network engine
designated as the Site Director
To extend the capabilities of your system, add one or more additional network engines. In Figure
7, one network engine designated as the Site Director provides the Site Management Portal to all
devices on the site. This configuration supports up to four simultaneous users.
Note:
• This configuration only provides long-term storage of data through the use of the
Metasys Export Utility installed on a computer.

• The NAE45-Lite can be partnered with other NAE45-Lite devices only. Additionally, the
NAE45-Lite requires an ADS-Lite-A Site Director, and both of these are available in specific
markets only.
• Similarly, the SNE110Lx can be partnered with other SNE110Lx type network engines only.
Additionally, the SNE110Lx requires an ADS-Lite-A Site Director, and both of these are
available in specific markets only.
Figure 7: Multiple network engine system configuration with one network engine designated
as the Site Director
Open Application Server (OAS) system configuration

The OAS combines the functions of a Network Engine with a Metasys Server.
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: Tyco C-Cure-victor, Modbus, M-Bus, and KNX, OPC Unified
Architecture (UA).
The OAS provides the Site Management Portal (SMP) and Metasys User Interface (Metasys UI).

Figure 8: OAS system diagram
Metasys Server Site Director with multiple network engines system

configuration
Sites that require more than four simultaneous users must add a Metasys Server (Figure 9). If
a large number of graphics are required to navigate through a site, the addition of the Metasys
Server allows access to a disk drive or network drive for graphic file storage. The Metasys Server
provides permanent storage of collected trend data samples, event messages, and audit trail
messages routed from the network engines.
Figure 9: Multiple network engines system configuration with Metasys Server Site Director
Metasys Server Site Director and secure NAE-S with unencrypted NAEs
Figure 10 shows a network that features a secure NAE-S network engine with other unencrypted
network engines reporting to a Metasys Server Site Director. For more details, refer to the NAE-S
Commissioning Guide (LIT-12012269).

Figure 10: Example network with encrypted and unencrypted NAEs
ADX unified or split configuration

The ADX software supports a unified or a split configuration. If the ADX and its accompanying SQL
Server database software is installed on one computer, it is known as a unified ADX. If the SQL
Server software is located on a different computer, it is known as a split ADX.
The ADX split configuration provides the ADX software/user interface on one computer (the web/
application server computer) and the alarm, audit, annotations, and historical trend data on
another computer with Microsoft SQL Server software (the database server computer). See Figure
11.

Figure 11: ADX split configuration
Figure 12 shows at a high level the difference between the unified and split ADX configurations.
Split ADX configurations are supported for 10-, 25-, 50-, or 100-user ADXs. For example, if you
require your database server to be separate from your application servers, you may want to use an
ADX split configuration.

Figure 12: Differences between unified and split ADX configurations
Unified and split ADX with dual network cards

A unified or split ADX system can use computers that have more than one network card. Other
Metasys software applications such as Metasys Export Utility, also support computers with multiple
network cards. The steps for configuring the cards are included with the software installation
instructions for the particular application. The following figure shows two examples of supported
network configurations.

Figure 13: Network examples with dual network cards
Large ADX site configuration

The ADX you select for a large site can be a 10-, 25-, 50-, or 100-user ADX. Refer to the Technical
Specifications section of the Application and Data Server (ADS) and Extended Application and
Data Server (ADX) Product Bulletin (LIT-1201525), Extended Application and Data Server System
Requirements (Unified ADX Systems, 50 or 100 Users) table for the technical specifications for a
large ADX system.
Note: Metasys for Validated Environments supports 5, 10, 25, and 50 users.
ODS workstation configurations

The three possible configurations for the ODS workstation are Site Manager workstation, BACnet
workstation, or the combined configuration of these two. The Site Manager configuration (Figure
14) is similar to an ADS or ADX. Web services facilitate communication with Metasys devices (for
example, NxEs), BACnet devices are connected through BACnet integration, and the ODS serves
as the Site Director. In the BACnet workstation configuration (Figure 15), the BACnet protocol
facilitates communication with Metasys and BACnet devices. NxEs, and FEC-family devices, mapped
through the BACnet integration, are treated the same as all other BACnet devices. In the combined
configuration (Figure 16), the strengths of the two configurations are available.

Figure 14: ODS Site Manager workstation configuration
Figure 15: ODS BACnet workstation configuration

Figure 16: ODS combined workstation configuration
BACnet/IP network system configuration

BACnet/IP devices are connected directly to the IP Ethernet network. The network engine
communicates with the devices using the BACnet protocol and presents the BACnet data to the
system in the same way as the other data in the Metasys system. Figure 17 shows the NAE35
network engine integrated into the Metasys network. Other BACnet/IP devices are integrated in the
same way.
Figure 17: BACnet/IP network integration system configuration
The NAE85 allows integration of larger BACnet integration projects.

Figure 18: NAE85 BACnet integration
Third-party network integration

The network engines offer seamless integration of Modbus, M-Bus, KNX, or other third-party
network to the Metasys system. Figure 19 shows the NAE45 and NCE25 controllers integrating third-
party devices. A KNX IP Gateway is also shown.
Figure 19: Third-party network integration

Wireless Metasys system configurations
Figure 20 shows various wireless Metasys system offerings, and how they coexist within the
Metasys system.
Figure 20: Wireless Metasys systems
Smoke Control application configuration

The following figure shows a configuration that complies with the UL 864 10th Edition UUKL/ORD-
C100-13 UUKLC Standard for Smoke Control System listing, incorporating smoke control and non-
smoke control systems. This configuration is only an example; the number and arrangement
of components in your system may differ. Ensure that your system complies with all device and
communication requirements and restrictions.

Figure 21: Metasys System UL 864 10th Edition UUKL/ORD-C100-13 UUKLC Standard for Smoke
Control
Performance guidelines and limitations

The following tables describe the recommendations and limitations of the various components of
the Metasys system.
Advanced Security Enabled attribute

This attribute provides an improved layer of security between Metasys Site Directors and devices.
With this attribute set to True, backward compatible methods of communication between the
Site Director and its network engines are disabled, which means a Site Director at Release 10.0 or
later discards all communication attempts from network engines prior to Release 10.0. This setting
applies to the entire site, so change this attribute to False if you have any network engines on the
site that are running a Metasys release prior to Release 10.0.
When you change this attribute to True, a user message appears to indicate that all network
engines prior to Release 10.0 remain online, but are disconnected from the site because they no
longer communicate with the Site Director. If this message appears, click OK to continue and set
the attribute to True, or Cancel to keep the attribute set to False.
Site Director limitations and recommendations

The following tables describe performance guidelines and limitations of the Metasys system Site
Directors.
Note: Upgrade the Site Director to Metasys Release 11.0 to take advantage of encrypted
communications. For best performance also upgrade the network engines to the newer
release. Network engines at Release 5.2 or later continue to work well with Release 11.0, but to
ensure best performance, upgrade engines to newer versions as soon as is practical.

Table 19: Engine Site Director limitations and recommendations
Maximum allowed Type of Site Director
NAE35 NAE45 NAE55 NAE85 NCE25
SNE1050x SNE1100x SNE2200x SNC
replacements of
1
NCE25
1
Total engines 3 3 4 4
2
1
2
Simultaneous SMP users 2 2 4 10 2
3
Objects in device 2,500 2,500 5,000 25,000 2,500
3
Objects within a single 300 300 700 700 300
folder
Dynamic values per
100
graphics
Results displayed in a
500
global search
Languages 1
Objects in entire system 3 million/ 750k (for ADX Site Director Only)
Characters in the name of 400
an object
Characters in the 64
description of an object
Nesting levels for object 7
creation
Extensions per object 10
Sets for third-party 1,000
BACnet states text
Characters for a third- 60
party BACnet states text
Members for a multi-value 500
third-party BACnet states
text
Non-Simultaneous SMP Limited only by memory capacity
users
SMP user views Limited only by memory capacity
Simultaneous browsers 2 (Mix of online, SCT, and Simulation)
per client computer
DLLR load extension Limited only by memory capacity. If you plan to attach a large number of load extensions to a
single DLLR object, consider the memory limitation. For load extensions attached to one DLLR
object, there is a 64 KB text limit for the list of the Loads fully qualified references. Load Limit
= (64 x 1024)/average number of characters per load. 1024 Bytes equals 1 KB. For example,
if your DLLR object is configured with Loads that have fully qualified references that average
100 characters (including dots) in length, then you can support approximately 650 loads (64 x
1024/100) for that DLLR. If you reach the memory limit, you may need to combine loads. For
example, if a site has multiple physical meters, split the meters across multiple controllers and
apply appropriate DLLR loads, if possible. Otherwise, use Interlock or Multiple Command objects
to reduce the number of loads added to the DLLR.
DLLR objects Limited only by memory capacity.
1 SNC25150-0, SNC25151-0, SNC25151-0H, SNC16120-0, SNC16121-0, and SNC16121-0H.
2 An NCE25 or SNC can only act as Site Director for itself.
3 Includes all points, extensions, graphics (background image), trend study, and other objects, such as schedules and
interlocks.

Table 20: Server Site Director limitations and recommendations
Maximum allowed Type of Site Director
ADS/ODS ADS-Lite-E
1
ADS-Lite-A
2
ADX ODS OAS
1
2
Desktop
Total engines 14
3
5
4
4
5
1,000
6
100 OASMIN: 0
3
4
5
6
OASSTD:
up to 2
Simultaneous SMP 5 5 5 10/25/ 5
7
5
users 50/100
7
7
Dynamic values per 100
graphics
Results displayed in 2,000
a global search
Languages 18
Objects in entire 3 million/ 750k (for ADX Site Director Only)
system
Objects in device
8
Limited by SQL Server storage capacity
8
Objects within a 700
single folder
name of an object
description of an
object
Nesting levels for 7
object creation
Extensions per 10
object
Sets for third-party 1,000
BACnet states text
Characters for a 60
third-party BACnet
states text
Members for a 500
multi-value third-
party BACnet states
text
Non-Simultaneous Limited only by memory capacity
SMP users
SMP user views Limited only by memory capacity
Simultaneous 2 (Mix of online, SCT, and Simulation)
browsers per client
computer
DLLR load extension Limited only by memory capacity. If you plan to attach a large number of load extensions to a single
DLLR object, consider the memory limitation. For load extensions attached to one DLLR object, there
is a 64 KB text limit for the list of the Loads fully qualified references. Load Limit = (64 x 1024)/average
number of characters per load. 1024 Bytes equals 1 KB. For example, if your DLLR object is configured
with Loads that have fully qualified references that average 100 characters (including dots) in length,
then you can support approximately 650 loads (64 x 1024/100) for that DLLR. If you reach the memory
limit, you may need to combine loads. For example, if a site has multiple physical meters, split the
meters across multiple controllers and apply appropriate DLLR loads, if possible. Otherwise, use
Interlock or Multiple Command objects to reduce the number of loads added to the DLLR.
DLLR objects Limited only by memory capacity.
1 The ADS-Lite-E cannot host servers.
2 The ADS-Lite-A cannot host servers.
3 Varies with concurrent connection.

4 Supports up to five of the following: SNE1100x, SNE1050x, SNC25150-0, SNC25151-0, SNC25151-0H, SNC25150-04,
SNC25151-04, SNC25151-04H, SNC16120-0, SNC16121-0, SNC16121-0H, SNC16120-04, SNC16121-04, SNC16121-04H,
NAE35, NAE45, NCE25, NIE29, NIE39, and NIE49.
5 Supports up to 3 NAE-Lite units plus up to 1 SNE110Lx, NIE29, NIE39, and NIE49.
6 Depends on computer hardware. To ensure best performance of sites with 100 or more engines use split configuration.
See the table Maximum number of network engines supported based on Metasys Server type and Server size for more
information.
7 Depends on version of ADX or ODS.
8 Includes all points, extensions, graphics (background image), trend study, and other objects, such as schedules and
interlocks.
Table 21: Maximum number of users supported on Metasys Server type Site Directors
Computer supported platform Site
Type of Metasys Management Metasys UI Users
Server Desktop Server Portal (SMP) (up to)
Users (up to)
ADS05U Yes - 5 5
1 2
OASSTD Yes Yes 5 5
1
2
1 2
OASMIN Yes Yes 5 5
ADX10U - Yes 10 25
ADX25U - Yes 25 25
ADX50U - Yes 50 50
ADX100U
3
- Yes 100 50
3
ODS 25,000
Yes Yes 5 Not Supported
Objects
1 Virtual Machine or Turnkey only.
2 Virtual Machine only.
3 Metasys for Validated Environments does not support the 100 user ADX.

Table 22: Maximum number of network engines supported based on Metasys Server type and
Server size
Site 1 to 14 1 to 25 1 to 50 1 to 100 1 to 300 1 to 1,000
Director engines engines engines engines engines engines
with
maximum
users
ADS05U ADS
ADX10U Small ADX Medium Medium/
ADX Large
ADX25U Small ADX Medium ADX
ADX
ADX50U Medium/ Large/ Extra Extra Large
Large Large ADX ADX
ADX100U
ADX
For ADS/ADX computer hardware requirements, refer to the Technical Specifications section of
the Application and Data Server (ADS) and Extended Application and Data Server (ADX) Product Bulletin
(LIT-1201525):
• For Unified ADS refer to Application and Data Server (ADS) system requirements (5 Users)
table.
• For small and small to medium Unified ADX refer to Extended Application and Data Server
system requirements (Unified ADX Systems, 10 or 25 Users) table.
• For medium to large Split ADX refer to Extended Application and Data Server system
requirements (Split ADX Systems, 10 or 25 Users) table.
• For medium to large and large Unified ADX refer to Extended Application and Data Server
system requirements (Unified ADX Systems, 50 or 100 Users) table.
• For large to extra large and extra large Split ADX refer to Extended Application and Data
Server system requirements (Split ADX System, 50 or 100 Users) table.
Network engine hardware limitations

The following table describes limitations of the Metasys system network engines.
Table 23: Network engine hardware limitations
Maximum allowed NCE25 NAE35 NAE45 NAE45-Lite NAE55 NAE85 OAS
ODS
Local Field Buses (FBs) 1 1 1 1 2 0 0
Remote Field Buses (RFBs) 0 3 4 0 6 or 7 16 16
Total Field Buses (Local and 1 (1 FB + 0 4 (1 FB + 3 5 (1 FB + 4 1 (1 FB + 0 8 (2 FB + 16 RFB only 16 RFB
Remote Field Buses) RFB) RFB) RFB) RFB) 6 RFB or 1 only
FB + 7 RFB)
MS/TP devices on FC Bus
1
Per trunk device limits if all devices are Metasys family devices, such as CGMs, CVMs, FACs,
1
FECs, VMAs, IOMs, and TEC3600s:
Note: N2 devices
follow the same rules 32 50 100 100 100 N/A N/A
as MS/TP devices, but Per trunk device limits if one device is a non-Metasys family device, such as a Facility Explorer
performance varies device, TEC2000, or third-party device:
based on controller
mix (N2Open/Sys91/ 32 50 64 64 64 N/A N/A
VMA).

Table 23: Network engine hardware limitations
Maximum allowed NCE25 NAE35 NAE45 NAE45-Lite NAE55 NAE85 OAS
ODS
Remote MS/TP devices on N/A 16 or 32 16 or 32 N/A 16 or 32 16 or 32 16 or 32
2
remote field bus
2
3
Mapped N2 points per trunk 2,500 2,500 2,500 N/A 2,500 N/A N/A
3
LonWorks devices
4
32 64 127 N/A 255 N/A N/A
4
Note: The LonWorks integration is only supported on NAE35s, NAE45s, and NCE25s with
the Metasys Release 9.0 software or earlier. The Release 9.0.7 and 9.0.8 patch updates
are not supported for these LonWorks models; they remain at Release 9.0. However, the
LonWorks integration is supported for NAE55s at Releases 10.0, 10.1, and 11.0.
LonWorks network variables 1,500 1,500 1,500 N/A 2,000 N/A N/A
Johnson Controls BACnet/ 50
5,6,7
50
5,6,7
50
5,6,7
50
5,6,7
200
5,6
NAE85: 1,000 200
5
6
7
IP devices and third-party Note:
BACnet/IP devices Before
11.0, the
NAE85
support
ed 200
devices.
ODS: 200
Objects 2,500 2,500 2,500 2,500 5,000 10,000 20,000
(default)
25,000
(upgrade)
Time on battery backup 1,024 seconds N/A N/A
1 Maximum 3 bus segments per FC Bus. Maximum 50 devices per bus segment. Bus segments on an FC bus are
connected with repeaters (only). Up to two cascaded repeaters may be applied to an FC bus (to connect three bus
segments).
2 The maximum device count is 32 if the bus contains all Johnson Controls devices, and 16 if the bus contains one or more
non-Johnson Controls devices.
3 Performance varies based on the point mix (N2 Open/Sys91/VMA). Recommend maximum for best performance is
1,000 points.
4 Single sub-net LonWorks network; does not support routers; supports physical repeaters
5 Depends on the number of objects each BACnet device supports.
6 Johnson Controls IP controllers only work with NAEs (and site directors) at Release 9.0 or later.
7 Some sites may require manual mapping based on system architecture. They may also require system adjustments,
such as BACnet communication adjustments, or firewall off.
See SNE Series Network Engines for details about SNE Series of Network Engines and see SNC
Series Network Control Engines for details about SNC Series of Network Control Engines.

Alarm and trending performance guidelines
Table 24: Alarm and trending performance guidelines
Description SNE/ NCE25/ NAE55 NAE85 ADS ADX OAS Comments
SNC NAE35/ ODS ODS
NAE45/ (Desktop) (Server)
Average 100 100 100 100 200 1,000 100 This number applies
maximum to alarms/events that
number originate from devices at
of alarms/ Release 5.2 or later.
events per
hour
Maximum 2,400 2,400 2,400 2,400 5,000 48,000 2,400 Within a 24-hour period.
number This number applies
of alarms/ to alarms/events that
events per originate from devices
day at Release 5.2 or later.
Supports one daily burst
of 25k alarms/events in
one hour.
Maximum 1,000 500 1,000 1,000 Limited by Limited Limited N/A
number SQL Server by SQL by SQL
of stored storage Server Server
alarms/ capacity storage storage
events capacity capacity
Average 1,500 1,500 1,500 1,500 22,500 100,000 1,500 This number applies
maximum to trend samples that
number originate from devices at
of trend Release 5.0 or later. The
samples per ADX supports one daily
hour burst of 300k trends in one
hour.
Maximum 36,000 36,000 36,000 36,000 540,000 2,400,000 36,000 Within a 24-hour period.
number This number applies to
of trend trend samples originating
samples per from devices at Release
day 5.0 or later.
Maximum Limited Limited Limited by 8,000,000 Limited Limited Limited N/A
number of by by memory only by SQL only only
stored trend memory memory usage storage by SQL by SQL
samples usage usage capacity storage storage
capacity capacity
Note: Alarms and trends from equipment controllers connected to any of these contribute to
the overall totals.
MS/TP performance guidelines

Table 25: MS/TP performance guidelines
Performance rating COV rate Token loop time
Low > 500 messages per minute > 3,000 ms
Between 400 and 500 messages
Medium Between 2,000 and 3,000 ms
per minute
High < 400 messages per minute < 2,000 ms

SCT limitations
Table 26: SCT limitations
Description Supported Comments
Max. number of simultaneous
1
users
Max. number of concurrently
10
active archives
Using supported Microsoft
SQL Server Express 2014 or
10 GB
Max. size of an active Microsoft SQL Server Express
database or project in SCT 2012 SP2
Using supported Microsoft SQL
No limit
Server Software
Equipment controller integration considerations

The CGM, CVM, FAC, and VMA1930 equipment controllers feature an integral real-time clock which
enables these equipment controllers to monitor and control schedules, calendars, alarms, and
trends. The local equipment controller trend, alarm, and event setup strategy should focus on
needs during a stand-alone commissioning session using CCT. The integration of an equipment
controller's trends, alarms, and events is governed by the network engine guidelines for trend and
alarm/event integrations.
The recommended limit threshold for trend samples for a network engine is 1,500 samples per
hour. The total number of trend samples forwarded from all equipment controllers integrated with
a network engine should not exceed this limit during the setup of the local equipment controller
trends.
The recommended limit threshold for alarm and event samples for a network engine is 100 events
per hour. The alarms that are set up in an equipment controller for use as BACnet Alarm extensions
in the network engine should be limited to only the points that normally are created as extensions
in the network engines. For consistency, the use of BACnet Alarm extensions instead of Metasys
Alarm extensions should also be considered when deciding whether the equipment controller's
BACnet Alarms should be enabled at the network.
In the following examples, we show acceptable limits with the following setups:
• 5 equipment controllers (CGM, CVM, FAC or VMA1930) with 6 alarms per hour plus 1 network
engine with 30 alarms per hour (Table 27)
• 5 equipment controllers (CGM, CVM, FAC or VMA1930) with 200 trend samples per hour plus 1
network engine with 500 trend samples per hour (Table 28)
• 5 equipment controllers (CGM, CVM, FAC or VMA1930) with 10 COVs per minute plus 35 FECs
with 10 COVs per minute (Table 29)
Table 27: Example 1
Setup Alarms per hour
5 equipment controllers with 6 alarms/hour
30 alarms per hour
each
1 network engine 30 alarms per hour
Total 60 alarms per hour

Table 28: Example 2
Setup Trend samples per hour
5 equipment controllers with 200 trend samples
1,000 trend samples per hour
per hour each
1 network engine 500 trend sample per hour
Total 1,500 trend samples per hour
Table 29: Example 3
Setup COVs per minute
5 CGMs, CVMs, FACs or VMA1930s with 10 COVs/
50 COVs per minute
minute
35 FECs with 10 COVs/minute 350 COVs per minute
Total 400 COVs per minute
For trend creations in the CGM, CVM, FAC, and VMA1930, the use of faster sample intervals of key
points provides a more intuitive troubleshooting interface in a CCT commissioning session via the
CCT's trend viewer. Setting up the trends for local use in CCT does not mean that the same points
and sample intervals have to be utilized in the network engine integration. The trends created in
an equipment controller do not have to be discovered and used by the network engines; separate
trends extensions can still be added at the network engine for any points that have equipment
controller-based trends created.
Transfer to device (download) limitations

Regarding transfer to device limitations, there is no difference between specific models of
equipment controllers (CGM, CVM, FAC, FEC, VMA), but the firmware and communication types
(BACnet MS/TP, N2, IP) matter.
The following transfer to device limitations apply:
• NxE Passthru is not supported for Transfer to Device (Download) for controllers using
firmware 7.0 or later when going through an engine at Release 8.1 or earlier. However,
NxE Passthru through an engine at Release 9.0 or later works for any Metasys equipment
controller.
• NxE Passthru is not supported for N2 devices, because an SA Bus connection is required in the
tool to communicate with an N2 controller.
• The MAP 4.2+ and BACnet Router methods work for any device.
• A Bluetooth or ZigBee Transfer to Device (Download) is supported for devices using 6.2
firmware or older. Bluetooth and ZigBee are not supported for Transfer to Device (Download)
for controllers using firmware 7.0 or later, such as IP controllers, the M4-CGM, and the M4-
CVM equipment controllers. CCT 14.0 does not work with the BTCVT Bluetooth Commissioning
Converter.
• Direct Ethernet works for any IP device.
Note: All transfers with SNC Local Applications are done through SCT Manage Archive, never
with CCT transfers.
The following table summarizes the transfer to device limitations.

Table 30: Transfer methods supported by device type and firmware
Supported CCT connection method
Note: The BTCVT Bluetooth Commissioning Converter is no longer
available (no longer in production), and is no longer a supported
connection method at Metasys Release 11.0.
Controller type NxE NxE MAP 4.2+/ Bluetooth ZigBee Direct
Passthru Passthru BACnet (BTCVT) Ethernet
- Engine - Engine Router
at 8.1 or at 9.0
earlier or later
BACnet MS/TP
controllers using 6.2 X X X X X
firmware or earlier
BACnet MS/TP
controllers using 7.0 X X
firmware or later
N2 controllers using
6.2 firmware or X X X
earlier
1
1
N2 controllers using
X
8.0 firmware or later
BACnet/IP
controllers using 7.0 X X X
firmware or later
1 Connecting through the SA Bus is required.
For further details refer to the Troubleshooting section in the Controller Tool Help (LIT-12011147).
Technical specifications and requirements

Hardware configuration requirements
Our suggested minimum hardware configuration is based on experience and testing for both client
and server platforms. These configurations are only suggestions and are not meant to imply that
older or slower machines are not usable.
Systems with less memory, smaller hard disks, or systems that are generally slower, may have
acceptable performance for basic operations. These systems may also be acceptable when not
called upon to operate simultaneous tasks that require hardware or network resources. Memory-
intensive applications may require additional memory for proper performance. Examples of these
optional or advanced features of the Metasys system include navigation and support for complex
graphics, operation with the maximum number of users, complex and extended queries with the
Metasys Export Utility, support for large network integrations, and large numbers of concurrent
open windows.
When deciding on computer hardware, consider the following important factors:
• Overall system performance is highly dependent on the total amount of available computer
RAM. If you experience performance issues with the ADS or ADX, increase the total amount of
RAM.

• For improved performance, consider Serial Attached SCSI (SAS) hard drives over Serial AT
Attachment (SATA) hard drives.
• Be sure to enable the write cache feature on the disk controller.
• Dell and HP are the preferred computer manufacturers. They offer machines that match the
hardware recommendations listed in this document.
• Do not enable power saving modes on the ADS or ADX computer. Such modes automatically
turn off disk drives and network cards, thereby adversely affecting proper Metasys system
operation.
• Remember to obtain Windows operating system Client Access Licenses (CALs) for the total
number of users and devices on your system. Refer to the Network and IT Guidance Technical
Bulletin (LIT-12011279) for more information on CALs.
Client computer requirements for UI client devices

The following table describes the recommended and minimum computer requirements for the
computer used for Site Management Portal, SCT, and Metasys UI access.
Table 31: Client computer requirements for Site Management Portal UI, SCT, Metasys UI, and
Metasys UI Offline
Site Management Portal UI Metasys UI
System Configuration Tool (SCT) Metasys UI Offline
Recommended processor
1
Intel® Core™ i5 Processor Intel® Core™ i5 Processor
1
Recommended Random 8 GB (4 GB minimum) 8 GB (1 GB minimum)
Access Memory (RAM) Note: If you use graphics intensively, you may experience better computer
performance with additional RAM.
Hard disk capacity 40 GB hard disk (minimum) 40 GB hard disk (minimum)

Metasys UI Offline
Supported operating SMP Metasys UI and Metasys UI Offline
systems Windows® 10 Pro and Windows 10 Enterprise Windows® 10 Pro and Windows 10 Enterprise
Editions versions 1903, 1909, and 2004 (64-
Editions versions 1903, 1909, and 2004 (64-bit).
bit). For all future Windows 10 updates after
version 2004, we will evaluate and certify that For all future Windows 10 updates after version
Metasys software can support the updates 2004, we will evaluate and certify that Metasys
before we provide guidance on support. software can support the updates before we
provide guidance on support.
Windows® 8.1 Pro and Windows 8.1
Enterprise Editions with Update (KB2919355)
(64-bit) Windows® 8.1 Pro and Windows 8.1 Enterprise
Editions with Update (KB2919355) (64-bit)
Windows® 7 Professional, Enterprise, and
Ultimate Editions with SP1 (64-bit)
Windows® 7 Professional, Enterprise, and
SCT and SCT Pro Ultimate Editions with SP1 (64-bit)
Windows® 10 Pro and Windows 10 Enterprise
Editions versions 1903, 1909, and 2004 (64-
bit). For all future Windows 10 updates after Apple® macOS® 10.15 Catalina
version 2004, we will evaluate and certify that Apple® macOS® 10.14 Mojave
Metasys software can support the updates
Apple® macOS® 10.13 High Sierra
before we provide guidance on support.
Apple® macOS® 10.12 Sierra
Windows® 8.1 Pro and Windows 8.1
Enterprise Editions with Update (KB2919355)
(64-bit)
Windows® Server® 2019 (version 1803 or

later) (64-bit)
Windows® Server® 2016 with Update

(KB4512495) (64-bit)
Supported web browsers Google® Chrome™ version 78 or later Microsoft® Edge® version 44 or later
Microsoft® Edge® version 44 or later Google® Chrome™ version 78 or later

3
3
2
Apple® Safari® 11 or later
2
4
4
Other web browsers, such as Mozilla® Firefox®,
are not officially supported by the UI. However,
the Metasys UI may appear and function
appropriately in these web browsers.
Supported mobile phone N/A Android phone 5.1 or later
operating systems iPhone iOS 11.4.1 or later

Metasys UI Offline
Supported tablet operating N/A Android tablet 5.1 or later
systems iPad iOS 11.4.1 or later
Network communication Ethernet network interface card 10/100/1000 Ethernet network interface card 10/100/1000
Mbps Mbps
Follow these guidelines and recommendations:
• For optimal performance, use a wired
connection for computers browsing to
the Metasys UI.
• Alternatively, for mobile phones and
tablets, you can use a wireless IEEE
802.11 connection on a 4G network.
Browsing to the Metasys UI over a 3G
communications network is possible, but
it is not recommended or supported.
• High latency (also called lag or wait time)
can cause the Metasys UI to disconnect
from the ADS or ADX.
• To avoid high latency, we recommend a
network with 20 mpbs upload speed.
• Signal strength impacts the overall
performance of the Metasys UI. For the
best results, ensure you have a strong
signal for your wireless connection.
Monitor 1024 x 768 or higher resolution and 16-bit or 1024 x 768 or higher resolution and 16-bit or
higher color depth higher color depth
Other features may require 1600 x 900
resolution. Additionally, you may need to set
your monitor display at Small 100% setting
(Control Panel > All Control Panel Items >
Display).
1 Our computer platform and memory recommendations are not meant to imply that older or slower machines are not
usable. Refer to the Network and IT Guidance Technical Bulletin (LIT-12011279) for more information regarding computer/
server recommendations.
2 In macOS, you cannot view Graphics+ graphics in the Site Management Portal UI. You use the web browser to download
the Launcher application. After you install the Launcher application, you use the Launcher, not the web browser, to log
in to the Site Management Portal (SMP) UI.
3 Metasys UI does not support incognito mode. To exit incognito mode, click or tap the X icon of the browser window
or tab and then open a new browser window or tab. For more information on incognito mode in Google Chrome, click
here.
4 Metasys UI does not support private browsing. To exit private browsing, click or tap Private in the browser window.

Application and Data Server (ADS) system requirements
Table 32: Application and Data Server (ADS) system requirements (5 Users)
Recommended Computer Intel i7 processor latest version with at least four cores or
Platform
1
1
better
2
2 x 500 GB hard disk (RAID 1) with 40 GB free space after
2
installation of all prerequisite software and before installation
of ADS software. Configure RAID 1 (mirroring) with disk
write-caching turned on.
Note: Prerequisite software includes the supported

operating system, database software, .NET Framework,
and any other software or service packs required for
your ADS configuration.
Graphics card (1 GB RAM, ATI® Technologies or NVIDIA®
Corporation, 64-bit compatible, Small Form Factor [SFF] if
required)
Required Minimum Memory
3
16 GB RAM
3
The VM host must have at least 8 GB of allocated RAM at all
time. When you configure the VM, do not select the enable
dynamic memory option.
Number of engines supported Up to 14
Number of Site Management
Up to five
Portal users supported
Number of Metasys UI users
Up to five
supported

Supported Operating Systems
4
Windows® 10 Pro and Windows 10 Enterprise Editions
4
and Database Software versions 1903, 1909, and 2004 (64-bit). For all future Windows
10 updates after version 2004, we will evaluate and certify
that Metasys software can support the updates before we
Supports:
• SQL Server® 2019 Express (64-bit)
Note: SQL Server 2019 may cause the configuration
service cache that builds stored procedures to time
out. This causes the user's log in to Metasys UI to
fail. To resolve this issue, set SQL Server 2019 to run
in 2017 compatibility mode. For more information,
refer to docs.microsoft.com
• SQL Server® 2017 Express with CU17 (64-bit)
• SQL Server® 2016 Express with SP2 CU10 (64-bit)
Windows® 8.1 Pro and Windows 8.1 Enterprise Editions with
Update (KB2919355) (64-bit)
Supports:
Supported Operating Systems for Windows® 10 Pro and Windows 10 Enterprise Editions
Metasys Site Management Portal versions 1903, 1909, and 2004 (64-bit). For all future Windows
Client Computer 10 updates after version 2004, we will evaluate and certify
that Metasys software can support the updates before we

Apple® macOS® 10.15 Catalina

Apple® macOS® 10.14 Mojave
Supported Web Browser Apple® Safari® 11 or later
Software for Metasys Site Notes:
Management Portal Client
• In OS X, you cannot view Graphics+ graphics in the
Computers
Site Management Portal UI.
• You use the web browser to download the
Launcher application. After you install the Launcher
application, you use the Launcher, not the web
browser, to log in to the Site Management Portal
(SMP) UI.

Supported Web Browser Microsoft® Edge® version 44 or later
Software for Metasys UI Client
Devices Google® Chrome™ version 78 or later
Note: Metasys UI does not support incognito mode.
To exit incognito mode, click or tap the X icon of the
browser window or tab and then open a new browser
window or tab. For more information on incognito mode
in Google Chrome, click here.

Note: Metasys UI does not support private browsing. To
exit private browsing, click or tap Private in the browser
window. Other web browsers, such as Mozilla® Firefox®,
are not officially supported by the UI. However, the
Metasys UI may appear and function appropriately in
these web browsers.
Supported Virtual Environments Microsoft Hyper-V™
VMware®
Supported User Interfaces Site Management Portal (SMP)
Metasys UI
Additional Software Included Launcher software, Network Engine images, Summary
with the ADS Software Download Definition Examples, Microsoft .NET Framework (multiple
versions), SQL Server Management Studio, Metasys Database
Manager, Toggletunnel, SNMP Management Information
Base example files (MIBs), Report Viewer 2010 and Report
Viewer 2012.
Optional Hardware Any network or local printer supported by the qualified
Windows operating system
Optional Software Graphic Generation Tool
CCT software
SCT software
Metasys Export Utility software

2 For best performance, use Serial Attached SCSI (SAS) hard drives, not Small Computer System Interface (SCSI) hard
drives.
3 For best performance, use the maximum amount of memory that the computer allows.
4 Refer to the Network and IT Guidance Technical Bulletin (LIT-12011279) for specific Microsoft Windows operating system
settings that may be required for your Metasys system configuration.
Extended Application and Data Server system requirements

(Unified 10 or 25 User ADX)
Use the following recommendations for small sites and small to medium sites.

Table 33: Extended Application and Data Server system requirements (Unified ADX Systems,
10 or 25 Users)
Recommended Server Processor for small sites: Intel® Xeon® Gold 5222 3.8 GHz, 4 cores/8
Platform
1
threads, 10.4GT/s, 16.5M Cache, Turbo, HT (105W) DDR4-2933 or
1
Intel® Xeon® Gold 6244 3.6 GHz, 8 cores/16 threads, 10.4GT/s, 24.75M
Cache, Turbo, HT (150W) DDR4-2933
Processor for small to medium sites: Intel® Xeon® Gold 5222 3.8
GHz, 4 cores/8 threads, 10.4GT/s, 16.5M Cache, Turbo, HT (105W)
DDR4-2933 and recommended second processor type is Intel® Xeon®
Gold 5222 3.8 GHz, 4 cores/8 threads, 10.4GT/s, 16.5M Cache, Turbo,
HT (105W) DDR4-2933
Hard drive: 2 x 960 GB SSD SATA Mix Use 6Gbps 512 2.5in Hot-
2
plug Drive (RAID 1) with 40 GB free space after installation of all
2
prerequisite software and before installation of ADS software.
Configure RAID 1 (mirroring) with disk write-caching turned on.
Note: ADX prerequisite software includes the Windows

operating system, SQL Server software, Windows .NET
Framework, and any other software or SPs required by your ADX
configuration.
Required Minimum 32 GB RDIMM, 2933MT/s, Dual Rank
3
Memory
3
The VM host must have at least 8 GB of allocated RAM at all time.
When you configure the VM, do not select the enable dynamic
memory option.
Number of engines For small sites: Up to 25
supported
For small to medium sites: Up to 50
Number of Site For small sites: Up to 10
Management Portal
users supported For small to medium sites: Up to 10
Number of Metasys UI For small sites: Up to 15
users supported
For small to medium sites: Up to 25

10 or 25 Users)
Supported Operating Windows® Server® 2019 (version 1803 or later) (64-bit)
4
Systems and Database
4
Supports:
Software
• SQL Server® 2019 (64-bit)
Note: SQL Server 2019 may cause the configuration service
cache that builds stored procedures to time out. This causes
the user's log in to Metasys UI to fail. To resolve this issue,
set SQL Server 2019 to run in 2017 compatibility mode. For
more information, refer to docs.microsoft.com
• SQL Server® 2017 with CU17 (64-bit)
• SQL Server® 2016 with SP2 CU10 (64-bit)
Windows® Server® 2016 with Update (KB4512495) (64-bit)
Supports:
Supported Operating Windows® 10 Pro and Windows 10 Enterprise Editions versions 1903,
Systems for Metasys 1909, and 2004 (64-bit). For all future Windows 10 updates after
Site Management Portal version 2004, we will evaluate and certify that Metasys software can
Client Computer support the updates before we provide guidance on support.
Windows® 8.1 Pro and Windows 8.1 Enterprise Editions with Update
(KB2919355) (64-bit)


10 or 25 Users)
Software for Metasys Notes:
Site Management Portal
Client Computers
• In OS X, you cannot view Graphics+ graphics in the Site
Management Portal UI.
• You use the web browser to download the Launcher
application. After you install the Launcher application, you
use the Launcher, not the web browser, to log in to the Site
Management Portal (SMP) UI.

Software for Metasys UI
Client Devices Google® Chrome™ version 78 or later
Note: Metasys UI does not support incognito mode. To exit
incognito mode, click or tap the X icon of the browser window
or tab and then open a new browser window or tab. For more
information on incognito mode in Google Chrome, click here.

Note: Metasys UI does not support private browsing. To exit
private browsing, click or tap Private in the browser window.
Other web browsers, such as Mozilla® Firefox®, are not officially
supported by the UI. However, the Metasys UI may appear and
function appropriately in these web browsers.
Supported Virtual Microsoft Hyper-V™
Environments
VMware®
Supported User Site Management Portal (SMP)
Interfaces
Metasys UI

10 or 25 Users)
Additional Software SQL Server® 2017 Express with CU17 (64-bit)
Included with the ADX Microsoft .NET Framework 4.7.2
Software Download Launcher Software
Metasys Database Manager software
Metasys Advanced Reporting System software
Note: The Metasys Advanced Reporting System requires an ADX.

The SCT computer must be online and accessible to the ADX at
all times.
Optional Hardware Any network or local printer supported by the qualified Windows
operating system
Optional Software Energy Essentials
5
5
Graphic Generation Tool
CCT Software
SCT Software
Metasys Export Utility

2 For best performance, use SSD (preferred) or SAS hard drives (not SATA hard drives) that use RAID controllers with
write-caching enabled.
3 For best performance, use the maximum amount of memory. An ADX with 32 GB RAM has much greater performance
than an ADX with only 16 GB RAM.
5 SQL Server 2017 has a separate installation for SSRS. For more information, refer to the SQL Server Update and
Installation Guide (LIT-12012240)
For SQL Server software, you must purchase SQL Server software licenses per the guidelines listed
here: SQL Server 2019, SQL Server 2017, SQL Server 2016, and SQL Server 2014.

(Split 10 or 25 User ADX)
Use the following recommendations for medium to large sites.

Table 34: Extended Application and Data Server system requirements (Split ADX Systems, 10
or 25 Users)
Recommended Server Web/Application Server
1
Platform
1
Intel® Xeon® Gold 5222 3.8GHz, 4 cores/8 threads, 10.4GT/s, 16.5M
Cache, Turbo, HT (105W) DDR4-2933 and the recommended second
processor type is Intel® Xeon® Gold 5222 3.8GHz, 4 cores/8 threads,
10.4GT/s, 16.5M Cache, Turbo, HT (105W) DDR4-2933
2
2 x 960GB SSD SATA Mix Use 6Gbps 512 2.5in Hot-plug Drive (RAID 1)
2
3
with 50 GB free space after installation of all prerequisite software
3
and before installation of ADS software. Configure RAID 1 (mirroring)
with disk write-caching turned on
Notes:
• Metasys Advanced Reporting System and Energy Essentials
must reside on the ADX web/application server.
• Metasys UI must reside on the ADX web/application server.
Database Server
Intel® Xeon® Gold 5222 3.8GHz, 4 cores/8 threads, 10.4GT/s, 16.5M

Cache, Turbo, HT (105W) DDR4-2933 and the recommended second
processor type is Intel® Xeon® Gold 5222 3.8GHz, 4 cores/8 threads,
2 x 960GB SSD SATA Mix Use 6Gbps 512 2.5in Hot-plug Drive (RAID 1)
2 3
with 50 GB free space after installation of all prerequisite software
and before installation of ADS software. Configure RAID 1 (mirroring)
with disk write-caching turned on
SCT Computer
In a split configuration, you cannot install SCT on either the ADX web/
application server computer or the ADX database server computer.
Refer to the System Configuration Tool Catalog Page (LIT-1900198) for
current SCT computer requirements.
Required Minimum 64 GB RDIMM, 2933MT/s, Dual Rank (web/application server and
Memory
4
database server for 10 or 25 user ADX)
4
memory option.
Number of engines Up to 100
supported
Note: To ensure best performance of sites with 100 or more
engines use split configuration.
Number of Site Up to 25
Management Portal
users supported
Number of Metasys UI Up to 50
users supported

or 25 Users)
5,6
Systems with
5
6
Supports:
Supported Database
Software • SQL Server® 2019 (64-bit)
Supports:
(KB2919355) (64-bit)


or 25 Users)
Client Computers

Note: Metasys UI does not support private browsing. To exit

Environments
VMware®
Interfaces
Metasys UI

or 25 Users)
Included with the ADX
Software Download Microsoft .NET Framework 4.7.2
Launcher Software

all times.
operating system
7
7
CCT Software
SCT Software

3 ADX prerequisite software includes the Windows operating system and SQL Server software, Windows .NET Framework,
and any other software or service packs required for your ADX configuration.
4 For best performance, use the maximum amount of memory.
5 The web/application and database servers must have the same operating system installed.

(Unified 50 or 100 User ADX)
Use the following recommendations for medium to large sites and large sites.

50 or 100 Users)
Recommended Server Processor for medium to large sites: Intel® Xeon®Gold 5222
Platform
1
3.8GHz, 4 cores/8 threads, 10.4GT/s, 16.5M Cache, Turbo, HT (105W)
1
DDR4-2933 and the recommended second processor type is Intel®
Xeon® Gold 5222 3.8GHz, 4 cores/8 threads, 10.4GT/s, 16.5M Cache,
Turbo, HT (105W) DDR4-2933
Processor for large sites: Intel® Xeon® Gold 6244 3.6GHz, 8 cores/16
threads, 10.4GT/s, 24.75M Cache, Turbo, HT (150W) DDR4-2933 and
the recommended second processor type is Intel® Xeon® Gold 5222
3.8GHz, 4 cores/8 threads, 10.4GT/s, 16.5M Cache, Turbo, HT (105W)
DDR4-2933
Hard drive for medium to large sites: 2 x 960GB SSD SATA Mix Use
2
6Gbps 512 2.5in Hot-plug Drive (RAID 1) with 50 GB free space after
2
installation of all prerequisite software and before installation of ADS
software. Configure RAID 1 (mirroring) with disk write-caching turned
on
Hard drive for large sites: 2 x 960GB SSD SAS Mixed use 12Gbps
2
512e 2.5in Hot-Plug PM5-V Drive, 3 DWPD, 5256 TBW (RAID 1) with 50
GB free space after installation of all prerequisite software and before
installation of ADS software. Configure RAID 1 (mirroring) with disk
write-caching turned on
PERC H730P RAID Controller, 2GB NV Cache, Minicard

Note: ADX prerequisite software includes the Windows
operating system, SQL Server software, Windows .NET
Framework, and any other software or SPs required by your ADX
configuration.
Required Minimum 64 GB RDIMM, 2933MT/s, Dual Rank
Memory
3
3
memory option.
Number of engines For medium to large sites: Up to 100
supported
For large sites: Up to 100

Number of Site For medium to large sites: Up to 25
Management Portal
users supported For large sites: Up to 50
Number of Metasys UI For medium to large sites: Up to 50
users supported
For large sites: Up to 50

50 or 100 Users)
4
Systems and Database
4
Supports:
Software
Supports:
(KB2919355) (64-bit)

Client Computers

50 or 100 Users)

Note:
Metasys UI does not support private browsing. To exit private
browsing, click or tap Private in the browser window.

Environments
VMware®
Interfaces
Metasys UI
Included with the ADX Microsoft .NET Framework 4.7.2
Software Download Launcher Software

all times.
operating system
5
5
CCT Software
SCT Software



(Split 50 or 100 User ADX)
Use the following recommendations for large to extra large sites and for extra large sites.

Table 36: Extended Application and Data Server system requirements (Split ADX System, 50 or
100 Users)
Recommended Server Web/Application Server
Platform
1
1
Processor for large to extra large sites: Intel® Xeon® Gold
6244 3.6GHz, 8 cores/16 threads, 10.4GT/s, 24.75M Cache, Turbo,
HT (150W) DDR4-2933 and the recommended second processor
type is Intel® Xeon® Gold 6244 3.6GHz, 8 cores/16 threads,
Processor for extra large sites: Intel® Xeon® Gold 6136 3.0GHz,
12 cores/24 threads, 10.4GT/s, 24.75M Cache, Turbo, HT (150W)
DDR4-2666 and the recommended second processor type is
Intel® Xeon® Gold 6136 3.0GHz, 12 cores/24 threads, 10.4GT/s,
24.75M Cache, Turbo, HT (150W) DDR4-2666
Hard drive for large to extra large sites: 960GB SSD SAS Mixed
use 12Gbps 512e 2.5in Hot-Plug PM5-V Drive, 3 DWPD, 5256
2
TBW (RAID 5) with 50 GB free space after installation of all
2
3
3
Configure RAID 5 with disk write-caching turned on. Use a
minimum of three hard drives for RAID 5 or a minimum of four
hard drives for RAID 10.
Hard drive for extra large sites: 960GB SSD SAS Mixed
2
3
Configure RAID 5 with disk write-caching turned on. Use a
Notes:
• Metasys Advanced Reporting System and Energy
Essentials must reside on the ADX web/application
server.
• Metasys UI must reside on the ADX web/application
server.

100 Users)
Recommended Server Database Server
Platform
Processor for large to extra large sites: Intel® Xeon® Gold
6244 3.6GHz, 8 cores/16 threads, 10.4GT/s, 24.75M Cache, Turbo,
HT (150W) DDR4-2933 and the recommended second processor
type is Intel® Xeon® Gold 6244 3.6GHz, 8 cores/16 threads,
Processor for extra large sites: Intel® Xeon® Gold 6136 3.0GHz,
12 cores/24 threads, 10.4GT/s, 24.75M Cache, Turbo, HT (150W)
DDR4-2666 and the recommended second processor type is
Intel® Xeon® Gold 6136 3.0GHz, 12 cores/24 threads, 10.4GT/s,
24.75M Cache, Turbo, HT (150W) DDR4-2666
Hard drive for large to extra large sites: 960GB SSD SAS Mixed
2
3
Configure RAID 5 with disk write-caching turned on.. Use a
Hard drive for extra large sites: 960GB SSD SAS Mixed
2
3
Configure RAID 5 with disk write-caching turned on.. Use a

Recommended Server SCT Computer
Platform
In a split configuration, you cannot install SCT on either the ADX
web/application server computer or the ADX database server
computer. Refer to the System Configuration Tool Catalog Page
(LIT-1900198) for current SCT computer requirements.
4
For large to extra large sites: 64 GB RDIMM, 2933MT/s, Dual
4
Rank
For extra large sites: 64 to 128 GB RDIMM, 2933MT/s, Dual Rank

memory option.

100 Users)
Number of engines supported For large to extra large sites: Up to 300
For extra large sites: Up to 1,000

Number of Site Management For large to extra large sites: Up to 50
Portal users supported For extra large sites:
Up to 100
Number of Metasys UI users For large to extra large sites: Up to 50
supported
For extra large sites: Up to 50
Supported Operating Systems Windows® Server® 2019 (version 1803 or later) (64-bit)
5,6
and Database Software
5
6
Supports:
out. This causes the user's log in to Metasys UI to fail.
To resolve this issue, set SQL Server 2019 to run in 2017
compatibility mode. For more information, refer to
docs.microsoft.com
Supports:
out. This causes the user's log in to Metasys UI to fail.
To resolve this issue, set SQL Server 2019 to run in 2017
compatibility mode. For more information, refer to
docs.microsoft.com

100 Users)
Supported Operating Systems Windows® 10 Pro and Windows 10 Enterprise Editions versions
for Metasys Site Management 1903, 1909, and 2004 (64-bit). For all future Windows 10 updates
Portal Client Computer after version 2004, we will evaluate and certify that Metasys
software can support the updates before we provide guidance
on support.



Software for Metasys Site Notes:
Management Portal Client
Computers
application. After you install the Launcher application,
you use the Launcher, not the web browser, to log in to
the Site Management Portal (SMP) UI.

Note: Metasys UI does not support incognito mode. To
exit incognito mode, click or tap the X icon of the browser
window or tab and then open a new browser window or tab.
For more information on incognito mode in Google Chrome,
click here.
Note: Metasys UI does not support private browsing. To

exit private browsing, click or tap Private in the browser
window. Other web browsers, such as Mozilla® Firefox®,
are not officially supported by the UI. However, the Metasys
UI may appear and function appropriately in these web
browsers.
Environments
VMware®
Metasys UI

100 Users)
Additional Software Included SQL Server® 2017 Express with CU17 (64-bit)
with the ADX Software
Download Microsoft .NET Framework 4.7.2
Launcher Software
Note: The Metasys Advanced Reporting System requires an

ADX. The SCT computer must be online and accessible to
the ADX at all times.
operating system
7
7
CCT Software
SCT Software

3 ADX prerequisite software includes the Windows operating system and SQL Server software, Windows .NET Framework,
and any other software or service packs required for your ADX configuration.
5 The web/application and database servers must have the same operating system installed.
OAS technical specifications

The OAS Turnkey has the following specifications:
Table 37: OAS Turnkey hardware and software specifications
Processor Intel® Atom® E3900
Operating system Windows 10 LTSB version 1607
Database software SQL Server® 2017 Express with CU17 (64-bit)
Memory 8 GB
Power input 12-24 VDC input

Table 37: OAS Turnkey hardware and software specifications
RS-232-C serial ports 1
USB serial ports
1
4 x USB 3.0 ports
1
Ethernet ports
1
2
Wireless card
1
M.2
Storage 128 GB eMMC
1 Although the USB ports are active on the OAS Turnkey hardware, the OAS does not support using them as an
integration method. For example, you cannot connect a trunk of field devices using the USB port. You must use a
remote field bus or BACnet/IP field devices.
Note: The OAS Turnkey does not meet the minimum requirements to run the fault detection
and fault triage features.
If you install the OAS on a virtual machine, review the following table to verify that you meet the
minimum hardware and software requirements.

Table 38: OAS application hardware and software requirements
Intel Core i7-8700 Processor, Six Cores, 3.20 GHz
or better
Note: Match the specs of the ADS/ADX

recommendations that correspond to the site
characteristics. For example, the number of
users, the number of engines and objects,
and site traffic. If you host the OAS on a
virtual machine, match the recommendations
Recommended computer platform listed in the Network and IT Guidance Technical
Bulletin (LIT-12011279).
128 GB hard disk with 40 GB free space after
you install all prerequisite software and before
installation of OAS software. Configure RAID 1
(mirroring) with disk write caching enabled
Note: Prerequisite software includes the

supported operating system, database
software, and .NET Framework.
Minimum: 8 GB
Note: The VM host must have at least 8 GB

Memory
1
1
of allocated RAM at all times. When you
configure the VM, do not select the enable
dynamic memory option.
Windows® 10 Pro and Windows 10 Enterprise
Editions versions 1903, 1909, and 2004 (64-bit).
For all future Windows 10 updates after version
2004, we will evaluate and certify that Metasys
software can support the updates before we
Windows® 8.1 Pro and Windows 8.1 Enterprise

Supported desktop operating systems and Editions with Update (KB2919355) (64-bit)
database software
Supports:

• SQL Server® 2016 Express with SP2 CU10 (64-
bit)
• SQL Server® 2014 Express with SP3 CU4 (64-
bit)

Table 38: OAS application hardware and software requirements
Windows® Server® 2019 (version 1803 or later)
(64-bit)
Windows® Server® 2016 with Update (KB4512495)

(64-bit)
Supported server operating systems and
Supports:
database software
Metasys User Interface
Supported user interfaces
Site Management Portal (SMP)
Microsoft Hyper-V™
Supported virtual environments
VMware®
Microsoft .NET Framework Version 4.7.2
Additional software included with the OAS
software download Launcher Software
Metasys Database Manager

Optional software
Language Installation Program
1 For best performance, use the maximum amount of memory that the computer allows.

Application and Data Server-Lite system requirements
Table 39: Application and Data Server-Lite system requirements
Recommended Computer Intel i7 processor latest version with at least 6 cores or better
Platform
1 2
2 x 500 GB hard disk (RAID 1) with 40 GB free space after installation of all prerequisite
1
2
software and before installation of ADS-Lite software. Configure RAID 1 (mirroring) with
disk write-caching turned on.
Note: Prerequisite software includes the supported operating system, database
software, .NET Framework, and any other software or service packs required for
your ADS configuration.
Graphics adapter (1 GB RAM, ATI® Technologies or NVIDIA® Corporation, 64-bit
compatible [for 64-bit operating systems], Small Form Factor [SFF] if required)
3
8 GB minimum, 16 GB recommended
3
The VM host must have at least 8 GB of allocated RAM at all time. When you configure
the VM, do not select the enable dynamic memory option.
Supported Operating Systems Windows® 10 Pro and Windows 10 Enterprise Editions versions 1903, 1909, and 2004
and Database Software
4
(64-bit). For all future Windows 10 updates after version 2004, we will evaluate and
4
certify that Metasys software can support the updates before we provide guidance on
support.
Supports:
Note: SQL Server 2019 may cause the configuration service cache that
builds stored procedures to time out. This causes the user's log in to
Metasys UI to fail. To resolve this issue, set SQL Server 2019 to run in 2017
compatibility mode. For more information, refer to docs.microsoft.com
Windows® 8.1 Pro and Windows 8.1 Enterprise Editions with Update (KB2919355) (64-
bit)
Supports:
Supported Operating Systems Windows® 10 Pro and Windows 10 Enterprise Editions versions 1903, 1909, and 2004
for Metasys Client Devices (64-bit). For all future Windows 10 updates after version 2004, we will evaluate and
certify that Metasys software can support the updates before we provide guidance on
support.
Windows® 8.1 Pro and Windows 8.1 Enterprise Editions with Update (KB2919355) (64-
bit)
Notes:
• In OS X, you cannot view Graphics+ graphics in the Site Management Portal
UI.
• Apple operating systems are supported for Metasys client computers only.

Table 39: Application and Data Server-Lite system requirements
Supported Web Browser Windows® Internet Explorer® 11.0.9600.18816 Update version 11.0.47 or later
Software for Metasys Site Note: Select the Use Microsoft compatibility lists option, found under Tools
Management Portal Client > Compatibility View Settings, to ensure that websites appear and function
correctly.

Note:
Other browsers, such as Mozilla® Firefox®, may also be used but are not fully
supported. You use the web browser to download the Launcher application. After you
install the Launcher application, you use the Launcher, not the web browser, to log in to
the Site Management Portal (SMP) user interface.
Supported Web Browser Windows® Internet Explorer® 11.0.9600.18816 Update version 11.0.47 or later
Software for Metasys UI Clients Notes:
• You use the web browser to download the Launcher. The Metasys UI does
not support Internet Explorer 11 on Windows 10 operating systems.
• Select the Use Microsoft compatibility lists option, found under Tools >
Compatibility View Settings, to ensure that websites appear and function
correctly.
• Metasys UI does not support InPrivate Browsing. To exit InPrivate Browsing,
close the browser window and open a new browser window.
Microsoft® Edge® version 44 or later
Google® Chrome™ version 78 or later

Note: Metasys UI does not support incognito mode. To exit incognito mode,
click or tap the X icon of the browser window or tab and then open a new
browser window or tab. For more information on incognito mode in Google
Chrome, click here.

Note:
Metasys UI does not support private browsing. To exit

Other web browsers, such as Mozilla® Firefox

Supported Virtual Environments Microsoft Hyper-V™
VMware®
Metasys UI
Additional Software Included Microsoft .NET Framework 4.7.2
with the ADS-Lite Software Launcher Software
Download
Optional Hardware Any network or local printer supported by the qualified Windows operating system
Optional Software Graphic Generation Tool
CCT Software
SCT Software
Metasys Device Manager
1
2 For best performance, use Serial Attached SCSI (SAS) hard drives, not Small Computer System Interface (SCSI) hard
drives.
3 It is recommended to use RAM that the computer supports.

SCT Technical Specifications
For instances where the SCT is installed on the same computer as the ADS/ADX software, refer
to the specifications in the Application and Data Server (ADS/ADX) Product Bulletin (LIT-1201525). For
applications where the SCT is installed on an ODS, refer to the specifications in the Open Data Server
(ODS) Product Bulletin (LIT-12011943).
Notes:
• Refer to the Network and IT Guidance for the BAS Professional Technical Bulletin (LIT-1201279)
for specific Microsoft Windows OS settings that may be required for your Metasys system
configuration.
• For information on licensing Microsoft SQL Server, refer to the Microsoft SQL Server Licensing
Guide for the edition of Microsoft SQL Server that you installed.
Table 40: SCT System Requirements
Product Code TL-SCT-0: New project software
TL-SCT-6: Upgrade software

Full server platform Intel® Core™ i7 processor, latest version with at least four cores, or
better
20 GB minimum free hard disk space available. Use a Solid State Drive
(SSD) to significantly improve performance compared to other types of
hard disks.
16 GB RAM (4 GB RAM minimum)

Desktop computer Intel Core 2 Duo E6700 or better (Intel Core 2 Duo E4300 minimum)
platform
20 GB minimum free hard disk space available. Use a Solid State Drive
(SSD) to significantly improve performance compared to other types of
hard disks.
16 GB RAM (4 GB RAM minimum)
Windows Server 2019

Supported full server Windows Server 2019 (version 1803 or later) (64-bit)
platform operating
systems and database Supports Microsoft SQL Server 2019 (64-bit), SQL Server 2017 with
software CU17 (64-bit), Microsoft SQL Server 2016 with SP2 CU10 (64-bit), or
Microsoft SQL Server 2014 with SP3 CU4.
Note: If you Windows Server 2016 with update KB4489890 (64-bit)
install the SCT
on a standalone Supports Microsoft SQL Server 2019 (64-bit), SQL Server 2017 with
server and not on CU17 (64-bit), Microsoft SQL Server 2016 with SP2 CU10 (64-bit), or
a Metasys server, Microsoft SQL Server 2014 with SP3 CU4 (64-bit)
you can also use the
Express versions
of Microsoft SQL
Server.

Table 40: SCT System Requirements
Supported desktop Windows® and Windows 10 Enterprise Editions versions 1903,
computer platform 1909, and 2004 (64-bit). For all future Windows 10 updates after
operating systems and version 2004, we will evaluate and certify that Metasys software
database software can support the updates before we provide guidance on support.
Supports Microsoft SQL 2019 Express (64-bit),SQL Server 2017 Express

with CU17 (64-bit), Microsoft SQL Server 2016 Express with SP2 CU10
(64-bit) or, Microsoft SQL Server 2014 Express with SP3 CU4 (64-bit).
Note: The Windows 10 version 1903 update is required for any

Windows 10 computer that runs Metasys 11.0 software, including
the ADS, ADX, ODS, and any Metasys software application. Verify
this update before installing Metasys 11.0 software. If you are
upgrading to Metasys Release 11.0 and do not have this update,
uninstall the previous release of all Metasys software, apply the
Windows 10 version 1903 update, then proceed with the Metasys
11.0 upgrade.
Windows 8.1 Pro and Windows 8.1 Enterprise Editions with update
KB2919355 (64-bit)
Supports Microsoft SQL Server 2017 Express with CU17 (64-bit),

Microsoft SQL Server 2016 Express with SP2 CU10 (64-bit), or Microsoft
SQL Server 2014 Express with SP3 CU4 (64-bit).
Supported web browser Microsoft® Edge® version 44 or later, Apple® Safari® 11 or later, and
software for Metasys Google® Chrome™ version 78 or later.
client computers Other browsers, such as Mozilla® Firefox®, may also be used but are
not fully supported.
Note: Use a web browser to download the Launcher application.

After you install the Launcher application, you can use the
Launcher to log in to the SCT UI. You can also use the web
browsers to access the Site Management Portal (SMP) UI, Metasys
UI, Metasys UI Offline, and SCT Pro sites. You can also add a
bookmark to the Metasys UI, Metasys UI Offline, and SCT Pro
sites.
Network Ethernet network interface card 10/100/1000 Mbps (100 Mbps network
communication for or better)
Metasys System
Configuration Tool
client computers
Optional software Note: A license for the SCT 14.0 is not included with Metasys
packaging server software. Obtain a license for each installation of the SCT
and obtain a license for Field Controller packages to upload and
download .caf files.

CCT technical specifications
Table 41: CCT system requirements
Recommended computer Intel® Core® 2 Duo E6700 or better. Minimum Intel Core 2 Duo
E4300.
20 GB free hard disk available. Minimum 600 MB.

Recommended memory Computer Platforms: 16 GB RAM. Minimum 4 GB RAM.
Supported operating Windows® 10 Pro and Windows 10 Enterprise Editions versions
system (OS) and database 1903, 1909, and 2004 (64-bit). For all future Windows 10 updates
software after version 2004, we will evaluate and certify that Metasys
software can support the updates before we provide guidance
on support.
Supports Microsoft SQL Server® 2019 Express (64-bit), SQL Server®

2017 Express with CU17 (64-bit), SQL Server® 2016 Express with SP2
CU10 (64-bit), or SQL Server® 2014 Express with SP3 CU4 (64-bit).
Note: The OS and software must both be 64-bit.

Supports Microsoft SQL Server® 2017 Express with CU17 (64-bit),

SQL Server® 2016 Express with SP2 CU10 (64-bit), or SQL Server®
2014 Express with SP3 CU4 (64-bit).
Note: The OS and software must both be 64-bit.

Supported full server Windows® Server® 2019 (version 1803 or later) (64-bit)
platform operating
systems and database Supports Microsoft SQL Server® 2019 (64-bit), SQL Server® 2017
software with CU17 (64-bit), SQL Server® 2016 with SP2 CU10 (64-bit), or SQL
Server® 2014 with SP3 CU4 (64-bit).
Supports Microsoft SQL Server® 2019 (64-bit), SQL Server® 2017

with CU17 (64-bit), SQL Server® 2016 with SP2 CU10 (64-bit), or SQL
Server® 2014 with SP3 CU4 (64-bit).
Required web browser Microsoft® Edge® version 44 or later, Apple® Safari® 11 or later,
software for Metasys client and Google® Chrome™ version 78 or later. Other browsers, such as
computers Mozilla® Firefox®, can also be used but are not fully supported.
Note: Web browser software is required if you want to view

the Controller Tool Help (LIT-12011147) online. However, you can
also access this help system as a PDF from the software.
Network communication Ethernet network interface card 10/100/1000 Mbps (100 Mbps
for CCT client Computer network or better recommended)

Table 41: CCT system requirements
Software optionally Microsoft .NET Framework version 4.7.2
installed during CCT
installation Microsoft SQL Server 2016 Express software with SP2
Optional connection Bluetooth Commissioning Converter (MS-BTCVT-1)
devices (order separately) Important: The BTCVT Bluetooth Commissioning Converter is
no longer available (no longer in production), and is no longer
a supported connection method at Metasys Release 11.0.
Laptop with Bluetooth® wireless communications or a computer

with a USB Bluetooth converter
The USB Dongle with ZigBee® Driver (ZFR-USBHA-0) includes a

wireless connection through the CCT for wireless commissioning of
the wireless enabled FEC and VMA16 field controllers. It is also used
in the ZCT.
The Mobile Access Portal (MAP) Gateway (TL-MAP1810-0Px) at

Release 4.2 and above includes BACnet routing functionality to
allow the MAP Gateway to easily connect to the field controller and
system tools through a WIFI connection to perform file transfers
and commissioning function. For further information, refer to the
Mobile Access Portal Gateway Product Bulletin (LIT-12011884).
The Portable BACnet/Internet Protocol to MS/TP Router (TL-

BRTRP-0) routes information between BACnet/IP and MS/TP
networks. For further information, refer to the Portable BACnet®.
IP to MS/TP Router (Part No. 24-10414-2) Adobe® Reader® software
Note: A PDF reader software is required for the Print function

in CCT.
Optional hardware Any network or local printer supported by the qualified Windows
operating system
SNC technical specifications

Table 42: SNC25151-0x and SNC16121-0x (display models)
Specification Description
Power Dedicated nominal 24 VAC, Class 2 power supply (North America), SELV power
requirement supply (Europe), at 50/60 Hz (20 VAC minimum to 30 VAC maximum)
33 VA maximum from main power supply
Power Note: The VA rating does not include any power supplied to the
consumption peripheral devices connected to Binary Outputs (BOs) or Configurable
Outputs (COs), which can consume up to 12 VA for each BO or CO, for a
possible total consumption of an additional 132 VA (maximum).
+15 VDC power source terminals provide 100 mA total current; quantity of
Power source inputs: five, located in Universal Input terminals; for active (3-wire) input
devices

SA Bus power 15 V at 240 mA maximum
Processor NXP i.MX6DualLite Processor, 1GHz 32-bit dual core Cortex A9 processor
16 GB flash nonvolatile memory for operating system, configuration data, and
operations data storage and backup
Memory
2 GB SDRAM for operations data dynamic memory
Universal Input
Input: 24-bit Analog to Digital converter
(UI) resolution
Analog Output
Output: +/- 200 mV accuracy in 0–10 VDC applications
(AO) accuracy
BACnet/IP, BACnet MS/TP, N2 Bus, LonWorks, Modbus, KNX, M-Bus, Zettler
Fire, OPC UA
Supported
integrations Tyco C•CURE 9000-victor video management, Simplex FACU, Molex Lighting
Control, Cree SmartCast Lighting Control
Two Ethernet ports; 1000/100/10 Mbps; 8-pin RJ45 connector
One FC port (RJ12 6-pin port; connects with 1.5 m [4.9 ft] RJ12 field bus cable)
One SA port (RJ12 6-pin port; connects with 1.5 m [4.9 ft] RJ12 field bus cable)
Network and
serial interfaces One optically isolated RS-485 port; with a removable 4-pin terminal block
One optically isolated SA Bus port; with a removable 4-pin terminal block
Two USB A ports. All support USB 2.0 and Open Host Controller Interface
[Open HCI] specification.
Ethernet communication: 100, or 10 Mbps
Transmission Optically isolated, serial communication (FC Bus): 76,800, 38,400, 19,200, 9600,
speeds or 1200 bps (selectable)
Sensor/actuator communication (SA Bus): 38,400 bps

Ambient Operating: 0°C to 50°C (32°F to 122°F)
temperature
conditions Non-operating: -40°C to 70°C (-40°F to 158°F)
Ambient humidity Storage: 5% to 95% RH, 30°C (86°F) maximum dew point conditions
conditions Operating: 0% to 90% RH, 30°C (86°F) maximum dew point conditions
Housing Black Polycarbonate and Acrylonitrile butadiene styrene (ABS) blend
Mounting On flat surface with screws on three mounting clips or a single 35 mm DIN rail
Dimensions
(width x height x 250 mm x 145 mm x 45.5 mm (9.84 in. x 5.71 in. x 1.79 in.)
depth)
Weight 0.65 kg (1.433 lbs)

United States: UL Listed, File E107041, CCN PAZX, UL 916, Energy
Compliance Management Equipment; FCC Compliant to CFR47, Part 15, Subpart B, Class A,
Conformance to FIPS 140-2 Level 1 and validated under NIST Certificate #3389
Canada: UL Listed, File E107041, CCN PAZX7, CAN/CSA C22.2 No. 205, Signal
Equipment; Industry Canada Compliant, ICES-003
Europe: Johnson Controls declares that this product is in compliance with the
essential requirements and other relevant provisions of the EMC Directive.
Australia and New Zealand: RCM Mark, Australia/NZ Emissions Compliant

BACnet International: BTL 135-2016 Listed B-BC/B-RTR/B-BBMD, Protocol
Revision 18
Table 43: SNC25150 and SNC16120

Power Dedicated nominal 24 VAC, Class 2 power supply (North America), SELV power
requirement supply (Europe), at 50/60 Hz (20 VAC minimum to 30 VAC maximum)
32 VA maximum from main power supply
Power Note: The VA rating does not include any power supplied to the
consumption peripheral devices connected to Binary Outputs (BOs) or Configurable
Outputs (COs), which can consume up to 12 VA for each BO or CO, for a
possible total consumption of an additional 132 VA (maximum).
+15 VDC power source terminals provide 100 mA total current; quantity of
Power source inputs: five, located in Universal Input terminals; for active (3-wire) input
devices
SA Bus power 15 V at 240 mA maximum
Processor NXP i.MX6DualLite Processor, 1GHz 32-bit dual core Cortex A9 processor
Memory
Universal Input
Input: 24-bit Analog to Digital converter
(UI) resolution
Analog Output
Output: +/- 200 mV accuracy in 0–10 VDC applications
(AO) accuracy
Supported
Fire Tyco C•CURE 9000-victor video management, Simplex FACU, Molex
integrations
Lighting Control, Cree SmartCast Lighting Control

Table 43: SNC25150 and SNC16120
One supported Ethernet port (top); 1000/100/10 Mbps; 8-pin RJ45 connector
One FC port (RJ12 6-pin port; connects with 1.5 m [4.9 ft] RJ12 field bus cable)
One SA port (RJ12 6-pin port; connects with 1.5 m [4.9 ft] RJ12 field bus cable)
Network and One optically isolated RS-485 port; with a removable 4-pin terminal block
serial interfaces
One magnetically isolated FC Bus port; with a removable 4-pin terminal block
One SA Bus port; with a removable 4-pin terminal block
Two USB A ports. All support USB 2.0 and Open Host Controller Interface
[Open HCI] specification.
Ethernet communication: 100, or 10 Mbps
Transmission Optically isolated, serial communication (FC Bus): 76,800, 38,400, 19,200, 9600,
speeds or 1200 bps (selectable)
Sensor/actuator communication (SA Bus): 38,400 bps

temperature
conditions Non-operating: -40°C to 70°C (-40°F to 158°F)
Dimensions
(width x height x 250 mm x 145 mm x 45.5 mm (9.84 in. x 5.71 in. x 1.79 in.)
depth)
Conformance to FIPS 140-2 Level 1 and validated under NIST Certificate #3389
Europe: Johnson Controls declares that this product is in compliance with the
essential requirements and other relevant provisions of the EMC Directive.

Revision 18
FIPS 140-2 Level 1: Compliant and certified with Federal Information
Processing Standard; https://csrc.nist.gov/Projects/cryptographic-module-
validation-program/Certificate/3389

The performance specifications are nominal and conform to acceptable industry standard. For
application at conditions beyond these specifications, consult the local Johnson Controls® office. Johnson
Controls, Inc. shall not be liable for damages resulting from misapplication or misuse of its products.
SNE technical specifications

Table 44: SNE2200x network engine
Dedicated nominal 24 VAC, Class 2 power supply (North America), SELV power
supply (Europe), at 50/60 Hz (20 VAC minimum to 30 VAC maximum)
Power
requirement Alternate: Dedicated nominal 24 VDC, Class II power supply input; North
America: ACC-PWRKIT-1A24; Europe: ACC-PWRKIT-1E24
Power
38 VA maximum
consumption
NXP i.MX6 DualLite processor, dual core Cortex-A9 processor at 1.0 GHz with
Processor
512 KB of L2 cache
Memory
Fire, OPC UA
Supported
integrations Tyco C•CURE 9000-victor video management, Simplex FACU, Molex Lighting
Control, Cree SmartCast Lighting Control
One Ethernet port; 1000/100/10 Mbps; 8-pin RJ45 connector
Two FC ports (RJ12 6-pin port; connects with 1.5 m [4.9 ft] RJ12 field bus cable)
Network and Two optically isolated RS-485 ports; with a removable 4-pin terminal block
Serial interfaces
Three USB ports (one Micro-B port, and two USB A ports). All support USB 2.0
and Open Host Controller Interface [Open HCI] specification; Micro-USB port
currently inactive
Ethernet communication: 1000, 100, or 10 Mbps
Transmission
speeds Optically isolated, serial communication (FC Bus): 76,800, 38,400, 19,200, 9600,
or 1200 bps (selectable)
temperature
conditions Non-Operating: -40°C to 70°C (-40°F to 158°F)
Black Polycarbonate and Acrylonitrile butadiene styrene (ABS) blend
Housing IP protection class: IP20
UL flammability rating: UL94-5VB

Table 44: SNE2200x network engine
Dimensions
(Height x Width x 190 mm x 125 mm x 44.5 mm (7.48 in. x 4.92 in. x 1.75 in.)
Depth)
Conformance to FIPS 140-2 Level 1 and validated under NIST Certificate #3389.
Europe: CE Mark – Johnson Controls, Inc. declares that this product is in
compliance with the essential requirements and other relevant provisions of
the EMC Directive.
Revision 18
Table 45: SNE1100x, SNE1050x, and SNE110Lx network engines

Dedicated nominal 24 VAC, Class 2 power supply (North America), SELV power
supply (Europe), at 50/60 Hz (20 VAC minimum to 30 VAC maximum)
Power
requirement Alternate: Dedicated nominal 24 VDC, Class II power supply input; North
America: ACC-PWRKIT-1A24; Europe: ACC-PWRKIT-1E24
Power
38 VA maximum
consumption
NXP i.MX6 DualLite processor, dual core Cortex-A9 processor at 1.0 GHz with
Processor
512 KB of L2 cache
Memory
Fire, OPC UA
Supported Tyco C•CURE 9000-victor video management, Simplex FACU, Molex Lighting
integrations Control, Cree SmartCast Lighting Control
Note: The SNE110Lx model supports one IP device integration, but does
not support the N2 Bus or LonWorks network interface.

Table 45: SNE1100x, SNE1050x, and SNE110Lx network engines
One Ethernet port; 1000/100/10 Mbps; 8-pin RJ45 connector
One FC port (RJ12 6-pin port; connects with 1.5 m [4.9 ft] RJ-12 field bus cable)
Network and One optically isolated RS-485 port; with a removable 4-pin terminal block
Serial interfaces
Three USB ports (one Micro-B port, and two USB A ports). All support USB 2.0
and Open Host Controller Interface [Open HCI] specification; Micro-USB port
currently inactive
Ethernet communication: 1000, 100, or 10 Mbps
Transmission
speeds Optically isolated, serial communication (FC Bus): 76,800, 38,400, 19,200, 9600,
or 1200 bps (selectable)
temperature
conditions Non-Operating: -40°C to 70°C (-40°F to 158°F)
Dimensions
(Height x Width x 190 mm x 125 mm x 45.5 mm (7.48 in. x 4.92 in. x 1.75 in.)
Depth)
Compliance
Management Equipment; FCC Compliant to CFR47, Part 15, Subpart B, Class A
Europe: CE Mark – Johnson Controls, Inc. declares that this product is in
compliance with the essential requirements and other relevant provisions of
the EMC Directive.
Revision 18
The performance specifications are nominal and conform to acceptable industry standard. For
application at conditions beyond these specifications, consult the local Johnson Controls® office. Johnson
Controls, Inc. shall not be liable for damages resulting from misapplication or misuse of its products.
LCS85 technical specifications

Table 46: LCS85 software system recommendations for installation or upgrade
Intel Xeon E5506, 2.13 GHz, 4 MB Cache
Recommended computer 2 x 160 GB 7.2K SATA, 8.9 cm (3.5 in.) Cabled

platform
3 Gbps, RAID 1 configuration with add-in SAS6/iR (SATA/SAS
Controller)
Recommended memory 16 GB RAM minimum; 32 GB RAM recommended
Hard disk 160 GB minimum
• Windows® Server® 2019 (version 1803 or later) (64-bit)
• Windows® Server® 2016 with Update (KB4512495) (64-bit)
Supported operating systems
and software Note: Microsoft .NET Framework 3.5 Service Pack (SP) 1
and Microsoft .NET Framework 4.7.2 are required for LCS85
software.
Internal optical drive DVD ROM, SATA
Windows® Internet Explorer® 11.0.9600.18816 Update version
11.0.47 or later
Note: In Internet Explorer 11, select the Use Microsoft

compatibility lists option, found under Tools >
Supported web browser Compatibility View Settings, to ensure that websites
Software for Metasys Site appear and function correctly.
Management Portal client
computers Google® Chrome™ version 78 or later
Other browsers, such as Mozilla® Firefox®, may also be used

but are not fully supported.
Supported virtual environments Microsoft Hyper-V™, VMWare®
Selectable Network Interface (if computer has multiple network
cards, during LCS85 installation, select the network card that
was configured for Metasys system use before installation)
Network communication
Ethernet network interface card 10/100/1000 Mbps (100 Mbps
or better recommended)
Uninterruptible power supply (UPS)
Recommended data protection
Smart-UPS SC 450VA, 280 W, 120 VAC input/output, NEMA 5-15R
output connections, OEM Part No. SC450RM1U

Technical specifications - NCE25, NAE35, and NAE45 models
Table 47: NCE25 technical specifications
Dedicated nominal 24 VAC, Class 2 power supply (North America),
Power Requirement SELV power supply (Europe), at 50/60 Hz (20 VAC minimum to 30 VAC
maximum)
25 VA maximum for NCE25 only
Note: The 25 VA rating does not include any power supplied
Power Consumption by the NCE to devices connected at the NCE BOs. BO devices
connected to and powered by an NCE can require an additional
125 VA (maximum).
+15 VDC power source terminals provide 100 mA total current; quantity
Power Source of inputs: five, located in Universal IN terminals; for active (3-wire) input
devices
Ambient Operating 0°C to 50°C (32°F to 122°F), 10% to 90% RH, 30°C (86°F) maximum dew
Conditions point
Ambient Storage -40°C to 70°C (-40°F to 158°F), 5% to 95% RH, 30°C (86°F) maximum dew
Conditions point
Supports data protection on power failure. Rechargeable NiMH battery:
Data Protection Battery 3.6 VDC 500 mAh, with a typical life of 5 to 7 years at 21°C (70°F);
Product Code Number: MS-BAT1020-0
Supervisory Controller: 192 MHz Renesas SH4 7760 RISC processor
Processors
Field Controller: 20 MHz Renesas H8S2398 processor
Supervisory Controller: 128 MB flash nonvolatile memory for
operating system, configuration data, and operations data storage and
Memory backup and 128 MB SDRAM for operations data dynamic memory
Field Controller: 1 MB flash memory and 1 MB RAM

Microsoft Windows Embedded CE 6.0 (Release 9.0.6)
Operating System
Buildroot 2017.08.2 with Linux kernel 14.4 (Release 9.0.7 or 9.0.8 patch)

• One Ethernet port; 10/100 Mbps; 8-pin RJ-45 connector
• One optically isolated RS-485 SA Bus port; with a pluggable and
keyed 4-position terminal block (on all NCE25 models)
• One optically isolated RS-485 port; with a pluggable and keyed 4-
position terminal block (only on NCE25 models that support an N2
Bus or MS/TP bus trunk)
Network and Serial • One LonWorks port; FTT10 78 Kbps; pluggable, keyed 3-position
Interfaces terminal block (only on NCE25 models that support a LonWorks
Network trunk). The LonWorks models are supported to run the
(Depending on NCE Metasys Release 9.0.6 software, but not the Release 9.0.7 or 9.0.8
model) patch update.
• One RS-232-C serial port with a standard 9-pin sub-D connector
that supports standard baud rates
• One USB serial port with standard USB connector that supports
an optional, user-supplied external modem. Modem functions are
available with Release 9.0.6, but are not available after the NCE is
Metasys patched with Release 9.0.7 or 9.0.8.
• Analog Input Points: 16-bit resolution
Analog Input/Analog
• Analog Output Points: 16-bit resolution and ±200 mV accuracy on
Output Point Resolution
0-10 VDC applications
• 10-Universal Inputs: Defined as 0–10 VDC, 4–20 mA, 0–600k ohm,
or Binary Dry Contact
• 8-Binary Inputs: Defined as Dry Contact Maintained or Pulse/
Accumulator Mode
Input/Output
Capabilities • 4-Analog Outputs: Defined as 0–10 VDC or 4–20 mA
• 7-Binary Outputs: Defined as 24 VAC Triac (selectable internal or
external source power)
• 4-Configurable Outputs: Defined as 0–10 VDC or 24 VAC Triac BO
155 mm x 270 mm x 64 mm (6.1 in. x 10.6 in. x 2.5 in.),
Dimensions
Minimum mounting space required: 250 mm x 370 mm x 110 mm (9.8
(Height x Width x Depth)
in. x 14.6 in. x 4.3 in.)
Plastic housing
Housing Plastic material: ABS and polycarbonate
Protection: IP20 (IEC60529)

On a flat surface with screws, on three mounting clips, or a single 35
Mounting
mm DIN rail
Shipping Weight 1.2 kg (2.7 lb)
Compliance United States: UL Listed, File E107041, CCN PAZX, UL 916, Energy
Management Equipment; FCC Compliant to CFR47, Part 15, Subpart B,
Class A

Canada: UL Listed, File E107041, CCN PAZX7, CAN/CSA C22.2 No. 205,
Signal Equipment Industry Canada Compliant, ICES-003
Europe: CE Mark - Johnson Controls declares that this product is
in compliance with the essential requirements and other relevant
provisions of the EMC Directive.
Australia and New Zealand: RCM Mark, Australia/NZ Emissions
Compliant
BACnet International: BTL 135-2010 Listed B-BC, Protocol Revision 12

maximum)
Power Consumption 25 VA maximum
Ambient Operating 0°C to 50°C (32°F to 122°F); 10% to 90% RH, 30°C (86°F) maximum dew
Conditions point
Ambient Storage -40°C to 70°C (-40°F to 158°F); 5% to 95% RH, 30°C (86°F) maximum dew
Conditions point
Supports data protection on power failure. Rechargeable NiMH battery:
Data Protection Battery 3.6 VDC 500 mAh, with a typical life of 5 to 7 years at 21°C (70°F);
Processor 192 MHz Renesas SH4 7760 RISC processor
128 MB flash nonvolatile memory for operating system, configuration
data, and operations data storage and backup
Memory
128 MB SDRAM for operations data dynamic memory
Microsoft Windows Embedded CE 6.0 (Release 9.0)
Operating System
Buildroot 2017.08.2 with Linux kernel 14.4 (Release 9.0.7 or 9.0.8 patch)

• One Ethernet port; connects at 10 or 100 Mbps; 8-pin RJ-45
connector
• One optically isolated RS-485 port; 9.6k, 19.2k, 38.4k, or 76.8k baud
(depending on protocol); with a pluggable and keyed 4-position
terminal block (FC Bus available on NAE351x and NAE451x models
only)
• One LonWorks port; FTT10 78 Kbps; pluggable, keyed 3-position
terminal block (LonWorks port available on NAE352x-x and
NAE452x models only). The LonWorks models are supported to run
the Metasys Release 9.0 software, but not the Release 9.0.7 or
Network and Serial 9.0.8 patch update.
Interfaces
• One RS-232-C serial port with standard 9-pin sub-D connector that
supports standard baud rates.
• Second serial port, on models without an internal modem, that
supports an optional, user-supplied external modem. Modem
functions are available with Metasys Release 9.0, but are not
available after the NAE is patched with Release 9.0.7 or 9.0.8.
• One USB serial port with standard USB connector that supports
an optional, user-supplied external modem. Modem functions are
available with Metasys Release 9.0, but are not available after the
NAE is patched with Release 9.0.7 or 9.0.8.
Plastic housing material: ABS polycarbonate
Housing
UL94-5VB Protection: IP20 (IEC 60529)
On a flat surface with screws on three mounting clips or a single 35 mm
Mounting
DIN rail
Dimensions 131 mm x 270 mm x 62 mm (5-3/16 in. x 10-5/8 in. x 2-1/2 in.)
Minimum space for mounting NAE35 and NAE45: 210 mm x 350 mm x
(Height x Width x Depth) 110 mm (8-3/16 in. x 13-13/16 in. x 4.-5/16 in.)
Compliance Management Equipment; FCC Compliant to CFR47, Part 15, Subpart B,
Class A
Signal Equipment; Industry Canada Compliant, ICES-003
Compliant
Europe: CE Mark – Johnson Controls declares that this product is

Technical specifications
Table 48: NAE5510-2U (UL 864, Smoke Control) technical specifications
Dedicated nominal 24 VAC, Class 2 power supply (North America) at
Power Requirement
50/60 Hz (20 VAC minimum to 30 VAC maximum)
Conditions point
Conditions point
Supports data protection on power failure. Rechargeable gel cell
Data Protection Battery battery: 12 V, 1.2 Ah, with a typical life of 3 to 5 years at 21°C (70°F);
Maintains real-time clock through a power failure. Onboard cell; typical
Clock Battery
life 10 years at 21°C (70°F)
Processor 1.6 GHz Intel Atom® processor
4 GB flash nonvolatile memory for operating system, configuration
data, and operations data storage and backup.
Memory
1 GB SDRAM for operations data dynamic memory for all models
Johnson Controls OEM Version of Microsoft Windows Standard 2009
Operating System
(used by Metasys system Release 8.1)
• One Ethernet port; 10/100/1,000 Mbps; 8-pin RJ-45 connector
• Two optically isolated RS-485 ports; 9.6k, 19.2k, 38.4k, or 76.8k
baud; pluggable and keyed 4-position terminal blocks
Network and Serial
• Two RS-232-C serial ports, with standard 9-pin sub-D connectors,
Interfaces
that support all standard baud rates
• Two USB serial ports; standard USB connectors (use is not
supported on Smoke Control NAEs)
Plastic housing with internal metal shield
Housing
Plastic material: ABS + polycarbonate
On a flat surface with screws on four mounting feet or on a dual 35 mm
Mounting
DIN rail
226 mm x 332 mm x 96.5 mm (8.9 in. x 13.1 in. x 3.8 in.) including
Dimensions mounting feet
(Height x Width x Depth) Minimum space for mounting: 303 mm x 408 mm x 148 mm (12.0 in. x
16.1 in. x 5.8 in.)
Management Equipment; FCC Compliant to CFR47, Part 15, Subpart B,
Class A
Compliance
UL Listed, File S4977, UL 864 UUKL/UUKLC 10th Edition Listed, Smoke
Control Units and Accessories for Fire Alarm Systems Equipment

Table 48: NAE5510-2U (UL 864, Smoke Control) technical specifications
Signal Equipment, Industry Canada Compliant, ICES-003
UL Listed, File S4977, UL 864 UUKL/ORD-C100-13 10th Edition Listed,

Smoke Control Units and Accessories for Fire Alarm Systems
Europe: CE Mark - Johnson Controls, Inc. declares that this product
is in compliance with the essential requirements and other relevant
Compliant
Table 49: NAE55xx-3 (UL 916, Energy Management) and NAE5510-3U (UL 864, Smoke Control)
technical specifications
maximum)
Conditions point
Conditions point
Supports data protection on power failure. Rechargeable gel cell
Data Protection Battery battery: 12 V, 1.2 Ah, with a typical life of 3 to 5 years at 21°C (70°F);
Maintains real-time clock through a power failure. Onboard cell; typical
Clock Battery
life 10 years at 21°C (70°F)
1.46 GHz Intel® Atom® Bay Trail E3815 processor for MS-NAE55xx-3
Processor
models
16 GB flash nonvolatile memory for operating system, configuration
data, and operations data storage and backup for MS-NAE55xx-3
Memory models.
2 GB DDR3 SDRAM for operations data dynamic memory for all models
NAE5510-3U (UL 864): Johnson Controls OEM Version of Microsoft®
Windows® Embedded Standard 7 with SP1 (WES7)
Operating System
NAE55xx-3: (UL 916): Wind River® Linux LTS 17 (LTS=long-term
support)

Table 49: NAE55xx-3 (UL 916, Energy Management) and NAE5510-3U (UL 864, Smoke Control)
technical specifications
• One Ethernet port; 10/100/1,000 Mbps; 8-pin RJ-45 connector
• Two optically isolated RS-485 ports; 9.6k, 19.2k, 38.4k, or 76.8k
baud; pluggable and keyed 4 position terminal blocks (RS-485
terminal blocks available on NAE55 models only)
• Two RS-232-C serial ports, with standard 9-pin sub-D connectors,
Network and Serial that support all standard baud rates
Interfaces • Two USB 2.0 serial ports; standard USB connectors support an
optional, user-supplied external modem (no longer supported at
Release 10.0 or later)
• One LonWorks port; FTT10 78 Kbps; pluggable, keyed 3-position
terminal block (LonWorks port available on NAE552x-x models
only)
Plastic housing with internal metal shield
Housing
Plastic material: ABS + polycarbonate; Protection: IP20 (IEC 60529)
On a flat surface with screws on four mounting feet or on a dual 35 mm
Mounting
DIN rail
226 mm x 332 mm x 96.5 mm (8.9 in. x 13.1 in. x 3.8 in.) including
Dimensions mounting feet
(Height x Width x Depth) Minimum space for mounting: 303 mm x 408 mm x 148 mm (12.0 in. x
16.1 in. x 5.8 in.)
Management Equipment, FCC Compliant to CFR47, Part 15, Subpart B,
Class A
Compliance
UL Listed, File S4977, UL 864 UUKL/UUKLC 10th Edition Listed, Smoke
Control Units and Accessories for Fire Alarm Systems Equipment (MS-
NAE5510-3U model only with Release 8.1 software)
Signal Equipment, Industry Canada Compliant, ICES-003
UL Listed, File S4977, UL 864 UUKL/ORD-C100-13 10th Edition Listed,

Smoke Control Units and Accessories for Fire Alarm Systems (MS-
NAE5510-3U model only with Release 8.1 software)
Europe: CE Mark - Johnson Controls declares that this product is
Compliant
BACnet International: BTL 135-2016 Listed B-BC/B-BBMD, Protocol
Revision 15
FIPS 140-2 Level 1: Compliant with Federal Information Processing
Standard (NAE55s at Release 11.0 only)

Metasys system related documentation
The documents in Table 50 contain information related to the features, installation, operation,
configuration, and troubleshooting of the Metasys system.
Table 50: Related documentation
For information about See document
How to install and upgrade the ADS and ADX Metasys Server Installation and Upgrade
Software; How to install and upgrade Metasys Instructions (LIT-12012162)
UI; How to install the Metasys Advanced
Reporting System
How to install and upgrade the ADS-Lite and Metasys Server Lite Installation and Upgrade
Metasys UI software Instructions (LIT-12012162)
How to install and upgrade SQL Server software SQL Server Installation and Upgrade Instructions
(LIT-12012240)
How to install and upgrade the OAS Open Application Server (OAS) Installation and
Upgrade Instructions (LIT-12013222)
How to install and upgrade the SCT, SCT Pro and SCT Installation and Upgrade Instructions
Metasys UI Offline Software (LIT-12012067)
How to install the CCT Software CCT Installation Instructions (LIT-12011529)
How to license Metasys system software Software Manager Help (LIT-12012389)
How to configure an ADS/ADX to be Site ADS/ADX Commissioning Guide (LIT-1201645)
Director, use ADS repositories, synchronize
time, use a network printer, accept dial-up
connections, and more
How to configure an OAS to be Site Director, OAS Commissioning Guide (LIT-12013243)
use Server repositories, synchronize time, use a
network printer, accept dial-up connections, and
more
Features, benefits, and specifications of the Metasys UI Help (LIT-12011953)
Metasys UI
Features, benefits, and specifications of the Metasys UI Offline Help (LIT-12012116)
Metasys Offline UI
Features, benefits, and specifications of Application and Data Server (ADS) and Extended
the Application and Data Server/Extended Application and Data Server (ADX) Product Bulletin
Application and Data Server (ADS/ADX) (LIT-1201525)
Features, benefits, and specifications of the Open Application Server (OAS) Product Bulletin
Open Application Server (OAS) (LIT-12013309)
Features, functions, and applications of Network Engines Product Bulletin (LIT-12012138)
the Network Automation Engines (NAEs)
in the Metasys system, including technical
specifications and ordering information
Features, functions, and applications of the SNE/SNC Product Bulletin (LIT-12013296)
SNE Series and SNC Series Network Engines
in the Metasys system, including technical

Network Engine commissioning for KNX vendor Network Engine Commissioning for KNX Vendor
integration Integration (LIT-12013148)
Network Engine commissioning for M-Bus Network Engine Commissioning for M-Bus Vendor
vendor integration Integration (LIT-12013149)
Network Engine commissioning for Modbus Network Engine Commissioning for Modbus
vendor integration Vendor Integration (LIT-12013150)
Network Engine commissioning for C·CURE 9000 Network Engine Commissioning for C·CURE 9000
Access Control and victor Video Management Access Control and Victor Video Management
Integration Integration (LIT-12013151)
Network Engine commissioning for Molex Metasys System Commissioning for Molex Digital
Digital Lighting Systems integration Lighting Systems Integration (LIT-12013153)
Network Engine commissioning for Cree Digital Metasys System Commissioning for Cree Digital
Lighting Systems integration Lighting Systems Integration (LIT-12013152)
Network Engine commissioning for Simplex Fire Network Engine Commissioning for Simplex Fire
System integration System Integration Application Note (LIT-12013060)
Network Engine commissioning for Zettler fire Network Engine Commissioning for Zettler Vendor
panels Integration Application Note (LIT-12013269)
Network Engine commissioning for OPC UA Network Engine Commissioning for OPC UA
client vendor integration Client Vendor Integration Application Note
(LIT-12013545)
Features, benefits, and specifications of the Field Metasys System Field Equipment Controllers and
Equipment Controller (FEC) family Related Products Product Bulletin (LIT-12011042)
Features, benefits, and specifications of the CG, Metasys CG, CV Equipment Controllers and XPM
CV Equipment Controllers Expansion Modules Product Bulletin (LIT-12013105)
Features, benefits, and specifications of the System Configuration Tool Catalog Page
System Configuration Tool (SCT) (LIT-1900198)
How to use the Metasys Database Manager to Metasys Database Manager Help (LIT-12011202)
manage historical data on an ADS
How to use the Advanced Reporting System Metasys Advanced Reporting System and Energy
Essentials Help (LIT-12011312)
How to apply, mount, wire, set up, and start NAE35/NAE45 Installation Instructions (Part No.
the NAE35 and the NAE45, including technical 24-10050-6)
How to apply, mount, wire, set up, and start the NAE55 Installation Instructions (Part No.
NAE55 including technical specifications and 24-10051-43)
ordering information
How to apply, mount, wire, set up, and start the NCE25 Installation Instructions (Part No.
NCE25, including technical specifications and 24-10143-63)
ordering information
How to set up an NAE35, NAE45, and NAE55 for NAE Commissioning Guide (LIT-1201519)
network connectivity and access the NAE user
interface to set the basic parameters

How to set up an NAE85 for network NAE85 Commissioning Guide (LIT-12011044)
connectivity and access the NAE85 user
interface to set the basic NAE85 parameters
How to set up a LonWorks® Control Server (LCS) LonWorks Control Server (LCS) 85 Commissioning
85 for operation on the Metasys network Guide (LIT-12011568)
How to use the SCT, including setting up archive Metasys SCT Help (LIT-12011964)
databases offline and basic N2 online network
setup
How to use SCT Pro, including the maintenance Metasys SCT Pro Help (LIT-12013035)
of site backups and provisioning a new network
engine
How to integrate an N2 network into the N2 Integration with the NAE Technical Bulletin
Metasys System (LIT-1201683)
Network Information (including security risks) Network and IT Guidance Technical Bulletin
(LIT-12011279)
How to apply and engineer a Metasys Smoke Metasys System UL 864 10th Edition UUKL/ORD-
Control System that complies with the Metasys C100-13 UUKLC Smoke Control System Technical
System UL 864 10th Edition UUKL/ORD-C100-13 Bulletin (LIT-12012487)
UUKLC Smoke Control Listing
Devices and logic used to implement a 10th Metasys System UL 864 10th Edition UUKL/
Edition Smoke Control System for Single Story ORD-C100-13 UUKLC Standard Smoke Control
Mall, Warehouse, and Multistory Building Applications Application Note (LIT-12012544)
How to integrate a fire system into the Metasys Metasys System Extended Architecture Fire System
network Integration Using the IFC BACnet® Gateway
Application Note (LIT-1201993)
SNE/SNC compliance with American National SNE/SNC Protocol Implementation Conformance
Standards Institute (ANSI)/American Society Statement (LIT-12013355)
of Heating, Refrigerating, and Air-Conditioning
Engineers (ASHRAE) Standard 135-2004,
BACnet® Protocol
NAE55 compliance with American National NAE55 Protocol Implementation Conformance
BACnet® Protocol
NAE85 compliance with American National NAE85 Protocol Implementation Conformance
BACnet® Protocol
How to install the Launcher Software Launcher Installation Instructions (LIT-12011783)
How to use the Launcher Software to shorten Launcher Tool Help (LIT-12011742)
the UI access time and manage sites

How to create and modify users and roles, Security Administrator System Technical Bulletin
configure user profiles, assign system access (LIT-1201528)
permissions, assign All Items Navigation View
permissions, and unlock user accounts
How to set up an MS/TP Communications Bus MS/TP Communications Bus Technical Bulletin
(LIT-12011034)
BACnet/IP configuration Metasys IP Networks for BACnet/IP Configuration
Guide Technical Bulletin (LIT-12012458)
How to set up an NAE as a BACnet/IP or BACnet BACnet Controller Integration with NAE/NCE/ODS
MS/TP system integrator in a Metasys network Technical Bulletin (LIT-1201531)
How to set up an NAE or LCS85 as a LonWorks LonWorks Network Integration with NAE and LCS
network integrator Technical Bulletin (LIT-1201668)
How to configure and enable the Demand DLLR Technical Bulletin (LIT-12011288)
Limiting and Load Rolling (DLLR) features on the
system
How to use CCT Software Controller Tool Help (LIT-12011147)
ZFR1800 Series Wireless Field Bus System ZFR1800 Series Wireless Field Bus System Technical
Bulletin (LIT-12011295)
WNC1800/ZFR182x Pro Series Wireless Field Bus WNC1800/ZFR182x Pro Series Wireless Field Bus
System System Technical Bulletin (LIT-12012356)
TEC Wireless Thermostat Controller System TEC Series Wireless Thermostat Controller System
Technical Bulletin (LIT-12011414)
WRS Series Many-to-One Wireless Room WRS Series Many-to-One Wireless Room
Temperature Sensing System Temperature Sensing System Technical Bulletin
(LIT-12011094)
TE-7800 Series One-to-One Wireless Room TE-7800 Series One-to-One Wireless Room
Temperature Sensing System Temperature Sensing System Technical Bulletin
(LIT-12011097)
WRZ-7850 One-to-One Wireless Room WRZ Series One-to-One Wireless Room Sensing
Temperature Sensing System System Technical Bulletin (LIT-12011641)
Product warranty
This product is covered by a limited warranty, details of which can be found at
www.johnsoncontrols.com/buildingswarranty.
Software terms
Use of the software that is in (or constitutes) this product, or access to the cloud, or hosted
services applicable to this product, if any, is subject to applicable end-user license, open-
source software information, and other terms set forth at www.johnsoncontrols.com/
techterms. Your use of this product constitutes an agreement to such terms.

Patents
Patents: https://jcipat.com
Contact information
Contact your local branch office: www.johnsoncontrols.com/locations
Contact Johnson Controls: www.johnsoncontrols.com/contact-us

© 2021 Johnson Controls. All rights reserved. All specifications and other information shown were current as of document
revision and are subject to change without notice.

Metasys System Configuration Guide: Building Technologies & Solutions 2021-01-12 LIT-12011832 Release 11.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Metasys System Configuration Guide: Building Technologies & Solutions 2021-01-12 LIT-12011832 Release 11.0

Uploaded by

Copyright:

Available Formats

Metasys System Configuration Guide

Building Technologies & Solutions LIT-12011832

Metasys System Configuration Guide 3

4 Metasys System Configuration Guide

Metasys System Configuration Guide 5

6 Metasys System Configuration Guide

The following information is new or revised:

Metasys System Configuration Guide 7

Figure 1: Example Metasys System Configuration

8 Metasys System Configuration Guide

CG/CV Equipment Controller family

Metasys System Configuration Guide 9

Figure 3: Expansion I/O modules

Table 2: New expansion I/O modules

10 Metasys System Configuration Guide

Field Equipment Controllers (FEC)

Metasys System Configuration Guide 11

VMA VAV Modular Assembly Series

12 Metasys System Configuration Guide

Expansion input and output (I/O) modules

Metasys System Configuration Guide 13

• CG series General Purpose Application Equipment Controllers

• SNE series Network Engines

14 Metasys System Configuration Guide

Controller Configuration Tool (CCT)

• Advanced Application Field Equipment Controllers (FACs)

Metasys System Configuration Guide 15

TEC3x00 Series Networked Thermostat Controllers

• local hydronic reheat valves

16 Metasys System Configuration Guide

• Network Automation Engines: NAE35 and NAE45

• Network Automation Engine: NAE55

Metasys System Configuration Guide 17

Figure 4: SNE series network engines

The following table outlines the SNE models in more detail.

Table 4: SNE series network engine details

18 Metasys System Configuration Guide

Metasys System Configuration Guide 19

• BACnet MS/TP Field Controller (FC) Bus

20 Metasys System Configuration Guide

SNC Series Network Control Engines

• CGM series general purpose application equipment controllers

Figure 5: SNC series network control engines

Metasys System Configuration Guide 21

Table 6: SNC series Network Control Engines details

22 Metasys System Configuration Guide

Metasys System Configuration Guide 23

24 Metasys System Configuration Guide

Network Engine Comparison

Metasys System Configuration Guide 25

Table 8: Network Engine integrations available by Metasys Release

26 Metasys System Configuration Guide

• supports a greater number of engines as a Site Director than an engine supports

Metasys System Configuration Guide 27

28 Metasys System Configuration Guide

Metasys System Configuration Guide 29

ADS/ADX concurrent users

30 Metasys System Configuration Guide

Metasys System Configuration Guide 31

32 Metasys System Configuration Guide

• Fault Detection—identifies and lists building system-related faults in order of severity to

Metasys System Configuration Guide 33

• pop-up alarm windows