MES

Capture the Process Data Behind Quality and Performance

Collect PLC and sensor values on the conditions you define, track them over time, and use that data for trends, alerts, and process monitoring.

10in6 turns live process signals into historical data your team can analyze and act on.

The data that exists but never gets used

Many important process values live in the PLC but never get collected in a useful way.

Temperature, pressure, speed, cycle time — the machine knows these values constantly, but without a system capturing and storing them, they disappear the moment the next cycle starts.

That makes it harder to see drift, catch abnormal conditions, investigate quality issues, or understand how the process was behaving during a specific run. The data exists. It just has nowhere to go.

What it looks like Process variable trend — Barrel Temp Zone 3, Press Line 4
Process Variable Collection Barrel Temperature — Zone 3  ·  Press Line 4
Source: Line 4 PLC Interval: Every 5 min ⚠ 2 Out of Range
Current 365.2°F
Target 365°F
Avg (2 hr) 365.8°F
Min 355°F
Max 374°F
UCL 373°F
LCL 357°F
UCL LCL 354 358 362 366 370 374 °F 08:00 08:25 08:50 09:15 09:40 10:05 10:24
Measured Value UCL / LCL Out of Range Target
How 10in6 Process Variable Collection works

From signal to searchable history.

01

Connect to the signals that matter

10in6 connects to PLC and sensor outputs — temperature, pressure, speed, level, position, or any value your process exposes — without requiring modifications to existing control logic.

02

Set when and how values are collected

Collection rules are configured through the 10in6 interface. Values can be captured on a timed interval, on change, or when they cross a defined threshold — no custom programming required.

03

View trends and catch drift early

Collected values are stored historically and displayed as trend charts with upper and lower control limits, so gradual drift is visible before it becomes a quality or performance problem.

04

Trigger alerts when limits are crossed

When a variable moves outside its defined range, alerts can notify the right people immediately — giving operators and engineers the chance to respond before the condition affects output.

05

Tie variable data to jobs and products

Collected values can be associated with the job or product running at the time of collection. That context makes it far easier to investigate quality escapes, compare process behavior across runs, and build the data foundation needed for SPC and continuous improvement.

What process variable data makes visible

Live signals stored as searchable history.

With 10in6 Process Variable Collection, your team can see:

  • Trend charts for any configured variable
  • Historical process values over any time range
  • Upper and lower control limits on every chart
  • Alerts when values move outside defined boundaries
  • Variable history tied to specific products or jobs
  • Multiple variables compared across the same time window
  • The data foundation for SPC and quality monitoring

Why this matters for quality and process improvement

Most quality investigations fail because the process data was never captured. With variable collection in place, engineers and quality teams can look back at exactly what the process was doing during a problem run — and use that data to find root cause faster, prevent recurrence, and build a stronger case for process changes.

Common Questions

Process Variable Collection questions

What types of signals can be collected?
Any value available through the PLC or connected sensors — temperature, pressure, speed, cycle count, level, position, or other process values your operation monitors.
How frequently can values be collected?
Collection frequency is configurable. Values can be collected on a timed interval, on change, or when a value crosses a defined threshold.
Can alerts be triggered when a variable goes outside normal range?
Yes. Upper and lower limits can be defined for any variable, and alerts can be triggered when values move outside those boundaries.
Can variable data be tied to specific jobs or products?
Yes. Collected values can be associated with the job or product running at the time of collection, making it easier to investigate quality issues or compare process behavior across runs.
Does this require custom programming to configure?
No. Collection rules are configured through the 10in6 interface. Engineering or IT involvement is not required for routine configuration changes.
Is this the same as SPC?
Process Variable Collection is the data layer that SPC builds on. It handles signal capture and historical storage. SPC analysis — control charts, capability indices, and statistical alerts — is a separate module that uses that data.
Software With Service

Need this configured around your actual equipment and workflows?

Every 10in6 deployment includes our team — connecting your equipment, configuring your workflows, and supporting your operation long after go-live.

See how the Delivery Model works →

Start capturing the process data that explains what is really happening.

Connect to the signals your PLCs already expose, build a historical record, and give your team the data foundation they need for quality monitoring and continuous improvement.

Request a Demo → Explore MES