10 Real-Time KPIs Every Carbon Capture and Storage Operations Leader Should Be Tracking

Carbon Capture and Storage

Dawn at a CO2 conditioning and injection terminal, where the columns hold compressed CO2 inside a narrow phase envelope. Operators walking the unit work to the same purity, pressure, and fugitive readings the control room is tracking in real time, because any drift here lands at the wellhead within minutes.

A Carbon Capture and Storage (CCS) operation is judged by what stays underground. Everything upstream of that, from the absorber column to the wellhead, exists to make sure the molecule you captured doesn’t end up back in the atmosphere or pooling somewhere it shouldn’t.

The chain is long: capture, conditioning, compression, transport, injection, storage. A problem at any point eventually shows up at every other point. Run blind for a shift and you risk an off-spec product entering a pipeline, missed tonnage commitments, or an induced seismic event that nobody flagged until it ended up on a regulator’s desk. Here are the ten real-time KPIs every CCS Operations Leader should have on the wall.

CO2 Capture Rate

  • Why it Matters: Capture rate drives every downstream metric. It defines whether the facility meets emissions targets, tonnage commitments, and credit obligations.
  • What it Measures: The percentage of CO2 removed from the inlet flue gas versus what slips through the absorber overhead vent.
  • What Happens if Missed: Slipping below target releases unaccounted CO2, jeopardizes 45Q credits, and forces costly solvent and steam corrections downstream.
  • Formula: (CO2 in – CO2 out) / CO2 in × 100
  • Indicator Type: Current. It reflects live capture performance and reacts within minutes to load swings or solvent degradation.
  • Unit of Measure: Percent (%)
  • Ideal Visualization(s): KPI blocks, KPI trend with real-time alerts, SPC trend (control chart)
  • Frequency: Real-time
  • Data Required: Inlet flue gas CO2 concentration, outlet vent CO2 concentration, inlet flow rate, outlet flow rate
  • Pro Tip: Run capture rate alongside reboiler duty on the same screen. The two move together, and the relationship exposes solvent health early.
  • Red Flag: Capture rate drifting down while reboiler duty climbs signals amine degradation, foaming, or fouling building inside the absorber.

Specific Reboiler Duty

  • Why it Matters: Reboiler duty is the largest energy cost in amine-based capture. Small drifts compound into millions of dollars across a year.
  • What it Measures: Thermal energy delivered to the reboiler per tonne of CO2 captured, expressed in gigajoules per tonne.
  • What Happens if Missed: Rising duty erodes margins, increases parasitic load on the host plant, and signals solvent or column problems forming underneath.
  • Formula: Reboiler heat input (GJ) / CO2 captured (tonnes)
  • Indicator Type: Current. It tracks energy efficiency continuously and surfaces creeping degradation before it shows up on the operating bill.
  • Unit of Measure: GJ per tonne CO2
  • Ideal Visualization(s): KPI blocks, KPI trend with real-time alerts, Histogram
  • Frequency: Real-time
  • Data Required: Steam flow to reboiler, steam enthalpy, condensate return rate, CO2 production rate
  • Pro Tip: Benchmark against commissioning baseline weekly. The first 0.1 GJ per tonne of drift is the cheapest one to investigate.
  • Red Flag: Duty rising with stable capture rate usually means heat exchanger fouling or solvent contamination, not a real load change.

CO2 Product Stream Purity

  • Why it Matters: Off-spec CO2 corrodes pipelines, damages compressors, and threatens injection well integrity. Specifications exist for hard physical reasons.
  • What it Measures: Concentration of CO2 in the compressed product stream, plus impurity levels including water, oxygen, H2S, SOx, and NOx.
  • What Happens if Missed: Wet or oxygenated CO2 accelerates pipeline corrosion. Shutting down transport for cleanup costs more than continuous inline monitoring.
  • Formula: N/A
  • Indicator Type: Current. Product analyzers run continuously, and any deviation cascades into transport and storage systems within minutes.
  • Unit of Measure: mol % (CO2), ppm (impurities)
  • Ideal Visualization(s): KPI blocks, KPI trend with real-time alerts, Tables
  • Frequency: Real-time
  • Data Required: Product stream CO2 concentration, H2O content, O2 content, H2S content, SOx and NOx levels
  • Pro Tip: Track moisture and oxygen on the same trend. Most pipeline operators treat these two as the gating impurities.
  • Red Flag: A sudden rise in moisture downstream of dehydration almost always means glycol carryover or a desiccant bed breakthrough.

CO2 Injection Rate

  • Why it Matters: Injection rate is the throughput number that ties storage commitments, capture-side production, and credit volumes together in one place.
  • What it Measures: Mass flow of CO2 entering the injection well at the wellhead, reconciled against allocation across the storage complex.
  • What Happens if Missed: Under-injection stalls upstream production and burns inventory. Over-injection risks exceeding permitted pressures and triggering regulatory review.
  • Formula: Cumulative mass flow / time period
  • Indicator Type: Current. It reflects active injection conditions and ties directly to pipeline throughput and capture-side production.
  • Unit of Measure: Tonnes per day (or tonnes per hour)
  • Ideal Visualization(s): KPI blocks, KPI trend with real-time alerts, Pareto chart when ranking wells by deviation from target, Group rollup bars
  • Frequency: Real-time
  • Data Required: Wellhead mass flow, wellhead pressure, wellhead temperature, injection valve position
  • Pro Tip: Plot actual rate against permit limits and target curve on the same chart. Operators stop second-guessing each other when both are visible.
  • Red Flag: Injection rate stable but wellhead pressure climbing fast usually points to near-wellbore plugging, not reservoir filling.

Bottomhole Pressure

  • Why it Matters: Bottomhole pressure defines the operating envelope for the entire storage complex. Exceed it, and you risk fracturing caprock or inducing seismicity.
  • What it Measures: Pressure measured downhole at injection depth, indicating reservoir response to cumulative CO2 placement over time.
  • What Happens if Missed: Pressure approaching fracture gradient invites induced seismicity, caprock breach, or regulatory suspension of the injection license.
  • Formula: N/A
  • Indicator Type: Leading. Rising bottomhole pressure signals approaching limits well before any surface metric catches up.
  • Unit of Measure: PSI or kPa
  • Ideal Visualization(s): KPI blocks, KPI trend with real-time alerts, SPC trend (control chart)
  • Frequency: Real-time
  • Data Required: Downhole pressure gauge readings, cumulative injected volume, reservoir temperature, injection rate
  • Pro Tip: Plot bottomhole pressure against cumulative tonnes injected. The slope tells you whether storage capacity behaves the way the model predicted.
  • Red Flag: A sudden non-linear jump in bottomhole pressure with no change in injection rate signals near-wellbore damage or reservoir compartmentalization.

Wellhead Annulus Pressure

  • Why it Matters: Annulus pressure is the earliest indicator of compromised well integrity. A casing leak in a CO2 well is not a minor event.
  • What it Measures: Pressure inside the annular space between casing strings, normally stable and tracked continuously against the established baseline.
  • What Happens if Missed: Undetected annular communication can vent CO2 into shallow zones or surface, triggering containment failure and mandatory remediation work.
  • Formula: N/A
  • Indicator Type: Leading. Annulus deviations precede visible leaks and offer the earliest possible warning of mechanical integrity loss.
  • Unit of Measure: PSI or kPa
  • Ideal Visualization(s): KPI blocks, KPI trend with real-time alerts, Pareto chart when ranking wells by deviation from baseline
  • Frequency: Real-time
  • Data Required: A-annulus pressure, B-annulus pressure, tubing pressure, ambient temperature
  • Pro Tip: Set narrow deviation alerts during early well life. A 50 psi drift in a new well is more informative than a wide static limit.
  • Red Flag: Annulus pressure tracking tubing pressure in real time means direct communication, which is active well integrity loss.

Microseismic Event Rate and Magnitude

  • Why it Matters: Induced seismicity is the regulatory and public-perception risk that ends CCS projects. Catching small events early prevents larger ones.
  • What it Measures: Rate, location, and magnitude of microseismic events detected within and around the storage complex by the monitoring array.
  • What Happens if Missed: Unmonitored event clustering can escalate to felt seismic activity, triggering injection halts, lawsuits, and erosion of the operating license.
  • Formula: N/A
  • Indicator Type: Leading. Microseismic patterns shift before macroseismic events occur, giving operators time to throttle injection or pause.
  • Unit of Measure: Event count and Moment Magnitude (Mw)
  • Ideal Visualization(s): GeoMap, KPI trend with real-time alerts, Histogram, Bar chart
  • Frequency: Real-time
  • Data Required: Event timestamp, hypocenter coordinates, magnitude, depth, event count by zone
  • Pro Tip: Pair event clustering with injection rate on one time axis. Causality conversations move faster when the data sits side by side.
  • Red Flag: A migrating cluster of events toward known faults or upward through the overburden warrants immediate review of injection strategy.

CO2 Plume Conformance

  • Why it Matters: Conformance is how you prove storage is going where the model said it would. Regulators, insurers, and partners all read this number first.
  • What it Measures: Observed CO2 plume extent and shape compared against the predicted footprint generated by the reservoir simulation.
  • What Happens if Missed: Plume migration outside the licensed area threatens the storage permit and pore-space leases. Recovery options are limited and expensive.
  • Formula: N/A
  • Indicator Type: Lagging. Conformance is observed after injection through monitoring wells, 4D seismic surveys, and modeled comparisons.
  • Unit of Measure: Percent deviation from predicted footprint, or square kilometers
  • Ideal Visualization(s): GeoMap, KPI Map, KPI trend with real-time alerts
  • Frequency: Updated with each monitoring campaign
  • Data Required: Time-lapse 4D seismic data, monitoring well pressure, monitoring well saturation, modeled plume boundaries
  • Pro Tip: Overlay each monitoring snapshot on the original simulation. Patterns of misfit show which subsurface assumptions need to be updated.
  • Red Flag: Plume movement faster than predicted, especially toward fault zones or property boundaries, signals a reservoir model that no longer holds.

Fugitive CO2 Emissions

  • Why it Matters: Every fugitive tonne cancels a captured tonne and undermines the credibility of the entire operation. Quantification is non-negotiable.
  • What it Measures: Detected CO2 concentrations from continuous point monitors, optical gas imaging, and ambient sensors across capture, transport, and injection sites.
  • What Happens if Missed: Undetected leaks compound emissions liabilities, invalidate credit claims, and put personnel and nearby communities at real risk.
  • Formula: Sum of leak rates across detection points × time
  • Indicator Type: Current. Sensors and imaging run continuously, though quantification depends on calibration and confirmation workflows.
  • Unit of Measure: Tonnes per day, ppm at detection point
  • Ideal Visualization(s): GeoMap, KPI blocks, KPI trend with real-time alerts, Pareto chart when ranking sites by detected emissions
  • Frequency: Real-time
  • Data Required: Point sensor concentrations, optical gas imaging detections, wind speed, wind direction, ambient temperature
  • Pro Tip: Tie wind data into every alert. A high reading downwind of a known vent is meteorology, not necessarily a leak.
  • Red Flag: A persistent low-level reading at a single sensor across multiple shifts is almost always a real leak, even when the magnitude looks modest.

Pipeline Flow Assurance

  • Why it Matters: CO2 pipelines operate in a narrow phase envelope. Drop out of dense phase and you get slugging, vibration, and unsafe shutdowns.
  • What it Measures: Pressure, temperature, and flow along the pipeline, evaluated against the supercritical or dense phase operating window.
  • What Happens if Missed: Two-phase flow damages compressors, pumps, and metering systems. Restarting from an unstable state is slow, costly, and risk-heavy.
  • Formula: N/A
  • Indicator Type: Current. Pipeline conditions update continuously and require active control to stay inside the dense phase envelope.
  • Unit of Measure: PSI, degrees C (or F), tonnes per hour
  • Ideal Visualization(s): KPI trend with real-time alerts, XY/scatter plot, Status history trends
  • Frequency: Real-time
  • Data Required: Inlet pressure, outlet pressure, temperature along the line, mass flow rate, ambient temperature
  • Pro Tip: Plot every operating point on a pressure-temperature scatter against the phase envelope. Operators spot drift visually long before alarms fire.
  • Red Flag: A widening gap between upstream and downstream pressure with stable flow signals phase change or hydrate formation along the line.

Why Real-Time Visibility Matters

CCS operates under permanent scrutiny: from regulators, from financiers, from the host plant whose emissions the facility exists to manage. Every captured tonne carries a paper trail, and the paper trail only works when the underlying data is current, accurate, and visible to the people who can act on it. Operating blind for a single shift can mean an off-spec product entering a pipeline, a missed injection target, or a microseismic cluster nobody flagged until it showed up in the news.

The chain runs from absorber to caprock, and a problem anywhere in it eventually shows up everywhere else. Real-time visibility connects capture efficiency to compression health to wellhead pressure to plume behavior, so the operations leader sees one system instead of five disconnected ones. That single picture is the difference between a project that earns credits and a project that earns headlines.

How Transpara Can Help

If real-time operational visibility is a challenge you’re facing, you’re not alone. At Transpara, we help teams like yours gain clarity from complex systems without the need to centralize or overhaul your data stack.
Learn more about Transpara
Browse our documentation
Contact us

10 Real-Time KPIs Every Ore Beneficiation Operations Leader Should Keep on Their Radar

Ore Beneficiation. A loaded Komatsu 960E haul truck climbs the ramp out of the pit with run-of-mine ore destined for the beneficiation plant, where recovery, grade, and throughput will decide how much of that payload becomes payable metal and how much ends up in the tailings dam.

A loaded Komatsu 960E haul truck climbs the ramp out of the pit with run-of-mine ore destined for the beneficiation plant, where recovery, grade, and throughput will decide how much of that payload becomes payable metal and how much ends up in the tailings dam.

Ore beneficiation is the narrow corridor between what the geology promised and what the smelter actually pays for. Every tonne of feed gets one chance to be liberated, separated, and concentrated, and every decision in that corridor either captures value or sends it to the tailings dam.

When a beneficiation plant runs blind, recovery slides before anyone notices, reagent dosing drifts, and grade variability shows up days later in the lab. By then the metal is gone and the only conversation left is who lost it. These ten KPIs are the ones a beneficiation operations leader should be able to see, trend, and act on in real time.

Metallurgical Recovery

  • Why it Matters: Recovery is the largest single lever on revenue per tonne milled. A one-point swing on a concentrator can mean millions per year.
  • What it Measures: The percentage of valuable minerals in the feed that reports to final concentrate, calculated from grade and tonnage on every stream.
  • What Happens if Missed: Metal leaves with the tailings, the loss compounds shift after shift, and the lab confirms it days after the money is gone.
  • Formula: Recovery (%) = (Concentrate Mass × Concentrate Grade) / (Feed Mass × Feed Grade) × 100
  • Indicator Type: Lagging, when calculated from assay. Current, when modelled from online analyzers. Treat any analyzer-driven recovery as a live operating signal.
  • Unit of Measure: Percent
  • Ideal Visualization(s): KPI block for current shift recovery, KPI trend with real-time alerts on downward drift, Pareto chart when ranking flotation lines by recovery deviation
  • Frequency: Real-time when online analyzers are available, hourly to shift-based on lab assay
  • Data Required: Feed tonnage, feed grade, concentrate tonnage, concentrate grade, tailings grade
  • Pro Tip: Pair the live analyzer recovery with the shift assay back-calculation. Persistent gaps usually point to a sampling or mass balance issue, not the process.
  • Red Flag: Recovery holding steady while concentrate grade falls. The plant is trading quality for the recovery number, and the penalty will follow.

Concentrate Grade

  • Why it Matters: Grade drives smelter payable value and penalty terms. Too low costs revenue; too high usually costs recovery.
  • What it Measures: The mass percentage of the target mineral in the final concentrate stream, measured by online analyzer or composite assay.
  • What Happens if Missed: Off-spec concentrate triggers smelter penalties, contract renegotiation, or rejection at the port if the deviation is severe.
  • Formula: Concentrate Grade (%) = (Mass of Target Mineral in Concentrate) / (Total Concentrate Mass) × 100
  • Indicator Type: Current. Online XRF and similar analyzers make this actionable within minutes rather than the next morning’s lab report.
  • Unit of Measure: Percent
  • Ideal Visualization(s): KPI block with live target band, KPI trend with real-time alerts on upper and lower limits, bullet chart against contract spec
  • Frequency: Real-time on analyzer, every 1-2 hours when sampled
  • Data Required: Concentrate analyzer reading, sample assay results, contract grade target
  • Pro Tip: Plot grade against recovery on an XY scatter for the last seven days. The cloud shows you the operating envelope and the outliers tell you where the upset windows are.
  • Red Flag: A stable grade average masking widening shift-to-shift variability. Sensor drift, sampler plugging, or a feed mineralogy shift is usually starting underneath it.

