Editing Execution Ref # information

This page allows you to edit technical log information. Tell me more.

• Select the “Edit Technical Log” link in the “Select Technical Log” page. Alternatively, click the hyperlinked technical log number in the multiline of the same page.

The “Edit Technical Log” page appears.

The system displays the following field:

The system displays the following in the “Tech Log Details” group box:

• Enter the following information:

Note: The technical log category cannot be modified, after the technical log is created.

Note: The “Operations Type” cannot be modified after the “Edit Log” pushbutton is clicked.

The system displays the following field:

• Select the hyperlinked aircraft registration number to view the aircraft record.

• Enter the following field:

Note: The “Tech Log Date and Time” must be later than or equal to the date and time entered in the “Gate-in Date & Time” field. The system displays the current server date and time by default.

Note: The “Tech Log Date & Time” must be later than the operational date and time of the aircraft.

Note: Ensure that “Tech Log Date & Time” does not fall in the range of the closed reliability period for the reliability fleet to which the aircraft is associated.

The system displays the following field:

• Enter the following fields:

• Click the “Get Details” pushbutton to retrieve details pertaining to the journey log number entered.

Note: If the execution status of any of the work units for this technical log number is pending, they are updated in the “Record Work & Sign-off Information” page.

The system displays the following in the “Execution Details” group box:

• Select the hyperlinked work center number to view work center information.

• Enter the following:

The system displays the following field:

The system displays the following field:

• Enter the following fields in the “Journey Log Details” group box:

Note: The journey log number or aircraft registration number must be entered for the “Tech. Log Basis”  other than “Non Journey Log”.

Note: The journey log number, flight and leg numbers and line number cannot be modified or deleted, if action has been recorded against the pilot reported discrepancies associated to the technical log through the journey log.   

If no action is taken against the pilot-reported discrepancies, the journey log number, flight and leg numbers and line number can be modified, deleted or no longer associated to the technical log. The status of such discrepancies is reverted to the previous status.

Note: If the “Tech Log Basis” is set as “JL - consolidated” or “JL - Leg Level”, and if only Journey Log # is entered, then the system ensures that the Journey Log #/Flight#/Leg# combination or Journey Log #/Line# combination for the Aircraft Reg # is not referred in any technical log. If the Journey Log has not been referred in any other Technical Log, system retrieves the Flight #/Leg # or Line # from the Journey Log whose arrival date and time is lesser or equal to the entered execution date and time and for which  “Maint. Execution” is set as “Yes”.

The system displays the following in the “Customer Order Details” group box:

•  Select the hyperlinked Customer Name to view Customer information

• Enter the following fields in the “Customer Order Details” group box:

The system displays the following in the “Customer Order Details” group box:

• Select the hyperlinked "Customer Order Desc" to view the customer order information.

• Select the “Discrepancy Details” tab to record discrepancy details associated to the technical log.

• Select the “Inspector / Mechanic Information” tab in the main page, if you wish to record additional information for the technical log.

• Select the “Cost & Additional Information” tab in the main page,  to record additional information and cost details incurred on the technical log.

The system displays the following in the “Link Info” group box, to indicate the information available for the technical log:

The system displays the following in the “Record Statistics” group box:

To update the modified details of the technical log

• Click the “Edit Log” pushbutton to save the updated details.

Note: The system calculates the actual cost for the technical log as the sum of material cost, resource cost, employee cost, labour cost, facilities cost and miscellaneous cost.

Note: This action is workflow-enabled. Notification messages can be sent and you can configure further processing of this document in the "Workflow Management" business component.

The system performs the following:

• The system does not permit modification of “Action” field from “Defer” to any other value in the “Deferred Discrepancy Resolution” multiline, if the maintenance report allocated to the current technical log is associated to any other execution document.

• The system does not permit modification of “Action” field from “Transfer” to any other value in the “PIREP & Tech Log Reported Discrepancy Details” multiline or “Deferred Discrepancy Resolution Details” multiline, if the component replacement has already taken place for the part #/serial # specified in the technical log.

