Terms of reference
TITLE: Train Operations Risk Group (TORG)
GOVERNANCE AND ADMINISTRATIVE ARRANGEMENTS
GOVERNANCE: The TORG terms of reference is approved by the System Safety Risk Group (SSRG)
FREQUENCY : Every 8 weeks – 4 hours (maximum), [nominally 4 weeks after SSRG meetings]
CHAIR: [Paul Watson, First TransPennine Express]
DEPUTY CHAIR: [Paul Rushton, East Midlands Trains]
MEETING MANAGER: RSSB
Core Members: Network Rail x 2, passenger operators x 3 (including 1 from ATOC), freight operators x 2,
infrastructure contractor mainline operator x 1, RSSB x 2 (director and head of operations research), Chair of
Traffic Operation and Management Standards Committee (TOM SC) x 1
Associate Members: Trade Unions x 3, ORR x 1, DfT x 1, London Underground Ltd x 1
External guests: Where appropriate, TORG may invite external guests to support individual agenda items. Expert guests from
other industries may also be invited to attend to inform the group on specific issues.
Location: London based (offices of RSSB, ATOC, ORR)
CONTEXT
The national railway system comprises passenger train operators, freight train operators, OTM operators, the national
infrastructure manager and their contractors, who are all required to manage their own risk in accordance with their safety
management systems. They are legally required (ROGS Regulation 22) under the terms of their Safety Certificate or Authorities to
work cooperatively with others to achieve the safe operation of their shared transport system through the development and
implementation of suitable control measures. Such cooperative activities between all transport operators should combine to
achieve the safe operation of the national railway system. In addition, they are required to cooperate with other transport system
operations.
PURPOSE of the TORG
The purpose of the TORG is to understand and review the proportion of total system risk relevant to its scope. The group is
required to: monitor the effectiveness of current control arrangements, identify and sponsor improvement opportunities including
research and RSSB-facilitated products and services; learn from and promote good practice; facilitate cooperation; respond to
requests from SSRG and other cooperative forums; and consider future developments that may impact its risk (horizon scanning).
SCOPE
1. Train accidents on the national rail network due to any cause (excluding at level crossings): human error, equipment
failure, environment, vandalism, and any other risks as directed by SSRG.
2. Train accident risk at yards, depots and sidings
3. Workforce risk to station and train crew from accidents occurring on the running line while changing ends of trains, or
investigating incidents/conditions on the line, eg slips, trips and falls, contact with objects, struck by train, and workforce
risk to shunters from accidents occurring on the running line while preparing trains, or investigating incidents/conditions
on the line, eg slips, trips and falls, contact with objects, struck by train.
4. Network Rail controlled infrastructure and train operations interfaces with other rail systems including: High Speed 1,
Crossrail, London Underground Ltd, Channel Tunnel.
RELATIONSHIPS
TORG will have relationships with:

SSRG will set TORG’s remit, refer items to TORG, and where necessary TORG will make recommendations to SSRG

SSRG subgroups: People on Trains & Stations Risk Group, Level Crossing Risk Group, National Suicide Prevention
Steering Group, and Data & Risk Modelling Strategy Group

Sector, route and other associated groups

RSSB including its Research and Development team and Traffic Operation and Management Delivery Unit (RSSB will be
the delivery resource for TORG and the meeting manager)
OPERATION
Members and nominated alternates to be inducted in to the purpose and operation of the TORG, only inducted and/or invited
members shall attend TORG. No other alternates will be accepted and the same applies to associate members.
Administrative support
Produce the draft minutes and action list for approval by the chair 1 week after the meeting – Mtg Mgr.
Send out chair approved minutes and action list to members 2 weeks after the meeting – Mtg Mgr.
Prepare draft agenda to be approved by chair using template 4 weeks before the meeting - Mtg Mgr. / Chair
Request inputs for pack 4 weeks before the meeting: deadline for submission, 14 days before meeting – Mtg
Mgr.
Review action list and follow up actions 4 weeks before the meeting - Mtg Mgr.
Compile meeting pack 1 week before meeting – Mtg Mgr.
Version
Date Approved
2.0
14.04.2014
Terms of reference
Send out meeting pack 1 week before meeting - Mtg Mgr.
Version
Date Approved
2.0
14.04.2014