Create / release package for execution

Select the type of the package in the “Package Type” drop-down list box above the “Job details” Gantt chart.
Check the following boxes to assign / unassign tasks to the employee:

Assign	Check this box to assign tasks in the package, to the employee in the “Manage Work Assignments” page of the “Work Monitoring and Control” business component.
Release	Check this box to create and release the Package in one go. If 'Release' check box is checked which is above the Job details Gantt, Release check box in Create / Release Package screen will also be checked indicating the user that create and Release will happen simultaneously

Click the ‘Create Package’ icon in the “Job details” section or the ‘Release Package' icon in the “Package Details” section.

The “Create / Release Package” window appears.

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 “Create / Release Package” window appears prompting you to specify these details.

Note: The “Create / Release Package” screen will be launched for you to enter Work Center #, Customer # and Customer PO # when you select a Customer Owned A/C / task of a Customer Owned A/C with no work center or for which Customer Order needs to be auto-pegged.

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.

Note that the system displays this field only on selecting the “Create Package” icon.

Package Type

The type of the package, such as Heavy and OCM.

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 values on the basis of the type of packages selected for release. The drop-down list box displays, Those quick codes defined for Quick codes type "Exec. Ref # Category" with “Active” Status in the Flight Log business component, if the Package Type is “Hangar Visit Package”. Those visit categories defined in the "Compliance Tracking & Control" component with 'Active' Status, if the Package Type is other than “Hangar Visit Package”. Both of the above, if packages selected for release include line/AME as well as hangar visit packages. Note that the system displays this field only when 'Release' check box is selected.
Primary Work Center	Use the drop-down list box to select primary work center for the package Mandatory. The drop-down list box displays work centers on the basis of the type of the package. The drop-down list box lists, Work centers in “Active” Status with the Execution Capability set to “Hangar”, “Line”, or “All”. Work centers in “Active” Status with the Execution Capability not set to “Shops Jobs”,“Automatic Line Scheduling” and work center of class “Execution”, if type of the packages is other than “Hangar Visit Package”. Work Center of class “Execution” of the “Work Center” business component interacting with the “Compliance Tracking & Control” business component. Both of the above, if you have selected line/AME as well as hangar visit packages for release. For customer-owned aircraft and the package type selected, ensure that the work center selected in this field is the same as the Work Center provided in the Contract.
Note: You cannot change the primary work center, if the package has already been allotted to a slot.
Supplier #	The maintenance operating unit that will execute the package on the aircraft. You must enter valid supplier # in the Active status with Partner ID associated with a company that is a maintenance operating unit as defined in Supplier. Note: This field is mandatory, if The process parameter ‘External Jobs?’ for the package type of the package in the Define Process Parameters activity in Common Master is 1/Yes. The process parameter ‘Transfer of Aircraft Required?’ for the package type of the package in the Define Process Parameters activity in Common Master is 1/Yes. Help facility available
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

The system displays the following field in the “Package Details” multiline:

Customer #

The code identifying the customer for whom the customer order is created.

Note that the system displays Customer # for Customer Owned Aircraft.

The system displays the customer number of the customer owned A/C Reg # by default.

Enter the following fields in the “Package Details” multiline:

Customer PO #

The customer purchase order associated with order.

For customer-owned aircraft and package type for which the parameter “Auto Generation of Customer Order # on Creation of Package” is set as “Not Required” in the “Set Process Parameters” page in the “Define Process Entities” activity of the “Common Masters” business component, ensure the following:

Data entry in this field is mandatory if no value is entered in the Customer Order # field for
A Customer Order # must exist for the given Customer PO #.
The Customer PO # specified in this field must be valid for the given Customer Order #.

Note the following:

The system displays this field only on selecting the “Release Package” icon.
The system does not allow modification of Customer Order # given in this field.

Note: If for the given package type, the specified Customer PO # is not available for the Customer Order, then the system generates a customer order # if the parameter “Auto generation of Customer Order # on creation of package” is set as “Required” in the “Define Process Entities” activity of the “Common Masters” business component.

