garrison geobase enterprise architecture workshop

I n t e g r i t y - S e r v i c e - E x c e l l e n c e

Headquarters U.S. Air Force

Garrison GeoBaseEnterprise Architecture

Workshop2004 Compass Conference

San Antonio, TX15 August 2004

Laura Silsbee, Garrison GeoBase Architect(with thanks to Stacey Tyley, CE Chief Architect)

AF/ILEI


Agenda

1:30 – 2:15 pm - Enterprise Architecture OverviewEnterprise Architecture 101Portfolio Management and Enterprise Architecture

2:15 – 3:00 pm - DoDAF Architecture ProductsOperational, System, and Technical Standards ViewsIntroduction to required and supplementary products

3:00—3:30 pm – Break3:30 – 4:30 pm – Specifics on Requested Products4:30 – 5:00 pm – Next steps: Garrison GeoBase Enterprise Architecture (Version 1.1)


What is Enterprise Architecture?

Enterprise Architecture (EA) is:A strategic plan for business visionand activities.A method for linking informationtechnology to business processes.A blueprint that explains how all theIT management and infrastructureelements work together as a whole.A tool for enabling intelligentdecisions on how an organizationspends money.A legislated requirement for federaldepartments and agencies


Why Enterprise Architecture?

Purpose: Align IT investments with business needs

AF/CE Business Priorities,Goals, and Outcomes

• Strategic Plan• Business Functions• Data Requirements

AF/CE IT Investments

• Major Development• System Modernization

• Infrastructure Upgrades

EA bridges business and IT providing basis forexecutive decision making and capital planning

and investment control guidance.


Enterprise Architecture Goal

CLEARLY link an organization’s mission, strategic plan, andbusiness processes to Enterprise Architecture to Capital IT

Investment Planning and Decision Making -Portfolio Management

Strategic Plan

BusinessProcesses

MISSION

EnterpriseArchitecture

Road Map

JustifiableIT FundingDecisions


How Did We Get to This Point?OMB CIRCULAR A-130

“The policies in this Circularapply to the information

activities of all agencies of theexecutive branch of theFederal government.”

CLINGER-COHEN ACT of 1996“Agencies must document and submittheir initial EA to OMB. Agencies must

submit updates when significant changesto the Enterprise Architecture occur.”

PL 107-314“The transition plan developed under subsection(a) shall contain specific time-phased milestonesfor modifying or eliminating existing systems and

for acquiring new systems necessary to implementthe proposed enterprise architecture.”

•SAF Policy on EA 6 Aug 02•EAIC Charter 20 Dec 02•SECAF &CSAF AFOSMP 20 Jan 04•Commander’s IPT 3 Mar 04

AF/IL PfM, EA,and GCSSCompliance

FY 04…05…06?

BUSINESSMANAGEMENT

MODERNIZATIONPROGRAM (BMMP):

Required by OMB, DoD,and AF; identifies

requirementsjustification; makes

USD(C) accountable forreleasing IT funds

TODAY!


A Common Sense Approach

PerspectiveIllustrates functional and integrated needs holistically

CommunicationProvides clear documentation of your enterprise so that it can beunderstood by all concerned

Analysis of Problem AreasHelps uncover and flag problems before it’s too late

BudgetHelps organizations make reasonable investment decisions

EfficiencyHelps ensure business processes are working optimally

Use of TechnologyHelps ensure that IT solutions are the right ones

TrainingHelps new personnel understand the enterprise and the toolsavailable to them


Collaboration is a Prerequisite

Federal EA

DoD EA

USA EAUSN EA

USAF EAWarfighter Mission Area

Infrastructure Environment

Operational Support Mission Area

Financial MgmtDomain Health Services

Domain

AcquisitionDomain Personnel

Domain

IL Domain

CESVS

COMM

LOG(Lead)


Additional Collaboration

Business Enterprise Architecture (BEA)

Operations Support Enterprise Architecture(OSEA)

WARFIGHTER(Lead: CJCS)

OSD Enterprise Architecture

AF Enterprise Architecture

BUSINESS MANAGEMENT(Lead: USD(C))

ENTERPRISE INFORMATIONENVIRONMENT

(Lead: ASD(NII)/DoD CIO)

