Scheduling a saved plan

Scheduling allows users to re-run the scheduling engine for visits and tasks that start after the specified scheduling start date (SSD.) It can be run for all aircraft, a single fleet, a single subfleet, or a single aircraft.

Scheduling will clear the existing visits that start after the SSD, and re-apply the same rules to current operational data.

General scheduling behavior

  • All unlocked visits (and their assigned tasks) which start after the SSD are cleared, and the scheduling engine regenerates the plan, from the SSD forward, using the current operational data.

  • Visits whose start dates are on or before the SSD are not updated to reflect the operational data, nor are their details changed or their tasks forecasted. i.e. Only visits whose start dates are AFTER the SSD are affected by scheduling.

  • Tasks that are assigned to visits whose start dates are on or before the SSD are not updated to reflect the operational data. This includes tasks whose optimal due dates are after the SSD, but have been assigned (manually, or by the scheduling engine) to a visit with a start date that is before the SSD.

  • Forecasting is run for all tasks whose visits start after the scheduling start date, including locked tasks and tasks assigned to locked visits. This could cause some locked tasks to become over due.

  • Any tasks that must be scheduled before the SSD will be placed into overflow. For example, new repeating or chained tasks where the first visit start date is before, or on, the SSD will be placed in overflow on their optimal due dates.

  • All visits on the Overflow or Retirement tracks are removed. If the current operational data requires them, they will be regenerated.

Locked visits and tasks

  • Locked visits and tasks assigned to locked visits are not moved, but are forecasted. This could cause some locked tasks to become over due.

  • Locked visits on a track that can no longer complete its tasks according to Location Capability will be left in place regardless.

Important:

There are some exceptions when locked visits are removed by scheduling:

  • Locked visits that are empty, or only contain ad hoc tasks, are removed.

  • Locked tasks, and tasks in locked visits, are removed if they are no longer applicable to the aircraft.

  • All visits on the Overflow or Retirement tracks are removed, even if they are locked. If the current operational data requires them, they will be regenerated, but will be unlocked.

Ad hoc visits and tasks

  • All ad hoc tasks are removed, unless they are assigned to a locked visit which also contains non-ad hoc tasks.

  • Ad hoc visits are treated the same as all other visits.

  • Visits are removed if they only contain ad hoc tasks even if the visit or tasks are locked. A locked visit must contain at least one non-ad hoc task to be retained.

Operational data changes that impact scheduling

Generally, any changes to your operational data will affect your plan when you run scheduling. Specifically, the following changes will affect your plan:
  • Adding new task definitions, including repeating or chained tasks that begin before the schedule change date

  • Modifying location capabilities

  • Adding new aircraft with applicable tasks
  • Adding new tasks to the end of a chain
  • Adding a new one-time task definition or repeating task definition that will apply to an aircraft.
  • Expanding task applicability rules. For example, tasks may be changed from applying to existing aircraft, to applying to subfleets and fleets.