aircraft, launcher & weapon interoperability common...

NIAG Subgroup 97Aircraft, Launcher & Weapon Interoperability

Slide 1

NATO Unclassified

SAE Aerospace ASDAvionic Systems Division

NIAG Subgroup 97In collaboration with SAE Aerospace AS-1

Aircraft, Launcher & Weapon Interoperability

Common Interfaces

Study Executive Briefing to

AS-2C

January 2007

Douglas Gregory

Chairman of NIAG Subgroup 97

Chairman of SAE Aerospace ASD


Slide 2

NATO Unclassified


Briefing Outline

• ALWI-CI High Level Operational Concept

• Study Background

• Study Elements

• ALWI-CI Concept

• Specific Findings/Recommendations


Slide 3

NATO Unclassified


High Level Operational Concept

Mission Plan(e.g. MIL-STD-3014)

Mission Update

Service Data

Broker

Publish

Discovered Mission ServicePnP Mission Service Data

Mission Service User

Subscribe

PnPStore Data

Weapon (e.g. NAI)

Load o

ut

Rapid integration & validation of

weapon load-out

PnP Load-outConfig. Data


Slide 4

NATO Unclassified


Study Background and Identification

• Third ALWI study:

– ALWI pre-feasibility study, NIAG Subgroup 59, December 1999

– ALWI-2 study, NIAG Subgroup 72, March 2004

• ALWI-CI study, NIAG Subgroup 97, November 2006

– ALWI-3 Follow Up Study Definition, April 2005

– Proposal for NIAG Study on ALWI Common Interface Control, Oct 2005

– Study Reference: NIAG-D(2006)0004 | AC/224(ACG/2)D(2006)0004


Slide 5

NATO Unclassified


Study Elements/Teams

1. Standards planning (Technical Architecture)

2. Common Store Control Service (API Methodology)

3. Universal Aircraft/Store Interface Concepts

• UAI

• NATO Mission Planning Systems

4. Aircraft Specific Implementations (Plug and Play)

• Grid Computing Compatibility

• Lifecycle Costs

• Certification

• Demonstrations


Slide 6

NATO Unclassified


Study Organisation and Support

NIAG Subgroup 97

Team 1

Team 4

Team 3

Team 2

D. Gregory (GDAIS) - USH-K. Wilhelm (IABG) - GEK. Rigby (BAE Systems) - UK

F. Benedick (WINTEC) - USK. Rigby (BAE Systems) - UK

A. Zuzej (Diehl-BGT Defence) - GER. Rodreguez (GTD) - SP

D. Neel (LM Aero) - USP. Miles (MBDA) - UK

H. Schlatt (EADS) - GEA. Vallee (Sagem) - FR

Supported by

SAE Aerospace AS-1B

Supported by

SAE Aerospace AS-2C

Supported by

USAF UAI

Supported by

Kennedy Carter


Slide 7

NATO Unclassified


Study Participants

France Dassault, MBDA, Sagem

Germany ACMA, Diehl-BGT Defence, EADS, ESG, IABG, MarServices

Italy Alenia Aeronautica, Galileo Avionica, MDBA

Spain GTD

Turkey STM, Tubitak-Sage

UK BAE Systems, Kennedy-Carter, MBDA, Qinetiq

USA Boeing, GDAIS, LM Aero, Raytheon, Sverdrup, USAF, WINTEC


Slide 8

NATO Unclassified


Study Flow

High-level operational concept

description OV-1

Overview and Summary

Information (AV-1)

Operational node connectivity description

OV-2

Operational information exchange

matrix OV-3

Operational activity model

OV-5

System Interface Description SV-1,

+SV-2

Systems Data Exchange Matrix SV-6

Technical standards

profile TV-1, +TV-2

Physical Schema SV11

Systems Technology

Forecast SV-9

Systems Evolution

Description SV-8

Systems Functionality Description SV-4


Slide 9

NATO Unclassified


System Technology/Evolution Forecast

5 yrs 10 yrs 15 yrs

MMC Micro-munitions Directed Energy WeaponsMission Stores

now

Weapons

Aircraft-weapon connectivity

AS5652

AS5653 WDM Optical LANµMSI

1553

UAI, MiDEF

Weapon message sets

NEW Weapon on Computing Grid

NNEC

SOA Mission ServicesMission Messaging