Flight #

The flight subsequent to which the package must be executed on the aircraft (Alphanumeric, 25). Note that the system displays this field only on selecting the “Create Package” icon.

Customer order #

The customer order reference, if the aircraft is owned by a customer Mandatory (Alphanumeric, 25). Data entry in this field is mandatory if no value is entered in the Customer PO # field for customer-owned aircraft and package type for which the parameter “Auto Generation of Customer Order # on Creation of Package” is set as “Not Required” in the “Set Process Parameters” page in the “Define Process Entities” activity of the “Common Masters” business component.

Ensure the following:

The customer order number entered in this field is a valid number that exists in the Customer Order business component in “Approved” status and the Order Applicability is “Aircraft”.
The Contract # and Revision # referred in the Customer Order is same in the Package.

Note that the system does not allow modification of Customer Order # given in this field.

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.

The system displays the following field in the “Package Details” multiline:

Estimation Status	The estimation status of the package.
Hold Status	The hold status of the package which could be either “On Hold” or blank.

Check the following box:

Release for Execution

Check this check box if you wish to release the package for execution. This check box appears only if the “Release” check box in the “Review Fleet Maintenance Plan” page is checked.

Select the “Create Package” pushbutton to create package.

The system performs the following:

Generates a customer order for a given package type in “Processed” status if the process parameter “Autogeneration of Customer Order # on creation of Package” is set as “Required” in the “Define Process Entities” activity of the “Common Masters’ business component.
Retrieves the Customer Order # in “Approved Status” if for the given package type for customer owned Aircraft, the process parameter “Autogeneration of Customer Order # on creation of package” is set as “Not Required” in the “Define Process Entities” activity of the “Common Masters” business component.
Updates the status of the retrieved customer order to “Processed", once Package is created against that Customer Order #.
Updates the current server date as the “Package Start Date” and calculates the Package End Date as package created date + 1 hour for packages created without any tasks or discrepancies.
Launches the “Create Package” page for you to enter Work Center #, Customer #, Customer PO # when a customer-owned aircraft or a task of a customer owned aircraft which does not have a work center is selected.
For Line Planning, if ‘Release for Execution’ check box is checked, the system creates and releases package simultaneously based on the Hold Status of the package, as follows.

If Hold Status of the package is not specified, the system allows release of package and changes Task Status to “Planned”.
If Hold status is “On Hold” and if the process parameter 'Prevent Task Status Change?' is set as 'Yes' for Hold code on which the package is put on hold, the system creates package, but does not allow package release and task status change.
If Hold Status is “On Hold” and if the parameter 'Stop A/C Maint. Execution?' is set as 'Yes', for the Hold code on which the package is put on hold, package is created and not released for execution.
If the package is on hold, with Hold code property 'Prevent Material Request?' set as “Yes”, the system releases the package without generating Material Requests, even though 'Auto Generation of MR' is set as "Required" for a Package type.

For Line Planning, if ‘Release for Execution’ check box is checked, the system creates and releases package simultaneously, if one of the following conditions is true:

if Contract for the Package # is in 'Firm' stage, Release of Package is allowed. If the Contract stage is 'Bid / Prospect', Package creation alone happens.
if Primary Work Center # is specified.
if Doc. Category is specified.
if Expense Type is selected as “Capital” and Capex Proposal # is specified.

On clicking the “Create Package” icon in the main page, the system performs the following based on the checked / unchecked state of the ‘Release’ and ‘Assign’ check boxes.

