Solidworks PDM Professional is... well, it's complicated

As an ardent proponent of Solidworks Workgroup PDM, it was disappointing to come to terms with its end of life. Originally developed by Design Source Technologies, Inc with president and co-founder Jim Foster, the PDM tool was entitled PDMWorks. It was out-of-the-box basic and simple all around, much to the delight of administrators and users alike. Solidworks recognized its value and acquired it, renaming it as Workgroup PDM where it continued to be appreciated as a reliable file management tool. Based on a flat windows folder database structure, it has understandably been showing its age and being included with Solidworks Premium and Professional licenses was not a revenue generator in and of itself. Now with its demise, the alternatives parlayed by Dassault Systemes are Solidworks PDM Standard and Solidworks PDM Professional. The later formerly known as EPDM or Enterprise PDM, was acquired from Conisio @ 2006. Based on Microsoft SQL database structure, Dassault Systemes has put forth great effort to promote it as a "data management solution for organizations large and small", with scripted information that makes for a good first impression.

Like most marketing and sales related impressions though, it's what is not being said or shown that needs to be asked. For PDM administrators, the dilemma is that you simply might not have a good working knowledge of a product until you've... well, worked with it. As such, it isn't always apparent what questions to ask until you turn a corner in your understanding and suddenly realize you don't know anything about what's next, or how one aspect relates to or controls another.

For Solidworks PDM Professional, from the online presentations to the VAR sponsored demos, there is a clean polished display of what it can do, and it looks and sounds great. It's from the point of commitment however that things become... well, it's complicated. From the perspective of transitioning from Solidworks Workgroup PDM to Solidworks PDM Professional, here are some things that if not already apparent, certainly need to be discussed with a VAR when you hear them. This is especially so if you are anticipating a contracted statement of work (SOW) prior to implementation.  

• "easily migrate CAD data"  This expression sounds like everything will be taken care of for migrating your data. If agreed upon, only the most recent CAD files will be migrated to the new vault in the same folder structure arrangement. However, they will be in a "legacy state" that will most likely require you to manually transition each file to a working workflow if you want them in a working state. Also, none of the PDF copies of drawings contained in the Workgroup PDM vault will be brought over unless you specifically request such, because after all, they're not CAD data. Yes, if only you knew what to ask.

• "have it all set up"  This expression sounds like everything will be taken care of and you will simply need to show up and turn the key. From the initial consultation of current workflow processes, to the Administrating Solidworks PDM Professional Training you will begin to grow in your awareness that most everything required to make your PDM system operational will need to be learned, setup and tailored to fit your needs. Some points of application might be easier to understand, others will be totally new concepts that will take time to understand, implement, and test. Once understood, additional questions will inevitably arise. The VAR training includes examples on many points in the manual, but there really isn't enough time to cover every aspect in detail, nor the subsequent questions that naturally arise. The VAR will initially take the lead in developing each of the needed elements for your PDM system, and provide assistance along the way, but the operative word here is "assistance". Likely, you will receive assistance as you request it during the subsequent weeks that follow deployment. However the Admin is more or less left to discover what works and what doesn't, followed by head scratching, on-line research, requesting assistance or direction from your VAR, development and testing. Yes, if only you knew what to ask.

• "have any questions"  This expression too sounds like everything will be taken care of if you should ever have a question. As already discussed, you WILL have questions that arise only after you have made advances in your working knowledge of the software. Depending on how you arrange your workflow and transitions, some aspects of PDM Professional can be automated within PDM, others will require knowledge of API or dispatch programming. This will apply if you want to simply update a drawing when changing states such as from preproduction to production, or to simply update a drawing Revision Table with revision information. For example, would you know to ask if the Solidworks Revision Table works for Solidworks PDM? It's not a stupid question. It really doesn't work. So you will need to use a General Table edited specifically to function as a revision table. (Update: with the 2018 release, PDM now integrates with the Solidworks Revision table.) As these types of boggling issues surface, the VAR may or may not provide the hand-holding assistance you would like to have to address your questions as you navigate to the next corner and emerging question. In fact, you most likely won't be aware of initial shortcomings in your preset workflow and transitions until you realize you don't have the functionality you expected. All of this leaves the Admin in the unenviable position of having to make these edits to tailored PDM functions as projects of themselves, while communicating to the engineering team why Workgroup PDM used to perform all of these functions but 'we can't right now with PDM Professional until we do more programming'. Programming, which in all likelihood will again require some form of research, requesting assistance or direction from your VAR, development and testing. Yes, if only you knew what to ask.

