On the agenda: St Cloud Regions Of The Statewide Emergency Communications Board meeting — data center (Sep 17)

Central Minnesota Regional Logger Committee
Location: Alexandria & Microsoft Teams Meeting

Online: Teams Meeting Link (Meeting ID: 278 167 313 071 Passcode: j8YPsn)
Phone: (320) 460-1141, Conference ID: 683 560 40#
Thursday, September 17, 2026

*Meeting will begin following the joint O&O/Users/RAC meeting*
Agenda
1. Call to Order
2. Roll Call
3. Revisions and Approval of Agenda (P1)
4. Approval of Minutes: July 16, 2026 (P2-7)
5. Communications
New Business
6. Discussion on upgrading Logger core
a. 2027 Logger Update (P8-9)
b. Motorola AIS (P10)
c. Motorola API Quote (P11)
d. BCA Requirements
e. Limited Members outreach on Budget
i. Sherburne County
ii. Washington County
iii. Sanford Health EMS
iv. CentraCare EMS
v. M Health EMS
7. Posting of the Logger Plan (P12-21) (Action Item)
Old Business
8. Logger Update
9. Logger User Concerns
10.Open Discussion
11.Next Meeting (View Meeting Schedule)
October 9th Teams Meeting/November 19th Joint Meeting
12.Adjourn

1

Central Minnesota
Regional Logger Committee Meeting
Douglas County Public Works – 526 Willow Dr, Alexandria, MN 56308
Hybrid Microsoft Teams Meeting
July 16, 2026 – 11:37 a.m.
Members/Alternates Present:
1.
Micah Myers, Chair – City of St. Cloud
2.
Julie Fraley – Benton County*
3.
Tom Egan* & Kevin Smith – Douglas County
4.
Sheriff Jennifer Vipond & Josh Ulrich – Grant County*
5.
Jody Norstegard – Kandiyohi County
6.
Bill Hudson – Meeker County*
7.
Andy Beckstrom, Vice Chair – Mille Lacs County
8.
Greg Seim – Otter Tail County
9.
Bryan Gates – Pope County*
10. Michele Burke* & Kristen Lahr – Stearns County
11. Haley Dubois – Wright County*
Members/Alternates Absent:
12. Big Stone County
13. Stevens County
14. Wilkin County
Guests Present:
1. Nathan Lahr – City of St. Cloud
2. Kent Bauman– Kandiyohi County
3. Joel Richter – Stearns County
4. Paul Botnen – CentraCare
5. Paul McIntyre – Mayo Clinic Ambulance*
6. Don Martin – Sanford Health*
7. Dereck Leyde – Northland & Companies*
8. Heidi Schultz – Northland & Companies*

Introductions:
Introductions were conducted. There was a quorum for the Committee.
* = Interactive Technology
Approval of the Agenda
Stearns County made a motion to approve the agenda. Douglas County seconded, motion carried.
Roll Call Vote: City of St. Cloud – Aye; Benton – Aye; Douglas – Aye; Grant – Aye; Kandiyohi – Aye;
Mille Lacs – Aye; Otter Tail – Aye; Pope – Aye; Stearns – Aye; Stevens – Aye; Wright – Aye.

1
2

Approval of Minutes
Otter Tail County motioned to approve the minutes from June 12, 2026. Mille Lacs County seconded,
motion carried. Roll Call Vote: City of St. Cloud – Aye; Benton – Aye; Douglas – Aye; Grant – Aye;
Kandiyohi – Aye; Mille Lacs – Aye; Otter Tail – Aye; Pope – Aye; Stearns – Aye; Stevens – Aye;
Wright – Aye.
Communications
None.
NEW BUSINESS
6. Stearns County Logger Capacity Request (Action Item)
Stearns County plans to move law enforcement dispatch traffic to an encrypted talk path in 2027.
Date is yet to be determined. A new talkgroup has been created for this purpose and Stearns is
requesting logging capacity on the CM Logger for this talkgroup. Pending approval by this
committee, Stearns County will coordinate with Northland on the purchase of licenses and
configuration in early 2027. Motion to approve the request from Stearns County to add the
additional encrypted talkgroups to the Logger. Mille Lacs County motioned. Benton County
seconded. Roll Call Vote: City of St. Cloud – Aye; Benton – Aye; Douglas – Aye; Grant – Aye;
Kandiyohi – Aye; Meeker – Aye; Mille Lacs – Aye; Otter Tail – Aye; Pope – Aye; Stearns – Aye;
Stevens – Aye; Wright – Aye. Motion carried.
7. Discussion on upgrading Logger core
a. 2027 Budget (Action Item)
Myers presented the 2027 budget and requested approval. Summary of spoken budget
details:
• SLA membership increased 7%: last year $8,900 this year $9,525
• Limited participation members expected: Washington County, Sherburne County, M Health,
CentraCare. There are 5 of them.
• Annual maintenance cost for the API (Verint) increased
• Motorola previously waived a $60,000+ bill; previous budget cycles we had that number at
15K; historically budgeted around $7,500 annually.
• Two-year AES encryption upgrade cost paid in two annual payments (~$8,975 each).
• Washington County’s AIS service contribution offset ($50,000 value) ended; Washington
County now pays full membership. It was an offset of $12,500 for 4 years in a row.
• Full member contribution now $6,600 (down about $600 due to Washington County
payment starting).
Myers looked for a motion to approve the budget presented here today. Otter Tail County
motion. Kandiyohi County seconded. Roll Call Vote: City of St. Cloud – Aye; Benton – Aye;
Douglas – Aye; Grant – Aye; Kandiyohi – Aye; Meeker – Aye; Mille Lacs – Aye; Otter Tail –
Aye; Pope – Aye; Stearns – Aye; Stevens – Aye; Wright – Aye. Motion carried.

2
3

NEW BUSINESS (Continued)
7. Discussion on upgrading Logger core
b. Motorola API Quote
Myers explained we had the bill, Northland had agreed to remove their costs. With the
current SUA agreement , there’s two upgrades. If we go with Revcord and we go to the
upgrades, do we have to pay this freight?
Leyde explained going forward with RevCord, there is no mandatory charge for these
upgrades unless that API indefinitely does change. RevCord is the only logging manufacturer
that is not going to mandate this. All the other logging manufacturers is a big reason why
we've partnered with Revcord to be their national distributor. All other manufacturers,
including Verint, Eventide, you name it, they're now saying it's mandatory to pay that every
two years. So, if there's a change in the API, then we'll have to charge it, but we're going to
have it funneled through Motorola. That's what we would prefer to do, because it's a
Motorola charge rather than putting us in the middle.
Myers is looking at pulling a substantial amount out of our reserve, which we built. We have
a reserve under the logger side to do that, but leaving enough in the bank for if we see the
API change down the road. One thing is certain that we do have to either upgrade the Verint
or we have to switch to RevCord. The other item we'll have to negotiate is that transfer fee
around $60K; if we can get that waived. And then there's the other costs on it, and I haven't
gotten an answer on, the BCA and this is one of the ones when we talk about encryption at rest.
Myers explained Northland met with each of our member agencies and even our limited to
go over what it would cost to upgrade their premise logger, because that's a component. If
we go with RevCord, depending on the timeliness of people being able to upgrade their
premise logger is going to determine if we can go full on or if we're going to do in a phase
one, phase two approach. If we can get a date that we can get everyone on board, if they're
going to switch and upgrade their premise loggers, we wanted to give you numbers so you
can plan. Do we do it in a phased approach? Myers asked Northland does it make a
difference if we do a phase or an all in one fell swoop for pricing? I thought if we prepaid up,
there was the prepaid maintenance, we got a discount. If we do the upgrade all in one fell
swoop, do we get a discount? I'm looking at putting together a total number, so I can look at
if we agree to do this sometime in 2027, or whenever we decide to make that move to the
RevCord, how much time would the agencies need? So that's where I have this column in
there. I don't need to have an answer here today, but I would like to look at for planning
purposes that if we decide. My recommendation to the group would be to go with the
RevCord, because the total over the next period before we'd have to do next upgrade, it will
be significantly cheaper operationally-wise from the maintenance. As we talk about the
Motorola piece for the API, unless there's a change, we don't have to pay that fee. Overall
operational costs for RevCord, the one caveat is that we have to upgrade your premise
loggers to do that. In discussions with Washington County, Washington County said if we
remain with Verint, they were going to withdraw from the from the regional logger. They
want the functionality that it is with the RevCord. Myers asked the group is there anyone on
the call today that is adverse to us moving? There was no response.
3
4

