We have MS Server 2010, gigabit network, 2 people that would be using PDM and curious if it's worth the hastle...any pros/cons?
In my opinion, PDM is about revision control not necessarily about the amount of users.
In considering it ask yourself:
Do I want to maintain an effective revision history? Able to go back and see old revisions either in the prototype stages or ECN control.
Do you want a safe and secure vault location for your files?
You also have to ask is it always going to be only 2 people? Or will there be more down the road. If you do it now it will be in place for
future users and will establish a firm foundation for your file structure.
I hope this helps you.
I would say if you need it, you know you need it. There is a large cost and curve to implement. I have thought about it for here where I work but we have other RN/ECN systems that capture the prints (which could be done without them by just exporting the PDFs to the folders with the rev added) and we in the CAD department copy off the parts to an obsolete folder to keep one revision back, we don't need any more than that. So we don't use PDM stuff. just my 2¢
I used PDM workgroup at my old job and actually I was an administrator.
At my present job they are considering it, but they have a system very similar to what you described.
But, we have 30 or more users and their system is a mess.
Duplicate files is a hugh issue with users copying files to their own file structure.
PDM eliminates duplication issues.
Depending on what version of SW you have it should not require a great deal of cost to get started using Workgroup. It comes standard with the Pro and Premium versions. it is fairly simple to set up and use. I think a previous responder was thinking about Enterprise as being expensive and requiring a good deal of training.
Jeff, I agree with you. Upgrading ones license to include PDM Workgroup should not cost that much.
In fact depending on the reseller one might get a good discount.
Buying a PDM Workgroup license is fairly expensive by itself. Like I said in my initial post, if you have SW Pro or Premium license, you already have the program with no extra purchase cost. If you are going to add it to a basic SWorks license, be sure to check whether the additional features included in the Pro or Premium will take some of the "bite" out of the cost. By all means, check with your VAR for any specials they may be willing to help you with.
I wasn't speaking of outright costs, I was thinking of hidden costs (energy to set up and learn) EPDM is just crazy, but there is cost involved with PDM, no matter what version you talk about.
2 people ... heck, it's great even for one person!!!
it's easy to use.
Why would you want to use PDM? In other words, what is your real need/desire that you expect this to fill? Based on your answers, you'll probably get some good feedback from others.
As for me, I control revisions flawlessly with my own system (which I've written about many times now). Simple, easy, effective. No need for any further points of failure between my data and me, and I like simplicity of systems.
Would PDM allow both your users to access data at the same time--or would it prohibit it more than you like? Or would you need to change your work-flow too much to accommodate the new software? Be sure to ask (and receive answers for) the questions that aren't spelled out in all the marketing. No use having any buyer's remorse.
I just started using PDM workgroup when they upgraded my SW to Pro.
I like it for many reasons not just rev. management.
The best feature is the simplicity of checking the project out from the server and working locally from my "working folder" on my C drive.( eliminated crashes on large assemblies) Then checking it back in and retaining the project locally with out worry of file replicating.
There is very little learning curve to overcome.
I looked at your profile and see that you are in the automation business. PDM workgroup would reduce the amount of files on your server when you use vendor models repeatedly while keeping the placeholder for the model in the same folder as the project.
I say go for it.
That is another great point Brian. It keeps the files stored locally to a minimum
because of the ability to delete them upon check in. Forgot about that feature.
Except I would recommend having the files checkout onto a network drive.
It can get backed up that way.
PDM all the way for me!! Not Enterprise far too expensive.
It's simple to use and you can easily set it up to the way your organisation works.
The main benefits we have are;-
1) No duplication.
2) Controls all the access problems in a multi-user environment.
3) Secure, no chance of someone deleting a vital part.
4) Full tracabilty of who did what and when.
What I find particularly useful is the revision process in the early design stages. You can have a revision scheme that allows 'Design Revisioning' that other departments don't see.
For example:- If your working on a design for a number of days, you can check all the models in at various stages of the design (I usually do it every night). This is very handy for development, say you've been working on a design for a while and the 'powers that be' decide they prefer a previous version of the design. PDM allows you to loads up the design from an earlier version and save them as the latest revision.
Also good if you start to have problems with your models and don't know why?, simply return all the models to the last revision.
Just my thoughts.
Hi Josh, and hi all.
we're running a different PDM software that is not PDM Workgroup, so I don't know what it provides when you need to deliver and/or receive assemblies to/from suppliers. But I know that it would be very hard to change the owner of swx-files without a pdm control.
It is also true that if you need to comunicate and co-engineer whit suppliers, they must have the same pdm software and the same Soliworks version.
So, think about this too, before deciding.
Thank you all for the input! We are gonna go for it!
Retrieving data ...