130 likes | 206 Views
VESSEL SAFETY. Version 1.0 01-Jul-2015. Version 1.0 01-Jul-2015. Safety is an absolute priority in ATI.
E N D
VESSEL SAFETY Version 1.0 01-Jul-2015 Version 1.0 01-Jul-2015
Safety is an absolute priority in ATI. On the 15th of September, 2013, a vessel crew member was killed during cargo discharge operations. A major contributory factor to the incident is the substandard lighting condition inside the vessel. In our effort to prevent similar incidents, ATI is issuing this safety handout as a guide for vessels on various unsafe conditions inside a vessel and the safety requirements that must be implemented to address them. In the event that similar unsafe conditions are found in any vessel, ATI reserves the right to cease operations until the unsafe condition is fully rectified. Please note that unsafe conditions are not limited to the circumstances included in this handout. Operations may be delayed or may cease if the safety of personnel are compromised. We will issue updates of this handout to capture other situations that may be observed in the future. If you have any questions or have any concerns, please don’t hesitate to call +632 528 6000 Loc. 332 to speak to an ATI Safety Officer. A good quality stowage plan must be provided to ATI. Vessel may be asked to rework the cargo if there are major deviations from the presented plan. Version 1.0 01-Jul-2015 Version 1.0 01-Jul-2015
UNSAFE SAFE Based on stowage presentation, stevedores are expected to step on the cargo to lash them. Lifting points are not readily identifiable on some of the cargo. The steel structures are stowed precariously and are not individually lashed. Cargoes may collapse if unlashed. Vessel may be required to rework cargo stowage before discharge operations can commence. Version 1.0 01-Jul-2015 Version 1.0 01-Jul-2015
UNSAFE UNSAFE SAFE Insufficient lighting of Cargo Hold passageways. Must maintain 20 lux minimum lighting in passageways. SAFE Insufficient vessel lighting. Must maintain 50 lux minimum lighting at work areas. Version 1.0 01-Jul-2015 Version 1.0 01-Jul-2015
UNSAFE Missing pins or pins that do not completely fit through the lock will not be acceptable UNSAFE SAFE SAFE Manhole Covers Must be secured properly Unprotected Cargo hold access ways Vessel will be asked to provide guardrails around the open manhole if it needs to be used as an accessway during the course of operations. Hazards: • Door may shut while stevedores are going down leading to loss of balance and falling. • Door may hit stevedores • Door may pin/pinch body parts of stevedores Version 1.0 01-Jul-2015 Version 1.0 01-Jul-2015
UNSAFE UNSAFE Poor passageway housekeeping UNSAFE Clear Passageways Inadequate protection or unprotected Leading Edges Vessel must provide railings that are: • Minimum 1-meter high • Supporting stanchions must be maximum 2-meters apart • Guide rails/rope must be taut (not sagging) SAFE Vessel will be asked to clear passageways before ATI will begin operation. Version 1.0 01-Jul-2015 Version 1.0 01-Jul-2015
UNSAFE UNSAFE SAFE SAFE Inappropriate or improperly placed extension gangplanks Improper Gangway placement Version 1.0 01-Jul-2015 Version 1.0 01-Jul-2015
UNSAFE UNSAFE Broken Strands on Cargo Runner Vessel will be required to replace the cargo runner and undergo class survey before operation can commence. SAFE Unevenly Spooled wire rope on winch drum. Wire rope may slip causing the load to suddenly drop. Version 1.0 01-Jul-2015 Version 1.0 01-Jul-2015
UNSAFE UNSAFE Unevenly stacked hatch covers that block the view of signalmen/ supervisors into the cargo hold. • Hatch covers must be stowed to allow signalmen and supervisors a clear view of the cargo hold. • Hatch cover may be stowed on the apron to allow for unobstructed view Unsafe hotworks devices/activities. • Gas cylinders must always be kept upright and chained to prevent toppling • Hoses must not have defects or extended with hose joints Version 1.0 01-Jul-2015 Version 1.0 01-Jul-2015
UNSAFE SAFE Hooks without safety latches. Load may be displaced and slip from the hook should the operator make an operational error. Version 1.0 01-Jul-2015 Version 1.0 01-Jul-2015