EMSA's Integrated Maritime Environment. - a tool for improved ... and ship
security, EMSA has the following main objectives: •. To ensure the .... (e.g email,
pdf).
EMSA’s Integrated Maritime Environment - a tool for improved Maritime Domain Awareness
October 2012 1
Justino de Sousa European Maritime Safety Agency C.3.1 Integrated Maritime Data
Introduction : the European Maritime Safety Agency (EMSA) Background: • Post Erika (2002: EMSA established, started in 2003) • Legal basis: Regulation 1406/2002/EC Regulatory Agency of the European Community • Own legal identity • Technical and operational support
2
Extending EMSA’s mandate November, 2002 - Prestige sinks off Galicia, Spain
3
Objectives of EMSA Within the fields of maritime safety, pollution prevention from ships and ship security, EMSA has the following main objectives: •
To ensure the proper implementation of EU maritime legislation by Member States
•
To foster technical cooperation and development and disseminate best practice
•
To provide technical advice to the Commission and Member States
•
To provide assistance to top-up Member States‟ capabilities for oil pollution response
4
IMDatE Project Background – Operational and Legal Context 1. Maritime Domain Awareness (MDA) is defined as the effective understanding of anything associated with maritime activities that could impact the security, safety, economy, or environment. 2. A complete maritime picture, at least at Regional level where neighbouring countries share the same maritime interests, provides substantial added value for a better Maritime Domain Awareness in the area of interest. 3. Following the adoption of the EU Integrated Maritime Policy (IMP) in 2009, EMSA has embarked on the project of integrating its maritime systems into a powerful and flexible operational platform called the Integrated Maritime Data Environment (IMDatE).
5
Project Background – Maritime Integration Principles Integrated maritime data for maritime awareness Ship reporting data
Satellite image vessel detections
S-AIS, T-AIS, VMS, LRIT “vessel positions” SAR and Optical Vessel detection “satellite detections” 6
Fusion and correlation of data
Service deliverables tailored according to user requirements Cooperative and noncooperative targets highlighted
Integrated vessel information “non-identified targets”
Project Background – The EMSA Maritime Applications IMDatE integrates data and services from 4 critical maritime applications – the main ones that EMSA is tasked to host and operate, namely: 1. SafeSeaNet (SSN) – the European coastal system of over 700 shorebased AIS receiving stations which automatically tracks all ships navigating within 100 Nautical miles (Nm) from the EU coastline, and receives and stores information concerning the cargo and voyages of vessels;
2.
EU LRIT DC (LRIT) – is the European Long Range Identification and Tracking Data Centre using communication satellites to track all ships (around 10,000) under EU flags all over the world, as well as any ship, irrespective of its flag, within a maximum 1,000 Nm from the EU coastline;
3.
CleanSeaNet (CSN) – the EU satellite-based system for detection of oil spills and vessels at sea using Satellite Aperture Radar (SAR) images;
4.
THETIS – is a web-based application providing ship inspection related information and reporting support to all European Port State Control officers.
7
SafeSeaNet, how does it work?
NCA
Request Regional server (Baltic /North Sea)
LRIT
(to SSN central)
Response NCA
SSN Streaming interface
8
SSN core
Request for details (to the owner) NCA
Regional server (Med)
Notifications
(Dangerous goods, alert, Port notification)
Back
CleanSeaNet : Near Real Time service – 30 min* Analysis Results (Oil spills and vessel detection) Phone and email alert (Alert Report) Data dissemination
Planning
Acquisition and Processing
Met-ocean & ancillary data
Oil Spill Analysis
CleanSeaNet Service providers T0 = End of scene acquisition
*
Product Processing and Alert Generation
EMSA CleanSeaNet Data Centre
F e e d b a c k
T = T0 + 30 min
Satellite images are acquired in segments up to 1400 km long. 30 min are for a 400 km long image
Project Background – and the 24 hour Maritime Support Services (MSS)…..
11
EMSA operational systems
EU LRIT DC
Integrated Maritime Data Environment 12
The IMDatE Concept 1. The IMDatE is a complex technical ICT integrated system aiming to provide an enhanced MDA to all EU Member States (MSs). 2. It would: i. Promote common services and data at enterprise level ii. Improve the data exchange between the applications iii. Allow new maritime services to be provided at lower cost and deployed in short times. iv. Demonstrate the new integrated services to the Member States.
3.
It was based on state-of-the-art technology and set-up on the principles of flexible and configurable Service Oriented Architecture (SOA) and Integrated Product Development (IPD).
13
The IMDatE Concept and Components
14
Challenges of the Project (1 of 2)
• It relies on other maritime applications that are under constant evolution. Coordinated parallel development was required. • It required involvement of staff from numerous different units of EMSA. – Ad-hoc working groups were established to address common services such as: –
Common user management of all applications
–
Adoption of common auxiliary databases
–
Common application monitoring approaches
• An overall governance body was put in place with representation from senior management.
15
Challenges of the Project (2 of 2) • The management of the project was innovative when compared with previous traditional (waterfall) project management approach used by the Agency as it was the first time that EMSA had used a Concurrent Engineering (CE) and agile software development approach. • Although a significant new experience for EMSA, including the relationship with suppliers, it was a logical choice given the inter-dependency with other applications and the need for a roadmap of coordinated changes. • The full life cycle addressed user requirements, propagating early conceptual designs, running computational models, creating prototypes, developing and delivering early products, testing and re-analysing needs and performance, incremental development and feedback in to design process.
16
IMDatE: From Systems to Data to Customisable Services USER COMMUNITY
EMSA SYSTEMS
CUSTOMISABLE
EMSA BUSINESS DATA
FRONTEX
REPORTING (e.g email, pdf)
USER SERVICES
TECHNICAL SERVICES
EFCA
MARITIME SURVEILLANCE
SHIP PARTICULARS
EUNAVFOR
BB CUSTOMS
PRESENTATION (WUP)
POSITION FUSION TARGET CORRELATION
SHIP POSITIONS
EVENT ASSOCIATION
ACCESS RIGHTS
SHIP VOYAGES
VTMIS
DISSEMINATION (e.g. S2S)
DATA MANAGEMENT
INCIDENTS
BUSINESS MONITORING
OTHER
INTEGRATION LAYER (ESB, NOTIFICATION SERVICES and OTHER MIDDLEWARE)
SOURCES PILLARS
LRIT
SSN
THETIS
CSN
OTHER (INTERNAL AND EXTERNAL) E.g. VMS data from EFCA
17
Propose, review and refine – new features (1 of 2)
A graphical “time slider” allows visualization for ship movement replay and correlation inspection
18/
Propose, review and refine – new features (2 of 2)
The Timeline Tool
ISP Timeline In addition to the map view, a „Timeline‟ tool provides better awareness of time related events/information. Clicking on an element in the timeline refocusses on 19/ the relevant part of the map.
Conclusions • EMSA‟s first experience with concurrent engineering practices provides an excellent test-bed to ascertain the Agency‟s capability to move from the traditional waterfall project management to a more flexible and iterative approach. • Whilst the focus was on parallel technical development of the existing systems and the new integrated product, we learned that governance and clarity of objectives is equally important when dealing with complex multidisciplinary issues. • Prototyping, incremental deliveries and iterative design reviews have allowed quick wins to be achieved whilst lowering projects risks.
20
Thank you very much
[email protected]