Central MN Owners & Operators and User Committee Meeting Douglas County Public Works, Alexandria, MN Thursday, November 15, :00 AM Agenda

Transcription

1 Central MN Owners & Operators and User Committee Meeting Douglas County Public Works, Alexandria, MN Thursday, November 15, :00 AM Agenda 1. Call to Order 2. Roll Call 3. Revisions and Approval of Agenda 4. Approval of Minutes from October 18, 2018 (P1-12) 5. Communications and Incidents a. January meeting - Election of Officers 6. Owners & Operators Business a. Kandiyohi County CRAE utilizing 8TAC94 (P13) action item b. BNSF Interop Participation Plan Expansion (P14-18) action item c. Article Stolen Police Radio Data (P19-20) 7. Joint Business a. CM Standards Review i. CM Requesting Full Participation (P21-27) b. Encryption discussion c Meeting Schedule (P28) action item 8. Users Business a. Communications Discussion City of St. Cloud b Training: i. Upcoming: ARMER Radio Trainer - December 6, Stevens County 9. Reports CMESB: a. ESB next meeting December 19 b. RAC next meeting November 9 (Stearns County) c. Next Gen 911 d. EMAC e. Regional Logger f. Grant Updates SECB/ARMER: g. Operations and Technical Committee h. Interoperability Committee a. STR Subcommittee b. COMU Subcommittee c. EMS/Hospital Subcommittee i. Interop Data Committee j. Steering Committee k. SMG no meeting 10. Upcoming Meetings a. Next meeting December 20, Adjournment

2 Central MN Owners & Operators and User Committee Meeting Douglas County Public Works, Alexandria, MN October 18, :00 AM OWNERS & OPERATORS MEMBERS/ALTERNATES PRESENT: 1. Julie Fraley Benton County 2. Ace Bonnema Big Stone County 3. Mike Henrion Douglas County 4. Tina Lindquist Grant County 5. Ace Bonnema Kandiyohi County 6. Randy Celander Meeker County 7. Victoria Ingram Morrison County 8. Sheriff Tim Riley Pope County 9. Kristen Lahr, Chair Stearns County 10. Judy Diehl Stevens County 11. Sarah Booker Todd County 12. Tyler Wheeler Wadena County 13. Sheriff Rick Fiedler Wilkin County USERS MEMBERS/ALTERNATES PRESENT: 1. Dean Wrobbel City of St. Cloud 2. Julie Fraley Benton County 3. Ace Bonnema Big Stone County 4. Mike Henrion Douglas County 5. Tina Lindquist, Vice Chair Grant County 6. Ace Bonnema Kandiyohi County 7. Randy Celander Meeker County 8. Victoria Ingram Morrison County 9. Michael Lange Otter Tail County 10. Sheriff Tim Riley Pope County 11. Paul McIntyre, Chair; Kristen Lahr, Chief Hughes, & Erin Hausauer Stearns County 12. Judy Diehl Stevens County 13. Sarah Booker Todd County 14. Tyler Wheeler Wadena County 15. Sheriff Rick Fiedler Wilkin County GUESTS: 1. Micah Myers City of St. Cloud 2. Jim Stromberg ARMER Program Manager/SWIC, ECN 3. Steve Tait RIC, ECN 4. Dan McCoy Granite Electronics 5. Sara Moulzolf Granite Electronics 1

3 OWNERS & OPERATORS MEMBERS/ALTERNATES ABSENT: 1. City of St. Cloud 2. Mille Lacs County 3. Otter Tail County 4. Sherburne County 5. Swift County 6. Traverse County 7. Wright County USER MEMBERS/ALTERNATES ABSENT: 1. Mille Lacs County 2. Sherburne County 3. Swift County 4. Traverse County 5. Wright County CALL TO ORDER: Meeting called to order by O&O Chair Kristen Lahr at 10:00 a.m. INTRODUCTIONS: Introductions were conducted. There was a quorum for both Committees. APPROVAL OF AGENDA: User Chair McIntyre added introduction of our new RIC under Communications. Stearns County made a motion to approve the O&O/Users Agenda. Benton County seconded, motion carried. APPROVAL OF MINUTES: Stevens County made a motion to approve the September 20, 2018 O&O/Users minutes. Morrison County seconded, motion carried. COMMUNICATIONS AND INCIDENTS: Steve Tait introduced himself as the newly appointed Regional Interoperability Coordinator (RIC) for the Central Region and the three southern regions. Tait started on October 1 st. Tait just retired in July from the Hennepin County Sheriff s Office after 26 years. Tait retired as a lieutenant of the technology unit, so he has a good baseline on the end user s needs as far as Public Safety communications. Tait also works part-time for Hennepin County Emergency Management doing some critical infrastructure work, resource management and information sharing projects. Tait is looking forward to supporting all 4 of the program areas that ECN offers. SWIC Stromberg explained he is excited that our RIC program has been reinvented in that we went from 3 RICs to 2. We cannot have the RIC going to every single meeting like we have done in the past. Marcus Bruning will continue to serve the Northwest and Northeast Regions and he will be picking up the Metro Region. Please utilize your RIC, Tait is very knowledgeable. O&O Chair Lahr stated the Regional Leadership Group meeting is on Monday. It is the leadership, or our counterparts, from the other regions around the state. There is good discussion and it is led by ECN. It is a good opportunity to see what is happening in other regions. Chief Hughes stated Wright County had a squad stolen last week. As they came into Stearns their dispatch (Wright County) lost mile markers on their mapping. They had an LTAC patched, Wright County was asking a few times for State Patrol to pick it up. Hughes did not hear Stearns, but they were the ones that actually pitted. Lahr will have Burke find some information to report. 2

