Skip to main content
GullySystem

Inspection, rework and re-dye records

Inspection, rework and re-dye records what is wrong with a roll, sends the lot back for correction and notes why. A re-dye or re-stenter takes steam, chemicals and machine time, so its cost is booked with its cause. The house then decides whether to charge the customer or absorb it.

Defects, causes and costs per roll

Inspection produces marks on cloth. The entry turns those marks into something the house can count, and ties the correction that follows to a cause. Without a cause, rework is only lost hours with no name on them. Names matter a great deal.

Defects marked on each roll

Each roll carries its own defects, marked where inspectors find them, such as stains, streaks, holes or uneven width. A roll can be graded alone. The lot then shows the count of rolls affected, so one bad roll is not blamed on the lot.

Shade and hand result

Beyond visible defects, the lot is judged on shade against the approved dip and on hand, the feel of the finished cloth. Failing either test sends it back to the machines. The result is written down. It is not remembered.

The cause behind a correction

Each returned lot carries a cause, such as shade low, uneven dyeing or wrong width set. The cause is picked from a list the house agrees. A named cause separates a pattern from a rumour. Picking takes a moment.

Cost charged or absorbed

The chemicals and machine hours spent on a correction are put against the lot. With the cause in front of it, the house decides whether to charge the customer or absorb the cost. The decision is recorded too.

The inspection table and the lot that comes back

Inspection sits at the end of a long route. What it finds lands on people who thought the lot was finished. A fault then travels from the table back to a machine. From there it reaches the bill. Patience runs short.

An inspector marks a streaked roll

Unrolling a roll at the table, an inspector sees a streak and marks it with its position. Other rolls from the same batch are checked next. Marks are entered before the roll is folded away. The order matters here.

The lot fails on shade

Held against the approved dip, one lot is found low in shade. Inspection sends it back with the cause noted. The dye master reads the entry and decides whether a re-dye is enough. That call is quick to make.

A re-dye is booked

Lot 507 goes back for a re-dye with its reason recorded as shade low. A new batch is planned, and the steam, chemicals and machine time of the second run are booked against the lot. The first run stays on record.

Marketing tells the customer

A customer asks why a lot is late. Marketing opens the lot and sees the cause and the correction in progress. The answer is plain. Whether the delay is charged is a matter the owner settles.

Who sees a rejected lot, and why

A rejection touches the table, the laboratory, the machines and the customer desk. Each needs a different part of the entry. Inspection writes it once. The others read the part that concerns them.

For inspection, marking and releasing

Inspectors and dispatch mark defects per roll, release finished lots and prepare the delivery note for the customer. A passing lot is released. A failing lot is sent back with a cause. Both outcomes are recorded.

For the laboratory, reading the cause

The laboratory reads the cause on a returned lot against the recipe and the batch that dyed it. A shade fault may point to the formula or to the run. The dye master decides which.

For supervisors, planning the rework

A machine supervisor sees the returned lot in the list of lots waiting, tagged as a re-dye or a re-stenter. The earlier run is visible. The supervisor loads the correction knowing what went wrong the first time.

For the owner, rework by cause

Re-dye and rework by cause gives the owner a ranked view of what costs the house money. A cause that recurs is worth an investigation. The owner reads cost, not just counts. Money gets a name.

Rework rules to fix before go-live

Rework is where houses lose money quietly. It is also where customers and houses disagree. Settle the rules with the owner, the dye master and inspection before the first lot is graded. Causes and charges are hard to rewrite later.

The list of rework causes

Choose the causes a lot can be sent back for, such as shade low, uneven dyeing, stenter width, hand or stain. A short, clear list gives clean figures. A long list gives noise. Add a cause only when it recurs.

Charging a re-dye or absorbing it

Decide which causes the house absorbs and which it charges to the customer, such as a change of shade request after the dip. The rule sits against the cause, so the bill follows it. Fewer disputes follow.

Defect marks and roll grading

Agree the words inspectors use for defects and the grades a roll can earn. Two inspectors who use different words for the same streak make the figures useless. A shared vocabulary fixes this for good.

Authority to return a lot

Name who may send a lot back, and who may release one that has doubtful marks. If every inspector can reject, planning suffers. If none can, faults reach the customer. Decide before the first lot.

Rework and the features it touches

A rejected lot returns to the route, so rework touches several other features. It reads the recipe and the batch that made the fault. It books chemicals and machine hours for the second run. It also changes what the bill and the statement say. Nothing is retyped here.

  • Machine batches by lot links each roll to its run
  • Lab dip and recipe library gives the formula to compare
  • Dyes, chemicals and utilities books the issues for the redo
  • Process rates and billing charges rework by its cause
  • Delivery note and process statement shows the lot once corrected

Where the rework record stops

This record names defects and causes and carries cost. It does not judge cloth, set the grade standard or decide who is to blame. Whether a defect passes is a call for inspection and the customer. Warranty and compensation terms belong to the owner and an adviser. A house with a few lots a week can mark defects on a sheet. That is enough.

FAQ

Frequently asked questions

Can defects be recorded roll by roll?

Defects are marked per roll, with their position and type. Each lot then shows the count of rolls affected, and which. One faulty roll does not condemn the whole lot unfairly. Each roll is followed.

Can a lot be corrected more than once?

Failing again sends a lot back again. Each correction is booked with its own cause and cost. Earlier runs stay on record. The owner can then see which lots were corrected twice, and for what.

How is re-dye cost worked out?

The chemicals issued and the machine hours used for the second run are put against the lot. Steam, water and power readings can be added where the house books them. Charging it is the house’s decision.

Does it tell us whose fault the rework was?

No. It keeps the cause chosen from the house list and the cost that followed. Whether a cause is the house’s, the customer’s or the grey’s is a judgement for people. The entries support that judgement.

Can the customer see the defect marks?

That depends on what the house sends. The process statement can show the outcome of inspection, and email or messaging can carry status. What is shown, and in what wording, is agreed at set-up with GullySystem staff.

Where it fits

How this feature fits the system.

Textile Processor Management Software: the parts that work with this feature, the trades that use it and the ways to put it in place.

Grey receipt and lot booking

Grey cloth is measured and weighed on arrival against the customer’s delivery note, and damage found at the gate is recorded before it is booked.

Goods Receipt (GRN)

Lab dip and recipe library

An approved shade carries its dyes, auxiliaries and conditions as a recipe, and the same formula is released for each repeat lot.

Bill of Materials

Machine batches by lot

The planner groups lots into jet and range batches by shade and weight and sees which machine is free after the current run.

Production Planning
Talk to us

Tell us what you need.

Tell us what your team does today, where work gets stuck and what you want to change.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements