AVEVA Flex Credits Explained: What They Cost and What to Do About It

Illustration of rising bar charts alongside cloud, database, and server icons, representing AVEVA software costs, Flex Credits, and growing industrial data infrastructure complexity.

Rising software costs, shifting license models, and AVEVA Flex Credits can turn operational visibility into a budgeting puzzle. The smarter move is knowing what you’re paying for, what value you’re actually getting, and where modern real-time alternatives can reduce complexity without sacrificing performance.

If you’re a current AVEVA PI customer and your last renewal landed with a number you didn’t expect, you’re not alone. Across industries, PI customers are reporting price increases of 2x to 4x compared to what they paid just a few years ago. Some are seeing even steeper jumps.

The system behind those increases is called AVEVA Flex Credits. It replaced the older PI licensing model after Schneider Electric completed its acquisition of AVEVA in 2023. If you’ve tried to figure out exactly what Flex Credits are, how they’re calculated, or why your bill went up so much, you’ve probably noticed that AVEVA makes that information very difficult to find.

This article explains how Flex Credits work, what customers are actually paying based on publicly available procurement data, and what your options are if the model isn’t working for you.

What Are AVEVA Flex Credits?

AVEVA Flex Credits are the unit of currency in AVEVA’s subscription licensing model. Instead of buying a per-server license for PI Data Archive or paying a fixed annual fee per module, you purchase a pool of credits and draw from that pool based on the products and capacities you use.

On paper, this model sounds flexible, buy what you need, scale up or down. In practice, it works differently.

The number of credits consumed by your PI deployment depends on several factors simultaneously:

Number of PI Data Archive tags. This is the biggest driver for most customers. More tags, more credits.
Number of PI interfaces. Each interface to a data source draws from the credit pool.
Number of connected clients and users. PI Vision users, PI DataLink users, and other client connections consume credits.
Which PI modules you use. PI Notifications, PI Integrators, PI Connectors, and other add-on modules each have their own credit draw.
Whether you use AVEVA Connect. AVEVA’s cloud offering has its own credit component on top of the base allocation.

None of this is published. AVEVA does not post a credit rate card. You negotiate your credit pool at renewal, and the calculation of how many credits each component consumes is determined by AVEVA’s internal pricing team. If you exceed your allocated pool, you purchase top-up credits at a separate rate.

This design makes it structurally difficult to forecast your costs, compare prices with other customers, or challenge a renewal quote with market data. That opacity is a feature of the model from AVEVA’s perspective, not a bug.

What Customers Are Actually Paying

Because AVEVA doesn’t publish pricing, the clearest window into real-world costs comes from public procurement records, bid documents, contract awards, and government purchasing databases that are subject to disclosure requirements.

Here is what those records show:

Organization Type	Tag Count	Annual Cost	Notes
Mid-size utility	25,000 to 50,000 tags	$108,570/year	Public procurement record. Does not include top-up credits.
Larger industrial deployment	Mid-size estimate	~$162,000/year	Extrapolated from procurement data patterns.
Top-up credits	Per credit	$14.44/credit	Publicly documented rate for over-allocation.

These are not worst-case examples, they’re baseline figures for organizations with moderate PI deployments. Customers with larger tag counts, more interfaces, or multi-server PI architectures report substantially higher figures.

The 2x to 4x price increase pattern comes from comparing current Flex Credit renewals to what those same customers paid under the previous per-server pricing model. The shift isn’t a one-time adjustment. Customers who negotiated their first Flex Credit contracts two or three years ago are now seeing the second and third rounds of renewals, each higher than the last.

Why Prices Are Going Up

Understanding the trajectory requires understanding what happened to OSIsoft.

OSIsoft built the PI System over four decades and accumulated one of the most deeply embedded installed bases in industrial software. In 2021, AVEVA (then itself being acquired by Schneider Electric) paid approximately $5 billion to acquire OSIsoft. That acquisition price, and the subsequent Schneider Electric takeover of AVEVA itself, created significant capital obligations that need to be recouped through the existing customer base.

The engineers and product leaders who built PI’s original reputation have largely moved on following the acquisition. Development pace has slowed. ProcessBook, the visualization client thousands of operators had used for years, hit end-of-life in 2024 with no direct functional replacement. The momentum that once justified PI’s premium pricing, continuous innovation, a growing ecosystem, a strong product roadmap, has not kept pace with the price increases.

What customers are experiencing is the financial mechanics of a large acquisition being worked out through subscription pricing, in a market where their options to leave quickly are constrained by 20 years of data, deeply integrated control system connections, and organizational familiarity with the tools.

AVEVA is aware of this dynamic. The Flex Credit model was designed in part to make switching costs higher, not lower.

What the Flex Credit Model Does to Your TCO

The headline renewal cost is only part of the picture. Three other cost factors compound the Flex Credit problem over time.

PI administration headcount. A PI deployment of any scale requires at least one dedicated PI administrator, and often more. Managing the credit allocation, maintaining interfaces, handling AF model changes, supporting upgrades, and responding to user requests are full-time activities in most PI environments. Those salaries don’t appear on the AVEVA invoice but they belong in any honest total cost comparison.

System integrator costs. Major PI changes, new server deployments, PI Collective configurations for high availability, large AF restructures, PI version upgrades, typically require SI consulting. The knowledge required to manage PI at enterprise scale is specialized, and the pool of qualified PI administrators is not growing. When your PI admin retires, finding a replacement is an increasingly expensive proposition.

The credit trap as you grow. One of the counterintuitive effects of the Flex Credit model is that it penalizes customers for doing more with their data. Adding tag count, connecting new data sources, bringing more users onto PI Vision, all of these legitimate operational improvements draw from the credit pool and accelerate the renewal cost upward. The model structurally discourages exactly the kinds of data expansion that drive operational value.

Your Options

If your Flex Credits renewal is the trigger for this conversation, you have three realistic paths.

Option 1: Negotiate hard at renewal. Some customers have had success pushing back on renewal quotes, particularly if they have competitive quotes in hand. AVEVA does not want to lose large accounts. The risk is that you accept a short-term number without changing the underlying trajectory, and you’ll be in the same position at the next renewal.

Option 2: Reduce your PI footprint before renewal. Auditing your actual tag usage and decommissioning inactive tags or interfaces before the renewal window can reduce your credit draw. This requires PI administration time and a clear picture of what’s actually being used versus what’s been accumulating over years. It’s a legitimate tactic but not a long-term strategy.

Option 3: Evaluate alternatives, on your timeline. This is where most customers with serious Flex Credits frustration eventually land. The good news is that you don’t have to replace PI to start reducing your AVEVA dependency or get more value from the data you already collect.

Transpara reads PI data natively through the AF SDK. You can deploy Transpara on top of your existing PI infrastructure without changing anything about how PI works. Many customers do this first, extend PI’s value, give more people access to operational data, and prove ROI from Transpara, before making any decision about reducing their PI footprint. When they do decide to migrate, Transpara’s tStore can replace PI Data Archive at their pace, without a forced cutover and high risk.

The alternative to per-tag Flex Credits is signal-based pricing that doesn’t meter the historian. No per-tag charges. No credit pools. No top-up surprises.

Comparing Pricing Models: Flex Credits vs. Alternatives

Pricing Factor	AVEVA Flex Credits	Transpara
Per-tag charges	Yes	Simple Packaged Pricing
Per-user charges	Yes	Simple Packaged Pricing
Per-interface charges	Yes	Simple Packaged Pricing
Admin staff required	Yes (dedicated)	No (no full-time staff required)
Renewal predictability	Low (2-4x increases reported)	High
On-prem deployment	Yes, but AVEVA is pushing their SaaS-based Connect offering over on-prem)	Yes, customer-controlled (on-prem, customer cloud, hybrid)
Data stays in your environment	Partially (AVEVA Connect is SaaS, so your data lives with AVEVA)	Yes, always under your control

Before Your Next Renewal: Questions to Ask

If your Flex Credits renewal is coming up, these questions will help you enter that conversation with more leverage, and help you evaluate whether alternatives are worth pursuing seriously.

What is your current credit allocation, and how is it broken down? Ask AVEVA for a full breakdown of credit consumption by component: tags, interfaces, users, modules. If they’re reluctant to provide this in writing, that tells you something.

What drives the increase from your last renewal? AVEVA should be able to explain what changed in their pricing model or your consumption that accounts for the delta. If the answer is vague, push for specifics.

What is the cost trajectory if your tag count grows by 20% over the next three years? Model your likely growth and ask AVEVA to price that scenario. The answer often clarifies the long-term exposure.

What are your switching costs, realistically? This is worth understanding honestly, not to avoid change but to plan it. Years of PI data, embedded control system interfaces, and AF models are real considerations. A phased migration plan reduces switching costs significantly, but you need to know what you’re actually working with.

What does a competitive alternative cost for your footprint? Talking to at least one alternative vendor before a renewal gives you both market data and negotiating leverage. That conversation costs nothing.

Frequently Asked Questions

Does AVEVA publish Flex Credits pricing? No. AVEVA does not publish a Flex Credits rate card or standard pricing. Pricing is negotiated individually with each customer, which makes it structurally difficult to benchmark your quote against market rates.

How are Flex Credits calculated? Credits are consumed based on a combination of PI Data Archive tag count, number of interfaces, number of connected users and client applications, and which PI modules are active in your deployment. The specific credit weighting for each factor is set by AVEVA and is not published.

What are top-up credits? When your PI deployment consumes more credits than your allocated annual pool, you purchase top-up credits to cover the excess. Published procurement data shows a top-up rate of $14.44 per credit. Customers with growing tag counts or expanding user bases often encounter top-up charges between renewal cycles.

Can I reduce my Flex Credits bill by decreasing tag count? Yes, decommissioning unused or redundant tags before a renewal audit can reduce your credit draw. However, identifying which tags are genuinely inactive requires PI administration time, and the process doesn’t change the underlying pricing trajectory for an active deployment.

Is AVEVA Connect required? AVEVA Connect is AVEVA’s cloud offering and is being positioned increasingly as the default deployment path. It is not strictly required for all customers today, but AVEVA’s product direction strongly favors it and most new developments are focused on it. AVEVA Connect has its own credit component and means your PI data moves to AVEVA’s cloud infrastructure rather than staying in your environment, a meaningful consideration for regulated industries and organizations with data residency requirements.

What is the alternative to Flex Credits for PI data? The most direct alternative for organizations that want to keep their PI data but eliminate Flex Credits dependency is to deploy a modern operational intelligence platform that integrates and amplifies the value of PI natively while evaluating and migrating at your own pace with minimal risk.For organizations ready to replace PI Data Archive itself, tStore provides a modern time-series historian, asset modeling, advanced calculation and analytics, visualization and industrial AI platform with pricing and no per-tag fees.

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

Best PI Vision Alternatives for 2026

News

Live KPIs, color-coded status, and a map of the operation, all on the device already in your hand. Operators shouldn’t have to learn engineering software just to see how their plant is running, the right PI Vision alternative gives them what matters in seconds.

PI Vision has one job: show your PI data to the people who need it. The problem is, it rarely gets that far. Displays have to be built by hand, one screen at a time, by someone who knows PI Asset Framework inside and out. For most organizations, that’s one or two people. The result is a backlog of dashboard requests, a visualization tool that only a fraction of your workforce can actually use, and operators making decisions from printouts or memory while perfectly good data sits in the historian.

Then PI ProcessBook hit end-of-life in 2024. The people who relied on it were pointed to PI Vision. And a lot of them weren’t (and still aren’t) happy about it.

If you’re evaluating PI Vision alternatives, whether to extend what PI does, reduce your AVEVA dependency, or replace the whole stack, this guide covers the realistic options in 2026. We’ve tried to be honest about each one, including where competitors are genuinely strong.

Quick Comparison: PI Vision Alternatives at a Glance

Tool	Best For	Reads PI Data?	Auto-Generates Views?	Serves Non-Engineers?	Requires Coding?
Transpara	Full PI Vision replacement; Adds deep KPI and alerting; Spans all data sources (not just PI); org-wide KPI visibility; AI capabilities baked in	Yes, natively	Yes	Yes	No
dataPARC	Visualization layer on top of existing PI	Yes	Partial	Partial	No
Grafana	Developer-led teams building highly custom dashboards; Willing to maintain them over time	Yes, with plugin	No	No	Yes
Seeq	Process engineers doing deep time-series analysis; Not a direct replacement for PI Vision	Yes, natively	No	No	Partial
Power BI	Business reporting teams already in Microsoft ecosystem; Best for static, historic analysis (not real-time)	Yes, with connector	No	Partial	No
Canary Axiom	Smaller organizations replacing the PI historian itself; Limited functionality	Yes, natively	Partial	Partial	No

