statewide emergency communications board …

STATEWIDE EMERGENCY COMMUNICATIONS BOARD

INTEROPERABILITY COMMITTEE

Tuesday, May 19, 2015 1:00 p.m. Chair: Dave Thomson CONFERENCE CALL

Video Conferencing Sites: dot r d3b St Cloud IP: 10.68.29.162 dot r training center IP: 10.68.30.98 dot r d8b Marshall IP: 10.68.29.66 co-stlouis-r-eoc co-lincoln r-em Call-in number: 1-888-742-5095 Conference code: 2786437892#

MEETING AGENDA

Call to Order

Approval of Agenda

Approval of Previous Meeting Minutes

ACTION ITEMS

ISSI Proposal

DISCUSSION

NEW BUSINESS

ANNOUNCEMENTS

ADJOURN

STATEWIDE EMERGENCY COMMUNICATION NETWORKS

INTEROPERABILITY COMMITTEE April 21, 2015 1:00 P.M.

Chair: Dave Thomson Special Meeting by Conference Call

MEETING MINUTES

Attendance: Present Members/alternates present:

Chair: Dave Thomson/Jim Crace—MN Chiefs of Police Association Vice Chair: Troy – Minnesota State Patrol Victor Wanchena/Vacant – MN Dept of Corrections

Clif Giese/Dan DeSmet– MN Ambulance Association Bill Schmidt/Vacant – MN Department of Health Brian Askin/Dan Kuntz – MN DNR Tim Lee/Mukhtar Thakur/Brad Peters – Mn/DOT Pam Biladeau/Bob Norlen – MN EMSRB Ron Jansen/Chris Kummer– MESB John Sanner/Rich Stanek – MN Sheriffs Association Ulie Seal/Vacant – MN Fire Chief’s Association Lance Lehman /Bill O’Donnell –MN Bureau of Crime Apprehension

Pat Coughlin/Vacant – MIFC Mike Martin/Brian Smith – Federal Seat B.J. Battig/Vacant – UASI Troy Tretter/Tom Simota – MN National Guard John Dooley/– HSEM Scott McKellep/ Michael Wisniewski - HSEM Greater MN Terry Stoltzman/Vacant – HSEM Region 6 Rick Freshwater/Mark Darnell – SE MN RAC John Maatz/Kimberly Hall / SW MN RAC Brett Miller/Darrin Haeder – SC MN RAC Micah Myers/Kristen Lahr– Central MN RAC Scott Camps/Kerry Swenson /Bruce Hegrenes– NE MN RAC Pat Novacek / Brian Zastoupil – NW MN RAC Monte Fronk – Tribal Government Jim Halstrom – Association of MN Emergency Managers (AMEM) *Members attending marked with highlight. Guests: Jackie Mines, DPS-ECN Cathy Anderson, DPS-ECN Carol-Linnea Salmon, DPS-ECN

Interoperability Committee April 2015 Page 1

Rubin Walker, DPS-ECN Randy Donahue, DPS-ECN Jill Rohret, MESB Rod Olson, City of Minneapolis Jon Vavruska, Hennepin County

Call to Order:

Chair Thomson calls the meeting to order at 1:05 p.m. Approval of Agenda:

Chair asks for a motion to approve the Agenda. John Dooley moves to approve the agenda. Terry Stoltzman seconds. Motion carries. Approval of Meeting Minutes:

Chair asks if there are any changes to the previous meeting’s minutes. None stated.

Ron Jansen moves to approve the previous meeting’s minutes. Clif Giese seconds. Motion carries.

ACTION ITEMS

STATE STANDARD 1.11.1 (CATHY ANDERSON)

Cathy Anderson presents the changes recommended by the work group and as presented in the meeting materials. She reads the suggested language under section four, “Recommended Protocol/Standard.”

Local System Administrators are responsible for maintaining system configuration databases for local infrastructure, subscriber databases, and console configuration databases. Therefore, they shall have successfully completed the appropriate training on the system management functions.

Appropriate training shall, at a minimum, include equivalent experience and/or formal factory training, either at the factory or in the field, conducted by a qualified instructor.”