Tailings Grade

  • Why it Matters: Every gram in the tails is lost revenue. Tailings grade is the cleanest signal that recovery is slipping before the daily reconciliation is done.
  • What it Measures: The residual grade of the target mineral in the final tailings stream, before discharge to the tailings storage facility.
  • What Happens if Missed: Persistent losses go unnoticed until month-end reconciliation, by which time the metal is unrecoverable and budget has eroded.
  • Formula: Tailings Grade (%) = (Mass of Target Mineral in Tails) / (Total Tails Mass) × 100
  • Indicator Type: Leading for recovery. A creeping tails grade almost always shows up before headline recovery moves.
  • Unit of Measure: Percent, or grams per tonne for precious metals
  • Ideal Visualization(s): KPI trend with real-time alerts on threshold breach, SPC trend (control chart), Pareto chart when ranking final tails streams across multiple banks
  • Frequency: Real-time on analyzer, hourly when sampled
  • Data Required: Tailings analyzer reading, tails sample assay, head grade for reconciliation
  • Pro Tip: Set the alert threshold off historical variability, not a fixed number. A 0.05% creep in copper tails over a week is worth more than a single spike that resets in an hour.

Mill Throughput

  • Why it Matters: Throughput sets the upper ceiling on revenue every shift. Every hour below nameplate is unrecoverable production.
  • What it Measures: Dry tonnes of ore processed through the comminution circuit per unit time, typically measured at SAG or ball mill feed.
  • What Happens if Missed: The plant misses monthly production targets, fixed costs spread over fewer tonnes, and downstream stockpiles run thin.
  • Formula: Throughput (t/h) = (Wet Tonnage × (1 – Moisture %)) / Operating Hours
  • Indicator Type: Current. Throughput is the live heartbeat of the plant and the constraint on almost every other beneficiation KPI.
  • Unit of Measure: Tonnes per hour (t/h)
  • Ideal Visualization(s): KPI block for instantaneous t/h, KPI trend with real-time alerts on dips below target, bullet chart against shift target, Pareto chart when comparing parallel grinding lines
  • Frequency: Real-time
  • Data Required: Belt weigh scale reading, moisture content, mill power draw, mill operating status
  • Pro Tip: Trend throughput alongside mill power and bearing pressure on a single time axis. The three together tell you whether you are feed-limited, power-limited, or grinding-limited.
  • Red Flag: Throughput holding while power and pressure climb. The mill is overfilling and you are minutes from a grindout or overload trip.

Grinding Circuit P80

  • Why it Matters: P80 sets ore liberation, which caps downstream recovery. Get the grind wrong and nothing in flotation can recover the loss.
  • What it Measures: The particle size at which 80% of the cyclone overflow stream passes, indicating the fineness of the grind feeding flotation.
  • What Happens if Missed: Coarse particles lock up valuable minerals and report straight to tailings; over-grinding wastes energy and creates slimes that hurt flotation.
  • Formula: N/A
  • Indicator Type: Leading. P80 deviations show up in flotation recovery within one to two residence times.
  • Unit of Measure: Microns (µm)
  • Ideal Visualization(s): KPI block for current P80, KPI trend with real-time alerts on band breach, histogram of size distribution across the day
  • Frequency: Real-time with online particle size monitor, hourly with manual screening
  • Data Required: Online particle size measurement, cyclone overflow flow, cyclone feed pressure, feed hardness index
  • Pro Tip: Correlate P80 against recovery on a rolling 24-hour window. The sweet spot is usually narrower than the operating procedure assumes.

Specific Energy Consumption (SEC)

  • Why it Matters: Comminution is the largest energy user on a beneficiation plant. SEC shows how efficiently power converts into liberation.
  • What it Measures: Energy consumed per tonne of ore milled, expressed in kilowatt-hours per dry tonne across the grinding circuit.
  • What Happens if Missed: Power costs creep upward, carbon reporting suffers, and you lose the early signal of a worn liner or an inefficient grind.
  • Formula: SEC (kWh/t) = Total Mill Power (kWh) / Throughput (t)
  • Indicator Type: Current. SEC is calculated continuously and trended against feed hardness and product size for context.
  • Unit of Measure: kWh per dry tonne (kWh/t)
  • Ideal Visualization(s): KPI trend with real-time alerts on upward drift, bullet chart against design SEC, Pareto chart when ranking mills by efficiency
  • Frequency: Real-time
  • Data Required: Mill motor power, throughput, ore hardness index, liner age
  • Pro Tip: SEC rising with stable throughput and P80 almost always means liners are worn or the media charge is off. One wasted month of high-SEC operation usually pays for the reline.

Flotation Reagent Consumption Rate

  • Why it Matters: Reagents are the second-largest variable cost in a flotation plant. Overdosing burns cash; underdosing burns recovery.
  • What it Measures: Mass of collector, frother, depressant, and modifier consumed per tonne of feed ore, by reagent type and by circuit.
  • What Happens if Missed: Dosing pumps drift, operators compensate by overfeeding, and the unit cost per tonne quietly inflates without anyone owning the number.
  • Formula: Reagent Consumption (g/t) = Total Reagent Used (g) / Tonnes of Feed Processed (t)
  • Indicator Type: Current. Real-time dosing combined with feed tonnage gives a live cost per tonne by reagent.
  • Unit of Measure: Grams per tonne (g/t)
  • Ideal Visualization(s): KPI block per reagent, KPI trend with real-time alerts on consumption above target, Pareto chart when ranking reagents by spend, bullet chart against target dosage
  • Frequency: Real-time
  • Data Required: Reagent flow meter readings, tank levels, feed tonnage, reagent unit cost
  • Pro Tip: Always trend reagent consumption alongside recovery and head grade. Reagent decisions made in isolation usually cost more than they save.
  • Red Flag: Collector dose rising while recovery stays flat. Either mineralogy has shifted, the reagent is degrading in storage, or someone has manually overridden the dose loop.

Flotation Cell Froth Depth and Pulp Level

  • Why it Matters: Froth depth controls the trade-off between grade and recovery in every flotation cell. A wandering level is a wandering profit margin.
  • What it Measures: Distance from the cell lip to the pulp froth interface in each flotation cell, measured continuously by float, ultrasonic, or radar sensor.
  • What Happens if Missed: Cells run shallow and grade tanks; cells run deep and recovery falls; cleaner circuits then chase the upset for hours.
  • Formula: Froth Depth (mm) = Cell Lip Height – Pulp Froth Interface Height
  • Indicator Type: Current. Level control is the most-tuned and most-disturbed control loop in flotation.
  • Unit of Measure: Millimetres (mm) or centimetres (cm)
  • Ideal Visualization(s): KPI trend with real-time alerts on level deviation, status history trends for control loop mode, bullet chart against setpoint, Pareto chart when comparing cells by deviation
  • Frequency: Real-time
  • Data Required: Level sensor reading, control valve position, controller setpoint, control loop mode (auto/manual)
  • Pro Tip: A cell sitting in manual for more than an hour is a silent recovery loss. Track time-in-auto by cell and by bank as a daily operations metric, not just an engineering one.

Cyclone Feed Slurry Density

  • Why it Matters: Slurry density at the cyclone feed controls classification cut size, which controls grinding load and downstream P80. Wrong density wastes both.
  • What it Measures: Mass of solids per unit volume of slurry entering the cyclone cluster, typically expressed as percent solids by weight.
  • What Happens if Missed: Cyclones bypass coarse particles to overflow, ball mill recirculating load swings, and P80 oscillates outside the recovery window.
  • Formula: Percent Solids (%) = (Mass of Solids) / (Mass of Solids + Mass of Water) × 100
  • Indicator Type: Leading. Density swings show up in P80, mill load, and ultimately recovery within minutes.
  • Unit of Measure: Percent solids by weight, or specific gravity (g/mL)
  • Ideal Visualization(s): KPI trend with real-time alerts on density excursion, SPC trend (control chart), bullet chart against target band
  • Frequency: Real-time
  • Data Required: Density gauge reading (nuclear or Coriolis), cyclone feed flow, sump level, water addition flow
  • Pro Tip: When sump pumps start cavitating or cycling, density is almost always the upstream cause. Trend pump speed and density together to catch it before a trip.

Plant Availability (Beneficiation Circuit)

  • Why it Matters: Every hour the plant is down is an hour of fixed costs with zero revenue. Availability sets the realistic ceiling on monthly throughput.
  • What it Measures: Percentage of scheduled production time the beneficiation circuit is actually available to process ore, by major equipment and overall plant.
  • What Happens if Missed: Unplanned stoppages cascade, maintenance windows compress, and the monthly plan quietly drifts out of reach by mid-month.
  • Formula: Availability (%) = (Operating Time / Scheduled Time) × 100
  • Indicator Type: Lagging, at plant level. Current, when measured continuously by asset. Use both views together.
  • Unit of Measure: Percent
  • Ideal Visualization(s): KPI block per major asset, KPI trend with real-time alerts on availability dip, Pareto chart when ranking equipment by downtime hours, status history trends for run/idle/fault states
  • Frequency: Real-time
  • Data Required: Equipment run/idle/fault status, downtime reason codes, scheduled operating hours, planned maintenance windows
  • Pro Tip: Pareto the last 30 days of downtime by reason code, not by duration. The repeating short stoppages almost always cost more than the one big event everyone remembers.
  • Red Flag: Availability holding flat while short-stop frequency climbs. The plant is being held together by operator intervention, and the next big trip is already on the calendar.

Why Real-Time Visibility Matters

Beneficiation plants make money in minutes and lose it in hours. A cyclone density excursion at 2am, a froth level drifting in cleaner cells, a collector pump quietly under-dosing on the rougher bank: none of these wait for the morning meeting. The plants that hit plan are the ones where the operations leader, the metallurgist, and the control room are all looking at the same live numbers and acting on them inside the same shift.

Running blind is expensive in this corridor of the operation. Recovery losses do not arrive as alarms; they show up in month-end reconciliations, in smelter penalties, and in stretched maintenance budgets. Real-time KPIs, trended against limits and pushed to the right person on the right device, turn a beneficiation plant from a reactive cost centre into a predictable revenue engine.

How Transpara Can Help

If real-time operational visibility is a challenge you’re facing, you’re not alone. At Transpara, we help teams like yours gain clarity from complex systems without the need to centralize or overhaul your data stack.
Learn more about Transpara
Browse our documentation
Contact us

10 Real-Time KPIs Every Hydrogen Production Plant Operations Leader Should Keep on Their Radar

Hydrogen Production Plant. Hydrogen storage vessels and interconnecting headers stage product for offtake. This is where purity excursions and small vent losses quietly compound into lost margin before monthly reconciliation catches them.

Hydrogen storage vessels and interconnecting headers stage product for offtake. This is where purity excursions and small vent losses quietly compound into lost margin before monthly reconciliation catches them.

Hydrogen production is mostly a fight between conversion efficiency and the cost of every electron or molecule of methane walking in the door. The margin is thin, the spec is tight, and the regulatory ground is moving.

When a hydrogen plant runs blind, the losses don’t announce themselves. They show up as a quarter point of SEC drift, a creeping impurity at the product header, or a vent valve cycling 40 seconds too often per shift. None of it triggers an alarm. All of it compounds. The KPIs below are the ones a hydrogen operations leader needs in real time, alerted, and trended, before drift turns into lost product.

Specific Energy Consumption (SEC)

  • Why it Matters: SEC is the single biggest driver of hydrogen cost. A 5% drift translates directly into millions per year on any commercial-scale plant.
  • What it Measures: Total electrical or thermal energy consumed per kilogram of hydrogen produced, including auxiliaries and parasitic loads.
  • What Happens if Missed: Margin erosion hides inside normal operations. By the time monthly accounting flags it, you’ve already lost the quarter.
  • Formula: SEC = Total Energy Input (kWh) / H2 Produced (kg)
  • Indicator Type: Current. Reflects the live efficiency of the conversion process and plant balance.
  • Unit of Measure: kWh/kg H2
  • Ideal Visualization(s): KPI block with target band, KPI trend with real-time alerts, bullet chart against design SEC
  • Frequency: Real-time, with rolling hourly and daily averages
  • Data Required: Total power draw, thermal energy input, hydrogen mass flow, ambient temperature, load setpoint
  • Red Flag: SEC creeping up at constant load and constant feedstock quality. That’s degradation or fouling, not weather.

Hydrogen Production Rate vs. Nameplate

  • Why it Matters: Production rate determines whether you meet offtake commitments and recover fixed costs. Below 85% of nameplate puts contracts and economics at risk.
  • What it Measures: Real-time hydrogen output expressed as a percentage of design capacity at current operating conditions and ambient.
  • What Happens if Missed: Offtake shortfalls trigger penalty clauses. Repeated underproduction forces the operator to renegotiate or buy hydrogen on the spot market to cover.
  • Formula: Production Rate % = (Actual H2 Flow / Nameplate H2 Flow) × 100
  • Indicator Type: Current. Shows whether the plant is delivering against design at this moment.
  • Unit of Measure: kg/hr and % of nameplate
  • Ideal Visualization(s): KPI block, KPI trend with real-time alerts, Pareto chart when ranking trains or modules by production deviation
  • Frequency: Real-time
  • Data Required: Hydrogen mass flow, design capacity, load setpoint, feedstock availability
  • Pro Tip: Always compare actual rate to load setpoint, not just nameplate. A plant running at 60% setpoint isn’t underperforming, but a plant at 100% setpoint hitting only 92% output is.

Hydrogen Purity

  • Why it Matters: Purity defines salability. Fuel-cell grade requires 99.97% H2 with strict limits on CO, H2O, and sulfur, and off-spec product gets vented or downgraded.
  • What it Measures: Hydrogen concentration at the product header, plus trace impurity levels for the key contaminants of your chosen sales spec.
  • What Happens if Missed: A purity excursion contaminates downstream storage, damages customer equipment, and can force a full plant blowdown to recover.
  • Formula: Purity % = (H2 vol / Total Product Gas vol) × 100, with separate ppm tracking for O2, H2O, CO, N2, S
  • Indicator Type: Current. Quality measurement at the point of sale or compression.
  • Unit of Measure: vol% H2 and ppm per impurity
  • Ideal Visualization(s): KPI block per impurity, KPI trend with real-time alerts, SPC trend (control chart) for each impurity stream
  • Frequency: Real-time from online analyzers, with periodic lab validation
  • Data Required: Product hydrogen analyzer reading, dryer dew point, deoxo bed temperature, PSA tail gas composition
  • Red Flag: A slow rise in any single impurity at constant production. That’s a bed, membrane, or analyzer drift, not noise.

Cell or Tube Outlier Spread

  • Why it Matters: Hydrogen plants run hundreds of cells or tubes in parallel. One bad unit drags efficiency and accelerates the failure of its neighbors.
  • What it Measures: Statistical spread of cell voltage across an electrolyzer stack, or tube skin temperature across an SMR furnace, against the fleet median.
  • What Happens if Missed: A failing cell or hot tube can cascade into stack damage, tube rupture, or an unplanned shutdown that costs days of production.
  • Formula: Spread = |Individual Reading – Fleet Median| / Fleet Median, with outliers flagged above defined sigma thresholds
  • Indicator Type: Leading. A widening spread shows up well before a hard alarm fires.
  • Unit of Measure: Volts (electrolysis) or °C (SMR), and standard deviations from median
  • Ideal Visualization(s): Box plot of all cells or tubes, bullet chart per outlier, Pareto chart when ranking units by deviation
  • Frequency: Real-time
  • Data Required: Per-cell voltage or per-tube skin temperature, fleet median, sigma thresholds, age and last replacement date of each unit
  • Pro Tip: Rank outliers by deviation and by rate of change together. A unit drifting fast is more urgent than one that’s been bad and stable for months.

Stack or Catalyst Degradation Rate

  • Why it Matters: Degradation sets stack replacement timing, catalyst change-out schedules, and the slope of your future SEC. It defines lifetime economics.
  • What it Measures: Rate of irreversible performance loss in the conversion unit, normalized to constant load and ambient conditions.
  • What Happens if Missed: You over-run a catalyst bed or stack into severe degradation and incur an unplanned outage, often at the worst possible moment.
  • Formula: Degradation Rate = ΔPerformance Metric / Operating Hours (e.g., μV/hr for stacks, ΔApproach to Equilibrium per khr for catalyst)
  • Indicator Type: Lagging. Real performance loss is only visible across hundreds of hours of operation.
  • Unit of Measure: μV/hr, %/khr, or ΔT approach per thousand hours
  • Ideal Visualization(s): KPI trend with real-time alerts, SPC trend (control chart) on normalized performance, bar chart of degradation rate per stack or bed
  • Frequency: Calculated daily, reviewed weekly
  • Data Required: Normalized voltage or catalyst activity, hours in service, load history, feedstock quality, ambient conditions
  • Red Flag: A step change in degradation rate after a startup, trip, or feedstock change. That’s damage, not normal wear.

Compressor Specific Power

  • Why it Matters: Compression can consume 10 to 15% of total plant energy. Drifting compressor efficiency adds directly to delivered hydrogen cost.
  • What it Measures: Power consumed per kilogram of hydrogen compressed, segmented by stage and across the discharge pressure profile.
  • What Happens if Missed: Worn seals, fouled coolers, and recycle drift quietly eat margin until trip alarms force attention. By then, repairs are expensive.
  • Formula: Compressor Specific Power = Compressor Power Draw (kW) / H2 Mass Flow Compressed (kg/hr)
  • Indicator Type: Current. Reflects the live mechanical and thermal health of the compression train.
  • Unit of Measure: kWh/kg H2 compressed
  • Ideal Visualization(s): KPI block per stage, KPI trend with real-time alerts, Pareto chart when ranking stages or trains by deviation from design
  • Frequency: Real-time
  • Data Required: Compressor power draw per stage, suction and discharge pressure, suction and discharge temperature, hydrogen mass flow, recycle flow
  • Pro Tip: Plot specific power against discharge pressure. A vertical drift at constant pressure is internal wear. A horizontal drift is a system or cooling problem.

