public safety communications in the district of columbia ... · 9/30/2016 · firstnet has...

CONFIDENTIAL – Official Government Use Only

Public Safety Communications in the District of Columbia: Data for FirstNet

District SLIGP Team Report for District of Columbia Public Safety

Leadership

September 30, 2016 (Revised)

District of Columbia Public Safety Communications Data - FirstNet

ii CONFIDENTIAL – Official Government Use Only

Revision History Revision Date Author Comment

1.0 10/5/15 District SLIGP team

Original submission

1.1 10/23 District SLIGP team

Revised submission based on FirstNet comment.

2.0 9/20/16 District SLIGP team

Revised submission with updated content:

1a. Coverage Objectives, under “District Coverage Analysis” the section has been updated with new mapping analysis.

2b. Devices: MPD has added 2800 body cameras deployed in 2016, changing total “Other Devices – Personnel” to 2923 and 1400 smart phones supporting the cameras, changing total “Voice/Data Devices – Personnel” to 8323.


1 CONFIDENTIAL – Official Government Use Only

Contents Introduction .................................................................................................................................................. 3

Background ............................................................................................................................................... 3

Public Safety Users and Entities ................................................................................................................ 3

FirstNet Requested Data ........................................................................................................................... 4

District Data Resources ............................................................................................................................. 4

1.a. Coverage Objectives ............................................................................................................................... 6

Coverage Background ............................................................................................................................... 6

District Coverage Analysis ......................................................................................................................... 7

Population ............................................................................................................................................. 9

Transportation .................................................................................................................................... 10

Key Points ............................................................................................................................................ 10

Calls for Service ................................................................................................................................... 10

1.b. Phased Deployment Approach ............................................................................................................ 11

2. User Data................................................................................................................................................. 12

2.a. Public Safety Entity Demographics .................................................................................................. 12

2.b. Devices ............................................................................................................................................. 14

2.c. Users and Devices Summary ............................................................................................................ 14

2.d-i. Operational Areas .......................................................................................................................... 16

2.d-ii. Calls for Service ............................................................................................................................. 17

3. Applications ............................................................................................................................................. 19

3.a Application Usage ............................................................................................................................. 19

Primary Application for Communications ........................................................................................... 21

Primary Application for VoIP ............................................................................................................... 21

Primary Application for AVL ................................................................................................................ 22

Primary Application for Location Services .......................................................................................... 22

Primary Application for CAD ............................................................................................................... 23

Primary Application for Database ....................................................................................................... 23

Primary Application for General Connectivity .................................................................................... 24

Primary Application for Field Based Reporting ................................................................................... 24

Primary Application for Intranet/VPN ................................................................................................ 25



Primary Application for Video ............................................................................................................. 25

Primary Application for Telemetry...................................................................................................... 26

Other Primary Applications ................................................................................................................. 26

3.b Data usage ........................................................................................................................................ 27

Average Monthly Data Usage ............................................................................................................. 27

Daily Data Usage ................................................................................................................................. 28

4. Contracts and Procurement .................................................................................................................... 29

4.a. Procurement Vehicles, Plan Costs, and Specialized Services ........................................................... 29

Provider Contracts Overview .............................................................................................................. 29

Providers ............................................................................................................................................. 31

Commercial Paging Use ...................................................................................................................... 33

User Fees ............................................................................................................................................. 33

4.b. Barriers to Adoption ........................................................................................................................ 34

Acronyms .................................................................................................................................................... 36



Introduction Information in this document meets FirstNet’s request for state public safety communications data and

has been collected in line with NTIA’s SLIGP approved Phase 2 activities.

Background The Nationwide Public Safety Broadband Network (NPSBN) managed by the federal FirstNet authority

will bring critical dedicated mobile broadband services to Washington, DC and National Capitol Region

first responders.

To serve its mission of building a nationwide network, the FirstNet must provide service to areas critical

to first responders. While it would be ideal to immediately cover all areas of the country, FirstNet’s

limited budget of $7 billion will require a staged implementation. Therefore, FirstNet has requested four

data collection elements from the District and states, which it will use for its Comprehensive Network

Solution(s) Request for Proposal (RFP) to be released in late 2015 and state network plans that will be

developed after the RFP is awarded.

Public Safety Users and Entities This document applies FirstNet’s working definitions of public safety users and entities, as interpreted in

the FirstNet Third Notice requesting public comment, to the District of Columbia public safety user

environment.

FirstNet’s interpretations of public safety users and entities have broad implications for states. Using

these interpretations as a guideline, the District SLIGP planning team has categorized entities within the

District of Columbia in the following ways:

District agencies under the mayor with a primary public safety mission. These agencies are first

responders in conformance with the traditional definition of public safety. They are represented

in the Statewide Interoperability Executive Council (SIEC) and the Interoperable

Communications Committee (ICC).

District agencies that directly support public safety. These agencies are also represented in the

SIEC and the ICC. Included here is the DC National Guard.

District agencies with some component that supports public safety. These agencies do not

directly support public safety but have a public safety or emergency management division that

qualify as public safety users under the FirstNet interpretation.

Other first responder entities, non-federal. These first responder entities in conformance with the narrow definition of public safety may be District or regionally focused, such as the National Cathedral Police or WMATA Metro Police.

Other first responder entities, federal. Federal agencies with a public safety mission are captured but data is not included in the District data package.

Utilities



FirstNet Requested Data FirstNet has requested four data collection elements from the District and states:

Coverage objectives – States should include desired coverage areas by developing their own

baseline coverage objectives or by providing feedback on the FirstNet-developed baseline.

FirstNet is also asking states to provide a phased build-out approach and recommendations on

targeted areas or objectives for each phase.

Users and their operations – Information about Public Safety Entities (PSEs), their devices, and

their operational areas.

Application usage – States should include information about public safety’s application usage;

frequency of use; and potential future use, as well as capturing and analyzing data that

quantifies how much data is actually being used by a variety of PSEs.

Current providers and procurement – Including information about mobile data providers, plans,

and costs.

District Data Resources The primary District data sources for the FirstNet analysis come from:

Calls for Service (CFS) provided by the Office of Unified Communications (OUC) – Descriptive statistics of the data indicate that 2014 and 2015 were stable years to conduct comparative data analysis. The data follows a relatively normal distribution of CFS, indicating that it would serve as a useful sample during analysis

