Quick answer
Set a controlled document register before comparing transformer quotations. Name the required language, units, drawing types, submission stages, reviewer, approval authority, revision code and final-record format. Approve the technical drawing against the same specification used for the quotation, then release one identified revision to manufacturing. A translated file or an attractive catalogue page is not a substitute for an approved project document.
Start with the document register
List the documents needed to select, manufacture, install and accept the offered transformer. The exact set depends on the project and contract:
| Document | Decision to record before the quote | Approval evidence |
|---|---|---|
| General arrangement or approval drawing | Which outline, terminals, clearances, lifting points and access dimensions must be shown? | Numbered drawing, revision, comments and approval status |
| Single-line and connection drawings | Which electrical interface and phase or terminal designations control? | Accepted diagram linked to the data sheet |
| Wiring and auxiliary schedule | Which alarms, controls, sensors and external terminals are included? | Terminal list, wiring diagram and responsibility matrix |
| Technical data sheet | Which ratings, taps, cooling, losses and environmental conditions are the quotation basis? | Signed or otherwise controlled revision |
| Test and inspection documents | Which routine, witnessed or special tests and reports are required? | Inspection and test plan with acceptance route |
| Manuals and final records | Which operating language, file format, serial references and handover items are required? | Document transmittal and final-record register |
Treat the register as a commercial boundary: “drawings included” could mean an outline sketch, approval drawing, wiring diagram or final as-built package.
Make language a technical requirement
Write the controlling language into the enquiry, including bilingual needs, units, decimal notation, abbreviations, terminal names and warning text. Apply the rule to drawings, data sheets, test reports, manuals, packing lists and any supplied display. Ask to see the translated terms in the approval copy; a promise to translate later cannot be checked.
Language availability and revision numbering are project and supplier specific. State the controlling language, any bilingual requirement and the revision field in the purchase documents; do not assume a language package or revision scheme before the Jinxing quotation confirms it.
Define drawing stages and approval authority
Use clear stage names such as quotation basis, approval drawing, manufacturing release and final record. Define what terms such as “for information” or “for approval” permit and who may close comments.
| Stage | What the supplier submits | What the buyer decides |
|---|---|---|
| Quotation basis | Preliminary configuration, assumptions and exclusions | Whether the offer is technically comparable |
| Approval drawing | Dimensions, terminals, accessories, interfaces and revision history | Whether the proposed arrangement fits the approved design |
| Manufacturing release | Closed comments and one controlling data set | Whether production may use this revision |
| Final record | Serial-linked drawings, reports, manuals and packing records | Whether the handover package is complete |
Do not let procurement approval authorize manufacturing while technical comments remain open. Assign owners for engineering, document control and commercial exclusions.
Check the drawing against the same baseline
A drawing review should cross-check the quotation, single-line, data sheet, layout, cable route, protection schedule and accessory list. Record each comment, owner, response and closure revision, then identify related documents when a value changes.
Request actual dimensions, weights, terminal layouts and wiring information in the controlled approval package for the quoted configuration. Compare the nameplate, layout drawing and specification before manufacturing release; a catalogue or generic drawing does not define the approval process for Jinxing.
Keep translation and technical approval separate
Separate language review from engineering approval. Route translated text to an owner who understands the project terminology, label reference copies, and identify the controlling version. Maintain one mapping when a translation is revised after engineering approval.
Example: an approved drawing and a different manual
Imagine an EPC team approves a dry-type transformer general arrangement in English. The supplier later sends a bilingual manual with a different terminal abbreviation and a revised enclosure drawing. The equipment may still be workable, but the handover set is no longer self-consistent.
The team should identify which revision controls, check whether the abbreviation changes a connection or only a translation, and request a coordinated document package. If the revised drawing changes a terminal, clearance or accessory, it needs technical review and a quotation or manufacturing update. Filing both versions without a status creates an avoidable acceptance risk.
Distinguish document approval from product acceptance
Approving a drawing confirms that the proposed information and interface are acceptable at that stage. It does not prove that the manufactured transformer matches the drawing or that the required tests have passed. Link the approved document register to the inspection and test plan, serial-specific records, photographs where required and final packing list.
The existing transformer nameplate approval guide focuses on physical identification fields; this article covers the wider language, register and drawing workflow. The transformer technical deviation schedule records departures from a requirement; it should be used alongside, not replaced by, document control. Use the transformer quotation page and project enquiry page to request the document list and approval route with the equipment offer.
RFQ checklist
- Required languages, controlling language, units, abbreviations and translation owner.
- Document register covering drawings, data sheets, wiring, tests, manuals and final records.
- Defined submission stages and what each stage permits.
- Named engineering, document-control and commercial approval authorities.
- Revision code, comment register, response owner and closure evidence.
- Cross-checks between drawing, single-line, data sheet, layout, cable and accessory schedules.
- Serial-linked final records, report language, file format and transmittal requirements.
- Explicit rule that drawing approval and product/test acceptance are separate decisions.
FAQ
Is a supplier catalogue enough for transformer drawing approval?
No. A catalogue can explain a product family, but the project needs an identified drawing and document set for the quoted configuration, interfaces and revision.
Should every translated document be treated as a separate technical design?
Not necessarily. Define which version controls and have a qualified reviewer check that translations preserve technical meaning. Any changed rating or interface still needs engineering review.
Does approval of a general arrangement allow the supplier to start manufacturing?
Only if the contract defines that stage as a manufacturing release and all required technical comments are closed. Otherwise, keep the approval conditional and identify the remaining documents.
Evidence boundary
This draft uses the Jinxing product scope, document-control workflow and project-confirmation requirements. It contains no third-party brand or external website citation; language, drawings, tests and final records remain subject to the actual quotation.