Get started with dynamic routing

A dynamic routing usage entry in the Dynamic Routing Usage tab specifies the conditions for triggering a specific dynamic routing process and some aspects of its runtime behavior. General runtime behavior—such as whether a dynamic routing process creates a separate work order or is merged into the work order of the originating process—is controlled by the parameters in the Dynamic Routing section in the General Parameters workspace tab (see System parameters reference).

Triggers

The triggering of a dynamic routing process depends on the following conditions:

• An item reason that, if selected when production is being reported, indicates that the quantity being reported requires rework. A trigger item reason must be entered for every dynamic routing usage entry.

• Optionally, the triggering can be further restricted by any combination of the following:

  • Production being reported from only certain jobs in an originating process

  • Production being reported for a specific item

Routing code

Each dynamic routing usage entry includes a routing code. If the optional originating process has been defined, then this routing code must also be assigned to any operations of that process whose jobs can trigger the dynamic routing process.

Dynamic routing process behaviors

The following settings affect specific behavior for the usage entry's dynamic routing process:

• How many times an instantiation of the dynamic routing process can be run for a specific rework of material production.

• To which operation in the originating process the reworked production should be re‑routed when the dynamic routing process is completed. If a re‑entry operation is not set up, then the reworked material will be routed to the operation that is subsequent to the operation from which the dynamic routing process was initiated.

What uniquely identifies a dynamic routing usage entry

A dynamic routing usage entry is uniquely identified by the item reason and routing code that is assigned to it. So, each item reason–routing code combination specifies a unique combination of:

• The dynamic routing process to be triggered.

• Optionally, specific jobs within an originating process from which rework is allowed.

• Optionally, a specific item for which rework is allowed.

If you want to vary any of these three elements for the same item reason trigger, then a new usage entry with a different routing code is required.

General configuration steps for a dynamic routing process

1. If the item reason that will be used to trigger the dynamic routing process doesn't already exist, create it.

2. In the Processes module, create the dynamic routing process.

   • On the process' Properties window, select the Dynamic Routing check box.

   • Set the item being produced by the process to the reworked material.

3. In the Dynamic Routing Usage module, create the usage entry.

4. In the usage entry's property settings, specify the following:

   • The item reason (Reason Description).

   • The routing code (Originating Routing Code).

   • The dynamic routing process (Dynamic Routing Process ID).

   • To optionally allow the production reporting of only a certain item to initiate rework, the item (Item ID).

   • Optionally, how many times an instantiation of the dynamic routing process can be run (Max Dynamic Routes).

5. To optionally allow only certain jobs to initiate rework:

   • For the usage entry, select the originating process (Orig. Process ID).

   • In the Processes module, for the originating process' operations that instantiate those jobs, assign the routing code that was entered for the usage entry (Originating Routing Code) as the operation's Dynamic Routing Code.

6. To optionally define a specific operation to which the completed reworked material is returned (i.e., other than the operation that follows the operation that initiated the dynamic routing process):

   • For the usage entry, enter a re‑entry route code (Re‑entry Route Code).

For the operation to which the completed reworked material is being returned, enter that re‑entry route code as the operation's Dynamic Routing Code.