Audience: Dispatchers and support users
The archive stores the history of emergency response tasks. Review what happened during each processing run: which resources were evaluated, which resources were excluded and why. Determine which urgent work order (WO) operations were assigned and which ones couldn't be assigned.
Prerequisites
Before you start, make sure:
-
You have configured an emergency response.
-
A technician has logged in an emergency response to analyze.
Follow the UI path
All following instructions start from this system path:
-
Navigate to Features > Core > Daily and Multi-day Plan > Daily Plan.
-
On the Daily plan page, go to the Filters panel.
-
Enter either:
-
Saved search.
-
Operations center and Date.
-
-
Include any desired parameters.
-
Click Search.
-
On the Daily plan page, click the Emergency response tab.
-
Click the Archive button.
Open the emergency response archive
To view all of the data collected from a previous emergency response:
-
To see a high-level view of each emergency response execution, view the Processing list table.
-
Each row represents one emergency response processing run.
-
See Reference: Daily plan emergency response archive | Processing list.
-
-
To analyze the data of a processing run, select a row from the Processing list, and examine these tabs in the Detail panel:
-
Excluded resources: Identifies the resources excluded during the selected processing run and the cause.
-
Check here when a dispatcher asks why a nearby technician wasn’t selected.
-
Identify why an urgent WO wasn’t assigned, like there weren’t any possible resources to assign.
-
To understand the fields, see Reference: Daily plan emergency response archive | Excluded resources tab.
-
-
Emergency response activities: Verifies the successful outcome of the emergency response and confirms who received the urgent activity.
-
To understand the fields, see Reference: Daily plan emergency response archive | Emergency response activities tab.
-
-
Planning changes: Shows the changes to the operational plan when you reprocess the processing run and reorganize non-urgent activities.
-
Access the scheduling log
Audience: IT and support users who analyze the emergency response task behavior.
To see the scheduling engine’s operations log for the processing run:
-
In the Processing list table, in the row you want to access, click the Three dots icon.
-
In the Scheduling log option, see the standard Scheduling log page pre-filtered for the selected processing run.
Understand scheduling log content
The Processing details section displays the individual steps performed during the VRP/scheduling engine execution, such as:
-
Data initialization and activity state management.
-
Resource selection according to the scheduling model.
-
Valid resource list per day (excluded resources due to unavailability, team conflicts, etc.).
-
Loading of booking, blocked, monitored, and saturation activities.
-
VRP daemon selection and time slot configuration.
-
Processing period definition.
-
Assignment results and error traces.
Each step is logged with its execution timestamp and outcome, which allows the user to reconstruct the full decision chain of the emergency response task.
What’s next
-
To understand the status of urgent work without archive access, see View emergency response activities.