NATIONAL FOREIGNINTELLIGENCE(Lead: USD(I))

MISSION AREAS

DOMAINSTBD Acquisition

(Lead: USD(AT&L))

Logistics(Lead: USD(AT&L))

Strategic Planning/Budgeting(Lead: USD(C))

Installations & Environment(Lead: USD(AT&L))

Accounting & Finance(Lead: USD(C))

Human Resources Mgmt(Lead: USD(P&R))

TBD TBD

ARCHITECTURES

MISSION AREAS

WARFIGHTING OPERATIONS SUPPORT INFRASTRUCTUREENTERPRISE

Combat Ops(Lead: ACC)

Health Services(Lead: AF/SG)

Installations & Logistics(Lead: AF/IL)

Modeling & Simulation(Lead: AF/XI)

Space Ops(Lead: AFSPC)

Mobility Ops(Lead: AMC)

Special Ops(Lead: AFSOC)

Air Traffic Management(Lead: AFFSA)

Weather(Lead: AF/XOW)

Personnel(Lead: AF/DP)

Acquisition(Lead: SAF/AQ)

Financial Management(Lead: SAF/FM)

Infostructure(Lead: AF/XI)

CivilEngineering

Logistics

Notes:1. Civil Engineer EA must respond to many forces.2. Logistics EA and Civil Engineer EA are in different domains in OSD, but in same mission areawithin AF, with AF/IL as lead3. Civil Engineer should work with Combat Ops4. Civil Engineer should work with Modeling & Simulation cross-cutting area5. AF-CIO owns technology aspects of AF EA; AF CIPT owns business process aspects of AF EA


What’s the Payback?

INTEGRATING ENTERPRISE ARCHITECTURE AND PORTFOLIOMANAGEMENT PROVIDES OPPORTUNITIES TO:

Reshape strategic vision for organizationReduce or remove information and/or process stovepipesRevamp decision-making policiesImplement improved organizational governance and structureIncrease synergy between business and IT personnelIncrease communications about business and supporting ITVisualize impacts of change on business and supporting ITIncrease objectivity in decision-makingAnalyze rate of return for long-termsolutions


Enterprise Architecture Drivers

Legislation and policy have a“hammer”

IT initiatives with total funding> $1M will not be approvedwithout a completed EnterpriseArchitecture and transition planafter 30 Sep 05Continued lack of enterprisearchitecture is causing Congressto lose faith in DoD ITmanagement, resulting inreduced IT funding acrossappropriationsServices losing control of IT toOSD domains, includinginvestment decisions


Enterprise ArchitectureBasic User Needs

Understand Enterprise Architecture wellenough to:

Support Civil Engineer EA (CEEA)developmentRecognize and understand products

Understand Portfolio ManagementIntertwined with EnterpriseArchitecture

Understand GovernanceUnderstand how to fit into IL’s, AF’s,and OSD I&E’s governance structureChange ILE’s governance structureto accommodate strategic nature ofenterprise architecture and portfoliomanagement


Upcoming Suspenses

AF/IL Requirements per policy memos:By 30 Sep 04, must:

Identify EA project management office and chief architectIdentify small headquarters working groupDefine the scope, vision, and objectivesAdapt a methodologyDetermine framework and toolsetDefine working group(s) for BPRProduce a concept of operationsAcquire development support

By 30 Sep 05 must:Hold larger corporate working group(s)Produce framework products for as-is, to-be, and transition enterprise architecturesConduct public relations activities (i.e., education, organization change)

DoD has been directed by OMB and Congress to complete by 30 Sep 05

PLUS Periodic Checks with ILE for Mid-Course Corrections and Affirmation


EA First Step: Adopt Methodology

Provide a common set of procedures for developing architectureproducts to help ensure consistency across the organization fordeveloping and maintaining the enterprise architecture

Must be documented, understood, and consistently appliedPrescribed standards, steps, tools, techniques, and measuresto be used to provide reasonable assurance for product quality

OptionsMultiple approaches possibleCE will use Spewak’s enterprise architecture planning (EAP)methodology

Used by predominance of federal agencies that have selected amethodology (ref: GAO-04-40 Enterprise Architecture)Can be viewed as a cyclical wheel


