12011832-System Configuration Guide

Metasys System Configuration Guide
Building Technologies & Solutions LIT-12011832

www.johnsoncontrols.com
2023-06-01 Release 12.0.50
2 Metasys System Configuration Guide
Contents
Metasys System Configuration Guide introduction..................................................................................... 7
Contents
Summary of changes............................................................................................................................ 7
Metasys system................................................................................................................................................ 7
Equipment Controllers.......................................................................................................................... 8
CG series and CV series Equipment Controllers.......................................................................................9
Advanced Application Field Equipment Controller (FAC)...................................................................... 11
Field Equipment Controllers (FEC)........................................................................................................... 12
FEC Field Equipment Controller family comparison.............................................................................. 12
VMA VAV Modular Assembly Series......................................................................................................... 13
Expansion input and output (I/O) modules............................................................................................14
Wireless solutions...................................................................................................................................... 15
Controller Configuration Tool (CCT).................................................................................................. 15
TEC3x00 Series Networked Thermostat Controllers....................................................................... 16
Network Engines..................................................................................................................................17
SNE Series Network Engines.....................................................................................................................18
SNC Series Network Control Engines...................................................................................................... 21
NAE Series Network Automation Engine................................................................................................ 24
NCE Series Network Control Engine........................................................................................................ 25
Network Engine comparison.................................................................................................................... 25
Vendor integrations on engines...............................................................................................................26
Servers.................................................................................................................................................. 27
Application and Data Server (ADS) and ADS-Lite................................................................................... 27
Server comparison..................................................................................................................................... 28
Extended Application and Data Server (ADX)......................................................................................... 29
Open Application Server (OAS).................................................................................................................31
LCS85 LonWorks® Control Server............................................................................................................33
User Interface.......................................................................................................................................33
Tools...................................................................................................................................................... 34
Launcher......................................................................................................................................................34
System Configuration Tool (SCT)..............................................................................................................34
System Configuration Tool Pro (SCT Pro)................................................................................................35
Metasys Database Manager..................................................................................................................... 36
VMD Generator Express (VGE Tool)......................................................................................................... 36
Metasys system capabilities............................................................................................................... 37
Site Director................................................................................................................................................ 37
Time management.....................................................................................................................................37
System navigation......................................................................................................................................37
Monitoring and commanding.................................................................................................................. 38
Preferences................................................................................................................................................. 38
Alarm and event management.................................................................................................................38
Encrypted communication........................................................................................................................ 39
Destination Delivery Agents (DDA).......................................................................................................... 40
Metasys System Configuration Guide 3

Syslog DDA.................................................................................................................................................. 40
Encrypted email..........................................................................................................................................40
Scheduling...................................................................................................................................................41
Historical Data Management (Trend)...................................................................................................... 41
System security...........................................................................................................................................41
Logic Connector Tool (LCT)....................................................................................................................... 44
Interlock object...........................................................................................................................................44
Optimal Start...............................................................................................................................................44
Demand Limiting and Load Rolling......................................................................................................... 44
Audit Trails (Transaction Data Management).........................................................................................44
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...................................... 46
Active Directory Federation Service (ADFS) two-factor authentication............................................... 47
Reporting capabilities......................................................................................................................... 47
Metasys Export Utility Software............................................................................................................... 47
Metasys Advanced Reporting System..................................................................................................... 48
Energy Essentials........................................................................................................................................48
Metasys graphics options................................................................................................................... 48
Metasys UI Graphics.................................................................................................................................. 48
Standard Graphics......................................................................................................................................49
Integrations.......................................................................................................................................... 49
BACnet/SC integration...............................................................................................................................49
BACnet/IP integration................................................................................................................................50
MS/TP communications bus..................................................................................................................... 50
N2 field bus................................................................................................................................................. 51
N1 integration (Release 9.0 or earlier).................................................................................................... 51
LonWorks.................................................................................................................................................... 51
Modbus........................................................................................................................................................51
M-Bus...........................................................................................................................................................51
KNX...............................................................................................................................................................51
C•CURE 9000 Access Control..................................................................................................................... 51
victor Video Management.........................................................................................................................51
Simplex Fire system................................................................................................................................... 52
Cree and Molex lighting systems............................................................................................................. 52
Zettler Fire Panels...................................................................................................................................... 52
OPC Unified Architecture (UA)..................................................................................................................52
MQ Telemetry Transport (MQTT)............................................................................................................. 52
Metasys system revision compatibility overview.............................................................................52
General compatibility information for customer job sites....................................................................53
Compatibility rules for CCT and field controller revisions.....................................................................53
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
WRG1830/ZFR183x Pro Series Wireless Field Bus System.....................................................................55
LCS85 compatibility.................................................................................................................................... 55
Metasys system configuration examples......................................................................................... 55
Multiple network engine system configuration with one network engine designated
as the Site Director.....................................................................................................................................55
Open Application Server (OAS) system configuration...........................................................................56
Metasys Server Site Director with multiple network engines system configuration.........................57
ADX unified or split configuration............................................................................................................57
Unified and split ADX with dual network cards...................................................................................... 59
Large ADX site configuration.................................................................................................................... 60
BACnet/IP network system configuration...............................................................................................61
BACnet/SC network system configuration..............................................................................................62
Third-party network integration.............................................................................................................. 63
Wireless Metasys system configurations................................................................................................ 64
Smoke Control application configuration............................................................................................... 65
Performance guidelines and limitations...........................................................................................66
Advanced Security Enabled attribute...................................................................................................... 66
Site Director limitations and recommendations.................................................................................... 66
Network OAS and engine hardware limitations.....................................................................................70
Alarm and trending performance guidelines......................................................................................... 71
MS/TP performance guidelines................................................................................................................72
SCT limitations............................................................................................................................................ 72
Equipment controller integration considerations..................................................................................73
Transfer to device (download) limitations.............................................................................................. 74
Technical specifications and requirements.................................................................................................75
Hardware configuration requirements.............................................................................................75
Client computer requirements for UI client devices....................................................................... 76
Application and Data Server (ADS) system requirements..............................................................77
Extended Application and Data Server system requirements (Unified 10 or 25
User ADX)................................................................................................................................... 79
Extended Application and Data Server system requirements (Split 10 or 25 User ADX)............82
Extended Application and Data Server system requirements (Unified 50 or 100
User ADX)................................................................................................................................... 84
Extended Application and Data Server system requirements (Split 50 or 100 User ADX)..........87
OAS technical specifications...............................................................................................................90
Application and Data Server Lite system requirements................................................................. 92
SCT Technical Specifications...............................................................................................................94
CCT technical specifications............................................................................................................... 96
SNC technical specifications............................................................................................................... 97
SNE technical specifications............................................................................................................. 101
LCS85 technical specifications..........................................................................................................104
Technical specifications - NCE25, NAE35, and NAE45 models......................................................105
Technical specifications.................................................................................................................... 108

Metasys system related documentation................................................................................................... 111
Product warranty..........................................................................................................................................115
Software terms............................................................................................................................................. 115
Patents...........................................................................................................................................................115
Contact information.....................................................................................................................................115

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 54 at the end of this document.
Summary of changes
The following information is new or revised:
• Updated CG series and CV series Equipment Controllers to include MVE specific details.
• Updated Network Engines to add details to the engine descriptions.
• Updated User Interface to update table for Interface support at Release 12.x.
• Added new row to Release table in System Configuration Tool (SCT).
• Added Alarm Notification Bar information to Alarm and event management.
• Added OAS to Network OAS and engine hardware limitations.
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 (SMP) UI. You can configure the primary network and monitor the users of
all devices on the network with the SMP 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), and Open Application Servers (OAS), which are described
in further detail in this document. Metasys servers provide the same SMP UI as the engines.
Additionally, the Metasys UI is installed with the Metasys server software.
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 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 (CG series), VAV Box Controllers (CV series), Advanced Application
Field Equipment Controllers (FACs), Field Equipment Controllers (FECs), Variable Air Volume
Modular Assembly (VMAs), Input/Output Modules (IOMs), and Expansion Input/Output Modules
(XPMs). 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 series and CV series Equipment Controllers
At Releases 10.0, 11.0, and 12.0, we introduced the first members of a new, modernized equipment
controller family that succeeds our FEC/FAC/VMA series equipment controller family. This
modernized family shares similar design details, including the following:
• Modernized packaging and styling
• Removable screw terminal blocks
• Decimal MS/TP address set with three rotary switches
• More memory and faster processor
• Background file transfer
• Improved SA Bus commissioning
• Models with BACnet MS/TP and N2 networking with auto-detect (CGM and CVM models)
• Models with BACnet/IP and BACnet/SC networking (CGE and CVE models)
Note: The CGE and CVE models can act as BACnet/SC nodes.
• Models with an onboard display and keypad
• Device Security (CGE and CVE models)
• FIPS 140-2 Level 1 Compliance (CGE and CVE models)
• Wireless ZFR and ZFR Pro support
Figure 2: CG series and CV series equipment controllers and XPM expansion modules
The following table outlines the CG series and CV series controllers in more detail.
Table 1: CG series and CV series controllers details
CGM04060-0 CGE04060-0 CGM09090-0 CGE09090-0 CVM03050-0 CVM03050-0P CVE03050-0P
CGM09090-0H CGE09090-0H
Description General Purpose Application Controller VAV Box Controller
Inputs and 10 total: 18 total: 8 total: 8 total:
Outputs • 3 Universal Inputs (UIs) • 7 UIs • 3 UIs • 3 UIs
• 1 Binary Input (BI) • 2 BIs • 2 COs • 2 COs
• 4 Configurable Outputs (COs) • 4 COs • 3 BOs • 3 BOs
• 2 Binary Outputs (BO) • 3 BOs • Integral actuator • Integral actuator
• 2 Analog Outputs (AOs) • Integral DPT • Integral DPT
• Integral potentiometer to sense
actual VAV box damper position

Table 1: CG series and CV series controllers details
CGM04060-0 CGE04060-0 CGM09090-0 CGE09090-0 CVM03050-0 CVM03050-0P CVE03050-0P
CGM09090-0H CGE09090-0H
Communic- • FC Bus (BACnet BACnet/IP and • FC Bus BACnet/IP and • FC Bus (BACnet MS/TP) BACnet/IP and
ation MS/TP) BACnet/SC (BACnet MS/ BACnet/SC • N2 (software switchable) BACnet/SC
Protocols • N2 (software TP) • Zigbee for ZFR Pro Wireless Field Bus (add
switchable) • N2 (software on modules)
• Zigbee for ZFR switchable)
Pro Wireless • Zigbee for ZFR
Field Bus (add on Pro Wireless
modules) Field Bus (add
on modules)
Expandable Yes
through SA
Bus
Onboard Yes
Real Time
Clock
In addition, Release 12.0 included a new, remote-mountable color display that communicates to an
equipment controller over the SA Bus.
Figure 3: Remote mountable display
Table 2: Remote mountable display

Model number M4-DLK0350-0
Description Remote mountable display/keypad
Display details 3.5-inch, 320 x 240 resolution, color display
Keypad details Seven pushbuttons: up, down, left, right, OK, menu, and back
Mounting style Panel and surface mountable and portable
Power source Can be powered by controller over SA bus or powered externally
using 12 VDC external power supply.
Compatibility Connects to and communicates on the SA bus of the following
compatible devices:
• CG and CV series equipment controllers
• FAC, FEC, and VMA series equipment controllers
• SNC series network control engines
• NCE series network control engines

Table 2: Remote mountable display
Model number M4-DLK0350-0
Capabilities • Monitoring point values and status
• Viewing alarms and trends
• Overriding outputs
• Adjusting setpoints and parameters
Succeeds MS-DIS1710-0
The following figure and table outline the I/O expansion modules, first introduced at Release 11.0.
Figure 4: Expansion I/O modules
Table 3: 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 or
XPM 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 FAC3613-0 model includes 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 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 and BACnet/SC 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. 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 or XPM 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 4: 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:
• Rooftop Units • Equipment that requires • Pressure
• Heat Pumps local scheduling, independent VAV
alarming, and trending boxes
• Unit Ventilators
• Air Handling Equipment • Pressure
• Air Handling
• Central Plant Equipment dependent VAV
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

