Embed Size (px)
Citation preview
Page 1
TR21166
BIM for Infrastructure—Manage Your information Tomáš Lendvorský, Senior Tech. Sales Specialist – AEC, Autodesk Vincent Fredon, Tech. Sales Specialist – AEC, Autodesk
Description
Information is the most important part of Building Information Modeling (BIM). Come and learn how to add user-defined information to a 3D model, and how to use and manage that information downstream in the processes. We will show how you can add project-specific information to your infrastructure model and how other project stakeholders can use it. You can also share this information with different geographic information system (GIS) systems. Workflow will include AutoCAD Civil 3D software, Navisworks software, and BIM 360 cloud-based collaboration services. This session features AutoCAD Civil 3D, BIM 360 Team and Navisworks Simulate.
Your AU Expert(s)
Tomáš Lendvorský joined Autodesk, Inc., 11 years ago and currently is working as Senior Technical Sales Specialist, responsible for the architecture, engineering, and construction (AEC) Autodesk portfolio in Eastern Europe. Tomas has a master’s degree in land surveying from Czech Technical University in Prague. For more than 20 years he has been working with different infrastructure designing products. His current role is to work with Autodesk partners and customers actively promoting the AEC portfolio. Civil engineering expertise helps him be actively involved in countryfication of the product in different countries, ensuring product suitability for each region. He has over 20 years of working experience with civil designing software. You can reach Tomas at [email protected]
Vincent Fredon is Technical Sales Specialist in AEC in Autodesk within South Europe. He is Infrastructure specialist working with all the Autodesk infra solutions and mainly AutoCAD Civil 3D, InfraWorks 360 and Navisworks. Based in Paris, Vincent has worked 13 years for Engineering companies in the Infrastructure domain. He then moved to an Autodesk VAR (GraphLand) where he has been Trainer and Consultant for various enterprises and projects (road, rail, energy…) on different software and BIM processes implementation. During the last few years, he has developed a strong expertise in meeting the needs of French civil companies. Vincent also worked on the French Civil Country Kit and the Autodesk InfraWorks 360 localization, as a contractor for Autodesk. You can reach Vincent at [email protected]
Learning Objectives
Learn how to add user-defined properties to an infrastructure model Learn how to use information in a BIM workflow
Learn how to share information in an efficient way
Learn how to add value to your project
Page 2
Building Information Modeling
BIM is very hot topic and there can be many view on that. This session will focus on workflow, how infrastructure data, and more importantly INFORMATION, can be added and utilized across Autodesk products. According to our opinion Information are crucial part of BIM and it is very important to add information to 3D model throughout project lifecycle.
New AutoCAD Civil 3D 2017 functionality supporting BIM process
AutoCAD Civil 3D has couple of releases possibility to export Corridor model to AutoCAD Solids, which can be later on used in Navisworks for BIM model aggregation. However the latest AutoCAD Civil 3D release is equipped with a lot of new functionality, making BIM process easier. Here is the summary of new functionalities, which will be used in different workflows:
1) Create Data Shortcuts (DREF) from Corridor 2) Enhancements to extract Corridor Featurelines 3) Reference external styles 4) Add Property set to objects
Create Data Shortcut (DREF) from Corridor
Extended properties can be added to Solids, created from Corridor. New functionality to DREF Corridor and possibility to maintain dynamic link to original Civil 3D Corridor is important, because you can have separate DWG files for different purposes. One with Corridor design model and the second one for clean model with BIM information. Key points of new functionality:
- If you DREF Corridor, then system will automatically reference Alignment and Profile at the same time
- If your model contains larger amount of Corridors, you can benefit from new functionality to create folder structure for your referenced objects. This will make you project structure clean and structured.
- New Corridor command CreateCorridorReference controls referenced Corridor behavior, like drawing style, Code Set Style etc. (Picture 1)
- If Corridor is created from Feature Line, instead of Alignment and Profile, system will automatically create Alignment and Profile during referencing process and newly created objects will be referenced automatically
Page 3
Picture 1 - Command CreateCorridorReference
Enhancements to extract Corridor Feature Lines
Feature Lines created from Corridor are important assets in possible BIM workflows. They can represent curb, ditch, crash barrier etc. Key point of enhanced functionality are possibilities to control:
- Dynamic relationship with original Corridor (Picture 2) - Naming convention (Picture 2) - Style one by one or via assigned Code Set Style during extraction process (Picture 2) - Join Feature Lines in adjacent region (Picture 2) - Extraction process behavior – new command FeatureLinesFromCorridor (Picture 3)
¨
Picture 2 – Extract Corridor Feature Line dialog
Page 4
Picture 3 - command FeatureLinesFromCorridor
Style Management
New function Reference Styles enables to reference styles from different drawing/template. Without need to import styles you can bring into DWG different styles, related to your company or project. You can also define order, hence your preference which styles to use if referenced drawings/templates contains styles of the same name.
In BIM workflow you can have separate DWT file containing Property sets (see later) and not necessarily have all setting within one template.
Picture 4 – Reference styles
Page 5
Add Property Set to object
New capability to add Property set is the key functionality, which enables to attach wide range of information to different entities. Entity can be Civil 3D object or vanilla AutoCAD entity. Properties can be added either automatic or manual way. Important functionality is possibility to keep dynamic relation between original Corridor and extracted solids.
Picture 5 – Add automatic property set to Corridor Solids
Picture 6 – Add Manual property set to wide variety of entities
Page 6
Property set definition
What is needed to be understood, that Corridor solids have broader range of possibilities to extend properties then the rest of entities. As already mentioned, we can extend properties to Civil 3D objects or even AutoCAD entities. This can be done using Style Manager, which can be found under Manage -> Define Property Set (command _PropertySetDefine). Here you can create as many Property Set Definitions as you wish, depending on object type. It means, you have to define object set, where extended properties will be applied to (tab “Applies To”) later in the process (Picture 6). Under “Definition” tab you can define Properties using different possibilities.
Note: Handle/ObjectID is important property for Formula based Property Definition and for GIS workflow.
Adding Property Set Manually Style Manager can add manual, automatic or formula based properties and can define which objects will be affected. Therefore can be used not only for Corridor solids, but also for other Civil 3D or vanilla AutoCAD objects. Add Formula Property Definition can use ActiveX API. Here are examples:
Picture 7 – Define entity set, where extended properties will be applied to
Page 7
Picture 8 – Add Manual property sets
Add Formula Property Definition - examples 1) Feature Line length:
Applies To: Auto Corridor Feature Line, AutoFeature Line, Feature, Feature Line API formula: RESULT="--" On Error Resume Next Set oApp=GetObject(, "AutoCAD.Application") Set oCivilApp=oApp.GetInterfaceObject("AeccXUiLand.AeccApplication.11.0") Set obj=oCivilApp.ActiveDocument.HandleToObject("[Handle]") RESULT=obj.Length3D
Picture 9 – Feature Line user defined properties
2) Gravity Pipe length and slope: Applies To: Pipe objects API formula: RESULT="--" On Error Resume Next Set oApp=GetObject(, "AutoCAD.Application") Set oCivilApp=oApp.GetInterfaceObject("AeccXUiPipe.AeccPipeApplication.11.0")’ Set obj=oCivilApp.ActiveDocument.HandleToObject("[Handle]") RESULT=obj.Length3D RESULT="--" On Error Resume Next Set oApp=GetObject(, "AutoCAD.Application") Set oCivilApp=oApp.GetInterfaceObject("AeccXUiPipe.AeccPipeApplication.11.0") Set obj=oCivilApp.ActiveDocument.HandleToObject("[Handle]") RESULT=obj.Slope
Page 8
Picture 10– Gravity pipe user defined properties
3) Polyline length: Applies To: Line, Polyline, Polyline (2D, Polyline (3D) API formula: RESULT="--" On Error Resume Next Set oApp=GetObject(, "AutoCAD.Application") Set obj=oApp.ActiveDocument.ObjectIDToObject("[ObjectID]") RESULT=obj.Length
Picture 11 – Polyline user defined properties
4) 3D Solid volume: Applies To: Solid (3D) API formula: RESULT="--" On Error Resume Next Set oApp=GetObject(, "AutoCAD.Application") Set obj=oApp.ActiveDocument.ObjectIDToObject("[ObjectID]") RESULT=obj.Volume
Picture 12 – 3D Solid user defined properties
5) TIN Surface area: Applies To: TIN Surface API formula: RESULT="--" On Error Resume Next Set oApp=GetObject(, "AutoCAD.Application") Set oCivilApp=oApp.GetInterfaceObject("AeccXUiLand.AeccApplication.10.5") Set obj=oCivilApp.ActiveDocument.HandleToObject("[Handle]") RESULT=obj.statistics.Area3D
Page 9
Picture 13 – TIN Surface user defined properties Note: Different Civil 3D versions use different AeccXUiLand.AeccApplication (or AeccXUiPipe.AeccPipeApplication) versions: Civil 3D 2012 AeccXUiLand.AeccApplication.9.0 Civil 3D 2013 AeccXUiLand.AeccApplication.10.0 Civil 3D 2014 AeccXUiLand.AeccApplication.10.3 Civil 3D 2015 AeccXUiLand.AeccApplication.10.4 Civil 3D 2016 AeccXUiLand.AeccApplication.10.5 Civil 3D 2017 AeccXUiLand.AeccApplication.11.0
Corridor Shape properties Apart from Style Manager, Corridor Shape extended properties can be defined also: 1) Within Code Set Style as Classification Code
Picture 14 – Code Set Style with Classification Code
Page 10
2) While exporting Solids from Corridor as User defined Corridor Property data
Picture 15 – User defined property
Property Set labeling
“Civil 3D 2017 v1 Enhancements” package offers new functionality to display properties from Property Sets in Civil 3D labels. Only manual properties in the Property Set can be managed.
This is possible with an additional tab in the “Text Component Editor – Content” Palette
Picture 16 – Property Set label definition
Picture 17 – Result example
Page 11
IFC export In some cases, collaboration is done using IFC (Industry Foundation Classes) format. AutoCAD Civil 3D can export a generic IFC file (official infrastructure IFC classes are still to be defined) which support surfaces and volumes. It’s important to notice that all properties added to objects using Property Set are also supported in IFC export.
NAVISWORKS – ADD AND/OR UTILIZE INFORMATION
Utilizing additional information Autodesk Navisworks can utilize Extended properties for different purposes. Very important Navisworks funtionality is Search Set definition. Extended properties enriching Find Items capabilities and user can group together objects following searching criteria based on these properties.
Picture 16 – Searching criteria example based on extended properties
Add more info within Navisworks More Properties can be added within Navisworks environment.
User Data Property Manually you can add User Data Tab and Properties for selected item within Property window
Page 12
Picture 17 – User defined property
Data Tools Data Tools functionality enables to link external database with the objects. You can link Microsoft Access table columns to new property. Object will be linked to respective row via SQL String.
Picture 18 – DataTool Link Connection string: DSN=C:\Support\AU2016\Data\Maurits.accdb;DefaultDir=C:\Support\AU2016\Data;Driver={Microsoft Access Driver (*.mdb, *.accdb)};DriverId=25;Exclusive=0;FIL=MS Access;MaxBufferSize=2048;MaxScanRows=8;PageTimeout=5;ReadOnly=1;SafeTransactions=0;Threads=3;UID=admin;UserCommitSync=Yes; Yellow background – respective directory Grey background – respective Microsoft Access database SQL String: SELECT * From ObjectInformation WHERE "ModelObjectCode" = %prop("Objectdata","ObjectCode") Yellow background – Table name Grey background - Property
Note: Navisworks DataTools uses ODBC Driver. Therefore you need to install OBDC driver for MDB on the computer.
Page 13
Quantification using extended properties
Another possibility is to perform Quantity takeoff within Navisworks. Navisworks can aggregate data from different sources, within Infrastructure for example from Revit or Civil 3D and quantity surveyor delivering BOM can work on one model within one product.
Below example shows Quantity takeoff from Asphalt and Crash barrier, which has been designed as Pave1 shape within Civil 3D. Navisworks take quantification from the Properties, therefore whatever you want to quantify, you have to have Property containing either volume (Corridor Shape) or length (Feature Line)
Navisworks needs to understand, where quantity (length, area, volume) is coming from, therefore property mapping has to be done before quantification will be performed.
Picture 19 – Property mapping definition
Using standard Navisworks functionality you have to select objects, which you have to quantify and then use Model Take off Selected Model Items
Picture 20 – Asphalt takeoff
Page 14
Picture 21 – Crash barrier takeoff BIM 360 Collaboration with other project stakeholders can be done using BIM 360 Autodesk services – BIM 360 Team, BIM 360 Docs, BIM 360 Glue. Important is, that extended properties are tight to objects and are accessible in all these services. They are based on Large Model Viewer, which can be also accessed directly here
Picture 22 – Extended properties within BIM 360
Infraworks 360 workflow Extended Property data can be also used for asset management. To make available extended properties data within GIS model, we will need to work with AutoCAD entities only. This is why
Page 15
you need for example to explode Feature Line to polyline and attach extended properties to it. Exception are Pipe and Alignment objects, which can be exported to SDF file format. SDF will be used to connect design and GIS world. The process needs to be done in 2 steps Step 1 – Civil 3D: DWG with Extended properties and exploded entities:
- Export to geometry to SDF format using _MAPEXPORT command - Extended properties are not available while exporting data. Therefore we will export
property EHANDLE. - Command _EXPORTPROPERTYDATA will export property set data to Microsoft Access
database, MDB file
Step 2 – Civil 3D: new DWG: - In new drawing connect to SDF file using Map 3D FDO provider - Connect MDB file using ODBC FDO provider - Create a Join… to connect database data to vectors. - Export Layer Data to SDF… to create SDF containing extended properties
Step 3 - Infraworks 360
- Import design using standard AutoCAD Civil 3D DWG import - Optionally create new class or/and properties to import and map extended properties
from Civil 3D - Import SDF and map Civil 3D properties to Infraworks 360 properties
Picture 23 – Mapping Civil 3D extended property to Infraworks 360 property
Page 16
Picture 24 – Road asset with extended properties
Conclusion New Civil 3D functionality, enabling to add extended properties to different objects offers interesting workflows and opens new doors to true BIM – information flow across project lifecycle and among different stakeholders. Each flavor of Navisworks (Freedom, Simulate or Manage) can be used to access this info. Paid versions can be used to add more info into the model. Properties can be also accessible in BIM 360 services, therefore also for people outside the company without compromising intellectual property. It also enables to extend infrastructure workflow with Navisworks for quantification and Infraworks 360 to visualize your design and to manage assets.
