Rate Analyst
Modeling revenue requirements and forecasting
What You Do Today
Project the utility's revenue needs — operating costs, capital costs, return on investment — and determine how much total revenue rates must recover.
AI That Applies
AI generates revenue requirement projections from financial data, models scenarios with different capital plans and cost assumptions, and identifies key drivers of revenue need changes.
Technologies
How It Works
The system pulls financial data from operational systems — transactions, forecasts, actuals, and variance history. Predictive models decompose the historical pattern into trend, seasonal, and event-driven components, then project each forward while incorporating leading indicators from external data. The output — revenue requirement projections from financial data — surfaces in the existing workflow where the practitioner can review and act on it.
What Changes
Scenario modeling is fast and flexible. You explore more 'what-if' scenarios and present a richer picture of revenue requirement drivers.
What Stays
The assumptions behind the model — load growth, capital spending, inflation, regulatory treatment — are human decisions informed by judgment and policy.
What To Do Next
This section won't tell you what your numbers should be. It will show you how to find them yourself. Every instruction below produces a real, verifiable result in your organization. No benchmarks, no projections — just the steps to build your own evidence.
Establish Your Baseline
Know where you are before you move
Before adopting AI tools for modeling revenue requirements and forecasting, understand your current state.
Without a baseline, you can't measure whether AI actually improved anything. You'll adopt tools without knowing if they're working.
Define Your Measures
What to track and how to calculate it
Time per cycle
How to calculate
Measure how long modeling revenue requirements and forecasting takes end-to-end today, then after AI adoption.
Why it matters
The most visible improvement is speed. If AI doesn't save time, question whether it's adding value.
Quality of output
How to calculate
Track error rates, rework frequency, or stakeholder satisfaction scores before and after.
Why it matters
Speed without quality is just faster mistakes. Measure both.
Start These Conversations
Who to talk to and what to ask
your VP Operations or COO
“What's the current accuracy of our forecasting, and how would we know if an AI model is actually better?”
They're prioritizing which operational processes to automate
your process improvement or lean lead
“Which historical data do we have that's clean enough to train a prediction model on?”
They understand the workflow dependencies that AI tools need to respect
Check Your Prerequisites
Confirm readiness before you invest
Check items as you confirm them.