DCGIS core geospatial data collected through partnerships with multiple DC agencies, including: o Population o Transportation o Key points o Other Categories

Citywide Data Warehouse (CDW) – Additional data, including 311 data, or other datasets, deemed integral or that provide greater context to the analysis. The primary requirement for including or not including a dataset rests with whether it appeared to put a strain on broadband needs or availability.

All data with the exception of calls for service data is available at http://data.dc.gov.

All calls for service data are destroyed once the data has been processed and aggregated. All data will be

compiled and combined using a weighted “mesh” algorithm to establish an overall “Public Safety

Broadband Need” value. This will be delivered as a density map, with a weighted grid at 200 meters per

hexagonal cell. The “Public Safety Broadband Need” value is used to prioritize the broadband coverage

needs and establish a phased deployment plan for the mobile data broadband network in the District.

In addition to mapping data, the District SLIGP team gathered data from its face-to-face outreach

meetings with District public safety responder and public safety support agencies, as well as city

agencies that have some division of public safety response or support. The team also gathered data

from its outreach to non-District entities, including WMATA Metro Police, National Guard, Pepco, the

National Cathedral Police, the University Consortium police, and so on.

http://data.dc.gov/



The District SLIGP team is also including data gathered from the responses by 14 District public safety

entities that completed the Department of Homeland Security (DHS) Office of Emergency

Communications (OEC) Mobile Data Survey Tool (MDST): 12 District public safety responder and support

agencies, WMATA Metro Police, and the DC National Guard. Data in sections 2, 3, and 4 are drawn from

the survey results along with supplementary data (such as user counts) from other entities gathered in

earlier outreach sessions.

Groups involved in preparing data for this report include:

District public safety stakeholder agencies, via face-to-face discussions and participation in the

Mobile Data Survey Tool (MDST)

Office of the Chief Technology Officer (OCTO) GIS team in coordination with the OUC

District In-Building Wireless team (OCTO, OUC, Department of General Services (DGS),

Department of Consumer and Regulatory Affairs (DCRA))

OCTO Telecom Services team

The District FirstNet planning team (OCTO, OUC)



1.a. Coverage Objectives The District FirstNet team has determined that a coverage prioritization strategy is needed to analyze

where broadband coverage is most needed and to propose build-out phases. A methodology to

prioritize coverage based on specific need factors and historical data follows.

Coverage Background FirstNet has provided guidance to the states and the District on developing coverage recommendations

and how to discuss these with the FirstNet consultation team. Initially, FirstNet provided the District

with baseline coverage (Figure 1). This data uses a 1-mile by 1-mile grid based on the following data:

Public safety user population

US population

Developed areas/buildings

Roadways (and other transportation), including roads and highways, commercially navigable

waterways, railroads, and transit links

Public safety high risk/areas of interest

For the District of Columbia, it provides suggested levels of coverage based upon the following criteria:

High Concentration – Metro areas with a population density greater than 1,000 people per

square mile should be designed for In-Building Coverage with a handheld unit (Red).

Moderate Concentration – Areas where the population density is less than 1,000 people per

square mile but more than 500 people per square mile should be designed for Handheld

Coverage/Partial In-Building (Blue).

Low Concentration – Interstates and rural areas where the population density is at least 5

people per square mile should be designed for Vehicular Coverage (Green).

Federal land (Gray).

Note: Because most states do not have full coverage of every area by a public safety official, FirstNet

must account for farmlands and remote areas where public safety may not patrol. In contrast, as a

completely urban jurisdiction the District in its entirety requires some level of patrol coverage.



Figure 1: FirstNet Baseline Coverage Estimate

In this initial suggested baseline, the District notes that several areas identified by FirstNet as Moderate

Concentration include key areas of critical federal and District infrastructure, large public venues, key

and gathering places, in addition to residential and park areas:

National Mall, White House/Pennsylvania Avenue, Federal Triangle, and Tidal Basin (downtown)

DC Waterfront area (with Nationals Stadium, the Navy Yard, and planned DC United Stadium) and Bolling Navy Base (Southeast)

Washington Aqueduct/Water Treatment Facility (Northwest)

District Coverage Analysis Given that the majority of the District is identified as High Concentration, Figure 2 highlights areas where

coverage is most needed and where the system will need the most capacity.

The District provided more detailed analysis using a 200-meter hexagonal grid, with weighted factoring

in 911 calls for service data, population, transportation elements, critical facilities, public places and



venues, and other coverage. This includes data from over 696,000 911 calls, drawn from May-

September 2014 and May-September 2015. (These factors are explained in more detail in the

“Methodology” section.)

The traffic demand map highlights areas of the District where the network will have higher than average

network loading and may require additional LTE sites. Data categories include:

Population

Transportation

Key Points

911 calls for service

The map (shown in Figure 2 and Figure 3) is publicly accessible at http://arcg.is/1Qq7K4W.

Figure 2: Traffic Demand Map Tool

Source: OCTO GIS, 2016

http://arcg.is/1Qq7K4W



Figure 3: Public Safety Communications Demand Heat Map

Source: OCTO GIS, 2016

Note: Regarding in-building coverage, the District team has not yet competed its identification of the

level of coverage required and where coverage inside buildings is needed.

Population Census tract information and major gathering locations data were gathered to reflect the location

characteristics of population. These are represented in three layers: Population by Census, Major

Population Locations, and National Mall.

The Population by Census layer shows the level of population by census tract based on the 2010 census.

Dark violet tracts have a population over 3,000. Medium violet tracks have a population between 2,000

and 3,000. Light violet tracks have a population less than 2,000.



The Major Population Locations layer shows large gathering locations, such as hotels, museums, parks,

and event-driven sites such as stadiums and theatres.

The final layer shows the National Mall, which hosts many planned and unplanned major events, such as

presidential inaugurations, July 4th festivities, and marches and demonstrations.

Transportation Transportation and Metro station data were mapped to show major transportation-related locations as

critical to public safety coverage.

The Transportation heat map layer shows transportation-related infrastructure in a sector, including

evacuation routes, major roads, railroads, and metro lines. Areas in red indicate locations several of

these elements in close proximity. Yellow indicates areas with fewer transportation elements.

The Metro Station Concentrations layer shows Metro Stations throughout the city. Red dots indicate

