E-Book_Allplan 2012 Practical Manual

Allplan 2012

Practical Manual

Markus Philipp

Translated by: Steve Martin/linguists.com. Steve Martin has been specializing in IT and software trans lations

since 1992. He is also the founder of linguists.com, a network of experienced and professional translators

throughout Europe.

Originally published in German under the title Praxishandbuch Allplan 2012

ISBN 978-3-446-43036-5

Copyright © 2012

Carl Hanser Verlag, München

All rights reserved.

Authorised translation from the original German language edition published by Carl Hanser Verlag, München

English translation copyright © NEMETSCHEK Allplan GmbH, München

Cover concept: Marc Müller-Bremer, www.rebranding.de, München

Cover design: Stephan Rönigk

Contents

Introduction

... XI

1

_{General information}

... 1

1.1 Allplan 2012 product family

... 1

1.2 Installing Allplan

... 2

1.2.1 Hardware requirements ... 2

1.2.2 Operating systems ... 2

1.2.3 Installation types ... 3

1.2.4 System paths for Allplan ... 4

1.2.5 First-time installation of Allplan 2012 ... 5

1.2.6 Installation as upgrade ... 5

1.2.7 Installation of updates ... 5

1.2.8 Allplan and Services program launch ... 5

1.3 Updating Allplan – Allplan Update

... 6

1.4 Working with the Allplan 2012 Practical Manual

... 7

1.4.1 Structure of the following chapters ... 8

1.4.2 Data relating to the guide ... 9

2

_{An Introduction to Allplan 2012}

... 13

2.1 The project-based approach

... 13

2.1.1 Drawing files, layouts ... 13

2.1.2 Administration files ... 14

2.1.3 Resources (office or project) ... 15

2.1.4 Special resources ... 15

2.1.5 Settings

... 16

2.2 The document-based approach

... 16

Inhalt General information ... 1

1.1 Allplan 2012 product family ... 1

1.2 Installing Allplan ... 2

1.2.1 Hardware requirements... 2

1.2.2 Operating systems ... 2

1.2.3 Installation types... 3

1.2.4 System paths for Allplan ... 4

1.2.5 First-time installation of Allplan 2012 ... 5

1.2.6 Installation as upgrade... 5

1.2.7 Installation of updates ... 5

1.2.8 ...Allplan and Services program launch 5 1.3 Updating Allplan – Allplan Update ... 6

1.4  Working with the Allplan 2012 Practical Manual... 7

1.4.1 Structure of the following chapters ... 8

1.4.1.1 Subsections of the example 8 1.4.1.2 Typographic conventions in examples and explanations 8 1.4.2 Data relating to the guide... 9

1.4.2.1 Obtaining the data 9 1.4.2.2 Installing the data 9 1.4.2.3 Installed files and folders 9 An Introduction to Allplan 2012 ... 13

2.1 The project-based approach... 13

2.1.1 Drawing files, layouts... 13

2.1.2 Administration files ... 14

2.1.3 Resources (office or project) ... 15

2.1.4 Special resources ... 15

2.1.5 Settings ... 16

2.2 The document-based approach... 16

2.3 Dialog boxes for data organization ... 17

2.3.1 Open project ... 17

2.3.2 Open on a project-specific basis ... 19

2.3.3 Open on a project-specific basis: Drawing files... 20

2.3.3.1 Tools in both tabs 20 2.3.3.2 Drawing file status – Drawing file IDs 21 2.3.3.3 Fileset Structure tab 22 2.3.3.4 Building structure tab 24 2.3.3.5 Application tips for the building structure 32 2.3.4 Open on a project-specific basis: layouts ... 32

2.3.5 Open on a project-specific basis – select and move ... 36

2.3.6 Open – custom NDW ... 37

2.3.7 Open – custom layout ... 38

2.3.8 Select destination drawing file and related dialog boxes ... 38

2.3.9 Saving documents ... 39

2.3.9.1 Saving project-specific data 39 2.3.9.2 Saving file-specific data 40 2.3.10 Restoring files using *.bak files ... 40

2.4 Copying between files ... 41

2.4.1 Copying within the building structure ... 41

2.4.2 Copying within the layout structure ... 42

2.4.3 Moving/copying elements between documents ... 43

2.4.4 Copying using the Clipboard ... 44

2.4.5 Copying within a drawing file/layout ... 45

2.5 Storage locations and other data types... 45

2.5.1 Predefined storage locations ... 45

2.5.2 General storage locations ... 46

2.5.3 Favorites ... 47

2.6 ProjectPilot – data management ... 48

2.6.1 ProjectPilot interface ... 48

2.6.2 Tree structure ... 49

2.6.3 Where to find which data type – overview table ... 50

2.6.4 Using ProjectPilot ... 51

2.7 The Allplan Interface ... 51

2.7.1 Icons – cross-module similarities... 52

2.7.2 Allplan program interface... 53

2.7.2.1 User interface fundamentals 53 2.7.2.2 Palettes 54 2.7.2.3 Toolbars 56 2.7.2.4 Predefined user interface configurations 56 2.7.2.5 Downstream functions in dialog boxes 58 2.7.3 Viewports – workspace ... 58

2.7.3.1 Design viewport 60 2.7.3.2 Animation window 61

2.7.4 Display in the design and animation windows ... 63

2.7.5 Display in layout window ... 65

2.8  Adapting the interface to your own requirements... 66

2.8.1 Toolbars and shortcut keys... 66

2.8.2 Positioning toolbars and palettes... 67

2.8.3 Wizards ... 68

2.9 User entries ... 69

2.9.1 Making entries with the keyboard ... 69

2.9.2 Making entries using the mouse – mouse button assignments... 69

2.9.2.1 No tool active 70 2.9.2.2 Design tool active – point snap active 71 2.9.2.3 Edit tool is active 72 2.9.2.4 Navigating with the sphere and camera navigation mode 73 2.9.3 Activating and exiting tools ... 74

2.9.3.1 Activating a tool 74 2.9.3.2 Queries within the tool 74 2.9.3.3 Exiting tools 75 2.9.4 Undo and redo ... 75

2.10  Working with elements (and components) ... 75

2.10.1 Properties of elements ... 75

2.10.1.1 Format properties 75 2.10.1.2 Other element/component properties 77 2.10.2 Creating elements... 78

2.10.2.1 Point elements – drop-in point/reference point 78 2.10.2.2 Line elements – linear input 78 2.10.2.3 Surface elements – polygonal entries 79 2.10.3 Working with existing elements ... 81

2.10.3.1 Modifying elements 82 2.10.3.2 Edit toolbar 83 2.10.4 Selecting elements ... 84

2.10.4.1 Selection rectangle 84 2.10.4.2 Brackets 85 2.10.4.3 Activating with filters 85 2.11 Design tools ... 87

2.11.1 Input fields and symbols in the dialog line ... 87

