Work package loading spreadsheet
The following table lists the columns that must exist in any spreadsheet you use for loading or updating the work package of a project, in the order in which the columns must occur. Also provided are descriptions of the values to set, the maximum length, and any other restrictions that apply.
| Column name | Mandatory | Data type | Max. length in characters | Description |
|---|---|---|---|---|
| Action | Yes, when uploading new work package. No, when editing a work package. | Code | 6 | Specifies whether the task is new for the work package, or whether it must be removed from the work package. Select NEW when adding a new task. Set to CANCEL when canceling an existing task. Null value is acceptable when editing. |
| Task Name | Yes, for ad hoc tasks | Free-form text | 240 |
Name of the ad hoc task as it will appear in Maintenix. When creating tasks from requirement definitions—which you must identify using their requirement code in another column described below—there is no need to enter a name in this column. The task will inherit its name from the task definition. |
| Description | No | Free-form text | 4000 |
Description of the task as it will appear in Maintenix.
|
| Unique Identifier | Yes | Free-form text | 80 | Identifier that is unique within the project and that is used to identify the task. |
| Config Slot | No | Configuration slot where the task will be performed. When provided, must match existing config slot on assembly. When null, defaults to root, determined by task definition. |
||
| JIC Code | Auto-populated when applicable | Code | Leave this column blank. Not used when loading or updating the workscope. | |
| Requirement Code |
Yes to identify a task definition, otherwise No |
Code | 200 | The code assigned to the requirement task
definition. Leave blank for ad hoc tasks. |
| Task Subtype | No | Code | 8 | Identifies the type of task. In the production plan, PP&C uses this value when you assign tasks to phases automatically. Value must be a subclass code that exists in Maintenix. Not used for tasks created from task definitions. |
| Zones | No | Comma delimited set | Comma delimited list of aircraft zones where the task is performed. In the production plan, PP&C uses this value when you assign tasks to work areas automatically. The zone code must match a zone code already defined in Maintenix. Not used for tasks created from task definitions. | |
| Panels | No | Comma delimited set | Comma delimited set of panels where the task is performed. Can only be added to ad hoc tasks. | |
| Task Duration (Hrs) | No | Decimal | The expected number of hours from the start of the task to the completion of the task. When not specified, zero is used. Not used for tasks created from requirement task definitions, only used for ad hoc tasks. | |
| Instructions | No | Free-form text | 4000 | Any instructions associated with the ad hoc task can be entered here. These instructions appear in Maintenix when the technician accesses the Task Details. |
| Labor Skill #<x>* | Yes** | Code | 8 |
The code for the labor skill required on the task. The labor skill code must match a code that exists in Maintenix. You can specify up to five different labor skills in a task. Do not specify labor skills or hours per skill for tasks you are creating using requirement task definitions in Maintenix. You can use this column to edit skills on requirement task definitions. |
| Hours for Skill #<x>* | Yes** | Decimal |
The expected number of hours required for the labor skill. Do not specify labor skills or hours per skill for tasks you are creating using requirement task definitions in Maintenix. |
|
| Certification Required | No | YES or NO | If null, default is YES. When required, hours are set to zero. | |
| Inspection Required | No | YES or NO | If null, default is NO. When required, hours are set to zero. | |
| Status | N/A | Code | Used by the system to report the results of the load. Do not specify a value. | |
| System Comments | N/A | Text | Used by the system to report the results of the load. Do not specify a value. |
Notes
*For both of these fields, replace <x> with an integer. You can have up to five labor skills, and hours for skill, per task; this means you can have columns called Labor Skill #1, Labor Skill #2, Labor Skill #3, Labor Skill #4, and Labor Skill #5. The same applies to the column(s) called Hours for Skill.
**You must specify at least one Labor Skill and one Hours for Skill value for each ad hoc task. You do not have to do so for tasks based on requirement task definitions.