Selecting engineering document for releasing

This page allow  you to select the engineering documents for release or cancellation. Tell me more.

• Select the “Release Engineering Document” link under the “Engineering Document” business component.

The “Release Engineering Document” page appears.

The system displays the following field:

• Enter the following in the “Search Criteria” group box, to search for a engineering document. Data entry in the following fields is optional:

• Click the “Search” pushbutton, to display the search results.

Note: Depending upon the filter criteria specified, the system retrieves engineering documents, which are in the “Fresh” status, and for which the authorization status is set as “Authorization Not Required” or “Approved”.

The system retrieves only those engineering documents that await login user’s authorization as identified in the work flow configured in the “Work Flow Management” business component.

The system will not retrieve preloaded engineering documents.

The system displays the following fields in the “Search Results” multiline:

• Enter the following:

• Enter the following field if you wish to release or cancel the engineering document:

• If you wish to selectively release or cancel engineering documents, check the box in the “Select” column of the multiline to mark the engineering documents for releasing or cancelling.

To release engineering documents

Note: On releasing the Engineering Document ensure the following:

The model/part configuration associated to the Engineering Document, is in "Active" status.

The aircraft maintenance program is in "Active" status, if the Engineering Document applicability is set to "Aircraft".

The component maintenance program is in "Active" status, if the Engineering Document applicability is set to "Component" or "Engine".

• Click the “Release Eng. Doc.” pushbutton, to release the engineering documents selected in the multiline.

Note: The 'Next Schedule Date' or 'Next Schedule Value' will not be computed for tasks for which the 'Conditionally Evaluated?' field is set as "Yes" in the 'Conditional Maint. Evaluation' tab page of the 'Edit Parameter Reading / Conditional Maint. Eval.. Form' activity of the current business component.

Note: The Engineering documents will be released only if all the associated task cards are in activated status.

The system ensures the following before releasing the engineering document:

• Upon configuration change initiated by an engineering document , the component maintenance programs inherit the part program of the new part. However, if any of the tasks in the maintenance program is not effective for the component, the schedule status of the task is set as Inactive.

• Automatic inheritance upon part # modification: Based on the process parameter Inherit Part Program changes to Component Maintenance Program on Part modification? under the entity type Tech Records Process Ctrl and the entity Part Program in the Define Process Parameters activity ofCommon Master, the system updates the maintenance program of the component whose part # has been changed as illustrated below:

• The schedule (calendar or usage based) is provided if the “Schedule Type” is “On-time” or “Recurring”.

Note: The system releases the engineering document if only the “Model” or “Part Effectivity” is specified for the engineering document.

• The task must be schedule tracked.

• The task must have 'Conditionally Evaluated?' field is set as "No" in the 'Conditional Maint. Evaluation' tab page of the 'Edit Parameter Reading / Conditional Maint. Eval.. Form' activity of the current business component.

• The “Applicability Group #” must have been defined for Aircraft / Components in “Aircraft/ Component Effectivity Details” page.

• The schedule date should not be blank against each maintenance object identified in the effectivity of the engineering document and Revision Number combination.

•  The scheduled date/ value must have been entered in the “Initialize Eng. Doc. Schedules” page for tasks, which have ‘Prog. Item Type’ and ‘Conditionally Evaluated?’ fields in the ‘Edit Task Details’ page set as “Schedule Tracked” and “No” respectively.

• All the resources entered for the engineering document are defined in the respective business components

• For the engineering documents selected for release, the task and revision number combination should be unique.

• For the engineering documents with task classifier as “Existing / Improvised”, the task and revision number combination must have been defined in “Maintenance Task” business component in “Active” status.

The system performs the following on releasing the engineering document:

• If “Direct Execution” is not marked, the system ensures that atleast one maintenance program is defined for each aircraft identified in the effectivity, and it should be in “Active” status. If more than one program exits in ‘Active’ Status for an aircraft, then one of the Active Program should be a Primary Program for that aircraft.

