This Page is devoted to the 2002 National
Electrical Code Changes
National Electrical Code Changes
Terms and Definitions
Luminaire: Action taken by affected Code-Making Panels and the NEC Technical
Correlating Committee resulted in the acceptance of the term “luminaire”
as a replacement of the terms “lighting fixture,” “lighting
fixtures,” and “fixture” in appropriate locations
in the Code. The term “fixture” has many other uses than
that of describing a complete lighting unit. The term luminaire”
is used in both national and international product standards. The NEC
is an international electrical code and as such, it is appropriate to
use this internationally recognized term. In an effort to make the conversion
easier, the word “fixture” or “fixtures” will
follow the term “luminaire” in parentheses. The definition
of “luminaire” is also being added to Article 100. Proposal
1-1, ROP p. 1
Style and Layout
Summary of the Change: The NEC Style Manual now encourages code-making
panels to use parallel numbering in articles. Parallel numbering means
that certain numbered sections in articles of the Code have been assigned
to cover the same type of material in each article where applicable.
The 1999 use of the dash (-) separator in the Section and below number
has been replaced with a dot (.).
Example:
320 Armored Cable
320.1 Scope
320.2 Definitions
320.10 Uses Permitted
Analysis of the Change:
This change is the result of work done by the Technical Correlating
Committee Usability Task Group. Common types of rules or information
have been assigned the same numbered section in each article. As an
example, article scopes have been designated as “.1” and
definitions for the specific article have been assigned as “.2”.
This will help users of the Code locate this type of common material
without having to search for it in different locations in each article.
Most sections are not common in all articles and are not affected by
this new style rule.
We Thought You Might Like To Know:
How Does the Code Change Process Work?
Step 1. Proposal Submittal Phase
Call For Proposal ( Lasts 21 Weeks)
Code Making Panel (CMP) Meetings (Last 12 Weeks)
CMP Votes on Proposals by Letter Ballot (Lasts 9 Weeks)
The possible results:
Accept (Takes a 2/3 panel member Agreement)
Agree in Principle (Sent back to CMP for rewording or rework)
Reject (Can be reintroduced or appealed)
CMP Writes Report of Proposals (ROP) This includes decisions on all
proposals
submitted.
CMP sends out ROP to Public for Comments (Lasts 19 Weeks)
Step 2. Report on Comments Phase
CMP receives and reviews comments from public (Lasts 11 Weeks)
CMP Votes on Comments by Letter Ballot (Last 9 Weeks)
The possible results are:
Accepted As is (take 2/3 eligible members acceptance)
Accept in Principle (Supplement Report Back to CMP) (takes 6 Weeks)
and it can move forward if reworked and Approved
Rejected
Supplemental Report moves Moved into ROC (Takes 6 Weeks)
CMP Writes Report of Comments (ROC)
Step 3. The Association Meeting Phase
The Proposed and Reviewed Favorably Change is sent th the Annual or
Fall
Membership Meeting for Adoption/Reject by membership
If approved by Membership it is sent to Standards Council for final
decision
If the Change fails to get Membership Approval it is given 21 Days
to be
submitted in a Written Appeal by to the Standards Council.
The Standards Council reviews all Pending Changes and Appeals and decides
which will make the new Code Book.
Total Process takes approximately 104 weeks.
