Enterprise Architecture at Saint Louis University Copyright 2008

Enterprise Architecture at Saint Louis University Copyright 2008 Saint Louis University. 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 • Part 1: Don’t Fence Me In • Part 2: So What Worked? • Part 3: Ugh, That could have gone better… • Part 4: The Future

Part 1: Don’t Fence Me In The Rule of “Tactical Agility”

2006: Tactical Agility • Get-er Done • “Flexible and Agile” • Passive Change Control • Heroism at the Interfaces • Architecture in Silos

A Few Good Successes • Recent Network Redesign • Billiken Info Shield • Campus-wide DHCP • Banner ERP Upgrade • Beginnings of Identity Management

Part 2: The Birth of EA “Show me ROI for my investment. ” - Ellen Watson, SLU CIO, 2006

Other Drivers for EA at SLU • Mitigate Risk Associated with Banner Upgrade • • • and Related Projects SAS 112 / SOX IT control levels Lack of Standards and Documentation Inconsistent or Undocumented Architectural Decisions Lifecycle (Mis)Management Lack of Coordination across Technical Boundaries and organizational silos Section 2: Getting Started at SLU

Our Approach • Show Quick Results • Build Value through lasting Processes • Establish Governance • Get “ITS’ House In Order” First • Then Branch Out

The Purpose of Enterprise Architecture “EA provides a common basis for understanding and communicating how systems are structured to meet strategic objectives. ” Source: Bredemeyer Consulting Section 1: EA Overview

Part 3: So What Worked? • People, Process and Technology • The PIM: A Beginning • Partnering: Governance Relationships • Procurement: Server / Storage Deal • Persuasion: UCCI Architecture, Etc. • Governance Checklist

The PIM: Product Item Master • Standards Lifecycle Management • Boring But Essential • EA Website is becoming the definitive source (http: //ea. slu. edu) • Quarterly Reports

Partnering: It’s About Relationships • IT Business Office relationship • Ex-officio ARB seats • EIWG • Training Vendor relationship

Procurement: Saving Money • RFI/RFP for servers and storage: forward design and $$ savings • Standards/e. Commerce for commodity servers • Host Review problem survey/approvals • Build permit before procurement

Persuasion • James Madison story • Leveraging Across Projects • Strategic Planning Task Force

Part 4: Where do we Go From Here? • Architecture Gaps • Governance Gaps • Executive Buy-In • Organizational Placement • The Future

Governance Goals • Control of the work. • Co-ordination between different pieces of work. • Measurement of outcome. • Compliance with internal policy or regulation. • Justification of spending. • Accountability and transparency. • Connecting with the needs of customers, the broader organization, and other stakeholders.

flickr: Fort Photo

Q&A Saint Louis University Information Technology Services 3690 West Pine Mall St. Louis, MO 63108 -3304 James Hooper Enterprise Architect hooper@slu. edu Building an Enterprise Architecture Program at Saint Louis University © 2007 Saint Louis University

Recommended Sites • http: //ea. slu. edu • http: //www. bredemeyer. com • http: //www. togaf. com • http: //eajournal. blogspot. com • http: //www. nascio. org/nascio. Committe es/ea/EAMM. pdf