Metasysystem Configuide PDF

Metasys System Configuration Guide
Building Technologies & Solutions LIT-12011832

www.johnsoncontrols.com
2018-12-17 Release 10.0
Contents
Metasys System Configuration Guide Introduction......................................................................7
Contents
Summary of Changes............................................................................................................................7
Metasys System................................................................................................................................. 7
Equipment Controllers..........................................................................................................................8
General Purpose Application Controllers (CGMs) and VAV Box Equipment

Controllers (CVMs)...................................................................................................................... 8
Advanced Application Field Equipment Controller (FAC)..................................................... 12
Field Equipment Controllers (FEC).......................................................................................... 12
FEC Field Equipment Controller Family Comparison............................................................13
VMA VAV Modular Assembly Series........................................................................................ 13
Input/Output Module (IOM).................................................................................................... 14
Wireless Solutions.....................................................................................................................14
Controller Configuration Tool (CCT).................................................................................................. 15
TEC3x00 Series Networked Thermostat Controllers.......................................................................16
Network Engines................................................................................................................................. 16
NAE............................................................................................................................................. 17
NCE............................................................................................................................................. 18
NIE55/NIE85.............................................................................................................................. 18
NIEx9.......................................................................................................................................... 18
Network Engine Comparison.................................................................................................. 19
Servers.................................................................................................................................................. 19
ADS and ADS-Lite...................................................................................................................... 19
Server Comparison................................................................................................................... 20
ADX............................................................................................................................................. 21
ODS............................................................................................................................................. 22
LCS.............................................................................................................................................. 23
User Interface...................................................................................................................................... 23
Tools...................................................................................................................................................... 25
Launcher.................................................................................................................................... 25
System Configuration Tool (SCT).............................................................................................25
System Configuration Tool Pro (SCT Pro)...............................................................................26
Metasys Database Manager..................................................................................................... 26
VMD Generator Express (VGE Tool)........................................................................................ 26
NIEx9 Driver Manager Tool..................................................................................................... 27
Metasys System Capabilities..............................................................................................................27
Site Director............................................................................................................................... 27
Time Management................................................................................................................... 27
System Navigation.................................................................................................................... 27
Monitoring and Commanding................................................................................................ 28
Preferences................................................................................................................................ 28
Alarm and Event Management............................................................................................... 28
Encrypted Communication...................................................................................................... 29
Destination Delivery Agents (DDA)......................................................................................... 30
Syslog DDA.................................................................................................................................30
RADIUS Server Accounts.......................................................................................................... 30
Encrypted Email........................................................................................................................ 31
Scheduling................................................................................................................................. 31
Historical Data Management (Trend)..................................................................................... 31
System Security......................................................................................................................... 32
Logic Connector Tool (LCT)...................................................................................................... 34
Interlock Object.........................................................................................................................34
Optimal Start............................................................................................................................. 34
Demand Limiting and Load Rolling........................................................................................ 34
Audit Trails (Transaction Data Management)........................................................................34
System Diagnostics and Serviceability................................................................................... 35
Metasys for Validated Environments.......................................................................................35
UL 864 10th Edition UUKL and ORD-C100-13UUKLC Smoke Control Listing.................... 35
Reporting Capabilities.........................................................................................................................36
ii Metasys System Configuration Guide

Metasys Export Utility Software............................................................................................... 36
Metasys Advanced Reporting System..................................................................................... 36
Energy Essentials...................................................................................................................... 36
Metasys Graphics Options................................................................................................................. 36
Metasys UI Graphics..................................................................................................................36
Graphics+................................................................................................................................... 37
Standard Graphics.................................................................................................................... 38
Advanced Graphics Application Software..............................................................................38
Integrations..........................................................................................................................................38
BACnet/IP Integration.............................................................................................................. 38
MS/TP Communications Bus................................................................................................... 38
N2 Field Bus...............................................................................................................................39
N1 Integration (Release 9.0 or earlier)...................................................................................39
LonWorks................................................................................................................................... 39
Modbus...................................................................................................................................... 39
M-Bus..........................................................................................................................................39
KNX............................................................................................................................................. 39
C·CURE 9000 Access Control....................................................................................................39
victor Video Management....................................................................................................... 39
Simplex Fire system.................................................................................................................. 39
Cree and Molex Lighting Systems.......................................................................................... 40
Metasys System Revision Compatibility Overview........................................................................... 40
General Compatibility Information for Customer Job Sites................................................ 40
Compatibility Rules for CCT and Field Controller Revisions................................................ 40
Output Controller Module Upgrades..................................................................................... 41
Working with SCT Release 11.x or Later at Metasys Release 8.x and Later....................... 42
Graphics+ Release 1.3.............................................................................................................. 42
FEC, FAC Wireless Integrations................................................................................................42
WNC1800/ZFR182x Pro Series Wireless Field Bus System...................................................43
Metasys System Configuration Guide iii

LCS85 Compatibility..................................................................................................................43
Metasys System Configuration Examples......................................................................................... 43
Multiple NAE System Configuration with One NAE Designated as the Site Director....... 43
ADS/ADX Site Director with Multiple NAEs System Configuration..................................... 44
ADS/ADX Site Director and Secure NAE-S with Unencrypted NAEs.................................... 44
ADX Split Configuration............................................................................................................45
Unified and Split ADX with Dual Network Cards...................................................................47
Large ADX Site Configuration..................................................................................................48
ODS Workstation Configurations............................................................................................48
N1 Integration System Configuration.................................................................................... 50
BACnet/IP Network System Configuration............................................................................ 50
Third-Party Network Integration............................................................................................ 52
Wireless Metasys System Configurations............................................................................... 52
Smoke Control Application Configuration............................................................................. 53
Performance Guidelines and Limitations.........................................................................................54
Site Director Limitations and Recommendations................................................................. 54
Network Engine Hardware Limitations..................................................................................56
Alarm and Trending Performance Guidelines.......................................................................58
MS/TP Performance Guidelines.............................................................................................. 59
SCT Limitations..........................................................................................................................59
FAC Integration Considerations.............................................................................................. 59
Transfer limitations...................................................................................................................60
Technical Specifications and Requirements................................................................................60
Hardware Configuration Requirements........................................................................................... 60
Client Computer Requirements for UI Client Devices.................................................................... 61
Application and Data Server (ADS) System Requirements.............................................................63
Extended Application and Data Server System Requirements (Unified 10 or 25

User ADX)................................................................................................................................... 66
Extended Application and Data Server System Requirements (Split 10 or 25 User ADX).......... 70
iv Metasys System Configuration Guide

Extended Application and Data Server System Requirements (Unified 50 or 100
User ADX)................................................................................................................................... 74
Extended Application and Data Server System Requirements (Split 50 or 100 User ADX)........ 77
SCT Technical Specifications...............................................................................................................81
Metasys UI and Metasys UI Offline Technical Specifications........................................................... 83
CCT Technical Specifications.............................................................................................................. 86
NxE85/NIE89/LCS85 Technical Specifications.................................................................................. 88
Graphics+ Viewer Requirements....................................................................................................... 90
Metasys System Related Documentation.................................................................................... 91
Metasys System Configuration Guide v

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. It is an
expansion and replacement for the Metasys System Extended Architecture Overview Technical Bulletin
(LIT-1201527).
For a list of Metasys system related documentation, see Table 35 at the end of this document.
Summary of Changes
The following information is new or revised:
• Changed the information flow from top-down to bottom-up, starting with the basic components
of the Metasys system.
• Updated equipment controller content to reflect new models and enhancements.
• Updated network diagrams for the new release.
• Updated Metasys UI Release feature updates.
• Added information about the new integrations, including SIMPLEX® Fire System, C·CURE 9000
Access Control system, victor Video Management system, and Cree® and Molex® digital lighting
systems.
• Updated CCT Release feature updates.
• Updated SCT Release feature updates.
• Added information about the new SCT Pro UI.
• Updated password rules in System Security.
• Removed section on P2000 integration. The integration between the P2000 Security
Management System and the Metasys Building Automation System is no longer supported at
Release 10.0.
• Updated Network Engine Hardware Limitations.
• Updated Technical Specifications.
• Updated Related Documentation.
• Removed Windows® 7 Professional, Enterprise, and Ultimate Editions with SP1 (32-bit). This
operating system is no longer supported for host computers at this release. However, Windows 7
(32-bit) is still supported for client computers.
• Changed licensing document referenced in Related Documentation to Software Activation

Manager Help (LIT-12012389).
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.
Metasys System Configuration Guide 7

A Metasys site comprises one or more Metasys devices on a continuously connected IP network.
A site’s primary network consists of one or more engines. The engines also provide the Site
Management Portal UI. You can configure the primary network and monitor the users of all
devices on the network with the Site Management Portal UI. The engine types are Network
Automation Engines (NAEs), Network Integration Engines (NIEs), 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 BACnet® Open Data Servers (ODS), which are described in
further detail in this document. Metasys servers provide the same Site Management Portal UI as the
engines. Additionally, the Metasys UI is installed with the Metasys server software.
Each Metasys site has one device (engine or server) that is designated as the Site Director. Typically,
the Site Director is the single point of access for all Site Management Portal UI users because the
Site Director includes a view of all Metasys devices on the site. If a server is connected to a site, you
must designate the server as the Site Director. For more information, see Site Director.
Figure 1 shows an example Metasys system configuration. The Metasys System Configuration
Examples section shows a variety of configuration examples.
Figure 1: Example Metasys System Configuration
Equipment Controllers
Metasys includes several model series of equipment controllers, including General Purpose
Application Controllers (CGMs), VAV Box Controllers (CVMs), Advanced Application Field Equipment
Controllers (FACs), Field Equipment Controllers (FECs), Variable Air Volume Modular Assembly
(VMAs), and Input/Output Modules (IOMs). These devices provide direct, operational control over
HVAC and other mechanical and electrical equipment and are typically networked together and
supervised by network engines. The BACnet® family of controllers is tested by an independent
BACnet Testing Lab. A complete listing of the tested Johnson Controls® BACnet devices is available
at the following link: http://www.bacnetinternational.net/btl/index.php?m=15
General Purpose Application Controllers (CGMs) and VAV Box Equipment

Controllers (CVMs)
Starting at Metasys Release 10.0, a new family of equipment controllers is available. The first two
models of this new, modernized family are the M4-CGM and the M4-CVM equipment controllers.
8 Metasys System Configuration Guide

Figure 2: General Purpose Application Controller
(CGM) and VAV Box Equipment Controller (CVM)
The following table describes the new equipment controllers in detail.

Table 1: New Equipment Controllers at Release 10.0
M4-CGM09090-0 M4-CVM03050-0 M4-CVM03050-0P

Description General Purpose VAV Box Controller VAV Box Controller with
Application Controller position feedback
Inputs/Outputs • 18 total inputs and • 8 total inputs and • 8 total inputs and
outputs: 7 UI, 2 BI, 4 outputs: 3 UI, 2 CO, outputs: 3 UI, 2 CO,
CO, 2 AO, and 3 BO and 3 BO and 3 BO
• Supports SA Bus • Integral actuator • Integral actuator
expansion • Integral DPT • Integral DPT
• Supports SA Bus • Integral
expansion potentiometer to
sense actual VAV box
damper position
• Supports SA Bus
expansion
Field Bus Networking • BACnet MS/TP • BACnet MS/TP • BACnet MS/TP
and Tools • N2 • N2 • N2
• ZigBee for ZFR Pro • ZigBee for ZFR Pro • ZigBee for ZFR Pro
Wireless Field Bus Wireless Field Bus Wireless Field Bus
(add-on modules) (add-on modules) (add-on modules)
• CCT 13, Release • CCT 13, Release • CCT 13, Release
Mode 10.4 Mode 10.4 Mode 10.4
Firmware package New Metasys field controller firmware package files for CCT (MS-FCP-0)
files are available for the latest field controllers from the central installation
server that allow Johnson Controls employees, channel partners, and
end customers to source and license the use of their field controller
packages.

Table 2: New Equipment Controllers features and benefits
Feature Description Benefits

New packaging and styling New equipment controller Provides a modern,
models are packaged in black aesthetically pleasing industrial
enclosures with rounded design.
corners.
Removable screw terminal Pluggable input/output wiring Provides electrical installers
blocks terminal blocks that can be and field technicians the ability
removed from the controller. to quickly and easily install and
service a controller without
the need to disconnect and
reconnect the input/output
wiring.
Decimal MS/TP address set Three rotary switches are used Easy-to-use rotary switches set
with three rotary switches to set the MS/TP address in a the MS/TP address in decimal
decimal format (x100, x10, x1). format.
High memory capacity and New 16MB flash memory Provides application engineers
fast processing power (formerly 640KB-2MB); new with more horsepower to meet
8MB SRAM/DRAM memory more sophisticated control
(formerly 128KB-1MB); new 120 requirements.
MHz processor speed (formerly
32 MHz)
Background transfer Enables downloading of Saves field technicians’
firmware and controller time, enables productivity
application files that can and minimizes equipment
be applied at a later, disruption, since the controllers
predetermined time and in are operating while file updates
the background while field take place in the background
controllers are still operating. and the application can be left
This can be done on multiple disabled until the system is
controllers at the same time ready to run.
for further efficiency. Once
firmware and controller
application files are applied,
you can decide when to enable
the logic of applications in a
device using the Enable Logic/
Disable Logic options in CCT.
Improved SA Bus Enables a field controller to Saves field technicians time
commissioning transfer and apply firmware when commissioning SA Bus
files to all the SA Bus IOM IOM devices.
devices connected to it at the
same time.

Table 2: New Equipment Controllers features and benefits
Feature Description Benefits

Common release mode CCT programming and • Improves the productivity
commissioning for new and of controls technicians and
recently-released controller reduces their frustrations
models can be performed in by mitigating the need to
the same CCT release mode. switch between multiple CCT
release modes.
• Provides configuration
consistency, simplicity,
and efficiency through CCT
during configuration and
commissioning.
BACnet MS/TP support New controller models Ensures openness and
have been BTL-listed at interoperability with other
Protocol Revision 15 as BACnet devices and systems.
BACnet Advanced Application
Controllers (B-AAC).
Wireless ZFR and ZFR Pro Provides wireless connectivity • Provides a wireless
support between field controllers and alternative to hard-wired
network engines over the Field MS/TP networking, offering
Controller (FC) bus. application flexibility and
mobility with minimal
disruption to building
occupants.
• Simplifies and speeds up
replacements.
N2 support Enables a field controller to Provides a cost-effective
be installed in an existing N2- migration path for customers
based system. with legacy, N2-based offerings
with a single controller model
(rather than multiple models
for BACnet MS/TP and N2
support).
Auto-detection of Controller auto-detects the Enables the same controller
communication protocol protocol that is connected to it. to support multiple
communication protocols
without the need to purchase a
special model per protocol, and
without extra manual setup.
Optional integrated feedback Provides feedback of the VAV Reassures users and field
potentiometer on VAV box damper’s actual position. technicians of the VAV box
controller damper’s actual position and
enables them to easily confirm
and troubleshoot VAV controller
operations, confirm that the
actuator is at the desired
position, and track the damper
position.

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

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

FEC Field Equipment Controller Family Comparison
Table 3: Field Equipment Controller Family Comparison
Advanced Application Variable Air

Field Equipment
Field Equipment Volume Modular
Controllers (FECs)
Controllers (FACs) Assemblies (VMAs)
Typical Applications Controlling: Controlling: Controlling:
• Rooftop Units • Equipment that requires • Pressure