Next Step: Determine Framework

EA framework (or model) provides formal structure forrepresenting the architecture and serves as basis fornature and content of the specific products

Ensures consistent representation of informationDecreases difficulty of maintenance

Framework has been determined by DoD and AFDepartment of Defense Architectural Framework (DoDAF)Includes 3 layers of architectural views:

OperationalSystemTechnical Standards


Third Step: Define ToolsetAutomated EA tool serves as the repository of architectureartifacts, which are work products that are produced and used tocapture and convey architectural informationWho’s using what?

Predominance of federal agencies: System Architect, Microsoft OfficeOSD I&E: Metis (a visual modeling tool)AF-CIO: Metis and System ArchitectAF/IL: ARIS (but has requested sub-domains use System Architect)

Tools of ILE Choice? System Architect and DOORSSystem Architect is configure to build DoDAF productsDOORS captures business requirementsSupplemented with Microsoft Office files

Garrison GeoBase will use System Architect to interface withlarger ILE requirements

Field submittals expected to be in common Microsoft Office formatsuch as Word, Excel, Access, Visio, and Project


Conceptual Approach toEnterprise Architecture

1. Define Vision, Scope, Objectives

2. Map BusinessProcesses for To-Be

Architecture

3. Document HighLevel As-Is

Architecture

4. Analyze Gaps and Opportunities

6. Implement

5. Build TransitionPlan

ContinuouslyReview

and Update

START HERE!


Define Scope, Vision,and Objectives

Carefully define the scope of the specific enterprisearchitecture

Include all areas that need to share data, internal andexternalRealistically bound the extents of your architectureGarrsion GeoBase architecture will take a tieredapproach

Installation/DRUMAJCOM/FOAAF/ILEI

Strategic vision should look about 10 years aheadObjectives should identify what is to be accomplished,with focus on business benefits


Tiered ArchitecturesDifferent organizational levels will have different levels of specificdetail in their Enterprise Architectures

Installation architectures represent finest detailDay to day operations and processesWidest variety of specific requirements

MAJCOM/FOA will represent next level of abstraction, but stillspecific to individual mission requirementsGarrison GeoBase EA will be most general to encompass allgeospatial processes, technologies, data, organizations, etc.

INSTALLATION/DRU MAJCOM/FOA AF/ILEI, etc.

SPECIFIC TECHNICAL DETAIL ABSTRACTED VIEWS


Scoping the EnterpriseArchitecture

Federal EA

DoD EA

USA EAUSN EA

USAF EAWarfighter Mission Area

Infrastructure Environment

Operational Support Mission Area

Financial MgmtDomain Health Services

Domain

AcquisitionDomain Personnel

Domain

IL Domain

CESVS

COMM

LOG(Lead)


Perform Garrison CE Processes

Perform Real Property Activities

Perform Military Family Housing

Activities

Perform Explosive Ordnance Activities

Perform Furnishings

Management Activities

Perform Fire Department Activities

Perform Project Management

Activities

Perform Readiness Activities

Perform Operations Activities

Perform Environmental

Activities

Perform Personnel and Training

Related Activities

Perform Administration

Activities

Perform Expeditionary (Forward Ops)CE Processes

Perform COCOM CE Processes

Perform MAJCOM CE Processes

Perform HAF CE Processes

Perform FOA Processes

Perform AF I&L Processes

Perform DoD I&E Processes

Perform Capability Activities

(Protect: Deny and Respond)


(Protect: Recover)


(Prepare & Sustain)


(Intelligence)


(Command & Control)

MAJCOM Supportfor AEF

Scope of CEEA

Red lines identifysupporting rolesBlue line identifiesCEEA scopeActivities may notbe completelyidentified

Expeditionaryactivities arebased onMCL

Connection with AFI&L and DoD I&Ereinforces need toforward data to thelarger enterprises

Garrison GeoBase EA


Vision

Civil Engineer Enterprise Architecture (CEEA) visionbegins with the Air Force Civil Engineer Mission

Provide, operate, and maintain installations,infrastructure, and facilities necessary to create andsustain responsive, persistent, and effective combatoperations

Garrison GeoBase EA vision is “one installation…onemap”

A sub-architecture to the CEEA, but still part of the largerCE visionSupports CE activities in a cross-cutting fashion throughfocus on installation mapping and visualizationcapabilities


CEEA Objectives

Objectives begin with the AF/CE Strategic PlanRight Expeditionary EngineeringRight Installation Size and PlaceRight Installation, Environment, and Base Services QualityRight Installation Safety and SecurityRight Installation ResourcesRight Tools and Metrics

Determine if these objectives hold true for the 10-year vision


Garrison GeoBase EAObjectives

Support basing mission safety, efficiency and effectivenessthrough improved geospatial information resourcesEnsure long-term adoption and tight integration of geospatialcapabilities into the AF enterpriseEffectively manage geospatial information resources and relatedinformation technology investmentsUse strategic planning to:

Secure fiscal accountabilityReduce investment riskGuide and monitor long-term geospatial resource development

Implement standardized geospatial data architectures andquality assurance proceduresAssure protection of geospatial information resources


Map “To Be”Business Processes

Tie to mission requirementsSeek guidance from DoD and AF resources, such as

Directives, Architectures, PoliciesAF/CIO, AF/ILEI, GCSS-AF Outreach Team

Conduct business process engineering sessions tomap future processes in sufficient detail to:

Make investment decisionsSatisfy the scope, vision, and objectivesDefine methods to measure success

Consult subject matter experts, particularly for missiondata set developmentDevelop appropriate DoDAF products


Document As-IsArchitecture

Review and map existing processesDevelop appropriate DoDAF productsDocument “as is” so as to comparable to the “to be”state

Conduct business process engineering sessions tomap future processes in sufficient detail to:

Make investment decisionsSatisfy the scope, vision, and objectivesDefine methods to measure success


Analyze Gaps andOpportunities

Compare existing and future processesDefine requirementsIdentify all existing functional capabilities related toperceived gaps across the enterprise (may be in adifferent organization or functional area)GeoBase Capabilities Registry designed to help at thisstage

Perform gap analysisIdentify opportunities to enhance basic capabilities


Build Transition Plan

Document plan ahead in the transition road mapHow will you get from where you are to where you wantto be?May include a third transitional phase between the “asis” and “to be” statesIdentify milestones and metricsIdentify funding streams


Implement TransitionPlan

Review steps ahead with:Enterprise Architect(s)Portfolio ManagersNetwork AdministratorsInternal hierarchy (as appropriate):

Installation/DRUMAJCOM/Related Centers of ExcellenceAF/ILEIIM&V CouncilAF/ILEILDAC/EAICAF/CIO


Start the Next Round…



Architecture


Architecture


6. Implement


ContinuouslyReview

and Update


Portfolio Management andEnterprise Architecture

•Policy and Process•Legislation•Based on DoD/AF Strat Plans•ILE Operational Goals•Ties to Master Capabilities List

•Policy, Process, Control•Existing IT Systems

•Sustainment•Enhancement

•Concepts for New Systems

•Day-to-Day Operations•Existing IT Systems

•Sustainment•Enhancement

•Development of New Systems

ValueProposition

ResourceAllocation

InvestmentAnalysis &Selection

PortfolioManagement (PfM)

Priorities

InvestmentsInvestment

Control

InvestmentEvaluation

StrategicPlanning(i.e., EA)

ProgramManagement


What’s Happening With PfM?

New Policy MemoReasserts 6 Aug 03 ILE-2 memo regarding PfMDelineates new roles and responsibilities for AF/ILE-I andAFCESA/CEOI (related to EA and PfM)Directs MAJCOMs and FOAs to identify portfolio manager assingle point of contactIdentifies upcoming data call for system information

Now anticipated for late JulyOSD I&E Domain and AF I&L Domain are both formulating datarequirements; will try to use their requirements in developing callBroadens scope of what systems should be identified (e.g., administrativesystems at MAJCOMs/FOAs/HAF, energy control management systems)

New AF/ILE Portfolio Manager


What’s Happening With PfM?(cont.)

New Processes from OSD I&E and AF I&L DomainsHave specifically held back in defining governance processesto meet OSD and AF domain requirementsOSD domain will likely take lead

IL Registry no longer used!Data migrated to new system

ILE portfolio includes 55 systemsILE has own registry to “get arms around” capabilities

Reports to AF/IL, AF CIPT (Operational Support EA), OSD I&ENot ALL systems must be reported to these organizations

OSD(C) certification process and worksheet being developed forsystems requiring >$1M fund expendituresPfM is adding Certification and Accreditation as a professional“expertise”


Roles/Responsibilities

AF/ILE-IFocus shifting from GeoBase only to CE informationresource managementResponsible for strategic perspective and policy

Enterprise Architecture and Portfolio Management consideredstrategic activities

AFCESA/CEOIFocus shifting from strategic and tactical informationresource management to program management


Understand Governance

What is meant by governance as it pertains to EA andPfM?

It is the set of processes and organizations by which wemake investment (i.e., information technology) decisions

AF Civil Engineer is subject to the governance ofothers; must address internal governance to conformand work with those


Existing Governance Structure

Automation Steering GroupILE-2 Chair

Meets every 3 months

Configuration Control BoardAFCESA/CEOI ChairMeets every 3 months

9 ACESIntegrated Process Teams

Expeditionary Site Mapping

Panel

GarrisonSite Mapping

Panel

EESOH CCB

Meets every 3 months

Installation Mapping & Visualization CouncilMeets every 3 months

Focused WorkingGroups

SAF/IEE EAIC

CE InvestmentsOnly

CE InvestmentsOnly

ACES Environmental IPT Inputs

GeoBase IPT Inputs

AF/IL Panel

ILDAC


Changing Governance Structure

Must demonstrate through organization how both enterprisearchitecture and portfolio management will be governed within CE

Need to implement for EAEnterprise Architecture Executive Steering Committee

Need to implement for PfMCapital Investment CouncilTechnical Review CommitteeConcept / Business Case Functional Review Boards

New structure would require new or modified processes, newform(s), and different mindset

Goal is to have new structure and processes in place by Jan 05IM&V Council Charter must be approved by 15 Oct 04


Steps Ahead

Understand Enterprise ArchitectureSupport Civil Engineer EA (CEEA) developmentSupport Garrison GeoBase Enterprise Architecture developmentRecognize and understand DoDAF architecture products

Understand Portfolio ManagementEstablish an active working relationship with your organization’s PfMProvide input when data call is madeRequest clarification and assistance when requests are unclear orissues appear

Understand GovernanceUnderstand how to fit into IL’s, AF’s, and OSD I&E’s governancestructureSupport changes to ILE’s governance structure to accommodatestrategic nature of enterprise architecture and portfolio management(such as 04 AUG Memo signed by Maj Gen Fox, the AF Civil Engineer)


Top Management Involvement

Every successful EA has cited Top Management awareness, recognition,and acceptance as the single most important factor in its success!

Top Management refers to executives in the business area beingplanned AND in information systemsAwareness means the executives know about the EA process, itsbenefits, and its productsExecutives must recognize the reason for developing architecturesand their importance to the organizationAcceptance means that management understands the rationale for EAand accepts their role and responsibility to the EA process forsuccessfully achieving its objectives

SOLUTION: Institute an education process to bring management onboard.

GAO-04-40: “Agencies continue to face the same management challenges that we identified 2 yrsago – that is, obtaining top management support and commitment, overcoming parochialism,

and having the requisite resources (financial and human capital) to get the job done.”


Commitment to EA

Commitment means that sufficient personnel, funds, time, andmaterial are allocated to do EA properly and in a timely mannerWithout commitment, EA cannot succeed.Part of the FY05 GeoBase program management reviews will beto put forth a plan to complete the requisite DoDAF architectureproducts for each MAJCOM/FOA/DRU. In that plan:

Identify timeline to complete products1st drafts due in March 052nd drafts June 05Will be incorporated into CEEA due Sep 05

Realistically evaluate existing capabilities and potentialshortfalls in personnel, expertise, or other resources

**More discussion to follow in session after the break**


Enterprise Architecture

Department of Defense ArchitectureFramework

(DoDAF)Version 1.0, August 2003


Definitions

ArchitectureArchitecture“….the structure of components, their relationships, and the principles

