If you are running multiple products on the same line, which have different targets, we can use the batch feature to set product-specific targets. From batch tracking, we can track the following KPIs:

• Cycle time per product
• Duration time for different batch sizes per product
• Time loss data for technical stops, speed loss, change-over activities, and non-production related activities per product

Targets can also be set for each OEE category to create high-level and summarized KPIs. These are often used to compare different line performance or to consolidate a manufacturing area's performance.

Using Products

Products need to be configured to use batches. Products can be managed in the Batch tab on every line. Products can be used to set specific expected, validated speed, and data multiplier depending on what product is running on the line. The item number needs to be unique for each product.

Products can be configured with custom product parameters, such as barcode, material size, packaging material etc. The product parameters can be used to create a changeover matrix, setting targets for the changeover depending on changes in product parameters. 

Using Batches

• Batches can be managed in the Batch tab on every line
• Only one batch can run at a time (green)
• Multiple batches can be planned in the future (yellow “pending”)
• Batches that are completed will be marked blue

Scheduling Batches

• Batches are planned using the plus symbol in the lower right corner.
• Products can be used to as presets for the data multiplier, expected, and validated speed on the line (watch the video above)

When planning and running batches, it can be helpful to know when in the future the batch will be completed. Per default, Factbird calculates the time of completion using the expected speed of the product. This timestamp is visible in the planned stop column in the batch table.

Taking into account the shift schedule

When calculating the time of completion for a batch, it’s possible to have the system take into account only the available time of the Shift schedule. That means you get a better idea of when your batches will end, based on the schedule you’ve entered in Factbird.

ℹ️ Example
Let’s say your line only runs from 8-16 every day. It’s currently 10:00, and you are running a batch that needs 10 more hours to be completed. With the new setting enabled, the ETC for the batch will be 12:00 the next day. With the setting disabled, the ETC will be 20:00 the same day.

To enable this functionality, go to line settings, “Batch”, and enable the setting:

After enabling the setting, you will see that the planned stop for pending batches will take into account the available time in the shift calendar. That means, if there isn’t enough time in a shift to complete the batch, the system will find the next available time in the calendar and estimate based on that. Additionally, the estimated time of completion for running batches will also take into account the available time in the shift calendar: