Port Process & ICT Workshop 4 February 2009

Transcription

1 Port Process & ICT Workshop 4 February 2009 Casa de Asturia Brussels

2 Agenda General Session

3 Port Process & ICT Workshop: Objectives Present the tentative results Get feedback from the port experts Adjust the results Final EFFORTS WP3.1 results

4 EFFORTS WP3.1 Results and Benefits for the Ports Results Benefits Easier access to information within the port Methodology and tools for development of interoperable port IT systems Easier access to information from other ports Less manual input and output of data Less errors in data Faster implementation of changes Faster adaptation of new requirements

5 Agenda General Session

6 EFFORTS Introduction (Jens Froese)

7 Agenda General Session

8 WP3.1 - Port Processes Navigation in ports Ports and environment WP3.1 Port Processes Port organisation Education, training and development WP3.2 Risk Assessment

9 WP 3.1 Port Process The Objective WP 3.1 Port Processes aims at providing the methodology and necessary ICT tools to create interoperability solutions between stakeholders in ports

10 Certain focus on small and medium sized ports Most large ports have well functioning port community systems. Larger benefits for small and medium sized ports.

11 WP3.1 Partners MARINTEK NO (WP leader) ISSUS DE ISDEFE ES TREDIT GR Nielsen und Partners DE Port of Gijon ES Port of Hamburg DE Port of Thessaloniki GR Port of Dublin - IE With additional assistance from: University of the Aegean GR Wilhelmsen Ship Services - NO

12 Starting Point The details of internal port processes are very different between countries, regions and ports (ref. MarNIS). There are some international standards available for port/ship data interchange, but these are not always used (particularly in smaller ports) (ref. MarNIS). A general information architecture is being developed in MarNIS (ARKTRANS). However, this needs to be instantiated for port processes. Physical wireless communication facilities are available. However, new initiatives on e-navigation and e-maritime will be a new factor in this.

13 Expected Results 1 A standard port process reference model A roadmap for developing port interoperability solutions based on a service oriented architecture (SOA). An ICT toolbox to support the ICT roadmap (based on Sparx systems Enterprise Architect). Alignment of ICT toolbox with ARKTRANS and other MarNIS results (as specified in proposed ISO 28005) Analysis of wireless communication requirements in ports and port approaches (Input to e- Maritime strategy). Validation of the roadmap for two different IT systems in two different ports (Thessaloniki and Dublin) for selected processes.

14 EFFORTS Port Process Map

15 A standard port process reference model. Expected Results 2 A roadmap for developing port interoperability solutions based on a service oriented architecture (SOA). An ICT toolbox to support the ICT roadmap. Alignment of ICT toolbox with ARKTRANS and other MarNIS results (as specified in proposed ISO 28005) Analysis of wireless communication requirements in ports and port approaches (Input to e- Maritime strategy). Validation of the roadmap for two different IT systems in two different ports (Thessaloniki and Dublin) for selected processes.

16 act BRV - AD Accept Order Order Contractor Enter Orde r Inform a tion Place Order Order Order Rejected Order is rejected Order needs to be corrected Handle Correction Request Order Confirmation Receiv e Order Confirmation Order Request Order Confirm ation Check Order Customer Accept O rde r sd BTV - Choreography Converter System Customer Customer Order System CreateOrderData() Send OrderData() CustomerOrder() SendOrderCancellation() CustomerOrderResponse() CustomerOrderCancel() CustomerOrderResponse() OrderMsg() OrderCorrMsg() OrderConfMsg() CancelMsg() CancelConfMsg() Contractor Order System class BRV - Class Diagram +belongs to Order 1 CheckOrder() Order_Position 1..* +contains custom Test Scenarios Send Order Re ques t orde r correction Cancel Order stm BRV - State Diagram «invokes» Order open m odify order «invokes» «precedes» Confirm Order Correction for orde r requested Order Canc elled «invokes» Rej ect Order «precedes» «precedes» Order sent Order checked Order accepted Orde r c onfirm ed Modify Order Cancel Order Order rejected EFFORTS Conceptual Model for Interoperability Phase 1: Process Model Business & Technical Process EFFORTS Process Modelling Framework: E-CIMOSA Phase 2: Specification Model Procedure Model Business Domain View Use Case Use Case Description Business Requirement View Activity Diagram State Diagram Process Map Class Diagram Process Modelling Tool: EPC, Interfacing Inc. Business Choreography View Sequence Diagram Business Transaction View Business Information View Class Diagram composite structure BTV - Information «interface» OrderInterface «use» «use» CustomerOrder OrderMsg Process Model Test View (Validation) Test Scenario Diagram

