books

In this article, experts discuss how Systems Engineering is applied in real construction projects, highlighting lessons learned and difficulties encountered over years of experience.

Standardization by listening

Over 20 years ago, Rijkswaterstaat, the Dutch road and waterway authority, chose the principle of outsourcing “The market, unless…”. As the largest client in the civil engineering sector, although Rijkswaterstaat still determined what function should be realized, it would henceforth leave the design and execution to the market. In that case, you have to engage in functional specification and you automatically end up with Systems Engineering, which was on the rise at the time. Martine van Dalfsen, Niels Meijer and Willem van de Wetering, each in their own roles, were closely involved in the implementation and adoption of Systems Engineering within their organization. Niels was involved from the beginning, Martine and Willem only got involved around 2011. They look back on the shifts this development has brought about. And how Systems Engineering has been embedded in the corporate culture through an engaging learning process.

Around 2000, it seemed like Systems Engineering was the new gold. Systems Engineering thinking was gaining steam, and with the choice of “The market, unless…”, Rijkswaterstaat underwent a reorganization. Moreover, we saw that after the construction fraud, there was also a need for more transparency in the market. In the face of these major changes, Systems Engineering had enormous potential. The method not only helped to better manage projects, it also made it clear what you wanted as a client and whether you were demonstrably getting that result from the contractor. The promise was great. However, we did not yet know exactly how to make it work in practice.

The method first had to land well in our organization, and from the projects soon came the demand to support Systems Engineering with effective and flexible tooling. This helped to further shape our own processes and thinking. At first, we worked in Excel and later, a different Systems Engineering tool. Because functional specification is about defining relationships, the use of a relational database is a logical choice. In practice, this meant that projects soon began using Relatics. In this experimental phase, there was no defined approach or standard.

“Standardization certainly does not mean that developments stand still; quite the contrary. We continue to improve Grip with small iterations.”

One template

Because Systems Engineering was new to the organization, a business case had to be built for software support to projects. There was initially an Systems Engineering tool that did not fit the needs of the projects, leading to the decentralized application of Relatics. Projects made their own choices and applied them as they saw fit. An inventory revealed that some 25 different environments were in use. This fueled the call for a central template, which continued to be developed under the name Grip.

The starting point of Grip was to bring standards and projects closer together. This way, standards improved and projects in turn began to work more according to these standards. Where no standard was yet available, namely at the instruction level, projects did initially set up the processes themselves. Projects thus provided a joint response to this need, which in turn provided useful feedback for the standards. It was crucial to carefully observe how Systems Engineering was deployed by the project teams. In preparing the business case, there was deliberately a lot of room for dialogue with the project teams. We literally went into a cubicle for project analysis on the information models and to ask what the teams needed. This soon became mostly about interpretation. There was barely any more discussion about the method itself. This approach proved to be a good basis for developing best practices that soon found their way into projects.

Generating support

Standardization certainly does not mean that developments stand still; quite the contrary. We continue to improve Grip with small iterations. We were actually already working agile when it wasn’t even called that. We retrieved requirements and quickly created output, which prompted the request for immediate feedback. This approach helped identify experiences from the projects and get everyone involved. This was also necessary to create and maintain support. Ingrained in the engineering culture is the desire to solve things yourself. This underscored the importance of providing an appropriate solution quickly under the right circumstances. Otherwise, there is always the risk that people will start working on their own, which can undermine the standard.

Traceability

The demand for customization, by the way, remains a concern. Every project wants some customization. But that should be limited. The challenge is to entice teams as well as convince them to stop using customization. This works pretty well by always asking enough questions and trying to get to the bottom of the underlying problem. We engage in the conversation and ask: do you really need it? Often that turns out not to be the case or the standard already provides it. The room for customization is much less and the need also decreases. That said, it is crucial to continue to listen carefully to the projects. With Grip, it has helped us that we do this with a compact team. This is how we maintain clout. We know each other, know who does what and how we handle questions. Moreover, we record everything. Systems Engineering is all about traceability and, in our opinion, so is support; practice what you preach.

Do you want to discover more lessons learned?

This article is part of a collection brought together in this book, based on interviews and practical experience from the construction industry.

Libraries