• When any of the maintenance report associated to the current technical log is deferred while modifiying the technical log, the system checks the deferral limits based on the type of the deferral limit and the deferral limit basis.

Note: The system does not allows you to defer the maintenance report if the threshold date (or) revised threshold date is earlier than the current server date, and if the threshold value (or) revised threshold value is less than the current parameter value associated to the aircraft.

• If the “Auto inclusion of jobs based on Alert Date/Value” field is set as “Technical Log” or “Line Package & Technical Log” in the “Set Options” activity of the “Central Planning” business component, then the system retrieves all the pending jobs from component planning and central planning pending tray, whose alert date is earlier than or same as the current technical log date and time. This is not applicable if the back end option “Retrieval of Forecasted Work Units/Deferred Discrepancies" is set as either “Deferred Discrepancies” or “None”.

• The system retrieves and allocates the pending work units and discrepancies to the current technical log based on the value set for the back end set option “Retrieval of Forecasted/Deferred Discrepancies” and “Allocation Basis of Pending Work Units to Techlog”. The “Retrieval of Forecasted/Deferred Discrepancies” back end set option could be any one of the following options: “Forecasted/Overdue work units”, “Deferred Discrepancies”, “Both”, or “None”, and the “Allocation Basis of Pending Work Units to Techlog” could be “Scheduled Date”, “Planned Start Date” or “Which ever is earlier”.

1. If the backend option is set as “Forecasted/Overdue Work Units” then work units will be assigned automatically on creation of technical log.

2. If the backend set option is set as “Deferred Discrepancies”, then the system automatically retrieves all the deferred discrepancies on creation of the technical log.

3. If the backend set option is set as “Both”, the  system retrieves both the work units and the deferred discrepancies on creation of the technical log. Else, if it is set as “None”, then none of the workunits/deferred discrepancies will be retrieved.

Note: The system will retrieve the Maintenance Report (Deferred Discrepancies) only on clicking the “Get Details” pushbutton.

• If the back end set option is “Forecasted/Overdue Work Units”, then the system automatically retrieves and allocates the work units from the pending tray to the current technical log that is being created in spite of whether the work unit is due or not, based on the value set for the back end option “Allocation Basis of Pending Work Units to Techlog”.

Note: For example: If the “Allocation Basis of Pending Workunits to Techlog” is “Scheduled Date”, then the system retrieves and allocates the work units to the technical log based on the schedule date alone. But, if the work unit does not have a “Schedule date” against it, for eg: in case of As Required Work Units, the system will retrieve and allocate the work unit based on its “Planned Start Date”. If the back end option is “Which ever is earlier”, then the system will allocate the work units depending on the “Scheduled Date” or the “Planned Start Date” which ever is earlier.

Note: The above mentioned validation is not applicable if the “Retrieval of Forecasted/Deferred Discrepancy” back end option is set to either “Deferred Discrepancy” or “None”.

Note: If the technical log is created with reference to line package, then the system does not consider the back end set option set for “Retrieval of Forecasted/Deferred Discrepancies”.

• While editing the technical log, the system updates the maintenance report details simultaneously in the “Discrepancy Processing business component when the “Action” field is set to “Deferred”.

Note: The system updates the record status of the maintenance report from “Deferred” to “Under Resolution”, if the “Action” field is set to a value other than “Defer”.

• The system posts the financial entries to the relevant account codes in the "Finance Book Processing" business component.

To confirm the technical log

Before confirmation, ensure the following:

• A discrepancy is reported in the technical log, when the “Discrepancy Rep?” field is set as “Yes” while providing sign-off information in the “Record Work & Sign-Off Information” page.

• The status of the technical log is not “Confirmed” or “Cancelled”. On confirmation, the status of the technical log is updated to “Confirmed”.

• The component replacement records, with the “Source” set as “Remove”, “Attach” or “Swap”, are confirmed in the “Replace Components” page.

