Maintaining repair scheme

Unified Glossary

Basics of using a typical web page

Using Online Help

This page allows you to can create a repair scheme for the tasks by grouping the tasks based on the need of users, MRO, operator, etc. Tell me more.

The “Maintain Repair Scheme” page appears.

Note: The “Maintain Repair Scheme” page automatically retrieves Operational tasks for the primary task selected in the “Maintain Task Relationship” page.

The system displays the following field:

Date & Time Format

The format in which the date and time fields must be entered. 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 and time format from the “Enterprise Modeling” business component by default.

The system displays the following details in the “Primary Task Details” group box:

Task # / Description

The code identifying the task / textual description of the task.

Base Model #

The number identifying the base aircraft model on which the task can be performed.

Effectivity Control

Use the drop-down list box and select one of the following options to retrieve the related tasks. The system lists the following values:

  • None – Select this option to indicate that the repair scheme is applicable for all the operators, parts or aircraft models.

  • Specific – Select this option to indicate that the repair scheme is applicable for a specified operator, part or aircraft model.

By default, the system displays “None”. However, if this page is accessed from another activity, effectivity control is set to “None”, if no part, aircraft model or operator is defined for the task in the previous page. Conversely, effectivity control will be “Specific”, if a part, an aircraft model or an operator is specified for the task.

The system displays the following fields for you to enter, only if the “Effectivity Control” is selected as “Specific”. You must specify values in one of the fields.

Operator Code

Use the drop-down list box to specify the code identifying the airline operator. The system lists all the ‘Active’ operator codes defined in the “Common Master” business component. The operator code selected must be effective for the Primary Task #, as defined in the current business component.

The system leaves the field blank, by default.

Maint. Object #

The maintenance object for which the task is applicable. The system displays one of the following values based on the applicability of the task:

  • “Aircraft Model #”, if the Applicability of the task in the header in “Aircraft”. Enter a valid Aircraft Model # defined in the “Aircraft” business component, in the box provided alongside. The Aircraft Model # entered must be effective for the Primary Task # in the header.

  • “Part #”, if the Applicability of the task is other than “Aircraft”. The Part # entered  must be a valid part defined in the “Part Administration” business component. The part # must be effective for the Primary Task # in the header, as defined in the current business component.

Effective for Alternates

Use the drop-down list box to specify whether the repair scheme is applicable for parent part alternates. The system lists the values ‘yes’ and ‘No’. The system displays the value ‘No’, by default .

Note: This field is enabled only if the ‘Effectivity Control’ field is chosen as 'Specific'.

Note: 1) For the Primary Task #, the system retrieves all the related tasks which are in “Active” or “Fresh” status from the task relationship defined in the current business component. 2) The system automatically displays details of the task selected in the previous page thus making the search function needless.

Work Center #

Use the drop-down list box to select the work center in which the task must be executed. The system lists all the ‘Active’ work centers with ‘Work Center Class’ set as “Reference” in the “Work Center” business component. If none of the Work Center # is defined with ‘Work Center Class’ as "Reference", the system lists all the ‘Active’ work centers with "Work Center Class" set as "Execution".

The system leaves the field blank, by default.

Repair Classification

Use the drop-down list box to specify the classification in order to differentiate the tasks which are over and above the contract between the operator and the MRO. The system lists all the ‘Active’ quick codes of type “Repair Classification” defined in the current business component.

The system leaves the field blank, by default.

Repair Agency #

The code identifying the repair agency to which the part must be sent for repair. (Alphanumeric, 45). The repair agency entered must be an ‘Active’ Supplier # defined in the “Supplier” business component.

Help facility available.

Maint. Type

Use the drop-down list box to specify the type of maintenance work to be carried out on the part. The system lists the following values:

  • “Overhaul”  - Select this option to indicate that the part need to be overhauled.

  • “Repair” - Select this option to indicate that the part need to be repaired to rectify to the discrepancies reported.

  • “Inspection” - Select this option to indicate that the part needs to be inspected.

  • “Others” - Select this option to indicate that the part will be subjected to any other maintenance work.

  •  “Retire” - Select this option to indicate that the part needs to be retired from further usage.

The system leaves the field blank, by default.

Repair Basis

Use the drop-down list box to select the basis on which the repair scheme is acquired or modified for the execution of the task. The system lists the following values:

  • “OEM” – Select this option to indicate that the repair scheme is given by the Original Equipment Manufacturer (OEM).

  • “MRO specific”  - Select this option to indicate that the repair scheme is modified based on MRO need.

  • “Operator specific” – Select this option to indicate that the repair scheme is modified based on operator need.

