AB1796 Advanced Techniques For Building Data in Revit - Presentation

Advanced Techniques for Managing Building Data
in Autodesk Revit
Mario Guttman
Senior Design Technology Specialist CASE
Twitter: https://twitter.com/MarioGuttman
Class summary
The collection and management of building data, including the requirements for rooms,
equipment, and other needs, as it evolves from early design through construction
documentation and as a basis for facility management, can be enhanced through advanced
techniques in Autodesk Revit software.
This includes linking to an external data source, automating the creation of areas and
rooms, creating room data sheets, and other graphic and non-graphic processes that
complement BIM. This class covers basic database theory, the structure of objects and their
relation to data management, and Revit techniques for implementing this general theory in
actual projects.
We also discuss third-party software and customizations, and how they are used to further
advance these processes. The class goes beyond learning Revit commands and looks at
the underlying information requirements of emerging integration in project delivery.
Advanced Techniques for Managing Building Data in Autodesk Revit
Key learning objectives

At the end of this class, you will be able to:
Understand how building data is represented in objects and databases.
Evaluate computer system architectures and software options.

Use Revit to study conceptual design and building massing.
Create room data sheets in Revit and in an external database.
The presentation also includes sections on:

Supplemental Material.
Example Project.
Introduction to Building Data
BUILDING DATA
The Problem
Kinds of Project Information:
Building Data: rooms, activities,
ownership, furniture, equipment, etc.
Project Data: team makeup, project
budget, schedule, etc.
(We are not going to talk about this.)
Needs for Managing Data:

Accuracy.
Validation.
THE PROBLEM
BUILDING DATA
SOURCE DATA
DATABASE SYSTEM
DELIVERABLES
CLIENT
REQUIREMENTS
PRE-DESIGN
INTERVIEWS
DESIGN TEAM
EXPERTISE
BIM
DRAWINGS
REPORTS
CONSTRUCTION
SYNCHRONIZE
FA C I L I T Y
M AN AG EM E N T
AGENCY
REQUIREMENTS
DESIGN
DECISIONS
DATABASE
MODELS / DATA
INFORMATION FLOW THROUGH A DATABASE SYSTEM
BUILDING DATA
Information Flow
Owners Requirements
Designed for readability.
Complex data structure
Paper or raster mode.
INFORMATION FLOW
BUILDING DATA
Design Team Requirements

Relational data.
Software use.
Reporting.
BUILDING DATA
First, we want to understand our data,

and define objectives for using it.
Then, we can implement software to

achieve those objectives.
General Principles of Objects and Databases
DATA PRINCIPLES
Objects and How Revit Uses Them

Object-oriented programming (OOP).
Things in Revit.
All objects have:
Methods: Behavior (wall hosting.)
Properties: Data (dimension; manufacturer.)

Ole-Johan Dahl and Kristen Nygaard developed
Simula in the 1960s at the Norwegian Computing
Center in Oslo. (Wikipedia)
OBJECTS AND HOW REVIT USES THEM
DATA PRINCIPLES
Object Inheritance
Objects derive
from parent object.
DATA
ACCUMULATES
W ITH EACH
GENERATION
OBJECT
CHILD
Children inherit
properties.
ELEMENTS
TEXT
ELEMENT ID
CHILD
FAMILY
TEMPLATES
FURNITURE
FAMILIES
PARENT CHILD OBJECTS

HOST TYPE
CHILD
OMNICLASS
DATA PRINCIPLES
Object Types
(Classes)
FURNITURE
Families are one

kind of thing.
Types are different
kinds of the family.
Instances are
placements of a
specific type.
DATA
FURTHER
ACCUMULATES
TO TYPES
CHILD
TABLE
FAMILY
FAMILY
TYPES
MODEL
CHILD
SIZE
36 x 36
72 x 36
FAMILY
INSTANCES
CHILD
MATERIAL
36 x 36
36 x 36
72 x 36
72 x 36
FAMILIES TYPES INSTANCES

DATA PRINCIPLES
MODEL ENVIRONMENT
Revit Parameters
(object properties with data in them)
Shared Parameter: Same name is used in other models.

(Not-shared) Parameter: Name is used only in this model.
FAMILY EDITOR
Project Parameter: Parameter applies to all families.

Family Parameter: Parameter is part of the family.
THESE ARE INDEPENDENT OF ONE ANOTHER