Plug and Play Computing

Std APIs (PIMs)Auto-codeMDA for embedded

computing


Slide 10

NATO Unclassified


ALWI-CI Parallel with PC Industry Interoperability

IEEE-1284

HPGL

MIL-STD-1760

UAI_PSICD

Connector Interface1980s

Printer_driver_type.DLL

Printer_driver_type.INI

Software Interface (API)Plug and Play

ALWI ONST asked for similar flexibility


Slide 11

NATO Unclassified


Problems with PC Architecture for ALWI-CI

• No standard platform architecture can be assumed across NATO

– Solution is Platform Independent Model

• Hard performance requirements:

– Safety

– Continuous system availability

– Deadlines (hard real-time)

• Challenging resource constraints

– Processor throughput

– Memory

– Communications bandwidth

Design-time integration with

Platform Specific Model


Slide 12

NATO Unclassified


Model Driven Architecture (Platform Independent)

Printer_driver_model.XMI

Printer_data.XMLPrinter_data.XML

Network PrinterDesk Printer

Abstraction

UNIX Architecture PC Architecture PDA

Platform Independent Model (PIM)

Platform Specific Implementation



Transformation Transformation


Slide 13

NATO Unclassified


ALWI-CI Concept:

MDA Applied to Common Store Control Service

Store_control_model.XMI

Platform Independent Model (PIM)




Store_data.XMLStore_data.XML

Transformation Transformation

Abstraction


Slide 14

NATO Unclassified


ALWI-CI Concept:

Software Principal Class Packages (PIM)

Loading NewWeapon

Store Configuration

Network CentricOperations

Mission Services

Weapon Control

Implemented by

ServiceRegistration &

Discovery

Implemented by

Employ Weapon

Implemented by


Slide 15

NATO Unclassified


ALWI-CI Concept:

Compatible with UAI Instance

UAI Compliant Aircraft

UAI Compliant Store

MIL-STD-1760 AEIS

Avionics

System

Mission Data

OtherUAI Configuration

Data Files

Work Station

UAI Compliant

JMPS

12

LAR Coefficients

GPS Receiver

Configuration Data

UAI Message Set

MiDEF Mission Data

Data Storage

System

Loading NewWeapon

Store Configuration


Mission Services

Weapon Control

Implemented by

Service

Registration & Discovery

Implemented by

Employ Weapon

Implemented by


Slide 16

NATO Unclassified


ALWI-CI Concept:

MDA PIM to PSI Transformation

PIM

of aircraft

system

Platform

Specific

Model

Source

Code

Mapping Mapping

Transformation

tool

Transformation

tool

ALWI-CIservice

component

Aircraftspecific

component

PIM to PSI transformation

Rapid verification of

performance & resources


Slide 17

NATO Unclassified


PSM

ALWI-CIservice

component

PIM

ALWI-CI Concept:

Weapon Integration Steps

Source

Code

Mapping Mapping

Transformation

tool

Transformation

tool

Aircraftspecific

component


xUML

Editor/Analyzer

AADL

Editor/Analyzer

Step 1: MDA tool environment

Step 2: MDA models

Step 3: Integrating weapons in spin-out

PnP store data

PnP load-out configuration data

Capability Spin-Outs


Slide 18

NATO Unclassified


ALWI-CI Concept:

NNEC Compatibility

PIM of

Client NC3

system

PIM

of aircraft

system A

PSM BSource

Code

Mapping Mapping

Transformation

tool

Transformation

tool

PSM ASource

Code

Mapping Mapping

Transformation

tool

Transformation

tool

inte

ropera

bili

ty

inte

ropera

bili

ty

Transformation for NEC infrastructure A

Transformation for NEC infrastructure B

inte

ropera

bili

ty


Slide 19

NATO Unclassified


Team 1:

Standards Planning

Loading NewWeapon

Store Configuration


Mission Services

Weapon Control

Implemented by

ServiceRegistration &

Discovery

Implemented by

Employ Weapon

Implemented by

Aircraft

Weapon

AEIS

Avionics

External Node(Service Client)

Post Launch

Data Link

Post Launch

Data Link

Data Link

External Node(Broker)

Data Link

Data Link

NC3Workstation

NC3

Terminal

1

3

265

4

Interface Standards (Protocols)

ALWI Services

Modeling Standards


