title tbd: "18 hundred seconds"

Mil – OSS WG2

Title TBD‘18 hundred seconds’

Trey Oats04 August 2010

Statement A: Approved for public release; Distribution is unlimited (11 May 2010)

‘Operational Problem’

What problem are we trying to solve…Statement A: Approved for public release; Distribution is unlimited (11 May 2010) 2

3

High Level Operational Concept (OV-1)

4

▼OPNAV N2/N6 Sponsor Advocacy Develop architecture / infrastructure once, use

declining resources for application / capability development

−Value across multiple CS/C2 systems moving to enterprise solution

Addressing challenging Disconnected, Intermittent & Low Bandwidth (DIL) communications environment (ROWC2 implications)

Maintain required decision OPTEMPO while reducing uncertainty

CNO Information Dominance brief to All Hands San Diego 3 Feb 2010CNO Information Dominance brief to All Hands San Diego 3 Feb 2010

• Technology development, prototyping & experimentation critical to achieving Information Dominance (“Build a little; Test a lot!”)

– Information management across the seams in DIL environment– Fully flesh-out KPPs– Validate emerging CONOP(s)– Venue for OPNAV/PEO/ONR/Joint Collaboration

Co-Evolution of Technology & CONOP/TTP through Experimentation Co-Evolution of Technology & CONOP/TTP through Experimentation

Achieving Information Dominance Vision

‘the open source approach’

Statement A: Approved for public release; Distribution is unlimited (11 May 2010) 5

‘Maga Design’

Agenda Topics for Discussion

▼ Space and Naval Warfare System Center Atlantic▼ Exposure to our Operating Environment and Past Experiences –

What have we learned?▼ Insight into the Net-Centric Service Based Solutions and Current

Efforts – Who are our customers?▼ Opportunity to reuse capability investments across our

Government Sector – What is the opportunity?▼ Open Source Methodology Applied


Our Focus

▼ Speed to engineered capability ▼ Systems engineering▼ Responsiveness and agility▼ Innovation and experimentation


““The Navy will remain a powerful component of Joint The Navy will remain a powerful component of Joint warfare by exploiting cutting edge technology and warfare by exploiting cutting edge technology and cooperating closely with the other Services, the cooperating closely with the other Services, the interagency community, allies, and international interagency community, allies, and international partners.”partners.”

ADMIRAL GARY ROUGHEAD, Chief of Naval Operations

(excerpt referencing 2009 Priorities, taken from statement made before the Senate Armed Services Committee 28 FEB 08)

7

Major Customers


TOA FY 09 $5.2 Billion

Providing quality full-service systems engineering and acquisition to rapidly

deploy capabilities.

37%Joint 51% Naval

12% National

Navy Marine Corps Army Air Force Unified Combatant Commands Dept. of Defense Dept. of State Dept. of Veterans Affairs Dept. of Justice Dept. of Treasury Dept. of Homeland Security Federal Aviation Admin. National Science Foundation

Oct.’09 Values Oct.’09 Values Oct.’09 Values Oct.’09 Values

8

▼ Understanding and applying Governance as a Standard Engineering approach

across design and development in a System, Systems of Systems (SoS), or Enterprise Environment

− Internal success through application of a Standards, Specifications, Patterns and Practices approach

− Capability Engineering Approach− Coordinated informal testing across SOA programs

− Driving development with open standards regardless of sponsor− Manage the development and implementation process to remain open and flexible and

prevent single vendor or proprietary solutions▼ Align activities across the various Organizations or Agency on implementation of

standards − Informally engaging and connecting program sponsors in each Organization or Agency to

understand requirements to reduce development risk (“Net-Centricity from the bottom-up”)

SSC Atlantic’s early SOA experience enabled:

Leading SOA Development


▼ 1992 - 1999 Tactical/Mobile Variant (TMV) Web XML Documentation Re-Engineering / Data Modelling

▼ 2001 Task Force Web NESI

▼ 2002 - 2003 FORCEnet Horizontal Fusion Begins (October 2002) Horizontal Fusion Quantum Leap 1 (August 2003)

▼ 2004 Horizontal Fusion Quantum Leap 2 (August 2004) Marine Link

▼ 2005 Horizontal Fusion Transitions to Operations

▼ 2006 Horizontal Fusion Merges with NCES

Horizontal Fusion was the first DoD sponsored pure SOA Initiative

SSC Atlantic’s experience with Horizontal Fusion laid the foundation for leading Service Oriented development within the government

SSC Atlantic was OSD’s Technical Lead

HF was adopted as the prototype effort to enable

NCES to enter Milestone B

Historical SSC Atlantic SOA Efforts


Lessons LearnedCollaboration

