Non-SCORM/TinCan API Compliant CMS-Future problems?

Hi Wendy,

The SCORM compliance aspect of the system doesn't hurt or benefit your operation in anyway. It depends on what your needs are. I'll explain, but before I do that, let's explore what SCORM is use for. SCORM is simply an elearning specification that provide interoperability between different systems for elearning content. For example, I can take a SCORM compliant course produced by Articulate and load it into SumTotal LMS or Saba LMS. In addition, the specification provides certain user progress tracking methodologies that is shared by many LMSs. 

While you can use your CMS to host your elerning content through HTML or Flash publishing, you may not have the user progress/tracking capability unless you custom built it or use some other software to provide that function. That may or may not be a roadblock depending on your company's needs.  In addition, most elearning development software provide SCORM compliant publishing as a default choice. This simplifies the process for newbies who may not be familiar with nuances of the LMS administration or content management. 

The flip side of this is that because you already have a CMS and use it for learning content, you won't need to implement a LMS to get your content out there. However, you won't get the many benefits that LMS has to offer your end user and the administrator. Then again, your user won't have to learn a new system to access content. 

Without knowing the full scope your company's needs. I would say if the budget and resources are there, go for the LMS. If not, you can rig the CMS to provide some of the same functionality but it may be harder to scale the system later on.