1 / 25

Assessment of Portal Options

Assessment of Portal Options. Presented to: Technology Committee UMS Board of Trustees May 18, 2010. The CPS Assessment Team. Matt Combs. Ed Cornelius. Brian Ellis. Tom Danford. Topics for this Presentation. Purpose of the Project Benefits of a Portal Data we Collected

marcin
Download Presentation

Assessment of Portal Options

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Assessment of Portal Options Presented to: Technology CommitteeUMS Board of TrusteesMay 18, 2010

  2. The CPS Assessment Team Matt Combs Ed Cornelius Brian Ellis Tom Danford

  3. Topics for this Presentation • Purpose of the Project • Benefits of a Portal • Data we Collected • What UMS Constituents Want in a Portal • Different Types of Portals we Considered • The Two we Recommend and Why

  4. What We Were Asked To DO • Research various portal options in the market. • Recommend one or more options that will meet the needs of the University of Maine System institutions.

  5. What is a Portal? Most would agree that an enterprise portal creates a common gateway to the data and services that the people throughout a school or system need to effectively share information, deliver constituent services more efficiently and work together on projects.

  6. What is a Portal? NOTE: V2 The enterprise portal is an integration platform that securely provides a central point for accessing, personalizing and configuring information and applications that are appropriate to their role(s) in the university.

  7. Benefits of a Portal • Saves time • Increases student engagement • Facilitates anytime, anywhere learning • Helps make better decisions • Lets faculty focus on research and instruction • Streamlines administrative tasks • Connects with your community

  8. Data Collection Methods The Information We Collected to Make a Recommendation

  9. Data Collection Methods • Focus group sessions • Online Survey • Input from portal vendors

  10. Focus Group Participation • 9 Focus Group Sessions with participants from all institutions • 14 Faculty members • 18 Students • 32 Administrative Staff • 15 Technical Staff • 6 SMEs from UMS

  11. Online Survey Participation

  12. Vendor Participation • 35 organizations were identified, contacted, and asked to provide information • A statement of work and a response spreadsheet were circulated • 15 vendors (43 percent) willingly returned information on costs, timeline, functionality, and other factors

  13. Results: Part 1 What Constituents Wanted in a Portal

  14. Strongest Needs • Portal must make navigating from one resource to the other more efficient and more user friendly • Portal must allow for campus specific branding and personalization of content and capabilities • Portal must allow for distributed administration even when centrally hosted • Portal should allow for users with multiple campus relationships and multiple roles

  15. Portal needs to include more collaborative tools or features to facilitate communication between student, students and advisors, instructors and student, and peer to peer • Portal must integrate with critical administrative systems to trigger alerts and notifications to relevant users • Portal should be able to allow for distributed contribution model

  16. Results: Part 2 Portal Options That We Investigated

  17. Five Categories of Portals • Portal Development Partner (Commercial) • Portal Development Partner (Open Source) • Turnkey COTS Portal • Turnkey COTS SaaS • Turnkey Non-Profit Consortium

  18. Factors That we Assessed for each Portal Option • Benefits • Drawbacks • Acquisition costs • Maintenance & upgrade costs • Implementation costs • Timeframe • Technical skills needed • Level of risk • Hardware costs • Staffing costs • TCO • ROI factors

  19. Selected Findings • Each portal category had its strengths and weaknesses • All portal options will satisfy most if not all the needs and requirements of UMS stakeholders • Projected over 5 years, the lowest TCO estimates were $3M to $4.4M • The highest TCO estimates were in a range of $13.3M to $13.7M

  20. Options Going Forward The Two Portal Options We Recommend and Why

  21. Two Solutions that will Best Benefit the UMS Institutions Turnkey COTS (PeopleSoft) Turnkey Non-Profit Consortium (Liferay) • These two portal options had several advantages for UMS institutions • Lowest TCO over five years in the range of $3.5M - $4M vs. the $5M - $13M range of the other portal option categories

  22. Turnkey COTS (PeopleSoft) • PeopleSoft portal is already integrated with the MaineStreet applications • Large installed base of clients • Software code is maintained and updated by the vendor • PeopleSoft portal can handle all user needs that we identified • Has the lowest TCO and the potential for the highest ROI

  23. Turnkey Non-Profit Consortium(Liferay) • Liferay is the leading open source enterprise portal • CampusEAI has support services and a private consortium of like minded schools • Liferay integrates with all key higher education administrative systems • Can deliver most if not all user needs • Comparatively low TCO

  24. The Choice for UMS • UMS essentially must make a choice between relying on a well regarded commercial product (PeopleSoft) and a well regarded “open source” product (Liferay). • Both paths have pros and cons and the good news is that UMS has experience with each. Total Cost of Ownership over time is fairly similar and risk factors equal out.

  25. Assessment of Portal Options Presented to: Technology CommitteeUMS Board of TrusteesMay 18, 2010

More Related