|
Good Answer! That talks about the greatness of the people. Frederick, you have always been helping me out. Thanks a lot! Best Regards, Prashanth On Sat, 17 Sep 2005 Frederick C Davy wrote : >pd, > >Unless you are using BPCS Finite Forward Scheduling (MRP640), none of the >planning or shop order releasing will take capacity constraints into >consideration when assigning start/completion dates. Finite Forward >Scheduling requires you to assign all the work centers associated to a >routing to a Production Line in the Work Center Master (CAP100), and does >not work well unless the most critical work center is the first operation >on the routing (there is too much to Finite Forward Scheduling to write it >up here, you just need to know that the program will "level load" a >Production Line to maximize capacity, but may cause some orders to finish >late). > >The best thing for you to do is to use Capacity Planning by running CAP600 >directly after MRP600 and reviewing each of your work centers in CAP300 >(check the profile view first, the work center calculated capacity is on >the "X" axis, and the planned/scheduled load is on the "Y" axis and if the >graft has no red flashing columns, you aren't overloaded). If you see a >period that is flashing red, "click" on the column and press F4 to see the >orders that are causing the problem. Then you can either adjust the >capacity by scheduling overtime, or off load some of the work to other >work centers, or reschedule noncritical orders. > >The tool to use if you are only working on an individual shop order would >be to use program SFC350, enter action code "13" to check Capacity >Availability for the item you will be making. When you get to screen >SFC350D3-1, tab to the quantity field and enter the quantity you will be >making and press "Enter". The bottom part of the screen will display how >much setup and run time will be required to make the order. Now, key "5" >into the "Act" field next to one of the operations on the displayed >routing. This will take you to CAP300. Type "11" in the "Act" field next >to the work center for your operation, and press enter. You will now see >the capacity profile for that work center and you can make an intelligent >decision about where your new order will fit (based on the number of hours >calculated by SFC350). Neat, but it requires you to do some work. Good >luck. > > > > >"p d" <prd2005@xxxxxxxxxxxxxx> >Sent by: bpcs-l-bounces+amkavoulakis=sealinfo.com@xxxxxxxxxxxx >09/16/2005 12:38 AM >Please respond to >"SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx> > > >To >"SSA's BPCS ERP System" <bpcs-l@xxxxxxxxxxxx> >cc >misterbpcs@xxxxxxx >Subject >Re: [BPCS-L] Re: BPCS-L Digest, Vol 3, Issue 199 > > > > > > > >Hi, > >The question was related to execution phase in manufacturing, when planned >orders are converted to shop orders. > >My question was, in planning phase, the release date is worked out from >due date based on lead time maintained in item master for an item. >However, how is it (Release date) worked out in execution phase, specially >where routing is taken into consideration to check for capacity >constraints & actual lead time ? How system works it out ? Whether it is >LCR record that plays a role (input) in working out Release date based on >given due date (in case of Backward scheduling) or whether FRT & LWK >records play the role or is there any other mechanism/ Input which plays >role in working out Release Date ? > >Basically, whether the release date at planning phase & that at execution >date can be different (based on actual lead time maintained through >routing) ? if so, how is it worked out ? > >regards, >Prashanth > > >On Thu, 15 Sep 2005 misterbpcs@xxxxxxx wrote : > >This question and it's answer is so garbled and disjointed, that it is >very difficult to determine what is the subject. Please restate. > > > >Ric Weide > >R C Weide Consulting > >Tel: (678) 575-2620 > >Email: MisterBPCS@xxxxxxx > > > > > >-----Original Message----- > > From: bpcs-l-request@xxxxxxxxxxxx > >To: bpcs-l@xxxxxxxxxxxx > >Sent: Wed, 14 Sep 2005 12:00:33 -0500 > >Subject: BPCS-L Digest, Vol 3, Issue 199 > > > > > >Send BPCS-L mailing list submissions to > > bpcs-l@xxxxxxxxxxxx > > > >To subscribe or unsubscribe via the World Wide Web, visit > > http://lists.midrange.com/mailman/listinfo/bpcs-l > >or, via email, send a message with subject or body 'help' to > > bpcs-l-request@xxxxxxxxxxxx > > > >You can reach the person managing the list at > > bpcs-l-owner@xxxxxxxxxxxx > > > >When replying, please edit your Subject line so it is more specific > >than "Re: Contents of BPCS-L digest..." > > > > > >Today's Topics: > > > > 1. manufacturing execution (p d) > > 2. Re: manufacturing execution (joe.walsh@xxxxxxxxx) > > > > > >---------------------------------------------------------------------- > > > >message: 1 > >date: 14 Sep 2005 05:34:50 -0000 > > from: "p d" <prd2005@xxxxxxxxxxxxxx> > >subject: [BPCS-L] manufacturing execution > > > > > >Hi, > > > >If a planned order for a manufactured item in BOM is due on a particular >date (1 > >day) say for qty. of 100, whereas considering the capacity constraint, if >LCR > >record suggest that order be split in 10 days, each day with qty.10. > > > >In such case, whether the release date (for shop order) would be 10 days >before > >the due date when planned order is converted to shop order during >execution ? > > > >whether LCR plays any role in calculating release date of a shop order at >this > >execution phase or FRT & LWK together will be the input in calculating >the > >release date of a shop order (converted planned order) ? > > > >regards, > >Prashanth > > > >------------------------------ > > > >message: 2 > >date: Wed, 14 Sep 2005 04:40:17 -0700 > > from: joe.walsh@xxxxxxxxx > >subject: Re: [BPCS-L] manufacturing execution > > > > Prasanth > > > > You are asking many relativel operations, perhaps a few days of one >on o > >greatly increase the level of your knowledge of BP that progress. > > > > regards > > Joseph Walsh, CPIM, CIRM > > Sr. Business Consultant > > IBS US - 201 W. Passaic St > > Rochelle Park, NJ 0766 > > cell: 845-380-4257 > > joe.walsh@xxxxxxxxx > > > > > >------------------------------ > > > >-- > >This is the SSA's BPCS ERP System (BPCS-L) digest list > >To post a message email: BPCS-L@xxxxxxxxxxxx > >To subscribe, unsubscribe, or change list options, > >visit: http://lists.midrange.com/mailman/listinfo/bpcs-l > >or email: BPCS-L-request@xxxxxxxxxxxx > >Before posting, please take a moment to review the archives > >at http://archive.midrange.com/bpcs-l. > > > > > > > >End of BPCS-L Digest, Vol 3, Issue 199 > >************************************** > >-- > >This is the SSA's BPCS ERP System (BPCS-L) mailing list > >To post a message email: BPCS-L@xxxxxxxxxxxx > >To subscribe, unsubscribe, or change list options, > >visit: http://lists.midrange.com/mailman/listinfo/bpcs-l > >or email: BPCS-L-request@xxxxxxxxxxxx > >Before posting, please take a moment to review the archives > >at http://archive.midrange.com/bpcs-l. > > > >Delivered-To: prd2005@xxxxxxxxxxxxxx > >-- >This is the SSA's BPCS ERP System (BPCS-L) mailing list >To post a message email: BPCS-L@xxxxxxxxxxxx >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/mailman/listinfo/bpcs-l >or email: BPCS-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/bpcs-l. > >Delivered-To: amkavoulakis@xxxxxxxxxxxx > >-- >This is the SSA's BPCS ERP System (BPCS-L) mailing list >To post a message email: BPCS-L@xxxxxxxxxxxx >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/mailman/listinfo/bpcs-l >or email: BPCS-L-request@xxxxxxxxxxxx >Before posting, please take a moment to review the archives >at http://archive.midrange.com/bpcs-l. > >Delivered-To: prd2005@xxxxxxxxxxxxxx
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.