Industrial Engineer in a Garment Factory: What IE Does — and What Software Now Does For You
I run a 100-machine CMT garment factory in Nepal. When I bought it, I did what every small factory owner does: I looked at what the big export houses have — a proper IE department with an IE head, two or three engineers, and a data entry operator — and then I looked at my margins and closed the spreadsheet.
A full IE department was never going to happen at my size. But the work the IE department does — knowing how long each operation should take, whether operators are hitting targets, where bundles are piling up — that work still needed to happen. Skipping it is why most small factories run at 50% efficiency and don't know it.
This article is the breakdown I wish I had found back then: what an industrial engineer actually does all day in a garment factory, what each piece of that work costs, and — honestly — which parts a software system does automatically now versus which parts still need a human with a stopwatch.
What the IE Department Actually Does
The best public documentation of garment IE work comes from Online Clothing Study's duties breakdown, written by the IE head of a Chennai export house. In a full-size export factory, the IE department is 4–5 distinct roles: an IE head, industrial engineers, junior IEs on the sewing floor, junior IEs in cutting and finishing — and, notably, a dedicated data entry operator whose job is preparing efficiency reports, lost-time reports, and costing documents.
Read that again: the IE department in a traditional garment factory includes a full-time position for typing production data into reports. Keep that in mind for later.
Across that article, Textile Learner's responsibility list, and OCS's "top 5 IE activities", the work condenses into seven core tasks:
- Time study. Stand behind an operator with a stopwatch, time the operation over 10–15 cycles, rate the operator's pace, and derive a standard time.
- SMV / SAM setting. Convert time studies into a Standard Minute Value for every operation of every style, and maintain that SAM database as methods improve.
- Line balancing. Distribute operations across operators so no single station drowns while the next one starves — based on capacity studies and live WIP.
- Target setting. Convert SMVs into hourly and daily targets per operator and per line.
- Efficiency measurement. Compare actual output against standard, per operator, per line, per day — and prepare the daily efficiency reports management runs on.
- Bottleneck detection. Find the operation that limits the whole line's output — through capacity studies and floor observation.
- Skill matrix. Track which operators can do which operations at what efficiency, typically updated every three months.
Also on the IE plate in bigger factories: operation bulletins, machine layout plans, thread consumption charts, operator training programs (15-day basic training for new recruits, with a pass mark above 50/100), and labor costing support for merchandisers. The IE department is frequently the factory's entire MIS/reporting function — OCS notes that in many companies the production reporting system is completely handled by the IE team.
What This Costs
For a 1,000-machine export house, that cost disappears into the overhead line and pays for itself many times over. For a 50–150 machine CMT factory, it's a real decision. Most small factories decide "no" — and then run blind: no measured SMVs, targets set by feel, efficiency unknown, bottlenecks discovered at 5 PM when the output number comes up short.
The result shows up in the industry-wide numbers. Practitioner consensus puts most South Asian factories at 50–60% line efficiency, and capacity planning guides assume 50% as the default. Meanwhile published line-balancing case studies show what measurement unlocks: one documented project lifted a sewing line from 43.96% to 67.64% efficiency using systematic line balancing; another moved a line from 79.68% to 88.31%. Dr. Rajesh Bheda's research puts it bluntly: average apparel manufacturers in the developing world have close to 100% productivity improvement potential.
The Time Study, Honestly Explained
Because everything downstream depends on it, it's worth understanding what a real time study involves — and why no software can skip it.
The engineer times an operation over 10–15 cycles and averages the result. But a fast operator or a slow operator would distort the standard, so the observed time is multiplied by a performance rating. The classic tool is the Westinghouse rating system (from the 1930s, still standard), which scores four factors: skill (−22% to +15%), effort (−17% to +13%), conditions (−7% to +6%), and consistency (−4% to +4%).
Then allowances are added for personal needs, fatigue, and unavoidable delays. The ILO's widely used allowance tables start from 5% personal needs plus a 4–5% base fatigue allowance, with additions for heat, load, and posture — though it's worth knowing the ILO itself has never adopted allowances as a formal standard; they're guidance. Garment factories typically apply 15–20% total allowance.
Worked example (from OCS's SAM guide): observed cycle time 0.5 minutes × 120% performance rating = 0.6 basic minutes. Add 20% allowances → 0.72 SMV. That operation's hourly target is 60 ÷ 0.72 ≈ 83 pieces.
Large factories sometimes replace stopwatch studies with predetermined motion-time systems like GSD — but adoption in most of South Asia is still minimal; the stopwatch remains the tool of record. If you want the full formula walk-through, we've published a separate deep dive: SAM & SMV calculation for garment factories and a step-by-step stopwatch method guide.
What Software Automates: 5 of the 7 Tasks
Here is the honest mapping. I'll use my own system (Scan ERP, which runs my factory) as the example because I can describe exactly what it does rather than what a brochure claims — but the logic applies to any scan-based production tracking system.
The key architectural fact: once every bundle carries a QR code and every operator scans at pick-up and completion, the system has a timestamped record of who did which operation on which pieces on which machine, and how long it took. Everything below falls out of that single data stream.
| IE Task | Traditional Method | What the Software Does |
|---|---|---|
| 2. SMV database | Excel sheet maintained by IE, re-created per style, lost when the IE resigns | SMV, SAM, and piece rate stored once per operation in a style template; reused every time the style repeats |
| 4. Target setting | IE calculates 60 ÷ SMV per operation, writes targets on a whiteboard | Auto-computed from the template (60 ÷ SMV = pieces/hour), shown live on floor TV dashboards; line target derived from the bottleneck operation's SMV |
| 5. Efficiency measurement | Data entry operator types production sheets into Excel; report available next morning | Every scan updates pieces-per-hour per operator in real time; efficiency bonuses calculated automatically when thresholds are crossed |
| 6. Bottleneck detection | Junior IE walks the floor doing capacity studies; problems found in hours | WIP count per operation is live; work piling up at one station is visible the moment it starts (see our WIP tracking guide) |
| 7. Skill matrix | Updated quarterly by the IE from memory and paper records | Built continuously from scan history: the system scores every available job for every operator (experience, speed, machine familiarity) and recommends work accordingly |
And remember the dedicated data entry operator position from the traditional IE department? That role simply stops existing. The reports that person spent all day preparing — daily efficiency, lost time, operator output — are generated as a side effect of operators scanning bundles they were already picking up.
What Software Does NOT Automate: The Other 2 Tasks
This is the part vendors don't put in brochures, so let me say it plainly as someone who runs the system daily.
1. The initial time study still needs a human
Software does not invent SMVs. When a new style arrives with an operation nobody has timed before, someone still stands with a stopwatch (or a phone timer), watches 10–15 cycles, applies a rating, and enters the number into the template. In my factory that's a supervisor-level job that takes an hour or two per new style — not a full-time department — but it is real work and it requires judgment. Garbage SMV in, garbage targets out.
2. Line balancing decisions still need a human
The system will show you — in real time — that bundles are piling up at collar attach while the next station starves. What it will not do is physically move a machine, retrain an operator, or decide that operator 14 should shift from overlock to flatlock for the afternoon. The data arrives instantly; the decision and the action are still the supervisor's. Software compressed the detection time from hours to seconds. The fixing time is unchanged — it's a management skill.
Honest summary: a scan-based system converts the IE department from "3–4 salaried people, one of whom types data all day" into "a few hours of supervisor time per new style, plus dashboards." It does not convert it into zero. Factories that expect software to think for them are disappointed; factories that expect it to measure for them are not.
How This Runs in My Factory
A concrete picture from Trishakti Apparel, my CMT factory in Gaindakot, Nepal, where Scan ERP has tracked over 1,400,000 pieces:
- When a new style comes in, we time the new operations and build the template once: operation sequence, machine type, SMV, and piece rate per operation.
- The system generates the work pool and QR bundle labels from that template. Targets appear on the floor TV automatically — no whiteboard.
- Operators scan bundles in and out. Their pieces-per-hour, earnings, and efficiency update with every scan. Efficiency bonuses are computed by rule, not by argument at the pay table.
- When WIP stacks up anywhere, the dashboard shows it while it's happening. My supervisor rebalances in minutes, not the next morning.
- The skill data accumulates by itself. When work is assigned, the system already knows who has done that operation before and how fast.
What I did not hire: an IE head, junior IEs, or a data entry operator. What I still do: time studies on new operations, and the human judgment calls the data points to.
The Decision Framework for Factory Owners
| Factory Size | Sensible IE Setup |
|---|---|
| Under 100 machines | No IE staff. Scan-based tracking + a supervisor trained to do stopwatch time studies on new styles. |
| 100–300 machines | One IE (or a strong production supervisor with IE training) + software. The IE spends time on method improvement and line balancing, not report preparation. |
| 300+ machines / export house | Full IE department — but software still removes the data-collection and reporting layer so engineers do engineering, not typing. |
The wrong answer at any size is the common one: no measurement at all. If your targets come from feel and your efficiency number is a guess, you are statistically likely to be running near 50% — and leaving the equivalent of an entire second factory's output on the table.
Scan ERP by Country
Run IE-Grade Measurement Without an IE Department
Scan ERP gives you SMV-based targets, live operator efficiency, automatic bottleneck alerts, and a self-building skill matrix — from the QR scans your operators already do. Built and tested in a working CMT factory.
Request a Free DemoOne question to leave with: if I asked you right now what your line efficiency was yesterday — the actual number, not the feeling — could you answer?
Santosh Rijal is the founder of Scan ERP, a garment manufacturing ERP system designed for factory floor operations. He works directly with sewing lines, cutting rooms, and production supervisors across Nepal's garment manufacturing sector.