OHIO Ciber Portal Requirements Report

OHIO UNIVERSITY RUFUS INITIATIVE
ENTERPRISE PORTAL REQUIREMENTS INITIATIVE
Prepared by: Marc Troeger, CIBER, Inc. Kerensky Rowan, CIBER, Inc. July 2009
Rufus Initiative
Enterprise Portal Requirements
1. CHANGE HISTORY
VERSION DATE CHANGED BY CHANGE
1 2
06/23/2009 7/16/2009
Marc Troeger Marc Troeger Kerensky Rowan
1st draft Final Draft
Proprietary and Confidential: Ohio University
Page 2 of 47
Rufus Initiative
2. CONTENTS
1. 2. 3. 4. CHANGE HISTORY ......................................................................................................................................... 2 CONTENTS........................................................................................................................................................ 3 OVERVIEW ....................................................................................................................................................... 4 REQUIREMENTS AND FINDINGS ............................................................................................................... 7 4.1 4.2 4.3 4.3.1 4.3.2 4.3.3 4.4 4.5 4.5.1 4.5.2 4.5.3 4.6 5. GENERAL PORTAL DEMONSTRATION .......................................................................................................... 7 BRANDING ................................................................................................................................................... 8 CONTENT................................................................................................................................................... 10 Portal Content ..................................................................................................................................... 10 Search .................................................................................................................................................. 15 Monitoring and Reporting Tools ......................................................................................................... 17 NAVIGATION ............................................................................................................................................. 18 TECHNOLOGY ............................................................................................................................................ 20 System Requirements and Infrastructure ............................................................................................. 22 Scalability ............................................................................................................................................ 23 Services and support ............................................................................................................................ 24 SECURITY AND ROLE MANAGEMENT ........................................................................................................ 26
SUMMARY AND RECOMMENDATIONS ................................................................................................. 29 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 OU PORTAL DEFINITION ........................................................................................................................... 29 BRANDING AND DESIGN............................................................................................................................. 29 CONTENT AND NAVIGATION ..................................................................................................................... 30 TECHNOLOGY AND INTEGRATION ............................................................................................................. 31 SECURITY .................................................................................................................................................. 31 DEPLOYMENT AND TIMETABLE ................................................................................................................. 32 REPORTING AND TRACKING ...................................................................................................................... 33 RESOURCE SUPPORT AND SKILL SETS ....................................................................................................... 33 TRAINING .................................................................................................................................................. 33 SYSTEM SUPPORT AND MAINTENANCE ..................................................................................................... 34 GOVERNANCE ........................................................................................................................................... 34 KNOWLEDGE TRANSFER............................................................................................................................ 35 ASSUMPTIONS AND RISKS ......................................................................................................................... 35
6.
CONCLUSION................................................................................................................................................. 36
APPENDIX A PORTAL COMMITTEE.............................................................................................................. 37 APPENDIX B PORTAL SESSIONS AND ATTENDEES .................................................................................. 38 APPENDIX C - RESOURCES ................................................................................................................................. 42
Portal Vendors and Service Providers to Higher Education (partial list) ........................................................................ 42 Examples of Portals and Demo Sites .............................................................................................................................. 42 Portal Reference Articles and Whitepapers..................................................................................................................... 44
OVERVIEW OF RUFUS INITIATIVE PROJECT............................................................................................... 46 CONSULTING PARTNERSHIP ............................................................................................................................. 47
Page 3 of 47
Rufus Initiative
3. OVERVIEW
In June of 2009, Ohio University began a five week Portal Requirements project, as part of the Rufus Initiative, that will transform the student administration system across all campuses. The purpose of Portal Requirements project was to meet with the many faces and departments of OU to gather requirements in preparation for preparing a Request for Proposal (RFP) and selecting a portal software application. As part of this requirements gathering initiative, Ohio University contracted with CIBER, Inc. to assist in the following: Define what a portal is to Ohio University Define the overall requirements a portal should provide to the University community Identify the needs specific to students, faculty, staff and administrators involving input from various groups from across the university Work with the Portal Committee to begin addressing issues related to the selection and deployment of a portal.
Requirements Gathering
Sessions will be conducted with various groups on campus, representing many different offices and departments on campus (see Appendix B for list of attendees and offices represented). The agenda for each of these sessions will be to: 1. Explain the general concept of a portal 2. Provide examples of how portals are used at various universities around the country 3. Identify requirements specific to the offices and departments represented 4. Solicit additional thoughts and ideas for what a portal means for Ohio University Participants will be given a general overview of what a portal is, using various examples of commercially available portals such as Yahoo or Google, and then presented with real-life examples of portals that have been deployed at colleges and universities around the country (see Appendix C for list of examples). Participants will be introduced to the general concepts and components of a portal:
Page 4 of 47
Rufus Initiative
During the sessions, the participants will be asked to focus on the content they would expect to see as part of the portal. Content types will be represented in three different categories: Content Type Transactions Communication Description Transactions related to a specific user within a specific role Communication related to a specific user or to a specific user role; a communication is considered time sensitive and relative to a specific point-in-time or event Information is less time-sensitive and covers a broader scope and audience. Information does not have to be directed to a specific role. Examples Registering for classes, checking financial aid, reviewing benefits, downloading pay stub Holds and messages directed to the user; alerts and special notices directed to user roles; emergency notifications Community calendar, course catalog, weather information
Information
Additionally, sessions will be held with staff from the Office of Information Technology (OIT) to review technical and security requirements, particularly as they relate to the overall Rufus Initiative.
Findings and Final Report
At the conclusion of the requirements gathering, a report will be produced outlining the requirements that were identified and recommendations as OHIO moves forward with RFP preparation and vendor selection.
Page 5 of 47
Rufus Initiative
State of Portal in Higher Education
Enterprise Portals are proving their value within large colleges and universities, becoming fullyintegrated business solutions that are front and center in managing and e-enabling global operations and diverse workforces. Leading organizations are pushing portals beyond their early value propositions and expanding these channels to support critical change initiatives, foster student, faculty and staff communications, realize the internal brand, and enhance innovation and growth. Colleges and universities are constantly adapting to changes in the educational marketplace, facing competitive pressures from traditional and online institutions and facing more and more federal and state regulatory scrutiny. These changes in turn depend upon improved process controls, better information sharing, and more effective use of intellectual assets. Enterprise portals can help support all of those initiatives with: More effective process management of students, faculty and staff Information sharing tools, including content/document management, project collaboration tools, and multi-platform search and navigation A single point of access to management information, such as data warehouses and related business intelligence repositories A single, consistent place for information and application services Deliver dashboard-style interface integration, including personalization The demand to create a more efficient and responsive university is a key driver behind most campus IT strategic initiatives. So what is so different about portals? Portals play a role in several broad strategic initiatives by: Improving coordination with business partners, suppliers, and customers Facilitating internal collaboration between student, faculty and staff Allowing better management of intellectual assets Aiding in compliance with government regulations In addition to efficiency, the convergence of portals and social networking is on the forefront of technology. Enterprise adaptation rates will increase within the next few years as the new Websavvy generation joins the work force. Enterprise portals are beginning to embrace social networking components that facilitate their metamorphosis into online communities. They will still fit the definition of an Enterprise portal, but will enhance the status of their "users" to "members" because members will be able to steer the direction of the site. Internal and external communities alike will enable easy collaboration and communication amongst members, and will also expand to allow multi-directional communications by providing typical social networking components such as groups, blogs and bulletin boards. In addition, a mobile component and interaction will be an essential part of todays Enterprise portal. Students will want to be engaged with the institution while away from their computers and need to have access to the class assignment information, scheduling, calendar events, etc.
At a basic level, portals address the need for improved capabilities by providing a framework for integrating existing applications and information stores, and creating a flexible infrastructure that can adapt to emerging needs and requirements.
Proprietary and Confidential: Ohio University Page 6 of 47
Rufus Initiative
4. REQUIREMENTS AND FINDINGS

The agenda the requirements gathering meetings will be: Explain the general concept of a portal Provide examples of how portals are used at various universities around the country Identify requirements specific to the offices and departments represented Solicit additional thoughts and ideas for what a portal means for Ohio University The requirements identified during these sessions will be listed in the following sections: 1. Branding 2. Content 3. Navigation 4. Technology 5. Security and Role Management As the requirements are identified, they will also be identified with a rating of (R)equired or (D)esired. Two columns will be used so that the initial rating will be made by the consultants, with follow-up ratings made by OHIO staff.
4.1
General Portal Demonstration

1. Provide a brief history of your company including years in business and acquisitions. 2. Give an overview of our companys products and services, highlighting the key products your company offers. 3. As part of your application demonstration, give a 360 degree Day-in-theLife overview of your application as it relates to: a. Students b. Faculty c. Staff d. Parents e. Guests f. Vendors 4. Show examples of you application operating using various browsers. Provide demonstrations of your applications mobile capabilities. Include various mobile formats such as: iPhone, Smartphone, small-screen browsers.
Questions:
Page 7 of 47
Rufus Initiative
4.2
Branding
Branding is critical to creating identity and environment in a portal. While branding should be controlled and consistent, the branding itself should not impede the common fact that a portal should provide a comfortable, consistent environment in which users perform transactions, manage communication, and seek information. Branding should enhance the user experience and be a part of the online relationship the University is trying to establish with the user. To build this relationship, the following should be taken into consideration: Branding should be a wrapper that frames the portal in an attractive, yet functional form Branding curates content, defines the style, look and feel for the interaction/direction and eventual destination/transactions Branding is consistent and familiar. While the content of a portal is dynamic, the brand should be familiar and welcoming; consistent across the portal Branding lends to ease of use; branding itself should not overshadow the purpose
Branding Requirements Identified
Requirement Allows full customization of look and feel of portal design Supports placement of interactive media Branding is locked into templates and can only be updated by key individuals Is software agnostic in accepting a multitude of media formats Is browser agnostic; should work across various web browsers Allows for highly configurable branding to conform to University image standards to control pages and pagelets CSS compliant Allows for user configured style sheets to control pages and pagelets Allows users to select alternate style sheets, based on user role/security? Allows for importing of content from external HTML editors Recognizes standard HTML formatting tags
OHIO
CNSLT R D R R R R D D D R R
Notes Colors, images, logos, links, shades, shaping, tabs, fonts Videos, slideshows, audio,
i.e. .jpg, .gif, .png, .mp4, etc. i.e. Firefox, Opera, Chrome, mobile browsers Must allow the University to manage and control style and branding directly Allows full flexibility for design and branding
Page 8 of 47
Rufus Initiative
Application includes an HTML editor, allowing for direct editing Provides tools within the application to validate and identify errors within HTML scripts Provides formatting to accommodate mobile hardware Support for ADA compliance standards Allows for various web design programming languages Allows for co-branding based upon user role and affiliations Allows for co-branding with external sites While the main Branding wrap is locked, other individuals can update cobranding areas Provides an authorization system that requires manager approval of branding changes made by another user, before it is published
Additional Questions:
R R R R D D D D Portal pages for schools, departments, organizations affiliates with OHIO iPhone, Smartphone, smallscreen cell phones Americans with Disabilities Act AJAX, JAVA, Pearl, php, etc.
1. Provide a demonstration, showing the branding capabilities of your application. 2. Give an overview on how style templates and style sheets can be used for maximum branding flexibility. 3. Describe how your product applies and enforces style restrictions and constraints. 4. Explain any branding restrictions your application has. 5. Provide examples in how your application maintains ADA compliance.
Page 9 of 47
Rufus Initiative
4.3
Content
In a web portal, everything is content. From the pagelets that provide access to registration or payment of bills, the search box at the top of the page or the contact information in the footer of a page, all are content that has meaning to the user. In a portal, content can be arranged to have greater meaning to the user based on the role(s) assigned to that user.
4.3.1 Portal Content
Content Requirements Identified
Requirement Content Features Provides Instant messaging capability Provides voice chat capability Integrates with VOIP applications Provides scrolling news/information tickers Provide delivered pagelets with functional tools and 3rd party integration such as calculators, notepads, stickies, Weather Bug, Google maps, news feeds, etc Provide the ability to print portal content in printer friendly format Allows for customizable content without user having to log in
OHIO
CNSLT D D D D D
Notes i.e. help desk i.e. Skype Promotes University news, events, alerts, etc
D D i.e. OHIO has this feature now for prospective students to indicate major and activity interests through drop downs to create a customized portal focusing on those interests i.e. 3rd party Alumni portal i.e. iPhones, Smartphone, small-screen cell phones
Allows interfacing with content from other portal applications Supports creation of content that can also be rendered on mobile hardware Provides mobile features that identifies specific mobile hardware logging and is automatically formatted to meet the display requirements of that hardware. Provides ability to deliver BI content, such as KPIs in a secure, graphical environment Provide a bookmarking feature for internal and external content
D R D
D R
Page 10 of 47
Rufus Initiative
Allow guests to RSVP to invitations to events regardless whether he/she is a registered user Provide gateway for secure, financial transactions Provide ecommerce functions for bookstore or alumni products Easily allows for third-party integration of point-of-purchase providers Provide security for limited access portals.
D R D
i.e. At OHIO, students can grant access to parents to view and pay bill through CASHNet. A parent portal provides access where students can grant parents access to pay their bills, look at grades, etc Personal To Do items Administrative To Do items
Provide an event management system, tied into calendaring feature Provides To Do functions that allow user to manage personal as To Do lists. Provides a comprehensive To Do list that draws task items from several sources and combines them into one list Includes tools to allow portal content to push content through external APIs such as Facebook or MySpace Customizable calendar that allows content from other external calendars to be pushed into one comprehensive user calendar with features to filter content by user Allow students to create their own portal page and content for student groups and organizations Provide features that create a Craigslist-type bulletin board where users can post sale/wanted ads (i.e. textbooks, rooms for rent, etc) Provide tools and features for creating and promoting polls and surveys Editing Tools Provides editing tools to easily allow creation of content in the form of pages, tabbed sections, pagelets and other sites
D R R
D D
D D
D R
Page 11 of 47
Rufus Initiative
Provides an easy to use preview tool to review content in WYSIWYG format, before publishing Includes tools to publish content as magazine/newsletter formats Provides project management tracking for content development Includes the ability for content developers to record notes and version update comments that are directly related to the content Provide role-based security that defines who has access to edit/manage content Provide role-based security that defines how a user has access to edit/manage content Provides easy to use editing tools for users with minimal skill set to add or update content Provides built in spell checker Supports the copying/moving of content from one portal site to another Provides tools to optimize/reformat uploaded content such as pictures/videos for optimal performance Allows assigned user to create content/pagelets made up of internal and external hyper links Provide the ability to publish content for future dates Provides workflow features that require manager approval of content created by another user before it is published. Workflow should also include notification features. Provides automated notification workflow to manage approval system Provide feature that allows customizable ads or badges that visually promotes critical transactions, notices or events Supports various interface/API standards to external content Easily stores and organizes uploaded content
D D D R i.e. student newspaper, departmental newsletters, etc
R R R D R R R R R i.e. view only, update only, creation only, etc. i.e. to add/update portal content
R D i.e. Give to Current Campaign Promote sporting or theater event and other alerts or announcements i.e. WeatherBug, Facebook/MySpace streaming, RSS feeds Pictures, videos, documents, etc.
Page 12 of 47
R R
Rufus Initiative
Provides tools for building database queries into content. Provides delivered integration to Oracle/PeopleSoft Campus Solutions Provides delivered integration to Oracle HR and Finance Provides delivered, single-sign on integration to Adirondack housing system Provides tools to enable single-sign on with other applications. Alerts/Notifications Provide an emergency alert notification system through the portal Provides tools to push information/announcements/alerts to users via delivery medium of their (users) choice Allows content from other systems to be pushed to the portal, based on user roles, providing highly visual alerts and notifications Sends notices to administrators/authors when content has expired Allow alerts to be created that notify users of updates or additions to content Provides visual/audio alerts to notify of upcoming To Do/Calendar events
R R R R R
R R
i.e. alerts from an emergency notification system pushed to the portal
D D D i.e. content has been revised on a pagelet or article.
1. Describe how content is created using your application. 2. Describe the process for submitting and approving content in your application. 3. Explain the workflow process your application provides. Include how developers and managers are notified throughout the workflow process. 4. Demonstrate how your application builds internal and external RSS feeds are into content. 5. Provide a demonstration for the most optimal way a user will be alerted to: a. Campus emergencies b. Individual student related alerts related to to-do items, holds, late payment notifications c. Campus events and activities, including the ability to filter relevant content d. Academic calendar events and deadlines 6. Give an overview of the project management tools your application provides. 7. Describe the process that occurs when content is revised.
Rufus Initiative
8. Describe how content is secured and linked to users and roles using your application. 9. Describe how your product integrates with other editing tools for creating content. Explain how content can be imported from HTML editor. 10. Give an overview of the latest scripting technologies (i.e. AJAX, Pearl, PHP) your application uses in delivering content. 11. Explain how your application integrates with other 3rd party content using APIs (i.e. Facebook, Google, Yahoo, etc). 12. Give a demonstration showing how database queries can be displayed as content. 13. Explain the type of skills a user will need in order to create content, using your application. 14. Describe how your application validates and reports on issues/errors related to content. 15. Explain how developers and managers are notified of content that has been expired or has not been updated within a certain period of time. 16. Describe how standards are applied to uploaded objects (i.e. images, video, and documents), and how it is automatically formatted to meet those standards. 17. Give an overview on how uploaded content is managed and stored in your applications directory system.
Page 14 of 47
Rufus Initiative
4.3.2 Search
It is predicted that, in the next 10 years, search will play a much more significant role in personal, online interaction with all facets of data. In fact, search will eventually become a seamless part of the tasks that people will perform while online. The next revolution in web technology, which has only just begun, will be toward more semantic searches; a more intelligent, seamless search across multiple resources, returning more accurate, personalized results. In a sense, the semantic search will act, unto itself, as a vast database and repository. Key to the success of a portal is the capability for allowing users to find the information they need, and just as important, the information they are authorized to access. The portal can be the doorway to a secure search environment across all the applications and administrative systems that OHIO deploys by taking advantage of features that include: Single sign-on that allows searches to securely cross into authorized applications Indexing of multiple data elements including tags, metadata Allows search to be performed securely across platforms
Search Requirements Identified
Requirement Supports tagging and linking metadata tags to for content searches Allows for the creation of indexes to optimize content search Prevents searching on secure data that user is not authorized to access Capable of using other search engines for portal searches Provides ability to create pagelets to execute searches within other systems
OHIO
CNSLT R R R R R
Notes
i.e. allows institution to choose to use Google or Bing search engines i.e. University Library, campus staff/student/faculty directory
1. Demonstrate how your application performs content and navigation searches. Include examples of your advanced search capabilities. 2. Explain how archived content can be included in searches. 3. Show how 3rd party search engines can be integrated into your application. 4. Describe how your system tracks and indexes content and content metadata. Provide examples on how content is classified and indexed for optimal search:
Rufus Initiative
a. Text b. Images and other objects c. Keywords d. Tags and metadata 5. Explain how your application indexes images and other objects that are uploaded? Provide an overview on how metadata is linked to these objects. 6. Give a description in how content navigation is indexed and optimized for best optimal search. Show an example of how this would appear in search results.
Page 16 of 47
Rufus Initiative
4.3.3 Monitoring and Reporting Tools
Monitoring and reporting tools are critical to evaluating the success of a portal and content. Upon deployment, a portal administrator should monitor many facets of the portal usage including: Log-on statistics Navigation to content Content usage Searches performed Errors and system issues Security issues (i.e. SSO monitoring)
Monitoring and Reporting Requirements Identified
Requirement Allows querying of portal database through delivered query tools or via 3rd party reporting tools Provide tools to monitor links, indentifying dead links with notifications/alerts Provide reporting tools to track content as it is developed and throughout the content lifecycle Provides tools that monitor user access, tracking statistics on user navigation and content accessed Provide tools to monitor searches performed while logged into the portal
OHIO
CNSLT R D R R R
Notes
1. Provide an overview of the tools your application has for querying the application database. 2. Give examples of the integrated monitoring tools your application uses to track content and user usage. 3. Explain how your application integrates with other major analysis tools.
Page 17 of 47
Rufus Initiative
4.4
Navigation
Navigation in the portal should be seen as a dynamic, logical pathway to content. It should lead to the presentation of content is such a way that is intuitive and comprehendible by the specific user. Many facets need to be taken into consideration including the user role, the users purpose for being on the portal, the transactions available to the user and even considerations such as multi-lingual and multi-cultural needs. Without proper navigation, content can be considered irrelevant if users cannot easily complete tasks or find information they seek. Navigation should be considered key to defining the portal relationship you want to build with a users or a role that is defined for a group of users. Establishing a good, user relationship will enhance the user experience, encouraging them to return.
Designing Navigation
Examples of key questions that that should be asked when building navigation include: How will users navigate to the portal? How will users discover relevant content? How will your navigation provide a "pleasant" user experience? Navigation should be well thought out and reviewed. It should be graphically mapped in order to evaluate its usability and include access to features such as search boxes, contextual help, FAQs, breadcrumbs to retrace paths, indexes and content maps, navigation bars, menus etc. An example of a navigation graphical layout is shown below. This example was developed using a mind-mapping tool (See Appending B for more information):
Page 18 of 47
Rufus Initiative
Navigation Requirements Identified
Requirement Provides features that allow for the automatic creation of navigation or menus based on content creation options Provides the ability to automatically repair menu links when content is deleted/moved Includes tools that validate menu structure and links Allows user to personalize content by selecting content to appear that is relevant to that person Allows user to personalize content by moving content/pagelets around on page Allows administers to lock down content, preventing user from removing or moving it Allows groups/departments to create their own portal sites, independent of the main portal site, yet with all the controls and security.
OHIO
CNSLT D
Notes
R R
i.e. emergency alert pagelet
This would be sub-portal, (not an additional tab) that might allow a department to set up their own portal and content, with the overall control of branding, content, security residing with main portal administrators.
1. Give an overview on how the menus and navigation can be generated as content is created. Include how that content can be managed and manipulated by developers. 2. Provide an example, showing how your application updates navigation when content is moved or the hierarchy is changed. Include a demonstration of the tools that provide the checks and balances.
Page 19 of 47
Rufus Initiative
4.5
Technology
Defining the technical design and architecture of a portal solution can be an extremely complex activity. Many technical components must work cohesively to harness the foundational requirements (e.g., security, personalization, search, transaction integration, content publishing, and collaboration) that need to be leveraged across business solutions.
Technology Requirements Identified
Requirement Should have the capability to track login statistics Should follow the traditional implementation Path Ability to create additional environments for development phases Should provide online help capability within the application Should integrate with Blackboard Should integrate with PeopleSoft Campus Solutions Should integrate with Oracle Financials Should integrate with CommonSpot CMS application Should easily integrate with OHIOs tuition payment vendor, CASHNet Should integrate with CRM product of choice Should integrate with any of the Campus legacy applications Should support the major types of integration protocols such as (XML) Should have some type of intrusion prevention capability Should provide system monitoring capability Should provide system performance monitoring capability
OHIO
CNSLT R R
Notes
R R R R R R R R R R R R
Page 20 of 47
Rufus Initiative
Should have development tools to migrate configurations and customizations between environments Provide open API capability Should provide server side caching for increased performance Should support RSS feeds within pagelets Should have the ability to attach and upload any standard file type Should leverage 3rd party performance monitoring tools Should leverage 3rd party load testing software
R R R R D R Such as Loadrunner Such as word, excel, pdf
1. Explain the functional components your product delivers. Include other modules and features that can be added on. 2. Give a technical overview for how content is organized and stored. 3. Show how your product easily imports: a. Legacy web content b. XML based content c. Other Web Services d. Other scripting tools and applications e. 3rd party content using interfaces, APIs, etc. 4. Demonstrate how content can exported to other systems. 5. Provide an overview on how content is archived. Include the search capabilities of archived content. 6. Explain and demonstrate how your applications can be developed using multiple page templates for optimal display capabilities using many different browsers and formats. 7. Show how your application can integrate with other applications, servers and tool sets 8. Demonstrate how content from other databases (i.e. student administration system) can be imported, secured and displayed in your portal application. 9. Explain how your application allows for various instances in allowing for testing, configuration and production environments. 10. Explain the origin of the portal application technology you will be describing. If this application was acquired through acquisitions, provide a history of the changes to the code lines and integration that was needed and is currently needed. 11. Provide an explanation of the programming languages used to develop the technology used in your application. 12. Provide a list of all third-party applications required to meet the requirements of this RFP.
Page 21 of 47
Rufus Initiative
4.5.1 System Requirements and Infrastructure
A solid architectural foundation is critical to scalability and manageability. Portal products must either have an all-encompassing foundational package or leverage the load balancing, security, integration, task management and prioritization features of application servers.
System and Infrastructure Requirements Identified
Requirement Compatible with existing or New Hardware platform configuration Compatible with existing operating system (either Red Hat Linux or Windows OS) Compatible with existing database platform (either Oracle or MS SQLServer) Should have Database Redundancy and Failover capability. Should have ability to tune the various components within the architecture. Should support major standard email applications integration such as MS Exchange (administrative email system) and MS Live (student email system) Integrates University email system into alerts and messages as a result of actions occurring within the portal, with opt in/out options Should support various internet browsers Should support screen resolution variations Should be able to integrate content from current CMS system Should provide the ability to access the system from a mobile device
OHIO
CNSLT R R R R R
Notes
Ease of recovering if theres and outage Such as Web servers, Application servers, Database servers.
R To Do reminders, update to content in portal, campus alerts, etc. Internet Explorer, Fire Fox, Google Chrome i.e. Paperthins CommonSpot CMS application iPhone, Palm, Blackberry
R R R R R
Page 22 of 47
Rufus Initiative
1. Explain the typical installation and configuration process. 2. Provide a timetable showing the amount of time needed for installation, configuration and certification. 3. Demonstrate, using a flow chart, the hardware, software and networking configuration required to install your application. 4. Give an overview of the backup and restore process. Include recommendations for redundant systems.
4.5.2 Scalability
An ongoing Site Support and Maintenance services naturally follow the implementation of a major portal solution. A vendor should provide the full spectrum of support necessary to sustain and evolve an established online presence, with services as vital as governance, content creation, and metric assessments, to more ad hoc requirements such as technical troubleshooting and support, visual design, and quality control.
Scalability Requirements Identified
Requirement Should afford the ability for future growth in the number of users accessing the system Should provide Backup and System recovery capability to minimize down time Configurations should allow 24/7 accessibility Should have load-balancing, clustering, and failover capabilities. Should provide a disaster recovery plan
OHIO
CNSLT R R R R R
Notes
Integrate with existing Load-balancing hardware
1. Provide an overview of the growth of your product. Include explanations of releases that have involved significant updates and the efforts required to implement them. 2. Explain the hardware and networking requirements your product will need to provide 24/7 uptime and support for a university the size of OHIO. 3. Give an overview of the staff needed to support your application for a university the size of OHIO. 4. Provide a typical user response time while navigating through the application. Give examples of various infrastructure configurations, and explain how they would affect the user response time. 5. Provide the number of concurrent users that can login to the system at any given time without hindering performance.
Rufus Initiative
6. Provide examples of user login ratios of power user to super users to typical users, logging into the system. 7. Give an overview of resources that each component of the portal infrastructure will utilize on individual servers, such as memory foot print, hard drive space, and CPU utilization.
4.5.3 Services and support
A companys support of its products is critical to its success. Additionally, training and ongoing customer services are key to a good customer service model.
Services and Support Requirements Identified
Requirement Should provide procedures for error reporting and resolutions Should provide procedures for contacting the vendor helpdesk Should provide access to a knowledge based site to search for fixes and solutions Should provide procedures for escalating incidents Should provide 24/7 support Should outline an implementation approach that maximizes mentoring, coaching and knowledge transfer Should provide a schedule for patches and fixes Should have development tools for implementation Should provide and automated implementation tool and full release or version automated upgrade tool. Should provide schedule for proposed upgrades and updates Should provide technical and user training Should provide documentation supporting and outlining the configuration Should provide network specifications outlying system requirements and dependencies. Supports HIPAA Compliance
OHIO
CNSLT R R R R R D R R R R R R R R
Notes
Page 24 of 47
Rufus Initiative
Supports PCI Compliance Supports FERPA Compliance Should provide a dedicated technical resource for initial implementation
R R D
1. Provide an overview of the included standard support offering for your product. Explain any additional related costs. 2. Provide information on extended support and related costs. 3. Explain your companys system support policy. Include an overview of issues escalation and prioritization. 4. Provide an overview of your training program. Include current training offerings and the type of training material that is included. 5. Give an overview of the various skill sets and roles required to support your application. 6. Provide an overview of the professional services available to implement and support continued ongoing development of your application. Explain how these services are factored into the licensing and maintenance cost of your application.
Page 25 of 47
Rufus Initiative
4.6
Security and Role Management
Implementing security in a portal requires a basic understanding of standard security concepts. Using a Role based security matrix lets you dynamically match users to roles at login. Different roles allow users access only to the resources and tools that their assigned. Single sign-on (SSO) is mechanism whereby a single action of user authentication and authorization can permit a user to access all computers and systems that he or she has access permissions for, without the need to enter multiple passwords. A portal should seamlessly connect users, teams, and knowledge so that people can take advantage of relevant information across business processes to help them work more efficiently. A portal application service provider should provide an overview of their SSO such as the example below:
Security and Role Management Requirements Identified
Requirement Should integrate with the existing IDMS system Should be SSL compliant Should track login history
OHIO
CNSLT R R R
Notes
Page 26 of 47
Rufus Initiative
Should provide a notification mechanism if security breach is detected Should have to ability to encrypt passwords in the database Should have the capability to replicate users to multiple databases Should have the ability to implement single sign-on Should have the ability to audit user profile deletion or modifications Should have the ability to audit user profile deletion or modifications Should seamlessly SSO with PeopleSoft Campus Solution system Should seamlessly SSO with Oracle Human Resources system Should seamlessly SSO with Oracle Financials system Should seamlessly SSO with Blackboard system Should seamlessly SSO with the DARS system Should seamlessly SSO with the Data warehouse application chosen Should SSO with OHIOs CMS application, CommonSpot Should seamlessly SSO with the CRM system chosen Should seamlessly SSO with Campus Legacy systems Should allow browser to pass authentication cookies to Web server Should utilize authentication domain
R R R R R R R R R R R R R R R R
This configuration allows user browsers to send a single-sign on cookie to all the web servers
Page 27 of 47
Rufus Initiative
1. Provide an overview of how security is managed within your application. 2. Explain how roles are defined and assigned to users in your application. 3. Discuss what happens when a set standard of roles have been defined and used over a period of time and then additional roles are added or taken away. What issues arise when the original hierarchy is changed? 4. Provide examples of how granular roles can be developed. 5. What tools are integrated in your application that monitor and report on security related issues? 6. Describe how SSO is configured in your application. Note: Mathew Dalton will add additional security requirements and scenarios.
Page 28 of 47
Rufus Initiative
5. SUMMARY AND RECOMMENDATIONS

