SCORM, the Sharable Content Object Reference Model, integrates a set of related technical standards, specifications, and guidelines designed to meet ADL’s functional requirements–accessibility, interoperability, durability, and reusability.

There are numerous benefits to adopting SCORM, and all are related to ADL’s functional requirements for SCORM.

• Accessibility: The ability to locate and access instructional components from multiple locations and deliver them to other locations. For example, a content author can search the ADL Registry and identify relevant content that has already been developed by another organization and deploy that content on any LMS that is conformant to the same version of SCORM to learners anywhere in the world.
• Interoperability: The ability to take instructional components developed in one system and use them in another system. For example, content packaged for delivery in one SCORM-conformant LMS could be loaded into another LMS that is conformant to the same version of SCORM for delivery to learners.
• Durability: The ability to withstand technology evolution and/or changes without costly redesign, reconfiguration, or recoding. For example, upgrading to a new computer operating system should have no impact on the delivery of content to learners.
• Reusability: The flexibility to incorporate instructional components in multiple applications and contexts. For example, e-learning content designed for one organization can be redeployed, rearranged, repurposed, or rewritten by other organizations that have similar learning needs.

The “ilities”, typically benefits associated with SCORM are:

• Accessibility: The ability to locate and access instructional components from multiple locations and deliver them to other locations.
• Interoperability: The ability to take instructional components developed in one system and use them in another system.
• Durability: The ability to withstand technology evolution and/or changes without costly redesign, reconfiguration, or recoding.
• Reusability: The flexibility to incorporate instructional components in multiple applications and contexts.

The Department of Defense (DOD) established the ADL Initiative in 1997 to standardize and modernize training and education management and delivery. The Department of Defense (DoD) Office of the Deputy Assistant Secretary of Defense (Readiness) oversees the ADL Initiative. The vision of the ADL Initiative is to provide access to the highest-quality learning and performance aiding that can be tailored to individual needs and delivered cost-effectively, anytime, and anywhere. The ADL Initiative developed SCORM and the ADL Registry to address ADL’s functional requirements–accessibility, interoperability, durability, and reusability (the “ilities”) within the DoD training, education, and performance support communities, as well as in government, academia, and industry.

SCORM consists of four distinct “books” that contain the critical elements of SCORM:

• The SCORM Overview book contains high-level conceptual information, the history, current status and future direction of ADL and SCORM and an introduction to key SCORM concepts.
• The SCORM Content Aggregation Model (CAM) book describes the components used in a learning experience, how to package those components for exchange from system to system, how to describe those components to enable search and discovery and how to define sequencing rules for the components.
• The SCORM Run-Time Environment (RTE) book describes the learning management system (LMS) requirements for managing the run-time environment (i.e., content launch process, standardized communication between content and LMSs, and standardized data model elements used for passing information relevant to the learner’s experience with the content). It also contains information about content (SCOs) and how they use the API and CMI Data Model to get and set values.
• The SCORM Sequencing and Navigation (SN) book describes how SCORM-conformant content may be sequenced to the learner through an interoperable set of learner-initiated or system-initiated navigation events. The branching and flow of that content may be described by a predefined set of activities, typically defined at design time.

The SCORM Test Suite verifies conformance for LMSs, content packages, and Sharable Content Objects (SCOs). It produces a detailed log of each test outcome.

The SCORM Test Suite is available to anyone. Vendors should use it to self-test their products; developers should use it to test their content; program managers should use it to test content and products during the acquisition processes or for product acceptance.

The Test Suite and other ADL Tools are always free. You can find specific versions in the “Resources” section of each SCORM project or all of the versions in the SCORM Capability “Resources” section

The Sample Run-Time Environment (SRTE) is a prototype LMS that serves as a reference implementation of the LMS components of SCORM. It is an example of how SCORM’s LMS requirements may be implemented within an enterprise LMS. It is a test platform that can be used to view content as it may be displayed in a “real” LMS.

The Sample RTE and other ADL Tools are always free. You can find specific versions in the “Resources” section of each SCORM project or all of the versions in the SCORM Capability “Resources” section

The ADL Initiative created an international community to collaboratively develop a cost-effective distributed learning model that is consistent across national and organizational borders. To achieve this goal, ADL worked with the Institute of Electrical and Electronics Engineers (IEEE), the Aviation Industry CBT (Computer-based Training) Committee (AICC), the IMS Global Learning Consortium, Inc., and the Alliance of Remote Instructional Authoring & Distribution Networks for Europe (ARIADNE). These organizations develop guidelines and specifications that make learning software accessible, interoperable, durable, and reusable. Whenever possible ADL adopts, clarifies, harmonizes, synchronizes, and applies the documentation that these standards organizations develop. ADL promotes the application of standards with reference implementations and tools to assess conformance to the requirements.

