Main Categories
- Agriculture and Agri-food (0)
- Business Management (0)
- Construction and Engineering (5)
- Electrical (20)
- Energy (11)
- Environment and Climate Change (2)
- Health Care and Medical Devices (0)
- Information Technology and Telecommunication (1)
- Infrastructure and Public Works (0)
- Mechanical and Industrial Equipment (0)
- Nanotechnologies (0)
- Natural Resources (0)
- Occupational Health and Safety (2)
- Public and Community Safety (4)
- Transit and Passenger Rail (0)
- Unclassified documents (0)
- Canadian Electrical Code, Part I (24)
- ANSI BSR8 (0)
Draft Amendment to C22.1
Draft Amendment to C22.1
Draft Amendment to C22.1
Draft Amendment to C22.1
Draft Amendment to C22.1
Draft Amendment to C22.1
Draft Amendment to C22.1
1 Scope
1.1 General
This Standard specifies special requirements for the durability aspects of the design and construction of new parking structures and parts of buildings subject to vehicular traffic.
This includes pedestrian traffic areas adjoining to or contained within parking structures. These include areas such as stairs, and pedestrian bridges from parking structures.
The application of this Standard includes structures which are designed for the storage and/or repair of vehicles whether those structures are stand alone, above ground or below ground, part of or connected to the structure of a larger structure/development.
Note: This includes commercial, residential, industrial or institutional, and all other building types.
1.2 Structure types
New parking structures constructed of structural steel, reinforced concrete (including prestressed concrete), or a combination of these materials fall within the scope of this Standard.
1.3 Repair of existing parking structures
This Standard does not cover the repair of existing parking structures, and the provisions of this Standard are not necessarily appropriate for the repair and protection of existing structures.
Note: See CSA S448.1 for information on the repair of concrete structures.
1.4 Reference standards
In the event of conflict between this Standard and the reference standards, this Standard takes precedence.
1.5 Terminology
In this Standard, “shall” is used to express a requirement, i.e., a provision that the user is obliged to satisfy in order to comply with the Standard; “should” is used to express a recommendation or that which is advised but not required; “may” is used to express an option or that which is permissible within the limits of the Standard.
Notes accompanying clauses do not include requirements or alternative requirements; the purpose of a note accompanying a clause is to separate from the text explanatory or informative material.
Notes to tables and figures are considered part of the table or figure and may be written as requirements.
Annexes are designated normative (mandatory) or informative (non-mandatory) to define their application.
1.1 General
This Code specifies the requirements for those parts of a building’s information and communication technology (ICT) infrastructure that enhance the safety, security, and reliability of the building by detecting or causing changes through the direct monitoring and/or control of a building’s real property equipment, assets, processes, and events. It applies to buildings, structures, and premises including factory-built relocatable and non-relocatable structures.
This Code outlines requirements for the following criteria relevant for building systems ICT infrastructure:
operational performance;
security and privacy;
network typology; and
physical environment.
1.2 Inclusions
The Code applies to network security profile, environmental protection, and ICT infrastructure that is associated only with building systems (e.g., HVAC, lighting, video surveillance systems) for office, multi-unit residential, and institutional buildings (e.g., schools, universities, convention centres, health care facilities).
1.3 Exclusions
The Code does not cover
detailed design of building systems connected to the ICT system;
tenant systems (e.g., file servers, printing, IP phones, HR systems) and the ICT infrastructure associated with these systems; and
health care systems (e.g., nurse call systems, oxygen supply systems, CT scans, MRIs) and the ICT infrastructure associated with these systems.
1.4 Terminology
In this Code, “shall” is used to express a requirement, i.e., a provision that the user is obliged to satisfy in order to comply with the Code; “should” is used to express a recommendation or that which is advised but not required; and “may” is used to express an option or that which is permissible within the limits of the Code.
Notes accompanying clauses do not include requirements or alternative requirements; the purpose of a note accompanying a clause is to separate from the text explanatory or informative material.
Notes to tables and figures are considered part of the table or figure and may be written as requirements.
Annexes are designated normative (mandatory) or informative (non-mandatory) to define their application.