areas where three or more stations are tightly grouped, orange shows two stations in close proximity,

and yellow indicates stand-alone stations.

Key Points The Key Points layer shows public safety locations such as fire and police stations and hospitals. Like the

Metro Station layer, a darker color indicates locations where facilities are close to each other.

Calls for Service The Calls for Service layer shows 911-call activity as a heat map based on where the emergency

occurred, not from where the call originated. Data is from 2014 and 2015. The color ranges from red to

yellow, with red indicating the greatest density of calls.



1.b. Phased Deployment Approach As a small, densely populated jurisdiction of 68.3 square miles and a number of dense, historical

buildings, the District of Columbia has a need for ubiquitous coverage in a public safety mobile data

broadband network. As home to the federal government and hub for many large-scale planned (and

unplanned) events, the District has significant needs for high capacity.

In general, the District’s requirements for the network are set according to public safety standards

(including 99.999 percent availability, no single point of failure, etc.).

Table 1: District of Columbia Proposed Deployment Phases

Phase Requirements Rationale Standards Timing

1 100 percent external coverage entire District

Indoor coverage in existing DC government buildings or roaming to commercial

Small geographic area (68.3 square miles).

Need for ubiquitous coverage throughout jurisdiction

95% reliability, 256 Kbps minimum throughput per user with the following minimum objectives:

Outdoor on-street and In-car everywhere

Residential two-wall penetration

Dense urban Areas (downtown business district) one-wall penetration

Initial deployment

2 In-building coverage in District downtown fire zone and other identified critical infrastructure buildings outside the fire zone.

In-tunnel coverage for Metro, commuter rail, and highway tunnels.

Many District government and most federal government and commercial buildings are within the fire zone area.

Metro and other tunnels, through which over 700,000 people pass per day, remain vulnerable areas of unreliable coverage.

Address additional capacity and throughput concerns by adding new sites to Phase 1 network as needed and where necessary.

Connect FirstNet to in-building wireless systems deployed and under construction by the District, and to in-building wireless systems operated by commercial carriers and building owners.

3 Enhanced external coverage, addressing:

Special events capacity

Federal enclave area

The District regularly hosts NSSEs and events of over 500,000 people.

Federal seat of government

Address additional capacity and throughput concerns, by adding new sites to Phase 1 and 2 network as needed and where necessary.



2. User Data See also the separate spreadsheet (DC_Agency_Outreach_MDST_Data_20150930.xlsx) for full

information.

2.a. Public Safety Entity Demographics The following table shows data from MDST responses along with additional information provided by

agency through outreach.

Comments:

The overall employee (user) count includes agency data from the MDST and information from

face-to-face outreach.

Twenty-eight federal law enforcement agencies operate with full police powers in the District

with 10,222 full-time federal officers, according to 2008 Department of Justice statistics.1 These

agencies, listed in Section 2.d-i., are not included in District data.

HSEMA’s part-time employees are interns. Two of its vehicles are unified mobile command

vehicles, approximately seven are command vehicles and others are executive transport.

DFS count includes four new vehicles it is purchasing by FY16.

OCME plans to increase its vehicles to 18-20 by the end of FY16.

DGS PSD plans to increase staffing to 220 by 2022.

WMATA Metro Police data is included here, but may also be counted in data provided by the

state of Maryland. The user count of 745 includes 450 sworn officers, 100 Special Police, 17

communication staff and other staff.

In separate discussions with MPD, not captured in the MDST results, MPD and HSEMA stated

the need for an autonomous LTE base station with core.

PUBLIC SAFETY ENTITY EMPLOYEES FULL TIME EMPLOYEES

PART TIME EMPLOYEES

VOLUNTEERS VEHICLES

Dept. of Health (DOH) 900 900 50 50

Dept. Public Works (DPW) 1400 1400 2534

D.C. Fire and EMS Department (F/EMS)

2001 2001 392

Homeland Security & Emergency Management (HSEMA)

105 85 20 16

D.C. Metropolitan Police Dept. (MPD)

4600 4400 100 100 1500

D.C. Nat Guard - Joint Force Headquarters

1445 375 1070 100

D.C. Office of Unified Communications (OUC)

340 340 12

1 http://www.bjs.gov/content/pub/pdf/fleo08.pdf

http://www.bjs.gov/content/pub/pdf/fleo08.pdf



Dept of Corrections 920 920 30 45

Office of the Chief Technology Officer

563 563 33

Department of Forensic Sciences

130 130 1 12

Office of the Chief Medical Examiner

80 80 17

District Department of Transportation

1300 1000 200

Dept. of Youth Rehabilitation Services (DYRS)

514 484 30 80 6

University of the District of Columbia (UDC)

40

DC Department of Human Services/Emergency Response (DHS)

54

DC Water 130

Department of Behavior Health (DBH)*

25

DC DGS Protective Services Division (PSD)

50

DC Public Library Police* 25

DC Housing Authority Police

50

Executive Office of the Mayor*

5

National Cathedral Police 15

Private universities police and security*

390

Private hospital emergency management *

100

WMATA Metro police 745 170

Pepco* 900

American Red Cross* 240

American Medical Response*

100

Total 17205 12678 1221 360 5087

*Estimated based on entity inputs.



2.b. Devices The following table shows data from MDST responses along with additional information provided by

agency through outreach.

PUBLIC SAFETY ENTITY

VOICE/DATA DEVICES - PERSONNEL

DATA ONLY DEVICES - PERSONNEL

OTHER DEVICES - PERSONNEL

VOICE/DATA DEVICES - VEHICLES

DATA ONLY DEVICES -VEHICLES

OTHER DEVICES - VEHICLES

DOH 572 313

DPW 1401 405

F/EMS 273 25 123

HSEMA 81 50

MPD 2962 300 2800

D.C. National Guard

114 525

OUC 120 1400

DOC 143 6

OCTO 607 418

DFS 83 13

OCME 54 100

DDOT 1453 480 50 10

DYRS 200 80 3

DC Water 100 45

WMATA Metro Police

260 30 50 50

Pepco 1800 1000

Totals 8323 6045 2923 53 1145 10

2.c. Users and Devices Summary On questions related to use of personal devices, the use of machine-to-machine (M2M), and planned

changes, agencies provided the following answers:

Eight of 13 agencies allow personal devices to be used for work while 10 of 13 acknowledged

that personal devices were permitted on the agency network and access to applications.

No agency provides a stipend for use of personal devices.

Five agencies (DOH, DPW, HSEMA, DOC, MPD and OCTO) use or will soon use M2M devices.

Four agencies (DPW, MPD OCTO, and DDOT) foresee significant changes that will impact

increase in device counts.

Notes on users and devices:

The DOH device count of 572 includes 490 OCTO managed devices, seven EWRAP devices, and

75 patient tracking devices. DOH also considers its patient tracking devices (handheld scanners

and tablets) as M2M devices.

DPW plans to add 100-150 devices for parking enforcement in FY16.



OUC has included in voice/data devices the devices OUC staff use and in data only device counts

the tablets and modems it manages for FEMS and MPD.

Most agencies allow personally owned devices to enhance communications for messaging on

Outlook Exchange.

MPD deploys M2M devices for its License Plate Reader (52), Automated Traffic Enforcement

Unit (317), CCTV (140), and ShotSpotter (240).

MPD has added 2,800 body cameras and 1,400 smart phones.

DOC uses four M2M devices for wireless fingerprint scanning.

OCTO has estimated that it will be deploying an estimated 100 M2M devices for Smart City pilot

and future initiatives.

DFS is looking to purchase up to 70 laptop/tablet devices for the increase in its Crime Scene

Sciences staff. It will also be using TeamViewer, a product similar to VPN level of encryption to

prevent unauthorized user access. Some investigators cameras have M2M capability but not an

official use at this time.

DDOT has deployed 160 ITS and roadway sensors for traffic counting purposes. It has deployed

nearly 200 wireless tablets in the last 2 years.

DYRS will be launching a medical records system and so will issue approximately 20 mobile

tablets.


PERSONAL DEVICES PERMITTED FOR WORK

PERSONAL DEVICES PERMITTED ON AGENCY NETWORK/APPS

STIPEND PAID FOR USE OF PERSONAL DEVICES

USE OF M2M DEVICES

M2M DEVICES

PLANNED CHANGES THAT IMPACT DEVICE COUNTS

DOH Yes Yes Unknown Yes 75 Minor to no change

DPW No Unknown No Yes 20 Significant increase

F/EMS Yes Yes No No

HSEMA Yes Yes No Yes Minor to no change

MPD Yes Yes No Yes 1949 Significant increase

D.C. National Guard

No No No No Minor to no change

OUC No No No No Unknown

DOC Yes Yes No Yes 4 Minor to no change

OCTO Yes Yes No Yes 100 Significant increase

DFS Yes Yes No No Minor to no change

OCME No Yes No No Minor to no change

DDOT No Yes No Yes 160 Significant increase

DYRS Yes Yes No No Minor to no change

WMATA Metro Police

Yes Yes No No Undetermined

Total 3058



2.d-i. Operational Areas District of Columbia government public safety user agencies operate throughout the entire District.

However, the following responder agencies have specific areas of operation within the District:

DCPL Police – Public Libraries

National Cathedral Police – National Cathedral grounds

Private universities police and security – University campuses

Metro Transit Police – Full local police authority in Maryland, Virginia, and Washington, DC, with

a focus on the 1,500 square mile transit zone including buses and subways.

In addition, the numerous federal law enforcement agencies have varying jurisdictional areas and or

focus, including:

Amtrak Police

Armed Forces Retirement Home Police

Bureau of Alcohol, Tobacco, and Firearms

Bureau of Engraving and Printing Federal Police

Drug Enforcement Agency

Federal Bureau of Investigation

Federal Bureau of Prisons

Federal Protective Service

GPO Uniformed Police Branch

Homeland Security Investigations

Military Police Corps

National Zoological Park Police

Supreme Court Police

Smithsonian Police

US Air Force Office of Special Investigations

US Army Criminal Investigative Command

US Capitol Police

US Coast Guard Investigative Service

US Department of Defense Police

US Department of Veterans Affairs Police

US Federal Reserve Police

US Mint Police

US Naval Criminal Investigative Service

US Park Police

US Pentagon Police

US Postal Inspection Service

US Secret Service

US State Department Diplomatic Security Service



2.d-ii. Calls for Service The Office of Unified Communications manages the District’s Public Safety Answering Point (PSAP), and

handles an average of 1.5 million 911 calls per year. The District team analyzed 911 call data from 2014

and from a sample window of May through September 2015. Figure 4 shows the sheer density of 911

calls distributed across the entire District.

Figure 4: District 911 Calls – 2015 (May-September)

Data Source: OUC and OCTO GIS, September 2015



In addition to aggregated call data over time, the District team compared 911 call data on Saturday, July

4, 2015 with Tuesday, July 7, 2015, a more typical weekday, across a 24-hour period (see Figure 5). The

results show an overall significant difference for the holiday, especially (as expected) in the evening

calls.

Figure 5: 911 Call Comparisons, July 4 and July 7, 2015

Data Source: OUC, September 2015

The following maps show the comparison of data by location in Hour 23 (11 p.m.) for the two days.

Figure 6: 911 Call Comparisons - July 4 and July 7, 2015

Data Source: OUC, September 2015

0

50

100

150

200

250

300

350

400

1 3 5 7 9 11 13 15 17 19 21 23

7/4/2015 (Saturday)

7/7/2015 (Tuesday)

3,260 calls

2,669 calls



3. Applications The following tables show data from Mobile Data Survey responses along with additional information

provided by agency through outreach.

3.a Application Usage Primary application usage data in the different communications areas is drawn from agency responses

to the MDST and through agency outreach meetings. The MDST design in this section has the potential

for improvement as District respondents found selections ambiguous, with some being overly specific

and others overly broad.

Highlights for application usage include:

Communications – Not surprisingly, most agencies listed the email exchange used daily as their

primary communications tool.

o DOH listed Health Alert Network (HAN) as the primary alerting program used during an

incident. It allows for text to voice, pager, SMS, etc., as well as confirmation that the

message is received. It has the capability to enhance messaging by adding data/video to

e-mail alerts.

o HSEMA noted that while email is the primary application used for day-to-day

communications for administration staff; the Everbridge application is used to send

text/SMS/email/voice for operational staff. Also of note in relationship to Everbridge, is