4 O&O BUSINESS: a. Other O&O does not have any business this month. JOINT BUSINESS: a Regional Training O&O Chair Lahr stated we are looking at finalizing some dates and final locations for training for next year. In the packet are the list of courses. ARMER Dispatcher is March 11 th at Alex Tech. REFRESHER: ARMER Radio Trainer is October 15 th in Otter Tail County. ARMER Radio Training (2-day) is going to be in Morrison County on December 2-3. APX Radio Programming Workshop (3-days) and the 1-day Advanced Programming class we are hoping to hold in Stearns County. The dates the vendor supplied were May 6-9 th. The 6-8 th would be the 3-day programming workshop and that fourth day would be the advanced programming 1-day. Hausauer said the EOC is available. All Hazard Incident Dispatcher. User Vice Chair Lindquist explained Steve Olson with On Target is going to be instructing this course. (1) There is the 4-day OEC course with certificate; or (2) Two (2) day course as described in On-Target s proposal. Lahr inquired if OEC certificate was available with two (2) day course it is not. Discussion on holding two (2) day course, and Myers suggested surveying participants to see if interest in OEC four (4) day certificate course. On Target prefers Alex Tech or St Cloud PD for hosting facility. Stromberg added to be staterecognized in the communications unit position of Incident Tactical Dispatcher you do need the full OEC-approved course. Discussion on intent of course 1) become state resource as an Incident Dispatcher or 2) provide training opportunity for our regional dispatchers for All Hazard Incidents. Lahr informed the committees that the training from First Contact was a regional training opportunity. Diehl added a two (2) day course is more realistic for small PSAPs, then a four (4) course. Lindquist noted if we want the 4-day training, the proposal was for 2 days so we would have to look at a revision to the proposal and costs. Stevens County made a motion that the All Hazards Incident Dispatcher be a 2-day course held at Alex Tech or St. Cloud PD. Stearns County seconded, motion carried. Lindquist asked if the group has a preference over location? Diehl replied Alex Tech would be more centrally located. Lindquist will check with Alex Tech for room availability. We are looking at September th. i. ICS/Communications Planning Workshop (2 day) date/location suggestion Meeker County is willing to host on June th. Send out a Save the Date encouraging a group from your county to attend. Lindquist explained the first time around it was technical. This time it is pared down it focuses on setting-up Incident Command with dispatch being involved. ii. Advanced Search & Rescue Training (2 day) date/suggestion (Kandiyohi County) Lindquist reported we are bringing a Search and Rescue Incident Management course, a 1-day course for 8 hours, on October 24 th at Kandiyohi County EOC. Lindquist suggested we Save the Date to all our local responders. It is up to 60 people. Instructor is Rick Slatten from Woodstalk. 3

5 JOINT BUSINESS: (Continued) b. CM Standards Review i. CM Requesting Full Participation Lahr edited the regional standard and in doing so she had some questions on the intent for the standard: This is requesting full participation to the ARMER system within the region, but not necessarily requesting to be a member of the region? Myers replied that is correct. Lahr stated this is what an agency would need to do to request full participation similar to when the Mille Lacs Band was requesting full participation. Lahr listed the edits: Updates to names of committees. Purpose or Objective Updating reference to the 800 digital trunked radio system to ARMER. Technical Background We added these definitions: Public Safety Agency, Public Service Organization, EMS Provider, Full Participant, Limited participant, and Interoperability participant. Capabilities We crossed out some old language. Updated where the technical design documents go (approved by the O&O on behalf of the ESB). Constraints There was some reference to statute that seems to be crossed out of similar standards, so Lahr did so here too. Eligibility is limited to public safety agencies and is defined in Section 2. Operational Context describes how people communicate on ARMER system. Recommended Protocol/Standard It is including who would all potentially be reviewing that. Our original standard listed all of the items that needed to be included in the plan. That has been eliminated, Lahr compared that to state and the Metro Regional standard and they did not have an itemized list. Recommended Procedure Lahr updated the second paragraph stating the Regional Coordinator of the CMESB shall forward copies of the request to the Chair of the Owners and Operators Committee for inclusion in the meeting packet so it can be reviewed. Myers inquired about the Director of Electronic Communication in the last line asking are we going to tell an entity that they need to reach out to MnDOT, or do we forward that on to MnDOT, because that is where that is actually going. Myers explained what we have done in the past is it is a 3-way contract with the board, MnDOT and the participating agency. Lahr asked should we keep the last line that is struck out? Myers said to leave and the Director of MnDOT, or to the contracting agency. Myers noted in Section 2 Technical Background: Under Public Safety Agency change police to law enforcement because the Sheriff s Offices are not technically considered the police. Does emergency services make reference to Emergency Management? Under Public Service Organizations do we want to put Public Works in there? Lahr replied Public Works would be a public department. Capabilities in the last sentence after the ARMER system add within the Central Region, because we cannot govern outside of our region. 4

6 JOINT BUSINESS: (Continued) b. CM Standards Review (Continued) i. CM Requesting Full Participation (Continued) Stromberg inquired you include the limited participant and that is something that is in the state standard. Stromberg explained within the state there is only Red Lake County that remains a limited participant. We are moving forward language and conversation about changing the types of participation and getting rid of that limited plan, because that is just for the purposes of patching your legacy VHF system to ARMER. Stromberg asked as a region, do you look at Stevens County EMS as a participant, or just as Stevens County, because Stevens County is a full ARMER participant? Do you need a limited plan? Myers questioned entities like the hospitals and the St. Cloud VA and we also have a limited participation with St. Cloud State Public Safety. We still do have limited participation and they are included in the City of St. Cloud plan. They operate daily and maintain a subsystem. Lahr provided an example if there would be a new private ambulance service, and they intend to buy ARMER radios, or they have their own VHF radios, could they be sponsored by Stearns County, or would they need to bring their plan to O&O and follow the standard and that is where we would need to have their limited participation called out? Myers replied when an entity is coming on they still have to come up with a plan because they still need to get radio IDs unless you are giving them the radio IDs out of your pool, but they have to be associated with someone. Stromberg would argue with the example, a new ambulance service agency comes into existence and if they have a VHF radio system and they choose to have a hard patch into ARMER locally that is fine there may be a place for a limited, but if you are going to be providing them radio IDs, and those radio IDs are going to come out of Stearns County s pool of IDs then Stearns County s full participation plan with the state should be amended to say that we are adding the ambulance company. Myers stated that is all of their day traffic, however with the example that Myers gave with SCSU security staff they are not a full participant because they still tie back to their legacy campus system, because those other members of campus cannot come onto ARMER, so they are maintaining two systems. The way Myers reads this is their primary voice system is integrated into it, not from where we are giving them radios. It is separate from an interoperable, because interoperability is on an event. They are operating their security daily on ARMER and then they have to still communicate with the rest of campus communications. Myers stated we cannot lessen what they do at the state, but we can put additional requirements on it. Myers added one of the things that we do here in the region is we have regional assets and in order to get access you need to be sponsored. McIntyre said he would be a good example, when we first came on we operated in four counties under that limited plan and our IDs came from the EMS/Hospital pool from the state, we were just doing dispatch within the region and not our statewide response. CentraCare if they came forward between Wright, Stearns, Todd might be one again when they start looking do they go full statewide or do something regionally. So, there is potential to keep the language in there. Recommended Procedures Lahr mentions striking out existing paragraph that reads if the agency does not have a design plan that the region will work with them to help develop a plan. Added in the language of acquiring a qualified consulting engineer. Todd County noted a typo retrained should be retained. 5

