February 2017 Minutes - Minnesota Department of Public Safety

February 2017 Minutes

NG911 Committee February 2017 Page 1

STATEWIDE EMERGENCY COMMUNICATIONS BOARD NG911 COMMITTEE

February 15, 2017

MEETING MINUTES Attendance Member/Alternate Darlene Pankonie, Chair/ Capt. Kathy Hughes, MN SHERIFFS ASSN Nancy Shafer/ Jill Olson, NORTHWEST MINNESOTA Steve Olson/ Patrice Erickson, NORTHEAST MINNESOTA Judy Diehl/ Jody Norstegard, CENTRAL MINNESOTA Wayne Betcher/ Faith Evers, SOUTHEAST MINNESOTA Pat Wallace/Peggy Reimers, SOUTH CENTRAL MINNESOTA Joe Reith/vacant, SOUTHWEST MINNESOTA Mary Borst, Vice Chair/Marion Larson, MAA Ross Tiegs/Vacant, MN CHIEFS OF POLICE Tim Boyer/Christine Krajsa, STATE PATROL Matt Goodman/vacant, GIS Dana Wahlberg/Adam Iten, ECN Deb Harmon/ Vacant, TRIBAL PSAP Christine McPherson /Susan Bowler, METRO MINNESOTA Ward Parker/Vacant, MN FIRE CHIEFS *Members attending are marked with yellow highlight. Guests reporting: Tony Martin, City of Edina Cathy Anderson, ECN Rick Juth, ECN Pete Eggimann, MESB Al Fjerstad, Central Jackie Mines, ECN Kelli Peters, ECN Dustin Leslie, ECN Rick Juth, ECN Dan Craigie, ECN Carol Salmon, ECN Judy Siggerud, Otter Tail County Tom Egan, Douglas County Caitlin Christenson, Stevens County Jill Bondus, Rice/Steele Counties Jonathan Rasch, Ramsey County Dave Deal, Washington County Val Spryncyznatyk, Anoka County Brian Kyllonen, PSC Alliance Mary Terway, Stearns County Kelly Kukowski, Kittson County Mike Beagles, MPC Sherri Griffith Powell, MPC


CALL TO ORDER

Chair Pankonie calls the meeting to order at 1:00 p.m.

APPROVAL OF AGENDA

Judy Diehl makes a motion to approve the agenda. Kathy Hughes seconds the motion. The motion carries.

APPROVAL OF PREVIOUS MEETING’S MINUTES

Kathy Hughes makes a motion to approve the December 2016 minutes. Judy Diehl seconds the motion. The motion carries.

Pat Wallace mentions it doesn’t show that Peggy attended the meeting by phone for South Central. Kathy Hughes makes a motion to approve the January 2017 minutes as amended. Nancy Schafer seconds the motion. The motion carries.

ACTION ITEMS

INTRODUCTION AND OVERVIEW OF GENERAL PROCESS (DANA WAHLBERG) Dana Wahlberg gives an overview on general process for action items. The SIP guidelines will not be brought forward for action today but we want Craigie to be able to speak to that. These were introduced over a year ago when MCP started the process along with a small group of those with IT interest or background or experience with firewalls. We feel like we have a guideline version that we’re going to have ready at the next meeting to have approved, but given the input we’ve received since we distributed it, we decided we didn’t want to rush. Dan Craigie is going to do a little more discussion on it, but Wahlberg will give some background. NextGen911 was not officially part of the SECB board when we started to deploy NG911. In 2011, Director Mines was in Wahlberg’s position and she was working with MCP on a 911 plan. We’ve brought that forward now that we are starting to become more active and deploying features and functionality onto the ESI net. We are going to take some time to formalize that plan with this committee. It had initially been brought to a NG advisory committee but it was more of an informal group that was part of MSA and not part of the SECB. At the next meeting, we hope to have that plan to bring forward or else you will receive it in advance of the meeting to review. It is a very high level document that outlines the steps that the state will take towards NG911. It’s not meant to include any of the technical or operational standards that are specific to each step within that plan but more of a high level overview that describes for the SECB the direction we’re going, the funding we may request them to allocate on our behalf, and it is something the legislature would look at annually when Jackie goes to present before them. We will have that initial statewide plan, which we have followed quite closely as we’ve migrated first to the interop piece where we can do call transfers between PSAPs and then getting people onto the ESI net. The first two amendments we intend to present to the plan is the SIP migrations and migrating off of the CAMA interface gateway and into a direct sip environment and the second to


migrate to text-to-911 as a state. These documents will be something you want to watch for within the next month. We will want to bring those documents for a formal action vote of approval before we send them to the SECB. Rick Juth asks if there is any relationship between the plan Wahlberg talked about and the county 911 plans or if the county plans and the state plan are separate. Dana says they are separate. Mines says the NG911 plan is similar to the ARMER backbone plan. AMENDMENT TO STATEWIDE PLAN: PSAP SIP ENABLED GUIDELINES (DAN CRAIGIE) Dana turns over the SIP guidelines enablement document discussion to Dan Craigie. Dan says this is more of a planning document. Mike Beagles, Dave Deal, and Eggimann provided valuable input for crafting the document as far as what the direction of the document could be. The document will provide enough details that MN PSAPs and ESInet will be protected from cyber security concerns. On the first page, it states what design and perks of the ESInet are. The scope of document provides a better understanding of path, costs, and requirements for this undertaking. The document does not have specific technical guidelines but there are guidelines for recommending the firewall. This is the first introduction of what role firewalls are going to play in the MN ESInet and it will explain things like where they fit, why they are valuable, who is going to pay for it on a high level. There is a diagram indicating that the PSAP network and the 911 CPE are essentially connected. That can be done in a few ways. Dave Deal brought up there are CJIS security concerns with that happening. We will investigate and ensure whatever technical guidelines come out address that concern. It also provides other options for whether they are inserting their own firewall into different parts of this diagram or coming straight from a vendor supporting CAD or other devices within the PSAP. Do they come through their own provided firewall or do they use the ones we’re providing? It hasn’t been completely decided yet, but it gives the PSAP managers a brief overview of how it may or may not be once it happens. There is a convergence cost guide, which is pretty general, that says talk to your CPE provider because they will have the most up-to-date information about what it will cost. This document is really looking at West/Intrado costs and maybe some licensing agreements. It’s more of a planning document, and you do not want to budget off of this but if you are looking to next year or the year after, it will be a valuable tool. Beagles says nothing is specific to anybody, but we do indicate on the table for the conversion cost estimates are subject to change per CPE configuration. There may be additional considerations that come along with SIP conversion. Reach out to your CPE vendor prior to putting in an official budget together. Management and Governance, Eggimann provided some recommendations we will be looking at. The more people that look at the document and provide input, the better off we will be. That means we will have more buy-in, which will be important. ECN will be managing these and the vendor we choose. Craigie will be doing an update on the RFP soon. This will be a vendor doing the management, monitoring, and any maintenance. The technical requirements are yet to be determined. There is a FAQ section with questions like why should I convert to SIP, what are the costs. Good to ask yourself before you go into a SIP deployment.


Looking forward to having more input and adding info as needed. And having this be a part of the statewide plan. Pankonie asks what the next steps are. Craigie says it was emailed out and has been shared with partners. The goal is to bring it by a month from now – within the next three weeks would be sufficient/a week before the next meeting. Direct feedback to him at [email protected]. There may be some major changes before next month, depending on input. May change language as far as mandating firewalls, as we had recommended them before. Pete Eggimann says there is Metro TOC meeting tomorrow. He recommends that the firewalls should be mandatory. There is grant money available to buy them, the state is going to manage them, minimal impact to the PSAPs. If we utilize the ESInet the way the NENA ESInet design document would indicate where we’re using it for more than 911; for example, if a group of PSAPs came together with a CAD interoperability project and wanted to move back and forth, then use of the firewall becomes very critical. If they didn’t have a firewall in place, it puts the rest of the network at risk. The other issue is a lesson learned encountered early on when some of our early network converted to SIP and we did not understand the full extent of how the call control changed or what the impact was. Things that were traditionally understood were controlled by the ESInet that got pushed over to PSAP configuration. We didn’t figure that out until we were having issues with calls. As a consequence, we can’t measure one grade of service -- does the PSAP have enough sessions to meet requirements and rules and we don’t know what their configuration is. Now we are backtracking and have to figure out. This document is an introductory document if a PSAP hasn’t made their decision yet. This is an introductory document and will help to figure out how many sessions you need, overflow, how you are going to do the routing. You should also know how it’s going to impact the other PSAPs around you. We can introduce that in here without going into a lot of detail. We will have a section with routing issues but don’t have to explain the whole routing issue. Question was asked if two firewalls will be mandated. Per Craigie, any ESInet circuit going to a PSAP will have two. Does the security change in the diagram? Craigie says it could be based on recommendations. He has looked through the CJIS security requirements and adding a firewall could alleviate some of the concerns. Dave Deal says the firewall will help protect one way or the other. It can be turned to protect CAD or the NG911 network. You want it on your NG911 so infiltration of our network doesn’t cause a problem for the entire state. The CJIS rules have to deal with the initiation of the traffic so if communication is initiated from the outside in, that’s generally disallowed under CJIS unless from another CJDN source. The firewall would be needed on our side and you would end up with two firewalls looking at each other, kind of like what we have on the ARMER network. Putting a firewall in place does not fix the problem with communications—that will come down to how we build interface and how we have the systems talking to each other. Chair asks if it will be ready to go out for people to read and come back with a decision in one month. Craigie feels comfortable with that, as the language has been drafted. He feels three weeks to investigate security is sufficient. The new draft should be out at least one week before the next meeting.


Eggimann says it is anticipated that the vendor for the firewall contract that will manage this will be involved in enforcing or implementing some policy related to how the firewalls are set up. It is not clear to him how that policy will be established and if PSAP personnel are going to have input. He asks if we need to find IT people that have that expertise to represent us and says that would help if we had direction so we can start rounding up resources. This is the logical group to set up a policy formation or policy input group. . Pankonie said we had a subgroup formed to work on the first draft of this, but they haven’t met since the first draft of it and asked if we bring that group back. Eggimann said he did not know we had a group. Pankonie reminded him it was a minor subgroup consisting of him, Eckel, and herself that met with MnIT. Pankonie asks if the subgroup should be started back up under Craigie so the next time it comes here, it has met with approval of the subgroup. Eggimann refers to Craigie and Director Mines. Mines says on the ARMER side we form workgroups and try to get two people from every region. In this case maybe IT and PSAP operational persons might be appropriate. You could call for setting up a workgroup and the committee would recommend and vote to create a workgroup made up X number of people, at least one from every region and X number of experts, at least IT people, and that workgroup would work to create that policy with input from the staff. Dan asks if we are talking actual policies for the firewall that we will write into it or if we are talking more general like management and implementation of the project. Dana says when we go to create a technical standard, we will need to have representation from each region and create a workgroup. This is not a technical standard. It is an amendment to identify to PSAPs that there’s an expectation that when they migrate to SIP they will need to have firewalls, and there will be a technical standard that describes exactly how they will do this. Dana doesn’t think we are ready to write a technical document and Eggimann agrees. Chair asks how you install technology without a technical standard. Eggimann says there are two sides. One is the initial deployment, where you can set up rules about how the ESInet is going to interact. There is also the side that when a county wants to make a change to the system, someone needs to decide what we will or will not allow. Mines says before you have a vendor on board, you don’t know what some of those things are that have to be decided. We may need to inform the vendor some of our policy but some of this has to come after we identify who the responder is and what they are going to offer. The vendor will come back with some questions and that’s where the policy group will get involved. You could set up your committee prior to the vendor being on board, but a lot of the questions will come out of the vendor once you have one. Eggimann says one of the first questions is how are we going to allow access for a CPE vendor to manage CPE equipment. Mines says you have to work that out with the vendor. Craigie says once we have that vendor he can keep the group updated and anyone interested can be involved with the group and meet about those policies. Dar says the point is today to get this out because we know people are moving forward with direct SIP connections and putting in those firewalls so why not put them in because they are a piece to the puzzle


down the road when they are really necessary. We will look for the new draft in three weeks or less and come back next month and talk about it.

ECN REPORTS

E911 AUDIT AND APP REPORT OUT (KELLI PETERS) Peters reports that majority of the E9-1-1 audits for 2016 have gone out and those that haven’t have residual issues from last year. She is working to get the remaining issues on 2015 resolved and hopes to distribute the last of the audits soon. Brief follow up from last month. LaaSer 9-1-1, the app she reported on last month, led to discussion about concerns with LaaSer and other apps, in general. Some have misleading claims about endorsements from NASNA or the FCC and some have had misleading marketing claims. Next month’s packet will include two letters, one from NASNA in October 2016 and the other from California Emergency Services. These letters echo some of the concerns that we had last month and they are concerns that are being shared across the county Peters researched Great Call. They are based in California and offer health and safety solutions for older adults and their caregivers. They have a suite of easy to use mobile devices to use which include: Jitterbug smart phone (simplified) with large icons, usage meters, internet access, and connects to the 5 star app. Jitterbug flip phone – a traditional flip with easy to read buttons, also offers a one-button connect to 5 star app. Great Call lively – a mobile urgent response device that can be carried in a pocket or handbag. It’s a one-touch device for emergencies that contains a GPS monitor and has fall detection. It can be carried or worn around the neck and can automatically connect with 5-star in event of a fall. Great Call lively wearable – a smart fitness tracker and safety monitor for seniors. Can be paired with Great Call Smartphone. Can issue daily challenges and goals and can send updates to family members and caregivers. Also has an emergency button that can connect with 5 star. All have a purchase price and monthly fee. There is also an additional monthly fee to connect to 5 star app. Five Star is an urgent response service provides access to certified agents who can confirm location, help evaluate a situation, and engage appropriate help 24 hours a day. Agents are trained in emergency situations and can assist in an unsafe situation or in an emergency. They advertise help for being lost, walking in an unfamiliar place at night, or for a medical emergency. You can personalize it to have call family members, or they can make calls like a locksmith, roadside assistance, or 911. They are marketed toward older adults and seniors. Their technologies for this demographic tend to be underleveraged. After evaluating the information, some questions and concerns: If you connect directly with 5 star instead of 911 could valuable time be lost connecting with 3rd party? You can talk to 5 star about medication, exercise and nutrition, something you might need to go to clinic for. If someone is accustomed to pushing the button to chat in a real emergency, would they be too familiar with it to call 911, and could this cause confusion?


Are seniors paying for services they might not need? What if the device is deactivated and you can’t communicate with the owner? What does 5 star do if unable to communicate with the person? Call family? Look at personal profile? Contact 911? Wasn’t a lot of info as to trouble shooting a call where they couldn’t communicate with the person. Kelli says if anyone would like her to research any apps, let her know and she will look into it. . GIS PROJECT AND EMERGENCY SERVICE MAP VIEWER INFORMATION (ADAM ITEM) Dana says Iten is on a data collection and assessment trip. If you look at the map in your packet, all counties highlighted in green have had data preparation completed. All of NE except for Pine county, all of SE and now working on CM. Adam has a couple weeks scheduled in CM so he will be covering it soon. His goal is to meet with all of the counties by fall 2017. Would like to have all of the data prep work completed for counties in Metro regions that have already had their meeting and are engaged with statewide portals or in case of Metro, working with Metro GIS portal. That project is moving along well. Adam asked that she convey thanks and appreciation for all of you who have welcomed him and his team into your PSAPs to get this project kicked off. Emergency service boundary map viewer. Wahlberg and Craigie saw a demo on this. Iten and MNGEO are working hard to provide an initial version of a statewide boundary map and are working to resolve gaps and overlaps. Pushing to have it ready by the time we deploy Text-to-911. It will be a layer that will reside over the top of your own mapping layer. If you don’t have mapping, you will have access to it that will plot the coordinate of the call if you receive a text – the coordinate of that text will plot on the map and will be easily identifiable what jurisdiction the caller is in or which should have received the text if every PSAP were receiving texts. Working hard to get that going. Looked impressive from the demo. It is likely there will be a little window that will pop up that will tell you name of county and the 24/7 phone number to relay the text info verbally to them. Hoping to have gaps and overlaps removed by June of this year so it will be avail for PSAPs by the time we deploy text to 911. GIS standards committee meets monthly. They have a goal to gain formal approval of their standards by this summer. It is a very engaged and large group. They are making regular forward progress. Latest issue of newsletter is in the final stages of editing and should be available on the ECN website soon.