Table 4: Field Equipment Controller family comparison
Advanced Application Variable Air
Field Equipment
Field Equipment Volume Modular
Controllers (FECs)
Controllers (FACs) Assemblies (VMAs)
Communication • BACnet MS/TP (B- • BACnet MS/TP (B-AAC) or • BACnet MS/TP (B-
protocol ASC) or N2 (field N2 (field switchable) ASC) or N2 (field
switchable) • BACnet/IP (B-AAC) switchable)
• ZigBee Wireless (model IP FAC4911 only) • BACnet/IP (B-
(with an add-on • BACnet/SC (B-AAC) AAC): (model IP
module) (model IP FAC4911 only) VMA1930 only)
• ZigBee Wireless (with an • BACnet/SC (B-
add-on module) AAC): (model IP
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
Note: You can upgrade existing VMA1930 units in the field to support BACnet/SC, but this
model is discontinued from manufacturing.
VMA VAV Modular Assembly Series

VMA16 (32-bit) VAV Modular Assembly
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' 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.
VMA1832 (32-bit) VAV Modular Assembly
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 and BACnet/SC 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. 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

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
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, VMA17, 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
• 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).
IOM series expansion I/O modules
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, CGE, CVM, CVE, 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, CGE, CVM, CVE, 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.
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
• WRG1830/ZFR183x Pro Series Wireless Field Bus with Wireless TEC31xx Series Thermostats
• 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:
• FAC series Advanced Application Field Equipment Controllers
• FEC series Field Equipment Controllers
• VMA series VAV Box Controllers
• VAV series VAV Box Controllers
• XPM series I/O Expansion Modules
• IOM series I/O Expansion Modules
• NCE series Network Control Engines

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 box 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.
Note: ZCT is not compatible with the WRG1830/ZFR183x Pro Series.
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 the latest CCT Release, 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/TEC3100 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 equipment controllers:
• General Purpose Application MS/TP Controllers (CGMs)
• General Purpose Application Ethernet Controllers (CGEs)
• VAV Box MS/TP Controllers (CVMs)
• VAV Box Ethernet Controllers (CVEs)
• 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 the following types:
SNE Series Network Engines
SNE series network engines were initially introduced at Release 10.1 and are intended to succeed
the NAE and NIE series network engines. Includes models SNE1050x, SNE1100x, SNE110Lx, and
SNE220x.
SNC Series Network Control Engines
SNC series network control engines were initially introduced at Release 10.1 and are intended to
succeed the NCE and NIE29 series network control engines. Includes models: SNC1612x-xxx and
SNC2515x-xxx
NxE35/NxE45/NxE55 Series Network Automation Engines

The NAE55 and NIE55 series network automation engines were initially introduced as part of the
original Metasys System Extended Architecture (MSEA) back in 2003, and this series has been
expanded to include the NAE35, NAE45, NIE39, NAE45, and NIE49 series, and they have been
updated regularly since then. The NAE35/NAE45/NAE55 series and their NIE variants are now at
End-of-Life, but they can still be incorporated into the Metasys system architecture.
NCE Series Network Control Engines
The NCE series network control engines were initially introduced at Release 3.0, and this series has
been expanded and updated regularly since then. The NCE series (and NIE29 variants) are now at
End-of-Life, but they can still be incorporated into the Metasys system architecture.
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

The SNE series network engines are the most recent family of network engines in the Metasys
building automation system portfolio.
Figure 5: SNE series network engines
The following table outlines the SNE models in more detail.

Table 5: SNE series network engine details: SNE2200x, SNE1100x, SNE1050x, SNE110Lx
Features SNE2200x SNE1100x SNE1050x SNE110Lx
11
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 USB ports
22 • 2 USB ports
Maximum number 3 2 2 0
of child engines
when acting as a
Site Director

11
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/SC 1 1 1 1
maximum trunks
BACnet/SC 150 100 50 10
maximum devices
3
per trunk
BACnet MS/TP 2 1 1 1
maximum trunks
BACnet MS/TP 100 100 50 100
maximum devices
per trunk (Johnson
Controls devices
only)
Note: A
repeater is
required if
more than 50
Johnson Con-
trols devices
are on the
same trunk.
maximum devices
per trunk (with
third party)
Note: A
repeater is
required if
more than 32
devices are on
the same trunk
and some are
third party.
N2 maximum 2 1 1 N/A
trunks

11
Mapped N2 devices 100 100 50 N/A

per trunk
Note: A
repeater is
required if
more than 50
devices are on
the same trunk.
LonWorks 1 1 1 N/A
maximum trunks
LonWorks 255 127 60 N/A
maximum devices
Remote Field Bus 6 3 3 N/A
maximum trunks
maximum Johnson
Controls Devices
per bus
maximum devices
per bus (with third-
party devices)
Maximum objects 5000 2500 2500 2500
44
in device
Supported type of • ADS • ADS • ADS ADS-Lite-A only
parent server • ADX • ADX • ADX
• OAS • ADS-Lite-E • ADS-Lite-E
• OAS • OAS

11
Supported • BACnet/SC
integrations • BACnet/IP
- 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 (OPCUA/UA)
• MQ Telemetry Transport (MQTT)
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 Multiple IP integrations can be on an engine, including BACnet/IP and BACnet/SC, but this is limited by the maximum
devices that can be mapped to a trunk. The total number of BACnet/IP or BACnet/SC devices that you can map is 150.
You cannot map 150 IP and 150 SC devices at the same time because they use the same BACnet Integration object.
4 Suggested object limit for performance considerations.
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:
• 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 6: SNC series network control engines
The following table outlines the SNC models in more detail.

Table 6: SNC series Network Control Engines details
Features SNC2515x-0 SNC2515x-04 SNC1612x-0 SNC1612x-04
SNC2515x-0H SNC2515x-04H SNC1612x-0H SNC1612x-04H
Succeeds NCE25 Series NCE25 Series NCE25 Series NCE25 Series
Onboard inputs and • 40 total onboard I/O: 14 UI, 11 • 28 total onboard I/O: 10 UI, 6 BI, 4
outputs BI, 4 CO, 4 AO, 7 BO CO, 4 AO, 4 BO
• Supports SA Bus expansion • Supports SA Bus expansion
Communication • 1 Ethernet port: SNC25150-0, SNC25150-04, SNC16120-0, SNC16120-04,
interfaces SNC25152-0, SNC25152-04, SNC25152-0H, SNC25152-04H, SNC16122-0,
SNC16122-04, SNC16122-0H, and SNC16122-04H
• 2 Ethernet ports: SNC25151-0, SNC25151-0H, SNC25151-04,
SNC25151-04H, SNC16121-0, SNC16121-0H, SNC16121-04, SNC16121-04H
• 1 RS-485 port
11
• 2 USB ports for connecting external integration adapters
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
BACnet/SC 1 1 1 1
maximum trunks
BACnet/SC 50 4 50 4
maximum devices
per trunk
maximum trunks

maximum devices
per trunk (Johnson
Controls devices
only)
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 60 4
devices per trunk
LON maximum 1 1 1 1
trunks
Remote Field Bus 3 3 3 3
22
maximum trunks
maximum Johnson
Controls Devices
per bus
maximum devices
per bus (with 3rd
party devices)
Maximum objects 2500 2500 2500 2500
33
in device
Supported type of • ADS
parent server • ADX
• ADS-Lite-E
• OAS

Supported • BACnet/SC
integration drivers • BACnet/IP
- 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
• MQ Telemetry Transport (MQTT)
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.
NAE Series Network Automation Engine

The NAE is available in many different models with options to support various communications
protocols including BACnet/SC (NAE85 and NAE55xx-3 only), BACnet/IP, BACnet® MS/TP, N2 Bus,
N2 over Ethernet, and LonWorks® protocol. Built-in support for third-party protocols, including
Modbus, M-Bus, KNX, C•CURE-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 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.

From Release 12.0, the NAE85 supports BACnet/SC and can act as a Primary Hub, Failover Hub,
or Node in the BACnet/SC network topology. You need to purchase the M4-BACNETSC-0 add-on
license to use BACnet/SC. For more information about BACnet/SC, refer to BACnet/SC Workflow
Technical Bulletin (LIT-12013959).
Note: At Release 12.0, an NAE85 can act as a Site Director only. Do not upgrade any child
NAE85s to 12.0.
Note: 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 Series Network Control Engine

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 or Release 10.0 Release 10.1 Release 11.0 Release 12.x
later
NCE25 Succeeded by SNC models, but NCE25
X X
11
continues to ship out of factory at Release 9.0.7.
NAE35, NAE45 The SNE1050x succeeds the NAE35 series and the SNE1100x
X X
22 succeeds the NAE45 series, but NAE35 and NAE45
series continue to ship out of factory at Release 9.0.7.
NAE55 X X
33
X
44
X
55
X
66
NAE85 X X X X X
77
NIE29, NIE39,
X X
88 Discontinued Discontinued Discontinued
NIE49
NIE59 X X X X
Important: All NIEx9 models have been discontinued from
X 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, 11.0, and 12.0 respectively.
NIE89 X X X X
Important: All NIEx9 models have been discontinued from
X 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, 11.0, and 12.0 respectively.
NIE55, NIE85 X
SNE X X X
SNC X X X
1 Only NCE25xx-0 is available to upgrade to Metasys 9.0.7 or later with Linux OS.
2 Only NAE35xx-2 and NAE45xx-2 are available to upgrade to Metasys 9.0.7 or later with Linux OS.
3 Only NAE55xx-2 and NAE55xx-3 are available to upgrade to Metasys 10.0 with Linux OS.
6 Only NAE55xx-3 is available to upgrade to Metasys 12.0 with Linux OS.
7 At 12.0, an NAE85 can act as a Site Director only. Do not upgrade any child NAE85s to 12.0.

8 Only NIE29xx-0s, NIE39xx-2, and NIE49xx-2 are available to upgrade to Metasys 9.0.7 or later with Linux OS.
Table 8: Network Engine integrations available by Metasys Release

Integration Release Release Release Release Release Release
9.0 9.0.7 or 10.0 10.1 11.0 12.0
later
BACnet/SC X
11
MQTT X
22
BACnet/IP X X X X X X
BACnet MS/TP X X X X X X
Legacy N1 LAN X
Legacy N2 Bus X X X X
33
X
3
LonWorks X X X
44
X
4
Modbus RTU and TCP X X X X X X

KNX IP X X X X X X
M-Bus Serial and IP X X X X X X
C•CURE-victor X X X X
Simplex Fire (secondary X
X X X
monitoring only)
Preferred Vendor X
X X X
Lighting Systems
Zettler Fire Panel X X X
OPC Unified X
X
Architecture (OPC UA)
WRS-RTN Wireless X
Supervisor
1 NAE85, NAE55xx-3, SNEs, and SNCs support BACnet/SC.
2 MQTT is supported only on the SNC and SNE series engines from Release 12.0.
3 The M4-SNE110Lx-0 model does not support the N2 Bus.
4 The M4-SNE110Lx-0 model does not support LonWorks.
Vendor integrations on engines

The maximum number of simultaneous integrations supported on an engine depends on the
processing capabilities of the engine's platform.
An NAE8500 or an OAS that runs on an appropriately resourced platform can simultaneously
support a maximum of eight vendor-based integrations. All NAE and SNx based engines can
simultaneously support a maximum of two vendor-based integrations. Embedded platforms like
the NAE and the SNx based engines tend to be resource constrained, so some protocols like KNX,
C•CURE-victor, OPC UA, and Zettler can be impacted if they are combined with other vendor-based
integrations. Combinations like KNX + Modbus are not supported on these type of engine models
and can result in unexpected behavior, if implemented. The following table shows the maximum
number of simultaneous integrations that are supported on an NAE or SNx based engine.

