ohio ciber portal requirements report

7/31/2019 OHIO Ciber Portal Requirements Report

1/47

OHIOUNIVERSITY

RUFUSINITIATIVE

ENTERPRISE PORTAL REQUIREMENTS INITIATIVE

Prepared by:Marc Troeger, CIBER, Inc.

Kerensky Rowan, CIBER, Inc.

July 2009


2/47

Rufus Initiative Enterprise Portal Requirements

Proprietary and Confidential: Ohio University Page 2 of 47

1.CHANGE HISTORYVERSION DATE CHANGED BY CHANGE

1 06/23/2009 Marc Troeger 1stdraft

2 7/16/2009 Marc TroegerKerensky Rowan

Final Draft


3/47



2.CONTENTS1. CHANGE HISTORY ......................................................................................................................................... 2

2. CONTENTS ........................................................................................................................................................ 3

3. OVERVIEW ....................................................................................................................................................... 4

4. REQUIREMENTS AND FINDINGS ............................................................................................................... 7

4.1 GENERAL PORTAL DEMONSTRATION .......................................................................................................... 74.2 BRANDING................................................................................................................................................... 84.3 CONTENT................................................................................................................................................... 10

4.3.1 Portal Content ..................................................................................................................................... 104.3.2 Search .................................................................................................................................................. 154.3.3 Monitoring and Reporting Tools .................... ........... ........... ........... .......... ........... ........... ........... ......... 17

4.4 NAVIGATION ............................................................................................................................................. 184.5 TECHNOLOGY............................................................................................................................................ 20

4.5.1 System Requirements and Infrastructure ............................................................................................. 224.5.2 Scalability ............................................................................................................................................ 234.5.3 Services and support ............................................................................................................................ 24

4.6 SECURITY AND ROLE MANAGEMENT ........................................................................................................ 265. SUMMARY AND RECOMMENDATIONS ................................................................................................. 29

5.1 OUPORTAL DEFINITION ........................................................................................................................... 295.2 BRANDING AND DESIGN............................................................................................................................. 295.3 CONTENT AND NAVIGATION ..................................................................................................................... 305.4 TECHNOLOGY AND INTEGRATION ............................................................................................................. 315.5 SECURITY.................................................................................................................................................. 315.6 DEPLOYMENT AND TIMETABLE................................................................................................................. 325.7 REPORTING AND TRACKING ...................................................................................................................... 335.8 RESOURCE SUPPORT AND SKILL SETS ....................................................................................................... 335.9 TRAINING .................................................................................................................................................. 335.10 SYSTEM SUPPORT AND MAINTENANCE ..................................................................................................... 345.11 GOVERNANCE ........................................................................................................................................... 345.12 KNOWLEDGE TRANSFER............................................................................................................................ 355.13 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) ........................................................................ 42Examples of Portals and Demo Sites .............................................................................................................................. 42Portal Reference Articles and Whitepapers ..................................................................................................................... 44

OVERVIEW OF RUFUS INITIATIVE PROJECT............................................................................................... 46

CONSULTING PARTNERSHIP ............................................................................................................................. 47


4/47



3.OVERVIEWIn 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 OUto 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 anddeployment 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). Theagenda for each of these sessions will be to:

1. Explain the general concept of a portal2. Provide examples of how portals are used at various universities around the country3. Identify requirements specific to the offices and departments represented4. 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 ofcommercially 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:


5/47



During the sessions, the participants will be asked to focus on the content they would expect tosee as part of the portal. Content types will be represented in three different categories:

Content Type Description ExamplesTransactions Transactions related to a specific

user within a specific role

Registering for classes, checking

financial aid, reviewing benefits,downloading pay stubCommunication Communication related to a

specific user or to a specific userrole; a communication isconsidered time sensitive andrelative to a specific point-in-timeor event

Holds and messages directed to theuser; alerts and special noticesdirected to user roles; emergencynotifications

Information Information is less time-sensitiveand covers a broader scope andaudience. Information does not

have to be directed to a specificrole.

Community calendar, course catalog,weather 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 RufusInitiative.

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.


6/47



State of Portal in Higher Education

Enterprise Portals are proving their value within large colleges and universities, becoming fully-

integrated 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, fosterstudent, 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 processcontrols, 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 Web-

savvy generation joins the work force. Enterprise portals are beginning to embrace socialnetworking 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 socialnetworking 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 willwant 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 forintegrating existing applications and information stores, and creating a flexible infrastructure that can

adapt to emerging needs and requirements.


7/47



4.REQUIREMENTS AND FINDINGSThe 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. Branding2. Content3. Navigation4. Technology5. 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 theconsultants, with follow-up ratings made by OHIO staff.

4.1 General Portal Demonstration

Questions:

1. Provide a brief history of your company including years in business andacquisitions.

2. Give an overview of our companys products and services, highlighting thekey products your company offers.

3.

As part of your application demonstration, give a 360 degree Day-in-the-Life overview of your application as it relates to:

a. Studentsb. Facultyc. Staffd. Parentse. Guestsf. Vendors

4. Show examples of you application operating using various browsers. Providedemonstrations of your applications mobile capabilities. Include various

mobile formats such as: iPhone, Smartphone, small-screen browsers.


8/47



4.2 BrandingBranding is critical to creating identity and environment in a portal. While branding

should be controlled and consistent, the branding itself should not impede the commonfact 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, yetfunctional form

Branding curates content, defines the style, look and feel for theinteraction/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 thepurpose

Branding Requirements Identified

Requirement OHIO CNSLT NotesAllows full customization of look andfeel of portal design

RColors, images, logos, links,shades, shaping, tabs, fonts

Supports placement of interactivemedia

DVideos, slideshows, audio,

Branding is locked into templates andcan only be updated by key individuals

R

Is software agnostic in accepting amultitude of media formats

Ri.e. .jpg, .gif, .png, .mp4, etc.

Is browser agnostic; should workacross various web browsers

Ri.e. Firefox, Opera, Chrome,mobile browsers

Allows for highly configurable brandingto conform to University imagestandards to control pages andpagelets

R

Must allow the University tomanage and control style andbranding directly

CSS compliantD

Allows full flexibility for designand branding

Allows for user configured style sheetsto control pages and pagelets D

Allows users to select alternate stylesheets, based on user role/security?

D

Allows for importing of content fromexternal HTML editors

R

Recognizes standard HTML formattingtags

R


9/47



Application includes an HTML editor,allowing for direct editing

R

Provides tools within the application tovalidate and identify errors within HTMLscripts

R

Provides formatting to accommodatemobile hardware

R iPhone, Smartphone, small-screen cell phonesSupport for ADA compliance standards R Americans with Disabilities ActAllows for various web designprogramming languages

DAJAX, JAVA, Pearl, php, etc.

Allows for co-branding based uponuser role and affiliations

D

Allows for co-branding with externalsites

D

While the main Branding wrap islocked, other individuals can update co-

branding areas

DPortal pages for schools,departments, organizations

affiliates with OHIOProvides an authorization system thatrequires manager approval of brandingchanges made by another user, beforeit is published

D

Additional Questions:

1. Provide a demonstration, showing the branding capabilities of yourapplication.

2. Give an overview on how style templates and style sheets can be used formaximum branding flexibility.

3. Describe how your product applies and enforces style restrictions andconstraints.4. Explain any branding restrictions your application has.5. Provide examples in how your application maintains ADA compliance.


10/47



4.3 ContentIn 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 thefooter 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 OHIO CNSLT NotesContent FeaturesProvides Instant messaging capability D

Provides voice chat capability D i.e. help desk

Integrates with VOIP applications D i.e. SkypeProvides scrolling news/informationtickers

D Promotes University news,events, alerts, etc

Provide delivered pagelets withfunctional tools and 3rd party integrationsuch as calculators, notepads, stickies,Weather Bug, Google maps, newsfeeds, etc

D

Provide the ability to print portal contentin printer friendly format

D

Allows for customizable content without

user having to log in

D i.e. OHIO has this feature now

for prospective students toindicate major and activityinterests through drop downs tocreate a customized portalfocusing on those interests

Allows interfacing with content fromother portal applications

D i.e. 3rdparty Alumni portal

Supports creation of content that canalso be rendered on mobile hardware

R i.e. iPhones, Smartphone,small-screen cell phones

Provides mobile features that identifiesspecific mobile hardware logging and is

automatically formatted to meet thedisplay requirements of that hardware.

D

Provides ability to deliver BI content,such as KPIs in a secure, graphicalenvironment

D

Provide a bookmarking feature forinternal and external content

R


11/47



Allow guests to RSVP to invitations toevents regardless whether he/she is aregistered user

D

Provide gateway for secure, financialtransactions

R

Provide ecommerce functions forbookstore or alumni products

D

Easily allows for third-party integrationof point-of-purchase providers

Provide security for limited accessportals.

R i.e. At OHIO, students cangrant access to parents to viewand pay bill through CASHNet.A parent portal provides accesswhere students can grantparents access to pay theirbills, look at grades, etc

Provide an event management system,tied into calendaring feature

D

Provides To Do functions that allowuser to manage personal as To Do lists.

R Personal To Do items

Provides a comprehensive To Do listthat draws task items from severalsources and combines them into onelist

R Administrative To Do items

Includes tools to allow portal content topush content through external APIssuch as Facebook or MySpace

D

Customizable calendar that allowscontent from other external calendars tobe pushed into one comprehensiveuser calendar with features to filtercontent by user

D

Allow students to create their own portalpage and content for student groupsand organizations

D

Provide features that create aCraigslist-type bulletin board whereusers can post sale/wanted ads (i.e.

textbooks, rooms for rent, etc)

D

Provide tools and features for creatingand promoting polls and surveys

D

Editing ToolsProvides editing tools to easily allowcreation of content in the form of pages,tabbed sections, pagelets and othersites

R


12/47



Provides an easy to use preview tool toreview content in WYSIWYG format,before publishing

D

Includes tools to publish content asmagazine/newsletter formats

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

Provides project management trackingfor content development

D

Includes the ability for contentdevelopers to record notes and versionupdate comments that are directlyrelated to the content

R

Provide role-based security that defineswhohas access to edit/manage content

R

Provide role-based security that defineshow a user has access to edit/managecontent

R i.e. view only, update only,creation only, etc.

Provides easy to use editing tools forusers with minimal skill set to add orupdate content

R i.e. to add/update portal content

Provides built in spell checker D

Supports the copying/moving of contentfrom one portal site to another

R

Provides tools to optimize/reformatuploaded content such aspictures/videos for optimal performance

R

Allows assigned user to createcontent/pagelets made up of internal

and external hyper links

R

Provide the ability to publish content forfuture dates

R

Provides workflow features that requiremanager approval of content created byanother user before it is published.Workflow should also includenotification features.

R

Provides automated notificationworkflow to manage approval system

R

Provide feature that allows

customizable ads or badges thatvisually promotes critical transactions,notices or events

D i.e. Give to Current Campaign

Promote sporting or theaterevent and other alerts orannouncements

Supports various interface/APIstandards to external content

R i.e. WeatherBug,Facebook/MySpace streaming,RSS feeds

Easily stores and organizes uploadedcontent

R Pictures, videos, documents,etc.


13/47



Provides tools for building databasequeries into content.

R

Provides delivered integration toOracle/PeopleSoft Campus Solutions

R

Provides delivered integration to Oracle

HR and Finance

R

Provides delivered, single-sign onintegration to Adirondack housingsystem

R

Provides tools to enable single-sign onwith other applications.

R

Alerts/NotificationsProvide an emergency alert notificationsystem through the portal

R

Provides tools to push

information/announcements/alerts tousers via delivery medium of their(users) choice

R

Allows content from other systems to bepushed to the portal, based on userroles, providing highly visual alerts andnotifications

R i.e. alerts from an emergencynotification system pushed tothe portal

Sends notices to administrators/authorswhen content has expired

D

Allow alerts to be created that notifyusers of updates or additions to content

D i.e. content has been revisedon a pagelet or article.

Provides visual/audio alerts to notify ofupcoming To Do/Calendar events

D


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 emergenciesb. Individual student related alerts related to to-do items, holds, late payment

notifications

c. Campus events and activities, including the ability to filter relevantcontent

