NextGen FSM
2026 Wave Two 2026 Wave Three 2026 Wave One
2026 Wave Two 2026 Wave Three 2026 Wave One

Access the emergency response archive

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:

Follow the UI path

All following instructions start from this system path:

  1. Navigate to Features > Core > Daily and Multi-day Plan > Daily Plan.

  2. On the Daily plan page, go to the Filters panel.

  3. Enter either:

    • Saved search.

    • Operations center and Date.

  4. Include any desired parameters.

  5. Click Search.

  6. On the Daily plan page, click the Emergency response tab.

  7. Click the Archive button.

Open the emergency response archive

To view all of the data collected from a previous emergency response:

  1. To see a high-level view of each emergency response execution, view the Processing list table.

  2. To analyze the data of a processing run, select a row from the Processing list, and examine these tabs in the Detail panel:

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:

  1. In the Processing list table, in the row you want to access, click the Three dots icon.

  2. 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