Local System Administrators shall be familiar with the ARMER State Standards. In addition, personnel responsible for day-to-day database administration (i.e. moves, changes, or additions to a system or subsystem subscriber database) shall receive formal vendor/factory training from the equipment manufacturer or a trained individual designated by the Local System Admin. If necessary, MNDOT will provide additional ARMER “add-on” training.”


Discussion about how to define “equivalent experience”. Suggestion that with the “and/or” added it says if you have equivalent experience, then that is your training.

Anderson reports that there may have been liability reasons to leave it vague (and not require certification). She said the workgroup especially didn’t want “qualified instructor” removed because you could get a third party shop without that language. The general consensus is that they wanted it to stay fairly nebulous but yet say that somebody had to be qualified. Discussion about what is equivalent training and how could it be interpreted. Agreement that “equivalent training” should be defined. All system administrators should have the same level of understanding of the system.

Tim Lee clarifies that MnDot does not provide system training. MnDot provides the “dos and don’ts” of the system, the best practices. Brian Zastoupil moves to change the wording of the last sentence on page 1 to read: “If necessary, MnDot would provide additional ARMER System Administrator best practices training.” Kerry Swenson seconds.

Discussion about the fourth paragraph, where it says “or trained individual designated by the Local System Admin.” Anderson says the example was if somebody leaves their position and someone takes their place as the new county system admin, they could be trained locally, for their county.

Concerns that the quality of training could be diminished as it is handed from one person to another and so on. Discussion about the role of the system admin. The system admin keeps in mind the local and regional needs and balances those with the best interests of the bigger picture of the system. Because of this responsibility, it is suggested that factory training be required of all system admins. It is suggested that this is outside of the scope of the factory training and is covered under the requirement that the system admin be familiar with the ARMER State Standards. Motion carries.

Further discussion about requiring vendor/factory training for anyone who will be a local system admin. Lee says that MnDot sends every new person to factory training. It depends on how you set up the accounts. MnDots radio techs and engineers have different rights for what they can do in the system. The radio shops that are programming radios can deal with the alias and I.D.s for radios but they can’t go in and build talk groups. It’s all how you set up the accounts and what you allow them to do.

Jansen moves to require manufacturing training to be a local system administrator. He moves to change the second to last line on page 1 to read: “shall receive formal vendor/factory training from the equipment manufacturer.” Swenson seconds.

BJ Battig points out that the fourth paragraph begins, “In addition, personnel….” It does not say, “In addition, local system administrators…” He proposes a friendly amendment to change this language.


Jansen and Swenson accept a friendly amendment from B.J. Battig to change “In addition, personnel responsible for day-to-day database administration…” to “In addition, Local System Administrator responsible for day-to-day database administration...” Motion carries. Ron Jansen says we need to define “equivalent experience” or remove it in paragraph two.

Ron Jansen moves to remove “equivalent experience” in paragraph two. This changes the Standard to read, “Appropriate training shall, at a minimum include, formal factory training, either at the factory or in the field, conducted by a qualified instructor.” Zastoupil seconds. Discussion about further defining the training. Should it list the Motorola or the 7.X or keep it more open so it will not have to be changed if the vendor changed, etc.

Jansen suggests changing it to, “Appropriate manufacturer training shall, at a minimum, include formal factory training, either at the factory or in the field, conducted by a qualified instructor.” Anderson suggests, “Appropriate training shall at a minimum include ARMER infrastructure formal factory training, either at the factory or in the field, conducted by a qualified instructor.” Thomson suggests adding ARMER. Friendly amendment was accepted to change the Standard to read: “Appropriate training shall, at a minimum, include ARMER infrastructure formal factory training, either at the factory or in the field, conducted by a qualified instructor.” Motion carries. Long discussion about different levels of those performing system admin functions and is there a need for more than one tier and should everyone need to take the factory training. Randy Donahue reports that in the southern region, for example, it has been defined as being two different jobs. By MnDot requirement, every county’s participation plan has to have someone named on the document as a local system manager or administrator. That person in most of the very rural counties manages everything. They manage I.D.s, keep track of where the radios are, etc. The only thing they don’t do is the actual technical programming of the radios or getting into a client terminal and activating the radios. You could have two distinct positions where one is just doing the technical labor and the other is doing the nuts and bolts of managing the county’s resources. In many rural areas, the technical work is done by the Motorola vendor. Mike Martin gives the example of the FBI. They program their own radios but don’t do anything with the P.M. Discussion and agreement that this Standard is meant to address the person who is sitting in front of a P.M. It is suggested that the committee may want to revisit the topic of the various levels of system administration that are carried out in different regions or capacities and particularly how that relates to State Standards. Monte Fronk moves to approve Standard 1.11.1 as amended. Kerry Swenson seconds. Motion carries.


