Task lists are connected to the engineering change management. You can use the engineering change management to change master data of the task list with date validity. This can lead to data, which are valid today, no longer being valid at a particular time in the future, because the data was changed, deleted, or complemented. Among other things, the maintenance packages , which can be assigned to the individual operations of the task list, belong to the task list data.
In turn, the maintenance packages are the basis for the scheduling of strategy-based maintenance plans , for displaying task lists from the maintenance plan, the maintenance plan costing, and the scheduling overview and simulation.
The following text describes the effects of the change status of task lists on the maintenance planning.
When scheduling strategy-based maintenance plans, the maintenance packages that are assigned at the operation level in the task list are taken into consideration. Pay particular attention to the validity date of the affected task lists, the operations, and the assignment of the operations to maintenance packages.
Example
A package maintained in the maintenance strategy (for example, a two-month package) should lead to a maintenance call every two months in the maintenance plan scheduling. The package must be assigned to at least one task list operation, which is integrated in the maintenance item of the maintenance plan.
This assignment means that the two-month package in the maintenance plan is considered as used, and taken into consideration during the scheduling of the maintenance plan.
Whether a maintenance package is used (that is, is assigned to an operation in the task list) and is valid, is determined dynamically through the scheduling. This means, the master data of the task list are not read for a date (system date) and are set as constant. All packages, which were ever or will ever be used in a task list, are taken into consideration for scheduling. Even if, for example, the assignment of a package to an operation in the task list is only valid in the future.
The scheduling determines a “first” scheduling screen for the totality of “used” packages. If a deadline with a concrete planned date is determined, the system checks the validity of the packages for this date.
Invalid packages are deleted and not displayed. If no package is valid for the key date specified, the entire maintenance date is deleted. However, subsequent dates build on this date, and continue the package sequence of the strategy.
The display of task lists and packages follows the logic described above. For further information on peculiarities, see Displaying the Task List and Packages for the Key Date .
The
maintenance plan costing
uses the existing maintenance calls in a costing time period for a maintenance plan (that is, maintenance calls with the status
Called
and
On Hold).
Any deadlines that are still outstanding in that period are “simulated” on the basis of the existing deadlines. This simulation for strategy plans is done under consideration of the engineering change management for task lists.
In the scheduling overview and simulation you can also simulate additional deadlines for a freely definable period as well as the pre-existing deadlines. The simulation for strategy plans is also done under consideration of the engineering change management for task lists.