Review SIRE 2.0 inspection history, self-assessments, observations and corrective work with vessel and shore teams. Faromo does not replace OCIMF’s official inspection and publication processes.
OCIMF creates a vessel-specific CVIQ for each SIRE 2.0 inspection using vessel type, outfitting, HVPQ, PIQ and booking data. The operator must maintain current PIQ, standard photographs and certificate data in the official system and declare that information accurate and current for the inspection.
Faromo does not reproduce those official submissions or the inspector application. Its internal readiness workflow brings together chapter-level gaps, inspection history, observations and evidence links, root-cause hypotheses and HSEQ CAPA status. The TMSA area remains an admin-only preview until the licensed TMSA 3 content is validated; it must not be used as an official self-assessment or OCIMF submission.
SIRE 2.0 is a controlled OCIMF process spanning operator inputs, a vessel-specific CVIQ, physical inspection, observation response and report publication. Faromo supports the internal readiness and action side of that chain; it is not an OCIMF programme participant, official question compiler, inspection editor or report-publication channel. TMSA 3 separately depends on OCIMF’s paid best-practice publication.[1][2][3][4][5]
The PIQ is a living record. Before inspection, the PIQ, standard vessel photographs and certificates must be reviewed in the official OCIMF environment, with currency and accuracy confirmed through the inspection declaration.
The CVIQ is compiled from vessel type, outfitting, HVPQ/PIQ and booking context. Core, rotational, campaign and conditional questions mean that preparing only for questions seen in a previous inspection is insufficient.
The OCIMF report format separates operator comments into immediate cause, root cause, corrective action and preventative action. The initial comment window is 14 days after release to the operator, and the official response is managed through the OCIMF system.
TMSA 3 is a third-edition 2017 best-practice guide intended to complement IMO conventions and codes. Element and KPI wording must be verified against the current licensed publication obtained by the operator, not Faromo placeholders.
The same information may be tracked in two places, but the authorized system for declarations, inspector records and report publication does not change. This table sets out the current product boundary.
| Workflow | Official process | Current Faromo record | Core data / evidence | Current boundary |
|---|---|---|---|---|
PIQ / REPOSITORIES | PIQ, standard photographs, certificates and the inspection declaration are managed in the OCIMF environment. | Relevant certificates, documents, equipment and readiness records can be referenced during internal review. | Vessel master data, freshness date, file or record link and owner | There is no PIQ completion, OCIMF repository upload, declaration or direct integration. |
CVIQ / INSPECTION | The OCIMF compiler creates a vessel-specific CVIQ; the inspection follows the authorized process and inspector. | A 12-chapter catalog, chapter-level self-assessment summary, target inspection date and inspection history are retained. | Chapter applicability, compliant/partial/non-compliant counts, port, date and inspection metadata | Faromo does not generate a CVIQ, assign official questions or provide physical-inspection or inspector-editor functionality. |
OBSERVATION / CAPA | Negative observations, operator comments, resubmission and publication proceed through the OCIMF workflow. | An observation is tracked with chapter, question reference, category, dimension, description, evidence URL, root-cause hypothesis and HSEQ CAPA link. | Observation text, evidence, responsible CAPA, status and closure date | There is no official operator-comment submission, report resubmission or OCIMF publication connection. |
READINESS SCORE | OCIMF does not publish a 0–100 vessel-readiness score or acceptance threshold; the decision depends on programme-recipient policy. | Faromo calculates an internal indicator from open negative/other observations, report freshness and incomplete self-assessment. | 0–100 value, RAG band and penalty breakdown | Weights and the 85/60 thresholds are Faromo-defined; this is not an OCIMF score, vetting outcome or charterer acceptance. |
TMSA SELF-ASSESSMENT | Company self-assessment follows the current licensed TMSA 3 guide and authorized OCIMF process. | An admin-only period-assessment preview with unverified element titles is available. | Period, draft/review status and internal assessment fields | It is not open for operational use until licensed content is validated and does not make an official TMSA declaration or submission. |
A completed internal record does not mean that the OCIMF declaration, inspector validation, published SIRE report or programme-recipient acceptance is complete.
This operational checklist reconciles official OCIMF actions with internal evidence and action tracking. Current OCIMF documents and programme-participant permissions must be checked separately for every inspection.[1][2][3][4][5]
Faromo is an internal readiness and action-record system. It does not replace the OCIMF SIRE 2.0 system, an authorized inspector, a published report, licensed TMSA 3 content or a charterer vetting decision.
Retain inspection date, port, requesting company, inspector, status, report link and observation counts by vessel.
Track compliant, partial and non-compliant counts by chapter with a target inspection date and superintendent review note.
Record observations with chapter, question reference, category, hardware/process/human/photo dimension, description and evidence URLs.
Link an open observation to a CAPA record and track closure through open, assigned, awaiting-verification and closed states.
Sort the fleet view by lowest internal score first and show observation, report-freshness and incomplete-assessment penalties separately.
Expose period-assessment infrastructure only to authorized admins and do not publish unverified element titles as an operational standard.
The implemented SIRE record workflow keeps inspection history, observations, evidence links, root-cause hypotheses, CAPA status and Faromo’s internal readiness indicator in the same vessel context.
No. Faromo provides internal readiness, inspection-history, observation and CAPA records. PIQ, photograph/certificate repositories, inspection declaration, CVIQ generation, inspector editor, operator-comment submission and report publication remain in OCIMF’s authorized environment.
No. OCIMF does not publish such a score or 85/60 acceptance thresholds. Faromo’s indicator is an internal heuristic using open observations, report freshness and incomplete self-assessment; it does not replace a charterer or programme-recipient decision.
No. The current product stores a 12-chapter catalog and chapter-level self-assessment summary. The vessel-specific CVIQ is generated by the OCIMF compiler from current official inputs; Faromo neither generates it nor assigns official questions.
The official operator comment is entered in OCIMF within the initial 14-day window using immediate cause, root cause, corrective action and preventative action. Faromo retains internal evidence, root-cause hypothesis, HSEQ CAPA link, status and closure date for the same observation, with the two outcomes reconciled separately.
No. The current TMSA area is an admin-only preview. It is not used as an operational self-assessment until element titles and KPI structure are validated against the current licensed TMSA 3 publication, and it does not make an official OCIMF declaration or submission.