Robert,
Thanks for uploading the BAQ!
Steve
-----Original Message-----
From: Robert Brown [mailto:robertb_versa@...]
Sent: July 14, 2008 1:10 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] 8.03.403C - Visual Scheduling Boards seriously SLOW
I just uploaded the DBD & BAQ xml as well as a explanatory readme to the
files section under folder "ResSchedBrdDashboard".
I suggest you look at the readme as much of the design is likely specific to
things in our processes that may not be important to yours.
Modify away...
(Programming 101: Never write what you can 'borrow'.)
Rob Brown
--- On Mon, 7/14/08, melissa hietala <kevmel822@yahoo.
<mailto:kevmel822%40yahoo.com> com> wrote:
From: melissa hietala <kevmel822@yahoo. <mailto:kevmel822%40yahoo.com> com>
Subject: Re: [Vantage] 8.03.403C - Visual Scheduling Boards seriously SLOW
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Date: Monday, July 14, 2008, 12:47 PM
I would also be interested in this. Thank you.
Melissa Hietala
UMC, Inc.
melissah@ultramc. com
----- Original Message ----
From: Robert Brown <robertb_versa@ yahoo.com>
To: vantage@yahoogroups .com
Sent: Sunday, July 13, 2008 11:30:19 AM
Subject: Re: [Vantage] 8.03.403C - Visual Scheduling Boards seriously SLOW
Sure. There is nothing proprietary about it. I'll send you the BAQ when I'm
in the office tomorrow.
I never used Preactor but always heard VERY good things about it. Are they
still in business selling it as a stand alone product or has someone gobbled
them up via M&A and integrated it into an ERP suite?
Rob Brown
Thanks for uploading the BAQ!
Steve
-----Original Message-----
From: Robert Brown [mailto:robertb_versa@...]
Sent: July 14, 2008 1:10 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] 8.03.403C - Visual Scheduling Boards seriously SLOW
I just uploaded the DBD & BAQ xml as well as a explanatory readme to the
files section under folder "ResSchedBrdDashboard".
I suggest you look at the readme as much of the design is likely specific to
things in our processes that may not be important to yours.
Modify away...
(Programming 101: Never write what you can 'borrow'.)
Rob Brown
--- On Mon, 7/14/08, melissa hietala <kevmel822@yahoo.
<mailto:kevmel822%40yahoo.com> com> wrote:
From: melissa hietala <kevmel822@yahoo. <mailto:kevmel822%40yahoo.com> com>
Subject: Re: [Vantage] 8.03.403C - Visual Scheduling Boards seriously SLOW
To: vantage@yahoogroups <mailto:vantage%40yahoogroups.com> .com
Date: Monday, July 14, 2008, 12:47 PM
I would also be interested in this. Thank you.
Melissa Hietala
UMC, Inc.
melissah@ultramc. com
----- Original Message ----
From: Robert Brown <robertb_versa@ yahoo.com>
To: vantage@yahoogroups .com
Sent: Sunday, July 13, 2008 11:30:19 AM
Subject: Re: [Vantage] 8.03.403C - Visual Scheduling Boards seriously SLOW
Sure. There is nothing proprietary about it. I'll send you the BAQ when I'm
in the office tomorrow.
I never used Preactor but always heard VERY good things about it. Are they
still in business selling it as a stand alone product or has someone gobbled
them up via M&A and integrated it into an ERP suite?
Rob Brown
--- On Sun, 7/13/08, Lou Laird <loulrd@yahoo. com> wrote:
From: Lou Laird <loulrd@yahoo. com>
Subject: Re: [Vantage] 8.03.403C - Visual Scheduling Boards seriously SLOW
To: vantage@yahoogroups .com
Date: Sunday, July 13, 2008, 1:05 AM
Excellent comments about the scheduling board. Before our upgrade I looked
at it once and turned it off. I used Preactor scheduling in a past life,
excellent scheduling engine and graphical capabilities. Would you be open to
sharing your dashboard definitions?
----- Original Message ----
From: Robert Brown <robertb_versa@ yahoo.com>
To: vantage@yahoogroups .com
Sent: Thursday, July 10, 2008 1:03:04 PM
Subject: Re: [Vantage] 8.03.403C - Visual Scheduling Boards seriously SLOW
We are on 404 and Resource Scheduling Board has more bugs than it did on
403: Don't hold your breath awaiting Epicor's 405 promised fixes to be true.
Why are you even using this tool? What you are seeing is not the real time
actual schedules anyway - Just the mirror-like Load table data that is
static.
Are your Global scheduling results so poor you have to 'hand lay' in every
OP per resource to get a decent schedule? (If so, I assume you are then
locking your carefully laid out schedules so they don't get REscheduled. )
"Graphical" scheduling is a sales buzzword. I've never an product that has
anything close to being an efficient one except Lilly Software's product
(that also has probably the best overall scheduling engine I've ever seen).
We don't (and won't likely ever) use Resource Scheduling Board.
We have a simple Dashboard that displays the ACTUAL OP schedules. From that
it is a simple right click to Job Entry to fine tune schedules if you wish.
My suggestion to you would be to do the same.
Rob Brown
--- On Thu, 7/10/08, bpbuechler <pbuechler@uvcolor. com> wrote:
From: bpbuechler <pbuechler@uvcolor. com>
Subject: [Vantage] 8.03.403C - Visual Scheduling Boards seriously SLOW
To: vantage@yahoogroups .com
Date: Thursday, July 10, 2008, 10:03 AM
I am getting some serious heat from my Scheduling Department.
We use the Resource Scheduling Board and the Multi-Resource
Scheduling Board to move operations/assembli es/jobs all day long.
Just to move one operation can take up to 4 minutes for the boards to
refresh.
Epicor provided me the secret of establishing debug.txt; so each and
everytime the scheduler moves something, it writes out to the
\\server\mfgsysdata \Reports\ schedulername. But when I look at the
text file, the amount of time it logs to programtically process the
move is within a minute (for a large job) and seconds for a single
move.
For those that use the Visual Scheduling Boards, do you experience
serious slowness of the boards refreshing; even though the program
seams to quickly process through move?
We are on 8.03.403c and Epicor promises 8.03.404B and SP 405 resolves
the slowness. Can anyone testify to this promise?
Thanks
Patty Buechler
UV Color
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]