NEW BUSINESS (Continued)
7. Discussion on upgrading Logger core (Continued)
b. Motorola API Quote (Continued)
Myers asked would there be any obstacles preventing you from upgrading your premise
loggers? We're under maintenance with Verint through July of next year. We’ve paid
Northland for that maintenance. If we're looking at doing a switch, would you be able to
replace yours in a year, which would be into the 2027 budget cycle? Would there be anyone
that couldn't accomplish that by the end of July when the maintenance for the Verint
expires? There was silence. By the time we have the logger meeting next month, if you
could look and see, because everyone's going through their budget process right now. If
there's anything that comes by way to say you can't do that in 2027, let us know. It sounds
like we want to move to RevCord. Whether we do it all in one fell swoop or we do the phase
approach. The phased approach will allow agencies time to upgrade their back-end
hardware. So, we put in our termination. We will not renew the Verint maintenance. If you
can provide to me a best guess, I'm not going to hold anything to it. Looking at when you
will be able to upgrade your premise loggers. And then we'll time it up. Once we know
everyone's schedule, then we will coordinate with Northland to do the core upgrade. We
can keep both systems running as just when we sunset them. I would look at a sunset date
for the Verint to be when the maintenance expires in July of 2027. And we'll look at getting
the core on board and everything, but we'd have to take an action with the group to move
forward with the RevCord option when we do our next upgrade, because we do have to do
an upgrade, whether it's Verint or whether it's RevCord.
Myers would look for a motion to move forward with RevCord as our recording solution.
Benton County moved. City of St. Cloud and Douglas County seconded. Roll Call Vote: City of
St. Cloud – Aye; Benton – Aye; Douglas – Aye; Grant – Aye; Kandiyohi – Aye; Mille Lacs –
Aye; Otter Tail – Aye; Pope – Aye; Stearns – Aye; Stevens – Aye; Wright – Aye. Motion
carried.
c. BCA Requirements
See Motorola API quote.
d. Limited Members outreach on Budget
i.
Sherburne County
Myers would do a follow-up with Northland to make sure they’re on board with
everything.
ii.
Washington County
See Motorola API quote.
iii.
Sanford Health EMS
Martin noted Sandford Health was already in the process of upgrading already, so
we are glad to hear you guys are moving forward with RevCord.
iv.
CentraCare EMS
Myers noted CentraCare does not really have any hardware online. Botnen stated at
the present time, not having a premise logger is the plan.
v.
M Health EMS
4
5

NEW BUSINESS (Continued)
8. Posting of the Logger Plan
Myers explained there were some changes that were made in the logger. There was more specific
detail in there as to firewall stuff we didn't want to put in. We will be looking at posting the logger
plan, but we're removing that language in the logger plan specifically calls out the model and make
of our firewall. It was 2021 was the last time this group had some discussions where they were
looking at making edits to it, but those edits were never taken back and fully adopted. That's what
we're looking for is the edits that the group had made. Otherwise, there was nothing else really
earth shattering we would consider as a security constraint. It was voted on and approved from this
group. We'll move that to the ESB for adoption. Once that has taken place, we will post that version
minus the firewall settings and it online. As we go forward with the logger, if we make changes, we
have to be mindful of the things that are in there as this document will be online.
OLD BUSINESS
9. Logger Update
Schultz did meet with each county or entity over the last month to discuss those individual plans to
move to RevCord. They have all been quoted for a like to like transition, as well as some of those
optional add-ons that would add value to their system, such as that Rapid SOS integration,
the cloud backup, or the automated transcription search and QA. I have provided additional demos
of the RevCord and Revi platforms to a few of the counties that have requested it. If anybody would
like to see another demo one-on-one, you can ask more detailed questions. About the RevCord
quote we provided to Central Region, the RevCord part does have encryption included. I just
wanted to be clear about that. Verint is that additional fee that you saw, but on the RevCord side, it
is included. Then for the individual counties, as you're trying to come up with funding, we can split
the payment of your upgrade with two budget years if we need to do that.
Myers asked the existing repositories we have, will those be migrated over? How is that handled
both on the premise and on the regional core?
Schultz responded we will migrate all that data over to the new system. It'll all be searchable and
you'll be able to create incidents like you do now. We'll just use your current retention period.
Myers asked the RevCord includes the encryption. The data that we currently have is not encrypted.
Will you encrypt it at that point when you migrate it?
Schultz replied yes, it will be encrypted when we migrate it onto the new system.
10. Logger User Concerns
a. Logger freezing
Myers stated so it's redirecting back to the premise instead of playing from the regional
loggers.
Leyde added this is something active our engineers are working on. There is some firewall
reconfiguration work it appears we're going to possibly need between Mille Lacs and St.
Cloud. We tried to make some host file edits to override that to make it static, and it seemed
like maybe it did help a little.
5
6

