Avoiding the Big C: Strategies for keeping your Customizations to a minimum
Session Number: 30393
Track: Project Management & Life Cycle
Sub-Categorization: Implementation
Session Type: Tips and Tricks
Tags: Best Practices, business process review, Customizations, Implementation tips, maintenance, Upgrade Challenges
Primary Presenter: Thomas Ball [Senior Practice Director US Higher Education Delivery and Business Development - Oracle]
Co-Presenter: Joaquin Ramos [Senior Consultant - Oracle]
Time: Mar 21, 2012 (09:15 AM - 10:15 AM)
Room: Ryman Studio PQR
Learning Objectives from Session: Understand how to assess the long-term cost of customizations; Recognize the difference between types of customizations; Learn techniques for recommending functional process changes instead of technical customizations.
Product: PeopleSoft
Version Presenting: N/A
Level of Customization: None or N/A
Level of Partner Integration: Partner Alone
Project Phase: Implementation
Project Go Live: N/A
Target Audience: Functional
Audience Level: General
Your Training in this Area: PeopleSoft Campus Solutions
Project Management
Description: While customizations to your Campus Solutions system may seem absolutely necessary at the time, schools often discover that they were not as critical as originally believed. Many of them can cause long-term, maintenance headaches that lessen the value of the system. Learn how some schools have taken steps to reinterpret policies and adjust business processes in an effort to make the CS system work as delivered. During this interactive session, tips will be shared about how to prioritize alternatives to delivered CS functionality and how to weigh the short term benefits of customizations to the long-term costs associated with their maintenance. Since some customizations are unavoidable, a non-technical explanation of the differences between a modification, bolt-on, and interface will be provided. This presentation is geared toward new implementers seeking advice and those looking to retire customizations as part of an upgrade or a maintenance milestone.
Session Number: 30393
Track: Project Management & Life Cycle
Sub-Categorization: Implementation
Session Type: Tips and Tricks
Tags: Best Practices, business process review, Customizations, Implementation tips, maintenance, Upgrade Challenges
Primary Presenter: Thomas Ball [Senior Practice Director US Higher Education Delivery and Business Development - Oracle]
Co-Presenter: Joaquin Ramos [Senior Consultant - Oracle]
Time: Mar 21, 2012 (09:15 AM - 10:15 AM)
Room: Ryman Studio PQR
Learning Objectives from Session: Understand how to assess the long-term cost of customizations; Recognize the difference between types of customizations; Learn techniques for recommending functional process changes instead of technical customizations.
Product: PeopleSoft
Version Presenting: N/A
Level of Customization: None or N/A
Level of Partner Integration: Partner Alone
Project Phase: Implementation
Project Go Live: N/A
Target Audience: Functional
Audience Level: General
Your Training in this Area: PeopleSoft Campus Solutions
Project Management
Description: While customizations to your Campus Solutions system may seem absolutely necessary at the time, schools often discover that they were not as critical as originally believed. Many of them can cause long-term, maintenance headaches that lessen the value of the system. Learn how some schools have taken steps to reinterpret policies and adjust business processes in an effort to make the CS system work as delivered. During this interactive session, tips will be shared about how to prioritize alternatives to delivered CS functionality and how to weigh the short term benefits of customizations to the long-term costs associated with their maintenance. Since some customizations are unavoidable, a non-technical explanation of the differences between a modification, bolt-on, and interface will be provided. This presentation is geared toward new implementers seeking advice and those looking to retire customizations as part of an upgrade or a maintenance milestone.
