Using construction robots on site doesn’t necessarily mean that the whole building will be completely constructed by autonomous systems (although it will be cool if that would be possible – imagine C-3PO building you dream house!). Realistically it will be a cooperative tandem of robots and humans, guided by the Pareto rule.

The Pareto Principle, also known as the 80/20 rule, suggests that 80% of results come from 20% of efforts and 20% of results from 80% of efforts.

In context of construction it can mean that 80% of the time invested during the construction the value gained is 20% – and 20% of the time invested a value of 80% is gained. So robots can be used for repetitive tasks not adding significant value (e.g. transporting material) and humans can focus on the 20% which generates 80% value, such as craftsmanships, where robots dont give as good results as humans do.

Robots on construction sites excel at handling repetitive and physically demanding tasks. For example: Bricklaying and masonry, excavation and site preparation, material transport, welding or drilling which would be equivalent to the 80% of the time.

This would free up human workers to focus on high-value, complex tasks. Humans would be able to concentrate on the 20% for example doing: Finishing touches, creative problem-solving, supervision or quality control.

This balance not only enhances efficiency but also potentially improves health of humans, as humans are less exposed to dangerous or physically exhausting conditions, with robots taking on the heavy lifting.

As automation technology advances, the line between the 80% and 20% may shift, but the need for human oversight, creativity, and craftsmanship will always remain. Rather than replacing human workers, robotics in construction empowers them to work smarter, not harder.

Automation and robotics are not about eliminating jobs—they’re about redefining roles. Robots and humans, working together in tandem, can achieve what neither could accomplish alone.

The construction site of the future won’t just be a place dominated by machines; it will be a dynamic, collaborative ecosystem. And honestly, that’s way more exciting than a fully autonomous site. Rather than leaving everything to R2-D2 and C-3PO, I’ve always wanted to be part of the action. Or instead of watching Wall-E toil away alone, I’d much rather join in and rummage through the junkyard together!

https://auconindustry.com/2024/11/16/how-to-use-robotics-on-the-construction-site-with-the-80-20-pareto-rule/

In Germany, restrictive building regulations limit high-rise construction in most areas. Depending on the federal state and local community, developers may be restricted to a maximum of, for example, four stories in urban areas, and only two stories in smaller towns and villages. This low-rise approach has significant consequences: land is scarce and expensive, and new development areas often become densely packed with closely spaced houses, each with minimal garden space. In cities, green spaces are increasingly being converted to fill urban gaps—a practice known as “Nachverdichtung”—which consumes large areas of greenfield land and disrupts natural ecological balance.

These green spaces could instead be used to plant trees, shrubs, and flowers that support urban biodiversity, providing habitats for birds, insects, and other wildlife. This approach would help foster a more sustainable coexistence between urban development and nature, allowing cities to retain vital green corridors for ecological health.

This „Nachverdichtung“ also interferes with the natural water cycle. By covering large areas with buildings and streets, water is directed into sewer systems instead of seeping naturally into the ground, which disrupts groundwater replenishment and affects overall environmental health.

Germany has only one city with a notable skyline—Frankfurt am Main. The limited adoption of high-rise buildings in Germany isn’t due to technical constraints but rather to enduring political and cultural preferences. A strong emphasis on preserving traditional cityscapes has shaped urban planning, with many cities reluctant to alter their historic character. Additionally, high-rise living carries a stigma rooted in the post-World War II era, when “Plattenbau” prefabricated high-rise complexes were associated with social issues and became symbols of poorly planned, low-quality housing. This legacy has left a lasting reluctance to embrace vertical development.

To address the country’s pressing housing needs, Germany must explore new concepts that welcome diverse types of housing for various income levels, from luxury apartments to middle-class and affordable housing. Examples from cities like Singapore show that high-density living can be both attractive and sustainable. With more high-rise residential buildings, Germany could ease the pressure on its property market, create more space for green areas, and reduce the impact on natural groundwater systems. Embracing vertical development could offer a way to balance growth with sustainability, preserving green spaces while providing housing that meets modern needs.

https://auconindustry.com/2024/11/13/germany-must-learn-to-build-vertical-than-horizontal/

