Key takeaways
A time study is a direct observation of one operator doing one operation, broken into elements, timed cycle by cycle and converted into a standard time.
The output is not "how long it took". It is how long the job should take, at a defined pace, with defined recovery time.
That number drives the routing (run time per piece, setup per order), costing, capacity, line balancing and the staffing a cell needs to hold takt time.
It also feeds the performance factor of OEE, but only after a correction most plants get wrong.
A standard is only as good as the method it was timed against, so it must point at a specific standard work revision.
Most plants run studies on paper, then type the result into the ERP. The raw readings are lost, and nobody can recompute the standard two years later.
Split the sheet into three tables: study, element definitions, individual readings.
One row per study, and the part an auditor reads first.
| Field | What it holds |
|---|---|
| study_ | Unique study number, e.g. TS-2026-0184 |
| part_ | Part or product the study covers |
| operation_ | Operation in the routing, e.g. 030 Press and deburr |
| work_ | Machine, cell or station |
| method_ | Work instruction and revision. Without it the study means nothing |
| operator_ | Who was observed, and their experience level |
| observer_ | Who ran the study, and their qualification |
| study_ | Date, start and end time, shift |
| timing_ | Snapback or continuous |
| rating_ | Which scale, e.g. 100 as standard performance |
| uom_ | Decimal minutes, seconds or TMU. One per plant |
| conditions | Material, tooling, anything unusual that day |
Record the conditions. A study on a new die and a study on a worn one are two different studies, and only this field says which is which.
One row per element per study. Elements are the units you reuse, compare and move between stations.
| Field | What it holds |
|---|---|
| element_ | Sequence within the operation |
| element_ | Verb plus object, e.g. "Load blank into fixture" |
| break_ | The exact sound or sight that ends the element |
| element_ | Repetitive, occasional, machine controlled, or foreign (not part of the method, so it is timed and then kept out of the standard) |
| frequency | Occurrences per cycle, e.g. 1 or 1/20 |
| ratable | Yes for operator paced work, no for machine controlled |
| mean_ | Mean of the valid readings |
| rating_ | The rating used for this element |
| basic_ | Derived: mean of (observed time × rating ÷ 100) across valid cycles |
The break point is the field people skip and the one that ruins comparability. "Until the press bang" and "until the part is clear of the die" are different elements.
One row per element per cycle. This is the evidence, and it is what spreadsheets usually throw away.
| Field | What it holds |
|---|---|
| study_ | Which element of which study |
| cycle_ | 1, 2, 3 and so on |
| watch_ | What the watch showed at the break point |
| observed_ | Elapsed time for this element in this cycle |
| rating | Rating for this cycle, if rated per cycle |
| is_ | True or false. Never delete a reading |
| exclusion_ | Mandatory when is_ |
is_valid plus exclusion_reason is the honesty mechanism of the model. A reading removed without a written reason is a number someone decided you should not see.
The two stopwatch methods store different things, and converting between them works in one direction only.
| Method | What you record | What the table holds |
|---|---|---|
| Snapback | Watch reset to zero at every break point | watch_ |
| Continuous | Watch runs from the start of the study | watch_ |
With continuous timing the observed time is this break point minus the previous one: readings of 0.15, 0.55 and 0.77 give element times of 0.15, 0.40 and 0.22 min.
That matters for audit: every second is accounted for, interruptions included, because the readings must always increase.
Snapback cannot be rebuilt into a timeline, because it never records a cumulative clock and each reset quietly loses a fraction of a second. Time continuously whenever the study has to be auditable, and keep snapback for quick checks where the timeline does not matter.
Five steps, in this order. Each gets its own stored column so the arithmetic can be checked.
The observed time is the raw elapsed time for one element in one cycle. The rating is the observer's judgement of pace against a defined standard performance.
The common scale sets 100 as standard performance, so a rating of 110 means a pace 10% above it. Standard performance is the rate a qualified, motivated worker can hold for a whole shift without over-exertion, and that sentence has to be written into the study or the number means nothing.
Record which scale you used, because more than one is in circulation and they are not interchangeable. A rating of 80 is above standard on one scale and well below it on another.
Basic time = observed time × rating ÷ 100. A rating above 100 raises the observed time, below 100 lowers it.
Apply it cycle by cycle, then average. Rating every reading and averaging the results is not the same calculation as multiplying a mean observed time by an average rating, and only the first one survives a review.
Occasional elements do not happen every cycle, so multiply their basic time by the frequency.
Changing a tote every 20 pieces at 0.500 min contributes 0.500 × 1/20 = 0.025 min per piece.
Allowances are added time for things that are real but are not the work itself.
| Allowance | What it covers |
|---|---|
| Relaxation, personal | Drinks, washroom, personal needs |
| Relaxation, fatigue | Recovery from effort, posture, heat, noise, attention |
| Contingency | Small irregular unavoidable work or delay, too short to time |
| Policy or special | Added by agreement, not by measurement. Keep it in its own column and outside the measured standard time |
Allowance percentages are set by each plant, not by this page. The relaxation allowance tables that circulate in work study textbooks are illustrative examples, not an issued standard, and no body certifies the numbers in them.
Treat any published table as the opening position for a local agreement. The values you apply are your own, and they must be agreed, dated and documented.
The percentages below are example inputs only, not standards.
Standard time = total basic time × (1 + allowance fraction). Store the allowance percentage next to the result, never folded into it.
Check what the percentage is a percentage of. The formula above reads 14% as 14% of basic time, but many agreements express rest as a share of total working time instead.
On that second reading the divisor changes: standard time = basic time ÷ (1 minus 0.14), which turns 0.8095 min into 0.9413 min rather than 0.9228 min. Store the base in its own field beside the percentage, because the two readings differ by about 2% on every piece.
One press operation, four elements, decimal minutes. This plant has agreed 12% relaxation and 2% contingency, 14% in total.
| Element | Observed × rating | Basic time (min) |
|---|---|---|
| 1. Load blank (repetitive) | 0.150 × 95 | 0.1425 |
| 2. Press cycle (machine) | 0.400, not rated | 0.4000 |
| 3. Unload and deburr (repetitive) | 0.220 × 110 | 0.2420 |
| 4. Change tote, 1/20 (occasional) | 0.500 × 100, ÷ 20 | 0.0250 |
| Total basic time | 0.8095 |
Check element 1: 0.150 × 0.95 = 0.1425. Check element 3: 0.220 × 1.10 = 0.2420.
Now the allowances. 0.8095 × 1.14 = 0.9228 min, which is 55.4 seconds per piece, or 65 pieces per hour.
Many plants apply relaxation allowance only to the manual basic time, because the operator is not working during the machine element.
Manual basic time here is 0.1425 + 0.2420 + 0.0250 = 0.4095 min.
Then 0.4095 × 1.14 = 0.4668, plus the machine time 0.4000, gives 0.8668 min: 52.0 seconds and 69 pieces per hour.
Two methods, 65 and 69 pieces per hour, and they are not equally defensible. Relaxation allowance pays for recovery from effort, so putting it on time the operator spends watching a press is a convention of convenience rather than a rest requirement.
Write down which one your plant uses, because mixing them makes work centres impossible to compare. If the operator is genuinely idle during the machine element, that unoccupied time belongs in its own column, not inside a relaxation percentage.
Rating is the only step in the chain that is not a measurement. Two trained observers watching the same operator will not always write the same number.
A rating corrects pace, never method. If the operator walks three steps the layout does not need, rating at 100 prices those steps into the standard for as long as the standard lives.
So store it separately rather than hiding it, and a reviewer can accept the timings while challenging only the judgement.
Two controls cost nothing: rate per element per cycle rather than once for the study, and have two observers rate the same recorded cycles each quarter.
Machine controlled elements must never be rated. The press takes 0.400 min whoever stands in front of it, so a rating of 95 would cut the basic time to 0.380 min and delete 0.020 min of real machine time.
A rating of 110 does the opposite and invents 0.040 min that nobody spent. Either way the error is silent, because the machine element looks like every other row.
Set ratable = no so the system refuses any rating but 100, and apply the same rule to conveyor, oven and curing paced elements.
The honest answer is that variability decides, not a round number. The formula for a sample size at a stated confidence and precision is:
n = ( z × s ÷ (a × mean) )²
Here z is the confidence factor (1.96 for 95% confidence), s the sample standard deviation, a the relative precision (0.05 means plus or minus 5% of the mean, not 0.05 min) and mean the mean observed time.
Three assumptions ride inside it. The readings must be independent draws from one roughly normal population, the normal z is used even though s comes from a small pilot, and the answer sizes one element, not the study.
So run it element by element and take the largest answer. Then recompute s once the extra cycles are in, because a ten reading pilot can understate the requirement badly.
Ten readings of element 3, unload and deburr, in decimal minutes: 0.21, 0.23, 0.20, 0.22, 0.24, 0.21, 0.25, 0.22, 0.20, 0.22.
They sum to 2.20, so the mean is 0.220 min, and the squared deviations sum to 0.0024.
The sample standard deviation is the square root of 0.0024 ÷ 9, which is 0.0163 min.
Now the formula: 1.96 × 0.0163 = 0.03195, and 0.05 × 0.220 = 0.01100.
0.03195 ÷ 0.01100 = 2.905, and 2.905² = 8.4, so 9 cycles. The ten already taken are enough.
Note how hard this bites. Double the standard deviation and the required cycles quadruple, from 8.4 to 33.8, so 34 cycles.
Many plants never run this calculation. They use a published table saying something like "cycle under 0.10 min, take 40 readings; cycle over 2 min, take 10".
Those tables are a shortcut used in real factories every day, and also a guess about your variability made by someone who never saw your line. Take the table's number, then compute s and add cycles only if the formula says you must.
Store all three statistics per element. They answer different questions, and the gap between them is a signal.
| Statistic | What it tells you |
|---|---|
| Mean | The value that goes into the standard. Sensitive to one bad reading |
| Median | The typical cycle. Barely moves when one reading is extreme |
| Standard deviation | How consistent the method is, and it drives the sample size |
When mean and median separate, something happened that is not the job. Take the same ten readings, but cycle 7 now reads 0.62 min because the operator waited for a missing tote.
The median is still 0.220 min. The mean jumps to 2.57 ÷ 10 = 0.257 min, which is 16.8% higher from one reading.
The standard deviation jumps to 0.128 min, and the sample size becomes (1.96 × 0.128) ÷ (0.05 × 0.257) = 19.53, squared = 381.2, so 382 cycles.
That is the argument for exclusions. One unhandled interruption turned a 9 cycle study into a 382 cycle study, and would have padded every piece for years.
Do not go and time 382 cycles. The sample is no longer one population, so the formula is sizing mixed data, and 382 is a flag on your sheet rather than a work order for the observer.
"Mean 0.220 min, 10 readings" and "mean 0.220 min, 9 valid, 1 excluded, reason recorded" are not the same study.
A standard time and an ideal cycle time are different numbers with different jobs, and plants routinely use one where the other belongs.
| Number | Contains | Use it for |
|---|---|---|
| Standard time | Rating and allowances | Routings, costing, staffing, capacity |
| Ideal cycle time | Neither. Fastest sustainable time per piece | The OEE performance factor |
Our guide to cycle time defines the actual and ideal versions. The trap appears when the padded standard is loaded into OEE as the benchmark.
A work centre runs 405 minutes and produces 380 pieces.
On the standard time of 0.9228 min: 380 × 0.9228 = 350.7 min earned, and 350.7 ÷ 405 = 86.6% performance.
On the unpadded basic time of 0.8095 min: 380 × 0.8095 = 307.6 min, and 307.6 ÷ 405 = 76.0% performance.
Basic time is still not the ideal cycle time. It is the time at standard rating, while the OEE benchmark is the fastest sustainable time, so the honest performance figure is lower again.
The padded benchmark hides 10.6 percentage points of speed loss, roughly 43 minutes of output per shift that nobody is looking for.
Keep both fields: standard time for money and people, ideal cycle time for OEE performance. The same warning applies to production efficiency, where a loose standard gives a flattering percentage and no action.
Stopwatch time study is one of four ways to get a time, and each is right somewhere.
| Method | What it gives | When it fits |
|---|---|---|
| Time study | Element times from your own operation, with rating and allowances | Existing repetitive work, when you need a defensible standard now |
| PMTS (for example MTM, MOST) | Times from licensed motion and activity tables, set at a defined performance level, so no rating is applied. Allowances still are | Setting a time before the job exists, and consistency across sites. Needs a trained and certified analyst |
| Work sampling | Proportion of time spent in each activity, from many random observations | Allowance and utilisation studies, long or irregular work |
| Machine measured cycle | Actual cycle times and stops, every cycle, with no observer | Machine paced work, and checking a standard against reality |
These are complementary, not rivals. PMTS or time study sets the standard, and machine data collection checks weekly whether it still describes reality.
Someone will eventually ask why a part is costed at 0.92 min and who approved it. Never update a standard in place: insert a new version and close the old one.
| Field | What it holds |
|---|---|
| standard_ | Part plus operation plus version |
| version / status | Draft, Approved, Superseded, Retired |
| effective_ | The window this version priced and planned |
| source_ | The study behind it, so the readings stay reachable |
| method_ | The work instruction revision it was timed against |
| basic_ | Before allowances |
| allowance_ | Split by type, never folded into basic time |
| standard_ | Derived, not typed |
| approved_ | Name and date, on the record |
| change_ | Method change, new tooling, restudy, error correction |
| review_ | When the standard must be re-checked |
Two rules make this work. A method_rev change forces a new standard version, and a standard past its review_due belongs on a report rather than being silently trusted.
The same versioning applies to times carried on production orders, covered in our production work order data model.
Fabrico is not a time study or work measurement tool. It holds no observation sheets, calculates no ratings or allowances, and produces no standard time.
Fabrico is an OEE platform with a full CMMS. It measures actual cycle times, short stops and downtime through PLC connectivity, IoT sensors and computer vision cameras, the options compared in our guide to machine monitoring systems.
That is the check your standard needs, and the comparison stays in your hands. The field Fabrico uses as the OEE benchmark is the ideal cycle time, so load that one and keep the padded standard out of it.
Then set your calculated standard beside the measured cycle times yourself, shift after shift. When the machine has quietly been beating the standard for a month, the standard has drifted.
Order data, including the product and its ideal cycle time, can be imported from your ERP, so the OEE benchmark is the one your engineers approved rather than a number retyped by hand.
On the maintenance side your team creates work orders, runs preventive plans and records spare parts used per work order from web or mobile. The AI assistant answers questions about a machine's history in plain language.
Want to see how your approved standards compare with what your machines actually do? Book a 30 minute demo with a Fabrico consultant, no commitment, or contact us with your questions.
A study header (study_id, part_no, operation_no, work centre, operator, observer, date, method revision, timing method, rating scale), an element table (element_no, description, break point, element type, frequency, rating, basic time) and a readings table with one row per element per cycle.
Keep the raw readings with an is_valid flag and an exclusion reason, because a study you cannot recompute cannot be audited.
Multiply the mean observed time by the rating divided by 100 to get basic time, multiply occasional elements by their frequency per cycle, add the basic times, then multiply the total by 1 plus the allowance fraction.
In the example above, 0.8095 min of basic time with 14% allowances gives 0.8095 × 1.14 = 0.9228 min per piece.
Use n = (z × s ÷ (a × mean))², where z is 1.96 for 95% confidence and a is your precision, such as 0.05 for plus or minus 5%.
Many plants use rule-of-thumb tables based on cycle length instead, which is a workable shortcut but a guess about your variability rather than a measurement of it.
No. A press, oven or conveyor runs at its own pace, so rating it would add or remove time that no operator controls.
No, not without removing the allowances and the rating effect, because a standard time is deliberately padded for recovery and contingencies.
Using it as the OEE benchmark makes the performance factor look better than reality, which is exactly where speed loss hides.
Zakažite sastanak KSNUMKS-to-KSNUMKS sa našim stručnjacima ili se direktno upišite u naš besplatni plan.
Nije potrebna kreditna kartica!