The scheduler is a mess until you hit 405. I've been testing 405 for a couple of days now and this little trick worked. (It doesn't on our live 404 system.)
Of course, now I will have to retest everything as 405A is out and (apparently) fixes some things 405 blew up. :(
Rob
Of course, now I will have to retest everything as 405A is out and (apparently) fixes some things 405 blew up. :(
Rob
--- On Fri, 8/8/08, jplehr <jlehr@...> wrote:
From: jplehr <jlehr@...>
Subject: [Vantage] Re: Resource Group Queue Time
To: vantage@yahoogroups.com
Date: Friday, August 8, 2008, 9:58 AM
Thanks Rob.
First, have you tested this process? I just ran the process by
posting zero activity against the operation(s) and ran a infinite
forward schedule, from Job Entry. The new dates are still taking
into consideration the queue time.
Second, I am well aware that there are many issues with the
scheduling engine in .305 because I have posted many of them. As
with everything, they are apparently fixed in 400 and above. If you
have ran this process successfully, what release are you on? If it
works in the release you are running I won't spend any more time on
it here and waite until I can upgrade...September .
Thanks for the other insight. I am aware of the impact this can have
in Global Rescheduling. I do not allow rescheduling of started
operations.
I am also with you on the queues but for now it is what the COO wants
to see. Yes, it is over inflating and we are working through that
now.
Jeff
--- In vantage@yahoogroups .com, Robert Brown <robertb_versa@ ...>
wrote:
>
> In general - no way to do it via editing job details.
>
> In practice, do a zero activity labor report (or a 1% set up
complete) and then do an infinite (forward) job entry schedule to get
the no queue OP start date you want. Once any activity occurs against
an OP, the Queue should go away.
>
> The negative is that this op will not rescheduled (via global)
unless you have enabled 'allow reschedule of in process OPs' in
company set up.
>
> That, as a company default option is not a great 'normal' option to
use as it can create more practical schedule chaos (as perceived by
dispatch users - since it can 'break set ups') than it is worth.
>
> Why are you using Queues anyway? (Not a good practice unless you
have a SMALL handful of resources that are common constraints that
you ALWAYS want available work piling up in front of them - so they
ALWAYS are in use.)
>
> Queues set up for all resources just tend to inflate your schedule
lead times.
>
> Rob Brown
>
>
>
> --- On Thu, 8/7/08, jplehr <jlehr@...> wrote:
> From: jplehr <jlehr@...>
> Subject: [Vantage] Resource Group Queue Time
> To: vantage@yahoogroups .com
> Date: Thursday, August 7, 2008, 4:13 PM
>
>
>
>
>
>
>
>
>
>
>
> Vantage 8.03.305L
>
>
>
> We have queue time tied to all of our Resource Groups. Does anyone
>
> know of a way to remove queue time on a specific Job. We want to
>
> shrink the schedule of a Job and we know, if we remove the queue
time,
>
> we can reflect a better more accurate schedule.
>