The Information Delivery Specification (IDS) has become a standard in the construction industry. This development is set to (hopefully) improve Building Information Modeling (BIM) workflows, enhancing efficiency, collaboration, and project outcomes.

In this article I want to give an overview what the IDS is and how to use it in BIM projects.

What is the Information Delivery Specification?

Since 2023, the Information Delivery Specification (IDS) has been recognized by buildingSMART International as a standard to define computer-readable exchange requirements for BIM models. It is a framework that standardizes the exchange of information across all phases of a construction project. It is used to define clear information requirements that can be easily interpreted by both humans and computers, ensuring consistency and accuracy to enable an openBIM workflow.

From Freestyle to Efficiency

There are many other possibilities to specify the information requirements e.g. LOIN (Level of Information Need), Data Dictionary or in-house standards. So from project to project there is a risk that each time a different method is used based on the preference of the employer or the different parties involved. Additionally, these methods often aren’t machine-readable, which increases the risk of human errors during data transfers. Or in the worst case there is no strategy at all to specify information requirements, leading to frequent miscommunications and data discrepancies. Information would be added ad hoc when planners realized that essential information was missing. This of course delays projects due to the need for revisions and discussions are needed to agree on a method with which all parties feel comfortable. Check out in the Knowledge Section how IDS is related to other Concepts.

So the IDS as a human and machine readable standard brings the possibility to automate the information exchange and as a standard enables an openBIM workflow.

Tomczak et al. have compared the different possibilities in a conference paper. An overview can be seen in the table below.

How IDS Works

The IDS can serve as a checklist for creating BIM models in authoring tools or be used to verify that a BIM model contains all the required project information. It is equivalent to the MVD (Model View Definition), where it can define the geometry to be shown or exported as an IFC file, or it can check the geometry of an IFC file. For example, it can verify if an IFC file contains columns. Similarly, the IDS can be used to define and check alphanumeric information rather than geometry.

So the BIM-Management can define what information need to be included or exchanged depending on a BIM use case. These information are written in the EIR (Employers Information Requirements). And the BIM-Modeller has to implement it. The BIM Management can validate if the correct information have been modeled. And this can be done automatically based on the IDS. So it can be checked, that all the objects within a BIM-Modell have a certain Property, e.g. a value for a heat influx or a fire rating.

he specifications for what information should be included in a project can be sourced from the bsDD (buildingSMART Data Dictionary) or the UCM (Use Case Management).

The IDS is readably by humans and machines. So commonly the file is based on XML-scheme. buildingSMART International uses the XSD (XML Schema Definition) to specify the structure. A specification contains metadata, applicability and requirements. Meta data contain relevant information like IFC Version or name. Applicability define what calsses, elements or properties are applied to the use case. And the Requirements contain what exactly is required to the specific class, element or property.

Example of an IDS as a XML-file:

More details are described in the bsD BuildingSMART Germany Magazine.

Example of an IDS Validation workflow

A possible workflow proposed by buildingSMART of integrating IDS into BIM projects with the development of an IDS by the client using predefined templates and Use Case Management (UCM). This specification is then sent to the modeller, who verifies that their software can fulfill the requirements set out in the IDS. The modeller proceeds to generate the necessary data, enriching it with information from the buildingSMART Data Dictionary (bSDD). This data is subsequently validated against the IDS to confirm its compliance. Once validated, the data is exported as an IFC file. If there are any issues during validation, a BIM Collaboration Format (BCF) file documenting these issues is also produced. The final IFC file is sent to the client, either directly or through an openCDE API, who then performs a final validation to ensure all specifications are met. This systematic approach helps in maintaining precision and efficiency throughout the BIM project lifecycle.

The workflow can be seen in this image from buildingSMART International.

Future Prospects

Plans are underway to introduce IDS-editors and IDS-libraries to enhance the workflow. As mentioned earlier, these tools are expected to improve BIM workflows, although their impact will depend on how extensively they are adopted. Previous tools from buildingSMART sometimes faced challenges due to complexity and user-unfriendliness, like mvdXML. However, it is encouraging that there are already software solutions that integrate with IDS, promising a smoother integration into existing systems.

Here some softwares using IDS:

• BIMvision
• ACCA Software
• BIMcollab Nexus
• Solibri

https://auconindustry.com/2024/07/06/how-to-work-with-the-new-information-delivery-specification-standard-in-bim-projects/

I have often read discussions on LinkedIn where many criticize the IFC format as complicated and useless, preferring proprietary data formats from various companies. I agree that the IFC format is more complicated than it should be, but many participants in these discussions misunderstand how the official IFC file should be used. While I understand why the confusion occurred, I want to clarify how to-date the IFC model is generally used.

Many view IFC as an exchange format that allows a colleague to continue working on a model e.g. modeling in Revit (Autodesk) and shares this to Allplan (Nemetschek) to continue modelling. However, with official finished IFC standards, this is not the case.

IFC is an open standard for exchanging model information. It is similar to how a non-editable PDF document can be exported from a Word document. Using a BIM authoring tool is like working with Word, and exporting to IFC is like creating a PDF. The IFC model is not meant to be edited but to be placed in a Common Data Environment or linked in another authoring tool for further analysis, such as collision detection or quantity takeoffs. The intention is to share the model without allowing others to modify it, which is why it is called IFC4 Reference View or Coordination View. Details are described in buildingSMART. Here, key characteristics and workflows as well as use cases are described and show how it was originally intended.

Key Characteristics:

• BIM Information Source: Remains with the originator.
• Intellectual Property: Full parametric behavior and intellectual property stay with the originator.
• Model Ownership and Accuracy: Responsibility remains with the originator.
• Model Publication: Published as an IFC4 Reference View, reflecting its as-is status.
• Receiver Access: Full access to the IFC4 Reference View content.
• No Modifications: The receiver is not supposed to modify the model.
• Analysis and Extraction: The receiver can analyze and extract model information.
• Change Requests: Must be communicated to the originator.
• BCF Support: The buildingSMART standard BCF supports these change requests efficiently.

Common Workflows and Use Cases:

• Coordination Planning: Combining discipline-specific IFC models for visual checking.
• Clash Detection: Identifying clashes between different discipline-specific IFC models.
• Background Reference: Loading an IFC model from a different discipline as a linked model.
• Quantity Take-off: Determining quantities of model elements.
• Construction Sequencing: Associating the IFC model with a construction schedule.
• Visual Presentation: Presenting the IFC model to a broad audience.

But still, editing an IFC file would be ideal for collaboration, allowing colleagues to assist each other when needed. There have been experiments with IFC4 Design Transfer View to enable model modification, but this cross-platform approach was not finalized and is not officially available, so you have to be lucky if your authoring tool supports IFC4 Data Transer View. And because some softwares support it but some don’t, it is understandable that there is much irritation. It would be beneficial for development to continue, allowing the choice between sharing an editable “Word” document or a non-editable “PDF” model being more widespread.

Of course there are possibilities to modify IFC (Reference Models) with IFCopenshell or BlenderBIM, but these are not yet user-friendly enough for the entire community to easily utilize them, but they are improving! Luckily buildingSMART has noticed that the solutions proposed are not widely spread due to the complexity and non-user-friendliness and they have a strategy to improve it.

I hope this comes soon and finally makes planning processes easier.

https://auconindustry.com/2024/07/21/understanding-how-to-use-ifc/

Extreme lunar temperatures continue to pose challenges for machines operating on the moon. Recently, Intuitive Machines’ lander, Odysseus, experienced permanent damage attributed to the harsh cold. However, a Japanese moon lander has demonstrated resilience by successfully awakening after enduring the frigid lunar night, lasting 14 days. During this period, it was strategically placed into a dormant state to safeguard against the detrimental effects of the extreme cold.

For establishing a permanent base on the moon, the poles offer a strategic advantage due to the continuous availability of sunlight and light. However, in regions outside the poles, alternative solutions will be imperative to contend with fluctuating temperatures and reliance on solar power. Otherwise, operations would be limited to the lunar day cycle, necessitating a 14-day wait for machines to resume activity.

Source: The Economist

https://auconindustry.com/2024/03/28/challenges-for-machines-on-the-moon/

#construction #moon #space #spaceconstruction