University Of Massachusetts

1. University Of Massachusetts PeopleSoft HEUG Conference 2003 Managing Third Party Products With PeopleSoft March 17, 2003 • Bill Smith • Univ. of Massachusetts Infrastructure Project Manager • Lee Hoelscher • Accenture Tech Manager

2. University Of Massachusetts • Business Metrics • 5 Campuses • Central Presidents Office • 2,000 HR Users – (120 concurrent) • 2,700 Fin Users – (100 concurrent) • 35,000 Employees • PeopleSoft HRSA 7.6 – Went Live March 02 • PeopleSoft Financials 7.5 – Went Live July 02

3. University Of Massachusetts • Technical Metrics • Oracle 8.1.7 (9i with PeopleSoft 8.X) • Sun UltraSPARC II 4500 and 450 servers and Sun UltraSPARC III 3800’s • Solaris 8 • Citrix MetaFrame XP • W2K web servers

4. University Of MassachusettsThird Party Tools Inventory

5. University Of Massachusetts • Third Party Tools • Security • Batch Scheduling • Report Distribution • Experience • Selection process through production support • Lessons Learned

6. University Of MassachusettsThird Party Tools Inventory

7. University Of MassachusettsThird Party Tools Inventory Security – PentaSafe (acquired by NetIQ): Database Security Manager (DSM) and Password Manager (PM) • Business Requirements • Why PentaSafe DSM and PM? • Lessons Learned

8. University Of Massachusetts • Security Business Requirements • Decentralized Security Maintenance (campus-based security administrators; help desk) • Password Management & Policies • Audit Security Administrator Activity • Password Synchronization • Intrusion Detection

9. University Of Massachusetts • Why PentaSafe DSM and PM? • Tools evaluated (DSM & PM from PentaSafe, MORE Systems – went out of business) • DSM – decentralized security admin across multiple databases (HR, FIN, Rptg) • PM – provides password aging, history, policy enforcement, break-in detection, and DB synch • No other Tools met Requirements prior to V8

10. University Of Massachusetts • Lessons Learned – Security • Establish tool in test environment that mimics production for testing config changes as well as upgrades & fixes • Develop & test real-life scenarios early on during implementation • Understand future direction of PeopleSoft relative to meeting business requirements

11. University Of MassachusettsThird Party Tools Inventory

12. University Of MassachusettsThird Party Tools Inventory Batch Scheduling – BMC: Control-M • Business Requirements • Why BMC Control-M? • Lessons Learned

13. University Of Massachusetts • Batch Scheduling Business Requirements • Job sequencing with inter-dependencies • Data file movement and sensing input file arrival • Mixing PeopleSoft & non PeopleSoft jobs • Visuals of job flows, schedule and calendars • Automated error control • Automated job resubmission • Advanced process alerts

14. University Of Massachusetts • Why BMC Control-M? • Tools evaluated (Control-M and AutoSys) • Integrated toolset • Single vendor for contracts, support, maintenance • Integration with BMC Patrol • References

15. University Of Massachusetts Lessons Learned – Batch Scheduling • Procure and implement early • Involve UMass resources in implementation • 4 months to implement and stabilize tool • Freeze schedule prior to testing phases • Use tool in operations & performance test • Multithreading improves performance • Establish technical test environment for testing upgrades & fixes

16. University Of MassachusettsThird Party Tools Inventory

17. University Of MassachusettsThird Party Tools Inventory Report Distribution – Mobius: ViewDirect (VD) and DocumenDirect for the Internet (DDI) • Business Requirements • Why Mobius VD & DDI? • Lessons Learned

18. University Of Massachusetts • Report Distribution Business Requirements • Web distribution of reports • Secure reports by department security • Sectioning reports by key fields • Reducing paper output • Keep reports simple – minimize training • Report archival management • Ad-hoc & batch reports • Link PeopleSoft security with reporting security

19. University Of Massachusetts • Why Mobius VD and DDI? • Tools evaluated (ViewDirect/DocumentDirect from Mobius and Brio Portal) • Document Direct met business requirements • ViewDirect for PeopleSoft interface • Cost

20. University Of Massachusetts Lessons Learned – Report Distribution • Involve UMass resources in implementation • Lengthy time to implement and stabilize tool • Involve functional resources in report design and initial configuration of tool • Performance test the tool • Make sure the product is mature on desired platform • Allow time for vendor management • Establish technical test environment for testing upgrades & fixes

21. University Of MassachusettsThird Party Tools Inventory

22. University Of MassachusettsThird Party Tools Inventory

23. University Of MassachusettsThird Party Tools Inventory

24. University Of MassachusettsThird Party Tools Inventory

25. University Of Massachusetts Managing Third Party Products With PeopleSoft ??? Questions ???

26. University Of Massachusetts Contact Information Bill Smith • UMass Infrastructure Project Mgr • Bill.smith@umassmed.edu • 508-856-2787 Lee Hoelscher • Accenture Tech Manager • Lee.K.Hoelscher@accenture.com • 614-629-2233