| Field | Explanation |
|---|---|
| Quantity factor | Adjust the number of pieces on the specific operation. Example: An order produces 100 tables. The current operation produces table legs. For every table on the production order, this operation produces 4 table legs. The quantity factor is set to 4. The capacity on the operation is indicated for one table leg. Has only effect when the work load is calculated based on capacity and quantity. Can also be used when different unit of measures are used. E.g. when order size is in tonne and you want to specify the capacity in kg. In this case the quantity factor is set to 1000. Also see difference between Quantity and Workload factor explained on the Workload factor field |
| Workload factor | Similar to Quantity factor. The difference is that the workload factor impacts on the workload both when the workload is calculated on the basis of constant workload as well as capacity and quantity. Another difference also is, that the quantity factor will impact the quantity consumed by BOM-lines. The workload factor will not impact BOM-line consumptions. |
| Settings: Qty / qty fact. | Is used when the quantity must be divided by the quantity factor. An example use case is business card printing. 8 business cards will be cut from a single sheet of paper. In this case enable Qty / qty fact. and set Quantity factor=8. Effectively the quantity going through the operation will now be 1/8. We can cut 10 sheets an hour (6 minutes per sheet), so we specify capacity=10. If creating a production order for 16 business cards, the calculated workload of the operation is now (16 / 8) * 6 = 12 minutes |
| Workload | The work load indicates the number of hours to perform this operation. The work load can be fixed (white background) or calculated based upon the capacity (grey background). Double click in the field to make it active. |
| Capacity | Capacity is used when the workload for an operation must be calculated as function of the quantity and the capacity.
Settings: Cap. from res. The capacity is obtained from the resource rather than from the operation. See edit resource description. |
| Quantity | The quantity to be produced in this operation. If the quantity is changed it is only the quantity for this operation that is changed. This means the other operations in the order can have a different quantity. |
| Prev. queue time | Hours before the operation starts. Prev. queue hours are reserved independent of the resource calendar. Both working hours and non working hours are used. The hours are marked as black line in front of the operation. |
| Setup time | Hours for setup on the machine before the production starts. The hours specified are reserved according to the resource calendar. Only working hours are used. The hours specified is shown as a load on the resource. In the menu Functions->Settings->General set the “Apply resource efficiency on setup time” if you want to let the resource efficiency have effect on the Setup time. |
| Switch over time | Hours for switching over the machine after production is finished. The hours specified are reserved according to the resource calendar. Only working hours are used. The hours specified is shown as a load on the resource. |
| Post queue time | Hours after the operation is finished before the next operation in the order must start. E.g. planned/necessary buffer time before the next operation. Post queue hours are reserved independent of the resource calendar. Both working hours and non working hours are used. The hours are marked as a black line after the operation. |
| Transport time | Hours for transport to the next operation. The hours specified are reserved according to the resource calendar. Only working hours are used. The transport time does not load the resource. The hours are marked as a black line after the operation. |
| Start- and end time | Edit start- and end time for the selected operation. The fields shows the original planned start- and end times for the selected operation, that is before status was changed to Started and any progress has been reported. |
| Duration | The duration of the operation, that is the time from the operation starts till it ends. |
| Efficiency | Operation efficiency: The efficiency of the selected operation.
Resource efficiency: The efficiency of the resource the selected operation is placed on. Example: an operation with workload=1 hour and operation efficiency=0.5 with have a duration of 2 hours. The operation will each hour book 0.5 hour on the resource For an elaborate description please see the Operation efficiency chapter. |
| Planning factor | Works similar to the operation efficiency, but without having any effect on the calculated workload of the operation. Example: an operation with workload=1 hour and operation planning factor=0.5 will have a duration of 1 hour. The operation will each hour book 1.0 hour on the resource. Planning rules will however allow two operations with planning factor=0.5 to run in parralel on the resource See example table below |
| Overlap | Specify an overlap to the following operation in the same order. For an elaborate description please see the Controlled overlap chapter. |
| Settings: Locked | Lock the start and end time of the operation. When the operation is locked a lock icon is shown on the operation in the gantt-chart, and it is not possible to move or reschedule the operation |
| Settings: Hard link next | Lock the start of the next operation to the end of this operation. When the operation is hard linked to the next operation a icon is shown on the line between the two operations in the gantt-chart. When moving or rescheduling one operation the hardlinked operation will always follow NOTE: Hard linked operations are disabled into and out of Operation groups |
| WASTE ADDITIONS: | Important: Most of these settings becomes visible when “Show Waste” is selected |
| Settings: Show waste | Should the Waste Factor, Input Quantity and Output Quantity fields be shown |
| Waste Factor | The waste factor of the operation defines the percentage of the quantity that is lost during the operation. E.g. a value of 0.1 means a waste of 10%. Quantity In – (Quantity In * Waste Factor) = Quantity Out The production order the operation belongs to has a setting next to it’s quantity field called “Quantity In”: If “Quantity In” is set: The output quantity is calculated based on the quantity coming from the previous operation and the waste factor of the operation. ( Quantity Out = Quantity In * (1.0 - Waste Factor))If “Quantity In” is NOT set: The input quantity is calculated based on the required output quantity (input for the next operation) and the waste factor of the operation. ( Quantity In = Quantity Out * (1.0 / (1.0 - Waste Factor))) |
| Quantity In | The calculated quantity coming INTO this operation from the previous operation. Please observe impact of “Quantity In” setting at production order level, as explained in Waste factor NOTE: The calculations are based on the quantity set on the order, not on quantities set on individual operations!! |
| Quantity Out | The calcualted quantity going OUT of this operation to the next operation. Please observe impact of “Quantity In” setting at production order level, as explained in Waste factor NOTE: The calculations are based on the quantity set on the order, not on quantities set on individual operations!! |
| Capacity on output | This option decides whether the capacity applies to the input quantity or the output quantity When calculating the workload based on capacity this option decides wether the capacity applies to the input quantity or the output quantity. If set: Workload = Quantity Out * Capacity If NOT set: Workload = Quantity In * Capacity |
Planning factor examples
A few examples of combining planning factor and different operation and resource level settings
| Resource calendar factor | Operation efficiency | Planning factor | Workload | Calculated workload | Number of operations planned at same time. |
|---|---|---|---|---|---|
| 2 | 1 | 1 | 1 | 1 | 2 |
| 2 | 2 | 1 | 1 | 2 | 1 |
| 2 | 1 | 2 | 1 | 1 | 1 |
| 2 | 1 | 0.25 | 1 | 1 | 4 |
An example usage of the planning factor is an operator attending 3 machines. In that case the planning factor of the operator operation can be set to 0.33, without the duration of the operation being affected by this change.
Post your comment on this topic.