local scheduling, alarming, independent VAV
• Heat Pumps boxes
and trending
• Unit Ventilators • Pressure
• Air Handling Equipment
• Air Handling dependent VAV
Equipment • Central Plant Equipment boxes
• Central Plant • Zone Dampers
Equipment
• Exhaust Fans
• Supplemental
Heating
Equipment
Processor 32-bit 32-bit 32-bit
Onboard Real Time No Yes Yes - on IP VMA1930
Clock model only
Communication • BACnet MS/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) (model switchable)
• ZigBee Wireless IP FAC4911 only) • BACnet/IP (B-
(with an add-on • ZigBee Wireless (with an AAC): (model IP
module) add-on module) VMA1930 only)
• ZigBee Wireless
(with an add-on
module)
Expandable through Yes Yes Yes
SA Bus
Programmable Yes Yes Yes
Control Logic
Programming Tool CCT CCT CCT
Commissioning Tool CCT, MAP CCT, MAP CCT, MAP
VMA VAV Modular Assembly Series

VMA16 (16-bit) VAV Modular Assembly
VMA16 (16-bit) VAV Modular Assembly controllers are programmable BACnet application specific
controllers with RS-485 MS/TP communications. VMA controllers feature an integral 4 N•m damper
actuator and Differential Pressure Transducer (DPT) with models for cooling only or cooling
with reheat applications and fan control. The differential pressure sensor in the VMA16 (16-bit)
controllers provides consistent flow readings with minimal drift and requires minimal auto-zero
calibration. There are no filters to change, which helps to ensure very close tolerance to published
accuracy. The VMA16 (16-bit) controllers can be configured for single-duct, dual-duct, and supply/
exhaust applications. Note that some of these applications may require an additional actuator

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

The IOM Controllers are expansion input and output modules with integral RS-485 MS/TP
communications. IOMs can serve in one of two capacities, depending on where they are installed in
the Metasys system. When installed on the SA Bus of a CGM, CVM, FAC, FEC, or VMA controller, the
IOMs expand the point count of these controllers. When installed on the FC Bus, the IOMs support
monitoring and control from an NAE or NCE as I/O point multiplexors. The point multiplexor can
also be useful for sharing points between other field controllers on the FC Bus using peer-to-
peer connectivity. A full range of CGM, CVM, FAC, FEC and VMA models combined with the IOM
models can be applied to a wide variety of mechanical and electrical equipment control applications
ranging from simple fan coil or heat pump control to advanced central plant management.
Wireless Solutions
Several wireless Metasys solutions are available for integrating wireless connectivity in desired
portions of a Metasys network. These solutions provide wireless communication between
controllers, thermostat controllers, coordinators, routers, and room sensors.
• ZFR181x Series Wireless Field Bus System

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

You use the Controller Configuration Tool (CCT) to configure, simulate, commission, and transfer
application files to the following controllers on a BACnet MS/TP bus:
• Field Equipment Controllers (FECs)
• Advanced Application Field Equipment Controllers (FACs)
• Input/Output Modules (IOMs)
• General Purpose Application Controllers (CGMs)
• Variable Air Volume Box Equipment Controllers (CVMs)
• Variable Air Volume Controllers (VAVs)
• Variable Air Volume Modular Assembly Controllers (VMAs)

CCT operates in three modes that provide key functionality for your system:
• Use the Configuration mode to select a wide variety of mechanical and control logic options
through system selection trees for typical air handling, terminal unit, central plant, and VAV
box mechanical systems. When required, 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 set up break points that pause the simulation session
based on criteria that you set up. While viewing a simulation session, transitions taking place in
the logic are highlighted for a few seconds to help you quickly identify where the changes occur.
• Use the Commissioning mode to connect to a device and view actual data from that device. You
can use this mode to monitor your device and set Offsets, COVs, and Polarity in addition to other
parameter and detail changes.
For VAV applications, CCT includes an optional box flow test to automatically exercise all the VAV
boxes to ensure correct mechanical installation and proper configuration of the key flow setup
parameters.
The ZFR Checkout Tool (ZCT) is available to validate the wireless connectivity and health of your
wireless mesh network. Refer to the ZFR Checkout Tool Help (LIT-12012292) for details.
Controller Application Files (CAFs) can be transferred and commissioned to a device through a wide
variety of connection interfaces including: NxE Passthru, MAP 4.2+ / BACnet router, ZigBee, and
Direct Ethernet.
CCT and the Facility Explorer® Programmable Controller Tool (FX-PCT) are no longer separate
software tools. Users of CCT and FX-PCT at Release 10.2 must first uninstall the previous version

before installing Release 13.0. Users of CCT and FX-PCT software at Release 10.3 can upgrade
directly to Release 13.0. For information on how to upgrade to or install CCT, refer to the CCT
Installation Instructions (LIT-12011529).
For a list of updated features and benefits available at CCT Release 13.0, refer to the Controller
Configuration Tool (CCT) Catalog Page (LIT-1900386).
TEC3x00 Series Networked Thermostat Controllers

The TEC3x00 Series Thermostat Controllers are configurable, application-specific controllers with
embedded sensors. TEC3x00s are housed in enclosures suitable for mounting on a wall in an
occupied space, and each model features an intuitive user interface with backlit display that makes
setup and operation quick and easy.
Depending on the model and configuration options you select, TEC3x00s provide on/off, floating,
and proportional control of:
• local hydronic reheat valves
• pressure-dependent VAV equipment with or without local reheat
• two- or four-pipe fan coils
• cabinet unit heaters
• other zoning equipment using an on/off, floating, or 0 to 10 VDC proportional control input
• single- or two-stage unitary rooftop units (RTUs) and heat pumps, with or without economizers
The TEC3600 series models feature field-selectable BACnet MS/TP or N2 communication capability,
enabling supervisory control from a Metasys network engine or communication to third-party
BAS devices. The TEC3000 series models feature ZFRPro compatible wireless communication
capabilities, enabling supervisory control from a Metasys network engine through a Wireless
Network coordinator.
Network Engines
Network engines perform a key role in the Metasys system architecture. These network engines
provide network management and system-wide control coordination over one or more networks of
equipment controllers, including the following Metasys field controllers:
• General Purpose Application MS/TP Controllers (CGMs)
• VAV Box Equipment MS/TP Controllers (CVMs)
• Field Equipment Controllers (FECs) and Advanced Application Field Equipment Controllers (FACs)
• Variable Air Volume Modular Assembly (VMA) Controllers

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

Large-capacity engines
• Network Automation Engine: NAE55
• Network Integration Engines: NIE55 and NIE59

Software-only engines
• Network Automation Engine: NAE85
• Network Integration Engine: NIE85 and NIE89

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.
NAE
The NAE is available in many different models with options to support various communications
protocols including BACnet over IP, BACnet® MS/TP, N2 Bus, N2 over Ethernet, and LonWorks®
protocol. Built-in support for third-party protocols, including Modbus, M-Bus, KNX, and Tyco
C•CURE 9000/victor is also included. The following models are available:
• The NAE55 Series supports a comprehensive set of supervisory control features and functions for
large facilities and technically advanced buildings and complexes.
• The NAE-S (MS-NAE551S-x) is a secure NAE55 with increased security features—embedded

encryption technology under a securely fastened enclosure to protect and secure the building
management system at the endpoint. The engine meets the Federal Information Processing
Standard (FIPS 140-2), Security Level 2, that specifies the use of a cryptographic module and a
tamper-proof housing.

• The NAE35 and NAE45 Series extend the power of the NAE to the smaller buildings (or small
areas of larger buildings) and enable the wider distribution of supervisory control functions in
larger facilities.
• The NAE45-Lite, available only in specific markets, is a functionally limited NAE45 that you cannot
use as a Site Director and functions only with a corresponding ADS-Lite.
Note: The NAE45-Lite engine does not support the Remote Field bus.
• The NAE85 supports large BACnet/IP integrations.
NCE
The NCE provides support for the same communications protocols as the NAE, but also offers
the Input/Output (I/O) point connectivity and direct digital control capabilities of a Metasys Field
Equipment Controller (FEC). The NCE provides a cost-effective solution designed for central
plants and large built-up air handler applications. All NCE models provide IP Ethernet network
connectivity, the Site Management Portal UI, and the network supervisory control functions
featured on network automation engines. Depending on the model and software release, an NCE
supports either a BACnet MS/TP Bus, an N2 Bus, or a LonWorks network trunk. Built-in support for
third-party protocols, including Modbus, M-Bus, KNX, and Tyco C•CURE 9000/victor, is also included.
NIE55/NIE85
The NIE55/NIE85 are specialized versions of the NAE and are designed to provide for the migration
of existing N1 networks into the current generation Metasys system. These models are only
available at Metasys Release 9.0 or earlier. The NIE55/NIE85 provided the same Site Management
Portal UI as the NAE. Unlike the NAE, the NIE55/NIE85 does not support integration of BACnet MS/
TP or BACnet/IP, N2, or LonWorks networks. Two models of the NIE55/NIE85 are available. The
NIE55 supports smaller N1 networks, whereas the NIE85 supports large N1 integrations.
NIEx9
The NIEx9 is a specialized version of the NAE and is designed for integration of building control
devices that communicate over the MODBUS®, MBus, KNX, or Tyco C•CURE 9000/victor protocol.
The NIEx9 also communicates over the BACnet MS/TP, BACnet/IP, N2, or LonWorks networks.
This specialized version of the NIE is designed to provide for the migration of these existing third-
party networks into the current generation Metasys system. The NIEx9 provides the same Site
Management Portal UI as the NAE or NIE. The following models are available:
• NIE59 Series (Release 10.0) supports two integrations in addition to a BACnet MS/TP, BACnet/
IP, N2, or LonWorks network for use at large facilities and technically advanced buildings and
complexes.
• NIE39 and NIE49 Series (Release 9.0.7) extends the integration power of the NIE to the smaller
buildings (or small areas of larger buildings) and enables the wider distribution of integration
functions in larger facilities. These engines support two integration integrations in addition to a
BACnet MS/TP, BACnet/IP, N2, or LonWorks network.
• NIE29 Series (Release 9.0.7) combines the network integration capabilities of an NIEx9 with the
Input/Output (I/O) point connectivity and direct digital control capabilities of a Metasys Field
Equipment Controller (FEC). These engines support two integration integrations in addition to a
BACnet MS/TP, BACnet/IP, N2, or LonWorks network.
• NIE89 (Release 9.0.7) provides a computer-based version of the NIE59 that supports large
integrations. This engine supports eight total integration integrations in combinations of four
(for example, four Modbus TCP and four KNX TCP).

Network Engine Comparison
Table 4: Network Engine Release support comparison
Model Release 9.0 Release 9.0.7 Release 10.0

NCE25 X X
1
NAE35, NAE45 X X
2
NAE55 X X
3
NAE85 X X
NIE29, NIE39, NIE49 X X
4
NIE59 X X
5
NIE89 X
NIE55, NIE85 X
1 Only NCE25xx-0 is available to upgrade to Metasys 9.0.7 with Linux OS.

2 Only NAE35xx-2 and NAE45xx-2 are available to upgrade to Metasys 9.0.7 with Linux OS.
3 Only NAE55xx-2 and NAE55xx-3 are available to upgrade to Metasys 10.0 with Linux OS.
4 Only NIE29xx-0s, NIE39xx-2, and NIE49xx-2 are available to upgrade to Metasys 9.0.7 with Linux OS.
5 Only NIE59xx-2 and NIE59xx-3 are available to upgrade to Metasys 10.0 with Linux OS.
Important: All NIEx9 models, with the exception of the NIE59 model, are no longer offered
at Metasys system Release 10.0 because NAEs at Release 10.0 now include the integration
functionality from Release 9.0.x.
Table 5: Network Engine integrations available by Metasys Release
Integration Release 9.0 Release 9.0.7 Release 10.0

BACnet/IP X X X
BACnet MS/TP X X X
Legacy N1 LAN X
Legacy N2 Bus X X X
LonWorks X X
Modbus RTU and TCP X X X
M-Bus Serial and IP X X X
KNX IP X X X
C·CURE 9000 and victor X
Simplex Fire (secondary monitoring only) X
Preferred Vendor Lighting Systems X
Servers
ADS and ADS-Lite
The ADS is a Metasys server running on a computer that has a supported Microsoft® Windows®
operating system and two specific components. The first component is the relational database
management system using a supported edition of Microsoft SQL Server® Express software to

store collected trend data, audit trail messages, and alarm and event messages with operator
annotations. The second component is the web server software that provides SMP UI and Metasys
UI access to data and routes commands to the Metasys system.
The ADS also:
• supports a greater number of engines as a Site Director than an engine supports
• supports multiple, simultaneous international languages at the user interfaces
• allows a greater number of simultaneous users than is supported by an engine
• provides added storage for memory-intensive Metasys features, such as User Graphics
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
Table 6: Application and Data Server Family Comparison
Feature Application and Data Server (ADS) Extended Application and Data
Server (ADX)
Host Platform Desktop computer platform: Server platform:
• Microsoft Windows® operating • Microsoft® Windows Server®

system operating system
• Microsoft SQL Server Express • Microsoft SQL Server database
database
• Open Database Connectivity (ODBC)
compliant database package
Supported Up to 5 users Up to 10, 25, 50, or 100 users (license
Simultaneous specific)
Users
Network Engine Up to 14 engines Up to 1,000 engines (support for
Management engines varies depending on size of
server hardware)
Archival of Manual, scheduled, or automatic Manual, scheduled, or automatic
Historical Data
User Interface Metasys UI Metasys UI
SMP SMP
Supports Export Yes Yes
Utility
Supports Metasys No Yes
Advanced
Reporting
Supports Energy No Yes
Essentials
Support for Split No Yes
Configuration

Table 6: Application and Data Server Family Comparison
Feature Application and Data Server (ADS) Extended Application and Data
Server (ADX)
Supports Metasys No Yes
for Validated
Environments
(MVE)
Five Years of Metasys UI Metasys UI
Historical Data
For more information, refer to the Application and Data Server (ADS) and Extended Application and
Data Server (ADX) Product Bulletin (LIT-1201525).
ADX
The ADX is a version of the ADS with extended capabilities for historical data archiving that expand
the multi-user web access capabilities of the system. The ADX supports the relational database
management system that uses a supported edition of Microsoft SQL Server software to store
collected trend data, audit trail messages, and alarm and event messages with user annotations.
This relational database also stores configuration information for site security, trend studies,
and other features. The ADX supports the Metasys Advanced Reporting System, which has a web-
based reporting interface and standard report sets. The users can review the alarm and trend
configuration of their site, run summary and detail reports to monitor alarm and event information,
view offline information, combine alarm and audit information in a single report, and aggregate
trend data at a summary or detailed level. An ADX can also support the optional Energy Essentials
reporting feature, which is an extension of the Metasys Advanced Reporting System.
If the ADX software with its accompanying SQL Server database software is installed on one
computer, it is known as a Unified ADX. If the SQL Server software is located on a different
computer, it is set up 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.
Supported Concurrent Users

ADS/ADX concurrent users
The following table shows examples of the total number of supported users who can be
simultaneously logged in to the SMP and Metasys UI.
Table 7: Examples of ADS/ADX/ADS-Lite concurrent users
ADS/ADX type Examples of ADS/ADX concurrent users

SMP UI Metasys UI
5-user ADS/ADS-Lite 0 5
2 3
5 0
10-user ADS 0 10

Table 7: Examples of ADS/ADX/ADS-Lite concurrent users
ADS/ADX type Examples of ADS/ADX concurrent users