d. Academic calendar events and deadlines6. Give an overview of the project management tools your application provides.7. Describe the process that occurs when content is revised.


14/47



8. Describe how content is secured and linked to users and roles using yourapplication.

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) yourapplication 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 beenexpired or has not been updated within a certain period of time.

16.Describe how standards are applied to uploaded objects (i.e. images, video, anddocuments), and how it is automatically formatted to meet those standards.17.Give an overview on how uploaded content is managed and stored in yourapplications directory system.


15/47



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 becomea 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; amore 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 andadministrative 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 OHIO CNSLT NotesSupports tagging andlinking metadata tags to forcontent searches

R

Allows for the creation ofindexes to optimize contentsearch

R

Prevents searching onsecure data that user is notauthorized to access

R

Capable of using othersearch engines for portalsearches

R i.e. allows institution to choose to useGoogle or Bing search engines

Provides ability to createpagelets to executesearches within othersystems

R i.e. University Library, campusstaff/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:


16/47


17/47



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 theportal 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 OHIO CNSLT NotesAllows querying of portal databasethrough delivered query tools or via 3rd

party reporting tools

R

Provide tools to monitor links,indentifying dead links withnotifications/alerts

D

Provide reporting tools to track contentas it is developed and throughout thecontent lifecycle

R

Provides tools that monitor useraccess, tracking statistics on usernavigation and content accessed

R

Provide tools to monitor searches

performed while logged into the portal

R


1. Provide an overview of the tools your application has for querying the applicationdatabase.

2. Give examples of the integrated monitoring tools your application uses to trackcontent and user usage.

3. Explain how your application integrates with other major analysis tools.


18/47



4.4 NavigationNavigation 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 andcomprehendible 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 transactionsavailable to the user and even considerations such as multi-lingual and multi-culturalneeds. 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, userrelationship 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):


19/47



Navigation Requirements Identified

Requirement OHIO CNSLT NotesProvides features thatallow for the automaticcreation of navigation or

menus based on contentcreation options

D

Provides the ability toautomatically repair menulinks when content isdeleted/moved

D

Includes tools that validatemenu structure and links

R

Allows user to personalizecontent by selectingcontent to appear that is

relevant to that person

R

Allows user to personalizecontent by movingcontent/pagelets around onpage

R

Allows administers to lockdown content, preventinguser from removing ormoving it

R i.e. emergency alert pagelet

Allows groups/departmentsto create their own portal

sites, independent of themain portal site, yet withall the controls andsecurity.

D This would be sub-portal, (not anadditional tab) that might allow a

department to set up their own portal andcontent, with the overall control ofbranding, content, security residing withmain portal administrators.


1. Give an overview on how the menus and navigation can be generated as content iscreated. Include how that content can be managed and manipulated by

developers.

2. Provide an example, showing how your application updates navigation whencontent is moved or the hierarchy is changed. Include a demonstration of thetools that provide the checks and balances.


20/47



4.5 TechnologyDefining the technical design and architecture of a portal solution can be an extremely

complex activity. Many technical components must work cohesively to harness thefoundational requirements (e.g., security, personalization, search, transaction integration,

content publishing, and collaboration) that need to be leveraged across business solutions.

Technology Requirements Identified

Requirement OHIO CNSLT Notes

Should have the capability totrack login statistics

R

Should follow the traditionalimplementation Path Ability tocreate additional environmentsfor development phases

R

Should provide online helpcapability within the application

R

Should integrate withBlackboard

R

Should integrate withPeopleSoft Campus Solutions

R

Should integrate with OracleFinancials

R

Should integrate withCommonSpot CMS application

R

Should easily integrate with

OHIOs tuition payment vendor,CASHNet

R

Should integrate with CRMproduct of choice

R

Should integrate with any of theCampus legacy applications

R

Should support the major typesof integration protocols such as(XML)

R

Should have some type ofintrusion prevention capability

R

Should provide systemmonitoring capability

R

Should provide systemperformance monitoringcapability

R


21/47



Should have development toolsto migrate configurations andcustomizations betweenenvironments

R

Provide open API capability R

Should provide server sidecaching for increasedperformance

R

Should support RSS feedswithin pagelets

R

Should have the ability to attachand upload any standard filetype

