An S&OP process for a power generation company brings fuel, maintenance and dispatch planning into one monthly decision cycle. Sales and operations planning is a manufacturing method, but the problem it solves is familiar to every genco: three teams plan separately, and the conflicts only appear when it is too late to avoid them. An outage lands in a peak month, or coal stock runs low just as demand rises. This guide shows how to adapt the method to generation, step by step. To see a shared planning view for your fleet, book a short walkthrough.
Building an S&OP Process for Power Generation Companies: One Plan for Fuel, Maintenance and Dispatch
A monthly cycle that puts fuel, outage and dispatch plans on one page, finds the conflicts early and gives leaders a clear decision to make.
Five steps each month, ending with decisions by senior leaders.
Fuel, maintenance and dispatch usually sit in separate teams and files.
An outage against a demand peak, or a fuel shortfall before a high-load month.
Everyone works from the same forecast, the same outage dates and the same stock position.
What Is S&OP, and Does It Apply to Power Generation?
Sales and operations planning is a monthly process that balances demand and supply and ties both to the financial plan.
A monthly, cross-functional planning cycle. Each function refreshes its plan, the gaps are worked through together, and senior leaders approve one agreed plan.
- Demand side. For a genco, this is the dispatch forecast: how much the grid or customers will take.
- Supply side. Unit availability, which depends on maintenance, and fuel, which depends on supply and logistics.
- Finance. Revenue, fuel cost and penalties that follow from the combined plan.
The method fits because the structure is the same: several plans that depend on each other and must agree. We can map it to your planning calendar on a call.
Planning in Silos: Fuel, Maintenance, Dispatch
Each team makes a sensible plan on its own. The trouble starts where the plans meet.
Works from a generation forecast that may be weeks old.
Fixes dates around contractors and parts, not always around demand.
Assumes units and fuel will be there.
Sees the effect only when results arrive.
| Conflict | How it happens | What it costs |
|---|---|---|
| Outage in a peak month | Outage dates set before the demand forecast was revised | Lost generation when it is worth most |
| Fuel short before high load | Fuel plan based on last quarter’s dispatch view | Units backed down or stock run below norm |
| Too much fuel during an outage | Deliveries not adjusted for a unit being offline | Stockyard congestion and carrying cost |
| Two units out together | Plants plan separately | Fleet availability falls below commitment |
None of these needs new technology to prevent. They need the three plans on one page, reviewed together. See what that looks like in a demo.
Why Coordination Matters More Now
Availability rules, tight scheduling and thin fuel stocks all reward gencos whose plans line up.
average coal stock at Indian thermal plants in September 2026, with 60% of 190 plants holding less than a week. Consumption had grown 8% while receipts grew 3%.
When stocks are this thin, a fuel plan that lags the dispatch plan by even a few weeks can leave a unit short. The same is true of an outage that overruns into a high-demand period.
A monthly cycle keeps the three plans in step. Our specialists can show where yours diverge today.
The Five-Step Monthly Cycle, Adapted for a Genco
The standard S&OP cycle has five steps. Each maps cleanly to generation planning.
Close last month: generation, availability, fuel receipts, stock.
Refresh the dispatch forecast by unit and month.
Refresh outage and fuel plans against it.
Find the conflicts; prepare options.
Decide; approve one plan.
| Step | Who leads | Main output |
|---|---|---|
| Data review | Performance team | Plan against actual for the month |
| Demand review | Commercial and scheduling | Dispatch forecast for 18 months |
| Supply review | Outage and fuel planning | Outage calendar and fuel plan |
| Pre-meeting | Planning head | List of gaps with costed options |
| Executive meeting | Senior leadership | Approved plan and decisions |
The discipline is the calendar. Each step happens in the same week every month, so the executive meeting always has fresh numbers.
A first cycle can run on existing data. We set up the calendar and views in every rollout.
How S&OP Fits With Other Planning Horizons
S&OP covers the middle ground between daily scheduling and long-range resource planning.
| Process | Horizon | Decides |
|---|---|---|
| Day-ahead scheduling | Next day, in 15-minute blocks | Unit commitment and declared capability |
| S&OP or integrated planning | Rolling 18 months, reviewed monthly | Outage timing, fuel plan, generation targets |
| Annual outage and load plan | One year | Regional outage schedule; in India, the LGBR prepared with the Regional Power Committees |
| Integrated business planning | 24 to 36 months | Adds financial and strategic reviews |
| Integrated resource plan | 10 to 20 years | New capacity and retirements |
Integrated business planning is the later, wider form developed by Oliver Wight in 2005. It adds strategy and finance reviews and looks further ahead.
Most gencos already have the top and bottom rows. The monthly middle layer is the usual gap. Ask our team how it connects to both.
What Goes on the Shared View
The whole process rests on one page that every function recognises as true.
Illustrative. A dip like November’s is the kind of gap the pre-meeting should resolve.
Days of stock, outage dates and forecast load on one chart make conflicts obvious. See yours in a session.
Testing a Decision Before the Meeting
The pre-meeting should bring options with numbers, not problems.
Illustrative. Real options should carry revenue, fuel and contractor costs.
- Bring two or three options. Including doing nothing.
- Show the cost of each. In the same units, so they can be compared.
- Name the constraint. Contractor dates, grid approval or parts.
Scenario tools make this quick. Our engineers can set up the common cases.
Who Does What
Clear ownership keeps the cycle running when people are busy.
| Role | Responsibility |
|---|---|
| Process owner | Runs the calendar and the pre-meeting; usually the planning head |
| Commercial lead | Owns the dispatch forecast |
| Outage planning lead | Owns the outage calendar |
| Fuel lead | Owns the fuel and logistics plan |
| Finance lead | Translates the plan into revenue and cost |
| Plant heads | Confirm unit capability and risks |
| Executive sponsor | Chairs the decision meeting and settles trade-offs |
The executive sponsor matters most. Without someone able to settle a trade-off between functions, the meeting becomes a status report.
A one-page charter with these names is a good first deliverable. Discuss it with our advisors.
How to Tell if It Is Working
A few plan-against-actual measures show whether the cycle is improving decisions.
Illustrative values. The lowest ring is the first topic for next month’s review.
- Forecast accuracy. Dispatch forecast against actual generation.
- Outage adherence. Start date and duration against plan.
- Fuel plan adherence. Receipts and stock days against plan.
- Availability. Declared availability against target.
- Late changes. How many plan changes were made inside the month.
Published S&OP benefit figures come from manufacturing and should not be read across to power. Measure your own baseline and track it.
Fewer late changes is usually the first visible sign. We set up the measures in a working session.
Siloed Planning vs an Integrated Cycle
The difference shows in how surprises are handled.
- Three plans in three files
- Conflicts found when they happen
- Each team defends its own plan
- Leaders hear about problems late
- Finance sees results after the month
- One shared view
- Conflicts found months ahead
- Options prepared together
- Leaders decide on trade-offs
- Finance sees the effect of each option
The change is in behaviour more than tools: a fixed calendar and a habit of bringing options. A pilot on one plant shows it in practice.
Common Pitfalls
Most failed attempts share a few causes.
- No executive time. If leaders skip the meeting, decisions drift back to the silos.
- Too much detail. The review should look at months and units, not hours and valves.
- Different numbers. If teams bring their own figures, the meeting argues about data.
- No options. Presenting a gap without a proposal wastes the meeting.
- Looking backward. Spend most of the time on the next three to eighteen months.
- Treating it as a report. The output is a decision, not a slide pack.
Start small: one plant, three plans, one meeting a month. Scope it with a planning review.
How iFactory Supports Integrated Planning
iFactory puts dispatch, outage and fuel plans on one view and highlights where they disagree.
Dispatch, outages and fuel by unit and month.
Flags outages against peaks and low stock.
Options side by side with their effects.
Refreshed from plant and ERP data.
Gaps, options and decisions in one place.
Answers planning questions in plain language.
It runs on premises and links to your scheduling, CMMS and ERP data. Share three plans and we will show the first conflicts in a trial.
See Where Your Three Plans Disagree
Share your dispatch forecast, outage calendar and fuel plan. We put them on one view and list the conflicts for the next 12 months.
The Unit 3 overhaul starts on the 4th, in the same week the dispatch forecast peaks and coal receipts are planned to be lowest. Moving it two weeks avoids both conflicts.
An Outage, a Peak and a Fuel Dip in the Same Week
This is how a planning head might prepare for the monthly review.
iFactory ships as a pre-configured NVIDIA AI server, racked and ready with the integrated planning models loaded. Rack it, plug in power and Ethernet, and the AI is live. Scope covers data connections across units, control room, stores and planning office, DCS, historian, CMMS and ERP integration, cabling and network setup, team training and 24×7 remote monitoring.
Server installed, DCS, historian and CMMS links live, history loaded.
Models tuned on your own plant data, then piloted on one unit with your team reviewing every output.
Rollout to the agreed units, team training done, 24×7 remote monitoring in place.
Software, server and integration come as one package. For pricing, contact our sales team.
Frequently Asked Questions
A monthly planning cycle that brings dispatch, maintenance and fuel plans together, finds conflicts and ends with one plan approved by senior leaders. Gencos often call it integrated planning.
The term comes from manufacturing and is not standard in power. The principles apply well, because generation also depends on several plans that must agree.
Data review, demand review, supply review, a pre-meeting to resolve gaps, and an executive meeting to decide.
Typically a rolling 18 months, reviewed every month. Integrated business planning extends this to 24 to 36 months.
A planning head usually runs it, with an executive sponsor who chairs the decision meeting and settles trade-offs between functions.
A shared view and a first monthly cycle on one plant typically fit within a 6–12 week rollout. Plan it with our specialists.
Put Fuel, Maintenance and Dispatch on One Plan
iFactory brings the three plans into one view, flags conflicts months ahead and prepares the options for your monthly review.
Illustrative. Each bar shows actual as a share of plan; the lowest one is the first agenda item.
