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

Tailings Management

Every tonne of ore on this belt ends its journey as tailings. The processing circuit gets the attention, but the facility downstream carries the risk.

A tailings facility rarely fails without warning. It fails without anyone watching the warnings. The warning signs live in millimeters of movement, liters per second of seepage, and centimeters of pond migration. When that data sits in monthly instrument rounds and quarterly spreadsheets, the facility drifts between reviews. Phreatic surfaces rise, beaches shrink, and deformation accelerates while everyone waits for the next report. The engineer of record sees a snapshot. The dam lives in real time.

These are the ten KPIs that belong on a live board, not in a quarterly binder.

Phreatic Surface Elevation

  • Why it Matters: The phreatic surface drives embankment stability. Every major dam failure review starts with the question of where the water was.
  • What it Measures: Piezometric water levels within the embankment and foundation, compared against design trigger levels at each instrument location.
  • What Happens if Missed: Elevated pore pressure quietly erodes your factor of safety. You find out during the investigation, not before it.
  • Formula: Measured piezometric elevation – Design trigger elevation (per instrument)
  • Indicator Type: Leading. Pore pressure rises days or weeks before deformation shows, which is exactly the window you need.
  • Unit of Measure: m
  • Ideal Visualization(s): KPI trend with real-time alerts per piezometer; Pareto chart when ranking piezometers by deviation from trigger level; KPI Map for spatial context across the embankment.
  • Frequency: Real-time from automated piezometers
  • Data Required: Piezometric elevations, design trigger and threshold elevations, instrument locations, pond elevation.
  • Pro Tip: Set alerts on rate of change, not just absolute level. A fast rise below the trigger beats a slow drift above it.
  • Red Flag: A piezometer that stops responding to rainfall events. A flat line usually means a dead instrument, not a stable dam.

Freeboard

  • Why it Matters: Freeboard is your buffer against overtopping, which remains the fastest route from normal operations to catastrophic release.
  • What it Measures: Vertical distance between the pond water surface and the lowest point of the dam crest.
  • What Happens if Missed: A design storm arrives with no buffer left. Overtopping erodes an embankment crest in hours, not days.
  • Formula: Lowest crest elevation – Pond water surface elevation
  • Indicator Type: Current. It states today’s buffer, and pairing it with forecast inflows makes it predictive.
  • Unit of Measure: m
  • Ideal Visualization(s): KPI block with status limits; bullet chart against minimum design freeboard; KPI trend with real-time alerts.
  • Frequency: Real-time
  • Data Required: Pond water level, surveyed crest elevations, minimum design freeboard, storm storage allowance.
  • Pro Tip: Track freeboard against the environmental design storm requirement, not just the operating minimum. Your regulator will.

Beach Above Water

  • Why it Matters: The beach keeps the pond off the embankment. It’s the cheapest stability control the facility has.
  • What it Measures: Distance from the dam crest to the decant pond edge, tracked separately for each deposition zone.
  • What Happens if Missed: The pond migrates against the embankment, saturating the shell and raising the phreatic surface where it hurts most.
  • Formula: Distance from crest to pond edge (per zone)
  • Indicator Type: Leading. Beach loss precedes phreatic rise, which precedes the stability problems everyone actually notices.
  • Unit of Measure: m
  • Ideal Visualization(s): KPI Map showing beach length by zone; Pareto chart when ranking deposition zones by deviation from minimum beach; KPI trend with real-time alerts.
  • Frequency: Daily, or per deposition cycle
  • Data Required: Pond edge position, crest alignment, minimum beach criteria per zone, active spigot status.
  • Pro Tip: Rotate spigots based on measured beach length, not the deposition schedule taped to the control room wall.

Embankment Deformation Rate

  • Why it Matters: Movement is the dam telling you something changed. The rate matters far more than the absolute displacement.
  • What it Measures: Displacement velocity at prisms, inclinometers, and radar monitoring points across the embankment and abutments.
  • What Happens if Missed: Accelerating creep gets rationalized as survey noise until the trend is unmistakable and your options have narrowed.
  • Formula: Change in displacement / Change in time (per monitoring point)
  • Indicator Type: Leading. Acceleration in deformation is the classic precursor to slope instability.
  • Unit of Measure: mm/day
  • Ideal Visualization(s): KPI trend with real-time alerts; SPC trend (control chart) to separate movement signal from survey noise; Pareto chart when ranking monitoring points by velocity.
  • Frequency: Real-time for radar, hourly to daily for prisms and inclinometers
  • Data Required: Displacement readings per monitoring point, timestamps, velocity thresholds, monitoring point coordinates.
  • Red Flag: Inverse velocity trending toward zero. That curve has a name in the literature, and it isn’t a reassuring one.

Seepage Flow Rate

  • Why it Matters: Seepage changes signal internal erosion or drain failure long before anything shows on the embankment surface.
  • What it Measures: Flow volumes at toe drains, weirs, and collection sumps, tracked per location against established baseline ranges.
  • What Happens if Missed: Piping starts small. By the time turbidity appears at the toe, internal erosion has a head start.
  • Formula: Measured flow rate vs Baseline range (per collection point)
  • Indicator Type: Leading. Deviations from baseline flag internal changes well ahead of visible distress.
  • Unit of Measure: L/s
  • Ideal Visualization(s): KPI trend with real-time alerts per weir; Pareto chart when ranking collection points by deviation from baseline; XY plot of seepage against pond elevation.
  • Frequency: Real-time or hourly
  • Data Required: Flow rates per collection point, baseline flow ranges, pond elevation, rainfall totals, seepage turbidity.
  • Pro Tip: Correlate seepage with pond level and rainfall. Flow that rises without a driver is the flow that matters.
  • Red Flag: A sudden decrease is as serious as an increase. A blocked drain pushes water somewhere you can’t see it.

Tailings Slurry Density

  • Why it Matters: Density controls beach slope, water load, and storage efficiency. It’s set upstream but paid for at the dam.
  • What it Measures: Percent solids by mass in the tailings discharge stream leaving the thickeners or cyclone circuit.
  • What Happens if Missed: Thin slurry sends extra water to the pond, flattens beaches, and burns storage volume you budgeted for solids.
  • Formula: (Mass of solids / Total slurry mass) × 100
  • Indicator Type: Current. It reflects thickener performance right now and shapes facility behavior for weeks afterward.
  • Unit of Measure: % solids (w/w)
  • Ideal Visualization(s): SPC trend (control chart) for shift-level stability; KPI trend with real-time alerts; histogram of density distribution by shift.
  • Frequency: Real-time
  • Data Required: Slurry density, discharge flow rate, solids throughput, thickener underflow density targets.
  • Pro Tip: Chase a density drop back to the thickener before adjusting deposition. Fixing the symptom at the dam costs more.

Deposition Rate vs Plan

  • Why it Matters: The deposition plan is the stability plan. Tonnes placed in the wrong cell undo months of beach development.
  • What it Measures: Actual tonnes deposited per zone or spigot against the deposition plan for the current period.
  • What Happens if Missed: Uneven raises, over-steepened beaches, and a facility geometry your engineer of record never signed off on.
  • Formula: (Actual tonnes deposited / Planned tonnes) × 100
  • Indicator Type: Lagging. It confirms placement after the fact, but sustained deviations predict every geometry problem that follows.
  • Unit of Measure: % of plan
  • Ideal Visualization(s): Group rollup bars by deposition zone; Pareto chart when ranking cells by deviation from plan; KPI trend with real-time alerts on cumulative deviation.
  • Frequency: Per shift
  • Data Required: Tonnes discharged per spigot or cell, deposition plan targets, discharge line status, active zone assignments.
  • Red Flag: One cell consistently over plan while its neighbors run under. Someone is choosing the convenient valve, not the right one.

Rate of Rise

  • Why it Matters: Rate of rise governs consolidation and strength gain. Raise faster than tailings consolidate and you’re building on mud.
  • What it Measures: Vertical rise of the tailings surface or embankment crest per unit time, tracked per zone.
  • What Happens if Missed: Under-consolidated layers with low shear strength stack up quietly inside the facility, waiting for a trigger.
  • Formula: Change in surface elevation / Change in time (per zone)
  • Indicator Type: Leading. Excessive rise rates today become stability and capacity problems on a predictable schedule.
  • Unit of Measure: m/year
  • Ideal Visualization(s): KPI trend with real-time alerts; bullet chart against the design maximum rise rate; Pareto chart when ranking zones by rise rate.
  • Frequency: Weekly, or per survey cycle
  • Data Required: Surface elevations per zone, survey timestamps, design maximum rise rate, deposited tonnage.
  • Pro Tip: Compare rise rate against pore pressure dissipation in the same zone. Consolidation sets your safe raise schedule, not the calendar.

Reclaim Water Quality

  • Why it Matters: Water quality is the compliance boundary of the facility, and exceedances become reportable events with regulators and communities watching.
  • What it Measures: pH, turbidity, conductivity, and dissolved metals in decant and seepage return water against permit limits.
  • What Happens if Missed: A quiet exceedance becomes a notice of violation, a discharge shutdown, or both at once.
  • Formula: Measured parameter value vs Permit limit (per parameter)
  • Indicator Type: Current. It reflects conditions now, and trending against limits provides early compliance warning.
  • Unit of Measure: Parameter-specific (pH units, NTU, µS/cm, mg/L)
  • Ideal Visualization(s): KPI blocks per parameter with status limits; KPI trend with real-time alerts; SPC trend (control chart) for slow drift detection.
  • Frequency: Real-time for online analyzers, per sample for lab parameters
  • Data Required: Analyzer readings per parameter, permit limits, sample locations, lab confirmation results.
  • Red Flag: Conductivity creeping upward in seepage return. Something new is dissolving, and you want to know what before the lab does.

Facility Water Balance

  • Why it Matters: Every tailings failure mode has water in the numerator. The balance tells you whether you’re storing more of it.
  • What it Measures: Net water inventory change: slurry water, precipitation, and runoff in, minus reclaim, evaporation, seepage, and discharge out.
  • What Happens if Missed: Inventory creeps up through a wet season until freeboard, beach, and phreatic KPIs all degrade at once.
  • Formula: Σ inflows – Σ outflows
  • Indicator Type: Leading. Inventory trends forecast freeboard and pond position weeks in advance.
  • Unit of Measure: m³/day (net change)
  • Ideal Visualization(s): KPI trend with real-time alerts on net inventory; bar chart of inflow and outflow components; KPI block for current inventory against storage allocation.
  • Frequency: Daily, with real-time inputs
  • Data Required: Slurry water volume, precipitation, runoff, reclaim volume, evaporation estimate, seepage volume, discharge volume.
  • Pro Tip: Run the balance against the wet-season forecast, not last year’s average. The design storm doesn’t care about averages.

Why Real-Time Visibility Matters

Tailings facilities punish slow feedback loops. A phreatic surface that rose in March but surfaced in the June instrumentation report gave you three months of eroding safety margin with no decisions made. The industry’s worst failures share a pattern: the data existed, the instruments worked, and the signal sat in a spreadsheet until it became a headline. Monthly rounds and quarterly reviews were built for a regulatory era that no longer exists.

Real-time KPIs collapse that lag to minutes. When piezometers, seepage weirs, pond levels, and deformation points stream into live views with alerts, the surveillance engineer sees the anomaly the day it starts, and the engineer of record reviews trends instead of snapshots. Trigger action response plans only work if the trigger fires when the threshold is crossed, not when someone compiles the report. That gap between the event and the awareness of it is where tailings risk actually lives.

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

How to Replace Your PI Historian Without Disrupting Operations

Data pipeline

Your PI historian keeps running while Transpara mirrors the data stream. No rip-and-replace, no downtime.

Replacing a historian that has been running for 20 years feels like open-heart surgery. The PI Data Archive touches everything: control systems feeding it live data through dozens of interfaces, the AF model that every engineer has spent years building out, PI DataLink reports that half the organization relies on, and PI Vision screens that took months to configure. Shut any of it down incorrectly and you lose operational continuity.

So most PI customers do nothing. They pay the Flex Credits renewal, watch the bill go up, and defer the problem to the next budget cycle.

The headline is that the migration doesn’t have to work that way. The choice depends on your objectives (get more value out of PI, reduce costs, improve scale, leverage more data sources, etc.). Replacing a PI historian is not a cutover event. It’s a series of discrete, reversible, low-risk phases, each one delivering value independently, none of them requiring you to turn off PI before the next one is ready. You control the pace. You define the scope of each phase before you start it. And if anything doesn’t behave as expected, you roll back that step without touching the rest of the system.

We assume you found this post because you are actively trying to replace PI due to cost, performance, slow development, or other issues. Just know that there are great ways to make this painless and always under your control.

This is the migration strategy Transpara customers use. It’s built around how PI actually works and what the realistic risks are at each step.

One last note before we dive in: You don’t have to replace PI at all to take advantage of everything Transpara does. We work in tandem with it and we are fans of PI. We just know that there are a lot of people looking for something more modern, scalable and with better commercial terms.

First: What You’re Actually Replacing

Before any migration planning, it helps to be precise about what “replacing PI” means. The AVEVA PI System is a family of products, not a single one, and different parts of that family have different replacement paths, different timelines, and different risk profiles.

  • PI Data Archive. The historian itself. This is where your time-series data lives. It’s what per-tag pricing is associated with. Replacing it with Transpara tStore (or any other historian) is the longest phase of the migration and usually the last step in the process.
  • PI Asset Framework (AF). The asset model, templates, Event Frames, and AF Analytics. This is where your engineering team’s intellectual property lives. Replacing it with tModel (Transpara’s graph-based asset model) is typically mid-migration.
  • PI Vision. The visualization layer. This is usually the first thing to replace and the one that delivers the fastest, most visible ROI. Transpara’s tView replaces it without touching the historian at all.
  • PI DataLink. The Excel add-in. Transpara has a native Excel add-in that pulls from tStore, PI, and every other connected source. This coexists with DataLink during migration.
  • PI Interfaces. The connectors to your control systems and DCS. These are the last components to migrate and require the most care. You take this last step once you are fully confident in the new platform and have tested everything extensively.

Most organizations don’t need to replace everything. Some replace PI Vision and leave PI Data Archive in place indefinitely. Some reduce their tag count to lower Flex Credits costs and keep the rest running. Some migrate completely over two to three years. The guide that follows covers the full path, but you can stop at any phase and you are always in control.

Before You Start: The Inventory You Need

A migration that skips the inventory phase runs into surprises that stall it. An afternoon of documentation work now prevents weeks of unplanned remediation later.

Tag inventory. Pull a full list of active tags from PI Data Archive. Note which ones are actually being read by applications versus which are archived but unused. Many PI deployments have accumulated tags over years that nothing actively queries. These don’t need to be migrated and shouldn’t consume your team’s time.

AF model(s). Understand the maturity of your AF structure: the number of element templates, the number of elements, which Event Frame definitions are in active use, and which analytics/calculations are still valid, up-to-date, and driving operational decisions. A mature AF implementation may have hundreds of templates and hundreds of thousands of elements. If you have a model you are happy with, this is easily brought into Transpara using the Remote Context Service feature of both Visual KPI and Transpara (even if you are keeping AF).

Interface inventory. List every PI Interface: what it connects to, which tags it feeds, how frequently it writes, and who owns the source system. This is your dependency map. Interfaces to legacy DCS platforms that no standard connector supports are the migration steps that require the most careful planning.

Downstream dependency inventory. Identify every application, report, dashboard, or integration that reads from PI. PI DataLink reports, custom PI SDK applications, PI Vision displays, third-party analytics tools with PI connectors, and anything reading via PI Web API. These represent the cutover commitments you’ll need to honor before retiring each PI component.

Compliance and data retention requirements. Some industries have specific requirements for how long operational data must be retained and in what format. If PI is your system of record for compliance purposes, understand those requirements before modifying it.

Visualization requirements. Understand what existing displays need to be kept as is, or those that can be improved via better visualization, KPIs, etc. Even if you plan to keep some PI Vision graphics, you can embed those in Transpara screens to keep the best of both worlds.

The Migration at a Glance: Where Everything Lives

Before the phase-by-phase detail, here is the whole journey on a single screen. At every stage, one question tells you exactly where you stand: where does each part of your operation actually live? Track four things, your data interfaces, your time-series data, your asset model, and your calculations, and the migration stops looking like one risky cutover and starts looking like four deliberate moves you make on your own schedule.

Every move is independent and reversible. You can sit at any sequence for as long as it serves you, and many customers do. Data moves into tStore only when there is a good reason to move it, and your model and calculations follow only when you are ready.