1. Transpara — Best Overall PI Vision Alternative

Best for: Organizations that want to replace PI Vision across sites or the whole organization, not just for engineers. Especially strong when you also want to mix PI data with other sources in a “single pane of glass” solution.

Transpara is not just the most direct replacement for PI Vision, it can also work together with PI Vision as you evaluate it. It is also the only option on this list that has a very different e design philosophy. PI Vision is focused on custom charts, trends and displays that require your team to build and maintain every screen. Transpara automatically generates most visualizations from your asset model, KPI definitions, etc and lets your users adjust them, drag and drop to dashboards and more, without needing to maintain them as displays or documents (they are part of a system, so changes to the model, KPI limits, filters, etc are automatically handled).

Define a KPI in tStudio, give it a name, a data source, and a set of thresholds, and tView automatically produces many visualizations of it, including status, a color-coded rollup including peers, a trend, a bullet chart, guague/dial, and more. Operators, plant managers, field staff, and executives all get meaningful views without anyone in IT building screens on their behalf or having to maintain them over time.

Critically, Transpara reads PI Data and PI AF (Asset Framework) natively. Your AF hierarchy imports and/or syncs directly into tModel using Transpara’s proprietary Remote Context Service (RCS) feature. Your tags stay in PI until and unless you choose to move them. You can be running Transpara on top of your existing PI System (and many other data sources)in days, without touching anything that already works.

What it does better than PI Vision:

Auto-generated views: no screen-building backlog
Mobile-first: fully responsive and genuinely usable on a phone, not just in demos
Multi-source: PI data sits alongside ERP, LIMS, other historians, SCADA, relational databases, data lakes and more in the same model and with the same obvious and consistent views
User-managed alerts: operators set their own thresholds and notification channels without requiring admin involvement
No AF or PI Vision specialist needed: if someone can use a any basic web or phone app, they can use Transpara. No training required.
No rework if key team members leave. Low long-term cost of ownership.

Honest limitations:

For highly custom PI Vision symbol libraries (think P&ID overlays with bespoke graphics), some transition work is involved.

Verdict: If your goal is to get operational data in front of more people, operators, managers, field teams, executives, without a permanent backlog of dashboard requests, Transpara is the strongest PI Vision alternative available in 2026. Its KPI-first design gives users more obvious performance signals and alerting, along with a mobile-first experience. It is also the only viable alternative that supports thousands of other data sources aggregated together with ease, and the only option here that doesn’t require your team to do most of the heavy lifting.

2. dataPARC — Best for a Familiar PI Vision Replacement

Best for: Organizations running PI that want a visualization replacement with a similar feel to what they already have, without changing the underlying data infrastructure.

dataPARC is the most frequently searched alternative to PI Vision, and it earns that position. It’s a process data visualization tool with a long track record in pulp and paper, and it openly markets itself as a PI Vision replacement. More than 50% of dataPARC installations run on top of existing PI historians, which means the migration story is straightforward: keep PI, swap the visualization layer.

The interface is familiar to PI users. It supports trends, displays, and process graphics in a way that won’t require your team to relearn how to navigate their data. For organizations where the main frustration with PI Vision is stability, performance, or the ProcessBook EOL, rather than a desire to reach more data sources or a much wider user base, dataPARC is a reasonable and proven option.

Where dataPARC works well:

Strong in process industries, especially pulp, paper, and chemicals
Reads PI data natively, relatively simple transition
Users familiar with PI Vision will find the learning curve gentle
Solid process graphics and trend capabilities

Honest limitations:

Still PI-centric. dataPARC doesn’t solve the multi-source problem, if your data lives beyond PI, you’re still dealing with it separately.
Views are still largely manually configured. The auto-generation problem that makes PI Vision frustrating doesn’t fully disappear.
Serves visualization specialists and engineers more naturally than it serves executives, field staff, or non-technical managers.
Thinner product outside its core pulp/paper/chemicals base.

Verdict: A solid choice if your main industry is pulp & paper, your key issue is that PI Vision is frustrating to use or maintain, and your goal is a like-for-like swap for a more pleasant experience on top of the same PI data. Not the right answer if you want to significantly expand who has access to operational data, additional data sources, and making things easier to maintain over time.

3. Grafana — Best for Developer-Led Teams

Best for: Organizations with technically strong OT/IT teams who want full control over their visualization stack and are willing to build it nearly from scratch and maintain it as a fully customer application.

Grafana is the most widely deployed open-source visualization tool in the world. It has plugins for PI data, it’s free to start, and it can be made to look impressive. For a technically capable developer team with time to invest, it can produce genuinely good industrial dashboards.

The trade-off is structural. Grafana is a blank canvas, it has no concept of KPIs, no asset model, no built-in historian, no advanced calculation engine, and no industrial alerting framework. Every dashboard is a custom development project. Every alert rule is written by hand. Every new user who needs a view or an adjustment means someone builds it for them. If the person who built your Grafana dashboards leaves, you inherit undocumented custom code.

Where Grafana works well:

Free entry point, hard to argue with for small deployments or proof-of-concepts
Enormous plugin ecosystem, including PI data connectors
Strong developer community and documentation
Well-suited for DevOps-culture organizations that already think in metrics and dashboards

Honest limitations:

Zero industrial structure out of the box. No KPIs, status colors, no automatic rollups.
High long-term total cost of ownership: developer time to build, developer time to maintain, developer time to onboard new users.
Not designed for operators, plant managers, or executives. Serving those users requires building separate custom applications.
Every Grafana deployment is unique, which makes it difficult to scale or transfer knowledge.

Verdict: The right call if your team is developer-led, already invested in Grafana infrastructure, and sees building software as part of their remit. Not the right call if your goal is putting operational data in front of 500 people who don’t have time to learn a complex tool and don’t have developers to build screens for them.

4. Seeq — Best for Process Engineers Doing Deep Analysis

Best for: Process engineering teams that need sophisticated time-series analysis capabilities, pattern recognition, SPC, correlation, and advanced troubleshooting, on top of PI data.

Seeq is great at what it does. In fact, it is overkill for many organizations or teams. It reads PI data natively, gives engineers powerful self-service analytics, and has earned its position as a leading industrial analytics tool for process engineers. Its 2025 Green Quadrant recognition reflects real product depth.

However, Seeq is not a PI Vision alternative in the way most readers of this page expect. It has no real-time KPI framework. It has no built-in historian. It has no org-wide visibility layer. It’s an analytics workbench for process engineers and data science specifically, not an operational dashboard for an entire facility.

Where Seeq works well:

Deep time-series analysis: pattern recognition, SPC, capsule-based event analysis
Strong for process troubleshooting and root cause investigation (reactive)
Self-service for engineers who know what they’re looking for
Integrates with PI natively

Honest limitations:

Recent dramatic price increases can make it very expensive quickly when you want more than a small engineering team to access operational data.
o real-time KPI framework, no org-wide alerting.
Requires engineers with deep training who know how to use it, not designed for operators, field staff, managers or executives.
SaaS-only, so your data lives with Seeq on their cloud

Verdict: If your goal is better visualization and broader access to PI data across your organization, Seeq is not the tool you’re looking for. If your goal is giving your process engineering team better analytical depth on top of PI data you’re already collecting, Seeq is worth evaluating, and it integrates with Transpara if you want both.

5. Power BI — Best for Static Analysis and Reports in Microsoft-Centric Organizations

Best for: Organizations focused on static reports and analysis that are already standardized on Microsoft that want to pull PI data into the same BI environment as their other reporting.

Power BI has a PI connector. It works, but in batch and not real-time. For organizations that already live in Microsoft and want a consistent reporting layer across operational and business data, this is a pragmatic option with a low adoption barrier; most people already have Power BI in their environment.

The honest conversation about Power BI for PI Vision replacement is the same one that applies to BI tools generally: Power BI was built for static, scheduled reporting, not live operational data. It refreshes on a schedule, not in real time. It has no KPI status framework, no industrial alerting, and no asset hierarchy. Most companies will have BI Tools AND OT visualization tools for good reason. They serve very different purposes, data sources, users and use cases.

Where Power BI works well:

Already in your Microsoft environment, no new vendor
Familiar to advanced analytics teams, reporting teams and trained knowledge workers
Good for operational reporting that doesn’t need to be real-time: shift summaries, weekly or monthly production reports, compliance snapshots

Honest limitations:

Not real-time. A tool that refreshes on a schedule is not the same as a tool that tells your operator right now that a compressor is about to fail.
No KPI framework or consistency, no status colors, no automatic alerting.
Building and editing production-grade operational dashboards in Power BI requires significant BI developer time and ongoing maintenance.
Licensed per user within Microsoft 365 plans or separately, can get expensive at scale.

Verdict: Use Power BI for static reporting. Use a purpose-built operational intelligence platform for live operations. Many Transpara customers run both, Power BI for scheduled business reporting, Transpara for real-time operational visibility. They serve different jobs, and conflating them usually means neither gets done well.

6. Canary Axiom — Best for Organizations Replacing the PI Historian

Best for: Smaller organizations that want to replace both the PI historian and the visualization layer together, starting from the data storage layer up.

Canary Labs is a historian-first company, its core product is a transparent, competitively priced time-series database that competes directly with PI Data Archive. Axiom is the visualization layer that sits on top of it. Canary’s pricing is fully published online (a rarity in this market), and unlimited-tag server licenses are available at roughly one-third the cost of AVEVA PI.

If your dissatisfaction with PI Vision is downstream of dissatisfaction with the PI System itself, the per-tag pricing, the Flex Credits model, the Windows dependency, then Canary is worth a look as a simple bundled historian and basic visualization replacement.

Where Canary works well:

Transparent, published pricing, no Flex Credit negotiation
Strong historian fundamentals: lossless compression, good data reliability
Axiom provides basic trend and display capabilities on top of Canary data
Over 20,000 installs in 75+ countries, so it’s a proven product

Honest limitations:

Canary is primarily a storage layer with visualization added. It doesn’t have the KPI framework, asset modeling, or multi-source aggregation that an organization-wide operational intelligence platform needs.
Axiom is functional but not the strongest visualization layer in this comparison. It serves its own historian use case well, not the org-wide operational visibility use case.
Best fit for price-sensitive organizations looking to solve the historian cost problem rather than the visualization reach problem.

Verdict: A strong option if your primary pain is PI historian pricing and you want a cleaner, cheaper storage layer with basic visualization included. Not the right choice if your primary goal is getting operational data to 500 people who currently have no access to PI Vision. Canary can also serve as a data source for Transpara, they’re complementary rather than mutually exclusive.

How to Choose

The right PI Vision alternative depends on what you’re actually trying to solve.

If your problem is “PI Vision is hard to use” and your team can’t keep up with screen requests: Transpara. It’s the only option that removes the screen-building bottleneck entirely by generating views from KPI definitions.

If you want visualization that spans multiple data sources (the “single pane of glass” concept): Transpara. It’s the only one that can quickly aggregate PI, other historians, and thousands of other applications into a single, obvious visualization layer.

If your problem is “PI Vision is frustrating” and you want a familiar replacement on the same PI data: dataPARC. Lower disruption, similar operational model.

If you want to get real-time operations data in front of more users in real-time without the need to train them all: Transpara. The KPI focus with status, color, alerting, and other context allows you to put valuable data in the hands of more users without adding to your maintenance burden.

If you you have a strong dev team and want full control and a completely custom experience: Grafana. Accept the TCO trade-off and build deliberately.

If your problem is your process engineers need better analytical tools: Seeq. Not a PI Vision replacement, but a genuine upgrade for engineering-depth users.

If your problem is PI historian pricing: Canary + Axiom. Solve the storage problem first, then revisit visualization.

If your problem is PI Vision and PI historian pricing and you want to solve both: Transpara replaces PI Vision immediately and can replace the PI historian at your pace, on your timeline.

Frequently Asked Questions

Does PI Vision have any free alternatives? Grafana is the only genuinely free option on this list, and it’s open-source. The total cost of ownership over three years is rarely lower than a paid platform once you account for developer time to build and maintain dashboards. For industrial operations teams where developer resources are limited, the free entry point often becomes a cost trap.

