Work packages
For scheduling, tracking, and organizing purposes, work packages group tasks that are executed during maintenance visits. Work packages can contain only one task or hundreds. They are created automatically in various workflows, manually by planners, MOC, and others, or can be loaded into Maintenix using dataloading tools.
You can create an empty work package for an aircraft or component and then add tasks and faults to it, or you can select tasks or faults for an aircraft or component, and create the work package to include those tasks or faults.
You can continue to add tasks and faults to a work package after it has been created.
- For any type of maintenance—line, heavy, or shop—you can create work packages manually from several to-do lists and details pages in Maintenix.
- For line maintenance, you can create turn work packages and service work packages to create turn checks and service checks. Depending on how your baseline is set up, creating turn and service check work packages is a partially automatic process.
- For shop maintenance tasks that must be performed on a component by a specific due date, Maintenix creates work packages automatically when the tasks to be executed are created.
- When an unserviceable component is removed from the parent inventory; for example, when an engine or a tracked part is removed from an aircraft, Maintenix automatically creates a work package.
- For heavy maintenance, the Long Range Planner (LRP) application creates work packages automatically.
After work packages are created, a variety of roles take the next steps in the process and manage the work package to completion. Steps in the process include:
Adding unassigned tasks and faults to the work package
The Assigned Tasks tab for the work package shows all the tasks that are assigned to the work package. Job cards are displayed under their parent requirements. Production planners review the Unassigned tab to see if there are other ACTV tasks or faults that can or should be brought into the work package. Using the View Opportunistic Tasks button, you can also view tasks are opportunistically linked with tasks in the work package and if you have the resources to do the work, you can assign the tasks to the work package.
Generating the workscope
The workscope is the collection of executable tasks that make up a work package - executable requirements, job cards, ad hoc tasks, and faults. At any time while you are packaging tasks, you can generate the workscope to see a list of all the executable tasks in the work package. Generating the workscope adds the Workscope tab to the Work Package Details page. The Workscope tab lists all executable tasks as numbered line items. Note that if a requirement has job cards, you don't see the requirement on this tab, only it's job card sub-tasks.
Generating the workscope also generates the open and close job cards for aircraft panels (if your organization uses master panel card task definitions), and suppresses duplicate job cards from the workscope. The workscope does include duplicate job cards if the same job card definition is assigned to two different requirements included in the workscope. You can make further adjustments to the workscope as needed, clear the workscope, and regenerate it as many times as you need before you commit the workscope.
Scheduling the work package
You can schedule a work package as soon as it's created.
When you schedule or reschedule a work package, you set the start date, end date, and the location where the work will be done. You can schedule a work package initially with just the start and end dates and add the location later.
Before you can commit the workscope or start a work package, the work package must be scheduled - including start date, end date, and location.
After a work package is scheduled, a Work Package Number is generated.
Committing the workscope
After the workscope of a work package is defined, you commit the workscope. Committing the workscope does the following:
- Runs auto-reservation to fulfill open part requests. Part requests that are not fulfilled using auto-reservation appear on the material controller's (or warehouse manager's) to-do list.
- Aircraft work packages that were created in Long Range Planner (LRP) are no longer controlled by LRP. Workscope and scheduling changes are now made in Maintenix.
- Updates the location of tasks in the work package either to the same location as the work package or if it's a component work package, updates task locations to ones that are assigned the capability to perform the task work type.
Any time after the workscope is committed, you can generate the tally sheet - this is usually done when the work package is complete, but can also be done periodically to monitor progress.
If a work package isn't started, you can click the Uncommit Scope button to undo the commit operation. Undoing the commit operation removes the date and location from part requests, and cancels any part reservation created manually or automatically.
Modifying the workscope after the commit point affects material reservation and can result in a shortage of resources such as skilled labor and tools. You might also need to revise the end date for the work package.
If you do change the workscope after a work package is committed, rows of added tasks are visually separated from the tasks agreed to in the workscope by a line across the table on the Work Package Details. Tasks, such as faults, that are added after the work package is committed, are displayed below the line.
Starting work package
Starting a work package starts the maintenance visit. When a work package is started, its status changes to In Work, and tasks and faults within the work package can be started.
You don't start component work packages that are scheduled to external repair vendors; they are started automatically when the inventory is shipped to the repair vendor.
As work progresses, you can preview the release for a summary of potential issues that might prevent closure of the work package (and release to service if it's an aircraft work package).
Completion
When all the work has been performed — there are no more IN WORK labor rows on completed tasks, tasks and faults are completed or deferred, mandatory components are installed, and job cards are collected (if required)—production controllers can generate a tally sheet in preparation for reviewing and completing a work package.
Previewing the release is part of the work package completion process in which you resolve errors and warnings such as overdue tasks, missing mandatory components, or incomplete labor or part requirements.
An assembly is complete when all of its mandatory, applicable components are installed. On the Inventory Details page, Sub Inventory tab of an aircraft, if an aircraft is complete, you see a check mark in the Complete column. If there's no check mark, you can expand the list to see what's missing.
A background job evaluates aircraft completeness, but if there are no missing mandatory parts yet the aircraft is not complete, you can manually trigger the evaluation by clicking the Evaluate Completeness button (permission required for the button is ACTION_EVALUATE_COMPLETENESS).
Maintenix can be configured to allow work package completion when there are missing components.