VectorWorks ‘BIM in Practice’ Series

Building Information Modeling

Demonstration Project #2:
Collaborative Strategies for a Large Project

Ellicott Heights
Mixed Use Development
Ellicott City, Maryland

Robert Anderson, AIA

Vice-president, Integrated Products

Jeffrey W. Ouellette, Assoc. AIA

Content Developer, Integrated Products
VectorWorks BIM in Practice Series

Table of Contents
1 Introduction......................................................................................... 3 Building Section ................................................................................ 11
Unit Plans........................................................................................... 11
Download and Installation .......................................................................... 3
4.2.3 Conceptual Modeling........................................................................... 11
2 Project Summary................................................................................ 4 Preliminary DTM............................................................................... 11
2.1 BIM Implementation ............................................................................ 4 Building Massing Model....................................................................11
2.2 Architectural Design ............................................................................. 4 4.3 Design Development BIM................................................................... 12
2.2.1 Site............................................................................................................4 4.3.1 Site Model..............................................................................................12
2.2.2 Architectural Design Program.............................................................. 5 4.3.2 Building Model ..................................................................................... 12
BIM Data Structure - Level I............................................................. 12
3 Designing the BIM...............................................................................6
BIM Data Structure - Level II............................................................ 12
3.1 Workflow Factors .................................................................................. 6
4.3.3 Drawings................................................................................................13
3.1.1 Output......................................................................................................6
Schematic Design Drawings.............................................................. 13
3.1.2 Project Size.............................................................................................. 6
Design Development Drawings......................................................... 13
3.1.3 The Project Team.................................................................................... 6
3.1.4 Consultants..............................................................................................6
3.2 Project Model Data Structure .............................................................. 7
3.2.1 Building vs. Site...................................................................................... 7
3.2.2 Building Data.......................................................................................... 7
Horizontal Vs. Vertical Data Sets ........................................................ 7
The “I” of BIM – Object Data and Schedules ..................................... 7
Dependent Views ................................................................................. 8
Resource Management......................................................................... 8

4 Ellicott Heights BIM......................................................................... 10

4.1 Project Setup........................................................................................ 10
4.1.1 Project Template................................................................................... 10
4.1.2 Project File/Folder Data Organization ............................................... 10
4.2 Preliminary/Schematic Design BIM.................................................. 11
4.2.1 Site GIS Data........................................................................................ 11
4.2.2 Conceptual Drawing ............................................................................ 11

BIM Demonstration Project #2 NNA2008.01- Ellicott Heights 2 of 14

