In v6, there is a field in the Job Operation screen called Machines.
Set that to 2 if you always want to schedule it on 2 machines.
HTH,
Brian Stenglein
--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...>
wrote:
set up under it.
multiple 'drill-#'s, set the operation scheduling blocks to indicate
how many (max) 'drill-#'s you want this OP parallel (start to start)
split scheduled across.
other job OPs from having capacity to run in parallel to the current
job) - set scheduling blocks to 2.
blocks field being disabled (read only if the job details were
generated from a method) - or perhaps even hidden - in job entry.
(Nothing that couldn't be cured with some .NET customization.)
capacity & resulting cost. Those problems observed could have been
bugs since fixed.
an OP in a method (or in a job's details) to either
process "S"erially or in "P"arallel if multiple qualified resources
are available.
systems simply allowed you to create a workcenter (resource) &
indicate how many machines or people it had available to schedule
into their capacity.
machine.
job would actually finish sooner?
Set that to 2 if you always want to schedule it on 2 machines.
HTH,
Brian Stenglein
--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...>
wrote:
>capable & defined 'drill-1, drill-2, drill-3,... drill-20' resources
>
> If you're on v6 - no idea.
>
> If you're on v8 here is an example:
>
> You have a resource group called 'drill press' with 20 identically
set up under it.
>you want the load of that OP scheduled to be split across
> Your method OP simply call to use resource GROUP 'drill press'. If
multiple 'drill-#'s, set the operation scheduling blocks to indicate
how many (max) 'drill-#'s you want this OP parallel (start to start)
split scheduled across.
>practical to do 20 simultaneous drill setups or effectively block any
> If you never want to consume more than 2 (perhaps because it isn't
other job OPs from having capacity to run in parallel to the current
job) - set scheduling blocks to 2.
>detail level as well. I seem to recall som issue with the scheduling
> Theoretically I think you can do this at the individual job op
blocks field being disabled (read only if the job details were
generated from a method) - or perhaps even hidden - in job entry.
(Nothing that couldn't be cured with some .NET customization.)
>piloting and it produced some odd results in regard to perceived
> We don't do this - but I recall testing it on one of the 305's when
capacity & resulting cost. Those problems observed could have been
bugs since fixed.
>term method maintenance and job management)... You could simply set
> I suggest you model it in your train db and test it thoroughly 1st.
>
> Other systems I've used handle this much more efficiently (re long
an OP in a method (or in a job's details) to either
process "S"erially or in "P"arallel if multiple qualified resources
are available.
>programmer would love it) resource group/resource paradigm. Older
> That simplification also applies to the whole nutty (only an OOP
systems simply allowed you to create a workcenter (resource) &
indicate how many machines or people it had available to schedule
into their capacity.
><vantage@yahoogroups.com>
> Good luck!
>
> Rob
>
> --- On Fri, 2/13/09, Jasper Recto <jrecto@...> wrote:
>
> From: Jasper Recto <jrecto@...>
> Subject: [Vantage] Work center scheduling and shop load
> To: "Vantage Groups (vantage@yahoogroups.com)"
> Date: Friday, February 13, 2009, 11:50 AMin it. When you schedule that operation, it puts the load all on one
>
>
>
>
>
>
> We have an operation that goes to a work center that has 4 machines
machine.
>up the job so that the load is on the work center is doubled and the
> If we decide to run 2 machines for that operation, how do you set
job would actually finish sooner?
>machines, how do we setup our master files to reflect this?
> How can you do this on the job AND if we want to permanently use 2
>
> Thanks,
>
> Jasper
>
> [Non-text portions of this message have been removed]
>