Campus transport
TRANGO moves batches from central stores to buildings.
Hospital general supplies delivery solution
General supplies move from store to department.Configure campus and indoor routes as needed.
Move office supplies, linen, care consumables and support items from central stores to departments, focusing on standardized small items and repeat routes.
Request
Users
Select items, destination and required time.
Deliver
Robot
Follow configured routes and access rules.
Handover
Recipients
Receive the arrival alert, use configured access and verify receipt.
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.
Users
Request
Select items, destination and required time.
Dispatch staff
Prepare and load
Check items, packaging and compartments; load manually and confirm.
Robot
Deliver
Follow configured routes and access rules.
Recipients
Handover
Receive the arrival alert, use configured access and verify receipt.
Managers
Retain records
Review completion, exceptions and handover records.
Confirm execution separately from human handover/review; assigned staff take over exceptions.
Roles
Dispatch and receiving staff
Request, prepare, load, verify and acknowledge receipt.
Robot
Transport, notify and return status within the configured scope.
Management and support
Maintain points, schedules, equipment, exception handling and records.
Service modes
Select modes for the workflow; agree extensions separately.
Indoor delivery
KAGO handles frequent floor/department runs.
Task sources
Configure manual, system-created or scheduled tasks.
Medication, specimens, medical waste, meals and heavy handling belong to separate solutions, outside the default general-supplies scope.
Terminals and configuration
Document-based scope; confirm supplied model, options and site fit.
TRANGO and KAGO
Select for batches, routes and compartments; staff transfer between robots if needed.
Systems
Run independently; assess optional HIS/logistics APIs.
Suitability
Scenario fit
Move office supplies, linen, care consumables and support items from central stores to departments, focusing on standardized small items and repeat routes.
Campus transport
TRANGO moves batches from central stores to buildings.
Indoor delivery
KAGO handles frequent floor/department runs.
Task sources
Configure manual, system-created or scheduled tasks.
Where the service helps
Reduce repeated trips around these tasks and define on-site handovers.
| Service area | Service scope |
|---|---|
| Campus transport | TRANGO moves batches from central stores to buildings. |
| Indoor delivery | KAGO handles frequent floor/department runs. |
| Task sources | Configure manual, system-created or scheduled tasks. |
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.
Central store
Classify, check and load.
Building / department receipt
Configure password, badge or acknowledgement access.
Support
Confirm charging, waiting, doors and lifts.
Locations
- Central store
- Building / department receipt
- Support
Validate a complete loop
Central store → Building / department receipt → 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.
Load limits
Source KAGO reference: 20 kg total, 5 kg small/10 kg large compartment; TRANGO: 150 kg total. Confirm supplied-model and compartment limits.
Human ownership
Hospital staff own store checks, receipt, exception returns and cleaning procedures.
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 | Central store, Building / department receipt, 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 | Dispatch and receiving staff, Robot, Management and support | Agree notifications, staff takeover, records and review rules. |
Fleet planning
Pilot and expansion
The document recommends one store, one building and three to five frequent departments before expanding.
TRANGO and KAGO
Select for batches, routes and compartments; staff transfer between robots if needed.
Systems
Run independently; assess optional HIS/logistics APIs.
Sizing considerations
| Sizing variable | Effect on capacity |
|---|---|
| Task cycle | Measure request, execution, handover, return and charging time. |
| Site scope | Central store, Building / department receipt, 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
Site preparation
The document recommends one store, one building and three to five frequent departments before expanding.
Configure and commission
Once prerequisites are ready
Check devices, routes, points, accounts and necessary access/system interfaces.
Trial and acceptance
As agreed for the project
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
Medication, specimens, medical waste, meals and heavy handling belong to separate solutions, outside the default general-supplies scope.
Responsibilities
Dispatch and receiving staff, Robot, Management and support
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
- TRANGO and KAGO
- Select for batches, routes and compartments; staff transfer between robots if needed.
- Systems
- Run independently; assess optional HIS/logistics APIs.
Document and current product versions may differ; confirm supplied specifications and project configuration.
Common questions
Where should the pilot start?
The document recommends one store, one building and three to five frequent departments before expanding.
How do robots and staff share work?
Dispatch and receiving staff：Request, prepare, load, verify and acknowledge receipt. Robot：Transport, notify and return status within the configured scope. Management and support：Maintain points, schedules, equipment, exception handling and records.
What needs separate confirmation?
Medication, specimens, medical waste, meals and heavy handling belong to separate solutions, outside the default general-supplies 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.
Plan a project
Pilot preparation
The document recommends one store, one building and three to five frequent departments before expanding.
Discuss the solution- Scope and points
- Central store, Building / department receipt, 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
- Dispatch and receiving staff, Robot, Management and support 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 indoor public-area security patrol
Support hospital security through scheduled/ad hoc indoor rounds, live views, remote voice, checkpoint photos and event records.