Technology Integration for Energy & Utilities in New Orleans, LA
Entergy New Orleans operates under a regulatory structure that doesn't exist anywhere else in the country. The New Orleans City Council is the rate regulator for Entergy's electric and gas utility within Orleans Parish, instead of the Louisiana Public Service Commission that regulates the rest of Entergy Louisiana. That single structural fact reshapes everything about how technology integration has to be planned, documented, and defended in New Orleans. Every major integration initiative eventually touches a rate case or a reliability filing in front of the Council, and every reliability event — Katrina still in living memory, Ida in 2021, Francine in 2024 — gets reviewed publicly with data that flows from the integration layer. Meanwhile the actual systems — Oracle CC&B on the customer side, a modernized OMS, a multi-year AMI rollout, Esri GIS with Utility Network work underway, the ERCOT-equivalent MISO market interface — carry the same technical complexity as any large IOU, plus the additional stack shared with the broader Entergy corporate footprint. MSG builds integration that holds through hurricane events, passes Council scrutiny, and respects the peculiar regulatory architecture of this market.
New Orleans context
Orleans Parish is 384,000 people and the New Orleans metro runs to 1.27 million across eight parishes. Entergy New Orleans serves electric and gas within Orleans Parish, with approximately 210,000 electric customers and 105,000 gas customers. The unusual regulatory structure — New Orleans City Council as rate regulator — means Entergy New Orleans has its own rate cases, its own reliability filings, and its own public process distinct from Entergy Louisiana's LPSC-regulated territory. The Council's Utility, Cable, Telecommunications and Technology Committee handles most of the regulatory workload, with its own advisory staff and its own public engagement process.
The broader Entergy corporate footprint shapes the integration environment. Entergy Services provides shared technology infrastructure across Entergy Arkansas, Entergy Louisiana, Entergy Mississippi, Entergy New Orleans, and Entergy Texas. Many core systems — CIS, elements of the OMS, AMI headend, financial systems — are shared or shared-pattern across operating companies. That creates integration efficiency but also means Entergy New Orleans-specific integration work has to respect enterprise architecture decisions made at the corporate level. It also means work done for Entergy New Orleans has patterns that generalize across the Entergy footprint — valuable context for both sides of the engagement.
Hurricane exposure is the dominant operational reality. Katrina (2005) reshaped the utility permanently. Ida (2021) produced widespread infrastructure damage and extended outages that ran into weeks for parts of the territory. Francine (2024) was a newer reminder that the threat is active. Every integration design has to assume significant storm events at multi-year frequency and has to carry operational behavior that stays coherent through multi-week restoration periods. MISO is the RTO, with its own transaction flows, reliability coordinator interfaces, and market settlement requirements. MSG is 241 miles east of New Orleans on I-10 — about three and a half hours. For New Orleans engagements we structure around multi-day onsite immersions, weekly video cadence between, and onsite presence through hurricane season operational planning and any active event window.
Delivery
An Entergy New Orleans integration engagement starts with an audit that respects the enterprise architecture context while identifying the local integration work that's most impactful for the utility's own operations and regulatory posture. We map the CIS (shared Oracle CC&B footprint across Entergy companies), OMS, ADMS, AMI headend (the multi-year AMI deployment has specific integration implications), GIS and asset management, MISO-facing integration, and the middleware layer. We read the actual data flows for a customer move-in in Orleans Parish, an outage event from last-gasp through crew dispatch and restoration, a rate rider application, and the regulatory reporting that eventually produces Council-reviewed filings.
From the audit we produce architecture recommendations that coordinate with Entergy enterprise architecture while addressing the specific integration gaps and storm-mode patterns that matter locally. Implementation runs on the existing integration platform — Entergy's enterprise integration investments — with selective pattern changes where they're needed. We design for hurricane-season operational readiness explicitly: storm-mode activation, event restoration workflows that carry data cleanly through multi-week restoration, mutual assistance integration, and the specific reporting cadence that Council post-event reviews demand.
For New Orleans engagements we typically scope in phases: foundational audit and architecture (10-14 weeks), first high-priority integration build (14-22 weeks), broader roadmap rollout over 9-15 months with explicit pre-hurricane-season (June) and post-season (November) operational review checkpoints.
Energy & Utilities angle
New Orleans utility integration carries characteristics that generalize poorly to other markets. The Council regulatory relationship means integration work has a public accountability layer that PSC-regulated utilities don't face in the same way. Public meetings, direct advisory staff scrutiny, and community input processes all touch the integration roadmap. Integration projects that assume a PSC-style docket-driven regulatory process miss the political and community dynamics that actually shape decisions here. We've watched integration initiatives stall because the technical merit was solid but the Council engagement was weak. Good integration engagement plans Council interaction as a first-class workstream.
Hurricane-cycle operational integration is the dominant technical reality. A typical major hurricane produces hundreds of thousands of customer outages, field crew deployments from mutual assistance across the country, restoration timelines that stretch into weeks, and real-time public communication requirements that don't stop. The integration layer has to hold through all of it. AMI last-gasp volume, OMS trouble call context preservation through multi-day events, CIS customer context availability when the contact center is running 24/7, crew dispatch and mutual assistance coordination, outage map publishing, and regulatory reporting during and after the event all pull from the same integration layer. Storm-mode design isn't a feature — it's the central architecture concern.
MISO-facing integration has its own rhythm. Reliability coordinator interfaces, real-time telemetry, day-ahead and real-time market participation, settlement reconciliation, and the transmission planning coordination all produce integration surface distinct from retail-side work. The Entergy footprint's MISO participation is substantial, and New Orleans integration plays in that broader context.
Why MSG
MSG builds production software for real customers. ServiceStorm is a multi-tenant SaaS serving Gulf Coast home services operators — including operators in New Orleans navigating every hurricane cycle since we've been in market. We know what storm-cycle operational reality looks like because our own customers live through it. MFGBase connects manufacturers globally. LocalAISource is a live production directory. Each of those products demands real integration work that functions at real volume — the engineering discipline required shows up in utility engagements.
Our engagement model respects the unusual New Orleans regulatory architecture. We plan Council engagement as part of integration work, not as an afterthought. We document every architectural decision with an audit trail that stands up to Council staff review. We coordinate with Entergy enterprise architecture teams explicitly rather than pretending operating company work exists in isolation. And we're Gulf Coast operators ourselves — we plan engagements around hurricane season, we don't treat a May-November timeline as if it were a July-December timeline, and we're available for pre-season readiness work and post-event response work.
Beaumont to New Orleans is 241 miles, three and a half hours on I-10. That's closer than most of our Texas metro engagements. We structure New Orleans work around real onsite presence — multi-day weeks during active implementation, weekly onsite during steady state, onsite through any active storm event during the engagement.
Twelve months in, an Entergy New Orleans-focused integration engagement delivers a layer that holds through hurricane events, supports Council reporting without heroic manual work, and extends cleanly into future DER and program expansion. Customer events flow end-to-end from AMI through OMS and CIS. Storm-mode behavior is designed and practiced. MISO-facing flows are clean. Council-ready reliability reporting produces directly from operational systems. The integration team extends the platform without vendor dependency.
FAQ
The City Council regulatory model is unique. How does MSG actually plan around it?
As a first-class engagement workstream with documented Council interaction planning from day one. We work with your regulatory affairs and legal teams to identify where integration work will surface in Council proceedings — rate case filings, reliability filings, storm response reviews, specific technology-related resolutions — and we plan the technical work with those checkpoints in mind. Every major architectural decision gets documented with the kind of written rationale that stands up to Council staff review. Public-facing deliverables (reliability metrics, rate case data, outage reporting) are designed with auditability as a first-class requirement, not a retrofit. We've seen enough consulting engagements in publicly-accountable environments to understand the difference between technical work that's right and technical work that's defensible — we aim for both. We also respect that Council timelines aren't negotiable and plan the engagement around them. Missing a Council deadline because the integration work slipped is the kind of outcome that erodes trust for years. Planning backward from Council dates rather than forward from engagement start is the discipline that makes this work durable.
Our AMI rollout is in progress. How should integration design accommodate a partial-deployment footprint during the rollout phase?
With explicit dual-mode patterns and a clean transition plan. During AMI rollout, integration has to handle a heterogeneous meter population — new smart meters, legacy AMR meters, remaining manual-read meters — all producing data into the same CIS and billing stack. Integration patterns have to accommodate mixed data timing (smart meter intervals versus legacy reads), mixed event capability (only smart meters produce last-gasp outage signals), and mixed field service workflows. We'd design integration for the during-rollout state explicitly — not pretending the deployment is complete — and build in the transition patterns that let each meter upgrade flow through without requiring a separate integration project. Post-deployment, the OMS integration with AMI last-gasp data and the customer portal integration with interval data become first-class workflows that weren't possible at full scale before. Planning for the post-AMI state during the rollout saves significant rework later. Too many AMI deployments end up with integration debt that wasn't there before the rollout because the during-rollout state was treated as temporary rather than as a design constraint. We design for both states explicitly.
Hurricane season is the dominant operational risk. How do you design integration for storm-mode behavior specifically?
With storm-mode as a first-class architecture concern, not a feature added later. Every integration pattern gets a storm-mode behavior specification: asynchronous queues with backpressure handling so producers don't cascade-fail when consumers are overwhelmed, degraded-mode fallbacks that preserve core functionality when components are struggling, event replay capability so data is never lost even if it's delayed, and observability that gives the operations center real visibility into what the integration layer is actually doing during the event. We also design for multi-week restoration — the integration patterns that hold for a three-day outage may not hold for a three-week one, and Ida is the recent reminder that multi-week restoration is a real requirement. Pre-hurricane-season operational readiness reviews (typically May or June) are when we validate that storm-mode behavior actually works under simulated load. Post-season (November) is when we review what actually happened and improve.
How does MSG coordinate with Entergy's enterprise architecture and shared services organization?
Explicitly and with clean scope boundaries. Enterprise architecture decisions for shared systems (CIS, AMI headend, core financials) are made at the corporate level across Entergy operating companies, and integration work in New Orleans has to respect those decisions rather than work around them. We coordinate directly with Entergy Services enterprise architecture, document interface contracts in writing, and keep the scope of New Orleans-specific work clearly distinguished from enterprise work. When New Orleans-specific integration surfaces a pattern that would benefit the broader Entergy footprint, we document it in a form that supports enterprise adoption. When enterprise decisions create constraints that limit what's achievable at the operating company level, we're honest about that rather than promising outcomes that aren't reachable. This collaborative model produces better results than either pretending the operating company exists in isolation or trying to impose New Orleans-specific solutions on the enterprise. Engagements that respect both cadences produce durable work; engagements that don't produce artifacts that fail enterprise review or operating-company scrutiny and have to be rebuilt.
Can you actually work MISO-facing integration, or is that outside your scope?
Yes, we work MISO-facing integration. Wholesale market integration is a distinct discipline from retail and distribution integration, with its own transaction flows, settlement cadence, and reliability coordination requirements. We audit the current flows: real-time telemetry, day-ahead and real-time market participation, transmission planning coordination, settlement ingestion and reconciliation, reliability coordinator interfaces, and the accounting and treasury integration downstream. We identify fragility points that are producing settlement risk or operational scrambling, and redesign patterns with cleaner contracts, better reconciliation logic, and observability that surfaces issues before they hit settlement deadlines. MISO-specific integration is work that demands engineering discipline plus market-specific knowledge, and we bring both. For a New Orleans engagement we'd coordinate closely with the operational and trading teams throughout. Settlement exposure is where fragile wholesale integration bleeds money quietly, and cleanup work often pays back within a single market cycle. The investment is measurable.
What's the realistic presence model for a New Orleans engagement from your Beaumont base?
More physical presence than most Texas engagements because the drive is shorter. Three and a half hours on I-10 makes New Orleans one of our most accessible markets. 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 pre-hurricane-season readiness reviews (June), through any active storm event during the engagement, and through post-season operational reviews (November). For a 12-month engagement we typically deliver 50-70 onsite days. We document the cadence upfront so everyone knows what presence to expect. The hurricane-season operational discipline is not something we treat as optional — it's baked into how we structure every New Orleans engagement. When a system forms in the Gulf, we're already inside the operations center because we planned for it months earlier, not scrambling to book flights.
Other Industries in New Orleans
Tech Integration in Other Cities
Other MSG Services
Ready to integrate your New Orleans utility stack with Council-grade discipline?
Let's audit the storm-mode patterns, the Council-facing reporting, and the MISO flows — then build integration that holds through the next Ida.