AI Implementation for Energy & Utilities in Plano, TX

The utility load story in Plano is a corporate-campus story. Toyota North America at Legacy West, JPMorgan Chase's largest campus outside New York, Liberty Mutual, Frito-Lay, and a dense ring of enterprise tenants each running 24/7 data operations, thousands of HVAC tons, and EV-fleet charging that didn't exist on the 2015 feeder plan. Oncor's Plano distribution territory has absorbed that growth inside a decade, and the feeder reconfigurations, transformer loading profiles, and coincident-peak behavior of this service area look nothing like a standard North Texas suburb anymore. AI implementation here has to respect that operational reality first. Not a dashboard. Not a procurement-side analytics toy. Production AI that reads from Oncor's ADMS, AMI MDMS, and GIS Utility Network in a way that tightens DMS-level switching decisions, sharpens outage triage when a Legacy West tenant loses two feeders, and gets ETR accuracy inside the SLA expectations that corporate campus facilities teams will accept. Add in ERCOT real-time price volatility — Plano's largest commercial accounts run demand-response programs that need load-forecast accuracy inside 4CP windows — and you have a grid-edge AI problem that rewards specificity and punishes generic frameworks. MSG scopes one production-grade system at a time, ships in 12 weeks, integrates with the actual utility stack Oncor operates against, and refuses to leave with data in a vendor vector store your IT team can't audit. The goal is a system running at month 18 without us on retainer, documented against PUCT filings and NERC CIP auditability from commit one.

01 · Local

Plano Reality

Oncor Electric Delivery serves Plano as part of its 13-million-meter North Texas footprint — the largest T&D utility in Texas by meter count, owned by Sempra and Texas PUF investors, regulated by the Public Utility Commission of Texas, operating inside ERCOT. The Plano service territory carries a customer-mix distortion that matters for any AI work: a heavy concentration of Class 4 and 5 commercial accounts relative to residential, which drives load factors, demand-response participation rates, and outage-response SLA expectations closer to what you'd see in a downtown core than a typical suburb.

Legacy West alone changed the feeder topology conversation. The campus buildout pulled feeders into a network configuration more typical of dense urban load, and the ongoing Toyota, FedEx Office, Liberty Mutual expansions keep pushing transformer loading into near-capacity regimes that AI-assisted load forecasting and transformer health analytics can genuinely improve. North Texas data center load growth — the larger regional story driven by hyperscale buildout west of DFW — doesn't hit Plano directly the way it hits Irving or Richardson, but it raises the stakes on every capacity planning decision Oncor makes inside the region.

Weather exposure is the other operational variable that shapes AI scoping. Uri-scale freeze events are now a permanent part of ERCOT planning reality, and Plano's 2021 experience with load-shed rotations under the EEA-3 order is institutional memory for every corporate-campus facilities lead in the city. May-September convective season drives the SAIDI/SAIFI numbers that matter in PUCT reporting. AI systems that don't load-test against Uri-class cold snaps and Derecho-class storm cells don't survive a North Texas production cycle.

MSG is 289 miles southeast of Plano on I-45 and US-75 — roughly a four-and-a-half-hour drive. That's a multi-day-visit commitment rather than a day-trip, which we scope into engagement structure: 3-4 day kickoff immersion, onsite cadence pegged to integration milestones, and pre-summer-peak onsite readiness review in late May.

02 · Approach

How We Deliver

Against Oncor's operational stack, the highest-leverage first AI systems for a Plano-focused engagement cluster around three patterns. First, OMS triage tuned for the coincidence of Legacy West campus outage calls — a single tenant losing power generates 400+ parallel customer-service contacts within the first 15 minutes, and the triage system needs to collapse those into a correct feeder-level incident without dropping a legitimate second incident on a different feeder. Second, AMI analytics that actually leave MDMS — Oncor's Itron/Landis+Gyr deployment produces meter-level voltage, outage-flag, and interval-load data that in most utilities still lives in a Meter Data Management System read by a billing analyst once a month. We build retrieval and inference layers that pull that data into operational signal: transformer-loading anomaly detection, non-technical loss pattern identification at the commercial meter level, voltage excursion alerts at the service drop. Third, demand-response and 4CP forecast accuracy improvement for the commercial programs Oncor and the competitive retail providers operate against — Plano's Class 4/5 participation in those programs is heavy, and the economic value of tightening coincident-peak forecasts inside a 30-minute window is measurable.