5.1
OU Portal Definition
The Portal Committee was charged with coming up with OHIOs definition for a portal. This should also serve as reference or even mission statement for what OHIO expects their portal to be. The OHIO portal will integrate information, people, processes and resources across institutional boundaries to provide a secure, single signon access point for information, communication and transactions as defined by the characteristics of the user. The successful OHIO portal will allow for de-centralized content contribution and content management, ensuring that the information and communication on the portal is current.
5.2
Branding and design
During the information gathering sessions, it was clear that a brand and design is important to the success of the OHIO portal. Over the past year, OU has completely revamped their web presence, designing a look and feel that is consistent and provides easier navigation. A portal will need to be flexible enough to allow OU to apply the same branding theme and branding design guidelines that have been established. While the look of the portal is important, it was encouraging to hear, during our meetings with University Communication and Marketing (UCM), that they are advocates of form follows function and strongly support ease of use, relevant and fresh content, and clarity in navigation above branding. It is important, though, that UCM should have a role in the initial deployment and ongoing development of the portal as branding and design is part of the overall user experience, and key to building the online relationship with users. One key point that was made in virtually every discussion group was that the portal will not replace OHIOs current web site. OHIOs web presence will continue to serve a much broader audience than those who would have a defined role within the portal.
Page 29 of 47
Rufus Initiative
5.3
Content and Navigation
The key to a portal is maximizing the ability to provide access to information and user transactions. It was quite evident, during the information gathering meetings, that there are a variety of applications that students, faculty, staff, parents, prospective students, alumni and visitors use every day to transact business and gather information related to Ohio University. Frustrations were voiced numerous times due to the inability to easily find content and information through the current web sites. For the portal to be a success, carefully organized navigation will be just as critical as the content it contains. In fact, navigation should help point users to content that is external to the portal as well (i.e. information residing on University, college or departmental web sited). This will require careful planning and mapping of existing data and content as it resides on systems across OU. Equally important was the expressed need to, not only organize content, but to make that content relevant to the role of that user. Content and navigation to that content should be controlled and secured based on the users role in the system. This will help to filter out data that is irrelevant to the user. While there were many content requirements (all are listed in section 4), one of the most requested was the need for better and more instantaneous communication. There was an expressed need for the ability to provide not only critical communication (i.e. emergency alerts), but to consolidate communication from many different sources into one consistent place. This would ensure that communication related to classroom changes, class assignment postings, holds or checklist items are communicated in an effective way for the user. That implies that the portal will allow the user to make a choice as to how these communications are delivered (i.e. email, text messaging, a portal announcement or to do list). Additionally, OHIO is open to allowing trained end users in the colleges, departments and even students groups and organizations to develop content through a common workflow approval process.
Page 30 of 47
Rufus Initiative
5.4
Technology and Integration
The Vendor should describe its approach for the design, development, testing, and deployment of automated interfaces between the various ERP systems and other OHIO University systems. The Vendor should be responsible for the development and deployment of a set of standard inbound and outbound interfaces for OHIO University to process transactions to and from the Portal and all the various applications systems. The Vendor will also be responsible for developing all required temporary interfaces due to OHIO Universitys intended phased deployment approach. For each required interface, services to be provided by the Contractor should include (but are not limited to): Interface design Interface development Testing Development of procedures that support interface operations. It is important that OHIO consider the architecture on which a vendors product is built. Critical to choice is scalability, versatility and openness. OHIO runs their administrative applications on Oracle or MS SQL Server databases, using Red Hat Linux or Windows operating systems. When reviewing applications, OIT needs to consider the current skill set and the applications required skill set. The implementation timeline is tight and training on new technology and development tools will have an impact on deployment. It is recommended that, at the time of vendor presentations, OHIO arrange for separate sessions to review the applications technology in more detail.
5.5
Security
Security is of the utmost importance to OHIO. It was made very clear during information gathering that this is one area where a portal application must meet or exceed the Universitys security standards. The Vendor will need to describe in detail, its approach to analyzing, establishing, and documenting security functions across all software modules, and integrating these security functions into the OHIO Universitys security network. The vendor should outline options for configuring application security that OHIO University may want to consider, and advantages or disadvantages of proposed approaches. It is equally important that vendors are aware of the IdM and MDM applications that OHIO plans to implement as part of the overall Rufus Initiative. It is strongly recommended that, at the time of vendor presentations, OHIO arrange for separate sessions to cover the security functionality of the application in more detail.
Page 31 of 47
Rufus Initiative
5.6
Deployment and Timetable
It has been stated that Portal (along with CRM and SoA) are foundations to the early success of the overall Rufus Initiative. While deployment and timetable will be somewhat dependent on the portal application selected, the vendors under consideration should be aware of the overall scope and timeline of the Rufus Initiative as shown below (as of July 1, 2009).
Rufus Initiative Implementation Timeline
At the time of the Portal Requirements gathering, the go-live deployment of the OHIO Portal is scheduled for August 2010.
Current portal deployment timeline
Milestone Requirements Gathering RFP Draft Complete Procurement Complete Implementation Begins Final Testing and Review Go-live Deployment
Deadline July 16, 2009 August 1, 2009 September 2009 October 2009 July 2010 August 2010
Page 32 of 47
Rufus Initiative
5.7
Reporting and Tracking
Reporting and monitoring were considered important, particularly during meetings with OIT. It was a common requirement from most groups that there be a tool to track usage statistics, expired content and workflow tools for new content approvals. Reports and monitoring tools are critical to evaluation the success of a portal and content. Upon deployment, a portal administrator should monitor many facets of the portal usage including: Log-on statistics Navigation to content Content usage Searches performed A vendors reporting functionality should be evaluated on the tools that are integrated with the application as well as the ability to use reporting and monitoring tools OHIO currently uses.
5.8
Resource Support and Skill Sets
Until a portal application is selected, OU does not know the resources and skill sets that will be required for the portal deployment. The OIT staff has a broad range of technical experience and skill sets. Those skill sets should be taken into consideration when evaluating vendors and their portal application. This is particularly important when considering the portal projects tight timeline and implementation schedule.
5.9
Training
During the vendor evaluations, OU will need to require the vendors to provide strategy and training plans that have been successful with other clients. The vendor should also provide schedules of classes offered and explain the delivery format (i.e. instructor taught, online, etc.). The vendor should address various types of training available including but not limited to: Project team functional training Project team technical training End-user training (through the use of a train-the-trainer approach) On-going training after the system is in production (e.g., new hire training, refresher training, and training on new software functionality)
Page 33 of 47
Rufus Initiative
5.10 System Support and Maintenance

