Authorizing part program

This page allow you to search for the part program to be authorized by providing filter criteria such as the part. Tell me more.

Select the “Authorize Part Program” link under the “Component Maintenance Program” business component.

The “Authorize Part Program” page appears.

The system displays the following field:

Date Format

The format in which the date fields must be displayed 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 filter criteria in the “Search Criteria” group box to search for a part. Data entry in the following fields is optional:

Part #	The number identifying the part for which the maintenance program details are to be authorized (Alphanumeric, 40). You can enter the part number in full, or specify it partially using the “*” character. The system retrieves all the part numbers that are similar to the value entered here.
Part Description	The textual description of the part (Alphanumeric, 150). You can enter the description in full, or specify it partially using the “*” character. The system retrieves all the parts whose description is similar to the description entered here.
Maintenance Process	Use the drop-down list box to select the maintenance process, which could be “Hard-Time”, “On-Condition” or “Condition Monitoring”. The system retrieves all the parts that are associated with the maintenance process selected here. The system leaves the field blank by default.
ATA #	The ATA chapter to which the part belongs (Alphanumeric, 16). You can enter the ATA chapter number in full, or specify it partially using the “*” character. The system retrieves all the parts whose ATA chapter numbers are similar to the value entered here.

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

Note: The system retrieves the part for which the “Program Defined” field is set as “Yes” and whose status is “Fresh”. If the option setting “Planner Group Security” is set as “Required” in the Set Options activity, then the system retrieves only those parts associated to the Planner group to which the login user has been mapped.

The system displays the following in the “Part Details” group box based on the search criteria specified:

Part #	The part number retrieved by the system.
Part Description	The textual description of the part.
Maintenance Process	The maintenance process of the part which could be “Hard-Time”, “On-Condition” or “Condition Monitoring”.
ATA #	The ATA chapter to which the part belongs.
Program Revision #	The revision number of the part program.
Updated By	The name of the user who updated the part program.
Updated Date	The date on which the part program was updated.

Enter the following:

Select All

Check the box to mark all the part programs displayed in the multiline for authorization.

Click the “Authorize Program” pushbutton to authorize the part program.

Note: On clicking “Authorize Program”, the system pops up a confirmation message ‘Would you like to Authorize Program?” before proceeding the authorization of part program.

The system performs the following on clicking the “Authorize Program” pushbutton:

Sets the status of the selected part program as “Authorized”.
Sets the status of the existing “Authorized” revision number of the Part Maintenance Program to “Revised”.
If a component under the part number does not have a component maintenance program defined, then the system copies the part program as the component maintenance program and sets the status of the program as “Fresh”, if schedules of recurring type are defined for the part program. Otherwise, the system sets the status of the program as ”Authorized”.
Calculates the Next Schedule Date (NSD) and Next Schedule Value (NSV) for ‘One time’ or ‘Recurring’ tasks, based on the value of ‘Reset On Attachment’.

Reset On Attachment	NSD	NSV
Not Required	NSD = Threshold value in Part Program + Component Induction date	NSV = Threshold Value in Part Program
First Attachment	NSD = Threshold value in Part Program + Component Attachment date and time If the component is not attached in an Aircraft, NSD is updated as Blank.	NSV = Threshold Value in Part Program
Every Attachment	NSD = Threshold value in Part Program + Component Attachment date and time If the component is not attached in an Aircraft, NSD is updated as Blank.	NSV = Current Value on attachment date and time + Threshold Value in Part Program

Note: Ensure that the part number of the selected part program is mapped to a restoration work unit in the “Maintain Restoration Work Unit” activity, if there is at least one off-wing work unit in the part program and if the “Parent Removal” flag of the part is set as “Not Required” in the “Maintain Part Program” activity.

If the “Shelf Life Expiry” flag for the work units is set as “Yes” in the “Maintain Component Maintenance Program” activity, the system authorizes the component maintenance program, irrespective of the link information set for the program.

The system ensures that, for each record selected in the multiline, a date-based schedule or a usage-based schedule is defined for the part.

