Skip to content

Spinning: count-wise production and USTER results from your records

Ask which counts ran below plan last shift, how a lot’s USTER results compare with the buyer’s limits, or which bales went into it. The agent shows the rows and reports it used, and nothing is changed or sent unless an admin approves it.

Works from: Mixing sheet, Count change log, USTER/HVI report, Lot card

Four problems between the bale and the packed cone

They sit in records the mill keeps, many by hand: the daily production report, the USTER printout, the mixing sheet and the waste register. They cost kilos not spun, cones packed out of spec, and cotton bought at lint price that leaves the mill as waste.

  • A lot questioned weeks later, and its mixing sheet in a binder

    The mixing sheet records each HVI-graded cotton lot and its share, the comber noil and any recycled fibre, signed on paper by the mixing master. Weeks later a knitter reports neps, contamination or shade bands in fabric from one yarn lot. Tracing it back to the mixing and the bale set means pulling binders and lot cards, while the buyer waits to hear which bales went into which lot.

    22%

    Share of cottons that spinning mills perceived as moderately or seriously contaminated in ITMF’s 2022 survey of 104 mills in 21 countries, down from 25% in 2019. The ten most contaminated included Indian and Pakistani growths.

    Source: Textile World (ITMF release), ITMF’s Cotton Contamination Survey Number 16/2022 Reveals Decreasing Levels Of Contamination And Stickiness (opens in a new tab), 2023.

  • Waste weighed by section, yarn realisation worked out late

    Blow room droppings, card waste, comber noil, yarn waste and sweep are weighed by section; invisible loss is what is left unaccounted for. Setting them against cotton issued and yarn packed is a month-end job, if anyone does it, so a section over its norm stays hidden for weeks. A 2023 article from Ethiopia’s textile research centre says almost all mills in Ethiopia cannot calculate yarn realisation accurately.

    40–70%

    Raw material’s share of yarn cost, depending on the count, as quoted in a 2023 article on yarn realisation in Ethiopian mills. It adds that a 1% fall in realisation hits profit almost as hard as a 1% rise in lint cost.

    Source: Indian Textile Journal, Yarn realisation in spinning: Some case studies in Ethiopian mills (opens in a new tab), 2023.

  • Shift production written in a register, read the next morning

    Each shift writes kilos by count, frame efficiency, stoppages and count changes into a register or an Excel sheet. Next morning the spinning master rebuilds count-wise totals against plan by hand, but not frame by frame. The playbook reads a frame more than 5% off its target as a mechanical or operator issue. In a register, that frame stays hidden until someone adds up the week.

  • USTER reports checked against the buyer’s limits by eye

    The lab prints the USTER report per machine and shift. Someone compares U%, IPI and hairiness with the buyer’s spec by eye, and the cones go to packing. U% drifts after a rushed count change, and IPI creeps up as card clothing wears. When nobody sets two shifts side by side, cones outside the buyer’s USTER 25%-tile reach the knitter, and the spinning manager and the QA head hear of it as a claim.

What the spinning agent works out, reads and drafts

It answers from your production reports, USTER and HVI exports, mixing sheets and ERP records, and shows the files and rows it used. A message to the next shift or a new start on a production order waits for an admin to approve or decline.

  • Count-wise production against plan, totalled from the rows

    Answers with sources

    Upload the shift’s production report and the count-wise plan as Excel or CSV files. The agent totals the kilos of each count on the plan from the actual rows and sets each total beside its plan figure. It reads each ring frame’s efficiency and target from the report and names the frames it finds more than 5% off target, the playbook’s line for a mechanical or operator issue, citing each row.

    Ask“Which counts ran below plan on C shift last night, and which frames were more than 5% off target?”

  • USTER and CSP results read against the buyer’s spec

    Reads your documents

    Upload the USTER and strength test results as PDFs with text, Excel or CSV files, with the buyer’s yarn spec. The agent sets U% or CVm, thin and thick places, neps, hairiness and CSP against the limits the spec names, lot by lot and frame by frame, and cites the files. It is not connected to the tester, and a photographed printout has no text to read.

    Ask“Does lot 2231 of 30/1 combed meet the buyer’s spec for CVm, neps and hairiness? Show each value against its limit.”

  • A yarn lot traced back to its mixing sheet and bales

    Answers with sources

    Ask about a lot and the agent finds its lot card, the mixing sheet behind it and the HVI table for that bale set, when they are uploaded or kept in a connected Google Sheet. When an uploaded HVI table names each bale’s mixing, it works out that mixing’s average, lowest and highest micronaire from the rows. A photo or scanned copy of a signed mixing sheet has no text to read; the typed or Excel copy does.

    Ask“Trace lot 2236 to its mixing and bale set. What was the micronaire range of the bales in it?”

  • The month’s waste and realisation sheet, built from your register

    Creates files

    Upload the month’s waste register with cotton issued, yarn packed, the opening and closing process stock and the usable waste reused. The agent sums waste by section from the rows: blow room, card, comber noil, yarn and sweep. It sets each against your norms on file, works out yarn realisation for the mixing and builds the sheet. Ask for another column and it edits that part; every revision is kept.

    Ask“Build this month’s realisation sheet for the 40s combed mixing, with waste by section against our norms.”

  • A count run that has to wait, moved in the production order

    Reads your ERP

    When the trial cone fails USTER, the new count cannot start on time. Ask the agent to draft a new planned start for that production order in Odoo, or a change to who it is assigned to. A department admin approves or declines the change, and it runs in Odoo only if approved. Only an Odoo production order can be moved this way.

    Ask“The trial cone on frame 14 failed USTER. Draft a new planned start of Thursday, 6 am, for production order MO/00482.”

