Nessun titolo diapositiva -...

Distribution Statement A: Approved for public release; distribution is unlimited (2 DEC 09)1

IDLS 2009

Present and Future of MIDS-LVT

Platform Integration, Terminal Modifications

and Future Enhancement Options

Alfonso Zamorano, Ph.D. (COL Spanish Army)Roberto Sabatini, Ph.D. (MAJ Italian Air Force)

Luc Aulanier (CDR French Navy)

Manuel Martinez, Ph.D. (CDR Spanish Navy)

Henning Rutz (LTC German Air Force)

Laurie Foreman (United States Department of Defense)

Ben Pour (United States Department of Defense)

Samantha Snow (United States Department of Defense)

MIDS International Program Office

33050 Nixie Way, Bldg 17A, Suite 416

San Diego, CA 92147-5110


• Introduction – MIDS Program Overview

– MIDS Family of Terminals and Production Lines

– MIDS-LVT Hardware and Software Components

• MIDS-LVT Platform Integration Programs– Platform Integration Requirements

– LINK-16 Interoperability Issues

• MIDS-LVT Upgrade Activities– Mandated Modifications (U.S. DoD/DoT)

– Optional Modifications

• Conclusions

SCOPE


MIDS International Program Organization

STEERING

COMMITTEE

PROGRAM MANAGER – U.S.

DEPUTY PROGRAM MANAGER - FR

MATRIXSUPPORT

HOST/NATION

Programmatic

Authority

Execution/Management

MIDS - IPO

Administrative

TECHNICAL DIV

IT

THIRD PARTY SALES DIV

U.S.

ACQUISITION MGMT DIV

U.S.

PLATFORM REQUIREMENTS

LOGISTIC DIVSP

CONFIG. CONTROL &

DATA MGMT DIVGE

Distribution Statement A: Approved for public release; distribution is unlimited (2 DEC 09)

Program Phases

I II III IVI II III IV

USAF LEAD/ 8 NATO NATIONS

JTIDS CL 2 P 3 I

PMOU AND SUPPLEMENT 1

5 NATIONS

U.S. HOST NATION

USN LEAD

ORGANIZE EMD

COEA

PMOU/ SUPPLEMENT 2

TERMINAL DEVELOPMENT AND QUALIFICATION

INITIAL PLATFORM INTEGRATION

ORGANIZE PRODUCTION

PMOU/SUPPLEMENT 3

PLATFORM INTEGRATION AND TESTS IN PROGRESS

PMOU/SUPPLEMENT 3 Extension

I II III IV

2000thru

2009

PROJECT

DEFINITION

PRE-EMD EMD PRODUCTION

AND SUPPORT

1994thru

2000

1990thru

1993

1987thru

1990


MIDS-LVT Family of Terminals

MIDS-LVT(2) Terminal• Full MIDS LVT Compatibility

• Ethernet/ADDSI X.25 Interfaces

• Unique Cooling Unit and PS Added

MIDS-LVT(3) Terminal • Fighter Data Link (FDL) Terminal

• FDL MIL-STD 1553 Interface

• MIDS-LVT Commonality

• Growth Allocation for Fighters

MIDS-LVT(1) Terminal• Open and Modular Design

• SEM-E Cards/VME Bus

• TADIL J/IJMS

• 3910/1553/Ethernet/X.25 Interfaces

• Voice and TACAN


MIDS-LVT Production Lines

• Two Production Lines in the U.S.

• One Production Line in Europe

– THALES

– SELEX COMMS

– EADS

– INDRA


MIDS-LVT(1) Hardware Components

• Remote Power Supply– All Platforms except EF2000

• Ancillary LRUs– DC Adapter, AC Adapter, High Power Amplifier

Interface Assembly (HIA)

• Main Terminal SRUs– Chassis

– Power Amplifier (PA)

– Exciter/IPF (Interference Protection Feature)

– Receiver Synthesizer (R/S, 2 per terminal)

– Signal Processor/Message Processor (SMP)

– TACAN (optional)

– Voice (optional)

– Data Processor/Avionics Multiplexer (DP/A MUX)

– Tailored Processor/Ground Multiplexer (TP/G MUX)

– Receiver-Transmitter Interface (RTI)/DiscreteC

on

trol

Inverte

r

Pre

am

p/D

river F

inals

Excite

r / IPF

TA

CA

N

RC

VR

/ Syn

th

RC

VR

/ Syn

th

SP

/ MP

Vo

ice

Dis

cre

tes

DP

TP

RT

I

Mu

xes

X.2

5 M

ux


MIDS-LVT (1) Software Components

CSCI: Computer Software Configuration ItemC

on

trol

Inverte

r

Pre

am

p/D

river F

inals

Excite

r / IPF

TA

CA

N

RC

VR

/ Syn

th

RC

VR

/ Syn

th

SP

/ MP

Vo

ice

Dis

cre

tes

DP

TP

RT

I

Mu

xes

X.2

5 M

ux

Closely tied to hardware implementations

TACAN CSCI

SMP CSCI

Voice CSCI

Core CSCI - Performs LINK-16 message processing

functions, including navigation, synchronization, and system time maintenance;

- Executed on a Motorola 68040;

- Written in FORTRAN;

- Consists of the Run-Time Executive, Virtual Controller and three CSCIs

Tailored I/O CSCI

– Performs host interface processing functions, including message filtering, VMF, connectivity processing, route establishment;

– Consists of three CSCIs executed on separate processors:

• TIO - Motorola 68040, Ada (using Alsys Ada Run Time Kernel)

• Avionics MUX - Motorola 68332

• Ground MUX - Motorola 68360


MIDS-LVT INTEGRATION PROGRAMS


U.S. PROGRAMS• AIR FORCE: F-15, F-16, ABL, B-1, B-2, B-52, etc.

• NAVY: F/A-18, EA-6B, Aircraft Carriers, Cruisers

• ARMY: PATRIOT Info Coord./Command Post (ICC/BCP), Air Defence Platforms, etc.

FRA PROGRAMS• AIR FORCE: RAFALE, MIRAGE 2000-5/D, Air Force C2 System (SCCOA)

• NAVY: HORIZON and FREMM Frigates

• ARMY: MIDS-Terre (Martha C2S, SAMP/T Missile, etc.)

ITA PROGRAMS• AIR FORCE: TYPHOON, TORNADO IDS/ECR, Mobile C2 (C2M), etc.

• NAVY: HORIZON and FREMM Frigates, “Cavour” Aircarft Carrier, etc.

• ARMY: SAMP/T Missile, A-129 “Mangusta”, etc.

DEU PROGRAMS• AIR FORCE: TYPHOON, TORNADO, SAMOC SAM Operations Centre

• NAVY: F123 and F122 Frigates, K130 Corvette, F125, etc.

ESP PROGRAMS• AIR FORCE: TYPHOON, F-18, SIMCA Integrated C2, A400

• NAVY: F-100 Frigates, LPD/LHD (Amphibious Transport Dock/Assault) Ships, etc.

MIDS-LVT Integration Programs


MULTI-NATIONAL PROGRAMS


EF TyphoonEF Typhoon

FREMMFREMM

AA--400400

SAMP/TSAMP/T

HorizonHorizon

EHEH--101101



PLATFORM REQUIREMENTS

Format & Functions

Data Fusion Requirements

HW Requirements

BUS Management

Navigation Requirements

EW Requirements

TACAN Requirements

Free Text &

Voice Management

I

N

T

E

G

R

A

T

I

O

N

ICD

Interoperability

Evaluation

MIDS-LVT

Interface

Requirements

Platform

Electronics

Systems

Link 16

Requirements



LINK-16 INTEROPERABILITY

The Interoperability Evaluation (IOE) of a group of platforms

(Platforms Under Evaluation - PUEs) is performed at different levels:

• Interface Exchange Requirements (IER) – Highest level of

interoperability evaluation. Functional area implementation evaluation.

• System Implementation Document (SID) – Detailing which messages,

message fields and message field values will be transmitted by the platform and

which will be received and processed by the platform.

• Interoperability Matrix (IOM) – Matrix description comprising answers to

platform capability questions (LINK-16 features) that are supplemented by

rationales. Any interoperability issues discovered as a result of this analysis will

be evaluated against the LINK-16 operational requirements of the PUE.

• Platform Implementation Difference Document (PIDD) – Involves the

procedural aspects of LINK-16 implementation. Defines the LINK-16

implementation in terms of difference versus an implementation standard (such

as the MIL-STD-6016C, STANAG 5516, or National MIDS Interface Requirements

Specifications). This greatly enhances and complements the results of the

previous phases (IER, SID, IOM).



LESSONS LEARNED – AIR PLATFORMS

• Aircraft are challenged by multipath and extreme environmental

conditions

• Very demanding Electro Magnetic Interference (EMI)

requirements, as well as strict cooling and vibration

requirements

• Aircraft require TACAN, which is often a very demanding

platform integration task (e.g., F/A-18)

• Important lessons learned from past integration tasks would be

to develop a simulator/test-equipment that closely approximates

the actual operational flight environment so that the design and

test results seen during the development phase would better

match the actual live test performance

• Also, performing flight testing in parallel with development work

as soon as the HW is assessed air worthy can reduce a

significant amount of rework later



LESSONS LEARNED – GROUND PLATFORMS

• Ground operations show a wide range of applications

• Ground terminals are often being used in extreme heat

conditions and in close proximity in confined shelters

• Requirements to reduce the noise of the cooling units to meet

the safe decibel level specifications, while maintaining sufficient

cooling for 120º F climates. Other systems are being used in

Alaska in extremely cold conditions

• Issues of battery life and remote rekeying

• Some users preferred to use LVT(1) also for commonality

reasons and in these cases they addressed specific functional

and environmental issues (i.e., power supply, cooling,

vibrations, etc.) at the host level with suitable support devices

• The U.S. Army preferred to develop the ad-hoc variants

LVT(2)/(11), incorporating specific cooling and power supply

units into the terminals



LESSONS LEARNED – MARINE PLATFORMS

• Navy ships MIDS-LVT often operate in a high power

configuration

• Should avoid RF interference with other on-board equipment in

the same band

• They are also subjected to strong vibrations

• Their navigation requirements are typically different from

aircraft applications, mainly due to the different dynamic

conditions

• Different characteristics of the on board navigation sensors

(various architectures are possible for MIDS relative navigation

data processing)

• Recent efforts aimed at developing platform interfaces for low

dynamics platforms (the terminal introduced two new host

interface types for platforms using either MIL-STD-1553 or

Ethernet)



LESSONS LEARNED - MANAGEMENT

• The management process for Systems Engineering and

Integration (SE&I) activities established at the MIDS IPO with a

Platform Representative assigned from each MIDS nation and

the adoption of a Problem Tracking Data Base (PTDB) for

correcting all deficiencies found during the platform integration

activities, has been an excellent solution for reducing platform

integration technical risks and costs

• The approach of having the Government Furnished Software

divided in two sets (Core and TIO software) guarantee that a

common software is maintained for all MIDS-LVT versions and

allows for the introduction of new interfaces and operational

capabilities when these are required by the platforms, often by

modifying the TIO software only. This contributes to a

significant reduction of the MIDS lifecycle costs


THE FUTURE OF MIDS-LVT


MIDS-LVT Upgrades

– Throughput (Data-rate)– Flexibility and Integrity– Security– Conflicts with radio-navigation systems

Mandated modifications (FAA/NSA) and optional enhancements to

improve:

Allowing the optimal use of LINK-16 in net-centric operations


• Frequency Remapping (FR): remapping 14 (band 969-1008 MHz) of the 51 available frequencies.

• Information Assurance (IA) Modernization (IAM): introduces a new family of programmable IA modules in line with recent U.S. DoD regulations in this domain.

M

A

N

D

AT

E

S

• LINK-16 Enhanced Throughput (LET): Link 16 data-rates greater that the current 115 Mbps (up to 1.1 Mbps).

• Concurrent Multi-Netting (CMN): allows reception of various networks (up to 4 contemporarily)

• Extended 1553 (E1553): allows bus data-rates greater than 102

Mbps without rewiring of the platforms

O

P

T

I

O

N

S

MIDS-LVT Upgrades


Mandate #1: Frequency Remapping – DoD/DoT

Memorandum of Agreement (MOA), 2002

MIDS-LVT Upgrades


FREQUENCY REMAPPING

969 MHz 1008 1053 1065 1113 1206

IFF IFF

Example: The MIDS terminal reallocates the frequencies

1-14 (969-1008 MHz) to 14 other frequencies in the

bands 1053-1065 MHz and 1113-1206 MHz. The

distribution is uniform over the 37 available frequencies.

MIDS

The remapping algorithm is described in the document DoD Reg. 4650.1-R1, Appendix 2 (DTIC web site).

MIDS-LVT Upgrades


Mandate #1: Frequency Remapping (FR)

Technical and Operational Aspects

• Modification of MIDS-LVT teminal: HW and SW

• No modifications required on the platforms

