Standard operations
You can use standard operations to make creating or updating routings easier. Standard operations are "template" operations that provide default information for a production task independently of the routings. Information such as which machine or work center performs the work, setup and run times, delay times, and the operation unit. They can be operations that are used regularly, or are used in more than one routing and ad hoc operations that are specific to particular circumstances.
You use this function to create standard operations independently of the routings. When adding operations to the routing, you can select a standard operation from the database. You can then change the default information provided by the standard operation for the routing operation you're creating.
Where standard operation times are expressed in a time unit that's different from the time unit defined in the routing header, the standard operation times are converted based on the routing time unit.
Prerequisites
Screen management
Home
You use the home section to define the standard operation reference and the production site.
| Standard operation (STDOPENUM) |
|
The standard operation. The definition of the fields of a standard operation is similar to that of a routing operation. Recover the standard operation data:
Note - warningWhen modifying a standard operation, the routing operations created from it are not updated.
|
| Site (FCY) |
|
The production site. The production site defined on the user record is displayed by default but can be edited. Note - tipYou can define the same standard operation code for multiple sites.
|
| Description (STDOPEDESA) |
| The standard operation description. |
Tab Time
You use this section to define the work centers used for the operation, along with their 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.
A work center is defined as a machine, a labor, or a subcontract work center. Additional work centers cannot be assigned to an operation if the number of resources needed to carry out an operation is specified.
A labor work center is associated with the main work center. Scheduling is not carried out for labor work centers because 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. You can define the number of resources to assign to the labor, the secondary work center for the operation.
If the main work center is a subcontracting work center, there's no associated secondary work center.
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. Note - informationIf 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.
|
| Setup time (SETTIM) |
|
Specifies a fixed amount of time needed to prepare a work center. It’s 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. The time can be zero. |
| 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:
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.
|
| 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. Note - informationPreparation 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. Note - informationWaiting 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:
|
| 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. Note - informationPost 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:
If the operation requires an "emergency release", a reduction coefficient can be assigned that makes it possible to completely remove any post run time. Note - warningWhen 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:
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.
Description
| Technical sheet (TECCRD) |
|
The technical sheet. It records 2 types of information:
|
| 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 |
|
Indicates if the operation is subcontracted to an outside company. Subcontract is the term used to describe the purchase of a service for carrying out an operation for a work order.
|
| 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:
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
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. |
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
| Select the Text action to view, enter, or modify text associated with the standard operation. |
Error messages
In addition to the generic error messages, the following messages can appear during the entry:
The labor work center must not be identical to the principal work center (in the labor work center)The main work center and the labor work center need to be different.
Incorrect work center typeThe work center defined is the wrong type. A labor work center needs to be defined as a Labor type and a subcontract work center needs to be defined as a Subcontracting type.
Warning, verify that the times (setup, running or rate) are still correct (in the management unit, operation unit and time unit)When there's 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’s 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’s 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)or
If the sub-contracting is activated, the sub-contracting product is mandatory! (in the sub-contracting code)
A subcontract code with the value Normal or By exception signifies that the operation is subcontracted. The subcontract product is mandatory. The main (principal) subcontract work center is assigned as the subcontract work center.