Can I replace PI Vision without replacing PI Data Archive? Yes. Transpara, dataPARC, Seeq, and Grafana all read PI data natively. You can keep your PI historian and swap only the visualization layer. This is the most common starting point for Transpara customers.

Does PI Vision work on mobile? Technically, PI Vision is web-based and can render on mobile. In practice, given how customer every display is, most PI Vision deployments are not optimized for mobile use. The displays are built for desktop screens and typically don’t adapt well to smaller viewports. Transpara is the only one with a genuinely mobile-first design.

What is the difference between PI Vision and PI ProcessBook? PI ProcessBook was OSIsoft’s older desktop-based visualization client (before AVEVA purchased OSIsoft). AVEVA ended support for ProcessBook in 2024 and directed users to PI Vision as the replacement. PI Vision is web-based; ProcessBook was a Windows fat client. Many ProcessBook users have found PI Vision to be a step backward in terms of workflow flexibility, which is a significant driver of the PI Vision alternative market in 2026.

Is Transpara officially an AVEVA partner? Yes. Transpara has partnered with OSIsoft and AVEVA for years and it integrates deeply with PI, AF and other AVEVA tools using the same mechanisms used by AVEVA’s own tools. Customers can run Transpara alongside their existing AVEVA licensing without requiring AVEVA’s approval or involvement.

How Transpara Can Help

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

Industry KPIs, News

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

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

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

Catchment Rainfall Intensity

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

Pump Station Wet Well Level

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

CSO Activation Frequency and Volume

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

Detention Storage Available

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

Sewer Surcharge Events

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

Outfall Turbidity at Discharge

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

Pump Cycling Frequency

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

Pump Specific Energy

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

Infiltration and Inflow Rate

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

Detention Basin Drawdown Time

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

Why Real-Time Visibility Matters

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

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

How Transpara Can Help

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

Industry KPIs, News

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

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

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

Power Usage Effectiveness (PUE)

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

IT Load Utilization

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

Inlet Air Temperature

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

UPS Battery Runtime Reserve

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

Cooling Unit Availability and Redundancy Margin

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

Generator Fuel Level and Auto-Start Readiness

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

Relative Humidity by Zone

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

Critical Power Path Availability

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

Rack Power Density

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

Network Infrastructure Uptime

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

Why Real-Time Visibility Matters

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

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

How Transpara Can Help

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

Industry KPIs, News

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

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

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

Crusher Throughput Rate

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

Crusher Availability

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

Crusher Power Draw

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

Closed Side Setting (CSS)

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

Feed Size Distribution (F80)

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

Liner Wear Index

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

Circuit Utilization

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

Vibration Index (Bearing and Drive)

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

Lubrication System Oil Temperature

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

Product Particle Size (P80)

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

Why Real-Time Visibility Matters

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

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

How Transpara Can Help

10 Real-Time KPIs Every Battery Manufacturing Operations Leader Should Be Tracking

Industry KPIs, News

A lithium-ion battery module moves through an automated assembly line, where real-time monitoring of cell voltage, temperature, and throughput rate keeps battery manufacturing operations running at peak efficiency and safety.

A gigafactory floor has no tolerance for ambiguity. Every process step from electrode coating to cell formation runs at speed, at scale, and in sequence, and a deviation at any one of them propagates downstream before most reporting systems even register that something changed. Lithium-ion battery manufacturing is one of the most process-sensitive production environments on the planet.

Moisture, temperature, coating uniformity, and electrochemical formation all interact across hundreds of interdependent steps. When visibility lags, defects compound silently, yield losses accumulate across millions of cells, and root cause analysis becomes archaeology. The ten KPIs below are the ones that keep gigafactory operations leaders ahead of the process rather than behind it.

Electrode Coating Weight and Thickness Uniformity

Why it Matters: Coating uniformity directly determines cell energy density, capacity, and cycle life. Variance at this step creates a defect that no downstream process can correct.
What it Measures: The mass loading of active material per unit area and the physical thickness of the wet and dry electrode coating across the full web width.
What Happens if Missed: Under-coated or over-coated electrodes produce cells outside specification, requiring sorting, rework, or scrap that multiplies across every cell in the affected roll.
Formula: Coating Weight Variance (%) = (Actual Coating Weight – Target Coating Weight) / Target Coating Weight × 100
Indicator Type: Current. Coating weight is a real-time in-line measurement; deviations compound with every meter of coated foil before intervention.
Unit of Measure: mg/cm²; µm (micrometers)
Ideal Visualization(s): KPI trend with real-time alerts for cross-web and machine-direction variance; bullet chart against target weight and tolerance band; Pareto chart when ranking coating lanes or shifts by defect frequency
Frequency: Real-time, continuous during active coating runs (every few seconds per in-line measurement point)
Data Required: In-line basis weight sensor readings (beta or X-ray gauge), wet film thickness, dry film thickness, line speed, target coating weight per recipe, tolerance limits
Pro Tip: Track cross-web uniformity as a separate KPI from machine-direction uniformity. They have different root causes and require different interventions.
Red Flag: A coating weight drift that tracks slot die pressure fluctuations confirms a feed system or rheology issue. A drift that tracks line speed changes points to a drying or tension control problem.

Drying Oven Moisture Content at Exit

Why it Matters: Residual moisture in electrodes is one of the primary causes of lithium plating, gas generation, and early cell failure. Every part per million above spec is a liability baked into every cell.
What it Measures: The moisture content of the dried electrode web at the exit of each drying oven zone, measured in parts per million by weight.
What Happens if Missed: Electrodes with excess moisture trigger electrolyte decomposition during formation, accelerate SEI layer degradation, and reduce cycle life in ways that don’t appear until field use.
Formula: N/A
Indicator Type: Current. Moisture at oven exit is a live pass/fail gate for every meter of electrode produced.
Unit of Measure: ppm (parts per million by weight)
Ideal Visualization(s): KPI trend with real-time alerts; bullet chart against specification limit and upper control limit; SPC trend (control chart) to detect moisture drift across production runs
Frequency: Real-time, continuous (in-line near-infrared or capacitance sensor)
Data Required: In-line moisture sensor readings per oven zone, oven temperature profile per zone, line speed, dew point of oven atmosphere, target moisture specification per electrode type
Pro Tip: Monitor dew point inside the oven atmosphere alongside electrode moisture. A rising dew point with stable oven temperature means your oven sealing or exhaust system is degrading.
Red Flag: Moisture readings that are consistently higher at the web edges than at the center indicate an airflow uniformity problem inside the oven, not a coating issue.

Dry Room Dew Point

Why it Matters: The dry room environment is the controlled atmosphere that protects electrodes, cells, and electrolyte from ambient moisture throughout assembly. A dew point excursion contaminates everything exposed during that window.
What it Measures: The dew point temperature of the dry room atmosphere at multiple monitoring points across the production floor, against the required specification for each process zone.
What Happens if Missed: Even brief dew point excursions during electrolyte filling or cell assembly introduce moisture that cannot be reversed. The affected cells either fail formation or degrade prematurely in the field.
Formula: N/A
Indicator Type: Current. Dry room dew point is a continuous environmental control KPI that must be within specification at all times, not just at the start of a shift.
Unit of Measure: °C dew point (typically maintained below -40°C or -50°C depending on process zone)
Ideal Visualization(s): KPI trend with real-time alerts per monitoring zone; group rollup bars showing dew point compliance status across all dry room zones; status history trend to identify which zones have the most excursion history
Frequency: Real-time, continuous (every 30 seconds to 1 minute per sensor)
Data Required: Dew point sensor readings per zone, HVAC dehumidification system status, air handling unit performance metrics, door open/close events, personnel entry logs
Pro Tip: Log door open events as a time-stamped overlay on your dew point trend. You’ll identify which access points are your largest moisture ingress sources within a week.
Red Flag: A dew point that recovers slowly after a door event compared to historical recovery time indicates dehumidification capacity degradation. It won’t suddenly fail. It will just keep getting slower.

Calendering Density and Porosity

Why it Matters: Calendering compresses the coated electrode to its target porosity, which governs lithium-ion transport, energy density, and rate capability. Over- or under-calendering cannot be compensated downstream.
What it Measures: The post-calendering electrode density (mass per unit volume) and estimated porosity, derived from thickness measurements and coating weight.
What Happens if Missed: Under-calendered electrodes have excessive porosity and lower energy density. Over-calendered electrodes crack the active material layer, creating internal resistance and mechanical failure points.
Formula: Electrode Density (g/cm³) = Coating Weight (mg/cm²) / Calendered Thickness (µm) × 1000
Indicator Type: Current. Calendering density is set in real time and determines the structural quality of every cell made from that electrode.
Unit of Measure: g/cm³; % porosity
Ideal Visualization(s): KPI trend with real-time alerts; bullet chart against target density and upper/lower limits; Pareto chart when ranking calender roll pairs by density deviation frequency
Frequency: Real-time, continuous (in-line thickness and weight measurement after calender nip)
Data Required: Post-calender electrode thickness, coating weight from upstream measurement, foil thickness, calender nip pressure, roll temperature, line speed
Pro Tip: Track calender roll temperature independently from nip pressure. Thermal expansion of the rolls shifts effective nip gap in ways that pressure control alone won’t compensate for.
Red Flag: Electrode density that oscillates with a repeating spatial frequency points to roll eccentricity or bearing wear on the calender. The pattern appears in the data before it appears in yield.

Formation Cycle Capacity and Coulombic Efficiency

Why it Matters: Formation is the first charge/discharge of each cell and determines whether the SEI layer forms correctly. It is the electrochemical birth certificate of every cell leaving the line.
What it Measures: The discharge capacity achieved during formation cycling as a percentage of the theoretical design capacity, alongside coulombic efficiency (charge returned divided by charge input) per cycle.
What Happens if Missed: Cells with low formation capacity or poor coulombic efficiency have compromised SEI layers that continue to grow during use, accelerating capacity fade and increasing field failure risk.
Formula: Coulombic Efficiency (%) = Discharge Capacity (mAh) / Charge Capacity (mAh) × 100
Indicator Type: Lagging for the completed formation cycle; Leading for field performance and warranty outcomes.
Unit of Measure: mAh (capacity); % (coulombic efficiency)
Ideal Visualization(s): KPI trend with real-time alerts by formation channel or tray; bullet chart comparing actual capacity against design specification; Pareto chart when ranking formation trays or channels by yield failure rate
Frequency: Per formation cycle step (multiple data points per cell over hours to days of formation)
Data Required: Charge capacity per channel, discharge capacity per channel, voltage profile per step, formation temperature, channel current accuracy, cell internal resistance at end of formation
Pro Tip: Coulombic efficiency on the first cycle is the most predictive single number for long-term cycle life. Build your grading thresholds around it, not just around capacity.
Red Flag: A cluster of low-efficiency cells from a specific formation tray position that repeats across batches points to a channel calibration or contact resistance issue at that physical location.

Electrolyte Fill Weight Accuracy

Why it Matters: Electrolyte fill volume determines lithium-ion transport capacity, wetting uniformity, and ultimately cell impedance. Fill variance is capacity variance, locked in before the cell is sealed.
What it Measures: The actual mass of electrolyte injected into each cell compared to the recipe target fill weight, measured gravimetrically at the fill station.
What Happens if Missed: Underfilled cells have higher impedance and lower rate capability. Overfilled cells risk electrolyte leakage at the seal or venting events during formation.
Formula: Fill Weight Variance (mg) = Actual Fill Weight – Target Fill Weight
Indicator Type: Current. Fill weight is measured and locked at the point of injection; there is no opportunity to correct it after sealing.
Unit of Measure: grams (g) or milligrams (mg); % variance from target
Ideal Visualization(s): KPI trend with real-time alerts per fill needle or station; bullet chart against target and tolerance; SPC trend to detect fill system drift before yield impact
Frequency: Per cell filled; real-time during active filling operations
Data Required: Gravimetric fill weight per cell per fill station, target fill weight per cell format, fill needle pressure, electrolyte temperature and viscosity at point of use
Pro Tip: Track fill weight variance by fill needle position, not just by station. Individual needle wear or partial blockages produce systematic underfill patterns that averaging hides.
Red Flag: Fill weight that drifts downward gradually over a shift without a recipe change points to electrolyte viscosity change from temperature or moisture absorption in the supply line.

Cell Internal Resistance at End of Line