R Such as word, excel,pdf

Should leverage 3rd partyperformance monitoring tools

D

Should leverage 3rd party load

testing software

R Such as Loadrunner


1. Explain the functional components your product delivers. Include other modules andfeatures 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 contentb. XML based contentc. Other Web Servicesd. Other scripting tools and applicationse. 3

rd

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 sets8. 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 thisapplication 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 technologyused in your application.

12.Provide a list of all third-party applications required to meet the requirements of thisRFP.


22/47



4.5.1 System Requirements and Infrastructure

A solid architectural foundation is critical to scalability and manageability. Portalproducts must either have an all-encompassing foundational package or leverage the load

balancing, security, integration, task management and prioritization features ofapplication servers.

System and Infrastructure Requirements Identified


Compatible with existing or NewHardware platform configuration

R

Compatible with existing operatingsystem (either Red Hat Linux orWindows OS)

R

Compatible with existing database

platform (either Oracle or MSSQLServer)

R

Should have DatabaseRedundancy and Failovercapability.

REase of recovering iftheres and outage

Should have ability to tune thevarious components within thearchitecture.

RSuch as Web servers,Application servers,Database servers.

Should support major standardemail applications integration suchas MS Exchange (administrative

email system) and MS Live(student email system)

R

Integrates University email systeminto alerts and messages as aresult of actions occurring withinthe portal, with opt in/out options

R

To Do reminders,update to content inportal, campus alerts,etc.

Should support various internetbrowsers

RInternet Explorer, FireFox, Google Chrome

Should support screen resolutionvariations

R

Should be able to integrate

content from current CMS system R

i.e. Paperthins

CommonSpot CMSapplication

Should provide the ability toaccess the system from a mobiledevice

RiPhone, Palm,Blackberry


23/47




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 networkingconfiguration required to install your application.

4. Give an overview of the backup and restore process. Include recommendations forredundant systems.

4.5.2 Scalability

An ongoing Site Support and Maintenance services naturally follow the implementationof 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


Should afford the ability for futuregrowth in the number of usersaccessing the system

R

Should provide Backup andSystem recovery capability tominimize down time

R

Configurations should allow 24/7accessibility

R

Should have load-balancing,clustering, and failover capabilities. R

Integrate with existingLoad-balancinghardware

Should provide a disaster recoveryplan

R


1. Provide an overview of the growth of your product. Include explanations of releasesthat have involved significant updates and the efforts required to implement them.

2. Explain the hardware and networking requirements your product will need to provide24/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 thesize of OHIO.

4. Provide a typical user response time while navigating through the application. Giveexamples 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 timewithout hindering performance.


24/47



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 willutilize on individual servers, such as memory foot print, hard drive space, and CPUutilization.

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


Should provide procedures forerror reporting and resolutions

R

Should provide procedures for

contacting the vendor helpdesk

R

Should provide access to aknowledge based site to searchfor fixes and solutions

R

Should provide procedures forescalating incidents

R

Should provide 24/7 support R

Should outline an implementationapproach that maximizesmentoring, coaching andknowledge transfer

D

Should provide a schedule forpatches and fixes

R

Should have development tools forimplementation

R

Should provide and automatedimplementation tool and fullrelease or version automatedupgrade tool.

R

Should provide schedule forproposed upgrades and updates

R

Should provide technical and user

trainingR

Should provide documentationsupporting and outlining theconfiguration

R

Should provide networkspecifications outlying systemrequirements and dependencies.

R

Supports HIPAA Compliance R


25/47



Supports PCI Compliance R

Supports FERPA Compliance R

Should provide a dedicatedtechnical resource for initialimplementation

D


1. Provide an overview of the included standard support offering for yourproduct. 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 trainingofferings and the type of training material that is included.

5. Give an overview of the various skill sets and roles required to support yourapplication.

6. Provide an overview of the professional services available to implement andsupport continued ongoing development of your application. Explain howthese services are factored into the licensing and maintenance cost of your

application.


26/47



4.6 Security and Role ManagementImplementing 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 atlogin. 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 shouldseamlessly 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 IdentifiedRequirement OHIO CNSLT Notes

Should integrate with the existingIDMS system

R

