Updating line package details

This page allows you to retrieve the information of all the work units that are pending against an aircraft registration number and associate selected or all pending work units to a line package, to perform line maintenance activity on the flight.

Select the “Line Package Details” tab in the “Plan Gate Maintenance” page.

The “Line Package Details” page appears.

Enter the following fields in the “Gate Details” group box:

Gate #

Use the drop-down list box to specify the gate for which maintenance activities are to be planned. The system lists all the gates for the selected terminal and station combination. The system also lists an additional option “Unassigned” to indicate the gates that are not assigned to any of the flights. By default, the system displays the first gate defined for the selected terminal and station combination.

Plan Date

The date for which the flight schedule is planned (Date Format). Mandatory. By default, the system displays the current system date.

The system displays the following fields in the “Flight Information” group box:

Note: The system retrieves the details of the first flight that is scheduled for the date specified in the “Plan Date” field.

A You can use and buttons to retrieve the information of the first and the last flights for the plan date.

A You can use and buttons to retrieve the information of the preceding and succeeding flights for the plan date.

Flight #	The number identifying the first flight that is scheduled for the date specified in the “Plan Date” field.
Flight Type	The flight type, which could be “Arrival” or “Departure”.
Aircraft Reg #	The aircraft registration number of the flight under consideration.
Sch. Date & Time	The date and time for which the flight is scheduled.
Stopover Time	The time period between the expected arrival time and the expected departure time of the aircraft. The stopover time represents the time for which the aircraft is available in the station.

Note: Stopover time is computed as the difference between the actual date/ time of arrival and the date/time at which the same aircraft is scheduled for its next flight from the station.

Act. Date & Time	The actual arrival and departure time of the flight in the gate.
Journey Log #	The journey log number associated to the flight.
Delayed by (Hrs)	The time period for which the flight is delayed.

Note: If the flight type is “Arrival”, “Delayed by (Hrs)” is calculated as Actual Arrival Date & Time – Sch. Arrival Date & Time.

If the flight type is “Departure”, “Delayed by (Hrs)” is calculated as Actual Departure Date & Time – Sch. Departure Date & Time.

Tech Log #

The technical log number associated to the flight.

The system displays the following fields in the “Pending Jobs Summary” group box:

Pending Planned Jobs

The number of pending planned jobs that are available against the selected aircraft, in the central planning pending tray.

The pending planned jobs from the central planning pending tray include the following work units:

i. Pending work units with schedule date earlier than or equal to the current system date, with no associated plan dates.

ii. Pending work units with schedule date earlier than or equal to the current system date.

iii. Allocated work units with line package reference and no technical log reference and with schedule date earlier than the latest technical log date in “Fresh” or “Confirmed” status.

Pending Discrepancies	The pending discrepancies recorded against the aircraft, or the maintenance reports created against the aircraft with record status as “Pending” or “Deferred”. The system considers the discrepancies which are in "Fresh", "Pending", "Under Resolution" and "Retired" statuses associated to the Aircraft Reg. # as pending discrepancies.
Incomplete Jobs	The pending work units against the aircraft with “Incomplete (Y/N)” marked as “Yes” and available in the central planning pending tray.

Click the “Get Pending Jobs” pushbutton to retrieve the details of the pending jobs in the “Work Unit Details” multiline.

Note: If a line package exists, the system retrieves only those work units that are part of the line package, in the “Work Unit Details” multiline. Otherwise, the system retrieves all the work units that are pending for the aircraft.

Enter the following field in the “Line Package Comments” group box:

Comments

Any general information pertaining to the line package for the selected plan date, flight, leg and status (Alphanumeric, 2000).

On launch of the page, the system displays the comments of the line package if available.

Enter the following fields in the “Work Unit Details” multiline:

Note: If a line package already exists for the given plan date, flight, leg and station number, the system retrieves the work units that are available in the line package.

On clicking the “Get Pending Jobs” pushbutton, the system retrieves work units with job type as “Aircraft”, “On-wing”, and restoration work units with job type as “Component Replacement” from the central planning pending tray and component planning pending tray, in the multiline.

The pending work units include:

Pending work units with schedule date earlier than or equal to the current system date, with no associated plan dates.

Note: If the option “Auto Inclusion of Jobs based Alert Date / Value” is set as “Line Planning” or “Technical Log & Gate Maintenance” in the “Compliance Tracking & Control” business component, the system considers the alert date instead of the schedule date.

Pending work units with schedule date earlier than or equal to the current system date.
Allocated work units with line package reference and no technical log reference and with schedule date earlier than the latest technical log date in “Fresh” or “Confirmed” status.

Note: The pending work units also include work units that are part of “Start Maintenance Event” or “End Maintenance Event” for the flight number and leg number combination. If the flight type is “Arrival”, the system retrieves end maintenance type work units. If the flight type is “Departure”, the system retrieves start maintenance type work units.

