emerging trends in net-centric operations

Emerging Trends in Net-Centric Operations

Standards and Technology

Robert Marcus

Themes

A key emerging trend is shared resources e.g. data, events, hardware, network, and services

Process, organizational, frameworks, and standards support is needed for efficient interoperable sharing

Standards can depend on collaboration use cases and domain-specific requirements

Interoperability use cases can often be categorized as Intranet-Centric (Mandated), Extranet-Centric (Negotiated), and Internet-Centric (Voluntary)

The selection and deployment of the appropriate technologies and standards for specific use cases is a critical issue for net-centric operations

Topics

Net-Centric Operations 2.0 (NCOIC) Enterprise Architecture Delivery (OSD NII, DISA) M&S Enhanced Systems Engineering (NCOIC) Systems and SOA standards (NCOIC) Capabilities Mediation for SOA (DISA) Emerging Standards for SOA (OMG, DISA) Industry Standards for C2 Data Sharing (JFCOM) Complex Event-Decision-Response (NCOIC, DISA) Adaptive Information Dissemination (Army) Foundation Information Grid (NCOIC and SPAWAR)

NCOIC = Network Centric Operations Industry Consortium

The Consortium exists to exchange ideas and produce process and technology deliverables that facilitate force transformation through NCO.

4

NCOIC Overview A Forum for Subject Matter Experts to Collaborate on NCO Initiatives:

Better Understand Customer’s NCO Vision, Goals, and Objectives Exchange strategies and proven approaches to enhance system

delivery

An Organization Committed to Establishing Open, Interoperable Systems using Common Best Practices and Systems Engineering Techniques:

Facilitates Consistency Across Industry (100 members) Advocates for Open and Interoperable Systems Design

Companies Committed to Meeting the Government More Than Half-Way: Understanding Industry’s Responsibilities and Acting Addressing the Problem, Taking Initiative, Understanding the

Requirement Seeking close collaboration with Government and the rest of industry

5

NCOIC Technical Approach Complete a thorough and rigorous analysis of pertinent government agency

architectures Customer Requirements Team

Develop a secure information management overarching architectural framework / reference model to identify open standards and their patterns of use

Architectures and Standards Analyses Team

Identify the widest possible community of open standards-based product types Building Blocks Team

Develop a program for education for NCO Education and Outreach Team

To plan and implement strategies to develop effective collaborative engineering environments

Engineering Processes Team

Net-Centric Operations 2.0

Overview slide for an NCOIC session that I organized covering standards from the desktop (e.g. OpenAjax) to tactical networks (e.g. Data Distribution Services)

The goal of the session was to present emerging technologies and interoperability standards

Key issues were areas where more interoperability standards were necessary e.g. ESBs and mashups

Net-Centric Operations 2.0

1. Web Client Application

4. Composites

2. Web Message Bus

3 .Enterprise Service Manager

5. Enterprise Service Buses

6. Enterprise Data and Systems

8. Tactical Networks

7. Gateway

Adaptor

Data

Browser – RIA, AJAX, Mashups

XML over HTTP

XMLHttpRequest

Web Server

SOAP over HTTP

SOAP Server, WCF Host, Application Server

Services, SCA Services, SCA ESBs with multiple transports

Orchestration – BPEL, BizTalk

Data

HTTP

EnterpriseMashups/Pipes

System

Aggregation

Gateway Server – Protocol and Data Transformations

Sensor Networks, Mobile Platforms, Devices, Gateways (DDS, Efficient XML)

Event Processing

External Interfaces

SDO SDO

Net-Centric Operations 2.0 Issues

Rich Interface Applications (RIA)

Enterprise Service Managers

ESB ESB ESB

Tactical Networks

Near Real-time Data Gateways

InteroperabilityInteroperability

Web Message Bus

Connections and nodes in bold are some key issues for Net-Centric Operations 2.0

Enterprise Service Buses

Enterprise Architecture Delivery Process

This is slide from a presentation at an NCOIC session that I organized for DISA and OSD NII on “SOA Deployment: Industry Best Practices”

The talk was based on my experiences at Boeing and General Motors

A similar approach was the basis of a chapter that I wrote for the CRC Handbook of Object Technology on “Transitioning Large Organizations to Object Technology” and an Architecture Delivery Process that I created at General Motors.


1.Concept Refinement

2. Technology Development

3.System Development

and Demonstration

4. Production and

Deployment

5. Operations And SupportProjects

Enterprise Architecture Delivery Group

Centralized Shared Resources

StandardReusableCONOPS

StandardReusable

TechnologyComponentsAnd Services

Standard Models,Existing Testbeds And Simulations

Existing Hosting

Centers andPlatforms

Reusable System

ManagementTools and Processes

Up arrows are delivered standards. Down arrows are improvements based on experience

1104/08/23

ReusableResource Repository

Project 1

Project 2

Project 3

Project 4

Centralized Standards

Organization

Enterprise Architecture

DeliveryTeam


This slide was originally prepared for a proposal to the Air Force Research Lab on “Test Tracks for System of Systems Testing”

The basic concept was to combine Live, Virtual and Constructive (LVC) simulations of systems at different stages in the system life cycle in an integrated testing environment

M & S Enhanced Systems Engineering

M & S Enhanced Systems Engineering

Proof of Concept

Live (C), Virtual (B) and

Constructive (A)System and Services

TestTrack

TechnologySimulation

TechnologyEmulation

LiveSystem

withServices

System and Services

Verification

DesignTesting

Systems andServices

Validation

InterfaceTesting

Concept Testing

System andService Analysis,Design, andDevelopment

System Development, Services Composition, and Systems Integration

AB

C

Concept Refinement,System and ServiceRequirements

DoD System Life Cycle

Simulations, Systems and Services

e.g. A, B,C

Tests and V & V

System Engineering and SOA Standards

Overview slide for an NCOIC Session on Modeling and Simulation enhancements for System Engineering that I organized

The speakers included leaders on many of these topics including SysML, SDF, and UPDM.

The key issue for the session was the relationship between system and service modeling including related simulations

A secondary issue was the mapping between enterprise and technical architectures

System Engineering and SOA Standards

DoDAFDoDArchitecturalFrameworkacross multiplelevels(Zachman And MoDAF are similar)

UPDMUnified

Modeling Language

(UML) Profile

forDoDAF

and MoDAF

SOAArchitecture

basedon

services

SysML UML Extension

for SystemsEngineering

FEA-DEA-BEAFederal and Defense

Enterprise Architectures

SCA and OSOA Component Interface

Description

SCBAFEA extension to

Services and Components

SDFService Interface

Descriptions

Layers

EnterpriseArchitects

SoftwareArchitects

ProgramArchitects

System Architects

And Engineers

MDAUML Models For software Architecture,

Components and interfaces

Developers Testbeds such as Federated Development and Certification Environment (FDCE)including Live Systems, Modules, Components ,Services and Simulations

Services - EnterpriseSystems - Operations

Capabilities Mediation for SOA

This slide was developed in conjunction with DISA’s Net –Enabled Command Capability (NECC) group

The purpose of the slide was to lay out a strategy for defining, discovering and developing new application capabilities within service oriented architecture

It was also meant to be the basis for a series of Industry Day seminars to DISA


Existing, Enhanced, Composite and possible new services and/or systems

USERS

Capability specifications (with priorities) and possible new capabilities

Capability description (with cost of implementation) and possible new capabilities

New capabilities available

New capabilities needed

Set of Services

Set of Requirements

Mediating

User Requirements and Derived Requirements

Matchmaking

Systems Engineering

Group

Emerging Technology

Group

Capabilities Mediation

Group


JPMO

FDCE Vendors

Open SourceLibraries

StandardsBodies

Contractors

Consumers Producers

MikeHebert(JPMO) Bob

Marcus(NCOIC)

Needs

Offerings

(1) (2)

(3)

(4)

NECC ST&TMarketplace

(5)(6)

(7)

(8)

(3)

(7)

(9)

JMPO, FDCE groups solicited for ST&T needs

Needs consolidated, prioritized and binned

Needs sent to Bob Marcus

Clarify need

Match needs with offerings

Gain producers interest

Develop list of offerings – use Industry Days as delivery mechanism

Scrub list of offerings and do final offering selections, finalize schedules for Industry Day(s)

Ensure Industry Day(s) meet needs and ensure participation

Emerging Standards for SOA

Overview slide for an OMG session that I organized for DISA’s Net-Enabled Command Capability group

The goal of the session was to learn about the emerging standards and to discuss possible harmonization across standards groups

I later presented a similar talk at a meeting of the Federal SOA Community of Practice (SOACoP)

Emerging Standards for SOA

Service Data Objects

Service ComponentArchitecture

Open SOA Standards

Web ServicesDescription Language(WSDL from W3C)

Web Service StandardsDevelopment

Apache Tuscany

Eclipse SOADevelopment Tools

C2 Model-BasedData Engineering

Universal Description, Discovery and Integration (UDDI from OASIS)

Submissions to W3CWS-Policy Assertions and Attachment

Web Ontology Language(OWL-S)

WSDL-S

OASIS and WS-I StandardsOASIS WS-Security

WS-I Security Profiles

Efficient XML

Service Data Objects

Service ComponentArchitecture

Web ServicesDescription Language(WSDL)

Apache TuscanyEclipse SOADevelopment Tools

C2 Model-BasedData Engineering

Universal Description, Discovery and Integration (UDDI)

WS-Policy Assertions and Attachment

Service Definition Framework (SDF)

Web Ontology Language for Services (OWL-S)

WSDL-S

WS-Security and WS-I Security Profile

Emerging Standards for SOA (Timeline)

Industry Standards for C2 Data Sharing