2.11.2 Shortcut menu for the Point wizard... 89

2.11.3 Point snap... 91

2.11.4 Point snap options... 91

2.11.5 Track tracing ... 92

2.11.6 Examples of use for point snap – initial design ... 94

2.11.6.1 Point at an offset from an existing point 94 2.11.6.2 Point on an element at offset from end point 94 2.11.6.3 Define virtual point of intersection as point 95 2.11.6.4 Line in the shape of a rectangle 96 2.12 The Allplan plane model ... 96

2.12.1 Plane – basic terms... 97

2.12.2 The Floor Manager ... 98

2.12.3 Assigning planes to drawing files ... 100

2.13 Layers – the special property ... 102

2.13.1 Definition of terms ... 102

2.13.2 Drawing files ↔ layers? ... 103

2.13.3 Tools and settings ... 104

2.14  Display in the design and animation windows... 107

2.14.1 Displayed drawing files ... 107

2.14.2 Visible layers... 108

2.14.3 Functions for the screen display ... 109

2.14.4 Reference scale and drawing type ... 110

2.15 Display in layout window ... 111

Basic settings ... 113

3.1 Options... 113

3.1.1 Using the Options dialog box ... 114

3.1.2 Settings and explanations on options ... 115

3.1.2.1 Desktop environment options 115 3.1.2.2 Mouse and crosshairs options 116 3.1.2.3 Selection options 117 3.1.2.4 Catalog options 117 3.1.2.5 Component options 119 3.1.2.6 Rooms options 120 3.2 Additional basic settings ... 121

3.2.1 Building structure/fileset structure, layout structure... 121

3.2.2 Office-specific modification... 121

3.2.3 Share project attributes ... 122

3.2.4 Settings for layers... 123

Project start to site plan ... 125

4.1 Create a project – project properties... 125

4.1.1 New project . . . ... 125

4.1.2 Copy project ... 127

4.1.3 Project settings... 128

4.1.3.1 Rename project 128 4.1.3.2 Properties 128 4.1.4 Example – copy project template... 130

4.2  Create project structure – create plane model ... 131

4.2.1 Structure project – fundamentals... 131

4.2.2 Edit drawing files – fundamentals ... 132

4.2.3 Fileset structure – fundamentals ... 132

4.2.4 Building structure – fundamentals ... 132

4.2.5 Example – project structure and plane settings ... 135

4.2.6 Example – assigning drawing file names ... 137

4.3 Insert site plan as scanned image ... 139

4.3.1 Scan – fundamentals ... 139

4.3.2 Scanned image – check size ... 140

4.3.3 Example – Link site plan with scanned image ... 141

4.4 Prepare site plan ... 142

4.4.1 Draft module – fundamentals ... 142

4.4.2 Additional drafting tools ... 146

4.4.3 Advanced Draft module... 149

4.4.4 Text module – fundamentals ... 150

4.4.5 Additional text functions ... 153

4.4.6 Dimension Lines module – fundamentals ... 154

4.4.7 Additional dimension line tools... 158

4.4.8 Example – redrawing a site plan ... 159

4.5 Data exchange: importing/exporting ... 171

4.5.1 Import and export ... 171

4.5.1.1 DWG, DXF, DGN and other data types 172 4.5.1.2 PDF files 175 4.5.1.3 IFC files 175 4.5.1.4 3D graphics files 176 4.5.1.5 Allplan BCM – data exchange with the TAI system 177 4.5.1.6 Exchanging Allplan data (import/export) 177 4.5.2 XRefs and custom XRefs ... 178

4.5.3 Importing site plans as DXF files ... 179

4.5.4 Example – extending the building structure ... 180

4.5.5 Example – Importing site plan data, XRef... 182

4.5.6 Example – importing a site plan from construction stage I ... 186

4.5.7 Example – Aligning a site plan ... 187

4.5.8 Example – result of site plan ... 190

Building model – unfinished structure... 191

5.1 Architectural components – fundamentals... 191

5.1.1 Height association of components... 191

5.1.2 Format properties ... 193

5.1.3 Surface elements... 194

5.1.4 Surface (animation)– preview window... 194

5.1.5 Material and further attributes... 194

5.1.6 Modifying properties of components ... 195

5.2 Walls and other linear components ... 198

5.2.1 Linear components – fundamentals... 198

5.2.1.1 General properties of linear components 198 5.2.1.2 Wall, profile wall, beam, strip foundation linear components 200 5.2.2 Editing linear components... 201

5.2.3 Example – lower floor walls ... 202

5.3 Windows, doors and other openings... 207

5.3.1 Openings in linear components – fundamentals... 207

5.3.1.1 Entering openings 207 5.3.1.2 General properties of openings 208 5.3.1.3 Properties for doors, windows and corner windows 209 5.3.1.4 Properties for niche, recess, slit (including polygonal) 211 5.3.2 Example – lower floor interior doors ... 212

5.3.3 Example – lower floor exterior doors ... 215

5.3.4 Example – lower floor windows ... 217

5.3.5  Example – copy lower floor as template for basement and top floor ... 219

5.4 Using the default planes ... 220

5.4.1 Assign planes... 221

5.4.1.1 Assigning planes via the building structure 222 5.4.1.2 Assigning planes via List default planes 222 5.4.2 Example – assigning planes... 223

5.4.3  Example – change component properties – basement and top floor ... 224

5.4.4 Example – changing floor heights ... 228

5.5  Roofscape, roof plane, custom pair of planes ... 229

5.5.1 Special planes ... 229

5.5.1.1 Custom planes 229 5.5.1.2 Roof plane and dormer window 230

5.5.2 Modify special planes ... 233

5.5.3 Roofscape ... 233

5.5.4 Example – create roof plane... 235

5.5.5 Example – including roofscape in plane model ... 237

5.6 Further architectural components... 239

5.6.1 Slab and other area components... 239

5.6.1.1 Slab and slab foundation 239 5.6.1.2 Roof covering 240 5.6.2 Openings in area components... 242

5.6.2.1 Recess and opening 242 5.6.2.2 Skylight 243 5.6.3 Column and other symbol components ... 244

5.6.4 Miscellaneous architectural components... 245

5.6.5 Example – slab ... 245

5.6.6 Example – roof covering... 248

5.6.7 Example – floor slab... 250

5.6.8 Example – strip foundations ... 251

5.6.9 Example – columns and roof upstand... 253

5.7 Stairs... 254

5.7.1 Stair components – fundamentals ... 254

5.7.2 Create stair ... 256

5.7.3 Further stair tools ... 258

5.7.4 Displaying the stair across stories ... 259

5.7.5 Example – stair lower floor – upper floor ... 260

5.7.6 Example – stair basement – lower floor ... 264

5.7.7 Example – stair display in the stories... 266

5.8 Dimension building, label components... 268

5.8.1 Dimension walls... 268

