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:
Date Format |
The format in which the date fields must be entered in this page. This format is displayed from the "User Preferences" component based on the login user ID. In case the format is not defined, the system displays the date format from the “Enterprise Modeling” business component by default. |
Enter the following in the “Search Criteria” group box, to search for a engineering document. Data entry in the following fields is optional:
Source Doc Type |
Use the drop-down list box to select the type of the modification document or the source document of the engineering document. The system lists all the values defined in the “Create MCR Document Type" activity of the “Common Master” business component. Leave this field blank, if you wish to retrieve engineering documents irrespective of the source document type. |
Eng. Doc # |
The unique number of the engineering document (Alphanumeric, 18). You can enter the number in full or specify it partially using the “*” character. The system lists all the engineering document numbers that are similar to the values entered here. |
User Status |
Use the drop-down list box to select the user status of the engineering document.
The system retrieves the engineering document numbers that are in the user status specified here. Leave this field blank, if you wish to retrieve engineering documents irrespective of their user status.
|
Eng. Doc. Type |
Use the drop-down list box to select the Eng.Doc Type. The system lists the user defined "Document Types" in “Active” status for the "Eng. Doc Type" in the interacting “Configure Document Attributes” activity of the “Common Master” business component. The system leaves the field blank by default. |
Exe. Type |
Use the drop-down list box to select the execution type. The valid options are “Major” , “Minor” and Blank. The system leaves the field blank by default. |
Process Ref. # |
To retrieve the release engineering document, enter the process reference number applicable for a MCR # and Revision # combination. |
Eng. Doc Category |
Use the drop-down list box to select the category to which the engineering document belongs. The system lists all the quick codes of type “Eng Doc-Category” defined in the “Create Quick Code” activity. The system retrieves all the engineering documents that belong to the category selected here. |
ATA # |
The ATA chapter on which engineering document must be executed (Alphanumeric, 16). You can enter the number in full or specify it partially using the “*” character. The system retrieves all the engineering documents containing ATA chapter number similar to the value entered here. Leave the field blank to retrieve all the engineering documents irrespective of the ATA chapter number. |
Applicability |
Use the drop-down list box to specify the applicability of the engineering document document to be retrieved. The engineering document could be applicable for “Aircraft”, “Engine” or “Component”. The system sets the field to “Aircraft” by default. |
MCR # |
The maintenance change request against which the engineering document is created (Alphanumeric, 40). The system retrieves all the engineering documents with the MCR number entered here. |
Revision # |
The revision number of the maintenance change request (Alphanumeric, 40). |
MCM: From Date |
The starting date, in the range of dates, on which the MCM was conducted (Date Format). The date entered here should be in the format displayed in the “Date Format” field. The system retrieves all the engineering documents for which the MCM was convened on the specified date. |
MCM: To Date |
The ending date, in the range of dates, on which the MCM was conducted (Date Format). The date entered here should be in the format displayed in the “Date Format” field. The system retrieves all the engineering documents for which the MCM was convened on the specified date. The date entered here should be greater than the “MCM: From Date”. |
Aircraft Model # |
The number identifying the aircraft model (Alphanumeric, 20). You can enter the number in full or specify it partially using the “*” character. The system retrieves all the engineering documents applicable to the aircraft model specified here. |
Part # |
The number identifying the part for which the engineering document is applicable (Alphanumeric, 40). You can enter the number in full or specify it partially using the “*” character. The system retrieves all the engineering documents that are applicable for the part specified here. |
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:
Eng. Doc Type |
The type of engineering document. |
Eng. Doc # |
The unique number of the engineering document. |
Revision # |
The revision number of the engineering document. |
Applicability |
Indicates whether the engineering document is applicable for “Aircraft”, “Component” or “Engine”. |
Exe Type |
The type of execution, whether “Major” or “Minor”. |
User Status |
The user status of the engineering document. |
Process Ref # |
The process reference number applicable for a MCR # and Revision # combination |
MCR # |
The number identifying the MCR against which the engineering document is created |
Revision # |
The revision number of the maintenance change request |
ATA # |
The ATA chapter, on which the engineering document must be performed. |
Eng. Doc Category |
The category to which the engineering document belongs. |
Subject |
The textual description of the engineering document. |
Enter the following:
Select All |
Check this box to select all the engineering documents in the multiline for bulk releasing or canceling. |
Enter the following field if you wish to release or cancel the engineering document:
Release / Cancellation Comments |
Any comment pertaining to the release or cancellation of engineering document (Alphanumeric, 255) |
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: You cannot release Engineering Documents that are applicable to the aircraft with record status “Frozen”.
The system ensures the following before releasing the engineering document:
Atleast one task with ‘Conditionally Evaluated?’ field in the ‘Edit Task Details’ page set as “No”.
The schedule information (calendar or usage based) for all tasks, which have ‘Prog. Item Type’ and ‘Conditionally Evaluated?’ fields in the ‘Edit Task Details’ page set as “Schedule Tracked” and “No” respectively, when the Engineering Document doesn’t have specific Aircraft or Component effectivity defined.
If tasks with, ‘Conditionally Evaluated?’ field in ‘Edit Task Details’ page set as “Yes” exists,
a) Then if more than one tasks with ‘Conditionally Evaluated?’ field set as “No” exists, then system would ensure that for all the conditionally-evaluated tasks ‘Conditional’ relationship with any other task exists in the ‘Maintain Task Relationship’ activity in the interacting ‘Maintenance Task’ component.
b)If only one task with ‘Conditionally Evaluated?’ field set as “No” exists, then on release of the engineering document, system would establish ‘Conditional’ relationship between that task and all other tasks with ‘Conditionally Evaluated?’ field set as “Yes”.
The “Applicability Group #” must have been defined for Aircrafts/ Components in “Aircraft/ Component Effectivity Details” page. However, this validation is not applicable if only Model #/ Part # are defined for the engineering document.
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 exisits 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.
For the “Improvised” task, if a new revision number is identified, the system updates the revision type of the task depeding 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 “Activie” 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. However, this validation is not applicable if only Model/ Part Effectivity details are only defined in the engineering document.
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:
Work units (task or standard procedure) of the engineering documents with applicability “Engine” or “Component”, if “Direct Execution” is marked as “No”.
Part program of the parts identified under the part effectivity of the selected engineering documents, if the “Update Part Program” is set as “Yes”.
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.
The system updates the sign-off requirements for the sub task as explained below:
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.
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.
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 view authorization committee comments
Select the “View Authorization Committee Comments” link at the bottom of the page, to view the comments.
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.