Table 9: Maximum number of simultaneous integrations that are supported on an NAE or SNx
based engine
Vendor integration type Maximum number of supported simultaneous
integrations (standard protocol drivers)
Modbus (TCP or RS-485) 2
M-Bus 2
KNX 1
C•CURE-victor 1
OPC Unified Architecture (UA) 1
Zettler 1
Servers
Application and Data Server (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 the following:
• a greater number of engines as a Site Director than an engine 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
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 10: Metasys Server family comparison
Feature Application and Data Server Extended Application and Data Open Application Server (OAS)
(ADS) Server (ADX)
Host Platform Desktop computer platform: Server platform: Turnkey and virtual desktop
• Microsoft Windows® • Microsoft® Windows Server® platform (virtual machine (VM)):
operating system operating system • Microsoft Windows®
• Microsoft SQL Server • Microsoft SQL Server operating system
Express database database • Microsoft SQL Server
• Open Database Express database
Connectivity (ODBC) • Open Database Connectivity
compliant database (ODBC) compliant database
package package
Virtual server platform (VM):

• Microsoft® Windows
Server® operating system
• Microsoft SQL Server
database
Supported Up to 5 users Up to 10, 25, 50, or 100 users Up to 5 users
Simultaneous Users (license specific)
Network Engine Up to 14 engines Up to 1,000 engines OASMIN: 0 engines
Management
Note: Support for engines OASSTD: up to 2 engines
varies depending on size of
server hardware.
Direct BACnet Device No No Yes, BACnet/IP and BACnet/
Management SC devices can be managed
directly. BACnet MS/TP devices
can be managed by using a
BACnet/IP to MS/TP router. A
maximum of 200 devices are
supported.
Archival of Historical Manual, scheduled, or Manual, scheduled, or automatic Manual, scheduled, or automatic
Data automatic
Note: You need to
purchase the Metasys
Historical Data add-on
license to use this feature.
User Interface Metasys UI Metasys UI Metasys UI
SMP SMP SMP
Supports Export Utility Yes Yes No
Supports Metasys No Yes No
Advanced Reporting
Supports Energy
Note: Energy Essentials is discontinued from Release 12.0.
Essentials
Support for Split No Yes No
Configuration
Supports Metasys No Yes No
for Validated Metasys UI
Environments (MVE) SMP
Note: You need to
purchase the MVE add-on

Table 10: Metasys Server family comparison
Feature Application and Data Server Extended Application and Data Open Application Server (OAS)
(ADS) Server (ADX)
Five Years of Historical Yes Yes Yes
Data in Metasys UI
Note: You need to
purchase the Metasys
Historical Data add-on
Supports Metasys Yes Yes Yes
Database Manager
Supports Fault Yes Yes Yes
Detection and Fault
Note: At a minimum,
Triage features you require 8GB of RAM
and four virtual cores
to support the Fault
Detection and Fault Triage
features on an OAS.
Note: You need to purchase the Fault Detection and Fault Triage add-on licenses to use
these features.
FIPS 140-2 Level 1 Yes Yes Yes
compliance
ADFS two-factor Yes Yes Yes
authentication Note: ADFS authentication is available to Metasys UI users, but is not available to Metasys
SMP users.
Supports BACnet/SC Yes Yes Yes
Note: You need to purchase the M4-BACNETSC-0 add-on license for each Server to use
BACnet/SC.
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).
Extended Application and Data Server (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.
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.
ADS/ADX concurrent users

Use the following table to help you determine the 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 to the Metasys UI and SMP.
Note: The following information provides the supported concurrent user limitations. Usage
beyond the supported limitations may yield system or server performance issues.
Table 11: Examples of Metasys Server concurrent users
ADS/ADX type Examples of ADS/ADX concurrent users
SMP UI Metasys UI
1
5-user ADS/ADS-Lite/OAS 0 5
2 3
5 0
10-user ADX 0 25
22
5 20
8 17
10 15
25-user ADX 0 25
10 15
20 5
25 0
50-user ADX 0 50
10 40
25 25
50 0
100-user ADX 5 50
33
10 50
3
25 50
3
50 50
3
75 25
100 0
1 Metasys UI includes users logged-in to Metasys UI, as well as any Metasys API users.
2 The 10-user ADX has an SMP 10 concurrent user limitation. The Metasys UI concurrent user limitation is 25.
3 The 100-user ADX has an SMP 100 concurrent user limitation. The Metasys UI concurrent user maximum is 50.
For example, as shown in Table 11, 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.

Open Application Server (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.
There are two licensing options available for the OAS, the OAS Minimum (M4-OASMIN-0) and the
OAS Standard (M4-OASSTD-0). The OAS Minimum is a variant of the OAS offering whose capabilities
are license-limited. The OAS Minimum cannot supervise child network engines unless a migration
license (M4-OASSTD-8) is purchased. The OAS Minimum is offered at a lower price point than the
OAS Standard. This provides an affordable Server option for smaller or less complex projects. For
more information about the OAS versions, see the following table:
Table 12: OAS versions
Features OAS Minimum OAS Standard
Supports Metasys UI Yes Yes
Supports engines No Two
Can license add-ons Yes Yes
Note: Fault Detection and
Fault Triage are not sup-
ported on the turnkey
solution.
Direct support for field devices 200 200
Supports SMP Yes Yes
Note: Do not install SCT or CCT on the OAS Turnkey computer. If you need SCT or CCT for
commissioning the job site, install the tools on a different computer with network accessibility
to the OAS. However, if you host the OAS on a virtual machine (VM), you can install SCT and
CCT on the same VM as the OAS software.
As a Site Director, the OAS Standard supports up to two supervisory devices, 200 field devices, and
20,000 objects using BACnet/IP and Remote Field Bus integrations. The OAS supports integration
with the following devices and systems: C•CURE-victor, Modbus, M-Bus, KNX, and OPC Unified
Architecture (UA).
The maximum number of supported simultaneous vendor integrations on an OAS is 8. The
following table provides more information about the available integrations, whereby the limits
relate to standard protocol drivers only.
Table 13: Vendor integration types and numbers
Vendor integration type Maximum number of supported
simultaneous integrations (standard
protocol drivers)
Modbus (TCP or RS-485) 4
M-Bus 4
KNX 2
C•CURE-victor 1

Table 13: Vendor integration types and numbers
Vendor integration type Maximum number of supported
simultaneous integrations (standard
protocol drivers)
OPC Unified Architecture (UA) 1
Zettler Not supported. Zettler requires a serial
connection. Serial connection is not supported
on the OAS and the Zettler driver is not included
in the OAS platform. The Zettler driver is
included only in engines with Linux-based
platforms.
The OAS provides database software options for archiving licensed historical data using the
Microsoft® SQL Server software database, and it enables secure communication to a range of
Network Engines, including the NAEs, NCEs, SNEs, and SNCs. The OAS is compatible with both
Metasys UI and Site Management Portal (SMP). You can configure the OAS through the System
Configuration Tool (SCT).
The following table provides a summary of the OAS Standard capabilities:
Table 14: OAS Standard capabilities
ADS-type capabilities Network Engine-type capabilities
Supports supervising up to two network engines Supports supervising up to 200 field devices
(SNE, SNC, NAE, or NCE Series). directly or 20,000 objects, using BACnet/IP and
Remote Field Bus integrations.
Provides the Metasys UI, an intuitive, well- Provides supervisory capabilities such as
organized, mobile-friendly user interface. scheduling, alarming, trending, data sharing,
interlocking, and logic for system-wide control
and coordination.
Optionally (with add-on licenses) provides long
term archival of historical data, trends, alarms,
and events.
Figure 7: OAS system diagram

LCS85 LonWorks® Control Server
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.
From Release 12.0, the LCS85 supports BACnet/SC and can act as a Primary Hub, Failover Hub,
or Node in the BACnet/SC network topology. You need to purchase the M4-BACNETSC-0 add-on
license to use BACnet/SC. For more information about BACnet/SC, refer to BACnet/SC Workflow
Technical Bulletin (LIT-12013959).
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.
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).
Note: From Release 12.0, Metasys UI is also supported on the NAE85 and LCS85.
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. For further information
about the SMP, refer to Metasys Site Management Portal Help (LIT-1201793).
The following table describes the offerings at Release 12.0 and if they support Metasys UI, SMP with
an add-on license, or SMP without an add-on license:
Table 15: Interface support at Release 12.x
ADX ADS OAS NAE85 SNE SNC NxE55xx-3 NxE55xx-2
ADS-Lite LCS85
SMP X
11
X
1
X
1
X
1
X X X X
1 At Release 12.0 and 12.0.50, the SMP is a separate license available on this offering only to existing Metasys sites and to
new or existing Metasys for Validated Environment (MVE) sites. If SMP is needed for this offering for an existing, non-
MVE site, it must be purchased separately. For MVE sites, the SMP license is included with the MVE license and does not
need to be purchased separately.

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 the following:
• 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,
JCT, 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-victor, 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 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), 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.7.2. 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 JCT 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.3 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 16: SCT, Metasys Server, and NAE Update Tool releases
Release Date SCT NAE Update Tool Metasys Server
October 2015 Release 7.0 Release 7.0 Release 7.0
September 2016 Release 11.0 Release 11.0 Release 8.0
February 2017 Release 11.1 Release 11.1 Release 8.1
August 2017 Release 12.0 Release 12.0 Release 9.0
December 2018 Release 13.0 Release 13.0 Release 10.0
October 2019 Release 13.2 Release 13.2 Release 10.1
October 2020 Release 14.0
11 The NAE Update Tool Release 11.0
continues to be a
November 2020 Release 14.1 Release 11.0
component of the SCT
May 2021 Release 13.3 and 14.2 install. However, we Release 11.0
May 2022 Release 15.0.1 encourage you to work Release 12.0
May 2023 Release 15.0.3 with SCT Pro instead of Release 12.0.50
the NAE Update Tool.
1 SCT 14.0 was discontinued when SCT 14.1 was released.
For a list of updated features and benefits available at the latest SCT Release, refer to the System
Configuration Tool Catalog Page (LIT-1900198).
System Configuration Tool Pro (SCT Pro)

SCT Pro is a modernized version of SCT that runs in the browser and does not require the Launcher.
SCT Pro 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 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 SCT. With each release,
features from 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 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. You can use 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
Note: SCT Pro does not have the ability to configure many complex values including but not
limited to the MVE Signature and Annotation inclusion or exclusion lists. The use of SCT pro
does not currently prevent these edits and doing so can cause archive corruption. Do not edit
any configuration data using SCT Pro until this issue is resolved.
The following table describes which specific tools and capabilities are most appropriate for each
type of network engine:
Table 17: Network Engine Re-imaging Tools
Tools to use NAE35, NAE45, NAE35, NAE45, NAE55 SNE, SNC
NCE25, NAE55 NCE25
Release 9.0 Release 9.0.7 or Release 10.0, Release 10.1,
Windows later Linux 10.1, 11.0, or 11.0, or 12.0
12.0 Linux Linux
NAE Update Tool

11 X X X —
SCT 15.0 X — X X
SCT Pro 15.0 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).

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. 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 Building Network tree in the Metasys
UI, but they do not appear in the All Items tree in SMP. To reorganize the order of objects, use
the Organize Tree feature in Metasys UI.
The SMP UI and Metasys UI support 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. At Metasys Release 12.0, use SMP or SCT to create
and modify a User View.
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 do the following:
• 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. You can configure the
routing of event messages to destinations such as the server for permanent storage. The SMP UI
features a pop-up alarms window, which alerts you to potential problems whenever you are 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.
You 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.
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. You can
retrieve and examine events stored in the Event Repository.
You 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. You 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. You can access both the Alarm Manager and the Alarm Monitor on
computer and tablet platforms. To manage alarms on phone platforms, you 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.
You can also view and manage all audits (events) and alarms that are forwarded from an engine to
the Site Director directly in Metasys UI with System Activity. The data is presented in the form of a
timeline in System Activity. Every audit and alarm instance appears in chronological order in System
Activity, including alarms that do not require acknowledgment. The alarms are not rolled up, as is
the case in Alarm Manager. The feature helps you understand changes that have occurred in the
Metasys system over a period of time, whereby you can display audits and alarms as far back as the
data set.
The Alarm Notification Bar feature in Metasys UI provides you with quick access to see and take
action on the top priority alarm that is pending your acknowledgment. This feature is similar to the
alarm pop-up in SMP.
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.
Encrypted communication
All Metasys Server based devices (ADS, ADX, and OAS) 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 and Upgrade Guide (LIT-12013222). The steps for installing trusted
certificates on network engines are described in SCT: System Configuration Tool 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, or OAS) 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 the latest
Metasys release.
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.
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)

You 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. You 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. You 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.
For more information, refer to the Metasys UI Help (LIT-12011953) or Metasys Site Management Portal
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.
You 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.
You can assign user access permissions to specific spaces and the equipment serving those spaces
with the Metasys UI Space Authorization. You 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 Active Directory Federation Service (ADFS), also provides
the ability to use Single Sign-On to access the Metasys system, together with other supported
applications on the enterprise network. ADFS authentication is available to Metasys UI users, but is
not available to Metasys SMP users.
The Audit Log and the System Activity feature record 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 18: Metasys system password rules
Supported language Enforced password rules
locale
English (en_us) • 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.
• 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) • The password must include a minimum of 8 characters and a
German (de_de) maximum of 50 characters.
Spanish (es_es) • The password cannot include spaces or include a word or phrase
French (fr_fr) that is in the Blocked Words list.
Hungarian (hu_hu) • The password and the username cannot share the same three
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) - Include at least one special character (-, ., @, #, !, ?, $, %)
Portuguese (Brazilian)
(pt_br)
Russian (ru_ru) - Include at least one lowercase character
Swedish (sv_se) - Include at least one Unicode character that is categorized as
Turkish (tr_tr) an alphabetic character but is not uppercase or lowercase
Chinese Simplified (zh_cn) • The password must include a minimum of 8 characters and a
Chinese Traditional (zh_tw) maximum of 50 characters.
Japanese (ja_jp) • The password cannot include spaces or include a word or phrase
Korean (ko_kr) that is in the Blocked Words list.
• The password and the user name cannot share the same three
consecutive characters.
• The password must meet two of the following conditions:
- Include at least one number (0–9)
- Include at least one special 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 UI or SMP UI, or offline through JCT or SCT. When you view the finished programs through
the Metasys UI, JCT, or 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.
You 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.
You 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.
You can also view audit messages in the Audit Viewer of the SMP UI. When you log in to the Site
Director, you can view all audit messages from the server or any device that contains a Local Audit
Repository. When you directly log into a device not designated as the Site Director, you 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.

You 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. You 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 and 11.0 validated engines and the
Release 12.0 MVE supported validated engines:
Table 19: MVE validated engines
Release 10.1 Release 11.0 Release 12.0
MS-NAE5510-2 MS-NAE5510-2 —
MS-NAE5510-3 MS-NAE5510-3 MS-NAE5510-3
M4-SNE22000-0 M4-SNE22000-0 M4-SNE22000-0
M4-SNE22001-0 M4-SNE22001-0
M4-SNE22002-0 M4-SNE22002-0
M4-SNC25150-0 M4-SNC25150-0 M4-SNC25150-0
M4-SNC25151-0 M4-SNC25151-0
M4-SNC25152-0 M4-SNC25152-0
M4-SNC25150-04 M4-SNC25150-04 M4-SNC25150-04
M4-SNC25151-04 M4-SNC25151-04
M4-SNC25152-04 M4-SNC25152-04
M4-SNC16120-0 M4-SNC16120-0 M4-SNC16120-0
M4-SNC16121-0 M4-SNC16121-0
M4-SNC16122-0 M4-SNC16122-0
M4-SNC16120-04 M4-SNC16120-04 M4-SNC16120-04
M4-SNC16121-04 M4-SNC16121-04
M4-SNC16122-04 M4-SNC16122-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 12.0, the validated Site Director also needs to be at 12.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.
At Release 12.0.50, MVE is only supported on an ADX server at 12.0.50 and validated engines at
Release 12.0. At Release 12.0.50, MVE also supports MVE on Metasys UI, and MVE on SMP UI.
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] 2021).

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. Three Metasys component types have been updated at Release

