Why do you have to look at buildings, tasks and teams holistically?

Let us look at this challenge completely detached from BIM and Lean Construction. The builders of many past eras also faced these challenges. The amount of time we can use computers and software to support it is small. Buildings and their assemblies, components and components are more technical today and therefore more complex in a different way and we now have computers and software at our disposal as technical aids. So why should we not take advantage of technological achievements? The question then arises, however, whether we are exploiting and applying the potential and whether we have the necessary digital tools at our disposal.

In large construction projects we have thousands of tasks. The number can easily go into the 6-digit range. Each planned, installed, serviced, and disposed of part is associated with a task that must be completed by a different team member in the respective phase. This realization is not new, but it must be kept in mind.

Different parts are assembled into assemblies. The team responsible for this task must perform the different tasks in a specific order. The chain of tasks can be summarized as a sequence under a milestone. If this sequence is used more often during the construction of the structure, we can use this sequence for cycle planning. It follows from this realization that the cycle planning is a special case. In a digital model planning you can copy the constellation of the components. However, new objects are created with each copy. These findings are not new either.

Each part, all related tasks, and all related executing team members are continuously expanded with this information. In large buildings, there are countless but limited components, tasks and executing team members. The resulting amount of data is constantly growing. The larger a building is, the larger the number of paper folders in the past, the more difficult it was to obtain information about individual components and their development.

Cars manufactured in a factory on the assembly line can be manufactured in shifts regardless of weather conditions and times of day. Buildings are built according to location and are subject to different weather conditions. Similarly, shift operation is usually not possible there. The various influencing factors affect productivity, completion times, and costs. As a result, teams need to work more agile, transparent, and more cooperatively. The operational plans drawn up by the project managers are put to the test every day and must be able to be efficiently always adapted. An announcement from top to bottom is no longer up to date.

Everyone is talking about Industry 4.0. Digital support is designed to be popular in all areas of work and to help increase productivity. At the same time, intelligent digital factory witnesses, teams and team leaders are to support and relieve the burden. At the same time, the satisfaction and coexistence of all team members can be positively changed through a change in cooperation. Everyone can participate. No one is excluded. You can only exclude yourself. I have already actively supported Industry 1.0, 2.0 and 3.0. In level 4.0, the last one is also expected to make the leap into the digital world. Users can be advised to finally move from levels 1.0, 2.0 and 3.0 to level 4.0. Everyone is welcome to analyse their own status quo and then rally and act.

The question then arises whether our software manufacturers and their digital tools really make this leap, or whether the users who would like it still to fail because of the many unresolved problems in the digital chain. Only when the last paper folder, the unnecessary phone calls or the flood of e-mails have disappeared, the software developers have made their contribution to the topic of Industry 4.0. Industry N.0 sends greetings. I have been looking at the development for over 30 years and over the last 5 years I have had the time to analyse developments in the areas of BIM and Lean Construction intensively. There is still work to be done. Get started and improve the situation of your users. If someone feels unfairly treated, please feel right to contact me. It will be a pleasure to analyze your software.

Tagged with:

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.