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.

Systems thinking in the built environment

In his work, Wim Pullen always put the users of buildings first. After all, they are the ones who need to work pleasantly. Yet this group did not always have a clear voice in building plans and renovations. In the past, other stakeholders, such as the client or architects, often determined the requirements a building had to meet. Systems Engineering, he says, has helped make the user’s perspective clear and testable in a systematic way.

Systems thinking entered my working life through practice. At the Central Government Real Estate Agency, I was tasked with improving the matching process between buildings and users. Previously, this was done primarily based on experience and feeling. There was no clear structure. To find the solution for better matches, I looked to a systematic approach. However, this does mean you have to properly define the system first. And determine the interrelationships and boundaries that exist within them, so that you can also monitor those well. Principles that also play a key role in Systems Engineering.

After transferring to the Center for People and Buildings, one of the things I researched was how organizations can use buildings better and more efficiently. With an eye on quality and cost, of course. In order to do that, you need to know what the user wants and needs. This will give you a better understanding of the desired functionality and also allow you to estimate what will be needed in the future. Systems thinking played a role here as well. User experiences were systematically mapped and models were used to look for constants in behavior.

“To increase the uniformity of the construction brief, it was crucial to understand and record all perspectives, requirements, wishes and interrelationships.”

Tower of Babel

I discovered the power of Systems Engineering during the second opinion for the construction brief for the renovation of the Ministry of Finance in The Hague. Several parties had prepared a thick set of requirements for this PPP tender. The result was a fragmentary document with lots of different definitions. This left room for unwanted interpretations by everyone involved. This would create a kind of Tower of Babel, with which no one would ultimately be satisfied.

To increase the uniformity of the construction brief, it was crucial to understand and record all perspectives, requirements, wishes and interrelationships. By looking at the brief from a systems perspective, we succeeded. This way, it was always clear from which point of view a requirement was formulated: from the user, the building or the environment.

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.

The user in the picture

For a long time, the user hardly played a role in building plans. The architect did do an intake, but that was often with management. The real users did not come into the picture. The result was that the requirements and wishes were far from complete. I see in recent years that awareness has grown. A good idea of the requirements and wishes of users is necessary to design or adapt better buildings.

The prerequisite is that you systematically identify those requirements and wishes. You engage in conversations about the building in order to distill the essence and definitions that are unambiguous and testable. This way, Systems Engineering helps put issues on the agenda and make them discussable. This goes far beyond technical building requirements. To create a good building, the consequences for users must also be considered. Here it is essential to understand the impact of the choices. Only when those are clear can you ask the question: do you really want this? In this way, Systems Engineering acts as a mirror for all involved.

Lessons learned

  • Pay explicit attention to the user of the building.
  • Determine a unified set of definitions on which there is consensus with all stakeholders.
  • Systematically describe user requirements and desires and make them testable.
Biography

Wim Pullen

Wim Pullen began his career in 1983 with the Central Government Real Estate Agency (Rijksgebouwendienst, now Rijksvastgoedbedrijf) where he initially worked on housing. He later headed the agency’s research department, which included research on the relationships between buildings and people. From 2000 until his retirement in 2021, he was director of the Center for People and Buildings in Delft.

Relatics - Pioneers in Systems Engineering

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