Routing operations

• 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).

• Leave this check box clear to update existing operation details.
  The field Application date is not available.
  Routing operations that meet the entered selection criteria and are valid today (the run date) are selected.
• Click (select) this check box to replace operations.
  The field Application date is available for entry or selection. This field defaults to today's date. If the replacement is valid from a later date type in, or select the effective date.
  Routing operations that meet the entered selection criteria and are valid on and after the effective date are selected.

• 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.

• 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.
It is an entity for which the load needs to be planned and/or the production times need to be tracked.

• 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:

• No. The operation is never subcontracted. You cannot assign a subcontract product or a subcontract work center to this operation.
• Normal. The operation is always subcontracted. The factory does not have the required skills or toolings. The subcontract product is mandatory. The main (principal) subcontract work center is assigned as the subcontract work center.
• By exception. The operation is carried out internally. It can be subcontracted in exceptional circumstances such as when instances of overload or temporary issues occur. The subcontract product and the subcontract work center are mandatory.

• 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: 

• Managing load issued to a subcontractor;
• Tracking subcontracted hours (if used for 'generic' subcontracted work);
• To represent a specific subcontractor.

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.

 An error message is displayed if you refer to tables which are not generally used by the configurator, or to unknown variables.

• 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.

• 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.

 An error message is displayed if you refer to tables which are not generally used by the configurator, or to unknown variables.

• 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:

• expressed in hours or minutes (see the time unit),
• assigned to 1, 100, 1000 or a lot of units of the operation based on the management unit,
• proportional or fixed based on the type of operation time
  Example: Time unit = Hours Time type = proportional Management unit = Time for 100 Operation time = 2 Operation unit = Kg Finished product unit = A REL-OPE conversion coefficient = 0.5
  The operation time is equal to 2 hours for 100 Kg. If the Work Order is launched for 1000 units of finished product, the time necessary to produce this operation is 10 hours to obtain 500 Kg.

• 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). Preparation time is not applied to the work center load.

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). Waiting time is not applied to the work center load.

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:

• When scheduling waiting time the calendar for the defined resource is applied. Waiting time will be interrupted by the one hour break.
• When scheduling time for the additional resource the calendar for the defined resource is applied. Time will be interrupted by the one hour break.

• 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:

• When scheduling post run time a neutral 24 hour calendar for the defined resource is applied. Post run time is not, therefore, interrupted by the one hour break.
• When scheduling time for the additional resource the calendar for the defined resource is applied. 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 post run time.

 When scheduling time for these resources, if both waiting time and post run (post operation) time has been declared for the operation only the largest of the two values is used.

• 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.
This field is only available for entry if the labor work center is entered.

• 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.
The number of units is expressed according to the time unit.
It can only be entered if the operation time type is the "rate".

• 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'.

• 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:

• Mixing time (operation 1) is expressed for a lot with Kilogram as the unit;
• Extrusion time (operation 2) is a rate in meters per hour;
• Cutting time (operation 3) is expressed in hours per unit.

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.
Efficiency makes it possible to correct the standard times of the routing (multiplying factor) according to the used resource.

Two efficiency rates are managed depending on the following:

• Work center: The rate is applied to all the routing operations that will take place at the work center.
• Routing operation: The rate only applies to the considered operation.

If both factors are entered, they add up.
The calculated operating time is corrected in the following way: work center efficiency * operation efficiency * time.

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.

• If WSTEFFINH is set to Yes, the efficiency entered in the work center is suggested by default when creating the routing operation with this work center. The calculated runtime = runtime entered * 1 / operation efficiency.
• If WSTEFFINH is set to No, the efficiency entered in the work center is combined with that entered in the routing operation. The calculated runtime = runtime entered * 1 / work center efficiency * 1 / operation efficiency.

• Formula (field EFFF)

Enter, select or build an Enterprise Management filter calculation expression using the formula editor.

 An error message is displayed if you refer to tables which are not generally used by the configurator, or to unknown variables.

• 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.

 An error message is displayed if you refer to tables which are not generally used by the configurator, or to unknown variables.

• 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.

 Operations based on a standard operation are not updated if the standard operation is changed.

• 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:

• setting coefficient,
• operating coefficient applied to the setting time and operating time of the principal work center.

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.
The following values are possible:

• Proportional: the production time is proportional to the released quantity. It is expressed in hours and minutes (based on the time unit) for a given number of units (based on the management unit and basic quantity).
  With a proportional time type, the production time is entered in the operation time section and the rate section cannot be assigned.
