Current fleet position
Resolve the latest location report against the registered robot identity and operating state.
GPS fleet intelligence
Location becomes part of robot trust.
Associate every position report with a registered robot CPID, timestamp, accuracy, speed, heading and operating state. Solarion turns location from an isolated map point into governed machine context.
CONTEXT, NOT CONTROL
GPS is evidence about where a robot reports operating.
It is not a safety localization system and should not replace collision avoidance, functional safety or OEM navigation controls. Its role in Solarion is to enrich identity, policy, operations and investigation with location context.
POSITIONCPID-bound telemetryLatitude, longitude, altitude and timestamp.
MOTIONSpeed + headingOperational movement context for review.
BOUNDARYGeofence postureInside, near or outside approved operating zones.
Capabilities
See where each machine is—and whether that context still makes sense.
Route history
Review recent path evidence alongside timestamps, software state and health signals.
Geofence evaluation
Compare position against configured home zones and allowed operating radii.
Fix quality
Expose accuracy and freshness so downstream users know whether a location claim is reliable enough to use.
Exception evidence
Preserve out-of-zone or stale-location events for operational review and investigation.
Edge API ingestion
Accept real robot location feeds through authenticated edge integrations in production architectures.
Policy context
Location can participate in a decision without becoming the decision itself.
Solarion can expose location context to policy engines alongside identity, software and risk state.
01CPIDWho is reporting?
→02FIXIs location fresh enough?
→03ZONEIs the robot in policy?
→04DECISIONAllow / flag / restrict
→05EVIDENCEPreserve context
Telemetry contract
A compact location event designed for machine use.
In production, location reports should be authenticated, time-bounded and associated with the specific robot credential that produced them.
{
"robot": "cpid:robot:sr-h01",
"observed_at": "2026-08-21T03:55:42Z",
"lat": 43.6532,
"lon": -79.3832,
"accuracy_m": 2.8,
"speed_mps": 1.1,
"heading_deg": 84,
"geofence": "in_policy"
}Working MVP
Open GPS Tracking ↗Review CPID-bound fleet location inside Robot Control.
The demo includes sample routes, geofence state and robot context. Production deployments connect approved positioning feeds through the edge/API layer.