Welcome to the CMAS Forum

1
Welcome to the CMAS Forum
2
CIPAC Protection

• Kory Whalen
• Branch Chief,
• DHS Emergency Services Sector,
• Sector Specific Agency

3
3
4
Stakeholder Driven
General Public
Practitioners
Needs
Priorities
Commercial Mobile Service Providers
Government
5
Purpose and Outcomes

• Purpose To convene the alerts and warnings
  community (including message originators,
  responder organizations, industry organizations,
  academia, and organizations representing special
  needs populations) to address critical issues and
  determine next steps for the Commercial Mobile
  Alert Service (CMAS) research, development, test,
  and evaluation (RDTE) Program
• Outcomes
• Shared understanding of the CMAS RDTE effort
• Identified needs for the CMAS RDTE Program to
  address
• Defined clear next steps for stakeholder
  involvement (to include Working Group and/or
  Action Teams)
• Coalition of local, state and Federal
  representatives working toward an effective CMAS
  solution

6
Agenda

• 830 am Welcome - Denis Gusty, CMAS Program
  Manager
• Meeting Overview
• Opening Remarks - Dr. David Boyd
• CMAS Partnership Panel Presentation
• Breakout Session Identification of CMAS Needs
• 1200 130 pm Lunch On your own
• Afternoon Speaker Philip Schaenman
• Breakout Session How to Address CMAS Needs
• Report Out Prioritization
• Wrap Up
• Next Steps Closing Remarks Denis Gusty
• 430 pm Adjournment

7
Guiding Principles

• Listen as allies
• Upgrade versus criticize
• Finish each part
• Move on despite ambiguity

8
Whos in the room?
9
Whos in the room?
10
Whos in the room?
11
Whos in the room?
12
Morning Speaker

• Dr. David Boyd
• Director, Command, Control Interoperability
  Division, ST

13
Command, Control and Interoperability Division

David G. Boyd, Ph.D.DirectorCommand, Control
and Interoperability DivisionJuly 30, 2009
14
Todays Challenge

• The need for real-time, actionable information is
  critical during day-to-day and emergency response
  operations.
• Critical information is often trapped in silos
  and inaccessible to those who need it the most.
• Components, systems, and architectures have
  limited ability to provide robust information
  sharing without the benefit of a national
  strategy and applicable standards.
• Information does not make it into the hands of
  those who need it most.
• State and local agencies often cannot afford to
  abandon current systems wholesale.

15
Virtual USA Strategic Initiative

• Virtual USA is an initiative to drive a technical
  and cultural shift in how the nation shares
  information during emergencies.
• It will create a virtual nationwide capability,
  enabling the sharing of information when needed,
  on demand, and as authorized, capitalizing on the
  latest emerging technologies.

16

Virtual USA

• Supports tactical, strategic, and planning
  decisions for homeland security practitioners by
  enabling the exchange of information in whatever
  form is needed, delivered to whatever device is
  available.
• Seeks to unify activities related to acquiring,
  managing, analyzing, sharing, and securing
  information.
• Serves as a way of organizing efforts at the
  National level.
• Advances application- and platform-agnostic
  technologies, standards, governance models, and
  other tools.

17

Virtual USA Core Principles

• Integrates existing frameworks to establish
  seamless information exchange among participants,
  as needed and as authorized.
• Builds on existing investments by leveraging a
  system of systems model to permit both new and
  existing technologies and concepts to exchange
  information without requiring agencies to replace
  existing systems.
• Draws on practitioner input at every step of the
  CCI project lifecycle.
• Employs a comprehensive approach by fostering
  dynamic information sharing between all
  practitioners, not specific, fixed points.

18

Virtual USA Core Principles

• Integrates existing frameworks to establish
  seamless information exchange among participants,
  as needed and as authorized.
• Builds on existing investments by leveraging a
  system of systems model to permit both new and
  existing technologies and concepts to exchange
  information without requiring agencies to replace
  existing systems.