For the engineers who want the component-level view, each sequence switches on a specific set of platform parts. Sequence 1 reads in place through the PI Interface, the AF Interface, and the AF Remote Context Service (RCS). Sequence 2 adds the PI Extractor and tStore while still reading the model through the AF Interface, AF Data Reference, and RCS, and it brings tModel and tCalc online against that live AF model. Sequence 3 adds the AF Extractor so tModel and tCalc hold the model and calculations outright, with the PI Extractor still feeding data and tView driving the dashboards. Sequence 4 replaces the PI-specific connectors with Transpara’s own Interfaces and Extractors, leaving tStore, tModel, tCalc, and tView running with no PI components in the path at all.

SequenceData interfacesDataModel + model dataModel equationsWhat moves, and where it maps in this guide
1PIPIAFAFStarting point. Everything stays native to PI and AF, read in place. Maps to Phase 1, where you deploy Transpara alongside PI and change nothing in it. This is how it works with Visual KPI as well.
2PItStoreAFAFYour tag data now lives in tStore, pulled across by the PI Extractor. Your model and calculations stay in AF. Maps to Phase 2.
3PItStoretModeltCalcYour asset model moves into tModel and your calculations into tCalc. Data still originates from PI. Maps to Phases 3 and 4.
4tSystemtStoretModeltCalcTranspara’s own interfaces and extractors (tSystem) connect directly to your control systems. PI leaves the data path entirely, and you can retire it. Maps to Phase 6.

Phase 5 does not get its own row because it does not change where anything lives. It redirects the applications that read your data, the DataLink reports, the custom scripts, the dashboards, from PI to Transpara. Your data, model, and calculations stay exactly where Sequence 3 put them.

The Phase-by-Phase Migration Strategy

Each phase below is independent. You can complete Phase 1 and stop for six months before starting Phase 2. Every step is designed to be testable and rollback-safe before you proceed.

Phase 1: Deploy Transpara Alongside PI

What happens: You install Transpara in the same network environment as your existing PI Server. Nothing changes about PI. No tags move. No interfaces change. Transpara connects to PI Data Archive and PI AF using AVEVA’s published AF SDK, the same read interface that PI Vision and PI DataLink use.

What this gives you: Transpara’s tView starts generating real-time KPI dashboards from your PI data. Operators, managers, and executives who currently have no access to PI Vision get mobile-friendly, color-coded operational views immediately. The visualization ROI from Phase 1 alone typically justifies the Transpara investment in the first quarter.

Technical notes:

  • Transpara authenticates to PI using your existing PI trust or PI identity credentials. Your PI security model carries through unchanged.
  • The Remote Context Services (RCS) component reads your AF hierarchy and maps it into tModel. Your existing AF element structure, templates, and attributes are preserved. You don’t rebuild the model from scratch. This stays in sync with AF, so any changes you make on the AF side are reflected in Transpara automatically.
  • KPIs you define in tStudio (or in AF using the RCS) reference PI tags through the AF SDK in real time. Data is read from PI on demand, not stored in Transpara (yet).
  • Your PI admin sees Transpara as a read-only client to PI. Nothing in PI changes.
  • This isn’t just about PI. You can also add as many other data sources as you want, giving you a single, real-time operating view of all data, without the need to centralize or migrate any of it.

Risk level: Very low. Transpara is additive. Removing it at this stage requires only uninstalling the software.

When to move to Phase 2: When you’re confident in the connection stability, the model looks right, and your team is using tView in production.

Phase 2: Mirror PI Data Into tStore

What happens: You activate Transpara’s extractors to begin pulling PI tag values into tStore, Transpara’s time-series historian. The extractors run continuously, keeping tStore synchronized with PI Data Archive in real time. They also backfill historical data from PI into tStore, so tStore builds up a complete historical record matching what PI holds.

During this phase, both PI and tStore hold the same data. Your existing PI applications continue reading from PI exactly as before. Transpara applications can now read from either PI or tStore, and you can compare the two to verify data fidelity, scale, performance and more before making any cutover commitments.

What this gives you: A verified, production-tested mirror of your PI historian. At the end of Phase 2, tStore holds your full tag history, stays synchronized with PI in real time, and has been validated against PI’s own data. You can make the next migration decisions from a position of verified confidence rather than assumption.

Technical notes:

  • Extractors are distinct from interfaces. Interfaces read data from a source in place, without storing or migrating it. Extractors pull data from a source and write it into tStore, either as a primary data source or for other reasons (e.g. analytics or performance cache).
  • The PI extractor uses the AF SDK to read tag values and writes them into tStore with identical timestamps and data quality flags. Compression algorithms handle storage efficiency.
  • Backfill duration depends on your tag count, data density, and available network bandwidth. For large PI deployments or many years of history, backfill may run for days. During this time, both systems are fully operational.
  • You choose which tags to mirror and which to leave PI-only. Tags you’re considering decommissioning don’t need to be extracted.

Risk level: Low. PI continues running unchanged. tStore data can be validated against PI before any cutover.

When to move to Phase 3: When backfill is complete, data fidelity has been verified, and you’re ready to start migrating the model layer.

Phase 3: Migrate the AF Model to tModel

What happens: You transition from using RCS to read the AF model passively to fully migrating the AF structure into tModel. The graph-based tModel becomes the authoritative asset model for Transpara. Your existing PI AF stays in place and continues to be the data source for anything still reading from PI directly.

What this gives you: tModel now holds your full asset hierarchy, element templates, attributes, and relationships. Because tModel is a graph database rather than a relational model, it can represent relationships between assets across PI and non-PI sources in a way that AF cannot. This is where you start adding non-PI data sources to the same model: ERP data, LIMS results, IoT sensor feeds, and anything else that belongs in your operational picture alongside PI tags.

Technical notes:

  • The Transpara RCS automates the initial import. It reads your AF element structure, templates, and attributes and maps them into tModel’s graph structure. Relationships are preserved as graph edges rather than relational foreign keys.
  • When ready, tModel becomes Transpara’s authoritative model. AF remains unchanged and continues serving any applications still pointed at it.
  • You do not need to migrate every AF template at once. Start with the element types and process areas you actively use in tView. Migrate the rest as your team verifies each section.
  • AF Event Frames become first-class events in tModel. They can drive tCalc calculations, tView alerts, and dashboards exactly as they do in PI today.

Risk level: Low to medium. The AF model is being read and copied, not modified. AF continues to function for any application still using it.

When to move to Phase 4: When your tModel accurately reflects the AF structure and you’ve verified that tView dashboards built from tModel are correct.

Phase 4: Migrate AF Calculations to tCalc

What happens: You migrate your AF Analytics calculations, Performance Equations, and any custom logic that currently runs inside AF into Transpara’s tCalc engine. Each calculation is migrated, tested against the PI/AF result, and validated before the AF equivalent is retired.

tCalc is event-driven rather than schedule-based. Calculations trigger on data events, which makes them more responsive than AF’s polling-based execution for high-frequency process data. Python extensibility means any logic that was difficult to express in AF’s syntax can be rewritten cleanly.

What this gives you: Your calculated KPIs and other calculations now run in tCalc, pulling from tStore data rather than PI Data Archive. You’re no longer dependent on AF Analytics for your core calculations. Any new calculations you build going forward can leverage Python, integrate with AI models, and reference data from any source in your environment.

Technical notes:

  • Migrate calculations in groups by process area or template type, not all at once. Test each group against the AF result before deactivating the AF equivalent.
  • Some AF calculations reference PI-only data during transition. These continue to work via the PI interface until the underlying tags move to tStore in a later phase.
  • AF Performance Equations can generally be rewritten directly in tCalc’s no-code interface for simple expressions, or in Python for complex logic.
  • The RCS can assist with automated mapping of AF calculation templates to tCalc equivalents for common patterns.
  • Do not retire an AF calculation until the tCalc equivalent has been running in parallel and verified for a defined period, typically two to four weeks depending on your confidence threshold.

Risk level: Medium. This is where most of the intellectual property of your PI deployment lives. Work methodically through calculation groups with explicit validation criteria before retiring each one.

When to move to Phase 5: When tCalc covers all active calculations and tStore holds verified data for all tags feeding those calculations.

Phase 5: Redirect Downstream Applications

What happens: You update applications that currently read from PI to read from tStore or from Transpara’s query layer instead. This includes PI DataLink reports, any custom applications using the PI SDK or PI Web API, third-party tools with PI connectors, and any remaining PI Vision displays.

This is the phase that requires coordination with the most stakeholders. Every team that has a PI DataLink report, a custom script using the PI SDK, or a PI Vision display needs to know what’s changing, when, and what the equivalent is in Transpara.

What this gives you: Transpara becomes the primary data layer for operational data. PI Data Archive is still running, but nothing reads from it. At this point, you’re paying for PI but not using it. That’s the economic trigger for the next phase.

Technical notes:

  • The Transpara Excel add-in is a direct replacement for PI DataLink. It reads from tStore, tModel, and any other connected source using the same formula-based interface engineers are already familiar with.
  • Custom applications using the PI SDK or PI Web API can be migrated to Transpara’s query layer. The specifics depend on what those applications do. Some can be redirected to tStore’s REST interface. Others may require rewriting.
  • Third-party analytics tools with PI connectors can typically be redirected to tStore via its published APIs.

Risk level: Low risk but medium-high effort for individual applications, manageable in aggregate when phased by application group. Keep PI running in parallel until every downstream dependency has been verified on Transpara.

When to move to Phase 6: When all downstream applications have been verified on Transpara and no production reads are still going to PI.

Phase 6: Retire the PI Interfaces and Decommission PI Server

What happens: You replace PI Interfaces, the connectors from your control systems and DCS to PI Data Archive, with Transpara Extractors pointed directly at those same sources. Instead of data flowing to PI and then being read by Transpara, data flows directly into tStore.

Once the Extractors are running and verified, PI Data Archive has no live data flowing into it and no applications reading from it. You can decommission the PI Server at your discretion.

What this gives you: Zero dependency on AVEVA PI. No Flex Credits. No per-tag licensing. No PI admin overhead. Your tags and your history exist in tStore on infrastructure you control, priced on a model that doesn’t penalize you for tag count.

Technical notes:

  • The priority order for Interface migration is: start with sources where Transpara has a well-tested direct extractor, and leave the most complex or non-standard interfaces for last.
  • For proprietary DCS connections where no standard extractor exists, you have options: use the existing PI Interface as a bridge temporarily (read from PI into tStore while you build the direct path), replace with OPC-UA, MQTT, or Modbus where the DCS supports these, or commission a custom extractor for specific legacy sources (although Transpara supports hundreds already).
  • Historical data from before the extractor cutover date already lives in tStore from Phase 2. There is no gap in history at the handoff point.
  • PI Data Archive can be kept in a read-only state for a defined period after the extractors are running, giving you a rollback option if any interface produces unexpected data. When you’re satisfied, shut it down.

Risk level: The highest of any phase, concentrated in the interface-to-source migration step. Mitigate by migrating interfaces one at a time, running PI and the Transpara extractor in parallel until you verify data parity, and maintaining the rollback option until you’re confident.

What You Keep, and What Changes

At the end of a full migration, here’s the honest accounting:

What stays the same for your operations team: They still see process data, KPIs, trends, and dashboards. The data is the same data. The only difference is that it now comes from a modern platform with better, more flexible visualizations and the ability to use it on their phones or any other device.

What stays the same for your engineering team: The asset hierarchy and process structure carries forward from AF into tModel. Calculations that run in AF Analytics run in tCalc. Excel reports that use DataLink use the Transpara add-in. The intellectual work your team has put in over the years doesn’t disappear.

What changes: PI Vision screen-building becomes optional. KPI-centric views generate automatically or via drag and drop. Every operator and manager who previously had no access to PI data now has a real-time view on any device. Calculations that required specialized AF knowledge can now be built and maintained by any engineer who knows Python. And you stop receiving Flex Credits renewal invoices.

What you need to plan for: The PI admin skill set that manages your current deployment is specialized. That expertise is valuable during the migration and for maintaining tStore and tCalc afterward. The learning curve is real, though much shorter than the PI learning curve was. Transpara has no customers that require a dedicated full-time Transpara administrator, even on global deployments.

Frequently Asked Questions

How long does a full migration take? For most enterprise PI deployments, a full migration from first deployment to PI decommission takes 4 to 36 months. The range is wide because the pace is entirely customer-controlled. Organizations under active Flex Credits pressure tend to move faster through Phases 2 through 4. Organizations with complex, non-standard PI Interfaces to legacy hardware take longer on Phase 6. Most customers start seeing ROI within the first 30 days of Phase 1.

Do we have to migrate all our tags? No. A tag audit typically reveals that a meaningful percentage of tags in any long-running PI deployment are no longer actively read by anything. These don’t need to migrate. You pay for them in Flex Credits today; you don’t have to bring them forward. The migration is a natural opportunity to rationalize your tag inventory and only carry forward what earns its keep.

What happens to our 20 years of PI history? Your historical data backfills into tStore during Phase 2. The backfill process reads historical PI data and writes it into tStore with full fidelity, including timestamps and data quality flags. At the end of Phase 2, tStore holds your complete history going back as far as PI does. Nothing is lost.

What if we have a custom PI Interface to a legacy system? Custom or non-standard PI Interfaces to proprietary hardware are the most complex piece of any migration. You have three options: use the existing PI Interface as a temporary bridge while you build a direct Transpara path, migrate the source system to a standard protocol (OPC-UA, MQTT, Modbus) that Transpara supports natively, or work with Transpara to develop a custom extractor for the specific source. None of these require shutting down PI before the replacement is ready.

Can we migrate just PI Vision and keep PI Data Archive? Yes, and this is the most common first step. Phase 1 of this guide delivers exactly that: tView running on top of your PI data, giving your operators and managers modern mobile dashboards without touching anything in PI. Many customers stay at this configuration indefinitely because it solves their most urgent problem, better operational visibility, without requiring any data migration.

What does Transpara tStore replace technically? tStore replaces PI Data Archive as a time-series historian. It runs on the battle-tested foundation of PostgreSQL/TimescaleDB (but productized for industrial use and supportability by Transpara), operates on Linux via Kubernetes, and provides horizontally scalable, high-availability storage for industrial time-series data. It is a more modern and flexible version of PI. It includes all the fundamental historian capabilities: compression, interpolation, historical playback, and high-frequency data storage.

What is the rollback plan if something goes wrong? Each phase of this migration is designed with an explicit rollback. In Phases 1 through 4, PI continues running unchanged. Transpara is additive. If something doesn’t work as expected, you remove or revert the Transpara component without touching PI. In Phase 5, you maintain PI in parallel until every downstream application is verified. In Phase 6, you keep PI Data Archive in read-only mode until you’re satisfied with the extractor output. A full cutover only happens when your team has verified the replacement at each stage.

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 Zinc and Lead Processing Operations Leader Should Keep on Their Radar

Zinc and Lead Processing: An operator walks the cell tops of an electrolytic tankhouse, hunting shorts across thousands of live electrodes by hand. Real-time short-circuit and current efficiency KPIs decide whether that round confirms a healthy section or uncovers a shift's worth of metal already lost.

An operator walks the cell tops of an electrolytic tankhouse, hunting shorts across thousands of live electrodes by hand. Real-time short-circuit and current efficiency KPIs decide whether that round confirms a healthy section or uncovers a shift’s worth of metal already lost.

Zinc and lead processing is a chemistry business that pays its bills in electricity. Between the roaster, the leach circuit, the cell house, and the lead furnace, the margin lives in tenths of a percent, and every one of those tenths is moving right now. When this environment runs blind, the failures are quiet and expensive. Impurity breakthroughs surface as cathode losses a day later. Slag chemistry drifts until recovery takes the hit. Stack emissions creep toward permit limits while everyone waits for the monthly report. By the time a lagging number confirms the problem, the metal, the power, and sometimes the goodwill of the regulator are already gone.

The fix isn’t more reports. It’s a short list of KPIs, watched live, with alerts that reach the right person while the shift can still do something about it. Here are the ten that matter most.

Concentrate Feed Rate vs Plan

  • Why it Matters: Roasters and smelting furnaces set the pace for the entire plant. Feed you miss upstream is metal you never cast.
  • What it Measures: Actual concentrate tonnage fed to roasters and furnaces against the shift or daily plan, tracked per unit and plant-wide.
  • What Happens if Missed: Sustained shortfalls quietly erode monthly production targets. By the time the report lands, the tonnes are gone for good.
  • Formula: (Actual Feed Tonnes / Planned Feed Tonnes) × 100
  • Indicator Type: Current. It tells you right now whether the plant is on plan, while there’s still time in the shift to react.
  • Unit of Measure: % of plan
  • Ideal Visualization(s): KPI trend with real-time alerts; bullet chart against plan; Pareto chart when ranking feed units by shortfall
  • Frequency: Real-time, aggregated hourly
  • Data Required: Feed rates per unit, planned tonnage, concentrate moisture content, run status per roaster and furnace
  • Pro Tip: Track dry tonnes, not wet. Moisture swings in concentrate can hide a real feed shortfall for hours.
  • Red Flag: Feed rate holding plan while calcine output drops. That points to bed problems in the roaster, not the feed system.

Overall Zinc Recovery

  • Why it Matters: Recovery is the plant’s report card. A single point of recovery at a large operation is worth millions per year.
  • What it Measures: The percentage of zinc contained in feed concentrate that ends up as saleable cathode or finished metal.
  • What Happens if Missed: Zinc lost to leach residue, drosses, and effluent leaves as waste. Nobody refunds you for metal you already paid for.
  • Formula: (Zinc in Product / Zinc in Feed) × 100
  • Indicator Type: Lagging. It confirms performance after the fact, which is exactly why the leading KPIs around it matter so much.
  • Unit of Measure: %
  • Ideal Visualization(s): KPI block with target and status; SPC trend (control chart) with real-time alerts on daily values
  • Frequency: Daily reconciliation, with shift-level estimates
  • Data Required: Concentrate assays, feed tonnage, cathode production tonnes, residue assays and tonnage
  • Pro Tip: Watch residue assays as the fast proxy. Zinc climbing in leach residue shows up days before the monthly metal balance does.
  • Red Flag: Recovery trending down while every unit reports normal. That usually means your assay or weighing data has drifted, not the process.

Electrowinning Current Efficiency

  • Why it Matters: Power is the largest single cost in zinc production. Current efficiency decides how much of that power becomes metal.
  • What it Measures: Actual zinc deposited on cathodes as a percentage of the theoretical deposit predicted by Faraday’s law.
  • What Happens if Missed: Efficiency slipping from 92 to 88 percent burns the same power for less metal. The energy bill doesn’t shrink to match.
  • Formula: (Actual Zn Deposited / Theoretical Zn per Faraday’s Law) × 100
  • Indicator Type: Current. Calculated per harvest cycle, it reflects cell house health as it stands today, not last quarter.
  • Unit of Measure: %
  • Ideal Visualization(s): KPI trend with real-time alerts; bullet chart against target; Pareto chart when ranking cell sections by efficiency loss
  • Frequency: Per harvest cycle, typically every 24 to 72 hours, with intermediate estimates
  • Data Required: Cathode weights, cell current, plating time, number of cathodes per cell
  • Pro Tip: Correlate efficiency dips with purification upsets 24 to 48 hours earlier. The cell house usually pays for yesterday’s chemistry.
  • Red Flag: One cell section consistently lagging the rest. Look for shorts, manifold blockages, or electrode alignment before blaming electrolyte quality.

Specific Energy Consumption

  • Why it Matters: Electrowinning consumes roughly 3,000 kWh per tonne of zinc. Small percentage improvements translate directly into margin at plant scale.
  • What it Measures: Total electrical energy consumed per tonne of zinc cathode produced, tracked at cell house and whole-plant level.
  • What Happens if Missed: Creeping energy intensity gets absorbed as normal until the utility invoice forces the question. By then the root cause is cold.
  • Formula: Total kWh Consumed / Tonnes of Zinc Produced
  • Indicator Type: Current. It moves with cell voltage, current efficiency, and electrolyte condition in near real time.
  • Unit of Measure: kWh/t
  • Ideal Visualization(s): KPI trend with real-time alerts; histogram of daily values; bullet chart against budget
  • Frequency: Hourly, rolled up daily
  • Data Required: Rectifier power draw, cathode production tonnes, cell voltages, electrolyte temperature
  • Pro Tip: Track the cell voltage distribution, not just the average. A fat right-hand tail in the histogram is money leaking as heat.
  • Red Flag: Energy per tonne rising while current efficiency holds steady. Check anode condition and contact resistance before anything else.

Purified Electrolyte Impurity Levels

  • Why it Matters: A few milligrams of cobalt or antimony per litre can wreck a cell house shift. Purification quality decides electrowinning performance.
  • What it Measures: Concentrations of cadmium, cobalt, copper, antimony, and germanium in the purified electrolyte feeding the cell house.
  • What Happens if Missed: Impurity breakthrough triggers re-dissolution and hydrogen evolution on cathodes. You lose current efficiency and metal that was already plated.
  • Formula: N/A
  • Indicator Type: Leading. Electrolyte quality now predicts cell house performance over the next one to two days.
  • Unit of Measure: mg/L per impurity
  • Ideal Visualization(s): SPC trend (control chart) with real-time alerts per impurity; KPI Map showing all impurities at a glance
  • Frequency: Every 2 to 4 hours from lab or online analysis
  • Data Required: Electrolyte assays per impurity, zinc dust addition rate, purification tank temperatures, reaction residence times
  • Pro Tip: Alert on rate of change, not just absolute limits. A fast-rising cobalt trend deserves attention before it crosses the line.
  • Red Flag: Rising impurities alongside falling zinc dust consumption. Someone is under-dosing the purification circuit, deliberately or otherwise.

Cell House Short-Circuit Rate

  • Why it Matters: Every short circuit dumps current through a dead path instead of plating zinc. Shorts are efficiency loss you can actually see.
  • What it Measures: The number of active shorts detected per cell section each shift, from infrared scans or gaussmeter rounds.
  • What Happens if Missed: Persistent shorts overheat contacts, damage anodes and cathodes, and quietly drag efficiency down across an entire section.
  • Formula: Shorts Detected / Cells Scanned
  • Indicator Type: Current. It reflects the physical condition of the cell house right now, shift by shift.
  • Unit of Measure: shorts per 100 cells
  • Ideal Visualization(s): Group rollup bars by section; Pareto chart when ranking cell sections by short count; status history trend with real-time alerts
  • Frequency: Per scan round, typically every 2 to 4 hours
  • Data Required: Short counts per cell, cell section identifiers, time to clear, cell current
  • Pro Tip: Track time-to-clear alongside the count. Ten shorts cleared within the hour beat three left standing all shift.
  • Red Flag: Shorts clustering in cells fed by the same electrolyte manifold. That’s a distribution problem, not a random electrode issue.

Acid Plant SO2 Conversion Efficiency

  • Why it Matters: Roaster offgas becomes either sulphuric acid revenue or a stack emission problem. Conversion efficiency determines which one you get.
  • What it Measures: The percentage of SO2 in converter feed gas converted to SO3 across the catalyst beds.
  • What Happens if Missed: Falling conversion pushes stack SO2 toward permit limits. Exceedances risk fines, curtailment orders, and a very unwelcome regulator visit.
  • Formula: ((SO2 In – SO2 Out) / SO2 In) × 100
  • Indicator Type: Current. Continuous gas analysis makes this a live compliance and revenue signal at the same time.
  • Unit of Measure: %
  • Ideal Visualization(s): KPI trend with real-time alerts tied to permit thresholds; SPC trend (control chart) with real-time alerts; KPI block with status
  • Frequency: Real-time from continuous emissions monitoring
  • Data Required: Inlet SO2 concentration, outlet SO2 concentration, gas flow, catalyst bed temperatures
  • Pro Tip: Watch bed temperature spreads as the early warning. Catalyst degradation shows in the temperature profile before conversion visibly drops.
  • Red Flag: Conversion dipping every time roaster feed changes. Your gas strength is swinging harder than the acid plant can absorb.

Slag Zinc Content

  • Why it Matters: Zinc reporting to lead furnace slag is recoverable metal headed for the waste dump, or for the fumer at extra cost.
  • What it Measures: Zinc concentration in slag tapped from the lead blast furnace or direct smelting vessel, per tap or shift composite.
  • What Happens if Missed: High-zinc slag overloads the fuming circuit or leaves as permanent loss. Either way, recovery and cost both take the hit.
  • Formula: N/A
  • Indicator Type: Lagging. Each assay confirms furnace chemistry after the tap, so trend direction matters more than any single value.
  • Unit of Measure: % Zn
  • Ideal Visualization(s): SPC trend (control chart) with real-time alerts on composites; histogram of tap assays; XY/scatter plot against furnace temperature
  • Frequency: Per tap or per shift composite
  • Data Required: Slag assays, tap weights, furnace feed composition, reductant rate, furnace temperatures
  • Pro Tip: Pair slag zinc with furnace temperature at tap. Cold taps carry more zinc, and the correlation shows up fast on a scatter plot.
  • Red Flag: Slag zinc climbing while the feed blend is stable. Check reductant quality and tuyere condition before adjusting the recipe.

Lead-in-Air Concentration

  • Why it Matters: Airborne lead drives blood lead levels, regulatory exposure, and whether people can keep working in the area. Nothing outranks this one.
  • What it Measures: Airborne lead concentration in defined work zones, from fixed monitors and personal sampling, measured against occupational exposure limits.
  • What Happens if Missed: Exceedances mean medical removals, restricted zones, and regulatory intervention. Losing experienced smelter operators to blood lead is self-inflicted damage.
  • Formula: N/A
  • Indicator Type: Leading. Airborne readings today predict blood lead results weeks from now, while you can still intervene.
  • Unit of Measure: µg/m³
  • Ideal Visualization(s): GeoMap of monitor locations with live status; KPI trend with real-time alerts; Pareto chart when ranking work zones by exceedance count
  • Frequency: Real-time from fixed monitors; per campaign for personal samples
  • Data Required: Airborne lead readings per zone, ventilation flow rates, baghouse differential pressure, exposure limit thresholds
  • Pro Tip: Correlate spikes with specific tasks like drossing, launder cleaning, or baghouse maintenance. Most exposure comes from a handful of activities.
  • Red Flag: Rising zone readings with baghouse differential pressure trending abnormal. Your dust capture is failing before anyone files a complaint.

Critical Asset Availability

  • Why it Matters: The plant runs as a chain: roaster, leach, purification, cell house, casting. One weak link throttles everything downstream.
  • What it Measures: The percentage of scheduled time each critical asset actually runs, tracked per unit and rolled up plant-wide.
  • What Happens if Missed: Unplanned stops cascade fast. A casting crane failure backs up the cell house within hours, and delayed harvests cost efficiency.
  • Formula: (Runtime / Scheduled Time) × 100
  • Indicator Type: Current. Live run status tells you where the plant is constrained at this moment, not last month.
  • Unit of Measure: %
  • Ideal Visualization(s): Group Map of assets with live status; Pareto chart when ranking assets by downtime hours; status history trend with real-time alerts
  • Frequency: Real-time
  • Data Required: Run and stop status per asset, downtime duration, downtime reason codes, scheduled operating hours
  • Pro Tip: Rank by downtime cost, not just hours. An hour of roaster downtime and an hour of casting downtime are not the same money.
  • Red Flag: Availability high but throughput low across multiple assets. Equipment is running below rate, which the availability number will never show you.

Why Real-Time Visibility Matters

In zinc and lead processing, the expensive problems announce themselves quietly and early: a cobalt trend creeping up in purified electrolyte, a bed temperature spread widening in the acid plant, a cluster of shorts in one cell section. Caught within the hour, each is a routine adjustment. Caught at the daily meeting, it’s a lost shift of current efficiency, a permit conversation, or a fuming circuit running overtime to chase zinc that never should have reached the slag.

The ten KPIs above only earn their keep if they’re live, in context, and pushing alerts to the people who can act. A recovery number in a month-end spreadsheet is history. The same number trending on a screen in the control room, with a threshold and an alert behind it, is a decision you still get to make. That’s the whole difference between running the plant and reading about it afterward.

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 LNG Import Terminals Operations Leader Should Keep on Their Radar

LNG Import Terminals - An empty berth at dusk, unloading arms parked upright and cryogenic transfer lines cold, waiting on the next carrier's window. Every hour of that discharge runs against the clock, where live transfer rates and BOG headroom decide whether the cargo lands on plan or on demurrage.

An empty berth at dusk, unloading arms parked upright and cryogenic transfer lines cold, waiting on the next carrier’s window. Every hour of that discharge runs against the clock, where live transfer rates and BOG headroom decide whether the cargo lands on plan or on demurrage.

An LNG import terminal is a just-in-time business run at minus 162 degrees Celsius. Cargoes arrive on a schedule, the grid pulls on demand, and everything in between is cryogenic inventory that never stops trying to turn back into gas. When a terminal runs blind, the failures compound quietly. Boil-off creeps up, a vaporizer derates during a cold snap, a stratified tank sits primed for rollover, and the first anyone hears about it is a flare event or a curtailed nomination. By then the money is already gone.

The fix isn’t more reports. It’s a short list of KPIs, live, in front of the people who can act on them. Here are the ten that matter most.

Send-Out Rate vs. Nomination

  • Why it Matters: Send-out is the terminal’s product. Miss nominations and you’re facing imbalance penalties and shippers who remember at contract renewal.
  • What it Measures: Actual gas send-out to the grid compared against confirmed shipper nominations for the current gas day.
  • What Happens if Missed: Imbalance charges accrue, the grid operator intervenes, and your reliability record takes a hit that outlasts the gas day.
  • Formula: (Actual Send-Out Volume / Nominated Volume) x 100
  • Indicator Type: Current. Deviation shows up within the gas hour, leaving time to adjust the vaporizer lineup before penalties accrue.
  • Unit of Measure: %
  • Ideal Visualization(s): KPI trend with real-time alerts; bullet chart against the nominated target
  • Frequency: Real-time
  • Data Required: Send-out flow, confirmed nominations, gas day schedule, vaporizer throughput
  • Pro Tip: Track the cumulative intraday balance, not just the instantaneous rate. A flat deficit discovered at hour 18 is unrecoverable.
  • Red Flag: Repeated late-day catch-up ramps mean vaporizer availability, not grid demand, is shaping your send-out profile.

Boil-Off Gas (BOG) Rate

  • Why it Matters: BOG is product evaporating in place. Managed well, it feeds fuel or send-out. Managed poorly, it becomes flared money.
  • What it Measures: Volume of LNG vaporizing across tanks and lines, expressed as a percentage of stored inventory per day.
  • What Happens if Missed: Excess BOG overwhelms the compressors, tank pressure climbs, and you end up venting or flaring gas you already paid for.
  • Formula: (BOG Mass Flow / Total LNG Inventory Mass) x 100 per day
  • Indicator Type: Current. A rising BOG rate reflects heat ingress or pressure management problems happening right now, not last week.
  • Unit of Measure: % per day
  • Ideal Visualization(s): KPI trend with real-time alerts; SPC trend (control chart) to catch slow drift
  • Frequency: Real-time
  • Data Required: BOG compressor flow, tank pressures, LNG inventory levels, ambient temperature
  • Pro Tip: Baseline BOG per tank and per ambient temperature band. A tank drifting above its own baseline matters more than the site average.
  • Red Flag: BOG rising with stable ambient conditions and steady inventory points to insulation degradation or a passing valve.

Tank Inventory and Days of Cover

  • Why it Matters: Inventory is the buffer between cargo arrivals and grid demand. Too low risks curtailment; too high blocks the next cargo.
  • What it Measures: Current usable LNG volume across all tanks, translated into days of send-out at the forecast demand rate.
  • What Happens if Missed: You either curtail send-out waiting on a cargo or hold a laden carrier at anchor while demurrage accumulates.
  • Formula: Usable LNG Inventory / Forecast Daily Send-Out
  • Indicator Type: Leading. Days of cover projects forward, flagging supply gaps before they become curtailment events.
  • Unit of Measure: Days
  • Ideal Visualization(s): KPI block with sparkline; bullet chart against minimum and maximum operating bands
  • Frequency: Hourly
  • Data Required: Tank levels, tank densities, send-out rate, forecast demand, scheduled cargo arrivals
  • Pro Tip: Run cover against the demand forecast, not the trailing average. Cold snaps eat inventory faster than history suggests.
  • Red Flag: Cover repeatedly dipping below the planning threshold means your cargo scheduling assumptions no longer match demand reality.

Tank Stratification and Rollover Risk

  • Why it Matters: Rollover releases massive BOG in minutes and can lift relief valves. It’s the tank event nobody wants to explain afterward.
  • What it Measures: Density and temperature differentials between LNG layers in each tank, indicating stratification after mixing heel with new cargo.
  • What Happens if Missed: A sudden rollover overwhelms BOG handling, forces emergency venting, and can trigger a full terminal shutdown.
  • Formula: Density Differential = Bottom Layer Density – Top Layer Density
  • Indicator Type: Leading. Stratification builds over days after a cargo, giving ample warning before rollover conditions develop.
  • Unit of Measure: kg/m³
  • Ideal Visualization(s): KPI trend with real-time alerts per tank; table of layer densities and temperatures across tanks
  • Frequency: Every 15 minutes
  • Data Required: In-tank density profiles, temperature profiles by level, tank pressure, fill history
  • Pro Tip: Flag any incoming cargo whose density differs from the tank heel beyond your mixing threshold before unloading starts, not after.
  • Red Flag: Unusually flat BOG from a recently filled tank can mean vapor trapped under a stratified layer. That’s the quiet before rollover.

