130 likes | 313 Views
PDQ Policy to improve OEMs-Suppliers Data Exchanges ProSTEP iViP Symposium 2007. Direction des Systèmes d’Information RENAULT. 25/04/2007. Summary. Basic issues Consequences PDQ History RENAULT PDQ history (milestones) Deployment roadmap of CATIA PDQ Zoom on the deployment of CATIA
E N D
PDQ Policy to improve OEMs-Suppliers Data Exchanges ProSTEP iViP Symposium 2007 Direction des Systèmes d’Information RENAULT 25/04/2007
Summary • Basic issues • Consequences • PDQ History • RENAULT PDQ history (milestones) • Deployment roadmap of CATIA PDQ • Zoom on the deployment of CATIA • CATIA V4 • CATIA V5 • Some results (graphics, focus on Catia V5) • Next steps • Profit evaluation • Conclusion
Basic issues • Data Exchanges between CAD systems have always been difficult. • Waste of time, and loose of information. • Rebuild of the digitalisation, • Misunderstanding • Errors of translation • Multiple loops of exchange • The Management ignore that issue • Data exchange must be fluent and free of expenses • Data Exchange never improve the quality of the data : • Garbage in, garbage out…
Consequences • To ensure a completed Data exchange : • The main issue is the quality of the digitalisation, • and the only efficient way is to work on the original digitalisation. • We defined digitalisation quality rules • such as their use ensure as much as possible the completion of the exchange
RENAULT PDQ history (milestones) • Some Quality rules were used in Euclid at the end of the 80’s to help the supplier chain. • GALIA et VDA Geometrical Guidelines were written. • 3 CAD systems were available in 1998 in Renault • Catia V4 was especially sensitive to imported data • SASIG workshops on PDQ (1999-2007…) • SASIG PDQ Guidelines • Deployment of CATIA V4 checks (2001). • Deployment of CATIA V5 checks (2005). • GALIA Workshop on Catia V5 PDQ (2006).
Deployment roadmap of CATIA PDQ • Steps of the deployment : • First, some Quality rules within Catia V4 (/cln) • Then, use of an external checking tool • Then, insertion of the checking tool in the PDM • Then, Quality results targets • Then, implication of the suppliers • At last but not least, the recording in the PDM is forbidden in case of lack of quality. • To be followed by : • Some Catia V5 rules checked in the PDM. • Increasing of the number of Catia V5 checks.
Results Within PQA versions, 2005 2006 2007 2008
Results • The users point of view • Checking time must be as short as possible • Quality rules must be easy to understand 3’00’’ 2’35’’ 1’50’’ 1’44’’
Results • Focus on the two main Renault Engineer Departments : Mechanical Department (grey) Vehicle Department (yellow – “under construction” data / red - official data).
Next steps • The next steps 2007-2008 • 3 PQA releases • C5I21 vs. current release + 6 checks • C5I22 vs. C5I21 + 13 checks • C5I23 vs. C5I22 + 4 checks (then still 16 checks to reach the current target) • 100% official data stored in the PDM with no K1 errors.
Profit Evaluation Example
Conclusions • We know the amount of money which can be saved is significant, despite the fact that it is rather difficult to evaluate it… • The PDQ Policy is currently mainly accepted by all actors in OEMs-Supplier automotive industry. The rate of data with a good Quality rate is significant (more that 95% of the official data). • To be more efficient, a target could be to share the common main Quality rules among major OEMs and Suppliers. That’s what we do in France, at least…