Don't start a job that won't be finished before shift ends

Question

question

Dylan R2 asked Oct 24, '18 Jason Lightfoot edited May 10, '19

Don't start a job that won't be finished before shift ends

I have a model with an operator working two shifts each day during the week, with fairly lengthy processing times. I would like to change my model so if the operator doesn't have enough time to complete the whole run before the end of the day, he will complete the setup and wait to begin processing during the next work period.

Software Version:

FlexSim 18.2.2

manufacturing schedules operator and resource processing schedule processor

· 1

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

tannerp commented · Oct 24, 2018 at 05:48 PM

@Dylan R2, If you add a label that identifies the length of the process time, you could use a decide activity to either delay or send the token on.

Would it be possible for you to upload your model or a sample of it so we can find something that would work in your situation?

2 ·

Answer 1 · 2019-05-10T14:39:08Z

Jason Lightfoot answered May 10, '19 Jason Lightfoot edited May 10, '19

Assuming you're using a date-based timetable/calendar to define your shift stops - in the upfunction (shown as Resume Function in the GUI functions) you can find the time of the next planned stop for a given timetable calendar using this:

double timeofnextplannedstop=GLOBAL_DELAYINDEFINITE;
Table calendar=getvarnode(current,"table");
if (calendar.numRows>tablerow)
	timeofnextplannedstop=calendar[tablerow+1][1]-getvarnum(current,"modelstarttime");

So record that time as the shift end somewhere, and refer to it after setup to see if you have enough time

double timetoshiftend =timeofnextplannedstop-time();
if (processtime<=timetoshiftend)

//  START or PULL etc...<br>

· 1

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Jason Lightfoot ♦♦ commented · May 10, 2019 at 02:41 PM

If your object is a member of multiple timetables this becomes harder - in the past I've written functions to consolidate them into one "netavailability" timetable so that the above code would still work on the "net calendar".

0 ·

question