Ship Unloading Duration

  • Why it Matters: Berth windows are scheduled tight. Slow discharges cascade into delayed cargoes, demurrage claims, and inventory shortfalls downstream.
  • What it Measures: Elapsed time from arms connected to arms drained, benchmarked against the discharge plan for each carrier class.
  • What Happens if Missed: Demurrage accrues by the hour, the next arrival slips its window, and send-out planning unravels behind it.
  • Formula: Actual Discharge Duration – Planned Discharge Duration
  • Indicator Type: Lagging. The final number lands after the ship sails, so watch live transfer rate to catch a slow discharge mid-cargo.
  • Unit of Measure: Hours
  • Ideal Visualization(s): Bar chart by cargo; Pareto chart when ranking carriers by schedule deviation; KPI trend with real-time alerts on live transfer rate
  • Frequency: Per cargo, with real-time transfer rate during discharge
  • Data Required: Arm connection timestamps, transfer flow rates, ship pump pressures, vapor return flow, planned durations
  • Pro Tip: Watch the transfer rate curve in the first two hours. A slow ramp usually predicts the whole discharge running long.
  • Red Flag: The same carrier class consistently running long points to a vapor return or receiving constraint on your side, not theirs.

Vaporizer Capacity Utilization

  • Why it Matters: Vaporizers set your maximum send-out. Fouled or derated units quietly cap capacity right when winter demand peaks.
  • What it Measures: Actual regasification throughput per vaporizer against rated capacity, alongside approach temperature on ORVs and fuel efficiency on SCVs.
  • What Happens if Missed: You discover the missing capacity during a cold snap, curtail send-out, and shippers buy expensive replacement gas elsewhere.
  • Formula: (Actual Throughput / Rated Capacity) x 100
  • Indicator Type: Current. Approach temperature drift flags fouling as it develops, well before throughput visibly suffers.
  • Unit of Measure: %
  • Ideal Visualization(s): Group rollup bars across vaporizers; KPI trend with real-time alerts on approach temperature; Pareto chart when ranking vaporizers by capacity deviation
  • Frequency: Real-time
  • Data Required: Throughput per unit, gas outlet temperature, seawater inlet and outlet temperatures, fuel gas consumption
  • Pro Tip: Trend ORV approach temperature by season. Marine fouling accelerates in warm months and shows up as a slow, steady climb.
  • Red Flag: Outlet temperature hunting near the low-limit trip means you’re one demand spike away from a cold gas excursion.

BOG Compressor Availability and Spare Capacity

  • Why it Matters: BOG compressors are the pressure relief you actually want to use. Lose one and flaring becomes your fallback plan.
  • What it Measures: Running status, load, and remaining spare capacity across the BOG compressor train, measured against current BOG generation.
  • What Happens if Missed: Tank pressure rises unchecked during unloading, forcing flaring or, worse, a discharge stoppage mid-cargo.
  • Formula: Spare Capacity = Total Available Compressor Capacity – Current BOG Load
  • Indicator Type: Current. Spare capacity is what stands between a routine unloading and a flaring event tonight.
  • Unit of Measure: %
  • Ideal Visualization(s): KPI blocks per compressor; bullet chart for spare capacity; status history trends for availability
  • Frequency: Real-time
  • Data Required: Compressor running status, suction pressure, throughput per machine, BOG generation rate
  • Pro Tip: Check spare capacity against forecast BOG for the next unloading, not current generation. A discharge can double BOG within an hour.
  • Red Flag: Frequent recycle valve operation at low load signals a machine running outside its envelope and heading for a trip.

Send-Out Gas Quality (Wobbe Index)

  • Why it Matters: Off-spec gas gets rejected at the grid entry point. One quality excursion can shut in the entire terminal.
  • What it Measures: Wobbe Index and heating value of send-out gas against grid entry specifications at each export point.
  • What Happens if Missed: The grid operator closes the entry valve, send-out stops, and every downstream nomination fails at once.
  • Formula: Wobbe Index = Higher Heating Value / sqrt(Specific Gravity)
  • Indicator Type: Current. Quality shifts with cargo blend and nitrogen injection, so live measurement is the only real defense.
  • Unit of Measure: MJ/Sm³
  • Ideal Visualization(s): SPC trend (control chart) with real-time alerts; bullet chart against specification limits
  • Frequency: Real-time
  • Data Required: Gas chromatograph composition, heating value, specific gravity, nitrogen injection rate
  • Pro Tip: Watch the quality trajectory during tank switchovers. Rich heel blending into a lean cargo is where most excursions start.
  • Red Flag: Steadily rising nitrogen injection to hold spec means the cargo mix is drifting rich and your ballasting headroom is shrinking.

Flare and Vent Volume

  • Why it Matters: Every flared cubic meter is purchased product destroyed, plus emissions your regulator and your neighbors both count.
  • What it Measures: Total gas volume flared or vented, coded by cause: pressure relief, maintenance, compressor trips, or unloading peaks.
  • What Happens if Missed: Chronic flaring erodes margin, breaches emissions permits, and hands the regulator a reason to look closer.
  • Formula: Sum of Flare and Vent Meter Volumes per Period
  • Indicator Type: Lagging. The gas is gone, but cause-coded totals point straight at the upstream failures worth fixing.
  • Unit of Measure: Sm³
  • Ideal Visualization(s): Pareto chart when ranking flare events by cause; KPI trend with real-time alerts on flare flow
  • Frequency: Real-time, totalized hourly
  • Data Required: Flare meter flow, vent valve positions, event cause codes, compressor trip records
  • Pro Tip: Assign a cause code to every flare event within the shift. Uncoded events become unfixable statistics within a week.
  • Red Flag: A rising baseline flare with no logged events usually means a passing relief valve, not an operational cause.

Energy Intensity per Unit of Send-Out

  • Why it Matters: Regasification margins are thin. Fuel gas and power are your largest controllable costs after the LNG itself.
  • What it Measures: Total fuel gas and electrical energy consumed per unit of gas sent out, across the whole terminal.
  • What Happens if Missed: Creeping intensity quietly compounds into a material margin hit long before the monthly report catches it.
  • Formula: (Fuel Gas Energy + Electrical Energy) / Send-Out Volume
  • Indicator Type: Current. Intensity moves with the vaporizer lineup and pump scheduling decisions operators make every shift.
  • Unit of Measure: kWh/Sm³
  • Ideal Visualization(s): KPI trend with real-time alerts; histogram by operating mode; Pareto chart when ranking consumers by energy per unit
  • Frequency: Hourly
  • Data Required: Fuel gas flow, electrical power consumption, send-out volume, running equipment lineup
  • Pro Tip: Normalize by send-out band before comparing shifts. Intensity at 30% turndown will always look ugly; compare like with like.
  • Red Flag: Intensity rising at constant send-out and lineup means an individual consumer, often a pump, is quietly degrading.

Why Real-Time Visibility Matters

An import terminal doesn’t fail loudly. It fails through a stratified tank nobody profiled, a vaporizer that derated over a fouling season, and a BOG train that had no spare capacity the night a Q-Max came alongside. Each of these announces itself days or weeks in advance, but only in live data. Monthly reports tell you what the flare already burned.

The ten KPIs above share one trait: they’re all actionable while the situation is still cheap to fix. Days of cover moves before curtailment does. Density differentials move before rollover does. Approach temperature moves before the cold snap arrives. Put them in front of the shift, with alerts, and the terminal stops running on surprises.

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 Ammonia Production Operations Leader Should Be Tracking

Ammonia Production - Every kilogram of gas that leaves these columns feeds the synthesis loop, so what you can and cannot see at this stage sets the ceiling on conversion, energy, and catalyst life.

Every kilogram of gas that leaves these columns feeds the synthesis loop, so what you can and cannot see at this stage sets the ceiling on conversion, energy, and catalyst life.

Ammonia is one of the most energy-hungry molecules made at industrial scale, and the margin lives in the last few percent of efficiency. Whether the hydrogen comes from natural gas or from an electrolyzer, the synthesis loop behaves the same way: it rewards steady, precise operation and punishes drift. The failure modes are quiet. Catalyst poisons slip through and do their damage months before conversion visibly drops. Energy creeps up while rates look fine. A hot spot builds in a converter bed or a reformer tube while the control room watches averages. By the time these show up in a monthly report, the tonnes and the catalyst life are already gone.

The KPIs below focus on what an ammonia operations leader needs to see while there is still time to act, across both green and grey plants.

Ammonia Production Rate vs Plan

  • Why it Matters: Production rate against plan tells you whether the plant is earning or bleeding margin every hour it runs. Everything downstream depends on it.
  • What it Measures: Actual ammonia output over a period compared to the planned or nameplate target for that same window.
  • What Happens if Missed: Sustained shortfalls quietly erode monthly volume and contracts. By the time reports catch it, the tonnes are already gone.
  • Formula: (Actual NH3 Output / Planned NH3 Output) x 100
  • Indicator Type: Lagging, but it moves fast enough to act on within a single shift if you watch it live.
  • Unit of Measure: Percent of plan (%)
  • Ideal Visualization(s): KPI trend with real-time alerts, bullet chart against target.
  • Frequency: Real-time, rolled up hourly and per shift.
  • Data Required: Ammonia product flow, plan target rate, on-stream hours.
  • Pro Tip: Watch load factor beside energy use. Green plants chase available renewable power and drift off target if nobody flags the trade-off.
  • Red Flag: Output holding steady while feed or power climbs. You are paying more for the same tonnes.

Specific Energy Consumption

  • Why it Matters: Energy is the single largest variable cost in ammonia. A small drift across a large plant burns real money daily.
  • What it Measures: Total energy input per tonne of ammonia produced, whether that energy arrives as natural gas or as electricity.
  • What Happens if Missed: Efficiency losses hide inside normal operation. You keep making product while margin leaks through fouled exchangers and aging catalysts.
  • Formula: Total Energy Input / Tonnes NH3 Produced
  • Indicator Type: Lagging, but comparing it live against your best historical run exposes creeping inefficiency early.
  • Unit of Measure: GJ per tonne (grey) or MWh per tonne (green)
  • Ideal Visualization(s): KPI trend with real-time alerts, bullet chart against benchmark, SPC trend to catch slow drift.
  • Frequency: Real-time, evaluated hourly and per shift.
  • Data Required: Natural gas or power input, ammonia production rate, steam import and export.
  • Pro Tip: Normalize for ambient temperature and feed quality. Raw numbers make winter look like a triumph and summer like a failure.
  • Red Flag: Energy per tonne climbing while rates stay flat. Something is fouling, leaking, or degrading upstream of the loop.

Hydrogen-to-Nitrogen Ratio

  • Why it Matters: The synthesis loop wants close to three parts hydrogen to one part nitrogen. Stray from it and conversion falls off fast.
  • What it Measures: The molar ratio of hydrogen to nitrogen in the makeup gas entering the ammonia synthesis loop.
  • What Happens if Missed: Off-ratio gas cuts conversion, loads the recycle harder, and wastes compression energy on gas that never becomes product.
  • Formula: mol H2 / mol N2
  • Indicator Type: Current, and it reacts within minutes to front-end upsets, so live tracking pays off.
  • Unit of Measure: Molar ratio (dimensionless)
  • Ideal Visualization(s): KPI trend with real-time alerts, bullet chart against the 3:1 setpoint.
  • Frequency: Real-time.
  • Data Required: Hydrogen makeup flow, nitrogen makeup flow, loop composition analysis.
  • Pro Tip: On green plants the ratio wanders when electrolyzer output swings. Tie nitrogen supply to hydrogen availability, not a fixed setpoint.
  • Red Flag: Ratio drifting with no operator action. The front end is telling you something changed before the loop does.

Ammonia Conversion per Pass

  • Why it Matters: Higher conversion per pass means less gas recycled, lower compression energy, and more product from the same footprint.
  • What it Measures: The fraction of syngas converted to ammonia in a single pass through the synthesis converter.
  • What Happens if Missed: Falling conversion loads the recycle compressor and refrigeration harder while output slips, often blamed on the wrong equipment.
  • Formula: (NH3out – NH3in) / (H2 + N2)in x 100
  • Indicator Type: Lagging, though it tracks catalyst health closely enough to serve as an early warning on the bed.
  • Unit of Measure: Percent (%)
  • Ideal Visualization(s): KPI trend with real-time alerts, SPC trend to separate normal scatter from real decline.
  • Frequency: Real-time, trended over days and weeks.
  • Data Required: Converter inlet and outlet ammonia concentration, inlet syngas flow, loop pressure.
  • Pro Tip: Plot conversion against bed temperature over months. Together they tell you whether you have a process issue or a tired catalyst.
  • Red Flag: Conversion sliding while pressure and temperature hold. The catalyst is aging or slowly being poisoned.

Synthesis Converter Bed Temperature Profile

  • Why it Matters: The bed profile is the catalyst’s vital sign. A shifting hot spot warns of aging or poisoning before conversion drops.
  • What it Measures: Temperature at each catalyst bed level through the converter, tracked as a shape rather than a single number.
  • What Happens if Missed: A runaway hot spot can sinter catalyst permanently. Miss the trend and you shorten a charge that should last years.
  • Formula: N/A
  • Indicator Type: Leading, because the profile shifts before conversion and energy numbers react.
  • Unit of Measure: Degrees Celsius (°C)
  • Ideal Visualization(s): KPI trend with real-time alerts per bed, status history trends, bullet chart against the safe operating band.
  • Frequency: Real-time.
  • Data Required: Bed inlet and outlet temperatures, quench flows, converter pressure.
  • Pro Tip: Watch where the peak sits, not just how high it is. A hot spot creeping toward the inlet usually means front-end poison breakthrough.
  • Red Flag: Peak temperature climbing while conversion falls. Classic signature of catalyst deactivation, not a control problem.

Reformer Tube Metal Temperature (Grey Front End)

  • Why it Matters: Reformer tubes are the most expensive metal in a grey plant. Overheating one trades years of tube life for a few tonnes.
  • What it Measures: The external metal temperature of individual reformer tubes across the firebox, watched tube by tube.
  • What Happens if Missed: A single overheated tube can rupture, forcing an unplanned shutdown and a repair that dwarfs whatever production you gained.
  • Formula: N/A
  • Indicator Type: Leading, since sustained high metal temperature drives creep long before a tube actually fails.
  • Unit of Measure: Degrees Celsius (°C)
  • Ideal Visualization(s): KPI trend with real-time alerts per tube, Pareto chart when ranking tubes by peak temperature, KPI Map of the firebox.
  • Frequency: Real-time, with periodic thermographic surveys.
  • Data Required: Individual tube skin temperatures, firebox draft, feed and fuel flows.
  • Pro Tip: Rank tubes by cumulative time above the creep threshold, not just current temperature. Damage accumulates, and a snapshot hides it.
  • Red Flag: A cluster of hot tubes in one zone. That points to burner imbalance or flow maldistribution, not a single bad tube.

Electrolyzer Specific Energy Consumption (Green Front End)

  • Why it Matters: Electrolysis is where most of a green plant’s energy and cost live. Efficiency here sets the economics of every tonne downstream.
  • What it Measures: Electrical energy consumed per kilogram of hydrogen produced, measured across the electrolyzer stacks and their balance of plant.
  • What Happens if Missed: Rising energy per kilogram signals stack degradation. Ignore it and you slowly turn cheap hydrogen into expensive hydrogen.
  • Formula: kWh Consumed / kg H2 Produced
  • Indicator Type: Lagging on stack health, though live tracking against baseline flags degradation well before a forced rebuild.
  • Unit of Measure: kWh per kilogram H2
  • Ideal Visualization(s): KPI trend with real-time alerts, Pareto chart when ranking stacks by energy per kilogram, SPC trend for drift.
  • Frequency: Real-time.
  • Data Required: Stack power draw, hydrogen production rate, cell voltage, stack temperature.
  • Pro Tip: Compare stacks against each other, not just against spec. The worst performer usually schedules your next maintenance window for you.
  • Red Flag: Cell voltage climbing at constant current. The stack is degrading, and energy cost is rising right along with it.

Synthesis Gas Purity

  • Why it Matters: The synthesis catalyst tolerates almost no oxygen compounds. A brief poison slip can cost permanent activity the plant never recovers.
  • What it Measures: Concentration of catalyst poisons, mainly oxygen, carbon oxides, and sulfur, in the gas reaching the synthesis loop.
  • What Happens if Missed: Poisons deactivate catalyst irreversibly. The damage surfaces months later as lost conversion nobody can trace back to the event.
  • Formula: N/A
  • Indicator Type: Leading, because a slip appears in gas analysis before conversion or bed temperature reacts.
  • Unit of Measure: Parts per million (ppm)
  • Ideal Visualization(s): KPI trend with real-time alerts, status history trends to log every excursion.
  • Frequency: Real-time.
  • Data Required: Oxygen concentration, carbon monoxide and dioxide slip, sulfur content, loop inlet composition.
  • Pro Tip: On grey plants watch methanator performance; on green plants watch oxygen crossover. Both are the last guard before the catalyst.
  • Red Flag: Any sustained oxygenate breakthrough. Treat it as catalyst damage in progress, not an analyzer glitch, until proven otherwise.