• Updates the “Task Classifier” as “New” or “Improvised” in the “Maintenance Task” business component.

• For the “New” and “Improvised” tasks, the system copies all information identified for engineering document  and task combination including the periodicity details.

• For the “New” tasks, the current engineering document is updated as the source document for the task and the task category is updated as “Mod” in the “Maintenance Task” business component.

• Updates Maintenance Task with Part MOD details from Engineering / MOD tasks.

• For the “Improvised” task, if a new revision number is identified, the system updates the revision type of the task depending on the MCR source.

• If the “Update Model / Part Configuration” is set to “After Release” in the "Edit Engineering Document" activity, the system updates the existing part numbers in the position code and level code of the model or part configuration, with the new part number. The revision number of the configuration is incremented by '1' and the status of the configuration changes to “Active”. If the “Base Line (Y/N)” option is enabled, the system baselines the new revision number for the model or part configuration.

• Updates the component maintenance program details. If the “Direct Execution” check box is not selected, the system updates the work units (Task or Standard Procedure ) and with “Engine” or “Component” applicability, identified for the engineering document in the component maintenance program. Also if the “Update Part Main. Program” options is selected as “Yes”, the system updates the part program of all the parts identified as part effectivity for engineering document.. If the work unit already exists in the component maintenance program the system updates the changes made to the work units. The resource and material requirement information identified for the tasks / standard procedures are also updated to the component maintenance program.

• Generates the purchase request for all the parts identified in the “Plan Material Requirement” page.

• Updates the standard procedures in the “Maintenance Task” business component with the new task details defined for the engineering document.

• Update all the certificate coverages identified for each task in the “Maintain Certificate Information” activity of the “HR Setup” business component.

• Updates part details: If a new part of type “Component” is getting defined or an existing part is improvised, the system updates the part effectivity for the aircraft model in the “Maintain Part Information” activity of the “Aircraft” business component.

• Cancels the terminated engineering documents, when the engineering document released is a ‘Terminating Engineering Document’. For all such terminated engineering documents, the system changes the status "Cancelled" and inserts cancellation comments stating "Terminated by <Eng Doc #> " (For Ex:Terminated by Eng Doc/02/112)

• Sets the status of the engineering document to “Released”.

Note: This action is workflow-enabled. Notification messages can be sent as per the settings you have defined in the "Workflow Management" business component.

• Updates the status of the Task # as “Active” irrespective of the value specified in the “Auto Task Card Authoring?  of in the interacting “Common Master” business component

• Updates the compliance status of the engineering documents to “Not Complied” against each effectivity identified for the engineering document. Updates the compliance status and copies the compliance details when the Action on Rev. Effectivity for the engineering document is set as “Carryover Compliance”.

• If  the “Action on Revision Effectivity” is "Carryover Compliance",  the maintenance objects (Aircraft Reg # or Part # and Serial #) that were already complied will  be copied from the previous Revision # to the new Revision # with the “Compliance Status” as "Complied". The release of engineering document would be applicable for the maintenance objects with the '”Compliance Status” as "Not Complied".

• If the “Action on Rev. Effectivity” is set as “Revoke”:

• The system removes all the references of the engineering document from the aircraft maintenance program and component maintenance program.

• The system also removes work units having reference of the engineering document from the central planning pending tray and component pending tray.

Note: Revoking an engineering document will not change any configuration updates, part number changed, new parts created or purchase requests created because of the previous revision.

• For engineering document with schedule type “Recurring” or “One Time”:

a) A schedule (calendar or usage based) should exist for each Task # of type Schedule and Applicability Group # combination in "Edit Schedule Information" screen.

b) At least one Next Schedule Value and/ or Next Schedule Date should be available for each “Schedule Tracked” task in the ”Initialize Eng. Doc. Schedules” page.

• If the tasks of Program Item Type as “Non Tracked” exists in the “Edit Schedule Task Information” page, the system executes the following:

a) If only one task with the Program Item Type as “Schedule Tracked” exists, and the “Conditionally Evaluated?" field is set as "No" the system establishes a “Concurrent Relationship” between the Schedule Tracked tasks and the Non-Tracked tasks. Also, the system add entries in the “Maintain Task Relationship” activity where the “Schedule Tracked“ task will be considered as the primary task and the “Non-Tracked” tasks will be considered as the related tasks with the relationship between the primary and related tasks as “Concurrent – Specific”.

b) If more than one task with the Program Item Type as “Schedule Tracked” exists, the system ensures that a “Concurrent Relationship” exists between the “Schedule Tracked” tasks and the “Non-Tracked” tasks  irrespective the task is conditionally evaluated.

• Updates conditional relationship between the task and the follow-up tasks defined in the 'Edit Parameter Reading / Cond. Eval. Form' activity of the 'Conditional Maint. Evaluation' tab page in the “Maintain Task Relationship” activity of the interacting “Maintenance Task” business component,.

• The terminated engineering documents are transferred to the pending tray of the “Central Planning” and “Component Maintenance Planning” business components for processing.  The system updates the status of all the terminated engineering documents as “Cancelled” and their cancellation comments as “Terminated By”.

• If the applicability of the engineering document is “Component” or “Engine” and if the effectivity is “Component”, the system ensures the work unit that is available in the component maintenance program / pending tray is not duplicated in the task details of the engineering document.

• The system updates the following in the component maintenance program:

1. Work units (task or standard procedure) of the engineering documents with applicability “Engine” or “Component”, if “Direct Execution” is marked as “No”.

2. Part program of the parts identified under the part effectivity of the selected engineering documents, if the “Update Part Program” is set as “Yes”.

3.  Periodicity details, schedule details and threshold value of the engineering document.

Note: The system deletes the work units (task or standard procedure) of the terminated engineering documents with applicability as “Engine” or “Component” from the component maintenance program and from the central planning / component pending tray. Also the system updates the status of the terminated engineering documents as “Cancelled” and cancellation comments with “Terminated By”.

• If “Update Part Program” is set as “Yes”, the system updates reference schedule information from the reference work unit as available in the maintenance program to the engineering document work unit that is updated in the aircraft maintenance program or part program.

• When the ‘Action on Revision?’ is set as “Revoke/Terminated” while releasing the Engineering Document, if the schedule status of the task is updated as “Inactive” / “Terminated” in Aircraft / Component Maintenance Program, with the task having Escalation Ref # in Aircraft / Component Maintenance Program, the system deletes the task from the pending tray, if the Line Status of the task is updated as “Cancelled” as shown in the below table.

Note: The system deletes all the tasks whose Line Status is updated as “Cancelled”, from the pending tray.

•  The system updates the sign-off requirements for the sub task as explained below:

1. Updates the sign-off status as “Not Required”, if the resource group is set as “Not Required” for the sub task in the “Edit Sub Tasks” page.

2. Updates the sign-off status as “Pending”, if the resource group is set as “Inspector”, “Mechanic” or “Insp. & Mech” in the “Edit Sub Tasks” page.

• On releasing the engineering document, the system updates the NSD / NSV and the NSD / NSV computation basis controls ‘Next Due Calc. On’, ‘Calc. Ref. Date’ and ‘Last Schedule Date / Value’ in various scenarios, as explained in the table.

• Future-dated engineering documents: The process parameter “Update Next Sch. Date in maintenance program for future dated Eng. Doc.?” under the entity type “Eng. Doc. Type” of entity “—All Eng. Doc.—“ in the Define Process Entities activity of Common Master decides whether date scheduled tasks from engineering documents must  get updated as  "To Be Decided" or "Non-Block" in maintenance programs. If the effective date for the engineering document lies in the future, and, if the value of the process parameter “Update Next Sch. Date in the maintenance program for future dated Eng. Doc.?” is ‘0’; upon release, the system adds tasks from the engineering document to all ‘Active’ maintenance programs for the component/ aircraft wherein:

