1. Fall 2003 CSG Workshop Buy vs. Build vs. Open Source Maloney, Morgan, Morooney, Hanss, Eadie

2. Wednesday Workshop Agenda Morning: Morning: Sebastian Rahtz, U Oxford, JISC Advisory Service on Open Source Software winnersSebastian Rahtz, U Oxford, JISC Advisory Service on Open Source Software winners Bernie Gleason, BC, “Business of Open Source”Bernie Gleason, BC, “Business of Open Source” Afternoon: Afternoon: Panel Discussion – decision processPanel Discussion – decision process Panel Discussion - PortalsPanel Discussion - Portals

3. They said it… “In general, we believe ‘buy versus build’ is no longer an issue on which organizations can usefully take a categorical stance. IT leaders should focus on practical considerations rather than pointless philosophical discussions.” IT Insights from the Meta Group, Tips on managing the application portfolio, 12/10/2002

4. University of Texas Buy vs. Build Quiz

5. Sage Thought… Who said: “We face the choice of dying by our own hands or at the hands of the vendors.”

6. Sage Thought… Who said: “We face the choice of dying by our own hands or at the hands of the vendors.” Terry Gray

7. Survey Question # 1 Does your institution and/or department have a policy/principles (written or unwritten) regarding buy vs. build vs. open-source? Does your institution and/or department have a policy/principles (written or unwritten) regarding buy vs. build vs. open-source? Nearly unanimous>> Unwritten policies and strategies Nearly unanimous>> Unwritten policies and strategies

8. University of Texas Documented Principles

9. Lessons Learned Back office systems usually bought Back office systems usually bought Trend/Wisdom seems to be: Trend/Wisdom seems to be: Going from build to buy, and,Going from build to buy, and, Going from buy to Open SourceGoing from buy to Open Source Strong unwritten policy culture and decision-making Strong unwritten policy culture and decision-making Timely discussion, esp. re. OS Timely discussion, esp. re. OS

10. Survey Question #2 Please rank the following decision factors in determining a "buy vs. build vs. open source" decision: Please rank the following decision factors in determining a "buy vs. build vs. open source" decision: 1. support 2. cost 3. standards 4. security 5. speed of implementation and changes 6. access to source code 7. licensing

11. Lessons Learned Easier to write survey than to tabulate results! Easier to write survey than to tabulate results! Could/should have included: Could/should have included: TCOTCO FunctionalityFunctionality Ability, viability, and vision of providerAbility, viability, and vision of provider Integration & Implementation becoming increasingly challenging Integration & Implementation becoming increasingly challenging

12. Survey Question #3 Specify bought, built, or open-source solution: a. Admin Systems--- buy a. Admin Systems--- buy b. Anti-SPAM services--- buy/os b. Anti-SPAM services--- buy/os c. Anti-virus services --- buy c. Anti-virus services --- buy d. Authentication --- built/os d. Authentication --- built/os e. Backup Systems --- buy e. Backup Systems --- buy f. Calendaring --- buy f. Calendaring --- buy g. Content Mgt/Lib --- buy/built g. Content Mgt/Lib --- buy/built h. E-commerce --- buy h. E-commerce --- buy

13. Survey Question #3 Specify bought, built, or open-source solution: i. Email client --- buy i. Email client --- buy j. Email service --- os/buy/built j. Email service --- os/buy/built k. Enterprise Directory--- buy/os/built k. Enterprise Directory--- buy/os/built l. Firewalls --- buy l. Firewalls --- buy m. Intrusion Detection--- os/buy/built m. Intrusion Detection--- os/buy/built n. LMS --- buy/built n. LMS --- buy/built o. Net/Server Mgt/Mon--- buy/built o. Net/Server Mgt/Mon--- buy/built p. Portal --- buy/os/built/no portal p. Portal --- buy/os/built/no portal q. Search Engine --- buy q. Search Engine --- buy

14. In the News - ComputerWorld Buy major ERP and CRM suites Buy major ERP and CRM suites Build software if have special feature or capability needs Build software if have special feature or capability needs Buy packaged solutions, much cheaper and faster to implement Buy packaged solutions, much cheaper and faster to implement Build custom software that provides differentiation Build custom software that provides differentiation ComputerWorld, June 2, 2003, Chart: Tipping Factors in the Buy vs. Build Debate

15. In the News – Mitre Report OS Successes – Emacs, GNU, Apache, Sendmail and Linux OS Successes – Emacs, GNU, Apache, Sendmail and Linux Decision process Decision process Lifecycle CostLifecycle Cost BenefitsBenefits Intangibles, e.g., peer supportIntangibles, e.g., peer support Growth in OS usage Growth in OS usage Mitre Corp, A Business Case Study of Open Source Software, July 2001

16. In the News – Mitre Report, cont. Open Source vs. Buy Decision Steps 1. Assess supporting OS community 2. Examine Market 3. Conduct specific analysis of benefits and risks 4. Compare long-term costs 5. Choose your strategy

17. Buy Paradigm Pros Pros Less expensiveLess expensive Implement quicklyImplement quickly Known features and functionalityKnown features and functionality Cons Cons Will the vendor deliver, and/or surviveWill the vendor deliver, and/or survive Release dilemmaRelease dilemma Integration with disparate systemsIntegration with disparate systems

18. Build Paradigm Pros Pros Total controlTotal control Develops staff skillsDevelops staff skills Custom fitCustom fit Cons Cons CostlyCostly Hard workHard work Slow to deploySlow to deploy Staff OTJ trainingStaff OTJ training

19. Open Source Paradigm Pros Pros Price is rightPrice is right Lots of controlLots of control Quicker to implement than BuildQuicker to implement than Build Solid collaborative efforts (uPortal) esp. in higher edSolid collaborative efforts (uPortal) esp. in higher ed Technical staff very interested/motivatedTechnical staff very interested/motivated Cons Cons Life of OS communityLife of OS community SupportSupport Reliant upon staffingReliant upon staffing CustomizationCustomization