Local Control

Local control stops Fleetera from sending commands while people work on the equipment. While it is on, every command to the affected assets is refused before anything is sent, and the command pages show who switched it on, when and why.

You can put a single gateway or a whole site under local control.

A gateway

Open the site, then Gateways, then the gateway. Its page has a Local control card that shows the state the gateway last reported, who switched it on, when and why.

• An administrator sets and clears it here. Select Set local control or Clear local control, enter a reason, and confirm. The reason is required in both directions and is recorded with your name.
• A person at the gateway can switch it on in the gateway's Edge UI, on the Control page, with a reason. They cannot switch it off there: the page says that local control is cleared from Fleetera by an administrator.
• Operators and viewers see the state only.

The gateway applies a change from Fleetera on its next heartbeat. Until then the card shows Waiting for the gateway since the time of the request, with who asked and why, and commands follow the state the gateway last reported. A gateway that is offline applies the change when it reconnects.

A site

Open the site, then Settings. The Remote control card has a Local control switch. Only a tenant administrator can move it, and every change needs a reason. When switching to local control you can also set an end time, after which commands are accepted again.

Who can change it

A person at the gateway can switch its local control on in the Edge UI, whatever their Fleetera role.