THEY ARE NOT RELEVANT TO BUILDING DATA
DATA PRINCIPLES
FAMILY EDITOR
Built-in Parameter
(Family-level Parameter)
TABLE
FAMILY
FAMILY
TYPES
36 x 36
72 x 36
36 x 36
36 x 36
FAMILY
INSTANCES
72 x 36
72 x 36
DATA PRINCIPLES
FAMILY EDITOR
Type Parameter
MODEL ENVIRONMENT
TABLE
FAMILY
FAMILY
TYPES
36 x 36
72 x 36
36 x 36
36 x 36
FAMILY
INSTANCES
72 x 36
72 x 36
DATA PRINCIPLES
FAMILY EDITOR
Instance Parameter
MODEL ENVIRONMENT
TABLE
FAMILY
FAMILY
TYPES
36 x 36
72 x 36
36 x 36
36 x 36
FAMILY
INSTANCES
72 x 36
72 x 36
DATA PRINCIPLES
Data equivalence of Types and Instance Parameters

DOOR
FAMILY
ONE DOOR TYPE

INSTANCE PARAMATER
Door Color
Door Color: RED
Door Color: BLUE
TWO DOOR TYPES

DOOR TYPES
TYPE A
RED
TYPE B
BLUE
DOOR TYPE A
DOOR TYPE B
DOOR SCHEDULE
DOOR ID
COLOR
100
RED
200
BLUE
DATA PRINCIPLES
Use of Schedule Keys with Instance Parameters

DOOR
FAMILY
ONE DOOR TYPE

INSTANCE PARAMATER
Door Color
PATIENT ROOM
OFFICE
SCHEDULE KEY
DOOR STYLE
DOOR COLOR
PATIENT ROOMS
RED
OFFICES
BLUE
DOOR SCHEDULE
DOOR ID
COLOR
100
RED
200
BLUE
DATA PRINCIPLES
Basics of Relational Databases

Tables and Relationships
RELATIONSHIP
TABLE
TABLE
BASICS OF RELATIONAL DATABASES
DATA PRINCIPLES
Tables
Rows
COLUMNS (FIELDS)
Columns
ROOM ID
ROW S
(RECORDS)
TYPE
FLOOR
AREA
10101
OFFICE - LARGE
FLOOR 01
1000
10101A
OFFICE - MEDIIUM
FLOOR 01
800
10102
OFFICE - SMALL
FLOOR 01
400
10103
CONFERENCE
FLOOR 01
640
20110
BREAK ROOM
FLOOR 02
820
20111
COPY AREA
FLOOR 02
220
20123
STORAGE
FLOOR 02
100
20843
CLASSROOM 1
FLOOR 02
740
30102
CLASSROOM 2
FLOOR 03
820
30104
CLASSROOM 3
FLOOR 03
1020
30105
STUDY AREA
FLOOR 03
600
ROOMS TABLE
DATA PRINCIPLES
Primary Key Field

Uniquely identifies a record.
It must be:
PRIMARY KEY
ROOM ID
TYPE
FLOOR
AREA
Not Null
10101
OFFICE - LARGE
FLOOR 01
1000
10101A
OFFICE - MEDIIUM
FLOOR 01
800
Unique
10102
OFFICE - SMALL
FLOOR 01
400
10103
CONFERENCE
FLOOR 01
640
20110
BREAK ROOM
FLOOR 02
820
20111
COPY AREA
FLOOR 02
220
20123
STORAGE
FLOOR 02
100
20843
CLASSROOM 1
FLOOR 02
740
30102
CLASSROOM 2
FLOOR 03
820
30104
CLASSROOM 3
FLOOR 03
1020
30105
STUDY AREA
FLOOR 03
600
ROOMS TABLE
DATA PRINCIPLES
Foreign Key Field

FLOOR ID
Points to the Primary Key of

another table.
FOREIGN KEY
It may be Null.
AREA
FLOOR 01
23100
FLOOR 02
32800
FLOOR 03
32400
FLOORS TABLE
ROOM ID
TYPE
FLOOR
AREA
10101
OFFICE - LARGE
FLOOR 01
1000
10101A
OFFICE - MEDIIUM
FLOOR 01
800
10102
OFFICE - SMALL
10103
CONFERENCE
FLOOR 01
640
20110
BREAK ROOM
20111
COPY AREA
FLOOR 02
220
20123
STORAGE
FLOOR 02
100
20843
CLASSROOM 1
30102
CLASSROOM 2
FLOOR 03
820
30104
CLASSROOM 3
FLOOR 03
1020
30105
STUDY AREA
FLOOR 03
600
ROOMS TABLE
DATA PRINCIPLES
One to Many Relationship

FLOOR ID
Defined by a Foreign Key.
A value can occur:

