Recording effectivity details

This tab allows you to define effectivity details for the selected Engineering Document. You can define both Aircraft and Part #- Serial # effectivity by specifying a serial range for the Aircraft Model # or Part #. All aircraft of specific Model # or all Components of Part # can be defined as effective. You can also define action of revision at effectivity level, enter previous compliance details and Inactive / Terminate ‘Schedule Status’ of the tasks in the respective programs.

On addition of effectivity, you must ensure that aircraft / component is in "Active" status. At Serial Level, when you add or modify effectivity, the system allows Aircraft / Component saved in previous revision, irrespective of the status.

Select the “Effectivity” tab in the “Manage Eng. Document” page.

Effectivity Level

Auto-Embodiment

Auto-embodiment refers to the process of upgrading an existing part to a new part as per the stipulations of an engineering order. The engineering order typically specifies the tasks that must be executed on the existing part so as to upgrade the part to the new part.

4 However, it must be noted that auto-embodiment will be based on the definition set in the “Edit Recommended Part Effectivity” activity or “Edit Advanced Part Effectivity” activity for the MCR associated with the engineering document.

4The system triggers auto-embodiment for all the serial # of the part # that has been included in Advanced Part Effectivity for the MCR associated with the engineering document based on specific criteria (MSN range, Part # range, Mfr. Date Range and Aircraft Model). The engineering order tasks will be updated in the maintenance programs of the associated components with the schedule in the 'Active' status.

However, if the process parameter "Enable Part level MCR / EO processing?” under the entity type Eng. Doc Type and the entity All Eng. Doc is set as 1 for Yes, the following auto-embodiment happens by default:

o The parts impacted by the advanced part effectivity defined for the MCR associated with the engineering document for which currently serial # do not exist will be retrieved in the multiline of the Effectivity tab.

o Next, the new components of new parts will be auto-embodied based on advanced part effectivity in the MCR on basis of which engineering order is created.

o Auto-embodiment will not be carried out on parts, if Applicability is set as Hold or No.

o On engineering order release, restrictions defined for the parts become applicable for the serial # too.

Select the "Auto-Embodiment Required?" check box to update details of effective components/aircraft activated post engineering document creation.
On check box selection, any new activated component/aircraft activated on which the engineering document must be executed is updated in the document automatically by the system.
Select the “Manage Adv. Part Effectivity” link to record part effectivity for the engineering document. The “Edit Advanced Part Effectivity” popup appears.

Note: The “Edit Advanced Part Effectivity” popup will appear only;

a) If the EO has been created independently without any MCR reference. (If the EO has MCR reference, any update of advanced part effectivity must be carried out in the MCR component only.)

b) If EO Applicability is Component or Engine

c) In the Display-only mode, if you have launched the “Manage Engineering Document” activity in the View mode (selected the View radio button).

d) If the status of the EO# or Rev# is Fresh or Revised and not Released

Note: The “Edit Advanced Part Effectivity” popup will not appear, if part effectivity has already been defined in the serial range for the EO#.

If a MCR # based PCR is created for which ‘Adv. Part effectivity’ is defined in the MCR and, if an existing direct EO # is provided as a reference to the PCR, the system will include the Adv. Part effectivity defined in MCR to the direct EO #.

Select one of the following radio buttons:

At Serial Level

Select this radio button to define effectivity for each Aircraft Reg # / Part # - Serial #. On selecting this radio button, the serial level ‘Effectivity Details” multiline is visible. A drop-down list box ‘'Update Maint. Prog. Template' is displayed below the multiline.

This radio button appears selected, by default.

Serial Range

Select this radio button to define effectivity by specifying a serial range for Aircraft Model # or Part #. All aircraft of specific Model # or all Components of Part # can be defined as effective.

A button 'Display Serial Number' is displayed below the multiline. Click on this button to view the serial range.

Effectivity Details