The Vendor should describe its approach to issue identification, tracking, and resolution. This discussion should include the use of any tools or techniques that are integrated into configuration management, software change control, and the overall project management methodology. Topics to be addressed in this section include: Issue identification Issue tracking Issue review and prioritization Issue analysis Issue resolution Issue escalation In addition, the Vendor should describe its approach to making enhancements or modifications to the portal in a manner that facilitates an easy, low-cost and low risk migration to new releases of the baseline product. The Vendor should describe its approach to coding and documenting modifications in such a way as to ensure that they can be easily re-applied when Ohio University upgrades to new releases of the proposed software. The Vendor should also include its business-justification process for prioritizing and approving each of the identified potential enhancements.
5.11 Governance
Governance, particularly IT governance infers that there are a number of interested stakeholders, including the leaders of the RUFUS initiative, not to mention the CIO and, indirectly, all the leaders and board members above him, who have the necessary input into the portal decision making process. This is especially critical with the portal being the very visible front door to the RUFUS initiative. The key to the governance plan OHIO puts in place will prevent the portal from being "solely an IT project" and brings in critical users and voices from across the University together to be involved in decision making. Governance policy should define the responsibilities and rolls to plan, manage and direct, not only the implementation of a portal, but how the deployment of the technology will be managed across the University including expectations on how the portal will be used. Governance policies should be developed that define responsibilities related to: overall success of the portal the look and feel of the portal (branding) content and those who will be granted access to create content security and access control Monitoring and usage of portal Portal infrastructure, maintenance and updates Regular reviews of overall portal strategy and ongoing development See Appendix C for additional resources on portal governance.
Rufus Initiative
5.12 Knowledge Transfer