11.0 and Release 12.0, respectively, 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 or later 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
from Release 11.0.
• CGE and CVE series equipment controllers: FIPS 140-2 Level 1 compliance is included by
default in all CGE and CVE series equipment controllers at Release 12.0 that have 10.0 firmware.
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 20: 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 12.0. NAE85/LCS85 at at Release 12.0
FIPS 140-2 is Release 12.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 or 12.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 authentication is available to Metasys UI users, but is not available to Metasys
SMP users. 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. You can use this data to manage daily
building operations. The Metasys Export Utility software extracts historical trends, alarms, and
audit data from an engine or server. You can collect data 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 you with the ability to create runtime studies and discover root
cause analysis of system changes and mechanical equipment failures. You 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 ADX servers when using
supported SQL Server software, with SQL Server Reporting Services (SSRS) installed. The web-based
reporting interface provides standard report sets. You can review the alarm and trend configuration
of your 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. You can customize the date range and data type for each report. When a report is
created in the user interface, you 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 you can add to the Metasys Advanced
Reporting System. Energy Essentials 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: Energy Essentials is discontinued from Release 12.0.
Metasys graphics options

Metasys UI Graphics
Metasys system designers can efficiently create, edit, and manage graphics in either Metasys UI
or JCT. 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 guidelines in
the table below.
Table 21: Suggested maximum selections
Item or element Guidelines 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 For optimal performance, you should have
Metasys points no more than 200 bound Metasys points
on a single graphic, unless you are using a
Status Summary element.

Table 21: Suggested maximum selections
Item or element Guidelines Notes
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 guideline 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: For optimal performance,
images should have a maximum size
of 1,600 pixels (height) by 1,200 pix-
els (width) and 1 MB in file size. If your
images exceed these dimensions, you
may experience 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/SC integration
BACnet Secure Connect (BACnet/SC) is a recent update to the BACnet interoperability standard
aimed at improving cybersecurity and network infrastructure integrity. BACnet/SC is defined
in Annex AB of the ASHRAE 135-2020 BACnet protocol standard. BACnet/SC identifies a secure,
encrypted datalink layer specifically designed to meet the requirements, policies, and constraints of
IP networking infrastructures.
From Release 12.0, BACnet/SC is supported by the following components, when these components
are field-upgraded to or factory-shipped with Release 12.0 software:
• Application and Data Server (ADS), ADS-Lite, Extended Application and Data Server (ADX), and
Open Application Server (OAS) series application server software

• NAE85 and LCS85 series software-based network engines
Note: You need to purchase the M4-BACNETSC-0 add-on license to use BACnet/SC on the
ADS, ADS-Lite, ADX, OAS, NAE85, or LCS85.
• NAE55xx-3x, SNE, and SNC series network engines
• VMA1930, FAC4911, CGE, and CVE series IP-based equipment controllers
The primary benefits of Metasys BACnet/SC compliance include the following:
• Ensures Metasys follows the latest IT security and infrastructure protocols while still
maintaining interoperability.
• Addresses many concerns that IT departments have expressed over the original BACnet/IP
protocol.
For details about BACnet/SC, refer to the BACnet/SC Workflow Technical Bulletin (LIT-12013959).
BACnet/IP integration
BACnet/IP integration is available with a number of Metasys equipment controllers:
• CGE09090 General Purpose Application Controller
• CGE04060 General Purpose Application Controller
• CVE03050-0P VAV Box Controller with Position Feedback
• FAC4911 Advanced Application Field Equipment Controller
• VMA1930 VAV Modular Assembly Controller
Note: You can upgrade existing VMA1930 units in the field, but this model is discontinued
from manufacturing.
These controllers communicate on BACnet/IP networks and support increased network
performance, enabling faster access to data and faster troubleshooting. Metasys BACnet/IP
equipment controllers can be connected to a BACnet/IP building automation network in multiple
ways: as daisy-chained devices, as part of a star (also called home run) network, or as part of a ring
network. Daisy-chained networks require less physical wiring and new devices can be added easily
to the network. In a star network, each controller is connected by Ethernet cable directly back to a
main switch. This configuration reduces the possibility of network failure, but requires more wiring
to install. A ring network is a chain of controllers virtually closed by a software component in an
Ethernet switch. These controllers support Media Redundancy Protocol (MRP). With MRP, a ring of
Ethernet controllers can overcome a single communication failure, with a recovery time faster than
a non-ring (daisy chain or star) architecture. Most networks use combinations of these topologies.
For details, refer to the Metasys IP Networks for BACnet/IP Controllers 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. 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.
MQ Telemetry Transport (MQTT)

MQTT is an OASIS standard messaging protocol for the Internet of Things (IoT). MQTT is designed
as an extremely lightweight publish/subscribe messaging transport that is ideal for connecting
remote devices with a small code footprint and minimal network bandwidth.
From Release 12.0, the SNE and SNC series network engines include an MQTT driver that supports
bidirectional communication between network engines and a generic MQTT broker.
Metasys system revision compatibility overview

This section describes high-level revision-to-revision compatibility scenarios for customer job sites
when you upgrade to the latest Metasys release. 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, 11.0, and 12.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 12.0, this includes Releases 11.0, 10.1, and 10.0.
SCT no longer requires the same revision as the Site Director when integrated with the ADS/ADX.
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.
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 equipment
controllers 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 enables 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 JCT configuration.
Auto-Discovery of Serving Relationships uses a matching algorithm to automatically fill Serving and
Served By columns in the Equipment Discovery window. Enhancements to the Find and Replace
functionality give you increased control over Equipment Name and Equipment Descriptions to aid
in more accurate auto-discovery matches.
Equipment controller wireless integrations

The ZFR181x Series wireless system was introduced at Metasys Release 4.0.
• The ZFR181x Series wireless system connects to the network engine through the FC Bus using
BACnet MS/TP.
• 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.

WRG1830/ZFR183x Pro Series Wireless Field Bus System
The WRG1830/ZFR183x Pro Series Wireless Field Bus System was introduced at Metasys Release
11.0, but it does not require Metasys 11.0.
The WRG1830/ZFR183x Pro Series Wireless Field Bus System uses different wireless coordinators,
routers, and repeaters than the ZFR1810 Series Wireless Field Bus System and the WNC1800/
ZFR182x Wireless Field Bus System. You cannot intermix WRG/183x, WNC/182x, or ZFR181x Series
wireless devices on the same wireless PAN. However, you can have WRG/183x, WNC/182x, or
ZFR181x wireless devices on separate PANs using separate coordinators under the same network
engine. The ZFR183x Series wireless system connects to the network engine through Ethernet using
BACnet/IP.
For more information about The WRG1830/ZFR183x Pro Series Wireless Field Bus System, refer to
WRG1830/ZFR183x Pro Series Wireless Field Bus System Technical Bulletin (LIT-12013553).
LCS85 compatibility
There are no known issues with the integration of the LCS85 to a Metasys Release 12.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 the
following figure, 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 8: 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: C•CURE-victor, Modbus, M-Bus, KNX, and OPC Unified
Architecture (UA).
The OAS provides the Site Management Portal (SMP) and Metasys User Interface (Metasys UI).
Note: SMP is only available once licensed.
Figure 9: 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. 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 10: Multiple network engines system configuration with Metasys Server Site Director
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 the
following figure for details.

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.

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. The following figure shows the
SNE1050 integrated into the Metasys network. Other BACnet/IP devices are integrated in the same
way.
Figure 14: BACnet/IP network integration system configuration
The NAE85 allows integration of larger BACnet integration projects.

Important: The following configuration is allowed with NAE85s at Release 11.0 or earlier only.
At Release 12.0, the NAE85 can act as a Site Director only. In the following example, you could
remove the ADS/ADX and use the NAE85 as Site Director to support Release 12.0.

Figure 15: NAE85 BACnet integration
BACnet/SC network system configuration

BACnet/SC uses a hub-and-spoke topology. The central Hub Function performs message
forwarding for all broadcast messages and for point-to-point messages for devices that do not
support more efficient direct connections. All Metasys devices support direct connections.
The following figure illustrates the normal scenario of the BACnet/SC network, where every node is
connected to the Primary Hub.

Figure 16: Normal BACnet/SC network scenario
The following figure illustrates the failover scenario of the BACnet/SC network, where the Primary
Hub is offline and nodes get re-routed to the Failover Hub.
Figure 17: Failover BACnet/SC network scenario
For more information about the BACnet/SC topology and BACnet/SC more generally, refer to
BACnet/SC Workflow Technical Bulletin (LIT-12013959).
Third-party network integration

The network engines offer seamless integration of Modbus, M-Bus, KNX, or other third-party
network to the Metasys system. The following figure shows the SNEs and SNC integrating third-
party devices. A KNX IP Gateway is also shown.

Figure 18: Third-party network integration
Wireless Metasys system configurations

The following figure shows the WRG1830/ZFR183x Pro Series wireless Metasys system offering, and
how it coexists within the Metasys system.

Figure 19: 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 20: 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 12.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 function with Release 12.0, but to ensure best
performance, upgrade engines to newer versions as soon as it is practical.

Table 22: Engine Site Director limitations and recommendations
Maximum allowed Type of Site Director
NAE35 NAE45 NAE55 NAE85 NCE25
SNE1050x SNE1100x SNE2200x SNC
replacements of
11
NCE25
Total engines 3 3 4 4 1
22
Simultaneous SMP users 2 2 4 10 2

Objects in device
33 2,500 2,500 5,000 25,000 2,500
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 SNC2515x-0xx, SNC2515x-04x, SNC1612x-0xx, and SNC1612x-04x.
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 23: Server Site Director limitations and recommendations
Maximum Type of Site Director
allowed ADS 11 22 ADX OAS
ADS-Lite-E ADS-Lite-A
Desktop
Total engines 14
33
5
44
4
55
1,000
66 OASMIN: 0
OASSTD: up to 2
Simultaneous 5 5 5 10/25/ 5
SMP users 50/100
77
Dynamic values 100

per graphics
Results 2,000
displayed in a
global search
Languages 18
Objects in 3 million/ 750k (for ADX Site Director Only)
entire system
Objects in Limited by SQL Server storage capacity
88
device
Objects within a 700
single folder
Characters in 400
the name of an
object
Characters in 64
the description
of an object
Nesting levels 7
for object
creation
Extensions per 10
object
Sets for third- 1,000
party BACnet
states text
Characters for 60
a third-party
BACnet states
text
Members for 500
a multi-value
third-party
BACnet states
text
Non- Limited only by memory capacity
Simultaneous
SMP users
SMP user views Limited only by memory capacity
Simultaneous 2 (Mix of online, SCT, and Simulation)
browsers per
client computer

Table 23: Server Site Director limitations and recommendations
Maximum Type of Site Director
allowed ADS 11 22 ADX OAS
ADS-Lite-E ADS-Lite-A
Desktop
DLLR load Limited only by memory capacity. If you plan to attach a large number of load extensions to a single DLLR
extension 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, SNC2515x-0xx, SNC2515x-04x, SNC1612x-0xx, SNC1612x-04x,
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. 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.
8 Includes all points, extensions, graphics (background image), trend study, and other objects, such as schedules and
interlocks.
Table 24: Maximum number of users supported on Metasys Server type Site Directors
Type of Metasys Computer supported platform Site Metasys UI Users
Server Desktop Server Management (up to)
Portal (SMP)
Users (up to)
ADS05U Yes - 5 5
OASSTD Yes
11
Yes
22 5 5
OASMIN Yes
1
Yes
2
5 5
ADX10U - Yes 10 25
ADX25U - Yes 25 25
ADX50U - Yes 50 50
ADX100U
33 - Yes 100 50
1 Virtual Machine or Turnkey only.
2 Virtual Machine only.
3 Metasys for Validated Environments does not support the 100 user ADX.

