This screen appears when you double-click the routing step on the Routing tab page of the Routing Maintenance screen in the drawing area.
The following tables describe fields requiring explanation:
Field |
Description |
---|---|
Step ID |
The unique identification of the step Note You can assign a step ID manually, or the system automatically assigns a step ID when the routing definition is saved. This value appears on some reports and activities to help you distinguish among duplicate operations on a routing. The step ID does not control step sequencing but affects the order of steps in the list of routing steps. End of the note. |
Entry Step |
If selected, this step is the entry step on the routing. Only one routing step can be the entry step. |
Operation |
The operation being used as a routing step The operation is defined in Operation Maintenance. Note that you can use the same operation multiple times as steps on the same routing if the Allow Duplicate Operations on Routing system rule is set to TRUE. |
Step Type |
The type of the routing step Normal: The routing step cannot be started until a previous routing step has been completed. Optional: The step may be optionally started or skipped based on the decision of the operator. Simultaneous: A set of routing steps in a group that are completed simultaneously (either independently or dependently of one another) on an SFC number. Any order: A set of routing steps in a group that can be completed in any order but must all be completed before an SFC number can be started at a routing step outside of the group. Note This field appears only for tabular routings. Select the Tabular Routing checkbox on the Main tab of the Routing Maintenance screen to create a routing in the tabular mode. End of the note. |
Maximum Loop Count |
The maximum number of times an SFC number can be processed at an operation Note End of the note. The value 0 (zero) indicates that there is no maximum. |
Reporting Step |
The step as it is known on an ERP system, if an ERP system and the system have been set up to exchange step-level data. This value is used for sending confirmations back to the ERP, so the ERP can track the SFC number's progress down the routing. When an SFC number completes this step, a confirmation is sent back to the ERP using this reporting step identification. |
Work Center |
The work center at which you perform this operation Note This is used strictly for some reports and is not used to control the flow of an SFC number within work centers. End of the note. |
Special Instructions |
The special one-line instruction displayed to the operator on starting the SFC number at an operation in the POD |
Queue Decision |
Determines which operator decides where the SFC number should be queued after it completes this routing step Completing Operator: The operator completing the SFC number at this routing step determines where the SFC number is put in queue. Next Operator: The operator at the next routing step determines where to start work on the SFC number. The SFC number is placed in queue at all the next routing steps and the first operator to start it controls where the SFC number is processed. |
Rework Step |
If selected, the time spent at this step is considered rework. |
Required Time In Process (minutes) |
The required elapsed time for the routing step measured in minutes (see Elapsed Time in Process Check) |
Field |
Description |
---|---|
Sequence |
The order the system executes this hook point. Note The system uses this value to sequence all activities associated with this hook point. End of the note. |
Hook Point |
Specifies when the system should execute the activity identified in the Activity column of this row. |
Activity |
The hook point activity that system runs when this hook point is triggered at the routing step |
Enabled |
If selected, allows the system to run the specified activity when this hook point is triggered for this routing step. Note You can use this checkbox to temporarily disable the activity hook, for example when troubleshooting a problem. End of the note. |
User Argument |
Used only with hook point activities; contains additional parameters or values to be passed to the activity during the hook execution |