In the eTASK.Maintenance workflow, the most important date is the "Execution Due Date": the work must be completed by this date. Based on this date, all other dates are generated according to the selected order type and the tolerance periods specified therein.
Note: If there is a deviation from the originally planned "Execution Deadline" upon completion of the maintenance order, a notification is sent to indicate this. This allows, for example, the completion dates of subsequent orders to be adjusted. The deviation may also affect future order planning. Adjustments can then be made here as well.
Order Start Date: At this point, an automatically generated order changes from the status “Order Created” to the status “Review by Client.”
Note: This time is not relevant for one-time orders.
Client (AG) review deadline: By this time, the client should have reviewed the order and either forwarded it for further processing or closed it, for example, because the required maintenance tasks have already been completed by another maintenance activity.
Contractor Acceptance Date: By this date, the contractor should have accepted the order. The contractor may be a coordination office within or outside the client’s company and does not have to be the same as the executing company.
Deadline for Acceptance by Executor: By this date, the executing company should have accepted the order.
Note: When using the workflow without direct participation by the executing party, this workflow step—and thus this deadline—is omitted. The workflow can be customized accordingly using a plugin. If interested, please contact your eTASK representative.
Processing Deadline: By this date, the executing company should have reported the order as completed.
Deadline for review and acceptance: By this date, the review by the coordinator on the client side should be completed.
For the Client Review, Contractor Acceptance, and Processing Due dates, there are two reminder dates (escalations) for each, at which reminder emails are sent. If the respective workflow step is completed before the target date for that step is reached, no reminders are sent.
