A useful transformer SFRA baseline is a comparison record, not simply a graph labelled “factory test.” If sweep frequency response analysis is required for a liquid-filled substation transformer, agree which equipment condition each measurement represents, which later measurement it will support, and which files and configuration records must be handed over. A shipping-condition reference and a final assembled-condition reference answer different questions. Have the responsible engineer define the required comparisons before the order is released.
AI-generated illustration of a hypothetical transformer shipping state, not a HEAKOR product, test, facility or project photograph, and not an approved transport arrangement.
This guide is for EPC procurement teams and owners’ engineers specifying three-phase liquid-filled substation transformers for industrial projects with an agreed IEC or purchaser-specific test basis. It addresses the evidence purchased with an agreed test scope—not test execution, fault diagnosis or permission to energize.
Start with the comparison the buyer actually needs
Ask whether the required record is intended to support a transport-condition review, establish a reference for the completed installation, or both. Write the intended use beside each deliverable. The phrase “SFRA included” does not explain whether the proposed work supplies a usable reference for either purpose.
IEC 60076-18:2012 addresses measurement technique and equipment when frequency-response measurement is required, at a factory or on site. Its scope does not establish a blanket purchasing requirement for every transformer. IEEE C57.149-2024 addresses application and interpretation for oil-immersed transformers, including data retention. Agree the applicable document and edition with the project engineer rather than treating the two references as interchangeable contractual wording.
Do not confuse a shipping reference with an installed reference
Transport and final assembly can leave the transformer in different documented conditions. Instrument-maker technical guidance on comparative measurements identifies oil-fill condition, bushings, tap positions and connections as relevant to comparability. Consequently, an earlier trace should not be treated as directly comparable solely because its serial number matches.
Consider a hypothetical order with a factory record taken in one assembly condition and a later record taken after site completion. Before interpreting a difference, the reviewing engineer needs to know what changed between those states. This example does not prescribe how either measurement should be performed or require an additional test. It illustrates why procurement must preserve the condition information.
Use separate record names for different agreed purposes. Avoid a single folder called “baseline” containing several unlabeled states. Keep superseded references available, with the reason a newer reference was designated; do not silently replace the historical file.
Agree a small comparison schedule before quotation closes
The following is a proposed buyer document, not a mandatory standard form. Ask bidders to complete the applicable rows and flag any comparison their proposed scope cannot support.
Suggested SFRA comparison schedule
Decision: Purpose
Information to agree: Transport review, final-condition reference or another named engineering purpose.
Question the buyer closes: What later decision is this record intended to support?
Decision: Reference state
Information to agree: Equipment identifier, stage, date and documented assembly/fluid condition.
Question the buyer closes: Which physical state does the reference describe?
Decision: Comparison partner
Information to agree: Planned later record and the responsible engineer’s comparability requirements.
Question the buyer closes: What will be compared with what?
Decision: Condition record
Information to agree: Approved record format for relevant settings, connections, configuration photographs and deviations.
Question the buyer closes: Can the reviewer establish whether conditions match?
Decision: Data handover
Information to agree: Original measurement files, readable report, file-format details and access arrangements.
Question the buyer closes: Can the receiving team retrieve and review the evidence?
Decision: Review outcome
Information to agree: Named technical reviewer, questions requiring resolution and the written disposition.
Question the buyer closes: Who decides whether the comparison is usable?
Give each required deliverable a quotation status: included, separately priced, by an identified third party, or unresolved. Agree the submission milestone and recipient. A test price without the associated data and review scope leaves an avoidable gap between factory procurement and site acceptance.
Purchase usable data, not only a plotted PDF
Specify the file package the receiving engineering team can actually use. A readable report helps document the result; original data allow the appointed reviewer to work with the measurements rather than a screenshot. Ask the proposed service provider and receiving reviewer to confirm usable formats before testing, especially if different organizations will collect and assess the records.
Retain an index linking each data file to its reported measurement, equipment condition and report revision. Request an explanation of any conversion, renamed trace or missing file. These are recommended information-management controls, not a claim that a particular software export satisfies a standard.
For the separate task of matching documents to the supplied equipment, use the HEAKOR technical document centre. This article adds the narrower question: will the designated reference support the intended comparison?
Resolve a comparability gap without inventing an acceptance result
A missing configuration record or an unexplained difference should become a specific engineering question, not an automatic declaration of damage or satisfactory condition. Ask the reviewer to identify the evidence gap, what conclusion remains unsupported, and what additional information or assessment is needed.
Keep the reviewer’s disposition with both records. If the available baseline is unsuitable for the intended comparison, say so explicitly and obtain an agreed alternative plan. This guide supplies no numerical trace-deviation limit, diagnostic rule, retest procedure or release criterion. Other contractual tests and approvals remain separate.
Frequently asked questions
Can a supplier’s generic SFRA report serve as the baseline?
Not as a same-unit baseline merely because the rating matches. If another unit’s data are proposed as a reference, ask the responsible engineer to explain the permitted use and its limitations. Label that evidence differently from measurements of the purchased unit.
Must the factory and site use the same instrument brand?
Do not make brand identity the sole comparability test. Public instrument guidance discusses comparisons across test sets under suitable conditions. Ask the technical reviewer to confirm measurement compatibility and usable data formats for the actual proposed arrangement.
Does an acceptable SFRA comparison replace other acceptance tests?
No. A comparison supports its defined assessment purpose, not every transformer requirement. Retain the other tests and approvals specified for the equipment and project.
What if the existing purchase order says only “SFRA report”?
Clarify the intended reference state, comparison purpose and data handover before the relevant work takes place. Obtain written agreement on any scope or commercial change rather than assuming additional measurements or engineering review are included.
Include the baseline purpose in your HEAKOR enquiry
Start with the substation transformer category. Send the required ratings, winding voltages, phase and frequency, destination, project test specification, intended shipping condition and the comparison purpose. Mark unknown conditions as to be confirmed.
Submit Your Project Specification to request a quotation addressing the required equipment and document scope. SFRA availability, performing party, reference conditions, file deliverables and review responsibilities require written confirmation for the proposed offer; this guide does not establish a HEAKOR testing capability or included service.