IWCE is part of the Informa Connect Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Conference: March 8-11, 2027
Exhibits: March 10-11, 2027
North Hall, Las Vegas Convention CenterLas Vegas, NV

2027 Agenda

How Vermont's Grid Utility Chose Its Dispatch System

Satish Angur  (Senior Radio Engineer @ VELCO, Vermont Electric Power Company, Vermont Electric Power Company)
Date: Wednesday, March 10
Time: 2:30 pm - 3:00 pm
Topic: Budget, Procurement & Strategic Planning
Format: Power Session
Vault Recording: TBD

Seven console manufacturers. Forty existing dispatch positions. One statewide radio network that could not go quiet during the change.

When VELCO, the nation's first statewide transmission-only electric utility, decided in 2024 to replace MPT 1327 analog trunking with DMR Tier III across 56 sites and more than 1,100 subscribers, the dispatch console became the most consequential purchase in the program. It was the one component that had to work with the network being retired as well as the network being built.

This session opens up VELCO's evaluation end to end: how the shortlist was built, what was asked of all seven manufacturers, and why capability matrices and reference sites were not enough to separate them. The deciding test was not a feature comparison. It was whether a vendor would develop and prove a migration path on VELCO's actual network, including writing a radio access protocol from scratch, validating it in the radio manufacturer's lab, and putting an engineer on site in Vermont for a week to find out what would break.

Something did break. A legacy inactivity timer silently killed console patching, and the fix, voice activity detection, only surfaced because the testing was real.

Anyone holding a communications modernization budget will leave with VELCO's evaluation criteria, the questions that produced honest answers from vendors, and a look at the deployment now underway: around 60 positions, a redundant core, gateways, location services, and IoT.

Takeaway

- A repeatable evaluation framework for dispatch console selection when a network migration, not steady-state operation, is the real requirement.
- The specific questions that separated seven console manufacturers once feature matrices and reference sites had been exhausted.
- Why proof-of-migration testing on the live network belongs before contract award, and what it costs to run it properly.
- How to build a console business case that carries beyond cutover into location services, IoT and long-term platform value.