Usability and Operational Efficiency in Emergency Response Applications: A Case Study<br />
GIS-enabled emergency applications, while increasingly critical to planning and managing response to incidents on the grou...
SWUG 2009<br />Usability Ideas for<br />Emergency Response<br />Applications<br />http://www.flickr.com/photos/soldiersmed...
http://www.flickr.co/m/photos/zooboing/3711224527<br />
http://www.flickr.com/photos/malcolmtredinnick/317603723<br />
http://www.flickr.com/photos/poolie/2430954000<br />
http://www.flickr.co/m/photos/killbox/387652272/<br />
http://www.flickr.co/m/photos/syslfrog/172945973<br />
http://www.flickr.com/photos/gretyl/54301880<br />
http://www.flickr.com/photos/chascar/476475563/<br />
http://commons.wikipedia.org<br />
http://www.flickr.com/photos/scissorhands33/3371981988<br />
Emergency Response<br />workflow application<br />multi-service “mash-up”<br />ESRI JS API + Dojo<br />ArcGIS Server 9.3 R...
SWUG 2009<br />Real-Time<br />Weather<br />http://www.flickr.com/photos/92833011@N00/824037794<br />
SWUG 2009<br />Incident<br />Boundaries<br />http://www.flickr.com/photos/martiniko/2354406802<br />
SWUG 2009<br />Human<br />Impacts<br />http://www.flickr.com/photos/pedrosimoes7/393217457<br />
SWUG 2009<br />Material<br />Impacts<br />http://www.flickr.com/photos/kenneth_hynek/3844780152<br />
SWUG 2009<br />The<br />Tour<br />
IIS<br />JS Starter Kit<br />Get Config<br />Config.json<br />
SWUG 2009<br />Identity<br />Matters<br />
JS Framework<br />ASP.NET MVC<br />Get Config<br />Config<br />SQL Server<br />
Workflows<br />
1<br />SWUG 2009<br />Weather<br />Warnings<br />
What if…<br />
3<br />2<br />SWUG 2009<br />Real-Time<br />Modeling<br />
Action<br />
Zoom to spatial results<br />layer created<br />tabular results<br />
3<br />SWUG 2009<br />Ad-Hoc<br />Incidents<br />
SWUG 2009<br />Usability<br />Features<br />
simplicity.<br />
consistency<br />
SWUG 2009<br />smart<br />features<br />Do Stuff!<br />
SWUG 2009<br />quick<br />plume<br />
SWUG 2009<br />one-click<br />reports<br />
SWUG 2009<br />flexible<br />configuration<br />
User Managment<br />
SWUG 2009<br />user<br />manager<br />
SWUG 2009<br />catalog<br />manager<br />
Incident Layers<br />Standard Layers<br />Local or Remote AGS<br />Tiled or Dynamic<br />Bitmap or Geometry*<br />Public o...
Data Type controls the icon<br />Name<br />Short Description<br />Long Description<br />In pop-up window<br />
SWUG 2009<br />challenges<br />
SWUG 2009<br />secured<br />services<br />
Request<br />Response<br />
Credentials<br />Token<br />Request + Token<br />Response<br />
Couldn't someone sniff <br />the credentials or <br />the token and subvert <br />the whole thing?<br />
Credentials<br />Token<br />Request + Token<br />Response<br />
Credentials<br />AGS<br />Token<br />Request<br />PROXY<br />Response<br />Request + Token<br />Response<br />Credentials<...
SWUG 2009<br />Fun and games<br />https://<br />SSL + proxies<br />
Credentials<br />AGS<br />Token<br />Request<br />PROXY<br />Response<br />Request + Token<br />Response<br />Credentials<...
Source Server<br />Request<br />E<br />D<br />PROXY<br />Response<br />E<br />D<br />
KC AGS<br />KC AGS<br />KC AGS<br />ArcGIS Online<br />Request<br />E<br />D<br />Source Server<br />PROXY<br />Response<b...
90<br />%<br />increase<br />
SWUG 2009<br />random<br />errors<br />
Remote<br />AGS<br />Request<br />E<br />D<br />Source Server<br />PROXY<br />Response<br />E<br />D<br />
Remote<br />AGS<br />Request<br />E<br />D<br />Source Server<br />PROXY<br />Response<br />E<br />D<br />
Remote<br />AGS<br />Service<br />Harvesting<br />
HTTP 404: Resource Not Found<br />
hell<br />SWUG 2009<br />browser<br />
Browsers<br />
Upcoming SlideShare
Loading in...5
×

Usability in Emergency Response Applications

1,214

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

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

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

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 &amp; 8Worked fine in Safari, FF, Chrome, but IE was hell
  • While we were able to skip IE6, Making this all work in 7 &amp; 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
  • Usability in Emergency Response Applications

    1. 1. Usability and Operational Efficiency in Emergency Response Applications: A Case Study<br />
    2. 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<br />
    3. 3. SWUG 2009<br />Usability Ideas for<br />Emergency Response<br />Applications<br />http://www.flickr.com/photos/soldiersmediacenter/3059082014<br />
    4. 4. http://www.flickr.co/m/photos/zooboing/3711224527<br />
    5. 5. http://www.flickr.com/photos/malcolmtredinnick/317603723<br />
    6. 6.
    7. 7. http://www.flickr.com/photos/poolie/2430954000<br />
    8. 8. http://www.flickr.co/m/photos/killbox/387652272/<br />
    9. 9. http://www.flickr.co/m/photos/syslfrog/172945973<br />
    10. 10. http://www.flickr.com/photos/gretyl/54301880<br />
    11. 11. http://www.flickr.com/photos/chascar/476475563/<br />
    12. 12. http://commons.wikipedia.org<br />
    13. 13. http://www.flickr.com/photos/scissorhands33/3371981988<br />
    14. 14. Emergency Response<br />workflow application<br />multi-service “mash-up”<br />ESRI JS API + Dojo<br />ArcGIS Server 9.3 REST<br />
    15. 15. SWUG 2009<br />Real-Time<br />Weather<br />http://www.flickr.com/photos/92833011@N00/824037794<br />
    16. 16. SWUG 2009<br />Incident<br />Boundaries<br />http://www.flickr.com/photos/martiniko/2354406802<br />
    17. 17. SWUG 2009<br />Human<br />Impacts<br />http://www.flickr.com/photos/pedrosimoes7/393217457<br />
    18. 18. SWUG 2009<br />Material<br />Impacts<br />http://www.flickr.com/photos/kenneth_hynek/3844780152<br />
    19. 19. SWUG 2009<br />The<br />Tour<br />
    20. 20.
    21. 21. IIS<br />JS Starter Kit<br />Get Config<br />Config.json<br />
    22. 22. SWUG 2009<br />Identity<br />Matters<br />
    23. 23. JS Framework<br />ASP.NET MVC<br />Get Config<br />Config<br />SQL Server<br />
    24. 24. Workflows<br />
    25. 25. 1<br />SWUG 2009<br />Weather<br />Warnings<br />
    26. 26.
    27. 27.
    28. 28. What if…<br />
    29. 29.
    30. 30.
    31. 31.
    32. 32.
    33. 33.
    34. 34.
    35. 35. 3<br />2<br />SWUG 2009<br />Real-Time<br />Modeling<br />
    36. 36.
    37. 37.
    38. 38.
    39. 39.
    40. 40. Action<br />
    41. 41. Zoom to spatial results<br />layer created<br />tabular results<br />
    42. 42.
    43. 43.
    44. 44.
    45. 45. 3<br />SWUG 2009<br />Ad-Hoc<br />Incidents<br />
    46. 46.
    47. 47.
    48. 48.
    49. 49.
    50. 50.
    51. 51.
    52. 52.
    53. 53. SWUG 2009<br />Usability<br />Features<br />
    54. 54. simplicity.<br />
    55. 55. consistency<br />
    56. 56. SWUG 2009<br />smart<br />features<br />Do Stuff!<br />
    57. 57. SWUG 2009<br />quick<br />plume<br />
    58. 58. SWUG 2009<br />one-click<br />reports<br />
    59. 59. SWUG 2009<br />flexible<br />configuration<br />
    60. 60. User Managment<br />
    61. 61. SWUG 2009<br />user<br />manager<br />
    62. 62.
    63. 63.
    64. 64. SWUG 2009<br />catalog<br />manager<br />
    65. 65. Incident Layers<br />Standard Layers<br />Local or Remote AGS<br />Tiled or Dynamic<br />Bitmap or Geometry*<br />Public or Secured<br />
    66. 66. Data Type controls the icon<br />Name<br />Short Description<br />Long Description<br />In pop-up window<br />
    67. 67.
    68. 68.
    69. 69.
    70. 70.
    71. 71.
    72. 72.
    73. 73.
    74. 74.
    75. 75.
    76. 76. SWUG 2009<br />challenges<br />
    77. 77. SWUG 2009<br />secured<br />services<br />
    78. 78. Request<br />Response<br />
    79. 79. Credentials<br />Token<br />Request + Token<br />Response<br />
    80. 80. Couldn't someone sniff <br />the credentials or <br />the token and subvert <br />the whole thing?<br />
    81. 81. Credentials<br />Token<br />Request + Token<br />Response<br />
    82. 82. Credentials<br />AGS<br />Token<br />Request<br />PROXY<br />Response<br />Request + Token<br />Response<br />Credentials<br />
    83. 83. SWUG 2009<br />Fun and games<br />https://<br />SSL + proxies<br />
    84. 84. Credentials<br />AGS<br />Token<br />Request<br />PROXY<br />Response<br />Request + Token<br />Response<br />Credentials<br />
    85. 85. Source Server<br />Request<br />E<br />D<br />PROXY<br />Response<br />E<br />D<br />
    86. 86. KC AGS<br />KC AGS<br />KC AGS<br />ArcGIS Online<br />Request<br />E<br />D<br />Source Server<br />PROXY<br />Response<br />E<br />D<br />
    87. 87. 90<br />%<br />increase<br />
    88. 88. SWUG 2009<br />random<br />errors<br />
    89. 89. Remote<br />AGS<br />Request<br />E<br />D<br />Source Server<br />PROXY<br />Response<br />E<br />D<br />
    90. 90. Remote<br />AGS<br />Request<br />E<br />D<br />Source Server<br />PROXY<br />Response<br />E<br />D<br />
    91. 91. Remote<br />AGS<br />Service<br />Harvesting<br />
    92. 92. HTTP 404: Resource Not Found<br />
    93. 93. hell<br />SWUG 2009<br />browser<br />
    94. 94.
    95. 95.
    96. 96.
    97. 97. Browsers<br />
    98. 98. dbouwman@dtsagile.com<br />
    99. 99.
    100. 100. http://www.flickr.com/photos/uberzombie/330972741<br />
    101. 101.
    102. 102. configurable<br />secure<br />usable<br />

    ×