1. ROUND 3 User Security Set Up Presented by: Shirley Criscillis, Frank Green and Mollie Alberts

2. Agenda  Review  Roles  Security Development Cycle  Security Build Process  Introduce  New Security Request System  Define  Milestones

3. Roles

4. DEVELOPMENT CYCLE ROLES

5. Security Development Cycle & Build Process

6. LEADS SMEs TECHNICAL SECURITY ADMIN Provide PeopleSoft expertise Manage system access Perform technical development & administer system (HW, SW, LAN, etc.) Provide University expertise DEVELOPMENT CYCLE

7. UNIVERSAL SELF SERVICE CORE USER END USER Used to build foundation Used to enter transactions Used to validate transactions Used to “help yourself” DEVELOPMENT CYCLE

8. B ridges Users — These users are responsible for maintaining the basic configuration of the system. They will be responsible for researching errors. They will recommend and implement change in business processes and policies in coordination with campus administrative areas. These users are responsible for the base system integrity through design, testing, upgrades, patching and routine maintenance. Generally duties are assigned where the volume and frequency is low, a high level of specialized software knowledge is required, and coordination with multiple modules and administrative applications is required. They will be responsible for execution of the daily and monthly schedules for the systems. C ore Users — These users are responsible for validating data reconciliation within PS and between feeder system and PS. Core users drive the business schedule of processes and are responsible to daily reconcile to ensure that data totals are as expected. As errors occur, they will work in coordination with the Bridges team to research and resolve the errors. They will run processes that are not appropriate for the nightly/monthly scheduling tools. They will manage the data flow so that transactions are posted in a timely manner. These users will be responsible for review and final approval of certain transactions that End-users have entered. They will also enter transactions similar to those of End-Users. E nd Users — These users generally enter the majority of daily transactions and use both managerial and performance reporting from delivered inquiries and Cognos reports. - Bridges Finance Team, Via 5/4/2004 Email from Stephen Stanley B ridges Users — These users are responsible for maintaining the basic configuration of the system. They will be responsible for researching errors. They will recommend and implement change in business processes and policies in coordination with campus administrative areas. These users are responsible for the base system integrity through design, testing, upgrades, patching and routine maintenance. Generally duties are assigned where the volume and frequency is low, a high level of specialized software knowledge is required, and coordination with multiple modules and administrative applications is required. They will be responsible for execution of the daily and monthly schedules for the systems. C ore Users — These users are responsible for validating data reconciliation within PS and between feeder system and PS. Core users drive the business schedule of processes and are responsible to daily reconcile to ensure that data totals are as expected. As errors occur, they will work in coordination with the Bridges team to research and resolve the errors. They will run processes that are not appropriate for the nightly/monthly scheduling tools. They will manage the data flow so that transactions are posted in a timely manner. These users will be responsible for review and final approval of certain transactions that End-users have entered. They will also enter transactions similar to those of End-Users. E nd Users — These users generally enter the majority of daily transactions and use both managerial and performance reporting from delivered inquiries and Cognos reports. - Bridges Finance Team, Via 5/4/2004 Email from Stephen Stanley FOR YOUR INFORMATION

9. ROUND 2, VERSION 4 ROUND 2, VERSION 2 TRAINING CERTIFICATIONS ROUND 2, VERSION 3 ROLE TYPE CONFLICTROLE CONFLICT USER ROLES, DEPTS ROUND 2, VERSION 1 USER ROLES, TEAM LEADS SECURITY BUILD PROCESS

10. Used by Security team BUDGET APPLICATION LETTERS OF APPOINTMENT T & L APPROVERS WORKFLOW Used by Budget coordinators Used by “Approvers” Used by Bridges team Used by LOA team DEPT SECURITY DEVELOPMENT CYCLE

11. ROUND 3, FINAL – PEOPLESOFT PAPRD ROUND 3, VERSION 2 – PEOPLESOFT PADEV ROUND 2, FINAL -> ROUND 3,VERSION 1 – PEOPLESOFT PADEV CUSTOM APPLICATION OWNERS APPLICATION USER BUDGET APPLICATION LETTERS OF APPOINTMENT T & L APPROVERS SELF SERVICE SECURITY -> PASSWORD PROJECT LEGACY SEC. ADMIN ROUND 2 CONTACTS SECURITY BUILD PROCESS PORTAL

12. GUESTS QUERY EXTERNAL Used to access My UFL Used by eBill Customers Used by Bridges & Core Users Used by Job Applicants REPORTING Used by End & Core Users DEVELOPMENT CYCLE

13. ROUND 4 – FINAL - PEOPLESOFT PAPRD ROUND 4, VERSION 2 – PEOPLESOFT PAQAT ROUND 3, FINAL -> ROUND 4,VERSION 1 – PEOPLESOFT PAQAT GUESTS WORKFLOWQUERYREPORTING EXTERNAL SECURITY BUILD PROCESS BRIDGES UPDATE

14. CORE USER EXTERNAL END USER BUDGET APPLICATION LETTERS OF APPOINTMENT T & L APPROVERS SELF SERVICE DEPT SECURITY ROLES RECAP PORTAL GUESTS WORKFLOW QUERY REPORTING LEADS SMEs UNIVERSAL TECHNICAL SECURITY ADMIN

15. New Security Request System

19. MANAGE SECURITY REQUESTS

21. REVIEW SECURITY REQUESTS New Security Request System

22. LEGACY Processing Changes Dept. Requestor Dept. Sec. Admin System Owner IS Dept. Sec. Admin IS Requests change Approves request IS Makes change Make / Apprv req. Reviews request IS Makes change

23. New Process Dept. Sec. Admin UF Bridges/Sec. Admin Make / Apprv req. Reviews request UF Sec. Admin. Makes change Dept. Sec. Admin IS Make / Apprv req. Reviews request IS Makes change

25. REPORT ON SECURITY REQUESTS New Security Request System

27. DEPARTMENTS ADMINISTERED New Security Request System