|The cost and difficulty of developing and maintaining large, complex application systems is daunting and perceived to be unpractical.
|Uncertainty of support and lack of expertise
|we feel that it is critical to have a vendor supported system that would keep their software current with technology and funds a significant amount toward R&D. We also want a strong support group and maintenace contract.
|We have a very small I.T. staff
|We are still in the investigation stage.
|We are focussing on more productive engagement with our major vendors, and adopting applications across our university sytem for economies of scale.
|Due to our small staff size and FTE limitations, it is easier for us to get dollars to pay a vendor for a system and maintenance than to hire staff to work on one ourselves.
|Current immature state of open source. No funding to switch from current path.
|not (yet) convinced that it would be cheaper
|We did in the past and found it too expensive to maintain. We are considering Sakai
|Core applications not available in open source
|We haven't reached critical mass yet to meet the support obligations of Open Source. That said, we think we are close on course management and ERP financials.
|We are a small college and do not have the development staff to support open source.
|Supportability, interoperability, lack of tools
|Standardization and support
|The staff has very limited knowledge regarding open source.
|We don't see the quality, dependability or accountability required before we would consider them.
|Department standards and application systems are based on Microsoft products.
|lack of long term viability.
lack of contractual commitments.
lack of long term roadmap.