IEC 60794 vs. IEEE 1222: Which Standard Applies to Your ADSS Cable Project?

Your ADSS cable tender says “shall comply with applicable international standards.” Which one? IEC 60794 and IEEE 1222 are the two dominant standards — but they’re not interchangeable. Specifying the wrong one can mean your cable passes tests that don’t match your installation environment. This guide explains the difference and how to choose.

IEC 60794: The International Baseline

IEC 60794 covers optical fiber cables for outdoor applications. It specifies construction, mechanical testing (tensile, crush, impact, bend), environmental testing (temperature cycling, water penetration), and optical performance. IEC 60794 is the default standard in Europe, Africa, Asia, and most international projects.

Related Reading: IEC 60794 procurement guide · Voltage class selection

IEEE 1222: The North American Alternative

IEEE 1222 covers all-dielectric self-supporting fiber optic cables specifically for electric utility applications. It includes additional tests for tracking resistance and ozone exposure that IEC 60794 does not explicitly require. IEEE 1222 is commonly referenced in North American projects.

How to Choose

  • Projects in Europe, Africa, Asia, Middle East: Specify IEC 60794 as primary, with IEEE 1222 as supplementary if additional tracking tests are required.
  • Projects in North America: Specify IEEE 1222 as primary. Note that most international manufacturers test to IEC 60794 by default — request IEEE 1222 compliance explicitly.
  • International tenders with global bidders: Specify IEC 60794 and list additional IEEE 1222 tests as optional. This ensures maximum bidder participation.

Key Takeaways

  • IEC 60794 is the international default. IEEE 1222 is North America-specific.
  • IEEE 1222 adds tracking resistance and ozone tests not in IEC 60794.
  • Specify the standard that matches your project’s regulatory jurisdiction.

Writing an ADSS Tender?

We help procurement teams draft technically accurate specifications that reference the correct standards.

Request Specification Support →

Similar Posts