Statement of Direction Campus Solutions 2012 2013

May 2012

Oracle PeopleSoft Campus Solutions 9.0 Statement of Direction 2012

Oracle Statement of Direction—PeopleSoft Campus Solutions 2012

Disclaimer

This document in any form, software or printed matter, contains proprietary information that is the exclusive

property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions

of your Oracle Software License and Service Agreement, which has been executed and with which you agree

to comply. This document and information contained herein may not be disclosed, copied, reproduced or

distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of

your license agreement nor can it be incorporated into any contractual agreement with Oracle or its

subsidiaries or affiliates.

This document is for informational purposes only and is intended solely to assist you in planning for the

implementation and upgrade of the product features described. It is not a commitment to deliver any material,

code, or functionality, and should not be relied upon in making purchasing decisions. The development,

release, and timing of any features or functionality described in this document remains at the sole discretion

of Oracle.

Due to the nature of the product architecture, it may not be possible for us to safely include all features

described in this document without risking significant destabilization of the code.

Oracle Statement of Direction—Campus Solutions 2012

Purpose ............................................................................................. 1

Introduction ....................................................................................... 2

Oracle PeopleSoft Campus Solutions Drivers .................................... 3

Oracle PeopleSoft Campus Solutions: The Year in Review ............... 6

Campus Community – Prior-Year Updates .................................... 6

Recruiting and Admissions – Prior-Year Updates ........................ 12

Student Records – Prior-Year Updates ........................................ 13

Academic Advisement – Prior-Year Updates ............................... 18

SAIP: Student Administration Integration Pack – Prior-Year Updates 19

Financial Aid – Prior-Year Updates .............................................. 20

Student Financials – Prior-Year Updates ..................................... 22

Contributor Relations – Prior-Year Updates ................................. 23

Oracle PeopleSoft Campus Solutions: Planned Features ................ 25

Campus Community Planned Features ....................................... 25

Campus Access Planned Features .............................................. 30

Admissions and Recruiting Planned Features ............................. 30

Student Records Planned Features ............................................. 33

Academic Advisement Planned Features .................................... 39

Financial Aid Planned Features ................................................... 39

Student Financials Planned Features .......................................... 40

Contributor Relations Planned Features ...................................... 41

PeopleSoft CRM for Higher Education 9.1 ....................................... 42

CRM for Higher Education Prior-Year Updates ............................ 42


CRM for Higher Education Planned Features .............................. 43

Campus Solutions Warehouse (An EPM 9.1 Solution) .................... 44

Campus Solutions Warehouse Prior-Year Updates ..................... 44

Campus Solutions Warehouse Planned Features ........................ 47

Conclusion ...................................................................................... 48


1

Purpose This document provides an overview of features and enhancements included in Oracle

PeopleSoft Campus Solutions Release 9.0. It is intended solely to help you assess the

business benefits of planning for the implementation of the product features described.

The purpose of this document is to provide an annual update to the Oracle PeopleSoft

Campus Solutions (Campus Solutions) customers about activities impacting their use of

the Campus Solutions applications and related products. The document will provide an

overview to the enhancements and other updates that have been delivered since the last

Statement of Direction document, as well as an overview of features and enhancements

planned for the Campus Solutions codeline within the next 12 months. It is intended

solely to help you assess the business benefits of applying new maintenance and

planning for the implementation of the product features described.

Oracle plans to issue this document annually, targeting the second quarter of each year.

Additional, more detailed documentation will accompany the actual release of new

features.


2

Introduction Global economic uncertainty continues to impact higher education institutions and the

students seeking a post-secondary education. All are increasingly looking to technology

to help them do a better job of meeting goals, expectations and requirements including:

• Increased operating efficiencies and lower costs

• Faster, more secure access to information

• Increased and easier collaboration and sharing of information

• Flexible, open source and open standards-based solutions to more readily enable

information sharing and access

• Single, reliable source of data with the ability to support multiple systems and diverse

business processes

• Better business intelligence to inform more strategic, pro-active planning and decision-

making

Today’s colleges and universities must make technology investements that are strategic

and provide measurable value and return on investment not only to the institution, but to

all its constituents—prospects, applicants, students, faculty, alumni, donors and other

funding organizations.

In response to customer and market demands, Oracle continues to innovate and develop

products, features, and functions that support the unique academic mission of each of its

higher education customers. The Campus Solutions team has planned enhancements for

the next 12 months that build on the innovations in earlier releases by advancing

functional excellence, adding powerful business intelligence, and extending the services

framework to enhance integration.

This statement of direction describes planned enhancements in Campus Solutions for the

next 12 months.


3

Oracle PeopleSoft Campus Solutions Drivers

Campus 22002200 is a theme familiar to our customers who have attended recent Higher

Education User Group Alliance conferences. Campus 2200

2200 represents Oracle’s vision for the next

generation of Higher Education applications. But the vision does not come just from within

Oracle. Working collaboratively with our customers, we are focused on delivering modern

solutions so you can create a flexible, scalable and information-rich environment to support the

mission of higher education and the unique needs of your institution.

This vision is expressed in our product strategy which is extending beyond traditional functional

silos into a platform strategy, creating a new ‘core’ framework to support integration,

interoperability and the intersection of academic and administrative systems. This evolution is

driven by the architectural and functional needs of you, our customers.

More specifically, Campus 2200

2200 represents how we think about extending and enhancing Campus

Solutions. We think about every feature we enhance or build with a future-looking approach;

how can we make sure our customers all over the world can use this feature, now and into the

future? Our imperative is to build solutions that are adaptable to diverse education models,

support operational excellence and provide a natural, intuitive user experience that promotes

productivity for all users.

As we look at the big picture of how we collectively need the CS product to evolve, the highest

priority is deploying new enrollment and student support models to allow your institution to be

more flexible in how it accommodates new models, new demographics and new demands from

outside constituents. We are strengthening the core in an attempt to “future-proof” the student

system; a service-oriented architecture is key. An important objective of everything we build or

enhance is creating the ability for you to differentiate your institution by extending the product,

whether that is realized through unique programs of study, powerful CRM capabilities or

distinctive self-service. The roadmap that you see elucidated in this year’s Statement of Direction

is a continuation of our evolution to the next generation student system.

The evolution continues on both the technology and functionality fronts. We continued the

expansion of a service oriented architecture over the last year, with the release of a set of web

services to support the complete enrollment process. Customers saw the delivery of several

phases of major functionality to support a number of new features, including:

• Program-based enrollment (supporting the ability to structure the curriculum a student

needs to follow to achieve an academic goal)

• Activity management (supporting the ability to flexibly collect and evaluate learning

activities, including exams, along with progression rules)

• Evaluation Management System (supporting the ability to track and assess the progress of

the evaluation of an applicant)


4

• Research Enrollment Tracking (supporting the ability to manage key aspects of a research

candidate’s data and progress with their thesis)

• Third Party Contracts and Corporate Billing enhancements (supporting more flexibility in

defining and managing how Third Party Contracts are maintained and assigned to students

as well as how the Corporate Bill is processed)

This Statement of Direction will highlight what we plan to deliver in each of these areas over the

next 12-18 months.

Customers have been increasingly focused on providing a modern engagement platform for their

constituents, particularly their applicants, students, alumni, donors and faculty members. Many

customers have built applications to allow access to Campus content and transactions, including

mobile access. So in addition to the targeted new features identified above, the Campus Solutions

team is evaluating the use of our delivered web services to enable us to provide a more modern

user experience for our customers’ “customers”, including mobile access to high-value content

and activities.

Each of these enhancements represents another step in our roadmap to provide customers with

a modern, extensible solution that will continue to evolve to the next generation student system.

Each phased delivery is accompanied by extensive documentation in PeopleBooks as well as in

some cases, supplemental guides and White Papers. To promote customer awareness of the “big

picture” for the major features we are delivering in phases, we produce a specific type of

document called Benefits Documents that help customers understand the overall functionality of

the feature and how we expect they will be able to leverage that feature at their institutions.

The ongoing enhancement of the Campus Solutions applications represents a continued

commitment to excellence and quality. Leveraging evolving technologies, the Higher Education

team at Oracle delivered many new capabilities in four Additional Feature bundles during the last

12 months, which we will discuss in more detail in the following sections.

A number of the new features on which we are working are planned to be delivered over several

phases, likely covering 18 to 24 months duration. In this 2012 Statement of Direction, we’ll cover

the high level overview of the feature and then highlight the pieces of the functionality that we

plan to deliver in the next 12 months.

Characteristics of the Roadmap – The Continuous Delivery Model

The CS Continuous Delivery Model (CDM), which maintains a core baseline of the CS 9.0

codeline with incremental enhancements (Additional Features) delivered throughout the year, is

the enabler for our evolution. The CDM allows the development team to deploy new features in

more consumable increments, as part of the current CS codeline, easing your effort in adopting

new capabilities. It is important to note that many of the major initiatives on the roadmap will

have initial phases delivered that customers will not fully deploy; these initial phases will likely

consist of the architectural foundation pieces and the web services supporting the feature.


5

Subsequent phases will deliver the capabilities for the administrative users (the processes and

incorporation of a rules engine) and then end-users (student and faculty engagement).

Expected Benefits of this Roadmap

With the focus noted above, clearly, we expect this roadmap will provide customers with the

ability to support global enrollment models and functionality, whether they follow a very

structured, program-based enrollment model or a more open, flexible model (common in the

United States) or a hybrid of both models. Funding models are changing; for many of our

customers, the increased use of Third Party Contracts will be streamlined due to the delivered

enhancements. Many of our customers point out that their business models are evolving and they

don’t follow a single model with all their students (undergraduate, research students, non-

traditional education, professional education or workforce development.). The ability for

customers to leverage the delivered functionality beyond what we deliver is important; web

services allow you to connect other pieces of your ecosystem to our supported services which

connect to the core system. Finally, a huge benefit to be realized from the current roadmap is the

ability to retire customizations, to replace your custom solution, when you’re ready. The

incremental delivery model should provide you with the opportunity to understand, analyze, plan

and test for deploying a supported solution, reducing the burden of maintaining custom

solutions.

Planned enhancements to other products in the Oracle family to support Higher Education over

the next 12 months include the PeopleSoft EPM Campus Solutions Warehouse and Fusion

Intelligence products as well as PeopleSoft CRM for Higher Education. Additionally, the

Campus Solutions team expects to evaluate and prioritize incorporation of features from the

PeopleTools 8.50, 8.51, 8.52 or 8.53 releases into the CS 9.0 applications. Our stated policy

requires customers to be current on PeopleTools 8.51 or higher by September 2012. We do not

expect to release fixes or regulatory/legislated updates which require Tools 8.51 (or higher) until

that date. .However, it is likely that some of our new enhancements will require customers to be

on the current Tools level when that functionality is released. We will call out any Tools pre-

requisite in the specific sections of this Document. (For more information on the Campus

Solutions PeopleTools Adoption policy, please see Doc ID 1365646.1 in My Oracle Support.)

NOTE: The PeopleSoft Enterprise Components team certified features to be delivered on the

PeopleSoft 9.1 application releases. This resulted in the Campus Solutions 9.0 customers not

being able to fully leverage these new capabilities, such as the Forms and Approval Builder. The

PeopleSoft Enterprise Components team plans to work with Campus Solutions to enable

Campus Solutions 9.0 customers to leverage the Enterprise Components features. The target for

completing this project is in the next 12 months.

In this annual Statement of Direction document, Oracle is providing information about

significant updates to Campus Solutions delivered during the previous 12 months as well as

looking forward to planned enhancements and regulatory updates for the next 12 months.


