Coverage and Readiness

See which assets can be commanded, site by site, what stands in the way for the rest, and the link that fixes each gap.

Coverage answers one question for the whole fleet: which assets can be commanded right now, and what stops the others. Open Command, then Coverage.

Reading Coverage

The page header says how many assets with commands can be commanded, for example "4 of 7 assets can be commanded". The line under it says when the counts were made: counts are up to a minute old. Fleetera checks every command again when it is sent, so a count that has not caught up yet never lets a command through.

Each site has a row with its own sentence, for example "2 of 5 assets ready, 3 not bound". A site under local control also shows who switched it on, when and why. On each row:

Show assets opens the site's assets; Hide assets closes them.
Run on ready assets opens the Execute Command wizard with that site chosen. It appears when the site has ready assets and your role can send commands.

Coverage with one site open: two assets Ready and three Not bound, each with a Bind link in the Fix column

The open site lists its assets, 50 to a page:

Column	What it shows
Asset	The asset's name and the gateway that manages it, or "No gateway resolved"
Readiness	The asset's readiness. Hover it for the reason
Commands	How many commands the asset has. Open it to see each command with its own readiness, its reason and its fix link
Fix	The one link that closes the asset's gap, for example Bind Set curtailment cap. Shown only to people who can send commands

An asset is Ready when at least one of its commands is ready. Otherwise it takes the state of the command that is closest to ready, so its row names the next thing to fix.

Filters

Three filters narrow the page: Any template, Any readiness and Any command. Each choice is kept in the page address, so a filtered view can be shared as a link. The Overview's coverage line links here with the readiness filter already set, for example from "3 not bound".

Readiness states

The same readiness words appear on Coverage, on an asset's Commands section and in the Execute Command wizard. When several things are wrong, the state shown is the first in this table.

State	What it means	What to do
Not permitted	Your role cannot send commands, or your organization is suspended. Shown only on the commands you look at, never in the counts	Ask an admin to change your role
Not in plan	Your plan does not include sending commands to equipment	View plan
Switched off	The command is switched off for this asset	The app has no control to switch a command on or off today. Contact Fleetera support
Not bound	The command has no binding, no gateway manages the asset, or the command is bound to a connector the asset's gateway does not run	Bind the command, or add a gateway at the site, or add the asset to a gateway's scope
Site under local control	The site is under local control	An admin switches the site back to remote control in Open site settings
Gateway under local control	The gateway reports that it is under local control	An admin clears it on the gateway's page
Gateway offline	The gateway is offline, or has never connected	Open gateway and bring it back online
Protocol cannot carry it	The command's connector cannot carry this kind of command, for example a method call bound to a Modbus connector	Bind it to a suitable connector, or change the command type
Gateway cannot run it	The gateway's runtime reports that it cannot run this kind of command, for example a method call	Update the gateway's runtime, or bind the command as a value write
Not determined	Something Fleetera needs to decide could not be read: for example, a gateway that has not reported its capabilities or its local-control state, or a site with several gateways none of which has reported yet	Follow the reason. A command that is not determined is never counted as ready and cannot be sent
Ready	Every check passed on what Fleetera knows	Send it

Readiness is about one command on one asset at the moment it was read. Ready does not promise that the equipment will accept the value, and it says nothing about the asset's other commands.

Asset readiness and your role

The counts, the site sentences and the asset rows describe the equipment, so everyone sees the same numbers whatever their role. A missing permission to send is not a fault in the fleet, so Not permitted never appears in a count. It appears only on the per-command list, for a person whose role cannot send.

When no commands are declared

If your organization has not declared any command yet, Coverage shows the same starting point as the Overview, with Declare commands on a template and a link to Command Definitions.