This document expands on key questions regarding the transfer of skills between different Computer-Aided Design (CAD) and Building Information Modeling (BIM) programs, focusing particularly on how each platform organizes project information and manages sheet output.1. Transferable Skills: The Foundation Beyond the Interface.
When transitioning to a new CAD/BIM program (e.g., moving from Archicad to Revit, Vectorworks, or Chief Architect), what fundamental skills remain applicable?
Core Drafting and Design Principles: The understanding of architectural drawing standards, orthographic projection (plans, sections, elevations), dimensioning techniques, and annotation standards are universally applicable. Knowing why a detail is needed and what information it conveys transcends specific software.
BIM Methodology (If Applicable): If you are moving between two BIM programs (e.g., Archicad to Revit or Vectorworks), the concept of modeling elements rather than lines, utilizing parametric objects, managing schedules/quantities, and understanding the project lifecycle integration remains essential.
Spatial Reasoning and Visualization: The ability to mentally manipulate 3D space, interpret 2D plans, and visualize the final structure is independent of the software tool.
Documentation Workflow: Understanding the process of setting up a drawing set, linking views to sheets, managing revisions, and publishing deliverables (PDFs, DWGs) is a valuable process skill, even if the tools and terminology change.
Understanding Data Structure: Recognizing the importance of classification, naming conventions, and utilizing object data (properties/attributes) for scheduling and reporting is a transferable concept, even if the specific implementation (layers, categories, classes) differs.
The core concept remains consistent across all platforms: separate the creation environment (Model Space/Design Layers/Model) from the documentation environment (Paper Space/Layouts/Sheets). The ability to manage this separation and link dynamic model views to static output sheets is the critical transferable skill.
Archicad | Chief Architect | Revit | Vectorworks | AutoCAD | Focus |
Layers | Layers (Used for visibility and control of object types, similar to Archicad/AutoCAD) | Categories and Subcategories (e.g., Walls, Doors, Plumbing Fixtures). Visibility/graphics are controlled by filters and view templates. | Classes (Controls graphical attributes, visibility, and 2D/3D representation) | Layers (Primary mechanism for organizing geometry, controlling color, linetype, and plot style) | Core separation of elements (Architectural, Structural, MEP, Annotation, etc.) |
Elements (Objects, Walls, Slabs) are assigned to a single Layer. | Objects are assigned to layers based on their type (e.g., Cabinets are on the 'Cabinets' layer). | System/Component Families (The parametric definition of an object) are bound to their respective Category. | Objects (Objects, Walls, Slabs) are assigned to a single Layer. | Model Space (objects) | Grouping and controlling display attributes |
Layer Combinations (Sets of visible/hidden layers for specific views) | Layer Sets (Predefined combinations of visible/hidden layers) | View Templates (Controls Categories, Filters, Link settings, and more for a specific view) | Viewports and Saved Views linked to Design Layers and filtered by Classes | Viewports in Paper Space are linked to Model Space layers | View-specific control |
Output Management: Structuring the Deliverable Set
How do different programs organize the final documentation set, linking 3D/2D model views to printable sheets?
Archicad | Chief Architect | Revit | Vectorworks | AutoCAD | Function |
Layouts | Layouts | Sheets | Sheet Layers | Paper Space/Layouts | The printable sheet (Contains title block, revision history, and linked views) |
Drawings (Linked views from the Model/View Map placed onto Layouts) | CAD Details/Views (Views from the model, or 2D details, placed onto Layouts) | Views (Plans, Sections, Details, Schedules, 3D Views) placed onto Sheets | Viewports (Linked views from Design Layers placed onto Sheet Layers) | Viewports (Frames defining a view of Model Space placed onto Paper Space) | The container for model views |
Publisher Sets (Manages output settings for an entire set of Layouts) | Print/Export Tools (Directly manages the output of Layouts) | Print Settings/Sheet Sets (Manages batch printing/exporting of Sheets) | Publish Command (Manages batch printing/exporting of Sheet Layers) | Plot/Publish Command, Sheet Set Manager (.dst) | Batch printing and organization |
The core concept remains consistent across all platforms: separate the creation environment (Model Space/Design Layers/Model) from the documentation environment (Paper Space/Layouts/Sheets). The ability to manage this separation and link dynamic model views to static output sheets is the critical transferable skill.
No comments:
Post a Comment