Part of a NCOIC deliverable that I prepared in response to specific requests from the Joint Forces Command (JFCOM)

Standards and technologies were discussed and recommended based on categories of use cases

The draft of the deliverable was circulated within DISA and OSD NII as a possible model for standards description

Industry Standards for C2 Data Sharing

Based on Use Cases (e.g. Intranet-Centric, Extranet-Centric, Internet-Centric)

Web of Services (SOAP/HTTP, ESBs, REST) Data Sharing (Databases, Data Models, Metadata) Detailed Summary Table with 23 Rows covering

Standard or Technology Description or Purpose Status and Future Plans Relationship to Other Standards Recommendations

Industry Standards for C2 Data Sharing Concepts Intranet-Centric Extranet-Centric Internet-Centric

Business analogs Internal Enterprise Business to business Business to public

Examples of Use Cases Single organization operations Joint operations Emergency and stability operations

Implementation of standards Mandated Negotiated Partial and de facto

System Coupling Tighter coupling Looser coupling Ad hoc coupling

Communities of users Communities of interest (COI) Cross COI collaboration External non-COI collaborators

Governance Centralized pre-defined policies Contractual agreements Dynamic policies enforced

User authentication Individuals users known in advance

User organizations known in advance

Dynamic users and organizations

Middleware for services Enterprise Service Bus SOAP Web Services, Service Gateways

Simple Web services e.g. REST

Service Discovery Design-time Deployment and Configuration Run-time

Composition and mashups More static and controlled More dynamic based on standards Ad hoc and less maintainable

Data sharing Common databases, data models, and semantics

Standard data models and message formats for data exchange

Public databases and self describing data in messages

XML Metadata Internal standards Shared standards Public standards

Complex Event-Decision-Response

Slide prepared for an NCOIC session on “Event Processing in Net-Centric Operations” that I organized and a workshop on Complex Systems

The key idea is that there are multiple levels of event processing, reactive decisions, and output responses


PreprocessIn

Event Input

u

SimpleEvent

Processing

ComplexEvent

Processing

ModelUpdate

New Model

StrategyTactics HQOperations

FieldOperations

Situation Impact Object Process

Simple Response

Service Composition of Services

Plan Modification

New Plan

Complex Response

Update Plan

Create New Goals and

Plan

Sensor and Effects

Management

Observation and Control Components

InRespon

se Output

u

Assess and

Decide

Measurement

Field Processors

Data Structured Data Information Knowledge Wisdom

Sense

Respond


Sense and Respond applications include Algorithmic Trading, Threat Detection, Logistics and C4ISR

Event processing provides sensing capabilities for applications Services can be used to provide response capabilities Complex responses are created by composing simple

responses Complex events are created by combining simple events

similar to data fusion in C4ISR Complex Event Processing engines combine multiple

capabilities and near real-time performance The OMG is developing an events Reference Metamodel

27

Adaptive Information Dissemination

I developed a design for bandwidth management of the Army’s Future Force Warrior mobile ad hoc network

The goal was to ensure important messages had sufficient QoS even when resources were limited

The importance of a message was determined by a software Dissemination Strategy Manager at the application layer

Adaptive Information Dissemination Limited bandwidth on the battlefield requires selective

allocation of resources Cost–benefits analysis and decision rules for QoS mode

selection Modes determine frequency, latency, fidelity, and streaming

rates Impact analysis of events on costs and benefits Benefits analysis based on mission value of nodes

messages Costs computed from bandwidth (and battery charge for

dismounts) resource constraints

3004/08/23

1. Battlespace Event from External Applications

6. New Mode Decision

Strategy Manager 4.Impact Analysis for Event

5.Assess Aggregate Benefit versus Cost

Event has low impact

No need tochange mode

DecisionSupportSystem (DSS)

2. Data Update to DSS Object

3. Data Extracted from DSS Object

StateVariables

Adaptive Information Dissemination

Foundation Information Grid

I proposed the Storage Resource Broker (SRB) from UC San Diego as a foundation for bottom-up construction of information grids for NCOIC demos

An SRB Zone provides unified access through a Metadata Catalog to multiple data sources independent of location, database and storage device

SRB Zones can be federated by mappings between Metadata Catalogs

The SRB is freely available to government projects


Physical Storage Independence

Database Independence

Location Independence

MetadataCatalog

Zone1

Physical Storage Independence

Database Independence

Location Independence

MetadataCatalog

Multiple Client Interfaces e.g. Web Services

Zone 2

Drivers Drivers

3304/08/23


Future Activities Technical Lead for NCOIC review of DISA’s

NECC architecture documents Explore possible standardizations for Complex

Event Processing with OSD NII and FAA Organize a session on “Net-Centric Computing

Environments: From Grids to Virtualization ” co-hosted by NCOIC and Open Grid Forum

Analyze feasibility for defining verifiable layers of interoperability for specific missions with NATO