• Rate: the production time is proportional to the released quantity. The rate is used to express the time in number of units per hour or minute, depending on the time unit.
  With a rate time type, the production time is entered in the rate section and the operating times, management unit and basic quantity cannot be entered.
• Fixed: the production time is independent of the released quantity. This time is expressed in hours or in minutes depending on the management unit.
  With a fixed time type, the production time is entered in the operating time section and the management unit, basic quantity and rate cannot be entered.
  

• 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.
The management unit makes it possible to express the operation time for 1, 100, 1000 or a lot of units of parts to be produced.
If the management unit is chosen by lot, the size of the lot can be entered in the basic quantity.

• Base quantity (field BASQTY)

The basis quantity entry depends on the management unit.
In effect, if the time is expressed for 1 unit, for 100 units or for 1,000 units, the basis quantity is forced, respectively to 1, 100 or 1,000 units.
However, if the time is expressed for a lot, the basis quantity can be entered. If the processed routing code is dedicated to a site, it is initialized by the lot size of the product-routing for this site.
The basis quantity entry format depends on the operation unit.

• 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:

• expressed in hours or minutes (see the time unit),
• assigned to 1, 100, 1000 or a lot of units of the operation based on the management unit,
• proportional or fixed based on the type of operation time
  Example: Time unit = Hours Time type = proportional Management unit = Time for 100 Operation time = 2 Operation unit = Kg Finished product unit = A REL-OPE conversion coefficient = 0.5
  The operation time is equal to 2 hours for 100 Kg. If the Work Order is launched for 1000 units of finished product, the time necessary to produce this operation is 10 hours to obtain 500 Kg.

• 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.
The number of units is expressed according to the time unit.
It can only be entered if the operation time type is the "rate".

• 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.
Efficiency makes it possible to correct the standard times of the routing (multiplying factor) according to the used resource.

Two efficiency rates are managed depending on the following:

• Work center: The rate is applied to all the routing operations that will take place at the work center.
• Routing operation: The rate only applies to the considered operation.

If both factors are entered, they add up.
The calculated operating time is corrected in the following way: work center efficiency * operation efficiency * time.

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.

• If WSTEFFINH is set to Yes, the efficiency entered in the work center is suggested by default when creating the routing operation with this work center. The calculated runtime = runtime entered * 1 / operation efficiency.
• If WSTEFFINH is set to No, the efficiency entered in the work center is combined with that entered in the routing operation. The calculated runtime = runtime entered * 1 / work center efficiency * 1 / operation efficiency.

• 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.
This field is only available for entry if the labor work center is entered.

• 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). Preparation time is not applied to the work center load.

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). Waiting time is not applied to the work center load.

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:

• When scheduling waiting time the calendar for the defined resource is applied. Waiting time will be interrupted by the one hour break.
• When scheduling time for the additional resource the calendar for the defined resource is applied. Time will be interrupted by the one hour break.

• 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:

• When scheduling post run time a neutral 24 hour calendar for the defined resource is applied. Post run time is not, therefore, interrupted by the one hour break.
• When scheduling time for the additional resource the calendar for the defined resource is applied. 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 post run time.

 When scheduling time for these resources, if both waiting time and post run (post operation) time has been declared for the operation only the largest of the two values is used.

• 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:

• Mixing time (operation 1) is expressed for a lot with Kilogram as the unit;
• Extrusion time (operation 2) is a rate in meters per hour;
• Cutting time (operation 3) is expressed in hours per unit.

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)

The Stock unit-Operation unit conversion coefficient is used to convert the released quantity of finished product into the quantity of the operation according to its unit.
It belongs to the coefficient table.

• 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.
It can take the following values:

• No: the operation is never sub-contracted. The sub-contracting product and the sub-contracting work center cannot be assigned,
• Structural: the operation is systematically sub-contracted. The factory does not have the required skills or toolings. The sub-contracting product is mandatory and the sub-contracting work center cannot be assigned. it is loaded with the principal work center, which, in this case, must be of the sub-contracting type.
• Temporary (conjuncture related): the operation is carried out internally in priority, but in case of overload or temporary problem, it can be sub-contracted. The sub-contracting product and the sub-contracting work center can be assigned and are mandatory.

• Subcontracted prod. (field SCOITMREF)

This is the code for a product with the category type ‘service’.
The service can be performed by an external subcontractor.

• Subcon w/c (field SCOWST)

A subcontract work center can be used for the following: 

• Managing load issued to a subcontractor;
• Tracking subcontracted hours (if used for 'generic' subcontracted work);
• To represent a specific subcontractor.

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.