AIM FRB Briefing

Strategic Systems Programs (SSP)

Briefer: Jamie SwaimBillet: Personnel Program Coordinator

Learning Center: SLCDate: 11/04/08

Use of Traditional AIM I LP/TG Content

• ILT materials are maintained in Central Site AIM I, which is hosted by NAVAIR Orlando.

• Courses are exported to SCORM V1.2 and imported into Elite.

Top Five AIM Change Requests (ACRs)

• 1. AIM-I-2003-002: Add RRL, OAC, and FAL to HTML output.

• 2. AIM-I-2004-003: Add ability to create changes to RRL items.

• 3. AIM-I-2007-001: Include TG graphics that were embedded in Word in SCORM output.

• 4. AIM-I-2008-002: Allow simultaneous editing of TCCD, COI, and LP/TG.

• 5. AIM-I-2008-004: Add Developing Authority functionality to LO module.

Electronic Classroom and ILT Delivery

• All ECs are connected to a central server, which contains the Elite courses, IETMs, IMIs, and Training Assets Menu.

• The EC Instructor stations are dual-monitored for simultaneous viewing presentation materials and staging of materials for broadcast to Student stations.

• Materials are sent to Student stations from the Instructor station using Robotel.

JTA/NJA Data and ProcessSSP has:• Revised OCCSTDS• Re-developed NJA

and OCCSTDS• Uploaded NJA into

CPM (R&D site) from Excel spreadsheets

• Sent refreshed OCCSTDS for NAVMAC review

SME Panel (SME, SLC, TYCOM,

SSP, Fleet)Develops integrated

OCCSTDS/NJA

Skill Group (KSAs) Tasks (KSAs) Subtasks (KSAs) Steps (KSAs)

Reviewed and approvedSSP and SLC

OCCSTDS WGPulled NJA data out

and created OCCSTDS update

OCCSTDS Review/Approval Process

Operator NJA

Technician NJA

Manager NJA

MT 3 OCCSTDS

FunctionalAreaTasks

Functional AreaTasks

Functional AreaTasks

Functional AreaTasks

MT 2 OCCSTDS

MT 1 OCCSTDS

MTC OCCSTDS

ILE Projects and CPM/LO Module

• MT Continuum– MT Continuum Overview– Development Process

MT Continuum Development Process

MT Continuum Development Process

NJA

Excel

COI/ISD

Word Doc

MT Continuum Process Lessons Learned

• Need to be able to update AIM data with changes made in final development (As Designed = As built) for maintenance of content.

• AIM automatic metadata needs better definition process to make more effective.

• Must have a “GOTS” product do the “finishing work”—or else minor changes require going back to developer EVEN if you have the source files.

• Need a Configuration Management toolset to control final product AND source files. (CMAD did NOT do this, and now no toolset is planned to accomplish).

Top Five AIM/CPM FRM Items• 1. (Multiple FR items): Change Compare Report –

surveillance needs are high and more costly than initial development.

• 2. (Multiple FR items): Work flow (approval) – ensures CM.

• 3. (4.2.4.3): Import open XML into LO Module from other applications – supports maintaining as designed data (LO Module) = as built data (other app).

• 4. (4.2.4.9): Import option to overwrite existing material or not – supports maintenance.

• 5. (4.2.3.41): Build NLOS from existing NLOS and maintain links to existing content AND utilize the same ELO in LO Module – supports content re-use

Points of Contact

Jamie Swaim703.313.0360 or

jamie.swaim@sp15.chenegafederal.com

Richard Garrison301.685.3275 or

richard@garrisonconsulting.biz