The New Product Introduction process for Box Build moves a product through a series of evidence-based decisions: define the scope, establish the product baseline, review manufacturability, plan materials, develop the route, prepare verification, run a pilot, close issues, and authorize production. Each step should have an owner, entry condition, output, and release decision.

The steps below form a framework rather than a fixed calendar. Product risk, maturity, configuration count, supplied materials, test development, and unresolved design work determine how much iteration each stage needs.

Step 1: Define the delivered Box Build

Describe the exact incoming and outgoing states. List what the partner receives, what it sources or coordinates, which operations it performs, which evidence it retains, and what condition defines an accepted deliverable. Include accessories, firmware, labels, and packaging when they belong to the finished state.

Create a responsibility matrix for design authority, material approval, tooling, test development, nonconformance, changes, and production release. Use what Box Build assembly includes to frame the integration boundary and prevent hidden scope from emerging after kickoff.

Step 2: Establish the product baseline

Collect the structured bill of materials, assembly model, drawings, schematics, cable and connection data, approved sources, firmware identifiers, configuration matrix, test requirements, label artwork, and packaging definition. Record the revision and release status of each item.

Name the governing source when documents conflict. Preliminary information may support planned learning, but it should never look like a production release. Assign every missing or unresolved input to an owner and expected decision point.

Step 3: Run the cross-functional design review

Review the product as a connected system. Check mechanical access, fastener sequence, connector mating, cable routing, strain relief, grounding, thermal interfaces, closure, service access, label placement, test access, and pack-out protection.

The DFM framework for Box Build assembly turns these observations into controlled decisions. Log each issue with the affected requirement, proposed action, owner, document impact, and evidence required for closure. Separate design changes from process clarifications.

Step 4: Build the material readiness plan

Map every bill-of-material line to its approved source, sourcing owner, required incoming state, substitution authority, and configuration use. Define how customer-supplied material will be counted, identified, inspected, stored, and handled if it arrives damaged, short, or at the wrong revision.

Do not use an unapproved substitute to preserve an internal target. If availability creates a constraint, make the decision visible to engineering and procurement. The plan should also identify material that can block a learning objective even when the rest of the kit is available.

Step 5: Develop the manufacturing route

Convert design outputs into an ordered route that protects the product and exposes defects before later work hides them. Define incoming control, kitting, subassembly preparation, mechanical integration, electrical connection, configuration, verification, closure, labeling, and packaging as applicable.

Route question Required decision
What must be verified before installation? Incoming acceptance state
Which operations depend on sequence? Controlled work order
What needs a fixture or approved tool? Tooling responsibility and revision
Which features become hidden? In-process inspection point
How are variants separated? Configuration and kit controls
Where do failed units go? Containment and disposition route

The electromechanical assembly capability provides context for the physical operations, but the product documents must define the actual requirements.

Step 6: Release instructions, tooling, and training

Write station instructions that show part identity, orientation, sequence, tool method, product protection, inspection points, and escalation rules. Controlled visuals can clarify the action, but references must remain tied to released engineering data.

Identify fixtures, gauges, adapters, software, and handling aids. Define their owner, revision, approval, verification, maintenance, and storage. Train participants on the released route and record authorization where the project requires it. Training on an obsolete draft cannot support production readiness.

Step 7: Prepare configuration and functional testing

Define the unit under test, hardware revision, firmware, options, fixture, test software, connection method, sequence, expected responses, limits, retained data, safe-stop conditions, and failure route. Separate product validation from routine manufacturing acceptance.

The functional test plan for Box Build explains how to build a coverage matrix and preserve original results. If the test method or fixture still needs development, treat that work as an NPI deliverable with its own approval rather than hiding it inside production execution.

Step 8: Set pilot objectives and entry criteria

Write the questions the pilot must answer. These might concern assembly access, route sequence, fixture fit, instruction clarity, configuration control, test behavior, traceability retrieval, failure handling, or packaging. Choose the build scope according to those questions and product risk.

Before starting, confirm the applicable data set, material status, available tools, approved temporary controls, trained participants, data-capture method, and decision-makers. If an input is missing, decide whether the pilot can still create valid evidence and document the limitation.

Step 9: Execute the pilot and capture evidence

Run the units through the proposed route without relying on undocumented expert memory. Capture the affected unit, operation, document revision, observed issue, immediate containment, and proposed correction while the context is available.

Preserve original test failures, rework, and deviations. A final pass does not erase the path used to reach it. The Box Build traceability and serialization guide shows how unit identity can connect these events for later review.

Step 10: Close issues and verify corrections

Classify every issue as product design, material, process, tooling, instruction, test, configuration, or quality control. Assign the correct authority, update the governing documents, and verify the correction in the operation where the problem appeared.

