TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
I have been tasked with producing a list of ranked requirements, needs and wants, that I would expect from a PLM tool in TechComm. Oh and by next Tuesday! (The other functions within the company are also tasked with producing requirements for their departments, hardware, mechanical, CM etc.)
My reason for posting is to tap into the collective experience of other tech writing folk in using such a tool.
Currently I use ClearCase as a repositry of source files and material and Notes as a vehicle for sign-off approvals. The files in Notes are the final files that can be accessed through our ERP. Cludgy, but that is what the company currently uses.
My very basic understanding of PLM from a tech writing perspective is that I will be able to control both source files, revision control and sign-off in one place?
Any input would be appreciated. What tools to suggest, pros and cons and any experiences, good or bad that you may have had with specific tools.
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-