28
ROUND 3 ROUND 3 User Security User Security Set Up Set Up Presented by: Shirley Criscillis, Frank Green and Mollie Alberts
ROUND 3 ROUND 3 User Security Set User Security Set
UpUp
Presented by: Shirley Criscillis, Frank Green and Mollie AlbertsPresented by: Shirley Criscillis, Frank Green and Mollie Alberts
AgendaAgenda
ReviewReview RolesRoles Security Development CycleSecurity Development Cycle Security Build ProcessSecurity Build Process
IntroduceIntroduce New Security Request SystemNew Security Request System
DefineDefine MilestonesMilestones
Roles Roles
DEVELOPMENT CYCLEDEVELOPMENT CYCLE
ROLES ROLES
Security Security Development Development
Cycle & Cycle & Build ProcessBuild Process
LEADSLEADS
SMEsSMEs
TECHNICALTECHNICAL
SECURITY ADMINSECURITY ADMIN
Provide PeopleSoft expertiseProvide PeopleSoft expertise
Manage system accessManage system access
Perform technical development & administer system (HW, SW, LAN, etc.)
Perform technical development & administer system (HW, SW, LAN, etc.)
Provide University expertiseProvide University expertise
DEVELOPMENT CYCLEDEVELOPMENT CYCLE
UNIVERSALUNIVERSAL
SELF SERVICESELF SERVICE
CORE USERCORE USER
END USEREND USER
Used to build foundationUsed to build foundation
Used to enter transactionsUsed to enter transactions
Used to validate transactionsUsed to validate transactions
Used to “help yourself”Used to “help yourself”
DEVELOPMENT CYCLEDEVELOPMENT CYCLE
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.
End 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
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.
End 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 INFORMATIONFOR YOUR INFORMATION
ROUND 2, VERSION 4ROUND 2, VERSION 4
ROUND 2, VERSION 2ROUND 2, VERSION 2
TRAINING CERTIFICATIONSTRAINING CERTIFICATIONS
ROUND 2, VERSION 3ROUND 2, VERSION 3
ROLE TYPE CONFLICTROLE TYPE CONFLICT
ROLE CONFLICTROLE CONFLICT
USER ROLES, DEPTSUSER ROLES, DEPTS
ROUND 2, VERSION 1ROUND 2, VERSION 1
USER ROLES, TEAM LEADSUSER ROLES, TEAM LEADS
SECURITY BUILD PROCESSSECURITY BUILD PROCESS
Used by Security teamUsed by Security team
BUDGET APPLICATION
BUDGET APPLICATION
LETTERS OF APPOINTMENT
LETTERS OF APPOINTMENT
T & L APPROVERST & L APPROVERS
WORKFLOWWORKFLOW
Used by Budget coordinatorsUsed by Budget coordinators
Used by “Approvers”Used by “Approvers”
Used by Bridges teamUsed by Bridges team
Used by LOA teamUsed by LOA team
DEPT SECURITYDEPT SECURITY
DEVELOPMENT CYCLEDEVELOPMENT CYCLE
ROUND 3, FINAL – PEOPLESOFT PAPRDROUND 3, FINAL – PEOPLESOFT PAPRD
ROUND 3, VERSION 2 – PEOPLESOFT PADEVROUND 3, VERSION 2 – PEOPLESOFT PADEV
ROUND 2, FINAL -> ROUND 3,VERSION 1 – PEOPLESOFT PADEVROUND 2, FINAL -> ROUND 3,VERSION 1 – PEOPLESOFT PADEV
CUSTOM APPLICATIONOWNERS
CUSTOM APPLICATIONOWNERS
APPLICATION USERAPPLICATION USER
BUDGET APPLICATIONBUDGET APPLICATION LETTERS OF
APPOINTMENT
LETTERS OF APPOINTMENT T & L APPROVERS
T & L APPROVERS
SELF SERVICESELF SERVICE
SECURITY -> PASSWORD PROJECT
SECURITY -> PASSWORD PROJECTLEGACY SEC. ADMINLEGACY SEC. ADMIN ROUND 2 CONTACTSROUND 2 CONTACTS
SECURITY BUILD PROCESSSECURITY BUILD PROCESS
PORTALPORTAL
PORTALPORTAL
GUESTSGUESTS
QUERYQUERY
EXTERNALEXTERNAL
Used to access My UFLUsed to access My UFL
Used by eBill CustomersUsed by eBill Customers
Used by Bridges & Core UsersUsed by Bridges & Core Users
Used by Job ApplicantsUsed by Job Applicants
REPORTINGREPORTING Used by End & Core UsersUsed by End & Core Users
DEVELOPMENT CYCLEDEVELOPMENT CYCLE
ROUND 4 – FINAL - PEOPLESOFT PAPRDROUND 4 – FINAL - PEOPLESOFT PAPRD
ROUND 4, VERSION 2 – PEOPLESOFT PAQATROUND 4, VERSION 2 – PEOPLESOFT PAQAT
ROUND 3, FINAL -> ROUND 4,VERSION 1 – PEOPLESOFT PAQATROUND 3, FINAL -> ROUND 4,VERSION 1 – PEOPLESOFT PAQAT
GUESTSGUESTS
WORKFLOWWORKFLOW
QUERYQUERY
REPORTINGREPORTING
EXTERNALEXTERNAL
SECURITY BUILD PROCESSSECURITY BUILD PROCESS
BRIDGES UPDATEBRIDGES UPDATE
CORE USERCORE USER
EXTERNALEXTERNAL
END USEREND USER
BUDGET APPLICATION
BUDGET APPLICATION
LETTERS OF APPOINTMENT
LETTERS OF APPOINTMENT
T & L APPROVERST & L APPROVERS
SELF SERVICESELF SERVICE
DEPT SECURITYDEPT SECURITY
ROLES RECAPROLES RECAP
PORTALPORTAL
GUESTSGUESTS
WORKFLOWWORKFLOW
QUERYQUERY
REPORTINGREPORTING
LEADSLEADS
SMEsSMEsUNIVERSAL
UNIVERSAL
TECHNICALTECHNICAL SECURITY ADMIN
SECURITY ADMIN
New Security New Security Request Request SystemSystem
New Security New Security Request System Request System
MANAGE MANAGE SECURITY REQUESTSSECURITY REQUESTS
REVIEW REVIEW SECURITY REQUESTSSECURITY REQUESTS
New Security New Security Request System Request System
LEGACY Processing Changes LEGACY Processing Changes
Dept. RequestorDept. Requestor
Dept. Sec. AdminDept. Sec. Admin
System OwnerSystem Owner
ISIS
Dept. Sec. AdminDept. Sec. Admin
ISIS
Requests changeRequests change
Approves requestApproves request
Approves requestApproves request
Approves requestApproves request
ISIS Makes changeMakes change
Make / Apprv req.Make / Apprv req.
Reviews requestReviews request
ISIS Makes changeMakes change
New ProcessNew Process
Dept. Sec. AdminDept. Sec. Admin
UF Bridges/Sec. Admin
UF Bridges/Sec. Admin
Make / Apprv req.Make / Apprv req.
Reviews requestReviews request
UF Sec. Admin.UF Sec. Admin. Makes changeMakes change
Dept. Sec. AdminDept. Sec. Admin
ISIS
Make / Apprv req.Make / Apprv req.
Reviews requestReviews request
ISIS Makes changeMakes change
REPORT ON REPORT ON SECURITY REQUESTSSECURITY REQUESTS
New Security New Security Request System Request System
DEPARTMENTS ADMINISTEREDDEPARTMENTS ADMINISTERED
New Security New Security Request System Request System
