zip file for each Content Package (CP), providing evidence that the CP SCORM. The following documents will be cited in the solicitation document (keyed to the appropriate section) for distributed learning (DL): ADL Initiative SCORM conformance testing requirements.Īcceptance shall be based on the following:Ĭonformance: An error-free repeatable test log output saved as a. The contractor shall ensure distributed learning content is conformant to SCORM. SCORM Acquisition GuidanceĭoD and other Federal Government organizations are encouraged to use the following statement in their acquisition documents (e.g., statements of work, performance work statements, or other applicable program requirements documentation): DoDI 1322.26 contains the current guidance for SCORM conformance in DoD.
Developers who are implementing other versions of SCORM are encouraged to modify their work to comply with one of the existing specified versions. While the ADL Initiative (and DoDI 1322.26) now recommends xAPI and cmi5 solutions for new e-learning acquisitions and implementations, it is understood that SCORM solutions are still in wide use to enable interoperability (course re-use) across compliant systems. LETSI produced over 100 white papers that would later become essential artifacts and sources of requirements for the newer xAPI specification for e-learning. In 2008, the Learning-Education-Training Systems Interoperability (LETSI) Federation was formed to investigate the next generation of SCORM requirements. The ADL Initiative maintains documentation for SCORM 1.2, SCORM 2004 3rd Edition, and SCORM 2004 4th Edition (see Versions & Resources section below). The most recent release (2009) is SCORM 2004 4th Edition. Version 1.0 of SCORM was released in 2000, followed by SCORM 1.2 in 2001. SCORM HistoryĪ 1999 executive order signed by President Bill Clinton established a task force charged with developing new standards and specifications for e-learning across the Federal Government and the private sector.
Unlike SCORM, xAPI can be used to track and share data from mobile learning, simulations, virtual worlds, serious games, real-world activities, wearable devices, experiential learning, social learning, offline learning, and more. To extend these concepts to track performance data on emerging learning capabilities (e.g., mobile learning), DoDI 1322.26 has been updated to allow a more capable standard called the Experience API, or xAPI.
Under a series of DoD Instructions – most recently DoDI 1322.26 – SCORM has been officially specified as one of the allowed metadata tracking options for DoD e-learning content. SCORM allowed browser-based e-learning with plug-and-play portability, reusability, and instructional sequencing of self-paced content. With this, the ADL Initiative designed SCORM to leverage standard web technologies as well as emerging learning technology specifications. To provide organizations with the capability to reuse instructional components in multiple applications and environments regardless of the tools used to create them, the ADL Initiative led and conducted the research required to ensure that content could be separated from context specific run-time constraints and proprietary systems so that it could be incorporated into different applications. Conversely, large content vendors often specified their own delivery environment, requiring organizations to implement different delivery modules for each content vendor. This research was driven by the challenge that enterprise organizations faced when upgrading systems or changing vendors, which often required them to abandon expensive content and start from scratch. The Sharable Content Object Reference Model (SCORM®) was created in 2000 by the ADL Initiative to address e-learning interoperability, reusability, and durability challenges.