Maintenance intervals
What it is
Section titled “What it is”Every maintenance item has an interval type that decides how Syndik8 tracks “when is it next due?”. Three types exist:
- Hours — usage-based. Driven by the asset’s running meter (Hobbs, Tacho, engine hours).
- Days — calendar-based. Driven by elapsed time.
- Cycles — usage-based. Driven by landing cycles on aircraft (landings + touch-and-gos).
Who can use it
Section titled “Who can use it”Interval type is a field on the maintenance item form, visible to anyone who can view the item, editable by admins and owners.
Where to find it
Section titled “Where to find it”- Create Maintenance Item screen — Interval Type dropdown.
- Edit Maintenance Item screen — same control.
Fields / options
Section titled “Fields / options”| Type | Unit | Typical example | Visible in new-item form |
|---|---|---|---|
| Hours | Engine hours | 50-Hour check, 100-Hour check | Yes |
| Days | Calendar days | Annual inspection (365), ARC (365), Transponder check (730) | Yes |
| Cycles | Landing cycles | Landing-gear inspections | No — see Behaviour rules |
Behaviour rules
Section titled “Behaviour rules”- Hours and cycles are usage-based. The item’s “due at value” is a meter reading:
last_completed_value + interval_value. Completion happens when the asset’s current meter reaches or exceeds that number. - Days is calendar-based. The item’s “due at” is a timestamp:
last_completed + interval_value days. - Cycles is hidden from the create and edit forms. Existing items with a cycles interval continue to display, calculate status, and recur correctly. This keeps the UX simpler for the common cases (hours and days) without removing support for assets that already track cycles.
- Status calculation is identical across types — percentage or absolute-threshold rules apply the same way. See Maintenance items → Behaviour rules.
- Currently supported units are the three listed above. A “months” interval is not a separate type — multi-month calendar intervals use Days (e.g. 24 months = 730 days).