The Standard will go before the Operations and Technical Committee in May.

ANNOUNCEMENTS

Chair Thomson announces that the ISSI proposal will be coming before this committee next month on May 19th. Meeting adjourns at 2:14 p.m.


1 Minnesota OTC ISSI Report

Operational and Technical Committee (OTC) Inter SubSystem Interface (ISSI) report

July 14, 2014

Prepared by OTC ISSI sub‐committee:

Nathan Timm Patrol Sergeant / Radio Admin Goodhue County Sheriff’s Office

Red Wing, MN 651‐385‐3155

[email protected]

Bruce Hegrenes Radio System Administrator

St. Louis County Sheriff’s Office Duluth, MN

[email protected]

Brian Zastoupil Radio Systems Coordinator

Red River Regional Dispatch Center Fargo, ND

701‐451‐7683 [email protected]

With assistance by:

Mike Fink Senior Account Manager Motorola Solutions, Inc

612‐567‐2911 [email protected]

Carl Guse

Wisconsin State Patrol Madison, WI 920‐210‐4455

[email protected]


BACKGROUND AND INTEROPERABILITY

Radio communications are an essential element of any emergency response. The importance of communications is often praised or criticized in event after action reports. Large events, or events on jurisdictional borders, often involve a response by multiple agencies who may not be on the same radio system. If those agencies are on different radio systems or bands, the ability for those first responders to inter operate will be impaired or impossible. In Minnesota, the widespread transition to the state 800mhz ARMER radio system has resulted in nearly all public safety and support personnel being on one common system. As such, event communications have been greatly simplified. Staff can interoperate on shared regional or statewide talkgroups, regardless of discipline. The ARMER radio system is known as a “trunked radio system.” Rather than most entities having their own radio frequencies, the system pools many frequencies and assigns them to users as needed. This increases efficiency and also allows users to roam between tower sites – users are no longer restricted to the range of the local repeater. The system is digital so voice clarity is increased. Because users can roam around the state, interoperability in Minnesota is exceptional. However, this situation becomes complicated when working with neighboring states, or Canada. Foreign users in those areas do not have the ability to use the Minnesota ARMER system. One prime example of this problem exists in the Duluth area. Duluth is a City of the First Class with an International Seaport that is managed by Duluth and Superior, Wisconsin. Duluth first responders have a close working relationship with their counterparts in Superior Wisconsin. Prior to the transition to ARMER system, conventional VHF repeaters were widely used in this area. Users in both Superior and Duluth had each other’s radio repeaters in their radios. Users scanned across the border and could easily talk with their counterparts. When Duluth and St. Louis County moved to ARMER, that ability was lost. There has been a desire in the Duluth area to connect the trunking systems in Minnesota and Wisconsin. To that end, the Operational and Technical Committee tasked this group to research cross border interoperability. Months of research have been conducted, including a break out session at the 2014 Interoperable Communications Conference in St. Cloud.

SHARING CONTROL STATIONS

