1. MT Continuum Status 3 Apr 12 Tiffany Dombrowski, AIM Pgm Mgr Gerry Cullison, SSP Mark Campbell, MT Continuum Team Jamie Stewart, AIM team

2. Overview MT Continuum overview Application to other communities Project status Lessons learned for other NETC communities SSP Electronic Classroom Control Software Change

3. MT Continuum Project Strategic Systems Programs (SSP) re-engineering 30+ week training pipeline for TRIDENT Ballistic Submarine (SSBN) Missile Techs (MTs) into blended just-enough/just-in-time ILE-conformant Instructor Led (ILT) and Interactive Multimedia Instruction (IMI) segments AIM CPM and LO Module toolsets part of SSP’s baseline business process for this re-engineering First major end-to-end design, development, and maintenance project that’s defining CPM/LO Module business rules and data exchange mechanisms MT Continuum team: – SSP - Requirements Owners, Afloat Delivery System – Contractor team – ILT development, IMI Storyboard development, SMEs – NAWCTSD / AIM team - CPM/LO Module support – NUWC – LMS (Seaware) – LSI, Inc. - ISD and IMI design/development – CFS – CM/QA agent for SSP – Fleet – SMEs

4. Application to Other Communities Based on NETC-mandated JDTA as fleet performance requirement basis for learning content design and development Closely coordinated with NAVEDTRA 136 development Hands-on production phase development of complete LO Module ILT lessons/sections and design of IMI lessons/sections as well as definition of new JDTA/LO Module versioning concepts Integrated development and maintenance environment for blended, SCORM and 136-compliant learning content Bi-directional interface between LO Module and LSI Venus.net CBT toolset for IMI development/maint.

5. Project Status Plan, Analyze and Design Completed – JDTA – Establishment of initial 3 major projects – Revised 9-project structure Approval of learning objectives Ongoing development of ISD considerations elements as part of script-storyboard effort Development (production) Phase underway 15 May 11 – 9 projects exported from CPM to LO Module for production development in AIM I Rel 5.0 on fedsun – SWS AIM I instance in production at NETPDTC

6. Lessons Learned for Other NETC Communities Completion of supporting documentation in Design Phase is crucial – (IMDP, Learning Objectives, Process Documents) Establish standard for estimating TTT in Design Phase Establish change request process in Design Phase Development IMS/POA&M– crucial to support reviews Storyboard Training – Consider Learning Curve for Storyboarding in the LOM

7. SSP Electronic Classroom Control Software Change Background – The introduction of electronic documentation in the early 2000’s saw the migration of a majority of paper Instructor Guides (IGs) to electronic Lesson Plans (LPs). This required the introduction of tools (TechSight) necessary to access, present and view them – Classroom Control (software) – In 2005 the CCS tool of choice (TechSight) was experiencing obsolescence issues. A replacement product “Elite” was selected (to address these issues) for evaluation and after some modifications for use.

8. SSP Electronic Classroom Control Software Change (contd) Evolving requirements and obsolescence issues are forcing a Classroom Control Software change. Some of these but not all: – Policy DODI 1322.26 - Embedded training and distributed learning shall be considered as the first option. OPNAVINST 1500.76A – Navy Training Systems Requirement Acquisition and Management DoD directive 8500.1M – Information Assurance – Standards SCORM 2004 HTML 5, XML – Software Applications – I.E., Flash, MS Office, Java 6.4… Operating Systems (OS) - Windows 7, 64 Bit, Windows Server 2008 64 bit

9. SSP Electronic Classroom Control Software Change (contd) Approach – Identify and correct issues in the areas of Policy, Standards and Software in an update to the CCS tool or in the development of a new (CCS) tool. Options – SSP has identified 3 potential options to address this approach: Update Current CCS (Elite) Develop New CCS Integrate CCS Software into LMS

10. SSP Electronic Classroom Control Software Change (contd) Option 1: Update Current CCS (Elite) –Pros Update can be incremental Low schedule risk –Cons Cost Proprietary Risk may drive redesign Retains unused legacy capabilities

11. Option 2: Develop New CCS –Pros Develop to Software requirements Develop to Standards Develop to Policies –Cons Cost Schedule Unknown Risks SSP Electronic Classroom Control Software Change (contd)

12. Option 3: Integrate CCS into the LMS –Pros Update can be incremental Low schedule risk – LMS Development efforts underway –Initial feedback indicates a 24 month development effort Develop to Software requirements Develop to Standards Develop to Policies –Cons Cost Schedule Unknown Risks SSP Electronic Classroom Control Software Change (contd)

13. Questions?

14. Backup Slides

15. 15 Modernized AIM Modernized AIM can tie the entire process together Modernized AIM can tie the entire process together

16. MT Continuum Process 16