Description For scheduling, the system converts all the on-holdmaintenance calls>, with adate that satisfies the call horizon>, into amaintenance call object>(for example, maintenance order>) The system also performs a complete rescheduling of themaintenance plan>, and ensures that maintenancecalls exist for the next n days (field Scheduling period> in theScheduling parameters> screen). The system always generates atleast one on-hold maintenance call. Start deadline monitoring regularly (for example, using reportvariants). Deadline monitoring for a weekly strategy should ideally runevery week.Beispiel Scheduling period:,,,,,,,,30 days Report run on:,,,,,,,,,,January 1, 19XX Scheduling performed up to:,,,,February 1, 19XX Hinweis Even if you have not set a scheduling period>in the maintenance plan, scheduling> will always beperformed once. You no longer need to schedule the maintenance planmanually.Procedure In the initial screen, choose between the modes Call transaction>and Batch input> by selecting the appropriate field. The calltransaction mode is proposed automatically in the initial screen.Output You can display a list of all the maintenance call objects that thesystem generated during deadline monitoring. You can display the list of maintenance orders generated usingLogistics> -> Plant maintenance> -> Maintenanceprocessing> -> Orders> -> Display list editing>. In the field Entered by>, enter the group name that the systemproposes on the initial screen of the date monitoring session. IP1019950101,,--> All maintenance orders from January 1, 1995 IP10199501,,,,--> All maintenance orders in January 1995 IP101995*,,,,--> All maintenance orders in 1995 |