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 Mobile Maintenance for Aviation.
The Mobile Maintenance Work Package Loader enables line planners to:
After loading or publishing, the work package file is processed and reaches a state of:
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 Mobile Maintenance for Aviation 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.
To create or update a work package in Mobile Maintenance for Aviation:
Work packages that are loaded or published, containing tasks and faults
Skills/labor,
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 Mobile Maintenance for Aviation 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 Mobile Maintenance for Aviation 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 Mobile Maintenance Work Package Loader. See About Specifications for Load and Publish Work Package for details.
An AD Chain Cleanup Workscope Loader database task chain, predefined in the installation script, deletes transactions in the external file tables and records from intermediate processing tables. The database task chain is scheduled to run once a month, on the 1st day of every month, at 12 am. The period after which transactions for the external file tables must be deleted is predefined as 30 days. A system administrator can edit the database chain schedule and 30-day value with appropriate grants. Refer to the Mobile Maintenance for Aviation topic in IFS Cloud Technical Documentation for more information.