Standard: LUL - G1001
INCIDENT MANAGEMENT ARRANGEMENTS - CIVIL ASSETS
This standard is available with a subscription to IHS Standards Expert.
IHS Standards Expert subscription, simplifies and expedites the process for finding and managing standards by giving you access to standards from over 370 standards developing organizations (SDOs).FEATURES & BENEFITS
- Maximize product development and R&D with direct access to over 1.6 million standards
- Discover new markets: Identify unmet needs and discover next-generation technologies
- Improve quality by leveraging consistent standards to meet customer and market requirements
- Minimize risk: Mitigate liability and better understand compliance regulations
- Boost efficiency: Speed up research, capture and reuse expertise
HOW TO SUBSCRIBE
This scope applies to LUCM. The scope of the LUCM incident management arrangements is to enable the civils organisations to:
It does this by setting out clear guidelines and processes that:
So any impact on the business and its operations is managed ALARP and that the situation is resumed to a ‘normal’ operational state with tolerable disruption and cost.
The purpose of this document is to provide guidance by which London Underground (LU) Civils Maintenance (LUCM) emergency response supports the LU Rule Book 2 ‘Managing incidents’ 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 LU’s business.
These ‘Incidents’ are often defined using many different terms such as ‘emergency’, ‘crisis’ as well as ‘incident’. Therefore the incident is defined as an event that has a potential to cause safety and/or service loss risk to the operational railway.
For the purposes of the civils, an incident is defined as an event which results in damage to a structure.
Assets that fall under the civils discipline area include:
Note: Pumps are managed and maintained by premises M&E and station drainage and track drainage for BCV/SSL by track.
The guidance in this document applies to incidents involving any such asset regardless of ownership or maintenance responsibility
|Organization:||London Underground Library|
|Change Type:||COMPLETE REVISION|
|Most Recent Revision:||YES|
|Document #||Change Type||Update Date||Revision||Status|
|G1001||Change Type: STCH||Update Date: 2011-01-10||Status: INAC|