Get in touch with Toplit Transformer Co., Ltd Company
How we use your enquiry information: Privacy Policy.
Procurement evidence guide · Updated October 2026
A buyer-side method of tracking project inputs through design review, applicable test evidence, configuration release, shipment, receipt and lifecycle handover.
Choosing a power transformer manufacturer isn’t a bid process based on evaluating the number of certificates presented by the bidder. A power transformer manufacturer is the supplier whose design, quality assurance, test, delivery, and handover evidence is being audited in this guide. The key question is whether the supplier can connect your approved inputs to a controlled design, show which evidence applies to that design, prove the required tests for the target unit, and maintain one configuration throughout shipment and site acceptance.
Toplit already has a commercial power transformer manufacturer solution page. That page covers product scope, project configuration, commercial discussion and the intent to respond to an RFQ. This page covers a different search. How does a utility, EPC or consultant audit evidence prior to commercial transfer? Maintaining two separate pages allows each page to remain useful without competing to serve the same function. For transformer fundamentals such as types, ratings, losses, operation, and maintenance, use the power transformer guide instead.
Direct answer: begin with one project-and-unit identity, then ask whether each claim is supported at the right level. Confirm the quality-system scope, connect purchaser inputs to released design records, test the applicability of representative evidence, inspect exact-unit results, reconcile changes, and follow the required evidence path through shipment or site assembly.
“the design review process; and the assessment of the capability of a transformer manufacturer.” CIGRE Technical Brochure 529 public summary
CIGRE identifies specification preparation, design review, and manufacturer-capability assessment as separate procurement steps. The main audit rule is that evidence from one layer cannot silently stand in for evidence from another. A valid quality certificate can coexist with an incomplete project design review and doesn’t establish applicability to the proposed unit. A type-test report can be relevant to a design but may still require an applicability link to the proposed unit. Treat a signed FAT certificate as weak if its results, uncertainties, deviations or configuration identity are missing.
Direct answer: Evidence from one layer cannot serve as evidence for another. For example, a type or design report may represent a design family, while routine and agreed FAT records address the target unit. Shipping, receipt, and site records address delivered condition. None substitutes the others.
The edition check matters. ISO now lists ISO 9001:2026 as the current quality-management-system edition, published in September 2026. A supplier may be in an authorized transition period, so the audit should record the certificate’s edition, legal entity, manufacturing site, scope, certification body, validity, and transition status. The audit should not turn away a certificate just because it changed, and it should not accept a current certificate as evidence to accept an exact unit.
| Evidence layer | What it can support | What it cannot prove alone |
|---|---|---|
| QMS certificate | Audited management-system scope for the named organization and site | That the proposed design is suitable or the shipped unit passed its required tests |
| Representative type/design evidence | A defined design’s performance when applicability is established | That every field or result belongs to the target serial number |
| Exact-unit routine/FAT record | Measured results and disposition for the identified unit under the stated procedure and conditions | Every design duty, transport condition, or installed-site acceptance question |
| Shipment, receipt, and SAT file | Release identity, delivered condition, site work, and agreed final checks | Missing design applicability or an unresolved factory nonconformance |
The matrix prevents two errors. One is accepting a brand-level certificate as evidence of a transformer. The other is refusing evidence simply because its serial number is different. The audit should consider what the evidence was designed to prove, whether its scope aligns with the claim, and what links it to the target unit.
Direct answer: A controlled design starts with a purchaser input register. Each voltage, duty, site condition, interface, standard, test requirement, and open assumption should result in a reviewed engineering decision, released record, and named verification method.
The register should identify the project, purchase order, unit count, transformer duty, system voltages and frequency, connection and grounding basis, fault duties, service conditions, transport limits, interfaces, monitoring, the applicable power-transformer standard and edition, required documents, and test path. There are many examples of entries that are appropriate for project controls for a renewable energy project. On a renewable energy or power grid project, for example, entries such as 33 kV, 50 Hz, a 40°C ambient, or a ±2% tolerance are useful only when their source, units, and governing technical specifications are also controlled. Record what’s supplied by the buyer, what’s proposed by the manufacturer, what’s calculated, and what’s open. Verbal agreements aren’t controlled records.
| Input field | Buyer register | Released drawing | Test plan |
|---|---|---|---|
| Frequency example | 50 Hz | 50 Hz | 50 Hz |
| Maximum ambient example | 40°C | 40°C | 40°C |
| Minimum ambient example | −25°C | −25°C | −25°C |
| Altitude example | 1,000 m | 1,000 m | 1,000 m |
| Transport-width example | 3,200 mm | 3,200 mm | 3,200 mm |
| Auxiliary-supply example | 110 V | 110 V | 110 V |
| Alarm-delay example | 10 s | 10 s | 10 s |
The examples given above are generic. The audit point is transcription control: if one controlled record says 50 Hz and another says 60 Hz, or one carries 40°C while another carries 45°C, the discrepancy needs a documented technical disposition before release.
Then follow each input forward. A voltage and grounding basis should appear consistently in the data sheet, connection diagram, nameplate, protection inputs, and test plan. Transport limitations should cover the general arrangement, shipping configuration, impact-monitoring plan, receipt inspection, and reassembly instructions. A change after a design review should identify all downstream drawings, calculations, procedures and test records that must also be changed or checked.
An applicability bridge isn’t bureaucracy for its own sake. It explains why representative short-circuit, temperature-rise, dielectric, sound, or other design evidence can support the proposed transformer. It also addresses differences that require new analysis or testing. The outcome can be to accept, accept with defined limitations, request more evidence, or reject the mapping. “Same series” isn’t a technical conclusion.
A FAT file should identify the unit, the applicable procedure and revision, test setup, instruments, calibration status, measurement conditions, raw data, acceptance criteria, uncertainty or decision rule (if applicable), deviations, retests, disposition, witnesses, and approval. At the transformer factory, quality control turns the approved inspection and test plan into traceable observations, measured results, deviations, and authorized dispositions.
To begin, separate evidence for routine, type/design, special, inspection, FAT, and SAT tests. The labels describe the applicability. A routine test, in the IEC vocabulary, is a conformity test made on each individual item during or after manufacture. A type test is a conformity test made on one or more items representative of the production. A special test may be required only by agreement. FAT is a project event that may incorporate reviews and inspections, and witnessed tests; it doesn’t turn every attached report into exact unit evidence.
The factory acceptance test index should allow a reviewer to move from the purchase requirement to the approved inspection and test plan to the procedure and instrument list to raw sheets to result calculation to deviation record to authorized disposition. A retest record should retain the failed or questioned result, its cause review, corrective action, retest basis, and closure. Replacing a previously documented questioned or failed result with a clean, positive result eliminates the audit trail.
Calibration is a necessary activity, but it isn’t the end of metrology. NIST’s traceability policy states that traceability to a national standards institute doesn’t mean an instrument is fit for its intended purpose, and that calibrating an instrument doesn’t, by itself, establish the traceability of a measurement result. Ask yourself, is measurement uncertainty accounted for by rounding? Did the instrument/device meet its method capability? Was the environmental condition within specification? Was the agreed decision rule complied with?
CIGRE’s FAT/SAT partial-discharge guidance gives a useful bounded example: calibration, sensor and recorder setup, noise, sensitivity, and reproducibility affect whether factory and site measurements can be compared. This doesn’t lead to a single universal PD limit. This is why a “pass” cell without evidence of setup and method may be considered too thin.
The tested, as-built, nameplated, packed, released, received, and finally handed-over states should resolve to one controlled transformer configuration. The serial number is a primary key field, but revision and applicability are equally important.
Establish a configuration baseline at the approved-for-manufacture state. It should contain the data sheet, principal drawings, bill or list of controlled materials (where contractually required), accessories and wiring, ITP, test procedures, software and settings (where applicable) and deviation register. When a change is approved, record the reason, who authorized it, which records it affects, and whether earlier analysis or tests remain applicable.
Upon release for shipment, compare the configuration baseline with the as-built file, nameplate, test index, open punch items, packing list, loose accessories, preservation and shipping configuration. A correct nameplate doesn’t close an unresolved winding or drawing change. A complete packing list doesn’t prove that the tested state matches the released design. Configuration control means reconciling these records, not merely having each record present.
A public-owner specification like the City of Danville transformer procurement file is useful because it illustrates actual controls on drawings, changes, witnessing, shipment, transport condition, field acceptance, and final records. Its project terms don’t become generally accepted terms. Adjust the control questions, not the contract’s language or duties.
Direct answer: Use one card to illustrate which identity connects each record, and which evidence uses a representative-design mapping. The card reveals gaps quicker than a folder inventory, because it asks how the records are related to each other.
| Record | Join key | Audit question |
|---|---|---|
| Purchase data and released design | Project, unit tag, drawing revision | Do approved inputs resolve to this released configuration? |
| Representative design/type report | Applicability matrix, design identity | Are differences in drawing, material, process, factory, and duty addressed? |
| Routine and FAT records | Serial number, procedure revision, date | Do raw results, criteria, deviations, and approvals belong together? |
| Nameplate and as-built drawings | Serial number, final revision | Does the marked unit match the tested and released state? |
| Packing and shipment release | Serial number, package ID, release note | Are accessories, preservation, monitors, and open items controlled? |
| Receipt, assembly, SAT, and turnover | Serial number, site tag, final dossier index | Is delivered condition reconciled with the valid project test path? |
The card is a buyer’s tool, not an IEC or CIGRE card; a public-owner transformer specification illustrates the project-specific drawing, shipment-release, and final-record controls that such a card can reconcile. Change it to reflect the contract. Its main discipline is the identity and applicability split: a serial number exactly joins unit records, and a technical mapping explains why representative evidence is applied.
Direct answer: Audit the actual path declared. A conventionally factory-assembled transformer usually moves from factory release to transport, receipt inspection, installation, SAT, and energization authorization. A legitimate site-assembled transformer may complete whole-unit testing at site. Audit the path declared, rather than forcing every case to follow a prescribed path.
For a traditional shipment, factory release verifies only the agreed factory boundary. Transport can cause impact, displacement, exposure to moisture, loss of pressure, accessory damage, and/or preservation concerns. Receipt must compare the units and packages against the release file, shipping monitors, preservation instructions, visible conditions, accessory list, and storage requirements. Installation and SAT then address the agreed site boundary before energization.
The public summary of the 2022 CIGRE Technical Brochure 857 on site assembly and testing documented another legitimate route: some large transformers received full testing only after site assembly. This is a project-path example; not all projects follow it. In this case, lack of whole-unit factory testing doesn’t automatically constitute a defect when the declared project requirements allow site testing. The audit should identify component and process evidence, transport and preservation controls, on-site assembly procedures, drying or treatment records where applicable, final test procedures, acceptance criteria, and authorized release. The same public summary reports site-test examples up to 800 kV, heat-run power supplies around 2 MW, and mobile impulse systems up to 1800 kV BIL; these are capability examples, not universal acceptance limits.
The transfer lesson is conditional. For factory-assembled equipment, receipt is a second piece of evidence after FAT. For site-assembled equipment, receipt and assembly are inputs to the final whole-unit test. In both cases, the declared path must be stated before the buyer judges a missing record.
Direct answer: Use the checks below as pass/no-pass questions, not a weighted manufacturer ranking. A “no” means clarify or hold until the project authority decides whether the gap is curable, acceptable with a stated limitation, or disqualifying.
| Check category | Pass question | Hold trigger |
|---|---|---|
| 1 | Does the QMS certificate match the legal entity, manufacturing site, scope, edition, body, and transition status? | Identity, site, scope, validity, or edition status is unresolved. |
| 2 | Are project inputs, standards, units, interfaces, and open assumptions in one controlled register? | Design is proceeding against verbal or conflicting inputs. |
| 3 | Does design review close or assign every material technical query? | An open item can change design, test, interface, or safety duty. |
| 4 | Is representative design evidence mapped to the target design and factory? | “Same series” is asserted without an applicability assessment. |
| 5 | Do exact-unit records consistently identify the serial number, unit tag, procedure, revision, and date? | Unit identity or record lineage cannot be reconciled. |
| 6 | Was the ITP/FAT or site-test plan approved before the relevant work? | Witness, hold, procedure, criteria, or retest rules were undefined. |
| 7 | Are raw measured results, conditions, calculations, criteria, signatures, and disposition retained? | Only a pass certificate or transcribed summary is available. |
| 8 | Are calibration, traceability, uncertainty, method capability, and decision rule fit for the acceptance question? | A calibration certificate is used as the sole measurement-quality argument. |
| 9 | Are nonconformances, deviations, repairs, retests, and concessions visible and authorized? | An earlier result disappeared or closure authority is unclear. |
| 10 | Do tested, as-built, nameplated, packed, and released states resolve to one revision baseline? | A change has no downstream drawing, analysis, or retest disposition. |
| 11 | Does the declared assembly/test path control shipment, monitors, preservation, receipt, storage, and site work? | The reviewer assumes a standard sequence that the project does not use. |
| 12 | Is the final dossier complete for as-builts, tests, manuals, spares, settings, SAT, and energization authorization? | Operations inherits an unresolved identity, test, safety, or support boundary. |
The checklist is evidence-led. It doesn’t allot points for factory age, annual production volume, brochure detail, export numbers, customer logos, or the number of certificates shown. These may be relevant to a commercial discussion, but they don’t answer the technical questions above. For the separate task of comparing named companies, use the power transformer manufacturers roundup.
Direct answer: Clarify when a gap is bounded and answerable, hold when the gap could change design applicability or acceptance, and hand off commercially when the required evidence path is defined and material technical barriers are closed or accepted.
| State | Use it when | Next action |
|---|---|---|
| Clarify | The missing item has a named owner, defined scope, and no current conflict with a released decision. | Issue a technical query with due date and required evidence. |
| Hold | Applicability, unit identity, measurement fitness, deviation closure, configuration, or test path is unresolved. | Stop the affected approval, release, shipment, or energization decision. |
| Commercial handoff | The technical scope and evidence route are defined, with residual limitations authorized and visible. | Move configuration, delivery, commercial, and RFQ questions to the solution Page. |
Price and lead time won’t resolve an unaddressed identity or test-evidence gap. When the evidence boundary is clear, use the commercial manufacturer page to discuss the required transformers and quotation. For first-party company identity and manufacturing context, see Jiangsu Toplit Electric Co., Ltd.’s About Us page. Company history is company evidence; project suitability requires the project file.
Discuss a project evidence package
Follow the evidence chain from approved project inputs to design review, applicable representative evidence, exact-unit records, configuration release, and the declared factory or site test path. Check the legal entity and factory, but don’t stop at company credentials. Assign owners to open queries, preserve failed results and deviations, and reconcile the final unit with shipment, receipt, SAT, and turnover records. The audit should end in a clear state: clarify, hold, or commercial handoff, not an unsupported supplier score.
Ask which certificates the contract, market, product, and manufacturing site actually require, then verify legal entity, site, scope, edition, certification body, validity, and transition status. ISO 9001:2026 is now the current QMS edition, but organizations may be transitioning from the 2015 edition under certification-body rules. A valid management-system certificate supports the supplier’s process controls; it does not replace design review, applicable type evidence, exact-unit routine records, or project acceptance.
It should identify the project and unit, procedure and revision, test setup, instruments, calibration status, conditions, raw measurements, calculations, criteria, uncertainty or decision rule where relevant, witnesses, deviations, retests, and authorized disposition. The report index should connect these records to the approved ITP and released design. A one-page pass certificate may be a useful summary, but it isn’t enough when the decision depends on missing raw results, unclear applicability, or an unclosed nonconformance.
Yes, because type or design evidence may come from a representative transformer rather than the target unit. The buyer still needs an applicability bridge that compares design, drawings, materials, manufacturing process, factory, rating, and declared differences. A different serial number isn’t automatic rejection. A matching number also doesn’t prove that every attached design report applies. Exact-unit routine evidence and representative design evidence should remain separate in the dossier, with their relationship explicitly approved.
Only when the contract defines FAT as the relevant release boundary and all required identity, applicability, measured-result, metrology, deviation, configuration, and approval records are closed. Conventional projects still need controlled packing, preservation, transport, receipt, installation, SAT, and turnover evidence. A factory pass can’t prove delivered condition. It also can’t erase an open change or concession. Shipment release should therefore name the accepted baseline, open items, required site actions, and the authority that approved them.
Follow the declared site-assembly path: check component evidence, transport, assembly, final testing, deviations, and authorized release at the site boundary.
Toplit publishes transformer field guides from project routing, factory loss-data discipline, and specification review experience. We help engineering and procurement teams compare transformer types, voltage classes, installation constraints, and quotation evidence before they commit to a build.