Defining Static Schedules

Prev Next

A recurring Schedule can be labeled as a Static Schedule. If labeled as a Static Schedule, the NID will be based on the User Date / User Interval and will ignore the LID, unless the inspection takes place more than a year before the Schedule due date, in which case the LID year is taken into account. 

Static Schedules are meant for inspections allowed (by code or authority) to be performed at any given date within the year it is due.

Activating the Static Schedule option

Static Schedules are an option that can be activated for PLSS, PEI, Civil, and FMA. By default this option is hidden. If you want to use this option it must be turned on via the Application Setting Enable IsStatic Flag on schedules. Please submit a request to Support if you need to have it turned on.

Setting a Schedule Static

When creating a new Schedule, you need to check Recurring. When this is checked the Static schedule checkbox will be shown. However, now you have to set a User Date and User Interval. Only then can the Static schedule box be checked.

Caution

For PEI, when Static schedule is checked, IMS will check if the Equipment has an RBI Component. If so then the Ignore RBI Interval/NID is checked by default and the RBI date is removed from the NID horserace.

Note

We recommend setting the User Date to 31.12 of the desired year. The Static Schedule year then runs from 01.01. to 31.12 of the same calendar year.

With a different day and month, for example 15.06.2024, the Static Schedule year runs from 16.06.2023 to 15.06.2024 and spans two calendar years.

Comparing regular recurring Schedules and Static Schedules

NID independent from LID 

The main difference between regular recurring Schedules and static Schedules is that regular recurring Schedules always get their NID from the LID + Time Interval, regardless of User Date. Static Schedules ignore the LID, and base the NID on the last NID + Time Interval.

Example: Regular vs Static NID calculations

Regular Schedule

NID1: 01.05.2023 / 12 months

ECH1: 15.04.2023

NID2: LID1 + 12m = 15.04.2023 + 12m = 15.04.2024

ECH2: 19.03.2024

NID3: LID2 + 12m = 19.03.2024 + 12m = 19.03.2025

Static Schedule

NID1: 01.05.2023 / 12 months

ECH1: 15.04.2023

NID2: NID1 + 12m = 01.05.2023 + 12m = 01.05.2024

ECH2: 19.03.2024

NID3: NID2 + 12m = 01.05.2024 + 12m = 01.05.2025

Crediting the Schedule more than a year early

There is an exception to the rule. When an inspection is done a year or more ahead of its due date on a Static Schedule, the NID is now counted from the year the inspection was done. The day and month stay the same.

Example 1: Schedule is credited more than a year before it is due

A Schedule has a 3-year interval and is due on 31.12.2023. The inspection is done on 15.06.2022.

Regular Schedule

NID2: LID1 + Interval = 15.06.2022 + 3 years = 15.06.2025

Static Schedule

NID2: LID1 (year) + User (month and day) + Interval = 31.12.2022 + 3 years = 31.12.2025

Example 2: Schedule is still credited within the year that it is due

A Schedule has a 3-year interval and is due on 31.05.2023. The inspection is done on 15.06.2022.

Regular Schedule

NID2: LID1 + Interval = 15.06.2022 + 3 years = 15.06.2025

Static Schedule

NID2: User Date + Interval = 31.05.2023 + 3 years = 31.05.2026

Crediting the Schedule after the due year

When a Static Schedule is credited after the year that it is due, no credit is taken for the LID, i.e., the Static Schedule still ignore the LID, and base the NID on the last NID + Time Interval.

Example: Schedule is credited after due date

A Schedule has a 3-year interval and is due on 31.12.2023. The inspection is done on 15.03.2024.

Regular Schedule

NID2: LID1 + Interval = 15.03.2024 + 3 years = 15.03.2027

Static Schedule

NID2: User Date + Interval = 31.12.2023 + 3 years = 31.12.2026

Horserace - any User Date can be defined

Regular Schedule

You cannot define a User Date that is later than the Time Interval Date (today's date + Time Interval).

Example: Regular Schedule User Date

Today is 02.03.2023.

If you define a Time Interval of 12 months, you cannot specify a User Date later than 02.03.2024.

Static Schedule

You can define any date you want.

Time Interval Date = User Date + Time Interval. Thus the Time Interval Date will always be later than the User Date.

Example: Static Schedule User Date

Today is 02/03/2023. 

If you define a User Date as 01.01.2026 and a Time Interval of 12 months.

Then Time Interval Date = User Date + Time Interval = 01.01.2026 + 12m = 01.01.2027.

NID stays at User Date (01.01.2026).

Horserace - RBI NID does not take part (only PEI)

For regular Schedules in IMS PEI, when the Component is linked to an RBI Analysis then the RBI NID and MII will take part in the Schedule's NID horserace. However, when a Static Schedule is created the Ignore RBI Interval/NID is checked by default and in this way RBI is removed from the NID horserace.

Planned Event / Campaign Date do not influence the NID

Planned Event and Campaign Dates do not influence a regular Schedule's NID, as the Planned Event and Campaign Dates do not take part in the linked Schedule's horserace. This is also the case for Static Schedules.