Technical scope and responsibilities
Freeze the product variants, process flow, station list, automation boundary, buyer-supplied items, data interfaces, and acceptance criteria.
Overseas project planning
Use this page to define the buyer and supplier interfaces behind an overseas battery line project. It covers FAT evidence, packing and transport inputs, site readiness, installation, SAT, training, and the information needed for a project-specific quotation.
Answer first
A useful delivery plan connects the approved equipment scope to the building, utilities, logistics, installation sequence, acceptance evidence, and operator handover. The schedule becomes reliable only after those interfaces have owners and review dates.
Lead time, local compliance documents, travel scope, response time, spare parts, warranty, and site support must be confirmed in the quotation or contract for the specific destination and project.
Each workstream has a release condition. A shipment date by itself does not show whether the site, samples, data interfaces, and acceptance team are ready.
Freeze the product variants, process flow, station list, automation boundary, buyer-supplied items, data interfaces, and acceptance criteria.
Agree on samples, test conditions, pass or fail limits, cycle definitions, data files, punch-list ownership, and the evidence required before packing.
Confirm equipment dimensions and weights, lifting points, packing list, route constraints, consignee details, trade terms, and who supplies customs information.
Close the floor, access, foundations, power, air, exhaust, cooling, network, safety, unloading, storage, and contractor interfaces before arrival.
Repeat the agreed site tests, record open items, verify recipes and data paths, and define the production material and staffing needed for the handover run.
List the operator, maintenance, controls, quality, and safety training deliverables. Record the support channel, response terms, spare-parts scope, and warranty start point in the project agreement.
Use this matrix during the RFQ review. Unresolved inputs should appear as assumptions, not hidden commitments.
| Interface | Buyer input | Supplier output | Release evidence |
|---|---|---|---|
| Product and process | Cell, module and pack drawings; variants; target output; quality gates | Process map, station list, automation boundary, changeover assumptions | Approved technical agreement and revision list |
| Factory and utilities | Dimensioned floor plan, access route, available utilities, local safety contacts | Layout, equipment envelope, utility load list, service clearances | Signed interface list and site-readiness review |
| FAT and SAT | Samples, acceptance limits, witness team, production criteria | Test protocol, result format, punch-list process | Approved test matrix and release record |
| Logistics | Destination, consignee, trade terms, unloading capacity, route limits | Packing list, dimensions, weights, lifting and storage instructions | Approved shipping documents and receiving plan |
| Data and MES | Network rules, protocols, tag list, data owner, security review | Interface definition, data fields, test method, version record | Interface acceptance record |
| Installation and training | Site team, contractors, permits, shifts, training roles and language | Installation sequence, staffing assumption, training scope, handover list | Mobilization and handover plan |
Providing these items early makes the quotation easier to compare and reduces assumptions that later turn into schedule changes.
A destination is only one input. The schedule also depends on line scope, approval cycles, FAT conditions, packing and transport route, customs responsibilities, building readiness, installation sequence, samples, and SAT requirements.
Agree on product variants, samples, test conditions, cycle-time definition, quality limits, data records, witness responsibilities, deviation handling, and the release criteria for packing.
Provide a current floor plan, equipment access route, unloading and lifting plan, floor and foundation conditions, utilities, network and MES interfaces, local safety requirements, storage conditions, and the site team's responsibilities.
These items should be written into the project quotation or contract. The scope can vary by equipment, destination, site readiness, travel conditions, support model, and the buyer's service requirements.
Send the destination, product drawings, target output, line scope, building information, utility conditions, and desired production date. The RFQ should separate confirmed scope from buyer inputs and open assumptions.