Seed-coat fragments are one of the few cotton impurities that survive both the fine cleaner and the card, which means the gin’s process problems become the spinner’s yarn defects and the dyehouse’s dark specks on greige fabric. AFIS at the gin already measures neps and seed-coat neps per gram of lint. The spinner’s batch record almost never sees that data, so the trace from a fabric claim back to a gin lot ends at goods receipt.
iFactory / Seed-coat nep source tracking
Trace Seed-Coat Fragments From the Gin Through Your Fiber Batch Record
Link the gin's AFIS or nep-proxy reading to the fiber batch the spinner receives, so a nep source stays visible three process steps downstream — where the claim will actually land.
140–292
AFIS neps/g by cultivar
13–27%
of neps contain SCF
Gin-to-spinner
AFIS write-back
The Problem on the Line
Seed-coat fragments — the seed pieces broken loose during ginning that leave with the lint — are the impurity carding cannot remove and the yarn clearer will not always catch. In the Boykin AFIS study of Mississippi cultivars, neps ranged 140 to 292 per gram of lint, and 13 to 27% of neps carried seed-coat fragments. In the smaller AFIS subset scored as seed-coat neps — 0.5 to 3 mm with fibers still attached — the fragment survives the fine cleaner and the card entirely, then appears as a nep in yarn and a dark speck on greige fabric. The gin already knows moisture and settings shifted the number. The spinner’s batch record does not.
What Escapes Into the System of Record Today
AFIS reports and vision-trash classes at the gin are typically kept as gin-side records. The spinner's fiber batch record — the one that would let a QA head trace a nep back to a source — usually has no link to them.
Paper
Gin AFIS printout sits in a gin-office file drawer. The spinner receives the bales with an HVI classing sheet — which does not include AFIS nep or SCN data — and nothing else.
WhatsApp
Gin manager and spinner's procurement team compare notes ad hoc on high-nep lots by phone or WhatsApp. Nothing lands in the batch record the QA head consults when a dye spot appears.
Winder-only data
Elevated foreign-fiber-not, class-A defect count on the yarn clearer registers days later. The winder record shows a yarn defect; it does not know whether the source was gin nep, mixing contamination, or card wire damage.
Nowhere at all
Dye spots on greige fabric are recorded on a lab loft inspection sheet weeks after the yarn shipped. The lint that produced them was consumed six weeks earlier and the bale genealogy back to the gin does not exist.
What the Camera or Agent Actually Sees
The camera or agent in this case is smaller and more focused: not a bale-opener contamination system, but a link that pulls the gin-side AFIS nep and SCN readings, plus any vision-trash class the gin already runs, into the fiber batch record the spinner uses.
Gin AFIS Data
AFIS nep count, seed-coat nep count, and SCN size distribution captured at the gin's AFISPro run and linked to the bale IDs from that run.
Read: AFIS neps/g + SCN/g
Gin Vision Trash
If the gin runs a vision trash classifier at the lint slide or bale press, its per-bale trash-class output is pulled into the same batch record.
Read: trash class per bale
Moisture & Settings
Gin moisture at the extractor-feeder and gin-stand settings for the run, since Boykin's work confirms both shift the SCF-in-lint number the spinner will see.
Read: gin process context
Bale Genealogy
The link that binds gin-side readings to the bale IDs and to any downstream mixing lot the spinner assembles from that receipt.
Link: gin lot → mix → yarn
What Gets Written Back
For this problem the write-back is less about blocking a lot and more about carrying context forward. The spinner's system of record has to hold what the gin's system of record already knows, so a downstream dye-spot claim can be traced to a source.
Batch Classification
SAP Batch Mgmt
Gin AFIS nep count, SCN count, and trash class attached to the bale batch's classification characteristics — the same view the QA head already queries by batch.
Inspection Lot
SAP QM
Incoming inspection lot (type 01) at goods receipt populated with the gin's AFIS data instead of only the mill's bale-side sample, so the number the UD is made against is truthful.
Vendor Master QII
SAP QM Q-Info
Quality info record against the gin as vendor, so nep and SCN trends per gin per month become a procurement conversation, not a phone call.
Yarn Batch Trace
SAP Batch Genealogy
Yarn batch's upstream trace includes the gin-side AFIS profile of the source bales — the dyehouse can ask why fabric shows dye spots and get an answer, not a shrug.
Take one yarn batch that produced a fabric dye-spot claim last quarter. See how far back its bale genealogy goes today. If it stops at your goods receipt, the gin is invisible to your quality system. Book a plant assessment — we'll show what the trace looks like with gin-side data linked in.
12-Week Pilot Shape on One Station
One gin partner, one spinner, one product family. This pilot is not vision-heavy — it is a data-link pilot. The point is to prove that gin AFIS and trash-class data, delivered into the spinner's batch record, changes what the QA head can see when a claim arrives.
Weeks 1–2
Data Handshake
Gin AFIS/AFISPro output and any vision-trash classifier output identified. File format, cadence, and bale-ID mapping agreed. Data pipeline sketched between gin office and spinner's SAP QM inspection lots.
Weeks 3–4
Baseline Match
Two weeks of parallel capture: spinner's mill-side AFIS sample and the gin's AFIS on the same receipts. Reconciliation between the two numbers so the QA head trusts the linked data.
Weeks 5–8
Batch Link Live
Gin AFIS nep, SCN, and trash class written to the bale batch classification and the incoming inspection lot in SAP QM. Vendor Q-info record populated per gin per month.
Weeks 9–12
Claim Trace Test
First fabric claim in the window is traced back through yarn batch genealogy to bale batch classification to gin AFIS record. The question shifts from "which bales?" to "which gin process context?"
Who Owns the KPI
Cross-boundary data links have a habit of decaying because no single role owns them. This is where naming the KPI owners at both the spinner and the gin matters more than the technology.
QA Head (Spinner)
SCN/g per gin per month
Owns the SCN trend and the decision to escalate a gin partner where the number drifts. Reviews yarn claims traced to elevated SCN batches monthly.
Packing / Bale Yard
Bales received with linked AFIS data %
Owns the receipt-side workflow — every bale receipt is expected to arrive with the gin AFIS reading available. Missing data is a receipt exception, not a quiet gap.
Dyehouse Liaison
Dye-spot claims traced to a source SCN batch
Owns the loop-close on fabric claims. When a dye spot lands in the loft, the trace must reach the gin AFIS number or the trace pipeline is broken.
Procurement / GM
Gin AFIS profile written into supplier scoring
Owns the annual gin evaluation. AFIS nep and SCN trend feeds the price and volume decision, so gins with cleaner ginning discipline receive commercial signal.
FAQ
Why AFIS specifically? Isn't HVI classing enough?
HVI classing gives length, strength, micronaire, uniformity, and color grade — the traits that price the bale. It does not report nep count or seed-coat nep count, which are the two AFIS measurements that predict dye spots on greige fabric. Boykin and Bel's USDA-ARS work at the Cotton Ginning Lab established SCN as the closest fiber-side measurement of what shows up on dyed fabric as dark specks. If nep and SCN are not in your batch record, HVI classing alone will not let you trace a dye-spot claim to a source.
What if my gin partners don't run AFIS?
Two paths. First, many gin partners that supply spinners at scale already run AFIS or AFISPro because their own quality customers require it — the data exists, it is just not being handed forward. Second, where AFIS is not available at the gin, an equivalent vision-trash and nep-proxy reading at the bale press, run by the mill's own portable sampling, can populate the same batch classification field. The record structure matters more than the source instrument, as long as the measurement is repeatable.
How does this interact with our existing yarn clearer's foreign-fiber-not class-A tally?
The yarn clearer stays exactly where it is and continues to make the winding-time cut decision. What changes is that a class-A defect log at winding can now be traced backward: which yarn batch, which mix, which bales, which gin AFIS record. Instead of only knowing that yarn-side defects are elevated on Wednesday's production, you can attribute the elevation to a specific gin lot with a specific SCN profile — which is the level at which procurement and gin-partner discipline can actually change.
Stop stopping the trace at goods receipt.
See a Gin-to-Yarn AFIS Link on One of Your Own Claims
Bring one fabric dye-spot claim from the last quarter and the yarn batch that produced it. We'll show what the linked bale genealogy would look like if gin AFIS data lived in your batch classification, and what that changes at your procurement review.
