Your SlideShare is downloading. ×
0
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Usability in Emergency Response Applications
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Usability in Emergency Response Applications

1,186

Published on

Slides to go with my 2009 ESRI South West Users Group (SWUG) talk on creating a highly usable web application for emergency response users. Video of this talk can be viewed at http://vimeo.com/7557517

Slides to go with my 2009 ESRI South West Users Group (SWUG) talk on creating a highly usable web application for emergency response users. Video of this talk can be viewed at http://vimeo.com/7557517

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,186
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Kansas City is a great place…
  • Missouri river runs through the city
  • It has a history of heavy industry, in various states of repair
  • And with that comes industrial chemicalsWhen it comes to emergency planning, you need to take into account
  • Fires happen…
  • Accidents happen…http://www.flickr.com/photos/gretyl/54301880
  • Major storms happen…
  • And of course tornados happen.
  • All of this leads to complex emergency management scenarioshttp://www.flickr.com/photos/scissorhands33/3371981988
  • Mid America Regional Council – KC MPO
  • Keep track of what’s happening weather wise…http://www.flickr.com/photos/92833011@N00/824037794/sizes/l/
  • So that when an incident occurshttp://www.flickr.com/photos/martiniko/2354406802
  • To determine who may need to be evacuated or helped, with a focus on “critical infrastructure” like schools, day cares, hospitalshttp://www.flickr.com/photos/pedrosimoes7/393217457
  • As well as other facilities which may be impacted which can amplify the situation – refineries, chemical plants, power stations etc
  • Secured system, requires a login…
  • Map centric applicationBased on beta version of the JS Starter Kit with some key modifications
  • We needed to build the UI based on your role…
  • Now we’ll take a look at the three main workflows…
  • Turn on NEXRAD radar layer, and the Weather Warnings and Watches…
  • A call comes into dispatch, specifying an address and that there is a gas leak. Minimal information, but some action is needed.
  • 3 things automatically happenedTabular resultsLayer created (auditing, additional reports)-zoom to results
  • The last major work flow is for ad-hoc incidents… say a tanker crashed on I70…
  • User zooms to the general area
  • Is prompted to digitze the incident area
  • Prompted for some basic information and the report to generate
  • And they can see the results. In this case, there were not critical infrartucture sites
  • They can also run the other reports directly from the incident shape.
  • Admin Tools
  • Not supported in JSAPI when this was written
  • Regular applications work like this.. Request / response
  • In order to use Token secured ArcGIS Services, it works a little different
  • Lets go back to this diagram, but lets simplify it a little
  • 90% increase in the time to fetch an image tile – 1 second to about 2; Not major, but noticable.
  • Request Data Frame name sometimes returns a 404 from the SOAP API. Unknown reason, major time sink, Solution: did not find one.MapService.GetDefaultMapName()The request failed with HTTP status 404: Not Found
  • Mainly an issue when we are trying to Add services from a remote AGS box
  • SOAP Request
  • We make a call to the server to get the map services, and some basic info about the service (layers etc)
  • Part of this requires that we get the DefaultMapName (REST API can only serve data from Default Map),And this method randomly returns a 404: Not Found error.MapService.GetDefaultMapName()The request failed with HTTP status 404: Not Found
  • Lastly I wanted to mention browser hell…
  • System had to support FF 3, 3.5 and IE 7 & 8Worked fine in Safari, FF, Chrome, but IE was hell
  • While we were able to skip IE6, Making this all work in 7 & 8 was a HUGE time sink. Over a month of time was spent fighting with IE specific issues.This was somethings were cosmetic and others were critical. For the most part the ESRI API was fine, but building out complex multi-component widgets added extra complexityKudos to Mike and Mike our CSS and Javascript kung-fu masters.
  • Fire Fighters need to be
  • Under the covers, this is a pretty complex system…
  • The challenge was to create something that was highly configurable, secure and usable
  • Transcript

    • 1. Usability and Operational Efficiency in Emergency Response Applications: A Case Study
    • 2. GIS-enabled emergency applications, while increasingly critical to planning and managing response to incidents on the ground, must avoid the pitfalls of providing full-featured GIS packages to management and response personnel. Because these personnel are not typically trained GIS analysts or power users, significant operational efficiencies can be gained through the deployment of focused applications that match the mental model of response personnel when coordinating the response to an incident. DTSAgile has implemented a system for the Mid American Regional Council using the ESRI ArcGIS Server JavaScript and REST APIs that removes much of the perceived GIS complexity for emergency managers. The application instead relies on a focused, highly performant application supporting a finite number of workflows for the most common operational tasks or scenarios. This presentation will focus on approaches to building focused, workflow enabled emergency management applications with ESRI technologies. A case study involving a recently completed emergency response application will be used to illustrate design and implementation patterns, UI paradigms, key useability and operational efficiency features, data and functional considerations, and security options for applications serving the emergency response / emergency management markets
    • 3. SWUG 2009
      Usability Ideas for
      Emergency Response
      Applications
      http://www.flickr.com/photos/soldiersmediacenter/3059082014
    • 4. http://www.flickr.co/m/photos/zooboing/3711224527
    • 5. http://www.flickr.com/photos/malcolmtredinnick/317603723
    • 6.
    • 7. http://www.flickr.com/photos/poolie/2430954000
    • 8. http://www.flickr.co/m/photos/killbox/387652272/
    • 9. http://www.flickr.co/m/photos/syslfrog/172945973
    • 10. http://www.flickr.com/photos/gretyl/54301880
    • 11. http://www.flickr.com/photos/chascar/476475563/
    • 12. http://commons.wikipedia.org
    • 13. http://www.flickr.com/photos/scissorhands33/3371981988
    • 14. Emergency Response
      workflow application
      multi-service “mash-up”
      ESRI JS API + Dojo
      ArcGIS Server 9.3 REST
    • 15. SWUG 2009
      Real-Time
      Weather
      http://www.flickr.com/photos/92833011@N00/824037794
    • 16. SWUG 2009
      Incident
      Boundaries
      http://www.flickr.com/photos/martiniko/2354406802
    • 17. SWUG 2009
      Human
      Impacts
      http://www.flickr.com/photos/pedrosimoes7/393217457
    • 18. SWUG 2009
      Material
      Impacts
      http://www.flickr.com/photos/kenneth_hynek/3844780152
    • 19. SWUG 2009
      The
      Tour
    • 20.
    • 21. IIS
      JS Starter Kit
      Get Config
      Config.json
    • 22. SWUG 2009
      Identity
      Matters
    • 23. JS Framework
      ASP.NET MVC
      Get Config
      Config
      SQL Server
    • 24. Workflows
    • 25. 1
      SWUG 2009
      Weather
      Warnings
    • 26.
    • 27.
    • 28. What if…
    • 29.
    • 30.
    • 31.
    • 32.
    • 33.
    • 34.
    • 35. 3
      2
      SWUG 2009
      Real-Time
      Modeling
    • 36.
    • 37.
    • 38.
    • 39.
    • 40. Action
    • 41. Zoom to spatial results
      layer created
      tabular results
    • 42.
    • 43.
    • 44.
    • 45. 3
      SWUG 2009
      Ad-Hoc
      Incidents
    • 46.
    • 47.
    • 48.
    • 49.
    • 50.
    • 51.
    • 52.
    • 53. SWUG 2009
      Usability
      Features
    • 54. simplicity.
    • 55. consistency
    • 56. SWUG 2009
      smart
      features
      Do Stuff!
    • 57. SWUG 2009
      quick
      plume
    • 58. SWUG 2009
      one-click
      reports
    • 59. SWUG 2009
      flexible
      configuration
    • 60. User Managment
    • 61. SWUG 2009
      user
      manager
    • 62.
    • 63.
    • 64. SWUG 2009
      catalog
      manager
    • 65. Incident Layers
      Standard Layers
      Local or Remote AGS
      Tiled or Dynamic
      Bitmap or Geometry*
      Public or Secured
    • 66. Data Type controls the icon
      Name
      Short Description
      Long Description
      In pop-up window
    • 67.
    • 68.
    • 69.
    • 70.
    • 71.
    • 72.
    • 73.
    • 74.
    • 75.
    • 76. SWUG 2009
      challenges
    • 77. SWUG 2009
      secured
      services
    • 78. Request
      Response
    • 79. Credentials
      Token
      Request + Token
      Response
    • 80. Couldn't someone sniff
      the credentials or
      the token and subvert
      the whole thing?
    • 81. Credentials
      Token
      Request + Token
      Response
    • 82. Credentials
      AGS
      Token
      Request
      PROXY
      Response
      Request + Token
      Response
      Credentials
    • 83. SWUG 2009
      Fun and games
      https://
      SSL + proxies
    • 84. Credentials
      AGS
      Token
      Request
      PROXY
      Response
      Request + Token
      Response
      Credentials
    • 85. Source Server
      Request
      E
      D
      PROXY
      Response
      E
      D
    • 86. KC AGS
      KC AGS
      KC AGS
      ArcGIS Online
      Request
      E
      D
      Source Server
      PROXY
      Response
      E
      D
    • 87. 90
      %
      increase
    • 88. SWUG 2009
      random
      errors
    • 89. Remote
      AGS
      Request
      E
      D
      Source Server
      PROXY
      Response
      E
      D
    • 90. Remote
      AGS
      Request
      E
      D
      Source Server
      PROXY
      Response
      E
      D
    • 91. Remote
      AGS
      Service
      Harvesting
    • 92. HTTP 404: Resource Not Found
    • 93. hell
      SWUG 2009
      browser
    • 94.
    • 95.
    • 96.
    • 97. Browsers
    • 98. dbouwman@dtsagile.com
    • 99.
    • 100. http://www.flickr.com/photos/uberzombie/330972741
    • 101.
    • 102. configurable
      secure
      usable

    ×