The system displays the effectivity details in the multiline based on the selection of the radio buttons and the applicability of the Eng. Doc. # in the header. The following fields are displayed for the Eng. Docs of ‘Aircraft’ Applicability.

Effectivity Details - At Serial Level

The system displays the following fields:

The Compliance Status of effectivity of the Aircraft Reg #. The compliance status is represented by various icons as shown below:

- Indicates that the tasks associated to the applicability group are complied.

- Indicates that the tasks associated to the applicability group are yet to be complied against the effectivity and engineering document.

- Indicates that the tasks associated to the applicability group are compiled and are recurring.

- Indicates that the tasks associated to the applicability group are partially complied against the effectivity and engineering document.

- Indicates that ‘Applicable?’ is set as “Previously Complied”

- Indicates that effectivity defined is not applicable for the engineering document. i.e. Applicable? is set as “No”.

- Indicates that ‘Applicable?’ is set as “Hold” for the effectivity.

Note: This field is available only if you have selected the ‘At Serial Level’ radio button

Enter the following details in the multiline:

AC Reg #	The registration number of the aircraft. The aircraft registration number entered here must be defined as ‘Active’ in the “Aircraft” business component. Note: 1) This field is aircraft-specific. 2) Any of the two are mandatory: A/C Reg. # or A/C MSN. Help facility available. Process Parameter Dependency: The aircraft you enter here must be mapped to the maintenance operator tagged to the login user, if the process parameter “Allow addition/modification of Aircraft & Component from other Maint. Operator codes in EO?” is set as "0" for “Not Allowed” under the entity type Eng. Doc Type and the entity “All Eng. Doc” in the Define Process Entities activity of Common Master.
A/C MSN	The manufacturer serial # number of the aircraft. Note: 1) This field is aircraft-specific. 2) Any of the two are mandatory: A/C Reg. # or A/C MSN.
Part #	The part # of the component. Note: This field is component-specific. Help facility available
Serial #	The serial # of the component. Note: This field is component-specific. 2) Either Serial # or MSN is mandatory. Help facility available. Process Parameter Dependency: The serial # / component you enter here must be mapped to the maintenance operator tagged to the login user, if the process parameter “Allow addition/modification of Aircraft & Component from other Maint. Operator codes in EO?” is set as "0" for “Not Allowed” under the entity type Eng. Doc Type and the entity “All Eng. Doc” in the Define Process Entities activity of Common Master.

The multiline displays the following.

Serial Exists?

Indicates whether the serial # of the part/aircraft model is available in inventory or has been phased out of operation.

Enter the following details in the multiline:

MSN	The manufacturing serial number of the component. Note: 1) This field is component-specific. 2) Either Serial # or MSN is mandatory. Help facility available
App. Grp. #	The applicability group of the engineering document. A positive integer must be entered here. If not entered, on save the system defaults “0”.
Applicable?	Use the drop-down list box to specify the applicability of effectivity for the engineering document. The system lists the values “Yes”, “No”, “Hold” or “Previously Complied”, selectively, based on the process parameter ‘Specify values for ‘Applicable?’ set in the “Common Master” business component. "Yes”, “No”, “Hold”, if the process parameter is set as 'Hold'. “Yes”, “No”, “Previously Complied”, if the process parameter is set as “Previously Complied' “Yes”, “No”, Hold”, “Previously Complied”, if the process parameter is set as “Hold” and “Previously Complied”. “Yes”, “No”, if the process parameter is set as 'None'.
Reference Date Basis	Use the drop-down list box to specify the Reference Date basis for the effective from date of the Aircraft Model #/ Part #. The system lists the values “Induction Date”, “Operational Date” and “Manufactured Date” along with a blank value.
Eff. From Date	The date from which the Aircraft Model #/ Part # is effective.
Action on Rev. Effec. ?	Use the drop-down list box to specify the option for copying the effectivity details of the engineering document from the previous revision to the new revision number. This field is displayed, only if the Revision # of the Eng. Doc. in the header is greater than ‘0’. The system lists the following values: “Re-Comply”, "Carryover Compliance”, “Revoke” and “Terminate”, if the Applicability of the Eng. Doc. is “Aircraft”. “Re-Comply”, "Carryover Compliance” and “Revoke”, if the Applicability of the Eng. Doc. is “Engine” of “Component”. By default, the system defaults the values defined for the attribute “Default value for ‘Action on Rev. Effec. ?’ in Effectivity” in the “Common Master” business component. Note: This field is available only if the engineering document is a revision.
Prev. Comp. Doc. #	The code identifying the document that was previously complied.
Prev. Comp. Date #	The date of previous compliance of the engineering document.

