Contracts
Service contracts can be inserted into Optimize My Day to handle long-term contractual obligations. Optimize My Day will create service orders automatically, taking the visit frequency into account.
Service orders are created before the next visit is due. The timespan between the date of service order creation and the due date is referred to as margin. If a maintenance task for the current interval does not exist yet, it will only be created if the interval has not past a limit. Margin and limit are defined as a preference, along with the default status code used during the creation of a new maintenance task.
Example
Suppose we have a service contract with two lines. Each line indicates a frequency of 6, meaning that the customer's equipment must be serviced every two months. The contract started on January 1, 2010. Using a margin of two weeks, the first new service order in 2010 was created mid February, with an earliest/latest of March 1 to March 31. The last service order created in 2010 ranged from January 1 to January 31, 2011. It was created mid of December 2010. Since the contract lines have identical frequencies, the two corresponding service orders will be planned as a group, i.e. the planning algorithms will consider both service orders as joined visits which should be planned for the same trip.
Generated tasks are given a time frame (earliest/latest) that corresponds to the visit frequency:
| Frequency | Days |
|---|---|
| 1 | 30 |
| 2 | 30 |
| 6 | 30 |
| 12 | 30 |
| 24 | 15 |
| 52 | 7 |
| 182 | 3 |
| 365 | 1 |
In case of inspections, a value indicating the month of the first inspection will be used to create the next annual service order within the same month.
From time to time the execution of a task might be delayed to the end of the time frame they were created for. After exceeding the middle of the time frame, OMD will decide to create the next task for the second half of the next interval earliest.