1. Presented by Bob Diehl bdiehl@towson.edu June 13, 2003 Configuration Management and Version Control in PeopleSoft

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

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

4. Hardware Architecture - Production

5. Hardware Architecture - Development

6. 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

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

8. 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

9. Environmental Model - Databases

10. Environmental Model – Databases and LOCs

11. 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) 7.6 - Human Resources (3) 8 - Human Resources (2) 7.6 - Pension Administration (1) 7.6 - Student Records (2) 7.6 - 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: 505959000 Resolution Type: Application Date Posted: 2002-06-06 10:04:20.0 Required For: N\A Supersedes: None URL To Resolution ID: 103172 http://www4.peoplesoft.com/cchomepage.nsf/mainloginnew?openagent&url=192.206.43.125/servlets/psportal/peoplesoft8/?url=

12. The Process – Log it

13. The Process – Download/Import

14. The Process – Impact on TU Mods

15.  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

16. The Process – Move to QA

17. The Process – Move to Production

18. The Process – Document Your Progress

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

20. STAT – CSR Console

21. STAT – Tracking an Upgrade or Fix

22. STAT – Coordinating Object

23. STAT – Automated Object Distribution

24. STAT – TU Enhancement Workflow

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

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

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

28. Discussion