Knowledge Transfer between a software application partner and the vendor is paramount to a successful implementation. While "knowledge transfer" itself would not be a feature requirement, it should be clearly understood by the vendor and contracted implementation partners that OHIO must be satisfied with the amount of knowledge and skill that has been passed on during the implementation and ongoing deployment.
5.13 Assumptions and Risks

Assumptions
While risk is never desirable in a project, it should always be taken into account along with appropriate contingency plans. By defining assumptions, you are outlining a succession of steps or events that must occur for a successful outcome. Examples of assumptions could be: 1. Core implementation will be completed on schedule allowing functional testing to be completed by _____________ 2. Testing effort will have adequate staff and consultant resources 3. Production equipment/software will be delivered and functional 4. Identity management system will be deployed
Risks
A risk would be areas where inherent issues have been identified (i.e. tight timeline, possible staffing shortages, under-trained resources, etc.) that could have impacts on the project success. Identifying those risks and their impacts early will allow you to make contingency plans to lessen any negative impact. Below are a few examples of risks involved with a testing strategy:
Risk 1 Implementation and development is not completed on schedule. Impact Testing is delayed and not completed on time. Contingency Contingency 1: The projects progress will be continually monitored. If the project schedule becomes a concern, appropriate action will be taken at the time to keep the project on schedule. Contingency 2: Shorten test phases. 2 3 Testing personnel shortage Not enough time to test Testing timetable may suffer Testing timetable may suffer Identify and train a backup testers Prioritize testing to ensure application functionality works for critical and major business processes.
Page 35 of 47
Rufus Initiative
6. CONCLUSION
While this document outlines the requirements for a portal, it also sets the foundation for what the Ohio University Portal is to become. Intrinsically, a portal should not be considered as just a collection of transactions, information and links to content; it should be thought of as a framework toward building the online relationship Ohio University wants to establish with all users. In an article by Susan Heid, titled All Roads Lead to Portal1 she writes: As student populations grow and automated self-service becomes the norm, the information systems the school implements actually become the personality modules of the institution. If the personality module failsif we cant remember who you are or dont remember that youre marriedwere not convincingly there, he maintains, and it weakens the sense of having a real relationship. As in any relationship, the keys to building a strong foundation include dependency, trust, familiarity and, most importantly, communication. During the many portal requirements gathering sessions, the most common request was the need to effectively communication with the user, and to do so in a way that best served that user. This is supported as Heid continues with input from John Savarese, a portal expert: Another concrete sign of portal maturity, says Savarese, is to empower the person receiving a message to choose the medium for delivery, rather than leave the choice to the person sending it How should that happen? It ought to happen the way students want it to happen, says Savarese. The portal should offer, How do you want urgent messages delivered to you? Then students can indicate a text-message or e-mail address, or request an automated voicemail message to a particular number. Few schools have reached that level of unified messaging. A portal will bring a fundamental shift to not only how data will be accessed by users, but just as important, how data will be managed by the administration. Governance will be key in managing all aspects of OHIOs portal. A portal should not be considered an IT responsibility; but must involve a broader representation of the OHIO community. Champions should be sought out who can be a part of the shaping of this portal. Champions can be identified as those who get it, who now understand the depth and the breadth of the project scope at hand. It was clear, during the many meetings and discussions, that the OHIO community is excited about how a portal can transform information and content delivery across the University. As part of the portal project, the Portal Project team needs to not only have a well defined project plan but they need to also fully understand the impact a portal will have on the University.
All Roads Lead to Portal, Campus Technology, Susan D. Heid, May 01, 2007 Proprietary and Confidential: Ohio University Page 36 of 47
Rufus Initiative
APPENDIX A PORTAL COMMITTEE

