top of page

COMMON SAFETY METHOD (CSM)

1_CSM_robofleet.png

​RISK ANALYSIS INCLUDING
HAZARD IDENTIFICATION

​​

  • Identify all relevant hazards and associated safety measures as part of the risk management process

  • Create or update hazard record until all changes are accepted or the safety assessment report is released

  • Demonstrate how hazard record is tracking progress in risks monitoring associated with identified hazards

  • Communicate hazards to responsible actors who must evaluate the related risks and agree on risk mitigations

  • Maintain the accepted and operational hazard log by infrastructure manager or railway operator

2_CSM_robofleet.png

​SYSTEM DEFINITION IN
ACCORDANCE WITH CSM-RA​

​​

  • Intended purpose(s) of the system and assumptions that define the scope of the risk assessment

  • System functions and components, including human, technical and operational elements

  • Functional and physical and interfaces, incl. functional input / output and interacting systems

  • Specified safety measures and safety requirements identified by the risk assessment process

  • System boundaries, including other interacting systems and the system environment, including operational use

3_CSM_robofleet.png

​​RISK ACCEPTANCE
PRINCIPLE (RAP)

​​

  • Overview of risk acceptance principles according to (EU) 402/2013, Annex I

  • Evidence of compliance with the  Code of practice (CoP)

  • Evidence of similarity to similar reference systems (RS)

  • Evidence of explicit risk estimation (ERE)

  • Identified safety measures transferred to safety requirements to make the risks of the system on acceptable level

4_CSM_robofleet.png

​​EVIDENCE FROM THE APPLICATION 
OF THE RISK MANAGEMENT PROCESS​

​

  • Description of the organization and identification of the experts responsible for conducting the risk assessment process

  • Documentation of the results at each phase of the risk assessment and a listing of all safety requirements

  • Summary of all assumptions made during system definition, design, and risk assessment

  • Submission of all approved evidence demonstrating compliance with the safety requirements

  • Commissioning, supporting, and supervising the preparation of the safety assessment report by an independent assessment body

REQUIREMENTS CAPTURE (Article 13 (EU)2018/545)

01_RQC_robofleet.png

​​METHODOLOGY OF REQUIREMENTS CAPTURE ACCORDING TO (EU) 2018/545

​

  • Essential requirements for subsystems referred in Article 13 to (EU) 2018/545 and specified in Annex III to (EU) 2016/797

  • Application of a standardized/recognized methodology for requirements capture

  • Complete system definition, consistent with design of vehicle

  • Consistent hazard identification and classification, with a structured hazard management

  • Requirements derived from risk analysis are properly traced from hazard to evidence of requirement compliance

  • Identify the non-compliance with essential requirements that may lead to amendment or revocation of an authorization

02_RQC_robofleet.png

CAPTURE, MANAGEMENT AND 
ACHIEVEMENT ALL REQUIREMENTS

 

  • Identification of all relevant requirements covering the complete vehicle design for its life cycle

  • Assign all relevant requirements to functions or subsystems of vehicle

  • Address all relevant requirements by conditions for use or other restrictions

  • Ensure that all relevant requirements are implemented and validated

  • Safety requirements related to vehicle and its subsystems for the aspects that are not covered by European TSI and National Technical Rules (NTR)

03_RQC_roboflleet.png

​SAFE INTEGRATION 
OF THE VEHICLE

​

  • Record and documentation of requirements for the safe integration of the individual vehicle subsystems

  • Safety-related application conditions (SRAC) to ensure and support the aspects of safe integration

  • Safe vehicle integration confirmed by NoBo / DeBo assessments, documented in certificates and their associated dossiers

  • Evidence of the CCS device integration into the rail vehicle

  • Data recording device and accessibility

04_RQC_robofleet.png

​TECHNICAL COMPATIBILITY WITH 
RAILWAY NETWORK IN AREA OF USE​

​

  • Definitions relating to technical compatibility

  • Requirements for compatibility between the rail network characteristics in specified area of use and vehicle characteristics to ensure safe operation

  • Documentation of technical compatibility between the vehicle’s subsystems as part of the vehicle assessment

  • Documentation of technical compatibility between the vehicle and the railway network in the area of operation

  • Confirmation of technical compatibility through assessments by the Notified Body (NoBo) or the Designated Body (DeBo), documented in their certificates and the associated dossiers

bottom of page