Trust & Proof

Marine Engine-Room Spare Parts
Supply Case Notes

A public-safe framework for future, evidence-backed process notes

Evidence-gated by design

A safe case-note framework separates useful process detail from unsupported proof.

This page is a publication framework, not a record of completed Vessel Core jobs. A future case may be published only after factual evidence, confidentiality review, counterpart approval and accountable human sign-off.

Its purpose is practical: define how a future approved note could explain the supply-route process and help ship managers and purchasing teams understand what information makes an RFQ easier to review.

Case-note patterns

These formats show how technical evidence, supply route and vessel timing can be summarized safely.

Evidence

What to attach to a spare parts RFQ

The set common to every pattern above. The more of it that arrives at once, the fewer clarification emails stand between the request and a quotation.

  • Maker, equipment make and type, and the build as it reads on the nameplate
  • Serial number, and a photograph of the whole nameplate rather than a crop
  • Part number, designation or a previous order reference
  • Part-book page or a drawing of the assembly
  • Quantity per line, and the unit it is counted in
  • Close-up of the part and a general view of the assembly
  • Installed position and what the part does in the system
  • Hours run since new and since the last overhaul
  • How it failed or why it is being replaced — measured wear, scoring, leakage, fracture
  • Port of call and ETA
  • The buyer's approval and documentation requirements
  • Class requirements: whether a class certificate or a works certificate of conformity is needed
  • Contacts for technical clarification, on board and in the office
  • A line-by-line list in Excel or PDF, numbered

None of this is mandatory to start. A request with three of these fields is still a request — it simply takes more passes to reach the point where a quotation can be prepared, and each pass costs a day the vessel may not have.

Review order

How a request is reviewed

The sequence is the same for every pattern: technical identification first, documentation requirements second, and only then the supply route.

Confirmed is separated from assumed

The review marks explicitly what is documented — by a nameplate, a part-book page, a drawing — and what stays an assumption until the vessel answers. An assumption is never carried into a quotation as a fact.

Identification before routes

Until a designation resolves to a part-book page or a previous order reference, discussing a supply route is premature. An engine make or series on its own confirms no line of the request.

Documentation and class certification

Where class requirements apply to a line, the review records which class certificate the buyer needs and whether it is requested from the maker. That changes which routes are even reviewable.

OEM or alternative is the buyer's call

For running spares and planned maintenance, verified alternative routes are reviewed where approval requirements permit. For class-surveyed work an OEM-route review can be requested. See OEM or alternative.

The schedule is recorded, not promised

Port of call and ETA are needed to weigh handover and documentation. The review carries no firm delivery commitment: terms are confirmed only in the quotation for that specific RFQ.

Confidentiality is checked before publication

Before any pattern reaches this site, identifying buyer, vessel and supplier detail is removed. Publishing a real case requires written agreement from the counterpart and sign-off by an accountable person at Vessel Core.

Publication workflow

Every public case note should pass a confidentiality and claims check.

Before a case note is published, remove vessel names, IMO numbers, buyer names, supplier identities, prices, tracking numbers and document screenshots unless written approval exists.

The note should describe the category, evidence received, missing information, supply route logic and what improved RFQ quality. It should not imply fixed delivery timing, stock availability or official dealer status.

For public trust, a documented process note is stronger than a dramatic claim. A future approved note should show how the technical supply context was reviewed without overpromising.

Case-note FAQ

The approval boundary for future public case-note material.

Are these public client testimonials?

No. Case notes are process explanations and anonymized patterns. They do not replace verified reviews or approved client references.

Can Vessel Core publish a real case?

A future case can be considered only after its facts are documented, confidential data is removed, the counterpart approves any identifying details and an accountable person signs off the final wording.

What makes a case note useful for buyers?

It should show what evidence was useful, what was missing, how the supply route was reviewed and how buyers can send clearer RFQs.

What never appears in a public RFQ case note?

Vessel names and identifiers, buyer and supplier names, prices and commercial terms, counterparty documents, screenshots of correspondence, and any claim about lead time, stock or special status with a manufacturer. Lead time and price are confirmed only in the quotation for that specific RFQ.

Prepare a better RFQ

Send the evidence behind the request.

Attach vessel, equipment, part evidence, quantity, urgency and port / ETA. Photos, nameplates, drawings and Excel lists help structure the review.