Benefits of Adopting Systems Engineering Approaches in Rail Projects
Total Page:16
File Type:pdf, Size:1020Kb
BENEFITS OF ADOPTING SYSTEMS ENGINEERING APPROACHES IN RAIL PROJECTS by BRUCE JEFFREY ELLIOTT A thesis submitted to the University of Birmingham for the degree of DOCTOR OF PHILOSOPHY School of Civil Engineering College of Engineering and Physical Sciences University of Birmingham April 2014 University of Birmingham Research Archive e-theses repository This unpublished thesis/dissertation is copyright of the author and/or third parties. The intellectual property rights of the author or third parties in respect of this work are as defined by The Copyright Designs and Patents Act 1988 or as modified by any successor legislation. Any use made of information contained in this thesis/dissertation must be in accordance with that legislation and must be properly acknowledged. Further distribution or reproduction in any format is prohibited without the permission of the copyright holder. ABSTRACT Systems Engineering (SE) is being used increasingly in rail projects, with the aim of creating better systems in better ways, thus generating a return on the effort invested. However, it is not entirely clear what exactly that return will be or how to maximise it. This thesis contains the results of research into the relationship between the adoption of SE in rail projects and project outcomes. The writer shows that determining the success of a project, and thus the impact of SE, by simply measuring its cost and duration and assessing the performance of the system that it delivers, is problematic. He argues that the adoption of an SE approach can lead to decisions to correct faults in the system design and make other desirable changes being taken earlier, which will improve the outcome in most cases. Theoretical reasons and practical experience lead him to believe that many of the benefits of applying SE on projects will be enjoyed as a consequence of reducing change latency, where change latency is defined to be the unnecessary delay in deciding to make a change. A tentative theory of how SE can reduce change latency is proposed and tested against data collected from nine rail projects. The data corroborate several proposed causal mechanisms in the tentative theory but also suggest that the reduction in change latency achieved depends upon other factors, particularly the contractual and quasi-contractual relationships between the parties to the project. For practitioners considering whether to apply SE on a project, the research findings provide encouragement but also a warning that the full benefits of applying SE will only be enjoyed if other pre-requisites for sound decision making are in place. The findings also provide guidance on how to adapt SE practices when applying them to rail projects, in order to maximise the benefits enjoyed. The writer argues that change latency is a valuable metric for both practitioners and researchers and that formulating and refining explicit theories about the manner in which SE delivers benefits can assist researchers investigating these benefits to build upon each other’s work. This thesis is dedicated to the many men and woman working on railway projects who take pride in their work and deserve to be able to take pride in their achievements; to my parents, Jeremy and Elizabeth, who brought my siblings and me up to value learning; but above all to my wife, Caroline, without whose support it could never have been written. ACKNOWLEDGEMENTS It was Ian Shannon, my manager when we both worked at Atkins, who suggested that doctoral research was the correct vehicle for me to find out what I wanted to know about the benefits of systems engineering. Ian remained my industrial supervisor long after we both left Atkins. I am grateful to him both for the initial inspiration and for his sustained encouragement. I am also grateful to Atkins, who provided financial support during the early stages of this research. My academic supervisors, Professor Felix Schmid and Professor Clive Roberts, have provided me with consistently sound advice – never trying to steer the direction of the research – but drawing on their considerable knowledge and insight to help me evaluate where I had got to and to find a way forward. I am grateful, not only for their wise advice, but also for their patient encouragement. More than a dozen busy managers and engineers have given up their time to help me collect data about the projects on which they worked. Having promised them anonymity, I cannot name them here, but I wish to record my gratitude to them and also to their employers, where they gave permission for data to be collected for this research. The research would have been impossible without this input and I am grateful to those who provided it. The people who build complex systems are, in my experience, realistic about the chances of encountering disappointment along the way but remain stubbornly keen to learn how to do better. I have been granted access to project data in the belief that I may be able to make a contribution to this cause. I hope that in this thesis I can discharge that trust. TABLE OF CONTENTS 1 INTRODUCTION ........................................................................................................ 1 1.1 Background to the research .............................................................................................. 1 1.2 Generic objectives for the research .................................................................................. 2 1.3 The structure of this thesis ............................................................................................... 3 1.4 A note on style .................................................................................................................. 5 1.5 Key points .......................................................................................................................... 6 2 THE NATURE OF THE RESEARCH PROBLEM ................................................................ 7 2.1 Observations on the field of study .................................................................................... 7 2.2 The objects in the field of study do not easily permit controlled experiments ............. 10 2.3 The objects in the field of study are defined differently by different observers ........... 10 2.4 The objects in the field of study are drawn from populations of great variety ............. 11 2.5 The objects in the field of study are subject to continual change .................................. 12 2.6 Reflections ....................................................................................................................... 13 2.7 Key points ........................................................................................................................ 13 3 PRIOR WORK .......................................................................................................... 15 3.1 The outcomes enjoyed by projects ................................................................................. 15 3.2 Theories about how SE contributes to project outcomes .............................................. 17 3.3 Empirical evidence .......................................................................................................... 24 3.4 Reflections on the state of knowledge ........................................................................... 28 3.5 Planning a way forward................................................................................................... 29 3.6 Key points ........................................................................................................................ 29 4 PRELIMINARY INVESTIGATIONS .............................................................................. 31 4.1 First preliminary study .................................................................................................... 31 4.2 Second preliminary study................................................................................................ 34 4.3 The nature of rail systems and projects .......................................................................... 38 4.4 Key points ........................................................................................................................ 41 5 A WORKABLE CHARACTERISATION OF SYSTEMS ENGINEERING ............................... 43 5.1 Introduction .................................................................................................................... 43 5.2 SE in the wider systems movement ................................................................................ 43 5.3 Existing characterisations of SE ....................................................................................... 44 5.4 Core SE ............................................................................................................................ 51 5.5 Good practice in core SE ................................................................................................. 59 5.6 Key points ........................................................................................................................ 60 6 A WORKABLE CHARACTERISATION OF ‘BETTER’ ...................................................... 61 6.1 Characterising ‘better’ in terms of time, cost and performance .................................... 61 6.2 Characterising ‘better’ in terms of volume of change ................................................... 63 6.3 Change latency ..............................................................................................................