Professional Documents
Culture Documents
Metasys System Configuration Guide: Building Technologies & Solutions 2022-05-20 LIT-12011832 Release 12.0
Metasys System Configuration Guide: Building Technologies & Solutions 2022-05-20 LIT-12011832 Release 12.0
Metasys System Configuration Guide: Building Technologies & Solutions 2022-05-20 LIT-12011832 Release 12.0
Summary of changes
The following information is new or revised:
• Added information about BACnet Secure Connect (BACnet/SC) throughout the document,
including BACnet/SC integration, as this is a newly supported protocol standard at Metasys
Release 12.0.
• Added information about MQ Telemetry Transport (MQTT), including MQ Telemetry Transport
(MQTT), as this is a newly supported integration at Metasys Release 12.0.
• Replaced references to Metasys UI Offline with Johnson Controls System Configuration Tool
(JCT) throughout this document, as this tool was rebranded.
• Updated sections that reference Energy Essentials. Energy Essentials is being discontinued at
Release 12.0.
• Added detail that Metasys UI is now supported on the NAE85 and LCS85.
• Updated information about CG series and CV series Equipment Controllers, including the
addition of two new CG series General Purpose Application controller models with an onboard
display and the new Local Controller Display model.
• Updated SNE Series Network Engines, SNC Series Network Control Engines, NAE Series
Network Automation Engine, and Network Engine comparison with Release feature updates.
• Updated Server comparison, Open Application Server (OAS), and LCS85 LonWorks® Control
Server with Release feature updates.
• Updated User Interface with a table that describes the 12.0 offerings and if they support
Metasys UI, SMP with an add-on license, or SMP without an add-on license.
• Updated SCT and System Configuration Tool Pro (SCT Pro) to reflect the latest releases.
• Updated Technical Specifications.
- Added support for Windows ® 10 Enterprise LTSC (21H2)
- Updated information about Windows 10 versions, Windows Server 2019, Windows Server
2016, SQL Server 2019 Express and Standard, SQL Server 2017 Express and Standard, SQL
Server 2016 Express and Standard.
- Removed support for Windows 8.1, SQL Server 2014 Express and Standard.
• Updated Related Documentation to include the new BACnet/SC Workflow Technical Bulletin
(LIT-12013959), Mass Changes Tool (MCT) Help (LIT-12013963), and MQTT Client External Data
Connector Network Engine Commissioning Guide (LIT-12013976).
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
Equipment Controllers
Metasys includes several model series of equipment controllers, including General Purpose
Application Controllers (CG series), VAV Box Controllers (CV series), Advanced Application
Field Equipment Controllers (FACs), Field Equipment Controllers (FECs), Variable Air Volume
Modular Assembly (VMAs), Input/Output Modules (IOMs), and Expansion Input/Output Modules
(XPMs). These devices provide direct, operational control over HVAC and other mechanical and
electrical equipment and are typically networked together and supervised by network engines.
The BACnet® family of controllers is tested by an independent BACnet Testing Lab. A complete
The following table outlines the CG series and CV series controllers in more detail. The models
introduced at Release 12.0 are CGM09090-0H and CGE09090-0H. The letter H in the product code
number indicates that the controller model has an onboard display.
Table 1: CG series and CV series controllers details
CGM04060-0 CGE04060-0 CGM09090-0 CGE09090-0 CVM03050-0 CVM03050-0P CVE03050-0P
CGM09090-0H CGE09090-0H
Description General Purpose Application Controller VAV Box Controller
Inputs and 10 total: 18 total: 8 total: 8 total:
Outputs • 3 Universal Inputs (UIs) • 7 UIs • 3 UIs • 3 UIs
• 1 Binary Input (BI) • 2 BIs • 2 COs • 2 COs
• 4 Configurable Outputs (COs) • 4 COs • 3 BOs • 3 BOs
• 2 Binary Outputs (BO) • 3 BOs • Integral • Integral actuator
• 2 Analog Outputs (AOs) actuator • Integral DPT
• Integral DPT • Integral potentiometer to sense
actual VAV box damper position
Communic- • FC Bus (BACnet BACnet/IP and • FC Bus BACnet/IP and • FC Bus (BACnet MS/TP) BACnet/IP and
ation MS/TP) BACnet/SC (BACnet MS/ BACnet/SC • N2 (software switchable) BACnet/SC
Protocols • N2 (software TP) • Zigbee for ZFR Pro Wireless Field Bus
switchable) • N2 (software (add on modules)
• Zigbee for ZFR switchable)
Pro Wireless • Zigbee for
Field Bus (add ZFR Pro
on modules) Wireless
Field Bus
(add on
modules)
Expandable Yes
through SA
Bus
Onboard Yes
Real Time
Clock
In addition, Release 12.0 includes a new, remote-mountable color display that communicates to an
equipment controller over the SA Bus.
The following figure and table outline the I/O expansion modules, first introduced at Release 11.0.
Note: XPM series expansion modules may coexist on the SA Bus with IOM series input/output
expansion modules.
XPM series expansion modules can be connected to the FC bus of the following network engine
types:
Note: XPM series modules may coexist on the FC Bus with IOM series input/output expansion
modules.
For more information about the M4-XPM series, refer to the M4-XPM Expansion Modules Catalog
Page (LIT-1901145).
Wireless solutions
Several wireless Metasys solutions are available for integrating wireless connectivity in desired
portions of a Metasys network. These solutions provide wireless communication between
controllers, thermostat controllers, coordinators, routers, and room sensors.
• ZFR181x Series Wireless Field Bus System
Depending on the model and configuration options you select, TEC3x00s provide on/off, floating,
and proportional control of:
• local hydronic reheat valves
• pressure-dependent VAV equipment with or without local reheat
• two- or four-pipe fan coils
• cabinet unit heaters
• other zoning equipment using an on/off, floating, or 0 to 10 VDC proportional control input
• single- or two-stage unitary rooftop units (RTUs) and heat pumps, with or without economizers
The TEC3600 series models feature field-selectable BACnet MS/TP or N2 communication capability,
enabling supervisory control from a Metasys network engine or communication to third-party BAS
devices. The TEC3000/TEC3100 series models feature ZFRPro compatible wireless communication
capabilities, enabling supervisory control from a Metasys network engine through a Wireless
Network coordinator.
Network Engines
Network engines perform a key role in the Metasys system architecture. These network engines
provide network management and system-wide control coordination over one or more networks of
equipment controllers, including the following Metasys equipment controllers:
• General Purpose Application MS/TP Controllers (CGMs)
• General Purpose Application Ethernet Controllers (CGEs)
• VAV Box MS/TP Controllers (CVMs)
• VAV Box Ethernet Controllers (CVEs)
Large-capacity engines
• Network Automation Engine: NAE55
• SNE Series of Network Engines: SNE2200x
Note: The SNE2200x succeeds the NAE55 model of engines.
Software-only engines
• Network Automation Engine: NAE85
NAEs provide network supervisor capabilities and IP network connectivity. NCEs also provide
network supervisor capabilities and IP network connectivity, but also feature the I/O point
connectivity and direct digital control capabilities of an FEC. NIEs are variants of NAEs and NCEs that
include legacy and third-party device integration capabilities.
BACnet MS/TP 2 1 1 1
maximum trunks
BACnet MS/TP 100 100 50 100
maximum devices
per trunk (Johnson
Controls devices
only)
Note: A
repeater is
required if
more than 50
Johnson Con-
trols devices
are on the
same trunk.
BACnet MS/TP 64 64 50 64
maximum devices
per trunk (with
third party)
Note: A
repeater is
required if
more than 32
devices are on
the same trunk
and some are
third party.
N2 maximum 2 1 1 N/A
trunks
Mapped N2 devices 100 100 50 N/A
per trunk
Note: A
repeater is
required if
more than 50
devices are on
the same trunk.
LonWorks 1 1 1 N/A
maximum trunks
LonWorks 255 127 60 N/A
maximum devices
Remote Field Bus 6 3 3 N/A
maximum trunks
Remote Field Bus 32 32 32 N/A
maximum Johnson
Controls Devices
per bus
At Release 12.0, the SNC series network control engines include a MQ Telemetry Transport (MQTT)
driver that supports bidirectional communication between network engines and a generic MQTT
broker. Additionally, the SNC supports BACnet/SC from Release 12.0. For more information about
these features, refer to the SNC Catalog Page (LIT-1901115).
The following table outlines the SNC models in more detail.
Table 6: SNC series Network Control Engines details
Features SNC2515x-0 SNC2515x-04 SNC1612x-0 SNC1612x-04
SNC2515x-0H SNC2515x-04H SNC1612x-0H SNC1612x-04H
Succeeds NCE25 Series NCE25 Series NCE25 Series NCE25 Series
Onboard inputs and • 40 total onboard I/O: 14 UI, 11 BI, • 28 total onboard I/O: 10 UI, 6 BI, 4
outputs 4 CO, 4 AO, 7 BO CO, 4 AO, 4 BO
• Supports SA Bus expansion • Supports SA Bus expansion
Communication • 1 Ethernet port: SNC25150-0, SNC25150-04, SNC16120-0, SNC16120-04,
interfaces SNC25152-0, SNC25152-04, SNC25152-0H, SNC25152-04H, SNC16122-0,
SNC16122-04, SNC16122-0H, and SNC16122-04H
• 2 Ethernet ports: SNC25151-0, SNC25151-0H, SNC25151-04,
SNC25151-04H, SNC16121-0, SNC16121-0H, SNC16121-04, SNC16121-04H
• 1 RS-485 port
11
• 2 USB ports for connecting external integration adapters
Note: Servers must be equal to or at a higher Metasys Release than their child engines,
including the SNCs.
NIE29, NIE39, 88
X X Discontinued Discontinued Discontinued
NIE49
NIE59 X X X X
Important: All NIEx9 models have been discontinued from
X manufacture, because starting at 9.0.7 and 10.0, NAE models
include the integration functionality of the NIE. Existing NIE59s
can be field-upgraded to 10.0, 10.1, 11.0, and 12.0 respectively.
NIE89 X X X X
Important: All NIEx9 models have been discontinued from
X manufacture, because starting at 9.0.7 and 10.0, NAE models
include the integration functionality of the NIE. Existing NIE89s
can be field-upgraded to 10.0, 10.1, 11.0, and 12.0 respectively.
NIE55, NIE85 X
SNE X X X
SNC X X X
1 Only NCE25xx-0 is available to upgrade to Metasys 9.0.7 or later with Linux OS.
2 Only NAE35xx-2 and NAE45xx-2 are available to upgrade to Metasys 9.0.7 or later with Linux OS.
3 Only NAE55xx-2 and NAE55xx-3 are available to upgrade to Metasys 10.0 with Linux OS.
4 Only NAE55xx-2 and NAE55xx-3 are available to upgrade to Metasys 10.1 with Linux OS.
5 Only NAE55xx-2 and NAE55xx-3 are available to upgrade to Metasys 11.0 with Linux OS.
6 Only NAE55xx-3 is available to upgrade to Metasys 12.0 with Linux OS.
7 At 12.0, an NAE85 can act as a Site Director only. Do not upgrade any child NAE85s to 12.0.
8 Only NIE29xx-0s, NIE39xx-2, and NIE49xx-2 are available to upgrade to Metasys 9.0.7 or later with Linux OS.
MQTT X
22
BACnet/IP X X X X X X
BACnet MS/TP X X X X X X
Legacy N1 LAN X
Legacy N2 Bus X X X X
33
X
3
LonWorks X X X
44
X
4
Servers
Application and Data Server (ADS) and ADS-Lite
The ADS is a Metasys server running on a computer that has a supported Microsoft® Windows®
operating system and two specific components. The first component is the relational database
management system using a supported edition of Microsoft SQL Server® Express software to
store collected trend data, audit trail messages, and alarm and event messages with operator
annotations. The second component is the web server software that provides SMP UI and Metasys
UI access to data and routes commands to the Metasys system.
The ADS also supports the following:
• a greater number of engines as a Site Director than an engine supports
• multiple, simultaneous international languages at the user interfaces
• allows a greater number of simultaneous users than is supported by an engine
For more information, refer to the Application and Data Server (ADS) and Extended Application and
Data Server (ADX) Product Bulletin (LIT-1201525) and to Open Application Server (OAS) Product Bulletin
(LIT-12013309).
5 20
8 17
10 15
25-user ADX 0 25
10 15
20 5
25 0
50-user ADX 0 50
10 40
25 25
50 0
100-user ADX 5 50
22
10 50
2
25 50
2
50 50
2
75 25
100 0
1 The 10-user ADX has an SMP 10 concurrent user limitation. The Metasys UI concurrent user limitation is 25.
2 The 100-user ADX has an SMP 100 concurrent user limitation. The Metasys UI concurrent user maximum is 50.
For example, as shown in Table 11, with a 5-user ADS or ADS-Lite, 5 Metasys UI users are supported
if no SMP users are logged in, or 3 Metasys UI users are supported if 2 SMP users are logged in.
Similarly, with a 50-user ADX, 50 Metasys UI users are supported if no SMP users are logged in,
or 40 Metasys UI users are supported if 10 SMP users are logged in. The only Metasys UI user
restriction applies to a 100-user ADX: no more than 50 Metasys UI users are supported, regardless
of the number of SMP users.
Note: Do not install SCT or CCT on the OAS Turnkey computer. If you need SCT or CCT for
commissioning the job site, install the tools on a different computer with network accessibility
to the OAS. However, if you host the OAS on a virtual machine (VM), you can install SCT and
CCT on the same VM as the OAS software.
As a Site Director, the OAS Standard supports up to two supervisory devices, 200 field devices, and
20,000 objects using BACnet/IP and Remote Field Bus integrations. The OAS supports integration
with the following devices and systems: C•CURE-victor, Modbus, M-Bus, KNX, and OPC Unified
Architecture (UA).
The maximum number of supported simultaneous vendor integrations on an OAS is 8. The
following table provides more information about the available integrations, whereby the limits
relate to standard protocol drivers only.
Table 13: Vendor integration types and numbers
Vendor integration type Maximum number of supported
simultaneous integrations (standard
protocol drivers)
Modbus (TCP or RS-485) 4
M-Bus 4
KNX 2
C•CURE-victor 1
OPC Unified Architecture (UA) 1
Zettler Not supported. Zettler requires a serial
connection. Serial connection is not supported
on the OAS and the Zettler driver is not included
in the OAS platform. The Zettler driver is
included only in engines with Linux-based
platforms.
User Interface
Two variations of the user interface are available: Metasys UI and Site Management Portal (SMP).
Tools
Launcher
The Launcher is a software application that lets you use the SMP or SCT to access the Metasys
system, server or network engine on the building network, regardless of its software version. Key
features of the Launcher include the following:
• Installation of a separate folder to store the Metasys release software on your hard disk. This
practice provides for an isolated, private version of the Java® Runtime Engine (also referred
to as Java Runtime Environment [JRE] ) required to run Metasys software. If you have installed
multiple releases of Metasys software, a separate folder is created for each. The JRE folder
separation strategy allows for independence from the public Java Runtime Engine.
• Support for launching any version of the SMP user interface or SCT. All Metasys server types
and network engine types are supported.
Note: For Release 5.2 or earlier, the specific Java Runtime Environment particular to the
SMP or SCT software release is still required on the client computer.
• Support for launching any website, including Metasys software products, such as Metasys UI,
JCT, SCT Pro, and the Metasys Advanced Reporting System, as well as popular websites such as
the Google® website.
For a list of updated features and benefits available at the latest SCT Release, refer to the System
Configuration Tool Catalog Page (LIT-1900198).
For a guided tour of features on a particular page in SCT Pro, click on your account name in the
upper-right corner of the SCT Pro window, and then click Tour.
For more information about SCT Pro, refer to SCT Pro Help (LIT-12013035).
Time management
The time and date used by all devices connected to a site are synchronized automatically,
preventing errors from manual time entry and clocks that become inaccurate over time. Network-
wide time management ensures that scheduling, trending, audit trailing, data collecting, time-
stamping of alarms, and other functions requiring accurate time management use the same time
and date consistently for all system operations. Because the Site Director is the master time keeper
for all engines and servers on a single site, all of these devices are assumed to use the same time
zone for all time-rated functions.
For network-wide time synchronization, the engine or server acting as Site Director is the time
server for the entire site. All other devices are time clients because they receive the time from
the Site Director. The Site Director can be configured to use three different methods of time
synchronization: Unicast Simple Network Time Protocol (SNTP) (also known as Microsoft Windows
time synch), Multicast SNTP, or BACnet time synch. The Site Director can also be configured to
synch its time from an external website.
New multi-time zone enhancements allow you to schedule events using local machine time
management instead of calculating the Site Director time in relation to the device hosted in a
different time zone.
System navigation
The Metasys UI supports navigation in the form of spaces and equipment relationships. A space is
the physical location or area that is served by a piece of equipment. Equipment is the broad term
used to describe the physical controllers and devices that make your building run. These controllers
and devices include boilers, chillers, air handling units, lights, meters, security, and anything else
used to maintain your building's environment. Equipment can serve spaces and other equipment.
A Metasys system administrator can create spaces and equipment and define the relationship
between them in SCT.
The Building Network tree in Metasys UI provides access to objects using an alternative navigation
tree to the Spaces tree. The Building Network organizes objects according to the Metasys object
hierarchy, similar to the All Items tree in the SMP. Objects listed in the Building Network tree are
identified by name and by icon and display Global Status indicators.
Note: The Building Network tree order is inherited from the SMP All Items tree with minor
exceptions. For example, extension objects appear in the Building Network tree in the Metasys
UI, but they do not appear in the All Items tree in SMP. To reorganize the order of objects, use
the Organize Tree feature in Metasys UI.
The SMP UI and Metasys UI support user-customized system navigation schemes in the form of
User Views, a hierarchical method of organizing and displaying some or all of the items within a
system. A Metasys system administrator can limit a user’s access to the Metasys system by creating
User Views and assigning them to specific users. At Metasys Release 12.0, use SMP or SCT to create
and modify a User View.
Syslog DDA
The Metasys system provides the optional capability of sending its configured audit log entries
and alarm notifications to an external, industry-standard Syslog server, conforming to Internet
published RFC 3164. The Syslog option provides positive indication of each field possible in the
Metasys event and audit entries, replacing any blank field with the single character dash (-).
Individual fields of each Metasys message are sent to the Syslog server separated by the vertical
bar symbol (|), ensuring the integrity of all data sent to the Syslog server.
After the Syslog DDA is configured, all messages sent to the local ADS Repository are also sent
immediately to the configured Syslog server. You can apply forensic analysis on the consolidation of
all electronic audit and event information at the Syslog server.
Encrypted email
Metasys software features an email encryption capability that encrypts user names and passwords
as they are entered into the SMP UI. Embedded and server machines can thereby send emails
to email servers over a secure channel (secure socket layer [SSL]). The entire email payload
is encrypted, and allows Metasys software to communicate to email servers that require SSL
connections.
Users can configure email encryption with no authentication required, including SMTP
authentication, and POP-Before-SMTP authentication.
Scheduling
Scheduling provides a graphical user interface that illustrates when events are scheduled to occur.
Scheduling automates routine functions, such as transferring a room from occupied mode to
unoccupied mode for heating and cooling needs, and energy optimization. Each schedule consists
of a weekly schedule, an exception schedule, a list of items in the schedule, and an effective period.
Exception schedules take precedence over the daily schedule only for their configured length
and then return the schedule to its typical weekly schedule. Exceptions can include references to
Calendars that can, for example, reflect a holiday schedule for the entire facility or show selected
tenant spaces in the building. Another view within the schedule, called Today’s Schedule, shows the
current day’s schedule including how each exception schedule affects the current day’s schedule.
A multi-time zone feature is available that allows the definition of schedules across different time
zone. You can program schedules based on device time zones instead of converting the time to
correlate to the Site Director's time zone.
System security
User accounts control user access to the Metasys system. An account defines which portions of the
Metasys data a user can access (for example, all HVAC data or all lighting data from a particular
area of the building) and which functions the user can perform on that data, from view-only access
to configuring new databases. The Metasys system provides the ability to divide the data into 13
pre-defined categories (including HVAC, Fire, and Security), plus 150 additional custom categories;
and has 10 different levels of user functionality.
You can further limit user accounts to operate only at specified times on specified days of the week.
The System Administrator creates all account settings.
Each account can also have associated preferences, such as which graphic or trend to display when
a user logs in to the SMP UI, or which User Views appear in the Navigation Tree.
The SMP and Metasys UI can use Microsoft Active Directory® accounts.
The User Management feature facilitates the creation and management of users and their roles,
category-based permissions, and privileges directly in Metasys UI Online, without the need to
install software on client machines. Administrators can create and manage user details for Active
Directory and Metasys local users. This feature is also available in the Metasys Site Management
Portal (SMP), but over time it will be available in Metasys UI Online only.
You can assign user access permissions to specific spaces and the equipment serving those spaces
with the Metasys UI Space Authorization. You can thereby segment user access by physical space
within the building or campus.
In addition to making it easier for system administrators to manage Metasys account access,
Microsoft Active Directory®, including Active Directory Federation Service (ADFS), also provides
the ability to use Single Sign-On to access the Metasys system, together with other supported
applications on the enterprise network. ADFS authentication is available to Metasys UI users, but is
not available to Metasys SMP users.
The Audit Log and the System Activity feature record all user activities, and the System
Administrator can thereby monitor user actions.
User names and passwords are obscured at login for local and Active Directory accounts. After
login, user names are partially obscured on the SMP or SCT UI window (for example, JohnSmith
appears as Joh***).
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.
Important:
All validated engines have to be at the same release as the validated site director. For example,
if the validated engines are at 12.0, the validated Site Director also needs to be at 12.0.
However, you can have non-validated engines at a previous release (11.0 or earlier). Refer to
Metasys for Validated Environments, Extended Architecture Catalog Page (LIT-1900466) for further
information about validated engines.
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
Reporting capabilities
Metasys Export Utility Software
The Metasys Export Utility software provides facility managers with the ability to easily build custom
reports using historical data from the Metasys system. You can use this data to manage daily
Energy Essentials
Energy Essentials is an optional software feature that you can add to the Metasys Advanced
Reporting System. Energy Essentials offers seven types of energy reports that provide a high-
level view of normalized energy use across your site, and presents your daily electrical demand
graphically.
Note: Energy Essentials is discontinued from Release 12.0.
Standard Graphics
Standard Graphics is the default Metasys graphics package used to design equipment and floor
plan graphics in scalable vector based format. The package comprises of two components, Graphics
Stencil Library (GSL) and User Graphics Tool (UGT).
GSL is a set of Visio Stencils, Templates, and add-ons (including Gzip, a compression utility), used
with Microsoft® Visio® Professional 2002 to create graphics for use in your Metasys system. The
graphic files created are imported in the User Graphics Tool (UGT), which has the ability to accept
a wide variety of image formats such as SVGs, SVGZs, or JPG files for background images which can
represent buildings, floor plans, mechanical equipment, and any other image that represents the
location or function of the equipment in the graphic. Within UGT, users can bind their graphics to
Metasys objects. Users can view Standard Graphics on the SMP user interface.
Integrations
BACnet/SC integration
BACnet Secure Connect (BACnet/SC) is a recent update to the BACnet interoperability standard
aimed at improving cybersecurity and network infrastructure integrity. BACnet/SC is defined
in Annex AB of the ASHRAE 135-2020 BACnet protocol standard. BACnet/SC identifies a secure,
encrypted datalink layer specifically designed to meet the requirements, policies, and constraints of
IP networking infrastructures.
From Release 12.0, BACnet/SC is supported by the following components, when these components
are field-upgraded to or factory-shipped with Release 12.0 software:
• Application and Data Server (ADS), ADS-Lite, Extended Application and Data Server (ADX), and
Open Application Server (OAS) series application server software
BACnet/IP integration
BACnet/IP integration is available with a number of Metasys equipment controllers:
• CGE09090 General Purpose Application Controller
• CGE04060 General Purpose Application Controller
• CVE03050-0P VAV Box Controller with Position Feedback
• FAC4911 Advanced Application Field Equipment Controller
• VMA1930 VAV Modular Assembly Controller
Note: You can upgrade existing VMA1930 units in the field, but this model is discontinued
from manufacturing.
These controllers communicate on BACnet/IP networks and support increased network
performance, enabling faster access to data and faster troubleshooting. Metasys BACnet/IP
equipment controllers can be connected to a BACnet/IP building automation network in multiple
ways: as daisy-chained devices, as part of a star (also called home run) network, or as part of a ring
network. Daisy-chained networks require less physical wiring and new devices can be added easily
to the network. In a star network, each controller is connected by Ethernet cable directly back to a
main switch. This configuration reduces the possibility of network failure, but requires more wiring
to install. A ring network is a chain of controllers virtually closed by a software component in an
Ethernet switch. These controllers support Media Redundancy Protocol (MRP). With MRP, a ring of
Ethernet controllers can overcome a single communication failure, with a recovery time faster than
a non-ring (daisy chain or star) architecture. Most networks use combinations of these topologies.
For details, refer to the Metasys IP Networks for BACnet/IP Controllers Technical Bulletin (LIT-12012458).
BACnet/IP is also used to integrate the Simplex Fire System and lighting systems from preferred
partners into the Metasys system. For more information about these integrations, see Simplex Fire
system and Cree and Molex lighting systems, respectively.
N2 field bus
The N2 field bus is a local network that links controllers and point interfaces to some network
engines. The N2 bus uses a MS/TP protocol, in which the supervisory device (the network engine)
initiates the communication with the N2 bus devices.
LonWorks
The LonWorks network is a local operating network that was developed by Echelon Corporation.
The network is built around the Neuron chip, a microprocessor that combines three CPUs into
one chip. The LonWorks network uses the LonTalk® protocol, a software language for field device
communication. This protocol uses the Open Systems Interconnect (OSI) reference model and
features all seven communication layers for interoperability among control devices.
Modbus
Modbus is one of the most common communication protocols used in the industry. It is openly
published and royalty-free, making it relatively easy to deploy for an industrial network. Modbus
transmits raw bits, or words without placing many restrictions on vendors. Metasys Network
engines support both Modbus RTU (RS-485, RS-232) and Modbus TCP/IP connectivity. The OAS uses
the default network interface and supports Modbus TCP/IP only. For more information, refer to the
Network Engine Commissioning for Modbus Vendor Integration Application Note (LIT-12013150).
M-Bus
M-Bus (Meter Bus) is a European standard (EN 13757-3) that applies to heat and electric meters.
These meters measure the heat absorbed or released by an energy-conveying liquid in a heat-
exchange circuit. An M-Bus level converter is necessary for an M-Bus integration. The converter
connects a network engine to an M-Bus network.
KNX
Use the KNX Bus to control lighting, blinds and shutters, heating, and attendance systems. KNX
(KONNEX) was created out of the EIB (European Installation Bus), BatiBUS, and EHS (European
Home System) protocols. You need a KNX IP Gateway to connect a network engine to a KNX
network.
Working with SCT Release 11.x or later at Metasys Release 8.x and later
SCT Release 11.x or later features new functionality to save time by simplifying the configuration
process for sites using the Metasys UI. SCT's most valuable enhancement, Rapid Archive Creation,
uses controller application files and templates to efficiently build site archives in a fraction of the
time from previous releases.
In addition to Rapid Archive Creation, SCT now permits spaces and equipment-only downloads
and auto-discovery of serving relationships for Metasys UI. The Downloading Only Metasys UI
Spaces and Equipment options enables sites to download Metasys UI spaces and equipment
information to your Release 7.0 or later server class device (ADS, ADX, or ADS-Lite) through the
Manage Archive Wizard. This new download feature is not intended to replace a full download to
your server; instead it offers a specific and simplified download for JCT configuration.
Auto-Discovery of Serving Relationships uses a matching algorithm to automatically fill Serving and
Served By columns in the Equipment Discovery window. Enhancements to the Find and Replace
functionality give you increased control over Equipment Name and Equipment Descriptions to aid
in more accurate auto-discovery matches.
LCS85 compatibility
There are no known issues with the integration of the LCS85 to a Metasys Release 12.0 site.
Figure 10: Multiple network engines system configuration with Metasys Server Site Director
Figure 12 shows at a high level the difference between the unified and split ADX configurations.
Split ADX configurations are supported for 10-, 25-, 50-, or 100-user ADXs. For example, if you
require your database server to be separate from your application servers, you may want to use an
ADX split configuration.
The following figure illustrates the failover scenario of the BACnet/SC network, where the Primary
Hub is offline and nodes get re-routed to the Failover Hub.
For more information about the BACnet/SC topology and BACnet/SC more generally, refer to
BACnet/SC Workflow Technical Bulletin (LIT-12013959).
Table 24: Maximum number of users supported on Metasys Server type Site Directors
Type of Metasys Computer supported platform Site Metasys UI Users
Server Desktop Server Management (up to)
Portal (SMP)
Users (up to)
ADS05U Yes - 5 5
OASSTD Yes
11
Yes
22 5 5
OASMIN Yes
1
Yes
2
5 5
ADX10U - Yes 10 25
ADX25U - Yes 25 25
ADX50U - Yes 50 50
ADX100U
33 - Yes 100 50
Mapped N2 points per trunk 2,500 2,500 2,500 N/A 2,500 N/A N/A
33
See SNE Series Network Engines for details about SNE Series of Network Engines and see SNC
Series Network Control Engines for details about SNC Series of Network Control Engines.
Note: Alarms and trends from equipment controllers connected to any of these contribute to
the overall totals.
SCT limitations
Table 29: SCT limitations
Description Supported Comments
Max. number of simultaneous 1
users
Max. number of concurrently 10
active archives
Max. size of an active 10 GB Using supported Microsoft
database or project in SCT SQL Server 2019 Express or
Microsoft SQL Server 2017
Express
No limit Using supported Microsoft SQL
Server Software
For further details refer to the Troubleshooting section in the Controller Tool Help (LIT-12011147).
22
Apple® Safari® 13.1 or later Apple® Safari® 13.1 or later
44
Supports:
For SQL Server software, you must purchase SQL Server software licenses per the guidelines listed
here: SQL Server 2019, SQL Server 2017, and SQL Server 2016.
For SQL Server software, you must purchase SQL Server software licenses per the guidelines listed
here: SQL Server 2019, SQL Server 2017, and SQL Server 2016.
Supports:
For SQL Server software, you must purchase SQL Server software licenses per the guidelines listed
here: SQL Server 2019, SQL Server 2017, and SQL Server 2016.
Supports:
For SQL Server software, you must purchase SQL Server software licenses per the guidelines listed
here: SQL Server 2019, SQL Server 2017, and SQL Server 2016.
Ethernet ports
22 2
Wireless card
33 M.2
Note: The OAS Turnkey does not meet the minimum requirements to run the fault detection
and fault triage features.
If you install the OAS on a virtual machine, review the following table to verify that you meet the
minimum hardware and software requirements.
Table 41: OAS application hardware and software requirements
Recommended computer platform Intel Core i7-8700 Processor, Six Cores, 3.20 GHz
or better
Note: Match the specs of the ADS/ADX rec-
ommendations that correspond to the site
characteristics. For example, the number of
users, the number of engines and objects,
and site traffic. If you host the OAS on a vir-
tual machine, match the recommendations
listed in the Network and IT Guidance Technical
Bulletin (LIT-12011279).
Two 500 GB hard disk with 40 GB free space
after you install all prerequisite software and
before you install OAS software. Configure RAID 1
(mirroring) with disk write caching enabled
Note: Prerequisite software includes the sup-
ported operating system, database software,
and .NET Framework.
Memory Minimum: 8 GB
Note: The VM host must have at least 8 GB of
allocated RAM at all times. When you config-
ure the VM, do not select the enable dynamic
memory option.
Other browsers, such as Mozilla® Firefox®, may also be used but are not fully
supported. You use the web browser to download the Launcher application. After you
install the Launcher application, you use the Launcher, not the web browser, to log in to
the Site Management Portal (SMP) user interface.
Supported web browser Windows® Internet Explorer® 11.0.9600.18816 Update version 11.0.47 or later
software for Metasys UI clients Notes:
• You use the web browser to download the Launcher. The Metasys UI does
not support Internet Explorer 11 on Windows 10 operating systems.
• To ensure that websites appear and function correctly, select the Use
Microsoft compatibility lists option, found under Tools > Compatibility
View Settings.
• Metasys UI does not support InPrivate Browsing. To exit InPrivate Browsing,
close the browser window and open a new browser window.
server recommendations.
2 For best performance, use Serial Attached SCSI (SAS) hard drives, not Small Computer System Interface (SCSI) hard
drives.
3 It is recommended to use RAM that the computer supports.
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.
Notes:
• Refer to the Network and IT Guidance Technical Bulletin (LIT-12011279) for specific Microsoft
Windows OS setting requirements for your Metasys system configuration.
• For information on licensing Microsoft SQL Server, refer to the Microsoft SQL Server Licensing
Guide for your edition of Microsoft SQL Server.
Table 44: SCT System Requirements
Specification Description
Product code TL-SCT-0
TL-SCT-P
Full server platform Intel® Core™ i7-8700 processor, Six Core, 3.20GHz.
20 GB minimum free hard disk space available. Use a Solid State Drive
(SSD) to significantly improve performance compared to other types of
hard disks.
8GB to 16GB 2666MT/s, Dual Rank DDR UDIMM
Power Requirement Dedicated nominal 24 VAC, Class 2 power supply (North America),
SELV power supply (Europe), at 50/60 Hz (20 VAC minimum to 30 VAC
maximum)
Power Consumption 25 VA maximum
Ambient Operating 0°C to 50°C (32°F to 122°F); 10% to 90% RH, 30°C (86°F) maximum dew
Conditions point
Ambient Storage -40°C to 70°C (-40°F to 158°F); 5% to 95% RH, 30°C (86°F) maximum dew
Conditions point
Data Protection Battery Supports data protection on power failure. Rechargeable NiMH battery:
3.6 VDC 500 mAh, with a typical life of 5 to 7 years at 21°C (70°F);
Product Code Number: MS-BAT1020-0
Processor 192 MHz Renesas SH4 7760 RISC processor
Table 53: NAE55xx-3 (UL 916, Energy Management) and NAE5510-3U (UL 864, Smoke Control)
technical specifications
Power requirement Dedicated nominal 24 VAC, Class 2 power supply (North America),
SELV power supply (Europe), at 50/60 Hz (20 VAC minimum to 30 VAC
maximum)
Power consumption 50 VA maximum
Ambient operating 0°C or 32°F to 50°C or 122°F; 10% to 90% RH, 30°C or 86°F maximum
conditions dew point
Ambient storage -40°C or -104°F to 70°C or 158°F; 5% to 95% RH, 30°C or 86°F maximum
conditions dew point
Data protection battery Supports data protection on power failure. Rechargeable gel cell
battery: 12 V, 1.2 Ah, with a typical life of 3 to 5 years at 21°C (70°F);
Product Code Number: MS-BAT1010-0
Clock battery Maintains real-time clock through a power failure. Onboard cell; typical
life 10 years at 21°C or 70°F
Processor 1.46 GHz Intel® Atom® Bay Trail E3815 processor for MS-NAE55xx-3
models
Memory 16 GB flash nonvolatile memory for operating system, configuration
data, and operations data storage and backup for MS-NAE55xx-3
models.
2 GB DDR3 SDRAM for operations data dynamic memory for all models
Operating system NAE5510-3U (UL 864 UUKL 10th ed /S527 UUKL7 4th ed): OEM Version
of Microsoft® Windows® Embedded Standard 7 with SP1 (WES7)
NAE55xx-3: (UL 916): Wind River® Linux LTS 17 (LTS=long-term
support)
Product warranty
This product is covered by a limited warranty, details of which can be found at
www.johnsoncontrols.com/buildingswarranty.
Software terms
Use of the software that is in (or constitutes) this product, or access to the cloud, or hosted services
applicable to this product, if any, is subject to applicable end-user license, open-source software
information, and other terms set forth at www.johnsoncontrols.com/techterms. Your use of this
product constitutes an agreement to such terms.
Patents
Patents: https://jcipat.com
Contact information
Contact your local branch office: www.johnsoncontrols.com/locations
Contact Johnson Controls: www.johnsoncontrols.com/contact-us
© 2022 Johnson Controls. All rights reserved. All specifications and other information shown were current as of document
revision and are subject to change without notice.