This page allow you can also specify the regulatory authority that has approved the change request. Tell me more.
Select the “Process Change Request” link at the bottom of the “Select Change Request” page.
The “Process Change Request” page appears.
Note: This page will not be launched for MCR of “Fresh” status if the “MCR Processing Option" for the chosen MCR “Source Doc. Type” is set as "Post Confirmation" in the “Common Masters” business component interacting with the current login OU,
The system displays the following:
Date Format |
The format in which the date fields must be entered in this page. This format is displayed from the "User Preferences" business 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 fields in the “MCR Details” group box:
Process. Ref. # |
The number identifying the MCR # and Revision # combination. |
Process. Ref. Status |
The system displays any one of the following statuses of the Process Ref. #.:
|
Change Request # |
The change request number for which the process change request page is launched. |
Revision # |
The revision number of the change request if any. |
Subject |
The textual description of the change request. |
Source Doc. Type |
The type of the modification document or the source document of the change request. |
Mandatory? |
Indicates whether the engineering change must be effectively executed on the part # - serial # on which MCR is applicable. The drop-down list box displays No and Yes. |
Reliability Impact?
|
Indicates whether the part # - serial # impacted by the engineering change must be taken into consideration for component reliability analysis. The drop-down list box displays No and Yes. |
Enter the following fields in the “Processing Details” group box :
Execution Decision |
Use the drop-down list box to select any one of the following options:
The system leaves the field blank by default. This field is mandatory. |
Reason for Non- Execution |
Use the drop-down list box to select the reason for non-execution. The system lists all the "Active" quick codes defined against the "Reason for Non-Execution" quick code type in the “Engineering Document” business component. The system leaves the field blank by default. This field is mandatory only if you selected the “Execution Decision” as “Not to Execute” |
Processing Comments |
Any comments pertaining to the processing details (Alphanumeric, 255). |
Auto-Embodiment Required? |
Select the check box to indicate whether the system must automatically carry out the auto-embodiment of the part. |
Enter the following fields in the “Default Details” groupbox to default the values in the “Effectivity Details” multiline :
Mode of Execution |
Use the drop-down list box to select any one of the following mode of execution:
The system leaves the field blank by default. This field is mandatory. |
Applicable ? |
Use the drop-down list box to select any one of the following options:
The system leaves the field blank by default This field is mandatory if value is not available in the ‘Execution Decision’ dropdown. |
Eng. Doc. # |
The unique identifer of the engineering document (Alphanumeric, 18). |
Action on Rev. Effectivity |
Use the drop-down list box to select the option for copying the aircraft or component effectivity details of the engineering document from the previous revision to the new revision number. The system lists the following options:
The system leaves the field blank by default. |
Reason for Non – Execution |
Use the drop-down list box to select the reason for non-execution. The system lists all the "Active" quick codes defined against the "Reason for Non-Execution" quick code type in the “Engineering Document” business component. The system leaves the field blank by default. |
Category |
Use the drop-down list to select the category to which the engineering document belongs. The system lists all the active quick codes that are of type “Eng. Doc - Category” as defined in the “Create Quick Codes” activity. By default the system leaves this field blank. |
Applicability Notes |
Any notes pertaining to the selection of applicability. |
Enter the following fields in the “User Defined” section.
User Defined 1 |
Additional details on the engineering change. |
User Defined 2 |
Additional details on the engineering change. |
User Defined 3 |
Additional details on the engineering change. |
User Defined 4 |
Use the drop-down list box to select the user defined value. The drop-down list box displays the 'Active' quick codes defined under the quick code type 'User Defined 4' in the Create Quick Codes / Edit Quick Codes screen of Engineering Document. |
User Defined 5 |
Use the drop-down list box to select the user defined value. The drop-down list box displays the 'Active' quick codes defined under the quick code type 'User Defined 5' in the Create Quick Codes / Edit Quick Codes screen of Engineering Document. |
User Defined 6 |
Use the drop-down list box to select the user defined value. The drop-down list box displays the 'Active' quick codes defined under the quick code type 'User Defined 6' in the Create Quick Codes / Edit Quick Codes screen of Engineering Document. |
Enter the following fields in the “Effectivity Details” multiline to add or modify the details:
Note: 1) The system defaults the values in the “Effectivity Details” multiline based on the values entered in the “Default Details” group box. 2) If you replace the default value with the required value in any one of the fields below, the new value entered overrides the defaulted value.3) If the “MCR Applicability” is set as “Aircraft”, a value must exist in the Aircraft Reg # column and the Part # field must be left blank. However, if the ”MCR Applicability” is set as “Engine” or “Component”, a value must be available in the “Part #” & “Serial #” columns in the multiline and the “Aircraft Reg #” field must be left blank.4) The multiline retrieves impacted components from the Impact Assessment documents for which advanced part effectivity has been defined for the MCR, if the process parameter "Update impacted components from impact assessments to PCR on creation of PCR" under the entity Eng. Doc. Type and the entity All Eng. Doc. in the Define Process Entities activity of Common Master set to 1 for Yes.
Aircraft Reg # |
The aircraft registration number for which the change request is applicable (Alphanumeric, 30). Mandatory. The aircraft registration number should have already been defined in the “Create Aircraft Record” activity of the “Aircraft” business component, and the status of the aircraft registration number should be “Active”. Ensure that the aircraft registration number is unique in the multiline. |
Part # |
The part for which the change request is applicable (Alphanumeric, 40). Mandatory. The part number should be unique within the multiline. The part number must have already been defined in the “Create Parts Main Information“ activity of the “Part Administration” business component. Help facility available. |
Note: Ensure that the Part # exists if a value exists for the Serial #.
Serial # |
The serial number of the part for which the change request is applicable (Alphanumeric, 40). Mandatory. The serial number should have already been identified in the “Maintain Maintenance Info. For Part” of the “Aircraft” business component and the serial number should be in “Active” status. Ensure that the serial number is unique in the multiline. Help facility available. |
Note: It is mandatory to ensure that a value exists in the Aircraft Reg # or the Part # and Serial #
Applicable ? |
Use the drop-down list box to select any one of the following options:
The system leaves the field blank by default |
Note: It is mandatory to select a value from the Applicable? drop-down list box, if a value exists for the Aircraft Reg # or Part # and Serial #.
If the “Execution Decision” field value is set as “Not to Execute” in the “Processing Details” group box, the value for “Applicable ?” drop-down list box must be set to “No” for all the records in the multiline.
If the “Execution Decision” field value is set as “Hold” in the “Processing Details” group box, the value for “Applicable?” drop-down list box must be set to “Hold” for all the records in the multiline.
Mode of Execution |
Use the drop-down list box to select any one of the following mode of execution:
The system leaves the field blank by default. |
Note: It is mandatory to select the Mode of Execution, If the “Execution Decision” is set as “Yes” in the multiline. However, “Mode of Execution” cannot be selected, if the “Execution Decision” is set as “No” or “Hold” in the multiline.
Eng. Doc Type |
Use the drop-down list box to select the Engineering Document 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. If a value is not selected against any maintenance object, system defaults this list box with the ‘Default Eng. Doc #’ defined for the ‘Source Doc. Type’ of the MCR. The system leaves the field blank by default. |
Category |
Use the drop-down list to select the category to which the engineering document belongs. The system lists all the active quick codes that are of type “Eng. Doc - Category” as defined in the “Create Quick Codes” activity. Data entry in this field is mandatory if in the “Edit Document Type Attributes” page:
The system defaults the previously saved value if any, else leaves this field blank. |
Eng. Doc # |
The unique identifier of the engineering document (Alphanumeric, 18). It is mandatory to enter a value in this field if the “Mode of Execution” field is set to “Existing Eng. Doc #” or “Revised Eng. Doc #”. Help facility available |
Eng. Doc. Appl. Group # |
The number identifying the engineering document applicability group (Alphanumeric, 5) |
Action on Rev. Effectivity |
Use the drop-down list box to select any one of the following options:
|
Disposition Code |
Use the drop-down list box to select the disposition code applicable for the part # - serial # impacted by the engineering change. The drop-down list box displays the ‘Active’ quick codes defined under the quick code type “Disposition Code” in the Create / Edit Quick Codes activity of Engineering Document. |
Disposition Remarks |
Additional details regarding disposition of the part # - serial # impacted by the engineering change. |
Restricted? |
Use the drop-down list box to indicate whether the part #- serial # impacted by the engineering change can be restricted to specific transactions. The drop-down list box displays No and Yes.
Note: All restriction codes specified for the applicability group will be removed, if you modify or delete the option in this field. |
Restriction Code |
Use the drop-down list box to select the restriction code for the part # - serial # impacted by the engineering change. The drop-down list box displays the Active entities defined under the entity type Restriction Code in the Define Process Parameters activity of Common Master. Note: This field is mandatory, if you have selected Yes in the “Restricted?” field. |
Restriction remarks |
Additional details regarding restricted usage of the part # - serial # impacted by the engineering change. Note: This field is mandatory, if you have selected Yes - Generic in the “Restricted?” field. |
Reason for Non-Execution |
Use the drop-down list box to select the reason for non-execution. The system lists all the "Active" quick codes defined against the "Reason for Non-Execution" quick code type in the “Engineering Document” business component. The system leaves the field blank by default. It is mandatory to select a value, if the Applicability is set to “No” for the aircraft or part # and serial #. |
Applicability Notes |
Any notes pertaining to the selection of applicability (Alphanumeric, 255). |
Processing Comments |
Any comments pertaining to the processing details (Alphanumeric, 255). |
The system displays the following:
Eng. Doc Rev # |
The unique identifier of the revised engineering document. |
Eng. Doc Status |
The status of the engineering document. |
The system displays the following on clicking the “Record Assessment” pushbutton:
Effectivity Status |
The system displays any one of the following effectivity statuses:
|
Compliance Status |
The system displays any one of the following statuses:
|
Aircraft Model # |
The number identifying the aircraft model of the ‘Aircraft Reg. #’. |
Eng. Doc Processed ? |
The system displays any one of the following options:
|
Created By |
The login user id of the employee who created the process reference. |
Created Date |
The date on which the process reference was created. |
Last Modified By |
The login user id of the person who last modified the process reference. |
Last Modified Date |
The date on which the process reference was last modified. |
Confirmed By |
The login user id of the person who confirmed the process reference. |
Confirmed Date |
The date on which the process reference was confirmed. |
Enter the following in the “Meeting Details” group box:
Meeting Ref. # |
The unique reference number of the meeting (Alphanumeric, 18). |
Meeting Date |
The date on which the meeting took place (Date Format). It is mandatory to enter the meeting date, if you have entered the meeting reference number. |
Approval # |
The number identifying the approval document (Alphanumeric, 30). |
Approved Date |
The date on which the details of the MCR # and Revision # was approved (Date Format). Ensure that the date entered is in the Date format specified and is earlier than the current server date. It is mandatory to enter the approved date, if you have entered the meeting reference number |
Chair Person |
The name of the chair person in the meeting (Alphanumeric, 255). |
Regulatory Authority |
Use the drop-down list box to select the regulatory authority. The system lists all the "Active" 'Regulatory Authority Codes' defined in the “Common Masters” business component currently interacting with the login OU. The system leaves the field blank by default. |
Members |
The employee codes or the names of the members in the committee (Alphanumeric, 255). Help facility available. |
Comments |
Any comments pertaining to the meeting (Alphanumeric, 255). |
File Name |
The file name associated to the change request (Alphanumeric, 30). Help facility available. |
User Status |
Use the drop-down list box to select the user-defined status of the engineering document. The system lists all the active quick codes that are of type “Eng. Doc - User Status” as defined in the “Create Quick Codes” activity. The system leaves the field blank by default. |
Select the “Record Assessment” pushbutton.
The system updates the following:
If “Process. Ref. #” is not available for the MCR # and Revision # combination, the system generates a Process. Ref. # and updates the “Process. Ref Status” to “Fresh”.
If the “Process. Ref Status” is in “Confirmed” status, the system updates the status to “Fresh”.
The system ensures the following:
The “Eng. Doc Appl. Group #” field value cannot be modified if the “Mode of Execution” is “New Eng. Doc” and the maintenance object (Aircraft Reg. # or Part # - Serial #) details and the “Eng. Doc Appl. Group #” field details are retrieved from the maintenance change request.
If the “Execution Decision” is set as “Execute” and a value is available in the “Aircraft Reg #” or Part # and Serial #, the system ensures that a value is available in the “Applicability” field. However, if no value is available, the system defaults the value specified in the “Default Details” group box.
If the “Execution Decision” is set as "Not To Execute" and a value is available in the “Aircraft Reg #” or Part # and Serial #, the system updates the “Applicability” field with the value “No” irrespective of the value entered by the user.
If the “Execution Decision” is set as "Hold" and a value is available in the “Aircraft Reg #” or Part # and Serial #, the system updates the “Applicability” field with the value “Hold” irrespective of the value entered by the user.
The “Execution Decision” field value cannot be modified if the Eng. Doc Processed ? value is set as “Yes” for a Process Ref # against any one of the maintenance object (Aircraft Reg. # or Part # - Serial #) in the “Effectivity Details” multiline.
The details against the maintenance object (Aircraft Reg. # or Part # - Serial #) cannot be modified if the Eng. Doc Processed ? value is set as “Yes” for a Process Ref # in the “Effectivity Details” multiline.
Select the “Confirm Assessment” pushbutton.
The system ensures the following:
The Process. Ref # is in “Fresh” status.
The details corresponding to the Process Ref # are not modified by another user.
The “Processed” details against the Process. Ref # cannot be modified on confirmation.
If the “Execution Decision” is set as “Execute” and the “Mode of Execution” is set as “New Eng. Doc #”, the system generates a new engineering document of “Fresh” status.
If Eff. From Date Basis of the MCR is set at ‘Maint. Obj. Level’, then the system saves and inherits the ‘Ref. From Date basis’ and ‘Effec. From Date’ of the Maintenance Objects (Aircraft Model #, Aircraft Reg. #, Part #, Component #) applicable for the corresponding MCR # , to the created “Eng. Doc. #”.
The attributes are defined for the “Eng. Doc Type” field in the “Configure Document Attributes” activity of the “Common Masters” business component interacting with the current component in the login OU.
A value must exist in the “Eng. Doc Type” field under the following circumstances:
- If a “Default Eng. Doc Type” field value is not available in the “Common Masters” business component for a “Source Doc. Type” of the MCR, which is being processed .
- If the “Source Doc. Type” of the MCR is not in “Active” status in the “Common Masters” business component.
A value must exist in the “Category” field under the following circumstances:
- The attribute “Numbering Logic” is set as “Confirgured” in the “Edit Document Type Attributes” page of the “ Common Masters” buisiness component.
- The attribute “Include “Eng Doc Type” for Numbering Generation? is set as “1” ie, “Yes” in the “Edit Document Type Attributes” page of the “Common Masters” business component.
If the “Mode of Execution” is set as "New Eng. Doc" and the “Numbering Logic” attribute is set as “Manual” for the “Document Type” in the “Configure Document Attributes” page in the “Common Masters” business component, a value must exist in the “Eng. Doc #” field
If the “Mode of Execution” is set as "New Eng. Doc" and the “Numbering Logic” attribute is set as “Automatic” for the “Document Type” in the “Configure Document Attributes” page in the “Common Masters” business component, the system generates the number in the “Eng. Doc # field based on the “Default Numbering Type” defined.
The system updates the following:
The system copies the header details, the Process Reference details, MCR # details, Document Attachment details, Weight-Moment details, Task details, Concurrent Requirements, Configuration details, Reference Details, Publication details, Kit Details, Notes details, Terminated Engineering Document details and Scheduled details to the new engineering document. Also, the system copies the work center details if the “Applicability” for the change request is not “Aircraft” and copies the Priority details as well.
The system copies the “Aircraft” or “Part” effectivity details and the “Applicability Group #” to the new engineering document.
The system updates the Process. Ref # to “Confirmed” status.
If the Eng. Doc Type Attribute, "Auto Task Card Authoring? “ is set as “Yes” in the interacting “Common Master” business component for the selected “Eng. Doc Type”, the system updates and adds the task details applicable to the engineering document.
If the “Execution Decision” is set as “Execute” and the “Mode of Execution” is set as “Revise Eng. Doc #”, the system generates a new Revision # for the engineering document and updates the engineering document to “Fresh” status.
If the “Action on Rev. Effectivity” is set as “Recomply”, the system updates the following:
The new revision # is generated by copying the effectivity details from the previous revised engineering document to the new revised engineering document irrespective of whether the engineering document was complied on the maintenance object (Aircraft Reg. # or Part # - Serial #)or not.
The system updates the “Compliance Status” as “Pending” for all maintenance objects(Aircraft Reg. # or Part # - Serial #) that are being copied. The Task details, Schedule Details, Configuration Details, Concurrent Requirments, Reference Details, Publication Details, Notes Details, Resource Details and Kit Details are also copied to the new revised engineering document.
The system updates the “Eng. Doc Processed?” Status as "Yes" where the “Applicable?” field value is set as "Yes" for the maintenance object (Aircraft / Part # - Serial #).
The system updates the “Eng. Doc Processed?” Status as "No" where the “Applicable?” field value is set as "No" or “Hold” for the maintenance object (Aircraft / Part # - Serial #)
If the “Action on Rev. Effectivity” is set as “Carry Over Compliance”, the system updates the following:
The new revision # is generated by copying the effectivity details from the previous revised engineering document to the new revised engineering document irrespective of whether the engineering document was complied on the maintenance object (Aircraft Reg. # or Part # - Serial #)or not.
The system retains and copies the “Compliance Status” existing in the previous revised engineering document to the new revised document. The Task details, Schedule Details, Configuration Details, Concurrent Requirements, Reference Details, Publication Details, Notes Details, Resource Details and Kit Details are also copied to the new revised engineering document.
The system updates the “Eng. Doc Processed?” Status as "Yes" where the “Applicable?” field value is set as "Yes" for the maintenance object (Aircraft / Part # - Serial #).
The system updates the “Eng. Doc Processed?” Status as "No" where the “Applicable?” field value is set as "No" or “Hold” for the maintenance object (Aircraft / Part # - Serial #)
The system updates the “Process. Ref. Status” to “Confirmed” status.
The system updates the “Confirmed By” field with the logged in user name and the “Confirmed Date” field with the current date.
The system updates the Status to “Processed”.
The restriction codes mapped to an applicability group will be deleted, if the Restricted? flag for an applicability group is modified/deleted.
To proceed, carry out the following
Select the “Edit Terminated Change Requests” ink at the bottom of the page to edit terminated change requests.
Select the “View MCR Information” link at the bottom of the page to view the details of the MCR selected in the “Selection of Maintenance Change Request” page .
Select the “View MCR Aircraft Effectivity Details” link at the bottom of the page to view the aircraft effectivity details of the MCR.
Select the “View MCR Part Effectivity Details” link at the bottom of the page to view the part effectivity details of the MCR.
Select the “View MCR Part Serial Effectivity” link at the bottom of the page to view the part serial effectivity details of the MCR.
Select the “View MCR Conditional Effectivity Details” link at the bottom of the page to view the effectivity details of the MCR.
Select the “Evaluate Change Request” link at the bottom of the page to evaluate the change request.
Select the “View Change Request Cost Benefit Analysis” link at the bottom of the page to view the change request cost benefit analysis.
Select the “Track Maintenance Compliance History” link at the bottom of the page to view the details of completion of the task(s) for a maintenance object (aircraft or component)
Select the “Edit Engineering Document” link at the bottom of the page to modify the details of an engineering document.
Select the “Upload Documents” link at the bottom of the page to upload the documents against the Process Change Request.
Select the “View Associated Doc. Attachments” link at the bottom of the page to view the documents associated to the Process Change Request.
Select the “View Customer List” link to view the customers associated with the MCR # / Revision # referenced to the PCR.
Select the “Manage Cust. Specific Restriction” link to manage the customer specific restriction of components.
Processing change request – An overview
The proposed engineering change is first evaluated by a management committee comprising representatives from engineering, maintenance planning, material planning and production planning, and in certain cases, a representative of the local regulatory authority.
The system displays the change requests selected in the “Select Change Request” page.
You can assign a user-defined status for the change requests and record the decision on whether the engineering change must be executed or not. The decision is taken after an extensive cost benefit analysis and evaluation of the safety and reliability implications.
You can also specify the regulatory authority that has approved the change request, the approval document number, approval date and any comments pertaining to the processing of the change request.
You can also retrieve the MCRs, which are identified as concurrent requirements (for the change requests) in the “Maintenance Change Request” business component, and process them.
Record MCM decision on executing the change request
Specify the mode of execution of the change request
Retrieve related change requests
Record MCM decision on executing the change request
You can record the decision taken by the MCM regarding the execution of the change request.
In the “Change Request Details” multiline,
Set the “MCM Decision” field to “Execute”, if the MCM has decided to execute the change request.
Set the “MCM Decision” field to “Not to Execute”, if the MCM has decided not to execute the change request.
Set the “MCM Decision” field to “Hold”, if the MCM has decided to hold the execution of the change request.
Specify the mode of execution of the change request
You can specify the mode in which the change request must be executed.
If the change request document is of type “MCR”, set the “Mode of Execution” field to “Engineering Document” or “FCD”, to execute the change request as Engineering Document or Campaign Directive.
Retrieve related change requests
You can retrieve MCRs that have been identified as concurrent requirements (in the “Maintenance Change Request” business component) for the change request selected in the multiline.
Check the box in the “Select” column of the multiline to select the change request.
Click the “Get Related Change Requests” pushbutton to retrieve the related change requests.