Switchgear Test Evidence and Editions

A certificate is an index to evidence, not proof that the exact switchgear offered for a project meets every requirement. Acceptance requires a traceable chain from contract and standard edition to test object, configuration, laboratory scope, raw results, deviations, design changes and the serial-numbered equipment delivered.

This guide provides a practical document-control and technical-review method for IEC-based MV switchgear projects. It separates declarations, certificates, type-test reports, routine-test records, FAT results and calibration evidence, then shows how to control amendments, corrigenda and legacy designs.

Executive conclusions

Freeze the contractually applicable standard number, edition, amendment, corrigendum and interpretation sheet for every product and test.
“IEC 62271 compliant” is incomplete: IEC 62271-1 provides common specifications while the relevant product/assembly part adds or modifies requirements.
A declaration of conformity is the supplier’s statement; a certificate is a conformity-assessment output; a test report contains the technical evidence. They are not interchangeable.
ISO/IEC 17025 accreditation is meaningful only when the issuing laboratory, location, test method and relevant scope were accredited at the test date.
Map the offered design to the tested object: ratings, compartment, gas, breaker, busbar, CT/VT, materials, dimensions and manufacturing site.
Read the complete report, including photographs, test arrangement, instrumentation, sequence, failures, repairs, retests and conclusions—not only its cover page.
Type tests qualify a design/configuration; routine tests screen each manufactured unit; FAT verifies agreed functions/interfaces. None replaces the others.
A later standard edition does not automatically invalidate installed equipment, but a new procurement must resolve edition deltas and legal/contract requirements.
Manufacturer extension-of-validity rules must be technically demonstrated; similarity is not evidence by assertion.
Use controlled metadata, checksums and an evidence matrix so the accepted dossier remains auditable after staff and software change.

1. Build the applicable-standard matrix

Requirement layer	Typical source	Control question
Law/regulation	Country grid/safety/environmental rules	What is mandatory at placing on market, installation or energization?
Installation	IEC 61936-1, national wiring/earthing/fire rules	How is product integrated safely?
Common switchgear	IEC 62271-1:2017+AMD1:2021	Which common service, rating, design and test provisions apply?
Assembly	IEC 62271-200:2021+AMD1:2024	Which LSC, partition, accessibility and IAC claims apply?
Component	IEC 62271-100/-102/-103/-105 etc.	Which breaker, disconnector, switch or combination duties apply?
Instrument transformers	IEC 61869 series	Which CT/VT/LPIT accuracy and transient requirements apply?
Protection/control	IEC 60255, IEC 61850 and cyber/EMC requirements	Which device, communication and system evidence applies?
Project	Employer specification, data sheets and approved deviations	What exceeds or selects among standard options?

For each row record title, exact edition/date, amendments, corrigenda, interpretation sheets, national adoption, language, contract clause and precedence. A standard-series reference without its part/edition cannot be audited.

2. Understand document types

Document	What it normally establishes	What reviewer must still verify
Manufacturer declaration	Supplier asserts conformity	Scope, legal basis, signatory, product identity and supporting evidence
Third-party certificate	Certification body evaluated defined product/scheme	Scheme, accreditation, certificate validity, listed model/configuration and surveillance
Type-test report	Specific design object passed specified tests	Complete configuration, method, quantities, deviations, failures and applicability
Test summary/certificate	Headline test/result reference	Underlying full report and conditions
Routine-test record	Tests on a serial-numbered production unit	Correct acceptance criteria, instruments and traceability
FAT/SAT record	Project functions/interfaces checked	Coverage, approved procedure, punch list and retest
Calibration certificate	Instrument result and traceability at a date	Range, uncertainty, status during test and out-of-tolerance impact
Design calculation	Analytical support for rating/design decision	Inputs, method, validation, software/version and independent review

3. What ISO/IEC 17025 accreditation does—and does not—mean

ISO/IEC 17025:2017 is the current international standard for testing/calibration laboratory competence, impartiality and consistent operation; ISO confirmed it in 2023. Accreditation can increase confidence, but the accreditation symbol on a report is not universal coverage.

verify accreditation body and recognition arrangement where contractually required;
download the scope valid on the test date;
match legal entity and physical laboratory location;
match test method/standard, voltage/current/range and field of testing;
identify subcontracted or off-site tests and their accreditation status;
confirm the report carries the appropriate accreditation mark/reference;
distinguish accredited results from non-accredited opinions/calculations in one report;
check revisions, suspensions and withdrawals without assuming today’s scope applied historically.

Accreditation does not decide whether a different offered design is covered by the tested object, whether the owner selected the right standard, or whether all project requirements were included.

4. Freeze the edition baseline