and guidelines governing their design and evolution over time.”--C4ISR Architecture Framework, Version 2.0

(evolved into DoDAF, Version 1.0)FrameworkFramework“…common, pragmatic guidelines for describing an architecture to

enable comparisons and integration.”“…architectural discipline for examining processes and system

alternatives in context with mission operations and informationrequirements.”

--Kathie Sowell, FEAC InstituteDoDAFDoDAFThe architecture framework that the Department of Defense has chosen

to use


DoDAF Views

The DoDAF uses three different data perspectives (views) that“logically combine to describe an architecture.”

Operational View (OV): describes required tasks, activities,operational elements, and information exchanges

What has to be done?Who does it?Who needs to get the information?

Systems View (SV): describes systems andinterconnections

What is the material solution by which operational “nodes” interactwith each other and with the outside world?

Technical Standards View (TV): describe technical systemrules that govern the arrangement, interaction, andinterdependence of system elements

What technical standards must be met (i.e. J2EE or SDSFIE)?What performance criteria must be met (i.e. minimum response time)?


DoDAF Architectural ViewsNeeded Information

Activity RelationshipsInformation Relationships

Node LocationsBusiness Processes

Information Exchanges

Activities Source of Information

Standards Exchange CriteriaJTA Compliance

Technical Implementation

GIG Standards

OPERATIONALVIEW

System InterfacesSystem Laydown

Links to NodesLinks to Activities

System ComponentsInformation Exchanges

SYSTEMSVIEW

TECHNICALVIEW


Links Between Views

Operational View(Identifies Players,

Relationshipsand Information Needs)

Systems View(Relates Capabilities& Characteristics to

Operational Requirements)

Technical View(Prescribes Standards

and Conventions)

Syste

ms a

ssoc

iation

s to

node

s,

activ

ities,

need

lines

, and

rqm

ts

Proc

essin

g an

d int

er-n

odal

levels

of in

form

ation

exc

hang

e rq

mts

Technical criteria governing interopimplementation of selected system

Specific capabilities to satisfy info-exchange levels & other ops rqmts

Base technology supportability

and new capabilities

Processing and levels of info-

exchange requirements


Associated Products

26 products acrossviewsColor coding

AV – BlackOV – BlueSV – BrownTV – Red

Products are highlyintegratedCore products are thosemost commonly used,and, until recently,required - still highlyrecommended

View Abbrev Product Core?All Views (Context) AV-1 Overview and Summary Information YesAll Views (Terms) AV-2 Integrated Dictionary Yes

Operational OV-1 High-Level Operational Concept Description YesOperational OV-2 Operational Node Connectivity Description YesOperational OV-3 Operational Information Exchange Matrix YesOperational OV-4 Organizational Relationships ChartOperational OV-5 Activity Model YesOperational OV-6a Operational Rules ModelOperational OV-6b Operational State Transition DescriptionOperational OV-6c Operational Event/Trace DescriptionOperational OV-7 Logical Data Model

Systems SV-1 System Interface Description YesSystems SV-2 Systems Communications DescriptionSystems SV-3 Systems - Systems MatrixSystems SV-4 Systems Functionality DescriptionSystems SV-5 Operational Activity to System Function Traceability MatrixSystems SV-6 System Data Exchange MatrixSystems SV-7 System Performance Parameters MatrixSystems SV-8 System Evolution DescriptionSystems SV-9 System Technology ForecastSystems SV-10a Systems Rules ModelSystems SV-10b Systems State Transition DescriptionSystems SV-10c System Event/Trace DescriptionSystems SV-11 Physical Schema

Technical TV-1 Technical Standards Profile YesTechnical TV-2 Standards Technology Forecast


DoDAF Views

The DoDAF also describes a fourth view that is related to all ofthe other three (OV, SV, TV):All Views (AV): describes pertinent to the architecture but doesnot describe a distinct view

Overarching perspective, such as the scope of thearchitectureCommon terminology used throughout the architectureUsually in document format

**Although enterprise architecture is aimed at managing InformationTechnology, the concepts apply to any process you might want tomap.

The next example looks at architecting a manufacturingprocess that manages physical goods rather thanelectronic information


DoDAF Views –The Margarita Example

