4892-1

NCOIC MSD Initiative:

Net-Centric Operations 2.0,

Domain-Specific SOA Frameworks,

and M&S Testbed Demos

Bob Marcus robert.marcus@sri.com

4892-2

Executive Summary

The NCOIC and its customers are implementing service-oriented architectures (SOA) in multiple domains

Domain-specific SOA frameworks can be used to provide a foundation for specifying required capabilities for projects

NCOIC M&S demonstrations can test and evaluate the available capabilities of emerging technologies for these frameworks

There is a suite of new technologies that will enable future agile implementation and deployment of new applications

These technologies and applications can be characterized as “Net-Centric Operations (NCO) 2.0”

Proposed Initiative: Work with multiple NCOIC and customer projectsto design and implement test and evaluation demos of NCO 2.0 technologies applied to domain-specific SOA framework scenarios

4892-3

NCOIC Initiative Summary Diagram

Net-Centric Operations 2.0 Emerging Technologies

Customers

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

Customer Domain-Specific Framework Requirements

Matchmaking TestingNCOIC

4892-4

Net-Centric Operations 2.0

4892-5

Operations = Enterprise and Tactical Networks

From RTI

4892-6

Net-Centric Operations 2.0 Architecture

1. Web Client Application

4. Composites

2. Web Message Bus

3.Enterprise Service Manager

5. Enterprise Service Buses

Adaptor

Data

Browser – RIA, AJAX, Mashups

XML over HTTP

XMLHttpRequest

Web Server

SOAP over HTTP

SOAP Server, WCF Host, Application Server

Services, SCA Services, SCAESBs with multiple transports and XML and binary XML data

Orchestration – BPEL, BizTalk

Data

HTTP

EnterpriseMashups/Pipes

6. Enterprise Data and Systems

System

Aggregation

8. Tactical Networks

7. Gateway Gateway Server – Protocol and data transformations

Sensor Networks, Mobile Platforms, Devices, Gateways

4892-7

Issues for Net-Centric Operations 2.0

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 key issues for Net-Centric Operations 2.0

Enterprise Service Buses

4892-8

Office of Force Transformation Domains

Physical Domain

where strike, protect, and maneuver take place across

different environments

Information Domain

where information is created, manipulated and shared

Cognitive Domain

where perceptions, awareness, beliefs, and values reside

and where, as a result of sensemaking, decisions are made

Social Domain

interactions between and among force entities

Source: http://www.oft.osd.mil/library/library_files/document_353_NCO%20CF%20Version%201.0%20(FINAL).doc

TacticalNetworks

EnterpriseSystems

Rich Interfaces

Web 2.0Applications

4892-9

NCO 2.0 Enabled Applications in OFT Domains

Physical – Gateway servers support integration across networks

Information – Mashups, adapters, and grids support data sharing

Cognitive – Rich Interface Applications support decision support

Social – Web 2.0 applications supported by Web Message Bus

4892-10

Domain-Specific Frameworks for SOA

4892-11

NCOIC and Customer Projects

DISA Network Enabled Command Capability

JFCOM Modeling & Simulation

SPAWAR Maritime Domain Awareness

ASD NII End-to-end QoS and Network Management

NATO Network Enabled Command and Control

NCOIC Sense and Response Logistics

NCOIC Net-Enabled Emergency Response

NCOIC Building Blocks Certification

4892-12

Domain-Specific Frameworks for SOA

Common Services Across Multiple Domains

Domain Framework

including Service

Specifications, XML

Message Formats,

Customized Displays,

and Process Models

Domain Framework

including Service

Specifications, XML

Message Formats,

Customized Displays,

and Process Models

Domain Framework

including Service

Specifications, XML

Message Formats,

Customized Displays,

and Process Models

Interfaces Services

Interfaces Services

4892-13

Domain-Specific Frameworks for SOA Steps

Divide the enterprise into domains

Identify and implement common services across domain

For each domain; specify domain-specific services, XML message formats, process models, customized displays, and other needed standards

Document the interface services needed between domains

Implement the domain-specific SOA framework by:

• Choosing middleware (e.g. enterprise service bus),

• Selecting and/or creating services meeting specifications

• Map standard data models to XML message formats

• Developing customized user interfaces

• Create executable processes across services using middleware

Build interface services across domains

4892-14

NCOIC M&S Testbed Demos

and Capabilities Mediation

4892-15

Capabilities Testing and Evaluation (Mediation)

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 Testing

4892-16

Implementation of Capabilities Testing

Organization – Domain experts, emerging technology leaders, and NCOIC M&S Test and Evaluation group

