To put it bluntly, in retrospect, EVERYTHING demonstrated during the sales process was pure B.S.
That said, once the limits of a system are understood, workarounds can almost always be put in place. Vantage is no different.
Rob Brown
That said, once the limits of a system are understood, workarounds can almost always be put in place. Vantage is no different.
Rob Brown
--- On Tue, 5/20/08, Barbara Kite <barken2008@...> wrote:
From: Barbara Kite <barken2008@...>
Subject: Re: [Vantage] (unknown) - Job Detail tree: 'red dot' material availability
To: vantage@yahoogroups.com
Cc: BARBARA.KITE@...
Date: Tuesday, May 20, 2008, 11:35 AM
Robert,
Thanks for the insight. We have ignored them and it was disappointing because during the sales process this was shown to us and we were thrilled to have this feature. Misleading? Absolutely..
Barbara
----- Original Message ----
From: Robert Brown <robertb_versa@ yahoo..com>
To: vantage@yahoogroups .com
Sent: Tuesday, May 20, 2008 3:04:38 AM
Subject: Re: [Vantage] (unknown) - Job Detail tree: 'red dot' material availability
Forget the 'red dots' (or lack there of)... They absolutely DO NOT reliably indicate what Epicor documentation claims (up to v8.03.404B) re: true material availability. Train your people to completely ignore them and instead to use Material availability/ status check Action from Job Entry.
You can change how tree views are displayed but I've yet to see a way to turn off the process responsible for the misleading material availability color coding.
The global scheduler is pretty much trash as well. Several known incident reports filed and still no (believable) pending patch resolution dates given.
1. "Calculate Global Scheduling Order" uses wrong job header dates in its calculation.
2. Under typical 'real world' capacity/load conditions, backward finite scheduled jobs will forward schedule and, even if using prioritized scheduling codes, will give you the jobs you need least, first - and those you need the most, late.
3. OPs and resources set for parallel processing fail to do so (and scatter those job schedules in general).
All (but perhaps 3.) can be overcome well enough with some customization and pre-global mass data manipulation. Anyone who blindly allows a complex (never truly reflecting actual daily reality) resource/scheduling model to run their operations is naive anyway - using ANY scheduler product. (Skilled PEOPLE run successful business operations - not computer models. The models are just aids.)
If you are experiencing any of these issues and they are really hurting you, search epicweb for the incident reports and add your name to them so they get more priority from the programming division.
Rob Brown
--- On Mon, 5/19/08, Barbara Kite <barken2008@ yahoo. com> wrote:
From: Barbara Kite <barken2008@ yahoo. com>
Subject: [Vantage] (unknown)
To: vantage@yahoogroups .com
Date: Monday, May 19, 2008, 10:08 PM
We implemented 8.03.05F a few months ago and have an issue that we haven't been able to resolve nor has Epicor been able to help us.
When a job is built and the tree on the side shows red dots, we cannot rely on the red dots (or lack of them) to tell us if we actually have the material available.. Sometimes the red dot appears and we have plenty in stock. If we go to job manager I can look to see what other jobs are scheduled that requires that part and cannot see where there is a constraint. Other times when the red dot does not appear, I will look at job manager and I can see where another job receipt or purchase receipt is scheduled to arrive before I need it for this job, therefore it appears to be working properly. Other times the red dot does not appear but from looking at job manager, I can see the jobs that require the part and based upon future receipts, I will not have enough to complete this job therefore it should have a red dot
Any suggestions on what else we need to do (e.g., settings). We are still unclear on the scheduling so I don't know if that is the problem.
Thanks
Barbara Kite
Controller
Cableform, Inc.
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]