scope:

The scope of the LUCM Incident Management Arrangements is to enable the Civils organisations to:

• Identify/Assess

• Respond/Recover

• And Learn from any incident that impacts on its business.

It does this by setting out clear guidelines and processes that:

• Define the roles and responsibilities of Civils staff involved in incident management.

• Identifies a clear 'chain of command' so there is no doubt as to who controls and takes responsibility for the organisations response to any incident.

• Explains the LUCM's interactions with other London Underground and external departments during incidents that impact on the operational railway.

So any impact on the business and its operations is minimised and that situation is returned to normal with minimal disruption and cost.

Purpose

The purpose of this document is to define the process by which London Underground Civils Maintenance (LUCM) Emergency Response supports the London Underground Rule Book 2 requirements for Civils Asset Incidents and how specific 'Incidents' (see definition and examples below) are identified, managed and communicated to ensure there is minimum delay & disruption to the London Underground's (LU) business.

For the purposes of the Civils, an Incident is defined as in LU 1-622 Glossary of Terms:

'An event which results in damage to a structure.'

These 'Incidents' are often defined using many different terms such as 'Emergency', 'Crisis' as well as incident. All have a tendency to give different interpretations to different people. Therefore the term 'Incident' has been adopted by the Civils as a catch all for such occurrences to avoid any misunderstanding or confusion. It also takes some of the emotion and 'loss of control' that can be associated with other terminology.

Some examples of the Incidents and their impact on the Civils covered by this procedure are listed below.

• Bridge Strike.

• Embankment collapse.

• Flooding of Asset.