Enterprise Architecture: Enterprise Architecture: Partnering, Procurement, Partnering, Procurement, and Persuasionand Persuasion

Enterprise Architecture: Enterprise Architecture: Partnering, Procurement, Partnering, Procurement, and Persuasionand PersuasionCopyright 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.

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 1Getting “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

Architecture Council (or members)

Architecture ReviewBoard

Enterprise Architecture(practitioners)

Project Office Change Control Board

2v. - MM2/23/2007 . MMMMM

InputsLegend

DecisionRequest

FYI

Referral

Technology Architecture Standards Governance Model

Deliverables

DecisionRequest

FYI

Referral

Approved

Request forInformation

Deferral ofdecision

Rejected

Conditionaldecision

DecisionRequest

FYI

ArchitectureReview

PIMvariancereview

Submit andAttend ARB

Intake Formand

Documentation

Intake Form andDocumentation

Agenda

Prod changePIM

compliant?

Agenda

Yes

CCB governs

Gate 1Review

No

Gate 2Review

Business Office, Security, Other

Governance Units

Referral

FYI

To Originator

- Add product to PIM- Status move on PIM- Remove item from PIM- Nonstandard use of item

- R&D early eval products- "Heads up" from IT units- Project gate 1 reviews

- IT governance units

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 information

– Quarterly ARB reports, weekly email– 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

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 LaptopsNew LaptopsNew DesktopsNew Desktops2005 Desktops2005 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

Dilemma EA 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

BIS Changes Workflow

STEP ONEGather ChangesRemedy Change TicketsContinuous

STEP TWOSet ScopeSet Ad Hoc TeamWeek 3 of Month

STEP FOURPublish Proposed Image

Gather Feedback

Week Two (One Week)

STEP FIVESend to Server Team for Scheduling andPrioritization

Server Team Manager Schedules CCBNotify Working GroupWeek 3

STEP THREEWork the ProblemBuild Proposed ImageTestDocumentWeek Four, One

STEP SIXPublish New Image

Post Changes

Post Documentation

February 12, 2008Version 102506.2JH

CustomerService

EIW Ad Hoc Team

EIWG Image Change WorkflowEIWG 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 email 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

Epic

Future

Future

Future

Why isUnified Campus Computing Infrastructure

the "Right" Solution?

Common Infrastructure MeansFewer Moving Parts & Easier Upgrades

World Class Hardware toAchieve 99.99% Availability

and Disaster Recovery

Industry Best Practice to ConsolidateApplications for Cost Reduction

Simplified Manageability andGreater Reliability

Capacity on Demand to Alleviate PerformanceBottlenecks and Reduce Costs

of Future Upgrades

More Time Between Refreshes MeansLong Term Cost Reductions

Enables SLU to Achieve StrategicGoals

Epic

Banner

Epic

Future

Data

Site

Failo

ver

Primary Data Center

Disaster Recovery Site

Integrity Servers Storage

Integrity Servers Storage

Unified Enterprise Computing - October 16, 2007 101607.2 jh kb

Epic

Banner

IDX

Future

Epic

Future

Future

Future

Brings EHR Server/Storage CostsCloser to Budget

Data Network(Midtown STL -On Campus)

VLANSegments

2InternetLink

Internet1ISP

Internet2ISP TBA

-Partner LinksTenet, SSM , etc.

Enterprise Networking Environment

- Client Server Logical Infrastructure(Midtown STL -On Campus)

DHCP DNS

Wireless

- University wide Hosting Environment

NetworksAuthentication

File/PrintAuthentication

VPNAuthentication

NetStorage (myFiles)Authentication

ApplicationAuthentication

Outsourced ApplicationAuthentication

Resnet

UserIdentities

Outsourced Application Secure Transport

ITS Datacenters Redundant Physical Infrastructure(Midtown STL -On Campus)

IP Voice,Controls

ISP Name and Routing Services

Desktop Management

- - University wide Server Storage Environment

Enterprise Tiered Storage

SAN Fabrics

Enterprise App - Servers Prod

and Test

EnterpriseBackup-(Non network)

Power, Cooling,Systems

Management

-Single unitGovernance:

-Enterprise wide,- Non ITS Hosted

Facilities Sites

Library Sites

Typical DLC - (Departmental Local

Constituents),- Non ITS Hosted

Academic Clusters

Dept. Servers

BandwidthManagement

Firewalls

Security Monitoring

-WAN Links Remote Sites

TelephoneInfrastructure

Computers

IP VideoConferencing

ControlSystems

(Campus Network)(External Networks)

(On-campus)(Off-campus)

(Inside)(Outside ITSDatacenters)

Outsourced ApplicationERP Interface

DLC Servers in DatacentersSLA

Outsourced Managed Services

Saint Louis University Enterprise Information Systems Infrastructure:Functional View

Enterprise Architecture 1/11/2008 - John M. Ashby

CopperStructured

Cabling

FiberInfrastructure

ITS ControlsMidtown STL -On Campus

Saint Louis University Hosting and Compliance Environment

ChangeControl

ManagedArchitecture

PrioritizeProjects

InformationSecurity

QualityAssurance

FCCPCIGLBOther

Compliance

HIPAA CALEASOXMandates

Unified Campus Computing Infrastructure

(UCCI)

HP/UX Placeholder

SolarisDisqualified

RFI

CDWG / HPAwarded Contract

HPUX = Unix EnterpriseStandard

RFP

Linux Strategy

Reduce Costand Complexity

EpicRequirements

AssessLinux

CurrentBanner

SolarisSun's RFPResponse

HPUXRequired

BannerRefresh

