<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article  PUBLIC "-//NLM//DTD Journal Publishing DTD v3.0 20080202//EN" "http://dtd.nlm.nih.gov/publishing/3.0/journalpublishing3.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="3.0" xml:lang="en" article-type="research article"><front><journal-meta><journal-id journal-id-type="publisher-id">JTTs</journal-id><journal-title-group><journal-title>Journal of Transportation Technologies</journal-title></journal-title-group><issn pub-type="epub">2160-0473</issn><publisher><publisher-name>Scientific Research Publishing</publisher-name></publisher></journal-meta><article-meta><article-id pub-id-type="doi">10.4236/jtts.2022.124032</article-id><article-id pub-id-type="publisher-id">JTTs-119178</article-id><article-categories><subj-group subj-group-type="heading"><subject>Articles</subject></subj-group><subj-group subj-group-type="Discipline-v2"><subject>Engineering</subject></subj-group></article-categories><title-group><article-title>
 
 
  A Comparative Study of Managing a Project Using Traditional Management Techniques and a Critical Chain Project Management Methodology in Aircraft Maintenance Field
 
</article-title></title-group><contrib-group><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Devinder</surname><given-names>Kumar Yadav</given-names></name><xref ref-type="aff" rid="aff1"><sup>1</sup></xref><xref ref-type="corresp" rid="cor1"><sup>*</sup></xref></contrib><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Anand</surname><given-names>Kulkarni</given-names></name><xref ref-type="aff" rid="aff2"><sup>2</sup></xref></contrib><contrib contrib-type="author" xlink:type="simple"><name name-style="western"><surname>Hui</surname><given-names>Yao</given-names></name><xref ref-type="aff" rid="aff3"><sup>3</sup></xref></contrib></contrib-group><aff id="aff2"><addr-line>Department of Management, National University of Singapore, Queenstown, Singapore</addr-line></aff><aff id="aff3"><addr-line>Ningbo DEKO Information Technology Company Limited, Ningbo, China</addr-line></aff><aff id="aff1"><addr-line>University of Nottingham Ningbo China, Ningbo, China</addr-line></aff><pub-date pub-type="epub"><day>29</day><month>07</month><year>2022</year></pub-date><volume>12</volume><issue>04</issue><fpage>544</fpage><lpage>558</lpage><history><date date-type="received"><day>5,</day>	<month>July</month>	<year>2022</year></date><date date-type="rev-recd"><day>13,</day>	<month>August</month>	<year>2022</year>	</date><date date-type="accepted"><day>16,</day>	<month>August</month>	<year>2022</year></date></history><permissions><copyright-statement>&#169; Copyright  2014 by authors and Scientific Research Publishing Inc. </copyright-statement><copyright-year>2014</copyright-year><license><license-p>This work is licensed under the Creative Commons Attribution International License (CC BY). http://creativecommons.org/licenses/by/4.0/</license-p></license></permissions><abstract><p>
 
 
  Aircraft on ground or down-time for its maintenance is a clear loss in revenue for an airline operation. With never ending competition and growing
   operating costs of aircraft, airlines continuously need to explore opportunities to reduce the aircraft down-time in order to remain sustainable. Due to round the clock operation feature of scheduled airlines, aircraft maintenance operations are generally carried out using traditional management methodologies instead of considering it as a project. Though aircraft heavy maintenance checks consist of several major tasks that can last from few weeks to a year, the maintenance organisations do not adopt modern project management methodologies. Therefore, this paper models a heavy maintenance check of an Airbus aircraft as a typical project and adopt
  s
   contemporary project management methodology to explore the possibility of reducing the downtime. To thi
  s end, a case study has been done at an aircraft maintenance company to analyse the potential of this project management method in aircraft maintenance industry.
 
</p></abstract><kwd-group><kwd>Aviation</kwd><kwd> Airline</kwd><kwd> Aircraft</kwd><kwd> Engineering</kwd><kwd> Management</kwd><kwd> Maintenance</kwd><kwd> Operations</kwd><kwd> Planning</kwd><kwd> Project</kwd></kwd-group></article-meta></front><body><sec id="s1"><title>1. Introduction</title><p>Project management methodologies to achieve efficient and quality assured deliverables of projects are being used in various industries for a while. Especially large civil engineering projects are executed effectively using modern project management methodologies. However, project management is not very popular in aircraft maintenance industry including airlines engineering operations or aircraft maintenance repair overhaul (MRO) companies. Though project management is now commonly used, and planning has become an essential part of a project, many companies plan their projects using Excel or PowerPoint instead of scheduling through critical path method, this traditional method does not guarantee the project completion as planned [<xref ref-type="bibr" rid="scirp.119178-ref1">1</xref>].</p><p>Aircraft maintenance managers confront with tight deadlines and handle tremendous pressure to start planned maintenance work packages as soon as possible (ASAP) once they receive the aircraft from flight operations for maintenance. Therefore, according to standard practices, maintenance tasks are scheduled ASAP even if all necessary aircraft parts required for the maintenance are not available at their maintenance facility. Such practices of starting tasks ASAP increase internal competition among different trades of aircraft maintenance or types of aircraft for available resources, which are generally limited. For example, trade supervisors of different fields, such as airframe, engine, avionics, and aircraft interior cabins start forcing their technicians for multitasking. As a result, work-in-progress (WIP) levels become unnecessarily high, and it overloads the back shops and the internal supply chain system. Likewise, other support departments, such as technical service and quality assurance also get strained, because they need to provide relevant documentation and technical support to execute the open tasks caused by multitasking. A combination of these factors actually increases delays that trigger a vicious cycle of starting more tasks ASAP leading to further delays. Consequently, hard work and expediting the tasks using labour overtime, the task cycle times remain long. As a result, the maintenance completion gets delayed, overall productivity remains low and costs overrun occurs frequently. According to [<xref ref-type="bibr" rid="scirp.119178-ref2">2</xref>], aircraft maintenance sector is extremely affected by fluctuations in the financial market and competitions. Hence, MRO organisations must reduce the maintenance costs and aircraft ground time for the maintenance. Furthermore, they should provide a high-quality service that meets airworthiness requirements and at a competitive cost [<xref ref-type="bibr" rid="scirp.119178-ref3">3</xref>]. Despite all these issues, maintenance managers are not very keen in adopting the modern project management methodologies as used by other fields of engineering industry, because they are not yet fully tested and validated in aircraft maintenance industry.</p><p>This paper is based on a case study, which was carried out using Airbus 320 aircraft that underwent a heavy maintenance check at a large MRO company located in Singapore. The study modelled the maintenance check as a typical project and used the critical chain project management method for executing the project tasks. Findings of the study clearly indicate that the project management methodology brings cost benefits and reduces the aircraft down-time period.</p></sec><sec id="s2"><title>2. Problems Associated with Traditional Aircraft Maintenance Practices</title><p>Aircraft is a multi-technology machine involving many engineering fields including mechanical, electrical, electronics, structures, computer technology, material science, etc. As a result, a typical heavy maintenance check of an aircraft is to be performed by several technical personnel from these fields and concurrently often. The check involves completion of numerous engineering and testing tasks, and they must be completed within a specified amount of time in order to reduce the aircraft grounding period. [<xref ref-type="bibr" rid="scirp.119178-ref4">4</xref>] believe that the grounding time for a heavy maintenance check can be influenced by strategic and tactical issues of the maintenance company including available technical personnel, required spare parts of the aircraft, and financial value of the planned tasks. Furthermore, the checks must meet the civil aviation regulatory requirements and airworthiness standards, because aviation is still a highly regulated industry. This exerts a tremendous professional pressure on the personnel and also on revenue of MRO companies and the airline operators. Therefore, aircraft maintenance is a multidisciplinary task that frequently requires tradespersons from different engineering fields, such as airframe, propulsion, and avionics to work concurrently on a typical aircraft system. Therefore, it is not an engineering or a supply-chain issue. Instead, it is a project management problem, if a cost overrun happens or aircraft downtime increases. Consequently, a management approach that cut across traditional functions fields becomes necessary in order to meet planned goals and deliverables in time and within the cost. According to [<xref ref-type="bibr" rid="scirp.119178-ref4">4</xref>], a teardown execution approach and modern project management methodology should be considered by aircraft maintenance managers to make MRO companies more cost effective and also to improve the situation of prolonged aircraft downtime required for carrying out heavy maintenance checks.</p><p>[<xref ref-type="bibr" rid="scirp.119178-ref5">5</xref>] argue that aircraft maintenance scheduling is considered as an end-stage in an airline operation, but it has possibilities of cost reductions. Traditional aircraft maintenance management system considers a mission accomplished if individual tasks are completed within stipulated time. Therefore, every individual task duration estimates must be accurate with a high probability of completing the task on time. Consequently, a safety buffer or contingency period is added to the task duration in planning stage itself to ensure that task completion probability remains high. This may absorb the lost time caused by multitasking and variation in tasks, if any. However, this safety buffer remains hidden in the task inflating the task duration as a result. With the inclusion of safety buffer into a task duration, there is more than the required time available for completing the task. Furthermore, this management practice does not generally offer any incentive to complete the task before a deadline. This behaviour triggers unproductive situations, occasionally. For example, student syndrome where people try to put off the task until the task deadline approaches. The task in this case is often delayed (<xref ref-type="fig" rid="fig1">Figure 1</xref>).</p><p>According to [<xref ref-type="bibr" rid="scirp.119178-ref6">6</xref>], student syndrome is a legitimate part of any project life cycle that may end up in a constraint. This demonstrates that human factors play an important role in a project execution, because it influences the time of task completion. It may also affect the whole project path, if the project has tasks which are interrelated. As a result, the whole project may get delayed. The researcher believes that the student syndrome generally occurs, if a participant has been allocated excess time for carrying out a task. Similarly, according to Parkinson’s Law, tasks are executed at a slower pace to fill the available time duration. As a result, the safety buffer included at the planning stage is wasted and if a task duration increases due to some reason, the project deadline also gets affected.</p><p>The current maintenance management practices of starting the maintenance tasks as soon as possible once the aircraft is grounding for a maintenance check without ensuring availability of all required resources force maintenance personnel to work on more than one task at once. This creates multitasking situation that turns unmanageable occasionally. According to [<xref ref-type="bibr" rid="scirp.119178-ref7">7</xref>], multi-tasking happens due to high demand on a resource’s time. Consequently, the resource is forced to try their hand on a task before completion to work on another task. Though the intention of high resource utilization looks good on surface, but it adds wasteful practice into managing the project [<xref ref-type="bibr" rid="scirp.119178-ref8">8</xref>]. <xref ref-type="fig" rid="fig2">Figure 2</xref> indicates the hidden cost of multi-tasking.</p><p>Similarly, the unknown-work phenomenon also pushes the schedule towards potential delays. For example, an aircraft sometimes reaches its performance limits long before its compressor limiting operating cycles [<xref ref-type="bibr" rid="scirp.119178-ref9">9</xref>]. As a result, it needs extra restoration work. Similarly, some maintenance incidents are impossible to predict. For example, unscheduled engine removals occur due to foreign object damage, bird strikes or other environmental impacts that brings in unknown work. Thus, the personnel keep switching between tasks that leads to elongation of planned time estimates and it further wastes the embedded task safety buffer in execution. Likewise, according to classical maintenance management techniques, tasks are managed by deadlines or milestones and task</p><p>owners are held accountable for any delay related to their respective task completion. As a result, the task owners resist reporting any early finishes. The belief is that if an early finish is reported, the task owner is held responsible for over estimation. Furthermore, the management may also tend to shorten the duration of similar task on other similar projects. This shorter time estimate may not offer sufficient safety buffer to the project in case of variation though. Hence task owners ensure that sufficient safety margin is always available in each task estimate, the margin remains hidden, and it is used in execution of the task. Though the resulting longer task completion duration affects the entire project, but benefits from tasks finished early are not passed on to the project.</p></sec><sec id="s3"><title>3. Hypothesis and Case Study</title><p>Available literature related to aircraft maintenance suggests that delays in aircraft maintenance tasks completion are primarily caused by uncertainty and variation in tasks that leads to multitasking and overestimation. Secondly, the safety margin built into the task duration is wasted due to student syndrome and Parkinson’s Law that delayed the whole project as a result. Thirdly, the current management practices of managing the tasks by milestones and deadlines that force managers to start jobs as early as possible without considering the availability of resources leading to multitasking and increasing the task duration. Finally, the policy of no incentive for finishing the task early. Modern project management methodology, such as a critical chain project management method may present a solution to mitigate the uncertainty and task duration variation by incorporating safety buffers that reduces the wastage caused by the student syndrome and Parkinson’s Law phenomena. This can be done by using aggressive task duration estimation steps. Similarly, the multitasking issue can be handled by designing a critical chain path based on resources and task constraints. Similarly, managing the completion deadlines and milestones by monitoring the progress based on buffer consumption. Therefore, it can be hypothesised that the modern project management methodology can be applied in aircraft maintenance industry by considering the aircraft maintenance checks as projects. The case examined by this paper is mentioned below:</p><p>A maintenance check of an Airbus 320 transport aircraft was professionally observed from beginning to the end at a civil aircraft maintenance facility approved under civil aviation regulatory framework. The aircraft underwent a heavy maintenance check at this large MRO organisation located in Singapore and the maintenance check was modelled as a typical project. Subsequently, it was managed and executed according to critical chain project management methods and principles. As a result, a detailed planning was carried out defining the scope of work scope and preparing required job cards after negotiating with the aircraft owner about the value and period of the project. Hence a maintenance schedule was created and handed over to the maintenance management team of the project.</p><p>The plan was then executed by the team corresponding to the schedule, and the tasks were carried out by appropriately qualified aircraft engineers and technicians according to their respective trades. Consequently, the tasks were carried out by specialized technical personnel from airframe, engine, avionics, and non-destructive testing (NDT) fields. The personnel were further divided into various sub-teams covering aircraft wing, fuselage, engine, interior cabin, etc. Required resource allocation was done by the management team on a daily basis to ensure and monitor effective utilisation of the resources. Similarly, the tasks were completed daily and the job cards were signed off and handed over to the planners. In addition, the scientific or engineering problems encountered were tackled by professional engineers using engineering judgements or by consulting the aircraft manufacturer.</p></sec><sec id="s4"><title>4. Methodology and Data Collection</title><p>The single case analysis method was used in this paper a research methodology. Consequently, a heavy maintenance check of an Airbus 320 was modelled as a project for data collection. Therefore, the maintenance planning documents supplied by the aircraft manufacturer was used to plan and prepare the aircraft maintenance schedule. A direct observation of planning and execution of the aircraft maintenance tasks was done by the second author while the maintenance work was carried out by the relevant technical personnel of the MRO establishment at its facility. This assisted the authors to identify the maintenance management issues experienced by the organisation and its stake holders. The case study methodology was chosen, because there were not enough data related to aircraft maintenance management are available in public domain. From direct observation of various maintenance task procedures, it was also become possible to know whether the tasks were carried out in accordance with the civil aviation regulatory standards or not. As multiple case studies were not feasible, a single case analysis was considered adequate, and the problems identified in the case study were generalized for all types of aircraft maintenance checks performed by an MRO facility.</p><p>A maintenance schedule for the maintenance check was designed in accordance with guideline of the maintenance planning document (MPD) of the aircraft manufacturer, which the Airbus Company in this case (<xref ref-type="table" rid="table1">Table 1</xref>). A typical heavy maintenance check requires 40,000 to 50,000 man-hours of schedule work and it may be extended to additional 10,000 man-hours of unanticipated work [<xref ref-type="bibr" rid="scirp.119178-ref10">10</xref>]. The maintenance check schedule is a large document which not possible to reproduce here in total. So, <xref ref-type="table" rid="table1">Table 1</xref> shows only a part of it. Furthermore, references and identity information of the related MRO organisation has been removed from the schedule document to protect privacy as requested by the organisation. Therefore, evidence by direct observations of the maintenance planning and project execution process was undertaken by the authors in unclassified manner. As operational planning involves short-range detailed planning and execution of the heavy maintenance check, after the project was accepted more detailed information about resource and material requirements were made available from technical services department and process planning section of the organisation. The work packages from the customer were broken down into smaller activities with specific duration and resource usage based on technical and detailed process planning information. As a result, the planning and execution was done according to critical path method. In fact, most aircraft maintenance projects must deal with tremendous uncertainties. They are caused primarily by unknown work, which is usually hard to predict. Hence, it is difficult to plan. The unknown work is generally related to aircraft structural damages caused by stresses [<xref ref-type="bibr" rid="scirp.119178-ref11">11</xref>]. Unfortunately, aircraft spare parts are not readily available at maintenance facilities often for the unknown work. The unknown work also contributes to project delays and a delay in tasks on the project work chain path feeding into the longest chain can impact the project by delaying a subsequent task on the critical chain. Therefore, feeding buffers were required on a feeding path and the critical chain to absorb this delay.</p><p>At the project execution stage, resources were dedicated to a typical task until it was completed to prevent multi-tasking. Consequently, each task was started as soon as the resource was made available and prerequisite tasks completed. Additionally, all resources on the project were given clear priorities considering the project as a whole. The tasks were prioritised based on rate of buffer consumption and priorities were assigned to completing the task that had potential to affect the project critical chain before completing any other task on feeding path. Likewise, the project staff were encouraged to follow the roadrunner approach, so that the work could be performed at the fastest possible speed to the completion without compromising quality of deliverables. As task duration estimates margin reduces, they drive resources to meet more aggressive durations and limit the student syndrome and Parkinson’s Law behaviours. Similarly, the managers monitored the buffer consumption and acted to reduce its rate of consumption. In this situation, it was important to monitor the buffers and the remaining duration of tasks.</p><table-wrap id="table1" ><label><xref ref-type="table" rid="table1">Table 1</xref></label><caption><title> First week tasks of a typical maintenance schedule of an aircraft</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >SN</th><th align="center" valign="middle" >Workshop transit items</th><th align="center" valign="middle" >7 Oct 12</th><th align="center" valign="middle" >11 Oct 12</th><th align="center" valign="middle" >5 days</th><th align="center" valign="middle" ></th><th align="center" valign="middle" ></th><th align="center" valign="middle" ></th><th align="center" valign="middle" ></th><th align="center" valign="middle" ></th><th align="center" valign="middle" ></th><th align="center" valign="middle" ></th><th align="center" valign="middle" ></th><th align="center" valign="middle" ></th><th align="center" valign="middle" ></th><th align="center" valign="middle" ></th></tr></thead><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >NLG torque link apex pin for MPI</td><td align="center" valign="middle" >7 Oct 12</td><td align="center" valign="middle" >7 Oct 12</td><td align="center" valign="middle" >1 day</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >Perform magnetic practice inspection Of the elevator inboard and Outboard servo controls rod eye ends</td><td align="center" valign="middle" >7 Oct 12</td><td align="center" valign="middle" >9 Oct 12</td><td align="center" valign="middle" >3 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Portable halon fire extinguishers for weight check</td><td align="center" valign="middle" >7 Oct 12</td><td align="center" valign="middle" >11 Oct 12</td><td align="center" valign="middle" >5 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Remove lavatory A, E, D fire extinguisher bottle for weight check</td><td align="center" valign="middle" >7 Oct 12</td><td align="center" valign="middle" >11 Oct 12</td><td align="center" valign="middle" >5 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >4</td><td align="center" valign="middle" >Fwd and Aft gallery drain valve for cleaning (if applicable)</td><td align="center" valign="middle" >7 Oct 12</td><td align="center" valign="middle" >11 Oct 12</td><td align="center" valign="middle" >5 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >5</td><td align="center" valign="middle" >Fwd cabin vacuum toilet rinse valve for cleaning</td><td align="center" valign="middle" >7 Oct 12</td><td align="center" valign="middle" >11 Oct 12</td><td align="center" valign="middle" >5 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >6</td><td align="center" valign="middle" >Functional check Of pressure reducer for cargo fire extinguisher system</td><td align="center" valign="middle" >7 Oct 12</td><td align="center" valign="middle" >11 Oct 12</td><td align="center" valign="middle" >5 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >7</td><td align="center" valign="middle" >Eng #1; clean integrated drive generator (IDG) Oil cooler</td><td align="center" valign="middle" >7 Oct 12</td><td align="center" valign="middle" >11 Oct 12</td><td align="center" valign="middle" >5 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >8</td><td align="center" valign="middle" >Avionics—cleaning of Oxygen masks</td><td align="center" valign="middle" >7 Oct 12</td><td align="center" valign="middle" >11 Oct 12</td><td align="center" valign="middle" >5 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >SN</td><td align="center" valign="middle" >Major modifications</td><td align="center" valign="middle" >6 Oct 12</td><td align="center" valign="middle" >12 Oct 12</td><td align="center" valign="middle" >7 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >Mod intro bearing assy On retract jack SB A320-57-1157 V00 R00</td><td align="center" valign="middle" >6 Oct 12</td><td align="center" valign="middle" >9 Oct 12</td><td align="center" valign="middle" >4 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >Avionics—Mod inst wiring prov for ATC/XPDR</td><td align="center" valign="middle" >6 Oct 12</td><td align="center" valign="middle" >12 Oct 12</td><td align="center" valign="middle" >7 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Avionics—Mod install RS422 wiring</td><td align="center" valign="middle" >6 Oct 12</td><td align="center" valign="middle" >13 Oct 12</td><td align="center" valign="middle" >7 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >4</td><td align="center" valign="middle" >Avionics—Mod inst FDIMU from teledyn</td><td align="center" valign="middle" >6 Oct 12</td><td align="center" valign="middle" >14 Oct 12</td><td align="center" valign="middle" >7 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >5</td><td align="center" valign="middle" >Avionics—Mod intro wiring provision for FDIU/DMU</td><td align="center" valign="middle" >6 Oct 12</td><td align="center" valign="middle" >15 Oct 12</td><td align="center" valign="middle" >7 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >6</td><td align="center" valign="middle" >Avionics—Mod-wire harness inst at interface section 19/19.1</td><td align="center" valign="middle" >6 Oct 12</td><td align="center" valign="middle" >16 Oct 12</td><td align="center" valign="middle" >7 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >7</td><td align="center" valign="middle" >Wing: Install trunnion sliding panel with new attachment IAW SB A320-57-1147 Rev 03</td><td align="center" valign="middle" >7 Oct 12</td><td align="center" valign="middle" >9 Oct 12</td><td align="center" valign="middle" >3 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >8</td><td align="center" valign="middle" >Eng #1, Eng #2; O/w mod rpl deploy tube adaptor “o” ring</td><td align="center" valign="middle" >7 Oct 12</td><td align="center" valign="middle" >9 Oct 12</td><td align="center" valign="middle" >3 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >9</td><td align="center" valign="middle" >Mod cockpit door module improvement</td><td align="center" valign="middle" >8 Oct 12</td><td align="center" valign="middle" >8 Oct 12</td><td align="center" valign="middle" >1 day</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >SN</td><td align="center" valign="middle" >Major restoration</td><td align="center" valign="middle" >10 Oct 12</td><td align="center" valign="middle" >13 Oct 12</td><td align="center" valign="middle" >4 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >All required access panels and fairings</td><td align="center" valign="middle" >10 Oct 12</td><td align="center" valign="middle" >13 Oct 12</td><td align="center" valign="middle" >4 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >All fuel tank access panels</td><td align="center" valign="middle" >10 Oct 12</td><td align="center" valign="middle" >13 Oct 12</td><td align="center" valign="middle" >4 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Electrical power On</td><td align="center" valign="middle" >13 Oct 12</td><td align="center" valign="middle" >13 Oct 12</td><td align="center" valign="middle" >1 day</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >SN</td><td align="center" valign="middle" >Functional checks</td><td align="center" valign="middle" >13 Oct 12</td><td align="center" valign="middle" >14 Oct 12</td><td align="center" valign="middle" >2 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >System functionals</td><td align="center" valign="middle" >13 Oct 12</td><td align="center" valign="middle" >14 Oct 12</td><td align="center" valign="middle" >2 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >LDG retraction test</td><td align="center" valign="middle" >14 Oct 12</td><td align="center" valign="middle" >14 Oct 12</td><td align="center" valign="middle" >1 day</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >SN</td><td align="center" valign="middle" >Final checks</td><td align="center" valign="middle" >14 Oct 12</td><td align="center" valign="middle" >15 Oct 12</td><td align="center" valign="middle" >2 days</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >Refuel/leak check</td><td align="center" valign="middle" >15 Oct 12</td><td align="center" valign="middle" >15 Oct 1 2</td><td align="center" valign="middle" >1 day</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >Eng wash+ Eng run</td><td align="center" valign="middle" >15 Oct 12</td><td align="center" valign="middle" >15 Oct 12</td><td align="center" valign="middle" >1 day</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >3</td><td align="center" valign="middle" >Aircraft handover</td><td align="center" valign="middle" >15 Oct 12</td><td align="center" valign="middle" >15 Oct 12</td><td align="center" valign="middle" >1 day</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" >5 Oct 12</td><td align="center" valign="middle" >6 Oct 12</td><td align="center" valign="middle" >7 Oct 12</td><td align="center" valign="middle" >8 Oct 12</td><td align="center" valign="middle" >9 Oct 12</td><td align="center" valign="middle" >10 Oct 12</td><td align="center" valign="middle" >11 Oct 12</td><td align="center" valign="middle" >12 Oct 12</td><td align="center" valign="middle" >13 Oct 12</td><td align="center" valign="middle" >14 Oct 12</td><td align="center" valign="middle" >15 Oct 12</td></tr><tr><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" >day 1</td><td align="center" valign="middle" >day 2</td><td align="center" valign="middle" >day 3</td><td align="center" valign="middle" >day 4</td><td align="center" valign="middle" >day 5</td><td align="center" valign="middle" >day 6</td><td align="center" valign="middle" >day 7</td><td align="center" valign="middle" >day 8</td><td align="center" valign="middle" >day 9</td><td align="center" valign="middle" >day 10</td><td align="center" valign="middle" >day 11</td></tr></tbody></table></table-wrap></sec><sec id="s5"><title>5. Discussion and Analysis</title><p>The aircraft maintenance heavy check direct observation and analysis of various data including task completion rate indicates that the project budget overrun and project completion time delays are affected by interdisciplinary trade tasks interdependency, resource usage overlap, unknown-work and sudden variation of tasks because of the unknown-work. Multitasking occurs when maintenance managers insist to start the tasks as early as possible without ensuring the availability of all the required resources. MPD was not effectively used to address the tasks and resources interdependency early as the project progressed (<xref ref-type="table" rid="table2">Table 2</xref> and <xref ref-type="table" rid="table3">Table 3</xref>). The direct observation had also presented the opportunities to examine compliance with standard project planning, execution and tracking methods used during the project in addition to civil aviation regulatory compliance and airworthiness standard conformity.</p><table-wrap id="table2" ><label><xref ref-type="table" rid="table2">Table 2</xref></label><caption><title> Example of project task time overestimation</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >S. No</th><th align="center" valign="middle" >Maintenance task</th><th align="center" valign="middle" >Project planned man-hours</th><th align="center" valign="middle" >MPD suggested man-hours</th></tr></thead><tr><td align="center" valign="middle" >1</td><td align="center" valign="middle" >Aircraft engine removal or installation</td><td align="center" valign="middle" >39.00</td><td align="center" valign="middle" >16.00</td></tr><tr><td align="center" valign="middle" >2</td><td align="center" valign="middle" >Aircraft avionics compartment smoke detectors replacement</td><td align="center" valign="middle" >65.00</td><td align="center" valign="middle" >2.00</td></tr></tbody></table></table-wrap><table-wrap id="table3" ><label><xref ref-type="table" rid="table3">Table 3</xref></label><caption><title> Sample page of maintenance planning document (after [<xref ref-type="bibr" rid="scirp.119178-ref15">15</xref>])</title></caption><table><tbody><thead><tr><th align="center" valign="middle" >Task Number</th><th align="center" valign="middle" >Zone</th><th align="center" valign="middle"  colspan="3"  >Description</th><th align="center" valign="middle" >Threshold Interval</th><th align="center" valign="middle" >Source</th><th align="center" valign="middle" >Reference</th><th align="center" valign="middle" >Men</th><th align="center" valign="middle" >M/H</th><th align="center" valign="middle" >Applicability</th></tr></thead><tr><td align="center" valign="middle"  rowspan="3"  >552600-01-1</td><td align="center" valign="middle"  rowspan="3"  >335 345</td><td align="center" valign="middle" >Elevators attach fittings: check of elevator attachment fittings for wear, LH/RH</td><td align="center" valign="middle"  rowspan="3"  >AF</td><td align="center" valign="middle"  rowspan="3"  >CHK</td><td align="center" valign="middle" >I: 12YE</td><td align="center" valign="middle"  rowspan="3"  >SIL</td><td align="center" valign="middle" >552600-200-002. SIL55-35</td><td align="center" valign="middle" >1 1</td><td align="center" valign="middle" >2.50 2.50</td><td align="center" valign="middle"  rowspan="3"  >All</td></tr><tr><td align="center" valign="middle" >Prep: elevator removed; elevator servocontrol removed</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" >*</td><td align="center" valign="middle" >TBD</td></tr><tr><td align="center" valign="middle" >Access: 334BB, 334DB, 334FB, 334HB, 344BB, 344DB, 344FB, 344HB</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" >* *</td><td align="center" valign="middle" >0.13 0.13</td></tr><tr><td align="center" valign="middle"  rowspan="3"  >553600-01-1</td><td align="center" valign="middle"  rowspan="3"  >325</td><td align="center" valign="middle" >Rudder attachment fittings</td><td align="center" valign="middle"  rowspan="3"  >AF</td><td align="center" valign="middle"  rowspan="3"  >CHK</td><td align="center" valign="middle" >T: 6YE</td><td align="center" valign="middle"  rowspan="3"  >SIL</td><td align="center" valign="middle" >SIL55-038</td><td align="center" valign="middle" >1</td><td align="center" valign="middle" >6.42</td><td align="center" valign="middle"  rowspan="3"  >All</td></tr><tr><td align="center" valign="middle" >Check of rudder attachment fittings for wear</td><td align="center" valign="middle" >I: 6YE</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" >Access: 325BL, 325BR, 325CL, 325CR, 325DL, 325DR, 325EL, 325ER</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" >*</td><td align="center" valign="middle" >0.16</td></tr><tr><td align="center" valign="middle" >554611-01-1</td><td align="center" valign="middle" ></td><td align="center" valign="middle" >*****task deleted*****</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" >*****end*****</td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td><td align="center" valign="middle" ></td></tr><tr><td align="center" valign="middle"  colspan="11"  >Systems and powerplant program: Stabilizers Rev. Date: Jun 01/12 Section: 2 - 55 page 1</td></tr></tbody></table></table-wrap><p>The critical chain methodology had effectively managed these issues. However, [<xref ref-type="bibr" rid="scirp.119178-ref12">12</xref>] had investigated the possibilities of implementing the critical chain method for product development program. They achieved mixed results that were not very promising in that sector. Nevertheless, a very useful feature of this methodology is that it especially tackles various human factors issues [<xref ref-type="bibr" rid="scirp.119178-ref11">11</xref>]. The research also indicates that the methodology reduces the amount of work during execution stage by calculating the work according to constrained resources, because this resource affects the work that can be completed. Similarly, it eliminates safety margin buffers from individual tasks and add them into total project buffer. This can provide an extra cushion to the project timeline. Secondly, there is no need to prepare precise timeline for resources at planning stage and develop the timeline while executing the project depending on the residual buffer remaining. Consequently, the tasks with lowest buffer remaining will get the highest priority. This improves overall efficiency of the project. However, allocation of resources for multitasking needs to be discouraged. This can also reduce strain on project support services that provide technical documents, spare parts and engineering advice related to unknown work. [<xref ref-type="bibr" rid="scirp.119178-ref11">11</xref>] did a similar study and found that the critical chain project method used at a United States Air Force maintenance facility managed to reduce the aircraft down-time by five days for a typical heavy maintenance check. As a result, the aircraft was available for additional flight operation time that translates into extra revenue generation of US$40,000 per day. Though revenue or finance balance sheet may not be important for military operations, but readiness of aircraft for flight is crucial. According to [<xref ref-type="bibr" rid="scirp.119178-ref13">13</xref>], the readiness depends on a total number of available aircraft as well as the total remaining flight time of all available aircraft in a fleet. Hence, one of the objectives of maintenance is to achieve maximum availability of the aircraft for flights. This certainly presents a convincible case for adoption of the method not only at civil MRO companies, but also for military aviation maintenance facilities.</p><p>Releasing work according to availability of overloaded or limited resources may seem counterproductive at times, because it is against the practices of completing the work rapidly. Conversely, releasing work without considering the situation of constrained resources may negatively affect the project completion time, it was observed. The critical chain methodology had assisted in measuring the project progress against the plan differently than the traditional style. For example, visual signals were used to indicate the progress instead of conventional methods such as Gantt charts and due dates. For example, showing the project status as amber colour means prepare a recovery plan. Likewise, the red indicates that implementing the recovery plan is necessary. This helped in reducing the student syndrome issues. Likewise, the project indicators were updated regularly, so that the management team could keep a strategic control on the task completion period. This was analysed using direct observation of multiple teams that carried out different tasks during the execution stage of the project. The results prove the hypotheses that the critical chain methodology can reduce the student syndrome problem. [<xref ref-type="bibr" rid="scirp.119178-ref14">14</xref>] suggests that the critical chain project management supports Murphy strikes and risks that improve on-time delivery of a project. The researcher further stated that this feature shares the safety margins that benefit the overall project. Additionally, it also assists in specific time allocations for unplanned tasks emerged as a result of unknown work. However, these buffers need to be estimated according to statistical data collected from other similar projects.</p><p>While analysing the number of man-hours allocated for any typical maintenance task by the MRO Company and the required hours suggested by the MPD supplied by the aircraft manufacturer, a rampant overestimation was noticed (<xref ref-type="table" rid="table2">Table 2</xref> and <xref ref-type="table" rid="table3">Table 3</xref>). At time, it seems that the overestimation is intentional instead of a professional error or technical misjudgement. For example, the aircraft avionics compartment smoke detectors replacement task was planned to be completed in 65 man-hours by the project management team, but MPD suggests only 2 hours for this task. Similarly, removal or installation of an engine from the aircraft was planned to be completed in 39 man-hours. However, the MPD suggests 16 hours for this task. Likewise, many other overestimations of the task completion man-hours have been noticed throughout the project plan. This might be done to mitigate the delays caused by unknown-work or it could be driven by financial reasons to enhance profit for the company, because MRO companies charges their customers according to number of man-hours spent on the maintenance tasks in addition to other charges, such as cost of spare parts, consumable, insurance, etc. This may not be the case, if an airline carryout the maintenance in-house at its own maintenance facilities. Hence, the overestimation issue seems to be subjective and depending on where and how the maintenance is being performed. Though the task durations estimated in the MPD are the minimum duration required to complete the tasks assuming the availability of all resources and after carrying out required facilitation of the tasks, they still can be considered as aggressive. The facilitation work may involve access panel removal, opening of enclosed sections of the aircraft, securing the electrical wiring, and plumbing to prevent damage and protecting aircraft instrument. For example, many panels are required to be opened before performing maintenance, and they need to be closed after the maintenance task is completed. This interdisciplinary work causes task interdependency which is not considered in MPD suggested man-hours.</p></sec><sec id="s6"><title>6. Conclusions</title><p>Many fields of engineering use critical chain project management methodologies to efficiently manage and control large projects, but it is not yet popular in aircraft maintenance industry. According to current aircraft maintenance practices, the maintenance work is to be started and completed ASAP upon receiving the aircraft from flight operations department or from external customers. This initiates the work without even ensuring the availability of necessary resources, such as required spare parts, sometimes. Consequently, an internal competition for taking over the resources occurs among various trade supervisors involved in the maintenance. Subsequently, it overloads the resources and negatively affects the internal supply chain system. It brings additional strain on support services too, which are responsible for providing technical documents, quality assurance, aircraft spare parts and consumables. Finally, these factors increase the probability of delay in project completion. On project management front, it opens the flood gate for multitasking that is not considered as an efficient practice in a project environment, because it may lead to labour overtime that put pressure on project costs. However, it is observed that many maintenance managers are not very keen in adopting the modern project management methodologies despite experiencing these issues.</p><p>This study was carried out at an MRO company facility located in Singapore using direct observations while an Airbus 320 aircraft was undergoing a heavy maintenance check. Therefore, in order to examine the feasibility of applying the critical chain project management method in aircraft maintenance field for executing the maintenance tasks the check was modelled as a typical project. The results demonstrates that the project management methodology reduces the aircraft grounding time, thereby cutting the maintenance cost and enhance the aircraft operator’s revenue by improving the aircraft availability for flight operations. Aircraft flight dispatch reliability was not evaluated in this study though. This research presents that combining the feeding buffer into the total project buffer assists in mitigating the overall project delay. Likewise, using visual indicators instead of traditional due date method for project progress evaluations helps in reducing the student syndrome in a project.</p><p>Extensive overestimation of man-hours allocation for many maintenance tasks by the MRO maintenance team was noticed during this study. These are more than ten times than the hours suggested by the MPD supplied by the aircraft manufacturer. As MRO companies charges their customers for aircraft maintenance based on several man-hours spent to carry out the planned work, it seems to be a revenue enhancement exercise for the MROs. The estimation may be very different in case of the maintenance carried out in house by the aircraft owner or operating airline, it is assumed. Though the task durations estimation provided by the aircraft manufacture does not include facilitation work required to carry out the maintenance, the planned duration by the MRO may still look excessive. While the skillset of a maintenance worker team may affect the deliverable of an engineering project, this study did not examine the capabilities and competency levels of the aircraft maintenance teams, because it was assumed that they all meet the qualifications standards laid down by the relevant national civil aviation administration.</p></sec><sec id="s7"><title>7. Future Research</title><p>This research is primarily focused on one type of civil transport aircraft. Aircraft maintenance is evolving rapidly with time and different manufactures may have different approaches for maintaining the continuing airworthiness of their aircraft and aeronautical products. Different aircraft types have different operating situations and capabilities. Therefore, their maintenance needs also differ. Consequently, it will be interesting to see, if a similar study can be done on aircraft manufactured by other manufactures including military aircraft producers.</p></sec><sec id="s8"><title>Conflicts of Interest</title><p>The authors declare no conflicts of interest regarding the publication of this paper.</p></sec><sec id="s9"><title>Cite this paper</title><p>Yadav, D.K., Kulkarni, A. and Yao, H. (2022) A Comparative Study of Managing a Project Using Traditional Management Techniques and a Critical Chain Project Management Methodology in Aircraft Maintenance Field. Journal of Transportation Technologies, 12, 544-558. https://doi.org/10.4236/jtts.2022.124032</p></sec></body><back><ref-list><title>References</title><ref id="scirp.119178-ref1"><label>1</label><mixed-citation publication-type="other" xlink:type="simple">Critical Chain (n.d) Manage Projects with the Critical Chain: The Critical Chain Project Management, an Alternative to Classic Project Planning Issues. https://www.critical-chain-projects.com/the-method</mixed-citation></ref><ref id="scirp.119178-ref2"><label>2</label><mixed-citation publication-type="other" xlink:type="simple">Junqueira, V.S.V., Nagano, M.S. and Miyata, H.H. (2020) Procedure Structuring for Programming Aircraft Maintenance Activities. Revista de Gest&amp;#227;o, 27, 2-20. https://doi.org/10.1108/REGE-02-2018-0026</mixed-citation></ref><ref id="scirp.119178-ref3"><label>3</label><mixed-citation publication-type="other" xlink:type="simple">Reményi, C. and Staudacher, S. (2014) Systematic Simulation Based Approach for the Identification and Implementation of a Scheduling Rule in the Aircraft Engine Maintenance. International Journal of Production Economics, 147, 94-107. https://doi.org/10.1016/j.ijpe.2012.10.022</mixed-citation></ref><ref id="scirp.119178-ref4"><label>4</label><mixed-citation publication-type="other" xlink:type="simple">Kulkarni, A., Yadav, D.K. and Hamid Nikraz, H. (2017) Aircraft Maintenance Checks Using Critical Chain Project Path. Aircraft Engineering and Aerospace Technology, 89, 879-892. https://doi.org/10.1108/AEAT-10-2013-0186</mixed-citation></ref><ref id="scirp.119178-ref5"><label>5</label><mixed-citation publication-type="other" xlink:type="simple">Atli, O. and Kahraman, C. (2012) Aircraft Maintenance Planning Using Fuzzy Critical Path Analysis. International Journal of Computational Intelligence Systems, 5, 553-567. https://doi.org/10.1080/18756891.2012.696920</mixed-citation></ref><ref id="scirp.119178-ref6"><label>6</label><mixed-citation publication-type="other" xlink:type="simple">Balyuk, A. (2020) Student Syndrome in Project Management: Real Constraint or Just Human Factor? Epicflow. https://www.epicflow.com/blog/student-syndrome-in-project-management-real-constraint-or-just-human-factor/</mixed-citation></ref><ref id="scirp.119178-ref7"><label>7</label><mixed-citation publication-type="other" xlink:type="simple">Goldratt, E. (1997) Critical Chain. North River Press Publishing Corporation, Great Barrington.</mixed-citation></ref><ref id="scirp.119178-ref8"><label>8</label><mixed-citation publication-type="other" xlink:type="simple">Robinson, H. and Richards, R. (2010) Critical Chain Project Management: Motivation &amp; Overview. Proceedings of 2010 IEEE Aerospace Conference, Big Sky, 6-13 March 2010, 1-10. https://doi.org/10.1109/AERO.2010.5446879 https://ieeexplore.ieee.org/document/5446879</mixed-citation></ref><ref id="scirp.119178-ref9"><label>9</label><mixed-citation publication-type="other" xlink:type="simple">Seitza, M., Luchta, T., Kellerb, C., Ludwigc, C., Strobeltd, R. and Nyhuisa, P. (2020) Improving MRO Order Processing by Means of Advanced Technological Diagnostics and Data Mining Approaches. Procedia Manufacturing, 43, 688-695. https://doi.org/10.1016/j.promfg.2020.02.121</mixed-citation></ref><ref id="scirp.119178-ref10"><label>10</label><mixed-citation publication-type="other" xlink:type="simple">Srinivasan, M.M., Best, W.D. and Chandrasekaran, S. (2007) Warner Robins Air Logistics Center Streamlines Aircraft Repair and Overhaul. Interfaces, 37, 7-21. https://doi.org/10.1287/inte.1060.0260</mixed-citation></ref><ref id="scirp.119178-ref11"><label>11</label><mixed-citation publication-type="other" xlink:type="simple">Srinivasan, M.M. and Best, W.D. (2006) Back on the Runway: The United States Airforce Meets Critical Chain Project Management. APICS Magazine. http://realization.us/pdf/articles/Back-on-the-Runway.pdf</mixed-citation></ref><ref id="scirp.119178-ref12"><label>12</label><mixed-citation publication-type="other" xlink:type="simple">Luiz, O.R., DeSouza, F.B., Luiz, J.V.R., Jugend, D. and Salgado, M.H. (2019) Impact of Critical Chain Project Management and Product Portfolio Management on New Product Development Performance. Journal of Business &amp; Industrial Marketing, 34, 1692-1705. https://doi.org/10.1108/JBIM-11-2018-0327</mixed-citation></ref><ref id="scirp.119178-ref13"><label>13</label><mixed-citation publication-type="other" xlink:type="simple">Kozanidis, G., Liberopoulos, G. and Pitsilkas, C. (2010) Flight and Maintenance Planning of Military Aircraft for Maximum Fleet Availability. Military Operations Research, 15, 53-73.</mixed-citation></ref><ref id="scirp.119178-ref14"><label>14</label><mixed-citation publication-type="other" xlink:type="simple">Marris Consulting. (n.d) Critical Chain Project Management &amp; MRO: How a New Project Management Approach Can Help Reduce Turnaround Time? https://www.marris-consulting.com/en/our-expertise/critical-chain-project-management/critical-chain-project-management-mro</mixed-citation></ref><ref id="scirp.119178-ref15"><label>15</label><mixed-citation publication-type="other" xlink:type="simple">Airbus, S.A.S. (2005) Airbus 320: Maintenance Planning Document. Maintenance Planning Services.https://dokumen.tips/documents/a320-maintenance-planning-document-mpd-envcursobasicoiva-a-a-maintenance.html?page=1</mixed-citation></ref></ref-list></back></article>