Enterprise Architecture: Partnering, Procurement, and Persuasion Copyright 2008 Saint Louis University. This work is the intellectual property of the authors. 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 Introductions Section 1: EA in Year 1 Section 2: Partnering Section 3: Procurement Section 4: Persuasion

Kevin Ballard Chief Architect Department head of Business Intelligence Functional DBA and Information Architect Corporate IT Background (19 years) Introductions

James Hooper Bredemeyer-trained Enterprise Architect 5 years as Director of Client/Systems Services and lead systems architect 5 years+ as a lead systems architect 16 years IT technical roles Degrees in Biology and Management Information Systems Introductions

John Ashby 7 years in IT management: educational technology (classrooms, content/ distribution, computing) 12 years academic media management 14 years media services roles 17 years as adjunct faculty MA - Communication Introductions

Section One: EA in Year 1 Getting “ITS House in Order” Developed Architecture Governance –Integrate with Project Management Framework Started Producing Results Right Away –Expand the Product Item Master to Document Standards and Lifecycle –Identify opportunities for $$ savings

Evolving Entity Relationships

Governance Structure Enterprise Architecture –(3 positions, Summer-Fall 2006) Architecture Council –(19 positions, December 2006) Architecture Review Board (ARB) –(principles adopted, began September 2007) Different Governance, Vision, Charters Section 1: EA in Year 1

PIM beginnings for Standards… Section 1: EA in Year 1

ARBAF as Input Section 1: EA in Year 1

Architecture Review Board Tactics Maintain PIM: boring but essential! Publish!!! –EA Website must become definitive source for ARB decisions, IT standards, processes, design informationEA Website –Quarterly ARB reports, weekly –Stats and metrics Section 1: EA in Year 1

Projects and “Culture of Design” “EA Buddy” offer Advancing the ARB “Build Permit” Design review before procurement/construction Design Documents Guidelines for PMs and functional architects Design Documents Guidelines Section 1: EA in Year 1

Variability Reduction: Forward Plan Examples Desktop Power Management SQL Server Consolidation Virtualization to address datacenter issues Consolidated Server-storage architecture Section 1: EA in Year 1

New Laptops New Desktops 2005 Desktops Potential Savings: Generational Changes in Power Management

Section Two: Partnering IT Business Office relationship Ex-officio ARB seats EIWG Training Vendor relationship

ITS Business Office Supports Asked to approve all SLU computer and software requisitions Limited information on purchase requisitions Approval based on ???? Sure we have standards – lots of them! PIM now answers the question of “clearly OK” EA responds to requisitions requiring impact analysis Coordination of standards bodies: Architecture Council, Desktop Standards Committee Section 2: Partnering DilemmaEA Supports

Ex-officio ARB Seats Information Security Office Project Office Chair of Change Control Board Section 2: Partnering Mutual Stakeholders in IT Continuity

EIWG (Enterprise Infrastructure Working Group) Novell Zenworks: Enterprise “base PC image” contains – what? Central and distributed IT staff stakeholders in computer support Chartered to govern desktop system planning and change Outcome: “Modular Base Image” Section 2: Partnering

EIWG Image Change Workflow

Training Vendor Relationship IT Training Vendor: space needs ITS: Consumer of training, “free” seat allocation School of Business: MIS identity expansion opportunty Mutual responsibilities Section 2: Partnering

Section 3: Procurement RFI/RFP for servers and storage: forward design and $$ savings Standards/eCommerce for commodity servers Host Review problem survey/approvals Build permit before procurement

Server/storage RFI and RFP History of one-project-at-a-time IT hardware procurement No leveraging of distributed server- storage purchase volume Forward plan needed for multiple upcoming investments Section 3: Procurement

RFI First: Seeking Best Product Mix Overarching theme: managing datacenter assets across products, projects, and time Best of breed directions: virtualization, tiered storage, power management Opening our minds to new platforms Manufacturer-focus, not VAR Helped qualify RFP invitees

Multi-solution architecture

