Ballast Water Record Book Assistant: IMO MEPC.369(80)

Q: What key amendments were introduced under IMO Resolution MEPC.369(80)?

Resolution MEPC.369(80) introduced the revised BWRB format: establishing mandatory Code F logging for separate reporting of BWMS failure and restoration, clarifying D-1/D-2 wording, and standardizing circulation and port reception facility codes.

Q: Should ballast operation times be logged in Ship's Local Time or UTC?

All operational timestamps in the Ballast Water Record Book must be recorded in Coordinated Universal Time (UTC) followed by the designator hrs UTC as instructed by IMO BWM.2/Circ.80.

Q: How must a BWMS failure and its subsequent restoration be recorded (Code F)?

Code F is deployed as two distinct entries: the first records the time, operation, and nature of the equipment failure, while the second documents the completion of repairs, testing, and system restoration.

Q: Who is required to sign off the individual entries and completed log pages?

Each completed ballast operation must be signed by the Officer in Charge, and each completed page must be reviewed and counter-signed by the Master.

Q: Are vessel particulars and historical log entries preserved across browser sessions?

Yes, vessel profile parameters and cumulative record entries save automatically to browser LocalStorage and can be exported as CSV or JSON files.

🚢 Vessel Profile: (Click to edit)

▼ Edit

📝 1. Select Operation Code

Code A: Ballast Water Uptake

1. Start Time (UTC) & Loc:

2. Comp. Time (UTC) & Loc:

2. Min Depth (if at sea): (optional)

4. Uptake Vol (m³):

4. Final Retained (m³):

5. Compliance Standard: 6. Treatment Method:

Code B: De-ballasting (Discharge to Sea)

1. Start Time (UTC) & Loc:

2. Comp. Time (UTC) & Loc:

2. Min Depth (if at sea):

4. Discharged Vol (m³):

4. Final Remaining (m³):

5. Compliance Standard: 6. Treatment Method:

Code C-1: Ballast Water Exchange

1.1 Start Time (UTC) & Loc:

1.2 Comp. Time (UTC) & Loc:

1.3 Distance & Depth or Area: 1.4 Method (BWMP):

1.6 Exchanged (m³):

1.6 Retained (m³):

1.7 Treatment of Incoming Water:

Code C-2: Internal Treatment / Circulation

2.1 Start Time (UTC):

2.2 Comp. Time (UTC):

2.4 Treated Vol (m³):

2.5 Treatment Method:

Code D: Discharge to Port Reception Facility

1. Start Time (UTC) & Loc:

2. Comp. Time (UTC) & Loc:

4. Discharged Vol (m³):

4. Remaining (m³):

5. Reception Facility Name:

5. Receipt / Certificate Ref:

6. Compliance Statement: 7. Additional remarks / Documentation:

Code E: Accidental / Exceptional Ingress or Discharge

1. Date & Time of Occurrence (UTC):

2. Location & Water Depth:

3. Estimated Volume (m³):

4. Event Nature:

5. Circumstances and Reason: 6. Action Taken, Treatment & Notifications:

Code F: BWMS Inoperability / Failure Entry Sub-Type:

1. Time (UTC) & Loc of Failure:

2. Operation Conducted:

3. Description of Failure / Alarm / CWQ: 4. Status / Time Operational:

Code G: Tank Cleaning / Flushing & Sediment Removal

1. Start Time (UTC) & Loc:

2. Comp. Time (UTC) & Loc:

4. Method of Cleaning & Disposal:

5. Quantity of Sediments Disposed:

5. Receipt / Certificate Details:

Code H: Additional Procedures & General Remarks

1. Date & Time (UTC) & Loc:

2. Equipment / Tanks Involved:

3. Description of Operation / Remark: 4. Quantity (m³) or Additional Details: (optional)

📋 Generated Entry Preview

Date (dd-mmm-yyyy)	Code (letter)	Item (number)	Record of operations / signature of officer in charge

📖 BWRB Logbook (Stored Records) 0 lines

Date	Code	Item	Record of operations / signature	Action
No records stored in local logbook. Generate an entry and click "Add to Logbook".

Action completed

Environmental Compliance Hub IMO // MEPC.369(80) • BWM.2/CIRC.80