If the Eng. doc reference # exists for the task and if the task attributes are modified, the system allows you to Authorize the Part Program, only if the process parameter “Allow modification of Eng. Doc. task in Maintenance Program” is set as “Allowed” in the “Define Process Entities” activity of the “Common Master” business component.
On authorization of Part Program, system copies the part program as Component Maintenance Program for those components under the part # which does not have a CMP defined yet. The system updates the computation basis controls ‘Next Due Calc. On’, ‘Calc. Ref. Value / Date’ and ‘Last Schedule Date / Value’ in the “Edit Date Based Schedule Information” and “Edit usage Based Schedule Information” page of the current business component as shown in the below table:

Scenario	Next Due Calc. On	Calc. Ref. Date	Last Schedule Date
If NSD is computed based on ‘Manufactured Date’	Mfr. Date	Corresponding Date	Not Applicable
If NSV is computed based on 'Threshold / Interval Value'	Initial Interval	Threshold / Interval Value	Not Applicable
On addition of a task with 'Initiated / Reset by' set as "Related Task Compliance"	Not Applicable	Not Applicable	Not Applicable
If there are no schedules and for tasks with 'Prog. item Type' "To be Decided"	Blank	Blank	Blank

Copying the part program to components

The system copies the part program as the component maintenance program (CMP) for the components (if CMP does not exist) defined under the parts.
Sets the “CMP Defined” field as “Yes” for the components.
If the program does not have any schedules of the "Recurring" type, it sets the CMP status as "Authorized". Otherwise it sets the CMP status as "Fresh".

This matrix illustrates the scenarios of inheritance by component maintenance programs from part programs, if ‘Copy to Components’ flag is set for the part program. However, schedule/NSD/NSV updates are not copied to component maintenance programs for tasks with Position Based schedules.

Process parameter 'Revise Component Maintenance Programs on copying from Part Program?' = No:
CMP status = ’Fresh’	CMP status = ’Authorized’
The system updates part program changes in existing revision as well as the previous revision that exists in ‘Authorized’ status.	The system updates part program changes only in existing revision.
Process parameter 'Revise Component Maintenance Programs on copying from Part Program?' = Yes and process parameter 'Component Maintenance Program status on copying from Part Program' = 'Fresh':
CMP status = ’Fresh’	CMP status = ’Authorized’
The system updates part program changes in existing revision.	The system increments the revision # by 1 and updates part program changes in the new revision created in ‘Fresh’ status.
Process parameter 'Revise Component Maintenance Programs on copying from Part Program?' = Yes and process parameter 'Component Maintenance Program status on copying from Part Program' = 'Authorized’:
CMP status = ’Fresh’	CMP status = ’Authorized’
The system updates part program changes in existing revision.	The system increments the revision # by 1 and updates part program changes in the new revision created in ‘Fresh’ status.

Exceptional scenarios in which the system does not update CMP

If any user has deleted NSD/NSV, the system does not recompute NSD/NSV for tasks, such as below:

(i) If ‘Reset on Attachment’ is ‘Every Attachment’ and, if the task has not yet been complied for the component

(ii) If ‘Initiate / Reset by’ is 'Related Task Compliance’ and if ‘Relationship Type’ of the task is ‘Initiate Schedule’ cyclically with other tasks in the maintenance program

(iii) If the task is a Short Term Escalated task in the CMP.

Copying part program revisions to component maintenance programs

If you have selected the Copy to Components check box, the system inherits the part program revisions to maintenance programs of all components (Both Active and Inactive) associated to the part as explained below:

Inheritance based on Change Type

Change Type

NSD/NSV Re-calculation

Fields updated

Blank / Correction

Yes

§ Next Due Calc. On

§ Calc. Ref. Date / Value

§ Last Schedule Date / Value

Re-baseline

Not Applicable

Revisions changes are committed in both Active and Fresh versions of the component maintenance programs.
Schedule and NSD/NSV changes are not copied to component maintenance programs, if a task has a Position Based Schedule. However, changes in the tasks will be committed to the component programs.
If any task is deleted from the part program, the schedule status of the task in the component maintenance program becomes ‘Inactive’.
If schedule changes are inherited from the part program to CMP regardless of the Active or Inactive status of the task in the CMP. The schedule status of the task in the CM is set to the schedule status of the task in the part program.
The schedule changes made in the task in the part program are no inherited to the task in the CMP, if the schedule statusof the task in the CMP is Terminated.

