Transcript Delay Attribution Guide April 2011 Changes

Delay Attribution Guide
April 2011 Changes
Ana Maria Sanchez
Delay Attribution Board Administrator
New Codes
• 4 new codes have been introduced to the April 2011 Delay Attribution Guide (DAG)
CODE
CAUSE
OW
Connections held where the prime incident
causing delay to the incoming train is a FOC
owned incident and service is more frequent
than hourly.
ABBREVIATION
FOC CONN
PS
- Check paragraph 4.28.2 for likely situations.
Cancellation of a duplicate or erroneous
schedule.
DUPE SCHLD
X9
- Check Appendix A section P
Points failure caused by severe snow where
heaters are working as designed.
SEV SNOW
XO
- Check flowchart 4.37.6d for guidance in dealing
with the impact of snow, ice or frost
External trees, building or objects encroaching
onto Network Rail infrastructure (not due to
weather or vandalism)
EXT OBJECT
1ST MARCH 2011
2
XO Delay Code reasoning
The new XO delay code has been introduced to reduce the use of XZ (generic external)
for certain events such as:Trees falling from outside railway boundaries
Masonry / buildings (non railway) falling or threatening to fall onto the infrastructure
Motor Vehicles landing on infrastructure
Air borne ‘machinery’ landing on the infrastructure
Cautioning for potential external interference – e.g. cranes operating near to railway lines that
could fall / drop
 (In all circumstances the event must not be due to weather or vandalism which has defined
coding in the DAG)
1ST MARCH 2011
3
KEY AMENDMENTS
• Section 4.3.7.1 letter b Code JP.
– Now reads: Failure to maintain vegetation within network boundaries in accordance
with prevailing Network Rail Standards.
• This change has been made so that the DAG reflects the prevailing standards
for vegetation maintenance regimes.
• Appendix A Section J – code JP has been edited to reflect the wording in section
4.3.7.1 letter b
• Section 4.4.3 flowchart – Did the animal originate from the train or from Railway
Infrastructure (Non-Network Rail)
– Railway Infrastructure has been added to remove any possible confusion which
could lead attribution staff to include incidents where animals originated from
fields.
1ST MARCH 2011
4
KEY AMENDMENTS
•Section 4.28.2 (f)
No
f.
Circumstances
Waiting passenger connections within the
TOC/Network Rail connection policy,
where the prime incident causing delay to
the incoming train is a FOC owned
incident..
Delay Code
YL
Incident Attribution
Prime incident causing incoming train to be
late at that point, if the connecting service is of
hourly or lower frequency. If more than hourly
frequency then separate incidents to be
created attributable to Network Rail
(OW/OQ**)
• Section 4.37.1 –
– The wording of this section has changed slightly and special attention should be given to the
removal of the question marks after ‘other modes of transport have been affected.
– Also note that the criteria for the severe weather warning must be issued by the Met Office
but it must be relevant to the type of delay and the area in which the delays are occurring.
• The term ‘the effect of the weather is outside the design parameters of infrastructure and fleet
equipment’ has been removed because, it was identified that it would be very difficult and not
practical or useful to state what kind of effects would be constituted as being outside of design
parameters of each asset for the purposes of Delay Attribution. It is still valid however to indicate
that the effect of the weather must be unavoidable through maintenance.
1ST MARCH 2011
5
KEY AMENDMENTS
• References to Weather Management ‘RED alert’ and EWAT teams have been ADDED in order to
have a nationally consistent trigger to start implementation of attribution to ‘external’ codes in
exceptional conditions. The NCI approved Code of Practice ‘Section 7.1 Weather management’ is
a cross industry procedure triggered by Route Control Manager
• Note that:
• All references to Rules of the Plan (or wording variations of the same document such as
ROTP) now read Timetable Planning Rules
• All references to Rules of the Route (or wording variations of the same document such as
ROTR) now read Engineering Access Statement.
1ST MARCH 2011
6
Any Questions?
• We encourage you all to visit the DAB website at: www.delayattributionboard.co.uk
• There you will find the latest copies of the DAG, FAG and competency standards.
• The web site is updated regularly with up and coming events and activities that the DAB are
undertaking.
• You can use the website to obtain the forms to make proposals for change to the DAG and PDAC
as well as requests for guidance.
• You can use the website to make suggestions on how to improve delay attribution on the whole.
• You can email your representative via the website, however, please do not use this facility to
request specific attribution guidance – the request for guidance process is to be followed in these
cases.
• Feel free to email the DAB Secretariat on: [email protected] for clarification on
process in regard to delay attribution/disputes.
1ST MARCH 2011
7