CSA TS-128:25 ✓ Most Recent

Preface 

This is the first edition of CSA TS-128, Safety and security for public transit systems — Definitions, metrics, and data collection methods and uses. This Technical Specification document (referred to as "this Document" from here on) provides an overview of how transit systems can track, measure, collect, and analyze safety and security information as it relates to the interactions between customers (or between customers and employees) that occur within that space. Currently, data regarding public transit passenger and employee safety and security is not defined or collected in a uniform manner across Canada. The data that is available is fragmented, collected using a variety of methodologies and definitions, and often gathered by different types of organizations with different objectives. This inconsistency limits the usefulness of the data that is collected, which has numerous implications for public transit. This Document is designed to provide a common language and common methods for data collection, analysis, and reporting in relation to safety and security. CSA Group acknowledges that the development of this Technical Specification was made possible, in part, by the Canadian Urban Transit Association (CUTA). This Document was prepared by the Developmental Committee on Safety and Security. 

Scope 

1.1 Application 

This Document is applicable to all new and existing modes of public transit. Its scope includes all safety and security data used by transit systems, with "safety and security" referring to the well-being and physical safety of the public and transit employees when interacting with or being present within a transit system. This Document establishes relevant metrics and provides overall guidance for consistent data collection methods and reporting metrics. In addition, it provides best practices for how best to handle safety and security data to make them as useful and consistent as possible. 

1.2 Exclusions 

This Document excludes the safety of transit operations, such as the safe operation of a bus or train. 

1.3 Terminology 

In this Document, "shall" is used to express a requirement, i.e., a provision that the user is obliged to satisfy in order to comply with the Document; "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 Document. 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.