Missouri FY 10 Interoperable Grant Guideline Definition and Examples of Eligible Procurement

Similar documents
The Benefits of Project 25

Command, Control and Interoperability

Project 25 Mission Critical PTT

3 4 1: 2: SAFECOM : 4: 5: 6: 7: IP

Current Systems. 1 of 6

Communications Interoperability- Current Status

P25 and Interoperability. RadioResource. User Benefits, Cautions and Case Studies. October 2013 MCCmag.com TM

MOTOBRIDGE IP Interoperable Solution

PERSPECTIVE. Jim Downes Chair, Project 25 Technology Interest Group. August 3, Copyright Project 25 Technology Interest Group Slide 1

Wyoming s Statewide Public-Safety Interoperable Radio Communications System WyoLink Frequently Asked Questions (FAQ)

Project 25 Compliance

LMR Encryption Navigating Recent FCC Rule Changes

Radio Technology Overview. January 2011

Report on the Use of Encryption on the Interoperability Channels

FCC Report to Congress: Maintaining Communications Following a Major Disaster

INTEROPERABILITY PLANNING FOR PUBLIC SAFETY

Project 25 Equipment Testing

Federal Partnership for Interoperable Communications

Long Term Evolution (LTE) Next-Generation Public Safety Communications. Fred Scalera

Guide for Short Term Interoperability

Federal Partnership for Interoperable Communications

ATLAS. P25 Systems. LMR communications made simple.

Rulemaking Hearing Rules of the Tennessee Department of Health Bureau of Health Licensure and Regulation Division of Emergency Medical Services

Before the FEDERAL COMMUNICATIONS COMMISSION WASHINGTON, D.C

Project 25 Update for 2015

Public Safety Radio Communications System Update. Presented by Steve Streiffert Assistant Director, IT Solutions May 10, 2011

Resolution Authorizing Expenditure Appropriations to Purchase Radio Equipment and Facilitate Infrastructure R56 Grounding Work

Project 25 with LTE: Mission Critical PTT Interworking Standards in Development

Missouri Statewide Interoperability Network. DNR Park Rangers Conference April 2018

Office of Emergency Communications

Project 25 Wireline Standards Update

National Incident Management System

Public Safety Interoperable Communications (PSIC)

Training that is standardized and supports the effective operations of NIIMS.

Guide for Short Term Interoperability Revised June 24, 2009

Datacasting for Public Safety Access to Enhanced Technology via Public Television

Missouri State Interoperability Executive Committee 700 MHz Interoperable Channel Template

BUTLER COUNTY RADIO RFP RESPONSES TO VENDOR QUESTIONS. Butler County 700 MHz, P25 Public Safety Radio Network Issued July 8, 2016

Pick Me! Choosing the Right Digital PTT Technology for Your Needs

FY 2008 (October 1, 2007 September 30, 2008) NIMS Compliance Objectives and Metrics for Local Governments

VA Tech Plan Blueprint / Sept Page 2 of 54

Interoperable Communication Sustainment

Project 25 Inter-RF Subsystem Interface (ISSI) and Console Subsystem Interface (CSSI) Primer

SERS primary mission was to design, purchase, build and operate a county-wide 800 MHz radio system along with supporting infrastructure and

Saluda County 911 Center Upgrades Console System and Improves Operations

The Professional Consulting Services Communications Consultant E-911. Design Alternatives

NG9-1-1 / LAND MOBILE RADIO & LTE / EMERGENCY NOTIFICATION. Copyright 2014 Cassidian Communications, Inc. All rights reserved.

Optimal Interoperability. H. Scot Smith Manager, Interoperability Solutions Sprint Nextel

NCSL Legislative Summit Improving Emergency Communications

FCC NARROWBANDING MANDATES. White Paper

Pennsylvania STARNet NASCIO Awards Information Communications Technology Innovation Commonwealth of Pennsylvania

PALMETTO 800 History Project Cost

Radio System Replacement Project

Dynamic Dual Mode for ASTRO 25 Systems:

ALMR FREQUENTLY ASKED QUESTIONS

ROUTT COUNTY, COLORADO

VHF/UHF Narrowbanding Information for Public Safety Licensees

Connecting Smartphones and Radios using RoIP and the JPS VIA app

Writing Guide for Standard Operating Procedures

Canada Voice Communications Plan (The Way Forward)

