Finite Horizon Blank Title 116197

That all pretty much sounds like information right from the scheduling technical manual. Hope you didn't get charged for that! What would you have the system do? Just curious.. There is no magic button finite scheduling system (of any brand). This system does have some real opportunities for sure, but anytime you're at or near capacity on a particular resource the system will generate an exception. Seldom does it handle it in a fashion we want it to, but that makes sense to me. I've found more often than not unworkable schedules (on a job by job basis) come more from the fact that we as people and organizations feed the system inaccurate information or don't give it enough information with regards to what our real time behavior out on the shop floor is. Whether that be defined capacity, completed operations, available equipment and other human resources, or even scheduled hours vs. earned hours (how accurate are your route times), the list goes on.

Trick is to manage this to a level where you can handle the exceptions with a dedicated master scheduler (either full or part time depending on the scale of your environment) who can realign priorities, and resolve conflicts (whether they be real, or due to inaccuracies based off information we've put in the system, or not put in the system). Now, the farther away you are from your stated capacity, finite scheduling gets pretty easy, the closer you get to your stated capacity the trickier it will become to navigate around your constraints. I'm hoping they do some revamping of the scheduling algorithms in E10, but over all we've had some pretty good success in using the tools provided to finite schedule. No, it's not perfect by any means, but neither is anyone executing it...



Rob Bucek
Production Control Manager
PH: (715) 284-5376 ext 311
Mobile: (715)896-4832
FAX: (715)284-4084
[cid:1.234354861@...]<http://www.dsmfg.com/>
(Click the logo to view our site)<http://www.dsmfg.com/>

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of cesatlanta
Sent: Wednesday, November 28, 2012 9:29 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Finite Horizon



We're almost two years into E9 and 67 months into the scheduling effort.
We would like to have the engine schedule forward finite for 5 working
days and them change to infinite after that time. Based on the
documentation, that's exactly what the Finite Horizon setting is
supposed to accomplish.

We couldn't get consistent results and it appeared that the engine was
handling late jobs differently from on-time jobs which made no sense. We
engaged an Epicor resource and walked through the situation and got the
following response:

"In regards to resource scheduling I've found that the scheduling
engine looks at job's Required By dates to decide whether to
schedule finitely or infinitely. If the job's Required By date
falls inside the finite horizon, it will be scheduled using finite
capacity and only scheduled to start when a finite resource is
available. This explains why in your example all late jobs (showing in
red) are scheduled in tandem going out several weeks, well beyond your
finite horizon. On the other hand, if the job's Required By date
falls past the finite horizon, the job is backward scheduled using
infinite capacity. This means that the start date may fall within the
finite horizon and thus stack up against fully loaded resources. In
addition, the finite horizon calculation is based on calendar days,
including weekends and holidays. For example, if you select five (5)
days, your finite horizon will be the MRP Start date plus 5."

Has anybody ever successfully set-up finite scheduling in E9 or are we
just the latest victim of the flawlessly executed sales demo?

[Non-text portions of this message have been removed]



[Non-text portions of this message have been removed]
We're almost two years into E9 and 67 months into the scheduling effort.
We would like to have the engine schedule forward finite for 5 working
days and them change to infinite after that time. Based on the
documentation, that's exactly what the Finite Horizon setting is
supposed to accomplish.

We couldn't get consistent results and it appeared that the engine was
handling late jobs differently from on-time jobs which made no sense. We
engaged an Epicor resource and walked through the situation and got the
following response:

"In regards to resource scheduling I've found that the scheduling
engine looks at job's Required By dates to decide whether to
schedule finitely or infinitely. If the job's Required By date
falls inside the finite horizon, it will be scheduled using finite
capacity and only scheduled to start when a finite resource is
available. This explains why in your example all late jobs (showing in
red) are scheduled in tandem going out several weeks, well beyond your
finite horizon. On the other hand, if the job's Required By date
falls past the finite horizon, the job is backward scheduled using
infinite capacity. This means that the start date may fall within the
finite horizon and thus stack up against fully loaded resources. In
addition, the finite horizon calculation is based on calendar days,
including weekends and holidays. For example, if you select five (5)
days, your finite horizon will be the MRP Start date plus 5."

Has anybody ever successfully set-up finite scheduling in E9 or are we
just the latest victim of the flawlessly executed sales demo?



[Non-text portions of this message have been removed]