Table 25: 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/ Large/Extra Extra Large
ADX Large Large ADX ADX
ADX25U Small ADX Medium ADX
ADX
ADX50U Medium/
ADX100U Large
ADX
For ADS/ADX computer hardware requirements, refer to the Technical Specifications section of
this document:
• For Unified ADS refer to Application and Data Server (ADS) system requirements.
• For small and small to medium Unified ADX refer to Extended Application and Data Server
system requirements (Unified 10 or 25 User ADX).
• For medium to large Split ADX refer to Extended Application and Data Server system
requirements (Split 10 or 25 User ADX).
• For medium to large and large Unified ADX refer to Extended Application and Data Server
system requirements (Unified 50 or 100 User ADX).
• For large to extra large and extra large Split ADX refer to Extended Application and Data Server
system requirements (Split 50 or 100 User ADX).
Network OAS and engine hardware limitations

The following table describes limitations of the OAS and the Metasys system network engines.
Table 26: Network OAS and engine hardware limitations
Maximum allowed NCE25 NAE35 NAE45 NAE45-Lite NAE55 NAE85 OAS
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
11 Per trunk device limits if all devices are Metasys family devices, such as CGMs, CVMs, FACs,
FECs, VMAs, IOMs, and TEC3600s:
Note: N2 devices 32 50 100 100 100 N/A N/A
follow the same rules
Per trunk device limits if one device is a non-Metasys family device, such as a Facility Explorer
as MS/TP devices, but
performance varies device, TEC2000, or third-party device:
based on controller 32 50 64 64 64 N/A N/A
mix (N2Open/Sys91/
VMA).
Remote MS/TP devices on N/A 16 or 32 16 or 32 N/A 16 or 32 16 or 32 16 or 32
22
remote field bus
Mapped N2 points per trunk 2,500 2,500 2,500 N/A 2,500 N/A N/A
33

Table 26: Network OAS and engine hardware limitations
Maximum allowed NCE25 NAE35 NAE45 NAE45-Lite NAE55 NAE85 OAS
LonWorks devices
44 32 64 127 N/A 255 N/A N/A
Note: The LonWorks integration is only supported on NAE35s, NAE45s, and NCE25s
with the Metasys Release 9.0 software or earlier. Patch updates 9.0.7 and later 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, 11.0, and 12.0.
LonWorks network variables 1,500 1,500 1,500 N/A 2,000 N/A N/A
Johnson Controls BACnet/ 50
55,66,77
50
5,6,7
50
5,6,7
50
5,6,7
200
5,6
1,000 200
IP devices and third-party
Note:
BACnet/IP devices Before
11.0, the
NAE85
support
ed 200
devices.
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 27: Alarm and trending performance guidelines
Description SNE/ NCE25/ NAE55 NAE85 ADS ADX OAS Comments
SNC NAE35/
NAE45
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.

Table 27: Alarm and trending performance guidelines
Description SNE/ NCE25/ NAE55 NAE85 ADS ADX OAS Comments
SNC NAE35/
NAE45
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 28: MS/TP performance guidelines
Performance rating COV rate Token loop time
Low > 500 messages per minute > 3,000 ms
Medium Between 400 and 500 messages Between 2,000 and 3,000 ms
per minute
High < 400 messages per minute < 2,000 ms
SCT limitations
Table 29: SCT limitations
Description Supported Comments
Max. number of simultaneous 1
users
Max. number of concurrently 10
active archives
Max. size of an active 10 GB Using supported Microsoft
database or project in SCT SQL Server 2019 Express or
Microsoft SQL Server 2017
Express
No limit Using supported Microsoft SQL
Server Software

Equipment controller integration considerations
The CGM, CGE, CVM, CVE, 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, CGE, CVM, CVE, FAC, or VMA1930) with 6 alarms per hour plus 1
network engine with 30 alarms per hour (Table 30)
• 5 equipment controllers (CGM, CGE, CVM, CVE, FAC, or VMA1930) with 200 trend samples per
hour plus 1 network engine with 500 trend samples per hour (Table 31)
• 5 equipment controllers (CGM, CGE, CVM, CVE, FAC, or VMA1930) with 10 COVs per minute plus
35 FECs with 10 COVs per minute (Table 32)
Table 30: 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 31: 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 32: Example 3

Setup COVs per minute
5 CGMs, CGEs, CVMs, CVEs, FACs, or VMA1930s 50 COVs per minute
with 10 COVs/minute
35 FECs with 10 COVs/minute 350 COVs per minute
Total 400 COVs per minute

For trend creations in the CGM, CGE, CVM, CVE, 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.
Note: You can upgrade existing VMA1930 units in the field, but this model is discontinued from
manufacturing.
Transfer to device (download) limitations

Regarding transfer to device limitations, there is no difference between specific models
of equipment controllers (CGM, CGE, CVM, CVE, FAC, FEC, and VMA), but the firmware and
communication types (BACnet MS/TP, N2, BACnet/IP, and BACnet/SC) 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. CCT 14.0 and later 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 33: 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 and later.
Controller type
Supervisor Supervisor MAP 4.2+/ Bluetooth ZigBee Direct
Passthru - Passthru - BACnet Router (BTCVT) Ethernet
Engine at Engine at
8.1 or earlier 9.0 or later
BACnet/SC controllers X
using 10.0 firmware or
Note:
higher Engine
must X
be at
Release
12.0 or
later.
BACnet/IP controllers
using 7.0 firmware or X X X
higher
BACnet MS/TP controllers
X X X X X
using 6.2 firmware or lower

Table 33: 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 and later.
Controller type
Supervisor Supervisor MAP 4.2+/ Bluetooth ZigBee Direct
Passthru - Passthru - BACnet Router (BTCVT) Ethernet
Engine at Engine at
8.1 or earlier 9.0 or later
BACnet MS/TP controllers
using 7.0 firmware or X X
higher
N2 controllers using 6.2
11 X X
firmware or lower
N2 controllers using 8.0
X
firmware or higher
1
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 34: Client computer requirements for Site Management Portal UI, SCT, Metasys UI, and
JCT
Site Management Portal (SMP) UI Metasys UI
System Configuration Tool (SCT) JCT
Recommended processor
11 Intel® Core™ i5 Processor Intel® Core™ i5 Processor
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)
Supported operating SMP Metasys UI and JCT
systems Windows® 10 Pro and Windows 10 Enterprise Windows® 10 Pro and Windows 10 Enterprise
Editions versions 21H2, 22H2 (64-bit). For Editions versions 21H2, 22H2 (64-bit). For all
all future Windows 10 updates after version future Windows 10 updates after version 22H2,
22H2, Johnson Controls will evaluate and Johnson Controls will evaluate and certify that
certify that Metasys software can support Metasys software can support the updates
the updates before we provide guidance on before we provide guidance on support.
support. Windows® 10 Enterprise LTSC (1809, 21H2) (64-
Windows® 10 Enterprise LTSC (1809, 21H2) bit)
(64-bit) Apple® macOS® 11 Big Sur
Apple® macOS® 11 Big Sur Apple® macOS® 10.15 Catalina
Apple® macOS® 10.15 Catalina Apple® macOS® 10.14 Mojave
Apple® macOS® 10.14 Mojave
SCT and SCT Pro
Windows® 10 Pro and Windows 10 Enterprise
Editions versions 21H2, 22H2 (64-bit). For
all future Windows 10 updates after version
22H2, Johnson Controls will evaluate and
certify that Metasys software can support
the updates before we provide guidance on
support.
Windows® Server® 2019 (version 1809 or
later) (64-bit)
Windows® Server® 2016 (version 1607 or

later) (64-bit)
Supported web browsers Google® Chrome™ version 100 or later Microsoft® Edge® version 100 or later
Microsoft® Edge® version 100 or later Google® Chrome™ version 100 or later
33
22
Apple® Safari® 15 or later 44
Apple® Safari® 15 or later
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 9.0 or later
operating systems iPhone iOS 13.0 or later
Supported tablet operating N/A Android tablet 9.0 or later
systems iPad iOS 13.0 or later

Table 34: Client computer requirements for Site Management Portal UI, SCT, Metasys UI, and
JCT
Site Management Portal (SMP) UI Metasys UI
System Configuration Tool (SCT) JCT
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, use 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 SMP 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 SMP.
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 35: Application and Data Server (ADS) system requirements (5 Users)
Recommended Computer Platform
11 Intel Core i7-8700 Processor (Six Core, 3.20GHz)
22
2 x 500 GB 7200 rpm SATA 3.5 in. drive with 40 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.
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
33 16 GB RAM
The VM host must have at least 8 GB of allocated RAM at all times. When you
configure the VM, do not select the enable dynamic memory option.

Number of engines supported For information about the number of engines supported, refer to the table
labeled Maximum number of network engines supported based on Metasys Server
type and Server size in the Metasys System Configuration Guide (LIT-12011832).
Number of Site Management Portal users Up to five
supported
Number of Metasys UI users supported Up to five
44
Supported Operating Systems and Windows® 10 Pro and Windows 10 Enterprise Editions versions 21H2, 22H2
Database Software (64-bit). For all future Windows 10 updates after version 22H2, Johnson
Controls will evaluate and certify that Metasys software can support the
updates before we provide guidance on support.
Windows® 10 Enterprise LTSC (1809, 21H2) (64-bit)
Supports:
• SQL Server® 2019 Express with CU19 (64-bit)
Note: SQL Server 2019 may cause the configuration service cache
that builds stored procedures to time out. This causes the user's
login to Metasys UI to fail. To resolve this issue, set SQL Server
2019 databases to run in 2017 compatibility mode. For more
information, refer to docs.microsoft.com

• SQL Server® 2016 Express with SP3 GDR (64-bit)
Supported Operating Systems for Metasys Windows® 10 Pro and Windows 10 Enterprise Editions versions 21H2, 22H2
Site Management Portal Client Computer (64-bit). For all future Windows 10 updates after version 22H2, Johnson
Controls will evaluate and certify that Metasys software can support the
updates before we provide guidance on support.
Apple® macOS® 11 Big Sur

Apple® macOS® 10.15 Catalina
Supported Web Browser Software for Apple® Safari® 15 or later
Metasys Site Management Portal Client
Notes:
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.
Supported Web Browser Software for Microsoft® Edge® version 100 or later
Metasys UI Client Devices Google® Chrome™ version 100 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 Metasys UI
Site Management Portal (SMP)
Note: SMP requires a license at Release 12.0 and later. The license is
available only to existing Metasys customers.

Additional Software Included with the ADS Launcher software, Summary Definition Examples, Microsoft .NET Framework
Software Download (multiple versions), SQL Server Management Studio, Metasys Database
Manager, 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 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 36: Extended Application and Data Server system requirements (Unified ADX Systems,
10 or 25 Users)
Recommended Server Platform
11 Processor for small sites: Intel® Xeon® Gold 5222 3.8 GHz, 4 cores/8 threads, 10.4GT/
s, 16.5M Cache, Turbo, HT (105W) DDR4-2933 or 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
22
Hard drive: 2 x 960 GB SSD SATA Mix Use 6Gbps 512 2.5in Hot-plug Drive (RAID 1) with
40 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.
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.
33 32 GB RDIMM, 2933MT/s, Dual Rank
The VM host must have at least 8 GB of allocated RAM at all times. When you configure
the VM, do not select the enable dynamic memory option.
Number of engines supported For information about the number of engines supported, refer to the table labeled
Maximum number of network engines supported based on Metasys Server type and Server
size in the Metasys System Configuration Guide (LIT-12011832).
Number of Site Management For small sites: Up to 10
Portal users supported For small to medium sites: Up to 10
Number of Metasys UI users For small sites: Up to 15
supported For small to medium sites: Up to 25

10 or 25 Users)
Supported Operating Systems
44 Windows® Server® 2019 (version 1809 or later) (64-bit)
and Database Software Supports:
• SQL Server® 2019 with CU19 (64-bit)
Note: SQL Server 2019 may cause the configuration service cache that builds
stored procedures to time out. This causes the user's login to Metasys UI
to fail. To resolve this issue, set SQL Server 2019 databases to run in 2017
compatibility mode. For more information, refer to docs.microsoft.com
• Note: Metasys Advanced Reporting System does not support SQL Server
2019.

• SQL Server® 2016 with SP3 GDR (64-bit)
Windows® Server® 2016 (version 1607 or later) (64-bit)
Supports:
2019.

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

Apple® macOS® 12 Monterey
Apple® macOS® 13 Ventura
Supported Web Browser Apple® Safari® 15 or later
Software for Metasys Site
Notes:
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.
Supported Web Browser Microsoft® Edge® version 100 or later
Software for Metasys UI Client Google® Chrome™ version 100 or later
Devices
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.
VMware®

