πŸ“– This is a static documentation page. Open the interactive version with live canvas demos β†’

Templates & Reuse

A Template is a special container for grouping microelements into a reusable block outside the main process hierarchy. It reduces duplication and ensures consistency of recurring work fragments.

Why templates exist

In real production, many actions share identical sequences of elementary motions β€” "reach, grasp part, move to fixture" for example. Without templates, you would copy the same microelements into every action that uses them.

A template lets you assemble the sequence once and insert the entire block wherever needed.

A template is technically a microelement of a special group (blank). It appears in the Microelements panel alongside standard groups.


Creating a template

Drag the Template element from the Microelements panel onto the canvas. A new empty template appears, ready to accept children.

At creation, the template receives:

  • A default name based on the current language
  • A mechanisation tag set to manual labour (level 0)
  • An empty combined group for future children

What templates accept

Templates follow strict nesting rules:

  • Microelement β€” yes
  • Template β€” yes, templates can be nested
  • Action β€” no
  • Process Item β€” no
  • Flow Item β€” no
  • Environment β€” no

Nesting is performed by drag-and-drop β€” the same capture (red dot) and insert (green line) mechanism described in the Combine & Nest documentation.

Templates can be nested inside templates to any depth. This allows building complex reusable sequences from simpler reusable blocks.


Placing templates into the hierarchy

Once assembled, a template can be inserted into:

  • An Action β€” as part of the process hierarchy
  • Another Template β€” as a sub-block

To insert, drag the template towards the right edge of the host element until the red dot indicator appears, then release.

The template and all its children become part of the host's combined group. Their times are included in the host's calculation.


Level of mechanisation

Every template carries a mechanisation tag that classifies the degree of automation of the contained work:

  • 0 β€” Manual labour β€” operations performed by hand or with non-powered tools
  • 1 β€” Powered-hand labour β€” manual work using powered hand tools
  • 2 β€” Machine-hand β€” operations with machines requiring physical effort from the worker
  • 3 β€” Machine (apparatus) β€” process operations under active control of equipment
  • 4 β€” Automated β€” machine processing under passive supervision
  • 5 β€” Automatic β€” processing without direct worker involvement

The level is set in the Properties panel via a tag selector.

The mechanisation level affects the analysis context β€” it contributes to the Stability (S) metric at the operation level. It does not directly change the calculated time of contained microelements.


Template vs. Action

Templates and Actions are often confused because both can hold microelements. The key differences:

Structural role

  • Action β€” lives inside the process hierarchy (Product β†’ Operation β†’ Step β†’ Action). It is part of the production sequence.
  • Template β€” lives outside the hierarchy. It is a reusable building block inserted into Actions or other Templates.

Tags

  • Action has three tag axes: Purpose (production, delivery, decision…), Medium (physical, digital, cognitive…), Flow (value-adding, supporting, waste)
  • Template has one tag: Level of Mechanisation (0–5)

Intensity

  • Action supports intensity settings (quantity, time, or percent) with phase control
  • Template does not support intensity β€” its time is the sum of its children times the multiplier

Nesting

  • Action accepts microelements, templates, delays, and machine time. It cannot accept another action.
  • Template accepts only microelements and other templates.

Quality factors

  • Action does not have quality factors
  • Template does not have quality factors

Both support: alias, comment, overlapped employment toggle, value block, multiplier, combined group visibility.


Time from templates

A template's time is calculated as the sum of all its children:

  • Each child microelement contributes its calculated time
  • Nested templates contribute their own aggregated time
  • The template's multiplier applies to the total

When a template is nested inside an action, its time becomes part of the action's total. The multiplier chain applies β€” a template with multiplier 2 inside an action with multiplier 3 contributes six-fold.

The overlapped employment toggle determines whether the template's time runs in parallel with machine time or is added to the total.


Practical patterns

Standard grasp-move sequence

Create a template containing: Reach β†’ Grasp β†’ Move β†’ Place. Insert this template into every action that involves picking up and positioning a part.

Tool operation

Create a template with mechanisation set to Powered-hand (level 1). Add: Grasp tool β†’ Move to workpiece β†’ Machine time β†’ Release. Reuse across operations that use the same tool.

Nested templates

For complex assembly, create a "prepare fastener" template (reach β†’ grasp bolt β†’ move) and a "tighten" template (place β†’ rotate β†’ press by hand). Then create a parent "bolt assembly" template that contains both. Insert the parent into any action.

Templates do not need to be universal. If a sequence appears in two or more actions, it is worth extracting into a template β€” even if it is only used twice. The benefit is consistency: update the template once, and both actions reflect the change.


Editing and updating

When you modify a microelement inside a template:

  • The change applies to that specific template instance
  • Time recalculates throughout the entire chain β€” template β†’ action β†’ step β†’ operation β†’ product
  • The change is recorded in the command history and can be undone

To add or remove children, use the same drag-and-drop and ungroup operations as with any combined group.

If you need the same template with different factor values, create a copy. Templates are not shared references β€” each instance on the canvas is independent.