Loop Inert Concentration and Purge Loss

  • Why it Matters: Inerts build up in the loop and choke conversion. Purging clears them but throws away hydrogen you paid dearly to make.
  • What it Measures: Concentration of inert gases, mainly argon and methane, in the synthesis loop, and the hydrogen lost through purge.
  • What Happens if Missed: Purge too little and conversion suffers. Purge too much and you vent the product. Either way, margin drains.
  • Formula: mol Inerts / mol Total Loop Gas x 100
  • Indicator Type: Current, and it responds directly to purge rate, so operators can tune it in real time.
  • Unit of Measure: Percent inerts by volume (%)
  • Ideal Visualization(s): KPI trend with real-time alerts, bullet chart against the target inert band.
  • Frequency: Real-time.
  • Data Required: Loop inert concentration, purge gas flow, purge gas hydrogen content, loop pressure.
  • Pro Tip: Route purge gas to hydrogen recovery before flare or fuel. On a green plant, that recovered hydrogen is your most expensive input.
  • Red Flag: Inert levels rising while purge holds steady. Something changed in the makeup gas, and conversion will follow it down.

Ammonia Storage Temperature and Boil-off Rate

  • Why it Matters: Refrigerated ammonia sits near minus thirty-three Celsius. Lose refrigeration control and boil-off climbs, pressure rises, and safety margins shrink fast.
  • What it Measures: Storage tank temperature and pressure alongside the rate of boil-off gas the refrigeration system has to reclaim.
  • What Happens if Missed: Rising boil-off means the compressor is losing the battle. Left alone, it ends in venting or a relief event.
  • Formula: N/A
  • Indicator Type: Leading, since boil-off rate climbs before tank pressure reaches any alarm limit.
  • Unit of Measure: Degrees Celsius for temperature, tonnes per hour for boil-off
  • Ideal Visualization(s): KPI trend with real-time alerts, bullet chart against refrigeration capacity.
  • Frequency: Real-time.
  • Data Required: Tank temperature, tank pressure, boil-off gas flow, refrigeration compressor load.
  • Pro Tip: Trend boil-off against ambient temperature and ship loading. Spikes that match neither point to tank or insulation trouble.
  • Red Flag: Compressor at full load with boil-off still rising. Refrigeration is undersized for current conditions or losing efficiency.

Why Real-Time Visibility Matters

Ammonia plants fail slowly and expensively. Catalyst deactivation, tube creep, and stack degradation all accumulate out of sight, and the cost of missing them compounds long after the shift that caused it has ended. Averages and daily reports hide exactly the signals that matter: the drifting ratio, the creeping hot spot, the boil-off that will not settle.

Real-time visibility turns those slow failures into decisions you can still make. When the syngas ratio, the bed profile, and the energy per tonne are live and alarmed, a green or grey plant runs closer to its limits with less guessing and fewer surprises. The difference between catching a poison slip in minutes and finding it in a report is the difference between a tuning adjustment and a lost catalyst charge.

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 Combined Heat and Power Plant Operations Leader Should Be Tracking

Combined Heat and Power Plant

A biomass combined heat and power plant with its fuel supply stacked alongside. Keeping both electricity and heat flowing from wood like this is exactly where real-time visibility earns its keep.

A combined heat and power (CHP) plant only beats separate generation when both products, electricity and heat, leave the building doing useful work. The moment you dump heat to chase megawatts, or back down power to protect a steam header, you’re running an expensive machine at half its purpose.

That balance is hard to hold because it never sits still. Electrical demand, steam demand, fuel price, and ambient temperature all move against each other throughout the day, and a plant that reacts to yesterday’s report is always a step behind. Heat gets rejected while fuel keeps burning. Header pressure sags and the host process complains. A bearing starts to fail at 3 a.m. and nobody sees it until shift change.

The KPIs below are the ones a CHP operations leader should watch in real time, the numbers that tell you whether both halves of the plant are earning their keep right now.

Total CHP Efficiency (Energy Utilization Factor)

  • Why it Matters: This is the number that justifies the plant existing. Beat separate heat and power generation here, or the investment case falls apart.
  • What it Measures: The share of fuel energy converted into useful output, counting both net electrical generation and delivered thermal energy.
  • What Happens if Missed: Fuel burns while recovered heat slips, and you quietly slide back toward the economics of a standalone power station.
  • Formula: (Net Electrical Output + Useful Thermal Output) / Total Fuel Energy Input × 100
  • Indicator Type: Current. It reflects how efficiently the plant is converting fuel right now, across both outputs at once.
  • Unit of Measure: Percent
  • Ideal Visualization(s): Bullet chart against the design efficiency target, paired with a KPI trend with real-time alerts when efficiency drops below threshold.
  • Frequency: Real-time, updated every minute.
  • Data Required: Net electrical output, useful thermal output delivered, fuel flow rate, fuel heating value.
  • Pro Tip: Judge it against live thermal demand, not a fixed target. A plant at part load can still hit high efficiency if recovered heat gets used.
  • Red Flag: Total efficiency sliding while electrical output holds steady. Recovered heat is leaking out as rejection somewhere downstream.

Power-to-Heat Ratio

  • Why it Matters: It tells you how the plant is splitting its output between the grid and the host process, which drives both dispatch decisions and contract compliance.
  • What it Measures: The ratio of net electrical generation to useful thermal output at any moment, showing the current operating balance of the unit.
  • What Happens if Missed: You drift out of the band your steam host or power contract expects, and you find out through a penalty or a process complaint.
  • Formula: Net Electrical Output / Useful Thermal Output
  • Indicator Type: Current. It captures the live trade-off between the two products as load and demand shift through the day.
  • Unit of Measure: Ratio (kWe per kWth)
  • Ideal Visualization(s): KPI trend with real-time alerts, alongside an XY scatter plot mapping electrical output against thermal output to expose drift from the design line.
  • Frequency: Real-time.
  • Data Required: Net electrical output, useful thermal output.
  • Pro Tip: Overlay the design ratio as a reference line. Sustained excursions usually trace back to a heat sink that isn’t taking its share.

Heat Recovery Effectiveness

  • Why it Matters: Recovered heat is the cheapest energy in the plant. Every unit you reject into the atmosphere is fuel you have already paid for and lost.
  • What it Measures: The fraction of available exhaust and jacket heat actually captured and delivered as useful thermal energy, versus what gets dumped.
  • What Happens if Missed: The radiators and dump condensers quietly carry the load, your fuel bill holds while useful output falls, and nobody notices for weeks.
  • Formula: Useful Thermal Energy Recovered / Total Recoverable Thermal Energy × 100
  • Indicator Type: Leading. A falling trend warns of fouling, valve position errors, or a heat sink backing off before efficiency fully reflects it.
  • Unit of Measure: Percent
  • Ideal Visualization(s): Bullet chart against the recovery target, with a KPI trend with real-time alerts to flag sustained shortfalls.
  • Frequency: Real-time, updated every five minutes.
  • Data Required: Recovered thermal energy delivered, heat rejected to atmosphere, total exhaust and jacket heat available.
  • Pro Tip: Pair recovery with exhaust gas temperature into the heat exchanger. Recovery dropping while inlet temperature holds points squarely at fouling.

Net Electrical Heat Rate

  • Why it Matters: It’s the cleanest read on how much fuel each megawatt-hour of power actually costs you, independent of the thermal side.
  • What it Measures: The fuel energy consumed per unit of net electricity generated, after station service loads are removed.
  • What Happens if Missed: Creeping heat rate hides real money. A point of degradation across a year of runtime buys a lot of unplanned fuel.
  • Formula: Total Fuel Energy Input / Net Electrical Output
  • Indicator Type: Current. It moves with compressor fouling, ambient conditions, and part-load operation, so trend it rather than reading single points.
  • Unit of Measure: Btu per kWh (or kJ per kWh)
  • Ideal Visualization(s): KPI trend with real-time alerts, backed by an SPC trend (control chart) to separate normal scatter from genuine degradation.
  • Frequency: Every fifteen minutes, smoothed to filter load swings.
  • Data Required: Fuel flow rate, fuel heating value, net electrical output.
  • Pro Tip: Normalize for ambient temperature before you act. A gas turbine’s heat rate climbs on hot days without anything actually being wrong.
  • Red Flag: Heat rate climbing while load and ambient hold flat. That combination usually means compressor fouling or a failing inlet system.

Exhaust Gas Temperature Spread

  • Why it Matters: A widening spread across the exhaust thermocouples is one of the earliest signs of a combustion or turbine problem you’ll get.
  • What it Measures: The temperature difference between the hottest and coldest exhaust thermocouples around the turbine outlet at a given moment.
  • What Happens if Missed: An uneven temperature profile points to a failing fuel nozzle or burner. Ignore it and you risk hot-section damage or a trip.
  • Formula: Maximum Exhaust Thermocouple Temperature – Minimum Exhaust Thermocouple Temperature
  • Indicator Type: Leading. It flags developing combustion faults well before they reach an alarm or a forced shutdown.
  • Unit of Measure: ºC (or ºF)
  • Ideal Visualization(s): KPI trend with real-time alerts on the spread value, plus a Pareto chart when ranking thermocouples by deviation from the mean. A box plot exposes the full distribution.
  • Frequency: Real-time, continuous monitoring.
  • Data Required: Individual exhaust thermocouple temperatures, mean exhaust temperature.
  • Pro Tip: Trend the spread, not just the peak. A slow widening over days tells you far more than any single high reading.
  • Red Flag: One thermocouple jumping while its neighbors hold steady. That’s a localized fault, usually a nozzle, not a sensor glitch.

Steam Header Pressure Stability

  • Why it Matters: The host process runs on stable steam. Let header pressure wander and you trip equipment downstream or breach a supply agreement.
  • What it Measures: How tightly actual steam header pressure tracks its setpoint, measured as the live deviation from target.
  • What Happens if Missed: Pressure swings ripple straight into the host plant. A sagging header can stall a process or force an unplanned curtailment.
  • Formula: Actual Steam Header Pressure – Target Setpoint Pressure
  • Indicator Type: Leading. Early deviation signals a load imbalance or control issue before it cascades into the host process.
  • Unit of Measure: bar (or psi)
  • Ideal Visualization(s): SPC trend (control chart) with real-time alerts on the deviation, paired with a KPI trend with real-time alerts to watch the live value against limits.
  • Frequency: Real-time, sub-second sampling.
  • Data Required: Steam header pressure, pressure setpoint, steam flow to host.
  • Pro Tip: Set alert bands tighter than the trip points. By the time pressure hits a trip limit, a process upset is already underway.

NOx Emissions Rate

  • Why it Matters: Your permit sets a hard ceiling. Cross it and you face fines, forced derates, or a shutdown order, none of them cheap.
  • What it Measures: The rate of nitrogen oxide leaving the stack, corrected to a reference oxygen level for a fair comparison against the limit.
  • What Happens if Missed: A drift over the limit during an audit window can cost the plant its permit margin and put compliance reporting under scrutiny.
  • Formula: Measured NOx Concentration corrected to reference O2 level
  • Indicator Type: Current. It reflects live combustion conditions and reacts quickly to load changes, fuel quality, and burner tuning.
  • Unit of Measure: mg per Nm³ (or lb per MWh)
  • Ideal Visualization(s): KPI trend with real-time alerts against the permit limit, supported by an SPC trend (control chart) to catch upward drift early.
  • Frequency: Real-time, continuous monitoring.
  • Data Required: NOx concentration, exhaust oxygen concentration, exhaust flow rate, net energy output.
  • Pro Tip: Alert on the trend, not just the threshold. A steady climb toward the limit gives you time to retune before you breach it.
  • Red Flag: NOx rising with no load change. Combustion tuning is drifting, or water and steam injection isn’t delivering what it should.

Rotor and Bearing Vibration

  • Why it Matters: Vibration is the rotating equipment telling you something’s wrong before it fails. It’s your earliest warning on the most expensive assets.
  • What it Measures: Vibration amplitude at each turbine, engine, and generator bearing, tracked continuously against its established baseline.
  • What Happens if Missed: A bearing that starts whispering at night becomes a catastrophic failure and a long forced outage if no one is watching the trend.
  • Formula: N/A
  • Indicator Type: Leading. Rising vibration precedes most mechanical failures by hours to weeks, giving you a real window to plan an intervention.
  • Unit of Measure: mm per second RMS (or microns displacement)
  • Ideal Visualization(s): KPI trend with real-time alerts per bearing, with a Pareto chart when ranking bearings by vibration amplitude and sparklines for an at-a-glance view of every point.
  • Frequency: Real-time, continuous.
  • Data Required: Bearing vibration amplitudes, shaft speed, baseline vibration limits.
  • Pro Tip: Watch the rate of change, not just the absolute level. A fast climb from a low number often beats a steady high one to failure.
  • Red Flag: Vibration that tracks with load or speed. That pattern usually means a mechanical issue like imbalance or misalignment, not sensor noise.

Forced Outage Rate

  • Why it Matters: Unplanned downtime is the most expensive way to lose a generation. It hits revenue, contract obligations, and your standing on the grid at once.
  • What it Measures: The share of time the plant was unavailable due to forced outages, relative to the time it was expected to run.
  • What Happens if Missed: Without tracking causes, the same failures keep recurring. You treat symptoms repeatedly instead of fixing the root problem once.
  • Formula: Forced Outage Hours / (Forced Outage Hours + Service Hours) × 100
  • Indicator Type: Lagging. It confirms reliability after the fact, but the cause breakdown drives where you focus maintenance next.
  • Unit of Measure: Percent
  • Ideal Visualization(s): Bar chart of the rate over time, with a Pareto chart when ranking outage causes by downtime hours to surface the worst offenders. Status history trends show the pattern.
  • Frequency: Daily, on a rolling twelve-month window.
  • Data Required: Forced outage hours, service hours, outage cause codes.
  • Pro Tip: Break the rate down by cause and unit. A single recurring failure mode often drives most of the number and the obvious fix.

Spark Spread

  • Why it Matters: It tells you, in real time, whether running the plant makes money. When the spread goes negative, every hour online burns cash.
  • What it Measures: The margin between the market price of electricity and the fuel cost to generate it, adjusted for the plant’s heat rate.
  • What Happens if Missed: Run blind to the spread and you can generate at a loss for hours, especially when fuel spikes faster than power prices follow.
  • Formula: Electricity Price per MWh – (Fuel Price per MMBtu × Heat Rate in MMBtu per MWh)
  • Indicator Type: Leading. It signals when economics favor running, ramping, or backing down before the cost shows up in the monthly numbers.
  • Unit of Measure: Currency per MWh
  • Ideal Visualization(s): KPI block for the live value, with a KPI trend with real-time alerts that fires when the spread crosses your dispatch threshold.
  • Frequency: Real-time, refreshed every fifteen minutes with market prices.
  • Data Required: Electricity market price, fuel price, net electrical output, plant heat rate.
  • Pro Tip: Fold the recovered heat value into the calculation. A thermal credit can keep a CHP unit profitable when a power-only plant would shut down.

Why Real-Time Visibility Matters

A CHP plant is two plants sharing one fuel stream, and the value lives in the seam between them. The numbers that matter, total efficiency, the power-to-heat balance, recovered heat, all shift minute to minute as electrical demand, steam demand, and ambient conditions move against each other. Read them on a daily report and you’re always reacting to yesterday.

Operating blind is where the cogeneration advantage quietly disappears. Heat gets rejected while fuel keeps burning, header pressure sags into the host process, emissions drift toward the permit line, and a bearing degrades through a shift change. Real-time visibility, with alerts on the trends that lead failures rather than confirm them, is what keeps both halves of the plant pulling their weight.

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 Bulk Material Handling Operations Leader Should Be Tracking

Bulk Material Handling - Truck unloading at the receiving pit. The airborne dust and the grain skipping off the edges are two KPIs you can read from across the room.

Truck unloading at the receiving pit. The airborne dust and the grain skipping off the edges are two KPIs you can read from across the room.

Bulk material handling is a continuous-flow business where a single stalled conveyor idles everything downstream of it. The material is loose, dusty, abrasive, and often combustible. A hot idler, a drifting belt, or a plugging chute starts as a minor reading and ends as a fire, a torn belt, or a line down for a shift. The operations leaders who stay ahead watch a handful of signals continuously instead of waiting for the alarm. Here are ten worth keeping live.