Once on the
one side.
Many times on
the many side.
ROOM ID
TYPE
FLOOR
AREA
FLOOR 01
23100
FLOOR 02
32800
FLOOR 03
32400
FLOORS TABLE
AREA
10101
OFFICE - LARGE
FLOOR 01
1000
10101A
OFFICE - MEDIIUM
FLOOR 01
800
10102
OFFICE - SMALL
FLOOR 01
400
10103
CONFERENCE
FLOOR 01
640
20110
BREAK ROOM
FLOOR 02
820
20111
COPY AREA
FLOOR 02
220
20123
STORAGE
FLOOR 02
100
20843
CLASSROOM 1
FLOOR 02
740
30102
CLASSROOM 2
FLOOR 03
820
30104
CLASSROOM 3
FLOOR 03
1020
30105
STUDY AREA
FLOOR 03
600
ROOMS TABLE
DATA PRINCIPLES
Referential Integrity
FLOOR ID
The one side must exist

before the many side can be
used
Changes can
cascade from the
one to the many.
Deletions can
cascade but may
delete the whole
record.
ROOM ID
TYPE
FLOOR
AREA
FLOOR 01
23100
FLOOR 02
32800
FLOOR 03
32400
FLOORS TABLE
AREA
10101
OFFICE - LARGE
FLOOR 01
1000
10101A
OFFICE - MEDIIUM
FLOOR 01
800
10102
OFFICE - SMALL
FLOOR 01
400
10103
CONFERENCE
FLOOR 01
640
20110
BREAK ROOM
FLOOR 04
820
20111
COPY AREA
FLOOR 02
220
20123
STORAGE
FLOOR 02
100
20843
CLASSROOM 1
FLOOR 02
740
30102
CLASSROOM 2
FLOOR 03
820
30104
CLASSROOM 3
FLOOR 03
1020
30105
STUDY AREA
FLOOR 03
600
ROOMS TABLE
THIS VALUE
FLOOR 04
CANNOT BE
ADDED SINCE
THERE IS NO
SUCH VALUE
IN IN THE
FLOORS TABLE
DATA PRINCIPLES
Normalizing Data
A table is Not Normalized if it has redundant data.
NAME
OFFICE
ADDRESS
ADAM SMITH
ACME CONSTRUCTION
123 NORTH MAIN ST., CULVER CITY, CA 94306
BETTY JONES
ACME CONSTRUCTION
CLARK KENT
BEST ENGINEERING
2100 FLAGSHIP WY., SACRAMENTO, CA 94563
STEVE WONG
BEST ENGINEERING
MARY STAFFORD
BEST ENGINEERING
THIS DATA IS
REDUNDANT
CONTACT TABLE WITH OFFICE ADDRESSES
The data can be Normalized by using two tables.

Name
OFFICE
ADAM SMITH
ACME CONSTRUCTION
BETTY JONES
ACME CONSTRUCTION
CLARK KENT
BEST ENGINEERING
STEVE WONG
BEST ENGINEERING
MARY STAFFORD
BEST ENGINEERING
CONTACT TABLE
OFFICE
ADDRESS
ACME CONSTRUCTION
BEST ENGINEERING
OFFICE TABLE
DATA PRINCIPLES
Flattening Data
Normalized data can be difficult to use in Revit.
Name
THIS DATA IS DIFFICULT TO USE W HEN

W ORKING W ITH THE CONTACT TABLE
OFFICE
ADAM SMITH
ACME CONSTRUCTION
BETTY JONES
ACME CONSTRUCTION
CLARK KENT
BEST ENGINEERING
STEVE WONG
BEST ENGINEERING
MARY STAFFORD
BEST ENGINEERING
OFFICE
ADDRESS
ACME CONSTRUCTION
BEST ENGINEERING
CONTACT TABLE
OFFICE TABLE
The data can be Flattened by compressing it into a single table.

NAME
OFFICE
ADDRESS
ADAM SMITH
ACME CONSTRUCTION
BETTY JONES
ACME CONSTRUCTION
CLARK KENT
BEST ENGINEERING
STEVE WONG
BEST ENGINEERING
MARY STAFFORD
BEST ENGINEERING
CONTACT TABLE WITH OFFICE ADDRESSES

THIS DATA IS
MORE EASILY
ACCESSIBLE
DATA PRINCIPLES
Revit Objects and Relational Data

Mapping Revit Objects to Database Tables
OBJECT DATABASE MAPPING
OBJECT INSTANCES
OBJECT TYPES
REVIT
DATABASE
REVIT
DATABASE
AREA
OBJECTS
LINK
AREA
TABLE
FURNITURE
OBJECTS
FURNITURE
INSTANCES
TABLE
ROOM
OBJECTS
LINK
ROOM
TABLE
FURNITURE
OBJECTS
LINK
FURNITURE
TABLE
LINK
LINK
OBJECT
TYPE
RELATED
TABLE
FURNITURE
TYPES
FURNITURE
TYPES
TABLE
LINK
REVIT OBJECTS AND RELATIONAL DATA
DATA PRINCIPLES
Mapping Revit Parameters to Database Fields

