Blast Furnace Hot Stove — Dome Temperature, Checker Condition & Combustion AI

Why Fixed Firing Schedules Leave Hot Blast Temperature on the Table

Most stove batteries rotate through firing, blast, and heating phases on a schedule designed around conservative dome temperature limits set to protect the weakest checker zone in the weakest stove. That approach is safe, but it means every stove in the battery is firing to the limit of its worst-performing neighbor rather than its own actual condition.

This conservatism compounds as a stove battery ages. Stoves commissioned together on the same schedule inevitably diverge in condition — one stove might see slightly more dust carryover, another might have a hotter burner zone, and a third might simply have accumulated more operating cycles due to rotation sequencing quirks. Over a multi-year campaign, these small differences add up to a meaningful spread in real capability, yet the firing schedule usually treats every stove as if it still matches its neighbors exactly as it did at commissioning.

How iFactory Models Combustion and Checker Performance Together

Hot stove performance is really three connected problems — combustion efficiency, checker heat transfer, and dome temperature management — that are usually monitored and adjusted separately by different teams. iFactory brings these together into a single per-stove performance model. Talk to a process engineer about how the combustion model is calibrated for your specific stove design.

Why Fixed-Schedule Firing Falls Short Compared to Model-Guided Firing

The gap between fixed firing schedules and a per-stove combustion model widens over a campaign, as checker condition and refractory wear diverge between stoves that started out identical.

These comparisons reflect relative performance scores observed across stove batteries before and after moving from fixed schedules to model-guided firing recommendations, based on deployment data across multiple furnace operations.

The Real Cost of Treating Checker Fouling as a Refractory Problem Only

Checker fouling is usually discussed as a refractory maintenance issue — something to plan for at the next reline. That framing misses how much of the cost shows up long before any physical checker replacement happens. As checker heat transfer efficiency declines, the stove needs more firing time to reach the same dome temperature, which increases fuel consumption per cycle. To compensate, some operations extend firing phases at the expense of blast phase duration, which in turn can affect hot blast temperature consistency delivered to the furnace.

None of this shows up as a single dramatic event. It shows up as a slow upward creep in fuel consumption per tonne of hot metal and a slow downward drift in average hot blast temperature, both of which are easy to attribute to other causes — burden quality, ambient conditions, coke rate targets — unless someone is specifically isolating checker heat transfer efficiency as its own variable. Process engineers reviewing monthly fuel consumption reports often see the aggregate trend without the stove-level detail needed to trace it back to a specific checker's condition.

This is also where campaign life planning intersects with day-to-day combustion tuning. A stove firing harder than its checker condition can sustain is accumulating thermal stress that shortens refractory life, even if hot blast temperature targets are being met in the short term. Being able to see checker heat transfer efficiency and thermal stress accumulation side by side with firing decisions gives process engineers the information needed to balance near-term production targets against long-term campaign life — a tradeoff that is difficult to manage well without stove-level visibility.

What Process Engineers Get Access To

iFactory's hot stove combustion platform is built around the specific decisions process engineers make daily and weekly — firing schedule adjustments, rotation sequencing, and campaign life tradeoffs — rather than presenting raw sensor data that still requires manual interpretation.

Deployment Timeline for Hot Stove Combustion Analytics

iFactory deploys against existing dome temperature, flue gas, and blast air instrumentation already present on most stove batteries. No internal checker instrumentation is required.

Fits Into Existing Instrumentation and Control Systems

iFactory connects to the DCS platforms and combustion control systems already running most stove batteries, including Honeywell, Siemens, and Emerson environments, using standard OPC-UA and Modbus connectivity. There is no requirement to replace burner management systems, dome temperature transmitters, or flue gas analyzers already in place.

For process engineers, this means the historical data used to build the per-stove model comes from your own equipment's operating history rather than a generic industry benchmark. That historical grounding is part of why recommendations tend to align closely with what an experienced stove operator would recognize as sound firing practice, just applied with more consistency and more advance warning than manual trend review allows across a full battery on a rotating shift schedule.

Results from Stove Batteries Running iFactory Combustion Analytics

The following outcomes reflect process engineering teams that adopted per-stove combustion modeling in place of fixed battery-wide firing schedules. Request the full performance data for a stove design comparable to yours.

Frequently Asked Questions