7 JOINT BUSINESS: (Continued) b. CM Standards Review (Continued) i. CM Requesting Full Participation (Continued) Recommended Procedures (Continued) Lahr kept the language as it read that the ESB would act on the request. The ESB has granted O&O authority to approve/deny participation plan requests and changes. Would we want to keep the language as is, or change that to Owners and Operators on behalf of CMESB? Myers replied you are an extension of the Board, so you can leave it as is. We are not always the rubber stamp; an entity can still go to board if they object with the opinion of this group. Management Updated to state CM Owners & Operators Committee. We can cross out staff. Lahr will bring a marked-up and a clean copy in our packet for next month. c. Encryption discussion Lahr stated the frequency of using encrypted resources within the region is increasing and with that increased questions or issues have been cropping up. Encryption is a broad topic and we can go in all manner of directions: Policy per standard, who can or cannot use encrypted resources per standard, an operational avenue like who do we need to talk to, do these people have encrypted capability, when do you use an encrypted talkgroup, technical considerations, how does encryption work in a radio, how do you get it to successfully work in a radio, how is encryption set-up in the system, do encrypted resources work in the console, how does that all work together, why does it not work sometimes, why am I hearing beeping in the PSAP. Then there is this philosophical or future discussion of encryption. Is what we are using now secure enough, has it been hacked? Do we need to move from what we are using now and how do we pay for that? Lahr explained we can get into the weeds quickly when we start talking about encryption, so this is an open discussion. Lahr thought it would be a good idea to lay some good foundation work just to see how encryption resource use is going in the region and see that we cannot make sure it is used successfully on a consistent basis within our region before we start talking about the next steps. Questions: 1. Who here is using encryption? Do we all have encrypted resources in our agencies right now? Lahr stated generally, we all have access to encrypted resources. 2. What disciplines with your agencies are using encryption? Is it just law enforcement? Myers replied law enforcement, but we have had the request now with Fire. Wrobbel explained it gets back to our interoperable St. Cloud talkgroups where we are assisting police (i.e. drug bust, hazmat incidences, terrorist event) where we go statewide response and we might want to get in to encryption. We have also had the discussion with Police about going to encryption on all of our talkgroups and just have clear channel as our dispatch channel. We have one Fire talkgroup that is encrypted. Myers explained the white paper that SWIC Stromberg had sent out and Nate Timm s response. Myers explained we had this discussion at Strategic Planning and Myers discussed key mismatch on the Logger and the IV&D project. Myers explained that Timm s response was what is our objective, what are we trying to accomplish with encryption? Is it simply so we can avoid scanner, or are we looking at the disgruntled worker or the hacks as your system starts to plug into the IP? The current level of encryption has been hacked for over 10 years. 6

8 JOINT BUSINESS: (Continued) c. Encryption discussion (Continued) SWIC Stromberg stated the state is multifaceted. DPS-ECN is very concerned about how outdated DES-OFB encryption is. We support more cyber security initiatives and migrating to AES. MnDOT has a lot of security in mind and is protecting ARMER adequately. How to increase our cyber protection and improve upon our encryption are expensive, challenging, time-consuming tasks. We do not have a clear plan for remedying those concerns. Lahr stated it would be nice to have the successful operation of encryption on a consistent basis within the region. There have been hiccups in the last handful of incidences that we have gone to an encrypted talkgroup. Unless we have a solid understanding of what we are using right now and is that working good for everybody. Can you use it successfully when you need to? It is hard to have that next conversation. We want to discuss this encryption discussion at future meetings. So, if we can build on the subject and have something tangible to discuss and potentially educate everybody at future meetings. Myers explained you need to have someone with passion who is going to take the lead on that and push it. First step is identifying what do we have in our region. Lahr added and how are we using it and is it working for everybody? And if it is not working, why is it not working? Myers would go one step further what is our desired outcome for encryption? If we are simply trying to keep people from listening to us then we do not have to do anything. But, if our objective is to secure and ensure that our public safety communication network stays uncompromised then that would be our objective. McIntyre responded he cannot think of any small fire, rescue squads, ambulance provider in our region that have encrypted. We need to start looking at it, and it added a huge cost to his proposal to move forward with replacing radios. We are working in multiple areas and it becomes an almost unimaginable task of how to figure out who uses what encryption. At least maybe coming to a consensus in the region that we get to this. We recommend Best Practices, start developing some of those after we take inventory, saying if you are going to be upgrading your fleet we recommend you do this and show them the cost at the time of inquiring the radios. Stromberg stated it is a two phase approach: (1) Using the existing technology of DES-OFB with the proper administration and technical understanding you can have encryption that will work well; (2) The second step is moving forward and that involves key management, methodology for rekeying in something other than a manual way. And what do you buy in encryption? Federal grant funding is mandating if you are going to buy radios with grant money you need to have AES encryption. In MN, we have DES-OFB, so you will also need to have multikey. We will never migrate away from DES-OFB unless we start buying radios that are multikey and AES. Stromberg is waiting to get on the agenda to talk about this at the Grants Workgroup. Myers explained how the Grants Workgroup is going to have to change their current model and make encryption a requirement. Lahr recapped we do have potential considerations by some Fire agencies to use encryption, but its current use is generally law enforcement. Questions: 1. Who are you talking to? Do you have local encrypted talkgroups for your agency that you are using for a daily basis when you go to a routine call? Do you have local talkgroups that are encrypted? There were nods of yes. 2. Do you also communicate regionally? Do you have regional taskforces or do you work with neighboring counties? Lahr explained how Stearns County partners with agencies. We are moving to a statewide/regional talkgroup frequently. Pope County has West Central SWAT with six counties, but it was allowed region-wide with 3 talkgroups encrypted. 7

