ndia aiaa interoperability system integration conference industry session n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
NDIA/AIAA Interoperability & System Integration Conference Industry Session PowerPoint Presentation
Download Presentation
NDIA/AIAA Interoperability & System Integration Conference Industry Session

Loading in 2 Seconds...

play fullscreen
1 / 11

NDIA/AIAA Interoperability & System Integration Conference Industry Session - PowerPoint PPT Presentation


  • 79 Views
  • Uploaded on

NDIA/AIAA Interoperability & System Integration Conference Industry Session. Rick Baily The Boeing Company. Interoperability Challenges. Huge number of “separate” systems Unique/non-standard messages Systems continue to change. JBMC2 Mandate: Interoperability or retirement by 08’

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'NDIA/AIAA Interoperability & System Integration Conference Industry Session' - tanith


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
ndia aiaa interoperability system integration conference industry session

NDIA/AIAAInteroperability & System Integration ConferenceIndustry Session

Rick Baily

The Boeing Company

interoperability challenges
Interoperability Challenges
  • Huge number of “separate” systems
  • Unique/non-standard messages
  • Systems continue to change

JBMC2 Mandate: Interoperability or retirement by 08’

Appropriate, but challenging, goal that requires systematic process

to assure success

interoperability definition from jbmc2 roadmap industry summit
Interoperability Definition(from JBMC2 Roadmap Industry Summit)
  • Definition of interoperability – The ability of systems, units, or forces to provide service to and accept services from other systems, units, or forces and to use the services so exchanged to enable them to operate effectively together.
    • DoDI 4630.8 defines a process for achieving systems interoperability … uses mission area integrated architectures as the basis for interoperability requirements …
    • CJCSI 6212.01C details a methodology to develop interoperability key performance parameters (KPPs) based on integrated architecture products …
    • CJCSM 3170.01 states interoperability KPPs are based on the top-level information flows depicted as information exchanges in OV-3s …
    • Joint Technical Architecture (JTA) (and other sources) suggest developing Technical Views (TVs) to define standards and rules governing the … interaction and interdependence of systems … use TVs to promote efficiency and interoperability …

Recurring Theme – Use Architectures to Define/Implement Interoperability

Definition must have JBMC2 context (relevant /tailored)

network centric interoperability
Network Centric Interoperability
  • NC Communications Interoperability ensures bits move between nodes
  • NC Information Interoperability ensures:
    • Bits converted correctly into information
    • Information exchange properly managed
    • Applications find compatible applications to collaborate with and understand semantics of information exchanged
general node level interoperability

Mission App

Mission App

App compatibility

Common Serv.

Common Serv.

Info Mgmt

Info Mgmt

Info compatibility

Network & Trans.

Network & Trans.

Comm compatibility

Phy & Data Link

Phy & Data Link

General Node Level Interoperability
  • Interoperability between two nodes requires
    • Application compatibility
      • Logic – including algorithmic compatibility
      • Information semantics
    • Information management compatibility
      • Syntax, middleware
    • Communications compatibility
      • Physical, data link, network, transport
future combat systems fcs interoperability challenges
Future Combat Systems (FCS)Interoperability Challenges
  • 85 systems required
  • Vast amounts of unique/non-standard messages
  • Limited amount of testing with live systems
  • Interoperability services time-phasing with C2 services development
  • External systems changing – need synchronized change process

Approved for Public Release, Distribution Unlimited TACOM 23 March 2004

fcs interoperability services levels
FCS Interoperability Services Levels
  • Simple Message Exchange
    • Uses Proxies and translators
    • Limited to Situation Awareness via positional data
    • Requires prior knowledge of systems, sensors, and effectors
  • Dissemination and Discovery
    • Nodes discover other nodes capabilities without prior knowledge or planning (i.e. “devices on the net”)
      • Exchange done via native XML communication
  • Common C2 Services
    • No human translation or analysis/understanding required
    • Everyone “sees” same thing

Approved for Public Release, Distribution Unlimited TACOM 23 March 2004

fcs interoperability architecture
FCS Interoperability Architecture

Current systems provide a Service Based Interface (SBI) to the SOSCOE system (Open Architecture) or have a specific conversion service within Interoperability Services to enable their capabilities as services (Closed Architecture).

Use or disclosure of data contained on this page is subject to restrictions on title page.

Approved for Public Release, Distribution Unlimited TACOM 23 March 2004

fcs interoperability enabling services

Discovery

Service

Configuration File

4a

4b

Reads

config file

1

Registers potential services and attributes of external systems

Discovers for specified

Services

Remote Proxy

Service

Creates Translators as Threads

2

Translator Service

Decoder

Protocol

Comm Intf

Encoder

Translator Service

Translator Service

Decoder

Decoder

Protocol

Protocol

Comm Intf

Comm Intf

Encoder

Encoder

3

3

3

Self configure components

FCS Interoperability Enabling Services
  • Remote Proxy Services
  • Self Configuring Translator(s)
  • Discovery Service

Approved for Public Release, Distribution Unlimited TACOM 23 March 2004

roadmap to interoperability
Roadmap To Interoperability
  • IER based
  • Hard coded interfaces (syntax & structure)
  • Tightly coupledphysically
  • Point to point logically
  • Brittle and rigid
  • Enterprise/program level

SemanticServices

ApplicationIntegration

Service Integration

  • Ontology based
  • Semantic mediation
  • Semantic mapping
  • Context sensitivity
  • Global/joint level
  • Service oriented
  • Std. schemas & interfaces
  • Discovery of services
  • Loosely coupled physically
  • Point to point logically
  • Vertical industry/service level

Net CentricEnvironment

1990s

2000s

2020s

interoperability recommendations
Interoperability Recommendations
  • Create JBMC2-level architecture to drive interoperability
  • Use systematic process to assess level of interoperability affordably achieved by each current system
  • Have a current force “hit list” of interoperability issues to solve and derive lessons-learned
  • Settle on a limited, but not singular, set of message and data standards – consistent with JBMC2 architecture and warfighting environment
  • Provide rapid, adaptable testing with emulated and live systems in realistic environment
  • Provide mechanism for publishing changes to current systems to allow pre-synchronization of future systems