16
AIM-IETM Interface AIM-IETM Interface 15 March 2012 15 March 2012

AIM-IETM Interface 15 March 2012

Embed Size (px)

DESCRIPTION

AIM-IETM Interface 15 March 2012. The Problem. No cost-effective method for responsively keeping learning content current with changes to authoritative technical data AIM solved for paper and CD-based tech data in 2000 - PowerPoint PPT Presentation

Citation preview

Page 1: AIM-IETM Interface 15 March 2012

AIM-IETM InterfaceAIM-IETM Interface15 March 201215 March 2012

Page 2: AIM-IETM Interface 15 March 2012

The ProblemThe Problem• No cost-effective method for responsively

keeping learning content current with changes to authoritative technical data– AIM solved for paper and CD-based tech data in 2000– Navy shifting to on-line enterprise data repositories

with no enterprise solution to this problem– Even more important for distributed Web-based

training as instructor surveillance efforts are removed

– Must address emerging S1000D standard adopted by DoD / Navy

Page 3: AIM-IETM Interface 15 March 2012

Functional RequirementFunctional Requirement• Support design and development of learning

content tied to performance requirements• Streamline QA review, approval, and

configuration management• Simplify instructor preparation and delivery• Promote efficient life-cycle surveillance and

update• Enhance cost-effective re-purposing of proven

content

Page 4: AIM-IETM Interface 15 March 2012

Design and DevelopmentDesign and Development• Technical and procedural documents are primary

authoritative data source for technical training content

• For ILT, developer must associate technical / procedural documents to learning content for display in classroom

• For self-paced training, developer must include pertinent data and associate tech / procedural document to learning content for computer display and student interaction

Page 5: AIM-IETM Interface 15 March 2012

QA Review, Approval, and CMQA Review, Approval, and CM• QA must confirm associations made with

and data copied from technical / procedural documents accurate and current

• Approval authority must ensure complete and accurate learning content in place

• Content manager must ensure approved content is prepared by instructors and taught in classrooms / delivered by LMS

Page 6: AIM-IETM Interface 15 March 2012

Instructor Preparation / DeliveryInstructor Preparation / Delivery• As part of preparation, instructor must

confirm hundreds of links to technical / procedural documents and prepare to present documents in classroom

• During presentation, instructor must quickly display authoritative documents to students

• For self-paced content, students must launch technical / procedural documents for reference and interaction

Page 7: AIM-IETM Interface 15 March 2012

Life-cycle Surveillance / UpdateLife-cycle Surveillance / Update

• Curriculum maintainer must re-confirm accuracy of all links in baseline learning content to technical / procedural documents each time document is updated

• Based on that analysis, maintainer must generate change / rev to learning content to ensure it remains current and accurate

Page 8: AIM-IETM Interface 15 March 2012

Overview of Overview of Operational Operational

IETM/AIM InterfaceIETM/AIM Interface

Page 9: AIM-IETM Interface 15 March 2012

BenefitsBenefits• Integrated, standardized, configuration-

managed development, QA, and management of baseline curricula and electronic classroom content

• Reduced workload, better accuracy, and faster turnaround for schoolhouse LSO and instructor staff

• Reduced workload, better accuracy, and faster turnaround of training content surveillance and update

Page 10: AIM-IETM Interface 15 March 2012

A Few Metrics . . .A Few Metrics . . .• A single 23-week replacement course on-line

today contains more than 1500 separate links to more than 5 separate technical / procedural manuals

• All tech / procedural manuals updated quarterly

• @ 2 minutes per link, review for possible changes during curriculum maintenance would take 50 person-hrs per quarter

Page 11: AIM-IETM Interface 15 March 2012

Demo of Current Demo of Current InterfaceInterface

Page 12: AIM-IETM Interface 15 March 2012

Technical Process Technical Process for IETM Interfacefor IETM Interface

Page 13: AIM-IETM Interface 15 March 2012

Interface ProcessInterface Process• EXTRACT structural data (“table of contents”) from IETM

database

• IMPORT structural data into AIM

• BROWSE IETM Structure via Resource Requirements List (Site RRL). Launch IETM viewer/browser to verify applicability of reference

• LINK specific Related Instructor Activity (RIA) or Trainee Guide (TG) Sheet to IETM reference

• CONDUCT SURVEILLANCE of curricula by importing revised IETM structural data and using detailed Change Impact Report/auto-generated maintenance flags signaling affected curriculum elements

Page 14: AIM-IETM Interface 15 March 2012

DevelopmentDevelopment

IETM Authoring

System

Resource Requirements

List (RRL)

Lesson Plan /

Trainee Guide

Section (Enabling Learning Object)

IMPORT

Positioning msg to IETMViewer/Browser

IETM Display with correct file / node

IETM Viewer/Browser

EXTRACT

BROWSE(from LP/TG or Section)

LINK

IETM Structural ("Table of Content")Baseline data

Authoring Instructional Materials

(AIM)

Page 15: AIM-IETM Interface 15 March 2012

Surveillance/UpdateSurveillance/Update

IETM Authoring System

Resource Requirements

List (RRL)

Lesson Plan /

Trainee Guide

Section (Enabling LearningObject)

IMPORT

Positioning msg to IETMViewer/Browser

IETM Display with correct

file and frame

IETM Viewer/Browser

EXTRACT

BROWSELINK

Change Data(including "version" information for

added or modified elements)

Change Impact Report

Page 16: AIM-IETM Interface 15 March 2012

IETM AuthoringIETM Authoring Unique Element ID: Alphanumeric value used

by IETM to assign distinct identifier for specific element

Element Title: English language descriptive name for each individual node in IETM

Persistent Element ID: Unique element ID maintained over multiple versions of IETM

Version Information at Element Level: Alphanumeric value used by individual IETM element to identify change level for that particular element (when element was added or modified)