Why it Matters: Internal resistance (IR) is a composite indicator of electrode quality, electrolyte wetting, tab welding integrity, and SEI formation. It tells you the condition of the entire cell in one number.
What it Measures: The AC impedance or DC internal resistance of each cell measured at end-of-line testing, compared against the specification for that cell format and chemistry.
What Happens if Missed: High-IR cells have reduced power capability and generate excess heat under load. Shipping them undetected creates field warranty exposure and safety risk in energy storage applications.
Formula: IR Variance (%) = (Actual IR – Target IR) / Target IR × 100
Indicator Type: Lagging for the production process that created the cell; Leading for field reliability and thermal management performance.
Unit of Measure: mΩ (milliohms)
Ideal Visualization(s): KPI trend with real-time alerts; bullet chart against specification and upper control limit; Pareto chart when ranking production lines or shift periods by high-IR cell yield
Frequency: Per cell at end-of-line test; real-time during active testing
Data Required: AC impedance measurement per cell (at 1kHz), DC pulse resistance measurement, state of charge at test, cell temperature at test, test fixture contact resistance calibration values
Pro Tip: Separate IR into its resistive and reactive components if your test equipment allows it. Rising reactive impedance with stable DC resistance points to a wetting or SEI issue. Rising DC resistance points to a tab or contact problem.
Red Flag: A shift in median IR across an entire production lot without a recipe change usually traces to a change in raw material lot. Cross-reference your material traceability data immediately.

Winding or Stacking Alignment Tolerance

Why it Matters: Electrode and separator alignment during winding or stacking determines the physical integrity of the jellyroll or stack. Misalignment creates internal short-circuit risk that thermal runaway events are built from.
What it Measures: The lateral offset of anode, cathode, and separator layers relative to each other at the winding mandrel or stacking station, measured in real time by vision systems.
What Happens if Missed: Misaligned electrodes allow lithium deposition on exposed anode edges, creating metallic lithium dendrite nucleation sites that grow into short circuits under cycling.
Formula: Alignment Offset (mm) = Measured Edge Position – Target Edge Position
Indicator Type: Current. Alignment is a real-time in-process measurement with no correction window once the cell is wound or stacked and sealed.
Unit of Measure: mm
Ideal Visualization(s): KPI trend with real-time alerts per web guide axis; bullet chart showing offset against tolerance band; Pareto chart when ranking winding or stacking stations by alignment fault frequency
Frequency: Real-time, continuous (vision system frame rate, typically multiple measurements per second)
Data Required: Vision system edge detection measurements for anode, cathode, and separator per axis, web tension readings, winding speed or stacking cycle rate, machine vibration sensors
Pro Tip: Set tighter alert thresholds than your outgoing inspection reject limits. Finding alignment issues in the winder costs seconds. Finding them at EOL costs cells.
Red Flag: Alignment drift that correlates with winding speed increases points to a web tension control issue. Drift that correlates with roll changeovers points to a splicing or core loading problem.

First Pass Yield by Process Step

Why it Matters: First pass yield (FPY) at each process step reveals where defects originate, not just where they are detected. The gap between those two locations is where your scrap cost lives.
What it Measures: The percentage of cells or electrode units that pass each process step’s quality gate without requiring rework, sorting, or scrap on the first attempt.
What Happens if Missed: Without step-level FPY visibility, defect origination is invisible. Total yield looks acceptable while one or two process steps silently drive all the losses and rework cost.
Formula: FPY (%) = Units Passing Step Without Rework / Total Units Entering Step × 100
Indicator Type: Lagging at the step level; Leading for overall line yield and cost of quality.
Unit of Measure: % yield
Ideal Visualization(s): KPI trend with real-time alerts per process step; Pareto chart ranking process steps by FPY loss contribution; bar chart comparing FPY across shifts, lines, or product formats
Frequency: Per production lot or batch; rolling hourly for operational awareness during active production
Data Required: Units in per step, units passing per step, rework volume per step, scrap volume per step, defect classification codes per step, shift and line identifiers
Pro Tip: Cascade FPY data from final test back to the originating process step using defect traceability codes. Yield loss detected at formation frequently originates at coating or calendering.
Red Flag: FPY that degrades progressively across a shift without a recipe or material change points to tool wear, consumable degradation, or an environmental drift that builds over time.

Formation Throughput vs. Capacity Plan

Why it Matters: Formation is the longest fixed-time process in cell manufacturing. It cannot be rushed, and every channel-hour lost is a cell-hour of capacity permanently gone.
What it Measures: The actual number of cells completing formation per hour or per shift compared against the planned throughput required to meet the production schedule.
What Happens if Missed: Formation bottlenecks suppress every upstream and downstream process in the factory. When formation falls behind, the entire line either waits or builds an inventory problem.
Formula: Formation Throughput Variance (%) = (Actual Cells Completed – Planned Cells) / Planned Cells × 100
Indicator Type: Current. Throughput variance accumulates in real time and determines whether that shift meets its plan or borrows from the next one.
Unit of Measure: Cells per hour; cells per shift; % variance from plan
Ideal Visualization(s): KPI trend with real-time alerts; bullet chart showing actual throughput against plan and lower threshold; group rollup bars showing throughput status across formation room sections
Frequency: Real-time, rolling hourly; per shift summary
Data Required: Active channel count, cells in formation per channel, cells completing formation per time period, formation cycle time per recipe, planned throughput from production schedule, channel fault or downtime events
Pro Tip: Track available channel utilization separately from throughput. Low throughput from low utilization is a scheduling problem. Low throughput from extended cycle time is a process or recipe problem.
Red Flag: Formation throughput that declines across the week without a downtime event usually means channel maintenance backlog is accumulating. The decline accelerates if it isn’t addressed.

Why Real-Time Visibility Matters

Lithium-ion gigafactory operations run at a scale where small process deviations become large financial and safety consequences within hours. A dew point excursion that lasts twenty minutes, a coating weight drift that runs for two rolls, or a formation channel fault that goes unreported until end-of-shift are not isolated incidents. At gigafactory throughput rates, they are yield events measured in thousands of cells and hundreds of kilowatt-hours of lost capacity.

The KPIs in this list share a common requirement: they need to be visible in real time, correlated across process steps, and connected to alerts that reach the right people before the window for intervention closes. Tracking them after the fact tells you what happened. Tracking them live gives you the chance to change what happens next.

How Transpara Can Help

10 Real-Time KPIs Every Brewing and Distilling Operations Leader Should Keep on Their Radar

Industry KPIs, News

Rows of stainless steel mash tuns line the brewhouse floor of a modern brewing and distilling facility, where precise temperature and process control at every stage determines product consistency and yield quality.

Fermentation doesn’t wait for your shift report, and neither does a stuck mash, a runaway temperature, or a batch heading toward drain disposal. In brewing and distilling, the margin between a great product and a costly write-off is often measured in degrees, minutes, and fractions of a percentage point. When you’re running multiple fermenters, stills, and aging vessels simultaneously, operating on lagging data means you’re always reacting to problems that have already finished happening.

The ten KPIs below are the ones that separate operations leaders who catch issues early from those who find them during quality checks, or worse, during customer complaints.

Fermentation Temperature Deviation

Why it Matters: Temperature variance during fermentation directly affects yeast health, flavor compounds, and final alcohol yield. A runaway fermenter can ruin an entire batch.
What it Measures: The difference between the actual fermentation vessel temperature and the target setpoint at any given moment.
What Happens if Missed: Off-flavors, yeast stress, incomplete attenuation, and potential batch loss compound across every hour you miss the deviation.
Formula: Actual Vessel Temperature – Target Setpoint Temperature
Indicator Type: Current. Temperature is moving in real time, and the damage accumulates while you’re not watching.
Unit of Measure: °C or °F
Ideal Visualization(s): KPI trend with real-time alerts; bullet chart showing current value against target and high/low limits
Frequency: Real-time (every 30 seconds to 1 minute)
Data Required: Vessel temperature sensor readings, target temperature setpoint per vessel, high/low limit thresholds
Pro Tip: Set your alert thresholds tighter than your quality limits. Catching a 0.5-degree drift early is far cheaper than chasing a full-degree excursion.
Red Flag: Repeated temperature cycling in the same vessel over multiple batches signals a glycol chiller or control valve issue, not a one-off event.

Alcohol by Volume (ABV)

Why it Matters: ABV is a regulated value, a product specification, and a direct measure of fermentation performance all at once. Missing target means blending, dilution, or disposal.
What it Measures: The deviation of current or projected final ABV from the recipe target, tracked through the fermentation cycle.
What Happens if Missed: Under-attenuation ships a weaker product. Over-attenuation triggers labeling and compliance issues that are expensive to unwind.
Formula: (Projected Final ABV – Target ABV) / Target ABV × 100
Indicator Type: Leading. Gravity readings mid-fermentation forecast where ABV is heading before it gets there.
Unit of Measure: % ABV
Ideal Visualization(s): KPI trend with real-time alerts; bullet chart against recipe specification limits
Frequency: Every 15 to 30 minutes during active fermentation; hourly during conditioning
Data Required: Original gravity, current gravity, temperature-adjusted density readings, target final gravity, recipe ABV specification
Pro Tip: Calculate projected ABV from current gravity trajectory rather than waiting for final gravity. You have time to intervene if you look early enough.
Red Flag: Fermentation that stalls above target gravity and stays flat for more than six hours needs immediate attention. Waiting another shift is not a strategy.

Still Reflux Ratio and Distillate Cut Point

Why it Matters: The reflux ratio controls the balance between yield and purity. Getting the cut wrong means heads and tails contaminate your hearts fraction, or you leave yield on the table.
What it Measures: The ratio of liquid returned to the still column versus distillate collected, alongside the temperature profile at the cut transition points.
What Happens if Missed: Methanol and fusel alcohols carry into the product. Quality failures at this stage require redistillation or disposal, both expensive.
Formula: Reflux Ratio = Liquid Returned to Column / Distillate Collected
Indicator Type: Current. Both the ratio and the cut point temperatures shift dynamically as the run progresses.
Unit of Measure: Ratio (dimensionless); cut point in °C or °F
Ideal Visualization(s): KPI trend with real-time alerts for cut point temperature; bullet chart for reflux ratio against target range
Frequency: Real-time (continuous during active distillation run)
Data Required: Column temperature at multiple tray levels, distillate flow rate, reflux return flow rate, condenser inlet/outlet temperatures
Pro Tip: Map your cut point temperatures against your specific wash chemistry for each product. A generic temperature threshold will cost you yield or quality.
Red Flag: A rising still head temperature that plateaus and then drops again mid-run signals a flooding event in the column. Stop the run and investigate.

Yeast Viability and Pitch Rate

Why it Matters: Pitching stressed or under-count yeast is the fastest way to a slow, incomplete, or contaminated fermentation. It sets the ceiling on every batch before it starts.
What it Measures: The count of viable yeast cells per milliliter of wort or wash at the point of pitching, compared against the recipe target pitch rate.
What Happens if Missed: Under-pitching produces stressed yeast and off-flavors. Over-pitching accelerates fermentation so quickly that flavor development suffers in styles where it matters.
Formula: Pitch Rate Variance (%) = (Actual Cells/mL – Target Cells/mL) / Target Cells/mL × 100
Indicator Type: Leading. Pitch rate determines fermentation trajectory before the vessel is even sealed.
Unit of Measure: Cells/mL; % variance from target
Ideal Visualization(s): KPI block with status color; bullet chart showing actual pitch rate against target and tolerance bands; Pareto chart when ranking batches by pitch rate deviation across multiple fermenters
Frequency: Per batch at time of pitching; trended over batch history
Data Required: Yeast cell count at pitching, yeast viability percentage, wort/wash volume, target pitch rate from recipe
Pro Tip: Track viability alongside cell count. 200 million cells/mL at 60% viability is a very different pitch than the same count at 95% viability.
Red Flag: A consistent decline in viability across successive repitch generations signals it’s time to retire the strain, not just repitch again.

Dissolved Oxygen at Packaging

Why it Matters: Oxygen pickup at packaging is the single largest controllable driver of stale, cardboard, or papery flavors in finished beer and spirits. You can brew perfectly and package badly.
What it Measures: The concentration of dissolved oxygen in the product at the point of filling, measured in parts per billion or parts per million.
What Happens if Missed: Elevated Dissolved Oxygen (DO) accelerates oxidation in the package, shortening shelf life and degrading flavor, often before the product reaches the consumer.
Formula: N/A
Indicator Type: Current. DO at the filler is a real-time pass/fail signal, not a historical report.
Unit of Measure: ppb (parts per billion) or ppm (parts per million)
Ideal Visualization(s): KPI trend with real-time alerts; SPC trend to detect process drift over filling runs
Frequency: Real-time, continuous during filling operations
Data Required: Inline DO sensor readings at filler bowl or product manifold, target specification, upper control limit
Pro Tip: Monitor both the product DO and the counter-pressure gas purity independently. A clean product line with contaminated CO2 or nitrogen will still give you elevated DO.
Red Flag: A stepwise increase in DO readings that corresponds with a pump seal change or line connection event points to a specific mechanical failure, not random variation.

