Centralised Monitoring
One redundant platform for every utility, building and production system on site
Our centralised monitoring platform is a redundant SCADA and historian system that brings energy, building, utility and production data into one set of screens, alarms and reports for data centres, pharma sites and industrial plants.
Last updated:
ROOMS · DIFFERENTIAL PRESSURE / TEMP / RH
Filling A
15Pa
21.4°C · 45%
Filling B
14Pa
21.8°C · 47%
Buffer
11Pa
22.1°C · 49%
Change rm
8Pa
22.6°C · 52%
Corridor
6Pa
22.9°C · 50%
Wash
12Pa
23.0°C · 55%
TREND · FILLING A · DP24 h
AUDIT TRAIL · 21 CFR PART 11READ-ONLY
| 10:42:18 | DP high SP · Filling A | 18 → 17 Pa |
| 10:41:55 | Alarm ack · Change rm | DP warning |
| 09:03:07 | Report signed · Daily EMS |
What the system does
Most sites run their EMS, BMS, utilities and production machines as separate islands, each with its own screen, alarm list and export format. Operators chase problems across systems, and auditors receive reports that do not line up.
Our centralised monitoring platform collects data from every one of these systems over standard industrial protocols, stores it in a redundant historian and presents it through operator stations, web thin clients and mobile alerts. The architecture is the one we build and run today: primary and secondary SCADA servers, redundant database servers with real-time replication, and a redundant industrial Ethernet ring down to the controllers.
For regulated sites, the same platform carries the controls required by 21 CFR Part 11: electronic records, electronic signatures, a non-editable audit trail and automated PDF reports with QA review blocks, backed by GAMP 5 validation documentation.
- 01
Multi-protocol data acquisition
Connects to field devices and controllers over Modbus TCP, OPC UA, OPC DA, BACnet IP, SNMP, MQTT, Profinet, EtherNet/IP and RS-485. New and legacy equipment report into the same tag database.
- 02
Redundant server architecture
Primary and secondary SCADA servers, an application, report and web server, and redundant SQL database servers with real-time replication. A server failure does not stop data collection or alarming.
- 03
Alarm management and alerts
Central alarm list with generation, normalisation and acknowledgement times, user and comment. Alerts go out by email, SMS through a GSM modem or SMPP gateway, and WhatsApp messages.
- 04
Historian and data archiving
Per-minute data logging into a SQL database on Windows Server, with archiving, backup and recovery. Trends and min/max analysis are available for any tag over any period kept in the archive.
- 05
21 CFR Part 11 controls
Electronic records with retention, electronic signatures with double signature on setpoint changes, role-based access, encryption and a secure audit trail recording date, time, variable, previous and new value, user and comment.
- 06
Automated compliance reports
Data, alarm, event, audit and trend reports generated as PDF, each with “Reviewed by user” and “Reviewed by QA” signature blocks.
- 07
Web and mobile access
Operator stations, an engineering station and a reporting station on site, plus web thin clients and mobile alerts for managers who are away from the control room.
- 08
Common system services
User management, role-based access, NTP time synchronisation, backup and recovery and data archiving run as shared services across every connected system.
Across the automation layers
What the solution does at each layer of your facility.
L1 · Field
Reads meters, sensors, analysers and machine controllers in place, without replacing field equipment that already works.
L2 · Control
Connects to existing PLCs, DDC controllers and DG, UPS and chiller controllers over a redundant industrial Ethernet ring.
L3 · Supervision
Runs redundant SCADA servers with a single alarm list, historian, trends and operator graphics for all connected systems.
L4 · Enterprise
Delivers PDF compliance reports, web dashboards, mobile alerts and a validated audit trail for management, QA and auditors.
Scope and specification
| Item | Scope |
|---|---|
| Systems unified | EMS, BMS, LAF, water (PW, RO, VC, MEDS, WFI, PSG), nitrogen, compressors, chillers, vacuum, boilers, UPS, DG and production machines |
| Communication protocols | Modbus TCP, OPC UA, OPC DA, BACnet IP, SNMP, MQTT, Profinet, EtherNet/IP, RS-485 |
| Server layer | Primary and secondary SCADA servers; application, report and web server; redundant database servers with real-time replication |
| Network | Redundant industrial Ethernet ring to field devices and controllers |
| Clients | Operator stations, engineering station, reporting station, web thin clients, mobile alerts |
| Alert channels | Email, SMS (GSM modem or SMPP), WhatsApp messages |
| System services | User management, role-based access, audit trail, alarm management, backup and recovery, data archiving, NTP time sync |
| Reports (PDF) | Data, alarm, event, audit and trend reports with user and QA review signature blocks |
| Validation documents | URS, FS, DS, IQ, OQ, PQ, traceability matrix, risk assessment, validation summary report (GAMP 5) |
| Reference deployment | 8 servers, about 65,000 tags per server, about 520,000 tags in total, 50 web clients |
What it means for operations
- One alarm list instead of manyOperators see utility, building and production alarms in one place, with acknowledgement and comments recorded against each event.
- Audit-ready recordsReports, signatures and the audit trail are produced by the system, so QA reviews records instead of rebuilding them from exports.
- No single point of failure in monitoringRedundant servers, databases and network ring keep data collection and alarming running through a hardware fault.
- Room to growNew buildings, lines or utilities are added as new tags and connections on the same platform rather than as another standalone system.
Frequently asked questions
Can the platform connect to the BMS, EMS and machines we already have?
Yes. It reads existing systems over standard protocols such as Modbus TCP, OPC UA, BACnet IP, SNMP and Profinet, so working controllers and meters stay in place. We survey each system’s interfaces during the requirement study and confirm the integration method before design.
How large a system can it handle?
One pharma deployment we built runs on 8 servers with about 65,000 tags per server, roughly 520,000 tags in total, and 50 web clients. Smaller sites start with a single redundant server pair and add servers as tag counts grow.
Does it meet 21 CFR Part 11 and EU Annex 11 expectations?
The platform provides electronic records, electronic signatures, double signature on setpoint changes, role-based access and a non-editable audit trail. We also supply the GAMP 5 validation set, from URS through IQ, OQ and PQ to the validation summary report, to support your qualification.
What happens if a server fails?
The secondary SCADA server takes over from the primary, and the database servers replicate in real time, so data collection, alarms and history continue. The redundant Ethernet ring protects the network path to the controllers in the same way.
What experience do you have with centralised systems?
We run more than 25 live centralised monitoring deployments connecting over 2,000 assets and processing more than 2 million data points a day. They cover hyperscale and colocation data centres, pharma plants, steel producers and automotive assembly lines.
Let’s start by understanding your facility
Send us a short description of the site and its current systems, and an engineer will come back with clear next steps.