VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

The Gold Standard of Polymer Science | Hierarchical Seal-Width Models, Machine–Shift Variance and Process-Capability Gates

GOLD STANDARD · POLYMER SCIENCE · HOW X WORKS

Separate machine, shift, unit and perimeter variation before calling a seal process capable

Seal-width measurements are nested: positions sit within units, units within shifts, and shifts within machines or lots. A hierarchical model keeps those levels visible, so a large pile of perimeter pixels cannot disguise a weak machine–shift combination or inflate confidence in lot release.

This guide connects the Gold Standard of Polymer Science, Gold Standard of Education, and How X Works hub.

CHAPTER 1 OF 12 · MAP THE HIERARCHY

1. A perimeter scan contains several sampling levels

Back to contents

Sixteen positions from one module do not equal sixteen independent modules. They share material, dispenser setup, cure history and operator conditions. Modules share a shift; shifts share a machine and recipe. Write this nesting before estimating any uncertainty.

A useful baseline is position within unit, unit within machine–shift, and machine–shift within lot. Add material batch, tool head or cavity when the process makes them distinct. The hierarchy should follow physical causes, not whichever columns happen to exist in the spreadsheet.

Contents · Next chapter

CHAPTER 2 OF 12 · MAP THE HIERARCHY

2. Decide which effects are fixed, random or changing

Back to contents

A fixed effect estimates named differences the team wants to act on, such as Line A versus Line B. A random effect estimates variation across sampled shifts or units and supports prediction to comparable future levels. Time drift may require a trend or state model rather than either label.

The choice changes the claim. A model that treats two specific machines as random cannot confidently describe the wider factory fleet from only two levels. State the population of inference beside every variance component.

Contents · Previous chapter · Next chapter

CHAPTER 3 OF 12 · ESTIMATE VARIATION

3. Build a variance ledger before a capability index

Back to contents

Estimate how much spread belongs to gauge, machine, shift, unit and perimeter position. A component can have a small average effect but create an important tail when it combines with another level. Retain interactions when engineering suggests them, especially machine by shift or machine by material batch.

LevelPossible mechanismAction if large
GaugeLighting, edge algorithm, fixtureImprove or guard-band measurement
MachineNozzle alignment, clamp geometryService or qualify separately
ShiftSetup, temperature, operator sequenceStandardise and monitor
UnitGlass bow, material placementTrace upstream variation
PositionCorners, starts, splicesTarget local geometry
The ledger links statistical variation to a repair route; it is not a claim that every effect is independent or normal.

Plot raw profiles alongside model estimates. A single variance number can hide systematic corner dips, multimodal machines or a slow drift across the shift.

Contents · Previous chapter · Next chapter

CHAPTER 4 OF 12 · ESTIMATE VARIATION

4. Respect clustering when constructing uncertainty

Back to contents

Use cluster-aware intervals, hierarchical simulation or block resampling that keeps positions from one unit together. Counting every pixel as independent can shrink a standard error by an order of magnitude while adding almost no information about future units.

Include measurement uncertainty at the correct level. Repeatability contributes to position-level noise; station or operator bias may sit higher. If the gauge has not been characterised, the process model is partly a measurement-system model.

Contents · Previous chapter · Next chapter

CHAPTER 5 OF 12 · WORK THE MODEL

5. Work a machine–shift variance decomposition

Back to contents

Suppose two machines are observed across four shifts, with 25 modules per machine–shift and 16 perimeter positions per module. A fitted illustrative model estimates standard deviations of 0.20 mm between machines, 0.30 mm between shifts within machine, 0.24 mm between modules and 0.40 mm around the perimeter.

SummaryMachine AMachine BDecision signal
Mean width9.65 mm9.28 mmB is closer to lower limit
Worst shift mean9.41 mm8.91 mmB-night needs containment
Predicted 0.1% tail8.54 mm8.08 mmB crosses 8.50 mm limit
Naive pooled Cpk1.341.07Pooled number hides local tail
Illustrative values. Real tail estimates require validated distributional assumptions, stable operation and gauge uncertainty.

