A Concept of Operations for Community Readiness

1. A Concept of Operations for Community Readiness

2. SDSU Basics • Physical • Wide bandwidth • Substantially wireless • Multiple modes • Location • Three sites • Communications Line of Sight to Qualcomm Stadium • Stadium provided relay link to all three • Governing Principles • Community involvement • Focus on COTS solutions • On-going Activity • Environmental monitoring via sensors • Video Monitoring • Distributed medical reachback

3. Concept: Empower the community to help support their own safety • Physical Infrastructure • Communications (bandwidth) • Systems • Power • Technical (sensors) • Professional Relationships • Response as a Community • Trust • Personal Interactions • Working together to solve real problems • Application of Common sense for Common Good

4. Technical and Operational Concept Knowledge on Demand by: • Onsite monitoring • with communications to • Dynamic Management of Information Transfer and Display • with communications to • Reachback to subject matter expertise

5. Technical Considerations • No large scale integrator • Participation based on ability of applications “Playing nice with others” • Not just on the technical integration of data input and output, but also in the self-sufficiency of their operation • Each participant brought along own gear • Affordability and Availability were key factors

6. On-Site Monitoring • Sensor Data • Essentially dynamic. Kinds: • Acoustic • Chemical • Radiation • Visual • GPS • Water • Fire • Weather • Traffic • Air • Motor vehicles • Vital Signs of first responder(s)

7. Dynamic Management of Information Transfer and Display • A wide variety of media data • Text input for TIDES • Dynamic management of essentially static information • 3-D maps • GeoViz • GeoFusion • Optical Network • TeraBurst

8. Dynamic Management of Information Transfer and Display (2) • From handheld PDAs in the field • Software solution allowing for immersive 3D (MUSE 3D) for immediate access to a selectable number (in this case 52) internet websites simultaneously • Specialization of information • Application sharing

9. Reachback to Subject Matter Experts • Scenario-based • Earthquake • Vicinity Qualcomm • 400+ dead • Fires • Contamination • With interactive capability with headmounted visual data source on-scene • Groove application and WAVE Three Session Software enabled a very robust V/C capability.

10. Reachback to Subject Matter Experts (2) • Distributed connectivity via mobile Ku-Band satcom, 155mb laser, and 45mb wireless comms • Univ of Virginia • East Carolina Univ • SUNY • Univ of Kentucky • Univ of Southern Alabama • Denver Health • Virginia Commonwealth • Driscoll Children’s hospital • MedWeb • Medaire • Sharp Hospitals of San Diego • Focused at the Forward Operations Center with additional communications in and from Camp Synergy (within the Qualcomm security enclave)

13. TIDES Visualization PointSource Vigilant Microbiometer TeraBurst GEOFusion GeoViz.com Groove Sun Microsystems Telesis ESP Group, LLC Cybercop CAL-(IT)2 SDSC MindTel TITAN Ambient WAVEthree MUSE LightPointe • Nextel Prominent Applications and Resources

14. SDSU Foundation SDSU TNS SDSU Campus Police SDSU Grounds Department SDSU Field Offices SDSU College of Sciences Significant Plant Resources

15. The result was a two-tier architecture • Command level – Visualization Laboratory • Action level – Forward Operating Centers • With an even-more-forward tactical node inside a secure enclave • With direct reachback to SMEs • Mutually supporting each other and supported, in turn, by technology applications

16. Lessons Learned • A significant amount of community infrastructure can be brought to bear with relatively small investment. • Committed technical partners • COTS solutions • Volunteer SMEs • It was often difficult to keep consistent data feed to the Visualization Center • Despite real value-added capability provided by the MUSE application, keeping its various URLs “refreshed” when data feeds are interrupted requires attention

17. Lessons Learned (2) • The robust chat capability enabled by Groove and WAVEthree was used not only for medical reachback but also to arrive at technical connectivity solutions • A high visibility event, exercise or demonstration will attract media attention • The SDSU community relations team may be brought into the picture earlier to shield the key decision-makers from episodic diversions introduced by the press.

18. Lessons Learned (3) • The Shadowbowl cadre was all first-teamers. A system that supports Emergency Services organizations (Federal, State, Local) will need to be able to be sustainable for more than a single short iteration and may need to be able to operate 24/7 as well.

19. Lessons Learned (4) • Although many of the principals contend that a successful ShadowBowl would have occurred if their participation had been curtailed midway in the process, it would be risky to extrapolate to that degree. • Particularly, since one of the founding premises is that there would be no single responsible industry integrator on which to fall back upon in the case of unavailability of SDSU principals. • Likewise, the San Diego community, in general, and the SDSU environment, in particular, probably represent critical enabling factors that would not allow the success in Shadowbowl to be easily replicated elsewhere. • More words on replication here

20. Lessons Learned (5) • Federal, state and local public safety organizations have their own strongly held ideas about “security” • The campus security may be brought into planning earlier • Be proactive to the evolving nature of opportunities • CampSynergy • “Playing Nice” wasn’t for everybody • Some possible volunteers opted out early; some opted out late

21. Lessons Learned (6) • The principal participants have gained a level of experience in ShadowBowl that could not have been gained in a static demonstration environment • The Two-Tier operational architecture that SDSU evolved into for ShadowBowl, and felt comfortable operating in, has a direct reflection in the Federal, State, and local emergency response architectures, especially the Incident Response System.

22. Supplement

23. Federal and State Implications • It can be important for SDSU to note that as a result of Shadowbowl, the University can point to where it fits into the Homeland Security Department IT development strategy. When promulgated, the HSD strategy will doubtless have the following key goals:

24. Provide a technical development environment for applications that enhance: 1 – Common, Consistent Knowledge 2 - Dynamically Managed, High-Capacity Connectivity 3 - Time-Sensitive Decision-making 4 - Distributed Planning and Execution ShadowBowl technical environment supported this kind of development!

25. Common, Consistent Knowledge Desired Capabilities: • Exploit, manage and integrate complex, heterogeneous information • User-tailorable picture • Situation-at-a-glance awareness • Natural, intuitive Human Computer Interaction ShadowBowl provided this!

26. Dynamically Managed, High-Capacity Connectivity Desired Capabilities: • Efficient utilization of area high-performance computing assets • Wireless Networking • Affordable Network Relays • Dynamic Bandwidth Management • GOTS/COTS solutions ShadowBowl provided this!

27. Time-Sensitive Decision-making Desired Capabilities: • Support for rapid threat assessment and local response • Rapid, effects-based planning • Enroute response cueing and briefing ShadowBowl provided this!

28. Distributed Planning and Execution Desired Capabilities: • Coordinated planning across all geographically distributed echelons and security enclaves – especially tactical • Reach-back for required subject matter expertise • Facilitated access to relevant databases • Intuitive management of collaboration services • Device & connectivity-independent collaboration • Support for plan assessment and rehearsal ShadowBowl provided this!