Last done for forecasting

Typically, a Last Done record for work completed needs to be matched up with a task and visit already on the plan. Once the matching/pairing is completed, Fleet Planner will only use the usages and completion date of the last done record to forecast and schedule future iterations of that repeating task or task chain. This overrides the usages and completion date the plan may have for that task.

When the last done record includes the iteration, it will be paired with task in the plan with the same Task Id, Aircraft, and Iteration.

When the last done record omits an iteration, Fleet Planner will try to match it with a task in the plan based on the visit start date. Fleet Planner will match with a task where the last done completion date is ONE day before, ON, or AFTER the visit start date of the task. For repeating tasks, there may be multiple visits in the plan with the matching task that start on or before the last done completion date. In this case, it will match with the most recent one.

Last done data fields that affect forecasting
Field Change to data Forecast result
Completion Date Update with new data. The next iteration of the task's due date and yield are updated.
Iteration
Due Date The next iteration of the FIS task’s due date and yield are updated
Hours The next iteration of the task's due date and yield are updated.
Cycles