Open Discussion
None.
Next Meeting: August 14, 2026 – Microsoft Teams Meeting (Jointly after the RAC)/September 17
Adjournment
Chair Myers made the executive motion to adjourn the meeting and the motion was carried
unanimously at 12:17 p.m.
Minutes generated with the assistance of AI Microsoft Copilot and edited for accuracy by Shari
Gieseke.

6
7

Sales Proposal

Purchase

Date:

Equip Move

Lease

New Customer

Sales Rep: Dereck Leyde

6.3.2026

Maintenance Agreement

SHIP TO CUSTOMER

Central Region - Shared Equipment

SAME

Phone:

Phone:

Contact:

Contact:

Email:

Email:

Order To Be Filled

Ship Via

Requested Installation Date
(AM or PM)

Quantity

NBS Product No.

Demo

Present Customer

BILL TO CUSTOMER

COD

LaaS

Credit Memo

Order Delivered

Purchase
Order Number

Stairs:
Pick-up: (Yes
(Yes or No)
or No)

Pick-up Information
(List Model Info)

One Time Hardware/Permanent Software

Tax Exempt Number

Unit Price

Total

$203,998.00
included
included
included
included
-$50,000.00
-$25,000.00
$60,000.00

$203,998.00
included
included
included
included
-$50,000.00
-$25,000.00
$60,000.00

$125,000.00
included
included
included
-$19,000.00

$125,000.00
included
included
included
-$19,000.00

$227,762.50

$227,762.50

included
($10,000.00)

included
-$10,000.00

Phase 1
1
1
2
2
11
1
1
1

MCS
REVENT
USB3012P25
REVTRUNK
CHANTALK
DISCOUNT
DISCOUNT
MOTA-TRANSFER

Revcord 4U Rackmount Server 1TB RAID5, Dual Power, Full SQL
Revcord Enterprise License
12 Channel P25 Decoders
Interface for Wireline Trunked Radio to Motorola (per AIS)
Talk Path Recording Licenses
Northland Customer Loyalty Discount
Revcord Discount
Motorola Transfer Fee (paid directly to Motorola)

1
2
2
11
1

MCS
USB3012P25
REVTRUNK
CHANTALK
DISCOUNT

Revcord 4U Rackmount Server 1TB RAID5, Dual Power, Full SQL
12 Channel P25 Decoders
Interface for Wireline Trunked Radio to Motorola (per AIS)
Talk Path Recording Licenses
Northland Customer Loyalty Discount

Phase 3

Subscription Based Software and Annual Support
5 Years Hardware and Software Support Services*
Includes software updates and unlimited training
*Includes 5% pay up front discount

1

1
1

DISCOUNT

One-Time Professional Services
Project Management, Installation, Configuration and Training
Additional Discount if both Phase 1 and 3 are done at the same time

Total of Purchase and Five Years Maintenance

$512,760.50

Comments / Notes / Additional Information:
Central Region will need to provide 1 VM for the enterprise database logger. Northland will install Revcord software, configure and connect to AIS logger and
premise loggers.
50% of total is due with order, remaining 50% will be due at completion of installation.
Note: There is no charge by Revcord/Northland for any Motorola AIS updates if there isn't a change to the API.

Customer Signature: X

Date:

NBS Signature:

Date:

All mathematical and pricing errors are subject to correction upon invoicing.

This is not an invoice

8

Central Region Consolidation (MN) - Revcord v. Verint Pricing

Proposed Revcord System

Cost

PHASE 1: Purchase
Northland loyalty discount
Revcord discount
Motorola Transfer Fee

$
$
$
$

203,998.00
(50,000.00)
(25,000.00)
60,000.00

PHASE 3: Purchase
Northland loyalty discount

$
$

125,000.00
(19,000.00)

If Phases 1 and 3 are done at the same time: additional discount

$

(10,000.00)

Total Upgrade Fee

$ 284,998.00

Verint System

Cost

Upgrade current Verint system
Includes:
Encryption
2 AIS loggers
Verint License Transfer Fee

$

Total Upgrade Fee

