Overcoming barriers to transferring systems engineering practices into the rail sector

Abstract

There is increasing interest within the rail sector in applying the concepts of systems engineering. This paper presents arguments that the balance of concerns differs between a typical project in the rail sector and one in the domains in which systems engineering was developed and that this difference, together with a lack of agreement on the scope of systems engineering and differences in tradition between systems engineering and the established rail disciplines, raise barriers to the effective and efficient importation of systems engineering ideas into the rail sector. It is suggested that the system engineering community can lower these barriers by strengthening published systems engineering guidance in certain areas, being prepared to express themselves in plain language and packaging their practices in a more portable fashion, while the rail community can help by being prepared to adapt the systems engineering approach to meet their needs better and introducing new practices in a measured and systematic fashion. The benefits to both communities are identified and found to justify the investment required to take these steps.

Applying systems engineering in the civil engineering industry: an analysis of systems engineering projects of a Dutch water board

“…This is in keeping with existing literature, which states all layers of the organisation should be involved in implementing SE practices (Elliott et al 2012). This includes management support as it is required to align the organisational culture to support SE processes, to make a compelling case for change, and to provide the necessary political capital (McComb et al 2008;Sheard, Lykins, and Armstrong 2000;Armstrong 2000).…”

“…However, trying to do this all at once is considered a barrier for implementing and applying SE. Instead, an incremental approach is recommended (Elliott et al 2012;Sheard, Lykins, and Armstrong 2000).…”

“…These SE improvements are mentioned in literature as well (INCOSE 2015;Locatelli, Mancini, and Romano 2014;Sheard 1996;De Graaf, Voordijk, and Van den Heuvel 2016;Whyte, Stasis, and Lindkvist 2016;Elliott et al 2012). For example, in literature it is suggested to establish a verification and validation role in the project by making someone responsible for it.…”

“…For example, SE in this industry is discussed or mentioned in peer reviewed academic journals, conference proceedings, professional magazines, and in guidelines and handbooks (Blockley 2013;De Graaf, Voordijk, and Van den Heuvel 2016;Elliott et al 2012;Van Der Meer et al 2015;Aslaksen et al 2012;ProRail et al 2008; U.S. Department of Transportation 2007; Van der Laan 2008). Also committees and working groups, such as the INCOSE 1 Infrastructure Working Group, are exploring the use of SE in civil engineering, and in the Netherlands the two main clients of civil engineering projects, Rijkswaterstaat 2 and Prorail approach and means to enable the realisation of successful systems.…”

Selling Systems Engineering by Searching for the Sweet Spot

“…"It is difficult to sell something if you do not use language intelligible to your prospective customers." (Elliott, et al 2011). Unfamiliar terms and new concepts offered by systems engineering pose a challengeobviously signaling change, something new and different, which for established industries and organizations with strong institutional culture can garner reactions of distrust, skepticism or outright refusal.…”