identify the tender issue date and governing law/regulation;
list every normative document and exact edition available at that date;
record amendments, corrigenda and interpretation sheets separately;
state whether later publications automatically apply or require change control;
resolve conflicts between employer specification and standard;
issue a supplier-confirmed compliance/deviation schedule;
freeze the accepted baseline before design approval;
monitor standards through manufacture/commissioning and assess changes formally.

Use the official IEC Webstore lifecycle page or official publisher record to confirm publication and replacement status. A search-engine snippet, reseller catalogue or undated PDF is not edition control.

5. Amendment, corrigendum and interpretation sheet

Amendment: changes/adds normative content; specify whether base + amendment or consolidated version applies.
Corrigendum: corrects errors in a publication; it can materially change a boundary or value and must be tracked.
Interpretation sheet: official interpretation of a requirement; include relevant sheets in the baseline.
Consolidated version (CSV): combines base publication and amendments for convenience; edition notation must remain clear.
Redline/commented/extended product: presentation/value-added format; confirm the underlying normative publication.

Example: procurement may cite IEC 62271-200:2021+AMD1:2024, not simply “IEC 62271-200 latest.” The latter can shift obligations after tender and create inconsistent bids.

6. Test-object identity sheet

Create a one-page structured identity record for every type-test report:

manufacturer, factory, product family, type designation and serial number;
rated voltage, insulation level, frequency, current, short-time current/duration and peak;
breaker/switch/contactor/fuse type and operating mechanism;
gas/insulation medium, pressure, partition material/class and enclosure material;
busbar material/size/support spacing, joint design and conductor arrangement;
compartment dimensions, pressure relief, duct/plenum and IAC access sides;
CT, VT, sensor, bushing, cable termination and earthing switch;
IP/IK, indoor/outdoor state and normal/special service condition;
drawing/BOM revisions and photographs;
test date, report number/revision, laboratory and witnesses.

7. Offered-versus-tested applicability matrix

Feature	Tested	Offered	Effect/rationale	Disposition
Continuous current/busbar	Report/drawing value	Project value	Temperature rise/field distribution	Covered/calculation/retest
Short-circuit duty	kA, duration, peak	Required duty	Thermal/electrodynamic	Accept/reject
Enclosure/compartment	Dimensions/material	Dimensions/material	IAC pressure/thermal/IP	Engineering assessment
Breaker	Type/rating/mechanism	Type/rating/mechanism	TRV, heat, interfaces	Component + assembly evidence
CT/VT	Types/quantity/location	Types/quantity/location	Heat, field, obstruction/arc path	Covered/extra evidence
Gas/pressure	Medium/min pressure	Medium/min pressure	Dielectric/thermal/arc	No casual substitution
Factory	Manufacturing site	Manufacturing site	Process/material control	Quality-transfer evidence

Do this per test because the worst case differs. The configuration most severe for temperature rise is not necessarily most severe for dielectric, short-circuit or IAC performance.

8. Review the complete test sequence

approved standard and clause/test duty;
test circuit, supply, earthing, environmental conditions and tolerances;
instrument IDs, calibration and uncertainty where relevant;
preconditioning and sequence of tests on the same object;
measured values/oscillograms, not only “pass”;
acceptance criterion and how it was evaluated;
photographs before/after and inspection/dismantling observations;
aborted attempts, nonconformities, repairs and design changes;
retest scope and whether earlier tests remain representative;
laboratory conclusion, signatures, seals and report revision history.

If a failure led to a design modification, require an engineering assessment of every test affected by the modification. Passing one repeated test does not automatically restore the complete type-test sequence.

9. Core IEC 62271-200 evidence families

dielectric tests and partial-discharge requirements where applicable;
radio interference/EMC and auxiliary/control circuit tests as applicable;
resistance and continuous-current temperature-rise tests;
short-time/peak withstand of main and earthing circuits;
making/breaking evidence from relevant switching-device standards and assembly integration;
mechanical operation/endurance and interlock tests;
IP protection and environmental tests where specified;
internal arc classification only when assigned, at stated current/duration/accessibility/sides;
cable-test provisions and insulation after relevant operations;
routine tests on each manufactured assembly.

The exact required set depends on design and classifications. Use the normative edition, not this summary, to build the clause-by-clause checklist.

10. Type test, routine test, FAT and SAT

Stage	Primary purpose	Typical blind spot
Design/type verification	Demonstrate representative design performance	Offered variant not represented
Routine production test	Detect manufacturing/assembly defects on each unit	Does not repeat destructive/high-power design tests
FAT	Verify project wiring, logic, interfaces, operation and documents	Primary system/source/installation not yet present
SAT/commissioning	Verify as-installed circuits, protection, interlocks and system integration	Cannot repair missing design qualification
Maintenance test	Assess condition/performance over life	Pass does not rewrite original ratings/classification