$ 372,755.00

Maintenance Options

Maintenance Options

Option 1 - Pay for 5 years maintenance upfront
Includes a 5% discount on maintenance
Option 2 - Sign a 5 year contract, pay annually - price lock
Pay $47,950 per year
Option 3 - Pay for maintenance each year
with a 5% uplift

$

227,762.50

$

239,750.00

Option 1 - Pay for 5 years maintenance upfront
Includes 5% discount on maintenance and 2 cycles of Motorola AIS update fees
Option 2 - sign a 5 year contract, pay annually:
price lock at $66,000 per year and 2 cycles of Motorola AIS update fees

$

47,950.00

Option 3 - Pay for maintenance each year with a 5% uplift

372,755.00

$

318,750.00

$

330,000.00

$

45,000.00

9

Motorola AIS/VPM EOL

10

SALES QUOTE
Sales Quote No: SQ2328
Date: 3/13/25
Account No: MNCENR

Bill To:

Ship To:

MN Central Region Consolidation
Attn: Micah Myers
1201 7th Street South
St. Cloud, MN 56301

Sales Person

P.O. Number

Heidi Schultz

MN Central Region Consolidation
Attn: Micah Myers
1201 7th Street South
St. Cloud, MN 56301

Ship Method

Payment Terms

Quote Expires On

UPS Ground

Net 30

4/12/25

Notes
Mandatory upgrade as the State of Minnesota ARMER is upgrading to version 2024.1.
Item No
Logger - Labor

Description

Quantity

UM

Price

1.00

EA

$15,000.00

Motorola License Upgrade to 2024.1 (AIS 1)

Disc

Amount

0.00

$15,000.00

Logger - Labor

Motorola License Upgrade to 2024.1 (AISs 2, 3, 4)

3.00

EA

$12,500.00

0.00

$37,500.00

Logger - Labor

API Installation, Configuration, Testing

4.00

EA

$2,500.00

0.00

$10,000.00

Subtotal

$62,500.00

Discount

$0.00

Freight

$0.00

PLEASE REMIT PAYMENTS TO:
NBS/Wahltek - Payment Processing Center
12150 Nicollet Ave
Burnsville, MN 55337
For questions please call: 952-894-4204 or email [email protected] or [email protected].

Sales Tax

$0.00

Sales Order Total

$62,500.00

THANK YOU FOR YOUR BUSINESS!

12150 Nicollet Avenue Burnsville, MN 55337-1647

952-894-4204
11

Page 1 of 1

October 152, 20126

Central Minnesota
Emergency Services Board
Regional Logger Plan
ESB Approved January 2017
ESB Revision Approved September 2017
ESB Revision Approved March 2018
Amended September 17, 2026

12

TABLE OF CONTENTS
REGIONAL COMMUNICATIONS LOGGING PLAN
1.
2.
3.
4.

5.

6.
7.
8.
9.
10.
11.
12.
13.
14.
15.

Installation Timeline
Party Agreement
Additional Equipment
Network Connection
a. Firewall
b. VPN Access
c. Other Security Concerns
Required Equipment and Licensing
a. Hardware
1. Verint Premise Logger
2.
3.
b. Software/Licenses
1. Talkgroup License
2.
3.
Archiving
Training
System Administration
System Access Requirements
System Maintenance & Support
System Replacement
Operational Standards
Retention
Budget
a. Annual
b. Replacement and Emergency Fixes
Request for Recordings

APPENDICES
1.

Statements of Work

2.

Motorola Services and First Year Warranty

3.

Regional Resources

4.

Budget

5.

System Design

6.

System Admin Contacts

7.

Glossary of Terms

-2-

13

-3-

14

