Single-sourcing with DITA (at Philips Ultrasound)
Resource: Submitted by wandajane on Mon, 2007-04-02 10:29.
At Philips Ultrasound, we deal with a number of driving forces. First and foremost for us are the regulatory and legal requirements of the medical device field. Part of that are the language requirements for various countries. Finally, we are dealing not just with a software environment but a complex scenario involving software development, interoperability, hardware manufacturing, and service operations.
Currently, our content is authored in unstructured FrameMaker using standard templates and a strict style guide. Our content management system is a Documentum Docbase. This provides both version control and workflows. We plan to introduce some automation as well. We link the two products, FrameMaker and Documentum, using FrameLink.
This presentation identifies our goals in moving to DITA and some information on our process of converting legacy content.
Currently, our content is authored in unstructured FrameMaker using standard templates and a strict style guide. Our content management system is a Documentum Docbase. This provides both version control and workflows. We plan to introduce some automation as well. We link the two products, FrameMaker and Documentum, using FrameLink.
This presentation identifies our goals in moving to DITA and some information on our process of converting legacy content.
Attachment | Size |
---|---|
Single-sourcing with DITA.ppt | 298.5 KB |
training new techs
We have found that software inoperabilty is key in training new techs. We often get techs that have worked using other Ultrasound Parts. They come to us and have to start all over. Sure, many of the procedures are the same, but offering more inoperabilty would greatly reduce training costs. Thanks for working on such a great product.