Feedstock-to-Hydrogen Conversion Efficiency

  • Why it Matters: Conversion efficiency shows how much of your methane or water actually leaves as product hydrogen. It’s the second-biggest cost lever after energy.
  • What it Measures: Hydrogen produced per unit of feedstock consumed, expressed as a percentage of the thermodynamic maximum for the process.
  • What Happens if Missed: Feedstock slip, side reactions, and methane breakthrough drive up consumption without showing up in production rate until invoices arrive.
  • Formula: Conversion Efficiency = (H2 Produced × MW H2) / (Feedstock Consumed × Stoichiometric Factor)
  • Indicator Type: Current. Live view of how well the conversion chemistry is performing.
  • Unit of Measure: % of theoretical maximum
  • Ideal Visualization(s): KPI block, KPI trend with real-time alerts, bullet chart against design conversion
  • Frequency: Real-time
  • Data Required: Hydrogen mass flow, feedstock mass flow, feedstock composition, reformer or stack temperature, steam-to-carbon ratio (SMR), current density (electrolysis)
  • Red Flag: Conversion dropping while feedstock flow rises. The plant is hiding lost throughput inside higher feed consumption.

Hydrogen Loss Rate (Vent and Flare)

  • Why it Matters: Every kilogram vented or flared is hydrogen you paid to produce and didn’t sell. Losses above 2% wipe out efficiency gains elsewhere.
  • What it Measures: Hydrogen mass routed to vent stacks, flares, or fuel headers, expressed as a percentage of total production.
  • What Happens if Missed: Sustained losses get normalized as part of operations. They never appear on operator screens, but they show up clearly in monthly reconciliation.
  • Formula: Loss Rate % = (H2 Vented + H2 Flared + H2 to Fuel) / Total H2 Produced × 100
  • Indicator Type: Current. Live view of where product is escaping the system.
  • Unit of Measure: % of production, and kg/hr lost
  • Ideal Visualization(s): KPI block per loss path, KPI trend with real-time alerts, Pareto chart when ranking loss sources by mass
  • Frequency: Real-time
  • Data Required: Vent stack flow, flare flow with H2 fraction, fuel header H2 content, PSA tail gas mass flow, total H2 production
  • Pro Tip: Tag every vent and flare event with its upstream cause. Most “unexplained” losses are repeat patterns from startups, trips, or pressure swings.

Carbon Intensity per kg H2

  • Why it Matters: Carbon intensity defines hydrogen color and unlocks subsidies, tax credits, and offtake premiums. A 1 kg CO2e shift can move a plant across regulatory thresholds.
  • What it Measures: Total scope 1 and scope 2 greenhouse gas emissions per kilogram of hydrogen produced, calculated in real time.
  • What Happens if Missed: Plants exceed certification thresholds without knowing it, lose access to incentive markets, and rebuild offtake terms after the fact.
  • Formula: Carbon Intensity = (Scope 1 Emissions + Scope 2 Emissions) / H2 Produced
  • Indicator Type: Current. Tracks regulatory and commercial standing as it happens.
  • Unit of Measure: kg CO2e per kg H2
  • Ideal Visualization(s): KPI block, KPI trend with real-time alerts, bullet chart against certification threshold, SPC trend (control chart) for variance
  • Frequency: Real-time, with daily and monthly rollups for reporting
  • Data Required: Fuel gas consumption, grid electricity draw, on-site renewable generation, carbon capture rate, fugitive emissions, hydrogen production
  • Red Flag: A sustained jump after a feedstock or grid mix change. Most plants only catch this in monthly disclosures, far too late.

Plant On-Stream Factor

  • Why it Matters: On-stream factor determines annual production, contract delivery, and capital recovery. A 1% drop on a 30,000 tpa plant costs roughly 300 tonnes of hydrogen per year.
  • What it Measures: Hours of hydrogen production at or above minimum spec, divided by total available hours in the period.
  • What Happens if Missed: Trip patterns, slow restarts, and short outages compound. Annual availability misses the budget by a margin that’s almost impossible to recover.
  • Formula: On-Stream Factor = (Hours at or above Spec / Total Period Hours) × 100
  • Indicator Type: Lagging. Reflects accumulated uptime over a defined period.
  • Unit of Measure: % of period
  • Ideal Visualization(s): Status history trend, KPI block with monthly and yearly rollup, Pareto chart when ranking outage causes by lost hours
  • Frequency: Hourly updates, daily and monthly rollups
  • Data Required: Production state per minute, spec compliance flags, trip events, planned maintenance windows
  • Pro Tip: Separate planned outage time from unplanned. Unplanned hours are where operations leaders actually have leverage.

Why Real-Time Visibility Matters

Hydrogen plants don’t fail loudly. They fail slowly, through a quarter point of SEC drift, a creeping impurity, a flare event that’s become routine. The cost of any single moment looks small. The cost across a quarter does not. By the time monthly accounting closes the books, the operations leader is reading history, not running the plant.

The hydrogen plants that hit their certification thresholds, meet their offtake contracts, and stay profitable across the next round of energy-price moves are the ones that catch drift in hours, not weeks. Every KPI on this list is a leading or current indicator that, properly alerted and trended, gives the team enough time to act before the loss is locked in. 

How Transpara Can Help

If real-time operational visibility is a challenge you’re facing, you’re not alone. At Transpara, we help teams like yours gain clarity from complex systems without the need to centralize or overhaul your data stack.
Learn more about Transpara
Browse our documentation
Contact us

10 Real-Time KPIs Every Mineral Processing Operations Leader Should Be Tracking

Mineral Processing image. Crushed product moves from screens to stockpiles across a web of conveyors and transfer points, where every belt is a live readout of throughput, particle size, and circuit balance. When these feeds drift out of spec, downstream recovery and grade pay the price within the next shift.

Crushed product moves from screens to stockpiles across a web of conveyors and transfer points, where every belt is a live readout of throughput, particle size, and circuit balance. When these feeds drift out of spec, downstream recovery and grade pay the price within the next shift.

A mineral processing plant has one job: separate value from waste every second of every shift. When the circuit drifts and nobody sees it in real time, recovery slips, reagent bills balloon, and concentrate grade walks out the door with the tailings. Most plants don’t lose money in one big event.

They lose it in 2% recovery drops, 30-minute mill stalls, and grind size creeping coarser while everyone watches lagging shift reports. By the time the daily metallurgical balance lands, the metal is already gone. These ten KPIs are the ones a mineral processing operations leader should see updating live, with alerts firing on the deviations that actually matter.

Mill Throughput

  • Why it Matters: Throughput drives revenue. Every tonne not milled is a tonne of unrecovered metal sitting in the stockpile or the pit.
  • What it Measures: Tonnes of dry ore processed per hour through the grinding circuit, measured at the mill feed weightometer.
  • What Happens if Missed: Hidden bottlenecks compound. Operators chase phantom issues while the real constraint, often a single cyclone or pump, stays invisible.
  • Formula: Throughput (t/h) = Σ dry tonnes fed / Σ operating hours
  • Indicator Type: Current. It reflects live grinding circuit performance against design capacity.
  • Unit of Measure: Tonnes per hour (t/h)
  • Ideal Visualization(s): KPI blocks for current throughput, KPI trend with real-time alerts on sustained dips, Pareto chart when ranking mill lines by throughput deviation
  • Frequency: Real-time, 1-minute updates
  • Data Required: Mill feed mass flow, ore moisture content, mill operating status

Metallurgical Recovery

  • Why it Matters: Recovery is the difference between a profitable plant and a tailings dam full of money. Even 1% lost across a year is millions.
  • What it Measures: Percentage of valuable mineral in the feed that reports to final concentrate, calculated by the two-product or three-product formula.
  • What Happens if Missed: Recovery losses compound silently across shifts. Without live visibility, root cause hunts start days after the metal is already in the tailings.
  • Formula: Recovery (%) = (C × c) / (F × f) × 100
  • Indicator Type: Current. Modeled from online analyzers it updates live; based on shift assays it lags by hours.
  • Unit of Measure: Percent (%)
  • Ideal Visualization(s): KPI blocks for live recovery, KPI trend with real-time alerts on recovery drops, SPC trend for shift-over-shift variability
  • Frequency: Real-time when modeled from online analyzers, otherwise every shift
  • Data Required: Feed grade, concentrate grade, tailings grade, feed mass flow, concentrate mass flow

Concentrate Grade

  • Why it Matters: Grade determines smelter payable terms and freight efficiency. Low-grade concentrate gets penalized at the smelter and costs more to ship per tonne of metal.
  • What it Measures: Percentage by mass of the valuable mineral or metal in the final concentrate stream.
  • What Happens if Missed: Operators chase recovery and let grade slip, or chase grade and bleed recovery. Without live grade visibility, the trade-off is guesswork.
  • Formula: Grade (%) = mass valuable mineral / total concentrate mass × 100
  • Indicator Type: Current. Online analyzers deliver live readings; shift composites lag the operating decision by hours.
  • Unit of Measure: Percent (%) or grams per tonne (g/t) depending on commodity
  • Ideal Visualization(s): KPI blocks for current grade, KPI trend with real-time alerts on grade slippage, XY scatter plot for grade versus recovery trade-off
  • Frequency: Real-time with online analyzer, every 30 to 60 minutes with composite sampling
  • Data Required: Online analyzer readings, concentrate mass flow, feed grade for reconciliation
  • Pro Tip: The grade-recovery curve isn’t static. Watch how it shifts with feed mineralogy, reagent dose, and froth depth. The operating point should move with the ore.

Grind Size (P80)

  • Why it Matters: Grind size sets the ceiling on recovery. Too coarse and minerals stay locked, too fine and energy and reagents are wasted on overgrind.
  • What it Measures: The particle size at which 80% of the cyclone overflow passes, measured by online particle size analyzer.
  • What Happens if Missed: P80 drifts coarser as liners wear or feed hardens. Recovery quietly drops for hours before assay results catch up.
  • Formula: N/A
  • Indicator Type: Leading. Grind size changes show up in recovery several minutes to hours later.
  • Unit of Measure: Microns (µm)
  • Ideal Visualization(s): KPI blocks for live P80, KPI trend with real-time alerts on coarsening, histogram of the full size distribution
  • Frequency: Real-time, 1 to 5 minute updates from the particle size analyzer
  • Data Required: Online particle size analyzer output, mill discharge density, cyclone feed pressure
  • Red Flag: P80 coarsening with stable mill throughput and load. That’s usually cyclone wear or feed density drift.

Specific Energy Consumption

  • Why it Matters: Grinding consumes 40 to 60% of plant electricity. A few kWh/t saved across a high-tonnage mill is a major operating cost win.
  • What it Measures: Electrical energy consumed per tonne of ore milled across the comminution circuit.
  • What Happens if Missed: Energy creep gets blamed on ore hardness when it’s often worn liners, suboptimal ball charge, or pump inefficiency.
  • Formula: SEC (kWh/t) = Σ kWh consumed / Σ tonnes milled
  • Indicator Type: Current. It moves with load, liner condition, and ore competence in real time.
  • Unit of Measure: Kilowatt-hours per tonne (kWh/t)
  • Ideal Visualization(s): KPI blocks for live SEC, KPI trend with real-time alerts on sustained rises, Pareto chart when ranking mills by SEC deviation from baseline
  • Frequency: Real-time, 1-minute updates
  • Data Required: Mill motor power draw, mill feed tonnage, mill operating status
  • Pro Tip: Benchmark SEC against ore Bond Work Index, not against a static target. The ratio of actual to theoretical SEC tells you how efficiently the mill is running today.

Reagent Consumption per Tonne

  • Why it Matters: Flotation reagents are one of the largest variable operating costs. Overdosing is wasted money, underdosing is lost metal.
  • What it Measures: Mass of each reagent (collector, frother, depressant, modifier) consumed per tonne of ore processed.
  • What Happens if Missed: Operators dose to a fixed setpoint regardless of ore type. Recovery drifts and reagent costs creep with nobody connecting the two.
  • Formula: Dose (g/t) = reagent mass flow (g/h) / feed tonnage (t/h)
  • Indicator Type: Current. Live dosing rates show whether circuits are over-fed or starved against present ore conditions.
  • Unit of Measure: Grams or kilograms per tonne (g/t or kg/t)
  • Ideal Visualization(s): KPI blocks per reagent, KPI trend with real-time alerts on dose deviation, Pareto chart when ranking reagents by cost contribution
  • Frequency: Real-time, every 1 to 5 minutes
  • Data Required: Reagent flow rates, reagent density, feed tonnage, ore type indicator
  • Red Flag: Reagent dose climbing while recovery stays flat. That signals the circuit isn’t responding and there’s a deeper chemistry or feed mineralogy issue.

Cyclone Overflow Percent Solids

  • Why it Matters: Classification sets up flotation. Wrong overflow density skews the particle size reporting to flotation and degrades both grade and recovery downstream.
  • What it Measures: Mass percentage of solids in the hydrocyclone overflow stream feeding the flotation circuit.
  • What Happens if Missed: A drifting nuclear density gauge or a worn apex masks a classification problem for hours. Flotation gets blamed for grinding’s mistakes.
  • Formula: % Solids = mass solids / total slurry mass × 100
  • Indicator Type: Current. It reflects the live operating state of the classification circuit.
  • Unit of Measure: Percent solids by mass (%)
  • Ideal Visualization(s): KPI blocks for current % solids, KPI trend with real-time alerts on deviation, Pareto chart when ranking cyclones by deviation from target
  • Frequency: Real-time, 1-minute updates
  • Data Required: Cyclone overflow density, slurry flow rate, water addition rate, cyclone feed pressure
  • Pro Tip: Pair this with cyclone feed pressure. Pressure drifting up with stable flow usually means apex wear or roping, both of which kill classification.

Plant Availability

  • Why it Matters: Availability is a direct multiplier on annual production. An hour lost on the SAG mill is rarely recovered, since downstream circuits can’t run dry.
  • What it Measures: Percentage of scheduled time the plant or a critical asset is actually available to process ore.
  • What Happens if Missed: Small repeating stoppages get coded as “minor” and never escalate. A 20-minute trip three times a shift is an hour of lost production nobody is accounting for.
  • Formula: Availability (%) = Operating Time / Scheduled Time × 100
  • Indicator Type: Lagging. It summarizes recent runtime against schedule.
  • Unit of Measure: Percent (%)
  • Ideal Visualization(s): KPI blocks per circuit, status history trends for outage causes, Pareto chart when ranking downtime events by cause and duration
  • Frequency: Real-time status, with hourly and shift rollups
  • Data Required: Equipment run status, stoppage reason codes, scheduled operating hours
  • Red Flag: Availability above 95% with throughput below target. The plant’s running but throttled, which is a hidden bottleneck, not an uptime win.

Tailings Slurry Density and Water Recovery

  • Why it Matters: Water is a regulated, cost-laden resource. Thicker tailings mean more recycled water, lower pumping costs, and safer dam operation.
  • What it Measures: Density of thickener underflow and the percentage of process water recovered for reuse back into the plant.
  • What Happens if Missed: Thickener upsets push thin tailings to the dam, raise freshwater intake, and quietly inflate water balance reports until regulators or auditors notice.
  • Formula: Water Recovery (%) = recycled water volume / total process water consumed × 100
  • Indicator Type: Current. Density and recovery move with flocculant dose, bed level, and feed solids in real time.
  • Unit of Measure: Percent solids (%) for density, percent (%) for water recovery
  • Ideal Visualization(s): KPI blocks for live density and recovery, KPI trend with real-time alerts on thickener bed level, SPC trend for stability
  • Frequency: Real-time, 1-minute updates
  • Data Required: Thickener underflow density, overflow turbidity, flocculant dose rate, bed level, recycled water flow
  • Pro Tip: Watch flocculant consumption per tonne of solids. A rising flocculant dose with stable feed is the first sign of mineralogy or pH changes hitting settling rates.

Mass Pull

  • Why it Matters: Mass pull links grinding, flotation, and the grade-recovery curve. It’s a fast proxy for circuit response when assays lag.
  • What it Measures: Percentage of feed mass reporting to concentrate, measured by mass flow before assay results are available.
  • What Happens if Missed: Mass pull drifts up and operators read it as recovery success when it’s really dilution. Concentrate grade quietly drops behind it.
  • Formula: Mass Pull (%) = concentrate mass flow / feed mass flow × 100
  • Indicator Type: Leading. Mass pull moves minutes ahead of any grade or recovery confirmation.
  • Unit of Measure: Percent (%)
  • Ideal Visualization(s): KPI blocks for current mass pull, KPI trend with real-time alerts on rapid shifts, XY scatter plot for mass pull versus grade
  • Frequency: Real-time, 1-minute updates
  • Data Required: Concentrate mass flow, feed mass flow, slurry densities
  • Red Flag: Mass pull climbing while concentrate grade falls. That’s froth carrying gangue, often from over-aerated cells or too-shallow froth depth.

Why Real-Time Visibility Matters

Mineral processing operates on minute-by-minute trade-offs. A grind size drift, a reagent overdose, a thickener bed creeping up: none of these show up cleanly in a shift report, but each one moves recovery, grade, and operating cost in real time. When the visibility window is 12 hours wide, every shift starts behind, reacting to yesterday’s metal balance instead of today’s circuit.

