Accomplished
We continue to iterate the script/storyboards for the Responder Maps video. These activities are moving in parallel with requirements analysis. Based on the personas and context scenarios previously mentioned, the focus of the video is shaping up around mapset assembly, sharing, and consumption in the field. I’ve also added some key contacts to my rolodex, firefighters/incident managers from the Menlo Fire District and the Palo Alto Fire Department, that we’ll approach for more detailed feedback on workflows and protocol involving maps and devices in the field.
Challenges
At this Monday’s plenary discussion, attendees heard in detail about the challenges facing the adoption of common standards/services targeting the requirements of multiple stakeholders and end users in the disaster management community. Similar to the common operating picture (or BayCOP) initiative, the Common Alerting Protocol (CAP) struggles to deliver on its vision amid a backdrop of cultural, institutional, and technological obstacles. Maintaining the critical path involves focusing on core requirements (timely delivery of a standardized information payload) and refusing to “branch prematurely” (succumb to calls for “mass” personalization early in the design process.)
Following the foregoing presentation by Art Botterell, Trey and I participated in a breakout session of DMI/BayCOP stakeholders where various constituents (representing interests in fire, earthquake, and critical infrastructure/key resources (CK/IR)) tried to reconcile their diverse interests and visions. Keeping the lessons from CAP in mind, we introduced plans underway to complete the Responder Maps video and highlight key functionality in the context of everyday firefighting response activity. The response was supportive, and, predictably, overwhelming as each party offered directions and concepts to incorporate into the scenario(s).
In closing, we emphasized our focus on capturing authentic goals/behavior from the firefighting domain that could inform best practices and structured data applicable to multiple domains (protection of CI/KR, earthquake response, etc.)
Goals
The primary goal for the coming week is still on development of the Responder Maps video and reaching out to first responders for feedback and research. In addition to capturing the fire-fighting focused scenario in the video, we’ll likely use some time in the closing to describe parallel activities by DMI partners and how common efforts are needed to realize the BayCOP vision of integrated information display and delivery. Given the perspective offered by the DMI presentation and discussions, I’m confident the video will go a long way towards aligning stakeholders behind product priorities.
Related articles
- Responder Maps: Week 6 (geoffnet.com)
- Responder Maps: Week 5 (geoffnet.com)
- Responder Maps: Week 3 (geoffnet.com)
- Responder Maps: Weeks 1-2 (geoffnet.com)
