I lean towards Rob's assessment as well. I've never used 6.1 (so have no idea what it is capable of) - but finite scheduling (as a concept) is pretty much in fundamental conflict with the whole Lean load leveling paradigm - although both are simply at-odds paradigms intended to deal with the same issue.
I guess you could characterize the major differences as:
Finite - Computer intensive model (of your detailed resources/workcenters & much more complex & detailed routings) that tries to optimize throughout my maximing utilization (which drives up WIP as OP cycle times are rarely balanced) and achieve the 'least worst' resulting compliance with your req'd by dates.
Level loading: The entire line process takt time is the driver & the production sup-ops are proactively designed/tooled tooled to make set up a minimal obstacle and to also allow increased throughput simply by adding more human resources to parallel flow process the discrete sub-ops capabilities built into the physical design of the line process (which is design to process similar enough products in 'mixed mode'). Production planning/scheduling emphasis is on managing the WIP queue in front of each line (and is much less computer intensive.. Often able to be done with visual non-computer scheduling techniques self managed by the line). Self management also extends to authorizing the line leaders to adjust the sequence of jobs in order to minimize (already minimized by proactively thought out low set up tooling/fixturing) non-value added set up. (It works just fine in an infinite environment... In fact, in my experience, applying a finite model over it
makes it much less efficient and flexible.)
As to you 6.1 issue & question - Why not just make a copy of your db and try it (on your copied over test system)?
You'll get you're answer pretty quickly.
Rob Brown
________________________________
From: Rob Bucek <rbucek@...>
To: vantage@yahoogroups.com
Sent: Tuesday, September 1, 2009 6:09:00 PM
Subject: RE: [Vantage] Finite Scheduling-version 6.10
We don't run v6, nor have I ever seen it, but I would be very surprised
if Vantage 'remembered' that you level loaded a work center when you ran
Finite scheduling again. Is there any processes that refer to
calculate global scheduling order or adjust global scheduling order?
I'm not sure how mature the scheduling system was in v6 but if it had
some way of establishing job priority in any fashion, I believe the
scheduling function would look to that for its information in how to
schedule.
What you're really expecting from the way you described it, is that all
those work centers that were level loaded would have their operations
'locked'. My hunch is that in the finite world if you subsequently
tried to reschedule everything in a finite mode around some work centers
with locked operations (not possible even in v8, the whole job is locked
or not at all), you would not get a feasible schedule (i.e. too much too
late, or too early).
My guess is that you would in reality have to level load again. But I'd
listen to the other v6 experts out there before me.
Rob Bucek
Manufacturing Engineer
PH: (715) 284-5376 ext 3111
FAX: (715)284-4084
<http://www.dsmfg com/>
(Click the logo to view our site) <http://www.dsmfg com/>
From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf
Of Bill Jackson
Sent: Tuesday, September 01, 2009 2:11 PM
To: vantage@yahoogroups .com
Subject: [Vantage] Finite Scheduling-version 6.10
A question for any who use or have used, Finite Scheduling in Vantage
ver 6.10.
WE have 'load-leveled' certain Work Centers.
After scheduling more jobs, and then running 'Finite Scheduling' again,
will the Work Centers need to be 'load-leveled' again?
We are thinking that Vantage runs 'Finite Scheduling' with the knowledge
that certain Work Centers are load-leveled.
Thanks,
Bill J
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
I guess you could characterize the major differences as:
Finite - Computer intensive model (of your detailed resources/workcenters & much more complex & detailed routings) that tries to optimize throughout my maximing utilization (which drives up WIP as OP cycle times are rarely balanced) and achieve the 'least worst' resulting compliance with your req'd by dates.
Level loading: The entire line process takt time is the driver & the production sup-ops are proactively designed/tooled tooled to make set up a minimal obstacle and to also allow increased throughput simply by adding more human resources to parallel flow process the discrete sub-ops capabilities built into the physical design of the line process (which is design to process similar enough products in 'mixed mode'). Production planning/scheduling emphasis is on managing the WIP queue in front of each line (and is much less computer intensive.. Often able to be done with visual non-computer scheduling techniques self managed by the line). Self management also extends to authorizing the line leaders to adjust the sequence of jobs in order to minimize (already minimized by proactively thought out low set up tooling/fixturing) non-value added set up. (It works just fine in an infinite environment... In fact, in my experience, applying a finite model over it
makes it much less efficient and flexible.)
As to you 6.1 issue & question - Why not just make a copy of your db and try it (on your copied over test system)?
You'll get you're answer pretty quickly.
Rob Brown
________________________________
From: Rob Bucek <rbucek@...>
To: vantage@yahoogroups.com
Sent: Tuesday, September 1, 2009 6:09:00 PM
Subject: RE: [Vantage] Finite Scheduling-version 6.10
We don't run v6, nor have I ever seen it, but I would be very surprised
if Vantage 'remembered' that you level loaded a work center when you ran
Finite scheduling again. Is there any processes that refer to
calculate global scheduling order or adjust global scheduling order?
I'm not sure how mature the scheduling system was in v6 but if it had
some way of establishing job priority in any fashion, I believe the
scheduling function would look to that for its information in how to
schedule.
What you're really expecting from the way you described it, is that all
those work centers that were level loaded would have their operations
'locked'. My hunch is that in the finite world if you subsequently
tried to reschedule everything in a finite mode around some work centers
with locked operations (not possible even in v8, the whole job is locked
or not at all), you would not get a feasible schedule (i.e. too much too
late, or too early).
My guess is that you would in reality have to level load again. But I'd
listen to the other v6 experts out there before me.
Rob Bucek
Manufacturing Engineer
PH: (715) 284-5376 ext 3111
FAX: (715)284-4084
<http://www.dsmfg com/>
(Click the logo to view our site) <http://www.dsmfg com/>
From: vantage@yahoogroups .com [mailto:vantage@yahoogroups .com] On Behalf
Of Bill Jackson
Sent: Tuesday, September 01, 2009 2:11 PM
To: vantage@yahoogroups .com
Subject: [Vantage] Finite Scheduling-version 6.10
A question for any who use or have used, Finite Scheduling in Vantage
ver 6.10.
WE have 'load-leveled' certain Work Centers.
After scheduling more jobs, and then running 'Finite Scheduling' again,
will the Work Centers need to be 'load-leveled' again?
We are thinking that Vantage runs 'Finite Scheduling' with the knowledge
that certain Work Centers are load-leveled.
Thanks,
Bill J
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]