MARINTEK 1 Integrated Emergency Management Ship-Shore coordination Ørnulf Jan Rødseth, MSc Senior...
-
Upload
kevin-roberts -
Category
Documents
-
view
225 -
download
0
Transcript of MARINTEK 1 Integrated Emergency Management Ship-Shore coordination Ørnulf Jan Rødseth, MSc Senior...
1MARINTEK
Integrated Emergency ManagementShip-Shore coordination
Ørnulf Jan Rødseth, MSc
Senior Scientist
Logistics and Technical Operation
MARINTEK
2MARINTEK
Contents
Background
Emergencies and emergency management
Emergency management systems
Emergency management organisation
Support for ship-shore coordination
3MARINTEK
Background – some projects
Autronica AM5000
ITEA-DS
Intelligent Tools for Emergency Applications and
Decision Support
DSS DCDecision Support System for ship
in Degraded Condition
Maritime NavigationInformation Services
4MARINTEK
Background – large passenger ships
M/S Voyager of the Seas: 3114+1181 (1999)
M/S Quen Mary II: 2620 + 1253 (2004)
RCCL Freedom class: 3600 +1400 (2006)
5MARINTEK
Background – environmental damage
The grounding of Arisan near Runde ‘92
Prestige accident outside Galicia ‘03
6MARINTEK
Background - terrorism
M/T Limburg ’02
7MARINTEK
Contents
Background
Emergencies and emergency management
Emergency management systems
Emergency management organisation
Support for ship-shore coordination
8MARINTEK
Some types of emergencies Fire / explosion Stranding/grounding (powered or drift), collision Structural failure (hull, shell doors, tanks, flooding) Pollution (oil spill, chemical spill, on or off ship) Unlawful acts (bomb threat, violence, hijack, arson) System failure (blackout, propulsion, steering) Heavy weather (at sea or in port) Man overboard Medical emergency (injury or illness) Other cargo related problems Assistance other ships
9MARINTEK
Emergency management
Survivability of ship (until abandon ship) Strength and stability
Mustering and evacuation, abandon ship crew and passengers
Situation control avoid escalation, fix problem
Avoid environmental discharge
10MARINTEK
Large passenger ships:What are the main problems?
Large number of persons Many passengers to guide, unfamiliarity with ship Many crew to co-ordinate Panic and congestion, language difficulties
Size of ship and afflicted area 12 passenger decks, 71 m high, 345 m long (QM II)
Landing of passengers and crew Ship as its own lifeboat
11MARINTEK
Cargo ships:What are the main problems?
Few crew to handle situation and do management Requires efficient ship-shore coordination Requires easy to use onboard systems
Generally less money spent on DSS General cargo has higher fatality rate than “higher cost”
ships
12MARINTEK
DSS_DC Lessons learned
1. Emergency operation cargo ships: Very few people
2. Minimize detailed planning or operation onboard
3. Continuous communication with shore office
4. Many alternatives are explored by shore office
5. When to decide? Not too early, nor too late
Must be supported in EMS !
13MARINTEK
Contents
Background
Emergencies and emergency management
Emergency management systems
Emergency management organisation
Support for ship-shore coordination
14MARINTEK
Fire and damage control
15MARINTEK
Control of safety systems
16MARINTEK
Interface to CCTV
17MARINTEK
Electronic plotting table
18MARINTEK
Stability and strength
19MARINTEK
Typical installation on board
ISEMS 1 ISEMS 2
FireVDR
Fire ISEMS 3
Safety room/Bridge
ECR
ISEMS 4
Conning
20MARINTEK
Contents
Background
Emergencies and emergency management
Emergency management systems
Emergency management organisation
Support for ship-shore coordination
21MARINTEK
Emergency management onboard
Bridge and ECR has overall control (ECR for engine spaces) On Scene Commander and Damage Control Teams do local handling Bridge and ECR continues normal operation where applicable Passenger ships may have safety centre and/or hotel section
ECR
Engine spaces
Engine
Bridge
Coordination
Navigation
On SceneCommander
Local mngm.
Damage controlteams
Damage ctrl.
UHF
22MARINTEK
Emergency management on shore
Ship-shore via satellite (SAR and owner) Owner-SAR via telephone Specialist support for strength/stability
Owner/operator
ECC
Specialist
Specialist support
Specialist
Shore - SAR
Rescue
Bridge
Coordination
Navigation
23MARINTEK
Contents
Background
Emergencies and emergency management
Emergency management systems
Emergency management organisation
Support for ship-shore coordination
24MARINTEK
Distributed Emergency Management
Otherservices
SAR
SERS
SAR and special response teams: Via shore office and WWW
Normal operation
Ship basedISEMS
OOW ENG
Normal operation: OOW and maintenance (Engineer)
Shore office
ECC
Land basedISEMS
Shore office Emergency Command Centre
Ship em.
EMT
OSC
DCT
Ship emergency: Emergency Management Team, On-Scene Commander and Damage Control Teams
25MARINTEK
Three-tier emergency management
Ship systems
Navigation/Bridge AutomationSafety Stability
Specialists’ workstations - shore or shipDegraded manoeuvring
and propulsionIntentionalgrounding
Collision andhull damage
Technical conditionmanagement
...
Tactical and strategic planning - Multi-Function Console - Shore and ship
Alarm summaryShip system overviewSpecialist workstation
summary
Weather andsea routing
26MARINTEK
Three-tier emergency managementUse at different positions
Safety centre
MFC
Owner/operator
Engine control room
Ship systems
MFC
Specialist DSS
MFC
Specialist DSS
Specialist support
MFC
Specialist DSS
Shore - SAR
MFC
Hotel section
Ship systems
MFC
Bridge
Ship systems
MFC
Specialist DSS
27MARINTEK
Ship-land communication
Global: Inmarsat, Iridium Coast: VHF, Cellphone, WiMax Regional: VSAT
AMVER plot July 2004Red: > 50; Blue < 4
28MARINTEK
Communication for ship-shore coordination
Available high-seas communication VSAT: Limited areas, high data rates, low cost Inmarsat Fleet 77: 128 kbit/s Inmarsat Fleet 55: 64 kbit/s Inmarsat B: 9.6 – 64 kbit/s Iridium: 9.6 kbits/s
Basic requirements: Should be minimum 64 kbit/s Can use VSAT as main channel, Inmarsat as backup
Main problem is transmission of CCTV images May use still picture or dropped if VSAT is unavailable