Name Linda Lockhart Patrick ORegan Jenny Hall-Jones Colleen Carow Tracy Galway Sean OMalley Jay Beam Title Manager, Communications, Regional Campuses & Outreach Assoc Dir Info Systems, Admissions Assistant Dean of Student Affairs Dir External Relations, Russ College of Engineering Director Advancement Special Projects OIT Communications Manager Email address
Director of Web Services & Departmental Solutions, OIT
Page 37 of 47
Rufus Initiative
APPENDIX B PORTAL SESSIONS AND ATTENDEES

Session University Communication and Marketing Attendees Stacey Stewart, Multi-media Designer/Information Architect Dave Hannum, Web Analyst/Programmer Renea Morris, Executive Director, UCM Mark Krumel, Senior Director of Creative Services, UCM Jay Beam, Director of Web Services & Dept Solutions, OIT Ed Yost, Exec Dir Grad Exec Education Israel Urieli, Assoc Prof Mech Engineering Herman Butch Hill, Dir Cutler Scholars, Prof EE Kevin Berisso, Asst Prof Industrial Tech Ken Sampson, Assoc Dean, Russ College of Engineering Colleen Carow, Dir, External Relations, Russ College of Engineering Jay Beam, Director of Web Services & Dept Solutions, OIT Chris Mercer, CIBER, Inc. Patrick ORegan, Assoc Dir Info Systems, Admissions David Axsom, Asst Dir Admissions/Func Lead Bob Burlow, Asst Registrar/Func Lead Patrick Beatty, Assoc Registrar/Func Lead Jill Harris, Emergency Programs Coord Kim Trout, Assoc Bursar/Func Lead SF Jill Lallier, Assoc Dir Operation/Func Lead FA Sondra Williams, Director Student Financial Aid Shelley Ruff, SIS Program Director, OIT Tanya Barnett, Dir Communication, Univ College Tracy Galway, Dir Advancement Special Projects Jay Beam, Director of Web Services & Dept Solutions, OIT Chris Mercer, CIBER, Inc. Cheryl Sickels, HR Records Specialist, University Human Resources Renee Perry, IT Acquisitions Mngr, OIT Valerie Denney, Admin Assoc, Dining Services Bruce Tong, Software Engineer, OIT Nathan Watson, Programming Analyst, OIT Jay Beam, Director of Web Services & Dept Solutions, OIT Sue Carano, Oracle App Sys Admin, OIT
Faculty
Administrative Staff
HR/Employees
Page 38 of 47
Rufus Initiative
Students
Technology
Security Navigation
Library
Tiffani Reeves, FreshmanHealth Care Admin Jesse W. Neader, Junior-Communication Scott Sheeler, GradSpecial Education Michael Adeyanja, GradPublic Admin Chauncey Jackson, Senior-Political Science Cassie Hauber, Freshman-Health Services Admin Michael J. Ward, Senior-Music Education Jay Beam, Director of Web Services & Dept Solutions, OIT Tom Perrone, Senior-Business(MIS) Nathan Galieti, Grad-Aviation P.J. Guthrie, Grad-Nursing Jenny Hall-Jones, (staff) Student Affairs Matt Hyclak, Senior Systems Administrator, OIT Hyun Park, Web Developer, OIT Allen Gattis, Server Administrator, OIT Don Pendergast, Software Architect/SIS Tech Lead Dick Piccard, Web Resource Manager, OIT Dave Hannum, Web Analyst/Programmer/Tech Lead OIT Kevin Kimbrough, Oracle DBA, OIT Scott Pack, Information Security Analyst, OIT Brian Bowe, , Director, Business Applications & Information Services, OIT Jay Beam, Director of Web Services & Dept Solutions, OIT Matthew Dalton, Director, Information Technology Security, OIT Jay Beam, Director of Web Services & Dept Solutions, OIT Patrick ORegan, Assoc Dir of IS, Admissions Dave Hannum, Web Analyst/Programmer/Tech Lead OIT Stacey Stewart, Multi-media Designer/Information Architect Mark Krumel, Senior Director of Creative Services, UCM Jay Beam, Director of Web Services & Dept Solutions, OIT Mark Mace, Systems Administrator, Library David Dudding, Director, Library IT Carrie Preston, Continuing Resources/Database Maintenance Catalog Librarian Gary Ginther, Fine Arts Librarian Annette Talbert, Circulation Services Tim Smith, Reference Department Jay Beam, Director of Web Services & Dept Solutions, OIT
Page 39 of 47
Rufus Initiative
Regional Campuses
BI/Data Warehouse
Academic Technology
Chillicothe Campus Richard Bebee, Dean Mike Lafreniere, Associate Dean Patty Griffith, Information Technology Services Jaime Lowe, Student Services TJ Eveland, Student Recruitment Charlotte McManus, Assoc Director of Nursing Zanesville Campus Jim Fonseca, Dean Raj Tamburaj, Interim Associate Dean Pam Sealover, Assoc Director Nursing Karen Ragsdale, Admissions Monica Jones, Student Services Jason Howard, Student Services Larry Tumblin, Dir, IT Services Eastern Campus Rich Greenlee, Dean Kevin Chenoweth, Student Services Southern Campus Bill Willan, Dean Dave Lucas, Interim Assoc Dean Robert Pleasant, Student Services Nicole Pennington, Assoc Dir Nursing Jay Beam, Director of Web Services & Dept Solutions, OIT Lancaster John Furlow, Dean Candice Thomas-Maddox, Interim Assoc Dean Pat Fox, Student Services Paul Allen, Dir. Computer Services & Instructional Technology Brian Bowe, Director, Business Applications & Information Services, OIT Colleen Egan, CIBER, Inc. Jay Beam, Director of Web Services & Dept Solutions, OIT Dave Matthews, Director Academic Technology, OIT Candice Morris, Educational Testing Center Administrator, Academic Technology Paul ODonnell, Interactive Web/Multimedia Designer, Academic Technology Joan Wigal, Assoc Dir, Academic Technology Sarah Rist, Lab Manager And Training Specialist, Academic Technology Jay Beam, Director of Web Services & Dept Solutions, OIT
Page 40 of 47
Rufus Initiative
Portal Committee
OIT Administration Student Affairs
University College
Linda Lockhart, Manager, Communications, Regional Campuses & Outreach, UCM Tanya Barnett, Dir Comm, UC Patrick ORegan, Assoc Dir Info Sys, Admissions Jenny Hall-Jones, Asst Dean of Student Affairs Colleen Carow, Dir External Relations, Russ College of Engineering Tracy Galway, Dir Advancement Special Projects Sean O'Malley, OIT Communications Manager Chris Mercer, CIBER, Inc. Jay Beam, Director of Web Services & Dept Solutions, OIT Brice Bible, CIO Jay Beam, Director of Web Services & Dept Solutions, OIT Jacki Legg, Interim Director Student Health Services Char Kopchic, Asst Dean of Students, Campus Programs Tom Korvas, Dir Career Services Jenny Hall-Jones, Asst Dean of Student Affairs Sujit Chemburkar, Exec Dir Baker Conf Services, Univ Events Christine Sheets, Exec Dir Housing, Student Affairs Jay Beam, Director of Web Services & Dept Solutions, OIT Wendy Merb-Brown, Director LC Programs Cynthia King, Asst Dean, AAC Library David Descutner, Dean University College Jenny Klein, Dir Allen Student Help Center, Orientation Tanya Barnett, Dir Communication, Univ College Jay Beam, Director of Web Services & Dept Solutions, OIT
Page 41 of 47
Rufus Initiative
APPENDIX C - RESOURCES
Portal Vendors and Service Providers to Higher Education (partial list)
Vendor uPortal Luminous (Pipeline / Sungard SCT) Oracle/PeopleSoft Enterprise Portal Oracle Application Portal 10g Blackboard Microsoft Sharepoint Datatel Unicon Jenzabar Campus Cruiser Vignette Application Liferay CampusEAI
Notes http://www.jasig.org/uportal http://sungard.com/ http://www.oracle.com/applications/portals/enterprise/enterprise-portal.html http://www.oracle.com/technology/products/ias/portal/index.html www.blackboard.com/ http://sharepoint.microsoft.com/Pages/Default.aspx Datatels ActiveCampus Portal runs on top of Microsoft SharePoint http://www.datatel.com/products/products_a-z/activecampus_portal.cfm http://www.unicon.net/ (Provides implementation services for uPortal) http://jenzabar.net/products.aspx?id=136 http://www.timecruiser.com/ http://www.vignette.com http://www.liferay.com/ http://www.campuseai.org/
Examples of Portals and Demo Sites Institution Kwantlen Colorado State Wayne State Lake Michigan State Northeastern Wentworth Alabama Clayton State Cornell Pepperdine University Moody Bible Institute Bellevue University Tallahassee CC URL https://my.kwantlen.ca http://rampoint.colostate.edu/ https://pipeline.wayne.edu http://wavelink.lakemichigancollege.edu/ http://myneu.neu.edu/ http://lconnect.wit.edu/ http://mybama.ua.edu/ http://swan.clayton.edu http://guest.uportal.cornell.edu/uPortal/render.uP https://wavenet.pepperdine.edu/psp/paprd89/EMPLOYEE/E MPL/h/?tab=PAPP_GUEST https://my.moody.edu/psp/PA90PD/EMPLOYEE/EMPL/h/?t ab=PAPP_GUEST https://bruin.bellevue.edu/psp/PBVUNP/EMPLOYEE/EMPL/ h/?tab=PAPP_GUEST https://presentations.tcc.fl.edu/demo/default.aspx
Proprietary and Confidential: Ohio University Login/Password guest/guest click demo links wsuguest/warrior lmcstudent/lmc neustudent/husky sct_student/student107sct_f aculty/faculty_107 click guest sign in click "Guest Account" Demo/demo CHANSEN3/ DR&~~WQF%$*382 n/a n/a n/a
Page 42 of 47
Rufus Initiative
Enterprise Portal Requirements n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a n/a
Tarrant Count CC Greenville Technical College UW Madison U Toronto USC UNH Dillard University Mount Hood CC Elizabethtown College UVA UCLA University of Minnesota University at Buffalo University of Washington University of Texas at Austin JA-SIG UPortal Princeton University George Mason University
https://prod.campuscruiser.com/q?pg=home_welcome&cx= 22.142 http://prod.campuscruiser.com/PageServlet?pg=home_welc ome&cp=168 https://mydemo.doit.wisc.edu/portal/render.userLayoutRootNode.uP https://portal.utoronto.ca/webapps/portal/frameset.jsp http://online.uscny.edu/ https://blackboard.unh.edu/webapps/portal/frameset.jsp https://mydu.dillard.edu/ics/Welcome/ https://my.mhcc.edu/ics https://ecweb.etown.edu/exweb/login.asp https://sisuva.admin.virginia.edu/psp/epprd/EMPLOYEE/EM PL/h/?tab=PAPP_GUEST http://my.ucla.edu/ http://onestop.umn.edu/ http://www.buffalo.edu/aboutmyub/ http://www.washington.edu/protos/myuw/demo/ http://utdirect.utexas.edu/utdirect/ http://www.mis2.udel.edu/ja-sig/portal.html http://asigdev.princeton.edu:82/portal/ http://gmucommunity.blackboard.com/
Page 43 of 47
Rufus Initiative
Portal Reference Articles and Whitepapers
General Portals 101 A portal guide http://www-01.ibm.com/software/websphere/portal/portals101/ What is a Web Portal and how it is different from a website? http://www.atlanticwebfitters.ca/Home/WhatisaWebPortal/tabid/95/Default.aspx What is a Portal? http://www.gobcantabria.es/portalHelp/en/__inl.inline.true/__inl.topic.welcport_htm/__inl.h tml What is a portal, really? http://compnetworking.about.com/od/internetaccessbestuses/l/aa011900a.htm Branding and Design Consider User Satisfaction in Designing Web-Based Portals http://net.educause.edu/ir/library/pdf/eqm0315.pdf Creating a Successful Web Portal http://download.backbase.com/rich-portal/Whitepaper-Creating-a-Successful-WebPortal.pdf Content Management and Navigation Content Management: The Keys to Portal Success http://www.silkroad.com/SiteGen/Uploads/Public/SRT/Whitepaper/Keys_to_Portal_Success .pdf Human-Centric design of Percipient Knowledge Distribution Service http://portal.acm.org/citation.cfm?id=1434395 Web Content Management Systems in Higher Education http://net.educause.edu/ir/library/pdf/eqm0325.pdf Content Strategy: The Philosophy of Data http://www.razorfish.com/download/articles/ContentStrategy_RachelLovinger.pdf The Discipline of Content Strategy http://www.alistapart.com/articles/thedisciplineofcontentstrategy Best Practice The Campus Portal: 5 Best Practices http://campustechnology.com/Articles/2008/09/5-Best-Practices.aspx?p=1
Page 44 of 47
Rufus Initiative
All Roads Lead to Portal http://campustechnology.com/Articles/2007/05/All-Roads-Lead-to-Portal.aspx?p=1 Is Your University Portal Up to Snuff? http://campustechnology.com/Articles/2008/04/Is-Your-University-Portal-Up-toSnuff.aspx?p=1 Governance Winning Strategies for Portal Governance http://www.ibm.com/developerworks/websphere/library/techarticles/0904_behl/0904_behl.h tml Defining a Governance Model for Portals http://www.infosys.com/IT-services/systems-integration/white-papers/portals-governancemodel.pdf A Winning Portal Governance Strategy https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5d939290-0201-00105781-fe3840b45557 What is Governance? http://technet.microsoft.com/en-us/library/cc263356.aspx Vendor Evaluation Assessing Risks in Selecting an Enterprise Portal Vendor http://www85.homepage.villanova.edu/timothy.ay/DIT2160/Portal/AssessingRisk.pdf Portal Evaluation Criteria Update: Getting to What Matters http://download.microsoft.com/download/4/7/3/473B072C-5D69-4B7C-B0FD2607813413C3/Evaluation_Criteria_for_Enterprise_Portals.pdf
Applications and Tools Freemind Mindmapping Application http://freemind.sourceforge.net/wiki/index.php/Main_Page
Page 45 of 47
Rufus Initiative
OVERVIEW OF RUFUS INITIATIVE PROJECT

