using enterprise architecture to avoid errors and ensure success: a marine corps case study

Using Enterprise Using Enterprise Architecture to Avoid Errors Architecture to Avoid Errors

and Ensure Success: A and Ensure Success: A Marine Corps Case StudyMarine Corps Case Study

Dr. Geoffrey P MalafskyDr. Geoffrey P MalafskyPresident, TECHi2President, TECHi2

Ms. Elizabeth SedlacekMs. Elizabeth SedlacekDirector Information Systems & Director Information Systems &

InfrastructureInfrastructureMarine Corps Systems CommandMarine Corps Systems Command

2220Sep200420Sep2004 TECHi2, MCSCTECHi2, MCSC

ArchitectureArchitecture

The art & science of designing and erecting The art & science of designing and erecting buildings.buildings.A style and method of design and constructionA style and method of design and constructionOrderly arrangement of parts; structure: the Orderly arrangement of parts; structure: the architecture of the federal bureaucracy; the architecture of the federal bureaucracy; the architecture of a novel.architecture of a novel.Computer Science: The overall design or Computer Science: The overall design or structure of a computer system, including the structure of a computer system, including the hardware and the software required to run it, hardware and the software required to run it, especially the internal structure of the especially the internal structure of the microprocessor.microprocessor.


When We Think of Architecture..When We Think of Architecture..


Architecture Includes …Architecture Includes …

FormForm

MaterialsMaterials

StructureStructure

AestheticsAesthetics

Use patternsUse patterns

MaintenanceMaintenance

ConstructionConstruction

SafetySafety

An architecture is “the structure of components, their relationships, and the principles and guidelines governing their design and evolution over time.” (IEEE Std 610.12)


Architecture for ITArchitecture for IT

Network diagramsNetwork diagrams

Software modelsSoftware models

Communication protocolsCommunication protocols

Hardware connectionsHardware connections


Yes, But Also…Yes, But Also…

How, who, when, why, where, what of How, who, when, why, where, what of design, funding, decision-making, design, funding, decision-making, development, operation and maintenancedevelopment, operation and maintenanceWhy all of these “soft” issuesWhy all of these “soft” issues Lessons Learned from many years of large Lessons Learned from many years of large

scale IT programsscale IT programs Organizational issues can dominate systems Organizational issues can dominate systems

engineeringengineering Real success depends on single system Real success depends on single system

blending people, process, technologyblending people, process, technology


Architecture FrameworksArchitecture Frameworks

Federal Enterprise Architecture Federal Enterprise Architecture Framework (FEAF) Framework (FEAF) Zachman framework Zachman framework The Open Group Architecture Framework The Open Group Architecture Framework (TOGAF) (TOGAF) Object Management Group (OMG) Model Object Management Group (OMG) Model Driven Architecture (MDA) Driven Architecture (MDA) Department of Defense Architecture Department of Defense Architecture Framework (DODAF)Framework (DODAF)


Zachman FrameworkZachman Framework


DODAFDODAF

Defines 3 primary viewsDefines 3 primary views There is no single view of an architecture (business process, There is no single view of an architecture (business process,

network, hardware, data management, etc.) that describes all network, hardware, data management, etc.) that describes all critical components, data, and userscritical components, data, and users

Use standardized products, terms, and definitionsUse standardized products, terms, and definitions

Operational View: tasks and activities of concern and the Operational View: tasks and activities of concern and the information exchanges requiredinformation exchanges requiredTechnical View: profile of a minimal set of time-phased Technical View: profile of a minimal set of time-phased standards and rules governing the implementation, standards and rules governing the implementation, arrangement, interaction, and interdependence of arrangement, interaction, and interdependence of system elements.system elements.System View: systems of concern and the connections System View: systems of concern and the connections among those systems in context with the operational among those systems in context with the operational architecture view.architecture view.


DODAF: Example Key ProductsDODAF: Example Key Products

ALL ViewsALL Views AV-1: Overview and Summary InformationAV-1: Overview and Summary Information AV-2: Integrated DictionaryAV-2: Integrated Dictionary

Operation ViewsOperation Views OV-1: High-level Operational Concept GraphicOV-1: High-level Operational Concept Graphic OV-2: Operational Node Connectivity DescriptionOV-2: Operational Node Connectivity Description OV-3: Operational Information Exchange MatrixOV-3: Operational Information Exchange Matrix

System ViewSystem View SV-1: System Interface DescriptionSV-1: System Interface Description

Technical ViewTechnical View TV-1: Technical Architecture ProfileTV-1: Technical Architecture Profile


System Design & Development: System Design & Development: Known HurdlesKnown Hurdles

Acquisition is structured to purchase tools Acquisition is structured to purchase tools based on lists of functionsbased on lists of functionsUsers need support of business processesUsers need support of business processesNo single organizational group makes all No single organizational group makes all necessary decisions and controls all types necessary decisions and controls all types of fundsof fundsSuccess or failure of the system and Success or failure of the system and program hinges on the intangibles of program hinges on the intangibles of usefulness, usability, relevanceusefulness, usability, relevance