Informal TestingShared Artifacts

Shared ApproachesShared Code

Co-Evolution of SOA Processes and Artifacts (read:

GOVERNANCE)

Current SSC Atlantic SOA Efforts

▼ Navy Consolidated Afloat Networks & Enterprise System (CANES) ONR Command and Control Rapid Prototype Capability / NAVY SOA Distributed Common Ground System - Navy (DCGS-N)

▼ Marine Corps Marine Air Ground Task Force C2 (MAGTF C2) Marine Link Distributed Common Ground System - Marine Corps (DCGS-MC)

▼ Office Secretary of Defense (OSD) Regional International Outreach (RIO) / SPAWAR Collaboration Hub and Online

Learning Architecture (SCHOLAR) OSD AT&L Acquisition Visibility Tool Adaptive Planning/Force Management Planning & Execution JCTD

▼ Federal Domestic Nuclear Detection Office (DNDO)

▼ Joint Joint Command and Control (JC2) Net-Centric Enterprise Services (NCES) National Senior Leaders Decision Support Service (NSLDSS) JCTD Tactical Edge Data Solutions (TEDS) JCTD C2 CORE JCTD

▼ SSC Atlantic Service Oriented Architecture – University (SOA-U) Multi-Service SOA Consortium SSC-Atlantic Innovation Program

▼ And the list goes on….

SSC Atlantic applies Standards, Specifications, Patterns and Practices across all SOA efforts


SSC AtlanticSSC

Atlantic

Technical

Authority

Programmatic Operations

Capability

Portfolio

Management

TestingFunding

RequirementsApproach to SOA

Governance enables us to look beyond a single

program

Understanding of the intersection between key elements of critical Joint

and Service specific efforts

Strategic GovernanceScales from Enterprise to Project

SSC Atlantic’s Approach to SOA Governance


▼ Technical Governance is enabled by the co-evolution of an Interoperability Baseline

• Co-evolution requires a transparent Collaborative Engineering Environment

• SSC LANT’s ACE is a SOA enabler and leverages the key SOA tenet of Re-use • Discovery• Context• Service Descriptions• Unintended Consumer ($$$$)• Scalability and Extensibility• Interfaces

Advanced Composeable Environment (ACE)

Technical Governance Enabler


▼ Collaborative development across DoD programs is leading to a standard approach to deploying capability through a Capability Module approach Close collaboration during design process is imperative to assure

interoperability Collaboration as each program leverages lessons learned from

other programs during the development process is essential

DeliveryCapability Module is a basic unit of functionality that implements a

certain set of requirements grouped around a specific and focused operational activity

DeliveryCapability Module is a basic unit of functionality that implements a

certain set of requirements grouped around a specific and focused operational activity

As a government-led development effort there are no conflicts of interest with collaborating

– Requirements can be bundled into Capability Modules that can be designed to deliver specific capability within a SOE

– Vendors, Program of Records or Government Agencies can propose/bid on specific Capability Modules

– Capability Modules provide a manageable approach to implementing Service-based requirements

Delivering Capability – SoA What?


TODAY• Siloed development environments• Expensive and time consuming start-up • Limited exposure, sharing, or re-use• Duplication of effort

Developer

Tester

UserCertifier

Shared Test & Development Tools/Services/Environments

Shared Asset Libraries & Repositories

Developer

FORGE.mil• Agile development and testing • Cross-program sharing: software and services• Early and continuous collaboration • Integrated approach to development life cycle• Extensible platform to support delivery of partner capabilities

DoD Open Community Efforts – Forge.mil


DoD Adoption of Commercial Patterns – Joint Combat Systems to Command and Control Limited Technology Experiment

Leveraging Commercial Business and Industry Best Practices and Patterns, the DoD can rapidly accelerate from concepts to employments

AMCO – TrainMRG + ESB

USN - Ships


▼ Understanding of Open Source is still evolving Community / Government / Military Open Source

▼ Understanding of Service Orientation is still evolving Both the design pattern and the technologies

▼ Understanding of Governance is still evolving Interoperability will be achieved through Technical Governance that enables participation in a

flexible, transparent collaborative process Re-use goes beyond just code and applies to knowledge, processes, artifacts, approaches, and

testing (There is no single answer)− Co-evolution of an interoperability baseline of SSPPs will help prevent stove-pipes

▼ Understanding of Cloud is still evolving SaaS / PaaS / IaaS / XaaS Operational requirements - CYBER

“SOA is not the answer to everything; One SOA is not the answer to anything.”

The Challenge Continues…


SSC Atlantic is:▼ Committed to Joint Interoperability

SSPPs Gov’t / Gov’t / Industry Partnerships

