The 2005 edition of the National Model Construction Codes is presented in a new format called “objective-based codes” that is structured in three Divisions (A, B and C). For the first time, the Codes contain explicitly defined objectives and functional statements (see Division A), which are statements on the functions that the components of a building must perform and the objectives that these functions must satisfy. Most of the Code provisions in Division B-now called acceptable solutions-are linked to at least one of those objectives and functional statements.

These new elements were developed through a process called “bottom-up analysis,” which involved the analysis of each provision in the 1995 Codes to determine its intent and application and derive applicable objectives and functional statements. The Canadian Commission on Building and Fire Codes (CCBFC) wanted the scope of each Code to remain unchanged through its conversion to an objective-based format.

The bottom-up analysis of the acceptable solutions was carried out by the standing committees of the CCBFC with extensive support from the staff of the Canadian Codes Centre (CCC) together with groups of subject matter experts and external consultants. The technical changes that have been incorporated into Division B of the 2005 Codes also underwent the same bottom-up analysis. The results were reviewed, revised and approved by the appropriate standing committee.

Although the intent and application statements are included in the integral CD-ROM version of the 2005 Codes, it soon became apparent that this information would also be a valuable resource for users of the printed versions of the Codes. And so it was decided to publish the intent and application statements on CD-ROM as user's guides to each Code.

Only the provisions in Parts 3 to 9 of Division B (i.e. the acceptable solutions not including their Appendix Notes) have intent and application statements and, if applicable, objectives and functional statements.

Clicking on a Sentence reference in the left-hand portion of the screen brings up an analysis window on the right-hand side, which contains that Sentence's applicable objectives, attributions and intent and application statements.

For the most part, entire Sentences are analyzed as units of text. In such cases, only the Sentence number is identified in the analysis window and the actual text of the Sentence can be found in the printed Code. In some instances, however, the analysis applies to only a portion of a Sentence; in such cases, the Clause or Subclause being analyzed is identified in the field entitled “Attribution” or the portion of text being analyzed is quoted or summarized in that field and introduced by the phrase “Applies to.”

The objectives attributed to the provisions or portions of provisions in Division B are derived from the bottom-up analysis. Each analysis window contains tabs displaying the acronyms for each objective attributed to the text being analyzed. Clicking on a tab reveals a panel containing the information related to that objective attribution, e.g. OH1 Indoor Conditions.

Some provisions or portions of provisions in Division B have no objectives attributed to them. In such instances, the tab will display the symbol “+” rather than an objective such as OH1, OS3, etc. See a related discussion below under “Intent.”

The specific functional statements and sub-objectives attributed to the text being analyzed are presented in square brackets in the Attribution field. If the attributions and analysis (i.e. intent and application statements) apply to the entire Sentence, no explanatory text will appear before or after the square brackets; if they apply to only a portion of a Sentence, the square brackets will either be preceded by the Clause or Subclause identifier, or followed by a phrase beginning with “Applies to,” which specifies which portion of the Sentence the attributions and analysis apply to.

An application statement for a provision or portion of provision contained in Division B specifies the component(s) of a building to which the text being analyzed applies or in which circumstances the text applies.

Application statements generally identify which entity-i.e. occupancy, building element, material, activity, etc.-the Code provision applies to. The Code already contains provisions that state the application of most of the technical provisions but the application may be broadened or narrowed by cross-references or exceptions elsewhere in the Code. Sentence-, Clause- or Subclause-specific application statements combine all this information in one place.

An intent statement explains the purpose of a provision or portion of provision found in Division B. It reveals what the standing committee was trying to achieve by introducing the Code provision in the first place or what the Code-user community has come to understand as the reason for the provision's existence.

Generally speaking, intent statements present the consequences of non-compliance with a requirement. They try to answer the question “What are the undesirable thing(s) that might happen if this provision is not complied with?” In many cases, the initial consequences of non-compliance may lead to a chain of consequences; the link between those consequences and the overall objective of the provision may only become apparent in the description of the latter consequences in the chain. All functional statements and objectives identified in Division A and attributed to the provisions in Division B of the 2005 Codes are derived from the intent statements.

Not all Code provisions are technical requirements; some act as definitions, clarifications, application modifiers or pointers to another provision. In such cases, the intent statement explains the role the provision plays in the Code and there is no chain of consquences. These types of provisions have no objectives or functional statements attributed to them. Appendix Note A-1.1.2.1.(1) in Division B of the Code provides information on how these types of provisions shall be interpreted in regards to their relation to objectives and functional statements.

