Patrol capture
Associate snapshots with route/point context.
Building stranger patrol and enterprise matching
Robots capture. Enterprise systems match.Staff review returned alerts.
Robots capture faces with time, floor, point and task ID and send them to enterprise personnel systems for matching. Enterprise results return as platform/app alerts.
Configure
Managers
Set areas, checkpoints, routes, time and frequency.
Report
Platform
Present collected information, task states and alerts.
Review
Duty staff
Review readings, images or live views and decide on action.
Pilot the documented workflow with responsible staff verifying key handovers.
The service
Service flow and ownership
Robots execute configured tasks; responsible staff retain verification and on-site response.
Managers
Configure
Set areas, checkpoints, routes, time and frequency.
Robot
Patrol
Follow configured indoor routes and collect at checkpoints.
Platform
Report
Present collected information, task states and alerts.
Duty staff
Review
Review readings, images or live views and decide on action.
Site staff
Resolve and record
Mark the outcome and retain task, location, time and event records.
Confirm execution separately from human handover/review; assigned staff take over exceptions.
Roles
Robot
Patrol, collect and report site information.
Duty staff
Review conditions and contact responders.
Site and support staff
Respond and maintain equipment, routes and records.
Service modes
Select modes for the workflow; agree extensions separately.
Enterprise matching
Enterprise systems match staff, visitor or blacklist records.
Notifications
Returned enterprise results appear in platform/app for human review.
Capture and matching belong to robot and enterprise systems respectively; no match does not establish a violation. Posture, clothing, behavior, prolonged-stay detection, trajectory replay and access-permission control are outside scope.
Terminals and configuration
Document-based scope; confirm supplied model, options and site fit.
Standard interface
HTTP/HTTPS and JSON; agree snapshot fields, returned results and alerts.
Environment
Exclude underground, outdoor, high-humidity and strong-sunlight settings; no trajectory replay.
Suitability
Scenario fit
Robots capture faces with time, floor, point and task ID and send them to enterprise personnel systems for matching. Enterprise results return as platform/app alerts.
Patrol capture
Associate snapshots with route/point context.
Enterprise matching
Enterprise systems match staff, visitor or blacklist records.
Notifications
Returned enterprise results appear in platform/app for human review.
Where the service helps
Coordinate routes, content and staff around these tasks.
| Service area | Service scope |
|---|---|
| Patrol capture | Associate snapshots with route/point context. |
| Enterprise matching | Enterprise systems match staff, visitor or blacklist records. |
| Notifications | Returned enterprise results appear in platform/app for human review. |
Coordination priorities
Reduce repeated trips
Assign suitable repeated routes to robots and compare results in the pilot.
Clear handovers
Verify outcomes against task, destination and responsible role.
Operational review
Use task states and exception records to adjust routes, schedules and configuration.
Building route
Routes and service points
Configure routes for the actual site; diagrams explain the workflow.
Indoor routes
Use validated floor shared-area routes.
Capture points
Configure authorized snapshots under enterprise rules.
Response desk
Staff verify identity, contact security and retain outcomes.
Locations
- Indoor routes
- Capture points
- Response desk
Validate a complete loop
Indoor routes → Capture points → Response desk
Diagrams explain the flow; survey actual passages, thresholds, access and stops.
Site readiness and operations
Confirm site, equipment and staffing; verify interfaces per project.
Patrol frequency
Increase priority-point frequency at night or outside working hours as configured.
System boundary
Robot access commissioning differs from personnel clearance; patrol does not grant/revoke people’s access.
Commission configured interfaces, notifications and access; assign site contacts and staff fallback.
Suggested readiness checks
Swipe horizontally to see all columns.
| Item | Scope | Confirmation |
|---|---|---|
| Scope and points | Indoor routes, Capture points, Response desk | Confirm accessible scope and responsible staff on site. |
| Routes and access | Maps, passages, doors/lifts, network and charging. | Commission cross-floor and controlled-door access as needed; diagrams do not replace site tests. |
| Handover and exceptions | Robot, Duty staff, Site and support staff | Agree notifications, staff takeover, records and review rules. |
Fleet planning
Pilot and expansion
Source reference: 2–4 robots, one API service, one web management platform and dashboards/reports; size by floors, routes and frequency.
Standard interface
HTTP/HTTPS and JSON; agree snapshot fields, returned results and alerts.
Environment
Exclude underground, outdoor, high-humidity and strong-sunlight settings; no trajectory replay.
Sizing considerations
| Sizing variable | Effect on capacity |
|---|---|
| Task cycle | Measure request, execution, handover, return and charging time. |
| Site scope | Indoor routes, Capture points, Response desk |
| Staff coordination | Allow for available receiving, reviewing and exception-response staff. |
Source configurations/data refer to their stated scenario; confirm final sizing through site validation.
Pilot & operation
Suggested implementation
The following are project assessment and acceptance suggestions, subject to site confirmation.
Confirm scope
Site preparation
Source reference: 2–4 robots, one API service, one web management platform and dashboards/reports; size by floors, routes and frequency.
Configure and commission
When ready
Check devices, routes, points, accounts and necessary access/system interfaces.
Trial and acceptance
By project agreement
Validate real tasks, staff coordination, exceptions and records before expansion.
Suggested exception handling
The following are project assessment and acceptance suggestions, subject to site confirmation.
View the exception checklist
Swipe horizontally to see all columns.
| Condition | Action | Ownership and records |
|---|---|---|
| Task cannot continue | Pause, wait or hand over to staff under site rules. | Managers record cause, owner and recovery conditions. |
| Handover/review incomplete | Contact the assigned staff; automatic task closure does not replace their confirmation. | Record the reason and follow-up. |
| Device/access exception | Follow support procedures and use staff service if required. | Support and site staff coordinate and validate recovery. |
Suggested acceptance
The following are project assessment and acceptance suggestions, subject to site confirmation.
View acceptance measures and responsibilities
Swipe horizontally to see all columns.
| Check | Status | Verification |
|---|---|---|
| Task execution | Suggested acceptance item | Complete tasks within agreed routes/scope and record success, failure and reasons. |
| Staff coordination | Suggested acceptance item | Verify notification, permissions, human review/handover and exception takeover. |
| Operational records | Suggested acceptance item | Sample tasks, times, points and outcomes; agree metrics and targets with the project team. |
Agree before delivery
Service scope
Capture and matching belong to robot and enterprise systems respectively; no match does not establish a violation. Posture, clothing, behavior, prolonged-stay detection, trajectory replay and access-permission control are outside scope.
Responsibilities
Robot, Duty staff, Site and support staff
Configuration and metrics
Agree device models, options, interfaces, timing and targets in project documents.
Questions
Related equipment
Review product information and reconcile the document version with the supplied model/configuration.
View productDocument configuration and device checks
- Standard interface
- HTTP/HTTPS and JSON; agree snapshot fields, returned results and alerts.
- Environment
- Exclude underground, outdoor, high-humidity and strong-sunlight settings; no trajectory replay.
Common questions
Where should the pilot start?
Source reference: 2–4 robots, one API service, one web management platform and dashboards/reports; size by floors, routes and frequency.
How do robots and staff share work?
Robot：Patrol, collect and report site information. Duty staff：Review conditions and contact responders. Site and support staff：Respond and maintain equipment, routes and records.
What needs separate confirmation?
Capture and matching belong to robot and enterprise systems respectively; no match does not establish a violation. Posture, clothing, behavior, prolonged-stay detection, trajectory replay and access-permission control are outside scope.
How are configuration and acceptance set?
Use source recommendations as a starting point, then confirm against site routes, supplied equipment and trial data. Suggested checks do not establish fixed performance or service guarantees.
Pilot preparation
Source reference: 2–4 robots, one API service, one web management platform and dashboards/reports; size by floors, routes and frequency.
Scope and points
Indoor routes, Capture points, Response desk Confirm accessible scope and responsible staff on site.
Routes and access
Maps, passages, doors/lifts, network and charging. Commission cross-floor and controlled-door access as needed; diagrams do not replace site tests.
Handover and exceptions
Robot, Duty staff, Site and support staff Agree notifications, staff takeover, records and review rules.
Related solutions
Choose a dedicated solution for each workflow.
Building environmental patrol and purification
AIR collects environmental readings on shared-area routes and provides mobile purification, with task/device/exception records for human review.
Building autonomous delivery solution
Connect takeaway, parcels, documents, retail and internal supplies through robot transport with booking/loading flows for users, couriers, merchants and reception.
Building document delivery solution
Support floor-to-floor documents, reception bulk dispatch, reverse pickups to mailrooms and urgent tasks, with human packaging/recipient/handover checks.