howard cohen hampton roads incose chapter meeting 2010

Multiple technical configurations One warfighter

Howard Cohen Joint Architectures & Capability Engineering [email protected]

Incose Dinner 2010

Joint Architecture Federation “SOA In Action - for Joint Warfighter Capabilities”

Enterprise consisting of people, process, Methods and Tools including applications providing a standard framework and repeatable process enabling the generation of reusable architecture depicting operational, system and technical perspectives.

Joint Forces J89 System Engineering and Architectures.

People

• Project Leadership

• Stakeholders• Facilitator• Engineer• Architect

Process

• Consistent Patterns

• Capture as-is• Define

“Desired State”

Methods

• A piece of code associated with a class or object to perform a task

• Service Oriented Architectures

To

ols

• Virtualization • Operating

System• Application

Servers • Integration • Tuning

System Integration

J89 Created a Virtual Enterprise.

System VirtualizationThe term virtualization broadly describes the separation of a resource or request for a service from the underlying physical delivery of that service.

Deploy

ProductionVM

ProductionVM

ProductionVM

ProductionVM

DEVVM

QAVM

TestDevelop

Development Quality Assurance

System Quality

and Assurance

System Testing

App Server

App Server

Citrix Server

App Server

Database Server

1

Database Server

App Server

App Server

Citrix Server

App Server

Many to One

ServerConsolidation

ESX

TeamCenter Systems Engineering

Apache Tomcat 6.0.18Weblogic 9.2

32 Bit Windows 2003 R2


Versant7.0.1.4 Patch11

Sun Solaris 9

System Layers

TeamCenter System Engineering

Apache Tomcat 6.0.18Weblogic 9.2



Versant7.0.1.4 Patch11

Sun Solaris 9

64 Bit

Windows

2003 R2

Test

Tune

Build

Apache Tomcat 6.0.18

Weblogic 9.2 Sun Solaris 9

Versant

7.0.1.4 Patch11

32 Bit

Windows

2003 R2System Tuning

System Deployment

Methodology

Service Oriented Warfighter


• Reduce Rework and Eliminate/Reduce Duplication of Effort

• Share Data Between Various Organizations, Tools and Environments – Encourage a More Effective Collaboration

Environment – Create More Efficient Architecture Development and

Analysis Processes in Support of DoD Initiatives – Improved Speed of Development

**Ar

chit

ectu

re C

onte

xt

Discover

Authoritative data

Visualize

ConnectReuse

**Ar

chit

ectu

re C

onte

xt Service Oriented Warfighter

13

Operational Activities

Systems Functions

Joint StaffJ7 Mapping

Architectures

Analysis

Accreditations

Concepts/Plans

Assessments

Policy

Standards

Policy

Standards

Policy

Standards

Policy

Standards

Policy

Standards

Policy

Standards

Operational

Programmatic

Technical

Documentation

Policy

Standards

Joint Integration& Interoperability

Recommendations via Detailed

DOTMLPF Analysis

Policy

Standards

Joint Capability Areas (JCAs)

Other CPMs

C2 Portfolio* - Programs of Record - Systems - Sub-systems - New Capabilities

JCAs- to- PECs

PA&EMapping

CPM Areas

Capability Mapping Baseline“Periodic Table” for Operational DOTMLPF-P Analysis

NCES/NECCUSAF

USAUSMC

USN

Joint CommonSystem Functions

List (JCSFL)

JTF OperationalActivities / Tasks / Sub-tasks

Tier I

UJTLSN X.XST X.XXOP X.X.XTA X.X.X.X

Joint Warfighter Billets

Authoritative Sources:

AUTLs, MCTL, NTTL, AFTL

Platforms/Weapons

Applications/Services

ADS & Data Models

Networks/Comms

Joint Tasks

Service Tasks

OpNodes

Operational Nodes & Billets

JCAs

JCAs

14

Joint Capability Areas(JCA)

Additional Task Details (ATD)

UNTL

AUTL

AFUTL

MCTL

Universal Joint Task List(UJTL)

SystemsApplications

Services

Joint Common System Function

List(JCSFL)

Joint Conditions

Navy System Functions

Army System Functions

Air Force System Functions

Marine Corps System Functions

Joint Task Force Activities

DoD IT Standards Registry (DISR)

Authoritative Data Source (ADS)

Registry

Net Ready KPP’s(NR-KPP)

Connection Via Service Tasks

Program Elements (PE)

Budget Line Item Numbers

(BL)

Connection Via JTF Activity

Name

Connection Via System,

Application or Service Name

Connection Via System Function

Name

Connection Via Program

Information

Architecture Federation to the Joint Environment (JACAE)

LegendRed Border = Logical Federation Connection Points

Dotted Line = Future Relationships/ConnectionsSolid Line = Existing Relationship Mappings

Shaded Background/Orange Border = Planned Partnerships

JFLCC HQ

JSOTF/JPOTF

JFMCC/MHQ-MOC

JFACC/JAOC

Connection Via Node

(Performer) Name

Nodesi.e. PlatformsOrganizationsWarfightersConnection Via

JTF Architecture

C2 Registry

C2-Pedia

JTF-HQ

Joint Mission Threads

Connection Via Joint Mission

Threads

15

Sample Web Service Endpoint Connections

