What is NPI? The Definitive Guide to New Product Introduction in Manufacturing.

NPI, new product introduction, or new part introduction as most contract manufacturers call it, is the cross-functional process that takes a product from finished design to repeatable, qualified production. It is where engineering hands off to operations, where prototypes become first articles, where supplier readiness has to line up with internal capacity, and where a missed step costs premium freight, customer penalties, or a program that ships six months late. Every aerospace, defense, electronics, and advanced-manufacturing supplier runs one, sometimes formally with stage gates and AS9102 packages, often informally on Excel and email. The well-run shops treat NPI as its own discipline. This guide covers what NPI is, its phases, who is involved, where it breaks, and why coordination is what separates programs that ship on time from programs that slip.

What is NPI?

NPI is the cross-functional manufacturing process that takes a released product design through tooling, process validation, supplier qualification, and pilot production until it can be produced at full rate, on specification, repeatably.

It starts when engineering releases the design package and ends when manufacturing can produce the part at full rate without further engineering help. In between, it pulls in process engineering, quality, supplier quality, supply chain, production, and the program management function that holds the whole thing together.

In aerospace and defense, NPI is the bridge between system development and serial production: the program that gets the part through First Article Inspection (FAI) per AS9102 and into a stable production stream. In automotive and electronics, it runs from design release through Production Part Approval Process (PPAP) submission and into full-rate production. In medical devices, it carries the design through process validation under FDA 21 CFR Part 820. The acronym is the same and the deliverables differ by industry.

Three properties define every NPI program:

• It is time-bounded. Every program has a start (design release) and an end (qualified, full-rate production). A program that drags past its end date becomes a quality problem in production.
• It is cross-functional. A typical program at a mid-market contract manufacturer involves five to ten people across at least four functions, plus the customer's own program team.
• It is gate-driven. Progress is measured against staged sign-offs. A program that has closed 80% of its tasks but missed two gate reviews is not 80% done.

NPI is sometimes confused with New Product Development (NPD), the design and engineering work that produces the released drawings, and with product launch, the commercial introduction to the market. NPI is the manufacturing introduction: the program that proves a released design can be made.

Across contract manufacturing, NPI takes four common flavors that share the same spine but differ in deliverables: precision machining (CNC, EDM, grinding: first articles, capability studies, machined-part FAI), PCBA / electronics manufacturing services (SMT line balancing, AOI, X-ray inspection, ICT/FCT), plastics injection molding (mold qualification, moldflow analysis, gate-vestige and warpage validation), and sheet-metal fabrication and assembly (welder qualification, weld procedure qualification, NDT such as radiographic and dye-penetrant, assembly first articles). The phases below apply to all four; the quality artifacts and tooling differ.

The 5 phases of the NPI process in manufacturing

The names vary by company and standard, but the structure is consistent. A typical mid-market contract manufacturer moves a program through five phases.

Phase 1: Design transfer and DFM

The released design arrives from the customer or internal engineering. Drawings, GD&T, BOM, source-controlled material list, and any specifications get a structured walk-through. Process engineering runs a Design for Manufacturability (DFM) review and either signs off on the design or returns it with questions. A clean DFM review with all questions resolved closes the phase.

The biggest cause of slips in this phase is DFM questions waiting on a customer engineer who isn't responding. A program that has sat "in design transfer" for six weeks usually has one or two open DFM items that nobody is chasing.

Phase 2: Tooling, fixtures, and gauges

Tooling design, fabrication, and try-out, whether that means CNC fixtures and EDM electrodes (machining), injection molds (plastics), SMT stencils and selective-solder pallets (PCBA), or weld fixtures and assembly jigs (fabrication). Fixture design and try-out. Gauge design, calibration, and Measurement System Analysis (MSA), including a Gauge R&R study. The phase ends when the shop has the physical capability to produce a representative part and the gauges to measure it.

This is the phase most often skipped under schedule pressure. A team that goes to first article without a fully validated gauge R&R study almost always fails the article, because the measurement system can't reliably prove the part is good even when it is.

Phase 3: Process validation and first article