VectorWorks BIM in Practice Series
1 Introduction
VectorWorks Architect provides Building Information
Modeling (BIM) capabilities that offer a true increase in
productivity and benefits in the design process. Using a
BIM methodology, your 3D models, 2D drawings, and
project data are linked into a simple, yet flexible and
powerful, design and documentation environment.
The VectorWorks BIM in Practice Series is an ongoing
collection of projects that provide users with practical,
pragmatic guidance and discussions about how to
implement projects in VectorWorks using BIM methods.
This collection contains a variety of project types, sizes,
style and complexities. Each project is meant to
highlight a particular method, workflow or set of tools,
and vary from project to project, to cover a variety of
strategies. At Nemetschek North America, we hope the
lessons they provide will address the widely varying
needs of our customers.
The architectural design of this project is a theoretical/
fictional exploration, conceived entirely by Nemetschek
North America, Inc. for the sole purpose of
demonstrating the technologies of VectorWorks
described herein. A great deal of effort, however, was
spent to create a design that follows current codes and
realistic construction strategies. Any relationship to
actual projects and/or design concepts is purely
unintentional and coincidental.
The drawings, specifications, ideas, designs and
arrangements represented thereby are and shall remain
the property of Nemetschek North America, Inc., the
copyright holder. They are for the sole purpose of
education and not guaranteed nor offer warranty for use
for construction. No part thereof shall be copied or
disclosed to others or used in connection with any work
or project or by any other person for any purpose
without the written consent of Nemetschek North
America, Inc.
While not exhaustively comprehensive, the drawing set,
a “Design Development” package, contains enough
examples of drawings – site and floor plans, enlarged
plans, exterior elevations, building sections, wall
BIM Demonstration Project #2
sections, interior elevations, integrated schedules and
rendered perspectives of various types – to give users
direction of how to construct a multi-user, BIM-based
architectural drawing set in VectorWorks Architect.
The discussion of the white paper follows an intertwined
two-part scheme; the BIM implementation and the
architectural design. While the emphasis will be on the
implementation of the technology and methods, the
discussion of the design is important to support the logic
for the technical methods implemented.
Download and Installation
This project was created using VectorWorks Architect
with RenderWorks 2008 and should be viewable by all
VectorWorks 2008 products. Due to the file format
change for 2008 (from .mcd in v12 to .vwx) and the
project’s reliance on the new Design Layer Viewports,
these files are NOT compatible with earlier versions of
VectorWorks.
All files associated with this project are located in a
single file folder “NNA2008_01”, contained in a .ZIP
archive and available for download on the VectorWorks
website.
The primary BIM file is a collection of external
references and their presentation as a whole building in
various architectural drawings:
NNA2008_01>Building>Building_Model.vwx
All files are setup with relative referencing; as long as
the files maintain their locations within the
“NNA2008_01” project folder, then, no matter the
location of the project folder on a destination storage
device, all references should properly resolve
themselves.
PDF versions of the Schematic Design and Design
Development documents are also available as separate
downloads.
NNA2008.01- Ellicott Heights 3 of 14
VectorWorks BIM in Practice Series
2 Project Summary
The primary purpose of the Ellicott Heights project is to
explore the best method of using VectorWorks Architect
in a [strict] BIM workflow, on an architectural design of
significant size/scope, in a collaborative team
environment. As the design and construction industry
moves to embrace the potential of a more collaborative,
technologically advanced, and fluid means of project
conception and execution, it is important to educate our
users about VectorWorks’ ability to fulfill the needs of
our users in such an environment.
This project and supporting materials, such as this
document, are intended to serve as references for the
implementation of BIM practices, where our users may
find themselves unfamiliar with the full extent of
VectorWorks functionality. The creation of an
‘intelligent model’ has been within the scope of
VectorWorks capabilities for some time, but many users
are struggling to transform their practices and their
working methods, to use the program to its fullest
extent.
The project and documentation assumes there is already
a familiarity and expertise with a broad range of
functionality in VectorWorks. Thus, the intent is to
expand on the user’s knowledge and illustrate at least
one method of implementing various tools and
functionality, with further exposition, or sidebars, of
possible alternatives, in appropriate topics.
Many of the best practices described in this document
strictly follow the intended functionality of particular
tools. However, some recommendations are based on
negotiating between the ‘ideal’ functionality and the
pragmatic concerns of the user putting the tools into
practice.
While the architectural design and aesthetic is really
secondary to the purpose of this project, every attempt
has been made to adhere to real-world design
constraints, construction methods, standards and code
requirements.
BIM Demonstration Project #2
2.1 BIM Implementation 2.2 Architectural Design
This project describes a set of best practices for Ellicott Heights is a design proposal for a mixed-use,
integrating a BIM methodology in the design of a large- medium-high density, urban context redevelopment of
scale project using VectorWorks Architect in a an existing suburban, under-utilized area of Ellicott City,
collaborative environment. Maryland. This design proposal is a purely speculative
and theoretical undertaking; its primary purpose to
The following aspects of a VectorWorks BIM
explore the capabilities of VectorWorks on a large
implementation will be explored:
project.
1) Large scale/scope; A project encompassing at least
Our proximity to the proposed site and familiarity with
1,000,000 total square feet of construction
the region were important factors in trying to establish a
development in the form of a multi-use, multi-story
project with some real-world context and constraints,
building and structured parking with a significant
instead of focusing on small, individual, disconnected
site footprint (≥150,000 sq.ft.);
vignettes to describe functionalities. This should help
2) Distributed/collaborative workflow; Exploring our users understand how smaller processes relate to
methods of enabling multiple users to create and each other in a larger context of project design and
manipulate data through the following techniques: documentation.
a) Use of multiple files; the larger building and
2.2.1 Site
site are broken up into multiple pieces for
manipulation; The proposed site is an amalgamation of several existing
lots located to the north of the historic town center in the
b) Multiple users working with any of the files, at northwest quadrant of the intersection of U.S Highway
any time, to increase the level of productivity;
40 (east-west) and Rogers Avenue (north-south).
c) Use of referencing technology to assemble the Currently, the site is occupied by an automotive retailer,
multiple files into a single BIM from which all an abandoned “big box” retail development, and a small
plot files are created; driver’s education business, located in a residential
structure between the larger properties.
3) Utilizing supplied VectorWorks Architect tools and
procedures for the setup and management of the
BIM and associated drawings;
4) Accommodating interaction with design consultants
such as M/E/P, structural and civil engineers;
5) Integrating common design/thinking techniques and
strategies employed in preliminary design,
schematic design and design development phases,
such as 2D sketching/drawing and 3D volumetric
modeling and space planning.
Figure 01: Google Map of project location and vicinity
NNA2008.01- Ellicott Heights 4 of 14
VectorWorks BIM in Practice Series
Please refer to the Google Maps link here (click link or
copy and paste the web address into your browser):
http://maps.google.com/?q=8620+Baltimore+National+Pike,
+Ellicott+City,+MD
+21043&sll=39.284324,-76.810377&sspn=0.009376,0.013229
&ie=UTF8&ll=39.282522,-76.81102&spn=0.009376,0.01322
9&t=h&z=17&iwloc=addr&om=0
This project is one piece of a larger urban design
proposal for the Ellicott City community with the goal
of increasing the density of occupation and functional
use of an area outside the historic core, promoting a
more intensively used, urban environment along a major
travel corridor. It also considers the recently devised
Howard County General Plan 2000, examining past
trends, anticipating future growth and promoting
strategies to cope with development in the county for the
next 20 years.
For those interested, the General Plan documents can be
found at the following link to the Howard County
Maryland government website:
Howard County Department of Planning & Zoning General
Plan 2000
Figure 02: Howard County General Plan 2000 map
BIM Demonstration Project #2
2.2.2 Architectural Design Program
The design program for the project incorporates the
following aspects, in no particular order or priority:
1) Mixed-use occupancy; encouraging a more
intensive use of the site and diversifying the
existing neighborhood through the following
functions:
a) Medium/large retail;
b) Small retail/Small office;
c) Residential (possible mix of rental/condo); with
a variety of unit types and sizes (1-, 2-, and 3-
bedroom) including a “penthouse level”;
d) Primary parking as structured parking for
commercial users and residents;
e) Secondary parking using surface parking for
commercial/retail users;
f) Semi-public, interior & exterior “green space”,
available to residents/tenants and their guests;
2) Multi-story, single structure;
3) Use of an atrium configuration in the residential
portion of program to incorporate natural air and
light into the interior of the structure;
4) Provide “visual anchor” to proposed larger
redevelopment of vicinity;
5) Modern construction and aesthetic with references
to historical/regional materials and design elements;
6) Propose an alternative means to engaging the
existing environment and infrastructure by
increasing density of the site and creating an “edge”
along the north side of U.S. Highway 40.
The complexity of the program is seen as an opportunity
to explore the flexibilities of a VectorWorks Architect
BIM implementation in addressing many ‘parts’ of a
whole project.
NNA2008.01- Ellicott Heights 5 of 14
VectorWorks BIM in Practice Series
3 Designing the BIM
Parallel with, or even prior to, the architectural design,
there is a “design” of how all the data and its
representations (e.g. model, drawings, schedules and
specifications) will be structured to accommodate the
desired format for the output of information, the amount
of data/size of project, the size of the team/workgroup,
the responsibilities of various team members, and the
exchange of information with consultants, who may be
on entirely different data platforms. Each of these
workflow factors has an effect on the level of
consolidation or distribution of project model data and
where ideas and data are created, managed or extracted
for representation uses.
3.1 Workflow Factors
3.1.1 Output
Now and in the foreseeable future, output requirements
for a project implementing BIM really aren’t different
than a traditional drafting methodology. With or without
BIM, at the end of the design and documentation
process, the architect must have a set of paper drawings
and specifications that describe the intent of the
construction of the building and its relationship to the
site it is located on. Today, these documents are integral
to the legal basis for the contracts of the design and
construction process between all parties involved.
Regardless of input or output technology, the design
process is about creating information. This information
is codified in a product that contains views pertinent to
various aspects of the building’s functionality and
construction.
Without BIM, the process of creating this information
relies on a great deal of direct communication and
manual coordination to ensure that the data, in its
different forms (e.g. drawing vs. text, notation vs.
schedule vs. specification) and locations (e.g.
architectural plans, section, elevations, details,
engineering drawings, shop drawings, specifications,
etc.) agree. Also, the transformation of one type of data
into another (i.e. architectural plan into material take-off
BIM Demonstration Project #2
and cost) requires a great deal of work and error
checking.
With BIM, once data is entered into the model, it can be
formatted and reformatted, on the fly, as needed. Output
can be formatted and tailored in a number of different
ways, to specific purposes, such as quantity schedules
for more accurate cost determination by contractors or
3D representations of the building for better
coordination with engineering consultants. Drawings,
schedules, and specifications are nothing more than
views of the same data set that are formatted for a
specific purpose.
For the purposes of this project, and the needs of the
design and construction industry today, we will focus on
providing a “print-based” output, whether paper or
electronic (e.g. PDF).
3.1.2 Project Size
The Ellicott Heights project explores the best method of
“dividing and conquering” an architectural design of
significant size/scope in a team environment while
implementing a BIM methodology using VectorWorks.
Beyond sheer amount of building area, the multivalent
nature of the project is just as important to consider. If
the project were 1 million square feet of a simple
geometric, single-use space (e.g. “big box” retail or dry
goods warehouse), dividing the work among a team of
people may be more complex than is effective. With a
mixed-use/mixed occupancy project, there are many
ways to parcel the project based on functional expertise
of team members, as well as logical divisions of use/
occupancy or formal geometry.
3.1.3 The Project Team
Traditionally, projects of this size and type done in
larger offices, in a drafting method, would have a sizable
team assigned, with each member of the team taking a
particular task- or output-based responsibility (e.g.
building elevations vs. building sections vs. floor plans
vs. unit plans vs. stair plan and details vs. bathroom
plans, interior elevations and details vs. wall sections/
details vs. schedules, etc.). With BIM, these separations
NNA2008.01- Ellicott Heights
are artificial, because the nature of data- and geometry-
rich objects allows an input once, view many times,
many ways method; there are fewer “nodes” of input for
the same number of outputs.
Without being prescriptive, for this particular project,
one could speculate a project team of five (5) people,
including a Project Architect, a Project Manager, and
three other architectural team members that divide up or
exchange responsibility for the actual input of data into
the BIM with the Project Manager. While the Project
Architect may focus on the larger picture of design and
client/consultant coordination, the Project Manager
might focus on the units and all their data and views and
focus on the final drawing set output, ensuring that
everything is coordinated and properly formatted.
Another person might be responsible for the parking
ramps, a fourth on the residential floors and the fifth
person focusing on the retail/office along with vertical
circulation and site integration.
3.1.4 Consultants
The larger and more complex a project gets, the more
the architect relies on specialized consultants to input
information into the data set for the description of the
building. Prior to the use of CADD, this data was
exchanged via “paper” drawings and schedules. There
was really only one format (regardless of whether it was
mylar, vellum, paper or transparencies). CADD (and
computer platforms, in general) introduced an additional
problem of compatibility of data between digital file
formats (e.g. dwg, dxf, pln, dgn, mcd, etc.), even if it
essentially described the same thing.
Ellicott Heights will assume that Mechanical/Electrical/
Plumbing (MEP) designs will be the sole responsibility
of consultants. Their primary interface with the BIM
data will be 2D, via the import of CAD data into the
architectural set for coordination purposes. The BIM
provides layers for MEP content to be imported
independent of the architectural data, yet allow for
coordination and possible return export.
6 of 14
VectorWorks BIM in Practice Series
The structural design always proves to be more
complex, because of its integral relationship to the
architecture. We will assume that the structural design is
a more collaborative process, allowing the architecture
team to manipulate the structural components and
concepts in concert with the structural engineering
consultant.
With VectorWorks Architect’s IFC Import/Export
capabilities, there will be opportunities for the exchange
of 3D data, like the structural elements, between IFC
compliant platforms.
3.2 Project Model Data Structure
If the primary purpose of the Ellicott Heights project is
to explore the best method of “dividing and conquering”
an architectural design of significant size in a team
environment then some care must be taken initially in
determining the levels of division appropriate for such a
large amount of data. Given the workflow factors
described above, the project data needs an
organizational structure that offers a restrained number
of input points that can be effectively coordinated
between each other, eliminating duplication of effort and
the potential chaos of multiple authors of the same data.
3.2.1 Building vs. Site
The project data is first divided between the site model
and the building model. Separating the building from the
site, but maintaining a link between the two, allows site
and building to be developed simultaneously and reduce
the size of a single large data file into smaller data files,
optimizing speed of any single data set.
This project maintains a set of site data files separate
from the building data files, with the final site design
being referenced into the building model file to provide
the proper context for various views of the building
model (e.g. site plan and exterior building, sections and
elevations).
This also builds flexibility into the design process
allowing the designers of the site and the building to
explore multiple configurations/design options in
BIM Demonstration Project #2
separate files and testing concepts until finally linking
the ultimate solutions together.
3.2.2 Building Data
The building model is a large set of data that can be
divided into smaller pieces for more efficient input by
multiple team members. Attention must be paid to the
effects of any such division on the identification of
objects and scheduling, the display of views dependent
upon a consolidated model (e.g. building elevations,
building sections) or distributed model (e.g. interior
elevations of units, unit plans), and the management of
common resources (e.g. textures, symbols, walls styles,
hatches, etc.) across multiple files.
The division of the building model data may be among
either the levels (i.e. 1st floor, 2nd floor, etc.) or the
functions (i.e. common vertical circulation core, parking
structure, atrium, etc.) of the building design. This data
structure may also depend the heavy use of large
repetitive elements, either vertically or horizontally,
which may prejudice one scheme over another, in
addition to level-based or functional options.
Horizontal Vs. Vertical Data Sets
One could consider two methods of distributing the
larger set of building data, horizontal or vertical.
In a horizontal schema, a building level/story is seen as a
singular data set that can reside in an individual file and
be pulled together with others into an amalgamated
building model file. Formal elements that may be
common to multiple floors then require another level of
distribution/integration/coordination of resources.
In a vertical schema, programmatic functions are seen as
a singular data set, regardless of their number of levels
(e.g. parking ramp, vertical circulation, residential, etc.)
that can reside in an individual file. Formal elements
that may be common to multiple floors can be more
easily managed.
At first glance, the choice between these two options
may be obvious for a given project. The Ellicott Heights
project explores the use of both methods
NNA2008.01- Ellicott Heights
simultaneously; the floors of the main building are
individual, single-story “level” files and the parking
structures are individual, multi-story files. To further
explore the possible complexity of data distribution and
conglomeration, the residential levels 3, 4, and 5 are just
copies of the same source file, placed on different story
layers using design layer viewports.
The “I” of BIM – Object Data and Schedules
A distributed data workflow, using referencing to a
central BIM model, can create a unique dilemma in the
identification of objects such as doors and windows for
scheduling purposes. The dilemma is determining where
object data and schedules are located and how to
“count” the identified, or labeled, objects from
referenced sources.
If all the building data sets are unique (i.e. each floor has
a different configuration or low level of repetition to
negate the need for comprehensive symbols), then
identifying each door and window with a unique ID tag
would be easy enough and logical.
If, however, there is a moderate to high degree of
repetition from floor to floor, the use of symbols to
describe “bays” of construction, repetitive units plans, or
layer links/design layer viewports to copy multiple
iterations of the same floor/story, then it would be better
to treat doors and windows as ‘types’, identifying each
set of common/identical parameters with a single label
(i.e. all 2’-0”x4’-0” fixed aluminum windows would be
W-A, while all 3’-0”x 6’-0” casement aluminum
windows would be W-B, etc.).
In either case, a worksheet could be configured to count
and schedule all items (e.g. door schedule, window
schedule). In the first case of unique IDs, all objects and
their parameters would be listed in the schedule.
In the second case of ‘typed’ objects, the list would only
display the different types and their parameters, but also
include a count of the number of each type located in the
model. For large projects, this would significantly
reduce the physical size of the schedule and shift the
coordination issues of verifying the unique
characteristics of each door or window to verifying an
7 of 14
VectorWorks BIM in Practice Series
objects compliance with a standard type, regardless of
where it is.
Because Ellicott Heights so heavily leverages the use of
symbols for creating common exterior envelope bays
and the repetition of unit plans on multiple layers/stories
with the further complexity of residential layers being
duplicated, the door schedule example is a “type”
schedule. This schedule identifies unique types of doors
in the model, lists their common parameters and then
counts the number of time they are located in the model.
At the design development level, this may be all that is
needed to help give the design team and contractor
enough information for cost estimating purposes.
Depending on the construction methodology of the
contractor, this may be sufficient for construction
documents, but the same data, with some effort could be
transformed to accommodate the unique identification of
every door for location and sequencing purposes.
Dependent Views
Under the “draw/model it once” paradigm of BIM, data
is entered once in any location and viewable or
represented in many other formats, viewpoints or
locations. The type and/or extent of the views, as well as
the team configuration and desired workflow helps
determine the location and organization of the building
geometry data and notations/dimensions.
In a typical project documentation the following views
are required to thoroughly describe the intent of the
design:
• Site Plan
• Floor Plans
• Building Elevations
• Building Sections
• Plan Details
• Wall Sections
• Section Details
• Interior Elevations
BIM Demonstration Project #2
• Schedules
Each of these views requires a unique representation of
the same set of data. In a BIM implementation, some
rely on purely 2D geometry representations more than
3D model views. Some are more efficient by being
orthogonal views of a 3D model than 2D “drawings”.
Some views rely on the entire set of building data (e.g.
building elevations and sections need all floors/stories
adjacent to each other in one place), but other views rely
only on a much smaller portion of the model (e.g. floor
plans and unit interior elevations).
Concurrently, there is the issue of where the output
drawings (i.e. Sheet Layers) reside. Is there a central
BIM file from which ALL drawings are plotted, to
leverage the power of the Issue Manager and make it
easier to coordinate drawings? Or are drawings located
closest to the source of their views (e.g. floor plans in
the level plan files, unit plans and elevations in unit
file)?
The site plan may require only the site model
information and one ground level floor plan. Thus, there
is a choice between referencing the site model into the
building model (possibly creating a larger, but
comprehensive, file) or only the ground floor of the
building into the site plan (a smaller file, but limited in
the flexibility of views derived from it).
The floor plans require only the 2D views of the
particular story/level they represent. But, is it efficient to
spread out the floor plan sheet layers across multiple
source files?
Some views (e.g. exterior building elevations, building
sections, wall sections) require the entire data set
(geometry) of the BIM to be centralized in some place,
regardless of whether other views (e.g. floor plans and
plan details) are created in separate files.
How do team configurations and workflows affect
views? Intertwined with the team configuration and
workflow is the responsibility and location of view
dependent information (e.g. notes, markers and
dimensions). In a highly referential BIM, are they
located in the source file or the target/central file? Are
NNA2008.01- Ellicott Heights
they located on a design layer or in the annotation space
of a viewport? Some views, like section viewports,
require that notations occur within the annotation space
of the viewport. Plans could have their notes and
dimensions in either the source document design layer,
the central BIM model design layer where the
referenced design layer viewport is located, or in the
annotation space of the viewport no matter its file
location.
Are the team members responsible for input into the
model also responsible for the display/views/
presentations of that data? In a traditional drafting
paradigm, the answer “yes” may be obvious. However,
in a BIM implementation, is it necessary for the person
inputting model data to be responsible for the formatting
or even notation of the views? Couldn’t a viable
alternative of distributing workload responsibility create
an organization where lots of people populate the model
with data, but only one person controls how that data is
viewed? Such a workflow might increase the accuracy
of coordination between notations and consistency of
drawing output. If responsibility for the creation of
views and notation of those views is delegated to the
authors of parts of the model, what happens when views
or data overlap? Could the main BIM file be duplicated
to distribute the workload?
Ellicott Heights is set up as a ‘centralized documentation
model’. All of the parts of the project (e.g. floor levels/
stories and site model) are referenced into a single,
central model file in which all sheet layers for the
drawing set are located. It makes for a larger file, but it
helps in coordinating the markers for elevations, details,
and sections. The drawing list on the cover sheet is a
worksheet that automatically ‘counts’ and lists the sheets
in the set, as the number and type of drawings grows or
shrinks. It centralizes the plotting/publishing of the
documents.
Resource Management
Finally, there is the issue of Resource Management, the
creation, editing, coordinating, and management of data
and drawing resources like symbols, custom wall styles,
hatches, textures, record formats, etc.
8 of 14
VectorWorks BIM in Practice Series

