The Structured Phase Product Content Maturity Model Series Agenda Introductions Product Content Maturity Model Overview The Autodesk Story SDL Trisoft Our Presenters Andrew J Thomas Director Product Marketing ID: 800600
Download The PPT/PDF document "Product Content Evolution" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Slide2Product Content EvolutionThe Structured Phase
Product Content Maturity Model Series
Slide3AgendaIntroductionsProduct Content Maturity Model OverviewThe Autodesk StorySDL Trisoft
Slide4Our Presenters
Andrew J. Thomas
Director, Product Marketing
SDL
Marie
Salet
Principal CMS Engineer
Autodesk
Slide5Product Content Maturity Model Overview
Slide6Current Pressures
Slide7Deliver Product Content on demand
Content created and filtered for Customer Profiles
Interactive and dynamic, while still versioned and controlled
Incremental Updates
Analytics beyond page hits to capture “content utility”
Enable social interactions between community and authors
Crowd Authoring through easy WYSIWYG interface
Branding and terminology maintained, regardless of who creates the content
Content re-used consistently at every creation point
The Engaged Vision
Slide8Product Content
Product
Content
Marketing
Support
Engineering
Field Service
Personnel
Training
& Learning
Partners
Slide9Product Content Maturity Model
Structured
Content
Model
Beginning
to s
tructure Content for Product Categorizations
Process
Structured Content
Efficiency gains in content develop and localization
Tools
XML Authoring
Component
Content Management
Slide10Phase 2: Structured
Company Overview
Investment in structure has begun and older unstructured content is being migrated into DITA
New writing tools are being deployed and content creators are focused on learning new creation methods
Best Practices
Choose team evangelists that can help others with learning curve issues
Deploy a component content management system during migration to increase operational efficiency
Develop a content re-use/sharing methodology
Allow new roles to emerge – information architect, shared content lead
Next Steps
Finish conversion of legacy documents
Reach out to other departments involved in product content to determine what content can be re-used across
Slide11Content locked in context
Information can’t easily appear in multiple
context
and can’t be tailored readily to audience
High costs of formatting
Content gets out of synch and is difficult to refresh
Customers can’t find what they
need
XML Topic Methodology
Content can be reshuffled for deliverableSame content can live in multiple outputsContent can be delivered easily as web pages to consumeMetadata and conditions can allow content to be tailored on the fly Content can be easily refreshed
Traditional Book Methodology
Topic Based / DITA Methodology
Benefits of DITA
Slide12Contracting Product Life Cycles
Research & Development
Market Life
PRD
International Release
English Release
Shelf Life
Traditional
Research & Development
Global Revenue & Market Capture Life
Modular writing
Localization
Author
Review
Publish
Author
Review
Publish
Localize
Key:
Slide13The Autodesk Story: The Road to DITA
Marie Salet
Principal CMS Engineer
Slide14The Road To DITAAbout AutodeskDeciding to MoveUnstructured to StructuredStructured to DITA
Lessons
Slide15Autodesk
Autodesk is a world leader in 3D design, engineering, and entertainment software.
The broadest and deepest product portfolio in the design world
10 million+ users in over 800,000 companies
3,500 development partners
1.2 million students trained on our products every year
6,800 Employees in 95 Locations
Founded 1982
Fiscal year 2011 revenue US$1.95 billion
Slide16Product Documentation at AutodeskOur products are complex and require extensive documentation
Autodesk documentation regularly wins awards
Product documentation localized into up to 19 languages
High volume of source content (12 million words)
Technical writing groups decentralized
Localization is a (mostly) centralized organization
Slide17Show and Tell
Slide18Even for the web
Slide19Once upon a time, a long long time ago…
Slide20Documentation LocalizationDecentralized Tech Pubs departments created documentation in many formats:RoboHELPHTML, created in Dreamweaver, HomeSite, NotePad
Unstructured FrameMaker converted to HTML using WebWorks
Proprietary tools
Localization challenges included:
Managing manual handoffs between writers and translators
Investing heavily in Tech Pubs engineering to handle diverse formats, technical challenges
Spending substantial $$ for desktop publishing
Slide21Getting Our Feet Wet
Slide22Localization Proposes Buying a TMS/CMSGOAL: Reduce localization costs and improve efficiency
Winter 2003: Start of pilot project
Spring 2004: Pilot project completed
Fall 2004: First major product releases in WorldServer
Spring 2005: First WS cycle completed for all major products
Slide23Migrating Content to StructuredMigrating unstructured content to XML was not a trivial effortAutomated scripts and programs were developed to migrate content, but…
Extensive manual cleanup was required after content was in XML. Writers needed to do much of cleanup because they were the ones who knew the content.
Slide24Developed the CPM Data ModelDeveloped the CPM (Common Pubs Model), a corporate-standard XML model for technical publications in 2002/03Supports specialization of a base element set, and makes use of the class attribute value to define specialization inheritance
CPM specialization is "additive" rather than "restrictive", however, which is more flexible but precludes content sharing via "generalization"
Can share content authored using the "base" model amongst specializations however, as is done for the I&L books
Single-sourcing managed via XML attributes (e.g. product-exclude, product-include, units, mediaExclusions)
Slide25Getting Support…and Facing ResistanceAuthoring Tech Pubs teams could not agree on a single data model (DTD)
Teams had to invest time and money to convert unstructured docs to XML format
Authoring teams had to learn structured authoring and drastically change way of working
Slide26Success
Slide27SuccessWe can output HTML or PDF from any of our source with the click of a button or on a scheduled basisDocumentation localization costs go down on projects year over year
Throughput has increased dramatically
Translation memories are managed centrally and are very high quality
Localization workflow is highly automated
Slide28Help and PDF Automation
XML
repository
XSLT
XSL-FO
HTML
PDF
Slide29Never Satisfied
Slide30ChallengeCreate an environment that provided better performance and stability for our authors. Provide better authoring tools which will enable them to focus on content development rather than fighting with the tools. Resulting in faster time to market.
Slide31Separate CMS and TMSWorldServer is a TMS not a true CMSVersioning
Link Management
Assembly
Slide32Custom DTD or DITASupporting a custom DTD Authoring toolsRendering
CMS
DITA
Industry Standard
Out of the Box Tools
Slide33Déjà vu
Slide34TrisoftComponent Content Management SystemVersioningWorkflows
Slide35XMetalIntegrated with TrisoftDITA
Slide36Customizations
Importer
Set Metadata
Publishing Environment
World Server/Trisoft integration
Autodesk Branding
Slide37Support and TrainingSharePoint blogsYammerTrain the trainers
Slide38Lessons LearnedGet an Executive sponsorManage changeDon’t do everything at onceEnsure a front to back strategy (including localization)
Set expectations
Communicate!
Slide39The Eco System
Slide40Machine Translation
(LS-trained or
LS-supported)
Translation CMS
SDL Worldserver
+ TMs
Translators’ Review & Post-editing
Content CMS
SDL Trisoft
*Any* Autodesk Content
LS Translation Ecosystem
Community
Content
Web-Based Help (WBH)
or HTML Help
Autodesk User Assistance Content
The CMS Ecosystem
Slide41Marie.Salet@autodesk.com
Slide42SDL Trisoft
Slide43Structured Content Infrastructure
Structured Product Content Suite
Content Quality Checking
Intelligent Product Content Dynamic Delivery
Reviewers / SMEs / Casual Contributors
DITA
Component Content Management
Global
Customer Engagement
Slide44Most companies adopting component content management (CCM)Content Management Focus to Handle XML “Component Content Management”
Vision of single CMS for every business
maturing to specialized systems
Web CMS
, Source Control, Component Content all driving specializations
CMS’s that are not developed to specialize with DITA
can’t
meet requirements
Companies with standard CMS’s are adopting CCM to handle DITA (Dell, VMware, Nokia, + others)
Slide45Increase Productivity
Slide46The Problem of DITA Management
Slide47DITA Plus Translation
Slide48Differences of CMS and Component Content Management
Non DITA Solution
Specialized DITA CCM
Business Impact
Versioning
Yes
Out of the box
Tracks backups
Link management in DITA
No
Out of the box
Reduces manual tasks 30% and increases reuse 30-50%
Variable management in DITA
No
Out of the box
Increases reuse and reduces manual tasks and scripting
Publication Management
Scripted by technical resource
Out of the box
Manages releases, allows fallback and quick updates. Tracks history. Makes updates and mistakes 50% easier
Condition management
Scripted by technical resource
Out of the box
Increases reuse / reduces costs. Today managed in scripting
Translation reuse
No
Out of the box
Reduces translation costs
Speeds time to global markets. Increases quality
Reuse management
No
Out of the box
Reduces costs of content and translation
Slide49Publication Object
Publication Object
=> output
Master Document
(e.g. DITA Maps)
=> assemblage/ structure
Components
(e.g. Topics,
illustrations...)
=> content
Electronic output format
Baseline
Context
Variable definition
Layout template
Slide50t
Versions
Baselines
Third
edition
Second
edition
First
edition
Slide51V1
V2
EN
DE
EN
Target languages (eg FR)
Released
Released
Reviewed
Released
DE
To be translated
updated block
non modified block
Pre-Translation of
non modified blocks
In Context of the module!
Pre-Translation
Slide52Trisoft Physical Architecture
Slide53Major SDL Trisoft DifferentiatorsRelease
Management / Publication Object and Baseline
Increased productivity and ease of use (no link to version!!!)
Business Benefit: More manageability for releases and
reuse
Universal Topics / Conditions
Increased component reuse
Business Benefit: Higher Levels of Reuse
Multilingual Content Management / Translation IntegrationIncreased savings (higher ROI) Reduced Translation Costs and OverheadEnd to End Structured Content Solution Already integrated components for authoring, contribution, print, smart intelligent docsLong Term ROI on Extending the Solution
Slide54CMS Watch Report: Strengths of TrisoftWhat Analysts Are Saying …
“Extraordinarily good DITA support, including specializations and managing concurrent versions of documents”
“Provides support for highly-granular, complex customer content variations through enhanced condition support”
“Very good multilingual content support”
“Authors can work with content offline”
“Offers some translation matching, potentially saving money in localization scenarios”
Slide55Some of Our Customers
Slide56Questions?
Slide57Thank You for Joining Us
Coming Attractions:
DITA Webinar
Dec 15:
DITA Emerging Trends and Best Practices: Practical Solutions for 2012 and Beyond
Guest speaker
JoAnn
Hackos
of Comtech ServicesRegistration at www.sdl.com/en/xml/events
SDL Innovate 2012
March 2012
Santa Clara, CA
www.sdl.com/innovate
Slide58