General Terms for I&C (BMS) Deliveries

For integration into the Mervis SCADA cloud system (central monitoring) and to ensure the proper operation of technical equipment, the following standards must be met for I&C deliveries within individual technological systems:

• Network Communication: An Ethernet network must be used for data transfer between controllers and the central station, as well as between controllers themselves.
• Protocols: Modbus TCP or BACnet must be used for all data points involving the delivered technology and existing technology control. Other open protocols may be permitted only after written approval by the client.
• Data Access: The system must allow both monitoring and writing for all critical data points. A description must be provided for each data point to facilitate integration, including information on safe values and ranges.
• Source Code Handover: Complete source code for all installed control systems must be handed over upon project completion to ensure future modifications are not dependent on the original supplier.
• Credentials: All access passwords, administrative codes, and logic modification keys must be included in the handover.
• Metering: All installed meters must be equipped for remote data transfer via M-Bus or Modbus protocols to the I&C system.
• Schedules: The I&C system must allow for the dynamic modification of time schedules where relevant to the technology.
• Project Oversight: Compliance with these requirements must be monitored throughout project implementation. Any equipment substitutions or deviations must be consulted with the client to prevent disruption of the planned data communication. It is recommended that a representative responsible for central integration attends selected project review days.

If local visualization is part of the delivery, every provided system should enable the operator to successfully pass the Easter Test. This specifically entails:

• Data Logging: Storing all data points available in the visualization with a period of 1–5 minutes.
  • At a minimum, this must include the: Recommended Data Points.
• Retention: Storing data indefinitely (for at least 2 years).
• Time Programs: Allowing user changes to time programs, ideally using exceptions.

Furthermore, it should be possible to provide historical data to other systems in an open manner via:

• Access through a documented API.
• Data storage in an open data management system (such as standard SQL or NoSQL databases).

As part of the handover protocol, all access and administrator usernames and passwords for all components of the visualization system must be provided.