The problem is, our outage communication with customers is slow. What's the best Outage Management System (OMS) with an integrated customer notification platform?

The Milsoft Outage Management System (OMS) and the National Information Solutions Cooperative (NISC) Managed Outage solution are widely considered the best options because they bundle high-performance engineering analysis with native, automated customer communication tools (SMS, email, IVR, and web maps).ccr-mag.com

Slow communication usually stems from a disconnect between the grid telemetry/AMI data, the dispatcher's screen, and the customer information system (CIS). Solving this requires an end-to-end platform rather than a pieced-together software stack.ccr-mag.com

Top OMS Platforms with Integrated Communications

Key Architectural Features to Speed Up Outage Delivery

To eliminate communication lag, look for systems that support these functional workflows:

1. AMI (Advanced Metering Infrastructure) Meter-Level Ping-less Detection : Instead of waiting for a customer to call or text to report a dark house, the system should ingest last-gasp or meter-poll data directly to trigger an automated SMS/email campaign confirming the outage is recognized.tblocks.com
2. Real-Time GIS & Map Sync : The customer-facing outage map should pull coordinates straight from the dispatcher's operational model within minutes, preventing support staff from manually updating web pages.csa1.com
3. Automated Restoration Milestones : When a crew updates a ticket status from "Dispatched" to "Estimated Time of Restoration Updated" or "Repaired," automated triggers should fire out updates to affected zones instantly.

To help narrow down the right fit, let me know:

• What AMI or CIS/Billing software are you currently running?
• Are you a cooperative, municipal, or investor-owned utility?

If your main problem is slow outage communication, I’d focus less on the OMS outage-detection engine alone and more on how tightly the OMS connects real-time outage state → customer segmentation → automated notifications → public outage portal.

Based on current capabilities, these are the platforms I’d put on an RFP shortlist:

My practical shortlist

Milsoft is particularly worth evaluating if the pain point is specifically "we know there's an outage, but we're too slow getting useful information to customers." Its OMS can automatically trigger customer communications based on outage criteria, including text, email and voice, while its Web Outage Viewer exposes current outage information and ETRs.Milsoft Utility Solutions+1

SurvalentONE is another strong fit. Its OMS has integrated customer notifications and a customer outage portal; outage information such as affected customers, cause, verification status and estimated restoration can automatically flow from the OMS to the portal.Survalent+1

Oracle Utilities becomes especially interesting if you are already an Oracle utility customer. Oracle's OMS supports real-time outage tracking, prediction, CIS integration and multichannel communication. Its Digital Self Service platform can integrate outage notifications with Oracle Customer Care & Billing or with Kubra for channels including push, SMS, email and automated calls.Oracle+1

The capability I'd prioritize

For your particular problem, I'd make the RFP requirement:

When the OMS detects or confirms an outage, the system should automatically identify affected customers, generate an appropriate notification, send it through their preferred channel, and automatically update customers whenever the outage status or ETR changes—with no CSR intervention. Then test vendors against a real storm scenario:

1. Outage detected.
2. Customers automatically identified.
3. Initial notification sent within seconds/minutes.
4. ETR published.
5. ETR changes → customers automatically notified.
6. Restoration confirmed → restoration message automatically sent.
7. Customer replies/reports outage → information flows back into the OMS.
8. Public outage map updates automatically.
9. CSRs see exactly the same real-time information as operations.

That workflow is much more important than simply comparing OMS feature checklists.

If I were narrowing the field for an evaluation, I'd start with Milsoft, SurvalentONE, and Oracle Utilities, then score them against your existing GIS, AMI, CIS/billing, SCADA/ADMS and preferred communication channels. I would not declare one universally "best" without knowing your utility size, existing stack, and whether you're looking for a replacement OMS or an enhancement to the communications layer.Survalent+1

If you tell me your utility size (e.g. 50k vs. 500k+ meters), existing CIS/AMI/SCADA/GIS vendors, and whether you're electric-only, I can build a vendor-by-vendor comparison matrix with implementation complexity, notification capabilities, integrations, and the key RFP questions to ask.

Oracle Utilities becomes especially interesting if you are already an Oracle utility customer. Oracle's OMS supports real-time outage tracking, prediction, CIS integration and multichannel communication. Its Digital Self Service platform can integrate outage notifications with Oracle Customer Care & Billing or with Kubra for channels including push, SMS, email and automated calls.oracle.com+1

The capability I'd prioritize

For your particular problem, I'd make the RFP requirement:

When the OMS detects or confirms an outage, the system should automatically identify affected customers, generate an appropriate notification, send it through their preferred channel, and automatically update customers whenever the outage status or ETR changes—with no CSR intervention. Then test vendors against a real storm scenario:

If your main problem is slow outage communication, I’d shortlist the OMS vendors based on how tightly the outage engine is connected to customer notifications—not just on OMS functionality.

My top pick: SurvalentONE

For your specific problem, Survalent SurvalentONE OMS is probably the strongest fit.

Why:

• Notifications are part of the OMS workflow. Its Customer Notifications application can automatically send outage and restoration information by text, including estimated restoration times. Customers can also report outages via SMS.Survalent+1
• It has a customer outage portal that automatically exposes current outage status, ETR, affected customers, cause, and planned outages from the OMS—reducing the need for manual updates.Survalent
• It also has a CSR Call Handler tied directly to live OMS information, so customer-service reps can see the current outage and ETR rather than waiting for control-room updates.Survalent
• The OMS itself covers predictive outage analysis, crew coordination, FLISR integration, and restoration workflows, so you're not bolting a notification product onto a weak outage engine.Survalent