Slide 20

NATO Unclassified


Volume 1: Technical Architecture

• Proposal for SAE Aerospace Standard

– Technical Cooperation Agreement with NSA (AOTWG)

• Contents

– Technical Reference Model

• NNEC compatibility

– Recommended Interface Standards (e.g. UAI)

– Recommended Service Standards (Plug and Play)

– Recommended Modeling Standards

– DoDAF view


Slide 21

NATO Unclassified


Team 2:

Common Store Control Service (PIM)

Loading NewWeapon

Store Configuration

Network Centric

Operations

Mission Services

Weapon Control

Implemented by

Service

Registration &

Discovery

Implemented by

Employ Weapon

Implemented by

CommunicationsStation

Services

Weapon

Software

Communications

Store Control Service

OSI Service Station Services

Weapon

IC

D

Payload Configuration

Weapon

Aircraft Mission


Slide 22

NATO Unclassified


Volume 2: API Methodology

• Layered domain architecture (previous slide)

• Recommendation to use Executable UML (xUML)

• Preliminary domain models with configurability using data classes

• Plug-in architecture for unforeseen weapon functions

• e.g. photon torpedo


Slide 23

NATO Unclassified


Team 3:

Universal Aircraft/Store Interface Concepts

Aircraft Planning Component

Platform

MethodsCDFs

Platform

Routes

Common Component

Common

Data Types

Common

Interfaces

Mission Planning System

Framework Store Planning Component #1

Store

MethodsMission

Data

Set

Store

Plan

Store Planning Component #2

Store

MethodsMission

Data

Set

Store

Plan

Data Transfer

Device

UAI interfaces

UAI Compliant Aircraft

UAI Compliant Store

MIL-STD-1760 AEIS

Avionics

System

Mission Data

Other

UAI Configuration

Data Files

Work Station

UAI Compliant

JMPS

12

LAR Coefficients

GPS Receiver

Configuration Data

UAI Message Set

MiDEF Mission Data

Data Storage

System

• Common Platform/Store ICD

• Configuration Data Set for each integration

• Common LAR Approach

• Mission Planning Interfaces

• Processes and tools


Slide 24

NATO Unclassified


Volume 3: Universal Aircraft Store Interface

Concepts

• UAI is only known applicable concept

• Recommend development of NATO Armament Interface (NAI)

– using UAI as start

• Will require release of UAI documents to NATO


Slide 25

NATO Unclassified


AADL

SysML

Physical

Component

Physical System Model

Embedded Software System

Execution

Platform

Embedded

Application

Software

DoDAFSystem Views

Team 4:

Aircraft Specific Implementations

Based on SAE AS5506

Architecture Analysis and Design Language (AADL)


Slide 26

NATO Unclassified


Team 4:

ASAAC Case Study

SystemManagement

Application Layer

Operating System Layer

Module Support Layer

APOS

MOS

ApplicationsApplicationManager

Generic

SystemManager

Operating

SystemRuntime

Blueprints

Mapping to ASAAC IMA

and AADL analysis

PnP store data

PnP load-out

configuration data


Slide 27

NATO Unclassified


PSM

ALWI-CIservice

component

PIM

Team 4:

Certification

Source

Code

Mapping Mapping

Transformation

tool

Transformation

tool

Aircraftspecific

component


xUML

Editor/Analyzer

AADL

Editor/Analyzer

PnP store data

PnP load-out

config. data

Tradition Software

Certification Focuses Here

ValidationValidation

Incremental

Verification

Incremental

Verification


Slide 28

NATO Unclassified


Team 4:

Lifecycle Costs

Aircraft Software

Airframe IntegrationMission Planning Software

System Engineering

Integration & Test

Miscellaneous

a b c d e f

a b c d e f

c

d e f

a b

d e f

Analysis

Analysis

Design Coding Integration Testing Programme Mgt

Design Coding

Integration Testing Programme Mgt

Duplicate Effort

Common Effort (PIM)

System A

System B

System A

System B

Conventional Software Development Lifecycle Cost

MDA Development Cost

• Common Effort (PIM)

• Initial Development Productivity

• Subsequent data-driven integration


Slide 29

NATO Unclassified


Volume 4: Plug and Play Implementation

• Feasibility of PIM to PSI transformation using AADL

– Safety

– Real-time performance

