Hi all,
I have a use case where I want to monitor the production Lead Time of my products accross the shofloor.
Therefore, I have a table with this type of data :
My difficulty is that my shopfloor is not open 24/7.
It is open only from Monday to Friday and from 6am to 9pm (and this can be variable).
What I want is a “real” lead time when my shopfloor is open.
Anyone has already calculate similar things ?
I would appreciate a little help on how to do it.
Thanks !
Paul
Hey Paul,
This is an interesting question for a bunch of reasons but before I take you too far away from the technical question you’re asking let me start by giving you an answer that you are most likely expecting.
Writing this function in Tulip’s expression editor is possible but very annoying and unreadable. The expression editor uses some version of moment.js I think, and even that community uses plugins for this calculation. In Tulip’s case (depending on when and where you want to calculate it) I’d use @Pete_Hartnett 's custom widget method Get working hours between two dates and times. Nowadays you could also use automations and split out the expression logic so it’s easier to follow.
You might come back saying “well what about days where we only worked 6 hours or days where we did overtime?”. And this is where I’ll take you away from your original question and get at the why of it all…
What are you doing this for? Sometimes we think of lead time from the consuming location perspective, for the purpose of materials planning. How long between when I order to when I receive. I’m assuming you aren’t looking at lead time for this purpose, but instead to understand how long it takes you to process things from start to finish in a cell you own. This is a good lagging indicator of performance but I wonder how well you could dig into it for problem solving. For example, let’s say your lead time balloons out of control because a machine went down and now WIP is piling up. Lead time as a measurement goes up no matter how you calculate it and no amount of cutting days out of it will help you reason that its because a machine went down and WIP has gone up. Does this example make sense?
Maybe another way to say it is, if you are looking at lead time from the perspective of a customer I would suggest keeping the fat in the measurement and if you are doing it from the perspective of the supplier then I’d be interested in lead times from process to process and other metrics like WIP, availability, etc.
Anyway, I just like thinking and talking about this stuff. Hope that link was helpful! And if you do want to find a way to calculate lead time this way including all sorts of variables I’d be willing to help you think it through, I like technical challenges for technical challenges sake, too.
Hi Mark,
Thanks a lot for your message and for sharing your very interesting thoughts !
To answer your questions, I would like to measure both Client LeadTime and Process LeadTime.
My objective in measuring process leadtime is for performance analysis. We try to have the shortest leadtime between two operations (product waiting time before process).
It could be a way to challenge our operators team in the shopfloor. And also to check if the FIFO is respected (but for this maybe no need to have the shopfloor opening hours).
I tried to install the Custome Widget from Pete Get working hours between two dates and times but I didn’t managed to do it. If you have any ideas why, I’m interested.
Do you know if there will be updates on the “Schedule and shifts” tool in the future ?
Maybe it could be a way to answer my use case for Process LeadTime.
Thanks,
Paul
Hi Paul,
For your question regarding the custom widget, that likely was made on a much older release of Tulip and is no longer compatible with the current releases. I can check with Pete and see if he has that customer widget still on hand and can re-export (no promises there though!)
As for the schedule & shifts tool - this thread (Shift and Schedules enhancements) has the most up to date information on what the Tulip team is considering for that feature, but as of now there are not prioritized enhancements coming for it.
