Technology Integration for Energy & Utilities in Arlington, TX
Arlington is one of those middle-ring DFW cities where the utility reality doesn't get a marquee headline but where the integration layer carries a heavier load than the city's population suggests. Oncor serves the T&D footprint, REPs carry the retail relationships, and the customer base runs from residential neighborhoods through the University of Texas at Arlington, AT&T Stadium, Globe Life Field, and the industrial and logistics corridor along I-20 and I-30. The integration challenge here isn't exotic — it's the accumulated weight of a decade of tactical integration work, middleware nobody fully documents, and the pressure of being a secondary node in a much larger Oncor integration architecture that wasn't designed city-by-city. When a storm rolls through the DFW metroplex, Arlington's outages feed into the same OMS, the same CIS, and the same public outage map as the rest of the Oncor footprint — but the integration layer has to work specifically for Arlington's feeders, Arlington's customer mix, and Arlington's operational partnerships. MSG builds integration that respects that reality.
Arlington Reality
Arlington is ~395,000 people in the middle of the DFW metroplex, bounded roughly by Fort Worth to the west, Dallas to the east, Grand Prairie to the south, and Irving to the north. The city serves as a major employment, entertainment, and education node: UT Arlington's campus, the Rangers and Cowboys stadiums and the surrounding entertainment district, General Motors' Arlington Assembly plant (one of GM's largest SUV production sites), and a significant healthcare and logistics presence. Oncor is the TDU serving the electric T&D footprint, with the standard Texas market split between wires (Oncor) and retail (REPs through ERCOT).
The mix of residential, educational, entertainment venue, and heavy industrial load creates integration complexity that doesn't show up in a population count. AT&T Stadium and Globe Life Field are high-profile customers with specific reliability requirements and event-driven load patterns. GM Arlington Assembly is a large industrial customer with contract-backed service expectations. UT Arlington operates as a campus-scale customer with its own distribution and growing microgrid and solar interest. Hospitals, data-adjacent logistics, and commercial corridors along the I-30 and I-20 crosshair add more demanding load profiles. Every one of those customer segments shows up in the integration layer differently — in the CIS customer records, in the OMS priority routing, in the ADMS feeder modeling, in the customer portal expectations.
Storm exposure is real. DFW-area convective events, ice storms, and occasional tropical remnants all produce Arlington outages, and the integration layer has to carry event data cleanly across the metroplex during regional events. Post-Uri and post-Beryl (remnants hit the metroplex), the performance of the integration layer during major events has become a recurring regulatory conversation. MSG is 315 miles east of Arlington on I-20/I-10 — about five hours. For Arlington engagements we structure around multi-day onsite immersions with weekly video cadence between, and we commit to onsite presence through cutover and major event windows.
How We Deliver
An Arlington-focused integration engagement — whether for an Oncor-aligned workstream, a REP with significant Arlington-area load, or a large end customer like a campus or major commercial account — starts with an audit that maps the actual state of the integration layer. For a utility-side engagement, that's CIS, OMS, ADMS, AMI headend, GIS and asset management, the ERCOT-facing transaction layer, and the middleware tying them together. For a large end-customer engagement, it's the energy management systems, building management, submetering, demand response platform, and the integration with the REP and TDU interfaces that flow billing and operational data.
From the audit we produce architecture recommendations that respect existing platform investments and regulatory constraints. Implementation runs on your existing integration platform. We design explicitly for storm-mode behavior — the integration patterns that hold at normal load versus the patterns that need to carry 10x event volume during a major storm. We design explicitly for the customer-segment realities of Arlington's mix: high-profile venue customers, industrial customers, education campus customers, and residential.
For Arlington-scale engagements we typically scope in phases: foundational audit and architecture (8-12 weeks), first high-priority integration build (12-20 weeks), broader roadmap rollout over 9-15 months. We scope every engagement to end with your team running the platform independently.
Energy & Utilities Angle
Middle-ring suburban integration work has a specific character the big consultancies often miss. The customer mix is heterogeneous in ways that push integration patterns harder than a pure-residential or pure-industrial footprint. A Saturday evening Rangers game coincides with peak summer residential AC load and a hospital's baseline critical load and a GM shift change's industrial load. The integration layer that supports outage management, customer communication, and reliability reporting has to carry all of those customer segments simultaneously, and the patterns that work for a residential-only city don't scale cleanly to this mix.
Storm-mode integration is where most middle-ring utilities take the hardest hits, because event volume spikes 10-20x normal and the integration patterns designed for steady-state behavior cascade-fail. AMI last-gasp signals surge, OMS trouble call queues back up, CIS customer context lookups lag, outage map traffic overwhelms the publish pipeline, and crew dispatch handoffs lose context. The integration architecture has to include explicit storm-mode behavior — asynchronous queues with backpressure, degraded-mode fallbacks, event replay capability, and observability that shows what's actually happening under load. Most utilities discover these gaps during the event and spend the next six months patching.
Large end-customer integration is a growing area in middle-ring cities. Campus-scale and industrial customers are investing in energy management, submetering, and on-site generation and storage at a rate that outpaces utility integration capability. The integration between customer-side EMS/BMS and the utility CIS, AMI, and DR platforms is often ad hoc — usually a flat file export or a utility-provided portal scrape. There's significant value in building clean API-level integration here, both for the customer's operational needs and for the utility's program capability.
Why MSG
MSG runs production software. ServiceStorm is a multi-tenant home services SaaS serving operators across the Gulf Coast. MFGBase is a B2B marketplace connecting manufacturers. LocalAISource is a live AI directory. Every one of those systems has real integration surface that has to function at real volume, every day, with real customers depending on it. The engineering discipline required to operate those systems shows up in how we run utility integration engagements.
We write adapters, build observability, sit in operations centers during storm events, and scope engagements to end at a system your team runs without us. We work with your existing integration platform rather than arriving with a product to sell. We document everything so the next engineer on the platform — whether on your team or ours — can pick up the work without tribal knowledge.
Beaumont to Arlington is five hours on the ground. We structure Arlington engagements around multi-day onsite immersions, weekly video cadence between, and onsite presence during major events. Control-system and integration work rewards physical presence, and we deliver it rather than pretending that quarterly Zoom calls are equivalent.
12 Months In
Twelve months in, an Arlington-focused integration engagement delivers a layer that handles storm-mode load, carries the customer segment mix cleanly, and produces reliability reporting that passes regulatory scrutiny. OMS holds context through major events. CIS customer context is available in real time to the customer-facing channels. Large end-customer integrations are clean. The integration team extends the platform without vendor dependency.
Common questions
What's the realistic scope for an Arlington-focused integration engagement, given we're inside a much larger Oncor footprint?
Usually a specific workstream rather than a full architecture redesign. Middle-ring utilities inside a large TDU footprint don't get their own CIS or OMS — they inherit the Oncor-scale systems. The integration work that makes sense locally is usually around the specific Arlington-area workflows that matter operationally: major-customer integration (venues, campuses, large industrial), storm-mode behavior for the Arlington feeders, coordination with city-level emergency management, and specific reliability reporting for Arlington's notable customer base. We'd audit what's specifically Arlington-shaped in the integration layer, identify where the generic Oncor patterns are underserving the local reality, and scope targeted work that closes those gaps. This is usually a tighter engagement — 6-9 months — focused on specific outcomes rather than a broad architectural rebuild. The scoping conversation is the single most important step: a clear definition of what's in scope, what's out of scope, and what measurable outcome each workstream produces. We document that in writing before any code is written, and we revisit it monthly to keep the engagement honest.
Our OMS struggled during the last major storm that hit the metroplex. Can integration work improve storm-mode behavior specifically for Arlington?
Yes, and storm-mode redesign is one of the more measurable integration workstreams. We'd reconstruct what happened during the last major event at the integration layer: AMI last-gasp signal volume and how it was handled, OMS trouble call backlog and where it accumulated, CIS customer context lookup latency during the event, outage map publish pipeline behavior, and crew dispatch handoff patterns. From that reconstruction we identify specific choke points and redesign integration patterns for storm mode — asynchronous queues with backpressure, degraded-mode fallbacks that preserve core functionality when components are struggling, event replay capability, and observability that surfaces issues during the event rather than after. We'd also design explicit storm-mode activation procedures so the integration layer behaves differently under event load without requiring manual intervention. Then we rehearse. Storm-mode behavior that isn't exercised against simulated event load tends to fail in novel ways during the real event. We build rehearsal runs into the engagement and validate behavior before hurricane season arrives.
We have high-profile venue customers — Cowboys and Rangers stadiums — with specific reliability expectations. How does integration work support that?
Venue customers have particular integration needs around event-driven load patterns, reliability priority routing, communication workflows, and coordination with venue operations during incidents. The CIS has to carry the venue customer record with appropriate priority flags. The OMS needs to route venue-adjacent outages for fast response and escalation. The customer communication layer has to support direct coordination with venue operations during events — not just generic customer notifications. The AMI data has to support the detailed load analysis these customers increasingly want for their own operations. We'd map the venue-specific integration requirements, coordinate with the venue operations teams, and build integration patterns that make venue customer service a first-class workflow rather than a bespoke exception. This generalizes to other high-profile customers — major hospitals, data centers, major industrial customers — so the investment pays back beyond just the stadiums. A Saturday evening game day exercises the grid in ways that a generic residential-shaped integration layer won't handle well, and building venue-grade patterns surfaces improvements applicable to every critical-infrastructure customer in the territory.
How do you handle NERC CIP compliance during integration work?
Explicitly, from the first week. Every integration design we produce includes a CIP scoping document identifying electronic security perimeter boundaries, compensating controls, and change management implications. CIP-005, CIP-007, and CIP-010 are designed into the architecture, not retrofitted at audit. For integration crossing the ESP, we use data diode or one-way transfer patterns where appropriate, documented API gateways with change-controlled whitelists where bidirectional flow is required, and logging that gives your compliance team a defensible audit trail. We coordinate with your CIP compliance lead throughout the engagement so there are no surprises at audit. We've seen enough utility integration projects go sideways on CIP documentation to know the specific places where scope creep drags new assets into applicability, and we design against those risks upfront. Clean CIP documentation at engagement start also makes subsequent audit cycles materially easier because the paper trail already exists — the next auditor isn't rebuilding context from operational memory.
We have large end customers — GM Arlington Assembly, UT Arlington, major healthcare systems — asking for real API-level integration. Is that work you do?
Yes, and it's an underserved area at most utilities. Large end customers increasingly want programmatic access to usage data, programmatic enrollment in programs (DR, TOU, EV), and programmatic interaction with interconnect workflows. The 'green button' standard is a floor, not a ceiling. Building a real customer API layer means taking CIS, AMI, and program data and exposing it through a coherent external interface with authentication, rate limiting, versioning, and developer documentation. That's not trivial — it touches every downstream system — but the payoff is significant. For large end customers specifically, we'd also look at integration into their EMS/BMS platforms, into their submetering systems, and into their demand response and energy management workflows. Clean integration here reduces the manual data exchange that currently eats operational time on both sides, and positions the utility as an integration partner rather than a passive vendor when customers plan their next capital project expansion.
How often will MSG actually be onsite for an Arlington engagement?
For an active implementation phase, weekly minimum and typically multi-day (two to four day onsite weeks). For steady-state work, weekly or bi-weekly. During any major event — storm, cutover, go-live — we're onsite for the duration. The five-hour drive from Beaumont makes Arlington one of our accessible Texas markets, and we structure engagements around real presence rather than pretending video calls substitute for whiteboarding integration patterns in person. For a 9-month engagement we typically deliver 25-35 onsite days. For a 12-month engagement, 40-50 onsite days. We document the cadence upfront so everyone knows what presence to expect, and we block the calendar against it rather than treating onsite work as aspirational. Control-system and integration work is done better with engineers in the room, not on a video call, and we deliver that reliably over the course of the engagement rather than apologizing for absence later.
Other Industries in Arlington
Tech Integration in Other Cities
Other MSG Services
Ready to sharpen your Arlington utility integration layer?
Let's audit the storm-mode patterns, the major-customer integrations, and the reliability reporting — then build integration that holds up.