Operational Excellence for Energy & Utilities in Garland, TX
Garland Power & Light is one of the few municipal utilities inside the DFW metroplex, which makes Garland operationally distinct from every other city in the North Texas region. While Dallas, Plano, Frisco, Arlington, and the rest of the metroplex run inside Oncor's wires-only TDU structure, Garland owns and operates its own vertically-integrated utility — generation, transmission participation, distribution, and customer operations all inside a city-owned structure governed by the Garland City Council. That municipal structure shapes every operational excellence conversation here. The governance model is different, the operational scorecard gets read in council sessions, the customer-owner relationship compresses the distance between operational decisions and public response, and the vertically-integrated operational scope means op-ex work has to consider generation-dispatch coordination alongside distribution and customer operations inside a single organizational structure. MSG walks into Garland with explicit recognition that a muni engagement isn't an IOU engagement wearing different branding — it's a structurally different operating reality that needs its own engagement shape.
Garland Context
Garland's population runs just under 250,000 inside city limits, in the eastern metroplex between Dallas and Rockwall. Garland Power & Light (GP&L) serves approximately 72,000 electric customers across the city and has a participant position in the Texas Municipal Power Agency (TMPA) alongside other Texas muni utilities. GP&L's generation portfolio participates through TMPA arrangements rather than standalone large-scale generation, which means the operational picture includes transmission and generation-market coordination without the full generation-fleet operations burden of a CPS Energy or Austin Energy.
The operational calendar matches the broader DFW metroplex — March-June severe weather with tornado and hail risk, summer thermal peaks, fall severe weather, winter cold-snap readiness post-Uri in February 2021. Garland-specific operational features: the city-owned utility structure produces governance dynamics distinct from IOU operations, the TMPA participant position adds generation-market coordination layered on top of distribution operations, and the eastern-metroplex geography puts Garland in a distinctive position within the Dallas operating ring.
MSG is 305 miles southeast of Garland — about four and a half hours. Garland engagements are structured with multi-day onsite blocks at operational inflection points rather than weekly same-day trips, weekly video cadence in between.
How We Deliver
Discovery for a GP&L or municipal utility engagement starts with three parallel tracks. Track one: distribution operations immersion. Morning huddles across shifts, ride-alongs with troublemen and lineman crews, full-shift dispatcher observation. Track two: operational data pull. 24 months of SAIDI/SAIFI/CAIDI by circuit, outage records cross-referenced against AMI exception volumes, crew utilization from work management (SAP PM, Maximo, or the specific muni system in use), vegetation cycle adherence. Track three: governance and reporting review. How operational metrics get presented to the city council, which metrics get public scrutiny, and where the reporting cadence is driving or distorting operational priorities.
Scope typically covers five operational domains. Control-room huddle discipline — morning and shift-change cadence, decision rights, event-class escalation, with specific adaptation for smaller-staff muni operating realities where the same supervisor might cover multiple roles. Dispatch workflow operations — OMS ticket lifecycle, AMI exception triage, mutual-assistance integration protocols, and coordination with TMPA generation-market activity where relevant. Crew scorecard design that respects municipal utility culture — metrics field supervisors own, not metrics imposed from outside. Restoration ETR accuracy ops across winter and summer event types. And vegetation management cycle ops adapted to the specific Garland operating territory.
Execution runs 6-12 months with onsite anchoring at operational inflection points: pre-severe-weather-season (February-March), summer peak readiness (May), peak-season ops check-in (August), fall severe weather (September), winter-readiness (November-December).
Energy & Utilities Angle
Municipal utility operational excellence has specific character that IOU-trained consultants often miss. The governance model is an operational variable, not just a legal structure. GP&L's operational metrics get read in council sessions. That public accountability compresses the distance between operational decisions and customer response in ways IOU management structures don't replicate.
Three dynamics matter specifically in this environment. First, public accountability on operational performance forces transparency in ways IOU utilities don't face directly. You can't bury an operational miss inside a rate case — the council member whose constituents went dark for 18 hours is asking questions about it in the next session. Operational excellence work that produces sustained scorecard improvement matters more visibly than in IOU environments, and the council and member-owner audience is a real factor in how the operational story gets told.
Second, municipal utility culture tends to reject performative consulting faster than corporate utility culture does. Operational excellence initiatives that look like 'corporate transformation' get cultural rejection quickly. Work that sticks gets framed as serving the customer-owner or the rate-paying citizen, not as optimization for its own sake. This isn't a sales framing — it's an honest description of how muni operators think about their work, and consulting engagements that don't adapt to that reality don't land.
Third, the smaller operational scale of muni utilities compared to IOUs means operational improvements have higher per-customer visibility. A SAIDI improvement from 120 minutes to 95 minutes at a 72,000-customer muni shows up in concrete customer experience in a way the same percentage improvement at a 2.8-million-customer IOU doesn't. That visibility is operational leverage — it means op-ex work produces clear, attributable customer-facing results that muni leadership can point to.
MSG's ServiceStorm background with multi-tenant software gives us pattern recognition across operator types and scales. We've seen how operational excellence work translates across different organizational structures, and we apply that pattern-matching to municipal utility engagements without trying to force an IOU playbook onto muni ops.
Why MSG
MSG is an operator-consulting firm built around field operations. We don't scope like a Big Four practice. Our engagements start small, prove value on a specific operational domain, and expand only after we've shipped results. For a muni utility that typically means starting with one operational area — specific circuits, a specific dispatch team, a specific operational metric — and doing the work that moves that number before we touch anything else.
We build production software (ServiceStorm, MFGBase, LocalAISource) and consult alongside that build practice. That operator depth shows up in engagement week one — we walk into control rooms and dispatch centers understanding workflow, ticket lifecycle, crew productivity, and field-tech culture from the engineering side, not just the consulting side.
And we scope engagements at whatever size matches the operational domain. Small-muni engagements at GP&L scale work for us the same way larger engagements work — the operational disciplines are the same, the consulting economics just fit the operational reality.
Outcome
Twelve months into a Garland-area municipal utility engagement, operational discipline has tightened visibly. SAIDI and SAIFI trends are moving in the right direction by circuit. ETR accuracy on major events is up 15-20 points. Morning ops huddles run on fixed cadence with clear decision rights. Crew scorecards reflect metrics field supervisors own and believe in. Vegetation cycle adherence is tracked weekly by circuit. Winter-readiness ops are documented and practiced, producing a walkthrough checklist that actually runs in December. For a muni engagement, the operational improvements show up in public-facing metrics the council can see, which gives utility leadership a concrete story to tell that's backed by operational reality rather than framed around consulting deliverables.
FAQ
GP&L is a city-owned utility under city council governance. How does MSG handle the political-operational layer?
By staying out of the political layer and doing the operational work. We don't engage on rate strategy, regulatory positioning, council relations, or public-communications strategy — those belong to your executive team, utility director, and communications. MSG works at the operational layer: control-room discipline, dispatch workflow, crew scorecards, restoration ops, vegetation cycle. When operational improvements produce better public-facing metrics, GP&L leadership owns the external narrative. We don't present to city councils. We work with operations leadership, produce operational change, and let the utility's leadership translate that into whatever external story fits the governance model. That separation protects the operational work from getting politicized and keeps our engagement focused on where we actually add value.
We're a smaller muni compared to CPS Energy or Austin Energy. Is MSG's approach still useful at our scale?
Especially. Smaller munis get underserved by national utility consulting firms because engagement economics don't fit — national firms need million-dollar-plus engagements to make their models work, and most 50,000-100,000-customer munis can't justify that spend for operational work. MSG is built for this middle. We scope engagements that produce real operational results at timelines and budgets that fit a GP&L-scale muni. The operational disciplines are the same as at larger munis (control-room ops, dispatch workflow, vegetation cycle, ETR accuracy); the consulting economics just finally fit. Some of our best utility engagements have been with smaller systems where operational changes we help implement directly move the SAIDI number the council is asking about. The fundamentals don't change at smaller scale.
Post-Uri winter-readiness ops in North Texas keep getting rebuilt every year. What makes MSG's approach stick?
By building readiness into the operational rhythm instead of documenting it in a binder. Most winter-readiness programs post-Uri have been document-heavy — procedures written, tabletops run once, binders filed. When December arrives the procedures get rediscovered at 3am during the first cold event and half of them don't execute cleanly because nobody's run them in 10 months. Our approach runs the readiness steps through the November-December ops cadence as a continuous rhythm: pre-cold-snap ops huddle protocol on the 5-day forecast cycle, substation winterization walkthrough with field-supervisor ownership, customer-communication template pre-drafting, clear decision rights on any ERCOT-directed load shed. We observe the first cold event of the season in real time and tune protocols based on actual execution. That's the version that holds from one winter to the next rather than needing rebuild.
Our TMPA participant position adds coordination work we sometimes struggle with. Can MSG help with that?
Partly. TMPA coordination specifics involve generation-market participation that isn't MSG's core scope — we don't engage on generation-market strategy or bidding discipline, which belong to your TMPA coordination and regulatory leadership. Where we do add value is the operational interface between distribution operations and TMPA-related activity: how dispatch coordination handles planned and unplanned generation-related events, how the operational rhythm accommodates TMPA-driven operational activity, how event-class response coordinates across the participant relationship. That operational-interface work is within our engagement scope. The market and strategic layer of TMPA participation isn't.
Can MSG work with our existing OMS and work management without forcing a platform conversation?
Yes — we specifically avoid platform-replacement conversations in op-ex engagements. If your current OMS, work management (SAP PM, Maximo, or the specific muni system in use), GIS, or CIS has genuine architectural problems, that's capital planning for IT and utility leadership, not op-ex. Our engagement works at the procedural and workflow layer on top of whatever tooling you have. We'll identify tooling-driven operational friction and document it for IT's roadmap, but we won't try to sell you a replacement program. What looks like 'the OMS is broken' often turns out to be 'the OMS is configured suboptimally and procedures around it are undisciplined' — fixable without capital spend. We'd rather find that diagnosis than automatically recommend replacement.
How often will MSG actually be in Garland?
For a 6-month engagement: 3-4 day kickoff immersion plus 4-6 onsite visits at operational inflection points. For a 12-month engagement: 8-12 visits building year-round onsite cadence. Weekly video cadence in between. The 305-mile drive from Beaumont puts Garland at four and a half hours — we structure onsite as multi-day blocks rather than weekly same-day trips. For event-class responses during the engagement period we coordinate additional onsite presence as operational reality requires.
Other Industries in Garland
Ops in Other Cities
Other MSG Services
Tightening municipal utility operations in Garland?
Let's sit in on a GP&L ops huddle and start the work in the control room where the council-facing numbers actually move.