This page is the system map for the vessel maintenance deferrals guide, which explains why these records matter. Here the focus is narrower: where each record lives, which identifier joins it to the next one, and who administers each system.
The five systems that hold one postponed job
A postponed job rarely lives in one place. The planned maintenance system holds the job card, but the reasoning and the evidence spread out from there into mailboxes, purchasing and document folders, each with its own numbering.
| System | Records it holds | Linking key it carries | Owner or administrator |
|---|---|---|---|
| Planned maintenance system | Defect reports, deferral or postponement requests, closing work orders, running hours | IMO number, equipment code, job number, deferral reference | Technical department, fleet superintendents |
| Superintendent email | Office approvals, conditions, questions to the crew | Postponement reference if quoted; otherwise ship name and date | Each superintendent; email policy set by IT |
| Document control or safety management system | Non-conformity reports, risk assessments, procedure versions | Report number, sometimes the job number | Designated person ashore or quality manager |
| Purchasing module or ERP | Parts requisitions, purchase orders, delivery notes | Job number on the requisition, PO number | Purchasing, finance |
| Vendor and class records | Service engineer reports, survey reports, conditions of class | PO number, IMO number, survey date | Technical department |
The ship key is the most stable. IMO describes its ship identification number as permanent: it stays the same through changes of flag, name or ownership and appears on the ship's certificates. Internal keys are less stable. Equipment codes and job numbers belong to whichever system issued them, so they can change when a new manager takes over or a new system is installed.
Which key joins which record
Five joins carry a postponed job from finding to closure. Each has a typical weak point.
| Join | From | To | Key | Where it usually breaks |
|---|---|---|---|---|
| 1 | Defect report | Postponement request | Job number on both | Defect raised as a free-text note with no job number |
| 2 | Postponement request | Office approval | Postponement reference quoted in the approval | Approval given by phone or in a thread with no reference |
| 3 | Office approval | Parts requisition | Job number on the requisition | Requisition raised in a purchasing module that does not ask for it |
| 4 | Parts requisition | Service report | PO number or job number | Vendor report filed under the ship, not the job |
| 5 | Service report | Closing work order | Job number and running hours | Job closed with "done" and no evidence attached |
Joins 2 and 4 cross a system boundary into tools the planned maintenance system does not control. That is why they fail most often, and why a reviewer asks about them first.
There is a regulatory reason the chain matters. IMO guidance on implementing the ISM Code says the Company determines and initiates corrective action for a non-conformity, and that corrective action should not normally exceed three months. A deferral history that joins across systems can show when the problem was found, when the action was decided and when it was closed; one that does not can show only that a job was eventually closed.
One ballast valve case, fully joined (Illustrative)
Illustrative. A fictional 230-person ship manager operates nine product tankers. Every reference below is invented.
| Step | Record | System | Key that carries it forward |
|---|---|---|---|
| 1 | Hydraulic leak found on a ballast valve actuator during rounds | Planned maintenance system, defect report | Job 4471, equipment code BAL-V12 |
| 2 | Repair postponed to next port; valve locked in position, daily checks | Planned maintenance system, postponement form | Reference DEF-0388, citing job 4471 |
| 3 | Superintendent accepts the postponement with conditions | Superintendent email | Subject line quotes DEF-0388 |
| 4 | Seal kit ordered for delivery at port | Purchasing module | Requisition cites job 4471; PO 77120 |
| 5 | Service engineer replaces the seals and tests the actuator | Vendor report, filed in document control | Report cites PO 77120 |
| 6 | Job and postponement closed with test result and running hours | Planned maintenance system, closing work order | Job 4471, DEF-0388 closed |
Every join holds because each record quotes the key of the one before it. Take away the reference in step 3, and the approval can only be found by searching a mailbox for the ship name in the right week. Take away the PO citation in step 5, and the service report sits in a folder with no path back to the deferral. The fleet maintenance records page describes the same problem when trucking asset IDs change.
A twenty-chain test the technical team can run
A partner does not need to see a single record to learn how well the chains hold. Ask the technical team to pick twenty closed postponements from at least two years ago, chosen at random, and report three counts:
- Chains that rebuild by reference alone.
- Chains that need one match by date and wording.
- Chains that break.
Ask for the counts and the weakest join, never the records. SourceX publishes no benchmark for a good result; the counts are a starting picture for its review. The logistics exceptions guide uses a similar join test on shipments.
Two events often break chains at scale. A handover between managers where the incoming manager loads only open jobs leaves every closed join in the outgoing system; the retention timeline covers that case. And a system replacement can renumber equipment codes, which breaks join 1 for all older history unless a cross-reference was kept; the CMMS migration guide covers export checks for land-based systems.
Who controls each system, and what that means for licensing
Administering a system is not the same as owning its records. In ship management, the agreement between owner and manager decides that. BIMCO's SHIPMAN 2024, the industry's standard ship management agreement, added provisions on access to and ownership of vessel data held in the managers' information system. So the same deferral chain may cross systems the manager runs and records the owner controls. The who-can-license page sets out who can approve a discussion.
At metadata level, the partner can confirm: which of the five systems exist, how many ships and years each covers, roughly how many postponements a year, and whether the job or postponement reference appears in email and purchasing records. The company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 90% of the data is in English.
Unknown until SourceX reviews it: buyer interest, how crew names and ship identifiers would be treated in preparation, the rights split between owner and manager, and any offer. Partners sign the Channel Partner Agreement before submitting introductions. Why linked maintenance histories matter for AI work is covered in maintenance data for AI training.
Next step
Refer a company. Earn up to $100,000. Default reward: 25% of Actual Supplier Payout, capped at $100,000 cumulatively per referred company. Eligibility and payment conditions apply, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.
If a ship manager's twenty-chain test shows most chains still rebuild by reference, register as a partner, confirm the company on who qualifies and read the terms before you introduce the technical director.