1. Can Acquiring Structured Data Improve a Learning Content Development Environment? Mr. Wayne Gafford Advanced Distributed Learning (ADL) Mr. Schawn E. Thropp Concurrent Technologies Corporation ( CTC )

2. Focus and Takeaways Problem Statement Structured Data and its Benefits NPS Survey Summary Structured Data Acquisition Policy Overview Cost Benefit Analysis 2

3. Problem Statement Technical learning content not aligned with authoritative source information Minimal governance or standardization for enterprise data acquisition through lifecycle maintenance 3 AcquisitionDesign/Development Lifecycle Management

4. A Quantitative Fact Supporting the Need for Integrated Distributed Learning Content Development and Management “Of the 408 projects submitted for Computer-Based Training and PC- Simulation Maintenance, two-thirds reported the primary reason for the maintenance request was due to equipment or publication changes. Better integration of technical information with training would alleviate some of this rework.” Computer-Based Training & Personal Computer-Simulation Prioritization and Cost Estimation Assessment for NETC COO Supporting FY10/11 Spend Plan and POM12 Submittal (NETC 2009) 4

5. Structured Markup & Acquisition Structured technical content based on technical data specifications is one cornerstone to enabling best practices in learning content management and development environments. Benefits: Ensure logistical support analysis is linked to product support. Trace spiral development data development. Align tech data products to fielded and configured systems. 5 Technical Data & Learning Content Ensured Traceable Aligned

6. Structured Data and its Benefits Formal representation of data (separated from context)  HTML, S1000D, DITA, etc FeatureBenefit Standardized ManagementStandard approaches to managing content development and lifecycle processes through a formal content structure, specific syntax/semantics of elements and common storage mechanisms Defined Patterns/StructuresConsistent, institutionalized use and meaning of content structures (e.g., naming conventions, unique identification, meta data) Flexibility in AuthoringContent is not trapped by a single proprietary format. Content can be created/edited in a variety of authoring tools Write Once  Publish Many Formats Context-free and can be added at publish time (device rendering, style rendering, multi-lingual) Lifecycle ManagementStructured data stored in a common repository can improve learning content development by assisting in the identification (i.e., through XML linking structures) of content effected by changes. 6

7. NPS Survey Summary Title: Should S1000D be required by DoD? Sponsor: OSD P&R Conducted by: Naval Postgraduate School (Oct 2009 – May 2010) Focus: Use of an XML based data markup specification  S1000D Should S1000D be required by DoD? Survey shows programs and industry support DoD policy requiring structured data  Foster cooperation and integration between tech data and learning data  Link to NPS Survey on Use of S1000D Link to NPS Survey on Use of S1000D 7

8. Structured Markup in Acquisition Policies DoD Instruction 5000.2 – Operation of the Defense Acquisition System The Defense Acquisition Guidebook DoD Directive 8320.02 – Data Sharing in Net-Centric DoD 8

9. DoD Instruction 5000.2 Flexible management framework for translating capability needs and technology opportunities into stable, affordable and well-managed acquisition programs Data management intersections  Milestones A  C references  “data management strategy”  Lifecycle sustainment considerations  Data management and technical data rights 9

10. Defense Acquisition Guidebook (DAG) Designed to compliment DoDI 5000.2 by providing tailorable best practices for acquisition workforce Central Theme: Fostering Integrated Data Environments 10 Key Touch Points Data Management StrategyReflect the assessment and integration of data requirements across all the functional disciplines Integrated Data EnvironmentsEstablish a data management system Key Program DocumentsProduct support package development Initial Lifecycle Sustainment PlanSupportability analysis processes Maintenance & Sustainment StrategySupply chain features for analysis and rapid response Data AcquisitionAll activities that create, obtain or access data

11. DoD Directive 8320.02 Data Sharing in a Net-Centric DoD  Direct the use of resources to implement data sharing within the GIG DAG  suggests compliance with 8320.02 is essential prerequisite Creation and association of metadata Promote semantic and structural agreements for data sharing Structured data is a key ingredient  Unifies common content – cost effectively 11

12. Cost Benefit Analysis – The Process Use of S1000D for integrating technical learning content and technical data in a common source database Goal: Reduction in the number of hours required to develop and manage technical information Founded on 4 principles Tech information structured in S1000D Tech information stored in common source database Connect learning content development tools to source data Identify information that needs changed efficiently 12

13. Cost Benefits Analysis - Results Reduction of Life Cycle Support Hours  Technical Manual  490 hrs (6%)  One hour of courseware  66 hrs (16%) Estimated 10-Year Savings  Range from $32M to $165.5M  Integrating HM&E tech manuals and CBT courses 13

14. In conclusion… Sample Text 14