Entering component removal-installation details

You can use this tab to enter/modify the component removal and installation details.

• Select the “Removal/Installation Details” tab in the “Update Component Replacement Details” page.

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

Note: The system displays the details of the “Removed Part #”, “Removed Serial #”, “Component #” and its NHA details for the “Aircraft Reg #” and “Position Code” combination, as retrieved from the “Configuration” business component.

To perform a component removal transaction

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

Note: If the source document is Hangar, Line or Component work order, then the “Planned Start Date” and "Planned Start Time" are considered for the default replacement date and time. If the source document is Technical Log, then the “Reporting Date” and "Reporting Time" are considered as the default replacement date and time.

Note: The system ensures the following:

1. If the attachment status of the position code is other than “Unknown”, the removal date and time must be later than the previous installation date and time of the removed component as available in the configuration history.

2. The removal date and time must  be earlier than the installation date and time of the installed component.

3. The removal date and time must be later than the journey log creation date and time, as available in the “Flight Log” business component.

4. The removal date and time must be later than the induction date of the component, as available in the “Aircraft” business component.

5. The removal date and time must be later than the initialization date and time of the removed component parameter value as available in the parameter value history, in the “Aircraft” business component.

If any of the above conditions are not satisfied, then the system will generate an error log, which can be viewed by clicking the “Error Log” tab in this page.

• Enter the following fields in the “Removal Reason Details” group box:

• Click the “Create CR” pushbutton in the main page, to create the component replacement transaction.

Note: The system will not allow two or more users to simultaneously update the same component replacement details, for the same part number.

The system performs the following:

• The system generates the component replacement transaction number, as a serial number prefixed and suffixed by the prefix and suffix defined for the selected “Numbering Type” and sets the status of the transaction as “Fresh”.

• If discrepancies have been reported against the removed part number, serial number or component number in the “Discrepancy Processing” business component, the system retrieves these details and stores it against the component replacement transaction number.

• If the “Reason #”, “Removal Type” and “Basic Removal?” details are entered, then the system updates the CR document with the defined values.

• Allows component replacement despite invalid installed part/component data and generates error records in the Error log, if the "Permit Error Logging of Component Replacement" in the Set Options activity is set to "Yes" and the Record Mode is set to “Error”. Tell me more

For more information, see “View Error Log Details” page.

Restrictions on part/serial replacement

You cannot attach part #/serial # to a NHA/aircraft during the effective period, if the process parameter “Allow Component Attachment?” for the restriction code of the part #/serial # is ‘No’.

Similarly, you cannot remove part #/serial # from a NHA/aircraft during the effective period, if the process parameter “Allow Component Removal?” for the restriction code of the part #/serial # is ‘No’.