Errors to AvoidErrors to Avoid

““Wrong” group doing:Wrong” group doing: RequirementsRequirements Technical specificationsTechnical specifications Program managementProgram management Systems engineeringSystems engineering

Debating the above issues across organizational roles Debating the above issues across organizational roles and responsibilitiesand responsibilitiesRelying on vendor or analyst literature for technical Relying on vendor or analyst literature for technical designdesignFocusing most effort on networks, hardware, software Focusing most effort on networks, hardware, software instead of business process, operational instead of business process, operational capabilitiescapabilities


Success Factors to PromoteSuccess Factors to Promote

Clear roles and responsibilitiesClear roles and responsibilities

Maximize use of industry and government Maximize use of industry and government standardsstandards

Business focused Measures of Business focused Measures of EffectivenessEffectiveness

Constantly restate role of technology as Constantly restate role of technology as supporting not driving design of supporting not driving design of capabilitiescapabilities


How does EA Help?How does EA Help?

Keeps people aware of need for synergy Keeps people aware of need for synergy among people-process-technology among people-process-technology Highlights operational capabilities as Highlights operational capabilities as source of design and development not by-source of design and development not by-productsproductsForces explicit definition of information Forces explicit definition of information needs, by whom, when, ….needs, by whom, when, ….Requires explicit statement of Requires explicit statement of organizational roles and responsibilitiesorganizational roles and responsibilities


Example: Who Defines Example: Who Defines RequirementsRequirements

Operational Views show the goals and Operational Views show the goals and major information requirementsmajor information requirementsSystem Views show the layout and System Views show the layout and connections of network, hardware, connections of network, hardware, softwaresoftwareWhich view states requirements?Which view states requirements?Who defines the requirements?Who defines the requirements?Answer: Different roles for different Answer: Different roles for different requirementsrequirements


DODAF ViewsDODAF ViewsRequirements group, e.g. CIOSystems

engineering group: e.g.

MCSC

Standards group, e.g.

Acquisition, policy,

industry


DODAF OVsDODAF OVsFrom Software Productivity

Consortium


DODAF SVsDODAF SVsFrom Software Productivity

Consortium


As an example, a portal was designed for the Commandant of the Marine Corps (CMC). As this OV-1 shows, the intent of the portal is not to deploy just a portal but to provide the

Marine Corps senior leadership with one secure tool bringing

together applications, databases, and

metadata to provide key information and

data.


The OV-2 for the Commandant’s portal

shows the major stakeholders and how they are connected in terms of information

needs. A separate product (i.e. SV) will

show how the system components are

connected for each stakeholder.


Need Line ID

Info Exch ID

Content Scope Media Type

Acc Producer

Cons Security Class

Time Crit Freq IA

A (ACMC-CMC)

A-1 CMC Issues

Maintains Organizational awareness at same level as CMC in role as Assistant

Data, Text, Graphics, Audio, Video

High ACMC CMC U, SBU minutes-weeks

High Event Driven

High

A-2 Congressional Issues

Keeps CMC informed of Congressional activities that affect USMC


High ACMC CMC U, SBU hours-days

High Event Driven

High

A-3 OSD Issues

Keeps CMC informed of OSD issues that affect USMC


High ACMC CMC U, SBU hours-days

High Event Driven

High

CMC Portal OV-3: Information Exchange Requirement


The SV-1 for the Commandant’s portal

shows the major system components

and how they are connected in terms of

hardware needs.

Ms. Elizabeth SedlacekMs. Elizabeth Sedlacek

Director Information Systems and Director Information Systems and InfrastructureInfrastructure

Marine Corps Systems CommandMarine Corps Systems Command

United States Marine Corps Enterprise Architecture


What is an Enterprise What is an Enterprise Architecture?Architecture?


What is an Enterprise Architecture?What is an Enterprise Architecture?

Takes the…Baseline Architecture

To develop…a Target Architecture

Utilizes… an Integration Plan

Enterprise Architecture –

•Is a discipline for assessing and recommending candidate Information Technology solutions in an integrated context with business and mission operations

Translates to –

•Significant increase in the Warfighting Capability


How do we use the Enterprise Architecture? How do we use the Enterprise Architecture? - Operational Requirements- Operational Requirements

Provides the basis from which we define operational capabilities

Describes the linkages among systems, which turn separate systems into Warfighting Capabilities.

EA is the disciplined approach to achieve a Network Centric Warfare Capability


How do we use the Enterprise How do we use the Enterprise Architecture? – Systems EngineeringArchitecture? – Systems Engineering

It provides a tool for systems engineers to communicate so that the separate system designs become integrated to produce required Operational Capabilities.


