110 likes | 200 Views
AIM Background & Current Capabilities Brief to FRB. 4 November, 2008. Jake Aplanalp AIM/CPM Program Manager NAWCTSD Orlando 407.380.4685 Jacob.Aplanalp@Navy.mil. Focus of Presentation. AIM Background & History AIM Current Software Status AIM Future Software Status Demos, Questions.
E N D
AIM Background & Current Capabilities Brief to FRB 4 November, 2008 Jake Aplanalp AIM/CPM Program Manager NAWCTSD Orlando 407.380.4685 Jacob.Aplanalp@Navy.mil
Focus of Presentation • AIM Background & History • AIM Current Software Status • AIM Future Software Status • Demos, Questions
Authoring Instructional Materials (AIM): • Government-owned & managed system used by the Navy to design, develop, update, manage, and integrate training content • Provides automated conformance to standards (NAVEDTRA 130A/131A, ILE, & RIT II) resulting in efficient, cost effective development & maintenance of learning content • Links learning requirements to performance standards • Links learning content to Interactive Electronic Tech Manuals (IETMs) (**S1000D & other formats) • Automates identification and notification of potential learning content update requirements based on performance standard & tech datachanges • Streamlines integration of changes into previous learning content baseline with minimum impact (because built on relational database) • Supports multiple output methods (paper, PDF, HTML, & SCORM conformant XML formats) AIM is a mature application & service provider supporting the development & sustainment of 300,000+ instructional hours of formal Navy training content
AIM-based Learning Content Usage* • Others include: • NSWC • SPAWAR • NMPT&E • NNSY • CPPD • CNE • CID • CEODD • CSS Big “3” Example *Data captured in 4th Quarter of FY07
AIM Management Organization Configuration Control Board (CCB)/ Resource Sponsorship: Surface/Air/Sub/NETC Functional Area Manager OPNAV Functional Area Manager OPNAV – N79 Functional Area Manager OPNAV – N00T Functional Area Manager OPNAV – N12 (proposed) Executive Steering Committee (ESC) Functional Requirements Board (FRB) Program Manager OPNAV N75 Program Manager NAWCTSD Orlando Columbus Technologies- Prime Support Contractor System Support Office (SSO) NAWCTSD Orlando
CNET drafts Operational Requirement (OR) 1981 NPRDC Conducts R&D 1981-87 NPRDC Awards R&D Contract 1987 CNO Establish Project Manager 1989 AIM MNS/Milestone 0 Approved 1990 Milestone I/II approved 1992 Initial version of AIM (UNIX) distributed 1993 Milestone III approved (Implementation) 1994 AIM System Support Office (SSO) at NAWCTSD Established 1994 AIM I Implementation 1996 AIM II Implementation 1997 Program Management Shift to NAWCTSD 1997 IETM Interface 1998 SCORM Output Utility 2001 SQL Server 2002 Word as editor; IMI Library 2003 AIM first GOTS SCORM Adopter 2004 Prototype LO Module; NMCI certification** 2005 Navy ILE ILT authoring/maintenance tool** 2006 Prototype Content Planning Module (CPM)** 2007 NMCI Certification & Distribution of AIM LO Module** 2008 CPM Operational** 2008 AIM Historical Perspective Program of Record with history of continuous improvement and successful adaptability in meeting the user’s changing requirements and technology advances. **Key Components of Modernized AIM
AIM Current Software Status • AIM I/II Rel 3.3 • Superseded Rel 3.2.1 • NMCI certified in May 08 • Pushed to NMCI end users in Jun-Jul 08 • Includes first version of Learning Object (LO) Module • Central site Citrix Metaframe enhancements • CMS Web service interface to CeTARS • Content Planning Module (CPM) 3.0 • GAT conducted May 08 • Operational s/w posted Jun 08
AIM Software Plans - Modernization • AIM I/II Rel 4.0 • LO Module • Initial GAT conducted Jun 08 • Significant additional functionality being coded now; in work for Mar 09 delivery for testing • Anticipated NMCI push Jun 09 • CPM • Significant additional functionality being coded now; in work for Mar 09 delivery for testing • Anticipated operational Jun 09 • Interim builds available to support ongoing ILE projects • FRB-prioritized ACRs incorporated in LP/TG modules
AIM Software Plans – Modernization (contd) • AIM I/II Rel 4.1 • LO Module • requirements define by FRB feedback on FRM • planned delivery for GAT and NMCI testing in Mar ‘10 • anticipated NMCI push in Jun ‘10 • CPM • requirements defined by FRB feedback on Functional Reqts Matrix • planned delivery for GAT testing in Mar ‘10 • Operational in Jun ‘10 • Interim builds available to support ongoing ILE projects • FRB-prioritized ACRs incorporated in LP/TG modules