The system displays the following field:

Part Change

Indicates whether the EO entails part# change for the component.

Note: This field is component-specific.

Enter the following field below the multiline:

Srl. # Change?	Use the drop-down list box to indicate whether the engineering document entails serial # change for the component. The drop-down list box displays ‘None’ and ‘Specific’. Note: This field is component-specific.
New Srl. #	The new serial # for the component as stipulated by the engineering document. Note: This field is component-specific.
Aircraft Model #	The model number of the aircraft. Note: This field is aircraft-specific. Help facility available
Processing Comments	Any comments related to the effectivity. Data entry in this field is non-mandatory, on addition / modification of effectivity.

The “Effectivity Details” multiline displays the following.

Program Exist?	Indicates whether maintenance program for the aircraft/component is defined in the system..
Program Updated?	Indicates whether the maintenance program for the component/aircraft has already been updated as stipulated in the engineering document.

Created By	The login user who created the record.
Created Date	The date on which the login user created the record.
Modified By	The login user who most recently modified the record.
Modified Date	The date on which the login user most recently modified the record.
Source Document #	The document reference for inducting the component into the inventory, such as Customer Goods Receipt or Goods Receipt.

Effectivity Details - Serial Range

Enter the following fields:

Aircraft Model #	The model number of the aircraft. Mandatory. The model number entered here must be defined as ‘Active’ in the “Aircraft” business component. Note: This field is aircraft-specific. Help facility available.
Part #	The number identifying the part. Mandatory. The part number entered here must be defined as ‘Active’ in the “Aircraft” business component. Note: This field is component-specific. Help facility available.
Include All Srl.	Check this box to retrieve all the serial # of the part # or the aircraft model #. All the serial # of the part # must be mapped to the maintenance operator tagged to the login user, if the process parameter “Allow addition/modification of Aircraft & Component from other Maint. Operator codes in EO?” is set as "0" for “Not Allowed” under the entity type Eng. Doc Type and the entity “All Eng. Doc” in the Define Process Entities activity of Common Master.
A/C MSN From	The starting serial number in the range of serial numbers for the specified part # / aircraft model #. Note: This field is aircraft-specific. Help facility available.
A/C MSN To	The ending serial number range in the range of serial numbers for the specified part # / aircraft model #. Note: This field is aircraft-specific. Help facility available.

Note: For any record selected, if Aircraft Model # is available, both ‘A/C MSN - From’ and ‘A/C MSN - To’ must be entered.

MSN – From

The starting serial number in the range of manufacturer serial numbers.

Note: This field is component-specific.

Help facility available.

MSN - To

The ending serial number range in the range of manufacturer serial numbers.

Note: This field is component-specific.

Help facility available.

Note: For any record selected, if Part # is available, both ‘MSN - From’ and ‘MSN - To’ must be entered.

Note: For Eng. Docs of ‘Engine’ or ‘Component’ Applicability, the system hides ‘Aircraft Model #’, ‘A/C MSN – From’ and ‘A/C MSN – From’ fields.

Note: The same range of respective serial numbers entered here must not be repeated for the same Aircraft Model # or Part #. For the Aircraft Model # / Part # entered, you must select ‘Include All Srl.’ or enter the respective serial range.

