Session S101

Introduction to BIM – GIS

Integration

John Przybyla, PE, GISP,

Woolpert, Inc.
 National Institute of Building
Sciences
National Institute of
• 1974 - Public Law 93-383, Sect. 809 Building Sciences
– Bridge between Private and Public Construction
– Non-governmental – Unique 501c3 Organization
– Unique in that it represents all disciplines in industry
• Architects, Engineers, Contractors, Insurers, Unions, Manufacturers, Legal,
Housing, Vendors, Owners, Consumers, State & Federal Government, Codes
& Standards, and Testing
– buildingSMARTalliance is a council of the Institute
– Formerly International Alliance for interoperability

• NIBS Related Products –

– Construction Criteria Base
– Whole Building Design Guide
– National CAD Standard
– National BIM Standard

An Authoritative Source of Innovative Solutions for the Built

Environment
 buildingSMARTalliance Relationships
NIBS
NIBS
Board
Boardofof
Directors
buildingSMART
Directors
International

NIBS President

buildingSMART alliance™ Staff Board of Direction

Alliance Programs

Projects
External and Internal Projects From all members External and Internal Projects
of the Alliance

Sponsors and Members

The Alliance

Vision
• A global environment where all participants can readily
and transparently share, apply and maintain
information about facilities and infrastructure to
enhance quality and economy of design, construction,
operation and maintenance
Mission
• Improve all aspects of the facility and infrastructure
lifecycle by promoting collaboration, technology,
integrated practices, and open standards
buildingSMARTalliance BIM-GIS Project
http://www.buildingsmartalliance.org/projects/activeprojects/27
Elements of the Project Charter
• Spatial awareness across AEC lifecycle is defined to be
critical requirement
– Inside and outside of a building

• Identify and define requirements where convergence

between geospatial and building information across the
building lifecycle is needed

• Review and where possible adapt geospatial standards-

based workflows that meet requirements, save time and
effort where convergence exists

• Identify existing standards that are ready for immediate

testing for candidate status
BIM-GIS Project Focus
• How can BIM applications and information seamlessly
interact with geospatial information during across the
lifecycle process to address requirements related to site
conditions and surroundings?

• How can BIM and geospatial applications be used to

communicate campus-wide information requirements for
lifecycle facility management and operations?

• How can 3-D CAD and geospatial portrayal services

facilitate modeling in campus-wide and facility
perspectives for as-is BIM model and further extension
for planning or design activities?
Committee Members
• Deke Smith • Jaymes Cloninger • Peter Sforza
• Earle Kennett • Mark Butler • Keith Beck
• Bill East • Hector Camps • Mike Parkin
• John Messner • Phillip Cousins • Joseph Mudry
• Dennis Shelden • Diane Davis
• Horatio McDowney
• Calvin Kam • Alan Edgar
•
• Steve Sims
• Mitch Schefcik Kristine Fallon
• Chris Andrews • Dave Jordani • Francois Grobler
• Paul Cote • Dave Morris • Jason Mayes
• Don Kuehne • Bill Napier • Brent Kastor
• John Young • Mark Reichardt • Giovanni Migliaccio
• Niels LaCour • Angela Lewis • Mike McSween
• Alexander Stepanov • Kimon Onuma
• Eric Wittner • Clark Morgan
• Louis Hecht • Tim Murtha
• Russ Manning • Paul Seletsky
• Renee Tietjen • Kathy Kalscheur
• Jason Combs • Louise Sabol
• Scott McFarlane • Jeremy Hazel
• Babak Jalalzadeh • Michael Rendler
• Ken Casazza • Theresa Thompson
• Stu Rich • Mohammed Biswas
BIM-GIS Interaction Issues
• What are the business practices where converged
geospatial and AEC information can be maximized?

• What open standard tool sets (IFC-BIM, AECxml, GIS,

CMMS, IWMS, etc.) should be used to perform what
functions?

• Are there requirements for convergence that can only be

supplied by file exchange? What message format(s)
should be used for data exchange?

• What data standards and service interfaces exist or need

to be developed?

• What role do web services play?

 BIM Provides Benefits for
Design and Construction
• Improved design process
• 3-D visualization for owner (static only)
• Coordination between disciplines
• Interference checking
• Facilitates energy efficiency and LEED
• Automated quantity take offs
• 4-D scheduling
• Improved documentation of design intent
• Potentially used for fabrication
Elements in BIM are Created at a
High Level of Detail

This data is required to

convey the information
needed to construct the
facility.

All BIM products export

BIM data to and Industry
Foundation Classes
(IFCs)
 Can We Use BIM As a Spatial
Data Repository?
• File-based
• Proprietary data formats
– Exports to IFC not uniform
• Not easily query-able across multiple facilities
• Not scalable to large number of users
– BIM Server technology limited to design focus
• Limited security
• No clustering, failover, etc.

Not a Viable Solution –

Look at standards-based
geospatial tools
Traditional Scalability Using GIS
World

Country

Region

State / Province
Natural Asset
County
Air / Space
City
Underground
Site
Traditional
Water / Sea GIS Space
Real
Property Asset
Land / Parcel

Facility / Built
Building
System
Traditional Sub-Systems
Space Components
CAD/BIM Space Level
Overlay
Room
Structure
System
Sub-Systems
Space Components
Level
Overlay Room
Linear Structure
Node
Segment
GIS has Advanced to Total Scalability

World

Country

Region

State / Province
Natural Asset
County
Air / Space
City
Underground
Site
Water / Sea
Real
Property Asset
Land / Parcel

Facility / Built
Building
System
Sub-Systems
Space Components
Level
Overlay
Room
Structure
System
Sub-Systems
Space Components
Level
Overlay Room
Linear Structure
Node
Segment
The Analytic Power of GIS
• Spatial analysis and modeling
– Overlay analysis (union, intersect)
– Proximity analysis (buffer, near)
– Surface analysis (hill shade, slope)
– Linear analysis (connectivity, tracing)
– Raster analysis
• Geoprocessing tools
• Relational Database structure
• Enterprise-ready
• Web services
• Integrates with
– EDMS
– CMMS
– CAFM
– IWMS
BIM to GIS
Integration Issues
• BIM is MUCH richer in detail than a
GIS database

• GIS has only recently become fully

3-D

• Design BIM contains all the

information needed to construct a
building, but not to manage it
– Space polygons
– Occupant information
– Asset details (make, model, etc.)
– Equipment maintenance data

• Some of the missing data can be

supplied by COBie

• GIS database and BIM will require

network capabilities to share
information
Fundamental Differences Between BIM
and GIS

BIM (IFC) GIS

• Highly standardized • User defined structures
structure • Parametric – loosely
• Parametric – highly structured
structured • Server based - relational
• File based database
• File based exchange • File and web services for
• Inferior data exchange exchange
between COTS products • Maximum integration
• Small number of users flexibility
• Thick client • Large numbers of users
• Thick and thin clients
Developments in BIM-GIS Integration

•Geographic Elements within IFC

•COBie2 Standard
•CityGML
•Full 3-D GIS/3-D Analysis
•Building and Interior Spaces Data Model
buildingSMART IFC for
GIS Project/IFC 2.4 RC2
IFC 2.4
Spatial & Geographic Elements
• New entity for spatial zones
– the zone can now have own location, shape and functional type as
required e.g. in thermal or lighting zones.
– Both zones, with an without own shapes, can now be assigned to
different levels of the project structure.

• Space boundaries for curved building elements,

such as arc walls, can now be defined by
bounded cylindrical and bounded swept
surfaces.

• A clear differentiation between 1st and 2nd

level space boundaries is made
Spatial & Geographic Elements
IFC 2.4
• External spaces
– separate the external air, earth, water, with the definition of
external space boundaries to identify the gross volume of stories or
buildings.