SMP UI Metasys UI
5 5
8 2
10 0
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
10 50
25 50
50 50
75 0
100 0
For example, as shown in Table 7, 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 10
Metasys UI users are supported if 40 SMP users are logged in. The only Metasys UI user restriction
applies to a 50-user or 100-user ADX: no more than 50 Metasys UI users are supported, regardless
of the number of SMP users.
ODS
Important: ODS is supported at Release 9.0 but not upgradable to Release 10.0.
The Metasys Open Data Server (ODS) is a BACnet Testing Laboratories® (BTL) Listed BACnet®
Operator Workstation (OWS). It conforms to the B-OWS profile. The ODS supports up to 25,000 local
objects and up to five users. You can configure the ODS as a BACnet Workstation, as a Site Manager
Workstation, or as a Combined Workstation.
In the BACnet Workstation configuration, the ODS uses the BACnet protocol to communicate
with networked BACnet devices. BACnet integration maps NxEs, Field Equipment Controller (FEC)-
family devices, and BACnet devices into the ODS. NxEs and FEC-family devices are treated the same
as BACnet devices. This configuration is best for the customer who requires a BACnet operator
workstation using standard BACnet messages. BACnet features are emphasized, and viewable
object capacity is limited to 25,000 objects.
In the Site Manager Workstation configuration, the ODS acts similarly to an Application and Data
Server/Extended Application and Data Server (ADS/ADX) and uses web services to communicate
with the NxE network engines. Other BACnet devices are mapped into the Metasys system through
the NxE using BACnet integration. The Site Manager Workstation configuration is best when
features and capability (for example, object capacity and performance) are more important to
the customer than strict use of standard BACnet services. The ODS provides all advanced Metasys
system features, and the viewable object capacity includes all of the objects from all of the network
engines reporting to the Site Manager Workstation. In this configuration, the ODS can serve as the

Site Director for up to 100 NxE network engines. In addition, you can connect Johnson Controls® IP
controllers, Johnson Controls MS/TP controllers, and BACnet MS/TP devices over a remote field bus
with the use of a BACnet/IP-to-MSTP router.
In the combined configuration of BACnet Workstation and Site Manager Workstation, the strengths
of both configurations are combined to deliver an optimal solution to the customer. NxE network
engines can use the ODS as a Site Director and communicate with the ODS using web services,
allowing extended object capacity and advanced Metasys system features. In addition, the ODS can
directly access BACnet devices and FEC-family devices using the BACnet integration capability of the
ODS. This configuration is best for the customer who values features and capability, and also needs
the functionality of a BACnet operator workstation for BACnet devices not associated with a Metasys
engine. In this way, operator monitoring and control is extended to BACnet devices outside of the
control of a Metasys engine.
Table 8 lists which Metasys products are compatible with the ODS Workstation.
Table 8: Metasys Products Compatible with ODS
Metasys Product or Feature ODS Compatibility

Advanced Graphics Application (AGA) Not Supported
Controller Configuration Tool (CCT) Supported
Energy Essentials Supported
FECs, FACs, IOMs Supported
Graphics+ (GGT) Supported
Metasys Advanced Reporting System Supported
Metasys Database Manager Supported
Metasys Export Utility (MEU) Supported
Metasys for Validated Environments (MVE) Not Supported
Metasys UI Not Supported
NxE Engines Supported
ODS Split Configuration Not Supported
Standard Graphics (UGT) Supported
System Configuration Tool (SCT) Supported
ZFR Wireless Network Not Supported
LCS
The LCS85 is a computer-based server that is used to communicate with LonWorks devices
over an IP network. The LonWorks field devices are normally connected to an IP router. In this
arrangement, the Metasys system is used in a flat LonWorks configuration.
User Interface
Two variations of the user interface are available: Metasys UI and Site Management Portal (SMP).
The Metasys UI provides a simple location-based navigation approach to finding information,
including the ability to search for any location by name and to bookmark a location in the browser.
All data displayed in the Metasys UI is organized in a dashboard format, presenting to you the
complete story of what is happening within a space, equipment, or central plant. You can access
the Metasys UI from any type of client device with any screen size. The Metasys UI includes features
ideal for efficient building operations, including:
• views of all equipment serving a space or another piece of equipment
• a single view of all items in alarm, warning, overridden, out of service, and offline states within a

space
• a single view to understand the correlation between disparate events within the system
• trends of historical equipment data for up to 10 points (computer platform) and four points
(tablet and phone platforms) at a time, on up to three different charts at once
• views of all relationships a piece of equipment has with other equipment, spaces, and network
field controllers
• comparisons of all similar equipment that directly serves the space and all downstream spaces
• viewing floor plan and equipment graphics without the need for third-party plug-ins or additional
spaces
• viewing and managing alarms by space and equipment
• viewing alarms while not logged in (Alarm Monitor)
• commanding and modifying points relating to spaces and equipment in bulk
• a single view to determine what command priority is currently active on a point object
• viewing and editing space and equipment schedules
• creating, editing, and managing Metasys UI graphics
• importing and exporting custom symbols with the Custom Symbol Library
• managing legacy graphic associations with spaces and equipment
• smart filtering by launching directly from certain widgets into a pre-populated Advanced Search
• scheduling reports that are regularly emailed to you
• tracking the ways users interact with the Metasys software with Usage Analytics
The Metasys SMP provides real-time and historical data views, extensive alarm management
capabilities, and system configuration functions for system administrators or dedicated building
operators. The SMP transforms the raw data from the site and organizes it into a comprehensive
set of information management tools and reports. You can access this portal using the Launcher
through an Internet or intranet connection to a Metasys server or engine. The SMP has all the
features one expects from a traditional workstation, including:
• pop-up alarm windows
• navigation tree—you can create multiple custom trees to best represent the logical layout of the
facility
• dynamic graphics of systems and floor plans that you can zoom in on to show fine details
• multiple display areas you can size and control individually
• global search function and sorting capability that help you find system information within
seconds
• the entire user manual available in the Help system
Information Management is an inherent capability of the overall user experience and reporting
capabilities. Whether you are logged in to the SMP UI running online reports, using the Metasys
Advanced Reporting System, or retrieving data from an engine with the Export Utility, you are
transforming the data collected by the system into information you can use to manage your site.

Tools
Launcher
The Launcher is a software application that lets you use the SMP or SCT to access the Metasys
system, server or network engine on the building network, regardless of its software version. Key
features of the Launcher include:
• Installation of a separate folder to store the Metasys release software on your hard disk. This
practice provides for an isolated, private version of the Java® Runtime Engine (also referred to as
Java Runtime Environment [JRE] ) required to run Metasys software. If you have installed multiple
releases of Metasys software, a separate folder is created for each. The JRE folder separation
strategy allows for independence from the public Java Runtime Engine.
• Support for launching any version of the SMP, ODS, and SCT UIs. Supported site directors include
the ADS, ADX, ODS, NAE, NIE, and NCE.
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.
Note: ODS is not supported at Release 10.0.
• Support for launching any website, including Metasys software products, such as Metasys UI,
Metasys UI Offline, SCT Pro, and the Metasys Advanced Reporting System, as well as popular
websites such as the Google® website.
• Option for restricting communication with only secure Metasys servers and network engines.
Contact your local Johnson Controls® representative for access to the Launcher software.
System Configuration Tool (SCT)

The System Configuration Tool (SCT) supports the engineering, installation, and commissioning of
your building automation system. The SCT application enables offline generation of the complete
site and user interface creation of the system, including point naming; integration of N1, N2,
BACnet, and LonWorks networks; integration of Modbus, M-Bus, and KNX third-party protocols;
integration of building systems such as C·CURE 9000 access control, victor video management,
Simplex fire, and connected lighting systems from preferred vendors; integration of local and
remote MS/TP devices; definition of tailored summaries and user views; and the creation of custom
control logic using a graphical user interface.
SCT also manages the maintenance of the archive database for the Network Automation Engine
(NAE), Network Control Engine (NCE), Network Integration Engine (NIE), Application and Data
Server/Extended Application and Data Server (ADS/ADX), Open Data Server (ODS), and Metasys User
Interface (UI). To keep the archive database current, the user can set up the SCT to schedule regular
uploads from the devices on the site. When the system is operational, you can make online changes
to the database at the engine, ADS/ADX, or ODS with the same user interface that was used for the
offline data generation in SCT.
SCT offers productivity features, such as the mass creation of equipment, spaces, and serving
relationships, and the migration of supervisory devices. You can also use SCT to fully manage a
mixed release site for a Metasys system at Release 5.2 or later.
SCT has a one-click installation. The new SCT installers install the required software prerequisites,
such as Internet Information Services (IIS), SQL Server 2014 Express software (if no SQL Server
present), and Microsoft .NET Framework 4.6.1.
The new SCT installers also include two additional applications. You can use the Metasys UI Offline
software to configure Metasys UI graphics and the display of data without a live connection to
devices. SCT Pro is a web application that significantly streamlines some SCT workflows, and greatly
simplifies tasks such as scheduling recurring backups, upgrading sites, and site discovery. For

example, with site discovery, you can rebuild the entire archive database from the online system.
This is a useful option if the original archive is missing, corrupt, or was never maintained.
Metasys uses secure HTTP with Transport Layer Security (TLS) 1.2 between the SCT computer, all
Metasys servers, and network engines that are upgraded to Metasys Release 9.0 and later. The
encrypted HTTPS communications apply to the ADS, ADX, ODS, Metasys UI, network engines, and
SCT. This ensures that unauthorized users and computer hackers cannot view the contents of
communications sent between Metasys devices. 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.
For a list of updated features and benefits available at SCT Release 13.0, refer to the System
Configuration Tool Catalog Page (LIT-1900198).
System Configuration Tool Pro (SCT Pro)

SCT Pro is the next generation interface for SCT. It provides significantly streamlined workflows,
and greatly simplifies tasks that were previously time consuming or cumbersome. For example, you
can use SCT Pro to maintain healthy backup practices for a site, such as setting up backups to occur
automatically on a recurring schedule. SCT Pro does not include the full range of features that are
available in SCT, but new features will be added over time; and SCT remains available for the tasks
that SCT Pro does not yet support. SCT Pro is installed during the installation of SCT Release 13.0
and later.
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
You can launch the new HTML user interface from SCT or from a URL on any client device type
(workstation, tablet, or phone).
For more information about SCT Pro, refer to SCT Pro Help (LIT-12013035).
Metasys Database Manager

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

The VMD Generator Express (VGE) tool allows you to view, create, and modify the vendor model
definition (VMD) files required by third-party integrations on the NIEx9. Both the TCP/IP and
Remote Terminal Unit (RTU) formats are supported.

The VGE tool incorporates a version tracking system that stores data and comments every time you
create or modify a file. The tool allows generic modeling for standard integrations, meters, chillers,
and air handling units (AHUs).
NIEx9 Driver Manager Tool

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

Site Director
When users access any engine or server directly through a web browser, only the information local
to that device is accessible. To make all information in the facility accessible from a single point,
the Metasys system uses a Site Director. The Site Director is the device designated to maintain
the site information, including the logical organization of data about your facility, user password
administrative information, and overall master time and date. This function resides in an engine
or, on large installations, a server. For networks that do not have a server, one of the engines is
designated as the Site Director. When one or more servers are part of the network, one server must
be designated as the Site Director. The Site Director provides a uniform point of entry and supports
functions such as user login, user administration, time synchronization, and traffic management.
Consider a server as the Site Director if you require:
• support of multiple international languages
• repository for trend and alarm data and operator transactions, along with annotations for MVE
systems
• a greater number of simultaneous users than an engine allows
Time Management
The time and date used by all devices connected to a site are synchronized automatically,
preventing errors from manual time entry and clocks that become inaccurate over time. Network-
wide time management ensures that scheduling, trending, audit trailing, data collecting, time-
stamping of alarms, and other functions requiring accurate time management use the same time
and date consistently for all system operations. Because the Site Director is the master time keeper
for all engines and servers on a single site, all of these devices are assumed to use the same time
zone for all time-rated functions.
For network-wide time synchronization, the engine or server acting as Site Director is the time
server for the entire site. All other devices are time clients because they receive the time from
the Site Director. The Site Director can be configured to use three different methods of time
synchronization: Unicast Simple Network Time Protocol (SNTP) (also known as Microsoft Windows
time synch), Multicast SNTP, or BACnet time synch. The Site Director can also be configured to synch
its time from an external website.
New multi-time zone enhancements allow you to schedule events using local machine time
management instead of calculating the Site Director time in relation to the device hosted in a
different time zone.
System Navigation
The Metasys UI supports navigation in the form of spaces and equipment relationships. A space is
the physical location or area that is served by a piece of equipment. Equipment is the broad term
used to describe the physical controllers and devices that make your building run. These controllers

and devices include boilers, chillers, air handling units, lights, meters, security, and anything else
used to maintain your building's environment. Equipment can serve spaces and other equipment.
A Metasys system administrator can create spaces and equipment and define the relationship
between them in SCT.
The Building Network tree in Metasys UI provides access to objects using an alternative navigation
tree to the Spaces tree. The Building Network organizes objects according to the Metasys object
hierarchy, similar to the All Items tree in the SMP. The Building Network tree supports the Detail
widget, which supports the Focus view, Network view, and Diagnostic view, the Summary view
widget, Equipment Relationships widget, and Trend widget depending on the object selected.
Objects listed in the Building Network tree are identified by name and by icon and display Global
Status indicators.
Note: The Building Network tree order is inherited from the SMP All Items tree with minor
exceptions. For example, extension objects appear in the All Items tree in the Metasys UI,
whereas they do not appear in the All Items tree in SMP. To reorganize the order, use the All
Items tree organizer in SMP.
The SMP UI supports user-customized system navigation schemes in the form of User Views,
a hierarchical method of organizing and displaying some or all of the items within a system. A
Metasys system administrator can limit a user’s access to the Metasys system by creating User Views
and assigning them to specific users. User Views provide organizational structure and data filtering
for the information displayed in the Metasys Advanced Reporting System UI.
Monitoring and Commanding

Monitoring and commanding allows you to efficiently navigate through items associated with your
building operations as well as view, analyze, and modify these items. After creating items with
wizards, use these features to:
• access, view, and modify item data
• send commands to items
• run reports to analyze item information
Preferences
The Metasys system provides customized preferences for the Metasys user interfaces. The
preferences allow you to configure how the user interfaces behave, including the sounds and
colors, the startup views, alarm priorities, and links from within the user interfaces to external
applications. Preferences are divided into two categories: system preferences and user preferences.
System preferences apply to all users who log in to the site or device and affect the performance
and operation of the system. User preferences apply to a specific Metasys system user and define
how information is displayed in the user interfaces. User preferences do not affect the operation of
the system.
At Metasys Release 8.0 and SCT Release 11.0 and later, user preferences are stored in archives. You
no longer need to reconfigure your settings or object lists after upgrading or updating.
Alarm and Event Management

The alarm and event feature provides event management for the system. Users can configure the
routing of event messages to destinations such as the server for permanent storage. The Metasys
Site Management Portal UI features a pop-up alarms window, which alerts the operator to potential
problems whenever the operator is logged in to the system; and an event viewer, which provides
for greater analysis or a history of alarms and events in the system.
Note: To ensure proper pop-up alarm functionality, always use the Desktop mode for Windows
10, Windows 8.1, or Windows Server® 2012 R2 computer.
Users can configure alarms and events with the Metasys system, using either a Metasys alarm
extension or a BACnet alarm (intrinsic or algorithmic). Metasys alarm extensions generally

provide more feature capability and ease of setup, whereas the BACnet alarms provide better
interoperability with other BACnet systems.
Users can also view and take action on alarms that occur in the Metasys system with the Alarm
Manager and the Alarm Monitor in the Metasys UI. The Alarm Manager and Alarm Monitor display
all alarms pending acknowledgment and discarding. Users can access the Alarm Manager when
they are logged in to the Metasys UI, and they can access the Alarm Monitor when they are not
logged in to the Metasys UI. Users can access both the Alarm Manager and the Alarm Monitor
on computer and tablet platforms. To manage alarms on phone platforms, users can access the
Metasys UI Alarms list. The Alarms list displays alarms that have occurred for points mapped and
unmapped to Metasys UI equipment. You can see the top 100 alarms in the Alarms list. The listed
alarms include the latest occurrences, and alarms that were acknowledged, as indicated by a green
tick mark.
The Equipment Activity widget in the Metasys UI also displays alarms and user changes made
during a time range of up to one year within the last five years for a selected piece of equipment.
Note: An event is a notification of a status change in the Metasys system. An alarm occurs
when a value defined in an engine goes outside of a user-defined range, changes to a user-
defined contact condition, or fails to respond to a command within a user-specified time.
When an alarm occurs, an event is generated. Events can be generated by any Metasys
platform. For example, if the NAE detects that a network node is offline, it can generate an
event. If an error occurs in the server platform, an event can also be generated. Once an event
is generated, it is stored in an Event Repository file located on the device that generated the
event. Users can retrieve and examine events stored in the Event Repository.
Encrypted Communication
Beginning at Release 8.1, all Metasys Server based devices (ADS, ADX, ODS, and NAE8500) 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 Wizard (LIT-12012162)
or ODS Installation and Upgrade Instructions Wizard (LIT-12011945). The steps for installing trusted
certificates on network engines are described in Metasys SCT Help (LIT-12011964).
When deploying certificates, keep the following in mind:
• The steps for setting up trusted certificates can be complicated. Ask the customer's IT
department for assistance.
• Secure and encrypted communication has the greatest importance between the Site Director and
a client logging in to the Site Director from the Metasys SMP. In many cases, the most practical
choice is to install a trusted certificate at the Site Director (ADS, ADX, or ODS) and a self-signed
certificates on each network engine that is upgraded to Release 8.1 or later. If the Site Director is
a network engine, you might want to install a trusted certificate on just the Site Director NAE and
self-signed certificates on its child devices.

