Heathrow Terminal 5
| (13 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | ''Developed by Sanna Monjezi'' | |
| − | '''The Heathrow terminal 5 (T5) project''' was created with the intent of easing the congestion of the airport, centralizing all British Airways flights, and increasing the revenue from other airlines. Due to the size of the project both in size and budget it was complex to manage | + | |
| − | The project consisted of a control tower, two satellite buildings, and supporting infrastructure. The latter included river diversions, connections between terminals, and a train station. This resulted in 16 major projects, and 147 sub-projects, all separate from each other and involving over 60 contractors in total. <ref>[''http://www.airport-technology.com/projects/heathrow5/''] ''London Heathrow Airport Expansions (LHA/EGLL), United Kingdom | + | |
| + | '''The Heathrow terminal 5 (T5) project'''also known as the T5 project, was created with the intent of easing the congestion of the airport, centralizing all British Airways (BA) flights, and increasing the revenue from other airlines. Due to the size of the project both in size and budget it was complex to manage. This was not ameliorated by the fact that it took eight years to get government approval. The project consisted of a control tower, two satellite buildings, and supporting infrastructure. The latter included river diversions, connections between terminals, and a train station. This resulted in 16 major projects, and 147 sub-projects, all separate from each other and involving over 60 contractors in total. <ref>[''http://www.airport-technology.com/projects/heathrow5/''] ''London Heathrow Airport Expansions (LHA/EGLL), United Kingdom | ||
'' </ref> | '' </ref> | ||
| − | Due to the fact that construction projects by nature are prone to delays it’s quite remarkable that | + | Due to the fact that construction projects by nature are prone to delays it’s quite remarkable that the T5 project was completed on time, within budget, and with less fatalities than expected. The reason for this was the fact that the contracts between British Airways and the contractors were quite unique for their time. The contracts were unique because all contractors pooled together risk payments and were promised a share in the event that their work was finished on time. This proved to be an effective incentive not only to be on time and on budget, but also to nudge the contractors towards better teamwork as the prospects of getting the bonuses was higher that way. The result was a construction project finished on time and on budget with fewer fatalities than there would normally be on a project of that size. Unfortunately there were issues on the operation level that led to bad reviews on the opening week that overshadowed the success of the construction project. <ref>[''http://www.the-chiefexecutive.com/features/feature68469/''] 'Why stakeholders matter'' </ref> |
| Line 9: | Line 10: | ||
T5 project is considered a mega project; due to the fact that these are ''"projects of a significant cost that attract a high level of public attention or political interest because of substantial direct and indirect impacts on the community, environment, and budgets"''. <ref>[''http://flyvbjerg.plan.aau.dk/whatisamegaproject.php''] ''What is a Megaproject?'' </ref> The client and owner of Heathrow Airport, and by extension T5, in this case is BAA. In this article only one of the contractors will be singled out; Lain O’Rouke. This is due to the fact that LOR grew with the project in such a way that it has completely changed the shape of the organization today. | T5 project is considered a mega project; due to the fact that these are ''"projects of a significant cost that attract a high level of public attention or political interest because of substantial direct and indirect impacts on the community, environment, and budgets"''. <ref>[''http://flyvbjerg.plan.aau.dk/whatisamegaproject.php''] ''What is a Megaproject?'' </ref> The client and owner of Heathrow Airport, and by extension T5, in this case is BAA. In this article only one of the contractors will be singled out; Lain O’Rouke. This is due to the fact that LOR grew with the project in such a way that it has completely changed the shape of the organization today. | ||
=Phases of T5 project = | =Phases of T5 project = | ||
| − | The T5 project in question can be divided into 4 phases shown in figure 1. It should be noted that the planning phase contains a 4-year long period of inquiry (1995-1999) and subsequent ''"consent to proceed with construction"''<ref name="Davies, Gann, Douglas"> Andrew Davies, David Gann,Tony Douglas"> ''Innovations in Megaprojects: Systems Integration At London Heathrow Terminal'', California Management Review, 2009</ref>. in 2001. The T5 project is one of the longest in British history and cost around £80, cementing its label as a mega project. | + | The T5 project in question can be divided into 4 phases shown in figure 1. It should be noted that the planning phase contains a 4-year long period of inquiry (1995-1999) and subsequent ''"consent to proceed with construction"''<ref name="Davies, Gann, Douglas"> Andrew Davies, David Gann,Tony Douglas"> ''Innovations in Megaprojects: Systems Integration At London Heathrow Terminal'', California Management Review, 2009</ref>. in 2001. The T5 project is one of the longest in British history and cost around £80, cementing its label as a mega project. Even though all of the phases are of great importance to the success of the project, only the planning phase is described. This is due to the fact that the planning phase bye nature of a hierarchical model sets the serves as a firm foundation for the project. The rest of the phases are all depending on the fact that the planning phase is completed as indicated, which includes the use of specific processes, roles and responsibilities as well as technologies. These activities may seem excessive, but they are needed in other phases, and thereby crucial in leading the project to fruition |
| − | + | ||
[[File:ProjetLifeCycle.png|thumb|right|300px|Figure 1: Life cycle of T5 project (click to zoom)]] | [[File:ProjetLifeCycle.png|thumb|right|300px|Figure 1: Life cycle of T5 project (click to zoom)]] | ||
| − | == | + | ==Planning phase== |
| + | In 1990 Sir John Egan became the CEO of BAA and would continue to work through 1999. He had previously worked for Jaguar, a company that seemed to be very close to shutting down, but he turned the trend and is largely credited for the success.<ref>[''http://www.birminghampost.co.uk/news/local-news/how-jaguar-found-new-life-9678099''] ''How Jaguar found a new life after near collapse'' </ref> Egan used his knowledge about Lean production from the automobile industry and attempted to apply it the construction of T5. Furthermore he recognized that projects are often unique and therefore approached as a ''"blank slate"''<ref name="Davies, Gann, Douglas"> Andrew Davies, David Gann,Tony Douglas"> ''Innovations in Megaprojects: Systems Integration At London Heathrow Terminal'', California Management Review, 2009</ref>, as BAA did prior to his arrival. In an effort to ameliorate this he wanted to create standardized parts of projects in an effort to apply Lean principles, that emphasized simplification and standardized tasks. | ||
| + | |||
| + | Egan gathered a team to explore practices, principles, and technologies from different industries in an effort to see what would work in the T5 project. Later on he would establish an organization that worked independently from BAA in an effort to ''"provide the freedom of choice needed to promote experimentation and innovation"'''<ref name="Davies, Gann, Douglas"> Andrew Davies, David Gann,Tony Douglas"> ''Innovations in Megaprojects: Systems Integration At London Heathrow Terminal'', California Management Review, 2009</ref>. Later on BAA would establish a Continuous Improvement Project Process (CIPP) in an effort to ''"provide a set of standardized and repeatable time-sequenced tasks, milestones, and stage-gates to deliver cost-effective and profitable projects"'''<ref name="Davies, Gann, Douglas"> Andrew Davies, David Gann,Tony Douglas"> ''Innovations in Megaprojects: Systems Integration At London Heathrow Terminal'', California Management Review, 2009</ref>. The projects in question would have a budget between $4M-$8M. CIPP also looked into the design process by working with modular design, so that the construction processes would have similar construction processes, despite being vastly similar. This was not done with the sole intent to apply these processes to T5, but for capital projects. Furthermore it gave BAA knowledge about suppliers’ capabilities, which was used in T5. | ||
| + | |||
| + | =Hierarchical model of project processes= | ||
| + | The processes of a mega project have been developed into a hierarchical model seen in figure 2 <ref name="Davies, Gann, Douglas"> Andrew Davies, David Gann,Tony Douglas"> ''Innovations in Megaprojects: Systems Integration At London Heathrow Terminal'', California Management Review, 2009</ref>. In the T5 project BAA was the systems integrator and thereby responsible for all management and coordination throughout the project. It is preferential to use such a model in case of a mega project, as it indicates which phases are to be done and in which order. Furthermore the model illustrates the order of which activities in the phases are to be completed. This is preferential because they are thought of in advance to aid the next phase and even more so, they encourage a more rigid division of roles and responsibilities. The division of roles and responsibilities is paramount in projects in general and even more so in complex project, where the amount of people involved is extremely high. If these people are not clear on their roles and responsibilities they run the risk of misunderstanding their responsibility and thereby waste time. | ||
| + | [[File:MegaProjectProcesses.png|thumb|right|300px|Figure 2: Processes of a Mega Project (click to zoom)]] | ||
| + | |||
| + | ==Research of pitfalls from similar projects== | ||
| + | BAA approached this responsibility by starting with research into similar projects. These were divided into two categories: construction projects in the UK with a budget over $2B and all airport constructions in the world. The timeframes were 10 years and 15 years respectively. This enabled the research team to recognize problem areas and look for efforts to improve them. | ||
| + | |||
| + | The research showed that no major projects in the UK or international airports had been completed and successfully accomplished any goals pertaining to time, budget, quality, and safety. The research on airports around the world proved no better, but gave a numerical estimate of how much the T5 project could be over budget etc. On the other hand the team divided the problem areas into two areas: ''"lack of collaboration among project partners; and clients’ reluctance to assume responsibility for project risks."''<ref name="Davies, Gann, Douglas"> Andrew Davies, David Gann,Tony Douglas"> ''Innovations in Megaprojects: Systems Integration At London Heathrow Terminal'', California Management Review, 2009</ref> Furthermore, the first Project Director of T5 noted that most projects failed due to a lack of sufficient funding of the design phase. | ||
| + | ==Project processes== | ||
| + | These processes nicely complement each other to form a foundation of organization and management throughout the project. First of all the T5 legal agreement was created in order to bind all parties to a structured workflow of specific tasks and tools. Moreover it serves as an aid throughout all phases of the project. The challenge of T5 was that it had a lot of contractors and was dependent on lots of technologies that BAA was not intimately familiar with. This was ameliorated by the fact that the BAA (in this case: the client and systems integrator) assumed all responsibility of risks and gave the contractors an incentive to work together. More importantly, a single-model environment (SME) enabled coordination throughout phases and across design disciplines. This is due to the fact that multiple users can share designs and the SME will detect any clashes. This decreases the risk of mistakes in the design phase that could potentially be found out during the construction phase. These types of mistakes are costly due to the fact that they inhibit the project moving along thus creating chaos. Solutions to these types of mistakes are often not completely thought out due to the fact that they are created in a hurry and don’t undergo the same process as all the other decisions. Adding to this, SME enables design disciplines to create a construction that is favorable during operation as well. This could be by adding enough space to make it easier for the person doing the electrical repairs to actually see what’s going on without e.g. visual aids due to the space being too small. This is favorable in terms of work environment laws. Lastly SME is a great tool during the planning phase as it is a visual aid of the construction site and it’s entries, walkways, exists. This will be further detailed in the next section. Tying these pieces together it is crucial to incorporate project and program management processes as these manage both the main project, which is T5, but also all the sub-projects. | ||
| + | |||
| + | ==Operational processes== | ||
| + | During the project processes, SME served as a tool for planning the logistics of the construction site. Geographically the site was placed near a busy highway and to make matters worse the construction site only had one entry. LOR used to work by buying supplies as cheaply as possible and having them sent to the construction site for assembly etc. During the T5 project this would entail “8000 workers a day and nearly 250 deliveries of materials per hour” <ref name="Davies, Gann, Douglas"> Andrew Davies, David Gann,Tony Douglas"> ''Innovations in Megaprojects: Systems Integration At London Heathrow Terminal'', California Management Review, 2009</ref>], which would be impossible logistically. For this reason modular pre-assemblies and just-in-time logistics were perfect as they enabled the producers to test the assembly before arriving at the construction site. Pre-assembly and modular construction often involves off-site fabrication, which decreases the risk of mistakes and accidents on the construction site. This is due to the fact that all safety factors that need to be taken into consideration to assemble or fabricate something are gone. There are no parts of the constriction site that need to be isolated, and there is no need to take any extra safety precautions on the construction site. This should not be taken lightly as the legalities regarding work environment and safety are quite extensive. It is therefore favorable to make use of off-site fabrication as it frees up a lot of resources that would be otherwise engaged with safety regulatory processes, and reduces the chance of extra-work due to mistakes. The latter is meant to indicate that for the T5 project, pre-assembled modular were tested off-site to ease the final construction on the construction site. Furthermore, it reduced the risk of supplies being delivered at the wrong place, and needing them to be moved during the construction process. Often times, the supplies are quite heavy and work environment laws have limits on how much a labor is allowed to carry. The case could also be that the supplies can only be moved by machinery, which may be used for a different purpose at the time. Pre-assembly and modular-construction therefore reduce all sorts of risks, enable the producers to test the object and can ensure that the project stays within budget due to the lack of unforeseen expenses. LOR, which was responsible for a large portion of the construction used a “consolidation facility” that meant that modules and components were transported to a temporary storage unit, so that they could be transported to the construction site just-in time. This was an effective way of ensuring that the project stayed within the given timeframe. | ||
| + | |||
| + | =Implications= | ||
| + | Overall this cannot easily be used as a template for other projects due to the nature of the hierarchical model of processes. Essentially, what happens is that a great deal of planning creates a firm foundation to move the project through the remaining phases. Furthermore the planning phase should be done in a specific fashion, where certain technologies and roles are required or at the very least suggested. | ||
| + | Moreover the hierarchical model indicates that ” a systems integrator is responsible for the management and governance of the megaproject through all phases in its life cycle: planning, design, construction, and operational readiness.”<ref name="Davies, Gann, Douglas"> Andrew Davies, David Gann,Tony Douglas"> ''Innovations in Megaprojects: Systems Integration At London Heathrow Terminal'', California Management Review, 2009</ref> TThis is difficult role to fulfill due to nature of most infrastructure projects such as T5. The system integrator usually employs other to work across disciplines e.g. design and construction. Then the system integrator relies on itself to integrate the outsourced work and deliver a final project. This does not happen easily and requires a lot of knowledge in order to successfully coordinate. In a sense, the system integrator serves as the glue to hold all parts together and deliver a final project. In the case of the T5 project, BAA was more than capable to handle the role of system integrator, but most owners and clients don’t aren’t as capable, in which case using T5 as a template will fail. LOR saw the T5 project as an opportunity to further their capabilities and take on the role of system integrator in projects that enabled it. They have invested in doing so and been quite successful. On projects they may create a team that consists of former project managers and consultants to represent the client and serve as system integrator. They have been quite successful in developing their capabilities, which is apparent by their revenue being 8 times what it was during T5. | ||
| − | |||
| − | |||
| − | |||
| + | =Conclusion= | ||
| + | The T5 project has been successful due to the fact that it incorporated lean principles that emphasize simplification and standardization. Single-model environment (SME) is perfect for this as it enables architects and engineers across design disciplines to work share their work and build upon it with the intent of creating 3D or 4D models. This not only aids in visualization but also decreases design error. Furthermore the fact that the construction site proved to be a logistical nightmare was actually a blessing in disguise. This is due to the fact that it enforced the use of off-site fabrication and testing before anything came on site. These things would of course not work as effectively had there not been an effort to utilize just-in time logistics. Overall these processes created a safe work environment, enabled better collaboration between partners, and ensured that T5 was completed on time, within budget, and of high quality. | ||
=References= | =References= | ||
<references/> | <references/> | ||
Latest revision as of 15:03, 18 December 2018
Developed by Sanna Monjezi
The Heathrow terminal 5 (T5) projectalso known as the T5 project, was created with the intent of easing the congestion of the airport, centralizing all British Airways (BA) flights, and increasing the revenue from other airlines. Due to the size of the project both in size and budget it was complex to manage. This was not ameliorated by the fact that it took eight years to get government approval. The project consisted of a control tower, two satellite buildings, and supporting infrastructure. The latter included river diversions, connections between terminals, and a train station. This resulted in 16 major projects, and 147 sub-projects, all separate from each other and involving over 60 contractors in total. [1]
Due to the fact that construction projects by nature are prone to delays it’s quite remarkable that the T5 project was completed on time, within budget, and with less fatalities than expected. The reason for this was the fact that the contracts between British Airways and the contractors were quite unique for their time. The contracts were unique because all contractors pooled together risk payments and were promised a share in the event that their work was finished on time. This proved to be an effective incentive not only to be on time and on budget, but also to nudge the contractors towards better teamwork as the prospects of getting the bonuses was higher that way. The result was a construction project finished on time and on budget with fewer fatalities than there would normally be on a project of that size. Unfortunately there were issues on the operation level that led to bad reviews on the opening week that overshadowed the success of the construction project. [2]
Contents |
[edit] Overview
T5 project is considered a mega project; due to the fact that these are "projects of a significant cost that attract a high level of public attention or political interest because of substantial direct and indirect impacts on the community, environment, and budgets". [3] The client and owner of Heathrow Airport, and by extension T5, in this case is BAA. In this article only one of the contractors will be singled out; Lain O’Rouke. This is due to the fact that LOR grew with the project in such a way that it has completely changed the shape of the organization today.
[edit] Phases of T5 project
The T5 project in question can be divided into 4 phases shown in figure 1. It should be noted that the planning phase contains a 4-year long period of inquiry (1995-1999) and subsequent "consent to proceed with construction"[4]. in 2001. The T5 project is one of the longest in British history and cost around £80, cementing its label as a mega project. Even though all of the phases are of great importance to the success of the project, only the planning phase is described. This is due to the fact that the planning phase bye nature of a hierarchical model sets the serves as a firm foundation for the project. The rest of the phases are all depending on the fact that the planning phase is completed as indicated, which includes the use of specific processes, roles and responsibilities as well as technologies. These activities may seem excessive, but they are needed in other phases, and thereby crucial in leading the project to fruition
[edit] Planning phase
In 1990 Sir John Egan became the CEO of BAA and would continue to work through 1999. He had previously worked for Jaguar, a company that seemed to be very close to shutting down, but he turned the trend and is largely credited for the success.[5] Egan used his knowledge about Lean production from the automobile industry and attempted to apply it the construction of T5. Furthermore he recognized that projects are often unique and therefore approached as a "blank slate"[4], as BAA did prior to his arrival. In an effort to ameliorate this he wanted to create standardized parts of projects in an effort to apply Lean principles, that emphasized simplification and standardized tasks.
Egan gathered a team to explore practices, principles, and technologies from different industries in an effort to see what would work in the T5 project. Later on he would establish an organization that worked independently from BAA in an effort to "provide the freedom of choice needed to promote experimentation and innovation"[4]. Later on BAA would establish a Continuous Improvement Project Process (CIPP) in an effort to "provide a set of standardized and repeatable time-sequenced tasks, milestones, and stage-gates to deliver cost-effective and profitable projects"[4]. The projects in question would have a budget between $4M-$8M. CIPP also looked into the design process by working with modular design, so that the construction processes would have similar construction processes, despite being vastly similar. This was not done with the sole intent to apply these processes to T5, but for capital projects. Furthermore it gave BAA knowledge about suppliers’ capabilities, which was used in T5.
[edit] Hierarchical model of project processes
The processes of a mega project have been developed into a hierarchical model seen in figure 2 [4]. In the T5 project BAA was the systems integrator and thereby responsible for all management and coordination throughout the project. It is preferential to use such a model in case of a mega project, as it indicates which phases are to be done and in which order. Furthermore the model illustrates the order of which activities in the phases are to be completed. This is preferential because they are thought of in advance to aid the next phase and even more so, they encourage a more rigid division of roles and responsibilities. The division of roles and responsibilities is paramount in projects in general and even more so in complex project, where the amount of people involved is extremely high. If these people are not clear on their roles and responsibilities they run the risk of misunderstanding their responsibility and thereby waste time.
[edit] Research of pitfalls from similar projects
BAA approached this responsibility by starting with research into similar projects. These were divided into two categories: construction projects in the UK with a budget over $2B and all airport constructions in the world. The timeframes were 10 years and 15 years respectively. This enabled the research team to recognize problem areas and look for efforts to improve them.
The research showed that no major projects in the UK or international airports had been completed and successfully accomplished any goals pertaining to time, budget, quality, and safety. The research on airports around the world proved no better, but gave a numerical estimate of how much the T5 project could be over budget etc. On the other hand the team divided the problem areas into two areas: "lack of collaboration among project partners; and clients’ reluctance to assume responsibility for project risks."[4] Furthermore, the first Project Director of T5 noted that most projects failed due to a lack of sufficient funding of the design phase.
[edit] Project processes
These processes nicely complement each other to form a foundation of organization and management throughout the project. First of all the T5 legal agreement was created in order to bind all parties to a structured workflow of specific tasks and tools. Moreover it serves as an aid throughout all phases of the project. The challenge of T5 was that it had a lot of contractors and was dependent on lots of technologies that BAA was not intimately familiar with. This was ameliorated by the fact that the BAA (in this case: the client and systems integrator) assumed all responsibility of risks and gave the contractors an incentive to work together. More importantly, a single-model environment (SME) enabled coordination throughout phases and across design disciplines. This is due to the fact that multiple users can share designs and the SME will detect any clashes. This decreases the risk of mistakes in the design phase that could potentially be found out during the construction phase. These types of mistakes are costly due to the fact that they inhibit the project moving along thus creating chaos. Solutions to these types of mistakes are often not completely thought out due to the fact that they are created in a hurry and don’t undergo the same process as all the other decisions. Adding to this, SME enables design disciplines to create a construction that is favorable during operation as well. This could be by adding enough space to make it easier for the person doing the electrical repairs to actually see what’s going on without e.g. visual aids due to the space being too small. This is favorable in terms of work environment laws. Lastly SME is a great tool during the planning phase as it is a visual aid of the construction site and it’s entries, walkways, exists. This will be further detailed in the next section. Tying these pieces together it is crucial to incorporate project and program management processes as these manage both the main project, which is T5, but also all the sub-projects.
[edit] Operational processes
During the project processes, SME served as a tool for planning the logistics of the construction site. Geographically the site was placed near a busy highway and to make matters worse the construction site only had one entry. LOR used to work by buying supplies as cheaply as possible and having them sent to the construction site for assembly etc. During the T5 project this would entail “8000 workers a day and nearly 250 deliveries of materials per hour” [4]], which would be impossible logistically. For this reason modular pre-assemblies and just-in-time logistics were perfect as they enabled the producers to test the assembly before arriving at the construction site. Pre-assembly and modular construction often involves off-site fabrication, which decreases the risk of mistakes and accidents on the construction site. This is due to the fact that all safety factors that need to be taken into consideration to assemble or fabricate something are gone. There are no parts of the constriction site that need to be isolated, and there is no need to take any extra safety precautions on the construction site. This should not be taken lightly as the legalities regarding work environment and safety are quite extensive. It is therefore favorable to make use of off-site fabrication as it frees up a lot of resources that would be otherwise engaged with safety regulatory processes, and reduces the chance of extra-work due to mistakes. The latter is meant to indicate that for the T5 project, pre-assembled modular were tested off-site to ease the final construction on the construction site. Furthermore, it reduced the risk of supplies being delivered at the wrong place, and needing them to be moved during the construction process. Often times, the supplies are quite heavy and work environment laws have limits on how much a labor is allowed to carry. The case could also be that the supplies can only be moved by machinery, which may be used for a different purpose at the time. Pre-assembly and modular-construction therefore reduce all sorts of risks, enable the producers to test the object and can ensure that the project stays within budget due to the lack of unforeseen expenses. LOR, which was responsible for a large portion of the construction used a “consolidation facility” that meant that modules and components were transported to a temporary storage unit, so that they could be transported to the construction site just-in time. This was an effective way of ensuring that the project stayed within the given timeframe.
[edit] Implications
Overall this cannot easily be used as a template for other projects due to the nature of the hierarchical model of processes. Essentially, what happens is that a great deal of planning creates a firm foundation to move the project through the remaining phases. Furthermore the planning phase should be done in a specific fashion, where certain technologies and roles are required or at the very least suggested. Moreover the hierarchical model indicates that ” a systems integrator is responsible for the management and governance of the megaproject through all phases in its life cycle: planning, design, construction, and operational readiness.”[4] TThis is difficult role to fulfill due to nature of most infrastructure projects such as T5. The system integrator usually employs other to work across disciplines e.g. design and construction. Then the system integrator relies on itself to integrate the outsourced work and deliver a final project. This does not happen easily and requires a lot of knowledge in order to successfully coordinate. In a sense, the system integrator serves as the glue to hold all parts together and deliver a final project. In the case of the T5 project, BAA was more than capable to handle the role of system integrator, but most owners and clients don’t aren’t as capable, in which case using T5 as a template will fail. LOR saw the T5 project as an opportunity to further their capabilities and take on the role of system integrator in projects that enabled it. They have invested in doing so and been quite successful. On projects they may create a team that consists of former project managers and consultants to represent the client and serve as system integrator. They have been quite successful in developing their capabilities, which is apparent by their revenue being 8 times what it was during T5.
[edit] Conclusion
The T5 project has been successful due to the fact that it incorporated lean principles that emphasize simplification and standardization. Single-model environment (SME) is perfect for this as it enables architects and engineers across design disciplines to work share their work and build upon it with the intent of creating 3D or 4D models. This not only aids in visualization but also decreases design error. Furthermore the fact that the construction site proved to be a logistical nightmare was actually a blessing in disguise. This is due to the fact that it enforced the use of off-site fabrication and testing before anything came on site. These things would of course not work as effectively had there not been an effort to utilize just-in time logistics. Overall these processes created a safe work environment, enabled better collaboration between partners, and ensured that T5 was completed on time, within budget, and of high quality.
[edit] References
- ↑ [http://www.airport-technology.com/projects/heathrow5/] London Heathrow Airport Expansions (LHA/EGLL), United Kingdom
- ↑ [http://www.the-chiefexecutive.com/features/feature68469/] 'Why stakeholders matter
- ↑ [http://flyvbjerg.plan.aau.dk/whatisamegaproject.php] What is a Megaproject?
- ↑ 4.0 4.1 4.2 4.3 4.4 4.5 4.6 4.7 Andrew Davies, David Gann,Tony Douglas"> Innovations in Megaprojects: Systems Integration At London Heathrow Terminal, California Management Review, 2009
- ↑ [http://www.birminghampost.co.uk/news/local-news/how-jaguar-found-new-life-9678099] How Jaguar found a new life after near collapse
