Virtual sensing¶
Inferring a sensor-like reading of a target quantity from other measured signals through an inferential model when direct measurement is unavailable or impractical for the intended task.
Core Idea¶
Virtual sensing infers a sensor-like reading of a target quantity from other physical measurements through a model. The target is unavailable or impractical to measure directly for the intended task. A model maps auxiliary signals to an estimate that can stand in for a direct reading, subject to evidence that the mapping works on representative data. The method can be developed and tested without yet being deployed in monitoring or control.[1][2]
The defining substitution is informational: measured inputs and an inference rule produce a value for a different quantity. The model may be built from physical relationships or data. Its identity does not depend on a neural network, a particular update rate, or periodic recalibration against a physical target sensor. Those are design choices and validation practices, not universal conditions.[1]
Structural Signature¶
- Target quantity. This is the value the designer wants to read, such as free lime in a kiln product or vehicle side-slip angle. Without an identified target, the computation is general prediction rather than virtual sensing.
- Available measured inputs. Physical sensors supply other signals related to the target. Without measured inputs, the result is simulation or calculation without the sensing relation.
- Inferential model. A rule links the measured inputs to the target estimate. The rule can vary by application; without it, the auxiliary readings do not become a reading of the target.
- Validation against representative data. Comparison with observed target values, when available, tests whether the inferred reading is credible for the intended task. A successful test in one dataset does not guarantee all future conditions.
- Sensor-like output. The model makes the inferred target value available for a sensing task. Actual consumption by an operating controller is possible but not required for a studied virtual-sensor design.[1][2]
What It Is Not¶
Virtual sensing is not a second name for the physical input sensor. A yaw-rate measurement is an input; inferred side-slip angle is the target reading. It is also not any computer model that predicts a quantity. The model needs current or case-relevant measured signals and an intended substitute reading for a target that is not directly available in the task.[2]
Nor does this entry exclude Kalman-based estimation: the process-control literature describes Kalman-filter soft sensors, and the vehicle study compares a Kalman method with a neural-network method.[1][2]
Scope of Application¶
In industrial process control, a soft sensor can estimate a product-quality or emission variable from process measurements when laboratory analysis is slower or continuous direct measurement is difficult. Bao Lin and colleagues studied free-lime and nitrogen-oxide estimates for a cement kiln. Their free-lime assays arrived about every two hours while process signals were recorded every ten minutes; the study used process data to build and validate models. Those intervals describe that case, not a defining sampling schedule for all virtual sensors.[1]
In vehicle dynamics, Fen Lin and Youqun Zhao compared methods for estimating side-slip angle from measured yaw rate and lateral acceleration, evaluating estimates against measured side-slip angle. The author abstract presents potential guidance for stability-control design, not proof of an installed operational controller or a quantitative accuracy claim accessible from that abstract.[2]
Clarity¶
The abstraction distinguishes what is directly observed from what is inferred. A report that says a system “measures free lime” can hide the difference between an intermittent laboratory assay and a model's more frequent inferred value. The distinction determines which signal can validate the other, and which failures can arise from input-sensor error, model mismatch, or target-reference error.[1]
It also separates the method from its use. Comparing side-slip estimators against a measured reference demonstrates a virtual-sensor design; it does not by itself demonstrate control deployment. The same role map can describe a tested prototype and an operating system while keeping their evidence levels separate.[2]
Manages Complexity¶
A soft-sensor implementation may involve many process channels, cleaning decisions, model coefficients, and evaluation metrics. For initial classification, the useful compression is five questions: What target is wanted? Which physical signals are available? How are they mapped to the target? What comparison supports reliability? What sensor-like value is produced? Those questions preserve the inferential chain without treating the cement-kiln algorithm as the definition.[1]
The compression does not replace model assessment. The cement-kiln authors discuss outlier treatment and the danger of deleting process dynamics along with bad observations. The role map points to that issue as a validation question, not as a guarantee that any fitted model generalizes.[1]
Abstract Reasoning¶
When a claimed virtual sensor is evaluated, first identify the target and ask why its direct reading is unavailable or inconvenient for the proposed task. Trace each measured input into the model, and check that the output estimates the target rather than merely transforming or displaying the inputs. Then ask what target observations were used to test it and whether the tested conditions resemble the intended use.[1]
This sequence supports a conditional inference: if the model has been evaluated on relevant data, its output may be used as an inferred reading within that evidential scope. If inputs drift, the target relation changes, or reference comparisons are absent, that inference weakens. The abstraction directs the investigator to the broken link rather than declaring every soft sensor accurate or inaccurate.[1]
Knowledge Transfer¶
The role map transfers literally between industrial and vehicle engineering: both examples have physical auxiliary signals, a distinct target, an inferential mapping, a comparison against target measurements, and a sensor-like output. Their algorithms, update rates, and deployment evidence differ.[1][2]
Broader estimation methods can operate without a sensor-substitution task. A financial estimate or a forecast may share the evidence-to-unknown skeleton, but it is not automatically virtual sensing. The specialist identity remains tied to physical measured inputs and a target reading intended to function like a sensor output.
Examples¶
Canonical: free-lime estimation in a cement kiln¶
Bao Lin and colleagues built soft-sensor models for cement-kiln quality and emission targets, including free lime, using recorded process measurements. Laboratory free-lime analysis was less frequent than process recording. Their modeling and validation compared inferred values with observed target values; the study also treated data quality as consequential for performance.[1]
Mapped back: free lime is the target quantity; kiln process readings are available measured inputs; the authors' multivariate inferential method is the model; laboratory values and held-out comparison provide validation; the more frequent inferred free-lime value is the sensor-like output. This case does not make its algorithm or schedule mandatory elsewhere.
Applied: vehicle side-slip-angle estimation¶
Fen Lin and Youqun Zhao compared two soft-sensing methods for side-slip angle using yaw rate and lateral acceleration, then compared their estimates with measured side-slip angle. Their stated possible use was guidance for vehicle stability-control design. Only the original author abstract has been used here, so this example carries no unsupported numerical performance or deployment claim.[2]
Mapped back: side-slip angle is the target quantity; yaw rate and lateral acceleration are available measured inputs; the compared methods are inferential models; comparison with measured side-slip angle is validation; each method's inferred angle is the sensor-like output. Operational controller consumption is not claimed.
Structural Tensions¶
T1: Reject anomalous training data vs preserve real process behavior. In the cement-kiln study, filtering apparent outliers can protect the fit from bad observations, but aggressive filtering can also remove genuine process changes. Leaning toward retention admits more noise; leaning toward rejection can erase the behavior the sensor needs to track. This is a documented modeling tension in that case, not a requirement that every virtual sensor use the same cleaning rule. Diagnostic: Does an anomalous record reflect a measurement fault or a real operating change that the model must represent?[1]
Structural–Framed Character¶
This entry is mixed, leaning structural. The target-input-model-output relation is repeatable across different engineering systems. Evaluation still depends on a human task: what target is worth sensing, how much error is tolerable, and which conditions count as representative. Its use in control is a design purpose, not a constitutive condition; an undeployed study can still examine the same relation. The term comes from engineering practice rather than an institution granting formal membership.[1][2]
The vocabulary travels literally between a kiln and a vehicle because the roles can be identified in both. Importing it to an ordinary estimate with no physical sensing inputs would be analogy. A broader inference-from-observations skeleton is a future-prime or parent-definition question, not an approved parent in the current catalog; the named method retains sensor substitution as its differentia. Its character: an inferential engineering method whose evaluation is task-dependent but whose core roles can be tested without assuming a particular deployment.
Structural Core vs. Domain Accent¶
The broader skeleton is estimation: evidence and a model yield an approximate value for a target not known directly. The live Prime Estimation is a related, stronger construct but not a necessary genus: its current identity requires declared uncertainty and decision adequacy that every virtual-sensor design need not provide. The domain accent is using other physical sensor readings to supply a sensor-like target value under an intended measurement or control task. Statistical estimators, forecasts, and general approximations can satisfy the broader skeleton without this substitution.[1]
This named entry does not clear the Prime bar as a domain-neutral concept. Its diagnostic requires physical inputs and a target reading; remove those and the term becomes loose metaphor for model-based inference. The current catalog therefore leaves this entry a provisional unparented root after a typed comparison, subject to later review if the parent catalog changes.
Instantiates / Related Primes¶
Estimation shares the inference-from-evidence skeleton, but the live Prime demands explicit uncertainty and decision adequacy that this named method need not declare, so no strict parent edge is asserted. The live domain-specific Estimator names a statistical rule, not the whole sensor-substitution system. Measurement requires direct instrument–target coupling; Virtualization requires its own multiplexing or isolation relation; Proxy–Target Fidelity evaluates a stand-in relation rather than constructing this inferred reading. This entry is a provisional unparented root in the current catalog.
Neighborhood in Abstraction Space¶
Virtual sensing sits in a sparse region of the domain-specific corpus (98th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.
Family — Unclustered & Miscellaneous (2551 abstractions)
Nearest neighbors
- Floor Effect — 0.77
- Uncertainty analysis — 0.76
- Least-Squares Adjustment — 0.75
- Iterative reconstruction — 0.75
- Probability Bounds Analysis — 0.75
Computed from structural-signature embeddings · 2026-10-08
Not to Be Confused With¶
- Direct measurement: a physical instrument reads the target itself; a virtual sensor infers that target from other readings.
- A statistical estimator in general: the rule may estimate an unknown without providing a sensor-like output from physical auxiliary signals.
- An installed control sensor: validation of an inferential design does not prove that its output has been deployed in control.[2]
References¶
[1] Bao Lin, Bodil Recke, Jørgen K. H. Knudsen, and Sten Bay Jørgensen, “A systematic approach for soft sensor development,” Computers & Chemical Engineering 31 (2007), 419–425, DOI 10.1016/j.compchemeng.2006.05.030; especially abstract, introduction, §§4.1–4.2, and outlier discussion on p. 424. https://skoge.folk.ntnu.no/prost/proceedings/npc07/DTU/dtu09.pdf registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j ↩k ↩l ↩m ↩n ↩o
[2] Fen Lin and Youqun Zhao, “A Comparison of Two Soft-Sensing Methods for Estimating Vehicle Side Slip Angle,” SAE Technical Paper 2007-01-3587 (2007), original author abstract reviewed; full paper and numerical results not reviewed. https://saemobilus.sae.org/papers/a-comparison-two-soft-sensing-methods-estimating-vehicle-side-slip-angle-2007-01-3587 registry ↩a ↩b ↩c ↩d ↩e ↩f ↩g ↩h ↩i ↩j