Every code and standard on this site is reviewed against a specific edition. This hub is where we make that review visible — what edition we track, when we last checked it, what changed from the previous edition, and exactly what that means for your drawings, calculations, and specifications.
How to use this page: each standard below links to a dedicated page with the edition we currently track, a summary of what changed versus the previous edition (in our own words — never reproduced from the standard itself), common jurisdiction adoption caveats, and a practical checklist of what to revisit in existing work. These are educational summaries, not a substitute for the official published standard or your local building department's amendments.
A code is a body of requirements meant to be adopted, as a whole, into law by a governing jurisdiction — a state, county, or city. Once adopted, it becomes legally enforceable, typically through a building permit and inspection process. The National Electrical Code (NFPA 70), the International Building Code, and the International Fire Code are all model codes: written by an organization, but with no legal force anywhere until a specific jurisdiction formally adopts a specific edition, often layering its own local amendments on top.
A standardis a documented, agreed-upon technical requirement, test method, or performance specification for a narrower scope — a material property, a design calculation method, a piece of equipment, or a work practice. A standard becomes enforceable only when something else — a code, a specification, a contract, or an insurer’s requirement — references or incorporates it. ASME BPVC, ASTM A992, and IEEE 1584 are all standards: technically authoritative on their own subject, but not law until something legally binding points to them.
A city adopts the International Building Code (a code) as its legal building code. The IBC, in turn, requires that structural concrete be designed per ACI 318 (a standard) and that structural steel meet ASTM A992 (another standard). Neither ACI 318 nor ASTM A992 was independently voted into law by the city — they became enforceable on that project the moment the IBC, which the city did adopt, pointed to them. This reference chain — a code pulling in dozens of standards by citation — is how almost every real construction project ends up legally bound by standards that were never separately adopted as law in their own right.
Codes exist primarily to protect public health, safety, and welfare — minimum requirements a jurisdiction has decided are non-negotiable for anyone building or operating within its authority.
Standards exist primarily so that engineers, manufacturers, and contractors working independently of each other produce compatible, predictable, comparable results — the same test method, the same material grade, the same design method.
A code is enforced by an Authority Having Jurisdiction (AHJ) — a building department, fire marshal, or similar official — through plan review, permitting, and inspection.
A standard is typically enforced by whoever specified it: an engineer's stamped drawing, a purchasing specification, an insurer's policy condition, or a code that cites it by reference.
When you hit a requirement in a project, it’s worth asking which kind of document it came from, because the answer changes what you do next. If it’s from an adopted code, the question is which edition and which local amendments your specific AHJ is enforcing — that is a jurisdiction question, not an engineering-judgment question, and the only reliable source is the AHJ itself. If it’s from a standard, the question is whether anything actually requires it on this project — a referencing code, a client specification, a professional obligation, or an insurer’s condition — and, if so, which edition that reference points to, since a standard can be revised on its own schedule independent of whatever code or contract cites it. Treating every requirement as if it were the same kind of document is how projects end up citing a standard’s superseded edition, or assuming a voluntary industry standard has the force of law when nothing on that specific project actually made it mandatory.
What changed for electricians, engineers, and inspectors — article-by-article, in plain language.
Fire-alarm design implications of the latest edition — initiating devices, notification, and signaling changes.
What changed for commercial HVAC design — envelope, equipment efficiency, and controls requirements.
Wind, seismic, snow, and load combination changes — what shifts in your structural design basis.
Updates for OT and industrial-control security — what changed for SCADA, PLC, and ICS network design.
Behind every code and standard is an organization that develops, maintains, and periodically revises it. This directory maps the standards-issuing bodies most relevant to each major engineering discipline, so you know where a given requirement actually originates and where to go for the authoritative source.
Important: the summaries below describe each organization's general scope and role in our own words — they are not excerpts or reproductions of any published standard, and organizations frequently update their scope, structure, and publications. Always consult the official standard or code, published directly by the issuing organization, before relying on it for a real design, submittal, or compliance decision, and confirm which edition your local authority having jurisdiction (AHJ) has adopted.
Each entry below names the organization’s most relevant published codes and standards for engineering practice, what each one is actually used for, and how engineers apply it in real design, review, or certification work — not just a one-line scope description.
Mobile telecommunications standards, including LTE and 5G.
Used for: The complete technical specification set defining how 4G LTE and 5G cellular networks operate — air interface, core network architecture, and device requirements.
How it’s used: Telecommunications and RF engineers designing cellular infrastructure, DAS (distributed antenna systems), or private 5G networks work from 3GPP release specifications to ensure equipment interoperability.
Highway and transportation infrastructure design standards.
Used for: The controlling design standard for highway bridges in the U.S. — load factors, live-load models (design truck/lane), and material-specific design provisions.
How it’s used: Bridge engineers design girders, decks, and substructures to its load-and-resistance-factor provisions; state DOTs require conformance for any bridge in the public highway system.
Used for: Geometric design criteria for roadways — lane widths, sight distance, horizontal/vertical curve design, and design speed relationships.
How it’s used: Civil and transportation engineers set roadway alignment, curve radii, and sight-distance requirements from its tables during roadway design.
Concrete design, materials, and construction practice standards.
Used for: The controlling design standard for reinforced concrete structures — flexural and shear design, reinforcement detailing, and development lengths.
How it’s used: Structural engineers design concrete beams, slabs, columns, and foundations to its strength-design provisions; the IBC directly references it by adoption.
Used for: A reference specification for concrete materials, mixing, placing, and finishing that can be incorporated by reference into project specs.
How it’s used: Structural engineers cite ACI 301 in project specifications rather than writing bespoke concrete-placement requirements for every project.
Performance and certification standards for HVACR equipment.
Used for: The standardized test procedure behind published SEER/SEER2, EER, and HSPF ratings for residential and light-commercial AC and heat pump equipment.
How it’s used: HVAC engineers select equipment by comparing AHRI-certified performance ratings across manufacturers, and code-mandated minimum efficiency requirements are stated in these same AHRI rating terms.
Used for: Standardized test conditions and rating procedure for water-cooled and air-cooled chillers.
How it’s used: Mechanical engineers compare chiller selections using AHRI-rated kW/ton efficiency values at standard conditions, ensuring an apples-to-apples comparison across vendors.
Chemical process safety and engineering practice guidance (e.g., CCPS).
Used for: Widely used process-safety-engineering guidance documents — inherently safer design, layer of protection analysis (LOPA), and process hazard analysis (PHA) methodology.
How it’s used: Process safety engineers structure PHA/HAZOP studies and LOPA safety-integrity determinations following CCPS methodology, which regulators (OSHA PSM, EPA RMP) recognize as good engineering practice.
Structural steel design, fabrication, and erection standards.
Used for: The controlling design specification for structural steel members and connections — allowable stress and LRFD design methods.
How it’s used: Structural engineers size steel beams, columns, and connections to its provisions, typically through the companion Steel Construction Manual's design tables.
Used for: Additional detailing and design requirements for steel structures in seismic design categories requiring ductile behavior.
How it’s used: Structural engineers on projects in higher seismic design categories apply its special moment-frame or braced-frame detailing requirements on top of the base AISC 360 design.
Coordinates and accredits U.S. voluntary consensus standards across industries.
Used for: A jointly ANSI/TIA-published standard for structured cabling in commercial buildings — cable categories, topology, and performance requirements.
How it’s used: Telecommunications designers specify Category 6/6A cabling and horizontal/backbone topology against it when designing a building's structured cabling infrastructure.
Used for: Performance and marking requirements for safety eyewear and face protection used in industrial and construction settings.
How it’s used: Safety and industrial engineers specify Z87.1-marked eyewear in PPE programs, and it's the reference OSHA points to for eye-protection compliance.
Used for: Safety requirements for specific classes of machine tools — guarding, control reliability, and risk assessment for equipment like presses, machining centers, and robots.
How it’s used: Manufacturing and industrial automation engineers perform a risk assessment against the relevant B11 standard for a given machine type to determine required guarding and safety-control-system category.
Used for: Safety rules for the installation, operation, and maintenance of electric supply and communication lines — the code utilities use for overhead and underground power lines, distinct from the NEC's premises-wiring scope.
How it’s used: Utility and power-distribution engineers design pole lines, clearances, and grounding for utility infrastructure to the NESC rather than the NEC, which stops at the utility service point.
Oil and gas equipment, process safety, and pipeline standards.
Used for: Design, fabrication, and inspection requirements for large, field-erected, welded steel storage tanks.
How it’s used: Process and mechanical engineers design tank shell thickness, foundation loading, and appurtenances to it for atmospheric and low-pressure storage tanks at refineries, terminals, and bulk plants.
Used for: In-service inspection intervals and repair/alteration criteria for API 650 tanks over their operating life.
How it’s used: Mechanical integrity engineers schedule tank inspections and evaluate corrosion/repair findings against its acceptance criteria to determine continued fitness for service.
Used for: In-service inspection, repair, and rerating requirements for process piping systems.
How it’s used: Mechanical integrity engineers at refineries and chemical plants use it to set piping inspection intervals and corrosion-rate-based remaining-life calculations.
Used for: Design and performance requirements for centrifugal pumps used in petroleum and petrochemical service, beyond typical commercial pump standards.
How it’s used: Process/mechanical engineers write pump procurement specs referencing API 610 for critical hydrocarbon service pumps where a standard commercial pump spec would be insufficient.
Structural and civil design load standards, including ASCE 7.
Used for: The controlling standard for structural design loads — dead, live, wind, snow, seismic, and flood loads, and how to combine them.
How it’s used: Structural engineers pull site-specific wind speed, seismic parameters, and snow load from its maps/tables as the starting input for every structural calculation on a project.
Used for: Design requirements for buildings in flood hazard areas — elevation requirements, flood-resistant materials, and foundation design in flood zones.
How it’s used: Structural and civil engineers on coastal or floodplain sites use it to set minimum finished-floor elevation and select flood-resistant construction methods below the design flood elevation.
Used for: Performance-based methodology for evaluating and retrofitting existing buildings for seismic performance.
How it’s used: Structural engineers evaluating an older building for a seismic retrofit or change of use follow its nonlinear analysis and performance-level procedures rather than designing it as new construction.
HVAC, refrigeration, and building energy performance standards.
Used for: Minimum energy-efficiency requirements for commercial buildings — envelope performance, HVAC equipment efficiency, and lighting power density.
How it’s used: Mechanical and energy-modeling engineers demonstrate a building design meets or beats its baseline through prescriptive compliance or whole-building energy modeling, often required for a building permit or LEED credit.
Used for: Minimum outdoor-air ventilation rates for commercial and institutional buildings, by occupancy and space type.
How it’s used: HVAC engineers size outdoor-air intake and calculate ventilation rates per its occupancy-based tables during load calculations, feeding directly into air handler sizing.
Used for: Safety requirements for refrigeration systems by refrigerant classification — machine room ventilation, refrigerant quantity limits, and detection/alarm requirements.
How it’s used: Mechanical engineers designing refrigeration or large chiller plants size machine-room ventilation and specify refrigerant monitoring/alarm systems to its requirements based on the refrigerant's safety group.
Used for: Defines the combinations of temperature, humidity, and air speed that constitute an acceptable indoor thermal comfort range.
How it’s used: HVAC engineers use its comfort-zone charts to set design setpoints and to document that a space design falls within an acceptable comfort range, sometimes for LEED comfort credits.
Used for: Ventilation, pressure-relationship, and air-change-rate requirements specific to hospitals and outpatient facilities, by room type (OR, isolation room, etc.).
How it’s used: Healthcare HVAC engineers set air-change rates and pressure relationships (positive/negative) per its room-by-room table, which most healthcare facility codes explicitly reference as mandatory.
Mechanical engineering, pressure vessel, piping, and equipment standards.
Used for: The controlling design, fabrication, and inspection standard for boilers and pressure vessels in the U.S. — covers material selection, wall-thickness calculations, welding qualification, and inspection.
How it’s used: Pressure vessel and process engineers design vessel wall thickness and nozzle reinforcement to its formulas, and fabricators must hold an ASME "U" stamp certification to legally build code vessels.
Used for: Design, materials, and fabrication requirements for piping systems — B31.1 for power/utility piping, B31.3 for process piping in chemical and industrial plants.
How it’s used: Piping engineers calculate wall thickness, flexibility (thermal expansion), and support spacing to the applicable B31 code section for the specific service (steam, process fluid, etc.).
Used for: The geometric dimensioning and tolerancing system used on mechanical engineering drawings to specify allowable variation in part form, size, and location.
How it’s used: Mechanical designers apply GD&T symbols and tolerance zones to a drawing so manufacturing and quality inspection have an unambiguous, measurable definition of an acceptable part.
Used for: Design and safety requirements for elevators, escalators, and moving walks — car safety devices, hoistway construction, and emergency operation.
How it’s used: Elevator consultants and building engineers design hoistway dimensions, machine room requirements, and life-safety interfaces (fire alarm recall) to it, and it's enforced by elevator inspectors.
Product performance standards for plumbing safety devices (backflow preventers, etc.).
Used for: Performance and testing requirements for reduced-pressure-principle backflow preventers, used to protect potable water from contamination.
How it’s used: Plumbing engineers specify ASSE 1013-listed backflow preventers on domestic water service entrances and irrigation connections per local health-department requirements.
Used for: Performance requirements for thermostatic mixing valves that limit hot water temperature at fixtures to prevent scalding.
How it’s used: Plumbing engineers specify ASSE 1070-listed mixing valves at lavatories and showers in codes/occupancies (schools, healthcare) requiring scald protection.
Material property, test method, and product specification standards across nearly every discipline.
Used for: Chemical composition and mechanical property requirements for structural steel shapes and plate (A992 for wide-flange shapes, A36 for plate and general structural steel).
How it’s used: Structural engineers call out the specific ASTM steel grade on drawings, since a member's yield strength (used throughout the AISC design calculations) is defined by which ASTM spec it's ordered to.
Used for: The standardized furnace test that produces a building assembly's fire-resistance rating (1-hour, 2-hour wall/floor assemblies, etc.).
How it’s used: Architects and fire protection engineers select wall, floor, and door assemblies with an ASTM E119-tested (or UL-tested to the same method) fire rating that satisfies the IBC's required fire-resistance rating for that condition.
Used for: Material and dimensional specifications for PVC piping used in plumbing, irrigation, and drainage.
How it’s used: Plumbing and civil engineers specify PVC pipe by ASTM schedule/class designation to ensure pressure rating and dimensional compatibility with fittings.
Used for: Material-quality requirements for aggregate (C33) and Portland cement (C150) used in structural concrete mix designs.
How it’s used: Structural and materials engineers reference these when approving a concrete mix design submittal, ensuring the raw materials meet the quality basis ACI 318's strength design assumed.
Welding procedure, qualification, and inspection standards.
Used for: Welding procedure qualification, welder qualification, and inspection acceptance criteria for structural steel welding.
How it’s used: Structural and fabrication engineers require welders to hold AWS D1.1 qualification and inspectors to use its acceptance criteria (visual, and referenced NDT methods) for structural steel welds.
Used for: Welding requirements specific to highway bridge structures, typically more stringent than D1.1 for fatigue-critical members.
How it’s used: Bridge and transportation structural engineers specify D1.5 rather than D1.1 for bridge welds subject to cyclic loading and fatigue considerations.
Drinking water treatment, storage, and distribution standards.
Used for: Procedures for disinfecting new and repaired water mains before they're placed into service.
How it’s used: Civil/utility engineers and contractors follow its chlorination and bacteriological-testing procedure before a new water main is connected to an active distribution system.
Used for: Material, dimensional, and pressure-rating specifications for PVC pipe used in municipal water distribution.
How it’s used: Civil engineers specify AWWA C900/C905 class ratings for buried water main pipe sizing on utility drawings, distinct from the ASTM specs used for plumbing-scale PVC.
ICT and structured cabling design and installation best practices.
Used for: A comprehensive best-practices reference for designing and installing telecommunications and structured cabling infrastructure across an entire facility.
How it’s used: RCDD-credentialed (Registered Communications Distribution Designer) engineers use it as their primary design reference when scoping and specifying a building's complete ICT infrastructure.
Property-loss-prevention testing and certification, notably for fire protection equipment.
Used for: Loss-prevention engineering guidance covering fire protection, natural hazards, and equipment protection — often more stringent than minimum code.
How it’s used: Fire protection engineers on FM-insured facilities design sprinkler density and storage-commodity classification to FM Data Sheet requirements, which can exceed NFPA 13 minimums as an insurer condition.
Used for: Third-party testing and listing of fire protection and building products (similar in concept to a UL listing, run by a different certifying body).
How it’s used: Specifying engineers on FM-insured projects require "FM Approved" (not just UL Listed) products for certain fire protection equipment, since FM Global's own insurance underwriting requires it.
Publishes the Uniform Plumbing Code and related mechanical standards.
Used for: A model plumbing code — an alternative to the ICC's International Plumbing Code, adopted in different jurisdictions (notably much of the western U.S.).
How it’s used: Plumbing engineers need to know which of the two model codes (UPC or IPC) their jurisdiction has adopted, since fixture-unit tables and venting requirements differ between them.
Used for: A model mechanical code, IAPMO's counterpart to the ICC's International Mechanical Code.
How it’s used: Mechanical engineers in UMC-adopting jurisdictions design ventilation and equipment installations to its provisions instead of the IMC.
Model building, residential, fire, and plumbing codes adopted by U.S. jurisdictions.
Used for: The model building code most U.S. jurisdictions adopt (with amendments) as their base building code — occupancy classification, construction type, fire-resistance ratings, and structural-code cross-references.
How it’s used: Architects and engineers determine occupancy group and construction type early in design, since nearly every other code requirement (egress, fire rating, allowable area) flows from those two IBC classifications.
Used for: A stand-alone code for one- and two-family dwellings and townhouses, covering structural, mechanical, electrical, and plumbing provisions in one combined document.
How it’s used: Residential designers and builders work directly from the IRC rather than the IBC/NEC/IMC/IPC separately, since it's written as a simplified, prescriptive single-family code.
Used for: Model code for HVAC and mechanical systems — equipment installation, ventilation, and exhaust requirements.
How it’s used: Mechanical engineers design ventilation and equipment installations to satisfy the IMC as adopted locally, working alongside ASHRAE 62.1 which the IMC often references for ventilation rates.
Used for: Model code for water supply, drainage, and venting systems in buildings.
How it’s used: Plumbing engineers size fixture units, drainage, and venting to it (or to the competing Uniform Plumbing Code, depending on jurisdiction).
Used for: Model code addressing fire prevention and life safety in existing and new buildings — fire department access, hazardous materials storage, and fire protection system maintenance.
How it’s used: Fire protection engineers and AHJs use it alongside NFPA standards for ongoing fire-safety compliance, fire department access/water supply requirements, and hazmat storage limits.
International standards for electrical, electronic, and related technologies.
Used for: The international counterpart to the NEC — wiring rules, protection against electric shock, and installation requirements for low-voltage electrical systems, used throughout Europe and much of the rest of the world.
How it’s used: Electrical designers on non-U.S. projects size circuits and protection devices to it instead of the NEC; multinational firms need to know which of the two a given project falls under.
Used for: A standardized communication protocol and data model for substation automation — how protective relays, IEDs, and SCADA systems exchange data.
How it’s used: Substation and protection engineers specify IEC 61850-compliant relays and configure their communication mapping so devices from different manufacturers interoperate on the same substation network.
Used for: The base functional-safety standard behind Safety Integrity Levels (SIL) for safety-instrumented systems in industrial process control.
How it’s used: Process safety and controls engineers use it to determine the required SIL for a safety function (e.g., an emergency shutdown loop) and to select certified hardware that meets that SIL.
Used for: Cybersecurity requirements for industrial automation and control systems (IACS) — network zoning/segmentation, security levels, and secure product development lifecycle.
How it’s used: OT/ICS security engineers use its zone-and-conduit model to segment a plant network and assign target security levels to each zone, then select equipment certified against its component requirements.
Used for: Design verification and testing requirements for low-voltage switchboards and motor control center assemblies.
How it’s used: Switchgear manufacturers and panel builders verify a design to it (by test or by calculation) before labeling an assembly as compliant, and specifying engineers reference it in switchgear procurement specs.
Electrical, electronics, and communications engineering practice standards.
Used for: The engineering calculation method behind an arc-flash study — incident energy and arc-flash boundary as a function of system voltage, bolted fault current, and clearing time.
How it’s used: Power system engineers feed one-line diagram and protective-device coordination data into its equations (or arc-flash software implementing them) to produce the incident-energy values that ultimately drive NFPA 70E PPE labeling.
Used for: Limits on harmonic voltage and current distortion at the point of common coupling between a facility and the utility grid.
How it’s used: Power quality engineers evaluate a facility's nonlinear loads (VFDs, UPS systems, rectifiers) against its distortion limits and specify harmonic filters or mitigation when a design would otherwise exceed them.
Used for: Design, testing, and application requirements for power and distribution transformers — loading guides, insulation levels, and test procedures.
How it’s used: Substation and power engineers use it to select transformer ratings, insulation class, and loading limits, and to specify factory acceptance test requirements in procurement documents.
Used for: The physical- and data-link-layer specifications behind wired Ethernet (802.3) and Wi-Fi (802.11) networking.
How it’s used: Network and telecommunications designers reference these to select cabling categories, switch port speeds, and wireless access point specifications that guarantee interoperability across vendors.
Used for: Technical requirements for connecting distributed generation (solar PV, battery storage, backup generation) to the utility grid — voltage/frequency ride-through, anti-islanding, and protection settings.
How it’s used: Solar and power-systems engineers design grid-interconnection protection schemes to it, and utilities require conformance as a condition of approving an interconnection application.
Internet protocol standards (TCP/IP, DNS, and related RFCs).
Used for: The core specifications defining how packets are addressed and routed across IP networks.
How it’s used: Network engineers design IP addressing schemes and subnetting following these specifications for both legacy IPv4 and newer IPv6 network designs.
Used for: The protocol standard for automatic IP address assignment on a network.
How it’s used: Network engineers configure DHCP servers and scopes conforming to this RFC when designing automatic address assignment for a facility network.
Printed circuit board and electronics assembly standards.
Used for: Baseline PCB design rules — trace spacing, current-carrying capacity, and via requirements.
How it’s used: PCB layout engineers use its current-vs-trace-width charts to size copper traces for a given current and temperature rise before routing a board.
Used for: The most widely used workmanship standard for inspecting soldered electronic assemblies — defines what counts as an acceptable vs. defective solder joint or component placement.
How it’s used: Electronics manufacturers and quality inspectors reference its class-based (Class 1/2/3) acceptance criteria to accept or reject assembled boards during inspection.
Used for: Soldering process requirements — materials, methods, and verification criteria for producing the assemblies IPC-A-610 later inspects.
How it’s used: Manufacturing engineers set up and qualify a soldering process (reflow profile, flux selection) against it, often as a prerequisite to J-STD-001 operator certification.
Industrial automation, process control, and instrumentation standards.
Used for: The standardized symbol and tag-numbering system used on Piping and Instrumentation Diagrams (P&IDs) — how a transmitter, valve, or controller is drawn and tagged.
How it’s used: Instrumentation and controls engineers use its symbol library and tag-numbering convention (e.g., FT-101 for a flow transmitter) so P&IDs are readable consistently across a project and industry.
Used for: The process-industry-specific application of functional safety (SIL) concepts to safety instrumented systems (SIS) — emergency shutdown and safety interlock design.
How it’s used: Process safety engineers perform a SIL determination (via LOPA or similar) and design the safety instrumented function's sensor/logic-solver/final-element architecture to meet that target SIL.
Used for: A lifecycle framework for designing, rationalizing, and managing process-control alarm systems to avoid alarm flooding and nuisance alarms.
How it’s used: Controls engineers run an alarm rationalization exercise against its methodology to set priority, setpoints, and suppress redundant alarms in a DCS/SCADA system.
Industrial automation and control systems (OT) cybersecurity standards.
Used for: Defines system-level security requirements and the security-level (SL 1-4) target framework for industrial automation and control systems.
How it’s used: OT security engineers assign target security levels to network zones and verify that the deployed architecture meets each zone's SL-T requirements.
Used for: Component-level security requirements for individual devices (PLCs, HMIs, network equipment) used in industrial control systems.
How it’s used: Equipment vendors certify individual components against 62443-4-2, and OT engineers specify certified components when procuring new control-system hardware.
International standards spanning quality, environmental, safety, and industry-specific practice.
Used for: A generic quality-management-system framework applicable to any organization — document control, corrective action, and continual improvement processes.
How it’s used: Manufacturing and engineering firms certify their quality management system to ISO 9001, often a prerequisite for being an approved supplier to larger customers.
Used for: A framework for managing an organization's environmental impact and regulatory compliance obligations.
How it’s used: Facilities and engineering firms implement and certify an EMS to it as part of corporate sustainability programs or customer/contract requirements.
Used for: A framework for establishing, implementing, and maintaining an information security management system.
How it’s used: IT and OT security teams certify against it to demonstrate a structured security program, often required by enterprise customers or cyber-insurance underwriters.
Used for: A quality-management-system standard specific to the design and manufacture of medical devices.
How it’s used: Medical device engineering firms certify to it as part of the regulatory pathway (alongside FDA requirements) for bringing a device to market.
Used for: Functional-safety lifecycle requirements for electrical/electronic systems in production automobiles — the automotive-specific version of the IEC 61508 functional-safety concept.
How it’s used: Automotive electronics engineers determine an Automotive Safety Integrity Level (ASIL) for a vehicle function and design the hardware/software to meet that ASIL's process and architectural requirements.
Joint international information-technology and security standards, e.g. ISO/IEC 27001.
Used for: The internationally recognized certifiable standard for an information security management system.
How it’s used: Organizations pursue ISO/IEC 27001 certification to demonstrate a structured security program to customers, partners, and regulators — often required in enterprise vendor-risk assessments.
Used for: A standard for IT service management systems, covering how IT services are planned, delivered, and improved.
How it’s used: IT service organizations certify against it to formalize and benchmark their service-management processes, similar in spirit to ITIL but as a certifiable standard.
Global telecommunications and radio-spectrum coordination standards.
Used for: International specifications for optical fiber characteristics and transmission performance used in telecommunications and long-haul networking.
How it’s used: Telecommunications engineers select fiber types (single-mode/multimode) and design link budgets referencing these specifications for long-distance or carrier-grade fiber runs.
Used for: International coordination of radio-frequency spectrum use across countries, preventing cross-border interference.
How it’s used: RF and radio-communications engineers check ITU-R regional spectrum allocations (alongside national regulators like the FCC) before designing equipment for a given frequency band.
Semiconductor device and memory standardization.
Used for: Electrical and timing specifications for DDR memory generations (DDR4, DDR5) — pinout, signaling, and timing parameters.
How it’s used: Hardware and PCB engineers design memory-interface routing and timing budgets against the relevant JESD79 revision to ensure a board works with standard, interchangeable memory modules.
Used for: A family of standardized reliability and environmental stress tests for semiconductor components — thermal cycling, humidity, ESD.
How it’s used: Component and product-qualification engineers run JESD22 test procedures on new semiconductor parts to validate reliability before design-in.
Manufacturing and performance standards for electrical equipment.
Used for: Defines the NEMA enclosure-type rating system (NEMA 1, 3R, 4, 4X, 12, etc.) describing an enclosure's protection against dust, water, and corrosion.
How it’s used: Electrical and controls engineers specify a NEMA rating for panels and enclosures based on the installation environment — NEMA 4X for a washdown food-processing area, NEMA 3R for outdoor equipment.
Used for: Performance, dimensional, and testing standards for AC and DC electric motors and generators — frame sizes, efficiency classes, and service-factor definitions.
How it’s used: Mechanical and electrical engineers select motors by NEMA frame size and design letter (B, C, D) to ensure physical and electrical interchangeability across manufacturers.
Used for: Performance and rating standards for motor starters, contactors, and overload relays used in industrial control panels.
How it’s used: Controls engineers size motor starters and overload relays to NEMA size ratings (NEMA size 1, 2, 3...) when the design calls for NEMA-rated rather than IEC-rated control components.
Fire, electrical, and life-safety codes such as NFPA 70 (NEC) and NFPA 72.
Used for: The baseline safety code for essentially all electrical wiring, equipment, and installation practice in the U.S. — conductor sizing, overcurrent protection, grounding and bonding, and equipment-specific rules for everything from dwellings to industrial plants.
How it’s used: Electrical engineers and designers size circuits, panels, and services to its tables and rules; electricians install to it; inspectors enforce whatever edition the local jurisdiction has adopted (often with amendments). It is revised on a 3-year cycle.
Used for: Design, installation, and testing requirements for fire alarm and signaling systems — detector spacing, notification appliance coverage (audible/visible), circuit survivability, and system testing intervals.
How it’s used: Fire alarm designers use its detector-spacing and notification-coverage tables to lay out devices on floor plans; technicians follow its inspection and testing schedules for ongoing code-required maintenance.
Used for: Design and installation requirements for automatic fire sprinkler systems — hazard classification, hydraulic calculation methods, and sprinkler spacing/coverage.
How it’s used: Fire protection engineers classify the occupancy hazard, then hydraulically calculate pipe sizing and sprinkler density against its design-area tables to produce a stamped sprinkler drawing set.
Used for: Means-of-egress, occupant load, and general fire-safety requirements for buildings, organized by occupancy type — assembly, business, healthcare, and more.
How it’s used: Architects and fire protection engineers calculate occupant load and required egress width/travel distance from it during early design, since it directly drives stair, corridor, and exit-door sizing.
Used for: Workplace electrical safety practice — arc-flash risk assessment, required PPE categories, and safe work procedures around energized equipment.
How it’s used: Facilities perform an arc-flash study against it to generate equipment labels showing incident energy and required PPE category before anyone works on or near that equipment energized.
U.S. federal standards body; publishes the Cybersecurity Framework and measurement standards.
Used for: A risk-based framework (Identify, Protect, Detect, Respond, Recover) for organizing an organization's cybersecurity program, including OT/ICS environments.
How it’s used: Security engineers and CISOs map existing controls against its five functions to identify gaps and prioritize a cybersecurity roadmap, often as the top-level framework tying together more prescriptive standards like IEC 62443.
Used for: A detailed catalog of security controls used primarily for U.S. federal information systems and increasingly by private-sector compliance programs.
How it’s used: Security engineers on federal or federally-adjacent projects select and implement controls from its catalog to satisfy FISMA or contractual security requirements.
Used for: Security guidance specific to industrial control systems and OT environments, addressing the ways OT security differs from conventional IT security.
How it’s used: OT/ICS security engineers use it alongside IEC 62443 as guidance for securing SCADA, DCS, and PLC-based control networks without disrupting real-time control functions.
Aviation and aerospace systems standards, notably software/hardware assurance (DO-178C, DO-254).
Used for: The standard aviation regulators (FAA, EASA) recognize for certifying software used in airborne systems, tied to a Design Assurance Level (DAL) based on failure-condition severity.
How it’s used: Avionics software engineers develop and verify software following its DAL-specific process objectives, producing the certification evidence required for FAA/EASA approval.
Used for: The hardware counterpart to DO-178C — design assurance requirements for complex airborne electronic hardware (FPGAs, ASICs, custom circuit boards).
How it’s used: Avionics hardware engineers apply its design-assurance-level process to custom hardware design and verification as part of the same airborne-system certification package.
Automotive, aerospace, and commercial vehicle engineering standards.
Used for: The CAN-bus-based communication protocol used across heavy-duty vehicle and off-highway equipment networks — engine, transmission, and body-control-module data.
How it’s used: Automotive and off-highway electronics engineers implement J1939-compliant messaging so ECUs from different suppliers can share data on the same vehicle network.
Used for: The aerospace-industry-specific quality-management-system standard, built on ISO 9001 with additional aerospace requirements (configuration management, first-article inspection).
How it’s used: Aerospace manufacturers and their suppliers certify to AS9100 as a near-universal prerequisite for supplying parts into the commercial or defense aerospace supply chain.
Used for: Grade classification (Grade 5, Grade 8, etc.) defining the material and mechanical properties of bolts and threaded fasteners.
How it’s used: Mechanical engineers specify fastener grade on drawings to ensure the correct strength class is used in a bolted-joint calculation.
Ductwork construction and installation standards.
Used for: Duct gauge, reinforcement, and joint-construction requirements by duct pressure class (low, medium, high pressure).
How it’s used: Mechanical engineers specify a SMACNA pressure classification on drawings, and duct fabricators build to its gauge/reinforcement tables for that pressure class rather than re-engineering each duct run from scratch.
Used for: Construction standards for heavier-duty industrial exhaust and process ductwork beyond typical commercial HVAC pressure classes.
How it’s used: Industrial ventilation engineers reference it for process exhaust systems handling higher pressures, temperatures, or corrosive airstreams than standard commercial ductwork.
Structured cabling and telecommunications infrastructure standards.
Used for: Cable category performance requirements and structured-cabling topology for commercial buildings — the same standard co-published with ANSI, above.
How it’s used: Structured cabling designers use it to select cable category and design horizontal/backbone cabling topology, patch panel layout, and telecom room sizing.
Used for: Design requirements for the physical spaces (telecom rooms, cable pathways, conduit sizing) that house structured cabling infrastructure.
How it’s used: Telecommunications and architectural designers size telecom/IDF room dimensions and cable-tray/conduit fill from its requirements during building design.
Used for: Data center infrastructure design — tiered redundancy classification (comparable in concept to the Uptime Institute's Tier system), cabling, and physical security.
How it’s used: Data center designers use its tiered-redundancy framework and cabling/pathway requirements when scoping a new data center or colocation facility's infrastructure.
Product safety testing, certification, and listing standards.
Used for: Construction and evaluation requirements for industrial control panels — wire sizing, short-circuit current rating (SCCR), component spacing, and marking.
How it’s used: Panel shops build and label control panels to UL 508A so the finished panel can carry a UL listing mark, which many AHJs and end customers require before a panel can be energized.
Used for: Safety and performance testing for molded-case circuit breakers, including their interrupting rating.
How it’s used: Electrical engineers select breakers with a UL 489 interrupting (AIC) rating that meets or exceeds the calculated available fault current at that point in the system.
Used for: Safety and performance testing for surge protective devices (SPDs) — the same listing the 2023/2026 NEC now requires for new dwelling-unit services.
How it’s used: Electrical designers specify a UL 1449-listed SPD, Type 1 or Type 2 as applicable, at the service equipment to satisfy NEC 230.67.
Used for: A flammability-rating classification for plastics (V-0, V-1, V-2, HB) used in electronic and electrical products.
How it’s used: Electronics and product designers select enclosure and PCB materials rated to a specific UL 94 class to meet the fire-safety requirements of the end product's overall UL listing.
Used for: Safety requirements for information-technology and audio/video equipment — the standards behind most consumer and IT-equipment safety certification (62368-1 has superseded 60950-1).
How it’s used: Electronics manufacturers design and test products to it before they can bear a UL safety mark for sale in the U.S. market.
Codes and standards are revised on a cycle, and a design that was compliant under one edition can be non-compliant — or simply out of date — under the next. Every calculator, article, and design tool on this site is written against a specific edition, and that edition eventually changes. Rather than leaving that invisible, this page tracks it directly: what we currently reference, when we last reviewed it against the newest publication, and — critically — what practically changes for someone doing real design work. Jurisdictions adopt code editions on their own timelines and often layer local amendments on top, so always confirm the edition and any local amendments in effect with your local authority having jurisdiction (AHJ) before relying on any specific value for a real project.