SlideShare a Scribd company logo
New ProductIntroduction(NPI) Case Study
Project Scope:
The strategic goal of the project was to reduce the cycle time of the New Product Introduction
(NPI) process on a wet process tool for the semiconductor industry. This was a very complex
product with significant untried technologies. In the past, these types of products have taken
the company up to 39-weeks to complete. This exorbitant amount of time caused the
company to lose sales, affecting their bottom line. Our goal was to reduce this time to less
than 12-weeks, a 67% improvement in cycle time, while creating a repeatable NPI process.
This same process can be applied over a variety of industries. A side benefit of this
transformation was a tremendous shift in the culture of the business and the opportunity to
establish teamwork.
Boundaries:
The boundaries of the project began with the product development phase and went through
the integration of the new product into the mainstream of manufacturing and full production.
TeamMembers:
 Demand Planning Representative
 Engineering Representative
 Manufacturing Engineering Representative
 Manufacturing Management Representative
 Marketing Representative
 Materials Representative
 Production Scheduling Representative
 Project Champion
 Project Manager
 Quality Representative
 Safety Representative
Tools Deployed
Software:
 Microsoft Project® – Project management tool used as the master schedule
 SolidWorks® - 3D modeling tool used to layout the manufacturing cell
Quality Analysis:
 Design Failure Mode and Effects Analysis (DFMEA) – Reliability used tool to evaluate the
product design
 Process Failure Mode and Effect Analysis (PFMEA) – Reliability tool used to evaluate the
manufacturing process
 Process Mapping – Tool utilized to define the process flow within the manufacturing process
 Spaghetti Diagram – A Tool utilized to identify any redundancies within the workflow and
opportunities to expedite process flow.
 Gage R&R – Analysis tool used to define the capability of the test and measurement
equipment
Safety Analysis:
 Equipment Safety Assessment Forms – Safety assessment of the manufacturing equipment
 Process and Materials Safety Assessment – Safety assessment of the process and
