publishing single source dita contentditaexchange.com/wp-content/uploads/2015/04/kone... · pure...

Publishing Single Source DITA content

2 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

KONE worldwide

Moline, IL

Hyvinkää

Keighley

Pero

Kunshan

McKinney, Texas

Chennai

Ùsti nad Labem

Production site

KONE is present

Essen

Torreón

Global R&D centers

Helsinki

Head office

3 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Product Information Center

Global Processes

Training Center

Hyvinkää, Finland

Product Information

Center

China

Product Information Center

USA

Moline

Shanghai

Kunshan

Product Information Centers in KONE

4 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Single Source Modular Content with DITA

5 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Next Gen Way of doing, big picture Content Creation

Process

Roles

Reuse

New Information products

Systems

Tools

Standards

Quality

Training and Support

Project management

Coaching DE, reviews Teams

6 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Next Gen Way of doing, bigger picture

Product Lifecycle Management

Managing and Delivering Publication

User Satisfaction and Feedback

Content Localisation

7 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Process

Project management

Project Plan Followup & reporting Auditing

Change Management

Impact and Requirements Analysis

Content Analysis Content Plan

Storyboarding Review & Approval Publishing

Content Creation

Startup

Analysis & planning

Implementation

Closing

8 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Roles

Stakeholders Info Product Author

Program Manager

Writer

Illustrator

Animator

Chief Writer

Chief Illustrator

Chief Information Architect

9 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Technology

Global Standards State of the art technology

Skilled partners Efficient Processes

10 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Content, version and language management

Content map Topics

11 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Publishing

12 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Localisation Model, Example

Corporate Master Content

Master offering in different languages

Basic localisation

Local offering & Product names

Non-applicable part of global offering removed

Local content

Add-on local content

Utilises global structures and templates

13 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Content Localisation example Local Product Offering

14 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Localisation of Content Produce Local Topics

15 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Localisation Model, Managing Changes

Corporate Master Content

Master offering and language version

updated as new versions of content

in a managed release

Pure Local content

Maintained locally

Localised content

Local offering by editing the content map

Notifications on changes and diff maps

Ability to clone maps and topics

Approval workflow

Corporate Content

New DITA map (+Topics and Graphics)

Published Site

Content

Localisation

Localized content

Local site

Content Approval

Cycle

Map diffing

Topic diffing

Add/ remove Topics

Manage Variable

s

16 5/15/2012 © KONE Corporation | Publishing Single Source DITA Content to MOSS 2007

Practical Advice

Have a clear vision of what you you are going to achieve

Have a clear, well defined and documented process

Communicate!

Build quality control and coaching into the process

Build performance standards and measurement

Know what you are doing, the consultants necessarily

don’t

Keep it simple:

– Clear roles and interface for the systems and tools

– Do not customize (too much)

– Use standard interfaces between the systems