When planned maintenance moves: what should the record preserve?
By Georgios Zografos · Published
Every planned maintenance system lets a due date move. Fewer preserve the decision that moved it. This object sets out what the record should hold when maintenance is re-timed, and what is actually preserved in Full Ahead today.
What independent evidence establishes
Published, citable sources. These are not Full Ahead claims.
- The ISM Code requires the company to establish procedures to ensure the ship is maintained in conformity with rules and regulations and with any additional requirements the company establishes, with inspections held at appropriate intervals and non-conformities reported with their possible cause.
- The Code requires records of maintenance activity to be kept. It does not prescribe a data model, and it does not by itself require that the reason for a re-timing be preserved.
- Rest-hour instruments record declared hours (STCW A-VIII/1, MLC 2006 Reg. 2.3). They say nothing about why a maintenance job moved.
What Full Ahead observes and records
Product behaviour verified in the running system.
- When a maintenance job's due date or tolerance is changed in Full Ahead, the change is accepted only with a written reason above a minimum length.
- The record retains the previous position, the new position, the acting account, the role that account held in the workspace, and the timestamp.
- Evidence attached to the job stays with the job rather than with the person who attached it.
- The audit trail and the hash-chained ledger behind it are append-only in this implementation; update, delete and truncate are refused at the database level, and that refusal is exercised as a test.
What Full Ahead does not currently establish
Stated plainly, so nothing here is read as more than it is.
- Full Ahead does not claim that preserving the decision prevents a deficiency, a detention or a failure.
- Full Ahead does not claim that no other system preserves a reason. What is stated here is how this one behaves, verified in production — not a comparison with any named product.
- Full Ahead does not claim regulatory acceptance. What a surveyor, auditor or inspector makes of any record remains their judgement.
What a technical manager can practically examine
Questions that can be answered from the maintenance record already held, with or without this product.
- Take one vessel and list every maintenance job whose due date moved in the last twelve months.
- For each, ask three questions: who moved it, what reason was recorded at the time, and is the original position still visible.
- Count how many carry a reason recorded on the day, rather than one supplied afterwards during an audit.
- Check whether any of them moved more than once, and whether the sequence of moves is still readable in order.
What the product can currently support
Capability that exists today.
- Enforced written reason on re-timing and on tolerance changes, above a minimum length.
- Actor, role and timestamp bound to the change.
- Append-only storage with alteration and deletion refused at the database level.
- Evidence attachments held with the job.
What remains unvalidated
Open, undemonstrated, and not claimed.
- Whether a preserved decision record changes an audit or inspection outcome has not been demonstrated by Full Ahead and is not claimed.
- Whether the enforced reason improves the quality of the reasons recorded — as opposed to the presence of a reason — has not been measured.
References
Each reference is listed with the specific proposition it supports. No peer-reviewed status is claimed for this page.
- ISM Code, section 10 — Maintenance of the ship and equipment
IMO International Safety Management Code
Supports: Section 10 of the ISM Code covers maintenance of the ship and equipment, inspections at appropriate intervals, reporting of non-conformities and the keeping of records.
- STCW Code, section A-VIII/1 — Fitness for duty
IMO International Convention on Standards of Training, Certification and Watchkeeping
Supports: STCW Code section A-VIII/1 governs declared hours of rest, not maintenance re-timing.
- MLC, 2006 — Regulation 2.3, Hours of work and hours of rest
International Labour Organization
Supports: MLC, 2006 Regulation 2.3 governs hours of work and rest, not maintenance re-timing.