|
Thanks Nancy. Although you have an interesting method there it is not one I think we can use. Some of our facilities produce over 1,000 SKUs with any 200 being scheduled at a time, thus it is almost impossible to know which items can be grouped together on a work center until after finite forward scheduling is run. Any other ideas? Mitch Damon, CPIM Planning Systems Manager Agrilink Foods, Rochester NY (716) 383-1070 -----Original Message----- From: NAdamson@mother-parkers.com [SMTP:NAdamson@mother-parkers.com] Sent: Wednesday, May 02, 2001 5:22 PM To: BPCS-L@midrange.com Subject: Re: duplicate work centers and finite forward scheduling Mitch, We also ran into this problem (version 6.0.02) and aside from using alternate routing methods (which we didn't want to do because we have trouble enough keeping track of one routing per item, but you may want to explore this) our work around is to change the original routing operation to the alternate work center before we pull the planned orders into Finite Forward Scheduling. This sounds painful but we find it easier than changing the shop order after it has been created, and also allows us to capacity load each work center correctly using FFS. In our organization our routings are single level (products don't flow from work center to work center) so they only have one active operation in each routing. For products that can run in multiple work centers we create additional operations (pointing to the other work center, and with different run times if needed) and then leave them inactive until we decide to run the product in the alternate work center. To move a product to a different work center we just inactivate one operation and active the other. The product is moved to the alternate work center the next time we pull planned orders into FFS. Hope this helps - if you need a better explanation give me a call Nancy Adamson System Analyst - Supply Chain Mother Parker's Tea & Coffee Mississauga, Ontario (905) 683-5081 ext 214 "Damon, Mitch" <MDamon@agrilinkfoods.com>@midrange.com on 05/02/2001 04:20:16 PM Please respond to BPCS-L@midrange.com Sent by: owner-bpcs-l@midrange.com To: AAA-BPCS users listserve <BPCS-L@midrange.com> cc: Fax to: Subject: duplicate work centers and finite forward scheduling On ver 6.0.04 Does anyone have experience using finite forward scheduling in a situation where there are multiple work centers in the same warehouse that can produce the same item. The problem is that the routes assign each item to a particular work center which may or may not be the one we will run the item on. But in finite forward scheduling the item will only show up and can only be scheduled on the line the routing indicates, unless each shop order is edited. Any ideas would be greatly appreciated. Mitch Damon, CPIM Planning Systems Manager Agrilink Foods, Rochester NY (716) 383-1070 +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.