How do we use the Enterprise How do we use the Enterprise Architecture? – Modeling and TestingArchitecture? – Modeling and Testing

Architecture Cube

Agency-Level View (OV-2)

Roles & Chores (Composite View)

It provides a tool for test engineers to develop scripts which are operationally relevant and doctrinally sound that goes beyond architecture modeling.


How do we use the Enterprise How do we use the Enterprise Architecture? – Analyses Architecture? – Analyses

Map Roles & Chores to Systems

Assess Consistency of Doctrine, Organization, Training, and Materiel

Map Chores toSystem-Operator Steps

It provides a common framework to evaluate, analyze and report linkages and sensitivities among the DOTMLPF factors.


Roles and Responsibilities MOARoles and Responsibilities MOA

HQMC, C4 CIOHQMC, C4 CIO- Define and issue IT standards and policies- Participate in the collaborative environment- Develop the Roadmap for enhancing the EITA- Address architectures in AIS/IT requirements

MCCDCMCCDC- Develop and maintain the operational architectures and concepts- Participate in the collaborative environment- Address architectures in AIS/IT requirements

MCSCMCSC- Develop and maintain systems and technical architectures- Create a collaborative environment to develop and maintain the EITA- Ensure all IT programs are compliant with the EITA- Lead the resolution of conflicts between operational, systems, and technical views


Marine Corps Enterprise IT Marine Corps Enterprise IT Services (MCEITS)Services (MCEITS)

A look at the Marine Corps EA in A look at the Marine Corps EA in action……..action……..


What is MCEITSWhat is MCEITSMCEITS is envisioned to become the Marine Corps solution MCEITS is envisioned to become the Marine Corps solution for:for:

Infrastructure (brick and mortar)Infrastructure (brick and mortar)IT Centers – Physical location of hardware,IT Centers – Physical location of hardware,

software and computer applicationssoftware and computer applications

ServicesServicesData Management – Access to dataData Management – Access to data

needed to make decisionsneeded to make decisions

Application Management – 24/7 availabilityApplication Management – 24/7 availability

of computer applicationsof computer applications

GovernanceGovernancePolicy and Engineering Management – Standards and Systems EngineeringPolicy and Engineering Management – Standards and Systems Engineering

Acquisition SupportAcquisition Support

Infrastructure

Services

Governance


MCEITS and NCESMCEITS and NCESInfrastructureInfrastructure

The The IT CentersIT Centers will comprise a disciplined and will comprise a disciplined and standardized hardware, software, and firmware standardized hardware, software, and firmware baseline which will furnish the MC with proven, baseline which will furnish the MC with proven, reliable, resilient, and survivable production, reliable, resilient, and survivable production, testing, and development environments.testing, and development environments.

ServicesServices This baseline will host multiple database systems This baseline will host multiple database systems

and application in an N-tier architecture and will and application in an N-tier architecture and will also provide the requisite administrative and also provide the requisite administrative and management management ServicesServices to fully support the hosted to fully support the hosted systems.systems.

GovernanceGovernance The capabilities of the IT Centers and Services The capabilities of the IT Centers and Services

will be harnessed and augmented by a consistent will be harnessed and augmented by a consistent and disciplined and disciplined GovernanceGovernance process. process.

Beginning of MarineCorpsNet-CentricEnterpriseServicesImplementation


Overall BenefitsOverall BenefitsHarmonizes ITS/NSS Assets - Cost, readiness, interoperability Harmonizes ITS/NSS Assets - Cost, readiness, interoperability

Enables Marine Corps to respond to DoD IT business process Enables Marine Corps to respond to DoD IT business process improvement and transformation initiativesimprovement and transformation initiatives

Facilitates Marine Corps participation in DoD Net-Centric programsFacilitates Marine Corps participation in DoD Net-Centric programs

Creates conditions for enterprise IT demands (scalability)Creates conditions for enterprise IT demands (scalability)

Augments current initiatives (NMCI, COOP, PORs)Augments current initiatives (NMCI, COOP, PORs)

Provides common user / application servicesProvides common user / application services

Forcing function for creating system interoperability, integration and Forcing function for creating system interoperability, integration and trainingtraining


Forcing function for creating system Forcing function for creating system interoperability, integration and traininginteroperability, integration and training

System identification and interfacesSystem identification and interfaces

NCES/NII/OSD requirements NCES/NII/OSD requirements

Organizational processes Organizational processes

Program alignment and interoperabilityProgram alignment and interoperability

So what about the Enterprise So what about the Enterprise Architecture?Architecture?

Summary & QuestionsSummary & Questions

Brief is available at:Brief is available at:www.techi2.comwww.techi2.com

www.e-gov.com/events/2004/ea2/downloads/www.e-gov.com/events/2004/ea2/downloads/

using enterprise architecture to avoid errors and ensure success: a marine corps case study

Documents