metasys system configuration guide

Metasys System Configuration Guide

LIT-12011832

Release 10.0

Building Technologies & Solutionswww.johnsoncontrols.com2019-03-06

ContentsContentsMetasys System Configuration Guide Introduction......................................................................7

Summary of Changes............................................................................................................................7

Metasys System................................................................................................................................. 7

Equipment Controllers..........................................................................................................................8

General Purpose Application Controllers (CGMs) and VAV Box EquipmentControllers (CVMs)...................................................................................................................... 9

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

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

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

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

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

Wireless Solutions.....................................................................................................................15

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

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

Network Engines................................................................................................................................. 16

NAE............................................................................................................................................. 17

NCE............................................................................................................................................. 18

NIE55/NIE85.............................................................................................................................. 18

NIEx9.......................................................................................................................................... 18

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

Servers.................................................................................................................................................. 20

ADS and ADS-Lite...................................................................................................................... 20

Server Comparison................................................................................................................... 20

ADX............................................................................................................................................. 21

ODS............................................................................................................................................. 22

LCS.............................................................................................................................................. 23

User Interface...................................................................................................................................... 23

Tools...................................................................................................................................................... 25

Launcher.................................................................................................................................... 25

System Configuration Tool (SCT).............................................................................................25

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

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

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

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

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

Site Director............................................................................................................................... 27

Time Management................................................................................................................... 27

System Navigation....................................................................................................................28

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

Preferences................................................................................................................................28

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

Encrypted Communication...................................................................................................... 29

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

Syslog DDA.................................................................................................................................30

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

Encrypted Email........................................................................................................................ 31

Scheduling................................................................................................................................. 31

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

System Security.........................................................................................................................32

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

Interlock Object.........................................................................................................................34

Optimal Start............................................................................................................................. 34

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

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

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

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

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

Reporting Capabilities.........................................................................................................................36

Metasys System Configuration Guideii

Metasys Export Utility Software............................................................................................... 36

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

Energy Essentials...................................................................................................................... 36

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

Metasys UI Graphics..................................................................................................................36

Graphics+................................................................................................................................... 37

Standard Graphics.................................................................................................................... 38

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

Integrations..........................................................................................................................................38

BACnet/IP Integration.............................................................................................................. 38

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

N2 Field Bus...............................................................................................................................39

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

LonWorks................................................................................................................................... 39

Modbus...................................................................................................................................... 39

M-Bus..........................................................................................................................................39

KNX............................................................................................................................................. 39

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

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

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

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

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

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

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

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

Working with SCT Release 11.x or Later at Metasys Release 8.x and Later....................... 42

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

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

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

iiiMetasys System Configuration Guide

LCS85 Compatibility..................................................................................................................43

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

Multiple NAE System Configuration with One NAE Designated as the Site Director....... 43

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

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

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

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

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

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

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

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

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

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

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

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

Site Director Limitations and Recommendations.................................................................54

Network Engine Hardware Limitations..................................................................................56

Alarm and Trending Performance Guidelines.......................................................................58

MS/TP Performance Guidelines.............................................................................................. 59

SCT Limitations..........................................................................................................................59

FAC Integration Considerations.............................................................................................. 59

Transfer limitations...................................................................................................................60

Technical Specifications and Requirements................................................................................60

Hardware Configuration Requirements........................................................................................... 60

Client Computer Requirements for UI Client Devices.................................................................... 61

Application and Data Server (ADS) System Requirements.............................................................63

Extended Application and Data Server System Requirements (Unified 10 or 25User ADX)................................................................................................................................... 66

Extended Application and Data Server System Requirements (Split 10 or 25 User ADX).......... 70

Metasys System Configuration Guideiv

Extended Application and Data Server System Requirements (Unified 50 or 100User ADX)................................................................................................................................... 74

Extended Application and Data Server System Requirements (Split 50 or 100 User ADX)........ 77

SCT Technical Specifications...............................................................................................................81

Metasys UI and Metasys UI Offline Technical Specifications...........................................................83

CCT Technical Specifications.............................................................................................................. 86

NxE85/NIE89/LCS85 Technical Specifications.................................................................................. 88

Graphics+ Viewer Requirements....................................................................................................... 90

Metasys System Related Documentation.................................................................................... 91

vMetasys System Configuration Guide

Metasys System Configuration Guide IntroductionThis document introduces the components and capabilities of the Metasys® system. It alsodescribes how the system operates and provides an overview of the various configurations. It is anexpansion and replacement for the Metasys System Extended Architecture Overview Technical Bulletin(LIT-1201527).For a list of Metasys system related documentation, see Table 35 at the end of this document.

Summary of ChangesThe following information is new or revised:

• Changed the information flow from top-down to bottom-up, starting with the basic componentsof the Metasys system.

• Updated equipment controller content to reflect new models and enhancements.

• Updated network diagrams for the new release.

• Updated Metasys UI Release feature updates.

• Added information about the new integrations, including SIMPLEX® Fire System, C·CURE 9000Access Control system, victor Video Management system, and Cree® and Molex® digital lightingsystems.

• Updated CCT Release feature updates.

• Updated SCT Release feature updates.

• Added information about the new SCT Pro UI.

• Updated password rules in System Security.

• Removed section on P2000 integration. The integration between the P2000 SecurityManagement System and the Metasys Building Automation System is no longer supported atRelease 10.0.

• Updated Supported Concurrent Users.

• Updated Site Director Limitations and Recommendations.

• Updated Network Engine Hardware Limitations.

• Updated Technical Specifications.

• Updated Related Documentation.

• Removed Windows® 7 Professional, Enterprise, and Ultimate Editions with SP1 (32-bit). Thisoperating system is no longer supported for host computers at this release. However, Windows 7(32-bit) is still supported for client computers.

• Changed licensing document referenced in Related Documentation to Software ActivationManager Help (LIT-12012389).

Metasys SystemThe Metasys system is a network-based building automation system that operates multiple piecesof mechanical and electrical equipment found in commercial buildings. The system consists of awide variety of hardware and software components. You can apply these components in several

7Metasys System Configuration Guide

configurations to meet the scale and scope of the customer's building automation needs. Thisguide describes the capabilities of each Metasys component, as well as the capabilities of the entiresystem. This guide also lists examples of how you can integrate and apply the various Metasyscomponents 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 SiteManagement Portal UI. You can configure the primary network and monitor the users of alldevices on the network with the Site Management Portal UI. The engine types are NetworkAutomation Engines (NAEs), Network Integration Engines (NIEs), Network Control Engines(NCEs), or LonWorks® Control Servers (LCSs). These engines are described in further detail in thisdocument.A site can optionally have one or more Metasys servers—computer-based devices that add long-term data storage and support for larger Metasys networks. Metasys server products includeApplication and Data Servers (ADS), ADS-Lite (available only in specific markets), ExtendedApplication and Data Servers (ADX), and BACnet® Open Data Servers (ODS), which are described infurther detail in this document. Metasys servers provide the same Site Management Portal UI as theengines. Additionally, the Metasys UI is installed with the Metasys server software.Each Metasys site has one device (engine or server) that is designated as the Site Director. Typically,the Site Director is the single point of access for all Site Management Portal UI users because theSite Director includes a view of all Metasys devices on the site. If a server is connected to a site, youmust designate the server as the Site Director. For more information, see Site Director.Figure 1 shows an example Metasys system configuration. The Metasys System ConfigurationExamples section shows a variety of configuration examples.

Figure 1: Example Metasys System Configuration

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

Metasys System Configuration Guide8

http://www.bacnetinternational.net/btl/index.php?m=15

General Purpose Application Controllers (CGMs) and VAV Box EquipmentControllers (CVMs)Starting at Metasys Release 10.0, a new family of equipment controllers is available. The first twomodels of this new, modernized family are the M4-CGM and the M4-CVM equipment controllers.

Figure 2: General Purpose Application Controller(CGM) and VAV Box Equipment Controller (CVM)

The following table describes the new equipment controllers in detail.Table 1: New Equipment Controllers at Release 10.0

M4-CGM09090-0 M4-CVM03050-0 M4-CVM03050-0P

Description General PurposeApplication Controller

VAV Box Controller VAV Box Controller withposition feedback

Inputs/Outputs • 18 total inputs andoutputs: 7 UI, 2 BI, 4CO, 2 AO, and 3 BO

• Supports SA Busexpansion

• 8 total inputs andoutputs: 3 UI, 2 CO,and 3 BO

• Integral actuator• Integral DPT• Supports SA Bus

expansion

• 8 total inputs andoutputs: 3 UI, 2 CO,and 3 BO

• Integral actuator• Integral DPT• Integral

potentiometer tosense actual VAV boxdamper position

• Supports SA Busexpansion

Field Bus Networkingand Tools

• BACnet MS/TP• N2• ZigBee for ZFR Pro

Wireless Field Bus(add-on modules)

• CCT 13, ReleaseMode 10.4








Table 1: New Equipment Controllers at Release 10.0

M4-CGM09090-0 M4-CVM03050-0 M4-CVM03050-0P

Firmware packagefiles

New Metasys field controller firmware package files for CCT (MS-FCP-0)are available for the latest field controllers from the central installationserver that allow Johnson Controls employees, channel partners, andend customers to source and license the use of their field controllerpackages.

Table 2: New Equipment Controllers features and benefits

Feature Description BenefitsNew packaging and styling New equipment controller

models are packaged in blackenclosures with roundedcorners.

Provides a modern,aesthetically pleasing industrialdesign.

Removable screw terminalblocks

Pluggable input/output wiringterminal blocks that can beremoved from the controller.

Provides electrical installersand field technicians the abilityto quickly and easily install andservice a controller withoutthe need to disconnect andreconnect the input/outputwiring.

Decimal MS/TP address setwith three rotary switches

Three rotary switches are usedto set the MS/TP address in adecimal format (x100, x10, x1).

Easy-to-use rotary switches setthe MS/TP address in decimalformat.

High memory capacity andfast processing power

New 16MB flash memory(formerly 640KB-2MB); new8MB SRAM/DRAM memory(formerly 128KB-1MB); new 120MHz processor speed (formerly32 MHz)

Provides application engineerswith more horsepower to meetmore sophisticated controlrequirements.

Background transfer Enables downloading offirmware and controllerapplication files that canbe applied at a later,predetermined time and inthe background while fieldcontrollers are still operating.This can be done on multiplecontrollers at the same timefor further efficiency. Oncefirmware and controllerapplication files are applied,you can decide when to enablethe logic of applications in adevice using the Enable Logic/Disable Logic options in CCT.

Saves field technicians’time, enables productivityand minimizes equipmentdisruption, since the controllersare operating while file updatestake place in the backgroundand the application can be leftdisabled until the system isready to run.



Feature Description BenefitsImproved SA Buscommissioning

Enables a field controller totransfer and apply firmwarefiles to all the SA Bus IOMdevices connected to it at thesame time.

Saves field technicians timewhen commissioning SA BusIOM devices.

Common release mode CCT programming andcommissioning for new andrecently-released controllermodels can be performed inthe same CCT release mode.

• Improves the productivityof controls technicians andreduces their frustrationsby mitigating the need toswitch between multiple CCTrelease modes.

• Provides configurationconsistency, simplicity,and efficiency through CCTduring configuration andcommissioning.

BACnet MS/TP support New controller modelshave been BTL-listed atProtocol Revision 15 asBACnet Advanced ApplicationControllers (B-AAC).

Ensures openness andinteroperability with otherBACnet devices and systems.

Wireless ZFR and ZFR Prosupport

Provides wireless connectivitybetween field controllers andnetwork engines over the FieldController (FC) bus.

• Provides a wirelessalternative to hard-wiredMS/TP networking, offeringapplication flexibility andmobility with minimaldisruption to buildingoccupants.

• Simplifies and speeds upreplacements.

N2 support Enables a field controller tobe installed in an existing N2-based system.

Provides a cost-effectivemigration path for customerswith legacy, N2-based offeringswith a single controller model(rather than multiple modelsfor BACnet MS/TP and N2support).

Auto-detection ofcommunication protocol

Controller auto-detects theprotocol that is connected to it.

Enables the same controllerto support multiplecommunication protocolswithout the need to purchase aspecial model per protocol, andwithout extra manual setup.



Feature Description BenefitsOptional integrated feedbackpotentiometer on VAVcontroller

Provides feedback of the VAVbox damper’s actual position.

Reassures users and fieldtechnicians of the VAV boxdamper’s actual position andenables them to easily confirmand troubleshoot VAV controlleroperations, confirm that theactuator is at the desiredposition, and track the damperposition.

Advanced Application Field Equipment Controller (FAC)FAC Series Controllers support selectable BACnet or N2 field bus networking protocols. FAC SeriesControllers feature an integral real-time clock and support time-based tasks, which lets thesefield controllers monitor and control schedules, calendars, alarms, and trends. FACs can continuetime-based control and monitoring when offline for extended periods of time from a Metasyssystem network. FAC Series Controllers can also operate as stand-alone controllers in applicationsthat do not require a network engine or for network applications where it is preferred to havethe scheduling, alarming, and trending performed locally in the field controllers. The FAC2612controller features line-voltage relay outputs, making this controller well suited for use in terminalunits. The FAC2612-2 model uses a line-voltage power supply, eliminating the need for a 24 VACtransformer in line-voltage applications. A full range of FAC and FEC models combined with IOMmodels can apply to a wide variety of mechanical and electrical equipment control applicationsranging from simple fan coil or heat pump control to advanced central plant management.The FAC3611-0 and FAC3613-0 models include a fast persistence feature that facilitates data valuesto be held at a configurable value, up to once per second. Persistence refers to how often samplesof data are stored locally. The fast persistence feature ensures that in the event of a problem,such as a loss of power, you can retrieve up to the rate that the data is persisted, minimizingthe potential loss of data. When power is restored, previously persisted data, up to the rate ofpersistence, is still available and accessible. In the case of persistence configured for once persecond, you risk losing only one second of data. Persisting data is essential for situations thatrequire greater data accuracy and may include certain methods of utility data collection and billing.Attributes you can persist in the FAC3611-0 and FAC3613-0 include Counter Input Present ValueAttributes, Binary Input, Binary Output, Binary Value COS Counts, Active Time Attributes, and PID/PRAC tuning parameters.

Some controller models operate on BACnet/IP networks and integrate into Johnson Controls' andthird-party systems. For example, the FAC4911 BACnet/IP model is BTL-listed as an AdvancedApplication Controller. This model has an integral real-time clock for scheduling, alarming andtrending, 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 FAC4911and IP VMA1930 controllers, which are connected by Cisco® technology. The controllers can beconfigured in a ring network and continue to communicate even if one controller or networksegment within the ring network stops communicating. This provides network reliability bymitigating a single point of failure in the IP/Ethernet network wiring.

Field Equipment Controllers (FEC)FEC Series products support selectable BACnet or N2 field bus networking protocols. The FECfamily includes multiple models featuring a variety of total number and types of input and outputinterfaces. FECs feature 32-bit microprocessor architecture, patented continuous tuning adaptivecontrol, and peer-to-peer communications, and they are available with an optional built-in LCDscreen local UI. A full range of FEC models combined with IOM models can apply to a wide varietyof mechanical and electrical equipment control applications ranging from simple fan coil or heat


pump control to advanced central plant management. The FEC Series controllers support wirelesscommunications using the ZigBee® Field Router (ZFR) Series accessories.

FEC Field Equipment Controller Family ComparisonTable 3: Field Equipment Controller Family Comparison

Field EquipmentControllers (FECs)

Advanced ApplicationField Equipment

Controllers (FACs)

Variable AirVolume Modular

Assemblies (VMAs)Typical Applications Controlling:

• Rooftop Units• Heat Pumps• Unit Ventilators• Air Handling

Equipment• Central Plant

Equipment• Exhaust Fans• Supplemental

HeatingEquipment

Controlling:

• Equipment that requireslocal scheduling, alarming,and trending

• Air Handling Equipment• Central Plant Equipment

Controlling:• Pressure

independent VAVboxes

• Pressuredependent VAVboxes

• Zone Dampers

Processor 32-bit 32-bit 32-bitOnboard Real TimeClock

No Yes Yes - on IP VMA1930model only

CommunicationProtocol

• BACnet MS/TP (B-ASC) or N2 (fieldswitchable)

• ZigBee Wireless(with an add-onmodule)

• BACnet MS/TP (B-AAC) orN2 (field switchable)

• BACnet/IP (B-AAC) (modelIP FAC4911 only)

• ZigBee Wireless (with anadd-on module)

• BACnet MS/TP (B-ASC) or N2 (fieldswitchable)

• BACnet/IP (B-AAC): (model IPVMA1930 only)

• ZigBee Wireless(with an add-onmodule)

Expandable throughSA Bus

Yes Yes Yes

ProgrammableControl Logic

Yes Yes Yes

Programming Tool CCT CCT CCTCommissioning Tool CCT, MAP CCT, MAP CCT, MAP

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


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

Input/Output Module (IOM)The IOM Controllers are expansion input and output modules with integral RS-485 MS/TPcommunications. IOMs can serve in one of two capacities, depending on where they are installed inthe Metasys system. When installed on the SA Bus of a CGM, CVM, FAC, FEC, or VMA controller, theIOMs expand the point count of these controllers. When installed on the FC Bus, the IOMs supportmonitoring and control from an NAE or NCE as I/O point multiplexors. The point multiplexor canalso be useful for sharing points between other field controllers on the FC Bus using peer-to-peer connectivity. A full range of CGM, CVM, FAC, FEC and VMA models combined with the IOMmodels can be applied to a wide variety of mechanical and electrical equipment control applicationsranging from simple fan coil or heat pump control to advanced central plant management.


Wireless SolutionsSeveral wireless Metasys solutions are available for integrating wireless connectivity in desiredportions of a Metasys network. These solutions provide wireless communication betweencontrollers, thermostat controllers, coordinators, routers, and room sensors.

• ZFR181x Series Wireless Field Bus System

• WNC1800/ZFR182x Pro Series Wireless Field Bus with Wireless TEC3000 Series Thermostats

• WRS Series Many-to-One Wireless Room Temperature Sensing System

• WRZ-7860 One-to-One Wireless Room Temperature Sensing System

• TE-7800 Series One-to-One Wireless Room Temperature Sensing System

These wireless solutions reduce costs by minimizing wiring, provide application mobility andflexibility, and simplify the challenges of difficult or cost-prohibitive installations or renovations. Thewireless solutions can coexist with each other, and with hard-wired Metasys solutions.

Controller Configuration Tool (CCT)You use the Controller Configuration Tool (CCT) to configure, simulate, commission, and transferapplication files to the following controllers on a BACnet MS/TP bus:

• Field Equipment Controllers (FECs)

• Advanced Application Field Equipment Controllers (FACs)

