Workshop on distributed architecture and web servcies 2014-03-17 Leif Granholm

Web based BIM 11:00 Welcome Introduction of topic and goals 11:15 Web based BIM, DRUM project, short intro to Semantic Web 12:00 Experiences from ISO 15926 Workshop continues next page 12:30 Semantic Web EU project OWL ontology generation from IFC2x3 schema 12:45 Wrap up and conclusions, future actions

DRUM Project (2011-2013) Distributed Transactional Building Information Management (Tekla, Solibri, Skanska, CGI, M.A.D., Progman, Aalto) Goals Develop a framework and methods for decentralized BIM Develop methods for change management in building projects Results Web-based approach to decentralized BIM Use case analyzes Linking of three minimal design models (architectural, structural, and MEP) Exchanging status information across different parties in a building project Software Tool to convert building models Web-domain from IFC domain (IFC->RDF) Methods and tools for computing diffs between successive model versions A system for status information exchange based on distributed publish/subscribe Exploration of link generation methods based on clash checking

Multiple models of a same building Partial models Different aspects or parts of the building Contain different objects Require different expertize Created with different tools Architectural model Structural model MEP model Project plan Requirement model Owner Architect Structural engineer MEP designer Contractor ArchiCAD Tekla Structures MagiCAD Procore dRofus Parties Tools Partial models Same building Models must be compatible When a model is created/modified, information from other models needs to be used Complicating factors Fragmentation to many companies and models Friction in collaboration caused by contracts Changes are ubiquitous

Needs for building information exchange 2. Between the models and the environment 3. From project phase to operations External information Building codes, rules, regulations Infrastructure Building components and materials Sensor information People, companies, resources Building specific information Requirements Architecture Structure MEP Project plan 1. Inside a project (between models) Facility management Indoor maps project start project end time

Converting IFC models to Linked Data Enable instance-level interoperability with cross-model linking implemented with Linked Data technologies IFC Linked Data Query - SPARQL Access HTTP Ontology/schema EXPRESS OWL / RDFS Data representation IFC data RDF graph Serialization format Step File, IFCXML RDF/XML, N3, Turtle, JSON-LD Identifiers GUID URI Keep the most valuable part of IFC: the conceptual schema Switch to modern, widely-used technologies

Why Web of Data? – Linking at different levels RDF 1 RDF 2 Links between URIs + location + access + structure IFC 1 IFC 2 Links between IFC GUIDs - location - access + structure Native 1 Native 2 Links between native ids - location - access - structure Native 1 Native 2 IFC 1 IFC 2 RDF 1 RDF 2 Links between native ids - location - access - structure Links between IFC GUIDs + structure Links between URIs + location + access Native 1 Native 2 IFC 1 IFC 2 RDF 1 RDF 2 Links between native ids - location - access - structure Links between IFC GUIDs + structure Links between URIs + location + access Native 1 Native 2 IFC 1 IFC 2 RDF 1 RDF 2 Links between native ids - location - access - structure Links between IFC GUIDs + structure Links between URIs + location + access

Analysis of a minimal use case Architectural model A (ArchiCAD) based on based on Structural model S (Tekla Structures) MEP model M (MagiCAD) share space

Linking architectural and structural models 21.9.2018

LDAC workshop LDAC workshop 2014 Monday 26 – Tuesday 27 May 2014 Organised by Seppo Törmä – Aalto University – Department of Computer Science and Engineering The International Workshop on Linked Data in Architecture and Construction (LDAC) is a two-day workshop that addresses the usage and role of linked data in the context of architecture, engineering and construction (AEC). http://linkedbuildingdata.net/events/

Current Centralized Concept Downstream application data transformation Authoring software Downstream application IFC model instance Basic assumptions: IFC based model server is “Master”. IFC model is basically one logical model created and updated by several applications. Any application can technically read and write any data. Authoring software DRUM - Distributed information management

New OpenBIM Concept The ”Cloud” BIM software BIM software Native data (Master) BIM software Native data (Master) The ”Cloud” Basic assumptions: Master data in applications (native proprietary format) Applications publish a part of their data as IFC Only the application that has created and owns data can change it  No roundtrip IFC model is a combination of discipline and phase specific models that coexist throughout the project BIM software Native data (Master) DRUM - Distributed information management

”Cloud” functionality Transaction based communication Subscribing to published IFC datasets with incremental updates Any client can subscribe to any data published by another application Current situation transferred initially and after that changes only, as they are published Workflow type of action transactions with (semi)automatic routing F.ex MEP engineer needs penetrations through structures and requests these from architect and/or structural engineer Managing and publishing metadata of and from participating models Creating, managing and publishing relationships between objects in the participating models DRUM - Distributed information management

DRUM project The ”Cloud” BIM software BIM software DRUM aim: Native data (Master) BIM software Native data (Master) The ”Cloud” DRUM aim: Perform research and create foundation to define standard for interface between “Cloud” and clients Standard creates markets for “Cloud” functionality implementations and Client functionality BIM software Native data (Master) DRUM - Distributed information management

BIM – Structured data Objects describing building Functional objects Physical objects Logical objects Abstract objects Objects describing process Schedules Resources Costs Quality assurance Tasks Work Approvals RFI:s Submittals … DRUM - Distributed information management

Ambiguous modeling, different phases Detailing Engineering Architectural 21.9.2018 Leif Granholm

Reference model principle Application capable of presenting and using native objects and objects in foreign schemas (IFC)simulaneously Foreign information not bulk converted to native schema. Native objects IFC objects (retained in IFC format) 21.9.2018 Leif Granholm

Intra discipline workflow Intelligent object converter Application functionality -business logic -create relationships 21.9.2018 Leif Granholm

Actual BIM model structure Architectural spaces Structural general design MEP design MEP fabrication Architectural building parts Structural in situ concrete detailing MEP production Architectural detailing Structural precast concrete det. Architectural production Structural steel detailing Partial models coexist throughout the Project [Date] Structural site production

DRUM - Transaction based information sharing and distributed information management Budget 2 M€ Industrial Parties: Tekla (leader) Skanska Solibri Progman (MagiCAD) Logica (ERP) MAP (ArchiCAD dealer) Research parties Aalto university Georgia Tech

Funded by Tekes (Finnish government) Part of SHOK program DRUM Funded by Tekes (Finnish government) Part of SHOK program Original project idea: Create ”GSM” (Mobile network) for construction industry