Thieme Hennis Susan Lagerweij Hidde Schipper Sebastiaan Surie Sebastiaan Tiemens

1052381 1150243 1024329 1014617 1102400

Flooding Calamity Control
Research on communication, coordination and cooperation during a flood

June 6, 2006 Spm4910 ICT Group

Outline
• Introduction • HELGA • Process design • Technical design • Institutional design • Conclusions • Reflection and Recommendations • Questions

Introduction
Problem owner:
The Ministry of Interior and Kingdom relations (BZK) • Fundament:

• What are the bottlenecks concerning communication, coordination and cooperation between the different parties involved, in case of a water calamity?

Introduction (2)
Objectives after first phase:
• Link the three C’s • Create situational awareness

System design should contain:
• Process design • Technological design • Institutional design

Goal of the second phase is to design a system, which improves the information provision during water calamities.

HELGA

Water calamity exercise May 16 in ‘t Harde

Proces design
Division in rounds

Round 1: Generic process rules

Round 2: Requirements

Round 3: Design issues

Round 4: Costs and responsibilities

Round 5: Start project

time

Proces design (2)
Division of design issues in clusters

Round 3: design issues Cluster 4 (3-6-7-9)

Round 1: generic process rules

Round 2: requirements

Cluster 1 (2-8)

Cluster 2 (1)

Round 4: costs

Round 5: start project

Cluster 3 (4-5)

time

Proces design (3)
Cost and responsibility issues in clusters
Round 4: costs and responsibilities

Cluster (Investment) Round 5: start project

Round 1: generic process rules

Round 2: requirements

Round 3: design issues

Cluster (exploitation)

time

Proces design (4)
Integration of round 4 and round 5

Round 1: Generic process rules

Round 2: Requirements

Round 3: Design issues

Round 4: Costs and responsibilities

Round 5: Start project

time

Proces design (5)
Outcomes of round 2 and 3 form basis for technical design
Round 1: Generic process rules Round 2: Requirements Round 3: Design issues Round 4: Costs and responsibilities Round 5: Start project

time

Technical design
Current situation
Network
Diverse analogue mobile networks

GMS
Emergency Room

Operational Information Systems

CMS System ARBI’s OMS System

C2000

Data Communication Server Terminals

GIS Systems

Internet
ARBAC PC’s Monitoring Devices CCS-Vnet

Etc.

Technical design (2)
Centralised character
• Information providence is fully dependent on the emergency rooms • Information is provided push-based • Inefficient in time • Ineffective for non standardised information

Distinct types of information content;
• Standardised core information via voice • Interactive content via a data channel

Technical design (3)
Necessary technical modifications
Decentralising  A more layered structure

A combination of these approaches;
The different systems and databases should all be integrated in one overall system. The systems and databases should somehow be placed in an organized way next to each other, in which only the interfaces are integrated.

Technical design (4)
Proposed solution  Implement a Service-Oriented Architecture (SOA) Service-Oriented Architecture:
• • • • Is a collection of services on a network that is able to communicate with one another.
• The services are loosely coupled.

Consists of policies, practices, and frameworks Makes it easier to integrate the whole IT environment. Herewith provides a higher level of application development that helps to mask the underlying technical complexity of the IT environment.

Technical design (5)
The SOC paradigm* is used in order to cover all important SOA design issues SOC consists of three dimensions:
• • • Actor dimension  Institutional design Service layer dimension Service functionalities dimension

*(Service-Oriented Computing Paradigm of Papazoglou and Georgakopoulos, 2003)

Technical design (7)
Decisions made according to the paradigm:
• • • • • • Structuring services Integration innovative systems possible Service routing performed by the routing approach The data layer is based on a web-based portal The portal is manifested by web services, using SOAP calls carrying XML data content The GMS portal is supported by a web server

Technical design (6)
Proposed technical design
Network

GMS
Service Domain Router GMS Portal

Operational Information Systems

CMS System Web Server CCS-Vnet

C2000

Emergency Room
GIS Systems ARBI’s Data Communication Server Service Router Terminals HIS Viewer

Fliwas

Internet

Service Router PC’s Monitoring Devices

Etc.

SOA

Technical design (8)
Improvements by the proposed technical design:
• A more decentralized situation of the information provision  A more efficient calamity control  A more effective calamity control Pull information without the need for a direct (central) connection with an emergency room Receive information types, which are impossible to communicate via voice (maps, photos, etc.)

Institutional design
Important institutional design principles
• • • • • • Credibility Flexibility Democratic legitimacy Transparency Reliability Scalability

Institutional design (2)
Other important institutional aspects:
• Norms and values • Quantifying the amount of time (to change)

Institutional design (3)
Institutional arrangements:
• • • • Compatibility with other systems Standards and semantics External systems and security Responsibilities and authorization

• Responsibilities and costs • Designers choice

Conclusions
Current system lacks coordination, cooperation and communication causing a central information overload Web GMS is an ICT-based system, which enables: • Decentralised information streams • Pull-based information • Better involvement of operational services • Visual information provision • Shorter (communication) connections

Web GMS provides desired support, cooperation and coordination during a water calamity…

Reflection and recommendations
• Once the system is implemented a second cost calculation should be executed • The Web GMS: • Should be coupled to the existing Fliwas system • Could form the basis for a general calamity control and information system • Could be coupled to international systems • BZK should: • Set up a central database on semantics • Secure cooperation, coordination and communication among the relief services • Security issues should be subject of a follow-up research

Questions? Web GMS…
support, cooperation and coordination during a water calamity…

Master your semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master your semester with Scribd & The New York Times

Cancel anytime.