Enterprise ArchitecturePlanning

(EAP)

Office of Information Technology and System Strategy

23 FEB 2001 2

Discussion

• What is Enterprise Architecture Planning (EAP)?

• What is an EA used for?

• Why should we do it?

23 FEB 2001 3

A comprehensive blueprint of an organization.

The structure of (Enterprise) components and their relationships, as well as principles and guidelines governing their evolution over time.

A common understanding by all, of the names and definitions of an organization’s entities.

What is an Enterprise Architecture?

23 FEB 2001 4

The EA is a strategic asset repository which defines the current and target architecture environments, including:

•the business,

•the information,

•the technology, and

•the transitional processes.

What is an Enterprise Architecture?

Source: Federal Conceptual Architecture model

23 FEB 2001 5

PERSON PLACE THING EVENT CONCEPTCG MEMBER CG ORGANIZATION COAST GUARD ASSET MARITIME ACCIDENT REGULATIONAUXILIARIST NAVIGABLE WATERS ATON COASTAL INTRUSION LAWMARINER GOVERNMENT FACILITIES COMMERCIAL VESSEL RESPONSE ACTIVITIES STANDARDSRECREATIONAL BOATERS AIR RECREATIONAL BOAT ATON DISCREPENCY DIRECTIVECONTRACTORS BRIDGES PORT FACILITY PREVENTION ACTIVITIES PLANGOVERNMENT CONTACTS REGULATED MANUFACTURERS ICEBERG DEFENSE OPERATIONS MISSIONREGULATED MANUFACTURERS HAZARDOUS MATERIAL ACQUISITION LEGAL REQUIREMENTCASUALTY CUSTOMER ASSET SUPPORT OPERATIONS INTERNATIONAL AGREEMENT

BUDGET BUDGET BUILD POLITICSRADIO FREQUENCY SPECTRUM CASESUPPORT ASSETSTRAINING/EDUCATION PROGRAMSCASEMETA DATAFUNDS

Examples - Entities

Source: U.S. Coast Guard Information Architecture

A distinguishable - person - about which information is kept. place, thing, event, concept

23 FEB 2001 6

T1 Lines

HQFINCEN

MLCP

OSC

ISC Honolulu

D17

AR&SCISCBoston

ISC PortsTISCOMELCPPCISCNOLA

ISCMia.

ISC St Louis ISC Cleve. CAA MLCA

WMEC

WPB

WLB

AOR

FACILITIES

INFRASTRUCTURE

PLATFORMS

PERSONNEL

Architecture Layers

23 FEB 2001 7

Some EAP Components

•A standard methodology

•A standard set of templates

•A repository

•A configuration management process

•Easy access

•Ability to export

23 FEB 2001 8

List of LocationsImportant to Business

Node=Major Business Location

Data Function Network People Time Motivation

List of Things Important to Business

Entity=Class ofBusiness Thing

List of Processes theBusiness Performs

Function=Class of Business Process

List of OrganizationsImportant to Business

Agent=Major Org Unit

List of EventsSignificant to Business

Time=Major BusinessEvent

List of BusinessGoals/Strategies

End/Means=MajorBusiness Goal/CSF

e.g., EntityRelationship

Diagram

Ent=Business EntityRel=Business Rule

e.g., Function FlowDiagram

Function=Business Process

e.g., Data Model

Entity=Data EntityRelationship= Data

Relationship

e.g., Structure Chart

Funct=Computer FunctArg=Screen/Device

Formats

e.g., System Architecture

Node=Hardware/System Software

Link=Line Specification

e.g., Logistics Network

Node=Business Location

Link=BusinessLinkage

e.g., Program

Funct=Language StmtsArg=Control Blocks

e.g., NetworkArchitecture

Node=AddressesLink=Protocols

e.g., OrganizationChart

Agent=Org UnitWork=Work Product

e.g., Business Plan

End=Business Objectives

Means=BusinessStrategy

e.g., Human InterfaceArchitecture

Agent=RoleWork=Deliverable

e.g., Security Architecture

Agent=IdentityWork=Transaction

e.g., Processing Structure

Time=System EventCycle=Processing Cycle

e.g., Control Structure

Time=ExecuteCycle=Component Cycle

e.g., Timing Definition

Time=InterruptCycle=Machine Cycle

e.g., KnowledgeArchitecture

End=CriterionMeans=Option

e.g., Knowledge Design

End=ConditionMeans=Action

e.g., KnowledgeDefinition

End=SubconditionMeans=Step

e.g., Data DefinitionDescription

Ent=FieldsRel=Addresses

e.g., Data Design

Entity=Segment/RowRelationship=Pointer/

Key

e.g., Data Flow Diagram

Funct=Appl FunctionArg=User Views

Analyst Engineer Secretary

e.g., Human/Technology Interface

Agent=UserWork=Job

Analyst Engineer

e.g., Master Schedule

Time= Business EventCycle=Business Cycle

e.g., DistributedSystem Architecture

Node=Info Sys FunctLink=Line Char

Secretary

Planner’sView

Owner’sView

Designer’sView

Builder’sView

Subcontractor’sView

Zachman’s Framework forInformation Systems Architecture

23 FEB 2001 9

•Acquisition

•Investment decisions

•Modeling & Simulation

•Analysis

•Requirements definition

•Plan baseline

•Describing and understanding baseline

What is an EA used for?

23 FEB 2001 10

OperationalView

Identifies WarfighterRelationships and Information Needs

SystemsView

Relates Capabilities and Characteristicsto Operational Requirements

TechnicalView

Prescribes Standards andConventions

Specific CapabilitiesIdentified to SatisfyInformation-ExchangeLevels and OtherOperational Requirements

Technical Criteria GoverningInteroperable Implementation/Procurement of the SelectedSystem Capabilities

Processing and Levels of

Information Exchange

Requirem

entsBasic Technology

Supportability and

New

Capabilities

Syst

ems

Ass

ocia

tions

to N

odes

, Act

iviti

es,

Nee

dlin

es a

nd

Req

uire

men

ts

Proc

essi

ng a

nd In

ter-

Nod

al

Leve

ls o

f Inf

orm

atio

n

Exch

ange

Req

uire

men

ts

DoD C4ISR Architecture Framework 2.0

23 FEB 2001 11

DoD C4ISR Architecture Framework 2.0

23 FEB 2001 12

What is an EA used for?

• Promote interoperable and cost-effective systems

• Provide the rules, guidance and product descriptions for developing and presenting architectural descriptions

• Ensure a common denominator for understanding, comparing, and integrating architectures.

• Enable architectures to contribute more effectively to engineering interoperable and cost-effective systems.

• Provide a mechanism for managing complexity.

23 FEB 2001 13

Information SystemsTechnical Architecture

COMDTINST5230.45A

Information SystemsTechnical Architecture

COMDTINST5230.45A

USCGCommonOperation

Environment

(USCG COE)

COMDTINST5230.59A

USCGCommonOperation

Environment

(USCG COE)

COMDTINST5230.59A

Standard Workstation III Configuration Management

Policy

COMDTINST5200.16

Standard Workstation III Configuration Management

Policy

COMDTINST5200.16

USCGC4ISR

Baseline Architecture

COMDTINST3090.6

USCGC4ISR

Baseline Architecture

COMDTINST3090.6

Planning Approvalfor Automated

Information Systems(AIS)

COMDTINST5231.2

Planning Approvalfor Automated

Information Systems(AIS)

COMDTINST5231.2

InformationResource

Management(cancelled)

COMDTINST5230.41

InformationResource

Management(cancelled)

COMDTINST5230.41

Standard TerminalApplication Software

DeploymentCOMDTINST5234.3

Standard TerminalApplication Software

DeploymentCOMDTINST5234.3

Information TechnologyLife Cycle and

Configuration Management Policy

COMDTINST 9999.99

Information TechnologyLife Cycle and

Configuration Management Policy

COMDTINST 9999.99

IT Life Cycle and CM Policy Consolidation

ITSystems Development

Plan(DRAFT)

COMDTINST9999.99

ITSystems Development

Plan(DRAFT)

COMDTINST9999.99

Other Policy

TBD

Other Policy

TBD

23 FEB 2001 14

Benefits

Facilitates information services that provide:

flexibility,interoperability,reliability,survivability,affordability,sustainability,portability, reusability,Adaptability,Compatibility

23 FEB 2001 15

Business Benefits of EAP

• Focus on strategic use of technology for managing data as an asset• Standard vocabulary facilitates communication and reduces

inconsistency and data redundancy• Documentation increases understanding of the business• Models can be used to explain the business and assess the impact of

business changes• Decision making policies can be reviewed• Integration of current systems with new systems is considered.• It allows for a comprehensive, objective and impartial approach• The long range systems plan compliments the business plan• A cost-effective long term solution considers rate of return• It involves a feasible migration strategy with short term achievements• it is easier to assess the benefits of impact of new systems and

software• it allows easier accommodation of dynamic business changes such as

mergers, acquisitions, new products, lines of business.etc.

• Management participation provides a business prospective, credibility, confidence, and demystifies system development.

Source: Enterprise Architecture PlanningSteven Spewak

23 FEB 2001 16

Benefits to the Business of planned systems• More responsive to customer’s needs• Reduced data-entry costs• Head-count is reduced• Increased productivity of personnel permits increased level of

business and containment of costs• Improved skills raise enthusiasm and loyalty• Efficient systems maintenance means improved service.• Architectures eliminate complex costly interfaces incongruent

systems• Management decisions in all functional areas will be based on more

accurate and timely data, leading to various improvements and cost-saving measures

• End user has direct access to shared data• New systems are developed faster and at less cost due to common

data, common code, anda shortened requirements phase

• Easier to evaluate and select vendor SW packages• Effective use of repository and CASE products

Source: Enterprise Architecture PlanningSteven Spewak

23 FEB 2001 17

"You may think this is too much work…Or, it takes too long

And it costs too muchOr is too theoretical

Or too high riskOr too whatever.

However, if that’s your assessment…You can’t complain that

the systems aren’t “aligned” with the enterprise,orare inflexible,

or cost too much,or that vital information is not available,

or that the data you get isn’t any good, or too late,or you can’t change anything,

or that I/S is slow and unresponsive…and, I am here to tell you

Outsourcing isn’t going to fix the problem.Packages (in themselves) won’t fix the problem.

Decentralization won’t fix the problem.And, the Internet isn’t going to fix the problem.

No amount of money, Ortechnology is going to fix the problem!

It is NOT a technical problem, it is an ENTERPRISE problem.

Only ACTUAL WORK is going to fix the problem, and“Someday, you are going to wish you had all those

models, Enterprise wide,

horizontally and vertically integrated,at excruciating level of detail.”

You might as well start working on them TODAY!!!

John Zachman

Zachman reflections on EA Planning

23 FEB 2001 18

Next Steps

• CKO Charter an Enterprise Architecture Configuration Control Board (EACCB)

• Identify goals, objective, principles

• Establish membership

• Identify a methodology

• Identify a framework

• Identify resources

• Define deliverables

• Establish a timeline

• CKO Charter an Enterprise Data Dictionary Configuration Control Board (EDDCCB)

23 FEB 2001 19

DISCUSSION