Before SCORM and long before cmi5, there was AICC, the Aviation Industry CBT Committee.
Formed in the late 1980s, it wasn’t a tech company or a software vendor but a group of aviation professionals facing a familiar modern problem:
How can we make digital training content reusable, trackable, and compatible across different systems?
Back then, computer-based training (CBT) was still new. Airlines were investing heavily in simulators and digital lessons, but each vendor had its own proprietary player and data format. A course created for one system simply wouldn’t run on another. Tracking learner progress across vendors was nearly impossible.
✈️ The Problem That Started It All
The aviation industry thrives on precision and standardization, from cockpit interfaces to safety procedures. When digital training arrived, the same principles had to apply.
The AICC’s mission was simple but ambitious: define a common language that any course and any learning management system (LMS) could use to communicate, regardless of who built them.
🧩 The AICC Approach
The committee didn’t build software; they built specifications.
Their first achievement was a set of plain-text definition files (
.crs
,
.au
,
.des
, and
.cst
) that described everything from course structure to launch commands. Later came an elegant protocol called HACP (HTTP AICC Communication Protocol), which allowed a course to send learner data to an LMS using simple HTTP POST requests.
No browsers.
No JavaScript APIs.
Just files and URLs: straightforward, transparent, and dependable.
For developers, this simplicity was empowering. You could open any file in a text editor and understand exactly how the course was wired to the LMS. Debugging was a matter of reading, not reverse-engineering.
🧠 Why It Mattered
AICC’s specifications solved one of the earliest interoperability problems in e-learning and set a precedent that still guides us today.
Its principles of reusability, portability, and vendor-neutrality became the DNA of every standard that followed: SCORM, xAPI, and cmi5.
Even decades later, modern LMS platforms still recognize AICC packages. That longevity says a lot; not about technology, but about design philosophy.
💡 Developer Reflection
As developers, we constantly build APIs, schemas, and tools that connect systems. But how often do we design them to outlive our tech stack?
AICC did.
It favored human readability over complexity and long-term clarity over short-term convenience.
There’s something poetic about a standard born in aviation, an industry where interoperability and safety can’t fail, teaching the software world how to create reliable, portable learning systems.
🔭 What’s Next
Next week, we’ll unpack the anatomy of an AICC course, exploring how early developers used simple text files to define lessons long before XML or JSON.
From there, the series will trace how AICC handled communication, data tracking, and eventually evolved into SCORM and cmi5: the foundations of modern learning standards.
🔢 1 of 8 | AICC – The Origins of E-Learning Standards
