Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC Guide 117 — Type Testing Requirements
Harmonized Framework for Type Testing of Electrical Products
1. Understanding IEC Guide 117
IEC Guide 117 provides a harmonized framework for type testing of electrical products. Type testing — also known as design testing or prototype testing — is the process of verifying that a product design meets all applicable standard requirements before entering series production. The guide establishes common principles for sample selection, test sequences, pass/fail criteria, and documentation across all IEC product committees.
A well-planned type test program can reduce time-to-market by 3-6 months. Guide 117 helps product committees define efficient test sequences that minimize redundant testing while ensuring comprehensive coverage.
The guide distinguishes between type testing (performed once on a representative sample to validate the design), routine testing (performed on every production unit), and surveillance testing (periodic verification of continuing compliance). Each category has distinct sampling rules, test severities, and acceptance criteria.
2. Type Test Planning and Execution
Guide 117 recommends a structured approach to type testing. The first step is defining the test program based on the product category, applicable standards, and intended operating conditions. The test plan should include a clear specification of the test samples, the number of units required, preconditioning procedures, test sequence (some tests are destructive and must be performed last), and environmental conditions.
| Test Phase | Purpose | Typical Tests | Sample Requirements |
|---|---|---|---|
| Preconditioning | Stabilize sample before measurement | Temperature stabilization, humidity soak, burn-in | All samples |
| Basic Safety Tests | Verify fundamental protection | Dielectric strength, leakage current, grounding | All samples |
| Performance Tests | Verify functional specifications | Efficiency, accuracy, output characteristics | All samples |
| Environmental Tests | Verify robustness | Temperature cycling, vibration, humidity, IP rating | Subset of samples |
| Destructive Tests | Verify margins | Endurance, overload, short-circuit, mechanical impact | Dedicated samples |
| EMC Tests | Verify electromagnetic compatibility | Emissions, immunity, ESD, surge | Separate samples recommended |
Destructive tests must be clearly identified in the test plan because they render the sample unusable for subsequent testing. Guide 117 recommends allocating dedicated samples for destructive test sequences and ensuring that the total sample size is sufficient to cover all required tests.
3. Documentation and Compliance Strategy
Comprehensive documentation is a cornerstone of type testing. The type test report must include: identification of the testing laboratory and sample, reference to all applicable standards and editions, detailed test conditions and instrumentation, measured results with uncertainty, pass/fail determinations, and any deviations from the standard test methods.
From an engineering strategy perspective, Guide 117 encourages pre-compliance testing during the design phase to identify issues before the formal type test program begins. Pre-compliance testing typically uses reduced sample sizes and simplified setups but follows the same test methods, allowing engineers to identify and correct design deficiencies early.
Companies that implement a structured pre-compliance testing program report first-pass type test success rates above 85%, compared to less than 50% for those who go directly to formal type testing without pre-screening. The cost of a single formal type test failure often exceeds the entire pre-compliance test budget.
The guide also addresses the concept of “testing family” — groups of products that share a common platform or design architecture. If properly justified, type testing can be performed on the worst-case variant within a family, and results can be extended to other members without full retesting. This approach significantly reduces certification costs for product families.
4. Frequently Asked Questions
Q: How many samples are typically required for type testing?
A: This depends on the product standard, but Guide 117 recommends a minimum of 3-5 samples for most product categories. Complex products with multiple variants may require 8-12 samples to cover all test sequences.
A: This depends on the product standard, but Guide 117 recommends a minimum of 3-5 samples for most product categories. Complex products with multiple variants may require 8-12 samples to cover all test sequences.
Q: Can type testing be performed at an in-house laboratory?
A: Yes, provided the laboratory is appropriately equipped, uses calibrated instruments, follows the standard test methods, and operates under a quality system (ISO 17025 accreditation is preferred for regulatory acceptance).
A: Yes, provided the laboratory is appropriately equipped, uses calibrated instruments, follows the standard test methods, and operates under a quality system (ISO 17025 accreditation is preferred for regulatory acceptance).
Q: What happens if a sample fails a type test?
A: The design must be corrected, and the failed test — plus any affected downstream tests — must be repeated on a new sample. Guide 117 does not permit retesting the same modified sample without full re-qualification.
A: The design must be corrected, and the failed test — plus any affected downstream tests — must be repeated on a new sample. Guide 117 does not permit retesting the same modified sample without full re-qualification.
Q: How long is a type test report valid?
A: Typically 3-5 years, unless the product design changes or applicable standards are revised. Guide 117 recommends reviewing type test validity whenever a relevant standard edition is updated.
A: Typically 3-5 years, unless the product design changes or applicable standards are revised. Guide 117 recommends reviewing type test validity whenever a relevant standard edition is updated.
