the integrated digital built environment · •"moving features" data describes such...

The Integrated Digital Built Environment

interoperability standards for geospatial BIM

Jim Plume

openBIM Japan, Tokyo, Friday 19 October 2018

Once upon a time …

Sensors Everywhere (Things or Devices)50 billion Internet-connected things by 2020

Source: Open Geospatial Consortium & Intel 2013

Connect ‘em all with

SensorThings API

The Integrated Digital Built Environment

PIM

EnvironmentModelling

Built AssetModelling

• data capture• regional analysis• scenario modelling• forecasting

Understanding & Managing the Natural & Built Environment

Planning, Design, Construction &

Operation of Built Assets

Geospatial Modelling(OGC: GML schema / W3C: RDF triples)

Building Information Modelling(bSI: IFC schema, MVD & bSDD)

provides context

returns as-built data• design modelling• performance analysis• simulation• construction

Top

-Do

wn

ap

pro

ach

Bo

tto

m-U

p a

pp

roac

h

Dig

ital

En

gin

eeri

ng

& A

sset

Man

agem

ent

PIM – the Scale of Things

Source: UrbanIT, after Andreas Kohlhaas

Precinct

object type: Buildingusage: Residentialname: Altona mansionsno of apartments: 64

object type: Apartmentusage: Residentialapartment type: 2 bedwater consumption: 109k litres/pano of occupants: 3

object type: Public Parkgross area: 1.4ha

object type: Public Roadname: Marion Roadvehicles/hr: 1140

object type: Cadastrelot type: strataarea: 2200 m2

zoning: 2b

object type: Buildingusage: Residentialname: Altona mansionsno of apartments: 64

object type: Apartmentusage: Residentialapartment type: 2 bedwater consumption: 109k litres/pano of occupants: 3

object type: Public Parkgross area: 1.4ha

object type: Public Roadname: Marion Roadvehicles/hr: 1140

object type: Cadastrelot type: strataarea: 2200 m2

zoning: 2b

PIMObject

DB

DB Road Data

DB Cadastre

+

+

DB Water Data

+

Precinct Information Modelling

Source: CRC Low Carbon Living

Precinct lifecycle

-Energy consumption

-Life cycle cost

-Light, sound

-Specifications

-Estimates

-Accounting

Precinct

Information

Model

-Functions

-Conditions

-Requirements

Knowledge databases

-Best practise knowledge

-Trends

-Planning scenarios

-Environment Planning

-Building Assessment

-BASIX-Visualisation, 3D models

-Crowd management

-Security

Procurement-Sustainability

-Price databases

Facility management-Letting, sale, operations

-Maintenance

-Guaranties

-Rebuild

-Demolition

-Restoration

-Scheduling

-Logistics, 4D

-Engineering

analysis

-Fire & safety

-Environment

-Lifetime predictions

-Legal data

-Occupancy

-Usage

-Audit & analysis

-Geospatial data

-Land ownership

-Utilities

Operatio

ns

Center -Transport

-Roads & maintenance

-Public services


Precinct Use Case – Tonsley Precinct Model


Precinct Use Case – Broadway Space Data9


PIM – Extension to IFC standard

Constructed infrastructure(roads, railways, bridges, tunnels,

waterways …)

Civic space(parks, squares …)

Precinct Model

Geospatial data

Reference data


Precinct Model Components & Structure

Data dictionary

(ontology)

Data schema

• objects

• object types

• properties

• relationships

PIM schema

(BIM extended)

Precinct model(s)

Precinct objects library Reference data

Link

Link

Geo-located data+

Precinct application(s)

Exemplar

Link

Operational data


LandInfra / InfraGMLhttp://www.opengeospatial.org/standards/landinfra

Land Features

Roads

Railway

Alignment

Survey

Facilities

Projects

Land Division

Core

Condominiums

Storm Drainage

Water Distribution

Wastewater Underground UtilitiesSource: Open Geospatial Consortium

OGC CityGML Standard: Solar Energy Production Potential Analysis

• Solar power potential and CO2 offset potential computed for the 550,000 buildings in the Berlin 3D city model.

• City Model is based on OGC CityGMLStandard

Source: Open Geospatial Consortium

http://www.businesslocationcenter.de/wab/maps/solaratlas/

Integrated Outdoor / Indoor location/navigation

• IndoorGML Approved Sept 2014

OGC IndoorGML

Standard

http://www.opengeospatial.org/projects/groups/indoorgmlswg


OGC Moving Features Encoding Standard

• "Moving features" data describes such things as vehicles, pedestrians, airplanes and ships.• This is Big Data – high volume, high velocity

• CSV and XML encodings of ISO 19141


• GeoScience Markup Language

• the original use case was to exchange data typically found on a geological map

• geologic units, geologic time, faults, folds, etc

