Standard Operations
Standard operations are used to make the routing update easier: these are "template" operations that are used to define the data for a production task independently of the routings.
During the creation of the routing operations, it is possible to choose a standard operation from the library, to recover its default information and to modify this in order to adapt it to the context of the routing being considered. In most cases, only the information on the running times shall be reviewed, the other data (work centers, texts, toolings etc.) can be identical for a same production operation common to several products.
The link between a routing operation and the standard operation used in its creation is saved for information purposes. If the standard operation data has been changed, there is no update of the routing operations that have been created with the help of this standard operation.
Prerequisite
Screen management
Header
Field descriptions
| Standard operation (field STDOPENUM)
|
|
The standard operation is a "template" operation used to create or modify the routing operations.
The definition of the fields of a standard operation is very similar to that of a routing operation.
Recover the standard operation data:
- if the operation unit is mentioned in the standard operation, it is used again, otherwise, the stock unit of the product in the routing is used.
If not entered, the conversion coefficient is extracted from the coefficient table
- The times (rate, setting time and operating time) are converted if the time unit of the routing header is different from that of the standard operation.
The standard operation is referenced in the operation that called it as a template.
 When modifying a standard operation, the modifications are not passed on to the associated operations.
|
| Site (field FCY)
|
|
It is mandatory to enter a site for a standard operation.
The production site associated with the user is proposed by default. It can be modified by another site authorized for the operator, depending on its authorizations.
The chosen site conditions the choice of the work centers on which this operation is defined. These work centers must exist at the site in question.
It is possible to define the same standard operation code on two different sites. |
| Description (field STDOPEDESA)
|
|
Tab Time
This tab is used to describe the work centers of the operation, along with the running times. The times of the standard operation are entered in a time unit chosen in hours or in minutes, and for a given stock (or production) unit.
Field descriptions
Resources
| Work center (XWSTTYP)
|
|
Identifies the type of operation that's performed on the work center. This might be a machine, a labor, or a subcontracted operation.
Subcontracting type work centers are managed externally by subcontract suppliers.
|
| WST
|
|
Identifies the production resource to use for the operation. This work center is the main or principal work center for the operation.
The resource can be a machine, a labor, or a subcontract work center. Operation scheduling considers the availability of the work center.
Subcontracting type work centers are managed using the lead time defined in the subcontract product record. Subcontract operation times are not used by the scheduling.
|
| WSTDES
|
| The description of the work center.
|
| Number (WSTNBR)
|
|
The number for this particular production resource that are needed for the operation. For example, if 3 people are needed to operate a specific labor work center, enter 3.
|
| Labor wk C (XLABWSTTYP)
|
| Identifies the type of operation that's performed on the labor work center.
|
| LABWST
|
|
The labor work center.
When creating a routing operation, the work center site needs to match the site for the routing code, if defined.
Scheduling is not carried out for labor work centers. They’re 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 a Subcontracting type work center, there is no associated secondary work center.
|
| LABWSTDES
|
| The description of the labor work center. |
| Number (LABNBR)
|
|
The number for this particular production resource that are needed for the operation. For example, if 3 people are needed to operate a specific labor work center, enter 3.
|
Charged time
| Time unit (TIMUOMCOD)
|
|
Defines how time for the operation is expressed. The time unit can be hours or minutes.
The time applies to the setup time, run time, and the rate.
|
| Time type (ROOTIMCOD)
|
|
The operation time type applied to the production time entry.
- Proportional: The production time is proportional to the released quantity. It’s expressed in hours and minutes, as based on the time unit for a given number of units, which is based on the management unit and base quantity.
With a proportional time type, the production time is entered in the operation time section. 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. 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. The management unit, basic quantity, and rate cannot be entered.
|
| Setup time (SETTIM)
|
|
Specifies the actual time that it takes to prepare the work center.
This time forms part of the work center load. It’s expressed in either the time unit specified in the routing header or in the standard operation itself.
|
| Management unit (TIMCOD)
|
|
Depending on the resource being used, the number of decimals for 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, 1,000, or a lot of units of parts to be produced.
If the management unit is by lot, the lot size can be entered as the base quantity.
|
| Base quantity (BASQTY)
|
|
The base quantity depends on the management unit.
In effect, if the time is expressed for 1 unit, for 100 units or for 1,000 units, the base quantity is forced, respectively to 1, 100 or 1,000 units.
However, if the time is expressed for a lot, the base quantity can be entered. If the processed routing code is assigned to a site, it's initialized for the lot size of the product-routing for the site.
|
| Run time (OPETIM)
|
|
The time needed to manufacture the product described in the routing.
The operating time:
|
| Rate (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 Rate.
|
| % efficiency (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.
2 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 the work center. The calculated run time = run time 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 run time = run time entered * 1 / work center efficiency * 1 / operation efficiency.
|
| Shrinkage in % (SHR)
|
|
This percentage is used to balance the quantities on the production operations based on the released quantity.
It’s possible to introduce a shrinkage percentage on the work center, which is used to weight the planned run times for an operation using the work center by a loss or gain on the quantity produced for the work center.
|
Labor factor
| Setup time (SETLABCOE)
|
|
The coefficient applied to the planned setting time to obtain the setting 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.
|
| Run time (OPELABCOE)
|
|
The coefficient applied to the planned operation time 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. They're not in the stock unit of the finished product using the routing.
|
Off time charge
| Preparation (PRPTIM)
|
|
Preparation time is "waiting time" set at the start of an operation.
Preparation time is not applied to the work center load.
Preparation time is always expressed in hours. It does not use the time unit defined in the routing header (Time unit field).
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. When preparation time is used for setting time at the start of an operation, the resource needs to be available.
When scheduling preparation time, the calendar for the defined resource is applied. This means that if, for example, a machine or labor work center runs from 08:00 to 12:00 and from 13:00 to 17:00 with a 1 hour break from 12:00 to 13:00, preparation time will be interrupted by the 1 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.
|
| Wait time (WAITIM)
|
|
Waiting time is "delay time" that occurs after an operation. It’s non-productive time.
Waiting time is not applied to the work center load. It's for periods such as drying time or cooling time that occurs after a process was 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 (Time unit field).
If machine time is needed for an operation during the waiting time, you should add a new operation to the routing. A machine might be needed, for example, for drying or cooling components at a work center. The additional operation needs to be for the appropriate resource type, such as "cooler".
When scheduling time for these resources if, for example, a machine or labor work center runs from 08:00 to 12:00 and from 13:00 to 17:00 with a 1 hour break from 12:00 to 13:00:
- When scheduling waiting time: If the resource needs to be available, the calendar for the resource also applies to the waiting time. For this example, time will be interrupted by the 1 hour break.
- When scheduling time for the additional resource: The calendar for the defined resource also applies to the waiting time. The additional resource time will be interrupted by the 1 hour break.
|
| Post op time (PSPTIM)
|
|
Post operation, or post run time is a "deadline" that occurs after waiting time. It's non-productive time.
Post run time is not applied to the work center load. It's typically "transfer time", or a transition period from one work center to the next work center that occurs after a process was completed on a machine and until the machine can next be used.
Post run time is always expressed in hours. It does not use the time unit defined in the routing header (Time unit field).
If operator time is needed for an operation during the post run time, you should add a new operation to the routing. An operator might be needed, for example, for the transportation or carriage, or the transition between 2 work centers. The additional operation needs to be for the appropriate resource type, such as "carrier".
When scheduling time for these resources if, for example, a machine or labor work center runs from 08:00 to 12:00 and from 13:00 to 17:00 with a 1 hour break from 12:00 to 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 1 hour break.
- When scheduling time for the additional resource, the calendar for the defined resource is applied. Time will be interrupted by the 1 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 time was declared for the operation, only the largest of the 2 values is used.
|
Unit
| Operation UOM (OPEUOM)
|
|
Work order operation quantities are expressed in the operation unit. Use the operation unit to express the operating time in a different unit to that of the product being produced by the routing.
Example
A product managed by unit is subject to 3 different operations, none of which produce intermediate stock:
- Operation 1 = Mixing time, expressed for a lot with kilogram as the unit
- Operation 2 = Extrusion time, expressed as a rate in meters per hour
- Operation 3 = Cutting time, expressed in hours per unit
There's 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.
|
Tab Management
This section regroups technical information such as the tooling and workbench, and information concerning the potential subcontracting of the operation.
The elements needed for subcontracting are the subcontracting product and the work center. You can also specify the preferred subcontract supplier and a reference price.
The supplier can be modified on the routing and again on the work order.
Field descriptions
Description
| Technical sheet (TECCRD)
|
|
The technical sheet. It records 2 types of information:
- The text describing the control process or the operating mode
- A set of questions/answers in order to introduce a parameter entry during quality control or production tracking.
The answers provided can be controlled using preset values and to provide statistics.
|
| Operation plan no. (OPEPLNNUM)
|
|
The name of the workbench the operation refers to.
|
| Operation image (OPEROUPCT)
|
| The name of the image the operation refers to.
|
Miscellaneous
| Tools (EQUNUM)
|
|
The product reference for the tool. The product needs to have a Tool category.
|
| Fixture (FXGNUM)
|
|
This field is not associated with any processes.
|
| Program (PRGNUM)
|
| The name of the program that the operation refers to.
|
Subcontract
| SCOCOD
|
|
Defines if an operation is carried out internally or if it's sent to an external subcontract supplier.
- No: The operation is never subcontracted. You cannot assign a subcontract product or a subcontract work center to the 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.
|
| Product (SCOITMREF)
|
|
The service to be carried out by the subcontractor to execute the operations. The product needs to have a Service category.
|
| Work center (SCOWCR)
|
| The group of work centers this subcontracted work center belongs to. Work center groups are used to review workloads.
|
| XSCOWSTTYP
|
| Identifies the work center as being a subcontract work center.
|
| 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 that the work center site of a subcontract work center matches the site for the routing code, if defined.
|
| SCOWSTDES
|
| The description of the work center.
|
| BP (BPRNUM)
|
| The business partner code.
|
| Address (BPAADD)
|
| The ship-to address code.
|
| Reference price (REFPRI)
|
|
The generic price to apply to a subcontract service. This price will be applied (by operation unit) throughout the order process.
|
| CUR
|
| The currency for the subcontract service price. |
Tab Finite capacity
Field descriptions
Detailed scheduling
| Grouping criterion (SCHGRP)
|
|
The operation grouping code.
|
| Grouping formula (SCHGRPFOR)
|
|
The formula used to intervene in the formatting of the grouping code during release.
|
| Grouping formula (field SCHGRPFOR)
|
|
Formula used to intervene in the formatting of the grouping code during release.
|
Reports
By default, the following reports are associated with this function :
ROUOPESTD : Standard operations listing
This can be changed using a different setup.
Menu Bar
Text / Text
|
This menu is used to associate a text with the standard operation.
|
Error messages
In addition to the generic error messages, the following messages can appear during the entry :
The labour work center must not be identical to the principal work center (in the labour work center)
When a labour work center is entered in an operation, it must be different from the principal work center.
Incorrect work center type
In the labor work center: the type of the labor work center MUST be labor.
In the sub-contract work center: the sub-contract work center must be of sub-contract type.
Warning, verify that the times (setup, running or rate) are still correct (in the management unit, operation unit and time unit)
When there is a change to the units, this warning is used to stress the importance of coherence with the times already entered.
The management unit is by lot: the operation unit is mandatory (in the operation unit)
If the time is to be expressed by lot, it is necessary to enter the operation unit in order to specify that the time indicated is for a given quantity, expressed in this unit.
The management unit is by lot: the basic quantity cannot be zero (in the basic quantity)
If the user has chosen to express the time by lot, it is necessary to enter the base quantity in order to specify that the time specified is for this quantity expressed in the operation unit.
If the sub-contracting is structural, the principal work center must be of sub-contracting type (in the sub-contracting code)
A sub-contract code with the value "structural" signifies that the operation processed is always a sub-contract operation. Also, it is mandatory that the principal work center is of sub-contracting type.
If the sub-contracting is activated, the sub-contracting product is mandatory! (in the sub-contracting code)
This message appears if a modification has been requested for the sub-contracting code in such a way that this code has switched to the values "structural" or "temporary" and that the sub-contracting product is not entered.
Tables used