Those who have successfully navigated the implementation of Solidworks PDM Professional are to be commended. They have garnered a worthy skill set using a product that possesses a puzzling array of potential. To put it judiciously... it's complicated. It's certainly not what everyone wants but seems to be the only choice Dassault Systemes wants to offer. With years of use behind it, isn't it strange that Solidworks PDM Professional would be so unduly complicated, yet in many ways does less out-of-the-box than Solidworks Workgroup PDM?

In summary, Solidworks PDM Professional is anything but turn-key. It's an auto mechanic dropping in a new engine for you, tightening it to the frame, showing you how a hose or a cable connect, and saying "you can deploy in as little as ten days... to capitalize on new opportunities faster"! Sure, out of necessity you will figure it out... eventually,... but it's complicated. You asked for an expensive new engine and naively thought you could just show up and turn the key, because you didn't ask the right questions.

Epigrid... on the forefront of Cloud-Hosted EPDM

Recognition as to the benefits of a product data management (PDM) system is growing among many SolidWorks CAD users.  Higher-end PDM systems such as SolidWorks Enterprise PDM however, are often out of reach for most small businesses or independent CAD users.  In effect adding insult to injury, not only is the high cost of EPDM software an obstacle, just supporting such a system requires a real working knowledge of information technology.   So what solutions are available to bridge the "wants versus needs" gap inherent with current CAD PDM packages?

One company that has addressed this niche is Epigrid.   As to why he started the company, Chief Technical Officer Chad Garrish states "I saw a hole in the market between what engineering wanted, and what IT could really give them."  Founded in 2012, and based in Suwanee, Georgia USA, Epigrid provides affordable cloud-hosted EPDM.  Combining their experience in engineering data management along with server, network and  cloud management, Epigrid has made their services, vault configuration, and support flexible and scale-able to any sized group or budget. 

Notably, Epicure's approach to security reinforces they have a real grasp on what CAD users need in a hosted PDM service.  The importance of security is evident by their arrangement of privately hosted architecture, multiple layers of advanced security methods, constant data protection, HIPAA-compliant data centers, and disaster recovery center.

Epigrid also demonstrates an openness and transparency that is refreshing among young startups.  Chief Information Officer Lewis Halski warmly invites those interested to view their FAQ videos, and to call or email with questions.  With short to-the-point videos that reflect IT sensibility, and all the EPDM cloud-hosting tools one could ask for, Epigrid is on the forefront in providing a unique service that addresses a real need among many CAD users.

SolidWorks Workgroup PDM - Perhaps the fastest ROI one might ever see!

Avoiding additional license and support costs, SolidWorks Workgroup PDM might just provide the fastest CAD file management 'Return On Investment' (ROI) that one might ever see!

To be certain, Workgroup PDM is not for every company. Rather it seems to be ideally suited for smaller-sized engineering departments (1-15) that could truly benefit from a CAD vault system, but who do not require a full-blown PDM system. Of course, committing to any CAD vault system is an investment, therefore there are a few questions one should consider. The answers will build confidence in the decision making process, while gaining important 'buy-in' from those directly affected with the decision.

What are the Costs?
Since Workgroup PDM is included with each seat of the Professional and Premium license, the upfront monetary investment is $0. The only intrinsic costs to consider are simply time for setup and providing a server.
Please note that one could also choose to simply use an existing computer that could function as the 'vault server', however many CAD Administrators have preferred to assign an actual server that is separate from any of the users computers.

How easy is it to Implement?
Anticipate that a reasonable amount of time will need to be allocated for preparations, setup, testing, implementing, and training. These aspects will initially affect the CAD Administrator and in-house IT, but is quite easily fit into the schedule, per se. Bear in mind that the benefits will far outweigh the time expended.

How easy is it to Use?
Because this is a SolidWorks Add-In, most will find it is very intuitive. Access to the Vault is conveniently provided through either the SolidWorks Main Menu / Task Pane or through SolidWorks Explorer. The usability is very straightforward and basic. Albeit limited, there are a number of capable features that make this a very practical means to manage and control files. Typically, SolidWorks users who previously had no PDM system to manage their CAD files will quickly embrace Workgroup PDM as a significant contributor to improved performance.

What Support can be expected?
SolidWorks has openly acknowledged that for the foreseeable future they will continue providing and supporting Workgroup PDM. They have also stated explicitly that there will be no further development of the Add-In.