PREFACE
It is the intent of the requesting parties that the Logger Committee develop a Plan for the
provision of regional emergency communications recording and logging services
focusing on redundant centralized recording, management, administration and operation
for network communications across the ARMER network that is integrated with the
network technology and meets the regional requirements of the parties to the Agreement
forming the Central Minnesota ESB electing to participate in the Logger Committee. The
Plan is not required to provide for the local recording requirements of the parties to the
Agreement. Each party shall be responsible for the provision of those recording services
identified as local in nature.
Plan Approval. The parties electing to participate propose that the Plan developed by the
Logger Committee must be approved prior to implementation. They propose that the Plan
should be considered approved following unanimous approval by members (or alternates)
of the Logger Committee representing all of the parties electing to participate in the
project. Following approval by the Logger Committee the plan must be submitted to the
Board for final approval.
Plan Implementation. It is proposed that following Plan approval by the Board, the
Logger Committee may take such steps as are consistent with the Plan to ensure
implementation as provided in the Plan.
Plan Administrative Agent. The requesting parties propose that the Administrative
Agent appointed by the Board should serve as the administrative agent for the Project and
manage and supervise the financial aspects of the project. The administrative agent
should be required to prepare and distribute such reports and updates as the Logger
Committee and Board may require and are consistent with the provisions of the
Agreement. The administrative agent should ensure adequate audits of all funds and
transactions in compliance with the requirements of statute. The parties electing to
participate in the project agree that they should be assessed for all usual and customary
expenses associated with the performance of this service in the annual budget of the
Board.
Plan Modifications. The requesting parties propose that the Logger Committee should
modify and update the Plan as required on a schedule determined by the Logger
Committee and approved by the Board. All modifications to the Plan should require
consensus approval with no more than 2 descending dissenting votes of the Logger
Committee members representing all of the parties electing to participate in the project.
All modifications to the Plan approved by the Logger Committee must be submitted for
final approval and authorization by the Board.
1. Installation Timeline
The Plan should include a detailed timeline for the completion of Plan implementation.
See Appendix 1- Statement of Work
-4-

15

2. Party Agreement
The Plan should provide a timeline for integrating the parties to this Agreement into the
shared recording and logging system consistent with their individual needs and
requirements for those services. Participation levels are Full Member (the 20 ESB
members) or Limited Member (NGOs or other, subject to, but not limited to backup
resources and being able to pull recovered files). No membership changes will be made
within the first year of deployment;
3. Additional Equipment
The Plan should identify and specify the additional equipment and services required to
complete the shared recording and logging system;
4. Network Connection
The Plan shall identify the connectivity required to complete the recording network;
Firewall
Motorola has included a firewall for the interface between City of St. Cloud’s firewall to
the AIS, VPM and the Verint Logging recorder. This firewall will be set up in accordance
to the requirements set forth by the logging vendor selected by the City of St. Cloud. The
number of open ports is subject to approval by ARMER.
Point-to-Point Network Connectivity
A point-to-point connection or dedicated communication link between two systems is
required for secure upload and download of agency private data.

Formatted: Underline

Ports and Protocol
Select components require various secure ports and related protocol. See additional
documentation (Ports and Protocols Documentation) for specific requirements.

Formatted: Underline

VPN Access
SSL VPN connection on the City of St Cloud’s firewall.
Other Security Concerns
Agencies accessing the CJDN (Criminal Justice Data Communication Network) must
follow BCA security standards.
5. Required Equipment and Licensing
The Plan should identify the equipment and services required to provide connectivity to
the ARMER network backbone. Included shall be a review and summary of the required
agreements, contracts, MOU's and other instruments of agreement defining the
relationships between the parties and service providers, including other units of
government;
Integration Documentation
-5-

16

Motorola radio deployments consist of the Radio Network Infrastructure (RNI) and
optional Customer Environment Networks (CEN). All Motorola radio infrastructure
components, such as radio gateways, AIS servers, VPM servers and Consoles reside in
the RNI. CEN typically contains customer workstations and other non-radio related 3rd
party application servers such as the voice logging equipment Firewall devices are
deployed between RNI and CEN to protect the servers.
For additional integration information, see the Motorola Astro Logger Integration
Document.
Hardware
Verint Premise Logger
The Archiving interface Server (AIS) provides an interface between the radio system and
a 3rd party logging recorder. The Archiving Interface Server (AIS) provides flexible,
high-quality archiving services for audio and data associated with various types of calls
and events associated with radio resources. The AIS is a server which allows an IP-based
logging recorder to “log onto” the radio system and request IP talkgroup and IP
conventional channel metadata be directed to it for recording. Once configured by the
logging recorder, the VPM sends the audio and the AIS send any additional metadata
associated with the call to the recorder. The recorder combines the audio and metadata
for future playback.
The user can configure the IP Logging Recorder to monitor and record a set of radio
system resources (IP trunked or IP conventional). The AIS monitors the identified
resources, passes call-control information to the logging sub-system via an API, and
redirects audio for those monitored channels to the logging sub-system via the LAN. The
logging recorder then records this information to the storage media.
The AIS is comprised of a pPersonal cComputer (PC) and a Voice Processing Module
(VPM). Both the PC and the VPM have separate connections to the console site LAN
switch. The VPM communicates with the AIS PC via Ethernet. There is no direct
physical connection between the VPM and the PC.
Secure calls can be handled in one of two ways in a radio system that employs
encryption. The AIS can be configured to decrypt a secure call and pass the clear audio to
the recorder along with the call control information. Or, it can be configured to only pass
the call control information to the recorder and not pass any audio. This configuration is
under the complete control of the customer.
Primary Logging Equipment (MnDOT)
•
Resides in a secured server environment that is controlled by MnDOT and
is card and key access.
•
The equipment is protected by UPS battery backup and an emergency
generator.
•
MnDOT advised that they only lease space in these facilities to
governmental entities and access credentials are assigned to a person (employee)
of the agency.
-6-