The plants that pull ahead aren’t the ones with the newest equipment. They’re the ones where the control room, the metallurgist, and the maintenance lead all see the same live numbers, with alerts firing on the deviations that actually matter. Real-time KPIs turn a reactive plant into one that catches problems while the ore is still in the circuit.

How Transpara Can Help

If real-time operational visibility is a challenge you’re facing, you’re not alone. At Transpara, we help teams like yours gain clarity from complex systems without the need to centralize or overhaul your data stack.
Learn more about Transpara
Browse our documentation
Contact us

10 Real-Time KPIs Every Satellite Ground Station Operations Leader Should Keep on Their Radar

A mixed-aperture ground station at altitude, with each dish carrying its own pointing budget, link margin, and AOS clock. Real-time visibility is what keeps them aligned during the pass, not in the postmortem after.

A mixed-aperture ground station at altitude, with each dish carrying its own pointing budget, link margin, and AOS clock. Real-time visibility is what keeps them aligned during the pass, not in the postmortem after.

A ground station network earns its keep in the ten minutes a satellite is overhead. Everything else is preparation or postmortem. When a pass starts going sideways, the warning signs are short. Pointing drifts before lock is lost. Link margin erodes before bit errors spike. An HPA twitches off setpoint before it trips. Teams that wait for the postmortem are already working from data that’s a customer escalation.

These are the ten KPIs that decide whether a ground station network runs ahead of trouble or behind it.

Pass Success Rate

  • Why it Matters: Every missed pass is unrecoverable revenue and a customer escalation. This number is what your largest accounts measure you against.
  • What it Measures: The percentage of scheduled passes that delivered all telemetry, command, and mission data within contracted quality thresholds.
  • What Happens if Missed: SLA penalties stack, customers re-evaluate provider mix, and your network reputation takes hits that take quarters to repair.
  • Formula: (Successful Passes / Total Scheduled Passes) × 100
  • Indicator Type: Lagging. Reflects what already happened, but trended over rolling windows it exposes systemic degradation early.
  • Unit of Measure: Percent (%)
  • Ideal Visualization(s): KPI trend with real-time alerts, Pareto chart when ranking ground stations by failed-pass count
  • Frequency: Every pass, rolled up hourly and daily
  • Data Required: Pass schedule, pass completion status, data quality flags, customer acceptance status
  • Pro Tip: Slice by satellite operator, antenna, and time of day. The averages always look fine; the slices tell the truth.
  • Red Flag: A station hitting target on rate but failing a single customer disproportionately. Aggregate KPIs hide concentrated SLA risk.

Link Margin (Eb/No)

  • Why it Matters: Link margin is your headroom against rain, interference, and pointing drift. When it collapses, the data goes with it.
  • What it Measures: The difference between received energy-per-bit-to-noise ratio and the threshold required for the modulation and coding scheme in use.
  • What Happens if Missed: BER climbs, retransmits multiply, and high-rate downlinks degrade or drop entirely. Mission data arrives late or corrupted.
  • Formula: Eb/No_measured – Eb/No_required (in dB)
  • Indicator Type: Current. A real-time view of how much link you have to spare before quality collapses.
  • Unit of Measure: Decibels (dB)
  • Ideal Visualization(s): KPI trend with real-time alerts, Bullet chart against required threshold
  • Frequency: Real-time, sub-second sampling
  • Data Required: Received Eb/No, modulation scheme, coding rate, required Eb/No for current configuration
  • Pro Tip: Plot margin against elevation angle for each pass. Sudden margin dips at high elevation usually mean the antenna, not the weather.
  • Red Flag: Margin trending down across multiple satellites and stations simultaneously. That’s not weather, that’s a calibration or reference drift.

Antenna Pointing Error

  • Why it Matters: A few millidegrees of pointing error at S-band is annoying. At Ka-band it costs you the pass.
  • What it Measures: The angular distance between commanded antenna position and actual position during active tracking, in both azimuth and elevation.
  • What Happens if Missed: Link margin erodes, autotrack falls off the satellite, and high-frequency missions become unworkable in marginal conditions.
  • Formula: sqrt((Az_actual – Az_commanded)² + (El_actual – El_commanded)²)
  • Indicator Type: Leading. Pointing degrades before link margin and bit error rate do, so it warns ahead of the failure.
  • Unit of Measure: Millidegrees (m°)
  • Ideal Visualization(s): KPI trend with real-time alerts, SPC trend, Pareto chart when ranking antennas by tracking error
  • Frequency: Real-time, every servo cycle
  • Data Required: Commanded azimuth, commanded elevation, encoder azimuth, encoder elevation, frequency band, tracking mode
  • Pro Tip: Tracking error grows with wind. Correlate pointing residuals with anemometer data and you’ll predict pass risk hours ahead.
  • Red Flag: Asymmetric error in azimuth versus elevation. Often points to a gear, encoder, or counterweight issue rather than wind.

Bit Error Rate (BER)

  • Why it Matters: BER is the closest thing you have to ground truth on data quality. Everything downstream is hostage to it.
  • What it Measures: The fraction of received bits in error after demodulation but before forward error correction, on a given link.
  • What Happens if Missed: Retransmits eat throughput, mission products fail integrity checks, and customers stop trusting the data they’re paying for.
  • Formula: Bit Errors / Total Bits Received
  • Indicator Type: Current. Updates continuously during a pass and reflects the live state of the demodulation chain.
  • Unit of Measure: Errors per bit (e.g., 1E-6)
  • Ideal Visualization(s): KPI trend with real-time alerts, Histogram of BER across passes
  • Frequency: Real-time, second-by-second during active pass
  • Data Required: Demodulator error count, total received bits, modulation, FEC configuration
  • Pro Tip: Pre-FEC BER tells you the real story. Post-FEC looks clean right up until it doesn’t, and by then the data is gone.
  • Red Flag: BER good but frame sync repeatedly drops. Usually a clock recovery or AGC issue, not noise.

Acquisition of Signal (AOS) Timeliness

  • Why it Matters: Every second late on AOS is a second of telemetry and command opportunity you can’t get back this orbit.
  • What it Measures: The time difference between predicted AOS and actual carrier lock on the satellite during a scheduled pass.
  • What Happens if Missed: Short LEO passes lose meaningful capacity, command queues run long, and critical commanding slips to the next contact.
  • Formula: T_lock_actual – T_AOS_predicted
  • Indicator Type: Lagging per pass. Trended across the network it signals scheduling, TLE, or RF chain warm-up problems.
  • Unit of Measure: Seconds (s)
  • Ideal Visualization(s): KPI trend with real-time alerts, Histogram of acquisition delays, Pareto chart when ranking stations by late-AOS frequency
  • Frequency: Every pass
  • Data Required: Predicted AOS time, actual carrier lock time, TLE epoch, antenna pre-position status, RF chain ready status
  • Pro Tip: Persistent five-second late AOS across a station usually means stale TLEs or a slow handoff between scheduling and the antenna controller.
  • Red Flag: Late AOS that improves mid-pass with autotrack means you’re acquiring on signal, not on prediction. Your ephemeris pipeline is drifting.

Gain over Temperature (G/T)

  • Why it Matters: G/T defines the smallest signal your station can pull out of noise. It caps every link budget you build.
  • What it Measures: Antenna gain divided by system noise temperature, expressed as a single figure of merit for receive sensitivity.
  • What Happens if Missed: Low elevation and weak-satellite passes start failing first. You’ll discover the degradation only when customers complain.
  • Formula: G/T = Gain (dBi) – 10·log10(Tsys) (dB/K)
  • Indicator Type: Leading. Degrades slowly with LNA aging, feed contamination, or cooling failures, well before link metrics react.
  • Unit of Measure: Decibels per Kelvin (dB/K)
  • Ideal Visualization(s): KPI trend with real-time alerts, SPC trend, Pareto chart when ranking antennas by G/T degradation
  • Frequency: Daily measurement during noise-figure check, continuous when noise calibration is active
  • Data Required: Antenna gain calibration, LNA noise temperature, feed and waveguide losses, ambient temperature
  • Pro Tip: Run noise-figure checks on a fixed schedule with the antenna at zenith. Drift here is the earliest warning of LNA failure.
  • Red Flag: G/T drops correlate with rain or wind. Weather is reaching your feed or LNA enclosure where it shouldn’t.

Antenna Availability

  • Why it Matters: A booked antenna that won’t track is worse than no antenna at all. The schedule already promised it.
  • What it Measures: The percentage of scheduled antenna time that the system was fully ready and capable of executing a pass.
  • What Happens if Missed: Passes get reassigned in panic, customers absorb hits to their own missions, and SLA credits start eating margin.
  • Formula: (Available Antenna Hours / Scheduled Antenna Hours) × 100
  • Indicator Type: Lagging. Reports actual delivered capacity, and the breakdown by cause is what drives the maintenance plan.
  • Unit of Measure: Percent (%)
  • Ideal Visualization(s): KPI trend with real-time alerts, Pareto chart when ranking antennas by downtime cause, Status history trends
  • Frequency: Continuous, rolled up daily and weekly
  • Data Required: Scheduled antenna time, actual ready time, fault state, maintenance windows
  • Pro Tip: Track planned versus unplanned downtime separately. The blended number always looks acceptable; only the unplanned slice exposes real reliability.
  • Red Flag: Same antennas appearing repeatedly in unplanned downtime. Concentration in one or two assets points to a systemic fault no one is owning.

Schedule Utilization Rate

  • Why it Matters: Antennas are capital that depreciates whether they’re tracking or sitting idle. Empty minutes are money you’ve already spent.
  • What it Measures: The percentage of available antenna minutes booked against demonstrated capacity, after maintenance and reserve windows are excluded.
  • What Happens if Missed: Capacity planning loses credibility, new customer onboarding stalls, and the network grows in the wrong places at the wrong time.
  • Formula: (Booked Minutes / Available Minutes) × 100
  • Indicator Type: Current. Tells you in near real-time how full the network is and where there’s headroom to sell.
  • Unit of Measure: Percent (%)
  • Ideal Visualization(s): KPI trend with real-time alerts, Bullet chart, Pareto chart when ranking stations by utilization
  • Frequency: Hourly, with daily and weekly rollups
  • Data Required: Schedule database, antenna availability, maintenance calendar, contractual reservations
  • Pro Tip: Watch the gap between booked and executed minutes. Cancellations and reschedules quietly burn capacity that the booking number says is full.
  • Red Flag: High utilization with rising last-minute cancellations. The schedule looks full, but executed minutes are quietly draining and capacity planning is wrong.

Doppler Tracking Error

  • Why it Matters: LEO satellites move at orbital velocity. Bad Doppler tracking means lost lock and a useless pass.
  • What it Measures: The frequency offset between the predicted Doppler-compensated carrier and the actual received carrier during a tracked pass.
  • What Happens if Missed: Modems lose lock mid-pass, telemetry frames drop, and high-rate downlinks fail to close even when geometry is favorable.
  • Formula: |f_received – f_predicted|
  • Indicator Type: Leading. Tracking error climbs before lock is lost, giving you a short window to react.
  • Unit of Measure: Hertz (Hz)
  • Ideal Visualization(s): KPI trend with real-time alerts, XY scatter plot of error versus elevation, SPC trend
  • Frequency: Real-time, every second during pass
  • Data Required: Predicted Doppler, measured received frequency, reference oscillator status, modem lock status
  • Pro Tip: Compare Doppler error across passes for the same satellite. Persistent bias points to your reference, not the satellite.
  • Red Flag: Doppler error spikes only on specific satellites. Often your TLE source for that constellation is stale or low-priority in the pipeline.

HPA Forward Power Stability

  • Why it Matters: Unstable HPA output kills uplink quality and risks the amplifier itself. Both outcomes are expensive and visible.
  • What it Measures: The deviation of high-power amplifier forward output power from setpoint during active uplink, over a defined window.
  • What Happens if Missed: Uplink BER degrades, command rejections rise, and at the extreme you damage the HPA or the feed.
  • Formula: |P_forward – P_setpoint| / P_setpoint × 100
  • Indicator Type: Current. Live measurement of the transmit chain, with deviations almost always preceding a hard fault.
  • Unit of Measure: Watts (W) or percent deviation (%)
  • Ideal Visualization(s): KPI trend with real-time alerts, SPC trend, Bullet chart
  • Frequency: Real-time during transmit
  • Data Required: Forward power, reflected power, setpoint, HPA temperature, drive level
  • Pro Tip: Pair forward power with reflected power on one view. Swings without VSWR change usually mean the drive chain, not the antenna.
  • Red Flag: Forward power steady but reflected power climbing. That’s the antenna or waveguide telling you something cracked, iced, or shifted.

Why Real-Time Visibility Matters

Ground station operations live or die on what you can see during the pass, not after. A late AOS, a millidegree of pointing drift, an HPA twitching off setpoint: each one has minutes of warning before it costs you a customer minute. The teams that catch them in time are the ones with eyes on every link, every antenna, and every schedule slot, at the rate the satellites actually move.

The cost of operating blind isn’t theoretical. It’s a missed weather observation, a delayed Earth-observation tasking, a constellation operator looking at downtime credits and wondering whether your network is still the right one. The KPIs above are what turn a ground station from a reactive bottleneck into a predictable, sellable piece of capacity.

How Transpara Can Help

If real-time operational visibility is a challenge you’re facing, you’re not alone. At Transpara, we help teams like yours gain clarity from complex systems without the need to centralize or overhaul your data stack.
Learn more about Transpara
Browse our documentation
Contact us

10 Real-Time KPIs Every Pumped Hydro Storage Operations Leader Should Be Tracking

The gates and buttresses that gate every dispatch decision. In pumped hydro, a few centimeters of reservoir level is the difference between a profitable cycle and a missed market window

The gates and buttresses that gate every dispatch decision. In pumped hydro, a few centimeters of reservoir level is the difference between a profitable cycle and a missed market window.

Pumped hydro storage earns its margin in the gap between a market signal and a synchronized machine, and that gap closes fast when a unit refuses to swing into generate mode. Every second of delay is arbitrage revenue or ancillary services revenue walking out the door.

The expensive failures here are quiet ones. A drifting bearing temperature, an unnoticed cavitation pattern, a pressure transient nobody trended. Run a plant like this blind and you don’t lose dollars, you lose units for months while a stator gets rewound or a runner gets pulled. These ten KPIs are the ones every operations leader should have in front of them every shift.

Round-Trip Efficiency (RTE)

  • Why it Matters: RTE drives the core economics of the asset. A two-point drop on a 1 GWh cycle wipes out the day’s arbitrage spread.
  • What it Measures: Energy delivered during generation divided by energy consumed during pumping over a complete charge and discharge cycle.
  • What Happens if Missed: Silent efficiency loss erodes margin, and degraded runners or worn seals stay invisible until the next overhaul reveals them.
  • Formula: RTE = (MWh Generated / MWh Pumped) × 100
  • Indicator Type: Lagging. RTE confirms what already happened across a full charge and discharge cycle, but trended unit by unit it surfaces degradation early.
  • Unit of Measure: Percent
  • Ideal Visualization(s): KPI blocks, KPI trend with real-time alerts, Pareto chart when ranking units by RTE deviation, SPC trend (control chart)
  • Frequency: Per cycle (typically once daily, more often for fast-cycling units)
  • Data Required: Energy generated per cycle, energy pumped per cycle, cycle start and end timestamps
  • Pro Tip: Track RTE against head and load condition. A unit at part-load looks inefficient but may be operating exactly as designed.
  • Red Flag: A steady multi-week decline in RTE on a single unit while peers hold flat. Look at seal wear, runner cavitation, or instrument drift.

Upper Reservoir State of Charge

  • Why it Matters: State of charge defines how much energy you can dispatch and how much you can absorb. Get it wrong and you forfeit market position.
  • What it Measures: Usable storage between minimum and maximum operating levels, expressed as a percentage of total capacity.
  • What Happens if Missed: Bidders commit to dispatch that can’t physically be delivered, triggering market penalties and forcing emergency curtailment.
  • Formula: SoC = ((Current Level − Min Operating Level) / (Max Operating Level − Min Operating Level)) × 100
  • Indicator Type: Current. State of charge tells you exactly where the plant stands right now and what’s available for the next dispatch window.
  • Unit of Measure: Percent (and MWh equivalent)
  • Ideal Visualization(s): Bullet chart, KPI blocks, KPI trend with real-time alerts, Status history trends
  • Frequency: Real-time
  • Data Required: Upper reservoir level, lower reservoir level, reservoir geometry, current head, conversion factor to MWh
  • Pro Tip: Pair SoC with rolling 24-hour and 72-hour forecasts of price and inflow. Storage value depends entirely on when you plan to use it.
  • Red Flag: SoC drifts down between cycles without a matching pump schedule. Leakage, evaporation underestimation, or a metering error is the usual cause.

Unit Availability Factor

  • Why it Matters: A pump-turbine that can’t be called is worthless. Availability is what the market actually pays for through capacity and ancillary contracts.
  • What it Measures: Hours each unit was available for dispatch (pumping or generating) divided by total hours in the period.
  • What Happens if Missed: Forced derates and surprise outages erode capacity revenue and damage the operator’s standing in ancillary services markets.
  • Formula: Availability = (Available Hours / Period Hours) × 100
  • Indicator Type: Lagging. Availability is calculated after the fact, but daily and weekly views reveal patterns that predict the next forced outage.
  • Unit of Measure: Percent
  • Ideal Visualization(s): Bullet chart, KPI trend with real-time alerts, Pareto chart when ranking units by lost availability hours, Status history trends
  • Frequency: Hourly rollup, monthly summary
  • Data Required: Unit operating status, forced outage hours, planned outage hours, derate hours
  • Pro Tip: Track availability separately for pump mode and generate mode. Some failures only show up in one direction and a single number hides them.
  • Red Flag: A unit available in generate mode but repeatedly failing in pump mode. Motor starter, exciter, or dewatering system is usually the culprit.

