Converting Your Legacy Data to S1000D
5 likes4,572 views
The document discusses the challenges and considerations involved in converting legacy data to the S1000D standard, emphasizing the need for planning, identifying reusable content, and addressing both technical and human factors. It outlines the complexity of restructuring traditional documents into data modules and highlights the cost-effectiveness of conversion compared to rewriting. Key points include the importance of stakeholder engagement, understanding the conversion process, and utilizing tools to facilitate effective content reuse.
![10
Square Peg 3: Introductory Material That Applies to
Numerous DMs
Example:
1-1 Introduction
The following paragraph discuss servicing…
Personnel Recommended:
One 1-2
Two 1-3
WARNING
Make sure XYZ module is not connected…..
1-2 Remove XYZ Module
1. Loosen the screws.
2. Disengage the ejectors
1-3 Insert Replacement XYZ Module
1. Align the module.
2. Insert the module, pressing in firmly
[[start]]
[[stop]]](https://image.slidesharecdn.com/convertingyourlegacydatatos1000d-final-150514143933-lva1-app6892/85/Converting-Your-Legacy-Data-to-S1000D-10-320.jpg)
Converting Your Legacy Data to S1000D
- 1. www.dclab.com Converting Your Legacy Data to S1000D Naveh Greenberg, Director, US Defense Development Data Conversion Laboratory (DCL)
- 2. 2 Agenda • A very quick introduction to S1000D conversions • What the technical headaches are • Whether to convert or rewrite • Planning for a good conversion experience • What the timeline looks like • Some tools to help
- 3. 3 The Story with S1000D • Provides an international solution to standardize on a common spec across the services • Was developed from ATA Spec 100 to place greater emphasis on granularity and interchangeability of information • Allows for modularization of content with Data Modules (DM), and for easy re-use in multiple outputs • Standard and schemas are publicly available • Applicability is available at a very fine level • Standard format for external data exchange (Data Dispatch Notes) • Process DM to allow interactive processing structures and Learning DM for training (4.0)
- 4. 4 What Makes S1000D Conversion Difficult • S1000D is a conceptual departure from linear information – and is difficult for many to get used to • Turns the traditional book into a collection of DMs • DMC & business rules. • DMs can be thought of as interchangeable parts – to be reassembled in multiple ways – to be repurposed for multiple outputs – to be reused across multiple products • …but your documents weren’t likely to have been designed to do this.
- 5. 5 Structuring a Book into Data Modules in S1000D IPD Wiring Descriptive Crew Fault Appendix B Procedural Para 1-1Early S1000D Publication Para 1-2 Para 1-3 Para 1-1 Para 3-1 Para 2-1 PDF Book Para 1-2 38784 Book Para 2-1 Para 2-2 Appendix A Para 3-2 Appendix A Appendix B S1000D Common Source Database Publication 1 Publication 2 Subtask Task Subtask ATA Book Pageblock Pageblock Pageblock Pageblock Pageblock Task Maintenance Process Descriptive DM Procedural DM IPD DM Wiring DM Crew DM Process DM Maintenance DM Fault DM IPD Wiring Descriptive Crew Fault Procedural Maintenance Process Process Wiring Procedural Descriptive Fault Crew Process Publication 3
- 6. 6 Further Complications in S1000D Conversion • There’s the usual conversion issues – Accuracy of the transferred text – Tables – Math – Special Characters • There’s also the structuring issues – Identifying DMs – Identifying reusable content – Identifying Applicability • And the people issues – Deciding what needs re-authoring – Getting used to a new “document” paradigm – Getting rugged individualists to collaborate more
- 7. 7 Some Examples of Converted Data ≠BikeSample YourLegacyData
- 8. 8 Square Peg 1: Procedure Authored as a Table Issue: Tasks are done as tables rather than numbered lists. Automated conversion keeps the tables as tables, and steps are not tagged as steps. This is a big problem for Information Mapping users (standard layout for steps). Step Action 1 Check the phase sequence in the mains with the phase sequence indicator. 2 Check the direction of rotation of impeller. If a dry installation is made, check the direction of rotation through the inlet elbow access cover. Note: If done consistently, tables can be deconstructed programmatically.
- 9. 9 Square Peg 2: Multiple Steps in a Single Procedure Replacing an XYZ Module Use this procedure to replace an XYZ module Remove XYZ Module 1. Loosen the screws. 2. Disengage the ejectors 3. Pull the module straight out Insert Replacement XYZ Module 1. Align the module. 2. Insert the module, pressing in firmly 3. Engage the ejectors
- 10. 10 Square Peg 3: Introductory Material That Applies to Numerous DMs Example: 1-1 Introduction The following paragraph discuss servicing… Personnel Recommended: One 1-2 Two 1-3 WARNING Make sure XYZ module is not connected….. 1-2 Remove XYZ Module 1. Loosen the screws. 2. Disengage the ejectors 1-3 Insert Replacement XYZ Module 1. Align the module. 2. Insert the module, pressing in firmly [[start]] [[stop]]
- 11. 11 Square Peg 4: Irrelevant Cross-References Conversion to S1000D may make some source cross-references irrelevant. For example, assuming some chapter headings are dropped, a reference to a chapter is no longer valid. See Chapter 1, Introduction on page 2 Would be tagged as: See <dmRef><dmRefIdent><dmCode modelIdentCode=“.." systemDiffCode="A” . . . infoCodeVariant="A“ itemLocationCode="D"/></dmRefIdent></dmRef> NOTE: Hard-keyed page numbers are typically dropped from the cross- reference string since they are no longer relevant in S1000D. A project specific business rule will need to me made as to how to handle these links.
- 12. 12 Square Peg 5: Writer Creativity in Source Material <para>1. Clean the Engine.</para> <step1><para>Clean the Engine.</para></step1> <seqlist><item>Clean the Engine.</item></seqlist> <entry>1.</entry><entry>Clean the Engine. </entry>
- 13. 13 Square Peg 5: Writer Creativity in Source Material ……………..
- 14. 14 So… Maybe You Shouldn’t Bother Converting Your Content? • It seems like such a pain. • Too many rules. • There is always a need for some rewriting - few writers have the clairvoyance to author content with the intent that be converted in the future – might as well rewrite it all. • My writers aren’t very busy right now anyway. • It’s more fun and seems like less trouble to author anew.
- 15. 15 Think Again…. • If you rewrite you still need to fulfil the standard requirements. • Still need some XML knowledge. • Can take a very long time. For example a 5000 page project: • 15 minutes per page to rewrite. • 75,000 minutes => 1250 hours • At 7 hours per day (no breaks) => 179 days • But worse ... • Inconsistencies. • Writer creativity. • IETM/CMS may not properly function
- 16. 16 In Reality… Converting Your Content is Worth the Bother • Throwing it out and starting over is an expensive option – Rewriting at $25-$45+/page vs. converting to S1000D at $6-$12/page – The hidden costs of redoing index entries, links and other features you’ve built in – The hidden cost of reviewing and recertifying it all • It’s usually easier to use what you have as a base, and convert over – Needs planning – Needs time • Planning for a good conversion experience – Which content will you need? – Which content is worth converting? – Which content is suitable for re-use in multiple places? – What tools are available? – How to specify the conversion to get it right? – When do you start all this planning?
- 17. 17 Most Importantly – Plan!!! • Ask the important initial questions • Who are the stakeholders. Who is the final client/user? • What is the estimated volume and deadline? • What version of S1000D? • Do we know what CMS or rendering tools will be used? • Source format. Not all source data are created equal. • Budget? • Ask around or join discussion groups. • Prepare for the next step • Get your hands on the source data, business rules, and schemas. • Begin looking for the right people. You don’t need to be a S1000D savvy but you do at a minimum understand the concept. “If I had eight hours to chop down a tree, I'd spend six sharpening my ax.”
- 18. 18 What to Convert, and in What Order • Categorizing – Active documents in good shape – Active documents that need a lot of work – Somewhat inactive document that will likely be retired – Archival materials • Prioritizing – Documents that are most used – Documents that are customer favorites – Documents with longest product life – Start with most recent documents and go back • Identifying the process – Can be converted as is – Can be converted with some work – Needs to be rewritten – Don’t convert – just keep archival copies
- 19. 19 The Classic Conversion Process • Conversion of legacy data is usually an afterthought – a lot of scampering after the system is up and running • 3 years has been typical for DITA implementations, with another 1-2 years to really get it going; S1000D is longer Pilot Select CSDB Implementation Post-Conversion Cleanup Live Training Start Conversion
- 20. 20 The Classic Conversion Process Doing Cleanup and Implementation in Parallel Tracks: Pilot Select CSDB Implementation Post-Conversion Cleanup Live Initial Training Pre-Conversion Cleanup Refresher Training Start Pilot Select CSDB Implementation Post-Conversion Cleanup Live TrainingConversion Conversion
- 21. 21 Some Tools for a Good Conversion Experience • Conversion specifications – a formal process to specify the conversion so that all stakeholders can agree on a proper process • DMRL (Data Module Requirements List) - to verify that Data Modules have been properly identified • Content reuse identification – software to located potentially reusable content • Best practice scanners – to scan code to verify best practices have been followed • Test conversions into S1000D – to make sure the process works all the way through
- 23. 23 Data Module Requirement List (DMRL) Para No Original Title DMC Type Modelic FOREWORD SAMPLESYSTEM-A-00-00-00-00A-018A-D Desc SAMPLESYSTEM 1 INTRODUCTION. ------- 2 MANUAL ORGANIZATION. ------- CHAPTER 3 PREPARATION FOR USE AND RESHIPMENT NA SECTION I PREPARATION FOR USE SAMPLESYSTEM-A-00-00-00-00A-006A-A Desc SAMPLESYSTEM 3.1 INTRODUCTION. ------- 3.1.1 Nomenclature Setup and Initialization Instructions. SAMPLESYSTEM-A-00-00-00-00A-007A-A proc SAMPLESYSTEM SECTION II PREPARATION FOR RESHIPMENT SAMPLESYSTEM-A-00-00-00-00A-530A-A Desc SAMPLESYSTEM 3.2 INTRODUCTION. ------- 3.3 CONDITIONS AND METHODS OF RESHIPMENT. ------- CHAPTER 8 ILLUSTRATED PARTS BREAKDOWN SAMPLESYSTEM-A-00-00-00-00A-018B-D Desc SAMPLESYSTEM SECTION I INTRODUCTION NA 8.1 INTRODUCTION. ------- 8.2 MAINTENANCE PARTS LIST. ------- SECTION II MAINTENANCE PARTS LIST SAMPLESYSTEM-A-00-00-00-00A-075A-D IPB SAMPLESYSTEM SECTION III NUMERICAL INDEX N/A SECTION IV REFERENCE DESIGNATOR INDEX N/A GLOSSARY SAMPLESYSTEM-A-00-00-00-00A-006A-D Desc SAMPLESYSTEM
- 24. 24 Divide and Conquer for Effective Content Reuse • Content reuse frequently showed as a reason for moving to S1000D • However few had yet implemented; it was just too daunting a task • Divide and conquer the identification of reusable content • Use tools that help to identify reusable content • Create an iterative process to manage content reuse
- 25. 25 Content Reuse Analysis Reports • Finding exact or similar text will help you when mapping to Data Modules • It will also help to detect applicability and inconsistencies
- 26. 26 Summary • Conversion of legacy data to S1000D is not trivial – Significantly faster, safer and less expensive that rewriting – There are special S1000D consideration to be taken into account – Needs planning • Starting the conversion process earlier makes life easier – Shifts the critical path; speeds the process – More of the work can be done by the content owners – Eases the training and change acceptance burdens • Content re-use also needs planning – Starting early allows time for a more through review – Setting up collaborative teams sets the tone and allows one to “divide and conquer”
- 27. 27 Q&A Naveh Greenberg Director, US Defense Development Data Conversion Laboratory (DCL) (718) 307-5758 ngreenberg@dclab.com @dclaboratory