SIGNALS Docs
Exit Reader View
100%
Theme

Reader View

Equipment tests & Maintenance

Equipment test definitions, performing equipment tests, due status, certifications, and the dispatch gate.

Overview

Equipment tests define reusable safety and maintenance checks — PAT tests, LOLER examinations, service schedules, condition checks — and track when each asset is due, whether it passed, and whether it is safe to dispatch. The engine covers definitions, execution, due computation, certification expiry, auto-repair on failure, and a dispatch enforcement gate.

Equipment test definition routes:

Route Purpose
/equipment-tests Definition index
/equipment-tests/create Create a definition
/equipment-tests/{equipmentTest} Definition detail — fleet compliance, failure ranking, enforcement register
/equipment-tests/{equipmentTest}/edit Edit a definition
/equipment-tests/{equipmentTest}/results Result history for the definition
/equipment-tests/{equipmentTest}/activity Audit trail
/equipment-tests/{equipmentTest}/tabs/{key} Plugin-contributed tabs

Performing an equipment test and reviewing results:

Route Purpose
/assets/{asset}/inspect/{equipmentTest} Perform an equipment test on an asset
/equipment-test-results Equipment test result index
/equipment-test-results/{equipmentTestResult} Result detail with attachments

Defining an equipment test

Enter the name, then work through Enforcement, Certification validity, Schedules, Task list and Catalogue item assignment. Expand More details for the description. Custom fields follow the main form.

A definition is an ordered list of typed tasks:

Task type Captures
Pass / fail A pass or fail
Measurement A number checked against min/max bounds
Check A completed check
Choice A selection from a list
Text Free-text notes

Each definition has a schedule — a time interval, a usage threshold (against a usage metric), or both. When both are set, an asset falls due on whichever comes first. Definitions can be assigned to catalogue items from either the equipment test or the catalogue item; a certifying equipment test also carries a validity period used for certification expiry.

The definition detail page (/equipment-tests/{equipmentTest}) leads with fleet compliance: a per-asset census (clear / due soon / overdue / awaiting first reading, computed on the fly across the applicable fleet), a task-failure ranking drawn from real result snapshots, and an enforcement register listing signed dispatch overrides. Blocked dispatch attempts are not recorded, so only acknowledged overrides appear. Open Fleet → Results for result history or Fleet → Compliance for compliance details. Setup contains Catalogue items and Custom Fields; More → Activity opens the audit trail. Plugins can contribute further tabs.

Performing an equipment test

From the asset detail page, choose Perform Equipment Test and complete the task checklist. The outcome is derived automatically:

  • Pass/fail and check tasks start unset and require an explicit Pass or Fail choice before submission.
  • All required tasks answered and passing → pass (optional failures are ignored).
  • Any required task failing → fail.
  • A required task left unanswered → incomplete.

Task answers are snapshotted, so they survive later edits to the definition. Attachments can be added to the result. A new execution creates a result, while a follow-up submission by the same operator for the same asset and test amends that operator's existing incomplete result.

Equipment test certificates

For a passed result on a certifying equipment test, the result detail page (/equipment-test-results/{equipmentTestResult}) shows Issue certificate to users with equipment-test-certificates.issue. Issuance locks and rechecks the result, issues an existing numbered draft in place or generates one, records the issuer and UTC issue time, and audits equipment_test_certificate.issued. Repeating the action returns the same final certificate without consuming another number. Preview draft remains available to users with documents.create before issue.

There is one certificate per result. It is issued once, is final, and cannot be revoked or re-issued. If an amended result needs certification, create a new equipment-test result and issue that result's certificate. Delivery is download and handover; the result page exposes a Download action for the issued PDF.

The result detail page reads like the certificate it can issue: the computed verdict with its two separate clocks (certificate valid-until and per-test next-due — two different dates), the snapshotted readings with required failures graded, the result history chain for the same asset and test, and a register showing certificate status, issue time, and issuer. An issued snapshot is never silently rewritten if the result later changes; the page shows a mismatch warning instead. The performer and issuer are recorded separately — no signature field exists.

Due status & certifications

For every asset × equipment test, the engine computes the next due date from the last pass (or from asset creation if never tested), against time and/or usage. When a usage-scheduled metric has no readings yet, due degrades to time-only and the asset is flagged awaiting first reading. Cached next_equipment_test_due and equipment_test_status rollups are kept current on every change, with a daily scanner as a backstop. Certifying equipment tests feed a next_certification_expiry rollup and a threshold-gated expiring notification. Due, overdue, failed, and expiring notifications are transition-gated so daily scans do not re-spam.

Auto-repair on failure

A failing equipment test on a definition flagged for auto-repair raises a repair through the shared repair path, linked back to the result. The barcoded conflict policy still applies, and any rejection is audit-logged without blocking the result.

Dispatch enforcement gate

The dispatch pipeline includes an equipment-test gate that runs after the shortage gate. Per definition, enforcement is none, warn, or prevent, evaluated against the rental's off-hire date — so an asset that will fall due mid-hire is flagged before it leaves. The strictest applicable mode wins.

  • Warn — dispatch proceeds only when the operator holds the override permission and records an explicit acknowledgement.
  • Prevent — a hard compliance block that the override cannot relax.

The gate applies to single-asset, bulk, fulfilment batch, and flightcase/kit manifest dispatch, with Inspect Now deep links straight into the perform flow.

Permissions

Permission Grants
equipment_tests.access Access the equipment tests area
equipment_tests.view / .create / .update / .delete Manage equipment test definitions
equipment-test-results.view / .create / .delete Perform and manage results
documents.create Preview a draft equipment test certificate from an eligible result
equipment-test-certificates.issue Issue a certificate in an accessible warehouse
usage-readings.view / .create Capture asset usage readings
equipment_tests.override_dispatch Acknowledge a warn dispatch gate (does not relax prevent)

API

The result API exposes POST /api/v1/equipment_test_results/{result}/certificate/issue, idempotent with Idempotency-Key. It requires equipment-test-certificates.issue and documents:write. The issued document response includes its temporary download URL.

See the Equipment Tests API, Equipment Test Results API, and Usage Readings API.

API field names

Schedule units (schedule_type and certification_validity_type) use day, week, month, or year. Test definitions expose tasks as items. Results expose performed_at, performed_by, notes, outcome, and items. Use these core names in requests and filters; alternate field names return 422 with a message naming the correct field.

Task and result items expose field_type as text, number, boolean, or list, describing the recorded value.