System Throughput Rate

  • Why it Matters: Throughput is the plant’s heartbeat. Every downstream process, vessel, and contract depends on moving tonnage at or above the committed rate.
  • What it Measures: The actual mass of material crossing a point per unit of time, compared against rated design capacity.
  • What Happens if Missed: Sustained shortfalls quietly erode daily targets. By the time the daily report lands, the lost tonnage is gone for good.
  • Formula: Material Mass Moved / Elapsed Time
  • Indicator Type: Current. It shows live performance against target and exposes the gap between rated and actual capacity.
  • Unit of Measure: t/h
  • Ideal Visualization(s): Bullet chart against target, KPI trend with real-time alerts, Pareto chart when ranking conveyors by throughput shortfall.
  • Frequency: Real-time
  • Data Required: Mass flow rate, belt speed, run status.
  • Pro Tip: Track throughput against running time, not scheduled time. A line that hits rate but only runs half the shift still misses target.
  • Red Flag: Rated capacity on paper but chronic real-world shortfall points to an upstream feed or downstream restriction, not the belt.

Conveyor Belt Load Factor

  • Why it Matters: A belt running half-loaded burns the same power for less product. An overloaded belt spills, overstresses splices, and trips on overcurrent.
  • What it Measures: The ratio of actual material load on the belt to its rated cross-sectional carrying capacity.
  • What Happens if Missed: Run low and you waste energy and capacity. Run high and you accelerate belt wear and risk spillage at transfer points.
  • Formula: (Actual Load Per Meter / Rated Load Per Meter) x 100
  • Indicator Type: Current. It reveals in real time whether feed control is matching the belt to its optimal operating band.
  • Unit of Measure: % of rated capacity
  • Ideal Visualization(s): Bullet chart with low and high limits, KPI trend with real-time alerts.
  • Frequency: Real-time
  • Data Required: Material load per length, belt speed, rated belt capacity.
  • Pro Tip: Tune feeders to hold load factor in a steady band. Surging between empty and overloaded wears belts faster than a consistently high load.
  • Red Flag: Load factor swinging wildly at steady throughput means the upstream feed is unstable, not the belt.

Idler Bearing Temperature

  • Why it Matters: A seized idler bearing is the most common ignition source on a conveyor. Heat climbs long before the bearing fails or sparks.
  • What it Measures: The surface or bearing temperature of idler rollers along the conveyor, tracked against ambient and historical baselines.
  • What Happens if Missed: A hot idler that goes unwatched can ignite settled dust or a stalled belt, turning a five-dollar roller into a fire.
  • Formula: N/A
  • Indicator Type: Leading. Rising temperature gives early warning of bearing wear or friction well before failure.
  • Unit of Measure: °C
  • Ideal Visualization(s): KPI Map showing idlers by location, KPI trend with real-time alerts, Pareto chart when ranking conveyors by hot idler count.
  • Frequency: Real-time
  • Data Required: Idler temperatures, ambient temperature, idler location.
  • Pro Tip: Alarm on rate of rise, not just absolute temperature. A bearing climbing fast is failing faster than one sitting at a steady warm reading.
  • Red Flag: A cluster of warm idlers in one zone signals belt misalignment dragging on the structure, not isolated bearing wear.

Belt Tracking Deviation

  • Why it Matters: A belt drifting off center grinds against the structure, sheds material over the edge, and can tear itself apart at speed.
  • What it Measures: The lateral offset of the belt from its centerline at key points such as drives, tail pulleys, and transfer zones.
  • What Happens if Missed: Edge damage accumulates silently. By the time spillage is visible, the belt has lost cover and a splice may already be compromised.
  • Formula: N/A
  • Indicator Type: Leading. Growing deviation precedes edge wear, spillage, and structural contact, giving time to correct alignment.
  • Unit of Measure: mm
  • Ideal Visualization(s): KPI trend with real-time alerts, Pareto chart when ranking conveyors by tracking deviation.
  • Frequency: Real-time
  • Data Required: Belt edge position, belt speed, load condition.
  • Pro Tip: Correlate tracking with load. A belt that only wanders when fully loaded usually has an off-center feed, not a worn training idler.
  • Red Flag: Persistent drift to the same side after adjustment points to a frame out of square or a worn pulley, not idler training.

Transfer Chute Blockage Rate

  • Why it Matters: Transfer points are where material handling chokes. A plugged chute backs up the line and buries the area in spillage within minutes.
  • What it Measures: How often chutes and transfer points plug or restrict flow over a given period, broken out by location.
  • What Happens if Missed: A blockage that trips the upstream belt cascades the whole chain to a stop and demands a manual, often hazardous, clear-out.
  • Formula: Number of Blockage Events / Operating Hours
  • Indicator Type: Lagging. Event counts confirm which transfer points carry chronic flow problems and need a redesign.
  • Unit of Measure: blockages/h
  • Ideal Visualization(s): Pareto chart when ranking transfer points by blockage frequency, KPI trend with real-time alerts.
  • Frequency: Real-time
  • Data Required: Chute fill level, upstream belt trip events, flow interruption signals.
  • Pro Tip: Watch chute level alongside upstream belt current. A rising level with climbing motor load means a plug is forming before flow actually stops.
  • Red Flag: One transfer point dominating the blockage count usually signals a chute geometry or material moisture problem, not operator error.

Material Carryback and Spillage

  • Why it Matters: Carryback and spillage are pure loss: lost product, fouled rollers, slippery walkways, and a cleanup crew that should be doing real work.
  • What it Measures: The volume of material that clings to the return belt or falls outside containment along the conveyor run.
  • What Happens if Missed: Carryback builds on return idlers and pulleys, accelerates wear, fouls the belt, and quietly raises both maintenance cost and fire risk.
  • Formula: N/A
  • Indicator Type: Lagging. It confirms how well belt cleaners and skirting are performing after the material has already moved.
  • Unit of Measure: kg/h
  • Ideal Visualization(s): KPI trend with real-time alerts, Pareto chart when ranking transfer points by spillage volume.
  • Frequency: Per shift
  • Data Required: Cleanup labor hours, return belt buildup, spillage collection weights.
  • Pro Tip: Track cleanup hours by location as a proxy. The transfer point eating the most labor is the one whose cleaners need attention first.
  • Red Flag: Spillage rising after rain or a material change points to moisture and cleaner mismatch, not worn equipment.

Specific Energy Consumption

  • Why it Matters: Conveying is energy-hungry, and power is often the largest controllable operating cost. Energy per ton exposes inefficiency that throughput alone hides.
  • What it Measures: The electrical energy consumed to move one ton of material across the system, normalized for distance where relevant.
  • What Happens if Missed: Drives running empty, dragging belts, and fouled rollers all leak energy. Without the per-ton view, the waste blends into the total power bill.
  • Formula: Total Energy Consumed / Total Tons Moved
  • Indicator Type: Lagging. It reveals efficiency drift over time and pinpoints which conveyors cost the most per ton to run.
  • Unit of Measure: kWh/t
  • Ideal Visualization(s): KPI trend with real-time alerts, Pareto chart when ranking conveyors by energy per ton.
  • Frequency: Hourly
  • Data Required: Drive power draw, tonnage moved, run hours.
  • Pro Tip: Compare energy per ton at matched load. A conveyor that gets thirsty only when lightly loaded has a feed problem, not a drive fault.
  • Red Flag: Energy per ton creeping up at steady throughput means rising drag somewhere: buildup, misalignment, or bearings starting to bind.

Mechanical Availability

  • Why it Matters: A handling line that cannot run cannot earn. Availability is the ceiling on every throughput and tonnage target you set.
  • What it Measures: The share of scheduled operating time the system is mechanically able to run, after planned and unplanned downtime.
  • What Happens if Missed: Without live availability and downtime reasons, the same failures repeat. You manage by anecdote instead of by the assets actually costing you uptime.
  • Formula: (Available Time / Scheduled Time) x 100
  • Indicator Type: Lagging. It summarizes reliability over a period and ranks which assets drag the whole line’s uptime down.
  • Unit of Measure: %
  • Ideal Visualization(s): Bullet chart against availability target, Status history trends, Pareto chart when ranking assets by downtime contribution.
  • Frequency: Real-time status, summarized per shift
  • Data Required: Run status, downtime events, downtime reason codes, scheduled hours.
  • Pro Tip: Capture a reason code on every stop. Availability without causes tells you that you have a problem but never which one to fix.
  • Red Flag: High availability paired with low throughput means the line runs but runs slow. Look for hidden bottlenecks, not breakdowns.

Dust Concentration

  • Why it Matters: Airborne dust is a compliance liability and, with combustible materials, an explosion risk. It also blinds operators and chokes equipment.
  • What it Measures: The concentration of suspended particulate at transfer points, load-out zones, and along the conveyor path.
  • What Happens if Missed: Dust that exceeds limits unseen risks fines, a shutdown, or in the worst case an ignition in a confined transfer house.
  • Formula: N/A
  • Indicator Type: Current. It shows live exposure against limits and confirms whether suppression and extraction are keeping pace.
  • Unit of Measure: mg/m³
  • Ideal Visualization(s): KPI Map by zone, KPI trend with real-time alerts, Pareto chart when ranking zones by dust exceedances.
  • Frequency: Real-time
  • Data Required: Particulate concentration, suppression system status, transfer point activity.
  • Pro Tip: Tie dust readings to spray status. A spike while sprays run means clogged nozzles or low water pressure, not a sensor fault.
  • Red Flag: Dust climbing as ambient humidity drops shows your suppression is undersized for dry conditions, not failing outright.

Stockpile and Surge Bin Level

  • Why it Matters: Run a surge bin empty and you starve the line. Overfill it and you overflow or trip, and either way the flow stops.
  • What it Measures: The live material level in surge bins, hoppers, silos, and stockpiles feeding or buffering the handling system.
  • What Happens if Missed: A bin that runs dry stalls everything downstream. One that overfills spills, jams the feeder, or buries a discharge point.
  • Formula: (Current Volume / Total Capacity) x 100
  • Indicator Type: Current. It shows live buffer status and warns when a bin is heading toward starvation or overflow.
  • Unit of Measure: % full
  • Ideal Visualization(s): Bullet chart with low and high limits, KPI trend with real-time alerts, Group rollup bars across multiple bins.
  • Frequency: Real-time
  • Data Required: Material level, feed rate, discharge rate, bin capacity.
  • Pro Tip: Watch the rate of change, not just the level. A bin draining faster than it fills warns of a stoppage before the low alarm fires.
  • Red Flag: Bin levels swinging hard between high and low mean feed and discharge are fighting each other. Smooth the control before chasing equipment.

Why Real-Time Visibility Matters

Bulk material handling fails as a chain, not as a part. A single hot idler, a drifting belt, or a plugging chute does not stay contained. It trips the belt feeding it, backs up the one behind that, and idles every asset downstream within minutes. By the time a problem surfaces in a daily report, the tonnage is gone, the spillage is on the ground, and the cause is buried under three shifts of other events.

Watching these signals in real time changes the job from cleaning up to catching problems while they are still small. A bearing flagged on rate of rise gets greased instead of catching fire. A bin trending toward empty gets fed before it starves the line. The operations leaders who run the tightest handling systems are not the ones with the newest equipment. They are the ones who see the deviation while there is still time to act on it.

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 Waste-to-Energy Plant Operations Leader Should Be Tracking

Waste-to-Energy Plants: Waste entering the sorting and processing line at a modern Waste-to-Energy facility. Real-time monitoring of feedstock flow, composition, and throughput helps operators maximize energy recovery, reduce downtime, and maintain efficient plant performance.

Waste entering the sorting and processing line at a modern Waste-to-Energy facility. Real-time monitoring of feedstock flow, composition, and throughput helps operators maximize energy recovery, reduce downtime, and maintain efficient plant performance.

A waste-to-energy plant is a power station that runs on the most inconsistent fuel on earth. Every grab of municipal waste differs from the last in moisture, density, and energy content, and the furnace has to absorb all of it while holding emissions inside a legal envelope.

When the plant runs blind or reacts too late, the failures stack fast. Combustion temperature drifts, emissions creep toward permit limits, steam output wobbles, and the turbine loses the steady feed it needs to earn its revenue. These ten KPIs give an operations leader the real-time picture needed to keep combustion stable, emissions compliant, and export on target.

Furnace Combustion Temperature

  • Why it Matters: Sustained temperature above the regulatory threshold destroys dioxins and furans. Drop below it and the plant breaches its operating permit instantly.
  • What it Measures: Flue gas temperature in the post-combustion zone, where waste gases must hold heat long enough for complete destruction.
  • What Happens if Missed: Incomplete combustion releases dioxins, triggers regulatory violations, and can force a load reduction or a full shutdown.
  • Formula: N/A
  • Indicator Type: Leading. Temperature dips precede emissions spikes, giving operators a window to adjust before limits are breached.
  • Unit of Measure: °C
  • Ideal Visualization(s): KPI trend with real-time alerts; SPC trend (control chart) for combustion stability.
  • Frequency: Real-time
  • Data Required: Post-combustion zone temperature, furnace exit gas temperature, residence time.
  • Pro Tip: Track temperature against the two-second residence window, not just the setpoint. Margin matters more than the absolute number.
  • Red Flag: Frequent short dips below threshold even when averages look fine. That pattern signals uneven combustion or inconsistent feed.

Flue Gas Emissions Compliance Margin

  • Why it Matters: Emissions permits are legally binding. Operating close to limits risks fines, public scrutiny, and forced derates that erase the day’s revenue.
  • What it Measures: Real-time concentration of regulated pollutants such as CO, NOx, SOx, HCl, and particulates against permitted limits, shown as remaining headroom.
  • What Happens if Missed: A sustained exceedance triggers reportable violations, automatic load cuts, and in repeat cases, suspension of the operating license.
  • Formula: Compliance Margin = (Permit Limit – Measured Concentration) / Permit Limit × 100
  • Indicator Type: Current. It reflects live stack conditions and dictates immediate combustion and scrubber adjustments.
  • Unit of Measure: % of permit limit
  • Ideal Visualization(s): Bullet chart per pollutant against permit limit; KPI trend with real-time alerts; Pareto chart when ranking pollutants by exceedance frequency.
  • Frequency: Real-time
  • Data Required: Stack concentration for each regulated pollutant, permitted limits, flue gas flow.
  • Pro Tip: Watch the margin trend across all pollutants together. One tightening early usually predicts the next, especially during feed swings.
  • Red Flag: Margin erosion on several pollutants at once. That points to a combustion problem upstream, not a scrubber issue.

Steam Generation Rate

  • Why it Matters: Steam is the product that drives the turbine. A stable rate keeps power export steady and protects boiler tubes from thermal stress.
  • What it Measures: Mass of steam the boiler produces per hour, measured against its maximum continuous rating and current load demand.
  • What Happens if Missed: Swings starve the turbine, cut export, and accelerate fatigue on superheater tubes through repeated thermal cycling.
  • Formula: N/A
  • Indicator Type: Current. It tracks live boiler output and shows how well combustion matches steam demand.
  • Unit of Measure: tonnes/hour
  • Ideal Visualization(s): KPI trend with real-time alerts; SPC trend (control chart) for output stability.
  • Frequency: Real-time
  • Data Required: Feedwater flow, steam flow, drum pressure, drum level.
  • Pro Tip: Judge steam stability by variance, not the average. A flat hourly mean can hide minute-by-minute swings that wear the boiler.
  • Red Flag: Rising steam variance at a constant feed rate. That usually means inconsistent calorific value entering the furnace.

Waste Throughput Rate

  • Why it Matters: Throughput drives revenue on the gate-fee side and fuel supply on the energy side. Falling behind backs up the tipping hall.
  • What it Measures: Tonnes of municipal solid waste fed into the furnace per hour, measured against the design feed rate.
  • What Happens if Missed: Underfeeding wastes furnace capacity and gate-fee income; overfeeding chokes combustion and pushes emissions toward their limits.
  • Formula: N/A
  • Indicator Type: Current. It reflects live feed-crane and ram activity and sets the pace for the whole thermal process.
  • Unit of Measure: tonnes/hour
  • Ideal Visualization(s): KPI trend with real-time alerts; bar chart for shift-over-shift throughput.
  • Frequency: Real-time
  • Data Required: Feed ram cycle data, crane grab weights, bunker inventory, design feed rate.
  • Pro Tip: Pair throughput with calorific value. A high tonnage of low-energy waste can still leave the boiler short on steam.
  • Red Flag: Throughput holding steady while steam output drifts down. The waste mix is getting wetter or lighter.

