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.

Learning by trial and error

Marco Vos was introduced to the term Systems Engineering in 2005. At the time, it seemed primarily a tool that clients could use to control the contractual aspects of complex projects. Apparently, contractors also had to do something with it. Utility and necessity were still a long way off. Still, his interest was piqued, and skepticism vanished completely when the first version of the Dutch Systems Engineering Leidraad (‘guideline’) saw the light of day in 2007. With that explanation in hand, he discovered that it’s not a contract tool, but really a way to develop a system in a structured way.

I learned Systems Engineering in practice. At first, it was still searching for the relationship between a function tree and system tree, work packages and a Work Breakdown Structure. To really get that clear, I delved into the literature. I also interacted with experts from aerospace, installation engineering and from the Delft University of Technology. By listening a lot, I got a better grip on the subject matter. And I saw that happening around me, too.

The rise of Systems Engineering makes pretty good sense in retrospect. With the increased complexity of projects, we cannot escape working more explicitly. To me, complex means a project that takes a long time and where you have to work with various teams and colleagues you didn’t know before. Because you then have to deal with so much information, it makes sense that you need to record more information. That much information doesn’t fit in your head; you have to secure it in your team and in your project.

“This ensures that our work is never boring.”

Motivational role

The acceptance of Systems Engineering did not come naturally. The trend in the beginning was: deriving requirements is nonsense. We just build what’s on the drawing. Unfortunately, it no longer worked that way in practice. That is why it is important to have at least one person in a project who monitors the order, structure and approach. And believe me, that task is not something you do on the side, you really have to be on top of it daily. Such a systems engineer should not be working behind a screen somewhere in the corner of the site hut. He or she should be right at the entrance to the site hut to support and encourage the team. In that motivational role, I have always felt comfortable.

Another complaint about Systems Engineering that I heard a lot was that it is mostly accounting. It is true that it generates administration. But is it really more so than in the days of traditional construction specifications? Back then, every Friday, you submitted the progress statement with accompanying papers to the superintendent. If I’m honest, I still see quite large differences in the utilization of Systems Engineering and its experience. There are still parties that consider it to be accounting. Fortunately, an increasing number of organizations are fully embracing the method and integrating it into their design processes and quality management systems.

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.

‘Doing Systems Engineering’

As complexity increases, I think it is positive that clients and contractors are spending more and longer with each other during projects. From experience, I know that ‘doing Systems Engineering’ is very educational for both sides of the table. On the one hand, attention to stakeholders and asset managers with their wants and needs, and on the other hand, on-site inspection and testing. In between, the development process of decomposition, requirements derivation and integration then take place.

I hope that people in our industry remain open to the developments that are coming our way and dare to use them. This ensures that our work is never boring. Moreover, this fits perfectly with my motto: every day, a little smarter and better than yesterday. But that doesn’t happen by itself. In my view, we still don’t pay enough attention to education and training around Systems Engineering. It’s good to bring the new generation along in how you approach and structure a project these days. That approach is still left too much to the chance of those who meet each other in a project.

Lessons learned

  • Make sure you have at least one person per project who monitors the order, structure and approach.
  • Dare to do and get a little better each time.
  • Invest sufficiently in education and training around Systems Engineering.
Biography

Marco Vos

Marco Vos began his career as a designer/constructor, but quickly advanced to project coordinator at construction firm Van Hattum en Blankevoort. Following that, he held project manager roles at construction firms VolkerInfra and Van Oord. From his own company ProSysCo, he is now involved in projects such as Ruimte voor de Rivier Noordwaard, HSL-Geluid for Infraspeed and A27 Houten-Hooipolder Noord for Rijkswaterstaat, the Dutch road and waterway authority. Furthermore, he was an Systems Engineering and Systems-Oriented Contract Management trainer.

Relatics - Pioneers in Systems Engineering

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