When we talk about PLM we usually talk about Concept to Manufacturing or even Concept to Service / Retire business process. so how do NPI fits in? is it part of PLM implementation.
What is NPI?
NPI – New Product Introduction or NPD – New Product Development or even NPDI – New Product Development & Introduction as defined in Wikipedia:
The complete process of bringing a new product or service to market. There are two parallel paths involved in the NPD process: one involves the idea generation, product design, and detail engineering; the other involves market research and marketing analysis. Companies typically see new product development as the first stage in generating and commercializing new products within the overall strategic process of product life cycle management used to maintain or grow their market share.
So what is the difference between PLM process and NPI process? Is NPI part of PLM?
NPI deliver methodology of how to control the PLM process, from Concept to Manufacturing. Not from the individual item view, but from the high level project view.
NPI is a Phase-Gate approach: for each PLM phase I have a GATE, in order to pass a GATE I need to meet several predecessors.
![]()
Usually companies will create a procedure and a check list of the predecessors needs to be met in order to pass each gate, then a manual control process is been implemented to manually signoff each gate checklist form.
As we believe your PLM system should offer you a simple way to manage complex processes and enabling you to grow with your PLM implementation based on your maturity and schedule, we believe your PLM system should offer you 2 solution levels to meet NPI:
- The basic solution aim to replace the manual procedure with an electronic one:
A project plan has a GATE control business process, in order to approve a GATE you need to complete checklist of tasks (replacing the manual GATE checklists)
NPI Phase-Gate Workflow within ENOVIA SmarTeam demo:
- The more advanced approach will be to manage the complete NPI process with all tasks, predecessors, successors, dependences and due-dates.
This will be managed within a NPI program management approach. like in every complex process implementation, end-users acceptance is critical. This is why we believe each user should work from within his native user environment. The project manager should control the NPI program from within MS project and the team members (the engineers) need to work from within the PLM system. This enables full control of the user tasks, deliverables and attachments for each task. this will also enables connecting item release processes and ECOs into the NPI program tasks
NPI program management within ENOVIA SmarTeam demo (part 1):
NPI program management within ENOVIA SmarTeam demo (part 2):
No related posts.
You can leave a response, or trackback from your own site.
Filed Under :
Dec.1,2008


Tags :