--- title: "Static Schedules" slug: "static-schedules" tags: ["NID", "Schedules", "Planned Events", "ONE IMS"] updated: 2026-10-27T23:11:33Z published: 2026-10-27T23:11:33Z canonical: "ims-handbook.cenosco.com/static-schedules" --- > ## Documentation Index > Fetch the complete documentation index at: https://ims-handbook.cenosco.com/llms.txt > Use this file to discover all available pages before exploring further. # Defining Static Schedules 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 Last Inspection Date (LID). 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](/v414/docs/application-settings) Enable IsStatic Flag on schedules. Please submit a [request to Support](/docs/requesting-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. ![](https://cdn.document360.io/e492a0e0-a4ba-4aca-8fc6-76b95f91fdf3/Images/Documentation/pic%201(836).png?sv=2026-02-06&spr=https&st=2026-10-28T14%3A19%3A44Z&se=2026-10-28T15%3A19%3A44Z&sr=c&sp=r&sig=Q7iqjqdlBdD1moq98sLa6Suz4rvKxW4zQT6BcaX0JZk%3D) Note: 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. ## 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 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: 27.06.2024 > > NID3: NID2 + 12m = 01.05.2024 + 12m = 01.05.2025 ### 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). > For example, if today is 02/03/2023 and 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: Today is 02/03/2023. > > If you define a User Date as 1/1/2026 and a Time Interval of 12 months. > > Then Time Interval Date = User Date + Time Interval = 1/1/2026 + 12m = 1/1/2027. > > NID stays at User Date (1/1/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](/v414/docs/next-inspection-date-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](/v414/docs/next-inspection-date-nid-horserace). This is also the case for Static Schedules.