Release package for execution

Select the package you wish to release for execution in the “Package Details” section.
Click the icon.

The package now proceeds for execution in the primary work center, if the mandatory information is available. However, when the required information such as primary work center or document category is not specified, the “Release Package” window appears prompting you to specify these details.

The multiline displays the following.

Aircraft Reg #	The aircraft on which the package will be executed.
Package #	The package that is executed on the aircraft.

Specify the following for the package.

Package Description	The short name/description of the package.
Doc Category	The category of the document Mandatory. The drop-down list displays all the values defined for Quick Codes Type "Exec. Ref # Category" in the Flight log that are in “Active” status business component. Load only quick codes which are in Active status.
Primary Work Center	Use the drop-down list box to select primary work center for the package Mandatory. The drop-down list displays those work centers with the Execution Capability other than “Shops Jobs”. However, the work centers thus defined in the Work Center component must be in the “Active” status.
Note: You cannot change the primary work center, if the package has already been allotted to a slot.
Exec. Station	The station in which the visit package is executed on the aircraft (Alphanumeric, 40). If a Station is mapped to the Work Center # in Work Center business component, then system will default the Station #. The execution station you specify must be in “Active status and must be mapped to the primary work center. Help facility available
Flight #	The flight subsequent to which the package must be executed on the aircraft (Alphanumeric, 25).
Customer order #	The customer order reference, if the aircraft is owned by a customer Mandatory (Alphanumeric, 25). Help facility available

Note: The Applicability of the customer order you specify must be “Aircraft.

Expense Type

Use the drop-down list box to select the expense type of the visit package. The drop-down list displays “Revenue’ and “Capital”.

CAPEX Proposal #

The CAPEX proposal number for the capital jobs to be executed in the package (Alphanumeric, 40).

The CAPEX proposal number is mandatory for a package, if the Expense Type is “Capital”.

Help facility available

User Status

Use the drop-down list box to select the user status for the package Mandatory.

For a package of type Hangar Visit Package, the drop-down list displays the quick codes defined under the quick code type “User Status” in the Flight Log component. If the type of the package is other than Hangar Visit Package, the drop-down list box displays the quick codes defined under the quick code type “Exe. Ref User Status” in the Flight Log component.

Select the “Release” pushbutton.

Note: The system does not allow the release of a package for a customer-owned aircraft, if the customer order for the package is not in “Processed” status.

The system releases the package for execution on the aircraft after the flight at the execution station; further performs the following.

Updates the status of the package and its constituent tasks to “Planned”.
A task that does not have a primary work center inherits the primary work center of the package to which it is allocated.
If the expense type of any task in the package is “Capital’, its CAPEX # is inherited by all the other tasks. The expense type of all the tasks in the package is set to “Capital” as well.
The details of successfully released line packages including the primary work center, execution station, expense type, customer order # (if the ownership of the aircraft is “Customer”) and the aircraft release date is updated in the AME component. Similar details of hangar work orders are updated in the Visit Package component.

Status: The status of the package and its constituent tasks become,

“Fresh”, if the package type is “Hangar Visit Package”.
“Planned”, if the package type is other than “Hangar Visit Package”.

Short closing material request for deferred discrepancy with log card reference

If process parameter “Auto Short close of Open Material Request" is set as ''On Release of Package" in the Common Masters component

On release of the package for execution, the system

Short closes authorized material requests previously generated for deferred discrepancy.
Generates new material requests for deferred discrepancies with the following attributes

MT Type = Planned
MR Class = Maintenance
MR Status = Authorized
Reference document = new package

Note: However, if work center is not specified for material requests, the system does not short close authorized material requests associated with the deferred task.