17

•

Secondary Logging Equipment (St. Cloud Police)
•
The redundant equipment is located within our data center at our police
department that has many layers of physical security.
•
Similar with the MnDOT location, any vendors must be escorted while
on premise.
•
We do have partners that are co-located in this data center, but we require
each person with access to successfully complete a law enforcement conducted
background investigation.
This data center is also protected by UPS battery backup and an emergency
generator.

Formatted: Indent: Left: 0", Hanging: 0.5"

Software/Licenses
Talkgroup License
Any licenses above the already 320 purchased licenses will be billed at the current Verint
rate. New entities coming on the system must purchase their own license and
maintenance directly from Verint. For the need of redundancy, two licenses are required
to record 1 talkgroup.
Any surplus licenses that are owned by the Regional Logger Committee shall be offered
to an agency that is a member of the Central Minnesota Emergency Services Board
(CMESB) at the cost of the ongoing maintenance for those licenses. The Regional
Logger Committee shall retain a minimum number of licenses as identified in item #15
“Request for Recordings” in this plan for regional use. This offer is an incentive for
those CMESB agencies that have a desire to join the regional logger.
6. Archiving
The MCC 7500 AIS is used with a 3rd party logging recorder system. The interaction
between the AIS and the recorder system is based on an Application Programming
Interface (API) designed by Motorola. Motorola understands that the API has been
purchased either by the Central MN Emergency Services Board or by their logging
vendor. The recorder system uses the API to specify which talkgroups it wishes to record.
The AIS uses the API to pass call control information and vocoded audio packets
associated with radio calls to the recorder system via the LAN for storage and retrieval.
Keeping the audio in its vocoded format allows the recorder to store it in the exact form
in which it was passed through the radio system. This completely eliminates any
degradation of the audio quality due to compression techniques used by most recorder
vendors.
The following types of radio system calls are capable of being processed via the AIS:
• Trunking Talkgroup Call
• Trunking Announcement Group Call
• Trunking Emergency Call

-7-

18

The following types of trunking radio system events are capable of being processed via
the AIS.
• Emergency Alarm
• Emergency Acknowledge
• Emergency Knockdown
• Repeater On/Off
• System Access Priority Selection (Tactical/Normal)
The Central MN Emergency Services Board is responsible for working with their logging
vendor to interface to the AIS using the API to meet the Region’s logging requirements
especially as it pertains to additional information logged besides the audio.
7. Training
The Plan should identify a standard for the provision of training services for personnel
using the shared recording and logging system;
Logging Vendor will provide monthly webinar training as needed to agency members.
Training will include but is not limited to: new users, refresher training, report training
and quality assurance training.

8. System Administration
The Plan should identify minimum standards for equipment intended to access the shared
recording and logging system. There will be two levels of administration, regional and
local;
See Appendix 6 – System Admin Contacts

9. System Access Requirements
The Plan should identify the minimum-security requirements for the operation of the
shared recording and logging system. Vendors will have access to the logger remotely
through the City of St. Cloud provided VPM and physically on site if they are escorted
into the data center and during normal business hours;
10. System Maintenance & Support
The Plan should identify the projected maintenance requirements of the shared recording
and logging system. The Local System Administrator will be given as much advance
notice as possible to maintenance downtimes, but notice will be subject to the importance
of the maintenance. The preferred maintenance window will be from 10:00 AM – 12:00
PM. See Appendix 2 for more information on maintenance and support;
11. System Replacement
The Plan should address issues affecting upgrades of equipment and software for the
planned duration of the recording and logging system. The system replacement agreed
upon by the Regional Logger Committee is a seven-year life cycle;
-8-