• The “Execution Status” drop-down list box in the multiline of the “Record Work & Sign-off Information” page is not selected as “Pending” or “Incomplete”, if the work unit “Planning Type” is “Unplanned” and “Source” is “Discrepancy”.                                                                    

• Click the “Confirm Tech Log” pushbutton to confirm the technical log.

Note: This action is workflow-enabled. Notification messages can be sent and you can configure further processing of this document in the "Workflow Management" business component.

The system performs the following:

• The system calculates the actual cost for the technical log as the sum of material cost, resource cost, employee cost, labour cost, facilities cost and miscellaneous cost.

• If the Tech Log is based on a customer order with a service price list that has the “Pricing Method for Skills” set to “Roster Code”, the system (i) splits the time sheet records into various time slabs, and (ii) computes the skill price as defined in the roster code details of the service price list attached to the customer order.

• While confirming the technical log, the system ensures that a deferral task exist for the Maintenance Report, of deferral type “CDL” or “MEL”, if the “Sign-off reqd. for Deferral of Discrepancy” field is set to “Yes” in the “Set Options” activity of the current business component

• On confirmation of the technical log, when any of the maintenance report associated to the current technical log is deferred, the system checks the deferral limits based on the type of the deferral limit and the deferral limit basis.

Note: The system does not allows you to defer the maintenance report if the threshold date (or) revised threshold date is earlier than the current server date, and if the threshold value (or) revised threshold value is less than the current parameter value associated to the aircraft.

• For the Aircraft Reg # - Work unit combination, the system deletes the work units from Central Planning pending tray

(i) if the source of the work units is “Forecast” and the execution status is “Completed”, and

(ii) if the source of the work units is “Deferment Request” and the work unit execution status is  “Completed” or “Pre-Closed”

Updation of parameter values

For planned, unplanned and direct work units where the job type is on-wing and execution status is “Completed”, based on their maintenance type, the system resets the following parameter values, of the components on which work units are executed in the “Edit Consumption and Range Parameters” page of “Edit Component Record” activity in the “Aircraft” business component.

•  If the maintenance type is overhaul, the system resets the “Since Overhaul”, “Since Repair” and “Since Inspection” parameter values to zero.

• If the maintenance type is repair, the system resets the “Since Repair” and “Since Inspection” parameter values to zero.

• If the maintenance type is inspection, the system resets the “Since Inspection” parameter value to zero.

Note: The system will not reset any value, if the maintenance type for the work unit is “Others” or “Retire”.

If parameter values are recorded against the technical log, the system updates the parameter values with Techlog # / Line # / WorkUnit #/ Task# / Sub Task# reference in the parameter value history in the “Aircraft” business component, based on the update mode.

Compliance details updation for work units

On confirmation, for the un-forecasted work units added from the “Perform Opportunity Maintenance” page, and the direct work units added in the “Record Work and Sign-Off Information” page, where the execution status is set as “Completed”, the system updates the compliance information such as the ‘Last Performed Date’ and ‘Last Performed Value’. If those work units are repetitive, then their ‘Next Schedule Date’ and ‘Next Schedule Value’ are also updated in their respective aircraft maintenance program or component maintenance program. If work unit is scheduled more than once in the maintenance program, the system updates the compliance information for all of them.

If the operations type is “Flight Ops”, the system updates the compliance date of the work units in the compliance history of the “Aircraft” business component, based on the option set for the “Ref. Date for Compliance against Flight Ops” in the “Set Options” activity. If the option setting is “Start Date”, the system considers the start date of the technical log. If the option setting is “End Date”, the system considers the end date of the technical log. If the option setting is “User Defined”, the system considers the compliance date specified in the “Record Work Unit & Sign-off Information” page.

Note: The compliance date specified in the “Record Work Unit & Sign-off Information” page should lie between the “Actual Start Date & Time” and “Actual End Date & Time” of the technical log.

