Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Download
Standard view
Full view
of .
Look up keyword
Like this
2Activity
0 of .
Results for:
No results containing your search query
P. 1
MEPC.1-Circ.736-Rev.2 - Guidance For The Recording Of Operations In The Oil Record Book Part I – Machinery Space Operations... (Secretariat)(1)

MEPC.1-Circ.736-Rev.2 - Guidance For The Recording Of Operations In The Oil Record Book Part I – Machinery Space Operations... (Secretariat)(1)

Ratings:
(0)
|Views: 178|Likes:
Published by Krzysztofeles

More info:

Published by: Krzysztofeles on Dec 23, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

05/13/2014

pdf

text

original

 
 I:\CIRC\MEPC\01\736-Rev-2.doc
 
4 ALBERT EMBANKMENTLONDON SE1 7SRTelephone: +44 (0)20 7735 7611 Fax: +44 (0)20 7587 3210
MEPC.1/Circ.736/Rev.26 October 2011 
GUIDANCE FOR THE RECORDING OF OPERATIONS IN THE OIL RECORD BOOKPART I – MACHINERY SPACE OPERATIONS (ALL SHIPS)
1 The Marine Environment Protection Committee, at its sixty-second session,(11 to 15 July 2011), approved a revised text of the Guidance for recording of operations in theOil Record Book Part I – Machinery space operations (all ships) (MEPC 62/24, paragraph 7.23),set out in the annex.2 The Guidance is intended to facilitate compliance with MARPOL requirementson board ships by providing advice to crews on how to record the various operations in the OilRecord Book by using the correct codes and item numbers in order to ensure a more uniformport State control procedure.3 Administrations of Parties to MARPOL are invited to encourage implementation of theannexed Guidance for use aboard ships flying their flags and to disseminate it among allstakeholders including ship operators, surveyors and port State control officers.4 This circular revokes MEPC.1/Circ.736/Rev.1.***
 
MEPC.1/Circ.736/Rev.2Annex, page 1
I:\CIRC\MEPC\01\736-Rev-2.doc
ANNEXGUIDANCE FOR RECORDING OF OPERATIONS IN THE OIL RECORD BOOKPART I – MACHINERY SPACE OPERATIONS (ALL SHIPS)General Guidance
This guidance only includes sections C to I.
Operations should be recorded in chronological order as they have been executedon board.
Dates should be entered in dd-MONTH-yyyy format, e.g. 16-MAR-2009.
Incineration or landing ashore of oily garbage and used filters should be recorded in theGarbage Record Book only.
All Entries are to be made and signed by the officer or officers in charge of the operationsconcerned and each completed page shall be signed by the master of the ship.
Do not leave any full lines empty between successive entries.
If a wrong entry has been recorded in the Oil Record Book (ORB), it should immediatelybe struck through with a single line in such a way that the wrong entry is still legible.The wrong entry should be signed and dated, with the new corrected entry following.
Tank nomenclature should be recorded as per the format noted within the InternationalOil Pollution Prevention Certificate (IOPPC).
Recording of quantities retained in bilge water holding tanks listed under section 3.3 ofthe IOPPC is voluntary and not required by the Convention.
The recording of general maintenance of items pertaining to the OWS remains voluntaryand is not required to be recorded in the ORB.
Usage of code C.11: Collection of oil residues (sludge)
Example #1Weekly inventory of oil residues (sludge) tanks (tank listed under item 3.1 in the Supplement tothe IOPPC)
Date Code Item No.Record of operations/signature of officer in charge 
dd-MONTH-yyyy
 C 11.1 [Name of sec 3.1 Tank & Designation] 11.2 xx
 11.3 xx
 signed: (Officer-in-charge, Name & Rank)
dd-MONTH-yyyy
 
dd-MONTH-yyyy
 C 11.1 [Name of sec 3.1 Tank & Designation] 11.2 xx
 11.3 xx
 signed: (Officer-in-charge, Name & Rank)
dd-MONTH-yyyy
 

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->