The escalation function is designed to notify the relevant parties of a delay in order execution within the maintenance workflow. It is activated under the following conditions:
The "Acceptance by Contractor" deadline has been reached, but the order has not yet been accepted by the contractor
The "Execution Due Date" has been reached, but the order has not yet been reported as completed
The "Inspection and Acceptance" deadline has been reached, but the work has not yet been accepted
Note: For one-time orders, the escalation dates are defined centrally in the order by entering the "Deadline: Acceptance by Contractor," "Execution Deadline," and "Deadline: Inspection and Acceptance" in the order form. For recurring orders, these are calculated by the system but can be adjusted manually.
If the specified dates are exceeded, the escalation function triggers email notifications to the relevant parties. There are two escalation levels, resulting in emails sent at two different escalation points with varying degrees of urgency.
This table shows which role participating in the maintenance workflow receives which emails and when (1 = email in escalation level 1; 2 = email in escalation level 2).
Target start date exceeded | Target end date exceeded | Target completion date | |
|---|---|---|---|
Responsible Coordination Team | 1, 2 | 1, 2 | 1, 2 |
Responsible for coordination: Contractor | 1, 2 | 1, 2 |
|
Implementing |
| 1, 2 |
|
Property / Asset Manager |
|
| 1, 2 |
Note: If no single person is assigned to the respective responsibility, all members of the group assigned to that responsibility will receive an email.