materials specified within the new product design
New ProductIntroduction Case Study (con’t)
Project Review:
The project started by commissioning a cross-functional team (engineering, manufacturing,
marketing, materials, production, scheduling and quality) to streamline the New Product
Introduction process. By forming a cross-functional team, we began removing the silos within the
organization, giving project ownership to the supporting departments. This improved the lines of
communication between the departments and gave them a contact within the other departments.
This was a significant cultural event for the organization as well, one of the side benefits of the
project.
The project team developed a master schedule using Microsoft Project®. The supporting
departments identified the tasks required to complete their segment of the project. From the
departments’ input, the Project Manager (PM) compiled these tasks into the Master Project
Schedule (MPS). Employing the MPS enabled the PM to effectively direct and monitor the
progression of the project. The MPS was stored on the company drive and accessible to all team
members and management team. This action also started to break down some of the silos and
walls within the organization.
The PM scheduled weekly meetings to review the progress of the project, providing an avenue for
the team members to voice their concerns (apparent or potential) with either the MPS or product
design. As team members encountered problems, the members discussed resolutions to the
problems within the framework of the weekly meeting. If a problem required additional follow-up,
the PM assigned a task, with an expected completion date, to member(s) of the team then
followed up on the assignment during the ensuing meetings. Though the duration of these
meetings were short, less than 1-hour, the interaction between team members was crucial to the
success of the project. The meetings ensured timely transfer of information between the
department representatives, enabling the individual departments to manager their portions of the
project and the ability to respond faster as changes arise. This changed the organizations focus to
more of a communicative one.
At key points within the MPS, the PM deployed certain Lean Six Sigma quality tools. The tools
applied assessed the product design, the manufacturing process and equipment. The timely
deployment of these quality tools and the information acquired were vital to the successful
completion of this project.
Early in the design phase, the team conducted a Design Failure Mode Effect Analysis (DFMEA) of
the new product. From this analysis, the project team identified potential failure points within
product design. The early deployment of the DFMEA provided the necessary time for the project
team to design these failures points out of the product without affecting the scheduled release
date of the new product.
Upon finalizing the product design, the team entered the new items (raw materials and final
assemblies) and engineering BOMs into the business system. From this information, along with
the demand planning information, the team was able to communicate the demand requirements
with the suppliers. By communicating these requirements with the supplier, the team was able to
secure all materials needed in time for the product launch.
After the completion of the DFMEA, the project team began developing the manufacturing
process. Using a process-mapping tool, the project team constructed the manufacturing process
then evaluated the process using the Process Failure Mode Effect Analysis (PFMEA) tool. The
New ProductIntroduction Case Study (con’t)
outcome of the process mapping and PFMEA process, the project team developed the
manufacturing process and identified the supporting manufacturing equipment.
While developing the manufacturing process, the project team conducted the safety assessment
of the manufacturing process and materials. From the safety assessment, the team identified
several manufacturing materials were hazardous to the health of the assembler. Since team could
not eliminate these materials, the manufacturing team designed special handling equipment into
the process to remove the assemblers’ risk of exposure to the hazardous materials.
Using SolidWorks® (3D modeling software), the project team designed the layout of the
manufacturing cell. From this layout, the project team identified redundancies within the workflow
and expedited the process flow using a Spaghetti Diagram. Information obtained from the
development of the Spaghetti Diagram, the team optimized the workflow within the manufacturing
cell prior to moving in the manufacturing equipment.
As the new production equipment arrived, the project team validated the equipment’s
performance to the process requirement and conducted the new equipment safety assessment
prior to releasing the equipment to the manufacturing group. By evaluating the equipment at the
time of arrival, provided the project group the time required to make any modifications to the
equipment without effecting the release date of the new product.
Prior to releasing the test and measurement equipment, the project team calibrated and
conducted a Gage R&R analysis. From the information obtained from the Gage R&R analysis, the
project team implemented the Statistical Process Control (SPC) parameters used to monitor
performance of the manufacturing process.
Conclusion:
With the introduction of the New Product Introduction (NPI) process improvements, the project
team was able to reduce the introduction time of a new product by over 70% by reducing the
cycle time of the process from 39-weeks to 9-weeks. In addition, the team established a process
to capture the costs (labor hours and expenditures) associated with a new product development.
This new process developed an interactive system between the departments, allowing timely
transfer of information between the department representatives, enabled the individual
departments to manager their portions of the project and the ability to react faster as changes
arise. The team was able to update the project status while getting buy in through all stakeholders
by sharing the status on a company drive where all had read access and could monitor project
leaving very little time for static on follow up with the management team. An additional benefit,
which was not part of the original mission, was the culture shift in the organization. Sometime the
cultural shift in an organization, the desire to manage the right way is sometimes obscured by the
desire to successfully launch a new product, this helped tear down those walls and unify the
team.
The process is then used for all of the development projects coming out of engineering
substantially reducing lead time and managing cost expectations as well as delivering quality
prototypes into the customers hands far earlier than expected.

More Related Content

What's hot

Pmp capm exam preparation
Pmp capm exam preparationPmp capm exam preparation
Pmp capm exam preparation
Freedom Monk
 
9.process improvement chapter 9
9.process improvement chapter 99.process improvement chapter 9
9.process improvement chapter 9
Warui Maina
 
Project Health Check
Project Health CheckProject Health Check
Project Health Check
ihoudane
 
Pre planning for large ERP/CRM initiative
Pre planning for large ERP/CRM  initiativePre planning for large ERP/CRM  initiative
Pre planning for large ERP/CRM initiative
sureshgk
 
CMMI & PMBOK & OPM3
CMMI & PMBOK & OPM3CMMI & PMBOK & OPM3
CMMI & PMBOK & OPM3
DilekOzdemirci
 
Supply Chain Liaison 5 Step Management Program
Supply Chain Liaison 5 Step Management ProgramSupply Chain Liaison 5 Step Management Program
Supply Chain Liaison 5 Step Management Program
Stephen O'Neil
 
A Guide to the Forthcoming 2012 Revision of the IEEE Software Quality Assuran...
A Guide to the Forthcoming 2012 Revision of the IEEE Software Quality Assuran...A Guide to the Forthcoming 2012 Revision of the IEEE Software Quality Assuran...
A Guide to the Forthcoming 2012 Revision of the IEEE Software Quality Assuran...
dheimann5
 
Alleman coonce-agile-2017 may2
Alleman coonce-agile-2017 may2Alleman coonce-agile-2017 may2
Alleman coonce-agile-2017 may2
Glen Alleman
 
Project quality management - PMI PMBOK Knowledge Area
Project quality management - PMI PMBOK Knowledge AreaProject quality management - PMI PMBOK Knowledge Area
Project quality management - PMI PMBOK Knowledge Area
Imran Jamil
 
Infodream Articles about Continuous Improvement, Aerospace, Quality Control a...
Infodream Articles about Continuous Improvement, Aerospace, Quality Control a...Infodream Articles about Continuous Improvement, Aerospace, Quality Control a...
Infodream Articles about Continuous Improvement, Aerospace, Quality Control a...
Infodream
 
software engineering
software engineeringsoftware engineering
software engineering
shreeuva
 
John Glenning's Process Development and Manufacturing Strategy
John Glenning's Process Development and Manufacturing StrategyJohn Glenning's Process Development and Manufacturing Strategy
John Glenning's Process Development and Manufacturing Strategy
John Glenning
 
Project Management
Project ManagementProject Management
Project Management
Prarthan P
 
Project quality management
Project quality managementProject quality management
Project quality management
Mohammad Ashraf Khan, PMP
 
Project Health Checks
Project Health ChecksProject Health Checks
Project Health Checks
Torsten Koerting
 
Quality management strategy example
Quality management strategy exampleQuality management strategy example
Quality management strategy example
selinasimpson1201
 
RamkumarMV15
RamkumarMV15RamkumarMV15
AGILE PORTUGAL 2016: Adopted agile in a CMMI L5 enterprise: what were the fin...
AGILE PORTUGAL 2016: Adopted agile in a CMMI L5 enterprise: what were the fin...AGILE PORTUGAL 2016: Adopted agile in a CMMI L5 enterprise: what were the fin...
AGILE PORTUGAL 2016: Adopted agile in a CMMI L5 enterprise: what were the fin...
Délio Almeida
 
Contracting for Agile Software Development
Contracting for Agile Software DevelopmentContracting for Agile Software Development
Contracting for Agile Software Development
cspag67
 
Project Quality Planning and KickOff
Project Quality Planning and KickOffProject Quality Planning and KickOff
Project Quality Planning and KickOff
kaushikanirudh
 

What's hot (20)

Pmp capm exam preparation
Pmp capm exam preparationPmp capm exam preparation
Pmp capm exam preparation
 
9.process improvement chapter 9
9.process improvement chapter 99.process improvement chapter 9
9.process improvement chapter 9
 
Project Health Check
Project Health CheckProject Health Check
Project Health Check
 
Pre planning for large ERP/CRM initiative
Pre planning for large ERP/CRM  initiativePre planning for large ERP/CRM  initiative
Pre planning for large ERP/CRM initiative
 
CMMI & PMBOK & OPM3
CMMI & PMBOK & OPM3CMMI & PMBOK & OPM3
CMMI & PMBOK & OPM3
 
Supply Chain Liaison 5 Step Management Program
Supply Chain Liaison 5 Step Management ProgramSupply Chain Liaison 5 Step Management Program
Supply Chain Liaison 5 Step Management Program
 
A Guide to the Forthcoming 2012 Revision of the IEEE Software Quality Assuran...
A Guide to the Forthcoming 2012 Revision of the IEEE Software Quality Assuran...A Guide to the Forthcoming 2012 Revision of the IEEE Software Quality Assuran...
A Guide to the Forthcoming 2012 Revision of the IEEE Software Quality Assuran...
 
Alleman coonce-agile-2017 may2
Alleman coonce-agile-2017 may2Alleman coonce-agile-2017 may2
Alleman coonce-agile-2017 may2
 
Project quality management - PMI PMBOK Knowledge Area
Project quality management - PMI PMBOK Knowledge AreaProject quality management - PMI PMBOK Knowledge Area
Project quality management - PMI PMBOK Knowledge Area
 
Infodream Articles about Continuous Improvement, Aerospace, Quality Control a...
Infodream Articles about Continuous Improvement, Aerospace, Quality Control a...Infodream Articles about Continuous Improvement, Aerospace, Quality Control a...
Infodream Articles about Continuous Improvement, Aerospace, Quality Control a...
 
software engineering
software engineeringsoftware engineering
software engineering
 
John Glenning's Process Development and Manufacturing Strategy
John Glenning's Process Development and Manufacturing StrategyJohn Glenning's Process Development and Manufacturing Strategy
John Glenning's Process Development and Manufacturing Strategy
 
Project Management
Project ManagementProject Management
Project Management
 
Project quality management
Project quality managementProject quality management
Project quality management
 
Project Health Checks
Project Health ChecksProject Health Checks
Project Health Checks
 
Quality management strategy example
Quality management strategy exampleQuality management strategy example
Quality management strategy example
 
RamkumarMV15
RamkumarMV15RamkumarMV15
RamkumarMV15
 
AGILE PORTUGAL 2016: Adopted agile in a CMMI L5 enterprise: what were the fin...
AGILE PORTUGAL 2016: Adopted agile in a CMMI L5 enterprise: what were the fin...AGILE PORTUGAL 2016: Adopted agile in a CMMI L5 enterprise: what were the fin...
AGILE PORTUGAL 2016: Adopted agile in a CMMI L5 enterprise: what were the fin...
 
Contracting for Agile Software Development
Contracting for Agile Software DevelopmentContracting for Agile Software Development
Contracting for Agile Software Development
 
Project Quality Planning and KickOff
Project Quality Planning and KickOffProject Quality Planning and KickOff
Project Quality Planning and KickOff
 

Viewers also liked

Npi retail case studies
Npi retail case studiesNpi retail case studies
Npi retail case studies
Nitai Partners Inc
 
New Product development presentation
New Product development presentationNew Product development presentation
New Product development presentation
optiplex7866
 
Psychological test report ht pt
Psychological test report ht ptPsychological test report ht pt
Psychological test report ht pt
Polytechnic University of the Philippines
 
New product development
New product developmentNew product development
New product development
shdeepa
 
Full Psychological Report.Sample
Full Psychological Report.SampleFull Psychological Report.Sample
Full Psychological Report.Sample
debrajean333
 
New Product Development
New Product DevelopmentNew Product Development
New Product Development
Vishal Thakur
 
New Product Development
New Product DevelopmentNew Product Development
New Product Development
s junaid
 
New product devlopment ppt
New product devlopment pptNew product devlopment ppt
New product devlopment ppt
Rameshwar Swami
 
new-product-development-process
new-product-development-processnew-product-development-process
new-product-development-process
arunalapati
 

Viewers also liked (9)

Npi retail case studies
Npi retail case studiesNpi retail case studies
Npi retail case studies
 
New Product development presentation
New Product development presentationNew Product development presentation
New Product development presentation
 
Psychological test report ht pt
Psychological test report ht ptPsychological test report ht pt
Psychological test report ht pt
 
New product development
New product developmentNew product development
New product development
 
Full Psychological Report.Sample
Full Psychological Report.SampleFull Psychological Report.Sample
Full Psychological Report.Sample
 
New Product Development
New Product DevelopmentNew Product Development
New Product Development
 
New Product Development
New Product DevelopmentNew Product Development
New Product Development
 
New product devlopment ppt
New product devlopment pptNew product devlopment ppt
New product devlopment ppt
 
new-product-development-process
new-product-development-processnew-product-development-process
new-product-development-process
 

Similar to RGP--NPI Case Study July 2016

Quality Management Practice in IT Projects
Quality Management Practice in IT ProjectsQuality Management Practice in IT Projects
Quality Management Practice in IT Projects
Monzer Osama Alchikh WARAK
 
Software engg. pressman_ch-21
Software engg. pressman_ch-21Software engg. pressman_ch-21
Software engg. pressman_ch-21
Dhairya Joshi
 
Software Product Life Cycle
Software Product Life CycleSoftware Product Life Cycle
Software Product Life Cycle
Mahesh Panchal
 
Project Management Complete Concept
Project Management Complete Concept Project Management Complete Concept
Project Management Complete Concept
MuhammadTalha436
 
Presentation by lavika upadhyay
Presentation by lavika upadhyayPresentation by lavika upadhyay
Presentation by lavika upadhyay
PMI_IREP_TP
 
Software
SoftwareSoftware
Software
Parul Gupta
 
Managing Software Project
Managing Software ProjectManaging Software Project
Managing Software Project
Anas Bilal
 
Design Review Mini
Design Review MiniDesign Review Mini
Design Review Mini
ahmad bassiouny
 
Design Review Mini(2)
Design Review Mini(2)Design Review Mini(2)
Design Review Mini(2)
ahmad bassiouny
 
significance_of_test_estimating_in_the_software_development.pdf
significance_of_test_estimating_in_the_software_development.pdfsignificance_of_test_estimating_in_the_software_development.pdf
significance_of_test_estimating_in_the_software_development.pdf
sarah david
 
significance_of_test_estimating_in_the_software_development.pptx
significance_of_test_estimating_in_the_software_development.pptxsignificance_of_test_estimating_in_the_software_development.pptx
significance_of_test_estimating_in_the_software_development.pptx
sarah david
 
1 P a g e Going Agile – A Case Study Dwayne .docx
1  P a g e  Going Agile – A Case Study  Dwayne .docx1  P a g e  Going Agile – A Case Study  Dwayne .docx
1 P a g e Going Agile – A Case Study Dwayne .docx
honey725342
 
Case Study - Rescuing a Troubled Project C.A. McCall-Peat Liberty Li.pdf
Case Study - Rescuing a Troubled Project C.A. McCall-Peat Liberty Li.pdfCase Study - Rescuing a Troubled Project C.A. McCall-Peat Liberty Li.pdf
Case Study - Rescuing a Troubled Project C.A. McCall-Peat Liberty Li.pdf
sales88
 
Tp88 pub45
Tp88 pub45Tp88 pub45
Tp88 pub45
Dave Davidson
 
(Fall2016)Lecture1.pptx
(Fall2016)Lecture1.pptx(Fall2016)Lecture1.pptx
(Fall2016)Lecture1.pptx
garkapifye
 
Bca 5th sem seminar(software measurements)
Bca 5th sem seminar(software measurements)Bca 5th sem seminar(software measurements)
Bca 5th sem seminar(software measurements)
MuskanSony
 
Fixed Price Distributed Agile Projects
Fixed Price Distributed Agile ProjectsFixed Price Distributed Agile Projects
Fixed Price Distributed Agile Projects
Raja Bavani
 
SE_Lec 04_Agile Software Development
SE_Lec 04_Agile Software DevelopmentSE_Lec 04_Agile Software Development
SE_Lec 04_Agile Software Development
Amr E. Mohamed
 
Debahis CV
Debahis CVDebahis CV
Debahis CV
priyacivil93
 
SE chapters 21-23
SE chapters 21-23SE chapters 21-23
SE chapters 21-23
Hardik Patel
 

Similar to RGP--NPI Case Study July 2016 (20)

Quality Management Practice in IT Projects
Quality Management Practice in IT ProjectsQuality Management Practice in IT Projects
Quality Management Practice in IT Projects
 
Software engg. pressman_ch-21
Software engg. pressman_ch-21Software engg. pressman_ch-21
Software engg. pressman_ch-21
 
Software Product Life Cycle
Software Product Life CycleSoftware Product Life Cycle
Software Product Life Cycle
 
Project Management Complete Concept
Project Management Complete Concept Project Management Complete Concept
Project Management Complete Concept
 
Presentation by lavika upadhyay
Presentation by lavika upadhyayPresentation by lavika upadhyay
Presentation by lavika upadhyay
 
Software
SoftwareSoftware
Software
 
Managing Software Project
Managing Software ProjectManaging Software Project
Managing Software Project
 
Design Review Mini
Design Review MiniDesign Review Mini
Design Review Mini
 
Design Review Mini(2)
Design Review Mini(2)Design Review Mini(2)
Design Review Mini(2)
 
significance_of_test_estimating_in_the_software_development.pdf
significance_of_test_estimating_in_the_software_development.pdfsignificance_of_test_estimating_in_the_software_development.pdf
significance_of_test_estimating_in_the_software_development.pdf
 
significance_of_test_estimating_in_the_software_development.pptx
significance_of_test_estimating_in_the_software_development.pptxsignificance_of_test_estimating_in_the_software_development.pptx
significance_of_test_estimating_in_the_software_development.pptx
 