PARAMETERS DATABASE MAPPING
OBJECT INSTANCES
REVIT
OBJECTS
DATABASE
TABLE
OBJECT
RECORD
KEY PARAMETER
LINK
PARAMETER - 1
PARAMETER - 2
PARAMETER - 3
FIELD - 1
OTHER
VALUES
OBJECT
KEY PARAMETER
PARAMETER - 3
FIELD - 2
FIELD - 3
RECORD
LINK
PARAMETER - 1
PARAMETER - 2
KEY FIELD
KEY FIELD
FIELD - 1
OTHER
VALUES
FIELD - 2
FIELD - 3
REVIT OBJECTS AND RELATIONAL DATA
DATA PRINCIPLES
Mapping Revit Parameters to Database Fields

TYPE PARAMETERS DATABASE MAPPING
TYPE PARAMETERS DATABASE MAPPING
OBJECT TYPES
OBJECT TYPES
REVIT
OBJECTS
DATABASE
PRIMARY TABLE
REVIT
OBJECTS
DATABASE
PRIMARY TABLE
OBJECT
RECORD
OBJECT
RECORD
KEY PARAMETER
LINK
KEY FIELD
KEY PARAMETER
FOREIGN KEY
DATABASE
PRIMARY TABLE
PARAMETER - 1
PARAMETER - 2
ID KEY FIELD
TYPE FIELD
TYPE PARAMETER
LINK
RECORD
LINK
OTHER
VALUES
KEY FIELD
FOREIGN
KEY
RECORD
FIELD - 1
PARAMETER - 1
FIELD - 2
PARAMETER - 2
DATABASE
RELATED TABLE
KEY FIELD
OTHER
VALUES
FIELD - 1
FIELD - 2
System Architecture and Software Options
SOFTWARE OPTIONS
System Architecture
Single User
Option 1: Revit Add-in only.
Option 2: Windows application.
(option)
LOCAL
DATA
Advantages:
Simple; easy to use.
REVIT
IMAGES
Disadvantages:
LOCAL
REVIT
MODEL
DEDICATED
WINDOWS
APPLICATION
USER
Single-user.
ADD-IN
SYSTEM ARCHITECTURE
SOFTWARE OPTIONS
Multi-User LAN / WAN
USER
WIDE-AREA NETWORK
LOCAL-AREA NETWORK
USER
Advantages:
Multi-user.
Mature technology.
Disadvantages:
Only inside Firewall
IMAGES
SHARED
DATA
FI LES
CLI ENT
SERVER
USER
(option)
SHARED
REVIT
MODEL
REVI T
W ORKSHARI NG
LOCAL
REVIT
MODEL
REVIT
DEDICATED
WINDOWS
APPLICATION
ADD-IN
USER
SYSTEM ARCHITECTURE
SOFTWARE OPTIONS
HOST
SERVER
Multi-user Internet
( Web Cloud )
SHARED
DATA
Advantages:
Collaboration.
Centralized
administration.
Disadvantages:
Complex.
Less functional.
SHARED
MODEL
BUSINESS
APPLICATION
WEB
SERVICE
INTERNET
APPLICATION
LOCAL
REVIT
MODEL
INTERNET /
WEB / CLOUD
RICH
APPLICATION
REVIT
ADD-IN
BROWSER
USER
USER
USER
USER
SYSTEM ARCHITECTURE
SOFTWARE OPTIONS
USER
WIDE-AREA NETWORK
HOST
LOCAL-AREA NETWORK
SERVER
USER
IMAGES
USER
FI LES
SHARED
DATA
CLI ENT
SERVER
SHARED
REVIT
MODEL
DATA
SHARED
IFC
MODEL
BUSINESS
APPLICATION
REVI T
W ORKSHARI NG
WEB
SERVICE
(option)
LOCAL
REVIT
MODEL
LOCAL
DATA
INTERNET
APPLICATION
RICH
APPLICATION
REVIT
IMAGES
DEDICATED
WINDOWS
APPLICATION
ADD-IN
INTERNET /
WEB / CLOUD
BROWSER
USER
USER
SYSTEM ARCHITECTURE OPTIONS

USER
USER
SOFTWARE OPTIONS
Ideate - BIMLink
Link Microsoft Excel to Revit
Inexpensive, Wide Adoption

Features:
No training required
FlexLM licensing
Access to Revit Data beyond
Schedules
Element Creation
Standards Management
http://www.ideatebimlink.com/
Images copied from Vendor Website.
IDEATE BIMLINK
SOFTWARE OPTIONS
USER
WIDE-AREA NETWORK
LOCAL-AREA NETWORK
USER
SHARED
REVIT
MODEL
EXCEL
USER
REVI T
W ORKSHARI NG
LOCAL
REVIT
MODEL
EXCEL
REVIT
BIM LINK
ADD-IN
USER
SYSTEM ARCHITECTURE IDEATE BIM LINK