Should be SSL compliant R

Should track login history R


27/47



Should provide a notificationmechanism if security breach isdetected

R

Should have to ability to encryptpasswords in the database

R

Should have the capability toreplicate users to multipledatabases

R

Should have the ability toimplement single sign-on

R

Should have the ability to audituser profile deletion ormodifications

R

Should have the ability to audituser profile deletion ormodifications

R

Should seamlessly SSO withPeopleSoft Campus Solutionsystem

R

Should seamlessly SSO withOracle Human Resources system

R

Should seamlessly SSO withOracle Financials system

R

Should seamlessly SSO withBlackboard system

R

Should seamlessly SSO with theDARS system

R

Should seamlessly SSO with theData warehouse applicationchosen

R

Should SSO with OHIOs CMSapplication, CommonSpot

R

Should seamlessly SSO with theCRM system chosen

R

Should seamlessly SSO withCampus Legacy systems

R

Should allow browser to passauthentication cookies to Web

server

R

Should utilize authenticationdomain R

This configuration allowsuser browsers to send asingle-sign on cookie to allthe web servers


28/47




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. Whatissues 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.


29/47



5.SUMMARY AND RECOMMENDATIONS5.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 expectstheir portal to be.

The OHIO portal will integrate information, people, processes and

resources across institutional boundaries to provide a secure, single sign-

on 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 designDuring the information gathering sessions, it was clear that a brand and design isimportant 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 thesame branding theme and branding design guidelines that have been established.

While the look of the portal is important, it was encouraging to hear, during ourmeetings 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, thatUCM should have a role in the initial deployment and ongoing development of theportal 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.


30/47



5.3 Content and NavigationThe 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, thatthere are a variety of applications that students, faculty, staff, parents, prospective

students, alumni and visitors use every day to transact business and gather informationrelated to Ohio University. Frustrations were voiced numerous times due to theinability 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 asthe 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 ordepartmental 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 contentshould 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. Therewas 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 classroomchanges, 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, aportal 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 commonworkflow approval process.


31/47



5.4 Technology and IntegrationThe Vendor should describe its approach for the design, development, testing, and

deployment of automated interfaces between the various ERP systems and other OHIOUniversity systems. The Vendor should be responsible for the development and

deployment of a set of standard inbound and outbound interfaces for OHIO Universityto 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 limitedto):

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 theiradministrative 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 SecuritySecurity 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 orexceed the Universitys security standards.

The Vendor will need to describe in detail, its approach to analyzing, establishing, anddocumenting 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 toconsider, and advantages or disadvantages of proposed approaches. It is equallyimportant 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.


32/47



5.6 Deployment and TimetableIt 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 OHIOPortal is scheduled for August 2010.

Current portal deployment timeline

Milestone DeadlineRequirements Gathering July 16, 2009RFP Draft Complete August 1, 2009Procurement Complete September 2009Implementation Begins October 2009Final Testing and Review July 2010

Go-live Deployment August 2010


33/47



5.7 Reporting and TrackingReporting 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 usagestatistics, 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 SetsUntil 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 whenevaluating vendors and their portal application. This is particularly important when

considering the portal projects tight timeline and implementation schedule.

5.9 TrainingDuring the vendor evaluations, OU will need to require the vendors to provide strategyand 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)


34/47


35/47



5.12 Knowledge TransferKnowledge Transfer between a software application partner and the vendor isparamount to a successful implementation. While "knowledge transfer" itself would

not be a feature requirement, it should be clearly understood by the vendor andcontracted implementation partners that OHIO must be satisfied with the amount ofknowledge 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 mustoccur for a successful outcome. Examples of assumptions could be:

1. Core implementation will be completed on schedule allowing functional testingto be completed by _____________

2. Testing effort will have adequate staff and consultant resources3. Production equipment/software will be delivered and functional4. Identity management system will be deployed

RisksA 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 makecontingency plans to lessen any negative impact. Below are a few examples of risks

involved with a testing strategy:

Risk Impact Contingency

1 Implementation anddevelopment is notcompleted on schedule.

Testing is delayed andnot completed on time.

Contingency 1: The projects progress will becontinually monitored. If the project schedulebecomes a concern, appropriate action will betaken at the time to keep the project on schedule.

