Skip over navigation

About Us

What is Person Data?
Person Data can be broadly thought of as all Biographic/Demographic data related to a person as well as data related to their affiliation with the University. The Campus Community application, which is part of the PeopleSoft HCM/CS enterprise application, is the authoritative source for person related data for the University. It exchanges person related data with a variety of systems on campus via the Interface Hub. Person data resides in a variety of systems on campus and keeping this data synchronized and consistent across the various systems is crucial for the effective operation of University applications. One of the key systems that Campus Community propagates person data to is the University provisioning system which provisions accounts and determines access to technology resources based on the affiliation and business role of the person.
Why a Person Office?
Given the pervasive nature of person data and its impact, there is great value in putting in place a single point of contact that can serve as both the ‘champion’ for person data as well as the clearing house for all issues related to person data. The overall quality and consistency of person related data at Princeton has been steadily improving, especially since the implementation of the PeopleSoft HCM/CS application and the interface hub. Nevertheless, given the various business applications at Princeton that hold person data and the data flow between them, coupled with the various exceptions to guidelines/rules that exist on campus, there is always more to be done to enhance data quality, both operationally and strategically.
Another consideration is the complex nature of the University’s needs related to account provisioning and access to technology resources based on a person’s affiliation and business role. OIT recently implemented PUaccess (Princeton’s enhanced authentication service) to provide a more secure authentication mechanism for University applications as well as the ability to have single sign-on. Also planned is the implementation of Oracle Identity Manager (OIM) as a replacement to the APS. The current Account Provisioning System (APS) has various limitations that prevent these needs from being met fully. A significant amount of manual intervention is required.  
With these two initiatives, OIT is taking significant steps towards delivering one of the elements of building a services infrastructure, namely, implementing a comprehensive and secure authentication and authorization system that enables members of the extended Princeton community to access information services. For this goal to be effectively met, we see the need for a group that will work with both business offices and OIT departments that support these applications to co-ordinate the effective rollout of PUaccess across campus applications as well as ensure the effective operation of OIM. The Person Office will take on this role.