How do transformer and switchgear makers answer a tender?
A utility, EPC contractor or industrial owner issues a package for each equipment lot. It normally holds a technical specification, one or more datasheets, a set of schedules the bidder must fill in, a list of the IEC or IEEE standards that apply, and the buyer's own standard specifications. The schedules go by several names. In many markets they are called guaranteed technical particulars, or GTP.
The bidder has two jobs. One is to fill every line of the schedules with a figure it is prepared to guarantee. The other is to read the specification text, where the buyer sets test scope, accessories, documents and evidence, and to say where the offer differs.
- List every requirement in the specification, with its clause, and every line in the schedules.
- Fill each schedule line from the design or the standard product datasheet, and note which figures are guaranteed and which are typical.
- Check each called-up standard for its edition. A buyer's specification may cite an edition older than the one your type tests were made to.
- Match the test requirements to the type test reports you hold and to the routine tests your works performs on every unit.
- Mark each row complies, deviates, clarification or not addressed, and write the reason.
- Price what the standard offer leaves out: repeated type tests, special tests, witnessed tests and extra accessories.
The output is a compliance matrix that covers every clause and a technical deviation list that carries only the differences. Some buyers ask for the deviations on their own schedule form and treat anything not listed there as accepted.
Which standards come up in transformer and switchgear tenders?
Most tenders name a product series and leave the bidder to work out which parts apply. The table lists the series that appear most often, at name level. It is our own summary. Use the edition your contract names.
| Series | What it covers | Where the tender usually pins it down |
|---|---|---|
| IEC 60076 | Power transformers: general requirements, temperature rise, insulation levels and dielectric tests, short-circuit withstand, sound levels, dry-type units and more | Which tests are routine, type or special for this order, and which type test reports are accepted |
| IEC 62271 | High-voltage switchgear and controlgear above 1 kV: common specifications, circuit-breakers, disconnectors, metal-enclosed assemblies and gas-insulated switchgear | Ratings, internal arc classification, service continuity category and the type tests to be evidenced |
| IEC 61439 | Low-voltage switchgear and controlgear assemblies. Part 1 gives general rules and Part 2 covers power switchgear and controlgear assemblies | Design verification evidence for the assembly offered, and the routine verification done on each assembly |
| IEEE C57 series | Transformers where the buyer works to IEEE. C57.12.00 gives general requirements for liquid-immersed units and C57.12.90 is the matching test code | Whether the whole order is to IEEE or a mix. The test categories and terms are not the same as in IEC |
| Component standards | Bushings, tap-changers and insulating liquid each have their own IEC standard, and IEC 60076-1 refers to them | Named makes or approved-vendor lists for components, and the certificates wanted for each |
| Buyer and national specifications | Utility standard specifications and national adoptions that add to or change the IEC text | Extra tests, lower loss limits, a maximum age for type test reports and a list of acceptable laboratories |
A specification can name IEC and IEEE documents side by side. Do not assume the two give the same answer. If the order of precedence is not stated, ask.
What goes in the deviation list for electrical equipment?
The deviation list carries each point where the offer differs from the tender, with the clause, what is offered and why. For transformers and switchgear the same few areas come up in most offers.
| Area | What to check before you sign the offer |
|---|---|
| Losses and other guarantees | Whether the no-load loss, load loss, impedance and sound figures in the schedule are guaranteed maximums, and what the tender says happens if the tested figure is worse |
| Tolerances | Whether the buyer accepts the tolerances of the named standard or sets its own, including figures stated with no positive tolerance |
| Test scope | Which tests the tender moves from type or special into the routine list for every unit, and which it wants witnessed |
| Type test evidence | Whether an existing report is accepted, how old it may be, how close the tested design must be to the one offered, and which laboratories the buyer accepts |
| Accessories and fittings | Tap-changer, bushings, cooling equipment, monitoring and protection devices, cable boxes and terminals, compared with your standard scope |
| Components and sub-suppliers | Named makes for major components, and whether alternatives need approval before award |
| Service conditions | Altitude, ambient temperature, pollution and seismic figures that differ from the normal conditions the standard assumes |
| Documents and approval | Drawing approval steps, the document schedule, languages and the number of review cycles allowed in the programme |
Read the evaluation clauses before you declare a deviation
Many utility tenders evaluate losses in money and add the result to the bid price. Some state that an offer with missing schedule entries or with deviations from named clauses may be rejected. Find those clauses first, then decide whether a gap goes in as a deviation, a clarification question or a priced alternative.
Which documents follow after award?
After the order, the buyer's document schedule turns the tender requirements into submissions. The contract decides the list. These are the ones a transformer or switchgear maker should expect.
| Document | What the buyer looks for |
|---|---|
| Inspection and test plan (ITP) | Every works inspection and test in order, the procedure and acceptance basis for each, and the buyer's hold and witness points |
| Type test reports | The design tested, the standard and edition, the laboratory, the date and the tests covered, and a statement of how the tested unit relates to the one ordered |
| Routine test reports | One report per unit by serial number, each required test present, and results set against the guaranteed figures |
| Calibration certificates for test instruments | A valid, traceable certificate for each instrument named in a test report on the day it was used |
| Witnessed test and FAT records | The notice given, who attended, the signed results and a closed punch list. See FAT vs SAT |
| Component certificates | Test certificates for bushings, tap-changers, instrument transformers, relays and insulating liquid, as the contract lists them |
| Operation and maintenance manuals | Installation, commissioning, operation and maintenance instructions in the contract language, with as-built drawings |
| Final documentation dossier | All of the above in the buyer's index order, at the approved revision and signed where the contract says so |
For the instrument evidence, see the guide to calibration certificates for test reports. A checklist for the reports themselves is on the routine test report checklist template page.
How does OdysseyGPT help?
OdysseyGPT reads the documents you upload and checks them against the customer's written requirements. Each finding shows the passage it rests on in both documents. Document Review takes the tender specification as the base and your datasheets, filled schedules, type test report summaries and standard offer text as the documents to check. It works forward and in reverse, and it exports an editable compliance matrix with a deviations and clarifications list. The other tools each take a narrower set of documents.
| Your document | Tool | What it reports |
|---|---|---|
| Tender specification, schedules and your offer documents | Document Review | A status and a pair of quotes for each tender requirement, plus obligations in your documents the tender does not answer |
| Tender specification and the buyer's standard specifications | Customer Specification Review (beta) | A requirements register: one line per obligation for ratings, tests, accessories and documents, with its clause |
| The buyer's datasheet or schedule and your filled copy | Datasheet Comparison (beta) | Matched fields and every material difference in value, with the cell each figure came from |
| Offers from your component sub-suppliers | Technical Bid Evaluation (beta) | Each sub-supplier's answer to one requirement baseline, with declared and undeclared deviations. It does not pick a winner |
| Offer, clarification replies and the deviation schedule | Deviation Register (beta) | One running record of each deviation through the clarification rounds to the buyer's decision |
| The contract document schedule | VDRL/MDR Tracker (beta) | A register of each contractual submission with its due date and status |
| Your ITP and the buyer's quality and test clauses | ITP Validator (beta) | Tests the buyer asks for that the plan omits, and hold or witness points that do not match |
| Evidence for a witnessed inspection stage | Inspection Readiness Check (beta) | A readiness verdict for the stage, with blockers listed apart from advisory items |
| Routine test reports and calibration certificates | Calibration Validity Check (beta) | Each instrument named in a report matched to its certificate and checked for validity on the test date |
| FAT procedure, approved drawings, ITP status and open items | FAT Readiness Check (beta) | Whether the documents a witnessed test depends on are in place before the buyer travels |
| Final dossier folder and the buyer's index | MRB Readiness Check (beta) and MRB Compiler (beta) | Documents that are missing, unapproved or at the wrong revision, and a manifest in index order |
The tools sit in three stage groups: tender, inspection and handover. The wider picture is on the manufacturing page.
What does a result look like?
This table is an invented example. The utility, the transformer, the clause numbers, the maker's documents and every figure are made up to show the layout of a result. None of it comes from a real tender, a real manufacturer or a standard.
| Tender requirement (quoted) | Maker's document (quoted) | Status | Note |
|---|---|---|---|
| "Rated power 40 MVA at ONAF cooling, vector group YNd11." (Schedule A, lines 3 and 7) | "Rating: 30/40 MVA ONAN/ONAF. Vector group: YNd11." (GTP schedule, lines 3 and 7) | Complies | Same rating basis and vector group in both documents. |
| "No-load loss at rated voltage shall not exceed 18 kW. No positive tolerance is permitted." (Specification 5.2) | "No-load loss: 18 kW, subject to IEC tolerance." (GTP schedule, line 21) | Deviates | The figure matches but the maker reserves a tolerance the tender excludes. |
| "The temperature rise test shall be carried out on one unit of the order." (Specification 9.3) | "Temperature rise: type test report TR-2219 for an identical design is offered in lieu." (Offer letter, p. 4) | Deviates | A report is offered in place of a new test. Decide whether to price the test as an option. |
| "Type test reports shall be from an independent accredited laboratory and not more than five years old at bid opening." (Specification 9.1) | "Short-circuit withstand test report, dated March 2019." (List of type test reports, item 2) | Clarification | The report date falls outside the stated period. The laboratory's accreditation is not stated in the list. |
| "The on-load tap-changer shall be of a make listed in Annex C." (Specification 6.4) | "On-load tap-changer: vacuum type, 17 positions." (Datasheet DS-40-132, p. 3) | Clarification | The make is not stated in the datasheet. |
| "Frequency response measurement shall be made on each unit before dispatch and the records supplied." (Specification 9.6) | No matching statement found in the documents supplied. | Not addressed | Not in the maker's routine test list. Add it to the offer or declare it. |
| "Routine tests shall be witnessed by the Purchaser. Fourteen days' written notice shall be given." (Specification 9.8) | "The purchaser may witness routine tests. Notice of test: 7 days." (Quality plan QP-11, p. 6) | Deviates | The notice period offered is shorter than the tender asks for. |
| "Calibration certificates for all instruments used in the tests shall be included in the test report." (Specification 9.9) | "Test instruments are calibrated at intervals set by our procedure." (Quality plan QP-11, p. 7) | Clarification | The maker's text does not say the certificates are supplied with the report. |
A tender engineer opens the two quotes on each row and confirms or changes the status. The rows that stay as deviates or clarification feed the deviation schedule and the list of questions to the buyer.
Where OdysseyGPT falls short
- It performs no test and measures nothing. It is not test-bay software, it does not connect to test equipment, and it does not produce a test report.
- It does no design work. It does not calculate losses, impedance, temperature rise, short-circuit forces or busbar ratings, and it cannot tell you whether a guaranteed figure is achievable.
- It does not read single-line diagrams, general arrangement drawings, wiring diagrams or rating plate drawings. A requirement that appears only on a drawing is not checked.
- It does not judge whether a type test report covers the design you offer. It can show what the report states and what the tender asks for. An engineer decides whether the tested unit is close enough.
- It holds no standards. A limit that sits only inside IEC 60076, IEC 62271 or an IEEE document is checked only if you upload the edition and it is readable text.
- It can pair a requirement with the wrong line or miss one, most often in long schedules with repeated row labels. The quotes are there so that a person can catch this.
- It does not fill in the buyer's schedules for you, submit anything to a tender portal or set a price.
- Tools carrying a beta marker on this page are available on request, and we set each team up ourselves.
Talk through your tender review
See how OdysseyGPT reviews a tender
Tell us how your team reviews tenders today. We can walk through an example together.
