1. CAD INTEROPERABILITY IN THE NATIONAL CAPITAL REGION LYNN HADDEN IT SYSTEMS ARCHITECT FAIRFAX COUNTY, VIRGINIA

2. Presentation Topics > Program and Project Approach > Roles and Responsibilities > Communication > Timeline > Standards > Developments Approach and Architecture > Governance and Ongoing Support

3. PROGRAM & PROJECT APPROACH

4. Program Structure and Approach > The National Capital Region (NCR) includes the District of Columbia and parts of Maryland and Virginia » 6,000 square miles » 4.2 million citizens » 23 local jurisdictions > Operating as a regional partnership, the Metropolitan Washington Council of Governments (MWCOG), these jurisdictions have been working together since 1957 to implement “intergovernmental policies, plans and programs” > In 2005, the MWCOG Chief Information Officers (CIO) Committee established the NCR Interoperability Program (NCRIP), a regional initiative to create an Interoperable Communications Infrastructure (ICI) for public safety and emergency response utilizing funding from the U.S. Department of Homeland Security > CAD2CAD was one of many data exchanges envisioned to run over this infrastructure

5. Program Components DATA EXCHANGE HUB NCRNet

6. DEH – “Connecting the Dots” > The DEH is a Service Oriented Architecture designed to » facilitate information sharing between Emergency Support Functions to improve emergency response » reduce response times » enable appropriate deployment of resources > Economies of Scale will be realized through the reuse and sharing of technology and data Data sharing without DEHData sharing with DEH

7. DEH Goals and Strategic Objectives Goal Area 3 STANDARD OPERATING PROCEDURES Strategic Objective : Develop, adopt and implement standard policies, processes and procedures to facilitate information sharing. Goal Area 1 TECHNOLOGY INFRASTRUCTURE Strategic Objective : Ensure device independent access to data and services in real time when needed through implementation of a Service Oriented Architecture (SOA). Goal Area 4 TRAINING Strategic Objective: Ensure all necessary personnel are trained to support interoperability across all systems for shared situational awareness. Goal Area 5 GOVERNANCE Strategic Objective: Establish a common operational governance structure that improves the implementation of any major technology project. NCR Data Exchange Hub Goal Enable the efficient and secure exchange of data (text, voice, video and multi-media) across the NCR. NCR Data Exchange Hub Final Outcome A sustainable, enabling architecture for the secure sharing data (text, voice, video and multi-media) across all Emergency Support Functions within the NCR when needed and as authorized. Goal Area 2 SECURITY Strategic Objective : Preserve the inviolability of the DEH through sound security practices.

8. CAD2CAD Data Exchange Goals and Deliverables CAD2CAD is the first Operational Exchange on the ICI. CAD Integration means many things to many people:  CAD Incidents on a Regional Map  Transfer of eBOLO Messages between CAD Systems  Unified Dispatch  Ability to automatically request a resource The DEH CAD2CAD Data Exchange Consists of:  Two Web Services: » Unit Status Update provides the real-time status of fire units » Request for Resource allows jurisdictions to request units from one another in mutual aid responses  Command and Control Console: » Allows Exchange participants to monitor the operational status of each jurisdiction, utilize the System or Emergency Override capability for their own jurisdiction, and log units on and off the Exchange  CAD2CAD Customer Portal: » Directs Exchange Participants to the links for Incident Reporting, Standard Operating Procedures, the Command Console, and Change Advisory Board materials

9. Unit Status CAD2CAD - Yesterday and Today

10. CAD2CAD is Utilizing the ICI NCRNet Buildout FFX ARL ALEX DEH CAD2CAD Data Exchange

11. ROLES AND RESPONSIBILITIES

12. Internal Jurisdictional Roles and Responsibilities CAD Vendor Project Team Jurisdiction Staff Vendor and Consultant Staff KEY:

13. Project Roles and Responsibilities CAD Vendor Project Team CAD Vendor Project Team CAD2CAD Project Team Lead Project Manager Security / /Infrastructure Architect Financial / Administrative Analyst Process / Business Analyst Integration Architect Developer CAD Vendor Project Team Regional Executive Oversight Committees and Funding Agencies Alexandria ArlingtonFairfax (Grant Administrator) Jurisdiction Staff Vendor and Consultant Staff KEY: COG CAO Interoperability Council COG CIO Committee NoVA Fire Chiefs Committee NCR SAA for UASI Funding VDEM for State PSIC Funding Accountable to

14. COMMUNICATION

15. Communication Plan > Structured Meetings with Documented Agendas > Meeting Follow-Up - Documented Minutes and Action Items > Most Meetings were Virtual ( Video Conferencing and Web Conferencing ) > Team Portal for housing all Documentation > Monthly Weekly, Bi-Weekly and Adhoc Meetings

16. Meetings and Reports Weekly >Core DEH Consulting Staff >Expanded DEH Project Team (Core DEH Consulting with all 3 Jurisdiction Functional Leads) >Core DEH Consulting Staff and Each Jurisdiction with their Respective CAD Vendor Monthly >COG CIO Committee >COG Interoperability Council >NoVA Fire Chiefs ( Monthly Email Status Report) Quarterly >NCR SAA Financial Reporting >VDEM Financial Reporting Ad Hoc >NCRNet Team >Networking/Security Staff from each Jurisdiction

17. TIMELINE

18. Development Timeline

19. System and Integration Testing Timeline

20. Transition to Production Timeline

21. Vendor Participation >Detailed Technical Specifications >Detailed Functional Specifications >SOWs reference Specifications >Vendors are competitors with different technical implementations - adhering to national standards and consistent and well-documented requirements is essential to ensure fairness to all and willingness to participate

22. STANDARDS

23. Service Oriented Architecture Requires Adherence to Standards Artifacts should comply with National Standards to ensure ability to reuse data

24. Safecom Interoperability Continuum

25. Standards >LEITSC CAD Message Set NIEM 2.0 >NIST Security Standards >WSI Interoperability Specifications >NIEM IEPD Life Cycle

26. DEVELOPMENT APPROACH AND ARCHITECTURE

27. Exchange Development Life Cycle (Follows NIEM IEPD Life Cycle) Artifacts for NIEM IEPD

28. Development Life Cycle Approach Planning > CAD2CAD Project Charter

29. Development Life Cycle Approach Requirements Data Element Identification As-Is Process Flows Use Cases To-Be Process Flows

30. Development Life Cycle Approach Design Two Types of Services: Request for ResourceUnit Status Update SchemasMessage Structure

31. Development Life Cycle Approach Data Mapping

32. Development Life Cycle Approach Develop >Latency, not Load, was the prime driver for Technology Selection >Ability to Support the Selected Platform after Go Live >Serialization of Large NIEM Compliant Schemas is the Challenge >In addition to the 2 Core Web Services (i.e. R2I2 and USU), an End User Portal accessible to all Dispatch Centers must contain: »Command and Control Console to monitor “Heartbeat” (ie. Network and Application Connectivity) »Electronic processes for requesting Changes to Mapping of Data (Unit, Event Type and Unit Status) »Electronic processes for Adding Deleting Units, Event Types and Unit Status) »Access to the online Service Desk »Access to documented SOPs

33. Development Life Cycle Approach Testing Issue Tracking Software for Testing CAD Simulator Testing Tool allowed for testing of DEH with each CAD Vendor Testing Scripts tied back to Requirements

34. Development Life Cycle Approach Training >Common Training Objectives across all 3 jurisdictions >Jurisdictions have different training schedules but coordination is required to support responding to requests in training

35. > CAD2CAD Functional SOPs signed by Fire Chiefs » Safecom Template Development Life Cycle Approach Implement » CAD2CAD Customer Portal

36. Development Life Cycle Approach Sample SOP

37. NCR CAD2CAD IEPD http://www.ncrnet.us/cad-exchange

38. Infrastructure – As Is Production Test & Development

39. CAD2CAD Solution Architecture Allows for addition of Other Regional Participants

40. GOVERNANCE AND ONGOING SUPPORT

