Act on it, with people in control.
Fleetera doesn't replace the controllers that keep your equipment safe. Impact is the fleet-wide layer that lets you manage every site from one place, governed, audit-trailed, and always under human control.
Supervisory by design
Above the controllers, never instead of them.
Impact is a supervisory layer. It does not replace your BMS, PCS, EMS, or PLCs. Fast control loops stay local, at the site. Safety functions are never something Fleetera can command: an emergency stop belongs to your plant's hard-wired safety chain, and Fleetera refuses to define a command against one. Fleetera coordinates from above: fleet-wide configuration, governed commands, and a record of everything.
Change every site from one place.
Change what a site collects, how often, and how its signals map onto your assets, for any site, from the cloud. Each site picks the change up on its own. Every change is recorded: who changed what, where, and when.
Collect diagnostics
Low riskRead-only diagnostics snapshot. No equipment changes.
| Status | Asset | Duration |
|---|---|---|
| Completed | Turbine A07 | 1.2s |
| Completed | Turbine A08 | 1.4s |
| Executing | Turbine A09 | — |
| Dispatched | Turbine A12 | — |
| Turbine A19 | — |
Governed commands to equipment, fleet-wide.
Fleet Control sends supervisory commands to the equipment itself from the cloud, such as adjusting a limit or changing a mode, under the same governance as every configuration change. Commands go out over the OPC UA and Modbus TCP connectors; the MQTT and REST connectors read only and refuse every command. Calling a method on a controller is held to one check more: Fleetera sends that kind of command only to a gateway whose runtime has reported it can make the call, and refuses it otherwise rather than guessing.
Governance
Guardrails first, then power.
The rules for every action that leaves the cloud, live and enforced today. Configuration changes and Fleet Control's commands to equipment run under the same rules, with no way around them.
Immutable audit trail
Who sent what, when, to which asset, and what came back is recorded for every change and every command. Nothing happens off the record.
Tenant scoping
Every action is scoped to your tenant and the assets you choose. There is no cross-tenant path.
Risk classes
Every command carries a risk class, from low to critical, with stricter checks at each level before it can run.
A second person on critical commands
You can require a second person's approval before a critical command runs.
Permission to execute
Executing a command is its own permission, separate from viewing, granted per role, so read access never implies control. Sending commands to equipment also has to be switched on for your account.
Local fallback
If the link drops, the site keeps running on its local controllers. Fleetera never sits in the fast loop.
Where the layers close the loop.
Insight spots a condition and proposes the response; an operator decides. Over time, playbooks you have set up will carry the response out inside the same rules, and you decide which ones may run without you.
Keep exploring
Run your fleet from one place.
Start by managing every site's setup from the cloud, live today and recorded from day one.