METASYS

Conceptual view of Metasys building automation, HVAC and energy systems

What Is Metasys? Building Controls, N2 Networks and BACnet Integration

Metasys is Johnson Controls’ building automation and management platform. It brings equipment control together with supervision, alarms, schedules and operational records. In a building automation system, that means a combination of controllers, network engines and software—not a single cable type or a single communications protocol. [1]

The phrase “Metasys N2” in a drive manual refers to a specific field-network interface. It does not describe everything that a Metasys installation can do. A site may also use BACnet and other integration paths. The useful engineering question is therefore not just “Will it connect?” but “Which values and commands can this exact device exchange, through which supported path?” [6] [19]

Documentation scope: Product examples in this article use the Metasys System Product Bulletin, Release 15.0. Command behavior is referenced to Metasys UI Help, 8.1. These are identified documentation versions, not a claim that every installed site has the same capabilities or that 15.0 is the newest release.

What a successful integration actually delivers

A controller being online is only the first acceptance milestone. Metasys integration services can normalize third-party data into BACnet objects for use by the platform. The engineering work is to establish what each point represents and how it will be used. A temperature reading, an operator setpoint and an equipment status must remain distinguishable after they reach the supervisory display. [6]

Start with a point schedule, not a graphic. For each important value, record the source device, network address, point or object reference, data type, engineering units, read/write access, expected update behavior and loss-of-communication treatment. Add alarm and historical-recording requirements where needed. A label such as Fan Speed is incomplete unless it identifies whether the value is a demand, a drive output frequency or independently measured rotation.

For a BACnet product, obtain its Protocol Implementation Conformance Statement (PICS). This manufacturer document identifies the BACnet functionality implemented by that product. Match the required objects and services to the actual implementation. BTL certification adds evidence of independent product testing, but it does not certify your point mapping, sensor installation or entire mechanical control sequence. [17] [18]

This distinction matters when a project is described as “open.” A supported network interface gives you a route to interoperability; it does not guarantee that every internal variable is exposed or writable. Define the information exchange before choosing a gateway, and verify the required access on the exact model and firmware rather than relying on a family-level product description.

Follow one signal through an air-handling unit

Consider an illustrative AHU application in which a local controller regulates duct pressure and Metasys supervises its operating setpoint and status. The differential pressure sensor must be connected to the intended pressure locations. Pressure across a filter and duct pressure relative to a reference are different measurement duties; similar-looking labels do not make those points interchangeable.

Assumptions for this example: A linear transmitter covers 0–1000 Pa with a 4–20 mA output. Its measured signal is 12 mA. These figures are selected for the calculation; they are not specifications of a particular Metasys controller or transmitter.

Pressure = (12 − 4) / (20 − 4) × 1000 = 500 Pa
Operating setpoint = 600 Pa
Control error = 600 − 500 = 100 Pa

With the correct 4–20 mA scaling, the controller and the supervisory point should agree on 500 Pa. The 100 Pa error alone does not determine a particular fan frequency. The active control algorithm, tuning, output limits and equipment state determine the response.

Keep separate points for: measured pressure, effective setpoint, fan demand, actual run feedback and communication health. One animated fan symbol is not a substitute for this information.

A useful acceptance test compares the physical signal, the controller’s engineering value and the displayed value at the same time. If the controller is correct but the display is not, investigate the source reference and any additional scaling. If the input is already wrong, changing the network will not repair the measurement. Successful communications and accurate measurement are different acceptance criteria.

Who owns the command?

Metasys UI can show the Priority Array for applicable points. A higher-priority active command can prevent another command from taking effect, even when the new value looks reasonable. The point’s command capability, user permissions and existing overrides all matter. A temporary or permanent override can also be released through the supported interface. [12]

For example, a maintenance override may still hold an output while the normal schedule is asking for automatic operation. This is a diagnostic scenario, not an instruction to force the output at a stronger priority. Identify the active owner and the reason for the override, use the authorized release procedure, and confirm that the intended sequence resumes control. A successful software command is not independent proof that the fan has started.

A lost display is not the same failure as a lost field controller

Metasys uses distributed components, and supported equipment controllers execute programmable control logic locally. That makes it important to locate the control function rather than assume it lives in the operator’s browser. A local loop whose application, power and required inputs remain available may continue when supervisory access is lost. A function that depends on a remote value or upstream decision needs separate treatment. [2]

Design implication: Test browser/server access loss, network-engine loss, field-bus interruption and controller power loss as different events. For each event, identify what remains local, what becomes unavailable and how the application handles stale inputs or missing commands. Do not write a universal “everything keeps running” or “everything stops” statement into the operating procedure. Neither follows from the platform name.