Clean-in-Place Cycle Effectiveness

Why it Matters: An incomplete Clean-in-Place (CIP) cycle leaves residual organics, biofilm precursors, or caustic residue in vessels and lines. The next batch pays the price.
What it Measures: Whether each CIP stage (pre-rinse, caustic wash, acid wash, final rinse) reached its required temperature, concentration, flow rate, and duration.
What Happens if Missed: Microbial contamination, cross-flavor carryover, and regulatory non-compliance follow incomplete or out-of-spec cleaning cycles with compounding consequences.
Formula: CIP Compliance (%) = Steps Completed Within Spec / Total Required Steps × 100
Indicator Type: Lagging. CIP completion is confirmed after the cycle, but it directly determines the safety of the next run.
Unit of Measure: % compliance; individual step duration in minutes; temperature in °C; concentration in %
Ideal Visualization(s): KPI block with pass/fail status; status history trend to track CIP compliance across vessels over time; Pareto chart when ranking vessels by CIP failure frequency
Frequency: Per cycle; every CIP event logged and scored
Data Required: CIP step durations, caustic and acid concentrations, rinse water conductivity or pH, flow rates, temperatures per stage, pass/fail thresholds per recipe
Pro Tip: Log rinse conductivity as your final rinse confirmation. A conductivity reading that doesn’t reach baseline is more reliable than a timer as proof the caustic is gone.
Red Flag: A vessel that consistently shows marginal CIP compliance on the caustic step is telling you the spray ball coverage or flow velocity is degraded. Check the mechanical system, not just the recipe.

Barrel Fill Volume and Cooperage Utilization

Why it Matters: In distilling, every barrel is a long-term asset tied to a specific product commitment. Underfill means lost aging yield; overfill creates cooperage stress and potential leakage.
What it Measures: The actual fill volume per barrel at the point of barreling, compared to the target fill specification and total cooperage capacity utilization across the warehouse.
What Happens if Missed: Systematic underfilling silently erodes yield across thousands of barrels. Overfilling damages staves and hoops, leading to leakers and insurance events.
Formula: Fill Variance (%) = (Actual Fill Volume – Target Fill Volume) / Target Fill Volume × 100
Indicator Type: Current. Fill volume is a real-time measurement at the point of production, with long-term financial consequences.
Unit of Measure: Liters or gallons; % variance
Ideal Visualization(s): KPI trend with real-time alerts during barreling runs; bullet chart per filling station against target and tolerance; Pareto chart when ranking filling stations by variance frequency
Frequency: Per barrel filled; real-time during active barreling
Data Required: Flow meter readings per fill, target fill volume per cooperage type, total active cooperage count, warehouse location data
Pro Tip: Trend fill variance by filling station independently. Station-level drift is a mechanical calibration issue that gets hidden when you only look at batch averages.
Red Flag: Fill variance that tracks ambient temperature closely points to a thermal expansion issue in your flow measurement system, not an operator error.

Glycol System Capacity and Chiller Load

Why it Matters: Your glycol system is the thermal backbone of the entire facility. When it’s running at the edge of capacity, you lose the ability to respond to fermentation excursions or conditioning demands.
What it Measures: Current glycol chiller load as a percentage of rated capacity, alongside glycol supply and return temperatures across the distribution system.
What Happens if Missed: Overloaded chillers reduce cooling responsiveness across all vessels simultaneously, turning one fermentation excursion into several at once.
Formula: Chiller Load (%) = Current Thermal Load (kW) / Rated Capacity (kW) × 100
Indicator Type: Current. Chiller load is a live system health indicator tied directly to your ability to hold fermentation temperatures.
Unit of Measure: % load; °C or °F for supply/return temperatures; kW
Ideal Visualization(s): KPI trend with real-time alerts; group rollup bars showing load distribution across multiple chiller units
Frequency: Real-time (every 1 to 2 minutes)
Data Required: Compressor current draw or kW output, glycol supply temperature, glycol return temperature, rated chiller capacity, individual vessel demand signals
Pro Tip: Set a high-load alert well before rated capacity so you have time to shed non-critical loads before fermentation temperature control is compromised.
Red Flag: A chiller that runs at high load even when vessel demand is low signals refrigerant charge degradation, condenser fouling, or a glycol leak. It won’t self-correct.

Spent Grain and Byproduct Throughput

Why it Matters: Spent grain removal is a logistical constraint that directly affects brew cycle time. A bottleneck here backs up the lauter tun and delays subsequent brews.
What it Measures: The rate at which spent grain and other byproducts are removed from the brewhouse versus the production schedule requirement.
What Happens if Missed: Lauter tun holdups compress brew cycle time, reduce daily brew capacity, and create disposal compliance risks if wet grain sits too long.
Formula: Byproduct Removal Rate (tons/hr) = Volume Removed / Time Period
Indicator Type: Current. Removal rate tracks against a real-time schedule that determines whether the next brew starts on time.
Unit of Measure: Tons/hour or kg/hour; % of scheduled removal completed
Ideal Visualization(s): KPI block with status; KPI trend with real-time alerts against removal schedule; bullet chart showing actual vs. target removal rate
Frequency: Every 15 minutes during active removal; per brew event
Data Required: Spent grain conveyance system flow rate or load cell data, removal vehicle weight tickets, scheduled removal windows, lauter tun grain bed status
Pro Tip: Track this KPI by day of week and season. Spent grain contractors have their own capacity limits, and predictable shortfalls are schedulable if you spot the pattern.
Red Flag: Removal rates that decline progressively across the week without a schedule change point to conveyance equipment wear or contractor capacity issues building under the surface.

Energy Consumption per Barrel Equivalent (BBL)

Why it Matters: Energy is one of the largest controllable costs in a brewery or distillery. Tracking it per unit of production separates efficiency gains from volume changes.
What it Measures: Total energy consumed across thermal and electrical systems divided by the number of barrel equivalents produced in the same period.
What Happens if Missed: Energy cost creep is invisible until the utility bill arrives. By then, an entire month of inefficient operation has already been paid for.
Formula: Energy per BBL = Total Energy Consumed (kWh or BTU) / Total Barrel Equivalents Produced
Indicator Type: Lagging. This KPI reports on efficiency already achieved, but real-time sub-metering makes it possible to intervene within the same shift.
Unit of Measure: kWh/BBL or BTU/BBL
Ideal Visualization(s): KPI trend with real-time alerts for daily rolling values; bar chart comparing energy per BBL across production lines or product types; Pareto chart when ranking energy consumers by contribution to total load
Frequency: Rolling hourly for operational awareness; daily for reporting
Data Required: Electrical sub-meter readings by zone (brewhouse, fermentation, packaging, HVAC, refrigeration), steam or gas consumption, barrel equivalent production volume
Pro Tip: Segment energy per BBL by product type. High-gravity production, long conditioning runs, and distillation have radically different energy profiles that average out to meaninglessness when combined.
Red Flag: A sudden increase in energy per BBL without a product mix change or volume drop points to a specific piece of equipment running inefficiently. Sub-meter data will tell you which one.

Why Real-Time Visibility Matters

Brewing and distilling operations span days, weeks, and years across fermentation, aging, and packaging. The gap between a process signal appearing and an operations leader seeing it is where product quality, yield, and cost targets get eroded. A fermentation temperature deviation that goes unnoticed for four hours is not the same problem as one caught in four minutes.

The KPIs above are not observations made after the fact. They’re the operational signals that determine whether you’re making corrections or making excuses. When they’re visible in real time, correlated across vessels and systems, and set to alert the right people before thresholds become losses, they shift the entire operation from reactive to in control.

How Transpara Can Help

10 Real-Time KPIs Every Semiconductor Fabrication Operations Leader Should Keep on Their Radar

Industry KPIs, News

A technician seats a CPU into a motherboard socket during the assembly phase of semiconductor fabrication, where precision handling and controlled environments are critical to protecting delicate integrated circuits.

A fab floor is one of the most instrumented environments on the planet, and yet the gap between data collected and decisions made in time is where yield points and capacity commitments quietly disappear. When process drift goes undetected for even a few wafer lots, the cost compounds fast.

A single lithography excursion propagating through downstream steps before anyone catches it does not just damage those lots; it ties up equipment, disrupts WIP flow, and triggers expedite cycles that ripple across the schedule. Cleanroom events, tool availability drops, and cycle time excursions all operate the same way: invisible until they are expensive. The ten KPIs below are the ones that tell you what is actually happening inside your fab right now, not what happened during the last shift review.

Wafer Starts per Week

Why it Matters: Wafer starts drive every downstream capacity and delivery commitment. Deviations from plan compound quickly across a fab’s long cycle time.
What it Measures: The count of wafers entered into the production queue per week, compared against plan.
What Happens if Missed: Shortfalls surface too late to recover within the same planning horizon, forcing schedule push-outs to customers.
Formula: Actual Wafer Starts / Planned Wafer Starts x 100
Indicator Type: Current. This KPI reflects live production entry rate and signals capacity alignment in the near term.
Unit of Measure: Wafers per week (% of plan)
Ideal Visualization(s): KPI trend with real-time alerts; bullet chart showing actual vs. plan
Frequency: Daily rollup with real-time lot-entry tracking
Data Required: Lot release timestamps, wafer count per lot, weekly production plan targets
Pro Tip: Track by product family, not just total starts. Shortfalls on advanced node products are not equivalent to shortfalls on mature node products.
Red Flag: Three or more consecutive days below 95% of plan usually signals an upstream material or equipment availability issue, not a scheduling artifact.

Fab Cycle Time

Why it Matters: Cycle time is the primary lever on delivery performance and capacity utilization. Every extra day in queue is a day of customer lead time you cannot recover.
What it Measures: The elapsed time from wafer start to completion of the last process step, compared against target cycle time.
What Happens if Missed: Cycle time creep inflates WIP, reduces throughput efficiency, and breaks commit dates without any single obvious failure to point to.
Formula: Actual Cycle Time / Target Cycle Time x 100
Indicator Type: Lagging. Cycle time reflects the cumulative result of equipment availability, queue management, and process stability across all steps.
Unit of Measure: Days (% of target)
Ideal Visualization(s): KPI trend with real-time alerts; box plot for cycle time distribution by product layer
Frequency: Updated per lot completion; rolling 7-day average
Data Required: Lot start timestamp, lot completion timestamp, step-level queue wait times, target cycle time by product
Pro Tip: Separate queue wait time from active process time. Most cycle time inflation hides in queue, not on tool.
Red Flag: Cycle time rising while starts hold steady points to a bottleneck tool or a WIP imbalance building at a specific layer.

Gross Die Yield

Why it Matters: Gross die yield is the most direct measure of fab process health and the primary driver of cost per good die. Small yield shifts at volume have large financial consequences.
What it Measures: The percentage of functional dies produced per wafer relative to the theoretical die count at that reticle step.
What Happens if Missed: Yield excursions that propagate across multiple lots before detection create write-off events that cannot be recovered within the affected quarter.
Formula: (Good Die Count / Theoretical Die Count) x 100
Indicator Type: Lagging. Yield integrates the quality of every process step a wafer has passed through.
Unit of Measure: Percent (%)
Ideal Visualization(s): SPC trend (control chart) with real-time alerts; KPI trend with real-time alerts by product and lot
Frequency: Per lot at final electrical test; interim parametric yield at key in-line test steps
Data Required: Good die count per wafer, theoretical die count per reticle, lot identifiers, process layer, product code
Pro Tip: Watch yield by process layer, not just final test. Parametric yield at intermediate steps often predicts final yield weeks earlier.
Red Flag: A yield drop confined to a specific layer or tool group almost always points to a process excursion or equipment maintenance issue, not a random event.

Critical Tool Availability