By default, the system displays “OEM”.

Mandatory?

Use the drop-down list box to specify whether the execution of the task is mandatory or not. The system lists the following values:

  • “Yes” – Select this option to indicate that the execution of the task is mandatory.

  • “No” – Select this option to indicate that the execution of the task is not mandatory.

  • “One Time” – Select this option to indicate that the execution of the task is mandatory for the first time.

By default, the system displays “No”.

Execution Phase

Use the drop-down list box to specify the execution phase of the task. The system lists all the quick codes of type “Execution Phase” defined in the current business component.

The system leaves the field blank, by default.

Prime Part Group Appl. ?

Use the drop-down list box to specify whether the repair scheme is applicable for the parts having the same prime part number. Prime part is the part, which is most widely used and is latest in the group of alternate parts. The system lists the values “Yes” and “No”.

By default, the system displays “Yes”.

TAT (Days)

The turn around time (TAT) required to complete the task. (Alphanumeric, 13). Ensure that a positive integer greater than zero is entered here.

Remarks

Any additional comments related to the repair scheme. (Alphanumeric, 255).

On invoking the “Get Details” pushbutton, the system retrieves the repair scheme details into the multiline, as follows:

Task Control #

The master sequence number for the execution of the tasks. (Alphanumeric, ). A positive integer greater than zero must be entered here. The Task Control # must not be repeated in the multiline.

Related Task #

The code identifying the related task for the task specified in the header. (Alphanumeric, ). Mandatory. The task # entered must be a valid task defined in the current business component.

Note: 1) The related task must be effective for the operator code of the parent task. 2) The Operations Type attribute of the related task must be the same as that of the parent task.

Help facility available.

The system displays the following field:

Relationship Type

Indicates the type of relationship between the primary task and the related task. The valid options are  "Block Schedule", "Concurrent - Group", "Concurrent - Specific", "Concurrent - Conditional" and "Predecessor Constrained".

Effective for Alternates

Use the drop-down list box to specify whether the repair scheme is applicable for child part alternates. The system lists the values ‘yes’ and ‘No’. The system displays the value ‘No’, by default.

Child Position #

The position in which the task is executed. (Alphanumeric, 25).

Child Part #

The code identifying the child part. (Alphanumeric, 40). This field must be left blank, if the related task has Task Applicability set as “Aircraft”. If the Task applicability is “Component” or “Engine”, the part number entered here must be effective for the related task, as defined in the current business component.

Help facility available.

The system displays the “Child Mfr. Part” # and “Mfr. #” fields for you to enter, if the parameter “Enable Manufacturer Part # control in transaction” for the Category ‘Manufacturer Part’ is set as “Yes” in the “Set Inventory Process Parameters” activity of the “Logistics Common Master” business component.

Child Mfr. Part #

The number assigned to the child part, by the manufacturer of the part. (Alphanumeric, 40). This field must be left blank, if the related task has Task Applicability set as “Aircraft”. If the Task applicability is “Component” or “Engine”, the part number entered here must be effective for the related task, as defined in the current business component.

Help facility available.

Mfr. #

The code identifying the manufacturer of the child part. (Alphanumeric, 45).

You must enter the appropriate manufacturer number in this field, if Child Manufacturer Part # is entered and,  if more than one Manufacturer # is available for the Child Manufacturer Part # specified.

Help facility available.

Prime Part Group Appl. ?

Use the drop-down list box to specify whether the repair scheme is applicable for the parts having the same prime part number. The system lists the values “Yes” and “No”.

By default, the system displays “Yes”.

Maint. Type

Use the drop-down list box to specify the type of maintenance work to be carried out on the part. The system lists the following values:

  • “Overhaul”  - Select this option to indicate that the part need to be overhauled.

  • “Repair” - Select this option to indicate that the part need to be repaired to rectify to the discrepancies reported.

  • “Inspection” - Select this option to indicate that the part needs to be inspected.

  • “Others” - Select this option to indicate that the part will be subjected to any other maintenance work.

  • “Retire” - Select this option to indicate that the part needs to be retired from further usage.

The system leaves the field blank, by default.

Execution Facility

Use the drop-down list box to specify the location where the part can be repaired. The system lists the following values:

  • “In-House” – Select this option if the part can be repaired in the operator’s shop.

  • “Out-Source” – Select this option if the part can be repaired in the third party's location such as an authorized repair shop of the supplier.

  • “In-House & Out-Source” – Select this option if the part can be repaired in the operator’s shop or in the third party’s location.

