Next Generation SCORM

ADL will facilitate, coordinate and lead the design of a new model (and empower its development) to support innovative learning experiences. The Next Generation SCORM capability supports the NEXT GENERATION LEARNING ENVIRONMENT of ADL’s overarching research and development strategies.
Next Generation SCORM begins with a conceptual model based on industry trends, stakeholder requirements, and ADL’s historical experience. Initial components of the conceptual model are in place to address existing DoD requirements restricted in the current SCORM environment.
The Next Generation SCORM capability will contain several projects aimed at providing learning solutions for DoD stakeholders. Many of these projects will eventually be seamlessly integrated into the Next Generation SCORM as it becomes more defined.
This R&D effort will include a transition phase to shift pedagogy, technology, best practices, policy and procedures to the DoD, government, academia and industry.
The Next Generation SCORM capability is aimed at supporting use cases, submitted by an interested community. The community has already provided input through various discussions, ADL Help Desk tickets, and most recently, through a requirements gathering and ranking exercise as a part of Project Tin Can.
Research Summary
The Next Generation SCORM is being implemented in phases. Phase I identifies the gaps from the current online learning environment that uses SCORM. As many of the pieces are antiquated, this is essentially legacy SCORM even though it is the current version. Phase II extends the environment by implementing individualized adaptive training.
ADL Summit
ADL will be hosting a summit in early 2012 that will bring standards organizations together to advance the Next Generation SCORM effort. Stay tuned to ADLnet.gov for announcements regarding the details of this summit.
Phase I
Next Generation SCORM Phase I activities address a much-needed update to the learning content run-time environment (RTE). The legacy run-time is embedded in the browser and accessible via a JavaScript object which, although simple to use, has significant limitations.
Phase I includes a new RTE powered by web services. The change to a web service binding requires a new data model approach since SCORM does not define how to extend the data model or how to use it with different data bindings such as XML or JSON. As part of the data model work, extensibility of data model elements will be “built-in” from the beginning. This means any community of practice will be able to extend a “core” data model with community-defined models. In other words, you will be able to track what you want and how you want it.
Phase I targets many use cases not natively supported by SCORM. High-level use cases are included in the list below:
- Tracking of detailed learner interactions and learner performance characteristics that are richer in scope and depth than assessments involving score thresholds,
- Tracking of out-of-browser content to include games, simulations, virtual worlds and mobile apps,
- Launch and tracking of multi-modal content that renders intelligently based on device (ex. tablet, smart phone, laptop),
- Access to learner data during or after the learner experiences the content,
- Hosted content via a content as a service (CaaS) model, and
- Tracking of community-driven data models
The following are summaries of each of the efforts. Some have been absorbed into other projects, but we welcome anyone and everyone who wants to participate – it’s not too late to get involved. Check out the “Projects” tab for more information on any of the following:
- RTWS – Development effort of a Run-Time Web Service
- CMI5 – Next iteration of the original SCORM RTE Data Model
- TinCan – R&D effort of a Data Model starting from scratch
- Proofs-of-Concept – User requirement driven implementations of current versions of SCORM in Next Generation SCORM environments
Each Proof of Concept area includes a detailed mapping of community requirements to the actual efforts of each project.
Phase II
Phase II is in very early stages. ADL is counting on the continued involvement of the ADL Community in requirements gathering to make the individualized training in Phase I into adaptive training.

Project Tin Can, launched as a simultaneous Data Model creation exercise with CMI5, builds a model from scratch with the understanding of today’s technology and learners. Tin Can gathered community input on a variety of levels and moved in a direction that yielded a model centered around the user experience. Learn More…

The Learning Record Store is a proof-of-concept that is at the core of Next Generation SCORM activities. With the notion of web services, some or all functions traditionally associated with a Learning Management System are split out. The Learning Record Store takes over the tracking functionality. Learn More…

Integration with multiple user-interfaces and platforms is a goal of Next Generation SCORM. ADL, as a proof-of-concept, has deployed an Android app that not only uses the native environment (no browser needed), but is designed for instructors and administrators. This API (Application Programming Interface) exposes data traditionally obscured by Learning Management Systems by viewing data from multiple users and activities simultaneously. Learn More…

Requirements such as the rigid CMI Data Model, ECMAScript (JavaScript), and browser have hampered efforts of games and simulation in the current versions of SCORM. As a proof-of-concept, ADL has integrated with the Unity game engine to produce learning content that is delivered and tracked in a game environment. Learn More…

Content As a Service (CaaS) is a proof-of-concept that throws the idea of content packages out the window. Content can run as a web service and thus be on any platform, in a variety of different formats, and in multiple modalities. The process of “importing” content and the issues of cross-domain scripting, both stigmas of the current versions of SCORM, disappear. Learn More…

The information that is tracked by the Next Generation SCORM must be evaluated to make sure it is in-line with community needs and the evolvement of technology. CMI was the Data Model specification used in legacy SCORM. The next version of CMI, CMI5, will build on that model and modernize it. Learn More…

Legacy SCORM content is not obsolete. While platforms, technologies, and even learners have changed, millions of SCOs have been created that are instructionally sound and very valuable. ADL recognizes the need to have the Next Generation SCORM be backward compatible and has already developed, as a proof-of-concept, a wrapper for legacy content to integrate directly into the focus areas of Next Generation SCORM. Learn More…

The Next Generation SCORM seeks to deploy across all platforms and devices and move passed the online, single-session, browser-based model that was legacy SCORM. The Run-Time Service project looks to incorporate offline learning, out-of-browser learning, and enable deployment on mobile devices. It will use newer technology to solve these problems as well as the cross-domain scripting issue. Learn More…
ADL Technical Team Lead – Jonathan Poltrack
Jonathan Poltrack has been involved with the ADL Initiative since 1999 where he was an early contributor to the SCORM. As a software engineer, he has contributed to many ADL software projects including the SCORM Test Suite, the Sample Run-Time Environment, the ADL SCORM RELOAD Editor and numerous content examples. Recently, Jonathan has been leading efforts aimed to transition SCORM while specifying a new learning platform to support new types of systems and content. This includes, but is not limited to, coordination with international specification and standardization bodies such as the Aviation Industry CBT Committee (AICC) and the Institute of Electrical and Electronics Engineers (IEEE).

Welcome to the Next Generation SCORM Capability Resources section. If there is something that you need to know or find and cannot, please ask the experts! (helpdesk@adlnet.gov)
ADL is always looking for feedback regarding Next Generation SCORM and other efforts. Please email us with questions and concerns at helpdesk@adlnet.gov.
Team
|
ADL Technical Team Lead – Jonathan Poltrack
Jonathan Poltrack has been involved with the ADL Initiative since 1999 where he was an early contributor to the SCORM. As a software engineer, he has contributed to many ADL software projects including the SCORM Test Suite, the Sample Run-Time Environment, the ADL SCORM RELOAD Editor and numerous content examples. Recently, Jonathan has been leading efforts aimed to transition SCORM while specifying a new learning platform to support new types of systems and content. This includes, but is not limited to, coordination with international specification and standardization bodies such as the Aviation Industry CBT Committee (AICC) and the Institute of Electrical and Electronics Engineers (IEEE).
|
|
Robert Chadwick
Technical Team Member
|
|
Tom Creighton
Technical Team Member
|
|
Nik Hruska
Technical Team Member
|
|
Andy Johnson
Technical Team Member
|
|
Aaron Silvers
Technical Team Member
|
|
Melanie VanHorn
Technical Team Member
|