• New entity for geographic elements placed in the context of a

site.
– Using the enhanced external reference mechanism those
geographic elements, as any other element, can be assigned to
feature catalogs or any other external classification system.

• Parts of the specification for these elements were introduced

into IFC 2.4 as a result of output from AECOO-1.

• These capabilities have not been exercised with OGC GML

(Geographic Markup Language) nor CityGML.
Construction Operations
Building Information
Exchange (COBIE)
Construction Operations Building Information
Exchange (COBie) adds Tabular Information to
BIM
• Capture tabular data needed by the owner as it is created by
– Designers
– Constructors
– Commissioning Agents
• Industry participation
– BIM vendors now export to COBIE
– CMMS/CAFM vendors import COBIE

• Some of the COBie data

belongs in GIS
• GIS Asset tables need to
store a sufficient level of
detail
COBie is Structured to Import Non-
spatial Data into CMMS/CAFM/GIS
COBie2 Limitations

•COBie is focused on FM Handover

•COBie does not include spatial data
CityGML
CityGML Concepts

• Application independent Geospatial

Information Model for virtual 3D city and
landscape models
– Comprises different thematic areas
(buildings, vegetation, water, terrain, traffic
etc.)
– Data model (UML) according to ISO 19100
standards family
– Exchange format results from rule-based
mapping of the UML diagrams to a GML3
application schema
– Adopted OGC standard since 08/2008
 CityGML
• CityGML represents
– 3D geometry, 3D topology, semantics, and appearance
– In 5 discrete scales (Levels of Detail, LOD)

LOD 0 – Regional, landscape model

2.5D Digital terrain model, 3D landmarks

LOD 1 – City / Site model

Prismatic buildings without roof structures

LOD 2 – City / Site model

Simple buildings with detailed roof structures

LOD 3 – City / Site model

Detailed architectural models, landmarks

LOD 4 – Interior Model

“Walkable” architectural models

 The same object may be represented in different LODs

simultaneously
CityGML Strengths
Application Domain Extensions (ADE)
Generics
Appearance

CityObjectGroup

Transportation
CityFurniture

WaterBody
Vegetation
LandUse
Building

Relief

CityGML Core
GML 3.1.1
CityGML Limitations

•Some limited experimentation has taken

place to understand how IFC and
CityGML can work together.
•More work on this point is needed.
•CityGML is focused on visualization
3-D GIS
3-D GIS Analysis Tools
3-D GIS Example Data
3-D GIS Analysis Capabilities
3-D GIS Transportation Networks

Demo

ArcGIS 10
3-D GIS Limitations

•Limited experience converting IFC data

to GIS formats
•New technology with limited use for
facilities
•Complex data structures needed to
support facilities
ESRI Building and
Interior Spaces Data
Model
ESRI Geodatabase Data Models
Standardized Templates for Many Fields
• Address • Historic Preservation
• Agricultural & Archaeology
• Atmospheric • Homeland Security
• Base Map • Hydro
• Biodiversity • IHO
• Carbon Footprint • Land Parcels
• Census-Admin • Local Government
• Boundaries • Marine
• Defense-Intel • National Cadastre
• Energy Utilities • Petroleum
• Environmental • Pipeline
• Forestry • Telecommunications
• Geology • Transportation
• Groundwater • Water Utilities
• Health • Building Interior Space
Simple feature class Geometry Point
Contains M values No
Haul Contains Z values No
Allow Prec-
Field name Data type nulls Default value Domain ision Scale Length
OBJECTID Object ID
SHAPE Geometry Yes
HAULJOIN Long integer No 0
VESSELCODE Long integer No 0
CRUISE Long integer No 0
HAUL Long integer No 0
STATION_ID String No 7
SSTEMP Float No 0 0
BOTTOMTEMP Float No 0 0
EFFORT Float No 0 0
DataSourceID String Yes 50

Relationship class Table

