Implementing Integrated Vehicle Health Management (IVHM) Protocol for Support and Reliability of Digital Project Engineering.


Noor Ullah,Sayed Atif,Jehanzeb Khan,



Project Engineering,Engineering Management,integrated vehicle health management (IVHM),Project analysis,Reliability,


Project comes up with a lot of hurdles and unnecessary obstacles due to situational and appropriate eccentricity of engineering which usually left manager and engineers to take on these challenges with their exceptional managerial skills and to work effectively in the given scenarios. Engineering Project Health management (EPHM) is an important term for management engineers which is based on framework for observation of engineered program/structure with in context understanding. This paper presents a novel framework approach of integrated vehicle health management (IVHM) in engineering management. It is applied to four industrial cases through which mutual understanding of project activity is increased. The purpose of implementing IVHM protocol in management position is reduce the analytical efforts and to increase the reliability of project analysis.


I. A. I. Lavagnon, “Project success as a topic in project management journals,”
Project Manage. J., vol. 40, no. 4, pp. 6–19, 2009.
II. C. Chapman and S. Ward, Project Risk Management: Processes, Techniques
and Insights. Chichester, U.K.: Wiley, 1996.
III. C. Earl, C. Eckert, and J. Clarkson, “Design change and complexity,” in
Proc. 2nd Workshop Complexity Des. Eng., 2005, pp. 24–33.
IV. E. Baroth et al., “IVHM (Integrated vehicle health management) techniques
for future space vehicles,” in Proc. 37th Joint Propulsion Conf.
Exhibit, 2001, pp. 1–10.
V. I. Egan, J. M. Ritchie, and P. D. Gardiner, “Measuring performance
change in the mechanical design process arena,” Proc. Inst. Mech. Eng.
Part B, J. Eng. Manuf., vol. 219, no. 12, pp. 851–863, 2005.
VI. J. K. Pinto and S. J. Mantel, Jr., “The causes of project failure,” IEEE
Trans. Eng. Manage., vol. 37, no. 4, pp. 269–276, Nov. 1990.
VII. J. Watson, “Joseph Black Lecture, Design Exhibition,” University of
Bath, 2012. [Online]. Available:

VIII. L. Wallace and M. Keil, “How software project risk affects project performance:
An investigation of the dimensions of risk and an exploratory
model,” Decis. Sci., vol. 35, no. 2, pp. 289–321, 2004.
IX. M. Engwall, “No project is an island: Linking projects to history and
context,” Res. Policy, vol. 32, no. 2003, pp. 789–808, 2002.
X. M. Cataldo and S. Nambiar, “The impact of geographic distribution and
the nature of technical coupling on the quality of global software
development projects,” J. Softw. Evol. Process, vol. 24, pp. 153–168,
XI. M. Hobday, “The project-based organisation: An ideal form for
managing complex products and systems?,” Res. Policy, vol. 29, no. 7–8,
pp. 871– 893, Aug. 2000.
XII. S. D. Eppinger and A. R. Chitkara, “The new practice of global prod- uct
development,” MIT Sloan Manage. Rev., vol. 47, no. 4, pp. 22–30, 2006.
XIII. S. Floricel and R. Miller, “Strategizing for anticipated risks and
turbulence in large-scale engineering projects,” Int. J. Project Manage.,
vol. 19, no. 8, pp. 445–455, Nov. 2001.
XIV. W. Al-Ahmad, K. Al-Fagih, K. Khanfar, K. Alsamara, S. Abuleil, and H.
Abu-Salem, “A taxonomy of an IT project failure: Root causes,” Int.
Manage. Rev., vol. 5, no. 1, pp. 93–104, 2009.
XV. S.-R. Toor and S. O. Ogunlana, “Beyond the ‘iron triangle’: Stakeholder
perception of key performance indicators (KPIs) for large-scale public
sector development projects,” Int. J. Project Manage., vol. 28, no. 3, pp.
228–236, Apr. 2010.

View Download