If you are thinking about dbWorks implementation it is set up so that
you can do it yourself. The prerequisites are:
1. You know what you want to do as far as PDM. In other words, don't
expect them to come to you with ancient wisdom on the best part
numbering system, the best way to handle revisions, the best workflow.
Now some resellers may very well know all this, but not all. I would
be even more wary of a SW reseller, not that they are bad, but their
primary task is to sell SW, not get into the customer's business.
dbWorks is highly customizable and has reasonable defaults, but their
approach has been to train the customer in how to maintain and
2. You should be comfortable with Scripts, ie, vbScript and SQL. You
don't absolutely have to know this, but it depends on how much you
want to get out of it as to how much you will need to know this. They
are moving in the direction of configurable instead of customizable,
but if you want to get the most out of it this is a definite benefit.
You won't generally need to write scripts from scratch but you will
likely run into the need to change a script to meet your needs.
3. Depending on the size of the installation you can go with a free
MSoft mdb database, a free MSoft sql type database or full blown
Server 2005 database. If the later is in the cards be prepared to have
someone administer it. Most of the big boys are this way. It is also
possible to use mySQL as the database and there are some users in
Europe doing this.
4. Make sure whatever you are using for a vault is in decent order.
Duplicate filenames is the worst thing you could have. Having
consistent custom props that can be imported is a big plus.
5. Their support has been good and mostly by email. They can generally
handle things pretty well by email or webex. Only training requires
onsite support. There is a pretty good user group too with a few
really good gurus.