📖 This is a static documentation page. Open the interactive version with live canvas demos →

Calculation Engine

MPTS calculates time automatically. You never enter a duration — you describe the work through microelements and factors, and the system derives every number from that description. This document explains how the calculation works from bottom to top.

Calculation pipeline

The pipeline flows upward through the hierarchy:

Microelement → Template/Action → Step → Operation → Product

Each level aggregates the results of its children, applies its own parameters (multiplier, batch size, capacity), and passes the total upward. The final product result contains all time components for a complete production model.


Microelement: base time and factors

Every microelement starts with a base time (VAC) — a reference value in internal units (1/1000 of a minute) determined by its group and extension.

Quality factors as multipliers

Each quality factor has a power value for the selected characteristic. The base time is multiplied by each factor's power sequentially:

  • Power = 1 — the factor does not change the time (default)
  • Power > 1 — the factor increases the time (e.g. high degree of control)
  • Power < 1 — the factor decreases the time

Numerical factors as powers

Each numerical factor has a value (what you enter) and a power exponent:

  • If the exponent is 1, the time is simply multiplied by the value
  • If the exponent is not 1, the time is multiplied by value raised to that power

For example, travel distance with an exponent of 0.5 means time grows as the square root of distance — doubling the distance increases time by about 40%, not 100%.

Final microelement time

After all factors are applied, the result is multiplied by the element's multiplier. The output has four time components:

  • Full — total time including all components
  • Human — the portion performed by a person
  • Machine — autonomous equipment operation
  • Part — cycle time contribution (accounting for employment overlap)

Machine time and human share

When a microelement is of the Machine time group, the calculation follows a different path:

  • The full base time becomes the machine component
  • A human share is derived from the mechanisation level (0–5):

Human share = 1 − mechanisation × 0.2

  • Mechanisation 0 (manual) → human share = 100%
  • Mechanisation 3 (machine) → human share = 40%
  • Mechanisation 5 (automatic) → human share = 0%

The cycle time (Part) is the maximum of human and machine components — both channels run in parallel, and the longer one determines the cycle.


Overlap (BSM formula)

When microelements inside a template or action have an overlap coefficient (Kc), consecutive elements share part of their time:

Combined time = t_max + (1 − Kc) × t_min

Where t_max and t_min are the times of the larger and smaller elements in the pair.

  • Kc = 0 — no overlap, times are fully additive
  • Kc = 1 — full overlap, only the longer element counts
  • Kc between 0 and 1 — partial overlap

The formula is applied to all four time components (Full, Human, Machine, Part) independently.

Overlap models situations where a worker performs two actions simultaneously — for example, moving the left hand while the right hand holds an object.


Employment factor

Each microelement has an employment setting (overlapped / non-overlapped):

  • Non-overlapped — the time adds fully to the cycle (employment = 0)
  • Overlapped — the time runs in parallel with automatic machine operation and is excluded from the Part component

The Part time is calculated as: Part = Full × (1 − employment)

This means overlapped elements contribute to Full time but not to the production cycle — the machine works while the person performs overlapped actions.


Template and action aggregation

Templates and Actions aggregate their children's times:

  • Each child's four time components (Full, Human, Machine, Part) are summed
  • Overlap formulas are applied between consecutive children
  • The multiplier is applied to the total
  • Weighted averages of mechanisation level and production type are computed using Part time as weight

Intensity (Actions only)

Actions support an intensity setting that scales their contribution:

  • Quantity — the action occurs once per N units: factor = 1/N
  • Percent — the action occurs with a given probability: factor = %/100
  • Time — the action occurs once per time period: factor = cycle time / period

The intensity factor scales all four time components proportionally.


Step aggregation

A step collects its actions and templates, calculates each one, and sums the results. The step's multiplier is applied to the total.

The step also computes weighted quality metrics (QL, DPMO, Stability) from its children — see the Quality Metrics documentation.


Operation aggregation

The operation is where the three time groups come together:

Main time (cycle)

Steps of type main and auxiliary form the production cycle. Their Part times are summed and divided by processing capacity to get the per-unit cycle time:

P = sum of main steps' Part times × multiplier / capacity

Preparatory time (PR)

Steps of type organisational, workplace maintenance, preparatory, and rest & personal needs form the per-shift overhead. This time is deducted from the available working time budget every shift.

Setup time (ST)

Steps of type setup, technological needs, and equipment maintenance form the changeover overhead. This time is deducted on first start or when switching to a different product type.

Per-piece adjustment (P1)

The adjusted per-piece time distributes preparatory and setup overhead across the batch:

P1 = P + (PR + ST) × multiplier / (batch size × capacity)

The same formula applies to F1, H1, M1 — each component receives its share of the overhead.

The percentage shown after P1 indicates what fraction of the per-piece time comes from preparation and setup versus actual production work.


Product aggregation

The product sums its operations:

  • Each operation's times are weighted by its intensity factor
  • The product's multiplier is applied to the total
  • Setup and preparatory times are aggregated separately
  • All adjusted values (F1, H1, M1, P1) carry through

The final product result answers: "How much total time does it take to produce one unit, including all overhead?"


Result caching

Calculations are performed lazily — only when a result is requested or displayed. Once computed, the result is cached in the element's presentation layer.

When you change a factor, alias, or any parameter that affects time, the cache is invalidated up the chain. The next time a result is read, it recalculates from the changed point upward.

This means large models with hundreds of elements remain responsive — only the affected branch recalculates, not the entire tree.


Units

Internally, all times are stored in base units (1/1000 of a minute = 0.06 seconds). The Result block displays times in the unit you select:

  • Raw — base units (1/1000 min)
  • Seconds — base × 0.06
  • Hours — base × 0.06 / 3600
  • Time format — HH:MM:SS

The unit setting is per-element and does not affect the calculation — only the display.