that many recipients are from other city agencies and while HSEMA is the contracting

authority for Everbridge, a command center in another agency will also use the

application internally.

Over-the-top VoIP – Responses varied from “none at this time” (2) and “unknown” (2) to VoIP

(4), Cisco Jabber (2), Skype (2), and WebEx (1). The survey question and the range of selectable

answers were ambiguous. Agencies that use over-the-top VoIP do so either daily or weekly.

o OCME currently uses three Cisco Jabber clients for over-the-top VoIP (integrated with

Cisco VTC) for executives, with a plan to increase to 10.

o DYRS uses Skype for youth detained in remote locations to communicate with staff and

relatives.

AVL

o Six agencies currently do not use AVL (DOH, OCTO, DFS, OCME, and DYRS). Of these

DYRS and OCME indicated that AVL is desired.

o DPW and DDOT use Enterprise Information Solutions (for snow plow tracking) on an

infrequent basis.

o OUC, FEMS, and MPD use the Intergraph system for 911 daily.

CAD

o DOH, DPW, FEMS, HSEMA, MPD, and OUC are tied into the Intergraph CAD system

managed by OUC for 911.



o DOH is currently using CAD for monitoring only. The agency does not assume an active

role in entering data.

Database

o Most agencies are using SQL either on its own or with other solutions (Oracle, Crystal

Reports).

o DOH uses several databases built on multiple platforms. Some are commercially

developed; some are locally developed.

o DOC uses Pro Metrics for data gathering and agency reporting.

General Connectivity – District agencies are using the MS Exchange (MS Outlook is considered

part of MS Exchange) system managed by OCTO.

Field Based Reporting

o DOH inspectors use computer based reporting in the field.

o OCME plans to deploy a mobile version of case management system for its field based

reporting.

Intranet/VPN

o Most District agencies use the OCTO managed Juniper PIN Safe or Junos Pulse solution

on a daily or weekly basis.

o DFS uses TeamViewer, which provides an inexpensive, reliable and secure connection

using dual-factor remote access and support over a cellular service.

Video

o This survey question’s range of selectable answers was ambiguous. Most agencies

answered based on their use of video teleconferencing; some agencies also responded

based on their use of CCTV monitoring cameras.

o DOC uses Aventura for CCTV, Cisco VTC for executive communications, and GTL/Renovo

inmate video visitation.

Telemetry

o DDOT has District-owned street level imagery, including alleys.

o DYRS uses Veritraks, which is also used by the federal Court Services and Offender

Supervision Agency (CSOSA); the application offers web access to MPD and other local

law enforcement.

o MPD deploys bait cars and bait bicycles as needed, usually on a weekly basis.

Other

o DDOT plans to digitally transmit to MPD/FBI AFIS system case managers.

o DGS PSD monitors alarms for DC One Card readers in District government buildings.

o Pepco AMI uses 900 MHz spectrum for data connection, leased through a local vendor,

Silver Spring Networks.



Primary Application for Communications PUBLIC SAFETY ENTITY PRIMARY APPLICATION COMMUNICATIONS FREQ OF USE

DOH Health Alert Network Weekly

DPW email exchange - with unified messaging Daily

F/EMS email exchange Daily

HSEMA email exchange Daily

MPD email exchange Daily

D.C. National Guard email exchange Daily

OUC email exchange Daily

DOC email exchange Daily

OCTO email exchange Daily

DFS email exchange Daily

OCME email exchange Daily

DDOT email exchange Daily

DYRS email exchange Daily

DC Water

DGS PSD email exchange Daily

WMATA Metro Police Phone and tablet Daily

Pepco

Primary Application for VoIP PUBLIC SAFETY ENTITY PRIMARY APPLICATION - VOIP FREQ OF USE VOIP

DOH Unknown Unknown

DPW Unknown Unknown

F/EMS none at this time Not Used

HSEMA WebEx Daily

MPD None at this time Not Used

D.C. National Guard Polycom, VoIP Daily

OUC VoIP Daily

DOC Cisco Jabber Infrequently

OCTO VoIP Daily

DFS none at this time Infrequently

OCME Cisco Jabber Weekly

DDOT VoIP Daily

DYRS Skype Weekly

DC Water

DGS PSD

WMATA Metro Police Skype Infrequently

Pepco



Primary Application for AVL PUBLIC SAFETY ENTITY PRIMARY APPLICATION AVL FREQ OF USE AVL

DOH Currently not AVL'd Not Used

DPW EIS Infrequently

F/EMS Intergraph Daily

HSEMA Currently not AVL'd Not Used

MPD InMotion – managed by OUC Daily

D.C. National Guard Blue Force Tracker Infrequently

OUC Mobile Router, CAD Daily

DOC Autofind Daily

OCTO Currently not AVL'd Not Used

DFS Currently not AVL'd Not Used

OCME Currently not AVL'd Not Used but Desired

DDOT EIS Infrequently

DYRS Currently not AVL'd Not Used but Desired

DC Water

DGS PSD

WMATA Metro Police AVL integrated into CAD Daily

Pepco TELOGIS Daily

Primary Application for Location Services Most agencies that use location services are using some form of ArcGIS and/or Google Maps.

PUBLIC SAFETY ENTITY PRIMARY APPLICATION LOCATION SVC FREQ OF USE

DOH ArcGIS Infrequently

DPW ArcGIS and AGOL Infrequently

F/EMS Google Maps Daily

HSEMA ARCGIS Daily

MPD OUC managed tool Daily

D.C. National Guard Blue Force Tracker Infrequently

OUC CAD, Mobile Router (Mobility Server oMM) Daily

DOC None Not Used

OCTO ARCGIS, Google Maps, Internally developed fiber asset map tool

Daily

DFS Google Maps Daily

OCME ARCGis Infrequently

DDOT ArcGIS and AGOL / Daily

DYRS Google Maps Daily

DC Water ArcGIS Daily

DGS PSD

WMATA Metro Police CAD and Motorola P1 Daily

Pepco



Primary Application for CAD PUBLIC SAFETY ENTITY PRIMARY APPLICATION CAD FREQ OF USE

DOH Intergraph Daily

DPW Intergraph Daily

F/EMS Intergraph Daily

HSEMA Intergraph Daily

MPD Intergraph Daily

D.C. National Guard Not used Not Used

OUC Intergraph Daily