A short C shift, a USTER hold and shade bands blamed on the yarn

  • The morning after C shift fell short on two counts

    Spinning master

    The morning meeting is in twenty minutes, and the spinning master needs the frames behind the shortfall.

    1. Asks

      “Show count-wise production against plan for C shift, and the three ring frames with the lowest efficiency and their logged stoppages.”

    2. The agent

      Reads the shift’s production report, stoppage log and count-wise plan, each uploaded as its own Excel or CSV file. Totals the kilos of each count on the plan from the rows and sets each total beside its plan figure. Reads each frame’s efficiency from the report and lists the three lowest it finds, with the stoppage reasons logged against each. Cites the rows it used, and says where a frame has no entry.

    3. Result

      The meeting starts from the frames and stoppages on record, not from memory, with the rows behind every figure.

  • USTER out of spec for a second shift

    Spinning lab in-charge

    The 30/1 combed USTER results are outside the buyer’s 25%-tile on B shift, after the same on A shift.

    1. Asks

      “30/1 combed is out on USTER for two shifts. List the frames and values against the buyer’s spec, and draft the packing hold to the spinning manager and QA head.”

    2. The agent

      Reads both shifts’ USTER reports against the buyer’s yarn spec and lists the frames it finds outside a limit, with their U%, CVm and IPI. Quotes the playbook: two shifts below spec go to the spinning manager and the QA head, those shifts’ cones are held from packing, and the root cause is due within 24 hours. Adds the check order for U% drift, then drafts a WhatsApp Business message to both.

    3. Approval

      The message waits for a department admin, who approves or declines it. It is sent to the spinning manager and the QA head only if approved. The agent does not stop packing; the people on the floor do.

    4. Result

      A list of out-of-spec frames with their values and the playbook’s check order, ready for the 24-hour root-cause review.

  • Shade bands in fabric, blamed on the yarn

    Spinning manager

    The dye house reports shade bands in fabric knitted from yarn lots 2231 and 2236, and points at the yarn.

    1. Asks

      “Trace lots 2231 and 2236 to their mixings, give the micronaire average, lowest and highest for the bales in each, and the gap between the two lots.”

    2. The agent

      Reads the lot cards, the two mixing sheets and the bale HVI table uploaded to spinning. With a mixing column, it calculates each mixing’s average, lowest and highest micronaire and sets the gap between the two averages against the playbook’s 0.3 line for when yarn is part of a shade problem. Without one, it lists each bale’s micronaire as recorded and says the average needs a mixing column in the HVI table. It builds the traceability pack as a spreadsheet.

    3. Result

      The spinning manager has each lot’s bales and their micronaire from the records, and with a mixing column the gap between the two lots against the playbook’s 0.3 line, before anyone argues about a claim.

Capital, waste and power: what the published figures say

These are published figures on capital in spinning costs, blow-room waste and energy, each cited at its source. None of them is a Mavick result. Before a pilot, record yarn realisation, frame efficiency and units per kg (UKG), then compare them at its end.

  • Frames that lose output, found from the shift rows

    Over 40%

    Capital’s share of the manufacturing cost of spinning NE/30 yarn in Egypt, Central America and Pakistan, in ITMF’s 2021 cost comparison, which counts raw material separately. Labour is only 2–3% in India, Pakistan, Bangladesh and Egypt.

    How the agent helps

    Capital is paid for whether a frame runs or stands. Ask about a shift and the agent reads each ring frame’s efficiency from your uploaded production report, names the weakest and reads the stoppages logged against them in the stoppage log, citing each row. For one frame and count, it totals the shift’s kilos from the rows. It reads the record, not the frames.

    Track: Production per machine per shift (kg), by count

    Source: Specialty Fabrics Review (reporting ITMF), ITMF tracing production costs in the primary textile industry (opens in a new tab), 2022.

  • Yarn realisation worked out from your waste register

    7.45%

    Blow-room waste measured at one Ethiopian mill, against 5.22–6.53% expected from the trash in its mixing, in a 2023 case study by Ethiopia’s textile research centre with GIZ.

    How the agent helps

    The agent does not weigh waste. Upload the month’s waste register with cotton issued, yarn packed and the opening and closing process stock, and it sums waste by section from the rows, sets each against your norms and works out realisation for the mixing. A section above its norm shows on the sheet, with the rows behind it.

    Track: Yarn realisation %, by mixing and month

    Source: Indian Textile Journal, Yarn realisation in spinning: Some case studies in Ethiopian mills (opens in a new tab), 2023.

  • Energy per kilo, read from your meter sheet

    15–20%

    Energy’s share of production cost in textile mills, next only to raw material, as a 2013 energy-audit paper states. In the Tamil Nadu spinning mill it audited, ring spinning took about half the installed power.

    How the agent helps

    The playbook puts energy per kg in the daily report. Upload the day’s units consumed by section and the day’s production as Excel or CSV files, and the agent totals units and kilos from the rows and works out units per kg (UKG) for the day, or for a month when both sheets carry a month column. It reads what was recorded; it is not connected to the meters.

    Track: Energy per kg of yarn (UKG), by day

    Source: Journal of The Institution of Engineers (India): Series B (Springer), A Study on Energy Conservation in Textile Industry (opens in a new tab), 2013.

What to baseline before a pilot

Measure each one before the pilot starts, then again at its end.

Spinning: the KPIs to baseline before a pilot, and why each matters
KPI to baselineWhy it matters
Production per machine per shift (kg), by countThe playbook reads a variance of more than 5% from target as a mechanical or operator issue, frame by frame.
U% or CVm within the buyer’s specThe playbook targets 98% or more of cones within the buyer’s USTER 25%-tile. Below 95%, it calls for an immediate process review.
IPI: thin places, thick places and neps per kmThe playbook’s target is the USTER 25%-tile. A rise over a week points to card clothing wear.
CSP or RKM against the buyer’s specBelow 95% of target on any lot, the playbook says to stop, retest and find the root cause, starting with TPI and the twist multiplier.
End breakage per 1,000 spindle hours, by countIn the playbook’s reading, a sustained rise points to humidity, ring traveller wear or fibre length.
Mixing-recipe adherenceThe playbook’s target is 100% sign-off, with every deviation logged with its reason. It is what lets a lot be traced to its bales later.

What the agent works from

Records it reads

  • Mixing sheet
  • Count change log
  • USTER/HVI report
  • Lot card
  • Daily production report
  • Buyer yarn spec

In your ERP

Reads Odoo production orders (order, product, quantity, status) and stock transfers (transfer, partner, status, scheduled date, source document). Drafts an Odoo order’s planned start or assignee, or a transfer’s note or source document, for an admin to approve or decline. Spinning batches come from your files. The demo shows which of these your Odoo holds.

One ERP connection serves the whole factory: SAP Business One, SAP S/4HANA, Odoo, Oracle NetSuite, Microsoft Dynamics 365, WFX Cloud ERP or Datatex NOW. This agent reads only the records named above; we check yours on the call.

In your tools

Reads a production or count change sheet in Google Sheets when you ask. Prepares a count change as a new row in that sheet, and drafts a USTER hold or shift handover as a WhatsApp Business or Slack message, or a Gmail email to the QA head. Each waits for an admin to approve or decline it, and none of them runs unless approved.

Tools named today: Gmail, Outlook, Google Sheets, Slack and WhatsApp Business.

Never made up

  • Mixing percentages, bale selections or cotton fibre parameters
  • Count, TPI, draft or speed settings
  • USTER and HVI values: U%, IPI, hairiness, CSP, RKM
  • Lot numbers or production quantities

If it is not in your connected data, the agent says so.

Belongs to another department

What the Spinning playbook covers

  • SOP: a count change

    PPC issues the count change order and the spinning master schedules it. The team cleans the machines from blow room to ring frame, sets top-arm pressure, draft, break draft and TPI for the new count, spins a trial cone, USTER-tests it and signs off. The playbook’s line: a count change without a trial cone and a USTER pass “is not a count change; it is a future quality claim.”

  • Decision rule: U% drifts above target

    Check three causes in this order: the drawing draft mis-set after a count change, card cylinder loading above target, then a cotton lot with more trash than its HVI showed. Do not ship cones above the buyer’s U% spec. The playbook adds that an out-of-spec U% usually has two causes, one in carding and one at the ring frame.

  • KPI: cone weight CV%

    The playbook targets a cone weight CV of 1% or less, on a typical 1.89 kg cone held within ±1% and weighed every shift. Above 2%, it points to winder calibration. If most cones are right but about one in fifty is 2% short, it reads that as the auto-cone weighing scale drifting, not a fibre problem.

  • Edge case: a blend the mill has not run

    When a buyer asks for a blend the mill has not run before, such as 60/40 cotton-polyester, the playbook says to pilot it on one or two ring frames, run a full USTER on the trial, get the buyer’s approval on the trial cones, and only then scale up.

