Difference between revisions of "UK West Coast Route Modernisation Project"
Line 27: | Line 27: | ||
*[INCOSE 2011] Systems Engineering in Transportation Projects: A Library of Case Studies, INCOSE Transportation Working Group Issue 1.0, March 9th, 2011. HC 22 Session 2006-2007 | 22 November 2006 | *[INCOSE 2011] Systems Engineering in Transportation Projects: A Library of Case Studies, INCOSE Transportation Working Group Issue 1.0, March 9th, 2011. HC 22 Session 2006-2007 | 22 November 2006 | ||
*[NAO 2006] National Autid Office, The Modernisation of the West Coast Main Line, Report by the Comptroller And Auditor General, HC 22 Session 2006-2007, November 22, 2006. | *[NAO 2006] National Autid Office, The Modernisation of the West Coast Main Line, Report by the Comptroller And Auditor General, HC 22 Session 2006-2007, November 22, 2006. | ||
+ | |||
+ | ==References== | ||
+ | Please make sure all references are listed alphabetically and are formatted according to the Chicago Manual of Style (15th ed). See the [http://www.bkcase.org/fileadmin/bkcase/files/Wiki_Files__for_linking_/BKCASE_Reference_Guidance.pdf BKCASE Reference Guidance] for additional information. | ||
+ | |||
+ | ===Citations=== | ||
+ | List all references cited in the article. Note: SEBoK 0.5 uses Chicago Manual of Style (15th ed). See the [http://www.bkcase.org/fileadmin/bkcase/files/Wiki_Files__for_linking_/BKCASE_Reference_Guidance.pdf BKCASE Reference Guidance] for additional information. | ||
+ | |||
+ | ===Primary References=== | ||
+ | All primary references should be listed in alphabetical order. Remember to identify primary references by creating an internal link using the ‘’’reference title only’’’ ([[title]]). Please do not include version numbers in the links. | ||
+ | |||
+ | ===Additional References=== | ||
+ | All additional references should be listed in alphabetical order. | ||
+ | |||
===Article Discussion=== | ===Article Discussion=== | ||
[[{{TALKPAGENAME}}|[Go to discussion page]]] | [[{{TALKPAGENAME}}|[Go to discussion page]]] | ||
[[Category:Part 7]][[Category:Vignette]] | [[Category:Part 7]][[Category:Vignette]] |
Revision as of 17:40, 24 June 2011
Overview
The West Coast Main Line is a principal UK railway artery serving London, the Midlands, the North West and Scotland. The Line is responsible for over 2,000 train movements each day, with more than 75 million rail journeys made each year on the route; it accounts for 43% of Britain’s UK freight market. In 1998, the British government embarked on a modernization program, called the West Coast Route Modernisation (WCRM) project, to carry out a significant volume of modernization work between 1998 and 2008, delivering increased capacity and reduced journey times as well as replacing worn-out parts of the railway. It was challenging job involving 640 kilometers of track—much of it incapable of carrying high-speed rail cars. Some sections were seriously dilapidated, and new trains would require a complete overhaul of signaling, power supply, and switching systems. This vignette is based information from an INCOSE publication on systems engineering case studies [INCOSE 2011] and a report of the UK National Audit Office [NAO 2006].
Vignette Description
Early on the WCRM upgrade had serious problems. A major complicating factor was the introduction of new signaling technology to allow improved services delivered by new trains running at 140 miles per hour. By 2001, neither the rail infrastructure upgrade nor the new trains were on course for delivery as set out in the 1998 agreement. By May 2002 the projection of the program’s final cost had risen from £2.5 billion (in 1998) to £14.5 billion, but had delivered only a sixth of its scope.
In January 2002, the UK Secretary of State instructed the Strategic Rail Authority (SRA) to intervene and find a way to renew and upgrade the West Coast Main Line. An SRA analysis identified the following problems:
- The program lacked direction and leadership before 2002. The project did not have a delivery strategy and central point for responsibility and communication across the program.
- There was a lack of openness and communication of the program to interested parties before 2002 and a lack of stakeholder management.
- Scope changes arose because WCRM did not have an agreed specification which matched required outputs with inputs; and there was inadequate knowledge about the West Coast asset condition.
- Technology issues, in the decision to replace conventional signaling with unproven moving block signaling, introduced major risk into deliverability and cost before 2002. Technology issues caused scope changes and program delay.
- Project management was weak, with a lack of senior management skills, too many changes in personnel and ill-defined and fragmented roles and responsibilities. There was no integrated delivery plan and there was limited oversight of contractors. Poor management of contracts added to costs.
In order to remedy the situation The SRA initiated the following actions, which align with good SE practice:
- set a clear direction for the project, in its June 2003 West Coast Main Line Strategy, specifying what it wanted to achieve;
- established a clear, measurable set of program outputs, along with more detailed infrastructure requirements, which were then subject to systematic change control and monitoring procedures fixing scope, and then inviting contractors to tender to complete detailed designs and deliver the work to a fixed price;
- instituted clear program governance structures;
- and consulted widely with stakeholders and kept them informed.
The NAO report concluded that the new arrangements worked well and that the benefits included: facilitating a more intrusive regime of obtaining possession of the track for engineering work through extended blockades, which was crucial to delivery as access had been the program's key constraint and one of the key cost drivers; and identifying opportunities to reduce the program cost by over £4 billion.
The WCRM problems could be associated with a number of system engineering concepts and practices: stakeholders requirements (SEBoK 3.3.1), planning (SEBoK 3.6.1), risk analysis (SEBoK 3.6.3), decision management (SEBoK 3.6.5), change management (SEBoK 3.6.6), information management (SEBoK 3.6.7), and insufficient management oversight (SEBoK 3.6.2).
Summary
The WCRM project illustrates when SE concepts and practices are not used or applied properly, system development can experience serious debilitating problems. This project also demonstrates how such problems can be abated and reversed when system engineering principles and methods are applied. References
- [INCOSE 2011] Systems Engineering in Transportation Projects: A Library of Case Studies, INCOSE Transportation Working Group Issue 1.0, March 9th, 2011. HC 22 Session 2006-2007 | 22 November 2006
- [NAO 2006] National Autid Office, The Modernisation of the West Coast Main Line, Report by the Comptroller And Auditor General, HC 22 Session 2006-2007, November 22, 2006.
References
Please make sure all references are listed alphabetically and are formatted according to the Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.
Citations
List all references cited in the article. Note: SEBoK 0.5 uses Chicago Manual of Style (15th ed). See the BKCASE Reference Guidance for additional information.
Primary References
All primary references should be listed in alphabetical order. Remember to identify primary references by creating an internal link using the ‘’’reference title only’’’ (title). Please do not include version numbers in the links.
Additional References
All additional references should be listed in alphabetical order.