You want to architect making and serving the perfect margarita…What considerations would go into each of the views?

All View (scope and definitions)Operational View (activities)System View (material solutions to support activities)Technical View (standards and rules)

What would change if:You needed to serve a non-alcoholic version?You decided to patent your recipe?You wanted to sell your margaritas?You want to enable your drinks to be made around theworld?You wanted to have them made and sold worldwide?


Break

Something to think about on the break:Enterprise Architecture can apply to any process, from washing yourcar to colonizing Mars. It can certainly apply to mapping out how youwould approach creating the architecture product plan that will berequired during the FY05 GeoBase PMRs. Ponder the following, andwe’ll see if we can incorporate these ideas as we discuss the individualrequired products…

What is the scope of this assignment?What do these terms actually mean?Who will be involved?What information will I need?What standards do I need to follow?What activities will need to be done?What technology will I need to create and deliver the products?


Conceptual Approach toEnterprise Architecture



Architecture


Architecture


6. Implement


ContinuouslyReview

and Update

START HERE!


The Six Step Process in DoDAF

The DoDAF provides some high-level guidance on how to proceed.Determine the intended use of the architectureDetermine the intended use of the architecture

PurposeCritical IssuesTarget Objectives

Determine the architecture scopeDetermine the architecture scopeGeographicTimephase(s)Functional BoundsTechnology Constraints

Determine the characteristics to be capturedDetermine the characteristics to be capturedDepth of DetailPerformance Measures


The Six Step Process in DoDAF

Determine the views and products to be builtDetermine the views and products to be builtNot all architectures require all productsNone are strictly required at this point, but seven are highlyrecommendedRequesting seven out of the eight core products for GarrisonGeoBase Enterprise Architecture

Build the requisite productsBuild the requisite productsFor Garrison GeoBase, submit using Microsoft Office softwareWill be incorporated into larger CE Enterprise Architecture at AF/ILEIusing Popkin System ArchitectBuild additional DoDAF products if they will helpful

Use architecture for intended purposeUse architecture for intended purposeProduct investmentsBusiness process improvementIncreased interoperability


Core DoDAF Products

All Views (AV)AV-1: Overview and Summary Information (context )AV-2: Integrated Dictionary (terms)

Operational View (OV)OV-1: High Level Operational Concept DescriptionOV-2: Operational Node Connectivity DescriptionOV-3: Operational Information Exchange MatrixOV-5: Activity Model

Systems View (SV)SV-1: System Interface Description

Technical Standards View (TV)TV-1: Technical Standards Profile


Core All Views (AV)

AV-1: Overview and Summary Information (context )Definition

Executive level summaryAssumptions, constraints, limitations

PurposeServes as planning guide in early stagesProvides summary upon completion

Architecture Project IdentificationScopePurpose and viewpointContext

Tools and File Formats UsedFindings


Notional AV-1 Example


Core All Views (AV)

AV-2: Integrated DictionaryDefinition

Definition of terms used in an architecture – a glossaryIncludes taxonomies

Common terms linked to common definitionsUsed consistently throughout all architecture products

Metadata regarding architecture data types used

PurposeCentral repository for architecture’s data and metadataProvides unambiguous definitionsAllows architecture to stand alone, to be understood withminimal reference to external sources


Key AV-2 Taxonomies


Core Operational Views

OV-1: High-level Operational Concept DescriptionDefinition

Describes business process or missionHighlights main operational nodesCan represent geographic distribution of assetsDepicts interaction of architecture subject with externalentities

PurposeVisual depiction of what the architecture coversPrimarily graphic representation of mission and activities,supported by textual content where neededFocused towards high-level decision makers**Not being requested from field for Garrison GeoBase

enterprise architecture at this time**


Sample OV-1 (Tricare)


OV-1 Example – Navy



OV-2: Operational Node Connectivity DescriptionDefinition

Graphically depicts nodes where activities occur. A nodenode isan element that produces, consumes or processesinformation – generally a person, an organization, or afunctional areaShows needlines for information exchange between nodesDoes not detail physical or organizational connectivitybetween nodesIncludes internal and external nodes

PurposeTrack the need for information exchange between nodesIntegrates directly with the OV-5 Activity Model


