MTM-UAS
MTM-UAS is a time standard from the MTM organization that is used extensively in Europe. The detail level in the standard is mid-level; it is most applicable to process that last from one to five minutes.
Formal training on how to use this time standard is highly recommended. Courses and textbooks are available from the MTM organization.
MTM-UAS has a basic set of codes and a more advanced set that is referred to as the Standard Data Additions. MTM-UAS codes are included by default.
MTM-UAS Element Types
MTM-UAS has three element types
P (Process Time): Enter a quantity of TMU's in the Left Code field, or enter a time value followed by a dash and the time unit.
R (Retrieval): This is what you will use for all standard UAS Codes
L (Literal): This tells the calculator to ignore the line because it represents a comment
The Internal field for an element allows you to specify another element that this particular element is performed concurrently with. In this version, the Internal field is not implemented for MTM-UAS.
The Allowance% field allows you to specify an allowance for this specific element line.
MTM-1
MTM-1 is one of the original predetermined time standards. It is the oldest standard that is still in use. Since MTM-1 is a very detailed time standard, it is most often used for processes that are less than one minute in length.
Formal training on how to use this time standard is highly recommended. Courses and textbooks are available from the MTM organization.
MTM-1 Element Types
MTM-1 has two element types:
-
M: for code-based element strings
-
P: for user-specified process times. Simply enter a quantity of TMU's in the Left Code field, or enter a time value followed by a dash and the time unit (e.g. 30 SEC).
Manual codes (Reach, Move, etc.) are case sensitive, especially with reference to Move and Reach In-motion. Because of this, the code letters should always be upper case, and the "m" In-Motion modifier (prefix and suffix) should always be lower case.
Special Codes
MTM-1 has several different element special codes
/, //, \ or ; will cause the entire element line to be ignored (i.e. a comment line)
V or O:
'V' indicates that this element is inside the field of vision of the operator. Otherwise, if this is not specified, or if an 'O' (capital letter O for Outside) is specified, then the application assumes that the element task is Outside the field of vision of the operator.
The setting of this special code for an element is only relevant when that element has BOTH a Left-hand code and a Right-hand code, and the parser is trying to determine how to combine the two times into an overall concurrent task time. The (within/outside) normal vision special code is used by the parser when encountering Reach, Move, and Grasp elements.
D or E:
'D' indicates that this element involves a part that is Difficult to handle. Otherwise, if this is not specified, or if an 'E' (for Easy) is specified, then the application assumes that the part being handled is Easy for the operator.
The setting of this special code for an element is only relevant when that element has BOTH a Left-hand code and a Right-hand code, and the parser is trying to determine how to combine the two times into an overall concurrent task time. The (easy/difficult) to handle special code is used by the parser when encountering Position and Disengage elements.
Reach and Move Location Accuracy
The Reach and Move codes in MTM-1 are defined as being A, B, or C codes, which represent the accuracy at which the Reach or Move is required.
-
A = Reach to an object at a fixed location
-
B = Reach to an object in a variable location
-
C = Reach to an object jumbled with others
Weight with Move
When moving an object with a weight greater than 2 pounds, the time in MTM-1 is increased to allow for the additional effort. To specify the weight of an object with a move, simply append the weight in pounds after the code and use the comma as a separator. For example, to specify a 6-pound object that is moved 18 inches to a fixed location (i.e. code A), you would enter: M18A,6
Vision and Practice
A checkbox in the lower left-hand corner of the spreadsheet indicates whether the operator "Is Practiced." As with the Special Code for "V - Within Normal Vision", the value of this checkbox is used by the parser to determine the total time for an element line that contains BOTH a Right and Left-hand code.
Checking this box means that the entire list of elements is performed by the operator many times a day, and therefore it is to be assumed that the operator has significant practice and skill in performing those tasks.
Simultaneous Motion
The Simultaneous Motions Table in MTM involves the technique for computing the total time of an element that involves movement of both hands concurrently.
According to the MTM Association, when a MOVE-MOVE, MOVE-REACH, REACH-MOVE, or REACH-REACH two-handed element is encountered, then the parser will take the largest of the two times (right and left hand) provided that the tasks can be performed simultaneously. Otherwise, the parser will add 2 TMU's to the longest of the two times.
If any other combination of element codes is encountered between the hands, then the application will EITHER take the LONGEST of the two times (provided that they can be performed concurrently) or ADD the two times (if they cannot be performed concurrently - regardless of the codes appearing in the left and right-hand fields of the element).
Please reference the MTM-1 Simultaneous Motions table for more information on this topic.
MTM-MEK
MTM-MEK is a time standard from the MTM organization that is used extensively in Europe. The detail level in the standard is high-level; it is most applicable to order-oriented production of products with little or no repetition large number of product types and varieties long-cycle or non-cyclic work processes constant changes in the work processes and conditions relatively low degree of routine with limited possibilities of detailed work instructions with the associated result of increased variation in the work method.
Formal training on how to use this time standard is highly recommended. Courses and textbooks are available from the MTM organization.
MTM-MEK has a basic set of codes and a more advanced set that is referred to as the Standard Data Additions. MTM-MEK codes are included by default.
MTM-MEK Element Types
MTM-MEK has four element types
-
R (Retrieval): This is what you will use for all standard MEK Codes
-
P (Process Time): Enter a quantity of TMU's in the Code field, or enter a time value followed by a dash and the time unit.
-
MP (Manual Process): Enter a quantity of TMU's in the Code field, or enter a time value followed by a dash and the time unit.
-
L (Literal): This tells the calculator to ignore the line because it represents a comment
MEK blocks once selected will explode its components in multiple rows. The Internal field for an element allows you to specify another element that this particular element is performed concurrently with. The Allowance% field allows you to specify an allowance for this specific element line.
MTM-B
MTM-B is one of the newer time standards from the MTM organization. It is targeted for processes with long cycle times and for task descriptions for which a LEAN Benchmark is desired (i.e. Comparison of Current State versus Future State).
MTM-B is designed to be a quick and simple key-word based language of work. One difference between MTM-B and the other MTM-based time standards is that MTM-B will report in MU's by default, where the others have a base unit of TMU.
Formal training on how to use this time standard is highly recommended. Courses and textbooks are available from the MTM organization.
To see a list of the MTM-B key words, press F5 (function 5) while the MTM-B standard is selected. After the list is open, keywords can be selected from the list with the mouse.
As the process is described, the editor automatically color-codes keywords and keyword modifiers (quantities of distance or time). This makes it easy to determine if the keyword-code has been recognized. The processing time and corresponding value-add analysis will be computed by the application.