11. Routine-test traceability

serial number, panel lineup and as-built drawing/BOM revision;
standard/clause and approved test procedure revision;
test values, limits and pass/fail—not blank ticks;
instrument ID/range/calibration due date;
operator/checker/date and controlled corrections;
nonconformance, repair and full relevant retest;
software/firmware/settings used for functional checks;
link to FAT punch-list closeout and shipping release.

12. Calibration-certificate review

instrument serial number matches test record;
calibration was valid on test date;
range and points bracket the measurement;
measurement uncertainty is compatible with acceptance tolerance;
traceability and laboratory accreditation scope are stated;
as-found/as-left results and adjustments are visible;
out-of-tolerance findings trigger impact review of earlier tests;
environment/correction factors are included where required.

13. Legacy report against a newer edition

obtain both editions and official change information;
build a clause-level delta matrix: editorial, clarified, new/changed requirement or changed test;
map each technical delta to design/test evidence;
check whether the tested object equals the current offered design;
identify grandfathering/regulatory/contract rules;
accept existing evidence only with documented technical rationale;
perform supplementary analysis/test where evidence is missing;
obtain owner approval for deviations; do not silently relabel the old report.

A statement that “the new edition is mainly editorial” must be proven against the actual clauses affecting the product. IEC 62271-200:2021, for example, changed and clarified LSC and IAC-related provisions relative to the 2011 edition.

14. Design changes after type testing

busbar cross-section/material/plating/support spacing;
insulator material/profile or gas/pressure;
enclosure dimensions, thickness, doors/latches or pressure relief;
breaker/switch/earthing-switch type or mechanism;
CT/VT/sensor number, heat loss, position or size;
cable termination, bushing or plug-in interface;
partition class/material, shutters or ventilation;
control wiring, auxiliary voltage, EMC filter or firmware;
manufacturing site/process/supplier;
IAC duct/plenum/room interface.

Use the extension-of-validity provisions of the exact product standard where available. The assessment should identify the physical failure mechanism, whether the change is less severe, calculation/test validation and approval authority. “Same family” is not a technical argument.

15. Authenticity and anti-misrepresentation checks

obtain documents through manufacturer/laboratory controlled channel;
verify report/certificate number, revision, page count and signatures;
look for missing pages, inconsistent fonts, altered tables or cropped photos;
verify laboratory/certification-body directory entry and scope;
confirm product/type designation directly with issuer for high-risk evidence;
store original digitally signed file where available;
calculate and record a file checksum;
retain superseded revisions with status rather than overwrite them;
restrict edit rights and log downloads/approvals.

16. Evidence register structure

Metadata field	Example content
Requirement ID	Specification clause / IEC clause / legal article
Applicable edition	Base + amendment + corrigendum + interpretation sheet
Evidence	Report/certificate/drawing/calculation ID and revision
Test object	Type/serial/factory/rating/configuration
Applicability	Direct / extended with rationale / gap
Issuer status	Laboratory/accreditation/scope/date
Review	Engineer/date/comments/status
Change link	NCR, concession, design-change or retest reference
File integrity	Filename, checksum, source and access class
Final disposition	Accepted / conditional / rejected / superseded

17. Review gates

Tender: applicable editions, classifications, evidence schedule and deviations complete.
Design approval: offered-versus-tested matrix and outstanding tests approved.
Pre-FAT: type evidence, drawings/BOM, routine procedures and calibrations approved.
FAT release: results, NCRs/retests, serial mapping and punch-list disposition complete.
Shipment: as-built configuration and protected document package frozen.
Energization: SAT/commissioning, settings, interlocks and installation interfaces accepted.
Handover: searchable final dossier, lifecycle obligations and change triggers assigned.

18. Common mistakes

accepting a two-page certificate instead of the report;
citing an IEC series without part/edition/amendment;
assuming accreditation covers every method and location;
matching only rated voltage/current, not construction;
ignoring test failures, modifications and retest boundaries;
using one “family” report for all ratings/tests;
treating routine tests or FAT as type tests;
assuming a later edition automatically invalidates or validates old evidence;
not checking calibration range/uncertainty;
overwriting report revisions and losing audit history;
accepting “latest IEC” as a stable contract requirement;
releasing manufacture before evidence gaps are priced and scheduled.

Primary references

Application note: Standards are copyrighted normative documents. Use licensed copies and project-specific clauses for acceptance; summaries and checklists support but cannot replace them.

Certificates, Test Reports and Standard Edition Control