<< Click to display table of contents >> Navigation: TiCon EAWS > EAWS Analysis > EAWS Structure > Q x F |
It is possible to show or hide the columns Quantity and Frequency (Q x F) using the Structure ribbon.
Please note: |
The number of real actions must not be entered in the "Quantity" column! |
The columns Quantity and Frequency (as well as the associated Total Duration column) are hidden by default, since only the time and ergonomic boundary conditions are needed for the evaluation. Both columns behave differently, and this may easily confuse inexperienced users.
If the workflow, however, shall be evaluated typically according to MTM in the sense of process steps (elements), column Q x F can be used for this purpose.
The following definition applies according to UAS® training materials:
Number |
How many? |
e.g. nuts that are screwed down, nails that are driven home, number of meters one way each |
Frequency |
How often? |
e.g. revolutions/cycles per nut, blows per nail, frequency of the same way |
According to the UAS® control value, the analysis does not need to agree with the flow.
An analysis such as the following can therefore be interpreted in different ways.
Code |
Q x F |
---|---|
KA |
15 * 2 |
AA1 |
1 * 1.0 |
a)Walk 30 meters and place part >> Load type: Carrying
b)Walk 15 meters, place part and walk back 15 meters >> Load type: Repositioning
A similar problem also arises when using the factors, since it is not clear whether these are distances (KA) or quantities.
Example:
a)15 x 1 KA as load type Repositioning >> Are there 15 repositioning actions or 15 m and therefore, one repositioning action
b)20 x 1 KA as load type Carrying >> In this case, 20 is obviously the distance
Hints on how the number should not be used and how it should be used
•not to determine distances
•not to determine frequencies when forces are applied (Sections 2 and 4) and not either when handling loads. The frequencies must be entered in the respective fields (dynamic actions for forces and number for load handling actions).
•however, it is used to determine the duration to detect static actions:
While frequency behaves just the other way around:
•to determine repetitions
•to determine distances
•not to determine static time portions.