Operations include both direct product enhancement/value adding operations, as well as operations that do not themselves explicitly add any value to the product. Examples of the latter are loading, unloading and buffer operations.
For quality handling there might also be operations such as Sampling, Inspection, Re-inspection and Repair.
Id ✎
The operation id. This must be a unique number, and is explicitly set by the user creating the operation. The id cannot be changed once the operation has been created.
Name ✎
The operation name.
Description ✎
A custom operation description, for instance if you want to make it clear to use this operation instead of other operations with a similar name
Type ✎
The Operation Type for this operation.
Operation Group ✎
An operation group is created to group similar operations together. Some of the screens and reports are displayed or sorted by operation group.
Quality control can be performed registering the operation group instead of the operation.
The operation group. Mainly used for one - or more - out of three reasons:
- To set checkpoints for target handling.
- To register fault per Operation Group. This feature is a System Configuration.
- To configure Operator Messages per Operation Group.
Addressing Strategy ✎
Controls the workload of stations performing this operation. See Addressing Strategies.
SMV ✎
The SMV (Standard Minute value) is the time value calculated for a task based on the average rate of output which qualified workers will naturally achieve without over exertion provided that they know and adhere to the specified method and provided that they are motivated to apply themselves to their work.
The time is set in minutes with three decimal places. For details on how SMV calculation work, see Topic: SMV.
Piece Rate ✎
The operation piece rate value. Meaning the amount (in any given currency) the operators will earn when completing the operation. The operators pay is based on number of units or pieces produced rather than the number of hours worked.
Sampling Rate ✎
The % rate at which the production will be sampled. See Sampling
Sample To Route ✎
The Inspection Route to use when Sampling this operation.
Skip Check Node ✎
It's possible to dynamically skip an operation by configuring the Skip Check Node.
This refers to a node in the system that has a line reader. When a carrier heading to this operation passes the reader, the system will try to readress the carrier to the next operation. If successful, this operation will be skipped and carrier will head to next operation.
A scenario where this can be used is if you have a FIFO buffer used as overflow storage. All carriers are adressed to the buffer, but when they are close to the buffer, the system can try to see if there is place on the next operation.
This way, the carriers don't have to enter the buffer if they can go straight to the next operation.
⚠️ This feature is in preview and has limitations. Skipping a buffer call operation will not attempt to match the carrier to any made calls, but will instead directly address to any station in the station group.
New Bulk Factor ✎
This can be used to alter the outgoing Bulk Factor to be used when addressing to upcoming operation destinations.
This adjustment can be made when some operations make the hanging product more bulky. A typical example is mounting two sides together, which afterwards often takes more place than two separate sides hanging straight down.
Note that an original Bulk Factor is set per Article, which is used until any operation sets a New Bulk Factor. Which in turn is used until it is altered via a later operation.
The Bulk Factor tells us how much space/rail length the hanging article and its carrier takes in reference to the "normal bulk"/bulk 1.0 .
Bulk 1.0 can be determined either by the space of an empty carrier, or by the space of the smallest product and its carrier. In the case of the latter, the rail load limits to empty carrier storage should be tweaked a bit to reflect that empty carriers do not use a full bulk 1.0 .
Basic Terminal Message ✎
The basic terminal message, which is displayed on terminal when an operation starts. See Operation Messages. Overrides fallback values for terminal message sett on Operation Group and/or system settings.
Extended Terminal Message ✎
The extended terminal message, mainly used for the Web Terminal. The extended message can contain much more information than can be displayed on the terminals, and usually requires a phone/tablet that can display a web browser.
Overflow Route ✎
The Overflow Route to use when the normal destinations are full or unavailable for any other reason. If the operation has an overflow route set, the carriers will then be assigned on to the overflow side route.
Most commonly, a Mixed or FIFO buffer is used on a buffer operation in the overflow route to hold the extra carriers until they are able to be sent to their normal destination.
Express Buffer ✎
Buffer operations are normally skipped when the order line is marked as express. This flag will enable this buffer operation to still be included for express orders.
Recycle Limit ✎
This is the recycle limit for this operation.
| Value | Meaning |
|---|---|
| 0 | Recycle disabled |
| -1 | Unlimited recycle |
| (empty) | Use fallback value |
| X | Limit to X recycles |
Remember Operation ✎
Remember Operation setting for this operation
Station Group ✎
Used to set which station group should be used to perform this operation. This is the fallback value, and can be overridden by the route operation and/or the article route operation.
You can also set a custom list of stations, which will create a station group specific for just this operation.