Decision 1: What are you monitoring?
The first question determines your signal type.| You care about… | Signal Type | Example |
|---|---|---|
| A specific object’s behavior — where it goes, how long it stays, how fast it moves | Track State | Obstruction, wrong-way, speeding, loitering |
| What’s happening in a zone — how many objects are in it, regardless of which specific objects | Zone State | Congestion, congregation, occupancy limits |
| How two objects interact — proximity, overlap, co-location | Track State (batch) | Near-miss, PPE compliance, tailgating |
Decision 2: Do you need real-time alerting?
This determines your mode.- Yes — use Streaming
- No — use Batch
You need to react while conditions are developing. The workflow executes on every detection update.Trade-offs:
- Higher processing volume (hundreds of executions per track)
- Can alert while the event is still happening
- Required for zone state monitoring
- Must handle event closure separately (close path on the orchestrator)
Decision 3: Which check node?
Based on your signal type, choose the appropriate check node(s):For Track State
| Check Type | Use when… | Requires |
|---|---|---|
| Type I — Track in Zone | You need to check if a track is in a zone meeting threshold conditions (dwell time, intersection, velocity) | Streaming or Batch |
| Type II — Zone Sequence | You need to check if a track visited zones in a specific order | Streaming or Batch |
| Type III — Track Interaction | You need to check if two tracks interacted (proximity, overlap) | Batch only |
For Zone State
| Check Type | Use when… |
|---|---|
| Zone Activity Check | You need to check aggregate zone conditions (track count, per-track dwell time and intersection thresholds) |
Decision 4: Event scope
The Event Orchestrator prevents duplicate events by scoping them to an entity:| Scope | Use when… | Example |
|---|---|---|
| Track | One event per tracked object | Obstruction — each vehicle gets its own event |
| Zone | One event per zone | Congestion — one event per zone regardless of which tracks are in it |
| Device | One event per camera | Camera-level alerting |
| Site | One event per site | Site-wide incident tracking |
Quick reference: common use cases
| Use Case | Mode | Signal Type | Check | Scope | Guide |
|---|---|---|---|---|---|
| Obstruction / loitering | Batch | Track State | Type I | Track | Guide |
| Congestion | Streaming | Zone State | Zone Activity | Zone | Guide |
| Zone intrusion | Streaming | Track State | Type I | Track | Guide |
| Wrong-way detection | Streaming | Track State | Type II | Track | — |
| Speeding in zone | Streaming | Track State | Type I | Track | — |
| Safety near-miss | Batch | Track State | Type III | Track | — |
| PPE compliance | Batch | Track State | Type III | Track | — |
| Congregation | Streaming | Zone State | Zone Activity | Zone | — |
| Checkpoint bypass | Streaming | Track State | Type I + II | Track | — |