‘Release’ check box	‘Assign’ check box	The system performs the following:
Checked	Checked	Creates and Releases package simultaneously in the “Review Fleet Maintenance” page. Updates status of package and its tasks as “Planned”. Invokes “Manage Work Assignments and Reporting” screen of “Work Monitoring & Control” business component, with all the tasks in the Package. For internal aircraft, if ‘Document Category’ / ‘Primary Work Center’ / ‘Capex Proposal #’ (for task with Expense Type as “Capital”) is not available, the system launches the “Create / Release Package” screen. For Customer Owned A/C, if the process parameter if the 'Auto Generation of Customer Order # on Creation of Package' is 'Required' and workcenter is set as mandatory in the Customer Order’s contract, the system launches the “Create / Release Package” screen. For Customer Owned A/C, if the process parameter if the 'Auto Generation of Customer Order # on Creation of Package' is 'Not Required' ,the system launches the “Create / Release Package” screen for the user to provide Customer Order # / Customer PO for Package creation.
Unchecked	Unchecked	For Customer Owned A/C, if the process parameter if the 'Auto Generation of Customer Order # on Creation of Package' is 'Required' and workcenter is set as mandatory in the Customer Order’s contract, the system launches the “Create / Release Package” screen. For Customer Owned A/C, if the process parameter if the 'Auto Generation of Customer Order # on Creation of Package' is 'Not Required', the system launches the “Create / Release Package” screen for the user to provide Customer Order # / Customer PO for Package creation. Creates package. Updates status of package and its tasks as “Fresh”. Does not invoke “Manage Work Assignments and Reporting” screen.
Checked	Unchecked	Creates and Releases package simultaneously in the “Review Fleet Maintenance” page. Updates status of package and its tasks as “Planned”. Does not invoke “Manage Work Assignments and Reporting” screen. For internal aircraft, if ‘Document Category’ / ‘Primary Work Center’ / ‘Capex Proposal #’ (for task with Expense Type as “Capital”) is not available, the system launches the “Create / Release Package” screen. For Customer Owned A/C, if the process parameter if the 'Auto Generation of Customer Order # on Creation of Package' is 'Required' and workcenter is set as mandatory in the Customer Order’s contract, the system launches the “Create / Release Package” screen. For Customer Owned A/C, if the process parameter if the 'Auto Generation of Customer Order # on Creation of Package' is 'Not Required' ,the system launches the “Create / Release Package” screen for the user to provide Customer Order # / Customer PO for Package creation.
Unchecked	Checked	Creates package. Updates status of package and its tasks as “Fresh”. Does not invoke “Manage Work Assignments and Reporting” screen. For Customer Owned A/C, if the process parameter if the 'Auto Generation of Customer Order # on Creation of Package' is 'Required' and workcenter is set as mandatory in the Customer Order’s contract, the system launches the “Create / Release Package” screen. For Customer Owned A/C, if the process parameter if the 'Auto Generation of Customer Order # on Creation of Package' is 'Not Required' ,the system launches the “Create / Release Package” screen for the user to provide Customer Order # / Customer PO for Package creation.

Creates an AME package in “Fresh” status, based on the Package Type selected, and updates the relevant task details.
Updates the part requirements and resource requirements for each task to the AME package, from the “Maintenance Task” business component.
For each task, the Access Panel identified in the “Maintenance Task” business component, is updated to the AME package. For each identified Access panel, system also updates the corresponding open & close access panel tasks.
Updates the Schedule Relationships existing for each task to the AME package, from the “Maintenance Task” business component.
Transferred aircraft:

You cannot create a package for an aircraft that has been transferred to another operating unit for maintenance. The system allows for package creation upon return of the aircraft.

Package creation on selecting tasks / combination of tasks:

On selecting a single task / multiple tasks / combination of tasks and if Package Type is not selected in the “Review Fleet Maintenance Plan” page, on clicking the “Create Package” pushbutton, the system creates a package as shown in the table below:

Task Selection	Package Creation
Only one task is selected	The system creates a package with Package Type available for that task in the respective Maintenance Program.
If multiple tasks of the same ‘Program Item Type’ are selected	The system checks if the Package Type is available for all the tasks, is same in the respective Maintenance Program, and creates a package with this 'Package Type'.
If a Block Task and one or more tasks whose ‘Program Item Type’ is other than Block is selected	Creates a package with Package Type available for the Block Task in the respective Maintenance Program.
If multiple Block Tasks and one or more tasks whose Program Item Type is other than “Block” is selected	The system checks if the Package Type is available for all the selected Block Tasks, is same in the respective Maintenance Program, and creates a package with this 'Package Type'.
If tasks of different ‘Program Item Type’ other than “Block” are selected	The system checks if the Package Type is same for all the tasks. If ‘Yes’, the systems creates a package with this Package Type.

