Technology Integration for Energy & Utilities Operators in Irving, TX
Irving's energy operator profile is unusual because the city sits inside Oncor's distribution territory while hosting corporate headquarters and back-office operations for some of the largest energy companies in North America. ExxonMobil's HQ is in Las Colinas. Pioneer Natural Resources sat here before the Exxon acquisition closed. Vistra Energy is twenty minutes east in Irving's broader DFW backyard. The technology integration conversation in Irving therefore splits in two directions at once — distribution-utility operators wrestling with AMI data that never made it past the billing team, and corporate energy IT shops trying to rationalize a portfolio of acquired systems that span ERCOT operations, generation assets, and retail electric provider books. MSG works both sides of that conversation. We don't sell a platform. We come in, map what's actually running, find the integration gaps that cost money, and build the connective tissue that makes the existing investment finally pay back.
Irving Context
Irving sits in the heart of the DFW metroplex, 240,000 people inside city limits, embedded in a metro of 7.9 million. Las Colinas is the corporate spine — masterplanned in the 1970s, now home to ExxonMobil, Kimberly-Clark, McKesson, and a deep bench of Fortune 500 back-offices. The city's electric distribution is Oncor territory, the largest transmission and distribution utility in Texas with roughly 13 million customers across the eastern two-thirds of the state. Natural gas distribution is Atmos Energy. Water is City of Irving Water Utilities, drawing from the Trinity River basin and Dallas County reservoirs.
The regulatory backdrop is ERCOT — the Electric Reliability Council of Texas — which runs the grid serving roughly 90% of Texas load and operates as an island, largely disconnected from the Eastern and Western Interconnections. ERCOT's market design (energy-only, no capacity market, scarcity pricing capped at $5,000/MWh post-Uri reforms) drives the operational software requirements for any retail electric provider, generator, or large industrial load operator headquartered in or near Irving. The PUCT (Public Utility Commission of Texas) sits in Austin but its rulemaking — ERCOT market protocols, weatherization standards post-Uri, distribution reliability metrics — lands directly on Oncor and on every REP and IPP doing business in the territory.
MSG is 305 miles south of Irving on I-45 and US-287, about a five-hour drive. We treat DFW as a deliberate-cadence market — multi-day kickoff immersions, on-site visits structured around real operational milestones (ERCOT seasonal assessments, AMI deployment phases, post-event reviews), weekly video working sessions in between. We're close enough that an emergency post-event integration session is a same-day drive, far enough that we structure engagements for efficiency rather than drop-in informality.
How We Deliver
Discovery for an Irving energy or utility client starts with a stack audit week one. We document every operational system in the environment — OMS (often Oracle Network Management or GE PowerOn), AMI head-end systems (Itron, Landis+Gyr, Sensus depending on the vintage), MDM (Itron Enterprise Edition or Oracle MDM), GIS (Esri ArcGIS Utility Network), CIS/billing (Oracle CC&B, SAP IS-U, or one of the smaller utility CIS platforms), DMS, SCADA, ADMS where deployed, work management (Maximo, Click, IFS), and the increasing layer of analytics and DERMS tools sitting on top. For corporate energy operators we map ERCOT settlement systems, ETRM platforms (Allegro, OpenLink, RightAngle), gas nominations and scheduling systems, and the data warehouses that try to tie all of it together.
The integration work breaks down predictably. AMI-to-OMS feeds that should drive last-gasp outage notifications but don't. GIS-to-OMS connectivity model sync that drifts and produces phantom outages. MDM data that lands in billing but never reaches operations or planning. CIS customer hierarchy that doesn't match how field crews actually think about the territory. ETRM positions that don't reconcile cleanly to settlement. We design the integrations as additions to your existing architecture, not replacements — read-only data layers, defined contracts, change-controlled deployments. We build with API gateways where vendor systems support them, ESB or message-bus patterns for the systems that don't, and we document every interface so your team owns it after handoff.
Implementation runs in 8-16 week increments depending on scope. Training and handoff is non-negotiable in our scope — your operations team, your IT team, and your data team all get walkthrough sessions, written runbooks, and observability dashboards they can read on day one without us in the room.
Energy & Utilities Angle
Energy and utilities is the most heavily-systemed industry MSG works in, and ironically that's exactly why integration work is the highest-leverage investment most operators can make. The big platform vendors — Oracle, SAP, Esri, OSI, GE — all sell complete suites and all of them assume their suite is the center of the universe. In practice every utility runs a hybrid environment with components from multiple vendors layered over multiple decades of acquisitions, regulatory mandates, and technology cycles. The integrations between those components are where the operational pain actually lives.
AMI is the canonical example. Most utilities in ERCOT territory completed their AMI rollouts a decade ago, and most of them are still operationalizing the data primarily for billing. Outage management improvements, transformer load monitoring, voltage optimization, theft detection, DER visibility — all theoretically possible with AMI data, all blocked in practice by integration gaps between the head-end, the MDM, and the operational systems that need the data in near-real time. We've watched utilities run pilots on AMI-driven outage detection for years without operationalizing it, because the integration work to feed AMI into OMS reliably with proper data quality checks is harder than it sounds and nobody's accountable for it.
The corporate energy side has its own version of the same problem. Vistra, NRG, Calpine, and the IPP/REP cohort headquartered in DFW run ETRM, settlement, scheduling, and risk systems that all need to reconcile. ERCOT's 5-minute settlement cadence and the post-Uri weatherization and reliability rules have raised the bar on data integrity. The operators who have clean integration discipline run leaner risk and settlement teams. The ones who don't carry headcount in reconciliation that should be solving harder problems.
Distributed energy resources are now the variable that's rewriting all of it. Utility-scale solar in West Texas, behind-the-meter solar and battery growth across DFW residential and C&I, transportation electrification load showing up on distribution feeders that weren't designed for it. ADMS and DERMS deployments are real but they only work if the underlying GIS, AMI, and OMS integrations are solid. Skipping that foundation and bolting DERMS on top is how integration projects fail visibly at $20-50M each.
Why MSG
MSG is an operator-consulting firm that ships production software. We've built ServiceStorm (multi-tenant operations platform for service businesses), MFGBase (B2B manufacturing marketplace), and LocalAISource (AI professional directory) — production systems serving real users, not slide decks. That operator depth shows up in how we scope integration work. We don't deliver architecture diagrams and walk away. We build the integrations, we wire up the observability, we hand off runbooks your team can actually use.
We also don't carry vendor allegiances. Oracle, SAP, Esri, GE, OSI, Itron, Landis+Gyr — we've worked across all of them and we'll tell you directly when one component is the source of an integration headache and when it's actually fine and the problem is somewhere else. Most of the integration work that fails in utilities fails because the consultant had a financial reason to defend a particular platform's architecture. We don't.
And we're regional. Beaumont to Irving is a five-hour drive on I-45, not a flight from a coastal hub. Our DFW engagements have meaningful on-site presence at the operational moments that matter — pre-summer ERCOT seasonal assessment, post-event integration reviews, AMI deployment milestones, ADMS go-live windows. Gulf Coast operators talking to Gulf Coast operators about systems that have to work in the conditions we both live in.
Outcome
Twelve months into an MSG integration engagement, an Irving energy or utility operator has a stack that talks. AMI data flows from head-end through MDM into OMS, planning, and analytics with documented data quality checks at every hand-off. GIS-to-OMS connectivity sync runs on a schedule with drift detection, not on heroics. CIS customer hierarchy matches operational geography. For corporate energy operators, ETRM positions reconcile cleanly to ERCOT settlement, gas nominations flow into the same data warehouse as power scheduling, and the risk team stops carrying reconciliation headcount. The integrations are documented, observable, and owned by your team — not living in a consultant's laptop.
FAQ
We've spent years and tens of millions on AMI and we're still mostly using it for billing. Can MSG actually move us past that?
Yes, and we'd start by being honest about why you're stuck. The pattern is almost always the same — the AMI head-end and MDM were procured and operationalized by the metering and billing teams, the operational systems that would benefit from AMI data sit under different IT and operations leadership, and nobody owns the integration between them. The first 60 days of an MSG engagement maps the actual data flow from meter to MDM to whatever operational system needs it (OMS, planning, transformer monitoring, DER visibility), identifies the specific integration and data quality gaps, and scopes the build. Most utilities find the first high-leverage AMI use case — usually last-gasp outage notification feeding OMS, or transformer load monitoring feeding planning — pays back faster than the entire AMI deployment did, because the meter investment is already sunk.
Our environment is Oracle CC&B plus Esri ArcGIS Utility Network plus an Itron AMI head-end plus a couple of internal data warehouses. Is that something you've actually worked in?
Yes. That's a common mid-size IOU stack in ERCOT territory and the integration patterns between those systems are well-trodden territory for our team. The specific pain points tend to be CC&B-to-MDM customer hierarchy mismatches, GIS-to-OMS connectivity model sync drift, and the reporting layer trying to reconcile data across all three. We don't pretend to be Oracle CC&B implementation experts — that's a different consulting niche — but we are integration experts who can sit between the platforms and make the data flow correctly. If your environment includes platforms outside that core, we'll be direct about what we know cold versus what we'll need a week of ramp-up on.
How do you handle change control? Our IT and operations teams have well-defined release windows and we can't have a consultant pushing breaking changes.
Change control discipline is non-negotiable in utility environments and we structure every engagement around it. We work inside your existing change advisory board (CAB) cadence. Our deliverables are documented as standard change requests with full rollback procedures, test evidence, and operational acceptance criteria. We don't push to production without your team's sign-off, and we don't operate on a 'move fast and break things' tempo because we know what production means in a utility. If your shop has formal NERC CIP cybersecurity controls in scope, we work to those controls — that's where utility-grade discipline diverges from generic enterprise IT.
We're a corporate energy operator headquartered in Las Colinas — IPP and REP businesses both. ETRM, settlement, and scheduling integration is the pain point. Is that in MSG's wheelhouse?
Yes, and it's actually closer to MSG's core strength than the regulated-utility integration work. Corporate energy IT environments tend to be more pragmatic about platform choice and faster on change cycles, and the integration patterns between ETRM (Allegro, OpenLink, RightAngle), settlement, gas nominations, and the data warehouse are problems we can scope and execute against tight timelines. ERCOT 5-minute settlement, post-Uri weatherization reporting, and the increasing renewable portfolio penetration are pushing data quality and reconciliation discipline higher every year. We help operators get ahead of that curve.
What's a realistic budget for an MSG integration engagement?
We don't quote cookie-cutter pricing because integration scope varies hugely. A scoped first engagement — say, AMI-to-OMS last-gasp outage notification with proper data quality checks and operational handoff — typically runs in the low-to-mid six figures and 12-16 weeks. A larger engagement that addresses multiple integration gaps across an enterprise environment runs longer and bigger, but we structure those as a sequence of scoped deliverables rather than an open-ended retainer. We tell you upfront what we think we can move, on what timeline, for what fee.
How often will MSG actually be in Irving?
For a 6-month integration engagement, expect a 3-day kickoff immersion plus 4-6 on-site working sessions, typically tied to operational milestones — AMI deployment phases, ERCOT seasonal assessment prep, post-event integration reviews, ADMS go-live windows. For 12-month engagements, 8-12 on-site visits. Weekly video cadence in between. The 5-hour drive from Beaumont on I-45 makes Irving a deliberately-paced market — we structure for efficiency, not drop-in informality, but we're close enough that emergency on-site support is a same-day option when something breaks at 3 PM and your team needs us in the room by dinner.
Other Industries in Irving
Tech Integration in Other Cities
Other MSG Services
Ready to make your Irving energy stack actually work as one system?
Let's audit what you have, find the integration gaps that cost real money, and build the connective tissue that pays back the platform investments you've already made.