BIM works flows of using Autodesk products, such as Infraworks, Civil 3d, Map 3d, Recap Pro and Navisworks that makes my life easier.

Thursday, July 10, 2014

Infrastructure BIM model

I've finished up working at DoT and haven't really had time to blog / document about the work flows from the project. The project was a business case for a tack slab through the heart of a CDB. My involvement was looking at the cost impact of existing services and infrastructure. This was done by traditional feature survey and laser scanning of the 22km (500gb of point cloud data) alignment to create a BIM model of existing services, using AS5488 (SUE) classification of subsurface utility information as a base line. Majority of the existing in-ground services where modelled to class C with a couple of major services to class B. The model consisted not only of the existing infrastructure but the proposed light rail infrastructure which was created with multiple software's. 

The simple definition of the BIM process to create the model would be similar to a carpenters set of tools, with each piece of software having its own key use. Similar to how a carpenter uses specific tools to construct a house. 

The exchange process between different platforms was done via landxml. 
A simple list of the software's used and their function. 
  • Bentley Rail used for the rail design
  • 12d used for the road design
  • Civil 3d for the existing surface and existing utilities 
The large data set of the point cloud was processed using Recap which reduced the file size of the point cloud data from about 500gb down to 150gb. Which had the point cloud data set usable on a 22km alignment. 

All of the above was placed into navisworks to run multiple rules to determine the impact of the light rail on the existing infrastructure with the results exported to excel to be processed and costed. 

This Video below and what has been described above is only a snippet of what was done. On the bottom of the screen each service is colour coded.



Some of workflows I've blogged about already and have many more work flows to come.