The loss of VHF cross‐state interoperability was noted early on by several Minnesota counties. The State Division of Emergency Communications Networks obtained a grant to place two ARMER system control stations in each cross state border county that was willing to accept the equipment. The control stations are typically connected to the county’s dispatch console. This allows the county to monitor radio traffic on ARMER, and speak directly to the Minnesota dispatch center when needed. Furthermore, with many models of dispatch consoles, the cross state dispatch center can patch their radio system into ARMER. This solution does have some disadvantages. One disadvantage is the console connected control station can only have 8 talkgroups programmed (a restriction of tone remote control). It is impossible to program all interoperability talkgroups and local county resources into the stations. This results in finding a balance by programming only the most often used talkgroups.


Another disadvantage is most console systems do not buffer audio when the control station transmits. Every time a system radio transmits on a trunking radio system, a brief chirp is sounded before the user can speak. This gives the system enough time to recognize the transmitting user, find out what tower sites need to be activated to ensure all users on that talkgroup receive the signal, and verify none of those towers are busy. Because the console system immediately sends audio to the control station, the first approximate ¼ to ½ second of audio is clipped. A dispatcher can compensate for this issue by always giving a brief pause before speaking. When a patch is set up for first responders in a critical incident, those users cannot be expected to always pause before speaking. This could result in an officer speaking “don’t shoot” into the patched talkpath, and the other users on that path hearing “shoot.” Finally, the control station involved in a patch may be taking conventional analog audio and converting it to digital for the ARMER system. This results in loss of audio clarity. Of note is users working through a patch on a control station are still serviced by their home system. If a user roams outside of the home network, communication will be impossible.

THE ISSI SOLUTION

The ARMER system, like many others across the nation, is built on a digital standard called P25. This standard calls for the connection to other radio systems, and is named ISSI – Inter Sub System Interface. Motorola is the vendor for the ARMER system. The first generation of Motorola’s ISSI feature is named ISSI.1, and allows talkgroups to be shared across radio systems (including non‐Motorola systems). ISSI.1 mimics a tower site on the foreign system and does not allow roaming across systems – users will have to manually change channel positions to connect to the neighbor system. The connection between systems is “wireline” and is not integrated in any way. Because there is no system management integration, administrators on both systems have to add each other’s radio users and bridged talkgroups. This solution also has a disadvantage in that if two users on both systems simultaneously transmit, both will be granted talk permission. So receiving units will only hear one of the two users who simultaneously transmitted. Motorola’s second generation of this solution is named ISSI.8000. This solution allows a full connection of to up to 24 foreign radio systems. The foreign system could also be a third party console site, such as EF Johnson or Zetron. The solution will not allow duplicate transmissions as busy signaling is supported across connected systems. It also allows automatic roaming onto foreign systems (if the field radio is capable), alias names for users and talkgroups to transfer between foreign systems to console sites, allows direct patching to consoles sites, seamless sharing of talkgroups across systems, end to end encryption passing, and multi system emergency alarm. With talkgroups being shared on cross border console sites, digital to digital radio patches can be established. This will not impact audio clarity, and connected console sites will informed of active patches on both systems. Console sites can also monitor foreign talkgroups up to the capacity of the console system.


ISSI CONSTRAINTS

The solution will not be useful for cross border counties who remain on legacy conventional radio systems. In those cases, the existing control station solution will be needed. ISSI.8000 will only work on 7.13 and newer systems. ARMER is currently at 7.13. This may be a concern for any foreign systems using an older version. For full roaming integration, the base site must be equipped with GTR stations. If the site is simulcast it must be IP based. Sites not conforming to this will henceforth be referred to as “legacy sites.” Subscribers at legacy sites will not be able to affiliate to foreign talkgroups. Also subscribers affiliated to a home legacy site will not be able to see foreign ID information of active foreign units on that talkgroup. Astro Saber and XTS3000 series will not support ISSI and cannot roam onto foreign systems. Non Motorola radios depend on the manufacturer’s specifications. XTS and XTL users will need to purchase a flash upgrade to allow auto roaming (portable QA4444AA and mobile GA04444AA). APX units are ISSI capable without upgrade but must have recent firmware (firmware refresh is free). Features can only be shared that are common on both radio systems. Foreign emergency recognize, console emergency set up, and full featured alias sharing are only supported between Motorola systems. CENTRACOM Gold Elite consoles do not support any ISSI features, therefore those console sites cannot monitor or engage any foreign talkgroups. Gold Elites will receive calls on home talkgroups from a foreign user but all foreign radios will be displayed as a same single reserved home system ID.