Integration work is non-negotiable. Oncor operates an industry-standard ADMS stack with GE/Schneider patterns, Esri ArcGIS Utility Network for GIS, Oracle CC&B on the CIS side, and a mature AMI headend. Every AI system we build reads through governed data contracts — AF extracts, ODS pulls, API layers IT owns — never directly into BES Cyber Assets or control-plane systems. Retrieval and inference run inside your VPC and CIP perimeter where data classification requires it. Evaluation harnesses use Oncor's real historical operational data including Uri-week and 2023 Derecho event data — not synthetic benchmarks. Deterministic fallbacks are mandatory on anything that touches operational decision support. Handoff documentation is structured for Oncor's IT, ops, and reg-affairs teams to own and audit at month 18.

03 · Industry

Energy & Utilities Angle

Texas utility AI has a specific regulatory shape that shouldn't be glossed over. ERCOT operates outside FERC jurisdiction for most purposes, which changes the reliability-standards conversation — NERC CIP still applies to BES Cyber Assets, but the market-layer data exchange with ERCOT has its own protocols and timing requirements that AI systems touching bid submission, ancillary services, or real-time market data need to respect. PUCT oversight covers rate cases, reliability reporting, and prudence review of capital investments. An AI system classified as part of capital-investment spending has to survive PUCT prudence review — the documentation of value has to be structured the way rate-case filings are structured.

Post-Uri reliability is the dominant Texas regulatory conversation of this decade. Every utility capital plan, including AI-adjacent spending, is evaluated against contribution to reliability under extreme weather. Oncor's Uri experience was less catastrophic than some ERCOT entities but the system-wide political and regulatory aftermath — SB 3, weatherization requirements, PUCT market-design reform — reshaped the environment. AI investments that improve storm-event operational performance, load-shed coordination accuracy, or restoration sequencing have a clear path through prudence review. AI investments pitched as abstract modernization don't.

The corporate-campus concentration in Plano adds a customer-experience layer that doesn't exist in most utility markets. Toyota's facilities team, JPMorgan's operations leadership, Liberty Mutual's business continuity group each maintain expectations about outage communication accuracy, ETR precision, and post-event analytics that match what they'd expect from a commercial SaaS vendor. Oncor's customer-facing tools for these accounts — and the AI systems that feed them — operate at that SLA standard, not at a residential-customer-service standard. We scope accordingly.

04 · Partnership

Why MSG

MSG is a Gulf Coast operator-consulting firm that ships production software and has for the last decade. ServiceStorm operates at multi-tenant SaaS scale across Gulf Coast home services operators through hurricane seasons and freeze events. MFGBase is a B2B marketplace connecting manufacturers. LocalAISource is an AI professionals directory. That's operator experience, not a consulting deck. When we come into an Oncor-adjacent Plano engagement, we bring engineers who know what production reliability means in Texas weather — because our own systems survive Texas weather.

The 289-mile distance from Beaumont is honest. We're not down-the-street the way we are with Houston engagements. But the corporate-campus dynamic in Plano favors an onsite cadence pegged to integration milestones rather than weekly standups — a pattern we've refined across North Texas engagements. Multi-day kickoff immersion, integration-sprint anchoring visits, pre-summer-peak readiness review in May, post-winter-peak lessons-learned review in February.

We refuse scopes that don't ship. Most AI consulting in utility space ends at a roadmap deck. Ours end at a system running at month 18 without us, documented for PUCT prudence review and NERC CIP audit. The trade-off versus a national consulting firm is specific: you get engineers instead of analysts, Gulf Coast operational instinct instead of coastal-city abstractions, and production artifacts instead of slideware. What you don't get is a 50-person onsite team; we scope tight and ship.

05 · Outcome

12 Months In

Twelve months in, a Plano-focused engagement produces AI systems running against live Oncor operational data with measurable impact on the metrics PUCT, corporate-campus customers, and Oncor ops leadership actually track. SAIDI/SAIFI improvement from sharper OMS triage during convective-storm events, typically 8-14% on storm-attributed customer-minutes-interrupted. ETR windows tightened to within 30 minutes on routine feeder outages. AMI-to-insight time reduced from the monthly billing-report cadence to same-day operational signal. 4CP and DR-program forecast accuracy improved by single-digit percentage points that translate into real commercial-account savings. Systems owned by your team at handoff, documented to CIP-010 change-management standards.

