THE PLATFORM

One operating layer across fragmented infrastructure.

Saro connects the controls, meters, equipment and energy assets already on site; turns their signals into a common operating state; and sends decisions back into the physical system within constraints.

PHYSICAL → INTEROPERABLE → PHYSICALCONTINUOUS LOOP

Existing infrastructure

BMS / BASBACnet
Chillers / AHUsModbus
Meters / VFDsTCP / RTU
UPS / PDUAPI / gateway
Solar / BESSModbus / API
Contextweather / workload
SARO EDGE + OPERATING MODEL
Normalize. Understand. Coordinate.

Saro does not require every system to speak the same language before it can reason across them.

Physical outcomes

Setpoint changesthermal / process
Equipment sequencingplant / auxiliaries
Operator interventionsranked / explainable
Measured responseverify / learn / repeat
THE PREMISE

Interoperability is not a connector checklist. It is the ability to understand and coordinate physical systems across equipment, protocols and operating domains.

SYSTEM ARCHITECTURE

From heterogeneous physical signals to constrained action—and back again.

The platform can start read-only, operate in advisory mode, and graduate to closed-loop control where the site permits. Existing controls remain part of the architecture rather than something Saro has to replace.

EXISTING INFRASTRUCTURE → SARO → EXISTING INFRASTRUCTURELIVE OPERATING MODEL

Physical inputs

BMS + controllersBACnet/IP · BACnet MS/TP
Equipment controlschillers · AHUs · VFDs
Electrical telemetrymeters · CTs · switchgear
Power infrastructureUPS · PDU · inverters
Operating contextweather · occupancy · workload
Energy assetsgrid · solar · BESS
LOCAL INTEROPERABILITY
Saro Edge

Bridges visibility and control gaps where the existing system does not expose sufficient data directly.

Normalized operating state

Map heterogeneous points, units, timestamps, equipment relationships and operating context into one usable state model.

01SENSE
02UNDERSTAND
03DECIDE
04ACT
BACnet/IPBACnet MS/TPModbus TCPModbus RTUMQTTREST APINiagaraMeters / CTs

Physical outputs

Setpointstemperature · pressure · flow
Sequencesplant · pumps · auxiliaries
Schedulesruntime · demand windows
Operator actionsranked · contextual
Energy dispatchload · solar · storage
Measurementverify · learn · repeat
01 · CONNECT
Use what already exists.

Direct integrations first; Saro Edge where the signal or control path is incomplete.

02 · NORMALIZE
Create one operating state.

Different systems become comparable through a common equipment and state model.

03 · CONSTRAIN
Encode what cannot be crossed.

Comfort, safety, redundancy and operator rules remain hard limits.

04 · VERIFY
Measure physical response.

Observed system behavior feeds the next decision instead of stopping at a recommendation.

INTEROPERABILITY BY DESIGN

Connect. Normalize. Coordinate.

The point is not merely to ingest data from many protocols. The point is to make those systems participate in the same operating decision.

CONNECT

Meet the infrastructure where it is.

Use BMS, controller, meter, gateway and equipment interfaces already available before adding anything new.

NORMALIZE

Turn points into physical meaning.

Translate device-specific telemetry into equipment state, relationships, constraints and site context.

COORDINATE

Decide across systems, not inside silos.

Reason across thermal, electrical, storage, generation and workload conditions before selecting an action.

BACnet
BMS, AHUs, chillers, supervisory controls
OBSERVE / CONTROL
Modbus TCP / RTU
Meters, VFDs, chillers, inverters, power equipment
OBSERVE / CONTROL
MQTT / REST APIs
Gateways, cloud systems, contextual data and selected equipment interfaces
EXCHANGE / CONTEXT
Niagara / JACE
Existing building integration layer where deployed
INTEGRATION
Meters / CTs / Saro Edge
Fill physical visibility gaps where controls do not expose enough usable telemetry
EDGE VISIBILITY
SARO EDGE

Software when the signals exist. Physical edge when they do not.

ETH
RS-485
I/O
PWR

Interoperability anchored at the physical site.

Saro Edge extends sensing, protocol bridging and local intelligence without forcing a replacement of the installed controls layer.

DIRECT FIRST
If the BMS or equipment already exposes the required data and authority, Saro integrates directly.
FILL GAPS
If data is missing, fragmented or inaccessible, the edge layer adds the minimum physical interface needed.
LOCAL OPTION
Support staged authority, local execution and deployments where site or cybersecurity constraints limit cloud dependency.
THE DECISION LOOP

Watch different physical systems enter the same intelligence loop.

The architecture remains constant. The equipment, relationships, constraints and authority change by environment.

DATA CENTER INTELLIGENCE LOOPPHYSICAL → SENSE → UNDERSTAND → DECIDE → ACT → PHYSICAL ↺
01 · SENSE

CONNECTED EQUIPMENTLIVE
02 · UNDERSTAND

PHYSICAL RELATIONSHIP MODEL
03 · DECIDE

CONSTRAINT CHECKFEASIBLE
04 · ACT

COMMAND / OPERATOR ACTION
INTELLIGENCE DOMAINS

Different physics. One operating model.

THERMAL

Thermal Intelligence

Models cooling, HVAC and heat-transfer behavior against demand, equipment condition and environmental constraints.

CHILLERS · AHUs · CRAH/CRAC · PUMPS · COOLING TOWERS · ZONE / RACK TEMPERATURE
ELECTRICAL

Electrical Intelligence

Maps equipment-level electrical behavior to degradation, imbalance, losses and operational risk.

METERS · FEEDERS · MOTORS · VFDs · UPS · PDU · POWER QUALITY
ORCHESTRATION

Energy Orchestration

Coordinates demand, generation, storage, tariffs and operational rules as one constrained decision problem.

GRID · SOLAR · BESS · LOAD · TARIFF · WORKLOAD / PRODUCTION STATE
DEPLOYMENT AUTHORITY

The physical system stays under operator-defined authority.

READ-ONLY

Observe first.

Build the operating model and quantify opportunity without writing back to controls.

ADVISORY

Recommend with context.

Every action is presented with reasoning, expected effect and relevant physical constraints.

CLOSED LOOP

Act inside hard limits.

Approved setpoints and sequences can be written back with rollback, traceability and measured verification.

START WITH THE SYSTEM

Show us what your infrastructure already exposes.

We map controls, protocols, equipment, telemetry gaps and authority boundaries first—then define the smallest path to a useful Saro deployment.