Correct book, complete fields
Capture the operation against the official format for the applicable annex and part; do not complete the entry until conditionally required fields are present.
A digital form is not the same as an approved electronic record book.
Electronic record books under MARPOL have been available as an alternative to paper since 1 October 2020. The electronic BWRB option under the BWM Convention entered into force on 1 October 2025. Under both regimes, the electronic system requires approval by the relevant Administration and a written declaration of approval onboard.
The current Faromo workflow captures operations through book-specific fields, allocates vessel-level sequential entry numbers, stores officer and master fields and, for ORB, GRB and BWRB, links corrections as new entries instead of deleting the original. This scope does not by itself constitute flag approval, type approval or authorization to discontinue paper records.
An electronic book derives its value from record control, not the form alone.
IMO guidelines address more than displayed fields: user identity, amendment history, verification status, retention, backup and true-copy output are also part of the control environment. The model below separates official expectations from Faromo’s currently implemented scope.[1][2][3][4]
Identity, verification and amendment trail
Manage unique user identity, role-controlled access, officer and master verification and a reasoned amendment trail that leaves the original record visible.
Retention, backup and true copy
Acceptance-test the applicable retention period, offline backup, recovery procedure and output showing the responsible person, amendments, software version and pagination.
Book coverage and current control boundary
The table describes Faromo’s current data and workflow coverage. “Covered” does not mean Administration approval has been granted for a specific vessel and software version.
| Book | Regime | Record held in Faromo | Signature and correction | Current boundary |
|---|---|---|---|---|
ORB | MARPOL Annex I · Part I | A–I operation code, item code, tank, quantity, date-time and position | Officer and master fields; a new correction entry through correctionOf | ORB Part II is out of scope; official output and Administration acceptance require separate verification. |
GRB | MARPOL Annex V | A–K category, disposal method, quantity, position, port and receipt number | Officer and master fields; linked correction preserving the original | Conditional-field controls, receipt attachment and approved true-copy output require pilot testing. |
ODS | MARPOL Annex VI · Reg. 12 | Operation type, equipment, substance, kg, facility/supplier and applicable position | Officer and master fields; correction linkage | The current workflow is web-based; offline mobile and additional integrity controls are out of scope. |
BWRB | BWM Convention | Operation, tanks, volume, position/port, BWMS use and parameters | Officer and master fields; linked correction preserving the original | The electronic option has been in force since 1 October 2025; vessel-specific Administration approval is required. |
Cargo Record Book, ORB Part II, fuel-oil changeover, NOx tier/on-off and engine-parameter record books are not included in the current-scope claim on this product page.
What should be verified before paperless use on a pilot vessel?
A software demonstration is not an acceptance test. Vessel type, applicable book part, flag instructions and real operational scenarios must be verified in one pilot plan.[1][2][3][4]
- Applicability Define the book and part in scope: Map each vessel’s required book, part, operation codes and retention period to flag instructions and the company SMS.
- Approval Verify Administration approval and the onboard declaration: Obtain the written declaration for the software version in use and keep it accessible onboard for inspection.
- Fields Test conditionally required fields: Using real scenarios, verify that an entry cannot close without applicable date, position, tank, quantity, category and explanatory fields.
- Identity Test user and signature separation: Check unique login, authorization matrix, officer-master separation, authentication standard and role boundaries for the same user.
- Correction Preserve the original and reverification: Verify that correction reason, user, time, changed value, original entry and reverification status appear together in output.
- Supporting record Link receipts and endorsements: Test linkage and long-term access between the entry and port receipts, external records and authorized endorsements.
- Continuity Run a backup and recovery drill: Exercise connectivity and power loss, device failure, offline backup, restoration and access throughout the retention period.
- True copy Inspect the audit output end to end: Verify output containing the responsible person, signatures, amendments, print time, software version, page numbering and required endorsements.
Faromo’s feature scope must not be interpreted as approval or certification by any flag Administration. Paper records should be discontinued only after the relevant approval is complete.
Scope and core capabilities
Four distinct record workflows
Manage MARPOL ORB Part I, GRB and ODS separately from the BWM Convention BWRB.
Code-driven capture
Create structured entries with book-specific operation codes, categories, methods and technical fields.
Sequential entry numbering
Keep vessel- and book-level entry numbers unique even during concurrent capture.
Officer and master fields
Keep officer and master verification fields with the entry on endpoints restricted to relevant role groups.
Linked correction
For ORB, GRB and BWRB, link a new correction to the original entry number without deleting the mistaken entry.
Selected offline mobile flow
Queue ORB, GRB and BWRB entries locally in the native app; current ODS coverage is limited to the web.
Workflow
- Select the correct book: Identify the vessel, regime, book part and operation code.
- Capture the operation: Add date-time, quantity, tank, position and conditionally applicable fields.
- Verify the entry: Complete relevant officer and master fields with role and time context.
- Continue correction and shore follow-up: Preserve the original when an error occurs, then monitor the linked correction and the vessel’s latest record status.
Operational outcomes
- Avoid forcing four book workflows into one generic free-text screen.
- Keep the original entry and later correction in one inspection trail.
- Give vessel and shore a shared view of the latest entry date.
- Turn technical and operational gaps into a visible checklist before flag approval.
Product evidence
ORB, GRB, ODS and BWRB record chain
Operational entry, sequential record number, officer and master fields, and correction linkage remain in vessel context.
Frequently asked questions
Is Faromo an electronic record book approved by a flag Administration?
This page does not claim approval by any Administration. Statutory paperless use depends on written approval and an onboard declaration for the vessel, flag, applicable book and software version in use.
Which books are in the current scope?
The web application includes ORB Part I, GRB, ODS and BWRB data workflows. ORB Part II, Cargo Record Book, fuel-oil changeover and NOx records are not included in the current-scope claim on this page.
Can an incorrect entry be deleted?
The ORB, GRB and BWRB service flow does not use physical deletion; a new record links to the original entry number through correctionOf. ODS includes correction linkage, while additional integrity controls require separate verification during pilot acceptance.
Can entries be created without connectivity?
The native app can queue ORB, GRB and BWRB creation locally and submit entries after connectivity returns. ODS currently uses the web workflow. A real vessel pilot must separately test sessions, duplicate delivery, recovery and official output.
Primary sources
- Guidelines for the Use of Electronic Record Books under MARPOL (MEPC.312(74)) — International Maritime Organization
- MARPOL amendments on electronic record books (MEPC.314(74)) — International Maritime Organization
- Guidelines for the Use of Electronic Record Books under the BWM Convention (MEPC.372(80)) — International Maritime Organization
- BWM Convention amendments on electronic record books (MEPC.383(81)) — International Maritime Organization