• Draws on practitioner input at every step of the
  CCI project lifecycle.
• Employs a comprehensive approach by
• fostering dynamic information sharing
• between all practitioners, not specific,
• fixed points.

19
(No Transcript)
20

Virtual USA Lead Efforts

• Virtual City Pilots a national program that
  integrates multiple data sources and makes them
  more accessible for responders and other city
  officials.
• Virtual State Builds on existing investments in
  Virtual Alabama with advanced visualization,
  video streaming, and other technologies.
• Regional Operations Platform Project Expands the
  Virtual Alabama concept to a multi-state regional
  level and integrates existing platforms, enhanced
  visualization tools, and other data sets such as
  hurricane data to allow state systems to
  interoperate and exchange data with each other
  regardless of the platform or application in use.

21
Virtual USA Related Projects

• Acquire
• Tagging, Tracking, and Locating Technologies
• Sensor Webs
• Network Identity Management
• Manage
• Law Enforcement Information Framework
• CompStat 2
• Analyze
• Mid-Atlantic Data Sharing
• Enhanced Analytics Fusion Center Pilot
• Share
• Multi-Viewer
• Multi-Band Radio Pilot
• Emergency Data Exchange Language (EDXL) Data
  Messaging Standards
• Integrated Public Alert and Warning System
  (IPAWS)/Commercial Mobile Alert Service (CMAS)
• Regional Information Sharing and Collaboration

22
(No Transcript)
23
(No Transcript)
24
Panel Presentation

• Denis Gusty, DHS ST
• Jeff Goldthorp, FCC
• Dean Rychlik, FEMA
• Matt Gerst, CTIA
• Jim Johnston, Pasco County, FL Emergency
  Management

25
Morning Breakout Session

• Level Setting

26
Purpose of Breakout Sessions
27
Design of Breakout Sessions
Baseline CMSAAC Recommendations and FCC
rules Session 1 What is needed to move forward
with CMAS? Broken down by group Session 2
How do we move forward in addressing these
needs? Broken down by area After each
session, we will reconvene the plenary to report
out on the great work each group has done.
28
Morning Breakout Session Criteria

• Originators
• Individuals and organizations involved with the
  decision to send an alert and the creation of the
  alert message. These individuals are typically
  on the local or state level and interact with an
  emergency operations center during a time of
  emergency.
• Emergency Responders
• Individuals and organizations involved in
  responding the incident in the fields of 9-1-1,
  law enforcement, fire, and emergency medical
  services.
• Public Response
• Individuals and organizations working on issues
  related to how the public responds to an
  emergency and supporting public needs after a
  disaster.
• Communications Industry
• Individuals and organizations that represent the
  wireless industry, mobile device manufacturers,
  public broadcasting, and vendor solutions for the
  implementation of CMAS.
• Federal Partners
• Federal agencies working in the alerts and
  warnings arena.

29
Morning Breakout Session Groups

• Your group is determined by the color of the dot
  on your nametag
• Purple Communications Industry, Regency
  Ballroom
• Green Federal Partners, Potomac Room 4
• Blue Origination, Potomac Room 2
• Yellow Public Response, Potomac Room 1
• Pink Emergency Response, Potomac Room 3

30
LUNCH

• 1200 130 PM
• Lunch is on your own
• A list of restaurants in the area is provided in
  your CMAS Forum folder
• A lunch buffet is provided at the Hyatt Regency
  in Cinnabar on the main level
• Please return to the Regency Ballroom by 120 PM
  so that we are ready to start promptly at 130 PM

31
Afternoon Speaker

• Philip Schaenman
• President, TriData Division
• System Planning Corporation
• Mr. Schaenman has directed over 60 after-action
  studies of major public safety events. The events
  include the Columbine and Virginia Tech shooting
  incidents, the two World Trade Center attacks,
  the anthrax incidents involving the Pentagon
  mail office in 2004, and many others.

