Scenario |
NSD / NSV |
Next Due Calc. On |
Calc. Ref. Value / Date |
Last Schedule Date / Value |
|
If the task with Tracking type as ‘Schedule tracked’ and ‘Applicable’ set as “Yes” |
Threshold interval /repeat interval is defined in ‘Eng. Doc schedule information |
|
Eng. Doc. Effec. from Date (Date & Usage Based Schedule) |
|
Not Applicable (Date & Usage Based Schedule) |
If threshold date / value is defined in the Eng. Doc schedule information page |
|
Eng. Doc : Initial Interval (Date & Usage Based Schedule) |
|
Not Applicable (Date & Usage Based Schedule) |
|
If user manually initialize the task in “Initialize Eng. Doc” page |
|
Eng. Doc. - Manual : Correction |
User entered value |
Not Applicable |
|
If the task with initiate /reset by as ‘RTC’ and if the parent task (T1) has initiate schedule relationship with related task (T2) |
|
Not Applicable |
Not Applicable |
Not Applicable |
|
If the task with ‘Initiate / Reset by’ set as ‘RTC’ and if the Parent task(T1) has initiate schedule relationship with related task (T2) and if user manually initialize the task(s) in ‘Initialize Eng. Doc.’ page |
|
Eng. Doc. - Manual : Correction |
User entered value |
User entered value |
|
If the Eng. Doc effective from date is future date |
Blank |
Not Applicable |
Not Applicable |
Not Applicable |
|
If the Eng. Doc effective from date is future date and if the user manually initializes the task in “Engineering Document” business component |
NSV = User-entered value (Prog. Item Type of the task = “To be decided”) As indicated above, this reasoning works for tasks with Usage Based schedules only. However, for Date Based Schedules, the behavior would be the same as Usage Based schedules only if the process parameter value of "Update Next Sch. Date in maintenance program on release of future dated Eng. Doc.?" is 0 (No). For more details, go to Define Process Parameters activity in Common Master and refer to OLH. |
Eng. Doc - Manual : Re-baseline |
User entered value |
Not Applicable |
|
When revising the Eng. Doc, if the ‘Action on revision’ is selected as ‘Re-comply’ and if the task is complied in previous revision |
|
Eng. Doc. Effec. from Date (Date & Usage Based Schedule) |
|
Not Applicable (Date & Usage Based Schedule) |
|
When revising the Eng. Doc, if
|
|
Manual : Correction |
User entered value |
Not Applicable |
|
When revising the Eng. Doc, if the ‘Action on revision’ is selected as “Carry Over Compliance” and if the task is complied in previous revision |
The system retains the schedule in the program |
Time window / Actual completion / Schedule |
Last Performed Date or Value / Last Schedule Date or value |
Last schedule value |
|
If user revises the EO and selects the ‘Action on Revision’ as 'Revoke', on release of Eng. Doc. |
The task in the program is inactivated |
Blank |
Blank |
Blank |
|
If user revises the EO and selects the ‘Action on Revision’ as 'Terminate', on release of Eng. Doc. |
The task in the program is inactivated |
Blank |
Blank |
Blank |
|
If the ‘Mandate Revision on Modification of Effectivity?’ is set as ‘Yes’ or 'No' and the ‘Applicable’ is set as ‘No/hold/PCW’, on save or release |
The task in the program is inactivated |
Blank |
Blank |
Blank |