University of Colorado

Through the Higher Education Constituent Hub (HECH) and Oracle Data Quality, the University of Colorado is now able to see its 1.5 million constituents across three campuses within a single, secure view.

The Problem:

Over the past decade, the University of Colorado’s PeopleSoft Human Capital Management (HCM) system and legacy Student Information System (SIS) were not integrated around constituent data, so each of the university’s three campuses created their own procedures and systems to manage the data.  The result was that individuals received at least two or more IDs, which, for a long time, were coordinated using SSNs in a custom database dubbed the “Registry,” which had severe limitations and was expensive to manage.  Additionally, identity management was not synchronized with constituent data, so security risks became a concern.

In 2004, CU responded to federal mandates by launching an SSN-remediation project, which eliminated the ability to use SSN as a unique ID.  The project further exacerbated CU’s ability to synchronize constituent data within and across campuses.

In 2007, CU decided to retire its legacy Student Information System (SIS) and replace it with Oracle’s PeopleSoft Campus Solutions (CS) 9.0, which now needed to be synchronized with the existing HCM system

Compounded, these issues created a complicated and disconnected web of constituent information that was time-consuming and awkward to manage.

What We Did:

Based on our expertise in MDM and our long-standing partnership with Oracle, CU engaged LumenData to create a centralized way to persist and manage bio/demo data for its constituents (students, alumni, faculty, parents, donors, etc.).

The HECH implementation included:

  • De-duplication and synchronization of constituent information across HCM 8.9, CS 9.0, and Oracle PeopleSoft Enterprise CRM 9.0
  • Publication of constituent information to 34 downstream systems, including campus directories, identity (user) provisioning systems, and numerous administrative and academic systems
  • Retirement of expensive custom solutions, including the Registry, to eliminate redundant and difficult-to-manage business logic and to expand integration capabilities, such as moving from nightly batch to real-time updates
  • Elimination of various “exception” constituent provisioning systems previously installed to circumvent feature gaps in the Registry

With the newly acquired single view of the truth, CU could now leverage high-quality, real-time data from across its three campuses, reduce IT time and costs, and increase campus system security.