10 or 25 Users)
Supported User Interfaces Site Management Portal (SMP)
Note: For non-MVE sites at Release 12.0 or later, SMP requires a license. The
license is available only to existing Metasys customers. On MVE sites, SMP does
not require a license. The MVE license includes SMP UI access.
Metasys UI
Additional Software Included Microsoft .NET Framework 4.7.2
with the ADX Software Microsoft .NET 6.0.6
Download Launcher Software
Metasys Database Manager software
Metasys Advanced Reporting System software
RabbitMQ Server 3.11.7
Erlang OTP 25.2 (13.1.3)
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 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.
For SQL Server software, you must purchase SQL Server software licenses per the guidelines listed
here: SQL Server 2019, SQL Server 2017, and SQL Server 2016.

(Split 10 or 25 User ADX)
Use the following recommendations for medium to large sites.
Table 37: Extended Application and Data Server system requirements (Split ADX Systems, 10
or 25 Users)
11 Web/Application 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, 10.4GT/s, 16.5M Cache, Turbo, HT (105W) DDR4-2933
22
2 x 960GB SSD SATA Mix Use 6Gbps 512 2.5in Hot-plug Drive (RAID 1) with 50 GB free
33
space after installation of all prerequisite software and before installation of ADS
software. Configure RAID 1 (mirroring) with disk write-caching turned on
Notes:
• Metasys Advanced Reporting System 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, 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) with 50 GB
3
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.
44 64 GB RDIMM, 2933MT/s, Dual Rank (web/application server and database server for 10
or 25 user ADX)
Number of Site Management Up to 25
Portal users supported
Number of Metasys UI users Up to 25
supported

or 25 Users)
55,66 Windows® Server® 2019 (version 1809 or later) (64-bit)
with Supported Database Supports:
Software • SQL Server® 2019 with CU19 (64-bit)
2019.

Supports:
2019.

support.

Notes:
Management Portal Client • In OS X, you cannot view Graphics+ graphics in the Site Management Portal
Computers UI.
Devices
here.

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.
VMware®

or 25 Users)
Metasys UI
Erlang OTP 25.2 (13.1.3)
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)
11 Processor for medium to large sites: 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
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 6Gbps 512 2.5in
22
Hot-plug Drive (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
Hard drive for large sites: 2 x 960GB SSD SAS Mixed use 12Gbps 512e 2.5in Hot-Plug
2
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.
33 64 GB RDIMM, 2933MT/s, Dual Rank
Number of Site Management For medium to large sites: Up to 25
Portal users supported For large sites: Up to 100
Number of Metasys UI users For medium to large sites: Up to 50
supported For large sites: Up to 50
44 Windows® Server® 2019 (version 1809 or later) (64-bit)
and Database Software Supports:
2019.

Supports:
2019.


50 or 100 Users)
support.

Notes:
Management Portal Client • In OS X, you cannot view Graphics+ graphics in the Site Management Portal
Computers UI.
Devices
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.
VMware®
Metasys UI
Erlang OTP 25.2 (13.1.3)

50 or 100 Users)
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 39: Extended Application and Data Server system requirements (Split ADX System, 50 or
100 Users)
11 Web/Application Server
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
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
Hard drive for large to extra large sites: 960GB SSD SAS Mixed use 12Gbps
22
512e 2.5in Hot-Plug PM5-V Drive, 3 DWPD, 5256 TBW (RAID 5) with 50 GB free
33
software. 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 use 12Gbps 512e 2.5in
2
Hot-Plug PM5-V Drive, 3 DWPD, 5256 TBW (RAID 5) with 50 GB free space after
3
installation of all prerequisite software and before installation of ADS software.
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.
Notes:
• Metasys Advanced Reporting System must reside on the ADX web/
application server.
• Metasys UI must reside on the ADX web/application server.
Recommended Server Platform Database Server
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
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
Hard drive for large to extra large sites: 960GB SSD SAS Mixed use 12Gbps
2
512e 2.5in Hot-Plug PM5-V Drive, 3 DWPD, 5256 TBW (RAID 5) with 50 GB free
3
software. 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 use 12Gbps 512e 2.5in
2
Hot-Plug PM5-V Drive, 3 DWPD, 5256 TBW (RAID 5) with 50 GB free space after
3
installation of all prerequisite software and before installation of ADS software.
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.
Recommended Server Platform 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.
44 For large to extra large sites: 64 GB RDIMM, 2933MT/s, Dual Rank
For extra large sites: 64 to 128 GB RDIMM, 2933MT/s, Dual Rank
The VM host must have at least 8 GB of allocated RAM at all times. When you
configure the VM, do not select the enable dynamic memory option.

100 Users)
Maximum number of network engines supported based on Metasys Server type and
Server size in the Metasys System Configuration Guide (LIT-12011832).
Number of Site Management Portal For large to extra large sites: Up to 50
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 and Windows® Server® 2019 (version 1809 or later) (64-bit)
55,66 Supports:
Database Software
Note: SQL Server 2019 may cause the configuration service cache that
builds stored procedures to time out. This causes the user's login to
Metasys UI to fail. To resolve this issue, set SQL Server 2019 databases
to run in 2017 compatibility mode. For more information, refer to
docs.microsoft.com
• Note: Metasys Advanced Reporting System does not support SQL

Server 2019.
Supports:
Note: SQL Server 2019 may cause the configuration service cache that
builds stored procedures to time out. This causes the user's login to
Metasys UI to fail. To resolve this issue, set SQL Server 2019 databases
to run in 2017 compatibility mode. For more information, refer to
docs.microsoft.com
• Note: Metasys Advanced Reporting System does not support SQL

Server 2019.
Supported Operating Systems for Windows® 10 Pro and Windows 10 Enterprise Editions versions 21H2, 22H2 (64-
Metasys Site Management Portal bit). For all future Windows 10 updates after version 22H2, Johnson Controls will
Client Computer evaluate and certify that Metasys software can support the updates before we
provide guidance on support.

Supported Web Browser Software Apple® Safari® 15 or later

for Metasys Site Management Portal
Notes:
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.

100 Users)
Supported Web Browser Software for Microsoft® Edge® version 100 or later
Metasys UI Client Devices Google® Chrome™ version 100 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.
VMware®
license is available only to existing Metasys customers. On MVE sites, SMP
does not require a license. The MVE license includes SMP UI access.
Metasys UI
Additional Software Included with the Microsoft .NET Framework 4.7.2
ADX Software Download Microsoft .NET 6.0.6
Launcher Software
Erlang OTP 25.2 (13.1.3)
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 40: OAS Turnkey hardware and software specifications
Processor Intel® Atom® E3900
Operating system Windows 10 Enterprise LTSB version 1607
Database software SQL Server 2017 Express with CU17 (64-bit)
Memory 8 GB
Power input 12 VDC to 24 VDC input
RS-232-C serial ports 1
USB serial ports

11 Four USB 3.0 ports
Ethernet ports
22 2
Wireless card
33 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. Use a remote field bus
or BACnet/IP field devices.
2 Use only one Ethernet port for network connectivity.
3 The wireless card is not supported for use with Metasys.
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 41: OAS application hardware and software requirements
Recommended computer platform Intel Core i7-8700 Processor, Six Cores, 3.20 GHz
or better
Note: Match the specs of the ADS/ADX rec-
ommendations 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 vir-
tual machine, match the recommendations
listed in the Network and IT Guidance Technical
Bulletin (LIT-12011279).
Two 500 GB hard disk with 40 GB free space
after you install all prerequisite software and
before you install OAS software. Configure RAID 1
(mirroring) with disk write caching enabled
Note: Prerequisite software includes the sup-
ported operating system, database software,
and .NET Framework.
Memory Minimum: 8 GB
Note: The VM host must have at least 8 GB of
allocated RAM at all times. When you config-
ure the VM, do not select the enable dynamic
memory option.

Table 41: OAS application hardware and software requirements
Supported desktop operating systems and Windows® 10 Pro and Windows 10 Enterprise
database software Editions versions 2004, 21H1, and 21H2 (64-bit).
For all future Windows 10 updates after version
21H2, we will evaluate and certify that Metasys
software can support the updates before we
provide guidance on support
Windows® 10 Enterprise LTSC (1809, 21H2) (64-
bit)
Supports:
Supported server operating systems and Windows® Server® 2019 (version 1809 or later)
database software (64-bit)
Windows® Server® 2016 (version 1607 or later)
(64-bit)
Supports:
Supported user interfaces Metasys User Interface
Note: SMP requires a license at Release
12.0.50. The license is available only to exist-
ing Metasys customers.
Supported virtual environments Microsoft Hyper-V™
VMware®
Additional software included with the OAS Microsoft .NET Framework Version 4.7.2
software download Microsoft .NET Core 3.1.21
Launcher Software
Erlang OTP 23.2 (11.1.4)
Optional software Metasys Database Manager
Language Installation Program
Application and Data Server Lite system requirements

Table 42: Application and Data Server Lite system requirements
Recommended computer Intel i7 processor latest version with at least 6 cores or better
11
platform 22
2 x 500 GB hard disk (RAID 1) with 40 GB free space after installation of all prerequisite
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)
Required minimum memory
33 8 GB minimum, 16 GB recommended

Supported operating systems Windows® 10 Pro and Windows 10 Enterprise Editions versions 21H2, 22H2 (64-bit). For
and database software
44 all future Windows 10 updates after version 22H2, Johnson Controls will evaluate and
certify that Metasys software can support the updates before we provide guidance on
support.
Windows® 10 Enterprise LTSC (1809, 21H2) (64-bit)
Database software:
• SQL Server® 2016 Express with SP3 GDR (64-bit)
Supported operating systems for Windows® 10 Pro and Windows 10 Enterprise Editions versions 21H2, 22H2 (64-bit). For
Metasys client devices all future Windows 10 updates after version 22H2, Johnson Controls will evaluate and
certify that Metasys software can support the updates before we provide guidance on
support.
Apple® macOS® 10.15 Catalina
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.
Supported web browser Windows® Internet Explorer® 11.0.9600.18816 Update version 11.0.47 or later
software for Metasys Site
Note: To ensure that websites appear and function correctly, select the Use
Management Portal client Microsoft compatibility lists option, found under Tools > Compatibility View
Settings.

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.
• To ensure that websites appear and function correctly, select the Use
Microsoft compatibility lists option, found under Tools > Compatibility
View Settings.
• Metasys UI does not support InPrivate Browsing. To exit InPrivate Browsing,
close the browser window and open a new browser window.
Microsoft® Edge® version 100 or later

Google® Chrome™ version 100 or later
here.

click or tap Private in the browser window.
Supported virtual environments Microsoft Hyper-V™
VMware®

Supported user interfaces Metasys UI
Note: SMP requires a license at Release 12.0.50 The license is available only to
existing Metasys customers.
Additional software included Microsoft .NET Framework 4.7.2
with the ADS Lite software Microsoft .NET 6.0.6
download Launcher Software
Erlang OTP 25.2 (13.1.3)
Optional hardware Any network or local printer supported by the qualified Windows operating system
Optional software Graphic Generation Tool
CCT Software
SCT Software
Metasys Database 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

Depending on your operating system, refer to the following documents for further information:
Table 43: SCT Integrations
Operating system Integrations
Metasys For instances where you install SCT on the same computer as the ADS/
ADX software, refer to the specifications in the Application and Data
Server (ADS) and Extended Application and Data Server (ADX) Product Bulletin
(LIT-1201525).
Facility Explorer For further details, refer to the F4-SNC Commissioning Guide (LIT-12013549)
Notes:
• Refer to the Network and IT Guidance Technical Bulletin (LIT-12011279) for specific Microsoft
Windows OS setting requirements for your Metasys system configuration.
• For information on licensing Microsoft SQL Server, refer to the Microsoft SQL Server Licensing
Guide for your edition of Microsoft SQL Server.
Table 44: SCT System Requirements
Specification Description
Product code TL-SCT-0
TL-SCT-P
Full server platform Intel® Core™ i7-8700 processor, Six Core, 3.20GHz.
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.
8GB to 16GB 2666MT/s, Dual Rank DDR UDIMM