The pooled average suggests an acceptable process, but the hierarchical predictive tail identifies a machine–shift combination that cannot pass release. The repair is targeted qualification, not more positions from already-safe modules.

Contents · Previous chapter · Next chapter

CHAPTER 6 OF 12 · BUILD CAPABILITY GATES

6. Require stability before capability

Back to contents

NIST defines process capability as a comparison between a stable process and specification limits. If mean, variance or distribution changes across time, one Cpk number is not a lasting property. First show control within the intended operating state or model the changing state explicitly.

For a one-sided minimum width, use a lower capability measure or a predictive lower-tail rule. A symmetric two-sided index can waste attention on harmless high widths while understating the lower-edge risk.

Contents · Previous chapter · Next chapter

CHAPTER 7 OF 12 · BUILD CAPABILITY GATES

7. Use a sequence of release gates

Back to contents

A practical gate sequence is: qualified measurand and gauge; stable process within each claimed stratum; hierarchical tail above the guard-banded limit; no verified local failure; and engineering confirmation that width remains a valid control for the qualified seal system.

Failing an early gate blocks later numerical comfort. A high capability estimate from an unstable process or biased gauge is not a conditional pass. Record which gate failed and the corrective evidence required for reopening.

Contents · Previous chapter · Next chapter

CHAPTER 8 OF 12 · TRANSFER THE METHOD

8. Changed-context transfer: pouch sealing and adhesive dispensing

Back to contents

Heat-sealed pouches have positions within pouches, pouches within runs and runs within sealing jaws. Structural adhesive beads have cross-sections within assemblies, assemblies within fixtures and fixtures within shifts. Both benefit from the same nested sampling and variance ledger.

Failure modes differ. Channel leaks and contamination can dominate pouch performance; cure chemistry and joint loading can dominate structural adhesive. Transfer the hierarchy, not the seal-width threshold or capability target.

Contents · Previous chapter · Next chapter

CHAPTER 9 OF 12 · QUALIFY THE RESULT

9. Check model form with engineering residuals

Back to contents

Inspect residuals by position, machine, shift, width level and time. Heavy lower tails, multimodality or spatial correlation can make a normal random-effects model optimistic. A transformation or robust predictive quantile may be more honest than forcing Cpk.

Compare model predictions with held-out units and destructive references. Hierarchical complexity is not a substitute for external checking. If the rare tail is decision-critical, design sampling to observe it rather than relying only on extrapolation.

Contents · Previous chapter · Next chapter

CHAPTER 10 OF 12 · QUALIFY THE RESULT

10. Limits and common misconceptions

Back to contents

Variance components are conditional on the sampled design and can be weakly estimated with few machines or shifts. A large number of positions does not compensate for two machines. Random effects do not make every future factory line exchangeable.

Capability does not prove moisture life, adhesion or pinhole absence. It describes a measured geometric characteristic under stability and model assumptions. Keep the process claim narrower than the product reliability claim.

Contents · Previous chapter · Next chapter

CHAPTER 11 OF 12 · CHECK AND CONTINUE

11. Questions readers often ask

Back to contents

Why not calculate Cpk for each machine separately?

That can be useful, but it discards information about shared and shift-level variation unless the hierarchy is also examined. Separate indices should follow, not replace, a physical variance map.

Can a hierarchical model release a unit with one failed position?

Not when the unit rule treats a verified local failure as nonconforming. The model supports lot inference and process learning; it should not average away an absolute safety requirement.

Contents · Previous chapter · Next chapter

CHAPTER 12 OF 12 · CHECK AND CONTINUE

12. Evidence, connected routes and the next check

Back to contents

NIST guidance on nested variation explains hierarchical sampling structures and multiple variability sources. NIST process-capability guidance states the stability and distribution assumptions behind capability indices. JCGM 100:2008 provides the measurement-uncertainty framework.

Continue through seal-width metrology and lot-release confidence, seal-width tolerances and worst-case margins, seal-width scaling and corner diffusion, and barrier pinholes and ingress identifiability. The next check is to count independent machines and shifts, not perimeter pixels.

Contents · Previous chapter