– Continuous software availability

• Grid computing compatibility confirmed (ASAAC case study)

– But concept does not depend on this

• Certification addressed

– But requirements continue to be platform-specific

• Lifecycle costs addressed

– MDA has demonstrated benefits on other programs


Slide 30

NATO Unclassified


NATO Project Demonstrations (NPD)

• NAI

– Short term: UAI demo to demonstrate early feasibility

– Medium term: Validation of NAI specifications in reference system

• Common Store Control Service

– Short term: Refinement of SG-97 PIMs and feasibility demonstration

– Medium term: Validation of PIMs in reference system


Slide 31

NATO Unclassified


US UAI Compliant Aircraft

Non-US Weapon

MIL-STD-1760 AEIS

Avionics

System

Mission Data

UAI ConfigurationData Files

Work Station

UAI Compliant

JMPS

12

LAR Coefficients

GPS ReceiverConfiguration Data

UAI Message Set

MiDEF Mission Data

Data Storage

System

NAI NPD

Weapon Interest

Diehl-BGT Defence

MBDA

Sagem

SIL Interest

Boeing

LM Aero

Support Interest

Raytheon

Sverdrup


Slide 32

NATO Unclassified


Common Store Control Service NPD

Weapon Interest

DBD

MBDA

Sagem

WINTEC, Inc.

Modeling Interest

Sagem, Dassault

DBD, EADS, ESG, IABG

GTD

KC, BAE Systems, MBDA

GDAIS, WINTEC, Inc.

SIL Interest

EADS

BAE Systems

GDAIS


Slide 33

NATO Unclassified


Ongoing programs that could be leveraged

• Model Driven Weapon Integration

– GDAIS program with AFRL to develop xUML model of UAI weapon control

domain and demonstrate software in reference system. Collaboration with

WINTEC, Inc.

• Builds on AFRL programs since 2001

• Demonstration available in summer 2007

• POC: Douglas Gregory, GDAIS

• German Industry (DBD, EADS, ESG, IABG)

– IMA Weapon-integration Demonstration (IWiD) program based on ASAAC

platform and ALWI-CI study.

• Offer submitted to BWB T5.2

• 3-4 year duration

• POC: Reinhold Mahler, IABG


Slide 34

NATO Unclassified


Recommended NATO Actions – 1 of 3

Technical Architecture

• It is recommended that NATO tasks the AS-1 Committee with the generation and maintenance of an Aerospace Standard for the ALWI Technical Architecture that is based on the material in Volume 1. This task should be undertaken in collaboration with the NSA AOTWG.


Slide 35

NATO Unclassified



NATO Armament Interface• If it is determined that a NATO Armament Interface (NAI) initiative should be

started, it is recommended that:

1. NATO moves forward with the short term NATO Project Demonstration, i.e. modification of a non-US weapon to UAI requirements, and then integration of that weapon with a UAI-compliant US aircraft/JMPS system to prove out the UAI concept in a NATO environment;

2. NATO requests that the UAI documents be released to NATO industry to form the basis for the NAI initiative;

3. NATO contracts with the appropriate industry leaders to develop documentation to define the NAI.

• Execution of the NPD can identify issues that need to be addressed by the development of NAI. If NATO proceeds with NAI, consideration may also be given to the recommended medium term NATO Project Demonstration, i.e. validation of the draft NAI interface control documents to support the interoperability effort.

• The mechanics of any NAI initiative would need to be addressed at the government level.


Slide 36

NATO Unclassified



Common Store Control Service• If it is decided to proceed with a Common Store Control Service, it is

recommended that:

1. NATO moves forward with the short term NATO Project Demonstration, i.e. validation of a prototype platform-independent model in two implementations. There is industry interest in supporting such a demonstration, and existing national programmes may be leveraged.

2. Based on the findings of this demonstration, NATO proceeds through a funded programme to develop and maintain plug and play interoperability models for weapons using the MDA concepts described in this final report.

3. If it is determined that this should be done, consideration may be given to the medium term NATO Project Demonstration, i.e. validation of full

interoperability models to support the programme..


Slide 37

NATO Unclassified


NIAG Subgroup 97In collaboration with SAE Aerospace AS-1

Aircraft, Launcher & Weapon Interoperability

Common Interfaces

Questions

aircraft, launcher & weapon interoperability common...

Documents