For an Aircraft Model # / Part #, the range of serial number entered newly must not lie within the range of serial numbers already existing in the multiline.

App. Grp. #	The applicability group of the engineering document. A positive integer must be entered here.
Applicable?	Use the drop-down list box to specify the applicability of effectivity for the engineering document. The system lists the values “Yes”, “No”, “Hold” or “Previously Complied”, selectively, based on the process parameter ‘Specify values for ‘Applicable?’ set in the “Common Master” business component. “Yes”, “No”, “Hold”, if the process parameter is set as 'Hold'. “Yes”, “No”, “Previously Complied”, if the process parameter is set as “Previously Complied' “Yes”, “No”, Hold”, “Previously Complied”, if the process parameter is set as “Hold” and “Previously Complied”. “Yes”, “No”, if the process parameter is set as 'None'.
Disposition Code	Use the drop-down list box to select the disposition code to be associated to the part # -serial # impacted by the engineering order.
Disposition Remarks	More details on the movement of the part # -serial # impacted by the engineering order upon removal.
Restricted?	Use the drop-down list box to indicate whether the part # -serial # is restricted to certain transactions. The drop-down list box displays No and Yes.
Restriction Code	Use the drop-down list box to select the restricted code that must be mapped to the part # -serial # impacted by the engineering order. The drop-down list box displays the Active entities defined under the entity type Stock Restriction Code in the Defined Process Entities activity of Common Master.
Restriction Remarks	More details on the restriction imposed by the restriction code on the transactions involving the part # - serial # impacted by the engineering order.
Reference Date Basis	Use the drop-down list box to select reference date for the effective date. The system lists the values “Induction Date”, “Operational Date” and “Manufactured Date”.
Eff. From Date	The date from which the restriction on the part # - serial # becomes effective. Note: You must enter the effective date for the commencement of restrictions on the part # - serial # based on the reference date selected in the Reference Date Basis field. For instance, if you have selected Manufactured Date, the effective date for the part # -serial # will the date on which the part # - serial # was manufactured by the equipment manufacturer. Similarly, if you have selected Induction date, you must enter the date on which the part # - serial # was inducted into operations.

The system displays the following field:

Excep. Def?

Indicates the visibility of exception for the serial range defined. The system displays the following values:

“Yes” - If the aircraft exists in the defined range with ‘Applicable?’ set as “No”, “Hold” or “Previously Complied”.
“No” - If the Aircraft exists in the defined range with ‘Applicable?’ as “Yes”,

Enter the following field:

Action on Rev. Effec. ?	Use the drop-down list box to specify the option for copying the effectivity details of the engineering document from the previous revision to the new revision number. This field is displayed, only if the Revision # of the Eng. Doc. in the header is greater than ‘0’. The system lists the following values: · “Re-Comply”, Carryover Compliance”, “Revoke” and “Terminate”, if the Applicability of the Eng. Doc. is “Aircraft”. · “Re-Comply”, Carryover Compliance” and “Revoke”, if the Applicability of the Eng. Doc. is “Engine” of “Component”. By default, the system defaults the values defined for the attribute “Default value for ‘Action on Rev. Effec.?’ in Effectivity” in the “Common Master” business component. Note: This field is available only if the engineering document is a revision.
Prev. Comp. Doc. #	The code identifying the document that was previously complied. Mandatory, if ‘Applicable?’ is set as “Previously Complied’.
Prev. Comp. Date #	The date of previous compliance of the engineering document. . Mandatory, if ‘Applicable?’ is set as “Previously Complied’.
Processing Comments	Any comments related to the effectivity. Data entry in this field is non mandatory, on addition / modification of effectivity.

Note: The system does not display the ‘Prev. Comp. Doc. #’ and ’ Prev. Comp. Date. #’ fields, if the process parameter 'Specify values for ‘Applicable ?’ in Effectivity' is set as either 'Hold' or 'None' in the “Common Master” business component.