Work Unit Type	Use the drop-down list box to specify the type of work unit to be performed on the aircraft. The system lists the options “Task”, “Standard Procedure”, “Aircraft Work Package”, “Component Work Package” and “New Task”. By default, the system sets this field to “Task”.
Work Unit #	The number identifying the work unit to be performed on the aircraft (Alphanumeric, 30). Mandatory.

Note: If no line package exists for the given plan date, flight number, leg number and station, the system ensures that the work unit number is a valid work unit defined for the given aircraft registration number, in the “Maintenance Task”, “Aircraft Maintenance Program” or “Component Maintenance Program” business components. Also, the system ensures that the status of the work unit is not "Allocated" in the central planning pending tray.

The system performs the above check when new work units are added to an existing line package, as well.

Work Unit Desc

The textual description of the work unit (Alphanumeric, 150). Data entry in this field is mandatory if you have set the “Work Unit Type” as “New Task”.

The system displays the following fields:

Discrepancy / MR #	The number identifying the discrepancy or maintenance report recorded for the component.
Discrepancy / MR Description	The textual description of the discrepancy or the maintenance report.
Discrepancy / MR Status	The processing status of the discrepancy or the maintenance report.
Schedule Date	The date on which the execution of the work unit is scheduled.
Alert Date	The date on which the alert is raised for the execution of the work unit.
Rem. Days	The number of days remaining, before the forecasted arising of the pending work units.
Rem. FH	The number of flying hours remaining, before the maintenance activity is over due.
Rem. FC	The number of flying cycles remaining, before the maintenance activity is over due.

Enter the following fields:

Job Type	Use the drop-down list box to specify the job type of the work unit. The system lists the options “Aircraft”, “On-Wing” and “Off-Wing”. By default, the system sets this field to “Aircraft”.
Maintenance Type	Use the drop-down list box to specify the maintenance type of the work unit. The system lists the options “Overhaul”, “Inspection”, “Repair” and “Others”. By default, the system sets this field to “Overhaul”.

The system displays the following field:

Source

The source of the work unit, which could be one of the following:

Aircraft Forecast – If the work unit is derived from aircraft forecast.
Component Forecast – If the work unit is derived from component forecast.
Maintenance Event – If the work unit is derived from start maintenance event or end maintenance event for the selected flight.
EO Work Unit – If the work unit is derived from engineering order.
FCD Work Unit – If the work unit is derived from FCD.
Component Removal – If the work unit is derived from component removals.
As Required – If there are no schedules associated to the work unit.
Pending Discrepancies – If work units are derived from discrepancies.

Enter the following fields:

Est. Elapsed time	The time estimated for work unit completion (Time Format). Data entry in this field is mandatory, if you have set the “Work Unit Type” as “New Task”.
Time Unit	Use the drop-down list box to specify the time unit. The system lists the options “Days”, “Hours” and “Minutes”. By default, the system sets the field to “Hours”.
Part #	The part number for which pending work units have to be retrieved (Alphanumeric, 40). The part number must be defined in the “Part Administration” business component and must be valid for the component.
Serial #	The serial number of the component for which the pending work units have to be retrieved (Alphanumeric, 40). The serial number must be valid for the specified part.
Component #	The number identifying the component for which pending work unit details have to be retrieved (Alphanumeric, 40). The component number must be defined in the “Aircraft” business component. Data entry in this field is mandatory, if job type is “Component” or “Engine” and if “Part #” and “Serial #” fields are not entered.

Note: Ensure that the part number and serial number are compatible with the component number.

The system displays the following field:

EO # / FCD #

The number identifying the engineering order or a fleet campaign directive in which work units are defined.

Enter the following information:

Planning Comments

The comments pertaining to the planning of the execution of work units as available in the “Compliance Tracking & Control” business component (Alphanumeric, 255).

Note: Ensure that at least one record exists in the multiline.

To proceed, carry out the following

Select the “Identify Resolution Procedure” link to identify the resolution procedure that must be executed for the discrepancy or maintenance report.

Refer to the “Discrepancy Processing” online help for more details.

Select the “View Work Unit Dates & References” link to view the work unit details.

Refer to the “Compliance Tracking & Control” online help for more details.

Select the “Plan Material” link to plan material for execution of the visit package
Select the “View Task” link to view the task information details.
Select the “View Standard Procedure” link to view the standard procedure details.
Select the “View Component Work Package” link to view the work package details.
Select the “View Aircraft Work Package” link to view the aircraft work package details.
Select the “View Task Card” link at the bottom of the page to view the task card created in the third party application.

Refer to the “Task Card Publisher” Online help for more details.

Select the “View AMM Reference” link at the bottom of the page, to view the details of aircraft maintenance manual for the task.
Click the “Update Line Package” pushbutton to update the line package details.

Note: If a technical log exists for the plan date, flight number, leg number and station number, the system ensures that the technical log is not in “Confirmed” status.

If there is no line package, the system generates a line package number for the given plan date, flight number, leg number and station number.

The system performs the following:

Updates the job status of the work units to “Allocated” in the respective pending trays depending on the job type.
If there is a technical log in “Fresh” status for the given plan date, flight number, leg number and station number, the system moves all the work units selected for the line package, to the corresponding technical log. Also, the system updates the “Tech. Log #” of the corresponding work units in the component planning and central planning pending tray.
Copies the part requirements identified for each work unit, into the technical log.
Updates the material request if generated for the work units, into the technical log.
Updates the record status of the discrepancies to “Under Resolution” and updates the technical log number as “Resolution Document #’ in the “Discrepancy Processing” business component.
Generates a non-routine task if the “Work Unit Type” is “New Task”.
Displays the default resource group for the non standard task, based on the values set in the "Set Options" page of the "Maintenance Task" business component. For example, if the default value is selected as "Mechanic" in the "Set Options" page, the system displays "Mechanic" by default for the non standard task.
Updates the "Task Master" and the current business component.
Associates the work group number assigned for the gate number and flight date to the created line package, and updates the assignment type of all the employees to “Work Group”. Also, the system updates the earliest schedule or planned date of the work unit as “From Date” and latest schedule or planned date of the work unit as “To Date”.

Creating technical log

Click the “Create Technical Log” pushbutton to create the technical log.

Note: Ensure that a line package is defined for the given plan date, flight number, leg number and station number. Also ensure than a technical log, in “Fresh” or “Confirmed” status does not exist for the line package.

The system performs the following:

If a technical log in “Fresh” status exists for the given plan date, flight number, leg number and station number, the system moves all the work units selected for the line package, to the corresponding technical log. Also, the system updates the “Tech. Log #” of the corresponding work units in the component planning and central planning pending tray.
Copies the part requirements identified for each work unit, into the technical log.
Updates the material request if generated for the work units, into the technical log.
Updates the record status of the discrepancies to “Under Resolution” and updates the technical log number as “Resolution Document #’ in the “Discrepancy Processing” business component.

Canceling line package

Click the “Cancel Line Package” pushbutton to cancel the line package.

Note: Ensure that a technical log does not exist for the given plan date, flight number, leg number and station number.

The system performs the following:

Removes the line package created against the given plan date, flight number, leg number and station number, and also removes the work group associated to the line package.
Updates the job status of the work units to “Pending” in the respective pending trays, depending on the job type.
Updates the record status of the discrepancies / MRs to “Pending” in the “Discrepancy Processing” business component.

To record discrepancies

Select the “Record Discrepancies” link to record discrepancies associated to the aircraft.

To perform opportunity maintenance

Select the “Perform Opportunity Maintenance” link to execute work units on the aircraft as opportunity maintenance work units.

Refer to the “Compliance Tracking & Control” online help for more information.

To assign work group/employees

Select the “Assign Work Group / Employee (s)” link to assign work group or employees to gates at work unit level or line package level.

Reassigning work units or line package

Enter the following fields in the “Re-Assign To” group box:

Note: Ensure that a line package is defined for the given plan date, flight number, leg number and station number.

Update Option	Use the drop-down list box to specify the option for reassigning selected work units or complete line package to another flight date, flight number and leg number. The system lists the following options: “Complete Line Package” – Select this option if you wish to reassign the complete line package. “Selected Work Units” – Select this option if you wish to reassign the work units selected in the “Work Unit Details” multiline. Data selection in this field is mandatory. The system leaves this field blank by default.
Flight Date	The date for which the flight is scheduled (Date Format). Mandatory.
Flight #	The number identifying the flight against which the work units must be executed (Alphanumeric, 30). Mandatory.
Leg #	The number identifying the leg during which the work units must be executed (Integer). Mandatory.

Note: Ensure that the “Flight Date”, “Flight #” and “Leg #” are not the same as the plan date, flight number and leg number specified in the header. Also, no technical log must exist in “Fresh” or “Confirmed” status for the line package defined for the flight date, flight number and leg number specified above.

Note: Ensure that the “Aircraft Reg #” available in the “Flight Information” group box for the given flight, is the same as the aircraft registration number scheduled in the aircraft routing for the given flight date, flight number and leg number.

Select the work units to be reassigned in the “Work Unit Details” multiline, if you have set the “Update Option” as “Selected Work Units”.
Click the “Reassign Work” pushbutton, to reassign the execution of the selected work units or the complete line package, based on the selected update option.

The system performs the following:

Reassigns the selected work units or all work units of the line package, to the line package existing for the given flight date, flight and leg number.

Note: If a line package does not exist for the given flight date, flight, leg and station, the system creates a new line package and associates the work units to the line package.

Updates the line package associated with the work units, in the component and aircraft pending trays.
Removes the line package created against the given plan date, flight, leg and station.

To proceed, carry out the following

Select the “Update Routing Plan” tab if you wish to update routing plan for different flight number and leg number combinations.
Select the “Assign Work Group to Gate” tab if you wish to assign work group to the gate for executing line maintenance.