• The name of the network engine within the SCT archive and the subject common name (or
hostname associated with certificate) within the certificate must match exactly for a certificate to
be imported and bound to IIS.
• Some certificate authorities may require the subject common name (or hostname associated
with certificate) within the certificate to include a domain name. If you are implementing
certificate management on an existing Metasys system, adding a trusted certificate may require
you to add a domain name to the original host name of a server or engine. This action requires
you to rename all data in the Metasys historical databases. This renaming operation requires
intensive database operations that significantly prolong a system upgrade. Therefore, be sure to
allocate extra time if you are renaming historical data as part of an upgrade to Metasys Release
10.0.
Destination Delivery Agents (DDA)

DDAs are the method used for routing and delivering Metasys alarm extension event messages
to destinations such as pagers, printers, email, and Network Management systems. The Metasys
system uses an email DDA, Pager 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.
RADIUS Server Accounts

Similar to the existing Active Directory service support, you can control access to the Metasys
system with a Remote Authentication Dial-In User Service (RADIUS) server. When you select
RADIUS on the Metasys system log on screen, the RADIUS server authenticates your identity as an
authorized user of the system.
RADIUS implementation in the Metasys system adheres to the following Internet RFCs:
• RFC 2865 - Remote Authentication Dial In User Service (RADIUS)

• RFC 2548 - Microsoft Vendor-specific RADIUS Attributes
• RFC 2759 - Microsoft PPP CHAP Extensions, Version 2
RADIUS implementation:
• does not import authorization; all system users, both local and non-local, are authorized through
user configuration in the Metasys security database.
• is transparent at login time. Users do not independently select a domain. The user ID must
match what is expected to be authenticated by the RADIUS server, with or without the @domain,
as defined by the local RADIUS implementation.
• does not include the storage of RADIUS user passwords in the Metasys security database.
Because Metasys performs no local authentication of non-local users, all password functions are
unavailable or silently non-functional with RADIUS user accounts.
• requires a Metasys administrator to configure RADIUS users
When a user provides a non-local user name to the Metasys system for login, the controller passes
the user credentials to the configured RADIUS server for authentication. If the credentials are valid,
the RADIUS server confirms access and authorizes the user to log in as specified in the Metasys
security database.
Encrypted Email
Metasys software features an email encryption capability that encrypts user names and passwords
as they are entered into the SMP UI. Embedded and server machines can thereby send emails
to email servers over a secure channel (secure socket layer [SSL]). The entire email payload
is encrypted, and allows Metasys software to communicate to email servers that require SSL
connections.
Users can configure email encryption with no authentication required, including SMTP
authentication, and POP-Before-SMTP authentication.
Scheduling
Scheduling provides a graphical user interface that illustrates when events are scheduled to occur.
Scheduling automates routine functions, such as transferring a room from occupied mode to
unoccupied mode for heating and cooling needs, and energy optimization. Each schedule consists
of a weekly schedule, an exception schedule, a list of items in the schedule, and an effective period.
Exception schedules take precedence over the daily schedule only for their configured length
and then return the schedule to its typical weekly schedule. Exceptions can include references to
Calendars that can, for example, reflect a holiday schedule for the entire facility or show selected
tenant spaces in the building. Another view within the schedule, called Today’s Schedule, shows the
current day’s schedule including how each exception schedule affects the current day’s schedule.
A multi-time zone feature is available that allows the definition of schedules across different time
zone. You can program schedules based on device time zones instead of converting the time to
correlate to the Site Director's time zone.
Historical Data Management (Trend)

Users can collect, store, and view historical samples of object data with the Metasys Historical Data
Management capability. With the information generated by this feature, you can manage energy
usage, prove compliance to standards, and diagnose problems in your facility.
Each engine has a local buffer where it stores trend samples. Users can configure the size of this
buffer, in a number of samples. If a server exists on the site, you can send the trend samples to its
database. This database supports backup, restore, and archival of data to long-term storage. You
can display trend data as a graph or table of values on the SMP UI. The Trend widget in the Metasys
UI displays more recent historical data as a graph. Users can also copy trend data to the browser

computer’s clipboard, and thereby transfer the data to spreadsheets, databases, and Microsoft
Word documents.
The SMP UI makes it easier to detect system-level performance by displaying multiple trends on
a single graph or table. You can either predefine multiple trends in a trend study or dynamically
select various point trends to display on a single graph using the Trend Viewer or the Trend widget
in the Metasys UI. The Site Management Portal UI also offers information on the rate of events, rate
of samples, and number of samples that are lost. Refer to the Metasys SMP Help (LIT-1201793).
System Security
User accounts control user access to the Metasys system. An account defines which portions of the
Metasys data a user can access (for example, all HVAC data or all lighting data from a particular
area of the building) and which functions the user can perform on that data, from view-only
access to configuring new databases. The Metasys system provides the ability to divide the data
into 25 unique categories, including HVAC, fire, and security; and has 10 different levels of user
functionality.
Users can further limit user accounts to operate only at specified times on specified days of the
week. The System Administrator creates all account settings.
Each account can also have associated preferences, such as which graphic or trend to display when
a user logs in to the SMP UI, or which User Views appear in the Navigation Tree.
Basic Access is a feature through which users can create limited operator access to SMP features
based on the user’s assigned permissions in the Security Administrator. Users can avail of Basic
Access on all the Metasys system engines and servers.
The SMP and Metasys UI can use Microsoft Active Directory® accounts or RADIUS accounts.
Note: MVE sites do not support Basic Access and Tenant Access users.
Users can assign user access permissions to specific spaces and the equipment serving those
spaces with the Metasys UI User Authorization. Users can thereby segment user access by physical
space within the building or campus.
In addition to making it easier for system administrators to manage Metasys account access,
Microsoft Active Directory® also provides the ability to use Single Sign-On to access the Metasys
system, through the Site Management Portal UI, together with other supported applications on the
enterprise network.
The Audit Log records all user activities, and the System Administrator can thereby monitor user
actions.
User names and passwords are obscured at login for local and Active Directory accounts. After
login, user names are partially obscured on the SMP or SCT UI window (for example, JohnSmith
appears as Joh***).
The following table lists the password rules enforced by the Metasys system user's language locale
setting.

Table 9: 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)
French (fr_fr)
Hungarian (hu_hu)
Italian (it_it) • The password and the username cannot share the same three
Norwegian (nb_no) consecutive characters.
Dutch (nl_nl) • The password must meet three of the following conditions:
Polish (pl_pl)
Portuguese (Brazilian)
(pt_br) - Include at least one special character (-, ., @, #, !, ?, $, %)
Russian (ru_ru) - Include at least one uppercase character
Swedish (sv_se)
Turkish (tr_tr)
- Include at least one Unicode character that is categorized as
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)
Korean (ko_kr)
• 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 special character (-, ., @, #, !, ?, $, %)
- Include at least one uppercase character
- Include at least one Unicode character that is categorized as
an alphabetic character but is not uppercase or lowercase

Refer to the Account Policy Tab section in the Security Administrator System Technical Bulletin
(LIT-1201528) for further information about how passwords are used by the user account, the
account lockout policy and the inactive session policy.
Logic Connector Tool (LCT)

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

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

The Audit Trail feature records events generated either by user actions or system activity. Examples
of user actions include logging in to the Site Management Portal UI or issuing commands to a
point. Examples of system activity include device restart initialization settings or internal security
changes. An audit message consists of the information that describes a significant event on the
building automation system (BAS). For each significant event, a new audit message is generated
and appears in the Audit Viewer.
Once an event is sent to the Audit Trails subsystem, an audit message is generated and stored in an
Audit Repository file located on the server or engine that detected the condition.
Users can forward audit messages from the Local Audit Repository to a user-specified ADS Audit
Repository for permanent storage on a server (ADS/ADX), based on user-defined rules.
Users can view audit messages in the Audit Viewer of the SMP UI. Once a user logs in to the Site
Director, the user can view all audit messages from the server or any device that contains a Local
Audit Repository. When a user directly logs into a device not designated as the Site Director, the
user can only view audit messages in that device’s Local Audit Repository. Any audit messages
generated on a server are placed directly into the ADS/ADX Audit Repository.

Users can also view user changes made within the last seven days for a selected piece of
equipment in the Equipment Activity Widget of the Metasys UI. Users can also discard user changes
in this widget.
System Diagnostics and Serviceability

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

Metasys for Validated Environments (MVE), extended architecture is a feature designed for facilities
that require regulatory compliance for their environmental systems. The MVE feature operates
on an ADX, NAE55, NCE25, and NIE55, which are all supported as validated devices. MVE is not
supported on a BACnet ODS Workstation.
MVE is specifically designed to help customers address United States Food and Drug Administration
(USFDA) Title 21, Code of Federal Regulation (CFR) Part 11 compliance. MVE is also compliant with
other similar agencies around the world that deal with electronic records and electronic signature
requirements, such as Annex 11 of the European Union Good Manufacturing Practice (EU GMP)
regulations (European Medicines Agency [EMEA] 1998).
The ADX with MVE software provides secure data management and reporting capabilities, traceable
electronic records and signatures, and time-stamped audit trails for facilities subject to Part 11
compliance. It manages and protects the long-term storage of trend data, audit data, event/alarm
messages, annotations, and system configuration data. In addition, complex passwords and
message encryption secure the system from unauthorized access and data tampering.
Important: MVE is supported at Release 9.0 but not upgradable to Release 10.0.
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 designated operator or 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).
Reporting Capabilities
Metasys Export Utility Software
The Metasys Export Utility software provides facility managers with the ability to easily build custom
reports using historical data from the Metasys system. This data can be used to manage daily
building operations. The Metasys Export Utility software extracts historical trends, alarms, and audit
data from an engine or server. Users can collect data desired by the operator for analysis from the
system and store it in up to six different formats, including Microsoft Word® or Microsoft Excel®
files. In addition, the scheduling feature retrieves and saves data based upon user-configurable
time intervals.
The Metasys Export Utility provides the user with the ability to create runtime studies and discover
root cause analysis of system changes and mechanical equipment failures. Users can also collect
trended runtime data for use by a computerized maintenance management system (CMMS) to
schedule mechanical maintenance of HVAC systems.
Metasys Advanced Reporting System

The Metasys Advanced Reporting System is a standard capability of all ADXs and ODSs when using
supported SQL Server software, with SQL Server Reporting Services (SSRS) installed. The web-based
reporting interface provides standard report sets. Users can thereby review the alarm and trend
configuration of their site, run summary and detail reports to monitor alarm and event information,
view offline information, combine alarm and audit information in a single report, and provide
summary and detailed trend aggregations. The site’s All Items or User View navigation tree filters
the report information. Users can customize the date range and data type desired for each report.
Once a report is created in the user interface, users can export the data into common applications,
such as Microsoft Excel® spreadsheet or Adobe® PDF formats.
Note: ODS is supported at Release 9.0 but not upgradable to Release 10.0.
Energy Essentials
Energy Essentials is an optional software feature that can be added to the Metasys Advanced
Reporting System. It offers seven types of energy reports that provide a high-level view of
normalized energy use across your site, and presents your daily electrical demand graphically.
Metasys Advanced Reporting supports installation on a computer with SQL Server 2016 installed,
however; Energy Essentials does not support installation on a server using SQL Server 2016 or later.
Metasys Graphics Options

Metasys UI Graphics
Metasys UI allows Metasys system designers to efficiently create, edit, and manage graphics in
either Metasys UI or Metasys UI Offline. The Graphics Manager and Graphics Editor do not require
any additional software. System designers can immediately validate graphics created within the
Metasys UI. Included is a full library of symbols and templates that provide photo-realistic images of
equipment, systems, and floor plans as a starting point for system designers who do not have the
time or expertise to create graphics from scratch.

To ensure optimal performance of the graphics created in the Metasys UI, follow the
recommendations in the table below.
Table 10: Recommended Maximum Selections
Item or Element Recommendations Notes

Number of Elements 0–125 An element is any shape, symbol, or image
(Shapes, Symbols, or that is added to the graphic.
Images)
Number of Bound 0–200 We recommend that you have no more
Metasys Points than 200 bound Metasys points on a single
graphic unless you are using a Status
Summary element.
Number of Status 0–6 This limit allows for 50 bound Metasys points
Summaries per Status Summary with a recommended
maximum of six Status Summaries on a
graphic. The limit results in 300 points
whose statuses are summarized using
only five elements (not 300 elements). This
Status Summary exception contrasts the
bound Metasys point recommendation
of 200 maximum, because not all bound
values appear in the graphic.
Number of Images 0–5 An image is any image file that is added to
the Graphic Canvas.
Note: We recommend that images
have a maximum size of 1,600 pixels
(height) by 1,200 pixels (width) and
1 MB in file size. Exceeding the
recommended dimension size may
cause significant delays in load times.
Number of Animations 0–50 This number applies to animations that
are actively running at the same time (for
example, a supply fan and a return fan).
Graphics+
Graphics+ is a visualization software package designed for Metasys® building automation system
(BAS) operators to create interactive building data representations, empowering them to visualize,
analyze, and respond to problems faster. Graphics+ is made up of two components: the Graphic
Generation Tool (GGT) and the Graphics+ Viewer.
The Graphic Generation Tool helps designers to create compelling representations of their building
equipment and floor plans and bind them to Metasys data objects. You can save these graphics
directly to a supported Metasys Host, such as a Site Director or a SCT archive database.
The Graphics+ Viewer is integrated with the Metasys user interfaces (SMP and SCT), and users can
thereby show, command, or update in real time all the data-linked objects that were created in the
GGT.
Metasys UI and Metasys UI Offline supports viewing Graphics+ graphics. To view Graphics+ graphics
in the Metasys UI, associate your graphics to space or equipment objects using the SCT and then
download the ADS.

Note: The graphics need to be on either the ADS or the devices for the relationship to work
and display correctly.
To view graphics in the Metasys UI Offline, simply associate your graphics to space or equipment
objects and then log in to the Metasys UI Offline.
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.
Advanced Graphics Application Software

