Summary

SCORM and xAPI are the most popular technical standards for eLearning software products. Safety Made Simple supports both standards. This article provides a brief introduction to each specification.

Using these standards, content is easy to make, easy to migrate between different learning systems, and let you track learner progress.

SCORM explained

Safety Made Simple supports SCORM v 1.2 and SCORM 2004 (3rd and 4th editions). The supported features for SCORM 2004 include:

• most features previously supported in SCORM 1.2
• single Shareable Content Object (SCOs)
• single objectives
• learner comments

Note: The Exams/Interactions transcript report is not currently available for SCORM 2004.

When you create a course with a SCORM-compliant authoring tool, the output is a ZIP folder, which you upload to Safety Made Simple. The SCORM course tells Safety Made Simple which data to receive. You publish the course, and your learner launches it in a browser.

Safety Made Simple collects data to track and report results of your learners' performance. For the SCORM versions that Safety Made Simple supports, the data includes:

• lesson_location (where learner left off, so they can pick up again without restarting)
• suspend_data (bookmark with the specific information e.g. paragraph)
• lesson_status (pass, fail, complete, incomplete)
• session_time and total_time
• score_raw (score learner got)
• mastery_score (passing score - learners must score equal to or higher than this score)
• interactions (individual answers to exam questions, time spent etc.)

These fields cover the learner's status, the suspend data and the mastery score.

Safety Made Simple uses 4 SCORM statuses for modules, to indicate the status of the learner in a particular course:

• Incomplete: learner has not finished the module
• Completed: learner has read or reviewed all the content in the module
  
  • Passed: subset of Completed, where learner completed the content and passed an exam
  • Failed: subset of Completed, where the learner completed the content and failed the exam

Note: Completed and Passed are two different and distinct statuses in SCORM. Their meanings are similar for humans, but different for SCORM and for Safety Made Simple. Both Passed and Failed are sub-statuses of Completed. If you can keep these status meanings straight, SCORM features make more sense.

Tracking scores in SCORM modules

Not every SCORM module is designed to track scores: users can get a Completed status alone.

Modules which use exams, sometimes referred to as quizzes, almost always have scores.

Check with your SCORM course developer to ensure your courses have score tracking capabilities.

Mastery score in SCORM

For graded content like an exam or assignment, mastery score is the "passing" score. Learners must receive a score equal to or higher than this score to pass the module.

When you upload a SCORM module to Safety Made Simple, you import a mastery score with the module. Safety Made Simple needs a mastery score to track quiz or exam results.

If your SCORM doesn't include a mastery score for graded content, you can set a mastery score in the application.

xAPI (Tin Can) explained

Experience API, or xAPI, began life as a research project called "Project Tin Can", and the nickname stuck. The terms xAPI and Tin Can are used interchangeably and refer to the same standard.

The major difference between xAPI and SCORM is the type of learning content each can track.

SCORM records online learning only: documents, videos, webinars, ILTs. xAPI can track almost any activity including: reading a webpage, attending an event, borrowing a library book, playing a game, blended learning, and team-based learning.

xAPI compliant systems send records of learning in the form of statements. Each statement is composed of three elements, a structure known as xAPI syntax:

• Noun (Actor - or the ‘who’ part of an action)
• Verb (The action)
• Object (The ‘what’ part of an action)

For example:

• "I - did - this"
• "Phily - completed - health and safety training"
• "Kim - read - Safety Made Simple’s help guide"

xAPI uses these statements to track data about learner actions and reports them back to a learning management system, Learning Record Store (LRS), or any application that understands the xAPI language.

Your authoring tool exports your Tin Can course as a ZIP file, which you upload to Safety Made Simple. This file contains all the components of your course like images, video, or HTML. It also contains a tincan.xml file, at the root of the ZIP. 

xAPI vs SCORM

SCORM and xAPI are different protocols, which provide different ways to record and track data about your learners' progress. 

The quality of your learning content still relies on good authoring tools, and good instructional design. Safety Made Simple runs on any supported browser, and learners can use Safety Made Simple on phones, tablets and desktops. 

Tip: for best results, test your course content on different devices. Make sure your course layouts and graphics are responsive, so they scale smoothly and clearly at any viewing size.

As best practice Safety Made Simple recommends: make an "upload" copy of each SCORM or Tin Can zipped file, to use in Safety Made Simple. Keep your original files separate, in case you need to revise or edit them.

After you upload your zipped file, Safety Made Simple combines your file with its own code, to work in the user interface. You can't download the SCORM or Tin Can file again to edit it or use in another LMS.