I've seen a few different PDM threads and feel I've seen enough suggestions to ask this (I think!).
I saw it referenced a few places that it is easier to "ADD" to PDM then to create and then decide to change - true?
I also saw it referenced that if your documentation processes are less than stellar, it might not be best to use PDM - true?
Taking those two points above (assuming true) - we do not have good documentation standards at this time. Even with these standards (that we don't yet have) we would then need buy-in. While there is some, I foresee some growing pains in certain areas.
So, it would be ideal for me to roll out PDM as a parts vault only (I'm the only user at the moment) which gives me time to become more familiar with the software (I'd likely be the one administering it). That also would likely remove the step of paying our VAR for some of their PDM setup/training packages which would mean rolling it out sooner as well.
I'm asking, because either way I need to start reorganizing our existing part structure and would rather not do it twice (once w/o PDM and then once with PDM).