There are three options for managing and distributing The Ellicott Heights project relies on the second method
common resources in a distributed data model like the of resource management, using the project template file,
Ellicott Heights project. NNA2008_01>Resources>NNA2008_01-Template.vwx
The first option is really an on-the-fly workflow. As as the central repository for resources created by team
each user creates data/content in their files, they can members while working on the various parts of the
“push” (via the new ‘Export’ option in the Resource model.
Browser) from the file they are working into a template/
project file or the other team members can “pull” from
the template/project file into their current file (via the
‘Import’ option).
The other two options rely on creating a single container
for all resources to reside, a project library file. In these
cases the team may use the project template file.
The second option, like the first, is about the members
of the team exporting and importing, but now it is to and
from the project library file. However, updates from one
team member are not automatically recognized by the
system of another. It still requires a concerted effort to
communicate between team members. That
communication is not bad. In fact, this level of
communication can be seen as an advantage to
collectively control the quality of any changes or
additions to the resources content.
The third option provides more automation, but also
removes a level of separation that may be desired for
quality control. This involves setting up a Workgroup
Referencing (WGR) link in each BIM data file with the
project library file. In VW2008, users have the option to
use the new default style of referencing, which links the
data in the external source file, but leaves all instances
of that data in the external file, OR they have the option
to create a “legacy”-style WGR, where all the external
source information is copied into the current document
and can be accessed, via the Resource Browser. Team
members can then insert these referenced resources into
their own files. If the resources are changed in the
project library file, they are automatically updated in the
various target files.

