Save Schedule Result to Database
Explanation
This activity is used to save your schedule changes to the database. By
performing this activity, changes
are saved directly to the database by Maintenance Planning Board (MPB) adhering
to the database validations.
Prerequisites
This activity requires:
- a work order or PM action occurrence schedule, when working with the
Maintenance Planning Board.
- at least one unsaved change in the schedule.
- when working with the Maintenance Planning Board, that no changes is made outside
of the
Maintenance Planning Board to
the items that you are trying to save. If there is a change in one or more
of the items, you will be notified of the modifications and will not be
allowed to save back via the Maintenance Planning Board. Only items which do not have modifications
can be saved.
System Effects
As a result of this activity:
- The schedule is saved to the database. The planned start and finish times of work
orders, work tasks, PM actions occurrences and
work lists will be updated if they have been scheduled.
- The Scheduling Status field on work tasks and
work lists of the PM action occurrences, will be updated to Scheduled
if Maintenance Planning Board was able to allocate resources and schedule
the work orders or PM action occurrences adhering to scheduling rules.
- The Scheduling Status of a work task and
work lists of the PM action occurrences, will be updated to Unscheduled if at least one of the jobs and one of the respective
work list is
"unscheduled" by Maintenance Planning Board due to the inability to meet any
of scheduling requirements or constraints.
- The Scheduling Status of a work task and work lists of the PM action occurrences, will be updated to Needs
Rescheduling if work order or PM action occurrence is not yet
scheduled by Maintenance Planning Board or the earlier created schedule is
changed by the user by modifying some attribute which affect scheduling.
- The Sched Status of a work order and
Scheduling Status
of a PM Action occurrence will be set as Resolved if all the jobs
and respective work lists are "scheduled" by Maintenance Planning Board.
- The Sched Status of a work order and Scheduling Status
of a PM Action occurrence will be set as Unresolved (Tardy) if all the jobs
and respective work lists are "scheduled" by Maintenance Planning Board but
the work order or the PM action occurrence is scheduled later than its
required finish date.
- The Sched Status of a work order and Scheduling Status
of a PM Action occurrence will be set as Unresolved if at least one of the
jobs and on of the respective work list is "unscheduled" by
Maintenance Planning Board due to the inability to meet any of the scheduling
requirements or constraints.
- The Sched Status of a work order and
Scheduling Status
of a PM Action occurrence will show Needs Rescheduling if
work order or PM action occurrence is not yet scheduled by Maintenance
Planning Board or the earlier created schedule is changed by the user by
modifying some attribute which affects scheduling.
- You will be notified if any of the changes cannot be saved successfully
by Maintenance Planning Board by displaying errors and notifications in the Error Messages window.
- If there are scheduled resource breaks, status and
the planned start and finish date of the resource break is updated to the
database.
Window
Maintenance Planning Board
Maintenance Planning Board for Planning Network
Related Window Descriptions
Maintenance Planning Board Client
Procedure
- Open the Maintenance Planning Board client.
- In the Site field, specify a site for which
you need to start Maintenance Planning Board.
- The Maintenance Planning Board opens and work
orders, PM actions along with other activities and data will be
loaded.
- Make the desired scheduling changes by using the Gantt chart.
- From the File menu,
choose Save or select Database Save... icon in the tool bar
-
The Saving Schedule
changes...dialog box will appear and the schedule will saved to
the database.
- You will be notified if there are no changes to be
scheduled or if there are any errors when saving to the database.