The Advanced Graphics Application is an enhanced version of the Standard Graphics package
that provides dynamic capabilities such as custom animation, color changing, and flashing for
the Metasys system. The package includes a dynamic example stencil library and is an add-on to
Microsoft Visio® software. With a more comprehensive representation of facility support systems,
building operators can easily monitor the health of the system on a more intuitive interface. You
can view advanced graphics in the Metasys system Site Management Portal UI.
Integrations
BACnet/IP Integration
BACnet/IP integration is possible with two Metasys field equipment controllers, namely the IP
FAC4911 controller and the IP VMA1930 controller. These controllers communicate on Ethernet
IP networks and support increased network performance, enabling faster access to data and
faster troubleshooting. Metasys BACnet/IP Field Controllers may be connected to your building
automation network in two ways. You can connect them as daisy-chained devices or as part of a
star type network, which is also called home run. Beginning at Release 10.0, you can also network
the IP FAC4911 and IP VMA1930 controllers, which are connected by Cisco® technology, in a ring
Ethernet topology, which provides network reliability by mitigating a single point of failure in the IP/
Ethernet network wiring. Most networks use combinations of these topologies. For details, refer to
the Metasys IP Networks for BACnet/IP Configuration Guide Technical Bulletin (LIT-12012458).
At Release 10.0, 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 some NAEs/NCEs/NIEs and field
controllers using 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 an NAE/NCE/NIE. The Sensor Actuator (SA) Bus consists of point interfaces and
networked sensors supervised by a field controller. To communicate with field controllers on a
remote MS/TP Bus, you need a BACnet/IP to BACnet MS/TP Router connected to the building's IP
network. The ODS Workstation is also compatible with the remote MS/TP bus. For details, refer to
the MS/TP Communications Bus Technical Bulletin (LIT-12011034).

N2 Field Bus
The N2 Field Bus is a local network that links controllers and point interfaces to some NAEs/NCEs/
NIEs. The N2 Bus uses a MS/TP protocol, in which the master device (the NAE/NCE/NIE) initiates the
communication with the N2 Bus devices.
N1 Integration (Release 9.0 or earlier)

The N1 integration is based on the NIE. A single NIE or a network of multiple NIE devices are
configured 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 MS/TP communication protocols used in the industry. It
is openly published and royalty-free, making it relatively easy to deploy an industrial network.
Modbus transmits raw bits or words without placing many restrictions on vendors. The NIEx9
supports both Modbus RTU (RS-485, RS-232) and Modbus TCP/IP connectivity.
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 an NIEx9 to an M-Bus network.
KNX
KNX Bus is used 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. A KNX IP Gateway is required to connect an NIEx9 to a KNX network.
C·CURE 9000 Access Control

A VND (Vendor) 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

Starting at Release 10.0, 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.
Metasys System Revision Compatibility Overview

This section describes high-level revision-to-revision compatibility scenarios for customer job sites
when you upgrade to Metasys Release 10.0. This section also contains some information about
previous release revision compatibility for existing sites that are at a previous release. This section
also describes revision-to-revision compatibility scenarios for the Graphics+ feature within Metasys
user interfaces.
General Compatibility Information for Customer Job Sites

SCT allows you to maintain Release 5.2, 6.x, 7.x, 8.x, 9.0, and 10.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 8.1, this included Release 6.5, 7.0, and 8.0.
The SCT no longer requires the same revision as the Site Director when integrated with the ADS/
ADX. If you install the ODS software, your SCT must be at Release 6.5 or later.
Note: ODS is supported at Release 9.0 but not upgradable to Release 10.0.
For sites installed with the Metasys UI, the Site Director server must be at Metasys Release 7.0. Sites
using the Rapid Archive Creation feature of SCT 11.0 or later to quickly configure their Metasys UI
require the Site Director server to be at Release 8.0 or later.
Starting at Release 4.1, MS-NxE55-0 Engines can no longer be upgraded beyond Release 4.0. Sites
with -0 NxE55s upgraded to Release 4.0 are tested to coexist with the latest revision Site Director.
It may not be possible to edit Graphics or Logic Connector tool (LCT) processes in an Engine at
Revision 2.2 or earlier from a Site Director at Revision 3.0 or later. This is because the Scalable
Vector Graphic (SVG) rendering program was changed after Release 2.2. As a workaround, log in to
the Engine directly to make these edits.
Compatibility Rules for CCT and Field Controller Revisions

All revision-to-revision upgrade combinations for FEC/CCT applications are tested in the Product
Development Test Labs.
Starting at CCT Release 10.1, CCT is used to configure, simulate, and commission FECs, Advanced
Application Field Equipment Controllers (FACs), VMA16s, and VMA1832s on an N2 Bus. CCT 10.1 can
open and commission any previous FEC application created with an earlier revision.
FEC revisions can be mixed and matched on any Engine with MS/TP Integration. This means that
Release 5.3 based FECs 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 FEC.

The CCT upgrade process works between major and minor revision levels (for example, 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 FEC Display was added at Release 3.0. To incorporate a display into an FEC installed at a release
prior to 3.0, you must:
• upgrade the .caf file to the current release
• open the display configuration application within CCT and select the desired points to display
• download main and boot code, then download the upgraded .caf file
Output Controller Module Upgrades

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

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

• Users must apply the Metasys system 5.2.12 patch to a Site Director server/device and SCT
computer running Release 5.2, to fully utilize all features within the Graphics+ Release 1.3.
• Graphics+ Release 1.3 is guaranteed to be backward compatible with graphics created using the
Graphics+ Release 1.2 and 1.1. Therefore, customers currently running Release 1.1 or Release 1.2
can upgrade to Release 1.3 without having to manually touch every existing customer graphic.
• Graphics+ Release 1.3 includes performance enhancements when displaying graphics in the Site
Management Portal (SMP) UI. For performance enhancements to take effect, the Site Director
must be at Metasys Release 6.5 or later. Most performance enhancements require no user action.
However, there may be user action required to reduce the size of large dimension images within
graphics that contain large dimension images (using the Library Panel Basic Symbols Image
element). Refer to the Image section of the Graphic Enterprise Library portion of the Graphic
Generation Tool Help (LIT-12011697).
• Metasys UI and Metasys UI Offline Release 2.0 supports viewing Graphics+ graphics. To view
Graphics+ graphics in the Metasys UI, associate your graphics to space or equipment objects
using the SCT, then download the ADS.
Note: The graphics need to be on either the ADS or the devices for the relationship to work
and display correctly.
To view graphics in the Metasys UI Offline, simply associate your graphics to space or equipment
objects, then log in to theMetasys UI Offline.
For more information on Upgrade Considerations at Graphics+ Release 1.3, refer to the Upgrade
Considerations section of the Graphic Generation Tool Installation Instructions (LIT-12011685).
FEC, FAC Wireless Integrations

The Wireless ZFR181x Series System was introduced at Metasys Release 4.0.
• Wireless coordinators need to be at an equal or higher revision level than the controllers
associated with it.
• Within a wireless mesh, a mix of revisions of wireless pairs is allowed.

• Each wireless controller and associated wireless router need to be at the same release. CCT
automatically syncs release revisions between a controller and its associated router.
• Release 4.0 controllers are not compatible with 4.1 or later wireless routers and need to be
updated before connecting the wireless router.
WNC1800/ZFR182x Pro Series Wireless Field Bus System

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

Multiple NAE System Configuration with One NAE Designated as the Site
Director
To extend the capabilities of your system, add one or more additional NAEs. In Figure 3, one NAE
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 only other NAE45-Lite devices. Additionally, the
NAE45-Lite requires an ADS-Lite-A Site Director, and both of these are available only in
specific markets.
Figure 3: Multiple NAE System Configuration

with One NAE Designated as the Site Director

ADS/ADX Site Director with Multiple NAEs System Configuration
Sites that require more than four simultaneous users must add an ADS or ADX (Figure 4). If a large
number of graphics are required to navigate through a site, the addition of the ADS/ADX allows
access to a disk drive or network drive for graphic file storage. The ADS/ADX provides permanent
storage of collected trend data samples, event messages, and audit trail messages routed from the
NAE/NCE devices.
Note: Cloud-Based Applications are not available for all sites.
Figure 4: Multiple NAE System Configuration with ADS or ADX, and Metasys UI
ADS/ADX Site Director and Secure NAE-S with Unencrypted NAEs

Figure 5 shows a network that features a secure NAE-S network engine with other unencrypted NAE
engines reporting to an ADS/ADX Site Director. For more details, refer to the NAE-S Commissioning
Guide (LIT-12012269).

Figure 5: Example Network with Encrypted and Unencrypted NAEs
ADX Split Configuration

The ADX split configuration provides the ADX software/user interface on one computer (the web/
application server computer) and the alarm, audit, annotations, and historical trend data on
another computer with Microsoft SQL Server software (the database server computer). See Figure
6.

Figure 6: ADX Split Configuration
Figure 7 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 7: 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 8: Network Examples with Dual Network Cards
Large ADX Site Configuration

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

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

Figure 9: ODS Site Manager Workstation Configuration
Figure 10: ODS BACnet Workstation Configuration

Figure 11: ODS Combined Workstation Configuration
N1 Integration System Configuration

At Release 9.0 or earlier, the NIE (NIE55 and NIE85) provides a means of migrating your existing
Metasys N1 network to the Metasys system. For more details about NIEs, refer to the Release 9.0
version of the Metasys System Configuration Guide (LIT-12011832).
Important: Support for N1 integration ends at Release 9.0.
Figure 12: N1 Integration with NIE85 (Release 9.0 or earlier)
BACnet/IP Network System Configuration

BACnet/IP devices are connected directly to the IP Ethernet network. The NAE communicates with
the devices using the BACnet protocol and presents the BACnet data to the system in the same
way as the other data in the Metasys system. Figure 13 shows the NAE35 supervisory controller
integrated into the Metasys network. Other BACnet/IP devices are integrated in the same way.

Figure 13: BACnet/IP Network Integration System Configuration
The NAE85 allows integration of larger BACnet integration projects.
Figure 14: NAE85 BACnet Integration

Third-Party Network Integration
The Network Engines offer seamless integration of Modbus, M-Bus, KNX, or other third-party
network to the Metasys system. Figure 15 shows the NAE45 and NCE25 controllers integrating third-
party devices. A KNX IP Gateway is also shown.
Figure 15: Third-Party Network Integration
Wireless Metasys System Configurations

Figure 16 shows various wireless Metasys system offerings, and how they coexist within the Metasys
system.

Figure 16: 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 17: 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.
Site Director Limitations and Recommendations

Table 11 describes performance guidelines and limitations of the Metasys system Site Directors.
Particular release numbers are also provided.
Note: Upgrade the Site Director to Metasys Release 10.0 to take advantage of encrypted
communications, we recommend that you upgrade the network engines to the newer release
as well. Network engines at Release 5.2 or later continue to work well with Release 10.0, but to
ensure best performance, upgrade engines to newer versions as soon as is practical.
Table 11: Site Director Limitations and Recommendations
Maximum Type of Site Director
Allowed NAE35 NAE45 NAE55 NAE85 NCE25 ADS/ODS ADS-Lite-E ADS-Lite-A ADX ODS Server
(9.0.7) (9.0.7) (10.0) (10.0) (9.0.7) Desktop (10.0) (10.0)
1
(10.0)
1
Total engines
2 3 4 5 6 6
(including self for 3 3 5 5 1 1 to 14 5 4 1 to 1,000 1 to 100
NxEs)
Simultaneous 10/25/
SMP users 2 2 4 10 2 5 5 5 50/100 5
7
Dynamic values
100 100 100 100 100 100 100 100 100 100
per graphics
Results displayed
in a global 500 500 500 500 500 2,000 2,000 2,000 2,000 2,000
search

Table 11: Site Director Limitations and Recommendations
Maximum Type of Site Director
Allowed NAE35 NAE45 NAE55 NAE85 NCE25 ADS/ODS ADS-Lite-E ADS-Lite-A ADX ODS Server
(9.0.7) (9.0.7) (10.0) (10.0) (9.0.7) Desktop (10.0) (10.0)
1
(10.0)
1
Languages 1 18 18 18 18 18
Objects in entire
3 million/ 750k (for ADX Site Director Only)
system
Objects in device
8 2,500 2,500 5,000 25,000 2,500 Limited by SQL Server storage capacity
Objects within a
300 300 700 700 300 700 700 700 700 700
single folder
Characters in
the name of an 400
object
Characters in the
description of an 64
object
Nesting levels for
7
object creation
Extensions per
10
object
Sets for third-
party BACnet 1,000
states text
Characters for
a third-party
60
BACnet states
text
Members for a
multi-value third-
500
party BACnet
states text
Non-
Simultaneous Limited only by memory capacity
SMP users
SMP user views Limited only by memory capacity
Simultaneous
browsers per 2 (Mix of online, SCT, and Simulation)
client computer
DLLR load 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.
extension 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 cannot host servers.

2 An NCE25 can only act as Site Director for itself.
3 Varies with concurrent connection.
4 Supports up to five of the following: NAE35, NAE45, NCE25, NIE29, NIE39, and NIE49.
5 Supports up to 3 NAE-Lite units plus up to 1 NIE29, NIE39, and NIE49.
6 Depends on computer hardware. Both a unified and split ADX support a maximum of 1,000 engines.
7 Depends on version of ADX or ODS.
8 Includes all points, extensions, graphics (background image), trend study, and other objects, such as schedules and
interlocks. For the NxE85/NIE89, 25,000 object limit includes 15,000 object base license plus 10,000 object add-on
license.

Table 12: Maximum Number of Users Supported on ADS/ADX/ODS Site Director
Computer Supported Platform Site Metasys UI Users

Desktop Server Management (Up To)
Portal (SMP)
Users (Up To)
ADS 5 Users Yes - 5 5
ADX 10 Users - Yes 10 10
ADX 100 Users
1
- Yes 100 50
ODS 5-User; Yes Yes 5 Not Supported

25,000 Objects
1 Metasys for Validated Environments does not support the 100 user ADX.
Table 13: Maximum Number of Network Engines Supported Based on ADS/ADX (Unified and
Split Configuration) and Server Size
Site Director 1 to 14 1 to 50 Engines 1 to 250 Engines 1 to 1,000 Engines

with Maximum Engines
Users
ADS 5 Users ADS
ADX 10 Users Small/Medium ADX Large ADX Extra Large ADX
ADX 25 Users Large ADX
ADX 50 Users Extra Large ADX Extra Large ADX
ADX 100 Users
For ADS/ADX computer hardware requirements, refer to the Technical Specifications section of
the Application and Data Server (ADS) and Extended Application and Data Server (ADX) Product Bulletin
(LIT-1201525):
• For Unified ADS refer to Application and Data Server (ADS) System Requirements (5 Users) table.
• For Small, Medium, or Large Unified ADX refer to Extended Application and Data Server System
Requirements (Unified ADX Systems, 10 or 25 Users) table.
• For Small/Medium/Large Split ADX refer to Extended Application and Data Server System
Requirements (Split ADX Systems, 10 or 25 Users) table.
• For Extra Large Unified ADX refer to Extended Application and Data Server System
Requirements (Unified ADX Systems, 50 or 100 Users) table.
• For Extra Large Split ADX refer to Extended Application and Data Server System Requirements
(Split ADX System, 50 or 100 Users) table.
Network Engine Hardware Limitations

The following table describes limitations of the Metasys system network engines.

Table 14: Network Engine Hardware Limitations
Maximum allowed NCE25 NAE35 NAE45 NAE45- NAE55 NAE85

Lite 1
ODS
Local Field Buses (FBs) 1 1 1 1 2 0
Remote Field Buses 0 4 4 0 6 or 7 16
(RFBs)
Total Field Buses (Local 1 (1 FB + 0 5 (1 FB + 4 5 (1 FB + 4 1 (1 FB + 0 8 (2 FB + 16 RFB only
and Remote Field Buses) RFB) RFB) RFB) RFB) 6 RFB or
1 FB + 7
RFB)
MS/TP devices on FC Per trunk device limits if all devices are Metasys family devices, such as
Bus
2
CGMs, CVMs, FACs, FECs, VMAs, IOMs, and TEC3600s:
Note: N2 devices 32 50 100 100 100 N/A
follow the same Per trunk device limits if one device is a non-Metasys family device,
rules as MS/ such as a Facility Explorer® device, TEC2000, or third-party device:
TP devices, but
32 32 64 64 64 N/A
performance varies
based on controller
mix (N2Open/
Sys91/VMA).
Remote MS/TP devices N/A 16 or 32 16 or 32 N/A 16 or 32 16 or 32
3
on remote field bus
Mapped N2 points per 2,500 2,500 2,500 N/A 2,500 N/A
4
trunk
LonWorks devices
5
32 64 127 N/A 255 N/A
Note: The LonWorks integration is only supported on NAE35s,
NAE45s, and NCE25s with the Metasys Release 9.0 software or
earlier. The Release 9.0.7 patch update is not supported for these
LonWorks models; they remain at Release 9.0. However, the
LonWorks integration is supported for NAE55s at Release 10.0.
LonWorks network 1,500 1,500 1,500 N/A 2,000 N/A
variables
Johnson Controls ,,
6 7 8 ,,
6 7 8 ,,
6 7 8 ,,
6 7 8 ,
6 7 200
7
50 50 50 50 200
BACnet/IP devices and
third-party BACnet/IP
devices
Objects 2,500 2,500 2,500 2,500 5,000 10,000
(default)
25,000
(upgrade)
Time on battery backup 1,024 seconds N/A
1 ODS is not supported at Release 10.0.

2 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).

