1 of 14

Mapping Architecture Value

Face2Face 2013

2 of 14

3 of 14

4 of 14

Michigan IT Capital Project Requests

  • Teaching, Learning, Knowledge
    • BlueJeans site license
    • Lynda.com site license
    • Platform for T&L analytics
    • Large scale digital preservation repository
  • Research
    • Research Administration Portal (Rapids)
    • Visual Shared Services and Infrastructure
    • Campus collection of licensed software for research
    • Underwriting infrastructure costs of Flux cluster

​

​

​

Face2Face 2013

5 of 14

Michigan IT Capital Project Requests

  • IT Infrastructure
    • Mature IT Governance and Michigan IT
    • Enterprise Search capability
    • Improved IT Service Monitoring
    • Web Content Delivery Roadmap
    • Enterprise Identity and Access Management
    • Common Data for Analytics
    • Campus-wide Wi-fi upgrade
    • BYOD/Enabling unmanaged devices
  • Administrative Systems
    • Improve Biologic Safety & Compliance
    • Oracle Campus Solutions Upgrade
    • Oracle Financial Upgrade
    • Enterprise Technology Asset Management (ITAM)

​

Face2Face 2013

6 of 14

Michigan Enterprise Architecture Guiding Principles

Face2Face 2013

Principles that Drive the Direction of Technology at U-M

  • Innovation in technology should support the advancement of the university mission.
  • Pursue a “cloud first” approach to sourcing.
  • Pursue a “culture of plenty” with commodity services whenever practical.
  • Use the U-M IT governance structure to determine enterprise commodity services.
  • Construct systems in a modular way.
  • Seek agility. Choose solutions that can be readily implemented and extended.

​

7 of 14

Michigan Enterprise Architecture Guiding Principles

Face2Face 2013

Principles Pertaining to the Scope of Individual Services

  • Do not just provide tools; help users understand and adopt them.
  • Enable information access with appropriate data protection (free the data, responsibly).
  • Design from a user-centered workflow perspective.
  • Manage the full life cycle of a service.

​

8 of 14

Michigan Enterprise Architecture Guiding Principles

Face2Face 2013

Principles Pertaining to How Services are Built

  • Use service pricing and billing to incentivize user behavior whenever possible; supplement cost of services reasonably to promote universal adoption.
  • Use open standards whenever possible.
  • Establish effective service level standards.
  • Address compliance and policy requirements and support personal privacy.
  • Provide universal access for persons with disabilities.
  • Choose environmentally responsible solutions when possible (green computing).

9 of 14

Enterprise Architecture Assessment

​

Face2Face 2013

Campus Wide Lecture Capture Service

  • Strategic Class: Strategic. Blah Blah Blah
  • Adoption Pyramid: Common Good. Blah Blah Blah
  • Architectural Guidelines:
    • The following architectural guidelines satisfied with the proposal::
      • Guideline #1
      • Guideline #2
    • There are several guidelines that are applicable to this proposal that should be addressed during the design phase of the proposal.
      • Guideline #3.
      • Guideline #4
      • Etc. etc
  • Summary: Blah blah blah

10 of 14

Enterprise Architecture Assessment

​

Face2Face 2013

Campus Wide Lecture Capture Service

Architectural Impact

High

Low

Architectural Fit

High

Low

11 of 14

12 of 14

13 of 14

BlueJeans

Lynda.com

T&L Analytics

Digital Preservation

RAPIDS

Visualization Service

Research Software

Flux Infrastructure

IT Governance

Enterprise Search

Service Monitoring

Web Roadmap

Identity Access

Common Data (ESB)

Wi-fi Upgrade

BYOD

Biologic Safety

Financials Upgrade

Campus Solutions Upgrade

Asset Mgmt

14 of 14

Enterprise Architecture Value Mapping