I'm interested to hear from people that are using Windchill to manage their Arbortext content. We're investigating Arbortext at the moment and wanted to get some feedback from the group.
We do not have a dedicated tech doc publishing system (other than the usual suspects: MS Office, Corel Draw and Adobe Illustrator, Photoshop and In Design) and wanted to get an idea of why people chose Arbortext and Windchill as their technical docs tool and storage system.
Has it met expectations? What are some of the implementation issues that you had to deal with? Is it well integrated or is it clunky?
We currently use Intralink 9.1 for CAD data management, but since most of the intended users would not be CAD jockeys and have no familiarity with our data management tool, ease of use issues become very important.
We can see change management and workflow being key features, and we're very familiar with lifecycle states and version history from Intralink.
In a related question: has anyone used an outside resource (human or published) to help develop best practices in technical documents? We're looking through all that stuff at the moment and it might be useful to have some fresh ideas or direction from outside of our company.
Thanks in advance for any thoughts or suggestions..
Andrew Mansfield Product Design and Development KI Green Bay, WI