Investigate the problems at the terminal 5 opening, especially with the baggage handling system despite extensive simulated testing using thousands of bags and more than two thousand volunteers in the run up to the opening of T5
Identify the necessary risk strategies to be considered for such mega-projects, the benefits of such approaches, taking into account previous failed and successful projects, and any lessons to be learnt
Discuss the implementation approach adopted by BAA and the risk associated with this approach
Provide formative evaluation summarising key findings and conclusion based on evidence gathered from research
The terminal 5 project in addition to being a statement of intent for the future of British aviation was built with the aim of improving customer experience and to exhibit Heathrow as a world class international airport. The baggage handling system at T5 was designed to be the largest baggage handling system in Europe for a single terminal. The system consists of a main baggage sorter and a fast track system. The system was designed by an integrated team from BAA, BA and Vanderlande Industries of the Netherlands, with the aim of handling both intra-terminal and inter-terminal luggage. Its processing capacity was intended to be 70,000 bags a day. Bags are meant to undergo several processes on the way through the system, these include; automatic identification, explosives screening, fast tracking for urgent bags, sorting and automatic sorting and passenger reconciliation.
The scheduled completion and opening date was March 2008, and T5 was on time and on budget. This was a remarkable achievement especially in a sector where project delays and vast overspends are commonplace (the Millennium dome, Wembley stadium and the Scottish Parliament buildings were all opened late and cost a lot more than the original estimate). However, on its first day in operation, T5’s bespoke baggage system was affected by technical software problems, which led to a number of issues, such as cancelled flights, lost baggage, and substantial delays, but more importantly, BA’s challenge were its people issues and integrating teams of staff. Initial reports suggest that the day one issues were less to do with technology issues and more to do with inadequate staff training, and this was not just for one group of people but at all levels. Below is a summary of its problems on the opening day:
Hundreds of staff found it difficult finding the staff car park entrance
Check-in staff struggled with their systems, these problems ranged from very simple tasks such as logging into the baggage system to complex tasks
Security personnel who were totally ignorant of their new roles and had to be taken through new procedures in the morning in front of passengers
Ground staff and crews and ground staff getting lost in the huge building
Baggage handlers struggled to get a hang of the new baggage system
Baggage truck drivers got lost within the terminal and needed directions to the aircraft
Baggage drivers and handlers could not get luggage from the conveyors to the gates
On nine occasions, inspectors from the department of transport had managed to bypass security checks during trials of the terminal’s new systems and that the terminal’s alarm system was not working properly
Going through these problems therefore suggest that the entire problem was down to lack of adequate training or simply inappropriate appraisal of risk involved. This is very surprising as this was a very high profile project and taking into account that this was a simple 3 team process – get baggage, take baggage to aircraft and load baggage onto aircraft.
Training & System Testing Prior to Opening
Based on initial interviews with BA’s CIO, it would suggest that the human elements were given the importance it required. BA’s CIO, Paul Coby told CIO UK [in March 2007] “the IT work to support such a large-scale, new-build project was also going well. “Devices are deployed, connections are being integrated and 2007 will be testing year. The airline is moving onto the T5 systems, so they run for a year ready to operate at the new terminal when it opens in 2008”.
According to XXXXX, in the run up to the opening of T5 there were a series of overnight baggage-systems tests using thousands of bags, up to 2000 volunteers and full trials of the check-in procedure for all the IT systems. According to the spokesman for Vanderlande Industries, in testing the baggage handling system, emulation models were utilized broadly to test the low-level controls software, while computer programs took the place of the baggage handling system, and which behave (almost) the same as the part they replace. The report also suggests that for the high-level controls software, the emulation model was broadened by connecting the loose individual models into a large integrated system in which the physical equipment was replaced by a number of interconnected emulation models. According to a number of the volunteers who tested the system prior to its opening commented that the demos were extremely impressive and felt the system was ready in advance of its opening.
T5 System Simulation Prior to Opening
According to the spokesman for Vanderlande Industries, low-level emulation models were utilized in place of the physical transport equipment in each of the conveyor lines. The low and high level models that were developed produced the same electrical outputs in response to the same electrical inputs as their corresponding physical equivalent (motors, photo-electric cells, barcode scanners, etc), which in the view of both the software developers and management of BA, proof of extensive system testing. System interaction was facilitated with the use of control panels, and with the right frequency, set of bags or multiple bags were generated. During the testing, the conveyor motors were stopped and started utilizing different scenarios in order to generate as much errors as possible with the hope of fixing them. The spokesman also stated that the transport time between two photocells in emulation was equal to the actual time using the real equipment. The same measurement also applied to the total transport time.
In addition, during testing the T5 project, over 90 individual low-level emulation models were created as individual models were integrated into 5 different configurations. A separate team spent 4800 hours on building and testing these emulation models.
Questions: Training & Testing
But the first set of questions now has to be asked: how adequate was the tests and training were carried out in relation to T5’s baggage systems in advance of the opening? What were the results? What were the problems revealed? and what steps were taken to resolve the problems revealed? Were the tests re-run and, if so, what was the result? Was the right implementation strategy adopted? Or would it not have been better to open Terminal 5 on a phased basis, to make sure that all its systems were working before going fully operational?
The second set of questions to be asked would be: knowing that extensive simulation testing was carried out on the baggage system successfully; doesn’t that then suggest that carrying out simulated testing without the real customers is inadequate? With regards to the people issues, what sort of dry runs were carried out? If they were indeed adequate, why were the opening day hiccups not identified? Where there extra staff or volunteers in anticipation of potential glitches? If yes were these trained adequately? For every eventuality or possible scenario, what were the contingency plans?
In spite of the extensive testing carried out on the baggage system and the confidence which this would have placed on top management, from the experience on the opening day, we can conclude that in reality, the prospects of operating an airport terminal of such magnitude and scale would require more than simulated testing as the operations are virtually impossible to fully replicate. This then suggests that the risk management utilized by the BA was not robust to take the people issues into account. Good risk management might have come to the conclusion, if there was the possibility of failure.
Risk Management: Definitions
In order to manage risks we have to understand what a risk is. Smith and Merrit (2002) said that three essential aspects of risk are uncertainty, loss and time, see Figure 1.
Uncertainty: A project manager has to identify as many uncertainties as possible. A risk may or may not happen. This inherent uncertainty cannot be eliminated, but it can be made little clearer by clarifying the probability of occurrence of the risk, to get at better understanding of the consequences and alternatives if the risk occurs and determine the factors that influence the magnitude and likelihood of occurrence of the particular risk. This means that an uncertainty can never be completely eliminated, but it can be reduced to a level the project find tolerable. This means that even with the best plans there cannot be any guarantees that there will be no surprises .
Loss: A risk is always something that involves some kind of loss. If there is no loss possible, then the project is not concerned about the risk, because it cannot compromise the project .
Time: Associated with every risk there is a time where the risk no longer exists. Either the risk has occurred and the loss has been suffered or the potential problems that could cause the risk have been resolved and no longer pose a threat. It is important to know when this time has arrived so the risk can be removed from the agenda .
Among writers and in the literature there are differences in the meaning of risk management and risk analysis. Frosdick (1997) says that there are no clear views of the differences and what one writer defines as risk management another writer is calling it risk analysis. Frosdick‘s own view is that he separates them by saying that risk analysis is the sum of the processes of risk identification, estimation and evaluation and risk management is about planning, monitoring and controlling activities that are produced by the risk analysis activity.
The Association for Project Management (Chapman, Simister 2004) definition of risk analysis is similar to Frosdick‘s, they have however divided the risk analysis into two stages. The first stage is called the Qualitative Analysis and it is where risks are identified and subjectively assessed. These identified risks are then analysed in terms of e.g. cost and time estimates and that is called the Quantitative Analysis. Just like for Frosdick it is then followed by the risk management process. In their definition it is the process of formulating responses, both proactive and reactive ones.
Pennock & Haimes (2001) said that risk management could be represented in six steps, three each for risk assessment/analysis and risk management, where each step is a question.
What can go wrong? Identify as many risks as possible. The risks can be of any kind financial, time, resources etc. and no risk is too small to not be included .
What is the likelihood for the risk to occur? Try to measure how likely, or unlikely, it is for the risk to occur. Maybe some risks are dependent on each other .
What are the consequences? What will be the impact on the project if the risk occurs, is it a minor risk or maybe a stopping fault that endangers the whole project .
What can be done and what options are available? How to decrease the chance of a risk occurring, for example get more resources or have them readily available [2,3].
What are the tradeoffs in term of all costs, benefits and risks among the available options? For every risk there is somewhere a limit for how costly measures one can put in, where there is no economy in putting in more measures. Often the budget is not enough to eliminate all risks therefore one must choose which risks to put more emphasis on [2,3].
What are the impacts on current decisions on future options? 
The official definition provided by Professor James Garven, University of Texas at Austin is from the American Risk and Insurance Association: Risk management is the systematic process of managing an organization’s risk exposures to achieve its objectives in a manner consistent with public interest, human safety, environmental factors, and the law. It consists of the planning, organizing, leading, coordinating, and controlling activities undertaken with the intent of providing an efficient pre-loss plan that minimizes the adverse impact of risk on the organization’s resources, earnings, and cash flows.
Another definition given by Larry Krantz, Chief Executive of Euro Log Ltd in the UK, states that ‘A risk is a combination of constraint and uncertainty’. We all face constraints in our projects, and also uncertainty. So we can minimise the risk in the project either by eliminating constraints (a nice conceit) or by finding and reducing uncertainty .
The objectives of risk management/analysis
The Association for Project Management (Chapman, Simister 2004) defines Risk Management/Analysis as a process designed to remove or reduce the risks that threaten the achievement of project objectives. Properly undertaken it will increase the likelihood of successful completion of a project in terms of cost, time and performance objectives. PMBOK (PMBOK Guide, 2004) describes it similarly where they say that the objectives of project management are to increase the probability and impact of positive effects and decrease the probability and impact of events adverse to project objectives. Kendrick (2003) list seven benefits on the use of risk management:
Project Justification: Project risk management is undertaken primarily to improve the chances that a project will achieve its objectives. While there are never any guarantees, broader awareness of common failure modes and ideas that make projects more robust can significantly improve the odds of success. The primary goal of project risk management is either to develop a credible foundation for each project, showing that it is possible, or to demonstrate that the project is not feasible so that it can be avoided, aborted, or transformed .
Lower Costs and Less Chaos: Adequate risk analysis reduces both the overall cost and the frustration caused by avoidable problems . The amount of rework and of unforeseen late project effort is minimised. Knowledge of the root causes of the potentially severe project problems enables project leaders and teams to work in ways that avoid these problems. Dealing with the causes of risk also minimises "fire-fighting" and chaos during projects, much of which is focused short-term and deals primarily with symptoms rather than the intrinsic sources of the problems . Chadbourn (1999) describes it similarly when he likened the uncertainties to chaos, where a poorly designed project could be described as a room full of mousetraps, each with a ping pong ball . Before you know it, someone not under your control tosses in the first ball, thus mayhem and chaos erupts . In the ideal project the mousetraps are gone. In their place there is a network of dominos, where each action and reaction could be foreseen . It is within the role of organisations to try and identify these mousetraps and replace them with an orderly string of dominos .
Project Priority and Management Support: Support from managers and other project stakeholders and commitment from the project team are more easily won when projects are based on thorough, understandable information . High-risk projects may begin with lower priority, but a thorough risk plan, displaying competence and good preparation for possible problems, can improve the project priority . Whenever you are successful in raising the priority of your project, you significantly reduce project risk—by opening doors, reducing obstacles, making resources available, and shortening queues for services .
Project Portfolio Management: Achieving and maintaining an appropriate mix of ongoing projects for an organisation uses risk data as a key factor. The ideal project portfolio includes both lower- and higher-risk projects in proportions that are consistent with the business objectives .
Fine-Tuning Plans to Reduce Risk: Risk analysis uncovers weaknesses in a project plan and triggers changes, new activities, and resource shifts that improve the project. Risk analysis at the project level may also reveal needed shifts in overall project structure or basic assumptions .
Establishing Management Reserve: Risk analysis demonstrates the uncertainty of project outcomes and is useful in setting reserves for schedule and/or resources. Risky projects really require a window of time (or budget), instead of a single-point objective. While the project targets can be based on expectations (the "most likely" versions of the analysis), project commitments should be established with less aggressive goals, reflecting overall project risk. The target and committed objectives set a range for acceptable project results and provide visible recognition of project risk .
Project Communication and Control: Project communication is more effective when there is a solid, credible plan. Risk assessments also build awareness of project exposures for the project team, showing how painful the problems might be and when and where they might occur. This causes people to work in ways that avoid project difficulties. Risk data can also be very useful in negotiations with project sponsors. Using information about the likelihood and consequences of potential problems gives project teams more influence in defining objectives, determining budgets, obtaining staff, setting deadlines, and negotiating project changes .
Risk Assessment & Risk Control
There are two stages in the process of Project Risk Management, Risk Assessment and Risk Control. Risk Assessment can take place at any time during the project, though the sooner the better. However, Risk Control cannot be effective without a previous Risk Assessment. Similarly, most people tend to think that having performed a Risk Assessment, they have done all that is needed. Far too many projects spend a great deal of effort on Risk Assessment and then ignore Risk control completely .
Risk Assessment has three elements:
In this element, the entire project plans are explored, with special focus on areas of uncertainty .
In this element, the requirement is to specify how the areas of uncertainty will have an impact on the performance of the project, either in duration, cost or meeting the users’ requirements .
At this stage the requirement is to establish which of the Risks identified should be eliminated completely . This step is only is carried out due to the potential extreme impact, which should have regular management attention, and which are sufficiently minor to avoid detailed management attention .
In the same way, Risk Control has three elements, as follows:
According to Mobey et al (2002), risk mitigation would include taking the necessary actions that are possible in advance to reduce the effect of Risk. It is better to spend money on mitigation than to include contingency in the plan .
Plan for Emergencies
For all those Risks which are deemed to be significant, have an emergency plan in place before it happens .
Measure and Control
This involves tracking the effects of the risks identified and managing them to a successful conclusion .
There are different strategies and methods that have different approaches toward risk management. JISC (Joint Information Systems Management) says that the focus for risk management should be on risks related to the particular project, not project management in general (https://www.jisc.ac.uk/proj_manguide15.html). The overall goal according to Kendrick (2003) for risk management in a single project is to establish a credible plan consistent with business objectives and then to minimise the range of possible outcomes. That is why risk management in a project is about identifying potential risks, analyse the ones that have the greatest likelihood of occurring, grade their different levels of impact on the project and define a plan of how to avoid the risk and if it occurs how to reduce its impact (Heldman, 2005).
Smith & Merrit (2001) sees risk strategy as a five step process. Figure 3 shows the flow through the five-step process and lists deliverables from each step:
Step 1: Identify risks that you could encounter across all facets of the project .
Step 2: Analyse these risks to determine what is driving them, how great their impact might be, and how likely they are .
Step 3: Prioritise and map the risks so that you can choose those most important to resolve .
Step 4: Plan how you will take action against the risks on this short list .
Step 5: On a regular basis, monitor progress on your action plans, terminate action plans for risks that have been adequately resolved, and look for new risks .
Frosdick (1997) also mentioned Strutt‘s, definition of the concept of risk analysis that is a seven stage process.
Systematic assessment (item by item – question every part of the system) .
Identification of risks .
Assessment of risks (frequencies and consequences) .
Establish acceptable/tolerable levels of risk .
Evaluate the risks. Are they acceptable? Can they be reduced and at what cost?
Determine whether the risks are as low as reasonably practicable .
Determine risk reduction measures where appropriate .
Risk Assessment & Evaluation
There are many ways and different techniques to evaluate what the risks are, what the effect they have on the project and what measures can be put in if the risks should occur . Risk assessment is by most people divided into two areas, Quantitative Risk Analysis and Qualitative Risk Analysis.
In its most basic form the formula for risk quantification is: ―Rate of occurrence‖ multiplied by the ―impact of the event‖ = risk. Methods based on this method are often called ―expected value analysis‖ and include models like Annualized Loss Expectancy (ALM), the Courtney formula, the Livermore Risk Analysis Methodology (LRAM) and Stochastic Dominance (Snyder, Rainer Jr., Carr 1991). The advantages of Quantitative Risk Analysis methodologies are that they are good at identifying the most critical areas that, if something happens, will have the largest impact on the project. There are also disadvantages to Quantitative Risk Analysis. When one measures the probability of damage to the project the quantitative approach tends to average the events leading up to a problem (Snyder, Rainer Jr, Carr 1991).
Qualitative methods attempts to express risks in terms of descriptive variables rather than an economic impact. These approaches are based on the assumption that certain threat or loss of data cannot be appropriately expressed in terms of dollars or pounds and that precise information is impossible to obtain. These methodologies include Scenario Analysis/Planning, Fuzzy Metrics and questionnaires (Snyder, Rainer Jr., Carr 1991). The advantages of Qualitative Risk Analysis methodologies are that they save time, effort and expense over quantitative methods. This is because assets do not need exact values in dollars or pounds nor do threats need to have exact probabilities. It is also a valuable methodology in identifying significant weaknesses in a risk management portfolio. There are disadvantages with this method as well. Qualitative Risk Analysis is inexact, the variables used (e.g. low, medium and high) must be understood by all parties involved (Snyder, Rainer Jr., Carr 1991).
Once risks have been identified and evaluated they have to be responded to in some way. Wideman (1992) lists seven basic responses on identified risks:
Recognised but no action taken (absorbed as a matter of policy)
Avoided (by taking appropriate steps)
Reduced (by an alternative approach)
Shared (with others, e.g., by joint venture)
Transferred (to others through contract or insurance)
Retained and absorbed (by prudent allowances)
Handled by a combination of the above
Dorfman (1997) says that all techniques to manage the risk fall into one or more of these four major categories (remembered as the 4 T’s):
Tolerate (aka Retention)
Treat (aka Mitigation)
Terminate (aka Elimination)
Transfer (aka Buying Insurance)
Bliss (2005) listed these five types of similar risk responses as Dorfman and Wideman.
Risk avoidance: Also known as risk removal or risk prevention, risk avoidance involves altering the original plans for the project so that particularly risky elements are removed. It could include deciding not to perform an activity that carries a high risk. Adopting such avoidance techniques may seem an obvious way to deal with all risks. However, often the areas of the project that involve high risks are also the areas of the project that potentially contain the highest worth or the best value for money. Avoiding such risks may also result in removing potentially the ‘best bits’ of a resource, and an alternative strategy that retains these risks may be more appropriate .
Risk reduction: Risk reduction or risk mitigation involves the employment of methods that reduce the probability of a risk occurring, or reducing the severity of the impact of a risk on the outcome of the project. The loss of highly skilled staff is a considerable risk in any project and not one that can be totally avoided. Suitable risk mitigation could involve the enforcement of a notice period, comprehensive documentation allowing for replacement staff to continue with the job at hand and adequate management oversight and the use of staff development programmes to encourage staff to stay .
Risk transfer: Risk transfer moves the ownership of the risk to a third party normally by contract. This also moves the impact of the risk away from the project itself to this third party .
Risk deferral: The impact a risk can have on a project is not constant throughout the life of a project. Risk deferral entails deferring aspects of the project to a date when a risk is less likely to happen. For example managing the expectations users have about the content and delivery of a resource can be time-consuming, one way to reduce this risk is by not making a web resource available until user testing is complete .
Risk retention: Whilst a certain number of the risks to the project originally identified can be removed by changing the project plan or dealt with by transferring the responsibility of the risk to third parties inevitably certain risks have to be accepted as a necessary part of the project. All risks that have not been avoided or transferred are retained or accepted risks by default .
Previous Successful Project: St Pancras International Rail Station
According to XXXXXX, before St Pancras International rail station was opened; a number of days were devoted to testing all the systems and processes, using an army of thousands of volunteer ‘passengers’. These tests were carried out much before the opening day, thus providing enough time to resolve issues that might have occurred during testing .
By carrying out the testing in phases much long before the opening, members of staff were able to familiarize themselves with the systems and get actual hands-on experience before the station was opened to Eurostar traffic. Dry-runs were carried out as well with the vital lessons were learnt and adjustments made before exposing paying customers to the St Pancras experience. Inevitably the result was that on the opening day, everything went without glitches on the first day of international service .
Previous Failed Project: Denver International Airport
The Denver International Airport was scheduled to open on October 31, 1993 with all three of its concourses fully running on the BAE automated baggage handling system that. On February 28, 1995, the new airport finally opened. Its opening came sixteen months late. The automated baggage system was supposed to improve baggage handling by using a computer tracking system to direct baggage contained in unmanned carts that run on a track. BAE systems presented the City of Denver with a proposal to develop “the most complex and automated [and integrated] baggage system ever built. Original target opening date for the airport was (delayed seven times over the next three months). City of Denver invited reporters to observe the first test of the baggage system without notifying BAE. This was a public disaster! Reporters saw piles of disgorged clothes and other personal items lying beneath the Telecar’s tracks.
Lots of mechanical and software problems plagued the automated baggage handling system. When the system was tested, bags were misloaded, sent to different routes, and fell out of automated telecarts, thus causing the system to jam. The automated baggage system still continued to unload bags even though they were jammed on the conveyor belt, because the photo eye at this location could not detect the pile of bags on the belt and hence could not signal the system to stop.
One of the lessons BA and BAA might have been learnt from the Denver project, was that BAE actually built a prototype of the automated baggage handling system in a 50,000 sq. ft. warehouse near its manufacturing plant in Texas. But as similar to the T5 project, there was no evidence of adequate training and the results from simulation testing has been proven to be different to a real world scenario with real customers. I addition, research also shows that BAE had given an initial estimate of at least a year to test the system and get the system up and running, but United airlines and the other stakeholders pressed for a much shorter timeframe. City of Denver got the same story from technical advisers to the Franz Joseph Strauss airport in Munich (that less complicated system had taken 2 years testing and was running 24 hours a day for 6 months before the airport opened.
Risks recognised early in the Project
– Very large scale of the project.
– Enormous complexity.
– Newness of the technology.
– Large number of entities to be served by the system.
– The high degree of technical and project definition uncertainty.
PMBOK (PMBOK Guide, 2004) lists five tools and techniques for risk identification: documentation reviews, information gathering techniques, checklist analysis, assumption analysis and diagramming techniques.
Risk identification and analysis is a specialist business, but generally it can’t be done without first consulting key personnel, typically through interviews, questionnaires and workshops. Risk workshops are particularly effective in bringing together all those to be affected by the initiative, thus ensuring that everyone gets a chance to present their case, hear different points of view, raise and discuss ideas, and be more circumspect and candid .
Documentation Reviews: A structured review may be performed of project documentation, including plans, assumptions, prior project files, and other information. The quality of the plans, as well as consistency between those plans and with the project requirements and assumptions, can be indicators of risk in the project .
Information Gathering Techniques: Examples of information gathering techniques used in identifying risk can include:
Brainstorming: The goal of brainstorming is to obtain a comprehensive list of project risks. The project team usually performs brainstorming, often with a multidisciplinary set of experts not on the team. Ideas about project risk are generated under the leadership of a facilitator 
Delphi technique: The Delphi technique is a way to reach a consensus of experts. Project risk experts participate in this technique anonymously. A facilitator uses a questionnaire to solicit ideas about the important project risks. The responses are summarised and are then re-circulated to the experts for further comment. Consensus may be reached in a few rounds of this process. The Delphi technique helps reduce bias in the data and keeps any one person from having undue influence on the outcome .
Interviewing: Interviewing experienced project participants, stakeholders, and subject matter experts can identify risks. Interviews are one of the main sources of risk identification data gathering .
Root cause identification: This is an inquiry into the essential causes of a project‘s risks. It sharpens the definition of the risk and allows grouping risks by causes. Effective risk responses can be developed if the root cause of the risk is addressed .
Strengths, weaknesses, opportunities, and threats (SWOT) analysis: This technique ensures examination of the project from each of the SWOT perspectives, to increase the breadth of considered risks .
Checklist Analysis: Risk identification checklists can be developed based on historical information and knowledge that has been accumulated from previous similar projects and from other sources of information. The lowest level of the RBS can also be used as a risk checklist. While a checklist can be quick and simple, it is impossible to build an exhaustive one. Care should be taken to explore items that do not appear on the checklist. The checklist should be reviewed during project closure to improve it for use on future projects .
Assumptions Analysis: Every project is conceived and developed based on a set of hypotheses, scenarios, or assumptions. Assumptions analysis is a tool that explores the validity of assumptions as they apply to the project. It identifies risks to the project from inaccuracy, inconsistency, or incompleteness of assumptions .
Risk Management Perspectives
The first is precedent – how were risks handled before in similar circumstances? Much has been documented in this area in the form of case studies and anecdotes. Second, the current position needs to be fully considered: what are the specific, known and speculative risks relating to all the relevant factors? The workshop provides a good starting point to uncover evident and less apparent issues. But a third and complementary approach is also important – brainstorming or envisaging the totally unexpected, perhaps incredible, but nevertheless possible scenarios .
Lessons fro T5 Project
Training: People are the most important part of any project
According to XXXXXX, some middle managers and staff representatives within BA had warned of the apparent lack of training weeks before the opening of T5. As I stated previously system simulation testing was carried out initially with a few members of staff, but it was reported that subsequent tests which would have included all members staff in the baggage section was called off. It beats my imagination why this was not spotted as a potential risk. It would therefore seem that although training was carried out, but it was the wrong type of training, not sufficient, not with all members of staff, and it was not taken as part of a coherent management plan, the right sort of training would have made some difference.
T5 Risk Assessment: Reliance on System vs Processes
According to Kerzner (2003), for high profile projects, it is imperative to focus on testing the entire business processes and the systems as well rather than focus on system testing only. This concept comes from the tried and tested model office testing concept, whereby every detail in each process is tested as a separate entity. If such was applied to the T5 project, even processes such as members of staff finding their way to the car park would have been included.
T5 Risk Assessment: Scale & Volume
From the newspaper editorials, it can be observed that management misjudged in assuming that staff would simply pick up on the demands of terminal 5, without realising the expected volume and demands of the new terminal which was in sharp contrast to what they were used to in terminals 1-4. According to Chapman et al (2004), with the introduction of new systems or approach to working in an environment, there is usually a drop in performance, which can be attributed to glitches in getting used to the new system or way of carrying out work.
Contingency and failure of Risk Assessment
From the editorials analysed, it would seem that with the training that was carried out on the T5 baggage system, BA management did not act on the findings or results of the test carried out. This can only be described as blatant disregard or misunderstanding on the management of risk or gross incompetence.
According to Saff et al (2004), most software systems fail due to inadequate testing of system in its entirety, as most organizations or software developers are more interested in testing the system to scale through the process, rather than testing to reveal bugs and inaccuracies which is the fundamental purpose of testing in the first place .
Integrating Project Control Methods
According to Eason (1988), one of the areas that most organizations overlook when introducing a new system is change overload. This is a major risk factor as implementing so much changes too quickly without the adequate resources to deal with such a change is courting trouble as the collapse would be inevitable . First of all organizations will need to take into account the type of change to be effected and the corresponding management system / resources to handle the new systems and address any impending risk which might arise .
From the editorials analysed suggests that the “Big Bang” implementation method was utilized in the T5 project. According to Nah et al (2003), this is one of the most difficult kinds of implementation, as existing system is being discontinued in its entirety as the end of one day and a new system replaces it on the following day. A highly publicised example in recent years was the overnight switch of the London Stock Market to electronic trading in 1986.
Limitations of this Approach
Complex System Integration
Although in principle, this might have appealed as a very quick process in switching over to terminal 5, however, in practice it is a method that is fraught with so much risk as the implementation of over 21,000 PC’s, and a very complex baggage system is very risky due to the need for incorporating training and system integration which would take most members of staff a long while to master.
Human Resource Limitations
Implementing a big-bang approach would require lots of expert resources who would need very detailed training over a long period of time before the opening. Whilst this should have been a risk factor that BA should have incorporated regardless of the implementation approach, however, studies from previous projects have shown that this is difficult and is best utilized in a phased implementation approach.
One popular way of minimising the risks to the on-going, work is to introduce the new system alongside the old one and to run them in parallel until everybody is confident that the new system will be effective .
The problems of making massive changes can be eased by phasing in the changes over a period. There are two ways in which large-scale changes can be subdivided to facilitate phased introduction. First, the functionality of the technical system can be introduced in phases so that the basic task processes can be supported in the early stages and subsequently facilities can be added which support, for example, decision-making tasks. Second, it may be possible to introduce the system in different parts of the organisation at different times. A combination of these two approaches can also be used .
Trial and Dissemination
This strategy explicitly recognises that will be “teething troubles” when a new system is introduced. By holding an essential trial or pilot project before embarking upon full-scale implementation. This strategy provides a valuable opportunity to prepare thoroughly for implementation before it is in the throes of full-scale change. However, many organisations fail to make good use of the opportunities that the trial presents .
The alternative to a revolutionary change is gradual evolution. The growing sophistication and flexibility of technology is making the incremental implementation of system and increasingly practical proposition. When users are discretionary and powerful and their needs are varied, not to say idiosyncratic, the service has to be tailored to individuals and incremental implementation may be the only option that is acceptable to users .
 A Guide to the Project Management Body of Knowledge, (2004). Project Management Institute, 3rd edition (PMBOK® Guide).
Auguston, K. (1994), "The Denver Airport: A lesson in coping with complexity," Modern Materials Handling, Oct., pp. 40 – 45.
 Brandon D. (2006), Project Management for Modern Information Systems, IGI Publishing
 Brady, Tim, Davies, Andrew, Gann, David and Rush, Howard (2006). Learning from Landmark Projects: a Study of Heathrow Terminal 5. In IRNOP VII Project Research Conference, 11-13 Oct 2006, Xi’an, China.
Breier Neidle Patrone Associates (1990) DIA — Denver International Airport, Baggage Handling Systems, Conceptual Design Study Final Report, BNP Doc. Ref. 9016R.008,19 Oct.
 Carr H., Rainer Jr. R.K. & Snyder C. (1991), ‗Risk analysis for information‘, Journal of Management Information Systems, 8 (1), pp. 129-147
 Chapman C. & Simister S. (2004). The PRAM process Project Risk Analysis and Management Guide, 2nd Edition. APM Publishing Ltd.
 Company History (2001) Waterfront the journey so far. [Video VHS] Waterfront Consultants Media Archives.
 DfT (2004), Channel Tunnel Rail Link & London Underground Ltd Works – King’s Cross: Review of Phase 2, Department for Transport, London.
 Dinsmore P. & Cabanis-Brewin J. (2006), The AMA Handbook of Project Management, Second Edition, AMACOM
 Doernemann H. (2002),‘Tool-Based Risk Management Made Practical‘, Joint IEEE International Requirements Engineering Conference (RE’02), p. 192
 Donaldson A.J.M., (2002). Narrative Case Study of the Denver Airport Baggage Handling System, SFC TR 2002-01, https://www.cs.mdx.ac.uk/research/SFC/Reports/TR2002-01.pdf
 Dorfmann & Mark S. (1997), Introduction to Risk Management and Insurance (6th ed.), Prentice Hall
 Eason, K. D. (1988). Information technology and organisational change. London: Taylor and Francis
 Frosdick S. (1997) ‗The techniques of risk analysis are insufficient in themselves‘, Disaster Prevention and Management, 6 (3), pp. 165-177
 Guru Dutta, G Srikanth (2004). Operating Strategies Case Studies, BAA’s T5: Novel Project Management BAA Plc. An Icfai Business School Case Development Centre publication
 Gwynne, S., Galea, E.R., Owen, M., Lawerence, P.J. and Filippidis, L. (1999), ‘A Review of the Methodologies Used in the Computer Simulation of Evacuation from the Built Environment’, Building and Environment, 34: 741-749.
 Heldman K. (2005) Project Manager’s Spotlight on Risk Management, Sybex
 Implementation Insight (2005) Project Profile. [Video VHS] Waterfront Consultants Media Archives.
 Kendrick T. (2003) Identifying and Managing Project Risk: Essential Tools for Failure-Proofing Your Project. AMACOM
 Kerzner H. (2003) Project Management: A Systems Approach to Planning, Scheduling, and Controlling, Eighth Edition, John Wiley & Sons
 Westland J. (2006), The Project Management Life Cycle: Complete Step-by-Step Methodology for Initiating, Planning, Executing & Closing a Project Successfully, Kogan Page
 Lewis P. & Wong L. (2005), Accelerated Project Management: How to Be the First to Market, Wong McGraw-Hill
 Mahoney, J (2000): Identify misaligned roles that cause project failure, Gartner, TechRepublic. Project Management 1 Readings, Australian Computer Society
 Mobey A. & Parker D. (2002) ‗Risk evaluation and its importance to project implementation‘, Work Study, 51(4), pp. 202 – 208
 Nah, F. F. and Lau, J. L. (2003). Critical factors for successful implementation of enterprise systems. Business Process Management, 7(3), 285-296.
 Nakanishi, Y., Kim, K., Ulusoy, Y. and Bata, A. (2003), Assessing Emergency Preparedness of Transit Agencies: A Focus on Performance Indicators, Annual Transportation Research Board, USA
 RSSB (2003), Managing Large Events and Perturbations at Stations: Passenger Flow Modeling Technical Review, Railway Safety Standards Board, London.
 Schuyler J. (2001), Risk and Decision Analysis in Projects, Second Edition, Project Management Institute
 Smith P & Merrit G. (2002) Proactive Risk Management, Productivity press
 Taylor J. (2004), Managing Information Technology Projects: Applying Project Management Strategies to Software, Hardware, and Integration Initiatives, AMACOM
 Yin R. K. (2003). Case study research design and methods. Third edition. Thousand Oaks: Sage publication.
 Whitten N. (2005), Neal Whitten’s No-Nonsense Advice for Successful Projects, Whitten Management Concepts
 Wideman R. M. (1992.) Risk Management, A guide to Managing Project Risks & Opportunities, Project Management Institute
 Whitten N. (2005), Neal Whitten’s No-Nonsense Advice for Successful Projects, Whitten Management Concepts
 Saff. D and Ernst. M.D., (2004). An Experimental Evaluation of Continuous Testing
During Development. In ISSTA ’04: Proceedings of the 2004 ACM SIGSOFT International Symposium on Software Testing and Analysis, pages 76-85, Boston, MA, USA.
What did go wrong at Terminal 5? BBC
Terminal 5 fiasco: The new ‘Heathrow hassle’. The independent. By Danny Fortson on 28/03/2008
Technology not to blame for Terminal 5 fiasco. A case study from silicon website, by Tim Ferguson. 8/05/2008
Roger Collis: How to avoid Heathrow’s Terminal 5. International herald tribune. Roger Collis. 17/04/2008.
Lost luggage, delays, stress and tears welcome to Terminal 5. Published Date: 28 March 2008. By ANDREA VANCE
Baggage halted at £4.3b T5. A report by the BBC on 28/03/2008
IT failure at Heathrow T5: What really happened. Posted by Michael Krigsman. 7/04/2008.
Lack of software testing to blame for Terminal 5 fiasco, BA executive tells MPs. A blog entry posted at the Computer Weekly website on the 8/05/2008.
Crisis management lessons from Terminal 5. A write up by Charlie Maclean-Bristol MBCI FEPS, director, PlanB Consulting on the continuity website. 2/04/2008.
Terminal disgrace: Poor training and computer failings to blame for T5 chaos as flights fiasco to last into the weekend. Blog entries on this is London website. 29/03/2008.
BA cancels 66 more flights over new terminal fiasco in Britain an editorial at yahoo business website. By Ben Perry. 29/03/2008
Heathrow Terminal 5 chaos could last all week By David Millward, Transport Editor the telegraph. 21/04/2008
Terminal disgrace: Poor training and computer failings to blame for T5 chaos as flights fiasco to last into the weekend. Daily mail entry. 28/03/2008
Terminal 5 baggage losses ‘twice BA figures’ By David Millward, Transport Editor, the telegraph. 21/04/2008