OV-2 Template


OV-2 Example



OV-3: Operational Information Exchange MatrixDefinition

Identifies who exchanges what information with whomShows why information is necessaryDepicts how information exchange must occurOne OV-2 needline may have many individual informationexchanges on the OV-3

Information exchange: Information exchange: the act of exchanging informationbetween two nodes, including characteristics of the exchangeInformation elementInformation element: what is exchanged

PurposeExpress relationships across operational activities, nodes,and information flowFocus on key exchanges, minimal detail – don’t overdo it!


Notional OV-3



OV-5: Activity ModelDefinition

Describes operations normally conducted to achieve amission or a business goalDescribes capabilities, activities, and input/output flowbetween activitiesDepicts internal and external activities

PurposeKey product for describing capabilities and ties to missionsuccessDelineates operational node responsibilities for activities(OV-2)Pinpoints redundant or missing activitiesIntegrates tightly with information exchange matrix (OV-3)


OV-5 UML Template


Sample OV-5 (Tricare)

Military HealthSystem

Access to Care

1.0

Manage the Business

4.0

Population HealthManagement

3.0

Provision ofHealth Services

2.0

Manage Finances

4.2

Manage HumanResources

4.3

Patient FinancialManagement

4.4

Perform MedicalManagement

4.5

Review/ImproveBusiness Mgmt

4.6

SupportContracting

4.7

Deliver WorldwideLogistics

4.1


Conduct Combat Assessment OV-5 Example


Core System Views

SV-1: System Interface DescriptionDefinition

Depicts system nodes and the systems at those nodesDemonstrates how operational nodes (OV-2) are supportedby systemsCan identify cross-organizational system interfacesOne information needline may have many system interfaces

PurposeLinks systems to operations by assigning systems andsystem nodes to information exchange needlinesDocuments systems, subsystems, and hardware/softwarePhysical modes of system communication (routers,switches, etc.) are not documented here, but in the SV-2,System Communication Description


Core System Views

SV-1: System Interface Description (continued)Key InterfacesKey Interfaces have one of the following characteristics,and should be identified on the SV-1:

Spans organizational boundariesMission criticalDifficult or complex to manageCapability, interoperability, or efficiency issues

The SV-1 can be shown in different ways:Internodal Node-Edge-to-Node-EdgeInternodal System-to-SystemIntranodalIntrasystem


Notional SV-1 InternodalNode-Edge-to-Node-Edge


Notional SV-1 InternodalSystem-to-System


Notional SV-1 Intranodal


Notional SV-1 Intrasystem


SV-1 Example


Core System Views

TV-1: Technical Standards ProfileDefinition

Define systems standards rules, i.e.Data formatsCommunication protocolsApproved hardware/software

Outline constraintsTies to Joint Technical Architecture (JTA) at service level

PurposeApply standards for architecture implementation across anenterpriseIdentify technical standards utilized when evaluatinginteroperabilityGoverns hardware/software and data format choices


TV-1 Template (JTA)


Enterprise Architecture

Next Steps for Garrison GeoBaseEnterprise Architecture



Current version completed in January 03Primary focus on “as-is” and transitional statesBased on C4ISR Architecture PlanIncludes following products:

OV-1: High-leOvel Operational Concept DescriptionOV-2: Operational Node Connectivity DescriptionOV-3: Operational Information Exchange MatrixOV-4: Organizational Relationship ChartOV-7: Logical Data ModelSV-1: Systems Interface DescriptionTV-1: Technical Standards Profile

Version 1.1 expected to be completed December 04Will update existing products and add AV-1, AV-2, andOV-5



Version 2.0 will include information to be integrated into theCivil Engineer Enterprise Architecture (September 05)

Will draw from information provided by MAJCOM/FOA/DRUproductsShould be flexible and more easily maintained due to use ofautomated enterprise architecture softwareWill evaluate value of additional supplementary architectureproducts, such as the SV-11, Physical Schema, and the TV-2,Standards Technology ForecastWill incorporate policy and guidance changes since last version

Will either incorporate requirements, or serve as basis for,separate Expeditionary Site Mapping Enterprise ArchitectureWill also provide support for continued development ofinstallation mapping and visualization as an AF web service