• Prog. Item Type for the task will be “To Be Decided”

• NSD for the task will be Blank

On the arrival of the effective date, “Prog. Item Type” of these tasks is automatically set as “Non-Block”. However, this happens only for Scheduled-Tracked tasks of engineering documents.

Alternatively, if “Update Next Sch. Date/Value in maintenance program for future dated Eng. Doc.?” is ‘1’, the attributes would be like this:

• Prog. Item Type for the task = “Non Block”

• NSD for the task = Computed NSD

Note: To facilitate workscoping of tasks from future-dated engineering docs, set “Update Next Sch. Date in maintenance program for future dated Eng. Doc.?”to ‘1’. On the contrary, to defer workscoping of tasks till the effective date of the engineering doc, the process parameter must be ‘0’.

Typically, maintenance programs of maintenance objects are updated upon release of engineering documents. However, in a scenario where engineering documents could have been released even before the effected aircraft/component becomes ‘Active’, the system automatically updates the maintenance programs upon activation of these entities and sets ‘Program Updated?’ as ‘Yes’. However, if the engineering document is in the ‘Fresh’ status, the program update will not happen (though serial #s will be updated in the document) and Program Updated? will be ‘No’. ‘Program Updated?’ becomes ‘Yes’ only upon update of the maintenance program of the aircraft/component as necessitated by the engineering document. In a slightly different situation when the effective date of the released engineering document lies in the future, the system updates the task in the maintenance program though it does not update the NSD/NSV of these tasks and sets ‘Program Updated?’ as ‘Yes’.

Impact on Inactive aircraft: On release of an engineering order, the engineering tasks are added to the maintenance programs of effective aircraft, both Active and Inactive. Also, Schedule Status of such tasks is set as ‘Active’ in the maintenance programs of Active aircraft. However, Schedule Status of engineering tasks in the maintenance programs of Inactive aircraft depends on the process parameter “Update Eng.Task's schedule status as Inactive in maintenance program for inactive Aircrafts on release of Eng.Doc.?” under the entity type “Eng. Doc. Type” and the entity "All Eng. Doc” in the Define Process Parameters activity of Common Master. The next table elaborates on the functioning of the process parameter.

To cancel engineering documents

•  Click the “Cancel Eng. Doc.” pushbutton, to cancel the engineering document(s) selected in the multiline.

Note: You cannot cancel Engineering Documents that are applicable to the aircraft with record status “Frozen”.

• The system sets engineering document to “Cancelled” status.

•  If any of the cancelled task marked as “New” is referred in any other engineering document (that is in 'Fresh' status), the system sets the task classifier as “New” for the task in the second engineering document.

To create / edit engineering document

• Select the “Edit Eng. Doc.” Link at the bottom of the page to create / edit the engineering document.

To view authorization status log

• Select the “View Authorization Status Log” link at the bottom of the page, to view the authorization status log.

To view compliance history

• Select the “Track Maintenance Compliance History” link at the bottom of the page, to view engineering compliance details.

Selecting engineering document for releasing – An overview

You can select the engineering documents for release or cancellation, in this page. You can carry out a search based on the change document type, source document type, engineering document number, user status, Modification Committee Meeting (MCM) that processed the change request, category, ATA chapter, applicability and MCM date.

Based on the search criteria entered, the engineering documents that are assigned to the login user are displayed. You can release or cancel engineering documents in bulk, or select a particular engineering document to be released or cancelled. You can enter release or cancellation comments for the engineering document.

On releasing the engineering document, the task details and the configuration details are updated, and the purchase request is generated for the parts that are required for executing the engineering document.

You can also select a engineering document to view the authorization committee comments.