Contingency 2: Shorten test phases.

2 Testing personnelshortage

Testing timetable maysuffer

Identify and train a backup testers

3 Not enough time to test Testing timetable maysuffer

Prioritize testing to ensure application functionalityworks for critical and major business processes.


36/47



6.CONCLUSIONWhile 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 aframework toward building the online relationship Ohio University wants to establish with all

users. In an article by Susan Heid, titledAll 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 withthe 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 asimportant, 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 besought 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.

1 All Roads Lead to Portal, Campus Technology, Susan D. Heid, May 01, 2007


37/47



APPENDIX APORTAL COMMITTEE

Name Title Email address

Linda Lockhart

Manager, Communications, Regional

Campuses & OutreachPatrick ORegan Assoc Dir Info Systems, Admissions

Jenny Hall-Jones Assistant Dean of Student Affairs

Colleen CarowDir External Relations, Russ College ofEngineering

Tracy Galway Director Advancement Special Projects

Sean OMalley OIT Communications Manager

Jay BeamDirector of Web Services & DepartmentalSolutions, OIT


38/47



APPENDIX BPORTAL SESSIONS AND ATTENDEES

Session Attendees

University Communication andMarketing

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

Faculty 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.

Administrative Staff 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.

HR/Employees Cheryl Sickels, HR Records Specialist, University HumanResources

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


39/47



Students 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

Technology 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

Security Matthew Dalton, Director, Information Technology Security,OIT

Jay Beam, Director of Web Services & Dept Solutions, OIT

Navigation 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

Library 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


40/47



Regional Campuses 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 NursingZanesville 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 ServicesEastern Campus

Rich Greenlee, Dean Kevin Chenoweth, Student ServicesSouthern 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, OITLancaster

John Furlow, Dean Candice Thomas-Maddox, Interim Assoc Dean Pat Fox, Student Services Paul Allen, Dir. Computer Services & Instructional Technology

BI/Data Warehouse Brian Bowe, Director, Business Applications & InformationServices, OIT

Colleen Egan, CIBER, Inc. Jay Beam, Director of Web Services & Dept Solutions, OIT

Academic Technology 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


41/47



Portal Committee Linda Lockhart, Manager, Communications, RegionalCampuses & 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 ofEngineering 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

OIT Administration Brice Bible, CIO Jay Beam, Director of Web Services & Dept Solutions, OIT

Student Affairs 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

University College 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


42/47



APPENDIX C-RESOURCES

Portal Vendors and Service Providers to Higher Education (partial list)

Vendor NotesuPortal http://www.jasig.org/uportalLuminous (Pipeline /Sungard SCT)

http://sungard.com/

Oracle/PeopleSoftEnterprise Portal

http://www.oracle.com/applications/portals/enterprise/enterprise-portal.html

Oracle Application Portal10g

http://www.oracle.com/technology/products/ias/portal/index.html

Blackboard www.blackboard.com/Microsoft Sharepoint http://sharepoint.microsoft.com/Pages/Default.aspx

Datatel Datatels ActiveCampus Portal runs on top of Microsoft SharePointhttp://www.datatel.com/products/products_a-z/activecampus_portal.cfmUnicon http://www.unicon.net/ (Provides implementation services for uPortal)Jenzabar http://jenzabar.net/products.aspx?id=136Campus Cruiser http://www.timecruiser.com/Vignette Application http://www.vignette.comLiferay http://www.liferay.com/CampusEAI http://www.campuseai.org/

Examples of Portals and Demo Sites

Institution URL Login/Password

Kwantlen https://my.kwantlen.ca guest/guestColorado State http://rampoint.colostate.edu/ click demo linksWayne State https://pipeline.wayne.edu wsuguest/warriorLake Michigan State http://wavelink.lakemichigancollege.edu/ lmcstudent/lmcNortheastern http://myneu.neu.edu/ neustudent/huskyWentworth http://lconnect.wit.edu/ sct_student/student107sct_f

aculty/faculty_107

Alabama http://mybama.ua.edu/ click guest sign inClayton State http://swan.clayton.edu click "Guest Account"Cornell http://guest.uportal.cornell.edu/uPortal/render.uP Demo/demoPepperdine University https://wavenet.pepperdine.edu/psp/paprd89/EMPLOYEE/E

