understanding SCORM

SCORM stands for Sharable Content Object Reference Model. 

In order for one person to have a meaningful conversation with another person they need to speak the same language and follow the same set of rules for interaction. Let's call this sharing a common interface (i.e. the language that they are speaking). Once they've had a conversation using that common interface (language) then they are able to comprehend each other and report back on that conversation to others.

Think of SCORM in a similar way. It is a common interface that allows learning content to interact with a Learning Management System in a meaningful and standardised manner. SCORM dictates how learning content and Learning Management Systems (LMS) communicate with each other. 

Most vendors will refer to SCORM 1.1, SCORM 1.2 or SCORM 2004 compliance. These are just different versions of the standard. Nowadays its most common to see systems and content listed as SCORM 1.2 and 2004 compliant or SCORM1.2/2004 for short.

do you need SCORM?

You may not actually need SCORM compliance for all e-learning projects. However, its worth investigating before you begin because SCORM compliance provides you with interoperability across multiple vendors. SCORM is like an insurance policy for any investment made in e-learning. 

If you invest in creating online training you may want to deliver it on a number of different LMS platforms, either now or in the future. You ought to ensure it can be used to deliver and track many different online training programmes from different vendors.

If an LMS is SCORM compliant, it can work with any other training content that is also SCORM compliant. Additionally, any online training content that is SCORM compliant can be used in any SCORM compliant LMS.

Understanding the Experience API

The Experience API is known as xAPI for short and was formerly known as Tin Can. Think of it as the next generation of SCORM. Whereas SCORM really only takes care of interactions between the learning content and the LMS, xAPI enables other real-world experiences and interactions to be recorded.

For example, this real-world data might be that someone has:

• Read a book
• Attended a meeting or a lecture
• Completed a training course
• Gained a certificate
• Won a medal 
• Taken part in collaborative group sessions
• Written an article

The repository for all of this information is called a Learning Record Store and if a device, system or process supports the xAPI then it can record these experiences to the LRS.

Summary of SCORM and xAPI

In the world of SCORM the ‘learning’ that is tracked relates mainly to activity undertaken on e-learning programmes within an LMS environment.

In contrast, xAPI isn’t limited to the LMS environment. It supports a more ‘real life’ approach to learning by capturing learning activity from outside of the traditional LMS environment. This provides a better representation of ‘real life’ learning through the capture of on and off line experiences.

In the world of xAPI and the LRS, any device, system or process that supports xAPI can send a statement to an LRS regarding those broader learning activities.

Understanding an lRS

LRS stands for Learning Record Store. It is a repository or database for statements that have been created and sent using the Experience API. The LRS is principally a store for learning records.

The LRS can be accessed and interrogated by an LMS, by another LRS, or by other systems that support xAPI. The LRS can operate as a standalone records system or it can operate inside the In2itive LMS.

what this means for your business

To get to the bottom of this world of e-learning standards and technologies we encourage you to have a conversation with us. The choices you make related to learning technologies can positively or negatively impact your business and we can help you understand what’s important and what’s not so important. We'll  set you on the right path to accomplishing your e-learning plans.