If the operations type is “Repair Station”, the system updates the compliance date of the work units in the compliance history of the “Aircraft” business component, based on the option set for the “Ref. Date for Compliance against Repair Station” in the “Set Options” activity. If the option setting is “Start Date”, the system considers the start date of the technical log. If the option setting is “End Date”, the system considers the end date of the technical log. If the option setting is “User Defined”, the system considers the compliance date specified in the “Record Work Unit & Sign-off Information” page.

Note: The compliance date specified in the “Record Work Unit & Sign-off Information” page should lie between the “Actual Start Date & Time” and “Actual End Date & Time” of the technical log.

Note: If any work unit of the current technical log is “Pre-Closed”, the system updates the compliance details in the central planning pending tray based on the option setting.

If the execution status of the planned work units is “Completed” in the technical log, the system updates the compliance details in their respective  “Aircraft Maintenance Program” or “Component Maintenance Program”.

If the “Enforce Excess/Core Returns?” field in the “Set Options” activity is set as “No”, the Technical log gets confirmed without checking for the pending return quantity.

If the “Enforce Excess/Core Returns?” field in the “Set Options” activity is set as “Yes”, ensure that the following conditions are satisfied for work units available in the “Record Material & Report Consumption” page:

• “Issued Quantity” is specified for the corresponding part number and material request number.

• “Pending Return Qty”  and “Pending Return Qty–Core“ is zero.

Note: The system calculates the next schedule for incomplete work units based on usage schedules.

For work units with “Execution Status” as “Incomplete”, the system displays the first compliance date as the “Compliance Date” for the work units.

For the work units that are available in the “Record Work & Sign-off Information” page, with “Execution Status” as “Pending”, the system performs the following in the “Central Planning” and “Component Work Planning” business components:

• Sets the job status as “Pending”.

• Sets the job status as “Deferred”, for work units whose source is deferred in the “Record Work & Sign-off Information” page.

For work units available in the “Record Work & Sign-off Information” page for the current technical log number, with source as 'Aircraft Forecast' or 'Component Forecast' or 'Deferred', the system updates the following:

• The “Execution Status” as “Completed”, for maintenance programs to which the work units belong.

• The compliance date in the “Record Work & Sign-off Information” page.

For the work units available in the “Record work & Sign-off Information” page with source as “As Required” or “Maintenance Event”, and execution status is “Completed”, the system updates the following:

• The compliance history or the maintenance event execution history, of the primary maintenance program in the “Aircraft Maintenance Program” business component.

• Compliance Date available in the ”Record Work & Sign-off Information” page as the “Execution Date” in the “Aircraft Maintenance Program” business component.

For work units available in the “Record Work & Sign-off Information” page with source as “Aircraft Forecast” or “Component Forecast” and with execution status as “Pending” or “Incomplete”, the system updates the following:

• The execution status as “Pending”, of the “Aircraft Maintenance Program” or “Component Maintenance Program” business component.

• The execution status as “Deferred” if the source is deferred.

Note: The system releases the unissued-but-allocated quantity for a material request in the “Material Request” business component. This is made available to other technical logs for those material requests that were generated from the “Material Request” business component.

Other updations

The system will short close the material requests associated to the technical log, which are in “Authorized” or “Partially Issued” status. While short closing, the Stock Issue or Stock Transfer Issue documents, if any, created in “Fresh” status for those material requests, will be canceled. Stock Transfer documents associated with such canceled Stock Transfer Issue documents will also be short closed.