DOC Not used Not Used

OCTO Not used Not Used

DFS Not used Not Used

OCME Not used Not Used

DDOT ATMS and CapTop Daily

DYRS Not used Not Used

DC Water GeoTab Daily

DGS PSD Not Used Not Used

WMATA Metro Police PSSI Daily

Pepco

Primary Application for Database PUBLIC SAFETY ENTITY PRIMARY APPLICATION DATABASE FREQ OF USE

DOH Department Built Daily

DPW WALES and NCIC for towing Daily

F/EMS SQL Daily

HSEMA SQL and Oracle Daily

MPD Cognos Daily

D.C. National Guard SQL Daily

OUC SQL Daily

DOC SQL and Crystal Reports Daily

OCTO SQL Weekly

DFS Search Tool with product with help from Crystal Reports Daily

OCME SQL Daily

DDOT Oracle and SQL Daily DYRS Justis Daily

DC Water

DGS PSD WALES ORI, but no connection

WMATA Metro Police SQL Daily Pepco



Primary Application for General Connectivity PUBLIC SAFETY ENTITY PRIMARY APPLICATION CONNECTIVITY FREQ OF USE

DOH MS Outlook Daily

DPW MS Exchange Daily

F/EMS MS Exchange Daily

HSEMA Internal District government systems (including Exchange) over District government network Daily

MPD MS Exchange Daily

D.C. National Guard MS Exchange Daily

OUC MS Outlook Daily

DOC MS Exchange Daily

OCTO MS Exchange Daily

DFS MS Outlook Daily

OCME MS Exchange Daily

DDOT Internet Explorer, Outlook Daily

DYRS MS Exchange Daily

DC Water

DGS PSD MS Exchange Daily

WMATA Metro Police

Pepco

Primary Application for Field Based Reporting PUBLIC SAFETY ENTITY PRIMARY APPLICATION FIELD BASED REPORTING FREQ OF USE

DOH DPW Intergraph RMS Daily

F/EMS Fire RMS - Zoll; EPCR - Safetypad Daily

HSEMA WebEOC Daily

MPD Cobalt Daily D.C. National Guard none Not Used

OUC none Infrequently

DOC Lotus Notes and Pro Metrics Daily

OCTO none Not Used DFS

none Not Used but Desired

OCME none

Not Used but Desired

DDOT Cityworks and TOPS Daily

DYRS FamCare for case management and other things Daily

DC Water

DGS PSD MS Exchange Daily WMATA Metro Police

Pepco



Primary Application for Intranet/VPN PUBLIC SAFETY ENTITY PRIMARY APPLICATION INTRANET/VPN FREQ OF USE

DOH

DPW Pinsafe and Junos Daily

F/EMS NetMotion Daily

HSEMA Juniper VPN Daily

MPD SonicWall Daily

D.C. National Guard Citrix, Cisco VPN Weekly

OUC Juniper, Smithmicro Quicklink Mobility Daily

DOC Juniper Pulse Daily

OCTO Air Watch Daily

DFS TeamViewer Daily

OCME Juniper Pulse Weekly

DDOT Juniper and Junos Pulse Daily

DYRS Juniper PIN Safe Daily

DC Water

DGS PSD

WMATA Metro Police Verizon MPLS Daily

Pepco

Primary Application for Video PUBLIC SAFETY ENTITY PRIMARY APPLICATION VIDEO FREQ OF USE

DOH

DPW Daily

F/EMS none Not Used

HSEMA Multiple: Cisco, Skyline, Aventura Daily

MPD TASER AXON FLEX ON BODY POINT OF VIEW CAMERAS

dAILY

D.C. National Guard Polycom Weekly

OUC none Infrequently

DOC Aventura, Cisco VTC, GTL/Renovo Daily

OCTO Telepresence Daily

DFS none Not Used

OCME Cisco VTC Weekly

DDOT CCTV Daily

DYRS Cisco for site to site video conferencing Daily

DC Water

DGS PSD

WMATA Metro Police

Pepco

National Cathedral Police CCTV



Primary Application for Telemetry PUBLIC SAFETY ENTITY PRIMARY APPLICATION TELEMETRY FREQ OF USE

DOH

DPW EJ Ward W4 - fuel system sensors Daily

F/EMS Various proprietary Daily

HSEMA LMR, cellular and DSRC Daily

MPD Small selection operations (bait cars, bait bicycles) Weekly

D.C. National Guard LMR, cellular and DSRC Infrequently

OUC InMotion Router Daily

DOC None Not Used

OCTO None Not Used

DFS None Not Used

OCME None Not Used

DDOT Daily

DYRS Veritracks Daily

DC Water Maximo Daily

DGS PSD Daily

WMATA Metro Police Integrated through AVL and CAD Daily

Pepco Advanced Metering Infrastructure (AMI) Daily

National Cathedral Police CCTV integrated through Exacq

Other Primary Applications PUBLIC SAFETY ENTITY PRIMARY APPLICATION OTHER FREQ OF USE

DOH

DPW Bulk Mobile Daily

F/EMS Don't know Unknown

HSEMA Everbridge, Activu, Emnet, WAWAS, WebEOC, CCTV, VTC, GIS

Daily

MPD none Infrequently

D.C. National Guard Don't know Unknown

OUC Patient Care Safetypad, E-911 CAD, Police and Fire application

Daily

DOC none Not Used

OCTO Internally developed fiber asset map tool Daily

DFS none Not Used

OCME FACTS (Forensic Analytic Case Tracking System), 3M Cogent/Fusion Digital Fingerprinting

Daily

DDOT Street Level Imagery Cyclomedia Globespotter Daily

DYRS none

DC Water Monitoring 12,000 fire hydrants and 14,500 miles of water mains

DGS PSD Daily

WMATA Metro Police Updating CAD to Motorola Premier One



Pepco Mutual Assistance Routing System (MARS) to handle overflow calls

When needed, emergency

National Cathedral Police Clancey Handheld Ticket Writers; Alertus mass notifications

Daily

3.b Data usage

Average Monthly Data Usage The following table shows data entered in the MDST for average monthly data usage.

PUBLIC SAFETY ENTITY AVG MONTHLY DATA USAGE

DOH 1 - 5 Gb

DPW >10 Gb F/EMS Unknown

HSEMA 1 - 5 Gb