ISSI IMPLEMENTATION WITH WISCONSIN

Wisconsin has an existing P25 VHF trunked system named WISCOM, which is implemented by EJ Johnson. Douglas County Wisconsin, which is across from Duluth, is now transitioning to this system. There would be an immediate benefit for ISSI.8000 to share common interoperability talkgroups across the systems. This will allow the ability to scan those talkgroups and restore the interoperability that was lost with the St. Louis transition to ARMER. ISSI.8000 will also immediately benefit the Red Wing area. The Prairie Island Nuclear Generating Plant is located on the Minnesota side of the Mississippi River, just north of Red Wing. Because any release at that plant would affect both Minnesota and Wisconsin, drills and events require the participation of many agencies. This includes Goodhue County MN EOC, Dakota County MN EOC, Pierce County WI EOC, Minnesota state EOC in St. Paul, and Wisconsin State EOC in Madison. The direct connection of ARMER to WISCOM will greatly simplify coordination between the entities.


There is also a benefit to ambulance services who have service areas in Wisconsin. One example is Gold Cross, who is based out of Rochester Minnesota. The main Gold Cross dispatch center is located there. Gold Cross has an operation in Eau Claire, Superior and Douglas County Wisconsin. As such, control stations are interfaced back to Rochester with phone and internet circuits. This can introduce delay into the talkpath. Having an ISSI connection would allow the Rochester dispatch center to place WISCOM Gold Cross operational and dispatch talkgroups directly on the center’s consoles. Gold Cross transports most patients to Regional Trauma Centers in Duluth. Because the WISCOM system is VHF, only dual band radios would be able to roam onto their network. Of all border states, interoperability with Wisconsin has the most immediate need and is suggested to be the first system connection. There is existing microwave connections to the Wisconsin system in Duluth / Superior and LaCrescent / LaCrosse. So the required Ethernet system to system connection will be easy to establish. The WISCOM system already has the EFJ ISSI solution in place. WISCOM is currently using ISSI to connect to the county 7.11 Motorola system in Outagamie County using ISSI.1. Therefore, much of the technical research into setting up the connection has already been completed.

ISSI IMPLEMENTATION WITH IOWA Iowa does not have a statewide trunking system, but is currently trying to fund one. A RFP request is currently out, and specifies a P25 700mhz trunking system. With ISSI.8000 allowing for up to 24 system connections, Minnesota would be ready to connect to Iowa. This would allow Minnesota users to roam onto that 700mhz network, and vice versa. The existing control station solution will continue to be needed for the short term.

ISSI IMPLEMENTATION WITH SOUTH DAKOTA

South Dakota has implemented a Motorola statewide P25 trunking system. The system technology is older than ARMER, but because the South Dakota master controller is 7.13, the systems can be connected. This would have an immediate benefit in increasing interoperability between the states. One example is the national weather service in Aberdeen, SD. This center serves western Minnesota. Currently, control stations are working to provide interoperability. But with ISSI, the capacity to share will be greatly increased. It is also expected that some EMS services will have a use for the connection.

ISSI IMPLEMENTATION WITH NORTH DAKOTA

North Dakota does not have a state trunking system, and at this time is not planning one. The state is primarily on VHF conventional. The existing control station solution will continue to be utilized.

ISSI IMPLEMENTATION WITH CANADA

Minnesota shares a border with Manitoba and Ontario providences. At this time, it is unknown if those areas are planning to implement wide area trunking systems. The existing control station solution will continue to be utilized.


ISSI IMPLEMENTATION WITH FEDERAL PARTNERS

Most federal partners have agreements to use the ARMER system. Those same agencies have similar agreements with systems in our border states. ISSI would allow federal tactical talkgroups to be shared over system borders. ISSI could also be used to connect to federal P25 trunked radio systems to share talkgroups. There is a potential to reduce ARMER radio ID loading for federal systems that are capable of full ISSI, as individual radios would no longer need to be loaded in ARMER. ISSI could also be used to connect to private P25 radio systems, such as those at the Monticello and Prairie Island nuclear plants.

