The CC PAG would like to give an update on our goals for this year which emerged from the 2010 PAG Summit. We’re very interested in feedback from our Campus Community community :-), so please feel free to send any tips, questions, or suggestions to me, your friendly CC PAG Chair, at nutta003@umn.edu.
- Identify key requirements and best practices for periodic verification
This was our highest priority that came out of the 2010 Summit. We found that each of our schools had a business need for students to verify or validate various types information, and we suspected that there was a growing need among the greater HEUG community. Hopefully, you noticed our recent HEUG Online survey which appears to be confirming our suspicions. Our next step will be to synthesize the data from our survey and work with Oracle to translate that into a business case. We'll keep you posted on our progress via this blog.
- Stay engaged on Identity Management (IDM) and Master Data Management (MDM) initiatives
Oracle has devoted a lot of resources to PeopleSoft related IDM and MDM initiatives over the last couple years. The fruits of this labor can be seen in the Constituent Web Services package that came with Feature Pack 1 as well as modifications they’ve made to their data hub. The CC PAG have been very involved throughout these initiatives as most of the data they are managing falls under the Campus Community umbrella, and we intend to stay engaged as we believe they will be essential tools for facilitating the integration separate CS/HCM instances in a post HCM 9.1 world. Currently, we are working with the TAG to identify how we can each help educate and advocate around this topic.
- Better organize communications about CC PAG activities via the cc.ps list service, Issue Tracker, and HEUG Online Newsletters
We have begun with cleaning up our Issue Tracker back log. We’ve started by asking our Oracle representatives provide initial scope and feasibility analysis on all of our open issues. Our next step will be to reprioritize our issues based on current demand and their likelihood of being addressed by Oracle. We will also be communicating with the people involved with the individual issues themselves.
- Support the CS/HCM 9.1 integration
We haven’t begun work on this goal in earnest yet. We are currently on the lookout for schools who plan to be the earliest adopters of HCM 9.1, and we continue to advocate with Oracle to share information as it becomes available. Please stay tuned, and share your split/integration stories on the CC list serve as you go through the process.
- Identify emerging best practices from the new tools that come with Feature Pack 1 (e.g. Affiliations, CWS)
This is another goal where we haven’t focused on yet. We’re planning to gather information later in the year as more people begin to adopt the new features.
- Identify new priorities for the student system of the future
This is a less concrete goal than the rest. As you may have heard several times at the 2010 Alliance Conference, Oracle considers CS to be a mature product which is one of the impetuses for them separating the CS/HCM systems. The CC PAG found that, overall, we agree with this sentiment. While there certainly are features what we all still want and/or need, we feel that CS platform and particularly the Campus Community module have reached a stable and robust set of features. Consequently, we want to take some time this year to think outside of the box a little about what universal campus needs might emerge in the future.