Pankonie asks what browser this will be on. Craigie says it is a layer that goes over your current software and your own GIS people can download it.

Diehl said Mille Lacs will be taking calls for CM but they would need the map for all of CM. Not everyone has everybody’s map yet.

Craigie said it could be statewide, or they can do your region plus a county buffer. Wahlberg will get more info from Adam and says it was her understanding if you don’t have mapping application and you overlay this, there was a web browser you could view it in. That is all you would get, though.

FIREWALL RFP AND ABANDONMENT/ALTERNATE ROUTING (DAN CRAIGE) RFP – this is the first time a lot of people have done this in MN. From an administrative point, for purchasing. Alternate abandonment routing—we have a solid understanding and a document was submitted by West and Century Link within a SIP environment and a non-SIP environment how these routes will work. Wahlberg and


Craigie will meet with the regions to talk about this face-to-face. We will have a one-page document we will send out before the face-to-face meetings. WERM STATUS/LANGUAGE LINE UPDATE AND REGIONAL TRAINING BEST PRACTICES (DUSTIN LESLIE) Leslie says WERM is up and running. We are working through some bugs with MESB, but the actual functioning parts are working. PSAPs should be getting their emails. If you need help, first go to regional contact that you can find in the Contacts tab in WERM. If the regional contact can’t help you, you can contact Leslie.

Pankonie asked if that is all vendors, and Leslie said we are still waiting on T-Mobile. County plans—he has gotten a lot more plans in with help from regional leadership. He is waiting on 12 and is in contact with 8 of those. He is waiting on four counties about getting their county plans in. In the meantime, he will contact people by phone to do a final follow up.

Regional standards – we are getting closer. Some regions are farther than others. The trend is that a lot are using the Metro standard as a template.

Central has draft complete,working on getting approved by RAC.

South Central has an initial draft completed, with a meeting February 22 to get counties together to see what they want to add or take away from that.

NW has a draft that goes before their RAC on March 8.

SE is putting people together for a round table meeting.

NE is working on a round table meetings. Had to reschedule their meeting from January.

Rick Juth says the difference between standards and best practice is important. CM isn’t going to have a standard but they are doing it as best practice. Don’t want to lump all these under standards.

Leslie says a few regions said they will do best practices instead of a standard – CM and SC are doing it as best practices.

Leslie says he and Wahlberg sat with a Language Line account executive, who provided some statistics from Language Line last year. Total of 9185 calls, average length of call 7.1 minutes, average connect time 16.2 seconds. Most three used languages: Spanish 68% Somali 18% Hmong 6% One issue that was brought up is that Somali translators are harder to hire and retain, so it takes a lot longer for dispatchers to connect with Somali translators. They have made it a priority to hire Somali translators, and the average connect time has been reduced over the year. They are currently BETA testing a video function that officers will be able to use in the field. Once it is out of testing, an officer can download the app on smartphones and use it in the field. It will help PSAPs, as our language line access number is to be used by PSAPs for processing 9-1-1 calls only. Law Enforcement or other public safety


responders are not to be given our dedicated number to use. There was no cost given for the video service. Voice calls are currently $1.45 per minute on the State contract. Wahlberg said the video piece is coming and the RFP is about due to come out for the state contract. TEXT-TO-9-1-1 PSAP DATA READINESS RESPONSES (MISSION CRITICAL PARTNERS) Sherri from Mission Critical Partners— ECN worked with vendors to determine technical requirements for accepting integrated Text to 911. We prepared a readiness checklist that was distributed to all 104 PSAPs, we have 88% of them back. The readiness checklist is based off the form that the wireless carriers require when you’re requesting text to 911 request. We have been reviewing the response results to determine how to cover the initial seven regions that you can have a statewide texting deployment. We made good progress. ECN will use that data to put together a statewide texting plan and timeline for the rollout of the deployments. We hope to have a high-level timeline at the next meeting. In relation to the state plan, at the next meeting we would like to bring the statewide high level texting plan for the state. At least here is who is in the first and second round. We have a couple of regions that we need to nail down. Wahlberg says one of the challenges is working with Airbus and IES and getting info from them on when the VESTA regional PSAPs are going to be upgraded. There seems to be some confusion. Airbus doesn’t think they have the info from West that they need. They want to know when West will have the ESInet connected to the TCC because they need to know that before they can do some of their call flow work. Dana is trying to get West to answer yes or no—why is the ESInet no longer connected to the TCC, because we’ve had connectivity for testing? She thought that was never turned down. She is trying to figure out what IES and Airbus need that they don’t have today. One email said MN needs to tell the carriers that we are ready to go. We can’t do that until the PSAP equipment is ready. She is trying to work with West to get some answers on that. We are waiting to find out some of the vendor timelines before we can format a predictable timeline. We will continue to work to resolve this question. It is important that the regional PSAPs sign an MOU (Memo of Understanding) with the other PSAPs in the region for which they will be answering texts on their behalf. A sample one from another state was provided last month. Dana will work on a template that would be recommended as a starting point for our PSAPs. A lesson learned from other states was that there was not a sunset clause, so we will recommend December of 2018. At that time the expectation would be that PSAPs would be well on their way to being upgraded. There are more PSAP CPE’s that are not ready, and we need to encourage PSAPs to move forward on upgrading. Wahlberg will draft an MOU in which you can add any specifics for your region and PSAPs. Language that we do not want you to change will be noted in highlight. Judy Diehl said she ran the idea past their county attorney, who asked if this would be a caveat to the Central MN MOU that is already in place for things like sharing the logger. The next time the ESB redoes it’s MOU we could update it. Wahlberg says without seeing CM MOU, she recommends an amendment to the MOU that would include a specific end date. Diehl says she thinks it took a couple of years for the MOU to finally be approved by 19 or 20 different county attorneys. Tom Egan from Douglas County says they received the Patriot in 2012 and upgraded with Vesta a year later. They are now at the 5-year point for hardware replacement for e911 equipment and are visiting with IES about that as well as asking them about the SIP connection versus hardware stuff. They don’t want to purchase new hardware if it won’t be compatible to NG 911 stuff as we know it today. Not getting any info from IES and Airbus.


Wahlberg asks if they are asking IES for a version update to a VESTA 6.1 platform? Egan says we are on 4.2 on VESTA and with their hardware replacement, a contractual issue, we’re asking them for compatibility of this new hardware which we’re not purchasing until we know this, but we need the info on the 6.0 upgrade as well as getting quotes and prices for moving forward. It doesn’t seem like they know anything at this point. Judy Siggerud has also requested info and doesn’t know if West is holding them up, but Otter Tail is waiting for budgetary things. Jill Bondhus says they had a consulting company go through their system and they were told they were NG 911 compliant but found out they need to do a complete 911 update. The consultant says they really don’t have a true picture of how many hours long it is going to take. Airbus said X hours and IES duplicated. West copied that. Our upgrade came to $300,000, and they aren’t going to proceed with being one of the agencies in the region because they didn’t know how much it would cost. She doesn’t think they have an understanding of how much tech time it will take to do the project, which is causing delays for figures to come thru. Dana says there we a number of PSAPs that bought Sentinel Patriots about 4-5 years ago and thought they were buying the latest and greatest t available. A lot of them were Rescue Star PSAPS that knew they were coming up against end of life restrictions with their call handling system so they purchased Sentinel Patriots. Not sure if it wasn’t communicated at that purchase time that any CPE equipment is like purchasing a computer and not like an old analog telephone that was going to last for 20 years. She thinks there was a misunderstanding or lack of communication. Wasn’t a part of any of those presentations so she doesn’t know what was understood by PSAPs. Those Sentinel Patriots are all being upgraded to the Vesta platform. If they are 4-5 years old they are getting basically a complete refresh, (Polk bought 250K four years ago and now finding themselves if they want to do 911 test integrated with their CPE, they need to do another 250k and it’s not something they had considered.) IES/Airbus are not charging PSAPs anything for software upgrades if PSAPs have maintenance agreements, which it appears all of them do. However, IES/Airbus have identified integrated text requires a significant number of engineering hours and they are charging time and materials for this separate from the maintenance agreements. IES as a channel partner of Airbus and will be relaying on Airbus to be on site for the initial deployments until their technicians feel trained to complete them independently. Overall, NextGen 9-1-1deployment is costly. It is noted at a federal level. The FCC had a workgroup under the TFOPA Committee dedicated to look at how to manage the costs. One recommendation from the FCC workgroup is that there are too many PSAPs and some should be consolidated. ECN are neither proponents or opponents of that recommendation. Grant funding was provided to MN regions several years ago to complete consolidation studies. Shared services are being explored within regions now, given the identification of significant cost increases. Nancy from Polk says when they purchased the Patriot they were told they were Text-to-911 ready but they aren’t. And now to say it isn’t and it will cost another $250,000 to receive texts. That is the rub. Douglas County was told the same thing. Sherri -- unfortunately vendors make claims that are not always true. Nancy says that is why Polk is not ready to fork over another $250,000 early. Dar brings up other fees, licensing, etc. She asks if there were going to be examples in the NG911 plan what the costs should look like for people. She thought ECN asked the vendors what steps were involved and to specify the


equipment. Mike Beagles says we have asked repeatedly. They say all VIPERs are ready if they are on 5.3 or greater. Power 911 is the interface. If their VIPER is at that version and Power 911 is ready for that, that version is ready for text. They did not mention a licensing fee. Mines says the invoices are not specific enough about what being charged for. Make sure vendors are spelling out how much is licensing, is my MIS up-to-date, etc. She thinks we need a more detailed check-off list for PSAPs. What is necessary for recording? Mike Beagle will take the question about licensing fees to CenturyLink Project manager. Quote for $25,000 licensing fee (DAR) If you have quotes, concerns, email Mission Critical Partners Dana says we are getting conflicted information on questions. STATUSBOARD (CATHY ANDERSON) Cathy Anderson met with MN.IT regarding updates and upgrades. They will figure out hours and cost and she will bring it to Jackie. These are the things the regional StatusBoard administrators requested.

OLD BUSINESS

INTEROPERABILITY CONFERENCE (DANA WAHLBERG)

The NG 911 track is finalized. We took the feedback from this committee and incorporated into the program. We didn’t have a lot of feedback. Hopefully it will be valuable info. May 1 -3, keynote speakers are being solicited right now.

NEW BUSINESS

2016 ATTENDANCE AND ROSTER REVIEW (CAROL SALMON)

Attendance document attachment for committee review to ensure attendance was recorded correctly for 2016. Let Carol Salmon know of any inaccuracies. Soliciting input from committee to fill vacant positions.


ROBOCALLS TO PSAPS (DANA WAHLBERG)

Discussion around RRRDC receiving significant number of robocalls. Dan Craigie has engaged CTL, Sprint, Level 3 but is having a difficult time determining the root cause. He will continue to troubleshoot this. Any other PSAPs who experience this should report occurrences to Dan.

9-1-1 CALLS FROM APPLE WATCHES (DANA WAHLBERG)

Edina PSAP has reported several instances of Apple Watches inadvertently placing calls to 9-1-1. Apparently a design enhancement on the watch is causing this. This is mostly an FYI. Apple has not made any statements indicating they will modify their design.

STATEWIDE NG911 PLAN AND TEXT-TO-9-1-1 AMENDMENT (DANA WAHLBERG)

These documents will be distributed with the March meeting materials for Action.

VOLUNTEERS TO CREATE TEXT-TO-9-1-1 OPERATIONAL STANDARD (DANA WAHLBERG)

Dustin Leslie and Cathy Anderson are soliciting regional representation, especially from those PSAPs set to initially deploy Text-to-9-1-1 for the operational standard workgroup.

REGIONAL REPORTS

Northwest (Shafer/Olson) Northeast (Olson/Erickson) Central (Diehl/Norstegard) South Central (Wallace/Reimers) Southeast (Betcher/Evers) Southwest (Westfield/Ebert) Metro (McPherson/Bowler)


STANDING COMMITTEE REPORTS

NG911 BEST PRACTICES (DUSTIN LESLIE) Leslie reports that the Central region has drafted their NG911 Best Practices and it is going through the review process. The other regions have meetings scheduled. The Southwest region may need someone to help with the best training standards.

GIS SUBCOMMITTEE (ADAM ITEM) Presented above under ECN reports. ADJOURNED at 2:56 p.m.

March 2017 Minutes

NG911 Committee March 2017 Page 1

STATEWIDE EMERGENCY COMMUNICATIONS BOARD NG911 COMMITTEE

March 15, 2017

MEETING MINUTES Attendance Member/Alternate Darlene Pankonie, Chair/ Capt. Kathy Hughes, MN SHERIFFS ASSN Nancy Shafer/ Jill Olson, NORTHWEST MINNESOTA Steve Olson/ Patrice Erickson, NORTHEAST MINNESOTA Judy Diehl/ Jody Norstegard, CENTRAL MINNESOTA Wayne Betcher/ Faith Evers, SOUTHEAST MINNESOTA Pat Wallace/Peggy Reimers, SOUTH CENTRAL MINNESOTA Joe Reith/vacant, SOUTHWEST MINNESOTA Mary Borst, Vice Chair/Marion Larson, MAA Ross Tiegs/Vacant, MN CHIEFS OF POLICE Tim Boyer/Christine Krajsa, STATE PATROL Matt Goodman/vacant, GIS Dana Wahlberg/Adam Iten, ECN Deb Harmon/ Vacant, TRIBAL PSAP Christine McPherson /Susan Bowler, METRO MINNESOTA Ward Parker/Vacant, MN FIRE CHIEFS *Members attending are marked with yellow highlight. Guests reporting: Tom Egan, Douglas County Brandon Larson, St. Cloud Mike Henrion, Douglas County Rick Juth, ECN Judy Siggerud, Ottertail County Caitlin Christenson, Stevens County Mary Phillipi, RRRDC Mary Terway, Stearns County Nancie Pass, Ramsey County Kim Hegg, West Matthew Hoffer, CTL Jake Jacobson, CTL Dan Swiderski, CTL Mike Beagles, MCP Sherri Griffith Powell, MCP Chris Meyers, Motorola Dan Craigie, ECN Kelli Peters, ECN Cathy Anderson, ECN Carol Salmon, ECN

CALL TO ORDER

Chair Pankonie calls the meeting to order at 1:14pm. NO QUORUM (NE joined later in the meeting for a quorum, but not in time to go back)


APPROVAL OF AGENDA

No quorum – deferred to next meeting

APPROVAL OF PREVIOUS MEETING’S MINUTES

No quorum – deferred to next meeting

ACTION ITEMS

STATEWIDE NG9-1-1 STRATEGIC PLAN: (DANA WAHLBERG) Meeting packet contained 4 documents for which intended action was anticipated. Without a quorum, we will discuss the 4 documents and defer action to April meeting.

Document 1: NG9-1-1 Strategic Plan that was drafted in 2011. Never officially approved by the NG911 Advisory Committee which at that time was under the MSA. Now that NG9-1-1 is formally under the direction of the SECB, we want to approve the Strategic Plan and bring it to the SECB to be used as a living document moving forward. We have followed the steps as identified in the 2011 Plan and will continue to expand on it through amendments.