06 · FAQ

Common questions

Our Plano service area is a Class 4/5 commercial customer concentration. Does MSG build for that rather than a residential-dominated utility profile?

Yes, and it's a material scoping difference. Commercial-dominated service areas behave differently on almost every operational dimension that matters for AI: outage-call generation patterns cluster on single-feeder events, demand-response participation rates sit an order of magnitude higher than residential, 4CP coincident-peak behavior drives billing and capacity planning, and customer-experience SLA expectations resemble B2B SaaS rather than residential utility. We scope OMS triage models against commercial-outage call-surge patterns, build AMI analytics around commercial-meter anomaly detection at higher fidelity than residential, and structure customer-communication AI outputs at a commercial SLA standard. The residential service areas inside the same Oncor territory get treated on their own terms.

How does MSG handle the PUCT prudence review documentation requirement for capital-classified AI spending?

We structure deliverables, documentation, and outcome measurement from kickoff so the prudence-review artifacts are native to the engagement, not retrofit. That means: capital-versus-O&M classification clean from the accounting scope of work, defined outcome metrics tied to reliability or customer-experience improvements that match PUCT rate-case review patterns, cost-benefit documentation structured against historical baseline operational data, and a data-lineage record that a reg-affairs team can walk into a PUCT case with. We coordinate with your reg-affairs group in week one to confirm the documentation pattern matches how Oncor structures filings — we don't assume a one-size-fits-all model.

What's realistic for AI-assisted demand-response and 4CP forecasting given ERCOT's real-time price volatility?

Day-ahead 4CP forecasts at meter-level and feeder-level aggregation can realistically improve by 2-5 percentage points on mean absolute error against current utility baselines, which translates into commercial-account coincident-peak billing savings that are measurable in a single summer. Real-time DR dispatch optimization is a tighter problem — we can improve dispatch accuracy and reduce over-curtailment, but the ERCOT market dynamics introduce a forecast-uncertainty floor that no AI system can dissolve. We scope with realistic bounds and document the uncertainty, rather than promising miracle forecasts.

Legacy West and the Toyota/JPMorgan campuses have their own private utility infrastructure in some cases. How does AI work integrate across that boundary?

Campus-level private distribution behind a meter point is a data-access and integration question more than an AI modeling question. Where the campus facilities team is willing to share sub-meter data back to the utility through a governed interface, AI systems can extend visibility inside the campus load profile — which improves outage attribution, transformer loading understanding, and commercial-program design. Where they're not, the AI system operates at the utility side of the meter point and treats the campus as a load aggregate. We scope both patterns and we don't assume one fits all campus accounts; that's a customer-by-customer conversation.

How does Uri reality show up in MSG's AI engagement structure?

Uri is in every evaluation harness and every load-test scenario we design for Texas utility work. We take the February 2021 operational data — the load-shed rotations, the customer-service call-volume patterns, the communication-system stress, the ETR-accuracy degradation — and we use it as a benchmark condition. If an AI system doesn't perform acceptably under Uri-class scenarios, we don't ship it. We also design deterministic fallbacks for when primary operational systems are themselves in restoration or degraded state, because during Uri the communication and control systems themselves were stressed, and AI that depends on fully-healthy primary systems failed.

How often is MSG onsite in Plano during a typical engagement?

For a 12-week first engagement, we plan a 3-4 day kickoff immersion onsite, 4-6 additional onsite visits anchored to integration milestones, and a pre-summer-peak readiness visit in mid-May. The 4.5-hour drive from Beaumont means we don't do half-day drop-bys, but we do multi-day immersive work periods that actually fit the integration cadence. For extended engagements beyond 12 weeks, we add post-winter-peak lessons-learned visits in February. Remote cadence fills the gap — daily async standups, weekly video sessions, and integration-sprint working groups with your IT and ops teams.

Ready to engineer AI into your Plano utility operation?

Let's scope one production-grade system that integrates with Oncor's real stack and ships inside one Texas weather cycle.

Start a Conversation