Service Providers

Web Service Definition Language (WSDL) - Web Service Policies and Standards (DoDAF MetaModel et al.)

Architecture Repositories

DoDAF Products Performers Resources Capabilities Universal Joint and Service

Tasks System Functions Activities Systems Applications Services

Fit-For-Purpose Architecture Products Mission Threads Program Elements

External Information Repositories

Authoritative Sources Of Information

Program Information System Information Standards

Service Consumers

Architecture Repositories (Phase 2 and 3) External Information Repositories (Phase 2 and 3)

.xsl

t

.xsl

t

.xsl

t

.xsl

t

Joint Architecture Federation Concept (August 2009)

Publish Services

Subscribe to Services

JACAE CADIE MCAE SADIE OthersADS

Registry DISR Others

JACAE CADIE MCAE

SADIE Others

DoDAF Products

.xsd

Joint Mission Threads

.xsd

JTF Architectures

.xsd

Federated Architecture

Threads.xsd

Program Information

.xsd

Operational Activities

.xsd

Nodes (Performers)

.xsd

Joint/Service Tasks.xsd

System Functions

.xsd

Systems, Applications or Services

.xsd

ADS Registry DARS

E-ISP Others Standardized Portal Interface

(Phase 1)


Any Questions?

The warfigher is always on our mind

JACAE Services

BACKUP

Policy & Guidance • DoD Directive 8000.1, “Management of DoD Info Resources”, November 21,

2003• DoD Manual 8020.1-M, “Functional Improvement Process”, August 1992• DoD Directive 8100.1, “GIG Overarching Policy”, September 19, 2002• DoD Directive 8100.2, “Wireless Technologies and the GIG”, April 14, 2004• DoDI 8110.1 “Multinational Information Sharing Networks Implementation”.• DoD Directive 8115.1, "I.T. Portfolio Management", October 10, 2005• DoD Manual 8320.1-M, “Data Administration Procedures”, March 1994.• DoD Manual 8320.1-M-1, “Standard Data Element Development”, May 1992.• DoD Directive 8320.2, “Data Sharing in DoD”, December 2, 2004.• DoD Directive 8320.03, “Identification Standards”, March 23, 2007.• DoD Directive 8500.1, “Information Assurance”, October 24, 2004.• DoD Net-Centric Data Management Strategy: Metadata Registration, April 3,

2003• DoD Net Centric Strategy, May 9, 2003• Department of Defense Discovery Metadata Specifications• DEPSECDEF Memorandum on “Information Technology Portfolio

Management”,• March 22, 2004• Director of Central Intelligence, “Intelligence Information Sharing”, June 9, 2004

• DoD Directive 8320.02, Data Sharing in a Net-Centric Department of Defense, April 23, 2007

• Department of Defense Chief Information Officer, Department of Defense Net-Centric Service Strategy, May 4, 2007

• Global Information Grid (GIG) Architecture Federation Strategy, 01 August 2007

Policy Standards Guidance

Architecture Federation Guidance

• Business Transformation Agency (BTA), BMA – Federation Strategy and Roadmap, 26 September 2006

• US Army Regulation (AR) – 71, Force Development Architecture (Draft) 10 September 2008.

• DoD Instruction 8210.aa (Draft), Architecting the DoD Enterprise, 22 September 2008

• DoD Manual 8210.11 (Draft), DoD Architecture Federation, 22 September 2008

• DoD Metadata Registry and Clearinghouse Version 7.0 Federation Specification

• DoD Architecture Framework (DoDAF) 2.0

Policy & Guidance

• DoD CIO Executive Board (CIO EB)• Military Communications and Electronics Board (MCEB)• GIG E2E Systems Engineering Advisory Board (SSEB)• IT Standards Oversight Panel (ISOP)• Information Assurance Senior Leadership Group (IASLG)• Interoperability Senior Review Panel (ISRP)• GIG Waiver Board and Panel• DISN Flag Panel• DISN Designated Approving Authority (DAA)• DISN Security Accreditation Working Group (DSAWG)• DIAP (Defense-Wide Information Assurance Program.)• Joint Battle Management Board (JBMC2 BoD)• Defense Business Systems Management Committee (DBSMC)• CCB (Configuration Control Board)

• Architecture information, if properly developed, informs decision-making and assists in visualizing complex warfighter capability relationships and business processes

• Some standards and guidance for architecture development exist, however:– Data is “stove-piped” in various proprietary tools and repositories– Information sharing is difficult

• Use of proprietary architecture information has hampered the DoD’s capability to re-use and integrate previously developed architectures

Architecture Federation Project Background

24

JACAE Objectives

• Assist decision makers across the DoD by providing the ability to search, discover and visualize integrated, authoritative data and products from a secure, Joint/Service federated environment in support of Warfighter capability development.

• Provide a secure, federated Joint/Service repository of reusable architecture products and reports to enable architecture developers to improve speed of development, reduce or eliminate duplication of effort, and create more efficient, collaborative architecture development and analysis processes in support of developing Joint, interoperable solutions for the Warfighter.

• Provide a common infrastructure that is agile, scalable and reusable so that other architecture development efforts can easily integrate into the federation.

• Reduce resource requirements through use/reuse of already existing technical expertise and previously developed architecture products and services.