Scheduled rounds
Set day/night routes, points and frequency.
Hospital indoor public-area security patrol
Patrol indoor hospital public areas.Review remotely and respond on site.
Support hospital security through scheduled/ad hoc indoor rounds, live views, remote voice, checkpoint photos and event records.
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.
Ad hoc rounds
Duty staff create tasks as needed.
Remote review
Use live views, voice and photos for human confirmation.
The source excludes underground areas and parking. Robots do not replace security response or provide patient-fall, vital-sign or diagnostic functions.
Terminals and configuration
Document-based scope; confirm supplied model, options and site fit.
Patrol terminal
Rounds, image return, remote voice and charging return.
Management
Maps, routes, tasks, devices and event reports.
Suitability
Scenario fit
Support hospital security through scheduled/ad hoc indoor rounds, live views, remote voice, checkpoint photos and event records.
Scheduled rounds
Set day/night routes, points and frequency.
Ad hoc rounds
Duty staff create tasks as needed.
Remote review
Use live views, voice and photos for human confirmation.
Where the service helps
Coordinate routes, content and staff around these tasks.
| Service area | Service scope |
|---|---|
| Scheduled rounds | Set day/night routes, points and frequency. |
| Ad hoc rounds | Duty staff create tasks as needed. |
| Remote review | Use live views, voice and photos for human confirmation. |
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.
Public building areas
Choose accessible lobbies, lift halls and passages.
Priority points
Set photo rules, timing and escalation contacts.
Support
Commission charging, doors and lifts as needed.
Locations
- Public building areas
- Priority points
- Support
Validate a complete loop
Public building areas → Priority points → Support
Diagrams explain the flow; survey actual passages, thresholds, access and stops.
Site readiness and operations
Confirm site, equipment and staffing; verify interfaces per project.
On-site response
Remote staff confirm; security staff attend and record outcomes.
Deliverables
Maps, routes, checkpoints, device/IoT lists, trial records and training manuals.
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 | Public building areas, Priority points, Support | 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
Pilot public areas in one inpatient building during one night window; validate routes, images, alerts and human response.
Patrol terminal
Rounds, image return, remote voice and charging return.
Management
Maps, routes, tasks, devices and event reports.
Sizing considerations
| Sizing variable | Effect on capacity |
|---|---|
| Task cycle | Measure request, execution, handover, return and charging time. |
| Site scope | Public building areas, Priority points, Support |
| 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
Pilot public areas in one inpatient building during one night window; validate routes, images, alerts and human response.
Configure and commission
Check devices, routes, points, accounts and necessary access/system interfaces.
Trial and acceptance
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 exception handling matrix
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
The source excludes underground areas and parking. Robots do not replace security response or provide patient-fall, vital-sign or diagnostic functions.
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
- Patrol terminal
- Rounds, image return, remote voice and charging return.
- Management
- Maps, routes, tasks, devices and event reports.
Document and current product versions may differ; confirm supplied specifications and project configuration.
Common questions
Where should the pilot start?
Pilot public areas in one inpatient building during one night window; validate routes, images, alerts and human response.
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?
The source excludes underground areas and parking. Robots do not replace security response or provide patient-fall, vital-sign or diagnostic functions.
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.
Plan a project
Pilot preparation
Pilot public areas in one inpatient building during one night window; validate routes, images, alerts and human response.
Discuss the solution- Scope and points
- Public building areas, Priority points, Support 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.
Hospital medical-material delivery solution
Support one-to-many medication, many-to-one specimens and one-to-one sterilized tools/reports, sharing capacity by time while hospital staff verify handovers.
Hospital specimen delivery solution
Connect collection points and laboratories for packaged specimen transport.
Hospital ward replenishment solution
Replenish care consumables, daily items and small linen loads between central stores, ward stores, nurse stations and treatment rooms.