1 P a g e Going Agile – A Case Study Dwayne .docx
1  P a g e  Going Agile – A Case Study  Dwayne .docx1  P a g e  Going Agile – A Case Study  Dwayne .docx
1 P a g e Going Agile – A Case Study Dwayne .docx
 
Case Study - Rescuing a Troubled Project C.A. McCall-Peat Liberty Li.pdf
Case Study - Rescuing a Troubled Project C.A. McCall-Peat Liberty Li.pdfCase Study - Rescuing a Troubled Project C.A. McCall-Peat Liberty Li.pdf
Case Study - Rescuing a Troubled Project C.A. McCall-Peat Liberty Li.pdf
 
Tp88 pub45
Tp88 pub45Tp88 pub45
Tp88 pub45
 
(Fall2016)Lecture1.pptx
(Fall2016)Lecture1.pptx(Fall2016)Lecture1.pptx
(Fall2016)Lecture1.pptx
 
Bca 5th sem seminar(software measurements)
Bca 5th sem seminar(software measurements)Bca 5th sem seminar(software measurements)
Bca 5th sem seminar(software measurements)
 
Fixed Price Distributed Agile Projects
Fixed Price Distributed Agile ProjectsFixed Price Distributed Agile Projects
Fixed Price Distributed Agile Projects
 
SE_Lec 04_Agile Software Development
SE_Lec 04_Agile Software DevelopmentSE_Lec 04_Agile Software Development
SE_Lec 04_Agile Software Development
 
Debahis CV
Debahis CVDebahis CV
Debahis CV
 
SE chapters 21-23
SE chapters 21-23SE chapters 21-23
SE chapters 21-23
 

