A manual output log asks an operator to write down, once an hour, how many pieces were sewn and whether anything stopped the machine; the operator is busy sewing, so the number written down is usually a fair estimate rather than an exact count taken at the moment it happened. Machine data comes from a sensor on the machine itself, counting stitches or cycles and recording stop time automatically, without asking the operator to stop and write anything down.
Delta Garments' own sewing line for Order A currently runs on a manual hourly log; this lesson compares what that log shows against what the machines themselves would report, so a factory or buyer can judge how much the two actually differ.
You need: what an MES actually connects that separate paper systems do not (Lesson 2.1), useful preparation but not required.
By the end of this lesson you can:
Not covered here: choosing which IoT sensor to install (Lesson 2.3), or calculating a connected machine's own payback period (Lesson 2.4). This lesson only covers reading and comparing the data itself.
| Term | Meaning |
|---|---|
| Machine data | Production facts, such as stitch count or stop time, captured automatically by a sensor on the machine itself, without a person writing anything down. |
| Manual hourly log | A paper or simple digital record an operator fills in by hand, usually once an hour, stating pieces sewn and any stoppage. |
| Estimate gap | The difference between a manual log's own reported figure and what machine data actually recorded for the same period. |
| Stitch count | The number of stitches a sewing machine has completed, one of the raw facts a machine-mounted sensor can count directly. |
| Stop time | The total time a machine spent not sewing during a period, whether from a planned pause or an unplanned stoppage. |
| Cycle time | The time the slowest operator on a line actually takes to complete one piece at their own station, which sets the pace every other operator must match. |
A sensor mounted on a machine counts what the machine actually completed and records exactly when it stopped, with no memory or rounding involved. An operator filling in an hourly log is doing so between sewing pieces, often from memory of the last hour, and naturally rounds a number rather than counting exactly; the manual log is not dishonest, it is simply an estimate made under time pressure, and machine data is the more exact of the two records.
| What can differ | The shapes you meet | Why it matters to you |
|---|---|---|
| How busy the operator is | An operator on a fast-moving export order like Order A, working to a tight cycle time, has little spare attention to log figures precisely; a slower domestic run gives more time to note things accurately. | The busier the line, the wider the estimate gap between the manual log and machine data tends to be, because accurate logging competes directly with sewing time. |
| What is being measured | Counting pieces at the end of a bundle is fairly easy to estimate closely; recording the exact minute a short, repeated micro-stoppage occurred is much harder to do from memory. | A manual log is more reliable for simple totals than for the timing and frequency of short stoppages, which is exactly where machine data adds the most accuracy. |
| Business model | A Make to Order export shipment like Order A has one fixed ship date the whole line depends on; a Make to Stock domestic run can tolerate a wider margin of error in daily output tracking. | An estimate gap that would not matter on a flexible domestic run can matter directly on a fixed-date order where every hour of true output counts toward hitting the ship date. |
| How tightly the buyer needs the figure | Northline Apparel, tracking Order A against a fixed 16-week timeline, needs to know the line's true daily output, not an operator's rounded estimate, to judge whether the order is genuinely on schedule. | A buyer relying on a manual log's own rounded figures risks believing an order is on track when machine data would show a real shortfall building up unnoticed. |
Delta Garments is producing Order A, 15,000 pieces of the basic T-shirt, for Northline Apparel under Make to Order terms with a fixed 16-week timeline. The sewing line's operators currently fill in a manual hourly log, writing down pieces sewn and any stoppage once an hour, in between sewing.
Karim, Delta Garments' own production manager, wants to check how accurate that manual log actually is, so he compares one hour's own manual entry against what a machine-mounted sensor recorded for the same hour on the line's bottleneck machine.
The worked numberThe manual log overstated output by 6 pieces for that hour and reduced three separate short stoppages, worth 6 minutes of real stop time, to a single vague note; neither error is dishonest, but together they mean Karim's manual records cannot tell him how much of the line's own shortfall against target actually comes from stoppages rather than from slower sewing, which is exactly the distinction machine data provides directly.
A log kept diligently, filled in every hour without fail, still carries the operator's own rounding and memory limits in every entry; consistency in keeping a log is not the same as accuracy in what it records. A factory or buyer that never checks a manual log against machine data for even one sample period has no way of knowing whether the log's own daily totals are close to the truth or drifting steadily in one direction.
An operator filling in an hourly log by hand is doing their best while also sewing, so the number they write down is usually a rounded guess, not an exact count. A sensor on the machine itself counts exactly what happened and exactly when a stoppage occurred, with nothing rounded and nothing forgotten. Comparing one hour's manual entry against the machine's own data shows how far apart the two actually are, which is often more than people expect, especially for short stoppages that are easy to miss when writing from memory.
Karim has just found a 6-piece overstatement and 6 minutes of unrecorded stoppage in one hour's own comparison.
Should Karim start checking machine data on the bottleneck machine for the rest of Order A's run, or continue relying on the manual log alone? Decide before opening the answer.
Start checking machine data on the bottleneck machine. The two facts that decide this are the fixed timeline's own intolerance for an undetected shortfall, and the low cost of checking just one machine rather than the whole line.
1. Order A's fixed 16-week timeline has no slack for a shortfall that accumulates unnoticed, and the one sample hour already showed the manual log both overstating output and understating stop time in the same period. 2. The bottleneck machine is the one that actually sets the line's own daily ceiling, so any inaccuracy there has the largest effect on whether the whole line hits its target, more than the same-sized error on a faster machine would. 3. Checking machine data on one machine is a small, low-cost step, far short of installing a full connected system across the line, so it can start immediately without waiting for a larger investment decision.
Continuing to rely on the manual log alone risks letting the same kind of gap found in one sample hour repeat, unnoticed, across the rest of a fixed-date order that cannot absorb a shortfall discovered too late.
Forty-eight pieces a day is a small number against Order A's own 15,000-piece total, but repeated daily across the order's own production weeks it adds up to a shortfall the manual log alone would never reveal, since every individual hourly entry looks reasonable on its own even while the pattern behind it is not.
Use the T26-C02 MES and machine-data worksheet, "Manual log vs machine data" sheet. For a specific machine and hour, record the manual log's own entry, the machine data for the same period, and the estimate gap between them. Start with Delta Garments' own example above, then add a comparison of your own.
[Download the MES and machine-data worksheet](../../templates/T26-C02-mes-and-machine-data-worksheet.xlsx)
1. Why does a manual hourly log usually differ from machine data for the same period?
2. In Delta Garments' own worked example, what did comparing the manual log against machine data for one hour reveal?
| EN | AR | FR | TR | Meaning |
|---|---|---|---|---|
| Machine data | بيانات الماكينة | Données machine | Makine verisi | Production facts, such as stitch count or stop time, captured automatically by a sensor on the machine itself, without a person writing anything down. |
| Manual hourly log | السجل اليدوي بالساعة | Registre horaire manuel | Manuel saatlik kayıt | A paper or simple digital record an operator fills in by hand, usually once an hour, stating pieces sewn and any stoppage. |
| Estimate gap | فجوة التقدير | Écart d'estimation | Tahmin farkı | The difference between a manual log's own reported figure and what machine data actually recorded for the same period. |
| Stitch count | عدد الغرز | Nombre de points | Dikiş sayısı | The number of stitches a sewing machine has completed, one of the raw facts a machine-mounted sensor can count directly. |
| Stop time | زمن التوقف | Temps d'arrêt | Duruş süresi | The total time a machine spent not sewing during a period, whether from a planned pause or an unplanned stoppage. |
| Cycle time | زمن الدورة | Temps de cycle | Çevrim süresi | The time the slowest operator on a line actually takes to complete one piece at their own station, which sets the pace every other operator must match. |
Next you will use machine data like the kind read in this lesson to decide which IoT sensor is actually worth installing on a specific machine, and which is not. Back to the course map