Generally, vendors were pleased to have an organization like the ADL Initiative, through the U.S. Department of Defense (DoD), leading this work. Vendors are integral to the success of SCORM. Vendors realized that an environment that enabled interoperable e-learning content, removed from the vagaries of hardware or software changes, would actually create a multitude of potential new business lines. ADL and SCORM vendors and implementers have proven that, regardless of the sector, content can be shared across organizational and functional lines.

The current version of SCORM is SCORM 2004 4th Edition. It is a stable document suite that is ready for implementation.

Even though ADL cooperates and collaborates broadly across the federal government, ADL has no power or authority to mandate SCORM conformance for the federal government. However, many Federal agencies currently require their e-learning products to be SCORM-conformant when applicable. Within the U.S. Department of Defense, DoDI 1322.26, Development, Management, and Delivery of Distributed Learning, mandates the use of SCORM when applicable.

Numerous SCORM-conformant products, including both systems and content, are widely available. Please see the SCORM Certification section for more details on Certified Products and SCORM Adopters

Not necessarily. Content is not required to track everything to be conformant. Check with your vendor to determine the level of tracking provided.

A product that is SCORM conformant is not necessarily 508 compliant. However, does not hinder an authors ability to create 508 compliant materials.

It depends. SCORM incorporates portions of the AICC specification via the IEEE Data Model and API Standards. LMS or content products that adhere to Appendix B of the AICC CMI001 specification may, in some cases, be able to work with products conformant to SCORM.

Yes. LMSs and content can conform to both standards. Vendors can offer separate versions of their products for each standard, or can implement both standards in a single version. Conformance to one standard does not automatically imply conformance to the other.

SCORM does not address formatting issues like layouts, fonts, and color schemes.

SCORM and ADL generally refer to ‘web-based’ or ‘browser-based’ instruction that simply requires access to a web browser. An Internet connection is not always necessary. Most vendors address this issue independently since the more widely accessible their content and/or systems are, the more markets they are able to access.

The launching of content and the exchange of data such as learner ID numbers and test scores between LMSs and content are among the most important topics addressed by SCORM. These areas are addressed by the SCORM Run-Time Environment (RTE). SCORM also covers other critical areas.

SCORM also addresses a standard way to structure and exchange learning content. This occurs through the application of the IMS Content Packaging specifications.

In addition, SCORM defines a method for representing the intended behavior of an authored learning experience such that any LMS will sequence discrete learning activities consistently. This is accomplished through the application of the IMS Simple Sequencing Specifications.

Probably, as long as the content and the LMS conform to the same version and edition of SCORM.

No. SCORM requires use of the ECMAScript API defined in the SCORM RTE book.

SCORM does not standardize the implementation of LMSs. Although the standardized communication mechanism imposes some behavioral and functional requirements on the LMS, SCORM’s goal is to ensure that content runs and behaves the same on different LMSs.

There are no SCORM-imposed requirements on the size of a learning resource. Size should be based on several considerations:

• Reuse
• Portability
• Learner data tracking requirements
• Learning objectives or pedagogical model

A Package Interchange File (PIF) is a single file (such as a .zip file) that includes a top-level Manifest file named “imsmanifest.xml” and all other physical files as identified by the Manifest. A PIF is a concise web delivery format and a means of transporting related, structured information.

There is no requirement to incorporate packages into a Package Interchange File (PIF). A package may also be distributed on a CD-ROM or other removable media without being compressed into a single file. An IMS Manifest file and any other required supporting XML files (e.g. XSD) must be at the root of the content directory structure.

If you need to track the learner’s experience with the content, then SCORM provides an API and data model that enable the interoperable tracking of performance data. If you do not need to track the learner’s experience your content is not required to use the SCORM API. SCORM considers content that does not use the SCORM API to be non-communicative, and refers to it in the SCORM Documentation Suite as an asset.

At this time, ADL does not recommend the use of sub-manifests. In SCORM 2004 4th Edition, SCORM designates any content that uses a sub-manifest as non-conformant.

Conformance is the following of a functional requirement. The SCORM is a set of functional requirements, so if a product adheres to these requirements, it is conformant. Compliance is the following of a directive, law, or procedure. DoDI 1322.26 is a directive, so an organziation may comply with that directive. Certification is a procedure, a product would be compliant if Certified.

Contact Us. Thanks!