HaulHasFishCatch FishCatch
Type Simple Forward label FishCatch Allow Prec-
CardinalityOne to many Backward label Haul Field name Data type nulls Default value Domain ision Scale Length
Notification None OBJECTID Object ID
Origin feature class Destination table HAULJOIN Long integer No 0
Name Haul NameFishCatch SPECIESCODE Long integer No 0
Primary key HAULJOIN LATINNAME String No 28
Foreign key HAULJOIN COMMONNAME String No 21
No relationship rules defined. WEIGHTCPUE Double No 0 0
NUMBERCPUE Double No 0 0

Relationship class
DataSourceHasHaul Table
DataSource
Type Simple Forward label Haul
Cardinality One to many Backward label DataSource Allow Prec-
NotificationNone Field name Data type nulls Default value Domain ision Scale Length
Origin table Destination feature class OBJECTID Object ID
Name DataSource NameHaul DESC_ String Yes 35
Primary keyDataSourceID SOURCE String Yes 35
Foreign key DataSourceID CONTACT String Yes 20
No relationship rules defined. PREC String Yes 20
CREATE_DATE Long integer Yes 0
LAST_UPDATED Long integer Yes 0
DataSourceID String Yes 50
 ESRI’s Building Interior Space Data
Model (BISDM) for GIS
A user community effort

• Started in summer 2007

• Build template to serve many
uses cases and compatible
technologies
• Real-world project tested
• Support property, building, and
asset objects
• Models, supporting
documentation, data loading
tools, and sample viewers at
www.esri.com/datamodels
BISDM Supports Industry Standards

• Defining and measuring building space

– BOMA and FICM

• Classifying building space -- form, function, assets

– Open Standards Consortium for Real Estate (OSCRE)
– OmniClasstm

• Building information models (BIM)

– National BIM Standard
– Industry Foundation Classes (IFC)

• Building object information exchange  

– Construction Operations Building Information Exchange (COBIE)
BISDM Asset Data Feature
Classes

BISDM 2.0
Mimics the
structure
of IFCs
 “Split” Data Model to Interface with External
Database (or Future BIM Server)
vElevator

INNER JOIN ON 0..1

Elevator
“Is A Type Of” Relationship ConveyanceArea.AssetID =
(PK)ELEVATORID (guid)
Elevator.ELEVATORID
1 REFERENCE
FIREEXIT
ConveyanceArea CLEARWIDTH
CLEARDEPTH
(PK/FK)ASSETID (guid) CLEARHEIGHT
ALIAS
(FK)ENTITYID (guid) vEscalator
DESCRIPTION
0..1
Escalator
CAPACITY INNER JOIN ON
CONVEYANCEUSE ConveyanceArea.AssetID = (PK)ESCALATORID (guid)
CONVEYANCETYPE Escalator.ESCALATORID …
DOORQTY …
ADACOMPLIANT
FLOORSSERVED
KEYACCESFLOORS

vStairWell
0..1 Stairwell
BIM
INNER JOIN ON
ConveyanceArea.AssetID = (PK)STAIRWELLID Data
Stairwell.STAIRWELLID REFERENCE
NUMBEROFRISER
NUMBEROFTREADS
RISERHEIGHT
TREADLENGTH
NOSINGLENGTH
WALKINGLINEOFFSET
TREADLENGTHATOFFSET
TREADLENGTHATINNERSIDE
HEADROOM
WAISTTHICKNESS

vMovingWalkway
0..1
MovingWalkway
INNER JOIN ON
ConveyanceArea.AssetID = (PK)MOVINGWALKWAYID
MovingWalkway.MOVINGWALKWAYID …
…
 Potential Integrated