Controllers, engines, servers and engineering tools

Equipment controllers perform the local DDC function—Direct Digital Control—for the equipment application. SNE network engines provide supervisory integration, with different models offering different capacities and protocol support. In the Release 15.0 product table, the SNE1050x permits 50 mapped N2 devices per trunk, while the M4-SNE110Lx-0 has no N2 support. Those are model-specific limits, not a universal N2 network specification. [3]

SNC network control engines combine supervisory duties with onboard I/O and programmable equipment control. They illustrate why an engine should not automatically be treated as only a communications gateway. SNE and SNC are distinct product families, and the control functions present in a particular project must be checked in its application and hardware documentation. [4]

ADS means Application and Data Server; ADX means Extended Application and Data Server. Server software brings together site information and supports functions such as historical storage and the Metasys UI. A separate ADS/ADX is not mandatory for every possible site arrangement. Select the server architecture around the required scale, history and user access rather than treating it as the device that directly closes every control loop. [5]

The familiar controller → engine → server arrangement is not the only supported path. Release 15.0 documentation also describes licensed Server IP Controller Integration, allowing suitable IP equipment to be integrated directly without an intervening network engine. This option has its own support and licensing conditions. A drawing that forces every point through an SNE can therefore misrepresent an actual installation. [9]

CCT and SCT solve different engineering problems. The Controller Configuration Tool supports application development, simulation and commissioning for compatible equipment controllers. The System Configuration Tool works with offline engine/server and site configuration archives, downloads and backups. Controller packages, licenses and software compatibility must match the project. The operator UI is not a replacement for either engineering workflow. [10] [11]

Identify the network on each side of the connection

N2 is associated with legacy Metasys field installations and compatible replacement or third-party equipment. BACnet MS/TP, BACnet/IP and BACnet/SC are separate network options in the supported controller families. An Ethernet connection does not establish support for every IP-based application, and a label saying “Metasys” does not tell you which option is actually enabled. [19]

On supported Johnson Controls equipment, the FC Bus is the BACnet MS/TP field-controller network. The SA Bus connects a controller to supported sensors, expansion I/O and actuator-side equipment. Read the purpose of each communication port before wiring it. A familiar terminal layout is not evidence that an arbitrary device belongs on that port. [7] [8]

RS-485 describes an electrical interface, not a translator between N2 and Modbus RTU. Two products can use similar serial wiring and still be unable to exchange meaningful messages. They need a common protocol or an appropriate integration gateway. Likewise, the master–slave terminology found in an N2 manual should not be used as a complete description of every communication relationship in the building.

Other documented integration paths include LonWorks, Modbus and M-Bus. Check the chosen engine, interface hardware, driver and license rather than assuming that every port supports the whole list. A meter shown in Metasys through a gateway has not thereby become a native BACnet meter. [6]

A documented N2 example: the Yaskawa E7

The industrial communication archive includes a practical legacy example: Yaskawa E7. Its Metasys N2 technical manual specifies H5-08 = 1 for N2 and H5-02 = 3 for 9600 baud. Reference and run-command sources are separate settings, b1-01 and b1-02. Apply these details only to the E7 implementation covered by that manual. [16]

The manual also provides configurable communication-loss behavior, including stop or continued-operation options. It distinguishes an established connection being lost from a start-up with no connection. A disconnected N2 cable is therefore not a universal stop command. [16]

Not a start-up recipe: These settings demonstrate how to read a device-specific integration document. They are not authorization to change the run source or operate machinery remotely. Confirm the exact hardware and firmware, agree on a safe test plan, and control the mechanical risks before any write or functional test.

Build acceptance around evidence, not discovery alone

Document the starting point. Record complete product codes, installed releases, protocol paths, addresses, point schedules and available backups. For an existing site, obtain recoverable engineering archives rather than assuming that screenshots contain enough information to recreate the application. Identify both the update procedure and the route back to the known configuration.

Prove the physical and read-only path first. Check power, port assignment, topology, shielding and termination against the relevant device manuals. Do not assume a universal A/B convention or apply one serial product’s termination value to every bus. Then make a controlled, known change at the measurement source and confirm the correct point, units and response at the controller and supervisory layer.

Test operational behavior separately. Under the agreed authorization and safety arrangements, verify the permitted setpoint changes, actual equipment feedback, alarms and restoration of normal control. Record what happens to each critical dependency during the defined communication-loss tests. Include any remaining manual overrides and make their owner and expiry clear.

This process resembles good SCADA commissioning, but Metasys-specific tools, licensing and point semantics still apply. Treat the network drawing, control sequence and point schedule as complementary documents: the first shows the connection, the second explains the intended behavior, and the third identifies the data used to implement it.