17 A standard port process reference model. Expected Results 3 A roadmap for developing port interoperability solutions based on a service oriented architecture (SOA). An ICT toolbox to support the ICT roadmap. Alignment of ICT toolbox with ARKTRANS and other MarNIS results (as specified in proposed ISO 28005) Analysis of wireless communication requirements in ports and port approaches (Input to e- Maritime strategy). Validation of the roadmap for two different IT systems in two different ports (Thessaloniki and Dublin) for selected processes.

18 EFFORTS ICT Toolbox and Handbook An ICT Toolbox based on the Enterprise Architect system (Sparx) EFFORTS ICT Handbook An ICT handbook with guidelines and recommendations for development of interoperable port systems

19 A standard port process reference model. Expected Results 4 A roadmap for developing port interoperability solutions based on a service oriented architecture (SOA). An ICT toolbox to support the ICT roadmap. Alignment of ICT toolbox with ARKTRANS and other MarNIS results (as specified in proposed ISO 28005) Analysis of wireless communication requirements in ports and port approaches (Input to e- Maritime strategy). Validation of the roadmap for two different IT systems in two different ports (Thessaloniki and Dublin) for selected processes.

20 ARKTRANS Role Descriptions EFFORTS Toolbox EFFORTS role descriptions are based on ARKTRANS

21 A standard port process reference model. Expected Results 5 A roadmap for developing port interoperability solutions based on a service oriented architecture (SOA). An ICT toolbox to support the ICT roadmap (based on Sparx systems Enterprise Architect). Alignment of ICT toolbox with ARKTRANS and other MarNIS results (as specified in proposed ISO 28005) Analysis of wireless communication requirements in ports and port approaches (Input to e-maritime strategy). Validation of the roadmap for two different IT systems in two different ports (Thessaloniki and Dublin) for selected processes.

22 Developments in wireless communication Current focus on e-maritime will require a new data carrier for ship/shore communication: Digital VHF WiMax WiMax over UHF ( MHz) New international standard carrier opens possibilities for ship/port interfaces! WP 3.1

23 A standard port process reference model. Expected Results 6 A roadmap for developing port interoperability solutions based on a service oriented architecture (SOA). An ICT toolbox to support the ICT roadmap (based on Sparx systems Enterprise Architect). Alignment of ICT toolbox with ARKTRANS and other MarNIS results (as specified in proposed ISO 28005) Analysis of wireless communication requirements in ports and port approaches (Input to e- Maritime strategy). Validation of the roadmap for two different IT systems in two different ports (Thessaloniki and Dublin) for selected processes.

24 EFFORTS Validation For the pilot installations, a system to support berth planning has been selected, because it shows a high number of different information types collected from different sources.

25 Agenda General Session

26 EFFORTS Methodology and Interoperability Solution for Ports - A process-oriented Approach - Phanthian Zuesongdham (ISSUS / TUHH) Sven Mathes (NundP)

27 EFFORTS Process Map: Process Domains Public Marine Pilotage Tug Assistance Vessel Traffic Services Generation of ECDIS Data Interface to non-port Port Process Domains Infrastructure & Resources Logistics JF Berth Allocation Planning Loading / Discharging Foto Hafen Hamburg Source: Froese (2008)

28 EFFORTS Process Map Source: Froese (2008)

29 EFFORTS Port Process Map & ARKTRANS Roles

30 Process Modelling Framework: E-CIMOSA Source: Froese and Zuesongdham (2006)

