Or, if that behavior (and perhaps others) in 406a outweigh problematic behaviors (or outright bugs), just stay on 406a until there is REALLY a compelling reason to upgrade.
That's why we're still on 405a... Not worth the testing time & customization verification (or the discovery of undesired changed behavior) until at least 408 (when a global scheduling bug SCR we initiated - causing significant pain for us for the last year - while "Warren" screwed around for 4 months attempting every which way to deny it was a bug) is slated for release.
Even then... I'd prefer to wait until a 408b so as not to be the lab rat to deal with issues in the 1st 408 release.
Stability (even with known problems) is more important than latest greatest (that may not be so great for our business needs).
Rob
That's why we're still on 405a... Not worth the testing time & customization verification (or the discovery of undesired changed behavior) until at least 408 (when a global scheduling bug SCR we initiated - causing significant pain for us for the last year - while "Warren" screwed around for 4 months attempting every which way to deny it was a bug) is slated for release.
Even then... I'd prefer to wait until a 408b so as not to be the lab rat to deal with issues in the 1st 408 release.
Stability (even with known problems) is more important than latest greatest (that may not be so great for our business needs).
Rob
--- On Fri, 3/6/09, Ari Footlik <ari@...> wrote:
From: Ari Footlik <ari@...>
Subject: RE: [Vantage] Re: v8.03 (vs v6) Backward Scheduling Issue
To: vantage@yahoogroups.com
Date: Friday, March 6, 2009, 2:43 PM
We're running 8.03.406A and we definitely have the ability to choose
resources. We also definitely didn't do any customization of the MES
screen, so I don't know why it's working like it is. And now that I
hear from everyone that it's *not* supposed to work this way, it makes
me very nervous that one day it'll just plain STOP working this way...
--A
____________ _________ _________ __
From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf
Of Robert Brown
Sent: Friday, March 06, 2009 1:20 PM
To: vantage@yahoogroups .com
Subject: RE: [Vantage] Re: v8.03 (vs v6) Backward Scheduling Issue
I just checked and our MES (405a) does not allow floor people to change
the resource. (What version ar you running?)
The control appears natively disabled - although I suppose it could be a
case of the security role assigned to these users blocking the BO method
associated with the control.
Appeciate the feedback as I'd LIKE to allow floor people to do their own
on the fly workload balancing (and not have to run back to production
control).
I'll have to investigate further to see if we can give them that
capabiliity (either by tweaking user role security or w/ explicit VB
customization to re-enable control).
Thx Ari.
Rob
--- On Fri, 3/6/09, Ari Footlik <ari@zweig-cnc. com
<mailto:ari% 40zweig-cnc. com> > wrote:
From: Ari Footlik <ari@zweig-cnc. com <mailto:ari% 40zweig-cnc. com> >
Subject: RE: [Vantage] Re: v8.03 (vs v6) Backward Scheduling Issue
To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
Date: Friday, March 6, 2009, 9:31 AM
Well, I'm sure Warren appreciates you backing him up, but what he (and
you, and the other Rob) said would happen doesn't actually appear to be
the case.
I have a resource-group assigned to an operation. When I go out to the
floor and clock into the job, the "scheduled" resource is listed. But,
I can click on the "Resource ID" button and select a new resource in the
group. Furthermore, once I have the "Resource Search" box open, if I
clear the "Resource Group" field I get a list of *every* resource, and
can freely choose from that list.
I understand why for some companies this would not be the desired
behavior, but in our case, it is absolutely the desired behavior. I
hope someone could explain to me, though, why this works for us and how
to change this behavior, so that should something one day all of a
sudden stop working this way, I'll have some idea as to how to put it
back...
Thanks.
--Ari
____________ _________ _________ __
From: vantage@yahoogroups .com [mailto:vantage@ yahoogroups .com] On
Behalf
Of Robert Brown
Sent: Thursday, March 05, 2009 8:55 PM
To: vantage@yahoogroups .com
Subject: RE: [Vantage] Re: v8.03 (vs v6) Backward Scheduling Issue
Warren is right Ari (and that in ITSELF is a miracle as I've dealt with
him many times & it's like talking to a brick wall at times).
Once a specific resource is schedule assigned an operator can't clock in
to another (presumably same capability) resource on the fly as most
systems allow.
You have to edit the job details and reschedule.
Pain in the rear end (forever).
Rob
--- On Thu, 3/5/09, Ari Footlik <ari@zweig-cnc. com
<mailto:ari% 40zweig-cnc. com> > wrote:
From: Ari Footlik <ari@zweig-cnc. com <mailto:ari% 40zweig-cnc. com> >
Subject: RE: [Vantage] Re: v8.03 (vs v6) Backward Scheduling Issue
To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
Date: Thursday, March 5, 2009, 5:52 PM
Rob -
Thanks for the information. I'm not very familiar with scheduling (I'm
the IT Mgr, not one of the schedulers/engineer s) but I thought I had a
good basic understanding of what *should* happen. Turns out I was right
- the problem ended up being something completly different: We had a PO
already generated against the job, and the PO had a "due date" set.
Scheduling adjusted for the due-date. When I removed the due-dates from
the PO, un- and re-scheduled the job, the schedule came up as I thought
it should.
On the plus-side, I did manage to fix up our resource-groups :)
Unfortunately, in my discussions with Warren at Epicor, I discovered
we're in for a world of pain come these next few days... Warren said
that once the resurce is "assigned" by the schedule, our operators won't
be able to clock-in to a job using another member of the resource-group
unless/until somone moves the job. Any thoughts on this?
--Ari
____________ _________ _________ __
From: vantage@yahoogroups .com [mailto:vantage@ yahoogroups .com] On
Behalf
Of rob.bucek
Sent: Thursday, March 05, 2009 3:35 PM
To: vantage@yahoogroups .com
Subject: [Vantage] Re: v8.03 (vs v6) Backward Scheduling Issue
We battled with Epicor over scheduling for months and months and in the
end found out that there are no true scheduling experts left there. In
all our research and developement in this area towards the goal of
finite scheduling (which we are scheduled to go live with in the next
week or two) has taught us many things. You absolutely do not need a
calendar per resource group. Each resource group needs to be tied to A
calendar, but not necessarily a unique one per group. The combination of
calendars and number of resources per group should ultimately reflect
the capacity of your plant. We have calendars set up reflecting the
various 'shifts' working throughout the plant. This may vary by
department or resource group. Do what makes sense to you. Assigning a
resource group to an operation is just fine. At that point the system
will decide on its own during schedling which specific resource in that
group that it will assign to it. If there is only one resource in that
group it will of course pick that one. The other variable to consider of
course is capabilities if you are using those as well. The biggest thing
is to be consistent. If you assign a specific resource to an operation
and that resource exists in a group with other resources and you assign
that group to a different operation be aware that there will be
contention for that resource that was specifically assigned to an
operation. This could cause some unique scheduling constraints for you.
Any questions dont hesitate to ask as Ive lived and breathed vantage
scheduling enough to aspirate on it...
--- In vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com> ,
"Ari
Footlik" <ari@...> wrote:
>
> Thanks for the input.
>
> Epicor support is now saying there are multiple contributing factors:
> * We don't have a calendar specified on our resource groups
> * When we converted we didn't update the "Operations" to show the
> resources, so they all show "Converted Rates00001" on the "Resources"
> tab.
>
> They're suggesting we add a calendar to each resource-group (I have no
> problem with that suggestion), but that we need to add a "Resource" to
> each Operation. I'd rather add a "Resource Group" to each operation -
> that makes more sense to me for our environment. Is there any reason I
> couldn't do that?
>
> And, for that matter, does Epicor's thinking hold water?
>
> Thanks again.
> --Ari
>
> ____________ _________ _________ __
>
> From: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
[mailto:vantage@ yahoogroups .com <mailto:vantage% 40yahoogroups. com> ]
On
Behalf
> Of jpfinch1
> Sent: Wednesday, March 04, 2009 4:00 PM
> To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
> Subject: [Vantage] Re: v8.03 (vs v6) Backward Scheduling Issue
>
>
>
> I have seen this as well. We are able to correct it by scheuling the
job
> with the "ignore material contrainsts" after the "Allow Scheuling
Before
> Today" check box was checked. It seems to be a combination of both
that
> cause the problem.
>
> What is really strange is that if you do not own the Advanced
Materials
> Management Module, the Constrained material option is blanked in the
> part master and is not supposed to affect jobs.
>
> --- In vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
<mailto:vantage% 40yahoogroups. com> , "Ari
> Footlik" <ari@> wrote:
> >
> > Mark -
> >
> > Thanks a lot! That definitely helped. The start-date changed, but
> > somehow the system is still coming up with a due-date *after* the
> req-by
> > date. Turning on the "Override Material Constraints" option doesn't
> > have an effect.
> >
> > When I attempt to schedule the job, I get a warning that says, "The
> job
> > is currently scheduled to finish 6/5/2009. It will not meet its
> > required date of 5/15/2009" Perhaps the system is still seeing the
old
> > schedule for this?
> >
> > --Ari
> >
> > ____________ _________ _________ __
> >
> > From: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
<mailto:vantage% 40yahoogroups. com>
> [mailto:vantage@ yahoogroups .com <mailto:vantage% 40yahoogroups. com>
<mailto:vantage% 40yahoogroups. com> ] On
> Behalf
> > Of Mark Wonsil
> > Sent: Wednesday, March 04, :40 PM
> > To: vantage@yahoogroups .com <mailto:vantage% 40yahoogroups. com>
<mailto:vantage% 40yahoogroups. com>
> > Subject: RE: [Vantage] v8.03 (vs v6) Backward Scheduling Issue
> >
> >
> >
> > > Have you tried?
> > >
> > > System Mangement | Company Maintenance | Company
> > > Tabs: Modules | Production | Job
> > > Scheduling Panel: Allow Scheduling Before Today
> >
> > Forgot the Jobs Tab...
> >
> > Mark W.
> >
> >
> >
> >
> >
> >
> > [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]
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]