Mode Transition Time

  • Why it Matters: Fast transitions unlock high-value ancillary services revenue. Every extra minute from standstill to synchronized is paid for by someone else’s faster plant.
  • What it Measures: Elapsed time from a dispatch signal to the unit reaching commanded MW output in the requested mode.
  • What Happens if Missed: Slow transitions disqualify the asset from frequency response markets and reduce its value in fast-ramping merit orders.
  • Formula: Transition Time = Time at Commanded Output − Time of Dispatch Signal
  • Indicator Type: Current. Each transition is its own event, and trending the population of transitions surfaces slow-developing problems.
  • Unit of Measure: Seconds (or minutes for slower units)
  • Ideal Visualization(s): Histogram, Box plot, KPI trend with real-time alerts, Pareto chart when ranking units by average transition time
  • Frequency: Per transition event
  • Data Required: Dispatch signal timestamp, sync timestamp, MW setpoint, actual MW output, mode flag
  • Pro Tip: Separate generate-to-pump and pump-to-generate populations. They share equipment but stress it in different ways and they degrade independently.
  • Red Flag: Mean transition time creeping up by even a few seconds per week. Guide vane servos, dewatering pumps, or breaker timing usually cause it.

Dispatch Compliance

  • Why it Matters: Market operators pay for the MW you bid, not the MW you deliver. Persistent under or over-delivery brings penalties and bid rejections.
  • What it Measures: Actual MW output versus scheduled MW output across each dispatch interval, expressed as deviation or accuracy percentage.
  • What Happens if Missed: Settlement charges accumulate quietly, and chronic deviation can disqualify units from future ancillary services participation.
  • Formula: Compliance = (1 − |Actual MW − Scheduled MW| / Scheduled MW) × 100
  • Indicator Type: Current. Compliance is judged per dispatch interval and aggregated daily for settlement and market reporting.
  • Unit of Measure: Percent (and MWh deviation)
  • Ideal Visualization(s): KPI trend with real-time alerts, SPC trend (control chart), Bar chart, Pareto chart when ranking units by deviation magnitude
  • Frequency: Per dispatch interval (typically every 4 to 5 minutes)
  • Data Required: Scheduled MW setpoint, actual MW output, dispatch interval timestamps
  • Pro Tip: Tag deviations with root cause when they happen. Reconstructing why a unit underdelivered at 14:22 three weeks ago is nearly impossible.
  • Red Flag: Compliance trending down only during high-head or low-head extremes. The unit’s operating curve has shifted and the bid model hasn’t caught up.

Pump-Turbine Bearing Vibration

  • Why it Matters: Bearing vibration is the earliest warning of mechanical trouble. Catching a rising trend prevents a multi-month forced outage to replace a thrust bearing.
  • What it Measures: Vibration amplitude at upper guide, lower guide, and turbine guide bearings, captured continuously during operation.
  • What Happens if Missed: A failing bearing seizes, damages the shaft, and pulls the unit out of service during peak market hours.
  • Formula: Vibration Amplitude = RMS displacement or velocity per ISO 7919 / ISO 10816 standards
  • Indicator Type: Leading. Vibration trends climb well before a bearing fails, giving the operations team weeks of warning when the data is watched.
  • Unit of Measure: Micrometers (displacement) or mm/s (velocity)
  • Ideal Visualization(s): KPI trend with real-time alerts, SPC trend (control chart), Bullet chart, Pareto chart when ranking bearings by amplitude
  • Frequency: Real-time during operation
  • Data Required: Bearing vibration sensor readings, shaft speed, MW load, mode, head
  • Pro Tip: Normalize vibration against load and head. Raw amplitude looks alarming at full output and benign at part-load when the underlying condition is identical.
  • Red Flag: Vibration rising at the same load and head conditions over consecutive starts. The mechanical condition is changing, not the duty.

Generator and Motor Stator Temperature

  • Why it Matters: Stator insulation life halves for roughly every 10 degrees Celsius of sustained overheat. Hot operation today is a rewind invoice tomorrow.
  • What it Measures: Temperature at stator winding RTDs and core iron, monitored across all phases, slots, and cooling circuits during operation.
  • What Happens if Missed: Insulation degrades, a phase fault eventually develops, and the unit goes offline for a stator rewind costing months of downtime.
  • Formula: N/A
  • Indicator Type: Current. Stator temperature reflects real-time thermal balance between losses and cooling, and trends surface slow cooling-system degradation.
  • Unit of Measure: Degrees Celsius
  • Ideal Visualization(s): KPI trend with real-time alerts, Bullet chart, SPC trend (control chart), Pareto chart when ranking slots by temperature
  • Frequency: Real-time
  • Data Required: Stator RTD readings per phase and slot, cooling water inlet and outlet temperature, MW load, ambient temperature
  • Pro Tip: Track the spread between hottest and coldest slot, not just the peak. A widening spread reveals cooling problems before any RTD alarms.
  • Red Flag: One slot consistently 5 degrees hotter than its neighbors. A blocked cooling duct or a developing local fault is the usual cause.

Penstock Pressure Transients

  • Why it Matters: Water hammer events damage penstocks, valves, and turbine runners. A single severe transient can crack a pipe or warp a wicket gate.
  • What it Measures: Peak and trough pressure deviations in the penstock during load changes, mode transitions, and emergency wicket gate closures.
  • What Happens if Missed: Cumulative transient damage goes undetected until a leak appears or a valve seat fails, both of which take the unit offline.
  • Formula: Pressure Transient = |Peak Pressure − Steady-State Pressure| during transition event
  • Indicator Type: Leading. Transient severity correlates directly with fatigue accumulation in penstock welds and turbine components.
  • Unit of Measure: Bar or kPa (and percent of design pressure)
  • Ideal Visualization(s): KPI trend with real-time alerts, Histogram, SPC trend (control chart), Pareto chart when ranking events by severity
  • Frequency: Per transient event, with real-time capture
  • Data Required: Penstock pressure sensors at multiple stations, wicket gate position, valve position, mode flag, MW output
  • Pro Tip: Tie every transient back to the operator action or trip that caused it. Operator habits and control tuning are easier to fix than steel.
  • Red Flag: Transient peaks rising over time at the same operating sequence. Guide vane closure rate, surge tank condition, or relief valve performance has shifted.

Starts and Stops per Unit

  • Why it Matters: Each start consumes a measurable fraction of bearing, shaft, and stator life. Cycling assets are bought and sold on this number.
  • What it Measures: Cumulative count of unit starts and stops by mode and start type, tracked against design-life budgets per component.
  • What Happens if Missed: Starts accumulate faster than maintenance plans assume, and the next major overhaul arrives before the budget cycle does.
  • Formula: Cumulative Starts = Σ (mode transition events per unit per period)
  • Indicator Type: Lagging. The count itself is historical, but tracked against design budgets it becomes a forward-looking maintenance and capital signal.
  • Unit of Measure: Count (and percent of design budget consumed)
  • Ideal Visualization(s): Bar chart, Bullet chart, KPI blocks, Pareto chart when ranking units by cumulative starts, Group rollup bars
  • Frequency: Real-time event, daily rollup
  • Data Required: Unit status transitions, mode flag, start type (cold, warm, hot), event timestamps
  • Pro Tip: Weight starts by severity. A cold start does more damage than a hot restart, and treating them as equal undercounts real wear.
  • Red Flag: One unit absorbing a disproportionate share of starts because dispatch logic always picks it first. Rotate duty before the asset pays the bill.

Auxiliary Load Ratio

  • Why it Matters: Aux loads quietly eat into RTE. Small motors and pumps can consume one to three percent of gross output and rarely get attention.
  • What it Measures: Auxiliary power consumption as a percentage of unit gross output during generation or gross input during pumping.
  • What Happens if Missed: Plant-wide efficiency drifts down, and the cause hides inside dozens of small motors and pumps nobody trends individually.
  • Formula: Aux Load Ratio = (Auxiliary Power Consumption / Gross Unit Power) × 100
  • Indicator Type: Current. The ratio updates continuously during operation and aggregates cleanly per cycle for efficiency analysis.
  • Unit of Measure: Percent
  • Ideal Visualization(s): KPI trend with real-time alerts, Bullet chart, Pareto chart when ranking auxiliary loads by consumption, SPC trend (control chart)
  • Frequency: Real-time
  • Data Required: Auxiliary power meter readings, gross unit power, operating mode, ambient conditions
  • Pro Tip: Break aux load into cooling, lubrication, drainage, and ventilation buckets. A creeping number on one bucket is a clear path to the root cause.
  • Red Flag: Aux load ratio elevated only during pump mode startup. Dewatering or air injection systems are running longer than they should.

Why Real-Time Visibility Matters

Pumped hydro storage is most lucrative when it acts fast and most expensive when it acts late. A unit that takes ninety seconds longer to synchronize, a bearing that nobody noticed climbing, a transient that crossed a threshold last Tuesday, these are not small problems. They are the difference between a profitable cycle and a missed market window, between a routine overhaul and a stator rewind.

Operating these assets without continuous, alerted KPIs means trusting that nothing important happened between morning reports. In a plant where every dispatch interval is a financial event and every start consumes measurable equipment life, that trust is not supported by the math. Real-time visibility, with alerts that fire on the conditions that actually predict trouble, turns a multi-hundred-megawatt machine from a black box into something you can run on intent rather than reaction.

How Transpara Can Help

If real-time operational visibility is a challenge you’re facing, you’re not alone. At Transpara, we help teams like yours gain clarity from complex systems without the need to centralize or overhaul your data stack.
Learn more about Transpara
Browse our documentation
Contact us

10 Real-Time KPIs Every Underground Mining Operations Leader Should Be Tracking

Underground at the working face: a Sandvik LH625iE electric LHD loads ore beneath ventilation duct and service cabling, the choke point where airflow, fleet availability, and ore production all meet in a single heading

Underground at the working face: a Sandvik LH625iE electric LHD loads ore beneath ventilation duct and service cabling, the choke point where airflow, fleet availability, and ore production all meet in a single heading.

In an underground mine, every meter of advance is a trade against air quality, ground stability, and water inflow you cannot see from the surface. The faces that pay the bills are also the ones most likely to surprise you.

When data takes hours to reach the operations leader, decisions get made on yesterday’s reality. A blocked airway, a stalled pump, or a creeping convergence trace becomes a shift-ender instead of a fix. These ten KPIs are the ones that should be in front of operations leaders in real time, every shift, every panel.

Ventilation Air Volume at Working Face

  • Why it Matters: Adequate airflow dilutes diesel particulate, gas, and dust. Without it, the face shuts down or workers get hurt.
  • What it Measures: Volumetric flow of fresh air reaching each active heading, compared to regulatory and design minimums.
  • What Happens if Missed: Workings exceed exposure limits, production halts under regulatory order, or workers face acute health events that trigger investigations.
  • Formula: Measured airflow at heading / Required airflow per regulation
  • Indicator Type: Leading. Airflow drops precede gas accumulation, so a falling trace gives operators time to act before exposure becomes a problem.
  • Unit of Measure: m³/s or cfm
  • Ideal Visualization(s): KPI blocks for active headings, KPI trend with real-time alerts, Pareto chart when ranking headings by airflow deficit
  • Frequency: Real-time
  • Data Required: Heading airflow, fan duty, regulator position, design ventilation requirement
  • Pro Tip: Tie airflow alerts to mobile fleet position so operations sees airflow per occupied heading, not per nominal heading.
  • Red Flag: A heading whose airflow drifts down across consecutive shifts without a known fan or door change. Something has shifted in the network.

Hazardous Gas Concentration at Face

  • Why it Matters: Methane, CO, and NO₂ spikes can ignite, intoxicate, or trigger evacuation. Real-time visibility is the difference between a controlled response and a casualty.
  • What it Measures: Concentration of regulated gases at active headings, return airways, and bleeders relative to action and statutory limits.
  • What Happens if Missed: Ignition sources meet flammable atmospheres, crews are exposed beyond TLV, or false alarms erode trust in the monitoring system.
  • Formula: Measured concentration / Statutory limit
  • Indicator Type: Current. Gas readings reflect what is happening now, but the rate of change also functions as a leading signal.
  • Unit of Measure: ppm or %
  • Ideal Visualization(s): KPI blocks per zone, KPI trend with real-time alerts, KPI Map showing concentrations by location, Pareto chart when ranking zones by exceedance frequency
  • Frequency: Real-time
  • Data Required: Sensor concentrations, sensor calibration status, fan operating state, blast schedule
  • Pro Tip: Alert on rate of rise, not just absolute level. A slow methane crawl matters before it crosses the action threshold.
  • Red Flag: Repeated CO spikes correlated with diesel equipment cycles. The fleet is undermaintained or the airway is undersized.

Development Advance Rate

  • Why it Matters: Development feeds future production. If meters per shift slip, the production schedule slips with them, often by months.
  • What it Measures: Linear advance achieved per active development heading per shift or day, against the planned advance rate.
  • What Happens if Missed: Stope sequences run out of prepared ground, mill feed gaps appear, and contractors fall behind on milestone payments.
  • Formula: Meters advanced / Planned meters per period
  • Indicator Type: Lagging. Advance is reported after the round is complete, but cycle-time analysis turns it into a leading signal.
  • Unit of Measure: m/shift or m/day
  • Ideal Visualization(s): KPI trend with real-time alerts, Group rollup bars by crew or contractor, Pareto chart when ranking headings by advance shortfall
  • Frequency: Per round or per shift
  • Data Required: Round length, rounds completed, scheduled meters, drilling and blasting cycle times, support installation status
  • Pro Tip: Track cycle component times (drill, charge, blast, muck, support) separately. Aggregate advance hides which step is bleeding hours.
  • Red Flag: A heading that meets advance targets but with deteriorating support installation rate. You are buying meters with future ground problems.

Ore Production Rate per Stope

  • Why it Matters: Stope production is the revenue line. Real-time visibility lets the operations leader rebalance the fleet before a slow stope becomes a missed shift.
  • What it Measures: Tonnes mucked from each active stope or production heading per shift, compared to the production plan.
  • What Happens if Missed: Mill feed runs short, blending strategy collapses, and idle fleet hours compound across the shift.
  • Formula: Tonnes mucked per stope / Planned tonnes per stope
  • Indicator Type: Current. Updates as bucket counts or weightometer data arrives, giving the shift control room time to redirect units.
  • Unit of Measure: t/shift
  • Ideal Visualization(s): KPI blocks per stope, KPI trend with real-time alerts, Pareto chart when ranking stopes by production deviation
  • Frequency: Real-time
  • Data Required: LHD bucket counts or payload, conveyor weightometer, ore pass levels, planned tonnes per stope
  • Pro Tip: Calibrate bucket factors per LHD operator. The same machine moves different tonnes in different hands, and the variance is not noise.
  • Red Flag: A stope hitting tonnes but trending down on grade. The crew is mucking dilution to make rate.

Ore Dilution

  • Why it Matters: Dilution turns paying tonnes into hauling cost. Every percent of waste in the ore stream is mill capacity, energy, and reagent burned for nothing.
  • What it Measures: Proportion of waste rock in the ore stream, calculated against the geological block model and reconciled with mill grade.
  • What Happens if Missed: Mill recovery drops, concentrate quality fails contract specs, and reconciliation variances destroy confidence in the resource model.
  • Formula: (Mucked tonnes – Planned ore tonnes) / Mucked tonnes
  • Indicator Type: Lagging. Dilution is confirmed after reconciliation, but draw point grade trends provide a leading signal during the shift.
  • Unit of Measure: % dilution
  • Ideal Visualization(s): KPI trend with real-time alerts, Group rollup bars by stope, Box plot for dilution distribution, Pareto chart when ranking stopes by dilution percentage
  • Frequency: Per shift, with reconciliation per cycle
  • Data Required: Mucked tonnes, planned ore tonnes, draw point grades, mill head grade, block model estimates
  • Pro Tip: Track unplanned dilution separately from planned dilution. The operations leader can only act on the unplanned portion.
  • Red Flag: Steady dilution creeps on a single stope while drill and blast parameters have not changed. Wall slough or oversize draw is in progress.

Mobile Equipment Availability

  • Why it Matters: Underground fleet is expensive, hard to swap, and bottlenecks the entire production cycle. Availability gaps translate directly into missed tonnes.
  • What it Measures: Ratio of time mobile equipment is available to operate against total scheduled time, by unit and by class.
  • What Happens if Missed: A single down LHD or truck stalls a stope sequence. Hot-seat plans collapse and contractors charge standby.
  • Formula: (Scheduled hours – Down hours) / Scheduled hours
  • Indicator Type: Current. Status updates from telemetry let operations and maintenance coordinate before the next shift change.
  • Unit of Measure: % availability
  • Ideal Visualization(s): KPI blocks per unit, Status history trends, Group rollup bars by equipment class, Pareto chart when ranking units by downtime hours
  • Frequency: Real-time
  • Data Required: Equipment operating state, maintenance work order status, fault codes, scheduled hours
  • Pro Tip: Distinguish between mechanical downtime, waiting on service, and waiting on heading. They have different owners and different fixes.
  • Red Flag: Repeated short-duration stoppages on a single unit across shifts. A failure is forming and the long stop is coming.