32
Mass Shootings at Virginia Tech on April 16,
2007Lessons Learned from the Virginia Tech
Shootings

• Presented by
• Philip Schaenman
• TriData Division, System Planning Corporation
• (Staff Director for the Review Panel)

33
Aerial view of Virginia Tech campus
34
One of the six sirens that were being installed
on Virginia Tech campus
35
Exterior of West Ambler Johnston
36
Hallway outside dorm rooms in West Ambler
Johnston
37
Typical dorm room in Ambler Johnston
38
Fourth Floor, West Ambler Johnston Hall
First attack in Emily Hilschers room
Ryan Clarks room
39
Emily Hilschers door with peephole
40
(No Transcript)
41
(No Transcript)
42
One of the main entrances to Norris Hall
43
Hallway in Norris Hall
44
Interior of typical classroom
45


46
Questions? Comments?

• To get full Virginia Tech report, download from
  the Governor of Virginia's website
• http//www.governor.virginia.gov/
  TempContent/techPanelReport.cfm
• Or the review panels website
• http//www.vtreviewpanel.org/

47
Afternoon Breakout Session

• Level Setting

48
Afternoon Breakout Session

• Lets move toward solutions!
• Breakout Topic Areas
• Governance Policies
• Usage
• Standard Operating Procedures
• Technology
• Training Exercises
• You choose!

49
Definitions of the Continuum Lanes

• Governance and Policy The process of
  decision-making, necessary mandates, and overall
  how stakeholders in the this effort will be
  involved at a local, state, regional and federal
  level
• Standard Operating Procedures All processes or
  procedures needed to standardize the way CMAS
  alerts are crafted, processed, and delivered
• Technology The system aspects of CMAS including
  hardware, software, and infrastructure and
  includes necessary interface standardization
• Training and Exercises Everything from testing
  the system and its components to training people
  how to create CMAS messages
• Usage Public education, availability of CMAS
  enabled devices, carrier elections, the user
  interface, and other activities that promote use
  of the system

50
Afternoon Breakout Session Rooms

• Technology Regency Ballroom
• Governance Potomac Room 4
• Training Exercises Potomac Room 2
• Standard Operating Procedures Potomac Room 1
• Usage Potomac Room 3

51
Plenary Prioritization
52
Prioritization Instructions

• Get Informed (25 min)
• Rotate around the room to learn about all of the
  initiatives that came out of the breakout
  sessions
• Ask clarifying questions of the initiative
  breakout team
• Vote Power of the Dot (15 min)
• Each participant has 6 dots (in your nametag)
  that can be used for this prioritization voting
• Place dot(s) on the Activity Sheets of the
  initiative(s) that you think are of highest
  priority
• Sign up for a particular Action Team by placing
  your business card or writing your email in the
  sign-up section of each Activity Sheet

53
Prioritization Criteria

• Near-term need (must be accomplished before we
  can move forward or must be accomplished prior to
  the initial CMAS implementation (2012))
• Impacts a large number of stakeholders (across
  disciplines)
• Greatly improves the effectiveness and
  geo-relevancy of alerts

54
Prioritization Commitment

• We encourage you to sign up for one or more
  Action Teams
• We are looking for a commitment level of about 2
  conference calls per month for 3 months
• Not all groups will start at the same time
• Not all groups will be led by DHS
• You may not have worked on, or even agree with, a
  particular initiative, in which case you should
  be sure to sign up to get involved and share your
  thoughts and expertise

55
Wrap-up

• Take top priorities based on dot voting
• Working Group/Action Team Sign-up
• Provide updates moving forward
• Achieved our outcomes

56
Working Group Style
57
Next Steps Closing Remarks

• CMAS Forum Report
• Integrate input into Program plans
• Design Action Teams
• Is the Forum an ongoing activity?
• Feedback CMASForum_at_sra.com