Human-Approved Coordination for Robotic and Vision Systems

The problem

In day-to-day operations, camera events, robot status and safe-zone rules are held in separate records and files, preventing the team from reviewing the same case in a single view.

As a result, the link to source evidence can be lost while preparing a safe-stop recommendation and review record, leading to repeated checks and uncertainty about the basis for the decision.

Incomplete automation may overlook a person being detected, a loss of visibility or conflicting sensor readings, while poorly controlled automation risks physical harm.

What we set out to improve

• Time required to prepare a safe-stop recommendation and review record
• Correct routing of cases involving a person being detected, a loss of visibility or conflicting sensor readings to the appropriate specialist queue
• Recording of recommendations corrected or rejected by the site safety officer

How the system works

1. 01 Retrieve camera event, robot status and safe-zone rule data from an authorised source
2. 02 Verify the source system, record identifier and recency information
3. 03 Transform the fields into the target process schema
4. 04 Prepare a safe-stop recommendation and review record draft
5. 05 Compare the draft with business rules and source records
6. 06 Check for exceptions involving a person being detected, a loss of visibility or conflicting sensor readings
7. 07 Obtain the site safety officer's approval, correction or rejection
8. 08 Write the input, recommendation, changes and final decision to the audit log

Methods we used

• Source-traceable data extraction from camera events, robot status and safe-zone rules
• Structured output that restricts safe-stop and review record fields through business rules
• An exception gate that separates cases involving a person being detected, a loss of visibility or conflicting sensor readings
• A queue that shows the source and recommendation together for the site safety officer
• Duplicate-processing controls and rollback records to mitigate the risk of physical harm

Where people stay involved

Data and security

Only the fields required for the task are processed from camera events, robot status and safe-zone rules. Source-system permissions remain in force, and personal or commercially sensitive data is minimised before being provided to the model. Every read, recommendation, human amendment and write to the target system is logged.

Who this suits

Frequently asked questions