At my company, we have been using 3DVia Composer to perform service & repair procedures on vehicles virtually. On a drive we have ten folders. In each folder is a 3D vehicle. This vehicle is broken into functional areas and each on is saved in the .smgXML/.smgGEOM ("Shattered"?) formats.
The intent was to have our users create .smgProj files for each virtual procedure and link to this shattered data so that we don't duplicate the same cad data over and over again. Another benefit is that we can essentially have access to the entire vehicle but only open the functional areas we need with the unloaded modules taking up no memory.
This way of working seemed logical but has not worked well for our team. Here is a list of the issues we saw:
1) team was thrown by the .smgProj logic
2) team was confused by the folder that is created with .smgProj files
3) the source data somehow got tampered with
4) .smgProj files lost their linkage to the source data
5) various Composer files (views, scenes, xml, geom, etc.) found all over the place; even inside our source data.
We are now just using the simple .smg format.
For what we are trying to do...
1) what is the intended way to work with 3DVia Composer files?
2) how can we secure our source data so that users [I]can[/I] link to it but no one tampers with it?
3) should our source data be saved as .smgXML/GEOM? or .smg?