Home » Featured, Headline, Reviews, SolidWorks News, Technology

SolidWorks 2013 – Previous Version Interoperability

18 February 2013 6 Comments

SolidWorks 2013 Previous Version Interoperability

SolidWorks Previous Version Interoperability introduced with SolidWorks 2013 probably isn’t what most users were wanting (or at least, were expecting), but I believe it’s what most users need.

When users hear, “previous version capability”, most think of being able to save their files back to an earlier version.  I believe this is what most users were asking for.  But I think that trying to carry back new features introduced in each new version would be fraught with major issues.  And I also think that most people asking for this type of functionality are those who are not on subscription…

SolidWorks Previous Version Interoperability allows a users with a previous version of SolidWorks (immediately previous, as in Service Pack 5, to be exact) to open current version SolidWorks files.  Previous Version - Part FeatureTreeThis feature packs a little more functionality than just using a neutral file format.  The mates and materials/appearances are retained in the previous version, and part features and assembly components are replaced with “Future version file” icons in the previous version; any in-context relations created in the previous version is kept intact when opened in the the current version.

In SolidWorks’ own words:

Previous Release Operability [sic] allows users of previous releases of SolidWorks to utilize and reference files created in the latest release of the software. Interoperability between Customer, Suppliers and Vendors is no longer restricted to the version of the software one contributor to the design process is using. Users eager to take advantage of latest features no longer need to wait for other contributors using a more cautious upgrade period.

Unparalleled collaboration allows users to leverage the powerful new features of the latest release, while allowing others to collaborate when using more cautious upgrade cycles.

Where I work, certain groups only roll to newer versions of SolidWorks every other release, while the group I am in generally rolls as soon as a new version is available.  So this functionality will be excellent for us.  But if you are working with someone who hasn’t upgraded for several releases (most likely due to not being on subscription); or you’re the one on a deprecated release; its not going to work for you, and you will have to go the neutral-file-format path.

Previous Version - Assembly FeatureTreeAll this being said, working through neutral files has never been that much of an issue with my work, and this functionality has never been very high on my radar.  As I mentioned above, I believe that the majority of the folks requesting this type of functionality are those who are not on subscription (or those who regularly work with those not on subscription).  I do commend SolidWorks for making efforts to add functionality that will enable those who jump in immediately on a new release to work with those who cautiously upgrade.

I will mention that after this feature was announced at SolidWorks World 2012, I was told that the reason they were limiting support to the Service Pack 5 level of the previous version was due to support issues.  They are having to expand their QA matrix to be able to field any issues that may arise, and there is a cost associated with that.  This leads me to believe that there is not a major limitation to being able to go back further, but it is simply a support/money issue.

What do you think?  Will this functionality be of any use to you?  Are you a trail-blazer when it comes to using the newest version of the software, or are you more cautious, choosing to let others work out the issues before you take the plunge?  Or are you not currently on subscription, and using an older version of the software?  Let us know in the comments!

Image credit: DS SolidWorks Corporation

Post to Twitter Post to Facebook Post to LinkedIn Post to Delicious Post to Ping.fm Post to Digg Post to StumbleUpon Post to Technorati Post to Reddit Post to Slashdot

  • Hi Brian,

    The only reason we are able to even provide such functionality as the Previous Release Interoperability is that SP05 of the previous release comes out AFTER SP0 (FCS) of the next release.

    All of the changes to the file format in the new release for configurations, mates, BREP geometry schema, attributes, etc. can only be known after they are finalized for FCS of the new release.

    We can’t travel back in time to add those things to SP04 or earlier of the previous release.

    So this is not a support/money issue at all, but fundamentally a technical reason why we cannot support this in SP04 or sooner.

    Vajrang Parvate
    Director, SolidWorks Product Development

  • Personally, I think SW first release at backwards compatibility is a joke. Not much functionality and barely usable. Understandably, we’ll NEVER get the SAVE-AS type of functionality (like in AutoCAD) but I can see a future implementation work like this:

    Open files in previous version LOCKS current feature set/BREP. Previous version of software may not know about new command.
    But you should be able to add new features in old version. Can’t think of any features that have disappeared in a newer version.
    Opening file in newer version prompts you to rebuild/save file.

    One can only hope/dream…

  • Johannes Anacker

    The biggest advantage of “PVI” is IMO, to avoid creating neutral files (Parasolid, STEP, …) to share with people. That neutral files will become outdated minutes later due to changes in the originally SolidWorks file, and you have to ask for latest version again, export as neutral, import to old SolidWorks release, replace in the assembly, …
    With PVI you can use your real latest SolidWorks data to assemble in the previous SolidWorks release.

  • Thanks for clarifying that, Vajrang!

  • http://www.four-faith.com/En

    Four-Faith is a professional manufacturer of Industrial Router,Industrial SMS Modem,HSPA modem,RS232 modem,RS485 modem,Serial modem,Zigbee terminal, Gprs router,M2M Wireless,wifi Router,3g modem, Hsdpa router, EDGE router,Hsdpa Modem, Gsm Modem,3g modem,3g router,gsm router,Industrial Router,LTE Router,4G Router,RTU etc. M2M router and M2M Modem products are mainly used in industrial remote control, environment monitor, water schedule, CCTV, security surveillance, and many other areas

  • Scott

    We are an OEM and currently on Subscription with 9 seats of Solidworks (Pro, Permium, Standard) and have many outside vendor who are forced to support multiple computer drawings packages to take advantage of features like Pack & Go. I can understand those vendors not being able to pay subscriptions for every computer drawing package out there. You could send a step file but then would have to dig through our network folders to finds the 100’s of drawings in a pdf or dxf format to send in order to just get a quote. Pack and GO does this for you automatically in a flat file that can then be put in a dropbox for the vendor to access. The problem is if they are on an older release they can’t read the file.