Document 2: Progress Report which provides high level accomplishments from 2011 when the Plan was introduced to the present. Included for continuity purposes.

Document 3: Amendment 1 to Statewide NG9-1-1 Plan (SIP Enablement Guidelines). This amendment describes the method in which we will migrate all of our PSAPs from an analog (CAMA) conversion to the CPE to a end to end SIP environment.

Document 4: Amendment 2 to Statewide NG9-1-1 Plan (Text to 9-1-1). This amendment describes the method in which we will migrate MN PSAPs to becoming text to 9-1-1 capable. All of the documents are designed to provide high level information to the SECB as well as to legislators and elected officials. These are not intended to be technical in nature. Both technical and operational standards documents are being drafted. The Strategic Plan and subsequent Amendments are intended to educate and assist the SECB in prioritizing and approving future deployment projects of NG9-1-1 along with those of ARMER, FirstNet, and IPAWS as we focus as a state on the convergence of public safety networks. Chair Pankonie noted that feedback provided in the February meeting has been incorporated into the SIP amendment. Amendment 1 specifies the firewalls are required. Technical diagrams were also removed to keep the document higher level. Dan Craigie credited Pete Eggimann and others in the metro for their efforts in enhancing the SIP amendment. Kathy Hughes questioned the December 31, 2018 date identified in Amendment 2 (Text to 9-1-1). What if a PSAP is not ready then, the regional PSAP just cannot stop taking them on their behalf? Sherri Griffith Powell explained the December date gives PSAPs time to plan. It is not necessarily a deadline for all PSAPs to accept their own texts, but a timeframe within which they should be able to set a plan on whether they intend to accept their own, or desire to contract with another PSAP, either the regional PSAP, or perhaps another PSAP in their region, which may be in closer proximity and with whom they work more closely. Dana Wahlberg explained the selection of a sunset clause to this amendment is based on feedback from other states, including North Dakota, who wish they had inserted sunset language, in lieu of leaving it open-ended.


Following this discussion it was agreed that some clarification will be inserted into this paragraph in Amendment 2. Sherri Griffith Powell will modify the language and the document will be sent out in advance of the April meeting. The intent will be to take action in the April NG911 Committee to approve all 4 documents and bring them to the SECB at the May 1, 2017 meeting held in person in St. Cloud during the Public Safety Communications Conference.

ECN REPORTS

E911 AUDIT AND APP REPORT OUT: (KELLI PETERS) 39 of 98 E911 audits have been submitted. The due date of March 31 may be extended if there are items being resolved. Questions about eligible expenses to include on the audit should be directed to Kelli Peters.

ECN’s Kelli Peters and Dustin Leslie recently completed field testing with LaaSer Critical Communications, LLC. They have developed an emergency services location determination and call routing platform that they believe largely solves the Phase 1 routing challenges and provides significantly more accurate location information to 911 call takers. The software is imbedded into the smart phone. LaaSer provided five cell phones, four with service from each of the four major wireless carriers, and the fifth was equipped with the LaaSer technology. Test calls were placed from four different locations. The goal was to see if the location accuracy was more accurate with calls placed from the LaaSer equipped phone. LaaSer is partnered with IBM. In each of the test cases, the four phones using wireless carrier technology provided varying degrees of not only location accuracy. In some cases calls even routed to the incorrect PSAP. The LaaSer technology was well-received in the PSAP. The calls presented with accurate Phase 2 location as a VoIP Class of Service. The LaaSer phone consistently reached the correct PSAP and presented more precise location information. They anticipate a June roll out. The software will be part of future operating system upgrades in smart phones.

Some caveats: The technology does not yet work with Text to 9-1-1. There is no plan to equip non-smart phones with their software. There may be data privacy violation concerns with LaaSer’s intent to share their “advanced data” collection with PSAPs for subscription.

Refer to the attached information documents. More information may be found at www.laaser911.com

Chair Pankonie notes that it is the PSAPs that will ultimately be evaluating apps and software solutions and making recommendations through the NG9-1-1 Committee to the SECB on what apps or software solutions and/or feature enhancements appear to be the best suited for public safety and the citizens of Minnesota. Plan to have more discussion on this down the road. Dana Wahlberg notes this is why ECN has Kelli doing a monthly report out on an app or a software solution. Any PSAP that comes in contact with an app or software solution is encouraged to share that with Kelli to research.

Rick Juth questioned if the calls may have misrouted due to the cell sector being provisioned incorrectly, noting that calls, for example, placed from 445 Minnesota St., one of the test locations, should be routing to Ramsey County and not State Patrol. Dana Wahlberg notes will be part of the after-action activity to review the wireless provisioning. ECN tests phones from our office on Minnesota St. About 50% of the time, wireless calls route to Ramsey Co and 50% of the time, to State Patrol. Given their proximity to the junction of Hwy 52, I-35E, and I-94, it is likely there may be some tower sites that are designated to go to the State Patrol.


GIS PROJECT AND EMERGENCY SERVICE MAP VIEWER INFORMATION: (DANA WAHLBERG FOR ADAM ITEN)

Data Collection, Assessment, and Preparation continues. The NE and SE region counties are completed and visits are currently underway in the Central region. We are collecting GIS data from all of the regions in the state. MNGeo is working with all of that data to prepare it for NextGen purposes. MESB is working independently but closely with MNGeo.

The GIS Subcommittee Standards Committee continues to meet with a goal to have formal approval of the standards this summer.

Issue number 5 of the GIS newsletter is available and has also been distributed.

MNGeo team continues to work on the development of the Emergency Service Map Viewer to have it ready in advance of Text-to-9-1-1 deployment. FIREWALL RFP AND ABANDONMENT: (DAN CRAIGIE)

Dan Craigie says the Firewall RFP was published on March 2, proposals due March 31. We are looking forward to reviewing the proposals. We are on goal for a mid-to-late summer installation. We will deploy the firewalls in phases. We have grant funding to complete 48 PSAPs by the end of year 2017. We don’t have 48 PSAPs on the request list yet. That number was chosen with growth in mind. If there are other sites that are interested to deploy in 2017, we have funding. The vendors must also have resources available. The remaining 58 PSAPs will be eligible for grant money to cover non-recurring costs in future year(s). Dan will be presenting at the MSA conference and the Statewide Public Safety Communications Conference.

ECN has worked with CTL, West, and MESB and together we have developed an excellent informational document that may be used as a guide for determining Alternate and Abandonment Routing Rules going forward. Dan will be visiting each region to discuss alternate and abandonment routing options in depth, both in the traditional environment (for PSAPs who have not migrated to SIP), as well as for a direct SIP environment (for PSAPs who have migrated or have plans to migrate this year). Please reach out to schedule a meeting. It is important for PSAPs to understand the options available to them as compared to what existed in the past.

REGIONAL TRAINING BEST PRACTICES/WERM: (DANA WAHLBERG FOR DUSTIN LESLIE)

WERM has been up and running. There have been some glitches, which have mostly affected the Metro. We’ve had some calls between the Metro and Verizon and West. Verizon is assigning Lat and Long on each sector and it is affecting the process in WERM in that these tower sites that have already been provisioned are showing up as new sites but they are not. It does not seem to be impacting Greater MN as much. Greater MN should let Dustin know if you are experiencing this.


Some of the Points of Contact have not been receiving the heads-up email. Alert Dustin if you are not receiving these emails and learn of pending sectors only by logging into WERM to check. We want to make sure this is working. Steve Olson asks who the point of contact is for the NE with Kerry Swenson’s departure. Dustin will address this. TEXT-TO-9-1-1: (MISSION CRITICAL PARTNERS AND DANA WAHLBERG)

Dustin is attending a metro region round table discussion this afternoon with a group working on text to 911 operational standard for the metro. He and Cathy Anderson have been soliciting for a workgroup with representation from every region to work together on the Statewide Text-to-9-1-1 Operational Standard.

Regional Text to 9-1-1 PSAPs:

NE – St. Louis County – Viper NW – Beltrami County – Vesta Central – Mille Lacs County – Viper SE – Olmsted County – Viper SC – Waseca County - Viper SW—Nobles and Lyon – Vesta (dividing region 50/50) Metro—Hennepin County – Vesta (dividing region – TBD)

A draft Technical Standard has been created and will be included in next month’s meeting packet. This addition will bring to total, five documents for which we will be seeking approval to move onto the SECB May 1 meeting.

We are expanding the FAQ document (Part II) as well as and the Communication document for Text-to-9-1-1. These will be shared with this group and will be available at the ECN booth at the PSAP Conference in Alexandria.

Chair Pankonie is still waiting for an overview of what the CPE equipment requirements are for both Viper and Vesta to migrate to Text-to-911. The vendor quotes have been inconsistent and inaccurate which has led to much confusion and discussion of what PSAPs intending to deploy actually need. It makes planning difficult. Jake Jacobson from CenturyLink states they have been sharing information with the state, and he was thinking the state was going to provide that document. IES and Airbus are assisting in providing the same information. Dana Wahlberg confirms she received info from CTL but has many follow up questions and is not comfortable sharing it until she feels confident in the accuracy of the data she has received. She reports that there appear to be some misunderstandings on the parts of the vendors who are providing quotes for MN PSAPs. Through our NG9-1-1 contract with West, the state is paying the monthly recurring cost for text on behalf of all MN PSAPs. If you received a quote from either IES or West that identifies licensing fees –those are not applicable to our PSAPs under this contract. West exited their entire Midwest sales team in 4Q 2016. Our area is now being covered by sales teams from other parts of the country who are not familiar with the CTL/West - State of MN NG9-1-1 contract. When you do receive a quote from your CPE vendor, please come to us with any questions or concerns so we may seek clarification. Chair Pankonie says that helps if we can share the quotes, but she would still like that piece of paper on the front end. Dana has tried to escalate that and there has been so much incorrect info that she does not feel confident that she has accurate info that is consistent and conclusive. An attempt will be made to share such document with the next meeting packet.


STATUS BOARD: (CATHY ANDERSON) No unplanned outages in February. Nothing else to report

OLD BUSINESS

Upcoming Conference Reminders: There will be excellent breakout sessions on NG911 topics at both conferences. PSAP Conference March 20-23 in Alexandria Public Safety Communications Conference May 1-3 in St. Cloud

2016 ATTENDANCE AND ROSTER REVIEW (CAROL SALMON)

During the next month, we will be updating the NG911 membership roster. We will include a list of vacancies we desire to fill, rules about attendance and meeting a quorum. Going forward there will be a number of items requiring action on the part of the NG9-1-1 Advisory Committee to bring forward to the SECB, thus meeting a quorum in order to conduct business is paramount.

NEW BUSINESS

PROPOSED NG9-1-1 LEGISLATION (DANA WAHLBERG) Note the handout in the meeting packet announcing congressional legislation being introduced by Senators Klobuchar (MN) and Nelson (FL) to help spur the deployment of next generation 9-1-1 across the nation. The legislation maintains the current 9-1-1 state and local government structure while providing assistance from the federal government in the form of grants to assist states upgrade to next gen. The grant program will include conditions to ensure that the funding is used effectively. States will be required to identify a single point of contact and develop an NG9-1-1 deployment plan built upon accredited non-proprietary standards. It will be important for the NG9-1-1 Advisory Committee to begin to discuss our vision for next feature enhancements subsequent to, and/or in parallel with the Text to 9-1-1 Deployment, the GIS Project, and the SIP/Firewall Deployments.

VOLUNTEERS TO CREATE TEXT-TO-9-1-1 OPERATIONAL STANDARD (DANA WAHLBERG)

We have five volunteers from throughout the region. We are looking for more volunteers, we would prefer to have one person from every region to participate, with particular interest in having a representative from the regional text recipient PSAP. SC and NE regions currently do not have representation. Dustin and Cathy have made a plea to all of the regions to provide representation by this week. Dustin will be at the PSAP conference next week and will be actively soliciting support for this. The first meeting will be planned as soon as there is adequate representation from each region and in advance of that meeting, Dustin will send out a draft Text to 9-1-1 Operational Standard to use as a starting point.


REGIONAL REPORTS

Northwest (Shafer/Olson) Northeast (Olson/Erickson) Central (Diehl/Norstegard) South Central (Wallace/Reimers) Southeast (Betcher/Evers) Southwest () Metro (McPherson/Bowler)

STANDING COMMITTEE REPORTS

NG911 BEST PRACTICES: (DUSTIN LESLIE) No oral report given due to time, however written report follows.

Central Region: Jody Norstegard sent me their final approved copy of the Central Region’s Emergency Communications Professional Best Practices Guide. It has been approved by their Emergency Services Board. Good work, Central Region!

South Central: Peggy Reimers advised me that the region met on Feb 22nd attended by a good majority of the PSAPs. They came up with a draft that will be up for approval with their Chiefs and Sheriffs. If they do not have any issues with it, it will be up for approval at the Owners Operators/Users Committee on April 5th.

Southeast Region: Wayne Betcher sent in a draft for their Minimum Training Requirements proposal. The region will be bringing it to the SE region on March 16th for discussion before getting it approved at the O&O meeting in April.

Southwest Region: Joe Reith has stepped down as the regional NG911 contact as well as the subcommittee representative. Randy Willis has connected with Jon Schacherer from Chippewa to take over the role.

Northwest Region: Nancy Shafer sent me the final approved version of their NW Region Minimum Training Recommendations. It was approved by their board and RAC. Good work, Northwest Region!

Northeast Region: I am still trying to get a hold of Steve Olson for an update. Last I spoke they were trying to get a meeting together but did not have a specific date set.

GIS SUBCOMMITTEE (ADAM ITEM)

Provided during ECN GIS report. ADJOURNED at 3:00 p.m.

911 Strategic Plan

Minnesota

Department of Public Safety

Emergency Communication Networks

Next Generation 9-1-1 Strategic Plan

i

DOCUMENT CHANGE HISTORY

Version Publication Date Description of Change

Draft 1 07/27/2011 Internal review

Final Plan

Plan Progress Report

Amendment 1

Amendment 2

ii

Executive Summary

Recent reviews by the National Emergency Number Association (NENA), the United States Department of Transportation (USDOT) and the Federal Communications Commission (FCC) formalized a reality which those working closely with the 911 environment (technology, governance, funding, legislation, etc.) already knew; change is required to meet current and future requirements for those requesting- as well as those providing, emergency services. The new environment is referred to as Next Generation 911 (NG9-1-1). Call patterns have shifted over the years and currently the majority of calls to 911 are from wireless devices (estimated in the range to 70% – 75% of calls). This presented a challenge to 9-1-1 call location processes which resulted in the Wireless Phase 1 and Wireless Phase 2 programs to improve the accuracy of wireless call location information. This was purely a technical challenge. The advent of new communication capabilities such as texting, still photo and video challenges the entire 9-1-1 environment. The industry is early in the definition of new technology standards, as well as developing positions with regard to funding, collection and remittance regulations (i.e. administration). Technical standards are emerging which provide a starting point for vendors to begin developing systems. There is no doubt that these standards will evolve and system changes will be required and that vendors will rise to the task and keep their products current. The industry has also produced discussion and directional documents covering administrative changes necessary to support NG9-1-1 service. A more daunting task than development of the technology is the development of new legislation to affect administrative changes, given that the “9-1-1 community” is a part of a much larger “telecommunications industry and governmental body” with multiple federal, state and local governing entities. It is a time where the path to the end is not crystal clear; however, it is a time when strategies must be developed to meet the new challenge. The Minnesota Emergency Communication Networks partnered with local authorities via the 9-1-1 Advisory Committee to develop a strategic plan to establish the framework for initiating and guiding projects to implement the Minnesota 9-1-1 community’s vision as it relates to the challenge. The strategy employs a phased approach in which one phase builds on the previous. The current framework is divided into four phases.

