Detect Incidents

Detect Incidents tool icon The Detect Incidents tool evaluates features against a set of opening conditions and optional closing conditions and creates a unique incident for each continuous set of observations that satisfy the conditions.

Workflow diagram

Detect Incidents tool workflow diagram

Examples

  • Each vehicle in a fleet sends its location and current speed at regular intervals. If a vehicle's reported speed exceeds the posted speed limit for the location indicated, Detect Incidents opens an incident. For each subsequent observation reported by the vehicle, if its current speed continues to exceed the speed limit, the incident is maintained in an open state. When the vehicle reports its speed within the posted speed limit, the incident is closed.
  • A pressure sensor on a pipeline reporting the current measured pressure at a valve indicates a pressure out of normal operating range. Detect Incident opens an incident and continues to report an open incident each time the sensor indicates the pressure is out of normal range. When the pressure returns to normal, the incident is closed.
  • A convoy of trucks is approaching a tunnel where vehicles carrying hazardous materials are prohibited. Each vehicle reports its location and ArcGIS Velocity enriches the incoming information for each vehicles based on the current manifest of its cargo. One of the trucks is carrying oxidizers which are considered hazardous. Detect Incidents opens an incident based on the truck's proximity to the tunnel and its current cargo attributes. When the truck detours away from the tunnel the incident is closed.
  • A delivery vehicle assigned to a specified route area goes outside the area for a period of time. Detect Incidents opens an incident when the vehicle exits the assigned area and closes the incident when the vehicle reenters the area.

Usage notes

  • An Open Condition is required, however a Close Condition is optional. If a closing condition is not explicitly set, the logical NOT of the opening condition is implicitly used as the closing condition. An exception to this is if a spatial relationship of Enter or Exit is selected, the implicit Close Condition is Exit and Enter, respectively.
  • In a real-time analytic, if a spatial relationship of Enter or Exit is selected for the Open Condition or Close Condition, the tool will operate in a stateful manner which enables it to compare sequential observations to one another to detect a change in state, for example is the current condition different from that of the previous observation. With other spatial relationships in real-time analytics, the tool does not need to compare any observations with previous ones so it can run in a stateless manner, which is less resource intensive.
  • The tool has two inputs, however the Join Layer is only required if utilizing spatial relationships for the opening or closing conditions.
  • Open Condition and Close Condition are specified using Arcade expressions. For an overview of Arcade expressions and functions supported, see the ArcGIS Arcade documentation.
  • If the Close on Expiration parameter in a real-time analytic is set to Yes, any open incidents are closed when the Target Time Window expires. If set to No, any open incidents are discarded.
  • If a spatial relationship of Enter or Exit is selected for the Open Condition, then checking First observation can trigger enter or First observation can trigger exit indicates that the first target feature received can open an incident if it is inside any join feature in the case of Enter, or outside all join features in the case of Exit, despite having no prior target feature to which to compare the current target feature's location. The default is false (or unchecked).
  • The Target Time Window parameter in a real-time analytic should be at least as long as the longest anticipated interval between observations for any given track. Observations older than this duration will be purged from memory in order to manage resources.

Parameters

ParameterExplanationData Type

Input Layer

The features for which incidents will be detected using open and close conditions.

Features

Join Layer (optional)

Optionally choose which dataset to process a spatial relationship with as part of an opening or closing condition.

Features

Open Condition

The set of conditions that define the start of an incident. This can include a spatial condition, time range, and a set of attribute expressions.

  • Spatial Relationship—Defines the criteria used to spatially filter the target features. The parameter only appears if a dataset has been connected to the join port. Spatial operators include Disjoint, Enter (real-time analytics only), Equals, Exit (real-time analytics only), Near Geodesic, Near Planar, Touches and Within.
  • First observation can trigger enter and First observation can trigger exit—Enabled if Enter or Exit are selected as a spatial relationship and indicate the first target feature received can open an incident if it is inside any join feature in the case of Enter or outside all join features in the case of Exit, despite having no prior target feature to which to compare the current target feature's location. This default is false (unchecked).
  • Time Range—The time range in which the observation must take place. Choices include Between, Before, or After specified time(s).
  • Expression—An attribute expression to be evaluated to filter the incoming data. Attribute expressions are specified using Arcade expressions.
  • Match all open conditions—Whether the spatial, temporal, and attribute conditions must all be satisfied to open an incident. If No is selected, any one of the conditions will be sufficient to open an incident.

Parameters

Close Condition (optional)

The set of conditions that define the end of an incident. Like Open Condition, this can include a spatial condition, a time range, and a set of attribute expressions.

  • Spatial Relationship—Defines the criteria used to spatially filter the target features. This parameter only appears if a dataset has been connected to the join port. Spatial operators include Disjoint, Enter (real-time analytics only), Equals, Exit (real-time analytics only), Near Geodesic, Near Planar, Touches and Within.
  • Time Range—The time range in which the observation must take place. Choices include Between, Before, or After specified time(s).
  • Expression—An attribute expression to be evaluated to filter the incoming data. Attribute expressions are specified using Arcade expressions.
  • Match all open conditions—Whether the spatial, temporal, and attribute conditions must all be satisfied to open an incident. If No is selected, any one of the conditions will be sufficient to open an incident.

Parameters

Return Incidents Only

Whether to return only observations that relate to an incident (Yes) or all observations (No).

Boolean

TRACK_ID Fields (big-data analytics only)

Choose the field(s) to uniquely identify features to be processed. The parameter will be auto-populated if a TRACK_ID key field is set on the input layer.

Fields

Target Time Window (real-time analytics only)

Set the time window to at least as long as the longest anticipated interval between observations for any given track. Observations older than this duration will be purged from memory in order to manage resources.

String

Close on Expiration (real-time analytics only)

If set to Yes, any open incidents will be closed when the Target Time Window expires. If set to No, any open incidents are discarded.

Boolean

Output layer

The output layer will have the schema of the incoming features and will be enriched with the fields below.

Field NameDescriptionField Type

IncidentId

The unique identifier for the incident.

String

IncidentStatus

The current status of the incident including Started and Ended.

String

IncidentDuration

The number of seconds the incident was open.

Integer