Law Enforcement Division Federal Reserve Bank of Minneapolis€¦ · Law Enforcement Division 90...

Law Enforcement Division 90 Hennepin Avenue (612) 204-6000 Federal Reserve Bank of Minneapolis Minneapolis, Minnesota 55401-1804 Fax (612) 204-6012

February 10, 2017

Joe Glaccum, SECB OTC Chair

North Memorial Medical Center

4501 68th Avenue N

BROOKLYN CENTER MN 55429

Chair Glaccum,

I represent the Minneapolis Branch of the United States Federal Reserve Law Enforcement Division. We are located in Minneapolis and the Ninth District includes all of Minnesota, plus all or part of several other states as well. We are sworn and commissioned Federal Reserve Law Enforcement Officers.

In 2005, the Federal Reserve Law Enforcement Division (FRLED) entered into a Subscriber Agreement with MESB and later with MN-DOT to access the ARMER system. We were originally authorized to use ten radio IDs for handheld radios. The FRLED uses a MOTO TRBO Capacity Plus system day-to-day operations and we are considered an “occasional user” (Limited Inter-Op) on the ARMER system.

More recently, we added two additional mobile units and were granted system IDs at that time. It was brought to my attention recently that we have ten radios approved by the OTC, but twelve radios were found in PM. I have been working with Jim Stromberg, ARMER Program Manager to correct this situation.

I hereby request the OTC to approve two additional IDs, as well as eight more IDs, for any future expansion.

Our ARMER system administrator is ANCOM Communications. They have also done radio programming for us and ensured me that our subscriber units are complaint with technical standards. I am the authorized contact person from the LED.

The FRLED also has signed Talkgroup Authorization Agreements with the Minneapolis Police, Hennepin County Sheriff’s Office, Metropolitan Airport Police, and the Minnesota State Patrol.

Law Enforcement Division 90 Hennepin Avenue (612) 204-6000 Federal Reserve Bank of Minneapolis Minneapolis, Minnesota 55401-1804 Fax (612) 204-6012

Minneapolis FRLED personnel routinely monitor an ARMER radio 24 hours a day, 7 days a week in our Law Enforcement Communications Center (LECC). We are also participants in the Minneapolis Downtown Improvement District (DID) roll calls.

The Minneapolis FRLED does have activities external to the Minneapolis Bank and uses ARMER radios for those activities, including Executive Protection and Cash Destruction.

The Minneapolis FRLED has one talkgroup currently approved by the OTC and it was approved for statewide access. Our talkgroup gets occasional use to communicate with the Bank when we are out of range of our MOTO TRBO system.

The Minneapolis FRLED also has access to the various inter-operability talkgroups, including L TAC 1-4.

The Minneapolis FRLED conducts initial, new employee radio training, as well as refresher/on-going training. The training covers the topics referenced in SECB State Standard Number 1.11.4. As the ARMER contact person, I have conducted that training here at the Bank.

I request that this item be put on the agenda for the March 14, OTC Meeting.

Very respectfully,

James A. Schnoor

United States Federal Reserve System

Law Enforcement Division

9th District Minneapolis

Office: 612-204-6000

Fax: 612-204-6012

Mr. Troy Tretter

Regional Radio Services Coordinator

Metropolitan Emergency Services Board

2099 University Avenue West

St. Paul, MN 55104

Mr. Tretter,

Please consider this letter a request by Metro Mobility for a change in its participation plan.

Background

Metro Mobility is required under Minnesota Statute 174.30 Operating Standards, Special Transportation

Services (STS) Regulation 8840.5925 to equip all vehicles for two-way voice communications. Metro Mobility

currently is using approximately 364 radio IDs with 6 talk groups active. This number includes consoles, back-

ups, and handhelds in addition to mobile radios.

Change Request

Metro Mobility would like to move all dispatch MCC7100 consoles currently equipping its providers to direct

connection with ARMER via two leased T1s. Doing this would eliminate the need to use the Metropolitan

Council’s enterprise network as a primary link in the dispatch system. The use of the Metropolitan Council’s

enterprise network and the related network translation equipment has proved somewhat problematic in terms

of system reliability.

Impact on ARMER

It is not anticipated that using direct connections to the core will adversely affect Metro Mobility’s airtime use,

nor is it anticipated that this change would materially improve use rates. It is assumed that the elimination of

the council’s enterprise network, network translation equipment, and proxy server will contribute to improved

reliability for Metro Mobility and will probably enhance overall system security.

Thank you

Dana E. Rude

Project Administrator

Metro Mobility, Metropolitan Council

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �� ! � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � " � � � � � � !# $ % $ & $ ' ( ) $ ' * % + $ , - . $ , / + 0 1 , % + ( ' 2 1 - % & + 3 % 1 0 ) 4 - % 1 5 6 1 - 3 & + 7 % + $ , 8 9 8

SECTION 1

