The BIM and geospatial interoperability challenge is the latest symptom of the broader problem of integrating AEC and geospatial workflows, that has contributed to low productivity in the construction sector. After the announcement about a year ago by Jack Dangermond and Andrew Anagnost of a new relationship to build a bridge between Autodesk and ESRI technologies, I thought it a good time to review progress toward interoperability between the AEC and geospatial worlds.
ESRI and Autodesk partnership
In the mid-1990s Autodesk and ESRI, market leaders in their respective areas of CAD and GIS, attempted to collaborate to address the CAD and GIS interoperability problem. The result of the agreement between Jack Dangermond and Carol Bartz at the time resulted in an unsuccessful product called ArcCAD, which satisfied neither CAD nor GIS users.
A year ago Autodesk and ESRI, again agreed to collaborate. Expected benefits cited by Autodesk and ESRI from BIM and GIS interoperability include "unprecedented reductions in permitting through improved stakeholder engagement, more sustainable and resilient design through enhanced project insight, reduced risk via improved end-to-end flow of materials, resource availability and scheduling during construction," and "providing industry and city planners the ability to design in the context of the real world enabling communities to build connected, resilient, sustainable cities and infrastructure." This time around they are probably more aware of the technical and cultural issues hindering AEC and geospatial interoperability.
Integrating BIM and CAD with GIS
Revit is Autodesk's market-leading BIM application that is utilized by designers for vertical BIM (buildings), although there are landscape architects that have managed to use it as well. Revit models include spatial data and related non-spatial information. With the release of ArcGIS Pro 2.2 in June 2018 direct reading of Revit BIM (.RVT) files is now supported. In the past Revit models had to be imported through conversion to IFC (Industry Foundation Classes) files and then go through a second conversion to a geodatabase. ArcGIS Pro 2.2 makes it possible to open a Revit BIM model directly. Tools are provided for correctly georeferencing BIM models in ArcGIS. Revit data added to ArcGIS behaves like any other 3D GIS data and can be queried, measured and analyzed.
ESRI has provided for some time a product for AutoCAD users who want to work with ArcGIS data in a familiar context. It allows CAD users to edit GIS data, navigate drawings using location, imtegrate with GIS, and turn CAD data into GIS data. Shortly after the partnership announcement, an incremental release of ArcGIS for AutoCAD 370 was announced with support for the latest versions of AutoCAD. ESRI product management also promised that the future of ArcGIS for AutoCAD would continue with improved integration with ArcGIS Online/Portal. ArcGIS Pro 2.2 provides updated support for reading and exporting AutoCAD version 2018 and 2019 format files. Furthermore ESRI product management said that other CAD/BIM/AEC applications were being considered for future development using a similar integration pattern as ArcGIS for AutoCAD.
Integrating GIS with civil workflows
InfraWorks is Autodesk's application that allows civil engineers to perform conceptual design for roads and highways in context. InfraWorks 19.2, released in September 2018, now supports the Autodesk Connector for ArcGIS. Designers and engineers can bring GIS content from ArcGIS Online into InfraWorks allowing content such as roads, pipelines, and electrical transformers to be directly imported. The link is dynamic making it possible to build an InfraWorks model directly from GIS data published into ArcGIS Online. When the GIS data is updated, the InfraWorks model can be updated and refreshed. With the release of Autodesk Civil 3D 2019 InfraWorks models can be brought into Civil 3D, Autodesk's civil design product. Together these enhancements enable workflows from ArcGIS through InfraWorks to Civil 3D.
Integrating civil and geospatial workflows with BIM
A major challenge is interoperability between Autodesk's own products. A first step for integrating geospatial workflows into Revit is for site preparation. Autodesk offers a Site Designer for Revit plug-in that is intended to enable architects, designers, and planners to shape the terrain for building sites using grading tools to model pads, parking lots, streets, sidewalks, and retaining walls. But the integration between Autodesk's BIM and civil engineering products still inhibits site preparation workflows. Civil 3D was developed on the AutoCAD platform. Revit, which was acquired from Charles River Software in 2002, was built on different data structures. As a recent post from a landscape architecture site pointed out there remains a "gaping hole ... between Civil 3D and Revit".
Improving interoperability between the two products has now become a priority for Autodesk product management. According to the latest Autodesk roadmap associated with the Revit 2019 release, Autodesk is investing in improving how civil engineers and architects can collaborate better on the site design process. The very good news is that according to the Revit product management roadmap, collaboration with Civil 3D and Revit is now an "Accepted Revit Idea", which confirms that Revit/Civil 3D interoperability has become a development priority. Furthermore new features in Civil 3D 2019 includes enhanced structural and civil design collaboration for Civil 3D with Revit..
In conclusion the new relationship between Autodesk and ESRI is being translated into concrete actions to improve the interoperability between the AEC and geospatial worlds. There is a considerable distance to go yet, but there are grounds for optimism that there is a commitment to BIM and geospatial interoperability so that in the future workflows that involve both AEC and geospatial data and software will be able to surmount the CAD+GIS barriers that have represented major inefficiencies for the construction, utility and other sectors for decades.
Comments