3 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.
4 Performance varies based on the point mix (N2 Open/Sys91/VMA). Recommend maximum for best performance is
1,000 points.
5 Single sub-net LonWorks network; does not support routers; supports physical repeaters
6 Depends on the number of objects each BACnet device supports.
7 Johnson Controls IP controllers only work with NAEs (and site directors) at Release 9.0 or later.
8 Some sites may require manual mapping based on system architecture. They may also require system adjustments,
such as BACnet communication adjustments, or firewall off.
Alarm and Trending Performance Guidelines

Table 15: Alarm and Trending Performance Guidelines
Description NCE25/ NAE55 NAE85 ADS ADX Comments
NAE35/ ODS
1
ODS
1
NAE45/ (Desktop) (Server)

Average 100 100 100 200 1,000 This number applies to alarms/
maximum events that originate from
number of devices at Release 5.2 or later.
alarms/events
per hour
Maximum 2,400 2,400 2,400 5,000 48,000 Within a 24-hour period. This
number of number applies to alarms/events
alarms/events that originate from devices at
per day Release 5.2 or later. Supports
one daily burst of 25k alarms/
events in one hour.
Maximum 500 1,000 1,000 Limited by N/A
number of SQL Server
stored alarms/ storage
events capacity
Average 1,500 1,500 1,500 22,500 100,000 This number applies to trend
maximum samples that originate from
number of trend devices at Release 5.0 or later.
samples per The ADX supports one daily
hour burst of 300k trends in one hour.
Maximum 36,000 36,000 36,000 540,000 2,400,000 Within a 24-hour period. This
number of trend number applies to alarms/events
samples per day originating from devices at
Release 5.0 or later.
Maximum Limited by Limited by 8,000,000 Limited N/A
number of memory memory usage only
stored trend usage by SQL
samples storage
capacity
1 ODS is not supported at Release 10.0.
Notes:
• Alarms and trends from FACs connected to any of these contribute to the overall totals.
• ODS is not supported at Release 10.0.

MS/TP Performance Guidelines
Table 16: MS/TP Performance Guidelines
Performance Rating COV Rate Token Loop Time

Low > 500 messages per minute > 3,000 ms
Medium Between 400 and 500 Between 2,000 and 3,000 ms
messages per minute
High < 400 messages per minute < 2,000 ms
SCT Limitations
Table 17: 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 Express 2014 or
Microsoft SQL Server Express
2012 SP2
No Limit Using supported Microsoft SQL
Server Software
FAC Integration Considerations

The local FAC trend and alarm and event setup strategy should focus on needs during a stand-
alone commissioning session using CCT. The integration of an FAC's trends, alarms, and events is
governed by the NxE guidelines for trend and alarm/event integrations.
The recommended limit threshold for trend samples for an NxE is 1,500 samples per hour. The total
number of trend samples forwarded from all FACs integrated with an NxE should not exceed this
limit during the setup of the local FAC trends.
The recommended limit threshold for alarm and event samples for an NxE is 100 events per hour.
The alarms that are set up in all FACs for use as BACnet Alarm extensions in the NxE should be
limited to only the points that normally are created as extensions in the NxEs. For consistency, the
use of BACnet Alarm extensions instead of Metasys Alarm extensions should also be considered
when deciding whether the FAC's BACnet Alarms should be enabled at the NxE.
In the following examples, we show acceptable limits with the following setups:
• 5 FACs with 6 alarms per hour plus 1 NAE with 30 alarms per hour (Table 18)
• 5 FACs with 200 trend samples per hour plus 1 NAE with 500 trend samples per hour (Table 19)
• 5 FACs with 10 COVs per minute plus 35 FECs with 10 COVs per minute (Table 20)
Table 18: Example 1
Setup Alarms per Hour

5 FAC with 6 alarms/hour each 30 alarms per hour
1 NAE 30 alarms per hour
Total 60 alarms per hour

Table 19: Example 2
Setup Trend Samples per Hour

5 FAC with 200 trend samples per hour each 1,000 trend samples per hour
1 NAE 500 trend sample per hour
Total 1,500 trend samples per hour
Table 20: Example 3
Setup COVs per Minute

5 FACs with 10 COVs/minute 50 COVs per minute
35 FECs with 10 COVs/minute 350 COVs per minute
Total 400 COVs per minute
For trend creations in the FAC, 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 NxE integration. The trends created in the FAC do not have to be
discovered and used by the NxEs; separate trends extensions can still be added at the NxE for any
points that have FAC based trends created.
For alarm enables in the FAC, the use of the FAC's local event viewer should be taken into
consideration to provide a more intuitive troubleshooting interface during a CCT commissioning
session. The FAC holds the 100 most recent alarms/events in its local memory.
Transfer limitations
Bluetooth and ZigBee are not supported for Transfer to Device (Download) for controllers using
firmware 7.0 or later. 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. 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 21: Client Computer Requirements for Site Management Portal UI, SCT, Metasys UI, and
Metasys UI Offline
Site Management Portal UI Metasys UI

System Configuration Tool Metasys UI Offline
(SCT)
System Configuration Tool Pro
(SCT Pro)
Recommended Intel® Core™ i5 Processor Intel® Core™ i5 Processor
Processor
1
Recommended 8 GB (4 GB minimum) 8 GB (1 GB minimum)

Random Access Note: If you use graphics intensively, you may experience better
Memory (RAM) computer performance with additional RAM.
Hard Disk Capacity 40 GB hard disk (minimum) 40 GB hard disk (minimum)
Supported Operating Windows® 10 Pro and Enterprise Windows® 10 Pro and Enterprise
System Editions with Creators Update Editions with Creators Update (version
(version 1709) (64-bit) 1709) (64-bit)
Windows® 8.1 Pro and Windows® 8.1 Pro and Enterprise
Enterprise Editions with Update Editions with Update 1 (64-bit)
1 (64-bit) Windows® 7 Professional, Enterprise,
Windows® 7 Professional, and Ultimate Editions with SP1 (64-bit)
Enterprise, and Ultimate Editions Apple® macOS® 10.12 Sierra
with SP1 (64-bit) Apple® OS X® 10.11 El Capitan
Apple® macOS® 10.12 Sierra Apple® OS X® 10.13 High Sierra
Apple® OS X® 10.11 El Capitan
Apple® OS X® 10.13 High Sierra
Supported Web Windows® Internet Explorer® Windows® Internet Explorer®
Browsers 11.0.9600.18816 Update version 11.0.9600.18816 Update version
2 4
11.0.47 or later 11.0.47 or later
Apple® Safari® 11 or later

3
Microsoft® Edge® version 41 or later
5
Google® Chrome™ version 61 or later
6

Metasys UI Offline

(SCT)
(SCT Pro)
Supported Mobile N/A Android™ 5.1 or later
Phone Operating
iOS 10.0 or later
Systems
Supported Tablet N/A Android 5.1 or later
Operating Systems
iOS 10.0 or later
Network Ethernet network interface card Ethernet network interface card
Communication 10/100/1000 Mbps 10/100/1000 Mbps
Follow these guidelines and

recommendations:
• For optimal performance, use a

wired connection for computers
browsing to the Metasys UI.
• Alternatively, for mobile phones and
tablets, you can use a wireless IEEE
802.11 connection on a 4G network.
Browsing to the Metasys UI over
a 3G communications network is
possible, but it is not recommended
or supported.
• High latency (also called lag or wait
time) can cause the Metasys UI to
disconnect from the ADS or ADX.
• To avoid high latency, we
recommend a network with 20 mpbs
upload speed.
• Signal strength impacts the overall
performance of the Metasys UI. For
the best results, ensure you have
a strong signal for your wireless
connection.

Metasys UI Offline

(SCT)
(SCT Pro)
Monitor 1024 x 768 or higher resolution 1024 x 768 or higher resolution and 16-
and 16-bit or higher color depth bit or 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 Internet Explorer 11, select the Use Microsoft compatibility lists option, found under Tools > Compatibility View
Settings, to ensure that websites appear and function correctly.
3 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.
4 The Metasys UI does not support Internet Explorer 11 on Windows 10 operating systems. In Internet Explorer 11,
select the Use Microsoft compatibility lists option, found under Tools > Compatibility View Settings, to ensure that
websites appear and function correctly.Metasys UI does not support InPrivate Browsing. To exit InPrivate Browsing,
close the browser window and open a new browser window.
5 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.
6 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.
Application and Data Server (ADS) System Requirements

Table 22: Application and Data Server (ADS) System Requirements (5 Users)
Recommended Computer Intel i7 processor latest version with at least four cores or
Platform
1
better
2
2 x 500 GB hard disk (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: 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 [for 64-bit operating systems],
Small Form Factor [SFF] if required)

Required Minimum Memory

3
16 GB RAM
Supported Operating Systems

4
Windows® 10 Pro and Enterprise Editions with Creators
and Database Software Update (version 1709 or later) (64-bit)
Supports:
• SQL Server® 2016 Express with SP1 (64-bit)
Note: SQL Server 2012 with SP3 is not an automatic
Windows update. For more information, refer to
https://support.microsoft.com/en-us/kb/2979597.
Windows® 8.1 Pro and Enterprise Editions with Update 1 (64-
bit)
Supports:
https://support.microsoft.com/en-us/kb/2979597.
Windows® 7 Professional, Enterprise, and Ultimate Editions
with SP1 (64-bit)
Supports:
https://support.microsoft.com/en-us/help/3072779/
sql-server-2012-service-pack-3-release-information.
Supported Operating Systems for Windows® 10 Pro and Enterprise Editions with Creators
Metasys Site Management Portal Update (version 1709 or later) (64-bit)
Client Computer Windows® 8.1 Pro and Enterprise Editions with Update 1 (64-
bit)
with SP1 (64-bit)
with SP1 (64-bit)
Apple® macOS® 10.13 High Sierra
Apple® macOS® 10.12 Sierra

Supported Web Browser Windows® Internet Explorer® 11.0.9600.18816 Update

Software for Metasys Site version 11.0.47 or later
Management Portal Client
Note: In Internet Explorer 11, select the Use Microsoft
Computers
compatibility lists option, found under Tools >
Compatibility View Settings, to ensure that websites
appear and function correctly.

Notes:
• 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 Windows® Internet Explorer® 11.0.9600.18816 Update

Software for Metasys UI Client version 11.0.47 or later
Devices Notes:
• The Metasys UI does not support Internet Explorer 11

on Windows 10 operating systems.
• In Internet Explorer 11, select the Use Microsoft
• Metasys UI does not support InPrivate Browsing. To
exit InPrivate Browsing, close the browser window
and open a new browser window.

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

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

Supported User Interfaces Site Management Portal (SMP)
Metasys UI
Additional Software Included CCT software
with the ADS (one license per
SCT software
ADS license)
Export Utility software
Additional Software Included Launcher software, Network Engine images, Summary
with the ADS Software Download Definition Examples, Microsoft .NET Framework (multiple
versions), SQL Server Management Studio, Metasys Database
Manager, Toggletunnel, SNMP Management Information
Base example files (MIBs), Report Viewer 2010 and Report
Viewer 2012.
Optional Hardware Any network or local printer supported by the qualified
Windows operating system
Optional Software Graphic Generation Tool
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)
Table 23: Extended Application and Data Server System Requirements (Unified ADX Systems,
10 or 25 Users)
Recommended Server 2.4 GHz Intel Xeon® 6 core single processor or better
1
Platform 2
2 x 600 GB hard disk (RAID 1) with 40 GB free space after installation
2
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.
Required Minimum 16 to 32 GB RAM
3
Memory

10 or 25 Users)
Supported Operating Windows® Server® 2016 (64-bit)

4
Systems and Database Supports:
Software
• SQL Server® 2016 with SP1 (64-bit)
Windows update. For more information, refer to https://
support.microsoft.com/en-us/help/3072779/sql-server-2012-
service-pack-3-release-information.
Windows® Server® 2012 R2 with Update 1 (64-bit)
Supports:
Windows® Server® 2012 (64-bit)
Supports:
Supported Operating Windows® 10 Pro and Enterprise Editions with Creators Update
Systems for Metasys (version 1709 or later) (64-bit)
Site Management Portal Windows® 8.1 Pro and Enterprise Editions with Update 1 (64-bit)
Client Computer Windows® 7 Professional, Enterprise, and Ultimate Editions with SP1
(64-bit)
Windows® 7 Professional, Enterprise, and Ultimate Editions with SP1
(64-bit)

10 or 25 Users)
Supported Web Browser Windows® Internet Explorer® 11.0.9600.18816 Update version

Software for Metasys 11.0.47 or later
Site Management Portal
Notes:
Client Computers
• In Internet Explorer 11, select the Use Microsoft compatibility
lists option, found under Tools > Compatibility View Settings, to
ensure that websites appear and function correctly.
• Metasys Advanced Reporting System and Energy Essentials support
Internet Explorer 11 on all computer platforms except on Windows
10. On Windows 10 computers, both Internet Explorer 11 and
Microsoft® Edge® version 41 or later.
Notes:
• In OS X, you cannot view Graphics+ graphics in the Site

Management Portal UI.
application. After you install the Launcher application, you
use the Launcher, not the web browser, to log in to the Site
Management Portal (SMP) UI.

Software for Metasys UI 11.0.47 or later
Client Devices Notes:
• The Metasys UI does not support Internet Explorer 11 on
Windows 10 operating systems.
compatibility lists option, found under Tools > Compatibility
View Settings, to ensure that websites appear and function
correctly.
• Metasys UI does not support InPrivate Browsing. To exit
InPrivate Browsing, close the browser window and open a new
browser window.

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.

10 or 25 Users)
Supported Virtual Microsoft Hyper-V™

Environments
VMware®
Supported User Site Management Portal (SMP)
Interfaces
Metasys UI
Additional Software CCT software Microsoft SQL Server 2012
Included with the ADX software with SP4
5
5
Export Utility software SCT software
Metasys Database Manager Microsoft .NET Framework Version
software 4.6.1
Launcher software
Note: The Metasys Advanced Reporting System requires an ADX.
The SCT computer must be online and accessible to the ADX at
all times.
Optional Hardware Any network or local printer supported by the qualified Windows
operating system
Optional Software Energy Essentials
Graphic Generation Tool
2 For best performance, use 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 16 GB RAM has much greater performance
than an ADX with only 4 GB RAM.
5 SQL Server software is only included with the MS-ADX10SQL product.
For SQL Server software, you must purchase SQL Server software licenses per the guidelines listed
here: SQL Server 2016, SQL Server 2014, and SQL Server 2012.

(Split 10 or 25 User ADX)
Table 24: Extended Application and Data Server System Requirements (Split ADX Systems, 10
or 25 Users)
Recommended Server Web/Application Server

1
Platform 2.4 GHz Intel Xeon® 6 core single processor or better.
2
3
Notes:
• Metasys Advanced Reporting System and Energy Essentials
must reside on the ADX web/application server.
• Metasys UI must reside on the ADX web/application server.
Database Server
2.4 GHz Intel Xeon® 6 core single processor or better.