Process FMEA, control plan, and work instructions get drafted. Operator training is planned. Then the first article is run, inspected, and documented. In aerospace, this means an AS9102 First Article Inspection package (Forms 1, 2, and 3) submitted to the customer. The phase closes with a signed-off FAI and a process capability study (Cpk, Ppk) that proves the process is in statistical control.

Phase 4: Supplier qualification and PPAP

Sub-tier suppliers run their own first articles. Supplier capability surveys, source qualification audits, and supplier-side FAIs roll up into a PPAP package, the formal evidence that the part can be produced at the supplier's facility, repeatedly, on spec. Customer PPAP approval, at the level the customer requires (Level 1 through 5), closes the phase.

Phase 5: Pilot production and ramp

A pilot run is scheduled, often as Low-Rate Initial Production (LRIP). Yield, scrap, and rework get tracked against forecast. NCRs get worked, processes get refined, and the program approaches takt. A go/no-go gate review at the end of pilot moves the part into full-rate production. The NPI program closes and the part lives in steady-state production from there.

Phase boundaries are rarely clean. Phases 3 and 4 typically overlap, and Phase 5 can run for months in complex programs. The gate model holds throughout: every phase ends with a sign-off backed by evidence.

NPI vs. NPD vs. Product Launch: three terms people confuse

Three jobs, often run by three teams.

New Product Development (NPD) owns the design. R&D-heavy. Outputs: released drawings, BOM, design intent. Lives largely in PLM. Ends when the design package is released to manufacturing.

NPI owns the manufacturing introduction. Cross-functional. Outputs: qualified production, first article approvals, PPAP, validated process. Lives largely in spreadsheets, email, and PDF, which is the problem this category of software exists to fix. Starts when the design package is released and ends when full-rate production is qualified.

Product launch owns the market introduction. Commercial. Outputs: customer announcements, sales enablement, channel readiness, marketing campaigns. Lives in a CRM and the marketing stack. Often runs in parallel with the back half of NPI.

The three are sequential in classic stage-gate models, but in practice they overlap. Marketing announces a launch date that engineering has to design backward from, and NPI gets compressed when NPD slips. NPI absorbs both the upstream design churn and the downstream commercial pressure, which is part of why it carries the highest coordination tax.

The Roles Involved in NPI

An NPI program at a mid-market industrial supplier typically pulls in these functions:

• Program manager / NPI coordinator. Owns the schedule, runs the gate reviews, owns the customer-facing status. Often the most senior individual contributor on the program. (See: The NPI Coordinator's Survival Guide.)
• Design engineer. Source of design intent. Answers DFM questions. Approves engineering changes. In contract manufacturing, this person frequently sits at the customer, which adds hand-off latency to every interaction.
• Process engineer. Translates design to manufacturing process. Runs DFM review, drafts process FMEA, owns control plan and work instructions.
• Quality engineer. Owns FAI, PPAP, and gate evidence. The function that says "no" when documentation isn't where it needs to be, and the program is better for it.
• Supplier quality engineer. Owns sub-tier supplier readiness: capability surveys, source audits, supplier-side first articles.
• Production lead. Owns capacity, takt, and the floor's ability to run the part once qualified.
• Customer-facing PM (in contract manufacturing). The interface to the customer's own program team. Manages customer notifications, status updates, and escalations.

A supplier with five concurrent NPI programs typically has five to seven of these people working across all of them. None work on a single program full-time and all depend on each other for hand-offs. That is why NPI is coordination-heavy: nobody owns it end-to-end except the program manager, who can't drive every action item across every function alone.

Stage Gates in NPI: AS9102, PPAP, and DFM Reviews

A stage gate is a pause-point where evidence is reviewed before the program moves to the next phase. Industries codify gates differently, but the function is the same: hold the program accountable for readiness it can prove.

AS9102 First Article Inspection is the aerospace standard, maintained by SAE International. Form 1 covers part identification. Form 2 is product accountability, every drawing characteristic accounted for. Form 3 is characteristic accountability, every measurement and inspection result documented. An aerospace NPI program is done when the customer approves the AS9102 FAI.

PPAP (Production Part Approval Process) is the automotive and electronics standard, defined by AIAG. PPAP submissions come in five levels: Level 1 is just the warrant (a one-page certification), Level 5 is a full PPAP package on file at the supplier with all 18 elements. The customer specifies the level required. Different OEMs, even within the same industry, ask for PPAP in different formats, which is one of the unsung sources of NPI rework.

DFM reviews are formally a stage gate in few standards but function as one in practice. A program that hasn't completed DFM with the design team has only received drawings. Skipping DFM in the name of speed is the most common shortcut in NPI, and the most expensive.

APQP (Advanced Product Quality Planning) is the umbrella framework most automotive customers expect. Its five phases map roughly to the NPI phases above, with PPAP as the deliverable that closes Phase 4.

Vertical-specific gate artifacts sit alongside these standards: moldflow analysis and gate-vestige inspection for plastics injection molding; Weld Procedure Qualification (WPQ), welder certification, and Non-Destructive Testing (NDT: radiographic, dye-penetrant, ultrasonic) for sheet-metal fabrication; AOI and X-ray inspection programs, ICT/FCT setup, and SMT line characterization for PCBA. Different deliverables, same gate function: structured evidence that the program is ready to proceed.

Gates matter because under schedule pressure, teams skip them. The gate review is what stands between a program and "we'll fix it in production." A program that holds its gates ships fewer escapes, surprises the customer less, and recovers faster when something slips, because the evidence shows what was approved and when.

Why NPI Slips: the Coordination Tax (in brief)

Most NPI programs slip because the supplier email didn't get logged, the DFM question waited four days, the gate review was held without evidence, or the customer notification went out late. This is the coordination tax, and the same five patterns repeat across every vertical and every concurrent program. The thesis, the math, and the five issues are in a separate piece: How NPI Programs Slip: the Coordination Tax and the 5 Issues We See Most. For any team trying to improve, the first step is measuring it.

How to Measure NPI Performance

Most ops leaders can't answer this in five seconds: what's our NPI cycle time, and what's our gate-on-time rate?

Four metrics matter:

• Gate-on-time percentage. Of the gate reviews scheduled in the last quarter, what percentage closed on or before the scheduled date with all evidence in place? The best industrial suppliers track above 80%. Most mid-market suppliers track at 50 to 60% when they measure it honestly.
• First-article first-pass yield. Of the first articles run, what percentage passed inspection on the first attempt? A direct measure of process validation rigor. World-class is above 90%. Typical is 60 to 70%.
• NPI cycle time. Total elapsed weeks from design package release to PPAP/FAI approval. Every week saved per program brings multi-thousand-dollar revenue forward because full-rate production starts earlier, and that compounds across programs.
• Coordination hours per program. Hours spent on status reporting, follow-up, meeting prep, and document chasing per program per week. Most teams have never measured this, and once they do it turns out to be the single biggest controllable cost in NPI.

A team that can't answer these four numbers is running NPI on tribal knowledge. A team that can answer them, and can show the trend over the last six programs, is set up to improve.

What Modern NPI Software Is Supposed to Do

The traditional NPI stack is Excel or Smartsheet for the program plan, Outlook for comms, the ERP for parts and orders, the PLM for drawings, customer portals for evidence, and a SharePoint or shared drive for working documents. Six to eight tools that don't know about each other and need manual hand-off to stay in sync.

Modern NPI software replaces the spreadsheet plus the manual coordination tax with one system that:

• Models the NPI program as a first-class object with its own structure
• Owns the stage-gate model natively: AS9102, PPAP, DFM, APQP, and customer-specific variants
• Maintains a manufacturing ontology: part hierarchies, work packages, BOM linkage, supplier relationships
• Integrates with ERP, PLM, and MES so the systems of record stay in place (see: Why your ERP can't manage NPI)
• Surfaces portfolio-level visibility across every concurrent program in one view
• Supports ITAR / CUI requirements for aerospace and defense

The next step, what we mean by AI-native NPI software, closes the loop the rest of the way: agents that read inbound supplier and customer email, parse uploaded PDFs and spreadsheets, propose program-state updates for human confirmation, and learn from every confirmation. This is the architecture BlackOrbit is built around.