SOFTWARE OPTIONS
WhiteFeet Tools for Revit

Link Database to Revit
Hobbyist Unlimited Free Trial

Database Options:
Microsoft Access.
SQL Server.
MySQL.
Room Data Sheets

In Revit.
Database report.
www.WhiteFeetTools.com
WHITEFEET TOOLS FOR REVIT
SOFTWARE OPTIONS
WIDE-AREA NETWORK
USER
LOCAL-AREA NETWORK
USER
REPORT
WRITER
USER
ACCESS
DATABASE
SQL
SERVER
OR
MYSQL
SHARED
REVIT
MODEL
CLI ENT
SERVER
REVI T
W ORKSHARI NG
SHARED
OPTI ON
LOCAL
REVIT
MODEL
REVIT
SERVICE
VIEWS
LOCAL
OPTI ON
ROOM
VI EW S
DATABASE
LINK
ADD-IN
ROOM DATA
SHEET
ADD-IN
USER
SYSTEM ARCHITECTURE WHITEFEET REVIT DBLINK

SOFTWARE OPTIONS
Trelligence Affinity
Stand-alone Application
Proprietary Graphics
Proprietary Data Format
Link to Revit/Vasari,
ArchiCAD, AECOsim,
SketchUp, and IES
Features:
Architectural Programming
Early Design
Design Validation
BIM Integration
Sustainability Analysis
http://www.trelligence.com/
TRELLIGENCE AFFINITY
SOFTWARE OPTIONS
USER
USER
USER
WIDE-AREA NETWORK
LOCAL-AREA NETWORK
AFFINITY
MULTI USER
OPTION
SHARED
REVIT
MODEL
REVI T
W ORKSHARI NG
AFFINITY
WINDOWS
APPLICATION
LOCAL
REVIT
MODEL
REVIT
AFFINITY
DATABASE
ADD-IN
AFFINITY
GRAPHICS
USER
SYSTEM ARCHITECTURE AFFINITY

SOFTWARE OPTIONS
CodeBook
CAD/BIM linked to Database
CAD/BIM Options: Revit, AutoCAD,
Navisworks, MicroStation and ArchiCAD.
Database Options: Access, SQL Server
Strong in Healthcare market, especially in UK.
Features:
Boosts economic viability
Links everything to the brief
Validates design changes
Delivers results
http://www.codebookinternational.com/
CODEBOOK
SOFTWARE OPTIONS
WIDE-AREA NETWORK
USER
LOCAL-AREA NETWORK
USER
USER
ACCESS
DATABASE
CLI ENT
SERVER
REVI T
W ORKSHARI NG
LOCAL
REVIT
MODEL
SQL
SERVER
OPTI ON
ACCESS
DATABASE
SERVICE
SQL
SERVER
SHARED
REVIT
MODEL
ACCESS
OPTI ON
CODEBOOK
WINDOWS
APPLICATION
REVIT
CODEBOOK
ADD-IN
USER
SYSTEM ARCHITECTURE CODEBOOK

CODEBOOK
MOBI LE
HANDHELD
DEVICES
SOFTWARE OPTIONS
Nosyko dRofus
Cloud Solution based on Open Standards
Revit, IFC, ArchiCAD.
Historically strong in European Healthcare.
Government and industry collaboration.
Now in United States and other markets.
Features:
Logs: What changes have been made.
Report generator, Excel and Word.
Room Data Sheets.
Central server; work from any location.
Just PC and internet connection.
Standardized solutions.
Higher quality and control of data
Controlling programmed requirements.
Validate designed solution.
http://drofus.com/en/index.html
NOSYKO - DROFUS
SOFTWARE OPTIONS
USER
USER
USER
WIDE-AREA NETWORK
HOST
LOCAL-AREA NETWORK
SERVER
SHARED
REVIT
MODEL
POSTGRE
DATABASE
SHARED
IFC
MODEL
REMOTE
APPLICATION
REVI T
W ORKSHARI NG
APACHE WEB
SERVICE
LOCAL
REVIT
MODEL
LOCAL RICH
INTERNET
APPLICATION
REVIT
IFC
GRAPHICS
WEB
ADD-IN
USER
USER
SYSTEM ARCHITECTURE DROFUS

USER
USER
SOFTWARE OPTIONS
Onuma Planning System

Services and Middleware
ArchiCAD, Revit, SketchUp, and GIS.
Open Standards: IFC and OGC.
Strong in Government and Education