Serious effort was put into using a consistent, logical approach and standardized set of phrases and terms in the development of the intent statements. It is the ongoing responsibility of the standing committees to maintain, update and improve the intent and application statements over time. Any suggestions towards these endeavours are welcome.

Many of the hazards and undesirable events the Codes address, such as deterioration, spread of fire and heat loss, can only be minimized, retarded or controlled through compliance; other undesirable events such as the ignition of fire or structural collapse can never be prevented with absolute assurance. This is why the phrase “to limit the probability” is used in the intent statements rather than “to prevent.”

Using the phrase “to prevent” would mean that it is possible to comply fully with a requirement but still not meet its intent. The phrase “to limit the probability” was therefore adopted to clearly convey the notion that the Codes do not and cannot provide absolute protection.

In the development of the intent statements for Part 5 and Part 9, it was recognized that:

• non-compliance with a requirement in those Parts could have several adverse consequences,
• the immediately apparent adverse consequence(s) may not be the first or most likely to occur, nor the most serious, and
• one adverse consequence may lead to others that should also be identified.

Describing the logical progression of consequences-from the basic property or performance issue addressed by the provision through to the objectives-resulted in intent statements for some Part 5 and Part 9 provisions that are longer and more detailed than those for provisions in other Parts of the NBC.

Furthermore, some building elements addressed by Part 9 provisions may serve a variety of functions depending on the design of the building. In these cases, intent statements were developed for each function that the building element might serve.

Virtually all components of a building will eventually fail in the absence of maintenance, and many will eventually fail even with maintenance. This normal, expected failure cannot be addressed by code provisions. However, many NBC provisions, do address premature failure-failure that occurs at a time when the component would be expected to continue to perform its function without special maintenance. These provisions do not specify an expected service life (i.e. acceptable lifespan) for a material, component or assembly; in general, they prescribe performance criteria, material properties or service conditions that are expected to provide a reasonable service life (e.g. material type, thickness of a protective coating, minimum temperature of air contacting furnace heat exchangers). Only Sentence 4.1.1.3.(1) and Clause 5.1.4.1.(4)(b) in Division B refer explicitly to service life or to a time period over which a component is expected to perform, without stating a precise minimum period.

The intent statements for all provisions that promote resistance to deterioration describe the consequences of premature failure that would result from failing to comply with the respective requirement.

All intent statements describe the initial consequences of non-conformance with a Code provision. Many intent statements also describe a chain of consequences in cases where posterior consequences may be more severe than the initial hazard. One such scenario is the failure of environmental separation elements.

Many hazards addressed in Part 5 and Part 9, such as condensation and the ingress of precipitation that could result from non-compliance, would not only initially lead to adverse health effects but might also lead to the eventual deterioration of building elements, which can, in turn, lead to a multiplicity of negative effects on the performance of required environmental separation elements. Rather than including a detailed description of each and every specific potential effect in the applicable intent statements, the Standing Committee on Houses and the Standing Committee on Environmental Separation chose the phrase “which could lead to compromised integrity of environmental separators” to capture the concept of broader adverse performance implications.

Because environmental separators provide protection from issues like water ingress and condensation, they protect structural elements from rot, corrosion and conditions conducive to the infiltration of destructive insects. Consequently, most Code provisions dealing with environmental separation elements have a structural safety intent and objective as well as a health intent and objective.

Other scenarios involve environmental separation elements that also have a structural role and structural elements within environmental separators. In addition to describing the potential direct consequences of loss of structural integrity or structural collapse, the intent statements also describe the chain of consequences that would occur if only the environmental separation function were compromised. A comprehensive analysis of all these compromised functions would, however, increase the volume of text to such a degree that the standing committees decided to summarize the multiplicity of consequences with the phrase “failure of required environmental separation elements.” Thus, many Code provisions that mainly address structural issues also have health objectives stemming from the failure of required environmental separation elements.

In many intent statements related to the OH1 Objective, Indoor Conditions, negative effects beyond the initial consequences of non-conformance are identified in sets of short bulleted lists rather than in continuous, full-length sentences. Each item listed represents a consequence that is as likely to occur as another at this point in the chain of consequences. There is no direct correlation between the order in which the consequences are presented in these lists and the order and certainty of their occurring; each consequence identified in one set will potentially lead to at least one of the consequences in the subsequent set. This approach using simplified lists was implemented to improve the readability of the intent statements and to reduce their length.