Whyte, J; Davies, A and Sexton, C (2022) Systems integration in infrastructure projects: seven lessons from Crossrail. Proceedings of Institution of Civil Engineers: Management, Procurement and Law, 175(3), pp. 103-109. ISSN 17514304
Abstract
A systems integration model for the delivery of complex infrastructure projects is proposed. From the Crossrail case, the authors draw seven lessons for clients to: (1) manage programme delivery as an integration activity; (2) actively manage systems integration; (3) ensure authority to make decisions; (4) maintain configuration control; (5) plan for a lengthy testing and commissioning phase; (6) appreciate supply chain products that may be part of unaligned global research and development programmes; and (7) do final integration only when there is something to integrate. Central to the argument is the idea that on such complex projects, the client cannot outsource systems integration and thus needs to recognise they retain accountability, though roles and responsibilities can be assigned to the delivery partner, supply chain, chief engineer and/or contracted systems integration firm. A key question for the client at the outset is how to distribute interface management and systems integration responsibilities while retaining accountability and oversight. Rather than managing through contracts, budgets and schedules, the authors suggest a changed approach with priority given to managing integration, and contracts, budgets and schedules that support and incentivise this.
| Item Type: | Article |
|---|---|
| Uncontrolled Keywords: | management; procurement; project management |
| Index terms: | testing, infrastructure project, complex project, project management, engineer, global research, integration, commissioning, interface management, configuration, programme, accountability |
| Subjects: | strategic project management, professional practice, completion, liability law, business, profession, project management theory and practice, professional development, project controls, organizational analysis, systems engineering, infrastructure and transport systems |
| Topics: | Roles and Professions, Business Strategy, Information Management, Organizational Design, Time Control, Project Management, Engineering Principles, Legal Issues, Quality Management |
| Descriptive scope: | 2 PC |
N.B. Descriptive scope is a count of how many of the five facets of empirical research are indicated by the words used in title, abstract and keywords. It is not intended as a judgement on the research; merely a count of the kind of word we would expect to indicate Phenomenon, Concepts, Theoretical framing, Empirical techniques, Analytical techniques. If all five are present, then a code of “5 PCTEA” will indicate this. If you feel the coding for this record is questionable, we welcome discussion around the terms we matched or the way we categorized them. The facet you would expect may not be coded, or a facet may be coded inappropriately. This can also bear on a larger question, of which facets should be treated as defining in construction management research. Please get in touch, and we will look at it. More details here