Paste this where you want the calculator to appear. It works on any site — WordPress, Squarespace, Webflow, Ghost or plain HTML — and needs no JavaScript of yours. It carries a link back here, which is the only thing we ask for it.
The point is not saving the stopwatch. It is costing two proposed methods before either exists.
Synthetic SMV
—min
Standard minute value built from motion elements
Motion Build-up
Total TMU
—TMU
GET Motions
—TMU
PUT Motions
—TMU
Manual Time
—min
Basic Time
—min
Output at Standard
—pcs/h
The linear TMU model is a simplification of the MTM-2 data card, which is a stepped table by distance class and case — it tracks the card well across the middle of the range and diverges at the extremes, so short precise motions and long reaches both deserve the real table. Case selection matters more than distance in any event: a GET requiring careful grasp is worth two or three times a simple one, and choosing cases correctly is what MTM-2 training is for. Manual and machine time are added here as though sequential; where the operator handles the next piece while the machine runs, the overlap must be deducted separately.
Using this calculator
About the Synthetic SMV Builder from MTM-2 Motion Elements
The formula
This is the expression the tool evaluates. Every term is named underneath, with the unit it must be supplied in.
Each input feeds the expression evaluated in the browser; the symbol table below names every term and its unit.
Symbols used above
Symbol
Stands for
Unit
getMotions
GET Motions
no.
putMotions
PUT Motions
no.
averageDistance
Average Reach Distance
cm
otherTmu
Other Elements
TMU
machineTime
Machine-Controlled Time
min
getBase
GET Base
TMU
getSlope
GET per cm
TMU/cm
putBase
PUT Base
TMU
putSlope
PUT per cm
TMU/cm
allowance
Total Allowance
%
syntheticSmv
Synthetic SMV
min
totalTmu
Total TMU
TMU
getTmu
GET Motions
TMU
putTmu
PUT Motions
TMU
manualTime
Manual Time
min
basicTime
Basic Time
min
piecesPerHour
Output at Standard
pcs/h
How the result is derived
Step by step, from the values you type to the figure on screen.
The 10 inputs are read from the form on every keystroke: GET Motions, PUT Motions, Average Reach Distance, Other Elements, Machine-Controlled Time, GET Base, GET per cm, PUT Base, PUT per cm and Total Allowance.
Each value is checked against the accepted range in the input table below. A value outside its range stops the calculation rather than producing a misleading figure — the results blank out and a message appears.
The validated values are substituted into the expression above, which resolves Synthetic SMV together with every supporting figure in one pass — no value is carried over from a previous entry.
The supporting outputs — Total TMU, GET Motions, PUT Motions, Manual Time, Basic Time and Output at Standard — come from the same pass, so they always describe the same case as the headline figure.
Results are rounded for display only. The full-precision value is used throughout the chain, so reading a rounded intermediate figure back into the tool by hand can shift the last digit.
What each input means
Where to read each value on the floor, the unit it must be in, and the range the tool accepts.
The headline figure and every supporting value it is built from.
Output
Unit
What it tells you
Synthetic SMV (headline result)
min
Standard minute value built from motion elements
Total TMU
TMU
GET Motions
TMU
PUT Motions
TMU
Manual Time
min
Basic Time
min
Output at Standard
pcs/h
Worked example
Given
GET Motions
12 no.
PUT Motions
10 no.
Average Reach Distance
25 cm
Other Elements
45 TMU
Machine-Controlled Time
0.18 min
GET Base
5.93 TMU
GET per cm
0.2133 TMU/cm
PUT Base
8.67 TMU
PUT per cm
0.2667 TMU/cm
Total Allowance
18 %
The tool loads with this case already solved — the Synthetic SMV shown above is its answer. Change one value and the difference from this baseline is the sensitivity of the result to that variable.
How to use it
Work through the input groups in order — Motion Content and TMU Constants & Allowance. The defaults are a realistic case, so you can change one value at a time and watch what moves.
There is no calculate button. Every figure recalculates as you type or drag, which is what makes this usable for a what-if sweep rather than a single answer.
Read Synthetic SMV in the dark results panel — that is the headline figure, expressed in min.
Check the supporting rows underneath (Total TMU, GET Motions, PUT Motions, Manual Time, Basic Time and Output at Standard) before acting on the headline — they are where an implausible input usually shows itself first.
Reset to defaults returns every field to the reference case, which is the quickest way to check whether a surprising result came from the tool or from an input you had changed earlier.
Where this is used
Process planning — establishing Synthetic SMV before a trial is booked, so machine time and material in Industrial Engineering, Time & Motion are committed against a calculated figure rather than an estimate.
Costing and quotation — Synthetic SMV is an input to the cost sheet, and quoting from a worked number rather than a remembered one is what keeps a margin intact.
Troubleshooting — when the floor result drifts from plan, entering the measured values (starting with GET Motions) shows how much of the gap in Synthetic SMV each variable explains.
Teaching and study — the accepted ranges bracket normal Industrial Engineering, Time & Motion practice, so moving one variable at a time shows the shape of the relationship rather than a single answer.
Assumptions and limits
The linear TMU model is a simplification of the MTM-2 data card, which is a stepped table by distance class and case — it tracks the card well across the middle of the range and diverges at the extremes, so short precise motions and long reaches both deserve the real table. Case selection matters more than distance in any event: a GET requiring careful grasp is worth two or three times a simple one, and choosing cases correctly is what MTM-2 training is for. Manual and machine time are added here as though sequential; where the operator handles the next piece while the machine runs, the overlap must be deducted separately.
Every input is bounded to the range normal practice occupies (GET Motions 0 to 200 no., PUT Motions 0 to 200 no. and Average Reach Distance 2 to 90 cm, and so on for the rest). Those bounds are guard rails against typing errors, not a claim that the formula fails one unit outside them.
The calculation is deterministic: the same inputs always give the same result. It carries no allowance for machine condition, operator skill, ambient conditions or lot-to-lot material variation unless an input above explicitly represents one.
Nothing is sent anywhere. The maths runs in your browser, so the numbers you type never leave the page.
Questions people ask
What do I need to know before using the Synthetic SMV Builder from MTM-2 Motion Elements?
Have these to hand: GET Motions, PUT Motions, Average Reach Distance, Other Elements, Machine-Controlled Time, GET Base, GET per cm, PUT Base, PUT per cm and Total Allowance. With those entered, the tool returns Synthetic SMV immediately.
What exactly is Synthetic SMV?
Standard minute value built from motion elements. It is reported in min. It is derived from GET Motions, PUT Motions, Average Reach Distance, Other Elements, Machine-Controlled Time, GET Base, GET per cm, PUT Base, PUT per cm and Total Allowance, and is the figure the rest of the Industrial Engineering, Time & Motion calculation is built around.
Which units does this calculator expect?
Enter GET Motions in no., PUT Motions in no., Average Reach Distance in cm, Other Elements in TMU, Machine-Controlled Time in min, GET Base in TMU, GET per cm in TMU/cm, PUT Base in TMU, PUT per cm in TMU/cm and Total Allowance in %. Mixing unit systems is the most common cause of a result that looks an order of magnitude wrong — convert before typing, not after reading.
What are the other figures under the main result?
They are the intermediate quantities the calculation passes through: Total TMU, GET Motions, PUT Motions, Manual Time, Basic Time and Output at Standard. They are shown because a headline number nobody can trace is a number nobody trusts — checking them against your own expectation is the fastest way to confirm the inputs were read as you intended.
Can I rely on this for a production decision?
The linear TMU model is a simplification of the MTM-2 data card, which is a stepped table by distance class and case — it tracks the card well across the middle of the range and diverges at the extremes, so short precise motions and long reaches both deserve the real table. Case selection matters more than distance in any event: a GET requiring careful grasp is worth two or three times a simple one, and choosing cases correctly is what MTM-2 training is for. Manual and machine time are added here as though sequential; where the operator handles the next piece while the machine runs, the overlap must be deducted separately. Treat the output as an engineering estimate that narrows the trial window, not as a substitute for the trial.