NSD/NSV will not be recomputed in the following conditions:

For a schedule, if Change Type is Re-Baseline
If NSD/NSV are already deleted for the task with 'Reset on Attachment' as Every Attachment and RTC task in cyclic Initiate Schedule relationship in CMP
If the modified task is Short Term Escalated in CMP, NSD/NSV is not recomputed though Threshold & Interval are updated from the part program.

Short term Escalation impact

On Inheritance, if Schedule Status is Inactive for a task with Short Term Escalation, Short Term Escalation for the task is canceled in the CMP.

Program Item Type impact

If Program Item Type is changed from Block, Base, Non-Block, To be decided to As Required, Perpetual, or To be decided, the CMP will inherit schedule changes made in the part program.

Reset on Attachment impact

On inheritance, if Reset on Attachment is modified in the CMP to	NSD/NSV behavior in CMP
Not Applicable	Is recomputed for all schedules
Every Attachment	Is recomputed if the component is attached to aircraft Is blanked out, if the component is not attached to the aircraft
First Attachment	Usage-Based schedules NSV is recomputed for al schedules Date-Based schedules` § NSD is blanked out, if the component has never been attached to an aircraft or removed for the 1^st time and not yet attached for the second time § NSD is recomputed, if the component has been attached to an aircraft for the 1^st time/2^nd time

Initiated/Reset By impact upon inheritance

Reset on Attachment is modified in PP	NSD/NSV behavior in CMP
From Self Compliance to Related Task Compliance	The system recomputes all schedules of the Data based and Usage based schedules for the task
From any option to Not Applicable	Is recomputed for all schedules of the Data based and Usage based schedules for the task
From any option to Every Attachment	If the component is attached to an aircraft, the NSD/NSV for all the Data based and Usage based schedules is recomputed for the task. If the component is not attached to aircraft, the NSD/NSV for all the Data based and Usage based schedules is recomputed for the task.
First Attachment	For Usage based schedules: · Recomputes NSV for all Usage based schedules of the task. For Date Based Schedule: · Recomputes NSD, if the component is attached to aircraft for the first time / second time · Does not recompute NSD to Blank, if component is not attached to aircraft · Resets NSD to Blank, if the component has been removed from aircraft (not yet attached for 2nd time)

Eng Doc. changes impact

If Eng. Doc. # and Revision # has been changed in the part program, the system decides whether to inherit theses changes in the component maintenance program based on the process parameter 'Allow modification of Eng. Doc. task in 'Maintenance Program'?’ under the entity type Eng. Doc. Type and entity User-Defined document types in the Define Process Entities activity in Common Master.

Process Parameter Value	Impact in the component maintenance program
0/Not Allowed	Source Document Type, Source Document # and Revision # changes from the part program are not inherited by the component maintenance program
1/Allowed	Source Document Type, Source Document # and Revision # changes from the part program are inherited by the component maintenance program only if the component is effective for the engineering document.

Maintenance Type impact

The component maintenance program does not inherit any Active task of Maintenance Type ‘Retire’ from the part program, if it already has an active Retire task.

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 of Common Master, the system updates the maintenance program of the component whose part # has been changed as illustrated below:

Process parameter value	Impact on Inheritance of new part program
1/Yes	The maintenance program of the new part is copied to the component maintenance program. However, If the new part has any PBS, then PBS gets precedence over the new part program.
0/No	The maintenance program of the new part is not copied to the component maintenance program.

To proceed

Click the hyperlinked part number, to update the part program information.

Authorizing part program – An overview

You can search for the part program to be authorized by providing filter criteria such as the part number, description, ATA chapter and maintenance process. The details of the selected part, such as the part number, its description, type, maintenance process, ATA chapter to which the part belongs, part program revision number and the user name of the person who updated the part program and the updated date.

You can authorize the part programs in bulk or select a particular part program to be authorized. The system sets the status of the part program as “Authorized” and stores the name of the currently logged in user and the current server date.

The system also copies the part program as the component maintenance program (CMP) to all the components that are defined under the part. If the program has a schedule of the “Recurring” type or "One-Time" type, the system updates the CMP status of the components as “Fresh”. Otherwise, it sets the status as “Authorized”.