We have a product called "Peas in a Pod" (R) that was designed to
recognize lot attributes in BPCS' MPS/MRP processing. It was
invented for a carpet manufacturer.
As you tuft a 12' wide carpet, the ~1480 spools of yarn back
in the creel all have to come from precisely the same dye lot.
Just one spool from a different lot will cause a streak to
appear in the finished carpet. Peas in a Pod can be configured
so that even if you have 1400 yarn spools in lot #x1 and 1400
yarn spools in lot #x2, BPCS MPS won't "see" enough
on-hand yarn inventory to plan a carpet tufting shop order
until MRP can plan for the receipt of a new yarn lot with at least
1480 spools in that new lot.
The same Peas in a Pod logic recognizes the expiration date
attribute. Vanilla BPCS is perfectly happy to "use" on-hand
carrots for a planned soup blending order even when the
blending is scheduled after the expiration date of the carrot lot.
For more insight --> select green diamond on right side here:
Unbeaten Path International
North America: (888) 874-8008
International: +(262) 681-3151
From: Ruben Mirensky
Sent: Saturday, September 20, 2008 3:15 PM
Subject: [BPCS-L] Expiration dates
Has anybody developed a solution to deal with the expiration date
of lot controlled items in the MRP logic?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2022 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.