The system leaves the field blank, by default.

Work Center #

Use the drop-down list box to select the work center in which the task must be executed. The system lists all the ‘Active’ work centers with ‘Work Center Class’ set as “Reference” in the “Work Center” business component. If none of the Work Center # is defined with ‘Work Center Class’ as "Reference", the system lists all the ‘Active’ work centers with "Work Center Class" set as "Execution".

The Work center must be specified, if the “Execution Facility” is set as ”In-House” or “In-House & Out-Source”.

The system leaves the field blank, by default.

Repair Agency #

The code identifying the repair agency to which the part must be sent for repair (Alphanumeric, 45). The repair agency entered must be an ‘Active’ Supplier # defined in the “Supplier” business component. Data entry in this field is mandatory, if the “Execution Facility” is set as ”Out-Source” or “In-House & Out-Source”.

Help facility available.

Std. Disposition

Use the drop-down list box to specify the type of work performed on the part. The system lists the following values:

  • “Repair” – Select this option to specify that the part is repaired internally.

  • “Replace” - Select this option to specify that the part must be replaced.

  • “Exchange” – Select this option to specify that the part needs to be exchanged.

  • “Ext. Repair” – Select this option to specify that the component must be repaired externally.

The system leaves the field blank, by default.

Repair Classification

Use the drop-down list box to specify the classification in order to differentiate the tasks which are over and above the contract between the operator and the MRO. The system lists all the ‘Active’ quick codes of type “Repair Classification” defined in the current business component.

The system leaves the field blank, by default.

Execution Priority

Use the drop-down list box to specify the priority of execution of the task. The system lists the descriptions of all the priority numbers which are in ‘Active’ status as defined in the “Common Master” business component. The values are listed in the ascending order of the priority numbers.

The system leaves the field blank, by default.

Mandatory?

Use the drop-down list box to specify whether the execution of the task is mandatory or not. The system lists the following values:

  • “Yes” – Select this option to indicate that the execution of the task is mandatory.

  • “No” – Select this option to indicate that the execution of the task is not mandatory.

  • “One Time” – Select this option to indicate that the execution of the task is mandatory for the first time.

By default, the system displays “No”.

Routing Req.?

Use the drop-down list box to specify whether shop work order must be created for the execution of the tasks. The system lists the following values:

  • “Yes” – Select this option to indicate that the shop work order must be created.

  •  “No” – Select this option to indicate that the shop work order need not be created for the execution of the tasks.

The system leaves the field blank, by default.

Routing Sheet Updates

Use the drop-down list box to specify whether the shop work order is created automatically or manually. Data selection in this field is mandatory, if “Routing Req.?” drop-down list box is set as “Yes”. The system lists the following values:

  • “Automatic” – Select this option to specify that the shop work order is created automatically.

  •  “Manual” – Select this option to specify that the shop work order is created manually in the “Plan Work Order” page of the “Shop Work Order” business component.

The system leaves the field blank, by default.

Execution Phase

Use the drop-down list box to specify the execution phase of the task. The system lists all the Quick Codes of type “Execution Phase” defined in the current business component.

The system leaves the field blank, by default.

Est. Elapsed Time

The total time estimated for completing the task. (Decimal). The time entered here must be a positive value greater than zero.

Time UOM

Use the drop-down list box to specify the time unit for the estimated elapsed time. The system lists the values “Days”, “Hours” and “Minutes”.

By default, the system displays “Hours”.

Rel. Task Lag (Days)

The time lag (in days) in completing the task. (Integer). Ensure that a positive integer greater than zero is entered here.

Schedule Relationship

Use the drop-down list box to specify the sequence in which the related tasks must be executed. The system lists the following values:

  • “Start-Start”

  • “Start-Finish”

  •  “Finish-Start”

  • “Finish-Finish”

For example, if the relationship between the task T1 and T2 is “Finish– Start”, this indicates that T2 can commence only if the primary task T1 has been completed.

The system leaves the field blank, by default.

Base Model #

The number identifying the base aircraft model on which the task can be performed. (Alphanumeric, 30). The Base Model # must be a valid Aircraft Model # defined in the “Aircraft” business component. It must be effective for the Primary Task # as defined in the current business component.

Entry in this field is mandatory if the Task # entered has multiple Base Model # in the current business component.

If the Related Task # is defined with Aircraft applicability and if the Base Model # is entered, ensure that the Related Task # - Base Model # combination exists in the current business component.

Help facility available.

The system displays the following fields:

Parent Task