▼ Service-Oriented Technology SMEs for DoD Long history of involvement at the bleeding edge Depth of program and project experience across DoD / Federal Deep pool of resources working leading edge technology and governance

innovation− Committed to continued workforce development (SOA U)

▼ End-to-end engineering environment focused on Open Source / Service-Oriented / Net-Centric solutions

Summary


HR 2647, National Defense Authorization Act for Fiscal Year 2010, Sec. 804.

▼ “The Secretary of Defense shall develop and implement a new acquisition process for information technology systems. The acquisition process developed and implemented pursuant to this subsection shall, to the extent determined appropriate by the Secretary –

. . . be based on the recommendations in chapter 6 of the March 2009 report of the Defense Science Board Task Force on Department of Defense Policies and Procedures for the Acquisition of Information Technology; and

. . . be designed to include— early and continual involvement of the user; multiple, rapidly executed increments or releases of

capability; early, successive prototyping to support an evolutionary

approach; and a modular, open-systems approach.

CIO Memo “Clarifying Guidance Regarding Open Source Software (OSS)”

“To effectively achieve its missions, the

Department of Defense must develop and update

its software-based capabilities faster than ever, to

anticipate new threats and respond to continuously

changing requirements. The use of Open Source

Software (OSS) can provide advantages in this

regard.”

DoD CIO Policy and Guidance



“Open source software… is often licensed under terms that require the user to make theuser's modifications to the open source software or any software that the user 'combines'with the open source software freely available in source code form.” If the contractoruses open source software in the performance of a Government contract, it must ensurethat the use thereof does not: (i) create, or purport to create, any Government distributionobligations with respect to the computer software deliverables; or (ii) grant, or purport togrant, to any third party any rights to or immunities under Government intellectualproperty or Government data rights to the Government computer software deliverables. For example, the contractor may not develop a computer software deliverable using aopen source program (including without limitation libraries) and non-commercialcomputer software program where such use results in a program file(s) that contains code from both the non-commercial computer software and open source software if the open source software is licensed under a license that requires any ‘modifications’ be made freely available. Additionally, the contractor may not combine any non-commercialcomputer software deliverable with open source software licensed under the GeneralPublic License (GPL) or the Lesser General Public License (LGPL) in any manner wheresuch use would cause, or could be interpreted or asserted to cause, the non-commercialcomputer software deliverable or any modifications thereto to become subject to theterms of the GPL or LGPL.”

‘Naval Open Architecture Contract Guidebook For Program Managers Version 2.028 April 2010’

What’s ‘good enough’ for Contract Language

NECC C2 Alerting

MAGTF C2Open Community Process

Tactical SOE

CLDT Toolkit

CANESProprietary SOA solutions to expensive

Use of UCORE Data Model

Cross Domain Discovery/Consumption/Orchestration

Secure Discovery Research

ONR testing

AxiomOpen Source SOA Approach

Baseline Track Service

Federated Identity

Semantic SOA

NCES/HFStandards, Specifications, Patterns &

Practices Approach

Platter Development and Testing Concept

MarineLinkAxiom SOA Architecture

BATS Adaptor

Army CIDNE Service

NSLDSSNCES Core Service Integration

Experience

SOA-UTrained SOA Subject Matter

Experts

SCHOLARCollaboration Capability Module

Collaboration CONOPS

JCTD Adaptive PlanningJOPES Service

CFAST Service

JCRM Service

OSD AT&LAcquisition visibility into

Joint SOA DNDOCommon Alerting Protocol (CAP)

KML Servlet

Certification & Accreditation (C&A) of SOA

SOA Contributions to USMC CPMO


NECCSOA Reference Implementation with IATT

Mapping and Alerting Portlets

Army C2 Messaging CM Infrastructure (JMS/AMQP)

SourceForge Repository

CLDT Toolkit CANESOpen Source Approach

CLDT (VMF Framework)

Capability Engineering Approach

Co-Development of Reference Impl

Track Service

KML Servlet

AxiomCDLT (VMF Framework)

JBOSS Infrastructure

AMQP Messaging Approach

MarineLinkOpen Source Components

NSLDSSJBOSS Infrastructure

JCTDs (AP & TEDS)SOA Reference Implementation

Capability Engineering Approach

OSD AT&LCommon Infrastructure

Approach DNDOCommon Infrastructure Approach

NECC C2 Alerting

COCTactical SOE

AMQP and JMS Messaging

CLDT Toolkit

USMC CPMO Contributions to Community


Questions


title tbd: "18 hundred seconds"

Technology

public release distribution

technology development

experimentation statement

horizontal fusion merges

horizontal fusion transitions

forcenet horizontal

horizontal fusion quantum

open source approach