Publish Work Package

Explanation

In CAMO, select Publish Work Package to send the assigned tasks and faults to execution for aircraft maintenance. Where the work package is published depends on its type:

• A line work package is published to Line Maintenance Execution.
• A hangar (heavy) work package is published to Hangar Maintenance Execution.

Line maintenance

When the aircraft has a matching aircraft turn, the work package connects to that turn and appears on the Aircraft Turn Details page.

When the aircraft has no inbound or outbound flight, a line work package can still publish successfully—they appear on the No Turn Work Packages page.

Reschedule and republish

When a line planner reschedules a work package in CAMO to a different aircraft turn at the same airport, such as a new maintenance time or location, and then publishes the work package, the system associates it with the matching aircraft turn. After the work package is published successfully, it appears on the new turn in Line Maintenance Execution instead of the previous turn.

For schedule and reschedule rules, see Schedule Work Package.

Hangar maintenance

A hangar (heavy) work package is published to Hangar Maintenance Execution. It is not linked to an aircraft turn. Before you can publish a hangar work package, its workscope must be committed; a hangar work package cannot be published while it is only in the Active status. To commit the workscope, see Commit Work Package. To schedule a hangar work package to a hangar location or an external repair vendor, see Schedule Work Package (Hangar Maintenance).

After you publish a hangar work package, review the result on the Hangar Maintenance Work Package Publish Log page. See Hangar Maintenance Work Package Publish Log.

Update a published work package

Publish a work package after you remove items in CAMO to update it in Maintenance Execution. You can remove:

• Tasks, faults, and work types from the work package
• Parts, tools, actions, measurement, steps, and skills defined on tasks and faults

Publish timestamps

Publishing sets a timestamp on the work package. If multiple publish messages are queued for a work package, the system processes the update with the later timestamp.

Auto-reservation timing

If you publish from CAMO before auto-reservation of parts is complete, installed part information isn't available in Line Maintenance Execution. Republish the work package after auto-reservation completes to make installed part information available. See Auto Reservation of Tools / KITs / Parts.

Prerequisites

• To publish the work package from CAMO to Maintenance Execution:
  • The work scope must be generated
  • The work package must be scheduled
  • A line work package can be published when it is in the Active or Committed status. A hangar (heavy) work package must be in the Committed status before it can be published. See Commit Work Package.
  • Your system administrator must have the ACTION_PUBLISH_WORK_PACKAGE permission setting in CAMO.
• The MaintenixConnected property must be set to TRUE on the Apps-Mtx Config page in IFS Cloud Web.
• To create or update a work package and its contents successfully by publishing from CAMO:
• Basic data corresponding to the data for the work package and its contents must be set up in Maintenance Execution to avoid the work package publish failing due to invalid data.

• Make sure that the equipment baseline is aligned with line and hangar maintenance. That alignment ensures that tools, parts, and measurements transferred correctly with the work package.

System Effects

• For a hangar (heavy) work package, the work package is published to Hangar Maintenance Execution. Review the publish result on the Hangar Maintenance Work Package Publish Log page, where the status is Completed, Failed, or Error. See Hangar Maintenance Work Package Publish Log. The remaining effects below describe line maintenance.
• An event is received on the Communication Log page which can then be monitored to see the status of the work package publish in Line Maintenance Execution. For more information see About Communication Monitoring.
• If the work package publish was successful, on the Line Maintenance Work Package Loader page:
  • The status of the file is Completed.
  • The execution status of the rows in the tabs is Successful.
  • When a matching aircraft turn exists, the work package is displayed connected to that turn on the Aircraft Turn Details page.
  • Tasks and faults assigned to the work package are displayed with the work tasks for the work package.
  • If the work package was rescheduled to another aircraft turn before publish, it appears on that turn after a successful publish—not on the earlier turn.
• Work types can be seen specified on a turn on the Turn Work Assignments page.
• Part removal and part installation, tool usage, measurement, actions and steps can be seen on the Task Details and Fault Details pages, as applicable.
• If the publish failed:
  • If your system administrator set up to notify you when the work package publishing fails, the notification panel will contain a notification. When you select the notification for the error, you are directed to the Line Maintenance Work Package Loader page which indicates the cause of failure of the work package.
  • On the Line Maintenance Work Package Loader page:
    • The execution status in the Execution Summary section is set to Failed.
    • Work packages and their contents are not created or updated. Details of the failed rows can be viewed on the Line Maintenance Work Package Loader page by expanding the row with the Failed execution status. Note that to view all the columns for a row you must set the view to Table View for the tab. 
• Transactions associated with the published file can be viewed on the External File Transactions page by selecting External File Log.

Procedure

1. On the Work Package Details page in CAMO, select Publish Work Package.
2. To verify if the work package publish succeeded or failed, in IFS Cloud Web, open the Line Maintenance Work Package Loader page for a line work package, or the Hangar Maintenance Work Package Publish Log page for a hangar work package.
3. Depending on the execution status of the file, you must take actions as follows:
   1. Completed—Processing succeeded. You can view the created or updated work packages, tasks, and faults.
   2. Failed—Processing failed because of work package publishing errors. See Review Errors.
   3. Error—An unexpected error occurred. Publish the work package again.