In our company, Windchill's primary purpose is "Engineering Data
Management." Documents that have nothing to do with designs, bills of
material, CAD models, engineering changes, drawings, managing projects
related to engineering and sales order engineering, etc. should not go
into Windchill. Windchill's data model is usually much more complex than
most simple "document management" requests typically want. Also,
something like "training records" has no matching out of the box object
pre-modeled into the system. So, to use Windchill, you would have to
create light types with attributes and probably custom reports and
functionality to "remember" who took what training, and what documents
related to what training modules.
PTC University, for example, does not run on Windchill.
Therefore, I would guide people into something else for a specific
"training records management system" unless you want to do something fast,
you have Windchill already but not something better suited to your
requirements, and you don't have picky users who who will complain about
the search interface, or the way attributes are displayed, or the color
scheme, or the fact that "my documents don't need those attributes that
Windchill says are mandatory, can you make them go away...." etc. If all
of that is true, then you can certainly do something in Windchill, but it
will not be as good as a system specifically designed for training and
training records management.
Al