5.8.2 Label components ... 269

5.8.3 Example – dimension lower floor ... 270

5.8.4 Example – labeling components ... 273

5.9  Example – building model result – unfinished structure... 275

Building model – finish... 277

6.1  Quantity takeoff: rooms, surfaces, stories ... 277

6.1.1 Rooms, stories, finish specifications – fundamentals... 277

6.1.2 Further room and story functions ... 281

6.1.3 Explanation of the label styles used below ... 281

6.1.3.1 Different behavior of label styles (Standard – Office) 282 6.1.3.2 Label style for rooms 282 6.1.3.3 Label style for stories 283 6.1.3.4 Layer style for room and story group 283 6.1.4 Example – create rooms with finish ... 283

6.1.5 Example – create story... 287

6.1.6 Example – group rooms... 289

6.2  Smart symbols for opening components...290

6.2.1 Opening smart symbols – fundamentals ... 290

6.2.2 Create and edit opening smart symbols ... 292

6.2.2.1 Smart window and door symbols 292 6.2.2.2 Smart window sill symbol 293 6.2.2.3 Further functions for smart opening symbols 294 6.2.2.4 Insert smart symbol in opening – system description 295 6.2.3 Example – change and replace smart window symbols ... 296

6.3 Furniture and equipment elements... 299

6.3.1 Symbol catalogs ... 299

6.3.2 Example – plumbing component ... 301

6.3.3 Example – furniture... 302

6.3.4 Example – add external facilities ... 304

6.4 SmartParts for furniture... 306

6.4.1 Comparison of symbols – smart symbols – SmartParts ... 307

6.4.2 Example – furniture with SmartParts ... 307

6.5 Railing and façade ... 309

6.5.1 Railing ... 309

6.5.1.1 Railing – fundamentals 309 6.5.1.2 Railing – functions 310 6.5.2 Façade ... 311

6.5.3 3D modeling – basic functions ... 313

6.5.4 Example – stair and gallery railing ... 314

6.5.5 Example – façade of the glass structure ... 316

6.6 Example – building model result – finish ... 321

Views, sections, and lists... 323

7.1 Terms and basic functions... 323

7.2 Derived objects – views and sections... 324

7.2.1 Views and sections – building structure... 324

7.2.2 Individual steps for views and sections ... 324

7.2.3 Architectural section... 328

7.2.4 Hidden-line image settings ... 329

7.2.5 Postprocessing of sections and views ... 332

7.2.6 Example – create views... 333

7.2.7 Example – section line ... 335

7.2.8 Example – create sections ... 337

7.2.9 Example – postprocess views and sections ... 338

7.3 Derived objects – lists... 341

7.3.1 Lists and Reports – fundamentals ... 341

7.3.2 Lists – building structure... 342

7.3.3 Select list and settings (BS) ... 343

7.3.4 Selection dialog boxes and settings for reports and lists... 344

7.3.4.1 Selection – reports 344 7.3.4.2 Selection – lists 345 7.3.4.3 Settings for quantity analyses 346 7.3.4.4 Settings for area and room analyses 346 7.3.5 Layout Viewer and Layout Designer... 347

7.3.5.1 Functions in the Report Viewer 348 7.3.5.2 User interaction in selected reports 349 7.3.5.3 Layout Designer 354 7.3.6 Create stack lists... 354

7.3.7 Example – create lists ... 355

7.4  Views, sections, and lists – editing drawing files ... 358

7.4.1 Views, sections ... 358

7.4.2 Lists – special functions in the modules ... 359

7.5  Changes to the model – updating the derived objects... 359

7.5.1 Example – change roof inclination – replace roofscape... 360

7.5.2 Example – update section/view and lists ... 361

7.6 Example – sections and views result ... 362

Data output ... 365

8.1 Layout editor – printing layouts ... 365

8.1.1 Assembling layouts – fundamentals ... 365

8.1.2 Functions for assembling layouts... 366

8.1.3 Example – assembling layouts ... 369

8.1.4 Example – layout structure ... 375

8.1.5 Example – output layout on paper ... 377

8.2 Data output as file ... 380

8.2.1 Archive layouts/data... 381

8.2.2 Example – output layout as PDF file (2D) ... 381

8.2.3 Example – export model, PDF (3D) ... 383

8.2.4 Example – export model, C4D... 383

8.3 Layout output troubleshooting ... 385

8.3.1 Example 1 – layout size with width up to 841 mm... 385

8.3.2 Example 2 – layout size larger than width 841 mm... 385

8.3.3 Example 3 – layout size longer than DIN A0... 386

8.3.4 Example 4 – output of several layouts – with plot profiles ... 386

8.3.5  Example 5 – output of several layouts – plot profile of active layout ... 387

8.3.6 Example 6 – output of reduced layouts... 387

8.3.7 Test plot ... 388

8.4 Example – result of assembling layouts ... 389

Services application ... 391

9.1 Services application – fundamentals ... 391

9.1.1 Utilities ... 391

9.1.2 Data backup ... 392

9.1.3 Configuration ... 392

9.1.4 Service ... 393

9.1.5 Information ... 394

9.2 Services – data backup ... 395

9.2.1 Create project backup ... 395

9.2.2 Import project backup ... 396

SmartParts ... 397

10.1 SmartParts module – basic information ... 397

10.2 Using SmartParts ... 401

10.3 New SmartParts – basic information... 401

10.3.1 Extending the toolbars ... 401

10.3.2 System structure of a SmartPart – script structure... 403

10.3.3 SmartPart Editor interface ... 404

2.3 Dialog boxes for data organization

... 17

2.3.1 Open project ... 17

2.3.2 Open on a project-specific basis ... 19

2.3.3 Open on a project-specific basis: Drawing files ... 20

2.3.4 Open on a project-specific basis: layouts ... 32

2.3.5 Open on a project-specific basis – select and move ... 36

2.3.6 Open – custom NDW ... 37

2.3.7 Open – custom layout ... 38

2.3.8 Select destination drawing file and related dialog boxes ... 38

2.3.9 Saving documents ... 39

2.3.10 Restoring files using *.bak files ... 40

2.4 Copying between files

... 41

2.4.1 Copying within the building structure ... 41

2.4.2 Copying within the layout structure ... 42

2.4.3 Moving/copying elements between documents ... 43

2.4.4 Copying using the Clipboard ... 44

2.4.5 Copying within a drawing file/layout ... 45

2.5 Storage locations and other data types

... 45

2.5.1 Predefined storage locations ... 45

2.5.2 General storage locations ... 46

2.5.3 Favorites ... 47

2.6 ProjectPilot – data management

... 48

2.6.1 ProjectPilot interface ... 48

2.6.2 Tree structure ... 49

2.6.3 Where to find which data type – overview table ... 50

2.6.4 Using ProjectPilot ... 51

2.7 The Allplan Interface

... 51

2.7.1 Icons – cross-module similarities ... 52

2.7.2 Allplan program interface ... 53

2.7.3 Viewports – workspace ... 58

2.7.4 Display in the design and animation windows ... 63

2.7.5 Display in layout window ... 65

2.8 Adapting the interface to your own requirements

... 66

2.8.1 Toolbars and shortcut keys ... 66

2.8.2 Positioning toolbars and palettes ... 67

2.8.3 Wizards

... 68

2.9 User entries

... 69

2.9.1 Making entries with the keyboard ... 69

2.9.2 Making entries using the mouse – mouse button assignments ... 69

2.9.3 Activating and exiting tools ... 74

2.9.4 Undo and redo ... 75

2.10 Working with elements (and components)

... 75

2.10.1 Properties of elements ... 75

Contents 

V

2.10.3 Working with existing elements ... 81

2.10.4 Selecting elements ... 84

2.11 Design tools

... 87

2.11.1 Input fields and symbols in the dialog line ... 87

2.11.2 Shortcut menu for the Point wizard ... 89

2.11.3 Point snap ... 91

2.11.4 Point snap options ... 91

2.11.5 Track tracing ... 92

2.11.6 Examples of use for point snap – initial design ... 94

2.12 The Allplan plane model

... 96

2.12.1 Plane – basic terms ... 97

2.12.2 The Floor Manager ... 98

2.12.3 Assigning planes to drawing files ... 100

2.13 Layers – the special property

... 102

2.13.1 Definition of terms ... 102

2.13.2 Drawing files ↔ layers? ... 103

2.13.3 Tools and settings ... 104

2.14 Display in the design and animation windows

... 107

2.14.1 Displayed drawing files ... 107

2.14.2 Visible layers ... 108

2.14.3 Functions for the screen display ... 109

2.14.4 Reference scale and drawing type ... 110

2.15 Display in layout window

... 111

3

_{Basic settings}

... 113

3.1 Options

... 113

3.1.1 Using the Options dialog box ... 114

3.1.2 Settings and explanations on options ... 115

3.2 Additional basic settings

... 121

3.2.1 Building structure/fileset structure, layout structure ... 121

3.2.2 Office-specific modification ... 121

3.2.3 Share project attributes ... 122

3.2.4 Settings for layers ... 123

4

_{Project start to site plan}

... 125

4.1 Create a project – project properties

... 125

4.1.1 New project . . . ... 125

4.1.2 Copy project ... 127

4.1.3 Project settings ... 128

4.2 Create project structure – create plane model

... 131

4.2.1 Structure project – fundamentals ... 131

4.2.2 Edit drawing files – fundamentals ... 132

4.2.3 Fileset structure – fundamentals ... 132

4.2.4 Building structure – fundamentals ... 132

4.2.5 Example – project structure and plane settings ... 135

4.2.6 Example – assigning drawing file names ... 137

4.3 Insert site plan as scanned image

... 139

4.3.1 Scan – fundamentals ... 139

4.3.2 Scanned image – check size ... 140

4.3.3 Example – Link site plan with scanned image ... 141

4.4 Prepare site plan

... 142

4.4.1 Draft module – fundamentals ... 142

4.4.2 Additional drafting tools ... 146

4.4.3 Advanced Draft module ... 149

4.4.4 Text module – fundamentals ... 150

4.4.5 Additional text functions ... 153

4.4.6 Dimension Lines module – fundamentals ... 154

4.4.7 Additional dimension line tools ... 158

4.4.8 Example – redrawing a site plan ... 159

4.5 Data exchange: importing/exporting

... 171

4.5.1 Import and export ... 171

4.5.2 XRefs and custom XRefs ... 178

4.5.3 Importing site plans as DXF files ... 179

4.5.4 Example – extending the building structure ... 180

4.5.5 Example – Importing site plan data, XRef ... 182

4.5.6 Example – importing a site plan from construction stage I ... 186

4.5.7 Example – Aligning a site plan ... 187

4.5.8 Example – result of site plan ... 190

5

_{Building model – unfinished structure}

... 191

5.1 Architectural components – fundamentals

... 191

5.1.1 Height association of components ... 191

5.1.2 Format properties ... 193

5.1.3 Surface elements ... 194

5.1.4 Surface (animation)– preview window ... 194

5.1.5 Material and further attributes ... 194

5.1.6 Modifying properties of components ... 195

5.2 Walls and other linear components

... 198

5.2.1 Linear components – fundamentals ... 198

5.2.2 Editing linear components ... 201

Contents 

VII

5.3 Windows, doors and other openings

... 207

5.3.1 Openings in linear components – fundamentals ... 207

5.3.2 Example – lower floor interior doors ... 212

5.3.3 Example – lower floor exterior doors ... 215

5.3.4 Example – lower floor windows ... 217

5.3.5 Example – copy lower floor as template for basement and top floor ... 219

5.4 Using the default planes

... 220

5.4.1 Assign planes ... 221

5.4.2 Example – assigning planes ... 223

5.4.3 Example – change component properties – basement and top floor ... 224

5.4.4 Example – changing floor heights ... 228

5.5 Roofscape, roof plane, custom pair of planes

... 229

5.5.1 Special planes ... 229

5.5.2 Modify special planes ... 233

5.5.3 Roofscape

... 233

5.5.4 Example – create roof plane ... 235

5.5.5 Example – including roofscape in plane model ... 237

5.6 Further architectural components

... 239

5.6.1 Slab and other area components ... 239

5.6.2 Openings in area components ... 242

5.6.3 Column and other symbol components ... 244

5.6.4 Miscellaneous architectural components ... 245

5.6.5 Example – slab ... 245

5.6.6 Example – roof covering ... 248

5.6.7 Example – floor slab ... 250

5.6.8 Example – strip foundations ... 251

5.6.9 Example – columns and roof upstand ... 253

5.7 Stairs

... 254

5.7.1 Stair components – fundamentals ... 254

5.7.2 Create stair ... 256

5.7.3 Further stair tools ... 258

5.7.4 Displaying the stair across stories ... 259

5.7.5 Example – stair lower floor – upper floor ... 260

5.7.6 Example – stair basement – lower floor ... 264

5.7.7 Example – stair display in the stories ... 266

5.8 Dimension building, label components

... 268

5.8.1 Dimension walls ... 268

5.8.2 Label components ... 269

5.8.3 Example – dimension lower floor ... 270

5.8.4 Example – labeling components ... 273

6

_{Building model – finish}

... 277

6.1 Quantity takeoff: rooms, surfaces, stories

... 277

6.1.1 Rooms, stories, finish specifications – fundamentals ... 277

6.1.2 Further room and story functions ... 281

6.1.3 Explanation of the label styles used below ... 281

6.1.4 Example – create rooms with finish ... 283

6.1.5 Example – create story ... 287

6.1.6 Example – group rooms ... 289

