
Originally Posted by
Allwyn
Again it has been said by Capt. A, Capt. Fran, my self, and others. Your company is suffering from bad communication,
Fair enough, but then a background of what we've been doing to address this. I did make a strong pitch here on the necessity for increased transparency. Good communication does translate from transparency. Increased transparency is the result of good communication. I am sure you will agree this?
First thing between shore-ship. We made it understood that all communication from the office will be addressed to both Master and Chief Engineer. There is no secret communication and no secrets to hide. All telephone conversations in which the Office management suggests something to the Captain or the Chief will not carry weight unless there is a written confirmation: We are carrying out this..blah blah..as per our telecon on so and so date. This is extremely important if you realize. I cannot tell the Master or Chief Engineer something on the phone and leave hhim holding the baby if something goes wrong, while i hide behind plausible deniability.
But guess what, the maximum opposition to the 'end of secrecy' came from which quarters? No prizes, and it was not the Chief Engineers. We also have very smart Captains, who do realize and moan the fact they are being held responsible for IOPP violations. If you are hauled up in a court in South Korea on an IOPP violation, what are you going to tell 'his honor'? I trusted my Chief wrongly, plead guilty? No you are going to say, 'i should not be signing this. And do so only because it is mandated by law/ flag state requirement etc. The person ruly in charge and responsible for this is the Chief Engineer and he is paid for this'. But guess what the Chief does'nt have to sign on the ORB.
Some of this responsibility stuff is good on the golf course and it does awe the uninitiated. But in brick and mortar terms it means little. Even the Exxon Valdez Master got back his license and was full absolved. The pitch in the court house is always a different take. And should be rightly so.
If i try and focus on core responsibilities and take away minor, clerical jobs that take critical focus away, i should be encouraged in this task. Critical redundancy factors are mandated by class on some basic stuff. Operationally over the years, the scope increases over and above the basic minimum that the class recommends. Some engine rooms are difficult to run. Engineers are saddled with sometimes very poor ship designs, radical revamps on these machinery will cost most companies money they cannot afford. The moment ou run those DC ward leonard type cranes, you're talking 100% load on all generators. Charterers don't want delays. On such vessels i am totally dependent on the Chief to keep things moving. Not the Master. If the cranes have to be stopped due to breakdowns, we don't blame Masters. Target the Chief, not ask Master to ensure that breakdowns don't occur. The older a ship gets engineering reliability factors come down drastically. These don't effect the Master on board, they do entail more hardsip and understanding on the Chiefs part. Ofcourse a Master can say i ran a 30 year old ship for 4, 6 months without problems at the end of the day or contract. Looking through the subjectivity of 'running a ship" and identifying who is how critically responsible for what across the board is essential.
Look at it this way, if the Master is caught by law on IOPP, and the Company holds he C/E responsible there is a conflcit. I don't want the Masters signature on the ORB because i don't want him to be responsible for that. The Company cannot fire the Master in case the ORB is not maintained correctly. Masters questioning C/Es superficially on the ORB breeds onboard resentment. And no ship Master can monitor ever IOPP transfer record. Chiefs also cannot, but because he monitors the system extremely closely he is in the right position to be absolutely sworn responsible in the act.
Bookmarks