31 act BRV - AD Accept Order Order Contractor Enter Orde r Inform a tion Place Order Order Order Rejected Order is rejected Order needs to be corrected Handle Correction Request Order Confirmation Receiv e Order Confirmation Order Request Order Confirm ation Check Order Customer Accept O rde r sd BTV - Choreography Converter System Customer Customer Order System CreateOrderData() Send OrderData() CustomerOrder() SendOrderCancellation() CustomerOrderResponse() CustomerOrderCancel() CustomerOrderResponse() OrderMsg() OrderCorrMsg() OrderConfMsg() CancelMsg() CancelConfMsg() Contractor Order System class BRV - Class Diagram +belongs to Order 1 CheckOrder() Order_Position 1..* +contains custom Test Scenarios Send Order Re ques t orde r correction Cancel Order stm BRV - State Diagram «invokes» Order open modify order «invokes» «precedes» Confirm Order Correction for orde r reque sted Order Cancelled «invokes» Rej ect Order «precedes» «precedes» Orde r s ent Order checked Order accepted Orde r c onfirmed Modify Order Cancel Order Order rejected EFFORTS Conceptual Model for Interoperability Phase 1: Process Model Business & Technical Process EFFORTS Process Modelling Framework: E-CIMOSA Phase 2: Specification Model Procedure Model Business Domain View Use Case Use Case Description Business Requirement View Activity Diagram State Diagram Process Map Class Diagram Process Modelling Tool: EPC, Interfacing Inc. Business Choreography View Sequence Diagram Business Transaction View Business Information View Class Diagram composite structure BTV - Information «interface» OrderInterface «use» «use» CustomerOrder OrderMsg Process Model Test View (Validation) Test Scenario Diagram Source: Zuesongdham (2008)

32 E-CIMOSA and EFFORTS Specification Model E-CIMOSA Domain Identification and Objective & Concept Definition Business Domain View Process Modelling Roadmap Operational Model (Monitoring & Control) Requirement Definition Model Design Specification Model Validation Specification Model Business Requirements View Implementation Business Transaction View Specification Model Test Test Model Standard Business Cases Implementation Description Model Deployment Source: Zuesongdham and Mathes (2008)

33 EFFORTS Roadmap EFFORTS Roadmap is based on a Model Based Approach Specification Model forms the basis for all subsequent phases of the IT Development Lifecycle It is based on UN/CEFACT's Modeling Methodology (UMM) using UML 1.3 Incorporates Standard Business Cases which can be used as "Toolbox" to model a specific business case The Roadmap is supported by a template defined as a Base Project in the modeling tool "Enterprise Architect" (EA)

34 EFFORTS Roadmap Modeling Approach Business Domain View Specification Model Business Requirements View Business Transaction View Standard Business Cases Implementation Test

35 EFFORTS Roadmap Views of the Specification Model Business Domain View Focus on: Actors and Processes Business Requirements View Processes/Activities Business Transaction View Workflow/Messages Specification Model

36 EFFORTS Roadmap Development Lifecycle Spec. Model Implementation Roll-Out Plan Specification Roll-Out Test Model Validation Validation Protocol EA EA: Application of Enterprise Architect

37 EFFORTS Roadmap Implementation in EA

38 Agenda General Session

39 EFFORTS Risk Management Framework - Conceptual Model and Linkage to the Port Processes WP LEADER: D Appolonia Partners: ISSUS, IST, ISDEFE, JRC, APL, DPC, PAG

40 Risk Management in Ports

41 EFFORTS Risk Management Framework Conceptual Model Port Processes RAPORT Quick and easy access EFFORTS WP 3.2 Core Task Risk Assessments Glossary Methodologies Tools Information Materials Scenarios Hazards & Casualties Regulatory Framework Case Studies Best Practices Source: Froese (2008)

42 Risk Assessment for PORT = RAPORT Platform Port Risk Taxonomy INNOVATION Toolbox to assess port related risks Process-oriented Reference Architecture

43 Risk Assessment for PORT = RAPORT Platform Benefits for Port Operators Ability to Identify hazardous operation Ability to perform the first risk assessment themselves Ability to apply best practices Ability to draft risk assessment specification

44 RAPORT following FSA IMO Guidelines

