# Connect manufacturing quality with process evidence.

Connect process conditions, production records and inspection results to support manufacturing quality investigations.

Canonical: https://vieox.com/solutions/quality/
Publisher: VIEOX
Published: 2026-10-19
Updated: 2026-10-25

## What process information is useful in a quality investigation?

Start with the finding, the affected product or production period and the recorded conditions that can be linked to it reliably. Include how the quality measurement was made, what requirement applies and which parts of the history remain uncertain.

Software for monitoring manufacturing quality needs a dependable link between a finding, the product or batch and the process that made it. An OT foundation gives the investigation a clear starting point: which conditions were recorded, when they applied and how confidently they relate to the result.

## Connect the finding to the right period

Begin with a precise description of the concern: the characteristic measured, the result, the requirement and the product or lot involved. Then establish the relevant production window. The time an inspection result was entered may differ from the time the product was made.

Review process readings alongside the available production and inspection records. Confirm how they relate before combining them. If a record identifies only a shift or a batch, retain that level of certainty; avoid presenting it as evidence about a specific item without a dependable link.


## Understand what the comparison can tell you

Compare the affected period with a relevant reference period and note changes in material, settings, equipment or working conditions. Treat an apparent relationship as a lead for investigation. NIST's statistical guidance explains that an association between variables does not, by itself, establish cause and effect.

Where a team uses control charts, distinguish control limits from specification limits. Control limits help assess process consistency; specification limits concern the product's requirements. A process being statistically stable does not, by itself, show that its output meets those requirements.

- Keep the product requirement and the measurement method visible.
- Check that the selected periods and products can be compared.
- Record missing history and uncertain links between records.
- Ask what further evidence would confirm or challenge an explanation.

Sources: [1](https://www.itl.nist.gov/div898/handbook/eda/section3/scatterp.htm), [2](https://www.itl.nist.gov/div898/handbook/pmc/section3/pmc32.htm)

## Create a shared investigation

Bring production and quality colleagues into the same review, with maintenance or engineering where relevant. Record the observations, the proposed explanation and the next check separately. This makes it easier for another person to understand how the investigation progressed and where a conclusion still needs support.

VIEOX brings an OT perspective to manufacturing software: begin with the process and establish what the available records can support. ConverEDGE is designed to help teams review operating activity in context. A first discussion identifies the quality question, the process information available and the connection to production and inspection records that needs to be assessed.


## Connect the finding with its production context.

Consider a quality concern found after a run. The process history can help frame an investigation when it belongs to the relevant work.

### What the record may show

- The quality finding and the item or batch examined.
- Process conditions recorded during a particular period.
- A pattern the team wants to understand.

### What the team still needs to establish

- Whether the item and production period have been matched correctly.
- Which differences in material, settings or conditions matter.
- What supports an explanation of the quality finding.

## A quality concern within one production period

Hypothetical operating example.
Hypothetical example: a team finds an unusual dimensional result in a group of components. It wants to understand which process conditions deserve closer examination.

1. Confirm the inspection result, applicable requirement and affected group.
2. Establish when the components were produced using available records.
3. Compare relevant conditions with a suitable reference period.
4. Test the proposed explanation through the team's established investigation process.

## Practical starting points

- Choose one recurring quality question and one relevant process.
- Bring the finding, applicable requirement and available production context.
- Agree how the team will judge whether a connection is supported.

## Questions, answered

### Are process readings the same as product quality results?

They describe different things. A process reading records an operating condition; a quality result measures or assesses a product characteristic. The relationship between them needs to be established for the specific process and investigation.

### Can a chart prove the cause of a defect?

A chart can reveal patterns worth examining. Confirming a cause requires appropriate engineering or scientific evidence and consideration of other explanations. A visible relationship is a starting point for investigation, with its limits kept clear.

Sources: [1](https://www.itl.nist.gov/div898/handbook/eda/section3/scatterp.htm)

### What if a result is within specification but the process looks unusual?

The product requirement and process behaviour are separate questions. A process pattern may warrant investigation even when individual results meet specification. The quality team should interpret the evidence using a suitable method and its established procedures.

Sources: [2](https://www.itl.nist.gov/div898/handbook/pmc/section3/pmc32.htm), [3](https://www.itl.nist.gov/div898/handbook/pmc/section3/pmc31.htm)

### What should software for monitoring manufacturing quality connect?

Evaluate whether the proposed scope can relate inspection results to the appropriate item, batch or production period and to the relevant process history. Keep the measurement method, requirement and uncertain links visible. Agree how this supports the established quality system; an operating dashboard alone does not establish product acceptance.

## Sources and further reading

- [NIST — Scatter Plot](https://www.itl.nist.gov/div898/handbook/eda/section3/scatterp.htm)
- [NIST — What are Variables Control Charts?](https://www.itl.nist.gov/div898/handbook/pmc/section3/pmc32.htm)
- [NIST — What are Control Charts?](https://www.itl.nist.gov/div898/handbook/pmc/section3/pmc31.htm)

## Related reading

- [From a stop to a supported explanation](https://vieox.com/insights/investigating-production-downtime/)
- [Production visibility](https://vieox.com/solutions/production/)
- [Equipment condition and maintenance](https://vieox.com/solutions/maintenance/)
- [Why operational data needs context](https://vieox.com/insights/operational-data-context/)
- [Explore ConverEDGE](https://vieox.com/converedge/)