CADD/BIM/GIS Data Workflow
CMMS
COBIE CAFM/IWMS
Sp
BIM Data a t ia
lD
a ta Asset
E 1 3 , 0 8 9 ,2 5 0 E 1 3 , 0 8 9 ,5 0 0 E 1 3 , 0 8 9 ,7 5 0 E 1 3 , 0 9 0 ,0 0 0 E 1 3 , 0 9 0 ,2 5 0 E 1 3 , 0 9 0 ,5 0 0 E 1 3 , 0 9 0 ,7 5 0 E 1 3 , 0 9 1 ,0 0 0

8 3 5 .1
8 3 6 .5
8 2 7 .2 5 1
8 25

8 2 6 .8 8 2 8 .1
8 3 4 .3 8 2 7 .2 8 3 7 .1 8 3 5 .4
8 2 8 .8 8 2 8 .2 83
8 3 0 .3 8 2 9 .6 5
8 3 3 .4
8 3 5 .1 8 2 8 .3
8 2 9 .2 8 3 7 .1
83

8 3 5.2 8 2 9 .6
0

8 3 6 .2 8 2 9.8
8 4 0 .8 8 3 6 .7 83
8 2 9 .8 0
830 8 3 0.2 8 3 4 .2
8 2 9 .8 8 2 9.6
8 3 6 .5 8 3 5 .5
825

8 3 5 .7 RE
8 40

8 25

8 2 8 .4
8 2 8 .5
8 3 4 .8 D 82
83

8 2 8 .3 5
0

K E LLO G G C EN TE R 83 0 8 2 7 .7 8 2 9 .4
8 2 7.7
825

5 5
8 2 9 .3
CE
83 5

83 5

8 3 5 .7 8 2 7 .5 8 3 5 .4
8 3 4 .5 8 2 8 .3 8 3 4 .5 8
30 DA
R
835

8 3 5 .1 8 3 3 .6 S P A R TA N
8 3 7 .4 S TA TU E N 4 4 8 ,7 5 0

TBR ID G E
8 3 5 .7 8 3 5 .5 FO O 8 2 8 .4 8 2 9 .3
8 2 8 .2
8 3 2 .2 R IV
8 3 4 .7 8 3 5 .8 ER

8 2 7 .5 8 2 8 .4
8 2 8 .5 8 3 3 .5 8 3 2 .3
8 3 0 .3 RE D
8 3 4 .5
8 3 4 .5 8 3 1 .4
8 3 4 .4 8 27 .6
8 3 5 .8
8 3 5 .4 835 8 3 3 .7
8 3 2 .3
8 3 2.3 8 3 4 .2 CE
DA
8 2 9.6 8 2 9 .4 R 8 3 1 .6
8 3 6 .5 8 3 0 .3 8 3 3.3
8 3 5 .6 8 3 2 .6
8 3 2.7 8 3 3 .4 J EN IS O N G Y M NA S IU M 8 3 2 .6
8 3 3 .4 8 3 2 .8 8 3 1 .9
A ND 8 3 1 .2
KE LL O G G P A R KIN G 8 3 3 .4 8 3 2 .4
RO AD

8 3 0 .2
8 3 6 .3 LO T 66 8 3 2 .7 8 3 2 .6
8 2 9 .4
P A RK I N G L O T F I EL D H O U S E 8 3 2 .2
8 3 2 .8 8 3 2 .4 8 3 1 .2 RO
64 8 3 5 .8 56 8 3 2 .4 AD
8 3 3 .7 8 3 2 .8
8 3 2 .5 8 3 2.3
8 3 5 .6 8 3 0 .8
8 3 0 .3 8 3 2 .4 8 3 1 .3 8 3 1 .2

8 3 1 .1
11 7 8 3 2 .4 8 3 2 .4
8 3 5 .2 8 3 1 .1 8 3 N 4 4 8 ,5 0 0
8 2 9 .4 8 3 1.7
8 3 2.5
8 3 2 .9 8 3 0.6
T

8 3 3 .8
EE

8 2 5 .6 8 3 0 .6 8 3 0 .7
S TR

