Published by Jinfan
Published
What to bring to the review
- One dated requirement sheet and design revision
- Sample quantity, order quantity and forecast kept separate
- Required test outputs, interfaces and responsible teams
- Dated quotations with currency, validity and exclusions
1. Fix the comparison baseline
Use the same requirement revision for each supplier. Identify the proposed cell, pack configuration, BMS functions, connector, enclosure and charger boundary. If a supplier proposes an alternative, keep it as a separate option until the engineering owner accepts its implications. Matching voltage and capacity labels alone does not establish an equivalent design.
2. Keep a scope-deviation record
For each disputed line, record: required output; quoted output; included, excluded or unclear status; supporting quotation clause; person responsible for clarification; and the agreed resolution. Keep the original quotation reference when a supplier revises an answer. The following lines make the record practical:
- Samples: quantity, exact configuration and the evidence delivered with them.
- Engineering and fixtures: named deliverables, ownership, reuse rights and whether fees recur.
- Evaluation: test method, pack and host revisions, pass criteria, reporting and who pays for agreed repeat work.
- Delivery: packaging, destination and charges already included in another line; do not count them twice.
- Changes: proposed substitutions, approval owner and the evidence to revisit before accepting a revision.
3. Calculate a comparable subtotal, then resolve unknowns
For a defined order, use subtotal = quantity × unit price + confirmed additional charges not already included. This is a scoped comparison, not a complete lifetime-cost estimate. NIST treats total cost of ownership as broader than purchase price. Keep missing costs visible rather than assigning a guessed allowance or silently assuming zero.
Illustrative arithmetic only, not Jinfan pricing or a minimum order: 100 packs, all amounts in USD. Quote A: 100 × 60 + 900 + 300 = 7,200. Quote B: 100 × 56 + 1,100 + 300 = 7,000, but a required fixture is excluded and unpriced. B cannot yet be declared cheaper for the required scope.
If B later confirms USD 500 for that fixture, and all other required scope is genuinely equal, its comparable subtotal becomes USD 7,500. Record that confirmation; do not treat the example's numbers as market benchmarks. Recalculate for a different order quantity rather than spreading one-time fees over an uncommitted forecast.
NIST MEP: supply chain management and total cost of ownership
4. Check the boundary of any cost benchmark
DOE describes BatPaC as a model for mature, high-volume battery manufacturing. A model result is not a supplier offer for your development-stage pack. Before using a cost per kWh, check the year, chemistry, production scale, cost boundary and included engineering work. If those conditions differ, keep the number as context rather than a target price.
US Department of Energy: battery development, system analysis and testing
5. Close the engineering and purchasing decision together
The OEM defines host requirements and accepts deviations; the supplier identifies its deliverables and exclusions; partner responsibilities must be explicit. Jinfan has its own PACK production line and works with partners on BMS/protection boards and charging management. Confirm project-specific outputs and acceptance responsibilities in the quotation before committing to samples or production.