• The terminals modified will only be partially interoperable and compatible with the unmodified terminals. The unmodified terminals will be able to receive data from those modified, while the modified terminals will not be able to receive the data transmitted at all frequencies by the unmodified terminals (possible data loss)

MIDS-LVT Upgrades


Mandate #2: IA Modernization (IAM)

• Substitution of the IA Module in accordance with the recent NSA

regulations, in order to improve security and interoperability

with the DoD Key Management Infrastructure (KMI)

• Some IAM chips have been already developed for the U.S. DoD

but not customized specifically for the MIDS-LVT terminal

MIDS-LVT Upgrades


Mandate #2: IA Modernization (IAM)

Tecnical and Operational Aspects

• Modifications of the MIDS-LVT terminal: HW and SW

• No modifications necessary on platforms

• Necessary to customize the IAM chips (non-recurring activity) for MIDS-LVT. The activity will start in 2010 and will be followed by the terminal integration. IOC estimated for 2014

• The modified terminals will not be interoperable or compatible with the unmodified terminals, although in theory they could communicate with these terminals using the old algorithms (degraded security)

• The U.S. DoD expects the release of IAM ICD to the other MIDS nations, allowing EuroMIDS to design the new SMP

MIDS-LVT Upgrades


LINK-16 Enhanced Throughput (LET)

• LET will permit increased data-rate up to 1.1 Mbps, using different coding algorithms

• Greater data flow and more information available for multiple applications (e.g., Video, Images, Geo-referencing, Weaponry and better Situational Awarness)

• The LET capacity has been already demonstrated and prototyped in the U.S.

MIDS-LVT Upgrades


LINK-16 Enhanced Throughput (LET)


• MIDS-LVT Terminal Modifications: HW and SW

• Necessary to modify the platforms in order to use the highest data-rate (1.1 Mbps) – Data connection, rewiring, Operational Flight Program (OFP)

• The terminals modified with LET will be compatible with those not modified when communicating at 115 kbps but will not be interoperable when using the higher data-rates

• The current 1553 interface is not usable above 230 kbps. Therefore, it is necessary to use the Ethernet interface (available in the terminal) or the Extended 1553 bus (now under development in U.S./Canada)

MIDS-LVT Upgrades


Concurrent Multi-Netting (CMN)

Concurrent Multi-Netting (CMN) is an investigation into the feasibility of modifying Link 16 terminals to receive concurrently on multiple nets

• In a time slot

terminal can

transmit or

receive - not both

• Terminal

restricted to one

net each time slot

• 1536 time slots

per 12 seconds

(each net)

• 127 nets (one net

number reserved)

Terminal still

restricted to

transmit on one

net each time

slot; but receives

on “n” (2-4) nets

each time slot.

1 2 3 4 5 6

JIT

TE

R

SY

NC

MESSAGE PROPAGATION

7

127

0

NE

TS

TIME SLOTS 7.8125

msec

TIME SLOT

MIDS-LVT Upgrades


• CMN increases the collaboration between various LINK-16 networks with consequent improvement of the situational awareness

• The CMN capability is partcularly suited for air platforms with Command and Control (C2) functions and, secondarily, for multirole aircrafts (e.g., F/A-18)

• The CMN technology was only partially developed and has been demonstrated as stand-alone capacity


C2 Net

ISR net

Battle Force SA Net

Targeting/Weapons Net

MIDS-LVT Upgrades




• Significant platform integration effort (filters/antennae connections)

• Significant terminal modifications: HW and SW

• The required terminal modifications include SMP, RCVR Synthesizers, TP/GMux and Software

• The compatibility of CMN with CM still needs to be demonstrated technically (switching capacity between different networks with different IA keys)

• A possible alternative to the development of CMN in the MIDS-LVT terminal is the use of multiple terminals on platforms where this is possible (e.g., C2 with large avionics bays). In this case, however, the platformn integration impacts are very significant due to the greater volumes, cooling/power requirements, installation and connections with antennae

MIDS-LVT Upgrades


Extended 1553 (E1553)

• E1553 uses the same 1553 wiring already installed on the aircrafts, maximizing the use of the cable bandwidth, in parallel and without interferences with the structure and the functionalities of the 1553 bus already existing

• The 1553 technology is still uner developement (Canada/U.S.) and a new military stadard is beeing drafted

• Some experiments made by the U.S. Air Force (Wright Patterson Labs.) have confirmed the validity of the new technology

• E1553 will allow data-rate greater than 100 Mbps, satisfying LET requirements (up to 1.1 Mbps), with significant margins for further developments

