A beige background indicates that this node represents a choice between two or more alternative processes. Selecting a row that contains this type of node causes the system to auto-select between the underlying alternative processes.

A solid border indicates that this node is marked as required. A feasibility rule failure at one of these nodes will cause an entire routing alternative to fail.

A dashed border indicates that this node is marked as optional. It may be included or excluded via a right-click menu.

A clear background indicates that this node was not evaluated by the system in the last costing event. This is either because of a feasibility rule failure, because the node has been excluded from the routing by a user, or because the node was not required for the manufacturing of the component.

A green border and user-override symbol indicate that the routing was customized, and this node was added. It may be removed from the routing via a right-click menu.

The node succeeded (i.e., it passed feasibility evaluation).

A yellow status icon on a node indicates that the node passed feasibility evaluation but has some uncosted GCDs. Click on the icon to see which GCDs failed to cost.

A yellow status icon over a GCD icon in the Cost column indicates that this routing, although costed, has some uncosted GCDs associated with it. Hover the cursor over the icon to see what GCDs failed to cost.

A red status icon indicates that the node failed to cost. Click on the indicator to see why the process failed feasibility evaluation.

This node has Process Setup Options (PSOs) that can be customized by the user. Click the hammer or right-click the node and select Process Setup Options.

User override: .The routing has been customized.