Routing operations
Use this function to modify (or replace) operations in one or a range of routings at a specific site.
You can set a validity start date for replacement operations. The default is today's date. Replacement operations are given the same sequence number in the routings as the operations being replaced. Their index number is incremented and the validity start date set. The operation with the highest index number is the new operation.
This function does not 'delete' operations, it simply marks them as 'not valid' by setting the validity end date to the validity start date for the replacement operation minus 1 day (n-1).
The routing displays operations that are valid on a specific date. The new operation, therefore, is only displayed in the routing once it becomes valid (fields Reference date (DATREF)/Start date (VALSTRDAT)).
You cannot use this function to change work centers assigned to operations. Use the function Replace work-centers instead.
Prerequisites
Refer to documentation Implementation
Screen management
The Routing operations function displays two selection screens:
- An initial screen into which you enter your routing selection (or filtering) criteria;
- A validation screen in which you confirm the updated or replacement details.
A log file displays the results of the run. Any excluded version-managed routings are listed on the log file.
Entry screen
Type in, or select the site at which the routings are to be updated.
If operations are to be replaced, click (select) the Replacement by date check box and select the effective application date. This will be used as the validity start date for reindexed operations.
Then select the routings to be included in the run. You can include subcontract operations and operations assembled into routings from standard operations. Only routings that are not version managed will be updated.
Production site (field MFGFCY) |
Type in or select the site at which the routings are to be updated. The site defined on the user record is displayed by default but can be amended. |
Replacement by date (field REPLACEFLG) |
Use this check box to control if operations in the selected routings are to be updated or reindexed (replaced).
|
Application date (field APPDAT) |
This field is only available for entry if the Replacement by date check box ix selected. It defaults to today's date. If the replacement operation is valid from a later date type in, or select the effective date. |
Start-end ranges
A number of ranges are displayed.
- To update the operations in all applicable routings, leave all the fields as the default values or blank.
- To update the operations in selected routings, type in the required ranges. Leave the first field blank to include the lowest value or the second field blank to include the highest value.
You can optionally select the routings by applying a calculation formula.
Start - end range
Code (field ROUALTDEB) |
Filter for results within a range of routing codes. Multiple routings can be defined for a single product. Each routing code can be assigned specific management features. These include restriction of the routing to a specific site and to specific areas of functionality (for use in a manufacturing environment, for costing or for capacity planning). For a single routing code, enter the same sequence number in the from/start Code and to/end Code fields. |
Routing (field ROUNUMDEB) |
Filter for results within a range of routings. For a single route, enter the same routing code in the from/start Routing and to/end Routing fields. |
Operation (field OPENUMDEB) |
Filter for results within a range of operation sequence numbers. For a single operation sequence number, enter the same sequence number in the from/start Operation and to/end Operation fields. |
Work center (field WSTDEB) |
Filter for results within a range of planned work centers. For a single work center, enter the same work center code in the from/start Work center and to/end Work center fields. The planned work center is attached to a work center group. It corresponds to a production resource on which a routing operation is to be carried out. |
Labor center (field LABWSTDEB) |
Filter for results within a range of 'labor' work centers. For a single work center, enter the same work center code in the from/start Labor center (Subcontract work center) and to/end Labor center fields. The work center site of a 'labor' work center must match the site for the routing code, if defined. Scheduling is not carried out for labor work centers as they are considered secondary and 'always available' (or available at the same time as the main work center). Their load is managed for information purposes only using the coefficients defined for the main work center. If the main work center is of type 'subcontracting' there is no associated secondary work center. |
Subcontract type (field SCOCODDEB) |
Use this field to filter the routings according to the selected operation types (normal operations, subcontract operations or exceptional subcontract operations). For a single type of operation, enter the same type in the from/start Subcontract type and to/end Subcontract type fields. The subcontract type defines if an operation is carried out internally or if it is sent to an external (subcontract) supplier. It can be set to one of the following values:
|
Subcontract work C (field SCOWSTDEB) |
Filter for results within a range of subcontract work centers. For a single work center, enter the same work center code in the from/start Subcontract work C (Subcontract work center) and to/end Subcontract work C fields. A subcontract work center can be used for the following:
A subcontract work center has the work center type set to 'Subcontracting'. Routing operations are validated to ensure the work center site of a 'subcontract' work center matches the site for the routing code, if defined. |
Subcon prod (field SCOITMDEB) |
Filter for results within a range of services carried out by subcontractors. For a single service, enter the same product code in the from/start Subcontract prod (product) and to/end Subcontract prod fields. |
Selection formula (field FORMULE) |
Enter, select or build an Enterprise Management filter calculation expression using the formula editor.
|
Block number 2
Include the operations derived from std operations (field EFFUPD) |
Leave this check box clear to exclude operations assembled into routings from standard operations. To include operations assembled into routings from standard operations, click this check box. |
Exclude unmodified operations (field EFFUPD2) |
Leave this check box ticked (selected) to only display operations that meet the entered selection criteria that will be changed or replaced by the values defined in the Modification fields. Alternatively, clear this check box to display all operations that meet the entered selection criteria. |
Modification block
You use the fields in the Modification block to update specific fields on the operations that are used in the selected routings.
Click (select) the required check box to update the field then enter the new value. Alternatively you can apply a calculation formula to change the field values.
Modification
Setup time (field FSETTIM) |
Use this field to specify the actual time it takes to prepare this work center. This time forms part of the work center load. It is expressed in the time unit specified in the routing header or in the time defined for the standard operation, if a standard operation has been applied for this operation. |
Formula (field SETTIMF) |
Enter, select or build an Enterprise Management filter calculation expression using the formula editor.
|
Run time (field FOPETIM) |
The operation time is the time necessary to manufacture the product described in the routing. The operating time unit can be:
|
Preparation time (field FPRPTIM) |
Preparation time is 'waiting time' set at the start of an operation. Preparation time is always expressed in hours. It does not use the time unit defined in the routing header (field Time unit Although preparation time is waiting time it can be used for the time it takes to prepare for an operation on a work center. This might be time for settling liquids or cleaning a machine. For this type of scenario, that is when preparation time is used for setting time at the start of an operation, the resource must be available. When scheduling preparation time the calendar for the defined resource is applied. This means that if, for example, a work center (machine or labor) runs from 08:00-12:00 and 13:00-17:00 with a break for one hour between 12:00-13:00, preparation time will be interrupted by the one hour break. If the operation requires an 'emergency release', a reduction coefficient can be assigned that makes it possible to completely remove any preparation time. |
Waiting time (field FWAITIM) |
Waiting time is 'delay time' that occurs after an operation. It is non-productive time such as drying time or cooling time that occurs after a process has been completed on a machine and until the machine can next be used. Waiting time is always expressed in hours. It does not use the time unit defined in the routing header (field Time unit If machine time is required for an operation during the allowed waiting time you should add a new operation to this routing. A machine might be required for example, for drying or cooling components at a work center. The additional operation must be for the appropriate resource type, such as 'cooler'. When scheduling time for these resources if, for example, a work center (machine or labor) runs from 08:00-12:00 and 13:00-17:00 with a break for one hour between 12:00-13:00:
|
Post-operation time (field FPSPTIM) |
Post operation, or post run time is a 'deadline' that occurs after waiting time. It is non-productive time, typically 'transfer time', or a transition period from one work center to the next work center that occurs after a process has been completed on a machine and until the machine can next be used. Waiting time is always expressed in hours. It does not use the time unit defined in the routing header (field Time unit). Waiting time is not applied to the work center load. If operator time is required for an operation during the allowed post run time you should add a new operation to this routing. An operator might be required for example, for the transportation or carriage, or the transition between two work centers. The additional operation must be for the appropriate resource type, such as 'carrier'. When scheduling time for these resources if, for example, a work center (machine or labor) runs from 08:00-12:00 and 13:00-17:00 with a break for one hour between 12:00-13:00:
If the operation requires an 'emergency release', a reduction coefficient can be assigned that makes it possible to completely remove any post run time.
|
Labor setup factor (field FSETLABCOE) |
This is the planned setting time to obtain the setting time allocated to the labor work center linked to the main work center. This coefficient applied to the planned setting time to obtain the setting time allocated to the labor work center linked to the main work center. |
Labor operational factor (field FOPELABCOE) |
This is the coefficient applied to the planned operation time. It is used to obtain the operation time for the labor work center linked to the principal work center. This field is only available for entry if the labor work center is defined. Operation times are subdivided as follows: Proportional times are expressed for the production of an operation unit (and not in the stock unit of the finished product using the routing). |
Rate (field FCAD) |
The rate is a number of units produced by minute or by hour according to the time unit specified in the routing header (for an operation), or in the standard operation itself. |
No. of resources (field FWSTNBR) |
Use this field to define the number for this particular production resource that are required for this operation. For example, if three people are needed to operate a specific (labor) work center, type in '3'. |
No. of examples (field FLABNBR) |
Use this field to define the number for this particular production resource that are required for this operation. For example, if three people are needed to operate a specific (labor) work center, type in '3'. |
Modification block (continued)
Modification
OP UOM (field FOPEUOM) |
Work order operation quantities are expressed in the operation unit. Use this operation unit to express operating time in a different unit to that of the product being produced by the routing. For example, a product managed by unit is subject to three different operations, none of which produce intermediate stock:
There is no need to create semi-finished products for each production phase. The operation unit is associated with a conversion coefficient for the stock unit of the product being produced by the routing and the operation unit. |
Efficiency (field FEFF) |
Efficiency is a way to measure compliance to the preset standards. It can be calculated over a given period by work center: Standard hours calculated for a given production divided by the actual hours worked. Two efficiency rates are managed depending on the following:
If both factors are entered, they add up. The WSTEFFINH - Work center efficiency history parameter (GPA chapter, MIS group) is used to specify whether the efficiency defined at work center level should be used on the routing operation.
|
Formula (field EFFF) |
Enter, select or build an Enterprise Management filter calculation expression using the formula editor.
|
Shrinkage (field FSHR) |
This percentage is used to balance the quantities on the production operations based on the released quantity. It is possible to introduce a shrinkage percentage on the work center, which is used to weight the planned runtimes for an operation using this work center by a loss or gain on the quantity produced for the work center. |
Formula (field SHRF) |
Enter, select or build an Enterprise Management filter calculation expression using the formula editor.
|
Tab Modification of operations
You use this tab to confirm the details of the operations to be updated in the routings listed. You can change selected details, if required.
To cancel the update of a specific routing operation, click Delete from the Actions icon.
A log file displays the results of the run. Where appropriate it includes information which should be noted or acted upon. It also lists any excluded version-managed routings.
Block number 1
Production site (field MFGFCY) |
The site at which the selected routings will be updated. |
Routing (field ITMREF) |
This routing code describes the process involved in manufacturing (producing) or processing a product. That is, the sequence of operations and tools that are involved in producing or processing a particular product. The routing code matches the product code. The product code can be a manufactured product (a bill of materials), or a generic reference to a parent routing which is linked to several products. |
Alternative (field ROUALT) |
Multiple routings can be defined for a single product. Each routing code can be assigned specific management features. These include restriction of the routing to a specific site and to specific areas of functionality (for use in a manufacturing environment, for costing or for capacity planning). |
No. (field OPENUM) |
This field displays the sequence number of this operation. |
Index (field RPLIND) |
This field indicates if this operation has been amended. The value displayed concurs with the number of times this operation has been amended. The operation with the highest index number is the new operation. |
Start date (field VALSTRDAT) |
This field displays the start date of this operation's validity period. |
End date (field VALENDDAT) |
This field displays the final date of this operation's validity period. |
Std oper (field STDOPENUM) |
This field identifies the standard operation used to create this operation. Standard operations are simply 'template' operations that provide default information to be assembled into routings for producing or processing a particular product.
|
Work center (field WST) |
This field identifies the production resource that is to be used for this operation. This work center is the main (principal) work center for this operation. It can be a machine, labor or subcontract work center. The scheduling of the operations looks at the availability of this work center. Work centers of type 'subcontracting' are managed using the lead time defined in the subcontract product record. Subcontract operation times are not used by the scheduling. |
field WSTTYP |
This field identifies the type of operation that is performed on the selected work center. This might be a machine, labor or a subcontracted operation. Work centers of type Subcontracting are managed externally by subcontract suppliers. |
Work center group (field WCR) |
This field identifies the group of work centers to which this work center belongs. Work center groups are used to review workloads. |
Operation description (field ROODES) |
This field displays the description defined for the routing operation. |
Labor wk C (field LABWST) |
A labor work center can be associated with the machine-type or labor-type main work center. The labor work center times are calculated using two coefficients:
When creating a routing operation, the site attached to the work center must be the same as the site dedicated to the routing code, provided that the latter site is mentioned. This resource is considered as secondary and always available (or available at the same time as the main work center). Its load is managed for information purposes via coefficients applied to the main work center times. If the main work center is of sub-contracting type, no secondary work center can be associated. |
Labor work center group (field LABWCR) |
This field identifies the group of work centers to which this work center belongs. Work center groups are used to review workloads. |
Setup time (field SETTIM) |
Use this field to specify the actual time it takes to prepare this work center. This time forms part of the work center load. It is expressed in the time unit specified in the routing header or in the time defined for the standard operation, if a standard operation has been applied for this operation. |
Time unit (field TIMUOMCOD) |
This field displays the unit of time in which this operation is measured. |
Run time code (field ROOTIMCOD) |
The operation time type conditions the production time entry.
|
Management unit (field TIMCOD) |
Depending on the resource being used, the number of decimals of the operation time can be insufficient to express the production time. |
Base quantity (field BASQTY) |
Run time (field OPETIM) |
The operation time is the time necessary to manufacture the product described in the routing. The operating time unit can be:
|
Rate (field CAD) |
The rate is a number of units produced by minute or by hour according to the time unit specified in the routing header (for an operation), or in the standard operation itself. |
Number of resources (field WSTNBR) |
Use this field to define the number for this particular production resource that are required for this operation. For example, if three people are needed to operate a specific (labor) work center, type in '3'. |
Number labor res. (field LABNBR) |
Efficiency (field EFF) |
Efficiency is a way to measure compliance to the preset standards. It can be calculated over a given period by work center: Standard hours calculated for a given production divided by the actual hours worked. Two efficiency rates are managed depending on the following:
If both factors are entered, they add up. The WSTEFFINH - Work center efficiency history parameter (GPA chapter, MIS group) is used to specify whether the efficiency defined at work center level should be used on the routing operation.
|
Shrinkage in % (field SHR) |
This percentage is used to balance the quantities on the production operations based on the released quantity. It is possible to introduce a shrinkage percentage on the work center, which is used to weight the planned runtimes for an operation using this work center by a loss or gain on the quantity produced for the work center. |
Lab set fact (field SETLABCOE) |
This is the planned setting time to obtain the setting time allocated to the labor work center linked to the main work center. This coefficient applied to the planned setting time to obtain the setting time allocated to the labor work center linked to the main work center. |
Lab R/T fac (field OPELABCOE) |
This is the coefficient applied to the planned operation time. It is used to obtain the operation time for the labor work center linked to the principal work center. This field is only available for entry if the labor work center is defined. Operation times are subdivided as follows: Proportional times are expressed for the production of an operation unit (and not in the stock unit of the finished product using the routing). |
Preparation time (field PRPTIM) |
Preparation time is 'waiting time' set at the start of an operation. Preparation time is always expressed in hours. It does not use the time unit defined in the routing header (field Time unit Although preparation time is waiting time it can be used for the time it takes to prepare for an operation on a work center. This might be time for settling liquids or cleaning a machine. For this type of scenario, that is when preparation time is used for setting time at the start of an operation, the resource must be available. When scheduling preparation time the calendar for the defined resource is applied. This means that if, for example, a work center (machine or labor) runs from 08:00-12:00 and 13:00-17:00 with a break for one hour between 12:00-13:00, preparation time will be interrupted by the one hour break. If the operation requires an 'emergency release', a reduction coefficient can be assigned that makes it possible to completely remove any preparation time. |
Waiting time (field WAITIM) |
Waiting time is 'delay time' that occurs after an operation. It is non-productive time such as drying time or cooling time that occurs after a process has been completed on a machine and until the machine can next be used. Waiting time is always expressed in hours. It does not use the time unit defined in the routing header (field Time unit If machine time is required for an operation during the allowed waiting time you should add a new operation to this routing. A machine might be required for example, for drying or cooling components at a work center. The additional operation must be for the appropriate resource type, such as 'cooler'. When scheduling time for these resources if, for example, a work center (machine or labor) runs from 08:00-12:00 and 13:00-17:00 with a break for one hour between 12:00-13:00:
|
Post op time (field PSPTIM) |
Post operation, or post run time is a 'deadline' that occurs after waiting time. It is non-productive time, typically 'transfer time', or a transition period from one work center to the next work center that occurs after a process has been completed on a machine and until the machine can next be used. Waiting time is always expressed in hours. It does not use the time unit defined in the routing header (field Time unit). Waiting time is not applied to the work center load. If operator time is required for an operation during the allowed post run time you should add a new operation to this routing. An operator might be required for example, for the transportation or carriage, or the transition between two work centers. The additional operation must be for the appropriate resource type, such as 'carrier'. When scheduling time for these resources if, for example, a work center (machine or labor) runs from 08:00-12:00 and 13:00-17:00 with a break for one hour between 12:00-13:00:
If the operation requires an 'emergency release', a reduction coefficient can be assigned that makes it possible to completely remove any post run time.
|
OP UOM (field OPEUOM) |
Work order operation quantities are expressed in the operation unit. Use this operation unit to express operating time in a different unit to that of the product being produced by the routing. For example, a product managed by unit is subject to three different operations, none of which produce intermediate stock:
There is no need to create semi-finished products for each production phase. The operation unit is associated with a conversion coefficient for the stock unit of the product being produced by the routing and the operation unit. |
STK-OPE conversion (field OPESTUCOE) |
Subcontract (field SCOCOD) |
The sub-contracting code is used to determine whether the operation is carried out internally or if it is sent outside to a sub-contracting supplier.
|
Subcontracted prod. (field SCOITMREF) |
This is the code for a product with the category type ‘service’. |
Subcon w/c (field SCOWST) |
A subcontract work center can be used for the following:
A subcontract work center has the work center type set to 'Subcontracting'. Routing operations are validated to ensure the work center site of a 'subcontract' work center matches the site for the routing code, if defined. |
Subcontract work center group (field SCOWCR) |
This field identifies the group of work centers to which this subcontracted work center belongs. Work center groups are used to review workloads. |
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
"End range is less than Start range"The range you have selected is invalid.
"The number of resources is higher than the work center capacity"This message is displayed if the number of resources entered exceeds the maximum number of available work centers (main or labor).
"Warning, it is necessary to verify that the times (setting, operation or rate) remain correct"This warning is displayed if the operation unit (OPE) has been modified. When the units are changed you must check the coherence of the times already entered.
Version-managed routings included in the selection criteria are not processed. Update them manually.Amendments to the operations in a versioned routing are tightly controlled to minimize the impact on work orders. The selected operation is in one or more version-managed routings. The list of routings displayed will not include version-managed routings as these are excluded from the replacement process.
"No coefficient found between Operation Unit (OU) and Stock Unit (STK) (XX=OU, YY=STK)"This message is displayed if a conversion coefficient between the operation unit (OPE) and the stock unit (STK) has not been set up. A conversion coefficient of '1' has been applied (OPE/STK=1).
"Operation X/X/X. A replacement operation already exists"This message means that for the defined operation there is already a replacement operation in the routing. The initial and replacement operations have the same operation number, but they have been given different indices to distinguish them.
"Modification of operation X/X/X"This is an information message. Operations are modified when the modification run is confirmed.
"Creation of operation X/X/X"This is an information message. Replacement operations are created when the modification run is confirmed.