For the work units retrieved from the "Central Planning" business component, the system updates the "Job Status" of work units (for which the "Execution Status" is set as "Completed” in the "Record Work  & Sign-off Information" page) as "Completed" in the "Central Planning" business component.

If the “Automatic Confirmation of Maint.Report” option is set as “Yes” in the “Set Options” activity, the status of the maintenance report is automatically set to “Confirmed” on confirmation. The system also checks whether the login user has been assigned the rights to confirm a maintenance report in the “Discrepancy Processing” business component. If the login user does not have the required rights, then the status of the maintenance report will not be automatically confirmed even when the “Automatic Confirmation of Maint.Report” option is set as “Yes” in the “Set Options” activity.

The system posts the financial entries to the relevant account codes in the "Finance Book Processing" business component.

The system ensures that component replacement details are recorded for the completed replacement work units reported in the 'Record Work and Sign-Off Information page.

If component replacement details are available, the system updates them before confirming the technical log. The system performs the following if component replacement details are specified:

• If the component that is getting attached, or any of the child components, has some calender-based schedules and the updation is based on the date of attachment, the system adds the interval to the current replacement date. This date is updated to the next schedule date, in the “Component Maintenance Program” business component when the next schedule date is blank.

• If the incoming component, or any of its child components, has position-based schedules, then the system checks if the current aircraft model, configuration class and attached position or its child component has a defined position-based schedule. If so, the system adds the position-based interval to the last schedule date of the work unit for the respective component in the “Component Maintenance Program” business component.

• The system updates the position based formula of the component for the new position code, based on the source document type.

•  If the end date is left blank, the warranty date is updated depending on the flag set in the warranty agreement for the component or any of its child components in the “Warranty” business component.

• If the component is removed from the PBH assembly, then the system updates the ownership as “PBH” and the possession status as “PBH” in the “Aircraft” business component.

• Expense Type can be set as “Capital” only if the Ownership of the Aircraft Reg # is identified as “Owned” or “Leased Out” in the “Aircraft” business component.

• Ensures that the outgoing component is attached to the aircraft.

• For those records, which do not have a component replacement number, the system generates the component replacement number and cannibalization number for components for which the "Object Type" is set as "Component" in the "Replace Component" page.

To cancel the technical log

• Click the “Cancel Tech Log” pushbutton to cancel the technical log.

Note: This action is workflow-enabled. Notification messages can be sent and you can configure further processing of this document in the "Workflow Management" business component.

Note: The system does not allow you to cancel the technical log, if the selected technical log has been referenced in the purchase order of type “Adhoc PO” or “Service PO”, and if the status of the line item (technical log) is other than “Short Closed” or “Cancelled”.

The system verifies for the following, before canceling the technical log:

• Only technical logs that are in the “Fresh” status can be canceled.

• The “Execution Status” of the planned work units must not be “Completed” or “Incomplete”.

• You cannot cancel a technical log for which the component replacement transaction is confirmed.

Note: If the source of work units is “Aircraft Forecast “ or “Component Forecast”, the system updates the “Execution Status” of work units to “Pending”.

Note: If the source of the work units is “Deferred”, then the system updates the “Execution Status” of the work units to “Deferred”.

If the source of the work units is “Line Package”, the system updates the status of the work units from “Techlog Created” to “Package Created”, and removes the “Tech Log #” reference in the line package created in the “Line Planning and Control” business component.

The system will short close the material requests associated to the technical log, which are in “Authorized” or “Partially Issued” status. While short closing, Issue or Stock Transfer Issue documents, if any, created in “Fresh” status for those material requests, will be canceled. Stock Transfer documents associated with such canceled Stock Transfer Issue documents will also be short-closed.       

To proceed, carry out the following

• Select the “Record Work &Sign-off Information” link to update work information.

Refer “Updating work information details – An overview” for more details.

Note: On confirmation of the technical log, the execution status of all the work units specified in the “Report Additional Work Scope” page is set as “Completed”.

• Select the “Request Material & Report Consumption” link to update material request and report consumption details.

Refer “Updating material request and reporting consumption for the technical log  – An overview” for more details.

• Select the “Replace Components” link to update component replacement details.

Refer “Updating component replacement for maintenance report – An overview” for more details.

• Select the “Record Employee Time Sheet” link to update employee timesheet information.

Refer “Updating employee timesheet information – an overview” for more details.

• Select the “Perform Opportunity Maintenance” link to update opportunity maintenance details.

• Select the “Defer PIREP & Tech Log Reported Discrepancies” link to defer discrepancies reported in the technical log.

Refer “Deferring discrepancies from the technical log – an Overview” for more details.

• Select the “Edit References” link to edit reference document details for the technical log.

Refer “Entering reference document details for technical log – An overview” for more details.

• Select the “Create General Material Request” link to create a material request.

Refer to the “Material Request” online help for more details.

•  Select the “Create Maintenance Return” link to create a maintenance return document for returning the excess stock or core-returnable, if any.

Refer to “Stock Return” online help for more details.

• Select the “Report Resource Consumption” link to update resource actual information.

Refer “Updating resource actuals information for maintenance report - An overview” for more details.

• Select the “Release Aircraft” link to update aircraft release details for the technical log.

• Select the “Report Fuel / Oil Log” link to enter the fuel and oil consumption details.

• Select the “View Journey Log” link to view journey log details.

• Select the “View Aircraft Maintenance Log” to view the maintenance log details.

• Select the “View Return” link to view the part return details in the material return document.

• Select the “Update Parameter Details” link to update the aircraft parameter values.

• Select the “Create CWO/RO” link to create a component work order or a repair order.

• Select the “View Engg. Advice Note” link to view the details of the engineering advice note for the aircraft.

• Select the “Print Technical Log” link to preview and print technical log details.

• Select the “Launch Technical Documentation” link to  launch technical document.

• Select the “Inquire Engg. Service Request” link to view the details of the engineering service request.

• Select the “Generate Accountability Sheet” link to generate the accountability sheet.

• Select the “Generate component Change Sheet” link to generate the component change sheet.

•  Select the “View Associated Discrepancies” link to view the associated discrepancy details.

Refer the “View Discrepancy” online help for more details

Editing technical log information – An overview

In this page, you can edit the technical log information.

If a journey log associated to the technical log is modified, then the system deletes all the discrepancies from the journey log and updates the technical log with the modified discrepancies.

In this page, you can modify the deferral details specified for the discrepancies or maintenance reports. You can also modify the work unit details.

You can specify the maintenance activity that has to be performed to rectify the incident or accident on the incoming flight or the general maintenance check that has to be performed on the flight. The details of the maintenance activity such as the visit package number, maintenance program number, its type, cycle, schedule number, work unit that has to be performed and the work unit type can be specified.

You can also specify the maintenance check that has to be performed, if the flight is the first flight of the day. The system generates the technical log number and sets the status of the technical log to “Fresh”.

What you can do in this page

Choose a numbering pattern to generate the technical log number

Specify the category for the technical log

Set the default action for discrepancies in the multiline

Edit technical log

Choose a numbering pattern to generate the technical log number

You can select a numbering type for the technical log. A unique technical log number will be generated by the system based on the numbering type you select in this page.

• Select the numbering type in the “Numbering Type” drop-down list box.

• Enter all other technical log details.

On clicking the “Edit Log” pushbutton, the system generates the technical log number based on the selected numbering type.

Specify the category for the technical log

You can select the category to which the technical log belongs.

• Select the category from the “Tech. Log Category” drop-down list box.

• Enter all other details.

Set the default action for discrepancies in the multiline

You can set the default action for all the discrepancies in the multiline.

• Select the action from the “Default Action” drop-down list box.

• Enter all other details.

On clicking the “Edit Log” pushbutton, the system updates the default action in all the rows in the multiline.

Edit technical log

You can modify a technical log and also confirm the details in the same page.

• Enter the Tech.log Category , fuel, Reporting Station, Executiopn date & Time details in the respective group boxes.

• Enter the remedial action for the reported discrepancies, in the “PIREP & Tech Log Reported Discrepancies” multiline.

• Enter the remedial action for the deferred discrepancies, in the “Deferred Discrepancy Resolution Details” multiline.

• Enter the outgoing flight details, inspector details and mechanic details in the respective group boxes.

• Click the “Edit Log” pushbutton to create the technical log.

The system assigns the “Fresh” status to the created technical log.