Maintenance items
What it is
Section titled “What it is”A maintenance item is a scheduled task tracked against a single asset: an Annual Inspection, an ARC renewal, a 50-Hour check, an oil change. Each item records:
- What the task is (name, description).
- When it is next due (calendar date, or meter value).
- Its current status, calculated from how close to due it is.
- A completion history: who completed it, when, and at what meter value.
Items can be created by hand for a specific asset, or added from a maintenance template. Completing an item resets its interval (recording the new last-completed value and date); it does not automatically create a follow-on item.
Who can use it
Section titled “Who can use it”- All members can see maintenance items on assets in their syndicate.
- Admins can create, edit, and log completion. The server restricts logging a completion to syndicate admins, so a member who carried out a usage-based item themselves still asks an admin to record the completion.
Where to find it
Section titled “Where to find it”- Asset detail → Maintenance tile → Maintenance list.
- Route:
/syndicates/:syndicateId/assets/:assetId/maintenance. - A quick-stats card on the asset detail shows the next-due picture at a glance.
Fields / options
Section titled “Fields / options”| Field | Required | Notes |
|---|---|---|
| Name | Yes | Up to 100 characters. E.g. 100-Hour Check. |
| Description | No | Up to 500 characters. |
| Interval type | Yes | Hours or Days in the create form. Existing items may use Cycles (see Maintenance intervals). |
| Interval value | Yes | Number in the chosen unit (e.g. 50 for hours, 365 for days). |
| Last completed (date) | When calendar-based | Used to compute the next due date. |
| Last completed value | When usage-based | Meter value at last completion. |
Computed read-only fields:
| Field | Meaning |
|---|---|
| Due at (date) | For calendar-based items: last_completed + interval_value days. |
| Due at value | For usage-based items: last_completed_value + interval_value. |
| Status | One of OK, Approaching, Due Soon, Overdue, Completed. See Behaviour rules. |
Behaviour rules
Section titled “Behaviour rules”- Status calculation is automatic. It is derived from how much interval remains, not stored directly.
- Default thresholds (percentage-based):
- More than 20% remaining → OK
- 10–20% remaining → Approaching
- 0–10% remaining → Due Soon
- Past due → Overdue
- Absolute threshold takes priority. Some items carry a warning threshold value (set automatically when the item is created from a template). When present, the status uses absolute remaining instead of percentage:
- Remaining >
warningThresholdValue × 2→ OK - Remaining ≤
warningThresholdValue × 2→ Approaching - Remaining ≤
warningThresholdValue→ Due Soon - Remaining ≤ 0 → Overdue
- Remaining >
- Overdue grounds the asset. An overdue maintenance item makes the asset not airworthy and prevents new bookings. See Airworthiness rules.
- Completion resets the interval. The item records who completed it, when, and at what meter value, and the due date or due value advances accordingly. The item status becomes Completed until the next interval is reached.
- Completion records include the completing user, the timestamp, the meter value at completion (for usage-based items), and optional notes.
- The pre-booking maintenance check is computed locally. When a member opens the booking dialog, Syndik8 evaluates the asset’s open hours-based and calendar-based items against the synced meter reading and recent usage logs in around 10 ms, entirely on the device with no server call. The amber/red warning surfaces whether the device is online or offline. Calendar items raise an amber warning when the booking ends within 7 days of due. Hours-based items use a projected-remaining estimate based on the member’s recent usage rate.