Publication Date: 8/17/2026 Share Print

Previous Topic

Next Topic

Book Contents

Book Index

PN_EC_INSTDAYS - Count P/N E/Cs by E/C's Calendar Days or Part's Installed Days

but_X1 big switch

Count P/N E/Cs by E/C's Calendar Days or Part's Installed Days

Affected Window: w_ac_planning_qry

PN_EC_INSTDAYS_12.5(1)

 

The planning forecast will calculate an E/C's due date based on the switch setting and the selection made from the E/C Schedule tab, Calendar Days drop down.

logo_15 small switch PN_EC_INSTDAYS = Yes:

Calendar Days options:

  • Yes - the planning forecast calculates the due date from the E/C's Effective Date.
  • No - the planning forecast calculates the due date from the part's installed date. For P/N E/Cs only.
  • No Fly - the planning forecast calculates the due date from the last A/C flight or last E/C compliance date, whichever is more recent. For A/C E/Cs only.

PN_EC_INSTDAYS = No:

Calendar Days options:

  • Yes - the planning forecast calculates the due date from the E/C's Effective Date.
  • No Fly - the planning forecast calculates the due date from the last A/C flight or last E/C compliance date, whichever is more recent. For A/C E/Cs only.

    Note: When PN_EC_INSTDAYS is set to No, in Version 15 the available options are Yes and No Fly. In Version 12.5 the options are No and No Fly. The change from No to Yes was a field name change only, functionality did not change. When using the alternative to No Fly, the planning forecast calculates from the E/C's Effective Date. (This came into effect TRAX Version 15 SP6).

logo_12_5 small switch PN_EC_INSTDAYS = Yes:

Calendar Days options:

  • Yes - the planning forecast calculates the due date from the E/C's Effective Date.
  • No - the planning forecast calculates the due date from the part's installed date. For P/N E/Cs only.
  • No Fly - the planning forecast calculates the due date from the last A/C flight or last E/C compliance date, whichever is more recent. For A/C E/Cs only.

PN_EC_INSTDAYS = No:

Calendar Days options:

  • No - the planning forecast calculates the due date from the E/C's Effective Date.
  • No Fly - the planning forecast calculates the due date from the last A/C flight or last E/C compliance date, whichever is more recent. For A/C E/Cs only.

logo_11_small switch editedPN_EC_INSTDAYS = Yes:

Calendar Days checkbox:

  • Selected - the planning forecast calculates the due date from the E/C's Effective Date.
  • Not selected - the planning forecast calculates the due date from the part's installed date. For P/N E/Cs only.

PN_EC_INSTDAYS = No

Calendar Days checkbox is not available.

  • The planning forecast calculates the due date from the E/C's Effective Date (as if the checkbox were selected). 

Note: When the system is configured to calculate the P/N E/C's due date from the part's installed date, the part needs to be installed after the P/N E/C's Effective Date for the planning forecast to calculate the due date accurately. If the P/N E/C's Effective Date is after the part's installed date, the due date is calculated from the P/N E/C's Effective Date. If the part had previous remove/install transactions, prior to the P/N E/C's Effective Date, and those previous accrued times need to be included in the current calculations, the P/N E/C actuals for the part need to be updated to track and forecast the due date correctly. For more information, refer to the P/N E/C Actuals Calculations scenario guide.

For more information on the differences in this functionality between TRAX Version X, 11, and 12.5, refer to P/N E/C Calendar Days Planning, via the Engineering Training Manual.

 

Switch Set to Yes:

When set to Yes, in the Engineering Control, Schedule tab, three options are available from the Calendar Days drop down (Yes, No, No Fly) and the planning forecast calculates the E/C's due date based on the selection made.

  • Yes - E/C due date is calculated based on Calendar Days starting from the E/C's Effective Date.
  • No - E/C due date is calculated from the parts installed date (if the installed date is after the E/C's Effective Date). For P/N E/Cs only.
  • logo_12_5 small switch No Fly - E/C Due Date is calculated from the last A/C flight or the last E/C compliance date, whichever is more recent. For A/C E/Cs only.

12_Planning_Yes

 

Calendar Days set to No

The below P/N E/C's Effective Date is 07/01/2020, Calendar Days is set to No, and the E/C has a repeat schedule of 180 days.

PN_EC_INSTDAYS_12.5(2)

P/N is linked to the P/N E/C.

PN_EC_INSTDAYS_12.5(3)

P/N S/N is tracking against the P/N E/C and has an Effective Date of 07/01/2020; the E/C has not yet been complied with.

PN_EC_INSTDAYS_12.5(4)

The P/N S/N was installed 09/15/2020.

PN_EC_INSTDAYS_12.5(5)

Because the P/N E/C's Calendar Days drop down is set to No, the planning forecast calculates the Due Date based on the part's installed date.

PN_EC_INSTDAYS_12.5(6)

The Due Date is therefore 180 days after the part's installed date.

PN_EC_INSTDAYS_12.5(10)

Note: If the part was installed on the aircraft prior to the P/N E/C's Effective Date, the planning forecast would count days only from the E/C's Effective Date, not from the part's installed date. For the planning forecast to include the days the part was installed on the aircraft prior to the P/N E/C's Effective Date, the user needs to determine the number of days accrued between the install date and E/C Effective Date and update the P/N E/C actuals for the part.

 

Calendar Days set to Yes

Using the same P/N E/C above, the Calendar Days is set to Yes; the E/C Effective Date is still 07/01/2020.

PN_EC_INSTDAYS_12.5(7)

Because the P/N E/C's Calendar Days drop down is set to Yes, the planning forecast calculates the Due Date based on the P/N E/C's Effective Date.

PN_EC_INSTDAYS_12.5(8)

The Due Date is therefore 180 days after the P/N E/C's Effective Date.

PN_EC_INSTDAYS_12.5(11)

 

Calendar Days set to No Fly

The below A/C E/C Effective Date is 10/01/2020, Calendar Days is set to No Fly, and the E/C has a repeat schedule of 10 days.

PN_EC_INSTDAYS_12.5(12)

A/C is tracking against the A/C E/C and has an Effective Date of 10/01/2020.

PN_EC_INSTDAYS_12.5(13)

The A/C last flight date is 10/02/2020.

PN_EC_INSTDAYS_12.5(14)

The A/C E/C is then complied with 10/13/2020.

PN_EC_INSTDAYS_12.5(15)

The A/C E/C Effective Date is updated to reflect the last compliance date.

PN_EC_INSTDAYS_12.5(16)

Because the Calendar Days drop down is set to No Fly, when the planning forecast is generated it looks at the A/C last flight date and the E/C last compliance date (Effective Date) and uses the most recent date to calculate the Due Date. Since the E/C has not flown since 10/02/2020 and the A/C E/C was complied with 10/13/2020, the planning forecast uses the last compliance date to calculate the Due Date.

PN_EC_INSTDAYS_12.5(17)

The Due Date is therefore 10 days after the A/C E/C Effective Date.

PN_EC_INSTDAYS_12.5(18)

The A/C is then flown and the A/C last flight date is now 10/20/2020; the A/C E/C Effective Date is still 10/13/2020.

PN_EC_INSTDAYS_12.5(19)

Because the A/C last flight date is more recent than the A/C E/C last compliance date, the planning forecast calculates the Due Date based on the A/C last flight date.

PN_EC_INSTDAYS_12.5(20)

The Due Date is therefore 10 days after the last A/C flight date, October 20, 2020.

PN_EC_INSTDAYS_12.5(21)

 

Switch Set to No:

When set to No, only two options are available from the Calendar Days drop down (Yes, No Fly) and the planning forecast calculates the E/C's due date based on the selection made.

  • Yes - E/C due date is calculated based on Calendar Days starting from the E/C's Effective Date.
  • No Fly - E/C Due Date is calculated from the last A/C flight or the last E/C compliance date, whichever is more recent (A/C E/Cs only).

12_Planning_No

Note: When set to No, the mixed schedule functionality is activated. Therefore, if existing E/Cs accrue time while this switch is set to Yes and is later switched to No, utilizing a schedule of hours/cycles mixed with days will require you to contact Customer Support to review your data for optimal accuracy. This additional precaution is only required when switching from Yes to No settings. This precaution is not required for newly created E/Cs that have yet to accrue time/data.

In TRAX Version 12.5 -> Version 15 SP5:
When PN_EC_INSTDAYS is set to No and No is selected from the Calendar Days options, the system functions the same as when PN_EC_INSTDAYS is set to Yes and Yes is selected from the Calendar Days options - the planning forecast will use the E/C's Effective Date to calculate the due date. Refer to Calendar Days set to Yes example above.

In TRAX Version 15 SP6 (and later releases):
When PN_EC_INSTDAYS is set to No and Yes is selected from the Calendar Days options, the system functions the same as when PN_EC_INSTDAYS is set to Yes and Yes is selected from the Calendar Days options - the planning forecast will use the E/C's Effective Date to calculate the due date. Refer to Calendar Days set to Yes example above.

When PN_EC_INSTDAYS is set to No, and No Fly is selected from the Calendar Days options, the system functions te same as when PN_EC_INSTDAYS is set to Yes and No Fly is selected from the Calendar Days options - the planning forecast calculates the due date from the last A/C flight or last E/C compliance date, whichever is more recent. Refer to the Calendar Days set to No Fly example above.

See Also

Planning Switches

ACPLANQ - A/C Planning Query Fast Mode

ACROLAVG - Use A/C Rolling Average for Mean Hours and Cycles

ALWMULTTSK - Prevent Element from being Added to a Work Order

APUMEAN - Mean APU Calculation

AUTOWONHADESC - Enables Auto W/Os generated via Planning to automatically include NHA P/N, S/N and Position Info

AUTOMANHOURSCHEDULE - Allow AUTO_MANHOUR_SCHEDULE_JOB to Appear in Trax Database Jobs

AUTOTSKPRIORITY - Enable Auto Task Priority Functionality

CHILDECNOSH - Show Child E/Cs With No Schedule in A/C Planning Query

CPYSCHFROMTRANS - Use Planning Transaction Schedule for TCs on Work Orders with a Line Status

DUEATPRJCT - Project the Due At Hours and Cycles using the mean hours and cycles

EMPATTSEQ - Employee Attendance Sign-On / Sign-Off Next Sequence

INTERACTPLANMANHOURS - Interactive Planner Displays Daily Man Hours per Location/Site

LBRBYHCNT - System Labor by Head Count

LivePlan - Enables the Live Planning Functionality

MANHOURSAUTOCOMP - Auto complete certain fields in Man Hours Schedule Override

MANPLNDLF - Default Man Hour Schedule Planner to Location/Site of the Employee

MELDEFLOC - Deferred Defect Convert Reported/Deferred day to Local Time Zone

OVNDATADAYS - Define Number of Days to Display in Overnight Station Report Tab

OVNTACMS - Overnight Station Default

PASTASCH - Create Past Absence Record

PLANBY - DO NOT CHANGE FROM NO Capacity Planning By: Week = (YES) or Month = (NO)

PLANDEPT - Planning Department and Planning Sub Department fields Mandatory

PLANDUE% - Planning Warning When Percent Due

PLANPNSEQ - Planning P/N Next Sequence Number

PLNAUTO7D - Activate Seven Day Forecast Automatically at Set Interval

PLNHISTML - Determine Planning History Time Limit

PLNJBDFLT - Default Planning Job Checkbox

PLNJOBACNO - Run Planning Jobs by Program Instead of Oracle Scheduler

PLNJOBQUE - Activate Planning Job by Java Queue

PLNTRNNO - Planning Transactions Sequence Number can only be changed by the TRAX Application

PLNWSHDCHLD - Hide Child E/C on Planning Control Workscope by Default

SCHEDULEWORKG - Allow Work Group Selection Filter

SELFSCHLM - Self Assignment Schedule Date Range Limit

SHOPCAPNOT - Do Not Validate Against Shop Capability in the Shop Resource/Tasks Planner

SHPPLNDLF - Default Shops Resource/Tasks Planner to the Location/Site in Employee Master

STREAMLINE - Clean Up Employee Schedules

TOEXITMS - Turn Off Exit Pop Up Message in Planning Query

TOOLWARN - Issues warning if tool expires during W/O scheduled date range

Top of Page Publication Date: 8/17/2026 Share Print