Linux orHPUX

?

HPUX Decision Tree - September 5, 2007 - V_090507.1 jh

CurrentHP InstallHP's Response

EA ConceptualArchitecture

EA ProjectRequirements

Maybe Linux

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 Management Distributed Identity Management

SLU-Owned Clinic Exam Room

User Log-On Cases - EHR ProjectEnterprise ArchitectureFebruary 13, 2008021608.2 jh

SLU Wired Desktop

Non-SLU Clinic Exam Room

Non-SLU Remote Desktop

SLU Wireless Desktop(Local)

Non-SLU Wireless Desktop(Local)

Patient Log-On

User DataSources

Banner

MagisIDMS

Credentials Ok?

Yes/No

Epic

NovellDesktop

Environment

Citrix

myChart

Lo

gin

A

B

IDX

OtherSLU

Systems

OtherPartner

Systems

Other Credentials

SLU Remote Desktop

Non-SLU Remote Desktop

"The Internet"

Key:

A

B

Internal Patient Credential Store

Magis Credential Store

SLU Information Systems: Distributed Hardware Management Alignment

Data NetworkMidtown STL -On Campus

VLANSegments

2InternetLink

Internet1ISP

Internet2ISP TBA

-Partner LinksTenet, SSM , etc.

Saint Louis University Enterprise Networking Environment

- Client Server Logical InfrastructureMidtown STL -On Campus

DHCP DNS

Wireless

Saint Louis University Enterprise Hosting Environment

NetworksAuthentication

File/PrintAuthentication

VPNAuthentication

NetStorage (myFiles)Authentication

ApplicationAuthentication

Outsourced ApplicationAuthentication

Resnet

UserIdentities

Outsourced Application Secure Transport

ITS Datacenters Redundant Physical InfrastructureMidtown STL -On Campus

IP Voice,Controls

ISP Name and Routing Services

Desktop Management

- Saint Louis University Server Storage Environment

Enterprise Tiered Storage

SAN Fabrics

Enterprise App - Servers Prod

and Test

EnterpriseBackup-(Non network)

Power, Cooling,Systems

Management

-Single unitGovernance:

-Enterprise wide,- Non ITS Hosted

Facilities Sites

Library Sites

Typical DLC - (Departmental Local

Constituents),- Non ITS Hosted

Academic Clusters

Dept. Servers

BandwidthManagement

Firewalls

Security Monitoring

-WAN Links Remote Sites

TelephoneInfrastructure

Computers

IP VideoConferencing

ControlSystems

(Campus Network)(External Networks)

(On-campus)(Off-campus)

(Inside)(Outside ITSDatacenters)

Outsourced ApplicationERP Interface

DLC Servers in DatacentersSLA

Outsourced Managed Services

Enterprise Architecture 20071218_v3 - John M. Ashby

CopperStructured

Cabling

FiberInfrastructure

ITS Controls Saint Louis University Compliance Environment

ChangeControl

ManagedArchitecture

PrioritizeProjects

InformationSecurity

QualityAssurance

FCCPCIGLBOther

Compliance

HIPAA CALEASOXMandates

Enterprise ITResources

Aligned

FacilitiesResources

Aligned

Unitime?

Envision?

BbCommunity?

Maximo

LobbyWorks?

Prowatch?

ABM/Phoenix?

MetaSys?

Archibus?

Application Managed by Owner on Enterprise Hardware Application/Hardware Managed by Owner

Unit-specificMulti-division impact

Single unit governanceShared governance

Maxicom

TMS

TicketTrac

Keystone

Arrival

Auditable Controls Accountability

Cameras

SMART gates

Dispatch

High dependency Low Enterprise ITResources dependency

ITS

En

terp

rise

Hard

ware

Enterprise Virtual Server/Storage

Unified Campus Computing Infrastructure

Facilities Services Division Use Case

Exchange(Outsourced)

-

Ow

ner

man

ag

ed

Hard

war e

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/growthTechnology 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

• Assessment3. Integrate tech & research

DistributedClinics

Residents

Students

FT/EmeritusTA/RAs

Faculty

Service Units (e.g. Facilities,IT)

Academic Deans and

Chairs

ResidentsPhysicians

Clinicians

Administration and Support

Systems

Patients

User Context for Technology Strategy

(Centralized & Distributed Planning)

-Nontraditional

ResearchSubjects

Customers (Product User)

Adjunct/PT

Business, HR, Legal, Functional

Support

Academic &StudentSupport

ResearchAdmin.

Providers(Product

Creation User)

Commuters UMG Clinical

SupportStaff

-Dual role?

The Higher Education Technology User View

Auxiliaries

Market &Environ.

Enterprise Architecture 3/7/07 - John M. Ashby

LegalMandates

RegulatoryConstraints

Alumni andCommunity

FundraisingHumanCapacity

FinancialSources

Accreditation,Carnegie Class

Recruitment,Discount Rate

TechnologyExpectations

TechnologyLiteracy

Competitionfor Grants

Patents andIP Transfer

Competitionfor Customers

Competitionfor Faculty

-Multi role?

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 Architectkballar2@slu.edu

James Hooper Enterprise Architecthooper@slu.edu

John AshbyEnterprise Architect ashbyjm@slu.edu

Saint Louis University

Information Technology Services

3690 West Pine Mall

St. Louis, MO 63108-3304

http://ea.slu.edu

Q&AQ&A

Recommended Sites

• http://ea.slu.edu• http://www.bredemeyer.com• http://www.togaf.com• http://eajournal.blogspot.com• http://

www.nascio.org/nascioCommittees/ea/EAMM.pdf