CAD INTEROPERABILITY IN THE NATIONAL CAPITAL REGION

LYNN HADDENIT SYSTEMS ARCHITECTFAIRFAX COUNTY, VIRGINIA

Presentation Topics

> Program and Project Approach> Roles and Responsibilities> Communication> Timeline> Standards> Developments Approach and Architecture> Governance and Ongoing Support

PROGRAM & PROJECT APPROACH

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

Program Components

DATA EXCHANGE HUB

NCRNet

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 DEH

District of Columbia

Fairfax

Frederick

Loudoun

Prince George’s

District of Columbia

Fairfax

Frederick

Loudoun

Prince George’s

Regional Interoperability Backbone

Data sharing with DEH

DEH Goals and Strategic Objectives

Goal Area 3

STANDARDOPERATING

PROCEDURESStrategic Objective:

Develop, adopt and implement standard policies, processes and procedures to facilitate information sharing.

Goal Area 1

TECHNOLOGYINFRASTRUCTURE

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

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

Unit Status Unit Status

Un

it S

tatu

s

CAD2CAD - Yesterday and Today

CAD2CAD is Utilizing the ICICAD2CAD is Utilizing the ICI

NCRNet Buildout

FFX

ARL

ALEX

DEHCAD2CAD

Data Exchange

ROLES AND RESPONSIBILITIES

Internal JurisdictionalRoles and Responsibilities

CAO

FireChief CIO PSC

Director

FireFunctional

Lead

IT Functional

Lead

PSC Functional

Lead

CAD VendorProjectTeam

Jurisdiction Staff

Vendor and Consultant Staff

KEY:

Project Roles and Responsibilities

CAO

Fire Chief CIO PSC

Director

FireFunctional

Lead

IT Functional

Lead

PSC Functional

Lead

CAD VendorProjectTeam

CAO

Fire Chief CIO PSC

Director

FireFunctional

Lead

IT Functional

Lead

PSC Functional

Lead

CAD VendorProjectTeam

CAD2CAD Project Team Lead

Project ManagerSecurity / /Infrastructure

Architect

Financial / Administrative

Analyst

Process / Business Analyst

Integration Architect Developer

CAO

Fire Chief CIO PSC

Director

FireFunctional

Lead

IT Functional

Lead

PSC Functional

Lead

CAD VendorProjectTeam

Regional Executive Oversight Committees and Funding Agencies

Alexandria Arlington Fairfax (Grant Administrator)

Jurisdiction StaffVendor and Consultant Staff

KEY:

COG CAO Interoperability

Council

COGCIO

Committee

NoVAFire ChiefsCommittee

NCRSAA

for UASI Funding

VDEM for

State PSIC Funding

Accountable to

COMMUNICATION

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

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

TIMELINE

Development Timeline

System and Integration Testing Timeline

Transition to Production Timeline

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

STANDARDS

Service Oriented ArchitectureRequires Adherence to Standards

Artifacts should comply with National Standards to ensure ability to reuse data

Safecom Interoperability Continuum

Standards

> LEITSC CAD Message Set NIEM 2.0 > NIST Security Standards> WSI Interoperability Specifications

> NIEM IEPD Life Cycle

DEVELOPMENT APPROACH AND ARCHITECTURE

Exchange Development Life Cycle(Follows NIEM IEPD Life Cycle)

WSBuilding

WSBuilding

WS Publish,Bind, Find

WS Publish,Bind, Find

REQUIREMENTS DESIGN IMPLEMENTDEVELOP

.NetWSDL.Net

WSDLJava WSDLJava WSDL

WS Security Policies

WS Security Policies

WSDL UDDI

Registration

WSDL UDDI

Registration

Messageson

ESB

Messageson

ESB

EXCHANGE DEVELOPMENT LIFE CYCLEEXCHANGE DEVELOPMENT LIFE CYCLE

ARTIFACTSARTIFACTS

JIEMSite DBJIEM

Site DB CharterCharter

Work-GroupWork-Group

ProjectInceptionProject

Inception

IDEIDE RegistriesRegistriesPolicy ManagerPolicy ManagerESBESB

DomainModelingDomain

ModelingGJXDMMappingGJXDMMapping

SchemaBuildingSchemaBuilding PackagingPackaging

DomainModel

DomainModel

MappingArtifact

MappingArtifact

XMLSchema

XMLSchema

MethodSignature

From JIEM

MethodSignature

From JIEM

JIEMReference

