Taking Our Information Assets to the Next Level: Kyocera Case Study
-
Upload
scott-abel -
Category
Technology
-
view
932 -
download
0
description
Transcript of Taking Our Information Assets to the Next Level: Kyocera Case Study
DocTra
in W
est
2008
May 8, 2008
Taking Our Information Assets to the Next Level: Kyocera Case Study
DocTra
in W
est
2008 In this presentation, you will learn
How a small group of technical communicators is re-engineering its information development methods and output
What prompted the change
Where DITA and a CMS fit into our strategy
How we prepared
Where we are in the process
Highlights of our experience so far
How we see the short and long term future playing out
DocTra
in W
est
2008 Some Background
Kyocera is an $11B company built around ceramic technology with a strong emphasis on building products that are environmentally-friendly.
Kyocera Mita is the printer and copier division of Kyocera, contributing $2.5B to corporate revenue. Ceramics in the drum and the toner result in long life and low TCO.
Kyocera Technology Division is a group of approximately 80 developers creating driver and utility software for Kyocera’s printer business.
KTD’s Technical Communication group supports the printer software developers with user assistance, user guides and localization coordination.
DocTra
in W
est
2008
Kyocera Mita's largest market is in Europe, followed by North America and Japan
A Global Company
DocTra
in W
est
2008
Kyocera Mita Products
Monochrome Printers
Monochrome
Copiers/MFPs
Color MFPs
DocTra
in W
est
2008
An important consideration in copier and printer selection is speed and volume
Many Product Configurations
DocTra
in W
est
2008
We support a growing number of software platforms and languages
Many Software Formats and Languages
DocTra
in W
est
2008
The number and complexity of our products and platforms has been growing.
Both trends will continue:
The number of supported platforms continues to expand, for example, 64-bit PCs, Mac OS X and beyond, embedded systems, more flavors of UNIX.
New output format. XPS is a major change for the entire industry.
More target languages for software under development.
So…
DocTra
in W
est
2008
The Technical Communication Manager recognized our customers’ need for flexible, configurable user assistance that could be produced in an agile fashion. He came to the conclusion that the only way to accomplish this was to adopt a single-source strategy. Further investigation convinced him that the key would be topic-based writing.
With the strong support of management behind him, he hired a new employee with experience in content management and structured authoring, but not DITA.
The technical writers on staff started reading and discussing the new concepts and how to implement the change.
Backing Up About Two Years…
DocTra
in W
est
2008
The Silicon Valley DITA Users Group: regular attendance at these monthly meetings was key to what followed.
The Technical Communication group met weekly to watch a training video on XML. This provided background on the concepts upon which DITA is based.
We held a three-day DITA training from the authors of the Open Toolkit User Guide.
We attended a STC Writing Workshop.
A Chronology: The Training Process
DocTra
in W
est
2008
Our vendor conducted a document analysis session with us. We selected two forms of Help and one User Guide to analyze. The Help analysis was very straightforward, the User Guide analysis a bit more challenging.
The user guide conversion to DITA was simplified by the fact that the vendor flattened the variety of topic support to a single type. The many possibilities for tag use and formatting has led to a number of adjustments as we go along. For the Help conversion, we easily achieved equivalent output.
Before implementation, the vendor returned and gave us two days of training on the system.
The content management system was loaded with the converted data. Later, the translation memories were added.
We were ready to go…
A Chronology: Analysis> Conversion> Training> CMS Is Turned On
DocTra
in W
est
2008
The Technical Communication team holds weekly DITA authoring meetings. We address authoring issues, and expand upon our authoring guidelines.
We hold weekly status meetings with the vendor.
We are authoring a new User Guide with a DITA format.
We are using the CMS workflow to review one another’s work.
We are testing our translation tools and will translate our User Guide once the authoring finishes.
We are working to format our terminology databases in the CMS to more easily synchronize them with the terminology used by the hardware engineers in Japan.
Where We Are Now: Writing DITA Topics in the CMS
DocTra
in W
est
2008 Where We Are Now: Some Unforeseen Side Effects
Since the CMS tracks every version of each DITA topic, there is high visibility as to just how many times each writer had to go back ad correct a typo or add a tag.
It is challenging for authors to estimate how close they are to completion since the process is so new.
On the other hand, there is much more visibility as to how much content each writer has actually created, since it is all visible to the entire team.
DocTra
in W
est
2008
We will support the full set of translated languages and locales to meet our customers’ needs. Full integration with authoring will reduce overhead and turn-around time.
Kyocera will be better prepared to:
expand the language support set.
support additional forms of output, such as Eclipse-based help or knowledge bases.
support new types of products, such as published APIs, and services, as well as their incremental updates.
implement “author memory.” Similar to Translation Memory, author memory automates reuse of source content.
Where We Are Headed
DocTra
in W
est
2008
SVDIG (Silicon Valley DITA Interest Group) and the members, presenters and organizers are very generous with their time and expertise
The contributors to dita-users on Yahoo Groups.
Other DITA User Groups outside of Silicon Valley. Thanks to Bob Doyle and his recording efforts, many of these local presentations are now online.
Where to get Help: Valuable Resources
DocTra
in W
est
2008 Questions?