Why it Matters: Availability of bottleneck tools drives fab throughput more than any scheduling decision you can make. A lithography stepper or etch chamber down at the wrong time cascades across the entire floor.
What it Measures: The percentage of scheduled production time that a critical tool is available and running, excluding planned maintenance windows.
What Happens if Missed: Unplanned downtime on a bottleneck tool creates WIP starvation at downstream steps and ripples through delivery schedules within hours.
Formula: (Scheduled Time – Unplanned Downtime) / Scheduled Time x 100
Indicator Type: Current. This KPI reflects live equipment state and responds immediately to faults, alarms, and maintenance events.
Unit of Measure: Percent (%)
Ideal Visualization(s): KPI blocks for each critical tool; Pareto chart when ranking tools by unplanned downtime contribution; KPI trend with real-time alerts
Frequency: Real-time, updated per tool state change
Data Required: Tool scheduled production time, unplanned downtime events with timestamps, tool state (running, idle, down, maintenance), tool classification
Pro Tip: Track availability separately for bottleneck tools vs. non-bottleneck tools. Aggregate fab availability numbers mask the equipment that actually controls throughput.
Red Flag: Availability trending down gradually over two to three weeks often signals a tool that needs preventive maintenance before it causes an unplanned stop.

Defect Density (D0)

Why it Matters: Defect density is the leading process health signal at every layer. It predicts yield before electrical test data is available and identifies contamination events early enough to contain them.
What it Measures: The number of particle or pattern defects per square centimeter on the wafer surface at a given process step.
What Happens if Missed: A defect density excursion that is not caught at the inspection step will be confirmed only at final yield, by which point multiple additional lots have passed through the same compromised process.
Formula: Total Defects / Inspected Wafer Area (cm²)
Indicator Type: Leading. D0 at in-line inspection predicts final electrical yield and flags equipment or process issues before they fully express as failures.
Unit of Measure: Defects per cm²
Ideal Visualization(s): SPC trend (control chart) with real-time alerts; KPI trend with real-time alerts by inspection layer and tool
Frequency: Per lot at each scheduled inspection point
Data Required: Defect count per wafer, inspected area per wafer, inspection step, lot identifier, tool used at prior process step
Pro Tip: Correlate D0 spikes with specific tool IDs at the preceding process step. Most contamination events have a single tool source that shows up clearly in the data.
Red Flag: D0 rising on a single inspection layer while adjacent layers hold steady is a strong signal of a localized tool or chamber problem, not a systemic process drift.

Cleanroom Particle Count

Why it Matters: The cleanroom environment is a shared resource. A particle event anywhere in the fab threatens yield across all product types running on the floor simultaneously.
What it Measures: Airborne particle concentration in the production environment, measured at defined monitoring points by particle size class.
What Happens if Missed: Particle excursions that are not caught in real time expose every wafer on the floor to potential contamination, with yield impact that only becomes visible at downstream inspection or test.
Formula: N/A
Indicator Type: Leading. Particle count in the environment directly predicts defect density risk on wafers before any in-process inspection occurs.
Unit of Measure: Particles per cubic meter (by size class)
Ideal Visualization(s): KPI trend with real-time alerts; Group Map showing particle count status by cleanroom zone
Frequency: Continuous real-time monitoring, updated per sensor sample interval
Data Required: Particle counts by size class, sensor location identifiers, cleanroom zone mapping, ISO class thresholds per zone
Pro Tip: Map particle sensor alerts to concurrent wafer lot locations on the floor. This lets you immediately identify which lots were at risk during an excursion.
Red Flag: A particle spike isolated to one zone with no corresponding increase in adjacent zones almost always points to a local equipment or process event, such as a robot fault or filter bypass.

Photolithography CD Uniformity (Within-Wafer)

Why it Matters: Critical dimension variation at the lithography step propagates directly into device performance and yield. CD control is the foundation of every node’s process window.
What it Measures: The standard deviation or range of patterned feature dimensions across the wafer surface at a given lithography step.
What Happens if Missed: CD excursions that exceed the process window cause parametric failures at electrical tests, often appearing as yield loss that is difficult to trace back to the original source step.
Formula: N/A
Indicator Type: Leading. CD uniformity at the patterning step predicts parametric yield and device performance before any downstream electrical test.
Unit of Measure: Nanometers (nm), expressed as 3σ
Ideal Visualization(s): SPC trend (control chart) with real-time alerts; KPI trend with real-time alerts by stepper tool and lot
Frequency: Per lot at lithography inspection; real-time overlay from inline metrology tools
Data Required: CD measurements by wafer location, lot identifier, stepper tool ID, reticle ID, process layer, target CD value
Pro Tip: Separate within-wafer uniformity from lot-to-lot variation. Systematic within-wafer patterns often point to illumination or focus issues on a specific tool.
Red Flag: CD drift that tracks a specific reticle across multiple tools rules out the stepper as the source and implicates the mask itself.

WIP (Work in Progress) Lot Velocity

Why it Matters: WIP balance drives cycle time efficiency. Lots stacking at a specific process layer signal a bottleneck or scheduling problem that will translate into missed delivery dates within days.
What it Measures: The average number of process steps completed per lot per day, compared against plan, across the active WIP population.
What Happens if Missed: WIP accumulation at bottleneck steps inflates cycle time silently until it is visible in delivery performance, at which point the recovery window is already narrow.
Formula: (Steps Completed per Lot) / (Elapsed Days in Fab) vs. Plan
Indicator Type: Current. Lot velocity reflects the real-time flow rate of active WIP and responds immediately to tool downtime and queue imbalances.
Unit of Measure: Steps per day (% of plan)
Ideal Visualization(s): KPI trend with real-time alerts; Group rollup bars by process area or layer group; Pareto chart when ranking layers by WIP accumulation
Frequency: Updated continuously as lots complete steps; hourly summary
Data Required: Step completion timestamps, lot identifiers, planned step sequence, current step for each active lot
Pro Tip: Track velocity by process area, not just total fab. A velocity problem in lithography looks completely different from one in etch or CMP, and the response is different too.
Red Flag: Velocity holding on track overall while WIP accumulates at one specific layer is the classic signature of a hidden bottleneck that aggregate metrics will not surface.

Etch Rate Uniformity

Why it Matters: Etch rate variation within a wafer or between chambers drives CD deviation, profile changes, and selectivity failures that directly affect device characteristics and yield.
What it Measures: The uniformity of material removal rate across the wafer surface during dry or wet etch processes, expressed as a percentage variation from the mean.
What Happens if Missed: Chamber drift that is not caught before production lots are processed creates systematic defects across every wafer run on that tool until the issue is identified and corrected.
Formula: (Max Etch Rate – Min Etch Rate) / (2 x Mean Etch Rate) x 100
Indicator Type: Leading. Etch uniformity measured on monitor wafers or via in-situ endpoints predicts process stability before product wafers are exposed to the same conditions.
Unit of Measure: Percent (%) non-uniformity
Ideal Visualization(s): SPC trend (control chart) with real-time alerts; Pareto chart when ranking etch chambers by non-uniformity contribution; KPI trend with real-time alerts by chamber ID
Frequency: Per lot or per chamber qualification run; real-time where endpoint detection is available
Data Required: Etch depth measurements by wafer location, mean etch rate, chamber identifier, process recipe, lot identifier, monitor wafer results
Pro Tip: Run chamber-matching analysis regularly across your etch tool set. Systematic differences between chambers cause within-lot yield variation that is easy to miss when you look at averages.
Red Flag: Etch rate non-uniformity trending upward on a single chamber while sister chambers hold control is the clearest signal of a chamber component issue such as a worn electrode or blocked gas inlet.

Overall Equipment Effectiveness (OEE) for Critical Tools

Why it Matters: OEE for bottleneck tools ties together availability, throughput rate, and quality in a single number. It is the most complete view of whether a tool is delivering its full production capacity.
What it Measures: The product of tool availability, performance (actual vs. rated throughput), and quality (lots processed without excursion) for a defined set of critical tools.
What Happens if Missed: OEE drift that is not tracked in real time allows compounding inefficiencies across availability, speed loss, and quality losses to accumulate before any single metric triggers a response.
Formula: Availability (%) x Performance (%) x Quality (%)
Indicator Type: Current. OEE integrates live tool state data and responds to changes in any of its three components in real time.
Unit of Measure: Percent (%)
Ideal Visualization(s): KPI blocks by critical tool; KPI trend with real-time alerts; Pareto chart when ranking tools by OEE loss contribution
Frequency: Real-time, updated per tool state change and lot completion
Data Required: Tool scheduled time, unplanned downtime, actual run rate, rated run rate, lots processed, lots with quality excursion, tool classification
Pro Tip: Decompose OEE losses into their three components when diagnosing performance problems. Most tools lose more to speed and quality losses than to downtime, but downtime gets all the attention.
Red Flag: OEE trending down on a tool where availability is stable almost always means performance or quality losses are accumulating, often from process drift or recipe creep that maintenance checks will not catch.

Why Real-Time Visibility Matters

Semiconductor fabs operate at process tolerances measured in nanometers, across hundreds of sequential steps, with cycle times stretching across weeks. In that environment, a process excursion at layer 10 does not announce itself at layer 10. It shows up at electrical tests, by which point the affected lots have traveled through dozens more steps and consumed capacity that cannot be returned. Real-time KPIs at every critical layer close that gap before it becomes a write-off event.

The same logic applies to equipment availability, WIP flow, and cleanroom integrity. Each of these operates on a time scale where a few hours of missed visibility translates directly into schedule impact that no expedite process can fully recover. The KPIs above are not reporting metrics; they are the operational controls that keep a fab running at plan instead of reacting to the last thing that went wrong.

How Transpara Can Help

10 Real-Time KPIs Every Mine Hauling Operations Leader Should Keep on Their Radar

Industry KPIs, News

A large excavator loads material into a haul truck at an open-cut mine site, where real-time monitoring of truck cycle times, payload weights, and equipment utilization drives measurable gains in production throughput.

Hauling is where mine plans either hold together or fall apart. Every ton moved late, every truck idling at a shovel, and every unplanned breakdown ripples back through the entire production schedule in ways that are expensive to recover from and easy to prevent with the right visibility. When hauling teams operate without real-time data, they manage by radio call and shift report.

By the time a dispatch supervisor knows a haul road is creating cycle time overruns or that payload variance is quietly eroding tonnes-per-hour targets, the shift is already lost. The next shift inherits the problem. These ten KPIs give hauling operations leaders the live signal layer they need to keep trucks moving, loads full, and the mine plan intact.

Truck Payload Utilization

Why it Matters: Payload underloading is one of the most common and least visible sources of production loss in open-pit hauling operations.
What it Measures: The ratio of actual payload per truck cycle to the truck's rated payload capacity, expressed as a percentage.
What Happens if Missed: Consistent underloading means more cycles are needed to move the same tonnes, burning fuel and hours without proportional output.
Formula: (Actual Payload / Rated Payload Capacity) × 100
Indicator Type: Current. It reflects loading performance in real time and drives immediate shovel operator coaching or dig plan adjustments.
Unit of Measure: Percentage (%)
Ideal Visualization(s): KPI trend with real-time alerts; bullet chart comparing actual versus target payload per truck or shovel; Pareto chart when ranking shovels by average payload variance
Frequency: Per truck cycle, updated in real time
Data Required: Onboard payload measurement per cycle, rated truck capacity, shovel ID, truck ID, cycle timestamp
Pro Tip: Track payload distribution by shovel, not just fleet average. A single shovel running 15% underloaded can mask strong performance elsewhere and skew your daily tonne target.
Red Flag: Payload that trends downward across a shift without a bench change usually means dig conditions have deteriorated or the shovel operator's pass technique has drifted.

Truck Cycle Time

Why it Matters: Cycle time is the clock that governs fleet productivity. Every minute added to the average cycle time reduces the number of cycles available per shift.
What it Measures: The total elapsed time for a single truck cycle from load point departure to return, including travel, queuing, dumping, and spotting time.
What Happens if Missed: Undetected cycle time creep compresses tonnes-per-hour output and forces unplanned fleet additions or overtime to recover shift targets.
Formula: Dump Arrival Time - Load Departure Time + Return Time + Spot Time
Indicator Type: Current. It updates per cycle and immediately reflects haul road conditions, queuing delays, or dispatch routing problems.
Unit of Measure: Minutes
Ideal Visualization(s): KPI trend with real-time alerts; Pareto chart when ranking haul routes or trucks by average cycle time deviation
Frequency: Per cycle, in real time
Data Required: GPS timestamps at load point, dump point, and key haul road waypoints; truck ID; route assignment
Pro Tip: Decompose cycle time into its sub-components. A cycle time increase driven by queuing at the dump is a dispatch problem. One driven by travel time is a haul road problem. They require completely different responses.
Red Flag: A fleet-wide cycle time increase that coincides with a shift change often points to a road watering or grading gap between shifts rather than a dispatch or equipment issue.

