The story of AICC did not end with SCORM. It evolved.
In its later years, the same committee that created AICC began working on a new specification called cmi5.
Their goal was clear and ambitious: to combine the structure and reliability of SCORM with the freedom and flexibility of xAPI.
🧩 A New Generation of Learning Standards
As digital learning matured, the limits of SCORM became more obvious.
Courses were confined to the LMS browser frame, constant connectivity was required for tracking, and anything happening outside that window was invisible to the system.
Learning, however, was happening everywhere. It took place in mobile apps, in simulations, in virtual reality, and even in real-world environments.
The AICC recognized this shift and wanted a model that kept the clarity of traditional standards while embracing modern learning experiences.
That idea grew into cmi5, short for Computer Managed Instruction version 5.
🔗 The Bridge Between SCORM and xAPI
Where SCORM defined how courses communicate with the LMS inside a browser, cmi5 defined how learning content can run in many environments while still being tracked consistently.
It uses xAPI as its communication method, sending learning records to an LRS (Learning Record Store) instead of relying on an LMS runtime API.
In practice, cmi5 provides rules for the following:
How a course is launched
How learner sessions are identified
How xAPI statements should be structured
How completion, scoring, and progress are recorded
This makes it possible to run a learning experience in a browser, a native application, a simulation, or even offline, while still capturing accurate analytics once the system reconnects.
Where SCORM was tightly attached to the LMS environment, cmi5 opens the door for LMSs, LRSs, and independent systems to work together through a shared contract.
📜 The AICC’s Final Chapter
By 2014, after more than two decades of shaping e-learning standards, the AICC formally disbanded.
Before closing, they ensured that their work would continue.
The cmi5 specification and all related materials were transferred to ADL (Advanced Distributed Learning Initiative), the same organization responsible for SCORM.
The handover symbolized the continuation of AICC’s influence into the next generation of learning standards.
🌱 The Legacy That Endures
AICC’s journey from early CBT formats to modern web-based models and finally to cmi5 is more than a technological timeline.
It is a story about resilience and clarity in system design.
It shows what happens when a standard is built with transparency, portability, and long-term thinking at its core.
The ideas AICC introduced are still alive today.
Whenever a system talks about tracking learning beyond the LMS or about separating content from the platform, it is echoing principles AICC defined decades ago.
💡 Developer Reflection
AICC’s evolution demonstrates the value of long-term design thinking.
It proves that the real legacy of a system is not whether it stays the same forever but whether it can adapt without losing its purpose.
As developers, we often focus on solving what is directly in front of us.
Yet the work that lasts is often the work that can grow and change.
Ask yourself:
What parts of your work could outlast you by evolving with intention rather than remaining fixed?
🔭 What’s Next
In the final post of this series, we will build a minimal AICC prototype.
This small hands-on example will show how these legacy ideas can still be implemented today and why they remain relevant for modern developers
🔢 7 of 8 | AICC – The Origins of E-Learning Standards
