Because the Metasys system uses the standard data formats and communication protocols of the BAS and IT worlds, it is compatible with the networking infrastructure found in most buildings today. The Metasys system integrates building equipment and systems using BACnet/SC, BACnet/IP, BACnet MS/TP, N2, LonTalk®, MODBUS, M-Bus, KNX, OPC UA and web services communication technology. The Metasys system supports BACnet Protocol Revision 18. Johnson Controls BACnet devices and third-party BACnet devices can be connected directly to the IP Ethernet network or to the MS/TP Field Bus. BACnet/IP is also used to integrate SIMPLEX Fire Systems and lighting systems from preferred partners into the Metasys system.
LonWorks® controllers from Johnson Controls or LonMark® certified devices from other manufacturers can integrate into the Metasys system architecture. In a similar fashion, prior generations of N2-based Metasys components can integrate into the newer architecture, helping to modernize legacy Metasys installations. The Metasys system also communicates to third-party devices using MODBUS, KNX, and M-Bus integrations. Regardless of the protocols used, the data is available for display in the Metasys UI, for archiving in application servers, and for transmission to other devices on the IP network.
- HTTPS with TLS 1.3 as the secure communication protocol between network engines, Application and Data Servers (ADS), Open Application Servers (OAS), and web browsers
- Simple Network Management Protocol (SNMP) for alarm traps and object queries in the Management Information Base (MIB)
- Simple Network Time Protocol (SNTP) for network time synchronization
- Simple Mail Transfer Protocol (SMTP) for email message transfer
- Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS) for device naming and dynamic network addressing
- Simple Object Access Protocol (SOAP) and XML, which transfer data between components of the system and make the data available to enterprise applications through the use of published web services
- Wireless communication standards, including Wi-Fi (used in network communication) and ZigBee® (for field controller and sensor mesh)
- The Microsoft® Active Directory® service, which provides a standard IT
integration of the Metasys system into a customer's existing Active
Directory service infrastructure for the SMP UI and Metasys UI login
authentication purposes. Starting at Release 11.0, Active Directory includes
Microsoft Active Directory Federation Services (ADFS) in addition to Active
Directory LDAP authentication, with the ability to enforce two-factor
authentication (2FA) when the ADFS Server is configured for 2FA. Note: ADFS and AD/LDAP are not supported on SNx engines.
- The SQL database format, used by the Metasys server to store historical data, which facilitates the use of Microsoft SQL Server® software
- A growing suite of REST-compliant Application Programming Interfaces (APIs), including an API that enables reading, writing, and commanding of one or more Metasys objects/properties to provide a secure way to bi-directionally integrate with third-party applications.
- MQTT integration driver supports bidirectional communication between network engines and a generic MQTT broker to enable exchanging Metasys data with popular IoT platforms and applications.