Technology Integration for Energy & Utilities in San Antonio, TX
CPS Energy is the largest municipally owned electric and gas utility in the United States, and the integration challenges that come with that scale are unusual. A San Antonio municipal utility doesn't have the competitive-retail complexity of a Houston TDU, but it carries the full vertical integration stack — generation, transmission, distribution, customer billing, gas distribution — under one governance umbrella, plus the political and regulatory layer of a city-owned enterprise answering to a board of trustees, City Council, and a ratepayer base that includes everyone from the military installations to the downtown hospitality district. Technology integration in that environment means carrying more data surface area than most IOUs, with fewer of the competitive-market integration headaches but more of the public-accountability ones. The systems are familiar — ADMS, OMS, AMI, CIS, GIS — but the workflows layered on them are shaped by the municipal operating model, the generation fleet transition from coal toward solar and storage, and the demands of serving Joint Base San Antonio and a fast-growing metro. MSG builds integrations for that reality.
San Antonio Context — energy & utilities in this market+
San Antonio is 1.5 million people inside the city limits and 2.6 million across the metro, with CPS Energy serving approximately 915,000 electric customers and 360,000 natural gas customers across Bexar County and portions of seven surrounding counties. CPS is vertically integrated — it owns generation (natural gas, nuclear stake in STP, solar, wind, and the coal fleet that's in managed transition), transmission, distribution, and customer service. That vertical integration changes the shape of the technology stack versus a Texas TDU: the CIS doesn't have to talk to ERCOT's CRR and settlement flows in the same way, but it does have to support a full customer lifecycle from move-in through final billing, including the municipal-specific workflows around LIHEAP, senior and disability programs, and city-council-directed rate initiatives.
ERCOT is still the market operator — CPS participates in the wholesale market, and generation and transmission operations have to integrate with ERCOT telemetry, settlement, and reliability reporting. But from the customer and distribution side, CPS runs like an integrated utility. The generation transition is significant. The board approved a Flexible Path strategy that retires the coal fleet on a defined timeline, accelerates solar and storage investment, and reshapes the dispatch profile — all of which creates integration requirements between the EMS, the generation management stack, the DERMS as customer-side resources grow, and the resource adequacy reporting that ERCOT demands.
Joint Base San Antonio is a distinct operating reality. JBSA has its own internal distribution, but it's a large interconnected customer with specific reliability, security, and resilience requirements that flow into CPS's integration work. The military energy program and the growing role of on-base microgrids create integration touchpoints that don't exist in civilian-only utility markets. MSG is 244 miles east of downtown San Antonio on I-10 — roughly three and a half hours. For San Antonio engagements, we structure around concentrated onsite immersions with weekly video cadence between, and we're onsite through any major integration cutover or storm-season operational phase.
How We Deliver+
A CPS-scale integration engagement starts with an audit that respects the municipal operating model. We map the systems end-to-end: the Banner or CC&B customer system, the OMS, the AMI headend (CPS runs a large Landis+Gyr and Itron footprint), the EcoStruxure or equivalent ADMS, the GIS (Esri, with Utility Network increasingly in scope), the asset management stack, the gas distribution SCADA and asset systems, the EMS for generation and transmission, and the middleware stitching them together. We read the actual integration code — not the architecture slides — and interview the teams who operate the integration layer through thunderstorm season, winter events, and the day-to-day load of a million-plus-meter utility.
From there we build an integration architecture that's explicit about what crosses the IT-OT boundary, how NERC CIP applies to the bulk electric system components, how TSA natural gas cybersecurity requirements apply to the gas distribution stack, and how the municipal governance layer consumes reliability and financial data. Implementation runs against your existing platform — whether that's MuleSoft, Informatica, a Kafka backbone, or a mix — and we keep what works while replacing only the patterns that are causing failures. For CPS-scale engagements we typically scope in phases: foundational audit and architecture (8-12 weeks), first high-value integration build (12-20 weeks), broader roadmap execution (12-18 months).
Energy & Utilities Angle+
Municipal utility technology integration has characteristics that the big consulting firms systematically miss. The governance cadence is different. A CPS-scale municipal answers to a board of trustees with public meetings, a City Council with elected priorities, and a ratepayer advisory process that gives the public direct input into strategic technology decisions. Integration projects have to show their work in ways that IOU projects don't — reliability metrics have to be auditable by people who aren't utility engineers, rate case data has to flow cleanly from operations into regulatory filings, and public dashboard commitments have to be backed by real-time data pipelines that actually work.
The vertically integrated model concentrates risk and concentrates opportunity. Because CPS owns generation, transmission, distribution, and the customer relationship, a well-designed integration layer can carry value across the full chain in ways that a disaggregated Texas TDU can't. Load forecasting that uses real customer-side data, DER programs that integrate generation planning with customer enrollment, rate design that reflects actual cost-to-serve by segment — all of these are integration-layer capabilities that only work when the systems talk to each other cleanly. Most municipal utilities we've worked with have untapped value in this direction because the integration layer has been built reactively rather than strategically.
The generation transition is a live integration driver. As the coal fleet retires and solar-plus-storage scales up, the EMS-to-ADMS-to-DERMS chain has to handle a different dispatch profile, different contingency scenarios, and different data volumes than it did five years ago. Storage is particularly integration-hungry — state-of-charge data, dispatch signals, settlement data, and customer-side program data all have to flow through systems that were designed in a thermal-generation era.
Why MSG+
MSG is an operator-engineering firm, not a Big Four consultancy that renamed its digital practice. We built ServiceStorm, a multi-tenant SaaS serving Gulf Coast home services operators, with the full integration surface that implies. We built MFGBase for B2B manufacturer connectivity. We built LocalAISource as a production directory. Each of those systems has live integration work that has to run reliably at real scale — we understand integration at the operational level because we operate integrated systems ourselves.
That operator depth changes how we engage with a municipal utility. We don't deliver a strategy deck and disappear. We write the code that moves data between systems. We sit in the NOC during storm events. We build observability that gives your integration team real visibility. We scope every engagement to end with your team running the system without us — not to lock in a retainer.
The Gulf Coast geography helps. Beaumont to San Antonio is a single day's travel on I-10, and we structure San Antonio engagements around multi-day onsite immersions rather than two-hour video calls. When CPS's integration team needs a working session with whiteboards and actual code on the screen, we can be there.
12-Month Outcome+
Twelve months in, a CPS-scale utility has an integration layer that holds through storm events, supports board and council reporting without nightly heroics, and gives the generation-transition planning teams real data to work with. Customer events flow cleanly from the AMI through OMS to CIS and onward to the customer portal. DER and solar program enrollment is integrated across CIS, DERMS, and AMI. Reliability metrics are auditable end-to-end. The integration team can extend the platform without vendor dependence.
FAQ
We're a municipal utility with a board and City Council oversight. How does that change how MSG structures an integration engagement?+
Materially. Municipal engagements require different stakeholder management, different documentation, and different pacing than IOU engagements. We structure scope, budget, and milestones so that board and council reporting is clean — no surprises in public meetings because the project charter, the spend cadence, and the measurable outcomes are documented upfront. We design integration work with public-facing deliverables in mind: if reliability metrics are being committed to in public, the integration pipeline that produces those metrics has to be auditable. We respect the governance timeline — board meetings are not negotiable, and rate case filings have hard dates. Our project management assumes municipal cadence from the start rather than importing an IOU timeline that doesn't fit. We've worked in enough public-accountability environments to know the difference, and most Big Four firms learn this the hard way the first time a board member asks a pointed question they weren't prepared for.
CPS is transitioning the coal fleet and scaling solar and storage. How does that affect integration work on the EMS-ADMS side?+
Substantially. The generation transition changes the shape of dispatch, contingency analysis, and resource adequacy modeling, which pushes through the EMS into the ADMS and into the DERMS as customer-side resources become more significant. Storage resources especially need integration across EMS (for wholesale dispatch), ADMS (for distribution-level coordination), DERMS (for customer-side programs), and the settlement and accounting stack. We work this as a dedicated integration workstream: map the current data flows, identify the specific gaps the transition is creating, design pattern changes that scale with the transition plan, and implement in phases that align with the generation retirement and commissioning schedule. We also coordinate with your ERCOT-facing integration work because the transition affects wholesale market participation and the data flows that support it. Generation transition integration done well positions the utility for a decade of evolving resource mix; done poorly, it creates fragility that compounds with each new resource added to the portfolio. We scope it as durable architecture investment, not a point-in-time project tied to a single retirement date.
Our CIS is older and the vendor has been shipping a modernization path we haven't committed to. Should we modernize first, or integrate around what we have?+
It depends on specifics we'd need to audit. CIS modernization projects are multi-year, multi-million-dollar programs that touch every customer-facing workflow — they're not a good prerequisite for otherwise valuable integration work. Usually we can build integration improvements around the current CIS that deliver 70-80% of the customer experience and reliability reporting value, with explicit architectural choices that don't paint you into a corner when CIS modernization happens later. The integration layer becomes the abstraction that survives the CIS swap. Occasionally the current CIS is so integration-hostile that it's a blocker — no usable APIs, no event capabilities, schema that breaks on any significant change. In that case we'd be honest about the constraint and scope integration work to what's actually achievable. But we'd never recommend pausing all integration work for 3-4 years waiting on a CIS modernization that may slip further.
How do you coordinate with our existing systems integrator or prime contractor on a large program?+
Directly and in writing. Many CPS-scale utilities have an incumbent SI or prime on major programs — Accenture, Deloitte, or a specialist firm running an ADMS or CIS implementation. Our role is usually to handle a specific integration workstream that the prime isn't staffed or focused on, or to audit and rebuild the integration layer the prime delivered that isn't performing in production. We coordinate with the prime, document interface contracts explicitly, and keep the scope boundaries clean. We don't get into consulting-firm territorial disputes — our goal is to ship working integration, and we'll work inside whatever governance structure the utility already has. If the prime is doing great work and our scope ends at their interface, we respect that. If the prime has delivered something that isn't working and our scope is to fix it, we'll document what we found and what we did in a way that doesn't blow up the relationship but also doesn't hide the truth from the utility.
What about the gas distribution side? We have gas CIS, gas SCADA, and gas asset management systems that don't always play well with the electric stack.+
Gas integration is a distinct workstream with its own regulatory overlay — TSA pipeline cybersecurity requirements, PHMSA reporting, and a different data model than the electric side. For a combined electric and gas utility like CPS, the integration strategy has to treat the two stacks as related but not merged. Customer-facing systems (CIS, billing, customer portal) should present a unified view where the customer has both services, which is an integration problem. Operations systems stay separate because the operational realities are separate — gas distribution doesn't have an OMS in the electric sense, it has a gas control center with different workflows. Asset management often benefits from a common platform across electric and gas, with the integration layer handling the different inspection, maintenance, and compliance workflows. We map this explicitly and design integrations that respect the separation where it matters and unify where the business value is real. Combined electric-and-gas utilities often leave customer experience value on the table because the integration layer treats the two services as if they were unrelated. Clean integration recovers that value without over-merging operations that have good reasons to stay separate.
We have Joint Base San Antonio as a significant customer with unique reliability and security requirements. Does that affect integration design?+
Yes, and it's a good stress test for the broader integration architecture. JBSA has specific reliability commitments, security protocols, and increasingly microgrid and DER capabilities that require careful integration on the CPS side. The CIS has to handle the customer relationship with appropriate classification and access controls. The OMS and ADMS have to support JBSA-specific reliability reporting and may eventually need to coordinate with JBSA's internal distribution during islanding events. The security posture for anything JBSA-adjacent has to be elevated — separate logical segmentation, tighter access controls, and specific audit requirements. We design for this explicitly. The patterns that work for JBSA often become the template for other large critical-infrastructure customers (hospitals, water treatment, data centers) because the requirements generalize well. JBSA-aware integration design is a differentiator, and most utilities treat it as a one-off rather than a repeatable pattern. Treating critical-infrastructure customer integration as a template rather than a series of bespoke projects turns the biggest customers from operational headaches into showcases for what the utility can deliver.
Other Industries in San Antonio
Tech Integration in Other Cities
Other MSG Services
Ready to integrate your San Antonio utility stack cleanly?
Let's audit CPS-scale systems, respect the municipal governance model, and build integration that earns the board's confidence.