ebook img

BIM Manual Civil Works and Infrastructure BIM Manual Civil Works and Infrastructure PDF

85 Pages·2016·6.05 MB·English
Save to my drive
Quick download
Download
Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.

Preview BIM Manual Civil Works and Infrastructure BIM Manual Civil Works and Infrastructure

BIM Manual Civil Works and Infrastructure December 2016 /LOSK +45 22709597 [email protected] BIM Manual Civil Works and Infrastructure REV. DATE DESCRIPTION/CHANGES PREPARED CHECKED APPROVED BY BY BY 0 Jan 2015 First edition incl. comments from D&E LOSK DWP POL 1 Dec 2016 Release to external parties, general corrections LOSK DWP POL 2 3 MT Højgaard A/S Knud Højgaards Vej 7 2860 Søborg +45 7012 2400 mth.dk CVR 12562233 Table of Contents 1. Introduction 3 2. BIM processes 4 2.1 Roles 5 2.2 Effective data flow 5 2.3 Common Data Environment 10 3. BIM as CAD production basis 12 3.1 Template 12 3.2 Reference points 12 3.3 Coordinate system/elevation systems 12 3.4 Revision documentation 13 4. Structuring BIM Models 15 4.1 Type models 15 4.2 Folder structure 17 4.3 Reference systems 18 4.4 Naming of BIM Models 21 4.5 Naming of objects 22 4.6 Model list 26 4.7 Levels of development 26 5. Subscription tools 27 5.1 Geotechnical Module 2017 28 6. BIM Models on the construction site 41 6.1 Fix points 41 6.2 Site model 41 6.3 Excavation 41 7. Data extracts from BIM Models 43 7.1 Drawing production 43 7.2 Quantity takeoffs 46 7.3 Export from Revit to AutoCAD Civil 3D 49 8. Quality control of BIM Models 50 8.1 Approved 50 8.2 Authorised 53 8.3 Verified 53 9. Exchange 54 9.1 Machine control and surveying 54 9.2 Formats 55 10. Lists 56 10.1 List of abbreviations 56 10.2 List of formats 56 10.3 List of Softwares 57 11. Appendices 57 11.1 Appendix 1 Effective Data Flow 57 11.2 Appendix 2 Example of Common Data Environment (CDE) 57 11.3 Appendix 3 Example of QC of BIM Models 57 11.4 Appendix 4 Naming of objects 57 Page 2 of 57 1. Introduction This Manual describes building information modeling (BIM) processes and tools for MT Højgaard’s (MTH) earthworks and road projects. AutoCAD Civil 3D and the associated processes and tools form the backbone of building information modeling (BIM). Over the past years, BIM has been used on more and more projects. For instance, BIM and machine control are often used for excavation models for foundations and pipework. This emphasises the importance of this Manual. You do not need to read the Manual from start to finish. Below you can see the intended addressees of the different sections:  Chapter 2 describes BIM processes and roles. This chapter is relevant for all parties involved in civil works and infrastructure projects.  Chapters 3-8 describe AutoCAD Civil 3D procedures and are therefore relevant for AutoCAD Civil 3D users. The chapters require a basic knowledge of AutoCAD Civil 3D and are not a software manual. Use this Manual in your daily work and make sure that you always use the right naming and object for the task you perform.  Appendices 1-3 provide detailed descriptions of various processes. Read them if necessary. The document refers to these descriptions where relevant.  Appendix 4 contains all naming tables of objects from section 4.5. If you have any questions, comments or input to the BIM Manual, please write to [email protected]. In the document, file formats will be abbreviated using a full stop and three lower-case letters such as .pdf for a digital plot in the Adobe format. We use upper-case letters for abbreviations. For instance, GPS is an abbreviation of Global Positioning System. At the very back of the document, there is a list of abbreviations, formats and softwares (see sections 10.1, 10.2 and 10.3). Page 3 of 57 2. BIM processes A building information model is not just one model. It generally contains a lot of references, objects, property data and history. The processes through to a finished BIM Model may involve different paths, and the end result may have a multitude of appearances. Figure 1 illustrates this complexity where information merges and is presented and used in different ways. (See section 4.1 for an overview of the various types of models shown in the figure). Chapter 2 describes how and why BIM processes in MTH are performed in the same way because it results in:  A more comprehensive overview of the project  More accurate BIM Models  Fewer errors in the design basis Figure 1: BIM processes. Source: Supplement to the bips CAD Manual 2008. Sections 2.2 and 2.3 provide a more detailed description of BIM processes. See also Appendix 1 for specification of Effective Data Flow and Appendix 2 for an example of a BIM Model’s journey through the Common Data Environment. But first the BIM roles must be in place. Page 4 of 57 2.1 Roles Table 1 below describes BIM roles on earthworks and road projects. It is possible for one person to have several roles. The roles will apply throughout the Manual. Roles Description BIM Coordinator Coordinator of the BIM work. Each firm appoints one or more BIM Coordinator(s) BIM Manager Manager of the different BIM Coordinators Designer The designer creating the BIM-model Design Engineer Designer with design responsibility Approver In most cases a project or design manager Model secretary A person keeping an eye on the client’s project web and Shared. When there are new files, the Model Secretary will notify the project team. Table 1: Roles 2.2 Effective data flow The effective data flow (Figure 2) describes how to effectively exchange data between different tools throughout the construction process. The appendix provides a general description of the tools as the processes can be carried out using Autodesk as well as Bentley tools. The effective data flow supports effective BIM collaboration on the project if the right tools and competencies are available and can be used for all types of civil works and infrastructure projects such as roads, railways, bridges, tunnels and land developments. The effective data flow enables the reuse of data from process to process on the individual project. The reuse of data reduces errors and workload. Page 5 of 57 Figure 2: Effective data flow. The top of Figure 2 shows two types of modeling tools: a Preliminary project tool (1) and a Design tool (2), and the bottom of Figure 2 describes the possibilities of further processing the BIM Models in other tools (3-6). The arrows between the tools indicate data flow directions. Active interaction between the tools in all phases of the project adds tremendous value as the tools contain different design and analysis options, and the tools allows for easy exchange of information/data. The different types of tools and processes are described in further detail below. Tools 1. Preliminary project tool The Preliminary project tool makes it possible to create conceptual designs of different solutions and to present processes and solutions. The tool is intended to support the design and visualisation processes in the Design tool (2) to facilitate easy interchange of data between these two tools, without any loss of data. The tool must be able to import a large number of file formats to build the conceptual design. Likewise, the tool must be able to import existing data such terrain, buildings, roads and pipes. The tool must also include a BIM Model analysis option such as roadway curves, analyses of visibility from cars, profile optimisation and shade conditions. The tool may also include an option to develop conceptual designs of bridges, roads and drainage systems which can be processed in detail in ancillary Design tools (2). As an example of Preliminary project tools are Autodesk InfraWorks 360 or Esri CityEngine, which both can import most file formats and perform various analyses. Page 6 of 57 2. Design tool The Design tool should allow for detailed design and optimisation of Alignments, Profiles, road structures, excavations, surfacing, etc. The tool must be able to automatically generate quantity takeoffs, cross sections as well as plan and profile views so that products such as quantities and drawing production need no longer be made manually. Autodesk AutoCAD Civil 3D, Trimble Tekla Structures and Bentley Microstation Inroads are examples of Design tools in civil works and infrastructure projects. 3. Production planning Production planning includes various project and process planning initiatives, including:  Site model  Visualisation of critical processes/building components  Materials and logistics optimisation By planning the execution the construction works from start to finish already in the design phase, most challenges are taken into account before the first turf is cut. This will, for instance, minimise unforeseen costs and production stoppage and reduce fuel consumption and CO2 emissions – and ultimately shorten construction time. Autodesk Navisworks and InfraWorks are also examples of tools that can be used for production planning in civil works and infrastructure projects. 4. BIM detailed project planning The Design tools (2) are used for detailed design in BIM. 5. Earthworks optimisation For earthworks optimisation, we use a location-based project management tool that can handle soil quantities and which supports planning and management of large linear civil works and infrastructure projects such as roads or railways as well as, for instance, mass optimisation. Dynaroad is an example of a state-of-the-art tool designed specifically for the planning and management of large linear civil works and infrastructure projects. 6. Machine control and surveying Building information models are used for machine control and surveying. BIM Models from the Design tools (2) can be entered in machine control and surveying equipment to enable the crew to stake out reference points, grade and begin excavation directly. The work performed can also be measured automatically for control and as-built documentation. The Leica iCON system is an example of a tool for both machine control and surveying. To inquire about a trial period, contact Leica Geosystems in Denmark (leica- geosystems.dk). Data flows a. From Preliminary project tool (1) to Design tool (2) and vice versa. Central and crucial to effective data flow is the exchange of data between Preliminary project tools (1) and Design tools (2). It is therefore essential that the two tools interact well enough to avoid any loss of data during the exchange. Below follows an example of a procedure between these two tools: In the project start-up phase, the existing conditions will be imported into the Preliminary project tool (1) to generate a conceptual design. The conceptual design Page 7 of 57 could for instance consist of a bridge (see Figure 3a). The conceptual design, including existing conditions, will then be exported to the Design tool (2) to detail the design (see Figure 3b). In the course of the design phase or after the end of the design, information on the project can be gathered in the Preliminary project tool (1) for a visualisation of the designed project (see Figure 3c). a b c Figure 3: Relationship between Design tool and Preliminary project tool. b. From Preliminary project tool (1) and Design tool (2) to production planning (3). Production planning is a broad concept when it comes to tools and processes. The starting point of this document is planning based on a site model, visualisation of critical processes/building components and materials and logistics optimisation. b1. Site model Site models are BIM Models of the construction project with existing surroundings, build in the Preliminary project tool (1) or the Design tool (2) and using building site objects (e.g. cranes, containers, signs, etc.). The site model gives a good overview of the construction period and makes it possible, among other things, to identify any space and logistics problems in the design phase and to minimise relocation of functions at the site because all factors have been considered from the outset. The site model must be updated as the project progresses. Figure 4 shows an example of a site model. The model includes site accommodation, car parking, excavation, materials store, fences, interim roads, etc. Figure 4: Site model. Page 8 of 57 b2. Visualisation of critical processes/building components The Preliminary project tool (1) is used for visualisation of critical processes, e.g. crane lifting, fencing, interim measures, health and safety and scaffolding. It may also be useful to visualise carriage roads etc. if there is little space around the site. Visualisations make it possible to think the critical process/building component through and to find a useful and tested solution. b3. Materials and logistics optimisation A location-based project management tool (5) is used for materials and logistics optimisation. See the next section (d) for more details. c. From Preliminary project tool (1) to Design tool (2) to BIM detailed design (4). The preliminary designs in the Preliminary project tool (1) are exported to the Design tool (2) for detailed planning. The same BIM Model is used in the preliminary design and the detailed planning phase. This is to ensure that the same geometry is used and that the design is well-coordinated. Below is an example of a detailed design of a bridge component. The component is exported from the Preliminary project tool (1) to the Design tool (2) where the geometry is updated and 3D reinforcement models are produced. Figure 5: BIM detailed design of bridge component. d. From Design tool (2) to location-based planning tool (5) and vice versa. Calculated earth quantities from the Design tool (2) are imported in the location-based planning tool (5) from Excel. The quantities in Excel are generated in the Design tool (2), in which they are analysed and segmented according to application categories. On that basis, the location-based planning tool (5) calculates haul distances and thereby visualises areas where the design could benefit from vertical changes to the Alignment or other changes (see Figure 5). If possible, the design will be adjusted in the Design tool (2) on the basis of the calculations in the location-based planning tool (5), and then the quantities will be recalculated and reimported into the location-based planning tool (5). The process runs iteratively until the optimum solution has been found. e. From Design tool (2) to machine control/surveying (6) and vice versa. The design file is imported into the machine control and surveying tools (6) to generate a terrain model, an alignment file and a file containing information on the project's coordinate system. The files can be used for machine control and in a total station (see Figure 6). The systems can also measure in points during performance of work for control and as-built documentation. These Points are exported to the Design tool (2) to check the work performed. Page 9 of 57 Figure 6: Display of design on tablets at total station and in machine house. f. Handover Handover may consist of quantities, production drawings, visualisations, parts lists, presentation model, schedule, as-built, etc. 2.3 Common Data Environment When exchanging files, it is important that the structure is transparent and works. There are many example of situations where the project team has lost track of which files are current, which files have been released, etc. The structure shown in Figure 7 (Common Data Environment, CDE) can help overcome these challenges. This structure is based on British Standard PAS 1192-2:2013, which provides a detailed description of the work processes involved in this structure. The most important elements are described below. Figure 7: Common Data Environment from PAS 1192-2:2013. Figure 7 shows the journey of a BIM Model from start to publication. Each individual BIM Model will follow its own path from start (Work In Progress) to handover (Published), but a common feature for all BIM Models is that they must all go through the elements shown in the figure one or more times. The Common Data Environment (CDE) involves four model areas and three quality control processes. The quality control processes take place in between the four model areas Work in progress, Shared, Published and Archive. The three different quality control processes Page 10 of 57

See more

The list of books you might like

Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.