BUDGET

A copy of the Motorola ISSI.8000 proposal for ARMER is included with this report. At this time the total cost of equipment and implementation (with WISCOM) is $306,102. This breaks down to $148,102 for equipment with the remainder to integration. This includes a license for 10 active talkgroups. Blocks of additional active talkgroups are $50,000 each. Roaming talkgroups can be configured for more than the active amount. For example, all interoperability talkgroups could be configured between Wisconsin and Minnesota with the understanding that only 10 could be used at any one time. Motorola states that the ISSI solution will add $27,000 to $30,000 a year to the SUA maintenance contract. This includes dispatch service, network monitoring, technical support, network PM, and on site infrastructure repair. It is expected that any future connections to other systems will require additional implementation costs, but will not increase SUA expenses. Mn/DOT technicians could potentially be trained to do that work. St. Louis County Minnesota is currently applying for a port security grant that would partially fund the ISSI solution.

PROVISIONING

There will be an investment of time from select Mn/Dot managers and technicians to implement and administer this solution. The Motorola Unified Network Configurator (UNC) is used to set up ISSI.8000 and foreign configuration parameters. This then populates the Provisioning Manager database. The UNC application reads foreign subscriber information needed for each zone, where the zone controllers use the data to process calls from foreign systems. When data entry and set up is completed in UNC, local sub system administrators with proper rights can assist in maintaining the solution. This would relieve administration burdens from Mn/DOT system managers


RECOMMENDATION

The ISSI sub‐committee of the Operational and Technical Committee recommends that Minnesota purchase ISSI.8000 for existing and future needs, if budget allows. It is recognized that the initial connection to Wisconsin will not support many roaming users, due to disparate bands. The primary use will be intersystem talkgroup console patches. Real world use may show the need for additional 10 talkgroup license purchases. Respectfully submitted, Nathan Timm Bruce Hegrenes Brian Zastoupil Source data: Motorola document 6871023P61‐A: ISSI.8000 integration manual Motorola document 6871022P97‐B: ISSI.1 integration manual Motorola ISSI.8000 cut sheet

The design, technical, pricing, and other information (“Information”) furnished with this budgetary submission is proprietary information of Motorola Solutions, Inc. (“Motorola”) and is submitted with the restriction that it is to be used for evaluation purposes only. To the fullest extent allowed by applicable law, the Information is not to be disclosed publicly or in any manner to anyone other than those required to evaluate the Information without the express written permission of Motorola. The Information provided in this budgetary submission is provided for evaluation purposes only and does not constitute a binding offer to sell or license any Motorola product or services. Motorola is making no representation, warranties, or commitments with respect to pricing, products, payment terms, credit, or terms and conditions. A firm offer would require more information and further detailed analysis of the requirements. MOTOROLA, MOTO, MOTOROLA SOLUTIONS, and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license. SYMBOL is a trademark owned by Symbol Technologies, Inc., which is a wholly owned subsidiary of Motorola Solutions, Inc. All other trademarks are the property of their respective owners. © 2013 Motorola Solutions, Inc. All rights reserved. Control No. PS-000041152

ST. LOUIS COUNTY JUNE 2014

ISSI 8000 BUDGETARY QUOTE

St. Louis County June 2014 ISSI 8000 Budgetary Quote Use or disclosure of this budgetary proposal is subject Control No. PS-000041152 to the restrictions on the cover page.

Motorola Solutions Confidential Restricted Table of Contents i

TABLE OF CONTENTS

Section 1

Overview ............................................................................................................................................ 1-1

1.1 ARMER to EFJ Wiscom ISSI ............................................................................................. 1-1

Section 2

Services ............................................................................................................................................. 2-1

2.1 Professional Integration Services ....................................................................................... 2-1

2.1.1 Motorola System Support ............................................................................................... 2-1

Section 3

Assumptions ...................................................................................................................................... 3-1

Section 4

System Estimate ................................................................................................................................ 4-1


Motorola Solutions Confidential Restricted Overview 1-1

SECTION 1

OVERVIEW In response to St. Louis County’s request for a price estimate and system recommendation, we selected our ISSI 8000 for ASTRO P25 Release 7.13 solution to best suit your communication needs.

Motorola Solutions Inc. (Motorola) is pleased to propose a Project 25 Inter-RF Subsystem Interface on the ARMER System to address the need to connect to other disparate trunking systems in the area.

Motorola has demonstrated its leadership in the P25 ISSI community by being the first manufacturer to announce a shipping product that supports the P25 ISSI. Motorola has also participated in multivendor ISSI demonstrations at IWCE (2007) and APCO (2008 and 2009), and hosted the first P25 ISSI Interoperability Event in February 2010. The ISSI8000 Network Gateway is Motorola’s second P25 ISSI solution. This is a network gateway comprised of server hardware and applications that works in conjunction with an ISSI firewall.

ISSI 8000 allows an ASTRO 25 trunked network to connect to up to 24 other Project 25 (P25) ISSI-compliant trunked networks though one ISSI 8000 Gateway. ISSI 8000 can be implemented today on ARMER’s current ASTRO 25 7.13 system.

ISSI 8000 is an Interoperability Solution that enables an ASTRO 25 system 7.13 or higher to connect to other P25 systems regardless of their RF bands, manufacturer type and release versions. ISSI 8000 can save customers capital by leveraging the infrastructure of neighboring P25 systems to effectively extend the range of their network without investing in additional RF sites and its associated costs. So a user can maintain communication with their home system when they roam outside of the coverage of their home system—(Inter Agency Task forces, car chases over state lines). ISSI 8000 is useful for the Deploy & Assist Scenario where a user from one system can roam onto a foreign system to help users in that system with specific tasks and establish communication with the foreign system—(Inter Agency Task forces, disaster recovery, car chases over state lines). ISSI 8000 is useful for Coordinated Incident Management where users in separate systems responding to a region wide event can communicate with each other while remaining in their own systems—(Inter Agency Task Forces, disaster recovery).

1.1 ARMER TO EFJ Wiscom ISSI Motorola has designed and quoted the ISSI8000 Network gateway and firewall the ARMER System to interface to the WISCOM System. The following ISSI8000 hardware has been included:

One ISSI8000 Network Gateway.

10 Talkgroups for Manual Roaming.

One ISSI8000 Firewall.

One system user license bundle of 500 subscribers.

The equipment will be installed at one of the six Master Sites within the ARMER System. Rack space and power must be provided for this equipment. Manual roaming has been quoted; therefore, each subscriber that needs to roam onto the “foreign system”—WISCOM users onto the “foreign” ARMER system and ARMER users onto the “foreign” WISCOM System—must have an ID assigned and set up in the foreign system. There are 500 additional user licenses (one bundle) included in this proposal for roaming users on the ARMER system.

June 2014 St. Louis County Use or disclosure of this budgetary proposal is subject ISSI 8000 Budgetary Quote to the restrictions on the cover page. Control No. PS-000041152

1-2 Overview Motorola Solutions Confidential Restricted

Also, the number of talkgroups that will be mapped require one Radio User ID per mapped talkgroup on each system. A total of 10 talkgroups have been included in this quote. Additional talkgroup licenses can be purchased in bundles of 10 at a price of $50,000.00.

Reprogramming the radios and entering Radio User IDs and interoperable Talkgroups into each system is a customer responsibility. Motorola has not included cost for reprogramming radios and UCS configuration in this proposal. Motorola will however provide programming and configuration for up to 5 radios during time of implementation in order to show ISSI roaming capabilities.

The following list summarizes the features enabled by ISSI 8000:

Multi-system Clear or Encrypted Group Call with up to 24 systems.

Multi-system Emergency Call with up to 24 systems.

PTT ID Display for foreign units including the full WACN/system ID.

Multi-system Emergency Alarm.

Multi-system Emergency Cancel.

Multi-system Emergency Recognize.

