This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Hello ,

I have one problem in Capacity Planning and need your support.

I have three steps routing.  All of them has basis codes 'H', (Standard Batch 
Size).  In practicle, Operation 10 and Operation 20 run concurrently while 
operation 30 runs after one day of the completion of Operation 10 and 20.

Op:10    Move Day -1    Work Centre: 10
Op:20    Move Day +1   Work Centre: 20
Op:30    No Move Days Work Centre: 30

My Forecaset is on 15th September, of 15,000 quantity


I run directly Detail capacity planning because all of my work centre are 
critical.  System plans backward.  Say depending upon my routing,  system 
finishes operation 30 on 13th Septembre.  Operation 30 on 13th September takes 
3 hours out of 8 hours of capacity.  According to my routing at operation 20,  
it starts on one day before operation 30.  So it starts correctly on 12th 
September.

Problem is that,  this operation 20 takes only 5 hours out of 8 hours of the 
capacity on 12th September.  It means it takes hours in proportion of the next 
operation completion.   Which is not practicle in our case.

In nutshell,  we neeed full 8 hours for operation 20 on 12th September.

Second problem is that, if the forecast quanitity is more than batch size,  
then setup hours are considered only once which is not practicle either.  We 
need full setup hours for each batch.

For your reference,  we are on BPCS Full Client Server, Ver. 6.1.  On drawback 
in Full Client Server is that it does not offer Finite Forward Scheduling.

See if you could advice at your earliest.


Imran Naseem

--




This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].