14
Page 1 Version 0.1 September 2004 MIT Enterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture Guide Project at MIT CSG Presentation 9/23/04 Jerry Grochow MIT’s ITAG team sponsored a six week initiative to document the current state architecture and to begin development of a vision for future state enterprise architecture. Documents will be on-line, refined, and continuously updated to reflect deeper understanding and changing needs of the Institute.

Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Embed Size (px)

Citation preview

Page 1: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 1 Version 0.1 September 2004

MIT

En

terp

rise

Arc

hit

ect

ure

© Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

Enterprise Architecture Guide Project at MIT

CSG Presentation 9/23/04Jerry Grochow

MIT’s ITAG team sponsored a six week initiative to document the current state architecture and to begin development of a vision for future state enterprise architecture.

Documents will be on-line, refined, and continuously updated to reflect deeper understanding and changing needs of the Institute.

Page 2: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 2 September 2004 © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

Scope of Enterprise Architecture:

•Business processes and products, applications and data (Process)

•Software and hardware infrastructure (Technology)

•Knowledge and expertise (People)

Current State Assessment:•Documentation review•Interviews with ITAG and

departmental technology staff

•Workshops to validate information gathered

Future State:•Workshops (1/2 day) to

cover:•Future State Context•Future State Principles•Logical Architecture

Framework•Technology Standards•Services Matrix•Project Review process

Future Phases:•Roadmap and Planning•Build-out

Page 3: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 3 September 2004 © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

Audience and Value of the EA Guide (1 of 2)

Project Sponsors and Departmental Leadership

•Understand institute investments in technology

•Understand architectural governance process

•Provide technical direction to guide their investments

•Provide a way to assess architectural risks on projects

IT Architecture Group

•Common understanding of architecture

•Frames architectural review process for projects

•Inform gaps in the architecture and where we need to evolve

•Provide a way to assess architectural risks on projects

Page 4: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 4 September 2004 © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

Audience and Value of the EA Guide (2 of 2)

Developers

•Awareness

• of available services

• of enterprise data model

• of the landscape and future vision of enterprise architecture

• of supported and recommended standards

•Reduce redundancy of effort

•Provide a way to assess architectural risks on projects

•Know where to go to get help

•Awareness of their role in expanding the services offered in the enterprise architecture

Page 5: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 5 September 2004 © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

Enterprise Architecture Deliverables

Current State

System ContextDiagram

Key SystemsInventory

System Logical andPhysical Architecture

DiagramsContext

Services Matrix

Integration Inventory Systems on a Page

Business Process Flowsand Scenarios

Future State

Technology Standards Business Strategy Future State ServicesMatrix

Future State Logical Architecture Vision

Road Map

List of Initiatives

Prioritization Model

Architecture MigrationMaps

Short Term Roadmap

Long Term Roadmap

Timeless/ Evolutionary

Enterprise Data Model

Architectural ReviewProcess

IT Governance Process

ArchitecturalPrinciples

Page 6: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 6 September 2004 © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

Future State Context

• SAP will continue to be the primary ERP system

• The MIT Data Warehouse will be the central repository for

administrative data that is of interest to more than one DLC.

• The MIT community will continue to be global, 24x7 and

evolving

• There will be increased integration between MIT and other

universities

• The MIT environment is heterogeneous

• The MIT network will evolve to support needs of the enterprise

•We may have many research networks

•We will have an IPv6 network and we will need differentiated

services to better support user needs

Page 7: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 7 September 2004 © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

Architectural Principles

• Security: applications should ensure data and access

security

• Ownership: clear and explicit ownership of enterprise data

• Leverage assets: leverage existing services and capabilities

• Accessibility: be aware of to needs of all users (location &

disabilities)

• Real-time: Minimize latency of data updates

• Standards: promote consistency using standards

Page 8: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 8 September 2004 © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

Systems Context Diagram (Vers. 0.1)

Enterprise Administrative Systems

Integrated Operation/ Infrastructure Support

DNS DHCP Tether iPass CISCO VPN

MIT IDSystem

KerberosX509

CertificateActive

Directory

EmailTechtime(Calendar)

Zephyr Mailman

RolesActive

DirectoryAFS

OracleNameService

CaseTracker

MIT OnlineDirectory

MoiraData

Warehouse

CitrixAthenaDialup

MIT Web

Shop MITClear

CommerceEDI

Moira

Student ManagementLo

cal /

Departm

enta

l Syste

ms

Exte

rnal S

ystem

s

Admissions

Student

MIT SIS

Alumni

Advance

Web SIS

SloanAlumni

DB

AdmissionsPortal

UnderGraduateAdmission

GraduateAdmission

CardSystem

Tech Cash

Parking

Environmental Healthand Safety

EHS

Library

Barton

CorporateDatabase

ILP

Purchasing

SAP ECAT

Research Management

COEUS(GrantMgmt)

PracticeMgmt

System

ElectronicMedicalRecords

E-ScriptionPatientOnline

HR

SAP

SpaceMgmt.System

