Incidents are automatically created when a defined rule in an Area is triggered. These rules monitor sensor data and generate alerts when specific conditions are met. For more details on setting up sensors and defining rules, refer to the How to Use Sensors page.

​
How Incidents Are Created

  • Incidents are triggered by rules set in Areas where sensors are monitoring real-time data.
  • A rule is usually based on a threshold or limit being exceeded (e.g., maximum people count, high temperature, or no facemask detected).
  • When a rule condition is met, PADS4 automatically logs an incident.

​
Viewing and Managing Incidents

The Incidents page provides a log of all active incidents that have not yet been resolved.

​
Incident Details

  • Clicking on an incident entry will display detailed information about the event.
  • If an image is associated with the incident, it will be displayed in the details.

​
Resolving an Incident

  • To resolve an incident, click the Resolve button.
  • This action notifies the system that the issue has been addressed.
  • Once resolved, the incident is removed from the active list.

​
Incident Data Storage and Retrieval

  • All incidents are stored in a database for analysis, reporting, or integration with other systems.
  • Incident data can be retrieved and used through:
    • PADS4 Sensor Data Provider
    • Third-party tools that connect to the database

​
Choosing a Database

  • During initial setup, you can select the type of database where incident data will be stored.
  • This ensures that historical incidents can be analyzed or exported when needed.

​
Key Takeaways

✔ Incidents are automatically generated when predefined rules are triggered.
✔ The Incidents page logs all unresolved incidents with details and images.
✔ Incidents can be resolved with a single click.
✔ Incident data is stored in a database and can be accessed via PADS4 or external tools.