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.

Rules for project models

The complexity of civil engineering projects has only increased in recent years, according to Piet Zuidgeest. The development of the Dutch High Speed Line (HSL) was already very large, but greenfield. In projects such as the A4 Burgerveen – Leiden or the railway track doubling SAAL Amsterdam Zuid – Duivendrecht, the environment was a particular challenge. Incorporating systems into existing traffic systems is difficult, especially if the flow of traffic must be disturbed as little as possible. Again and again, additional layers and parties must be given a place in the design and construction phase. How did Systems Engineering help him do this?

The integrated view of projects has developed relatively quickly in the Netherlands. The V-model for Systems Engineering was the starting point here. You will work from coarse to fine for component development followed by detailed design. You make this whole process transparent and testable with good evidence. If you go through those steps together, all that’s left to do after that is to implement the project. Then it just works out. I like the observation that you no longer have to explain the method in the Netherlands. You can actually always see the main points in all major projects.

“Larger projects with more complexity require more information, and the surroundings are also going to demand more and more information.”

Limits to modelability

I do think it is a fallacy that any issue or discipline must be modeled entirely in subsystems with interfaces between them from the beginning. I think it is much more effective to accept that there are limits to modeling and control. When parts of a complex project still have too many degrees of freedom and the interpretation can still go either way, I think it is wise that the client and the contractor go on a journey together and take the right steps and decisions along the way. While doing so, always remember to keep the bigger picture in mind.

Of course, this process never happens completely by itself. Good direction is essential here. You will have to continually coordinate with the client on questions such as: what exactly do you want, what level of detail do you want and what evidence? Another essential question is: when do you think something is good enough? The trick is not to go too far with the requirements set and deriving requirements. You want to go far enough to maintain the return on investment. Otherwise, it quickly costs more than it brings in. From experience, I know that in the Netherlands it sometimes goes too far. Unfortunately, there is no golden rule for this; it requires experience, fingerspitzengefühl and a willingness to consult.

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.

Information is rock hard

Information management plays a key role within Systems Engineering. It is necessary to record things in a structured and complete way. You need a certain accounting discipline for this. I realize this is not the most fun work, but you can’t haggle with that. If the information structure for a project is well established, but the discipline to work consistently is lacking, then you still have disarray and cannot demonstrate project performance. The need for proper maintenance of information is rock solid. Larger projects with more complexity require more information, and the surroundings are also going to demand more and more information. Therefore, you must take a serious and structured approach to information management from the onset.

Good information management has the added benefit of making it easier to understand each other within the project. Right now, it still takes quite a few meetings to explain exactly what parties mean. This applies both to consultation between client and contractor and to coordination between contractor and subcontractors. To further streamline this communication, we need to continue to work toward a common language. Then we can move even faster and make fewer unnecessary mistakes.

Lessons learned

  • Accept that there are limits to modeling and control in complex projects.
  • Don’t haggle when it comes to structuring and recording information.
  • Work toward a single language for stakeholders, including suppliers and subcontractors.
Biography

Piet Zuidgeest

Piet Zuidgeest studied Civil Engineering at Delft University of Technology and during his career developed into an experienced project manager for integral infrastructure projects. In that role, he was involved in projects such as HSL Combinatie Zuid-Holland Midden, A4 Burgerveen – Leiden and OV SAAL Zuidtak Oost and the Afsluitdijk. He is currently a project manager responsible for the Merwede Bridge sub-project of the A27 Houten – Hooipolder Zuid project.

Relatics - Pioneers in Systems Engineering

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