6

Oracle PeopleSoft Campus Solutions: The Year in Review

This section of the annual Statement of Direction provides descriptions of features and

functionality that Oracle delivered for Campus Solutions over the prior 12 months. Please refer

to the Bundle documentation on My Oracle Support or PeopleBooks for more detail about a

specific feature.

Campus Community – Prior-Year Updates

Many customers began the projects to separate the Campus and HCM applications into separate

instances over the last year. We have been following their progress and engaging with the HEUG

community to assess areas for which we may need to provide additional support. Following on

the first phase of support for the CS – HCM Integration of core Person data, last year we

provided updated documentation as well as software updates to support an additional approach

of direct integration. We also delivered additional phases of enhancements for 3C Delete

capabilities, SEVIS support, enhancements to Affiliations and creation of a web service to

publish FERPA data. We’ve added several new frameworks to Campus Solutions, which are

designed to provide a consistent experience with those capabilities wherever they are used within

the product.

CS – HCM Integration: Providing the Tools and Guidance

Many customers are pursuing the Owner/Subscriber model, in which Campus Solutions is the

owner of all person data (add/update) and HCM subscribes to published messages. However,

others wanted a solution that allowed them to update the individual’s data in either system (CS or

HCM) and have the other system subscribe to those updates. In essence, they want to replicate

the behavior of the current, single database (with one set of Person tables) in which the last

update to a person’s record “wins”.

The delivered Person Basic Sync message and associated utilities support this type of dual update,

allowing the data in that message (PBS) to be updated in either HCM or CS, with the other

system subscribing. The Campus team delivered support for this model, under the title

“Subscriber Only”. There is a risk of data synchronization problems with this approach, resulting

in the need for customers to manage the resynchronization effort. Reports from customers

adopting this approach indicate the rate of data issues is low and the ability to manage updates in

each application (student updates in CS, employee updates in HCM) outweigh the issues with

data synchronization.

Some of the additional enhancements delivered to support the CS-HCM Integration included:

• Emergency Contact EIP

• Citizenship Status EIP

• Enhanced Boomerang Handler


7

• Continued updates to Implementation Guides

Data Truncation Recommendation

With the deployment of Campus Solutions and HCM in separate instances, each instance now

includes many tables (and data into those tables) that are no longer relevant or needed. For

example, in the CS instance, HCM tables that had previously been used as part of the combined

instance will no longer have data written to them (that data now being stored and transacted in

the separate HCM instance); this data not only consumes storage space, but can potentially

present the risk of accidental use of stale date in the generation of reports that fail to account for

the separation. Oracle delivered recommendations of HCM tables in Campus Solutions for

which the data can be “truncated” or deleted, as well as lists of CS tables in HCM (both HCM

9.0 and HCM 9.1, depending on which release a customer is running) that can be truncated. It is

important to note that since each customer implementation is unique, these lists should be vetted

against your environment, with appropriate testing, to ensure you get expected results.

NOTE: Please note this information for customers considering an upgrade to HCM 9.1. Oracle

waived the fee for the first 12 months of Extended Support for HCM 9.0. This means that

customers continue on Premier Support through December 2012; alternatively, they can take

advantage of Extended Support for HCM 9.0 during 2013 and 2014. As of December 2014,

HCM 9.0 moves to Sustaining Support. For more details, see the Oracle Lifetime Support Policy

on Oracle.com.

Another important clarification for customers involves the need to apply core HR and North

American Payroll (NAP) maintenance to the Campus Solutions 9.0 instance. Campus customers

are entitled to the core HR and NAP maintenance as part of their limited use license to those

two applications. Therefore, Campus customers will continue to apply core HR and NAP

maintenance to their CS 9.0 instance through December 2014. No Extended Support payment is

required. As of January 2015, the Campus Solutions team will provide support for the HR and

NAP objects, as necessary. For more information, see Doc ID 1437607.1 in My Oracle Support.

Campus Solutions Frameworks: Providing Extensibility and Re-usability

As new features are developed, the architecture team looks for ways to re-use utilities and

capabilities created for a particular business need. Wherever possible, the Campus team creates a

framework so that utility can be used in other business processes internally and also extended by

our customers. A number of new frameworks were introduced in the prior year.

Constituent Transaction Manager (CTM): Moving from an Unknown to a Known User

There are many scenarios within the Campus Solutions breadth of business processes in which

you want to allow an anonymous user to be able to interact with your system. In many cases you

want to capture who that person is and allow them to continue with other sorts of interaction.

And, if you already have a record of them in CS (i.e., they already have an EMPLID) you want to

be able to match up their current information with the existing record without creating a delay in


8

the current interaction. The admissions application is an obvious example of this type of

functionality, but there are many others.

The Constituent Transaction Manager, delivered in 2010 with the Admissions Application Web

Services, is a framework that manages constituent transactions requiring staged data. This

functionality allows the individual to start or complete a transaction within CS without first being

assigned an EMPLID. Search/Match is configured to run when you want it to, within the

transaction flow or after it is completed. The data entered by the individual is kept in staging

tables which you can review and update until the transaction is posted. When posted the staged

data is promoted to the appropriate CS tables (e.g., Admissions, Donations, etc.).

This past year we delivered a standalone utility for the Constituent Transaction Manager,

enabling this functionality beyond the Admissions application process. This framework supports

the existing functionality we call New User Registration, which allows the unknown user to

register and authenticate to your system prior to performing a self-service transactions. NUR is

the foundation for other sorts of possible interactions such as Delegated Access (e.g. Parent,

Guest, 3rd-party access), Contributor Relations fund-raising activities, and other types of guest or

visitor access to transactions within CS.

Shopping Cart Framwork: Supporting User “Checkout” for Enrollment or Payment

The Shopping Cart framework arose from the existing Shopping Cart functionality in the

enrollment process. As the team was creating the web services to support this aspect of the

enrollment process, they noted that there are other aspects of Campus Solutions that might be

able to leverage this type of control. Hence, the Shopping Cart framework provides a generic

web service (SCC_SHOPPING_CART). Customers can use this service to implement a

shopping cart for any Campus Solutions feature.

The benefits of using the Shopping Cart framework include:

• Your effort in building a shopping cart for a Campus Solutions application or a feature is

greatly reduced. The Shopping Cart framework supports the functionality common to all

shopping carts, such as adding items, checking out items, and so on. With the framework

already supporting the common functionality, your technical staff can focus their efforts in

implementing user interfaces that use this framework.

• You can improve the efficiency of code maintenance. For example, multiple shopping

carts for various Campus Solutions applications or features can use the same Shopping

Cart framework code. Therefore, with this framework, you are not repeating the code that

is common to all shopping carts.

• A Campus Solutions application or feature can store the shopping cart data in its own

tables, and add, delete, or modify this data.


9

• A shopping cart specific to an application or feature can have its own business logic. For

example, you could add your own logic to validate whether the items which the user wants

to add to a shopping cart satisfy certain conditions.

Entity Registry: Enhance Reusability and Reduce Maintenance Burden

An entity is an object that provides access (view, create, update) to data in a record and is

implemented through an application class. By design, an entity is the primary point of access to

the underlying records so that potential inconsistencies from having the same logic in multiple

places are avoided. This helps ensure the code is reusable and maintenance is easier.

In July, 2010, we introduced an innovative structure called the Entity Registry in which data is

defined and organized. The Entity Registry stores entity records, application classes, properties

and entity relationships. It stores the information relevant to building XML and has utilities for

generating schemas and base code which can then be modified. The Entity Registry is a

comprehensive source that defines the XSD (XML Schema Definition) for Campus Solutions

core tables and the data they contain. The entities for all core data records within the enrollment

and course areas are delivered within the Entity Registry component. The entity data is

considered system data and the registry is necessary for the correct functioning of many of the

Campus web services (including Admissions Application Web Services, FERPA service and the

Enrollment Web Services).

In the past year we enhanced the Entity Registry to provide additional flexibility and control by

your institution. We introduced the concept of “entity properties” as well as the use of the List of

Values (LOV) functionality within the Registry.

A property is defined as an individual value on the entity that is controlled by the Entity Registry

component. Properties are generally based on the fields of the underlying records (that is, a

staging record if it exists and the production record). Customers can now define how a property

should behave when its data is encoded as XML (for instance, when the system uses the property

inside web services).

The system uses the properties, and not the fields of the underlying records, as the source of

truth to drive the functionality of the underlying entity, and to generate the entity code and the

schema.

There are several benefits to the addition of entity properties.

• Ability to explicitly determine online what fields should be sent and what fields should be

updated when received via a web service.

• Ability to set what fields are required, since many fields marked required on the record

may be managed by the entity, and therefore not required via a web service.

• Customers can now extend entities by adding additional non-field properties, controlled

via the PeopleTools app class.


10

List of Values (LOV) Used in Entity Registry

Self-service user interfaces constructed using tools external to your Campus Solutions database

will typically contain data fields that have predefined or “prompt” values used to control and

streamline data entry for a user. If you want to display these values that are setup inside your

Campus Solutions database, whether it is for a prompt field or a field that contains translate

values, you can take advantage of the List of Values Web Service (SCC_GET_LOV introduced

in Feature Pack 3, July 2010) to do so. This delivered web service recognizes and provides the

values that are used to populate drop-down list boxes on a user interface and for validating

selections.

Over the past year, we have integrated the Entity Registry with the LOV framework to allow

sending the value description with the value included inside the outgoing XML. The value

description returned can be configured based on your needs. For instance you may want to

return the value’s long description instead of the short description.

In addition to the above enhancements, additional changes to the Entity Registry delivered last

year include:

• Entities no longer require coding, assuming they do not need custom validation or pre-

save logic.

• Improved performance due to enhanced entity caching.

• Allows new entity types to be defined.

• Enhanced Error Reporting.

Some of the other enhancements delivered in the prior year for Campus Community include:

• United States SSN Legislative Update – With the requirement from the US

Government to promote the Randomization of the Social Security Number, the Campus

Solutions and HRMS teams delivered a set of updates that enabled our customers to

comply with the new regulation. While there were a series of requirements related to this

update which introduced previously unassigned area numbers for assignment, a basic

requirement was that the use of “9” was not a valid number for the beginning number for

the SSN string. Historically, HCM (and therefore, CS) has used a value of “999-99-9999”

as the default for a missing SSN on a person’s record. This default value was modified to

‘XXX-XX-XXXX’. This edit and a number of related edits were provided to our

customers.

• SEVIS Release 6.7 – We delivered changes for the SEVIS Release 6.7 updates, including

the changes necessary for Alerts, Extract and Import SQRs and SQCs to support the

addition of Email Address for the events CreateStudent, Dependent-Add, Dependent-

Edit and Personal Info and to remove the logic for the fields no longer supported.


11

• 3C Delete Policy Manager – As part of ongoing enhancements to help manage the

deletion of the 3Cs, we have provided the ability to delete Communications, Checklists

and Comments both individually and using batch processes in order to help manage

tablespace sizes for the 3C tables. In addition to these bulk and individual delete

capabilities, however, customers wanted a more autonomous solution that would allow a

“super” user to set broader parameters for deletion and to have the deletion activity occur

on a scheduled basis. This allows much greater efficiency and less manual intervention in

the delete process.

Last year, we delivered the ability for designated users to be able to purge

communications, checklists and comments data according to broader parameters, and also

introduced the ability to define 3C Deletion exceptions based on service impacts. These

exceptions also apply to the previously delivered 3C Deletion functionality.

• Comm Gen – One of the most powerful features in Campus Solutions is the ability to

