Enterprise Architecture (EA)A Journey in Building a Corporate-wide EA Practice

Edwin Nassiff

Deputy CTO and Director of Architecture

May 15, 2008

Topics

• Lockheed Martin (LM) Corporation

• LM Enterprise Architecture (EA) Concept

• EA Background at Lockheed Martin (LM)

• LM Enterprise Architecture Framework (LEAF)

• Challenges

• Harmonization Example

• 140,000 Employees

• 70,000 Scientists and Engineers

– 25,000 IT Professionals

• Operations in 1,000 Facilities, 500 Cities, 46

States and 63 Countries

Lockheed Martin - Demographics

Building a Better Workforce

• Top Corporation for Multicultural Business (Top Corporation for Multicultural Business (Diversity Business)Diversity Business)• Number 1 – “Ideal Employer” (Number 1 – “Ideal Employer” (Universum Undergraduate Survey)Universum Undergraduate Survey)• Number 1 – “Best Place to Work” (Number 1 – “Best Place to Work” (Woman EngineerWoman Engineer))• Number 2 – “Best Places to Launch a Career” (Number 2 – “Best Places to Launch a Career” (Business WeekBusiness Week))• Number 4 – “Top 100 Employers” (Number 4 – “Top 100 Employers” (Black Collegian)Black Collegian)• Number 5 – “Top 100 Best Places to Work” (Number 5 – “Top 100 Best Places to Work” (Training Magazine)Training Magazine)

Recognized as “Employer of Choice” and Industry “Diversity Leader”

Executing Complex Projects

… Requiring Integrated Solutions

… With Advanced Technology and Systems Integration Skills

… Across Lockheed Martin and With OurPartners

… For Our Government Customers

Delivering Products and Services That Perform … with Extraordinary Reliability

Distinguished by Whole-Systems Thinking (Holistic Distinguished by Whole-Systems Thinking (Holistic Approach)Approach)

Distinguished by Whole-Systems Thinking (Holistic Distinguished by Whole-Systems Thinking (Holistic Approach)Approach)

Redefining What Is Possible

Return of Crew Space Return of Crew Space ExplorationExploration

BiometricsBiometricsBiometricsBiometricsHypersonics Hypersonics

Unmanned Unmanned and and

AutonomousAutonomousSystems Systems

Information FusionInformation FusionPersistent Surveillance Persistent Surveillance

A Passion for InventionA Passion for InventionA Passion for InventionA Passion for Invention

Lockheed Martin Business Areas

Electronic Electronic SystemsSystems

$12.1B$12.1B

Space SystemsSpace Systems

$7.9B$7.9B

AeronauticsAeronautics

$11.1B$11.1B

Information Information Systems & Systems &

Global Global ServicesServices

$10.1B$10.1B

2007 Total Sales - $41.2B2007 Total Sales - $41.2B2007 Total Sales - $41.2B2007 Total Sales - $41.2B

Enterprise and Architecture Definitions

• Enterprise: any organization that exists to perform business activities for some purpose or mission. For Lockheed Martin, examples include: – Lockheed Martin as a corporate entity– Business Areas/Business Units– Business Functions– Programs (including customers, business partners, and suppliers)– Any subset or combination of the above– In our case- the subject of an architecture analysis pertains to

achieving a business objective

 • Architecture: “The fundamental organization of a system, embodied in

its components, their relationships to each other and the environment, and the principles governing its design and evolution” (ANSI/IEEE Std 1471-2000)

Enterprise Architecture Defined

• Enterprise Architecture (as a practice): A business discipline of analytical tasks and techniques that use a business centric approach to documenting and analyzing an enterprise in its current and future states from an integrated business and technology perspective.

• Enterprise Architecture (as models): A holistic set of descriptions of an enterprise covering the perspectives of Business, Applications, Data, and Technical Infrastructure, the relationships between those descriptions, and the principles and guidelines governing their design and evolution over time.

• Systems Architecture: A decomposition of the technology architecture (IT computing systems) into System, Subsystem and Component Levels

Traditional IT Systems Engineering Approach

BusinessEngagesIT

BusinessIdentifiesNeed

BusinessPlansChanges

IT ImplementsSystem

Business Perspective

IT Systems Perspective

DevelopDesign

Deploy

ITVerifiesDesign

Results in

Separately Developed Local Solutions Create Significant Integration Challenges

Why Do EA?• Align IT to business needs• Facilitate dialogue among stakeholders and strategy execution• Improve investment decisions, success rate, and reduce risk• Create better business agility and lessen project development

duration • Produce more accurate project schedules• Leverage the scale of our enterprise by reducing duplicative efforts• Uncover and flag problems before it is too late• Eliminate high operation and maintenance costs (85% of costs are

in O&M)• Ensure that new systems are the right ones• Avoid consulting services• Take advantage of inside/out opportunities• Provide comprehensive documentation of the enterprise

EA Background at LM

• John Zachman assigned to Lockheed Aircraft facility in Burbank, CA - 1980’s

• Stove-pipes - EA widely practiced throughout LM - 1990’s• Clinger-Cohen Act of 1996 – mandates EA for government activities• IT Architecture Framework (ITAF) published - 1998• LM EA Community of Practice - Council of IT Architects (CITA) –

2003• Executive interviews on EA - May - September 2007• Spiral 1 - LM Enterprise Architecture Framework (LEAF) – May

2007• Formation of new governance councils with architecture orientation

– February 2008• LEAF EA Certification Training - April 2008

Information Systems

Architectures

Architecture Repository

Enterprise Architecture ConOps

Use harmonizedABD, SEP, etc.

Enterprise Architectures

ADM

ADLARM

EA Governance

Support TrainingTools

LEAF

LEAF Components

ArchitectureDevelopment

Language

ArchitectureDevelopmentMethodology

ArchitectureReference

Models

ArchitectureGovernanceProcesses

LEAF - Intended to Be Best in Show

LEAF ADM LEAF ARM

Artifact Guidance

Methodology Guidance

Low

High

The Open Group Architecture Framework (TOGAF)

DoD Architecture Framework (DODAF)

Zachman Framework

InformationContent Guidance

Medium

TOGAF

ZACHMAN

DODAF

Federal Enterprise Architecture Framework (FEAF)

FEAF

ReferenceModels

Lockheed Martin Enterprise Architecture Framework (LEAF)

LEAF ADL

Goals & Objectives

• Goals– Widespread reuse of architectural artifacts– Improved agility and integration– Optimize business alignment and return on IT investments

• Objectives– Establish a common EA discipline used in the development of business-aligned

internal-facing enterprise IT systems– Harmonize with other corporate processes (e.g., ABD, SEP, LM21, etc.) to facilitate

the alignment of IT to business requirements– Revise IT governance to appropriately guide IT architecture– Provide EA tools and services to support the above objectives

EA Critical Success Factors

• Executive sponsor support

• Participation by key BA stakeholders in development of reference architectures

• Adoption of LEAF and widespread reuse of architectures

• Staffing and retaining sufficient architects with requisite EA skills

• Harmonization with other related architecture processes

Views in the LEAF ADLMotivational View

Identifies what the enterprise wantsto achieve, how it measures success

-

Strategy View

Translates highest-level requirements into strategy

requirements

Strategy View

Identifies guidance that isin place to ensure success

Business View

Translates goals, principles, measures of success,

and strategy requirementsinto business requirements

Identifies what the enterprisedoes, its information andinformation exchanges

Systems View

Translates businessrequirements into

technology performance requirements

Systems ViewAssociates HW/SW withactions, organizations, business nodes,information exchanges

Information View

Translates all otherrequirements into

data/information requirements

Information View

Identifies data entities andrelationships, definitions,information production in the enterprise

Business strategies that reflect goals and architectural

principles

Actions, organizations, roles, business nodes, information exchange needs

Technology usedand interface standards

Enterprise goals, principles,and measures of success

Data entities

Data entities

Data entities

Business needs

Systems strategies that reflect goals and architectural

principles

Systems needs

Systems needs

Data entities

Data entities

Dataentities

Data entities

Dataentities

Business needs

Architecture Environment

PortfoliosPortfoliosPrinciplesPrinciplesStrategiesStrategiesRoadmapsRoadmapsStandardsStandardsPatternsPatternsProducts Products ServicesServices

ProcessesProcessesReference ArchitecturesReference Architectures

Enterprise Wide Enterprise Wide Business SpecificBusiness Specific

Support ServicesSupport ServicesTrainingTraining

ConsultingConsultingToolsTools

(Content)

Corporate Reference Architectures

RoadmapsProcesses

CorporateProducts

Strategies

Services

Architecture Building Blocks

Governance: Idea to Implementation Scenario

Other Reference Architectures

Core Artifacts

Mission and Vision StatementArchitecture Plan and JustificationBusiness Concept GraphicBusiness Actions ModelBusiness Node Connection ModelInformation Exchange MatrixImplementation RoadmapSystem Connection ModelHuman Actions/System Actions Matrix

Standards

Metadata

Reference Architecture

Contains

Is an instance of

Addresses

Mapped to

Depends on

May use

Is an alternative to

Is a subset of

Overlaps with

Expected status in one year

Expected status in three years

Strategy recommendation

Responsible architect

Type NumberElement

Architectural building block {0 .. n }

Link

age

Alig

nmen

tA

pplic

abili

ty

Exactly 1

LEAF-defined product

{1 .. n }

Reference model element {1 .. n }

Solution Architectures {0 .. n }

Architectural building block {0 .. n }

Solution Architectures {0 .. n }

{From set of defined terms]

{0 .. n }

Solution Architectures {0 .. n }

Solution Architectures

Exactly 1

Exactly 1{From set of defined terms]

Date

Exactly 1Individual

Exactly 1{From set of defined terms]

Current status Exactly 1{From set of defined terms]

Objective / requirement

Content Defined by LEAF product type

Effective/Expiration dates 1 each

Reference Architecture MetadataExampleLM P2P Ref Arch

Corp Standardization

Procurement Process

Parts Database

SAP Core Ref Arch

Legacy Procurement

LM Finance

None

TBD

01/2008 01/2013

Jane Doe

TBD

TBD

TBD

Growth, Run Business

(Content)

Corporate Reference Architectures

Architecture Governance

Core ProductsMission and Vision StatementArchitecture Plan and JustificationBusiness Concept GraphicBusiness Actions ModelBusiness Node Connection ModelInformation Exchange MatrixImplementation RoadmapSystem Connection ModelHuman Actions/System Actions Matrix

Metadata

Reference Architecture

IT Architecture Council

Recommend Approval

CIO Strategic Council

Approved

(Content)

Corporate Reference Architectures

Metadata

Other Reference Architectures

Contains

Is an instance of

Addresses

Mapped to

Depends on

May use

Is an alternative to

Is a subset of

Overlaps with

Expected status in one year

Expected status in three years

Strategy recommendation

Responsible architect

Type NumberElement

Architectural building block {0 .. n }

Link

age

Alig

nmen

tA

pplic

abili

ty

Exactly 1

LEAF-defined product

{1 .. n }

Reference model element {1 .. n }

Solution Architectures {0 .. n }

Architectural building block {0 .. n }

Solution Architectures {0 .. n }

{From set of defined terms]

{0 .. n }

Solution Architectures {0 .. n }

Solution Architectures

Exactly 1

Exactly 1{From set of defined terms]

Date

Exactly 1Individual

Exactly 1{From set of defined terms]

Current status Exactly 1{From set of defined terms]

Objective / requirement

Content Defined by LEAF product type

Effective/Expiration dates 1 each

Reference Architecture MetadataExampleLM P2P Ref Arch

Corp Standardization

Procurement Process

Parts Database

SAP Core Ref Arch

Legacy Procurement

LM Finance

None

Mandatory

Baseline

Baseline

Baseline

01/2008 01/2013

Jane Doe

Growth, Run Business

Typical EA Challenges

• Meaning of EA

• Autonomous Business Areas

• Business value of EA

• Change in leadership

• Products and architecture

• EA governance

• Moving train, fewer green fields• Perception of competing processes