The Rufus Initiative: Student Data When and Where You Need It is part of the overall administrative system renewal project at Ohio University that is set to transform services to enhance performance of faculty and staff as they strive to improve recruitment, academic success and overall experience of OHIO students. Working in partnership with Oracle and the PeopleSoft Campus Solutions application, along with the implantation partnership with CIBER, Inc., the RUFUS Initiative will enable fundamental changes throughout the University involving areas related to: admissions and recruitment career services data warehouse (reporting) grading housing self-service student financial aid advising course scheduling and curriculum degree audit registration student records student accounts student health
Further information on the project can be found online at the following link: http://www.ohio.edu/sisproject/
Page 46 of 47
Rufus Initiative
CONSULTING PARTNERSHIP
CIBER is proud to be a partner with the OHIO University and the RUFUS Initiative, supporting the implementation of the Oracle/PeopleSoft Campus Solutions student information system. CIBER (NYSE: CBR) is a leading international system integration consultancy with superior value-priced services for both private, government and higher education sector clients. CIBERs services are offered on a project or strategic staffing basis, in both custom and enterprise resource planning (ERP) package environments, and across all technology platforms, operating systems and infrastructures. CIBER, Inc. 5251 DTC Parkway Suite 1400 Greenwood Village, CO 80111 Tel: (303) 220.0100 Fax: (303) 220.7100 Toll Free: (800) 242.3799 www.ciber.com
Page 47 of 47