GAO FIRST RESPONDERS. Much Work Remains to Improve Communications Interoperability. Report to Congressional Requesters

FALL 2010 DANIELS ELECTRONICS NEWSLETTER If you are experiencing difficulty viewing this , please go to the Daniels Newsletters Page.

FREQUENTLY ASKED QUESTIONS ABOUT ALLOWABLE USES OF 911 FEES Updated January, 2018

OREGON WIRELESS INTEROPERABILITY NETWORK (OWIN) PROJECT. Conceptual Design for Radio System, Revision 1 (November 30, 2006) (Deliverable 9-D)

Statewide 800 MHz trunked radio system available for all emergency responders (local, State, Federal)

Radio Communications Essentials. Module 9: Narrowbanding Pete Peterson

Mission Critical Voice Communications Use Case Development

Consultation Paper on Public Safety Radio Interoperability Guidelines

Before the FEDERAL COMMUNICATIONS COMMISSION Washington, DC ) ) ) ) ) ) COMMENTS OF THE TELECOMMUNICATIONS INDUSTRY ASSOCIATION

Terminology. 700 MHz: A radio, system or channel that operates within the range of the MHz. These systems may be conventional or trunked.

VAR Generator Operation for Maintaining Network Voltage Schedules

IFERN / IFERN 2 Radio Base Stations for all Wisconsin MABAS Divisions/Counties

Low-Risk Steps to. Transitioning your Jurisdiction to MCPTT using Broadband PTT Interop

Simoco Xd Professional Digital Mobile Radio System. The complete end-to-end DMR solution supporting both Tier II conventional and Tier III trunked

Systems Engineering Approach to First Responder Interoperability

MOTOROLA MOTOTRBO CAPACITY PLUS RADIO SYSTEM DESCRIPTION

Statewide 800 MHz Communications System

EMERGENCY COMMUNICATIONS

Resource Review and Design Recommendations Public Safety Communications System Assessment and Design. Broome County, New York.

VAR Generator Operation for Maintaining Network Voltage Schedules

Challenging Communication Boundaries. RoIP Gateways. Radio over IP for Optimal Analog & Digital Radio Network Performance

ETSI TR V1.2.1 ( )

Technical Requirements for Land Mobile and Fixed Radio Services Operating in the Bands / MHz and / MHz

VAR Generator Operation for Maintaining Network Voltage Schedules

SUBJECT: MARIN EMERGENCY RADIO AUTHORITY (MERA) NEXT GENERATION

Joint System Owners Customer Information Meeting Thursday, December 7, 2017 Environmental Service Building

Eaton County Public Safety Radio System Recommendation

Radio Communications Essentials. Module 5: Mutual Aid Agreements and Common Use Channels Mark Conrey

TECHNOLOGY CHOICES NEIL HORDEN CHIEF CONSULTANT FEDERAL ENGINEERING, INC. August 13, Copyright 2017 by Federal Engineering, Inc.

CONCEPTS TO OPERATIONS, INC.

WAVE 5000 EVERY DEVICE. EVERY NETWORK. EVERY TEAM. CONNECTED LIKE NEVER BEFORE.

Public Safety Communications Commission

Gazette Notice SMSE

Chapter 3 Test. Directions: Write the correct letter on the blank before each question.

ELECTRIAL AND SIGNING MATERIALS STANDARDS VOLUME 3

National Incident Management System

Response to Consultation Paper on Public Safety Radio Interoperability Guidelines Notice NO. SMSE

DCC Trunked Radio System Proposer Questions and Answers, rev 2 September 28, 2011

25 CORE ASTRO FLEXIBLE, SCALABLE CONFIGURATIONS

Narrow-banding What It Means to Public Safety Webinar

Transcription:

Missouri FY 10 Interoperable Grant Guideline Definition and Examples of Eligible Procurement Missouri grant guidelines for interoperable communications equipment are changing for fiscal year 2010. Based on recommendations approved by the Governors Homeland Security Advisory Council (HSAC) in January, 2010 the following recommendations are to be utilized when utilizing grant funding to procure interoperable communications equipment: Mobile radios procured must be upgradeable to operate in the Project 25 trunked mode. The radio can be purchased initially with the ability to operate in the Project 25 trunked mode but at a minimum it must be a model which is capable of being upgraded at some point in the future. The ability for the radio to operate in the project 25 trunked mode is to ensure that agencies purchasing radios will be able to communicate via the State of Missouri s Statewide Interoperable Network (MOSWIN), an important aspect of the State of Missouri s overall interoperable vision. The radio network will provide mobile radio coverage so mobile radios purchased with FY10 grant funding should be capable of operating on the network. Starting in 2010, the federal government is requiring all Project 25 equipment sold (including base stations, repeaters, portable and mobile radios) to comply with Project 25 standards testing and to post the results of the tests, called Standard Declaration of Compliance (SDOC s), of their specific models on the following website https://www.rkb.us/. If the particular model requested does not have a SDOC for that Project 25 model radio posted on the website, it cannot be purchased with grant funding. Contact Stephen Devine, Interoperability Program Manager with the Missouri Department of Public Safety, for further information or with questions on the https://www.rkb.us website or Project 25 SDOC s. Consistent with additional federal guidelines, non-project 25 equipment can be utilized if the acquisition does not inhibit an agencies access to interoperability. In Missouri, being interoperable within the State s interoperable vision has been defined in its Statewide Communications Interoperability Plan (SCIP) as an agency being able to communicate with the Missouri Statewide Interoperability Network, which to achieve as indicated above requires a Project 25 trunked mobile radio (45 watts). Agencies can purchase non-project 25 equipment if they are able to communicate on the statewide network. In FY 10 grant guidelines, agencies wishing to purchase non-project 25 equipment will be required to provide a short narrative as to how they can communicate on the statewide interoperability network. The narrative showing how an agency can access the statewide interoperability network MUST accompany the request to purchase non-project 25 equipment or it will be returned as outside the current grant parameters.

Some examples of what solutions agencies can state their interoperable capabilities resulting from and define their access to the statewide interoperability network, thereby stating their interoperable capabilities and being eligible to acquire non-project 25 equipment, are: An agency can place a Project 25 Trunked Mobile Radio (Control Station) that has access to the statewide interoperability network in a PSAP or other fixed facility. This would make the applicant eligible for non-project 25 portable, base and repeater equipment since they are able to access the statewide interoperability network through their PSAP. An agency can place a Project 25 Trunked Mobile Radio that has access to the statewide interoperability network in a piece of bridging equipment they utilize (ACU-1000 or other bridging device) that allows users to bridge from their internal agency channels to access the P 25 trunked mobile radio and access the statewide network. In most configurations, the trunked radio attached to the bridging device will have to have the talk groups of the mobile radio changed manually so the location of the device and physical access to the radio are important elements of this particular configuration. This would make the applicant eligible for non-project 25 portable, base and repeater equipment since they are able to access the statewide interoperability network through their bridging device. An agency can place a Project 25 Trunked Mobile Radio that has access to the statewide interoperability network on a piece of response equipment (fire truck) to be able to access the statewide network. This would make the applicant eligible for non-project 25 portable, base and repeater equipment since they are able to access the statewide interoperability network through their equipment when deployed. What is important is to note that the request for Non-Project 25 portable radios, base radios and repeaters can be approved only when an agency has stated they can interact with and communicate on the statewide interoperability network. The paragraph that outlines this capability should be the first part of their grant request. The purchase of mobile radios, based on homeland security grant requirements, must adhere to the Governors Homeland Security Advisory Council recommendations that require any mobile radios be able to be upgraded to operate in the Project 25 trunked mode. Appendix A contains the grant language utilize for the FY10 State of Missouri grant guidelines. Should any additional questions arise, contact Missouri Department of Public Safety Interoperability Program Manager Stephen Devine at 573-522- 2382 or stephen.devine@dps.mo.gov