Shaft Hoisting Throughput

  • Why it Matters: The shaft is the choke point. Every tonne of ore and every person in or out of the mine moves through it.
  • What it Measures: Tonnes hoisted per hour and skip cycles per hour against rated capacity for production and service hoists.
  • What Happens if Missed: Ore stockpiles build at the loading pocket, shifts run short on workers underground, and emergency egress capacity becomes uncertain.
  • Formula: Skips hoisted per hour × skip payload
  • Indicator Type: Current. The hoist control system reports each cycle, allowing immediate response to load times or queue conditions.
  • Unit of Measure: t/h
  • Ideal Visualization(s): KPI blocks per hoist, KPI trend with real-time alerts, Histogram of cycle times, Pareto chart when ranking causes of hoist delay
  • Frequency: Real-time
  • Data Required: Skip cycle counts, payload per skip, loading pocket level, hoist availability state, cage occupancy
  • Pro Tip: Watch loading pocket fill rate as a leading indicator of upstream production. An empty pocket means a stope is in trouble.
  • Red Flag: Stable cycle count but rising mean cycle time. The hoist is masking a developing brake, rope, or skip-loading issue.

Mine Water Inflow vs Pumping Capacity

  • Why it Matters: Pumping water is one of the largest fixed costs underground. Losing the dewatering balance floods working areas and idles the lowest, often highest-grade levels.
  • What it Measures: Ratio of measured water inflow to active pumping capacity across the entire dewatering chain, level by level.
  • What Happens if Missed: Sumps overtop, electrical infrastructure floods, and lower levels are evacuated until pumping capacity is restored or augmented.
  • Formula: Total inflow / Active pumping capacity
  • Indicator Type: Leading. Inflow trends rise before sump levels become critical, giving time to start standby pumps or call out crews.
  • Unit of Measure: % of pumping capacity used
  • Ideal Visualization(s): KPI blocks per pump station, KPI trend with real-time alerts, Status history trends for pump state, Pareto chart when ranking stations by capacity used
  • Frequency: Real-time
  • Data Required: Pump flow rates, pump operating state, sump levels, motor current, inflow estimates by level
  • Pro Tip: Treat pump VFD output and motor current as health signals. A pump moving rated water at higher current is wearing out, not working harder.
  • Red Flag: Inflow climbing on a level that has not seen new development. You have intercepted a structure.

Seismic Activity and Ground Movement

  • Why it Matters: Rockbursts and falls of ground turn a shift into a fatality investigation. Real-time seismic data is the only early warning available.
  • What it Measures: Frequency, magnitude, and location of seismic events plus convergence and extensometer readings against ground control thresholds.
  • What Happens if Missed: Crews are exposed to unstable ground, exclusion zones are imposed reactively, and production areas are sterilized for re-entry protocols.
  • Formula: Event rate = N(M ≥ M_threshold) / Δt; Convergence rate = ΔDisplacement / Δt
  • Indicator Type: Leading. Event clustering and convergence acceleration precede major ground failures by hours to days.
  • Unit of Measure: Event count, local magnitude, mm/day
  • Ideal Visualization(s): KPI Map showing event location and magnitude, KPI trend with real-time alerts, Histogram of magnitudes, Pareto chart when ranking zones by event count
  • Frequency: Real-time
  • Data Required: Seismic event waveforms, event locations and magnitudes, extensometer and convergence readings, blast schedule
  • Pro Tip: Filter blast-induced events out of the trend. Otherwise alarm fatigue makes operators distrust the genuine signals when they arrive.
  • Red Flag: A migrating cluster of small events trending toward an active stope. Stress is redistributing and the next event may not be small.

Energy Consumption per Tonne Hoisted

  • Why it Matters: Underground mines are among the most energy-intensive operations on a per-tonne basis. Energy waste signals equipment problems and erodes margin.
  • What it Measures: Total electrical and diesel energy consumed per tonne of ore hoisted, broken down by major consumers (ventilation, pumping, hoisting, fleet).
  • What Happens if Missed: Demand charges spike, carbon reporting drifts, and degrading equipment runs unflagged because nobody is watching the consumption signal.
  • Formula: Total energy consumed / Tonnes hoisted
  • Indicator Type: Lagging at the period total, but real-time at the consumer level, where deviations indicate developing equipment issues.
  • Unit of Measure: kWh/t or MJ/t
  • Ideal Visualization(s): KPI trend with real-time alerts, Group rollup bars by consumer class, SPC trend (control chart) for stable consumers, Pareto chart when ranking consumers by share of total load
  • Frequency: Real-time at consumer level, daily and per-shift roll-ups
  • Data Required: Substation power readings, diesel fuel consumption, hoisting tonnes, consumer-level submetering
  • Pro Tip: Benchmark per consumer, not per mine. Total kWh/t is too noisy to drive decisions, while a fan or pump trending up gives a clear maintenance signal.
  • Red Flag: Hoisting energy per tonne climbing while tonnes per hour stays flat. Friction or rope condition is changing.

Why Real-Time Visibility Matters

Underground operations cannot be walked. The operations leader does not see the airflow dropping at a remote heading, the convergence opening on the back of a stope, or the pump current creeping up on a sump 800 meters below surface. Without real-time KPIs, those signals reach the surface as incidents instead of decisions.

The mines that run well are the ones where ventilation, ground, water, fleet, and production data converge in front of one shift control screen. When a leading indicator drifts, a person makes a call before the lagging indicator becomes a lost shift, a flooded level, or a rescue operation.

How Transpara Can Help

If real-time operational visibility is a challenge you’re facing, you’re not alone. At Transpara, we help teams like yours gain clarity from complex systems without the need to centralize or overhaul your data stack.
Learn more about Transpara
Browse our documentation
Contact us

10 Real-Time KPIs Every Stormwater Management Systems Operations Leader Should Be Tracking

image 598

Every section of pipe laid today becomes a sensor location tomorrow. Modern stormwater networks live and die by what operators can see in real time once construction crews leave the trench.

A stormwater network is fine until it isn’t, and the gap between those two states is measured in minutes. Rainfall arrives without negotiation, capacity is fixed, and every pump, gate, and basin has to perform on demand or fail in public. When a stormwater system runs blind, the consequences write themselves.

Streets flood, basements back up, outfalls discharge over permit limits, and pumps fail at the worst possible hour. By the time a daily report shows what happened, regulators, residents, and lawyers are already involved. The KPIs below are the ones an operations leader should be watching live, not pulling out of a monthly summary.

Catchment Rainfall Intensity

  • Why it Matters: Rainfall intensity drives every downstream decision. Knowing what’s hitting the ground now lets you stage pumps and clear storage before flow arrives.
  • What it Measures: Real-time precipitation rate across catchment rain gauges, typically expressed as inches or millimeters per hour.
  • What Happens if Missed: You react after the surge instead of before it. Pumps catch up rather than get ahead, and storage fills before gates can divert flow.
  • Formula: Rainfall depth / time interval
  • Indicator Type: Leading. Rainfall is the input that everything else in the system responds to.
  • Unit of Measure: in/hr or mm/hr
  • Ideal Visualization(s): KPI blocks, KPI trend with real-time alerts, GeoMap across rain gauges
  • Frequency: Real-time (every 1 to 5 minutes)
  • Data Required: Tipping bucket counts, rain gauge timestamps, gauge location, intensity thresholds
  • Pro Tip: Set tiered alerts on intensity, not just total volume. A half-inch in ten minutes hits the system harder than two inches over four hours.
  • Red Flag: Intensity climbing on multiple gauges simultaneously while pump stations are still in dry-weather mode.

Pump Station Wet Well Level

  • Why it Matters: Wet well level is the heartbeat of every lift station. It tells you if pumping is keeping up with inflow, second by second.
  • What it Measures: Real-time water depth in each lift station wet well, measured against high and low alarm setpoints.
  • What Happens if Missed: Levels climb past overflow setpoints and you find out from the public, not your control room.
  • Formula: N/A (direct measurement)
  • Indicator Type: Current. Reflects the active hydraulic balance between inflow and pumping capacity.
  • Unit of Measure: ft or m
  • Ideal Visualization(s): KPI blocks, KPI trend with real-time alerts, Pareto chart when ranking stations by deviation from setpoint
  • Frequency: Real-time (every 30 seconds to 1 minute)
  • Data Required: Wet well level transducer readings, high and low alarm setpoints, pump run status
  • Pro Tip: Watch the slope of the level curve, not just the absolute height. A flat-then-rising trace during a storm usually means a pump just dropped out.
  • Red Flag: Level rising while every pump shows running. Either a check valve has failed and a pump is coasting, or inflow has overrun installed capacity.

CSO Activation Frequency and Volume

  • Why it Matters: Combined sewer overflows are the most regulated event in your system. Volume and duration drive permit standing, public notification timelines, and consent decree obligations.
  • What it Measures: Number of overflow events at each CSO outfall and total volume discharged per event, per year.
  • What Happens if Missed: Late or inaccurate reporting becomes a compliance issue before it becomes an operational one. Penalties stack quickly.
  • Formula: Σ (Discharge flow × duration) per outfall per event
  • Indicator Type: Lagging. The event has to occur before it can be tallied, but real-time detection still drives response and notification.
  • Unit of Measure: count and gallons (or m³)
  • Ideal Visualization(s): KPI blocks, Bar chart by outfall, Pareto chart when ranking outfalls by volume, Tables for regulatory reporting
  • Frequency: Real-time during events, daily and monthly aggregates
  • Data Required: Outfall flow measurement, level above weir crest, activation duration, event start and end timestamps
  • Pro Tip: Tie every CSO activation to the upstream rainfall record automatically. Auditors will ask for that pairing every time.
  • Red Flag: Frequent low-volume activations from the same outfall during minor rain events. That points to upstream blockage or an undersized control structure.

Detention Storage Available

  • Why it Matters: Available storage is the buffer between inflow and discharge. It tells you how much rain the system can absorb before the network surcharges.
  • What it Measures: Remaining volume in each detention or retention basin relative to its full design storage capacity.
  • What Happens if Missed: Operations enters a storm with less buffer than expected and runs out of storage mid-event.
  • Formula: (Max storage – Current storage) / Max storage × 100
  • Indicator Type: Current. Reflects the immediate buffering capacity of each basin.
  • Unit of Measure: % or ft³ (m³)
  • Ideal Visualization(s): KPI blocks, Bullet chart against design capacity, KPI trend with real-time alerts, Pareto chart when ranking basins by remaining capacity
  • Frequency: Real-time (every 1 to 5 minutes)
  • Data Required: Basin level, basin stage-storage curve, design max storage, outflow rate
  • Pro Tip: Pre-storm drawdown is free capacity. Use forecast intensity to lower basin levels before the cell arrives.
  • Red Flag: Basin sitting above seasonal average level during dry weather. Outlet structure may be partially obstructed.

Sewer Surcharge Events

  • Why it Matters: Surcharge means pipes are running full and pressurized. Once surcharge reaches a manhole, you’re minutes from street flooding and basement backups.
  • What it Measures: Count and duration of events where the hydraulic grade line in a pipe exceeds the pipe crown elevation, by location.
  • What Happens if Missed: The first sign of trouble is water in basements or geysering manhole covers, not a screen alert.
  • Formula: Σ (Time HGL > pipe crown) per location per event
  • Indicator Type: Current. Surcharge happens in real time and resolves once flow drops back below pipe capacity.
  • Unit of Measure: count and minutes
  • Ideal Visualization(s): KPI blocks, Status history trends, Pareto chart when ranking pipe segments by surcharge duration, GeoMap across the network
  • Frequency: Real-time (every 1 minute)
  • Data Required: Pipe pressure and level sensors, pipe crown elevation, manhole rim elevation
  • Pro Tip: Track the lead time between rainfall peak and surcharge onset for each subbasin. That number is your operational window for proactive control.
  • Red Flag: Surcharge appearing in segments that didn’t surcharge during similar past storms. Usually a downstream constriction or new I/I source.

Outfall Turbidity at Discharge

  • Why it Matters: Turbidity is the most visible and most cited water quality parameter. Spikes at outfalls land directly on permit reports and public complaints.
  • What it Measures: Real-time turbidity at MS4 or treatment outfalls, typically reported in NTU at the point of discharge.
  • What Happens if Missed: Discharge events exceed permit limits without operations knowing until the lab pulls the next grab sample.
  • Formula: N/A (direct sensor reading)
  • Indicator Type: Current. Reflects in-stream water quality at the moment of measurement.
  • Unit of Measure: NTU
  • Ideal Visualization(s): KPI blocks, KPI trend with real-time alerts, SPC trend (control chart), Pareto chart when ranking outfalls by exceedance count
  • Frequency: Real-time (every 5 to 15 minutes)
  • Data Required: Turbidity sensor readings, outfall flow, permit thresholds, sensor calibration timestamps
  • Pro Tip: Pair turbidity with flow. High NTU at low flow means a sediment source upstream, not just first-flush wash-off from the storm.
  • Red Flag: Turbidity stays elevated long after rainfall stops. A construction site discharge or illicit connection is likely contributing.

Pump Cycling Frequency

  • Why it Matters: Excessive starts and stops are the leading cause of pump failure. High cycle counts predict motor and check valve problems before runtime reports show any wear.
  • What it Measures: Number of pump start events per hour or per day, calculated for each pump in each station.
  • What Happens if Missed: Pumps fail mid-storm because a small part wore out weeks earlier and nobody flagged the cycling pattern that predicted it.
  • Formula: Σ (Pump starts) / time interval
  • Indicator Type: Leading. Cycling patterns predict mechanical failure days or weeks ahead of breakdown.
  • Unit of Measure: starts/hour or starts/day
  • Ideal Visualization(s): KPI blocks, Histogram of cycle counts, Pareto chart when ranking pumps by cycles, Status history trends
  • Frequency: Real-time, rolled up hourly and daily
  • Data Required: Pump run and stop status, timestamps, runtime hours
  • Pro Tip: Rapid cycling during dry weather usually means the float or level controls are misaligned, not that demand is high.
  • Red Flag: Cycling rate doubling on a single pump while its lead and lag partner runs normally. That pump is doing more work and will fail first.

Pump Specific Energy

  • Why it Matters: Pumping is the largest controllable energy cost in stormwater operations. Specific energy reveals which stations and which pumps deserve attention first.
  • What it Measures: Energy consumed per unit volume pumped, calculated per pump or per station over a defined time window.
  • What Happens if Missed: Inefficient pumps run quietly for years, spending budget that could fund the next station rehab project.
  • Formula: kWh consumed / volume pumped (MG or m³)
  • Indicator Type: Lagging. Reflects performance over a completed pumping period rather than live operation.
  • Unit of Measure: kWh/MG or kWh/m³
  • Ideal Visualization(s): KPI blocks, Bar chart by station, Pareto chart when ranking pumps by specific energy, KPI trend with real-time alerts
  • Frequency: Hourly aggregation, daily and monthly rollups
  • Data Required: Pump motor power draw, flow rate per pump, runtime hours
  • Pro Tip: Compare specific energy across pumps in the same station. The outlier almost always traces to wear on the impeller or a partially closed isolation valve.
  • Red Flag: Specific energy creeping upward month over month at a station with no flow change. Mechanical degradation is in progress.

Infiltration and Inflow Rate

  • Why it Matters: Every gallon of groundwater or rainwater entering the sanitary side is one less gallon of capacity available for actual sewage during a storm.
  • What it Measures: Excess flow above dry-weather baseline attributable to groundwater infiltration and rainfall-derived inflow into the collection system.
  • What Happens if Missed: Treatment plants accept the cost, overflows accept the consequences, and source defects keep growing year over year.
  • Formula: Wet weather flow – Dry weather baseline flow
  • Indicator Type: Lagging. Calculated after a wet weather event by comparing flow against the established baseline.
  • Unit of Measure: MGD or m³/day
  • Ideal Visualization(s): KPI blocks, Bar chart by subbasin, Pareto chart when ranking subbasins by I/I contribution, XY/scatter plot of rainfall vs I/I response
  • Frequency: Calculated per storm event, rolled up monthly
  • Data Required: Flow at subbasin meters, dry-weather diurnal baseline, rainfall depth, groundwater elevation
  • Pro Tip: Plot I/I against antecedent moisture for each subbasin. Steep slopes point to inflow defects, while flat slopes with high baselines point to infiltration defects.
  • Red Flag: Subbasin I/I response getting worse across consecutive seasons. Pipe condition is deteriorating faster than rehab is keeping up.

Detention Basin Drawdown Time

  • Why it Matters: A basin that drains slowly isn’t ready for the next storm. Drawdown time tells you when the system is back to standby.
  • What it Measures: Time required for a detention basin to return from peak storage to its dry-weather operating level after a storm.
  • What Happens if Missed: Back-to-back storms hit a basin still partially full, and outlet controls can’t open fast enough to prevent surcharge.
  • Formula: t(level = operating baseline) – t(level = peak)
  • Indicator Type: Lagging. Measured along the recession limb of each storm event after the peak passes.
  • Unit of Measure: hours
  • Ideal Visualization(s): KPI blocks, KPI trend with real-time alerts, Bar chart by basin, Pareto chart when ranking basins by drawdown time
  • Frequency: Calculated per storm event
  • Data Required: Basin level over time, event start and end timestamps, outlet flow rate
  • Pro Tip: Compare drawdown across similar storms over the season. A growing drawdown time means the outlet is fouling.
  • Red Flag: Drawdown extending past design parameters with no upstream changes. The outlet orifice or flap gate is likely partially blocked.