Wide community involvement.
Features:
Predictive planning - early project stages.
Programming requirements for a project.
Management of as-built data for facilities.
Creates BIM with no BIM training required.
Many BIMs in a relational online database.
Multi Site, Multi Building.
Floors, Spaces, Furniture & Equipment.
Multi user collaboration on projects.
http://www.onuma.com/
ONUMA PLANNING SYSTEM
SOFTWARE OPTIONS
USER
USER
USER
WIDE-AREA NETWORK
HOST
LOCAL-AREA NETWORK
SERVER
SHARED
REVIT
MODEL
SHARED
IFC
MODEL
DATA
REMOTE
APPLICATION
REVI T
W ORKSHARI NG
WEB
SERVICE
LOCAL
REVIT
MODEL
WEB
BROWSER
APPLICATION
REVIT
PROPRIETARY
GRAPHICS
WEB
ADD-IN
USER
USER
USER
SYSTEM ARCHITECTURE ONUMA PLANNING SYSTEM

USER
Conceptual Design and Building Massing
CONCEPTUAL DESIGN PROCESS
Linking Revit to a Database

WhiteFeet RevitDbLink
Formalizing the Space Program

Interpreting a Space Program
DOCUMENT:
READABLE FORMAT
UNSTRUCTURED DATA
CLIENT REQUIREMENTS
(EXCEL W ORKSHEET)
DATA TABLE:
ROOM TYPE
ROOM USE
HOW MANY OF EACH
SPACE PROGRAM
(ACCESS TABLE)
DATA TABLE:
ROOM INSTANCES
ROOM TYPE
ROOM USE
ROOMS LIST
(ACCESS TABLE)
ROOM OBJECTS:
GEOMETRY
DATA ATTRIBUTES
BIM
(REVIT PROJECT)
FORMALIZING THE SPACE PROGRAM
Organizational Uses and Room Types

Organization: activity or department.
Type: characteristics of the room.
ORGANIZATION
ROOM TYPE
PRESIDENT
OFFICE - 1
ADMINISTRATION
OFFICE - 2
MAINTENANCE
RECEPTION
DIRECTOR
CLASSROOM - 1
TEACHING
CLASSROOM - 2
ASSISTANTS
LABORATORY
SINGLE-LEVEL ORGANIZATIONAL USES AND ROOM TYPES

Space Program
Organization and Type.
Quantity.
Area Each.
SPACE PROGRAM TABLE

IN MICROSOFT ACCESS
Aggregate Planning Areas

ROOM TYPES
ORGANIZATIONAL USES
UNIQUELY
IDENTIFIABLE
(ORGANIZATION VALUE)
ORGANIZATION
PRESIDENT
GROUPING
(ROLL-UP OF
AREAS AND COUNTS)
ORGANIZATION
CATEGORY
(ROOM TYPE VALUE)
ROOM TYPE
OFFICE - 1
GROUPING
(ROLL-UP OF
AREAS AND COUNTS)
ROOM TYPE
CATEGORY
OFFICE - 2
ADMINISTRATION
MAINTENANCE
UNIQUELY
IDENTIFIABLE
OPERATIONS
RECEPTION
DIRECTOR
CLASSROOM - 1
TEACHING
CLASSROOM - 2
INSTRUCTION
ASSISTANTS
LABORATORY
ADMINISTRATION
EDUCATION
GROUPING OF ORGANIZATIONAL USES AND ROOM TYPE

AGGREGATE PLANNING AREAS
Architectural Parti
Importing as Unplaced Areas
Placing Areas
Developing Massing
Manipulating Planning Areas
Architectural Elements
Validating Areas
Creating Rooms
Room Characteristics
ORGANIZATIONAL USES
ORG ID
DEPARTMENT NAME
ROOM TYPES
TYPE ID
TYPE NAME
01
MANAGEMENT
OFF01
OFFICE - LARGE
02
INSTRUCTION
OFF02
OFFICE - MEDIIUM
03
SALES
OFF03
OFFICE - SMALL
04
MARKETING
CONF
CONFERENCE
05
FACILITIES
BREAK
BREAK ROOM
COPY
COPY AREA
STOR
STORAGE
CLAS01
CLASSROOM 1
CLAS02
CLASSROOM 2
CLAS03
CLASSROOM 3
STUDY
STUDY AREA
DEFINITION OF TYPE AND ORGANIZATION KEY VALUES

