CASE68 · Manufacturing · Steam-meter data quality
Validating steam measurement before ranking boiler efficiency or claiming savings
Abnormal steam-flow values compromise the denominator of gas-per-steam intensity. The case prioritizes calibration and physical consistency before quantitative savings evaluation.
01 · CASE ANALYSIS
The denominator can reverse the ranking
Specific fuel use is gas in Nm³ divided by steam production in tonnes. Under-reported steam makes intensity look worse; over-reported steam can create false apparent efficiency.
A sensor being installed does not establish that its stored data are valid for analysis.
02 · CASE ANALYSIS
Source finding and calculation hold
Normally metered boilers were reported around 43.9–49.6 Nm³/tonne. Some steam-flow measurements were abnormal, and the source required calibration before calculating quantitative savings.
The intensity range is not a saving rate, and abnormal units are not used to manufacture a benefit.
| Principle | Key application question |
|---|---|
| DP / orifice | Installation, differential pressure and steam compensation |
| Vortex | Suitable flow range and conversion to mass flow |
| Coriolis | Steam suitability, line size, pressure loss and cost |
03 · CASE ANALYSIS
Validate the complete measurement chain
Check signal ranges, zero/span, communications, units, timestamps and compensation logic against raw instruments and calibration records.
Compare fuel, firing/load and steam patterns; use system mass/energy consistency to flag implausible values. A calculated soft-sensor estimate is a diagnostic aid, not automatically a replacement certified measurement.
04 · CASE ANALYSIS
Meter principles and steam state
DP/orifice and vortex systems infer flow through their principles and may require pressure/temperature/density compensation. Coriolis directly measures mass but feasibility still depends on the steam application.
Choose by range, pressure loss, installation, process state and required M&V confidence. This edition does not supply detailed standard compliance rules or a universal best meter.
| Pattern | Candidate cause | Action |
|---|---|---|
| Persistent fixed value | Frozen sensor/communications | Check signal and gateway |
| Short spikes | Noise/communication problem | Compare raw signals |
| Long-term bias | Calibration/range/compensation | Check reference and calibrate |
| High startup intensity | May be a real operating loss | Tag startup state |
| Steam unrelated to fuel/load | Meter or compensation problem | Physical consistency review |
05 · CASE ANALYSIS
Data-quality gate before performance claims
Tag missing, frozen, spiking and biased intervals; distinguish actual startup losses from sensor faults. Preserve raw values and document exclusions and corrections.
Resume quantitative performance evaluation only after the measurement basis and applicable uncertainty are supported.
APPLY TO YOUR SITE
Connect your operating data to an actionable energy strategy.
Discuss the measurement boundary, data quality, operating constraints and verification approach for your facility.
Discuss your project All English cases