Skip to main content

Scenario Management

A scenario defines "when EVA should send an alert." This page explains practical scenario-writing guidance, and each mode is covered in its own subpage.

Scenario Templates​

Scenario templates are reusable baselines for frequently used detection policies.
Applying a template first helps reduce setup time and keep team-wide operation standards consistent.

  • Use templates first when applying the same policy across similar sites.
  • For site-specific needs, apply a template and then adjust targets, details, and interval.
  • Use a clear naming rule such as location/task/risk for easier search and maintenance.


Scenario Writing Flow​

  1. Enter the target situation in a short, clear sentence.
  2. Check the generated scenario name, target objects, and situation text.
  3. Edit detailed conditions and advanced settings if needed.
  4. Save, monitor real alerts, and iteratively refine.

The key is iterative tuning based on real alert outcomes, rather than trying to finalize everything at once.



Writing Guidelines​

  • Keep one objective per sentence.
  • Use conditions that are distinguishable in the real environment.
  • Start with essential exceptions only; avoid overloading early.
  • Use short scenario names that are easy to search later.


Mode Guide​

  • Stepwise: Best when step-by-step logic and exception filtering are needed.
  • PPE: Best for checking protective equipment compliance.
  • Thinking: Best for interpreting visible risk events such as fire/smoke/fall.
  • Simple: Best for quickly checking object presence.

See details in each mode page below.



Operation Tips​

  • Split scenarios if similar alerts are repeated too often.
  • Keep only necessary detection targets.
  • If sensitivity seems off, check target/ROI/interval before rewriting the scenario.