bim & gis integration - bim middle east · bim & gis integration information exchange...
TRANSCRIPT
BIM & GIS Integrationinformation exchange standards for the built environment
Jim Plume
BIM Middle East 2019, Dubai, 23-24 September 2019
Sensors Everywhere (Things or Devices)50 billion Internet-connected things by 2020
Source: Open Geospatial Consortium & Intel 2013
Connect ‘em all with
SensorThings API• Objectives of integration BIM and GIS• In what areas and sectors is this most relevant?• Benefits and opportunities through integration• How buildingSMART is working with all
stakeholders• Understanding the challenges
The Scale of Things
Source: UrbanIT, after Andreas Kohlhaas
Precinct
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
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
Source: CRC Low Carbon Living
Precinct Use Case – Tonsley Precinct Model
Source: CRC Low Carbon Living
Precinct Use Case – Broadway Space Data8
Source: CRC Low Carbon Living
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
Source: CRC Low Carbon Living
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
Source: Open Geospatial Consortium
Open Standards for the Built Environment
bSI IFC for Linear Infrastructure
Source: buildingSMART International
Initiation Development Approval
SC SC SCWorking
DraftStandard
FinalStandard
Standardproposal
CandidateStandard
Projectproposal
Activityproposal
ConsensusBuildingevidence
Expert Panel
output
Software validation
Do
cum
ents
Stan
dar
dst
atu
s SC
consulted
SCE review
SC
vote
SCE review
1 < 4 1 < 4 4 < 8 weeks
bSI Standards Development Process
bSI Infrastructure Project Progress Timeline
Concept Harmonisation WS – Stockholm > < bSI Summit - Beijing
First Harmonisation WS – Munich >
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
Integrated Outdoor / Indoor location/navigation
• IndoorGML Approved Sept 2014
OGC IndoorGML
Standard
http://www.opengeospatial.org/projects/groups/indoorgmlswg
Source: Open Geospatial Consortium
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
Source: Open Geospatial Consortium
• 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
Source: Open Geospatial Consortium
Model Setup Example - interim test
grids
project site context
legal Lot
Source: buildingSMART International
• 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
Source: buildingSMART International
Questions / Discussion