U /C 8 3 0 .4 8 3 3 .8 8 3 1 .3 8 3 2 .3 8 3 1 .3
8 3 6 .1 8 3 3 .5 8 3 1 .4
AD
RO

8 3 5 .5 8 3 2 .2

Management
8 3 5 .5 8 3 5 .5 8 3 2 .4 8 3 0 .6
8 3 3 .8 8 3 1.7 P AR A DE F IE LD
8 35

8 3 2 .4 8 3 1 .2
8 2 9 .3
8 3 1 .5
8 3 1 .8
8 3 5 .5 8 3 1 .7
8 3 2 .3 8 3 1 .6
8 3 4 .7 8 3 1 .7
8 3 1 .6 8 3 3 .8
H A R R IS O N

8 3 0.3 8 3 3 .6 8 3 4 .7
8 2 8 .3 8 3 2 .5
ER

8 3 2 .7 8 3 2 .5
R IV

8 3 2 .8 8 3 3 .4 8 3 4 .7 8 3 2 .5
8 3 3 .6
8 3 4 .7 8 3 5 .4 8 3 2 .4
8 3 2 .5
8 2 7 .6 8 3 2 .7
8 3 5 .6 8 3 3 .2 8 3 3 .2
8 3 1 .5 8 3 5 .1
8 3 1 .4 8 3 2 .5
8 3 5 .6
83

8 3 3 .3 8 3 4 .4
5

8 3 2 .4
25

8 3 4 .7 8 3 3 .4
8

8 3 2 .2 830 8 3 0 .2 8 3 2 .6 8 3 2 .4
8 3 2 .4 8 3 2 .5 8 3 5 .4 8 3 5 .5
8 3 1.5 8 3 3 .7
R

8 3 5 .4
D A

825
CE

J E N IS O N
830 835
8 3 1 .6 P A R K IN G LO T 8 3 3 .4 I NT RA M U R A L P A R K IN G
8 3 1 .3 67 8 3 3 .5
8 3 3 .5
LO T 62
D
RE
UT

N 4 4 8 ,2 5 0
8 3 5 .3
S TN

Spat
E
CH

83
5
P A RK IN G 8 3 3 .5 8 3 4 .7
TO LL B O O T H 8 3 4 .8
50 8

8 3 7 .6 835
835

8 3 5 .8
8 3 6 .5 8 3 5 .4
8 4 4 .6 8 4 3 .4 D E M O NS TR A TIO N H A LL
8 4 2 .5 8 3 7 .7 8 3 7 .4 835 57 8 3 5.5
8 3 6 .7
84

8 4 1 .4
0

8 3 5 .7

8 3 6 .3
8 3 6 .3
8 4 2 .3 DE 8 3 5 .6
8 4 2 .5 8 4 2 .1 8 4 2 .3
M O 8 3 5 .5
8 3 6 .2
8 4 2 .8 NS
ZOO TR A
L AM A T IO
KA N
8 4 2 .2 8 3 6.7
8 3 5 .4
8 4 3 .5
8 3 7 .2 8 3 7 .3
HA

ia
840 LL 8 3 5 .9
8 4 3 .3

8 3 7 .7 N 4 4 8 ,0 0 0
8 3 5 .3
8 3 8 .8 RO
8 3 9 .2 A D
8 4 4.6

8 4 5 .5 8 3 6 .4

l Da
8 4 5 .3

8 4 5 .6 8 4 2 .7 845
8 4 3 .7 8 4 1 .3 8 4 1 .7

8 4 8 .3
8 4 0 .4

8 4 7 .4 8 4 7 .3
8 4 8 .8
8 4 4 .6 8 4 0 .6 8 4 8 .3 I NT RA M U R A L -RE C R EA TIV E

84
5 S P O RT S - W ES T
8 4 7 .6
15 1
845
8 5 7 .6 8 4 7.8
8 4 8 .3
855
D IR T P I LES 8 3 9 .7
8 50
8 4 5 .4 8 3 9 .8
R O AD

