Specifications for Load and Publish Work Package

The following tables contain specifications for data to create or update a work package and its contents either by publishing a work package from Maintenix or loading a .csv file with work package data.

Columns must be ordered by the Column No. when creating a .csv file to load work packages and their contents. If the value for a column is not mandatory, the value for the column in the file can be empty with a semicolon used as a delimiter before and after.

For work packages published from Maintenix, the value for any ID field is the ALT_ID.

Work Package Creation and Update

Column No.	Column Name	Description	Mandatory	Maximum Length
1	Line Type	The data set type. Must be WP for Work Package rows.	Yes	3
2	Work Order ID	The Work Order ID references the packaging in the external M&E system. E.g.: WO - 1218336.	Yes	80
3	Aircraft ID	The aircraft of the work package which is the concatenation of the Aircraft Type and Aircraft Registration Code. The Aircraft ID must be the aircraft type and aircraft registration code for an aircraft created previously in the system. E.g.: B737-200 236.	Yes	20
4	Work Package Name	A field describing the work package contents. E.g.: SERVICE.	Yes	500
5	Start Date	The starting date of the work package in the format yyyy-mm-dd hh:mi:ss. E.g.: 2022-07-15 17:45:00 Note: If Line Maintenance Execution is integrated with Maintenix, the format must be YYYY-MM-DDTHH24:MI:SS.Z where Z is the timezone.	Yes	Not applicable for date/time fields
6	Duration	The duration of the work package in HH:MM format. E.g.: 00:30.	Yes	10
7	Location	The maintenance location at which the work package is scheduled to take place. This must be a valid location set up on the *Maintenance Locations* page.	Yes	1000
8	Status	The current status of the work package. Valid values when creating a work package are Active, Committed and Canceled. You can change the status of an Active or Committed work package. Other status changes are not allowed. Canceling a work package deletes the contents of the work package including any tasks and faults assigned to the work package. To update work package details, the status of the work package must be Active or Committed. You cannot update canceled work packages.	Yes	50

In addition to the specifications above:

A flight must be scheduled to arrive at the airport of the work package location before the work package scheduled start time.
Only one work package must be committed at the location and time of an aircraft turn.
The turn status of the turn for the work package in Maintenance Execution must be Inbound or Arrived. For turns in the In Maintenance status, and where the work package has the status In Work in Line Maintenance Execution, you can only assign or un-assign tasks and faults from a work package.

Task and Fault Creation and Update

Column No	Column	Description	Mandatory	Maximum Length
1	Line Type	The data set type. Must be T for Task rows.	Yes	3
2	Work Order ID	The Work Order ID references the packaging in the external M&E system. E.g.: WO - 1218336. The Work Order ID must be for a work package created for the aircraft specified in the Aircraft ID.	Yes	80
3	Aircraft ID	The aircraft of the work package which is the concatenation of the Aircraft Type and Aircraft Registration Code. The Aircraft ID must be the aircraft type and aircraft registration code for an aircraft created previously in the system. E.g.: B737-200 236.	Yes	20
4	Task ID	The external identifier for the task. E.g.: T-001, If a task by the Task ID has not been created previously, a new task is created. If not, the task is updated.	Yes	80
5	ATA/Config Position	The ATA chapter or configuration position to which the task or fault relates. E.g.: 00-00. This is a free text field. For a task in a work package published from Maintenix, this is the config position. If it has not been specified, this is the config slot.	Yes	80
6	Task Type	The task type for the task. E.g.: CORR	Yes	16
7	Task Code	The task code for the task. E.g.: TASK01. This is not mandatory for ad-hoc tasks.	No	200
8	Task Name	The name of the task. E.g.: Task 01	Yes	200
9	Status	The status of the task. To create or update tasks, the value must be ACTIVE.	Yes	20
10	Estimated Duration	The estimated duration of the task in HH:MM.	No	10