Domains – Multiple domains that require SOA deployment

Tools – Framework design, capability matching, SOA implementation, modeling and simulation

Process – Receive required capabilities from domain experts and end-users. Determine available technology capabilities from emerging technology leaders and suppliers. Perform initial matchmaking to determine possible gaps. Use NCOIC M&S testbed demonstrations to evaluate the need and/or availability of additional capabilities

Communication – Iterative discussions with project teams and emerging technology suppliers

Skills – Understanding of emerging technology descriptions (e.g. NCO 2.0) and domain-specific framework specifications

4892-17

Capabilities Mediation Example

System of Systems Program

Management Vendors

Open SourceLibraries

StandardsBodies

Contractors

ConsumersProducers

SystemsEngineering

Group EmergingTechnology

StrategyGroup

Needs

Offerings

(1) (2)

(3)

(4)

(5)(6)

(7)

(8)

(3)

(7)

(9)

System of System Program solicited for ST&T needs

Needs consolidated, prioritized and documented

Needs sent to Emerging

Technology Strategy

Clarify need

Matchneeds with offerings

Evaluate producers

Develop list of possible offerings

Scrub list of offerings and do final offering selections,

Ensure offerings meet needs and constrains andfinal acceptance for Program

CapabilitiesMediation Group

4892-18

Net-CentricInteroperabilityDemos using

M&S

Net-CentricInteroperability

Command &Control

e.g. Models ofcustomerobjectives

e.g. NESI,NATO NC3TA

Others

e.g. E-commerceWeb Services

High LevelEnterprise

& Reference & Capability Models

(e.g. FEA, OSI, etc)

DomainMissionModels

Military

HomelandSecurity/

Police/Fire

NCAT

Others

DomainGeneral

Architectures

Specific NodeArchitectures

CR NIF

Common Framework of Guidance to

AchieveInteroperability

Model forAlignment ofBoundaries &Interfaces of

both Functions and Services

NIF

….…. SCOPE

Tailored

The NCOIC Tools work together to assist in achieving interoperable systems

BB.. ....……

NCOIC Demos for Capabilities Testing

MilitaryImplementation

Government/Commercial

Implementation

High Level Models

4892-19

Capabilities Mediation for NCOIC

Domain-specific SOA Frameworks will be used to define top-down required capabilities for NCOIC projects

Net-Centric Operations 2.0 will be used for bottom-up identification of emerging technologies

Domain-specific services and data models will also be part of the emerging technologies evaluated

Demonstrations will be created based on project scenarios to analyze the fit between domain-specific frameworks and technology implementation using emerging Net-Centric Operations 2.0 technologies

The results of the demonstrations will be reported back to the projects with recommendations for additional service needed or additional operation capabilities available,

4892-20

Net-Centric Operations 2.0

Backup Slides

4892-21

Net-Centric Operations 2.0 Elements

1. Web Client Application Container (RIA, AJAX, Mashups) - Browser extended with scripting, XML, and asynchronous server access (e.g. Ajax frameworks). Provides greater flexibility for creating rich customizable applications. 

2. Web Message Bus  - HTTP and XMLHtttpRequest (asynchronous) extended for reliability and two communication. Adds needed enterprise capabilities to application client containers.

3. Enterprise Service Manager (App Servers, SOAP Servers, Containers) - Combination of Web Server, Application Server, and Web Services Server. Core middleware for accessing enterprise SOA environments.

4892-22

Net-Centric Operations 2.0 Elements (con.)

4. Composites ( Aggregation, Mashups, Orchestration) -  Orchestration, Business Process Execution, Enterprise Mashups, and Pipes are examples of composites of services and/or data. Enables the rapid creation of new applications and data views from multiple underlying sources. 

5. Enterprise Service Bus (Message Brokers, Service-oriented) - This is the key infrastructure middleware for creating a large-scale Service Oriented Architecture. It combines messaging, multiple transports, data transformation and adapters to provide the foundation for enterprise SOA.

4892-23

Net-Centric Operations 2.0 Elements (con.)

6. Enterprise Data, Services and Systems (Data, Services, Systems) - Legacy and new enterprise resources. Standardized adapters and data access methods are needed to interface these resources to the enterprise SOA

7. Gateway Servers - Connects diverse networks and platforms to an enterprise or backbone network. Performs the require data and protocol transformations needed for efficient interoperability

8 . Mobile Tactical Networks (Vehicles, Devices, Sensors) – Networks that are used during field operations including combinations of mobile platforms, wireless communication, sensors and handheld devices. These networks will often have to support dynamic or ad hoc network protocols.