OHIO Ciber Portal Requirements Report

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

OHIO Ciber Portal Requirements Report

Enviado por

Direitos autorais:

Formatos disponíveis

OHIO UNIVERSITY RUFUS INITIATIVE

ENTERPRISE PORTAL REQUIREMENTS INITIATIVE

Enterprise Portal Requirements

Marc Troeger Marc Troeger Kerensky Rowan

1st draft Final Draft

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

OVERVIEW OF RUFUS INITIATIVE PROJECT............................................................................................... 46 CONSULTING PARTNERSHIP ............................................................................................................................. 47

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

State of Portal in Higher Education

Enterprise Portal Requirements

4. REQUIREMENTS AND FINDINGS

General Portal Demonstration

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

Content Requirements Identified

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

D D D R i.e. student newspaper, departmental newsletters, etc

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

i.e. alerts from an emergency notification system pushed to the portal

D D D i.e. content has been revised on a pagelet or article.

Enterprise Portal Requirements

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

Enterprise Portal Requirements

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

4.3.3 Monitoring and Reporting Tools

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

Navigation Requirements Identified

i.e. emergency alert pagelet

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

R R R R D R Such as Loadrunner Such as word, excel, pdf

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

4.5.1 System Requirements and Infrastructure

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

Integrate with existing Load-balancing hardware

Enterprise Portal Requirements

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements

Proprietary and Confidential: Ohio University

Enterprise Portal Requirements