45 RAPORT Requirements General Requirements Quick reference related to port and terminal processes; Easy access to relevant knowledge to support risk assessment and risk management; Reliable input to draft contingency plans; Clear information to perform the best practice. Design Requirements to follow the FSA process to be incorporated with EFFORTS port process model to support Hazard Identification to support risk assessment; to support cost-benefit assessment; to support risk management. Interface Requirements Understandable by all parties; Comprehensive; Adaptable; Flexible; Extensible.

46 RAPORT Definition Model General Information Introduction FSA Description Glossary others Repository Methodologies Tools Best Practices others Applications FSA Projects Scenario Creation Risk Matrix

47 PORT LAYER 0 LAYER 1 LAYER 2 DOMAINS (Port Process Model) Marine Infrastructure STRUCTURE MODEL Hazards Information Model Scenarios (Causes & Conditions) Probabilities FSA1 FSA2 Consolidated input for user interfaces Inputs for risk experts detailed evaluation Logistics Interface Public bodies Consequences Risks & Residual Risks FSA3 Inputs to daily oper. procedures and contingency plan Management FSA4&5

48 RAPORT APPLICATION Welcome to RAPORT Risk Assessment for PORT Create new risk assessment Please click this button, if you would like to start a new project on risk assessment following Formal Safety Assessment (FSA) Create scenario for specific hazard(s) Please click this button, if you would like to create a new scenario of specific hazards for your port operation environment Create result for specific FSA Step Please click this button, if you would like to conduct a single FSA step in specific by not following the complete approach Risk Matrix Portfolio for Port Please click this button, if you would like to create a risk matrix for hazards portfolio in your port for quick overview and evaluation RAPORT is a risk management supporting platform for port experts to enhance comprehensive understanding of risk management in ports following Formal Safety Assessment. It provides a wide range of information for decision making in risk management requirements and evaluation process of a risk management project.

49 Risk Assessment Project Pre-Step

50 SCENARIO DEFINITION The scenario is defined following the logic of 4-Wh

51 Hazard results for Collision

52 Selected Hazards

53 HAZARD / THREAT ANALYSIS HAZARD IDENTIFICATION ANALYSIS Version: 1.0 Date: Page: 1 of 1 Process Domain: Marine Meta-Process: Navigation Company Name: EFFORTS Port Authority Created by: ABC Approved by: XYZ No. Hazard / Threat Condition Hazard / Threat Effects Severity / Consequence Frequency Risk Remarks 1 Reduced or Restricted visibility in heavy rain or fog 2 Poor lookout on other ship, impedes passages of vessel of more than 500 GT Loss of possibility in precise conning Lower speed of manoeuvring operation Collision to other ships C1 C0 C4 Collision to other ships C4 F4 6 F4 F3 F following the MSA Framework 3 Misunderstood intentions or disregard of collision Prevention Rule Mishandling on the manoeuvring operation Collision to other ships C3 C4 F4 F VHF departure message is not received correctly by the ship or tug Miscommunication between ship and tug leading to difficulty in manoeuvring operation Collision to other ships C4 C4 F3 F4 7 6

54 RISK ASSESSMENT RESULTS RISK MATRIX

55 RAPORT Toolbox Risk Glossary FSA Description EXAMPLE TO EXTRACT INFORMATION Examples of Contigency Plan Risk Maagement Methodologies Risk Assessment Tools Regulatory Frameoworks Scenario Library Risk Assessment Techniques Hazards & Casualties Case Study Library This toolbox contains a list of available risk assessment techniques and is presented in association with FSA steps. Several attributes are provided to enable a quick reference and finding of further sources of information. Best Practices Information Materials

56 RISK ASSESSMENT TECHNIQUES FOR FSA STEP1

57 Web Based RAPORT Platform (Example) Creating a new risk assessment project

58 Web Based RAPORT Platform (Example) Choosing how to define the project

59 Web Based RAPORT Platform (Example) Hazard identification

60 CONCLUSIONS o RAPORT an open source of supporting tool providing a set of filtered available information in regards to risk assessment and management with focus on FSA. o RAPORT - innovative methods to provide of information in a fussy risk management world in more structural way. o RAPORT - Toolboxes and Application Wizards enable users to prepare their own risk assessment / specification o RAPORT enabling factor for more effective risk assessment activity