In May, Salt Lake City Department of Public Utilities procured five connected products in a single decision. Four are Harris ecosystem products. The fifth is Paymentus, which leads the utility payments market.
Most utilities run three to five disconnected vendors across billing, meter data, customer self-service, field operations, and payments. SLC didn’t. They got platform-level integration without giving up depth in any of those modules, and they did it through one primary vendor relationship plus a single outside partner for payments.
Here’s how that worked, and why it matters for any utility evaluating the same procurement.
What utilities actually want from a multi-system procurement
Most utility IT directors want two things from a multi-system procurement that don’t usually go together.
First, they want a platform: one primary vendor relationship, integration that comes built in, and a stack their team can run without juggling partnership agreements that may not survive the next renewal cycle.
Second, they want real depth in every module: the CIS that’s been through hundreds of rate cases, the MDM that’s already ingested every meter type they’re likely to deploy, the payments processor whose uptime defines whether Friday afternoons are quiet or chaotic.
Those two goals collide more often than not. Most of the time, IT directors have had to pick one.
Why most CIS vendors force that tradeoff
Three patterns dominate the utility software market, and each one forces a version of the tradeoff.
The unified-suite play
One vendor sells everything in one bundle. Integration is real because every module is theirs.
Tradeoff
Every module is as deep as a single vendor can keep them, and never as deep as a competitor whose only job is that one module.
The best-of-breed strategy
You pick the deepest product in each category and absorb the integration work into your IT team.
Tradeoff
Depth lives in the products; integration burden lives in your shop. Any vendor can change ownership, roadmap, or pricing in ways that ripple through the stack.
The roll-up consolidator
A holding company owns a collection of products that looks like a platform from the outside. Underneath, the products are managed for cash extraction, not reinvestment.
Tradeoff
One throat to choke, and slow under-investment across everything in the bundle.
Each pattern has been around long enough that utility IT directors recognize them by feel.
What the Harris ecosystem actually is
The Harris portfolio is structured differently.
Harris Computer sits inside Constellation Software, a publicly-traded Canadian company that owns more than 600 vertical-market software businesses. Constellation’s founder Mark Leonard has been explicit in his shareholder letters: Constellation acquires vertical software businesses and holds them indefinitely. No restructuring for resale. No forced synergies. The acquired businesses keep their own products, teams, and customer bases.
That’s what separates an ecosystem from a unified suite.
enQuesta runs as its own product, with its own team and its own customer base built over 50 years of utility billing work. SmartWorks Compass is a focused MDM product. Capricorn, owned by Silverblaze, is a focused self-service portal. enQuestaLink handles field service and work orders. Each BU has its own product roadmap and serves its own customers. None of them is a module of a bigger platform.
What the BUs share is an operating model and an integration discipline. Native integration paths between products are built by teams who sit in the same operating group and share institutional backing. The result is integration that’s done by the people who own the underlying products, not bolted on afterward by a separate middleware layer.
Because Constellation is a perpetual owner, none of the products is on an exit clock. No investor is pushing for a sale. No future acquirer will consolidate the portfolio and sunset whatever doesn’t fit a new strategy.
That’s the ecosystem effect. One accountable parent. Focused products with their own depth. Integrations that exist because the product teams build them, not because middleware was written to fake them for a demo.
What it looks like in Salt Lake City’s deployment
Salt Lake City Department of Public Utilities serves water, wastewater, stormwater, and waste and recycling customers. Their procurement covered the full set of systems their team runs day to day.
Four products come from the Harris ecosystem. SmartWorks Compass integrates with enQuesta because both are developed under the same operating model; Capricorn and enQuestaLink connect with the same discipline. Paymentus, the fifth, is an outside partner because the Harris ecosystem doesn’t try to replace vendors who do their category better than we would.
Five products. One procurement. The procurement committee got platform-level integration without giving up product depth.
“Salt Lake City serves a growing population with aging infrastructure and rising customer expectations. We needed a platform that could handle the complexity of our operations today while giving us room to grow. The Harris ecosystem gave us that in one procurement.”
Lisa Tarufelli
Finance Administrator, Salt Lake City Department of Public Utilities
She picked up the “Harris ecosystem” framing on her own. That’s the external validation procurement committees pay attention to.
Why this matters for the next utility making this call
The software has changed continuously over those years; the discipline behind how we invest in it hasn’t. The ecosystem around enQuesta operates the same way.
We’ve spent decades learning how utility billing breaks so yours doesn’t. That’s why our implementations don’t make headlines. And it’s why, when a utility wants platform-level integration without giving up depth, the Harris ecosystem is what most of the market can’t match.
The Proven CIS Partner for Modern Utilities.