3DVIA Sync and Automated Deliverables
A common problem many companies face is the ability to have deliverable documents, like web images, catalogs, and technical illustrations, mirror their final product. Because of the dynamic nature of design and engineering, it is often a struggle to keep this downstream output up-to-date without utilizing some type of automation. Using 3DVIA Sync ensures changes that have been made in the upstream CAD systems are reflected in the downstream content created in 3DVIA Composer. 3DVIA Sync gives the user the ability to:
- Publish and update output from 3DVIA Composer:
- Overwrite an existing set of files, so the latest file is the only available file
- Never overwrite files, so a library or history of files can be maintained
- Allow user interactivity, so a user can decide to overwrite or keep existing documents
- Save batch job settings to an XML file for future use
- Import and export 3D data into 3DVIA Composer:
- Export 3D formats like .STL, .VRML, .OBJ and more
- Import 3D formats like CATIA, Pro/Engineer, SolidWorks, STEP and others
- Update custom generated PDF output
The powerful link that is generated between 3DVIA Composer and the CAD system is enhanced with the use of 3DVIA Sync. Users can schedule 3DVIA Sync to run on a daily, weekly or monthly basis. The system can also be set to run on demand. Beyond being able to simply run the tool at a specific time, users also have the ability to save settings for particular types of updates and apply different preferences for distinct runs of the tool. For example, you would like to have the CAD models only imported on the first of every month, but want to only export the image data on a weekly basis. You can save these two different settings and have them run at their designated times. And with available integrations to PDM like ENOVIA SmarTeam, 3DVIA Sync can be driven on-demand by events taking place in other systems (i.e. when a new version is checked in, update these related deliverables but not these others). With this type of flexibility and control, you can now be sure that your technical documentation accurately matches the CAD data being provided to manufacturing.
Companies have numerous tools with which they generate a staggering amount of documentation. You can minimize the time it takes to update the 
documentation by processing only changed data. It is imperative that a system is in place to ensure theses documents maintain a level of accuracy. You don’t want to rely on a manual process. Take a look at 3DVIA Composer and 3DVIA Sync to save you time and improve the accuracy/timeliness of your documentation. If you have questions about these tools or need help determining how they would benefit your organization, please contact us.
Tags: 3DVIA Composer, 3DVIA Sync, CATIA, ENOVIA SmarTeam, Pro/Engineer, SolidWorks, technical illustrations
Read more posts by Johnny Molica
March 2nd, 2010 at 12:23 am
Just to be perfectly clear: to run 3DVIA Sync “automatically” or “unattended” (ie: scheduled, command-line, by trigger, etc) this actually requires 3DVIA Enterprise Sync.
March 4th, 2010 at 12:48 pm
Thanks for your feedback, Garth. Absolutely. I was trying to avoid going too deep into the subtleties between various product modules in making the point, but you are right to mention this. 3DVIA Sync does does let you update your Composer outputs automatically, but if you want schedule these updates or interact with the tool programmatically, you need 3DVIA Enterprise Sync.
April 8th, 2010 at 2:19 pm
does this work if the models are all located in folders inside EPDM?
April 9th, 2010 at 9:34 am
That is a great question. You can run this when files exist in EPDM. However, here it comes, there is an SPR from SolidWorks if the Enterprise PDM add in is turned on. 496082 is the SPR, and it is currently an open issue. One work around is to move the files outside the vault and then move them back in after the update. The second is to run Sync on a system that has SolidWorks but does not have the Enterprise add in.
You may also want to check out article S-037733 in the SolidWorks Knowledgebase.