Scenario 03 / Facilities

Autonomous patrol and inspection with accountable machine state.

Robots moving through buildings need more than route visualization. Solarion binds the machine to approved zones, software, schedules, health state and evidence so operators can distinguish normal autonomy from an exception.

OPERATIONAL GOALExtend inspection coverage without losing accountability for machine behavior.
CONTROL OBJECTRobot identity + route/zone context + approved perception stack.
SUCCESS SIGNALReliable patrol evidence with clear exception handling.
Patrol governance

Turn a route into a policy-aware operating record.

01

Assign identity

Bind every patrol unit to a persistent CPID and sponsor.

02

Define boundary

Set site, floor, geofence and shift context.

03

Approve perception

Track vision and detection packages by version.

04

Observe route

Correlate position reports with robot identity.

05

Flag anomalies

Surface stale GPS, software drift or health exceptions.

06

Review evidence

Reconstruct what the machine reported during an incident.

Investigation context

Ask where the robot was—and what state it was in.

Location evidence becomes more useful when tied to a verified identity and authorized software manifest.

CPIDcpid:robot:patrol-08
ZONEhq / level-02 / east
POSITION43.6532 / -79.3832
SOFTWAREpatrol-perception:v3.1
STATUSactive / in_policy
EVIDENCEroute-event / linked
Location-aware governance

Combine fleet tracking with identity and software state.

Use the GPS workspace to preview how location context can participate in robot operations without replacing safety localization.

Open GPS demo ↗