CREATING ROOMS
SPACE PROGRAM
PROG ID
ORG
01.0
ROOMS LIST
TYPE
COUNT
REQ AREA
ROOM ID
PROG ID
ORG
01
OFF01
01.1
01
OFF02
01.2
01
01.3
TYPE
800
01.0.0
01.0
01
OFF01
300
01.1.0
01.1
01
OFF02
OFF03
200
01.1.1
01.1
01
OFF02
01
CONF
800
01.2.0
01.3
01
OFF03
01.4
01
BREAK
600
01.2.1
01.2
01
OFF03
01.5
01
COPY
200
01.2.2
01.2
01
OFF03
01.6
01
STOR
100
01.2.3
01.2
01
OFF03
02.0
02
CLAS01
1500
01.3.0
01.3
02
CONF
02.1
02
CLAS02
1000
01.3.2
01.3
02
CONF
02.2
02
CLAS03
900
01.3.3
01.3
02
CONF
02.3
02
STUDY
800
01.3.4
01.3
02
CONF
02.4
02
CONF
200
01.4.1
01.4
02
CONF
ORGANIZATIONAL USES
ORG ID
SPACE PROGRAM
ROOMS LIST
DEPARTMENT NAME
NUMBER
ROOM TYPES
TYPE ID
TYPE NAME
01
MANAGEMENT
OFF01
OFFICE - LARGE
02
INSTRUCTION
OFF02
OFFICE - MEDIIUM
03
SALES
OFF03
OFFICE - SMALL
04
MARKETING
CONF
CONFERENCE
05
FACILITIES
BREAK
BREAK ROOM
NAME
ACT AREA
LINKING REVIT TO A DATABASE
Creating Room List in Database
Creating Rooms
Importing Unplaced Rooms
Placing Rooms
Rooms in Their Actual Location
Validating Program
with the Database
Supporting Construction Documentation

Data Not Included in the BIM
Room Requirements
Doors and Hardware
Furniture and Equipment Specifications
Room Data Sheets
Numbering Rooms
Construction Documentation Room Number
Different from:
RoomId.
Signage.
Processes
Stages
DATABASE SYSTEM
Programming
Design Development
ROOM
Workflows
BIM
VIEW
TAGGED VIEW
All in Revit
In Access
SYNCHRONIZE
IMAGE
DATABASE
ROOM
DATA
1027
REPORT
ALTERNATE ROOM DATA SHEET PROCESSES

1027
SHEET
Data Sheets in Revit

View for each room:
2D PLAN option.
DATA SHEETS IN REVIT
Tag all rooms:

Special room tag.
Room data values.
DATA SHEETS IN REVIT
Place Views on Sheets
Data Sheets in Access

Two views for each
room:
2D Plan option.
3D Options:
View angle.
Extents:
Section box.
Crop box.
Both.
DATA SHEETS IN ACCESS
Export images:
Naming.
File type.
Input Form:
Used in User Group
meetings to record
decisions.
Report:
Used to validate
decisions and track
data.
Supplemental Topics
ADDITIONAL TOPICS
Parent-Child Family
Relationships
Site FAR Example:
Parcels : Areas.
Buildings: Masses.
Buildings Area.
Roll-up floor areas.
SITE PLANNING
ADDITIONAL TOPICS
Floor-Area-Ratio (FAR)
AreaBLDG = Floor Areas.
Building Property
AreaPROPERTY = Property Area.

FAR = AreaBLDG / AreaPROPERTY
View Filter
ADDITIONAL TOPICS
Related Database Tables

in
Revit Color Fill Plans
Room Type Category:
Indirect values.
Rolled-up values.
Concatenation.
RELATED DATA IN COLORED PLANS
ADDITIONAL TOPICS
ROOMS
ID
TYPE
ROOM TYPE
10101
OFF-1
10101A
OFF-2
ID
10102
OFF-3
OFF-1
OFF
10103
OFF-3
OFF-2
OFF
10104
OFF-3
OFF-3
OFF
OFF
OFFICE
10105
CONF-1
CONF-1
MEET
INST
INSTRUCTION
20110
BRKRM
BRKRM
MEET
MEET
MEETING ROOM
20843
CLASS-1
CLASS-1
INST
30102
CLASS-1
CLASS-2
INST
30104
CLASS-2
STDY
INST
30105
STDY
30201
OFF-3
30202
OFF-3
30203
OFF-3
CATEGORY
ROOM TYPE CATEGORY

ID
DESCRIPTION
SUM ROOM AREA:

BY ROOM TYPE CATEGORY
BY FLOOR
ADDITIONAL TOPICS
Derived Values:
In Access:
Related Tables:
Primary Key
Foreign Key
ROOMS
ROOM
TYPES
ROOM TYPE
CATEGORIES
ADDITIONAL TOPICS
Revit Access
Using RevitDbLink
Update Derived Values
Related Table.
Parameter RoomTypeCategoryId.
Value from:
Room Parameter RoomTypeId.
Foreign Key to:
RoomTypes.RoomTypeCategory.
Parameter RoomTypeCategoryDescription.
Value from:
Room Parameter RoomTypeCategoryId.
Foreign Key to:
RoomTypeCategories.Description.
ADDITIONAL TOPICS
String Concatenation:
String Values From:
Parameter RoomTypeCategoryId.
Constant
Level Number
Combined To:
Parameter RoomTypeCategoryFloor.
Form: FOOD-01
Identifies Rooms:
Same category.
Same floor.
ADDITIONAL TOPICS
Math Calculation:
Numerical Values:
Parameter Area.
Grouped by:
Parameter RoomTypeCategoryFloor.
Summed to:
Parameter RoomTypeCategoryFloorArea.
ADDITIONAL TOPICS
Convert Number to String:

Numerical Value:
Parameter RoomTypeCategoryFloorArea.
Converted to String:
Parameter RoomTypeCategoryFloorString.
ADDITIONAL TOPICS
Using RevitDbLink
Update Derived Values
Concatenation.
Parameter: RoomTypeCategoryTitle.
Value from:
Room Parameter: RoomTypeCategoryId.
Constant: .
Room Parameter: RoomTypeCategoryDescription.
Constant: ( .
Room Parameter: RoomTypeCategoryFloorString.
Constant: SF )
ADDITIONAL TOPICS
Example Project
Example Project
Images courtesy Catherine Chan - HDR.
EXAMPLE PROJECT
Image courtesy Catherine Chan - HDR.
EXAMPLE PROJECT
EXAMPLE PROJECT
EXAMPLE PROJECT
EXAMPLE PROJECT
EXAMPLE PROJECT
Thank You
Please complete a Speaker Evaluation Form
AB1796 Advanced Techniques for Managing Building Data
in Autodesk Revit
Mario Guttman
Download Tools:
www.WhiteFeetTools.com
http://case-inc.com
Mario Guttman
Senior Design Technology Specialist
m.guttman@case-inc.com
Autodesk is a registered trademark of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear
in this document. 2013 Autodesk, Inc. All rights reserved.

AB1796 Advanced Techniques For Building Data in Revit - Presentation

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

AB1796 Advanced Techniques For Building Data in Revit - Presentation

Încărcat de

Drepturi de autor:

Formate disponibile

Advanced Techniques for Managing Building Data

Advanced Techniques for Managing Building Data in Autodesk Revit

Key learning objectives

Evaluate computer system architectures and software options.

The presentation also includes sections on:

Advanced Techniques for Managing Building Data in Autodesk Revit

Introduction to Building Data

Advanced Techniques for Managing Building Data in Autodesk Revit

Needs for Managing Data:

Advanced Techniques for Managing Building Data in Autodesk Revit

INFORMATION FLOW THROUGH A DATABASE SYSTEM

Advanced Techniques for Managing Building Data in Autodesk Revit

Advanced Techniques for Managing Building Data in Autodesk Revit

Design Team Requirements

Advanced Techniques for Managing Building Data in Autodesk Revit

First, we want to understand our data,

Then, we can implement software to

Advanced Techniques for Managing Building Data in Autodesk Revit

General Principles of Objects and Databases

Advanced Techniques for Managing Building Data in Autodesk Revit

Objects and How Revit Uses Them

Properties: Data (dimension; manufacturer.)

Advanced Techniques for Managing Building Data in Autodesk Revit

OBJECTS AND HOW REVIT USES THEM

PARENT CHILD OBJECTS

OBJECTS AND HOW REVIT USES THEM

Families are one

FAMILIES TYPES INSTANCES

OBJECTS AND HOW REVIT USES THEM

Shared Parameter: Same name is used in other models.

Project Parameter: Parameter applies to all families.

THESE ARE INDEPENDENT OF ONE ANOTHER

Advanced Techniques for Managing Building Data in Autodesk Revit

OBJECTS AND HOW REVIT USES THEM

Advanced Techniques for Managing Building Data in Autodesk Revit

OBJECTS AND HOW REVIT USES THEM

Advanced Techniques for Managing Building Data in Autodesk Revit

OBJECTS AND HOW REVIT USES THEM

Advanced Techniques for Managing Building Data in Autodesk Revit

OBJECTS AND HOW REVIT USES THEM

Data equivalence of Types and Instance Parameters

ONE DOOR TYPE

Door Color: RED

Door Color: BLUE

TWO DOOR TYPES

Advanced Techniques for Managing Building Data in Autodesk Revit

OBJECTS AND HOW REVIT USES THEM

Use of Schedule Keys with Instance Parameters

ONE DOOR TYPE

Advanced Techniques for Managing Building Data in Autodesk Revit

Basics of Relational Databases

Advanced Techniques for Managing Building Data in Autodesk Revit

BASICS OF RELATIONAL DATABASES

Advanced Techniques for Managing Building Data in Autodesk Revit

BASICS OF RELATIONAL DATABASES

Primary Key Field

Advanced Techniques for Managing Building Data in Autodesk Revit

BASICS OF RELATIONAL DATABASES

Foreign Key Field

Points to the Primary Key of

BASICS OF RELATIONAL DATABASES

One to Many Relationship

Defined by a Foreign Key.