BIM Demonstration Project #2 NNA2008.01- Ellicott Heights 9 of 14

VectorWorks BIM in Practice Series
4 Ellicott Heights BIM
Given the conceptual framework of addressing a BIM
implementation in the proposed project, we will now
analyze the actual execution. This analysis will focus on
the execution as carried out from an advanced schematic
design proposal stage to a geometrically complete, but
notationally light, design development level. At the
design development stage, all progress forward, into
construction documentation and beyond, generally falls
within the framework established by this point.
4.1 Project Setup
Every office has their own established set of standard
workflows, graphics, digital file management rules, and
CADD/BIM data standards. While this project/exercise
may not address the intricacies of all the issues on the
best quality standards or how to get there in a particular
design office environment, Ellicott Heights attempts to
address all of them, at least peripherally, in its execution.
4.1.1 Project Template
A project template file was established from the very
beginning using VectorWorks Architect’s built-in
standards, with some customization.
NNA2008_01>Resources>NNA2008_01-Template.vwx
This file was initially created using the VectorWorks
“Architect (Imperial).sta” stationery, then invoking the
following ‘File>Document Settings>...’ menu
commands:
1) Document Setup... - initializing drawing units,
general design layer scale, page size (a.k.a.
drawing area) and drawing grids. Note: Don’t
create a Drawing Border/Title Block at this point!
Wait until ‘Create Standard Viewports…’.
2) Standard Naming… - Ellicott Heights uses the
default ‘VWArch’ and Auto-classing is enabled.
But the command gives the user many options and
controls over how classes, design layers, sheet
layers, viewports and saved views are
automatically named when various commands and
tools and invoked
BIM Demonstration Project #2
3) Model Setup… - Model Setup was initially used to All external references, to the various level plans, ramps,
create an ‘outline’ of the building story/layer units and the proposed site model, in the file:
organization. After running ‘Create Standard
NNA2008_01>Site>Building Model.vwx
Viewports…’ further customization was done to
add the ‘Mod-?-?-RAMP’ layers are set to ‘relative’, allowing them to remain
‘connected’ as long as the entire project folder is kept
4) Create Standard Viewports… - The command intact, as shown, no matter where it is located.
name is a bit misleading because of how much
more it does beyond creating viewports. As it sets
up sheet layers/drawings it also populates the class
list with classes it assumes will be needed for the
information displayed in each drawing. This is
very useful in creating a comprehensive list of
standard classes upfront, rather than negotiating
class names on-the-fly. It also helps set up sheet
layers/drawings with a drawing border/title block
and allows you to specify drawings scales for
particular views. Again, further manual
customization was undertaken after this command
was invoked to accommodate the added
complexity of this particular project.
Once this template, and all its customization, was
completed, it was copied and renamed, as needed, to
start each new piece of the BIM that required its own
file. These files were then redacted, their class and layer
structure edited, to accommodate the different extents of
data in each BIM file.
The template also serves as a repository for the shared
resources of the project (e.g. symbols, textures, hatches,
wall styles) by using the new ‘Export’ functionality of
the resource browser from each file and reconciling the
resources throughout the rest of the project through
similar push/pull techniques.
4.1.2 Project File/Folder Data Organization
As discussed above, in section 3.2 Project Model Data
Structure, the project is distributed among several
different data files, imitating the workflow of a project
team. The hierarchy of the project folder is set to group
the building, site and miscellaneous resources in a way
to easily navigate from a general data management point
of view, as well as efficiently utilizing functionality,
Figure 03: Project folder, sub-folder and file structure
such as referencing, within VectorWorks.
NNA2008.01- Ellicott Heights 10 of 14
VectorWorks BIM in Practice Series
4.2 Preliminary/Schematic Design BIM
Though not exhaustive, the preliminary and schematic
design materials are intended to be representative of the
materials an architect may present to the client early in
the design process.
4.2.1 Site GIS Data
The site data was procured from the Howard County
Department of Technology & Communication Services,
Geographic Information Systems (GIS) Division.
The files were available in either an AutoCAD
compatible DXF or ArcGIS .SHP format. In this case,
the information was obtained in the .SHP format. All the
geographically relevant GIS data files were imported
into a blank file (a 481.7 MB file) and then extraneous
data cropped from around the proposed site. The raw
information was then edited (e.g. deletion or trimming
of objects, creation of continuous contour polylines) and
reformatted (e.g. re-assignment of classes and class
attributes to objects) for further use.
NNA2008_01>Site>Existing_Site_Model.vwx
The file was created as a starting point for all subsequent
branches of digital site modeling and preliminary design
iterations.
4.2.2 Conceptual Drawing
Even in the transition to a 3D workflow, the value of 2D
drawing is not diminished. Drawing/sketching is a
viable means of thinking about design. And this
drawing/thinking shouldn’t be divorced from the BIM
process, it should be an integral part of it. Traditionally,
architects approach a design problem by quickly
working out ideas from what they know about the site
and the program. Most often, this thinking is done in a
media or format that is not integrated directly with the
rest of the digital workflow. Yet, key to the discussion
and definition of BIM, is the integration of ALL
knowledge of the project, from beginning concept to
final occupation, or even demolition.
BIM Demonstration Project #2
Building Section existing site conditions and analysis information. Next, a
schematic design model file was created to work out
A drawing/thinking exercise in the design of this project
design concepts in 3D, merging schematic building
included a preliminary concept sketch of the section of
ideas with possible site development strategies.
the building. The following concept sketch was created
as a purely 2D drawing, with little detail: NNA2008_01>Site>SD_Site_Model.vwx
NNA2008_01>Resources>section_sketch_01.vwx This file uses the design layer viewport functionality
introduced in VectorWorks 2008 to meld the 3D site
The purpose of the sketch was to work out spatial and
with the conceptual building massing model. Some
structural ideas and relationships without dedicating
rough ideas about building location and grading were
time in a full-scale model. It is used, in conjunction with
determined using Site Modifier objects. After a site
the existing site model and site analysis diagrams, to
design concept was firmly established in 3D, this file
develop the first conceptual digital 3D models, as well
was spun off as the Design Development/Construction
as the further development of the BIM. Over time, as
Document model.
ideas and the model were developed, further revisions of
this sketch were created (…_02 & …_03) until the last
Building Massing Model
2D sketch:
Using the Massing Model object, a 3D concept model of
NNA2008_01>Resources>section_sketch_04.vwx
the building was created in the following file:
At this point, the concept was solidified and the “live”
NNA2008_01>Site>Building Massing Model.vwx
sections through the model dominated any further
development, details and coordination. Different Massing Model objects represent different
programmatic elements. Some of these objects are
Unit Plans multi-story. These different functions are colored
Simultaneously, residential unit plan concepts were differently for immediate recognition in the 3D model
and various 2D views.
started by using polygons and VectorWorks space
objects to define possible layouts and geometries based A database worksheet was then created to quantify the
on parameters considered in the section sketch and areas of the various programmatic elements.
general structural design strategies (e.g. cast-in-place
reinforced concrete vs. steel framing and structural bay
sizes). Then, the units were developed in more detail
with walls and various architectural objects as the
building shell was designed.
4.2.3 Conceptual Modeling
After establishing the relevant site data set and the
general building design parameters in 2D, 3D models of
the site and building concepts were more thoroughly
developed.
Preliminary DTM
The 2D information imported and edited in the existing
site file was converted into a 3D site model using the
Digital Terrain Model tools. This file maintains all
NNA2008.01- Ellicott Heights 11 of 14
VectorWorks BIM in Practice Series
4.3 Design Development BIM
The data and models from the preliminary and
schematic design phases were then culled and relevant
data copied into a new branch of files that became the
Design Development model and drawings.
4.3.1 Site Model
The preliminary DTM was copied and further developed
with more detail as the building model also received
more detail. The project’s proposed site development
data is located in the following file:
NNA2008_01>Site>Proposed_Site_Model.vwx
Prior to its current state, being referenced into the
building model file, this file contained a reference of the
first three stories of the building model to reconcile the
details of the site around the building.
The site model is composed of the following five (5)
layers which delineate the different data used to either
modify the DTM directly, or add 2D and/or 3D data to
describe the additional site improvements outside the
extents of the building model:
• Mod-Site-Landscape - Objects such as the
monument sign and flagpoles that are placed in the
landscape, but don’t directly modify the DTM or
are detached from the building;
• Mod-Site-Arch - Sidewalks and walls that are
directly adjacent or ‘attached’ to the building;
• Mod-Site-Civil - Driveways and parking lots,
property lines and easement lines
• Mod-Site-DTMdata - The DTM itself and all Site
Modifier objects that directly act upon the DTM;
• Mod-Guidelines - Miscellaneous line work used as
guides for layout/alignment.
With the exception of ‘Mod-Guidelines’ all layers are
referenced into the building model file.
4.3.2 Building Model
As discussed earlier in section 3 Designing the BIM,
there are many factors influencing how the data of the
BIM Demonstration Project #2
building model is distributed to most efficiently get the
information into the BIM from a team. In addition, their
is a need for team members to be able to coordinate the
data/geometry they may be working on with other pieces
of data in the hands of other team members. Finally,
there is the need to assemble all this data into a
comprehensive model from which geometric views (e.g.
floor plans, elevations, sections) and data reports (e.g.
door, window and room schedules, area calculations).
The entire set of data contained in the project folder
NNA2008_01 can be seen as the BIM. All the geometry
and data needed to describe the intent of the project are a
sum of the contents of all the files. But a mechanism is
needed to intertwine this geometry and data and
assemble it in a useful way.
VectorWorks provides a mechanism for sharing data
through the use of Workgroup Referencing (WGR); the
dynamic and persistent linking/import of data from
external files into another document. VW2008 enhances
this capability through the new technology of Design
Layer Viewports (DLVPs). DLVPs combine the external
referencing power of Workgroup Referencing (now with
‘true’ referencing) with the internal geometry linking
power of Layers Links and the flexibility and instancing
power of Symbols.
The Ellicott Heights project make very extensive use of
DLVPs to create a centralized point from which all the
BIM data can be reviewed, coordinated, scheduled/
counted and displayed. The following file is the
collection point for all the project data input:
NNA2008_01>Building>Building_Model.vwx
BIM Data Structure - Level I
The organizational structure of the BIM can be thought
of as a a tree or web of referenced links into this main
file (See Figure 03, page 15) using the following files/
data sets:
1)A single file for each of the parking ramps, containing
all levels/stories for each:
NNA2008_01>Building>Ramp_A.vwx
NNA2008_01>Building>Ramp_B.vwx
NNA2008.01- Ellicott Heights
2)A single file for each of the levels/stories of the main
building:
NNA2008_01>Building>...
...>Level_Plans>Level-B1_Basement.vwx
...>Level_Plans>Level-1_Retail.vwx
...>Level_Plans>Level-2_Main.vwx
...>Level_Plans>Level-3_4_5_Typ_Residential.vwx
...>Level_Plans>Level-6_Penthouse.vwx
...>Level_Plans>Level-7_Penthouse.vwx
...>Level_Plans>Level-8_Roof-1.vwx
...>Level_Plans>Level-9_Roof-2.vwx
3)A single file containing all the residential units:
NNA2008_01>Building>Unit_Plans.vwx
4)A single file for the structural grid:
NNA2008_01>Building>...
...>Level_Plans>Building_Structural_Grid.vwx
5)And, as explained earlier, a single file containing the
site model:
NNA2008_01>Site>Proposed_Site_Model.vwx
The information from each of these files is then
referenced into the main building model file for the
creation of dependent views/schedules and final output.
BIM Data Structure - Level II
Each level/story contains the following layer structure:
• Mod-Floor-x - Contains all explicitly architectural
data/geometry (e.g. non-structural walls, doors,
windows, railings, stairs, etc);
• Mod-MEP-x - Available for mechanical/electrical/
plumbing consultant data to be imported, as
necessary;
• Mod-Slab-x - Contains all explicitly structural data/
geometry (e.g. slabs/decks, columns, beams, joists,
structural walls, etc.)
12 of 14
VectorWorks BIM in Practice Series

