We have three seats of SW and three users. We are storing all of our files (>3000) on a server and accessing them with Windows File Explorer.
How much easier would our lives become if we transitioned to PDM? (Sorry, I'm an engineer...I can't help it. )
We need to justify the cost.
SolidworksSolidworks Pdm/enterprise Pdm
It is impossible for anyone to provide a useful answer to that question without an in-depth look at your specific use case and that person needs to have enough experience with Solidworks PDM to know how to apply it to your situation. Anything else will be someone's experience based on their use case which may or may not apply to yours.
...or marketing, could also be a response based in marketing.
Ironically, my response is based in my own experience for one unique use case.
Interesting ... I never thought this kind of estimating ever exists
The only time two people need to work on the same part would be if one has a large assembly open and the other wants to work on a component. But that's pretty rare for us (relatively speaking).
The biggest push right now is tracking revisions and being able to roll back if something heads south.
Oh yeah:
Do you need ot see where a part is used so when you decide to make a change, you see how many assemblies are going to explode? Then yes, it'll be easier.
I believe regular check in is required to "roll back".
I make daily and monthly backup.
Only once I needed something passed the monthly.
Daily saved a few blow up assemblies.
"Roll back" term in PDM is kind of a tactical nuke option to permanently remove versions of a file, something usually only Admin has access to and hopefully not part of normal work flow. However, have versions of files is nice. Once a user learns that they can check in and keep checked out for "exploratory modeling" and then go back and grab the best version (so long as they commented well on check in) then check that in as the new latest version can be handy.
Flip side of versions is there can be a lot of information there when you start looking at Where Used to understand which version(s) are using which version of files and which version was used when it was checked in by someone and which version you're looking at. If you can simply always work with the latest version that simplifies things. Some users pick it up fairly quick, some others... well, I haven't lost hope yet. But since you only have a few users you should be able to get them up to speed.
Sounds like all you need is PDM Standard. What version/s of SW do you have, Standard, Pro or Premium?
We have 1 seat of Premium, 1 seat of Pro, and 1 seat of Standard (soon to be upgraded to Pro).
I thought PDM Std allows only limited revisions of a part?
A team of three CAN work quite effectively without PDM. But it takes discipline.
PDM takes resources, human and otherwise. Someone has to get good at administrating the PDM. Someone has to set up, troubleshoot, maintain, upgrade, and take the 2AM calls.
Another plus in light of current events: PDM is better for remote work, especially if multiple users are on the same project..
Most small companies have either new SW users, or current users without training. Each user runs rampant using their own file structures. Over time, there are duplicate files and it becomes more difficult to maintain and track. I suggest at least PDM Std, get training on it.
So, when you upgrade that seat to Pro, you will have access to 3 licenses of PDM Standard. So you're not out of pocket one penny.
You could set up PDM Standard on a Windows Server today. Here are some instructions:
SOLIDWORKS PDM Standard Server Installation
SOLIDWORKS PDM Standard Client Installation
No, PDM Std. does not limit the number of revisions of a part, AFAIK.
The above doesn't apply to PDM Standard without some workarounds.
One set of "backup" is on an hardware encrypted USB drive.
Ready to work from home everyday.
Wow.... just pay me half of it and I'll be happy to fly over to your place to do the custom setup and training ...
Does all three work on same project at the same time? If yes, PDM.
Or they just need to check other's work when needed? If yes, you can just sync local to a network "backup".
Do you use toolbox?
Share library?
While that's a nifty sales gadget I'm getting a feeling it's not very realistic. It just told me that implementing a PDM system would save me 767K a year on 5million in sales with 10 engineers. That would be super awesome and all....but no :-)
I think it's actually easier to justify it by how much time you've already lost.
How many times have two people been working on the same part and one over wrote the other?
How many times have files been moved and assemblies blew up?
How many times have changes been made and then you decided the old idea was the better one?
and on and on
Look at all the problems you think a PDM will save you and look at the time you've lost. If you don't see any time that would have been saved already, very possible a PDM won't save you much time.
That stuff happens all the time (!!!) here. Along with having poorly named folders that can't be renamed, files scattered hither and yon, duplicates, etc.
I have a very limited understanding of PDM, though. Does it keep the folder structure, or is everything "tree shaped"..???
as Ben says, our input will be limited. but I see a few big potential advantages for you
Yes it keeps folder structure, but unlike win explorer you can move files around without losing references. You can also set up no duplicate names for SW files. You can make whole new assemblies with similar parts/reuse other parts using the copy tree function.
you can set and folder structure you want. it mostly looks like windows explorer (different colored icons) If you decide to browse through it. but you should generally just live in the search tool.
(and you CAN rename folders outside of PDM, but it is WAY easier inside )
It has what ever folder structure you set up. I have seen everything in one folder, in folders based on file types, in folders based on projects and in variations of these. And the nice thing, you can easily move files from one location to another and the links are maintained.
Are you concerned about having two files of the same name in two different folders and having one changed but not the other? PDM can control that if set to. On a big project that mistake alone can pay for the setup cost of having PDM standard implemented.
It was always so hard to break people of the click click click to this folder. Seriously, top level search is so easy.
we are goiong on 10 years with PDM, and some people STILL browse... worse yet, they train new people in their depts to browse...
PDM will not prevent duplicate files...it will prevent you from checking in duplicate files which means other people will not have access to them.
PDM will not prevent files being everywhere and just like solid works doesn't care where the files are for the most part.
Not sure what you mean by "Keep the folder structure". PDM like Jeremiah mentioned, is basically a specialized windows explorer. You can create any folder structure you'd like.
There would be diff. approaches.
Few yrs ago, we, like you, all shared the files in the server and I was the one who kept track and manually updated the rev. It was time consuming for checking the files at release. So I ended up learning wPDM and set the it up for the company. it was a long learning curve but really helped out in term of controlling the rev
Then again, I did the same thing with PDM standard couple yrs ago when SW stopped supporting wPDM
I guess you already know that if you own a Pro. or Pre. license, then PDM standard or old wPDm includes in the package while you have to pay for PDM Pro.
Now it's up to you: pay VAR to setup and train you guys to run PDM or learn and do it yourself.
One thing for sure you'll be sorry not to do this earlier soon you get PDM up and running
SOLIDWORKS has posted their PDM ROI calculator. You can find it here: SOLIDWORKS ROI Calculator .
Hopefully this helps you evaluate!
there are limits to PDM standard, but I don't think revs are one. you ARE limited to a single workflow and a max number of workflow states. and no API.
if you are serious about implementing PDM, my two biggest recommendations are:
I was comparing Std vs. Pro and I thought for sure they were limiting revisions. (I am wrong sometimes.)
I also thought it didn't have the option for restructuring file systems...(?)
Our IT guy claims it will cost us $18K to upgrade to the correct SQL version for PDM. That seems a bit suspect...….
I think $2000 is a very good deal. If if recalled correctly, I did ask for the quote and it's about 10K+.
Then you don't need PDM
PDM Standard can automatically create PDF files and add to the vault when the file gets to a point in your workflow process. It cannot do that for DXF of flat patterns. PDM Professional can do that for DXF and can also save the exports to location outside the PDM vault.
PDM can rename files and move to different folders, but you still have to be careful with that, but not as bad as no PDM system. Issues in PDM can occur when someone else has a file open in his assembly when you move that file., but with only three users good communication can overcome that issue.
Still good idea to maintain folder and file structure to be PDM compatible.
Having PDM is a plus to you, but it's not a must
I guess it depends on what you are looking for. Restructuring the files, as in moving files from one folder within PDM to another file within PDM? Yes you can do that all day long and PDM keeps track of the connections. Replacing one file with another, not so much.
That goes for the Pro version as well....???
Forgot to comment about Revision Scheme. You can have only one revision scheme, but that one scheme can include for example an Alpha-Numeric number for major-minor revisions if you need it.
yes - PDM std and PDM pro are the same software - just std has some features disabled or limited by licensing, and the SQL lite
yes
Excellent answer!
Two further points that have not yet been mentioned.
Since I work in custom machine shop, reused parts has different part number in different projects.
We don't stock them. We don't batch produce them. So just treat them as different parts is easier.
Valid points. I said I did it alone, but same as you I did get assistance. It consumed a lot of my time, but I do know how it works much more intimately. And you are going to need an "administrator", so I guess there's a good argument to do the install and configuration yourself.
PDM Standard runs on the free SQL Express. If you go with PDM Pro, yes there are some substantial SQL fees.
Please take some time to read info. from SW to understand the diff. between PDM std and Pro;.
Otherwise, you'd be confused between the two when people discuss the subject without ref. to the Std or Pro
You're the one to know what you need and find out what version fits yours
The pro might includes features you never use such as PDM std only allows one workflow and our company never need extra workflow which is available from PDM pro
Here's a comparison on Javelin's website:
SOLIDWORKS PDM Standard and Professional Comparison
From your description, it doesn't appear you need Pro.
As has been said, Std uses a freely provided version of SQL lite. So while your IT guy is probably correct for PRO he is wrong for Std. We did have our VAR give us a quote and it would cost around $2000 to have them setup STD on our system, migrate some of our files and then provide a day's worth of training. While you can use the provided information from Javelin to set it up yourself, I highly recommend having your VAR do it so they can help if you have problems, and for the training to get you started. While I don't find PDM that hard to grasp, there are maintenance items that you can easily miss if you attempt to go it alone. Plus the VAR has experiance that can help with suggestions on the setup.
I agree with what Jim states. Working for state gov't we didn't have a mechanism to pay the VAR for help for a program we already own that we're already paying the VAR to maintain (let that sink in). DS really should pay the VAR for setting up PDM Standard, IMO. So, I set it up myself. There was a lot of time involved with the install and setup. $2000 is cheap for what you get.
I had an interview with a place that had about 5 users. Their file-keeping was a mess. Then we went to their paper drawing library. I said to the the interviewer "Would you keep all these drawings in a leaky basement? Because that's what you're doing with your CAD."
I was hired, and immediately tasked to create a PDM system.
p.s. It worked fine. Not as slick as the store-bought variety, but it did the job.
Michael,
From what I have read so far, PDM Standard would do what you say you need. I do have a few other questions though. You have three SOLIDWORKS users, but what are their deliverables, SOLIDWORKS files or pdf's of the drawings? Are there other file types on your current file server that other users have access to? If so they would have to have at least viewer licenses that would have to be purchased on top of the one SOLIDWORKS Standard Upgrade. Are there other file types you want to revision control, Word, Excel, or AutoCAD?
I believe it just depends how you'd get the most from VAR. I myself setup the PDM standard for the company but I would give lot of credit to VAR as our VAR provided a big help including few remote sessions. The advantage of doing yourself would help you understand the package better which save you time later on for issues.
- What you're explaining is more than can be fixed with a PDM, if you only have (4) four users and that many issues, a PDM won't just be the "Answer" you can get ferhoodled just as easy with a PDM system in place. Here we have four users and have never ever run into the issues you talk about, it's file structure, file structure and file structure, and a swift kick in the a$$.....
I need a little trip, let me know when you want me there, we'll figure it out..
Totally agree with
PDFs and DXFs are the deliverables. PDFs for drawings and DXFs for laser. Of course we have .SLDDRW files but those aren't available to the floor. We don't really need a system for MS Word files, etc.
I've been doing some more research and I've got a few more questions on Std.
-Can we still restructure our files without blowing up assemblies?
-What does it mean by "limited to 2 revision schemes"?
Thanks a LOT to all of you guys. This place is really good!
My hope is that with a good admin (me.... ) we can manage it better and keep others from ferhoodling things when I'm not looking. Also set things up properly with renaming folders, etc. so everthing is easier to manage. We also have situations where Bracket XXX is used under a model file structure because it's a child part; six months down the road we use it on another model and bingo, copy or cross-reference with a dumb folder structure?
As far as a trip, I'd be thrilled to have you here. We're enroute to the UP, ya know.
i love the discussion