Queue Time at Shovel

Why it Matters: Trucks queuing at a shovel are producing nothing. Shovel queue time is one of the clearest signals of fleet and shovel imbalance in the hauling system.
What it Measures: The average time trucks spend waiting at a shovel before spotting and loading begins, per shift and per shovel.
What Happens if Missed: High queue times suppress fleet productivity, inflate fuel consumption, and mask shovel underperformance behind apparent truck availability numbers.
Formula: Spot Start Time - Arrival at Shovel Time (averaged per shovel per shift)
Indicator Type: Leading. Rising queue time predicts a tonnage shortfall before the shift target is missed.
Unit of Measure: Minutes
Ideal Visualization(s): KPI trend with real-time alerts; Pareto chart when ranking shovels by average queue time; KPI Map View showing queue time by shovel location
Frequency: Real-time, updated per truck arrival event
Data Required: Truck GPS arrival timestamp at shovel, spot start timestamp, shovel ID, truck ID
Pro Tip: Watch queue time in conjunction with shovel dig rate. A shovel running at full dig rate with high queue time means too many trucks are assigned. A shovel with low queue time and low dig rate means the opposite.
Red Flag: Queue time that spikes on a single shovel while others are idle points to a dispatch routing issue, not a fleet size problem.

Haul Road Speed Compliance

Why it Matters: Speed non-compliance on haul roads is the leading driver of tyre wear, suspension damage, and fatigue-related safety incidents in open-pit hauling operations.
What it Measures: The percentage of haul road segments where truck GPS-recorded speeds remain within posted speed limits for the road class and conditions.
What Happens if Missed: Excess speed accelerates tyre consumption, increases maintenance frequency, and raises the probability of a serious haul road incident that stops production entirely.
Formula: Compliant Haul Road Segments / Total Monitored Haul Road Segments × 100
Indicator Type: Current. Speed compliance reflects driver behavior and road condition interaction in real time, enabling same-shift intervention.
Unit of Measure: Percentage (%)
Ideal Visualization(s): KPI trend with real-time alerts; GeoMap showing speed exceedance events by road segment and truck
Frequency: Continuous, per GPS reporting interval
Data Required: GPS speed per truck per road segment, posted speed limit per segment, road classification, truck ID, driver ID
Pro Tip: Map speed exceedances by segment rather than by truck. A segment with repeated exceedances from multiple drivers signals a posted limit that does not match road geometry or conditions, not a driver behavior problem.
Red Flag: Speed exceedances concentrated on downhill segments during wet weather indicate that road conditions have changed and the speed limit has not been updated to match.

Fuel Consumption per Tonne Moved

Why it Matters: Fuel is one of the largest variable costs in open-pit hauling. Without real-time tracking, overconsumption hides inside monthly fuel reports that arrive too late to correct.
What it Measures: The volume of fuel consumed per tonne of material moved, tracked at the fleet and individual truck level.
What Happens if Missed: Inefficient trucks continue to operate at elevated fuel rates, driving cost overruns and potentially signaling engine or drivetrain issues that will worsen without intervention.
Formula: Total Fuel Consumed (L) / Total Tonnes Moved
Indicator Type: Current. It updates per cycle and reflects the combined effect of payload, road conditions, truck health, and operator technique in real time.
Unit of Measure: Litres per tonne (L/t)
Ideal Visualization(s): KPI trend with real-time alerts; Pareto chart when ranking trucks by fuel consumption per tonne; bullet chart comparing actual versus target L/t per shift
Frequency: Per cycle, aggregated per shift
Data Required: Fuel consumption per cycle from engine telemetry, payload per cycle, truck ID, route
Pro Tip: Separate loaded haul fuel rate from empty return fuel rate. An elevated empty return rate often signals an operator technique issue. An elevated loaded haul rate often signals a mechanical or road problem.
Red Flag: A single truck running 20% or more above fleet average fuel per tonne for more than one shift is almost always a maintenance signal, not an operator one.

Tyre Performance Index (TPI)

Why it Matches: Tyres are the most expensive consumable in a large haul truck fleet. Unplanned tyre failures stop trucks immediately and create safety hazards on active haul roads.
What it Measures: A composite real-time index of tyre temperature, pressure, and accumulated tonne-kilometres against expected tyre life for each tyre position and truck.
What Happens if Missed: Tyre failures occur without warning, causing unplanned truck downtime, haul road incidents, and replacement costs that exceed planned tyre budgets by significant margins.
Formula: Composite score derived from: Actual Tyre Temp / Limit, Actual Pressure / Target Pressure, Accumulated TKm / Rated TKm Life
Indicator Type: Leading. Tyre pressure and temperature trends predict failure risk before a blowout occurs.
Unit of Measure: Index score or percentage of rated life consumed
Ideal Visualization(s): KPI trend with real-time alerts for temperature and pressure per tyre position; bullet chart showing remaining tyre life versus replacement threshold
Frequency: Continuous, per TPMS reporting interval
Data Required: Real-time tyre pressure and temperature per position from TPMS, accumulated tonne-kilometres per tyre, tyre rated life, truck ID
Pro Tip: Alert on rate of temperature change, not just absolute temperature. A tyre that heats rapidly over 20 minutes is more urgent than one that has been running warm all shift.
Red Flag: Persistent high temperature on a single tyre position across multiple trucks on the same haul route points to a road geometry or road surface problem at a specific location.

Shovel-to-Truck Match Factor

Why it Matters: A fleet that is poorly matched to its shovels either over-queues trucks or leaves shovels idle. Both conditions destroy productivity without being immediately visible to dispatch.
What it Measures: The ratio of truck fleet capacity arriving at a shovel to the shovel's sustained loading capacity, calculated in real time per shovel and updated as trucks are dispatched.
What Happens if Missed: Over-trucked shovels create queue time that inflates cycle times across the fleet. Under-trucked shovels idle expensive dig equipment and miss tonnes targets.
Formula: (Number of Trucks × Average Payload) / (Shovel Dig Rate × Average Cycle Time)
Indicator Type: Leading. It predicts queue formation and production loss before they appear in cycle time or tonne data.
Unit of Measure: Ratio (target range typically 0.9 to 1.1)
Ideal Visualization(s): KPI trend with real-time alerts; KPI Map View showing match factor by active shovel; bullet chart comparing actual versus target match factor per shovel
Frequency: Real-time, updated per dispatch event
Data Required: Active truck count per shovel, average payload, shovel dig rate, average cycle time per route
Pro Tip: Match factor is only as useful as the cycle time estimate feeding it. Update cycle time inputs dynamically using GPS actuals, not static planning assumptions.
Red Flag: A match factor that looks balanced at shift start but drifts above 1.2 by mid-shift usually means a haul road event has extended cycle times without dispatch adjusting truck assignments.

Truck Availability

Why it Matters: Fleet availability is the ceiling on hauling productivity. No dispatch strategy recovers tonnes lost to trucks sitting in the workshop.
What it Measures: The percentage of the scheduled operating fleet that is mechanically available to work at any given time during the shift.
What Happens if Missed: Unplanned breakdowns erode shift targets and force reactive maintenance that is more expensive and less effective than planned interventions would have been.
Formula: (Scheduled Hours - Unplanned Downtime Hours) / Scheduled Hours × 100
Indicator Type: Current. It reflects the live state of the fleet and updates with every breakdown and return-to-service event.
Unit of Measure: Percentage (%)
Ideal Visualization(s): KPI trend with real-time alerts; bullet chart comparing actual versus target availability per shift; Pareto chart when ranking trucks by unplanned downtime contribution
Frequency: Real-time, updated per breakdown or return-to-service event
Data Required: Truck status per unit (running, queuing, under maintenance, waiting), breakdown start and end timestamps, scheduled operating hours
Pro Tip: Separate unplanned mechanical downtime from operator-delay downtime in your availability calculation. Mixing them produces a number that looks worse than it is and obscures where the actual losses sit.
Red Flag: Two or more trucks from the same model or vintage experiencing the same fault code within a short window points to a fleet-wide component failure mode that the workshop needs to investigate across all units.

Tonnes Per Operating Hour (TPOH)

Why it Matters: TPOH is the primary output measure of a hauling operation. It integrates the effects of payload, cycle time, availability, and fleet size into a single live productivity signal.
What it Measures: The total tonnes moved by the hauling fleet per hour of scheduled operating time, tracked in real time against the shift plan.
What Happens if Missed: TPOH shortfalls compound through the shift without triggering correction because no single KPI captures the combined effect of multiple small losses at once.
Formula: Total Tonnes Moved / Total Fleet Operating Hours
Indicator Type: Current. It updates continuously and reflects the cumulative impact of all hauling system variables in real time.
Unit of Measure: Tonnes per operating hour (t/oh)
Ideal Visualization(s): KPI trend with real-time alerts; bullet chart comparing actual versus target TPOH per shift; status history trend showing TPOH performance across the shift window
Frequency: Real-time, updated per completed cycle
Data Required: Payload per cycle, cycle completion timestamps, total fleet scheduled hours, truck count
Pro Tip: Track TPOH against the shift production plan on the same chart. A TPOH that looks acceptable in isolation can be well below the rate needed to recover an early-shift deficit.
Red Flag: TPOH that is on target for the first two hours of a shift and then declines consistently through the rest of the shift usually signals fatigue-related operator performance or road condition degradation that is not being addressed.

Haul Road Condition Index

Why it Matters: Haul road condition is one of the highest-impact variables in hauling operations and one of the least monitored in real time. A deteriorating road surface slows trucks, raises fuel consumption, and damages suspension and tyres simultaneously.
What it Measures: A composite index derived from road roughness, grade compliance, and active defect reports that reflects the operational quality of each haul road segment in real time.
What Happens if Missed: Road condition degrades gradually until the damage done to trucks is obvious. By then, the tyre, suspension, and fuel costs are already banked and the road requires significant rehabilitation to recover.
Formula: N/A
Indicator Type: Leading. Road condition trends predict tyre wear, fuel consumption, and cycle time overruns before they appear in those KPIs directly.
Unit of Measure: Index score (0 to 100, with 100 being optimal)
Ideal Visualization(s): GeoMap showing road condition index by segment with alert coloring; KPI trend with real-time alerts per key haul route; status history trend tracking condition changes versus grading and watering events
Frequency: Continuous for sensor-based inputs; event-based for defect reports
Data Required: Road roughness sensor data or onboard suspension load data from trucks, grade measurements per segment, active defect reports, grading and watering event timestamps
Pro Tip: Correlate road condition index events with grading and watering schedules. If condition degrades rapidly after a grading, the grading standard is the problem. If it degrades between waterings, the watering frequency needs adjustment.
Red Flag: A haul road segment that consistently returns to poor condition within hours of grading indicates a material or drainage problem that surface grading alone will not fix.

Why Real-Time Visibility Matters

Hauling operations generate enormous volumes of data every shift: GPS positions, payload measurements, engine telemetry, tyre pressure readings, and fuel consumption figures. The problem is rarely a shortage of data. It is the absence of a real-time layer that turns that data into signals operators and dispatchers can act on before the shift is lost. A cycle time overrun spotted in the first hour can be corrected by dispatch. The same overrun spotted in the shift report drives a conversation that changes nothing for the tonnes already missed.

The ten KPIs above span the full range of variables that determine hauling productivity: loading efficiency, road performance, fleet health, and system balance. Tracking them live, with alerts that reach the right person at the right time, is what separates a hauling operation that consistently hits its plan from one that is permanently in recovery mode. In a business where every tonne has a cost and a margin, the ability to see what is happening now and act before it compounds is not an advantage. It is the baseline for running a competitive operation.

How Transpara Can Help

10 Real-Time KPIs Every Pharmaceutical Manufacturing Operations Leader Should Be Tracking

Industry KPIs, News

In pharmaceutical manufacturing, precision has to show up on the line, not just in the batch record. Real-time visibility across sterile filling, inspection, and packaging helps teams protect quality, maintain compliance, and catch problems before they turn into waste or risk.

Pharmaceutical manufacturing is one of the few industries where a single data gap can turn a batch loss into a regulatory crisis. The margin between a validated run and a deviation report is often measured in minutes, not hours. When operations teams are flying blind, they find out something went wrong from a QA audit, not from their own systems.

