Process Nodes

Process Nodes

Process Nodes in Steelhead are the building blocks for Processes.

Together, process nodes map out how work is performed step-by-step for a specific process. Process nodes are mapped in processes in a tree structure called a Process Tree.

The first node in a process is a Parent Node, which means that it is the "parent" to one or more nodes beneath it. Nodes that branch from another node are called Child Nodes. Nodes that share the same parent are called Sibling Nodes. A single node can be a parent, sibling, and child all at the same time.

Process Node Types

There are many different types of process nodes:

Node Type	Description	Icon
General	The default option for nodes. General nodes represent a step in a process, usually at which a Treatment may be performed. A general node should be linked to one or more Stations.	no icon
Containerize	This is very similar to racking in Steelhead. Workers will be prompted to containerize parts, usually used when packaging parts before shipping.
Shipping	Shipping nodes are organizing, auto complete nodes that contain three child nodes: Ready for Shipping, Packing Slip Created, and Shipped. Parts that are in any of these nodes will appear in the shipping dashboard.
Invoicing	Parts that are in the Invoicing node appear on the Invoicing Dashboard as "Ready to Invoice." Usually, invoicing is the last step in a process.
Racking	Racking nodes prompt workers to rack parts. The racking interface is shown on the Work Parts screen, which allows for racking of multiple parts or work orders from, assembling multiple racks, or moving complete racks.
Unracking	Unracking nodes prompt workers to unrack parts and easily allow unracking multiple parts and work orders on workboards.
Outsourcing	Outsourcing nodes are used when parts leave your plant for work that you outsource to somewhere else. Use this node type when you routinely outsource one or more steps in your process. Parts will appear on the Outsourcing dashboard when at this node.
Super Node	Super nodes are used when you want to track parts through several nodes but do not want to step the parts through each node. When parts are stepped through a super node, each child node automatically completes and the parts are advanced through every child node of the super node. It can be helpful to think of a Super Node as a container that makes each child node an auto complete node. Super nodes are useful for auto lines or hybrid auto / manual lines, or in other situations where operators do not need to track time at each node. When working parts on a super node, each child node appears as a separate tab. Note that Super Nodes are only for unracked parts.
Super Card	A Super Card is like a Super Node, except only for racked parts.
Staging	Staging nodes are nodes where parts are queued for the next step in the process. For example, "Ready for Blast" could be a staging node directly before "Abrasive Blast". Parts in the "Ready for Blast" node are staged and waiting in line for the blasting booth. Staging nodes allow you to see instructions for the next process node from workboards.
Scanner	Scanner is a special node type that allows parts to be transfered among child nodes by scanning each Station's QR code when viewing an associated workboard. Only racks can be transfered by scanning.
Contract Review Node	Contract Review nodes allow for preview of every step of a part's recipe in order to verify that the part will be successfully completed. Necessary changes can be performed at this node, including changing a part's specs. Contract Review can be set up with Pass/Fail sign offs to allow/disallow the part to move on. Parts at a Contract Review node will appear in Steelhead's Contract Review module, and the same information can be seen on the work parts screen.
Quality Assurance Node	Quality Assurance nodes allow for you to view a part's recipe tree and spec measurements recorded. It is helpful for inspection of parts near the end of the process, before completion.	no icon

Node Auto Complete Setting

Setting a node to "Auto Complete" means that parts will not dwell in that node for any length of time. When parts are stepped into a node that has "Auto Complete" enabled, the parts will automatically move to the next node in the process tree. This setting is primarily used for nodes that are only included for organization.

In the example below, the "Shipping" node is set to auto complete, as indicated by the "Auto" and arrow icon. In this example, the parts will move directly from "Unracking" to "Ready for Shipping."

To enable Auto Complete on a node, check the "Auto Complete" box on the top tile of the node page.

Process Node Tags and Shared Nodes

Tags are a way to organize and differentiate your Process Nodes. Once a Process Node is tagged, you can add that node to another process with "Add Existing Node". This adds a Shared Node, meaning it is the same node appearing on multiple processes. Any changes made to a shared node will be reflected in all processes that share that node.

For example, if three processes share the "Abrasive Blast" node, adding children or changing the node type will add children or change the node type of Abrasive Blast on each process.

Video on Repeated Nodes for Opt-in/out Treatments

When you add the node to a process tree that you add it by 'existing node' or 'tag', you can sure it will populate on the workboard.
This is in the 'Processes' module from Steelhead Home page, editing a tree for a specific process:

When editing a specific WO process tree, this is where you will add it by the 'In-Process Inspection' tag:

Process Node Opt In/Opt Out

In cases where not every Node is used in every related Recipe, you can configure Opt-in and Opt-out options for Nodes. This allows you to generate Recipes that have flexibility, rather than having to create many Processes with only slight differences.

• Opt-Out: The default Recipe will include Opt-out Nodes, but you will have the option to exclude them during order entry. This is a good option for Nodes that are used most of the time, but not always.
• Opt-In: The default Recipe will exclude Opt-in Nodes, but you will have the option to include them during order entry. This is a good option for Nodes that are used infrequently.

To configure Opt-In or Opt-Out options for a Process:

1. Click CONFIGURE OPT-IN/OPT-OUT at the bottom of the tile on the Process page.
2. Select either Opt In or Opt Out for a Process Node & SAVE changes.

When creating a new work order, you will now have the option to opt in or out of the Nodes that you adjusted.

Process Node Occurrence:

If a Process Node is used multiple times in a Process, each Node will be a separate occurrence of that same Process Node. Occurrences can have different Treatment selections and Station routing on Part Numbers, Recipes, Specs, and other entities that use a default Process. On the Part Number Process Tree for any Part which is assigned to such a Process, you can enter differing work instructions for each occurrence of the duplicated Node.

• This allows precise control of all Work Orders and Sales Orders.
• It also improves the use of features like opt-ins/opt-outs, and the Process Composer.

Video explanation with more detail:
Process Node Occurrence

There is also a domain setting for default treatments.

Here is a video showing more info about how the process composer may be used.

Save-As Button:

This button can be found in the process composer menu

• Go into part number process composer
• Select and load a process
• Click the save as button next to a node
• This should create a new node that is a copy of that one
• Edit that node from the process composer
• Notice that these edits will only apply to the part number

--