CAD INTEROPERABILITY IN THE NATIONAL CAPITAL REGION

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

7
DEH Goals and Strategic Objectives
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
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

• Roles and Responsibilities

12
Internal JurisdictionalRoles and Responsibilities
13
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
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 ArchitectureRequires 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
To-Be Process Flows
As-Is Process Flows
Data Element Identification
Use Cases
30
Development Life Cycle Approach Design
Schemas
Message Structure

Two Types of Services Two Types of Services
Request for Resource
Unit Status Update
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
CAD Simulator Testing Tool allowed for testing of
DEH with each CAD Vendor
Issue Tracking Software for Testing
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
Development Life Cycle Approach Implement

• CAD2CAD Functional SOPs signed by Fire Chiefs
• Safecom Template

• CAD2CAD Customer Portal

36
Development Life Cycle ApproachSample SOP
37
NCR CAD2CAD IEPDhttp//www.ncrnet.us/cad-exchange


38
Infrastructure As Is
Test Development
Production
39
CAD2CAD Solution ArchitectureAllows for addition
of Other Regional Participants
40

• Governance and Ongoing Support

41
Regional Governance Needs Prior to CAD2CAD
People
Tools
Governance Artifacts
Mutual Aid Agreement
Information Support for Decisions Strategic
Direction
Executive
Policies
Equipment for Dispatch and Fire Fighting
Processes Change Unit ID
Functional
Procedures Remember to Call Other
Jurisdictions and make them aware of UNIT ID
Change
42
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
43
NCR NoVA Strategic Plans for Interoperability


44
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
Police
Fire
CIOs

• 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
Longer Term, when Cost Allocation Approach and
Operational Governance Structure is determined,
then proceed with one MOU regarding the
Interoperable Communications Infrastructure.
BOS or Council Approval Required
45
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
46
What will Transition ?
DEV AND TEST CAD2CAD Bs. Day
PRODUCTION CAD2CAD (24 x7 x 365)
Service Desk Incident and Change Management
Service Desk Incident and Change Management
DEH Hardware
DEH Operating System
DEH Software Platforms
CAD2CAD Biz Talk
NCRNet
Jurisdictions
DEH Hardware
DEH Operating System
DEH Software Platforms
CAD2CAD Biz Talk
NCRNet
Jurisdictions
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
47
Infrastructure To Be
Test Development
Production
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
(No Transcript)