CMI Data Model Harmonization


Current SCORM Use of the Data Model
SCORM has enabled interoperable tracking of learner progress since its inception through the ADL Data Model. Originally founded on the AICC CMI Data Model, ADL has continued to participate in the data model’s evolution into and through IEEE LTSC. Currently, SCORM 2004 4th Edition provides a stable and well-defined basis for capturing learner performance. 

Shortcomings
Over time, ADL has received feedback and requests for other data capture. ADL recognizes that the current SCORM Data Model does not meet all needs, nor is it sufficient for some forms of content. 

Some of the common concerns regarding SCORM Data Model include:
  • Data is only available for a single attempt
  • No LMS reporting requirements are imposed by SCORM, making data tracking less relevant
  • The size/type of data supported by SCORM are not sufficient for all communities of practice
  • Binding limitations restrict where and how the Data Model can be effectively used
  • Missing ‘context’ information that would enable more effective evaluation recorded data
  • Insufficient guidance on defining and using ‘objective’ information – especially in regard to competency/performance tracking
  • SCORM 1.2 and SCORM 2004 have different data models – legacy content needs to be supported directly
ADL’s Approach to CMI Data Model Harmonization
ADL is committed to facilitating a conversation that captures the Data Model requirements of the SCORM user community. We have established a facilitated discussion forum and a broader IdeaScale site to capture bugs, issues, recommendations, and experiences people have had with the SCORM Data Model. While this activity is focused on the SCORM 2004 Data Model (as realized from the IEEE CMI Standard), we also want to hear any and all concerns regarding the SCORM 1.2 Data Model and legacy content support issues. 

You and your organization are invited to join the broader discussion between ADL, AICC, IEEE LTSC, and LETSI. A meeting to discuss harmonization of the CMI Data Model will be hosted at the ADL Co-Lab Hub in Alexandria, Virginia on September 7th – virtual participation will be available. For those of you unable to attend, a Twitter stream with the hash tag #cmiharmony will provide a real-time capture of the discussions. ADL will summarize the meeting and steps ahead via this site.

ADL is considering future updates to SCORM and believes that a harmonized approach to the CMI Data Model, one that enables future learning applications, will benefit the SCORM User Community. To foster multi-lateral collaboration with other interested groups (AICC, IEEE LTSC, LETSI and possibly others), ADL will capture SCORM User Community feedback and represent that community in the discussions. 

Principally, ADL is interested in four areas of feedback:
  • Bugs, Issues, Constraints related to using the current SCORM Data Model – Please reference the SCORM 2004 4th Edition Run-Time Environment (RTE) Book to provide specific examples and/or missing use cases. If you are encountering issues migrating data tracking from legacy SCORM 1.2 content to SCORM 2004, please let us know.
  • Recommendations and New Feature Requests – What is missing from the current Data Model, from both capture and reporting points of view?
  • Methods and Approaches to Extending the CMI Data Model – Do you have community of practice data tracking requirements?
  • Binding Issues and Use Cases – Are there types of content, modes of delivery, or delivery environments that you would like supported that cannot be addressed by the current dot-notation (SCORM) binding? Have you used the IEEE CMI Data Model XML Binding? If so, what experiences have you had?
ADL will actively participate and monitor multiple channels for feedback and exchange: