Contents
What are production parameters?
Production parameters are the measurable control variables that determine how a manufacturing process behaves — temperatures, pressures, speeds, feed rates, dwell times, torques, concentrations, force curves, positioning tolerances. The textbook treats them as a list to be optimized. The interesting question is not what the list contains. The interesting question is whether the plant actually knows what values those parameters had during the last shift, or whether it only knows what values the recipe said they should have.
That distinction — between the setpoint (what you commanded) and the actual value (what the process did) — is where almost all the useful information in a production line hides. Plants that manage only setpoints are managing a document, not a process. Plants that capture actual values and correlate them to quality outcomes are managing the process itself. The gap between those two modes is not philosophical; it is measurable, it is large, and it is a major source of parameter-related scrap, micro-stops and quality drift. This article is about how that gap arises, how to close it, and what changes when you do.
The three-tier parameter model that actually works on the shop floor
In theory, a production parameter is a single number with a setpoint and a tolerance. In practice, every useful parameter exists in three tiers, and confusing the tiers is where most parameter strategies break down. The tiers are not academic distinctions; they correspond to three different data sources, three different capture mechanisms, and three different management actions.
Most plants have tier 1 under control. They have recipes, they have SOPs, they have parameter sheets on the machines. Tier 1 is easy because it is a document problem — the plant decides what the parameter should be and writes it down. Tier 2 is where the work is: getting the actual value out of a machine that was not necessarily designed to share it, sampling it at the right frequency, time-stamping it correctly, tying it to the production order that was running at that moment. Tier 3 is where the value is — the derived signal that says "the melt temperature has drifted 8 °C over the last three weeks even though the setpoint has not changed, and the scrap rate for product A has climbed in lockstep." That is the conversation a process engineer can act on. You cannot have that conversation if you only have tier 1.
Why most parameter strategies fail
The failure mode is almost always the same, and it is almost always at tier 2. The recipe is correct. The intention is correct. The operators are doing their job. But the actual values from the process are either not captured, or captured too coarsely, or not tied to anything meaningful. Three specific patterns show up repeatedly.
Pattern 1: Setpoints treated as actuals. The report says "melt temperature: 230 °C" because that is what the recipe specified. Nobody has looked at the actual zone temperatures on the last 500 shots. The assumption is that the machine did what it was told. Machines do not always do what they are told — valves stick, heaters age, thermocouples drift, insulation degrades. A plant that manages parameters from the recipe and not from the measurement is flying blind with a correct flight plan.
Pattern 2: Brownfield capture gaps. Maybe 20–40 % of the machines in a typical mittelständisch plant are from before 2005. They have PLCs, but not OPC UA. They have sensors, but no exposed data interface. The plant's "parameter strategy" covers the modern CNC centres and the new injection-moulding presses, and stops at the edge of the brownfield area. Everything older than a decade remains a black box, and that black box typically contains the plant's highest-variance processes. Plants often say "those machines cannot deliver data" — yet an I/O gateway can usually expose useful parameters quickly without touching the PLC. The machines can almost always deliver data. The industry has just built a habit of assuming they cannot.
Pattern 3: Parameters captured, never correlated. The actual values flow into a historian. The historian grows. Nobody ever asks the question that matters: "When this parameter deviated from its setpoint on Tuesday at 14:32, what happened to the parts we produced for the next 30 minutes?" Without the correlation to quality outcomes — rejects, rework, customer complaints — the parameter history is just telemetry. Telemetry without correlation is expensive noise; plants can spend large budgets collecting it before realising nobody is reading it.
In practice: a valuable moment in a parameter project is the first time the process engineer sees the actual tier-2 values on a dashboard next to the tier-1 setpoints for the same shift. It often shows deviations nobody expected, such as a zone running hotter than the recipe, a pressure peak that has drifted, or a cycle that is slower on nights than on mornings. Such deviations can explain scrap patterns and micro-stops that nobody had been able to root-cause. They only become visible the moment setpoints and actuals sit side by side.
How parameters actually get captured — the brownfield reality
The usual expected answer to how parameters are captured is "OPC UA." OPC UA is the right answer for only part of the typical industrial machine park. For the rest, the honest answer is "it depends on what the machine already has, and we will work from there." A modern machine-integration strategy is not one protocol. It is a tiered approach that covers every machine in the plant, not just the convenient ones.
The practical point is that every machine can deliver parameters, but the mechanism varies. A good integration strategy covers all four tiers on day one. A bad strategy covers only the first one, declares the rest "not feasible," and leaves the plant blind on its most troublesome processes. The cost difference between the four mechanisms is smaller than most people think; the coverage difference is enormous. In a recent project the retrofit of a 1998 press with a digital I/O gateway took six hours and required no PLC programming. That machine is now delivering twelve parameters per cycle to the MES. Six hours.
Parameter drift — the silent killer of SPC
The parameter topic most underestimated in textbooks is drift. A parameter rarely fails suddenly. It drifts — slowly, gradually, often silently — as sensors age, valves wear, thermal masses change, and the process equipment ages around it. Statistical process control works only if your measurement baseline is stable. If the baseline itself is drifting, every control chart you draw is wrong in a direction you cannot see.
A rising scrap rate does not always mean the process changed. A thermocouple that drifts cold, for example, makes the controller heat the zone too hot to reach the incorrectly reported setpoint; product quality degrades in step with the drift while the control charts stay green, because they are built on the drifting measurement itself. Comparing the sensor against a reference, or against similar sensors on the same line, reveals it. Multi-sensor comparison and long-term baseline tracking are the reliable defences against drift, and they only exist where tier 2 and tier 3 are instrumented properly.
SYMESTIC cites a 5–15 % reduction in scrap as the expected range when tier-2 capture and tier-3 correlation are done correctly. The reduction is not caused by the parameters themselves being better; it is caused by the parameters being seen for the first time, which is the precondition for everything else that follows.
FAQ
What are production parameters in manufacturing?
Production parameters are the measurable control variables that determine how a process behaves — temperatures, pressures, speeds, feed rates, dwell times, torques, forces, concentrations. They exist in three tiers: the setpoint (what you commanded), the actual value (what the process did) and the deviation over time (the actionable signal derived from the first two). Managing parameters from setpoints alone is managing a document. Managing them from actuals tied to deviations is managing the process.
What is the difference between a setpoint and an actual value?
The setpoint is the commanded or specified value — typically stored in the recipe, the production order or the ERP. It reflects what the process is supposed to do. The actual value is what the process in fact did, sampled from a PLC, sensor or gateway in real time. Setpoints and actuals diverge routinely: valves stick, sensors drift, heaters age, material properties vary. The gap between the two is where almost all useful parameter-related information lives, and it is the gap most plants do not systematically measure.
How do you capture parameters from older machines without PLC intervention?
The right answer depends on what the machine already exposes. Machines with modern controls deliver parameters via OPC UA. Machines with older PLCs on Ethernet deliver parameters via protocol-specific adapters without code changes. Machines with pre-2005 PLCs or no Ethernet at all deliver parameters through I/O gateways wired directly to the sensor layer or to relay outputs — no PLC program changes required, no production interruption. In a recent retrofit on a 1998 press, a digital I/O gateway installed in six hours surfaced twelve parameters per cycle without any programming work.
Why does parameter drift matter more than parameter deviation?
Because drift is silent and deviation is loud. A sudden parameter deviation triggers alarms, operator attention and usually a fix within a shift. A slow drift — a sensor aging 0.3 °C per month, a valve gradually sticking, a thermal mass changing as insulation degrades — hides behind a green control chart for years. The scrap rate climbs in lockstep with the drift, but because the measurement baseline itself is moving, conventional SPC cannot see it. Multi-sensor comparison and long-term baseline tracking are the only reliable defences, and they require tier-2 capture with enough history to see the slow curve.
Is OPC UA enough for production-parameter capture?
It is enough for modern machines and it should be the default for anything installed post-2015. It is not enough as a complete strategy, because the typical mittelständisch plant has 20–40 % of its machines pre-dating OPC UA availability, and those machines are often the ones with the highest process variance. A parameter strategy that covers only OPC UA leaves the most troublesome processes uninstrumented. The realistic stack is OPC UA for new machines, protocol adapters for legacy Ethernet PLCs, and I/O gateways for genuine brownfield — applied together, not in sequence.
What is the relationship between production parameters and SPC?
SPC is a statistical method for detecting when a parameter has moved out of its expected distribution. It requires three things: an accurate actual value, a stable measurement baseline, and a sufficient sample size. Plants that run SPC on setpoints — or on actuals with a drifting baseline — get charts that stay green while the process quietly degrades. SPC is only as good as the tier-2 capture underneath it. Done properly, SPC and parameter capture together give you early detection of genuine process changes; done improperly, they give you a false sense of control. SPC on untrustworthy data can be worse than no SPC at all.
How do production parameters connect to quality outcomes?
Through correlation. Parameters captured but never correlated to scrap, rework or customer complaints are just telemetry — expensive telemetry that nobody reads. The correlation has to be made at the level of the individual order, cycle or batch, because batch-average correlation loses the transient deviations that cause most of the problems. In a well-instrumented line, every quality event — a rejected part at end-of-line inspection — is automatically mapped back to the parameter state that produced it. That mapping turns a parameter history into a diagnostic tool instead of a storage cost. Plants that miss this step collect parameters for years without ever extracting the value.
What does SYMESTIC do for production-parameter capture?
Multi-tier capture across the whole machine park: OPC UA for modern controls, protocol adapters for legacy Ethernet PLCs, digital I/O gateways for brownfield machines without any native digital interface — all feeding into one unified data model. Every parameter is tied to the active production order automatically, so tier-1 setpoints (from ERP/MES) and tier-2 actuals (from the machines) sit in the same record. Deviations are computed continuously and surfaced on dashboards designed for shift use, not retrospective reporting. Parameter histories correlate with alarm events and quality outcomes, so a quality defect can be traced back to the parameter state that produced it. 15,000+ connected machines on this architecture. See SYMESTIC Process Data.
Related: Manufacturing Processes · Process Standardization · Performance Measurement · Machine Data Acquisition · OPC UA · Six Sigma · MES · SYMESTIC Process Data
Scrap isn't made at inspection. It's made minutes earlier at the machine.
Intervene while the part is still good
SYMESTIC continuously checks process values such as temperature and pressure against your limits and alerts you on deviation.