• Input/Output Modules (IOMs)

• General Purpose Application Controllers (CGMs)

• Variable Air Volume Box Equipment Controllers (CVMs)

• Variable Air Volume Controllers (VAVs)

• Variable Air Volume Modular Assembly Controllers (VMAs)

CCT operates in three modes that provide key functionality for your system:

• Use the Configuration mode to select a wide variety of mechanical and control logic optionsthrough system selection trees for typical air handling, terminal unit, central plant, and VAVbox mechanical systems. When required, you can customize the standard logic provided by thesystem selection process to meet your specialized control logic requirements.

• Use the Simulation mode to review the application logic as if you were commissioning thesystem. You can make adjustments to setpoints, inputs, or sensors during a simulation sessionto validate the logic before assigning the configuration to a specific controller. A simulationdebugging console is also available to set up break points that pause the simulation sessionbased on criteria that you set up. While viewing a simulation session, transitions taking place inthe 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. Youcan use this mode to monitor your device and set Offsets, COVs, and Polarity in addition to otherparameter and detail changes.

For VAV applications, CCT includes an optional box flow test to automatically exercise all the VAVboxes to ensure correct mechanical installation and proper configuration of the key flow setupparameters.


The ZFR Checkout Tool (ZCT) is available to validate the wireless connectivity and health of yourwireless mesh network. Refer to the ZFR Checkout Tool Help (LIT-12012292) for details.Controller Application Files (CAFs) can be transferred and commissioned to a device through a widevariety of connection interfaces including: NxE Passthru, MAP 4.2+ / BACnet router, ZigBee, andDirect Ethernet.CCT and the Facility Explorer® Programmable Controller Tool (FX-PCT) are no longer separatesoftware tools. Users of CCT and FX-PCT at Release 10.2 must first uninstall the previous versionbefore installing Release 13.0. Users of CCT and FX-PCT software at Release 10.3 can upgradedirectly to Release 13.0. For information on how to upgrade to or install CCT, refer to the CCTInstallation Instructions (LIT-12011529).For a list of updated features and benefits available at CCT Release 13.0, refer to the ControllerConfiguration Tool (CCT) Catalog Page (LIT-1900386).

TEC3x00 Series Networked Thermostat ControllersThe TEC3x00 Series Thermostat Controllers are configurable, application-specific controllers withembedded sensors. TEC3x00s are housed in enclosures suitable for mounting on a wall in anoccupied space, and each model features an intuitive user interface with backlit display that makessetup and operation quick and easy.

Depending on the model and configuration options you select, TEC3x00s provide on/off, floating,and proportional control of:

• local hydronic reheat valves

• pressure-dependent VAV equipment with or without local reheat

• two- or four-pipe fan coils

• cabinet unit heaters

• other zoning equipment using an on/off, floating, or 0 to 10 VDC proportional control input

• single- or two-stage unitary rooftop units (RTUs) and heat pumps, with or without economizers

The TEC3600 series models feature field-selectable BACnet MS/TP or N2 communication capability,enabling supervisory control from a Metasys network engine or communication to third-partyBAS devices. The TEC3000 series models feature ZFRPro compatible wireless communicationcapabilities, enabling supervisory control from a Metasys network engine through a WirelessNetwork coordinator.

Network EnginesNetwork engines perform a key role in the Metasys system architecture. These network enginesprovide network management and system-wide control coordination over one or more networks ofequipment controllers, including the following Metasys field controllers:


• General Purpose Application MS/TP Controllers (CGMs)

• VAV Box Equipment MS/TP Controllers (CVMs)

• Field Equipment Controllers (FECs) and Advanced Application Field Equipment Controllers (FACs)

• Variable Air Volume Modular Assembly (VMA) Controllers

• Terminal Equipment Controllers (TECs)

• LN series equipment controllers

• Legacy Metasys controllers, such as Unitary (UNT) controllers, Variable Air Volume Assembly(VMA14xx) controllers, and DX-9100 controllers

• Third-party equipment controllers

The network engines can be networked together for scaling up on large projects, and they can benetworked with an ADS or an ADX for additional functionality and site unification.Network engines provide building control scheduling, alarm and event management, energymanagement, data exchange, historical data storage and management, and custom controllogic. 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 permissionaccess control as well as IT security best practices.In addition to providing general comprehensive equipment monitoring and control, networkengines also offer specialized capabilities by series, model, and software release to meet a varietyof application requirements. The network engines are identified by three types:Small-capacity engines

• Network Automation Engines: NAE35 and NAE45

• Network Control Engine: NCE25

• Network Integration Engines: NIE29, NIE39, and NIE49

Large-capacity engines

• Network Automation Engine: NAE55

• Network Integration Engines: NIE55 and NIE59

Software-only engines

• Network Automation Engine: NAE85

• Network Integration Engine: NIE85 and NIE89

NAEs provide network supervisor capabilities and IP network connectivity. NCEs also providenetwork supervisor capabilities and IP network connectivity, but also feature the I/O pointconnectivity and direct digital control capabilities of an FEC. NIEs are variants of NAEs and NCEs thatinclude legacy and third-party device integration capabilities.

NAEThe NAE is available in many different models with options to support various communicationsprotocols 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 TycoC•CURE 9000/victor is also included. The following models are available:

• The NAE55 Series supports a comprehensive set of supervisory control features and functions forlarge facilities and technically advanced buildings and complexes.


• The NAE-S (MS-NAE551S-x) is a secure NAE55 with increased security features—embeddedencryption technology under a securely fastened enclosure to protect and secure the buildingmanagement system at the endpoint. The engine meets the Federal Information ProcessingStandard (FIPS 140-2), Security Level 2, that specifies the use of a cryptographic module and atamper-proof housing.

• The NAE35 and NAE45 Series extend the power of the NAE to the smaller buildings (or smallareas of larger buildings) and enable the wider distribution of supervisory control functions inlarger facilities.

• The NAE45-Lite, available only in specific markets, is a functionally limited NAE45 that you cannotuse 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.

NCEThe NCE provides support for the same communications protocols as the NAE, but also offersthe Input/Output (I/O) point connectivity and direct digital control capabilities of a Metasys FieldEquipment Controller (FEC). The NCE provides a cost-effective solution designed for centralplants and large built-up air handler applications. All NCE models provide IP Ethernet networkconnectivity, the Site Management Portal UI, and the network supervisory control functionsfeatured on network automation engines. Depending on the model and software release, an NCEsupports either a BACnet MS/TP Bus, an N2 Bus, or a LonWorks network trunk. Built-in support forthird-party protocols, including Modbus, M-Bus, KNX, and Tyco C•CURE 9000/victor, is also included.

NIE55/NIE85The NIE55/NIE85 are specialized versions of the NAE and are designed to provide for the migrationof existing N1 networks into the current generation Metasys system. These models are onlyavailable at Metasys Release 9.0 or earlier. The NIE55/NIE85 provided the same Site ManagementPortal UI as the NAE. Unlike the NAE, the NIE55/NIE85 does not support integration of BACnet MS/TP or BACnet/IP, N2, or LonWorks networks. Two models of the NIE55/NIE85 are available. TheNIE55 supports smaller N1 networks, whereas the NIE85 supports large N1 integrations.

NIEx9The NIEx9 is a specialized version of the NAE and is designed for integration of building controldevices that communicate over the MODBUS®, MBus, KNX, or Tyco C•CURE 9000/victor protocol.The NIEx9 also communicates over the BACnet MS/TP, BACnet/IP, N2, or LonWorks networks.This specialized version of the NIE is designed to provide for the migration of these existing third-party networks into the current generation Metasys system. The NIEx9 provides the same SiteManagement Portal UI as the NAE or NIE. The following models are available:

• NIE59 Series (Release 10.0) supports two integrations in addition to a BACnet MS/TP, BACnet/IP, N2, or LonWorks network for use at large facilities and technically advanced buildings andcomplexes.

• NIE39 and NIE49 Series (Release 9.0.7) extends the integration power of the NIE to the smallerbuildings (or small areas of larger buildings) and enables the wider distribution of integrationfunctions in larger facilities. These engines support two integration integrations in addition to aBACnet MS/TP, BACnet/IP, N2, or LonWorks network.

• NIE29 Series (Release 9.0.7) combines the network integration capabilities of an NIEx9 with theInput/Output (I/O) point connectivity and direct digital control capabilities of a Metasys FieldEquipment Controller (FEC). These engines support two integration integrations in addition to aBACnet MS/TP, BACnet/IP, N2, or LonWorks network.


• NIE89 (Release 9.0.7) provides a computer-based version of the NIE59 that supports largeintegrations. This engine supports eight total integration integrations in combinations of four(for example, four Modbus TCP and four KNX TCP).

Network Engine ComparisonTable 4: Network Engine Release support comparison

Model Release 9.0 Release 9.0.7 Release 10.0NCE25 X X1

NAE35, NAE45 X X2

NAE55 X X3

NAE85 X X

NIE29, NIE39, NIE49 X X4

NIE59 X X5

NIE89 X

NIE55, NIE85 X

1 Only NCE25xx-0 is available to upgrade to Metasys 9.0.7 with Linux OS.2 Only NAE35xx-2 and NAE45xx-2 are available to upgrade to Metasys 9.0.7 with Linux OS.3 Only NAE55xx-2 and NAE55xx-3 are available to upgrade to Metasys 10.0 with Linux OS.4 Only NIE29xx-0s, NIE39xx-2, and NIE49xx-2 are available to upgrade to Metasys 9.0.7 with Linux OS.5 Only NIE59xx-2 and NIE59xx-3 are available to upgrade to Metasys 10.0 with Linux OS.

Important: All NIEx9 models, with the exception of the NIE59 model, are no longer offeredat Metasys system Release 10.0 because NAEs at Release 10.0 now include the integrationfunctionality from Release 9.0.x.

Table 5: Network Engine integrations available by Metasys Release

Integration Release 9.0 Release 9.0.7 Release 10.0BACnet/IP X X XBACnet MS/TP X X XLegacy N1 LAN X

Legacy N2 Bus X X XLonWorks X X

Modbus RTU and TCP X X XM-Bus Serial and IP X X XKNX IP X X XC·CURE 9000 and victor X

Simplex Fire (secondary monitoring only) X

Preferred Vendor Lighting Systems X


ServersADS and ADS-LiteThe 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 databasemanagement system using a supported edition of Microsoft SQL Server® Express software tostore collected trend data, audit trail messages, and alarm and event messages with operatorannotations. The second component is the web server software that provides SMP UI and MetasysUI 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 limitationsto other Metasys devices such as ADSs and engines.

Server ComparisonTable 6: Application and Data Server Family Comparison

Feature Application and Data Server (ADS) Extended Application and DataServer (ADX)

Host Platform Desktop computer platform:

• Microsoft Windows® operatingsystem

• Microsoft SQL Server Expressdatabase

• Open Database Connectivity (ODBC)compliant database package

Server platform:

• Microsoft® Windows Server®operating system

• Microsoft SQL Server database

SupportedSimultaneousUsers

Up to 5 users Up to 10, 25, 50, or 100 users (licensespecific)

Network EngineManagement

Up to 14 engines Up to 1,000 engines (support forengines varies depending on size ofserver hardware)

Archival ofHistorical Data

Manual, scheduled, or automatic Manual, scheduled, or automatic

User Interface Metasys UI

SMP

Metasys UI

SMPSupports ExportUtility

Yes Yes

Supports MetasysAdvancedReporting

No Yes


Table 6: Application and Data Server Family Comparison

Feature Application and Data Server (ADS) Extended Application and DataServer (ADX)

Supports EnergyEssentials

No Yes

Support for SplitConfiguration

No Yes

Supports Metasysfor ValidatedEnvironments(MVE)

No Yes

Five Years ofHistorical Data

Metasys UI Metasys UI

For more information, refer to the Application and Data Server (ADS) and Extended Application andData Server (ADX) Product Bulletin (LIT-1201525).

ADXThe ADX is a version of the ADS with extended capabilities for historical data archiving that expandthe multi-user web access capabilities of the system. The ADX supports the relational databasemanagement system that uses a supported edition of Microsoft SQL Server software to storecollected 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 trendconfiguration 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 aggregatetrend data at a summary or detailed level. An ADX can also support the optional Energy Essentialsreporting 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 onecomputer, it is known as a Unified ADX. If the SQL Server software is located on a differentcomputer, it is set up as a Split ADX.You can install the ADX in a split configuration with the ADX software/SMP UI/Metasys UI on onecomputer (the web/application server computer) and the historical trend, audit, and event dataon another computer (the database server) running Microsoft SQL Server software. The SystemConfiguration Tool (SCT) software, which is used to generate, back up, and restore the networkdatabase offline, is installed on a separate computer in split configuration. The Metasys AdvancedReporting System is also available in a split configuration, if the SQL Server database componentsare installed on the database server and the SQL Server Reporting Services are installed on theweb/application server. In a split configuration, you can place your database server behind afirewall for an added layer of data protection.

Supported Concurrent Users

ADS/ADX concurrent usersThe following table shows examples of the total number of supported users who can besimultaneously logged in to the SMP and Metasys UI.


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

Examples of ADS/ADX concurrent usersADS/ADX typeSMP UI Metasys UI0 52 3

5-user ADS/ADS-Lite

5 00 255 208 17

10-user ADX

10 150 2510 1520 5

25-user ADX

25 00 5010 4025 25

50-user ADX

50 05 5010 5025 5050 5075 25

100-user ADX

100 0

For example, as shown in Table 7, with a 5-user ADS or ADS-Lite, 5 Metasys UI users are supportedif 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 10Metasys UI users are supported if 40 SMP users are logged in. The only Metasys UI user restrictionapplies to a 50-user or 100-user ADX: no more than 50 Metasys UI users are supported, regardlessof the number of SMP users.

ODSImportant: ODS is supported at Release 9.0 but not upgradable to Release 10.0.

The Metasys Open Data Server (ODS) is a BACnet Testing Laboratories® (BTL) Listed BACnet®Operator Workstation (OWS). It conforms to the B-OWS profile. The ODS supports up to 25,000 localobjects and up to five users. You can configure the ODS as a BACnet Workstation, as a Site ManagerWorkstation, or as a Combined Workstation.In the BACnet Workstation configuration, the ODS uses the BACnet protocol to communicatewith 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 sameas BACnet devices. This configuration is best for the customer who requires a BACnet operatorworkstation using standard BACnet messages. BACnet features are emphasized, and viewableobject capacity is limited to 25,000 objects.In the Site Manager Workstation configuration, the ODS acts similarly to an Application and DataServer/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 throughthe NxE using BACnet integration. The Site Manager Workstation configuration is best whenfeatures and capability (for example, object capacity and performance) are more important tothe customer than strict use of standard BACnet services. The ODS provides all advanced Metasyssystem features, and the viewable object capacity includes all of the objects from all of the networkengines reporting to the Site Manager Workstation. In this configuration, the ODS can serve as theSite Director for up to 100 NxE network engines. In addition, you can connect Johnson Controls® IPcontrollers, Johnson Controls MS/TP controllers, and BACnet MS/TP devices over a remote field buswith the use of a BACnet/IP-to-MSTP router.In the combined configuration of BACnet Workstation and Site Manager Workstation, the strengthsof both configurations are combined to deliver an optimal solution to the customer. NxE networkengines 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 candirectly access BACnet devices and FEC-family devices using the BACnet integration capability of theODS. This configuration is best for the customer who values features and capability, and also needsthe functionality of a BACnet operator workstation for BACnet devices not associated with a Metasysengine. In this way, operator monitoring and control is extended to BACnet devices outside of thecontrol of a Metasys engine.Table 8 lists which Metasys products are compatible with the ODS Workstation.Table 8: Metasys Products Compatible with ODS

Metasys Product or Feature ODS CompatibilityAdvanced Graphics Application (AGA) Not SupportedController Configuration Tool (CCT) SupportedEnergy Essentials SupportedFECs, FACs, IOMs SupportedGraphics+ (GGT) SupportedMetasys Advanced Reporting System SupportedMetasys Database Manager SupportedMetasys Export Utility (MEU) SupportedMetasys for Validated Environments (MVE) Not SupportedMetasys UI Not SupportedNxE Engines SupportedODS Split Configuration Not SupportedStandard Graphics (UGT) SupportedSystem Configuration Tool (SCT) SupportedZFR Wireless Network Not Supported

LCSThe LCS85 is a computer-based server that is used to communicate with LonWorks devicesover an IP network. The LonWorks field devices are normally connected to an IP router. In thisarrangement, the Metasys system is used in a flat LonWorks configuration.

User InterfaceTwo 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 thecomplete 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 featuresideal for efficient building operations, including:

• views of all equipment serving a space or another piece of equipment

• a single view of all items in alarm, warning, overridden, out of service, and offline states within aspace

• a single view to understand the correlation between disparate events within the system

• trends of historical equipment data for up to 10 points (computer platform) and four points(tablet and phone platforms) at a time, on up to three different charts at once

• views of all relationships a piece of equipment has with other equipment, spaces, and networkfield 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 additionalspaces

• viewing and managing alarms by space and equipment

• viewing alarms while not logged in (Alarm Monitor)

• commanding and modifying points relating to spaces and equipment in bulk

• a single view to determine what command priority is currently active on a point object

• viewing and editing space and equipment schedules

• creating, editing, and managing Metasys UI graphics

• importing and exporting custom symbols with the Custom Symbol Library

• managing legacy graphic associations with spaces and equipment

• smart filtering by launching directly from certain widgets into a pre-populated Advanced Search

• scheduling reports that are regularly emailed to you

• tracking the ways users interact with the Metasys software with Usage Analytics

The Metasys SMP provides real-time and historical data views, extensive alarm managementcapabilities, and system configuration functions for system administrators or dedicated buildingoperators. The SMP transforms the raw data from the site and organizes it into a comprehensiveset of information management tools and reports. You can access this portal using the Launcherthrough an Internet or intranet connection to a Metasys server or engine. The SMP has all thefeatures one expects from a traditional workstation, including:

• pop-up alarm windows

• navigation tree—you can create multiple custom trees to best represent the logical layout of thefacility

• dynamic graphics of systems and floor plans that you can zoom in on to show fine details

• multiple display areas you can size and control individually

• global search function and sorting capability that help you find system information withinseconds

• the entire user manual available in the Help system


Information Management is an inherent capability of the overall user experience and reportingcapabilities. Whether you are logged in to the SMP UI running online reports, using the MetasysAdvanced Reporting System, or retrieving data from an engine with the Export Utility, you aretransforming the data collected by the system into information you can use to manage your site.

ToolsLauncherThe Launcher is a software application that lets you use the SMP or SCT to access the Metasyssystem, server or network engine on the building network, regardless of its software version. Keyfeatures of the Launcher include:

• Installation of a separate folder to store the Metasys release software on your hard disk. Thispractice provides for an isolated, private version of the Java® Runtime Engine (also referred to asJava Runtime Environment [JRE] ) required to run Metasys software. If you have installed multiplereleases of Metasys software, a separate folder is created for each. The JRE folder separationstrategy allows for independence from the public Java Runtime Engine.

• Support for launching any version of the SMP, ODS, and SCT UIs. Supported site directors includethe ADS, ADX, ODS, NAE, NIE, and NCE.

Note: For Release 5.2 or earlier, the specific Java Runtime Environment particular to the SMPor SCT software release is still required on the client computer.

Note: ODS is not supported at Release 10.0.

• Support for launching any website, including Metasys software products, such as Metasys UI,Metasys UI Offline, SCT Pro, and the Metasys Advanced Reporting System, as well as popularwebsites such as the Google® website.

• Option for restricting communication with only secure Metasys servers and network engines.

Contact your local Johnson Controls® representative for access to the Launcher software.

System Configuration Tool (SCT)The System Configuration Tool (SCT) supports the engineering, installation, and commissioning ofyour building automation system. The SCT application enables offline generation of the completesite and user interface creation of the system, including point naming; integration of N1, N2,BACnet, and LonWorks networks; integration of Modbus, M-Bus, and KNX third-party protocols;integration of building systems such as C·CURE 9000 access control, victor video management,Simplex fire, and connected lighting systems from preferred vendors; integration of local andremote MS/TP devices; definition of tailored summaries and user views; and the creation of customcontrol logic using a graphical user interface.SCT also manages the maintenance of the archive database for the Network Automation Engine(NAE), Network Control Engine (NCE), Network Integration Engine (NIE), Application and DataServer/Extended Application and Data Server (ADS/ADX), Open Data Server (ODS), and Metasys UserInterface (UI). To keep the archive database current, the user can set up the SCT to schedule regularuploads from the devices on the site. When the system is operational, you can make online changesto the database at the engine, ADS/ADX, or ODS with the same user interface that was used for theoffline data generation in SCT.SCT offers productivity features, such as the mass creation of equipment, spaces, and servingrelationships, and the migration of supervisory devices. You can also use SCT to fully manage amixed release site for a Metasys system at Release 5.2 or later.SCT has a one-click installation. The new SCT installers install the required software prerequisites,such as Internet Information Services (IIS), SQL Server 2014 Express software (if no SQL Serverpresent), and Microsoft .NET Framework 4.6.1.


The new SCT installers also include two additional applications. You can use the Metasys UI Offlinesoftware to configure Metasys UI graphics and the display of data without a live connection todevices. SCT Pro is a web application that significantly streamlines some SCT workflows, and greatlysimplifies tasks such as scheduling recurring backups, upgrading sites, and site discovery. Forexample, with site discovery, you can rebuild the entire archive database from the online system.This is a useful option if the original archive is missing, corrupt, or was never maintained.Metasys uses secure HTTP with Transport Layer Security (TLS) 1.2 between the SCT computer, allMetasys servers, and network engines that are upgraded to Metasys Release 9.0 and later. Theencrypted HTTPS communications apply to the ADS, ADX, ODS, Metasys UI, network engines, andSCT. This ensures that unauthorized users and computer hackers cannot view the contents ofcommunications sent between Metasys devices. By default, self-signed certificates are installed onsupported products, with the option of configuring trusted certificates configured by an internalIT department or a Certificate Authority. To indicate the active security level (trusted, self-signed,or untrusted), three small security shield icons appear on the SCT login screens and on the SCT UIscreens. Johnson Controls continues to enhance the security of Metasys with the addition of signedresource files, and the pairing of supervisory devices with the site director to ensure encryptedcommunication.For a list of updated features and benefits available at SCT Release 13.0, refer to the SystemConfiguration Tool Catalog Page (LIT-1900198).

System Configuration Tool Pro (SCT Pro)SCT Pro is the next generation interface for SCT. It provides significantly streamlined workflows,and greatly simplifies tasks that were previously time consuming or cumbersome. For example, youcan use SCT Pro to maintain healthy backup practices for a site, such as setting up backups to occurautomatically on a recurring schedule. SCT Pro does not include the full range of features that areavailable in SCT, but new features will be added over time; and SCT remains available for the tasksthat SCT Pro does not yet support. SCT Pro is installed during the installation of SCT Release 13.0and later.Use SCT Pro to complete any of the following tasks:

• Provision a new Network Engine

• Upload and download a site

• Perform a backup of a site

• Schedule automatic recurring backups

• Restore a site from a backup

• Upgrade a device

You can launch the new HTML user interface from SCT or from a URL on any client device type(workstation, tablet, or phone).For more information about SCT Pro, refer to SCT Pro Help (LIT-12013035).

Metasys Database ManagerThe Metasys Database Manager provides both database management and database monitoringfunctions, handled in two separate windows. Database management includes summarizedinformation on and methods for backing up, purging, and restoring Metasys system trend, alarm(event), and audit databases. An ADS Rename function is also available that is most useful if you aremoving Metasys databases to a new computer. Monitoring includes an indication of database statuscompared to three levels of defined database sizes.


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

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

Metasys System CapabilitiesSite DirectorWhen users access any engine or server directly through a web browser, only the information localto that device is accessible. To make all information in the facility accessible from a single point,the Metasys system uses a Site Director. The Site Director is the device designated to maintainthe site information, including the logical organization of data about your facility, user passwordadministrative information, and overall master time and date. This function resides in an engineor, on large installations, a server. For networks that do not have a server, one of the engines isdesignated as the Site Director. When one or more servers are part of the network, one server mustbe designated as the Site Director. The Site Director provides a uniform point of entry and supportsfunctions such as user login, user administration, time synchronization, and traffic management.Consider a server as the Site Director if you require:

• support of multiple international languages

• repository for trend and alarm data and operator transactions, along with annotations for MVEsystems

• a greater number of simultaneous users than an engine allows

Time ManagementThe 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 timeand date consistently for all system operations. Because the Site Director is the master time keeperfor all engines and servers on a single site, all of these devices are assumed to use the same timezone for all time-rated functions.For network-wide time synchronization, the engine or server acting as Site Director is the timeserver for the entire site. All other devices are time clients because they receive the time fromthe Site Director. The Site Director can be configured to use three different methods of timesynchronization: Unicast Simple Network Time Protocol (SNTP) (also known as Microsoft Windowstime synch), Multicast SNTP, or BACnet time synch. The Site Director can also be configured to synchits time from an external website.New multi-time zone enhancements allow you to schedule events using local machine timemanagement instead of calculating the Site Director time in relation to the device hosted in adifferent time zone.


System NavigationThe Metasys UI supports navigation in the form of spaces and equipment relationships. A space isthe physical location or area that is served by a piece of equipment. Equipment is the broad termused to describe the physical controllers and devices that make your building run. These controllersand devices include boilers, chillers, air handling units, lights, meters, security, and anything elseused 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 relationshipbetween them in SCT.The Building Network tree in Metasys UI provides access to objects using an alternative navigationtree to the Spaces tree. The Building Network organizes objects according to the Metasys objecthierarchy, similar to the All Items tree in the SMP. The Building Network tree supports the Detailwidget, which supports the Focus view, Network view, and Diagnostic view, the Summary viewwidget, 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 GlobalStatus indicators.

Note: The Building Network tree order is inherited from the SMP All Items tree with minorexceptions. 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 AllItems 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. AMetasys system administrator can limit a user’s access to the Metasys system by creating User Viewsand assigning them to specific users. User Views provide organizational structure and data filteringfor the information displayed in the Metasys Advanced Reporting System UI.

Monitoring and CommandingMonitoring and commanding allows you to efficiently navigate through items associated with yourbuilding operations as well as view, analyze, and modify these items. After creating items withwizards, use these features to:

• access, view, and modify item data

• send commands to items

• run reports to analyze item information

PreferencesThe Metasys system provides customized preferences for the Metasys user interfaces. Thepreferences allow you to configure how the user interfaces behave, including the sounds andcolors, the startup views, alarm priorities, and links from within the user interfaces to externalapplications. 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 performanceand operation of the system. User preferences apply to a specific Metasys system user and definehow information is displayed in the user interfaces. User preferences do not affect the operation ofthe system.At Metasys Release 8.0 and SCT Release 11.0 and later, user preferences are stored in archives. Youno longer need to reconfigure your settings or object lists after upgrading or updating.

Alarm and Event ManagementThe alarm and event feature provides event management for the system. Users can configure therouting of event messages to destinations such as the server for permanent storage. The MetasysSite Management Portal UI features a pop-up alarms window, which alerts the operator to potentialproblems whenever the operator is logged in to the system; and an event viewer, which providesfor greater analysis or a history of alarms and events in the system.


Note: To ensure proper pop-up alarm functionality, always use the Desktop mode for Windows10, Windows 8.1, or Windows Server® 2012 R2 computer.

Users can configure alarms and events with the Metasys system, using either a Metasys alarmextension or a BACnet alarm (intrinsic or algorithmic). Metasys alarm extensions generallyprovide more feature capability and ease of setup, whereas the BACnet alarms provide betterinteroperability with other BACnet systems.Users can also view and take action on alarms that occur in the Metasys system with the AlarmManager and the Alarm Monitor in the Metasys UI. The Alarm Manager and Alarm Monitor displayall alarms pending acknowledgment and discarding. Users can access the Alarm Manager whenthey are logged in to the Metasys UI, and they can access the Alarm Monitor when they are notlogged in to the Metasys UI. Users can access both the Alarm Manager and the Alarm Monitoron computer and tablet platforms. To manage alarms on phone platforms, users can access theMetasys UI Alarms list. The Alarms list displays alarms that have occurred for points mapped andunmapped to Metasys UI equipment. You can see the top 100 alarms in the Alarms list. The listedalarms include the latest occurrences, and alarms that were acknowledged, as indicated by a greentick mark.The Equipment Activity widget in the Metasys UI also displays alarms and user changes madeduring a time range of up to one year within the last five years for a selected piece of equipment.

Note: An event is a notification of a status change in the Metasys system. An alarm occurswhen a value defined in an engine goes outside of a user-defined range, changes to a user-defined contact condition, or fails to respond to a command within a user-specified time.When an alarm occurs, an event is generated. Events can be generated by any Metasysplatform. For example, if the NAE detects that a network node is offline, it can generate anevent. If an error occurs in the server platform, an event can also be generated. Once an eventis generated, it is stored in an Event Repository file located on the device that generated theevent. Users can retrieve and examine events stored in the Event Repository.

Encrypted CommunicationBeginning at Release 8.1, all Metasys Server based devices (ADS, ADX, ODS, and NAE8500) andnetwork engines are installed with and operate in a secure mode using self-signed certificates.Self-signed certificates improve system security by providing a secure, encrypted connection tothe Metasys web server. All data on the network occurs over an https connection using TLS 1.2 thatcannot be read by a third-party application. When you use a self-signed certificate, the Metasysweb server is in effect saying, "don't worry, I am who I say I am. You can trust me." Employing self-signed certificates has no cost.If the customer wants a higher level of security, they can replace self-signed certificates thatare installed on the Metasys server and network engines with a certificate issued by a CertificateAuthority (CA). These trusted certificates can be generated by the customer's internal ITdepartment or be purchased from a CA such as Verisign or GoDaddy. When you use a trustedcertificate, the Metasys web server is in effect saying, "Trust me - the CA agrees I am who I say Iam."The steps for installing trusted certificates on a Metasys server are covered in the respectiveinstallation documents: Metasys Server Installation and Upgrade Instructions Wizard (LIT-12012162)or ODS Installation and Upgrade Instructions Wizard (LIT-12011945). The steps for installing trustedcertificates on network engines are described in Metasys SCT Help (LIT-12011964).When deploying certificates, keep the following in mind:

• The steps for setting up trusted certificates can be complicated. Ask the customer's ITdepartment for assistance.

• Secure and encrypted communication has the greatest importance between the Site Director anda client logging in to the Site Director from the Metasys SMP. In many cases, the most practicalchoice is to install a trusted certificate at the Site Director (ADS, ADX, or ODS) and a self-signedcertificates 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 andself-signed certificates on its child devices.

Important: ODS is supported at Release 9.0 but not upgradable to Release 10.0.

• The name of the network engine within the SCT archive and the subject common name (orhostname associated with certificate) within the certificate must match exactly for a certificate tobe imported and bound to IIS.

• Some certificate authorities may require the subject common name (or hostname associatedwith certificate) within the certificate to include a domain name. If you are implementingcertificate management on an existing Metasys system, adding a trusted certificate may requireyou to add a domain name to the original host name of a server or engine. This action requiresyou to rename all data in the Metasys historical databases. This renaming operation requiresintensive database operations that significantly prolong a system upgrade. Therefore, be sure toallocate extra time if you are renaming historical data as part of an upgrade to Metasys Release10.0.

Destination Delivery Agents (DDA)DDAs are the method used for routing and delivering Metasys alarm extension event messagesto destinations such as pagers, printers, email, and Network Management systems. The Metasyssystem uses an email DDA, Pager DDA, Syslog DDA, Printer DDA, and Simple Network ManagementProtocol (SNMP) DDA. The email DDA supports standard Simple Mail Transfer Protocol (SMTP), PostOffice Protocol (POP), and Internet Message Access Protocol (IMAP). The Metasys Server can use anyof these DDAs, but a network engine at Release 9.0.7 or later can only use the email DDA, SyslogDDA, and SNMP DDA.SNMP provides IP standard SNMP functionality in the Metasys system, enabling networkadministrators to manage Metasys network performance, find and resolve Metasys system-relatedissues, and plan for future growth of the Metasys system. SNMP functionality uses standard SNMPVersions 1, 2C, and 3 (excluding SNMP encryption and authentication support). The Metasys systemallows delivery of unsecured SNMP traps for Metasys alarm events from all engines and servers tothe facility owner’s Network Management System (NMS), and allows the NMS to execute SNMP Getsagainst engines. This version of SNMP support does not include the SNMP set commands.Johnson Controls has developed a downloadable custom dynamic Management InformationBase (MIB) that allows the NMS to monitor Metasys point objects, display attributes, and controlsequence objects. The MIB is constructed to accurately reflect the additions and deletions of objectsin the network engines as the changes occur. The custom MIB defines explicit traps and associatedattributes that align with Metasys alarm messages, making data correlation (parsing/sorting) at theNMS straightforward and seamless.

Syslog DDAThe Metasys system provides the optional capability of sending its configured audit log entriesand alarm notifications to an external, industry-standard Syslog server, conforming to Internetpublished RFC 3164. The Syslog option provides positive indication of each field possible in theMetasys 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 barsymbol (|), 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 sentimmediately to the configured Syslog server. You can apply forensic analysis on the consolidation ofall electronic audit and event information at the Syslog server.

RADIUS Server AccountsSimilar to the existing Active Directory service support, you can control access to the Metasyssystem with a Remote Authentication Dial-In User Service (RADIUS) server. When you select


RADIUS on the Metasys system log on screen, the RADIUS server authenticates your identity as anauthorized user of the system.RADIUS implementation in the Metasys system adheres to the following Internet RFCs:

• RFC 2865 - Remote Authentication Dial In User Service (RADIUS)

• RFC 2548 - Microsoft Vendor-specific RADIUS Attributes

• RFC 2759 - Microsoft PPP CHAP Extensions, Version 2

RADIUS implementation:

• does not import authorization; all system users, both local and non-local, are authorized throughuser configuration in the Metasys security database.

• is transparent at login time. Users do not independently select a domain. The user ID mustmatch 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 areunavailable or silently non-functional with RADIUS user accounts.

• requires a Metasys administrator to configure RADIUS users

When a user provides a non-local user name to the Metasys system for login, the controller passesthe user credentials to the configured RADIUS server for authentication. If the credentials are valid,the RADIUS server confirms access and authorizes the user to log in as specified in the Metasyssecurity database.

Encrypted EmailMetasys software features an email encryption capability that encrypts user names and passwordsas they are entered into the SMP UI. Embedded and server machines can thereby send emailsto email servers over a secure channel (secure socket layer [SSL]). The entire email payloadis encrypted, and allows Metasys software to communicate to email servers that require SSLconnections.Users can configure email encryption with no authentication required, including SMTPauthentication, and POP-Before-SMTP authentication.

SchedulingScheduling 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 tounoccupied mode for heating and cooling needs, and energy optimization. Each schedule consistsof 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 lengthand then return the schedule to its typical weekly schedule. Exceptions can include references toCalendars that can, for example, reflect a holiday schedule for the entire facility or show selectedtenant spaces in the building. Another view within the schedule, called Today’s Schedule, shows thecurrent 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 timezone. You can program schedules based on device time zones instead of converting the time tocorrelate to the Site Director's time zone.

Historical Data Management (Trend)Users can collect, store, and view historical samples of object data with the Metasys Historical DataManagement capability. With the information generated by this feature, you can manage energyusage, prove compliance to standards, and diagnose problems in your facility.


Each engine has a local buffer where it stores trend samples. Users can configure the size of thisbuffer, in a number of samples. If a server exists on the site, you can send the trend samples to itsdatabase. This database supports backup, restore, and archival of data to long-term storage. Youcan display trend data as a graph or table of values on the SMP UI. The Trend widget in the MetasysUI displays more recent historical data as a graph. Users can also copy trend data to the browsercomputer’s clipboard, and thereby transfer the data to spreadsheets, databases, and MicrosoftWord documents.The SMP UI makes it easier to detect system-level performance by displaying multiple trends ona single graph or table. You can either predefine multiple trends in a trend study or dynamicallyselect various point trends to display on a single graph using the Trend Viewer or the Trend widgetin the Metasys UI. The Site Management Portal UI also offers information on the rate of events, rateof samples, and number of samples that are lost. Refer to the Metasys SMP Help (LIT-1201793).

System SecurityUser accounts control user access to the Metasys system. An account defines which portions of theMetasys data a user can access (for example, all HVAC data or all lighting data from a particulararea of the building) and which functions the user can perform on that data, from view-onlyaccess to configuring new databases. The Metasys system provides the ability to divide the datainto 25 unique categories, including HVAC, fire, and security; and has 10 different levels of userfunctionality.Users can further limit user accounts to operate only at specified times on specified days of theweek. The System Administrator creates all account settings.Each account can also have associated preferences, such as which graphic or trend to display whena user logs in to the SMP UI, or which User Views appear in the Navigation Tree.Basic Access is a feature through which users can create limited operator access to SMP featuresbased on the user’s assigned permissions in the Security Administrator. Users can avail of BasicAccess on all the Metasys system engines and servers.The SMP and Metasys UI can use Microsoft Active Directory® accounts or RADIUS accounts.

