Rory and I traded a few emails on this today - here is the content of the emails that I sent him after reviewing the model data and the best approach to take.
Rory
I have started to look at the data and what I am seeing is basically what I posted on line the other day.
Siteworks today will display a Cross Section View of a model only when it is set up as a Corridor. To do that with this data you can create an alignment from the centerline of the dam that you sent to me (Use Existing Line) and then create a template and add one instruction - a Surface Instruction that references one of the surfaces of the Dam. You can then select the Corridor Model from the Project Explorer and export that as a VCL file into a Design folder in the "Designs" folder for Siteworks. That will take the HAL/VAL plus the Corridor Surface and create a VCL file.
If you dont need all the Corridors in the TBC Project (one for each surface, then all I would do is change the surface referenced in the Corridor Template and write out a new corridor as a VCL to another Designs Folder for Siteworks and repeat for each surface in your model. While you have 36 Surfaces, I see that many of them have a (2) after the name so I assume that is a Rev 2 Surface etc. so then you have 18 surfaces that appear to be getting revised - so the worst case if you need the corridors then you may need to create 18 corridors and then simply change the surface in the surface instruction if / when the surface is revised and then re write the VCL Design for the field users.
If you output all of the surfaces and a single alignment to a VCL then the field users can select the surface and the alignment for staking / checking and they will get the 3D view and the plan view but no section view
RoryI looked further into this and my advice is to stick with the Construction Data Export and use the Road Surface Model which will create the PRO File for Corridors - you can set up your Corridors as per the last email using a surface instruction for the surface in question and then run the Design Export from the Construction Data menu and use the Road Surface Model Option - select the corridor and that will give you the best result by far. You can see all the surface Break Points and all of the surface segments and use the full Road Staking capabilities.
The PRO is very stable and works well
The downside here is that you will need to do one of the following
1) If you use the Surface Instruction and just change the Surface that you are referencing, because you are using the Design exporter, the Design in the project is linked to the design written to the field, so if the project version changes it will update the design for the devices automatically. If you only want one design on the controller and want to change the surface to suit the work you are doing, this will be an OK approach,
2) However if you need to be able to change designs on the controller, then you will need to create a different corridor for each surface that you want as a design. However this approach, once you have set up all the corridors - each with a single surface instruction, will enable you to rapidly change the instruction to point at a new revision of the surface and that will automatically update the controller files in the Sync Folder for next time they sync up. This would be my preferred way to manage this.
The corridors can all use the same Alignment, each only needs a simple Template with a single Surface Instruction in it and you will be good to go.
While not able to support Multiple Corridor Surfaces in one model, this will at least give you the Plan, 3D and Sectional View.
Hope that this helps - I hope that one day they will support 3D View Linework and also VCL files for Corridors and Material Layers. The whole point of moving to VCL was to provide better / smarter data to the field.
I hope that this helps
Alan
I always use the create site / create design workflow and I don't really understand why you think it is convoluted - it puts the data in the right place and in the right formats and all it is is select what type of model you want and select the linework - what is easier in selecting an export, browsing to the right folder, creating a new folder in the right place, selecting the right format, selecting the right data and pressing export and then doing it all again for a dxf linework file?
With SCS / Siteworks because the data can be a TTM surface or a PRO model for a road / Dam etc and the linework is a dxf and because you can send eg one surface plus many alignments or one alignment and many surfaces and now they also added vcl the more structured approach to create the design is doing what you are asking for in an export
The only difference is that an export does not associate the project data to a design or track the project data for changes - where's as the site and design process does - and I guess I really like that feature because it warns me and takes care of design revisions for me keeping my field teams up to date.
I would really recommend its use over any other method especially on big projects like yours.
I guess we all have different perspectives though so do what you are most comfortable with!
Alan