Vendor-neutral data center monitoring across every site you run

Yes. ControlCom Connect is designed to sit on top of existing DCIM, BMS, and SCADA, not replace them. Most operators keep their DCIM for asset and capacity tracking and use ControlCom for the layer those tools do not deliver: cross-system data center monitoring, multi-site rollup, mobile access, and the equipment DCIM rarely reaches, paralleling switchgear, standby generators, ATS, branch circuits, and PDUs from multiple vendors. The integration burden is low because the platform reads from the equipment directly over Modbus TCP/RTU, BACnet, OPC-UA, and MQTT rather than through the DCIM, so nothing about the existing deployment has to change. In practice the two systems settle into different jobs: the DCIM answers what is installed and where capacity stands, while ControlCom answers what is happening right now across every system and every site, and pages the on-call engineer when the answer is wrong.

Yes. The platform includes generator compliance reports and EPA runtime reports built from the data it is already collecting. Every generator run is detected automatically, from the generator breaker closing or an ATS run request, and a compliance report is written per run: whether the unit held its configured minimum load for 30 continuous minutes, how each transfer switch performed against its required transfer time, and the specific reason when a test comes back incomplete. The runtime report splits engine hours into emergency and non-emergency time, the split EPA reporting asks for, with custom runtime overrides for runs recorded as routine that were in fact outages. Configurations are re-checked hourly, so a test performed on Tuesday shows up without anyone opening the page. Reports can be generated for any historical date range, exported as PDFs on demand, and regenerated from stored readings if the underlying data changes.

Yes. Multi-site fleet visibility is a default feature, not a custom build. Every colocation cage, enterprise data center, and edge site registers into one asset hierarchy, and portfolio dashboards roll up uptime, energy, PUE, capacity, and alarms across all of them, grouped by tier, region, customer, or any structure you define. Benchmarking works from the same view: compare PUE between facilities, alarm and excursion rates between sites, and generator runtime across the fleet without exporting a single CSV. A map view shows every site colored by alarm state, with live weather overlays, which matters when a storm front is moving across a region of edge sites. Each site keeps its own local dashboards and alarm routing for the operators who run it, while the portfolio level serves operations leadership and the customers who ask how their footprint is doing.

Through pre-built industrial protocol connectors. Modbus TCP/RTU, BACnet, OPC-UA, MQTT, and REST cover the protocols actually deployed on real switchgear, UPS, ATS, PDU, and chiller equipment, which means modern Schneider, Vertiv, Eaton, and Cummins gear and legacy Russelectric, ASCO, GE 7700, and Cutler-Hammer Digitrip equipment land in the same single pane of glass. The vintage of the equipment matters less than whether it exposes a register or a point, and after years of retrofitting paralleling switchgear we have read most of what is out there. For device types that need custom handling, the Edge SDK lets you onboard them visually without writing code, mapping registers to named points once and reusing that definition at every site running the same hardware. If something in your white space speaks none of these protocols, raise it during the demo and we will tell you plainly whether it can be read.

We hold a SOC 2 Type II report (available under NDA), with AES-256 encryption at rest and TLS 1.3 in transit. The edge agent is a Docker container running outbound-only, no inbound firewall holes punched into the OT VLAN. Role-based access, MFA and magic-link sign-in, API keys for the REST API, and audit logging are standard. ControlCom Connect itself is a hosted service on AWS, with no self-hosted version. The component that runs inside your boundary is that edge agent, the ControlCom Edge Server: it evaluates threshold alarms and runs Triggers for protective actions locally, serves Edge HMI panels on the local network, and keeps the site operating when the internet link drops. Local storage buffers unsent readings until the connection returns, and that autonomy was proven during the October 2025 AWS outage: fifteen hours, zero data loss, zero manual intervention.

Days, not months. A containerized edge agent drops on a small box at the site, makes outbound-only connections, and pre-built protocol connectors start pulling from the switchgear, UPS, generators, and cooling plant the same week the project starts, so a working dashboard exists before a traditional DCIM integration would have finished its kickoff meetings. The remaining effort is configuration rather than development: the asset hierarchy, alarm severities and routing groups, the generator report setup, and the portfolio rollup. Multi-site fleets then onboard site by site, with the first facility establishing templates that each subsequent site inherits, so the tenth site goes live faster than the first. There is no per-tag licensing, so instrumenting every branch circuit and every PDU instead of a shortlist is a coverage decision within the data volume and device allotment of your plan rather than a per-point license negotiation, and there is no multi-month custom integration before you start collecting data.