Net Electrical Export

  • Why it Matters: Net export is the revenue meter. Every megawatt sent to the grid is income; every megawatt consumed on-site is overhead.
  • What it Measures: Power delivered to the grid after subtracting the plant’s own parasitic load from gross generation.
  • What Happens if Missed: Rising parasitic load quietly erodes margin. Operators chase gross output while net export, the number that pays, falls.
  • Formula: Net Export = Gross Generation – Parasitic Load
  • Indicator Type: Lagging. It confirms the combined result of combustion, steam, and turbine performance after the fact.
  • Unit of Measure: MW
  • Ideal Visualization(s): KPI trend with real-time alerts; bullet chart against export target.
  • Frequency: Real-time
  • Data Required: Gross generator output, auxiliary power consumption, grid export meter reading.
  • Pro Tip: Track parasitic load as a percentage of gross output. A creeping ratio flags fouling fans, pumps, or scrubber demand.
  • Red Flag: Net export falling while gross stays flat. Something on-site is drawing more power, usually flue gas cleaning equipment.

Waste Lower Heating Value (LHV)

  • Why it Matters: LHV is the fuel quality of the waste. It sets how much steam and power a tonne yields and how stable combustion stays.
  • What it Measures: The usable energy content of the waste feed, estimated in real time from steam output and feed mass.
  • What Happens if Missed: Unseen LHV swings destabilize combustion temperature and steam flow, forcing constant reactive adjustments that wear equipment.
  • Formula: LHV ≈ (Steam Energy Output / Waste Feed Rate) adjusted for boiler efficiency
  • Indicator Type: Leading. Calorific shifts precede temperature and steam changes, giving operators early warning of combustion drift.
  • Unit of Measure: MJ/kg
  • Ideal Visualization(s): KPI trend with real-time alerts; histogram of LHV distribution across a shift.
  • Frequency: Real-time (calculated)
  • Data Required: Steam flow, steam enthalpy, waste feed rate, boiler efficiency.
  • Pro Tip: Use the LHV trend to anticipate feed-crane mixing. Blend wet and dry waste before it reaches the hopper, not after.
  • Red Flag: A widening LHV histogram across the shift. The bunker is poorly mixed and combustion will keep hunting.

Boiler Thermal Efficiency

  • Why it Matters: Efficiency decides how much of the waste’s energy becomes steam. A few points lost means lost export across thousands of operating hours.
  • What it Measures: The ratio of energy captured as steam to the energy released by burning the waste feed.
  • What Happens if Missed: Fouled tubes and excess air drag efficiency down silently. The plant burns the same waste for less power.
  • Formula: Boiler Efficiency = (Steam Energy Output / Waste Energy Input) × 100
  • Indicator Type: Lagging. It summarizes how well the boiler converted fuel after combustion and heat transfer have happened.
  • Unit of Measure: %
  • Ideal Visualization(s): KPI trend with real-time alerts; SPC trend (control chart) for drift detection.
  • Frequency: Hourly
  • Data Required: Steam flow, steam enthalpy, feedwater enthalpy, waste feed rate, waste LHV.
  • Pro Tip: Trend efficiency against flue gas exit temperature. A rising stack temperature is usually the first sign of tube fouling.
  • Red Flag: Efficiency sliding while load holds steady. Heat is escaping up the stack instead of reaching the water.

Bottom Ash Burnout (TOC)

  • Why it Matters: Low unburned carbon in ash proves combustion did its job. High residual carbon wastes energy and complicates ash disposal and reuse.
  • What it Measures: Total organic carbon remaining in bottom ash, indicating how completely the waste burned on the grate.
  • What Happens if Missed: Poor burnout signals incomplete combustion, lowers efficiency, and can push ash above the limits for reuse as aggregate.
  • Formula: TOC = (Organic Carbon Mass / Total Ash Mass) × 100
  • Indicator Type: Lagging. It confirms grate combustion quality after the waste has fully passed through.
  • Unit of Measure: % (loss on ignition)
  • Ideal Visualization(s): KPI trend with real-time alerts; box plot of burnout across grate zones.
  • Frequency: Per batch sample
  • Data Required: Ash sample carbon content, grate temperature profile, primary air distribution.
  • Pro Tip: Correlate burnout with primary air distribution across grate zones. Uneven air is the usual cause of carbon-rich pockets.
  • Red Flag: Rising TOC alongside falling grate temperatures. The fuel bed is moving too fast for complete burnout.

Flue Gas Oxygen Content

  • Why it Matters: Oxygen level reveals the combustion air balance. Too little starves the burn; too much chills the furnace and wastes heat.
  • What it Measures: The percentage of oxygen left in the flue gas after combustion, indicating the excess air supplied to the furnace.
  • What Happens if Missed: Low oxygen drives up CO and unburned waste; high oxygen cools the furnace and cuts efficiency through excess airflow.
  • Formula: N/A
  • Indicator Type: Leading. Oxygen shifts precede CO spikes and temperature changes, letting operators tune air before emissions react.
  • Unit of Measure: % O2
  • Ideal Visualization(s): KPI trend with real-time alerts; XY/scatter plot of oxygen versus CO.
  • Frequency: Real-time
  • Data Required: Flue gas oxygen concentration, CO concentration, primary and secondary air flows.
  • Pro Tip: Plot oxygen against CO continuously. The sweet spot sits just above the point where CO starts to climb.
  • Red Flag: Oxygen and CO rising together. Air is bypassing the fuel bed instead of feeding the combustion it should.

Emissions Reagent Consumption

  • Why it Matters: Reagents like lime, activated carbon, and ammonia control emissions but cost real money. Overdosing burns budget; underdosing risks a breach.
  • What it Measures: The mass of each reagent injected per tonne of waste processed to keep emissions inside permit limits.
  • What Happens if Missed: Blind dosing either wastes reagent on clean flue gas or leaves the plant exposed when pollutant loads spike.
  • Formula: Reagent Rate = Reagent Mass Consumed / Waste Processed
  • Indicator Type: Current. It tracks live injection against actual emissions, showing whether dosing matches the real pollutant load.
  • Unit of Measure: kg/tonne waste
  • Ideal Visualization(s): KPI trend with real-time alerts; Pareto chart when ranking reagents by cost per tonne; bullet chart against dosing target.
  • Frequency: Real-time
  • Data Required: Reagent injection rates, waste throughput, post-treatment pollutant concentrations.
  • Pro Tip: Tie dosing to live stack readings, not a fixed setpoint. Reactive dosing tracks the load and trims chemical spend.
  • Red Flag: Reagent use climbing while emissions margins hold steady. The system is overdosing or a feeder calibration has drifted.

Why Real-Time Visibility Matters

A waste-to-energy plant runs three businesses at once: a waste processor, a power station, and a regulated emitter. Each one moves on its own clock, and the waste feeding all of them changes load to load. When operators see these systems only in hourly reports, they react to problems that started long before, and the cost shows up as lost export, wasted reagent, or a reportable exceedance.

Real-time KPIs close that gap. Watching combustion temperature, oxygen, and emissions margins as they move lets operators correct drift before it turns into a violation or a derate. The plant burns the same waste either way. Visibility decides whether it earns full revenue or pays for the blind spots.

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 Aluminum Smelting Operations Leader Should Keep on Their Radar

Molten aluminum pours into a crucible truck along a potroom that runs the building's full length, an operator working the controls just feet from the stream. This is the moment tapped metal per pot and cell stability have to hold, where a misread means a breakout instead of a clean tap.

Molten aluminum pours into a crucible truck along a potroom that runs the building’s full length, an operator working the controls just feet from the stream. This is the moment tapped metal per pot and cell stability have to hold, where a misread means a breakout instead of a clean tap.

Aluminum smelting is a business where you sell stability and pay for instability in megawatt-hours. The Hall-Heroult process runs on a razor-thin energy balance, and the pots punish hesitation. When a potline drifts blind, you don’t get a sudden failure. You get a slow bleed: rising specific energy, falling current efficiency, anode effects piling up, and a cell heading toward freeze or meltdown long before anyone reacts. By the time the daily report lands, the money is already gone.

These are the ten KPIs that separate a potline running on plan from one paying compound interest on every missed signal.

Current Efficiency

  • Why it Matters: Current efficiency drives metal output per amp. A one-point drop across a potline quietly erases tonnes of production every single day.
  • What it Measures: The ratio of actual metal produced to the theoretical maximum from the current applied, per Faraday’s law.
  • What Happens if Missed: Back-reaction and metal re-oxidation go undetected, output sags, and you burn power producing less aluminum than the amps justify.
  • Formula: (Actual metal produced / Theoretical metal from Faraday’s law) x 100
  • Indicator Type: Lagging. It confirms what the cell chemistry already did, so pair it with leading bath signals.
  • Unit of Measure: Percent
  • Ideal Visualization(s): KPI trend with real-time alerts, Pareto chart when ranking pots by efficiency deviation
  • Frequency: Daily, with rolling shift estimates
  • Data Required: Metal tapped per pot, line current, tapping interval, pot count
  • Pro Tip: Track current efficiency per pot, not just per line. Line averages hide the handful of cells dragging everyone down.
  • Red Flag: A steady efficiency decline alongside stable current usually points to bath chemistry drift, not measurement noise.

Specific Energy Consumption

  • Why it Matters: Energy is the largest single cost in smelting. Specific energy consumption tells you how efficiently each kilowatt-hour becomes metal.
  • What it Measures: The DC energy consumed per unit of aluminum produced, combining cell voltage and current efficiency into one cost-anchored number.
  • What Happens if Missed: Creeping energy use goes unchallenged, margins thin out, and you discover the overrun only when the monthly power bill arrives.
  • Formula: Total DC energy consumed / Total aluminum produced
  • Indicator Type: Lagging. It rolls up voltage and efficiency, so use it to validate the leading signals feeding it.
  • Unit of Measure: kWh per kg aluminum
  • Ideal Visualization(s): KPI trend with real-time alerts, Bullet chart against target band
  • Frequency: Daily, with hourly estimates
  • Data Required: Cell voltage, line current, metal produced, time interval
  • Pro Tip: Watch specific energy against ambient temperature swings. Cold spells push it up fast if pot thermal balance isn’t managed.

Cell / Pot Voltage

  • Why it Matters: Pot voltage is the most direct, fastest signal of cell health. It moves the instant resistance, anode-cathode distance, or bath conditions shift.
  • What it Measures: The total voltage drop across an individual electrolysis cell, reflecting bath resistance, anode-cathode distance, and ohmic losses.
  • What Happens if Missed: A voltage excursion signals approaching instability or an anode effect, and ignoring it risks thermal runaway or a frozen cell.
  • Formula: Measured cell voltage (sum of decomposition, ohmic, and overvoltage components)
  • Indicator Type: Leading. It moves before efficiency or energy KPIs react, giving you the earliest warning on a cell.
  • Unit of Measure: Volts
  • Ideal Visualization(s): KPI trend with real-time alerts, SPC trend for excursion detection
  • Frequency: Real-time
  • Data Required: Individual cell voltage, line current, target voltage setpoint
  • Pro Tip: Set noise-band alerts, not just high-limit alerts. Rising voltage noise often precedes an anode effect by minutes.
  • Red Flag: Voltage climbing while current holds steady means resistance is rising, often a sign of alumina depletion in the bath.

Anode Effect Frequency

  • Why it Matters: Anode effects spike voltage, waste energy, and release potent perfluorocarbons. Frequency is both an efficiency metric and an emissions liability.
  • What it Measures: The number of anode effects per pot per day, triggered when alumina concentration drops too low to sustain normal electrolysis.
  • What Happens if Missed: PFC emissions climb, energy spikes accumulate, and regulators and your sustainability targets both take the hit unnoticed.
  • Formula: Total anode effects / (Number of pots x Days)
  • Indicator Type: Lagging. It counts events that already happened, so tie it to real-time alumina feed control.
  • Unit of Measure: Anode effects per pot-day
  • Ideal Visualization(s): KPI trend with real-time alerts, Pareto chart when ranking pots by anode effect count
  • Frequency: Real-time event logging, daily rollup
  • Data Required: Anode effect event flags, pot count, voltage spike timestamps
  • Red Flag: A cluster of anode effects on adjacent pots usually points to a feeder or alumina supply problem, not isolated cell behavior.

Bath Temperature

  • Why it Matters: Bath temperature governs the entire thermal balance of the cell. Too hot wastes energy; too cold risks sludge and freezing.
  • What it Measures: The temperature of the molten cryolite-alumina electrolyte, the key indicator of cell thermal state and chemistry stability.
  • What Happens if Missed: Undetected drift pushes the cell toward muck buildup or a frozen ledge, both of which are slow and expensive to recover.
  • Formula: N/A
  • Indicator Type: Leading. Temperature shifts precede efficiency and voltage problems, making it a core early-warning signal.
  • Unit of Measure: Degrees Celsius
  • Ideal Visualization(s): KPI trend with real-time alerts, Histogram of pot temperature distribution
  • Frequency: Periodic measurement, typically once or twice per shift
  • Data Required: Bath temperature reading, target temperature, bath ratio
  • Pro Tip: Trend bath temperature against superheat, not in isolation. The gap above liquidus tells you more than the absolute number.

Bath Ratio / Acidity

  • Why it Matters: Bath ratio controls electrolyte chemistry, liquidus temperature, and alumina solubility. It sets the operating window every other KPI lives inside.
  • What it Measures: The mass ratio of sodium fluoride to aluminum fluoride in the bath, defining acidity and chemical balance.
  • What Happens if Missed: Chemistry drifts out of range, temperature control gets harder, and current efficiency erodes from a foundation you can’t see moving.
  • Formula: Mass NaF / Mass AlF3
  • Indicator Type: Current. It describes the present chemical state that drives temperature and efficiency outcomes.
  • Unit of Measure: Ratio (dimensionless)
  • Ideal Visualization(s): KPI trend with real-time alerts, Box plot across pots in a line
  • Frequency: Per bath sample, typically daily
  • Data Required: NaF concentration, AlF3 concentration, AlF3 addition rate
  • Pro Tip: Adjust AlF3 additions in small steps. Bath chemistry responds slowly, and overcorrection swings you straight into the opposite problem.

Alumina Concentration

  • Why it Matters: Alumina is the feedstock the reaction consumes. Hold concentration in the sweet spot and you avoid both anode effects and sludge.
  • What it Measures: The dissolved alumina content in the bath, balanced between depletion that triggers anode effects and excess that forms undissolved sludge.
  • What Happens if Missed: Run too low and anode effects fire; run too high and sludge settles on the cathode, raising resistance and cutting efficiency.
  • Formula: N/A
  • Indicator Type: Leading. Concentration trends signal anode effects and sludge before either show up in voltage or efficiency.
  • Unit of Measure: Percent by mass
  • Ideal Visualization(s): KPI trend with real-time alerts, SPC trend for feed-cycle stability
  • Frequency: Estimated continuously from feed control, sampled periodically
  • Data Required: Feed rate, dissolution rate estimate, cell resistance response, bath mass
  • Red Flag: Resistance climbing between feed cycles means alumina is depleting faster than the feeder is keeping up.

Metal Tapped per Pot

  • Why it Matters: Tapped metal is the actual sellable output. Comparing it to theoretical yield exposes which pots underperform and why.
  • What it Measures: The mass of molten aluminum siphoned from each pot per tapping cycle, the direct measure of production per cell.
  • What Happens if Missed: Under-tapping raises metal pad height and destabilizes the cell; over-tapping disrupts thermal balance and pad protection.
  • Formula: Sum of metal mass tapped per pot per cycle
  • Indicator Type: Lagging. It records production after the fact, useful for ranking pots and validating efficiency estimates.
  • Unit of Measure: Kilograms
  • Ideal Visualization(s): KPI trend with real-time alerts, Pareto chart when ranking pots by yield gap
  • Frequency: Per tapping cycle, typically daily
  • Data Required: Tapped metal weight, target tap weight, metal pad height, pot count
  • Pro Tip: Reconcile tapped metal against current efficiency daily. A persistent gap usually points to a measurement or scale problem, not chemistry.

Anode Current Distribution

  • Why it Matters: Even current sharing across anodes keeps the cell stable. A skewed distribution overworks some anodes and starves others.
  • What it Measures: How line current divides among the individual anodes in a cell, revealing uneven wear, spikes, or misset anodes.
  • What Happens if Missed: Hot anodes wear fast and spike, cold anodes carry too little load, and the imbalance drives noise, instability, and lost efficiency.
  • Formula: Individual anode current / Average anode current
  • Indicator Type: Leading. Distribution skew appears before it cascades into voltage noise or cell instability.
  • Unit of Measure: Amps (or percent of average)
  • Ideal Visualization(s): Bar chart across anodes, Pareto chart when ranking anodes by current deviation
  • Frequency: Real-time
  • Data Required: Per-anode current, total line current, anode set timestamps
  • Red Flag: A single anode pulling far above average shortly after setting often means it’s poorly seated or making a spike.

