Aviation Industry Computer-Based Training Committee
An international industry association that developed interoperability guidelines for computer-based and web-based training systems.
Last updated November 4, 2026
AI crawler reads
No AI crawler has read this profile since Oct 28, 2026.
Overview
The Aviation Industry Computer-Based Training Committee, commonly known as AICC, was an international association of aviation and learning-technology professionals that operated from 1988 until its dissolution in December 2014. It was established by aircraft manufacturers, including Boeing, Airbus, and McDonnell Douglas, in response to airline concerns about the rising cost and incompatibility of multimedia computer-based training systems. At the time, training content was increasingly being distributed through different computer platforms, storage media, audio devices, and local networks, creating duplication and integration problems for airlines and training providers. AICC's central role was to create practical technical guidelines for the development, delivery, management, and evaluation of computer-based training (CBT), web-based training (WBT), and related learning technologies. Although its work originated in aviation, the committee generally aimed to make its specifications broadly applicable rather than narrowly aviation-specific. This allowed learning-technology suppliers to distribute development costs across multiple industries and helped AICC specifications gain adoption among both aviation and non-aviation users. The committee's early work addressed the computing platforms and media used to deliver training. In 1989, it issued recommendations that helped establish the personal computer as the principal delivery platform for CBT materials. In 1992, AICC published a digital-audio interoperability specification for DOS-based systems. That work enabled different CBT vendors to use a common audio interface and supported drivers for devices such as Elan and Sound Blaster audio cards. Elements of this older specification continued to be used by some legacy CBT applications. AICC's most influential contribution was its work on learning-management-system interoperability. In 1993, it produced CMI001, the AICC/CMI Guidelines for Interoperability, which is regarded as one of the earliest runtime interoperability specifications for learning-management systems and related computer-managed instruction systems. The original model supported CD-ROM and local-file or LAN-based delivery. A 1998 revision introduced HACP, an HTTP-based AICC/CMI Protocol, allowing a learning-management system to communicate with training content hosted on a web server. A 1999 revision added a JavaScript API runtime interface. The environment data model and API concepts later associated with SCORM were influenced by this earlier AICC work. AICC also developed PENS, or Package Exchange Notification Services, a mechanism intended to let authoring systems send content-package manifests to learning-management systems. Vendors demonstrated PENS interoperability at an AICC Plugfest held in connection with a September 2006 meeting. The committee coordinated its standards work with organizations and initiatives including IMS Global, the Open Knowledge Initiative, the Advanced Distributed Learning Initiative, IEEE/LTSC, LETSI, and ISO/SC36. In 2010, AICC began planning a successor to its existing computer-managed-instruction specification. The initiative became known as CMI-5. A SOAP-based draft was produced in 2012 but was not formally released in that form. Later in 2012, AICC announced that it would use the Experience API, also known as xAPI or Tin Can, as the basis for a substantial redesign of its CMI-5 work. The resulting effort was transferred to the Advanced Distributed Learning Initiative after AICC dissolved. AICC formally ended its operations in December 2014, citing declining participation. Its document archive and the CMI-5 effort were transferred to ADL. CMI-5 subsequently continued as an ADL-associated specification built on xAPI, intended to provide structured course assignment, launch, authentication, and reporting behavior in learning-management environments. The committee therefore survives primarily through its technical legacy: AICC communication protocols, historical CBT guidance, interoperability concepts, and the continued development of CMI-5 by successor organizations.
History
AICC emerged in 1988 when aircraft manufacturers, including Boeing, Airbus, and McDonnell Douglas, organized an industry association to address airline concerns about the cost and incompatibility of new multimedia training systems. The rapid spread of computer-based training had created a fragmented technology environment: training materials could depend on particular personal-computer configurations, storage media, audio hardware, and delivery networks. A common set of recommendations was intended to reduce the need for airlines to purchase or maintain incompatible systems. In 1989, AICC issued recommendations covering computer platforms and training media. These recommendations helped establish the PC platform as the principal delivery environment for CBT materials. The committee subsequently addressed audio interoperability. Its 1992 specification for DOS-based digital audio allowed multiple CBT vendors to work with a common audio-card interface, with drivers produced for hardware including Elan and Sound Blaster devices. Some legacy CBT systems continued to use elements of this work long after the technology had become obsolete in mainstream computing. The committee's most consequential technical work began in 1993 with CMI001, the AICC/CMI Guidelines for Interoperability. The specification provided a way for computer-managed instruction content to exchange information with a learning-management system or comparable host. Its first design focused on CD-ROM and local-file or LAN-based delivery. In January 1998, AICC revised the specification to include HACP, an HTTP-based protocol that allowed content and the calling learning system to communicate across web-server boundaries. In September 1999, a further revision added a JavaScript API runtime interface. These specifications provided an early foundation for tracking learner progress, completion, assessment information, and other runtime data. Concepts from the AICC data model and API influenced later learning standards, including SCORM. AICC specifications were deliberately designed to be general-purpose. While the aviation sector remained an important constituency, broader applicability allowed learning-technology vendors to serve other industries and spread their development costs. The HACP protocol was particularly notable for its ability to support communication between systems that were not hosted on the same server. It remained in use because of its comparatively clear and robust behavior, including in situations where content was hosted remotely from the learning-management system. The committee also worked on PENS, or Package Exchange Notification Services. PENS was intended to simplify the movement of content-package information from authoring tools to learning-management systems. AICC's September 2006 meeting included a Plugfest at which vendors demonstrated interoperability. During this period, the organization coordinated with other standards bodies and learning-technology initiatives, including IMS Global, OKI, ADL, IEEE/LTSC, LETSI, and ISO/SC36. By 2010, AICC was seeking a modern successor to its CMI work. The initiative was later called CMI-5. A SOAP-based version was drafted in May 2012 but was not formally released. In October 2012, AICC announced a major change in direction: the CMI-5 effort would use xAPI, also known as the Experience API or Tin Can, as its underlying framework. This represented a move away from the committee's earlier protocol model toward a modern learning-record architecture while retaining the need for structured LMS course launch and reporting behavior. AICC dissolved in December 2014 after reporting declining participation. It transferred the CMI-5 initiative and its document archive to ADL. CMI-5 continued under ADL-related stewardship as a modern specification built on xAPI. Later standardization activity sought to bring cmi5 into the IEEE Learning Technology Standards Committee process. AICC's organizational life consequently ended, but its specifications and design principles continued to influence learning-management interoperability, aviation training systems, and enterprise learning infrastructure.
- 2014
AICC dissolves and transfers its work
[1]The committee ends operations because of declining participation and transfers its archive and CMI-5 effort to ADL.
- 2012
CMI-5 direction shifts to xAPI
[1]AICC announces that the CMI-5 redesign will be based on the Experience API.
- 2010
Successor CMI work begins
[1]AICC announces work on replacing its existing CMI specification, eventually naming the effort CMI-5.
- 2006
PENS interoperability demonstration
[1]Vendors demonstrate interoperability for the Package Exchange Notification Services initiative at an AICC Plugfest.
- 1999
JavaScript runtime interface added
[1]AICC updates CMI001 to include a JavaScript API runtime interface.
- 1998
HACP is added
[1]The CMI001 specification is updated with an HTTP-based AICC/CMI Protocol for web-hosted content and learning systems.
- 1993
CMI001 interoperability specification
[1]AICC produces its first major runtime interoperability specification for computer-managed instruction and learning-management systems.
- 1992
DOS digital-audio interoperability specification
[1]AICC publishes a specification that allows different CBT vendors to use compatible audio-card interfaces on DOS systems.
- 1989
PC platform recommendations published
[1]AICC issues recommendations for CBT computing platforms and training media, identifying the personal computer as the primary delivery platform.
- 1988
AICC is formed
[1]Aircraft manufacturers, including Boeing, Airbus, and McDonnell Douglas, establish the committee to address airline concerns about incompatible and costly computer-based training systems.
Products and positioning
A practical, cross-industry standards association focused on interoperability, portability, and lower integration costs for aviation training and learning-management systems.
Learning-management interoperability specification · 1993
CMI001 / AICC-CMI Guidelines for Interoperability
AICC's principal computer-managed-instruction specification defined how training content and learning-management or computer-managed-instruction systems could exchange runtime information. It originated in a CD-ROM, local-file, and LAN-oriented environment and was later extended for web delivery. Its data model and runtime concepts influenced subsequent learning-technology specifications, including SCORM.
HTTP-based learning-content communication protocol · 1998
HACP
The HTTP-based AICC/CMI Protocol was introduced as an extension to CMI001. It enabled a learning-management system to communicate with training content hosted on a web server, including configurations in which the content and calling system were not located on the same server. HACP became one of the most durable parts of the AICC technical legacy.
Content-package exchange service
PENS
Package Exchange Notification Services was designed to help content-authoring tools send package manifests and related notifications to learning-management systems. The initiative addressed the operational handoff between content creation and LMS deployment and was demonstrated through vendor interoperability testing.
xAPI-based learning-management specification · 2010
CMI-5
CMI-5 began as AICC's proposed successor to its CMI specification. After an earlier SOAP-based draft, the project was redesigned around xAPI to combine modern learning-record capabilities with structured LMS course assignment, launch, and reporting behavior. AICC transferred the work to ADL when the committee dissolved.
Brand decisions
2014
Dissolve the association and transfer its technical assetsOtherBackground
AICC reported declining participation and no longer maintained a sustainable basis for continuing as an independent association.
Action taken
AICC formally dissolved and transferred its CMI-5 work and document archive to the Advanced Distributed Learning Initiative.
Aftermath
The organization's specifications remained available as historical and legacy interoperability resources, while cmi5 development continued through successor organizations.
2012
Redesign CMI-5 around xAPIStrategyBackground
AICC was developing a successor to its existing CMI specification after an unreleased SOAP-based draft. The learning-technology environment was moving toward xAPI and more flexible learning-record architectures.
Action taken
The committee announced that the CMI-5 effort would adopt the Experience API, also known as xAPI or Tin Can, as its underlying technology.
Aftermath
The redesign continued after AICC's dissolution under ADL-related stewardship and became the basis for ongoing cmi5 development.
Recent events
- Unconfirmed
AICC completes Pre-A funding round[2]
Reported:
Automotive intelligence developer AICC raised hundreds of millions of RMB in a Pre-A funding round led by Avic Capital and CICV, with funds intended for product R&D and collaborative mass production with automakers.
Sources2 sources
Cite this profile: Cite the canonical profile. /brand-wiki/aviation-industry-computer-based-training-committee · Editorial policy · How profiles are compiled