1. Port Security Social Media Project Advisory Group May 15, 2012

2. Agenda Introductions Post Initial Meeting Discussion Project Update Technical Update Project Timeline Update Gaps Next Steps

3. Introductions Who is on the call New people joining us

4. POST INITIAL MEETING DISCUSSION What have you thought about since the first meeting? What will keep you involved? What is the biggest benefit to the project? What is the biggest problem?

5. PROJECT OVERVIEW UPDATE Advisory Group Purpose  Validate project focus  Challenge assumptions  Make recommendations  Suggest workshops/exercises

6. PROJECT OVERVIEW UPDATE (Cont.) Focus group ideas  PIOs  Port Workers/TWIC Card Holders  Marketing  Who else?

7. PROJECT OVERVIEW UPDATE (Cont.) Workshop Ideas  App review/validation  Situational awareness tools/social media integration  Marketing campaign review/validation  Anything else?

8. PROJECT OVERVIEW UPDATE (Cont.) Exercise ideas  Seminar on tool set  Tabletop on App use  Limited functional single area  Anything else? Change?

9. TECHNICAL UPDATE

10.  Work has started on the Suspicious Activity Report smartphone application ◦ Scrolling design ◦ GPS location and Pictures ◦ Needs a new name – not suspicious activity  Good visit with PNNL and viewed systems ◦ SRS would be more useful, under consideration  Team reviewed integrating the social media system with the Google Alert system  Grant will allow system testers to receive an iPad to assist with the implementation

11. DRAFT Suspicious Activity Report

15.  CAP – Common Alerting Protocol ◦ International standard for publishing and sharing alerts. ◦ Used by Google Alerts, NOAA, National Weather Service, USGS  Google Public Alerts ◦ Public website to search for alerts. ◦ Contains feeds from NOAA, USGS. More in the future. ◦ http://www.google.org/crisisresponse/ http://www.google.org/crisisresponse/  Google Crisis Response ◦ Websites setup by Google for various major incidents around the world. ◦ Each deployment unique to the incident. Landing page and/or map page. Includes various image data, situation information, person finder, etc. ◦ http://www.google.org/crisisresponse/ http://www.google.org/crisisresponse/

20. Google Crisis Response: Examples

24.  Reliable. Google are well equipped and experienced in handling huge demand.  Widely used. Users already comfortable with Google Maps.  Regionally targeted search results.  Free. Their effort is part of Google philanthropic arm, Google.org.

25. 1. Bridge goes out. Let’s say both of the Narrows Bridges. 2. Our system has an “Export to Google Crisis Alerts” button (available to a select few). 3. One of the select few “official publishers” from our region creates a report for the incident, “Tacoma Narrows Bridges Destroyed”. The system will prompt them for all required details to be a valid CAP 1.2 report. 4. Our system publishes the CAP report, “Tacoma Narrows Bridges Destroyed”. 5. Google Crisis Alerts reads CAP report, “Tacoma Narrows Bridges Destroyed”. 6. Google makes the report “Tacoma Narrows Bridges Destroyed” available to public at Google Public Alerts and in relevant Google searches. 7. Google works with regional agencies to set up a landing page for the incident, be it bad weather, earthquake, terrorist attic or other reason for bridge being destroyed.

26. 1. Become a vetted publishing authority with Google. Vetting process begins by filling out this form:filling out this form

27. 1. Alpha Mock-up initial SAR Mobile user interface - complete Begin coding Suspicious Activity Reporting - in progress Establish testing process - alphas to iPhone, iPad and Android Complete Alpha Version of SAR Mobile Implement Testing Distribution System Test Alpha on Devices Begin coding TipReview Website (for mapping, viewing, processing tips)

28. 2. Beta Begin Beta SAR Mobile Test TipReview Website Test Beta SAR Mobile Complete TipReview website Complete Beta SAR Prioritize and begin coding next features: i. Expand to include Incident Activity Reporting ii. Enable trusted users (login to the app for enhanced reporting features and flag tips as high priority) iii. Export to CAP tool iv. Integrate with social media streams (TBD: pull Social Media and/or push Public Reports via RSS/WebServices) v. Integrate with partner systems (TBD: push and/or pull Tips, Situation Reports via RSS/SecureWebService)

29. 3. Launch Complete Version 1.0 Implement Production Distribution System Launch Version 1.0

31. PROJECTED PROJECT TIMELINE UPDATE 3456 7 89101112 13 2012 2013 2 Workshop IPR – project input Focus Group Scope – project validation Workshop IPR – project “gut check” Focus Group Marketing – project input Workshop IPR – marketing test concepts Focus Group Marketing – project validation Training Project implentation, marketing & exercise plan Exercise Seminar Tabletop or Functional Workshop Project review and action plan

32. PROJECTED DELIVERABLE STATUS Phase 1  Application development - June Phase 2  Visual display – July Phase 3  Social media integration - August

33. GAPS Who will hate this now? How do we overcome anxiety? What are we missing? Who are we missing? What should be included? Can we adapt to other uses? Is value added?

34. NEXT STEPS Setting up demonstrations/workshops Setting up focus groups Next advisory group meeting  Tuesday, June 19 (tentative - in person)  Will post information to: https://blog.co.pierce.wa.us/ports/