19

12. Operational Standards
The plan should identify required equipment, service and training standards required for
local recording and logging system intended to interoperate with the shared recording and
logging system.
13. Retention
No data will be converted to the premise or regional logger. All data will need to be
retained for a period of one year. If an agency decides they want different time period
they need to submit that in writing to the region administrators. State resources will be
retained in accordance with the state retention schedule.
14. Budget
Annual
The Plan should include a cost distribution plan defining individual contributions
required for construction, implementation and maintenance of the system, including
distribution of all grant funds dedicated to the project.
Replacement and Emergency Fixes
The Plan may, at the discretion of the Logger Committee and the approval of the Board,
contain and expand the cost sharing provisions provided in the Plan. The Plan should
include recommendations for development and administration of a contingency to
provide for major repairs or other unplanned events leading to additional costs or
expenses.

15. Request for Recordings
Local resources provided at discretion of resource owner Non-regional assets are at the
owner’s discretion as to when they can be sold. See Appendix 3 for items that are considered
regional in nature as part of this plan.
Regional resources State/Regional – Request are to be made in writing the regional
administrators any cost to provide will be determined by and reimbursed to the Regional
Administrators agency.
At times, an agency may require the ability to temporarily log a resource up to 30 days
when they do not have available licensing. Resources for five talkgroups have been set
aside for this purpose. A written request may be sent to the Regional Administrators and
use of a shared pool of licenses may be used. The Regional Administrators will monitor
the usage of these requests and keep in communication with the agency to determine
when the resource logging will be discontinued.

-9-

20

AN AGREEMENT FOR A
REGIONAL EMERGENCY SERVICES BOARD
This Agreement is entered into this __28_______ day of __April____________, 2014___, by and between
the following political subdivisions of the State of Minnesota, who are the members of the board:
City of St. Cloud
Office of the Mayor
City Hall
400 Second Street South
St. Cloud, MN 56301

Benton County
County Administrator
Benton County Courthouse
PO Box 129 531 Dewey St
Foley, MN 56329

Big Stone County
County Administrator
County Courthouse
20 Second Street SE
Ortonville, MN 56278

Douglas County
County Coordinator
County Courthouse
305 8th Avenue West
Alexandria, MN 56308

Kandiyohi County
County Administrator
County Courthouse
400 SW Benson Avenue
Willmar, MN
56201

Meeker County
County Administrator
County Courthouse
325 Sibley Avenue North
Litchfield, MN 55355

Morrison County
County Administrator
Government Center
213 First Avenue SE
Little Falls, MN 56345

Sherburne County*
County Administrator
Government Center
13880 Highway 10
Elk River, MN 55330-4601

Pope County
County Coordinator
County Courthouse
130 East Minnesota Avenue
Glenwood, MN 56334

Stearns County
County Administrator
Administration Building
705 Courthouse Square
St. Cloud, MN 56303

Swift County
County Administrator
County Courthouse
301 14th Street North
Benson, MN 56215

Todd County
County Administrator
County Courthouse
221 First Avenue South
Long Prairie, MN 56347

Wright County
County Administrator
Government Center
10 Second Street NW
Buffalo, MN 55313-1188

Otter Tail County
County Administrator
Government Services Center
500 Fir Avenue West
Fergus Falls, MN 56537

Grant County
County Coordinator
10 Second Street NE
PO Box 1007
Elbow Lake, MN 56531

Traverse County
County Coordinator
County Courthouse
702 2nd Avenue North
Wheaton, MN 56296

Wadena County
County Coordinator
County Courthouse
415 South Jefferson Street
Wadena, MN 56482

Wilkin County
County Coordinator
County Courthouse
300 South 5th Street
Breckenridge, MN 56520

Stevens County
County Coordinator
County Courthouse
400 Colorado Avenue
Morris, MN 56267

Mille Lacs County
County Coordinator
County Courthouse
635 2nd Street SE
Milaca, MN 56353

NOW, THEREFORE, in consideration of the mutual promises, covenants and consideration herein
contained, the parties to this Joint Power Agreement agree as follows:
*Sherburne County provided notice in December 2017 of leaving the Central Region starting in 2019.
Logger Committee voted in May 2025 to move Sherburne County to a Limited Partner in 2026.

- 10 -

21