Threshold

In industrial and manufacturing contexts, a threshold is a predefined limit or boundary value used to trigger an action, alert, classification, or decision. Thresholds are applied to measurements, counts, times, or calculated indicators to determine when a condition is acceptable, marginal, or unacceptable.

Thresholds are commonly used in:

• Quality control: upper and lower limits for dimensions, weight, or process parameters to decide if a unit is within specification.
• Process monitoring: alarm setpoints on temperature, pressure, speed, or vibration to trigger operator intervention or automatic control actions.
• Performance metrics: target or minimum values for OEE, yield, scrap rate, or throughput that indicate when performance requires escalation.
• Compliance and safety: limits related to exposure, emissions, or critical equipment states that drive procedural or shutdown actions.
• IT/OT systems: thresholds in MES, historians, and monitoring tools to raise alerts, generate events, or start workflows.

Operational characteristics

Thresholds are usually defined numerically, such as a value, range, or percentage. They may be configured as:

• Single-sided: only a maximum or only a minimum, such as a high-temperature alarm.
• Double-sided: both upper and lower limits, such as a control band for a critical process parameter.
• Static: fixed values defined in procedures, specifications, or system configuration.
• Dynamic: values derived from models, historical data, or context (for example, thresholds based on rolling averages).

Thresholds are often documented in specifications, control plans, procedures, recipes, system configuration records, or alarm philosophy documents. In regulated environments, changes to thresholds are typically controlled through formal change management and may require risk assessment and justification.

What a threshold is not

• It is not the same as a full control strategy or quality system; it is one parameter within those systems.
• It is not inherently a specification; specifications may contain thresholds, but also include context and requirements.
• It is not necessarily a physical limit of equipment; it is often set more conservatively for safety, quality, or regulatory reasons.

Common confusion

• Threshold vs. setpoint: A setpoint is the target operating value (for example, maintain 100 °C). A threshold is a limit at which an action occurs (for example, alarm at 105 °C). In some systems, alarm thresholds are defined relative to a setpoint.
• Threshold vs. tolerance: Tolerance is the allowed variation around a nominal value (for example, 10.0 ± 0.2 mm). Thresholds are the numerical boundaries used to judge whether a value is inside or outside that allowed range, or to trigger specific responses.
• Threshold vs. limit: In many manufacturing and OT/IT systems the terms are used interchangeably, but “limit” often refers to the numeric boundary itself, while “threshold” is the boundary in the context of a decision or trigger.

Use in OT, IT, and MES environments

In OT and manufacturing IT systems, thresholds are implemented as configuration values in controllers, SCADA systems, MES, historians, and analytics platforms. Examples include:

• Alarm and warning levels on tags collected from PLCs or sensors.
• Data validation rules that reject or flag readings outside predefined ranges.
• Workflow rules that open deviations, NCs, or CAPA tasks when metrics cross certain values.
• Dashboards that change status (for example, green/yellow/red) when KPIs move past defined thresholds.

Clear definition, documentation, and governance of thresholds support consistent operation, traceability of decisions, and audit readiness in regulated manufacturing environments.