What NPI engineering involves

Startups and product teams at any stage. Some have no hardware engineers yet. Some have one generalist who needs a second pair of hands or a review. Others have a team and a gap, such as FPGA, RF and antenna, power electronics and battery/BMS, motor control, embedded Linux or the certification path.

Software and app companies adding their first device fit here too. Our engineers take the roles that are missing on that project: the whole design, one discipline, or one specialty. The NPI work itself stays the same. Only the starting stage changes.

Whatever exists today. A requirement document, a sketch, a schematic, a layout, a BOM, enclosure CAD or a working demo build are all valid starting points. Add the target volume, the markets you will sell in and the date that cannot move. Those three decide which stage we start at and what each build must prove.

A partial file set is normal. Our engineers read it, tell you which stage your project is really in, and say what the next stage gate needs. That answer comes in the free engineering review on a portal order, or in a scoping call when you talk to an engineer.

A prototype is built to answer questions about the product, and it may be built any way that answers them. A pilot build is made the way production will make it, so the process is under test as much as the product. Mix them up and you pay pilot prices for prototype answers, or learn nothing about the process.

The portal records this as a declared project phase: concept, prototype, pilot or production. In stage terms, the portal's pilot phase is the PVT build. Everyone then knows which kind of build is being paid for.

Concept turns a requirement into something specific enough to price: function, success criteria, envelope, motion and load, duty cycle and environment. Prototype answers the product questions. Pilot answers the process questions. Production is where the design stops changing and the controls take over.

On the layout, two: placement approval and routing approval. Both are declared milestones on a PCB layout order. On the build, one: production-file confirmation, which holds fabrication until you approve the file that will run. Then each stage gate needs your yes, and the golden sample needs your signature.

Placement is where mechanical fit, heat and manufacturability are decided. If you review it only after routing, you review it after the expensive work is done. That is why placement approval sits before routing on the order.

Production-file confirmation is a declared toggle on board and stencil orders. When you request it, fabrication waits for your approval of the exact file. Between these three approvals, the points where a mistake becomes costly are the points where someone has to say yes.

The alternates policy, the inspection level, the test definition and the traceability requirement. Each is a declared field on its order route, and each costs less to settle now than to add later. A production run without a defined pass condition for its functional test makes units nobody can accept or reject.

The design should be finished too. Production is where change becomes expensive: new programs, new fixtures, new first articles. The prototype and pilot stages exist so that the changes happen there.

Two pieces of tooling follow a fixed order. Production molds are cut after DVT closes the design. Production test fixtures are built before PVT, so the PVT run tests the fixtures as well as the product. Tooling you pay for, such as molds, fixtures and test stations, belongs to you, and you may move it to another factory.