|
Communicating High Level Assembly Changes to Suppliers |
 |
 |
 |
|
Friday, 08 September 2006 11:59 |
|
Need Help:Communicating High Level Assembly (HLA) changes to suppliers
Our company tries as frequently as possible to buy at the highest level assembly (HLA) possible. Within the HLA, there are other assemblies that are purchased from other vendors before all the assemblies come together to form the HLA. We need to communicate the documentation & BOM to each supplier every time the HLA or one of its purchased assemblies changes. We are struggling with how to communicate this.
Although the normal mechanism would be to communicate changes when a revision changes, there is some resistance to this since there are thousands of part records and drawings to change and many *MANY* business rules involved in doing so. Programmatically, we can't determine which parts are HLAs. Right now a separate list is kept.
In brainstorming, ideas brought up to communicate HLA changes to vendors has been:
-1.Foward Compliance, but this is not closed loop since suppliers are not forced to acknowledge that they have obtained the updated drawings & BOMs and taken action n them.
-2. Email to all affected suppliers and the buyers that work with the suppliers. Then asking each party to take action, following up through our portals that allow formal communication to take place and also where the documentation can be obtained.
-3. A special revisioning system that breaks all the rules (no or limited checks) so that HLA revisions can be changed quickly so that communication regarding the change can take place within normal means of communicating change.
What do you think? Do you know anyone already dealing with communicating High Level Assembly changes to suppliers?
|
|
Last Updated on Friday, 08 September 2006 12:00 |
Users: If you have a Gmail account, you do not need to register; you may login using your full Gmail account username and password.
Article Index 
