Figuratively speaking, SCORM is a “language” used by a learning course to “talk” to an LMS and submit a learner’s results. It also describes the structure of a course. What data is being transmitted and how does a learning system decide if a course is passed or failed? Let’s unveil the communication mechanism. iSpring SCORM course structure In SCORM terminology, a course item is called an SCO (Sharable Content Object). An iSpring course is always a single SCO that is stored in a .zip content package. As shown in the picture above, there are several organizational levels in SCORM: Asset. The smallest particle of a course: an HTML page, image, mp3 audio, Flash quiz as an .swf file, etc. Note: An iSpring tool may produce two types of resources: Flash and HTML5. It doesn’t matter to the LMS what type of content is placed in a .zip package, because the SCORM API is the same. Course reporting to an LMS An iSpring SCO uses the SCORM API Runtime environment to communicate with an LMS. After the course is completed by a learner, an LMS shows the result. Also, some Learning Systems provide detailed information that shows time spent on each slide, answers to questions, etc.