WIP Tracking and Labeling Across Operations in IFS

This is great news, Björn.

We had been considering a configuration using Handling Units to support this requirement, as the customer wants to track each individual part—even though the parts are not serialized.

For example, if the lot size is 100 pieces, they want to ensure that all 100 pieces completed from the first operation are physically identified and remain available near the work center for the next operation. To support this, they are looking for a labeling approach such as:

<Order No> – <Completed Operation No> – <Sequence No>
e.g., 152435-10-01, 152435-10-02, …

The intention is to generate a unique barcode label for each WIP piece to enable clear identification and tracking on the shop floor.

With the introduction of WIP Products, do you think this type of piece-level barcode labeling can be achieved through standard configuration, or would it require customization?

Thanks again for sharing this update—it’s very helpful.

Packing of WIP products into handling units are not supported in 26R1. You can print labels for each piece, but it’s not possible to generate any unique identifier for each item, 

​@Vulcan Here is a high-level summary of a solution implemented in Apps10 at a customer without the labelling of each piece.

1. Created a zero-cost Inventory Part for the WIP part (e.g., [MAIN PART]-WIPCOMP).
2. Added this part as a component AND as a by-product in the Product Structure.
3. When the operation is reported, receive the by-product into stock.
   1. This was received into an inventory location (a cart with an ID tag on it) and then moved to the next machine. I proposed that this cart could be a Handling Unit as it would move to another machine but the customer wanted the 'mobile' inventory locations.
4. As the by-product part is also a shop order component, this by-product would then be consumed at the next operation.

Thank you Matt

​@Björn Hultgren Could you confirm this has been enabled for all types of SOs, MRO ones included ?

​@Bertrand Dousset Unfortunately not. To define WIP products when the routing is dynamic based on the repair codes is not as straight forward. Please feel free to register an idea describing the requirements for this in the MRO context. 

​@Bjorn Disappointing as the original demand was also asked for such customers. What about the repair orders that are dynamically defined by repair codes, and can even been revisited and updated during execution now ? Isn’t it the same constraint we have for MRO disassembly, MRO assembly and disposition but based on a maintenance level ?

Hi all,

Is there any chance that traceability will be enabled for WIP products in the future? (batch tracking, serial numbers). Currently, this cannot be used for items with batch tracking, as WIP items are consolidated in inventory.

Tracking the WIP products with serials and/or lot/batch numbers would basically require that completed and scrapped operation quantities also can be reported against serials and lot/batch numbers. This has been requested before, but requires a rather major implementation. (for instance here: Traceability at operation level for tracked products in production | IFS Community)

Feel free to update, or create your own idea especially for tracked WIP products!

Meanwhile, you do get some tracking if you use the Inventory Parts in Stock Reservations page as that will show the WIP products in stock by part number + shop order since the WIP products always remains reserved to the shop order.

Thank you for your answer. There is an option to set Lot/Batch Tracking / Order based for WIP product. It is a litle bit confusing.

It should not be allowed to have an inventory part with part type set to WIP product to be serial or lot/batch tracked. Looks like a bug. Will take care of that. Thanks!

I thought it was in preparation for the next release …. 😁

Hi Bjorn, 

Could you elaborate the reason?

Shouldn't the user allow to decide, “ ok , I have done my first serial and it will be in the outbound location to be transported to next WC inbound location ?” 

or for that mater with lot tracking when multiple lots are allowed per order, it would be useful to work with lot batch numbers with pack size 

Thanks

It would be valuable to support this. However, it would require introducing the capability to report the serials and/or lot numbers associated with items completed or scrapped on operations.

This change would impact multiple interfaces, including:

• Workbench
• Shop order operation reporting
• Time clock
• APIs

Each of these would require redesign.

In addition, it would introduce an extra step for operators, as they would need to explicitly report the serial or lot number when completing items.

Thank you very much @bjorn