
dd40fd0d24f25ee971dc51f11e47e0cf.ppt
- Количество слайдов: 19
Planning: Project Readiness and Costs Mike Conlon Director of Data Infrastructure University of Florida Copyright Michael Conlon, 2004. This work is the intellectual property of the author. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of the author. To disseminate otherwise or to republish requires written permission from the author.
Agenda § Planning for Directory Services at the University of Florida § Project Costs for Directory Services § Extended Q&A and Discussion CAMP Directory Workshop Feb 3 -6, 2004
Context for Directory Services are created in context – Institutional Context – IT Service Process Context – Deployment Environment Context CAMP Directory Workshop Feb 3 -6, 2004
One Slide About UF § 49, 000 students in Gainesville Fl § Freshman class: 3. 92 GPA, 1300 SAT § $1. 8 Billion annual budget, $450 million in research -- growing at 12% per year, Health Sciences – 52% of research § 140 academic departments in 23 colleges § Land grant – extension in all 67 counties § The Gators, Lady Gators, Gator. Ade CAMP Directory Workshop Feb 3 -6, 2004
IT Service Processes Discovery • Assess needs • Analyze • Recommend • Decide Delivery • Make or buy • Integrate • Develop policy & procedures • Deployment Roadmap CAMP Directory Workshop Feb 3 -6, 2004 Operations • Manage resources • Provide business continuity Support • Help • Teach • Consult
Deployment Environment Users Requirements, acceptance, access, policies, procedures, communication, training, support, change management User Technology PCs, printers, PDAs, laptops, storage, office machines, video, phones, browsers, office suites, local and custom software System Architecture Models of access, security, business logic, transaction logic, business objects, messaging, middleware, system interfaces System Infrastructure Operational systems for transaction processing, databases, middleware, job control, workgroup, storage, business continuity Transport Layer Switches, routers, gateways, bridges, access points, Internet 2, telecommunications, monitoring, DHCP, DNS, VPN CAMP Directory Workshop Feb 3 -6, 2004
One Slide About UF Technology § § § § 500 IT professionals across campus Very decentralized Over 300 email servers, 200 LANs 30, 000 devices on the open network AD, NDS, i. Planet, Open. LDAP, Kerberos Directory Project (2000 -2003) People. Soft implementation (2002 -2007) CAMP Directory Workshop Feb 3 -6, 2004
UF Directory Background § Community effort to solve the directory problem at UF -- 17 sources for directory information. Limited sharing § Strong data “ownership” § Information Systems, Academic Technology, Health Center, Registrar, Data Center involved from the beginning CAMP Directory Workshop Feb 3 -6, 2004
UF Directory Background § Gator. Link – Kerberos-based authentication mechanism since 1997. § Unsponsored campus LDAP and NDS. § DB 2 -based registry of people information. § Adhoc integration. § Many feeds to the registry, few from the registry. CAMP Directory Workshop Feb 3 -6, 2004
SWOT Analysis § Strengths – Experience with registry, LDAP, Kerberos. – Vision – Spontaneous community effort § Weaknesses – Organizational barriers § Opportunities – SSN. Cleanup. Get to the next level. New organization § Threats – Commitment. Complexity CAMP Directory Workshop Feb 3 -6, 2004
Planning Effort § Ad hoc 14 member workgroup formed in August 2000 § Considered all aspects of directory services § Connected with national efforts. Ken Klingenstein § Cross team planning with SSN task force § Cross team planning with IT Review § Completed white paper in August 2001 CAMP Directory Workshop Feb 3 -6, 2004
A Vignette Bill is a physician faculty member in the College of Medicine. He and/or his department administrator can update his contact information using a web page. This information automatically populates/updates the personnel system, the Shands Communications system (CHRIS), the Shands Health. Care on-line directory of physicians, Bill’s entry in Netware Directory Services, Active Directory, the on-line phone book, the UF enterprise directory database, and the UF LDAP directory. People using email programs and their address books always automatically access Bill’s current email address. UF business processes have access to Bill’s current information. Bill’s information is updated once and is used and accessed consistently across the enterprise. CAMP Directory Workshop Feb 3 -6, 2004
UF Directory Project § § Start planning August 2000 Finish report September 2001 Begin implementation October 2001 Deploy new directory January 23, 2003 § http: //www. it. ufl. edu/projects/directory CAMP Directory Workshop Feb 3 -6, 2004
Directory Project Deliverables § § § § § New Registry New LDAP schema based on edu. Person and edu. Org New IDs – UFID and UUID tied to Gator. Link 50, 000 new Gator One cards 1, 500 applications modified New self-service apps http: //phonebook. ufl. edu New directory coordinator apps Directory Architecture New APIs for directory-enabling business processes CAMP Directory Workshop Feb 3 -6, 2004
Identifiers § Gator. Link – public username, email address (mconlon@ufl. edu), single sign-on. Revocable. Lucent. § UFID. Eight digit random number assigned by UF. nnnn-nnnn. Used where SSN was used previously. Protected. Revocable. Opaque. § UUID (GUID) “NDC”. Non-revocable. Opaque. Not used outside central systems. CAMP Directory Workshop Feb 3 -6, 2004
UF Directory – Architecture CAMP Directory Workshop Feb 3 -6, 2004
Project Cost § Project Cost at UF was estimated solely on staff time to design and implement ($400 K). Other costs not considered – – – 1. 0 FTE Software Development Manager 0. 5 FTE Communications, Documentation 0. 25 FTE Database Administration 2. 0 FTE Application Developers 1. 0 FTE Systems Programmers (LDAP, ETL) 0. 25 FTE Trainer § Total project cost at completion estimated at $4. 7 million over 18 months. This includes training, all conversion § No hardware. All systems run on existing hardware CAMP Directory Workshop Feb 3 -6, 2004
Functional Issues § § § Who can update data? Who can replicate data? Who resolves conflicting values? Who owns data? Who can access data? What business processes are supported? What processes are not supported? CAMP Directory Workshop Feb 3 -6, 2004
Your Turn § Context, roadmap, opportunities § What could work for you? What may not work for you? After the CAMP: UF Directory Project http: //www. it. ufl. edu/projects/directory Email: mconlon@ufl. edu CAMP Directory Workshop Feb 3 -6, 2004