English
Views: 0 Author: Site Editor Publish Time: 2026-10-12 Origin: Site
A supplier sends a test report marked “passed.” The transformer is ready for dispatch, and the shipping date is approaching.
Before approving release, one question matters: does this report demonstrate that the ordered equipment meets the agreed requirements?
Dry-type transformer test reports need more than a stamp. Buyers should check equipment identity, test scope, measurement conditions, results, and unresolved items.
This guide explains how to review the document package before shipment. It is intended for engineers, procurement teams, and inspectors—not as an instruction manual for performing electrical tests.
Match unit-specific reports to the transformer serial number and approved specification.
Separate routine results from design-level evidence and additional contractual tests.
Compare measured values only under compatible conditions.
Agree on witness requirements and document deliverables before testing begins.
Close outstanding technical items before issuing the appropriate shipment release.
A report cannot resolve requirements that were never clearly agreed.
Start with the purchase order, approved technical specification, drawings, and inspection plan. Together, these documents should define what the supplier must demonstrate.
Confirm the applicable standard and edition. Also identify any project-specific requirements that supplement it.
Do not assume every dry-type transformer follows the same testing framework. Voltage class, construction, application, and contractual requirements can change the scope.
When comparing dry-type transformer options, discuss the documentation package alongside the electrical configuration.
If requirements remain incomplete, address them while preparing a transformer specification, rather than waiting until dispatch.
For each acceptance requirement, identify the document that will demonstrate compliance.
For example:
Voltage ratio: the relevant electrical test record.
Terminal arrangement: the approved drawing and inspection record.
Temperature-monitoring functions: the agreed accessory verification.
Special acoustic requirements: the applicable sound-test evidence.
This approach makes missing evidence easier to identify without turning the review into a collection of unrelated certificates.
Similar-looking transformers can have different electrical configurations.
Begin with traceability before reviewing individual results.
For unit-specific reports, check:
Manufacturer and equipment identification.
Serial number and purchase-order reference.
Rated capacity, voltages, phase, and frequency.
Connection group and relevant tap configuration.
Test date, report number, and revision.
Compare these details with the approved data sheet and nameplate information.
A model name alone may not identify the delivered unit. This matters particularly when an order includes several similar transformers.
Some evidence may relate to a tested design rather than the exact unit being shipped.
That does not automatically make it unsuitable. However, the supplier should explain its applicability to the ordered configuration.
Ask which characteristics match and whether relevant design changes affect the evidence.
Keep this distinction visible in the document register. A representative report should not be presented as a unit-specific measurement.
These terms describe different parts of the acceptance process.
Routine tests generally address checks required on individual units under the applicable framework.
The exact scope depends on the product and agreed requirements. Confirm which results must be supplied for each serial number.
Do not assume a generic statement of conformity replaces the required measurements.
Type tests generally support specified design characteristics. Special tests address additional requirements under the applicable standard or agreement.
Their classification and applicability need confirmation for the particular transformer.
A temperature-rise report, for example, should identify the tested configuration and operating conditions. Its relevance should be established before relying on it for another design.
A factory acceptance test, or FAT, is an agreed acceptance activity.
It may include witnessed electrical tests, document review, visual inspection, and accessory checks.
A FAT visit does not automatically include every possible test. Nor does attendance replace missing results.
The inspection plan should establish what will happen, who will attend, and which records will be issued.
A measured value becomes useful when its identity, units, conditions, and acceptance basis are clear.
The following examples explain common review questions. They are not a universal mandatory test list.
Check that the reported ratio corresponds to the specified voltages and relevant tap positions.
For three-phase equipment, confirm that phase-relationship information matches the approved connection arrangement.
A single ratio result may not demonstrate all tap settings required by the contract.
Check which winding, terminals, phases, and tap positions were measured.
Temperature matters when comparing resistance results. Confirm the recorded temperature and any correction used for comparison.
An unexplained difference should be referred to the responsible engineer. Do not apply an arbitrary percentage limit copied from another transformer.
Review the rating base, tap position, temperature basis, and units.
For impedance, establish whether the reported percentage corresponds to the specified transformer rating.
For load loss, confirm whether the stated result has been corrected to the agreed reference condition.
This review checks the report against the specification. It does not replace the project’s fault-current or protection study.
Confirm the voltage and frequency conditions associated with the results.
Compare the values with the agreed guarantees and applicable acceptance rules.
Avoid treating a general brochure figure as the acceptance limit when the approved technical offer states something different.
Electrical insulation tests address different characteristics. Their names should not be treated as interchangeable.
An insulation-resistance reading, for example, is not equivalent to an applied-voltage withstand result.
Where dielectric or partial-discharge testing is required, the report should identify the relevant method and conditions.
Review the recorded test level, duration, result, and acceptance basis as applicable.
A partial-discharge figure needs context.
The applied voltage, measurement arrangement, background interference, and method influence interpretation.
A smaller number from a different test condition is not automatically stronger evidence.
Where a result or limit is unclear, request the supporting explanation. Do not infer compliance from a promotional phrase such as “negligible discharge.”
A satisfactory test result demonstrates performance under the specified conditions. It does not guarantee that future insulation problems are impossible.
Electrical test results do not confirm every physical detail.
The inspection package should also address the configuration that will reach the site.
Depending on the order, check:
Nameplate details and terminal markings.
Enclosure and cable-entry arrangement.
Mounting dimensions and connection interfaces.
Temperature sensors and controller configuration.
Fan controls, alarms, and agreed outputs.
An accessory function marked “checked” should be understandable. The record should identify what was verified and against which requirement.
For example, confirming that a temperature display powers on is different from verifying an agreed alarm output.
Any configuration change after inspection should be recorded and assessed. Relevant documents or checks may need updating.
If customer or third-party attendance is required, establish the arrangements before testing.
Confirm the notice period, test agenda, witness responsibilities, and required sign-off.
Also distinguish a witness point from a hold point under the project’s inspection plan. The agreed rules determine whether work may proceed without attendance or approval.
A witness signature records participation within its stated scope. It is not automatically an independent product certification.
For remote witnessing, agree on equipment identification, result visibility, communication, and retained records.
Do not leave these arrangements until the test bay is booked and shipment is imminent.
Most acceptance reviews produce questions. Some are document corrections; others require technical action.
Record each unresolved item with:
A clear description and reference.
The responsible party.
The required response or corrective action.
The closure evidence and approval status.
A corrected serial-number typo is different from an unexplained result outside the agreed limit.
Both need resolution, but they should not be treated as the same kind of issue.
If a report changes, retain its revision history.
Where corrective work or retesting occurs, the final record should explain what changed and which results remain applicable.
An updated report should not simply make the earlier discrepancy disappear without explanation.
Document approval, shipment release, and site energization are different decisions.
A transformer may satisfy the agreed factory release requirements but still need receiving inspection and commissioning checks.
Packing damage, transport conditions, installation changes, and site connections remain outside the scope of many factory tests.
Shipment approval should therefore state its purpose clearly.
Before dispatch, confirm the agreed handover package is complete and easy to navigate.
It may include:
Approved technical data and final drawings.
Unit-specific test reports.
Applicable design or special-test evidence.
FAT records and closed inspection items.
Installation and maintenance instructions.
Accessory documents and packing information.
Use a document register to identify the final revision of each item.
Keep the package accessible to the receiving and commissioning teams. Reports that remain only in a purchasing email thread are difficult to use later.
The factory records can also provide useful reference information for future engineering reviews, provided comparison conditions are understood.
Dry-type transformer test reports should connect the delivered equipment to clear, agreed acceptance requirements.
Start with identity and scope. Then review the results, their conditions, accessory checks, and outstanding actions.
A pass stamp is not a substitute for that connection. Equally, a missing explanation should prompt clarification rather than an unsupported diagnosis.
For a SNTOOM project, agree on the test and documentation scope before ordering. This gives both parties a clearer basis for inspection, release, and handover.
Preparing a Transformer Inspection or FAT Plan?
Share your transformer specification, applicable standards, witness requirements, acceptance criteria, and document schedule. Discuss your test and documentation requirements with SNTOOM before finalizing the order.
Not necessarily. A conformity document may summarize a compliance declaration. A test report provides results for identified tests. Confirm which documents the contract requires.
Unit-specific reports should be traceable to the delivered equipment. Representative design-test evidence may reference another unit, but its applicability needs a clear technical basis.
A combined document may contain results for several units. Each unit’s identification and applicable results should remain clear. Do not assume one measurement covers every transformer.
Refer it to the responsible engineer and supplier. Check units, conditions, corrections, and acceptance criteria before deciding whether clarification, correction, or further testing is needed.
No. Factory witnessing addresses the agreed factory scope. Receiving inspection, installation verification, and commissioning address conditions after transport and installation.
Possibly, but availability and contractual obligations vary. Agree on document deliverables before ordering, especially where special testing, witnessing, or specific reporting formats are required.