9 JOINT BUSINESS: (Continued) c. Encryption discussion (Continued) Questions: 3. Are you using statewide encrypted talkgroups on a regular basis? Pope County responded not on a regular basis. Myers responded on large events and asked how do we handle mutual aid events? Pope County added we do have access to all the encrypteds we just do not use them often. Lahr asked but your encrypted radios do have LTAC 5-12E in them? Pope County replied, yes. 4. How often do you see your agencies going to an encrypted talkgroup? Pope County replied a couple times a year. SWAT Team use it for training monthly. Myers would say daily for VOTF. Meeker County would probably be 20% of our communications are encrypted. All our jail traffic is on an encrypted talkgroup and that is running daily 24/7. Lahr summarized sometimes it is special assignment, incident dependent, or training, but sometimes it is a daily use. 5. We know everybody is using DES-OFB, is there anybody using an additional encryption type like ADP (Motorola proprietary) or a higher level of encryption of AES? Myers responded with our new radios we went with AES. Lahr asked are you using AES encryption on any of your talkgroups? Myers replied we do not have it on the talkgroup, but our radios are capable, because no one else around us is. Lahr explained how Stearns County has one talkgroup that is ADP encryption capable. 6. Have you experienced problems using encryption? Whether it is your agency using encryption or your dispatchers saying why is this console beeping. Pope County responded if we have 10 radios on the same encrypted talkgroup somebody is not going to communicate. Someone cannot hear, or they are getting a key fail. Lahr stated on a subscriber-level you have had issues. Meeker County responded for as much as we use encryption we really have not had any problems. The console beeping because somebody changed a key someplace. Myers added some issues during a recent event with multiple agencies, but typically we are not seeing anything. 7. Have you had any other issues or potential questions that come up? Lahr explained how Stearns County will get a request from a sergeant/officer to patch a couple of talkgroups together when they are working with encryption, because they have somebody coming into assist on an emerging event. Do you have questions on protocol for that within your agencies? Do you have issues on if can you patch things, or have you tried to patch things and you have not been able to talk to each other? There is a standard with rules involved with that decision, and then there are technical considerations to make that work. This request is becoming more frequent for Stearns County. Myers explained on the training aspect when we are doing dispatch training we have On Target place emphasis on if there is policy. Dispatchers do not know if they can do it, but they need to understand the protocols. Lahr gave an example from the last standards call regarding questions about law enforcement LTACS and the encrypted law enforcement talkgroups. Lahr noted it is against standard to patch a clear mode talkgroup to a statewide encrypted talkgroup and questioned if there is officer safety involved and you just need all those people to communicate regardless of protecting that conversation, should that be an option in dire straits? Stromberg replied there seems to be some appetite for creating an exception in an unfolding emerging event. Caution came up that if you have some narcotics people that are used to working in an encrypted environment and now that they are patched to a clear channel that there needs to be some clear announcement made. Kandiyohi County would push back because the people who are going to want us to patch that are agencies that refuse to buy encrypted radios, so it is jeopardizing why we have encryption. An example of a hostage situation was explained. 8

10 JOINT BUSINESS: (Continued) c. Encryption discussion (Continued) Lahr asked the group where do you want the next discussion to start? Do you want a technical overview: Here is your encrypted talkgroup; This is how the encryption is applied in the system; This is how it needs to be programmed into your radio. Or, do we talk bigger picture? Lindquist asked would it be beneficial for the next meeting to come with an encrypted radio? Lahr said we can do a couple of quick tests to see if we can all hear each other on our regional/statewide encrypted talkgroups. Myers would suggest having people start answering the questions and taking an asset inventory: Radio model, what I have for encryption, when are you using it, how frequently are you using it? Lahr replied people can fill it out in the room and hand it in at the end of the meeting. USER BUSINESS: a Training: a. Upcoming: ARMER Radio Trainer December 6, Stevens County b. Recent: REFRESHER: ARMER Radio Trainer Diehl reported it was very good with interesting discussions. Lindquist stated next month will be the City of St. Cloud for a User s training or communication event. Pope County suggested an encryption discussion. REPORTS: CMESB: Emergency Services Board (ESB) December 19, 2018 Board met on the 26 th. Going forward the ESB did take action to allow administratively the contract that we have to do with Alex Tech to use their facility. The Board chair can sign off on it as long as it remains a $0 sum. Executive Committee Looking at utilization of Microsoft s One Drive out of Office 365 and also looking at using an electronic signature program to get contracts signed. We will be electing a new Chair at the December meeting for going into January. With the pending elections, we assume there will be some who will make the request as to whether, or not, they want the training if we have new Commissioners coming on board. Regional Advisory Committee (RAC) November 9 (Stearns County) Met on Friday. We had a good discussion on centralizing the RAC instead of moving it around the region like we have been. With the Attendance Policy, we want to do our best effort. We talked about looking at voice and video conferencing, but there are always challenges. We want to still keep them face-to-face. Tait introduced himself to the group. Next Generation 911 Committee Diehl reported we had our statewide meeting yesterday. Two COOP plans in Central MN have been reviewed and all in Central MN have been turned in. There were no unplanned StatusBoard outages last month. The refresh rate has been changed down to 90 seconds. Please hit refresh before you make a reservation. One county had a problem with getting logged off occasionally. It was because a user had been deleted from the system and they had a future reservation made, so it was bumping their dispatchers off. They are saying do not delete just lock their account. Dustin Leslie had said for text-to-911 Winona went live, Dakota, Chisago, Eden Prairie then Wright County are next. Last month there were only 344 texts. Dan Craigie mentioned better caller location for wireless calls; AT&T is looking at turning on the device location in December. 9

11 REPORTS: (Continued) CMESB: (Continued) Next Generation 911 Committee (Continued) We had discussion on what the class of service will show up on the CPE at the PSAP. Verizon went with Comtech and you get a zero uncertainty. There is a CPR bill that will probably be passed. It will require dispatchers to give emergency medical dispatch advice to a caller. We talked about maintenance and outage notifications. We are going to try to get better information on outage and maintenance. Mille Lacs County had reported there were 34 text messages for our region last month. Firewall that was installed at the Minneapolis airport did fail again. They are considering trying the Ramsey back-up location. We talked about a shared CAD Subcommittee/workgroup. The geospatial validation and edge matching deadlines are due November 30 th. EMAC Ingram reported this past Tuesday we had an EOC exercise. It was supposed to be for Mutual Aid, but we ended up spending a lot of time working with HSEM representative on their web EOC application. On the 24 th, we will be having our EMAC quarterly meeting in Swift County. On December 5 th, we are going to have our end of year meeting in Fergus Falls we will be electing a Chair and Vice Chair. Regional Logger Committee: (Brandon Larson s report) The CM Logger committee last met following the RAC and approved a data request form. There was discussion surrounding the ARMER upgrade and the upgrade timeline for the logger. Discussion will continue at the next meeting regarding a potential new membership type for the committee. Grant Updates Myers reported the only new item is there was a grant sent on the list serve the AFG grant due next week. We put in the Albany schools if there are any turnback funds available. In infrastructure report you will see what is pending for BDAs. Grant County applied for one of the School Safety grants and their school actually got their BDA project covered 100%. Diehl asked Stevens County has the two T1 lines that go to our tower site and connect our consoles with the tower site. Federated telephones seem to do maintenance on those T1 lines and our consoles go down. Tom Justin had wondered why we do not have a secondary microwave link. Is there ever any grant money available? Lahr answered that Stearns County did that last year, they had a couple sites that only had one path back to zone controller so we added redundant links to all of our tower sites and we needed to upgrade some of our microwaves that were end of life. REPORTS: SECB/ARMER: Operations and Technical Committee (OTC) No meeting. Interoperability Committee No meeting. a. STR Subcommittee December will be the next meeting. b. COMU Subcommittee Wrobbel reported we had a telephone call on Tuesday. We approved a bunch of COMU and ASCI certifications. We went over standards and cleaned-up language. 10