RGP--NPI Case Study July 2016

  • 1. New ProductIntroduction(NPI) Case Study Project Scope: The strategic goal of the project was to reduce the cycle time of the New Product Introduction (NPI) process on a wet process tool for the semiconductor industry. This was a very complex product with significant untried technologies. In the past, these types of products have taken the company up to 39-weeks to complete. This exorbitant amount of time caused the company to lose sales, affecting their bottom line. Our goal was to reduce this time to less than 12-weeks, a 67% improvement in cycle time, while creating a repeatable NPI process. This same process can be applied over a variety of industries. A side benefit of this transformation was a tremendous shift in the culture of the business and the opportunity to establish teamwork. Boundaries: The boundaries of the project began with the product development phase and went through the integration of the new product into the mainstream of manufacturing and full production. TeamMembers:  Demand Planning Representative  Engineering Representative  Manufacturing Engineering Representative  Manufacturing Management Representative  Marketing Representative  Materials Representative  Production Scheduling Representative  Project Champion  Project Manager  Quality Representative  Safety Representative Tools Deployed Software:  Microsoft Project® – Project management tool used as the master schedule  SolidWorks® - 3D modeling tool used to layout the manufacturing cell Quality Analysis:  Design Failure Mode and Effects Analysis (DFMEA) – Reliability used tool to evaluate the product design  Process Failure Mode and Effect Analysis (PFMEA) – Reliability tool used to evaluate the manufacturing process  Process Mapping – Tool utilized to define the process flow within the manufacturing process  Spaghetti Diagram – A Tool utilized to identify any redundancies within the workflow and opportunities to expedite process flow.  Gage R&R – Analysis tool used to define the capability of the test and measurement equipment Safety Analysis:  Equipment Safety Assessment Forms – Safety assessment of the manufacturing equipment  Process and Materials Safety Assessment – Safety assessment of the process and materials specified within the new product design
  • 2. New ProductIntroduction Case Study (con’t) Project Review: The project started by commissioning a cross-functional team (engineering, manufacturing, marketing, materials, production, scheduling and quality) to streamline the New Product Introduction process. By forming a cross-functional team, we began removing the silos within the organization, giving project ownership to the supporting departments. This improved the lines of communication between the departments and gave them a contact within the other departments. This was a significant cultural event for the organization as well, one of the side benefits of the project. The project team developed a master schedule using Microsoft Project®. The supporting departments identified the tasks required to complete their segment of the project. From the departments’ input, the Project Manager (PM) compiled these tasks into the Master Project Schedule (MPS). Employing the MPS enabled the PM to effectively direct and monitor the progression of the project. The MPS was stored on the company drive and accessible to all team members and management team. This action also started to break down some of the silos and walls within the organization. The PM scheduled weekly meetings to review the progress of the project, providing an avenue for the team members to voice their concerns (apparent or potential) with either the MPS or product design. As team members encountered problems, the members discussed resolutions to the problems within the framework of the weekly meeting. If a problem required additional follow-up, the PM assigned a task, with an expected completion date, to member(s) of the team then followed up on the assignment during the ensuing meetings. Though the duration of these meetings were short, less than 1-hour, the interaction between team members was crucial to the success of the project. The meetings ensured timely transfer of information between the department representatives, enabling the individual departments to manager their portions of the project and the ability to respond faster as changes arise. This changed the organizations focus to more of a communicative one. At key points within the MPS, the PM deployed certain Lean Six Sigma quality tools. The tools applied assessed the product design, the manufacturing process and equipment. The timely deployment of these quality tools and the information acquired were vital to the successful completion of this project. Early in the design phase, the team conducted a Design Failure Mode Effect Analysis (DFMEA) of the new product. From this analysis, the project team identified potential failure points within product design. The early deployment of the DFMEA provided the necessary time for the project team to design these failures points out of the product without affecting the scheduled release date of the new product. Upon finalizing the product design, the team entered the new items (raw materials and final assemblies) and engineering BOMs into the business system. From this information, along with the demand planning information, the team was able to communicate the demand requirements with the suppliers. By communicating these requirements with the supplier, the team was able to secure all materials needed in time for the product launch. After the completion of the DFMEA, the project team began developing the manufacturing process. Using a process-mapping tool, the project team constructed the manufacturing process then evaluated the process using the Process Failure Mode Effect Analysis (PFMEA) tool. The
  • 3. New ProductIntroduction Case Study (con’t) outcome of the process mapping and PFMEA process, the project team developed the manufacturing process and identified the supporting manufacturing equipment. While developing the manufacturing process, the project team conducted the safety assessment of the manufacturing process and materials. From the safety assessment, the team identified several manufacturing materials were hazardous to the health of the assembler. Since team could not eliminate these materials, the manufacturing team designed special handling equipment into the process to remove the assemblers’ risk of exposure to the hazardous materials. Using SolidWorks® (3D modeling software), the project team designed the layout of the manufacturing cell. From this layout, the project team identified redundancies within the workflow and expedited the process flow using a Spaghetti Diagram. Information obtained from the development of the Spaghetti Diagram, the team optimized the workflow within the manufacturing cell prior to moving in the manufacturing equipment. As the new production equipment arrived, the project team validated the equipment’s performance to the process requirement and conducted the new equipment safety assessment prior to releasing the equipment to the manufacturing group. By evaluating the equipment at the time of arrival, provided the project group the time required to make any modifications to the equipment without effecting the release date of the new product. Prior to releasing the test and measurement equipment, the project team calibrated and conducted a Gage R&R analysis. From the information obtained from the Gage R&R analysis, the project team implemented the Statistical Process Control (SPC) parameters used to monitor performance of the manufacturing process. Conclusion: With the introduction of the New Product Introduction (NPI) process improvements, the project team was able to reduce the introduction time of a new product by over 70% by reducing the cycle time of the process from 39-weeks to 9-weeks. In addition, the team established a process to capture the costs (labor hours and expenditures) associated with a new product development. This new process developed an interactive system between the departments, allowing timely transfer of information between the department representatives, enabled the individual departments to manager their portions of the project and the ability to react faster as changes arise. The team was able to update the project status while getting buy in through all stakeholders by sharing the status on a company drive where all had read access and could monitor project leaving very little time for static on follow up with the management team. An additional benefit, which was not part of the original mission, was the culture shift in the organization. Sometime the cultural shift in an organization, the desire to manage the right way is sometimes obscured by the desire to successfully launch a new product, this helped tear down those walls and unify the team. The process is then used for all of the development projects coming out of engineering substantially reducing lead time and managing cost expectations as well as delivering quality prototypes into the customers hands far earlier than expected.