1. AIM Background & Current Capabilities Brief to FRB Jake Aplanalp AIM/CPM Program Manager NAWCTSD Orlando 407.380.4685 Jacob.Aplanalp@Navy.mil 4 November, 2008

2. Focus of Presentation AIM Background & History AIM Current Software Status AIM Future Software Status Demos, Questions

3. 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 data changes 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

4. AIM-based Learning Content Usage* Big “3” Example Others include: NSWC SPAWAR NMPT&E NNSY CPPD CNE CID CEODD CSS *Data captured in 4 th Quarter of FY07

5. AIM Management Organization System Support Office (SSO) NAWCTSD Orlando System Support Office (SSO) NAWCTSD Orlando Program Manager OPNAV N75 Program Manager OPNAV N75 Program Manager NAWCTSD Orlando Program Manager NAWCTSD Orlando Configuration Control Board (CCB)/ Resource Sponsorship: Surface/Air/Sub/NETC Configuration Control Board (CCB)/ Resource Sponsorship: Surface/Air/Sub/NETC Functional Area Manager OPNAV – N00T Functional Area Manager OPNAV – N00T Executive Steering Committee (ESC) Functional Requirements Board (FRB) Executive Steering Committee (ESC) Functional Requirements Board (FRB) Functional Area Manager OPNAV – N12 (proposed) Functional Area Manager OPNAV – N12 (proposed) Functional Area Manager OPNAV – N79 Functional Area Manager OPNAV – N79 Functional Area Manager OPNAV Functional Area Manager OPNAV Columbus Technologies- Prime Support Contractor Columbus Technologies- Prime Support Contractor

6. CNET drafts Operational Requirement (OR)1981 NPRDC Conducts R&D1981-87 NPRDC Awards R&D Contract1987 CNO Establish Project Manager 1989 AIM MNS/Milestone 0 Approved1990 Milestone I/II approved1992 Initial version of AIM (UNIX) distributed1993 Milestone III approved (Implementation)1994 AIM System Support Office (SSO) at NAWCTSD Established1994 AIM I Implementation1996 AIM II Implementation1997 Program Management Shift to NAWCTSD1997 IETM Interface1998 SCORM Output Utility2001 SQL Server2002 Word as editor; IMI Library2003 AIM first GOTS SCORM Adopter2004 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

7. 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

8. 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

9. 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

10. AIM Modernization Timeline

11. Software Demo & Discussion