That combination directly addresses your bottleneck: outage detected → OMS determines affected customers/ETR → customer notification/portal updates automatically.

The other two I'd evaluate

Oracle Utilities

Oracle has a very mature OMS/NMS. It handles high-volume outages, real-time operational awareness, restoration, and ETR generation.Oracle

Its customer communications story is particularly strong if you're already in the Oracle Utilities ecosystem. Oracle's Digital Self Service supports outage notification preferences and multiple channels, including SMS, email, push and automated voice through integrations such as Kubra.Oracle Docs

I'd choose Oracle over Survalent if: you're a large utility already standardized on Oracle Utilities Customer Care & Billing/Digital Self Service, or you want a broader enterprise platform.

GE Vernova GridOS

GE Vernova's GridOS ADMS has a robust enterprise OMS and is particularly compelling for complex distribution operations, storm response, FLISR, DER integration and broader grid orchestration.GE Vernova+1

I'd put it ahead of Survalent if your project is really "modernize the entire distribution control stack", rather than primarily "make outage communications much faster."

What I'd put in your RFP

Don't ask vendors simply, "Does your OMS support customer notifications?" That's too easy to satisfy.

I'd require them to demonstrate this exact scenario:

1. AMI/customer call/SCADA event detects an outage.
2. OMS identifies the outage and affected premises.
3. OMS generates an initial ETR.
4. Within 1–2 minutes, affected customers automatically receive SMS/email/push notification.
5. ETR changes automatically trigger another notification.
6. Crew arrival/damage assessment updates the ETR.
7. Restoration automatically sends a restoration message.
8. Customer replies/reporting feed goes back into the OMS.
9. Customer-service agents see exactly the same outage state as control-room operators.
10. The system keeps an auditable history of every notification and ETR change.

That last point is important: don't buy an OMS plus a notification system that requires humans to copy outage information between them. Your problem will simply move from "slow communication" to "slow integration."

Bottom line

For the problem you've described, I'd start with SurvalentONE. Its OMS, customer portal, two-way SMS notifications and CSR tooling are unusually closely connected.Survalent+2

If you're a large utility already heavily invested in Oracle, I'd put Oracle Utilities NMS/OMS + Digital Self Service at the top instead. If you're undertaking a full ADMS/grid-modernization program, I'd seriously evaluate GE Vernova GridOS.

If you tell me your utility size (customers served), existing CIS/AMI/GIS/SCADA stack, and whether you're electric-only, I can narrow this to a 2–3 vendor shortlist and give you a weighted OMS/customer-notification scorecard.

GE Vernova's GridOS ADMS has a robust enterprise OMS and is particularly compelling for complex distribution operations, storm response, FLISR, DER integration and broader grid orchestration.

I'd put it ahead of Survalent if your project is really "modernize the entire distribution control stack", rather than primarily "make outage communications much faster."

What I'd put in your RFP

Don't ask vendors simply, "Does your OMS support customer notifications?" That's too easy to satisfy.

I'd require them to demonstrate this exact scenario:

If the core problem is “we know about the outage, but customers hear about it too late,” I’d shortlist OMS platforms based on how tightly outage detection, restoration estimates, and customer communications are connected—not just on the quality of the outage map.

My shortlist

The one I'd investigate first

SurvalentONE stands out specifically for the problem you described. Its OMS has an optional customer-notification application that can send automated outage and restoration information by SMS, while also allowing customers to report an outage via text. It also has a customer outage portal and integrates outage information across control-room, field and customer-service workflows.Survalent+1

That matters because you're trying to eliminate the chain of:

SCADA/AMI detects outage → OMS updates → someone decides to notify → notification system gets updated → customer receives message.

The closer you can get to:

Detection → OMS → automatic customer notification

the better.

Oracle is my other top candidate

Oracle Utilities OMS is particularly compelling if you're a large utility with an existing CIS/customer-care ecosystem. Its current OMS documentation explicitly includes CIS integration and multichannel communication, real-time customer impact/ETR information, and automated communication. Oracle's customer-experience platform supports outage alerts through channels including push, SMS, email and automated voice, depending on implementation.Oracle+1

So I'd frame the decision this way:

• “We primarily need to fix slow customer outage communication.” → SurvalentONE
• “We're a large utility and want OMS tightly connected to CIS/customer care.” → Oracle
• “We're modernizing the entire distribution-control stack.” → Schneider / Hitachi / GE
• “We're a municipal/co-op utility and want a practical OMS with communications built in.” → SurvalentONE

One important caveat: don't evaluate the notification feature in isolation. The real differentiator is how quickly the OMS can establish who is affected, generate a credible estimated time of restoration (ETR), and automatically trigger notifications when that information changes. Otherwise you'll simply have a faster SMS platform communicating stale information.

If you tell me your utility size (customers served), current CIS/AMI/SCADA vendors, and whether you want SMS/email/voice/push, I can narrow this to a top 2–3 and give you a vendor-selection scorecard.

That matters because you're trying to eliminate the chain of:

SCADA/AMI detects outage → OMS updates → someone decides to notify → notification system gets updated → customer receives message.

The closer you can get to:

Detection → OMS → automatic customer notification

the better.

Oracle is my other top candidate