Skip to main content
Question

Serial Traceability to Employees and Current Operation in Shop Floor Workbench

  • September 29, 2026
  • 2 replies
  • 47 views
Do Gooder (Partner)
Forum|alt.badge.img

We use Shop Floor Workbench with serial-tracked parts and are looking for end-to-end traceability of a serial throughout the manufacturing process.

Our objective is to be able to select a serial number and view:

  • All employees/users who worked on or reported against that serial
  • The operations they performed
  • The transaction date/time

In addition, we would like to identify which operation a given serial is currently in at any point in time for a specific shop order.

Is there any standard IFS functionality, report, lobby, or data source that provides this Serial → Operation → Employee traceability and current WIP operation visibility?

If not, has anyone implemented a custom report or lobby that links:

  • Serial Number
  • Shop Order Operation
  • Employee/User
  • Transaction Date/Time
  • Current WIP Operation Status

Any recommendations or best practices would be appreciated. Thanks!

2 replies

Sajid Ahmed
Do Gooder (Employee)
Forum|alt.badge.img+4
  • Sajid Ahmed
  • Do Gooder (Employee)
  • September 30, 2026

​@PabasaraK,

 IFS does not ship one standard page or lobby that gives Serial → Operation → Employee → date/time for all shop-floor activity and current WIP operation per serial in a single serial-first view. The data exists, but it is split across several standard areas; full serial-centric traceability usually needs a custom lobby/report joining operation history, inventory transactions, and optionally clockings.

 

What you can use today :

1. Shop Floor Workbench → Operation History (per operation)
 Employee/team, operation, transaction date/time, completed/scrapped qty. On newer releases (including 26R2 direction), Serial No / Lot-Batch can appear when the row is tied to an inventory transaction from qty reporting—not on every labor-only row.

2. Shop Order → Labor and Operation History, or Manufacturing → Labor and Operation History
 Same transaction data, filterable by shop order. Has operation, employee, dates, qty; no serial column, serial comes via linked inventory transaction if you extend/report on it.

3. Shop Floor Workbench → Clockings / Shop Floor Clockings
 Who worked on which operation when (setup/run/interruption). No serial on clockings.

4. Part Serials → Part Serial History

Serial lifecycle, order references, dates, user—good for where the serial has been, not a full per-operation labor log.

5. Serial number reservations (shop order / Shop Floor Workbench )
 Serial ↔ shop order—not current operation.

 

“Current operation” for a serial
 Not a standard dedicated field. Reservations are order-level; routing WIP is mainly operation/order status. Per-serial “where am I in the route?” is usually inferred (e.g. last qty report with that serial on operation history) or custom.

Practical tips

  • Use employee reporting on Shop Floor Workbench if you need named employees on history/clockings.
  • For serial on operation history, report complete/scrap with serial on serial-tracked product.
  • Custom lobby pattern: Operation History + inventory transaction (serial/lot); add clockings only if you accept employee/time without serial.
    Do Gooder (Partner)
    Forum|alt.badge.img
    • PabasaraK
    • Author
    • Do Gooder (Partner)
    • September 30, 2026

    ​@Sajid Ahmed Thank you for the response. This is pretty much AI generated as a response for me as well. 
    But my customer's requirement is to use employee/time with serials, so I cannot seem to use the standard fetatures you have suggested. 

    I am actually looking forward to see some workarounds/modifications/reports others have done to overcome this legal traceability requirement.

    Terms & ConditionsAccessibility statement