Phase 1 – Call Transfer Interoperability This phase addresses the need to transfer calls between any of the current Public Safety Answering Points (PSAP) in the state with the data required to accurately identify the location of the caller. The phase successfully completed in September 2010.

Minnesota ECN Strategic Plan

iii

Phase 2 – IP Connectivity Proof of Concept / Legislation, Governance and Funding Review Phase 2 is designed to provide Internet Protocol (IP) connectivity within the 9-1-1 network. This proof of concept involves a limited number of PSAPs to reduce risk. IP connectivity is a fundamental requirement of the NG911 technical infrastructure. Phase 2 also provides recommendations for revising existing statutes and rules to reflect the NG9-1-1 administrative environment as we know it today. The recommendations provide for aligning the current legislative documents with known changes. This phase is scheduled to complete in the fourth quarter 2011. Phase 3 – IP Connectivity Full Implementation Following the successful completion of the proof of concept in Phase 2, IP connectivity will be rolled out to all PSAPs in the state. This positions the Minnesota 9-1-1 system for the commencement of the NG migration. Phase 3’s completion date is July 2013. Phase 4 – i3 Implementation With the IP connectivity in place the migration to the NG9-1-1 technology can begin. The functions of this technology are often referred to as “i3 functions” following NENA’s designation. In the end state, these functions will deliver the vision of ubiquitous connection to emergency services from all communications devices with advanced data presented to emergency service professionals which support their duties. Recognizing that NG9-1-1 is a transition and not an event, a plan will be developed which takes advantage of the then current capabilities and addresses issues facing the Minnesota 9-1-1 community.

This planning effort was undertaken with the full knowledge that in this nascent stage of NG there will be changes which affect the strategic plan. A commitment to the review and revision of the plan is being made so that the state remains on track to a successful implementation of NG9-1-1.


P a g e | 4

Table of Contents Introduction ................................................................................................................................ 5

Overall Vision ............................................................................................................................. 7

A Phased Approach to the Vision ........................................................................................ 8

Technology ............................................................................................................................. 9

Legislation, Governance and Funding Review .......................................................................10

NG911 i3 Compliant Functions .......................................................................................13

NG911 Database Services .............................................................................................16

Transition Considerations .........................................................................................................17

Public Education ....................................................................................................................17

Statutes and Rules ................................................................................................................17

Governance ...........................................................................................................................18

Funding .................................................................................................................................18

Transition Timeline ................................................................................................................18

Critical Supporting Functions .................................................................................................18

Summary ..................................................................................................................................18

References ...............................................................................................................................20


P a g e | 5

Introduction The public safety community has recognized the need to evolve legacy emergency services networks to next generation concepts which may facilitate new capabilities and services. As such, there are numerous industry associations and Standard Development Organizations (SDOs) defining architectures and protocols for next generation networks. The public safety community desires to take advantage of this work and address the challenge it represents to emergency communications. To this end, work is progressing in other NENA committees to define the specific emergency services architectures and protocols involved. The transition of emergency services addressed by this document relies upon this collective work. Transition to NG9-1-1 is expected to be an evolutionary process, involving technological, operational, economic, and institutional change. In some cases, the path to NG9-1-1 implementation will depend on the underlying infrastructure of the Public Safety Answering Points (PSAP) and 9-1-1 Authorities involved. The NG9-1-1 environment may differ considerably from the current 9-1-1 environment. According to the National Emergency Number Association (NENA) NG9-1-1 is: “...an IP based replacement for E9-1-1 features and functions that supports all sources of emergency access to the appropriate PSAPs, operates on reliable, secure, managed multi-purpose IP networks, and provides expanded multimedia data capabilities for PSAPs and other emergency responders….” Calls to 9-1-1 have been migrating for some time from being predominantly wire-line to wireless. The Wireless Association®, formerly known as the CTIA, reports that as of December 2010, there were 302.9 million wireless connections in the US. This equals approximately 96% of the population. As well, the CTIA also reports that about 26.6% of households are wireless only. The industry had to adjust, and wireless Phase 1 and Phase 2 programs were implemented to improve location information associated with wireless calls. End user devices have changed as well. The devices are much more sophisticated and support a significant number of data services such as text messaging, gaming, streaming video and the downloading and transferring of pictures. According to a study conducted by the CTIA, US wireless consumers used more than 2.2 trillion minutes during the 12 months ending December 2010 (or just over 6.3 billion minutes per day) and more than 2.1 trillion text messages were sent and received (or 5.75 billion text messages per day). There were in excess of 296,000 wireless 9-1-1 calls placed every day in the US. This increasing dependence on new communications technology is changing the consumers’ expectations of how they communicate with 9-1-1. The newer


P a g e | 6

expectation within our communities is that they will be able to reach 9-1-1 using the capabilities of their devices which they use in everyday communications. The current 9--11 system in Minnesota is based on a traditional Public Switched Telephone Network (PSTN). There are two 9-1-1 service providers: Qwest Communications and Independent Emergency Services LLC (IES). Qwest (recently acquired by CenturyLink) is the incumbent local exchange carrier (ILEC) in the state, while IES is a company formed by seven independent telephone companies located in central Minnesota. Both Qwest and IES provide E9-1-1 network facilities, PSAP customer premises equipment (CPE) and ALI database services on a competitive basis. Qwest and IES support a statewide analog network that provides access to 9-1-1. Both companies collect wireline and wireless surcharge fees and remit those fees to the state. The state, in turn, distributes surcharge funds to PSAPs using a legislated formula-calculation system that attempts to distribute surcharge funding equally across the state. Funds from the enhanced 9-1-1 service fee are sent monthly to the qualifying cities, counties, and other governmental entities operating 9-1-1 centers. Distribution is on a modified pro rata basis, with half the amount divided equally among the 87 counties (and included cities) and 13 other governmental entities, and the other half divided only among counties and cities on the basis of percentage of population. Although extremely reliable, the current networks will not keep up with advancing technology and will therefore be unable to guarantee access to 9-1-1 services to emerging communication devices. Currently, the network it is not capable of processing data, such as text messaging, pictures or video. In short, the Minnesota E9-1-1 networks and infrastructure must begin the transition to a modern IP-based network capable of meeting future public safety needs in the state as soon as possible.

Purpose The purpose of this document is to communicate the vision of the Minnesota NG9-1-1 System to stakeholders so that they may be actively engaged in its development and deployment. The Minnesota NG9-1-1 Strategic Plan presents a Minnesota perspective of the system functionality, management, operations, security and governance required to meet current and future user expectations.

Background The first 9-1-1 systems in Minnesota were implemented in the cities of Windom and St. James in 1968. Today, every city and county provides E9-1-1 services. This accomplishment involved the passage of legislation, the establishment of a 9-1-1


P a g e | 7

funding mechanism, and State assistance to the cities and counties for the purpose of providing public safety services for the citizens of Minnesota. Statewide 9--11 coverage is provided by 87 county systems. All counties are served by selective router-based enhanced 9-1-1 systems with Automatic Number Identification (ANI), and an automatically updated off-premises database, Automatic Location Identification (ALI). The selective router-based enhanced 9-1-1 systems are operated by IES and Qwest Communications. There are seven IES selective routers, serving 60 counties, and five Qwest selective routers serving 27 counties. Having two competing 9-1-1 service providers presents challenges of interoperability among counties served by different 9-1-1 networks and databases. As the cities and counties evolved from basic 9-1-1 to E9-1-1, the networks evolved with limited commonality or standardization. This is also true with regard to the equipment being used on the networks and at the local PSAPs. Minnesota’s E9-1-1 system has served its citizens well, but is based on older technologies and capabilities of the past. The Minnesota Department of Public Safety (DPS), in collaboration with the 9-1-1 Advisory Committee, recognized the need to begin the transition to NG9-1-1 technology, governance and funding environments and began with creating a vision.

Overall Vision The Minnesota DPS, in a continuing effort to provide assistance to counties in the state of Minnesota, recognized the need for a statewide, fully-redundant, fail safe, IP-enabled, state-of-the-art 9-1-1 system for providing 9-1-1 services to the citizens of the State, hereafter referred to as the MN NG9-1-1 system. This vision is in alignment with that held by the NENA, as well as the USDOT. Technology will be built using open standards systems and next generation IP-based networks. NENA envisions an IP-based inter-network (network of networks) shared by all agencies which may be involved in any type of emergency response. In this vision, multiple local networks (e.g. counties) may be interconnected to form regional networks, which in turn may be interconnected to form a statewide network. The ultimate NENA/USDOT vision is that state networks are interconnected such that calls may be received from any communication device and any agency or responder, regardless of location, can participate in the delivery of emergency services as requested by users of the system. To advance a nationwide vision of an IP-based 9-1-1 system, the USDOT assisted in the research and development needed to bring about a more capable IP-based solution design. The overarching goal was to produce a system that supports all types of emergency call delivery and maximizes service responses across a diverse


P a g e | 8

stakeholder community, such as those in Minnesota. The USDOT participation in the NG9-1-1 vision and plan development resulted in several items of reference that included the USDOT NG9-1-1 Transition Plan version 1.0, February 2, 2009, as well as the NENA NG9-1-1 Transition Plan Considerations Information Document (NENA 77-501), Version 1, February 24, 2011. The path to NG9-1-1 implementation in Minnesota strongly depends on the underlying infrastructure involved and the characteristics of the PSAPs and 9-1-1 authorities in a defined geographic area. At the same time, it is also true that Minnesota’s transition to NG9-1-1 will depend on the ability of service networks to deliver NG9--11 content and calls via native IP-based infrastructure to jurisdictions that are prepared to receive it. In this document, we are adopting the following broad definitions of Next Generation:

“NG” refers to the technology, process and legislative environments required to deliver the vision.

“i3” is the set of functional components of hardware and software which deliver the database, validation, routing and policy to connect those seeking service with agencies that provide the service.

“ESInet” is the IP network transport which interconnects i3 components. Minnesota will implement the MN NG9-1-1 system based on the set of evolving NENA standards. There is much discussion in the industry during this early stage of developing the standards, but the State cannot stand still and wait; it must move forward on a well-planned journey. It is anticipated that change will occur for some time so decisions made now must address a path to remaining compliant. Given NG9-1-1 is a transition not an event, and to mitigate the effects of change, the State is employing a phased approach.

A Phased Approach to the Vision In recognition that NG is a multi-faceted evolution and not a flash cut to a new technology, a phased approach is being adopted. The NG9-1-1 vision not only includes technology change, it may also require changes to legislation, governance, funding and PSAP processes. Four phases have been identified as follow: Phase 1 – Call Transfer Interoperability

Phase 1 provides the capability for all primary and secondary PSAPs in Minnesota to transfer a 9-1-1 call to any other primary or secondary PSAP within the state, along with ANI and ALI regardless of the 9-1-1 service provider.


P a g e | 9

This addresses one of the largest problems PSAPs are facing in Minnesota, as well as all over the country. With the reality that wireless calls are the predominant type handled in PSAP, as documented earlier in this plan, and the inherent issues with determining the location of the caller, transfers are critical to ensure the correct PSAP handles the call. Phase 1has successfully addressed this issue. Phase I was completed on September 28, 2010 and is a resounding success for Minnesota PSAPs. As of June 2011, statistics show 75 of the 116 PSAPs have taken advantage of the improved transfer capabilities since the launch. Calls transferred to the Qwest-served State Patrol PSAPs from IES-served PSAPs account for approximately 69% of the call transfer volume. Transfers may be performed from all 116 primary and secondary PSAPs in the state to any other PSAP in the state, regardless of who the 9-1-1 service provider may be. This sets the stage for the next phase, implementing IP connectivity and preparing for other changes required to implement NG9-1-1.

Phase 2 – IP Connectivity Proof of Concept / Legislation, Governance and Funding Review

In Minnesota planning and design is underway for the IP network which will interconnect the 116 PSAPs, 12 Selective Routers and two redundant ALI databases. A robust Multiprotocol Label Switching (MPLS) architecture will be implemented to ensure the performance and security required of this mission critical transport network. Once proven, the full roll out of the network will be completed in Phase 3. Phase 2 also includes a review of state rules and statutes to identify changes required in support of the NG environment.

Technology In the NG architecture, it is required that all elements of technology are connected via an IP network. The new capabilities which are part of the NG9-1-1 vision require transport of data (e.g. texting, video, etc.); the voice grade circuits used in the current state networks are not capable of meeting this requirement. However, once again it is prudent to ensure a smooth transition via a phased approach. The goal in Phase 2 is to provide IP connectivity to a limited number of PSAPs on each provider’s network that will eventually lead to the replacement of the emergency message (EM) trunks and ALI circuits. This phase establishes the foundational IP network known as the ESInet in the NG9-1-1 architecture. Gateways are to be installed at each access point (e.g. PSAP, selective router, ALI


P a g e | 10

provider) to provide legacy interworking since at this stage existing routing and database system which cannot interface with the IP network remain in place. It is anticipated that this proof of concept phase will complete in the fourth quarter of 2011.

Legislation, Governance and Funding Review In addition to the IP network proof of concept, an effort to address the non-technical components of the NG transition in this phase include a thorough review of existing state statutes and rules applicable to telecommunications, 9-1-1, and cost recovery. The intent is to identify outdated language and recommend it for removal or revision through the state’s legislative and/or regulatory process. This activity follows recommendations documented in NENA Next Generation 9-1-1, Transition Policy Implementation Handbook, A Guide for Identifying and Implementing Policies to Enable NG9-1-1, March 2010. This handbook states: “It is important to note that most policy and governance issues should not be addressed by individual Public Safety Answering Points (PSAPs) or even individual 9‑1‑1 Authorities. Given the interconnected nature of NG9‑1‑1 systems, it is important for all 9‑1‑1 Authorities in a region or state, along with other related emergency response and government stakeholders, to jointly address policy and governance issues in a coordinated manner.” This collaboration of “all 9-1-1 Authorities” will continue to be accomplished by close working of the NG911 Advisory Committee and ECN staff.

Governance The NG9-1-1 vision potentially impacts responsibility for systems, but not the responsibility for delivery of emergency services. Governance issues and methodologies must mature as NG9-1-1 standards, systems, and stakeholder experience mature. Minnesota’s vision is supported by state level network & systems. Though regional and state networks are being considered and current statutes provide for their existence, the strategic direction responsibility for emergency service delivery remains at the local level. Funding & Costs Funding and cost distribution models will be researched using the NENA funding model report1 as a guide. There is one funding mechanism in the state of Minnesota, and that consists of 9-1-1 surcharge fees on fixed landline phones

1 Funding 911 Into the Next Generation: An Overview of NG911 Funding Model Options for Consideration March 2007


P a g e | 11

and wireless (cellular) phones. The current funding distribution model will not be changed; however, the existing service fee legislation will need modification to ensure that it reflects today’s funding realities. As well, legislation is in process to address point of sale pre-paid wireless, and “pay as you go” wireless devices. This point of sale approach captures devices not under the umbrella of the traditional emergency telecommunications surcharge service fee. It consists of a point of sale transaction fee assessed for pre-paid wireless as well as pay as you go phones. In addition, the definition of 9-1-1 service must be expanded to cover all appropriate “providers” such as VoIP and other non-traditional purveyors of 9-1-1 capable telecommunications devices. In other words, specific requirements must be developed for service providers delivering calls via non-traditional transport arrangements to accurately identify line equivalents (e.g. Vonage, Comcast, Magic Jack, etc.) It is anticipated that this review will be completed in the third quarter of 2011.

Phase 3 – IP Connectivity Full Implementation

