|
You didn't say exactly where the gaps are, but here is some information that might help. The BPCS FOD (Shop Order Operation) file stores a number of pieces of information for each shop order operation. The following pieces of information are available: - Scheduled start date - Scheduled completion date - Original Run hours (scheduled hours) - Original Setup hours (scheduled hours) - Original Machine hours (scheduled hours) - Scheduled/Expected quantity - Actual run hours reported - Actual machine hrs reported - Actual setup hours reported - Actual Quantity reported - Move Time - Queue Time The FOD file also stores the total actual hours per operation. FOD file does not store the actual operation completion date, but you can get that from your labor reporting in the BPCS FLT (Labor Ticket) file. One note: the FLT files also stores a field called "quantity at standard". The field is supposed to store the total hours, based on the routing file standard, that should have been used to complete the quantity reported on the labor ticket. I know that there are situations in v6.04 when this field is not calculated correctly. There are at least two BMRs related to this problem for SFC650 and JIT600 labor posting programs. The BPCS shop order files will help you track performance by shop order and/or item. If you are looking at a broader picture, you may want to try another approach. For example, I worked with a process industry client who wanted to track schedule performance on a weekly basis. At the beginning of the period, we took a "snapshot" of the schedule, and stored that as the "planned" schedule. During the period, actual performance is accumulated via the standard Shop Order posting process. At the end of the period, we can compare the actual against the "planned". Using this method allows us to compare actual performance against the plan for the period vs against the myriad of schedule changes that happen during the week. Please call if I can be of further assistance. Peggy Heritz Senior BPCS Specialist Crowe, Chizek & Company, LLP http://www.crowechizek.com/scg/ phone: 219.236.8698 fax: 219.236.7615 |--------+------------------------> | | "Coen,Gordon" | | | <gordon.coen@a| | | bbott.com> | | | | | | 03/08/00 06:10| | | AM | | | Please respond| | | to BPCS-L | | | | |--------+------------------------> >----------------------------------------------------------------------------| | | | To: BPCS-L@midrange.com | | cc: (bcc: Peggy A. Heritz/SB/CroweChizek/US) | | Subject: Manufacturing Cycle Times | >----------------------------------------------------------------------------| Hello all, BPCS MM 6004 /AS400. We are currently working on a project to improve the cycle time of our products. The main source of information will be the manufacturing system with the aim of producing a report which could provide a comparison of actual times/dates versus scheduled times/dates. We will be able to get some information on actual times from labour hour reporting but it won't quite meet all our needs. Has anyone else out there tried anything similar ? Is there some base BPCS functionality that I have overlooked which would help ? If not what did you do to retrieve this information. Thanks, Gordon. +--- | 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.