Column No	Column Name	Description	Mandatory	Maximum Length
1	Line Type	The data set type. Must be F for Fault rows.	Yes	3
2	Work Order ID	The Work Order ID references the packaging in the external M&E system. E.g.: WO - 1218336. The Work Order ID must be for a work package created for the aircraft specified in the Aircraft ID.	Yes	80
3	Aircraft ID	The aircraft of the work package which is the concatenation of the Aircraft Type and Aircraft Registration Code. The Aircraft ID must be the aircraft type and aircraft registration code for an aircraft created previously in the system. E.g.: B737-200 236	Yes	20
4	Fault ID	The external identifier for the fault. E.g.: F-0001. If a fault by the Fault ID has not been created previously, a new fault is created. If not, the fault is updated.	Yes	80
5	ATA/Config Position	The ATA chapter or configuration position to which the task or fault relates. E.g.: 21-10. The ATA chapter must have been created previously.	Yes	80
6	Description	The description of the fault.	Yes	500
7	Fault Source Code (Optional)	The code for the fault source of the fault. E.g.: CABIN. This must be a fault source code previously created on the *Fault Sources* page.	No	20
8	Fault Raised on Date	The date the fault was found on in the format yyyy-mm-dd hh:mi:ss. E.g.: 2022-07-15 17:45:00 Note: If MM is integrated with Maintenix, the format must be YYYY-MM-DDTHH24:MI:SS.Z where Z is the timezone.	Yes	Not applicable for date/time fields
9	Logbook Type (Optional)	The code of the logbook type. This must be a logbook type previously created on the Logbook Types page. E.g.: CABIN	No	8
10	Logbook Reference (Optional)	If the fault was first recorded in a logbook, the logbook reference is the logbook reference number. E.g.: RL00001	No	80
11	Status	The status of the fault. Valid values are Open or Deferred.	Yes	20
12	Failure Type Code	The code for the category of failure on the fault. E.g.: A referring to Bent, Buckled or Distorted failures	No	8
13	Fault Code	The fault code.	No	80
14	Found By User	The username of the user who found the fault. E.g. MXI.	No	40
15	Phase of Flight Code	The code for the phase of flight during which the fault was found. E.g.: TAXI for taxi-off.	No	8
16	Estimated Duration	The estimated duration of the fault in HH:MM. E.g.: 00:30.	No	10

You can also only assign/un-assign tasks/faults for a work package which has a status of Active/Committed or In Work. You cannot do so from a work package which has a status of Canceled or Completed.
If parts, tools, actions, and skills are defined on faults, they are copied to the corresponding task as well.
When tasks and faults are removed from a work package, for tasks and faults with the work task status set to Active, the tasks and faults are removed from the work package and any parts, tools, actions, measurement, steps, and skills defined on these tasks and faults are deleted.
To remove a task or fault from a work package you must delete the row for the task from the work package loader file and upload the work package loader file. The corrective task that was previously created for the fault is removed as well.
The Task ID is displayed in the External ID field of Task Details page and the Fault ID is displayed in the External ID field of the Fault Details page as well External ID field of the Task Details page for the corrective task for the fault.
If a fault was raised in Line Maintenance Execution, no changes can be made to the fault using the work package integration.
For faults raised in Line Maintenance Execution with an integration with Maintenix, on deferral the fault is created and deferred in Maintenix. If such a fault is published via another work package to Maintenance Execution only fault details such as Description, ATA, Fault Code, Logbook Reference, Fault Type, Fault Source, and Phase of Flight can be updated on the fault.

Work Package Work Types Creation and Update

Column No	Column Name	Description	Mandatory	Maximum Length
1	Line Type	The data set type. Must be WT for Work Type rows.	Yes	3
2	Work Order ID	The Work Order ID references the packaging in the external M&E system. E.g.: WO - 1218336. The Work Order ID must be for a work package created for the aircraft specified in the Aircraft ID.	Yes	80
3	Aircraft ID	The aircraft of the work package which is the concatenation of the Aircraft Type and Aircraft Registration Code. The Aircraft ID must be the aircraft type and aircraft registration code for an aircraft created previously in the system. E.g.: B737-200 236	Yes	20
4	Work Type Code	The code for the work type on the work package. E.g.: TURN, LINE or SERVICE.	Yes	8

Task/Fault Action Creation and Update

Column No.	Column Name	Description	Mandatory	Maximum Length
1	Line Type	The data set type. Must be TFA for Task Fault Action rows.	Yes	3
2	External ID	The external identifier for the task action. E.g.: TFA-001, If a task action by the External ID has not been created previously, a new task action is created. If not, the task action is updated.	Yes	80
3	Task Fault ID	The ID of the task or fault for the action. E.g.: T-001	Yes	80
4	Action Order	The sequence of the actions on the task. E.g.: 1. The action order of actions must follow a sequence. i.e. To accept an action with action order 2, the task must have an action with action order 1.	Yes	Not applicable for number fields
5	Action User	The codename for the user who performed the action on the task. This must be a valid user in IFS Cloud. E.g. MXI.	Yes	30
6	Action Description	The description of the corrective action on the task. E.g. replaced lamp.	Yes	4000
7	Action Date	The date the action was logged, in the format yyyy-mm-dd hh:mi:ss. E.g.: 2023-01-15 17:45:00 Note: If MM is integrated with Maintenix, the format must be YYYY-MM-DDTHH24:MI:SS.Z where Z is the timezone.	Yes	Not applicable for date/time fields

Task/Fault Skill Creation and Update

Column No.	Column Name	Description	Mandatory	Maximum Length
1	Line Type	The data set type. Must be TFL for Task Fault Labor rows.	Yes	3
2	External ID	The external identifier for the labor row. E.g.: TFL-001, If a task skill by the External ID has not been created previously, a new task skill is created. If not, the task skill is updated.	Yes	80
3	Task Fault ID	The ID of the task or fault for the skill. E.g.: T-001	Yes	80
4	Competency ID	The code for skill/competency on the task/fault. E.g.: 1. The skill must be a valid skill that exists as a competency in IFS Cloud. A minimum of one skill must be added for a task/fault	Yes	20
5	No of People Required	The number of resources for a required skill on the task. E.g. MXI. The number of resources must be 1 or more.	Yes	Not applicable for quantity fields
6	Hours per Person	The number of hours per resource for the required skill on the task in the HH:MM format. E.g.: 00:30	Yes	10