Why Real-Time Visibility Matters

Stormwater operations live or die by what happens in the first thirty minutes of a storm. By the time a daily report shows a pump cycled too often or an outfall ran turbid for an hour, the regulatory clock has already started and the public has already noticed. Real-time visibility flips that timeline. Operators see rainfall climbing, storage filling, and pumps responding while the system can still be steered.

Operating blind in stormwater is expensive in ways that don’t show up on a single line item. CSO penalties, basement backup claims, emergency overtime, and accelerated pump rehabs all trace back to decisions that arrived a few minutes too late. Continuous KPIs across rainfall, hydraulic state, water quality, and asset performance give operations leaders the lead time and the evidence to act before those costs compound.

How Transpara Can Help

If real-time operational visibility is a challenge you’re facing, you’re not alone. At Transpara, we help teams like yours gain clarity from complex systems without the need to centralize or overhaul your data stack.
Learn more about Transpara
Browse our documentation
Contact us

10 Real-Time KPIs Every Data Center Operations Leader Should Keep on Their Radar

image 596

A dense server row with active power and network cabling throughout, where rack-level power density, inlet air temperature, and critical power path status determine whether every unit stays online or becomes the failure nobody saw coming.

A data center that loses power, overheats, or runs out of cooling capacity doesn’t fail slowly. It fails in minutes, and the consequences travel far beyond the facility floor. The challenge isn’t that these environments lack data. Every UPS, CRAC unit, PDU, and generator is generating a continuous stream of signals. The challenge is knowing which numbers actually matter, what they’re telling you right now, and what they predict if the trend holds.

Most operations teams are watching dashboards that tell them what happened. What you need to know is what’s about to happen. These ten KPIs cover the operational and infrastructure health signals that matter most in a data center. Track them in real time, alert on deviation, and you shift from reacting to leading.

Power Usage Effectiveness (PUE)

  • Why it Matters: PUE is the universal benchmark for data center energy efficiency. It reflects how much of your total facility power is actually reaching IT equipment, and where the rest is going.
  • What it Measures: The ratio of total facility power consumed to the power delivered to IT loads, with a perfect score of 1.0 meaning zero overhead loss.
  • What Happens if Missed: PUE drift goes unnoticed until the energy bill arrives. By then, the inefficiency had been compounding for weeks, often traced back to a cooling failure or change in IT load distribution that nobody flagged.
  • Formula: Total Facility Power (kW) / IT Equipment Power (kW)
  • Indicator Type: Current. PUE responds in real time to changes in cooling efficiency, IT load, and facility overhead, making it an immediate proxy for overall operational health.
  • Unit of Measure: Ratio (dimensionless)
  • Ideal Visualization(s): KPI trend with real-time alerts when PUE exceeds target threshold; bullet chart against facility PUE target; sparklines for shift-over-shift comparison.
  • Frequency: Real-time (per-minute rolling average)
  • Data Required: Total facility power draw (utility meter or PDU rollup), total IT equipment power (PDU branch circuit readings or server-level metering)
  • Pro Tip: Track PUE separately by zone or data hall if your facility has multiple cooling strategies. A single facility PUE hides localized inefficiencies that are costing you real money.
  • Red Flag: PUE rising during a period of stable IT load. That combination almost always points to cooling degradation: a failed CRAC unit, a blocked airflow path, or a chiller running outside its optimal range.

IT Load Utilization

  • Why it Matters: Knowing how close you are to your critical load ceiling is the difference between planned capacity expansion and an emergency that forces customer conversations you don’t want to have.
  • What it Measures: The percentage of total installed critical power capacity actively consumed by IT equipment across the facility or by zone.
  • What Happens if Missed: Operations teams that don’t track live load utilization routinely discover capacity constraints during provisioning requests or, worse, during a partial power path failure when N+1 redundancy suddenly matters.
  • Formula: Total IT Load (kW) / Total Critical Load Capacity (kW) × 100
  • Indicator Type: Current. Load utilization reflects live provisioning decisions and gives immediate warning when headroom is shrinking faster than planned.
  • Unit of Measure: %
  • Ideal Visualization(s): Bullet chart against capacity threshold targets (e.g., 70%, 80%, 90%); KPI trend with real-time alerts when utilization crosses defined thresholds; Pareto chart when ranking zones or data halls by load utilization percentage.
  • Frequency: Real-time (updated per PDU or metering scan cycle)
  • Data Required: Branch circuit power readings per PDU, total rated critical load capacity per zone, installed UPS capacity per bus
  • Pro Tip: Set your alert threshold well below nameplate capacity. At 80% utilization with an N+1 power path configuration, a single UPS module failure removes your redundancy before you’ve had a chance to respond.
  • Red Flag: Load utilization trending upward steadily without a corresponding provisioning event in the change log. Untracked power draw is a real phenomenon in environments with active deployment pipelines and manual processes.

Inlet Air Temperature

  • Why it Matters: Server inlet temperature is the thermal health signal closest to the equipment itself. Consistent overtemperature at rack inlets means servers are throttling performance or shutting down to protect themselves.
  • What it Measures: The air temperature at the front face of server racks, representing the air the equipment is actually drawing in for cooling.
  • What Happens if Missed: Sustained inlet temperatures above ASHRAE A1/A2 thresholds trigger server thermal events. In a dense compute environment, a single hot aisle containment breach can affect dozens of racks before anyone notices.
  • Formula: Measured Inlet Temperature (°C) vs. Target Range (18°C to 27°C per ASHRAE A2)
  • Indicator Type: Current. Inlet temperature responds within minutes to airflow changes, cooling failures, or containment breaches, giving a short but actionable window for response.
  • Unit of Measure: °C
  • Ideal Visualization(s): KPI trend with real-time alerts on high temperature deviation per zone; KPI Map overlaid on facility floor plan to visualize thermal hot spots spatially; Pareto chart when ranking rack rows by peak inlet temperature exceedance frequency.
  • Frequency: Real-time (continuous sensor polling)
  • Data Required: Temperature sensor readings per rack or per row (front of rack preferred), ASHRAE or OEM inlet temperature limits, cooling zone assignments
  • Pro Tip: Don’t rely solely on average inlet temperature. Track the maximum reading per row. A single outlier rack running 8°C above its neighbors often indicates a containment gap or a dead spot in airflow distribution, not a global cooling problem.
  • Red Flag: Inlet temperatures rising on one side of a hot aisle while the adjacent cold aisle remains within range. This pattern typically points to a specific CRAC unit that has failed or shifted into a degraded operating mode.

UPS Battery Runtime Reserve

  • Why it Matters: Your UPS battery runtime at current load is the only number that tells you how long you can sustain IT operations during a utility power failure before the generators must pick up the load. Get it wrong and the math is unforgiving.
  • What it Measures: The estimated runtime available from installed UPS battery systems at current IT load, accounting for actual battery state of health and current draw.
  • What Happens if Missed: A UPS reporting 10 minutes of runtime at nameplate capacity may only deliver 4 minutes at current load on an aging battery string. That gap is invisible until the transfer happens and the generator doesn’t start in time.
  • Formula: UPS Battery Capacity Available (kWh) / Current IT Load (kW) × Battery State of Health (%)
  • Indicator Type: Leading. Runtime reserve predicts your ability to ride through a power event before it occurs, not during it.
  • Unit of Measure: Minutes
  • Ideal Visualization(s): Bullet chart against minimum runtime SLA target; KPI trend with real-time alerts when runtime falls below minimum threshold; Pareto chart when ranking UPS modules by available runtime at current load.
  • Frequency: Real-time (continuous UPS polling)
  • Data Required: UPS battery state of charge (%), battery state of health (%), current IT load per UPS bus, rated battery capacity at nameplate, UPS efficiency factor
  • Pro Tip: Calculate runtime reserve per power bus, not just per facility. In an A/B feed configuration, you need both buses protected independently. A healthy facility average can hide a single bus that’s one bad battery string away from a gap.
  • Red Flag: Runtime reserve trending down over days without a corresponding increase in IT load. Battery capacity degradation is the cause, and it accelerates. A string that loses 15% capacity in a month will likely lose the next 15% faster.

Cooling Unit Availability and Redundancy Margin

  • Why it Matters: Cooling is the operational constraint that most data centers underestimate until they lose a unit. Knowing your live redundancy margin tells you exactly how much capacity you’d lose if the next failure happened right now.
  • What it Measures: The number of active cooling units (CRAC, CRAH, in-row coolers) running versus total installed, and the resulting N+x redundancy margin available at current IT load.
  • What Happens if Missed: A facility running at N+1 cooling with one unit already offline is effectively running with zero redundancy. Without live visibility into that state, the next failure becomes a thermal emergency, not a maintenance event.
  • Formula: (Total Installed Cooling Capacity (kW) – Load on Active Units (kW)) / Per-Unit Cooling Capacity (kW) = Redundant Unit Equivalent
  • Indicator Type: Current. Redundancy margin reflects the live operational state of the cooling infrastructure and changes the moment a unit trips offline or shifts into a degraded mode.
  • Unit of Measure: Number of equivalent redundant units (or %)
  • Ideal Visualization(s): Bullet chart against minimum redundancy target; KPI trend with real-time alerts when redundancy margin drops below N+1; status history trend to visualize cooling unit availability across a rolling 24-hour window.
  • Frequency: Real-time (updated on unit status change events)
  • Data Required: Cooling unit run/stop status per unit, rated cooling capacity per unit, actual cooling load per unit (return air delta-T or compressor power), total IT heat load
  • Pro Tip: Track cooling redundancy by zone independently from the facility aggregate. A facility showing N+2 overall can have a specific zone running at N+0 if units are unevenly distributed or a localized load spike has shifted the balance.
  • Red Flag: Cooling units cycling on and off at unusually short intervals. Short cycling signals a unit struggling to maintain setpoint, which accelerates compressor wear and is a reliable early warning of an imminent failure.

Generator Fuel Level and Auto-Start Readiness

  • Why it Matters: Generator readiness is a binary outcome: either it starts when utility power fails, or it doesn’t. Fuel level and last auto-start test result are the two leading indicators that tell you which outcome to expect.
  • What it Measures: Diesel fuel tank level as a percentage of capacity and the result and timestamp of the most recent auto-start test for each generator set.
  • What Happens if Missed: A generator that has never been tested under load in the past 90 days, or one sitting at 40% fuel during a winter storm, is an availability risk that no amount of UPS runtime compensates for fully.
  • Formula: Current Fuel Volume (L) / Tank Capacity (L) × 100
  • Indicator Type: Leading. Fuel level and test recency predict generator availability before a utility event occurs, when there’s still time to act.
  • Unit of Measure: % (fuel level); days since last test (readiness)
  • Ideal Visualization(s): Bullet chart against minimum fuel level threshold; KPI trend with real-time alerts when fuel drops below refill trigger level; table showing each generator’s last auto-start test date and result.
  • Frequency: Real-time (fuel level continuous; auto-start test result updated on test completion)
  • Data Required: Fuel tank level sensor per generator, generator run status, auto-start test result and timestamp, minimum fuel level specification, refill lead time
  • Pro Tip: Set your low-fuel alert threshold around your refill lead time plus one standard deviation of demand uncertainty. If refueling takes 24 hours to arrange and you’re running a 72-hour generator runtime target, a 50% alert threshold isn’t conservative enough.
  • Red Flag: A generator that starts on auto-test but fails to reach rated voltage or frequency within the specified transfer time. Starting is not the same as being ready. Transfer time compliance is the metric that actually validates grid-to-generator switchover.

Relative Humidity by Zone

  • Why it Matters: Humidity outside the acceptable operating band is a hardware risk that operates silently. Too low and you’re accumulating electrostatic discharge risk. Too high and you’re introducing condensation risk on active equipment.
  • What it Measures: Relative humidity percentage at defined monitoring points throughout the facility, compared against the ASHRAE-recommended operating envelope for data center environments.
  • What Happens if Missed: Humidity exceedances rarely cause immediate failures. They cause corrosion, accelerated component degradation, and ESD events that shorten hardware lifespan by months or years in ways that are impossible to attribute directly at the time.
  • Formula: Measured RH (%) vs. Target Range (40% to 60% RH per ASHRAE A2 guidelines)
  • Indicator Type: Current. Humidity responds to seasonal changes, cooling system operation, and facility airflow dynamics in real time.
  • Unit of Measure: % RH
  • Ideal Visualization(s): KPI trend with real-time alerts on high and low RH deviation; KPI Map overlaid on facility floor plan to identify zones drifting outside the acceptable band; Pareto chart when ranking zones by frequency of RH exceedance events.
  • Frequency: Real-time (continuous sensor polling)
  • Data Required: Relative humidity sensor readings per monitoring zone, dew point readings where available, ASHRAE operating envelope limits, humidifier and dehumidifier status
  • Pro Tip: Correlate humidity readings with cooling unit return air temperature. Cooling units running colder than setpoint can cause localized condensation risk even when facility-level humidity appears within range.
  • Red Flag: Humidity trending upward in a zone where cooling units are recently serviced. Refrigerant charge changes, coil cleaning, or set point adjustments during maintenance can shift the moisture balance in ways that don’t stabilize immediately.

Critical Power Path Availability

  • Why it Matters: Redundant power paths only protect you if both paths are live and healthy. An operations team that can’t see the real-time status of every segment from utility feed to rack PDU is operating on faith, not data.
  • What it Measures: The operational status of each segment of the critical power path, from utility entry through switchgear, UPS, static transfer switch, and PDU, to the point of load.
  • What Happens if Missed: Single points of failure hide inside a nominally redundant architecture whenever monitoring has gaps. A failed static transfer switch that nobody has confirmed is functional is not a redundant path. It’s a trap.
  • Formula: N/A
  • Indicator Type: Current. Power path availability reflects the live operational state of every component in the critical infrastructure chain and changes the moment any element degrades or trips.
  • Unit of Measure: Status (online / degraded / offline per segment)
  • Ideal Visualization(s): Status history trend showing power path health over a rolling 7-day window; KPI Map overlaid on single-line diagram to visualize the full path state; KPI trend with real-time alerts on any status change from normal.
  • Frequency: Real-time (updated on status change events)
  • Data Required: Breaker and switch status per segment, UPS bypass status, static transfer switch position, PDU health status, utility feed voltage and frequency
  • Pro Tip: Model your power path as a hierarchy in your monitoring system, not a flat list of devices. When a PDU goes offline, you want to know immediately which racks and circuits it feeds without having to trace it manually on a spreadsheet.
  • Red Flag: A power path segment showing degraded status during a period of normal IT load. Degraded status under low stress means that segment’s performance under a real switchover event is unknown, and unknown is not acceptable.

Rack Power Density

  • Why it Matters: Average power density across the facility tells you very little. Rack-level density tells you which racks are approaching their physical power and cooling limits, and which ones have room to grow.
  • What it Measures: The actual power draw per rack in kilowatts, compared against the rack’s rated power capacity and the cooling infrastructure’s ability to manage that heat load in that specific location.
  • What Happens if Missed: Deploying high-density compute into a rack that’s already at its cooling limit causes localized thermal events. That happens regularly in environments where provisioning and operations teams work from different data.
  • Formula: Actual Rack Power Draw (kW) / Rack Rated Power Capacity (kW) × 100
  • Indicator Type: Current. Rack density changes with every provisioning event and responds in real time to workload shifts in virtualized or cloud environments.
  • Unit of Measure: kW (absolute) and % of rated capacity
  • Ideal Visualization(s): Bullet chart per rack or per row against rated capacity; Pareto chart when ranking racks by power density percentage; KPI trend with real-time alerts when a rack exceeds defined density threshold.
  • Frequency: Real-time (per PDU outlet or branch circuit scan cycle)
  • Data Required: PDU outlet or branch circuit power readings per rack, rated circuit capacity per rack, cooling zone assignment and cooling capacity per zone
  • Pro Tip: Don’t evaluate rack density in isolation from cooling zone capacity. A rack at 6 kW in a zone designed for 8 kW average density is fine. The same rack in a zone designed for 4 kW average is a thermal problem in the making.
  • Red Flag: Rack power draw increasing steadily without a corresponding provisioning ticket. This usually reflects VM consolidation, workload migration, or an automated scaling event that the operations team wasn’t notified about.

Network Infrastructure Uptime

  • Why it Matters: Every compute workload in the facility depends on the network. A top-of-rack switch, spine link, or border router that goes down silently takes a portion of your customers’ services with it, regardless of how well everything else is running.
  • What it Measures: The operational availability of critical network infrastructure components, including core switches, spine and leaf layers, uplinks, and border connections, measured against uptime SLA targets.
  • What Happens if Missed: Network failures without real-time alerting are discovered by customers, not by operations. That sequencing is the definition of a bad day, and it’s entirely preventable.
  • Formula: (Total Monitored Component Hours – Downtime Hours) / Total Monitored Component Hours × 100
  • Indicator Type: Current. Network uptime reflects live device and link status and changes the moment a component or path degrades.
  • Unit of Measure: %
  • Ideal Visualization(s): KPI trend with real-time alerts on status change for any critical path component; status history trend to visualize availability patterns across a rolling 30-day window; Pareto chart when ranking network segments by cumulative downtime minutes.
  • Frequency: Real-time (continuous polling or event-driven on link state change)
  • Data Required: Device availability status per monitored component, link state per uplink and inter-switch connection, latency and packet loss where applicable, SLA uptime target
  • Pro Tip: Separate availability tracking for in-band management paths from out-of-band. When a switch goes down, you need your out-of-band management network to still be reachable so you can diagnose and recover without needing physical access to every affected device.
  • Red Flag: Uptime tracking at 100% for extended periods with no recorded events. That’s almost never accurate. It usually means monitoring coverage has gaps, polling intervals are too slow to catch brief link flaps, or alert thresholds are set too permissively.

