Available for
- Roles: Administrator
- Plans: Starter, Premium, On demand
The fixed-date maintenance plan allows you to automatically create maintenance tasks according to a predefined schedule.
It works like a true maintenance calendar: tasks are created on the scheduled dates, no matter what.
This type of plan is particularly suited for recurring operations that must take place on specific dates or days, regardless of operating conditions or the status of other tasks.
How It Works
When a fixed-date maintenance plan is configured:
- tasks are automatically generated according to the defined frequency;
- each task is created independently of the others;
- task creation does not depend on the closure or completion of previous tasks.
Once the plan is activated, Mobility Work takes care of creating the tasks on the scheduled dates, without manual intervention.
Main Plan Settings
A fixed-date maintenance plan relies on several key parameters:
- Start Date: the starting point of the schedule.
- Frequency: repetition interval (weekly, monthly, every X weeks, etc.).
- Specific Days or Dates: for example, only Mondays or a specific day of the month.
The combination of these parameters allows for both simple scenarios and very precise scheduling.
Common Scenario Examples
Example 1: Weekly Maintenance on a Fixed Day
You need to perform a visual inspection of the installation every day, except weekends.
With a fixed-date maintenance plan:
- the frequency is set on a weekly basis;
- the trigger days are fixed from Monday to Friday;
- a new task is created for each weekday, even if the previous task is not yet completed.
This ensures perfect regularity, ideal for operational routines.
Example 2: Maintenance Every Three Weeks on Monday
Some operations require a more specific frequency, for example, every three weeks.
The fixed-date plan allows you to:
- set a three-week frequency;
- keep the trigger always on the same day of the week;
- automatically handle calendar variations (shorter or longer months).
Tasks are thus scheduled in advance with high accuracy.
Example 3: Monthly Maintenance on a Fixed Date
You need to carry out an intervention on the 15th of each month, without exception.
In this case:
- the trigger date is explicitly fixed;
- a task is created each month on the same date;
- scheduling does not depend on any other event.
This scenario is common for regulatory, administrative, or contractual operations.
Behavior of Generated Tasks
Tasks created by a fixed-date maintenance plan:
- are independent of each other;
- can be open simultaneously if multiple deadlines overlap;
- retain their scheduled date, even if processing is delayed.
This provides a clear view of upcoming, ongoing, and overdue interventions.
Chronological Processing Rules
Tasks must be processed in the chronological order of their scheduled dates.
For example:
- a task scheduled for 10/15 cannot be completed or canceled if the task scheduled for 09/15 is still active;
- tasks must therefore be closed in the order of their planned dates.
Reopening Completed Tasks
If you need to reopen tasks already marked as completed, they must be set to not completed in reverse chronological order, one by one (from the most recent to the oldest).
Rescheduling Tasks
It is possible to reschedule a task to an earlier or later date. However:
- a task cannot be rescheduled before the date of the previous task;
- nor after the date of the next task.
These rules ensure schedule consistency and avoid any breaks in the intervention timeline.