SCORM State of the Union

1
SCORM State of the Union

• Philip Dodds
• Paul Jesukiewicz
• Schawn E. Thropp
• Plugfest 9
• Wednesday, February 23, 2005

2
We have come a long way

• From a boy and dog in late 1997 to
• Global adoption of SCORM
• Content interoperability
• Stable feature set
• A solid model for reusability
• A stable platform
• International Plugfest February 2004
• Over 320 participants
• 210 organizations
• 37 Countries
• 77 organizations participated in Plug and Play
• demonstrating more than 120 products including
  authoring tools, content examples, and learning
  management systems.  

3
SCORM Core Complete
4
SCORM Evolution
SCORM 1.1
SCORM 1.2
SCORM 2004
Content Aggregation Model Metadata Binding
Content Aggregation Model Metadata
Binding Adds Content Packaging Content
Organization
Content Aggregation Model Metadata
Binding Content Packaging Content
Organization (updated/fixed)
CAM 1.3
Run Time Environment API Data Model
Run Time Environment API Data
Model (updated/fixed)
Run Time Environment API Data
Model (updated/fixed)
RTE 1.3
Sequencing Navigation Rules and Behaviors (new)
SN 1.3
5
(No Transcript)
6
Future Versions of SCORM
Read my lips! No new features Its time to
let it bake and deploy
7
Stabilization / Clarification / Issue Resolution
SCORM 2004 January 2004
SCORM 2004 2nd Edition July 2004
SCORM 2004 3rd Edition Q2 2005 (est.)
Bug Fixes, Corrections Clarifications
8
SCORM 2004

• SCORM 2004 3rd Edition
• Release awaiting final ballot of IEEE XML Binding
  of LOM
• Incorporates bug fixes to IMS Content Packaging
• Rolls contents of the SCORM Addendum Document
  into core document set
• Remember SCORM SCORM 2004 Addendum

9
Certified Products

• SCORM 1.2
• LMS 47
• Content 25
• SCORM 2004
• LMS 2
• www.ADLNet.org
• Certification of SCORM 2004 is following the same
  pattern as happened with 1.2

10
Adopters

• SCORM 1.2
• 134 Adopters
• SCORM 2004
• 9 Adopters
• www.ADLNet.org
• Adoption of SCORM 2004 is following the same
  pattern as happened with 1.2

11
Lots of Supporting Infrastructure

• SCORM 2004 (2nd Edition) The books of SCORM
• SCORM 2004 Addendum
• SCORM 2004 Conformance Requirements
• Cross Domain Scripting Guidance
• SCORM 2004 Baby LMS (Sample Run Time
  Environment)
• SCORM 2004 Test Suites (LMS Content)
• ADL SCORM Certification Centers (2)
• SCORM 2004 Development tools (Reload)
• SCORM 2004 Utilities
• SCORM 2004 Content examples and guidance
• e.g. Flash, Director,

12
SCORM Stewardship
ADL continues to examine the best path to
independent, international stewardship of
SCORM ADL will continue to maintain and support
SCORM until an appropriate organization is
identified
13
Supporting Activities

• Current technical activities that support SCORM,
  but are not part of it
• Sharable State Persistence (SSP)
• XML Content Formats
• Package Exchange Notification Services (PENS)
• IEEE XML Binding of the Content Object
  Communication Data Model
• IEEE Competencies

14
Snap Shots From The Field

• Paul Jesukiewicz ADL CoLab Director
• Input gathered in fall of 2004
• Would like to get updates throughout Plugfest
• Will report out findings on Friday

15
Service LMS Implementation

• Current Planned
• Army ALMS (Saba version 3.4.1) ALMS
  (Saba 5.2)
• ILMS (Aspen v 1.1 w/Build 7.0.1173)
  (Spring 05)
• Aspen v2.0
• Core v2.3.8
• Meridian KSI
• Blackboard
• mGen
• Navy THINQ THINQ 5.2
• (Jan 05)
• Air Force No single LMS (currently 7)
  Meridian V 3.0
• Meridian KSI (9 out of 16 AF orgs)
  (Dec 04)