Pot Stability / Cell Noise

  • Why it Matters: Cell noise is the heartbeat of pot health. A quiet cell is a stable cell; rising noise means the metal-bath interface is rolling.
  • What it Measures: The high-frequency fluctuation in cell voltage or resistance, reflecting magnetohydrodynamic movement of the liquid metal pad.
  • What Happens if Missed: Growing instability erodes efficiency, raises anode effect risk, and can tip a cell into an excursion that demands operator intervention.
  • Formula: Standard deviation of cell resistance over a rolling window
  • Indicator Type: Leading. Noise rises before efficiency or voltage limits trip, giving operators time to act on a destabilizing cell.
  • Unit of Measure: Microohms (or normalized noise index)
  • Ideal Visualization(s): KPI trend with real-time alerts, SPC trend for noise excursions
  • Frequency: Real-time
  • Data Required: Cell voltage, line current, derived cell resistance, rolling time window
  • Pro Tip: Alert on the rate of change in noise, not just the level. A fast climb matters more than a high but steady reading.

Why Real-Time Visibility Matters

Aluminum smelting runs on energy balances that shift faster than any daily report can capture. A cell heading toward a freeze, a feeder falling behind on alumina, or an anode spiking out of distribution all announce themselves in minutes through voltage, noise, and temperature. Seen in real time, each is a small correction. Seen tomorrow morning, each is lost tonnes, wasted megawatt-hours, or a cell pulled offline for recovery.

The cost of operating blind compounds across a potline of hundreds of cells. A one-point slip in current efficiency, a creeping rise in specific energy, or a cluster of anode effects spreads quietly until it shows up where it hurts: the power bill, the emissions report, and the production target. Real-time KPIs turn those slow bleeds into early signals an operator can still do something about.

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 Mining Exploration Operations Leader Should Keep on Their Radar

Mining Exploration. A large hydraulic excavator loads a haul truck at an open-pit mine face, where real-time equipment utilization and fleet availability KPIs determine whether every loaded cycle advances the production plan or compounds a shift-level delay.

A large hydraulic excavator loads a haul truck at an open-pit mine face, where real-time equipment utilization and fleet availability KPIs determine whether every loaded cycle advances the production plan or compounds a shift-level delay.

Exploration is where capital goes to die quietly if nobody’s watching. You’re spending tens of millions drilling into uncertainty, and the margin between a productive campaign and a write-off often comes down to whether your teams are reacting in hours or days.

When exploration programs run without real-time visibility, the symptoms are familiar: drill programs drift off target, rig utilization collapses, sample turnaround times balloon, and field teams improvise decisions that should be data-driven. By the time the weekly report surfaces a problem, the damage is already compounded. The KPIs below are the ones that separate exploration programs that hit their resource targets from those that bleed budget on rework, idle equipment, and replanned campaigns.

Drill Rig Utilization Rate

  • Why it Matters: Drill rigs are the most expensive assets on an exploration campaign. Every hour of idle time is an unrecoverable cost with no geological return.
  • What it Measures: The percentage of scheduled drilling hours during which the rig is actually advancing the hole.
  • What Happens if Missed: Utilization drift below threshold goes unnoticed until the campaign is weeks behind schedule with no budget headroom to recover.
  • Formula: (Actual Drilling Hours / Scheduled Drilling Hours) × 100
  • Indicator Type: Current. It reflects live operational tempo and triggers immediate intervention when utilization falls.
  • Unit of Measure: %
  • Ideal Visualization(s): Bullet chart showing actual vs. target utilization per rig; KPI trend with real-time alerts; Pareto chart when ranking rigs by utilization deviation.
  • Frequency: Real-time, updated continuously.
  • Data Required: Rig engine run hours, scheduled shift hours, standby hours, breakdown hours, planned maintenance hours.
  • Pro Tip: Separate breakdown-driven downtime from weather and access delays. They require completely different responses and shouldn’t be masked in a single utilization number.
  • Red Flag: Utilization steadily above 95% sounds great until the rig fails. High sustained utilization with no planned maintenance windows is a breakdown waiting to happen.

Meters Drilled Per Day

  • Why it Matters: Daily advance rate is the primary throughput metric for any drill program. It governs whether you’ll complete the planned holes within budget and timeline.
  • What it Measures: The total meters of hole advanced across all active rigs in a 24-hour period.
  • What Happens if Missed: Consistently low advance rates cascade into budget overruns and resource estimate delays. By the time the pattern is obvious, you’ve lost weeks.
  • Formula: Sum of (End Depth – Start Depth) per rig per day
  • Indicator Type: Current. Daily advance rate captures the operational reality of the program in real time.
  • Unit of Measure: m/day
  • Ideal Visualization(s): KPI trend with real-time alerts showing daily meters vs. plan; bar chart comparing advance rates across active rigs; Pareto chart when ranking rigs by deviation from planned meters.
  • Frequency: Updated every shift, with cumulative real-time tracking.
  • Data Required: Hole depth at shift start and end, active rig count, downtime hours per rig, formation type encountered.
  • Pro Tip: Track advance rate by formation type separately. A rig drilling 60 m/day through competent granite is performing very differently than one drilling 60 m/day through fractured volcanics.
  • Red Flag: Sudden drops in advance rate without a corresponding logged breakdown or weather event usually mean formation problems or tooling issues the rig crew hasn’t formally reported.

Core Recovery Rate

  • Why it Matters: You can drill thousands of meters and still get nothing geologically useful if core recovery is poor. Recovery quality drives the integrity of your resource model.
  • What it Measures: The percentage of drilled intervals recovered as intact core samples.
  • What Happens if Missed: Persistently low recovery in mineralised zones leaves gaps in your geological model. You either accept uncertainty or redrill at significant cost.
  • Formula: (Recovered Core Length / Drilled Interval Length) × 100
  • Indicator Type: Current. Recovery is logged as drilling proceeds, giving the geologist real-time feedback on sample quality.
  • Unit of Measure: %
  • Ideal Visualization(s): Bullet chart per hole vs. target recovery threshold; KPI trend with real-time alerts for recovery dropping below threshold; Pareto chart when ranking holes by recovery deficit.
  • Frequency: Updated per run, typically every 1.5 to 3 meters.
  • Data Required: Core box number, drilled interval per run, recovered interval per run, formation logged, drilling fluid pressure and flow rate.
  • Pro Tip: Compare recovery against drilling parameters in real time. Drops in recovery correlated with increases in fluid pressure often indicate cavity encounters or structurally weak zones you need to log immediately.
  • Red Flag: Recovery below 80% in zones with high assay variance creates statistically unreliable data that may invalidate the resource block model for that intercept.

Sample Turnaround Time

  • Why it Matters: Exploration decisions depend on assay results. Delays in sample processing slow every downstream decision, from drill targeting to resource updates.
  • What it Measures: The elapsed time from sample dispatch at the drill site to certified assay results received from the laboratory.
  • What Happens if Missed: Extended turnaround blocks geological relogging, delays infill drilling decisions, and can suspend the entire program while waiting on results.
  • Formula: (Assay Result Received Date/Time) – (Sample Dispatch Date/Time)
  • Indicator Type: Leading. Turnaround time predicts when the geological team can action results. Delays surface before they halt decisions.
  • Unit of Measure: Days
  • Ideal Visualization(s): KPI trend with real-time alerts tracking average turnaround against SLA; status history trend per sample batch; table showing batch status by dispatch date.
  • Frequency: Updated on dispatch and receipt events, monitored daily.
  • Data Required: Sample dispatch timestamps, lab receipt confirmation timestamps, certified result delivery timestamps, batch size per dispatch.
  • Pro Tip: Track turnaround time by assay type separately. Multielement packages and fire assay runs have different SLAs. Averaging them masks which workflows are underperforming.
  • Red Flag: Turnaround times extending beyond the lab’s contracted SLA more than twice in a month usually signal a capacity problem at the lab that requires immediate escalation.

Hole Completion Rate vs. Plan

  • Why it Matters: The drill program is planned around a specific number of completed holes. Completion rate tells you whether you’re building the geological dataset you budgeted for.
  • What it Measures: The ratio of completed holes to planned holes within a defined program period.
  • What Happens if Missed: Falling completion rates compound. Incomplete programs leave gaps in the deposit model that require follow-up campaigns, increasing total exploration cost significantly.
  • Formula: (Completed Holes / Planned Holes) × 100
  • Indicator Type: Lagging. Completion rate reflects cumulative program progress and is assessed against the original drill plan timeline.
  • Unit of Measure: %
  • Ideal Visualization(s): Bullet chart showing completed vs. planned holes for the current program; KPI trend with real-time alerts when completion rate falls below threshold trajectory; Pareto chart when ranking incomplete holes by delay cause.
  • Frequency: Updated in real time as holes are finalised and logged.
  • Data Required: Planned hole count and targets, completed hole depth vs. planned total depth, abandonment or redirection events, rig assignments per hole.
  • Pro Tip: Separate early abandonment from completion. A hole abandoned at 60% depth due to geological redirection is a program decision, not a performance failure. Lumping them distorts your completion metric.
  • Red Flag: Completion rate falling more than 15% behind plan in the first third of a campaign rarely recovers without additional rig mobilisation or a revised program scope.

Consumable Burn Rate

  • Why it Matters: Drill bits, rods, casing, and drilling fluids are significant cost drivers. Burn rates that exceed planned consumption erode exploration budgets fast.
  • What it Measures: The actual consumption of key consumables (bits, drilling fluids, rods) against the budgeted consumption rate per meter drilled.
  • What Happens if Missed: Consumable overruns go undetected until a resupply crisis forces a rig shutdown or a significant budget reforecast late in the campaign.
  • Formula: (Actual Consumable Volume Used) / (Actual Meters Drilled) vs. (Budgeted Consumable Volume) / (Planned Meters)
  • Indicator Type: Current. Burn rate tracks against meters in real time and projects forward.
  • Unit of Measure: Units per meter (e.g., bits/100m, liters/m)
  • Ideal Visualization(s): Bullet chart for current burn rate vs. budget per consumable type; KPI trend with real-time alerts when burn rate exceeds threshold; Pareto chart when ranking consumables by variance from budget.
  • Frequency: Updated per shift as consumption is logged against advance.
  • Data Required: Consumable quantities issued per rig, meters drilled per shift, consumable inventory levels, restocking lead times.
  • Pro Tip: Elevated bit consumption in a specific hole or formation type is valuable geological information, not just a cost issue. Cross-reference bit consumption with hardness logs before escalating as a performance problem.
  • Red Flag: Drill fluid consumption spiking without a corresponding change in formation type often indicates a circulation loss zone that needs to be logged and addressed before continuing.

Geotechnical Hazard Event Rate

  • Why it Matters: Exploration drilling in complex terrain generates geotechnical events that risk crew safety, equipment loss, and hole integrity. Real-time visibility enables faster response.
  • What it Measures: The frequency of logged geotechnical events per 1,000 meters drilled, including stuck rods, cavity encounters, casing collapses, and slope instability events.
  • What Happens if Missed: Untracked geotechnical events obscure patterns in hazardous formation zones. Repeated encounters in the same geological corridor indicate a systematic risk that needs a procedural or design response.
  • Formula: (Total Geotechnical Events / Total Meters Drilled) × 1,000
  • Indicator Type: Current. Event logging in real time enables pattern detection before a cluster becomes a safety or operational crisis.
  • Unit of Measure: Events per 1,000 m
  • Ideal Visualization(s): KPI trend with real-time alerts; KPI GeoMap View showing event locations across the tenement; status history trend per drill hole.
  • Frequency: Logged per event, reviewed in real time.
  • Data Required: Event type classification, depth at event, formation logged at event depth, drilling parameters at time of event, hole location coordinates.
  • Pro Tip: Map geotechnical events against your geological model. Structural domains that produce repeated stuck-rod events are telling you something about orientation and fracture intensity that your geotech team needs to assess.
  • Red Flag: Two or more cavity encounters in the same formation corridor within a single program phase requires a design review before proceeding. Continuing without review is how you lose expensive drilling assemblies.

Environmental Compliance Incident Rate

  • Why it Matters: Exploration permits are conditional on meeting environmental conditions. Incidents trigger regulatory reviews that can suspend drilling programs entirely.
  • What it Measures: The number of environmental non-conformances recorded per 1,000 meters drilled, including spills, vegetation clearance overruns, and water management breaches.
  • What Happens if Missed: Environmental incidents accumulate without visibility until a permit holder review surfaces them. By then, you’re managing a regulatory relationship problem, not just an operational one.
  • Formula: (Total Environmental Non-Conformances / Total Meters Drilled) × 1,000
  • Indicator Type: Lagging. Incidents are logged after occurrence. The leading signal is monitoring of compliance controls in real time.
  • Unit of Measure: Incidents per 1,000 m
  • Ideal Visualization(s): KPI trend with real-time alerts for incident thresholds; status history trend for compliance status per drill site; KPI GeoMap View showing incident locations across the tenement.
  • Frequency: Logged per incident, reviewed daily.
  • Data Required: Non-conformance type, location, severity classification, responsible area, corrective action status and close-out date.
  • Pro Tip: Track corrective action close-out rate alongside the incident rate. An operation that logs incidents and closes them quickly looks very different to a regulator than one with chronic open actions.
  • Red Flag: Three or more open environmental non-conformances in the same area without close-out within the required period signals a systemic issue that needs escalation to site management and the permit holder.

Field Assay vs. Laboratory Assay Variance

  • Why it Matters: When portable XRF or field screening results diverge significantly from certified laboratory assays, your geological decision-making is unreliable. Catching variance early protects the resource model.
  • What it Measures: The percentage difference between field assay readings and certified laboratory results for the same sample, tracked per element and assay type.
  • What Happens if Missed: Systematic field-to-lab variance undetected for weeks corrupts drill targeting decisions. Holes get positioned on field-assay anomalies that lab assays subsequently fail to confirm.
  • Formula: ((Field Assay Value – Lab Assay Value) / Lab Assay Value) × 100
  • Indicator Type: Leading. Variance patterns predict reliability of field screening as a decision-support tool.
  • Unit of Measure: %
  • Ideal Visualization(s): XY/scatter plot of field vs. lab values per element; KPI trend with real-time alerts when variance exceeds threshold; SPC trend (control chart) to detect systematic bias developing over time.
  • Frequency: Calculated as certified results are returned, cross-referenced against field readings.
  • Data Required: Field assay readings per sample, certified lab assay results per sample, sample ID, element, formation logged, field instrument calibration logs.
  • Pro Tip: Separate variance by element and by formation type. XRF performance in lateritic or clay-rich zones is structurally different from performance in fresh rock. Averaging all variance obscures where your field screening is actually breaking down.
  • Red Flag: Variance consistently biased in one direction (field reads high or low vs. lab) indicates an instrument calibration problem, not geological noise. Recalibrate before continuing to use field data for targeting.

Exploration Cost Per Meter

  • Why it Matters: Cost-per-meter is the fundamental efficiency benchmark for exploration programs. It determines whether your program will deliver the planned meters within budget and justifies expenditure against resource discovery.
  • What it Measures: The all-in direct cost attributed to each meter of hole drilled, including rig hire, consumables, field labour, and mobilisation amortisation.
  • What Happens if Missed: Cost-per-meter creep is one of the most common causes of exploration budget overruns. Programs go from “on track” to “we need $3M more” with very little warning when this KPI isn’t tracked in real time.
  • Formula: Total Exploration Direct Costs / Total Meters Drilled
  • Indicator Type: Current. Cost-per-meter tracks cumulatively and in real time against budget benchmarks.
  • Unit of Measure: $/m
  • Ideal Visualization(s): Bullet chart showing actual vs. budgeted cost per meter; KPI trend with real-time alerts when cumulative cost-per-meter exceeds threshold; Pareto chart when ranking cost contributors by variance from budget.
  • Frequency: Updated per shift as cost and advance data are reconciled.
  • Data Required: Rig hire costs, consumable costs, field labour hours and rates, mobilisation and demobilisation costs, total meters drilled.
  • Pro Tip: Calculate cost-per-meter by formation type as well as program-wide. Drilling costs in structurally complex or deep zones may warrant separate benchmarks to avoid distorting your overall program efficiency picture.
  • Red Flag: Cost-per-meter rising steadily without a corresponding change in formation difficulty or program scope signals an operational efficiency problem, not a geological one. Look at consumable burn rates and rig utilization first.

Why Real-Time Visibility Matters

Exploration programs are managed against geological uncertainty that can’t be fully controlled. What can be controlled is how fast you detect the operational signals that compound that uncertainty into cost and schedule blowouts. A rig sitting idle for six hours before the operations centre knows about it, a sample batch sitting at the lab past its SLA without anyone escalating, a field assay bias running for three weeks unchecked: none of these are catastrophic individually, but together they destroy program economics and geological confidence.

The difference between an exploration campaign that delivers a credible resource model on budget and one that requires re-scoping mid-program is rarely a single large failure. It’s the accumulation of small deviations that nobody caught in time to correct. Real-time KPI visibility closes that gap. It puts the right signal in front of the right person at the moment it still matters, not after the weekly report lands and the options have narrowed.

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