Fleet details for forecasting

Fleet details data fields that affect forecasting
Field	Change to data	Forecast result
Fleet	Change the fleet number.	Successfully forecasts. Notes: The new fleet number must not have a subfleet to successfully forecast. If the new fleet is not applicable to a track, the aircraft and its visit will still display their original values after forecasting. If the fleet number is changed and the new fleet number has a subfleet, a validation error occurs and no forecasting results.
Fleet	Change the fleet to one that does not currently exist in the system.	Does not forecast; user sees an error.
Subfleet	Change the subfleet to one that does not currently exist in the system.	Forecasts with a warning.
Manufactured Date	Change the manufactured date.	The first task due date successfully forecasts. The visit end date does not change and future iterations of the task due date do not change.
In Service Date	Change the in service date.	The first task due date successfully forecasts. The visit end date does not change, and future iterations of the task due date change based on the FIS rule.
Planned Retirement	Change the planned retirement date of an aircraft to be earlier than the retirement task's previous task due date.	Does not successfully forecast, but no error is shown.
Planned Retirement	Change the retirement date of an aircraft to be later than the current retirement task's due date.	The task is created as an individual visit and put in overflow.