Skip to content

U-chart

A statistical process-control chart for nonconformities per inspection unit when the number or size of units inspected can vary between samples.

Version
v1 · 2026-09-08 · History
Domain-specific #
7309
Origin domain
statistical quality control
Subdomain
statistical quality control

Core Idea

The u-chart models defect opportunities through a Poisson-style count rate, uses a weighted center line, and adjusts each sample's control limits according to its exposure n_i. Nonconformity counts are divided by inspected units or opportunity; the pooled average estimates the process rate, and variance-scaled limits flag observations inconsistent with common-cause variation. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

Scope of Application

U-chart belongs to statistical quality control and is useful where the analyst can specify the typed statistical quality control carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, then evaluate the process and nonconformity definition, rational subgroup and opportunity unit, counts and varying sample sizes, pooled rate, Poisson and independence assumptions, limit formula and sigma level, zero truncation, overdispersion check, phase, and response rule are explicit. The scope is broad within that domain but bounded by the need for the process and nonconformity definition, rational subgroup and opportunity unit, counts and varying sample sizes, pooled rate, Poisson and independence assumptions, limit formula and sigma level, zero truncation, overdispersion check, phase, and response rule are explicit.

Clarity

The abstraction clarifies a crowded vocabulary by making the process and nonconformity definition, rational subgroup and opportunity unit, counts and varying sample sizes, pooled rate, Poisson and independence assumptions, limit formula and sigma level, zero truncation, overdispersion check, phase, and response rule are explicit the center of the account. A claim should name the carrier, the governing operation or relation, the applicable assumptions, and the recognition test.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to U-chart. U-chart compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: the typed statistical quality control carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2.

Knowledge Transfer

Knowledge transfers strongly among subfields of statistical quality control because they reuse the typed statistical quality control carrier, defining objects and relations, parameters, conventions, evidence, boundary cases, and comparison targets, Nonconformity counts are divided by inspected units or opportunity; the pooled average estimates the process rate, and variance-scaled limits flag observations inconsistent with common-cause variation., and type the carrier, state every parameter and convention in the definition, test that the process and nonconformity definition, rational subgroup and opportunity unit, counts and varying sample sizes, pooled rate, Poisson and independence assumptions, limit formula and sigma level, zero truncation, overdispersion check, phase, and response rule are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for U-chartParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.U-chartDOMAINPrime abstraction: Quality Control — is a kind ofQuality ControlPRIME

Current abstraction U-chart Domain-specific

Parents (1) — more general patterns this builds on

  • U-chart is a kind of Quality Control Prime

    The proposed strict upward parent is prime:quality_control.

Hierarchy paths (2) — routes to 2 parentless roots

Neighborhood in Abstraction Space

U-chart sits in a crowded region of the domain-specific corpus (20th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Quality Assurance & Process Capability (12 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08