Task definition
This template captures task definitions which include information about scheduling requirements.
For descriptions and examples of the various type of tasks supported in Fleet Planner, see Tasks.
| Column name | Required | Data type or format | Description and business rules |
|---|---|---|---|
| Task ID | Yes | Text field |
Task identifier. Must be unique. |
| Name | Yes | Text field | |
| Chained Tasks | No | Text field |
Only one chained task can have the initial range; all others must use repeat. With the exception of the initial chained task, all chained tasks must use NA in the Calculation From field. Initial range is defined on the first task in the chain. Subsequent tasks must have "repeat" range. To allow a one-time chained task to repeat on its own, you must chain the task to itself. When establishing a series of chained tasks, all tasks within the chain must have the same aircraft applicability. |
| Description | No | Text field | |
| Schedule | Yes | [LATEST, EARLIEST] |
Defines whether the scheduling engine uses the earliest or latest possible due date criteria. |
| Calculation From | Yes |
[NA, MANUFACTURE_DATE, EFFECTIVE_DATE, IN_SERVICE_DATE] |
The date the scheduling engine will use if Last Done data is not available, including for the first instance of a repeating or chained task, or for a one-time task. Must not be NA if the task is Due Date driven. This allows the scheduling engine to calculate yield. The NA value should only be used on chained tasks following a primary task. The task due date is then generated from the visit end date of the preceding task chain. If EFFECTIVE_DATE is noted, there must be an Effective Date defined. |
| Type | Yes | Text field |
Corresponds to Task Type in the Location Capability template. |
| Effective Date | *No | YYYY-MM-DD |
*Required if Calculation From value is EFFECTIVE_DATE The date to start counting the Initial Days, Hours or Cycles from. |
| Effective Hours | No | Integer (whole number) |
Decimal values are accepted, but truncated. They are not rounded to ensure no additional airframe hours are added. This value is not currently used by Fleet Planner. |
| Effective Cycles | No | Integer (whole number) |
Decimal values are accepted, but truncated. They are not rounded to ensure no additional cycles are added. This value is not currently used by Fleet Planner. |
| Initial Days | No | Integer (whole number) |
The number of days after the Calculation From date to schedule the first instance of this task. Decimal values are accepted, but truncated. They are not rounded to ensure no additional days are added. |
| Initial Hours | No | Integer (whole number) |
The number of usage hours after the Calculation From date to schedule the first instance of this task. Decimal values are accepted, but truncated. They are not rounded to ensure no additional hours are added. |
| Initial Cycles | No | Integer (whole number) |
The number of usage cycles after the Calculation From date to schedule the first instance of this task. Decimal values are accepted, but truncated. They are not rounded to ensure no additional cycles are added. |
| Repeat Days | No | Integer (whole number) | The number of days between repeating or cycled instances of a task. Decimal values are accepted, but truncated. They are not rounded to ensure no additional days are added. |
| Repeat Hours | No | Integer (whole number) | The number of usage hours between repeating or cycled instances of a task. Decimal values are accepted, but truncated. They are not rounded to ensure no additional hours are added. |
| Repeat Cycles | No | Integer (whole number) | The number of usage cycles between repeating or cycled instances of a task. Decimal values are accepted, but truncated. They are not rounded to ensure no additional cycles are added. |
| Due Date | No | YYYY-MM-DD |
Fixed scheduling date that is not affected by usage. If provided, Calculated From will only be used to calculate task yield. |
| FIS Days | No | Positive integer (whole number greater than 0) or null |
Fixed Interval Scheduling value (Days) |
| FIS Hours | No | Positive integer (whole number greater than 0) or null |
Fixed Interval Scheduling value (Hours) |
| FIS Cycles | No | Positive integer (whole number greater than 0) or null |
Fixed Interval Scheduling value (Cycles) |
| MinYield | No* |
Percent expressed as a decimal between 0 and 1 |
Cannot be less than zero or more than one. Up to three decimal places are supported. *This information must be entered for plans to be created or scheduled. If it is not included in an upload, it must be entered using the Data Management tool. |
| MaxYield | No* | Percent expressed as a decimal between 0 and 1 |
Cannot be less than zero or more than one. Up to three decimal places are supported *This information must be entered for plans to be created or scheduled. If it is not included in an upload, it must be entered using the Data Management tool. |
| Span | No* | Integer (whole number) |
The number of labor days the task requires. Must be greater than 0. *This information must be entered for plans to be created or scheduled. If it is not included in an upload, it must be entered using the Data Management tool. |
| Terminating Days | No | Integer (whole number) | When an aircraft has been in service this many days, this task will no longer repeat. |
| Terminating Usage Hours | No | Integer (whole number) |
When an aircraft accrues this many airframe hours, this task will no longer repeat. |
| Terminating Usage Cycles | No | Integer (whole number) | When an aircraft accrues this many airframe cycles, this task will no longer repeat. |
| Terminating Task | No |
Text field |
Task ID of the Terminating Task. When the Terminating Task occurs, the Task defined in this row will no longer repeat. Must exist in the Task Definition template. |
| Schedule by EOM | Yes | [TRUE, FALSE] |
Indicates if a task due date can be extended to the last calendar day of the month for which it is scheduled. |