Systems Engineering is the systematics that focuses on the entire life cycle of an asset. In it, Grip supports all work that is project-based in nature, regardless of the stage the project is in. The benefits go beyond just project support. In recent years, we have accumulated an enormous amount of experience and knowledge within Rijkswaterstaat. We record this knowledge in libraries. This way, we can reuse generic knowledge and information in specific projects. Because we can easily import the foundation of projects, projects get a head start.

Libraries are also very useful for the significant maintenance task we currently have. We also tackle maintenance and renovation projects on the basis of Systems Engineering. Libraries with standards for different elements are very useful for that. This completes the circle, from construction to maintenance. The final step, then, is the conservation function. In the future, we also hope to track the desired performance of our objects in this life cycle. Flawless exchange with maintenance systems is a prerequisite for this. We also want to be able to take the functions of an existing object from a library.

In practice, we aren’t quite there yet. Moreover, it then also becomes important to exchange relevant information unambiguously within the entire chain. The IT resources to organize this are available, but there are other interests at play. Parties have their own processes, for example, and that still makes the flawless exchange of information with a single taxonomy difficult. Such a taxonomy must be sector-wide. This is not so much an IT problem, but rather a challenge around operations and different organizational cultures. As with Systems Engineering adoption, this is a learning process that we go through together. We are already on our way, but have not yet reached the finish line.

Discovering together

The development of Grip over the past 10 years has been and continues to be successful. Although little internal PR was done, there was an oil spill effect. It is important that people continue to share positive experiences through word of mouth. It helps that Grip is based on what happens in the projects. We have seen that it is gradually becoming used at every level. Understanding that you don’t have a quality system where all the steps are elaborated down to the instructional level created the space in Grip to do that interpretation based on the needs of projects. It was uncharted territory that we discovered by playing and practicing with the organization. This applies to both the method and the supporting tools. You can always grow to maturity if you provide space to explore together. In doing so, you are allowed to make mistakes, as long as you fix them.

Lessons learned

  • Map best practices by project and involve everyone within projects.
  • Realize that tooling and Systems Engineering always go hand in hand.
  • Monitor the standard and limit customization, but do not become like rigid police.
  • Make sure the positive experiences are spread through word of mouth.
  • Keep listening carefully to the needs of project teams, and the demand for customization will naturally drop.
  • Standardize knowledge and information from previous projects and reuse it in new projects.
Biography

Martine van Dalfsen

Martine van Dalfsen studied Civil Engineering and started as a project manager at USG Innotiv in 1998. She then moved on to Rijkswaterstaat, where she worked as a contract manager. Subsequently, she was also a technical manager. Since 2010, Van Dalfsen has been a systems engineer and systems development consultant at Rijkswaterstaat.

Niels Meijer

Niels Meijer studied Civil Engineering and began his career in various positions at SCIA. He then became program manager of ICT Engineering at the Construction Department of Rijkswaterstaat. He completed the knowledge management technology program at Middlesex University in 2002. In 2007, he transferred to the Rijkswaterstaat Data & ICT Department where he became ICT product manager. He has since joined the Central Information Facility (CIV) of Rijkswaterstaat as ICT service manager for Construction Maintenance-Technical Management.

Willem van de Wetering

Willem van de Wetering studied at Wageningen University and Research and began his career there as a researcher. He later obtained an MBA from Business School Netherlands. After his research work at the agrotechnical research institute, he became a business consultant at Imtech. In 2006, Van de Wetering began working as a senior consultant at Rijkswaterstaat. He first worked at the Traffic and Shipping Department and later transferred to the Large Projects and Maintenance (GPO) office in Utrecht.

Discover more lessons learned

Lesson learned
One shared world

The introduction of Systems Engineering at Rijkswaterstaat, the Dutch road and waterway authority, presented challenges for both clients and contractors, Ton…

Buitenring-Parkstad-Limburg-001
Lesson learned
Throwing it over the fence

According to Harro Verhoeven, information management is key within Systems Engineering. In his view, however, when recording data in the process,…

Lesson learned
Spot the differences

Timo Giling saw Systems Engineering enter the civil engineering sector through ProRail, the Dutch railway authority, and Rijkswaterstaat, the Dutch road…

Relatics - Pioneers in Systems Engineering

Pioneers in Systems Engineering
Insights and lessons learned from construction industry professionals.