Build, Buy, Borrow
Build, Buy, Borrow Or
Blend 1
Presenters
Rebecca Porter
Executive Director of Enrollment Services Associate Vice Chancellor for Student Services Indiana University Purdue University-Indianapolis
Laurie Sullivan
Student Information Systems Director Student Enrollment Services Indiana University
2
Introduction Build your own Enterprise Resource Planning system (ERP) or Student Information System (SIS) Buy a complete system or module from a vendor Borrow components developed as open source or community source system Blend components from each of the preceding categories
3
Audience Poll Institution type?--2 year/4 year SIS type?—homegrown/vended Experience?—IT/functional user Making decision in next year?
4
Presentation Focus Issues
involved in making a decision
Disclaimer Speaking
from our own experiences
5
Historical Context
Æ mid 1990s
Institutions built independent applications
Mid 1990s
Upcoming Y2K problems served as driver Enterprise Resource Planning Systems Promote standardization Eliminates need for external interfaces between systems Lower maintenance demands Greater reporting capacity Based on ‘best practices’
6
Historical Context
“Enterprise resource planning (ERP) systems are the soap operas of the IT industry. They evoke the entire spectrum of human emotion, from longing and love to greed and betrayal. Like soap opera plot lines, ERP issues are constantly being recycled. …..Every senior IT manager seems to have an ERP war story. Veterans display their membership in this club like a red badge of courage, recounting tales of heroics and struggles.”
Thornton A. May Executive Education Programs, Haas School of Business, University of California http://www.bitpipe.com/detail/RES/1157348871_253.html
7
Decisions in the Current Environment
8
BUILD Resource, time, expertise INTENSIVE Build strategies focus on
Back end core business processes Components that address market differentiation Federal and STATE regulatory changes
9
BUILD
Benefits
You design the system that fits your needs exactly No vendor maintenance and licensing costs You control the changes to the system
Cautions
The challenges of building a full service SIS are overwhelming
10
BUY
Purchase the integrated components of the SIS
Vendor ERP solutions
Array of options depends on size and complexity of institution
Mix and Match options Implementation focus is on configuring and setting up the control tables (the tables with the business rules)
11
BUY
Considerations
Can you implement ‘vanilla’? Can you give up your love affair with the legacy system? Can you dedicate the required IT and functional resources needed during the implementation?
12
BUY
Considerations
Post Implementation (really Continual Implementation) Ongoing maintenance fees System maintenance workload
Routine—updates, patches, fixes Minor system changes Major upgrades Involves both IT and functional staff No longer have discretion on whether or not to invest in the changes and are driven by vendors’ timelines 13
BORROW
Collaborative efforts to build open source or community source product
Related to underlying concept of Linux operating system, Foxfire Web browser, and Wikipedia, but more typically involves a consortial effort
14
BORROW
Sakai Collaboration and Learning Environment for Education
http://sakaiproject.org/ Used to support teaching and learning, ad hoc group collaboration, support for portfolios and research collaboration Founded 2003 by Michigan, Indiana, MIT and Stanford in partnership with uPortal and OKI Original funding — $4.4M in shared staff (27 FTEs); $2.4M Mellon, $300K Hewlett grants; additional investment via community partners. 15
BORROW
Kuali Foundation
http://www.kuali.org/ Non-profit organization responsible for sustaining and evolving a comprehensive suite of administrative software that meets the needs of all Carnegie Class institutions Members are colleges, universities, commercial firms, and interested organizations that share a common vision of open, modular, and distributed systems for their software requirements Goal of Kuali is to bring the proven functionality of legacy applications to the ease 16 and universality of online services.
BORROW
Kuali Foundation
Financial Community Endowment Community Research Community Workflow Community Nervous System Community
Student Services System
Under development Release 1 proposed for 1st quarter 2009 17
BORROW
Keys to development of community source systems
Ability to identify partners Utilization of one university’s system as a starting point for development Extreme collaboration Upfront funding (with uncertain delivery timelines)
Systems will be built to meet the needs of the development partners 18
The FUTURE
19
BLEND Buy ‘best of breed’ for core business practices Build aspects that address market differentiation OR Buy and customize to meet your needs Borrow components from open source initiatives that meet your needs
20
BLEND
Indiana University BLEND strategy BUY PeopleSoft
for Student Administration 3rd Party vendor products for smaller applications Ad Astra for room scheduling PeopleSoft Reporting Data Service infiNET (eCommerce and SIS) ApplyYourself 21
BLEND
Indiana University BLEND strategy BUILD In-house
development for Electronic Documents IU modifications and customizations Interfaces among university information systems, batch processing, reporting Reporting environment for reports and data extraction
22
BLEND
Indiana University BLEND strategy Borrow Modifications
from other universities Sakai OnCourse course support product Watching for Kuali student developments
23
BLEND
What are the Drivers?
24
What is best for your organization?
25
Your Questions and Comments
26
Resources Building a Student Information System: Strategies for Success and Implications for Campus Policy Makers. Hosler D, ed. New Directions for Higher Education, no. 136, Winter 2006 Student Information Systems: A Guide to Implementation Success. Sharon F. Cramer, AACRAO 2005 Open Source Student Systems. Wheeler B. http://student.osnext.org/ 2006
27
Thank You
28
Blend 1
Presenters
Rebecca Porter
Executive Director of Enrollment Services Associate Vice Chancellor for Student Services Indiana University Purdue University-Indianapolis
Laurie Sullivan
Student Information Systems Director Student Enrollment Services Indiana University
2
Introduction Build your own Enterprise Resource Planning system (ERP) or Student Information System (SIS) Buy a complete system or module from a vendor Borrow components developed as open source or community source system Blend components from each of the preceding categories
3
Audience Poll Institution type?--2 year/4 year SIS type?—homegrown/vended Experience?—IT/functional user Making decision in next year?
4
Presentation Focus Issues
involved in making a decision
Disclaimer Speaking
from our own experiences
5
Historical Context
Æ mid 1990s
Institutions built independent applications
Mid 1990s
Upcoming Y2K problems served as driver Enterprise Resource Planning Systems Promote standardization Eliminates need for external interfaces between systems Lower maintenance demands Greater reporting capacity Based on ‘best practices’
6
Historical Context
“Enterprise resource planning (ERP) systems are the soap operas of the IT industry. They evoke the entire spectrum of human emotion, from longing and love to greed and betrayal. Like soap opera plot lines, ERP issues are constantly being recycled. …..Every senior IT manager seems to have an ERP war story. Veterans display their membership in this club like a red badge of courage, recounting tales of heroics and struggles.”
Thornton A. May Executive Education Programs, Haas School of Business, University of California http://www.bitpipe.com/detail/RES/1157348871_253.html
7
Decisions in the Current Environment
8
BUILD Resource, time, expertise INTENSIVE Build strategies focus on
Back end core business processes Components that address market differentiation Federal and STATE regulatory changes
9
BUILD
Benefits
You design the system that fits your needs exactly No vendor maintenance and licensing costs You control the changes to the system
Cautions
The challenges of building a full service SIS are overwhelming
10
BUY
Purchase the integrated components of the SIS
Vendor ERP solutions
Array of options depends on size and complexity of institution
Mix and Match options Implementation focus is on configuring and setting up the control tables (the tables with the business rules)
11
BUY
Considerations
Can you implement ‘vanilla’? Can you give up your love affair with the legacy system? Can you dedicate the required IT and functional resources needed during the implementation?
12
BUY
Considerations
Post Implementation (really Continual Implementation) Ongoing maintenance fees System maintenance workload
Routine—updates, patches, fixes Minor system changes Major upgrades Involves both IT and functional staff No longer have discretion on whether or not to invest in the changes and are driven by vendors’ timelines 13
BORROW
Collaborative efforts to build open source or community source product
Related to underlying concept of Linux operating system, Foxfire Web browser, and Wikipedia, but more typically involves a consortial effort
14
BORROW
Sakai Collaboration and Learning Environment for Education
http://sakaiproject.org/ Used to support teaching and learning, ad hoc group collaboration, support for portfolios and research collaboration Founded 2003 by Michigan, Indiana, MIT and Stanford in partnership with uPortal and OKI Original funding — $4.4M in shared staff (27 FTEs); $2.4M Mellon, $300K Hewlett grants; additional investment via community partners. 15
BORROW
Kuali Foundation
http://www.kuali.org/ Non-profit organization responsible for sustaining and evolving a comprehensive suite of administrative software that meets the needs of all Carnegie Class institutions Members are colleges, universities, commercial firms, and interested organizations that share a common vision of open, modular, and distributed systems for their software requirements Goal of Kuali is to bring the proven functionality of legacy applications to the ease 16 and universality of online services.
BORROW
Kuali Foundation
Financial Community Endowment Community Research Community Workflow Community Nervous System Community
Student Services System
Under development Release 1 proposed for 1st quarter 2009 17
BORROW
Keys to development of community source systems
Ability to identify partners Utilization of one university’s system as a starting point for development Extreme collaboration Upfront funding (with uncertain delivery timelines)
Systems will be built to meet the needs of the development partners 18
The FUTURE
19
BLEND Buy ‘best of breed’ for core business practices Build aspects that address market differentiation OR Buy and customize to meet your needs Borrow components from open source initiatives that meet your needs
20
BLEND
Indiana University BLEND strategy BUY PeopleSoft
for Student Administration 3rd Party vendor products for smaller applications Ad Astra for room scheduling PeopleSoft Reporting Data Service infiNET (eCommerce and SIS) ApplyYourself 21
BLEND
Indiana University BLEND strategy BUILD In-house
development for Electronic Documents IU modifications and customizations Interfaces among university information systems, batch processing, reporting Reporting environment for reports and data extraction
22
BLEND
Indiana University BLEND strategy Borrow Modifications
from other universities Sakai OnCourse course support product Watching for Kuali student developments
23
BLEND
What are the Drivers?
24
What is best for your organization?
25
Your Questions and Comments
26
Resources Building a Student Information System: Strategies for Success and Implications for Campus Policy Makers. Hosler D, ed. New Directions for Higher Education, no. 136, Winter 2006 Student Information Systems: A Guide to Implementation Success. Sharon F. Cramer, AACRAO 2005 Open Source Student Systems. Wheeler B. http://student.osnext.org/ 2006
27
Thank You
28
