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

Lean Tags

Every action on the canvas can be tagged in four dimensions that classify the type of work being performed. These tags drive the time breakdown analysis and help identify waste, automation potential, and value stream composition.

The Four Dimensions

Mechanisation

Classifies how a task is performed along the human–machine spectrum. Six levels:

  • Manual labour β€” entirely by hand
  • Manual-mechanised β€” hand work aided by simple tools
  • Machine-manual β€” machine performs work with manual control
  • Machine β€” machine performs work with partial autonomy
  • Automated β€” machine follows programmed sequence, human monitors
  • Automatic β€” fully autonomous, no human intervention

The mechanisation tag directly affects calculation: it determines the human/machine time split for each microelement and contributes to the weighted mechanisation level used in quality metrics.

Each level has a power value (0.5 to 1.1) that weighs its contribution to the aggregate mechanisation score.


Target

Classifies the purpose of the action. Fifteen values, divided into value-adding and waste categories:

Value-adding and necessary:

  • Production β€” directly creates or transforms the product
  • Delivery β€” moves the product to the next stage
  • Decision β€” selects the production path
  • Monitoring β€” checks process parameters
  • Inspection β€” quality verification
  • Coordination β€” synchronises between people or systems
  • Data management β€” records, retrieves, or updates information
  • Security & Compliance β€” regulatory and safety procedures
  • Movement β€” operator relocation

Lean waste types (muda):

  • Idle β€” waiting, no productive work
  • Overprocessing β€” doing more than required
  • Overproduction β€” producing more than needed
  • Rework β€” correcting defects
  • Unused talent β€” underusing operator skills
  • Task switching β€” context changes between different tasks

The target breakdown reveals what fraction of per-piece time goes to each purpose β€” instantly showing the waste ratio.


Carrier

Classifies the medium through which work is performed:

  • Physical β€” tangible manipulation of objects
  • Digital β€” work on screens, data entry, system interaction
  • Cognitive β€” thinking, planning, problem-solving
  • Organizational β€” meetings, handoffs, approvals

The carrier breakdown shows the nature of work: a heavily digital process might benefit from automation, while a cognitive-heavy one requires experienced operators.


Stream

Classifies where the action falls in the value stream:

  • Value β€” directly adds value perceived by the customer
  • Support β€” necessary but not value-adding (internal logistics, quality checks)
  • Waste β€” neither adds value nor is necessary (should be eliminated)

This is the classic lean trichotomy. The stream breakdown provides a single-number summary of process efficiency: what percentage of time is value, support, or waste.


Applying Tags

Tags are set on actions β€” the container elements that hold microelements. Each action can have one value per tag dimension.

In the properties panel, when an action is selected, the tags section shows a dropdown for each dimension. Selecting a value calls the command `cmnd.element.ml.setTag()` β€” the change is recorded in the undo/redo history like any other edit.

Actions without tags are reported as "untagged" in the breakdown (using the special key βˆ’1).


How Tags Drive Analysis

Step Level

When a step's time is calculated, each action's contribution is recorded in a breakdown entry that carries the action's target, carrier, and stream values along with its time. Untagged items (microelements outside actions) use βˆ’1.

Operation Level

The operation calculator aggregates step breakdowns into three maps β€” one per dimension (target, carrier, stream). Each map goes from tag value β†’ time contribution.

Two versions are produced:

  • partBreakdown β€” breakdown of the cycle time only
  • p1Breakdown β€” breakdown of the per-piece time (cycle + overhead amortised by batch)

Process and Product Levels

Parent elements merge their children's breakdown maps, applying intensity factors and scaling. This means the breakdown at the process level reflects all child operations weighted by their intensity.


Visualisation

The Passport on operations and processes includes a "Time Structure" section that renders the p1Breakdown as horizontal bar charts:

  • One chart per dimension (target, carrier, stream)
  • Each tag value gets a labelled bar showing its percentage of total P1 time
  • Bars are colour-coded by dimension for visual distinction

This visualisation immediately shows questions like:

  • What percentage of cycle time is pure waste?
  • How much time goes to rework vs. production?
  • Is the work mostly physical or digital?
  • What fraction is value-adding vs. support?