Information Technology Support Goals for PeopleSoft

Goal 1:  Create a test environment that will closely resemble our future implementation
  • Build 2 development servers
  • Install PeopleSoft applications & prepare the environment
  • Work on the data conversion and data modeling to populate  the PeopleSoft database
  • Use our data to prototype the future implementation
Goal 2:  Help to identify current business rules that are logically embedded and are transparent to the users
  • Review the control table setup that is completed by the user base; participate as necessary
  • Programmers begin identifying embedded logic within their areas of support
  • Document the areas that are discovered
Goal 3:  Keep parallel testing to an absolute minimum
  • Require testing & sign-off from programmers, user base, project manager, and management prior to implementation
  • Schedule ample time for testing from all stakeholders (test major events: registration, grade processing, month-end...)
  • Provide appropriate access to testing environments for stakeholders
  • Ensure ample resources are available at "go live" to support any problems since backing out is disastrous without parallel efforts
Goal 4:  Help ensure successful fit gap sessions
  • Help identify the functional experts we believe to be critical for fit gap participation
  • Review the fit gap agendas, participants, and RSVP's
  • Identify areas that require special fit gap sessions (from our list of current interfaces)
  • Ensure programmer participation in fit gap sessions
  • Review fit gap outcomes and help identify omissions
  • Provide feedback to Bernie
Goal 5:  Help identify any "key" omissions, which could create implementation failures
  • Review the functional goals and help discover any critical omissions within their goals
  • Identify & define interfaces with third party products
  • Provide feedback to Bernie of major issues (touchtone, MIS data, scheduling)
Goal 6:  Convert as much data as possible
  • Analyze the pros & cons of data quantity
  • Analyze technical issues surrounding the data that is not converted, assuming some retrieval is required
  • Review input from user base and management regarding data retention requirements
Goal 7:  Decline all "special requests" for Information Technology; the steering committee should be used for any exceptions
  • Require all computer service requests to be documented
  • Submit requests to the steering committee for guidance & prioritization
Goal 8:  Don't rely on only one technical individual as a resource for support
  • Create "backup" technical support as much as feasible
  • Allocate time for cross-training staff
  • Encourage district approach of cross-training the function experts
Goal 9:  Retire the Alpha system modules immediately after "go-live" (Information Technology cannot support two complete environments!)
  • Create a retirement strategy for the Alpha system
  • Eliminate user access to areas
  • Lock data elements (as feasible)