Multi-system Console Emergency Setup.

Multi-system Individual Alias Sharing.

Multi-system Phase 2 TDMA Group Call.

Busy Indication on multi-system Group Calls.

Multi-system Multigroup Call.

Multi-system Console Takeover and Resumption.

Patch between talkgroups home to different systems.

Foreign adjacent site broadcasts enable roaming to an adjacent system without a Full-spectrum scan.

Centralized Fault and Configuration Management for ISSI 8000 Gateway.

Performance Management for inter-system activity.

With manual roaming, the subscriber codeplug is enabled for Inter-WACN Roaming coverage type and is located at a G-series or other ISSI-capable RF site. There may be additional charges to enable this capability in the subscriber, depending on the subscriber model. In this mode, the subscriber cannot register in a foreign system, but can affiliate to a foreign system’s talkgroup, and display foreign or home PTT IDs. The subscriber can participate on multi-system calls on a home or foreign talkgroup. However, the following limitations apply:

In order to roam to a foreign system, it must have a personality with a unit ID belonging to that foreign system, and must manually select this foreign personality (manual roaming).

The subscriber can only authenticate with the local system while manually roaming. It cannot authenticate to its home system across the ISSI link.

Transmissions and emergency alarms from this subscriber while it is manually roamed in the foreign system will contain the PTT ID that the subscriber uses while in the foreign system, and not its home unit IThe features available on a given inter-system interface are the common set of features supported by both systems.


Motorola Solutions Confidential Restricted Services 2-1

SECTION 2

SERVICES 2.1 PROFESSIONAL INTEGRATION SERVICES

To ensure a smooth installation and deployment, our proposed solution for St. Louis County includes estimates for the following services:

Project Management for system installation and optimization.

Field Engineering and System Technologist support for system installation and optimization.

System installation and optimization.

This solution will be installed, optimized, and tested by our dedicated Project Implementation Team.

2.1.1 Motorola System Support Motorola’s standard warranty covers on-site response during normal business hours and provides for the repair of defective hardware components.


Motorola Solutions Confidential Restricted Assumptions 3-1

SECTION 3

ASSUMPTIONS Motorola has made several assumptions in preparing this budgetary proposal. In order to provide a firm quote, Motorola will need to verify all assumptions or seek alternate solutions in the case of invalid assumptions.

All existing sites or equipment locations will have sufficient space available for the system described.

All existing sites or equipment locations will have adequate electrical power and site grounding to support the requirements of the system described.

The customer will make any necessary site improvements to meet R56 standards.

Any site/location upgrades or modifications are the responsibility of the Customer.

Any required system interconnections not specifically outlined here will be provided by the Customer. These may include dedicated Ethernet or microwave links.

Where necessary, the Customer will provide a dedicated delivery point, such as a warehouse, for receipt, inventory, and storage of equipment prior to delivery to the sites.

Additional cost to configure/program link to other ISSI connections NOT included in this quote.

Network connections are Ethernet.

Can support up to 24 P25 interface through the ISGW (ISSI Gateway Server).

Hardware; ISGW Server, and ISG 1000 Firewall.

One (1) Manual Roaming License, supports 10 simultaneous TG Capacity. If more are needed, then additional licenses can be added in groups of 10 TGs.

Can monitor foreign talk groups on MCC7500.

Each ISSI link handles 10 TG. Customer wants one (1) link. Therefore, one Manual roaming license will be added. Up to 200 simultaneous calls.

No network connectivity equipment between the two systems has been included.

A Data Collection Device (DCD) HAS BEEN INCLUDED when implementing an ISSI8000 interface to another manufacturers’ P25 ISSI system.

Manual Roaming Subscribers will need to be provisioned in the foreign system and customers will have to manually change the mode on their radio when they get out of coverage of their home system.

Subscribers will need flash upgraded for auto Roam only. XTS Portable (QA04444AA) or XTL Mobile (GA04444AA). APX subscribers shipped before Q4-2012 will need a free software refresh.

Changes to connectivity will be additional cost, i.e. Ethernet microwave.

statewide emergency communications board …

Documents