• Marine Corps THINQ Training Server 4.6
  THINQ

16
SCORM Content Implementation

• Army
• Navy
• Air Force
• Marine
• Corps

• There are 43 fielded courses that are SCORM
  compliant 13 SCORM v1.1 and 32 SCORM v1.2.
• There are 14 SCORM v1.1 compliant courses still
  under development and 107 SCORM v1.2 compliant
  courses under development.
• One completed common critical task (for the 2005
  common tasks tests) is SCORM v1.2 compliant and
  38 common critical tasks under development/update
  will be SCORM 1.2 compliant.
• All of their WBT content is 1.2 SCORM
  conformant as long as the LCMS publishes it to
  SCORM 1.2.
• 80 of the WBT Content is SCORM 1.2
• 20 of the ADL content is SCORM 1.2 and 80 is
  AICC

17
LCMSs and Authoring Tools

• Army
• Navy
• Air Force
• Marine
• Corps

• Does not specify a specific development tool or
  LCMS they require that courseware comply with
  specific standards regardless of the authoring
  tool used. Currently they have courseware being
  developed using Flash, ToolBook, Dreamweaver,
  HTML editors, and Contractor produced
  productivity tools. This list is not all
  inclusive.
• All "A" school content being developed
  in Outstart Evolution
• HTML, XML, Flash
• None specified. Some of the USMC's commercial
  content developers use Outstart Evolution LCMS
  and some use a proprietary toolset called DOMS

18
SCORM 2004 Migration

• Army
• Navy
• Air Force
• Marine
• Corps

• The Army plans to start requiring SCORM 2004
  conformance in their courseware development
  contracts in about 6-9 months (after they receive
  a SCORM 2004 conformant LMS, develop their
  business rules, and develop their contract
  requirements.) Also as existing courses are
  updated, the plan is to convert them to be SCORM
  2004 conformant.
• LMS plans to be SCORM 2004 by Jan 05
• LCMS sometime during early CY05. Navy plans to do
  some experimentation to determine the efficacy of
  exploiting certain SCORM 2004 features in
  particular sequencing.  
• As soon as LMS vendor is SCORM 2004 - currently
  planned for Jan 05
• Q1 FY06

19
Major DoD Acquisition Programs

• Major DoD programs requiring SCORM
• F-35 Joint Strike Fighter (JSF)
• Future Combat Systems (FCS)
• Joint Tactical Radio System (JTRS)
• V-22 Osprey

20
SCORM Adoption Outside DoD

• Government Agencies
• IRS, CDC, DoL, NGB, NSA, USPS, TSA, VA, NASA,
  TSWG, others
• Industry
• Daimler Chrysler, IBM, Microsoft, Boeing, LG,
  Verizon, Delta Airlines, Oracle, Cisco,
  McDonalds, Home Depot, others.
• International
• Australia, Canada, Asia, Europe, Latin America

21
ADL Plugfests (then and now) provide a safe haven
for collaboration of industry and users. The
primary purpose is to promote successful adoption
of key specifications and the development of
guidance for implementation and
deployment. Working code trumps all theories
22
Meet The ADL SCORM Team

• Schawn Thropp ADL Technical Team
• Demos of ADL tools and utilities in Plug-n-Play
• Available for support
• Are here to answer your questions
• Can train you on conformance testing here on-site

23
ADL Technical Team

• ADL Technology Center
• Jennifer Brooks RELOAD Development Editor
• Jeff Falls Conformance Test Suite, SSP
• Cande Filip Instructional Design
• Matt Handwork Conformance Test Suite
• Rob Harrity Sample Run-Time Environment, SSP
• Kraig Mentor Content Developer/Examples
• Lori Morealli Conformance Test Suite
• Angelo Panar Sequencing, ADL Registry
• Doug Peterson Sample Run-Time Environment
• Aaron Perrin ADL Registry
• Aaron Silvers Content Developer/Examples
• Schawn Thropp SCORM, Standards/Specifications

24
ADL Technical Team

• Joint ADL Co-lab
• Steve Slosser
• Academic ADL Co-lab
• John Toews
• ADL Canada Partnership Lab
• Roger St-Pierre