Presented by Bob Diehl June 13, 2003 Configuration Management and Version Control in PeopleSoft

Agenda  Towson’s Current Architecture  New Challenges  First Steps  The Process Overview  Quest Stat  Lessons Learned  Discussion

Current Project Environment  PeopleTools  Oracle  People Soft Applications  Student Administration  Admissions, Student Records and Financial Aid – Live  Student Financials – 7/2  Human Resources/Payroll – This weekend

Hardware Architecture - Production

Hardware Architecture - Development

Initial Upgrade and Fix Challenges  Complexity  Test and Production  10 Plus  Responsibility  UMS Service Center  Just us  Managing Object Access During Development  Impact on Planned Business Rules

New Challenges  Towson Enhancements  Delivered PeopleSoft Objects  PeopleSoft Object Dependencies  Update Windows  24 x 7 Availability  Telecommuting  Timely Updates  Impact on Production

First Steps  Identify Proposed Environment Model  Database Instances  Common Lines of Code (LOC)  Determine Migration Processes and Decision Points  People Soft Upgrades and Fixes  TU Development

Environmental Model - Databases

Environmental Model – Databases and LOCs

The Process - What’s new this week ? Incidents Posted: The number in parenthesis indicates how many incidents have appeared this week under each of the products listed. (1) 8 - Campus Community (3) Human Resources (3) 8 - Human Resources (2) Pension Administration (1) Student Records (2) Time and Labor (1) 8 - Time and Labor 8 - Campus Community Apply to Product: Campus Community 8 Platforms Impacted: All Report Title: SA 8.0 delta for HRMS 8 SP1: HR-e 2002 Bundle #2 Report ID: Resolution Type: Application Date Posted: :04:20.0 Required For: N\A Supersedes: None URL To Resolution ID:

The Process – Log it

The Process – Download/Import

The Process – Impact on TU Mods

 Still needed ?  Changes to functionality ?  Step 2a - Mods in Production  Incorporate into delivered objects  Step 2b – Mods in Development  Move PS U&F to QA for testing  Move to Production  Re-establish objects in Development

The Process – Move to QA

The Process – Move to Production

The Process – Document Your Progress

Why Quest STAT ?  Object Coordination  Report Object History  Audit Trails  Automate Object Distribution  Application Designer Integration  TU Enhancements Workflow

STAT – CSR Console

STAT – Tracking an Upgrade or Fix

STAT – Coordinating Object

STAT – Automated Object Distribution

STAT – TU Enhancement Workflow

Lessons Learned  Model First  Compare/Report  Document Your Progress  Stay on Top  Familiarize with The Upgrade & Fix Website  Look for a Tool

More Lessons Learned  Model Again – Determine how to reapply mods  Documentation  Functional and Technical Specs  Track PeopleSoft Object Dependencies  Development Standards

Current Challenges  Impact Analysis  Testing  Scripts  Timing  Weekends  Who  Reviewing Existing Documentation

Discussion