1 / 54

CAD Interoperability in the NCR

CAD Interoperability in the NCR. 4/27/2010. Master Slide Deck. Program/Project Approach. Program Structure and Approach. History of CAD2CAD. City of Alexandria Fire and Rescue. Arlington County Fire and Rescue. Fairfax County Fire and Rescue.

mio
Télécharger la présentation

CAD Interoperability in the NCR

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CAD Interoperability in the NCR 4/27/2010 Master Slide Deck

  2. Program/Project Approach

  3. Program Structure and Approach

  4. History of CAD2CAD City of Alexandria Fire and Rescue Arlington County Fire and Rescue Fairfax County Fire and Rescue The Computer Aided Dispatch (CAD) systems of the NOVA Fire Departments have maintained other jurisdiction’s units in their own CAD systems. Previously • Each CAD System recommended NOVA units for dispatch based upon a ‘closest unit’ prediction. • All requests for resources were handled verbally by dedicated ring down telephone lines • One jurisdiction's Communication Center called another to confirm resource availability, transfer information, and perform dispatch

  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 and enable appropriate deployment of resources. Economies of Scale will be realized through the reuse and sharing of technology and data. Data sharing without DEH Data sharing with DEH

  7. 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. Goal Area 2 SECURITY Strategic Objective: Preserve the inviolability of the DEH through sound security practices. DEH Goals and Strategic Objectives 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.

  8. CAD2CAD Data Exchange Goals and Deliverables

  9. CAD2CAD - Yesterday and Today Unit Status Unit Status Unit Status

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

  11. NCRnet UASI-PSIC Completion Road Map 1 02/03/2010

  12. Roles and Responsibilities

  13. KEY: Jurisdiction Staff Vendor and Consultant Staff Internal JurisdictionalRoles and Responsibilities

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

  15. Communication

  16. Communication Plan

  17. Meetings and Reports

  18. Timeline

  19. Development Timeline

  20. System and Integration Testing Timeline

  21. Transition to Production Timeline

  22. Vendor Participation

  23. Standards

  24. Service Oriented ArchitectureRequires Adherence to Standards Artifacts should comply with National Standards to ensure ability to reuse data

  25. Safecom Interoperability Continuum

  26. Pilot Exchanges Helped Establish Standards NCR – IEPD Exchange Clearinghouse http://www.ncrnet.us/deh/IEPD/NCRIPDEHClearingHouse.html 1 NCR Crisis Information Management System (CIMS) Data Exchange http://www.ncrnet.us/deh/iepd/cims-exchange.htm 2 NCR Fire Incident Mapping Data Exchange http://www.ncrnet.us/deh/iepd/rms-exchange.htm 3 NCR Resource Typing Data Exchange http://www.ncrnet.us/deh/IEPD/index.htm

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

  28. Development Approach and Architecture

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

  30. Development Life Cycle Approach Planning CAD2CAD Project Charter

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

  32. Development Life Cycle Approach Design Schema Message Structure Unit Status Update Request for Resource

  33. Development Life Cycle ApproachData Mapping

  34. Development Life Cycle Approach Develop

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

  36. 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

  37. Development Life Cycle ApproachImplement CAD2CAD Functional SOPs signed by Fire Chiefs Safecom Template CAD2CAD Customer Portal

  38. Development Life Cycle ApproachSample SOP

  39. NCR CAD2CAD IEPDhttp://www.ncrnet.us/cad-exchange

  40. Infrastructure – As Is Test & Development Production

  41. CAD2CAD Solution ArchitectureAllows for addition of Other Regional Participants

  42. Governance and Ongoing Support

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

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

  45. NCR & NoVA Strategic Plans for Interoperability

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

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

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

  49. Infrastructure – To Be Test & Development Production

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

More Related