Desktop computer Intel® Core™ i7-8700 processor, Six Core, 3.20GHz.
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)
Supported full server Windows® Server® 2019 (version 1809 or later) (64-bit)
platform operating Supports Microsoft SQL Server® 2019 Express with CU19 (64-bit), SQL
systems and database Server® 2017 Express with CU31 (64-bit), or SQL Server® 2016 Express
software with SP3 GDR (64-bit).
Note: If you install Windows® Server® 2016 (version 1607 or later) (64-bit)
SCT on a standalone Supports Microsoft SQL Server® 2019 Express with CU19 (64-bit), SQL
server and not on Server® 2017 Express with CU31 (64-bit), or SQL Server® 2016 Express
a Metasys or Facil-
with SP3 GDR (64-bit).
ity Explorer server,
you can also use the
Express versions of
Microsoft SQL Server
when you install SQL
Express manually
before you install
SCT.
Supported desktop Windows® 10 Pro and Windows 10 Enterprise Editions versions 21H2,
computer platform 22H2 (64-bit). For all future Windows 10 updates after version 22H2,
operating systems and Johnson Controls will evaluate and certify that Metasys software can
database software support the updates before we provide guidance on support.
Supports Microsoft SQL Server® 2019 Express with CU19 (64-bit), SQL
Server® 2017 Express with CU31 (64-bit), or SQL Server® 2016 Express
with SP3 GDR (64-bit).
Note: Any Windows 10 computer that runs either Metasys 11.0
software, including the ADS, ADX, or Facility Explorer software
requires the Windows 10 version 1903 update. Verify this update
before you install either Metasys 11.0 or Facility Explorer software.
Note: [Metasys specific] If you upgrade 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.
Supported web browser Microsoft® Edge® version 100 or later, Apple® Safari® 15 or later, and
software for JCI client Google® Chrome™ version 100 or later.
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 applica-
tion. After you install the Launcher application, you can use the
Launcher to log in to the SCT UI.
Note: [Metasys specific] You can also use the web browsers to
access the Site Management Portal (SMP) UI, Metasys UI, Johnson
Controls System Configuration Tool (JCT) , and SCT Pro sites. You
can also add a bookmark to the Metasys UI, JCT, and SCT Pro sites.

Network Ethernet network interface card 10/100/1000 Mbps (100 Mbps network
communication for SCT or better)
client computers
Optional software Note: Metasys Server software does not include a license for SCT
packaging 14.1 or later. Obtain a license for each installation of SCT, device
packages, and the Generic SA Bus package, as well as a license
for field controller packages to upload and download .caf files.
The Generic SA Bus package is licensed with CCT, but the device
packages and field controller packages are licensed individually
through the License Portal.
CCT technical specifications

Table 45: 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 21H2, 22H2 (64-bit). For all future Windows 10 updates after
software version 22H2, Johnson Controls will evaluate and certify that
Metasys software can support the updates before we provide
guidance on support.
Supports Microsoft SQL Server® 2019 Express with CU19 (64-bit),
SQL Server® 2017 Express with CU31 (64-bit), or SQL Server® 2016
Express with SP3 GDR (64-bit).
Note: The OS and software must both be 64-bit.
Supported full server Windows® Server® 2019 (version 1809 or later) (64-bit)
platform operating Supports Microsoft SQL Server® 2019 with CU19 (64-bit), SQL
systems and database Server® 2017 with CU31 (64-bit), or SQL Server® 2016 with SP3 GDR
software (64-bit)
Supports Microsoft SQL Server® 2019 with CU19 (64-bit), SQL
Server® 2017 with CU31 (64-bit), or SQL Server® 2016 with SP3 GDR
(64-bit).
Required web browser Microsoft® Edge® version 100 or later, Apple® Safari® 15 or later,
software for Metasys client and Google® Chrome™ version 100 or later. Other browsers, such
computers as 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 45: CCT system requirements
Software optionally Microsoft .NET Framework version 4.7.2
installed during CCT Microsoft SQL Server 2017 Express software with SP2
installation
Optional connection Bluetooth Commissioning Converter (MS-BTCVT-1)
devices (order separately) Important: The BTCVT Bluetooth Commissioning Converter
is no longer a supported connection method from Metasys
Release 11.0 and later.
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 CCT for wireless commissioning of the
wireless enabled equipment 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
Optional software The Johnson Controls SA Bus Device Packages is licensed with
packages CCT and is a licensable feature of CCT. Device Packages are sold
separately.
SNC technical specifications

Table 46: SNC2515x-0xx and SNC1612x-0xx
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)
Power 33 VA maximum from main power supply
consumption Note: The VA rating does not include any power supplied to the periph-
eral 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).
Power source +15 VDC power source terminals provide 100 mA total current; quantity of
inputs: five, located in Universal Input terminals; for active (3-wire) input
devices
Display Screen 2.4 in (61 mm), 320 x 240 resolution display (-0H and -04H models only)
SA Bus power 15 V at 240 mA maximum

Processor NXP i.MX6DualLite Processor, 1GHz 32-bit dual core Cortex A9 processor
Memory 16 GB flash nonvolatile memory for operating system, configuration data, and
operations data storage and backup
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
Supported BACnet/IP, BACnet/SC, BACnet MS/TP , MQ Telemetry Transport (MQTT), N2
integrations Bus, LonWorks, Modbus, KNX, M-Bus, Zettler Fire, OPC UA
Tyco C•CURE 9000-victor video management, Simplex FACU, Molex Lighting
Control, Cree SmartCast Lighting Control
Network and 1 Ethernet port: SNC25150-0, SNC25150-04, SNC16120-0, SNC16120-04,
serial interfaces SNC25152-0, SNC25152-0H, SNC25152-04, SNC25152-04H, SNC16122-0,
SNC16122-0H, SNC16122-04, and SNC16122-04H
2 Ethernet ports: SNC25151-0, SNC25151-0H, SNC25151-04, SNC25151-04H,
SNC16121-0, SNC16121-0H, SNC16121-04, and SNC16121-04H
Ethernet port(s): 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)
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.
Transmission Ethernet communication: 100 or 10 Mbps
speeds The network engine can reside and interoperate on a 1 Gbps network, but
does not itself transmit at 1 Gbps.
Optically isolated, serial communication (FC Bus): 76,800, 38,400, 19,200, 9600,
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 Non-operating: -40°C to 70°C (-40°F to 158°F)
conditions
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
IP protection class: IP20
UL flammability rating: UL94-5VB
Mounting On flat surface with screws on three mounting clips or a single 35 mm DIN rail
Dimensions 250 mm x 145 mm x 45.5 mm (9.84 in. x 5.71 in. x 1.79 in.)
(width x height x
depth)
Weight 0.65 kg (1.433 lbs)

Compliance United States: UL Listed, File E107041, CCN PAZX, UL 916, Energy
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-2020 Listed B-BC/B-RTR/B-BBMD, Protocol

Revision 18
United Kingdom: Johnson Controls declares that this product is in compliance
with Electromagnetic Compatibility Regulations, The Electrical Equipment
(Safety) Regulations, and Restriction of the Use of Certain Hazardous
Substances in Electrical and Electronic Equipment Regulations.
Table 47: SNC25150 and SNC16120

Power 32 VA maximum from main power supply
consumption Note: The VA rating does not include any power supplied to the periph-
eral 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).
Power source +15 VDC power source terminals provide 100 mA total current; quantity of
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
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 BACnet/IP, BACnet/SC, BACnet MS/TP, MQ Telemetry Transport (MQTT), N2
integrations Bus, LonWorks, Modbus, KNX, M-Bus, Zettler Fire Tyco C•CURE 9000-victor
video management, Simplex FACU, Molex Lighting Control, OPC UA, Cree
SmartCast Lighting Control

Network and One supported Ethernet port (top); 1000/100/10 Mbps; 8-pin RJ45 connector
serial interfaces 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)
One optically 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.
speeds The network engine resides and interoperates on a 1 Gbps network, but does
not itself transmit at 1 Gbps.
Sensor/actuator communication (SA Bus): 38,400 bps
temperature Non-operating: -40°C to 70°C (-40°F to 158°F)
conditions
(width x height x
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 shall not be liable for damages resulting from misapplication or misuse of its products.
SNE technical specifications

Table 48: SNE2200x network engine
Alternate: Dedicated nominal 24 VDC, Class II power supply input; North
America: ACC-PWRKIT-1A24; Europe: ACC-PWRKIT-1E24
Power 38 VA maximum
consumption
Processor NXP i.MX6 DualLite processor, dual core Cortex-A9 processor at 1.0 GHz with
512 KB of L2 cache
Supported BACnet/IP, BACnet/SC, BACnet MS/TP, N2 Bus, LonWorks, Modbus, KNX, M-
integrations Bus, Zettler Fire, MQ Telemetry Transport (MQTT),OPC UA
Network and One Ethernet port; 1000/100/10 Mbps; 8-pin RJ45 connector
Serial interfaces Two FC ports (RJ12 6-pin port; connects with 1.5 m [4.9 ft] RJ12 field bus cable)
Two optically isolated RS-485 ports; with a removable 4-pin terminal block
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
speeds The network engine can reside and interoperate on a 1 Gbps network, but
does not itself transmit at 1 Gbps.
temperature Non-Operating: -40°C to 70°C (-40°F to 158°F)
conditions

Table 48: SNE2200x network engine
(Height x Width x
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 49: SNE1100x, SNE1050x, and SNE110Lx network engines

Alternate: Dedicated nominal 24 VDC, Class II power supply input; North
America: ACC-PWRKIT-1A24; Europe: ACC-PWRKIT-1E24
Power 38 VA maximum
consumption
Processor NXP i.MX6 DualLite processor, dual core Cortex-A9 processor at 1.0 GHz with
512 KB of L2 cache

Supported BACnet/IP, BACnet/SC, BACnet MS/TP, N2 Bus, LonWorks, Modbus, KNX, M-
integrations Bus, Zettler Fire, MQ Telemetry Transport (MQTT), OPC UA
Note: The SNE110Lx model supports one IP device integration, but does
not support the N2 Bus or LonWorks network interface.
Network and One Ethernet port; 1000/100/10 Mbps; 8-pin RJ45 connector
Serial interfaces One FC port (RJ12 6-pin port; connects with 1.5 m [4.9 ft] RJ-12 field bus cable)
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
speeds The network engine resides and interoperates on a 1 Gbps network, but does
not itself transmit at 1 Gbps.
temperature Non-Operating: -40°C to 70°C (-40°F to 158°F)
conditions
(Height x Width x
Depth)
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 50: LCS85 software system recommendations for installation or upgrade
Recommended computer Intel Xeon E5506, 2.13 GHz, 4 MB Cache
platform 2 x 160 GB 7.2K SATA, 8.9 cm (3.5 in.) Cabled
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
Supported operating systems • Windows® Server® 2019 (version 1809 or later) (64-bit)
and software • Windows® Server® 2016 (version 1607 or later) (64-bit)
• Windows® 10 Pro and Windows 10 Enterprise Editions
versions 21H2, 22H2 (64-bit). For all future Windows 10
updates after version 22H2, Johnson Controls will evaluate
and certify that Metasys software can support the updates
before we provide guidance on support.
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
Supported web browser Windows® Internet Explorer® 11.0.9600.18816 Update version
Software for Metasys Site 11.0.47 or later
Management Portal client Note: In Internet Explorer 11, select the Use
computers Microsoft compatibility lists option, found under
Tools > Compatibility View Settings, to ensure that web-
sites appear and function correctly.
Google® Chrome™ version 100 or later
Other browsers, such as Mozilla® Firefox®, may also be used
but are not fully supported.
Supported virtual environments Microsoft Hyper-V™, VMWare®

Table 50: LCS85 software system recommendations for installation or upgrade
Network communication 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)
Ethernet network interface card 10/100/1000 Mbps (100 Mbps
or better recommended)
Recommended data protection Uninterruptible power supply (UPS)
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 51: NCE25 technical specifications
Power Requirement 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 Consumption 25 VA maximum for NCE25 only
Note: The 25 VA rating does not include any power supplied by
the NCE to devices connected at the NCE BOs. BO devices con-
nected to and powered by an NCE can require an additional 125 VA
(maximum).
Power Source +15 VDC power source terminals provide 100 mA total current; quantity
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
Data Protection Battery Supports data protection on power failure. Rechargeable NiMH 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
Processors Supervisory Controller: 192 MHz Renesas SH4 7760 RISC processor
Field Controller: 20 MHz Renesas H8S2398 processor
Memory Supervisory Controller: 128 MB flash nonvolatile memory for
operating system, configuration data, and operations data storage and
backup and 128 MB SDRAM for operations data dynamic memory
Field Controller: 1 MB flash memory and 1 MB RAM
Operating System Microsoft Windows Embedded CE 6.0 (Release 9.0.6)
Buildroot 2017.08.2 with Linux kernel 14.4 (Release 9.0.7 patch or later)

Network and Serial • One Ethernet port; 10/100 Mbps; 8-pin RJ-45 connector
Interfaces • One optically isolated RS-485 SA Bus port; with a pluggable and
(Depending on NCE keyed 4-position terminal block (on all NCE25 models)
model) • 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)
• One LonWorks port; FTT10 78 Kbps; pluggable, keyed 3-position
terminal block (only on NCE25 models that support a LonWorks
Network trunk). The LonWorks models are supported to run the
Metasys Release 9.0.6 software, but not the Release 9.0.7 patch or
later.
• 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 later.
Analog Input/Analog • Analog Input Points: 16-bit resolution
Output Point Resolution • Analog Output Points: 16-bit resolution and ±200 mV accuracy on
0-10 VDC applications
Input/Output • 10-Universal Inputs: Defined as 0–10 VDC, 4–20 mA, 0–600k ohm, or
Capabilities Binary Dry Contact
• 8-Binary Inputs: Defined as Dry Contact Maintained or Pulse/
Accumulator Mode
• 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
Dimensions 155 mm x 270 mm x 64 mm (6.1 in. x 10.6 in. x 2.5 in.),
(Height x Width x Depth) Minimum mounting space required: 250 mm x 370 mm x 110 mm (9.8
in. x 14.6 in. x 4.3 in.)
Housing Plastic housing
Plastic material: ABS and polycarbonate
Protection: IP20 (IEC60529)
Mounting On a flat surface with screws, on three mounting clips, or a single 35
mm DIN rail
Shipping Weight 1.2 kg (2.7 lb)
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
Power Requirement Dedicated nominal 24 VAC, Class 2 power supply (North America),
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
Data Protection Battery Supports data protection on power failure. Rechargeable NiMH 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
Memory 128 MB flash nonvolatile memory for operating system, configuration
data, and operations data storage and backup
128 MB SDRAM for operations data dynamic memory
Operating System Microsoft Windows Embedded CE 6.0 (Release 9.0.6)
Buildroot 2017.8.2 with Linux kernel 14.4 (Release 9.0.7 patch or later)
Network and Serial • One Ethernet port; connects at 10 or 100 Mbps; 8-pin RJ-45
Interfaces 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)
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 patch or
later.
• 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 patch or later.
• 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 later.
Housing Plastic housing material: ABS polycarbonate
UL94-5VB Protection: IP20 (IEC 60529)
Mounting On a flat surface with screws on three mounting clips or a single 35 mm
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.)
(Height x Width x Depth) Minimum space for mounting NAE35 and NAE45: 210 mm x 350 mm x
110 mm (8-3/16 in. x 13-13/16 in. x 4.-5/16 in.)
Shipping Weight 1.2 kg (2.7 lb)
Class A
Signal Equipment; Industry Canada Compliant, ICES-003
Compliant
Europe: CE Mark – Johnson Controls declares that this product is
BACnet International: BTL 135-2020 Listed B-BC, Protocol Revision 12
Technical specifications
Table 52: NAE5510-2U (UL 864, Smoke Control) technical specifications
Power requirement Dedicated nominal 24 VAC, Class 2 power supply for North America at
50/60 Hz, 20 VAC minimum to 30 VAC maximum
Power consumption 50 VA maximum
Ambient operating 0°C or 32°F to 50°C or 122°F; 10% to 90% RH, 30°C or 86°F maximum
conditions dew point
Ambient storage -40°C or 104°F to 70°C or 158°F; 5% to 95% RH, 30°C or 86°F maximum
Data protection battery Supports data protection on power failure. Rechargeable gel cell
battery: 12 V, 1.2 Ah, with a typical life of 3 to 5 years at 21°C or 70°F;
Clock battery Maintains real-time clock through a power failure. Onboard cell; typical
life 10 years at 21°C or 70°F
Processor 1.6 GHz Intel Atom® processor
Memory 4 GB flash nonvolatile memory for operating system, configuration
data, and operations data storage and backup.
1 GB SDRAM for operations data dynamic memory for all models
Operating system Metasys system Release 8.1 uses Microsoft Windows Standard 2009
Network and serial • One Ethernet port; 10/100/1000 Mbps; 8-pin RJ-45 connector
interfaces • Two optically isolated RS-485 ports; 9.6k, 19.2k, 38.4k, or 76.8k baud;
pluggable and keyed 4-position terminal blocks
• Two RS-232-C serial ports, with standard 9-pin sub-D connectors,
that support all standard baud rates
• Two USB serial ports; standard USB connectors. However, these
ports are not supported on Smoke Control NAEs
Housing Plastic housing with internal metal shield
Plastic material: ABS + polycarbonate

