Editing SimSig:Disruption Management
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 11: | Line 11: | ||
Most TOCs use four incident levels for grading incidents on the railway to help staff understand the event's severity in question. The trigger points for incidents vary from TOC to TOC however, below is an explanation of our system which is derived from a suburban TOCs operating practice. The level of an incident is determined by service control staff and communicated to all impacted staff via verbal and written messages. | Most TOCs use four incident levels for grading incidents on the railway to help staff understand the event's severity in question. The trigger points for incidents vary from TOC to TOC however, below is an explanation of our system which is derived from a suburban TOCs operating practice. The level of an incident is determined by service control staff and communicated to all impacted staff via verbal and written messages. | ||
All levels above Code Green can be applied on a network-wide or line of route basis. For example, a Code Red could be declared on all lines in the West Midlands due to major signalling issues at Birmingham New Street, or it could be declared just for the Cross-City line due to a train fault. | All levels above Code Green can be applied on a network-wide or line of route basis. For example, a Code Red could be declared on all lines in the West Midlands due to major signalling issues at Birmingham New Street, or it could be declared just for the Cross-City line due to a significant train fault. | ||
=== Code Green === | === Code Green === | ||
| Line 18: | Line 18: | ||
A Code Green would be declared by service control if one of the following criteria are met: | A Code Green would be declared by service control if one of the following criteria are met: | ||
* An isolated incident delaying up to | * An isolated incident delaying up to 2 trains by less than 5 minutes | ||
* An incident not affecting services (e.g. overnight) but with the potential to impact train services resuming in the morning | * An incident not affecting services (e.g. overnight) but with the potential to impact train services resuming in the morning | ||
* An incident that was previously classed as YELLOW or RED where service has resumed to normal | * An incident that was previously classed as YELLOW or RED where service has resumed to normal | ||
[[File:TCF Example.png|thumb|563x563px|SimSig display showing a Track Circuit Failure (TCF) on the loop at Haywards Heath. The failure can been seen as the red line in the loop not associated with a train. In this case the failure can be worked around and would have minimal impact on trains. This would be a Code Green incident.]] | [[File:TCF Example.png|thumb|563x563px|SimSig display showing a Track Circuit Failure (TCF) on the loop at Haywards Heath. The failure can been seen as the red line in the loop not associated with a train. In this case the failure can be worked around and would have minimal impact on trains. This would be a Code Green incident.]] | ||
| Line 26: | Line 26: | ||
Code Yellow incidents are more serious than Code Green and have a more noticeable impact on the running of railway services. A Code Yellow incident is one which is expected to cause delays of between 5 and 20 minutes to a number of trains and which has the possibility of causing disruption to a wider section of the railway. | Code Yellow incidents are more serious than Code Green and have a more noticeable impact on the running of railway services. A Code Yellow incident is one which is expected to cause delays of between 5 and 20 minutes to a number of trains and which has the possibility of causing disruption to a wider section of the railway. | ||
Below are listed the criteria on which control will judge if an incident is to be categorised as a Code Yellow | Below are listed the criteria on which control will judge if an incident is to be categorised as a Code Yellow | ||
'''Off-Peak''' | '''Off-Peak Period''' | ||
* An incident expected to delay less than | * An incident expected to delay less than 15 trains by less than 15 minutes | ||
'''Peak''' | '''Peak''' | ||
* Incident expected to delay less than | * Incident expected to delay less than 10 trains by less than 5 minutes | ||
* | * 3 or more alterations/cancellations on the same route due to a single incident | ||
'''Suburban | '''Suburban Line''' | ||
* More than | * More than 3 services running more than 15 mins late | ||
'''Long Distance | '''Long Distance Line''' | ||
* More than | * More than 3 services running between 5 and 25 minutes late | ||
=== Code Red === | === Code Red === | ||
Code Red incidents are serious events which cause significant delay to train services or impact a large area of the railway. A Code Red incident is generally one which is expected to cause multiple suburban services to be delayed by over 15 minutes and long-distance services by over 30 minutes. A Code Red incident will result in significant levels of service alterations and cancellations. Code Red incidents are the most disruptive events that will occur randomly in our SimSig sessions. | Code Red incidents are serious events which cause significant delay to train services or impact a large area of the railway. A Code Red incident is generally one which is expected to cause multiple suburban services to be delayed by over 15 minutes and long-distance services by over 30 minutes. A Code Red incident will result in significant levels of service alterations and cancellations. Code Red incidents are the most disruptive events that will occur randomly in our SimSig sessions. | ||
Below are listed the criteria on which Control will judge if an incident is to be categorised as a Code Red | Below are listed the criteria on which Control will judge if an incident is to be categorised as a Code Red | ||
'''Off-Peak''' | '''Off-Peak period''' | ||
* Incident expected to delay | |||
'''Peak''' | * Incident expected to delay 15 or more trains by 15 minutes or more | ||
* Incident expected to delay | |||
* Any closure of | '''Peak Period''' | ||
'''Suburban | |||
* More than | * Incident expected to delay 10 or more trains by 5 minutes | ||
* Consistent alterations/cancellations to services on one line | * Any closure of 1 or more lines (e.g. UMSL or UMFL) on a core route | ||
'''Long-Distance | |||
* More than | '''Suburban''' | ||
* Consistent alterations/cancellations on one line | |||
* More than 5 services running more than 15 minutes late | |||
* Consistent alterations/cancellations to services on one line | |||
'''Long-Distance Lines''' | |||
* More than 5 services running more than 25 minutes late | |||
* Consistent alterations/cancellations on one line | |||
=== Code Black === | === Code Black === | ||
Code Black incidents are infrequent incidents that cause widespread delays and result in the unavailability of extensive parts of the network, such as the closure of a major terminal station for a prolonged period. In the real railway, a Code Black may often result in a TOC issuing an instruction for customers not to travel as the network has been rendered unusable. Due to the level of disruption involved | Code Black incidents are infrequent incidents that cause widespread delays and result in the unavailability of extensive parts of the network, such as the closure of a major terminal station for a prolonged period. In the real railway, a Code Black may often result in a TOC issuing an instruction for customers not to travel as the network has been rendered unusable. Due to the level of disruption involved generally if a simulation descends to the point that the level of disruption would warrant a Code Black declaration the session will be ended. | ||
=== Code Blue === | === Code Blue === | ||