Line properties

Production

Base machines

The first two sections of line properties asks you to select base machines, this can be any machine on the line which is included in all flows (is always used, when the line is used)

Open

Base availability selects the machine which will determine line’s state.
Described in detail here: https://ilabo.atlassian.net/wiki/spaces/LW/pages/1861976211

Base quantity selects the machine which will determine line’s production.
Described in detail here: https://ilabo.atlassian.net/wiki/spaces/LW/pages/1828454403/Counting+Production#Line-production

Base unit

Open

This is probably the most important line setting.

It determines the unit in which line production is counted, and stored. After set, it cannot be changed without interfering with historical data (all line production is stored in this unit)

It appears in the main dashboard:

And in all line production charts:

https://ilabo.atlassian.net/wiki/spaces/LW/pages/1875968001 are often used when converting from / to this unit.

• When counting OEE, expected performance is converted to this unit before comparison

• When counting line production, base quantity counter is converted to this unit

Default order unit

When creating new orders for that line, this is the default unit that is suggested in the form (can be different then the base unit)

Instantaneous performance

Please refer to machine properties:

Differential waste

When no explicit waste counters are available, you can decide to calculate waste as a difference between two machines - base quantity and any of the selected machines.

Read more:

Expected performance

There are two different measures of performance you can use to calculate line OEE

• Design performance - the maximum performance stated by the manufacturer

• Validated performance - the maximum real-life performance measured in the current conditions

Thresholds

After an order is activated on the line, PackOS starts tracking products counted in the activation period. If the order autostart threshold is set, after the specified amount of products has been reached - start is automatically triggered (and related changeover is completed).

For “Ending forced downtime“ setting a value bigger than 0 will force the line out of the current Downtime status (marked with 'Forced' tag) and back into normal states of work or failure.

For more details Ending forced downtime & Ending ongoing downtime description please refer to:

Expected OEE

Each line can be expected to meet some expectations in terms of OEE, you can define them here. They will appear in all charts, showing how much below/above the target you are.

If target is not met, OEE gauge will turn orange (the default is 80%).
If it’s below 30% of the target, it turns red.

Counting OEE

If the line is not yet ready, and you want to exclude it from factory-level OEE, you can turn on this flag.
The line will be also hidden from the factory overview in the ‘world’ view:

Allow production on downtime

Please refer to machine properties:

Threshold of a minor stop

Please refer to machine properties:

Energy

There are two options to calculate energy consumption for the line:

1. Have a central sensor which measures the total energy for the whole line. (Please see ENERGY_ACTIVE_COUNTER signal type, in ). In this case, this flag should be disabled.

2. Have separate sensors, for each individual machine. If that’s the case, you can enable this flag, and the line will aggregate total energy usage from all of the machines (regardless of the flow)

Manual way of working

There’s a possibility to enable In-process production reconcilliation for a specific line by setting property MANUAL_WAY_OF_WORKING_ENABLED to true.
There will be possibility now to use production reconcilliation without ending the order.

More here →