Skip to content
Menu
Request a Quote
[Part family] machined for this project, shown on a neutral background
Case template

Prototype to Controlled Batch: [Part Family]

[One-sentence project summary, to be supplied with the customer's permission].

This case follows one part from an accepted sample to its first controlled batch, for buyers and engineers who want to see how the accepted revision, the responsibilities and the batch records were kept together.

Project at a Glance

This summary lets a buyer judge quickly whether the project is comparable with their own part. Every row must come from the project record and be cleared for publication by the customer. A value that cannot be published is left out rather than estimated or rounded, and the row says so.

ItemProject record
Part family and function[Part family and function, to be supplied with permission]
Material and supplied condition[Material and condition as stated on the drawing]
Accepted sample revision[Drawing revision accepted at sample stage]
Batch revision and quantity[Revision and quantity of the first controlled batch]
Work performed by the factory[Operations carried out by the factory]
Work performed by others[Operations carried out by the customer or outside processors]
Records issued[Documents supplied with the batch]

Publication

the values in this table are published with the customer's permission. [Permission scope, to be confirmed before publication].

The part and the accepted sample

The Part and Its Original Constraints

This block must show what the part does in its assembly and which constraints shaped how it could be made, in terms a buyer can compare with their own drawing: the interfaces it locates or mates with, the features that were difficult to reach or measure, and what had to stay the same between sample and batch. [Part function and assembly context, to be supplied with permission].

Redacted part drawing view with the constraining features outlined and numbered

A redacted drawing view with the features that constrained the manufacturing route marked

[Original constraints: the features, material or finish requirements that decided the manufacturing route]. The comparison works at feature level, such as an interface and the datum it relates to, rather than at the level of a platform or programme name, which the customer may not wish to publish in any case.

Related: UAV components

Who Was Responsible for What

Responsibility is what a buyer checks first when a sample turns into a batch. This block must separate the work the factory carried out from the work done by the customer or by outside processors, and state who accepted each part of it. Without that split, a successful sample says little about who will control the next batch, or who answers a question about it.

Design and drawing

[Who owned the design and released each revision]

Machining

[Operations carried out by the factory]

Outside operations

[Finishing, treatment or other steps carried out by others]

Acceptance

[Who inspected and who approved the sample and the batch]

Evidence required

the purchase order scope or agreed work statement that shows this split. The block states only what that record supports.

Sample Acceptance and Revision Handover

This block must show what exactly was accepted at sample stage and how that acceptance was carried into the batch: the drawing revision, the features checked, the record of acceptance and any change agreed before the batch. [Sample quantity, revision and acceptance record, to be supplied with permission].

Redacted sample acceptance record showing part number, drawing revision and acceptance status

The redacted record that accepted the sample, with part number and revision visible

[Changes agreed between sample and batch, with the revision that introduced each one, or a statement that none were made]. If the batch was made to a later revision than the sample, the block must say which features changed and how they were checked again. An accepted sample covers only the revision it was made to.

Related: Small-batch production · From an approved prototype to a controlled batch

Evidence required

the sample acceptance record and the revision history between sample and batch, both redacted for publication.

Batch acceptance, records and limits

Batch Manufacturing and Inspection

This block must show how the batch was made and checked against the accepted definition: the operation sequence at summary level, the checks performed during and after machining, how many pieces were inspected for each characteristic and how results were recorded. [Batch manufacturing route and inspection plan, to be supplied with permission].

Machined parts from one batch on an inspection bench with measuring equipment

Parts from the batch at the inspection station, with the agreed checks in progress

[Inspection results, stated as recorded, with the coverage of each check]. Results are reported in the units and scope of the original record. If a characteristic was checked on a sample of the batch, the block says so, and it does not restate a sampled result as a result for every piece.

Related: Quality and inspection

Evidence required

the redacted inspection record for the batch and the drawing revision it refers to.

Delivery and Records Issued

This block must show what left the factory with the batch and how it identified the parts: labels, packing list, reports and any certificates, each tied to part number, revision, quantity and batch. [Documents and identification supplied with the batch, to be supplied with permission].

Packed machined parts from the batch with identification labels showing part number, revision and batch

The packed batch with labels carrying part number, revision and batch

Redacted packing list with part number, revision, quantity and batch reference for the shipment

The redacted packing list issued with the batch

A buyer reading it should be able to see how their own receiving team would match parts to paperwork.

Related: Packaging and delivery · Manufacturing documentation and traceability

Result and Limits of This Case

This block states only what the records support: [Result as recorded at acceptance of the batch, to be supplied with permission]. It adds no improvement percentages, lead-time claims or general statements about capability. If the record shows that the batch was accepted, the block says so and names the record; if issues were found and resolved, it says which, provided the customer agrees to publish them.

[Limits: conditions that would differ for other parts, such as material, size, quantity or revision history]. A buyer should leave this block knowing which parts of the project are comparable with their own and which would need to be reviewed again for a new drawing.

No outcome without a record

if no acceptance record can be published, this block is removed rather than written from memory.

What to Send for a Similar Part

If your own part is moving from an accepted sample to a batch, send the information that lets the review start from the same point as this project. A written description is enough for a first message; drawings and records can follow by the method you agree, once any confidentiality terms are settled.

Accepted revision: the drawing revision the sample was accepted to, and any change since.

Acceptance record: the sample report or your acceptance notes for the critical features.

Batch quantity: the quantity needed now and any planned later batches.

Records needed: the documents your receiving team needs with the batch.

Discuss a Batch Based on an Accepted Sample

Tell us which revision was accepted at sample stage, the batch quantity you need and the records your receiving team expects.

Sales contact photo to be confirmed

Sales contact (pending)

Name, role and photo to be confirmed

Drawings are optional for an initial discussion.

Start with the information you have; file exchange can be arranged afterward.

Name to be confirmed

Sales, company name to be confirmed

  • A short description is enough to start; files can be exchanged once the method is agreed.

Project Inquiry

Fields marked  are required.