On the contrary, if the restriction code of the part#/serial # allows component attachment/removal, the system proceeds with replacement.

 (You can place restrictions on attachment/removal of part#/serial# in the “Manage Part Restrictions” activity of Aircraft by associating a restriction code that does not allow attachment/removal during the period between Effective From and To dates. Restrictions placed on part # via the restriction code apply to all serial #s of the part. Restrictions can also be placed on a specific serial # or on a range of serial #s of a part. Process parameters of restriction codes determine whether they facilitate component replacement. And these are defined in the “Set Process Parameters” page of “Define Process Entities” activity of Common Master.)

• Click the “Confirm Removal” pushbutton in the main page, to confirm the removal after creating the component replacement transaction.

Note: For an empty position code, you can confirm the component removal only if the attachment status of the position code is “Unknown”.

Note: The system will not allow two or more users to simultaneously update the same component replacement details, for the same part number. Also, the system does not allow removal transaction if the position identified by the specified position code in the aircraft configuration, is empty.

The system performs the following on confirming the removal transaction:

• Ensures that the component replacement transaction is not in “Removed”, “Replaced” or “Cancelled” status.

• If the “Reason #”, “Removal Type” and “Basic Removal?” details are entered, then the system updates the CR document with the defined values.

• If the “Reason #” is entered by the user and the “Removal Type” and / or “Basic Removal?” details are not entered, then, on confirmation of CR, the system updates the “Removal Type” and “Basic Removal?” values with the values defined for the corresponding ‘Reason #’ in the “Maintain Reasons for Removal” activity of the “Common Masters” business component.

• If errors are encountered during the component removal transaction, the system updates the attachment status of the position code to “Error” and the CR status to “Error-Removed”.

• If no errors are encountered during the component removal transaction, the system performs the following:

1. Updates the CR status to “Removed” and sets the “Rem Confirmed By” and “Confirmed Date” fields to the name of the currently logged-in user and the current server date.

2. Updates the “Configuration” business component with the removed part and the serial number for the position code. The configuration details will not be updated, if the attachment status of the position code is “Unknown” or if any other “Error-Removed” or “Error-Replaced” CR exists for the same position code.

3. If the attachment status of the position code is “Unknown”, then on confirmation of removal, the system updates the attachment status of the position code to “Removed” in the “Configuration” business component, only if no other “Error-Removed” or “Error-Replaced” CR exists for the same position code.

4. Updates the condition of the removed component in the “Aircraft” business component.

5. Generates the warranty claim for the removed part and serial number or component number if you have set the “Automatic Generation of Warranty Claim” field to “Yes” in the “Set Options” activity and if the removed part and serial number has a warranty reference number in the "Confirmed" status on the date of removal in the “Component Warranty” business component, and the part number and serial number or the component number are within the warranty period.

6. Generates the warranty claim, when the status of the document is changed from “Fresh”  to “confirmed”.

7. If discrepancies have been reported against the removed part number, serial number or component number in the “Discrepancy Processing” business component, the system retrieves these details and stores it against the component replacement transaction number.

8. If the aircraft assembly is mapped to supplier as “PBH” and the part number that is removed from the assembly is identified as “PBH”, then the system updates the “Ownership” of the component as “Supplier” and “Possession Status” as “PBH”. For the part that is not attached to the aircraft, the system updates the ownership as “Supplier”, if the part that is being removed is a child of a component which is identified as “PBH” and if the serial number for that part is available in the PBH supplier list.

• Allows component replacement despite invalid installed part/component data and generates error records in the Error log, if the "Permit Error Logging of Component Replacement" in the Set Options activity is set to "Yes" and the Record Mode is set to “Error”. Tell me more

• Process Parameter dependency: If the process parameter “Auto Activation/Inactivation of schedule status of  tasks in CMP based on Maint. Operator change?” is set as 1 for Yes under the entity type “Tech. Records Process Ctr” and the entity “Part Prog in the “Define Process Entities” activity of Common Master, the system automatically activates Schedule Status of the tasks mapped to the maintenance operator associated with the component in the maintenance program. Further, Schedule Status of the tasks not related to the maintenance operator will be set as Inactive in the component maintenance program. However, if “Auto Activation/Inactivation of schedule status of  tasks in CMP based on Maint. Operator change?” is set as 0 for No, Schedule Status of the tasks will not be dependent on the maintenance operator.

For more information, see “View Error Log Details” page.

To perform a component replacement transaction

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

The system displays the following field:

Note: If the component replacement has resulted from a technical log or a hangar work order and if the installed part is taken from “Inventory”, ensure that an issue transaction is raised for the part on the source document, before the date of installation.

If the “Check whether assembly status is complete” option is set to “Yes” in the “Set Options” activity, then the system verifies whether the assembly status of the installed serial number is “Complete” in the “Configuration” business component, for all the CR transactions in other than “Error-Replaced” status. If this condition is not satisfied, the system generates an error log.

The system fills in the following field on clicking the “Create CR” pushbutton:

• Enter the following fields. Data entry in these fields is mandatory while clicking the “Confirm Replacement” pushbutton:

• Click the “Create CR” pushbutton in the main page, to create the component replacement transaction.

Note: The system will not allow two or more users to simultaneously update the same component replacement details, for the same part number.

The system generates the component replacement transaction number, as a serial number prefixed and suffixed by the prefix and suffix defined for the selected “Numbering Type” and sets the status of the transaction as “Fresh”.

• Click the “Confirm Replacement” pushbutton in the main page, to confirm the replacement details after creating the component replacement transaction.

Note: The system will not allow two or more users to simultaneously update the same component replacement details, for the same part number.

The system performs the following on confirming the component replacement transaction:

• Ensures that the condition of the installed component is "Serviceable" in the “Aircraft“ business component, when the “Source of Installed Comp” is set to “Inventory” or “Cannibalisation”. .  If this condition is not satisfied, the system generates an error log.

• Ensures that the installed part number and serial number is not attached to any position code as on the current system date. If it is attached to any position code, the system generates an error log.

• Ensures that the component replacement transaction is not in “Cancelled” or "Replaced" status, while confirming the component replacement.

• If a value exists in the “Component #”, “Part #” and “Serial #” fields, then the stock quantity of the part number and serial number  or component number should be “Nil” in the “Stock Maintenance” business component.  If this condition is not satisfied, the system generates an error log.

• If the “Reason #”, “Removal Type” and “Basic Removal?” details are entered, then the system updates the CR document with the defined values.

• If the “Reason #” is entered by the user and the “Removal Type” and / or “Basic Removal?” details are not entered, then, on confirmation of CR, the system updates the “Removal Type” and “Basic Removal?” values with the values defined for the corresponding ‘Reason #’ in the “Maintain Reasons for Removal” activity of the “Common Masters” business component.

• If the part / serial # is attached to aircraft or component and if the Object Type is “Component”, then on confirmation of the component replacement transaction, the system updates the Maintenance Issue document to specify that the issued part / serial # is attached. This is applicable only if the “Consumed?” drop-down list box is set as “Yes” or “Yes - Without Core” in the “Report Component Consumption Information” page of the “Component Work Reporting” business component.

• If errors are encountered during the confirm replacement transaction, the system updates the attachment status of the position code to “Error” and the CR status to “Error-Replaced”.

• If no errors are encountered during the component replacement transaction, the system performs the following:

1. Sets the status to “Confirmed Replacement” and sets the “Repl Confirmed By” and “Rem Confirmed By” fields to the name of the currently logged in user. Also, the “Rem Confirmed Date” and “Confirmed Date” fields are set to the current server date.

2. Updates the “Configuration” business component with the installed part and the serial number for the position code. The system also updates the attachment status of the position code as “Attached”. The configuration details will not be updated if the record mode is set as “Error” or if the same position code exists with attachment status “Error” in any other component replacement transaction.

3. If the status of the component replacement transaction is “Removed”, the system updates the removal details in the “Configuration” business component and in the replacement history.

4. Generates the warranty claim for the removed part and serial number if you have set the “Automatic Generation of Warranty Claim” field to “Yes” in the “Set Options” activity, and if the part number and serial number has a warranty reference number in the “Confirmed” status on the date of removal in the “Component Warranty” business component, and the component is within the warranty period.

5. Generates the warranty claim when the status of the document is changed from “Fresh” to “Confirmed”.

6. If a component is attached to the aircraft, the system udpates the ownership of the component as “Owned” and possession status as blank, in the “Aircraft” business component.

7. If the aircraft assembly is mapped to supplier as “PBH” and the part number that is removed from the assembly is identified as “PBH”, then the system updates the “Ownership” of the component as “Supplier” and “Possession Status” as “PBH”. For the part that is not attached to the aircraft, the system updates the ownership as “Supplier”, if the part that is being removed is a child of a component which is identified as “PBH” and if the serial number for that part is available in the PBH supplier list.

8. Updates the position formula (if it exists for the attached position) of the component for the new position code, based on the source document type to their respective business components

9. Updates the schedule details of the component in the “Component Maintenance Program” business component with the following:

1. For the components (or any one of the child components) having calendar-based schedule and “Updation Basis” as “Date of Attachment”, the system adds the schedule interval to the current replacement date and updates the resulting value as “Next Schedule Date”, if the “Next Schedule Date” is left blank. The system also updates the attachment date if the “Attachment Date” field is left blank.

2. If the component is attached to an aircraft and if the installed component or any of its child components has position-based schedules  the system adds the position-based interval to the last schedule date/value of the work unit for the respective component in the position.  

3. For usage-based schedule, the system adds the schedule interval to the last performed value and takes the resulting value as “Next Schedule Value”.

Note: The system performs this updation only for those parameters that are common between usage-based schedules for position code and usage-based schedules identified for the component.

For date-based schedule, the system checks the updation basis. If the “Updation Basis” is selected as “Attached Date”, then the system adds the schedule interval to the attached date to obtain the “Next Schedule Date”. If the “Updation Basis” is selected as “Last Performed Date”, then the system adds the schedule interval to the last performed date.

10. Updates the “Warranty Start Date” in the “Create Component Warranty Agreement” activity of the “Component Warranty” business component with the “Installation Date”, if the “Warranty Begins On” field for the component or child component being attached, is set as “Installation Date” in the “Create Component Warranty Agreement” activity of the “Component Warranty” business component.

Note: This update happens only if the “Warranty End Date” is blank.

11. Generates serial number for the “Manufacturer Serial #” and accordingly updates the “Stock Maintenance” business component, if the “Part #” is identified to be serial-controlled.

• Allows component replacement despite invalid installed part/component data and generates error records in the Error log, if the "Permit Error Logging of Component Replacement" in the Set Options activity is set to "Yes" and the Record Mode is set to “Error”. Tell me more

For more information, see “View Error Log Details” page.

• The system retains user-specified NSD/NSV of attached components during inheritance of the position based schedules on the basis of the process parameter ‘Retain manually corrected Next Due Date & Value for the component task when the position based schedule is inherited if LPD & LPV is not available' defined under  the entity type “Next Due Computation Logic” and entity "Maint. Program and Forecasting Options" in the Define Process Entities activity of Common Master. The impact of the process parameter during inheritance is explained here:

• Process Parameter dependency: If the process parameter “Auto Activation/Inactivation of schedule status of  tasks in CMP based on Maint. Operator change?” is set as 1 for Yes under the entity type “Tech. Records Process Ctr” and the entity “Part Prog in the “Define Process Entities” activity of Common Master, the system automatically activates Schedule Status of the tasks mapped to the maintenance operator associated with the component in the maintenance program. Further, Schedule Status of the tasks not related to the maintenance operator will be set as Inactive in the component maintenance program. However, if “Auto Activation/Inactivation of schedule status of  tasks in CMP based on Maint. Operator change?” is set as 0 for No, Schedule Status of the tasks will not be dependent on the maintenance operator.

To cancel a component replacement transaction

• Click the “Cancel CR” pushbutton in the main page to cancel the component replacement transaction.

The system ensures that the component replacement transaction is in “Fresh” status and sets the status of the transaction to “Cancelled”.

Note: The system will not allow two or more users to simultaneously update the same component replacement details, for the same part number.

To proceed carry out the following:

• Select the “Error Log” tab in the main page to view the errors encountered during the component replacement transactions.