Every file contains a guide/reference layer:

• Mod-Guidelines - Contains an external DLVP to the
Building_Structural_Grid.vwx file and any other
external references needed for coordination (e.g.
level above and/or level below);
The unit plans/models only contain one ‘Mod-Floor-x‘
layer per unit because they are essentially an ‘infill’ into
the surrounding system of structure, corridor and party
walls. The ‘Mod-MEP-x‘ layers for each unit could be
added.
As seen in Figure 03, each layer of each of the level
plans is referenced in separately. Each layer of each
level in the ramp files is also referenced in separately.
Such a DLVP setup gives the user more control over
different model views in the drawings and schedules.
For example, one could setup a saved view that was a
“structural” model by making only the ‘Mod-Slab-x’
layers visible.

4.3.3 Drawings

Schematic Design Drawings

The schematic design drawings are sheet layers in the
file:
NNA2008_01>Site>SD_Site_Model.vwx

Schematic Design Drawing List:

A001 – Project/Site Plan
A002 – Building Plans
A003 – Building Elevations & Sections
A004 – Building Elevations & Sections
A005 – Model Views & Renderings

Design Development Drawings

The design development drawings (future construction
documents) are sheet layers in the main BIM file:
NNA2008_01>Building>Building_Model.vwx

Figure 04: BIM file and layer reference diagram