Phase 3 is the last of the two-step process, implementing the full roll out of the network. Full implementation of the network in Phase 3 will be undertaken once the Phase 2 proof of concept is successfully completed. In this phase the remaining PSAPs are migrated to the IP network. At this point the transport infrastructure is in place to support NG9-1-1 routing and database systems. Figure 1 shows the MN NG9-1-1 IP network concept as it will exist post-Phase 3.


P a g e | 12

Figure 1 - MN-NG911 IP Network


P a g e | 13

It is anticipated that Phase 3 will complete in 2012 and positions the state to move forward with implementation of NG i3 components.

Phase 4 – i3 Implementation

Phase 4 involves the implementation of a NENA i3 compliant set of functions which deliver on the visions previously stated. It may be that progress on standards and vendor product development dictates that this effort be further divided into sub-phases. That decision cannot be determined at this time. To further assess industry progress toward providing systems which deliver i3 functionality, a process often referred to as “Due Diligence” will be undertaken to allow for the exchange of information between the State and vendor community. The purpose of Due Diligence is to facilitate the understanding of MN NG9-1-1 requirements as well as the current state of product development applying to those requirements. Based on the results of this process, a plan will be developed to implement i3 functionality.

NG911 i3 Compliant Functions

Though using IP protocol inside the 9-1-1 domain is new, the IP protocol is well established and has been used in other telecommunication and IT domains for many years. What is totally new, are the i3 routing and database functions and systems used to deploy the functions. The core set of i3 functions making up the technology of Next Generation environments are defined in the following standards:

National Emergency Number Association’s (NENA’s) i3 Technical Requirements

Document NENA 08-751, Issue 1, September 28, 2006

National Emergency Number Association’s (NENA’s) Functional and Interface

Standards for Next Generation 9-1-1, Version 1.0, (i3)

Detailed Functional and Interface Specification for the NENA i3 Solution - Stage 3_1

Document 08-003, June 14, 2011

U.S. Department of Transportation’s (USDOT’s) NG9-1-1 System Initiative Concept

of Operations.

The state plans to follow the recommendations and specifications of NENA. An important change in the NG9-1-1 environment is the definition of “calls.” As part of the Phase 2 work on statutes and rules, a recommendation will be made to adopt NENA’s revised definition:


P a g e | 14

“A generic term used to include any type of request for emergency assistance (RFEA); and is not limited to voice.”

NG i3 compliant functions are interworked via standards driven protocols to form a “system” capable of receiving calls, accessing databases for routing and policy data, and connecting to the appropriate answering point. The i3 functions and protocols are illustrated in the figure below. Given the early stages of i3 definition, standards will likely experience changes for several years. To address this reality the state will include a “Due Diligence” process to strengthen requirements definition prior to entering the procurement process. The intent of the due diligence process is to meet with potential service providers of i3 features and functions to learn about the respective service offerings and educate the potential service provider about Minnesota’s needs. These are highly interactive sessions surrounding the information provided by state stakeholders and the service provider. The over-arching goal is to craft an RFP document that ultimately generates thoughtful, relevant, and high-quality proposals from potential service providers. Each i3 function is further described in this section.


P a g e | 15

Figure 2- i3 Functions and Protocols

Border Control Function (BCF) – The BCF provides a secure entry into the ESInet for emergency calls presented to the network. The BCF incorporates firewall, admission control, and may include anchoring of session and media as well as other security mechanisms to prevent deliberate or malicious attacks on PSAPs or other entities connected to the ESInet. Emergency Call Routing Function (ECRF) – The ECRF receives location information (either civic address or geo-coordinates) as input and uses this information to provide a URI that can be used to route an emergency call toward the appropriate PSAP for the caller’s location. Depending on the identity and credentials of the entity requesting the routing information, the response may identify the PSAP, or an Emergency Services Routing Proxy (ESRP) that acts on behalf of the PSAP to provide final routing to the PSAP itself. The same database that is used to route a call to the correct PSAP may also be used to subsequently route the call to the correct responder, e.g., to support selective transfer capabilities. Emergency Services IP Network (ESInet) – This term is used to refer to a private IP network or IP Virtual Private Network (VPN) that is used for communications between PSAPs and among other entities that support, or are supported by PSAPs in providing emergency call handling and response. Emergency Services Routing Proxy (ESRP) – ESRP is an i3 functional element which is a SIP proxy server that selects the next hop routing within the ESInet based on location and policy. There is an ESRP on the edge of the ESInet. There is usually an ESRP at the entrance to an i3 PSAP. There may be one or more intermediate ESRPs between them. i3 Public Safety Answering Point (i3 PSAP) – The i3 PSAP is a PSAP that is capable of receiving IP-based signaling for delivery of emergency calls and for originating calls. The internal functions are not being specified in the i3 requirements, but the i3 PSAP is expected to be able to use SIP signaling for calls and IP-based data protocols for exchange of other information. It is expected that the CPE Technical Committee will produce a document describing the functionality of i3 PSAP equipment. An i3 PSAP is an instance of an IP PSAP, but in this document, we mean a PSAP conforming to the i3 standard. Legacy PSAP – This term is used to describe PSAPs that are not capable of communicating with VoIP protocols or of supporting the i3-based interfaces specified as part of the i3 solution. Legacy Gateway (LNG) – This term is used to refer to a signaling and media interconnection point between callers in legacy wireline/wireless originating networks and the i3 architecture, so that i3 PSAPs are able to receive emergency calls from such legacy networks. Location Information Server (LIS) – A LIS is a functional element that provides locations of endpoints. A LIS can provide Location-by-Reference, or Location-by-Value, and, if the


P a g e | 16

latter, in geo or civic forms. A LIS can be queried by an endpoint for its own location, or by another entity for the location of an endpoint. In either case, the LIS receives a unique identifier that represents the endpoint, for example an IP address, circuit-ID or MAC address, and returns the location associated with that identifier. The LIS is also the element that provides the dereferencing service, exchanging a location reference for a location value. Location Validation Function (LVF) – The LVF is used to validate location objects against the next generation Master Street Address Guide (MSAG). Pre-validation of the location information ensures that the calls can be routed to the appropriate PSAP and that emergency services can be dispatched to the correct location. Multimedia – Multimedia functions might include such things as conference bridge resources, or logging recording services for all forms of media: voice, video and text. Policy-based Routing Function (PRF) – This functional element applies techniques to determine alternate routing addresses based on policy information associated with the destination PSAP. The PRF uses its state knowledge, such as PSAP registration state or time of day and the policy for a PSAP to make a route determination. The PRF resides in the terminating ESInet. Routing Proxy – A term used in SIP to describe a SIP server that receives SIP requests and forwards them on behalf of the requestor. A routing proxy determines the next hop for a SIP message and forwards the message. Supplemental Data – Databases and Database Access Services that provide information requested by PSAPs and other entities on the ESInet in support of emergency services handling.

NG9-1-1 Database Services

The roles of databases are drastically different in NG9-1-1. As with other parts of the architecture a period of dual operation will exists and it must me planned. This section discusses these topics.

ALI The ALI database will continue to be involved in routing 9-1-1 calls until legacy originating networks convert to the NG9-1-1 architecture. There is no indication that this will occur in a short period of time. The i3 architecture calls for Telecommunications Service Providers (TSP) to implement the LIS function which replaces the ALI database in a fully implemented and transitioned NG environment. At the writing of this plan there are no TSP governing body statutes or rules which require the implementation of the LIS. Therefore, this plan accounts for the continued operation of the ALI database as part of transition considerations.


P a g e | 17

Geographic Information Systems (GIS) In the NG environment GIS changes from a storage and mapping system to a key routing component. This change precipitates a review of GIS data management as boundary precision requirements are much higher for routing calls and much higher point precision is required to support the NG vision (e.g. the ability to access structure floor plans and support data).

Transition Considerations The transition has begun. Phase 1 is complete and Phase 2 is well on its way to a successful completion of the IP network proof of concept. Once Phase 2 completes, then Phase 3 is a matter of replicating the successful network to interface with all PSAPs. Phase 4 represents a significant change. It is likely that this phase will be further subdivided in moving to the final NG9-1-1 configuration. A full assessment and planning will be undertaken to achieve a successful transition. This section discusses considerations for that plan as it is known today.

Public Education This is listed first as it is of paramount importance that the public understand the purpose, proper usage and capabilities of 9-1-1. As NG9-1-1 technologies and networks evolve, new methods of accessing public safety services will also evolve. There must be a clear and consistent message prepared and delivered to the public insofar as to what devices currently are capable of accessing 9-1-1 services. As well, the public must be aware of what devices are not yet capable of directly accessing 9-1-1. As NG9-1-1 networks evolve, and as access to 9-1-1 evolves beyond traditional telecommunications devices, public education must also evolve accordingly. Non-traditional methods such as text messaging, instant messaging, and email to name a few, must be included in present and future public education initiatives. The state will coordinate with counties to develop and deliver a consistent message as the phased approach to NG9-1-1 is executed. Existing resources and educational tools such as “Cell Phone Sally”, methods for measuring public education initiatives are available for these purposes.

Statutes and Rules Phase 2 began the revision of state statutes and rules to broaden them to include what is currently understood about NG9-1-1. This process will be repeated as more unfolds during further development of NG9-1-1.


P a g e | 18

Governance NENA’s vision of a “networks of networks” where regional, state and national networks all interconnect and the investment required to implement an i3 based solution requires review of roles and responsibilities. The state will continue to partner with local authorities to collaboratively identify and implement the most efficient model for Minnesota.

Funding Of all the considerations, this is by far the one which requires a more national approach to reach a final position. Changes to Minnesota statutes and rules as part of Phase 2 is only the first step. These changes are targeted at defining roles as they exist in the current transitional state to bring clarity to responsibilities for collecting and remitting 9-1-1 emergency telecommunications service fees (fee). The state will stay current with and participate in industry discussions regarding changes telephone line or equivalent based fees to other methods.

Transition Timeline The transition timeline to NG9-1-1 must include all aspects of the vision as outlined in this document. As expected, timing is highly dependent on NG9-1-1 standards maturation, the legislative process, and the available resources including both people and budget. A baseline will be established founded on the results of investigations associated with developing this strategic plan. It is anticipated that the actual timeline will be a living, dynamic and evolving process that will be updated periodically as more and more is learned in execution of this plan.

Critical Supporting Functions Services such as CAD and logging must interface with new functions and handle new data sources and/or formats. Definition has not progressed to a point that these requirements can be articulated; however, they are included here to facilitate further discussion and inclusion in implementation plans at the appropriate time.

Summary Recognizing the need to evolve Minnesota legacy emergency services networks to next generation concepts which may facilitate new capabilities and services the Emergency Communication Networks partnered with local authorities via the 9-1-1 Advisory Committee to developed a strategic plan to establish the framework for initiating and guiding projects to implement the Minnesota 9-1-1 community’s vision. Work is underway as evident by the fact that Phase 1 is completed and Phase 2 well on its way. The same level of expertise and professional approach brought to bear in these two phases will be used in the implementation of Phase 3 and 4 as well as future projects undertaken in the execution of the strategy.


P a g e | 19

It is anticipated that this will be a living document which will be reviewed and modified to adapt to a changing 9-1-1 environment. The ultimate goal is to continue to provide reliable 9-1-1 service to users in Minnesota and meet the current and future requirements resulting advances in communication capabilities adopted by the public.


P a g e | 20

References

(1) NENA 03-003 Recommendation for the implementation of Inter-Networking, E9-1-1 Tandem to Tandem, February 2000 (Tandem)

(2) NENA 03-005 January 2004 (Issue 1) Generic Requirements for an Enhanced 9-1-1 Selective Routing Switch (SR Standard)

(3) NENA 08-001 v2 - Interim VoIP Architecture (i2)

(4) NENA 08-002 v1 - Functional & Interface Standards for NG9-1-1 (i3)

(5) NENA 08-003 DRAFT - NENA i3 Solution

(6) NENA 08-501 v1 - Network Interface to IP Capable PSAP

(7) NENA 08-502 v1 - E9-1-1 Requirements

(8) NENA 08-503 v1 - VoIP Characteristics

(9) NENA 08-504 v1 - VoIP Standards Development Organizations (SDOs)

(10) NENA 08-505 v1 - Location Determination: IP-Based Emergency Services

(11) NENA 08-751 v1 - i3 Requirements (Long Term Definition)

(12) NENA 08-752 v1 - Location Information to Support IP-Based Emergency Services

(13) NENA i3 Technical Requirements Document NENA 08-751, Issue 1, September 28, 2006 (i3 TRD)

(14) NENA Functional and Interface Standards for Next Generation 9-1-1 Version 1.0 (i3) NENA 08-002 Version 1.0, December 18, 2007 (i3 Standard)

(15) NENA 08-DRAFT - Emergency Services IP Network Design for NG9-1-1

(16) NENA 75-001 v1 - NENA Security for Next-Generation 9-1-1 Standard (NG-SEC)

(17) NENA Baseline Next Generation 9-1-1 Description, February 22, 2011

(18) NENA NG9-1-1 Transition Plan Considerations Information Document, NENA 77-501, Version 1, February 24, 2011


P a g e | 21

(19) NENA Standard Data Formats for ALI Data Exchange & GIS Mapping (Data Standard) NENA-02-010, Version 8.2, June 10, 2009

911 Strategic Plan Progress

Report

Minnesota

Department of Public Safety

Emergency Communication Networks

Next Generation 9-1-1 Strategic Plan

Progress Report

Minnesota ECN Strategic Plan Progress Report

2 | P a g e

040417

Introduction

In July 2011, Emergency Communications Networks (ECN) partnered with local authorities via the 911 Advisory Committee to developed a strategic plan, Minnesota ECN Strategic Plan (the Plan), to establish the framework for initiating and guiding projects to implement the Minnesota 911 community’s vision as it relates to the challenge of Next Generation 9-1-1 (NG9-1-1) implementation.

The strategy employed a phased approach in which one phase builds on the previous. With the support of the 911 Advisory Committee and the local authorities it represents, considerable progress has been made on the journey to the NG9-1-1 vision as defined in the Plan.

Phase Status Date

Phase 1 – Call Transfer Interoperability* Complete Q2/2010

Phase 2 – IP Connectivity Proof of Concept

Complete

Q1/2012

Phase 3 – IP Connectivity Full Implementation Legislation, Governance and Funding Review

Complete Complete

Q1/2014 Q2/2014

Phase 4 – i3 Implementation Ongoing

* Phase 1 was competed prior to the Plan development. It is included for completeness.

Progress Summary

Phase 1 – Call Transfer Interoperability This phase addressed the need to transfer calls between any of the current Public Safety Answering Points (PSAP) in the state with the data required to accurately identify the location of the caller. The phase successfully completed in September 2010.

Minnesota ECN Strategic Plan Progress Report

3 | P a g e

040417

Phase 2 – IP Connectivity Proof of Concept The proof of concept was successfully completed in the first quarter 2012 when Carver County, a CTL/Intrado database supported PSAP and Kandiyohi County, an IES database supported PSAP, both migrated to the ESInet. Phase 3 – IP Connectivity Full Implementation IP connectivity to all PSAPs in the state was completed in February 2014. With IP connectivity in place, the State is positioned to plan and implement i3 capabilities that have matured since the development of the Plan. Legislation, Governance and Funding Review Due to the passage of legislation in 2014, the Statewide 9-1-1 Program was formally brought under the governance structure of the Statewide Radio Board, and the board was renamed as the Statewide Emergency Communications Board (SECB), to encompass planning, coordination, and standards development for end to end public safety networks, including NG9-1-1, ARMER radio, and later FirstNet and Integrated Public Alert and Warning System (IPAWS). Phase 4 – i3 Implementation As envisioned when the Plan was developed in 2011, i3 has progressed from a basic set of standards to implementations across the United States. The 9-1-1 industry is in the early stages of planning NG9-1-1 (i3) implementation. This will require Phase 4 to be broken into additional phases as described below.

