Scenario A05

Zone Obstruction (No-Occupancy)

Ticket-based workflow for corridor/loading dock obstruction. Inspired by Verkada Operator View: every incident is triaged, assigned, and tracked.

Priority
Event Snapshot (placeholder)
B1-FIRE-001 · Fire corridor
Placeholder
Event Snapshot (placeholder)
Structured Output (mock)
Stable JSON for rule engine
{
  "is_obstructed": true,
  "obstruction_type": "Boxes",
  "obstruction_percentage": 65,
  "severity": "critical",
  "description": "Boxes occupy ~60% of corridor width."
}
Latency
2.3s
Estimated cost
$0.0012 / run
Zone Definition Tool (placeholder)
Rect / polygon region tool
zone tool
Define clear zones (fire corridor / loading dock). Use baseline photos to reduce false positives.
Policy & Escalation
Low-risk adoption for hallucination control
Escalation rule
Recommended
Raise alert only if obstruction is detected 2 consecutive runs or duration exceeds 30 minutes.
Operator workflow
Triage → assign → close. Keep audit log for compliance.