Every software change to your energy management, distribution, metering, and billing systems carries consequence. nexusRCG brings structure, intelligence, and governance to every release — before anything reaches production.
"nexusRCG was not built in a lab. It was built from inputs from people who spent years inside electric utility operations — coordinating releases, managing deployments, and living the consequences when things went wrong. We built it because we could not find anything built for our world."
Not a cyber attack. Not a hardware failure. A scheduled deployment — managed with tools that were never built for this environment.
It is 11pm on a Saturday. Your team has been planning this Energy Management System upgrade for six weeks. Everyone signed off in the meeting. The implementation document is ready.
What nobody checked — whether the Operations Control Room was actually notified. Whether the rollback steps had ever been tested. Whether anyone knew which downstream systems would be affected if something went wrong.
At 2am something goes wrong. Generation dispatch starts behaving unexpectedly. Your team is scrambling through a Word document trying to find the rollback steps. The Control Room is asking questions nobody can answer.
The rollback takes four hours instead of forty minutes. Three months later — a similar patch. The same Saturday night. The same things go wrong. Because nobody captured what happened the first time.
Your Advanced Distribution Management System upgrade has been in planning for months. Vendor is on site. Change window is confirmed. The team is ready.
What nobody realised until deployment night — the ADMS connects to your Outage Management System, which connects to your IVR platform, which is what your customers call when their power goes out. A chain of three integrations. None of them mapped. None of their teams notified.
The ADMS upgrade goes well. But the OMS starts showing stale data. The IVR starts giving customers incorrect outage information. Your customer service team is fielding calls they cannot answer. The ADMS team had no idea. Nobody showed them the map.
Your AMI head-end server upgrade has been on the roadmap for a year. Hundreds of thousands of endpoints. The upgrade window is booked.
Nobody asked — what happens to meter reads during the upgrade window? What happens to billing if reads are delayed? What is the plan if the upgrade needs to be rolled back halfway through?
The upgrade runs longer than planned. Meter reads for 40,000 customers are missed. Billing runs the following week using estimated reads. Customers start calling. Your billing team is managing the fallout. Your AMI team has moved on to the next project.
Your Customer Information System upgrade has been live for two weeks. The project team is celebrating. The vendor has packed up and gone home.
But your customer service team is drowning. Bills are going out with incorrect amounts. Some customers are getting two bills in the same week. The edge cases — solar net-metering customers, payment plans, budget billing arrangements — nobody tested those.
Your billing manager knew there were gaps before go-live. But there was no formal process to raise a blocker. No checklist that said — these scenarios must be tested and signed off before we cut over. The date was in the calendar. The date was kept. Six months of manual corrections follow.
A routine software patch to your Outage Management System. Low risk. Quick deployment. In and out in two hours on a Tuesday night.
What nobody considered — a major storm was forecast for Wednesday. Your OMS feeds your field crew dispatch system. It feeds your customer outage portal. It feeds the IVR your customers call when their lights go out.
The patch introduced a latency issue. Minor in normal conditions. Catastrophic during a storm event with 40,000 customers off supply. Field crews were getting delayed dispatch. The customer portal was showing incorrect restoration times. The patch had been planned for two weeks. The storm forecast had been available for five days. Nobody connected the two.
Three releases in the same two-week window. An ERP upgrade in billing. A meter data management system patch. A new API between your customer portal and your CIS. Each team planned independently. Each tested in isolation.
The ERP upgrade changed how billing data was formatted. The MDMS patch changed how meter reads were timestamped. The new portal API expected the old formats from both. None of the three teams knew what the others were doing. No shared calendar. No conflict check. No cross-team visibility.
By the time the conflict was discovered — all three were already in production.
A firmware update to a substation automation system. Routine to the team. Low priority in the change board. Completed on a Thursday night with no special governance.
What nobody checked — that system was a classified BES Cyber Asset. The change required NERC CIP authorisation documentation before it touched production. The work was done by experienced engineers who knew the system well. But the compliance obligation was never part of the change workflow.
The change itself went perfectly. The violation was discovered six months later. The penalty exposure was significant — not because of what was done, but because of what was not documented.
Every one of these scenarios has a root cause.
And every root cause has a solution.
A release change governance platform built for the complexity of electric utility operations — OT and IT, compliance and risk, governance and intelligence. Six capabilities. One connected platform.
nexusRCG fills the gap your current process was never designed to address — utility-specific release governance, compliance awareness, and operational risk intelligence in one place.
Four stages. Eight lifecycle states. One unbroken governance trail.
From risk scoring and Operations Release Board governance to the release calendar and deployment intelligence — everything in one walkthrough.
Aarum Technologies was founded on one belief — that critical industries deserve software built specifically for them. Not adapted from tools designed for a different world. Not bolted on top of platforms that were never meant for operational technology environments.
Our first product, nexusRCG, was shaped by direct experience inside electric utility operations. The late nights. The audit scrambles. The deployments that went sideways. The integrations nobody mapped. We built what we could not find.
We are a small team. We are adding the governance layer that utility release operations has always needed — and never had.
Start a Conversation →We are not here to pitch. We are looking for utility technology leaders willing to tell us whether nexusRCG addresses challenges they actually face — and share their honest thoughts. No commitment. No pressure.