Table 52: NAE5510-2U (UL 864, Smoke Control) technical specifications
Mounting On a flat surface with screws on four mounting feet or on a dual 35 mm
DIN rail
Dimensions 226 mm x 332 mm x 96.5 mm or 8.9 in. x 13.1 in. x 3.8 in. including
(Height x Width x Depth) mounting feet
Minimum space for mounting: 303 mm x 408 mm x 148 mm or 12.0 in. x
16.1 in. x 5.8 in.
Shipping weight 2.9 kg or 6.4 lb
Class A
UL Listed, File S4977, UL 864 UUKL/UUKLC 10th Edition Listed, Smoke
Control Units and Accessories for Fire Alarm Systems Equipment
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
United Kingdom: Johnson Controls declares that this product is in
compliance with Electromagnetic Compatibility Regulations, The
Electrical Equipment (Safety) Regulations, and Restriction of the Use of
Certain Hazardous Substances in Electrical and Electronic Equipment
Regulations.
BACnet International: BTL 135-2020 Listed B-BC/B-BBMD, Protocol
Revision 15
Table 53: NAE55xx-3 (UL 916, Energy Management) and NAE5510-3U (UL 864, Smoke Control)
technical specifications
Power requirement Dedicated nominal 24 VAC, Class 2 power supply (North America),
maximum)
Power consumption 50 VA maximum
Ambient operating 0°C or 32°F to 50°C or 122°F; 10% to 90% RH, 30°C or 86°F maximum
Ambient storage -40°C or -104°F to 70°C or 158°F; 5% to 95% RH, 30°C or 86°F maximum
Data protection battery Supports data protection on power failure. Rechargeable gel cell
battery: 12 V, 1.2 Ah, with a typical life of 3 to 5 years at 21°C (70°F);
Clock battery Maintains real-time clock through a power failure. Onboard cell; typical
life 10 years at 21°C or 70°F

Processor 1.46 GHz Intel® Atom® Bay Trail E3815 processor for MS-NAE55xx-3
models
Memory 16 GB flash nonvolatile memory for operating system, configuration
data, and operations data storage and backup for MS-NAE55xx-3
models.
2 GB DDR3 SDRAM for operations data dynamic memory for all models
Operating system NAE5510-3U (UL 864 UUKL 10th ed /S527 UUKL7 4th ed): OEM Version
of Microsoft® Windows® Embedded Standard 7 with SP1 (WES7)
NAE55xx-3: (UL 916): Wind River® Linux LTS 17 (LTS=long-term
support)
Network and serial • One Ethernet port; 10/100/1000 Mbps; 8-pin RJ-45 connector
interfaces • 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,
that support all standard baud rates
• 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
terminal block. LonWorks port available on NAE552x-x models only
Housing Plastic housing with internal metal shield
Plastic material: ABS + polycarbonate; Protection: IP20 (IEC 60529)
Mounting On a flat surface with screws on four mounting feet or on a dual 35 mm
DIN rail
Dimensions 226 mm x 332 mm x 96.5 mm or 8.9 in. x 13.1 in. x 3.8 in. including
(Height x Width x Depth) mounting feet
Minimum space for mounting: 303 mm x 408 mm x 148 mm or 12.0 in. x
16.1 in. x 5.8 in.
Shipping weight 2.9 kg or 6.4 lb
Management Equipment, FCC Compliant to CFR47, Part 15, Subpart B,
Class A
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
United Kingdom: Johnson Controls declares that this product is in
compliance with Electromagnetic Compatibility Regulations, The
Electrical Equipment (Safety) Regulations, and Restriction of the Use of
Certain Hazardous Substances in Electrical and Electronic Equipment
Regulations.
BACnet International: BTL 135-2020 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 54 contain information related to the features, installation, operation,
configuration, and troubleshooting of the Metasys system.
Table 54: Related documentation
For information about Refer to
Newly introduced features at Metasys Release What's New at Metasys Release 12.0.50 (LIT-TBC)
12.0.50
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-12012258)
How to install and upgrade SQL Server software SQL Server Software Installation and Upgrade
Guide (LIT-12012240)
How to install and upgrade the OAS Open Application Server (OAS) Installation and
Upgrade Guide (LIT-12013222)
How to install and upgrade the SCT, SCT Pro and SCT Installation and Upgrade Instructions
JCT 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, Open Application Server (OAS) Commissioning
use Server repositories, synchronize time, use a Guide (LIT-12013243)
network printer, accept dial-up connections, and
more
Features, benefits, and specifications of the Metasys UI Help (LIT-12011953)
Metasys UI

MVE for Metasys UI Metasys UI Technical Bulletin (LIT-12012115)
Features, benefits, and specifications of the JCT Johnson Controls System Configuration Tool (JCT)
software Help (LIT-12012116)
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 Application Note (LIT-12013148)
Network Engine commissioning for M-Bus Network Engine Commissioning for M-Bus Vendor
vendor integration Integration Application Note (LIT-12013149)
Network Engine commissioning for Modbus Network Engine Commissioning for Modbus
vendor integration Vendor Integration Application Note
(LIT-12013150)
Network Engine commissioning for C·CURE 9000 Network Engine Commissioning for C•CURE/victor
Access Control and victor Video Management Integration Application Note (LIT-12013151)
Integration
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
System integration Fire System Integration Application Note
(LIT-12013060)
Network Engine commissioning for Zettler fire Network Engine Commissioning for Zettler MX
panels Speak 6.0 Vendor 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 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 software, including setting SCT: System Configuration Tool Help
up archive databases offline and basic N2 online (LIT-12011964)
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)
BACnet/SC workflow BACnet/SC Workflow Technical Bulletin
(LIT-12013959)
How to set up an NAE as a BACnet/IP, BACnet/ BACnet Controller Integration Technical Bulletin
SC, or BACnet MS/TP system integrator in a (LIT-1201531)
Metasys network
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)

WRG1830/ZFR183x Pro Series Wireless Field Bus WRG1830/ZFR183x Pro Series Wireless Field Bus
System System Technical Bulletin (LIT-12013553)
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-7860 One-to-One Wireless Room WRZ Series One-to-One Wireless Room Sensing
Temperature Sensing System System Technical Bulletin (LIT-12011641)
How to commission the MQTT client External MQTT Client External Data Connector Network
Data Connector in an SNE or an SNC network Engine Commissioning Guide (LIT-12013976)
engine
Using the Mass Changes Tool (MCT) to get Mass Changes Tool (MCT) Help (LIT-12013963)
configuration data into a format that you can
download into a network engine as resource
file.
MVE on SMP UI Metasys for Validated Environments Technical
Bulletin (LIT-12011327)
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 Johnson Controls representative: www.johnsoncontrols.com/locations
Contact Johnson Controls: www.johnsoncontrols.com/contact-us

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

12011832-System Configuration Guide

Uploaded by

Document Information

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

12011832-System Configuration Guide

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

Metasys System Configuration Guide 7

8 Metasys System Configuration Guide

Metasys System Configuration Guide 9

Figure 3: Remote mountable display

Table 2: Remote mountable display

10 Metasys System Configuration Guide

Figure 4: Expansion I/O modules

Table 3: Expansion I/O modules

Advanced Application Field Equipment Controller (FAC)

Metasys System Configuration Guide 11

Field Equipment Controllers (FEC)

FEC Field Equipment Controller family comparison

12 Metasys System Configuration Guide

VMA VAV Modular Assembly Series

Metasys System Configuration Guide 13

Expansion input and output (I/O) modules

14 Metasys System Configuration Guide

Controller Configuration Tool (CCT)

Metasys System Configuration Guide 15

TEC3x00 Series Networked Thermostat Controllers

16 Metasys System Configuration Guide

Metasys System Configuration Guide 17

SNE Series Network Engines

Figure 5: SNE series network engines

The following table outlines the SNE models in more detail.

Succeeds NAE55 Series NAE45 Series NAE35 Series NAE45-Lite

18 Metasys System Configuration Guide

Maximum allowed 600 150 60 110

Metasys System Configuration Guide 19

Mapped N2 devices 100 100 50 N/A

20 Metasys System Configuration Guide

SNC Series Network Control Engines

Metasys System Configuration Guide 21

Figure 6: SNC series network control engines

The following table outlines the SNC models in more detail.

22 Metasys System Configuration Guide

Metasys System Configuration Guide 23

NAE Series Network Automation Engine

24 Metasys System Configuration Guide

NCE Series Network Control Engine

Network Engine comparison

Metasys System Configuration Guide 25

Table 8: Network Engine integrations available by Metasys Release

Modbus RTU and TCP X X X X X X

Vendor integrations on engines

26 Metasys System Configuration Guide

Metasys System Configuration Guide 27

Virtual server platform (VM):

28 Metasys System Configuration Guide

Extended Application and Data Server (ADX)

Metasys System Configuration Guide 29

ADS/ADX concurrent users

30 Metasys System Configuration Guide

Metasys System Configuration Guide 31

Figure 7: OAS system diagram

32 Metasys System Configuration Guide

Metasys System Configuration Guide 33

System Configuration Tool (SCT)