X Close
Network Automation Engine

Network Engines

Metasys® Network Automation Engines, Network Control Engines & Network Integration Engines

Metasys® Network Engines provide management and system-wide control over one or more networks of equipment controllers. These Network Engines can be networked together for scaling up on large projects or networked with an Application and Data Server for additional functionality and unification. Our Network Engines feature several optional communication port selections for integrating both Metasys equipment controllers and hundreds of non-Metasys devices, and they feature software that normalizes data retrieved from these devices so a common set of control processes can be applied to each.

Features and Benefits

Examples of Automated System-Wide Control and Coordination with Network Engines:

  • Scheduling: enables network engines to automatically command mechanical or electrical equipment to a desired 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, pagers, 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 an Application and Data 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 controllers, 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.
Disclaimer: Lorem ipsum copy about spam sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliquadolore magnam aliquam quaerat voluptatem. sed do eiusmod tempor incididunt ut labore et dolore magna aliquadolore magnam aliquam quaerat voluptatem.
Cancel
Download
/-/media/jci/insights/2015/be/images/be_thumb_cs_central_bucks.jpg
Philadelphia, PA, US
When school officials at Central Bucks School District wanted to trim budgets, they insisted that nothing compromise the learning environment. Through a performance contract with Johnson Controls, school officials say they already are saving $1.5-2M in utility costs annually.
Other People Have Viewed

> Contact us for more information on Building Management

Call 877-976-9593

> Contact us for more information on Building Management

Call 877-976-9593

jQuery("a[href*='.docx'],a[href*='.pdf']").attr("onclick","LogClick(this);")