Appendix A Equipment Standards When procuring equipment for communications systems, whether voice or data, a standards based approach must be used to begin migration to multi-jurisdictional and multidisciplinary interoperability. The applicable requirements for land mobile radio (LMR) systems, Voice over IP (VoIP) systems and data-related information sharing systems are described below. Applicants must demonstrate how their procurements will comply with these requirements as applicable. Land Mobile Radio Systems All new digital voice systems must be compliant with the Project 25 (P25) suite of standards. This requirement is intended for government-owned or -leased digital land mobile public safety radio equipment. This requirement does not apply to commercial voice services that offer other types of voice interoperability solutions. To ensure encrypted interoperability, the P25 suite of standards references the use of Advanced Encryption Standard (AES) in the Project 25 Block Encryption Protocol, ANSI/TIA-102.AAD. Entities pursuing encrypted communications capabilities must be compliant with the P25 Block Encryption Protocol. This guidance does not preclude funding for non-p25 equipment when there are compelling reasons for using other solutions. Funding requests by agencies to replace or add radio equipment to an existing non-p25 system (such as procuring new portables for an existing analog system) will be considered if there is an explanation for how such equipment will improve interoperability or support eventual migration to interoperable systems. Absent these compelling reasons, P25 equipment will be required for LMR systems to which the standard s apply. Interoperability, as listed in the above SAFECOM grant guidance, is defined in Missouri by the Missouri Statewide Communications Interoperability Plan (SCIP). The Missouri SCIP identifies the states interoperable vision in the development of a statewide VHF Project 25 Trunked interoperability network. Subsequently, improving interoperability in Missouri is defined by an agency s ability to introduce or enhance access to the Missouri statewide interoperability network with a Mobile Project 25 VHF Trunked Radio. Infrastructure Equipment: Any piece of infrastructure equipment (including but not limited to base stations, receivers, repeaters, etc.) requested to be purchased must have that request accompanied by an Executive Summary that includes an Operation and Maintenance Plan which will show how the requested equipment will be implemented and maintained along with an explanation as to how that equipment is anticipated to operate and contributes to enhancing the agency s degree of interoperability while also enabling connection/access to the Statewide VHF P 25 Radio Interoperability Network. When purchasing Project 25 LMR equipment/systems, grantees will, at a minimum, ensure the vendor has participated in equipment testing consistent with the Project 25 Compliance

Assessment Program (P25 CAP). Where such equipment is covered in the Project 25 Compliance Assessment Program Requirements6 document, it must be tested in accordance with applicable standards and policies of the P25 CAP, and evidence of this testing must be documented through Supplier s Declarations of Compliance and Summary Test Reports that have been posted to http://www.rkb.us. Additionally, when P25 LMR equipment/systems are purchased with a non-standard, proprietary feature/capability and a comparable feature/capability is part of the standard, the P25 LMR equipment/systems must include the standards-based feature/capability. For assistance in determining eligible communications equipment purchases under this section, and in determining when justification material is required, grantees can access web based technical assistance tools at: http://www.pscr.gov/outreach/safecom/grant_guidance/grant_charts.php The OIC Wireless Communications Grant Guidance Tool will also give users access to detailed information that will be helpful in selecting and procuring Project 25 equipment. In addition, this tool offers links to documents available under the P25 CAP. Voice-over-Internet Protocol Systems When purchasing bridging/gateway devices that have a VoIP capability to provide connectivity between LMR systems, those devices must at a minimum, implement either the Bridging Systems Interface (BSI) specification or the P25 Inter RF Sub-System Interface (ISSI) as a part of their VoIP capability. Data-Related Information Sharing Systems Grant funded systems, developmental activities or services related to emergency response information sharing should comply with the OASIS Emergency Data exchange Language (EDXL) suite of data messaging standards. Compliance should include the following OASIS EDXL standards: Common Alerting Protocol (CAP), version 1.1 or latest version Distribution Element (DE), version 1.0 or latest version Hospital AVailability Exchange (HAVE), version 1.0 or latest version Resource Messaging (RM) standards, version 1.0 or latest version More information on each of these standards and its applicability can be found at: http://www.oasis-open.org. This guidance does not preclude funding of non OASIS EDXL-compliant systems when there are compelling reasons for using other solutions. Absent such compelling reasons, the OASIS EDXL standards identified above are the preferred standards. SAFECOM Guidance for Federal Grant Programs Grant funded systems, developmental activities, or services related to emergency response information sharing should also leverage the National Information Exchange Model (NIEM) for data component or element standards. More information on NIEM can be found at: www.niem.gov.

National Information Exchange Model Supporting Technology Evaluation Program Grant funded systems, developmental activities or services related to emergency response information sharing should also comply with the NIMS Supporting Technology Evaluation Program (STEP). The NIMS STEP provides objective evaluations of commercial software and hardware products, and reports on product conformity to standards and NIMS guidelines. Findings from evaluations may be accessed through the Responder Knowledge Base (RKB) website to assist grantees in making purchases. More information on the NIMS STEP can be found at: https://www.nimsstep.or