Server/storage RFP process Invitees: Sun, HP, and IBM (VARs their choice if desired) 5 “Typical” standard commodity servers specified for “apples-to-apples” comparison Multiple solutions and options requested Central and distributed eval committee “One Winner” intended for SLU Section 3: Procurement

Capabilities Sought Purchase Trends Reports Web e-Commerce Extended Services Special Pricing on Large Purchases Discounts and Product Lifecycle Standards maintenance process Integrate new and legacy systems

Server/storage RFP outcome Committee surprise: a hybrid solution preferred and negotiated Winning vendor services and eCommerce solution more important than platform Improved existing Volume Pricing Agreement $2.2M savings in first 6 months! Section 3: Procurement

Host Products Review: the Business Office Process Problem Can’t see others’ requisitions from ERP approval queue Limited information on requisitions: WHO to ask and FOR WHAT? Approval criteria: can Business Office understand the products requested? With servers and hosted software WHO should approve or review – many stakeholders? Every disapproval becomes “political” Section 3: Procurement

Online surveys

Host Product Review Solution: Policy & Procedure Daily requisition report with detail Online survey sent to requisitioner Review commences with survey submission by technical contact 5 working days for Security, Architecture, Network, etc. to comment Feedback sent to customer Business Office instructed to approve/disapprove Section 3: Procurement

Section 4: Persuasion James Madison story Leveraging Across Projects Strategic Planning Task Force We Need a Policy!

Leveraging Across Projects UCCI/Banner/EHR/Research Bldg HP/UX decision Identity Management alignment Facilities Host Systems Integration Section 4: Persuasion

HP/UX Placeholder

Enterprise Identity Management Driven by Common Requirements Reuse of Enterprise Investment Agility across data boundaries Global Uniqueness Unified Password Management Local Control Dedicated Support Driven by requirements of a single application Dilute Risk Unified Identity ManagementDistributed Identity Management

Reengineering Facilities IT Hosting: Illustrating Dependencies & Decisions

Strategic Planning Task Force Data from EA artifacts Visualization of Mission, Vision, Strategy Collaboration with deans on “user- centric” model Section 4: Persuasion

Saint Louis University’s Technology SUPPORTS Higher Ed CHALLENGES Space/growth Technology Strategic Planning Committee VALUES SLU Strategic Technology Direction 5. Enhance & sustain enabling infrastructure 6. Appropriate distributed & centralized tech budgets 4. Expand tech commercialization 2. Tech impact awareness 1. Tech in teaching User-centric perspective Aim for the future Technology funding: distributed AND centralized Proactive rather than reactive Finest Catholic University in the United States Banner ERP Network, Wireless, Internet 2 College technology investments Magis/Billiken Infoshield Grant funds Affordability Scalability Business Continuity Smaller student pool by 2010 Madrid Campus International Students Diversity by design Dialog and inquiry in curriculum Best Practices Best Value Research Innovation Centers of Excellence Enhanced Athletics Health Care Brand Top Research Five Dimensions Mission & Ministry Residential living Grand Center - Arts District On-Campus Facilities Synergy with other educational, research, health institutions Alumni development Connecting alumni & student recruiting Universitas and Web Reputation of Distinction Global Perspective Culture of High Performance Vibrant Urban Location Forever SLU Student Formation Engagement Classroom/computer refresh Enterprise Architecture 6/1/2007 – John M. Ashby Security/privacy Compliance Assessment 3. Integrate tech & research

Opportunity: “We Need a Policy” Guest Access Policy: started with “shared username” desktop security discussion; Integrated Sign-on added urgency Grew into Identity Policy committee, listing all “defined relationships” and deciding who can create/maintain these Section 4: Persuasion

Enterprise Architecture Program at Saint Louis University: Partnering, Procurement, Persuasion Kevin Ballard Chief Architect James Hooper Enterprise Architect John Ashby Enterprise Architect Saint Louis University Information Technology Services 3690 West Pine Mall St. Louis, MO Q&A

Recommended Sites es/ea/EAMM.pdf es/ea/EAMM.pdf