12 REPORTS: (Continued) SECB/ARMER: (Continued) Interoperability Committee (Continued) c. EMS/Hospital Subcommittee McIntyre reported we are still meeting monthly with the people that represent the board and all the subcommittees to the state radio board and to the MAA. Started meeting quarterly for the MAA board meetings. We have worked to make sure all of the committees we represent to the communications side are met. There is one opening for an alternate for the OTC if anyone knows any EMS that would be interested. Discussion of how we structure to bring back the EMS/Hospital Subcommittee formally. We are hoping to have a meeting yet this year and set a schedule for McIntyre reminded the group when you are bringing the aircraft in for EMS they get assigned the STAC and that should be a person on the ground talking directly with the aircraft. It should not be the day-to-day thing to patch in to the local interop talkgroup. Interop Data Committee (FirstNet) (Brandon Larson s report) We met in-person on Monday, there was a good discussion surrounding priority levels of FirstNet devices that can be set in the FirstNet portal. The discussion surrounded whether or not there should be a guide for users in the state as to what priority certain devices should be set when the line of service is provisioned. See the IDC packet for informational fliers regarding FirstNet deployables and products. After the close of the meeting OEC provided a presentation from the Mille Lacs County cellular drive test. After that was a meeting with the FirstNet Authority discussing the I-35 bridge collapse the series of response events, the technology in use during the response and how it would have changed with today s broadband technology. Hausauer noted she was randomly reached out to by somebody that wanted to solicit her business for FirstNet. Hausauer gets an or a phone call every single day for the last ten days. Lahr replied Stearns County does have an information meeting with an AT&T representative and Shane Olson and Lahr was going to run by this contact person. SWIC Stromberg cautioned to please engage Steve Tait before anybody makes a decision. Tait noted there are some counties on the northern part of the state that have been burned. Melinda Miller has put together a road map on things you should look at in making your decision. Steering Committee Lahr reported the Steering Committee met last week. We reviewed sections of the SECB Bylaws. SECB Bylaws also pair up with some language in statute that outlines the SECB how that committee is made up. There are a lot of things written into statute that would be better in Bylaws (meeting schedules, rules on cancellation of meetings, etc.). Stromberg stated the one that probably belongs in statute is the composition of the statewide communications board. For example, adding tribal bodies to the SECB is something that should be a legislative matter for the SECB. Lahr stated then the Bylaws will be updated. Update on the ARMER fees and participation by federal agencies. Director Wahlberg is struggling to get a solid decision from legal on whether, or not, charging a fee to federal agencies, or allowing federal agencies, to utilize the ARMER system which is being paid for by 911 fees is allowable, or if we are going against statute. Wahlberg has a feeling that some of the hesitation on getting a decision may have to do with the upcoming election. Director Wahlberg gave an update on some potential progress on trying to come up with a way to negotiate with Motorola on SUA contract. ECN is moving forward with writing an RFP to work with a consultant on negotiating with Motorola. Stromberg explained the vague high-level descriptions are not supporting the amount they want to charge. They might want to charge us for what the DOT is already doing for us. What they are asking is a lot more than we have paid in the past. Request to change regional delegate to Kristen Lahr, alternate as Tina Lindquist for Central Region. 11

13 REPORTS: (Continued) SECB/ARMER: (Continued) SMG (System Managers Group) Lahr reported there was a presentation by Motorola on the upgrade. They covered more of the new features that were available, but most of those features relied on data on the system for us to benefit from them. They went over finalized dates and times for any types of system outage. Tuesday the 23 rd is the next MTUG meeting in Rochester. NEXT MEETING: The next O&O/Users meeting will be November 15, 2018 at 10:00 AM at Douglas County Public Works. ADJORNMENT: Grant County made a motion to adjourn the meeting. Stevens County seconded and the motion was carried unanimously. The meeting adjourned at 12:17 p.m. Minutes recorded by Shari Gieseke. 12

14 612 Industrial DR SW, Willmar, MN Kandiyohi County Sheriff per Standard rd ST NE Suite 103 Willmar, MN Re: Application for FCC License for a CRAE using 8Tac 94 covering the City of Atwater. Kandiyohi County will request to install a CRAE (Conventional Resource ARMER Enhancement) repeater system, using NPSPAC 9TAC 94 channel for use by Emergency personal, for interoperability purposes for in building coverage through-out the city of Atwater. ARMER portable radio coverage within buildings in Atwater is not reliable. Use of SOA channels do not cover the city properties. By implementing a CRAE system in Atwater will give Emergency Repsonders unit to unit communications in Atwater, and access to a Kandiyohi County ARMER talk group. The coverage footprint will be limited for in building, town coverage, this will be achieved by, low repeater tower height, low power, no gain repeater antenna. The NPSPAC frequencies and tones will be used in an analog mode per Federal standards, and are already programmed into Kandiyohi and other County radios which respond for Atwater Emergency Services. Kandiyohi County Sheriff will be responsible agency Kandiyohi County Sheriff Stacey Bonnema rd St NE Suite 101 Willmar, MN Kandiyohi County CRAE will be submitted to Central Minnesota Emergency Service Board. It will also notify South Central and South West Regions which are within the 30-air mile range from Atwater. Once approval from all regions is received it will be forwarded to the Operations and Technical Committee for approval. The search for 8Tac94 licensed channels shows no use of this channel remotely close to Atwater. Attached are copies of the FCC License schedule D & H, and the search results. Kandiyohi Local System Administrator will be responsible for training of this CRAE. He will also update the Regional CASM (Communication Asset Survey Mapping) plan, and will also coordinate with SWIC (Statewide Interoperability Coordinator) to add this resource to the MNFOG plan. Submitted by: West Central Communications, David Sisser

