Trimble Business Center

No matter what I include/exclude using the "Create WorksManager Design", when opening in Siteworks I will get the following error "The VCL design file contains data that is not supported by Siteworks".  The surface dropdown in Siteworks always has "(No Surface Needed)" and does not have any other options even though a surface was selected/added from TBC.  I have tried just having one surface with nothing else and it still does not work.  I can create a TTM out of the same surface and that can be opened just fine from Siteworks.  Siteworks is running version 1.20.20100.  TBC Version 5.21.  Not sure what is going on.

What Design Option are you selecting Surface or Road Surface or User Defined? Have you tried the 5.3 version of TBC that was released last week?

Let me know and I can take a look - but we likely need your data to debug this as I have exported many Surfaces personally to Sitework as VCL files and they have worked - so it may be that you have something in the file that is causing this issue to arise and without the data it will likely be hard to recreate what you are seeing. VCL Format Is a Version Dependent Thing - the Version of TBC that you are running and the version of Siteworks that you are running is critical.and the VCL Versions need to correlate because TBC can create objects in a Newer Version that were not available in an earlier version etc. It seems that you have Siteworks up to data and 5.21 was released with it at ConExpo so they should match OK - however 5.3 was just released last week so I need to check with the SPS Team what their VCL Correlation is currently.

Alan

For the purposes of clarity, I just had a discussion with the TBC Development Team on the VCL Library use in products like Siteworks. TBC at each release will have a new VCL Library support and it can write out everything that TBC can create and Read it back in again. The VCL Library that is incorporated into the Field Systems to decode and use VCL Data may at times get outdated by a new version of TBC if the Field System is not updated in parallel. However there is a Flagging System in the Field System Library that identifies object types that are not supported with the version of library and those objects will get ignored.

For example, when we added the Extended Sideslope functions to TBC, the VCL library would write those out and read them back in again no problem. If a field system was able to read the corridor models but had an earlier version of the VCL library, those new extended objects would be ignored, so the corridor would have no sideslopes in the field system until such a time that the field system was updated with the latest library and the field tools to leverage those extended object types.

When we look at objects like Alignments, Surfaces, Linework and Points which are primarily the objects in use in the field systems today, they have not changed much if at all over the past  so they are unlikely to trip up because of a VCL library change.

Hope that this is helpful information

When I receive your file we can take a look to see what is happening

Alan

Shaun

Thanks for the data - I am seeing the same issue so have forwarded to dev for review - will let you know when I get an answer

In the meantime output a dxf and ttm using export and then add them to a design in Works Manager - that works as a fall back here

Alan