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.

Working based on requirements

Mark Moens first encountered Systems Engineering during the tender phase for the Maasvlakte 2 project. The call for tender from the Port of Rotterdam was based on system-oriented design, and this was new to the tender team. Initially, he was still somewhat hesitant about Systems Engineering with regard to managing complex projects. Still, he and his team found the right interpretation. And with success. The project was delivered on time, within budget and completed with the agreed-upon quality. By now, the approach is embedded in the market as well as in his own organization.

I especially had to get used to a different division of roles at the Maasvlakte 2. The responsibilities were different than in other projects. The client had a small project organization, inspected the process and monitored the commissioning. My team had many more responsibilities than I was used to. In port construction, it was common for the client to prescribe inspections for the agreed depth, for example. Now, the contractor had to determine the inspection themselves and indicate whether an object was approved or if there was a discrepancy. We had to think primarily about meeting the requirements rather than the solution.

“Despite my initial reluctance, I now see Systems Engineering as an important collaborative tool.”

No surprises

After these initial experiences, the Systems Engineering approach was fully embedded within the dredging and marine contractor Boskalis. It is the standard approach to any major project. In a tender, you get large amounts of information, increasingly digital, from which you have to extract the requirements yourself. All this information should be read carefully beforehand; otherwise, you may run into surprises later.

In my experience, Systems Engineering provides a lot of guidance, especially for complex projects. It helps to better understand the demand and identify the most critical requirements. If it turns out that there are conflicting requirements, you spot it quickly and can still consult with the client. In the past, the solution direction could sometimes drift somewhat away from the demand during the process. The result then, while beautiful, did not meet the original demand. We are able to prevent this now. For me, that outweighs the extra administrative work you have to do at the beginning of a project to get the requirements right.

The beauty of Systems Engineering is also that it makes the division of labor easier. You can clearly specify the demand for the different disciplines that will work with it. The work breakdown structure is thus directly linked to the requirements, so you don’t lose sight of consistency. And because you easily keep track of everything in one system, you can keep track of progress. You always maintain control.

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.

Fast delivery

That control also has advantages later in the process. For example, for inspections during execution. You can do those very specifically because everything is explicit. As a result, if there is an anomaly, you can take immediate action. You may deviate, but you must show that you meet the original requirement. An additional benefit is that during the project, you meticulously record all relevant information that is also required in the commissioning report. During the project, you already maintain the commissioning report with your inspections, making the completion of the commissioning report relatively easy. At the Maasvlakte 2, the final actions had already been carried out two weeks after delivery.

Despite my initial reluctance, I now see Systems Engineering as an important collaborative tool. It helps to understand the client’s requirements and provides a basis for taking on the project with your entire organization. You really have to do that together. There is no such thing as the Systems Engineering department; it is an integral part of the project approach. Just like safety and quality management.

Lessons learned

  • Take the extra administrative effort of Systems Engineering in the preliminary phase for granted, as it always pays off in the further course of the project.
  • Use Systems Engineering not only for collaboration, but also to distribute the work.
  • Consider requirements as your new handle on project management.
Biography

Mark Moens

Mark Moens studied Civil Engineering at Delft University of Technology. He then began his career at engineering firm Oranjewoud, now Antea Group. Starting in 1991, he joined the dredging and marine contractor Boskalis as a project engineer. Here he held various management positions and was involved in the realization of the Maasvlakte 2, among other things, as engineering manager. He currently serves in an international role as general manager Global Engineering at Boskalis Offshore Energy.

Relatics - Pioneers in Systems Engineering

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