Tooling and non-recurring engineering costs should buy defined development work and deliverables, not an unclear promise of a production-ready battery. Before approving an OEM project, separate one-time engineering scope from unit pricing, recurring testing and logistics.
Part 1: Understand the Cost Categories
1.1 Separate tooling from engineering
Tooling may include enclosure molds, assembly fixtures and test fixtures. Engineering may include mechanical design, electronics, firmware, prototypes and validation planning. The quotation should identify what is actually included rather than hiding all work under one NRE line.
1.2 Distinguish project-specific from existing resources
A mature battery platform may support limited customization, while a new enclosure or communication design can require additional development. Ask which elements already exist, which will change and which require new verification.
Large Power project pricing, MOQ and lead time require a project-specific proposal. An example from another program does not establish a standard commercial policy.
Part 2: Define Deliverables and Acceptance
2.1 List the engineering outputs
Agree on drawings, interface documents, sample quantities, firmware configuration, test plans and reports to be delivered. Identify file formats, revision control and approval responsibilities. A prototype that powers the host once is not sufficient evidence of production readiness.
2.2 Define milestone completion
Connect milestones to observable acceptance criteria: dimensional fit, electrical performance, host communication or other agreed outputs. Specify who reviews each milestone and how unresolved deviations are recorded. Payment terms remain subject to the agreed contract.
Part 3: Clarify Ownership and Access
3.1 Address physical tooling
Confirm ownership, storage, identification, maintenance, expected usage and access conditions. Discuss what happens if tooling is modified, damaged, transferred or no longer used. Paying a tooling fee does not automatically settle these questions.
3.2 Address design and firmware rights
Separate physical tool ownership from intellectual-property rights, source-code access and the right to reuse a platform. State whether deliverables include editable files, configuration data or only released production documents. Resolve these matters in the project agreement, not by assumption.
Part 4: Control Changes and Exclusions
4.1 Define revision rounds
Identify included sample iterations, the scope of each review and how customer-requested changes will be quoted. Cell substitutions, connector changes and revised enclosure dimensions may affect more than the visibly changed component.
For smart packs, define the BMS communication and protection scope before treating firmware work as complete.
4.2 Separate testing and market access
List qualification testing, transport evidence, external laboratory fees and documentation work separately. Clarify whether proposed fees cover planning, laboratory testing, report issuance or later updates. Applicable standards and market requirements depend on the actual product.
Part 5: Compare the Total Program Scope
One-time engineering and physical-tool deliverables.
Prototype, pilot and recurring production quantities.
Validation responsibilities and acceptance criteria.
Ownership, maintenance and access provisions.
Included revisions and change-quotation process.
Testing, packaging, shipping and other exclusions.
A lower NRE quotation may cover less work. Compare proposals against the same deliverable matrix and production assumptions before approving development.
FAQ
Does NRE include certification?
Only if the quotation explicitly defines the applicable testing and documentation scope.
Does tooling payment transfer every design right?
No automatic conclusion should be made. Ownership and access depend on the agreed terms.
How can an OEM obtain a scoped proposal?
Submit the requirements, drawings and production plan through the custom battery solution inquiry.