MPL/h/?tab=PAPP_GUEST

CHANSEN3/DR&~~WQF%$*382

Moody Bible Institute https://my.moody.edu/psp/PA90PD/EMPLOYEE/EMPL/h/?tab=PAPP_GUEST

n/a

Bellevue University https://bruin.bellevue.edu/psp/PBVUNP/EMPLOYEE/EMPL/h/?tab=PAPP_GUEST

n/a

Tallahassee CC https://presentations.tcc.fl.edu/demo/default.aspx n/a


43/47



Tarrant Count CC https://prod.campuscruiser.com/q?pg=home_welcome&cx=22.142

n/a

Greenville TechnicalCollege

http://prod.campuscruiser.com/PageServlet?pg=home_welcome&cp=168

n/a

UW Madison https://my-demo.doit.wisc.edu/portal/render.userLayoutRootNode.uP

n/a

U Toronto https://portal.utoronto.ca/webapps/portal/frameset.jsp n/aUSC http://online.uscny.edu/ n/aUNH https://blackboard.unh.edu/webapps/portal/frameset.jsp n/aDillard University https://mydu.dillard.edu/ics/Welcome/ n/aMount Hood CC https://my.mhcc.edu/ics n/aElizabethtown College https://ecweb.etown.edu/exweb/login.asp n/aUVA https://sisuva.admin.virginia.edu/psp/epprd/EMPLOYEE/EM

PL/h/?tab=PAPP_GUEST

n/a

UCLA http://my.ucla.edu/ n/aUniversity of Minnesota http://onestop.umn.edu/ n/aUniversity at Buffalo http://www.buffalo.edu/aboutmyub/ n/a

University ofWashington http://www.washington.edu/protos/myuw/demo/n/a

University of Texas atAustin

http://utdirect.utexas.edu/utdirect/ n/a

JA-SIG UPortal http://www.mis2.udel.edu/ja-sig/portal.html n/aPrinceton University http://asigdev.princeton.edu:82/portal/ n/aGeorge MasonUniversity

http://gmucommunity.blackboard.com/ n/a


44/47



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.html

What is a portal, really?http://compnetworking.about.com/od/internetaccessbestuses/l/aa011900a.htm

Branding and Design

Consider User Satisfaction in Designing Web-Based Portalshttp://net.educause.edu/ir/library/pdf/eqm0315.pdf

Creating a Successful Web Portal

http://download.backbase.com/rich-portal/Whitepaper-Creating-a-Successful-Web-

Portal.pdf

Content Management and Navigation

Content Management: The Keys to Portal Successhttp://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 Educationhttp://net.educause.edu/ir/library/pdf/eqm0325.pdf

Content Strategy: The Philosophy of Datahttp://www.razorfish.com/download/articles/ContentStrategy_RachelLovinger.pdf

The Discipline of Content Strategyhttp://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


45/47



All Roads Lead to Portalhttp://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-to-

Snuff.aspx?p=1GovernanceWinning 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-governance-

model.pdf

A Winning Portal Governance Strategy

https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5d939290-0201-0010-5781-fe3840b45557

What is Governance?http://technet.microsoft.com/en-us/library/cc263356.aspx

Vendor Evaluation

Assessing Risks in Selecting an Enterprise Portal Vendorhttp://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-B0FD-

2607813413C3/Evaluation_Criteria_for_Enterprise_Portals.pdf

Applications and Tools

Freemind Mindmapping Application

http://freemind.sourceforge.net/wiki/index.php/Main_Page


46/47



OVERVIEW OF RUFUSINITIATIVE 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 toenhance 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 advising career services course scheduling and curriculum data warehouse (reporting) degree audit grading registration housing student records

self-service

student accounts student financial aid student health

Further information on the project can be found online at the following link:

http://www.ohio.edu/sisproject/


47/47


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. CIBERsservices 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 1400Greenwood Village, CO 80111

Tel: (303) 220.0100

Fax: (303) 220.7100Toll Free: (800) 242.3799

www.ciber.com

ohio ciber portal requirements report

Documents