That being said, it then becomes a personal decision as to whether to commit to a PDM system that in all probability will eventually be phased out. Does the effort to establish a temporary PDM system outweigh the alternative of not having one. Probably so, as the benefits become instantaneous.  It also places one in a better position to migrate organized CAD files to another PDM system in the future, should the need arise.

Latest & Greatest? ...When to start running the latest SolidWorks CAD release

The anticipation of a new release of SolidWorks typically carries a measure of excitement! After all, we have become accustomed to seeing recognized design and software needs addressed or improved upon. As SolidWorks users, we certainly appreciate the efforts expended toward such development and the benefits that each new release brings. But this also means that each year we are faced with the question of when to start running (a.k.a. committing to) the newly released version. While some individuals or companies have a prearranged plan or standard, others simply wing-it as it were, and hope there will be no repercussions.

There are a number of factors involved which should be weighed in the decision of committing to running the new release. These should include awareness of:

• significant user interface differences
• limitations of version compatibility
• necessity of service pack upgrades
• file collaboration
• PDM integration

As with anything new, the more information we have in advance, the better our decision making capability should be. This is certainly true regarding the above points as well. It is therefore prudent that one would take advantage of any opportunities to learn as much as possible about the newest release prior to determining when to make the commitment. Most VARS (value-added resellers) of SolidWorks will annually hold a 'premiere' event to showcase the newest version and highlight the main aspects that will interest and impact users. By all means attend, if possible. It is probably the most time effective means of seeing the new features and software in action, and the most cost effective as well, since the event is free.
User Interface Differences
These differences should be almost self-evident. Because interface upgrades are intended to make the user-experience more efficient and effective, they are probably the most eagerly anticipated aspect of the new release. The only concern should be the learning curve involved. Regular users will most likely catch on quickly, but bear in mind that significant interface differences will mean your work will take a little longer until becoming accustomed to the new methods, icons, shortcuts, etc.
Version Compatibility
This is simply an awareness issue, especially for novice users, but is vital knowledge in determining what version to use in creating new files and when to commit to running the newest version. SolidWorks files are not backwards compatible. In other words, you can save an older file version into a newer version format, but you cannot do the reverse such as saving a newer version into an earlier version format. Yes, once a file is in the latest version, there is no going back with the exception of completely redoing your design in the earlier version.
Service Pack Upgrades
This too is an awareness issue. No matter how enthralled you or anyone feels about the newest released version, remember that it is not perfect! It will require necessary upgrades to work properly. This has been evident year after year, and really goes with the territory that SolidWorks lives in. The constraints of having to release a new version each year (read 365 days) limits how thoroughly the alpha and beta versions have been properly tested. Therefore, some choose to exercise patience by waiting until a number of service pack upgrades have been released before committing.
File Collaboration
If you are working in collaboration and sharing files with another, then this will be a major concern and most likely one of the main limiting factors in the decision to commit. Ironically, however, it may also have bearing on the impetus of when to commit. It is directly related to version compatibility, but additionally brings in the factors of other designers, toolers, or manufacturers that you may be working with. Typically, whomever in the design chain implements the newest release causes the others to commit. If your design chain goes in one direction, it may not be such a concern, but if your design chain tends to flow in both directions, then there may be issues. While it is not necessarily a negative, it is important that the commitment be communicated and agreed upon, or else one could run the risk of introducing a delay in the development process that could easily have been avoided.
PDM Integration
This should only be a concern for those who manage their CAD in vaulted PDM systems, or work in collaboration with those who do. Non-SolidWorks PDM systems can be intensive and expensive operations for a company and carry compatibility issues such as Viewers, which allow others in the PDM network to view a CAD file without necessarily having the CAD software. In this type of scenario, the PDM system may exert a large measure of influence on when, and even whether one commits to newer releases. If you are working in collaboration with a company that uses a non-solidworks PDM system, ask what SolidWorks version they are using before assuming they are running the latest. Note that some large companies have been known to be actively running SolidWorks versions that are at least 2 years old simply because of the restrictions placed by their PDM system and the expensive upgrades that are involved in keeping up with corresponding CAD releases.
In summary, by being cognizant of the above issues and weighing their relevance, the decision as to when to commit to running in a new release may become self-evident. That being said, some have determined that a specific calendar date, extended some months after the initial new release, is well suited on which to coordinate committing to running the latest release. Others may choose to be flexible, for example by waiting for a specific service pack upgrade (i.e.: 2.0). As with many business issues, communication and awareness will always be the most valuable aspects in the coordinated decision to commit to running the latest released SolidWorks version.