| 3.1. |
Requirements
for space planning and programming: |
|
3.1.1. |
Live
interface between the architectural program and the graphic
representation |
|
|
3.1.1.1. |
Ability
to quickly compare the areas assigned in a proposed layout
to the program requirements |
|
|
3.1.1.2. |
Ability
to visualize those areas through automated color coding |
|
|
3.1.1.3. |
Ability
to analyze and visualize adjacencies |
|
|
|
3.1.1.3.1. |
Horizontal
adjacencies |
|
|
|
3.1.1.3.2. |
Vertical
adjacencies |
| |
|
| 3.2. |
Requirements
for architectural design: |
|
3.2.1. |
Ability
to begin with generic components, then refine and substitute |
|
3.2.2. |
Ability
to start with complex abstract forms, transform them into building
elements: roofs, curtain walls, etc., and resolve constructibility
issues |
|
3.2.3. |
Ability
to explore elements of the design without committing |
|
3.2.4. |
Ability
to store sketch models and submodels, then accept or reject
them |
|
3.2.5. |
Ability
to pull details and intelligent product templates from vendor
Web sites |
|
3.2.6. |
Automated
functions to evaluate these alternative components and products
in terms of: |
|
|
3.2.6.1. |
Fit |
|
|
3.2.6.2. |
Performance |
|
|
3.2.6.3. |
Code
compliance |
|
|
3.2.6.4. |
Cost |
| |
|
| 3.3. |
Requirements
for engineering design: |
|
3.3.1. |
Two-way
interfaces with engineering design and analysis programs that
use and create building geometry and properties |
|
|
3.3.1.1. |
Structural |
|
|
|
3.3.1.1.1. |
RAM
Analysis |
|
|
|
3.3.1.1.2. |
SAFE |
|
|
|
3.3.1.1.3. |
STAAD-3 |
|
|
|
3.3.1.1.4. |
ADOSS |
|
|
|
3.3.1.1.5. |
RISA-3D |
|
|
3.3.1.2. |
Energy
analysis |
|
|
|
3.3.1.2.1. |
DOE
2 |
|
|
|
3.3.1.2.2. |
Visual
DOE |
|
|
3.3.1.3. |
Lighting |
|
|
|
3.3.1.3.1. |
Radiance |
|
3.3.2. |
Analysis
results, once accepted by the engineers, should automatically
update the model |
| |
|
| 3.4. |
Requirements
for design control |
|
3.4.1. |
Ability
to lock in design intent |
|
3.4.2. |
Ability
to lock out changes on specific components |
| |
|
| 3.5. |
Requirements
for cross-document and inter-disciplinary coordination |
|
3.5.1. |
Automate
production of a fully coordinated set of documents from the
design model |
|
3.5.2. |
If
an error is detected at plot time, ability to quickly correct
the "drawing" and have that correction reflected
in all representations of the model |
|
3.5.3. |
Interferences
between building systems is where all the rework occurs—the
model must accommodate all disciplines, in this order of importance: |
|
|
3.5.3.1. |
Structural |
|
|
3.5.3.2. |
Mechanical |
|
|
3.5.3.3. |
Technical
equipment and process piping |
|
|
3.5.3.4. |
Electrical/
telecom |
|
3.5.4. |
Automate
interference detection between all building systems and components;
visual inspection is not sufficient |
|
3.5.5. |
Interface
with Civil/ Site is required |
|
|
3.5.5.1. |
Ability
to register the building with the site |
|
|
3.5.5.2. |
Ability
to supply a building footprint to Civil for use in earthwork
calculations |
| |
|
| 3.6. |
Requirements
for basic life safety and code checking |
|
3.6.1. |
Fire
ratings enforced in all subcomponents of a fire-rated assembly |
|
3.6.2. |
Automatic
calculation of exiting distances |
|
3.6.3. |
Links
to model codes, for look-up |
|
3.6.4. |
Embed
model codes |
|
|
3.6.4.1. |
Automate
fire separation between specific occupancies, based on code |
|
|
3.6.4.2. |
Provide
checklists on code conformance |