Batch deviations, yield losses, and environmental excursions compound fast in this environment. A contamination event caught at final release costs far more than one caught at the bioreactor. Real-time visibility is not a convenience here. It is the difference between a successful campaign and a site shutdown.

These ten KPIs give pharmaceutical manufacturing operations leaders the live signal layer they need to stay ahead of deviations, protect yield, and keep production on schedule.

Batch Cycle Time

Why it Matters: Cycle time overruns compress scheduling across the entire suite and cascade into batch queue failures that are hard to recover from.
What it Measures: The elapsed time from batch initiation to final release, tracked live against the validated target.
What Happens if Missed: Delays compound across campaigns, equipment utilization drops, and API shortage risk rises without early warning.
Formula: Actual Batch End Time - Batch Start Time
Indicator Type: Current. It reflects where the batch stands relative to its target window in real time.
Unit of Measure: Hours
Ideal Visualization(s): KPI trend with real-time alerts; bullet chart showing actual versus target cycle time per batch
Frequency: Real-time
Data Required: Batch start timestamp, current timestamp, validated cycle time target, phase completion timestamps
Pro Tip: Break cycle time down by phase. Phase-level tracking tells you where overruns originate before they compound into a full batch delay.
Red Flag: Consistent overruns in the same phase across multiple batches signal a process drift or equipment issue that root cause analysis has not yet caught.

Batch Yield

Why it Matters: Yield directly determines the economics of every campaign. A 2% yield drop across a month-long production run is rarely caught until it shows up in the finance report.
What it Measures: The ratio of actual output to theoretical maximum output for a given batch, expressed as a percentage.
What Happens if Missed: Low yield batches ship late or get scrapped, driving material costs up and delivery commitments into jeopardy.
Formula: (Actual Output / Theoretical Output) × 100
Indicator Type: Lagging. It confirms batch performance after key process steps are complete, but real-time sub-step tracking can shift this toward current.
Unit of Measure: Percentage (%)
Ideal Visualization(s): KPI trend with real-time alerts; Pareto chart when ranking batches or production lines by yield deviation
Frequency: Per batch phase, updated in real time as steps complete
Data Required: Actual output mass or volume per step, theoretical yield per step, batch recipe parameters
Pro Tip: Track yield at each unit operation, not just at final release. Downstream losses always start upstream.
Red Flag: A yield that tracks normal through synthesis but drops sharply at purification points to a column efficiency or solvent issue worth investigating immediately.

Critical Process Parameter Deviation Rate

Why it Matters: CPP deviations are the leading cause of batch failures and regulatory findings. Every deviation that goes undetected in real time becomes a documentation burden after the fact.
What it Measures: The number of critical process parameters (temperature, pH, pressure, agitation) that have breached their validated operating ranges during a batch.
What Happens if Missed: Undetected CPP excursions invalidate batch data, trigger investigations, and in worst cases result in product recalls.
Formula: (Count of CPP excursions during batch / Total CPP monitoring points) × 100
Indicator Type: Leading. CPP deviations predict batch disposition outcomes before final QA review.
Unit of Measure: Percentage (%) or count
Ideal Visualization(s): KPI trend with real-time alerts; status history trend showing excursion events over the batch timeline
Frequency: Real-time, sub-minute for temperature and pressure parameters
Data Required: Real-time sensor values per CPP, validated operating range limits, batch phase timestamps
Pro Tip: Set alerts at 80% of the validated limit, not at the limit itself. Early warning gives operators room to correct before a formal deviation is triggered.
Red Flag: Multiple CPP excursions within a single phase on the same equipment across different batches indicates a calibration drift or equipment control issue.

Equipment Utilization Rate

Why it Matters: Underutilized equipment in a constrained pharmaceutical suite means schedule slippage, missed campaign targets, and idle capacity that erodes return on asset investment.
What it Measures: The percentage of planned production time during which equipment is actively running a validated process step.
What Happens if Missed: Bottlenecks go unidentified, maintenance windows get scheduled reactively, and campaign plans are built on utilization assumptions that are no longer accurate.
Formula: (Actual Run Time / Planned Production Time) × 100
Indicator Type: Current. It reflects how effectively equipment is being used right now against the production schedule.
Unit of Measure: Percentage (%)
Ideal Visualization(s): Bullet chart comparing actual versus target utilization per equipment unit; Pareto chart when ranking equipment by underutilization
Frequency: Real-time, updated per shift
Data Required: Equipment state (running, idle, CIP, maintenance), planned production schedule, shift start and end times
Pro Tip: Separate planned downtime (CIP, changeover) from unplanned idle time in your utilization calculation. The two have very different corrective actions.
Red Flag: Utilization that is consistently high but yield is dropping suggests the equipment is running but not performing, which is a process or maintenance signal, not a scheduling one.

CIP / SIP Compliance

Why it Matters: Clean-in-place (CIP) and sterilize-in-place (SIP) cycles sit on the critical path of every batch campaign. Overruns or failures directly delay the next batch start.
What it Measures: The elapsed time and pass/fail status of each CIP or SIP cycle against the validated procedure specification.
What Happens if Missed: A failed or incomplete cleaning cycle forces manual investigation, extends downtime, and can invalidate the next batch if the risk is not assessed before startup.
Formula: Actual CIP/SIP Duration vs. Validated Duration; Pass rate = Successful cycles / Total cycles × 100
Indicator Type: Current. CIP and SIP cycles run between batches and their real-time status drives equipment readiness decisions.
Unit of Measure: Minutes (cycle time); percentage (pass rate)
Ideal Visualization(s): KPI trend with real-time alerts for cycle time; status history trend for pass/fail tracking per piece of equipment
Frequency: Real-time during cycle execution
Data Required: CIP/SIP start and end timestamps, temperature and conductivity readings during cycle, validated acceptance criteria
Red Flag: Increasing CIP cycle times on the same equipment across consecutive runs indicate fouling or spray ball degradation that maintenance should inspect before the next scheduled intervention.

Environmental Monitoring Excursion Rate

Why it Matters: Microbial and particulate excursions in classified areas are regulatory red flags that can halt production and trigger Form 483 observations during inspections.
What it Measures: The rate of environmental monitoring results that fall outside classified area specifications for particulates, temperature, humidity, or differential pressure.
What Happens if Missed: Contamination events go undetected until final product testing, by which point a full batch investigation is required and recall risk rises sharply.
Formula: Excursion Results / Total Monitoring Points × 100
Indicator Type: Leading. Environmental trends predict contamination risk before product quality is affected.
Unit of Measure: Percentage (%)
Ideal Visualization(s): KPI trend with real-time alerts; GeoMap showing excursion locations across classified zones
Frequency: Continuous for physical parameters (differential pressure, temperature); per-sample for microbial results
Data Required: Real-time sensor readings per classified zone, historical baseline values, regulatory specification limits, sample results
Pro Tip: Trend differential pressure between zones continuously. A pressure drop is often the first signal of a HVAC issue long before a microbial result flags it.
Red Flag: Clustered excursions in the same zone during the same shift point to a personnel or procedural cause rather than an equipment failure.

On-Time Batch Release Rate

Why it Matters: Late batch release backs up the entire supply chain, delays customer shipments, and forces expedited logistics that destroy margin.
What it Measures: The percentage of batches released to warehouse or distribution within the validated release window following final QC sign-off.
What Happens if Missed: Supply commitments slip, customers escalate, and the operations team absorbs the consequences of QC and production problems they may not have caused.
Formula: Batches Released On Time / Total Batches Released × 100
Indicator Type: Lagging. It confirms release performance after the fact, but tracking it in real time against the schedule drives proactive escalation before the window closes.
Unit of Measure: Percentage (%)
Ideal Visualization(s): KPI trend with real-time alerts; bullet chart comparing actual release rate against target by campaign
Frequency: Per batch, updated at each QC milestone
Data Required: Batch release timestamps, scheduled release windows per batch, QC step completion times
Pro Tip: Track the time from final QC submission to release sign-off separately. That sub-step often reveals where release bottlenecks actually sit.

Overall Equipment Effectiveness (OEE)

Why it Matters: OEE gives operations leaders a single number that reflects availability, performance, and quality losses together. Tracking any one of these in isolation misses the interaction between them.
What it Measures: The product of equipment availability, production rate performance, and quality yield, expressed as a single percentage.
What Happens if Missed: Losses accumulate across all three dimensions without being attributed correctly, making improvement efforts unfocused and ineffective.
Formula: Availability × Performance × Quality
Indicator Type: Current. OEE reflects live operational performance when calculated continuously rather than at shift end.
Unit of Measure: Percentage (%)
Ideal Visualization(s): KPI trend with real-time alerts; bullet chart per production line; Pareto chart when ranking lines or equipment by OEE loss contribution
Frequency: Real-time, updated per shift and per batch phase
Data Required: Planned production time, actual run time, ideal production rate, actual production rate, good units produced, total units started
Pro Tip: Decompose OEE losses by type before any improvement project. Availability losses and performance losses have completely different root causes and corrective actions.
Red Flag: High availability with low performance suggests the equipment is running but the process is throttled. That is often a material, recipe, or operator issue rather than a maintenance issue.

Deviation and CAPA Closure Rate

Why it Matters: Open deviations and CAPAs are a regulatory liability. Inspectors treat aged open items as evidence of systemic quality management failures.
What it Measures: The percentage of open deviations and corrective and preventive actions closed within their target timeframe.
What Happens if Missed: Deviation backlogs grow, repeat events go uncorrected, and audit findings escalate from observations to warning letters.
Formula: CAPAs or Deviations Closed On Time / Total Open CAPAs or Deviations × 100
Indicator Type: Lagging. It measures the effectiveness of quality systems after events have occurred, but real-time tracking against aging thresholds drives timely closure.
Unit of Measure: Percentage (%)
Ideal Visualization(s): KPI trend with real-time alerts; table showing open items ranked by age and owner
Frequency: Daily refresh, with real-time escalation alerts for items approaching or exceeding target closure dates
Data Required: Deviation open date, target closure date, actual closure date, CAPA owner, event classification
Pro Tip: Separate minor deviations from major deviations in your tracking. Major deviations have regulatory timelines attached and need their own escalation path.
Red Flag: Repeat deviations of the same type within 90 days indicate a CAPA that was closed but not actually effective.

Utility System Performance (WFI, Clean Steam, HVAC)

Why it Matters: Water for injection, clean steam, and HVAC systems are invisible dependencies that stop production cold when they fail. They rarely appear on a production dashboard until a batch is already at risk.
What it Measures: Real-time operational status and specification compliance for critical utility systems supplying manufacturing suites.
What Happens if Missed: An out-of-specification WFI loop or a HVAC failure discovered mid-batch forces an immediate deviation investigation and potential batch hold.
Formula: Specification Excursions per Utility System / Total Monitoring Points × 100; individual trend tracking per utility parameter
Indicator Type: Leading. Utility system drift predicts batch and environmental risk before product quality is affected.
Unit of Measure: Varies by parameter (TOC ppb for WFI, CFU/mL for microbial, Pa for differential pressure, °C for temperature)
Ideal Visualization(s): KPI trend with real-time alerts per utility system; Group Map showing utility status across manufacturing suites; SPC trend (control chart) for conductivity and TOC
Frequency: Continuous for physical parameters; per-sample for microbial and chemical quality parameters
Data Required: Real-time sensor readings per utility loop, validated specification limits, flow rates, pressure readings, TOC and conductivity values
Pro Tip: Plot utility KPIs on the same time axis as batch events. Correlating a batch yield drop with a WFI conductivity excursion two hours earlier is the kind of root cause analysis that only works when both data streams are visible together.
Red Flag: Gradual TOC creep over multiple days in a WFI loop indicates biofilm formation. Waiting for a specification breach to act is already too late.

Why Real-Time Visibility Matters

Pharmaceutical manufacturing operates inside a validated envelope where every deviation has a documentation cost, a regulatory implication, and a downstream production consequence. When operations teams rely on shift reports and end-of-batch summaries, they are always looking backward. Deviations that could have been corrected in the first 15 minutes of a batch instead become full investigations that consume days of engineering and QA time.

The ten KPIs above cover the operational, quality, and utility dimensions that determine whether a campaign succeeds or stalls. Tracking them in real time, with alerts that reach the right person before an excursion becomes a deviation, is the difference between proactive operations and reactive firefighting. In an industry where a single recalled batch can cost millions and a warning letter can close a facility, real-time visibility is not an improvement initiative. It is a baseline requirement.

How Transpara Can Help

« Older Entries

Next Entries »