Enabling an Integrated Data Environment Framework for LCS MM

1. Enabling an Integrated Data Environment Framework for LCS MM CONOPS – Acquisition Support Material

2. Jeff Clem, Lockheed Martin Concept of Operations

3. Concept of Operations Document Purpose • Provides an enterprise business model for the acquisition, development and life cycle management of integrated product support data based on S1000D. • Provides a framework of discrete tasks and measurable requirements that folds technical training into a standardized, metadata-based configuration management protocol. • Provides how to use the S1000D Bridge Tool Set to meet the business model and configuration framework objectives. Lessons Learned • Earlier involvement of NETC N6 would have been helpful in determining technical barriers. • Earlier involvement with field activities, OEMs and instructional designers would have provided a better as-is state. • Involvement with LCS MM IPT would help with early buy-in of CONOPS. Implementation Gaps / Transition Needs • Work with local program offices to measure CONOPS use case applicability. • Address new areas of knowledge and skills training for training developers • Authority To Operate S1000D Bridge Toolset within Naval information systems. Accomplishments • Development of the Integrated Data Management Concept of Operations For Littoral Combat Ship Mission Modules Program, which defines: • Key System Enablers • Business Rules • Operational Scenarios

4. Dr. Leslie Lucas, Submarine Learning Center Acquisition Support Material

5. Acqusition Support Material Purpose Develop Acquisition Support Material to assist in the preparation of a Statement of Work (SOW) for the acquisition, development and life-cycle management of integrated data used in technical publications and interactive multimedia instruction products. Lessons Learned • Acquisition Support Material must be reviewed by cross functional team representing the acquisition, technical, and training community. Implementation Gaps / Transition Needs • Identify and define a cross functional team when preparing acquisition support material. • Continue to standardize template to support acquisition requirements and community needs. Accomplishments • Developed a SOW template that supports individual community requirements. • The SOW is provided along with a series of Contract Data Requirements List (CDRL) items that can be used in association with the SOW.

6. Technical Components of the LCS MM Integrated Data Environment Framework Bridge API – SDL Contenta – AIM – SCO Workbench – Transformation Toolkit – Product Data Lifecycle Service

7. Schawn E. Thropp, CTC Bridge API Specification

8. Bridge API Specification Purpose Develop a data exchange API that establishes an interoperable communications link between Learning Content Authoring Tools and Common Source Databases. Lessons Learned • Building industry consensus is a long process. • Early prototype implementations assisted development. • International support was critical to S1000D applicability. Implementation Gaps / Transition Needs • Put API to use in LCS Integrated Data Environment to determine gaps/faults/accuracies of use cases. • Continue “marketing” bridge API to technical publication and technical training community. • Continue standardization support through OASIS. Accomplishments • Specification V1.0 (WSDL, XSD) • Introduction to API – Whitepaper • Test Environment developed • Early prototype implementations from Industry (AIM, Contenta, SCO Workbench, Corena) • Bridge API adopted by Swedish Defense • Transition to OASIS started

9. Allen Seifert, SDL S1000D V4 Support in LiveContent and Contenta

