- Get Started
- Write Code
You’re going to issue an RFP for a learning technologies purchase and need it to have the kind of Tin-Can-enabled features you’ve read about on this website. Just add “Must be Tin Can conformant” to the RFP and the job’s done, right? Wrong. It’s a little more complex than that.
Tin Can is a specification that defines how data about learning and performance experiences and achievements can be communicated between systems. The applications of that technology are very broad, and Tin Can is being used in many different ways. We’ve outlined some of these for product vendors here.
The problem is that if you simply list “Must be Tin Can conformant”, your vendor won’t necessarily know what you want them to do with Tin Can. Should the product send Tin Can statements to an LRS or should it be an LRS itself? Should it launch Tin Can e-learning content or display Tin Can data in reports? You need to be specific about how Tin Can will be used.
Conformance should be a given however the application is using Tin Can. When you buy a computer, you might ask how many usb ports it has, but you don’t ask for a usb conformant computer, you expect it. It’s the same with Tin Can: ask what the product is doing with Tin Can and expect that whatever it is doing is conformant; get annoyed if it’s not!
We’re not going to give you a complete example RFP to copy and paste because your requirements relating to Tin Can should be driven by your requirements for the solution as a whole. This will be specific to your organization and project.
That said, below are some examples of what good requirements for an LMS RFP might look like. Not all of these requirements will necessarily be required in your organization, so please use these examples carefully. RFP requirements for other systems should include a similar level of detail.