Note: MVE sites do not support Basic Access and Tenant Access users.

Users can assign user access permissions to specific spaces and the equipment serving thosespaces with the Metasys UI User Authorization. Users can thereby segment user access by physicalspace within the building or campus.In addition to making it easier for system administrators to manage Metasys account access,Microsoft Active Directory® also provides the ability to use Single Sign-On to access the Metasyssystem, through the Site Management Portal UI, together with other supported applications on theenterprise network.The Audit Log records all user activities, and the System Administrator can thereby monitor useractions.User names and passwords are obscured at login for local and Active Directory accounts. Afterlogin, user names are partially obscured on the SMP or SCT UI window (for example, JohnSmithappears as Joh***).The following table lists the password rules enforced by the Metasys system user's language localesetting.


Table 9: Metasys system password rules

Supported languagelocale

Enforced password rules

English (en_us) • The password must include a minimum of 8 characters and amaximum of 50 characters.

• The password cannot include spaces or include a word or phrasethat is in the Blocked Words list.

• The password and the user name cannot share the same threeconsecutive characters.

• The password must meet the four following conditions:- Include at least one number (0–9)- Include at least one special character (-, ., @, #, !, ?, $, %)

Note: Only the special characters listed above can beused; all other special characters are invalid.

- Include at least one uppercase character- Include at least one lowercase character

Czech (cs_cz)German (de_de)Spanish (es_es)French (fr_fr)Hungarian (hu_hu)Italian (it_it)Norwegian (nb_no)Dutch (nl_nl)Polish (pl_pl)Portuguese (Brazilian)(pt_br)Russian (ru_ru)Swedish (sv_se)Turkish (tr_tr)

• The password must include a minimum of 8 characters and amaximum of 50 characters.


• The password and the username cannot share the same threeconsecutive characters.

• The password must meet three of the following conditions:- Include at least one number (0–9)- Include at least one special character (-, ., @, #, !, ?, $, %)- Include at least one uppercase character- Include at least one lowercase character- Include at least one Unicode character that is categorized as

an alphabetic character but is not uppercase or lowercase

Chinese Simplified (zh_cn)Chinese Traditional (zh_tw)Japanese (ja_jp)Korean (ko_kr)

• The password must include a minimum of 8 characters and amaximum of 50 characters.


• The password and the user name cannot share the same threeconsecutive characters.

• The password must meet two of the following conditions:- Include at least one number (0–9)- Include at least one special character (-, ., @, #, !, ?, $, %)- Include at least one uppercase character- Include at least one lowercase character- Include at least one Unicode character that is categorized as

an alphabetic character but is not uppercase or lowercase


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

Logic Connector Tool (LCT)Use the Logic Connector Tool (LCT) to create custom application programs that execute in anyengine. The programs are created using a drag-and-drop editor. The programmer can connect real-time point data in the engine with logic blocks that perform mathematical, logical, and variousspecialized control functions. You can create, edit, and view LCT programs online through theMetasys Site Management Portal UI, or offline using the SCT. When you view the finished programsthrough the SCT, you can simulate them to verify proper operation before you download them tothe engine.

Interlock ObjectThe Interlock object provides a means to establish conditional control over one or more otherobjects. It consists of an If conditional statement, True command statements, and False commandstatements. Through these statements, the user specifies a set of conditional checks (using one ormore points) for which a series of commands is used to control a collection of one or more otherobjects.

Optimal StartOptimal Start automatically determines the correct time to start HVAC systems to ensure the facilityis ready for occupants at the scheduled time. It adjusts to seasonal variations and minimizes theenergy used.The generic standard object screens handle the Optimal Start/Stop object configuration and focusviews. The object defines views for configuration and focus, and the generic screens interpret theviews to display the proper fields to the users. Users do not need custom screens or handlers.

Demand Limiting and Load RollingThe Demand Limiting (DL) feature reduces utility bills by limiting peak energy usage. DL electivelyturns off (sheds) equipment, such as fans and lights, or adjusts setpoints to limit energy use duringpeak times.The Load Rolling (LR) feature helps save money by reducing overall energy consumption. LR actscontinuously to maintain a specified energy reduction by shedding unnecessary loads. A facility canimplement either one or both of these features.

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


Users can also view user changes made within the last seven days for a selected piece ofequipment in the Equipment Activity Widget of the Metasys UI. Users can also discard user changesin this widget.

System Diagnostics and ServiceabilityThe engine collects and stores diagnostic data. The Diagnostic view of the engine device retrievesand displays diagnostic data related to communications, internal component performance, andother areas.

Metasys for Validated EnvironmentsMetasys for Validated Environments (MVE), extended architecture is a feature designed for facilitiesthat require regulatory compliance for their environmental systems. The MVE feature operateson an ADX, NAE55, NCE25, and NIE55, which are all supported as validated devices. MVE is notsupported on a BACnet ODS Workstation.MVE is specifically designed to help customers address United States Food and Drug Administration(USFDA) Title 21, Code of Federal Regulation (CFR) Part 11 compliance. MVE is also compliant withother similar agencies around the world that deal with electronic records and electronic signaturerequirements, such as Annex 11 of the European Union Good Manufacturing Practice (EU GMP)regulations (European Medicines Agency [EMEA] 1998).The ADX with MVE software provides secure data management and reporting capabilities, traceableelectronic records and signatures, and time-stamped audit trails for facilities subject to Part 11compliance. It manages and protects the long-term storage of trend data, audit data, event/alarmmessages, annotations, and system configuration data. In addition, complex passwords andmessage encryption secure the system from unauthorized access and data tampering.

Important: MVE is supported at Release 9.0 but not upgradable to Release 10.0.

UL 864 10th Edition UUKL and ORD-C100-13UUKLC Smoke Control ListingComponents of the Metasys system running Release 8.1 software are Underwriter Laboratories(UL) 864UUKL/ORD-C100-13 UUKLC 10th Edition Smoke Control Listed. In applications requiringsmoke control, this offering provides the protection of a UL 864UUKL listed smoke control systemthat has a lower installed cost and leverages the operational efficiencies of using a single systemto provide HVAC and Fire Alarm smoke control. Earlier versions of the Metasys system also supportUL 864UUKL 8th and 9th Editions. Many controllers and equipment that was qualified for theseearlier editions have been brought forward for use in the 10th Edition. Also, if different editions ofUL 864 must coexist in the same building, an Ethernet switch must be installed to isolate each UL864 Edition.The Metasys Smoke Control System consists of a set of hardware and software componentsspecifically UL 864 10thEdition UUKL/ORD-C100-13 UUKLC smoke control listed. The listing appliesto an indoor, dry environment only, where each Air Handling Unit (AHU) is located in an indoor,air-conditioned mechanical space. This listing also applies to an application where a Rooftop Unit(RTU) is located outside but the smoke control panel servicing the RTU is mounted in an indoor,conditioned mechanical space, with conduit wire runs to the RTU. However, this listing does notsupport applications where smoke control equipment is mounted in the RTU itself, or whereequipment is exposed to a damp or wet environment. Lastly, the 10th Edition listing is intended forbuilding systems in United States and Canada.The smoke control applications are performed with an NAE and Johnson Controls MS/TP and N2bus field controllers. The Metasys product code numbers with a dash U suffix indicate that they arefor the Metasys Release 8.1 UL 864 UUKL/ORD-C100-13 UUKLC smoke control. Also, specific SCT andCCT software releases are spelled out in the listing. For details, refer to the Metasys® System UL 86410th Edition UUKL/ORD-C100-13 UUKLC Smoke Control System Technical Bulletin (LIT-12012487).The smoke control offering provides a configurable yet straightforward application for receivingfire alarm signals, and it has the ability to control fans and dampers in a prescribed manner basedon prioritized smoke control schemes. Smoke Control systems can also be activated automaticallyfrom a firefighter's smoke control station (FSCS). The FSCS enables a designated operator or afirefighter to execute real-time control from the FSCS panel. Automation Displays, Incorporated


(ADI) has a UL/ULc Listed Firefighter's Smoke Control Station (FSCS) that integrates with the MetasysUL 864 10th Edition UUKL/ORD-C100-13UUKLC Smoke Control Listed Metasys Release 8.1 system.The UL/cUL 864 standard requires that one FSCS be included as part of the listed smoke controlsystem.

Note: The Authority Having Jurisdiction (AHJ) must approve the graphics on the FSCS panelas well as the location in a secured part of the building. Refer to the specific building codesor standards that often contain specifics about the FSCS. For more information, refer to theMetasys® System UL 864 10th Edition UUKL/ORD-C100-13 UUKLC Smoke Control System TechnicalBulletin (LIT-12012487).

Reporting CapabilitiesMetasys Export Utility SoftwareThe Metasys Export Utility software provides facility managers with the ability to easily build customreports using historical data from the Metasys system. This data can be used to manage dailybuilding operations. The Metasys Export Utility software extracts historical trends, alarms, and auditdata from an engine or server. Users can collect data desired by the operator for analysis from thesystem and store it in up to six different formats, including Microsoft Word® or Microsoft Excel®files. In addition, the scheduling feature retrieves and saves data based upon user-configurabletime intervals.The Metasys Export Utility provides the user with the ability to create runtime studies and discoverroot cause analysis of system changes and mechanical equipment failures. Users can also collecttrended runtime data for use by a computerized maintenance management system (CMMS) toschedule mechanical maintenance of HVAC systems.

Metasys Advanced Reporting SystemThe Metasys Advanced Reporting System is a standard capability of all ADXs and ODSs when usingsupported SQL Server software, with SQL Server Reporting Services (SSRS) installed. The web-basedreporting interface provides standard report sets. Users can thereby review the alarm and trendconfiguration 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 providesummary and detailed trend aggregations. The site’s All Items or User View navigation tree filtersthe report information. Users can customize the date range and data type desired for each report.Once a report is created in the user interface, users can export the data into common applications,such as Microsoft Excel® spreadsheet or Adobe® PDF formats.

Note: ODS is supported at Release 9.0 but not upgradable to Release 10.0.

Energy EssentialsEnergy Essentials is an optional software feature that can be added to the Metasys AdvancedReporting System. It offers seven types of energy reports that provide a high-level view ofnormalized energy use across your site, and presents your daily electrical demand graphically.Metasys Advanced Reporting supports installation on a computer with SQL Server 2016 installed,however; Energy Essentials does not support installation on a server using SQL Server 2016 or later.

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


To ensure optimal performance of the graphics created in the Metasys UI, follow therecommendations in the table below.Table 10: Recommended Maximum Selections

Item or Element Recommendations NotesNumber of Elements(Shapes, Symbols, orImages)

0–125 An element is any shape, symbol, or imagethat is added to the graphic.

Number of BoundMetasys Points

0–200 We recommend that you have no morethan 200 bound Metasys points on a singlegraphic unless you are using a StatusSummary element.

Number of StatusSummaries

0–6 This limit allows for 50 bound Metasys pointsper Status Summary with a recommendedmaximum of six Status Summaries on agraphic. The limit results in 300 pointswhose statuses are summarized usingonly five elements (not 300 elements). ThisStatus Summary exception contrasts thebound Metasys point recommendationof 200 maximum, because not all boundvalues appear in the graphic.

Number of Images 0–5 An image is any image file that is added tothe Graphic Canvas.

Note: We recommend that imageshave a maximum size of 1,600 pixels(height) by 1,200 pixels (width) and1 MB in file size. Exceeding therecommended dimension size maycause significant delays in load times.

Number of Animations 0–50 This number applies to animations thatare actively running at the same time (forexample, a supply fan and a return fan).

Graphics+Graphics+ is a visualization software package designed for Metasys® building automation system(BAS) operators to create interactive building data representations, empowering them to visualize,analyze, and respond to problems faster. Graphics+ is made up of two components: the GraphicGeneration Tool (GGT) and the Graphics+ Viewer.The Graphic Generation Tool helps designers to create compelling representations of their buildingequipment and floor plans and bind them to Metasys data objects. You can save these graphicsdirectly 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 canthereby show, command, or update in real time all the data-linked objects that were created in theGGT.Metasys UI and Metasys UI Offline supports viewing Graphics+ graphics. To view Graphics+ graphicsin the Metasys UI, associate your graphics to space or equipment objects using the SCT and thendownload the ADS.


Note: The graphics need to be on either the ADS or the devices for the relationship to workand display correctly.

To view graphics in the Metasys UI Offline, simply associate your graphics to space or equipmentobjects and then log in to the Metasys UI Offline.

Standard GraphicsStandard Graphics is the default Metasys graphics package used to design equipment and floor plangraphics in scalable vector based format. The package comprises of two components, GraphicsStencil Library (GSL) and User Graphics Tool (UGT).GSL is a set of Visio Stencils, Templates, and add-ons (including Gzip, a compression utility), usedwith Microsoft® Visio® Professional 2002 to create graphics for use in your Metasys system. Thegraphic files created are imported in the User Graphics Tool (UGT), which has the ability to accept awide variety of image formats such as SVGs, SVGZs, or JPG files for background images which canrepresent buildings, floor plans, mechanical equipment, and any other image that represents thelocation or function of the equipment in the graphic. Within UGT, users can bind their graphics toMetasys objects. Users can view Standard Graphics on the SMP user interface.

Advanced Graphics Application SoftwareThe Advanced Graphics Application is an enhanced version of the Standard Graphics packagethat provides dynamic capabilities such as custom animation, color changing, and flashing forthe Metasys system. The package includes a dynamic example stencil library and is an add-on toMicrosoft Visio® software. With a more comprehensive representation of facility support systems,building operators can easily monitor the health of the system on a more intuitive interface. Youcan view advanced graphics in the Metasys system Site Management Portal UI.

IntegrationsBACnet/IP IntegrationBACnet/IP integration is possible with two Metasys field equipment controllers, namely the IPFAC4911 controller and the IP VMA1930 controller. These controllers communicate on EthernetIP networks and support increased network performance, enabling faster access to data andfaster troubleshooting. Metasys BACnet/IP Field Controllers may be connected to your buildingautomation network in two ways. You can connect them as daisy-chained devices or as part of astar type network, which is also called home run. Beginning at Release 10.0, you can also networkthe IP FAC4911 and IP VMA1930 controllers, which are connected by Cisco® technology, in a ringEthernet topology, which provides network reliability by mitigating a single point of failure in the IP/Ethernet network wiring. Most networks use combinations of these topologies. For details, refer tothe Metasys IP Networks for BACnet/IP Configuration Guide Technical Bulletin (LIT-12012458).At Release 10.0, BACnet/IP is also used to integrate the Simplex Fire System and lighting systemsfrom preferred partners into the Metasys system. For more information about these integrations,see Simplex Fire system and Cree and Molex Lighting Systems, respectively.

MS/TP Communications BusThe MS/TP Bus is a local or remote network that connects some NAEs/NCEs/NIEs and fieldcontrollers using BACnet MS/TP protocol. Two tiers of MS/TP Buses exist in the Metasys systemarchitecture. The Field Controller (FC) Bus consists of BACnet controllers and point interfacessupervised by an NAE/NCE/NIE. The Sensor Actuator (SA) Bus consists of point interfaces andnetworked sensors supervised by a field controller. To communicate with field controllers on aremote MS/TP Bus, you need a BACnet/IP to BACnet MS/TP Router connected to the building's IPnetwork. The ODS Workstation is also compatible with the remote MS/TP bus. For details, refer tothe MS/TP Communications Bus Technical Bulletin (LIT-12011034).

Important: ODS is supported at Release 9.0 but not upgradable to Release 10.0.


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

N1 Integration (Release 9.0 or earlier)The N1 integration is based on the NIE. A single NIE or a network of multiple NIE devices areconfigured to map point objects of all or selected Network Control Module (NCM) devices on one ormultiple existing Ethernet N1 networks. The NIE to which an N1 object is mapped provides alarmand event management, trending, energy management, and scheduling capabilities.

Note: Support for N1 integration ends at Release 9.0.

LonWorksThe 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 intoone chip. The LonWorks network uses the LonTalk® protocol, a software language for field devicecommunication. This protocol uses the Open Systems Interconnect (OSI) reference model andfeatures all seven communication layers for interoperability among control devices.

ModbusModbus is one of the most common MS/TP communication protocols used in the industry. Itis 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 NIEx9supports both Modbus RTU (RS-485, RS-232) and Modbus TCP/IP connectivity.

M-BusM-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 converterconnects an NIEx9 to an M-Bus network.

KNXKNX 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 (EuropeanHome System) protocols. A KNX IP Gateway is required to connect an NIEx9 to a KNX network.

C·CURE 9000 Access ControlA VND (Vendor) Integration driver adds the ability for the Metasys system to provide data from theC·CURE 9000 Access Control system. You can use this data within Metasys to automate buildingconditions when triggered by security badge and door events.

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

Simplex Fire systemThe Simplex Fire system includes a BACnet/IP integration, which facilitates the integration withMetasys. The Metasys system serves as a secondary fire monitoring system that can alert morepeople and automate building conditions when triggered by a fire event. The Metasys toolset isenhanced to simplify the workflow for integrating a Simplex Fire system:


• The process of creating the Metasys Network, Equipment and Space integrations for SIMPLEX FirePanels 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 ofthe fire on the building and floor plan maps.

Cree and Molex Lighting SystemsStarting at Release 10.0, Cree and Molex LED lighting and sensor networks are tightly integratedwith Metasys. With this integration, you can easily control the lights of an entire building, and youcan automate lighting adjustments to achieve healthy and efficient lighting conditions. You cancoordinate lighting behavior for signaling to occupants regarding critical scenarios in a building,such as fire, intruder alert, lock-down, and code blue events.

Metasys System Revision Compatibility OverviewThis section describes high-level revision-to-revision compatibility scenarios for customer job siteswhen you upgrade to Metasys Release 10.0. This section also contains some information aboutprevious release revision compatibility for existing sites that are at a previous release. This sectionalso describes revision-to-revision compatibility scenarios for the Graphics+ feature within Metasysuser interfaces.

General Compatibility Information for Customer Job SitesSCT allows you to maintain Release 5.2, 6.x, 7.x, 8.x, 9.0, and 10.0 engines in the site's archive.The Site Director must be at an equal or higher revision to all the other servers and engineson a site. The Product Development Test Lab validates the latest revisions of a Site Director with amix of Engines three revisions back. At Release 8.1, this included Release 6.5, 7.0, and 8.0.The SCT no longer requires the same revision as the Site Director when integrated with the ADS/ADX. If you install the ODS software, your SCT must be at Release 6.5 or later.

Note: ODS is supported at Release 9.0 but not upgradable to Release 10.0.

For sites installed with the Metasys UI, the Site Director server must be at Metasys Release 7.0. Sitesusing the Rapid Archive Creation feature of SCT 11.0 or later to quickly configure their Metasys UIrequire the Site Director server to be at Release 8.0 or later.Starting at Release 4.1, MS-NxE55-0 Engines can no longer be upgraded beyond Release 4.0. Siteswith -0 NxE55s upgraded to Release 4.0 are tested to coexist with the latest revision Site Director.It may not be possible to edit Graphics or Logic Connector tool (LCT) processes in an Engine atRevision 2.2 or earlier from a Site Director at Revision 3.0 or later. This is because the ScalableVector Graphic (SVG) rendering program was changed after Release 2.2. As a workaround, log in tothe Engine directly to make these edits.

Compatibility Rules for CCT and Field Controller RevisionsAll revision-to-revision upgrade combinations for FEC/CCT applications are tested in the ProductDevelopment Test Labs.Starting at CCT Release 10.1, CCT is used to configure, simulate, and commission FECs, AdvancedApplication Field Equipment Controllers (FACs), VMA16s, and VMA1832s on an N2 Bus. CCT 10.1 canopen and commission any previous FEC application created with an earlier revision.FEC revisions can be mixed and matched on any Engine with MS/TP Integration. This means thatRelease 5.3 based FECs can be added to a Release 4.0 NxE's MS/TP Integration. The only risk is thatsome enumerations that were created in the 5.1 .caf may not display properly in the engineeringview for the FEC.


The CCT upgrade process works between major and minor revision levels (for example, Release10.0 to 10.1). CCT applications created during Alpha and Beta site releases (for example, 3.0.22 to3.0.25) do not automatically upgrade.The .caf files created by CCT are independent of the version of SQL Server (for example, a .caf filecreated on a customer's machine running SQL Express) can be opened on a Branch laptop usingMicrosoft SQL Server Data Engine (MSDE).The FEC Display was added at Release 3.0. To incorporate a display into an FEC installed at a releaseprior to 3.0, you must:

• upgrade the .caf file to the current release

• open the display configuration application within CCT and select the desired points to display

• download main and boot code, then download the upgraded .caf file

Output Controller Module Upgrades• Starting at Release 5.0, an Adaptive Tuning Reset Network Input was added. This feature is

created and connected only if you re-run System Selection. During the upgrade process, theinterface to the PID is created but is not connected.

• Starting at Release 5.0, the Adaptive Tuning logic is disabled when the Output point associatedwith the Output Controller is overridden. This feature is created and connected only if you re-runSystem Selection.

• Starting a Release 5.1, the following feature updates were made to all Output Controllers:

- General PID Process ID updates have been made to key tuning parameters and timersettings per control loop type. These changes are updated from either an upgrade orsystem selection.

- Fast Switching logic that bypasses saturation timers when zones need to quickly transitionfrom heating to cooling (for example, load changes in the space or setpoint changes). Thislogic is only created from system selection.

- A new Lead Compensator block is automatically integrated into output controller modulesfor zone control loops on water valves. This block acts as like an anticipator and reducesthe impact of the non-linearity of typical ball or globe valves. This is only created fromsystem selection.

- Updates to the default timer settings on Multi-Stage Controller (MSC) modules that reducecycling of stages while maintaining setpoint in both the occupied or unoccupied modes.These timer settings are updated during system selection or manual updates of theunoccupied duration timer.

• Starting at Release 5.1, updates to Output Controller Modules that contain PID and PIDpreprocessor blocks are made even when the module has been user modified:

- Output Controllers utilized with Proportional Outputs are fully upgraded with the latestlogic and all the necessary internal connections.

- Output Controllers utilized with Staged/MSC Outputs are upgraded with the latestprimitives but the connections between the blocks are not made. Instead, the PID primitiveuses 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 ZoneControl (VAV Boxes, Fan Coils, Unit Vents, and Heat Pumps).

Working with SCT Release 11.x or Later at Metasys Release 8.x and LaterSCT Release 11.x or later features new functionality to save time by simplifying the configurationprocess 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 thetime from previous releases.In addition to Rapid Archive Creation, SCT now permits spaces and equipment-only downloads andauto-discovery of serving relationships for Metasys UI. The Downloading Only Metasys UI Spacesand Equipment options allows sites to download Metasys UI spaces and equipment informationto your Release 7.0 or later server class device (ADS, ADX, or ADS-Lite) through the Manage ArchiveWizard. 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 populateServing and Served By columns in the Equipment Discovery window. Enhancements to the Findand Replace functionality allow you increased control over Equipment Name and EquipmentDescriptions to aid in more accurate auto-discovery matches.

Graphics+ Release 1.3• Users must apply the Metasys system 5.2.12 patch to a Site Director server/device and SCT

computer running Release 5.2, to fully utilize all features within the Graphics+ Release 1.3.

• Graphics+ Release 1.3 is guaranteed to be backward compatible with graphics created using theGraphics+ Release 1.2 and 1.1. Therefore, customers currently running Release 1.1 or Release 1.2can upgrade to Release 1.3 without having to manually touch every existing customer graphic.

• Graphics+ Release 1.3 includes performance enhancements when displaying graphics in the SiteManagement Portal (SMP) UI. For performance enhancements to take effect, the Site Directormust be at Metasys Release 6.5 or later. Most performance enhancements require no user action.However, there may be user action required to reduce the size of large dimension images withingraphics that contain large dimension images (using the Library Panel Basic Symbols Imageelement). Refer to the Image section of the Graphic Enterprise Library portion of the GraphicGeneration Tool Help (LIT-12011697).

• Metasys UI and Metasys UI Offline Release 2.0 supports viewing Graphics+ graphics. To viewGraphics+ graphics in the Metasys UI, associate your graphics to space or equipment objectsusing the SCT, then download the ADS.

Note: The graphics need to be on either the ADS or the devices for the relationship to workand display correctly.

To view graphics in the Metasys UI Offline, simply associate your graphics to space or equipmentobjects, then log in to theMetasys UI Offline.

For more information on Upgrade Considerations at Graphics+ Release 1.3, refer to the UpgradeConsiderations section of the Graphic Generation Tool Installation Instructions (LIT-12011685).

FEC, FAC Wireless IntegrationsThe Wireless ZFR181x Series System was introduced at Metasys Release 4.0.

• Wireless coordinators need to be at an equal or higher revision level than the controllersassociated 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. CCTautomatically 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 beupdated before connecting the wireless router.

WNC1800/ZFR182x Pro Series Wireless Field Bus SystemThe WNC1800/ZFR182x Pro Series Wireless Field Bus System was introduced at Metasys Release 8.1.The WNC1800/ZFR182x Pro Series Wireless Field Bus System uses different wireless coordinators,routers, and repeaters than the ZFR1810 Series Wireless Field Bus System. You cannot intermixWNC/ZFR Pro Series and older ZFR1810 Series wireless devices on the same wireless PAN. However,you can intermix WNC/ZFR Pro and older ZFR1810 devices on separate PANs using separatecoordinators.

LCS85 CompatibilityThere are no known issues with the integration of the LCS85 to a Metasys Release 10.0 site.

Metasys System Configuration ExamplesMultiple NAE System Configuration with One NAE Designated as the SiteDirectorTo extend the capabilities of your system, add one or more additional NAEs. In Figure 3, one NAEdesignated as the Site Director provides the Site Management Portal to all devices on the site. Thisconfiguration supports up to four simultaneous users.

Note:

• This configuration only provides long-term storage of data through the use of the MetasysExport Utility installed on a computer.

• The NAE45-Lite can be partnered with only other NAE45-Lite devices. Additionally, theNAE45-Lite requires an ADS-Lite-A Site Director, and both of these are available only inspecific markets.

Figure 3: Multiple NAE System Configurationwith One NAE Designated as the Site Director


ADS/ADX Site Director with Multiple NAEs System ConfigurationSites that require more than four simultaneous users must add an ADS or ADX (Figure 4). If a largenumber of graphics are required to navigate through a site, the addition of the ADS/ADX allowsaccess to a disk drive or network drive for graphic file storage. The ADS/ADX provides permanentstorage of collected trend data samples, event messages, and audit trail messages routed from theNAE/NCE devices.

Note: Cloud-Based Applications are not available for all sites.

Figure 4: Multiple NAE System Configuration with ADS or ADX, and Metasys UI

ADS/ADX Site Director and Secure NAE-S with Unencrypted NAEsFigure 5 shows a network that features a secure NAE-S network engine with other unencrypted NAEengines reporting to an ADS/ADX Site Director. For more details, refer to the NAE-S CommissioningGuide (LIT-12012269).


Figure 5: Example Network with Encrypted and Unencrypted NAEs

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


Figure 6: ADX Split Configuration

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


Figure 7: Differences between Unified and Split ADX Configurations

Unified and Split ADX with Dual Network CardsA unified or split ADX system can use computers that have more than one network card. OtherMetasys software applications such as Metasys Export Utility, also support computers with multiplenetwork cards. The steps for configuring the cards are included with the software installationinstructions for the particular application. The following figure shows two examples of supportednetwork configurations.


Figure 8: Network Examples with Dual Network Cards

Large ADX Site ConfigurationThe ADX you select for a large site can be a 10-, 25-, 50-, or 100-user ADX. Refer to the TechnicalSpecifications section of the Application and Data Server (ADS) and Extended Application andData Server (ADX) Product Bulletin (LIT-1201525), Extended Application and Data Server SystemRequirements (Unified ADX Systems, 50 or 100 Users) table for the technical specifications for alarge ADX system.

Note: Metasys for Validated Environments supports 5, 10, 25, and 50 users.

ODS Workstation ConfigurationsImportant: ODS is supported at Release 9.0 but not upgradable to Release 10.0.

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


Figure 9: ODS Site Manager Workstation Configuration

Figure 10: ODS BACnet Workstation Configuration


Figure 11: ODS Combined Workstation Configuration

N1 Integration System ConfigurationAt Release 9.0 or earlier, the NIE (NIE55 and NIE85) provides a means of migrating your existingMetasys N1 network to the Metasys system. For more details about NIEs, refer to the Release 9.0version of the Metasys System Configuration Guide (LIT-12011832).

Important: Support for N1 integration ends at Release 9.0.

Figure 12: N1 Integration with NIE85 (Release 9.0 or earlier)

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


Figure 13: BACnet/IP Network Integration System Configuration

The NAE85 allows integration of larger BACnet integration projects.

Figure 14: NAE85 BACnet Integration


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

Figure 15: Third-Party Network Integration

Wireless Metasys System ConfigurationsFigure 16 shows various wireless Metasys system offerings, and how they coexist within the Metasyssystem.


Figure 16: Wireless Metasys Systems

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


Figure 17: Metasys System UL 864 10th Edition UUKL/ORD-C100-13 UUKLC Standard for Smoke Control

Performance Guidelines and LimitationsThe following tables describe the recommendations and limitations of the various components ofthe Metasys system.

Site Director Limitations and RecommendationsTable 11 describes performance guidelines and limitations of the Metasys system Site Directors.Particular release numbers are also provided.

Note: Upgrade the Site Director to Metasys Release 10.0 to take advantage of encryptedcommunications, we recommend that you upgrade the network engines to the newer releaseas well. Network engines at Release 5.2 or later continue to work well with Release 10.0, but toensure best performance, upgrade engines to newer versions as soon as is practical.

Table 11: Site Director Limitations and RecommendationsType of Site DirectorMaximum

Allowed NAE35(9.0.7)

NAE45(9.0.7)

NAE55(10.0)

NAE85(10.0)

NCE25(9.0.7)

ADS/ODSDesktop (10.0)

ADS-Lite-E(10.0) 1

ADS-Lite-A(10.0) 1

ADX ODS Server

Total engines(including self forNxEs)

3 3 4 4 12 1 to 143 54 45 1 to 1,000 6 1 to 100 6

SimultaneousSMP users 2 2 4 10 2 5 5 5

10/25/50/100

75 7

Dynamic valuesper graphics

100 100 100 100 100 100 100 100 100 100

Results displayedin a globalsearch

500 500 500 500 500 2,000 2,000 2,000 2,000 2,000


Table 11: Site Director Limitations and RecommendationsType of Site DirectorMaximum

Allowed NAE35(9.0.7)

NAE45(9.0.7)

NAE55(10.0)

NAE85(10.0)

NCE25(9.0.7)

ADS/ODSDesktop (10.0)

ADS-Lite-E(10.0) 1

ADS-Lite-A(10.0) 1

ADX ODS Server

Languages 1 18 18 18 18 18Objects in entiresystem

3 million/ 750k (for ADX Site Director Only)

Objects in device8 2,500 2,500 5,000 25,000 2,500 Limited by SQL Server storage capacity

Objects within asingle folder

300 300 700 700 300 700 700 700 700 700

Characters inthe name of anobject

400

Characters in thedescription of anobject

64

Nesting levels forobject creation

7

Extensions perobject

10

Sets for third-party BACnetstates text

1,000

Characters fora third-partyBACnet statestext

60

Members for amulti-value third-party BACnetstates text

500

Non-SimultaneousSMP users

Limited only by memory capacity

SMP user views Limited only by memory capacitySimultaneousbrowsers perclient computer

2 (Mix of online, SCT, and Simulation)

DLLR loadextension

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 x1024)/average number of characters per load. 1024 Bytes equals 1 KB. For example, if your DLLR object is configured with Loads that have fullyqualified references that average 100 characters (including dots) in length, then you can support approximately 650 loads (64 x 1024/100) for thatDLLR. If you reach the memory limit, you may need to combine loads. For example, if a site has multiple physical meters, split the meters acrossmultiple controllers and apply appropriate DLLR loads, if possible. Otherwise, use Interlock or Multiple Command objects to reduce the number ofloads added to the DLLR.

DLLR objects Limited only by memory capacity.

1 The ADS-Lite cannot host servers.2 An NCE25 can only act as Site Director for itself.3 Varies with concurrent connection.4 Supports up to five of the following: NAE35, NAE45, NCE25, NIE29, NIE39, and NIE49.5 Supports up to 3 NAE-Lite units plus up to 1 NIE29, NIE39, and NIE49.6 Depends on computer hardware. Both a unified and split ADX support a maximum of 1,000 engines.7 Depends on version of ADX or ODS.8 Includes all points, extensions, graphics (background image), trend study, and other objects, such as schedules and

interlocks. For the NxE85/NIE89, 25,000 object limit includes 15,000 object base license plus 10,000 object add-onlicense.


Table 12: Maximum Number of Users Supported on ADS/ADX/ODS Site Director

Computer Supported PlatformDesktop Server

SiteManagementPortal (SMP)Users (Up To)

Metasys UI Users(Up To)

ADS 5 Users Yes - 5 5ADX 10 Users - Yes 10 10ADX 25 Users - Yes 25 25ADX 50 Users - Yes 50 50

ADX 100 Users1 - Yes 100 50

ODS 5-User;25,000 Objects

Yes Yes 5 Not Supported

1 Metasys for Validated Environments does not support the 100 user ADX.

Table 13: Maximum Number of Network Engines Supported Based on ADS/ADX (Unified andSplit Configuration) and Server Size

Site Directorwith MaximumUsers

1 to 14Engines

1 to 50 Engines 1 to 250 Engines 1 to 1,000 Engines

ADS 5 Users ADS

ADX 10 Users Small/Medium ADXADX 25 Users Large ADX

Large ADX

ADX 50 UsersADX 100 Users

Extra Large ADX Extra Large ADX

Extra Large ADX

For ADS/ADX computer hardware requirements, refer to the Technical Specifications section ofthe Application and Data Server (ADS) and Extended Application and Data Server (ADX) Product Bulletin(LIT-1201525):

• For Unified ADS refer to Application and Data Server (ADS) System Requirements (5 Users) table.• For Small, Medium, or Large Unified ADX refer to Extended Application and Data Server System

Requirements (Unified ADX Systems, 10 or 25 Users) table.• For Small/Medium/Large Split ADX refer to Extended Application and Data Server System

Requirements (Split ADX Systems, 10 or 25 Users) table.• For Extra Large Unified ADX refer to Extended Application and Data Server System

Requirements (Unified ADX Systems, 50 or 100 Users) table.• For Extra Large Split ADX refer to Extended Application and Data Server System Requirements

(Split ADX System, 50 or 100 Users) table.

Network Engine Hardware LimitationsThe following table describes limitations of the Metasys system network engines.


Table 14: Network Engine Hardware Limitations

Maximum allowed NCE25 NAE35 NAE45 NAE45-Lite

NAE55 NAE85

ODS 1

Local Field Buses (FBs) 1 1 1 1 2 0Remote Field Buses(RFBs)

0 4 4 0 6 or 7 16

Total Field Buses (Localand Remote Field Buses)

1 (1 FB + 0RFB)

5 (1 FB + 4RFB)

5 (1 FB + 4RFB)

1 (1 FB + 0RFB)

8 (2 FB +6 RFB or1 FB + 7RFB)

16 RFB only

Per trunk device limits if all devices are Metasys family devices, such asCGMs, CVMs, FACs, FECs, VMAs, IOMs, and TEC3600s:32 50 100 100 100 N/APer trunk device limits if one device is a non-Metasys family device,such as a Facility Explorer® device, TEC2000, or third-party device:

MS/TP devices on FCBus2

Note: N2 devicesfollow the samerules as MS/TP devices, butperformance variesbased on controllermix (N2Open/Sys91/VMA).

32 32 64 64 64 N/A

Remote MS/TP deviceson remote field bus3

N/A 16 or 32 16 or 32 N/A 16 or 32 16 or 32

Mapped N2 points pertrunk4

2,500 2,500 2,500 N/A 2,500 N/A

32 64 127 N/A 255 N/ALonWorks devices5

Note: The LonWorks integration is only supported on NAE35s,NAE45s, and NCE25s with the Metasys Release 9.0 software orearlier. The Release 9.0.7 patch update is not supported for theseLonWorks models; they remain at Release 9.0. However, theLonWorks integration is supported for NAE55s at Release 10.0.

LonWorks networkvariables

1,500 1,500 1,500 N/A 2,000 N/A

Johnson ControlsBACnet/IP devices andthird-party BACnet/IPdevices

5066,77,88 506,7,8 506,7,8 506,7,8 2006,7 2007

Objects 2,500 2,500 2,500 2,500 5,000 10,000(default)25,000(upgrade)

Time on battery backup 1,024 seconds N/A

1 ODS is not supported at Release 10.0.2 Maximum 3 bus segments per FC Bus. Maximum 50 devices per bus segment. Bus segments on an FC bus are

connected with repeaters (only). Up to two cascaded repeaters may be applied to an FC bus (to connect three bussegments).


3 The maximum device count is 32 if the bus contains all Johnson Controls devices, and 16 if the bus contains one ormore non-Johnson Controls devices.

4 Performance varies based on the point mix (N2 Open/Sys91/VMA). Recommend maximum for best performance is1,000 points.

5 Single sub-net LonWorks network; does not support routers; supports physical repeaters6 Depends on the number of objects each BACnet device supports.7 Johnson Controls IP controllers only work with NAEs (and site directors) at Release 9.0 or later.8 Some sites may require manual mapping based on system architecture. They may also require system adjustments,

such as BACnet communication adjustments, or firewall off.

Alarm and Trending Performance GuidelinesTable 15: Alarm and Trending Performance GuidelinesDescription NCE25/

NAE35/NAE45/

NAE55 NAE85 ADSODS1

(Desktop)

ADXODS1

(Server)

Comments

Averagemaximumnumber ofalarms/eventsper hour

100 100 100 200 1,000 This number applies to alarms/events that originate fromdevices at Release 5.2 or later.

Maximumnumber ofalarms/eventsper day

2,400 2,400 2,400 5,000 48,000 Within a 24-hour period. Thisnumber applies to alarms/eventsthat originate from devices atRelease 5.2 or later. Supportsone daily burst of 25k alarms/events in one hour.

Maximumnumber ofstored alarms/events

500 1,000 1,000 Limited bySQL Serverstoragecapacity

N/A

Averagemaximumnumber of trendsamples perhour

1,500 1,500 1,500 22,500 100,000 This number applies to trendsamples that originate fromdevices at Release 5.0 or later.The ADX supports one dailyburst of 300k trends in one hour.

Maximumnumber of trendsamples per day

36,000 36,000 36,000 540,000 2,400,000 Within a 24-hour period. Thisnumber applies to alarms/eventsoriginating from devices atRelease 5.0 or later.

Maximumnumber ofstored trendsamples

Limited bymemoryusage

Limited bymemory usage

8,000,000 Limitedonlyby SQLstoragecapacity

N/A

1 ODS is not supported at Release 10.0.

Notes:

• Alarms and trends from FACs connected to any of these contribute to the overall totals.

• ODS is not supported at Release 10.0.


MS/TP Performance GuidelinesTable 16: MS/TP Performance Guidelines

Performance Rating COV Rate Token Loop TimeLow > 500 messages per minute > 3,000 msMedium Between 400 and 500

messages per minuteBetween 2,000 and 3,000 ms

High < 400 messages per minute < 2,000 ms

SCT LimitationsTable 17: SCT Limitations

Description Supported CommentsMax. number of simultaneoususers

1

Max. number of concurrentlyactive archives

10

10 GB Using supported MicrosoftSQL Server Express 2014 orMicrosoft SQL Server Express2012 SP2

Max. size of an activedatabase or project in SCT

No Limit Using supported Microsoft SQLServer Software

FAC Integration ConsiderationsThe local FAC trend and alarm and event setup strategy should focus on needs during a stand-alone commissioning session using CCT. The integration of an FAC's trends, alarms, and events isgoverned by the NxE guidelines for trend and alarm/event integrations.The recommended limit threshold for trend samples for an NxE is 1,500 samples per hour. The totalnumber of trend samples forwarded from all FACs integrated with an NxE should not exceed thislimit during the setup of the local FAC trends.The recommended limit threshold for alarm and event samples for an NxE is 100 events per hour.The alarms that are set up in all FACs for use as BACnet Alarm extensions in the NxE should belimited to only the points that normally are created as extensions in the NxEs. For consistency, theuse of BACnet Alarm extensions instead of Metasys Alarm extensions should also be consideredwhen deciding whether the FAC's BACnet Alarms should be enabled at the NxE.In the following examples, we show acceptable limits with the following setups:

• 5 FACs with 6 alarms per hour plus 1 NAE with 30 alarms per hour (Table 18)

• 5 FACs with 200 trend samples per hour plus 1 NAE with 500 trend samples per hour (Table 19)

• 5 FACs with 10 COVs per minute plus 35 FECs with 10 COVs per minute (Table 20)Table 18: Example 1

Setup Alarms per Hour5 FAC with 6 alarms/hour each 30 alarms per hour1 NAE 30 alarms per hourTotal 60 alarms per hour


Table 19: Example 2

Setup Trend Samples per Hour5 FAC with 200 trend samples per hour each 1,000 trend samples per hour1 NAE 500 trend sample per hourTotal 1,500 trend samples per hour

Table 20: Example 3

Setup COVs per Minute5 FACs with 10 COVs/minute 50 COVs per minute35 FECs with 10 COVs/minute 350 COVs per minuteTotal 400 COVs per minute

For trend creations in the FAC, the use of faster sample intervals of key points provides a moreintuitive 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 sampleintervals have to be utilized in the NxE integration. The trends created in the FAC do not have to bediscovered and used by the NxEs; separate trends extensions can still be added at the NxE for anypoints that have FAC based trends created.For alarm enables in the FAC, the use of the FAC's local event viewer should be taken intoconsideration to provide a more intuitive troubleshooting interface during a CCT commissioningsession. The FAC holds the 100 most recent alarms/events in its local memory.

Transfer limitationsBluetooth and ZigBee are not supported for Transfer to Device (Download) for controllers usingfirmware 7.0 or later. NxE Passthru is not supported for Transfer to Device (Download) forcontrollers using firmware 7.0 or later when going through an engine at Release 8.1 or earlier. Forfurther details refer to the Troubleshooting section in the Controller Tool Help (LIT-12011147).

Technical Specifications and RequirementsHardware Configuration RequirementsOur suggested minimum hardware configuration is based on experience and testing for both clientand server platforms. These configurations are only suggestions and are not meant to imply thatolder or slower machines are not usable.Systems with less memory, smaller hard disks, or systems that are generally slower, may haveacceptable performance for basic operations. These systems may also be acceptable when notcalled upon to operate simultaneous tasks that require hardware or network resources. Memory-intensive applications may require additional memory for proper performance. Examples of theseoptional or advanced features of the Metasys system include navigation and support for complexgraphics, operation with the maximum number of users, complex and extended queries with theMetasys Export Utility, support for large network integrations, and large numbers of concurrentopen windows.When deciding on computer hardware, consider the following important factors:

• Overall system performance is highly dependent on the total amount of available computer RAM.If you experience performance issues with the ADS or ADX, increase the total amount of RAM.

• For improved performance, consider Serial Attached SCSI (SAS) hard drives over Serial ATAttachment (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 thehardware recommendations listed in this document.

• Do not enable power saving modes on the ADS or ADX computer. Such modes automatically turnoff disk drives and network cards, thereby adversely affecting proper Metasys system operation.

• Remember to obtain Windows operating system Client Access Licenses (CALs) for the totalnumber of users and devices on your system. Refer to the Network and IT Guidance TechnicalBulletin (LIT-12011279) for more information on CALs.

Client Computer Requirements for UI Client DevicesThe following table describes the recommended and minimum computer requirements for thecomputer used for Site Management Portal, SCT, and Metasys UI access.Table 21: Client Computer Requirements for Site Management Portal UI, SCT, Metasys UI, andMetasys UI Offline

Site Management Portal UISystem Configuration Tool(SCT)System Configuration Tool Pro(SCT Pro)

Metasys UIMetasys UI Offline

RecommendedProcessor1

Intel® Core™ i5 Processor Intel® Core™ i5 Processor

8 GB (4 GB minimum) 8 GB (1 GB minimum)RecommendedRandom AccessMemory (RAM)

Note: If you use graphics intensively, you may experience bettercomputer performance with additional RAM.

Hard Disk Capacity 40 GB hard disk (minimum) 40 GB hard disk (minimum)Supported OperatingSystem

Windows® 10 Pro and EnterpriseEditions with Creators Update(version 1709) (64-bit)Windows® 8.1 Pro andEnterprise Editions with Update1 (64-bit)Windows® 7 Professional,Enterprise, and Ultimate Editionswith SP1 (64-bit)Apple® macOS® 10.12 SierraApple® OS X® 10.11 El CapitanApple® OS X® 10.13 High Sierra

Windows® 10 Pro and EnterpriseEditions with Creators Update (version1709) (64-bit)Windows® 8.1 Pro and EnterpriseEditions with Update 1 (64-bit)Windows® 7 Professional, Enterprise,and Ultimate Editions with SP1 (64-bit)Apple® macOS® 10.12 SierraApple® OS X® 10.11 El CapitanApple® OS X® 10.13 High Sierra

Supported WebBrowsers

Windows® Internet Explorer®11.0.9600.18816 Update version11.0.47 or later2

Apple® Safari® 11 or later 3

Windows® Internet Explorer®11.0.9600.18816 Update version11.0.47 or later 4

Microsoft® Edge® version 41 or later

Google® Chrome™ version 61 or later 5

Apple® Safari® 11 or later6


Table 21: Client Computer Requirements for Site Management Portal UI, SCT, Metasys UI, andMetasys UI Offline



Supported MobilePhone OperatingSystems

N/A Android™ 5.1 or later

iOS 10.0 or later

Supported TabletOperating Systems

N/A Android 5.1 or later

iOS 10.0 or laterNetworkCommunication

Ethernet network interface card10/100/1000 Mbps

Ethernet network interface card10/100/1000 Mbps

Follow these guidelines andrecommendations:

• For optimal performance, use awired connection for computersbrowsing to the Metasys UI.

• Alternatively, for mobile phones andtablets, you can use a wireless IEEE802.11 connection on a 4G network.Browsing to the Metasys UI overa 3G communications network ispossible, but it is not recommendedor supported.

• High latency (also called lag or waittime) can cause the Metasys UI todisconnect from the ADS or ADX.

• To avoid high latency, werecommend a network with 20 mpbsupload speed.

• Signal strength impacts the overallperformance of the Metasys UI. Forthe best results, ensure you havea strong signal for your wirelessconnection.


Table 21: Client Computer Requirements for Site Management Portal UI, SCT, Metasys UI, andMetasys UI Offline



Monitor 1024 x 768 or higher resolutionand 16-bit or higher color depth

1024 x 768 or higher resolution and 16-bit or higher color depth

Other features may require 1600 x900 resolution. Additionally, you mayneed to set your monitor display atSmall 100% setting (Control Panel > AllControl Panel Items > Display).

1 Our computer platform and memory recommendations are not meant to imply that older or slower machines are notusable. Refer to the Network and IT Guidance Technical Bulletin (LIT-12011279) for more information regarding computer/server recommendations.

2 In Internet Explorer 11, select the Use Microsoft compatibility lists option, found under Tools > Compatibility ViewSettings, to ensure that websites appear and function correctly.

3 In OS X, you cannot view Graphics+ graphics in the Site Management Portal UI. You use the web browser to downloadthe Launcher application. After you install the Launcher application, you use the Launcher, not the web browser, to login to the Site Management Portal (SMP) UI.

4 The Metasys UI does not support Internet Explorer 11 on Windows 10 operating systems. In Internet Explorer 11,select the Use Microsoft compatibility lists option, found under Tools > Compatibility View Settings, to ensure thatwebsites appear and function correctly.Metasys UI does not support InPrivate Browsing. To exit InPrivate Browsing,close the browser window and open a new browser window.

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

6 Metasys UI does not support private browsing. To exit private browsing, click or tap Private in the browser window.Other web browsers, such as Mozilla® Firefox®, are not officially supported by the UI. However, the Metasys UI mayappear and function appropriately in these web browsers.

Application and Data Server (ADS) System RequirementsTable 22: Application and Data Server (ADS) System Requirements (5 Users)

Intel i7 processor latest version with at least four cores orbetter

2 x 500 GB hard disk (RAID 1)2 with 40 GB free space afterinstallation of all prerequisite software and before installationof ADS software. Configure RAID 1 (mirroring) with disk write-caching turned on.

Note: Prerequisite software includes the supportedoperating system, database software, .NET Framework,and any other software or service packs required foryour ADS configuration.

Recommended ComputerPlatform1

Graphics card (1 GB RAM, ATI® Technologies or NVIDIA®Corporation, 64-bit compatible [for 64-bit operating systems],Small Form Factor [SFF] if required)


https://support.google.com/chrome/answer/95464

Table 22: Application and Data Server (ADS) System Requirements (5 Users)

Required Minimum Memory3 16 GB RAM

Windows® 10 Pro and Enterprise Editions with CreatorsUpdate (version 1709 or later) (64-bit)

Supports:• SQL Server® 2016 Express with SP1 (64-bit)• SQL Server® 2014 Express with SP2 (64-bit)• SQL Server® 2012 Express with SP4 (64-bit)

Note: SQL Server 2012 with SP3 is not an automaticWindows update. For more information, refer tohttps://support.microsoft.com/en-us/kb/2979597.

Windows® 8.1 Pro and Enterprise Editions with Update 1 (64-bit)

Supports:• SQL Server® 2016 Express with SP1 (64-bit)• SQL Server® 2014 Express with SP2 (64-bit)• SQL Server® 2012 Express with SP4 (64-bit)

Note: SQL Server 2012 with SP3 is not an automaticWindows update. For more information, refer tohttps://support.microsoft.com/en-us/kb/2979597.

Supported Operating Systems4

and Database Software

Windows® 7 Professional, Enterprise, and Ultimate Editionswith SP1 (64-bit)

Supports:• SQL Server® 2014 Express with SP2 (64-bit)• SQL Server® 2012 Express with SP4 (64-bit)

Note: SQL Server 2012 with SP3 is not an automaticWindows update. For more information, refer tohttps://support.microsoft.com/en-us/help/3072779/sql-server-2012-service-pack-3-release-information.

Supported Operating Systems forMetasys Site Management PortalClient Computer

Windows® 10 Pro and Enterprise Editions with CreatorsUpdate (version 1709 or later) (64-bit)Windows® 8.1 Pro and Enterprise Editions with Update 1 (64-bit)Windows® 7 Professional, Enterprise, and Ultimate Editionswith SP1 (64-bit)Windows® 7 Professional, Enterprise, and Ultimate Editionswith SP1 (64-bit)Apple® macOS® 10.13 High SierraApple® macOS® 10.12 SierraApple® OS X® 10.11 El Capitan


https://support.microsoft.com/en-us/kb/2979597

https://support.microsoft.com/en-us/kb/2979597

https://support.microsoft.com/en-us/help/3072779/sql-server-2012-service-pack-3-release-information



Supported Web BrowserSoftware for Metasys SiteManagement Portal ClientComputers

Windows® Internet Explorer® 11.0.9600.18816 Updateversion 11.0.47 or later

Note: In Internet Explorer 11, select the Use Microsoftcompatibility lists option, found under Tools >Compatibility View Settings, to ensure that websitesappear and function correctly.

Apple® Safari® 11 or laterNotes:

• In OS X, you cannot view Graphics+ graphics in theSite Management Portal UI.

• You use the web browser to download the Launcherapplication. After you install the Launcher application,you use the Launcher, not the web browser, to log into the Site Management Portal (SMP) UI.

Supported Web BrowserSoftware for Metasys UI ClientDevices

Windows® Internet Explorer® 11.0.9600.18816 Updateversion 11.0.47 or later

Notes:

• The Metasys UI does not support Internet Explorer 11on Windows 10 operating systems.

• In Internet Explorer 11, select the Use Microsoftcompatibility lists option, found under Tools >Compatibility View Settings, to ensure that websitesappear and function correctly.

• Metasys UI does not support InPrivate Browsing. Toexit InPrivate Browsing, close the browser windowand open a new browser window.


Google® Chrome™ version 61 or laterNote: Metasys UI does not support incognito mode.To exit incognito mode, click or tap the X icon of thebrowser window or tab and then open a new browserwindow or tab. For more information on incognito modein Google Chrome, click here.

Apple® Safari® 11 or laterNote: Metasys UI does not support private browsing. Toexit private browsing, click or tap Private in the browserwindow. Other web browsers, such as Mozilla® Firefox®,are not officially supported by the UI. However, theMetasys UI may appear and function appropriately inthese web browsers.

Supported Virtual Environments Microsoft Hyper-V™

VMware®




Supported User Interfaces Site Management Portal (SMP)

Metasys UIAdditional Software Includedwith the ADS Software Download

Launcher software, Network Engine images, SummaryDefinition Examples, Microsoft .NET Framework (multipleversions), SQL Server Management Studio, Metasys DatabaseManager, Toggletunnel, SNMP Management InformationBase example files (MIBs), Report Viewer 2010 and ReportViewer 2012.

Optional Hardware Any network or local printer supported by the qualifiedWindows operating system

Optional Software Graphic Generation Tool

CCT software

SCT software

Metasys Export Utility software


2 For best performance, use Serial Attached SCSI (SAS) hard drives, not Small Computer System Interface (SCSI) harddrives.

3 For best performance, use the maximum amount of memory that the computer allows.4 Refer to the Network and IT Guidance Technical Bulletin (LIT-12011279) for specific Microsoft Windows operating system

settings that may be required for your Metasys system configuration.

Extended Application and Data Server System Requirements(Unified 10 or 25 User ADX)Table 23: Extended Application and Data Server System Requirements (Unified ADX Systems,10 or 25 Users)

Recommended ServerPlatform1

2.4 GHz Intel Xeon® 6 core single processor or better

2 x 600 GB hard disk (RAID 1) 22 with 40 GB free space after installationof all prerequisite software and before installation of ADS software.Configure RAID 1 (mirroring) with disk write-caching turned on.

Note: ADX prerequisite software includes the Windows operatingsystem, SQL Server software, Windows .NET Framework, and anyother software or SPs required by your ADX configuration.

Required MinimumMemory3

16 to 32 GB RAM


Table 23: Extended Application and Data Server System Requirements (Unified ADX Systems,10 or 25 Users)

Windows® Server® 2016 Standard Edition (64-bit)

Supports:• SQL Server® 2016 with SP1 (64-bit)• SQL Server® 2014 with SP2 (64-bit)• SQL Server® 2012 with SP4 (64-bit)

Note: SQL Server 2012 with SP3 is not an automaticWindows update. For more information, refer to https://support.microsoft.com/en-us/help/3072779/sql-server-2012-service-pack-3-release-information.

Windows® Server® 2012 R2 with Update 1 (64-bit)



Supported OperatingSystems4 and DatabaseSoftware

Windows® Server® 2012 (64-bit)



Supported OperatingSystems for MetasysSite Management PortalClient Computer

Windows® 10 Pro and Enterprise Editions with Creators Update(version 1709 or later) (64-bit)Windows® 8.1 Pro and Enterprise Editions with Update 1 (64-bit)Windows® 7 Professional, Enterprise, and Ultimate Editions with SP1(64-bit)Windows® 7 Professional, Enterprise, and Ultimate Editions with SP1(64-bit)Apple® macOS® 10.12 SierraApple® OS X® 10.11 El Capitan












Supported Web BrowserSoftware for MetasysSite Management PortalClient Computers

Windows® Internet Explorer® 11.0.9600.18816 Update version11.0.47 or later

Notes:

• In Internet Explorer 11, select the Use Microsoft compatibilitylists option, found under Tools > Compatibility View Settings, toensure that websites appear and function correctly.

• Metasys Advanced Reporting System and Energy Essentials supportInternet Explorer 11 on all computer platforms except on Windows10. On Windows 10 computers, both Internet Explorer 11 andMicrosoft® Edge® version 41 or later.


• In OS X, you cannot view Graphics+ graphics in the SiteManagement Portal UI.

• You use the web browser to download the Launcherapplication. After you install the Launcher application, youuse the Launcher, not the web browser, to log in to the SiteManagement Portal (SMP) UI.

Supported Web BrowserSoftware for Metasys UIClient Devices


Notes:• The Metasys UI does not support Internet Explorer 11 on

Windows 10 operating systems.• In Internet Explorer 11, select the Use Microsoft

compatibility lists option, found under Tools > CompatibilityView Settings, to ensure that websites appear and functioncorrectly.

• Metasys UI does not support InPrivate Browsing. To exitInPrivate Browsing, close the browser window and open a newbrowser window.


Google® Chrome™ version 61 or laterNote: Metasys UI does not support incognito mode. To exitincognito mode, click or tap the X icon of the browser windowor tab and then open a new browser window or tab. For moreinformation on incognito mode in Google Chrome, click here.

Apple® Safari® 11 or laterNote: Metasys UI does not support private browsing. To exitprivate browsing, click or tap Private in the browser window.Other web browsers, such as Mozilla® Firefox®, are not officiallysupported by the UI. However, the Metasys UI may appear andfunction appropriately in these web browsers.




Supported VirtualEnvironments

Microsoft Hyper-V™

VMware®

Supported UserInterfaces

Site Management Portal (SMP)

Metasys UIAdditional SoftwareIncluded with the ADXSoftware Download

Microsoft SQL Server 2014 Standard SP255

Microsoft .NET Framework Version 4.6.1

Launcher Software

Metasys Database Manager software

Metasys Advanced Reporting System software

Note: The Metasys Advanced Reporting System requires an ADX.The SCT computer must be online and accessible to the ADX atall times.

Optional Hardware Any network or local printer supported by the qualified Windowsoperating system

Optional Software Energy Essentials

Graphic Generation Tool

CCT

SCT

Metasys Export Utility


2 For best performance, use SAS hard drives (not SATA hard drives) that use RAID controllers with write-caching enabled.3 For best performance, use the maximum amount of memory. An ADX with 16 GB RAM has much greater performance

than an ADX with only 4 GB RAM.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.5 SQL Server software is only included with the MS-ADX10SQL product.

For SQL Server software, you must purchase SQL Server software licenses per the guidelines listedhere: SQL Server 2016, SQL Server 2014, and SQL Server 2012.


https://www.microsoft.com/en-us/sql-server/sql-server-2016-pricing

https://www.microsoft.com/en-us/licensing/product-licensing/sql-server-2014.aspx

http://download.microsoft.com/download/7/3/C/73CAD4E0-D0B5-4BE5-AB49-D5B886A5AE00/SQL_Server_2012_Licensing_Reference_Guide.pdf

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

Web/Application Server

2.4 GHz Intel Xeon® 6 core single processor or better.

2 x 600 GB hard disk (RAID 1)2 with 40 GB free space after installationof all prerequisite software3 and before installation of ADS software.Configure RAID 1 (mirroring) with disk write-caching turned on.

Notes:• Metasys Advanced Reporting System and Energy Essentials

must reside on the ADX web/application server.• Metasys UI must reside on the ADX web/application server.

Database Server

2.4 GHz Intel Xeon® 6 core single processor or better.

2 x 600 GB hard disk (RAID 1) with 40 GB free space after installationof all prerequisite software3 and before installation of ADS software.Configure RAID 1 (mirroring) with disk write-caching turned on.


SCT Computer

In a split configuration, you cannot install SCT on either the ADX web/application server computer or the ADX database server computer.Refer to the System Configuration Tool Catalog Page (LIT-1900198) forcurrent SCT computer requirements.

Required MinimumMemory4

16 GB RAM (web/application server and database server for 10 or 25user ADX)

Supported Operating

Systems5,6 withSupported DatabaseSoftware








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








Windows® 10 Pro and Enterprise Editions with Creators Update(version 1709 or later) (64-bit)Windows® 8.1 Pro and Enterprise Editions with Update 1 (64-bit)Windows® 7 Professional, Enterprise, and Ultimate Editions with SP1(64-bit) Windows® 7 Professional, Enterprise, and Ultimate Editionswith SP1 (64-bit) Apple® macOS® 10.12 SierraApple® OS X® 10.11 El Capitan











Notes:








Notes:

• The Metasys UI does not support Internet Explorer 11 onWindows 10 operating systems.

• In Internet Explorer 11, select the Use Microsoftcompatibility lists option, found under Tools > CompatibilityView Settings, to ensure that websites appear and functioncorrectly.




Apple® Safari® 11 or later

Note: Metasys UI does not support private browsing. To exitprivate browsing, click or tap Private in the browser window.Other web browsers, such as Mozilla® Firefox®, are not officiallysupported by the UI. However, the Metasys UI may appear andfunction appropriately in these web browsers.






VMware®






Launcher Software







CCT

SCT



2 For best performance, use SAS hard drives (not SATA hard drives) that use RAID controllers with write caching enabled.3 ADX prerequisite software includes the Windows operating system and SQL Server software, Windows .NET Framework,

and any other software or service packs required for your ADX configuration.4 For best performance, use the maximum amount of memory. An ADX with 16 GB RAM has much greater performance

than an ADX with only 4 GB RAM.5 The web/application and database servers must have the same operating system installed.6 Refer to the Network and IT Guidance Technical Bulletin (LIT-12011279) for specific Microsoft Windows operating system







Extended Application and Data Server System Requirements(Unified 50 or 100 User ADX)Table 25: Extended Application and Data Server System Requirements (Unified ADX Systems,50 or 100 Users)


Two processors: 2.4 GHz Intel Xeon® Dual Processors with aminimum of 8 cores each or better

6 x 300 GB 15,000 RPM hard disk (RAID 5)22 with 50 GB free space afterinstallation of all prerequisite software and before installation of ADSsoftware. Configure RAID 5 with disk write-caching turned on.

RAID Controller-PERC H710 with 1 GB CacheNote: ADX prerequisite software includes the Windows operatingsystem, SQL Server software, Windows .NET Framework, and anyother software or SPs required by your ADX configuration.

Required MinimumMemory

32 GB RAM







Supported OperatingSystems3 and DatabaseSoftware
















Windows® 10 Pro and Enterprise Editions with Creators Update(version 1709 or later) (64-bit)Windows® 8.1 Pro and Enterprise Editions with Update 1 (64-bit)Windows® 7 Professional, Enterprise, and Ultimate Editions with SP1(64-bit)Windows® 7 Professional, Enterprise, and Ultimate Editions with SP1(64-bit)Apple® macOS® 10.12 SierraApple® OS X® 10.11 El Capitan



Notes:










Notes:






Apple® Safari® 11 or laterNote:Metasys UI does not support private browsing. To exit privatebrowsing, click or tap Private in the browser window.

Other web browsers, such as Mozilla® Firefox®, are not officiallysupported by the UI. However, the Metasys UI may appear andfunction appropriately in these web browsers.



VMware®






Launcher Software










CCT

SCT



2 For best performance, use SAS hard drives (not SATA hard drives) that use RAID controllers with write caching enabled.3 Refer to the Network and IT Guidance Technical Bulletin (LIT-12011279) for specific Microsoft Windows operating system


For SQL Server software, you must purchase a SQL Server software licenses per the guidelineslisted here: SQL Server 2016, SQL Server 2014, and SQL Server 2012.

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


Web/Application Server


6 x 300 GB 15,000 RPM hard disk (RAID 5)2 with 50 GB freespace after installation of all prerequisite software3 and beforeinstallation of ADS software. Configure RAID 5 with disk write-caching turned on.

RAID Controller-PERC H710 with 1 GB cache

Notes:• Metasys Advanced Reporting System and Energy

Essentials must reside on the ADX web/application server.• Metasys UI must reside on the ADX web/application

server.





Table 26: Extended Application and Data Server System Requirements (Split ADX System, 50 or100 Users)

Database Server


6 x 300 GB 15,000 RPM hard disk (RAID 5) with 50 GB freespace after installation of all prerequisite software3 and beforeinstallation of ADS software. Configure RAID 5 with disk write-caching turned on.

RAID Controller-PERC H710 with 512 NV CacheSCT Computer

In a split configuration, you cannot install SCT on either the ADXweb/application server computer or the ADX database servercomputer. Refer to the System Configuration Tool Catalog Page(LIT-1900198) for current SCT computer requirements.

Required Minimum Memory4 32 GB RAM




Supported Operating Systems

and Database Software5,6













Supported Operating Systemsfor Metasys Site ManagementPortal Client Computer

Windows® 10 Pro and Enterprise Editions with Creators Update(version 1709 or later) (64-bit)Windows® 8.1 Pro and Enterprise Editions with Update 1 (64-bit)Windows® 7 Professional, Enterprise, and Ultimate Editions withSP1 (64-bit)Windows® 7 Professional, Enterprise, and Ultimate Editions withSP1 (64-bit)Apple® macOS® 10.12 SierraApple® OS X® 10.11 El Capitan

Supported Web BrowserSoftware for Metasys SiteManagement Portal ClientComputers


Notes:


• Metasys Advanced Reporting System and Energy Essentialssupport Internet Explorer 11 on all computer platforms excepton Windows 10. On Windows 10 computers, both InternetExplorer 11 and Microsoft® Edge® version 41 or later.



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





Supported Web BrowserSoftware for Metasys UI ClientDevices


Notes:


• In Internet Explorer 11, select the Use Microsoftcompatibility lists option, found under Tools >Compatibility View Settings, to ensure that websitesappear and function correctly.

• Metasys UI does not support InPrivate Browsing. To exitInPrivate Browsing, close the browser window and open anew browser window.


Google® Chrome™ version 61 or laterNote: Metasys UI does not support incognito mode. Toexit incognito mode, click or tap the X icon of the browserwindow or tab and then open a new browser window or tab.For more information on incognito mode in Google Chrome,click here.


Note: Metasys UI does not support private browsing. Toexit private browsing, click or tap Private in the browserwindow. Other web browsers, such as Mozilla® Firefox®,are not officially supported by the UI. However, the MetasysUI may appear and function appropriately in these webbrowsers.



VMware®

Supported User Interfaces Site Management Portal (SMP)

Metasys UIAdditional Software Includedwith the ADX SoftwareDownload



Launcher Software



Note: The Metasys Advanced Reporting System requires anADX. The SCT computer must be online and accessible tothe ADX at all times.







CCT

SCT



2 For best performance, use SAS hard drives (not SATA hard drives) that use RAID controllers with write caching enabled.3 ADX prerequisite software includes the Windows operating system and SQL Server software, Windows .NET Framework,

and any other software or service packs required for your ADX configuration.4 For best performance, use the maximum amount of memory. An ADX with 32 GB RAM has much greater performance

than an ADX with only 16 GB RAM.5 The web/application and database servers must have the same operating system installed.6 Refer to the Network and IT Guidance Technical Bulletin (LIT-12011279) for specific Microsoft Windows operating system



SCT Technical Specifications

For instances where the SCT is installed on the same computer as the ADS/ADX software, referto the specifications in the Application and Data Server (ADS/ADX) Product Bulletin (LIT-1201525). Forapplications where the SCT is installed on an ODS, refer to the specifications in the Open Data Server(ODS) Product Bulletin (LIT-12011943).

Note: Refer to the Network and IT Guidance for the BAS Professional Technical Bulletin(LIT-1201279) for specific Microsoft Windows OS settings that may be required for your Metasyssystem configuration.

Note: For information on licensing Microsoft SQL Server, refer to the Microsoft SQL ServerLicensing Guide for the edition of Microsoft SQL Server that you install.

Table 27: SCT System Requirements

Product Code TL-SCT-0: New project software

TL-SCT-6: Upgrade softwareRecommendedPlatform

Full ServerPlatform

Intel® Core™ 2 Duo E6700 or better (Intel Core 2 DuoE4300 minimum)

20 GB minimum free hard disk space available. Usea Solid State Drive (SSD) to significantly improveperformance compared to other types of hard disks.

16 GB RAM (4 GB RAM minimum)






DesktopComputerPlatform

Intel Core 2 Duo E6700 or better (Intel Core 2 Duo E4300minimum)

20 GB minimum free hard disk space available. Usea Solid State Drive (SSD) to significantly improveperformance compared to other types of hard disks.

16 GB RAM (4 GB RAM minimum)Windows Server 2016

Supports Microsoft SQL Server 2016 with SP1 (64-bit),Microsoft SQL Server 2014 with SP2 (64-bit), or SQLServer 2012 with SP4 (64-bit)Windows Server 2012 R2 with Update 1

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

Full ServerPlatforms

Windows Server 2012

Supports Microsoft SQL Server 2016 with SP1 (64-bit),Microsoft SQL Server 2014 with SP2 (64-bit), or SQLServer 2012 with SP4 (64-bit)Windows® 10 Professional or Enterprise (64-bit) withCreators Update (version 1709)

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

Note: The Windows 10 Creators Update (version1709) is required for any Windows 10 computerthat runs Metasys 10.0 software, including the ADS,ADX, ODS, and any Metasys software application.Verify this update before installing Metasys10.0 software. If you are upgrading to MetasysRelease 10.0 and do not have this update, youmust uninstall the previous release of all Metasyssoftware, apply the Windows 10 Creators Update(version 1709), then proceed with the Metasys 10.0upgrade.

SupportedOperating Systemsand DatabaseSoftware

DesktopComputerPlatforms

Windows 8.1 Pro and Windows 8.1 Enterprise Editionswith Update 1




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


Supported WebBrowser Softwarefor Metasys ClientComputers

Windows® Internet Explorer® 11.0.9600.18816 Update version 11.0.47 orlater, Microsoft® Edge® version 41 or later, Apple® Safari® 11 or later, andGoogle® Chrome™ version 61 or later.

Note: In Internet Explorer 11, select the Use Microsoft compatibilitylists option, found under Tools > Compatibility View Settings, toensure that websites appear and function correctly.

Other browsers, such as Mozilla® Firefox®, may also be used but arenot fully supported.

Note: Use the web browsers to download the Launcher application.After you install the Launcher application, you can use the Launcher tolog in to the SCT UI. You can also use the web browsers to access theSite Management Portal (SMP) UI, Metasys UI, Metasys UI Offline, andSCT Pro sites. You can also add a bookmark to the Metasys UI, MetasysUI Offline and SCT Pro sites.

NetworkCommunicationfor Metasys SystemConfiguration ToolClient Computers

Ethernet network interface card 10/100/1000 Mbps (100 Mbps network orbetter recommended)

Optional SoftwarePackaging

Note: A license for the SCT 13.0 is not included with the ADX, ADS, orODS software. You must obtain a license for each installation of the SCT.

Metasys UI and Metasys UI Offline Technical SpecificationsThe following tables list the technical specifications for the Metasys UI and Metasys UI Offline. Formore information about the ADS/ADX technical specification, refer to the Application and DataServer (ADS) and Extended Application and Data Server (ADX) Product Bulletin (LIT-1201525). For moreinformation about the ADS-Lite technical specifications, refer to the Metasys® Server Lite Installationand Upgrade Instructions Wizard (LIT-12012258). For more information about the SCT technicalspecifications, refer to the System Configuration Tool Catalog Page (LIT-1900198).Table 28: Metasys UI and Metasys UI Offline Client Technical Specifications for Phones andTablets

Supported Mobile PhoneOperating Systems

Android 5.1 or later

iOS® 10 or laterSupported TabletOperating Systems

Android 5.1 or later

iOS 10 or later


Table 29: Metasys UI and Metasys UI Offline Client Technical Specifications for Computers

Windows® 10 Pro and Windows 10 Enterprise Anniversary Update(version 1607 or later) (64-bit)

Web Browsers Supported:• Microsoft® Edge• Google® Chrome™ version 54

Windows 8.1 Pro and Windows 8.1 Enterprise with Update 1 (64-bit)

Web Browsers Supported:• Windows® Internet Explorer® 11.0.9600.18449 Update version

11.0.35 or later• Google Chrome version 54

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

Web Browsers Supported:• Windows Internet Explorer 11.0.9600.18449 Update version 11.0.35

or later• Google Chrome version 54

Windows 7 Professional, Enterprise, and Ultimate Editions withSP1 (32-bit)

Web Browsers Supported:• Windows Internet Explorer 11.0.9600.18449 Update version 11.0.35

or later• Google Chrome version 54

Apple® OS X® 10.13 High Sierra

Web Browsers Supported:• Apple® Safari® 11 or later• Google Chrome version 61

Apple® OS X® 10.12 Sierra

Web Browsers Supported:• Apple Safari 11 or later• Google Chrome version 61

Supported ClientComputer OperatingSystems and WebBrowser Combinations

Apple® OS X® 10.11 El Capitan

Web Browsers Supported:• Apple Safari 11 or later• Google Chrome version 61


Table 30: Metasys UI and Metasys UI Offline Client Technical Specifications for Web Browsers

Google® Chrome™ version 61 or later

Notes:• For better performance, we recommend using Google Chrome as

your preferred web browser for the Metasys UI and the Metasys UIOffline.

• The Metasys UI and the Metasys UI Offline does not support incognitomode. To exit incognito mode, click or tap the X icon of the browserwindow or tab and then open a new browser window or tab. Formore information on incognito mode in Google Chrome, refer tohttps://support.google.com/chrome/answer/95464?hl=en.

Windows® Internet Explorer® 11.0.9600.18449 Update version 11.0.35or later, and Microsoft Edge

Notes:• In Internet Explorer 11 to ensure that websites appear and function

correctly, select the Use Microsoft compatibility lists option, foundunder Tools > Compatibility View Settings.

• The Metasys UI and the Metasys UI Offline does not support InPrivateBrowsing. To exit In Private Browsing, close the browser window andopen a new browser window.

Apple® Safari® 11 or laterNote: The Metasys UI and the Metasys UI Offline does not supportPrivate browsing. To exit Private browsing, click or tap Private inthe browser window.

Supported WebBrowsers

General Web Browser Support Information:

Notes:• Other web browsers, such as Mozilla® Firefox®, are not officially

supported by the Metasys UI and the Metasys UI Offline. However,the Metasys UI and the Metasys UI Offline may appear and functionappropriately in other web browsers that are not officially supported.

• In supported web browsers on tablets and phones, Metasys UI andMetasys UI Offline does not support the desktop view options. To exitthe desktop view and load the mobile view:

- In Chrome, deselect the Request desktop site option.- In Safari, close the browser and open the Metasys UI and the

Metasys UI Offline.• Ensure your web browser has cookies enabled before browsing to

the Metasys UI and the Metasys UI Offline.• Ensure you have the Enable DOM Storage setting selected on the

client device. For Windows operating systems, go to Internet Options> Advanced > Security and verify the Enable DOM Storage setting isselected.


https://support.google.com/chrome/answer/95464?hl=en

Table 31: Metasys UI and Metasys UI Offline Client Technical Specifications for CommunicationChannels

SupportedCommunicationChannels

For optimal performance, we recommend a wired connection forcomputers browsing to the Metasys UI and the Metasys UI Offline.

Ethernet network interface card 10/100/1000 Mbps

Wireless IEEE 802.11 connection

4G Network

Notes:• The Metasys UI and the Metasys UI Offline may run over a 3G network.

However, browsing to the Metasys UI and the Metasys UI Offline over3G is not recommended or supported.

• High latency (also called lag or wait time) can cause the Metasys UIand the Metasys UI Offline to disconnect from the ADS or ADX, or SCTcomputer.

• Signal strength impacts the overall performance of the Metasys UI andthe Metasys UI Offline. For the best results, ensure that you have astrong signal for your wireless connection.

• To avoid high latency, we recommend a network with 20mbps uploadspeed.

CCT Technical SpecificationsTable 32: CCT System Requirements

Recommended Computer Intel® Core® 2 Duo E6700 or better (Intel Core 2 Duo E4300minimum)

20 GB free hard disk available (600 MB minimum)Recommended Memory Computer Platforms: 16 GB RAM (4 GB RAM minimum)Supported Operating System(OS) and Database Software

Windows® 10 Pro and Enterprise Editions with CreatorsUpdate (version 1709) (64 bit)

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

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

Note: The OS and software must both be 64-bit.


Table 32: CCT System Requirements

Windows 8.1 Pro and Windows 8.1 Enterprise Editions withUpdate 1 (64-bit)

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

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

Note: The OS and software must both be 64-bit.Windows 7 Professional, Enterprise, and Ultimate Editionswith SP1 (64-bit)

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

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

Note: The OS and software must both be 64-bit.Required Web BrowserSoftware for Metasys ClientComputers

Windows® Internet Explorer® 11.0.9600.18816 Update version11.0.47 or later, Microsoft Edge® version 41 or later, AppleSafari® 11 or later, and Google® Chrome™ version 61 or later.

Note: In Internet Explorer 11, select the UseMicrosoft compatibility lists option, found underTools>Compatibility View Settings, to ensure that websitesappear and function correctly.

Note: Web browser software is required if you wantto view the Controller Tool Help (LIT-12011147) online.However, you can also access this help system as a PDFfrom the software.

Network Communication forCCT Client Computer

Ethernet network interface card 10/100/1000 Mbps (100 Mbpsnetwork or better recommended)

Software Optionally InstalledDuring CCT Install

Microsoft .NET Framework version 4.6.1

Microsoft SQL Server 2014 Express software with SP2


Table 32: CCT System Requirements

Optional Connection Devices(Order Separately)

Bluetooth Commissioning Converter (MS-BTCVT-1)Note: The BTCVT is no longer available but continues to besupported.

Laptop with Bluetooth® wireless communications or acomputer with a USB Bluetooth converter

The USB Dongle with ZigBee® Driver (ZFR-USBHA-0)has a wireless connection through the CCT for wirelesscommissioning of the wireless enabled FEC and VMA16 fieldcontrollers. It also uses the ZCT in CCT.

The Mobile Access Portal (MAP) Gateway (TL-MAP1810-0Px ) atRelease 4.2 has a BACnet Router connection to the SA Bus of anIP field controller on your subnet.

BACnet Router Setup for Tool Connections—The BACnet Routersetup has been updated to allow the MAP Gateway to easilyconnect to the field controller and System Tools through aWIFI connection to perform file transfers and commissioningfunction. For further information, refer to the Mobile AccessPortal Gateway Product Bulletin (LIT-12011884).

The Portable BACnet/Internet Protocol to MS/TP Router (TL-BRTRP-0) routes information between BACnet/IP and MS/TP networks. For further information, refer to the PortableBACnet®/IP to MS/TP Router (Part No. 24-10414-2).

Adobe® Reader® software

Note: A PDF reader software is required for the Printfunction in CCT.

Optional Hardware Any network or local printer supported by the qualifiedWindows operating system

NxE85/NIE89/LCS85 Technical Specifications

Table 33: NxE85/NIE89/LCS85 Software System Recommendations for Installation/Upgrade

Product Code Number MS-NXE85SW-0 Network Integration Engine Software for 10,000 objects(new projects only software)

MS-NIE89SW-0 Network Integration Engine Software for 10,000 objects(new projects only software)

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

MS-15UKG-0 NXE/LCS Software Upgrade 15,000 additional objects(15,000 object upgrade for total of 25,000 objects)



RecommendedComputer Platform

Intel Xeon E5506, 2.13 GHz, 4 MB Cache

2 x 160 GB 7.2K SATA, 8.9 cm (3.5 in.) Cabled

3 Gbps, RAID 1 configuration with add-in SAS6/iR (SATA/SAS Controller)Recommended Memory 8 GB RAM minimumHard Disk 160 GB minimumSupported 64-bitOperating Systems andSoftware




Note: Microsoft .NET Framework 3.5 Service Pack (SP) 1 andMicrosoft .NET Framework 4.6.1 are required for any of theoperating systems.

Supported OperatingSystems for MetasysClient Computers

Windows® 10 Pro and Enterprise Editions with Creators Update(version 1709) (64-bit)

Windows® 8.1 Pro and Enterprise Editions with Update 1 (64-bit)

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

Apple® macOS® 10.12 Sierra

Apple® OS X® 10.11 El Capitan

Apple OS X 10.10 Yosemite

Note: Apple operating systems are supported for Metasys clientcomputers only. Also, in Apple OS X, you cannot view Graphics+graphics in the Site Management Portal UI.

Internal Optical Drive DVD ROM, SATASupported Web BrowserSoftware for MetasysSite Management PortalClient Computers

Windows® Internet Explorer® 11.0.9600.18816 Update version 11.0.47or later

Note: In Internet Explorer 11, select the Use Microsoftcompatibility lists option, found under Tools > CompatibilityView Settings, to ensure that websites appear and functioncorrectly.

Google® Chrome™ version 61 or later


Other browsers, such as Mozilla® Firefox®, may also be used but arenot fully supported.


Microsoft Hyper-V™, VMWare®



Network Communication Selectable Network Interface (if computer has multiple network cards,during NxE85/NIE89/LCS85 installation, select the network card thatwas configured for Metasys system use before installation)

Ethernet network interface card 10/100/1000 Mbps (100 Mbps or betterrecommended)

Recommended DataProtection

Uninterruptible power supply (UPS)

Smart-UPS SC 450VA, 280 W, 120 VAC input/output, NEMA 5-15R outputconnections, OEM Part No. SC450RM1U

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

Graphics+ Viewer RequirementsTable 34: Graphics+ Viewer System Requirements

Component DescriptionProduct Graphics+ Viewer built into Site Management Portal

(SMP) UI and System Configuration Tool (SCT) UI

Recommended Processor 11 22 33 Intel® Core™ 2 Duo E6700 or better (Intel Core 2 DuoE4300 minimum)

Memory 4 GB (2 GB minimum)Client Computer Operating System Windows® 10 Pro and Windows 10 Enterprise (64-bit)

Windows 8.1 and Windows 8.1 Pro (64-bit)

Windows 7 Professional, Enterprise, and UltimateEditions with SP1 (32-bit and 64-bit)

Windows Server® 2012 (64-bit)

Windows Server 2008 R2 with SP1 (64-bit)

Note: In OS X, you cannot view Graphics+graphics in the Site Management Portal UI.

Other Software Windows Internet Explorer® version 11

Note: In Internet Explorer 11, select the UseMicrosoft compatibility lists option, foundunder Tools > Compatibility View Settings,to ensure that websites appear and functioncorrectly.

Microsoft Silverlight® 5.0 or laterCommunication Ethernet network interface card 10/100/1,000 Mbps

(100 Mbps network or better recommended)

Note: We recommend using a wired ethernetconnection.

Wireless 802.11 connectionMinimum Screen Size 15 inch (21 inch recommended)


Table 34: Graphics+ Viewer System Requirements

Component DescriptionMinimum Screen Resolution 1024 x 768 (normal format)

1280 x 800 (wide screen format)Minimum Graphic Card Memory 64 MB

1 For large graphics, rendering the image is CPU intensive. In general, a higher performing CPU with multiple cores isrecommended.


3 We recommend client machines browsing to the Site Management Portal (SMP) UI for Graphics+ viewing have aCPU benchmark rating of approximately 2000. To view your client machine's CPU benchmark rating, go to https://www.cpubenchmark.net/cpu_list.php.

For more information on hardware and software requirements for the Graphic Generation Tool,refer to the Graphic Generation Tool Installation Instructions (LIT-12011685).

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

For information on See documentHow to License Metasys System Software Software Manager Help (LIT-12012389)Features, Benefits, and Specifications of theMetasys UI

Metasys UI Help (LIT-12011953)

Features, Benefits, and Specifications of theMetasys Offline UI

Metasys UI Offline Help (LIT-12012116)

Features, Benefits, and Specifications ofthe Application and Data Server/ExtendedApplication and Data Server (ADS/ADX)

Application and Data Server (ADS) and ExtendedApplication and Data Server (ADX) Product Bulletin(LIT-1201525)

Features, Benefits, and Specifications of theBACnet Open Data Server (ODS)

Open Data Server Product Bulletin (LIT-12011943)

Features, Functions, and Applications ofthe Network Automation Engines (NAEs)in the Metasys System, Including TechnicalSpecifications and Ordering Information

Network Engines Product Bulletin (LIT-12012138)

NAE Commissioning for KNX VendorIntegration

NAE Commissioning for KNX Vendor Integration(LIT-12013148)

NAE Commissioning for M-Bus VendorIntegration

NAE Commissioning for M-Bus Vendor Integration(LIT-12013149)

NAE Commissioning for Modbus VendorIntegration

NAE Commissioning for Modbus VendorIntegration (LIT-12023150)


https://www.cpubenchmark.net/cpu_list.php

https://www.cpubenchmark.net/cpu_list.php

Table 35: Related Documentation

For information on See documentNAE Commissioning for C·CURE 9000 AccessControl and victor Video ManagementIntegration

NAE Commissioning for C·CURE 9000 AccessControl and Victor Video Management Integration(LIT-12013151)

NAE Commissioning for Molex and CreeDigital Lighting Systems Integration

NAE Commissioning for Molex and CREE DigitalLighting Systems Integration (LIT-12013152)

NAE Commissioning for Simplex Fire SystemIntegration

NAE Commissioning for Simplex Fire SystemIntegration Application Note (LIT-12013060)

Features, Functions, and Applications ofthe Network Control Engine (NCE) 25 inthe Metasys System, Including TechnicalSpecifications and Ordering Information

Network Control Engine Product Bulletin(LIT-12011283)

Features, Benefits, and Specifications of theField Equipment Controller (FEC) Family

Metasys System Field Equipment Controllers andRelated Products Product Bulletin (LIT-12011042)

Features, Benefits, and Specifications of theCGx, CVx Equipment Controllers

Metasys CGx, CVx Equipment Controllers ProductBulletin (LIT-12013105)

Features, Benefits, and Specifications of theSystem Configuration Tool (SCT)

System Configuration Tool Catalog Page(LIT-1900198)

How to Install and Upgrade the ADS andADX Software; How to Install and UpgradeMetasys UI; How to Install the MetasysAdvanced Reporting System

Metasys Server Installation and UpgradeInstructions (LIT-12012162)

How to Install and Upgrade SQL ServerSoftware

SQL Server Installation and Upgrade Instructions(LIT-12012240)

How to Install and Upgrade the SCT andMetasys UI Offline Software

SCT Installation and Upgrade Instructions(LIT-12012067)

How to Install and Upgrade the ADS-Lite andMetasys UI Software

Metasys Server Lite Installation and UpgradeInstructions (LIT-12012162)

How to Install the ODS ODS Installation and Upgrade Instructions Wizard(LIT-12011945)

How to Use the Metasys Database Manager toManage Historical Data on an ADS

Metasys Database Manager Help (LIT-12011202)

How to Install the CCT Software CCT Installation Instructions (LIT-12011529)How to Install the Graphic Generation Tool Graphic Generation Tool Installation Instructions

(LIT-12011685)How to Use the Advanced Reporting System Metasys Advanced Reporting System and Energy

Essentials Help (LIT-12011312)How to Use Graphic Generation Tool Graphic Generation Tool Help (LIT-12011697)How to Configure an ADS/ADX to be SiteDirector, Use ADS Repositories, SynchronizeTime, Use a Network Printer, Accept Dial-UpConnections, and More

ADS/ADX Commissioning Guide (LIT-1201645)



For information on See documentHow to Configure an ODS to be a BACnetWorkstation or Site Director, Use ServerRepositories, Synchronize Time, Use aNetwork Printer, Accept Dial-Up Connections,and More

ODS Commissioning Guide (LIT-12011944)

How to Apply, Mount, Wire, Set Up, andStart the NAE35 and the NAE45, IncludingTechnical Specifications and OrderingInformation

NAE35/NAE45 Installation Instructions (Part No.24-10050-6)

How to Apply, Mount, Wire, Set Up, and Startthe NAE55 Including Technical Specificationsand Ordering Information

NAE55 Installation Instructions (Part No.24-10051-43)

How to Apply, Mount, Wire, Set Up, andStart the NAE55-S, Including TechnicalSpecifications and Ordering Information

NAE55-S Installation Instructions (Part No.24-10051-108)

How to Apply, Mount, Wire, Set Up, and Startthe NCE25, Including Technical Specificationsand Ordering Information

NCE25 Installation Instructions (Part No.24-10143-63)

How to Set Up an NAE35, NAE45, and NAE55for Network Connectivity and Access the NAEUser Interface to Set the Basic Parameters

NAE Commissioning Guide (LIT-1201519)

How to Set Up an NAE85 for NetworkConnectivity and Access the NAE85 UserInterface to Set the Basic NAE85 Parameters

NAE85 Commissioning Guide (LIT-12011044)

How to Set Up a LonWorks® Control Server(LCS) 85 for Operation on the Metasys®Network

LonWorks Control Server (LCS) 85 CommissioningGuide (LIT-12011568)

How to Use the SCT, Including Setting UpArchive Databases Offline and Basic N2Online Network Setup

Metasys SCT Help (LIT-12011964)

How to use SCT Pro, including themaintenance of site backups andprovisioning a new Network Engine

Metasys SCT Pro Help (LIT-12013035)

How to Integrate an N2 Network into theMetasys System

N2 Integration with the NAE Technical Bulletin(LIT-1201683)

How to Install the NAE Update Tool andUpdate NAEs From One Release to Another

NAE Update Tool Help (LIT-12011524)

Network Information (Including SecurityRisks)

Network and IT Guidance Technical Bulletin(LIT-12011279)

How to Apply and Engineer a Metasys SmokeControl System that Complies with theMetasys System UL 864 10th Edition UUKL/ORD-C100-13 UUKLC Smoke Control Listing

Metasys System UL 864 9th Edition UUKL/ORD-C100-13 UUKLC Smoke Control System TechnicalBulletin (LIT-12011252)



For information on See documentDevices and Logic Used to Implement a 10thEdition Smoke Control System for SingleStory Mall, Warehouse, and MultistoryBuilding

Metasys System UL 864 UUKL 9th Edition UUKL/ORD-C100-13 UUKLC Standard Smoke ControlApplications Application Note (LIT-12011308)

How to Integrate a Fire System into theMetasys Network

Metasys System Extended Architecture Fire SystemIntegration Using the IFC BACnet® GatewayApplication Note (LIT-1201993)

NAE Compliance with American NationalStandards Institute (ANSI)/AmericanSociety of Heating, Refrigerating, and Air-Conditioning Engineers (ASHRAE) Standard135-2004, BACnet® Protocol

NAE/NCE Protocol Implementation ConformanceStatement (LIT-1201532)

How to Install the Launcher Software Launcher Installation Instructions (LIT-12011783)How to Use the Launcher Software toShorten the UI Access Time and Manage Sites

Launcher Tool Help (LIT-12011742)

How to Use Web Service Technology forSecure Access to the Metasys System

Metasys System Secure Data Access DLL TechnicalBulletin (LIT-1201663)

How to Create and Modify Users and Roles,Configure User Profiles, Assign System AccessPermissions, Assign All Items NavigationView Permissions, and Unlock User Accounts

Security Administrator System Technical Bulletin(LIT-1201528)

How to Set Up an MS/TP Communications Bus MS/TP Communications Bus Technical Bulletin(LIT-12011034)

BACnet/IP Configuration Metasys IP Networks for BACnet/IP ConfigurationGuide Technical Bulletin (LIT-12012458)

How to Set Up an NAE as a BACnet/IP orBACnet MS/TP System Integrator in a MetasysNetwork

BACnet Controller Integration with NAE/NCE/ODSTechnical Bulletin (LIT-1201531)

How to Set Up an NAE or LCS85 as aLonWorks Network Integrator

LonWorks Network Integration with NAE and LCSTechnical Bulletin (LIT-1201668)

How to Configure and Enable the DemandLimiting and Load Rolling (DLLR) Features onthe System

DLLR Technical Bulletin (LIT-12011288)

How to Use CCT Software Controller Tool Help (LIT-12011147)ZFR1800 Series Wireless Field Bus System ZFR1800 Series Wireless Field Bus System Technical

Bulletin (LIT-12011295)WNC1800/ZFR182x Pro Series Wireless FieldBus System

WNC1800/ZFR182x Pro Series Wireless Field BusSystem Technical Bulletin (LIT-12012356)

TEC Wireless Thermostat Controller System TEC Series Wireless Thermostat Controller SystemTechnical Bulletin (LIT-12011414)

WRS Series Many-to-One Wireless RoomTemperature Sensing System

WRS Series Many-to-One Wireless RoomTemperature Sensing System Technical Bulletin(LIT-12011094)



For information on See documentTE-7800 Series One-to-One Wireless RoomTemperature Sensing System

TE-7800 Series One-to-One Wireless RoomTemperature Sensing System Technical Bulletin(LIT-12011097)

WRZ-7850 One-to-One Wireless RoomTemperature Sensing System

WRZ Series One-to-One Wireless Room SensingSystem Technical Bulletin (LIT-12011641)


metasys system configuration guide

Documents