The Path Forward

The Plan recognized that NG9-1-1 standards were evolving and would continue to evolve as the industry gained knowledge through trials and actual implementations. ECN is keeping the commitment to review the Plan to keep it aligned with industry standards and best practices. The 9-1-1 Program Manager, with input from the Next Generation 9-1-1 Committee, will provide the SECB with comprehensive overviews which highlight industry trends, along with recommendations for taking the best path forward with continued migration to reach end state NG9-1-1 deployment. Amendments to the Plan

Amendment Number 1 – Statewide SIP Guidelines 030817 Amendment Number 2 – Statewide Text to 9-1-1 Plan 030817 Amendment Number 3 – Statewide GIS Plan Under Development

911 Strategic Plan

Amendment 1

Minnesota ECN Strategic Plan Amendment Number One (1)

1 | P a g e 030817

Minnesota Department of Public Safety Emergency Communication Networks

Statewide SIP Enablement Guidelines Amendment Number One (1) to the SECB Statewide NG911 Plan

PURPOSE Minnesota’s Department of Public Safety Emergency Communication Networks division (ECN) has made significant investments in time and money to build a reliable and robust Emergency Services Internet Protocol (IP) Network (ESInet). It is the goal of ECN to encourage and help guide Public Safety Answering Points (PSAPs) to utilize the ESInet to the fullest extent. The first step is to move away from Centralized Automatic Message Accounting (CAMA) technology by implementing Session Initiation Protocol (SIP) to deliver 9-1-1 calls. The SIP enablement for a PSAP and its customer premises equipment (CPE) will help to bring public safety technology up to the same level used by wireline and wireless carriers when they deliver service to the community.

SCOPE The guidelines in this document are designed to help PSAPs plan for and implement a SIP conversion from CAMA, and to provide them with a better understanding of the tasks, costs, and requirements for this undertaking. PSAPs will be responsible for ensuring that their public safety applications are capable of converting to SIP. If the CPE and/or call-taker applications are not capable of supporting SIP, the replacement of those systems may be necessary and is beyond the scope of this document. Conversion from CAMA to direct SIP ESInet connections requires an update to the PSAP’s 9-1-1 Plan on file with the State.

IMPLEMENTATION GUIDELINES The design goal for any PSAP converting to SIP will be reliability. This is achieved through enhanced functional requirements for SIP and redundancy at the hardware level. In addition, it is required that a final design incorporate SIP-capable firewalls in front of the CPE as a security measure for Internet-facing CPE functions, and as a security layer for future Next-Generation 9-1-1 (NG9-1-1) capabilities. Any PSAP connected to the ESInet will be required to sign an agreement with the State of Minnesota that outlines acceptable use and management of the firewall devices. PSAPs unwilling to accept the installation and management structure defined in the agreement will be disconnected from the State supported ESInet and have to establish connectivity to a 9-1-1 service provider at their own expense, or have their 9-1-1 calls routed to the nearest willing and able PSAP on the ESInet.

CONVERSION COST GUIDE To help PSAP managers prepare for the SIP-conversion process, some associated cost ranges are listed below for a typical conversion from CAMA to SIP. Each PSAP will be responsible for determining the exact costs involved with the conversion and should solicit specific, individual quotes from its CPE vendor, as well as from CenturyLink, the State’s ESInet provider. The amounts provided in Table 1 below are based on the following assumptions:

The CPE is SIP capable CPE version/maintenance is current Cost calculations based on a four-position PSAP


2 | P a g e 030817

Table 1: SIP Conversion Cost Estimate*

Quantity Description Estimated Price Range Estimated Total

4 SIP CPE Licensing $260 – $410 $1,040 – $1,640

4 SIP CPE Support Option $50 – $160 $200 – $640

2 Firewall Hardware $0 $0

2 Firewall Licensing/Support $0 $0

2 Firewall Managed Services $0 $0

120 Vendor Labor Hours $60 – $100 $7,200 – $12,000

30 West Labor Hours $196 $5,880

Estimated Grand Total $14,320 – $20,160

*Pricing is subject to change based on the number of PSAP positions and CPE configuration (CPE may require initial configuration/upgrades to become SIP capable). ** Firewall hardware, licensing/support, and management will be covered by ECN.

FIREWALL MANAGEMENT AND GOVERNANCE Management As Minnesota PSAPs schedule their migrations to SIP call handling, appropriate planning must include the management of the firewall devices that act as a first step in protecting the ESInet from cyber threats and intrusions. These devices are placed at a critical point in the call-delivery path and therefore require consistent monitoring, support, and governance. The State wants PSAPs to stay focused on their core mission, and because of that desire, ECN will provide monitoring and support services for the firewalls that are deployed in a SIP conversion. The management and support of the firewalls will be conducted by a third party that reports directly to ECN. Once a vendor is chosen by the State, it will be charged with the task of monitoring, maintaining, and implementing the firewalls as SIP conversions take place at PSAPs across Minnesota. In general, there will be three areas of focus to sustain the integrity of each PSAP’s network that can be best described as Prevention and Protection, Detection, and Response.

Prevention and Protection includes SIP firewall management and administration, lifecycle and oversight management. The ongoing services also will include consultative support on an as-needed basis, as related to the network firewall use, security, functionality and accessibility.

Detection involves proactive SIP firewall monitoring through the service provider’s Network Operations Center (NOC).


3 | P a g e 030817

Response includes call center support, trouble reporting and problem escalation, along with logging and reporting. It also will include scheduled onsite support and preventive maintenance.

The monitoring and support services component of the SIP firewall implementation will be required for both new and existing SIP deployments. PSAPs with firewalls currently in place that are designed per the guidelines described in this document will be included in the monitoring-and-support-services solution offering, and thus will supersede the PSAP’s existing monitoring/management efforts. Governance Adherence to the standards and guidelines set forth in this document is crucial to ensuring the integrity of the ESInet, as well as each PSAP’s respective network environment . Scheduled and on-demand reporting will be conducted concerning the state of the monitored firewalls across Minnesota, to include the ongoing support provided to them and their settings. ECN also reserves the right to order onsite audits—on a schedule of its choosing—that will report on the functionality, physical layout, and setup of the SIP firewalls at each PSAP. ECN also will work with the appropriate State offices/departments, the Statewide Emergency Communications Board (SECB), and the selected monitoring vendor, to create a standard and consistent ruleset that governs the device configuration policies. ECN, working with the selected monitoring vendor, will verify on a regular basis that all firewall device configurations adhere to the State’s security policies. ECN may ask for input from the PSAP managers regarding the development of the hardware, software, and telecommunications profile, when appropriate. Finally, the ongoing costs for the monitoring and support services will be covered by ECN.

CALL CONTROL CONFIGURATION In a direct SIP environment, the call control that defines how many simultaneous 9-1-1 calls a PSAP can receive is determined by the 9-1-1 answering application configuration, rather than the ESInet. This call control configuration can determine whether a PSAP is in compliance with the 9-1-1 system load capacity required by MN Administrative Rule 7580.0500, Subpart 1, Load, which requires the 9-1-1 system to be designed and operated to maintain a grade of service such that no more than one call out of 100 incoming calls will receive a busy signal on the first dialing attempt during the busy hour of an average week during the busy month (AKA - P.01 grade of service). When PSAPs prepare to convert to a direct SIP connection to the ESInet, the PSAP and the vendor need to work with the MESB in the metro region and ECN in greater MN to determine a 9-1-1 answering application configuration that meets the State 9-1-1 system load requirements.

FREQUENTLY ASKED QUESTIONS Question: Why should I convert to SIP? Answer: SIP is already a primary call-delivery method for the public across the country. It is utilized by multiple entities that provide phone services in Minnesota, and it is a primary and necessary step for the PSAP to take in order to be NG9-1-1 ready. Public safety officials know that the systems fielding the requests for emergency help need to align closely with the capabilities of the devices used by citizens. SIP implementation is a big step in that direction, and many CPE systems currently are in development cycles that are leveraging SIP as the foundation for NG9-1-1 capabilities. Question: What other costs may be associated with my conversion to SIP?


4 | P a g e 030817

Answer: There may be costs associated with upgrading your CPE or replacing it altogether if SIP is not supported. Converting to SIP should be a phase in your upgrade to new CPE. Question: Will I be required to make any updates to my call logger when migrating to SIP? Answer: Depending on the brand, age, and version of your master recorder, there may be some upgrade requirements, especially if you currently record at the trunk level. In a SIP environment, IP recording capability must be enabled. This may require the purchase of a third-party recording kit. In most instances, such a kit is necessary only to accomplish trunk-level recording. Recording at the position level only may not require any logging recorder modifications. It is important to understand that trunk-level recording does not work exactly the same as it did in the legacy environment. All “audio before answer” is eliminated in a SIP environment; thus, there is nothing to record prior to the call being answered by a call-taker. However, the third-party recording kit does make it possible to record during the time a call is placed on hold. Please coordinate SIP recording capabilities between your CPE and call-logging vendors to ensure that your specific needs and requirements for recording are met. Question: What if my PSAP already has a firewall in place? Answer: As the process to select a vendor for the management and monitoring of the firewalls is ongoing, it is difficult to state one way or another. In one scenario, the chosen vendor is able to work with the existing devices and incorporates it into their monitoring program. In another scenario, the vendor is not able to incorporate it and requires their own device and configuration. How and when that process occurs will be done in coordination with the PSAP, their CPE vendor, ECN, and the chosen vendor for the firewall project. Question: How do these costs apply to a PSAP that is part of a shared call-handling system? Answer: This depends on the network configuration between the PSAPs on the shared system and the terms contained in the cooperative agreement in place related to cost management. Question: Can I use my Enhanced 9-1-1 (E9-1-1) money to pay for costs associated with this transition? Answer: Yes.

911 Strategic Plan

Amendment 2

Minnesota ECN Strategic Plan Amendment Number Two (2)

1 | P a g e 040417


Statewide Text-to-9-1-1 Plan

Amendment Number Two (2) to the SECB Statewide NG911 Plan

PURPOSE Minnesota’s Department of Public Safety Emergency Communication Networks division (ECN) recognizes the need to provide all citizens with equal access to the highest level of 9-1-1 service available by implementing text-to-9-1-1. Wireless customers have enjoyed the ability to send text messages to other wireless subscribers for several years and within the Deaf and Hard of Hearing community, this has become a very popular method of communication. The Emergency Access Advisory Committee (EAAC) presented a report to the FCC in July 2011 noting that texting has become one of the preferred methods of communication for the Deaf and Hard of Hearing. Text-to-9-1-1 allows this community equal access to 9-1-1 services for the first time in history.1 Text-to-9-1-1 also offers an alternative method for accessing 9-1-1 services when it is not safe to make a voice call, such as during a home invasion, or domestic incident. The goal of the statewide text-to-9-1-1 plan is to provide a proven method for equal access to 9-1-1 for the state’s citizens and visitors in the most expeditious and cost effective way, while allowing local Public Safety Answering Points (PSAPs) to migrate to the service when appropriate for them to do so based on available funding, policy and staffing.

BACKGROUND In December of 2012, AT&T, Sprint Nextel, T-Mobile, and Verizon entered into a voluntary agreement with the National Emergency Number Association (NENA) and Association of Public-Safety Communications Officials (APCO) International in which each of the four carriers agreed to provide text-to-9-1-1 service by May 15, 2014, to PSAPs that are capable of, and request to receive, text-to-9-1-1 service. The Federal Communications Commission (FCC) has placed a priority on deploying text-to-9-1-1 and in his January 2014 statement in relation to PS Docket No. 11-153, Facilitating the Deployment of Text-to-911 and Other Next Generation Applications, Chairman Wheeler stated “We’ve done our part. Now, the PSAPs must do theirs.” The FCC ruling helped to ensure that 9-1-1 keep pace with new technology, and, most importantly, save lives. ASSESMENT OF OPTIONS ECN has reviewed and evaluated the options available for deployment of a Short Message Service (SMS) solution and has determined the most viable interim SMS text-to-9-1-1 solution and deployment option is to provide statewide service with an integrated solution. The interim text-to-9-1-1 solution will utilize the most commonly available texting technology, carrier native -SMS texting. Carrier native SMS is a feature provided by the carrier, and not a third party texting or messaging application (app) that may be installed on the mobile device. The interim SMS text-to-9-1-1 service provides support for wireless subscribers to send 9-1-1 SMS text messages to PSAPs and for subscribers to receive text replies from PSAPs. Wireless

1 Report on Emergency Calling for Persons with Disabilities Survey Review and Analysis 2011


2 | P a g e 040417

customers with SMS service are able to send emergency SMS messages to a PSAP by using the single code “911” as the destination address of the SMS message. SMS text-to-9-1-1 service is national in scope and is independent of any vendor applications implemented in individual PSAPs. BENEFITS OF SELECTED OPTION Providing statewide service in this manner will provide the following benefits to the citizens of Minnesota:

An integrated solution deployed statewide will provide equal access to 9-1-1 services for all subscribers;

A statewide integrated solution will eliminate public confusion and disparate levels of services within the state. All citizens and visitors will have capability to text 9-1-1 and have their call received at a PSAP with trained personnel equipped to handle their request for service;

A statewide approach will allow the state to facilitate a consistent public education message to help ensure the speech and hearing impaired community are aware of the service capability and educated on its use.

A statewide approach will facilitate a more consistent method for training PSAP staff to become proficient and stay proficient in managing text-to-9-1-1 requests for service.

IMPLEMENTATION APPROACH Minnesota will implement a statewide approach to text-to-9-1-1 service in a phased approach with a cohesively managed methodology. The phased implementation will deploy texting initially in at least one identified PSAP in each of the seven regions. The regional PSAP will accept text on behalf of all PSAPs within the region. This will provide statewide service with all four of the major wireless providers in the most expeditious manner possible. In this way, deployment, testing, and practical application can be monitored and evaluated, and the lessons learned applied to future implementations. Additional PSAPs will deploy the integrated solution as call handling equipment is upgraded by local 9-1-1 authorities. Technical requirements for PSAP Customer Premise Equipment (CPE) to interface with the NG9-1-1 network in deploying text-to-9-1-1 have been created to provide the technical interface requirements between the ESInet and the PSAP 9-1-1 Call Handling System necessary for an integrated text-to-9-1-1 solution. This Technical Requirements Standard document will assist PSAPs in communicating with their CPE vendors and helping to ensure a smooth transition with the least amount of cost and rapid deployment timelines.

The initial seven regional PSAPs will be required to enter into a Memorandum of Understanding (MOU) with the other PSAPs in their region to accept text messages on their behalf until the other PSAPs are ready to take their own texts or until December 2018. PSAPs have until this date to finance equipment upgrades to facilitate deployment of Text-to-9-1-1, come to an agreement with the regional or another PSAP to accept their texts on a long term basis, or discuss alternative solutions with DPS-ECN. Establishing a future date for subsequent implementations will allow sufficient time for the other PSAPs in the region to plan for and fund upgrades to their CPE, establish necessary policy, and train personnel while supporting rapid text-to-9-1-1 service for their residents.


3 | P a g e 040417

