CSA Group CSA Z663:18 National Standard of Canada (reaffirmed 2023) Land use planning in the vicinity of pipeline systems

Preface

This is the first edition of CSA Z663, Land use planning in the vicinity of pipeline systems. It supersedes and replaces CSA PLUS 663, Land use planning for pipelines: A guideline for local authorities, developers, and pipeline operators published in 2004.

This Standard aims to address the challenges facing land use planning near pipelines in Canada; outlining key elements that when consistently applied will enhance safe and informed development. Users of this Standard are reminded that additional and site-specific requirements might be specified by federal, provincial/territorial, or municipal authorities. While risk-informed decision-making has become one of the methods supporting informed land development, it is not addressed in this Standard; however, users may choose to use risk-informed decision-making practice. The Technical Committee chose not to incorporate risk-informed decision-making given the multitude of other standards that more aptly address those practices.

This Standard should not be considered as a replacement for the requirements contained in any

a) applicable federal, provincial, territorial, regional, or municipal statute; or

b) regulation, licence, or permit issued pursuant to an applicable statute.

Explanatory material has been added to Annexes to clarify the content and provide guidance.

CSA Group acknowledges that the development of this Standard was made possible, in part, by thefinancial support of Canadian Energy Pipeline Association (CEPA) and Canadian Common Ground Alliance (CCGA).

This Standard was prepared by the Technical Committee on Land Use Planning in the Vicinity of Pipeline Systems, under the jurisdiction of the Strategic Steering Committee on Petroleum, Natural Gas, and Industry Systems, and has been formally approved by the Technical Committee.

This Standard has been developed in compliance with Standards Council of Canada requirements for National Standards of Canada. It has been published as a National Standard of Canada by CSA Group.

Notes:

1) Use of the singular does not exclude the plural (and vice versa) when the sense allows.

2) Although the intended primary application of this Standard is stated in its Scope, it is important to note that it remains the responsibility of the users of the Standard to judge its suitability for their particular purpose.

3) This Standard was developed by consensus, which is defined by CSA Policy governing standardization — Code of good practice for standardization as “substantial agreement. Consensus implies much more than a simple majority, but not necessarily unanimity”. It is consistent with this definition that a member may be included in the Technical Committee list and yet not be in full agreement with all clauses of this Standard.

4) To submit a request for interpretation of this Standard, please send the following information to [email protected] and include “Request for interpretation” in the subject line:

a) define the problem, making reference to the specific clause, and, where appropriate, include an illustrative sketch;

b) provide an explanation of circumstances surrounding the actual field condition; and

c) where possible, phrase the request in such a way that a specific “yes” or “no” answer will address the issue.

Committee interpretations are processed in accordance with the CSA Directives and guidelines governing standardization and are available on the Current Standards Activities page at standardsactivities.csagroup.org.

5) This Standard is subject to review within five years from the date of publication. Suggestions for its improvement will be referred to the appropriate committee. To submit a proposal for change, please send the following information to [email protected] and include “Proposal for change” in the subject line:

a) Standard designation (number);

b) relevant clause, table, and/or figure number;

c) wording of the proposed change; and

d) rationale for the change.

1 Scope

1.1

This Standard

a) provides minimum requirements, guidance, and best practices for land use planning and development processes in the vicinity of existing pipeline systems;

b) addresses roles, responsibilities, and engagement of all stakeholders to establish a consistent approach to land use planning in the vicinity of existing pipeline systems; and

c) focuses on long-range policy planning and site development planning processes in the vicinity of existing pipeline systems.

Note: Annex B provides additional topics and guidance that is not covered in this Standard but deemed beneficial to have available.

1.2

This Standard does not apply to

a) infrastructure other than pipeline systems, including but not limited to,

i) potable water;

ii) sewage;

iii) stormwater; and

iv) electric supply and communication.

b) sour gas pipeline systems addressed in CAN/CSA-Z662 and various provincial and/or federal legislation and regulation; and

c) planning and installation of future pipeline systems.

Note: See Figure 1.

1.3

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; and “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.

Note: Pipeline systems between the gate station/pressure regulation station/odourization station and the commercial customer and residential customer might include pipeline systems which might be outside of the scope of this Standard. AHJ’s and developers should contact the pipeline operator in these situations