BIM and Asset Lifecycle Management for Road Infrastructure

By Natasha Blommaert and Timothy Nuttens for Autodesk University

The Flemish Agency for Roads and Traffic focuses primarily on construction, maintenance, and exploitation of regional roads and motorways in Flanders, Belgium. Therefore, we are an infrastructure builder and an infrastructure manager, involved in and responsible for the whole lifecycle of infrastructural assets. We are responsible for almost 7,000 km of roads, 7,700 km of bicycle paths, 17,000 electromechanical installations and 1,600 traffic lights, all to realize a smooth, safe and sustainable mobility for all road users. In addition, we also manage many bridges, tunnels, ecoducts, and other road infrastructure elements such as sound barriers, traffic signs, guardrails, etc.

Our BIM vision therefore focuses on the following three tracks:

As a contracting authority, we not only focus on BIM modeling during the design and execution phases of a project, but we focus even more on the aspect of BIM management. Because the data is not only relevant when building and using the model during the investment projects, the data becomes essential for the operation and maintenance during the decades after the projects are realized.

BIM as an information management process is therefore central to all our processes. And as a contracting authority, we believe it is our responsibility to support the use of BIM and to promote maximum automation of all these steps. Tools we are developing ourselves will therefore be maximally available to all stakeholders and partners with whom we manage the infrastructure, such as engineering offices, contractors, surveyors, other infrastructure managers, and municipalities.

For us, BIM implementation is more than just developing a BIM model and exchanging information. We want to reach out to all stakeholders and help make it a win-win situation for everyone. By focusing on teamwork across organizational boundaries, everyone will improve their performance and all our road users will benefit from this.

Our BIM vision is supported by a number of necessary tools to have the data delivered, processed, validated, verified, approved, stored, and of course searchable in the AIM database.

The data flow (Fig. 2) goes through several steps and is supported by several ICT applications; for example:

A digital BIM model must of course contain the correct information, which is useful during every phase of the lifecycle. What knowledge, data, and information do we want to be linked to each object in a BIM model? How can we ensure that all BIM models are shaped on the same structured base over the coming years? For this we created the OTL or Object Type Library as a common language and semantic data standard that the entire construction industry can use in Belgium. The OTL establishes uniformly which information we wish to collect during the entire lifecycle of an asset.

The starting point of the OTL are objects in the real world: a camera installation — a light pole, a cabinet, a bridge, a tunnel, a traffic sign, the vertical road structure — but also less visible and yet essential parts for the correct operation of physical parts such as software components. The OTL describes these objects and records relevant properties (including option lists) and relationships. Thanks to this library, everyone can now start building BIM models uniformly, linking geometry and information together.

In collaboration with Autodesk, the first steps were taken to insert the OTL in the BeNeLux country kit for Civil 3D 2020, providing users tools to link the OTL compliant information to the geometry.

Four of the most commonly known or accepted advantages are the following:

But what does that mean for a specific project? What can or should we do in a specific project to create these added values? How can BIM help me improve a specific project? In which project phase can we start using BIM?

A first factor to take into account is when in the project’s flow we can start using BIM. Ideally, we can start working with BIM from the first idea or concept design of the project. During the design phase, we can build up the central BIM model with more design details, more detailed geometries, and more of the desired information. When the design is finished, we transfer the BIM model to the contractor for execution and let them deliver an as-built BIM model at the end of the execution phase. Based on the OTL, this as-built model will then contain exactly the information we need for the later operate and maintain phase.

A second factor to take into account when thinking about using BIM in a project is to decide how we are going to use the BIM model in that project to get the most out of it, in relation to the total cost and complexity of the project. Choosing for which purposes we are going to use the BIM model in the project involves selecting one or more so-called ‘BIM applications.’ For our use, we have divided these BIM applications into three groups (Fig. 4):

As a source of information during the design phase, we have of course the design itself. We can decide whether or not to add more detailed construction models, visualizing for example reinforcement bars, formwork, or other construction-specific items to efficiently prepare, improve, or follow-up the actual construction works.

The existing terrain situation should also often be included in the model. But depending on the project’s need, this existing situation can be very limited or it can be very detailed. The question is whether 3D points or lines coming from a topographical measurement are sufficient, or do we need these objects to be modeled as 3D objects? If they need to be modeled as 3D objects, is a low level of geometric detail sufficient or do we need very detailed 3D objects of the existing situation — because we need to attach a new bridge part to the existing bridge, for example? In addition, a lot of public data is also available that we can add to allow a better visualization and interpretation of our model. In the example below (Fig. 5), we’ve added a colored point cloud based on Lidar measurements and 3D building volumes, that can give us, without any further processing needed, a better interpretation of the wider project environment.

