Enterprise Architecture Executive Overview Executive Program Overview PDS Conference March 28, 2007

Enterprise Architecture Executive Overview

Executive Program OverviewPDS ConferenceMarch 28, 2007

Page Page 22

March 28, 2007 EA Program Overview - PDS Conference

Evolution of EA

The history of EA starts with the Zachman Framework of the 1980’s Segments an organization into

addressable pieces using "who, what, when, why, where, and how“

Segmenting the organization allows in-depth focus on each segment alignment with strategic goals and support for accomplishing the mission

The description becomes a model of the organization to be analyzed for efficiency opportunities.

The Zachman Framework evolved and became the baseline model for Enterprise Architecture. The FEA is rooted in this Discipline.

Page Page 33


Federal Enterprise ArchitectureCore Principles

Business-driven: The FEA is most useful when it is closely aligned with government strategic plans and executive level direction. Agency mission statements, presidential management directives and agency business owners give direction to each agency’s enterprise architecture (EA) and to the FEA.

Proactive and collaborative across the Federal government: Adoption of the FEA is achieved through active participation by the EA community in its development and use. The FEA community is responsible for the development, evolution and adoption of the FEA.

Architecture improves the effectiveness and efficiency of government processes: Architecture development is an integral part of the capital investment process. Investment decisions should be based on business-approved architecture.

Page Page 44


Federal EA GovernanceLaws and Policy

Government mandates require each Agency to plan, procure, and deliver business products and services through Enterprise Architectures:

LAW -The OMB’s Government Performance & Results Act (GPRA) and Chief Financial Officers (CFO) act mandates performance-based measures that tie all capital investments to Agency EA

LAW - The Clinger-Cohen Act (CCA) formerly known as the Information Technology Management Reform Act (ITMRA) originally assigned CIO’s the responsibility to develop and maintain an agency-level EA

POLICY - OMB M-97-02 - Requires that Agency investments in major information systems be consistent with EAs.

LAW - The Federal Information Security Management Act (FISMA) requires IT Security Planning as part of an EA

LAW - The Paperwork Reduction/Elimination Acts (PRA/GPEA) requires agencies to conduct operational and Strategic IT planning as a basis for budget requests

Page Page 55


NASA EA Guiding Principles

Customer Driven Solutions that Enable Business Achievement

Customer Focused Ownership Collaboration

Maintain an Adaptable Infrastructure Interoperable, Extensible, and Open Systems IT Security Smallest Set of Systems that Fully Cover

Agency Requirements Bind Technology at the Last Possible

Moment Commonality

Information is a Strategic Agency Asset Information Management Develop Conceptual Models to Facilitate

Discussions Include Appropriate Performance Metrics

Best Investment Value for the Agency Economically and Technically Achievable Leverage Existing Investments Focus on the "Big Picture.” Greatest Cost/Benefit

Page Page 66


Enterprise Architecture Roles

Business/ Technology

Strategy

EnterpriseArchitecture

Bu

sin

ess

Info

rmat

ion

Info

rmat

ion

S

yste

ms

Tec

hn

olo

gy

In

fras

tru

ctu

re

BP

M/C

RM

/ER

P

Su

pp

ly C

hai

n

Man

ag

emen

t

Wo

rkfl

ow

A

nal

ysis

Info

rmat

ion

A

nal

ysis

So

ftw

are

Arc

hit

ectu

re

Dat

a A

rch

itec

ture

Sec

uri

ty

Arc

hit

ectu

re

Net

wo

rk

Arc

hit

ectu

re

Solution Delivery

Solution Design

Strategic Governance Enterprise

Architects

System Architects

Software Architects

Systems Architecture

Solutions Architecture

Page Page 77


NASA EA Architecture States

Enterprise Architecture allows the Mission Areas to: Evaluate the Agency’s information solution and service needs required for

mission success against the current state Identify any gaps Formulate concepts and opportunities to fill the gaps

Baseline State Target State

What do we have? What do we need?

Lines of Business

Processes

Services

Capabilities

Data

Facilities

New Requirements

Processes

Services

Enabling Investments

Data

Facilities

Transition Strategy

Projects to build New Services/Capabilities

Funding Requests

Review Current Services for use in Future State

EliminateRedundantSystems

Sunset Obsolete Services

Milestones& Metrics

Identify Gaps & Build Plans

Page Page 88


Approach to Investing

Resources are freed and re-purposed for fundamental research and other scientific endeavors though increasing efficiency and effectiveness

Resources are freed and re-purposed for fundamental research and other scientific endeavors though increasing efficiency and effectiveness

DME

SS

Investment TypesInvestment Types

DME

Average Investment Average Investment Distribution (Industry)Distribution (Industry)Develop Develop

Modernize Modernize EnhanceEnhance

Steady StateSteady State SS

DME

SS

20%20%

80%80%

New investments that improve our enabling capabilities

Approved investments that support ongoing operations

…comes by improving operational efficiencies here.

New investment money here…

75%75%

25%25%

How do we fund How do we fund new DME?new DME?

Page Page 99


Contract Management ModuleEA Review Example: Cost Benefit Analysis

Project Costs - CMM 10-year Present Value Project Investment and O&SS Cost: ~$65,077,000

Project Savings: Retirement of Legacy Systems ~$43,466,000 *Additional System Cost Avoidance ~$25,649,000 **Realignment of work / Mission Savings ~$6,093,000 ***Total Savings: ~75,208,000

Total Positive CBA based on cost savings: ~$10,131,000

* Legacy system savings are based on decommissioning systems

** Cost avoidance is based on presumed upgrades, enhancements, and additional development that would have to be performed in order for status quo systems to meet Agency requirements

*** Mission savings are achieved when Contract Specialists can realign from low-value to high value-add tasks

The EA Review team helped structure and articulate the

positive benefits of this investment to NASA

Executive Management.

Information is shared with permission from the CMM EA Review, May 2005

Page Page 1010


NDC ServicesEA Review Example: Customer Analysis

Cu

sto

me

r D

en

sity

Bu

siness &

Fin

ance

Institu

tion

al and

In

frastructu

re

Pro

gram

/ Pro

ject

Hosting Mainframe (Avg) 144 61 261 19Hosting Midrange 4,300 1,200 3,100 0Basic Web Hosting (Avg) 2,038 0 2,038 0Archival (Agency Data Optical Storage System) 646 419 6 0Business Management (Brio Enterprise) 365 326 0 0Infrastructure Access Application Hosting (Citrix) (Avg) 3,101 3,051 0 50Collaboration (Sharepoint) 1,200 0 948 252Housing Service (Avg) 19,570 9,917 ~ 66,000 1,800 300Application Development & Sustaining Engineering 7 3 0 0Custom Course Development 20 2 6 2Print Service 4,995 2,000 2,421 550Scheduling Service 23 8 9 6Disaster Recovery Service 43,450 25,255 17,503 354Database Management and Administration (Avg) 9,473 3,681 16 317Security 7,222 200 5,362 1,570Systems Administration 7 3 3 1

Service

Hu

man

Cap

ital

2600

2213900

41024

0

0338

5,45990

The NDC currently provides IT operations and maintenance support for mainframe, midrange, infrastructure (SAN, Active Directory, etc.) and application development services.

The EA Review team helped the NDC define its

portfolio of services and the customers who use the services

Information is shared with permission from the NDC EA Review, June 2005

Page Page 1111


EA Promotes Investment Integration

Badging and Identity Services

CBACSMaster

IdentityValidation

LenelRegional

LenelRegional

IDMS

Public Directory Services Enterprise Directory Services

X500 PublicLDAP

Entrust CertificateAuthority

AgencyApplications

NISEE-Authentication

Portal to FederalE-Authentication

Gateway

E-Authentication Portal

Agency Domain

Center Domain

Center Domain

Center Domain

Active Directory Services

AccountManagement

Services

Meta-DirectoryServices

Workflow

LenelMaster


CBACSMaster

IdentityValidation

LenelRegional

LenelRegional

IDMS


X500 PublicLDAP


SSO Across Agency

ApplicationsNISE

E-Authentication

Inside NASA Portal to FederalE-Authentication

Gateway


Agency Domain

Center Domain

Center Domain

Center Domain


Self Service& SSO

Management Services

Management Services



Services

LenelMaster

CBACS Project NDC Active Directory Services


CBACSMaster

IdentityValidation

LenelRegional

LenelRegional

IDMS


X500 PublicLDAP


AgencyApplications

NISEE-Authentication

Portal to FederalE-Authentication

Gateway


Agency Domain

Center Domain

Center Domain

Center Domain


AccountManagement

Services

AccountManagement

Services



Workflow

LenelMaster


CBACSMaster

IdentityValidation

LenelRegional

LenelRegional

IDMS


X500 PublicLDAP


SSO Across Agency

ApplicationsNISE

E-Authentication

Inside NASA Portal to FederalE-Authentication

Gateway


Agency Domain

Center Domain

Center Domain

Center Domain


Self Service& SSO

Management Services

Management Services



Services

LenelMaster

CBACS Project NDC Active Directory Services

Through common reference architectures, EA helps integrate services to maximize NASA’s resources to achieve its mission.

Through common reference architectures, EA helps integrate services to maximize NASA’s resources to achieve its mission.

Example: NISE Identity Management System

(IDMS) Cyber Identity Management

System (CIMS) NASA Account Management

System (NAMS) E-Authentication Initiative

Page Page 1212


Approach to Success

By design, the EA program started out small in scope Focused on investments within the OCIO and cross-cutting institutional

investments Benefits of this Approach:

Build policy, governance, and methods within our own workspace Build tools and processes for investment reviews Record and analyze results Iterate, improve, and refine the EA program Prove that EA adds value

AND ONLY THEN

Extend the program as a service to the Mission Directorates, with the hope of delivering similar value

Must recognize that each Mission Directorate is unique, and so are many of its services and capabilities

Page Page 1313


EA Reviews: Federal Best Practice

The NASA Enterprise Architecture Team received the E-Gov Institute's "Government Civilian Leadership in Government Transformation Award" on September 13th, 2006.

NASA’s Enterprise Architecture Review process is recognized as a federal Best Practice.

Page Page 1414


NASA Enterprise Architecture

SOMD Segment

ESMD Segment

SMD

Se

gmen

t AR

MD

Segm

ent

Mission Support Segment

NASA has 5 Segment Architectures:

One for each Mission Directorate which are our Lines of Business (LoB)

One for Agency cross-cutting capabilities (IT, CFO)

Each Business has their own unique common operational elements

EOSDIS High-Performance Computing

Each Business has Federal Enterprise Architecture (FEA) unique Elements:

SMD: Under Development SOMD: ISS, Shuttle, CLV, CEV

Page Page 1515


SMD Segment (incomplete)

Major Mission Services

Mission Cross-cut Segment Services

Agency-wide, cross-cutting Services

Mission Support Services

Centers’ Mission Facilities

“The Scope of the SMD Segment includes SMD-funded research and analysis, and activities to the project level directly funded by the Science Mission Directorate:• includes space mission programs and projects, sub-orbital and laboratory programs and projects, scientific research, technology development, and applications research”-Gordon Johnston, SMD Chief Architect

Planetary Science

Earth Science

Astrophysics

Deep Space

NetworkData

Centers

Ground Network

Heliophysics

High Performance Computing

Page Page 1616


Mission Support Segment

Mission Support Segment includes: Executive Offices Mission Support Offices Executive Functions NASA Centers’

Infrastructure Component Facilities OCIO

OCFOGeneral Counsel

Proc

urem

ent

Human Capital

Chief Engineer

Administrator

PA & E

S &

MA

Ext

ern

al R

elat

ion

s

Pu

blic A

ffairs

OIGNASA

Centers’ Common

Infrastructure Support Facilities

Page Page 1717


EA support within each Mission Directorate Agency EA will be evaluated by OMB on ability to

develop Segment Architectures Agency EA will focus on bringing value to the Mission

Directorates, Mission Support Offices, and federal e-Gov programs

Explore EA integration with Agency Management & Focus Teams

In-depth analysis of agency services and SOA’s (Recent FCW Article on Popular SOA Myths)

Use of the EA repository to deliver information about investments and their relationships with other investments

EA Next Steps - Longer Term

Page Page 1818


Questions ????

Bob StaufferEnterprise Architect

[email protected]

Office: 440-328-3120Cell: 440-725-3194

Documents

Enterprise Architecture Executive Overview Executive Program Overview PDS Conference March 28, 2007