Recommended
Recommended
More Related Content
Similar to ISCRAM 2013: Supporting multi-level situation awareness in crisis management
Similar to ISCRAM 2013: Supporting multi-level situation awareness in crisis management (20)
More from ISCRAM Events
More from ISCRAM Events (20)
Recently uploaded
Recently uploaded (20)
ISCRAM 2013: Supporting multi-level situation awareness in crisis management
- 1. Technology for a better society Michael E. Stiso, SINTEF ICT, michael.stiso@sintef.no Aslak Wegner Eide, SINTEF ICT Ragnhild Halvorsrud, SINTEF ICT Erik G. Nilsson, SINTEF ICT Jan Håvard Skjetne, SINTEF ICT Supporting multi-level situation awareness in crisis management ISCRAM 2013
- 2. Technology for a better society Michael E. Stiso, SINTEF ICT, michael.stiso@sintef.no Aslak Wegner Eide, SINTEF ICT Ragnhild Halvorsrud, SINTEF ICT Erik G. Nilsson, SINTEF ICT Jan Håvard Skjetne, SINTEF ICT Supporting multi-level situation awareness in crisis management ISCRAM 2013 Building a flexible common operational picture to support situation awareness in crisis management BRIDGING Resources and Agencies in Large-Scale Emergency Management EU FP7 Collaborative Project SEC-2010.4.2-1: Interoperability of data, systems, tools and equipment www.sec-bridge.eu
- 3. Technology for a better society BRIDGING Resources and Agencies in Large-Scale Emergency Management EU FP7 Collaborative Project SEC-2010.4.2-1: Interoperability of data, systems, tools and equipment www.sec-bridge.eu Michael E. Stiso, SINTEF ICT, michael.stiso@sintef.no Aslak Wegner Eide, SINTEF ICT Ragnhild Halvorsrud, SINTEF ICT Erik G. Nilsson, SINTEF ICT Jan Håvard Skjetne, SINTEF ICT Building a flexible common operational picture to support situation awareness in crisis management ISCRAM 2013
- 4. Technology for a better society
- 5. Technology for a better society casualty reports water resources available personnel personnel status available vehicles vehicle status weather conditions hazmat locations fire locations comms sitreps previous events video
- 6. Technology for a better society casualty reports water resources available personnel personnel status available vehicles vehicle status weather conditions hazmat locations fire locations comms sitreps video common operational picture
- 7. Technology for a better society casualty reports water resources available personnel personnel status available vehicles vehicle status weather conditions hazmat locations fire locations comms sitreps video the "Master" common operational picture
- 8. Technology for a better society resource management triage risk analysis history and progress support awarenssof
- 9. Technology for a better society resource management triage risk analysis history and progress big picture + individual pictures
- 10. Technology for a better society
- 11. Technology for a better society layer = focused information and functions
- 12. Technology for a better society
- 13. Technology for a better society
- 14. Technology for a better society
- 15. Technology for a better society
- 16. Technology for a better society
- 17. Technology for a better society
- 18. Technology for a better society TimelineResource Manager eTriage Risk Analyzer
- 19. Technology for a better society TimelineResource Manager eTriage Risk Analyzer general awareness
- 20. Technology for a better society TimelineResource Manager eTriage Risk Analyzer Resources Police Fire Medical Incident units Casualties
- 21. Technology for a better society TimelineResource Manager eTriage Risk Analyzer monitoring tracking resources and changes to them understanding knowing what resources are doing, and what they can do allocation directing resources where needed Resource Manager
- 22. Technology for a better society Resource Manager TimelineeTriage Risk Analyzer monitoring
- 23. Technology for a better society TimelineResource Manager eTriage Risk Analyzer monitoring
- 24. Technology for a better society TimelineResource Manager eTriage Risk Analyzer understanding "We need to know who is doing what."
- 25. Technology for a better society TimelineResource Manager eTriage Risk Analyzer tasksunderstanding
- 26. Technology for a better society TimelineResource Manager eTriage Risk Analyzer allocation
- 27. Technology for a better society TimelineResource Manager eTriage Risk Analyzer allocation
- 28. Technology for a better society TimelineeTriage Risk AnalyzerResource Manager allocation
- 29. Technology for a better society eTriageeTriage TimelineRisk AnalyzerResource Manager
- 30. Technology for a better society TimelineResource Manager eTriage Risk Analyzer ID ID ID ID ID ID ID
- 31. Technology for a better society TimelineResource Manager eTriage Risk Analyzer ID ID ID ID ID ID ID
- 32. Technology for a better society TimelineResource Manager eTriage Risk Analyzer ID ID ID ID ID ID ID
- 33. Technology for a better society TimelineResource Manager eTriage Risk Analyzer ID ID ID ID ID ID ID "How about GPS, blood O2, blood pressure, pulse, respirati on…"
- 34. Technology for a better society TimelineResource Manager eTriage Risk Analyzer ID ID ID ID ID ID ID
- 35. Technology for a better society Risk AnalyzerRisk Analyzer TimelineResource Manager eTriage
- 36. Technology for a better society TimelineResource Manager eTriage Risk Analyzer
- 37. Technology for a better society TimelineResource Manager eTriage "Risks are often tied to infrastructure – buildings, bridges, tunnel s, etc." Risk Analyzer
- 38. Technology for a better society TimelineResource Manager eTriage risk library Risk Analyzer
- 39. Technology for a better society TimelineResource Manager eTriage Risk Analyzer
- 40. Technology for a better society (Timeline)(Timeline)Resource Manager eTriage Risk Analyzer
- 41. Technology for a better society (Timeline)Resource Manager eTriage Risk Analyzer 13:0011:0009:00 15:00 event event event event + – 15:40:45rew where we were where we're going where we are
- 42. Technology for a better society (Timeline)Resource Manager eTriage Risk Analyzer 13:0011:0009:00 15:00 event event event event + – 15:40:45rew "We would like to take a snapshot of the current situation."
- 43. Technology for a better society (Timeline)Resource Manager eTriage Risk Analyzer 13:0011:0009:00 15:00 event event event event + – 15:40:45rew
- 44. Technology for a better society conclusions (from the experts) Pros • There is a need for such a system. • It could aid cross-agency collaboration. • It could reduce the need for radio communication. Cons • It wouldn’t be used on a day-to- day basis, so probably wouldn’t be used in an emergency. • System should have a dedicated controller. • It should log all information during a response. • It should document the basis of decisions made.
- 45. Technology for a better society Questions or comments? Michael E. Stiso SINTEF ICT michael.stiso@sintef.no
Editor's Notes
- Before we get started, I should mention that this is actually not the title of the presentation I’m giving. During the submission process, a reviewer made an insightful comment that led us to refocus the paper a bit. So, the title you’ll find in the proceedings is actually this one.
- The change actually won’t impact the discussion too much, because I am mainly going to show you the system we’ve built, and some of the reasons behind the design.[]Also, the work here is part of the FP7 project BRIDGE.
- Bridge is focused on the management of large-scale incidents of some sort. Fire or flood or earthquake or terrorist action – any emergency that causes serious regional disruptions and requires a response from multiple agencies, possibly multiple countries.
- Generally, responses to giant emergencies like these will involve establishing some sort of command center, either fixed or mobile or both depending on the command system of whatever country or agency is leading the effort.Command staff/teams from different agencies can gather there to collect and exchange information and coordinate plans, making it a clearinghouse or information hub.
- However, because the command post is an information hub, the command staff within it can be subject to overwhelming amounts of information, particularly as advances in ICT continue.not a new problem
- As those different data points become increasingly digitalized, though, we have a better opportunity to organize, fuse, and present the information to commanders via some sort of common operational picture. The goal is for everyone in the command staff, and even the field personnel, to have access to the same streamlined picture of the situation.
- That’s what our system tries to do. We call it the Master, which comes from its purpose, which is to serve as a master framework that collects and enables interaction with many different streams of information. It is intended to be a means for users to access, filter, visualize, and share (in other words, to master) all the information collected during an emergency response.[]Its basic form consists of a 2D map and an indication of different operational areas, which are features in most any common operational picture. You’re looking at the desktop version here [], though the primary version is meant to go on a large touchscreen table display, and we are currently refining version for mobiles and tablets.
- The initial designs came about through previous work on Bridge and other projects. We refined the designs during a series of workshops involving users from different emergency services. Based both on that previous work and on early workshops, we decided to focus the Master on supporting user awareness of four critical aspects of emergency operations[]Our discussions with users have shown those to be among the top considerations in command decision-making.
- However, those 4 aspects tend to be more important to particular agencies at particular times – e.g., triage for medical officers, resources for police or fire officers, history and risk for whichever agency is in command.[]In the scenarios imagined in Bridge, any of those agencies might be using the Master at any given moment, or even at the same time, so we saw the need for a flexible COP that would provide users with a shared view of the situation, but would also let them modify it to their particular information and situation awareness needs.
- []
- So, conceptually, we decided to encapsulate information relevant to the awareness of each type of activity into a set of layers, which different users could hide or show as needed.Each layer then became a component in the Master – basically, a self-contained set of functions. We named the components accordingly.
- By providing layers of information relevant to particular activities in emergency operations, we let users from different agencies focus on their individual awareness needs by hiding or deemphasizing information that is not needed.
- But at the same time, all users have access to the same big picture…
- …as well as what is going on in other areas.
- Those four components, along with general incident information, are organized into a ribbon-like information bar. The bar is sized for fingers on a touchscreen, but also so that notifications and important details can fit inside the squares, although that is not shown here.
- The goal is for the bar to provide some important information in a format that users can take in at a glance, while providing a means for them to drill into certain types of information for further details.[]Up here, for example, users can get a snapshot of different types of resources deployed on the scene, as well as a casualty count.
- In addition to the information provided in the ribbon, users can filter what they see on the map by hiding and showing different layers. For example, users could tap on “Resources” to display all registered resources on the map, or they could choose to show just, say, firefighting resources – personnel, trucks, etc.Right now, the layers are accessed separately from the ribbon, but a better integration of the two will be coming in the future.
- That said, we'll now take a look at the Resource Manager component, which is probably the primary bit of functionality in this system. It was designed to address 3 main activities.[]
- Looking at monitoring support first, let's assume I turn the Resources Layer on and then tap the Resources button in the ribbon.[]
- It looks a bit cluttered right now, obviously, but this is with no filtering, and we have plans to clean things up a bit.[]Anyway, what you see on the map right now are a bunch of icons representing all the police, fire, and medical resources in this particular area, color and shape coded. They move as the locations of the actual vehicles or personnel move.[]In the ribbon is a list of all the resources involved in the response, including those not see on this part of the map. Users can tap an icon to center the map on it.
- On to resource understanding.During our workshops with users, we learned that it iscrucial for this system to be able to show the tasks to which resources are currently assigned.
- So, we added a label above the icons that describes a resource's current task and availability, such as busy triaging patients or performing search and rescue. The labels contribute a lot to clutter right now, but we plan on refining the visuals. It was important to get the actual functionality in place first.[]If more details are desired, users can select a resource to show additional information about it.
- And finally, allocation. The system lets command staff assign tasks to units in a few ways.[]One way is by selecting somewhere on the map, which will produce this dialog. Users can then request certain resources to perform a certain task in that spot.
- Another way is by interacting with specific resources. Selecting this one, for example, produces a pie menu with various tasks that can be assigned to it – search and rescue, firefighting, investigating, going somewhere, setting something up, like a roadblock.
- Another way is by interacting with specific resources. Selecting this one, for example, produces a pie menu with various tasks that can be assigned to it – search and rescue, firefighting, investigating, going somewhere, setting something up, like a roadblock.
- That’s it for the Resource Manager. Moving on to the next component, the eTriage provides a similar sort of situation awareness, but one focused on awareness of casualties and their states rather than resources. Turning on the triage layer and tapping the Ribbon gives this.
- The different colors indicate the criticality of the patient’s condition.
- And here is casualty information mixed in with the resources overlay, in case the user wants to know which response units (ambulances or whatever) are closest to the critical patients, or whether any of the patients are located near a particular risk and need to be moved right away, and so on.
- The Casualty status is monitored on this system through sensor bracelets that first responders place on people they come across, supporting high-level, pre-hospital triage.
- The domain experts we talked to stressed the usefulness of getting patient details, envisioning a GPS-based "casualty monitor" that would send information like blood oxygen, blood pressure, heart rate, respiration, etc. to paramedics, command staff, the operations center, and so on.
- I'm not sure if the bracelets can transmit all that information yet, but they do at least provide location and some basic health data. You can get that information by tapping on a casualty.
- Moving on to the next component, the Risk Analyzer provides information about particularly risky structures or locales.
- Risk assessment is essential in emergency response, both to anticipate potential hazards and to better protect responders and the public.Risks here are shown as icons. We may expand that in the future to show zones, as well.
- Our workshops revealed that many of the risks that commanders must watch out for in an emergency response are often tied to buildings, bridges, tunnels, and other infrastructure. In a disaster, you generally don’t have time to thoroughly assess the risks of such things, but risk analyses can be performed beforehand, either on specific structures or on types of structure, then modeled and stored in a library.
- The Risk Analyzer then provides access to that library.
- And lets you select a given risk to get more information on it. This one is empty right now because it’s really just a placeholder. It would need to be populated with data from another part of the system.[]Finally, it’s not implemented in the UI yet, but the Risk Analyzer component also ties into a system developed in another part of the BRIDGE project that enables communications within a network of relevant experts who can make clear the risks associated with given locations, entities, or hazards, thus increasing the command awareness of the risk situation.
- And last is the Timeline component. It is rightfully in parentheses here because it does not actually exist yet. We ended up not being able to implement it as scheduled, and so it is something we will be working on later this year. So, what I can show you are our hopes and dreams for it – basically, a mockup -- but not an actual instantiation yet.
- The Timeline was initially conceived as a way to help command staff maintain temporal awareness of an emergency – in other words, what led up to the current state of affairs, and where are things going. By helping commanders to understand how things came to be, we perhaps better enable them to anticipate how things will develop, in turn helping them to plan and prepare accordingly.Dragging back and forth along the timeline displays changes in the situation over time. The goal is also to display future system states, such as planned events, weather forecasts, anticipated spread of fire or some other hazard, and so on.
- During the workshops, experts mentioned a desire to be able to bookmark or take snapshots of the current state of things, so we added that feature to the designs. Users can tap on the bookmarks to recall those states and compare them to the current one.The experts also mentioned that a visualization like this could help the otherwise challenging problem of making the next command shift in a longer-term crisis aware of what has happened so far. In other words, it can support temporal awareness both in individuals and across groups.
- Another purpose for this tool is to help with task and event coordination between agencies. The Timeline uses stacked, horizontal lines to represent the start time and duration of different events and ongoing tasks, to give users an at-a-glance schedule of important tasks and their progress in the crisis response.