← All insights

AI & Data

Beyond OUAF: applying AI to bill estimation without customization

How a focused AI layer delivers estimation and payment reminders independently of OUAF. It is quicker to deploy, simpler to scale and free of customization debt.

March 2026 · 6 min · AI & Data Lead

Most utilities do not have an AI problem. They have a manual-exception problem that looks like a candidate for AI. Estimated reads, missed payments, usage anomalies, each pulls a person into a queue, and the queues never get shorter. The interesting question is not "where can we add intelligence," but "where is a person doing work a model could do reliably."

Why not just build it into OUAF?

The obvious path is to extend the Oracle Utilities Application Framework directly. It is also the path that quietly accumulates the most cost. Every customization inside OUAF is something to regression-test at each quarterly release and to carry through every future upgrade. For capability that sits slightly to the side of core billing, estimation, reminders, anomaly flags, that is a heavy price for the convenience of proximity.

The alternative is to run the AI layer alongside OUAF rather than inside it. It consumes the same data, returns results through standard integration points, and stays out of the upgrade path. The billing engine does what it does best; the model handles the judgment calls that used to land on a person's desk.

The goal is not a smarter platform. It is a billing team that no longer spends its week on exceptions a model can clear.
  • Bill estimation where reads are missing or implausible
  • Payment-reminder timing tuned to actual customer behavior
  • Usage anomaly detection that flags revenue leakage early

What "customization-free" actually buys you

Keeping the model outside OUAF is not an aesthetic preference. It means the capability can be deployed in weeks rather than a release cycle, scaled across utilities without re-customizing each one, and upgraded on its own schedule. When the core platform takes its next quarterly drop, nothing in the AI layer has to be retested against it. That separation is the entire point.

Used this way, AI in utilities is unglamorous and effective, which is exactly how mission-critical systems should adopt it.

Have a system you can't afford to get wrong? That's the kind of work we were built for.

Start a conversation