MIDS-LVT Upgrades


Extended 1553 (E1553)


• MIDS-LVT modifications are necessary: HW and SW

• Possible modifications in the platforms to make use of the higher data-rates (already expected for LET)

• Necessary to modify all interface cards of avionics systems using the E1553 (the interfaces bus-controller/remote-terminal of the avionics systems using the traditional 1553 will stay unchanged)

• The E1553 bus-controller functions can be allocated to any avionics terminal connected to the bus or to MIDS-LVT

• The industrial joint venture U.S./Canada/UK will develop the new standard (non-recurring engineering and testing efforts will be funded by U.S./Canada governments) in the period 2010-2012. If the tests will be successfull, other european/extra-european partners can be involved in the production phase

MIDS-LVT Upgrades


LVT(1) Terminal Modifications*

CM/FR, LET

LET via Ethernet

LET via E1553

Con

trol

Inverter

Pream

p/D

river

Fin

als

Exciter / IP

F

TA

CA

N

RC

VR

/ Syn

th

RC

VR

/ Syn

th

SM

P

Voice

Discretes

DP

Mu

xes

TP

X.2

5 M

ux

TP/GMUXSMP

10 Base T ConnectorR

T

I

DP/AMUX

*CMN modifications not shown

MIDS-LVT Upgrades


Further possibility of enhancement studied in the past but currently not under development/study for integration in MIDS-LVT terminals:

Other Enhancement Options

• S-TADIL J/Joint Range Extension Application Protocol (JREAP):

LINK-16 messages forwarded throughout the operational theater using satellites and other long-haul media.

• Flexible Access Secure Transfer (FAST):

- An alternative method to access the network (switchable mode) in

addition to TDMA

- Allows on-demand access to the network, with greater capacity and

reduced latency

- Allows point-to-point messaging for net-centric operations

- Solves most of the existing operational limitations of LINK-16:1. Reduced number of time-slots

2. Use of time-slot limited to transmission or reception

3. Latency in the access to the time-slots in a rigid network

4. Absence of emergency time-slots

5. Non IP friendly/capable protocol


CONCLUSIONS

• MIDS-LVT is an advanced C4I system providing highly effective and mission critical Link 16 network capabilities (wide-area and jamming-resistant TDMA communications)

• In addition to performing C4I functions, MIDS-LVT serves as a secondary navigation source by providing relative navigation position-keeping functions through the use of Link 16 PPLI and incorporates TACAN functionalities

• The reduced size and weight of the MIDS-LVT terminal have allowed integration on numerous U.S., French, Italian, Germany and Spanish platforms, and also on a great variety of 3PS nations and NATO agencies platforms

• Although all platform integration activities have their own peculiarities, we have identified some general guidelines (integration best practice) and important lessons learned, applicable to the majority of cases, which could assist for optimal integration of MIDS-LVT on many different types of platforms and support Link 16 interoperability evaluations


CONCLUSIONS (cont.)

• The strategy of establishing a Transatlantic International Cooperation (TIC) program, between a significant group of NATO nations (USA, France, Italy, Germany and Spain), for developing and producing the MIDS-LVT terminals has been a great success, fostering a model of TIC which is well harmonized with the dynamics of a competitive defense market

• These factors have allowed a large number of 3PS nations and NATO Agencies to procure MIDS-LVT terminals, giving their contributions to the MIDS IPO SE&I process and obtaining access to MIDS terminal technical and operational support services (block cycle releases, problem reporting, logistics support and other services)

• All these elements are an excellent foundation for further international cooperation activities, and constitute essential building blocks of current and likely future Network Centric Allied and Coalition Operations


Alfonso Zamorano, Ph.D. (COL Spanish Army)Roberto Sabatini, Ph.D. (MAJ Italian Air Force)

Luc Aulanier (CDR French Navy)

Manuel Martinez, Ph.D. (CDR Spanish Navy)

Ben Pour (United States Department of Defense)

Henning Rutz (LTC German Air Force)

Laurie Foreman (United States Department of Defense)

Samantha Snow (United States Department of Defense)

MIDS International Program Office

33050 Nixie Way, Bldg 17A, Suite 416

San Diego, CA 92147-5110

Tel. +1 619 524 1492

Contact email: [email protected]

IDLS 2009

mailto:[email protected]

Nessun titolo diapositiva -...

Documents

Transcript of Nessun titolo diapositiva -...