Where the 3D clash and issue detection is a BIM application that is generally included in our BIM projects, there are a lot of BIM applications that are not always useful in a project. For example, is including visualizations of the project phases in the BIM model an added value or not? Is the extra cost and effort worth it? Other analyses (water drainage, shadows, noise pollution) can also be selected.

Finally, we can look at possible deliverables based on the BIM model. Here we can choose to include some specific 2D drawings, some cross sections or an object-based bill of quantities for example, linking the cost elements with geometrical elements in the model. Often, some rendered visualizations, VR, or AR applications can help to better communicate with the public and give them a better impression of what is going to be built in their backyard.

If we have made project-specific decisions about which BIM applications to include, the next step is to see what that really means. Which objects have to be included in our model to put these applications into practice, how detailed do these objects have to be modeled and what information do they have to possess to make the required analyses possible? What is the so-called level of detail we need in our model?

In our case, the level of information (LOI) is clearly described and fixed in our data standard, the OTL. The use of the OTL is mandatory, meaning that no matter which BIM applications are included in a project, all information we want to receive in an as-built model is always compliant with the OTL. Our information needs has to be covered in every project.

The level of geometry (LOG) can vary from project to project or from project phase to project phase. We can even vary the LOG between different types of objects or between different locations in the project. Depending on the chosen BIM applications, a minimum LOG is often required, to make sure we can obtain the desired results. The other way around is also applicable, when you first have an idea of the LOG you want to use in your model, more BIM applications will become possible (or not).

We define our LOG in levels ranging from 0 to +4, from basic geometries to very detailed 3D models (Fig. 6). Geometry included in our BIM models can thus vary from Level 0, which can be visualized as a classical topographical measurement, including points, lines, and polygons. Level 3 includes very detailed 3D objects, including all exterior details, and Level 4 even includes fixing bolts or internal details such as reinforcement bars. We have also foreseen a LOG -1 for objects that do not have to be visualized and modeled themselves, but for which there is nevertheless an information need.

A BIM Execution Plan is also included in the contract, describing the specific BIM aspects for that project, starting from a general template. Also in this case we maximize the uniformity in our documents. The BIM applications can be selected from a general list, so that application A used in different projects is always described the same. Also the required minimal level of geometry is represented in a uniform way, using a LOG table, describing for each project phase and each group of objects which is the required LOG.

We have also chosen to always use the same collaboration platform in all of our BIM projects — again to maximize uniformity, specifically for all of our colleagues, so that they do not depend on the platform that is chosen by the engineering firm or contractor. We, as contracting authority, provide a BIM 360 environment for all of our BIM projects (Fig. 7).

Based on the project phase in which we can start to apply BIM, and based on the selected BIM applications and Level of Geometry, we always try to maximize the added value of BIM for a specific project, taking into account the possible advantages, but also the required effort, time, and costs.

We have already begun to include and require BIM in more than 10% of our annual investment projects this year by including guidelines and specifications in our tenders, the BIM Protocol, and BIM Execution Plan. For ourselves, but also for all our project partners, a large degree of standardization is essential to use BIM more efficiently in our projects.

As program manager of the BIM and AIM implementation program at the Flemish Agency for Roads and Traffic (AWV), Natasha Blommaert is responsible for the development of the BIM vision and the organization, implementation, IT coordination, and standardization of BIM for road infrastructure. She focuses on getting every stakeholder involved to work together towards an advanced and digital asset information management to improve the realization, maintenance, and exploitation of the Flemish road infrastructure. With her BIM, CAD, and GIS experience and change management expertise, she is also an enabler of digitization of the construction industry in general and a regularly invited speaker on events about BIM, digital twins, infrastructure management, digitization and standardization, smart applications, etc. In the Flemish Road Agency she also coordinates the GIS and Data Management team and she represents the agency in various national and international boards or steering committees.

Timothy Nuttens is BIM manager at the Flemish Agency for Roads and Traffic. He focuses on the practical aspects of how to implement the OTL data standard in BIM models and the collaboration with engineering firms and contractors in the agency’s projects. He also works on developing the BIM guidelines for these projects by elaborating the necessary contract documents and a standardized BIM Protocol and BIM Execution Plan for infrastructure projects. Together with his team, he is also responsible for the support of the internal colleagues involved in BIM projects throughout all project phases.

Related posts:

Everything you need to know about eSports Boxing Club.

Meat is an important part of our culture. With the rise of lab-grown beef and poultry, how will our attitudes changes?

The Velo Labs team is excited to announce that VELO tokens will soon be listed on VCC Exchange! Trading pair(s) and timing to be announced shortly.