Calendar

The Calendar shows the time ranges of your organization by month — in particular the occurrences of maintenance plans: when each job is due, which ones need preparing, which are late, which are done.

Open it from the sidebar: Knowledge › Calendar.

Plan a recurring jobCopy Anchor Link

Maintenance plans are ontology objects.

1. Install the Augmented maintenance pack (Ontology › Packs). It adds the Maintenance plan type.

2. In Ontology › Objects, pick Maintenance plan and create one. In its Schedule, set:

   • Every N days, weeks, months or years, and the first date;
   • Until — an optional end date;
   • Length — how many days one job lasts;
   • Prepare — how many days ahead the occurrence turns to prepare.

   The form previews the next dates.

3. Tick Count from the last completion for a floating plan: a job done late pushes the next one back. Unticked, the plan is fixed: the dates follow the plan whatever happens.

4. Optionally link the plan to what it maintains (Links › maintains): a pump, a machine, or a device on its own.

The occurrences of the next 90 days appear by themselves, in the calendar and in the Time tab of the plan and of every object linked to it — the pump shows its next greasing. They follow the plan when you change it, and disappear when you archive it.

Work on an occurrenceCopy Anchor Link

Click an occurrence in the calendar and pick a change:

• Done — the day it was done and the time spent. For a floating plan, the next dates are recomputed from this completion.
• Move — a new day, for this occurrence only.
• Cancel — this occurrence only; the plan is unchanged.

Done, cancelled and moved occurrences are history: changing the plan never rewrites them.

Ranges written by flowsCopy Anchor Link

Flows can add ranges to the same calendar with the Time range writer node — for example a corrective job opened when a predictive node detects an anomaly.

The calendar never starts or stops a machine. To act when a job starts, run the type's action from the object page (for example Start maintenance on a pump): a deployed flow decides what happens.

With the assistantCopy Anchor Link

Ask "what maintenance is late?" or "plan a greasing of pump P-12 every 3 months". The assistant reads the calendar, creates or updates plans, and proposes a change to an occurrence (done, move, cancel): a Review button under its answer opens the same dialog, and you apply it. It never applies the change itself.

RolesCopy Anchor Link

Viewers read the calendar but change nothing.

What it does not do yetCopy Anchor Link

The calendar plans preventive work by date. It is not a full maintenance management system yet:

• no meters — plans by running hours or cycle counts are not supported;
• no work orders — an occurrence records done, moved or cancelled, not parts, checklists or sign-off;
• no teams — occurrences are not assigned to people or crews;
• no .ics feed — the calendar cannot be subscribed to from an external calendar app.

Related pagesCopy Anchor Link

• Ontology — types, links and the Augmented maintenance pack
• Flows — Action trigger and Time range writer nodes
• Predictive maintenance