COST All Minnesota PSAPs are responsible for all costs associated with any necessary (or required) CPE replacements or upgrades to enable them to receive the interim SMS text-to 9-1-1 deployment with an integrated solution. ECN will pay the monthly recurring charges associated with Text Control Center (TCC) connectivity on behalf of all Minnesota PSAPs. SUMMARY All PSAPs within Minnesota are connected to the statewide Emergency Services IP Network (ESInet) designed to deliver 9-1-1 calls to the appropriate PSAP. ECN will leverage the investment in the ESInet and expand the service enhancements to keep pace with the communications technologies available for accessing emergency services. An integrated solution will utilize the ESInet connectivity to deliver text messages into the PSAP call handling equipment via a Session Initiation Protocol/Message Session Relay Protocol (SIP/MSRP). This solution allows the text to display on call handling equipment and should provide the smoothest transition to full Next Generation 9-1-1 (NG9-1-1) deployment.

LaaSer Software Solution

LaaSer Field Testing Monday, March 6, 2017 On Monday, March 6, Dustin and I conducted field testing with LaaSer and IBM representatives. LaaSer provided 5 cell phones: one with each major carrier, Verizon, AT&T, Sprint, and T-Mobile. The last cell phone was equipped with LaaSer technology. We tested all 5 phones in four different locations: 445 Minnesota Street (this building), Hamline University on Snelling Avenue in St. Paul, the University of Minnesota Library off Buford Avenue in St. Paul, and House of Coates off highway 52 in Dakota County. Our goal was to determine if 911 calls placed at each location were routed to the correct PSAP, and if LaaSer performed better at location accuracy than the regular cell phones. I traveled with the LaaSer/IBM team to each field location, and Dustin traveled to the Ramsey County PSAP, the U of M PSAP, and the Dakota County PSAP to collect data on our calls. At the first location, this building, the Verizon and AT&T phones routed our call to the State Patrol PSAP. Sprint and T-Mobile routed our calls correctly to the Ramsey County PSAP. The LaaSer-equipped phone connected to the correct Ramsey County PSAP, and provided our correct address – 445 Minnesota Street – which I’ve been told has been a troublesome address to plot. At the second location, Hamline University off Snelling, the Sprint phone misdirected our call to the U of M PSAP, while the other providers routed us correctly to the Ramsey County PSAP. The LaaSer equipped phone plotted our address as 774 Snelling Avenue North, our true location, as opposed to the “main” Hamline address of 1536 Hewitt Avenue. At the third location, the Magrath Library on the U of M campus, only one of the standard phones correctly routed us to the U of M PSAP, the Sprint phone. The other providers routed us to the Ramsey County PSAP. The LaaSer phone correctly plotted our address as 1984 Buford. At the Dakota County location, the House of Coates restaurant, all of the phones routed us correctly to the Dakota County PSAP. The LaaSer phone plotted our address correctly as 16300 Coates Blvd. In the PSAPs, the technology was well received. Generally the carrier phones came in on Phase 2 or at least got there after the first bid. However, the Laaser phone would come in right away with the correct address displaying on the screen. The phone showed up as a VOIP call and the information on the screen looked like a typical VOIP call. For all 4 Laaser calls, it came directly to the correct PSAP and didn’t have to be transferred. Every time the Laaser call had better location information than the carrier phones.

Call#1:PublicSafetyOffice

CallNotes:

• BothVerizonandAT&Tmisrouted toStatePatrol

• AT&Ttook4rebidsonceitgottocorrectPSAP

• T-Mobiletook4rebids, firstcamewith9546muncertainty

ReportedUncertainty|DistancefromActual

• AT&T– 443m|20mfromTrue• Sprint– 222m|21mfromTrue• Verizon– 46m|40mfromTrue• T-Mobile– 3035m|100mfromTrue• LaaSer– 10m|5mfromTrue

Call#2:HamlineCampus

CallNotes:

• SprintmisroutedtoUofMPSAP

• Verizon,T-MobileandAT&Ttook2bidstogetWPH2



Call#3:UniversityofMinnesotaLibrary

CallNotes:

• AT&T,VerizonandT-MobileMisrouted toRamseyPSAP



Call#4:HouseofCoates

CallNotes:

• Phase1forAT&Twas4milesoff

• Phase1forT-Mobilewas7milesoff



RapidSOS Software Report

RapidSOS NG911 Meeting, April 19, 2017 This month I have chosen to research RapidSOS, a smart phone software that aims to solve the problem of inaccurate location information reported to the PSAP from a cell phone. I spoke to Reinhard Ekl, a representative with RapidSOS, on Monday, March 27. Reinhard echoed the question many of us have – smart phones already have accurate location services, but how do we make that location information available to PSAPs during a 911 call? RapidSOS is a software embedded directly into a smart phone, which accesses advanced mobile location sensors such as Wi-Fi access points, GPS coordinates, and the like, as well as using cell tower triangulation to supplement and validate the location, and then sending that location to the PSAP. For RapidSOS to work, two components must be in place: First, the smart phone must be equipped with this software. Reinhard explained that Android devices already have the software, it just has to be “switched on” by Google, likely through a system update. Rapid SOS is still in talks with Apple, and there was no information given as to the status of the software on Apple devices. Second, the PSAP’s CAD or call taking system needs to be upgraded or configured to support Rapid SOS integration. This upgrade or configuration would be coordinated through the CAD or call system vendor. Reinhard confirmed that they have worked with many CAD vendors, including Intergraph and TriTech. Rapid OS encourages and advocates for this upgrade or configuration to be free to PSAPs, but cannot control if the vendors charge for this service. Once the CAD or call system is configured to integrate with RapidSOS, the process would work like this: an equipped smart phone makes a 911 call, the Rapid SOS software fires a query to the RapidSOS clearinghouse, pinpoints the location information, and then sends that information to the Rapid SOS enabled PSAP faster than phase 2 information. There is no time delay with this query to the clearinghouse. Reinhard also confirmed that RapidSOS location software works with texting. This has been successfully tested in Maryland and Tennessee. RapidSOS will be conducting some pilot testing in Washington County later this year. They are also looking for additional PSAPs in Minnesota that would be willing to perform testing. If you are interested, please let me know and I will relay that information to Reinhard.

GIS Report

Aitkin

Anoka

Becker

Beltrami

BentonBig

Stone

BlueEarth

Brown

Carlton

Carver

Cass

Chippewa

Chisago

Clay

Clearw

ater

Cook

Cottonwood

CrowWing

Dakota

Dodge

Douglas

Faribault FillmoreFreeborn

Goodhue

Grant

Hennepin

Houston

Hubbard

Isanti

Itasca

Jackson

Kanabec

Kandiyohi

Kittson

Koochiching

Lac QuiParle

Lake

Lake ofthe Woods

Le SueurLincoln Lyon

Mahnomen

Marshall

Martin

McLeod

Meeker

MilleLacsMorrison

Mower

Murray

Nicollet

Nobles

Norman

Olmsted

OtterTail

Pennington

Pine

Pipestone

Polk

Pope

Ramsey

Red Lake

Redwood

Renville

Rice

Rock

Roseau

Scott

Sherburne

Sibley

SaintLouis

Stearns

Steele

Stevens

Swift

Todd

Traverse

Wabasha

Wadena

Waseca

Washi

ngton

Watonwan

Wilkin

Winona

Wright

Yellow Medicine

Red Lake Nation

CENTRAL

METRO

NORTHEAST

NORTHWEST

SOUTHCENTRAL SOUTHEAST

SOUTHWEST

NG911 Data Preparation Kickoff Meetings

Thursday, April 06, 2017

StatusMeeting CompleteMeeting Not CompletedData Preparation handled by the MESB

NG9-1-1 GIS Project Update NG9-1-1 Committee Meeting 4/7/2017 Data Collection, Assessment, and Preparation Projects MnGeo is collecting the core NG9-1-1 GIS datasets from all regions in the state. The GIS data are being compared to corresponding 911 data (MSAG, ALI, ELT) to gain a better understanding of data readiness for each County and PSAP. The results are compiled into data readiness profiles and reports, which are shared with each county and PSAP during their data preparation kickoff meetings.

MnGeo is also meeting individually with each PSAP and their GIS agencies/vendors to discuss their data readiness findings and to kickoff each county’s data preparation effort. Thus far, MnGeo has met with all counties in the NE and SE regions. Kickoff meetings are currently being conducted in the Central region. The NW, South Central, and SW region meetings are being planned and scheduled. The MESB is working with the Metro region on their data preparation. Please see the attached Kickoff Status map.

The goal is to meet with all counties by fall of 2017. Another major goal is to complete all necessary data preparation work in the Metro and NE regions by the end of 2017.

Emergency Service Boundary Map Viewer MnGeo is developing a map viewer and associated user documentation to manage the emergency service boundaries (PSAP, Fire, Law, and EMS) statewide. The initial goal is to resolve gaps and overlaps among PSAP boundaries in order to produce a seamless, relatively accurate statewide PSAP boundary layer for use in text-to-911 and eventually the Emergency Call Routing Function (ECRF). The map viewer is currently being piloted in the NE region and will be expanded to other regions in the coming months. The 9-1-1 GIS Authorities will be asked to work with their PSAP Managers to resolve the gaps and overlaps. The goal is to resolve all gaps and overlaps by this July, so the seamless PSAP boundaries are available for the text-to-911 deployments.

Data Maintenance MnGeo is currently documenting requirements and workflows for the recurring data upload, normalization, and validation maintenance processes. MnGeo will begin focusing on the aggregation and provisioning process requirements this summer. ECN and MnGeo would also like to conduct 2-3 proof of concept projects related to GIS-based MSAG creation, Emergency Call Routing Function (ECRF), and Location Validation Function (LVF) in the coming year, which will include 1-2 counties in the Metro and Northeast regions.

MN NG9-1-1 GIS Data Standards MnGeo, ECN, MESB, and the NG9-1-1 GIS Standards Workgroup are preparing the draft MN NG9-1-1 GIS Data Standards and associated materials for the third stakeholder review. The core NG9-1-1 boundary sections (PSAP, Fire, Law, EMS, Data Maintenance Authority) have been added to the standards document, along with several revisions to existing sections based on thoughtful feedback from the second stakeholder review.

The third review period is anticipated to take place in May, which will include solicitation of feedback from all MN PSAP and GIS Managers. From there, the Standards Workgroup will attempt to finalize Version 1.0 of the standards. The goal is to gain formal approval of Version 1.0 by this summer.

Newsletter Issue #5 is available on the “GIS Information” page of the ECN website:

https://dps.mn.gov/divisions/ecn/programs/911/Pages/gis-information.aspx

Alternate and Abandonment

Routing Information

ALTERNATE AND ABANDONMENT ROUTING GUIDE|SIP CONVERTED

Alternate Routing is Automatic Re-Routing (Requires no PSAP intervention) When 9-1-1 sessions (SIP equivalent of legacy trunks) are fully in use: • When PSAP 9-1-1 session capacity set in the PSAP CPE configuration is

reached, Alternate Routing will invoke. • In a SIP environment, overflow from one call type (VoIP, Wireline, Wireless)

to another is controlled by the CPE configuration. When no answer/response from PSAP: • Alternate Routing occurs when the PSAP doesn’t answer the call after a

defined time limit. o The ESInet default time limit is configured at 120 seconds. o The CPE may be configured to invoke the alternate routing before this

120 second ESInet default time limit. Abandonment Routing is Manual Re-Routing (Requires action by a PSAP) There are three elements within abandonment routing: Primary Abandonment(s), Additional Abandonment(s), and a fast busy. Each PSAP may have up to 10 options, including the fast busy that are pre-programmed and can be ordered in a variety of ways. Primary Abandonment Route Pre-programmed route(s) which can be used to route 9-1-1 calls after CenturyLink 9-1-1 Operations (1-800-357-0911) is engaged.

• The 1st Primary Abandonment Route will be invoked when the PSAP contacts the CenturyLink (CTL) 9-1-1 Operations Center (1-800-357-0911) or if a PSAP Abandonment Device (PAD) is activated.

• If the PSAP wishes to have a 2nd (or 3rd, 4th, 5th, etc) Primary Abandonment Route, calls will overflow to each additional Primary Abandonment Route if the preceding Primary Abandonment Route is unavailable or unable to answer a call. See the examples at the end of this document.

• The number of Primary Abandonments will be distinguished by the placement of the fast busy in your Abandonment List. For example, if you want two Primary Abandonment Routes, you would list those in position 1 and position 2, a fast busy will then be placed in position 3. In the unlikely event your 1st and 2nd Primary Abandonments are unable to take a call, the caller would then receive a fast busy.

Why have more than one Abandonment? In 2014, a North-Central MN county was experiencing severe weather and lost power to their PSAP. As they only had approximately 20 minutes of power left, they called CenturyLink Ops to invoke their lone Abandonment option. When CTL called the PSAP who would be taking on the calls, to inform them of the impending abandonment, the PSAP was unable to do so as they were experiencing the same severe weather and would not be able to dispatch anyone due to the weather. CTL then attempted to contact the original county – but alas, their power was already out and were not reachable.

The question then was, who do we send their traffic to as there were no other Abandonment options? In an act of technological heroism, CTL was able to identify a willing and able PSAP and build the necessary routing to abandon the effected PSAP’s traffic. Taking a process that typically takes 5 days – they completed these tasks in about 2 hours.

Continued on next page.

Additional Abandonment Routes A PSAP should have contingencies pre-programmed in case the Primary Abandonment Routes aren’t viable (e.g. abandoning to a PSAP that isn’t functional), example setups are listed below.

• If the PSAP wants their 9-1-1 calls to abandon to somewhere other than the 1st Primary Abandonment Route, the PSAP can request the 9-1-1 Operations Center to invoke one of the additional pre-programmed Abandonment routes.

• Each PSAP is allotted up to 10 pre-programmed options (positions) for Abandonment Routes, including the fast busy.

Examples of setups Primary Abandonment Route with contingencies, i.e. subsequent abandonment routes if Primary not working:

• Primary Abandonment Route (position 1) – Used if no specific direction is given to the 9-1-1 Ops Center. It is also the Abandonment Route for the PAD if one is installed.

• Fast Busy (position 2) – fast busy tone sent to the 9-1-1 caller instead of connecting to dispatcher. Used if Primary Abandonment Route doesn’t work or if the PSAP listed as the Primary Abandonment Route is unable to answer the call.

• Additional Abandonment Route (positions 3-10) – Eight (8) additional preprogrammed Abandonment Routes readily available for abandonment.

Two Primary Abandonment Routes:

• 1st Primary Abandonment Route (position 1) – also the Abandonment Route the PAD is programmed to.

• 2nd Primary Abandonment Route (position 2), e.g if the 1st Primary Abandonment location isn’t available or unable to answer a call, it will automatically overflow to the 2nd Primary Abandonment.

• Fast Busy (position 3). • Additional Abandonment Routes (positions 4-10) – Seven (7)

additional pre-programmed Abandonment Routes.

Eventually, power was restored to the original PSAP and routing was normalized. Thankfully, no serious issues arose during the 2+ hours citizens were not able to reach 9-1-1.

We can, however, conceive of a scenario where we aren’t so lucky and something serious does happen.

By choosing a number of abandonment options, you increase the preparedness of your PSAP and ensure that, no matter the circumstance, citizens who rely on the ability to call 9-1-1 are always met with the comfort of a Dispatcher’s voice on the other end.

ALTERNATE AND ABANDONMENT ROUTING GUIDE|NON-DIRECT SIP

Alternate Routing is Automatic Re-Routing (Requires no PSAP intervention) When 9-1-1 sessions (SIP equivalent of legacy trunks) are fully in use: • If 9-1-1 sessions are unavailable for the particular Call Type/Class of Service

(COS), the Alternate Route will invoke. • The Alternate Route for a 9-1-1 call can be differentiated by Wireless or

Wireline COS (VoIP is folded into Wireline). You can also choose to invoke an overflow from Wireless, Wireline/VoIP COS to another.

When no answer/response from PSAP: • Alternate Routing occurs when the PSAP doesn’t answer the call after a

defined time limit. o The ESInet default time limit is configured at 120 seconds.

Abandonment Routing is Manual Re-Routing (Requires action by a PSAP) There are three elements within abandonment routing: Primary Abandonment(s), Additional Abandonment(s), and a fast busy. Each PSAP may have up to 10 options, including the fast busy that are pre-programmed and can be ordered in a variety of ways. Primary Abandonment Route Pre-programmed route(s) which can be used to route 9-1-1 calls after CenturyLink 9-1-1 Operations (1-800-357-0911) is engaged.

• The 1st Primary Abandonment Route will be invoked when the PSAP contacts the CenturyLink (CTL) 9-1-1 Operations Center (1-800-357-0911) or if a PSAP Abandonment Device (PAD) is activated.

• If the PSAP wishes to have a 2nd (or 3rd, 4th, 5th, etc) Primary Abandonment Route, calls will overflow to each additional Primary Abandonment Route if the preceding Primary Abandonment Route is unavailable or unable to answer a call. See the examples at the end of this document.

• The number of Primary Abandonments will be distinguished by the placement of the fast busy in your Abandonment List. For example, if you want two Primary Abandonment Routes, you would list those in position 1 and position 2, a fast busy will then be placed in position 3. In the unlikely event your 1st and 2nd Primary Abandonments are unable to take a call, the caller would then receive a fast busy.

Why have more than one Abandonment? In 2014, a North-Central MN county was experiencing severe weather and lost power to their PSAP. As they only had approximately 20 minutes of power left, they called CenturyLink Ops to invoke their lone Abandonment option. When CTL called the PSAP who would be taking on the calls, to inform them of the impending abandonment, the PSAP was unable to do so as they were experiencing the same severe weather and would not be able to dispatch anyone due to the weather. CTL then attempted to contact the original county – but alas, their power was already out and were not reachable.

The question then was, who do we send their traffic to as there were no other Abandonment options? In an act of technological heroism, CTL was able to identify a willing and able PSAP and build the necessary routing to abandon the effected PSAP’s traffic. Taking a process that typically takes 5 days – they completed these tasks in about 2 hours.

Continued on next page.

Additional Abandonment Routes A PSAP should have contingencies pre-programmed in case the Primary Abandonment Routes aren’t viable (e.g. abandoning to a PSAP that isn’t functional), example setups are listed below.

• If the PSAP wants their 9-1-1 calls to abandon to somewhere other than the 1st Primary Abandonment Route, the PSAP can request the 9-1-1 Operations Center to invoke one of the additional pre-programmed Abandonment routes.

• Each PSAP is allotted up to 10 pre-programmed options (positions) for Abandonment Routes, including the fast busy.

Examples of setups Primary Abandonment Route with contingencies, i.e. subsequent abandonment routes if Primary not working:

• Primary Abandonment Route (position 1) – Used if no specific direction is given to the 9-1-1 Ops Center. It is also the Abandonment Route for the PAD if one is installed.

• Fast Busy (position 2) – fast busy tone sent to the 9-1-1 caller instead of connecting to dispatcher. Used if Primary Abandonment Route doesn’t work or if the PSAP listed as the Primary Abandonment Route is unable to answer the call.

• Additional Abandonment Route (positions 3-10) – Eight (8) additional preprogrammed Abandonment Routes readily available for abandonment.

Two Primary Abandonment Routes:

• 1st Primary Abandonment Route (position 1) – also the Abandonment Route the PAD is programmed to.

• 2nd Primary Abandonment Route (position 2), e.g if the 1st Primary Abandonment location isn’t available or unable to answer a call, it will automatically overflow to the 2nd Primary Abandonment.

• Fast Busy (position 3). • Additional Abandonment Routes (positions 4-10) – Seven (7)

additional pre-programmed Abandonment Routes.

Eventually, power was restored to the original PSAP and routing was normalized. Thankfully, no serious issues arose during the 2+ hours citizens were not able to reach 9-1-1.

We can, however, conceive of a scenario where we aren’t so lucky and something serious does happen.

By choosing a number of abandonment options, you increase the preparedness of your PSAP and ensure that, no matter the circumstance, citizens who rely on the ability to call 9-1-1 are always met with the comfort of a Dispatcher’s voice on the other end.

Text-to-911 Information


Public Safety Answering Point Text-to-911 March 2017 Update

Minnesota’s Department of Public Safety Emergency Communication Networks division (ECN) along with the Metropolitan Emergency Services Board (MESB) worked with vendors to determine the technical requirements for accepting integrated texts and used that information to prepare a Text-to-911 Deployment Readiness Checklist. The checklist was distributed in January 2017 and responses were received from 92 of the 104 PSAPs. (88%) After reviewing the responses with the MESB, ECN has identified the initial eight PSAPs that will take texts for the seven regions.

Region PSAP Name Central Mille Lacs Southwest Nobles and Lyon will split the region Southeast Olmstead Southcentral Waseca Northwest Beltrami Northeast St. Louis Metro Hennepin

In addition, the ECN has created an amendment to the Statewide NG9-1-1 Strategic Plan defining the Statewide Text-to-911 Plan which will be presented to the NG9-1-1 Advisory Committee in March 2017. The plan provides information on the background and decision making process in selecting a statewide integrated implementation approach. Once approved by the committee, ECN will begin work on a more detailed deployment plan and timeline that will be added as an appendix to the initial plan.

ECN is in the process of finalizing the Technical Requirements for Public Safety Answering Point (PSAP) Customer Premise Equipment (CPE) to interface with NG9-1-1 Network in deploying Text-to-9-1-1. This technical requirement document has been created to provide the technical interface requirements between the ESInet and the PSAP 9-1-1 Call Handling System necessary for an integrated Text-to-9-1-1 solution. This requirements document will assist PSAPs in communicating with their CPE vendors and helping to ensure a smooth transition with the least amount of cost and rapid deployment timelines.

Finally, ECN will begin work with the NG911 Advisory Committee to create a single statewide Text-to-911 operational procedures document. ECN would like to have at least one representative from every region on that text standard working group. There is a lot of work to be done to make statewide access to text-to-911 a reality and ECN is excited to be an early adopter of this technology. ECN has prepared this communication along with a second list of some of the questions received to date, to keep MN PSAPs informed on the progress. Look for additional communications in the near future.

12/5/2016


Text-to-911 Frequently Asked Questions – Part I

1. If PSAPs are ready to deploy at the same time as the Regional PSAPs will they be allowed to take their own texts? RESPONSE: Yes. The language in the scope of work in the new 911 service provider contract was clarified to state “at least one PSAP in every region” from initially being one PSAP in every region. However, once the PSAP Text-to-911 Deployment Readiness Checklist responses are compiled, a deployment plan is created, and a timeline set, the deployment date will not be extended to continue to accommodate additional PSAPs in the regions. We will continue to deploy, adding PSAPs to the ongoing deployment timeline as they become ready, over the course of the next one to two years.

2. How will the regional PSAP advise the correct PSAP about a text – will they use MetCom or call on the phone? RESPONSE: It is the desire of ECN to have a single statewide standard that is developed through the NG911 Advisory Best Practices/Standards subcommittee. We would like to have at least one representative from every region on that text standard working group. It will be the responsibility of each regional representative to collaborate in between subcommittee conference calls with their own regional PSAP representatives so all voices are heard.

3. In relation to mapping and geography, the regional PSAP may not know that the address given in a text is an apartment building, for example. How will this be handled? RESPONSE: This is a valid concern. ECN is in regular communication with Adam Iten, our 911 GIS Project Manager. His MNGeo GIS team are making every effort to have a statewide PSAP boundary map available by mid-year 2017 which will hopefully align with our deployment. This will be a resource/tool of information that the receiving PSAP can share with the jurisdictional PSAP. The text caller must provide their location information. The location information initially received in ALI will identify the cell sector centroid. This is not the same as Phase I Wireless location. An improved location may be available in some instances with a rebid.

4. What if there is no response to a text to get additional information? Will the regional PSAP call the number the text came from or have the PSAP whose jurisdiction it is follow up? RESPONSE: See response to Question #2 above. This is something that should be discussed and a procedure developed and included in the text standard just as we have policies in place today for hang up calls.

5. If a PSAP is not ready to deploy when the regional PSAP starts taking texts what is the time frame for the other PSAPs to be able to take their own texts? RESPONSE: ECN is creating a Text-to-911 Deployment Plan that will contain a plan and timeline for all remaining MN PSAPs to transition to receiving their own texts as their CPE is capable and test calls are successfully completed. The Text Control Center (TCC) vendor has indicated that changing the routing for a PSAP is a relatively easy process and they are willing to do it as needed. Thus, the schedule to deploy may occur as frequently as weekly, as additional PSAPs become ready.

12/5/2016

6. Is there a cost associated with the regional PSAP taking texts? If not, how long will they continue to take the text messages? RESPONSE: As mentioned in Question #5 above, the Text-to-911 Deployment being created will include a transition plan for all remaining MN PSAPs. The regional PSAP will take text messages long enough to allow sufficient time for all of the PSAPs that want to take their own messages to deploy. After the first year, West will bill ECN as though all 104 PSAPs are taking their own texts, therefore ECN prefers as many PSAPs as possible are taking their own text by that time. There is a relatively small number of PSAPs who have indicated no desire to deploy service. These PSAPs will need to negotiate an agreement with another PSAP to accept their messages long-term. ECN will not expect a regional PSAP to have an open-ended relationship with any PSAP(s) in the region for indefinite support without compensation. This will be addressed if the need arises.

7. Will the regional PSAP print out the text message and send it to the PSAP of jurisdiction so they have it if needed for court? RESPONSE: See Question #2 above. This is a procedural item that should be discussed and included in the text standard.

8. How will the text message be routed to the correct PSAP? RESPONSE: Unlike a wireless 911 call that is routed by cell tower sector; a text is routed by the tower centroid location. A centroid is the geographic center of the cell sector’s RF footprint. It will be important during training to explain that a calltaker will not see the same tower address with a text as they do with a wireless call.

9. Will we receive texts from a non-service initialized (NSI) phone like we do with wireless calls? Many times, these are the phones that place prank calls. RESPONSE: Any phone that doesn’t have an active subscription that includes text capability (like an NSI phone) will not be able to send a text-to-911. For example, if using WIFI on an iPad/phone with no data package; if the user attempts to send a text-to-911 they will receive the bounce back message.

10. How many texts are expected to come in and will we need to increase staff to handle the texts? RESPONSE: The studies and feedback from early adopters show that the call volume is very low and regular refresher training is needed to keep skill sets fresh.

03/20/2015


Text-to-911 Frequently Asked Questions – Part II

1. Can you rebid a text call? I was under the impression that you cannot make it Phase 2. RESPONSE: You can attempt a rebid, but it may or may not work. Texts will come in with the address of the cell sector centroid, which is not the same as Phase 1 location; but very similar. RRRDC has been pleasantly surprised, reporting the accuracy to actually be more defined than Phase 1.

2. Can we place a voice call while dealing with a text call? Can we call the texter while the session is open if they’re able to talk? RESPONSE: This question has both a technical and operational response. From a technical perspective, PSAPs should have a discussion with their CPE provider to discuss this option as it is one of the configurable features of integrated texting. From an operational perspective, one of the first questions a 911 call taker should text to the texter is whether they are able to place a voice call to 911. If they answer yes, have them call, and terminate the session. If they answer no, chances are, they won’t answer your voice call if you call them. Depending on what they are reporting, a call back may jeopardize their safety. This will be one of the topics addressed by the Operational Standard Workgroup for inclusion in the operational standard.

3. Will multiple texts tie up multiple 911 trunks? RESPONSE: Integrated text (via the CPE), which is the solution we have selected for MN, will not tie up 911 trunks at all as the texts-to-911 come in on separate sessions. Only texts delivered via TTY tie up a 911 trunk. This functionality is configurable by the CPE provider. Some areas allow their call takers to handle a text and phone call at the same time. Other areas will allow call takers to handle multiple text sessions at a time. If multiple texts come in at the same time, after the number of texts are answered that equal the number configured, texters will get a bounce back asking them to place a voice call to 911.

4. Can you transfer a text from one console to another in the PSAP? Can you put it on hold and have someone else pick it up? RESPONSE: The PSAP should discuss this functionality with the CPE provider. It is our understanding that this is possible with both West and Airbus CPE.

5. What will the user interface for integrated text-to-911 look like? Are there screenshots available? RESPONSE: Stay tuned for Text-to-911 Frequently Asked Questions – Part III. We will provide sample screen shots for both Airbus and West CPE.

03/20/2015

6. Will we be able to transfer from PSAP to PSAP right away in the metro or between the other regions that are deploying? RESPONSE: The CPE providers are working with the Text Control Center (TCC) to test this functionality. Further information will be provided on this ability as we move closer to TCC testing.

7. What are the seven PSAPs that will be deploying in the first round? RESPONSE: Eight PSAPs volunteered to cover the seven regions for the initial deployment round. They are: Central Region – Mille Lacs Southwest Region – Nobles and Lyon will split the region Southeast Region – Olmstead Southcentral Region – Waseca Northwest Region – Beltrami Northeast Region – St Louis Metro Region - Hennepin

8. When will the Text-to-911 deployments begin? RESPONSE: ECN has delivered the Plan Change letters to Centurylink and West for the initial round of deployments. Establishing connectivity between the TCC provider West and each of the eight initial PSAPs will take between six and twelve weeks. Once TCC provider connectivity has been tested, testing with each of the big four wireless providers can begin. ECN anticipates the TCC testing will begin in mid-May 2017 and could last throughout the summer.

Statewide Text-to-9-1-1 Operational Standard Workgroup April 2017

Dustin Leslie, chair

Statewide Text-to-911 Workgroup

Representing

Cathy Anderson [email protected] State Dustin Leslie [email protected] State Dana Wahlberg [email protected] State Jeff Lessard [email protected] U of M Gary Mulleneaux [email protected] Olmsted - SE Mark Mather [email protected] Lyon - SW Teri Wold [email protected] Hennepin Heidi Hieserich [email protected] Airport Brandee Ockwig [email protected] Waseca - SC Kari Kopischke [email protected] Waseca - SC Nancy Shafer [email protected] Polk - NW Judy Diehl [email protected] Stevens - CE Pat Wallace [email protected] Blue Earth - SC Jody Norstegard [email protected] Kandiyohi - CE Emily Warnygora [email protected] St. Louis - NE Rick Juth [email protected] State Al Fjerstad [email protected] Mille Lacs - CE Faith Evers [email protected] Olmsted - SE Holly Martinson [email protected] Mille Lacs - CE Pete Eggimann [email protected] MESB

New Emergency Text Message Program Little Used

WDAY 6 News Fargo – Interview with Mary Phillippi - RRRDC

http://www.inforum.com/news/4247092-new-emergency-text-message-program-little-used

Six months into the program's launch, only a handful of people in North Dakota are texting for help. However it seems that dispatch centers would still prefer people to call 911 for help.

North Dakota launched its very own text-savvy emergency tool, but pretty quietly.

Many people in the metro don't even know there's a new way to "dial" in.

In the program's first six months, the dispatch center only receives 20 texts per month.

Dispatch centers found that people are still more comfortable, in emergency situations, to speak with a person rather than text.

The feature was originally designed with the deaf and hard of hearing in mind, but the dispatch centers say most people who text aren't from that community.

It might become the new thing. Texting 911 could be more popular than calling 911.

Dispatch centers are saying that picking up the phone and dialing 911 should still be option one.

Red River Dispatch takes the majority of text messages in North Dakota.

Their area covers around 600,000 people across the state.

February 2017 Minutes - Minnesota Department of Public Safety

Documents

Transcript of February 2017 Minutes - Minnesota Department of Public Safety