Fleet Control

Fleet Control is Fleetera's command and control layer. It lets you send commands to industrial assets — writing values and calling methods on physical equipment — from the web interface, routed through your edge gateways to the devices on site.

Commands flow from the cloud to the edge and back:

Fleetera Cloud                    Edge Gateway                   Equipment
┌──────────────┐    HTTP/VPN    ┌──────────────┐    OPC UA    ┌──────────┐
│   Command    │ ──────────►   │    Edge      │ ──────────►  │  Device  │
│   Service    │               │   Command    │              │  (PLC,   │
│              │ ◄──────────   │    Agent     │ ◄──────────  │  SCADA)  │
│  (status +   │   result      │              │   response   │          │
│   audit)     │               │  EdgeX Core  │              │          │
└──────────────┘               └──────────────┘              └──────────┘

The command service in the cloud dispatches commands over a secure VPN connection to the edge command agent running on your gateway. The agent translates the command into a protocol-specific action (for example, an OPC UA value write or method call) and executes it against the target device via EdgeX. The result is reported back to the cloud for audit and status tracking.

Supported protocols

Fleet Control currently supports the following command types over OPC UA:

Key concepts

• Command definitions are created at the template level. They define what commands are available for a type of asset — the command name, type, risk level, and timeout.
• Command instances are automatically created for each asset when it is instantiated from a template. They inherit the definition's properties.
• Command bindings map a command instance to a specific protocol address on a connector — for example, the OPC UA node ID to write to.
• Executions are the audit trail. Every time a command is sent, an execution record tracks the full lifecycle from request to completion or failure.

Prerequisites

Before you can execute commands on an asset, you need:

1. An asset template with command definitions configured
2. Assets instantiated from that template
3. A connector configured for the site where the asset is located
4. Command bindings mapping commands to protocol addresses
5. An edge deployment running at the site with the edge command agent