Technology Integration for Energy & Utilities in Garland, TX
Garland Power & Light is one of the few municipal electric utilities inside the DFW metroplex, which makes its integration environment distinct from the Oncor-TDU model that surrounds it. As a city-owned utility, GP&L owns generation (or generation entitlements through TMPA — Texas Municipal Power Agency), transmission participation, distribution, and customer service as a vertically integrated operation — a different stack shape than an Oncor-served REP relationship. The customer base runs across the City of Garland plus a small adjacent footprint, with residential, commercial, and industrial load typical of a mature DFW city. The ERCOT market context applies at the wholesale level, but the retail side runs on the municipal model: GP&L is the billing and customer-service relationship, not a REP. Integration for a Garland-sized municipal sits at an interesting scale — big enough to carry most of the integration complexity of any utility, small enough that every integration decision is felt across the whole operation. MSG builds integrations that fit that scale honestly, without importing Big Four assumptions that only work at IOU scale.
What makes Garland different for energy & utilities?
Garland is ~246,000 people in the northeast corner of the DFW metroplex, sharing borders with Dallas, Richardson, Mesquite, Sachse, and Rowlett. GP&L serves the electric utility for the City of Garland plus Heath and a small adjacent footprint — approximately 72,000 customers on the electric side. The utility is a department of the City of Garland, with governance running through the City Council and a Utility Advisory Board providing input. GP&L participates in TMPA (Texas Municipal Power Agency) for generation and transmission, which adds an inter-agency integration context.
As a vertically integrated municipal, GP&L carries the full customer lifecycle — from move-in through billing, collections, disconnects, service requests — inside the utility, rather than splitting between TDU and REP the way Oncor-served cities do. That changes the CIS integration reality: the system has to support full customer lifecycle, not just TDU-side interactions. Customer portal, payment integration, customer service workflow, and billing are all in scope for the utility's integration architecture. The OMS integration with customer-facing channels is closer to the customer experience because GP&L owns that relationship.
TMPA participation shapes the generation and transmission integration layer. TMPA members share generation assets (Gibbons Creek historically, with fleet transition in progress) and coordinate wholesale market participation. That inter-agency structure creates integration requirements that a standalone generator doesn't have — settlement allocation, dispatch coordination, and shared reporting all flow through systems that span member utilities. The DFW-area municipal utility cluster (Garland, Denton, Greenville, Bryan) provides peer context for how these integration challenges get addressed.
ERCOT applies at the wholesale level. GP&L participates in the ERCOT market through TMPA's integration, with the real-time telemetry, settlement, and reliability reporting that implies. MSG is 308 miles east of Garland on I-20/I-10 — about five hours. For Garland engagements we structure around multi-day onsite immersions with weekly video cadence between.
How does the engagement actually run?
A GP&L-scale integration engagement starts with an audit that respects the municipal vertical-integration model. We map the CIS (a small-to-mid-scale municipal CIS, often a different vendor than the Oracle/SAP patterns typical at IOUs), the OMS, AMI (GP&L's AMI footprint), GIS and asset management, customer portal and payment integration, TMPA-facing integration, and the middleware. We read the actual data flows for a customer move-in, an outage event, a disconnect workflow, and the TMPA-facing operational and financial reconciliation.
From the audit we produce architecture recommendations scaled to a municipal utility of Garland's size. This is important — architectural patterns that work for an IOU at multi-million-customer scale don't always fit cleanly at 72,000 customers, and architecture that treats GP&L as a smaller IOU produces over-engineered solutions that break the operational budget. We design for the actual scale, using right-sized patterns that can be maintained by GP&L's integration team without vendor dependency. Implementation runs on existing integration platforms, with selective pattern changes where they're warranted.
For GP&L-scale engagements we typically scope in phases: foundational audit and architecture (6-10 weeks), first high-priority integration build (10-16 weeks), broader roadmap rollout over 9-12 months. Every engagement scopes to end with your team running the platform. Municipal-scale work particularly demands honest scoping — there's no room for consultant dependency.
Why is energy & utilities strategy unique?
Municipal utility integration has a structural character that gets systematically missed by consulting firms optimized for IOU scale. The full-lifecycle customer relationship means integration has to support customer service workflows, bill presentment, payment processing, and collections — not just the TDU-side operations. The integration between the CIS and the customer-facing channels (portal, IVR, field service, customer service center) is often where the customer experience is made or broken at a municipal. Payment integration specifically is a workstream that IOU-scale frameworks underweight: municipal customers pay through local payment networks, city-facility walk-ins, automated phone systems, online portal, and sometimes direct city billing integration. Every one of those channels needs clean integration with the CIS.
TMPA-style inter-agency integration is a specific muscle. Shared generation, shared transmission participation, shared wholesale market position — all require settlement, dispatch, and reporting integration that spans organizational boundaries. This integration has governance implications: changes to shared systems affect multiple member utilities, so the change process isn't just internal. Good integration work respects this and designs for shared-governance change management.
Municipal-scale AMI and OMS integration has its own rhythm. At 72,000 customers the data volumes are manageable, but the per-customer value of AMI-driven integration (outage intelligence, billing accuracy, customer-facing usage data) is as high or higher than at IOU scale because every customer is a specific relationship the utility owns end-to-end. AMI ROI at municipal scale comes from using the data well, not just collecting it, and that's an integration layer challenge.
Why pick MSG?
MSG builds and runs production software every day. ServiceStorm serves home services operators across the Gulf Coast — municipal-scale operations in many cases, with the operational reality that implies. MFGBase connects manufacturers globally. LocalAISource is a live production directory. The engineering discipline required to operate these products at real scale shows up in how we engage with a municipal utility: we understand that right-sizing matters, that over-engineering is as costly as under-engineering, and that a maintainable system is better than an impressive one.
Our engagement model respects the municipal reality. We scope honestly, deliver against measurable outcomes, and scope to end at a system your team runs without us. We don't try to turn integration work into a multi-year retainer. We respect the City Council and Utility Advisory Board governance cadence and design deliverables with public accountability in mind. We work with your existing integration platform rather than arriving with a product to sell.
Beaumont to Garland is five hours on I-20/I-10. For Garland engagements we structure around multi-day onsite immersions, weekly video cadence between, and onsite presence through major cutovers. Municipal utility work rewards engineers who show up, and we deliver that rather than pretending occasional video calls substitute.
What does 12 months look like?
Twelve months in, a GP&L integration engagement produces a layer that handles full-lifecycle customer workflows cleanly, supports TMPA-coordination, delivers AMI and OMS integration value at municipal scale, and produces Council-ready reporting directly from operational systems. The integration platform is maintainable by the utility's own integration team without vendor dependency. Customer-facing channels (portal, payment, IVR, customer service) run off coherent integration rather than point-to-point patches. Your team owns the platform.
More Questions
As a municipal with vertical-integration, our CIS integration surface is bigger than a TDU-only utility. How does MSG approach full-lifecycle integration?
By treating the full customer lifecycle as the scope — from move-in through billing, collections, customer service, disconnect, and re-connect — rather than limiting integration work to TDU-side workflows. We'd map every customer-facing channel (portal, IVR, payment, customer service, field service) and identify where integration between the CIS and each channel is producing manual work or customer experience gaps. From there we build integration patterns that make each channel a first-class interface to the CIS rather than a screen-scraping workaround. Payment integration specifically gets careful attention at a municipal — the payment channels matter, and clean integration with payment processors, city walk-in systems, and automated phone payment is often where customer satisfaction is gained or lost. The investment produces measurable improvements in customer satisfaction and in customer service center efficiency. A municipal's customer relationship is more direct and more personal than an IOU's — people talk to the utility the way they talk to the city, and the integration layer has to support that relationship quality rather than fighting it.
TMPA coordination creates inter-agency integration requirements. How do you handle that?
Collaboratively and with respect for the shared governance model. TMPA integration touches settlement allocation, dispatch coordination, and shared reporting across member utilities. Changes to shared integration affect multiple members, so the change process isn't purely internal to GP&L. We engage TMPA coordination structures directly where scope requires, document interface contracts explicitly, and design integration work that respects the shared governance cadence. Some integration work is purely GP&L-side — reconciliation, internal reporting, customer-facing allocation of TMPA-sourced generation — and we scope that clearly as GP&L-internal work. Some requires TMPA coordination, and we plan for that cadence rather than pretending it can be rushed. The governance pattern actually parallels how IOU enterprise architecture works across operating companies, and similar discipline applies. The muscle memory we've built in that environment transfers directly — inter-agency coordination is inter-agency coordination whether the entities are Entergy operating companies or TMPA members.
Is MSG appropriately scaled for a 72,000-customer utility, or are you oriented toward larger engagements?
Appropriately scaled, and municipal work is something we specifically value. MSG is a focused engineering firm rather than a large consulting firm — we staff engagements with the engineers who actually do the work, not with layered project management structures that only make economic sense at IOU-scale fees. For a GP&L engagement, we'd scope with the real operational budget in mind, using right-sized patterns that produce actual ROI at 72,000-customer volume. Over-engineering is a real risk at municipal scale, and we design against it explicitly. The engagement economics work because we run lean and deliver specific outcomes rather than open-ended advisory relationships. Municipal utilities consistently get better engineering attention from focused firms than from Big Four consulting, and we lean into that reality. When a municipal hires a Big Four firm, they typically get the B team and a lot of junior analysts billing partner rates. We send the senior engineers who actually write the code. That's the whole pitch.
Our AMI footprint is mature but we're not getting the operational value we expected. Where does integration typically move the needle?
AMI ROI at municipal scale comes from using the data operationally rather than just collecting it. Common integration gaps: AMI last-gasp data not flowing into OMS with low enough latency to support real-time outage intelligence, interval data not flowing to CIS and customer portal in a form customers can actually use, billing exception handling eating the accuracy gains AMI should have produced, and field service integration not reducing manual meter service calls. We'd audit the actual AMI data flow end-to-end and identify the specific places where the data value is being lost between the headend and the operational systems that could use it. From there we design integration improvements that turn AMI data into actual operational and customer-facing value. Most municipals with mature AMI see measurable improvement from a focused 3-6 month integration engagement targeted specifically at AMI data utilization. The investment paid for AMI deployment itself is only realized when the data flows operationally, and the integration layer is where that realization happens or doesn't.
City Council and Utility Advisory Board governance. How does that shape engagement structure?
As a first-class design constraint. Municipal engagements require documentation and reporting that stands up to public accountability — Council meetings, Advisory Board reviews, ratepayer input. We produce written status reports at a cadence matching Council and Board review cycles. Every major architectural decision has a written rationale. Scope changes have formal change orders with business justification. We design integration deliverables with public-facing outputs in mind: reliability metrics, rate case data, customer satisfaction reporting all flow from operational systems through clean integration into publishable form. We respect the public accountability model rather than working around it. We've seen Big Four engagements at municipals go sideways specifically because the consulting firm treated public accountability as an annoyance. It's a first-class constraint, and engagements that respect it consistently produce deliverables that survive both the political cycle and the inevitable staff turnover on the utility side. Clear written records at engagement cadence also protect both the utility and the consultant when staff changes or Council membership shifts mid-project.
What's the onsite cadence for a Garland engagement?
Five hours from Beaumont on I-20/I-10. For active implementation phases we're onsite weekly minimum, typically multi-day (three to four day onsite weeks). For steady-state work we're weekly or bi-weekly. We commit to onsite presence through major cutover windows and through key governance milestones (Council presentations, Board reviews) where our presence is useful. For a 12-month municipal engagement we typically deliver 35-50 onsite days. We document the cadence upfront. Municipal-scale work specifically benefits from real presence because the team sizes are smaller and collaborative problem-solving depends on knowing the people, not just video-calling them. On a 12-person integration team, you can't hide behind org-chart abstraction — the work is person-to-person, and trust built in person outperforms trust attempted over video every time. We plan for it, and we keep presence cadence consistent across the engagement rather than front-loading it and disappearing later.
Other Industries in Garland
Tech Integration in Other Cities
Other MSG Services
Ready to right-size your Garland Power & Light integration layer?
Let's audit the full-lifecycle customer workflows, the TMPA coordination, and the AMI utilization — then build municipal-scale integration that works.