Schedules

A schedule is a template for recurring work: a checklist, instructions, spare parts, and a trigger that determines when the next work order is created.

Trigger types

• Manual templates never fire automatically. They are reusable task definitions you pull on demand.
• Time-based triggers fire on a cron schedule.
• Counter-based triggers fire after a usage counter reaches a value (every 500 operating hours, for instance) and reset when the work order closes.
• Condition-based triggers fire when a sensor reading or computed condition crosses a threshold. Conditions run as Python scripts in a sandbox with access to the Digel API, so they can express anything from "bearing temperature exceeds 85 degrees" to "vibration RMS has been above normal for 30 consecutive minutes."

Composite triggers

Triggers combine with AND/OR gates. "Every 500 hours OR every 6 months, whichever comes first." Or: "every 3 months, but only if vibration is above normal."

Completion-based scheduling

The next due date is calculated from when the previous work order was completed, not from the calendar. If a 3-month PM was done late, the next one is 3 months after completion. The interval is about wear, not calendar compliance.

No duplicates

If a work order from the same template is already open, the trigger will not create another one.