create and manage communications with your constituents; most of our customers are

heavy users of the Communications capabilities. We delivered a number of changes to

enhance the performance of the Communication Generation process. We continue to

work with customers to prioritize other areas of this important tool that need attention.

• Affiliations – Reacting to the early adopters of the Affiliations features, we added the

ability to Select and delete Affiliations as well as a third “view” which graphically displays

Affiliations assigned to a person.

• Higher Education Constituent Hub – The HECH Connector provides integration

support for Campus Solutions to the Higher Education Constituent Hub (an MDM

solution to master person data across campus systems). We delivered the ability for a user

running a search/match to import an existing HCM EMPLID ID (for use in the creation

of the CS record).

• FERPA as a Service – As CS delivers more and more points of exposure of Student

data, we have seen a significant interest and concern about FERPA data and elections.

How can we enable other systems which are ‘downstream’ from Campus Solutions to

know about the FERPA elections the student has made? The FERPA flag, indicating if

the student has applied any restrictions on their Directory information is published with

the Constituent Web Service. Now, the individual FERPA elections are exposed for use

by external systems via two methods:

- READ: An external system can query the FERPA service to retrieve an individual’s current FERPA elections

- PUBLISH: The FERPA service publishes an individual’s FERPA elections based on event triggers as updates are made in the system.


12

Recruiting and Admissions – Prior-Year Updates

File Parser Enhancements: Simplifying the Data Load Process

Updated in conjunction with the delivery of Admission Applications Web Services and

Transaction Management in July 2010, the File Parser is a utility that allows customers to define,

map and load external files from various sources to Campus Solutions. The increased popularity

of this utility in the global admissions community prompted plans for improving and updating

File Parser design and functionality. These included:

• Enhancement for additional date formats (MMYYYY, MMYY, etc.)

• Exposing File Data Elements for calculated field mapping actions.

• Added the ability to sub-parse an incoming field.

• Expanded error messages.

Revised Test Score Layouts

In keeping with our commitment to support test and data loads from external providers, we

updated a number of delivered processes:

• TOEFL Score updates;

• ACT Layout changes for 2011-2012

• GRE Test Score Load 2011-2012

• SAT Data and File Layout Changes 2011

• Student Search Service Data Layout Changes

• ACT EOS Layout Changes

• Student Search Service Data Layout Changes

Admissions and Recruiting: Regulatory Support and Updates

In keeping with our ongoing practice to provide reasonable and appropriate regulatory support

for various countries we delivered updates to:

• Victorian Tertiary Admissions Center (VTAC, AU)

• Universities and Colleges Admissions Service (UCAS, UK)

• Tier 4 Points-Based Immigration (PBI; UK)

• SEVIS Release 6.7 (US)

• Studielink (NLD)


13

Student Records – Prior-Year Updates

In 2011-2012 our major initiatives included Graduation Processing and the introduction of the

first phases of Program Enrollment, Activity Management, Research Tracking, and Evaluation

Management.

Graduation Processing

We delivered new functionality that supports the graduation clearance process that provided the

following benefits:

• Timelier processing of graduation applications.

• Enhanced review and tracking of graduation records.

• Enhanced service for students.

Program Enrollment

The Campus Solutions term “Program Enrollment” is, simply put, enrollment in courses

controlled by Academic Program requirements. These requirements are typically very structured,

where students complete course requirements in a series of stages. Students complete

requirements for one stage before progressing to the next. Using the continuous delivery model,

in 2011-2012 we delivered the foundation for comprehensive Program Enrollment feature

functionality. This included:

• Program Enrollment Structure: The ability to define a flexible and comprehensive

structure to accommodate a variety of patterns and rules for program-based enrollment.

We introduced a new structure called the Academic Item Registry (AIR). The AIR

provides the ability to define the framework, content and rules for a “program of study’,

or set of academic requirements that define what courses a student needs to take and the

order in which they need to be taken. It also allows users to organize academic

requirements into a hierarchy that can be used to provide a program template for driving

and controlling enrollment activity.

• Other delivered new structures that support the Academic Item Registry and the setup

required for Program Enrollment were:

- Program Format

- Enrollment Cohort

- Enrollment Category

- Item Attributes

- Course Group

We also introduced the student program record called the Academic Progress Tracker

(APT). This new structure allows administrators and advisors to track a student’s progress


14

through their program requirements while also providing the basis for a self-service planning

tool for the student. The Registry definition and the Academic Progress Tracker tie into

rules governing how a student progresses through their program requirements, measuring

results within groups of courses or an academic time period and at other levels of the

program of study.

Program Enrollment functionality that is anticipated in 2012-2013 is described in a later section

of this document.

Activity Management: Managing Course Content for Assessment

Many institutions require granular grading paradigms and calculation functionality to evaluate

student assignments, attendance and course level examinations. Specifically, schools need

extensive controls to:

• Define coursework structures for individual courses

• Set grading details that define mark rules, extra credit, capping marks, resit rules, and late

penalties

• Manage coursework requirements across multiple sections of a course or by individual

section

• Override coursework requirements for a given section(s) or student(s)

• Use course level results in calculations for additional program of study evaluations

(progression, honors, etc)

• Determine examination attributes including enrollment and staffing requirements

• Support separate examination scheduling and enrollment.

In order to meet these and other related requirements, we introduced the initial phases in 2011-

2012 of comprehensive functionality called Activity Management. We introduced the Activity

Registry which connects to course catalog entries and allows users to define a course

calculation structure in a hierarchical design where detailed grading rules can be defined. We

also delivered features that allow you to manage and organize this functionality including:

• Activity Generator: the mechanism to assign Activity IDs to coursework content and

associate an activity registry to class sections.

• Activity Manager: administrative access into class activities.

• The Result Scale which defines a comprehensive grading structure.

• The Academic Period Table which allows users to define time constructs in which to

schedule examinations.

• The Section Manager where exam sections will be associated with a facility, date, time and

other properties.


15

Activity Management functionality that is anticipated in 2012-2013 is described in a later section

of this document.

Research Enrollment Tracking: Managing the Lifecycle of the Research Student

The lifecycle of a student who is pursuing an advanced degree with a focus on research is very

different from the student pursuing an undergraduate degree or professional development

activities. Institutions need an efficient way to manage this type of student, from the time of

application, through their association with the supporting committee(s), through the funding

process, monitoring consumption and tracking of progress milestones and thesis evaluation.

In 2011- 2012, we introduced the first installment of Research Enrollment Tracking feature that

will address these requirements. This initial phase delivered research processing setup and the

main administrative components for Candidate Management and Thesis Processing including:

• Setup components in which users can identify and define research eligible academic

programs and plans, available research topics at the institution, and available research

supervisors and the level of their participation.

• A Candidate Management data structure which provides the ability to define and track a

research candidate's research topic, supervisors, thesis submission dates, and additional,

school-defined requirements (i.e. intellectual property implications, human and animal

testing clearances).

• A new Thesis Processing feature which will track the submission and evaluation of the

candidate's thesis or dissertation. This new feature is expected to utilize the new

Evaluation Management feature (see next section) to track the evaluation results from the

individual thesis examiners.

• Admissions Processing: A variety of new data elements were delivered to support the

unique needs and requirements related to advanced research candidate admission

application processing.

Research Tracking functionality that is anticipated in 2012-2013 is described in a later section of

this document.

Evaluation Management System

Evaluation Management (EMS) represents an innovative and comprehensive path to create a

‘generic’ evaluation solution which can be extended and applied to business needs in a number of

functional departments within an institution.

In 2011- 2012 we introduced the initial delivery phase for EMS that provided its administrative

structures and setup components. Using these structures a user can design an evaluation process

in order to:


16

• Tie the evaluation to a set of functional area data in the system (ex. Graduate level thesis,

doctoral dissertations, admissions, etc.)

- Define what is assessed in the evaluation, what ratings or measures are required, and assess the use of multiple rating schemes in the evaluation.

• Define who will evaluate the criterion in the rating schemes: Committees and/or an

individual evaluator as reviewers

• Create multiple levels of review and process flow of the evaluation

• Define specific values and function for recommendation and status fields which make

sense for the end users of the evaluation business process

• Control desired behavior in the administrative component

• Use batch processing to create, update and delete evaluation records.

EMS functionality that is anticipated in 2012-2013 is described in a later section of this

document.

Enrollment Web Services: Supporting Extensions of the Enrollment Process

In 2011-2012, the Campus Solutions web services framework continued to provide our

customers with more power to integrate with other campus systems as well as other UI tools,

mobile devices, and so on. Prior to 2011-12, we delivered the Constituent web service,

Admission Applications web services, as well as the services to support integration of enrollment

information with academic systems, such as Learning Management Systems. In 2011-2012 we

turned our attention to the enrollment processes. We delivered five web services, allowing

customers to leverage existing enrollment functionality. These included:

• Browse Course Catalog

• Class Search

• Shopping Cart processes

• Enrollment processes including Study List

We expect customers will benefit from these services as they use them as the foundation for

mobile applications or for localized, self-service user interfaces.

Student Records: Regulatory Support and Updates

In keeping with our ongoing practice to provide reasonable and appropriate regulatory support,

we delivered a number of updates in 2011-2012.


17

Higher Education Statistics Agency Updates (UK): We continued our support for required

HESA updates for the 2011/12 Student, Aggregate Offshore, Destination of Leavers, and Initial

Teacher Training (ITT) returns.

A number of updates were delivered to support regulatory mandates in the Netherlands

including:

• BRON BVE – Professional Education: We continued to provide support for BRON BVE

by delivering technological alignment and updates to improve performance and user

control over processing.

• Support for delivery of VAVO Combination Grade results as well as snapshot processing

• Internship Contracts: BPV enhancements for administration and automated calculation of

total hours BPV on Student contracts.

• Test Administration: Enhancements for calculation of Combination Grade

Canadian Post Secondary Information System: The Enhanced Student Information System

(ESIS), now renamed to the Post Secondary Student Information System (PSIS), introduced

regulatory changes which required modifications. Those modifications included:

• Renaming of pages and processes for the name change of ESIS to PSIS.

• Modifications to files, data elements and record layouts required as a result of the PSIS

codeset changes.

There were a number of updates made to regulatory support in Australia and New

Zealand including:

• Student Data Return (SDR) for New Zealand: Enhancements and re-design to enable

customer compliance.

• StudyLink for New Zealand: Enhancements and re-design to enable customer compliance.

• Automated Results Transfer System (ARTS) version 2.7 for Australia: Enhancements to

enable customer compliance.

• Updates to Department of Education, Employment and Workplace Relations (DEEWR)

2011 Reporting for Australia

• Updates to Student Amenities Fees and Higher Education Loan Program (HELP) for

Australia

National Student Clearinghouse: (USA): We delivered an additional process which will

recognize any units that have been designated as “withdrawn” and subtracts those units from the

overall unit total and stores the recalculated total for NSC reporting.


18

XMLP Transcripts: Define Transcript Type Update (9.0)

Since introducing the ability to create and deploy a flexible academic transcript using XML

Publisher in CS 9.0, we have made ongoing enhancements to this important functionality. Many

of these updates have come from customer suggestions. In 2011, we updated the Define

Transcript Type component so that a transcript template can be linked directly to the transcript it

defines. This enhancement allows the Report Definition and Template ID to be defined on each

Transcript Type.

Administrative Class Roster Updates (9.0)

In order to take advantage of similar functionality available to faculty users, we updated the

Administrative Class Roster Component to reflect the design and usability of the self service

class roster deployed on the Faculty Center including the notify by email feature.

Academic Advisement – Prior-Year Updates