The code identifying the parent task for the child tasks.

Created By & Date

The employee code of the login user who created the repair scheme details and the date on which the repair scheme details were created.

Last Modified By & Date

The employee code of the login user who last modified the repair scheme details and the date on which the repair scheme details were last modified.

If you wish to insert tasks in the multiline and assign sequence number for them, click the “Re Number” pushbutton to rearrange the existing rows in the ascending order of the sequence number. The system regenerates the sequence number in multiples of five, thereby enabling you to specify the sequence number for the newly added task.

  1. If no task is selected in the multiline, the system retrieves all the child related tasks.

  2. If a task is selected in the multiline, the system retrieves the child related tasks specific to the selected task, with Execution relationship defined as “Concurrent Group”, “Concurrent Specific” and “Concurrent Conditional”.

The “Predecessor Constrained” tasks will not be retrieved in the multiline. The count of the child related tasks is displayed as “Unprocessed Rel. Task”.

Unprocessed Rel. Task:

For the related tasks retrieved in the multiline, the system identifies all the child related tasks with Execution relationship defined as “Concurrent Group”, “Concurrent Specific” and “Concurrent Conditional”. The related tasks which are already available in the multiline are eliminated and the remaining number of child tasks is displayed as “Unprocessed Rel. Task”.

Example:

Let the Primary Task be ‘T1’ in the Repair Scheme.

Let the Related Tasks retrieved in the multiline be ‘T2’, ‘T3’ and ‘T7’.

If the Related Task ‘T2’ has its child tasks as ‘T3’, ‘T4’ and ‘T5’, the “Unprocessed Rel. Task” is displayed as 2. (i.e. T4, T5). (The child task ‘T3’ is not considered because it is already available in the multiline).

Note: When the related task is deleted from the multiline, all its child tasks also get deleted.

Note: The system displays an error message, if any other concurrent user attempts to update the repair scheme details.

Note: If the process parameter “Automatic update of Task-Part effectivity based on Repair Scheme Definition” is set as ‘1’(Required) in the Define Process Entities activity of the Common Master business component, then the system automatically updates the effectivity list of the child Task(s) with the Position Part # and its alternate Part # if they do not exist already.

If the process parameter “Automatic update of Task-Part effectivity based on Repair Scheme Definition” is set as ‘1’(Required) in the “Define Process Entities” activity of the “Common Master” business component and ‘Effective for Alternates’ is selected as ‘Yes’ in the “Task Detail” section, then the system automatically updates the effectivity list of the Repair Scheme Task with this specific repair scheme Part # and its alternate Part # if they do not exist already.

If the process parameter “Automatic update of Task-Part effectivity based on Repair Scheme Definition” is set as ‘1’(Required) in the “Define Process Entities” activity of the “Common Master” business component and ‘Effective for Alternates’ is selected as ‘Yes’ in the “Repair Scheme Details” multiline, then the system automatically updates the effectivity list of the child Task with this child Part # and its alternate Part # if they do not exist already.

The system generates Task Control #, on addition of new tasks.

The system creates a repair scheme for the tasks, if the task relationship with the primary task is already defined in the “Maintain Task Relationship” page. If the relationship does not exist with the primary task, system creates “Concurrent – Specific” relationship between the primary task and the related task for creating the repair scheme.

To proceed

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Maintain Repair Scheme – An overview

Maintain Task Relationship - A summary of the activity

In this page, you can create a repair scheme for the tasks by grouping the tasks based on the need of users, MRO, operator, etc. Grouping of the tasks can be done at model level or part level. You can specify the sequence in which the tasks must be executed. You can also specify the execution priority of the tasks and select the work center in which the task must be executed.

You can retrieve repair related tasks which are specific or not specific for any Operator Code or Maintenance Object (Aircraft Model # or Part #). You can specify various details of the task such as Relationship Type, Child Position #, Child Part #, Manufacturer #, Execution Facility for the repair of the part, Work Center in which the task must be executed, Repair Classification, Execution Priority, etc.

This page facilitates the user to perform the following:

You can insert tasks in the multiline and assign sequence number for them, by clicking the “Re Number” pushbutton to rearrange the existing rows in the ascending order of the sequence number. The system regenerates the sequence number in multiples of five, thereby enabling you to specify the sequence number for the newly added task.

For the related tasks retrieved in the multiline, you can retrieve all the child related tasks with Execution relationship defined as “Concurrent Group”, “Concurrent Specific” and “Concurrent Conditional”. The count of the tasks retrieved is displayed as “Unprocessed Rel. Task”.