Single Job, Multiple Heats, How are you applying lot numbers?

Kinetic ERP
,
1

Interested to see how others assign lot numbers when you have a single job, with multiple heat numbers.

Example:
Job ~ 000123
Heat 1 ~ XGY36A
Heat 2 ~ HE5I3T

Each separate heat number needs to have its own lot in our case.

What would you use as lot numbers to differentiate the heats/lots, yet keep it associated with the job?

It would be nice to have a BPM of some sort to allow for:
Lot 000123 ~ Heat XGY36A
Lot 000123A ~ Heat HE5I3T

I know it is still linked to the job THROUGH the job, but to be able to see that through the lot number would be nice.

What do others use to accomplish this?

Thanks, Randy

2

We don’t. New material lot, new job. We’re currently making to stock. That would be more work for Make To Order though.

3

I would suggest that the lot number created is the heat number
for example 20 received with one heat number, 20 with another, this would also work with MTO

4

We’re the same as @Mark_Wonsil, new heat # goes to a new Job #. It seems like more work but it’s WAY easier to segregate and track the parts later.

I really discourage creating “secret codes” - like add an “A” to the job number, or put something in a comment field. These work-arounds require users to be very disciplined in data entry and prevent the system checks-and-balances from working correctly.

5

I understand about the “secret codes”. That just adds more BPMs that we don’t need and try to maintain. I just wanted to see how others are doing this and what seems to be the easiest way.

The way you both suggested is the cut and dry method, but agree that it creates more work, but you have to sacrifice that for accuracy at times.

6

Thanks for the insight Andy. Follow-up question to that. When you go into Lot Number Entry, it wants a Part first, and then a Lot (in this case the heat).

Is there a setting you used that turned off the default of the job as the lot number?

7

This, or serializing your parts, is the only way to maintain traceability. Source: we’re aerospace and have a NADCAP certified business unit, which is far, far stricter than what the space and jet plane peeps require. I’ve sat through many discussions on traceability, audits, and corrective actions for process failures.

I have a BPM that auto-iterates lots after each job receipt. So unless overridden by users, the system assumes each issuance OUT of a job is a separate lot. Though, I figure there’s a 50% chance it will fail when we move to Kinetic Web UI.

That also only helps you with the outputs of your job. It doesn’t, and cannot, link your output to multiple input lots.