Hello all,Is it possible to publish .pro (road surface) files from TBC directly to WorksManager so that SiteWorks user can open those files on their TSC7 controller?
Greeting, thanks in advance for your response.
At this point for use with SCS900 and Siteworks I would still recommend that you use the SCS Data Manager to do this kind of conversion - if you have a LandXML that contains an Alignment and a Surface, SCS Data Manager has the original File Flipper and that converts LandXML to PRO no problem, it also organizes it into the correct folders for Sites, Designs and Work Orders as required for SCS900 / Siteworks.
SCS Data Manager was written for the Field SPS products whereas File Flipper and Works Manager have been written more for the machines and they really don't support the SPS systems that well when it comes to Roads.
As a user - I would personally always use TBC - appreciate that maybe the customer is reluctant to do so, but it is so much easier to load the data and preview it and then push it out to whichever systems that need it. If you import a LandXML file with an alignment and a surface in it, you can make a corridor using the alignment and use one instruction - a surface instruction to add the imported road surface to it to make it into a corridor. You can then export to SCS900 as a PRO or SIteworks as a VCL or PRO or to GCS900 / Exarthworks as as SVD/SVL or DSZ in one pass.
You do not however need to create a Corridor to export an Alignment and a surface as a PRO file - you can simply select the alignment and surface and output it as a Road Surface model and that works well also.
The challenge with Flippers is that you have to know what is in the source file and how that will be converted to the PRO and also you have to 100% trust that the data in the source file is good - if you bring it through TBC you have validation tools to make sure that is the case and you 100% know what you are working with and that when you output the data it will be 100% what you need for the field system.
The Field Data Edition of TBC is a good start point, but if you want to go down the Flipper route I would use SCS Data Manager to create the data for those devices and then load it into Works Manager as required.
The TBC publish to Works Manager always publishes a VCL file to Works Manager, and Works Manager does the data conversion when it delivers the data out to the controllers and machines i.e. The machines get SVD/SVL if they are a GCS900, they get a DSZ if an Earthworks, SCS900 gets a PRO file and Siteworks gets a VCL file these days on TSC7 or Tablet etc.
If there is an issue I am missing here let me know and I will let you know the answer
Thank you Alan for the quick reply.
I suspected that there would be such an answer, because I tested a little. Our client purchased SPS receivers with TSC7 and SiteWorks. They also purchased WorksManager and TBC. The problem is that they do not prepare corridors in TBC, but receive from designers a ready surface and alignment in an xml file. Then they upload the files to Worksmanager and then send them to SiteWorks. They blame us for not being able to view the cross section at SiteWorks, and they are right. When I prepare a .pro file for them from the xml files provided by them and upload via USB, the cross-sections in SiteWorks are displayed. My idea is to teach the client to create pro files. because there is no customer willingness to learn to create corridors, at least for the moment. Alan, do you have any other suggestion?
Thank you so much Alan for your help.
This answer clears up all my doubts. I will present the client with three options on how he can export road surface data to SiteWorks. Depending on the competences of people (surveyor, engineer, foreman), each of them will choose the most appropriate option.
Retrieving data ...