Hangar Maintenance Work Package Loader

Work packages and their contents can be created and updated either through the publishing of the work package from Maintenix or loading a .csv file with work package data from an M&E system to Hangar Maintenance Execution.

The Hangar Maintenance Work Package Loader enables line planners to:

1. Create and update work packages and their contents for planned maintenance to be executed by hangar technicians. This can be achieved through the upload of a semi-colon separated value (.csv) file with data for work packages. The line planner prepares a semi-colon separated value (.csv) file with data for work packages and its contents from an M&E System to fit the structure required by the Hangar Maintenance Work Package Loader. Refer to the activity description for Load Work Package for information on the file preparation.
2. Monitor the success or failure of the creation and update of work packages and their contents loaded either through the .csv file upload or through the publishing of work packages from Maintenix to Hangar Maintenance Execution.

After loading or publishing, the work package file is processed and reaches a state of:

1. Completed when the processing is successful and hasn't resulted in any errors.
2. Failed when the file is not successfully processed due to a data or business rule validation.
3. Error when the file is not successfully processed due to an unexpected processing error.

The creation and update of work packages and their contents come into effect only if the execution status of the file is Completed and no errors were raised on any of the rows or file lines. If the file status is Failed or Error, you must fix the data in the file or basic data in Hangar Maintenance Execution based on the error raised and upload the file or publish the work package from Maintenix again.

The process of updating the work package is iterative until it is ready for execution.

 Loading Work Package File or Publishing Work Packages from Maintenix

To create or update a work package in Hangar Maintenance Execution:

1. A comma separated value (.csv) file can be loaded directly using the Hangar Maintenance Work Package Loader page. Multiple work packages can be created or updated at a time via file loading.
2. A work package can be published from Maintenix. Publishing work packages from Maintenix can be done one work package at a time, which in turn creates a file with work package data and it's content which is loaded to the Hangar Maintenance Work Package Loader. 

Work packages that are loaded or published, containing tasks and faults, create or update the same tasks and faults for the work package in Hangar Maintenance Execution. It is also possible to create or update the work types for work packages on work packages in Hangar Maintenance Execution.

Skills/labor, part changes, tools and actions defined for tasks and faults in a work package can be created and updated for the same tasks and faults in the work package in Hangar Maintenance Execution. Additionally, measurements and steps for tasks can be created and updated similarly.

The work package file must be always loaded in its entirety. The Work Package Loader does not expect partial work packages or loading only changes. For faults that have been deferred in Maintenix, via initiating the deferral in Mobile Maintenance in Aviation, and thereafter published to Hangar Maintenance Execution as part of another work package, fault details can be updated via publishing the work package in Maintenix.

Basic data corresponding to the data for the work package and its contents must be set up in Hangar Maintenance Execution to avoid the work package upload or publish failing due to invalid data. Values for the mandatory fields must be specified according to work package specifications as required by the Hangar Maintenance Work Package Loader. See About Specifications for Load and Publish Work Package for details.

Note: Hangar maintenance planners can cancel work packages that are in the Committed but not In Work status and republish them to execution teams as canceled work packages.