1 / 28

ROUND 3

ROUND 3. User Security Set Up. Presented by: Shirley Criscillis, Frank Green and Mollie Alberts. Agenda. Review Roles Security Development Cycle Security Build Process Introduce New Security Request System Define Milestones. Roles. DEVELOPMENT CYCLE. System Support. Data Input.

feng
Download Presentation

ROUND 3

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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 System Support Data Input ROLES R0 R1 & 2 UF Custom Applications My UFL & Data Output R3 & 4 R2 & 3

  5. Security Development Cycle & Build Process

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

  7. DEVELOPMENT CYCLE Data Input Round 1 & 2 UNIVERSAL Used to build foundation SELF SERVICE Used to “help yourself” END USER Used to enter transactions CORE USER Used to validate transactions

  8. FOR YOUR INFORMATION Bridges 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. Core 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.EndUsers—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

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

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

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

  12. DEVELOPMENT CYCLE My UFL & Data Output Round 3 & 4 PORTAL Used to access My UFL GUESTS Used by Job Applicants EXTERNAL Used by eBill Customers Used by Bridges & Core Users QUERY REPORTING Used by End & Core Users

  13. SECURITY BUILD PROCESS ROUND 3, FINAL -> ROUND 4,VERSION 1 – PEOPLESOFT PAQAT WORKFLOW QUERY REPORTING ROUND 4, VERSION 2 – PEOPLESOFT PAQAT EXTERNAL GUESTS ROUND 4 – FINAL - PEOPLESOFT PAPRD BRIDGES UPDATE GO LIVE

  14. ROLES RECAP DEPT SECURITY GUESTS BUDGET APPLICATION LETTERS OF APPOINTMENT PORTAL WORKFLOW EXTERNAL T & L APPROVERS QUERY REPORTING System Support ROLES Data Input LEADS UNIVERSAL SMEs CORE USER SELF SERVICE SECURITY ADMIN TECHNICAL END USER UF Custom Applications My UFL & Data Output

  15. New Security Request System

  16. STEP 1

  17. STEP 2

  18. STEP 3

  19. New Security Request System MANAGE SECURITY REQUESTS

  20. New Security Request System REVIEW SECURITY REQUESTS

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

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

  23. New Security Request System REPORT ON SECURITY REQUESTS

  24. New Security Request System DEPARTMENTS ADMINISTERED

More Related