Plan the mission
Set the route, schedule, checkpoints, access rules and what should create an event.
Solution 01 / In development
Autonomous patrol. Verified handoff.
Patrol plans and supervises autonomous security missions. Robots cover the route; your control room receives the events that need a person.
- Status
- In development
- Execution
- Local at the site edge
- Response
- Human-owned
51.5082 N / 0.3411 W
Robot P-01Executing route
East loading gateObject detected
The operation
One continuous path from mission to evidence.
The robot is only one part. The service also needs policy, local execution, event verification and a clean handoff into the existing security operation.
Run it on-site
The local runtime supervises the robot and keeps the active mission close to the site.
Verify the event
A detection is checked against location, time, policy and recent mission context.
Hand it over
The existing team receives video, location, confidence and mission history together.
Patrol operator console
Review the event, its context and the handoff together.
Explore three illustrative patrol events. Switch between live evidence, site context and the incident record, then record the operator decision.
WM
PatrolOperator console / illustrative
Active siteNorthbank Logistics
P-01 connected 74%
LiveP-01 / Front RGB
0.4 m/s 082° 74% 38 ms
Mission events3 requiring review
Patrol deployment architecture
Cloud control. Site-edge execution. Human authority.
Patrol uses the wider WorkMachines system. Its mission control, site execution and machine connectors are also used by other WorkMachines applications.
System architecture
The parts used to plan, run and review a patrol.
Security operatorMission planningIncident reviewVMS / incident system
A named person remains responsible for the mission and any response.
PatrolRoutes & schedulesDetection policyHandoff rules
The first WorkMachines solution, configured for one site and operating model.
WorkMachines operating system
Mission plannerIdentity & accessAlertingEvidence catalogue
The cloud plans the mission and retains the complete operational record.
Detection policyMission contextEvent verificationHandoff policy
Patrol detections are interpreted, checked and governed before handoff.
Mission runtimeLocal safety policyRobot healthEvidence buffer
Local supervision, safety and buffering continue if the cloud is unavailable.
Patrol capabilityCommand translationSDK / ROS bridgeState normalisation
The Patrol service is isolated from each manufacturer’s SDK and state model.
QuadrupedCameras & LiDARIMU / RTKPatrol route
The active patrol route, the machine and its sensing payload.
Commands move down Telemetry and evidence returnSite execution remains local when connectivity drops
First deployment
Start where the route and response are already clear.
The strongest first sites have repeatable patrol paths, a meaningful coverage gap and a team ready to receive verified events.
Defined route
The patrol path and checkpoints can be mapped.
Useful coverage
There is a real gap in night, perimeter or remote-site coverage.
Clear response
A named team already owns the incident once it is verified.