Are work packages automatically generated in 8.1 sp3 of Maintenix and what auto generates them??

Thanks for the great answer.  I have another related question.  We have customers with open work packages but all the tasks within it are completed and the work packages never get closed.  How is this happening?

Hi Lauri,

This is an indicator that the customer in question may not have a formal process for closing work package prior to the Release to Service. If their operations demanded a serviceable state before flight, then completing the work package would be mandatory by process. However, there is nothing in Maintenix that will interrupt your efforts to record flights or add usage to an aircraft while there is an open work package. This type of constraint may pose an operational risk. One constraint in this area is that the software will prevent you from starting a work package at a different location than the open work package.

Another potential option is the complete work package constraints. There are several configurable parameters that will present Warnings or Errors on work package closure using the Preview Release feature. It is possible that the customer aircraft are not meeting the maintenance release rules, and thus it would not be possible to complete the work package and bring the aircraft into service. Hopefully, this is not the case.

These are the rules, you may read more about them in the User Guide under the heading “Previewing releases”:

1. AOG or undeferred faults
2. Overdue tasks or faults
3. Near-due tasks or faults
4. Uncollected job cards
5. Missing mandatory components