SYSTEM DESCRIPTION1.1 OVERVIEW: ; < = > ? @ > A [ P QA F T C D U R \ U V U O < W U ] ^ ; C N ; F A < N D E E < N O < T O D X D A W F U C E B G < O A R E S < T A F T C D E < O ^ D A S _ : ; C U U V U O < W N D W Y G C < U^ C O ; = L ` [ L A D M < N O P Q L ; F U < a A < b R C A < W < E O U _ [ c < A F G G N D E O A D G D X O ; < A F T C D E < O ^ D A S C U F N N D W Y G C U ; < TO ; A D R B ; O ; < R U < D X < G < N O A D E C N U T C U O A C \ R O < T O ; A D R B ; D R O O ; < E < O ^ D A S _ : ; < W F U O < A U C O < < b R C Y W < E O C E N G R T < UF Z W F A O d D E < ` D E O A D G G < A ] ^ ; C N ; C U R U < T O D Y A D N < U U F G G c D C N < N F G G U C E O ; D N ; < U O < AU C O < X D A d D E < j ] Z O _ ` G D R T U C O < X D A d D E < k ] l R G R O ; X D A d D E < Q ] F E T l < O A D C O m F S < U X D A d D E < n _ ? < O A D? D \ C G C O V T C U Y F O N ; ^ C G G \ < N D E E < N O < T O D O ; < e F O < A f U @ T B < ? F U O < A Z C O < o d D E < g p _ d D E < g C U W F T < R Y D XW R G O C Y G U C O ? @ > Z V U O < W C UN R A A < E O G V F O A < G < F U < q _ g Q _? D O D A D G F Z D G R O C D E U a E N _ o ? D O D A D G F p D X X < A U ? < O A D ? D \ C G C O V F E < O ^ D A S A < N D E X C B R A F O C D E D X O ; < C A < r C U O C E B? ` ` q Q I I s q g I I T C U Y F O N ; N D E U D G ? @ > : A R E S < T > F T C D Z V U O < W F UO ; A < D \ < A O Z O A < < O o ? ` ` q Q I I f U p ] u C A U O : A F E U C O @ F U O = A < F o ? ` ` q g I I f U p ] F E T: A F E U C O : < F W e : Z U C O < ^ F U Y F A O D X O ; < D A C B C E F G N D E U D G <T < U C B E ] C O C U ? D O D A D G F f U R E T < A U O F E T C E B O ; < < b R C Y W < E O X A D W O ; C U U C O < ^ F U F G G D N F O < T C E U O < F T O D < C O ; < A O ; <@ F U O F E T s D A e : Z G D N F O C D E _ : ; < u C A U O: A F E U C O @ F U O F E T : A F E U C O : < F W e D \ < A O U Z O A < < O G D N F O C D E F U C O C U N D E X C B R A < T O D T F V _: ; C U ^ C G G D X X < A C W Y A D c < T Y < A X D A W F E N < F E T N F Y F N C O V D X O ; < < r C U O C E B ? ` ` q g I I T C U Y F O N ; N D E U D G F T C Dw D F A T o Z > w p F E T Z O F O < ^ C T < [ Y < A F O C D E U x : < N ; E C N F G ` D W W C O O < < o [ : ` p _ : ; < A < b R C A < T A < U D R A N <F G G D N F O C D E F O O ; < ? F U O < A Z C O < E < < T U O D \ < N D D A T C E F O < T \ < O ^ < < E ? < O A D ? D \ C G C O V F E T ? y l [ : Y A C D A O D< b R C Y W < E O Y A D B A F W W C E B F E T D Y O C W C K F O C D E _1.2 SYSTEM DESIGN: ; < ? ` ` q g I I E < O ^ D A S A < N D E X C B R A F O C D E T < U C B E X D A ? < O A D ? D \ C G C O V N D E U C U O U D X O ^ D h h ? H I I Ih F O < ^ F V F E T Z ^ C O N ; ] D E < X D A < F N ; ? ` ` q g I I T C U Y F O N ; N D E U D G ? @ > H I I ? J K : A R E S < T Z V U O < W C E O < A X F N < O D O ; < e F O < A f U @ T B < ? F U O < A Z C O < _l < O F C G < T C E X D A W F O C D E D E < F N ; D X O ; < ? ` ` q Q I I C E O < A X F N < U C U Y A D c C T < T \ < G D ^ _1.2.1 Trunked System Interface ? D O D A D G F ; F U C E N G R T < T U < A c C N < U F E T O ; < E < N < U U F A V E < O ^ D A S C E B ? @ > H I I ? J K : A R E S < TZ V U O < W _ : ; < N D E U D G < U C O < T < U C B E X D A ? < O A D ? D \ C G C O V C E N G R T ? @ > E < O ^ D A S _ : ; C U T < U C B EA < b R C A < U ? < O A D ? D \ C G C O V O D Y A D c C T < O ^ D : g f U \ < O ^ < < E O ; < T C U Y F O N ; G D N F O C D E U o u C A U O : A F E U C O @ F U O = A < FF E T : A F E U C O : < F W e < U O = A < F p F E T O ; < ? F U O < A Z C O < e = y Z ^ C O N ; _ ? < O A D ? D \ C G C O V C U A < U Y D E U C \ G < X D A^ D A S C E B ^ C O ; ? y l [ : O D W F S < U R A < O ; < : g f U F A < C T < E O C X C < T O ; A D R B ; O ; < U ; F A < T ? C N A D ^ F c < E < O ^ D A S C XA < b R C A < T O D C E O < A X F N < O D O ; < e F O < A f U @ T B < ? F U O < A Z C O < _ = G G O F G S B A D R Y O A F X X C N ^ C G G \ < T < G C c < A < T O D O ; <N D E U D G < U C O < c C F O ; < : g C E O < A X F N < _

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � � �� " � � � � � � ! � � � � � � � ! � � � � � � � � � � �8 9 z ) 4 - % 1 5 6 1 - 3 & + 7 % + $ , # $ % $ & $ ' ( ) $ ' * % + $ , - . $ , / + 0 1 , % + ( ' 2 1 - % & + 3 % 1 0

1.2.2 Sparesy D U Y F A < < b R C Y W < E O ; F U \ < < E C E N G R T < T C E O ; C U Y A D Y D U F G _1.2.3 Power and Heat Requirements: F \ G < g v g U ; D ^ U O V Y C N F G Y D ^ < A N D E U R W Y O C D E X C B R A < U X D A E < ^ Z C O < y < O ^ D A S @ b R C Y W < E O \ F U < T D E R U C E Bg P I i = ` Y D ^ < A U D R A N < _ : F \ G < g v P U ; D ^ U O V Y C N F G O ; < A W F G X C B R A < U X D A E < ^ Z C O < y < O ^ D A S @ b R C Y W < E O _{ | } ~ � � � � � � � � � | � � � � � � � � ~ � � � � � � � � � � � � � � � � � �� ¡ ¢ £ � ¤ � ¤ ¥ � � � � � � � � � � ¦ § � � � ¢ ¨ ¥© ª « ¬ ¬ « ® ¯ ° ± ² ³ ´ ª µ ¶ ¬ · « ¸ ¹ º » ¼ « « ½ ¸ ¾ º » ¼ « « ½{ | } ~ � � � ¿ � � � � � | � � � � � � � � ~ � { � � � � | ~ À � � � � � �� ¦ Á � � ¤ ¢ ¨ Â � � � � � ¡ ¢ £ � ¤ � ¤ ¥ Ã ¢ � Á ¦ Á � � ¤ ¢ ¨ Â � � � � � ¦ § � � � ¢ ¨ ¥ Ã ¢ � Á© ª « ¬ ¬ « ® ¯ ° ± ² ³ ´ ª µ ¶ ¬ · « Ä Å Æ Ç È É Ê Ë ° ¹ Ì Í Ç È É Ê Ë °1.3 SUMMARY? D O D A D G F f U ? ` ` q Q I I l C U Y F O N ; ` D E U D G < D X X < A U ? < O A D ? D \ C G C O V F E R Y T F O < T T < U C B E F G D E B ^ C O ;X G < r C \ C G C O V O D F G G D ^ O ; < C A T C U Y F O N ; < A U O ; < F \ C G C O V O D T D O ; < C A M D \ C E O ; < W D U O < X X C N C < E O ^ F V Y D U U C \ G < _ @ F N ;T C U Y F O N ; Y D U C O C D E N F E \ < N D E X C B R A < T O D A < X G < N O O ; < < r F N O E < < T U D X O ; D U < T C U Y F O N ; < A U ] ^ ; C G < \ < C E B F \ G < O D\ < N ; F E B < T F E T W D T C X C < T ^ ; < E E < < T < T _1.4 METRO MOBILITY BLOCK DIAGRAML G < F U < U < < O ; < X D G G D ^ C E B Y F B < _

INFORMATION TECHNOLOGY DEPARTMENT

400 2nd Street South > St. Cloud, MN 56301-3699 > 320.255.7208 > Fax 320.255.7297 > www.ci.stcloud.mn.us

Date: 3/2/2017 TO: Joe Glaccum – OTC Chair From: Micah Myers - IT Director Subject: St. Cloud Participation Plan Amendment The City of St. Cloud is bringing forth an ARMER participation plan amendment that was recently approved by the Central MN Owners & Operators Committee at their February 2017 meeting. A summary of the amendment is as follows:

• 2 RF Channel addition to the St. Cloud Simulcast • Integrated Voice & Data (IV&D) • Enhanced Data (ED)

The IV&D and ED will be used for GPS location services and Over the Air Programming (OTAP). The Steering Committee has already approved our IV&D/ED project in their November 2016 meeting as a pilot project. During that meeting, the City of St. Cloud agreed to the terms of that pilot project. Thank you for the consideration.

Summary

The City of St. Cloud is asking to amend its participation plan to include two RF channel addition to its simulcast subsite to amount to a total of 12 RF channels. Per the Steering Committee’s approval of a pilot project, the City of St. Cloud also asks to add Integrated Voice & Data (IV&D) to the St. Cloud simulcast that will include capabilities of GPS and Over the Air Programming (OTAP). This project would be executed in 2017 with an anticipated completion date in the 3rd Quarter 2017.

Background

The City of St. Cloud has been exploring for a number of years the capabilities of data usage on the ARMER system. Now, with current funds and an upgrade of the city’s subscribers, there is a desire to make additions and modifications to the infrastructure. These additions would be two RF channel additions to bring the total to 12 RF channels on the St. Cloud simulcast subsite. The modifications would include adding the IV&D, OTAP and GPS specifically to the St. Cloud simulcast.

IV&D

The Integrated Voice & Data is a license that allows an ARMER site to utilize its RF channels for data purposes along with voice. The City of St. Cloud would be employing what Motorola is calling “enhanced” data for location services that is reportedly capable of packaging the data in a more efficient way.

GPS

The GPS capabilities would allow tracking of our subscriber’s geo location, including the portable radios on the hip of our Public Safety entities. This level of GPS location services can be leveraged to allow dispatch operators and even incident commanders the ability to view where personnel are located surrounding an incident scene.

OTAP

Over the Air Programming is a function that will utilize the IV&D licensing to allow differential write subscriber programming. This would be utilized via a Radio Management.

Technical Plan

The City of St. Cloud would achieve these changes with the employment of Motorola and in accordance with MNDOT requirements.

Motorola is providing the necessary infrastructure to utilize IV&D and other features to each master site in Minnesota. In accordance with Motorola and MNDOT, that infrastructure would be connected and properly firewalled so that the connection for data of GPS and OTAP would reside in the Customer Enterprise Network (CEN) and be transported on the city’s fiber optic network to the servers needing to handle that data.

The City of St. Cloud will be responsible for providing the servers to connect to the UNS/IWM to access the GPS data and conduct OTAP jobs.

For discussion regarding capabilities and constraints, see Steering Committee minutes from November 2016.

Capabilities • RF Channels can be preferenced to prefer voice traffic on those channels and only allow data if no other

data or non-preferenced channels are available and no voice traffic is not utilizing that channel. RF channels can also be preferred for data and allow voice if no other voice channels are available.

• GPS data is utilizing Motorola’s Enhanced Data (specific to GPS data) that is an in-bound data only and allows more data from multiple subscribers per channel than their Classic Data product.

• The OTAP feature paired with Motorola APX subscribers allows to send only the changes in the codeplug rather than the whole codeplug including all voice files. This uses the channels more efficiently.

Constraints • Licensing – See Appendix 1 • The UNS/IWM must be located at the zone Master Site. • There is a maximum capacity of 10 total UNS/IWM devices per Master Site. • Connection to the UNS/IWM for any purpose must have a data backhaul path identified. i.e. fiber

connection to your agency or microwave connection to your agency. • Only 1 Radio Management server can be connected per UNS/IWM at the Master Site. • In Provisioning Manager there are agency profiles to be set up to determine cadence rate for how often a

radio is told to send its GPS information. There is a limited number of these agency groups. • To utilize these features of data, the subscriber must be affiliated to the St. Cloud simulcast or any site

that has IV&D activated.

Steering Committee December 2016 Page 1

STATEWIDE EMERGENCY COMMUNICATIONS BOARD

STEERING COMMITTEE

WEDNESDAY, DECEMBER 13, 2016

1 P.M. CHAIR: DAN HARTOG

NORTH MEMORIAL AMBULANCE SERVICE 4501 68TH AVE N

BROOKLYN CENTER, MN 55429

MEETING MINUTES

Attendance Members: Present Member/Alternate Representing Dan Hartog, CHAIR Minnesota Sheriff’s Assn. Joe Glaccum, Vice Chair Minnesota Ambulance Association Mike Slavik/Tom Wolf/Troy Tretter Metropolitan Emergency Services Board Mukhtar Thakur/Tim Lee/Jim Mohn MnDOT OSRC VACANT MN State Patrol VACANT MN.IT Tina Lindquist/Kristen Lahr/Micah Myers Central MN ESB Guests: Jackie Mines, DPS ECN Jim Stromberg, DPS ECN Rick Juth, DPS ECN Carol Salmon, DPS ECN Marcus Bruning, DPS ECN Jim Jarvis, DHS-OEC

CALL TO ORDER

Chair Hartog calls the meeting to order at 1:06 p.m.

APPROVAL OF AGENDA

Jim Stromberg asks to add to the agenda a report from the Education and Outreach Committee. Troy Tretter makes a motion to approve the agenda as amended. Joe Glaccum seconds the motion. The motion carries.

APPROVAL OF PREVIOUS MEETING’S MINUTES


Tretter makes a motion to approve the November minutes. Glaccum seconds the motion. The motion carries.

ACTION ITEMS

STANDARD 2.9.1 TALKGROUP SITE ACCESS AND ROAMING (STROMBERG)

Jim Stromberg introduces the item by reminding the committee that in March of 2016 it formed a workgroup to explore a growing concern about ARMER users roaming onto neighboring subsystems. In response to the workgroup’s report to the committee, the committee asked the workgroup to draft a new standard related to subsystem roaming. Stromberg presents Standard 2.9.1, as submitted in the meeting materials. The workgroup’s report emphasized that quantifying subsystem roaming was in inadequate method to evaluate the concerns, and recommended a qualitative approach. Subsystem roaming concerns should be addressed through an established process that emphasizes communication between the involved parties. It also recommended that a Radio Programming Best Practices Guide be created. The workgroup found that Standards 2.9.0 and 2.11.0 were duplicative. The new standard is created from these two standards. The conflict resolution portions of these standards was put into a different standard which was already approved by the committee and the SECB. He asks for approval of Standard 2.9.1 and, contingent upon approval by the SECB, that Standards 2.9.0 and 2.11.0 be sunsetted. Glaccum adds that the Operation and Technical Committee discussed this and had no objections. Tretter makes a motion to approve Standard 2.9.1 and, contingent upon SECB approval of 2.9.1, that Standards 2.9.0 and 2.11.0 be sunsetted. Glaccum seconds the motion. The motion carries.

DISCUSSION ITEMS

REVIEW OF 2016 SECB INITIATIVES (JACKIE MINES)

Jackie Mines gives a review of the 2016 SECB initiatives. She notes that it is the first time ECN has done a read-out on the strategic initiatives and she is looking for feedback. The review looks at the Goals and Objectives laid out on pages 12-14 on the Strategic Plan. She distributes a report which she reads from and then asks for feedback.

Jim Jarvis says with the SCIP snapshot we look at what was the impact of accomplishing a goal or if not achieved what was the lesson learned. In the plan, there was not a target measurement. The tactic identifies more specifically what you are accomplishing. How you measure some of the things, such as securing funding, is more easily measured but in other instances the target accomplishment is not as specific. Those were some of the questions we had at OEC about the strategic plan. The next question will always be what your next step is. You mentioned the objectives of the staff. That fits into the objectives of the strategic plan or is it the other way around? Does the strategic plan drive their objectives?


Mines responds that it is a little of both. She says she thinks we need to look at the strategies. The strategies are much bigger objectives. There are a number of tactics that have to take place before we can achieve the strategy. The strategy might take five years to complete but some of the tactics might take place over the course of a year or two years. There is only so much the staff can manage at one time and she tries to keep them focused on what are the 2016 tactics for achieving the strategy. When we talk about lessons learned, she can identify those a bit more. How do we measure that success? The strategy won’t be successful if the tactics aren’t accomplished. The strategies are big, for example complete NextGen911, or complete a statewide GIS database so we can implement call routing. Jarvis says he compares the strategy to the goal, the tactics are the implementation steps to accomplish the goal. We measure the goal. Your strategy is the bigger picture. “Let’s improve our capabilities,” what does that mean? Our SCIP group had a problem wrapping around how do we measure it and how do we know we are moving forward and how does OEC incorporate that to the report we are sending up to Congress. He likes identifying the smaller steps toward the goal. The OEC talks about SMART goals. Specific, Measureable Achievable, etc. He likes that the goals were identified and then the smaller steps it will take to get there. Mines says she was thinking about doing an amendment to the section that will list additional tactics that will come next but ECN is not quite ready for that. Glaccum asks if it would work to take the strategies and say if they are green, yellow or red. He says it is hard from this report to determine if we are right on or close. Mines gives the example of the NextGen project. It all hinged on our two contacts and that put everything in yellow but it is a five year strategy so it is still in green. She does not feel that ECN will not meet those objectives but the individual tactics were not met in the timeframes expected. Mines will do the rest of the read-out in January.

Mines adds that everything has been on target for FirstNet and ECN and IDC have been working the workgroups. We put together a lot of data and information for FirstNet and are working with our workgroups to review the technical, operational, and business plan impact. We put together all the information for FirstNet and submitted it last September. Now we need to take a look at that information and divide it up based on the way we think the state plan will come from FirstNet. All the information resides in one or two sections of the state plan template. What we are trying to do is take the information that we have collected so far, put it what we call “the proper lane” and identify whether that item that we said was important to Minnesota is a “shall” or a “should” and have set in our work teams’ minds, if a plan comes in and item one is a “shall”, and the plan comes in without that in it, we know that is a red flag and we will be able to pinpoint that immediately to FirstNet and say this is a red flag for MN. We have told Tim Pierce that we are going to let him know right now what those hot buttons are so he can take that back to their vendor. We are also putting together a business case template for the governor and senior staff and for the board. Here are your three options: Opt-in, opt-out and build your own, opt-out and build your own with a partner. We are working on the body of that. So we are working on two things—the real deep technical stuff is really ferreted out and also making a high level business case. FirstNet’s goal was to make an announcement for who the vendor partner was. One of the vendors that submitted a proposal objected to the outcome and filed a complaint and that is scheduled to be heard in late January. We don’t know how long that will hold things up.

ARMER PARTICIPATION BY FEDERAL ENTITIES (JIM STROMBERG)

Stromberg reports that a federal law enforcement agency contacted him last month about getting onto the ARMER system. He summarizes Standard 1.10.0 which establishes the procedure for entities to apply for or modify ARMER participation. Most entities cleanly fit into the categories. The first and most common is the full participation plan.


That is an entity whose primary voice communications are on the ARMER backbone. Limited participation is an entity whose primary voice communications are integrated with the ARMER system, via patches, audio gateways or other means. Those are the counties that remained on VHF but were patched into the ARMER system until they could migrate over and those numbers are dwindling. The third category is the interoperability participant which is an entity which desires access to the ARMER system via subscriber equipment for the purpose of interoperability and not as the entity’s primary voice communication system, e.g. federal law enforcement or railroad police. In early November, he received a phone call from the IRS Criminal Investigations Unit asking about ARMER participation. He told them that they can use conventional interop channels and patch. Another option is to borrow ARMER cache radios. Another option is to apply for an interop radio plan, where the entity keeps its radio system and has shared channels for interoperability purposes. What was different was that the IRS said that they want to use ARMER as the primary communications tool and have their own talkgroups. They have agents in Metro, Rochester and Duluth and out of Minnesota but responsible for covering Minnesota. They wanted to get on ARMER as full participants and requested 70 mobile and 70 portable I.D.s. Stromberg explained that we don’t have any federal agencies that are primarily on ARMER. This falls outside of our normal operating procedures and recommended the interoperability plan. Stromberg says he found that some federal entities do have ARMER talkgroups but he didn’t understand why. He researched the ECN files and talked with MnDOT to research files there. He hands out a report to the committee. There are interoperability and limited participation plans and subscriber agreements with MnDOT, limited and interoperability. Both are engaged with over a dozen federal agencies and 40 talkgroups assigned.

He thought the request by the IRS was an honest one he suspects that they may request to make an approach to have a full participation plan on ARMER. As far as he can tell, the SECB has never approved a federal agency to use ARMER as a primary land mobile radio. We will likely be faced with this question and should be prepared to respond. As we begin the discussion, he reminds the committee that ARMER is funded through trunked highway and 911 funds and we need to be sure that we don’t do anything to jeopardize the funding. Servicing 911 responders should be our priority. He adds that federal law enforcement and federal entities are also serving Minnesotans as public safety and law enforcements. Rick Juth adds that he had a lengthy conversation with the special agent. They have an existing VHF system that costs 50,000 annually to support. They are interested in utilizing the ARMER system to alleviate the annual cost. Stromberg responds that the question transcends one particular entity. He thinks there have been inconsistencies to how federal agencies have been approved. He gives the example of the CP Rail having recently been approved for a limited plan. Hartog says on the local level we would give a cache radio and just-in-time training. Where is the request coming from? Who would we be dealing with? Juth thinks it is a lot like the other federal agencies. Local agents based in Minnesota become aware of the ARMER radio system and being able to communicate across the state. He thinks it was an agent that had some aptitude and interest in improving communications for staff across Minnesota.

Mines asks is there a reason some are interop and some are limited and some are unknown. Stromberg says the unknown is where we don’t have a record in our files. MnDOT told him that they have a subscriber agreement with the VA and it has nine talkgroups.


Tretter says the MESB has subscriber agreements with the VA, ATF, FBI, 34th Airforce Reserve, Federal Reserve Bank, and TSA. Discussion about federal agencies using state systems for coverage and about funding for maintenance, etc. What is the equitable way? Discussion to look at the report from MnDOT on the federal agency’s usage. Agreement to discuss further in January. Stromberg asks to move the education and outreach group to a higher priority at the next meeting.

Glaccum makes a motion to adjourn Tretter seconds the motion. The meeting adjourns at 3:00 p.m.

Allied Radio Matrix for Emergency Response (ARMER) Standards, Protocols, Procedures

Document Section 1 Management of System Status: Approved State Standard Number 1.08.1

Standard Title Change Management Date Established 09/22/2016

SECB Approval: 09/22/2016 Replaces Document Dated 1.08.0 (04/28/2011) and 1.05.2 (04/28/2011)

Date Revised n/a 1. Purpose or Objective This standard sets forth the process for considering operational and technical changes to the ARMER backbone. This process should ensure that change requests are managed, vetted, timed to correspond with budgets, and efficiently implemented. 2. Technical Background Capabilities This standard relates to future changes to the ARMER backbone but, in and of itself, is not a technical standard. Constraints The ARMER backbone is defined by Minnesota State Statue 403.21, subd. 9 and its definition limits the scope of this standard. The statute reads:

"System backbone" or "backbone" means a public safety radio communication system that consists of a shared, trunked, communication, and interoperability infrastructure network, including, but not limited to, radio towers and associated structures and equipment, the elements of which are identified in the region wide public safety radio communication system plan and the statewide radio communication plan under section 403.36.

3. Operational Context The Statewide Emergency Communications Board (SECB) is responsible for:

• Ensuring that ARMER maximizes interoperability • Establishing and enforcing performance and technical standards for ARMER • Establishing and enforcing priorities or protocols that facilitate uniformity

The SECB adopts ARMER Standards, Protocols, and Procedures to achieve these goals. Changes to the ARMER system are sometimes necessary and those changes must receive due consideration for economic impacts, operational impacts, and other issues that may compromise the integrity and use of the system. 4. Recommended Protocol/ Standard Changes that have one or more of the following effects on the ARMER backbone or impacting more than one emergency communication regions are subject to the procedures prescribed in this Standard:

• Changes affecting the majority of users • Changes mandating the placement of resources in communications equipment • Changes requiring updated user training • Changes requiring reprogramming of console and/or subscriber equipment • Changes resulting in costs beyond routine maintenance costs

5. Recommended Procedure Individuals or entities with a change suggestion that they believe may be subject to this standard should submit their suggestion to the Operations and Technical Committee (OTC) of the SECB. Items brought directly to the SECB or to other committees of the SECB that are subject to this standard will be directed to the OTC. Items may be brought to the OTC at any regular meeting. After receiving a request to change the ARMER system, the OTC will determine if the request is subject to this standard. If the OTC determines that the suggestion is subject to the terms of this standard, the OTC will ask the requestor to bring their request to specific entities for feedback and/or formal approval. The reviews shall scrutinize the change proposal by identifying pitfalls, considering variables, and identify alternatives. The OTC may establish a workgroup to facilitate this process before making a final recommendation to the SECB. The OTC shall first assign the requestor to consult the Minnesota Department of Transportation (MnDOT) for technical review and the Emergency Communication Networks (ECN) for an operational and financial review of the request. The requestor may consult with MnDOT and ECN prior bringing the request to the OTC and the input of MnDOT and ECN may be provided when the request is first introduced. Upon receipt of comment from MnDOT and ECN, the OTC will assign the requestor to consult the SECB’s Finance and Steering Committees of the SECB and the Emergency Communication Boards of each potentially impacted region. The OTC may also require the requestor to consult other committees or workgroups of the SECB or any other entity the OTC deems necessary. The OTC may consider and grant provisional authority, subject to SECB approval, for portions or the entire change request to be enacted. Temporary authority will allow for prompt implementation and may provide data about the proposal to assist with a permanent decision. The requesting entity will consult each of the entities identified by the OTC about their change request and follow through with those entities as directed. The requesting entity may modify their original request based on new information or suggestions received. The requesting entity should provide a status update to the OTC within six months and every three months afterward. Upon return to the OTC, the requesting entity should provide a report detailing their follow up. Modifications to the original request may be offered. Supporting materials such as meeting minutes or letters of approval should be submitted at this time. Relevant parties should be present for testimony. The OTC may then commence deliberations about the request, resulting in a recommendation to the SECB. Approved requests will be forwarded to the SECB for final review and consideration. Requesting entities may appeal decisions by the means provided in State Standard 7.3.0. Change requests approved by the SECB will be jointly managed by MnDOT and ECN. Generally, MnDOT will manage technical items and ECN will manage operational items. Concerns raised but not fully satisfied during the process should be considered as the change is implemented. ECN will be responsible for tracking requests subject to this standard. The following points related to timing should be followed during the implementation of this standard:

• Change suggestions may be submitted to the OTC at any time and this standard may be applied at any time.

• The process established in this standard should be expected to take at least six months so change suggestions subject to this standard should be submitted at least six months prior to consideration.

Change Management State 1.08.1 2

• Approved changes involving reprogramming of consoles or user equipment may be held up to two years so that multiple changes may be consolidated into one reprogramming and to allow for funding of the proposed changes.

• The monthly ECN report to the OTC will include a timeline detailing the approval and implementation of changes subject to this standard.

A timeline should be followed to ensure adequate timing to prepare and request funding. In the below table, Change Management matters follow a four-year timing cycle and letters represent years:

• Year AAAA: 2016, 2020, 2024, … • Year BBBB: 2017, 2021, 2025, … • Year CCCC: 2018, 2022, 2026, … • Year DDDD: 2019, 2023, 2027, …

January 1, AAAA

If allowing six months for this process, this is the last day to submit changes subject to the Change Management standard to the OTC for consideration in the CCCC/DDDD Minnesota budget.

July 1, AAAA

Deadline for the SECB to approve requests subject and for ECN to know financial needs to be considered for the CCCC/DDDD Minnesota Budget.

July 1, AAAA to January 1, BBBB ECN to obtain Governor’s approval of ECN budget and to prepare budget request for state legislature.

January 1, BBBB to May 1, BBBB ECN to present budget request to legislature. June 1, BBBB State legislature approves budgets. July 1, BBBB to June 30, CCCC Fiscal Year CCCC of CCCC/DDDD budget.

July 1, CCCC to June 30, DDDD Fiscal Year DDDD of CCCC/DDDD budget.

When the requirements of this standard cannot be met by an entity, the entity must apply for a waiver and that waiver must be considered by the OTC. 6. Management The OTC with administrative support from ECN is responsible for supervising and managing this process.

Change Management State 1.08.1 3

DATE: March 6, 2017

TO: SECB Operations and Technical Committee (OTC)

FROM: Cathy Anderson, Standards & Training Coordinator

RE: Standards / Best Practice Guide for consideration

The Standards workgroup is moving the following Standards and one Best Practice Guide forward for approval consideration.

1. 1.5.0 – STANDARDS OF STANDARDS: THE DEVELOPMENT AND MANAGEMENT OF REGIONAL STANDARDS

Most changes in this standard are changing RRB to ECB/ESB.

Consensus among the group was that they like consistency in the numbering process.

Removed part of first paragraph and last paragraph under #3 as it was determined they are not necessary.

#5 - Added that Regions shall post their own standards on their website.

#6 - changed oversight to Standards & Training Coordinator.

2. 1.5.3 – VARIANCES AND WAIVERS Changed policies to protocols (under #3 and #4) to remain consistent with verbiage on the standards. #5 first line changed from SECB to appropriate committee, as requests usually go straight to committee. #5 after first set of bullets – added paragraph for accountability that requestor attend committee meetings to answer questions. Left method of meeting attendance open intentionally so they don’t necessarily have to attend in person.

#5 paragraph under last set of bullets – changed SECB to appropriate committee. #5 next paragraph – changed SECB to SECB or appropriate committee and added agency designee in two spots. #5 next paragraph – System Administrator in place of Manager for consistency among the standards.

3. 4.6.0 – EQUIPMENT CONFIGURATION INFORMATION Many changes are minor for verbiage. #3 paragraph 2 – removed documentation to be maintained at each site. Not always the case/not practical. #5 – removed second bullet – all kept electronically. Also deemed security risk to keep hard copies.

4. 2.5.0 – Radio ID and Talkgroup Allocations

#2, paragraph 3 – question was asked if number had increased from 65,534. Per John A., this is still a valid range for talkgroups, with a quantity max of 16K.

#2, paragraph 4 – removed due to no GE consoles anymore.

#3, paragraph 1 – per John A, other regions do not follow the last entry. They have a large block mapped to each zone controller and the agencies are mapped out of those blocks, depending on their location in the state.

#4, paragraph 1 – removed three years because it can exceed the 3-year timeline but still be within the allowed number.

#5 – no longer believed this section is needed.

5. 1.4.2 – Maintenance of Alias List

#2, paragraph 1 – changed Managers to Administrators to be consistent with other standards.

#3 – added console ID’s and removed last sentence. Some have less than two, and it is felt there should not be contention over an alias. If there is, it goes to OTC.

6. 3.12.0 – Talkgroup and Multigroup Ownership Changed Managers to Administrators under #1 and 4 to be consistent with other standards. #4/Shared, paragraph 3 - added System Administrator so there is accountability/awareness (i.e., so two LE agencies cannot just give another agency permission). Changed RRB to ESB/ECB.

7. 2.7.0 – Use of Shared Talkgroups

Still valid – one minor change on page two – added Public to Works.

Standard of Standards: The Development and Management of Regional Standards State Standard 1.5.0 SRB Approval 10/23/2008 1


Document Section 1 Management of System Status: Complete State Standard Number 1.5.0 Standard Title Standard of Standards: The

Development and Management of Regional Standards

Date Established 09/29/2008 SECB Approval: 10/23/2008 Replaces Document Dated 09/29/2008 Date Revised 02/13/2017

1. Purpose or Objective The purpose of this standard is to define the method by which all Regional Emergency Communications Boards (ECBs)/Emergency Services Boards (ESBs) will prepare, implement, and maintain regional standards. Adherence to this policy will maintain consistency among Statewide Emergency Communications Board (SECB) and Regional ECB/ESB standards. 2. Technical Background Capabilities Emergency Communications Boards/Emergency Services Boards are able to develop standards for the governance of their regional systems. The standards developed by ECB/ESBs cannot be in conflict with an SECB standard. Constraints The Minnesota Department of Public Safety (DPS), Division of Emergency Communication Networks (DECN), will assign a number to the standard based on its purpose. The number assigned will correspond with similar standards already developed by the SECB, an ECB/ESB, or the next available number within the applicable chapter. The Regional Standards should relate to:

• Management of System • Configuration and Allocation • Interoperability Standards • Maintenance • System Access by Non-Governmental Organizations (NGOs) • Board Financial Policies and Procedures • Compliance and Conflict Resolution


3. Operational Context The SECB is responsible for developing standards for all items listed above. Regional standards shall follow the naming and numbering conventions as approved and published by the SECB. While developing a regional standard, a Regional ECB/ESB may set more stringent criteria than a State Standard; however, an ECB/ESB may not set less stringent criteria. 4. Recommended Protocol/ Standard When developing a Regional standard, each ECB/ESB should determine if an existing SECB standard is substantially similar to the standard the Region is considering to develop. If a substantially similar State standard exists, the ECB/ESB shall adopt the State standard number for their Regional standard number. The need for a Regional standard could arise when no published statewide standard relates directly to a Region’s proposed standard. 5. Recommended Procedure:

1. The Regional ECB/ESB will access the State Standard Template on the ECN website under ARMER and Standards.

2. The Regional ECB/ESB will determine if a substantially similar state standard exists by checking the ECN website under ARMER and Standards.

3. The Regional ECB/ESB will contact the Standards and Training Coordinator at DECN to have a number assigned.

4. The Regional ECB/ESB shall draft their standard following the standardized template and will include the name for the new standard.

5. The drafted standard will be brought before the appropriate Regional ECB/ESB for approval. . Regionally approved standards shall be posted on the appropriate Regional website.

6. Management: The DECN Standards and Training Coordinator is responsible for oversight of this standard.



Document Section 1 Management of System Status: Complete State Standard Number 1.5.0 Standard Title Standard of Standards: The

Development and Management of Regional Standards

Date Established 09/29/2008 SERB Approval: 10/23/2008 Replaces Document Dated 09/29/2008 Date Revised 02/13/2017

1. Purpose or Objective The purpose of this standard is to define the method by which all Regional Emergency Communications Boards (ECBs)/Emergency Services Boards (ESBs) Radio Boards (RRBs) will prepare, implement, and maintain regional standards. Adherence to this policy will maintain consistency among Statewide Emergency Communications Radio Board (SECRB) and Regional ECB/ESB Radio Board (RRB) standards. 2. Technical Background Capabilities Emergency Communications Boards/Emergency Services Regional Radio Boards are able to develop standards for the governance of their regional systems. The standards developed by ECB/ESBs Regional Radio Boards cannot be in conflict with an SECB Statewide Radio Board standard. Constraints The Minnesota Department of Public Safety (DPS), Division of Emergency Communication Networks (DECN), will assign a number to the standard based on its purpose. The number assigned will correspond with similar standards already developed by the SECBtatewide Radio Board, an ECB/ESB Regional Radio Board, or the next available number within the applicable chapter. The Regional Standards should relate to:

• Management of System • Configuration and Allocation • Interoperability Standards • Maintenance • System Access by Non-Governmental Organizations (NGOs) • Board Financial Policies and Procedures • Compliance and Conflict Resolution


3. Operational Context The SECBStatewide Radio Board is responsible for developing standards for all items listed above. As ARMER standards have been developed in greater Minnesota, the Statewide Radio Board recognized that each region had its own standard numbering method, which led to some confusion, when a metro area and central Minnesota standard with the same number were completely different policies. Regional standards shall follow the naming and numbering conventions as approved and published by the SECBtatewide Radio Board. While developing a regional standard, a Regional ECB/ESB Radio Board may set more stringent criteria than a State Standard; however, an ECB/ESB Regional Radio Board may not set less stringent criteria. The Statewide Radio Board Operations and Technical Committee (OTC), at their discretion, may request a copy of the regional standard for review to ensure there is no conflict or concern with existing standards. 4. Recommended Protocol/ Standard When developing a Regional standard, each ECB/ESB Regional Radio Board should determine if an existing SECBtatewide Radio Board standard is substantially similar to the standard the Region is considering to develop. If a substantially similar State standard exists, the ECB/ESBRegional Radio Board shall adopt the State standard number for their Regional standard number. The need for a Regional standard wcould arise when no published statewide standard relates directly to a Region’s proposed standard. 5. Recommended Procedure:

1. The Regional ECB/ESB Radio board will access the ARMER State Standards Procedural Template on the ECN website under ARMER and Standards. , located at www.srb.state.mn.us.

2. The Regional ECB/ESB Radio Board will determine if a substantially similar state standard exists by checking the ECN website under ARMER and Standards. Statewide Radio board standards at www.srb.state.mn.us.

3. The Regional ECB/ESBRadio Board will will contact DPS, the Standards and Training Coordinator at DECN to have a number assigned.

4. The Regional ECB/ESB Radio Board shall draft their standard following the standardized template and will include the name for the new standard.

5. The drafted standard will be brought before the appropriate Regional ECB/ESB for approval. Radio Board for approval. Regionally approved standards shall be posted on the appropriate Regional website. DPS will be notified and kept apprised of the Regional Radio Board action of the standard.

6. Management:


The DECN Standards and Training Coordinator is responsible for oversight of this standard. Department of Public Safety, Division of Emergency Communication Networks, manages the Statewide Radio Board standards and will be responsible for the numbering of all Regional standards. To request a number and to report the status of a Regional standard, please contact the Statewide Interoperability Coordinator (SWIC) through the DECN.

Variances and Waivers State Standard 1.5.3 SRB Approval 8/22/2013

1


Document Section 1 Management of System Status: Complete State Standard Number 1.5.3 Standard Title Variances and Waivers Date Established 03/19/2001 SECB Approval: 08/22/2013 Replaces Document Dated 08/06/2013 Date Revised 02/27/2017

1. Purpose or Objective The purpose of this standard is to set forth the process by which variances or waivers to ARMER standards, protocols, and procedures will be granted to a requesting agency.

• Variance is defined as an allowed divergence from full adherence to an adopted standard, protocol, or procedure.

• Waiver is defined as a complete release from an adopted standard, protocol, or procedure.

2. Technical Background Capabilities Constraints

3. Operational Context The Statewide Emergency Communications Board (SECB) is charged with setting standards and determining protocols and procedures for the smoothest possible operations between and among the users of ARMER. . These standards, protocols, and procedures have been set forth by teams consisting of radio users and managers to maximize service to the citizens of the state of Minnesota and minimize any potential negative consequences. Therefore, variances and waivers must not compromise the integrity of the ARMER system or any of its participants. 4. Recommended Protocol/ Standard Each request for variance or waiver from the adopted standards, protocols, and procedures must be made in writing to the SECB via the appropriate subject-matter committee. 5. Recommended Procedure A written request for the variance and/or waiver must be sent to the appropriate subject-matter committee and shall include:

• A full description of the desired variance or waiver, including section and sub-section references.


2

• The reason for the variance or waiver (including the potential consequences if the request is not approved).

• A preliminary assessment on the other regional system users and an estimate of any associated costs.

An agency designee seeking a variance or waiver must attend all appropriate committee meetings, with the support of their Local System Administrator, to be available for questions regarding their request.

Each variance or waiver shall be reviewed by the appropriate subject matter committee prior to consideration by the SECB:

• Requests that are technical in nature shall be reviewed by the Operations and Technical Committee (OTC).

• Requests that are operational in nature shall be reviewed by the Interoperability Committee (IOC).

• Other Committees as Appropriate When reviewing requests, the committee shall consider:

• Technical impact to current and future system performance, including which system or subsystem will be or may be affected.

• Operational capacity impact to current and future system performance, including which system or local system will be or may be affected.

• The degree of conformance with SECB plan and standards. • Cost impact to the SECB and current participants. • Potential alternative solutions.

The appropriate committee will advise affected agencies of all requests, along with potential impact and invite their comments.

The SECB and/or the appropriate committee may approve, disapprove, or modify the request. The SECB or appropriate committee will notify the agency designee of their decision. If necessary, the agency designee will notify all affected parties of the decision. The Chairman of the SECB, or his or her designee, in consultation with the affected System Administrator, may approve a temporary variance or waiver until the official process is completed. Emergency deviations from the standards must be communicated to all affected parties. If appropriate, the SECB will set forth operational and/or financial responsibility and notify all affected parties. 6. Management The Chairman of the SECB, or his or her designee, will manage this process.


1


Document Section 1 Management of System Status: Complete State Standard Number 1.5.3 Standard Title Variances and Waivers Date Established 03/19/2001 SECRB Approval:

08/22/2013 Replaces Document Dated 02/17/200508/06/2013 Date Revised 08/06/201302/27/2017

1. Purpose or Objective The purpose of this standard is to set forth the process by which variances or waivers to ARMER standards, protocols, and procedures will be granted to a requesting agency.

• Variance is defined as an allowed divergence from full adherence to an adopted standard, protocol, or procedure.

• Waiver is defined as a complete release from an adopted standard, protocol, or procedure.

2. Technical Background Capabilities Constraints

3. Operational Context The Statewide Emergency Communications Board (SECB) is charged with setting standards and determining protocols and procedures for the smoothest possible operations between and among the users of ARMER. the Allied Radio Matrix for Emergency Response (ARMER). These standards, protocolsolicies, and procedures have been set forth by teams consisting of radio users and managers to maximize service to the citizens of the state of Minnesota and minimize any potential negative consequences. Therefore, variances and waivers must not compromise the integrity of the ARMER system or any of its participants. 4. Recommended Protocol/ Standard Each request for variance or waiver from the adopted standards, protocolsolicies, and procedures must be made in writing to the SECBtatewide Emergency Communications Board via the appropriate subject-matter committee. 5. Recommended Procedure A written request for the variance and/or waiver must be sent to the appropriate subject-matter committee SECB and shall include:

• A full description of the desired variance or waiver, including section and sub-section references.


2

• The reason for the variance or waiver (including the potential consequences if the request is not approved).

• A preliminary assessment on the other regional system users and an estimate of any associated costs.

An agency designee seeking a variance or waiver must attend all appropriate committee meetings, with the support of their Local System Administrator, to be available for questions regarding their request.

Each variance or waiver shall be reviewed by the appropriate subject matter committee prior to consideration by the SECB:

• Requests that are technical in nature shall be reviewed by the Operations and Technical Committee (OTC).

• Requests that are operational in nature shall be reviewed by the Interoperability Committee (IOC).

• Other Committees as Appropriate When reviewing requests, the committee shall consider:

• Technical impact to current and future system performance, including which system or subsystem will be or may be affected.

• Operational capacity impact to current and future system performance, including which system or local system will be or may be affected.

• The degree of conformance with SECB plan and standards. • Cost impact to the SECB and current participants. • Potential alternative solutions.

The appropriate committee SECB will advise all affected agencies of all requests, along with potential impact and invite their comments.

The SECB and/or the appropriate committee may approve, disapprove, or modify the request. The SECBtatewide Emergency Communications Board or appropriate committee will notify the agency designee all affected parties of their decision. If necessary, the agency designee will notify all affected parties of the decision. The Chairman of the SECB, or his or her designee, in consultation with the affected System AdministratorManager, may approve a temporary variance or waiver until the official process is completed. Emergency deviations from the standards must be communicated to all affected parties. If appropriate, approved or modified, the SECBtatewide Emergency Communications Board will set forth operational and/or financial responsibility as appropriate and notify all affected parties. 6. Management The Chairman of the SECB, or his or her designee, will manage this process.

Equipment Configuration 1 Standard 4.6.0 SRB Approval 9/1/2005

Allied Radio Matrix for Emergency Response (ARMER)

Standards, Protocols, Procedures

Document Section 4 Maintenance Status: Complete State Standard Number 4.6.0 Standard Title Equipment Configuration

Information Date Established 02/20/2001 SECB Approval: 9/1/2005 Replaces Document Dated 05/10/2005 Date Revised 02/27/2017

1. Purpose or Objective The purpose of this standard is to outline the procedure for documenting system and subsystem equipment configuration, consoles, and the secure distribution of system configuration information to the System Administrators and technical support staff. This also classifies equipment configuration as “Security Information” and “General Non-Public Data,” pursuant to Minn. Stats. §13.37, Subd. 1a. 2. Technical Background Capabilities Current configuration documentation of equipment hardware, firmware, circuit routes, and software will greatly facilitate: • Troubleshooting of system and subsystem and equipment problems. • Reloading of a configuration into a piece of equipment that has just been replaced or has

had its configuration corrupted or lost. • Allowing staff to support equipment they have not been directly involved with, even if they

are familiar with the model of the equipment but not the current configuration. • Planning simplified configuration upgrades and changes by knowing the current

configuration. • Overall maintenance at a higher level for system users. Constraints Equipment configuration information should be made available to support staff that has a need for the information; it shall not be released to the general public. It will require staff time to maintain current configuration documentation, distribute the information, and maintain backup archives.


3. Operational Context System and Subsystem: System equipment providers will provide infrastructure as-built equipment configuration documentation as part of the system documentation. After the acceptance of the system, it shall become the “Owning” agency’s responsibility to maintain the equipment configuration information and to keep the information current. Current copies of all as-built equipment configuration documentation will be maintained by the System Administrators. The System Administrators will be responsible for maintaining configuration information of the system and subsystem equipment they are responsible for. The Statewide System Administrator shall be responsible for ensuring the accuracy of all as-built data related to the infrastructure equipment. Any changes or alterations that come to the knowledge of a Local System Administrator will be immediately forwarded to the Statewide System Administrator for entry into the records. The Statewide System Administrator will then distribute the updated information to the other Local System Administrators. Console: The Statewide System Administrator shall be responsible for backing up the console configuration files located on the individual zone elite servers. The backups will be done on a regular periodic basis. System Administrators can request additional backups if large volumes of changes have been made. The archive copies shall be stored as defined in the “Software Location” section of the standards manual. The System Administrators will be responsible for maintaining the configuration information of the console equipment they are responsible for. Portables and Mobiles: It shall be the individual subscribing agency/contracted provider’s responsibility to manage their mobile and portable radio fleet information, including such details as radio manufacturer, model, firmware, and flashcode. 4. Recommended Protocol/ Standard It shall be the intent to have a central electronic storage resource for the system equipment configuration information, which shall be accessible by the System Administrators. The details are at the discretion of the Statewide System Administrator. 5. Recommended Procedure Equipment vendors will provide as-built equipment configuration documentation as part of the system documentation.


The System Administrators will be responsible for managing the configuration information, including: • Maintaining current soft copies of the information and protecting the data from loss. • Updating the configuration information as changes are made within the system. • Informing the responsible System Administrators of configuration issues and errors. The disclosure of the equipment configuration information and other related system information would substantially jeopardize the security of the system against tampering, sabotage, unauthorized use, jamming, hacking, unauthorized access to the contents of confidential voice, and data communications, etc. Therefore, the system configuration information shall be classified as “Security Information” and “Non-Public Data”. 6. Management The System Administrators are responsible for maintaining and keeping the equipment configuration information current.


Formatted: Font: Times New Roman, Font color: Gray-50%

Formatted: Font: Cambria, 12 pt, Font color: Auto





Document Section 4: 4 - Maintenance Status: Complete State Standard NumberSub-Section:

State 4.6.0

Procedure Title:Standard Title

Equipment Configuration Information

Date Established: 02/20/2001 SECRB Approval: 9/1/2005 Replaces Document Dated: n/a 05/10/2005 Date Revised: 5/10/05 02/27/2017

1. Purpose or Objective The purpose of this standard is tTo outline the purpose and procedure for the documentingation of system and subsystem equipment configuration, consoles, and the secure distribution of the system configuration information to the System AdministratorsManagers and technical support staff. This also classifies equipment configuration as “Security Information” and “General Non-Public Data,” pursuant to Minn. Stats. §13.37, Subd. 1a. 2. Technical Background: Capabilities Current configuration documentation of equipment hardware, firmware, circuit routes, and software will greatly facilitate: • Troubleshooting of system and subsystem and equipment problems. • Reloading of a configuration into a piece of equipment that has just been replaced or has

had its configuration corrupted or lost. • AWill allowing staff to support equipment they have not been directly involved with, even

ifwhere they staff isare familiar with the model of the equipment, but not the current configuration.

• Planning simplified configuration upgrades and changes is easier by knowingwhen the current configuration is known..

• Overall maintenance at a will maintain a higher lLevel of Service for system the users of the system.

Constraints Equipment configuration information should be made available to the support staff that has a need for the information in the performance of their duties; it shall not be released to the general public.






It will require staff time to maintain current configuration documentation, distribute the information, and maintain backup archives. 3. Operational Context: System and Subsystem: System equipment providers will provide infrastructure as-built equipment configuration as-built documentation as part of the system documentation. After the acceptance of the system, it shall become the “Owning” agency’sies responsibility to maintain the equipment configuration information and to keep the information current. Current copies of all as-built equipment configuration documentation will be maintained at each site, for the equipment located at the site, and at the offices of by the the System Administrators. The System Administrators will be responsible for maintaining the configuration information of the system and subsystem equipment that they are responsible for. The Statewide System Administrator shall be responsible for ensassuring the accuracy of all as-built data related to the infrastructure equipment. Any changes or alterations that come to the knowledge of a Local one of the System Administrators will be immediately forwarded to the Statewide System Administrator for entry into the records. The Statewide System Administrator will then distribute the updated information to the other Local System Administrators. Console: The Statewide System Administrator shall be responsible for backing up the console configuration files located on the individual zone elite servers. The backups will be done on a regular periodic basis. System Administrators can request additional backups to be made if large volumes of changes have been made. The archive copies shall be stored as defined in the “Software Location” section of the standards manual. The System Administrators will be responsible for maintaining the configuration information of the console equipment that they are responsible for. Portables and Mobiles: It shall be the individual subscribing agency/contracted provider’s responsibility to manage their mobile and portable radio fleet information, including such details as radio manufacturer, model, firmware, and flashcode. 4. Recommended Protocol/ Standard:






It shall be the intent to have a central electronic storage resource for the system equipment configuration information, which shall be accessible by the System Administrators. The details are at the discretion of the Statewide System Administrator. 5. Recommended Procedure: Equipment vendors will provide as-built equipment configuration as-built documentation as part of the system documentation. The System Administrators will be responsible for managing the configuration information, including: • Maintaining current soft copies of the information and protecting the data from loss. • Maintaining current hard copies of the configuration of the equipment at the equipment

locations. • Updating the configuration information as changes are made within the system. • Informing the responsible System Administrators of configuration issues and errors. The disclosure of the equipment configuration information and other related system information would substantially jeopardize the security of the system against tampering, sabotage, unauthorized use, jamming, hacking, unauthorized access to the contents of confidential voice, and data communications, etc. Therefore, the system configuration information shall be classified as “Security Information” and “Non-Public Data”. 6. Management The System Administrators are responsible for maintaining and keeping the equipment configuration information current.

Radio ID and Talkgroup Allocation 1 State Standard 2.5.0 SECB Approval 10/22/2009



Document Section2 Configuration and Allocation Status: Complete State Standard Number State 2.5.0 Standard Title Radio ID and Talkgroup

Allocation Date Established 1/19/2001 SECB Approval: 10/22/2009 Replaces Document Dated 10/01/2009 Date Revised 02/27/2017

1. Purpose or Objective The purpose of allocating talkgroup ID ranges and radio ID ranges for individual agencies is to help manage their pool of IDs as talkgroups, radios, or console positions are configured. This will simplify the management of IDs and provide an easier indication of what IDs belong to what agency in the event that a radio user alias is not available. 2. Technical Background Radio IDs must be in the range of 1 to 16,777,211. It is recommended that IDs above 1,000,000 be reserved for future packet data use, although this recommendation isn't enforced via the user interface. These IDs will be the same that users enter when doing private calls or call alert pages. Also, the IDs picked at this step will be the same as the display on subscriber radios if the "ID Display" feature is purchased and enabled. These IDs will also be displayed at the console if the console alias feature is not used. Talkgroups must be in the range of 1 to 65,534. These are always prefixed with “800" so they will be entered and displayed on Provisioning Manager (PM) as "80000001" to "80065534." Every MCC 7500 dispatch console will use a single radio ID at each individual position. 3. Operational Context The Statewide Radio System will start at the beginning of the talkgroup range and the radio ID range with “1,” as indicated in the table of Allocated Talkgroup and Radio ID Numbers. In planning the values for the table, individual agencies should use a realistic anticipation of the numbers of talkgroup and radio user IDs that are expected to be in use during their initial implementation, plus a reasonable quantity for future growth. These amounts will then be entered into the Allocated Talkgroup and Radio ID Numbers as the Fleetmap process progresses.


The system management structure of the ARMER system allows for the Statewide System Administrator and other approved local System Administrators, defined in State Standard 1.11.1, to create and load IDs into the system. While the Statewide System Administrator has full PM rights to create/edit all IDs in the system, the other local System Administrators have PM access and creation rights to their defined security group. 4. Recommended Protocol/ Standard At the time of participation plan approval, the Operations and Technical Committee (OTC) will assign an approved number of talkgroup and radio IDs to the requesting agency. This number is the planned number initially needed by the agency, plus a reasonable quantity for future growth. If more IDs are required in the future, the agency will need to follow the procedures outlined in State Standard 1.8.0, Moves, Changes, and Additions, to request more IDs from the OTC. For programming radios, talkgroups, and console positions, individual agencies will use the IDs that have been reserved for them in the Table of Defined Ranges. Approved local System Administrators that have been assigned a system management account will load the appropriate IDs into the system as needed, not exceeding their allocation from the OTC. Agencies must not use IDs that are not their own. 5. Recommended Procedure N/A 6. Management The Statewide System Administrator will maintain the Table of Allocated Talkgroup and Radio ID Numbers and the Table of Defined Ranges. Local System Administrators will individually manage the ID ranges for day-to-day activities. All Local System Administrators shall complete monthly self-audits outlining the amount of ID’s currently in use by their agencies, in reference to their allocations. Local System Administrators will be required to attend a meeting called by the Statewide System Administrator to discuss system management procedures and review audits in need of attention. Between December 1 and 31 of each year, all Local System Administrators shall submit a yearly report to the Statewide System Administrator outlining the amount of IDs currently in use by their agencies, in reference to their allocations.


All System Administrators found to be in violation of this standard will be held accountable for their actions in accordance with Section 7 of the State Standards, Compliance and Conflict Resolution.

Radio ID and Talkgroup Allocation 1 State Standard 2.5.0

SRB Approval 10/22/20091

Formatted: Font: Times New Roman, 8 pt, Font color:Gray-50%

Formatted: Tab stops: 1.91", Left + Not at 3" + 6"

Formatted: Font: Cambria, 12 pt, Font color: Auto, Checkspelling and grammar



Formatted: Font: Times New Roman, 8 pt, Font color:Gray-50%, Check spelling and grammar




Document Section:2 2 – Configuration and Allocation Status: Complete State Standard NumberSub-Section:

State 2.5.0

Procedure Standard Title: Radio ID and Talkgroup Allocation

Date Established: 1/19/2001 SECRB Approval: 10/22/2009 Replaces Document Dated: 10/01/2009

Date Revised: 10/01/200902/27/2017 1. Purpose or Objective The purpose of allocating talkgroup ID ranges and& radio ID ranges for the individual agencies is to help manageallows the individual agencies to manage t their pool of IDs as talkgroups, & radios users, or / console positions are configured. This will simplify the management of the IDs and provide an easier indication of what IDs belong to what agency in the event that a radio user alias is not available. 2. Technical Background Radio IDs must be in the range of 1 to 16,777,211. It is recommended that IDs above 1,000,000 be reserved for future packet data use, although this recommendation isn't enforced via the user interface. These IDs will be the same that users will enter in when doing private calls or call alert pages. Also, the IDs picked at this step will be the same as the displaythat will be displayed on the ssubscriber radios if the "ID Display" feature is purchased and enabled. These IDs will also be displayed at the console if the console alias feature is not used. Talkgroups must be in the range of 1 to 65,534. These are always prefixed with “800" so they will be entered and displayed on Provisioning the Mmanager (PM) as "80000001" to "80065534." Every Gold Elite Dispatch console will also use a radio ID for each individual talkgroup at each individual position that is programmed into the console, and must be factored in the planning. Each CEB based logging track also requires a radio ID. Every MCC 7500 dDispatch console will also use a single radio ID at each individual position.

Radio ID and Talkgroup Allocation 2 State Standard 2.5.0

SRB Approval 10/22/20091


Formatted: Tab stops: 1.91", Left + Not at 3" + 6"

Formatted: Font: Cambria, 12 pt, Font color: Auto, Checkspelling and grammar



Formatted: Font: Times New Roman, 8 pt, Font color:Gray-50%, Check spelling and grammar


Radio ID and Talkgroup Allocation 1 State Standard 2.5.0 SECRB Approval 10/22/2009

Formatted: Left, Tab stops: 3.25", Centered


Formatted: No bullets or numbering




1. 3. Operational Context: The Statewide Radio System will start at the beginning of the talkgroup range and the radio ID range with “1,” and at the beginning of the Radio ID range with “1” as indicated in the table of Allocated Talkgroup and& Radio ID Numbers. The other regions of the state will follow the last entry. In planning the values for the table, the individual agencies should use a realistic anticipation of the numbers of talkgroup and& radio user IDs that are expected to be in use during their initial implementation, plus a reasonable quantity for future growth for 3 years. These amounts will then be entered into the Allocated Talkgroup and Radio ID Numbers as the Fleetmap process progresses. The system management structure of the ARMER system allows for the Statewide System Administrator and other approved lLocal System Administrators, defined in StateARMER Standard 1.11.1, to create and load IDs into the system. While the Statewide System Administrator has full UCM PM rights to create/edit all IDs in the system, the other lLocal System Administrators have PMUCM access and creation rights to their defined security group. 4. Recommended Protocol/ Standard: At the time of participation plan approval, the Operations and Technical Committee (OTC) will assign an approved fixed number of tTalkgroup and rRadio IDs to the requesting agency. This number is the planned number initially needed by the agency, plus a reasonable quantity for future growth for three years. If more IDs are required in the future, the agency will need to follow the procedures as outlined in StateARMER Standard 1.8.0, : Moves, Changes, and Additions, to request more IDs from the OTC. For programming radios users, talkgroups, and console positions, individual agencies will use the IDs that have been reserved for them in the Table of Defined Ranges. Approved lLocal System Administrators that have been assigned a system management account will load the appropriate ID’s into the system as needed, but not exceeding their allocation from the OTC. Agencies must not use IDs that are not their own. 5. Recommended Procedure At the time of participation plan approval the OTC will assign a fixed number of talkgroup and radio IDs to the requesting agency. This number is the planned number needed by the agency plus a reasonable quantity for future growth for three years. If more IDs are required in the future the agency will need to follow the procedures for moves changes and additions to request more IDs from the OTC.




Approved Local System Administrators that have been assigned a system management account will load the appropriate ID’s into the system as needed, but not exceeding their allocation from the OTC. At the OTC’s discretion, existing users may be required to submit a plan projecting the number of talkgroup and radio ID’s that will be needed for future growth. The approved three year projection plans will then be used to update the Table of Allocated Talkgroup & Radio ID Numbers. N/A 6. Management The Statewide System Administrator will maintain the Table of Allocated Talkgroup and& Radio ID Numbers and the Table of Defined Ranges. Local System Administrators will individually manage the ID ranges for day- to- day activities. All LLocal System Administrators shall complete monthly self-audits outlining the amount of ID’s currently in use by their agencies, in reference to their allocations. Local System Administrators will be required to attend a meeting called by the Statewide System Administrator, to discuss system management procedures and review audits in need of attention. Between December 1 and December 31 of each year, all LLocal System Administrators shall submit a yearly report to the Statewide System Administrator, outlining the amount of ID’s currently in use by their agencies, in reference to their allocations. All System Administrators found to be in violation of this standard will be held accountable for their actions in accordance with Section 7 of the StateARMER Standards Section 7,: Compliance and Conflict Resolution.

Formatted: Font: Not Bold

Maintenance of Alias List 1 State Standard 1.4.2 SRB Approval 12/17/2015



Document Section 1 Management of System Status: Complete State Standard Number 1.4.2 Standard Title Maintenance of Alias List Date Established 08/07/2001 SEC Approval: 12/17/2015 Replaces Document Dated 11/16/2015 Date Revised 03/06/2017

1. Purpose or Objective The purpose of this standard is to define a procedure for maintaining the Radio User and Talkgroup Agency Acronym table and for cases where two or more parties are in contention over an alias, agency prefix, etc. Login User aliases and agency acronym tables are stored within the system database and will be maintained by the Statewide System Administrator. 2. Technical Background Capabilities Having the agency acronym table readily available to the System Administrators will facilitate agency planning and assist agencies with reference information on identifying ownership of talkgroups and radio users. Constraints The agency acronym table must be kept up-to-date in a central location. 3. Operational Context Radio users, console ID’s, and talkgroups are prefixed by an agency ownership acronym, as defined in State Standard 2.2.0. The current acronym table will be kept on the system for easy access to the administration staff supporting the system. 4. Recommended Protocol/Standard N/A


5. Recommended Procedure The Statewide System Administrator will manage the contents of the agency acronym table. If there is a conflict over acronyms that cannot be resolved by agencies involved, the issue shall be bought to the Operations and Technical Committee (OTC) for resolution. 6. Management The Statewide System Administrator will be responsible for maintaining, archiving, updating, and distributing the agency acronym table.




Document Section 1 Management of System Status: Complete State Standard Number 1.4.2 Standard Title Maintenance of Alias List Date Established 08/07/2001 SECRB Approval:

12/17/2015 Replaces Document Dated 11/16/2015 03/03/2005 Date Revised 11/16/201503/06/2017

1. Purpose or Objective The purpose of this standard is to define a procedure for maintaining the Radio User and Talkgroup Agency Acronym table and for cases where two or more parties are in contention over an alias, agency prefix, etc. Login User aliases and agency acronym tables are stored within the system database and will be maintained by the Statewide System Administrator. 2. Technical Background Capabilities Having the agency acronym table readily available to the System Managers and Administrators will facilitate agency planning and assist agencies with reference information on identifying ownership of talkgroups and radio users. Constraints The agency acronym table must be kept up-to-date in a central location. 3. Operational Context Radio users, console ID’s, and talkgroups are prefixed by an agency ownership acronym, as defined in State Standard 2.2.0. The current acronym table will be kept on the system for easy access to the administration staff supporting the system. Only the first two characters are specified in the naming standard, and showing additional agency subdividing in the acronym table is optional. 4. Recommended Protocol/Standard N/A


5. Recommended Procedure The Statewide System Administrator will manage the contents of the agency acronym table. If there is a conflict over acronyms that cannot be resolved by agencies involved, the issue shall be bought to the Operations and Technical Committee (OTC) for resolution. 6. Management The Statewide System Administrator will be responsible for maintaining, archiving, updating, and distributing the agency acronym table.

Talkgroup and Multigroup Ownership State Standard 3.12.0 SECB Approval 6/1/2001

1


Document Section 3 Interoperability Standards Status: Complete State Standard Number 3.12.0 Standard Title Talkgroup and Multigroup

Ownership Date Established 01/01/2001 SECB Approval: 12/17/2009 Replaces Document Dated 11/29/2009 Date Revised 03/06/2017

1. Purpose or Objective The purpose of this standard is to define the ownership of private, shared, and interoperability talkgroups and multigroups. This provides standard, written documentation so System Administrators have firm guidelines as to who is permitted to have particular talkgroups and multigroups programmed into their radios. 2. Technical Background Capabilities Constraints 3. Operational Context Private and shared talkgroups and multigroups are owned by the agency creating, or requesting the creation of, the talkgroup/multigroup. The process for predefined sharing authorizations is explained in State Standard 2.7.0. 4. Recommended Protocol/ Standard There are three tiers of talkgroups and multigroups that will be programmed into the system: Private These are defined as private talkgroups or multigroups owned by individual user agencies and used for normal day-to-day operations. They are not shared with any other agencies. Private talkgroups and multigroups are either “Listed” or “Unlisted”. Only those private talkgroups/multigroups used for undercover operations or other highly sensitive confidential law enforcement activities may be “Unlisted.” The naming of private talkgroups will be in accordance with State Standard 2.3.0.


2

Shared These are defined as private talkgroups and multigroups owned by individual user agencies, shared by mutual agreement. These will generally be used for routine or pre-planned activities between the sharing agencies. The underlying principle of private and shared talkgroups and multigroups is that they are owned by a particular agency or group of agencies, and the talkgroup or multigroup will not be programmed into another agency's radios unless specifically authorized by the owner. System Administrators shall not allow a talkgroup or multigroup to be programmed into a radio without such authorization. Before a talkgroup or multigroup can be shared, the owning agency System Administrator must pre-authorize the sharing arrangement and/or provide a letter of authorization. The naming of shared talkgroups will be in accordance with State Standard 2.3.0. Interoperability Interoperability talkgroups and multigroups are intended for interagency communications. These interoperability talkgroups and multigroups may be statewide, regional, or local. Statewide interoperability talkgroups and multigroups are not to be owned by any specific agency and will not require agency letters of authorization. Regional interoperability talkgroups and multigroups are owned and managed by the region. Regional interoperability resources will be prefixed with regional prefix (see State Standard 2.3.0). The Regional Emergency Communications Boards (ECBs)/Emergency Services Boards (ESBs) will govern the standards for which radios may have regional interoperability talkgroups and multigroups, as well as standards regarding use of these resources. 5. Recommended Procedure The procedure regarding pre-authorizing talkgroup sharing is defined in State Standard 2.7.0. 6. Management The System Administrators will be responsible to see that this policy is implemented as defined in the system standards manual. Identified issues and concerns will be brought to the Statewide System Administrator or the appropriate ECB/ESB.


1


Document Section 3 Interoperability Standards Status: Complete State Standard Number 3.12.0 Standard Title Talkgroup and Multigroup

Ownership Date Established 01/01/2001 SECB Approval: 12/17/2009 Replaces Document Dated 04/25/200111/29/2009 Date Revised 11/29/200903/06/2017 1. Purpose or Objective The purpose of this standard is to define the ownership of private, shared, and interoperability talkgroups and multigroups. This provides standard, written documentation so System Administrators Managers have firm guidelines as to who is permitted to have particular talkgroups and multigroups programmed into their radios. 2. Technical Background Capabilities Constraints 3. Operational Context Private and shared talkgroups and multigroups are owned by the agency creating, or requesting the creation of, the talkgroup/multigroup. The process for predefined sharing authorizations is explained in State Standard 2.7.0. 4. Recommended Protocol/ Standard There are three tiers of talkgroups and multigroups that will be programmed into the system: Private These are defined as private talkgroups or multigroups owned by individual user agencies and used for normal day-to-day operations. They are not shared with any other agencies. Private talkgroups and multigroups are either “Listed” or “Unlisted”. Only those private talkgroups/multigroups used for undercover operations or other highly sensitive confidential law enforcement activities may be “Unlisted.” The naming of private talkgroups will be in accordance with State Standard 2.3.0.


2

Shared These are defined as private talkgroups and multigroups owned by individual user agencies, shared by mutual agreement. These will generally be used for routine or pre-planned activities between the sharing agencies. The underlying principle of private and shared talkgroups and multigroups is that they are owned by a particular agency or group of agencies, and the talkgroup or multigroup will not be programmed into another agency's radios unless specifically authorized by the owner. System Administrators Managers shall not allow a talkgroup or multigroup to be programmed into a radio without such authorization. Before a talkgroup or multigroup can be shared, the owning agency System Administrator must pre-authorize the sharing arrangement and/or provide a letter of authorization. The naming of shared talkgroups will be in accordance with State Standard 2.3.0. Interoperability Interoperability talkgroups and multigroups are intended for interagency communications. and assistance and fall into two categories: those used for 800 MHz communication only and those that are patched to conventional radio frequency (RF) resources. These interoperability talkgroups and multigroups may be statewide, or regional, or local.. Statewide interoperability talkgroups and multigroups are not to be owned by any specific agency and will not require agency letters of authorization. Regional interoperability talkgroups and multigroups are owned and managed by the region. Regional interoperability resources will be prefixed with regional prefix (see State Standard 2.3.0). The Regional Emergency Communications Boards (ECBs)/Emergency Services Radio Boards (ESBRRBss) will govern the standards for which radios may have regional interoperability talkgroups and multigroups, as well as standards regarding use of these resources. 5. Recommended Procedure The procedure regarding pre-authorizing talkgroup sharing is defined in State Standard 2.7.0. 6. Management The System Administrators will be responsible to see that this policy is implemented as defined in the system standards manual. Identified issues and concerns will be brought to the Statewide System Administrator or the appropriate ECB/ESBRRB.

Use of Shared Talkgroups State Standard 2.7.0 SECB Approval 9/1/2005 1


Document Section 2 Configuration and Allocation Status: Complete State Standard Number 2.7.0 Standard Title Use of Shared Talkgroups Date Established 03/01/2001 SERB Approval: 09/01/2005 Replaces Document Dated 04/12/2005 Date Revised 03/06/2017

1. Purpose or Objective The intent of this standard is to provide an option to ARMER users to allow talkgroup owners to predefine sharing authorizations for other agencies. 2. Technical Background Capabilities Constraints 3. Operational Context Talkgroups are considered to be “owned” by the agency requesting the creation of the talkgroup, similar to the ownership that applies to conventional radio frequency (RF) resources. As the owner of the talkgroup, the owning agency has the authority and control to define who can and cannot use the talkgroup and to what degree. Traditionally, this process has been primarily accomplished with “letters of authorization.” The optional method to simplify this process is for the owning agency to predefine sharing authorizations, as diagrammed in the chart in section 6. The predefined authorizations are kept in the talkgroup spreadsheet with the System Administrator, who is responsible for the system programming for the using agency. These spreadsheets would be shared among the System Administrators and would be a reference available for users of the system for talkgroup planning. If an agency does not predefine sharing authorization for a particular talkgroup, the default will be a “P,” as defined in paragraph 4.


4. Recommended Protocol/ Standard The following codes are combined to define the intended pre-authorizations:

P Permission is required to gain authorization for use. A letter of permission must be generated and on file with the appropriate System Administrators.

D Defined agencies may share, to be defined in a separate letter. The letter would outline specific purpose talkgroups, i.e., only dispatch console, only neighboring cities, etc. The letter will be on file with the appropriate System Administrators.

L Like agencies may share, “Fire, Medical, Law, Public Works, etc.”

A All agencies. No restriction on sharing, with the exception of the media, which is handled as a separate procedure in this manual. (See State Standard 5.1.0)

RX Only authorized to receive. TX Authorized to transmit and receive.

5. Recommended Procedure System Administrators, working with the user groups, perform this task. 6. Management The System Administrators are responsible for the management of this procedure.

*The following table is a portion of. The larger table is also used to lay out the fleetmap information as described in State Standard 2.6.0, “Fleetmap Standards”.


Talkgroup

Ow

ning Agency D

escription Adm

inistrating Agency Global Sharing Authorizations

P = Permission letter required to gain authorization for use D = Defined Use – Letter required L = Like Agencies may share “Fire, Medical, Law, Works” etc. A = All Agencies RX = Are only authorized to receive TX = Are authorized to receive & transmit**

Talkgroup 1 D-TX Talkgroup 2 L-TX Talkgroup 3 A-TX Talkgroup 4 P-RX Talkgroup 5 P-TX Talkgroup 6 D-TX Talkgroup 7 L-TX Talkgroup 8 A-TX Talkgroup 9 P-RX Talkgroup 10 P-TX Talkgroup 11 D-TX Talkgroup 12 L-TX Talkgroup 13 A-TX Talkgroup 14 P-RX etc. P-RX

**The "RX" option shown in the table is an authorization that permits receive only use, although the radio may be technically capable of transmitting (TX) operation on the talkgroup.



Document Section 2 Configuration and Allocation Status: Complete State Standard Number 2.7.0 Standard Title Use of Shared Talkgroups Date Established 03/01/2001 SERB Approval: 09/01/2005 Replaces Document Dated 12/04/200304/12/2005 Date Revised 04/12/200503/06/2017

1. Purpose or Objective The intent of this standard is to provide an option to ARMER users to allow talkgroup owners to predefine sharing authorizations for other agencies. 2. Technical Background Capabilities Constraints 3. Operational Context Talkgroups are considered to be “owned” by the agency requesting the creation of the talkgroup, similar to the ownership that applies to conventional radio frequency (RF) resources. As the owner of the talkgroup, the owning agency has the authority and control to define who can and cannot use the talkgroup and to what degree. Traditionally, this process has been primarily accomplished with “letters of authorization.” The optional method to simplify this process is for the owning agency to predefine sharing authorizations, as diagrammed in the chart in section 6. The predefined authorizations are kept in the talkgroup spreadsheet with the System Administrator, who is responsible for the system programming for the using agency. These spreadsheets would be shared among the System Administrators and would be a reference available for users of the system for talkgroup planning. If an agency does not predefine sharing authorization for a particular talkgroup, the default will be a “P,” as defined in paragraph 4.


4. Recommended Protocol/ Standard The following codes are combined to define the intended pre-authorizations:

P Permission is required to gain authorization for use. A letter of permission must be generated and on file with the appropriate System Administrators.

D Defined agencies may share, to be defined in a separate letter. The letter would outline specific purpose talkgroups, i.e., only dispatch console, only neighboring cities, etc. The letter will be on file with the appropriate System Administrators.

L Like agencies may share, “Fire, Medical, Law, Public Works, etc.”

A All agencies. No restriction on sharing, with the exception of the media, which is handled as a separate procedure in this manual. (See State Standard 5.1.0)

RX Only authorized to receive. TX Authorized to transmit and receive.

5. Recommended Procedure System Administrators, working with the user groups, perform this task. 6. Management The System Administrators are responsible for the management of this procedure.

*The following table is a portion of. The larger table is also used to lay out the fleetmap information as described in State Standard 2.6.0, “Fleetmap Standards”.


Talkgroup

Ow

ning Agency D

escription Adm

inistrating Agency Global Sharing Authorizations

P = Permission letter required to gain authorization for use D = Defined Use – Letter required L = Like Agencies may share “Fire, Medical, Law, Works” etc. A = All Agencies RX = Are only authorized to receive TX = Are authorized to receive & transmit**

Talkgroup 1 D-TX Talkgroup 2 L-TX Talkgroup 3 A-TX Talkgroup 4 P-RX Talkgroup 5 P-TX Talkgroup 6 D-TX Talkgroup 7 L-TX Talkgroup 8 A-TX Talkgroup 9 P-RX Talkgroup 10 P-TX Talkgroup 11 D-TX Talkgroup 12 L-TX Talkgroup 13 A-TX Talkgroup 14 P-RX etc. P-RX

**The "RX" option shown in the table is an authorization that permits receive only use, although the radio may be technically capable of transmitting (TX) operation on the talkgroup.

Bradley Hibben Radio Engineer 1 DOT Radio Operations Center Office of Statewide Radio Communications 651-234-7892 [email protected] Statewide Emergency Communications Board Operations and Technical Committee February 01, 2017 Re: Kenwood TK-5930 Mobile radio, ARMER System Subscriber Radio Testing Testing of the following radio for use on the ARMER System was completed January 25, 2017, using the “Subscriber Unit Test Procedure” dated March 2010: Kenwood TK-5930 Mobile, S/N B5900010 The testing was performed by the following individuals: Thomas Bredemus, MnDot Bradley Hibben, MnDot Thomas Kaisler, MnDot The radio passed all the required tests for use on the ARMER Network. Non-required tests the radio failed:

1) 5B, Test Results page 5, Receive a Multi-Group Call”. Operation was unreliable. 2) 6A, Test Results page 6, “Emergency Alarm/Call with Tactical Operation”. Note, tactical operation is not

allowed on the ARMER system. 3) 3, Test Results page 7, “Secure/Encryption Operation”, would not load keys 4) 4A, Test Results page 6, “Subscriber to Landline Telephone Interconnect” 5) 4B, Test Results page 8, “Subscriber to Landline Telephone Interconnect, Over-dial Mode” 6) 5, Test Results page 8, “Call Alert” 7) 6, Test Results page 8, “Private Call” 8) 9, Test Results page 8, “Direct Talk Around in Digital Encrypted Mode” 9) 2, Test Results page 11, “Radio Operates in Failsoft”

Bradley Hibben

mailto:[email protected]

ARMER Acceptance Test Checklist Kenwood TK-5930, S/N B5900010, Test ID 104955

APPENDIX A - TESTING CHECKLIST Radio Programming Software

Test # Test Description Comment or results noted Pass/Fail/or N/A

Required for operation on system

1 Programming Software Load Test Page 4

Vista, Windows 7, Windows 8/8.1

Pass

No

2 Read Configuration from Radio Test Page 4

Firmware rev must be within range of programming s/w

Pass

No

3 Radio Version Test Page 4

Select “Transceiver Information” , Version K2.01.00

Pass

No

4 Software Protection Test Page 4

Software and radio features are activated through MFG server. ASK’s are distributed via the MFG. To obtain a system key a form must be completed by the requesting agency and then authorized by the system owner before

EFJ/Kenwood will furnish a key.

Pass

No

5 Edit Radio Configuration Test Page 5

Unlocked features are editable

Pass

No

6 Save Radio Configuration to Disk Test Page 5

Saved as .dat files

Pass

No

1


7 Load Radio Configuration from Disk Test Page 5

Pass

No

8 Write Configuration to Radio Test Page 5

Pass

No

9 Clone Radio Test Page 5

Read config, write to new radio with Radio ID’s set in the personality

system information.

Pass

No

10 Test of a radio with No System Access Privileges Test Page 6

Invalid ID, Radio indicates “OUT OF RANGE”

Pass

No

Radio Registration / Affiliation Testing

Test # Test Description Page 7-8 for tests 1-4

Comment or results noted Pass/Fail/or N/A


5 Radio indication when account disabled in UCS Test Page 6

Radio indicates “SYSTEM DENY”

Pass

Yes

2


Configure Evaluation Radio for Testing.

Test # Test Description Page 6-7



1 Program the radio with the test configuration

Pass

1 Note

2 Note

3 Note

4 Note

5 Note

6 Note

3





1 Radio Registration with System Test Page 7

Pass

Yes

2 Radio De-Registration with System Test Page 7

Pass

No

3 Radio Affiliation Display / Updates Talkgroup Test Page 7-8

Roamed to Anoka on TG-D from City Center on TG-A

Pass

Yes

4 Radio Affiliation Display / Updates Multigroup Test Page 8

Displays TG-ABC as Expected

Pass

Yes

4


Trunking Tests



1 Talkgroup Call Test Page 8

Operates as expected

Pass

Yes

2 Smart PTT Test Page 9

Indicates “System Deny”

Pass

Yes

4 Continuous Assignment Updating Test Page 9

Updates and receives in progress call

Pass

No

5A Initiate a Multigroup Call Test Page 10

Will initiate MG call and receive talk back audio

Pass

No

5B Receive a Multigroup Call Test Page 10

Several attempts, this feature did not work. When feature was used while radio was locked to a site operating in “Site Trunking” mode the feature

worked. When the site went to “Wide Area” operation, the feature continued to work. Failed test because feature is unreliable. When it did work it

functioned as expected.

Fail

No

5


6A Emergency Alarm/Call with Tactical Operation Test Page 11

TG revert only

Fail/NA

No

6B Emergency Alarm/Call with TalkGroup Revert Test Page 11

Reverts as programmed

Pass

No

6C Emergency Alarm ID Display Test Page 12

Displays ID of Radio issuing the emergency

Pass

No

Radio Control Manager (RCM) Tests



1 Emergency Alarm Display Test Page 12

Displays in RCM, Zone Watch, and on radio

Pass

No

2 Dynamic Regrouping Test Page 13-14

Re-groups and operation as expected

Pass

No

3 Selective Radio Inhibit Test Page 14-15

Shows registered, not affiliated, blank screen, no operation

Pass

Yes

6


4 Radio Check Test Page 15-16

Pass

No

Features Testing



1A Non-Priority Scan Test Page 16-17

Pass

No

1B Priority Scan Test Page 17

Pass

No

1C User Editable Scan List Test Page 17

Pass

No

2 Rx Only Radio Test Page 18

Indicates “SYSTEM DENY”, will not TX. Individual TG’s can be

programmed as receive only

Pass

No

3 Secure / Encryption Operation Test Page 18-19

Would not load keys, would not recognize KVL 3000

Fail

No

4A Subscriber to Landline Telephone Interconnect Test Page 19-20

Fail

No

7


4B Subscriber to Landline Telephone Interconnect, Overdial Mode Test Page 20

Fail

No

4C Landline to Subscriber Telephone Interconnect Test Page 20-21

Will receive phone calls

Pass

No

5 Call Alert Test Page 21-22

Receives pages, will not send

Fail

No

6 Private Call Test Page 22-23

Receives calls, will not send

Fail

No

7 Conventional 800 MHz Resources Test Page 23

8CALL90 and 8TAC91

Pass

No

8 Direct Talk-Around in Digital clear mode Test Page 23

Pass

No

9 Direct Talk-Around in Digital encrypted mode Test Page 23-24

Unable to load keys, would not recognize KVL 3000

Fail

No

8


Radio Roaming Tests



1 Adjacent control channel Test Page 24

Roamed to Anoka on TG-D

Pass

Yes

2 Multizone Operation Test Page 24

Moved to Z2, Henn E on TG-F

Pass

No

3 Site Access Control for Talkgroup & Radio User Test Page 25

Pass

Yes

5 Site Preference & Roaming Test Page 26

Roamed and locked on to Hastings by Keats Ave on HWY 36

Pass

Yes

9


Technical Specification Testing



1 Radio RF specifications Test Page 27

8CALL90D, Frequency 808.01325(-175hz), PWR Low 1.95W, Med 9.89W, High PWR 39.6W, deviation 1.99 Khz

SOA-2 Squelch breaks @ -124 dbm, clear at -120, Modulation Fidelity 1.3%, Power 1.64/9.36/33.5. Frequency 853.937415Mhz (-85hz)

Pass

Yes

2 Environmental Testing Test Page 27

Pass

No

3 Battery Test Page 27

N/A

No

10


Trunking Tests

3 Busy Tone and Callback Test Page 28

Displays “Queued”, call will proceed when channel is clear

Pass

No

System Failure Mode Testing



1 Site Trunking Talkgroup Call Test Page 29

Displays “SITE TRUNK” with red border/banner

Pass

Yes

2 Radio Operates in Failsoft Mode Test Page 30

Displays “Failsoft” with red border/banner

Pass

No

3 Failsoft Recovery to Site Trunking Test Page 30

Recovers from “Failsoft”

Pass

No

Radio Roaming Tests

4 Site Avoidance Test Page 31

Roamed to Hastings by Keats Ave on HWY 36. RX and TX normal during

switch over.

Pass

Yes

11


Audio Quality Test



1 Audio Quality Testing Test Page 32

Clear audio, 4.5.

Pass

No

12

TK-5730/5830/5930 700/800 MHz • VHF • UHF • P25 PHASE 1 & 2 • FM ANALOG • LTR

Round-the-clock public safety operations can be extremely demanding for both personnel and equipment. The reliable TK-5x30 mobile radios offer clear mission critical communications for police, fire and EMS.

MAIN FEATURES• Digital operation in P25 Phase 1 & 2• P25 Phase 1 Conventional/Trunked Operation (standard) • Mixed Digital, FM Analog & LTR Operation allows intelligent migration in mixed sites & with digital radios in other sites• Large, color 2.55” (154 x 422 pixels) TFT Display• Easy to follow GUI & Multi-line Text to convey more information• Dual Remote Control Head Option & Multi RF Deck) Options• Built-In GPS Receiver for effective fleet management• Bluetooth® Module built-in for hands-free operation• Active Noise Cancelling utilizes built-in DSP with 2 microphones for suppression of ambient noise (dual-mic)• Built-in 56-bit DES encryption• Optional 256-bit AES encryption• microSD/microSDHC Memory Card Slot for increased memory capacity for voice and data• IP54/55 and MIL-STD-810 C/D/E/F/G• Maximum of 4,000 CH/Radio capacity, 512 CH/Zone, 128 Zones• DB-25 Accessory Connector• 4 W Speaker Audio

P25 Mission Critical

W

A R R A N T Y

STANDARD

3YR

ACCESSORIES• Complete line of accessories including mics & speakers. Download catalog at www.efjohnson.com/products/accessories.

MULTIPLE CONFIGURATIONS (OPTION)The TK-5x30 series allows users to create a variety of configurations to suit different requirements by combining different options.

• Single Remote Control Head/Single RF Deck: Mobile is controlled by a remote control head.• Single Remote Control Head/Multi RF Decks: Operate multiple (up to 3) radio decks from single control head.• Dual Remote Control Heads/Single RF Deck: One controller can be mounted on the dashboard with the other control head remotely mounted (such as the back of an ambulance or fire apparatus).• Dual Remote Control Heads/Multi RF Decks: This adds the convenience of a dual control head to the above configuration so 2 operators can control up to 3 radios from separate control heads.

DIGITAL - P25 MODE• P25 Phase 1 Conventional/Trunked Operation• P25 Phase 2 Trunked Operation• AMBE+2™ Enhanced Vocoder• Talk Group ID Lists• Individual ID Lists• Caller ID Display• Remote Monitor/Remote Check• Radio Inhibit• Encryption Key Zeroize & Retention• P25 GPS Location• P25 Over-the-Air Re-keying• Over-the-Air Programming*1

FM MODES - GENERAL• Conventional & LTR Zones• MDC-1200: PTT ID ANI / Caller ID Display, Emergency, Radio Check / Inhibit• QT / DQT & Two-Tone• Built-in Voice Inversion Scrambler

*1 Requires OTAP management software.

IGENERAL TK-5730 TK-5830 TK-5930

Frequency Range 136-174 MHz Type 1: 450-520 MHzType 2: 380-470 MHz

RX:763-776,851-870 MHzTX:763-776,793-806,806-825,851-870 MHz

Max. Channels Per Radio 1024 (Up to 4000 channels with option)

Number of Zones 128

Max. Channels Per Zone 512

Channel SpacingAnalog 12.5/15/20/25/30 kHz 12.5/25 kHz 12.5/25 kHz

Digital 6.25/12.5 kHz 6.25/12.5 kHz 6.25/12.5 kHz

Power Supply 13.6 V DC ±15 %

Current Drain

Standby 0.45 A

RX 2.3 A

TX 13 A

Operating Temperature -22 °F to +140 °F (-30 °C to +60 °C)

Frequency Stability ±1.0 ppm

Dimensions (W x H x D)Radio w/Control Head, Projections not Included

6.69 x 1.89 x 6.93 in. (170 x 48 x 176 mm)

6.73x1.89x7.72 in.(171.0 x 48.0 x 196 mm)

Weight (Radio w/Control Head) 3.53 lbs (1.6 kg) 3.75 lbs (1.7kg)

RECEIVER TK-5730 TK-5830 TK-5930

Sensitivity

P25 Digital (5% BER) 0.25 μV


Analog (12 dB SINAD) 0.25 μV

Selectivity

P25 Digital 63 dB

Analog @ 12.5 kHz 71 dB 70 dB

Analog @ 25 kHz 81 dB 78 dB

Intermodulation 80 dB

Spurious Rejection 87 dB 85 dB

Audio Distortion 2%

Audio Output Power 4 W/4 Ω (Remote Control Head: 3 W/4 Ω)

TRANSMITTER TK-5730 TK-5830 TK-5930

RF Power Output Power 50 to 5 W 45 to 5 W 30W to 2W (700 MHz)35W to 2W (800 MHz)

Spurious Emission -73 dB -75 dB -80 dB

FM Hum & NoiseAnalog @ 12.5 kHz 45 dB 40 dB

Analog @ 25 kHz 50 dB 45 dB

Audio Distortion 2%

Emission Designator 16K0F3E, 11K0F3E, 8K10F1E, 8K10F1D, 8K10F1W, 8K30F1E, 8K30F1D, 8K30F7W, 4K00F1E, 4K00F1D, 4K00F7W, 4K00F2D

*25 and 30 kHz are not included in the models sold in the USA or US territories. Analog measurements made per TIA 603 and specifications shown are typical. Digital measurements made per TIA 102CAAA and specifications shown are typical.

TK-5730/5830/5930 Mobile SPECIFICATIONS

All specifications are subject to change without notice. Please check the website for the latest version.V.03.15.16 © Copyright 2016 EF Johnson Technologies, Inc. (E.F. Johnson Company is operating entity)AMBE+2™ is a trademark of Digital Voice Systems Inc.SD and microSD are trademarks of SD-3C, LLC in the United States, and/or other countries. The Bluetooth word mark and logos are registered trademarks owned by the Bluetooth SIG, Inc.

EF Johnson Technologies, Inc.1440 Corporate Drive, Irving, TX 75038-2401

800.328.3911 • www.efjohnson.com

P25 Products Provided by EF Johnson Technologies, Inc., a JVCKENWOOD Company

INTERNATIONAL PROTECTION STANDARD

Dust & Water IP54, IP55*2

MIL STANDARD 810C 810D 810E 810F 810G

Low Pressure 500.1/ I 500.2/ I, II 500.3/ I, II 500.4/ I, II 500.5/ I, II

High Temperature 501.1/ I, II 501.2/ I, II 501.3/ I, II 501.4/ I, II 501.5/ I, II

Low Temperature 502.1/ I 502.2/ I, II 502.3/ I, II 502.4/ I, II 502.5/ I, II

Temp. Shock 503.1/ I 503.2/ I 503.3/ I 503.4/ I, II 503.5/ I

Solar Radiation 505.1/ I 505.2/ I 505.3/ I 505.4/ I 505.5/ I

Rain*1 506.1/ I, II 506.2/ I, II 506.3/ I, II 506.4/ I, III 506.5/ I, III


Humidity 507.1/ I, II 507.2/ II, III 507.3/ II, III 507.4 507.5/ II

Salt Fog 509.1/ I 509.2/ I 509.3/ I 509.4 509.5

Dust 510.1/ I 510.2/ I 510.3/ I 510.4/ I, III 510.5/ I

Vibration 514.2/ VIII, X 514.3/ I 514.4/ I 514.5/ I 514.6/ I

Shock 516.2/ I, II, V 516.3/ I, IV 516.4/ I, IV 516.5/ I, IV 516.6/ I, IV

*1: Blowing rain protection for the mobile radio’s Remote Control Head only. *2: IP54: RF Deck of the mobile radio; IP55: Remote Control Head for the mobile radio.

Bradley Hibben Radio Engineer 1 DOT Radio Operations Center Office of Statewide Radio Communications 651-234-7892 [email protected] Statewide Emergency Communications Board Operations and Technical Committee February 1, 2017 Re: ARMER System Subscriber Radio Testing Testing of the following radio for use on the ARMER System was completed January 25, 2017, using the “Subscriber Unit Test Procedure” dated March 2010: Kenwood TK-5430 Portable, S/N B5C00134 The testing was performed by the following individuals: Thomas Bredemus, MnDot Bradley Hibben, MnDot Thomas Kaisler, MnDot The radio passed all the required tests for use on the ARMER Network. Non-required tests the radio failed:

1) 6A, Test Results page 6, “Emergency Alarm/Call with Tactical Operation”. Note, tactical operation is not allowed on the ARMER system.

2) 4A, Test Results page 6, “Subscriber to Landline Telephone Interconnect” 3) 4B, Test Results page 8, “Subscriber to Landline Telephone Interconnect, Over-dial Mode” 4) 5, Test Results Page 8, “Call Alert” 5) 6, Test Results Page 8, “Private Call” 6) 2, Test Results Page 11, “Radio Operates in Failsoft”

Notes:

1) 5, Test Results Page 9 “Site Preference and Roaming”. To get this function to work correctly with a “Site Preference” table, the “Good RSSI” level and the “Level 2 Margin” settings require adjustment and multiple operational tests to establish correct settings.

2) 9, Test Results Page 8 “Direct Talk Around in Digital Encrypted Mode”. While this function operated correctly on a conventional digital channel with encryption. Inadvertently having the encryption set to “On” on a conventional channel which is not programmed for encryption will “Scramble” the audio with a proprietary Kenwood scheme. The user must set the encryption setting to off to send or receive audio on a “Non” encrypted conventional channel if any conventional channels are set up for encryption.

Bradley Hibben


ARMER Acceptance Test Checklist Kenwood TK-5430, S/N B5C00134, Test ID 104954





Pass

No


Pass

No


“Transceiver Information” under “Tools” Tab shows S/N, ESN, firmware version (K.1.64.00) and activated features list.

Pass

No


Software and radio features are activated through MFG server. ASK’s are distributed via the MFG. To obtain a system key a form must be completed by the requesting agency and then authorized by the system owner before

EFJ/Kenwood will furnish a key.

Pass

No


Unlocked features are editable

Pass

No


Saved as .dat files

Pass

No

1



Pass

No


Pass

No


Select “Model” from product information tab Pass

No


Displays “Out of Range”

Pass

No






Displays “System Deny”

Pass

Yes

2







Pass

1 Note

2 Note

3 Note

4 Note

5 Note

6 Note

3






Pass

Yes


Pass

No


Pass

Yes


Pass

Yes

4


Trunking Tests




Pass

Yes


Indicates “System Deny” Pass

Yes


Pass

No


Will initiate multi-group calls and will receive talk back calls during the hang time.

Pass

No


Will receive multi-group calls and talk back during the hang time.

Pass

No

5



Appears to program for tactical operation however radio would not stay on selected TG, it reverted to same TG as other TG’s.

Note: Tactical operation is not allowed on ARMER system

Fail N/A

No


Reverts to programmed TG as expected

Pass

No


Radio shows emergency received and ID of radio initiating the call

Pass

No





Displays on ZW and RCM

Pass

No


Indicates regroup with tone and displays “DYN RGROUP”

Pass

No


Display Blanks, affiliation display shows connection, no TG and no user

operation.

Pass

Yes

6



Radio check operates as expected

Pass

No

Features Testing




Pass

No


Pass

No


Pass

No


Displays “SYSTEM DENY”. Individual TG’s can be programmed as

receive only.

Pass

No


Supports multiple keys

Pass

No


Fail

No

7



Fail

No


Will receive phone calls

Pass

No


Will receive page, will not page out.

Fail

No


Will receive private calls, will not initiate a private call.

Fail

No


Pass

No


Pass

No


Pass

No

8


Radio Roaming Tests




Pass

Yes


Pass

No


Pass

Yes


This required multiple drive tests and adjustments of the “Good RSSI Level” and the “Level Margin 2 “settings in the code plug to get switching between sites to operate acceptably. The “Level Margin 2” setting is used when a site

preference table is used.

Pass

Yes

9






8CALL90D, Dev 2.00khz, Power Out 2.08w, Squelch breaks @ 0.36 uVolts, audio clear @ 0.48 uVolts, Freq 851.012335

SOA 2, Power Out 2.37 W, squelch breaks @ -123.7 dbm/0.15 uVolts, audio clear @ 0.2 uVolts (-121 dbm), Modulation fidelity 0.8%.Freq

853.9374 (-100 hz)

Pass

Yes


Pass

No


Pass

No

10


Trunking Tests


Displays “Queued” with key pressed and calls when clear. Auto key when channel clears

Pass

No





Radio prefers wide trunking. Used “Site Lock” to stay on “Site Trunking” site. Radio displays “Site Trunk”

Pass

Yes


Unable to get radio to operate in “Failsoft” mode

Fail

No


Radio will not operate in “Failsoft” however the radio will return to “Site Trunking” operation when the site returns to normal.

Pass

No

Radio Roaming Tests


Aprox 1.5 minutes to change sites Pass

Yes

11


Audio Quality Test




. Audio clear 4.5

Pass

No

12

TK-5230/5330/5430 700/800 MHz • VHF • UHF • P25 PHASE 1 & 2 • FM ANALOG • LTR

Compact P25 Phase 1/Phase 2 radio with large transflective color display, built-in GPS & Bluetooth® is a great fit for public works or public safety agencies looking for a smaller feature rich radio.

P25 Mission Critical

W

A R R A N T Y

STANDARD

3YR

ACCESSORIES• Complete line of accessories including speaker mics, cases, batteries, antennas & chargers. Download the accessory catalog at www.efjohnson.com/products/accessories.

MAIN FEATURES• Digital operation in P25 Phase 1 & Phase 2• P25 Phase 1 Conventional/Trunked Operation (standard)• Mixed Digital, FM Analog & LTR Operation allows migration in mixed sites• Large, color 1.74” (240 x 180 pixels) Transflective TFT Display for better use in direct sunlight & with use of polarized sunglasses• Easy to follow GUI for at-a-glance operational status checking & multi-line text• 4-way Directional-pad (D-pad) & 2-Position Lever Switch for intuitive control• Built-In GPS Receiver/Antenna for effective fleet management• Bluetooth® Module built-in for hands-free operation• Renowned audio quality with Active Noise Cancelling that utilizes built-in DSP with two microphones for suppression of ambient noise (dual-mic)• Built-in 56-bit DES Encryption (4-key DES standard)• Optional 256-bit AES Encryption• Built-in motion sensor for life-critical man down detection• microSD/microSDHC Memory Card Slot for increased voice & data memory capacity• IP67/68 & MIL-STD-810 C/D/E/F/G• Full key models (w/numeric keypad) & standard key models (w/o numeric keypad)• 1 W loud speaker audio

INTELLIGENT BATTERY SYSTEM (OPTION)• System consists of optional high- capacity Li-Ion Battery Series (KNB-L1/ L2/L3), Rapid Charger (KSC-Y32), & Battery Reader (KAS-12) software• Up to 30 rapid chargers can be chain- connected to PC installed with KAS-12• Battery conditions displayed in color illuminated indicators on the charger, & also displayed on connected PC with same color scheme• Up to 1,000 batteries can be managed at a time (requires additional option)

FM MODES - GENERAL• Conventional & LTR Zones• NPSPAC (USA only) Channels (±4.0 Modulation)• MDC-1200: PTT ID ANI / Caller ID Display, Emergency, Radio Check / Inhibit• QT / DQT & Two-Tone• Built-in Voice Inversion Scrambler

DIGITAL - P25 MODE• P25 Phase 1 Conventional/Trunked Operation (standard)• P25 Phase 2 Trunked Operation• AMBE+2™ Enhanced Vocoder• Talk Group ID Lists• Individual ID Lists• Caller ID Display• Remote Monitor/Remote Check• Radio Inhibit• Encryption Key Zeroize & Retention• P25 GPS Location• Over-the-Air Programming*1

*1 Requires OTAP management software.

ITK-5230/5330/5430 Portable SPECIFICATIONS

GENERAL TK-5230 TK-5330 TK-5430

Frequency Range 136-174 MHz Type 1: 450-520 MHzType 2: 380-470 MHz

RX: 763-776, 851-870 MHzTX: 763-776, 793-806, 806-825, 851-870 MHz

Max. Channels Per Radio 1024 (Up to 4000 channels with option)

Number of Zones 128

Max. Channels Per Zone 512

Channel SpacingAnalog 12.5/15/20/25*/30* kHz 12.5/25* kHz 12.5/25 kHz

Digital 6.25/12.5 kHz 6.25/12.5 kHz 12.5 kHz (6.25 kHz)

Power Supply 7.5 V DC ±20%

Battery Life(5-5-90/10-10-80 duty cycle)

KNB-L1 (2,000 mAh) 10 hours / 6.5 hours

KNB-L2 (2,600 mAh) 12.5 hours / 8.5 hours

KNB-L3 (3,400 mAh) 17 hours / 11 hours

Operating Temperature -22 °F to +140 °F (-30 °C to +60 °C)

Frequency Stability ±2.0 ppm ±1.0 ppm ±1.5 ppm

Dimensions (W x H x D)Projections Not Included

KNB-L1 (2,000 mAh) 2.28 x 5.47 x 1.52 in. (58 x 139 x 38.8 mm)



Weight(Dim. & Weight with Battery)

KNB-L1 (2,000 mAh) 15.52 oz (440 g)

KNB-L2 (2,600 mAh) 16.57 oz (470 g)

KNB-L3 (3,400 mAh) 17.98 oz (510 g)

RECEIVER TK-5230 TK-5330 TK-5430

Sensitivity



Analog (12 dB SINAD) 0.25 μV

Selectivity

P25 Digital 60 dB

Analog @ 12.5 kHz 67 dB 64 dB

Analog @ 25 kHz 73 dB

Intermodulation 73 dB 75 dB

Spurious Rejection 80 dB 75 dB

Audio Distortion 3%

Audio Output Power 500 mW/8 Ω (3% Distortion)/1,000 mW/8 Ω (5% Distortion)

TRANSMITTER TK-5230 TK-5330 TK-5430

RF Power Output Power 6 to 1 W 5 to 1 W 3 to 1 W

Spurious Emission -70 dB

FM Hum & NoiseAnalog @ 12.5 kHz 40 dB

Analog @ 25 kHz 45 dB

Audio Distortion 2%

Emission Designator 16K0F3E, 11K0F3E, 8K10F1E, 8K10F1D, 8K10F1W, 8K30F1E, 8K30F1D, 8K30F7W, 4K00F1E, 4K00F1D, 4K00F7W, 4K00F2D 16K0F3E, 14K0F3E,11K0F3E, 8K10F1E,8K10F1D,8K10F1W,8K30F1E, 8K30F1D, 8K30F7W,4K00F1E, 4K00F1D,4K00F7W, 4K00F2D

INTERNATIONAL PROTECTION STANDARD

Dust & Water

IP54, IP55

ImmersionIP67, IP68* *Portable radio immersed for 2 hours at a depth of 1 meter

All specifications are subject to change without notice. Please check the website for the latest version.V.03.15.16 © Copyright 2016 EF Johnson Technologies, Inc. (E.F. Johnson Company is operating entity)AMBE+2™ is a trademark of Digital Voice Systems Inc.SD and microSD are trademarks of SD-3C, LLC in the United States, and/or other countries. The Bluetooth word mark and logos are registered trademarks owned by the Bluetooth SIG, Inc.

EF Johnson Technologies, Inc.1440 Corporate Drive, Irving, TX 75038-2401

800.328.3911 • www.efjohnson.com

P25 Products Provided by EF Johnson Technologies, Inc., a JVCKENWOOD Company


Low Pressure 500.1/ I 500.2/ I, II 500.3/ I, II 500.4/ I, II 500.5/ I, II

High Temperature 501.1/ I, II 501.2/ I, II 501.3/ I, II 501.4/ I, II 501.5/ I, II

Low Temperature 502.1/ I 502.2/ I, II 502.3/ I, II 502.4/ I, II 502.5/ I, II

Temp. Shock 503.1/ I 503.2/ I 503.3/ I 503.4/ I, II 503.5/ I

Solar Radiation 505.1/ I 505.2/ I 505.3/ I 505.4/ I 505.5/ I

Rain 506.1/ I, II 506.2/ I, II 506.3/ I, II 506.4/ I, III 506.5/ I, III


Humidity 507.1/ I, II 507.2/ II, III 507.3/ II, III 507.4 507.5/ II

Salt Fog 509.1/ I 509.2/ I 509.3/ I 509.4 509.5

Dust 510.1/ I 510.2/ I 510.3/ I 510.4/ I, III 510.5/ I

Vibration 514.2/ VIII, X 514.3/ I 514.4/ I 514.5/ I 514.6/ I

Shock 516.2/ I, II, V 516.3/ I, IV 516.4/ I, IV 516.5/ I, IV 516.6/ I, IV

Immersion - - - 512.4/I 512.5/I

Bradley Hibben Radio Engineer 1 DOT Radio Operations Center Office of Statewide Radio Communications 651-234-7892 [email protected] Statewide Emergency Communications Board Operations and Technical Committee February 1, 2017, 2017 Re: ARMER System Subscriber Radio Testing Testing of the following radios for use on the ARMER System was completed January 31, 2017, using the “Subscriber Unit Test Procedure” dated March 2010: Harris XL-200 portable, S/N A40300000305 Harris XG-25 portable, S/N A40137004270 The testing was performed by the following individuals: Thomas Bredemus, MnDot Bradley Hibben, MnDot Thomas Kaisler, MnDot The radios passed all the required tests for use on the ARMER Network. Non-required tests the radios failed:

1) Both radios failed test “Trunking Test”, 6A, page 11, “Emergency Alarm/Call with Tactical operation. However, per ARMER Standards, this mode of operation would not be used on the system.

2) Neither radio was able to place Phone interconnect calls, but they would receive them. “Features Testing”, tests 4A and 4B, pages 19-20

3) Neither radio will operate in “Failsoft”. “System Failure Mode Testing”, tests 2 and 3, test page 30. When a site enters “Failsoft” the radios immediately start searching for a site in wide area operation.

4) The XG-25 did not operate with encryption. Although the code-plug could be programed for encrypted operation, the key loading operation did not function. “Features Testing”, test 3, pages 18 and 19, and test 9, pages 23 and 24

5) The XG-25 was able to make Multi-Group calls and receive them, however it would not talk back to the Multi-group. “Trunking Tests”, 5B Page 10. Note: Both radios would receive the MG call, regardless of the setting in the code-plug for the TG being part of a multi-group.

Bradley Hibben


ARMER Acceptance Test Checklist Harris XG-25P, S/N A40137004270, Test ID 100095





RPM, Rev 13, Windows server 2008 and Windows 7

Pass

No


Pass

No


Readable through the display on the radio. “Revision” menu.

R00.20.0040

Pass

No


License for S/W. Hardware USB dongle for programming. Master system

key for programming subscriber ASK’s

Pass

No


Pass

No


.PRS Files Pass

No

1



Pass

No


Serial Data Port

Pass

No


Select Program with override to change ID number

Pass

No


Displays “INVALID RADIO ID”, cannot initiate calls

Pass

No






Briefly indicates “Denied”, then immediately retries approximately every ½ second until PTT is released. Cannot make TG calls, will receive calls even

when attempting to make a denied call.

Pass

Yes

2







Pass

1 Note

2 Note

3 Note

4 Note

5 Note

6 Note

3






Registered with City Center on TG-A and TG-B

Pass

Yes


De-registers when powered down.

Pass

No


2 seconds to switch to TG-D at Anoka

Pass

Yes


Updates to MG-ABC

Pass

Yes

4


Trunking Tests




TX & RX on selected TG only.

Pass

Yes


Will not TX on calls in progress

Pass

Yes


Updated to new TG and receives in progress call

Pass

No


Initiates MG call and receives talkback audio.

Pass

No


Receives MG call but cannot talk back.

Fail

No

5



Not programmable- Talk group revert only. Tactical operation not allowed

on the ARMER network

Fail/NA

No


Programmable switch delay, 1 button clear

Pass

No


Displays call list alias if programmed into radio call list, otherwise the radio

ID is displayed

Pass

No





Displays in RCM and Zone Watch

Pass

No


Pass

No


Pass

Yes

6



Pass

No

Features Testing




Pass

No


Pass

No


“Add” key allows user to change the scan priority to 1,2, or 3

Pass

No


Individual TG’s set for receive only.

Pass

No


Fail

No


“Denied” on Display

Fail

No

7



Fail

No


Will receive calls

Pass

No


Pass

No


Sends and receives private calls

Pass

No


Pass

No


Pass

No


Fail

No

8


Radio Roaming Tests




Roamed to Anoka on TG-D from City Center on TG-E

Pass

Yes


Roamed to Henn E on TG-F from Anoka on TG-D

Pass

No


Sent and received pages @ City Center on TG-E and Anoka on TG-D

Pass

Yes


Solid affiliation to Hastings by Keats Ave on HWY 36

Pass

Yes

9






SOA-2, Power 2.94 W, Mod Fidelity 0.8%, Frequency 853.9376 MHZ (+100hz), Squelch breaks at -125 dbm, Audio clear @ -121.5 dbm

8CALL90R, Power 2.5 W, Frequency 806.12495 Deviation 4.35 khz, Squelch breaks @ 122.8 dbm, Clear @ - 120 dbm with some static

Pass

Yes


Pass

No


Pass

No

10


Trunking Tests


Displays “Queued”

Pass

No





Displays “F” for site trunking, cannot manually force a site move

Pass

Yes


Radio will not operate in “Failsoft”

Fail

No


Radio will not operate in “Failsoft”, roams immediately when site changes to

“Failsoft”

Fail

No

Radio Roaming Tests


Radio moves immediately in “Failsoft” and moves via preference table when site goes into “Site Trunking”

Pass

Yes

11


Audio Quality Test




Clear audio 4.5

Pass

No

12

ARMER Acceptance Test Checklist Harris XL-200, S/N A40300000305, Test ID 104956





Uses RPM 2, Windows XP, Server 2003, Windows 7

Pass

No


Reads radio as expected. Pass

No


S/W reads S/N and radio s/w version upon connection to radio.

R02A28

Pass

No


License for S/W. Hardware USB dongle to allow radio programming.

Master key to allow programming dongles for subscriber programming.

Pass

No


Pass

No


Files saved as .PRS files

Pass

No

1



Saved files can be loaded to radio. Pass

No


Pass

No


File can be saved with new ID or radios can be programmed with override function.

Pass

No


Radio indicates “INVALID ID” Pass

No






Radio indicates “INVALID UNIT” Pass

Yes

2







Pass

1 Note

2 Note

3 Note

4 Note

5 Note

6 Note

3






City Center & TG-A

Pass

Yes


De-registers when powered down

Pass

No


3 seconds to move to TG-D at Anoka

Pass

Yes


Displays MG-ABC

Pass

Yes

4


Trunking Tests




TX & RX on selected TG only.

Pass

Yes


Will not TX on in progress calls and emits a single tone when attempted.

Pass

Yes


Updates to new TG and receives in progress calls.

Pass

No


Initiates multi-group TG-Calls and receives talkback audio

Pass

No


Receives MG calls and can talk back to MG

Pass

No

5



Radio cannot be programmed with “Tactical” Emergency operation. A Emergency TG must be programmed.

Note: Tactical operation is not allowed on the ARMER network.

N/A Fail

No


Revert operation normal.

Pass

No


Displays ID of radio declaring emergency if it is not programmed into call list, otherwise it will display the programmed alias.

Pass

No





Displays in RCM and Zone Watch Pass

No


Display shows the TG the radio was regrouped to.

Pass

No


Operation as expected

Pass

Yes

6



Operation as expected.

Pass

No

Features Testing




Pass

No


Pass

No


Options menu to change priority after adding to scan list

Pass

No


Channels/TG’s can be receive only.

Pass

No


Will accept multiple keys. Radio does not indicate complete on key load,

shows load in progress.

Pass

No


Not programmable for telephone interconnect. Phone list can be programmed, however there is no way to make a call from

the radio.

Fail

No

7



Not programmable for telephone interconnect calling

Fail

No


Will receive calls

Pass

No


Key pad and call list

Pass

No


Sends and receives private calls

Pass

No


8CALL90D, 8TAC91D

Pass

No


SOA 2

Pass

No


Pass

No

8


Radio Roaming Tests




Roamed to Anoka from City Center when switched to TG-D from TG-E

Pass

Yes


Roamed to Henn E on TG

Pass

No


Sent and received calls and pages @ City Center on TG-E and Anoka on TG-D

Pass

Yes


Solidly affiliated to Hastings by Keats Ave & HWY 36

Pass

Yes

9






SOA-2 : Power 2.74w, 853.937538 (+38hz), Mod fidelity 0.8% Squelch breaks @ -122, audio clear @ -118 (0.28uV)

8CALL90D: Power 2.74 Watts, 3.74 Khz deviation, squelch breaks @ 0.19 uV, audio clear @ .3 uV

Pass

Yes


Pass

No


Pass

No

10


Trunking Tests


Displays “Call Queued

Pass

No





Displays and antenna tower with an !. Does not show site number and cannot

manually move to another site.

Pass

Yes


Radio does not operate in “Failsoft”

Fail

No


Radio does not operate in “Failsoft” Fail

No

Radio Roaming Tests


Moves immediately in “Failsoft” based on programmed site preference table.

Pass

Yes

11


Audio Quality Test




Good quality audio, 4.5.

Pass

No

12

Harris and assuredcommunications are registered trademarks of Harris Corporation.

Trademarks and tradenames are the property of their respective companies. Copyright © 2014 Harris Corporation All rights reserved. 02/14 ECR-7906P

Public Safety and Professional Communications 221 Jefferson Ridge Parkway Lynchburg, VA 24501 USA 1-800-368-3277 (+1-434-455-6403) www.pspc.harris.com

harris.com harris.com

The XG-25P meets the challenge. Armed with Bluetooth® functio-nality and ready for operation in the narrowband frequencies, the XG-25P is the economical solution for those who seek out the best in radio value. The XG-25P accomplishes this without sacri-ficing the functionality that is expected from a Harris radio in the XG family: exceptional audio in a rugged and lightweight design.

Standard features found on the XG-25P include:

AMBE+2™ Vocoder – enhances audio quality

Lightweight Design – does not weigh down a user with its total weight of 15 ounces (including Lithium Ion battery)

Rugged for Field Use – meets MIL standard for durability

Optional features include: Bluetooth Functionality – avoid troubles with corded

microphones

Factory Mutual Intrinsically Safe – for operation in hazardous conditions when paired with an Intrinsically Safe battery and other accessories

Available in both System and Scan models, the XG-25P offers a full complement of accessories to suit a variety of user needs.

SCAN SYSTEM

XG-25P: The Feature-rich and Economical Solution for Narrowband P25 Performance

XG-25P Portable VHF, UHF, 700/800 MHz

WHEN COMMUNICATION AND PERFORMANCE MATTER

ACCESSORIES

FUTURE READY The XG-25P is an economical investment that agencies can rely on as transitions occur to P25 technology. The portable supports P25 conventional and trunked operation, wideband and narrowband channels, and its software-defined architecture allows field upgrading to operating modes such as P25 Phase 2.

SUPERIOR AUDIO EXPERIENCE The XG-25P delivers the exceptional audio that users have grown to expect from Harris. The large speaker provides extremely powerful audio, and the AMBE+2 vocoder optimizes the quality of communications. The vocoder also controls distortion that may occur from shouting into the microphone. Through the combination of an oversized speaker and the AMBE+2 vocoder, the XG-25P provides one of the best audio experiences available.

BLUETOOTH READY The XG-25P delivers Bluetooth functionality for a wireless interface to selected accessories. Bluetooth provides freedom of movement with no protruding parts or cumbersome wires or cables, allowing users the flexibility to operate without corded microphones or programming cables if desired.

LIGHTWEIGHT AND ERGONOMIC DESIGN The XG-25P is one of the lightest radios in the Harris portfolio, weighing 15 ounces with the Lithium Ion battery. From the keypad buttons to the battery, each aspect of the radio has been developed to provide a better user experience. The knobs and buttons of the XG-25P have been designed to be strong enough to avoid incidental changes while still being easily managed by users wearing heavy gloves. The XG-25P is simple to operate so users may focus attention on the task rather than on radio operation.

The XG-25P operates with a wide range of Harris accessories. Several of the newest accessories are shown below.

The 3600 mAH Lithium Polymer battery is the highest capacity Harris battery for single-band radios. Offering the ultimate in performance and ease of use, the battery has an average 16-hour shift life, 400 charge cycles, and maintenance-free Lithium battery technology. With its IP67 rating for immersion and dust/dirt particle intrusion, the battery is ideal for public safety, commercial and industrial, and utility applications. The Wireless Bluetooth Remote Speaker Microphone (RSM) affords XG-25P users the capability to add an RSM to their system wirelessly. This Class 2 device, with a 10-meter wireless range, employs Secure Simple Pairing and encryption and contains a Lithium rechargeable battery with a 12-hour shift life. The compact design includes volume control buttons, a dedicated Emergency button, PTT button, Pairing and Power buttons, a 2.5-mm audio jack for earpiece accesso-ries, and a ruggedized lapel clip for secure attachment to clothing. The Standard Speaker Microphone includes a two-position volume control setting, emergency button, rubber PTT, and earphone jack in a compact yet highly functional design. A clothing clip that rotates a full 360 degrees provides complete accessibility. With construction that complies with MIL standard specifications, this speaker microphone meets the needs of a wide range of users.

GENERAL SPECIFICATIONS XG-25P Portables are available in 2 models: System: With dot matrix LCD and

DTMF keypad Scan: With dot matrix LCD and

limited keypad Dimensions (H x W x D): (Without Knobs and Antenna)

With battery: 5.89 x 2.44 x 1.85 in. (149.6 x 62.0 x 47.0 mm) Weight (with Battery & Antenna): Li-Ion: 15.0 oz (425g) Li-Polymer: 16.4 oz (465g) NiMH: 18.8 oz (533g) Input Voltage: 7.5 VDC (nominal) Vibration: 5 G (per U.S. Forest Service) Shock: 1 meter drop (per TIA-603-C) Battery Life (at 5% Tx, 5% Rx, and 90% standby): Li-Ion: 8 hours (2000 mAH) Li-Polymer: 16 hours (3600 mAH) NiMH: 10 hours (2400 mAH) Operating Temperature Range: Li-Ion: +14 to +140°F (-10 to +60°C) Li-Polymer: -4 to +140°F (-20 to +60°C) NiMH: -4 to +140°F (-20 to +60°C) Relative Humidity: 90% @ 122°F (+50°C) Altitude: Operational: 15,000 ft

(4,572 m) In Transit: 50,000 ft (15,240 m)

Color (case): Black Options and Accessories

Headset, earpiece, speaker microphones, PC programming software and cables, subminia-ture surveillance accessories, antennas, cases, straps, belt loops and swivel mounts, desk chargers, and wall chargers.

Intrinsically Safe Options* Factory Mutual Intrinsically Safe for Class I, II, and III, Division 1, Groups C, D, E, F, and G, Temp T3C, TA=+60C; Nonincendive for Class I, Division 2, Groups A, B, C, and D, Temp T4, TA=+60C. *For VHF only

RoHS compliant

TRANSMITTER TYPICAL PERFORMANCE SPECIFICATIONS VHF UHF 700/800Frequency Range (MHz): 136-174 378-470 764-776, 794-805, 806-825, 851-870Rated RF Power (W): 1.0-5.0 5 3 Frequency Stability (-30 to +60°C; +25°C Ref) (ppm): 1.5 1.5 1.5 Frequency Separation (MHz): 38 (full bandwidth) 92 (full bandwidth) NA Modulation Deviation (kHz): 5.0 (wideband*)

2.5 (narrowband) 5.0 (wideband*) 2.5 (narrowband)

2.5, 4, or 5 FM

FM Hum and Noise (Companion Receiver) (dB): 49 (wideband*) 45 (narrowband)

49 (wideband*) 44 (narrowband)

44 (700 MHz) 47 (800 MHz NPSPAC) 48 (800 MHz non-NPSPAC)

Spurious and Harmonics (dBm/dBc): -42/-80 -36/73 -55/90 Audio Response (dB): +1/-3 +1/-3 Meets TIA-603-C Section 3.2.6 Audio Distortion (1 kHz tone): @ 3 kHz deviation: @ 2.4 kHz deviation: @1.5 kHz deviation:

1% (wideband*) NA 1% (narrowband)

1% (wideband*) NA 1% (narrowband)

1% (800 MHz non-NPSPAC) 1% (800 MHz NPSPAC) 1% (700 MHz)

Project 25 Modulation Fidelity (%): 5 1.5 1 Project 25 Adjacent Channel Power (dBc): 73 67 73 *VHF and UHF product is compliant with applicable FCC narrowbanding mandate below 512 MHz.

RECEIVER TYPICAL PERFORMANCE SPECIFICATIONS VHF UHF 700/800Frequency Range (MHz): 136-174 378-470 764-776, 851-870 Frequency Separation (MHz): 38 (full bandwidth) 92 (full bandwidth) NA Channel Spacing (kHz): 25 (wideband*)

12.5 (narrowband) 25 (wideband*) 12.5 (narrowband)

12.5, 25, PLL Step

Frequency Stability (-30 to +60°C: +25°C Ref) (ppm): 1.5 1.5 1.5 Sensitivity (12 dB SINAD) (V/dBm): 0.25/-119.0 (wideband*)

0.30/-117.5 (narrowband)0.25/-119.0 (wideband*)0.30/-117.5 (narrowband)

0.21/-120.5 (700 MHz) 0.18/-122.0 (800 MHz NPSPAC) 0.19/-121.5 (800 MHz non-NPSPAC)

Project 25 Adjacent Channel Rejection @12.5 kHz (dB): 63 62 64 Offset Channel Selectivity@ NPSPAC (dB): NA NA 33 Selectivity @ 12.5 kHz (dB): @ 15 kHz (dB): @ 25 kHz (dB):

60 60 75

60 NA 72

NA 62 (700 MHz) 72 (800 MHz non-NSPPAC)

Intermodulation (dB): 70 75 72 Spurious and Image Rejection (dB): 75 73 72 FM Hum and Noise (dB): 45 (wideband*)

40 (narrowband) 54 (wideband*) 48 (narrowband)

45 (700 MHz), 50 (800 MHz NPSPAC)50 (800 MHz non-NPSPAC)

Rated Audio Output (mW): 500 500 500 Audio Distortion: 1% @ rated power 1% @ rated power 1% @ rated audio output power Project 25 Reference Sensitivity @ 5% BER (V/dBm): 0.22/-120.0 0.22/-120.0 0.22/-120.0 *VHF and UHF product is compliant with applicable FCC narrowbanding mandate below 512 MHz.

ENVIRONMENTAL SPECIFICATIONS STANDARD PARAMETER METHODS & PROCEDURESMIL-STD-810G* Low Pressure 500.5/1,2 High Temperature 501.5/1,2 Low Temperature 502.5/1,2 Temperature Shock 503.5/1 Contamination by Fluids 504.1/2 Solar Radiation 505.5/2 Blowing Rain 506.6/1 Humidity 507.4 Salt Fog 509.5 Blowing Dust 510.5/1 Blowing Sand 510.5/2 Vibration (Minimum Integrity) 514.6/1, Category 24 Vibration (Basic Transportation) 514.6/1, Category 4 Shock (Functional/Basic) 516.6/1 Shock (Transit Drop) 516.6/4 IEC 60529 Dust-tight, Powerful Water Jets IP66 U.S. Forest Service Vibration (10-60 Hz) USDA LMR Standard, Section 2.15 TIA-603-C Shock (1 meter drop) Paragraph 3.3.5.3 *Also meets equivalent superseded MIL-STD-810D, -E, and -F.

DIGITAL OPERATION PROTOCOL PROVOICE™ P25Vocoding Method: AMBE+2™ Enhanced Full Rate AMBE+2 Enhanced Full Rate & Enhanced Half Rate Signaling Rate (kbps): 9.6 9.6 Modulation: GFSK WCQPSK & C4FM Encryption Algorithms: AES (FIPS-140-2 certified) & DES AES (FIPS-140-2 certified) & DES

REGULATORY DATA FREQUENCY RANGE (MHz)

RF OUTPUT (W)

FREQUENCY STABILITY (ppm)

FCC TYPE ACCEPTANCE NUMBER

APPLICABLE FCC RULES

INDUSTRY CANADA CERTIFICATION NUMBER

APPLICABLE INDUSTRY CANADA RULES

NTIA CERTIFICATION NUMBER

136-174 5.0 1.5 OWDTR-0072-E 22, 80, 90 3636B-0072 RSS-119, RSS-210 J/F 12/10038 378-470 5.0 1.5 OWDTR-0109-E 22, 80, 90 3636B-0109 RSS-119, RSS-210 J/F 12/10038 769-869 3.0 1.5 OWDTR-0073-E 90 3636B-0073 RSS-119, RSS-210 NA

Technical specifications are subject to change without notice. Product sales are subject to applicable U.S. export control laws.

RUGGED AND FEATURE-RICH PORTABLE RADIO

Harris and assuredcommunications are registered trademarks of Harris Corporation.

Trademarks and tradenames are the property of their respective companies. Copyright © 2014 Harris Corporation All rights reserved. 02/14 ECR-7906P

Public Safety and Professional Communications 221 Jefferson Ridge Parkway Lynchburg, VA 24501 USA 1-800-368-3277 (+1-434-455-6403) www.pspc.harris.com

harris.com harris.com

The XG-25P meets the challenge. Armed with Bluetooth® functio-nality and ready for operation in the narrowband frequencies, the XG-25P is the economical solution for those who seek out the best in radio value. The XG-25P accomplishes this without sacri-ficing the functionality that is expected from a Harris radio in the XG family: exceptional audio in a rugged and lightweight design.

Standard features found on the XG-25P include:

AMBE+2™ Vocoder – enhances audio quality

Lightweight Design – does not weigh down a user with its total weight of 15 ounces (including Lithium Ion battery)

Rugged for Field Use – meets MIL standard for durability

Optional features include: Bluetooth Functionality – avoid troubles with corded

microphones

Factory Mutual Intrinsically Safe – for operation in hazardous conditions when paired with an Intrinsically Safe battery and other accessories

Available in both System and Scan models, the XG-25P offers a full complement of accessories to suit a variety of user needs.

SCAN SYSTEM

XG-25P: The Feature-rich and Economical Solution for Narrowband P25 Performance

XG-25P Portable VHF, UHF, 700/800 MHz

WHEN COMMUNICATION AND PERFORMANCE MATTER

XL-200P PORTABLEFULL-SPECTRUM MULTIBAND The XL-200P is Harris’ second generation full-spectrum radio. Every radio is capable of operating on VHF, UHF, and 700/800 MHz frequencies, as well as providing voice and data over LTE broadband. Users may purchase the porta-ble as single band, dual band, or full spectrum, and upgrade to add bands or LTE in the future.

EXCEPTIONALCOMMUNICATIONS IN SEVERE CONDITIONS

PARAGRAPH HEADING

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit. adipiscing elit,sed do eiusmod tempor incididunt

ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit. Excepteur sint occaecat cupidatat non lorem dolore.

Benefits/Facts list, lorem ipsum dolor sitamet, consectetur adipiscing elit

Incididunt ut labore et dolore magnaaliqua Ut enim ad minim

Nostrud exercitation ullamco laboris nisi utaliquip ex consequat

FEATURES

PARAGRAPH HEADING

Body Text consectetur adipiscing elit,sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Utenim ad minim veniam, quis nostrudexercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Paragraph Subhead • Bullet #1 Text

– Secondary Bullet #2 Text

› Tertiary Bullet #3 Text PARAGRAPH HEADING

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit. adipiscing elit, sed do eiusmod tempor incididunt ut labore et doloremagna aliqua. Ut enim ad minim veniam, quis nostrud

exercitation ullamco laboris nisi utaliquip ex ea commodo consequat. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit. PARAGRAPH HEADING

Paragraph Subhead • Bullet #1 Text


› Tertiary Bullet #3 Text PARAGRAPH HEADING Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

Benefits/Facts list, lorem ipsum dolor sit amet, consectetur adipiscing elit

Incididunt ut labore et dolore magna aliqua Ut enim ad minim

Nostrud exercitation ullamco laboris nisi ut aliquip ex consequat

SAMPLE TABLE

About Harris Corporation

Harris Corporation is a leading technology innovator that creates mission-critical solutions that connect, inform and protect the world. The company’s advanced technology provides information and insight to customers operatingin demanding environments–from ocean to orbit and everywhere in between. Harris has approximately $7.5 billion in annualized revenue and supports customers in more than 100 countries through four customer-focused business segments: Critical Networks, Space and Intelligence Systems, Electronic Systems and Communication Systems.

Harris is a registered trademark Harris Corporation. Trademarks and trade names are the property of their respective companies. © 2016 Harris Corporation 10/16 CS-PSPC ECR-8093S

Non-Export Controlled Information

* In Brazil, these options are not available.

Instant recall of received audio replays re-ceived transmissions to avoid missed calls.

Wi-Fi® connectivity allows voice delivery outside the radio coverage area using the Harris BeOn® application. Also, the op-tional cell modem provides voice and data wherever cellular/LTE is available.

Built-in GPS, Bluetooth®, Active Noise Cancel-lation, and 4-position A-B-C-D switch standard.

Unique user interface with two displays and innovative features such as Visual Zone identi-fication (color coding of talkgroups) to make radio operation simple and intuitive.

DESIGNED FROM THE GROUND UP TO CONVERGE VOICE AND DATA

Designed with input from mission-critical users, the XL-200P is an entirely new radio platform – processor, memory, and software – that merges robust LMR voice with unique-in-the-industry voice and data over cellular/LTE/Wi-Fi to provide leading-edge connectivity.

AUDIO EXCELLENCE

The new design pairs a powerful 1.5W audio amplifier with woofer and tweeter speakers (with resonant cavities and tuned ports) to conquer noise and deliver industry-leading clear and intelli-gible audio.

COMPACT AND ERGONOMIC ALL BAND + LTE RADIO

The shape of the XL-200P was based on extensive human factors research to create a radio that nestles naturally in users’ hands. Controls are shaped and arranged for ease of use and optimum performance, including accessory connections.

TOUGH MECHANICAL PACKAGE

With a rugged cast aluminum frame and tough seals, the XL-200P is constructed to operate in severe environments. This radio meets MIL-STD-810G for durability, including Method 511.5 for explosive atmospheres and Method 504.1 for con-tamination by fluids, so the radio can be scrubbed with cleansers and biological sanitizers.

ACCESSORIES

The XL-200P is available with a selection of dependable Harris accessories that operate in a range of environments. Several are shown below.

Headsets The XL-200P can be used with a wide variety of headsets and covert audio accessories to provide a complete user-gear solution for the industrial, public safety, utility, and transportation markets. Heavy-duty and lightweight headsets are available with in-ear or over-the-ear hearing protection, flexible boom microphones with noise-reduction technology, and standard or remote PTTs. In addition, the XL-200P can be used with Bone Con-ducting Skull Headsets and Throat Microphone/Headset Kits. Covert audio kits are available in black or beige, and in 2-wire or 3-wire configura-tions with earpiece, microphone, and PTT.

Tactical Headset 3-Wire Mini-Lapel Microphone

Carrying Cases Harris offers a versatile line of carrying cases for the XL-200P full-spectrum multiband radio. Options include a standard belt clip and premium belt loop, both of which afford the radio user a low-profile, integrated carrying option. In addition, a premium leather holster is available for attaching to a belt or wearing with the premium leather shoulder strap.

Leather Carrying Case

Chargers Harris offers a variety of chargers for the XL-200P: Single-Bay, Multi-Bay, and a Vehicular Charger for in-car charging. The chargers are designed to quickly and safely charge battery packs in approximately 1 to 4 hours.

Single-Bay Charger Multi-Bay Charger* Vehicular Charger*

Additional Accessories Available Bluetooth speaker microphones, Bluetooth covert earpieces, standard speaker microphones, Lithium Ion battery, PC programming software and cables, other subminiature surveillance accessories, and antennas.

Belt Clip

• Bullet #1 Text • Bullet #1 Text • Bullet #1 Text • Bullet #1 Text • Bullet #1 Text • Bullet #1 Text

GENERAL SPECIFICATIONS SAMPLE TABLE 1

PARAGRAPH HEADING Body Text consectetur adipiscing elit,sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Utenim ad minim veniam, quis nostrudexercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Paragraph Subhead • Bullet #1 Text



Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Excepteur sint occaecat cupidatat nonproident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit. adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.





ENVIRONMENTAL SPECIFICATIONS

STANDARD PARAMETER METHODS & PROCEDURES MIL-STD-801G Vibration 514.6 PI, CAT 4 & 24 Shock 516.6 PI, IV, V, & VI Solar Radiation 505.5 PI Low Temperature 502.5 PI & II High Temperature 501.5 PI & II Temperature Shock 503.4 Humidity 507.5 PI & II Low Pressure 500.5 PI

GENERAL SPECIFICATIONS

Radio Models Full Keypad: TFT LCD w/DTMF keypad, Nav cluster, Soft Keys Partial Keypad: TFT LCD w/partial keypad, Nav cluster, Soft Keys

Dimensions (Without Knobs and Antenna) Inches (w/Battery) Millimeters (w/Battery) Height: 5.8 148 Width: 2.3 60 Depth: 1.4 36

Weight Ounces Ounces Grams Grams

(w/o Bat & Ant) (w/Bat & Ant) (w/o Bat & Ant) (w/Bat & Ant)

Radio: 10.4 16.2 296 464

Housing Colors Midnight Black High-Visibility Yellow

Interfaces Front Display: 320 x 178 pixels, 1.8 in. transflective LCD,

16-bit color with backlight Top Display: 128 x 32 pixels, 1.1 in. multi-color

backlight, sunlight readable Keypad: Backlight, 3 soft keys, 5-way navigation

key, 4 x 3 keypad Buttons: Large PTT button, on/off knob, volume

knob, red emergency button, 16-position top-mounted rotary knob, 2-position concentric switch, 4-position toggle switch, 3 programmable side buttons

Tx/Rx Indicator: Multi-colored LEDs

Transceiver Supported Bands: VHF & UHF & 700/800 MHz & LTE Channel Capacity: 12,500 (1,250 per mission plan)

Environmental Specifications Relative Humidity: 5% @ 140°F (+60°C), 95% @ 122°F (+50°C) Vibration: USDA LMR Standard, Section 2.15 &

MIL-STD-810G, Test Method 514.6 Drop Shock: 1.0 meter drop to concrete (exceeds TIA-603-D)Immersion*: 2 meters for 4 hours in accordance with

MIL-STD-810G/IP68 *Optional feature

°F °C Operating Temperature*: -22 to +140 -30 to +60 *Extreme low temperatures adversely affect battery life

°F °C Storage Temperature*: -40 to +176 -40 to +80 *Store batteries at +25°C ± 5°C

Altitude Feet Meters Operational: 15,000 4,572 In Transit: 50,000 15,240 Electrical Input Voltage: 7.5 VDC (nominal) GPS/GNSS Specifications Channels: 52 Tracking Sensitivity: -166 dBm (GPS)

-163 dBm (GLONASS)Acquisition Sensitivity: -146 dBm (GPS) Cold Start w/-130 dBm input: <35 seconds Hot Start w/-130 dBm input: <1 second Safety Hazardous Location Options: Approved for use in the U.S. and Canada in Class I, Division 2, Groups A, B, C, and D hazardous locations RoHS compliant

LMR TRANSMITTER

Typical Performance Specifications Full-Spectrum Multiband* Frequency Range (MHz) Option 1 (U.S.):

Option 2 (International): 136-174, 378-522, 768-776, 798-806, 806-816, 851-861136-174, 378-522, 763-776, 793-806, 806-825, 851-870**

Rated RF Power (W): VHF: 1-6, UHF: 1-5, 700/800: 0.5-3 Rated RF Power Talkaround (W): VHF: 1-6, UHF: 1-5, 700/800: 0.5-3 Frequency Stability (-30 to +60°C) (ppm): 1.0 Modulation Limiting (kHz): 2.5, 4, 5 (FM) Audio Response (dB): +1/-3 Spurious and Harmonics (dBc): -80, FCC Part 90 FM Hum and Noise@25 kHz (dB): @12.5 kHz (dB):

VHF: 70, UHF: 60, 700/800: 55 VHF: 47, UHF: 47, 700/800: 45

Audio Distortion (%): <1.25 Project 25 Modulation Fidelity (%): 1.0 Project 25 Adjacent Channel Power (dBc): >71

*VHF and UHF product is compliant with applicable FCC narrowbanding mandate below 512 MHz. **Future option

REGULATORY DATA

Frequency Range (MHz)

RF Output (W)

Frequency Stability (ppm)

FCC Type Acceptance Number

Applicable FCC Rules

Industry Canada Certification Number

Applicable Industry Canada Rules

NTIA Certification Number

136-174 6.0 1.0 OWDTR-0133-E 22, 74, 80, 90 3636B-0133 RSS-119 SPS-217 49/1378-522 5.0 1.0 OWDTR-0133-E 22, 74, 80, 90 3636B-0133 RSS-119 SPS-217 49/1768-776 3.0 1.0 OWDTR-0133-E 90 3636B-0133 RSS-119 798-806 3.0 1.0 OWDTR-0133-E 90 3636B-0133 RSS-119 806-816 3.0 1.0 OWDTR-0133-E 90 3636B-0133 RSS-119 851-861 3.0 1.0 OWDTR-0133-E 90 3636B-0133 RSS-119 2402-2480 0.2 TBD OWDTR-0133-E 15 3636B-0133 RSS-119 5180-5825 0.1 TBD OWDTR-0133-E 15 3636B-0133 RSS-119


LMR RECEIVER

Typical Performance Specifications Full-Spectrum Multiband*Frequency Range (MHz) Option 1 (U.S.):

Option 2 (International): 136-174, 378-522, 768-776, 851-861136-174, 378-522, 763-776, 851-870**

Channel Spacing (kHz): 25 (wideband*), 12.5 (narrowband), 6.25 equiv (TDMA P25 Phase 2)Frequency Stability (-30 to +60°C) (ppm): 1.0 Sensitivity (12 dB SINAD) (dBm): VHF: -122, UHF:-121, 700: -121, 800: 120Project 25 Reference Sensitivity @ 5% BER (dBm): VHF: -122, UHF:-121, 700/800: -120.5Analog Selectivity @ 25 kHz (dB): @ 12.5 kHz (dB):

VHF: 77, UHF: 77, 700/800: 74VHF: 71, UHF: 70, 700/800: 64

P25 Adjacent Channel Rejection @ 12.5 kHz (dB): VHF: 66.2, UHF: 62.2, 700/800: 62.0Intermodulation (dB): VHF: 80, UHF: 81, 700/800: 78Spurious and Image Rejection (dB): VHF: 90, UHF: 87, 700: 84, 800: 80FM Hum and Noise @ 25 kHz (dB): @12.5 kHz (dB):

VHF: -60, UHF: -60, 700/800: -55VHF: -55, UHF: -53, 700/800: -50

Rated/Max. Audio Output (mW): 1500/4000 Audio Distortion: 1.1% @ rated power *VHF and UHF product is compliant with applicable FCC narrowbanding mandate below 512 MHz.**Future option

ENVIRONMENTAL STANDARDS

Standard Parameter Methods Procedures/CategoriesMIL-STD-810G* Low Pressure 500.5 1,2

High Temperature 501.5 1,2Low Temperature 502.5 1,2Temperature Shock 503.5 1Solar Radiation 505.5 1Contamination by Fluids 504.1 2Rain 506.5 1,3Humidity 507.5 2Salt Fog 509.5 1Blowing Dust & Sand 510.5 1,2Explosive Atmosphere 511.5 1Immersion** 512.5 1Vibration (Minimum Integrity) 514.6 1, Category 24Vibration (Basic Transportation) 514.6 1, Category 4Shock (Functional/Basic) 516.6 1Shock (Transit Drop) 516.6 4Shock (Bench Handling) 516.6 6

IEC 60529 Dust-tight, Continuous Immersion** IP68 *Also meets equivalent superseded MIL-STD-810D, -E, and -F. **Optional feature.

CELLULAR BROADBAND

LTE Protocol: 3GPP Release 9, Power Class 3 UE with RX diversity*Public Safety Broadband: Band 14, 788-798 MHz TX, 758-768 MHz RX, 5 or 10 MHz BW*

Commercial Broadband: Band 13, 777-787 MHz TX, 746-756 MHz RX, 5 or 10 MHz BW*

Commercial Broadband: Band 4, 1710-1755 MHz TX, 2110-2155 MHz RX, 5, 10, 15, or 20 MHz BW*

Wi-Fi: 802.11b/g/n 2.4 GHz & 5 GHz Bluetooth: Bluetooth 4.0 *Future option

DIGITAL OPERATION

Protocol ProVoice™* P25Vocoding Method: AMBE + 2™ Enhanced Full Rate AMBE + 2 Enhanced Full Rate & Enhanced Half Rate Signaling Rate (kbps): 9.6 9.6 Modulation: GFSK Phase1 TX: C4FM, RX: C4FM & WCQPSK

Phase 2 TX: HCPM, RX: WCQPSK *Future option

ENCRYPTION

Encryption Algorithms: AES, DES-OFB Encryption Keys per Radio: Capable of storing 128 keys (64 AES, 64 DES) Keying: Harris Key Loader, Over-the-Air Rekeying (OTAR), Motorola KVL 3000+/4000 Standards: FIPS 140-2, FIPS 197

BATTERIES

Type Dimensions (L x W x D) Weight Capacity (mAh) Li-Ion 3.0 x 2.3 x 0.9 in. 4.8 oz (136g) 3100

XL-200P PORTABLEFULL-SPECTRUM MULTIBAND The XL-200P is Harris’ second generation full-spectrum radio. Every radio is capable of operating on VHF, UHF, and 700/800 MHz frequencies, as well as providing voice and data over LTE broadband. Users may purchase the porta-ble as single band, dual band, or full spectrum, and upgrade to add bands or LTE in the future.

EXCEPTIONALCOMMUNICATIONS IN SEVERE CONDITIONS

PARAGRAPH HEADING

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit. adipiscing elit,sed do eiusmod tempor incididunt

ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit. Excepteur sint occaecat cupidatat non lorem dolore.

Benefits/Facts list, lorem ipsum dolor sitamet, consectetur adipiscing elit

Incididunt ut labore et dolore magnaaliqua Ut enim ad minim

Nostrud exercitation ullamco laboris nisi utaliquip ex consequat

FEATURES

PARAGRAPH HEADING

Body Text consectetur adipiscing elit,sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Utenim ad minim veniam, quis nostrudexercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Paragraph Subhead • Bullet #1 Text



Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. Lorem ipsum dolor sit. adipiscing elit, sed do eiusmod tempor incididunt ut labore et doloremagna aliqua. Ut enim ad minim veniam, quis nostrud





Benefits/Facts list, lorem ipsum dolor sit amet, consectetur adipiscing elit

Incididunt ut labore et dolore magna aliqua Ut enim ad minim

Nostrud exercitation ullamco laboris nisi ut aliquip ex consequat

SAMPLE TABLE

About Harris Corporation

Harris Corporation is a leading technology innovator that creates mission-critical solutions that connect, inform and protect the world. The company’s advanced technology provides information and insight to customers operatingin demanding environments–from ocean to orbit and everywhere in between. Harris has approximately $7.5 billion in annualized revenue and supports customers in more than 100 countries through four customer-focused business segments: Critical Networks, Space and Intelligence Systems, Electronic Systems and Communication Systems.

Harris is a registered trademark Harris Corporation. Trademarks and trade names are the property of their respective companies. © 2016 Harris Corporation 10/16 CS-PSPC ECR-8093S

Non-Export Controlled Information

* In Brazil, these options are not available.

Instant recall of received audio replays re-ceived transmissions to avoid missed calls.

Wi-Fi® connectivity allows voice delivery outside the radio coverage area using the Harris BeOn® application. Also, the op-tional cell modem provides voice and data wherever cellular/LTE is available.

Built-in GPS, Bluetooth®, Active Noise Cancel-lation, and 4-position A-B-C-D switch standard.

Unique user interface with two displays and innovative features such as Visual Zone identi-fication (color coding of talkgroups) to make radio operation simple and intuitive.

DESIGNED FROM THE GROUND UP TO CONVERGE VOICE AND DATA

Designed with input from mission-critical users, the XL-200P is an entirely new radio platform – processor, memory, and software – that merges robust LMR voice with unique-in-the-industry voice and data over cellular/LTE/Wi-Fi to provide leading-edge connectivity.

AUDIO EXCELLENCE

The new design pairs a powerful 1.5W audio amplifier with woofer and tweeter speakers (with resonant cavities and tuned ports) to conquer noise and deliver industry-leading clear and intelli-gible audio.

COMPACT AND ERGONOMIC ALL BAND + LTE RADIO

The shape of the XL-200P was based on extensive human factors research to create a radio that nestles naturally in users’ hands. Controls are shaped and arranged for ease of use and optimum performance, including accessory connections.

TOUGH MECHANICAL PACKAGE

With a rugged cast aluminum frame and tough seals, the XL-200P is constructed to operate in severe environments. This radio meets MIL-STD-810G for durability, including Method 511.5 for explosive atmospheres and Method 504.1 for con-tamination by fluids, so the radio can be scrubbed with cleansers and biological sanitizers.

ACCESSORIES

The XL-200P is available with a selection of dependable Harris accessories that operate in a range of environments. Several are shown below.

Headsets The XL-200P can be used with a wide variety of headsets and covert audio accessories to provide a complete user-gear solution for the industrial, public safety, utility, and transportation markets. Heavy-duty and lightweight headsets are available with in-ear or over-the-ear hearing protection, flexible boom microphones with noise-reduction technology, and standard or remote PTTs. In addition, the XL-200P can be used with Bone Con-ducting Skull Headsets and Throat Microphone/Headset Kits. Covert audio kits are available in black or beige, and in 2-wire or 3-wire configura-tions with earpiece, microphone, and PTT.

Tactical Headset 3-Wire Mini-Lapel Microphone

Carrying Cases Harris offers a versatile line of carrying cases for the XL-200P full-spectrum multiband radio. Options include a standard belt clip and premium belt loop, both of which afford the radio user a low-profile, integrated carrying option. In addition, a premium leather holster is available for attaching to a belt or wearing with the premium leather shoulder strap.

Leather Carrying Case

Chargers Harris offers a variety of chargers for the XL-200P: Single-Bay, Multi-Bay, and a Vehicular Charger for in-car charging. The chargers are designed to quickly and safely charge battery packs in approximately 1 to 4 hours.

Single-Bay Charger Multi-Bay Charger* Vehicular Charger*

Additional Accessories Available Bluetooth speaker microphones, Bluetooth covert earpieces, standard speaker microphones, Lithium Ion battery, PC programming software and cables, other subminiature surveillance accessories, and antennas.

Belt Clip

This document has been prepared by Brian Zastoupil of Pine to Prairie Solutions LLC on behalf of Lake of the Woods County. Questions concerning content of the plan amendment may be directed to Brian Zastoupil via e-mail: [email protected]

Lake of the Woods County, Minnesota

ARMER Participation Plan Amendment

Add CCGW

March 2017

EXECUTIVE SUMMARY

Below is a synopsis of the participation plan amendment proposed by Lake of the Woods County.

Lake of the Woods County currently has ARMER trunked mobile and portable communications issues in the Northwest Angle, Lake of the Woods County.

Lake of the Woods County proposes adding a Conventional Console Gateway (CCGW) and 800 MHZ consollette at the MNDOT Lude site which would control an 800 MHZ conventional repeater located on an existing communications tower within the angle.

Lake of the Woods County has previously been approved for an ARMER full participation plan.

This plan amendment only modifies the previously approved plan with addition of CCGW.

The target service date for CCGW is April 2017, pending plan amendment approval.

SECTION 1

BACKGROUND

Lake of the Woods County PSAP is physically located at the Lake of the Woods County Sheriff’s Office in Baudette, Minnesota. The PSAP is equipped with Zetron console positions (Wireless Dispatch)

Lake of the Woods law enforcement agencies are currently fully operational on the ARMER radio network.1 Although ARMER coverage has been adequate within the majority of the county, there is inadequate coverage within the Northwest Angle. This issue was previously identified in county ARMER full participation plan.2 MNDOT currently does not have plans to deploy an ASR site to remedy communications issues which currently exist in extreme northern Lake of the Woods County. Law enforcement agencies from Lake of the Woods County and EMS agencies from Roseau County respond to emergencies within the NW Angle. Additionally public safety agencies from the US Customs and Border Patrol, US Coast Guard and Minnesota Department of Natural Resources routinely patrol the area waters. A significant portion of the surrounding land mass is under authority of the Red Lake Band of Chippewa. Additionally, this geographic location is difficult for 1st responders to access. (With the exception of Alaska, this is the only section of the United States above the 49th parallel!) The only access via road is through the international border with Canada (Province of Manitoba). Interoperability with Manitoba Public Safety agencies has been a concern and continues to be challenging.

1 All footnotes are detailed at end of the plan under the heading of “References.” 2 RFCC report

SECTION 2

TECHNICAL PLAN

Lake of the Woods County is deploying an 800 MHZ conventional repeater on a leased tower in the township of Angle Inlet. The repeater has been licensed on the national interoperable channel 8TAC93. (Call sign WQXX444)

Additionally Lake of the Woods County will deploy a control station with low density CCGW (in a county supplied equipment rack) at the MNDOT Lude site, with the intent of RF control of the Northwest Angle 8TAC93 repeater.

The purpose of the CCGW deployment is to provide access to NWA 8TAC93 repeater via the ARMER network.

The plan is to have an existing MCC7500 host a soft patch between an ARMER talkgroup and NWA-8TAC93. (Existing MCC7500 host yet to be determined).

Since the approach utilizes existing national interoperability frequencies, no ARMER user radio reprogramming is required to utilize site as all ARMER radios already required to include this channel (Per ARMER Standard 3.16.6)

Additionally the use of national interoperability frequencies provide an opportunity to enhance interoperability with the province of Manitoba.3 This equipment will be installed with project oversight from Northwest Regional Administrator.

ARMER PROCEDURE COMPLIANCE Per ARMER standard 1.2.0 section 3, any hardware which could impact the system network must be reviewed and vetted by MNDOT and OTC.

SYSTEM MAINTENANCE Lake of the Woods County assumes maintenance responsibilities of repeater, control station and CCGW.

SUMMARY The primary points of contact for this project are: Gary Fish-Sheriff Lake of the Woods County Sheriff's Office 206 – 8th Ave. SE. Baudette, MN 56623 218-634-1143 Phone [email protected]

Jill Hasbargen Olson-Emergency Management Director Lake of the Woods County Sheriff's Office 206 8th Ave. SE. Baudette, MN 56623 218-634-4547 Phone [email protected]

Brian Zastoupil Pine to Prairie Solutions LLC 2429 Parkview Drive South Fargo, ND 58103 [email protected] Lake of the Woods County/RRRDC looks forward to the approval of this plan amendment with an expected implementation April 2017.

3 TB-8 — Compendium of Interoperability Voice/Data Channels That Can Be Used Nationwide in Canada and for Canada-United States Interoperability Operations




References 1) State of Minnesota Allied Radio Matrix for Emergency Response “ARMER”

https://dps.mn.gov/divisions/ecn/programs/armer/Pages/default.aspx 2) Rey Freeman Communications Consulting- RFCC- Lake of the Woods ARMER

Participation Plan- May 2015 3) Industry Canada- Spectrum Management and Telecommunications TB-8

https://dps.mn.gov/divisions/ecn/programs/armer/Pages/default.aspx

http://www.ic.gc.ca/eic/site/smt-gst.nsf/eng/sf10976.html

Allina Health Emergency Medical Services

ARMER Participation Plan Amendment Amendment

05/08/2017

Submitted by: Victoria Vadnais

Technology and Emergency Planning Specialist Amendment #1

Executive Summary

The Allina Health Emergency Medical Services ARMER Participation Plan was completed and approved by Metro Regional Advisory Committee, Metro Region Radio Board, Emergency Communications/Services Board, Minnesota Department of Transportation-Electronic Communications Division, Operations and Technical Committee of the State Emergency Communications Board. The Statewide Emergency Communications Board approved the Allina Health Emergency Medical Services ARMER Participation Plan in 2008

In this Amendment, Allina Health Emergency Medical Services proposes to add 3 talkgroups to the Northwest Radio Region. Allina Health Emergency Medical Services has contracted to dispatch for St. Mary’s EMS in Detroit Lakes, MN.

DETAILED REQUEST TECHNICAL, OPERATIONAL, & FINANCIAL IMPACTS OF THE PROPOSAL Allina Health Emergency Medical Services is a 14 position secondary PSAP operating the MCC 7500 Consoles. We ask to add 3 Allina Health Emergency Medical Services talkgroups for the dispatch operations for Detroit Lakes, St. Mary’s EMS. One talkgroup for day to day dispatching. Two talkgroups would be for agency interoperability and utilized for incident management. With approval from the Northwest Radio Board these talkgroup would be programmed under a Becker County Profile

Proposed Talkgroup Name Proposed Talkgroup Profile EMSAL SM RGN-NW-BK-R EMSAL TAC-1 RGN-NW-BK-BRDR EMSAL TAC-2 RGN-NW-BK-BRDR

Allina Health Emergency Medical Services will assume responsibility for the initial and continuing education for the St. Mary’s EMS Staff following the ARMER Standards for training. There are no foreseeable financial impacts to ARMER or the Northwest Region. Please see the attached proposed fleetmap ADMINISTRATIVE UPDATES Allina Health Emergency Medical Services Primary Point of Contact Victoria Vadnais 651-241-4405 [email protected] Allina Health Emergency Medical Services System Administrator Robert Schornstein 651-222-0555 [email protected]



H:\Statewide Emergency Communications Board\COMMITTEES\Operations and Technical\OTC Meeting Materials\2017 Meeting Materials\03 MAR\Copy of St Mary talkgroup list Mobile-A 3/8/2017

BK MAIN BK OTHER HOSP OTTERTAIL CLEARWATER NORMAN MAHNOMEN REG TRANSPORT 8 CALL 7C NAT 7SOA NAT MN2/DRO CM NW STAC1 AL-SM BK EMS MAIN ST MARY DL OT FIRE/EMS CR LAW ADA AMB MM EMS 1 NE CALL 8CALL90 7CALL50 7SOA 1 DRO 1 CM CALL NW CALL STAC 1 1

2 AL-SMTAC1 BK LAW MAIN PERHAM OT 2 BAGLEY HOSP ADA HOSP MM COM 1 NE 2 8TAC91R 7TAC51 7SOA 2 DRO 2 CM 2 NW 2 STAC 2 2

3 AL-SMTAC2 BK FIRE MAIN LK REGION FF OT 3 CR EMS MAIN MM COM 2 NE 3 8TAC92R 7TAC52 7SOA 3 DRO 3 CM 3 NW 3 STAC 3 34 BK 2 BK EMER SANFORD FARGO OT 4 CR FIRE MAIN HUBBARD MM COM 3 SW CALL 8TAC93R 7LAW61 7SOA 4 DRO 4 CM 4 NW 4 STAC 4 45 BK 3 BK WE FEST ESSENTIA FARGO OT 5 CR COM 1 HU EMS 1 MM COM 4 SW 2 8TAC94R 7LAW62 7SOA 5 SEMTAC CM 5 NW 5 STAC 5 56 BK 4 BK EVENT 1 ESSENTIA ADA OT 6 HU EMS 2 MM COM 5 SW 3 8CALL90D 7CALL70 7SOA 6 MSP CALL CM 6 NW 6 STAC 6 67 BK 5 BK EVENT 2 MAHNOMEN OT 7 CLAY HU COM 5 MAHN HOSP SR CALL 8TAC91D 7LAW81 7SOA 7 CM 7 NW 7 STAC 7 78 BK 6 BK EM/EOC SANFORD BAGLEY OT 8 SANFORD FARGO HU COM 6 WADENA SR 2 8TAC92D 7CALL50D 7SOA 8 CM 8 NW 8 STAC 8 89 BK 7 BK EMS TAC1 ST JO'S PARK RAPIDSPERHAM HOSP ESSENTIA FARGO HU COM 7 WD FIRE/EMS SR 3 8TAC93D 7TAC51D 7SOA 9 CM 9 NW 9 STAC 9 9

10 BK 8 BK VHF INTEROP WADENA LK REGION FF HU COM 8 WD 5 SE CALL 8TAC94D 7TAC52D 7SOA 10 CM 10 NW 10 STAC 10 1011 BK EMS TAC 1 EMS AL-SW ALTRU PK RPD HOSP WD 6 SE 2 8SOA1 7LAW61D 7SOA 11 CM 11 NW 11 STAC 11 1112 ST MARY DL ST CLOUD EMS-SMRCC 8SOA1 8SOA1 8SOA1 WADENA HOSP SE 3 8SOA2 7LAW62D 7SOA 12 CM 12 NW 12 STAC 12 1213 EMS-SMRCC ESSENTIA DULUTHEMS-MRCXP1 8SOA2 8SOA2 8SOA2 8SOA1 MSP CALL 8SOA3 7CALL70D 8SOA1 8SOA1 8SOA1 1314 EMS-MRCXP1 ST LUKE DULUTH EMS-MRCXP2 8SOA3 8SOA3 8SOA3 8SOA2 8SOA4 7LAW81D 8SOA2 8SOA2 8SOA2 1415 EMS-MRCXP2 ESSENTIA BRAINERMSP-CALL 8SOA4 8SOA4 8SOA4 8SOA3 1516 BK F/E ADMIN AL-SM AL-SM AL-SM AL-SM AL-SM 8SOA4 AL-SM AL-SM AL-SM AL-SM AL-SM AL-SM AL-SM AL-SM 1617

Allied Radio Matrix for Emergency Response

ARMER

Project Status Report

Reporting Period February 1, 2017 through March 1, 2017

Overall Status:

Green (Controlled)

Yellow (Caution)

Red (Critical)

Reason for Deviation

Budget

Schedule Land acquisition delays will impact completion of some sites

Scope

Controls Issue Status:

Change Status:

• No pending plan changes

Executive Summary

ARMER Backbone

98% On-the-air

Page 1 of 5

Monthly Status Report MnDOT Office of Statewide Radio Communications

Accomplishments

Accomplishments during this Reporting Period:

• The following sites went on the air:

• The land acquisition has been completed for the following sites:

o Silver Island Lake (NE Lake County)

Budget

Construction Budget Status as of March 1, 2017

Project Funding Original Budget Spent to Date

Unspent Balance

Remaining Encumbered Available

Balance

Phase 3 $45,000,000 $44,952,397.19 $47,602.82 $0.00 *COMPLETE

SRB Funds (FY 09) $1,902,831.00 $1,902831.00 $0 $0 COMPLETE

Phase 456 (FY 09) 61,996,957.89 $61,996,957.89 $0 $0 $ 0

Phase 456 (FY 10) $62,015,407.77 $62,005,047.77 $10,360.00 $10,360.00 $ 0

Phase 456 (FY 11, 12, 13) $61,987,634.34 $57,082,794.85 $4,904,839.49 $1,203,573.87 $ 3,701,265.62

Total Phase 456 $186,000,000.00 $181,084,800.51 $4,915,199.49 $1,213,933.87 $ 3,701,265.62

Projected Contingency as of March 1, 2017 $426,265.62

Comments:

Page 2 of 5


Scheduled Milestones / Deliverables

Status updated March 1, 2017

Milestone Total Sites Sites Not Started

Sites in Progress Sites Complete

ARMER Backbone Construction 335 Sites

Tower Site Acquisition 335 0 5

Tower Construction & Site Development Work 335 5 3

Microwave Connectivity & RF Deployment 335 5 2 331

On the Air Some Sites are on the air, but on the old towers or temporary towers. They are counted as on the air, but still require construction and/or installation at the new tower sites before they are complete:

o Finland o Lake Crystal

Of the 331, 2 are on temporary sites; sites construction and move still in the works.

SE – all sites completed SR – Land acquisitions completed, Lake Crystal and Madelia under construction. SW – all sites completed CM – all sites completed Metro – all sites completed NW – 1 land acquisitions remaining. NE – 2 land acquisitions remaining. Completion Targets ARMER all Phases: 3 original plan sites will be delayed due to delays in land acquisition.

Page 3 of 5


Ongoing ARMER System Work Motorola System Upgrade

• 7.15 upgrade in process. Master site upgrades completed. RF sites software upgraded. Working through dispatch center upgrades.

• Contracts completed for billing with local agencies involved in 7.19 equipment replacements under the Motorola contract.

• 2017 Motorola SUAII local agency billings notices to be sent soon. • SUAIIPlus 7.19 equipment upgrades. Over the next 5 years before we can go to Motorola

system release 7.19 all circuit based simulcast and Quantar based ASR sites need to be upgraded. The hardware and services are all included in our current SUAIIPlus contract. We have meet with the agencies that this involves and we have come up with the following tentative implementation schedule for these upgrades: System Equipment order Install

o St Cloud subsystem 1st half 2016(Rcvd) Completed o Stearns ASR sites 1st half 2016(Rcvd) Completed o Enfield(Wright-Sherburne) subsystem 1st half 2016(Rcvd) Completed o Goodhue subsystem 1st half 2016(Rcvd) Completed o North Branch(Isanti-Chisago) subsystem 1st half 2016(Rcvd) Completed o City Center 1st half 2016(Rcvd) Completed o Olmsted subsystem 2nd half 2016(Rcvd) Completed o Hennepin SAT COW ASR 2nd half 2016(Rcvd) Completed o Norwood (Carver- Scott) subsystem 1st half 2017(Ordered) 1st half 2017 o Hennepin West subsystem 2nd half 2017 2nd half 2017 o Washington subsystem 1st half 2018 1st half 2018 o Minneapolis subsystem 2nd half 2018 2nd half 2018 o Dakota subsystem 1st half 2019 1st half 2019 o Hennepin East subsystem 2nd half 2019 2nd half 2019 o Anoka subsystem 1st half 2020 1st half 2020 o Ramsey subsystem 2nd half 2020 2nd half 2020

Planned system upgrades during this contract period are:

• 7.17 End of 2018 • 7.19 End of 2020

Site improvements

• We are continuing our review of our leased sites/land. Plans had always been to build towers in these areas, but to get the project moving we leased sites to get on the air. In review of some of the land and lease cost it would make sense to find land in these areas and build towers. Also looking at long term land lease from private parties, would prefer to have towers we own on state, County or City owned land.

Page 4 of 5


• Replace Lake Crystal leased site with 2 new sites. This adds a new site to the area. Tower bids awarded sites under construction.

Microwave improvements

• Still reviewing microwave performance, ongoing.

Old towers that need replacement

• We have a number of towers that are on the air for ARMER that are old towers constructed in the 1950’s. These towers did not pass structural when we added the new ARMER equipment. But the level of structural deficiency was not a risk that required immediate replacement. So we have held off on replacement of these towers to see where we were in the ARMER budget to build what we had planned. We are still holding off on these until we are a little further along with ARMER. Towers not replaced under the ARMER project will be scheduled for replacement as the ARMER maintenance budget allows, estimate 1 to 2 per year until completed. In 2016 we replaced Russell and Hawley. For 2017 we have Cass Lake and Windom planned for replacement. Cass Lake and Windom tower replacement contracts awarded.

Page 5 of 5


$3,701,265.62

Finland Lake Replace Tower DNR/Envir $440,000.00 $3,261,265.62NE Lake County (Silver

Island Lake) Lake New tower Land Ready $930,000.00 $2,331,265.62

Lima Mt Cook New tower DNR/Envir $880,000.00 $1,451,265.62

Molde St Louis Replace fire tower DNR/Envir $320,000.00 $1,131,265.62

Berner Clearwater New tower Indent Land $505,000.00 $626,265.62

$200,000.00 $426,265.62

$0.00 $426,265.62

Freedhem Replace tower/shelter $600,000.00

Middle River $600,000.00

Thief River Falls Replace tower/shelter $600,000.00

Virginia $600,000.00

Viola $600,000.00

Kimball $600,000.00

Hoffman $600,000.00

New London $600,000.00

Woodland $600,000.00

Littlefork $600,000.00

Roosevelt $600,000.00

Hewitt $400,000.00

$500,000.00

$500,000.00

Replace Tower

Mapleton: Find land and build new tower

Geneva: Need to look at land purchase, new tower ?

TOWER REPLACEMENTS (This work being held until above projects completed)

Replace tower/shelter




Replace tower

Replace tower

Replace tower


Replace tower

PENDING WORK

Site clean up, shelter and tower removals

ARMER Construction Budget (Remaining Work)

Estimate to

CompleteSite Name (Green ‐ site on air) County Description

Land/

Construction

Unencumbered Fund Balance ( As of March 1, 2017)

Balance

Status February 2017Monday, March 6, 2017 9:21 AM

StatusBoard Page 1

Summary February 2017Monday, March 6, 2017 9:10 AM

StatusBoard Page 1

Law Enforcement Division Federal Reserve Bank of Minneapolis€¦ · Law Enforcement Division 90...

Documents

Transcript of Law Enforcement Division Federal Reserve Bank of Minneapolis€¦ · Law Enforcement Division 90...