The “Effectivity Details” multiline displays the following.

Created By	The login user who created the record.
Created Date	The date on which the login user created the record.
Modified By	The login user who most recently modified the record.
Modified Date	The date on which the login user most recently modified the record.

Click the “Displays Serial Details” pushbutton to display the effectivity details in a separate multiline below the ‘Serial Range’ multiline, based on the Eng. Doc. Applicability.

The system displays the following fields:

CS	The Compliance Status of effectivity of the Aircraft Reg #.

Enter the following fields:

AC Reg #	The registration number of the aircraft. The aircraft registration number entered here must be defined as ‘Active’ in the “Aircraft” business component. Process Parameter Dependency: The aircraft you enter here must be mapped to the maintenance operator tagged to the login user, if the process parameter “Allow addition/modification of Aircraft & Component from other Maint. Operator codes in EO?” is set as "0" for “Not Allowed” under the entity type Eng. Doc Type and the entity “All Eng. Doc” in the Define Process Entities activity of Common Master. Note: This field is aircraft-specific. Help facility available.
A/C MSN	The manufacturer serial # of the aircraft on which the engineering document must be implemented. Note: This field is aircraft-specific. Help facility available.
Part #	The part # of the component on which the engineering document must be implemented. Note: This field is component-specific. Help facility available.
Serial #	The serial # of the component on which the engineering document must be implemented. Note: 1) This field is component-specific. 2) Either Serial # or MSN is mandatory. Process Parameter Dependency: The serial # you enter here must be mapped to the maintenance operator tagged to the login user, if the process parameter “Allow addition/modification of Aircraft & Component from other Maint. Operator codes in EO?” is set as "0" for “Not Allowed” under the entity type Eng. Doc Type and the entity “All Eng. Doc” in the Define Process Entities activity of Common Master. Help facility available.

The multiline displays the following field:

Serial Exists?

Indicates whether the serial # of the part/aircraft model is available in the inventory or phased out of operation.

Enter the following field:

MSN

The manufacturer serial number of the aircraft/component on which the engineering document must be implemented.

Note: Either Serial # or MSN is mandatory.

Help facility available.

App. Grp. #	The applicability group of the engineering document. A positive integer must be entered here.
Applicable?	Use the drop-down list box to specify the applicability of effectivity for the engineering document. The system lists the values “Yes”, “No”, “Hold” or “Previously Complied”, selectively, based on the process parameter ‘Specify values for ‘Applicable?’ set in the “Common Master” business component. “Yes”, “No”, “Hold”, if the process parameter is set as 'Hold'. “Yes”, “No”, “Previously Complied”, if the process parameter is set as “Previously Complied' “Yes”, “No”, Hold”, “Previously Complied”, if the process parameter is set as “Hold” and “Previously Complied”. “Yes”, “No”, if the process parameter is set as 'None'. On save, if engineering document is in “Released” status and in ‘Edit’ mode, you can modify ‘Applicable?’ from “No” / ”Previously Complied” / “Hold” to "Yes", only if: Tasks are available for the corresponding applicable group. Schedules and Next Schedule Date / Value are available for the corresponding tasks of the applicable group.
Disposition Code	Use the drop-down list box to select the disposition code to be associated to the part # -serial # impacted by the engineering order.
Disposition Remarks	More details on the movement of the part # -serial # impacted by the engineering order upon removal.
Restricted?	Use the drop-down list box to indicate whether the part # -serial # is restricted to certain transactions. The drop-down list box displays No and Yes.
Restriction Code	Use the drop-down list box to select the restricted code that must be mapped to the part # -serial # impacted by the engineering order. The drop-down list box displays the Active entities defined under the entity type Stock Restriction Code in the Defined Process Entities activity of Common Master.
Restriction Remarks	More details on the restriction imposed by the restriction code on the transactions involving the part # - serial # impacted by the engineering order.
Reference Date Basis	Use the drop-down list box to select reference date for the effective date. The system lists the values “Induction Date”, “Operational Date” and “Manufactured Date”.
Effec. From Date	The date from which the restriction on the part # - serial # becomes effective. Note: You must enter the effective date for the commencement of restrictions on the part # - serial # based on the reference date selected in the Reference Date Basis field. For instance, if you have selected Manufactured Date, the effective date for the part # -serial # will the date on which the part # - serial # was manufactured by the equipment manufacturer. Similarly, if you have selected Induction date, you must enter the date on which the part # - serial # was inducted into operations.
Action on Rev. Effec. ?	Use the drop-down list box to specify the option for copying the effectivity details of the engineering document from the previous revision to the new revision number. This field is displayed, only if the Revision # of the Eng. Doc. in the header is greater than ‘0’. The system lists the following values: · “Re-Comply”, Carryover Compliance”, “Revoke” and “Terminate”, if the Applicability of the Eng. Doc. is “Aircraft”. · “Re-Comply”, Carryover Compliance” and “Revoke”, if the Applicability of the Eng. Doc. is “Engine” of “Component”. By default, the system defaults the values defined for the attribute “Default value for ‘Action on Rev. Effec.?’ in Effectivity” in the “Common Master” business component. Note: This field is available only if the engineering document is a revision.
Prev. Comp. Doc. #	The code identifying the document that was previously complied.
Prev. Comp. Date #	The date of previous compliance of the engineering document.