Oracle Campus Solutions and the Academic Advisement Product Advisory Group worked

together on defining the issues that appear to be of significant concern to the advisement

community. Some of the more significant enhancements or updates delivered in the prior year

are covered below.

Academic Advisement Report Enhancements for Prospective Students and Advisors

Often, prospective applicants want to view degree requirements in advance to better understand

the requirements related to an academic goal and to ascertain how their transfer credit will be

evaluated. Campus Solutions provided a valuable enhancement that gives pre-matriculated

students and advisors the ability to run what-if advisement reports for their intended area of

study. This enhancement included:

• Self-service pages that a prospective student, such as a prospect or applicant, can use to

generate a what-if advisement report.

• The ability to define advisement report types that include self-reported transfer credit

models and administratively completed models that are in the status of Completed (that is,

cannot be posted until the student is term activated).

• Advisor Center pages that advisors can use to generate a what-if advisement report for a

prospective or current active student.

• A batch process enabling administrators to generate what-if advisement reports for

prospective or active students.

Increase the Maximum Number of Requirement Groups Allowed

Working with our Academic Advising Product Advisory Group, we identified this important

update. Increasing the allowed maximum number of requirement groups in Academic


19

Advisement setup will make setup and reporting more functional and flexible. This enhancement

increased the maximum number of requirement groups permitted per career, program, plan, or

subplan level from 30 to 100. We also increased the number of requirement groups that can be

attached to a special requirement usage from 30 to 100.

SAIP: Student Administration Integration Pack – Prior-Year Updates

Campus Solutions delivered a significant milestone in the roadmap for the Student

Administration Integration Pack last year; that was the updated functionality to come into