Written as general textile practice and reviewed by four independent AI models. Not yet signed off by a human subject-matter expert. Upload your own SOPs and standards, and every answer shows which source it used.

Ten questions it ships with

The template’s starter questions. Your team can edit them, or ask in its own words.

  • Approved mixing recipe for a lot

    What is the approved cotton mixing recipe for this lot, and how does the mix actually running compare with it?

  • Count-wise production this shift

    Show count-wise production and efficiency for the last shift, and tell me which counts fell below target and by how much.

  • USTER results against the limits

    What do the USTER/HVI results for this lot show for U%, IPI and hairiness, and how do they compare with the required limits?

  • Trace a lot back to its mixing

    Trace this yarn lot back to the cotton mixing and bale set it came from, and show the mixing sheet behind it.

  • Why count strength moved

    Count strength has moved between these two lots. Compare their mixing, machine settings and test results and tell me what differs.

  • Shift handover summary

    Prepare a shift handover from the production, count-change and quality logs: what ran, what changed, what is pending, and what needs watching.

  • Count changes logged this week

    Which count changes were logged this week, on which frames, and how much production time did each change cost?

  • Machine-wise efficiency ranking

    Rank the ring frames by efficiency for the last shift and show the stoppage reasons logged against the lowest three.

  • Lots pending quality clearance

    Which yarn lots are produced but still pending quality clearance, and what test is each waiting on?

  • Waste percentage by process

    Show the waste percentage recorded at each process stage for the current mixing, and compare it with the norm on file.

Spinning: questions before a demo

Can it read our USTER and HVI reports?

Yes, when the export has text in it. Upload the USTER evenness report, the strength test sheet and the HVI report as a PDF with text, an Excel or a CSV file, up to 10 MB each, with the buyer’s yarn spec. The agent reads U%, CVm, IPI and hairiness from the evenness report, CSP or RKM from the strength sheet, and micronaire, strength and trash from the HVI report, by lot, frame and shift where the report records them. It sets them against the spec and cites the files. It does not connect to the tester. A photographed printout has no text to read, so export the report instead.

Our production register is on paper. Can the agent still help?

Only with what is connected. The agent cannot read a register that stays on the floor. Once the shift figures are typed into an Excel or CSV file you upload, it totals the kilos of each count or frame you name from the rows and reads each frame’s efficiency as entered, citing the rows; keep them on the first sheet, up to 5,000 rows. From a connected Google Sheet it reads the rows and cites them. Meanwhile, start with the SOPs, the USTER exports and any mixing sheets you already keep in Excel.

Does it connect to our ring frames, autoconers or humidification plant?

No. Mavick does not connect to machines, spindle data systems or the humidification plant, and it does nothing between questions. Machine figures reach it only from a file you upload or a connected Google Sheet; from Odoo it reads production orders (order, product, quantity, status), not machine data. Spinning batch records from the ERP do not reach it either: upload them as an Excel or CSV export. If a reading was never recorded, it says so instead of guessing.

Can it pick the cotton mix for a new count?

No. It does not choose bales, plan a laydown or predict yarn quality from HVI values: the mixing master decides. It finds the approved mixing recipe for a count and buyer, sets the mix that ran beside it when both are recorded, and works out the average, lowest and highest of a fibre value from an uploaded HVI table. It also quotes the playbook, such as checking the comber noil percentage before a recipe is signed off.

Can the agent change a count or TPI setting in our ERP?

No. Machine settings, mixing recipes, USTER values, lot numbers and production quantities are never written to any ERP. The ERP changes that fit spinning are narrow: in Odoo, a new planned start for a production order or who it is assigned to, or a note or source document on a stock transfer. A department admin approves or declines the draft, and Odoo changes only if approved. No other ERP is written from spinning. For anything else it drafts a message or a sheet row, which also waits for an admin.

Will the spinning agent see our cotton purchase prices?

Not from Sourcing & Procurement. Cotton rates stay in its files unless someone shares them across the factory; the spinning agent sees your mixing sheets, USTER reports and shift rows. From the ERP it reads only Odoo production orders and stock transfers, never purchase orders. Asked about cotton buying, it names Sourcing & Procurement and fetches nothing. It does read files uploaded to spinning, such as the bale HVI report, so keep price columns out of them.