AC Reg #	The registration number of the aircraft. The aircraft registration number entered here must be defined as ‘Active’ in the “Aircraft” business component. Note: This field is aircraft-specific. Help facility available
A/C MSN	The manufacturer serial # of the aircraft on which the engineering document must be implemented. Note: This field is aircraft-specific. Help facility available.
Part #	The part # of the component on which the engineering document must be implemented. Note: This field is component-specific. Help facility available.
Serial #	The serial # of the component on which the engineering document must be implemented. Note: 1) This field is component-specific. 2) Either Serial # or MSN is mandatory. Help facility available.

The multiline displays the following field:

Aircraft Model #

The model number of the aircraft on which the engineering document must be implemented.

Note: This field is aircraft-specific.

Part Change

Indicates whether the engineering document entails part# change for the component.

Note: This field is component-specific.

Enter the following field:

Srl. # Change

Use the drop-down list box to indicate whether the engineering document entails serial # change of the component.

Note: This field is component-specific.

New Srl. #

Use the drop-down list box to indicate whether the engineering document entails serial # change of the component.

Note: This field is component-specific.

Processing Comments

Any comments related to the effectivity. Data entry in this field is non-mandatory, on addition / modification of effectivity.

The system displays the following fields:

Program Exist?	Indicates whether maintenance program for the aircraft/component is defined in the system.
Program Updated?	Indicates whether the maintenance program for the component/aircraft has already been updated as stipulated in the engineering document.
Created By	The login user who created the record.
Created Date	The date on which the login user created the record.
Modified By	The login user who most recently modified the record.
Modified Date	The date on which the login user most recently modified the record.
Source Document #	The document reference for inducting the component into the inventory, such as Customer Goods Receipt or Goods Receipt.

Enter the following field below the multiline:

Update Maint. Prog. Template

Use the drop-down list box to specify whether the model program or part program has to be updated instead of aircraft specific program or component program. The system lists:

· ‘Model’, if the Applicability of the Eng. Doc. in the header is “Aircraft”.

· ‘Part’, if the Applicability of the Eng. Doc. # in the header is “Engine” or “Component”.

Revision Comments

Any comments related to the revision of the engineering document. You must enter the revision comments, on revising the Eng. Doc. #, if the process parameter ‘Engineering Document Revision Policy’ for the Eng. Doc is set as “Revision Mandatory”.

Click the “Save” pushbutton to update the effectivity details.

Note: The system displays an error message, if any concurrent user attempts to modify the Aircraft Effectivity details for the Eng. Doc. # and Revision #.

