What are Routings?

In Amper, the standard Parts list only allows you to set one target cycle time per part. But in reality, the same part can run on different machines, and each machine might have a different standard cycle time.

Routings in Amper give you more flexibility by letting you define not just the part, but also the specific operation, the machine it's running on, and the expected cycle time for that combination.

Why are Routings useful?

Routings allow you to:

1. Define different cycle times for a Part, depending on the operation and/or machine.
2. Limit which machines a part can run on, so operators only see parts relevant to the machine they’re using when they’re in Copilot.

Routings will eventually unlock the ability to:

1. Enforce the order of operations when producing a part from start to finish.
2. Improve visibility into WIP.

Defining Routings

Routings can be created, viewed, or edited in Settings > Parts .

Each Part in your list has an option for routings.

Clicking on Routings will take you to a page where you can create or see that part’s routings.

Click Create New Routing to name the routing (usually after the operation), define target cycle time, and select which machine(s) it applies to. You can add as many routings per part as desired.

When naming a routing, pick something that will make sense for your operators. When they are selecting routings from Copilot, it will appear as a combination of Routing Name - Part.

Some options for a naming convention are by operation, by numerical sequence, or a combination of the two.

CSV Upload

Routings can also be created via CSV upload. When creating routings, it is necessary that the part attached to the routing already exist in Amper.

Using Routings

Defining Jobs

Once you have created a routing, you can now put it into action by attaching it to a job.

When you go to Standards > Jobs and create a new job, you will be prompted to pick a routing instead of a part.

You will notice the target cycle time field is no longer there, since it is defined in the routing.

Once you select a routing, you will only be able to select a machine for the job that is compatible with the routing and vice versa.

Now, wherever you see job data (e.g. Scoreboards, Hour by Hour Board, Target Tracker), the part and target cycle time values will pull from the routing attached to the job.

Copilot

When an operator starts work in Copilot, they’ll now choose a routing instead of a part. They will only be able to select a routing valid for that machine.

Similarly, preexisting jobs will only show in the Job dropdown if the routing on the job is valid for that machine.

As with the web app, you will no longer choose a target cycle time or part for the job since those are included in the routing you select. The target cycle time value will be read only and will auto-populate when you select the routing.

Once you start production with the job and routing selected, all part or target cycle time values will pull from the routing.