See what each startcosts in component life.

INSUS reconstructs what each start-up transient did to critical components from historian data you already hold, so cycling damage is visible while it is still a dispatch decision. Plant engineers keep the call.

  • 01

    Damage tracked per component, not per start count.

  • 02

    Ramp profiles evaluated inside OEM limits.

  • 03

    Advisory. The DCS keeps control of the ramp.

The problem

A duty cyclethe plant was not designed for.

Thermal units built for baseload now face starts, shutdowns and load changes as routine duty. Fuel cost is visible immediately; thermal and mechanical damage may only appear at a later inspection or forced outage. Counting starts is not the same as knowing what a particular ramp at a particular severity consumed in component life.

Two units with similar operating hours and different start histories
01
02
03
  • 01Different start histories
  • 02Different thermal severity
  • 03Different accumulated damage

The shift

From counting startsto costing them.

The start still happens when dispatch says it happens. What changes is knowing what it consumed, and where.

Today

The damage is deferred to a later inspection

  • Start cost is approximated from fuel and staff time.
  • Hot, warm and cold starts are treated as counts rather than severity profiles.
  • Ramp profiles are set for start time and procedure alone.

With INSUS

Every start carries a measurable damage profile

  • Start cost includes modelled cycling damage indicators.
  • Starts are differentiated by the thermal transients they actually imposed.
  • Ramp profiles can be evaluated against the time-versus-damage trade.

How it works

From transientsto accumulated damage.

This fits OptiStudio as decision support beside existing plant systems. Access is read-only. The DCS remains responsible for ramp control.

  1. Connect

    Bring transients and asset history together

    Connect high-resolution historian data from start-ups, shutdowns and load changes with outage history, inspection records and OEM limits where they exist.

  2. Understand

    Characterise the start that actually happened

    Analyse each transient against the unit's own history: temperature differentials, rates of change and load trajectories, rather than the nominal procedure alone.

  3. Predict

    Track damage accumulation by component

    Generate component-level damage indicators for critical equipment and project how accumulation could develop under an expected dispatch pattern.

  4. Advise

    Quantify the time-versus-damage trade

    Evaluate alternative ramp profiles, estimate relative damage by start type and show where damage is concentrating, within applicable OEM limits.

  5. Verify

    Reconcile the model with inspection findings

    Compare modelled damage concentration with actual inspection findings and repairs. Where they conflict, inspection takes precedence and the model is recalibrated.

Plant historian records of high-resolution temperature and load transients

Getting started

Start with one unitand the starts you already ran.

For thermal and combined-cycle plants on flexible duty. Delivered through OptiStudio as cycling decision support. Expert Services can help with data assessment and validation. Advisory and read-only. Historian resolution through start transients matters.

  • What we need. High-resolution transient data from the DCS and historian, start logs, component metal temperatures, inspection findings, outage history and OEM operating limits where available.
  • What you see first. One unit with a substantial start history and at least one major inspection record: historical starts reconstructed and compared with what the inspection found.
  • Where the limits are. Historian resolution and metal-temperature coverage bound confidence. This is not a remaining-life assessment and does not control the ramp. Recommendations stay inside OEM limits.
Explore OptiStudio

Questions plant engineers ask us

Cycling damage is incurred during a start but often surfaces years later. This use case tracks component-level damage indicators from actual transients and evaluates ramp profiles for engineering review.

High-resolution transient historian data, start logs, component metal temperatures, inspection findings and outage history. Adequate metal-temperature coverage matters; missing critical measurements lower confidence.

No. Formal remaining-life assessment involves engineering analysis, inspection evidence and OEM expertise. This informs operating and maintenance decisions between those assessments.

No. The DCS remains responsible for control. Plant engineering owns life, maintenance and operating decisions. Recommendations stay within OEM limits.

It can evaluate alternative ramp profiles and quantify the modelled trade between start time and damage. The operating decision stays with plant engineering and operations.

Through OptiStudio as cycling decision support. Expert Services can support data assessment, integration and validation with your plant team.

Historian resolution and temperature coverage bound the model. Inspection evidence is sparse. Published cycling-cost figures should not be treated as a cost estimate for your plant.

Power · Cycling and asset life

Two units, same hours. Very different wear.

Reconstruct one unit's cycling history from the data you already hold, then compare it with what your inspections actually found.