1. Demonstrations AIM II CTTL Import to CPM for pre-JDTA
LO Module Webification Prototype 3
CPM Existing Interventions Linking
Front End Analysis (FEA) Prototype
AIM Team
Danette Likens
Mike Coyle

2. AIM II CTTL IMPORT CPM JDTA
Purpose: Automated import of user-specified data elements from existing CTTL and JTA to populate the Job Duty Task Analysis (JDTA) tab as base line JDTA .
How it works:
AIM II data output created as a CSV file with fields for the CTTL number, Source, Text, Type, and Level.
CPM will import CTTL data via CSV file and create the beginning of JDTA work.
If other JTA data is mapped to the same format as the CSV file, it could theoretically be imported into CPM as the beginning of JDTA work. 
Login to CPM at:
Select the JDTA link.
Expand the tree for AIM Team.
Expand the tree for Import CTTLs Testing.
Highlight Occupation – Import CTTLs Testing and select the New icon on the JDTA toolbar.
Enter “Your Initials” for the name of the new job in the right hand window then select the Save button.
With the job titled “Your Initials” highlighted in the left hand window, select the Import icon on the JDTA toolbar.
In the right hand window, select the Browse button.
Navigate to the place you saved the AIM CTTL output file in Step 8 and double left mouse click on the .csv file.
Select the Upload button in the right hand window of CPM.
In the right hand window of CPM, the tester has the options to select any of the skills listed to import as JDTA.
Must have a duty associated with Task IOT import.
Checkmark any task boxes and remember your selection.
Select the Save button.
Verify a dialog box appears stating “Your selection of data is saved;” and select the OK button.
Verify the left hand tree refreshes showing the CTTLs you selected as the Duties, Tasks, Subtasks, and Steps you picked in Steps 21 and 22.
With one of the Duties you imported from the CTTL highlighted in the left hand tree, select the Import icon on the JDTA toolbar.
Checkmark any boxes and remember your selection.
For the boxes you checkmarked, highlight the text in the Skill column and select Task, Subtask, or Step and remember your selection.
Verify the left hand tree refreshes showing the CTTLs you selected as the Tasks, Subtasks, and Steps you picked in Steps 27 and 28.
With one of the Tasks you imported from the CTTL highlighted in the left hand tree, select the Import icon on the JDTA toolbar.
For the boxes you checkmarked, highlight the text in the Skill column and select Subtask, or Step and remember your selection.
Verify the left hand tree refreshes showing the CTTLs you selected as the Subtasks, and Steps you picked in Steps 30 and 31.
With one of the Subtasks you imported from the CTTL highlighted in the left hand tree, select the Import icon on the JDTA toolbar.
For the boxes you checkmarked, highlight the text in the Skill column and select Step and remember your selection.

3. CTTL Import Demonstration

4. Questions?

5. LO Module Webification
Purpose: To meet NETC’s objective to modernize the AIM toolset into a fully Web-based environment
Prototype Information:
“Very” Early stages in prototype development
Build will integrate existing LO Module functions of AIM I/II desktop software – equivalent, not identical, functionality
Common look-and-feel of CPM
CPM and LO Module residing in the same software program will eliminate EDE file transfers
Simplify user account management
Expected delivery date for Phase I – Aug 13

6. LO Module Webification Demonstration

7. Questions?

8. Linking to Existing Interventions (EI) in CPM
Purpose: To create the capability to link web-hosted content for reuse/repurpose content development and maintenance information
New CPM EI capability includes links such as:
PDF or SCORM output of AIM I/II
e-learning
video snippets
electronic performance support objects; etc

9. Linking to Existing Interventions Demonstration

10. Questions?

11. FEA PROTOTYPE DEMO
It doesn't matter how sound the media strategy is if the design strategy is flawed

12. NAVEDTRA 138 The goal of the NETC Front End Analysis (FEA) is to:
analyze skills and knowledge needed to perform the job
assess available technologies for training
perform a media analysis to recommend the best mix of delivery media
determine the best methodology to develop and deliver training content

13. FEA Process Steps Document reason for conducting NETC FEA
Document existing (AS-IS) training requirements
Document new (TO-BE) training requirements
Compare existing (AS-IS) requirements with new (TO-BE) requirements to determine if a gap in training exists
Search existing course material for Reuse, Repurpose, or Reference (R3) to support new training requirements

14. FEA Process Steps
(contd)
Determine new (TO-BE) training requirements delivery methods (list in order of precedence)
Provide recommendations and solutions to close the gap in training
Prepare and finalize NETC FEA output statement
Route completed FEA to CCA for approval and NETC for concurrence
These steps have been incorporated into the functional requirements for the FEA toolset

15. FEA Media Selection Analysis of alternatives
Instructional Media Design Package (IMDP)
Reuse, Repurpose, and Reference (R3)
The front end analysis provides a list of alternatives (e.g., media strategies and methods) used in leveraging existing training interventions for previously selected tasks, and identifies interventions needed to be developed. This analysis will be further refined during the Design Phase and captured in the Instructional Media Design Package (IMDP). During the NETC FEA process, every attempt is made to reuse, repurpose, and reference (R3) existing content.

16. FEA Media Selection Tool
Identification of ‘ideal’ solutions and alternatives
Results feed Business Case Analysis (BCA)
The media selection tool is part of the FEA toolset, which is currently under development. Its design is intended to capture and interpret data entered by the subject matter experts and instructional designers to identify the ‘ideal’ solutions and alternatives for recommended media design and delivery. This information then feeds into the BCA for cost analysis and approval of media for actual development.

17. FEA Prototype Demonstration

18. Questions?

19. Backup Slides

20. Webification Phasing
Phase 1 (roughly analogous to Rel 4.0 of desktop client)
Schedule: Jun 13
Resources: TO 0005 Task 3.2.1
Phase 2 (incorporate Rel 5.0 enhancements)
Schedule: Dec 13
Resources: TO 0011 Task
Phase 3 (incorporate TO 0011/0012 enhancements)
Schedule: TBD
Resources: TBD
Phase 4 (final desktop client LO Module functionality)