Insite(SpaceAccting)

SAP - PlantMaint

Maximo

Key System

Budget

Nimbus SAP

Finance

SAPSummit

(HistoricalData)

Payroll

MITStudentPayroll

SAP(Pensions

Only)

Mainframe

Academic Systems

OCW D - Space

Barton Vera

EZProxy SFX

GIS

SloanSpace

Stellar

Admin

Enterprise ServicesPresident's OfficeMedicalFacilities

Network Connectivity

IdentityAuthentication

Groupware

Authorization Data Services & Storage

Application Connectivity

MIT Web

E-commerceInfrastructure

Library

Learning Management

Content Management

Resource Development

TLO

PlaceholderSystem

Page 9: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 9 September 2004 © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

Systems on a Page (Vers. 0.1)

Page 10: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 10 September 2004 © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

Enterprise Conceptual Data Model (Vers 0.1)

Degree

Organization

Cost Object

Property

Project

ProfitCenter

Appointment

Proposals

Employee

Sponsor

Fellowship

Space

Person

Applicant

Student

Course(Major)

Faculty

PrimaryInvestigator

(PI)

Subject Section

Hazard

owns

offer

offer

is represented by

is charged against

is expensed to

supervises

is representedby funds

funds

has oversight of

works on

receives

responsible for

is administrative department for

may contain

occupied by

occupies

is responsible for

a personcan be...

can becomeadvises

supervises

is responsible for / offers

may teach

havehave

enroll in

can receive

is responsible for

selects

may have

could become

Alumnus

may be

Chair is held by

funds

sent to

mayteach

Position

BudgetCourseContent

Gift

Job Company

Legend

one and only one

zero or one

zero or many

one or many

[name] entity

Page 11: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 11 September 2004 © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

Future State Vision (Vers. 0.1)

Service Integration Layer

Data

Security Services

Services

Data & Business Integration Layer

Administrative Services

ERP Services

Academic Services

Student InformationServices

Applications

User Interfaces

Auth

enti

cati

on Serv

ices

Auth

ori

zati

on Serv

ices

Learning Services Research Services

Applicant Portal

GrantManagement

PayrollFinance BudgetHR Purchasing

Applicants Students Alumni FacultyStaff

Core Services

List Management ServicesContent Management

ServicesE-Commerce Services

Directory & DemographicServices

Identity Services

EMail and MessagingServices

External IntegrationServices

Archival ServicesCollaboration ServicesMapping and Location

Services

Extended Community

Facilities

MedicalPresident's

OfficeEH & S Admissions Student Alumni

Library

ContentManagement

LearningManagement

TechnologyLicensing

Student Portal

Stand Alone GUIInterface

Stand Alone WebInterface

Alumni Portal

Extended CommunityPortal(s)

Faculty Portal

Staff Portal

ResourceDevelopment

FinanceData

HRData

FacilitiesData

GrantsData

MedicalData

StudentData

LearningData

ResearchData

LibraryData

DataWarehouse

Page 12: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 12 September 2004 © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

Example Logical Architecture Diagram: EHSWeb

Training Records& Requirements

DB(Oracle)

Users

SystemComponent

Key:

RelatedSystem

Other MITSystem

ExternalSystems

Other MIT Systems

Incoming: SAP TEM (On

Campus) SAP TEM (Lincoln

Labs) Roles

Outgoing: Data Warehouse

External Systems

Incoming: Netcaster (Web

based courses)

Outgoing: Netcaster (Web

based courses

Entering TrainingRules

UI

Training RecordsInput

UI

Training NeedsAssessment

UI

EHS Web

Training Records &Requirements

SAP TrainingEvents Module(On Campus)

SAP TrainingEvents Module(Lincoln Labs)

Data Warehouse

PI / SpaceRegistration

SARA(ReportingInventory)

Netcaster

Other MIT Systems

Page 13: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 13 September 2004 © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

Example Physical Architecture Diagram: EHSWeb

Facility W91 - Primary Facility E40 - Backup

RAID for DatabaseStorageVendor:Model:Capacity:

Facility orLocation

Key:

PhysicalServer orStorage

Production and Application Server:Hardware: SunOperating System: Sun SolarisSoftware: - Apache Web Server - Apache Tomcat

Production Database Server:Hardware: SunOperating System: Sun SolarisSoftware: - Oracle Database Server

Test/Backup Server:Hardware: SunOperating System: Sun SolarisSoftware: - Apache Web Server - Apache Tomcat

Page 14: Page 1Version 0.1 September 2004 MITEnterprise Architecture © Copyright Massachusetts Institute of Technology 2004, All Rights Reserved Enterprise Architecture

Page 14 Version 0.1 September 2004

MIT

En

terp

rise

Arc

hit

ect

ure

© Copyright Massachusetts Institute of Technology 2004, All Rights Reserved

MIT Enterprise Architecture Guide

Project

Further information:

Jerry Grochow ([email protected])

Scott Thorne ([email protected])

Steve Winig ([email protected])