cmi5 is a specification describing how an LMS and learning content communicate, using xAPI as the underlying data language. It combines the structure of SCORM, starting, completing, passing or failing, with the richer data capability and the loose coupling of xAPI.
SCORM dates from a time when learning content ran in the browser and had to live inside the LMS. cmi5 lets content run outside the platform, which is what VR applications, mobile apps and simulations that do not fit in a browser window need.
For anyone deploying VR or a field app, this is the practical route. With SCORM you end up at completed or not completed; with cmi5, what happened during the session comes back and the LMS administration stays intact. The limitation is the market: not every platform supports it, and that is a question to ask before purchase, not after.
Does cmi5 replace SCORM?
What is the difference between cmi5 and plain xAPI?
Does our LMS support cmi5?
Want to apply cmi5 in your own training programme?
We are happy to think along about the approach that fits your installation, your audience and your timeline.
Milan
Business development, STARK Learning