Location capability
This template defines the fleets and subfleets that can be received on a track. It also describes labor and other constraints.
| Column name | Required | Data type or format | Description and business rules |
|---|---|---|---|
| Track ID | Yes | Text field |
Must be unique. Used for scheduling and visit placement. Since it has a unique key, other elements of the track information (such as Track Name) can be modified without interrupting the existing schedule outputs. Displayed on the Gantt chart. |
| Hangar Name | Yes | Text field |
Short name that identifies the hangar. Not displayed on the Gantt chart. |
| Track Name | Yes | Text field |
Must be unique. Short name that identifies the track. Displayed on the Gantt chart for scheduling reference. |
| Fleet | *No | Comma-delimited list of Fleets |
Each individual Fleet must be listed in the Fleet Details template. *Fleet or Subfleet is required. |
| Subfleet | *No | Comma-delimited list of Subfleets |
Each individual Subfleet must be listed in Fleet Details. *Fleet or Subfleet is required. |
| Track Priority | No | Integer (whole number) | Priority assigned to the track while running the scheduling engine. 1 is the highest priority and priority decreases with increasing values. Tracks without a set priority field will receive the default priority of 100. |
| Task Type Priority Prefixes | No | Comma-delimited list of Task Type Prefixes | When task types priority prefixes are selected, the scheduling engine will prioritize scheduling matching task types on the track. If no value selected, all task types will be treated equally. |
| Task Type | *No | Comma-delimited list of Task Types |
Corresponds to Task Type in the Task Definition template. Used to match the applicability of a task to the track. This field is related to the "Ignore Location Capabilities" field in the Automerge Rules template. *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. |
| Proficiency Factor | No | Decimal number | Proficiency factor assigned to the track. A track with a proficiency factor of 2 means the track is more proficient, the turnaround time to complete the work is quicker on this track. A track with a proficiency factor of 0.5 means the track is less proficient, the turnaround time to complete the work is slower on this track. Proficiency Factor is a non-mandatory column and it's value should be limited to three decimal places. |
| Sunday | Yes | Integer (whole number) |
Labor hours available on that track for that day. |
| Monday | Yes | ||
| Tuesday | Yes | ||
| Wednesday | Yes | ||
| Thursday | Yes | ||
| Friday | Yes | ||
| Saturday | Yes | ||
| Daily Cost | No | Integer (whole number) |
Labor cost of this track. |
| Black Out Start | No |
Comma-delimited list of dates. YYYY-MM-DD |
Start date of a period when the hangar will be unavailable and unable to hold aircraft. Used in conjunction with Black Out End |
| Black Out End | No |
Comma-delimited list of dates. YYYY-MM-DD |
End date of a period when the hangar will be unavailable and unable to hold aircraft. Used in conjunction with Black Out Start |
| Leading Ferry Days | No | Integer (whole number) | Number of days required to get an aircraft to the location and ready for maintenance to begin. Decimal values are accepted, but truncated. They are not rounded. This value is not currently used by Fleet Planner. |
| Trailing Ferry Days | No | Integer (whole number) | Number of days required to get an aircraft back into service after maintenance is complete. Decimal values are accepted, but truncated. They are not rounded. This value is not currently used by Fleet Planner. |