3
SCT Computer
In a split configuration, you cannot install SCT on either the ADX web/
application server computer or the ADX database server computer.
Refer to the System Configuration Tool Catalog Page (LIT-1900198) for
current SCT computer requirements.
Required Minimum 16 GB RAM (web/application server and database server for 10 or 25
Memory
4
user ADX)
5,6
Systems with Supports:
Supported Database • SQL Server® 2016 with SP1 (64-bit)
Software

or 25 Users)
Supports:
Supports:
(64-bit) Windows® 7 Professional, Enterprise, and Ultimate Editions
with SP1 (64-bit) Apple® macOS® 10.12 Sierra

or 25 Users)

Notes:
Client Computers
Notes:



correctly.
browser window.

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

private browsing, click or tap Private in the browser window.

or 25 Users)

Environments
VMware®
Interfaces
Metasys UI
Additional Software CCT software Microsoft SQL Server 2012
Included with the ADX software with SP4 (64-bit)
7
Export Utility software Microsoft .NET Framework Version

4.6.1
Metasys Database Manager SCT software
software
Launcher software
all times.
operating system.
2 For best performance, use SAS hard drives (not SATA hard drives) that use RAID controllers with write caching enabled.
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.

(Unified 50 or 100 User ADX)
50 or 100 Users)
Recommended Server Two processors: 2.4 GHz Intel Xeon® Dual Processors with a
Platform
1
minimum of 8 cores each or better
2
6 x 300 GB 15,000 RPM hard disk (RAID 5) with 50 GB free space after
2
installation of all prerequisite software and before installation of ADS
software. Configure RAID 5 with disk write-caching turned on.
RAID Controller-PERC H710 with 1 GB Cache

Note: ADX prerequisite software includes the Windows operating
system, SQL Server software, Windows .NET Framework, and any
other software or SPs required by your ADX configuration.
Required Minimum 32 GB RAM
Memory
3
Systems and Database Supports:
Software
Supports:
Supports:

50 or 100 Users)
(64-bit)
(64-bit)
Notes:
Client Computers
Notes:


50 or 100 Users)


correctly.
browser window.


Note:
Metasys UI does not support private browsing. To exit private
browsing, click or tap Private in the browser window.
Environments
VMware®
Interfaces
Metasys UI
Additional Software CCT software Microsoft SQL Server 2012 software
Included with the ADX with SP4
4
Export Utility software Microsoft .NET Framework Version

4.6.1
Metasys Database Manager SCT software
software
Launcher software
all times.
operating system.

50 or 100 Users)
For SQL Server software, you must purchase a SQL Server software licenses per the guidelines
listed here: SQL Server 2016, SQL Server 2014, and SQL Server 2012.

(Split 50 or 100 User ADX)
Table 26: Extended Application and Data Server System Requirements (Split ADX System, 50
or 100 Users)
Recommended Server Web/Application Server

Platform
1
Two processors: 2.4 GHz Intel Xeon® Dual Processors with a

2
6 x 300 GB 15,000 RPM hard disk (RAID 5) with 50 GB free
3
space after installation of all prerequisite software and before
installation of ADS software. Configure RAID 5 with disk write-
caching turned on.
RAID Controller-PERC H710 with 1 GB cache
Notes:
• Metasys Advanced Reporting System and Energy
Essentials must reside on the ADX web/application server.
• Metasys UI must reside on the ADX web/application
server.
Database Server
Two processors: 2.4 GHz Intel Xeon® Dual Processors with a

6 x 300 GB 15,000 RPM hard disk (RAID 5) with 50 GB free

3
space after installation of all prerequisite software and before
installation of ADS software. Configure RAID 5 with disk write-
caching turned on.
RAID Controller-PERC H710 with 512 NV Cache

or 100 Users)
SCT Computer
In a split configuration, you cannot install SCT on either the ADX

web/application server computer or the ADX database server
computer. Refer to the System Configuration Tool Catalog Page
(LIT-1900198) for current SCT computer requirements.
Required Minimum Memory
4
32 GB RAM
Supported Operating Systems Windows® Server® 2016 (64-bit)

5,6
and Database Software Supports:
https://support.microsoft.com/en-us/help/3072779/sql-
server-2012-service-pack-3-release-information.
Supports:
Supports:
Supported Operating Systems Windows® 10 Pro and Enterprise Editions with Creators Update
for Metasys Site Management (version 1709 or later) (64-bit)
Portal Client Computer Windows® 8.1 Pro and Enterprise Editions with Update 1 (64-bit)
Windows® 7 Professional, Enterprise, and Ultimate Editions with
SP1 (64-bit)
Windows® 7 Professional, Enterprise, and Ultimate Editions with
SP1 (64-bit)

or 100 Users)

Software for Metasys Site 11.0.47 or later
Management Portal Client
Notes:
Computers
correctly.
• Metasys Advanced Reporting System and Energy Essentials
support Internet Explorer 11 on all computer platforms except
on Windows 10. On Windows 10 computers, both Internet
Explorer 11 and Microsoft® Edge® version 41 or later.
Notes:

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.

or 100 Users)

Software for Metasys UI Client 11.0.47 or later
Devices Notes:

InPrivate Browsing, close the browser window and open a
new browser window.

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

exit private browsing, click or tap Private in the browser
window. Other web browsers, such as Mozilla® Firefox®,
are not officially supported by the UI. However, the Metasys
UI may appear and function appropriately in these web
browsers.
Environments
VMware®
Supported User Interfaces Site Management Portal (SMP)
Metasys UI
Additional Software Included CCT software Microsoft SQL Server 2012
with the ADX software with SP4
7
Export Utility software SCT software

Metasys Database Manager Microsoft .NET Framework
software Version 4.6.1
Launcher software
Note: The Metasys Advanced Reporting System requires an
ADX. The SCT computer must be online and accessible to
the ADX at all times.
operating system

or 100 Users)
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.
SCT Technical Specifications

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

Recommended Full Server Intel® Core™ 2 Duo E6700 or better (Intel Core 2 Duo
Platform Platform E4300 minimum)
20 GB minimum free hard disk space available. Use
a Solid State Drive (SSD) to significantly improve
performance compared to other types of hard disks.
16 GB RAM (4 GB RAM minimum)

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

Supported Full Server Windows Server 2016

Operating Systems Platforms
Supports Microsoft SQL Server 2016 with SP1 (64-bit),
and Database
Microsoft SQL Server 2014 with SP2 (64-bit), or SQL
Software
Server 2012 with SP4 (64-bit)
Windows Server 2012 R2 with Update 1

Windows Server 2012

Desktop Windows® 10 Professional or Enterprise (64-bit) with
Computer Creators Update (version 1709)
Platforms
Supports Microsoft SQL Server 2016 Express with SP1
(64-bit), Microsoft SQL Server 2014 Express with SP2 (64-
bit), or SQL Server 2012 Express with SP4 (64-bit)
Note: The Windows 10 Creators Update (version

1709) is required for any Windows 10 computer
that runs Metasys 10.0 software, including the ADS,
ADX, ODS, and any Metasys software application.
Verify this update before installing Metasys
10.0 software. If you are upgrading to Metasys
Release 10.0 and do not have this update, you
must uninstall the previous release of all Metasys
software, apply the Windows 10 Creators Update
(version 1709), then proceed with the Metasys 10.0
upgrade.
Windows 8.1 Pro and Windows 8.1 Enterprise Editions
with Update 1

Windows 7 Professional, Enterprise, and Ultimate
Editions with SP1 (64-bit)


Supported Web Windows® Internet Explorer® 11.0.9600.18816 Update version 11.0.47 or

Browser Software later, Microsoft® Edge® version 41 or later, Apple® Safari® 11 or later, and
for Metasys Client Google® Chrome™ version 61 or later.
Computers Note: In Internet Explorer 11, select the Use Microsoft compatibility
Other browsers, such as Mozilla® Firefox®, may also be used but are
not fully supported.
Note: Use the web browsers to download the Launcher application.

After you install the Launcher application, you can use the Launcher to
log in to the SCT UI. You can also use the web browsers to access the
Site Management Portal (SMP) UI, Metasys UI, Metasys UI Offline, and
SCT Pro sites. You can also add a bookmark to the Metasys UI, Metasys
UI Offline and SCT Pro sites.
Network Ethernet network interface card 10/100/1000 Mbps (100 Mbps network or
Communication better recommended)
for Metasys System
Configuration Tool
Client Computers
Optional Software Note: A license for the SCT 13.0 is not included with the ADX, ADS, or
Packaging ODS software. You must obtain a license for each installation of the SCT.
Metasys UI and Metasys UI Offline Technical Specifications

The following tables list the technical specifications for the Metasys UI and Metasys UI Offline. For
more information about the ADS/ADX technical specification, refer to the Application and Data
Server (ADS) and Extended Application and Data Server (ADX) Product Bulletin (LIT-1201525). For more
information about the ADS-Lite technical specifications, refer to the Metasys® Server Lite Installation
and Upgrade Instructions Wizard (LIT-12012258). For more information about the SCT technical
specifications, refer to the System Configuration Tool Catalog Page (LIT-1900198).
Table 28: Metasys UI and Metasys UI Offline Client Technical Specifications for Phones and
Tablets
Supported Mobile Phone Android 5.1 or later

Operating Systems
iOS® 10 or later
Supported Tablet Android 5.1 or later
Operating Systems
iOS 10 or later
Table 29: Metasys UI and Metasys UI Offline Client Technical Specifications for Computers
Supported Client Windows® 10 Pro and Windows 10 Enterprise Anniversary Update

Computer Operating (version 1607 or later) (64-bit)
Systems and Web
Web Browsers Supported:
Browser Combinations
• Microsoft® Edge
• Google® Chrome™ version 54

Table 29: Metasys UI and Metasys UI Offline Client Technical Specifications for Computers
Windows 8.1 Pro and Windows 8.1 Enterprise with Update 1 (64-bit)

• Windows® Internet Explorer® 11.0.9600.18449 Update version
11.0.35 or later
• Google Chrome version 54
Windows 7 Professional, Enterprise, and Ultimate Editions with
SP1 (64-bit)

• Windows Internet Explorer 11.0.9600.18449 Update version 11.0.35
or later
Windows 7 Professional, Enterprise, and Ultimate Editions with
SP1 (32-bit)

• Windows Internet Explorer 11.0.9600.18449 Update version 11.0.35
or later
Apple® OS X® 10.13 High Sierra

• Apple® Safari® 11 or later
Apple® OS X® 10.12 Sierra

• Apple Safari 11 or later

• Apple Safari 11 or later

Table 30: Metasys UI and Metasys UI Offline Client Technical Specifications for Web Browsers
Supported Web Google® Chrome™ version 61 or later

Browsers
Notes:
• For better performance, we recommend using Google Chrome as
your preferred web browser for the Metasys UI and the Metasys UI
Offline.
• The Metasys UI and the Metasys UI Offline 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, refer to
https://support.google.com/chrome/answer/95464?hl=en.
Windows® Internet Explorer® 11.0.9600.18449 Update version 11.0.35
or later, and Microsoft Edge
Notes:
• In Internet Explorer 11 to ensure that websites appear and function
correctly, select the Use Microsoft compatibility lists option, found
under Tools > Compatibility View Settings.
• The Metasys UI and the Metasys UI Offline does not support InPrivate
Browsing. To exit In Private Browsing, close the browser window and
open a new browser window.
Note: The Metasys UI and the Metasys UI Offline does not support
Private browsing. To exit Private browsing, click or tap Private in
the browser window.
General Web Browser Support Information:
Notes:
• Other web browsers, such as Mozilla® Firefox®, are not officially
supported by the Metasys UI and the Metasys UI Offline. However,
the Metasys UI and the Metasys UI Offline may appear and function
appropriately in other web browsers that are not officially supported.
• In supported web browsers on tablets and phones, Metasys UI and
Metasys UI Offline does not support the desktop view options. To exit
the desktop view and load the mobile view:
- In Chrome, deselect the Request desktop site option.
- In Safari, close the browser and open the Metasys UI and the
Metasys UI Offline.
• Ensure your web browser has cookies enabled before browsing to
the Metasys UI and the Metasys UI Offline.
• Ensure you have the Enable DOM Storage setting selected on the
client device. For Windows operating systems, go to Internet Options
> Advanced > Security and verify the Enable DOM Storage setting is
selected.

Table 31: Metasys UI and Metasys UI Offline Client Technical Specifications for Communication
Channels
Supported For optimal performance, we recommend a wired connection for

Communication computers browsing to the Metasys UI and the Metasys UI Offline.
Channels
Ethernet network interface card 10/100/1000 Mbps
Wireless IEEE 802.11 connection
4G Network
Notes:
• The Metasys UI and the Metasys UI Offline may run over a 3G network.
However, browsing to the Metasys UI and the Metasys UI Offline over
3G is not recommended or supported.
• High latency (also called lag or wait time) can cause the Metasys UI
and the Metasys UI Offline to disconnect from the ADS or ADX, or SCT
computer.
• Signal strength impacts the overall performance of the Metasys UI and
the Metasys UI Offline. For the best results, ensure that you have a
strong signal for your wireless connection.
• To avoid high latency, we recommend a network with 20mbps upload
speed.
CCT Technical Specifications

Table 32: CCT System Requirements
Recommended Computer Intel® Core® 2 Duo E6700 or better (Intel Core 2 Duo E4300
minimum)
20 GB free hard disk available (600 MB minimum)

Recommended Memory Computer Platforms: 16 GB RAM (4 GB RAM minimum)
Supported Operating System Windows® 10 Pro and Enterprise Editions with Creators
(OS) and Database Software Update (version 1709) (64 bit)
Supports Microsoft® SQL Server® 2016 Express with SP1 (64-

bit), Microsoft SQL Server 2014 Express with SP2 (64-bit) , or
Microsoft SQL Server 2012 Express with SP4 (64-bit)
Supports Microsoft SQL Server 2016 Standard with SP1 (64-

bit), Microsoft SQL Server 2014 Standard with SP2 (64-bit) , or
Microsoft SQL Server 2012 Standard with SP4 (64-bit)
Note: The OS and software must both be 64-bit.

Windows 8.1 Pro and Windows 8.1 Enterprise Editions with

Update 1 (64-bit)
Supports Microsoft SQL Server 2016 Express with SP1 (64-

bit), Microsoft SQL Server 2014 Express with SP2 (64-bit) , or
Microsoft SQL Server 2012 Express with SP4 (64-bit)
Supports Microsoft SQL Server 2016 Standard with SP1 (64-

bit), Microsoft SQL Server 2014 Standard with SP2 (64-bit) , or
Microsoft SQL Server 2012 Standard with SP4 (64-bit)

Windows 7 Professional, Enterprise, and Ultimate Editions
with SP1 (64-bit)
Supports Microsoft SQL Server 2014 Express with SP2 (64-bit),
or Microsoft SQL Server 2012 Express with SP4 (64-bit)
Supports Microsoft SQL Server 2014 Standard with SP2 (64-bit),

or Microsoft SQL Server 2012 Standard with SP4 (64-bit)

Required Web Browser Windows® Internet Explorer® 11.0.9600.18816 Update version
Software for Metasys Client 11.0.47 or later, Microsoft Edge® version 41 or later, Apple
Computers Safari® 11 or later, and Google® Chrome™ version 61 or later.
Note: In Internet Explorer 11, select the Use

Microsoft compatibility lists option, found under
Tools>Compatibility View Settings, to ensure that websites
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 for Ethernet network interface card 10/100/1000 Mbps (100 Mbps
CCT Client Computer network or better recommended)
Software Optionally Installed Microsoft .NET Framework version 4.6.1
During CCT Install
Microsoft SQL Server 2014 Express software with SP2

Optional Connection Devices Bluetooth Commissioning Converter (MS-BTCVT-1)

(Order Separately) Note: The BTCVT is no longer available but continues to be
supported.
Laptop with Bluetooth® wireless communications or a

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

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

Release 4.2 has a BACnet Router connection to the SA Bus of an
IP field controller on your subnet.
BACnet Router Setup for Tool Connections—The BACnet Router

setup has been updated 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
NxE85/NIE89/LCS85 Technical Specifications
Table 33: NxE85/NIE89/LCS85 Software System Recommendations for Installation/Upgrade
Product Code Number MS-NXE85SW-0 Network Integration Engine Software for 10,000 objects
(new projects only software)
MS-NIE89SW-0 Network Integration Engine Software for 10,000 objects

(new projects only software)
MS-LCS85SW-0 LON Control Server Software for 10,000 objects (new

projects only software)
MS-15UKG-0 NXE/LCS Software Upgrade 15,000 additional objects

(15,000 object upgrade for total of 25,000 objects)

Recommended Intel Xeon E5506, 2.13 GHz, 4 MB Cache

Computer 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 8 GB RAM minimum
Hard Disk 160 GB minimum
Supported 64-bit Windows® Server® 2016 (64-bit)
Operating Systems and
Software
Note: Microsoft .NET Framework 3.5 Service Pack (SP) 1 and

Microsoft .NET Framework 4.6.1 are required for any of the
operating systems.
Systems for Metasys (version 1709) (64-bit)
Client Computers
Windows® 8.1 Pro and Enterprise Editions with Update 1 (64-bit)

(64-bit)
Apple OS X 10.10 Yosemite
Note: Apple operating systems are supported for Metasys client

computers only. Also, in Apple OS X, you cannot view Graphics+
graphics in the Site Management Portal UI.
Internal Optical Drive DVD ROM, SATA
Supported Web Browser Windows® Internet Explorer® 11.0.9600.18816 Update version 11.0.47
Software for Metasys or later
Note: In Internet Explorer 11, select the Use Microsoft
Client Computers
correctly.
Other browsers, such as Mozilla® Firefox®, may also be used but are
not fully supported.
Supported Virtual Microsoft Hyper-V™, VMWare®
Environments

Network Communication Selectable Network Interface (if computer has multiple network cards,
during NxE85/NIE89/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 Uninterruptible power supply (UPS)
Protection
Smart-UPS SC 450VA, 280 W, 120 VAC input/output, NEMA 5-15R output
connections, OEM Part No. SC450RM1U
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.
Graphics+ Viewer Requirements

Table 34: Graphics+ Viewer System Requirements
Component Description
Product Graphics+ Viewer built into Site Management Portal
(SMP) UI and System Configuration Tool (SCT) UI
Recommended Processor
1 2 3
Intel® Core™ 2 Duo E6700 or better (Intel Core 2 Duo
1
2
3
E4300 minimum)
Memory 4 GB (2 GB minimum)
Client Computer Operating System Windows® 10 Pro and Windows 10 Enterprise (64-bit)
Windows 8.1 and Windows 8.1 Pro (64-bit)
Windows 7 Professional, Enterprise, and Ultimate

Editions with SP1 (32-bit and 64-bit)
Windows Server® 2012 (64-bit)
Windows Server 2008 R2 with SP1 (64-bit)
Note: In OS X, you cannot view Graphics+

graphics in the Site Management Portal UI.
Other Software Windows Internet Explorer® version 11
Note: In Internet Explorer 11, select the Use

Microsoft compatibility lists option, found
under Tools > Compatibility View Settings,
to ensure that websites appear and function
correctly.
Microsoft Silverlight® 5.0 or later

Communication Ethernet network interface card 10/100/1,000 Mbps
(100 Mbps network or better recommended)
Note: We recommend using a wired ethernet

connection.
Wireless 802.11 connection

Minimum Screen Size 15 inch (21 inch recommended)

Table 34: Graphics+ Viewer System Requirements
Component Description
Minimum Screen Resolution 1024 x 768 (normal format)
1280 x 800 (wide screen format)

Minimum Graphic Card Memory 64 MB
1 For large graphics, rendering the image is CPU intensive. In general, a higher performing CPU with multiple cores is
recommended.
3 We recommend client machines browsing to the Site Management Portal (SMP) UI for Graphics+ viewing have a
CPU benchmark rating of approximately 2000. To view your client machine's CPU benchmark rating, go to https://
www.cpubenchmark.net/cpu_list.php.
For more information on hardware and software requirements for the Graphic Generation Tool,
refer to the Graphic Generation Tool Installation Instructions (LIT-12011685).
Metasys System Related Documentation

The documents in Table 35 contain information related to the features, installation, operation,
configuration, and troubleshooting of the Metasys system. Important user information is located in
the Metasys SMP Help (LIT-1201793).
Table 35: Related Documentation
For information on See document

How to License Metasys System Software Software Activation Manager Help (LIT-12012389)
Features, Benefits, and Specifications of the Metasys UI Help (LIT-12011953)
Metasys UI
Features, Benefits, and Specifications of the Metasys UI Offline Help (LIT-12012116)
Metasys Offline UI
Features, Benefits, and Specifications of Application and Data Server (ADS) and Extended
the Application and Data Server/Extended Application and Data Server (ADX) Product Bulletin
Application and Data Server (ADS/ADX) (LIT-1201525)
Features, Benefits, and Specifications of the Open Data Server Product Bulletin (LIT-12011943)
BACnet Open Data Server (ODS)
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
NAE Commissioning for KNX Vendor NAE Commissioning for KNX Vendor Integration
Integration (LIT-12013148)
NAE Commissioning for M-Bus Vendor NAE Commissioning for M-Bus Vendor Integration
NAE Commissioning for Modbus Vendor NAE Commissioning for Modbus Vendor
Integration Integration (LIT-12023150)


NAE Commissioning for C·CURE 9000 Access NAE Commissioning for C·CURE 9000 Access
Control and victor Video Management Control and Victor Video Management Integration
NAE Commissioning for Molex and Cree NAE Commissioning for Molex and CREE Digital
Digital Lighting Systems Integration Lighting Systems Integration (LIT-12013152)
NAE Commissioning for Simplex Fire System NAE Commissioning for Simplex Fire System
Integration Integration Application Note (LIT-12013060)
Features, Functions, and Applications of Network Control Engine Product Bulletin
the Network Control Engine (NCE) 25 in (LIT-12011283)
the Metasys System, Including Technical
Features, Benefits, and Specifications of the Metasys System Field Equipment Controllers and
Field Equipment Controller (FEC) Family Related Products Product Bulletin (LIT-12011042)
Features, Benefits, and Specifications of the Metasys CGx, CVx Equipment Controllers Product
CGx, CVx Equipment Controllers Bulletin (LIT-12013105)
Features, Benefits, and Specifications of the System Configuration Tool Catalog Page
System Configuration Tool (SCT) (LIT-1900198)
How to Install and Upgrade the ADS and Metasys Server Installation and Upgrade
ADX Software; How to Install and Upgrade Instructions (LIT-12012162)
Metasys UI; How to Install the Metasys
Advanced Reporting System
How to Install and Upgrade SQL Server SQL Server Installation and Upgrade Instructions
Software (LIT-12012240)
How to Install and Upgrade the SCT and SCT Installation and Upgrade Instructions
Metasys UI Offline Software (LIT-12012067)
How to Install and Upgrade the ADS-Lite and Metasys Server Lite Installation and Upgrade
Metasys UI Software Instructions (LIT-12012162)
How to Install the ODS ODS Installation and Upgrade Instructions Wizard
(LIT-12011945)
How to Use the Metasys Database Manager to Metasys Database Manager Help (LIT-12011202)
Manage Historical Data on an ADS
How to Install the CCT Software CCT Installation Instructions (LIT-12011529)
How to Install the Graphic Generation Tool Graphic Generation Tool Installation Instructions
(LIT-12011685)
How to Use the Advanced Reporting System Metasys Advanced Reporting System and Energy
Essentials Help (LIT-12011312)
How to Use Graphic Generation Tool Graphic Generation Tool Help (LIT-12011697)
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 ODS to be a BACnet ODS Commissioning Guide (LIT-12011944)
Workstation or Site Director, Use Server
Repositories, Synchronize Time, Use a
Network Printer, Accept Dial-Up Connections,
and More
How to Apply, Mount, Wire, Set Up, and NAE35/NAE45 Installation Instructions (Part No.
Start the NAE35 and the NAE45, Including 24-10050-6)
Technical Specifications and Ordering
Information
How to Apply, Mount, Wire, Set Up, and Start NAE55 Installation Instructions (Part No.
the NAE55 Including Technical Specifications 24-10051-43)
and Ordering Information
How to Apply, Mount, Wire, Set Up, and NAE55-S Installation Instructions (Part No.
Start the NAE55-S, Including Technical 24-10051-108)
How to Apply, Mount, Wire, Set Up, and Start NCE25 Installation Instructions (Part No.
the NCE25, Including Technical Specifications 24-10143-63)
and Ordering Information
How to Set Up an NAE35, NAE45, and NAE55 NAE Commissioning Guide (LIT-1201519)
for 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 LonWorks Control Server (LCS) 85 Commissioning
(LCS) 85 for Operation on the Metasys® Guide (LIT-12011568)
Network
How to Use the SCT, Including Setting Up Metasys SCT Help (LIT-12011964)
Archive Databases Offline and Basic N2
Online Network Setup
How to use SCT Pro, including the Metasys SCT Pro Help (LIT-12013035)
maintenance 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)
How to Install the NAE Update Tool and NAE Update Tool Help (LIT-12011524)
Update NAEs From One Release to Another
Network Information (Including Security Network and IT Guidance Technical Bulletin
Risks) (LIT-12011279)
How to Apply and Engineer a Metasys Smoke Metasys System UL 864 9th Edition UUKL/ORD-
Control System that Complies with the C100-13 UUKLC Smoke Control System Technical
Metasys System UL 864 10th Edition UUKL/ Bulletin (LIT-12011252)
ORD-C100-13 UUKLC Smoke Control Listing


Devices and Logic Used to Implement a 10th Metasys System UL 864 UUKL 9th Edition UUKL/
Edition Smoke Control System for Single ORD-C100-13 UUKLC Standard Smoke Control
Story Mall, Warehouse, and Multistory Applications Application Note (LIT-12011308)
Building
How to Integrate a Fire System into the Metasys System Extended Architecture Fire System
Metasys Network Integration Using the IFC BACnet® Gateway
Application Note (LIT-1201993)
NAE Compliance with American National NAE/NCE Protocol Implementation Conformance
Standards Institute (ANSI)/American Statement (LIT-1201532)
Society of Heating, Refrigerating, and Air-
Conditioning Engineers (ASHRAE) Standard
135-2004, BACnet® Protocol
How to Install the Launcher Software Launcher Installation Instructions (LIT-12011783)
How to Use the Launcher Software to Launcher Tool Help (LIT-12011742)
Shorten the UI Access Time and Manage Sites
How to Use Web Service Technology for Metasys System Secure Data Access DLL Technical
Secure Access to the Metasys System Bulletin (LIT-1201663)
How to Create and Modify Users and Roles, Security Administrator System Technical Bulletin
Configure User Profiles, Assign System Access (LIT-1201528)
Permissions, Assign All Items Navigation
View Permissions, and Unlock User Accounts
How to Set Up an MS/TP Communications Bus MS/TP Communications Bus Technical Bulletin
(LIT-12011034)
BACnet/IP Configuration Metasys IP Networks for BACnet/IP Configuration
Guide Technical Bulletin (LIT-12012458)
How to Set Up an NAE as a BACnet/IP or BACnet Controller Integration with NAE/NCE/ODS
BACnet MS/TP System Integrator in a Metasys Technical Bulletin (LIT-1201531)
Network
How to Set Up an NAE or LCS85 as a LonWorks Network Integration with NAE and LCS
LonWorks 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 WNC1800/ZFR182x Pro Series Wireless Field Bus
Bus System System Technical Bulletin (LIT-12012356)
TEC Wireless Thermostat Controller System TEC Series Wireless Thermostat Controller System
Technical Bulletin (LIT-12011414)
WRS Series Many-to-One Wireless Room WRS Series Many-to-One Wireless Room
Temperature Sensing System Temperature Sensing System Technical Bulletin
(LIT-12011094)


TE-7800 Series One-to-One Wireless Room TE-7800 Series One-to-One Wireless Room
Temperature Sensing System Temperature Sensing System Technical Bulletin
(LIT-12011097)
WRZ-7850 One-to-One Wireless Room WRZ Series One-to-One Wireless Room Sensing
Temperature Sensing System System Technical Bulletin (LIT-12011641)

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

Metasysystem Configuide PDF

Uploaded by

Copyright:

Available Formats

Metasysystem Configuide PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Metasysystem Configuide PDF

Uploaded by

Copyright:

Available Formats

Metasys System Configuration Guide

Building Technologies & Solutions LIT-12011832

General Purpose Application Controllers (CGMs) and VAV Box Equipment

Advanced Application Field Equipment Controller (FAC)..................................................... 12

Field Equipment Controllers (FEC).......................................................................................... 12

FEC Field Equipment Controller Family Comparison............................................................13

VMA VAV Modular Assembly Series........................................................................................ 13

Input/Output Module (IOM).................................................................................................... 14

Controller Configuration Tool (CCT).................................................................................................. 15

TEC3x00 Series Networked Thermostat Controllers.......................................................................16

Network Engine Comparison.................................................................................................. 19

ADS and ADS-Lite...................................................................................................................... 19

System Configuration Tool Pro (SCT Pro)...............................................................................26

Metasys Database Manager..................................................................................................... 26

VMD Generator Express (VGE Tool)........................................................................................ 26

NIEx9 Driver Manager Tool..................................................................................................... 27

Metasys System Capabilities..............................................................................................................27

Monitoring and Commanding................................................................................................ 28

Alarm and Event Management............................................................................................... 28

Destination Delivery Agents (DDA)......................................................................................... 30

RADIUS Server Accounts.......................................................................................................... 30

Historical Data Management (Trend)..................................................................................... 31

Logic Connector Tool (LCT)...................................................................................................... 34

Demand Limiting and Load Rolling........................................................................................ 34

Audit Trails (Transaction Data Management)........................................................................34

System Diagnostics and Serviceability................................................................................... 35

Metasys for Validated Environments.......................................................................................35

UL 864 10th Edition UUKL and ORD-C100-13UUKLC Smoke Control Listing.................... 35

ii Metasys System Configuration Guide

Metasys Advanced Reporting System..................................................................................... 36

Metasys Graphics Options................................................................................................................. 36

Advanced Graphics Application Software..............................................................................38

MS/TP Communications Bus................................................................................................... 38

N1 Integration (Release 9.0 or earlier)...................................................................................39

C·CURE 9000 Access Control....................................................................................................39

victor Video Management....................................................................................................... 39

Simplex Fire system.................................................................................................................. 39

Cree and Molex Lighting Systems.......................................................................................... 40

Metasys System Revision Compatibility Overview........................................................................... 40

General Compatibility Information for Customer Job Sites................................................ 40

Compatibility Rules for CCT and Field Controller Revisions................................................ 40

Output Controller Module Upgrades..................................................................................... 41

Graphics+ Release 1.3.............................................................................................................. 42

FEC, FAC Wireless Integrations................................................................................................42

WNC1800/ZFR182x Pro Series Wireless Field Bus System...................................................43

Metasys System Configuration Guide iii

Metasys System Configuration Examples......................................................................................... 43

ADS/ADX Site Director with Multiple NAEs System Configuration..................................... 44

ADS/ADX Site Director and Secure NAE-S with Unencrypted NAEs.................................... 44

ADX Split Configuration............................................................................................................45

Unified and Split ADX with Dual Network Cards...................................................................47

Large ADX Site Configuration..................................................................................................48

ODS Workstation Configurations............................................................................................48

N1 Integration System Configuration.................................................................................... 50

BACnet/IP Network System Configuration............................................................................ 50

Third-Party Network Integration............................................................................................ 52

Wireless Metasys System Configurations............................................................................... 52

Smoke Control Application Configuration............................................................................. 53

Performance Guidelines and Limitations.........................................................................................54