Job scheduling

Ok, spent a lot of time on this one before asking another dumb question…

We use back scheduling, verified, made to stock so no sales/customer attached. Global scheduling.

Steps:

  1. The user does a new job, types an item/part number in, enters qty and Req By date.

  2. Several days later, does the exact same thing. With a later req by date. Same everything.

  3. Later job entered with later Req Date shows a [StartDate] newer than the first job. Yet [DueDate] is earlier in the first job vs. the newer one.

Anything else to look for? Same exact ops, customer, etc. Wondering if it is a procedural issue on our end.

I’m thinking it coming down to the ops and tied in resources as well.

Thank you all.

do you have finite scheduleing? if so… there might be a new opening where the second job got scheduled into vs when the first job was scheduled, the timeslot didnt exist at that time.
Scheduling is a complex puzzle… every time something changes, something else can open up… and it always causes questions like this.

Look at it this way… when you call a hotel, and ask for a room, you might be told that the only rooms left have queen beds… you reserve one… then a co-worker calls in several days later, and gets a king room… you say “hey, they said they only had queen rooms”… but things changed… someone cancelled, and now the king is available… The hotel doesnt shuffle everyone every time there is a reschedule.

To extend Tim’s analogy.

You are the first to ring an airline and book a flight to arrive at insights exactly 4 hours early.

Perfect!

Then your colleague rings second, but the agent says “I’m so sorry, that flight is fully booked. There is another flight the night before. You’ll be 18 hours early so you might need to extend your accommodation.”

The one who was ‘scheduled’ second ends up flying out first.

Thank you both for those analogies, makes sense…now to share that info with folks.

I guess further question is are we stupid how we do things, ways to mitigate/optimize/etc. Guess in short perhaps best practices is what I’m asking?

Thank you.

:grinning_face:

So job 2 starts before job 1, but is due after job 1?

If you look at the job scheduling board for both jobs, you should see what’s happened. Post a screenshot if you like.

The last operation of job 2 got scheduled to finish by the required date. Then something about the production quantity or resource capacity has pushed back the start date of one or more prior operations.

Example

Job 1 required 9th of Whatember.

Op 30 scheduled 7th until 9th

Op 20 scheduled 5th until 7th.

Op 10 scheduled 4th until 5th.

Starts 4th, due 9th.

Job 2 required 10th of Whatember.

Op 30 scheduled 8th until 10th

Op 20 scheduled 6th until 8th.

Op 10 cannot be scheduled on the 5th, so it’s scheduled 3rd until 4th.

Starts 3rd, finishes 10th.