MPD 1 – 5 GB

D.C. National Guard 512Mb - 1Gb OUC 1 - 5 Gb

DOC <512 Mb

OCTO 1 - 5 Gb

DFS 1 - 5 Gb OCME 1 - 5 Gb

DDOT >10 Gb

DYRS 1 - 5 Gb

DC Water DGS PSD

WMATA Metro Police 1 - 5 Gb

Pepco



Daily Data Usage The following chart shows mobile data usage for District public safety for over one month from June 15,

2015 to July 15, 2015, which includes the July 4 celebrations. Peak usage occurred between June 30 and

July 1.

The following chart shows mobile data usage for District public safety for over 15 days from November

1, 2014 to November 15, 2015, which includes the Concert for Valor on November 11.

-

10.000

20.000

30.000

40.000

50.000

60.000

6/1

5

6/1

6

6/1

7

6/1

8

6/1

9

6/2

0

6/2

1

6/2

2

6/2

3

6/2

4

6/2

5

6/2

6

6/2

7

6/2

8

6/2

9

6/3

0

7/1

7/2

7/3

7/4

7/5

7/6

7/7

7/8

7/9

7/1

0

7/1

1

7/1

2

7/1

3

7/1

4

7/1

5

Data Usage (GB)

-

10.000

20.000

30.000

40.000

50.000

60.000

70.000

11/1 11/2 11/3 11/4 11/5 11/6 11/7 11/8 11/9 11/10 11/11 11/12 11/13 11/14 11/15

Data Usage (GB)



4. Contracts and Procurement

4.a. Procurement Vehicles, Plan Costs, and Specialized Services The District of Columbia has a flexible contract vehicle with cellular carriers for its enterprise-wide

wireless communications that is device independent and pools voice, data, and video usage across all

District agencies.

Provider Contracts Overview The District of Columbia uses the following carriers:

AT&T Mobility – IDIQ contract originally set to not exceed $2M per year.2

Sprint – IDIQ contract not to exceed $2.024M per year.3

T-Mobile – Products and services delivered in accordance with terms and conditions of its GSA

Schedule GS-35F-0503M, not to exceed $0.9M per year.

Verizon – Fixed Unit Prices from GSA FSS Contract, monthly billing set to not exceed $4.2M per

year.4

OCTO manages the District government cellular contracts on a 1-year contract basis with 1-year options.

The contract vehicle features:

Pooling

o Four largest cellular carriers are part of the citywide pooling program

o Standardized calling plan profiles by role and/or agency, and devices for Low, Medium,

High users

o Predictive monitoring through live feed from vendors

Centralized requirements policies:

o Procurements require contractor to provide mobile/PDA.

o 95% or above annual telecommunications assets certification.

o Identify end users to plan number and email address.

Self-service portal for agencies

No service for outbound international calls

E-mail bill and plan directly to end users (via OCTO Telecom team)

Internal alerts for cell phone overages

OCTO oversees cellular service on these contracts for the District of Columbia, and has the capability to

monitor device usage on carrier networks. Each agency assigns an Agency Telephone Coordinator (ATC)

2 http://dccouncil.us/B21-0062-Introduction-2.pdf

3 http://lims.dccouncil.us/Download/31639/PR20-0752-Introduction.pdf

4 http://dcclims1.dccouncil.us/images/00001/20130905111535.pdf

http://dccouncil.us/B21-0062-Introduction-2.pdf

http://lims.dccouncil.us/Download/31639/PR20-0752-Introduction.pdf

http://dcclims1.dccouncil.us/images/00001/20130905111535.pdf



to act as its point of contact with OCTO and to be the responsible party to review any procurement

requests related to the carrier contracts before submission to OCTO.

Highlights from the MDST responses include:

All responding agencies, except for the DC National Guard, use multiple providers.

Procurement process used by District agencies is a Master Contract – GSA/Federal managed for

the District government by OCTO.

The most common internal procurement option is the web-based Request for

Telecommunications Systems (RTS) service managed by OCTO. District agencies use other

procurement options if needed on a case-by-case basis: including agency procurement credit

card (P-card) and Memorandum of Understandings for capitally funded projects. DDOT also uses

an IDIQ contract.

OCTO has a direct sales account with providers on behalf of District agencies; some agencies

also have direct sales account relationships with providers.

Most agencies reported a direct technical support relationship with providers, through the

agency ATCs.

DPW, HSEMA, and OUC utilize specialized services: AT&T push-to-talk for DPW, cell-on-wheels

services for HSEMA for communication at special events, and data backhaul for OUC.

MPD and HSEMA use the Everbridge paging system and DOC uses paging for building-wide

announcements within its jail facility.

All agencies except one reported that they “would pay a little more to have fixed rates

regardless of usage.”

All agencies reported that the agency pays for the mobile service.

All agencies indicated that their data limits are either “Pooled” or “Unlimited.” For District

government agencies, OCTO manages the citywide contract, which has pooled for all elements

(voice, data, and video) unless otherwise specifically noted.



Providers PUBLIC SAFETY ENTITY

AGENCY USES MULTIPLE PROVIDERS

REASON FOR MULTIPLE PROVIDERS

OTHER PROCURMENT OPTIONS?

DESCRIPTION OF OTHER PROCUREMENT OPTIONS

DIRECT SALES ACCOUNT WITH PROVIDER

DIRECT TECH SUPPORT WITH PROVIDER

ANY ADDITIONAL SPECIALIZED SERVICES

SPECIALIZED

SERVICES

DESCRIPTION

DOH Yes Yes Agency procurement - Pcard

No Yes Unknown

DPW Yes AT&T, Verizon Wireless, Sprint

Yes P-card, RTS, MOU for capitally funded projects

Yes Yes Yes For example,

push to talk with

ATT, ability to

create talk

groups in-house

F/EMS Yes We used many different data connectivity methods, and RMS

Yes Credit card, competitive bid

No Yes Unknown

HSEMA Yes Verizon Wireless, AT&T, Sprint, and dedicated emergency management satellite provider (Comlabs)

Yes Agency procurement. No Yes Yes Potential

services on Cell

on Wheels for

special events

MPD Yes Verizon, AT&T Yes No No No

D.C. National Guard

No Unknown No No No

OUC Yes Yes State based contracts Yes Yes Yes Backhaul

DOC Yes AT&T 60%, Verizon Wireless 20%, Sprint 15%, T-Mobile 5%

Yes RTS No Yes No

OCTO Yes Verizon Wireless, AT&T Wireless

Yes Yes Yes No

DFS Yes Verizon Wireless, AT&T, T-Mobile

No Yes Yes No

OCME Yes AT&T 50%, Verizon Wireless 50%

Yes P-card for small amount/emergency, Purchase order for over $2500, RTS

No Yes No



DDOT Yes ATT 80%, Verizon Wireless 15%, Sprint 3%, T-Mobile 2%

Yes IDIQ the Architecture and Engineering schedule - agency procurements / p-Card / RTS

No Yes No

DYRS Yes Verizon Wireless and ATT Yes P-Card No No No

WMATA Metro Transit Police

No Yes Yes Yes



Commercial Paging Use PUBLIC SAFETY ENTITY AGENCY USES COMMERCIAL OR SHARED PAGING

DOH

DPW No

F/EMS Yes - Everbridge

HSEMA No

MPD Yes - Everbridge

D.C. National Guard No

OUC No

DOC Yes – For building-wide announcements in jail facility

OCTO No

DFS No

OCME No

DDOT No

DYRS No

User Fees Average costs per public safety user vary, pending promotions and other factors. As of May 20, 2015,

average costs are:

Voice and data cell phone (including smartphones): $40.30

Voice only cell phone: $22.41

Data only devices (tablets, Mi-Fi, and data cards): $30.37

This represents a reduction in average costs from the previous year of approximately $8 less for voice

and data, $3 less for voice only, and $6 less for data only. Some MDST responding agencies have

reported paying up to $50.43 for voice and data services (FEMS) and $45.00 for data only (OUC).



PUBLIC SAFETY ENTITY MONTHLY USER FEES FOR VOICE/DATA

MONTHLY USER FEES FOR DATA ONLY

DOH 40 30.37 DPW 55 34

F/EMS 50.43 33.86

HSEMA 40.03 30.37

MPD 40 30.37 D.C. National Guard 5100 965

OUC 48.52 45

DOC 45 35

OCTO 40.03 30.37 DFS 40 30.3

OCME 40 30

DDOT 40 30

DYRS 52 24 WMATA Metro Transit Police 17 25

4.b. Barriers to Adoption MDST responses indicate District public safety responder and support agencies are split on their

interpretation of whether service cost, network reliability, are security are barriers to service, while

most agree that coverage is a barrier.

Highlights:

Agencies were split on whether they considered cost a barrier: Six agencies reported it as a

barrier; six reported it was not.

Agencies were split on whether they considered network reliability a barrier: Seven reported it

as a barrier; six reported it was not. However, two agencies that reported reliability was not an

issue also reported coverage as a barrier – indicating as a caveat that where coverage exists,

reliability is not an issue.

Agencies were split on whether they considered security a barrier: Seven reported it as not a

barrier; six reported it as a barrier.

Ten agencies reported that lack of coverage, or dead spots, was a barrier to service; three

agencies reported it was not.

Eleven agencies did not consider technical expertise a barrier to adoption; two agencies whose

primary users are not technically oriented (DYRS caseworkers and National Guard) reported

expertise as a barrier.




COST NETWORK RELIABILITY

SECURITY COVERAGE EXPERTISE COMMENTS

DOH Yes, Cost is a Barrier

No, Network Reliability is not a Barrier

No, Security is not a Barrier

Yes, Coverage is a Barrier

No, Expertise is not a Barrier

DPW Unknown Yes, Network Reliability is a Barrier




Reliability is issue for all providers

F/EMS Yes, Cost is a Barrier

Yes, Network Reliability is a Barrier

Yes, Security is a Barrier



HSEMA Yes, Cost is a Barrier





MPD No, Cost is not a Barrier



No, Coverage is not a Barrier


D.C. National Guard

Yes, Cost is a Barrier




Yes, Expertise is a Barrier

FirstNet would make it easy for DC

OUC No, Cost is not a Barrier





DOC No, Cost is not a Barrier





Sprint and Verizon Wireless coverage very poor at DC Jail, especially indoor coverage.

OCTO No, Cost is not a Barrier





DFS No, Cost is not a Barrier





Cellular service in our building is not optimal.

OCME Yes, Cost is a Barrier





No redundancy for COOP/outage In building coverage is good

DDOT No, Cost is not a Barrier





DYRS No, Cost is not a Barrier




Yes, Expertise is a Barrier

Case workers who use the devices are not technically savvy



Acronyms ALI – Automatic Location Information

AVL – Automated Vehicle Location

CAD – Computer Aided Dispatch

CQI – Channel Quality Indicator

DAS – Distributed Antenna System

DDOT – District Department of Transportation

DFS – District of Columbia Department of Forensic Science

DOC – District of Columbia Department of Corrections

DOH – District of Columbia Department of Health

DPW – District of Columbia Department of Public Works

DYRS – District of Columbia Department of Youth Rehabilitation Services

FEMS – District of Columbia Fire and Emergency Medical Services Department

FirstNet – First Responders Network

GIS – Geographic Information System

GPS – Global Positioning System

HSEMA – District of Columbia Homeland Security and Emergency Management Agency

ICC – Interoperability Communications Committee

IP – Internet Protocol

MPD – District of Columbia Metropolitan Police Department

LMR – Land Mobile Radio

LPR – License Plate Reader

LTE – Long Term Evolution

MDR – Mobile Data Router

MDT – Mobile Data Terminal

NCIC – National Crime Information Center

NG911 – Next Generation 911

NPSBN – National Public Safety Broadband Network

NTIA – National Telecommunications and Information Administration

OCME – District of Columbia Office of the Chief Medical Examiner

OCTO – District of Columbia Office of the Chief Technology Officer

OUC – District of Columbia Office of Unified Communications

PSAP – Public Safety Answering Point

RAN – Radio Access Network

RoIP – Radio over Internet Protocol

RSRQ – Reference Signal Receive Quality

SIEC – Statewide Interoperability Executive Council

SLIGP – State and Local Implementation Grant Program

SWIC – Statewide Interoperability Coordinator

UCC – Unified Communications Center

public safety communications in the district of columbia ... · 9/30/2016 · firstnet has...

Documents