> For the complete documentation index, see [llms.txt](https://virtualfactory.gitbook.io/vlft/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://virtualfactory.gitbook.io/vlft/tools/mtm.md).

# MTM

### Introduction

The methods time measurement - universal analyzing system (MTM-UAS) is a methodology to clearly measure the processing times of some determined processes made by the operators, both manually and with the aid of some tools. The [MTM](https://en.wikipedia.org/wiki/Methods-time_measurement) methodology has been introduced in the '90s, and the last version is one of the most flexible and fast-to apply techniques, suitable in cases where relatively simple and short actions of the operator are involved. It is based on the classification of the possible operations done by the operator in 7 sections, that are translated in tables with different attributes from each other that returns values of processing TMUs depending on the situation.

MTM-UAS is a widely used method in the industry, especially when speaking about lot production. It is fast to use and quite flexible at the same time but it can have some limitations:

* the focus is on basic operations and not on basic motions like some other versions of the MTM: this lead to a **less accuracy** in the evaluation, an important issue in situations where complex and high-effort actions are required;
* **subactivities are not taken into account**, since the single activity has to be univocally assaigned to a specific section, and the time value is founded basing on the weight of the part handled, the accuracy needed in the movement and its difficulty;
* due to this, it could be necessary to put attenction in the definition of the activities, to avoid the underestimation of the time due to a choice of a very large aggregate activities not providing the due details for the analysis.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://virtualfactory.gitbook.io/vlft/tools/mtm.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.