Make - Buy Decisions
While open source provides better value and control it does not cover all the computing needs of the institution. Software developed and supported by companies will continue to be a part of Higher Education Information Services. The difference lies in the requirements. Institutions will insist that purchased application components operate within the constraints of the new model or framework.
Some examples:
| Component |
Legacy Product |
Open Source Replacement
|
|
Operating System
|
Solaris
|
Linux
|
|
Web Server
|
Netscape
|
Apache
|
|
Web Application Server
|
|
Tomcat
|
|
Portal
|
none
|
uPortal
|
|
Database
|
Oracle
|
Postgres
|
|
Search Engine
|
Verity
|
Lucene
|
|
Mail List Server
|
Lyris
|
Mailman
|
|
Workflow
|
none
|
OneStart, Twister
|
|
Collaborative Workspace
|
|
Mimerdesk, Jive Forums, Roller
|
|
Single Sign on
|
|
Liberty
|
|
Financials
|
SCT Banner
|
Kuali
|
|
Learning
|
WebCT
|
Sakai
|
Some decisional differences:
| Institutional need |
IT response - current |
IT response - future |
|
Student recruitment
|
Buy
|
Use Portal, Collaboration tools, Messaging, Workflow, Documents. Create specialized portlet(s) or use what is available from the community
|
|
Alumni system
|
Buy
|
Use Portal, Collaboration tools, Messaging, Workflow, Documents. Create specialized portlet(s)
|
|
Student System
|
Buy
|
Buy
|
|
Learning System
|
Buy
|
Sakai
|
|
Travel System
|
Develop in-house
|
Community project
|
|
Housing System
|
Develop in-house
|
Develop in-house
|
|
Library System
|
Buy
|
Buy based on requirement standards
|
|
|
|
|
|
|
