Production Blockers: A Taxonomy for High-Mix Manufacturing

TL;DR

"Late" is not a blocker.

It is the result of a blocker. High-mix shops need a shared taxonomy for what is actually stopping work: material, revision, tooling, programming, machine capacity, outside process, QC, customer clarification, labor, or business closeout.

In AIURION today, the Production matrix shows released jobs by phase health, blocked state, owner context, and next action. Material and Tooling use requirement rows; Programming, Setup, Operations, QC, and Packaging use production phases. The more detailed reason categories in this article are an operating convention, not a claim that every category is a dedicated product field.

Skip Ahead

• Why labels matter
• The blocker taxonomy
• Copyable blocker schema
• Example blocker board
• What good blocker records include
• Where AIURION OS fits
• Your next move

Why Labels Matter

If every issue becomes "delayed," the shop cannot improve.

Delay labels hide root cause. A blocker taxonomy makes the constraint visible.

NIST's digital-thread work focuses on keeping usable information connected across design, manufacturing, and product support; it also identifies gaps in those information flows as a barrier to enterprise-wide use ^[S1]. A blocker record is a small, operational version of that principle: the status needs its reason, evidence, owner, and next action.

Diagram: Blocker tracking works when the team shares reason, owner, and next action.

The Blocker Taxonomy

Start with the phases the shop already runs:

Production Phase	Example Blocking Reason
Material	stock late, cert missing, substitution open
Tooling	fixture unavailable, cutter not ordered
Programming	CAM not complete, setup strategy open
Setup	machine, fixture, program, or operator not ready together
Operations	machine unavailable, prior operation incomplete, assignment open
QC	inspection hold, FAI requirement, nonconformance
Packaging / Shipping	pack requirement, shipping document, or release evidence missing

Revision, customer clarification, outside process, and commercial closeout are still useful reason categories. In AIURION today they should be recorded in the relevant requirement or phase notes rather than presented as dedicated Production phases. The goal is not perfect classification. The goal is a useful next action without misrepresenting the operating system.

Copyable Blocker Schema

Use the same fields in a spreadsheet, stand-up board, or job record:

Field	Entry Standard
Blocker ID	Stable identifier for follow-up
Job	Order/job number and part
Production phase	Material, Tooling, Programming, Setup, Operations, QC, or Packaging
Reason category	Revision, supplier, customer, outside process, capacity, quality, documentation, or other local convention
Blocking fact	One observable condition; avoid "job late"
Evidence	PO, email, drawing revision, traveler operation, inspection result, or document reference
Owner	One person responsible for the next action
Next action	Verb + object + completion condition
Review by	Date/time when the blocker is checked again
Status	Open, monitoring, or resolved; map to the product phase status where applicable
Resolution evidence	What changed, when, and who verified it

Do not put several unrelated issues into one blocker. If a late material receipt and an unapproved revision require different owners, they are two records.

Example Blocker Board

The rows below are illustrative, not customer data.

ID	Job	Phase	Reason	Blocking Fact / Evidence	Owner	Next Action	Review By	Product State
BLK-104	J-2417 / valve body	Material	Supplier document	17-4PH stock is ordered, but the required cert is not attached; PO-7812	Maya / Purchasing	Obtain cert and attach it to the traveler before receipt is accepted	Jul 29, 2:00 PM	Material requirement: Ordered
BLK-105	J-2420 / clamp plate	Programming	Internal readiness	Operation 20 has no approved CAM program reference in the released routing	Eli / Programming	Post, verify, and record the approved program file in the operation notes	Jul 29, 11:00 AM	Programming phase: Blocked
BLK-106	J-2423 / cover	QC	Customer clarification	Drawing Rev C conflicts with PO note on finish inspection; email thread linked	Noor / Quality	Get written customer disposition and update the QC plan	Jul 30, 9:00 AM	QC phase: Needs Check

The Product State column deliberately uses current AIURION status language. The Reason column is the shop's classification convention.

What Good Blocker Records Include

A blocker should have:

• category
• plain-language description
• owner
• created date
• next action
• due or review date
• related job record
• resolution note

Without those fields, blocker tracking becomes another status board that needs a meeting to interpret.

Where AIURION OS Fits

AIURION OS exposes blocked released work through the Production matrix and its phase gates.

That lets the shop see:

• which jobs are blocked
• why they are blocked
• who owns the next step
• what customer or QC context matters
• which prerequisite must clear before the next phase can advance

Material and Tooling requirement rows carry label, status, owner, notes, and ETA. Programming, Setup, Operations, QC, and Packaging carry phase status, owner, and notes. The current assistant can summarize blockers and next actions from the available Production snapshot; people still classify the reason, assign the owner, update the record, and approve commitments.

For production visibility, see job shop production tracking. If blocker reviews are still verbal, request a focused pilot.

Your Next Move

Take this week's late jobs and enter them in the example board. If a row has no blocking fact, evidence, owner, or next action, fix that record before adding more categories.