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.

Spot the differences

Timo Giling saw Systems Engineering enter the civil engineering sector through ProRail, the Dutch railway authority, and Rijkswaterstaat, the Dutch road and waterway authority. He found that for many parties, it was still difficult to get the hang of how Systems Engineering works at first. While he certainly still sees differences in its application in the Netherlands, he does note that Systems Engineering is currently the de facto standard for complex projects in the non-residential construction and infrastructure sector.

In the beginning, we were still searching for how to create a good requirements set and link objects to eventually develop a good system. I had the opportunity to develop my own knowledge at engineering firm Movares. They saw that there was a need in the market and sought guidance on how to capitalize on this opportunity. I immersed myself in the methodology and began to help use Systems Engineering inside and outside my organization.

Structured data storage

The use of tools was a logical step for this. Especially with complex projects, you need to store all the information around requirements, objects and work packages in a structured way without losing track of the interrelationships. The solutions available at the time came from other sectors and did not fit the specific nature of construction. Relatics offered what the infrastructure sector needed, and because Rijkswaterstaat embraced this tool, it was practical to join in as an engineering firm or contractor as well.

“The tooling helps collect and organize data, but users are mainly interested in what they can get out of it in terms of reports and overviews.”

Maintaining energy

I did find that ease of use plays a major role in adoption. The tooling helps collect and organize data, but users are mainly interested in what they can get out of it in terms of reports and overviews. It really should be as easy as possible, preferably with just a few mouse clicks. It is worth investing in this when setting things up. Because if you approach Systems Engineering too high-handedly on projects, you run the risk of draining energy and losing support.

Over time, Systems Engineering became established in the Netherlands. Yet I have noticed that despite 20 years of Systems Engineering, the level of knowledge in the infrastructure and non-residential construction sector is still relatively limited among a large group of people. While many people are doing something with Systems Engineering, the focus is still on requirements and verification. However, that is only one part of Systems Engineering; in fact, there is much more to it. I do see a difference between installation engineering and civil engineering here. The installation sector is clearly leading the way. More complexity often also encourages the more effective use of Systems Engineering.

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.

Broadening my view

It was very fascinating to be able to broaden my view beyond my experiences in the Netherlands. Through INCOSE, I got a good idea of the deployment of the method in other countries. This made it clear to me that the Netherlands held a different position in the international community.

First, I noticed that the Systems Engineer in the Netherlands is usually a role that is mostly filled by someone who manages the tool and is mainly used to facilitate the design process and record the associated administration. In other countries, you see that the engineering process itself is the focus and Systems Engineering is seen as the way this engineering process is designed. As a result, the systems engineers are also the seniors there who, as “principal engineers,” lead the integrated design process.

Another big difference is in the application domain. Systems Engineering thinking was originally focused on large industries such as software, aerospace and defense. Internationally, it is clear that Systems Engineering is therefore mainly applied in those sectors. In the Netherlands, the emphasis is different. Here, Systems Engineering is commonplace particularly in the civil engineering and non-residential construction sector. Better yet, we are the global leaders in this regard. So it is nice to see that we have enriched the thinking we adopted years ago and are slowly spreading that knowledge to other countries.

Lessons learned

  • Pay above-average attention to software output when adopting Systems Engineering; generate rather than type.
  • Pay equal attention to all aspects of Systems Engineering, looking beyond requirements management and verification.
  • Recognize that Systems Engineering has strong differences internationally in terms of embedding and maturity.
Biography

Timo Giling

Timo Giling started his career in the rail sector. He worked for NS, Holland Railconsult and engineering firm Movares, among others. He then went to work for ENGIE Infra & Mobility (now Equans) where he held various roles including Systems Engineering consultant, project, tender and contract manager. He is currently a contract manager at water board Aa en Maas. Giling was president of INCOSE Netherlands for more than four years and was involved in SE-Boost, a stimulation initiative for Systems Engineering in the civil engineering sector and in HEEL, the development of Systems Engineering at water boards. He also provides training and education on Systems Engineering for various colleges and associations.

Relatics - Pioneers in Systems Engineering

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