Standards that shape ICT design: TIA, ISO/IEC, CSA and NFPA

In September, the Harbourview project's owner sends Lakehead Signal a forty-page document called ICT Design Standards. Daniel reads it with growing confusion. One page requires compliance with ANSI/TIA-568, another with CSA T529, a third with ISO/IEC 11801 for a lab used by an international research partner, and the electrical section refers to the Canadian Electrical Code. 'Which one wins?' he asks. Roz smiles. 'That's the right question, and the answer is almost never one of them. They each cover different things, and the design has to satisfy all the ones that apply.' This lesson introduces the main families of standards that shape ICT design, what each family covers and how they relate to one another.

This lesson cites standards by number and subject only. It does not reproduce their text or tables. Standards are revised regularly, and the edition in force for a project is the one named in the project documents or adopted by the authority having jurisdiction, so always check which edition applies.

What a standard is

A standard is a document, developed by consensus through a recognized process, that sets out requirements, specifications or guidance for products, processes or systems. In ICT infrastructure, standards define things such as cabling performance categories, maximum lengths, the size and features of telecommunications spaces, pathway design, labelling schemes, bonding systems and test procedures. They let products from different manufacturers work together and let owners specify performance without dictating a particular brand.

Standards are voluntary in themselves. They become mandatory when a code adopts them by reference, when a contract or specification requires them, or when an owner's own standards make them a condition of a project. That is why the owner's document Daniel received matters: by naming particular standards, it turns them into contractual requirements for the Harbourview design.

The TIA family

The Telecommunications Industry Association develops the ANSI/TIA standards used most widely in North America. They are written by engineering committees made up of manufacturers, designers, installers, owners and testing companies, and approved through a process accredited by the American National Standards Institute. The most important for an RCDD form a family that covers the whole infrastructure.

The 568 series deserves special attention because so much of the exam and of daily design depends on it. It is divided into parts: a generic part that sets out principles common to all premises, a part for commercial buildings, and parts for balanced twisted-pair cabling and components, optical fibre cabling and components, and other media. It defines the cabling subsystems, the recognized media, the maximum lengths for horizontal and backbone cabling and the transmission performance categories that cable, connectors and installed links must meet. Later courses in this program study it in depth.

The TIA family is organized by function. One standard covers cabling, another the spaces and pathways that hold it, another the labels and records, another the bonding. Premises-specific standards for data centres, healthcare, education and homes then adapt the general rules to particular building types. This modular structure is also reflected in the TDMM.

The ISO/IEC family

Internationally, cabling standards are developed by a joint technical committee of the International Organization for Standardization and the International Electrotechnical Commission, known as ISO/IEC JTC 1. Its main cabling standard is the ISO/IEC 11801 series, which covers generic cabling for customer premises and is divided into parts for offices, industrial premises, homes, data centres and distributed building services. Installation, administration and testing are covered by the ISO/IEC 14763 series, among others.

ISO/IEC and TIA standards cover much the same ground, but they use different terms and sometimes different structures. For example, ISO/IEC describes performance as classes for installed cabling and categories for components, while TIA uses categories for both. ISO/IEC names cabling subsystems by distributors, such as floor distributor and building distributor, where TIA uses terms based on spaces and cross-connects. An RCDD working with international clients, or with equipment and manufacturers from outside North America, needs to translate between the two.

CSA standards in Canada

In Canada, CSA Group develops national standards, many of which are accredited by the Standards Council of Canada as National Standards of Canada. For ICT cabling, CSA publishes a series of telecommunications standards, often referred to as the T500 series, that are closely harmonized with the TIA documents. For example, CSA T529 has covered commercial building cabling in parallel with TIA-568, and CSA T530 pathways and spaces in parallel with TIA-569. Canadian owners and governments may specify either the CSA or the TIA document, and many designers cite both. CSA Group also publishes the Canadian Electrical Code, Part I (CSA C22.1), which provinces adopt with their own amendments and which contains rules for communications systems, as lesson 8 explains. Harmonization is close but not always exact, and CSA and TIA editions are not always published at the same time, so check both when a project cites them.

NFPA codes and standards

