cmi5
cmi5 is a modern e-learning standard that combines the structure of SCORM with the rich tracking of xAPI.
cmi5 is a specification that brings together the launch, session and reporting structure familiar from SCORM with the flexible, detailed data capture of xAPI. It defines how an LMS launches content and how that content reports results back via an LRS.
cmi5 lets organizations track structured course completion and deeper experience data in one standard, including content delivered on mobile or offline.
How cmi5 works in Violetinfo.ai
Violetinfo.ai supports modern standards including SCORM, xAPI and cmi5, so content authored or imported tracks reliably across desk, mobile and offline learning.
Why cmi5 was created
xAPI gave organizations flexible tracking, but it deliberately left out rules for how an LMS should launch a course, pass learner details to it and decide when it is complete. Without those rules, each xAPI course and LMS could behave differently, which recreated the portability problem SCORM had solved.
cmi5 was started by the AICC and later carried forward with the ADL Initiative, with its first edition published in 2016. It is formally an xAPI profile: it uses ordinary xAPI statements but adds a defined set of launch, session and completion rules that both the LMS and the content must follow.
Key parts of a cmi5 course
A cmi5 course is described by a course structure file that lists its assignable units (AUs), the individual pieces of content the LMS can launch. For each AU, the course defines a moveOn rule that tells the LMS what counts as finished, for example completed, passed, completed and passed, or completed or passed.
cmi5 also defines a small vocabulary of verbs with specific meanings, including launched, initialized, completed, passed, failed, abandoned, waived, terminated and satisfied. Because every compliant system interprets these the same way, completion reporting is predictable while the content remains free to send additional, richer xAPI statements.
cmi5 compared with SCORM and plain xAPI
Compared with SCORM, cmi5 does not rely on a browser JavaScript API, so content can be hosted on a different domain from the LMS and can run in mobile apps or other environments. Compared with plain xAPI, it gives the LMS clear authority over launch, enrolment and completion. Violetinfo.ai supports SCORM, xAPI and cmi5, so content tracks across desk, mobile and offline learning.
Adopting cmi5 in practice
Moving to cmi5 does not require replacing existing content overnight. Most organizations keep their SCORM library running and publish new courses in cmi5 as their authoring tools and LMS support it. Before committing, confirm that both the authoring tool and the LMS support cmi5 launch and moveOn rules, and test a pilot course end to end, including completion, scoring and resuming an interrupted session.
It is also worth deciding early which extra xAPI statements, beyond the required cmi5 verbs, the content should send. Planning this alongside reporting needs keeps the Learning Record Store useful rather than cluttered, and makes it easier to compare cmi5 course data with other xAPI activity from mobile apps, simulations or on-the-job checklists.
Frequently asked questions
Is cmi5 the same as xAPI?
No, cmi5 is a profile built on top of xAPI that adds rules for launching content and determining completion. Every cmi5 course reports using xAPI statements, but not every xAPI implementation follows cmi5.
When should an organization choose cmi5 over SCORM?
Choose cmi5 when you need LMS-managed courses that also capture richer data, run on mobile or are hosted outside the LMS domain. For simple browser courses in an LMS that does not yet support cmi5, SCORM may still be the more practical option.
Does cmi5 need a Learning Record Store?
Yes, cmi5 content sends its statements to an LRS, which is usually provided by or connected to the LMS. The LMS gives the content the LRS address and a session credential at launch.