Why Real-Time Visibility Matters

Data center operations run on assumptions until they don’t. The assumption that the generator will start, that the cooling has enough headroom, that the UPS runtime is adequate at current load. These assumptions are fine right up until the moment they aren’t, and the gap between assumption and reality is almost always visible in the data well before it becomes a failure. The ten KPIs above are the places where that gap shows up first.

Facilities that operate with real-time visibility across power, cooling, and infrastructure availability don’t avoid all incidents. They avoid the ones that were predictable. And in a data center environment where every minute of unplanned downtime carries a measurable cost and a reputational consequence, predictable and preventable are the only categories worth chasing.

How Transpara Can Help

If real-time operational visibility is a challenge you’re facing, you’re not alone. At Transpara, we help teams like yours gain clarity from complex systems without the need to centralize or overhaul your data stack.
Learn more about Transpara
Browse our documentation
Contact us

10 Real-Time KPIs Every Mine Crushing Operations Leader Should Be Tracking

image 588 scaled

A bucket wheel reclaimer moving crushed ore across a stockpile, where feed rate consistency and particle size distribution determine whether the downstream crushing circuit runs to plan or spends the shift recovering from avoidable throughput gaps.

Crushing is the first place a mine turns ore into money, and the first place it can bleed throughput without anyone noticing until it’s too late. When your primary and secondary crushers are running blind, you’re not just risking downtime. You’re compounding losses across every downstream process that depends on a consistent feed.

A crusher that’s underperforming by 8% doesn’t announce itself. It shows up quietly in your daily tonnage report, already past the point where intervention was easy. Real-time visibility on the right KPIs is what separates a crushing circuit that consistently hits plan from one that’s perpetually catching up. These ten KPIs are the ones that matter most in a crushing operation. Track them live, alert on deviation, and you’ll spend less time explaining shortfalls and more time running the plant.

Crusher Throughput Rate

  • Why it Matters: Throughput rate is your crushing circuit’s primary output metric. It tells you immediately whether you’re meeting plan or falling behind, before the gap becomes unrecoverable.
  • What it Measures: Tons per hour processed through each crusher stage, measured against a planned rate target.
  • What Happens if Missed: Shortfalls accumulate across shifts. A sustained 10% gap can erode weekly production targets in ways that no amount of overtime fully recovers.
  • Formula: Actual Throughput (tph) / Target Throughput (tph) × 100
  • Indicator Type: Current. This KPI reflects real-time operational output and triggers intervention decisions as conditions change.
  • Unit of Measure: % of target (or tph absolute)
  • Ideal Visualization(s): Bullet chart against daily target; KPI trend with real-time alerts when throughput drops below threshold; Pareto chart when ranking crushers by deviation from plan.
  • Frequency: Real-time (per-minute rolling average)
  • Data Required: Belt scale tonnage readings, crusher feed rate, target throughput value per shift plan
  • Pro Tip: Compare throughput rate against feed size variability. A throughput dip driven by oversized feed is a drill-and-blast problem, not a crushing problem.
  • Red Flag: Throughput trending down while power draw holds steady, which usually points to liner wear or a bridged feed.

Crusher Availability

  • Why it Matters: Availability directly caps your production ceiling. An unavailable crusher that wasn’t flagged early is always more expensive to recover than one that was caught on the way down.
  • What it Measures: The percentage of scheduled operating time a crusher is mechanically ready to run, excluding planned maintenance windows.
  • What Happens if Missed: Unplanned downtime cascades through the circuit fast. A primary that goes down without warning stops everything behind it within minutes.
  • Formula: (Scheduled Hours – Unplanned Downtime Hours) / Scheduled Hours × 100
  • Indicator Type: Lagging. Availability captures downtime events after they occur, but trending it in real time reveals deterioration patterns before the next failure.
  • Unit of Measure: %
  • Ideal Visualization(s): Bullet chart against availability target; KPI trend with real-time alerts on status change; Pareto chart when ranking crushers by cumulative unplanned downtime.
  • Frequency: Real-time (updated on status change events)
  • Data Required: Crusher run/stop status, scheduled hours per shift, fault event timestamps, maintenance mode flags
  • Pro Tip: Segment availability losses by cause code (mechanical, electrical, feed starvation, operator). Feed starvation losses that get logged as crusher downtime will distort your maintenance planning.
  • Red Flag: Availability tracking above 90% while mean time between stops is decreasing. Short, frequent stops are often a sign of an emerging mechanical issue that isn’t yet tripping a hard fault.

Crusher Power Draw

  • Why it Matters: Power draw is one of the best real-time indicators of what’s happening inside a crusher you can’t see. Deviations from the normal operating band expose feed, liner, and mechanical issues before they become failures.
  • What it Measures: Instantaneous electrical power consumed by the crusher drive motor, compared to its normal operating envelope.
  • What Happens if Missed: Running above the rated power band accelerates liner wear and risks motor overloads. Running consistently below it typically means the crusher is starved or the gap has drifted open.
  • Formula: Actual Power Draw (kW) / Rated Motor Power (kW) × 100
  • Indicator Type: Current. Power draw responds immediately to changes in feed hardness, size, and crusher mechanical condition.
  • Unit of Measure: kW (or % of rated)
  • Ideal Visualization(s): KPI trend with real-time alerts on high and low deviations; SPC trend (control chart) to visualize normal operating band and flag statistical anomalies; bullet chart against rated capacity.
  • Frequency: Real-time (per-second or per-scan)
  • Data Required: Motor current readings, motor voltage, power factor, rated motor nameplate values
  • Pro Tip: Establish a normal power envelope per feed material type. A crusher running a harder ore zone should draw more power. If it doesn’t, your feed control may be limiting throughput unnecessarily.
  • Red Flag: Rapid power draw spikes followed by sharp drops often indicate liner cracking or a tramp metal event. Treat them as maintenance triggers, not normal process noise.

Closed Side Setting (CSS)

  • Why it Matters: CSS defines your product size distribution before you ever measure it. Drifting CSS is the invisible force behind downstream grind inefficiency and classification problems.
  • What it Measures: The minimum gap between mantle and concave at the closed position of the crusher cycle, which controls maximum product particle size.
  • What Happens if Missed: CSS creep from liner wear produces coarser product than the circuit expects. The SAG or ball mill compensates by grinding harder, drawing more power for the same output.
  • Formula: Current CSS (mm) vs. Target CSS (mm)
  • Indicator Type: Leading. CSS deviation predicts product size outcomes before particle size analyzers confirm the problem.
  • Unit of Measure: mm
  • Ideal Visualization(s): KPI trend with real-time alerts when CSS exceeds tolerance band; bullet chart against target CSS setpoint.
  • Frequency: Real-time or per-cycle (depending on measurement method)
  • Data Required: Hydraulic cylinder position, CSS measurement system output, target CSS setpoint, liner wear compensation offset
  • Pro Tip: Track CSS drift rate against liner hours, not just absolute position. A liner wearing faster than expected signals a feed hardness change or an alignment issue worth investigating.
  • Red Flag: CSS trending wider than target while throughput appears normal. The crusher is still moving tons, but it’s sending oversize to a downstream circuit that wasn’t designed for it.

Feed Size Distribution (F80)

  • Why it Matters: What you feed into the crusher determines what you get out. Oversized feed is the leading cause of throughput loss, blockages, and unplanned stops in a primary crushing circuit.
  • What it Measures: The 80th percentile feed particle size entering the crusher, used to confirm the blast and ROM fragmentation are delivering material within crusher design limits.
  • What Happens if Missed: Oversized feed drives packing events and bridging, which force manual clearing and stop the circuit. Systematic oversize also accelerates liner wear and increases power draw.
  • Formula: F80 (mm) vs. Maximum Feed Size Limit (mm)
  • Indicator Type: Leading. F80 data flags a problem that started at the blast before it becomes a crusher problem.
  • Unit of Measure: mm
  • Ideal Visualization(s): KPI trend with real-time alerts when F80 exceeds crusher design limit; histogram of feed size distribution over a shift window.
  • Frequency: Real-time or per-truck cycle (camera/laser-based systems) or per-batch (manual or sample-based)
  • Data Required: Feed size analyzer output (camera system or laser profile), crusher maximum feed size specification
  • Pro Tip: Map F80 exceedances back to blast blocks and source headings. Recurring oversize from the same area is a fragmentation design problem, and it’s solvable before it repeats.
  • Red Flag: F80 within limits but frequent bridging events. Check your feed moisture content. Wet, fine-grained material can pack and arch in the crusher throat even when particle sizing looks acceptable.

Liner Wear Index

  • Why it Matters: Liner wear is the primary consumable cost driver in crushing, and it sets a hard deadline on crusher availability. Knowing your wear rate in real time lets you plan changeouts without surprises.
  • What it Measures: The estimated remaining liner life based on cumulative tons processed, CSS drift, and wear compensation data relative to the liner’s rated service life.
  • What Happens if Missed: Liners run past service life increase the risk of breakage, which converts a planned changeout into an unplanned shutdown with a much longer recovery timeline.
  • Formula: Cumulative Tons Processed Since Last Changeout / Rated Liner Life (tons)
  • Indicator Type: Lagging. Liner wear accumulates over time, but tracking it continuously drives proactive scheduling rather than reactive failure response.
  • Unit of Measure: % of rated liner life consumed
  • Ideal Visualization(s): Bullet chart against rated liner life; KPI trend with real-time alerts when liner wear index crosses 80% and 95% thresholds; Pareto chart when ranking multiple crushers by remaining liner life percentage.
  • Frequency: Updated per shift (or per material processed)
  • Data Required: Cumulative tonnage since last liner changeout, liner manufacturer’s rated life (tons), CSS drift value as a wear proxy, last changeout timestamp
  • Pro Tip: Normalize liner life to ore hardness (using Bond Work Index or equivalent) rather than just tons. Harder ore zones will burn through liners faster, and your scheduling should reflect that.
  • Red Flag: Liner wear index advancing faster than expected tonnage-per-day would predict. Check your feed sizing. Coarse, hard feed consumes liner life disproportionately compared to well-fragmented feed at the same tonnage.

Circuit Utilization

  • Why it Matters: Utilization tells you how much of your scheduled crushing capacity you actually used. It exposes idle time that availability and throughput metrics won’t always surface on their own.
  • What it Measures: The percentage of scheduled operating time the crusher is actively processing material, as distinct from being mechanically available but waiting on feed or operator intervention.
  • What Happens if Missed: High availability and low utilization is a common combination in undermanaged circuits. The crusher is ready to run; it’s just not running, and nobody is tracking why.
  • Formula: Crushing Hours (material in motion) / Scheduled Operating Hours × 100
  • Indicator Type: Current. Utilization reflects real-time operational decisions and upstream feed management effectiveness.
  • Unit of Measure: %
  • Ideal Visualization(s): Bullet chart against utilization target; KPI trend with real-time alerts when utilization drops below acceptable threshold; status history trend to visualize idle and active periods across a shift.
  • Frequency: Real-time (updated on feed presence / belt load confirmation)
  • Data Required: Crusher run/stop status, belt load or feed presence signal, scheduled hours, idle event timestamps and cause codes
  • Pro Tip: Break utilization losses into categories: feed starvation, scheduled maintenance, unplanned downtime, and operator delays. The biggest opportunity for improvement is almost always in feed starvation.
  • Red Flag: Utilization consistently dropping in the last two hours of a shift. This often reflects haul truck management decisions rather than a circuit issue, and it’s worth surfacing to the mine planning team.

Vibration Index (Bearing and Drive)

  • Why it Matters: Crusher bearings and drive components fail with warning signs that show up in vibration data well before they cause a breakdown. Catching the early-stage signature avoids the most expensive failure modes.
  • What it Measures: Vibration amplitude and frequency spectrum from key bearing housings and the crusher drive, compared against established baseline and alarm thresholds.
  • What Happens if Missed: Bearing failures in a crusher are rarely clean events. They typically involve secondary damage to the mainframe or drive components, which extends repair time from hours to days.
  • Formula: Current RMS Vibration Amplitude (mm/s or g) vs. Baseline and Alarm Limit
  • Indicator Type: Leading. Vibration signatures shift before mechanical failure occurs, giving a window for planned intervention.
  • Unit of Measure: mm/s RMS (or g peak)
  • Ideal Visualization(s): KPI trend with real-time alerts when vibration crosses warning and alarm thresholds; SPC trend (control chart) to identify deviation from normal vibration baseline.
  • Frequency: Real-time (continuous or high-frequency sampled)
  • Data Required: Accelerometer readings per bearing location, drive vibration sensor output, baseline vibration profiles per operating condition, alarm setpoints
  • Pro Tip: Establish separate vibration baselines for different CSS settings and feed conditions. Vibration naturally increases with coarser feed and tighter CSS. Alarming against a single static threshold will produce noise.
  • Red Flag: Vibration increasing progressively over multiple shifts without a corresponding change in feed or operational parameters. Progressive increase without a clear cause is a classic early-bearing-failure signature.

Lubrication System Oil Temperature

  • Why it Matters: The lubrication system is the life support of a crusher. Oil temperature outside the normal operating band tells you the system is either failing to cool or failing to flow, both of which end badly.
  • What it Measures: Supply and return oil temperatures in the crusher lubrication circuit, compared against operating limits defined by the equipment manufacturer.
  • What Happens if Missed: Overtemperature operation degrades oil viscosity and accelerates bearing wear. A lubrication failure in a running crusher causes rapid, severe mechanical damage that can write off major components.
  • Formula: Current Oil Temperature (°C) vs. High Limit (°C)
  • Indicator Type: Current. Temperature responds in real time to changes in crusher load, ambient conditions, and lubrication system performance.
  • Unit of Measure: °C
  • Ideal Visualization(s): KPI trend with real-time alerts on high temperature deviation; bullet chart against manufacturer’s high temperature limit.
  • Frequency: Real-time (continuous)
  • Data Required: Supply oil temperature sensor, return oil temperature sensor, ambient temperature, oil cooler status, flow rate confirmation
  • Pro Tip: Track the delta between supply and return oil temperature, not just absolute values. A rising delta at constant load often means flow rate is dropping before either temperature reading crosses its alarm limit.
  • Red Flag: Return oil temperature consistently running at the top of the normal band during mild ambient conditions. This usually means the oil cooler is fouled and needs cleaning before summer temperatures push it into alarm.

Product Particle Size (P80)

  • Why it Matters: P80 is the crusher’s output quality metric. It’s what you’re actually delivering to the grinding circuit, and deviations in either direction cost money downstream.
  • What it Measures: The 80th percentile particle size of crushed product leaving the circuit, measured against the target size required by the next process stage.
  • What Happens if Missed: Product that’s too coarse overloads the SAG mill and reduces grind efficiency; product that’s too fine can cause classification problems and increase circulating loads in ways that aren’t always obvious.
  • Formula: Measured P80 (mm) vs. Target P80 (mm)
  • Indicator Type: Current. P80 reflects the combined effect of CSS setting, liner wear, feed characteristics, and crusher performance in a single output value.
  • Unit of Measure: mm
  • Ideal Visualization(s): KPI trend with real-time alerts when P80 exceeds upper or lower tolerance; bullet chart against target P80; histogram of product size distribution across a shift window.
  • Frequency: Real-time or near-real-time (camera/laser-based systems); per hour (sample-based)
  • Data Required: Product size analyzer output (or belt camera system), target P80 specification, CSS current value, throughput rate
  • Pro Tip: Correlate P80 deviations with CSS and feed hardness data before adjusting settings. Not all P80 exceedances call for the same correction, and the wrong response makes things worse before they get better.
  • Red Flag: P80 holding on target while crusher power draw is elevated. You’re achieving the right product size but working harder than you should be to get it, which means liner wear or feed conditions are costing you energy efficiency.

Why Real-Time Visibility Matters

Crushing operations generate a continuous stream of process signals that shift faster than any shift report can capture. When throughput dips, power draw spikes, or a liner approaches end of life, the cost of discovering it four hours later is always higher than the cost of knowing it when it happens. The KPIs above exist precisely because each one represents a decision point: adjust, investigate, or keep running.

The difference between a crushing circuit that consistently meets plan and one that doesn’t is rarely the equipment. It’s whether the operations team has enough real-time context to make fast, correct decisions across the full cycle from feed management to liner changeout scheduling. Visibility is not a luxury in a high-throughput, asset-intensive environment. It’s the operating model.

How Transpara Can Help

If real-time operational visibility is a challenge you’re facing, you’re not alone. At Transpara, we help teams like yours gain clarity from complex systems without the need to centralize or overhaul your data stack.
Learn more about Transpara
Browse our documentation
Contact us