Book a WhatsApp demo

Smart IE: Digital Industrial Engineering in a Garment Factory

S
Santosh Rijal
· November 18, 2026 · 11 min read Industrial Engineering

Quick answer. “Smart IE” is industrial engineering run on data captured on the sewing floor as work happens, rather than on occasional stopwatch studies. One example is an observed SMV taken from scan timestamps:

Observed SMV = 60 ÷ observed pieces per hour

Illustrative example: an operation has a standard SMV of 1.10 minutes. Scans show operators doing it at 48 pieces an hour. Observed SMV = 60 ÷ 48 = 1.25 minutes, 0.15 minutes above the standard. The gap is a question for the IE, not an answer: method, skill, waiting or a wrong standard.

Traditional garment IE runs on two kinds of data: a time study done when a style is set up, and output counted by hand during the day. Both are slow. A time study is a snapshot of one operator on one day; a tally sheet arrives hours after the problem it records. This guide looks at what changes when the same IE questions are answered from data the floor produces continuously, what the published research actually shows, and what that data cannot do. The formulas themselves do not change; they are all collected in our IE formula reference.

What is digital industrial engineering in the garment industry?

Digital industrial engineering means the IE works from production data captured on the floor as the work happens, by scans, sensors or tablets, instead of from occasional stopwatch studies and hand-written tallies. The formulas stay the same. What changes is how fresh, complete and per-operator the inputs are, and how quickly a problem shows up.

Textile Learner's piece on smart factories describes industrial engineering as "the field of study that is concerned with the design and optimization of complex systems", and lists the IE's work in a smart factory as time and motion study, method improvement, line balancing, capacity planning and workflow design, with the added job of making sure digital tools fit the way the floor actually works (Elma, Textile Learner, 2025). That is the useful framing: the data is new, the discipline is not.

What changes when IE data comes from the floor

The problem with manual data was described plainly in an Apparel Resources (StitchWorld) piece back in 2011: "Manual data collection is also laborious and error prone." The same piece estimated that collecting individual production figures from a 30-machine sewing line may take 15 to 20 minutes, and argued that collecting performance data directly from the operator turns it into information in real time (Apparel Resources, 2011). Here is what that means for each part of the IE's job:

IE question With stopwatch and tally sheets With real-time floor data
How long does this operation take? Standard SMV from a time study of a few cycles, rarely repeated Observed cycle time from bundle scan timestamps, compared with the standard SMV
Who should do this work? Supervisor's memory of who is good at what Skill records built from each operator's speed and defect history per operation
Where is the bottleneck? Walk the line and look for piles of bundles Work piling up at one operation while the next starves, visible as it builds
Who is idle? Seen only when someone walks past Operators with no active work, matched against queued work on their machine type
What is stuck? Found at lot close, when a bundle is missing Bundles that have not moved for longer than expected, flagged during the day
Is quality slipping? DHU totalled at day end Defects recorded per check, per operator and operation, through the day

Standard SMV vs observed cycle time

Prabir Jana made the IE case for observed times in 2010: "Cycle time is more important than standard time as it gives an accurate indication of what can be achieved", and "for balancing purposes, it is much better to use achieved cycle times than standard times" (Jana, Apparel Resources, 2010). The catch has always been collecting achieved cycle times for every operation without a second person with a stopwatch. When each bundle is scanned at the start and end of an operation, the timestamps give that cycle time as a by-product.

What the research shows

Three studies are worth reading in full, because they show both the gains and how they were measured:

These are single case studies in particular factories, not industry benchmarks. What they share is the mechanism: fresher data about where time is lost, followed by an engineer acting on it.

Does real-time scan data replace the time study?

No. Scan timestamps show how long work actually took, waiting and interruptions included, which is an observed cycle time. A standard time needs a defined method, a performance rating and allowances, which only a time study sets. Scan data is best used to check standards against reality and to see where the line is losing time.

An observed SMV that is well above the standard can mean four different things: a slow method, an operator still learning, a line that kept her waiting, or a standard that was wrong to begin with. Scan data narrows the search, but deciding which one it is still means going to the machine. The rating and allowance method is in our SMV and SAM calculation guide.

What Scan ERP does for IE today

Scan ERP is built around QR bundle scans, so most of what it offers an IE comes from those scans and from biometric attendance. In IE terms:

What it does not do (yet)

Where does a human IE still matter?

In three places data cannot cover: improving the method of an operation, setting the standard time a new style is costed and paid on, and deciding how to rebalance a line, which means weighing operator skills, machines and the order at hand. Real-time data tells the IE where to look; the IE still decides what to change.

What an IE does all day, and which parts of it software can take over, is covered in our guide to the industrial engineer in a garment factory.

Sources

See Your Floor's Real Cycle Times

Scan ERP turns QR bundle scans into observed SMVs, a skill matrix, bottleneck and idle alerts, and piece-rate pay, with worked minutes from ZKTeco punches. Ask the founder on WhatsApp and see it on a real line.

Ask on WhatsApp Request a Free Demo

Citing this reference

Digital (“smart”) industrial engineering uses production data captured on the floor as work happens. Observed SMV = 60 ÷ observed pieces per hour; it is an observed cycle time, waiting included, and does not replace a rated time study. Use it to check standards and find where time is lost.

Copy this attribution

Scan ERP — Smart IE: Digital Industrial Engineering in a Garment Factory. https://scanerp.pro/blog/smart-ie-garment-factory-scan-data.html

Free to reproduce with attribution. Last reviewed 18 November 2026.