15 Kerri Gortmaker, Senior Special Agent BNSF Railway Police 801 Main Ave Fargo, ND Office November 9, 2018 Director Micah Myers Central RAC Chair Subject: Interoperability Participation Plan Dear Director Myers, The BNSF Railway Police Department is currently operating on the Minnesota Allied Radio Matrix for Emergency Response (ARMER) system as a Metro Region interoperability user under an agreement with Anoka County. Because we have personnel operating throughout the state, our department is respectfully requesting authorization to expand their current ARMER system interoperability capabilities to include the regions in greater Minnesota. Prior to seeking approval from the Statewide Emergency Communications Board (SECB) Operations and Technical Committee (OTC), we are seeking the Central Region s support and endorsement of the interoperability plan proposal. The BNSF Railway Police Department protects and monitors 1,701 miles of track lines in the state of Minnesota and responds to approximately 1200 calls for service each year. Our Special Agents interact with local public safety agencies on incidents, community partnerships, community events, training events, and criminal investigations. We work to ensure a safe environment for BNSF Railway employees and the communities we serve. BNSF Railway Police Department Special Agents in the state of Minnesota conduct law enforcement functions under authority from the U.S. Secretary of Transportation Chapter 281, Subsection (49USC28101), which grants us authority to carry an officer s police commission from one state into another for specific, clearly defined rail-protection purposes. In order to complete our mission within Minnesota, we work closely in conjunction with city, county, and state law enforcement agencies in the course of investigations, emergency response, and enforcement activities. These activities require us to have the ability to quickly and compatibly communicate with law enforcement and other emergency response units. Above all, as railroad police officers most often work as single person units, mainly itinerant through the state; we feel the most vital need is the increase to officer safety while operating in the field. Our desire in seeking to join Minnesota Agencies on the ARMER system is for these interoperability purposes only, as our day-to-day operational communications are conducted on BNSF specific systems.

16 The proposed ARMER Interoperability Participation Plan is included as an attachment to this letter. All BNSF Railway Police Department users will utilize Minnesota SECB approved equipment and will undertake required training as required prior to any use of ARMER resources. I am available to answer any questions and to work as a point of contact for the BNSF Railway Police Department. We appreciate your time and look forward to working with you throughout this process. Sincerely, Kerri Gortmaker

17 INTEROPERABILITY PARTICIPATION PLAN: BNSF RAILWAY POLICE DEPARTMENT Section 1A: Agency ARMER Infrastructure Elements None Section 1B: Agency ARMER Subscriber Equipment Motorola Portable Radios Quantity Equipment Area of Operation 12 Motorola Apex Radios Statewide This equipment will be maintained in accordance with Statewide Emergency Communications Board (SECB) Standard and with a fleetmap consistent with that standard. Section 2: Other Equipment None Section 3: Radio User ID Requested The BNSF Railway Police Department respectfully requests the following quantity of radio user IDs: Purpose Current Number Estimated Three Year Growth Law Enforcement Interoperability Section 4: Additions to the ARMER Interoperability Infrastructure None Section 5: Interoperability Talkgroups The BNSF Railway Police Department propose the following ARMER talkgroup resources to achieve radio interoperability with Federal, State, and local partners in the performance of public safety activities: Law MN Metro NW NE MSP CALL MSP CALL MSPCALL NW CALL NE CALL LTAC1 STAC1 METAC1 NW2 NE2 LTAC2 STAC2 METAC2 NW3 NE3 LTAC3 STAC3 METAC3 NW4 NE4 Page 1 of 3

18 Law MN Metro NW NE LTAC4 STAC4 METAC4 NW5 NE5 STAC5 METAC5 NW6 NE6 STAC6 METAC6 NW7 NE7 STAC7 METAC7 NW8 NE8 STAC8 METAC8 NW9 NE9 STAC9 NW10 NE10 STAC10 NW11 NE11 STAC11 NW12 NE12 STAC12 CM SW SC SE 8C CM CALL SW CALL SC CALL SE CALL 8CALL90 CM2 SW2 SC2 SE2 8TAC91 CM3 SW3 SC3 SE3 8TAC92 CM4 SW4 SC4 SE4 8TAC93 CM5 SW5 SC5 SE5 8TAC94 CM6 SW6 SC6 SE6 8CALL90D CM7 SW7 SC7 SE7 8TAC91D CM8 SW8 SC8 SE8 8TAC92D CM9 SW9 SC9 SE9 8TAC93D CM10 SW10 SC10 SE10 8TAC94D CM11 SW11 SC11 SE11 SOA1 CM12 SW12 SC12 SE12 SOA2 SOA3 SOA4 Additional Talkgroup authorizations may be sought and obtained through controlling authorities such as individual counties and entities authorized to grant these permissions. All additional authorizations will be obtained per applicable SECB Standards. Section 6: BNSF Railway Police Department Specific Talkgroups None - Day-to-day operational communications will be conducted on BNSF Railway systems. Section 7: Training BNSF Railway Police Department personnel will not be allowed to use ARMER subscriber equipment programmed with ARMER resources until such time as they have been provided appropriate training as required by applicable SECB Standards. Page 2 of 3

19 Section 8: Designated Local Administrator BNSF will contract with SECB approved System Administrators (e.g. Brian Zastoupil, NW Region and Jake Thompson, Metro Region). The following person is designated as the agency administrative contact for any issues related to operation, deployment, and maintenance of the resources described herein: Kerri Gortmaker, Senior Special Agent BNSF Railway Police Department (Office) (Cell) (Agency Contact Signature) (Date) Page 3 of 3