Passage Planner Pro ↗ Steaming Time & Laytime ↗ DWA / FWA Calculator ↗

Ballast Water Record Book Assistant: Standardized Logging Under IMO MEPC.369(80)

Maintaining an accurate and legally compliant Ballast Water Record Book (BWRB) is a critical statutory requirement under Regulation B-2 of the International BWM Convention. Incomplete entries, erroneous operational codes, missing item numbers, or discrepancies between logbook remarks and Ballast Water Management System (BWMS) electronic event files trigger heavy deficiencies and potential detention during Port State Control (PSC) inspections and commercial vetting audits under OCIMF SIRE 2.0.

The NavLib BWRB Assistant automates official entry compilation in strict accordance with the updated IMO Resolution MEPC.369(80) standards and the instructional guidance of circular BWM.2/Circ.80. The software removes recording ambiguity across all designated operational codes (Codes A through H), enforces mandatory UTC timekeeping, maintains an accumulated browser log, and provides isolated DOM printing for standard A4 shipboard log sheets.

Regulatory Framework

Codes A to H Engine

Standardized entry formulation for Uptake (Code A), Discharge (Code B), Circulation (Code C), Port Reception (Code D), Accidental Ingress (Code E), and Cleaning (Code G).

BWMS System Status

Code F Logging Protocol

Strict two-step chronological reporting protocol separating the initial equipment failure/inoperability event from the subsequent operational restoration entry.

Audit & Archiving

A4 Print, CSV & Backup

Automatic vessel profile retention, spreadsheet export (CSV), lossless JSON file backup, and isolated DOM A4 printing for official shipboard record binders.

Frequently Asked Questions: Ballast Water Record Book Compliance (FAQ)

What key amendments were introduced under IMO Resolution MEPC.369(80)?

Resolution MEPC.369(80) revised the format and entry structure of the Ballast Water Record Book. Key updates include: mandatory deployment of Code F for separate logging of BWMS inoperability and its subsequent return to service; standardized terminology distinguishing between Regulation D-1 (Exchange) and D-2 (Performance Standard); and explicit entry items for internal circulation (Code C) and discharge to port reception facilities (Code D).

Should ballast operation times be logged in Ship's Local Time or UTC?

Pursuant to the operational instructions of IMO circular BWM.2/Circ.80, all start and completion timestamps in the Ballast Water Record Book must be entered in Coordinated Universal Time followed by the designator (e.g., 1400 hrs UTC). This ensures exact alignment between handwritten records and the internal automated datalogger of the type-approved BWMS unit.

How must a BWMS failure and its subsequent restoration be recorded (Code F)?

Under MEPC.369(80), Code F requires two distinct chronological entries:

Failure Occurrence: logs the time/port of the malfunction (Item 1), the operation being conducted (Item 2), the specific failure/alarm description or bypass details (Item 3), and current operational status (Item 4).
System Restoration: logged when the unit is repaired and tested, documenting time/location of restoration (Item 1), system identified (Item 2), rectification details (Item 3), and verification statement (Item 4).

Who is required to sign off the individual entries and completed log pages?

Each completed ballast operation must be signed without delay by the Officer in Charge of the operation (typically the Chief Officer). Each completed page of the Ballast Water Record Book must be formally reviewed and counter-signed by the Master of the vessel.

Are vessel particulars and historical log entries preserved across browser sessions?

Yes. The vessel profile (Ship name, IMO number, Flag), current form draft, and accumulated log lines persist securely within local browser memory (LocalStorage). For permanent voyage archiving or file sharing between bridge computers, the tool includes one-click export to CSV and JSON formats.

Regulations: BWM Convention Reg. B-2, IMO Res. MEPC.369(80), BWM.2/Circ.80

Inspections: PSC (Paris/Tokyo MoU, USCG), Flag State Administration, OCIMF SIRE 2.0

Engine: Extreme DOM Isolated Print (A4), CSV Export, JSON Backup

BWRB Assistant

Ballast Water Record Book Assistant: Standardized Logging Under IMO MEPC.369(80)

Frequently Asked Questions: Ballast Water Record Book Compliance (FAQ)

Leave a ReplyCancel reply