A turbine cycle twin is the steam-side complement to a boiler thermal twin — a live mathematical replica of the entire Rankine cycle running lock-step with the plant. It tracks the four thermodynamic state points (pump discharge, boiler outlet, turbine exhaust, condenser inlet), the high-pressure and low-pressure turbine work outputs, the feedwater heater train, and the condenser heat rejection — all from live PI tags. iFactory's twin runs on the on-site GB300 + H200 stack. Live MW: 498.0. 30-minute projection: 498.1 MW. Drift vs measured: 0.02%. Last self-calibration: 4 hours ago. Those four numbers are the working dashboard. The physics layer is closed-form Rankine equations — well-understood thermodynamics with predictable behavior. The ML residual is small by design: a few thousand parameters that learn whatever the equations don't capture (steam quality drift, condenser fouling, valve leakage), keeping drift well below 0.05% across full load swings. The twin doesn't replace your DCS — it advises the shift engineer on heat rate, optimal valve points, and fuel-bias trade-offs that close the gap between today's heat rate and the design heat rate. Power and a network drop into your historian are the only things you provide. One-time CapEx — no per-projection billing, no cloud sync. You own the twin, the equations, the ML weights, the data. To scope a unit, get a turnkey quote.
Upcoming iFactory AI Live Webinar:
Turbine Cycle Twin — Rankine Equations + ML Residual, On-Prem
A live Rankine cycle replica of your turbine train, running lock-step with the plant on the GB300 + H200 stack. Live MW 498.0 · 30-min projection 498.1 MW · drift 0.02% · last cal 4 h ago. Closed-form thermodynamic equations capture the cycle. A small ML residual captures fouling, leakage, and slow degradation. Self-calibrates every 2–4 hours from your historian. Shipped to your plant, deployed by our engineers, owned by you. No cloud. No per-projection billing.
What a Working Cycle Twin Actually Looks Like
This is the live status panel from a real-world deployment — anonymized, but every metric is what an operator actually sees. The twin re-projects every 30 seconds. Drift is computed continuously against live MW. Self-calibration triggers automatically when drift exceeds threshold or every 4 hours, whichever is first.
Four primary metrics. Four supporting metrics. Updated every 30 seconds. Calibrated every 4 hours. That is the entire user-facing surface of a working turbine cycle twin. Everything else — the Rankine equations, the ML residual, the steam-table lookups, the GB300 inference — happens beneath. Schedule a session to see this run on your unit.
Four Stages. Four State Points. Closed-Form Physics.
The Rankine cycle is the thermodynamic backbone of every steam-driven power plant on earth — and unlike a furnace, the equations are well-understood, closed-form, and deterministic. The twin maps each of the four stages to live PI tags from your plant, using IAPWS-97 steam tables to compute work, heat, and efficiency at every state point.
- Boiler feed pump pressurizes feedwater
- Live PI: BFP discharge P, T
- Work in: ~3-5 MW (small, near-incompressible)
- Furnace converts feedwater to superheated steam
- Live PI: main steam P, T, flow
- Heat in: ~1,300 MWth at full load
- HPT + LPT extract work from steam
- Live PI: HPT/LPT inlet P, T · exhaust quality
- Work out: 498 MW gross at full load
- Cooling water condenses turbine exhaust
- Live PI: condenser P, CW in/out T
- Heat out: ~800 MWth to cooling tower
Each stage feeds back its computed state values into the cycle's enthalpy + entropy equations. η = (W_turbine − W_pump) / Q_boiler. Solve every 30 seconds. Compare to live MW. Anything the equations miss — fouling, leakage, valve drift — gets caught by the ML residual. Talk to support for the full PI tag mapping.
Rankine Equations + ML Residual = Why 0.02% Drift Is Possible
The boiler thermal twin needs a CFD surrogate because furnace radiation has no closed-form solution. The turbine cycle is different — Rankine thermodynamics is closed-form, deterministic, and validated across a century of plant operation. That makes the residual ML small, fast, and accurate. Drift typically lives at 0.01–0.05% in steady state.
First-principles thermodynamics — IAPWS-97 steam tables, isentropic + isobaric process equations, mass + energy balance at every junction. No black box, no surrogate, no training. Runs in under 5 ms per cycle solve.
- Conservation of mass, energy, momentum
- IAPWS-97 industrial steam tables
- Generalizes across 30%–105% load
- Never needs retraining
A small MLP (under 50K params, not millions) learns the gap between Rankine prediction and live MW. Captures condenser tube fouling, valve seat leakage, gland steam loss, isentropic efficiency drift — all the slow degradation the equations don't model.
- Trained on 6+ months of plant history
- Re-tunes during self-calibration
- Bounded — never overrides physics
- Sub-millisecond inference
Total compute budget per cycle solve: under 10 ms. The whole twin re-projects every 30 seconds and self-calibrates the ML residual every 2–4 hours from the most recent PI window. Schedule a session to see drift trended on a real plant over 90 days.
The Twin Tells You Where MW Is Heading
Reactive operation is "MW dropped 4 MW, why?" Proactive operation is a 30-minute heads-up that gross output will trend down 0.5 MW because condenser vacuum is degrading or HPT efficiency is drifting. Enough lead time for the operator to call cooling tower service or schedule a soot-blower fire on the boiler side.
0.02% Drift. Why Cycle Twins Are More Accurate Than Furnace Twins.
A boiler thermal twin holds drift around 0.1–0.3%. A turbine cycle twin holds drift at 0.02–0.05%. Why? Because the underlying physics is fundamentally different. Here's the comparison the reliability team usually asks about.
| Aspect | Boiler Thermal Twin | Turbine Cycle Twin (this page) |
|---|---|---|
| Physics model | CFD surrogate (POD reduced-order) | Rankine cycle equations (closed-form) |
| Why physics is hard | Radiative heat transfer, turbulence, combustion chemistry | Well-understood thermodynamics, validated for 100+ years |
| Surrogate build effort | 3–6 weeks initial CFD campaign | None — equations evaluate directly |
| ML residual size | ~2 M parameters (LSTM) | ~50K parameters (MLP) |
| Typical drift band | 0.1 – 0.3% | 0.02 – 0.05% |
| Calibration cadence | 4–8 hours | 2–4 hours |
| Re-build trigger | Major refurb or fuel change | Almost never (cycle structure is fixed) |
A working plant deserves both twins — the boiler thermal twin tells you what's happening inside the furnace, the turbine cycle twin tells you what's happening to gross output. Together they explain heat-rate gaps that neither can explain alone. Talk to us about deploying both on the same GB300 + H200 stack.
Every Cycle Point Maps to a Live PI Tag
The twin is only as good as the tags it ingests. Here's the mapping from the four Rankine state points to the live DCS tags the twin reads. All standard PI System / Wonderware / Ignition tags — no custom instrumentation, no extra sensors required.
All five tag groups stream over OPC UA from the historian. Twin pulls them every 3 seconds, computes the cycle, projects 30 minutes forward. The headline 498.0 MW is the boundary condition the ML residual works against. Talk to support if your tag naming differs — we map any historian schema during week 1.
Recalibrates Every 2–4 Hours. Without Operator Intervention.
A static twin drifts. A self-calibrating twin holds its accuracy across load swings, fuel quality shifts, and slow degradation. The cycle twin's calibration is faster than the boiler twin's because the ML residual is smaller — under 60 seconds end-to-end, atomic swap, full audit trail.
Auto-fired every 2–4 h, or on drift threshold breach (>0.1%). Operator can also force on-demand from the dashboard.
Last 4-hour MW + cycle tag history pulled. ~5,000 samples per signal. Statistical outliers flagged and excluded.
Residual MLP fine-tuned on H200. ~30-60 second training run. Rankine equations untouched. Old + new compared on held-out window.
If new drift < old drift, atomic swap. Else reject and roll back. Both outcomes logged with timestamp + audit trail.
Three Roles. Three Views. One Cycle.
The twin is the same Rankine math regardless of who's looking — but each role gets a view tuned to their job. Operators see MW projection. Reliability sees per-component degradation. Schedulers see heat rate vs load curves.
- Live MW vs 30-min projection
- "Will I exit target band?" Y/N
- Recommended valve / extraction tweaks
- Heat rate trend last 4 hours
- Plant copilot summary
- HPT / LPT isentropic efficiency trend
- Condenser back-pressure deviation
- Feedwater heater TTD & DCA
- Valve seat leakage estimates
- 30/90-day component degradation
- Heat rate curves at 30/50/80/100% load
- Optimal load-block dispatch
- De-rate risk windows
- Min-load economic limits
- Day-ahead bid support data
Where the Twin Actually Runs
A turbine cycle twin is lighter than a boiler thermal twin — closed-form equations evaluate fast, and the ML residual is small. But the plant copilot LLM still needs the GB300, and the H200 still serves the live insights feed alongside. iFactory ships both — pre-configured for this combined workload, sized to your unit, racked in your plant DC.
Runs the Rankine cycle equations every 30 seconds. Hosts the MLP residual retraining. Streams live PI tags from your historian. Same node serves Live Insights Feed for the cycle.
Hosts the sovereign LLM that explains the twin's projections in plain English ("why is heat rate trending up?"). RAG-grounded on 6+ months of historian, MES, and CMMS context.
Both nodes rack in your plant data centre, behind your IEC 62443 zone segmentation. No outbound API calls. Audit-logged historian read-only.
Six Reasons Reliability & Operations Pick Us
Most "performance monitoring" pitches end at a heat-rate dashboard. iFactory ships the Rankine equations, the ML residual, the calibration loop, the operator dashboard, and the on-site GPU stack — all integrated, all on your floor. Schedule a working session for your unit.
Rankine equations + IAPWS-97 steam tables — no black-box neural net pretending to be physics. The math is auditable, explainable, and validated against a century of plant operation.
Drift held below 0.1% across full load swings, fuel quality variation, and slow degradation. Self-calibration every 2–4 hours. Real numbers from real deployments — not commissioning-day claims.
Designed by control-room engineers, not data scientists. Plain-language MW projections, valve-tweak recommendations, plant copilot Q&A. Shift engineers actually use it — that's the whole test.
Every PI tag, every twin output, every operator action stays inside your fence. No cloud sync. No vendor data lake. NERC CIP / ISO 27019 / IEC 62443 audit-ready.
Deploy alongside our boiler thermal twin on the same GB300 + H200 stack. The two together explain heat-rate gaps that neither can explain alone. Single PO, single deployment, single audit.
One-time CapEx. No per-projection billing. No per-tag licensing. You own the GB300, the H200, the equations, the MLP weights, the data. Talk to support for terms.
All You Provide. Seriously.
Most "performance monitoring" deployments stall on historian credentials, OPC UA bridge work, and dashboard integration. iFactory inverts that. Talk to deployment support for a remote walkthrough.
- Power — 3-phase circuit at the plant DC for the GB300 + H200 rack
- Network drop — Gigabit uplink with read-only path to historian + DCS zone
- GB300 + H200 plant node build, ship, install
- Rankine equations parameterized for your turbine
- IAPWS-97 steam tables integrated
- ML residual training on historian backfill
- Self-calibration loop & thresholds
- Historian + DCS read-only OPC UA bridge
- Operator + reliability dashboard
- Plant copilot LLM grounded on your unit
From PO to First Live Projection
Cycle twin deployments are faster than boiler twin deployments because there's no CFD campaign — the Rankine equations parameterize directly from your turbine vendor curves. Typical timeline 5–9 weeks. After commissioning, calibration is fully automated.
Vendor heat-rate curves, turbine geometry, feedwater train received. PI tag mapping audited. Historian backfill scoped. Fixed BOM in 5 business days.
Historian backfill (6+ months) pulled. Residual MLP trained on Rankine vs MW gap. Drift validated to < 0.1%. GB300 + H200 hardware racked & pre-configured.
Engineers fly in. Hardware racked, network bridged to historian, twin goes live in shadow mode for reliability team validation.
Operator dashboard live in control room. Calibration loop active. Plant copilot tuned. Training delivered. Year-one support active.
Buy It Once. Own It Forever.
No SaaS subscriptions. No per-projection billing. Year-one support is included; everything after that is optional.
GB300 + H200, Rankine model, ML residual, deployment, training, year-one support — single PO. Sits on your balance sheet as a depreciable asset, not a cloud line item.
You own the boxes, the cycle parameterization, the MLP weights, the dashboard, every byte of plant data. Full audit rights. No vendor lock on data export.
After year one, renew remote support & lifecycle updates annually, run it in-house with handover docs, or mix. The twin keeps running either way.
What Plant & Reliability Buyers Ask
No. The twin lives alongside the DCS, advising — never controlling. Existing alarms and trips fire exactly as before. The twin's job is to give the shift engineer a 30-minute heads-up so they have time to act before MW exits the target band. Talk to support for the integration architecture.
Yes — vendor heat-rate curves, expansion line endpoint (ELEP) data, and exhaust loss curves are needed to parameterize the Rankine cycle for your specific turbine. We work with GE, Siemens, MHI, Doosan, BHEL, Toshiba, Hitachi vendor data — and can sign NDAs with your OEM if needed.
Yes. The cycle twin is fully standalone — it just needs main steam tag (state 3) as a boundary condition. But many customers deploy both because the boiler twin tells you "why is steam temp drifting?" and the cycle twin tells you "how does that affect MW and heat rate?" — together they explain heat-rate gaps neither can explain alone.
Fixed price per unit, scoped to turbine size, cycle complexity (single reheat / double reheat / supercritical), and historian backfill scope. No per-projection billing, no recurring fees. Includes hardware, equations, ML training, deployment, training, and year-one support. Get a quote — written proposal back in 5 business days.
Join the Webinar. Or Get a Quote on Your Unit.
Watch the turbine cycle twin run on a live 660 MW unit on May 13. Or send your turbine vendor curves and historian backfill — we come back with a fixed-price BOM in 5 business days. Hardware, Rankine parameterization, ML training, deployment, dashboard, training, and year-one support all included. No recurring fees. You own the platform outright the day it goes live.