Account for Work Order Notifications and Interventions

Synchronize data between a Work Order (WO) and its associated technical notification. When a technician debriefs an intervention, the system automatically populates the notification details. This ensures that breakdown times, asset anomalies, and technical causes are accurately recorded.

Access the Notification Debriefing Interface

You can access the notification accounting panel through three primary paths in the UI:

Find debriefs in work order search

To enter an outcome directly from a schedulable operation into the WO search:

1. Navigate to Feature > Core > Work Order Management > Search WO.

2. In the Filters menu, enter the WO’s search parameters.

3. Click Search.

See Search Work Orders.

Find debriefs in daily plan

To see debriefs as you plan a schedule: 

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

2. In the table, locate the WO.

3. Right-click the scheduled WO.

4. Click Intervention Outcome.

Find debriefs in execution monitor

To see debriefs as you monitor what tasks have been completed: 

1. Navigate to Features > Core > Analytics > Execution Monitor.

2. In the right Configuration panel, enter parameters, such as dates.

3. Click Process diagram.

4. On a record, click Options.

5. Click Intervention Outcome.

See Search Work Orders

Manage notification data

To edit and account for all notifications linked to the order and determine whether they were created during planning or on-site:

1. In the execution monitor, go to the Intervention outcome interface.

   • See Find debriefs in execution monitor.

2. In the Notifications tab lists, locate the notification row.

3. Click the Menu icon > Edit notification.

4. In the Update notification data tab, review basic info like priority and type.

5. If needed, edit:

   • Status.

   • Subject.

   • Anomaly.

   • Notes.

6. In the Update notification management tab, enter:

   • Breakdown start / end: When the machine went down and was restored.

   • Closure date: When the notification resolves.

     • The default is the intervention end time.

   • Cause: The technical root cause from the predefined catalogs.

   • Attachments: Any relevant photos or documents.

SAP Status Mapping

The Next-Gen FSM Platform synchronizes its internal status with SAP Status (E000X) to ensure consistency across the enterprise landscape.