41. Policies Processes – Change Unit ID Procedures – Remember to Call Other Jurisdictions and make them aware of UNIT ID Change Mutual Aid Agreement Executive Functional PeopleTools Governance Artifacts Information Support for Decisions & Strategic Direction Equipment for Dispatch and Fire Fighting Regional Governance Needs Prior to CAD2CAD

42. Regional Governance Needs With CAD2CAD Policies – Service Support Processes – Submit Problem with C2C Exchange Procedures - Online Service Desk Policies Processes – Update UNIT ID Change Procedures – Access C2C Portal submit UNIT ID Change Mutual Aid Agreement MOUs Executive Technical Functional PeopleToolsGovernance Artifacts Hardware, Software, Networks, Middleware Equipment for Dispatch and Fire Fighting DEH NCRNet SLAs Regional Technical Support Could Be Outsourced Information Support for Decisions & Strategic Direction

43. NCR & NoVA Strategic Plans for Interoperability

44. NCR Mutual Aid Agreement CIOs Fire Police Emergency Management NoVa Mutual Response Agreement NoVa CAD to CAD Operational Plan Fire & Rescue Mutual Aid Operations Plan Police Mutual Aid Operational Plan Emergency Mgmt Operational Plan Interoperable Communications Infrastructure (ICI) Operations Plan to include : NCRNet Infrastructure DEH Certified Exchange or Application Policies, Processes Procedures Security, Information Mgt, ITSM, Network Mgt Longer Term, when Cost Allocation Approach and Operational Governance Structure is determined, then proceed with one MOU regarding the Interoperable Communications Infrastructure. Liability Protection through NCR Mutual Aid Agreement ( Authority derived from the Terrorism Act of 2005 ) At cutover to NCRNet each ESF Ops Plan should Reference the ICI Ops Plan Agreements Agency Head Signatures Required BOS or Council Approval Required ESF Operational Plans

45. Technical Operations delivered by 3 rd Parties Network Operations Center HostingData Center HostingHelp Desk Service Jurisdictional Hosted Components IT Service Delivery guided by Policies, Processes & Procedures Long Term IT Service Support CAD2CAD Support Transitioning to 3 rd Parties Security Policy Information Management Policy Service Catalog/Policy Network Management Policy NCR Mutual Aid Agreement ICI Ops Plan ICI Ops Plan

46. What will Transition ? Service Desk Incident and Change Management DEH Hardware DEH Operating System DEH Software Platforms Management and Administration of Windows Servers Management and Administration of SQL Database Servers Connected Storage Backup and Recovery Operations CAD2CAD & Biz Talk Managing of SmartCenter Firewall Management and Administration of Networking Equipment Remote Access for Application Administration DEH Hardware DEH Operating System DEH Software Platforms Management and Administration of Windows Servers Management and Administration of SQL Database Servers Connected Storage Backup and Recovery Operations Managing of SmartCenter Firewall Management and Administration of Networking Equipment Remote Access for Application Administration PRODUCTION CAD2CAD (24 x7 x 365) DEV AND TEST CAD2CAD Bs. Day NCRNet Jurisdictions CAD2CAD & Biz Talk NCRNetJurisdictions Service Desk Incident and Change Management

47. Infrastructure – To Be Production Test & Development

48. CAD2CAD Change Advisory Board (Functional Leads and Technical Project Staff)

49. Incident Management and Change Management >Well-defined and fully supported IT Service Support processes are crucial to the operation of the DEH CAD2CAD Exchange.

50. Service Desk > End-Users directly log Incidents and Change Requests. > Service Desk Staff use Incident Reporting software to respond to and track outstanding issues.

51. Next Steps for CAD Interoperability in the NCR >Unifying public safety communications (radio and data) across ESFs and executing on the vision of information sharing >Formalize processes for deciding on what to invest in, enhance, or maintain the governance structure itself >Outreach and buy-in by jurisdictions (across all ESFs) “Interoperability is a process that involves planning, requirements, and communication with many public safety and non-public safety disciplines. By establishing common values such as a bottom-up or practitioner driven approach and collaborative processes to share resources, a region can agree on common needs to support the interoperability vision.”

52. DISCUSSION