110 likes | 297 Views
MT Continuum Status. Gerry Cullison, SSP Mark Campbell, MT Continuum Team Jamie Stewart, AIM team. 18 Sep 12. Overview. MT Continuum overview Application to other communities Project status Lessons learned for other NETC communities SSP Electronic Classroom Control Software Change.
E N D
MT Continuum Status Gerry Cullison, SSP Mark Campbell, MT Continuum Team Jamie Stewart, AIM team 18 Sep 12
Overview • MT Continuum overview • Application to other communities • Project status • Lessons learned for other NETC communities • SSP Electronic Classroom Control Software Change
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 Project 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
Application to Other Communities • Based on NETC-mandated JDTA as fleet performance requirement basis for learning content design and development (NAVEDTRA 137) • 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.
Project Status • Plan & Analyze Phases Completed • JDTA – 3 Projects (Operator/Technician /Manager) • Revision/refinement will be needed. • Too granular • Not completely ‘Task based with knowledge to support performance’ centric. KPL and SPL (NAVEDTRA 137) • Revised project structure supports Operator, Technician and Manager training via initial training and follow on At Sea & Ashore Phases.
Project Status • Design Phase On going (In conjunction w/Development) • Approval of learning objectives (COI) • Refining levelization between initial operator and later technician phases • Separation of performance and knowledge objectives • Straight conversion of performance objectives to learning objectives • COI Revision completed September 2012 • ISD considerations elements as part of script-storyboard (SSB) effort • A significant effort that extends SSB production task time in the Development Phase. • Early and assertive ISD involvement and close ISD/SME collaboration. • Content thread concept – developing content that bridges learning levels
Project Status • Design Phase On Going (In conjunction w/Development) • Comprehensive Assessment Design Strategy still needed • NAVEDTRA 132 Revision needed • Blended assessment to compliment blended delivery • Performance Assessment needs further development • Delivery Method Analysis Process still needed • Scientific/Justifiable/Repeatable • Development Phase (15 May 2011) • LOM via NETPDTC server – CPM via AIMEREON server • Central Site connectivity still a challenge
Project Status • Development Phase (15 May 2011) • Maturity of Design Documents and Processes • IMDP, Learning Objectives (ISD Considerations), Process Documents, Assessment Design, Time to Train Estimations, Delivery Method Analysis • Establish change request process in Design Phase • Storyboard Training (IMI) • Understanding skill mix and team responsibilities • Levelization of content • Early and frequent collaboration
SSP Electronic Classroom Control Software Change • SSP Current Approach: Integrate CCS into the SSP LMS • Design in progress • Defining requirements and building use cases