20 11/6/2018 Homes raided, stolen police radio data put officers at risk Homes raided, stolen police radio data put o cers at risk By Repository staff report Posted Oct 23, 2018 at 2:09 PM Updated Oct 23, 2018 at 9:14 PM Someone has downloaded pilfered police radio templates onto several other black market radios, putting police and firefighting lives in danger, authorities say. Federal and local authorities raided seven homes Monday, seizing weapons and cloned police radios. Someone with templates of stolen or borrowed police or fire radios used those templates to hack into the public safety radio system by cloning the information and duplicating it onto police radios sold on the black market, Stark County Sheriff George T. Maier said Tuesday. Authorities believe the people using the cloned radios also were armed. Stark County Sheriff s deputies and Canton police, along with the U.S. Department of Alcohol, Tobacco, Firearms and Explosives, raided seven homes Monday seizing weapons and dozens of radios and other evidence as a result of their investigation into the stolen police radio data, the sheriff said. We ve identified eight to 10 people that are involved in this, people that we believe are the ones who did the cloning and the selling, he said. They remained persons of interest on Tuesday and had not yet been charged. All of them are adults. Investigators do not yet know how long people with these pilfered radio codes have been listening in on local law enforcement activity. People with these radios downloaded with those codes can even transmit. We just learned about it a week ago, Maier said. Officials with the Multi-Agency Radio Communication System, referred to as MARCS, watch the system to see where all law enforcement radios on their system are being used. Maier said they found extra radios using the system with the same code or key that is supposed to be used by radios already registered to the current system. By using a radio that has been coded with a police or firefighter s radio key, an officer s plea for help at an emergency may never be heard. If an officer in an emergency is trying to use his radio and the person with the cloned radio is using his signal, the officer s radio could be blocked, Maier said. That s the sense of urgency related to this crime. They are disrupting public service on a large-scale level, he said. Where did they get the radio key? Maier said one radio was stolen from the Canton Police Department and the investigation has revealed some duplicate keys were made of templates on radios used by the sheriff s department. But the culprit only needs the radio for a minute to download the key and clone it. It can then be replicated onto several other radios. He or she could have returned the registered radio undetected. 1/2

21 11/6/2018 Homes raided, stolen police radio data put officers at risk One they get one, they don t need any more. They can duplicated it onto several other radios. The problem is, it s a safety issue and they re infiltrating a public safety radio system, the sheriff said. The radios aren t new. These are all old radios. The radios that were stolen are radios that are used right now. They re not the new radios that we re getting. None of the new radios are missing, Maier said. And while the thief or thieves could share across state lines, Maier said investigators believe the issue is still just a local one. We think it s between us and maybe Summit County, and they have been contacted, he said. We re still investigating. We ll have those answers soon. Reach The Canton Repository at or newsroom@cantonrep.com. 2/2

22 Central MN ESB Region Allied Radio Matrix for Emergency Response (ARMER) Standards, Protocols, Procedures Document Section: 1. Management of System CM O&O Approved Sub-Section: CM Date: Procedure Title: Requesting Full Participation Date Established: April 22, 2009 Replaces Document Dated: April 22, 2009 ESB Approval: Date Revised: Date: 4/22/ Purpose or Objective To establish a procedure for an eligible entity, such as a county, a city, an EMS provider, or a special purpose governmental agency to apply for full participation in the Central region of the ARMER (Allied Radio Matrix for Emergency Response) system. 2. Technical Background: The following definitions apply to this standard: Public Safety Agency: is defined as a functional division of a public agency which provides firefighting, law enforcement, medical, or emergency management services, or a private entity which provides emergency medical or ambulance services Public Service Organization: is defined as a public facility, department, agency, board, or commission; owned, operated, or managed by on behalf of the state of Minnesota, or any subdivision thereof, including any county, city, town, township, or independent district in the state. EMS Provider: is defined as one licensed by the Minnesota Emergency Service Regulatory Board (EMSRB) to provide services with a designated emergency primary services area (PSA) where they are responsible to respond to medical 911 calls for service; or ambulance, also licensed by the EMSRB that provides emergency response. Capabilities The entity requesting participation must be prepared to migrate to the ARMER system. This will require a technical design document approved by the CM Owners and Operators Committee (CMO&O) and the Central Minnesota Emergency Services Board (CMESB). In addition it will require the purchase and installation of new equipment compatible with the ARMER system within the CM Region. Constraints The technical design plan must be consistent with the capacity constraints and operating constraints of the system. Operational plans must be consistent with established regional and statewide operational standards. Eligibility Eligibility for full ARMER participation is limited to public safety agencies and public service organizations as defined in Section 2 of this standard Managing Full Participation 1 Section #

23 3. Operational Context: Generally there are three ways to participate in the central region of the ARMER system: full participation, limited participation, and interoperability participation. Limited participation is through patches via a gateway device from a full participant. Interoperability participations is owning ARMER subscriber equipment for the purpose of communicating on ARMER for interoperability in an emergent event with a full participant. This procedure deals only with those entities seeking full participation 4. Recommended Protocol/ Standard: Requests for full participation shall be submitted by in writing by the governing board of the requesting entity to the CMESB via the CM Regional Coordinator. The requesting agency shall submit a design document to the CMESB, providing complete details on its plan for participation in the CM regional area of the ARMER system. The plan shall be subject to a review process, including but not limited to review by the CM O&O, by a qualified consulting professional engineer, by the Minnesota Department of Transportation, and by the CMESB. 5. Recommended Procedure: The request shall indicate any actions taken by the local governing board, including but not limited to detail on the extent to which the requesting entity has developed designs and plans for full participation. The written request shall indicate the name and contact information for the person designated to lead the project. The Regional Coordinator of the CMESB shall forward copies of the request to the Chair of the Owners and Operators Committee and to the Director of Electronic Communication for the Minnesota Department of Transportation. If a technical design plan is already in place, the entity shall submit the plan to the Central Minnesota Owners and Operators Committee (CMO&O) after which the CMO&O shall review the plan for compliance and compatibility with the CMESB s plan. The requesting entity should, as part of its planning process, retain the services of a qualified consulting engineer. Ideally the individual retained should be familiar with the ARMER system. Costs associated with the development of a technical design shall be borne by the requesting agency. When the design plan is complete, it shall be submitted to the CMO&O, which shall review the plan for compliance and compatibility with the CMESB s plan. The CMO&O shall report its findings to the CMESB. The CMESB shall act on the request within a reasonable time period. The CMESB may accept the request as submitted, accept the request with conditions or deny the request. If the request is initially denied, the CMESB shall provide details on changes or additions to the design plan that will bring the plan into compliance with the Board s plan Managing Full Participation 2 Section #

24 Following making design changes that bring the local entity s plan into compliance with the Board s plan, the requesting entity may resubmit its request. The CMESB may not deny the request if the design plan is compatible with the CMESB s region-wide plan. 6. Management The CM Owners & Operators Committee and the Central Minnesota Emergency Services Board are responsible for management of this procedure Managing Full Participation 3 Section #

