modelling crisis management for improved action and preparedness this project has received funding...
TRANSCRIPT
Modelling crisis management for improved action and preparedness
This project has received funding from the European Union’s Seventh Framework Programme for research, technological development and demonstration under grant agreement no 284552 "CRISMA“
CRISMA for C2-SENSEPeter Kutschera, AIT
19/04/23 | 2
Peter Kutschera, AIT
What is CRISMA?
The famous CRISMA catalogue
Main concepts
Architecture Overview
Mashups with WireCloud
CRISMA deployment
TOC
19/04/23 | 3
Peter Kutschera, AIT
Modelling crisis management for improved action and preparedness
EU FP7 Project Goals:
Build a framework that allows easy implementation of concrete applications
Focus on preparedness, planning, training Decision support system by comparing different options
Has to embed a lot of models Pilot applications dealing with following hazards:
toxic gas, earthquake, forest fire, flooding, power outages because of bad Nordic weather
What is CRISMA?
19/04/23 | 4
Peter Kutschera, AIT
Central project documentation repository for CRISMA users Description of:
Application Architectures Building Block and Model specifications (including interfaces) Reference Implementations and other software components Links to sources, demonstrators, background documentations Licenses, IPR conditions Input provided by every partner Now available for the public – in fact it’s now part of many
deliverables https://crisma-cat.ait.ac.at/
The famous CRISMA catalogue
19/04/23 | 5
Peter Kutschera, AIT
Worldstate: Describes the CRISMA-relevant state of the world at a certain
time stamp If something changes a new wordstate is created A series of timestamps describes a situation progress Different possible decisions are modelled as forks creating a
tree of worldstates: The decision tree
Main concepts
19/04/23 | 6
Peter Kutschera, AIT
OOI Object Of Interest Anything that is relevant for the actual use case and can change
over time Ambulances Patients …
There is a management GUI to define OOIs and there properties
Ambulances maximum speed Patients health …
Main concepts
19/04/23 | 7
Peter Kutschera, AIT
Models are used to calculate the consequences Of external events (e.g. earthquake) Of decisions (e.g. sending ambulances)
Model input are OOI and other data Model results create a single or a series of worldstates
Models are wrapped by WPS
Models
19/04/23 | 8
Peter Kutschera, AIT
Indicators are used to get an overview of a situation Number of patients Time-Interval needed for rescue Structured data like number of patients grouped by health
status …
Indicators
19/04/23 | 9
Peter Kutschera, AIT
Used for decision macking in a DSS Compare wordstates under the assumption of specific goals
Indicator (Key Performance Indicator, KPI) KPI: a single number (Length of a time interval, number of
collapsed buildings, ..) Criteria
Depending on a specific goal (Minimum recovery time, minimum recovery costs,..). Describes the importance of a single indicator value
Costs The weighted sum from the indicators. This result depends on
the goal
KPI and ICC
19/04/23 | 11
Peter Kutschera, AIT
A central datastore / catalogue Knows about worldstates
Relations between worldstates Specific data stores Indicator and ICC data
Knows about models and indicator services Method to access them (e.g. WPS) Concrete access data (e.g. WPS endpoint URL)
REST / JSON interface
ICMM
19/04/23 | 12
Peter Kutschera, AIT
Different GUIs exists within CRISMA WireCloud
Web-Based Different generic widgets can be combined to create a
use-case specific GUI Extendable by adding use-case specific widgets
Traditional Web-GUI Use-case specific Can also include WireCloud widgets
Installed application Can also include WireCloud widgets
GUI
19/04/23 | 13
Peter Kutschera, AIT
WireCloudCombine various widgets to an application
Modify widget size/position/name/ visibility
Put parts of the application on different tabs
19/04/23 | 14
Peter Kutschera, AIT
WireCloud: GUI
ICMM: Something between database and catalogue; holds WorldStates and (references to) data and services
OOI-WSR: Datastore for No-GIS data
Models: Any model behind an WPS. Uses / manipulates ICMM, OOI-WSR and other data
Indicators: Technically a model. Calculates indicator values for ICMM, OOI-WSR and maybe other data and stores them in ICMM
PubSub: Publish-Subscribe service (FI-WARE Orion) A WMS for background maps
Main components
19/04/23 | 15
Peter Kutschera, AIT
Architecture Overview(Just the C2-SENSE relevant part)
ICMM & OOI
WMSGUI
Indicator WPS
Models
PubSub
In C2-SENSE this would mean incoming sensor data, messages,…
C2-SENSE: ESB C2-SENSE: Emergency Maps Tool
In C2-SENSE: Limit Service
In C2-SENSE: NoMap Datastrore
19/04/23 | 16
Peter Kutschera, AIT
Communication within CRISMA
ICMM & OOI
WMSGUI
Indicator WPS
Models
PubSub
New data
19/04/23 | 17
Peter Kutschera, AIT
Communication within CRISMA
ICMM & OOI
WMSGUI
Indicator WPS
Models
PubSub
There are new data over there
19/04/23 | 18
Peter Kutschera, AIT
Communication within CRISMA
ICMM & OOI
WMSGUI
Indicator WPS
Models
PubSub
There are new data over there
19/04/23 | 19
Peter Kutschera, AIT
Communication within CRISMA
ICMM & OOI
WMSGUI
Indicator WPS
Models
PubSub
Get background maps
Get data
Show mashup
19/04/23 | 20
Peter Kutschera, AIT
Communication within CRISMA
ICMM & OOI
WMSGUI
Indicator WPS
Models
PubSub
There are new data over there
19/04/23 | 21
Peter Kutschera, AIT
Communication within CRISMA
ICMM & OOI
WMSGUI
Indicator WPS
Models
PubSub
Get dataCalculate IndicatorsStore result (new data)
19/04/23 | 22
Peter Kutschera, AIT
Communication within CRISMA
ICMM & OOI
WMSGUI
Indicator WPS
Models
PubSub
There are new data over there
19/04/23 | 23
Peter Kutschera, AIT
Communication within CRISMA
ICMM & OOI
WMSGUI
Indicator WPS
Models
PubSub
There are new data over there
19/04/23 | 24
Peter Kutschera, AIT
Communication within CRISMA
ICMM & OOI
WMSGUI
Indicator WPS
Models
PubSub
Get data
Refresh screen
19/04/23 | 26
Peter Kutschera, AIT
CRISMA Application GUICombine various widgets to an application
Modify widget size/position/name/ visibility
Put parts of the application on different tabs
19/04/23 | 28
Peter Kutschera, AIT
MarketplaceUpload widgets to local or public (FI-Ware Standard) marketplace
19/04/23 | 29
Peter Kutschera, AIT
ENVIROFI examplehttp://catalogue.envirofi.eu/news/envirofi-wirecloud-demo
CRISMA “pilot C” examplehttps://crisma-cat.ait.ac.at/pilot/Accidental-spillage-from-a-container-at-large-city-port-%28Israel%29/documentation
Application Mashup - Wirecloud - User and Programmer Guidehttps://forge.fiware.org/plugins/mediawiki/wiki/fiware/index.php/Application_Mashup_-_Wirecloud_-_User_and_Programmer_Guide
Mashups with WireCloud
19/04/23 | 30
Peter Kutschera, AIT
Initial situation at project start: as in every international project. Each partner provides one or more services. These are used by other partners over the internet. The interfaces are essential: Common data model, REST and
JSON, OGC WPS,… Later demonstrations (e.g. project review in Brussels):
Internet to slow, not reliable Some partners are just updating something, so service is not
available and incompatible afterwards Pilot implementations and deployment:
Have dedicated service instances Have them locally – great for development, essential at
deployment time for security and policy reasons
CRISMA deployment
19/04/23 | 31
Peter Kutschera, AIT
Each CRISMA Application consists of a set of services CRISMA-external services might also be used (e.g. background
maps from a public WMS) Typically services are distributed and accessed over the public
internet This even allows failover by the usage of alternative services if
a service is not available But in security sensitive and crisis management use cases the
usage of wide area networks is not permitted Security concerns Expected loss of
network connectivity
Initial Situation
Image: Stolen from the internet
19/04/23 | 32
Peter Kutschera, AIT
CRISMA Applications need a lot of services
Example: Resource Management Training CRISMA services
ICMM OOI-WSR Agents Resource Model plus WPS BasicIndicators including WPS PubSub Service WireCloud Service for the GUI
External services Map-Data for background maps
19/04/23 | 33
Peter Kutschera, AIT
It would be (sort of) simple to install a 19” rack
Unnecessary expensive Hardware Licenses Power consumption
Lot of systems needing permanent maintenance
One Server per Service?
Image: CC; Author Jfreyre; http://commons.wikimedia.org/wiki/File:Rack001.jpg
19/04/23 | 34
Peter Kutschera, AIT
Install all services on one machine Will work in some cases only – we actually did this for PilotEv1
But: Technical problem: Some services need specific and different
operating systems Logistical problem: Services are delivered by different partners
– messy integration, responsibilities become unclear
Some services might really need an own server for performance reasons
One Server to rule all Services?
19/04/23 | 35
Peter Kutschera, AIT
Virtualization allows to install all services as virtual machines on one real, big machine
Lot of overhead – Each service needs a full operating system installed
Better resource utilization compared to individual servers but still unnecessary expensive
Big hardware needed Licenses
Lot of systems needing permanent maintenance Some services might really need an own server for performance
reasons
One Virtual Server per Service?
19/04/23 | 36
Peter Kutschera, AIT
Containers are the newest hype when delivering services to the cloud (e.g. Docker)
Small Minimal overhead Much more lightweight than virtual machines in terms of size
and resources needed Very easy to build and deploy
And they can also be used in a local setup
But: Limited to some operating systems (Linux in the moment)
Containers?
19/04/23 | 37
Peter Kutschera, AIT
Deliver services as containers where possible Limited to some operation systems Docker can be used
Deliver virtual machines where needed E.g. Windows-based services Vagrant can be used
Deliver dedicated server machines for services with extreme performance needs
E.g. earthquake simulation model
Combine solutions!
19/04/23 | 38
Peter Kutschera, AIT
Virtual machines / docker images so far Crisma GUI
WireCloud Service for the GUI (Docker image) Crisma Core Service
ICMM (Docker image) Resource Management
OOI-WSR (VM) Resource Model
Agents Resource Model (VM) WPS for Resource Model (Docker image)
Indicators WPS interface + Implementation (Docker image)
Context Broker Orion (Docker image)
Crisma-external Services OSM tile cache (Docker image)
19/04/23 | 39
Peter Kutschera, AIT
FireWall
OOI-WSR
Resource Model
Example: Pilot C
Docker
WireCloud
Orion
Indicators
ModelWPS
ICMM
OSM cache
crisma-pilotC.ait.ac.at
19/04/23 | 40
Peter Kutschera, AIT
FireWall
OOI-WSR
Resource Model
Example: Pilot C
Docker
WireCloud
Orion
Indicators
ModelWPS
ICMM
OSM cache
crisma-pilotC.ait.ac.at
Real server running ESXi (VM-Ware)
Virtual machines (VM-Ware)
Containers (Docker)
19/04/23 | 41
Peter Kutschera, AIT
Deployment to a demonstration / customer machine is very easy Setup host machine with VM ESXi Copy VM images needed Deploy docker containers Configure the internal services: Nothing needed
All services communicate using the internal network, so no changes needed
Even the GUI works using the internal network only! Only network change is the external visible address.
This is handled by the FireWall VM (Apache virtual host config)
Only if there are external services used access needs to be configured
Deployment example: Easy
19/04/23 | 42
Peter Kutschera, AIT
Adopt CRISMA to the users business case / problem domain Implement specific data models (ICMM, OOI-WSR) Implement new models or at least build an interface to existing
specific models (WPS) Implement indicators Implement user specific GUI components
Application development is more work .-)