10. S1000D V4 Support:NAVSEA LiveContent Viewer Purpose • Provide support for S1000d Issue 4 technical data and learning data in the NAVSEA LiveContent Viewer. • For use in development of Interactive Electronic Technical Publications. ` Lessons Learned • Nothing significant to report. Implementation Gaps / Transition Needs • Deploy NAVSEA LiveContent Viewer. • Add support for interactive display of Learning Data Module content. • Finish loading and testing Q20 and MK50 data. • Integrate SCPM publish support into Contenta product. Accomplishments • Added Issue 4 tag support to NAVSEA LiveContent Viewer. • Created custom publish interface and scripts to publish SCPM and LDMs in NAVSEA LiveContent Viewer. • Uploaded Q20 tech data and MK50 tech and training data to Contenta and published it to LiveContent.

11. Bridge API Implementation: Contenta CSDB Purpose Provide the U.S. Navy with infrastructure to centrally produce and manage integrated product support content in S1000D through the implementation of the Bridge API into the enterprise wide CSDB. • NAVSESS Philadelphia Lessons Learned • Integration with client applications revealed additional implementation issues. • Use of Web service implementations still maturing in Product Support Data environments. Implementation Gaps / Transition Needs • Finalize API implementation against LCS requirements. • Finalize timeline for inclusion of API into Contenta product. • Deploy Contenta implementation to U.S. Navy environment. • Develop strategy for deployment at NAVAIR North Island. Accomplishments • Prototype implementation of Bridge API ready for SDL Product line for Navy enterprise use. • Prototype available to clients via scorm.sdl.com • Refinement of Specification through real implementation experience.

12. Teresa Rippeon, Aimereon Bridge API Implementation: Authoring Instructional Material (AIM)

13. Bridge API Implementation:U.S. Navy AIM Tool Purpose • Provide an enterprise level capability to author curriculum planning content in technical manual environments. • Support the U.S. Navy in developing technical instruction/training that can be reused with technical data. • Extend existing Authoring Instructional Materials (AIM) Content Planning Module (CPM) to support S1000D Issue 4.X. Lessons Learned • Perform early gap analysis between LCAT functionality and proposed standard. based data capture requirements (e.g., S1000D learning plan). Implementation Gaps / Transition Needs • Investigate gap between S1000D Issue 4.X and NAVEDTRA 136/CPM business process model. • Identify the AIM functional gaps and place those requirements/needs in the management process. Accomplishments • Completed first step in making AIM toolset ‘S1000D Issue 4.X aware’ by prototyping Bridge API-based interface between NAVEDTRA 136-compliant CPM and Contenta CSDB via Bridge API for generation of preliminary SCPM and Learn Plan LDM.

14. Mark Ewer, LSI Bridge API Implementation: SCO Workbench

15. Bridge API Implementation: Open Source SCOWorkbench Purpose • Implement a production-ready courseware development tool that communicates with a CSDB to develop and reuse S1000D learning content. Lessons Learned • The Bridge API is highly adaptable. • Gaps can exist between a standard that supports training (e.g. S1000D, DITA) and level of support provided by Learning Content Authoring Tools. Implementation Gaps / Transition Needs • Develop end-user training content on how to use S1000D SCO Workbench capabilities. • Test with real-world sample content from a CSDB. • Development of prototype lesson that reuses real-world content. Accomplishments • Implemented Bridge API connection and authentication with full check out / check in support. • Data Module search and download with a CSDB. • Map S1000D constructs to SCO Workbench infrastructure: • S1000D SCPM to Lesson Flow / SCO Flow • S1000D SCPM SCO Entry to Assessment • S1000D Learn Plan to Learning Plan • S1000D LDM to Screen or Question

16. Tyler Shumaker, CTC S1000D Bridge Transformation Toolkit

17. S1000D Transformation Toolkit Purpose • Provides reference implementation supporting the transformation, packaging and viewing of S1000D data into a SCORM 2004 3rd Edition Content Package, Mobile Web Application and PDF. Lessons Learned • Toolkit output for mobile better suited for performance support material. • More real world test data beyond Bike and MK50 is needed to better verify and validate Toolkit’s results. Implementation Gaps / Transition Needs • Identify LCS needs for use of mobile. • Testing of the Toolkit integrated in other applications. • Management and ownership of the S1000D Transformation Toolkit. Accomplishments • Developed SCORM Content Package examples. • Developed S1000D support for iPhone, iPad, and Android-based devices. • Implemented an extendable architecture.

18. Steve Worsham, IDSI Product Data Identification

19. Product Data Identification Service Purpose • To provide the means to quickly identify technical information in a common source data base that could be impacted by an engineering change proposal. Lessons Learned • Nothing significant to report. Implementation Gaps / Transition Needs • Further development efforts will be needed to achieve CON and ATO status for hosting within U.S. Navy networks. • Additional development in partnership with CSDB vendors to integrate service with product workflows in order to gain maximum effectiveness. Accomplishments • Development of application interfaces to provide retrieval, organization and review S1000D data. • Successful implementation of S1000D Bridge API for request and transmission of DMRL, DM and media data. • Rendering of the S1000D data in DM viewer.

20. S1000D Data Conversion for the LCS MM Program MK 50 – Q20

21. Steve Worsham, IDSI Kim Willmott, BTAS MK50 and Q20 Data Conversion

22. MK50 and Q20 Data Conversion Purpose • The MK50 and Q20 conversion efforts were conceived to demonstrate that product support data (technical and training) can exists in a CSDB and utilized by Bridge tools. Lessons Learned • When converting legacy product support data formats to S1000D, content developers must have access to SMEs. Implementation Gaps / Transition Needs • Operational S1000D V4.0 CSDB at NAVSESS Philadelphia (expected in October 2011). • Development of LCS MM best practices and business rules for consistent development of S1000D content. Accomplishments • Conversion of source technical documents from PPT products (Q20) • Development of learning DMRL from existing “tech” DMRL (Q20) • Conversion of PDF documents to S1000D data (MK50) • Origination of learning content DMRL from document structures (MK50) • Development of SCORM conformant packages (both)

23. Realizing LCS MMIntegrated Data Environment Transition from R&D to Implementation to Operations

24. From R&D to Implementation and Operation of Bridge Project Purpose • Identify all the areas in LCS requiring change management, ongoing support and training to support an operational S1000D environment. Lessons Learned • Hard to get input from OEMs and programs about training development and practices. • Security issues are hard to solve. Implementation Gaps / Transition Needs • Infrastructure • CSDB, AIM, SCO Workbench, API, Product Data Identification Service, Toolkit • Training • S1000D based ISD, training content configuration, content development tools • Develop and test use case workflows for integrated data environment. • Dept of Navy Policy Accomplishments • AIM, SCO Workbench exchange S1000D data with CSDB. • S1000D outputs to SCORM & mobile. • Data management web service locates impacted data. • MK50 and Q20 data converted • CONOPs developed. • Sample integrated data SOW developed. • IDA cost benefit analysis shows S1000D save money for LCS and Navy.

25. Areas to Consider: Change Management • Description of the operational paradigm shift. • We need to understand how training is currently developed. • Change management factors in the shift. • Personnel need to learn new skills, support systems (hardware and software) need to be set up to support new requirements. • Change management success factors. • Top level discussion with dept heads, senior personnel

26. Areas to Consider:Training • Areas of knew knowledge, skills and practices • This should be based on a job task analysis • Examples of new training required for implementation and operation of Bridge. • AIM interface training • SCO workbench interface training • Integrated front-end analysis • LDM and SCPM training • DMRL development training • New or tweaked ISD modes in an S1000D environment • ECP web service training

27. Specific Questions Going Forward • Security: How will NAVSSES, NAVAIR & NETC achieve ATO status? • Approval Authority (Val/Ver): Does integrated data impact existing approval authority?   • Conversion: What amount of LCS tech data and training be converted to S1000D? • Funding: Who provides support for S1000D, software and infrastructure updates? • Funding: Who provides support for training development and execution?