Maintenance workload and human performance at sea: what the evidence actually tells a technical manager

What independent evidence establishes

Published, citable sources. These are not Full Ahead claims.

• IMO's guidance on fatigue is issued as MSC.1/Circ.1598, Guidelines on Fatigue (2019), and is the reference document IMO points to on its own fatigue page.
• The guidelines address fatigue across several dimensions rather than a single one: the company and shore management, the seafarer, ship design, and Administrations and port States.
• Maintenance and repair of the ship appears among the management-related factors relevant to fatigue, and inspection and maintenance appear among the ship-specific factors. Workload is identified as relevant.
• Minimum rest requirements are set separately, in STCW Code section A-VIII/1 and in MLC, 2006 Regulation 2.3. Those instruments record declared hours; they are not a measure of workload.

What Full Ahead observes and records

Product behaviour verified in the running system.

• Full Ahead records, for each maintenance job, what was due, what was done, the acting account and role, the timestamp, and — where the product requires it — the written reason for a change.
• That audit trail is append-only in this implementation: update, delete and truncate are refused at the database level, including for ordinary application roles, and the refusal is exercised as a test rather than assumed.
• From the same records the product can compute fixed arithmetic over timestamps: the share of technical work recorded in circadian night hours, how often recorded work moves between unrelated jobs, consecutive days with recorded work and no clear stand-down, and the open critical backlog and priority mix.
• Those work-pattern figures are aggregated to vessel and role. They are never presented as a ranking of named seafarers.

What Full Ahead does not currently establish

Stated plainly, so nothing here is read as more than it is.

• Full Ahead does not establish that any of those figures predict human error, degraded judgement, sleep, alertness, incidents, near-misses or deficiencies.
• Full Ahead does not establish a lead time. No claim is made that a pattern appears any particular number of days before anything.
• Full Ahead does not establish a causal link between a recorded work pattern and an outcome on board.
• Full Ahead does not claim reduced errors, prevented failures, avoided detentions or monetary savings, because none has been established.

What a technical manager can practically examine

Questions that can be answered from the maintenance record already held, with or without this product.

• How much of the technical work on one vessel was recorded during night hours over the last quarter, and whether that share moved.
• Whether the critical backlog on that vessel grew, held or fell across the same period, and what the priority mix did.
• How often a due date moved, who moved it, and whether a reason was recorded at the time rather than reconstructed later.
• Whether the declared rest-hours record and the recorded pattern of maintenance work tell the same story. Where they diverge, that is a question for a competent human, not a finding.

What the product can currently support

Capability that exists today.

• A single maintenance decision record holding schedule, action, actor, role, time and reason together.
• Protection of that record against later alteration or deletion.
• Deterministic arithmetic over the recorded timestamps, aggregated to vessel and role, with a stated sufficiency floor of at least 12 signals across at least 3 distinct days before anything is reported at all.
• Consent-gated capture per workspace: the signals are not collected unless the operator switches capture on.

What remains unvalidated

Open, undemonstrated, and not claimed.

• Live-vessel validation of the work-pattern model has not been done. The signal data behind it to date is seeded internal Full Ahead data, not customer-fleet evidence.
• No accuracy figure is claimed, because none has been established.
• Whether these work-pattern figures carry operational meaning on a specific vessel is exactly what has not been demonstrated, and is stated as such rather than assumed.

References

Each reference is listed with the specific proposition it supports. No peer-reviewed status is claimed for this page.

1. MSC.1/Circ.1598 — Guidelines on Fatigue

   IMO Maritime Safety Committee, 2019

   Supports: MSC.1/Circ.1598 is IMO's Guidelines on Fatigue, and identifies maintenance, inspection and workload among the factors relevant to fatigue.

2. IMO — Fatigue

   International Maritime Organization

   Supports: IMO's fatigue page identifies MSC.1/Circ.1598 as the current guidelines and sets out the company, seafarer, ship-design and Administration/port-State dimensions.

3. STCW Code, section A-VIII/1 — Fitness for duty

   IMO International Convention on Standards of Training, Certification and Watchkeeping

   Supports: Minimum hours of rest for watchkeeping personnel are set in STCW Code section A-VIII/1.

4. MLC, 2006 — Regulation 2.3, Hours of work and hours of rest

   International Labour Organization

   Supports: Hours of work and hours of rest for seafarers are regulated by MLC, 2006 Regulation 2.3.

Related

• Maintenance workload and human factors
• Planned maintenance system
• Hours-of-rest checklist