Leave Your Message

Transformer Testing: FAT, Routine Tests, and Buyer Acceptance Evidence

2026-08-08

Transformer Testing begins with a procurement test plan before it becomes a factory event. It tells the buyer which evidence is needed, when it is reviewed, and who can accept or reject a deviation. The exact scope must follow the applicable edition of the agreed standard and the project specification.

Part 1: Start With the Evidence Decision

Factory acceptance testing, often called FAT, is a planned review of agreed evidence before shipment. Routine tests are normally a defined part of the manufacturer’s production and verification process, while FAT may also include document review, witness points, and commercial release conditions.

Write the decision you need from the evidence. A buyer may need confidence that the unit matches the approved design, that agreed checks were recorded, or that exceptions were resolved. Those are different questions and should not be merged into a vague request for “full testing.”

Part 2: Build the Test Plan Into the RFQ

Put the requested evidence in the RFQ, not in a late email after production begins. State the applicable standard edition, project requirements, test categories to be reported, witness notice period, acceptance criteria, and the required document format.

A clear RFQ also names the parties who can attend or review remotely. It should define how a nonconformance is recorded, who approves a concession, and what must be closed before shipment authorization. Engineering responsibility remains with the project team.

Part 3: Ask for Traceable Routine-Test Records

The useful question is not whether a supplier says that routine tests are available. Ask which records will identify the unit, the test date, measuring arrangement where relevant, observed result, applicable requirement, reviewer, and any approved exception.

Request a controlled index for the data book. That index can connect the purchase order, approved drawings, nameplate information, test records, and exception log without assuming that every transformer or project uses the same document set.

Part 4: Set Practical Witness Hold Points

Witnessing works best when the buyer selects a few decision points that materially affect acceptance. Examples include a pre-test document review, an agreed observation window, and a final review of the signed records. The agreed plan should say whether attendance is on site, remote, or document-based.

Avoid turning the witness plan into an unstructured tour. A short agenda, named attendees, language for measurements and reports, and a process for questions help both sides prepare. If a result needs technical interpretation, the project engineer should decide the acceptance path.

Part 5: Keep Factory Evidence Separate From Site Acceptance

Factory records support a shipment decision; they do not remove the need for project-specific receiving, installation, protection, and energization checks. Site acceptance belongs in a separate responsibility matrix because conditions after delivery are outside the factory test environment.

The matrix should assign owners for transport inspection, document handover, installation checks, commissioning activities, and final acceptance. It prevents a buyer from treating an FAT report as proof that every downstream interface is ready.

Part 6: Compare Responses With an Evidence Matrix

Use one comparison table for every bidder. Rows can cover requested test category, record format, witness option, notice period, exception process, document delivery, and responsibility after shipment. Mark each response as confirmed, qualified, or requiring clarification.

This approach makes differences visible without ranking suppliers on unsupported claims. It also gives the procurement team a focused list of clarifications before award rather than a late dispute over what “tested” meant.

Part 7: Turn the Plan Into a Product Discussion

When the project inputs are ready, use the FARADY ELECTRIC Transformer solutions page to start a product-family discussion. Confirm the rating, configuration, standards, test scope, and documentary evidence for the specific project before selecting a unit.

For a request that includes the evidence matrix, use the project inquiry channel. A category page is not a substitute for a project specification, and no specific transformer model should be selected from this guide alone.

FAQs

What is the difference between FAT and routine tests?

FAT is an agreed acceptance activity that can include witness and document-review steps. Routine tests are defined production or verification checks; the exact relationship must be set in the project specification.

Should a buyer witness every transformer test?

No universal rule applies. Select witness points that affect the project acceptance decision and record the agreed attendance method in the test plan.

What should a transformer test report identify?

It should identify the unit, test date, relevant requirement, recorded result, reviewer, and any approved exception as required by the project.

Does a factory test replace site acceptance?

No. Factory evidence supports shipment acceptance, while site acceptance covers delivery condition, installation, interfaces, and commissioning responsibilities.

Which standards should be named in an RFQ?

Name the applicable standard edition and every project-specific requirement. Confirm their relevance with the engineering authority before the RFQ is released.

Can one standard test plan fit every transformer?

No. Duty, design, purchaser requirements, destination rules, and acceptance responsibilities change the evidence plan.

References