BIM Demonstration Project #2 NNA2008.01- Ellicott Heights 13 of 14
VectorWorks BIM in Practice Series

Design Development Drawing List: A181 – Level 7a-Residential Penthouse 2 Plan

A182 – Level 7b-Residential Penthouse 2 Plan
Site Plan (1”=50’-0”)
A183 – Level 7c-Residential Penthouse 2 Plan
A011 – Design Development Site Plan A184 – Level 7d-Residential Penthouse 2 Plan
Building Plans (1/32”=1’-0”) A191 – Level Ra-Roof Plan
A192 – Level Rb- Roof Plan
A101 – Level B1-Basement Plan
A193 – Level Rc- Roof Plan
A102 – Level 1-Retail Plan
A103 – Level 2-Main Plan A194 – Level Rd- Roof Plan
A104 – Level 3-Residential 1 Plan Building Elevations (1/32”=1’-0”)
A105 – Level 4-Residential 2 Plan A201 – Building Elevations
A106 – Level 5-Residential 3 Plan A202 – Building Elevations
A107 – Level 6-Residential Penthouse Plan
A108 – Level 7-Residential Penthouse 2 Plan Enlarged Partial Building Elevations (3/32”=1’-0”)
A109 – Level R-Roof Plan A211 – Enlarged Building Elevations
A212 – Enlarged Building Elevations
Enlarged Partial Building Plans (3/32”=1’-0”)
A213 – Enlarged Building Elevations
A111 – Level B1a-Basement Plan A214 – Enlarged Building Elevations
A112 – Level B1b-Basement Plan A215 – Enlarged Building Elevations
A113 – Level B1c-Basement Plan A216 – Enlarged Building Elevations
A114 – Level B1d-Basement Plan
A121 – Level 1a-Retail Plan Building Sections (3/32”=1’-0”)
A122 – Level 1b-Retail Plan A301 – Building Sections
A123 – Level 1c-Retail Plan A302 – Building Sections
A124 – Level 1d-Retail Plan A303 – Building Sections
A131 – Level 2a-Main Plan A304 – Building Sections
A132 – Level 2b-Main Plan A305 – Building Sections
A133 – Level 2c-Main Plan A306 – Building Sections
A134 – Level 2d-Main Plan Unit Plans/Interior Elevations (3/32”=1’-0”)
A141 – Level 3a-Residential 1 Plan
A401 – Unit Types ‘A’, ‘B’ & ‘C’
A142 – Level 3b-Residential 1 Plan
A402 – Unit Type ‘D’ (Penthouse)
A143 – Level 3c-Residential 1 Plan
A144 – Level 3d-Residential 1 Plan
A501 – Door Schedule
A151 – Level 4a-Residential 2 Plan
A152 – Level 4b-Residential 2 Plan
A153 – Level 4c-Residential 2 Plan
A154 – Level 4d-Residential 2 Plan
A161 – Level 5a-Residential 3 Plan
A162 – Level 5b-Residential 3 Plan
A163 – Level 5c-Residential 3 Plan
A164 – Level 5d-Residential 3 Plan
A171 – Level 6a-Residential Penthouse 1 Plan
A172 – Level 6b-Residential Penthouse 1 Plan
A173 – Level 6c-Residential Penthouse 1 Plan
A174 – Level 6d-Residential Penthouse 1 Plan

BIM Demonstration Project #2 NNA2008.01- Ellicott Heights 14 of 14