One industrial IoT platform for every facility.

ControlCom Connect is a vendor-neutral, cloud-native industrial IoT (IIoT) platform that unifies monitoring, analytics, energy management, and compliance reporting across every site and every piece of equipment you run. The platform organizes an operation as a hierarchy: organizations at the top, then locations, devices, assets, and the individual variables each device reports. Data arrives through the ControlCom Edge Server, which reads industrial protocols at the site and forwards readings to the cloud, or through the API for custom hardware. On top of that stored data sit real-time dashboards, SCADA-style diagrams, alarms with SMS, email, and mobile push notifications, a Data Explorer for historical analysis, and scheduled compliance reports. Everything runs in the browser and on mobile, so the plant manager and the on-call technician are looking at the same live picture.

Modbus TCP and RTU, OPC-UA, BACnet, EtherNet/IP, and MQTT are all first-class, read side by side by the ControlCom Edge Server at the site. Because the platform is protocol-first rather than brand-first, Allen-Bradley, Siemens, Mitsubishi, ABB, and legacy controllers land in the same dashboard without a rip-and-replace: if the device speaks one of these protocols, it connects. Beyond the built-in protocol clients, a Sparkplug B listener picks up MQTT devices publishing in that convention, custom hardware can push readings directly through the HTTP API or MQTT, and a Node-RED integration covers gateways that already run flows. Every connected device exposes its data points as variables, the unit everything else is built from: assets combine them into equipment views, alarms watch them, and dashboards chart them, regardless of which protocol produced the reading.

Days, not months, and the sequence is short. The ControlCom Edge Server deploys as a Docker container on hardware you already have: an industrial PC, an ARM device such as a Raspberry Pi, or a virtual machine on VMware, Hyper-V, or KVM. Point its protocol connectors at the equipment, and readings start flowing into the platform as variables. From there, assets, dashboards, and alarms are configured in the browser rather than in custom code, so a working multi-site dashboard is typically live within the same week the project starts. There is no server build-out on your side because the cloud layer is already running, and the edge agent's outbound-only connection keeps the IT conversation to a single egress rule instead of a firewall redesign. Each site after the first repeats the same recipe faster.

Yes. The ControlCom Edge Server is a standalone application on your local network that does not depend on cloud connectivity. It gathers data from the field devices around it, stores readings locally, and forwards them to ControlCom Connect when a connection is available; if the site goes offline, the local system keeps working and no data is lost. Operators keep their visibility too: Edge HMI panels installed on local machines connect directly to the Edge Server, so live values and controls stay on screen through an outage. When the link returns, buffered readings sync and the fleet-wide picture fills back in. That architecture supports cloud-first deployments, hybrid setups where control stays local while analytics run in the cloud, and on-premise control rooms at high-security or remote sites where connectivity is restricted or intermittent.

The edge agent makes an outbound-only connection, so no inbound firewall ports are opened into the OT network and the equipment side of the deployment is never reachable from the internet. Data is encrypted with TLS in transit and encrypted at rest. Inside the platform, organizations are isolated from each other in a multi-tenant architecture, and role-based access control decides per user who can view dashboards, acknowledge alarms, edit configuration, or send commands, with multi-factor authentication and audit logging on top. Reports and scheduled jobs follow the same permission model, so an operator can watch a schedule without being able to change it. We hold a SOC 2 Type II report, available under NDA, and sites with stricter requirements can run hybrid or fully local, with controlled synchronization to the cloud.