6.2 Smart symbols for opening components

... 290

6.2.1 Opening smart symbols – fundamentals ... 290

6.2.2 Create and edit opening smart symbols ... 292

6.2.3 Example – change and replace smart window symbols ... 296

6.3 Furniture and equipment elements

... 299

6.3.1 Symbol catalogs ... 299

6.3.2 Example – plumbing component ... 301

6.3.3 Example – furniture ... 302

6.3.4 Example – add external facilities ... 304

6.4 SmartParts for furniture

... 306

6.4.1 Comparison of symbols – smart symbols – SmartParts ... 307

6.4.2 Example – furniture with SmartParts ... 307

6.5 Railing and façade

... 309

6.5.1 Railing

... 309

6.5.2 Façade

... 311

6.5.3 3D modeling – basic functions ... 313

6.5.4 Example – stair and gallery railing ... 314

6.5.5 Example – façade of the glass structure ... 316

6.6 Example – building model result – finish

... 321

7

_{Views, sections, and lists}

... 323

7.1 Terms and basic functions

... 323

7.2 Derived objects – views and sections

... 324

7.2.1 Views and sections – building structure ... 324

7.2.2 Individual steps for views and sections ... 324

7.2.3 Architectural section ... 328

7.2.4 Hidden-line image settings ... 329

7.2.5 Postprocessing of sections and views ... 332

7.2.6 Example – create views ... 333

7.2.7 Example – section line ... 335

7.2.8 Example – create sections ... 337

Contents 

IX

7.3 Derived objects – lists

... 341

7.3.1 Lists and Reports – fundamentals ... 341

7.3.2 Lists – building structure ... 342

7.3.3 Select list and settings (BS) ... 343

7.3.4 Selection dialog boxes and settings for reports and lists ... 344

7.3.5 Layout Viewer and Layout Designer ... 347

7.3.6 Create stack lists ... 354

7.3.7 Example – create lists ... 355

7.4 Views, sections, and lists – editing drawing files

... 358

7.4.1 Views, sections ... 358

7.4.2 Lists – special functions in the modules ... 359

7.5 Changes to the model – updating the derived objects

... 359

7.5.1 Example – change roof inclination – replace roofscape ... 360

7.5.2 Example – update section/view and lists ... 361

7.6 Example – sections and views result

... 362

8

_{Data output}

... 365

8.1 Layout editor – printing layouts

... 365

8.1.1 Assembling layouts – fundamentals ... 365

8.1.2 Functions for assembling layouts ... 366

8.1.3 Example – assembling layouts ... 369

8.1.4 Example – layout structure ... 375

8.1.5 Example – output layout on paper ... 377

8.2 Data output as file

... 380

8.2.1 Archive layouts/data ... 381

8.2.2 Example – output layout as PDF file (2D) ... 381

8.2.3 Example – export model, PDF (3D) ... 383

8.2.4 Example – export model, C4D ... 383

8.3 Layout output troubleshooting

... 385

8.3.1 Example 1 – layout size with width up to 841 mm ... 385

8.3.2 Example 2 – layout size larger than width 841 mm ... 385

8.3.3 Example 3 – layout size longer than DIN A0 ... 386

8.3.4 Example 4 – output of several layouts – with plot profiles ... 386

8.3.5 Example 5 – output of several layouts – plot profile of active layout ... 387

8.3.6 Example 6 – output of reduced layouts ... 387

8.3.7 Test plot ... 388

9

_{Services application}

... 391

9.1 Services application – fundamentals

... 391

9.1.1 Utilities

... 391

9.1.2 Data backup ... 392

9.1.3 Configuration

... 392

9.1.4 Service

... 393

9.1.5 Information

... 394

9.2 Services – data backup

... 395

9.2.1 Create project backup ... 395

9.2.2 Import project backup ... 396

10

_SmartParts

... 397

10.1 SmartParts module – basic information

... 397

10.2 Using SmartParts

... 401

10.3 New SmartParts – basic information

... 401

10.3.1 Extending the toolbars ... 401

10.3.2 System structure of a SmartPart – script structure ... 403

10.3.3 SmartPart Editor interface ... 404

Introduction

With Allplan 2012, the latest update of the 3D planning software from Nemetschek that

has been available since 1984, the future has arrived for intelligent and programmable

objects (SmartParts) and is providing new impetus for work.

Allplan 2012 is an enhancement of the previous version. The latest data versions have

been added to the options for data exchange. The changes to report lists have been

com-pleted in the new version. Most of the reports themselves have new filters and functions

that make it easier to check data.

The biggest innovation is the introduction of the SmartParts module. A SmartPart is an

intelligent object for which predefined processes are carried out, either by dragging

han-dles or changing parameters. As a result, by enlarging a table for example, you can also

change the number of chairs.

The modification of graphical output, the Graphics Engine, which began in Allplan 2011,

has been systematically pursued and improved. As a result, if the graphics boards

recom-mended by the software manufacturer are used, very significant increases in speed can

be achieved for display, and a live hidden-line image is possible.

This guide cannot and is not intended to be a complete documentation of Allplan.

There-fore, in addition to reading this guide as an introduction to Allplan 2012 (for experts and

beginners), I recommend the Allplan help and documentation, and advise you to visit our

websites http://www.nemetschek.de and http://www.allplan-connect.com. These contain

Allplan’s supported user forum. After free-of-charge registration, you can read and write

articles in the forum and access other portal content. With a service agreement, you get

access to an extensive object library with content that is continuously extended and

updated.

In addition to the web pages and the documentation on Allplan, the website http://www.

zeichenatelier.de/Allplan2012 contains information on this and other books.

This guide attempts to reflect my experiences of using Allplan on a day-to-day basis for the

planning of buildings and external facilities, as well as those gained in my capacity as a

trainer and from my many discussions with colleagues.

The title picture depicts a sample project after reworking in Cinema 4D. It is a design by

313-Architekten Landshut.

My particular thanks go to Sieglinde Schärl, Stefanie König and other colleagues at Carl

Hanser Verlag for their patience and help, as well as all employees at Nemetschek AG and

Martin Philipp for the background information on the new chapter 10,

SmartParts.

Markus Philipp

http://www.zeichenatelier.de

Landshut, November 2011

1

General information

What is Allplan 2012?

Allplan 2012 is an object-oriented 3D planning and design

software package for Building Information Modeling (BIM).

It covers all commonly used design types, from simple 2D

drafting all the way to virtual building modeling with integrated quantity take-off and

cost calculation. Allplan 2012 supports interdisciplinary planning among architects,

con-struction engineers, design professionals and facility managers.

 

■ 1.1 Allplan 2012 product family

Nemetschek offers separate product families for the various fields of planning and design;

these are integrated and connected with each other.

ƒ

Allplan 2012

→ for architects

The CAD solution for architects contains all the Allplan families (depending on the

license), covering the architect’s planning process from the initial draft sketches right

through to the working drawings. The building model created in Allplan 2009 serves as

the basis for the other design professionals.

→ for engineers

The CAD solution for engineers contains all the Allplan families needed for creating

general arrangement and reinforcement drawings etc. (depending on the license).

Round-Trip Engineering also permits the optimum combination of CAD and structural

analysis, because here, load-bearing components are transferred from the CAD system

directly to the structural analysis software.

ƒ

Allplan 2012 Sketch enables you to create professional sketches with ease. Various pen

types let you sketch your ideas and presentation drawings quickly and efficiently with

a wide range of presentation options. There are infinite possibilities for combining

sketches with photos, renderings and much more.

ƒ

(BCM = Building Cost Management) is an independent product for building cost

manage-ment and the area of TAI for planners. Thanks to the tight integration between Allplan

BCM and Allplan BIM, clear and reliable quantity takeoff operations can be carried out

in the early phases of planning, right through to settlement.

ƒ

Allplan 2012 IBD is a comprehensive, sector-specific database with which you can create

your building model and reliably calculate building costs. Allplan IBD ensures the

relevant information is exchanged and provides well-founded quantity calculations for

costing and bills of quantities.

 

■ 1.2 Installing Allplan

1.2.1 Hardware requirements

You can use the Systest2012 tool to check whether computers meet the system

require-ments for Allplan 2012. If the tool is on a DVD it can be launched from there; otherwise it

can be downloaded from http://www.nemetschek.eu/info/systest2012. For current

infor-mation on the recommended components, see

http://www.nemetschek.de/info/grafik-karten and http://www.nemetschek.de/info/plotter.

The following equipment information is from the manufacturer.

Recommended setup

Minimum setup

Intel Core i5 or i7 processor or compatible

Intel Core 2 processor or compatible

8 GB RAM

2 GB RAM

5 GB free hard disk space

DirectX 10-compatible graphics board

Resolution: 1600 x 1200

Field of application: Performance or high-end

Resolution: 1280 x 1024

1.2.2 Operating systems

The following operating systems for workstations and data servers are approved by the

manufacturer:

ƒ

Windows 7, Service Pack 1 (recommendation: 64-bit version)

ƒ

Windows Vista, Service Pack 2

ƒ

Windows XP, Service Pack 3 (Windows XP is supported for the last time in Allplan 2012

and should therefore only be used for existing systems)

ƒ

Windows Server 2008 R2, Service Pack 1

1.2 Installing Allplan 

3

ƒ

At the time of printing, no definitive information was available regarding the operation

of Allplan on MAC. For more information, see http://www.nemetschek.eu/info/mac2012.

Windows 7, Service Pack 1 in the 64-bit version was used for the creation of this book.

1.2.3 Installation types

Allplan is always installed individually on each workstation, i.e. the program is installed

locally. The data paths can be stored either locally or centrally on a server.

Allplan is either installed with a license (demo or final license), and offers the

correspond-ing modules. Alternatively, Allplan can be installed as a viewer in order to provide those

not involved in the design process, such as the building supervisor, with access to all

project data, for example, or to equip a mobile workstation for presentations and/or

meet-ings. On expiration of the license, Allplan can still be used as a viewer with restricted

functions (changes not possible, analyses and printing possible without restrictions, all

data visible).

Depending on the licenses available (one, several, with/without workgroup), the

follow-ing installation options are possible. The Allplan project folder is stored locally in

[system drive]:\programs\nemetschek\ (standard setting).

Comparison of installation types:

Standalone Network without

workgroup

Network with

workgroup

Program directory

Local

Local

Local

Project directory

Local

Server

Server/local

Office standard

Local

Server

Server

Network required

No

Yes

Yes

Private user directory

For each

workstation

For each

workstation

Centrally stored for each

Windows user

Sharing of office standards

No

Yes

Yes

Control of access to

projects

–

No

Yes

Simultaneous project

pro-cessing with several users

No

No

Yes

Installation on a standalone workstation

With this option, Allplan is only installed on the workstation in question (regardless of

whether this computer is in a network or not). All the data exists locally on this computer.

A standalone installation is particularly suited for a single workstation (e.g. laptop), if there

is no workgroup and/or it is the only workstation in the office. In the case of a stationary

workstation and data server in the local network, a network installation is preferable.

Network installation without workgroup

The central file directory allows all users to access the office standard and all the projects.

With this type of installation, collaboration between several employees in a project is not

possible. As soon as a user opens a project, this project is locked for all the other users,

ensuring that only a single user may edit a project. Other projects can be worked on by

other users (one user at a time).

This type of installation is preferable to standalone installation if the network contains a

data server. With more than two workstations, the data should always be stored centrally

in the network.

Network installation with workgroup

With this option, projects and user folders can reside on the server as well as on any

computer added to the Workgroup Manager, ensuring that all workstations have access to

this data.

You need to create and share a folder on each (standalone) workstation where projects or

user folders are to be stored. In addition, this folder requires a subfolder. Then you can

add the individual workstations using the Workgroup Manager.

Mobile workstations can be integrated in the system. Before exiting the workplace, the

user must check out the workstation.

1.2.4 System paths for Allplan

During installation of Allplan, two paths can

be entered. If possible, the central file

stor-age folder should be located on a server; the

program folder is always local.

Central file storage folder

For the CENTRAL FILE STORAGE FOLDER, you can select either a local path, or store the

data in a server directory. You must have sufficient rights to access the shared folder.

In the case of installation without workgroup, only the folders \PRJ (projects) and \STD

(office standard) are created.

Data for all computers are provided in the UPDATES folder, depending on the settings in

Allplan Update (see also section 1.3,

Updating Allplan – Allplan Update).

Program folder

The Allplan project folder is created locally. In addition to the program folder, important

resources that Allplan frequently accesses are stored locally. A number of folders are

cre-ated in the local program directory. In the event of an update, all the available files except

the USR directory are overwritten.

1.2 Installing Allplan 

5

1.2.5 First-time installation of Allplan 2012

Before installing Allplan 2012, you should perform the system test on all the CAD

compu-ters in the network in which Allplan 2012 is to be installed. The link can be found either

in the Start menu of the DVD, http://www.nemetschek.de or on the website for the Allplan

2012 Practical Manual at http://www.zeichenatelier.de/Allplan2012.

At detailed guide on the installation process on your system can be found on the Allplan

DVD, which you can request from the Nemetschek website.

During installation of an additional workstation in an existing network, the existing path

is to be specified as the central file directory. This is displayed e.g. in the Services

applica-tion.

1.2.6 Installation as upgrade

An upgrade is a version change e.g. from Allplan 2011 to Allplan 2012 and usually

involves a data conversion.

If older Allplan versions already exist, Allplan can be installed as an upgrade. All data

paths are retained and are assigned the new content. Before the upgrade installation, you

should save the content of the central file directory.

If several workstations need to be installed, work is not possible on the other

worksta-tions after the installation has been started on the first computer. As soon as the

installa-tion has been completed on the first workstainstalla-tion and this can be run (test one or more

projects quickly), the other installations can begin. Workstations on which the installation

has been completed can be operated again immediately.

1.2.7 Installation of updates

An update relates to an update of a main release and does not require a conversion of

data. In the last version, hotfixes were provided to fix bugs and an “interim version” was

made available. These updates should be imported to all workstations as soon as possible

after they are made available.

Interim versions are provided as a download on the internet and subsequently as a DVD

and must be imported separately on each workstation.

1.2.8 Allplan and Services program launch

After installing Allplan 2012, you will find two new icons on your desktop, as well as a

new program group under PROGRAMS in the Start menu.

You use the ALLPLAN 2012 icon to launch the CAD program and the SERVICES 2012

icon to launch a configuration program.

 

■ 1.3 Updating Allplan – Allplan Update

From Version 2011, Allplan offers a way of keeping all Allplan installations up-to-date at

all times easily and without effort. The automatic update works both for small changes

(hotfixes) and for large service releases and updated help files.

Allplan updates can be controlled in three ways

ƒ

Download and install updates automatically.

ƒ

Download updates automatically and install them manually.

ƒ

Download and install updates manually.

The settings made always apply for the computer, regardless of the user rights. Every user

can change the settings (with the exception of workgroup installation).

Allplan update in the workgroup

In a workgroup installation, the system administrator can make various settings, install

updates on all workstations automatically or distribute the updates to all workstations at

a particular point in time.

Allplan update settings

The ALLPLAN UPDATE SETTINGS dialog box is used to configure how Allplan performs

automatic updates. Depending on the chosen settings, you can prevent Allplan from being

updated (not advisable), or have it updated semi-automatically (good in networks with

system administrators) or fully automatically.

The settings can be seen by all users. In workgroup installations, the administrator can

control certain settings centrally and therefore deactivate them for the user.

The settings can be found in the ? (Help) menu

ƒ

INSTALL UPDATES AUTOMATICALLY

At the specified point in time, the system automatically

searches for new updates. As soon as a new update is

avail-1.4 Working with the Allplan 2012 Practical Manual 

7

able, it is automatically downloaded. The next time Allplan is launched, a downloaded

update is installed without further user interaction (even if it was manually downloaded

with FIND NOW).

ƒ

FIND UPDATES defines the times at which Allplan is to search for new updates. The

search is only carried out if an internet connection exists at this point in time.

NOTE:

 FIND UPDATES defines the interval at which Allplan is to search for

new updates, regardless of the installation type selected.

ƒ

DOWNLOAD UPDATES, INSTALL MANUALLY (recommended)

At the specified time, the system searches for and downloads updates. The next time

Allplan is launched, the update is installed after a confirmation prompt. If this setting is

chosen, you retain full control over the time at which an update is carried out, but do

not have to go to the trouble of finding updates yourself.

ƒ

DO NOT FIND UPDATES AUTOMATICALLY deactivates all automated search and

download functions. However, you can use FIND NOW to search for new updates

manu-ally. In this case, published updates are installed without the option of canceling.

ƒ

FIND NOW triggers an immediate search for new updates and downloads these after

confirmation by the user.

If

INSTALL UPDATES AUTOMATICALLY is activated, the downloaded update is

installed automatically the next time Allplan is launched. If DOWNLOAD UPDATES,

BUT INSTALL MANUALLY is activated, the downloaded update can be installed

manu-ally the next time Allplan is launched.

ƒ

SHOW UPDATE HISTORY shows the computer’s update history.

ƒ

SYSADM SETTINGS is only available for Allplan administrators in a workgroup

instal-lation and provides administrators with settings for controlling updates in the network.

 

■ 1.4  Working with the Allplan 2012

Practical Manual

The sections that follow describe how to operate Allplan 2012 based on a sample project

explained in manageable sections.

To simplify work and illustrate a modern method of working, wizards were stored on your

computer during installation of the project. These wizards contain all the elements and

components relevant for the project. As an alternative to working with wizards, you can

configure the properties yourself as required or, if available, use the favorites in the

tem-plate project.

Each example is preceded by a theory-based introduction. Please take the time to read

these sections, because they contain information and suggestions that go beyond those in

the example. The structure is roughly based on a possible project from the initial sketches

in the site plan through to finished application planning with extended labeling and

dimensioning.

All screenshots were created on a Windows 7 computer with a workgroup installation of

Allplan 2012. If different or fewer options are available on the screens for installation

without workgroup, you can ignore these.

1.4.1 Structure of the following chapters

An example is used to explain the basic working methods and options, from basic

know-ledge of Allplan, basic settings and basic information with the creation of a project from

a template project, the creation of a building model with equipment in order to generate

views, sections and lists from the model, through to data output on paper.

All areas are explained step by step on the basis of a sample project. The practical

exam-ples are preceded by an explanation of the tools and functions. In almost all cases, more

tools are described than are actually used in the example.

It is advisable to either start from scratch with the new project, or, if you have prior

knowledge, to work through the corresponding areas based on your own data.

1.4.1.1 Subsections of the example

The subsections that accompany the sample project through step by step are highlighted.

The top line contains the main topic/focus while the line below indicates the function or

feature being described.

1.4.1.2 Typographic conventions in examples and explanations

SMALL CAPS Function calls and texts that appear on the screens

h

Individual step in explanations of the principles in the theory-based areas

Z

Individual step during processing of the sample project

Italics User input during processing of the sample project

Functions that were significantly revised and/or extended in version 2011 and 2012, as

well as new functions and options in Allplan 2011 and Allplan 2012 are marked with the

icons on the right. The corresponding items are in the point

New in Version 2011 and

Revised in version 2011 as well as New in version 2012, Revised in version 2012 in the

index. New features from Allplan 2011 are also listed to provide all readers who are

read-ing the book in conjunction with version 2011 the information they require.

New feature in

version . . .

1.4 Working with the Allplan 2012 Practical Manual 

9

1.4.2 Data relating to the guide

1.4.2.1 Obtaining the data

You can obtain the project data relating to the guide as follows:

Option 1

Visit the website below, where you will find the project data and further information to

download.

ƒ

http://www.zeichenatelier.com/Allplan2012

1.4.2.2 Installing the data

When you start the setup procedure, the data relating to the book is installed

automati-cally. You must answer YES to any confirmation prompts that appear during setup. All the

required data is copied to the specified directories and project management is updated at

the end of installation.

In the event of a second installation, the existing projects are NOT overwritten.

1.4.2.3 Installed files and folders

You can use all the installed data for your own projects. You can either further develop

the book’s template project for your own purposes or copy the data (resources) from the

sample projects to your office standard or your template project. The steps required to

exchange resources are described either in the help or my book

Allplan 2009 für die

Aus-bilding [Allplan 2009 for training], Carl Hanser Verlag (ISBN 978-3-446-41928-5).

Project data

The project data for this book is automatically copied to project management by a setup

program and entered in the administration files. After the setup program has been

exe-cuted successfully, project management will contain two new projects.

ƒ

Template project Allplan 2012 Practical Manual Template: Contains all the data that is

used to work through the guide but is not part of the Allplan main installation.

ƒ

Project Allplan 2012 Practical Manual: Contains the complete project for the book.

The template project in detail

ƒ

Project settings: All path settings for resources are set to <Project>. This means that

you do NOT work with the main installation’s resources in the sample project.

ƒ

Building structure, fileset structure: The project does not contain a ready-made

building or fileset structure.

Project: Allplan 2012 Practical Manual contains an example

of a fileset structure. The building structure is created in chapter 4.2.5,

Example –

pro-ject structure and plane settings, with the wizards contained in the Plane Manager and

built on in the subsequent chapters.

ƒ

Layout structure: Since version 2009, there have also been structuring options for

layouts. The template project and the finished example contain a sample structure. You

can modify and reuse this if required.

Layouts are assigned to the individual structural levels. The structure itself is roughly

based on the HOAI project phases. See chapter 8,

Data output, for a more detailed

description.

ƒ

Resources – surface definitions: Where useful and necessary for the example, the

standard resources have been used and a few settings added. The additional data is

grouped together in the Allplan Practical Manual group.

ƒ

Resources – layers, line styles and drawing types: The layers contained are exactly

the same as those in the Allplan shipment; different layer groups not used in the book

have not been included in the project.

Settings have been added for line styles and drawing types to enable both plan views

and the sections derived from these to be created without sacrificing quality and

with-out the need for postprocessing. The groups are clearly marked and in some cases

described in the book.

ƒ

Label styles and smart symbols: The project contains all the variables, label styles for

components (room labels and story labels) used in the example and a title block. The

smart symbols to be generated during the example can also be found at the

correspond-ing points in the project.

ƒ

SmartParts: The SmartParts used in the example are either available for direct transfer

in the wizards or in the project directory for import.

ƒ

Surface files and textures: The components from the wizards are already created with

simple surfaces (with and without textures). The corresponding definitions are

con-tained in the project’s design folder or are based on the installed standard.

ƒ

Favorites files: At different points in the example, reference is made to favorites

(com-ponents, settings in the BS, display etc.). These are also contained in the project.

Wizards

During installation of the book data, a folder with wizards is copied to the local ETC

direc-tory of Allplan 2012 in addition to the project data. After installation (possibly after a

reboot), these wizards automatically appear in a new group and can be neither changed

nor extended.

The wizards contain all the components that are used and whose settings can be saved in

or accessed from wizards. In addition, they contain similar components, as well as 2D

ele-ments such as lines, texts and dimension lines.

Allplan 2012

Practical Manual

1.4 Working with the Allplan 2012 Practical Manual 

11

Layers

2D elements/

sections

Walls and columns

Windows and doors

Upper slabs, roof,

Rooms and stories

Outdoor facilities

Facade and railing

Furnishings –

Smart-Parts

The individual examples always show an extract from the wizard that contains the

com-ponents. The text description also refers to the required wizards and the component to be

transferred.

2

An Introduction to

Allplan 2012

 

■ 2.1 The project-based approach

To optimize the way you work with Allplan 2012, Allplan provides the project as the

means for managing and structuring your construction project data. Physically, each

pro-ject is a folder on the hard drive containing all propro-ject-specific data.

Project elements

A project consists of different data types that are subdivided into groups. The following

are the most important data groups.

ƒ

Drawing files, layouts, project attributes, administration files → found in every project

(max. 6000 drawing files and 3000 layouts per project)

ƒ

Resources (hatching styles, patterns, layers, etc.) → optional project elements

ƒ

Special resources (search project, drawing symbol regulations) → special,

project-spe-cific links

ƒ

Resources (bitmap files, surfaces, etc.) → available in project depending on usage

2.1.1 Drawing files, layouts

Drawing files – design area

In Allplan, you create your design using drawing files, much like a traditional building

design drawn on transparencies. This means you draw a floor, a view, a section or a detail

in a drawing file. In this way, drawing files can be used to give projects a differentiated

structure. You can display and edit up to 80 drawing files at once – in other words, you

can keep several files open simultaneously. For associative views, an option was created

to enable experts to open up to 188 drawing files internally.

Every drawing file corresponds to a file in the project folder on your hard drive and is saved

using a unique ID. The drawing file name visible in Allplan is not displayed as the Windows

file name on your hard drive. This allows you to use a drawing file multiple times within a

project. You can create a GRID drawing file in every construction stage, for example.

Drawing files are managed and activated for editing using the function OPEN ON A

PRO-JECT-SPECIFIC BASIS (fileset structure or building structure).

Layouts – output area

To output the drawings created in the drawing files, Allplan provides layouts for which

there is a separate mode (Layout Editor). This has been completely revised and improved

in the current 2011 version.

Every layout corresponds to a file in the project folder on your hard drive. This file only

stores the data created in the plot layout (layout border, layout header, drawing labels,

etc.), as well as the rules for displaying the layout elements in the layout. As for the

draw-ing files, a layout is saved with its own number. This means you can create several layouts

with the same name within a project.

All the documents (drawing files and NDW files) that you need for your layout are saved

as layout elements in the layout. When placing the layout elements (also afterwards), you

can define various settings such as scale, visibility of layers, etc.

The individual elements contained in the layout element are not actually placed in the

layout. Instead, a reference to the corresponding document (drawing file or NDW file) is

created. As a result, all the data displayed in a layout is always completely up to date with

the latest design status.

Differences between the drawing file/layout, custom NDW/custom layout

You can create design drawings using drawing files (project-specific) and custom NDWs.

These documents can have any required reference scale and any components.

For output you can use layouts (project-specific) and custom layouts.

Layouts and custom layouts are always created in scale 1:1. The drawing unit is

auto-matically converted to mm. You can combine drawing files in the layout. Layout borders

and other elements such as the layout headers and additions are created in layouts.

You can use the Layout Editor button to toggle between the two data types. When the

but-ton is pressed, you can edit layouts; when it is not pressed, you can edit drawing files and

custom NDWs.

2.1.2 Administration files

Project attributes

Project attributes are used to manage general information on a construction project. You

can, for example, use the attributes to save the exact name of the construction project, as

well as details on the client and the other project members. This data can then be accessed

throughout the project and used when labeling layouts and components.

The project attributes are therefore part of the project master data and can be accessed

at many points within the project. When you change an attribute (e. g. the client or the

name of the construction project), for example, it is updated in all layouts where that

attribute is included in the layout header.