The National Fire Protection Association is best known in ICT for NFPA 70, the National Electrical Code, which covers the safe installation of electrical and communications wiring in the United States. Its chapter on communications systems sets rules for the listing, installation and protection of communications cables, including requirements based on where cables run, such as plenums and risers. NFPA also publishes NFPA 72, the National Fire Alarm and Signaling Code, which affects how fire alarm and emergency communications systems use building infrastructure, and NFPA 75 and 76, which address the protection of information technology equipment and telecommunications facilities.

For Canadian designers, NFPA documents matter mainly when an owner, insurer or international client cites them, or when a facility follows NFPA 75 for its IT rooms. Electrical safety in Canada is governed by the Canadian Electrical Code rather than NFPA 70, and fire alarm systems by Canadian standards referenced in the National Building Code and provincial building codes.

Application standards: IEEE

The standards above define the infrastructure. Application standards define what runs on it. The IEEE 802.3 family defines Ethernet, from older speeds up to multi-gigabit and beyond, and includes the power over Ethernet amendments that deliver increasing amounts of power over balanced twisted-pair cabling. IEEE 802.11 defines wireless LANs. When the IEEE defines a new application, the cabling standards respond: they may define new performance categories, set new limits on cable bundling to control heat from power delivery, or add guidance on how wireless access points should be cabled. An RCDD should understand which cabling supports which application, and why.

How standards fit together

No single standard covers a whole project. A design for the Harbourview Centre will use the cabling standards for its horizontal and backbone systems, the pathways and spaces standard for its rooms and risers, the administration standard for labelling, the bonding standard for its grounding system, the healthcare standard for clinic areas, the education standard for classrooms and the outside plant standard for the link to the existing building, all within the limits of the electrical and building codes in force. When two documents differ, the designer usually satisfies the stricter one, unless the code or the contract says otherwise, and records the decision.

How standards are developed

Understanding how standards are made helps a designer read them well. Standards developers such as TIA and CSA work through committees of volunteers from manufacturers, designers, contractors, owners, test equipment companies and other interested parties. A proposal for a new standard or revision is drafted by a working group, circulated for comment, revised in response to comments and balloted by committee members. Consensus does not mean unanimity, but it does mean that objections have been considered and answered. Accredited processes require balance among interest groups so that no single group, such as manufacturers, can dominate.

This process has practical consequences. Standards tend to describe minimum requirements that the committee could agree on, which is why owners often add stricter requirements in their own design standards. Standards also lag technology slightly, because consensus takes time; a new product may appear on the market before the standards describe how to install or test it. And standards often include informative annexes, which give guidance but are not requirements, alongside normative content, which is mandatory for compliance. A careful designer notes which parts of a standard are normative before citing them in a specification.

Daniel discovers that one of the engineers at a firm he worked with in Thunder Bay has served on a CSA telecommunications committee for years. Over coffee, she explains how a single clause about patch cord lengths took three meetings and two ballots to settle. 'When you read a standard,' she tells him, 'remember that every sentence was argued over. If it says should rather than shall, that was a deliberate choice.'

Owner design standards

Large owners such as universities, hospital systems, governments and corporations often publish their own ICT design standards, like the document Daniel received for the Harbourview project. These documents usually adopt industry standards by reference and then add owner-specific requirements: preferred cable categories, outlet counts per room type, labelling formats compatible with the owner's records system, approved manufacturers, room layouts and testing procedures. For the designer, the owner's standard is usually the most specific and most binding document on the project, because the contract requires it. Read it first, note every requirement that is stricter than the industry standards, and ask the owner about any requirement that seems to conflict with a code.

Keeping track of editions

Standards are reviewed and revised on regular cycles, usually every five years or so, and amendments or addenda may be issued in between. A project should state which editions apply. If the project documents say only 'the latest edition', that can cause disputes when a new edition appears during construction. Good practice is to name the edition, or to state that the edition current at the date of the contract applies.

On the exam, questions are based on the standards as reflected in the TDMM edition used for the exam. In practice, you should check the edition actually in force. Subscriptions to standards services, membership in standards committees and continuing education help RCDDs keep track. Many RCDDs volunteer on TIA, CSA or ISO/IEC committees, which is both a service to the industry and a good way to understand where the requirements come from.