Task/Fault Tool Creation and Update

Column No.	Column Name	Description	Mandatory	Maximum Length
1	Line Type	The data set type. Must be TFT for Task Fault Tool rows.	Yes	3
2	External ID	The external identifier for the tool row. E.g.: TFT-001, If a task or fault tool by the External ID has not been created previously, a new task or fault tool row is created. If not, the task or fault tool row is updated.	Yes	80
3	Task Fault ID	The ID of the task or fault that requires the tool. E.g.: T-001	Yes	80
4	Tool Specification	The tool specification code for the tool required on the task or fault. E.g.: N/A Electrical Tape	False	50
5	Tool Part No	The part number of the tool required on the task or fault. E.g.: .	Yes	40
6	Tool Estimated Duration	The scheduled time that the tool is required in HH:MM. E.g.: E.g.: 00:30	Yes	10

The above only supports the creation and update of tool requirements for tools originating from Maintenix, on tasks and faults for work packages in Line Maintenance Execution.

Task/Fault Part Creation and Update

Column No.	Column Name	Description	Mandatory	Maximum Length
1	Line Type	The data set type. Must be TFP for Task Fault Part rows.	Yes	3
2	External ID	The external identifier for the part row. E.g.: TFP-001, If a task or fault part by the External ID has not been created previously, a new task or fault part row is created. If not, the task or fault part row is updated.	Yes	500
3	Task Fault ID	The ID of the task or fault that requires the part. E.g.: T-001	Yes	80
4	Position	The config slot position on which the part is required. E.g.: N/A Electrical Tape	Yes	260
5	Assembly Position	The assembly position for which the part is required. E.g.: 1. The assembly position must be a valid position in Maintenance Execution for the assembly and part group.	No	260
6	Part Group Code	The part group code of the part to be installed/installed part. E.g.: The part group code must be valid for the assembly in Line Maintenance Execution.	Yes	110
7	Removed Part No	The part number of the part to be removed/removed part. If there is a removed part, the removed quantity and removed part manufacturer are required. The removed part no must be valid for the part group in Line Maintenance Execution and the inventory class code of the removed part and installed part must be the same.	Yes	40
8	Removal Reason	The code for the reason for part removal. E.g.: IMSCHD for Unscheduled Failures. The removal reason must be a removal reason set up prior in Maintenance Execution.	No	8
9	Installed Part No	The part number of the part to be installed/installed part. If there is an installed part, the installed quantity and installed part manufacturer are required. The installed part number must be valid for the part group in Line Maintenance Execution, and the inventory class code of the removed part and installed part must be the same.	Yes	40
10	Installed Quantity	The number of installed parts/parts to be installed. E.g.: 2. The installed quantity of tracked and serial parts must be 1.	Yes	Not applicable for quantity fields

Task/Fault Measurement Creation and Update

Column No.	Column Name	Description	Mandatory	Maximum Length
1	Line Type	The data set type. Must be TM for Task Measurement rows.	Yes	3
2	Task ID	The ID of the task that requires the measurement. E.g.: T-001	Yes	80
3	Measurement Type Code	The code for the measurement type against which the measurement value is recorded. E.g.: DENTDIA	Yes	80
4	Measurement Value	The value of the measurement. E.g.: 2.	Yes	4000

Task Step Creation and Update

Column No.	Column Name	Description	Mandatory	Maximum Length
1	Line Type	The data set type. Must be TS for Task Step rows.	Yes	3
2	External ID	The external identifier for the step row. E.g.: TS-001, If a task or fault step by the External ID has not been created previously, a new task step row is created. If not, the task step row is updated.	Yes	80
3	Task ID	The ID of the task for which the step is applicable. E.g.: T-001	Yes	261
4	Step Order	The sequence number of the step. E.g.: 1.	Yes	Not applicable for quantity fields
5	Applicability	The applicability range for the step. E.g.: 2.	No	4000
6	Primary Skill	The code for the primary skill. E.g.: AVIONICS	No	200
7	Secondary Skill	The code for the secondary skill. E.g.: CLEAN	No	200
8	Step Description	The description of the step. E.g.: Clean filtration panel.	Yes	2000

Once steps have been published, when recording work on tasks, Maintenance Execution displays a maximum of 60 steps on a task in the mobile application.
Line Maintenance Execution supports a maximum of 2 skills, a primary skill and secondary skill, for a step. Step skills are not visible on a task card when recording work but are displayed on the Task Step tab of the Line Maintenance Work Package Loader page.