Conditions for creating a package to be executed by another operating unit

· In the Define Process Entities activity of Common Master;

o The process parameter "Transfer of Aircraft Required?" for the package type of AME Ref. # is 1

o The process parameter "Default Package Type in the Target Unit" is defined for the package type.

· The ownership type of the aircraft must be 'Owned'

· In the "Setup Operating Units for Data Replication" activity of Central Data Replication Configurator in the Target operating unit;

o The customer # - partner ID - Source operating unit mapping exists.

o The contract # - customer # - partner ID - Source operating unit mapping exists.

The contract # is effective (All effectivity / Model effectivity) to the aircraft.
The system sets Need Date of the material request on the basis of the AME Ref. # referenced task as illustrated in the table

If Plan Start Date of the task/discrepancy is a	Need Date of the MR will be set as
Current/Future date	Plan Start Date of the task/discrepancy
Past date	System Current date

In a situation in which multiple material requests are auto-generated by the system, the requests are consolidated on the basis of Need Date or the serviceable request warehouse of the task work center.

Select the “Release” pushbutton.

Note: This pushbutton appears only if this screen is invoked by clicking the ‘Release Package’ icon .

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” if the package selected for release is in “Draft” status.
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”.

The system holds the status of a package when it is selected for release, If for the given Package Type, the process parameter “Auto MR Generation on Package Release” is set as “Yes” in the “Define Process Entities” activity of the “Common Masters” business component.

Note: If the package which is on hold has hold code property “Prevent Material Request?” set as “Yes” in the ”Define Process Entities” activity of the “Common Masters” business component, then the system releases the package without generating material requests.

Task Status Change:

On release of the package, the system updates the status of the task to “Planned” if the hold status is blank.
On release of the package, the system does not allow release of the package or change of the status of the task if the “Hold Status” is “On Hold” and if the process parameter “Prevent Task Status Change?” set as “Yes” in the ”Define Process Entities” activity of the “Common Masters” business component.

Aircraft Maintenance Execution:

On release of the package, the system updates the status of the task to “Planned” if the hold status is blank.
On release of the package, the system does not allow release of the package or change of the status of the task if the “Hold Status” is “On Hold” and if the process parameter ““Stop A/C Maint. Execution?” set as “Yes” in the”Define Process Entities” activity of the “Common Masters” business component.

Material Request:

On release of the package, the system holds the status of the package if for that Package type the parameter, “Auto MR Generation on Package Release” is set as ”Yes” in “Define Process Entities” activity of the “Common Masters” business component.
On release of the package, the system releases the package without generating a material request if the package is on hold with hold code “Prevent Material Request?” set as “Yes” in the”Define Process Entities” activity of the “Common Masters” business component.
The system even allows creation of material requests for parts with Planning Status as ‘Inactive’. This is to facilitate releasing of packages those associated with Inactive parts to aid seamless maintenance planning.
Restricting Off Wing tasks in packages: You can add tasks with job type ‘Off Wing’ to a package, if the process parameter ‘Allow Off Wing Jobs?' under entity type ‘Package Type’ and entity User-Defined Packages or Log Cards in the Define Process Entities activity in Common Master is 1/Yes for the package type. However, the system does not allow for Off Wing tasks in a package, if ‘Allow Off Wing Jobs?' is 0/No.
The system sets Need Date of the material request on the basis of the AME Ref. # referenced task as illustrated in the table

If Plan Start Date of the task/discrepancy is a	Need Date of the MR will be set as
Current/Future date	Plan Start Date of the task/discrepancy
Past date	System Current date

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.