Campus Community Strategy

Definition and Overview

“Campus Community” is the core of the Oracle/PeopleSoft product. Campus Community refers to the collection of information related to a person: name, address, ethnicity, marital status, etc. The information is shared by Human Resources, Payroll, Contributor Relations, and Student Administration. Any person, regardless of their connection to the university (admissions prospect and applicant, student, alumni, and/or employee) will have information in the Campus Community set of pages. In addition, Campus Community refers to the collection of information related to such areas as organizations external to Cornell (companies, agencies, high schools, universities, etc.), the tracking of events, and the tracking of communications, and checklists.

Since Human Resources, Payroll, Contributor Relations, and Student Administration share the Campus Community, extra care needs to be given to ensure consistent use of PeopleSoft. Each area must agree to the values in setup tables and to the use of the Campus Community functionality.

The University Shared Data Committee (SDC) reviews proposals for the creation and use of shared data and the procedures and policies that will govern the consistent use of PeopleSoft across all areas. The group either will approve a proposal or determine that the issue needs to be elevated to the Oracle/PeopleSoft Project Directors group. The SDC consists of members from each functional area (Human Resources, Payroll, Contributor Relations, and Student Administration), CIT staff from Data Administration and PeopleSoft Development, and the Campus Community Director. (The Campus Community Director is a member of the Oracle/PeopleSoft Project Directors group).

In order to ensure that the use of PeopleSoft Campus Community functionality by the STARS team meets with the establish standards determined by the university SDC, a Student Administration (SA) SDC will be established which will consist of an SA Campus Community Lead and a functional area representative from each team (Admissions, Student Records, Financial Aid, and Student Financials.)

Goals and Benefits

Using common data, such as bio/demographic data about a person, enables Cornell to provide consistent information across all areas of the university. The University SDC and the PeopleSoft Project Directors provide the guidance and policies to enable consistent procedures and use of data throughout in Human Resources, Payroll, Contributor Relations, and Student Administration. This will allow for the elimination of “silos” that create inconsistent data and for more accurate reporting.

Assumptions

The SA SDC team will formulate proposals for the use of Campus Community data and functionality based upon thorough understanding of the business needs and careful analysis by all SA teams.
All members of the SA SDC will come to agreement on all Campus Community proposals before they are presented to the University SDC.
All proposals from the SA SDC will be put in writing using a common format.
The SA Campus Community lead will inform the SA team of all decisions made by the University SDC.
The SA team will adhere to the guidance and policies put forth by the University SDC.
Requests for changes to the policies and decisions made the University SDC will be requested via a proposal from the SA SDC.
Timely decisions will be made by all groups: SA SDC, University SDC, and, if necessary, the PeopleSoft Project Directors.
The SA Campus Community Lead will be able to enforce the decisions made by the University SDC.

Risks and Mitigation Strategy

Risk	Mitigation
Deviations from guidance and policies established by the University SDC could lead to inconsistent use of Campus Community.	The SA Campus Community lead will be able to enforce the University SDC decisions.
Lack of understanding of all SA business processes and their interrelations and lack of detailed analysis could result in an area’s inability to use Campus Community effectively.	The use of all Campus Community functionally will be analyzed and determined by a cross functional group from Admissions, Financial Aid, Student Financials, and Student Records
The inability to make timely decisions could adversely affect the SA project timeline.	Proposals will contain a due date. If issues are elevated to the Project Directors, decisions will be made based upon the issue escalation process.

Roles and Relationships

The SA SDC will ensure that the use of Campus Community is consistent across all the SA areas. They will review all proposals and provide guidance and recommendations to the SA Campus Community Lead. This will be important so that when proposals are elevated to the University SDC, there is buy-in and a common understanding among all the SA areas. The SA SDC will also serve as the review team for all SA setup tables.

As a member of the University SDC, the SA Campus Community Lead will provide the connection between the SA team and HR, PR, and CR. The lead will share in the decision making regarding all Campus Community proposals. This will establish the necessary consistency and use of the Campus Community functions throughout the University.

Since Campus Community impacts all SA functional areas, each area will need to work together in order to achieve desirable and agreed upon proposals for the University SDC. Likewise, the areas will need to accept and adhere to the decisions of the University SDC. The relationship between the SA functional areas and the University SDC is critical and tightly linked.