Branching with Nonconformance Codes and Scripting 
You can use branching, when you do not want operators to select the next step for an SFC number. Branching allows you to use a combination of NC codes and scripting to automatically control where the system sends SFC numbers.
NC codes are codes that operators can log against SFC numbers in the PODs. NC codes indicate what is wrong with the unit. As well as test failures, you can use NC codes to indicate any type of nonconformance of a unit, such as a scratch on a chassis.
Operators at operations such as ANALYSIS and REPAIR can log NC codes to indicate the result of their work. You can use such NC codes to track units through a repair loop and verify defects.
Note that machine interfaces can also send nonconformance messages to the system.
You can associate a coded script with any branch in a routing. You create a script for a branch by double-clicking the line between two routing steps and entering the code.
In the example in Branching, you can create a PASS script for the line between the TEST step and the PACK step, and a FAIL script for the line between the TEST step and the ANALYSIS step.
Following is the PASS script:
if (NC_CODE==null)exit(true);
Following is the FAIL script:
if (NC_CODE!=null) exit(true);
When an operator at the TEST step completes an SFC number, because the SFC number has no NC code, the system executes the PASS script and places the SFC number in queue at the PACK step. When an operator at the TEST step logs an NC code against the SFC number, the system executes the FAIL script and places the SFC number in queue at the ANALYSIS step.
Note
The system provides both of these scripts in Routing Maintenance. You can change them as needed.