Most value stream maps are static drawings. They’re useful for capturing a snapshot of how a part of a process flows, but they exist separately from the rest of the system, the actual instructions that run the process, the data that describes it, and the people improving it. Once drawn, they go out of date quickly and offer little ongoing analytical value.
The Map in Threaded is different. It’s the data model that connects your process structure and performance data into a single, connected and evolving system. Rather than a picture of your process, the Map is an executable description of it. Because it’s connected to your performance data and team, it can be analyzed, queried, and continuously improved with your team and AI.
#Key Concepts
Process nodes are the building blocks of the Map. Each node represents a step in your manufacturing process. Process and inventory nodes connect to form a value stream, mapping how inputs flow through your process to become finished products.
There are two types of nodes on the Map:
- Process nodes — operations where work is performed. Planned performance data (cycle times, operators, yield, uptime) is entered for these in Process Planning, not on the Map canvas.
- Inventory nodes — material flow points between operations. Used to model buffer stock, FIFO queues, or Kanban systems.
The Map is a flat value stream on the canvas, process and inventory nodes in sequence, without nested operation hierarchies on the map itself. Groups are used in Process Planning to define the hierarchy used for rollups, line balancing, and plan statistics. Assign Map process nodes to Groups to analyze lines, cells, or value streams at the scope you need.
#Navigation
Click Map in the top navigation to open the Map canvas. The org-level Map is where you build and organize your value stream. Line balancing, constraints, and detailed plan metrics live in Process Planning. The toolbar at the top of the canvas provides access to node controls and the commit selector.
#Commit Model
The Map has two commit states that reflect where your process currently stands:
- Published — the approved, active version that operators and reports see. This is the Published view of your value stream.
- Draft — the active editing environment where changes are made before they are published.
Use the version selector in the Map toolbar to switch between Published and Draft views, or to browse the history and review previous versions of the Map. When your edits are ready, click “Save” to create a new Published view. Editors work in Draft without affecting the Published view, so operators always see a stable, approved map.
#Building Your Map
#Adding Process Nodes
Process nodes can be added at the top-most level to the Draft map using the New node button in the Map toolbar (which creates a process node by default), or open the dropdown beside it for New Process Node and New Inventory Node. You can also add nodes directly inside the value stream using the + buttons that appear on the edges between existing nodes in the flow.
#Grouping and Organizing Nodes
Nodes can be grouped to reflect how your operation is physically or logically organized. Select multiple process nodes using Cmd/Ctrl + Click, or hold Shift and drag a box around nodes, then click Create Group in the toolbar. Groups created on the Map are linked to Process Planning for rollups and analysis.
To change group membership or reorganize hierarchy, use the Move button after clicking on a map node or use the Groups sidebar tree in Process Planning.
#Splitting Nodes
Complex operations can be broken into sequential steps by adding process nodes to the flow and grouping them in Process Planning for line balancing analysis.
#Inventory Nodes
Inventory nodes model material flow between operations. Hover over the connection line between two nodes and click + to add an inventory node. Three standard inventory node types are available: Buffer, FIFO, and Kanban. Each has configurable parameters for its inventory type that contribute to throughput time calculations.
#Performance Data
The Map connects to performance data that can be compared to identify gaps between the manufacturing plan and floor reality.
#Process Plan
Planned performance targets (cycle times, operator counts, yield, uptime, and related metrics) are entered in Process Planning for Map process nodes assigned to each Group, not on the Map canvas. See Process Planning.
#Metrics and Rollups
Each process node in Process Planning calculates and displays:
- Cycle Time — the governing time or rate of the process node (maximum of Operator C/T and Machine C/T)
- Effective C/T — cycle time adjusted for yield, uptime, and lot size
- Operators — headcount required
Group nodes roll up from their children:
- Effective Unit C/T — combined effective cycle time across the group
- Throughput Time — total processing time plus inventory time
- RTY — Rolled Throughput Yield across all operations
- Operators — total headcount across the group
#Process Planning
For line balancing, takt time, and performance statistics, see Process Planning.
#AI Analysis
Because the Map is a connected data model rather than a static drawing, the AI Assistant can reason about your entire process system—not just individual operations. Ask the AI to identify your primary constraint, analyze line imbalances, suggest how to redistribute work across operators, or estimate the impact of a process change before you make it.
@mentioning specific process nodes or groups in the AI chat focuses the analysis on that part of your value stream. For more on using the AI Assistant with your process data, see The AI Assistant.