0101
People & systemsCommission work. Retain authority.
Site teamsControl roomEnterprise
Technology / Architecture
One operating layer between human intent and machine execution.
WorkMachines coordinates applications, people, machines and the physical site around one accountable operating model. Patrol and Crop Monitoring configure the same core platform for different work.
WorkMachines / operating modelCommands down · Evidence up
System view
Four operating planes. Seven technical capabilities.
Start with the company-wide system, choose an application trace, then open any capability for its role in the operation.
System architecture
The full system used by every WorkMachines application.
OperatorsSite teamsControl roomsEnterprise systems
The teams and systems that commission work and receive the result.
PatrolCrop monitoringInspectionFurther applications
Packaged workflows built on the same operating layer.
WorkMachines operating system
Mission orchestrationFleet stateIdentity & accessEvidence catalogue
Missions, fleet state and the complete operational record.
Perception servicesPlanning & agentsPolicy engineEvent verification
Perception becomes a governed decision before any machine action.
Mission runtimeLocal policyHealth & diagnosticsEvidence buffer
The active mission stays close to the machine and keeps running locally.
Capability contractCommand translationSDK / ROS bridgeState normalisation
Robot-specific commands and states sit behind a common contract.
QuadrupedsAMRs & dronesSensorsRoutes & infrastructure
Machines, sensors, routes, assets and infrastructure.
Commands move down Telemetry and evidence returnSite execution remains local when connectivity drops
Boundaries
Keep each decision where it belongs.
Cloud systems are good at planning and retaining the record. The site edge is where active execution, immediate safety and degraded-connectivity behaviour belong.
Commands downMissions, schedules, policy and approved operator actions.
Decisions on-siteRoute execution, stop conditions, machine health and safe fallback.
Evidence upTelemetry, detections, video, decisions and mission outcomes.
Local execution
The active mission and its safe fallback remain on-site.
Human authority
Dispatch, override and incident decisions stay attributable.
Evidence by default
Actions, detections and overrides remain in one record.
Machine connectors
Vendor-specific commands remain behind a common boundary.