8 5 3 .1 8 4 6.7
8 50 8 40
8 4 6 .8 8 40 8 4 3 .3
8 4 7 .2
8 4 3 .6 N 4 4 7 ,7 5 0
8 4 4 .6

ta
8 3 9 .3 8 4 0 .4
8 4 0 .8 8 3 8 .5
8 4 3 .6
8 4 3 .5
8 4 1 .8

8 4 6 .6
8 4 1 .3 8 4 1 .8
8 4 3 .7
8 4 6 .5
M UN N A RE N A
B R ES LIN
B IR C H

S TU D EN T
8 4 6.5 8 4 6 .5 8 4 4 .3
8 4 5 .4 59 8 4 6 .6 PO O L

E V E N TS C E N TE R
8 4 1 .2 8 4 3 .6
8 4 0 .4
8 4 4 .3
8 4 6 .7
84
5

8 4 2 .7 845
8 4 1 .9 8 4 5 .4
8 3 2 .2 8 4 3 .6

8 4 6 .7
8 4 1 .8
8 4 6 .6
8 4 6 .7
8 4 3 .3
85 0

8 4 2.3
TR A C K
845
84

8 4 4 .7 8 4 6 .7 N 4 4 7 ,5 0 0
5

8 4 5 .7
8 4 4 .8
8 4 4 .5
8 4 2 .7 8 4 6 .7 8 4 6 .3
8 4 6 .6
84 5

850

T IT LE D W N. BY
R E VI S IO N S
N D IG ITA L D A TA B A S E A P P V D . BY

M A P P IN G D A TE
8 -89
G E O G R A P H IC 5 0' 0' 50' 1 0 0' 15 0 ' S C AL E
IN F O R M A TIO N S C A LE IN F E ET M IC H IG A N S TA T E U N I V ER S ITY 1 "= 5 0 '
D W G. N O .
W O O LP E R T
S E R V IC E S C O N TO U R IN T E R VA L : 1 FO O T P H Y S IC A L P LA N T D I V I S IO N M SU 2 C
E N G IN E E RI N G S ER V I C E S D E P A R T M E N T F IL E NO .

CADD Data GIS BIM

Tabular Data
Repository Repository
Spatial Data
GIS Data
ESRI BISDM Limitations

•Limited experience, especially with 3-D

•BIMServer for FM does not exist
BIM-GIS Committee
Direction
BIM-GIS Use Cases -
Planning/Design/Construction
• Site Selection/Location
planning
• Site Suitability/Alternatives
analysis
• Site
circulation/parking/vehicle
routing
• Permitting/zoning review
• Visualization
– Building Skins
– Textures
• View Shed analysis
• Drainage analysis
• Erosion control analysis
• Height analysis
• Airspace encroachments
• Shadow analysis (solar
potential)
• Security planning
• Evacuation routing
• Temporal Analysis
– Historical
– Existing
– Future
• Economic Analysis
• Demographics
• Soil Conditions
• Transportation
• Source locations of building
products (LEED analysis)
• Emergency
Management/Security
• Total Cost of
Ownership/Lifecycle
Analysis
BIM-GIS Use Cases - Operation
• GIS-based Facilities management (maintain 3-D models)
• MEP/data network routing/analysis
• Space Management/optimization
• Move management
• Asset management
• Public Safety
– Security
– Fire protection
– Evacuation routing
– Hazardous materials storage
• Way-Finding
– Proximity/routing
– ADA compliant routes
• Interior Space analyses
– Areas (organizational, operations, leasing, etc.)
– Elevation
– Volumes
• Energy Management
– Real-time sensor display
– Environmental contaminant analysis
GIS-BIM Use Cases –
Renovation/Repurpose
• Existing As-built architectural/structural models
• Existing As-built MEP/data networks
• Security planning
• Evacuation routing
Next Steps

•Define detailed use cases? IDMs?

•Define exchange standards?
•Define web services requirements for
BIM Server technology?
Discussion