1. Identity Management –Peoplesoft Kickoff January 14, 2010 This meeting will run 1.5 hours Victoria White Assoc. Lab Dir. for Computing Science and Technology (acting) CIO

2. Agenda  Introductions (all) – 10 mins  What’s all this about (Vicky) – 15 mins  Brainstorming session - 3 groups  4 x ten minute sessions + 5 minutes report out (1 hour) Identity Management -Peoplesoft kickoff 2

3. High Level Goals  Streamline and modernize business processes and applications that need person, identity, role information  Get rid of redundant systems and improve business processes  Provide single authoritative source of people data (employees, contractors, visitors, transients, etc.), organizations and roles  Provide a flexible and extensible centralized electronic identity management system for the lab and open science  Fix applications to use the single authoritative source of data and central authentication  Provide additional features to the lab and WDRS for the management of people (e.g. online performance review system) and workforce planning and information services. Identity Management -Peoplesoft kickoff 3

4. Constraints  Current Peoplesoft system will not be maintainable without upgrade to the latest version before end of 2010  All Information Projects (including ones we are currently actively executing (FTL, Teamcenter, Sharepoint rollout) need to be able to rely on a properly maintained and authoritative source of people, organization and role information. So rationalizing the current messy situation has to be done this FY.  We have only a finite amount of money allocated to attack these fundamental problems and issues Identity Management -Peoplesoft kickoff 4

5. Enterprise Architecture Business Process architecture Application architecture Data/information architecture Technology architecture  In meeting our goals (or as much as we find we can allow in scope, given the constraints) we simply must target our efforts towards a solid, agreed architectural view of our future desired state.  Part of what we must do in the initial stages of this effort is figure that out  Some pieces of that architecture have already been proposed/decided/assumed  Some architectural proposals have been made for Identity Management - but not validated or decided yet. Identity Management -Peoplesoft kickoff 5

6. Two major interconnected thrusts  Peoplesoft/HRMS  What do we have now, how is it implemented (current architecture)?  What are the requirements for additional functionality (from HR, from lab, from management, from the Identity Management thrust below)  What is the desired architecture we need to head towards? Could another HRMS system be a better choice for the future?  What is the project (or projects) that we can take on and what scope can it/they have this FY?  Identity Management (including relationship to Peoplesoft)  What do we have now, how is it implemented  Have we captured all the requirements in the study performed by Tusc – can we validate them?  What is the desired architecture we need to head towards  What is the project (or set of projects) that we can take on this FY Identity Management -Peoplesoft kickoff 6

7. Studies, Roadmaps, documentation  Study by TUSC (initiated under Tune IT up). Many pictures of the current state of systems/applications  no real details about information architecture  little on business processes such as new person/account management  Some work by consultants (Plexent, Kemtah) and others (actually long history of analysis by several people) of how we handle accounts at the service desk – big mess  Presumably there is an existing long list of requests from WDRS for improvements to Peoplesoft  Presumably there is a large set of use-cases/unit tests for Peoplesoft Identity Management -Peoplesoft kickoff 7

8. Getting Started  Will need some time from many people, with diverse domain knowledge – big team  Will need to gather more data on our current situation and on requirements and desires  Enterprise Architecture office will need to weigh in heavily in the analysis/scoping stage  Don Petravick + new Ent. Architect, Joe DiVenere  Project management office will need to organize the analysis/scoping efforts – and then manage the projects we decide on  Bill Boroski + Gary Gillette and Rob Kennedy Identity Management -Peoplesoft kickoff 8

9. Brainstorming on Requirements & Risks 1.What are we trying to make work better, more efficiently, more accurately, more cost effectively with this initiative? 2.What latent needs for better support for people-related business processes do we already know about? (Of course we have to go out and gather further requirements from stakeholders) 3.What vision of identity management, authorization, role and access management, single sign on, support for visitors, support for science, support for multi-factor authentication do we have? 4.What pitfalls and risks do we have to watch out for? Identity Management -Peoplesoft kickoff 9

10. Brainstorming Groups Identity Management -Peoplesoft kickoff 10  Split up into 3 groups – keep a mix of different subject matter experts and different skills and focuses  The PMO people will be scribes  Gary Gillette  Rob Kennedy  Tim Currie  Pick a spokesperson (can be the scribe if you want)  Scribes email powerpoint to me to avoid wasting time hooking up laptops  People move to a different scribe each question (split up again) – the idea is to talk with a different group each question