• the scope of GeoSciML has expanded over the last 13 years to also cover geological sampling and analytical data

GeoSciML


Linear Infrastructure Work Program

Source: buildingSMART International

ifcRail ProjectComplex Railway Elements


ifcRoad ProjectRoad concepts and Elements


Original Source: KICT

• Carried Elements

• Superstructure

• Substructure

• Temporary works

Carried system

Supporting system

Load-bearing system Foundation system

(Superstructure)

(Substructure)

(MINnD Project)

ifcBridge ProjectElement Breakdown Structure


ifcPorts&Waterways ProjectFacility Types – Maritime Structures


• Water Control & Retaining• Breakwaters, Weirs• Dams & Levees• Seawalls, Revetments, Groynes• Sluices, Spillways & Control Gates

• Launch & Recovery• Ship & Hydro lifts• Slipways,• Dry Docks. Floating Docks

• Water Side Structures• Quays & Wharfs• Piers & Jetty

• Transport Structures• Roads, Rail, Tunnels• Bridges, Entrance Gates

• Water Areas• Ship Locks• Anchorage (Offshore & Inshore)• Navigational channels/areas

• Land Areas• Transfer Areas,• Storage/Working Areas,• Intermodal Yards,• Buildings (w/ types)

Common Schema – Project TasksSpatial (Project) Structure - ifcBridge

Proposed Schema extension for IfcBridge

Recommendations:• Make IfcFacility non abstract

• Add IfcBridge.PredefinedType(replace StructureType property)

• Make IfcFacilityPart non abstract and empty superclass

• Add IfcBridgePart

• Add IfcBridgePart.PredefinedType (replace property PEnum_BridgePartType)

• Simplify PEnum_BridgePartType(avoid overlap with Assemblies and Systems)

IfcFacility

IfcFacilityPart

IfcBridgePart


Common Schema – Project TasksGeotechnics – Ports & Waterways

• A coherent collection of median covering surface representations and clash free solid

representations

• Parameters representing variations of shape of represented state for cycles and for uncertainty.

• Parameters or material constituent sets (ifc4)

• Parameters representing flow, temperature, pressure, or load capacity (with ranges?)

• Naming, description and classification of entities to local standards.

• Quantities to include plan area, top surface area, average (local) height/depth, local volume

• Hydrology: waves, tides,

• Sea/river: top surface representation

• Currents as Strata: naming, description and classification,

• Composition: Water, salt. Volume or percentage or mass basis

• Representations: medial top surface representation, solid representation

• Uncertainty: length: overall (xyz), horizontal (x), orthogonal (y), vertical (z)

• Depths: ranges, cycles

• Flow: ranges, cycles, direction

• Temperature: value, range

• Meteorology: air

• No top surface representation

• Currents as Strata: naming, description and classification,

• Composition: Air, Water. Volume or percentage or mass basis

• Representations: top surface representation, solid representation


• Depths: ranges, cycles

• Flow: ranges, cycles, direction

• Temperature and Pressure: value, range.

Existing and intended:

• Geology: land

• Terrain/seabed: top surface representation

• Strata: naming, description and classification,

• Composition: Rock, Clay, silt, sand, water, air. Organic matter? Volume or percentage or mass basis

• Representations: top surface representation, solid representation


• IfcTopographicElement (abs): IfcTopographicOcean, Land, Air

• Pset_TopographicCommon or IfcMaterialLayerSet or IfcMaterialConstiuentSet

• IfcClassification

• Qto_TopographicElement (plan area, top area, height/depth, volume)

• Qto_TopographicRange (instant range, diurnal range, monthly range, yearly range)

• Pset_Uncertainty



Common Schema – Project TasksEarthworks – CRBIM

Model Setup Example - interim test

grids

project site context

legal Lot


• A small Site is one that fits into approximately 1 Km square• A large Site may extend over tens, or even hundreds, of kilometres

In such a large site, there is usually one common feature that covers the whole site but there may also be many distinct smaller sites that are worked on separately but still have to be totally coordinated within the overall site

For example, a railway over tens of kilometres would be the large site but within that site could be many bridges, stations and other small structures such as buildings that are part of the whole project.

Coordinating Data from Sites

works around Station 3Bridge works

works around Station 2

works around Station 1

Railway


Data Integration Architecture

Standard Model Interfaces

• On-demand Query• Proxy / Cache• Authoritative Repository

Unified / Harmonized Data Access

Water

Power

A&E

Telecom

Diverse Data Sources, Systems, Formats

Collection +/- ETL

Assets

Structures

Networks

Functions

Unified Model with Multiple Perspectives

Federation +/- Aggregation

Distinct Data-driven Applications

Planning, Investment, Lifecycle

Safe Excavation

Large-scale Construction

Disaster Planning

Application +/- Computation


Questions / Discussion

the integrated digital built environment · •"moving features" data describes such...

Documents