# New Part Introduction Request Form Template

> Source: https://netray.co/tools/new-part-introduction-npi-request-form-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A request form that gives engineering and master data teams everything needed to create a new part in the ERP correctly the first time.

## Category

engineering-plm

## Industry

Discrete Manufacturing

## Audience

- Design engineer
- Engineering manager
- ERP master data owner

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company name

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Request date

**Key:** request_date

**Type:** date

**Default:** 2026-10-20

#### Requester

**Key:** requester

**Type:** text

**Default:** S. Alvarez, Design Engineer

#### Project or program

**Key:** project

**Type:** text

**Default:** Gearbox Gen 3

#### Proposed part number

**Key:** part_no

**Type:** text

**Default:** GB3-2204-A

#### Description

**Key:** description

**Type:** text

**Default:** Housing, gearbox, machined, aluminium 6061-T6

#### Make or buy

**Key:** make_buy

**Type:** select

**Options:**

- Make
- Buy
- Make and buy
- Phantom

**Default:** Make

#### Unit of measure

**Key:** uom

**Type:** select

**Options:**

- EA
- KG
- M
- L
- SET

**Default:** EA

#### Material and specification

**Key:** material

**Type:** text

**Default:** Aluminium 6061-T6, AMS 4027

#### Initial drawing revision

**Key:** revision

**Type:** text

**Default:** A

#### Proposed suppliers or work centre

**Key:** source

**Type:** text

**Default:** CNC cell 3, outside anodize by approved vendor

#### Date needed in ERP

**Key:** need_date

**Type:** date

**Default:** 2026-11-05

#### Special requirements

**Key:** notes_free

**Type:** textarea

**Default:** First article inspection required. Lot traceability required. Serialized after final assembly.

**Blocks:**

#### {{company}} New Part Introduction Request

**Body:** Request date: {{request_date}}
Requested by: {{requester}}
Project: {{project}}
Needed in ERP by: {{need_date}}

#### Part Identification

**Body:** Part number: {{part_no}}
Description: {{description}}
Initial revision: {{revision}}
Material and specification: {{material}}

#### Planning Data

**Body:** Make or buy: {{make_buy}}
Unit of measure: {{uom}}
Source: {{source}}

Special requirements: {{notes_free}}

#### Data Required Before Release

**Table:**

**Columns:**

- Item
- Needed
- Provided
- Comment

**Rows:**

**0:** Released drawing or model

**1:** Yes

**0:** Parent assembly / where used

**1:** Yes

**0:** BOM lines

**1:** If assembly

**0:** Routing and work centres

**1:** If made

**0:** Approved supplier / quote

**1:** If bought

**0:** Inspection plan or FAI

**1:** If required

**0:** Lot or serial control

**1:** Yes

**0:** Cost estimate

**1:** Yes

#### Approvals

**Signatures:**

- Requester
- Engineering manager
- Master data owner
- Quality (if inspection plan needed)

**Notes:** Map each field to your own item master screen. Do not create the part in the ERP until the drawing is released and the part number has been checked against your numbering policy for duplicates. This is a starting form, adapt it to your quality system.

## Content

**Intro:** Bad item masters start with a vague request. This form collects the identification, planning and supporting data a master data team needs to create a part, BOM and routing correctly, so the first work order does not fail on missing data.

**Sections:**

#### How to use the form

**Body:** The design engineer fills in the identification and planning fields, attaches the drawing and parent assembly, and sends the exported PDF to the master data owner. The checklist table makes missing items visible before the request is queued. Treat any row marked Needed but not Provided as a stop.

**Bullets:**

- Check the proposed number for duplicates and similar existing parts first.
- State make or buy clearly, since it decides whether a routing or a supplier record is needed.
- Give the unit of measure once and keep it consistent across BOM, purchasing and inventory.
- Flag lot, serial and inspection requirements here, not after receipt.

#### Why these fields

**Body:** They map directly to the usual item master decisions: item type, planning method, source, unit of measure, revision control, lot or serial tracking and costing. Whether you run SAP material master views, Epicor Part Maintenance, Infor SyteLine items or NetSuite item records, the same facts have to be known before the record is saved.

#### Typical flow after approval

**Body:** Master data creates the item and sets planning parameters, engineering loads the BOM and routing, purchasing adds the supplier source, and quality attaches the inspection plan. Release the part to production only after each of these has been signed. A short cycle is possible when the form is complete.

#### Common mistakes

**Body:** Requests without a unit of measure, material callouts that do not match the drawing, and missing serial control are the typical rework triggers. Another is requesting a new number when an existing part with the same form, fit and function could be reused. Ask whether a standard part already exists before approving.

**Cta:** If duplicate checks and item creation are slow in your ERP, we can help build a read-only duplicate finder over your item master.

**Faq:**

#### Who should approve a new part request?

**Answer:** Usually the engineering manager for technical content and the master data owner for numbering and completeness, with quality added when inspection or traceability rules apply. Keep the approver list short so requests do not stall.

#### Should the part number be assigned before or after approval?

**Answer:** Follow your numbering policy. Many companies assign a number after approval to avoid gaps and duplicates. If engineering needs a number earlier for drawings, reserve it and mark it as pending in the ERP.

#### What if the part is only a purchased catalogue item?

**Answer:** Still use the form but keep it short: description, manufacturer part number, supplier, unit of measure and cost. Skip the routing and inspection rows by writing not applicable in the comment column.

#### Can this feed an ERP import file?

**Answer:** The fields line up with typical item import columns, so you can copy values into your ERP data migration template. Always test in a non-production company first.

## Search terms

new part request form, new item creation form template, NPI part request template, item master request form, new part introduction form, part creation request ERP, new part number request form excel

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json