A changed document is necessary but may not be sufficient. Confirm that the revised design, sequence, fixture, script, or instruction works in practice. Record effective revisions and identify material or units affected by the change.

Step 11: Authorize the intended production state

Hold a release review covering product data, materials, route, tooling, instructions, training, configuration, verification, traceability, packaging, and exception handling. Every remaining item needs either closure or an approved owner and disposition. Certified manufacturing systems can support this control, while the evidence remains product-specific.

After release: moving from the pilot to the first production lots

A pilot proves the route on a small, controlled build; the first production lots prove it still holds when lot size, crew, material receipts, and schedule pressure change. Plan the transition as a controlled ramp with written exit criteria rather than an assumed continuation.

What changes between a pilot and the first production lot

Moving from NPI to mass production for Box Build changes the conditions around the released route. Define the controls before release so production does not have to resolve these differences during execution.

Variable Pilot condition First-lot risk Control to set before release
Lot size and takt Controlled batch with time to investigate Station imbalance or rushed checks at the planned pace Verify station cycle times against takt and define escalation for delays
Operators and training Selected crew with direct support Different operators interpret instructions differently Release station training and confirm operator readiness
Material receipts and lots Selected material with known receipt history Incoming lots vary or arrive out of sequence Define receipt acceptance, lot identity, and shortage handling
Fixtures and test assets Assets checked under pilot conditions Repeated use at production rate exposes instability Verify fixtures and test assets at the intended operating pace
Configuration/firmware selection Known variants selected under close supervision Incorrect image or option assigned to a unit Control configuration selection and retain verification evidence
Documentation revision Pilot documents held as a known set Obsolete instructions remain at a station Release a consistent revision set and remove superseded copies
Packaging and labeling Pack-out reviewed under pilot conditions Label mismatch or packing error during repeated handling Verify label data, unit matching, and released packing instructions

Clarify receipt responsibilities through the turnkey versus consignment material supply guide. Carry the approved pack-out requirements into the labeling, serialization, and packaging plan.

What carries over and what must be re-verified

The pilot-validated route, instructions, and test limits carry over only at the revision that was piloted. Anything changed after the pilot, including a design, source, fixture, script, or label, must be re-verified in the operation it touches. Do not claim the pilot covers a changed item. Keep verification evidence with the released baseline, and use the functional test plan to connect changed test conditions to acceptance evidence.

Run the first lot under enhanced watch with exit criteria

Enhanced watch means temporarily tighter in-process inspection and full record review on the first production lot or lots. Before the lot starts, agree in writing which checks are added, who reviews the evidence, and the explicit condition for returning to the normal inspection plan. Define who can authorize that return and how an unresolved finding keeps enhanced watch in place within the quality and traceability framework.

Track the same metrics from pilot data forward. First-pass yield per test stage is the share of units passing that stage on their initial attempt. Retest rate is the share of tested units requiring another attempt; retain the original result. Rework by cause code groups corrective work by its recorded cause. Cycle time by station is the elapsed processing time at each station, with a consistent rule for recording interruptions. Escapes found at pack-out are defects discovered during final packing that earlier controls should have caught.

Set thresholds per project from the pilot’s own data and the customer’s acceptance requirements; never use generic numbers. Review changes in these measures alongside the affected material lot, operator, and revision before deciding that the ramp can advance.

Freeze and change discipline during the ramp

Separate documentation-only changes, such as correcting a reference without changing an instruction, from changes to form, fit, or function. Review and release documentation corrections so stations retain a consistent baseline. Any form/fit/function or approved-source change after release should go through formal change control, using ISO 9001:2015 clause 8.5.6, “Control of changes” as the quality-system basis. It may require a limited re-pilot of the affected operation. Record the effective revision and the first serial number built to it so affected units can be identified, following the traceability and serialization guide.

Signals that you are not ready to ramp

  • Open design issues without an owner.
  • Unreleased or provisional test limits.
  • Even a single unapproved material or substitute.
  • A fixture not verified at production rate.
  • Traceability retrieval not demonstrated on pilot units.
  • A forecast not defined enough to plan material.

In those cases, keep running controlled low-volume builds (low-volume Box Build) until the gap is closed.

Use high-volume Box Build production for the volume-stage controls that follow the ramp. Review lead time drivers to see how ramp planning affects dates.

For more detail on the full handoff, read what NPI means in manufacturing. Review the NPI and pilot-build capability and organize inputs with the RFQ checklist. When the release baseline is ready, request a quote and ask for an NPI scope review before committing material or production authorization.

Use the stage gates to decide what may advance, then map approved operations onto the end-to-end Box Build process and define the corresponding inspection, change, and record controls in the quality and traceability framework. The checklist is a decision aid; the released project documents remain the governing source.

References & standards