Regarding the identification of suppliers, product development emphasizes more on the identification of suppliers. In process development, emphasis is placed both on identifying important technology as well as important suppliers. The selection of suppliers for process development should place greater emphasis on the technical capability of the suppliers.
Below is a model by Jiao et al( 2008) which compares ESI implementation with focus on product development and process development.
Supplier selection criteria for process development have to emphasize more on technology capability of the supplier rather than total cost of ownership. Even though a supplier may have a higher total cost of ownership, the company is forced to engage it when it is the only company with the technical expertise. In addition, obtaining suppliers' feedback regularly is important because they are the company's “informants” on new technology. Furthermore, process developments are more dependent on the OEMs because they produce the equipment. (Jiao et al, 2008)
Supplier development has 4 stages. It includes identifying the supplier base as well as assessing and rationalizing, problem solving improvement, proactive condition development, and integration development.
Aligning the processes has the additional advantage of increasing consistency and compatibility between the product design and plant capabilities, allowing a company to reduce tooling and manufacturing costs, and recover investment (Liker et al., 1996).
The creation of an agreed ``co-development process'' was felt to be accelerated when organizations conduct the activity together.
However the challenge is how to improve the co development performance and how the separate processes and design teams of each organization could be integrated and aligned to improve their combined performance.
The model by Evans and Jukes (2000) suggests that the alignment of processes proceeds in a series of steps, supported by joint team working.
In the first step you need to understand and internalize your customers' product development cycle, and learn to synchronize internal product development practices to fulfill time, cost, and product requirements (Kamath and Liker, 1994).
The second phase of process alignment requires knowledge to be shared across the collaborating organizations, the objective of which is to secure an in-depth understanding of each other's current practices.
Building a co-development framework is the third phase in the alignment process. This requires the synchronization of both development processes to ensure compatibility and waste elimination between the organizations.
The final step closes the loop and lesson learnt from the process is used as feedback for continuously improving subsequent processes.
The capture, application and embedding of ‘lessons learnt’ within a Full Service Supplier environment is a complex task for any vehicle manufacturer. Capturing ‘lessons learnt’ relates to organizational learning and four stages of learning were identified which are: Knowledge acquisition, Knowledge dissemination, Knowledge utilization, Knowledge keeping. [Southey et al 2000]:
4-NISSAN COGENT
Nissan’s European Technology Centre (NETC) and Cranfield University, both based at Cranfield, UK did a three year, three million pound co-development research project called ‘Cogent’ involving the participation of 85 of Nissan’s suppliers. The main objective of the project was to improve the co-development capabilities of Nissan and its suppliers in order to reduce both product development times and costs by a targeted 30% in three years. They identified that the suppliers’ design and development processes have to be of a very high standard in order to achieve ‘right first time’ designs and hence avoid late engineering changes and duplication of effort. Workshops at several levels of supplier management was conducted in order to develop, communicate and embed their co-development process understanding.(Southey et al., 2000)
Nissan identified that if the design is right first time, with early concurrent input from suppliers and manufacturing associates, then fewer additional costs subsequently occur during the design release, testing, manufacturing and assembly stages. With the earlier involvement of suppliers up front in the pre-design stage, such engineering change costs have been taken out and hence duplication avoided. At the design and development stage
Nissan applies all lessons learnt from previous projects (Southey et al., 2000).
NETC uses the ‘Merlin exercise’ to identify common problems existing between itself and its suppliers. After identifying what problems occurred along the way and how they overcame the obstacles, each individual issue was then uniquely addressed and solutions were jointly developed between Nissan and suppliers. The major issues revealed on a real development project between Nissan and its co-development suppliers were trust, communication, willingness to share confidential information and cost. Through working through these issues jointly with its suppliers, and through jointly developing an objective (rather than subjective) performance measurement system for design and development processes, Nissan has achieved the following substantial improvements on a recent model replacement program:
• 30% faster design time
• 40% reduced design budget
• 34% reduced part cost - across the vehicle (Southey et al., 2000)
The main focus of COGENT is to improve communication and understanding between the supplier and customer at the very earliest stage so that what follows is a natural co-development environment eliminating waste at every stage.
Cogent fast track concentrated on; aligned perceptions, aligned processes and aligned targets.
Steps were the same in each workshop
- Where do we want to be? in terms of world class performance levels of development
- Where are we now?
- How do we get there? Prioritization and improvement plan
- Implement improvement plan
- Monitor improvement plan At the end of it every supplier ended up with mutually agreed actions:
- Implement- review- improve plans
- Monitor-measure improvements
- Deliver the project
5- FINDINGS
The following driving forces were identified as reasons to establish co-development and lessons learnt processes with their first tier suppliers:
1- Cost reductions from the capture of ‘cost-down’ ideas prior to design commitment enable the embedding of savings at the conception stage.
2-Cost reductions through the standardization of designs and design processes, between Nissan and its supplier.
3- Aligned customer/supplier design processes lead to reduced design time and more robust design solutions with fewer engineering changes.
4- Co-development and ‘lessons learnt’ capture lead to higher designed-in product quality leading to higher customer satisfaction and reduced risk of product failure.
5- The embedding of processes which address environmental issues, (e.g. reducing waste and scrap, improving energy management etc.) and attack environmentally harmful or inefficient processes (e.g. changing from toxic paint plant chemicals, recycling paper, specifying reusable packaging etc) leads to lower total costs, lower environmental impact costs and an improved public profile.
From analysis of the case study by Southey et al., (2000), the barriers identified to improving co-development performance were found to be: Trust, Communication, Geography, Supplier changes, Constancy of design teams, Capturing ‘lessons learnt’, Alignment, Developing common industry standards
From the Nissan Cogent program, the following eight elements were also have been found to underpin improved co-development performance (Southey et al., 2000):
1 Co-development is primarily concerned with alignment of objectives, processes and targets, not with improving suppliers’ design expertise.
2 Internal consistencies within the customer is an important prerequisite for significant co-development improvement.
3 Improving communication and openness between a VM and its suppliers is accelerated by using a third party facilitator.
4 An objective performance measurement system is the best steering mechanism for setting and achieving improvement targets.
5 Enormous attentions to detail is required in order to remove the potential for stress and mistrust between VMs’ and suppliers’ representatives, and to ensure that agreed processes are repeated and embedded as a common way of working.
6 Co-development performance improvements is best pioneered on a real development project, so that all participants are focused by real targets and deadlines
7 Co-development improvements require enormous amounts of planning and execution time in order to overcome people’s natural fear, mistrust and resistance to change.
8 The intangible elements of a successful co-development program include a strong
belief in the principles of co-development, a tight process, great attention to detail to ensure the co-development processes become embedded, and a lot of effort and determination to overcome numerous ‘insurmountable problems’ and people issues.
6- COGENT FUTURE WORKS
Cogent can still be improved by taking the process to the second tier suppliers
7-CONCLUSSION
It is not just technical expertise in a variety of disciplines that is needed to rapidly develop a new product, but it is the way that this expertise is applied and integrated. Co development is primarily concerned with alignment. Internal consistency between the customers and suppliers processes is an important prerequisite for significant co development improvement.
For the best outcome and performance from the suppliers it is important to maintain a good communication with them. Supplier development is a crucial fact for the benefit of the buyer company. Supply chain integration and improvisation process of Nissan, which is known as COGENT, has increased the performance level of the company in various issues such as supply cost reduction, raw material and inventory maintenance, cost reduction and transport cost minimization. As COGENT case study describes, Nissan achieved NEXT21 goal by co-development and alignment, improved internal consistency for development, involvement of third party, use of performance measurement system, focusing on a real project and use of detail while interact and use the events as accelerators
8-REFERENCES
Southey, P., Steeple, D., and Wilhelm, M., (2000) “Buyer-supplier co-development in UK automotive manufacturing: Closing the continuous improvement loop”, Int. J. Manufacturing Technology and Management, Vol. 2, Nos. 1-7.
Stephen, E. and Jukes, S. (2000) “Improving co-development through process alignment”. International Journal of Operations and Production Management. 20 (8) 979 – 988
Nissan-Cogent Supply Chain Management Case Study (2010) Nissan Cogent Case [online] available from < http://www.scribd.com/doc/44579720/Nissan-Cogent-Supply-Chain-Management-Case-Study> [15 January 2011]
Yuan-Yuan Jiao, Jun Du, Roger J. Jiao, David L. Butler, (2008) "Operational implications of early supplier involvement in semiconductor manufacturing firms: A case study", Journal of Manufacturing Technology Management, Vol. 19 Iss: 8, pp.913 – 932
S. Dowlatshahi (1998) “Implementing early supplier involvement: a conceptualframework “
Daniel R. Krause , Robert B. Handfield , Thomas V. Scannell (1998) “An empirical investigation of supplier development: reactive and strategic processes” Journal of Operations Management 17 _1998. 39–58
Dyer, J.H., (1996), “How Chrysler created an American keiretsu’” Harvard Business Review, Vol. 74, No. 4, pp. 42–56.
Milburn, I. (1996) “How goes Nissan’s Supplier Improvement Programme?” The Automotive Engineer 21 (4) 65-66
Nissan-Cogent Supply Chain Management Case Study (2010) Nissan Cogent Case [online] available from < http://www.scribd.com/doc/44579720/Nissan-Cogent-Supply-Chain-Management-Case-Study> [15 January 2011]
Nissan Motor Manufacturing (UK) Ltd – The supplier Development Team Approach. Case Studies in Changing External Relationships. Ch9. p281
Southey, P., Steeple, D., and Wilhelm, M., (2000) “Buyer-supplier co-development in UK automotive manufacturing: Closing the continuous improvement loop”, Int. J. Manufacturing Technology and Management, Vol. 2, Nos. 1-7.
Stephen, E. and Jukes, S. (2000) “Improving co-development through process alignment”. International Journal of Operations and Production Management. 20 (8) 979 – 988
Keah-Choon Tan, Vijay R. Kannan, Robert B. Handfield, Soumen Ghosh, (1999) "Supply chain management: an empirical study of its impact on performance", International Journal of Operations & Production Management, Vol. 19 Iss: 10, pp.1034 - 1052
M25 – EKM SUPPLY CHAIN MANAGEMENT