Automated system-wide control and coordination - Metasys - LIT-1201526 - General System Information - Metasys System - 13.0.50

Metasys System Product Bulletin

Product name
Metasys System
Document type
Product Bulletin
Document number
Revision date
Product status

Metasys network engines provide automated system-wide control and coordination over multiple field devices under one or more field device networks. Some examples of the system-wide control coordination capabilities include:

  • Scheduling: enables network engines to automatically command any equipment or system integrated with Metasys to a preferred operational state (such as On/Off, Occupied/Unoccupied, Economy/Comfort, or Heating/Cooling/Economizer/Auto) based on a user-defined schedule. Operating parameters can be set according to time of day, days of the week, holidays, or calendar dates.
  • Alarm and Event Management: enables the network engines to generate alarms based on user-defined criteria; to send alarm and event messages to web browsers, email servers, Network Management Systems, and serial printers; and to store and view alarm and event logs on the network engine and transfer the data to a Metasys Server.
  • Network-Wide System Interlocking: enables network engines to collect data from field devices, make logical comparisons between the data, and issue relevant commands to other field equipment or systems, anywhere on the network.
  • Transaction Recording: audits and logs all user actions performed through the network engine. Operators can review these logs to understand what changes have been made to the system, who made them, and when.
  • Historical Data: can be collected and stored by network engines for any monitored data point value based on user-defined intervals or on a change of value. Network engines can transfer the data logs to the Application and Data Server at defined intervals or when the network engine logs are full.
  • Totalization: allows network engines to calculate rolling sums of any monitored data point value stream. Operators can use this information to monitor runtime information useful for service, maintenance, and early identification of building system problems.
  • Optimal Start: enables network engines to automatically determine the best time to start heating and cooling systems to ensure that the facility is conditioned for occupancy. It adjusts to seasonal variations and reduces energy use.
  • Demand Limiting Load Rolling (DLLR): enables network engines to monitor energy (electricity, gas, steam, or water) meters and automatically shed equipment loads according to user-defined levels. Demand Limiting helps manage utility demand charges, and Load Rolling controls equipment operating levels to reduce total energy consumption. Comfort overrides prioritize equipment shedding. You can create DLLR objects only through SCT or SMP. You cannot create DLLR objects through Metasys UI or JCT.