1. I-AM Request Presented by Carol Williams Manager, Security and Accounts Management, Information Technologies Wednesday, May 13, 2009

2. I-AM Request Adjusted go-live date 3 times ITPM 3443 Project Charter signed mid-July –Dependent on: Decision to build using PeopleTools workflow functionality; not buy Scope limited to PeopleSoft requests with capability of future use for other applications Upgrade to PeopleTools 8.489.06 in March 2008 Application Messaging (Phase I) –Resources from across teams over & above regular work Project Manager Application Developer (all three modules) Security Analyst Training Communications

3. I-AM Request Deliverable #1 Client facing, self-serve front end Employees with ‘View Paycheque’ will request common access for themselves Manager and designated users will be able request access on behalf of others Deliverable #2 Workflow for authorizations Application uses workflow similar to ePro requisitions Three levels of authorization –User’s Manager (HR project on Reporting Manager Identification) –Specific Role or Data ‘Owner’ (ie. AP roles) –Security Analyst Approvers can approve, deny or send for revision Authorizers sent an email notification of items needing attention; link in email (Deep linking)

4. I-AM Request Deliverable #3 Provisioning of Authorized Roles Automated in real time & batch Use of role sets where they have been identified to date Other security requirements out of scope of this phase of the project continue to be provisioned manually by Security Analysts –authorizations and provisioning pertaining to: »HCM row security »HCM paygroup security »FSR GL department security »FSR GL journal source workflow »FSR eProcurement preferences »FSR AR/BI preferences »SAS SACR security »training completion where it is a pre-requisite for granting access »Removal of roles

5. I-AM Request Deliverable #4 Reporting and Auditing –Requirement of Information Security Office for ongoing attestation –Daily reporting of status and provisioning –Auditor validation of request, authorization and provisioning Implementation in Stages a.Authorization workflow for Managers and Business Owners (role/data owner) for FSR & HCM modules into production b.Self-serve and Manager self-serve functionality for FSR & HCM modules into production c.Student Administration (SA) converted from hard copy forms to I-AM Request application

6. I-AM Request Project Office - Guidance & Support for Project Managers 1.Decision to build application in-house; not buy through the RFP process 2.Charter review and help to determine stakeholders & signatories (governance) 3.Project resource & budget estimating; and recommendations 4.Assistance to constrain the scope of the project 5.Identification of dependencies 6.Project tracking - sharepoint site(s) 7.Reporting to IT Steering Committee 8.Advice on whether to proceed when dependencies remained outstanding 9.Communication of schedule delays and urgent scope changes 10.Escalation of issues; how to document and what information to include 11.Business case to recommend procedure changes **after application in production! 12.And – probably a few more since we’re not yet fully implemented…..