Professional Documents
Culture Documents
Metasys System Configuration Guide: Building Technologies & Solutions 2020-08-12 LIT-12011832 Release 10.1
Metasys System Configuration Guide: Building Technologies & Solutions 2020-08-12 LIT-12011832 Release 10.1
Summary of changes
The following information is new or revised:
Metasys system
The Metasys system is a network-based building automation system that operates multiple pieces
of mechanical and electrical equipment found in commercial buildings. The system consists of a
wide variety of hardware and software components. You can apply these components in several
configurations to meet the scale and scope of the customer's building automation needs. This
guide describes the capabilities of each Metasys component, as well as the capabilities of the entire
system. This guide also lists examples of how you can integrate and apply the various Metasys
components to create specific building automation system configurations.
A Metasys site comprises one or more Metasys devices on a continuously connected IP network.
A site’s primary network consists of one or more engines. The engines also provide the Site
Management Portal UI. You can configure the primary network and monitor the users of all
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
Figure 2: General Purpose Application Controller (CGM) and VAV Box Controller (CVM)
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.
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.
• 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.
Depending on the model and configuration options you select, TEC3x00s provide on/off, floating,
and proportional control of:
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.
The network engines can be networked together for scaling up on large projects, and they can be
networked with an ADS, ADX, or OAS for additional functionality and site unification.
Network engines provide building control scheduling, alarm and event management, energy
management, data exchange, historical data storage and management, and custom control
logic. Network engines include an embedded user interface called the Site Management Portal
(SMP). Users access the SMP for system navigation and operation using web browser connections.
Network engines are secured from unauthorized access using password protection and permission
access control as well as IT security best practices.
In addition to providing general comprehensive equipment monitoring and control, network
engines also offer specialized capabilities by series, model, and software release to meet a variety
of application requirements. The network engines are identified by three types:
Small-capacity engines
Large-capacity engines
• Network Automation Engine: NAE55
• SNE Series of Network Engines: SNE22000
Note: The SNE22000 succeeds the NAE55 model of engines.
Software-only engines
• Network Automation Engine: NAE85
Figure 3: SNE Series of Network Engines: SNE22000, SNE11000, SNE10500, and SNE110L0
The following table outlines the features and benefits of the new SNE Series of the Network Engine
family.
Table 4: New SNE Series of Network Engine family features and benefits
Feature Description Benefit
Flexible scalable Four models with varying device Provides system designers with flexibility in
device capacities capacities and parent server type choosing the SNE model that is most cost-
appropriate for the intended application.
High capacity 2 GB RAM and 16 GB of eMMC • Supports the background file transfer
memory Flash feature.
• Provides room for future upgrades,
reassuring customers of a long
operational life once installed.
Linux Operating Wind River® Linux Reassures customers that the underlying
System (OS) operating system is a robust, widely-
accepted, and readily-supported operating
system well-suited for embedded hardware
devices.
The following table provides more details about the four available SNE models.
1
Succeeds NAE55 Series NAE45 Series NAE35 Series NAE45-Lite
Communication • 1 Ethernet • 1 Ethernet port
interfaces port • 1 RS-485 port
• 2 RS-485 2
• 2 USB ports
ports
• 2 USB
2
ports
2
Maximum allowed 600 150 60 110
devices across all
integrations. For
example, MS/TP
+IP. Includes VND
integrations and
devices brought in
via routers.
BACnet/IP 1 1 1 1
maximum trunks
BACnet/IP 200 100 50 10
maximum devices
per trunk
BACnet MS/TP 2 1 1 1
maximum trunks
BACnet MS/TP 100 100 50 100
maximum devices
per trunk
BACnet MS/TP 64 64 32 64
maximum devices
per trunk (with 3rd
party)
N2 maximum 2 1 1 N/A
trunks
Mapped N2 devices 100 100 50 N/A
per trunk
Remote Field Bus 6 3 3 N/A
maximum trunks
Remote Field Bus 32 32 32 N/A
maximum Johnson
Controls Devices
per bus
Remote Field Bus 16 16 16 N/A
maximum devices
per bus (with 3rd
party devices)
1
Maximum objects 5000 2500 2500 2500
in device
3
3
Supported type of • ADS • ADS • ADS ADS-Lite-A only
parent server • ADX • ADX • ADX
• OAS • ADS-Lite-E • ADS-Lite-E
• OAS • OAS
Supported • BACnet/IP
integrations - Simplex® Fire Alarm Control Unit (FACU)
- Cree® SmartCast® Lighting Control
- Molex® Lighting Control
The following table outlines the features and benefits of the new SNC Series of the Network Control
Engines family.
Table 6: New SNC of Series Network Control Engines family features and benefits
Feature Description Benefit
Flexible scalable Four models with varying onboard Provides system designers with flexibility
device capacities inputs and outputs (I/O) and in choosing the SNC model that is the
device capacities. most cost-appropriate solution for the
intended application.
High capacity 2 GB of DDR3 RAM and 16 GB of • Supports the background file transfer
memory eMMC Flash feature.
• Provides room for future upgrades,
reassuring customers of a long
operational life once installed.
Linux Operating Wind River® Linux Reassures customers that the underlying
System (OS) operating system is a robust, widely-
accepted, and readily-supported operating
system well-suited for embedded
hardware devices.
Diagnostic LEDs Diagnostic LEDs for indicating: Decreases time spent by electrical
• Heartbeat activity installers and field technicians when
troubleshooting installation or operational
• Faults
issues.
• Ethernet activity
• FC Bus communication
• SA Bus communication
• USB integration connectivity
• FC Bus End-of-Line status
Modernized Black enclosures with rounded Conveys a modern, high value, and
packaging corners, similar to the SNE and recognizable Metasys brand image.
the General Purpose Application
Controller (CGM).
The following table provides more details about the four available SNC models.
Table 7: SNC Series of Network Control Engines details
Features SNC25150-0 SNC25150-04 SNC16120-0 SNC16120-04
Succeeds NCE25 Series NCE2500 NCE25 Series NCE2500
Onboard inputs and • 40 total onboard I/O: 14 UI, 11 • 28 total onboard I/O: 10 UI, 6 BI,
outputs BI, 4 CO, 4 AO, 7 BO 4 CO, 4 AO, 4 BO
• Supports SA Bus expansion • Supports SA Bus expansion
Communication • 1 Ethernet port
interfaces • 1 RS-485 port
1
• 2 USB ports for connecting external integration adapters
1
24 Metasys System Configuration Guide
Table 7: SNC Series of Network Control Engines details
Features SNC25150-0 SNC25150-04 SNC16120-0 SNC16120-04
Maximum allowed 96 4 60 4
devices across all
integrations. For
example, MS/TP
+IP. Includes VND
integrations and
devices brought in
via routers.
BACnet/IP 1 1 1 1
maximum trunks
BACnet/IP 50 4 50 4
maximum devices
per trunk
BACnet MS/TP 1 1 1 1
maximum trunks
BACnet MS/TP 50 4 50 4
maximum devices
per trunk
BACnet MS/TP 32 4 32 4
maximum devices
per trunk (with 3rd
party)
N2 maximum 1 1 1 1
trunks
Mapped N2 devices 50 4 50 4
per trunk
Remote Field Bus 0 0 0 0
maximum trunks
Maximum objects 2500 2500 2500 2500
in device
2
2
Supported type of • ADS
parent server • ADX
• ADS-Lite-E
• OAS
• ODS
• BACnet MS/TP
• N2 Bus
• LonWorks® (requires USB to LON adapter)
• Modbus: Modbus TCP/IP on Ethernet and Modbus Remote Terminal
Unit on RS-485
• KNX IP
• M-Bus
• Tyco® C•CURE® 9000 and victor® Video Management
• Zettler® Fire Panel
Operating System Wind River® Linux LTS 17 (LTS=long-term support)
Microprocessor NXP i.MX6 DualLite processor
Memory 2 GB of DDR3 RAM and 16 GB of eMMC Flash
User Interface Site Management Portal (SMP)
1 Only the supported USB integration adapters function with the SNC. Other integration adapters that are not supported
shall not function with the SNC.
2 Suggested object limit for performance considerations.
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.
Note: Starting at Release 10.1, the SNC Series Network Controllers succeed the NCE Series of the
Network Control Engine family. For more information about the SNC see SNC Series of Network
Control Engines.
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
The Metasys Server software family includes variants (shown in the table below) with different
feature sets to meet a variety of different applications.
ADX
The ADX is a version of the ADS with extended capabilities for historical data archiving that expand
the multi-user web access capabilities of the system. The ADX supports the relational database
management system that uses a supported edition of Microsoft SQL Server software to store
collected trend data, audit trail messages, and alarm and event messages with user annotations.
This relational database also stores configuration information for site security, trend studies,
and other features. The ADX supports the Metasys Advanced Reporting System, which has a web-
based reporting interface and standard report sets. The users can review the alarm and trend
configuration of their site, run summary and detail reports to monitor alarm and event information,
view offline information, combine alarm and audit information in a single report, and aggregate
trend data at a summary or detailed level. An ADX can also support the optional Energy Essentials
reporting feature, which is an extension of the Metasys Advanced Reporting System.
If the ADX software with its accompanying SQL Server database software is installed on one
computer, it is known as a Unified ADX. If the SQL Server software is located on a different
computer, it is known as a Split ADX.
You can install the ADX in a split configuration with the ADX software/SMP UI/Metasys UI on one
computer (the web/application server computer) and the historical trend, audit, and event data
on another computer (the database server) running Microsoft SQL Server software. The System
Configuration Tool (SCT) software, which is used to generate, back up, and restore the network
database offline, is installed on a separate computer in split configuration. The Metasys Advanced
Reporting System is also available in a split configuration, if the SQL Server database components
are installed on the database server and the SQL Server Reporting Services are installed on the
web/application server. In a split configuration, you can place your database server behind a
firewall for an added layer of data protection.
For example, as shown in Table 11, with a 5-user ADS or ADS-Lite, 5 Metasys UI users are supported
if no SMP users are logged in, or 3 Metasys UI users are supported if 2 SMP users are logged in.
Similarly, with a 50-user ADX, 50 Metasys UI users are supported if no SMP users are logged in, or 40
Metasys UI users are supported if 10 SMP users are logged in. The only Metasys UI user restriction
applies to a 50-user or 100-user ADX: no more than 50 Metasys UI users are supported, regardless
of the number of SMP users.
OAS
Starting at Metasys Release 10.1, a new server offering is available. The Open Application Server
(OAS) combines many of the functions of a Network Engine with a Metasys Server into a single
piece of software with optional add-on features that can be hosted on a virtual machine or can be
purchased as a turnkey offering, where Johnson Controls provides hardware with software already
installed on it.
As Site Director, the OAS supports up to two supervisory devices, 200 field devices, and 20,000
objects. The OAS provides database software options for archiving licensed historical data using
the Microsoft® SQL Server software database, and it enables secure communication to a range of
Network Engines, including the NAEs, NCEs, SNEs, and SNCs. OAS is compatible with both Metasys
UI and Site Management Portal (SMP), and can be configured through the System Configuration
Tool (SCT).
The following table provides a summary of the OAS capabilities:
Table 12: OAS Series Open Application Server capabilities
ADS-type capabilities Network Engine-type capabilities
Supports supervising up to 200 field devices
Supports supervising up to two network engines
directly or 20,000 objects, using BACnet/IP and
(SNE, SNC, NAE, or NCE Series).
Remote Field Bus integrations.
Provides supervisory capabilities such as
Provides the Metasys User Interface (UI), an
scheduling, alarming, trending, data sharing,
intuitive, well-organized, mobile-friendly user
interlocking, and logic for system-wide control
interface.
and coordination.
Optionally (with add-on licenses) provides long
term archival of historical data, trends, alarms,
and events.
ODS
The Metasys Open Data Server (ODS) is a BACnet Testing Laboratories® (BTL) Listed BACnet®
Operator Workstation (OWS). At Release 10.1, ODS is at Protocol Revision 15. It conforms to the B-
OWS profile. The ODS supports up to 25,000 local objects and up to five users. You can configure
the ODS as a BACnet Workstation, as a Site Manager Workstation, or as a Combined Workstation.
In the BACnet Workstation configuration, the ODS uses the BACnet protocol to communicate with
networked BACnet devices. BACnet integration maps NxEs, Field Equipment Controller (FEC)-
family devices, and BACnet devices into the ODS. NxEs and FEC-family devices are treated the same
as BACnet devices. This configuration is best for the customer who requires a BACnet operator
workstation using standard BACnet messages. BACnet features are emphasized, and viewable
object capacity is limited to 25,000 objects.
In the Site Manager Workstation configuration, the ODS acts similarly to an Application and Data
Server/Extended Application and Data Server (ADS/ADX) and uses web services to communicate
with the NxE network engines. Other BACnet devices are mapped into the Metasys system through
the NxE using BACnet integration. The Site Manager Workstation configuration is best when
features and capability (for example, object capacity and performance) are more important to
the customer than strict use of standard BACnet services. The ODS provides all advanced Metasys
system features, and the viewable object capacity includes all of the objects from all of the network
engines reporting to the Site Manager Workstation. In this configuration, the ODS can serve as the
Site Director for up to 100 NxE network engines. In addition, you can connect Johnson Controls® IP
controllers, Johnson Controls MS/TP controllers, and BACnet MS/TP devices over a remote field bus
with the use of a BACnet/IP-to-MS/TP router.
In the combined configuration of BACnet Workstation and Site Manager Workstation, the strengths
of both configurations are combined to deliver an optimal solution to the customer. NxE network
engines can use the ODS as a Site Director and communicate with the ODS using web services,
allowing extended object capacity and advanced Metasys system features. In addition, the ODS can
directly access BACnet devices and FEC-family devices using the BACnet integration capability of the
ODS. This configuration is best for the customer who values features and capability, and also needs
the functionality of a BACnet operator workstation for BACnet devices not associated with a Metasys
engine. In this way, operator monitoring and control is extended to BACnet devices outside of the
control of a Metasys engine.
The following table lists which Metasys products are compatible with the ODS Workstation.
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
• 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
• a single view of all items in alarm, warning, overridden, out of service, and offline states within
a space
• viewing and managing alarms by space and equipment (Alarm Manager) as well as viewing
alarms while not logged in (Alarm Monitor)
• a single view to investigate system security risks, system status details, and user activity
information with the Cyber Health Dashboard
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:
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.
Contact your local Johnson Controls® representative for access to the Launcher software.
For a list of updated features and benefits available at SCT Release 13.2, refer to the System
Configuration Tool Catalog Page (LIT-1900198).
The following table describes which specific tools and capabilities are most appropriate for each
type of network engine:
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.
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.
• The steps for setting up trusted certificates can be complicated. Ask the customer's IT
department for assistance.
• Secure and encrypted communication has the greatest importance between the Site Director
and a client logging in to the Site Director from the Metasys SMP. In many cases, the most
practical choice is to install a trusted certificate at the Site Director (ADS, ADX, OAS, or ODS)
and a self-signed certificates on each network engine that is upgraded to Release 8.1 or later.
If the Site Director is a network engine, you might want to install a trusted certificate on just
the Site Director NAE and self-signed certificates on its child devices.
• The name of the network engine within the SCT archive and the subject common name (or
hostname associated with certificate) within the certificate must match exactly for a certificate
to be imported and bound to IIS.
• Some certificate authorities may require the subject common name (or hostname associated
with certificate) within the certificate to include a domain name. If you are implementing
certificate management on an existing Metasys system, adding a trusted certificate may
require you to add a domain name to the original host name of a server or engine. This action
requires you to rename all data in the Metasys historical databases. This renaming operation
requires intensive database operations that significantly prolong a system upgrade. Therefore,
be sure to allocate extra time if you are renaming historical data as part of an upgrade to
Metasys Release 10.1.
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.
• 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
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.
System Security
User accounts control user access to the Metasys system. An account defines which portions of the
Metasys data a user can access (for example, all HVAC data or all lighting data from a particular area
of the building) and which functions the user can perform on that data, from view-only access to
configuring new databases. The Metasys system provides the ability to divide the data into 13 pre-
defined categories (including HVAC, Fire, and Security), plus 150 additional custom categories; and
has 10 different levels of user functionality.
English (en_us) • The password must meet the four following conditions:
- Include at least one number (0–9)
- Include at least one special character (-, ., @, #, !, ?, $, %)
Note: Only the special characters listed above can be
used; all other special characters are invalid.
- Include at least one uppercase character
- Include at least one lowercase character
• The password must include a minimum of 8 characters and a
maximum of 50 characters.
Czech (cs_cz)
German (de_de) • The password cannot include spaces or include a word or
Spanish (es_es) phrase that is in the Blocked Words list.
French (fr_fr)
• The password and the username cannot share the same three
Hungarian (hu_hu)
Italian (it_it) consecutive characters.
Norwegian (nb_no) • The password must meet three of the following conditions:
Dutch (nl_nl) - Include at least one number (0–9)
Polish (pl_pl)
Portuguese (Brazilian) - Include at least one special character (-, ., @, #, !, ?, $, %)
(pt_br) - Include at least one uppercase character
Russian (ru_ru) - Include at least one lowercase character
Swedish (sv_se) - Include at least one Unicode character that is categorized
Turkish (tr_tr)
as an alphabetic character but is not uppercase or
lowercase
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.
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.
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).
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
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.
To ensure optimal performance of the graphics created in the Metasys UI, follow the
recommendations in the table below.
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.
Standard Graphics
Standard Graphics is the default Metasys graphics package used to design equipment and floor plan
graphics in scalable vector based format. The package comprises of two components, Graphics
Stencil Library (GSL) and User Graphics Tool (UGT).
GSL is a set of Visio Stencils, Templates, and add-ons (including Gzip, a compression utility), used
with Microsoft® Visio® Professional 2002 to create graphics for use in your Metasys system. The
graphic files created are imported in the User Graphics Tool (UGT), which has the ability to accept
a wide variety of image formats such as SVGs, SVGZs, or JPG files for background images which can
represent buildings, floor plans, mechanical equipment, and any other image that represents the
location or function of the equipment in the graphic. Within UGT, users can bind their graphics to
Metasys objects. Users can view Standard Graphics on the SMP user interface.
Integrations
BACnet/IP Integration
BACnet/IP integration is possible with two Metasys equipment controllers, namely the FAC4911
controller and the VMA1930 controller. These controllers communicate on Ethernet IP networks and
support increased network performance, enabling faster access to data and faster troubleshooting.
Metasys BACnet/IP Field Controllers may be connected to your building automation network in
two ways. You can connect them as daisy-chained devices or as part of a star type network, which
is also called home run. You can also network the FAC4911 and VMA1930 controllers, which are
connected by Cisco® technology, in a ring Ethernet topology, which provides network reliability by
mitigating a single point of failure in the IP/Ethernet network. Most networks use combinations
of these topologies. For details, refer to the Metasys IP Networks for BACnet/IP Configuration Guide
Technical Bulletin (LIT-12012458).
BACnet/IP is also used to integrate the Simplex Fire System and lighting systems from preferred
partners into the Metasys system. For more information about these integrations, see Simplex Fire
system and Cree and Molex Lighting Systems, respectively.
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.
• 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.
- 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.
• 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.
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).
• 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.
LCS85 Compatibility
There are no known issues with the integration of the LCS85 to a Metasys Release 10.1 site.
• This configuration only provides long-term storage of data through the use of the Metasys
Export Utility installed on a computer.
• The NAE45-Lite can be partnered with other NAE45-Lite devices only. Additionally, the
NAE45-Lite requires an ADS-Lite-A Site Director, and both of these are available in specific
markets only.
Figure 6: Multiple Network Engine System Configuration with One Network Engine
Designated as the Site Director
Figure 8: Multiple Network Engines System Configuration with Metasys Server Site Director
Metasys Server Site Director and Secure NAE-S with Unencrypted NAEs
Figure 9 shows a network that features a secure NAE-S network engine with other unencrypted
network engines reporting to a Metasys Server Site Director. For more details, refer to the NAE-S
Commissioning Guide (LIT-12012269).
Figure 11 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.
1
Simultaneous SMP users 2 2 4 10 2
2
Objects in device 2,500 2,500 5,000 25,000 2,500
2
Objects within a single 300 300 700 700 300
folder
Dynamic values per
100
graphics
Results displayed in a
500
global search
Languages 1
Objects in entire system 3 million/ 750k (for ADX Site Director Only)
Characters in the name of 400
an object
Characters in the 64
description of an object
Nesting levels for object 7
creation
Extensions per object 10
Sets for third-party 1,000
BACnet states text
Characters for a third- 60
party BACnet states text
Members for a multi-value 500
third-party BACnet states
text
Non-Simultaneous SMP Limited only by memory capacity
users
SMP user views Limited only by memory capacity
Simultaneous browsers 2 (Mix of online, SCT, and Simulation)
per client computer
DLLR load extension Limited only by memory capacity. If you plan to attach a large number of load extensions to a
single DLLR object, consider the memory limitation. For load extensions attached to one DLLR
object, there is a 64 KB text limit for the list of the Loads fully qualified references. Load Limit
= (64 x 1024)/average number of characters per load. 1024 Bytes equals 1 KB. For example,
if your DLLR object is configured with Loads that have fully qualified references that average
100 characters (including dots) in length, then you can support approximately 650 loads (64 x
1024/100) for that DLLR. If you reach the memory limit, you may need to combine loads. For
example, if a site has multiple physical meters, split the meters across multiple controllers and
apply appropriate DLLR loads, if possible. Otherwise, use Interlock or Multiple Command objects
to reduce the number of loads added to the DLLR.
DLLR objects Limited only by memory capacity.
1 An NCE25 or SNC can only act as Site Director for itself.
2 Includes all points, extensions, graphics (background image), trend study, and other objects, such as schedules and
interlocks.
1
2
Desktop
Total engines 14
3
5
4
4
5
1,000
6
100 2
3
4
5
6
Simultaneous SMP 5 5 5 10/25/ 5
7
5
users 50/100
7
7
Dynamic values per 100
graphics
Results displayed in 2,000
a global search
Languages 18
Objects in entire 3 million/ 750k (for ADX Site Director Only)
system
Objects in device
8
Limited by SQL Server storage capacity
8
Objects within a 700
single folder
Characters in the 400
name of an object
Characters in the 64
description of an
object
Nesting levels for 7
object creation
Extensions per 10
object
Sets for third-party 1,000
BACnet states text
Characters for a 60
third-party BACnet
states text
Members for a 500
multi-value third-
party BACnet states
text
Non-Simultaneous Limited only by memory capacity
SMP users
SMP user views Limited only by memory capacity
Simultaneous 2 (Mix of online, SCT, and Simulation)
browsers per client
computer
DLLR load extension Limited only by memory capacity. If you plan to attach a large number of load extensions to a single
DLLR object, consider the memory limitation. For load extensions attached to one DLLR object, there
is a 64 KB text limit for the list of the Loads fully qualified references. Load Limit = (64 x 1024)/average
number of characters per load. 1024 Bytes equals 1 KB. For example, if your DLLR object is configured
with Loads that have fully qualified references that average 100 characters (including dots) in length,
then you can support approximately 650 loads (64 x 1024/100) for that DLLR. If you reach the memory
limit, you may need to combine loads. For example, if a site has multiple physical meters, split the
meters across multiple controllers and apply appropriate DLLR loads, if possible. Otherwise, use
Interlock or Multiple Command objects to reduce the number of loads added to the DLLR.
DLLR objects Limited only by memory capacity.
1 The ADS-Lite-E cannot host servers.
2 The ADS-Lite-A cannot host servers.
3 Varies with concurrent connection.
4 Supports up to five of the following: SNE11000, SNE10500, SNC25150-0, SNC25150-04, SNC16120-0, SNC16120-04, NAE35,
NAE45, NCE25, NIE29, NIE39, and NIE49.
Table 20: Maximum Number of Users Supported on Metasys Server Type Site Directors
Computer Supported Platform Site
Type of Metasys Management Metasys UI Users
Server Desktop Server Portal (SMP) (Up To)
Users (Up To)
ADS05U Yes - 5 5
1 2
OASSTD Yes Yes 5 5
1
2
ADX10U - Yes 10 25
ADX25U - Yes 25 25
ADX50U - Yes 50 50
ADX100U
3
- Yes 100 50
3
ODS 25,000
Yes Yes 5 Not Supported
Objects
1 Virtual Machine or Turnkey only.
2 Virtual Machine only.
3 Metasys for Validated Environments does not support the 100 user ADX.
• 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.
4
Note: The LonWorks integration is only supported on NAE35s, NAE45s, and NCE25s
with the Metasys Release 9.0 software or earlier. The Release 9.0.7 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 variables 1,500 1,500 1,500 N/A 2,000 N/A
Johnson Controls BACnet/IP 50
5,6,7
50
5,6,7
50
5,6,7
50
5,6,7
200
5,6
200
6
5
6
7
devices and third-party BACnet/
IP devices
Objects 2,500 2,500 2,500 2,500
10,000 5,000
(default) 25,000
(upgrade)
Time on battery backup 1,024 seconds N/A
1 Maximum 3 bus segments per FC Bus. Maximum 50 devices per bus segment. Bus segments on an FC bus are
connected with repeaters (only). Up to two cascaded repeaters may be applied to an FC bus (to connect three bus
segments).
2 The maximum device count is 32 if the bus contains all Johnson Controls devices, and 16 if the bus contains one or more
non-Johnson Controls devices.
3 Performance varies based on the point mix (N2 Open/Sys91/VMA). Recommend maximum for best performance is
1,000 points.
4 Single sub-net LonWorks network; does not support routers; supports physical repeaters
5 Depends on the number of objects each BACnet device supports.
6 Johnson Controls IP controllers only work with NAEs (and site directors) at Release 9.0 or later.
7 Some sites may require manual mapping based on system architecture. They may also require system adjustments,
such as BACnet communication adjustments, or firewall off.
See SNE Series of Network Engines for details about SNE Series of Network Engines and see SNC
Series of Network Control Engines for details about SNC Series of Network Control Engines.
Note: Alarms and trends from equipment controllers connected to any of these contribute to
the overall totals.
SCT Limitations
Table 25: SCT Limitations
Description Supported Comments
Max. number of simultaneous
1
users
Max. number of concurrently
10
active archives
Using supported Microsoft
SQL Server Express 2014 or
10 GB
Max. size of an active Microsoft SQL Server Express
database or project in SCT 2012 SP2
Using supported Microsoft SQL
No Limit
Server Software
• 5 equipment controllers (CGM, CVM, FAC or VMA1930) with 6 alarms per hour plus 1 network
engine with 30 alarms per hour (Table 26)
• 5 equipment controllers (CGM, CVM, FAC or VMA1930) with 200 trend samples per hour plus 1
network engine with 500 trend samples per hour (Table 27)
• 5 equipment controllers (CGM, CVM, FAC or VMA1930) with 10 COVs per minute plus 35 FECs
with 10 COVs per minute (Table 28)
Table 26: Example 1
Setup Alarms per Hour
5 equipment controllers with 6 alarms/hour
30 alarms per hour
each
1 network engine 30 alarms per hour
Total 60 alarms per hour
For trend creations in the CGM, CVM, FAC, and VMA1930, the use of faster sample intervals of key
points provides a more intuitive troubleshooting interface in a CCT commissioning session via the
CCT's trend viewer. Setting up the trends for local use in CCT does not mean that the same points
and sample intervals have to be utilized in the network engine integration. The trends created in
an equipment controller do not have to be discovered and used by the network engines; separate
• NxE Passthru is not supported for Transfer to Device (Download) for controllers using
firmware 7.0 or later when going through an engine at Release 8.1 or earlier. However, NxE
Passthru through an engine at Release 9.0 or later works for any Metasys equipment controller.
• NxE Passthru is not supported for N2 devices, because an SA Bus connection is required in the
tool to communicate with an N2 controller.
• The MAP 4.2+ and BACnet Router methods work for any device.
• A Bluetooth or ZigBee Transfer to Device (Download) is supported for devices using 6.2
firmware or older. Bluetooth and ZigBee are not supported for Transfer to Device (Download)
for controllers using firmware 7.0 or later, such as IP controllers, the M4-CGM, and the M4-CVM
equipment controllers.
• Direct Ethernet works for any IP device.
Note: All transfers with SNC Local Applications are done through SCT Manage Archive, never
with CCT transfers.
The following table summarizes the transfer to device limitations.
Table 29: Transfer methods supported by device type and firmware
Controller type Supported CCT connection method
NxE NxE MAP 4.2+/ Bluetooth ZigBee Direct
Passthru Passthru BACnet (BTCVT) Ethernet
- Engine - Engine Router
at 8.1 or at 9.0
earlier or later
BACnet MS/TP
controllers using 6.2 X X X X X
firmware or earlier
BACnet MS/TP
controllers using 7.0 X X
firmware or later
N2 controllers using
6.2 firmware or X X X
earlier
1
1
N2 controllers using
X
8.0 firmware or later
BACnet/IP
controllers using 7.0 X X X
firmware or later
1 Connecting through the SA Bus is required.
For further details refer to the Troubleshooting section in the Controller Tool Help (LIT-12011147).
• 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.
2
installation of all prerequisite software and before installation
of ADS software. Configure RAID 1 (mirroring) with disk
write-caching turned on.
Supports:
• SQL Server® 2017 Express (64-bit)
• SQL Server® 2016 Express with SP2 (64-bit)
• SQL Server® 2014 Express with SP3 (64-bit)
• SQL Server® 2012 Express with SP4 (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 Windows 8.1 Enterprise Editions with
Update (KB2919355) (64-bit)
Supports:
• SQL Server® 2017 Express (64-bit)
• SQL Server® 2016 Express with SP2 (64-bit)
• SQL Server® 2014 Express with SP3 (64-bit)
• SQL Server® 2012 Express with SP4 (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® 7 Professional, Enterprise, and Ultimate Editions
with SP1 (64-bit)
Supports:
• SQL Server® 2014 Express with SP3 (64-bit)
• SQL Server® 2012 Express with SP4 (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/help/3072779/
sql-server-2012-service-pack-3-release-information.
Supported Operating Systems for Windows® 10 Pro and Windows 10 Enterprise Editions
Metasys Site Management Portal (version 1809 or later) (64-bit)
Client Computer
Windows® 8.1 Pro and Windows 8.1 Enterprise Editions with
Update (KB2919355) (64-bit)
VMware®
Supported User Interfaces Site Management Portal (SMP)
Metasys UI
Additional Software Included Launcher software, Network Engine images, Summary
with the ADS Software Download Definition Examples, Microsoft .NET Framework (multiple
versions), SQL Server Management Studio, Metasys Database
Manager, Toggletunnel, SNMP Management Information
Base example files (MIBs), Report Viewer 2010 and Report
Viewer 2012.
Optional Hardware Any network or local printer supported by the qualified
Windows operating system
Optional Software Graphic Generation Tool
CCT software
SCT software
2
of all prerequisite software and before installation of ADS software.
Configure RAID 1 (mirroring) with disk write-caching turned on.
Supports:
• SQL Server® 2017 (64-bit)
• SQL Server® 2016 with SP2 (64-bit)
• SQL Server® 2014 with SP3 (64-bit)
• SQL Server® 2012 with SP4 (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/help/3072779/sql-server-2012-
service-pack-3-release-information.
Windows® Server® 2012 with Update (KB3172614) (64-bit)
Supports:
• SQL Server® 2017 (64-bit)
• SQL Server® 2016 with SP2 (64-bit)
• SQL Server® 2014 with SP3 (64-bit)
• SQL Server® 2012 with SP4 (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/help/3072779/sql-server-2012-
service-pack-3-release-information.
Launcher Software
5
Graphic Generation Tool
CCT Software
SCT Software
For SQL Server software, you must purchase SQL Server software licenses per the guidelines listed
here: SQL Server 2017, SQL Server 2016, SQL Server 2014, and SQL Server 2012.
2
3
of all prerequisite software and before installation of ADS software.
3
Configure RAID 1 (mirroring) with disk write-caching turned on.
Notes:
• Metasys Advanced Reporting System and Energy Essentials
must reside on the ADX web/application server.
• Metasys UI must reside on the ADX web/application server.
Database Server
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)
4
Metasys System Configuration Guide 89
Table 33: Extended Application and Data Server System Requirements (Split ADX Systems, 10
or 25 Users)
Supported Operating Windows® Server® 2016 with Update (KB4489890) (64-bit)
5,6
Systems with
5
6
Supports:
Supported Database
Software • SQL Server® 2017 (64-bit)
• SQL Server® 2016 with SP2 (64-bit)
• SQL Server® 2014 with SP3 (64-bit)
• SQL Server® 2012 with SP4 (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/help/3072779/sql-server-2012-
service-pack-3-release-information.
Windows® Server® 2012 R2 with Update (KB2919355) (64-bit)
Supports:
• SQL Server® 2017 (64-bit)
• SQL Server® 2016 with SP2 (64-bit)
• SQL Server® 2014 with SP3 (64-bit)
• SQL Server® 2012 with SP4 (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/help/3072779/sql-server-2012-
service-pack-3-release-information.
Windows® Server® 2012 with Update (KB3172614) (64-bit)
Supports:
• SQL Server® 2017 (64-bit)
• SQL Server® 2016 with SP2 (64-bit)
• SQL Server® 2014 with SP3 (64-bit)
• SQL Server® 2012 with SP4 (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/help/3072779/sql-server-2012-
service-pack-3-release-information.
Launcher Software
7
Graphic Generation Tool
CCT Software
SCT Software
For SQL Server software, you must purchase SQL Server software licenses per the guidelines listed
here: SQL Server 2017, SQL Server 2016, SQL Server 2014, and SQL Server 2012.
2
installation of all prerequisite software and before installation of ADS
software. Configure RAID 5 with disk write-caching turned on.
Supports:
• SQL Server® 2017 (64-bit)
• SQL Server® 2016 with SP2 (64-bit)
• SQL Server® 2014 with SP3 (64-bit)
• SQL Server® 2012 with SP4 (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/help/3072779/sql-server-2012-
service-pack-3-release-information.
Windows® Server® 2012 with Update (KB3172614) (64-bit)
Supports:
• SQL Server® 2017 (64-bit)
• SQL Server® 2016 with SP2 (64-bit)
• SQL Server® 2014 with SP3 (64-bit)
• SQL Server® 2012 with SP4 (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/help/3072779/sql-server-2012-
service-pack-3-release-information.
Launcher Software
5
Graphic Generation Tool
CCT Software
SCT Software
For SQL Server software, you must purchase SQL Server software licenses per the guidelines listed
here: SQL Server 2017, SQL Server 2016, SQL Server 2014, and SQL Server 2012.
2
6 x 300 GB 15,000 RPM hard disk (RAID 5) with 50 GB free
2
3
space after installation of all prerequisite software and before
3
installation of ADS software. Configure RAID 5 with disk write-
caching turned on.
Notes:
• Metasys Advanced Reporting System and Energy
Essentials must reside on the ADX web/application
server.
• Metasys UI must reside on the ADX web/application
server.
Database Server
5
6
Supports:
• SQL Server® 2017 (64-bit)
• SQL Server® 2016 with SP2 (64-bit)
• SQL Server® 2014 with SP3 (64-bit)
• SQL Server® 2012 with SP4 (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/help/3072779/sql-
server-2012-service-pack-3-release-information.
Windows® Server® 2012 R2 with Update (KB2919355) (64-bit)
Supports:
• SQL Server® 2017 (64-bit)
• SQL Server® 2016 with SP2 (64-bit)
• SQL Server® 2014 with SP3 (64-bit)
• SQL Server® 2012 with SP4 (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/help/3072779/sql-
server-2012-service-pack-3-release-information.
Windows® Server® 2012 with Update (KB3172614) (64-bit)
Supports:
• SQL Server® 2017 (64-bit)
• SQL Server® 2016 with SP2 (64-bit)
• SQL Server® 2014 with SP3 (64-bit)
• SQL Server® 2012 with SP4 (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/help/3072779/sql-
server-2012-service-pack-3-release-information.
Metasys UI
Launcher Software
7
Graphic Generation Tool
CCT Software
SCT Software
For SQL Server software, you must purchase SQL Server software licenses per the guidelines listed
here: SQL Server 2017, SQL Server 2016, SQL Server 2014, and SQL Server 2012.
1
Ethernet Ports
1
2
Wireless Card
1
M.2
Storage 128GB eMMC
1 Although the USB ports are active on the OAS Turnkey Hardware, the OAS does not support using them as an
integration method. For example, you cannot connect a trunk of field devices via the USB port. You must use a Remote
Field Bus or BACnet/IP field devices.
If you are installing the OAS on a virtual machine, review the following table to verify that you meet
the minimum hardware and software requirements.
Table 37: OAS application hardware and software requirements
Intel Atom Processor E3900 or better
Supports:
Supports:
• Refer to the Network and IT Guidance for the BAS Professional Technical Bulletin (LIT-1201279)
for specific Microsoft Windows OS settings that may be required for your Metasys system
configuration.
• For information on licensing Microsoft SQL Server, refer to the Microsoft SQL Server Licensing
Guide for the edition of Microsoft SQL Server that you installed.
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.
Supports Microsoft SQL Server 2017 (64-bit), Microsoft SQL Server 2016
with SP2 (64-bit), Microsoft SQL Server 2014 with SP3 (64-bit), or SQL
Server 2012 with SP4 (64-bit)
Power Note: The VA rating does not include any power supplied to the peripheral
consumption devices connected to Binary Outputs (BOs) or Configurable Outputs (COs),
which can consume up to 12 VA for each BO or CO, for a possible total
consumption of an additional 132 VA (maximum).
+15 VDC power source terminals provide 100 mA total current; quantity of
Power source inputs: five, located in Universal Input terminals; for active (3-wire) input
devices
SA Bus power 15 V at 240 mA maximum
Operating System Wind River® Linux LTS 17 (LTS=long-term support)
Processor NXP i.MX6DualLite Processor, 1GHz 32-bit dual core Cortex A9 processor
16 GB flash nonvolatile memory for operating system, configuration data, and
operations data storage and backup
Memory
2 GB SDRAM for operations data dynamic memory
Universal Input
Input: 24-bit Analog to Digital converter
(UI) resolution
Analog Output
Output: +/- 200 mV accuracy in 0–10 VDC applications
(AO) accuracy
BACnet/IP, BACnet MS/TP, N2 Bus, LonWorks, Modbus, KNX, M-Bus, Zettler
Fire
Supported
integrations Tyco C•CURE 9000-victor video management, Simplex FACU, Molex Lighting
Control, Cree SmartCast Lighting Control
One supported Ethernet port (top); 1000/100/10 Mbps; 8-pin RJ45 connector
One FC port (RJ12 6-pin port; connects with 1.5 m [4.9 ft] RJ12 field bus cable)
One SA port (RJ12 6-pin port; connects with 1.5 m [4.9 ft] RJ12 field bus cable)
Network and
serial interfaces One optically isolated RS-485 port; with a removable 4-pin terminal block
One optically isolated SA Bus port; with a removable 4-pin terminal block
Two USB A ports. All support USB 2.0 and Open Host Controller Interface
[Open HCI] specification.
Ethernet communication: 1000, 100, or 10 Mbps
Transmission Optically isolated, serial communication (FC Bus): 76,800, 38,400, 19,200, 9600,
speeds or 1200 bps (selectable)
Ambient humidity Storage: 5% to 95% RH, 30°C (86°F) maximum dew point conditions
conditions Operating: 0% to 90% RH, 30°C (86°F) maximum dew point conditions
Housing Black Polycarbonate and Acrylonitrile butadiene styrene (ABS) blend
Mounting On flat surface with screws on three mounting clips or a single 35 mm DIN rail
Dimensions
(width x height x 250 mm x 145 mm x 45.5 mm (9.84 in. x 5.71 in. x 1.79 in.)
depth)
Weight 0.65 kg (1.433 lbs)
United States: UL Listed, File E107041, CCN PAZX, UL 916, Energy
Compliance Management Equipment; FCC Compliant to CFR47, Part 15, Subpart B, Class A
Canada: UL Listed, File E107041, CCN PAZX7, CAN/CSA C22.2 No. 205, Signal
Equipment; Industry Canada Compliant, ICES-003
Europe: Johnson Controls declares that this product is in compliance with the
essential requirements and other relevant provisions of the EMC Directive.
Australia and New Zealand: RCM Mark, Australia/NZ Emissions Compliant
BACnet International: BTL 135-2016 Listed B-BC/B-RTR/B-BBMD, Protocol
Revision 15
The performance specifications are nominal and conform to acceptable industry standard. For
application at conditions beyond these specifications, consult the local Johnson Controls® office. Johnson
Controls, Inc. shall not be liable for damages resulting from misapplication or misuse of its products.
Two FC ports (RJ12 6-pin port; connects with 1.5 m [4.9 ft] RJ12 field bus cable)
Network and Two optically isolated RS-485 ports; with a removable 4-pin terminal block
Serial interfaces
Three USB ports (one Micro-B port, and two USB A ports). All support USB 2.0
and Open Host Controller Interface [Open HCI] specification; Micro-USB port
currently inactive
Ethernet communication: 1000, 100, or 10 Mbps
Transmission
speeds Optically isolated, serial communication (FC Bus): 76,800, 38,400, 19,200, 9600,
or 1200 bps (selectable)
Ambient Operating: 0°C to 50°C (32°F to 122°F)
temperature
conditions Non-Operating: -40°C to 70°C (-40°F to 158°F)
Ambient humidity Storage: 5% to 95% RH, 30°C (86°F) maximum dew point conditions
conditions Operating: 10% to 90% RH, 30°C (86°F) maximum dew point conditions
Housing Black Polycarbonate and Acrylonitrile butadiene styrene (ABS) blend
Mounting On flat surface with screws on three mounting clips or a single 35 mm DIN rail
Dimensions
(Height x Width x 190 mm x 125 mm x 44.5 mm (7.48 in. x 4.92 in. x 1.75 in.)
Depth)
Weight 0.387 kg (0.852 lbs)
United States: UL Listed, File E107041, CCN PAZX, UL 916, Energy
Management Equipment; FCC Compliant to CFR47, Part 15, Subpart B, Class A
Compliance Canada: UL Listed, File E107041, CCN PAZX7, CAN/CSA C22.2 No. 205, Signal
Equipment; Industry Canada Compliant, ICES-003
Europe: CE Mark – Johnson Controls, Inc. declares that this product is in
compliance with the essential requirements and other relevant provisions of
the EMC Directive.
Australia and New Zealand: RCM Mark, Australia/NZ Emissions Compliant
BACnet International: BTL 135-2016 Listed B-BC/B-RTR/B-BBMD, Protocol
Revision 15
Supported Tyco C•CURE 9000-victor video management, Simplex FACU, Molex Lighting
integrations Control, Cree SmartCast Lighting Control
Note: The SNE110L0 model supports one IP device integration, but does
not support the N2 Bus or LonWorks network interface.
One Ethernet port; 1000/100/10 Mbps; 8-pin RJ45 connector
One FC port (RJ12 6-pin port; connects with 1.5 m [4.9 ft] RJ-12 field bus cable)
Network and One optically isolated RS-485 port; with a removable 4-pin terminal block
Serial interfaces
Three USB ports (one Micro-B port, and two USB A ports). All support USB 2.0
and Open Host Controller Interface [Open HCI] specification; Micro-USB port
currently inactive
Ethernet communication: 1000, 100, or 10 Mbps
Transmission
speeds Optically isolated, serial communication (FC Bus): 76,800, 38,400, 19,200, 9600,
or 1200 bps (selectable)
Ambient Operating: 0°C to 50°C (32°F to 122°F)
temperature
conditions Non-Operating: -40°C to 70°C (-40°F to 158°F)
Ambient humidity Storage: 5% to 95% RH, 30°C (86°F) maximum dew point conditions
conditions Operating: 10% to 90% RH, 30°C (86°F) maximum dew point conditions
Housing Black Polycarbonate and Acrylonitrile butadiene styrene (ABS) blend
Mounting On flat surface with screws on three mounting clips or a single 35 mm DIN rail
Dimensions
(Height x Width x 190 mm x 125 mm x 45.5 mm (7.48 in. x 4.92 in. x 1.75 in.)
Depth)
Weight 0.387 kg (0.852 lbs)
The performance specifications are nominal and conform to acceptable industry standard. For
application at conditions beyond these specifications, consult the local Johnson Controls® office. Johnson
Controls, Inc. shall not be liable for damages resulting from misapplication or misuse of its products.
(Height x Width x Depth) Minimum space for mounting: 303 mm x 408 mm x 148 mm (12.0 in. x
16.1 in. x 5.8 in.)
Shipping Weight 2.9 kg (6.4 lb)
Compliance UL Listed, File S4977, UL 864 UUKL/UUKLC 10th Edition Listed, Smoke
Control Units and Accessories for Fire Alarm Systems Equipment
Canada: UL Listed, File E107041, CCN PAZX7, CAN/CSA C22.2 No. 205,
Signal Equipment, Industry Canada Compliant, ICES-003
Table 47: NAE55xx-3 (Energy Management) and NAE5510-3U (Smoke Control) technical
specifications
Dedicated nominal 24 VAC, Class 2 power supply (North America),
Power Requirement SELV power supply (Europe), at 50/60 Hz (20 VAC minimum to 30 VAC
maximum)
Power Consumption 50 VA maximum
Ambient Operating 0°C to 50°C (32°F to 122°F); 10% to 90% RH, 30°C (86°F) maximum dew
Conditions point
Ambient Storage -40°C to 70°C (-40°F to 158°F); 5% to 95% RH, 30°C (86°F) maximum dew
Conditions point
Supports data protection on power failure. Rechargeable gel cell
Data Protection Battery battery: 12 V, 1.2 Ah, with a typical life of 3 to 5 years at 21°C (70°F);
Product Code Number: MS-BAT1010-0
Maintains real-time clock through a power failure. Onboard cell; typical
Clock Battery
life 10 years at 21°C (70°F)
1.46 GHz Intel® Atom® Bay Trail E3815 processor for MS-NAE55xx-3
Processor
models
16 GB flash nonvolatile memory for operating system, configuration
data, and operations data storage and backup for MS-NAE55xx-3
Memory models.
2 GB DDR3 SDRAM for operations data dynamic memory for all models
Johnson Controls OEM Version of Microsoft Windows Embedded
Standard 7 with SP1 (WES7, Release 9.0)
Operating System
Wind River® Linux LTS 17 (LTS=long-term support) at Release 10.1
(Height x Width x Depth) Minimum space for mounting: 303 mm x 408 mm x 148 mm (12.0 in. x
16.1 in. x 5.8 in.)
Shipping Weight 2.9 kg (6.4 lb)
United States: UL Listed, File E107041, CCN PAZX, UL 916, Energy
Management Equipment, FCC Compliant to CFR47, Part 15, Subpart B,
Class A
(Height x Width x Depth) Minimum space for mounting: 303 mm x 408 mm x 148 mm (12.0 in. x
16.1 in. x 5.8 in.)
Shipping Weight 3.88 kg (10.4 lb)
The Bureau of Industry and Security of the U.S. Department of
Commerce has regulated this shipment under 740.17(b)(2) of the EAR
Shipping Restriction
and restricted the shipment of this product to the following countries:
Cuba, Iran, North Korea, Sudan, and Syria.
Software terms
Use of the software that is in (or constitutes) this product, or access to the cloud, or
hosted services applicable to this product, if any, is subject to applicable terms set forth at
www.johnsoncontrols.com/techterms. Your use of this product constitutes an agreement to such
terms.
Product warranty
This product is covered by a limited warranty, details of which can be found at
www.johnsoncontrols.com/buildingswarranty.
Patents
Patents: https://jcipat.com