Model

JIEMReference

Model

JIEMTool

JIEMTool

Modeling/Diagramming

Tools

Modeling/Diagramming

Tools

LocalRequirements

LocalRequirements

GJXDMSearch

Tool

GJXDMSearch

Tool

JIEMTool

JIEMTool

SubsetSchema

Tool

SubsetSchema

Tool

XMLEditorXMLEditor TOOLSTOOLS

Artifacts stored in web-based IEPD

Establish Policy Framework

Public Safety and Security Risk

Establish Business Framework

Establish Agreements

Establish Technical FrameworkContinuous Monitoring

NCR Targeted

Capabilities

Policies PracticesLife Cycle

Costs

Operational Level

Agreement

InterconnectSecurity

AgreementService Level

AgreementAssessments AuditsStandards

Concept of Operations

Detailed Design

Training Plan

Deployment Plan

Operations Plan

Maintenance Plan

Artifactsfor

NIEM IEPD

Development Life Cycle Approach Planning

> CAD2CAD Project Charter

Development Life Cycle Approach Requirements

Data Element Identification

As-Is Process Flows

Use Cases

To-Be Process Flows

Development Life Cycle Approach Design

Two Types of Services:

ARL

ALEX FFX

DEH

ARL + ALEXUnit Statuses

FFXUnit Statuses

ARL + FFXUnit Statuses

ALEXUnit Statuses

ARLUnit Statuses

ALEX + FFXUnit Statuses

ALEX FFX

DEH 1. Unit Statusfor ALEX

2. Request forResource (E206)

3. Request forResource

5. ALEXUnit

StatusUpdate

Dispatcher

4. Dispatch Engine 206

6. Unit Statusfor ALEX

Request for ResourceUnit Status Update

Schemas Message Structure

Development Life Cycle Approach Data Mapping

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

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

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

> CAD2CAD Functional SOPs signed by Fire Chiefs

» Safecom Template

Development Life Cycle Approach Implement

»CAD2CAD Customer Portal

Development Life Cycle ApproachSample SOP

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

Infrastructure – As Is

Production

Test & Development

CAD2CAD Solution ArchitectureAllows for addition of Other Regional Participants

GOVERNANCE AND ONGOING SUPPORT

PoliciesProcesses –Change Unit ID

Procedures – Remember to Call Other Jurisdictions and make them aware of UNIT ID Change

Mutual Aid Agreement

Exec

utive

Func

tiona

l

People Tools Governance ArtifactsInformation Support

for Decisions &

Strategic Direction

Equipment for Dispatch and

Fire Fighting

Regional Governance Needs Prior to CAD2CAD

Regional Governance Needs With CAD2CAD

Policies – Service Support

Processes – Submit Problem with C2C ExchangeProcedures - Online Service Desk

PoliciesProcesses – Update UNIT ID Change

Procedures – Access C2C Portal submit UNIT ID Change

Mutual Aid AgreementMOUs

Exec

utive

Tech

nica

lFu

nctio

nal

People Tools Governance 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

NCR & NoVA Strategic Plans for Interoperability

NCR Mutual Aid Agreement

NCR Mutual Aid Agreement

CIOs FirePolice

EmergencyManagement

•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

AgreementsA

genc

y H

ead

Sig

natu

res

Req

uire

dB

OS

or

Cou

ncil

App

rova

l Re

qui

red

ESF Operational Plans

Technical Operations delivered by 3rd Parties

Network Operations Center Hosting Data Center Hosting Help Desk Service Jurisdictional Hosted Components

IT Service Delivery guided by Policies, Processes &

Procedures

Long Term IT Service Support CAD2CAD Support Transitioning to 3rd Parties

Security Policy Information Management Policy

Service Catalog/Policy Network Management Policy

NCR Mutual Aid

Agreement

NCR Mutual Aid

AgreementICI

Ops Plan

ICIOps Plan

What will Transition ?

Service DeskIncident 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

PRODUCTIONCAD2CAD

(24 x7 x 365)

DEV AND TESTCAD2CAD

Bs. Day

NCRNetJurisdictions CAD2CAD & Biz Talk

NCRNetJurisdictions

Service DeskIncident and Change Management

Infrastructure – To Be

Production

Test & Development

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

Incident Management and Change Management

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

Service Desk

> End-Users directly log Incidents and Change Requests.

> Service Desk Staff use Incident Reporting software to respond to and track outstanding issues.

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

DISCUSSION