You cannot edit the Eng. Doc. in ‘Released Status’, if the process parameter 'Engineering Document Revision Policy' for the Eng. Doc is set as “Revision Mandatory” in the “Common Master” business component.

The system performs the following on clicking the “Save” pushbutton:

4 The system allows addition / modification of effectivity, based on the Status of the Eng. Doc. # and the process parameter ‘'Engineering Document Revision Policy’ set in the “Common Master” business component, as shown in the below table:

Process Parameter ‘Engineering Document Revision Policy’	Revision Rule (Common Master)	Eng. Doc Status	Screen mode	The system performs the following on addition / modification of effectivity
Revision Mandatory	Not Applicable	Released	Revise	Allows addition of new effectivity / modification of existing effectivity and creates new revision # for the selected Eng. Doc.
As per Revision Rules	Mandate Revision on Addition of Effectivity? set as 'No' Mandate Revision on Modification of Effectivity? as 'Yes'	Released	Edit	Allows addition of new effectivity and, the system saves the new effectivity for the Eng. Doc. Does not allow modification.
As per Revision Rules	Mandate Revision on Addition of Effectivity? set as 'Yes' Mandate Revision on Modification of Effectivity? as 'No'	Released	Edit	Does not allow addition of new effectivity Allows modification of effectivity.
As per Revision Rules	Mandate Revision on Addition of Effectivity? as 'No' Mandate Revision on Modification of Effectivity? as 'No'	Released	Edit	Allows addition and saves the new effectivity for the Eng. Doc. Allows modification of effectivity.

Note: In the above scenarios, Revision # is not generated in ‘Edit’ mode.

The following task updates happen in the program / Eng. Doc., when the user works on released Eng. Doc. without revising it:

Task update in Program:

Inserts tasks in the Aircraft Maintenance Program or model program, if the effectivity is "At Serial Level" for a record with ‘Applicable?’ set as 'Yes' and Applicable group # defined and if schedule is available for those tasks.
If ‘Applicable?’ is set as “Yes”, on release of the Eng. Doc., if task is not available in the program, it gets inserted in the program.
If ‘Applicable?’ is changed from “Yes” to “No” / “Hold” / “Previously Complied”, if task is available in the program, Schedule Status of the task is changes as “Inactive”.
If ‘Action on Rev. Effec. ?’ is “Revoke”, if task is available, the system inactivates the task in the program.
If ‘Action on Rev. Effec. ?’ is “Terminate”, if task is available, the system inactivates the task in the program.

Task update in Eng. Doc.:

If ‘Applicable?’ is changed from “Yes” to “No” / “Hold” / “Previously Complied”, if task is associated to Aircraft Reg # for the particular Applicability Group, the corresponding task will be deleted from the Eng. Doc.
If ‘Applicable?’ is changed from “No” / “Hold” / “Previously Complied” to “Yes”, if task is available for the Applicability Group, task gets copied along with the schedule and NSD is computed.
Addition of effectivity of Released Eng. Doc:

If a new aircraft effectivity is defined for the EO and if ‘Applicable?’ is “Yes”, “No”, “Hold” or “Previously Complied”, the system displays an error message if 'Action on Revision Effectivity?' is selected.

Modification of effectivity on Release EO:

If for an existing aircraft effectivity, ‘Applicable?’ is modified, the system performs the following as shown in the table below:

‘Applicable?’ is changed from:	Action on Rev. Effec. ?	Impact on release of Eng. Doc.
“Yes” to “No” / “Hold” / “Previously Complied”	-	Updates the Task Status as “Terminate” in the Aircraft Maintenance Program or Model Program.
“No” / “Hold” / “Previously Complied” to “Yes”	Re-Comply or Carryover Compliance	Next Schedule Date (NSD) / Next Schedule Value (NSV) is calculated as follows: *Date Based Schedule:* If Threshold Date is not entered and Threshold is entered: Next Schedule Date = Effec. From Date + Threshold If Threshold Date and Threshold are not entered and Repeat Interval is entered: Next Schedule Date = Effec. From Date + Repeat Interval *Usage Based Schedule:* If Threshold is not entered and Threshold Interval is entered: Next Schedule Value = Parameter Value at Effec. From Date + Threshold Interval If Threshold and Threshold Interval are not entered and Repeat Interval is entered: Next Schedule Value = Parameter Value at Effec. From Date + Repeat Interval
	Revoke	Tasks are made ‘Inactive’ in the Aircraft Maintenance Program.
	Terminate	Tasks that are not complied before, will be updated as ‘Terminate’ in the Aircraft Maintenance Program. If tasks are complied or packaged already, the system displays error message.
“No” to “Hold” / “Previously Complied” “Hold” to “No” / “Previously Complied” “Previously Complied” to “No” / “Hold”	Must be left blank	Displays error message if ‘Action on Rev. Effec. ?’ is selected.

If the ‘Action on Rev. Effec.?’ is set as “Terminate” for an aircraft, the system allows addition of the same aircraft as a new effectivity, on revision.
Task deletion:

On flipping of ‘Applicable?’ from "Yes" to "No" / "Hold" / "Previously Complied", the system deletes the task corresponding to the applicable group, if effectivity does not exist.

Task Effectivity update

If ‘Applicable?’ is ‘Yes’ for a part #, aircraft model # or aircraft reg. #, the system makes the task from the applicability group applicable to the engineering document effective for the maintenance object in the Maintenance Task business component. However, once ‘Applicable?’ is changed from “Yes" to "No", effectivity of the task for the aircraft model #/aircraft reg. # is removed in Maintenance Task.

Note: If user works on the released engineering document in ‘Edit’ mode, the tasks do not get deleted from the corresponding program, but are inactivated.

Aircraft/Component Effectivity update

The system allows for the release of engineering documents even if the impacted aircraft/components are not available / Active in the organization/inventory. Upon creation of aircraft/component with Record Status as ‘Active’ in the Aircraft component, the aircraft/component is updated in the applicable engineering document with

Program Updated? = ‘No’
Applicable? = ‘Yes’
Created By = System

The system updates the serial details of the maintenance object in the latest revision of the engineering document. If multiple engineering documents are effective for a component/aircraft, the system updates all of these engineering documents in the order of their release dates. Program Updated becomes ‘Yes’ only upon update of the maintenance program of the aircraft/component as necessitated by the engineering document.

Impact on Inactive aircraft: When ‘Engineering Document Revision Policy’ is set as 'As per Revision Rules' & 'Mandate Revision on Addition of Effectivity?' is set as 'No' and, if the user modifies and saves the released engineering document, the tasks are added to the maintenance programs of aircraft newly added in the Effectivity tab. The tasks are added to the maintenance program of both Active & Inactive aircraft. Schedule status of tasks for Active aircraft is set as ‘Active’. However, Schedule Status of engineering tasks added in the maintenance programs of Inactive aircraft depends on the process parameter “Update Eng. Task's schedule status as Inactive in maintenance program for inactive Aircrafts on release of Eng.Doc.?” under the entity type “Eng. Doc. Type” and the entity "All Eng. Doc” in the Define Process Parameters activity of Common Master. The next table elaborates on the functioning of the process parameter.

Process Parameter Value	Impact on maintenance programs of Inactive aircraft
1	Schedule Status of the engineering tasks added in the maintenance programs is set as ‘Inactive’
0	Schedule Status of the engineering tasks added in the maintenance programs is set as ‘Active’

To proceed further

Select the “Main” tab to create / edit revise an engineering document.
Select the “Tasks” tab to define task details.
Select the “Schedules” tab to define schedules for tasks in engineering document.
Select the “References” tab to define reference details.
Select the “More Information” tab to record additional details like cost details, warranty details for the engineering document.