Introduction Scenario Seismic Damage Scenario Data Architecture ICT Architecture Presentation of the Applications

1. ICT Applied to Crisis Management and
Seismic Risk Assessment for Post Event Management
Maryam Izadifar Alireza Babaee Lorenzo Vidus Rosin Vincenzo Milesi

2.  Introduction
 Scenario
 Seismic Damage Scenario
 Data Architecture
 ICT Architecture
 Presentation of the Applications
Contents

3. Introduction Dealing
with
Unpredic
table
Complex
Disaster

4. Crisis Organizational
Problem will
start
Often large
crisis are
made by
small crises
Main Problems:
• Destabilized everyday life
• Difficult to evaluate situation
• Decide
Main Challenges:
• Communication
• Coordination
• Control
• Cognition

5. Crisis
Management
application of
strategies
designed to help
an organization
deal with a
sudden and
significant
negative event
Quick
Decisions

6. Phases of
Seismic
Crisis
Management

7. Case Study
 Salò is a town and commune in the
Province of Brescia in the region of
Lombardy (northern Italy) on the
banks of Lake Garda. The town has a
history of seismic events.

8. Seismic Scenario
• Magnitude: 5.2 in Richter scale
• Duration: 25 seconds
• Epicenter: 6 Km North of city
• Date & Time: Wednesday 24th November 2004 at
midnight (23.59 PM, local time)

9. Seismic Damage Scenario: Buildings
Vulnerability
Index of
each
building
block
Seismic
acceleration
in the
building area
Buildings
Damage

10. GIVEN DATA

11. Peak Ground
Acceleration
log10(Y) = a + bM + clog10(R2+h2)1/2 + e1S1 + e2S2  
According to attenuation law Sabetta–Pugliese:

13. BUILDING DAMAGE

14. ROAD DAMAGE OBSTRUCTION

15. DENSITY OF
POPULATION
IN ZONES

16. Seismic Damage Scenario: Areas
building’s typology
(construction
material, isolation
condition, number
of floors and
maintenance status)
construction
year period
(in terms of
volume)
an average
vulnerability
index
approximated
for each
section of the
area
Average
Seismic
acceleration
in the area
Area’s
average
damage
rate

17. VULNERABILITY
BASED ON CENSUS DATA
MAP

18. DAMAGE MAP
BASED ON CENSUS
DATA

19. Activity Diagram
Team Management

20. Entity-Relationship
Diagram BUILDING OWNER
NAME
SURNAME
PHONE NO.
CODICE FISCALE
EMAIL
BIRTH DATE
REQUEST OF ASSESSMENT
DATE
TIME
BUILDING
(1,n)
(0,1)
ADDRESS
OWNER NAME
OWNER SURNAME
FLAG PUBLIC BUILDING
CATEGORY
ACCESSED BY
ROAD
ROAD NAME
TYPE
(1,n) (1,n)
BELONG TO
AREA
ZONE NO.
GEO-REFERENCED
COORDINATION
POPULATION (1,1)(1,n)
TEAM
ALLOCATED TO
DATE
TIME
ASSESSED BY
DATE
TIME
(1,n)(1,n)
(1,n) (1,n)
TEAM ID
TEAM MEMBER
TEAM MEMBER ID
NAME
SURNAME
PHONE NO.
EMAIL
(1,n)
COMPOSED BY
(1,1)
ENGINEER ARCHITECHT FIREMAN
ENTITY-RELATIONSHIP DIAGRAM
BUILDING ID
Data Architecture

21. Use Case Diagram
ICT Architecture

22. Use Cases

23. Use Cases

24. Use Cases

25. Use Cases

26. Interface Design One (Assessment Request)
Step 1: Building owner enters his/her data Step 2: System shows the owner his/her buildings to be confirmed
Step 3: System shows the owner the position of the building Step 4: System gives a request code

27. Interface Design
Step 1: Log in page for authorizing Step 2: User can choose one option to enter its appropriate part
HR RESPONSIBLE
Authorized User 

28. Interface Design Two (Visualization of Requests)
Step 1: User chooses part one (visualization of requests) Step 2: System asks a date to show the requests till that time
Step 3: System shows requests, including pending from previous days Step 4: System shows all requests on the map

29. Interface Design Three (Team Composition)
Step 1: User chooses part two (team composition) Step 2: System asks a date Step 3: System shows list of available surveyors
Step 4: User chooses one engineer, one architect and one fireman Step 5: system shows the team composition to be confirmed

30. Interface Design Four (Team Planning)
Step 1: User chooses part three (team planning) Step 2: System asks a date for planning a team
Step 3: System shows a map with the zones to be chosen Step 4: System shows all requests on the chosen zone

31. Interface Design Four (Team Planning)
Step 5: User chooses building requests to be assessed Step 6: System shows all composed teams for that date
Step 7: User chooses one team
Step 8: System shows the result
(team, team members, buildings to be assessed, date, and time)