Use the symptom to choose the next check

A whole trunk is missing: Investigate common causes first—shared power, the selected port/protocol, trunk wiring, a short circuit or engine availability. One device is missing: Check its local power, address, configured protocol and support in the selected integration. These observations help separate a shared-path fault from a device-specific one; they do not by themselves identify the failed component.

A value is online but implausible: Compare the source reference, type, units, scaling and validity. The value is correct but a command has no effect: Separate read access from write access, then inspect command ownership and the equipment’s local/remote selection. Increasing traffic or changing a baud setting will not correct a misidentified point or an active override.

Live readings work but history is incomplete: Move the investigation to recording configuration, transfer, timestamps and storage. A functioning field link does not prove that a trend has been configured or retained. Conversely, an old historical value does not prove that the device is online now.

Size the history workload independently of the network

Metasys servers can extend the storage and management of historical data. Treat alarms, trends and audit records as different information: a condition needing attention, a time series, and a record of an action. As with a datalogger, a displayed live value is not automatically a stored sample. Decide what to record and why before choosing the retention settings. [5] [13]

Illustrative workload: If 80 points are recorded continuously once every 60 seconds, they generate 80 × 1440 = 115,200 samples per day. This is arithmetic for the assumed schedule, not a storage-size estimate or a product capacity limit. Change-based collection, gaps, data types and database overhead produce different workloads. Device count, object count and historical sample count must not be used interchangeably.

Check clock consistency and engineering units before comparing records. Measurement accuracy and calibration remain separate from database operation. For consumption or carbon-footprint calculations, document the period, meter multiplier, gaps and applicable conversion factors. A better-looking dashboard is not evidence that a building has saved a measured amount of energy.

Security belongs to the complete communication path

Johnson Controls documents encrypted web communication, identity management, certificates and auditing for applicable Metasys components. HTTPS in the browser does not establish encryption on a legacy N2 trunk. BACnet/SC likewise needs supported components and appropriate configuration. Include the building controls network in the site’s industrial cybersecurity plan rather than treating a secure login page as the whole security boundary. [14]

Recommended operating checks include individual accounts, least-privilege access, controlled remote connections, reliable time settings, managed certificates and recoverable backups. Plan compatibility checks and rollback before an update. Connecting an older device to an IP-capable gateway does not by itself add security features inside that older device.

Fire information and certified smoke control are different scopes. Johnson Controls separately documents specifically listed smoke-control configurations; the referenced section identifies a Release 14.0 configuration. A fire alarm displayed on an ordinary building-management screen is not proof that the entire installation meets that specialized scope. [15]

What to preserve when modernizing an N2 installation

Inventory the existing network and application before choosing replacements. Keep the actual point meanings, write permissions, control ownership, alarm behavior, trends and required fallback actions visible in the migration plan. A controller that physically fits the panel is not necessarily a functional substitute, and a new user interface does not automatically recreate the old control sequence.

The goal is a defined, testable system: the correct data reaches the intended application, authorized commands have the expected ownership, physical feedback confirms the result, and loss-of-communication behavior is documented. That is a more useful definition of integration than simply putting every device on the same screen.

Sources and documentation scope

The links below go to the relevant manufacturer sections rather than a generic product homepage. Sections of the same bulletin are separated to make specific claims traceable. The numerical examples are not field measurements.

[1] Metasys system. Johnson Controls, LIT-1201526, Release 15.0. Platform scope and principal building-management functions.

[2] Distributed; Onboard control logic. Johnson Controls, LIT-1201526, 15.0. Distributed architecture and programmable equipment-level logic. Actual failure behavior depends on the installed application.

[3] SNE series network engines. Johnson Controls, LIT-1201526, 15.0. SNE model comparison, including N2 support and separate device/object limits.

[4] SNC series network control engines. Johnson Controls, LIT-1201526, 15.0. SNC supervisory functions, onboard I/O and equipment control.

[5] Metasys Server; Server comparison. Johnson Controls, LIT-1201526, 15.0. Server role, ADS/ADX names and differences within the server family.

[6] Field equipment network management and integration. Johnson Controls, LIT-1201526, 15.0. Field-network integrations and normalization of integrated data into BACnet objects.

[7] Field Controller (FC) Bus. Johnson Controls, LIT-1201526, 15.0. The FC Bus on supported equipment-controller families.

[8] Sensor/Actuator (SA) Bus. Johnson Controls, LIT-1201526, 15.0. SA Bus connections to supported sensors, expansion I/O and associated equipment.

[9] Server IP Controller Integration. Johnson Controls, LIT-1201526, 15.0. L