conformance with the final public version of the IMS LIS 2.0 specification (see more

information on the specification at the IMS site at http://www.imsglobal.org/lis/alliance.html).

Because of the increasing adoption of this specification within the learning management system

(LMS) vendor community, we expect to see more of the LMS vendors create integration to the

LIS specification and therefore enable supported integration with Campus Solutions class,

instructor, enrollment and outcomes information.

Provider Initiated Snapshot

One of the capabilities enabled by the final LIS 2.0 specification is ability for bulk management

actions (“snapshots”) to now be initiated by the provider of the data (in earlier drafts of the

specification, a consumer requested initiation was required).

In the context of Campus Solutions integration with external systems, this means that a user can

run (ad hoc or via scheduled processes) a snapshot in SAIP (the “provider) to generate the XML

document containing the desired data, rather than relying on the LMS (the “consumer”) to send

a web service call to generate those documents. The creates a great deal more flexibility for

schools to control the timing, routing, and use of snapshots, not only for LMS integration but

especially for use in integrations with non-LIS conformant applications.

In addition, we enhanced the SAIP with new capabilities around class section association and

date controls.

Ad Hoc Section Association

The existing Student Records cross-listed, combined sections functionality is supported with

SAIP integration. However, customers indicated that they needed the ability to associate class

sections across course offerings. The goal of this enhancement was to enable faculty members to

combine class sections into course sites in the LMS that aren’t formally associated in Student

Records as combined sections or multi-section classes. Each association can contain multiple

class sections, but each class section can participate in only one association (this new

functionality does not support a one-to-many or many-to-many association).

For each Institution and Term event, the faculty member can define a Section Association ID,

along with a Description, and then add the sections which should be associated into a single


20

course site. All page logic regarding scoping and targeting is identical to that of the existing

Associate Combined Sections page.

Section level integration Dating

The SAIP uses the “Integration Start Date” to determine when SAIP data begins publishing to

an external system. Previously, the Integration Start Date for a class section was driven off of the

Term Start Date value; all class sections in that Term have the same “activation” date. Similarly,

the Integration End Date is the same as the Term End Date. In response for customer demands

for more granular controls, we enabled the Integration Start Date and End Date to be based on

the Section level Start and End Date. This provided the customer with the ability to set the

Integration Start and End Date based on a number of days (plus or minus) from the Section Start

and End Dates.

SAIP Integration Monitor

One of the challenges of integrating systems is monitoring the health and status of that

integration. The SAIP Integration Monitor allows customers who are using Snapshots and Event

Driven (real-time) integration to see the status of Integration Broker connections and cross-

system integration connections (using the IMS LIS standardized error codes), view the errors and

see where they’re happening. The Monitor also allows you to re-run events that have errored out,

easing the process of keeping the data synchronized across systems.

Financial Aid – Prior-Year Updates

Financial Aid provides support for automating federal and institutional financial aid processing to

ensure more efficient operations. Many regulations are built into the software, so your institution

has the tools to obtain and remain in compliance. Below are some of the more significant

enhancements delivered in the prior year.

Loan Period Dates: Enhanced Efficiency Through Automation

Many institutions have different definitions of academic years and different loan periods for

individual Academic Careers or Programs. To facilitate and streamline financial aid loan

processing for these institutions, we delivered a new process to update the default Loan Period

Start and End Dates and the Academic Year Start and End Dates on the Loan Origination

record. This new process allows you to process multiple populations during a single run, and by

using Population Selection you can define the specific population of loan records to be updated,

including only those for students in a specific Academic Program.

Extensions of Population Selection/Update Process: Creating Efficiencies

The Financial Aid community leverages the Population Select and Update processes extensively,

creating efficiencies in processes and increasing the accuracy of managing the student


21

populations they’re impacting. We delivered a couple of new uses for Population Select/Update

over the last year:

• Delivered a Population Selection process for updating FA Progress Units on Student

Enroll – Allows users to select a population of students to update the Unit Progress FA

and Grade Points FA fields on the Student Enrollment record.

• Enhanced the NSLDS Request process to use Population Selection. This will allow you to

specifically identify those students for whom you want to request Transfer Monitoring or

a Financial Aid History file.

• Delivered a Population Selection to expire anticipated aid - For the identified set of

students, users can expire all of the anticipated aid for the students or just a single item

type of anticipated aid. In addition, customers have the ability to extend the expiration

date of unexpired Anticipated Aid.

Other enhancements delivered last year include:

• Enhanced multi-institution functionality for Aggregates.

• Updated Return of Title IV Session based processing

• Updated COD reporting for Ability to Benefit (ATB)

• Other NSLDS enhancements.

• Support for Loan Exit Counseling Load - We delivered support for the import and

processing of the new NSLDS Exit Loan Counseling data file. The feature incorporates

the Population Selection utility and includes a system provided file mapping definition

specific to the EXTC01 and EXTC05 file formats.

Financial Aid (US): Regulatory Updates

Campus Solutions maintains a rigorous schedule of updates, endeavoring to enable timely

compliance by our customers. We work with our customers to determine which regulatory and

legislative updates are the highest priority and attempt to support the required timing of those

changes.

Regulatory Updates are delivered in each of the four scheduled maintenance bundles per year:

• October Bundle – Regs 1: ISIR load, INAS-IM, PROFILE, Return of Title IV

• January Bundle – Regs 2: Database Match and Eligibility updates, NSLDS, Verification,

COD Processing updates for Direct Lending, Pell Grants

• April Bundle – Regs 3: Redeliver INAS-FM, Pell Schedules, CommonLine Updates

• July Bundle – Regs 4: FISAP, Satisfactory Academic Progress

We also post additional individual updates, as required:


22

• Pell Schedule Updates

• INAS-FM (multiple technical updates from College Board)

• Perkins and Direct Lending promissory note updates

Financial Aid (UK): Regulatory Updates

• Student Loan Company (SLC; UK): New FTEs for SLC student process, new and

modified pages and processes modifications.

Student Financials – Prior-Year Updates

Over the last year, the focus for Student Financials has been on completing a comprehensive set

of updates to Third Party Contracts and Corporate Billing. The phased approach to Campus

Solutions enhancements allows institutions to evaluate, test and deploy new capabilities in

increments that are easier to manage than a major upgrade event. The past year’s efforts in the

Student Financials are a good example of this phased approach.

Third Party Contracts and Corporate Billing

One of the top enhancement requests from the customers using Student Financials was in the

area of Third Party Contracts (TPC) and related Corporate Billing. Use of this functionality

continues to expand, with different models of usage found in different countries. The variety and

number of third party “sponsors” continues to grow too, from government agencies to private

entities. As stated in the Student Financial PAG’s White Paper on this topic, enhancements were

needed to “assist Universities to better manage Third Party Contracts and Organization Billing

by:

• Providing increased flexibility

• Streamlining business processes

• Assisting Universities to better meet the requirements of Organizations and Sponsors.

To streamline the Contract Setup and Maintenance, we provided the following flexibility:

• A process to “roll third party contracts” in mass and “roll specific” students to the new

third party contracts.

• Provide the increased flexibility to group third party contracts for the purpose of capping

the total contract amounts and/or student amounts.

• To allow for changes in “eligible charges”, a new component in TPC setup that allows for

exclusions of tree nodes. In addition, an online edit to prevent duplicate nodes from being

identified on the TPC setup.

• Additional user-defined fields at both the contract and student level to allow for support

for the US Department of Defense Wide Area Workflow (WAWF), for example.


23

In order to providing the mandatory information based on sponsor requirements, we provided

additional flexibility in producing the invoice or an electronic file:

• Enhancements to the XML Corporate Billing file to include the new fields noted above

and the student’s academic information.

• Provided the flexibility to override the template defined on the invoice layout.

• Ability to inquire on global invoices to allow display of paid invoices to enable users to see

which payments were applied to invoices.

In response to the institutions’ business requirements in applying Corporate Payments, we

delivered the following capabilities:

• Improved performance of the posting process by reducing the need to review unnecessary

data.

• Enhanced posting to allow student’s due dates/billing dates to be moved to the corporate

account.

• Enhanced the Corp Group Post component to allow input into the Contract EMPLID

and Contract Num fields. The fields are available on the Group Line record and are

available for data entry.

In response to the institutions’ business needs for viewing corporate transactions, we provided

the ability to:

• Display Contract Number and Contract EMPLID for a payment

• Cross reference the student’s related charges and academic information.

1098T Updates: Regulatory Support

Updates to the 1098T form are part of our annual regulatory cycle.

Higher Education Contribution Scheme (Australia) – Regulatory Support

We delivered updates addressing the calculation and reporting of HECS for students with

multiple careers.

Contributor Relations – Prior-Year Updates

Contributor Relations provides support for the constituent, focused on the status associated with

the alumni or friend of the institution. Of course, the reach of the Contributor Relations

application extends beyond the traditional alumni to support the comprehensive ability to fund-

raise and friend-raise.


24

The Contributor Relations team works very closely with the customer community to prioritize

product areas for enhancement each year. The enhancements that were delivered over the course

of the last 12 months for CR are listed below.

Name Display Enhancements: Extending the Solution

We had previously delivered a significant enhancement to the Name display functionality,

focused on increased configurability for display choices on the administrative pages in the

Contributor Relations product. Last year, we delivered that same capability for the Secondary

pages in Contributor Relations.

Note: This enhancement was delivered for the Contributor Relations Administrative and

Secondary pages. We will continue to work with Campus Solutions customers to prioritize the

modules to be targeted for this update.

Prospect Strategy Status Enhancements

This enhancement allows an institution to track the prospect’s progress through the overall

prospect life cycle with effective dated rows for prospect status. Additionally, specific goals for

resources (staff, volunteers, and/or units) may be entered to track results in custom

accountability reports.

Person Profile – Parent/Child Academic Overview Section

This enhancement includes two additional grids in the Person Profile that display academic

information. The first displays the academic information for the person in context; the second

displays academic information for related IDs. For example, if the constituent in context is a

parent of a current student, the student’s academic affiliation(s) displays along with anticipated

graduation date. If the child is an alumnus, the Class Year displays in lieu of anticipated

graduation date.

In addition to the above enhancements, the CR community can take advantage of the updates

made to the functionality contained in the Campus Community module.

Campus Solutions Frameworks: Providing Extensibility and Re-usability

As new features are developed, the architecture team looks for ways to re-use utilities and

capabilities created for a particular business need. Wherever possible, the Campus team creates a

framework so that utility can be used in other business processes internally and also extended by

our customers. A number of new frameworks were introduced in the Prior year. Please see the

prior Section for Campus Community for a description of these new frameworks.

• 3C Delete Policy Manager - As part of ongoing enhancements to help manage the

deletion of the 3Cs, we have provided the ability to delete Communications, Checklists

and Comments both individually and using batch processes in order to help manage

tablespace sizes for the 3C tables. In addition to these bulk and individual delete


25

capabilities, however, customers wanted a more autonomous solution that would allow a

“super” user to set broader parameters for deletion and to have the deletion activity occur

on a scheduled basis. This allows much greater efficiency and less manual intervention in

the delete process.

Last year, we delivered the ability for designated users to be able to purge

communications, checklists and comments data according to broader parameters, and also

introduced the ability to define 3C Deletion exceptions based on service impacts. These

exceptions also apply to the previously delivered 3C Deletion functionality.

• Comm Gen - One of the most powerful features in Campus Solutions is the ability to

create and manage communications with your constituents; most of our customers are

heavy users of the Communications capabilities. We delivered a number of changes to

enhance the performance of the Communication Generation process. We continue to

work with customers to prioritize other areas of this important tool that need attention.

• Affiliations - Reacting to the early adopters of the Affiliations features, we added the

ability to Select and delete Affiliations as well as added a third “view” which graphically

displays Affiliations assigned to a person.

Oracle PeopleSoft Campus Solutions: Planned Features

Oracle PeopleSoft Campus Solutions planned features represent an ongoing commitment to

provide best-in-class products that provide real business value. The Planned Features section

provides descriptions of features and functionality that Oracle expects to provide in Campus

Solutions over the next twelve months.

Campus Community Planned Features

The core of the Campus Solutions product – Campus Community – continues to expand by

delivering frameworks that are not only leveraged by other modules in our product family, but

which can also provide significant benefits to our customers. The architectural approach we are

taking as we transform Campus Solutions to the next generation student system is evident not

only in the services-oriented architecture that you see realized through the increasing number of

web services but also in the innovative approach to enabling customer extensibility. This is where

the “framework” concept stands out! As we build out support for new business processes, in

areas like admissions, enrollment, Third Party contracts, assessment, and so on, we focus on how

best to enable the customer to extend the solutions. This has the benefit of ensuring a new

feature will “fit” your institution’s business needs, while reducing the cost of implementing and

maintaining a feature.


26

CS-HR Instance Separation – Direct; Synchronization Utility

As more institutions undertake the separation of their Campus Solutions and HCM instances, we

continue to look at what capabilities can be added to the existing Split integration tools and

framework to ease the ongoing support for integration between the systems.

To further ensure the health and accuracy of data synchronization between Campus Solutions

and HCM, the CS-HCM Data Synchronization Utility will allow institutions to run processes that

identify where data has become desynchronized due to Integration Broker issues or other errors.

In addition, the Synchronization Utility will provide the ability for institutions to resynchronize

the data by choosing which data or data set is the current or correct one.

Common Attribute Framework - Extending Each Solution

Requests for new data fields throughout Campus Solutions are fairly common from our global

customer base. However, delivery, testing, and documentation of new fields largely depends on

their common utility and impact on batch processes, components and core functionality. In

many cases, individual areas of an institution have valid business needs to add one or more fields

to a component. For example, the Admissions Office might want to include a Passport Number

in the General Materials component or the Dean’s Office require the display to faculty users the

expected time they will need to devote to a specific coursework activity. To allow customers and

implementation teams to easily add fields to existing tables via configuration rather than through

a development process is the goal of Common Attribute Framework (CAF). We anticipate that

CAF will provide a central location to define a “Common Attribute”. A common attribute is like

a field; it has a data type (e.g., number, date, string), it may have a set of valid values, and it can

be associated with a record in the system. An attribute is created, defined and associated to one

or more records through provided setup and can be accessed in any required page after a minor

modification (adding a subpage) to the page. We anticipate that CAF will have utility across

Campus Solutions over time by providing:

• A method for customers to add user defined fields to a PIA page without resorting to

customization

• An alternative approach to adding data fields associated with regional or country specific

extensions for national, provincial, or state reporting or other localized business processes.

Identity Management Integration with Campus Solutions – Supporting the Ecosystem

Ensuring robust security processes on campus has been and remains an area of critical concern.

Campus Solutions, working with the Oracle Identity Manager team, plan to provide

enhancements to existing Constituent and Affiliation messaging capability to provide an out of

the box integration with a new OIM Campus Solutions Connector. This planned capability will

allow institutions to manage in Campus Solutions the affiliations that an individual has with that

institution, and publish that information in such a way that identity records can be created and


27

updated. Provisioning and access decisions can seamlessly be made in OIM based on that

information.

Entity Framework: Extending the Solution

We plan to enhance the Entity Registry to enable a more general purpose import/export

framework. So while you will be able to import/export entities, we will also be able to use the

framework with other new functionality being delivered, such as the Delegated Access

framework and Common Attribute framework. This means rather than using a dat/dms

approach we will allow certain objects to be exported and imported as xml. This has numerous

functional benefits.

• Exporting data is simplified – Data is exported as a full object, so an entity is exported

rather than individual rows of a record.

• Controlled Import – A comparison report is provided when importing data and the user

has a choice of how to handle conflicts (ignore, merge).

• Replace functionality – Wipe out the existing entity and replace it with a new one. Overall

this should make it easier for customers to migrate their data from development to

production, which is crucial for the entity registry, the rules engine etc.

We plan to add entity “categories”; these will be used in conjunction with the rules engine for

classifying entities (e.g., Person entities, Student Record Entities, etc.) and granting security to

write rules only around specific entities.

Currently, we have delivered 183 entities; without categorization, performing any sort of

searching on those entities is difficult (if you do not know the exact name of your entity it is

currently very difficult to find an entity pertaining to an area, e.g., enrollment). By classifying

entities it facilitates customers’ ability to search for entities pertaining to the data they need.

This feature was primarily added to support integration of the planned rules engine, which will

limit the available entities based on the relationship between the rule category and the entity

category. For example a rule category for the new Academic Item Registry (used in Program

Enrollment) may limit the available entities to those pertaining to the AIR objects.

Additional features being added to the Entity Framework include:

• Integration between the entity registry and the new Common Attributes Framework.

Attributes will automatically be handled as properties on the entity.

• We plan to deliver a more formalized way of querying for entities. This can be used by

services and the rules engine to retrieve entity data in a more standardized way.

• Better integration of the xml schema with the message schema. Customers should be able

to see all entities that have message part schemas associated with them and more easily

update the schemas when the entity changes.


28

Delegated Access Framework: Enhance Collaboration and Service to Constituents

Delegated Access is a framework that standardizes "who can delegate what access to whom"

within the Campus Solutions self-service components. We plan to allow institutions to define

what data (components) a student (the Delegator) can delegate access to his/her parents or any

other person of their choice (the Proxy). We plan to deliver this feature over several phases,

some of which will be in the next 12 months while others will likely be realized later.

The basic requirements we plan to address include:

• Ability for the schools to decide what components should be eligible for delegation.

• Delegator needs to know the email address, the name of the person he/she wants to

delegate access to and the relationship with that person.

- In a future phase we will be looking at allowing a Delegator to delegate access to an unknown person -- ex.: an HR employee at a company or a person representing a military organization

• After entering the email address, the Delegator lists the transactions he/she wants the

Proxy to see or to update. For example, a transaction can include a collection of self-

service components like Make a Payment, View my class schedule or just one component.

- Delegator should be able to revoke access by removing one or all of the transactions listed for a specific Proxy.

• Once the Delegator identifies a Proxy and delegates access to one or more transactions,

we plan to send an email notification to the Proxy’s email address. Email should include a

URL link for the Proxy to access the CS database.

• The Proxy can be known by the system or not. If they are not, we plan to use the New

User Registration utility so the Proxy can create a User ID and a password. If the Proxy

already has a user ID to access the Campus Solutions database, he/she is able to reuse it.

• The plan is for the framework to link the Proxy’s User ID with the Delegator's EMPLID.

Once the Proxy agrees with the Terms & Conditions written by the schools for accessing

the Delegator’s data, the Proxy’s User Profile gets automatically updated with the Roles

tied to the transactions delegated by the student.

- The User Profile will also be automatically updated when Delegator removes transactions or adds more.

• An EMPLID can also be created or associated with the Proxy.

• Integration with the Affiliations features where an affiliation can be added to a Proxy is

planned for a future phase.

• In the first phase of the Delegated Access project, we plan to deliver the basic ability to

have the student indicate who the delegated person is and their access to certain

components.


29

• Later phases of the Delegated Access project – beyond the next 12 months - may include

a ‘Parent Center’ or a ‘Delegate Center’ which would display all the Delegators a Proxy has

delegated access to as well as links to the components to which they have been granted

access. We also plan to evaluate including an Administrative page to view the student’s

shared information as well as a “Help Desk” page to help the proxies to register or

authenticate and view the student’s data.

New User Registration: Enhancements

New User Registration (NUR) functionality was delivered in 2010 with the Admissions

Application Web Services (AAWS). It allows a person unknown to the CS application to create a

User ID and a password to access your system. In the context of AAWS, NUR is used to allow a

future applicant to register and get authenticated to your system so he or she can enter an online

application.

Our plan is to enhance the capabilities of this functionality by removing any dependencies to a

self-service transaction (AAWS) and allow security provisioning setup specific for the consuming

transaction. This effort is likely to be a multi-phased project.

SEVIS Release II Support: Regulatory Support

Based on input from the US Agency responsible for the new SEVIS II plan, we do not anticipate

any updates on this project for the next 12 months.

Communication Generation: Enhancements for Performance

One of the most powerful features in Campus Solutions is the ability to create and manage

communications with your constituents; most of our customers are heavy users of the

Communications capabilities. The Comm Gen process was delivered in Release 9.0 and many

customers are using this process to generate thousands of communications. Our plan is to

evaluate options for enhancing performance of the process as well as look at ways to streamline

the setup of Communications. This multi-phased effort has already delivered performance and

scalability improvements and in the near term we are looking to deliver improved error messages

to assist with problem diagnosis and we continue to look for ways to enhance ease of use.

Affiliations: Extending the Solution

A number of enhancements are being planned for the Affiliation feature. Those include:

• Context Data Inclusion – An additional element of the Affiliation definition will be

“Context Data”. This will allow the specification of additional record/field pairs to be

associated with the affiliation code and included as part of the data when the affiliation

message is published. We expect this enhancement to enable more flexibility and

definition when the affiliation is used in conjunction with other business processes such as

Identify Management.


30

• Affiliations Example Guide – Document and software package that contains three sample

Affiliations and a unit-testing framework for the Affiliation Framework. The following

sample Affiliations are included: Worker, Applicant and Student. This planned

documentation and examples will enhance customers understanding of the affiliations

feature and their ability to set up and test their own affiliations.

Australia and New Zealand: Regulatory Support

We plan to continue to provide regulatory support in Australia and New Zealand over the next

12 months. We will work with the customer base to validate our design for this support.

• New Zealand Qualifications Authority (NZQA): Enhancements to enable customer

compliance.

Campus Access Planned Features

We are introducing a new Section in this Statement of Direction to focus attention on our early

work with the usability of our applications. The execution on the vision of Campus 2200

2200 includes

investment to modernize the user experience of Campus Self-Service; we are using a working title

of “Campus Access” to identify these efforts. This project will extend over several years, will

likely leverage technologies in addition to PeopleTools and will be informed from working

closely with customers and students.

For the next 12 months, we plan to target a couple of areas, including the creation of the User

Experience for the student, advisor and faculty users of our new features, including Program

Enrollment, Activity Management and the Evaluation Management System. Beyond that work,

we also plan to create mobile access for the common, high-value student activities in Campus

Solutions.

Customers will see more specific information about how the Campus Access project is being

realized in the documentation for each Additional Feature bundle.

Admissions and Recruiting Planned Features

Working with various customer groups, especially our very active Recruiting and Admissions

Product Advisory Group, we plan to deploy innovative tools to our customer community to

support the efficient implementation of Admission Applications Web Services and to present a

new paradigm for loading external data.

Sample Online Application (SOLA)

Admission Applications Web Services (AAWS) has been successfully implemented by a number

of customers since its delivery in July, 2010. We have been working to improve the offering since

that time including redesigning and delivering new documentation to support its implementation.

However, we have also recognized that there may be considerable gaps in customer readiness


31

and required depth of understanding as they attempt to take advantage of this important

technology and functionality. Some customers have struggled with understanding Service

Oriented Architecture (SOA), WSDL, XML etc. while building an application user experience

during their implementations. In order to address this and to promote and support AAWS

uptake, we intend to deliver an “out of the box” sample online application that our customers

can use for reference, training, deconstruction, and testing. This unique deliverable is not

intended to be deployed to applicants but rather to be used as an example for technical

implementers to examine and understand how delivered web services operate. By providing

readily available tools like an admission application sample, we hope to greatly increase the

probability of successful implementations, reduce the time to their completion, and increase

customer confidence to uptake future SOA based projects.

The Sample Online Application (SOLA) is a unique deliverable that is anticipated to provide:

• A user interface built in PIA in a familiar PeopleTools package that can be easily

understood and referenced.

• A UI-SOA sample in which all of the web services (with the exception of List of Values

(LOV) in AAWS are working.

• The ability to use SOLA as a learning tool for AAWS Setup, Constituent Transaction

Management (CTM) Setup and administration.

• A working sample that can be used to create data in CTM and Application staging.

• A testing device for a locally customized user interface.

• Accompanying documentation that will assist implementers with useful reference in

addition to the content we have already provided.

Common Data Load (CDL)

Campus Solutions supports a number of test and data loads in the current code line which

frequently require updates as their sponsoring third party agencies update, add and re-design

them. In recent years we have noticed an increasing frequency of mandated file layout changes

that are required with little time for development, testing, and documentation. And the demand

for new data and test score loads continues to grow from our global customer base. It is apparent

that a new approach to supporting data loads for supplied external sources is required in order to

keep pace with the changing needs of our customers. A high priority of our HEUG Admissions

Product Advisory Group is to provide the “ability to take data from a variety of file types and layouts and

load these into the system.” Our customers have also expressed the need for a number of additional

data loads including new test data (IELTS, Pearson, Compass) as well as the need to load data on

persons (Prospects) from a variety of external data sources. It is our belief that a common data

load structure and related processes is required for us to sufficiently serve our current and future

customer demands.


32

We aim to create an innovative tool that will utilize existing functionality (Constituent

Transaction Management, the File Parser, Entity Registry, etc.) and provide new structures that

will allow customers to recognize, define, and map almost any external file containing data that

requires staging, search/match processing, and loading to production records. This could include

but is not limited to admissions test scores, prospects, volunteers, personal profiles, academic

knowledge test results, etc.

In the next 12 months, our focus will be to design the initial phase of the Common Data Load

functionality to:

• Produce a proof of concept using a recognized test load as an example

• Utilize File Parser; Field Conversion Definitions, Context Definitions and File Mapping

Definitions components to setup and map test layouts.

• Utilize the CTM data structures and staging components to capture bio/demo data

• Utilize the existing Transaction Setup and Transaction Management Process to enable

staging and posting of data.

• Utilize the existing Data Update Rules to allow the user to determine how existing

constituent data should be updated.

• Construct a new common structure for capturing test data and other optional data. This

new structure will keep in mind the ability to expand the record structures as other

‘common’ data needs are desired.

• Provide ability to create prospects via appropriate mapping definitions

• Construct a new common staging component displaying the populated staging structures.

• Construct new application packages to post test score data and (optionally) prospect and

other data to CS or CRM as part of the existing Transaction Management Process.

• Address the use of delivered Candidate Data in order to redesign and simplify the staging

and core records to avoid duplication and increase efficiency.

• Provide a security structure for the ‘common’ staging component to restrict access to only

those transactions a user can process.

In the future, we plan to:

• Deliver initial file mapping templates for currently supported test score loads which will

serve as the basis for these definitions. Going forward, layout changes will be the

responsibility of the customer.

• Using the new paradigm, we intend to support every currently supported admissions

related test score and data load


33

• Provide for data that is not limited to test scores; this structure delivers the ability to batch

load Prospects from diverse sources.

• Create a Prospect Web Service to populate the new staging structures and utilize the new

application packages.

By creating a common data load mechanism we can provide a paradigm changing methodology

that utilizes Constituent Transaction Management and the File Parser that will allow customers to

control and respond to outside test agencies and to create their own data loads depending on

their business needs.

Admissions and Recruiting: Planned Regulatory Support and Updates

• Studielink (NLD)

- Extension of Studielink messaging framework to encompass regulatory requirements for BRON-HO

- Studielink regulatory update 4.3

- Enhanced usability for Studielink processing and monitoring

• Continued support for the Points-Based Immigration (PBI) process, including the

following targeted updates (UK)

- Additional upload fields for Certificate of Acceptance of Studies (CAS) Details

- Updates to the upload extract and XML creation for bulk data transfer

• Universities and Colleges Admissions Service (UCAS): Continued support for required

2013 updates to the government-managed admissions process (UK)

• Victorian Tertiary Admissions Center (VTAC) regulatory updates. (Australia)

• Queensland Tertiary Admissions Center (QTAC) regulatory updates. (Australia)

Planned Revised Test Score Layouts

GMAT Changes for 2012 - Launching in June 2012, the Next Generation GMAT® exam will

feature a new Integrated Reasoning section, giving graduate management programs a new data

point to differentiate between top candidates. We plan to support these changes as they become

effective and customers are urged to stay apprised of the availability of delivered updates.

Student Records Planned Features

In response to the needs of a growing global customer base, a variety of Student Records related

projects are planned for the next 12 months. Oracle Campus Solutions continues to engage with

the HEUG Student Records Product Advisory Group and other customer groups to identify,

consider and evaluate new development, regulatory initiatives and functional updates.


34

Program Enrollment

In 2011-2012 we introduced the foundation for the Program Enrollment feature functionality.

Using our continuous delivery model we plan to continue with our efforts to deliver this

comprehensive functionality in 2012-2013 which will include:

• Ability to create AIR Course items from the Course Catalog

• Ability to create and assign an Academic Progress Tracker Instance in batch or for an

individual student from the Program/Plan component

• Ability to enroll students in required courses through a batch process

• Program Enrollment: - Applicant and Student Access

- Student Self Service Program Curriculum View

- Student Self Service Enrollment UI (includes exam enrollment)

- Student Self Service view of APT

- Student Self Service view of exam schedule

• Ability to enhance delivered structures utilizing the Common Attributes Framework (see

section on Common Attributes Framework in this document)

NOTE: This new functionality will have a PeopleTools pre-requisite. At the point of

publication of this document, the pre-requisite Tools version will be either 8.52 or 8.53. As

soon as we have determined which Tools version will be required to deploy the planned

Program Enrollment functionality, we will notify the community.

Activity Management

Activity Management allows you to use extensive feature functions to construct basic course

structure and its attributes and to define the result structure that maps marks, grades and

outcomes that are required by various academic areas, programs, and courses applicable to your

institution. We delivered the first phases of Activity Management in 2011-12, in 2012-13 we plan

to deliver:

• The Individual Activities & Marks (IAM) Request which is targeted to populate the

student record for Activity Management including exam activities

• Activity Management Student and Faculty Access:

- Student Self Service view of class coursework requirements

- Examination enrollment – student self service enrollment

- Faculty Self Service updates to coursework

- Activity Rosters

• Grade and Result Calculations


35

- Expert & Developer front end for Rules Engine

- Evaluation by a Rules Engine

- Calculation of course results incorporating penalty marks, resit regulations and capping rules.

- Updating APT and IAM with results from the rules engine

• Ability to enhance delivered structures utilizing the Common Attributes Framework (see

section on Common Attributes Framework in this document)

Campus Solutions Rules Engine

Most institutions have a variety of policies that govern decision making in admissions,

enrollment, academic progress, honors and awards, academic achievement and other operational

areas. These policies typically require the application of complex rules to students, applicants,

degree candidates and even to faculty as they perform various transactions. Policy rule sets vary

between institutions and usually vary within institutions; different rules are applied to

undergraduate admissions applications versus graduate school applications, academic probation

or progression rules vary from program to program, and rules for adjudicating completion of

advanced research vary depending on academic discipline and department.

While policy rules can be very complex, their organization, setup and implementation needs to be

highly configurable and easily expressed by non-technical business owners who have the ability

to define and update them and manage their application to various academic populations.

In 2012-13, Campus Solutions intends to deliver the first phases of a comprehensive CS Rules

Engine specifically designed to support Program Enrollment and Activity Management

functionality. . The first version of the CS Rules Engine is targeted to include the following:

• Ability to create rules that need to execute complex calculations, perform mathematical

functions, and execute transactional evaluations.

• Provide non technical users with a graphical editor in which to edit rules called the Rules

Engine Manager.

• The Rules Engine Manager can be deployed to Novice Users, Expert Users and

Programmer Developers offering each target audience their own set of rules building

capabilities.

• Ability to deploy a secure way of leveraging rules across the system.

• Ability to manage versions and modifications to the rules over time

The initial intention for the CS Rules Engine and the Rules Engine Manager is to provide and

manage rules which apply to the complex structures in Program Enrollment and , Activity

Management. In the future, they are also intended for use in Evaluation Management, Research


36

Tracking and throughout Campus Solutions wherever complex rules are built, applied, and

managed.

Research Tracking

In 2011- 2012, we introduced the first installment of the Research Enrollment Tracking feature

that provided the fundamental structures for addressing the unique requirements of candidates

pursuing research and the administration of their academic life cycle including the management

and evaluation of their thesis. Candidate Management and Thesis enhancements planned for

2012-2013 are:

• Research Topics – expanding their definitions to include internal and external organization

relationships and contact information

• Ability to enhance delivered structures utilizing the Common Attributes Framework for:

- Candidate Management

- Research Topic setup

- Thesis Management

• Supervisor Setup – a redesign of the data structure used to manage research supervisor

information that will use Affiliations to define the supervisor’s role at the university.

Additional supervisor attributes such as qualifications, detailed availability, and internal

and external organization relationships will be added.

• Candidate Consumption and Service Request Processing

- Consumption setup and calculations

- Defining and processing service requests e.g. LOA, load changes, extension requests, etc.

Milestones

Milestones offer important feature functionality for assigning and tracking non-course related

requirements for a variety of students. In conjunction with our efforts to extend this functionality

for managing advanced research students, we are planning to enhance existing milestone setup

and deliver new functionality and accessibility for Milestones in 2012-2013. These updates are

targeted to include:

• Changes to the milestone setup:

- Add fields to the milestone setup table and the milestone template to support calculation of completion dates and terms.

- Ability to identify and allow milestones to be displayed to students in the Student Center and to advisors in the Advisor Center.

- Add the milestone level to the milestone template.


37

• Redesigning the existing student milestones page to improve usability

- Provide the ability to have more than two advisors on a milestone.

- Add attachments to student milestone page.

• Provide a batch process using population selection to insert and update milestones.

• Provide a self service page to display milestones in the Student Center, the Advisor and

the Faculty Center.

Evaluation Management System (EMS)

Most institutions have evaluation policies and processes that require criteria to be applied to

candidates including those for admissions, scholarships, certifications, research dissertations, and

variety of other similarly designed and managed activities.

With the initial foundation for EMS provided in 2011-12, we plan to continue to deliver phased

functionality in 2012-2013 with primary focus on the critical component for fully realizing the

vision for EMS: The Evaluation Center.

The planned Evaluation Center will provide evaluators, acting individually or as part of a larger

committee, as well as those who are administering the evaluation process with a user interface

that assembles the tools they need to manage and conduct evaluations. We plan to develop two

forms of the Center; one for evaluators and one for administrators.

An Evaluator needs a way to enter their evaluation outcome (recommendations, ratings,

reviews/comments) and perform other data entry. The Center is a single location where the

Evaluator can access not only the data or credentials in a virtual candidate folder that contains

relevant materials, attachments or links to documents but also reference/instructional content

regarding the evaluation process. Organizational and collaborative tools can also be deployed in

the Center. A single person may act as an evaluator in various types of evaluative processes, so

the ability to organize and manage their evaluation work list is needed. The evaluator may need

to notify the administrator or contact a colleague regarding an evaluation.

An Administrator needs similar capabilities in the Center but with a 360 view of all evaluative

processes for which they have responsibility. They should be able to monitor progress and

completion of evaluations and drill down to a detail level on a single evaluation. An

Administrator needs to be able to troubleshoot and intervene when issues arise. As an example,

if an Administrator sees that an evaluator has overdue evaluations, the Administrator can trigger

reminders and/or messages to that evaluator. For an Administrator being able to maintain

evaluations either manually or in batch is also essential as is calendaring and messaging controls

relevant to the process.

To support the Evaluation Center, we anticipate developing:

• Setup pages to manage and configure the Center


38

• Self Service security to control display of data, access to content

• Modifications to existing EM setup components to support the Evaluation Center

Workflow and notifications are also planned for delivery to expedite and support the evaluation

process flow. We envision a configurable utility which will allow the administrator to define the

workflow process relative to the evaluation setup. To provide maximum flexibility, we anticipate

providing an administrator with the ability to add their own content for the notifications and

manage timing of notifications.

Other enhancements that we are targeting for EMS in 2012-2013 include:

• Copy function for setup components • Administrative component coding

• Ability to allow for attachments at every level of the evaluation.

Student Records: Planned Regulatory Support and Updates

• Continued support for the BRON process for sectors BO and VAVO (NLD)

• Higher Education Statistics Agency (HESA): Continued support for required 2012/13

updates (UK)

Under Consideration:

Depending on legislative cycles and government agency procedure, our support for regulatory

updates is not always determined in time for inclusion in our Campus Solutions Annual

Statement of Direction. We pursue a disciplined internal process for the ongoing evaluation of

our responses to requests for support of regulatory and legislative updates from our customers.

At publication time, we are still considering the following regulatory projects:

• Key Information Sets (UK)

• Veteran’s Benefits (US)

• Verzuim (NLD)

Oracle Campus Solutions will communicate with customers on an ongoing basis throughout the

year with timely updates on planned additional regulatory deliverables.

XMLP Transcripts: Increased Character Description for Transcript Text (CS 9.0)

Each year, we attempt to enhance and update the capabilities available with the flexible XMLP

Transcript introduced with Campus Solutions 9.0 and in 2012-13 we plan to continue this

practice. Currently, the descriptive text that we allow for free form Transcript Text is limited to

90 characters. A number of our customers have expressed the need to expand this limit as they

encounter requirements for posting certification statements, coursework explanatory notes and

other relevant content to be displayed on an academic record. Our aim is to expand the limit to

1000 characters.


39

Academic Advisement Planned Features

Campus Solutions continues to engage with an active advising user community and with the

Academic Advisement Product Advisory Group to identify and consider enhancements to

Academic Advisement functionality.

Academic Advisor Notes and Communications

Academic Advisors provide many of the key services that promote retention, timely graduation,

and mentorship in most institutions. Along with classroom faculty, academic advisors represent

the most important human link between an institution and the student. It’s imperative that

advisors provide the best communication, the most timely information, and high quality

interactions with advisees. Advisors assist students in making significant academic decisions

which require timely communication with their students and notation to student advisement

records. In the coming year, Campus Solutions plans to focus on supporting and sustaining the

services that your academic advisors provide. We plan to augment advisement functionality by

delivering enhancements that enable advisors, faculty, and staff to record notes about their

interactions with students when providing important information regarding discussions,

decisions, and plans and to provide functionality focused on facilitating communication with

students. Planned enhancements include:

• The ability for advisors to record notes and conversations and identify the type of

conversation.

- To this end, institutions can define the types of notes--whether it is related to class permissions, changes in program of study, exceptions, graduation, and so on.

• Enable two-way communication between students and advisors, as driven by the

institutions’ preferred methods of communication.

• Enable institutions to manage the respective users’ ability to view and or edit advisor notes

- Offer exposure of remarks and communications to users, as appropriate, according to institutional or external requirements.

- Provide the ability to secure notes, as appropriate, based on the institutions’ role-related security.

Financial Aid Planned Features

Financial Aid professionals live in an ever-changing world of highly regulated compliance while

striving to most efficiently deliver financial aid to students - all the while counseling students and

parents on financial options.

Regulatory Updates are delivered in each of the four scheduled maintenance bundles per year:

• October Bundle – Regs 1: ISIR load, INAS-IM, PROFILE, Return of Title IV


40

• January Bundle – Regs 2: Database Match and Eligibility updates, NSLDS, Verification,

COD Processing updates for Direct Lending, Pell Grants

• April Bundle – Regs 3: Redeliver INAS-FM, Pell Schedules, CommonLine Updates

• July Bundle – Regs 4: FISAP, Satisfactory Academic Progress

There are often additional updates we deliver, based on mandates from the US ED or other

country’s legislative changes. Some of the enhancements (in addition to annual regulatory

updates) planned for the next 12 months are listed below.

• PELL Lifetime Eligibility Used tracking – We plan to deliver updates to aggregates

processing and FA packaging to allow users to incorporate PELL lifetime eligibility data

coming from NSLDS.

• External Awards Processing – Plan to deliver enhancements to allow users to process

External Awards in “offer only” status.

• Population Updates – Plan to deliver additional support for population updates based on

customer input/priorities.

• PROFILE Delete – Plan to deliver the functionality to allow users to delete PROFILE

application records.

Financial Aid (UK): Regulatory Updates

• Student Loan Company (SLC; UK): Support for web services version and update HEI

version 3.0 changes

Student Financials Planned Features

Student Financials provides support for calculating, billing and collecting tuition and fees along

with other related student charges, payment plans, refunds, global invoicing, and workflows. A

key part of managing student receivables is disbursing financial aid. The following outlines the

new capabilities we have planned for the next 12 months.

Group Data Entry: Enhanced Functionality

Most institutions have transactions that need to be posted to a specific set of students outside of

tuition calc. Currently, the Student Financial External File Load functionality will allow an

external file to be loaded into Group Line to post various types of transactions.

The planned enhancement to Group Data Entry and Group Corp Data Entry will make use of

the Population Selection tool. Student Financials is planning on providing the capability for the

institution to use a query or an equation to write the criteria to identify the population for a

specific transaction. In addition, the file load capability of Pop Selection can be used.


41

Tuition Waivers: Enhanced Functionality

We are evaluating additional options for the application of waivers within the tuition calculation

process.

• Several institutions have requested that waivers be applied proportionally across the

installments created through tuition calculation. Each of these waivers would “stick” to

the installment and provide for the student’s bill to reflect accurately.

• In addition, students may be eligible for multiple waivers. Functionality to allow the

waivers to be prioritized and the flexibility of calculating on the net or the gross is being

reviewed.

1098T Delivery: Regulatory Support

We plan to make the appropriate update to this form in July of each year.

Contributor Relations Planned Features

Contributor Relations customers have identified their top priorities for attention over the next

year. Several of these enhancements are being designed now and others are under consideration

for delivery in the next 12 months. CR customers need to extend the application to leverage

third party solutions, such as social networking, automated contact systems and distinctive UI for

their communities. As such, they will benefit from the features and frameworks described in the

Campus Community section above.

Some of the enhancements targeted for the next 12 months are listed below.

Giving Club: Automation and Configurability

A top priority for the Contributor Relations Product Advisory Group is focus on the Giving

Club structure and support, primarily looking at ways to reduce manual entry to maintain the

Clubs, to add better date control to the structure and to add more flexibility and rule-based

processing in general. We are in the process of evaluating the entire Giving Club definition and

processing controls to determine how to phase in desired enhancements.

Workset Enhancements: Creating efficiencies and ability to collaborate

Worksets are a unique framework in CR that support the ability to work through a set of selected

records regardless of whether the constituent is a person or an organization. The number two

priority from the CR PAG was to enhance the capabilities of this structure; some examples

include:

• Sharing of Worksets (public and private options)

• Ability to add ID ids in a batch mode (mass assign)

• View by Alpha within worksets


42

• Join more than two worksets

• Expand use of worksets into other CR areas of the product.

Long Name Field

Add the ability to add the long name fields to person and organization records.

Publications Management

Add the ability to track to which address a constituent wants a particular communication type

sent.

Pledge Management

Extending pledge schedule and pledge reminder features to more easily update the schedule and

track reminders.

Affiliations: Extending the Solution

A number of enhancements are being planned for the Affiliation feature. Those include:

• Context Data Inclusion – An additional element of the Affiliation definition will be

“Context Data”. This will allow the specification of additional record/field pairs to be

associated with the affiliation code and included as part of the data when the affiliation

message is published. We expect this enhancement to enable more flexibility and

definition when the affiliation is used in conjunction with other business processes such as

Identify Management.

• Affiliations Example Guide – Document and software package that contains three sample

Affiliations and a unit-testing framework for the Affiliation Framework. The following

sample Affiliations are included: Worker, Applicant and Student. This planned

documentation and examples will enhance customers understanding of the affiliations

feature and their ability to set up and test their own affiliations.

PeopleSoft CRM for Higher Education 9.1

CRM for Higher Education Prior-Year Updates

When combined with Campus Solutions, PeopleSoft CRM for Higher Education provides your

institution with robust capabilities for extending and enhancing the types of outreach and

interactions you can provide to your various constituents. The pre-integrated solution provides

you with numerous capabilities that are complementary to Campus Solutions, extending what is

offered in Campus Solutions and in many cases filling gaps in what Campus Solutions provides

on its own. Over the past year, we have delivered even more robust functionality to provide you

with more flexibility in how you manage your constituent interactions.


43

Audience Builder Enhancements

To provide additional flexibility in defining audiences in CRM Marketing, we have introduced

several additional operators to audience builder. These new operators are all centered around

your ability to generate date and time sensitive communications and interactions. These new

operators include:

• Equal to, Prior to, After, Offset from Current date

• Equal to, Prior to, After, Offset from Current day, month, year

• Equal to, Prior to, After, Offset from Current time

Marketing Center Security

We have provided a new security feature called Marketing Centers. Modeled after Recruiting and

Application Centers in Campus Solutions, this new security feature allows you to define

Marketing Centers, which are then attached to various marketing objects and campaigns as well

as constituents. Only users who are authorized will then be able to view or use those objects and

constituents. This feature is especially useful for those institutions that have competitive

recruiting and admissions across different organizational units, (e.g., multiple campuses, or

departments such as Graduate Mechanical Engineering and Graduate Civil Engineering).

Person Basic Synch Enhancements

Person Basic Synch (PBS) is one of the primary EIPs we use for integrating person or

constituent data between Campus Solutions, HCM, and CRM. In order to enhance and

streamline the processing of new constituent records in CRM, we have delivered a number of

new enhancements to Person Basic Synch for CRM 9.1, including:

• Person Basic Sync and Fullsync subscription code redesign – provides additional

protection against running a Fullsync operation multiple times.

• BORM code modification

• New configuration options for Role Contact Method updates

• Decouple Search Match for Person Basic Fullsync

CRM for Higher Education Planned Features

We also plan to continue our strong momentum and roadmap for PeopleSoft CRM over the next

year with the following planned enhancements:

Online Marketing Single Sign-On

This planned enhancement will improve user access and usability by enabling single sign-on

access to Online Marketing (OLM) and Campus Solutions or HCM from an OLM dialog.


44

Multi-Row Profiles in Online Marketing

In order to simplify the collection of data in a form or survey in Online Marketing (OLM), we

are planning to deliver this enhancement to enable multiple responses (multiple rows) to a single

question. This is especially beneficial for collecting interests in multiple academic or

extracurricular areas, among many other uses.

Guests on Events

Many of your constituents want to bring a guest or multiple guests to your campus events. This

planned enhancement will enable the constituent to identify specific guests they intend to bring

to an event, enabling your institution to track the specific individuals as well as to plan

accordingly for space, meals, etc.

OLM emails on the 360

It order for your CRM users to see an accurate representation of the constituent and make timely

and appropriate decisions, the user must be able to see a complete and up-to-date summary of all

the interactions for that constituent. We are planning to deliver this enhancement that will

display on the Constituent 360-Degree View email interactions generated directly through OLM.

PCI Compliance in Online Marketing

Like you, we are concerned about the security of your user’s data. We want your Online

Marketing (OLM) transactions to meet the highest standards of security and compliance, and

with this planned enhancement we will ensure that these transactions are in compliance with PCI

standards.

Campus Solutions Warehouse (An EPM 9.1 Solution)

PeopleSoft Campus Solutions Warehouse provides a powerful foundation for making more

informed, strategic decisions about your enrollment efforts, course offerings, and student

population. PeopleSoft Campus Solutions Warehouse is comprised of four content-specific data

marts which, when deployed together, constitute a comprehensive, integrated analytic platform.

These data marts can also be deployed modularly to accommodate your specific business or

budgetary requirements. The four data marts are: Admissions and Recruiting, Student Records,

Campus Community and Student Financials. We now also provide a fifth, optional, data mart for

PeopleSoft CRM content if you are using that product for student recruiting, enabling you to do

true end-to-end analysis and planning for your recruiting and outreach efforts.

Campus Solutions Warehouse Prior-Year Updates

During this past year we have continued to enhance the Campus Solutions Warehouse with a

number of strategic enhancements to support the Higher Education community.


45

Snapshot Tables to Support Institutional Research

Snapshot tables are important for Higher Education customers, especially Institutional Research

offices, as they enable consistent, point-in-time reporting and analysis as well as longitudinal

analysis. Also known as “frozen files”, these snapshot tables allow you to take a data extract as of

a particular point in time (e.g., start-of-term, census date, mid-term, end-of-term) and then

preserve or locking that extract so that no further updates to it are allowed. We have designed the

system to enable you to create as many of these snapshots as you require and on whatever

schedule or frequency you require to meet your institution’s unique reporting needs.

• Admission Applications Snapshot (detailed by application)

• Student Program Stack Snapshot (detailed by student)

• Enrollment Snapshot (detailed by student and class)

• Completions Snapshot (detailed by student – degrees/certificates awarded, graduation

rates)

• End of Term Performance Snapshot (detailed by student)

Insttutional Reporting Dashboards

In addition to the new snapshot tables described above, we have delivered a number of new

dashboards and reports to work with the new snapshot tables. These dashboards and reports are

delivered as part of the Fusion Campus Solutions Intelligence product, which requires OBIEE to

access and display the results. The new dashboards and reports that we have delivered over the

past year include:

• Student Enrollment dashboard, which includes Student Enrollment Summary, Degree

Seeking Students Summary, Non-Degree Seeking Students Summary, and Student

Enrollment Analysis by Athlete

• Degree Completions dashboard, which includes Degree Completions Summary, Degree

Completions Summary By Primary Major, Degree Completions Summary By Secondary

Major, Degree Completions Award Trend, and Graduated Trend By Athlete

• Admissions dashboard, which includes Admissions and Enrollment Summary, Trend

Analysis by Admit Term and Test Scores Submitted (SAT/ACT), Student Test Scores

(SAT/ACT) Summary, and Applicant External Organization Summary by GPA

Materialized Views

In order to improve on the performance of incremental loads to the warehouse, we have

introduced Materialized Views. A materialized view log is a feature of the Oracle database and is

similar to an AUDIT table; it is the mechanism used to capture changes made to its related

master table. Rows are automatically added to the Materialized View Log table when the master

table changes. The Oracle database uses the materialized view log to refresh materialized views


46

based on the master table. This process is called fast refresh and improves performance in the

source database for the ETL load from the source Campus Solutions database to the Operational

Warehouse (OWS). Thus far we have delivered the materialized view log solution for six source

tables:

• PS_STDNT_CAR_TERM

• PS_ACAD_PROG

• PS_ACAD_PLAN

• PS_ADM_APPL_PROG

• PS_ADM_APPL_PLAN

• PS_ADM_APPL_DATA)

We intend to expand this with future releases.

Load Validation and Error Reporting

PeopleSoft EPM 9.1 provides a new optimal ETL design to capture job statistics for PeopleSoft

ETL jobs. A common component called SEQ_J_Handle_DATA_VALIDATION is used to

capture job statistics and stores the statistics in the Data Validation Summary table.

Additionally, the new Data Load Analysis dashboard for OBIEE provides consolidated and

summarized error data and job run statistic reports based on the data contained in the Data

Validation Summary and Data Validation Control tables. The user friendly reports help you

analyze error data and data completeness so that identifying the tables and data that fail

validation is quick and simple.

OBIEE 11g Certification

PeopleSoft EPM 9.1 includes OBIEE 11g (OBIEE 11.1.1.5) certification for the PeopleSoft

Fusion Campus Solutions Intelligence product. The delivered repository and Webcat have been

certified and customers can now take advantage of new features delivered in that OBIEE release.

Refer to 11g documentation for a comprehensive list of features.

PeopleSoft EPM 9.1 Feature Pack 1

In addition to the new features and functionality described above, the PeopleSoft EPM team has

released Feature Pack 1 (FP1) for the EPM 9.1 release. FP1 includes a consolidation of the

product maintenance and updates provided in Bundles 1-8, along with updated and consolidated

PeopleBooks and other documentation. While the Feature Pack is targeted at new customers

beginning an implementation, or existing customers planning an upgrade to the EPM 9.1 release,

existing EPM 9.1 customers will equally benefit from the reissued and consolidated PeopleBooks

documentation.


47

Campus Solutions Warehouse Planned Features

During the next 12 months, Oracle plans to deliver:

Enhanced Support for Institutional Research

We intend to continue to enhance the support we provide for the Institutional Research Office

with the delivery of additional snapshot tables, specifically for reporting and analyzing Student

Retention. In addition, we intend to provide additional dashboards and reports to support the

various snapshot subject areas (to be delivered as part of the Fusion Campus Solutions

Intelligence product, with OBIEE).

Data Lineage at the Field Level

As we continue to enhance and expand the use of the Campus Solutions Warehouse, we find we

also need to provide enhanced support for its usability. With any reporting tool or data

warehouse, it’s crucial that users understand the data and for them to be able to tie the data in the

warehouse to its source, in this case Campus Solutions. To provide additional support for this,

we intend to provide support for data lineage at the level of the individual data elements. This

will enable report writers and analysts with the ability to identify specifically where the data came

from within Campus Solutions.

Materialized Views

In Bundle 8, we delivered the materialized view log solution for the first six source tables in

Campus Solutions. In the next year we intend to continue to build on this and plan to deliver

materialized view logs for additional Campus Solutions source tables.


48

Conclusion

The Campus Solutions Continuous Delivery Model, introduced more than three years ago, has

resulted in significant new additions to the product delivered in consumable chunks throughout

the year. Many features are delivered in multiple phases in order to ease the analysis and testing

burden. Under the Continuous Delivery Model, new features are delivered in an inactive status,

so the institution can choose to deploy the feature when they have the window of opportunity.

As Campus Solutions moves to a service-oriented architecture, many of these new features

leverage web services and the Tools-based integration technologies, resulting in a need to ensure

your campus IT staff are skilled in using those technologies.

With the rapid pace of delivery of new features throughout the year, it is critical that our

customers are aware of the new capabilities being delivered. After all, customers expect Oracle to

deliver functionality that increases their productivity and lowers their overall cost of ownership

for our application. While we recognize that each institution’s unique business cycle and priorities

may not allow them to deploy the new functionality as it becomes available, we strongly

encourage institutions to stay current on what we are delivering and endeavor to understand how

the features could be leveraged.

There are a number of ways to stay informed of what is being delivered by the Campus

Solutions team:

• Campus Solutions Newsletter published by the Support team

• Single page on My Oracle Support dedicated to Campus Solutions information (see

DocID 975038.1)

• Home Page for all documentation related to Campus Solutions (see DocID 751540.1).

• This Statement of Direction, published annually

• Detailed Pre-Release Notes published prior to the general availability of each Additional

Features event (publication is highlighted through each Campus Solutions list serve on

HEUG online)

• Multiple sessions at the annual Alliance Conference (and plans for presenting at other

HEUG conferences throughout the year)

• Advisor calls and recorded webinars that accompany each Additional Features release

One of the key messages from Alliance 2012 was that our customers expect a simpler experience,

a more productive experience and, in fact, a transformative experience with Campus Solutions.

Customers understand we are on an evolutionary path to realize this transformative experience

by building out new capabilities within the product, to work in parallel with existing business

processes. They also know that we’re embracing new technologies that will support the types of

advanced capabilities they expect. They heard more about our plans to modernize how their


49

users engage with Campus Solutions, which begins with a simplification focus. Finally, the true

reflection of success in meeting customer expectations is in how well we enable your productivity

in using Campus Solutions. We believe we have the right roadmap for this year and next to

realize these ambitions.

Campus Solutions 9.0

May 2012

Oracle Corporation

World Headquarters

500 Oracle Parkway

Redwood Shores, CA 94065

U.S.A.

Worldwide Inquiries:

Phone: +1.650.506.7000

Fax: +1.650.506.7200

oracle.com

Copyright © 2012. Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and

the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other

warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or

fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are

formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any

means, electronic or mechanical, for any purpose, without our prior written permission.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective

owners.

0110