25 Central MN ESB Region 800 MHz Trunked Regional Public Safety Radio System Allied Radio Matrix for Emgergency Response (ARMER) Standards, Protocols, Procedures Document Section: Requesting Full CMNRAC CM O&O Participation1. Management ReviewApproved Signature of System Sub-Section: Central MN Date: Procedure Title: Requesting Full Participation Date Established: April 22, 2009 Replaces Document Dated: April 22, 2009 CMNRRB ESB Approval Signature: Date Revised: Date: 4/22/ Purpose or Objective To establish a procedure for an eligible entity, such as a county, a city, an EMS provider, or a special purpose governmental agency to apply for full participation in the Central regionwide 800 MHz digital trunked public safety radio of the ARMER (Allied Radio Matrix for Emergency Response) system. 2. Technical Background: The following definitions apply to this standard: Public Safety Agency: is defined as a functional division of a public agency which provides firefighting, law enforcement, medical, or emergency management services, or a private entity which provides emergency medical or ambulance services Public Service Organization: is defined as a public facility, department, agency, board, or commission; owned, operated, or managed by on behalf of the state of Minnesota, or any subdivision thereof, including any county, city, town, township, or independent district in the state. EMS Provider: is defined as one licensed by the Minnesota Emergency Service Regulatory Board (EMSRB) to provide services with a designated emergency primary services area (PSA) where they are responsible to respond to medical 911 calls for service; or ambulance, also licensed by the EMSRB that provides emergency response. Capabilities The entity requesting participation must be prepared to migrate to an APCO Project 25- compliant 800 MHz digital trunked radiothe ARMER system. This will require a technical design document approved by the Regional Advisory CommitteeCM Owners and Operators Committee (CMO&O) and the Central Minnesota Regional RadioEmergency Services Board (CMESB). In addition it will require the purchase and installation of new equipment compatible with the existing region-wide ARMER system within the CM Region Managing Full Participation 1 Section #

26 Constraints Minnesota Statutes Subdivision 2. Requirements to Join, states: Local governments and other entities eligible to join the regional public safety radio system which elect to join the system must do so in accordance with and meet the requirements of the plan adopted by the radio board. The technical design plan must be consistent with the capacity constraints and operating constraints of the first phase system. Operational plans must be consistent with established regional and statewide operational standards. Eligibility Elibigility for full ARMER participation is limited to public safety agencies and public service organizations as defined in Section 2 of this standard. 3. Operational Context: Generally there are two three ways to participate in the region-wide 800 MHz systemcentral region of the ARMER system: These are through full participation, and limited participation, and through interoperability participation. Limited participation is through interoperability is possible by those entities operating on VHF, UHF or 800 MHz analog systemspatches via a gateway device from a full participant. Interoperability participations is owning ARMER subscriber equipment for the purpose of communicating on ARMER for interoperability in an emergent event with a full participant. This procedure deals only with those entities seeking full participation Managing Full Participation 2 Section #

27 4. Recommended Protocol/ Standard: Requests for full participation shall be submitted by in writing by the governing board of the requesting entity to the CMESB via the CM Regional Coordinator.Central Minnesota Regional Radio Board (CMNRRB). The requesting agency shall submit a design document to the CMESB, providing complete details on its plan for participation in the CM regional area of the ARMER system. The plan shall be subject to a review process, including but not limited to review by the CM O&O, by a qualified consulting professional engineer, by the Minnesota Department of Transportation, and by the CMESB. Items that should be in the plan include: o Site additions o Channel additions o Equipment additions o Frequency plan o Subscriber radios o Talk groups o Prelim Fleet Map o PSAP Consoles o PSAP Logging o ATIA Data requirement o Contingency/backup o Connectivity o Alarm & monitoring o Training plan o Cut over plan o Schedule o Interop o System administration o Maintenance o Other local elements 5. Recommended Procedure: The request shall indicate any actions taken by the local governing board, including but not limited to detail on the extent to which the requesting entity has developed designs and plans for full participation. The written request shall indicate the name and contact information for the person designated to lead the project. The Executive DirectorRegional Coordinator of the Central Minnesota Regional Radio BoardCMESB shall forward copies of the request to the Chair of the Regional AdvisoryOwners and Operators Committee and to the Director of Electronic Communication for the Minnesota Department of Transportation Managing Full Participation 3 Section #

28 If a technical design plan is already in place, the entity shall submit the plan to the Central Minnesota Regional AdvisoryOwners and Operators Committee (CMNRACCMO&O) after which the CMNRAC CMO&O shall review the plan for compliance and compatibility with the Radio BoardCMESB s plan. If a technical design plan is not in place CMNRRB staff will work with the requesting entity to help it develop a plan. Costs associated with the development of a technical design shall be borne by the requesting agency. When the design plan is complete it shall be submitted to the CMNRAC, which shall review the plan for compliance and compatibility with the CMNRRB s plan. The CMNRAC shall than report its recommendations to the CMNRRB. The requesting entity should, as part of its planning process, retain the services of a qualified consulting engineer. Ideally the individual retained should be familiar with the ARMER system. Costs associated with the development of a technical design shall be borne by the requesting agency. When the design plan is complete, it shall be submitted to the CMO&O, which shall review the plan for compliance and compatibility with the CMESB s plan. The CMO&O shall report its findings to the CMESB. The CMNRRB CMESB shall act on the request within a reasonable time period. The CMNRRB CMESB may accept the request as submitted, accept the request with conditions or deny the request. If the request is initially denied, the CMNRRB CMESB shall provide details on changes or additions to the design plan that will bring the plan into compliance with the Board s plan. Following making design changes that bring the local entity s plan into compliance with the Board s plan, the requesting entity may resubmit its request. The CMNRRB CMESB may not deny the request if the design plan is compatible with the CMNRRB s CMESB s regionwide plan. 6. Management The Executive Director andcm Owners & Operators Committee staff of theand the Central Minnesota Regional RadioEmergency Services Board are responsible for management of this procedure Managing Full Participation 4 Section #

29 2019 CENTRAL MN OWNERS AND OPERATORS & USERS MEETING SCHEDULE (These are tentative dates and are subject to change.) Date Time Location January 17 10:00 a.m. Douglas County Public Works February 21 10:00 a.m. Douglas County Public Works March 21 10:00 a.m. Douglas County Public Works April 18 10:00 a.m. Douglas County Public Works May 16 10:00 a.m. Douglas County Public Works June 20 10:00 a.m. Douglas County Public Works July 18 10:00 a.m. Douglas County Public Works August 15 10:00 a.m. Douglas County Public Works September 19 10:00 a.m. Douglas County Public Works October 17 10:00 a.m. Douglas County Public Works (Unknown) November 21 10:00 a.m. Douglas County Public Works (Unknown) December 19 10:00 a.m. Douglas County Public Works (Unknown)