link 22 integration needs overview lockheed martin proprietary information lockheed martin australia...
TRANSCRIPT
1
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
MILCIS 2013 Canberra
Link 22 Integration Needs Overview
Presented by: Jason Longdon (Lockheed Martin Australia Limited)
Telephone: +61 (0) 400 858 253
Fax: +61 (0) 2 6211 3799
Email: [email protected]
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
2
Presentation Outline
Introduction
ADF Operational Context
Link 22 Sub-System Functional Overview
Link 22 Integration Activities
Link 22 Generic Issues
Link 22 Extant Products/Development
Link 22 CIWG Advert
TIE IO Link 22 Trial
2
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
3
Introduction
• Purpose
To Introduce Link 22 in the Australian Context
To introduce the principles of Tactical Data Link Integration, within the context of Link 22
To provide Integrators and Users with a Functional Overview
Introduce the Existing and Future “Electronic Boxes” that implement the Link 22 functionality
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
4
• ADF Beyond Line Of Sight (BLOS) Need
Identified by ADF TIE IO BLOS Study
Reinforced by AUSCANNZUKUS C4 Committee - L11 has endured for over 50 years
- Significant vulnerabilities in the L11 architecture - Mounting crypto equipment and terminal sustainment issues lead to significant negative impact on the Allied BLOS TDL capability - AUS and NZL have dispersed mobile and deployed joint forces that lack the persistent 24/7 airborne assets required to affect Link 16 (RF) LOS relay - Need viable BLOS TDL capability where satellite access is limited or denied. - Of replacement TDL Options available, only L22 (HF) can provide a persistent J-series compliant BLOS TDL capability
ADF Operational Need
* Information from April 2010 CCIB Presentation
3
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
IU01 Radar Surveillance
Range
IU 02 Radar Surveillance Range
IU 01
IU 02 (Radar Picket, Surf Attack Unit,
Third Party Targeting Unit or
Indep’t Ops – Airspace Mgt)
IU 10
HQ = No Sensors
Receives all network participants
( IUs) and all their tracks
(Receive, Plot and Update)
Common Tracking Zone
MUST be IAW Reporting
Responsibility & Correlation
Rules / Tolerances set by Mil-Std 6016
Reach-Back/Forward (Globally)
(One Deployed C2 unit assigned within TG
to reach back to fixed site
One way Transmission / Broadcast)
No Higher Latency
Could use IP / COP connection
Intra-Zone Via SATCOM Exchanging Common Tracks, must follow
rules
Both IU active on Satcom Link
Increased Latency, Subject to Satcom
availability
i.e 300 NM
i.e 300 NM
Typical HF TDL (> 300NM) or
Airborne Link 16 Relay, if available
Typical Ops >25NM to 60Nm and
Greater
Low Latency for Third Party Targeting
RF must be tactically employed
and available 24/7 = Persistent
TN 01001
TN 02000
Radar contact held only by IU 01
and reported as Remote Track
to all participants
i.e 300 NM
512 NM
Broadcast
(i.e. JREAP
to exchange
J-series Messages)
Approx 250 millisecond delay
National TDL (Connects all Tactical Sites, Sensors,
Exercise Areas and Weapon Ranges
Together)
MEZ
Inter/Intra-Zone Via HF
Common Tracks
Low Latency
Persistent
NATIONAL WAN
MEZ
BLOS TDL HF • BLOS TDL Layers
ADF Operational Need
* Information from April 2010 CCIB Presentation
5
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
Link 16
CSG
CSG
Link 22
Coalition ships
Coalition Ships
Land
Link 22
Link 16
JREAP
Data
Forwarder
VMF
Coalition Ships
JREAP
JDNO & JICO
OP HQ
BLOS TDL HF
• MTN: Future Concepts
ADF Operational Need
* Information from April 2010 CCIB Presentation
4
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
7
• Potential Platforms
LHD
AWD
FFH
Naval Helicopters
Maritime Patrol Aircraft
Broad Air Maritime Surveillance
ADF Operational Need
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
8
• Key Issues
Require persistence BLOS coverage without airbourne relay
SATCOM IP routing coverage
IP network design
Self managing of networks
Operate in disparate and out of LOS locations
Point to Point BLOS
ADF Operational Need
5
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
9
Link 22 Introduction
• Link 22 History On A Page
Why
– NATO identified a need to replace Link 11
– Increasing TDL performance required
When
– Definition 1989 to 1992
– Build 1992 to 2002
– Maintain 2002 – ongoing (2013)
What
– Network control software, cryptographic equipment,
RF modem, interface definition and test environment
– Assistance with message standard & integration
How
– Project Management Office set up by 7 NILE Nations
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
Link 22 Introduction
• Link 22 In Comparison
Link 1 Link 11 Link 11B IJMS Link 16 Link 22
Bearer Landline Radio
HF/UHF Multi-Media
Radio
UHF
Radio
UHF
Radio
HF/UHF
Speed / bps 1,200 1,800 1,200 28,800 53,760
or greater
Between HF 1,484 & UHF 12,645
ECM Resistance N/A CLEW-None
SLEW-Limited
Bearer dependent
High High Medium
Encrypted No Yes Yes Yes Yes Yes
Strengths Air Data Sharing
Widely Fitted Full Duplex Air Control
Data Rate
Air Control Voice,
Imagery, Data
Granularity
Data Routing
TBLOS
Priority Interrupt
Weaknesses
Air Only
No Platform Data, Old
Nodal
Granularity
Gridlock
Granularity
Point-Point
Compatibility
Terminal Size
LOS
LOS
FCA
Management
Capacity
HF
10
6
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
11
Link 22 Introduction
• Link 22 Key Characteristics
Dynamic Time Division Multiple Access
Dynamic Congestion Management
Multi-Medium (RF)
Multi-Network
Routing and Relay
Mission Area Sub Networks
Late Network Entry
Dynamic Reconfiguration/Initialization
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
12
Link 22 Introduction
• Link 22 Technical Characteristics
Media Types: HF FF, HF EPM, UHF FF and UHF EPM
Coverage: Up to 1000 nmiles (with relay)
Jam Resistance: Signal Processing with Error Detection and Correction, Network Packet Encryption (COMSEC) and ECM resistance (TRANSEC)
System Error Resistance: Goal of BER in Order
of 1x10-4
Robustness: Good. Non-nodal, Relay Available,
Multiple Sub-Nets and Dynamic Route
Selection
Medium Access: Time Division Multiple Access,
Optionally Dynamic
7
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
13
Link 22 Introduction
• Link 22 Technical Characteristics
Throughput: HF FF: (QPSK max) 31 messages per
sec, (8PSK max) 45 messages per sec
UHF FF: Approx 150 messages per sec
(Assuming 10 users over a cycle of ten
seconds, equates to track update rate)
User Data Rate: HF FF: 1493 – 4053bps,
HF EPM: 500 – 2200bps
UHF FF: 12667bps,
UHF EPM: Classified
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
14
Link 22 Introduction
• Link 22 Technical Characteristics
Max No. of SN Participants: 125
Max No. NN of: 8 (in SN), 4 (per NU)
8
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
15
Link 22 Introduction
• Link 22 Misunderstandings
“Link 22 or Link 16!”
– Link 22 was designed to complement Link 16
– Link 22 offers the ability to “offload” communications
“You need new radios”
– Link 22 was specified to use and has been demonstrated against existing Link 11 radios
“Nobody is installing Link 22”
– There are installations operating on Italian, Danish and
French platforms
– Trials have been undertaken on Finnish and German platforms
“Link 22 is not interoperable with Link 16”
– Link 22 uses a majority of Link 16 messages as is
– Link 22 shares the same data dictionary
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
16
Link 22 Introduction
• Link 22 CONEMP and CONOPS Overview
Operational Functions
– Network Design, Network Initialisation
– Network Amendment
– NILE Network Roles
– Multi-Link Roles
User Roles
– Network Planning
– Network Management
– Tactical Information Exchange Functions
Multi-Link Integration
Radio Frequency Integration
9
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
17
Link 22 Introduction
• Link 22 Messaging
Contained within STANAG 5522
- Shares the J – Series family data dictionary
Labelled F and FJ Series
- F Series are a 72bit word Link 22 unique structure
- FJ Series are a 72bit word directly incorporating a J Series message structure
Operational Implementation
- Network Management
- Participation and Location Information
- Surveillance
- Electronic Warfare and Intelligence
- Underwater Warfare
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
18
Link 22 Introduction
• Link 22 Messaging (cont.)
Operational Implementation
- Information Management
- Weapons Control
- Weapons Co-ordination/Mission Management
- Control (Not Fighters) / Control Co-ordination
- Status
10
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
19
Link 22 Sub-System Functional Overview
• Link 22 System Components NILE COMMUNICATIONS EQUIPMENT (NCE)
CRYPTO
CRYPTO
CRYPTO
CRYPTO
LLC
TDS DLP SNC
SPC
SPC
SPC
SPC
T O D
RADIO
RADIO
RADIO
RADIO
Link 22
Test and Validation
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
20
Link 22 Sub-System Functional Overview
• Host/Tactical Data System
Provides the Tactical Information Interface
Generates Tactical Data for Transmission
Processes Tactical Data Received
Conducts Operational Functions
Provides Platform Dependent Human Computer Interface to the Tactical Data Link Information Exchange
Maintains and Manages Tactical Data
11
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
21
Link 22 Sub-System Functional Overview
• Data Link Processor (Super) Network Establishment
– Pre-Mission Planning
– DLP Initialization
– NCE Configuration
– SNC SN Directory configuration
– Crypto Key Initialization
– Network Initialization
(Super) Network Operations Management – (Super) Network Management Configuration – Tactical Message Congestion Management – Security Management – NCE Management
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
22
Link 22 Sub-System Functional Overview
• Data Link Processor Link 22 Message Management
– Track Reporting – Tactical Message Selection – Tactical Message Transmission – Tactical Message Reception – Tactical Message Translation – Tactical Message Quality of service
12
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
23
Link 22 Sub-System Functional Overview
• System Network Controller (SNC)
Message Delivery Service
– Tactical Message Communication
– Network Packet Communication
– Network Access Management
Management Services
– DLP Management
– Media and Cryptographic Management
– Network Management
– Congestion Management
• Link Level COMSEC (LLC)
Network Security
– Transmission Security
– Communications Security
– Data Verification
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
24
Link 22 Sub-System Functional Overview
• Signal Processing Controller Provide Network Packet Delivery Service on the Media
MODEM
Provide Error Detection & Correction (EDAC)
Media Fragmentation and Reassembly
Reception Quality Assessment
Data Link Layer Service (Optional)
HMI (Optional)
Radio Silence Management
• Radios
Inject Media Coding Frames onto Required Frequency Band Generates Waveform for Injection Radiate RF
13
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
25
Link 22 Sub-System Functional Overview
• Test and Integration
NILE Reference System – Multi-Link Test Tool (MLTT)
- Sub-System Simulation and Stimulation
- Validation of System Interfaces
- Scalable Integration of Sub-Systems
- Recording and Playback
- Scenario Creation and Application
- Multi-System Integration
- Analysis of Data and Information Exchange
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
26
Link 22 Integration Activities
Legend: Technical IO Procedural IO Operational IO
010110 010110
DLP +
NCE
DLP +
NCE
Box-to-Box
Operator Operator
Knowledge Knowledge
Display Display
System
Information Information
Host Host
Data Link
Data Data
Data Protocol & Integration
HCI Brain-to-Brain
RF
14
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
27
Link 22 Integration Activities
• Need Determination Operational Employment
– Roles and Responsibilities
– Operational Capabilities
– Information Exchange Requirements
– Single Link or Multi-Link
Host Environment Constraints
– New System, New Development, New Platform,
Legacy Systems, Legacy Platform
– Platform Types
Acquisition/Integration Approach
– Bespoke/COTS or both
– Total System or Elements
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
28
Link 22 Integration Activities
• Functional Partitioning
Tactical Data Handling
– Host/TDS and DLP Separations
– Information or Services
– Interoperability Planning
Network Management – Link 22 Network Management Aspects
– External Network Planning/Preparation
NILE Communications Equipment Constraints – Mandatory Needs
– Embeddable Options
15
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
29
Link 22 Integration Activities
• Functional Allocation Host - User Interfaces - Operational Functions – C2, Situational Awareness
Support System
- Network Management
DLP
- Tactical Message Handling
- Tactical Interface Functions
SNC Embedding
- Where to put the SNC software
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
30
Link 22 Integration Activities
• Functional Allocation (cont.) Cryptographic Equipment
- Fixed by NILE PMO
SPC Embedding
- Standalone or integrated
Radio
- Existing or new
16
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
31
Link 22 Integration Activities
• Interface Definition
Interface Control Document Generation
– Host/TDS and DLP Separations
– Information or Services
– Host to Host Tactical Message Exchange
Extant Interface Standards/Specifications
– DLP – FRS
– SNC IDD
– LLC IDD
– SPC IDD (All Media Types)
– Radio Standards
– ADatP-3 – OPTASK LINK
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
32
Link 22 Integration Activities
• Interface Definition (cont.)
Implementation Specific Standards
– Host to Host
– Host to DLP
– DLP to SNC
– Network Planning to DLP
17
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
33
Link 22 Integration Activities
• Interface Definition (cont.)
Link 22 SLIRS
SPC SS
National Implementation
LLC IDD, LLC IRS, LLC KMP
SNC Segment Specification
DLP Functional Requirement
Specification
IDD for DLP and SNC
National Implementation
Link 22 SLIRS
Link 22 Documents
Link Level COMSEC (LLC)
RADIO
Signal Processing
Controller (SPC)
System Network Controller
(SNC)
Data Link Processor
(DLP) STANAG 4610
This document should
incorporate Information
from NILE Communication
Equipment documents
It is NOT yet in issue, and may
never be issued, at least in the
immediate future.
Combat System /
Tactical Data System
NATO Standards Link 22 Systems
STANAGs 4539, 4205, 4285
STANAG 4444 STANAG 4372
STANAG 4538
Tactical Messages STANAG 5522
Operational Procedures ADatP 33
Data Forwarding (L11 & 16) STANAG 5616/MIL-STD 6020
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
NCE
34
Link 22 Integration Activities
HOST DLP SNC
LLC SPC RADIO Network(s)
SUT Emulated STD
Host Functions – DLP Interface
NCE
HOST DLP SNC
LLC SPC RADIO Network(s)
Host Functions – DLP Interface – STANAG 5522 Compliance
NCE
HOST DLP SNC
LLC SPC RADIO Network(s)
Full System Under Test – Emulated NILE Systems
18
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
35
Link 22 Integration Activities
HOST DLP SNC
NCE NILE
Network Other NILE
Systems
SUT Emulated STD
Full SUT into Emulated Network – with other L22 Systems
HOST DLP SNC
Interoperability Testing – STANAG 5522 Compliance - SIMPLE
Live Interoperability
NCE SIMPLE Network
Other NILE Systems
HOST DLP SNC
NCE RF
Network(s) Other NILE
Systems
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
36
Link 22 Integration Activities
• Interoperability Testing
NATO TDLITS Model
– Model Provides a Best Practice Approach to IO Testing
– Conducts Multi-Level Testing
Paper Based
Test Rig
Live Testing
– Tests at the Host/TDS Interface Level
National and International Exercises and Experiments
– Opportunity exercises
– Experimentation Activities
– Formal Capability Demonstrations of Equipment
– Formal Testing and Demonstrations
19
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
37
• Interoperability Management
Link 22 Integration Activities
- Interoperability Management
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
38
iSMART is a structured through project life cycle process
– Maximise the use of IO information available at each project
phase - ensuring early identification and resolution of IO
problems
– Requirements includes:
A Single TDL Authority
TDL Implementation and Testing Policies
Information Exchange Requirement Capture
Detailed TDL Standards
Detailed and Common Platform Specification Documents
Integration Development Testing & Feedback Processes
IO Review, Analysis, Testing and Feedback Processes
Supporting Tools and CM Procedures
interoperable Systems Management and
Requirements Transformation
Link 22 Integration Activities
- Interoperability Management
20
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
39
• Components Information Exchange Requirement (IER) analysis (IER Tool)
Standards Documentation System
Platform Documentation Tool – eDOC
Platform Implementation Database – eBIT
Inter-Operability Matrix (IOM)
Inter-Operability Assessments (IOAs) and Evaluations (IOEs)
Standard Interface for Multiple Link Evaluation (SIMPLE)
Link 22 Integration Activities
- Interoperability Management
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
TDL Standards IER Capture
Defence Inter Operability
Requirement Spec (DIORS)
Platform Requirement Difference
Document (PRDD)
Platform Requirement Specification (PRS)
Platform Implementation Difference
Document (PIDD)
Actual Platform Implementation
Specification (APIS)
Interface Requirement
Specification - Part II
Single-Link e.g. Link 16
(SLIRS) - (One per Link)
Now also MIL-STD-
6016C
Interface Requirement
Specification - Part I
Multi-Link - (MLIRS)
• Standards Hierarchy
Link 22 Integration Activities
- Interoperability Management
40
21
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
41
Contractual
Documents
MIL-STD = US Military Standard
SLIRS = Single Link Interface Requirement Specification
PRDD = Platform Requirement Difference Document
PRS = Platform Requirement Specification
PIDD = Platform Implementation Difference Document
APIS = Actual Platform Implementation Specification
MIL-STD-6016C/D = 6016B + SLIRS
PRDD specifies differences from Mil-Std
PRDD + Mil-Std-6016C/D = PRS
PIDD + Mil-Std-6016C/D = APIS
Measure
aspiration
against actual
Link 22 Integration Activities
- Interoperability Management
• iSMART Documents
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
REQUIREMENT
CONCEPT OF OPERATIONS
SYSTEM SPECIFICATION DOCUMENTS
LINK 22 DTDL - SLIRS
PRDD / PIDD
PRS / APIS
STANGAG 4610 / DLP SPEC
NDS ICD
PARTITIONING DOCUMENT & ICDs
IMPLEMENTATION DOCUMENTS
NMRS
STANAG 5522
PLATFORM
OP SPECS
IER
Capture
Link 22 Integration Activities
- Interoperability Management
• Example Specification Tree
42
22
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
43
Link 22 Integration Activities
• TDL Needs Determination RPDE’s Capability Network Options Assessments products
Step 1 - Capture
Capability Needs
Step 3 -
Identify
Network
Options
Step 4 -
Assess
Network
Options
Step 5 –
Select
Capability
Options
Step 6 -
Document
CNOA NCAM
Net Force Operating Concept
NCDT – S/W Tool
NCAM Building Blocks NCAM Taxonomy
CNOA Framework
Step 2 - Identify
Net Force
Integration
Requirements
- The Net Force Operating Concept
- CNOA Net Force Capability Analysis Methodology (NCAM)
- NCAM Building Blocks
- NCAM Taxonomy
- Net Force Capability Design Tool (NCDT) – “Net Force Designer”
* RPDE – Task05 – CNOA Sourced
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
44
Link 22 Integration Activities
• CNOA - NCAM
* RPDE – Task05 – CNOA Sourced
Step 1 - Capture
Capability Needs
Identify Project
Capture Operational Constraints
Identify Operational Effects
Structure
Build Capability Needs Statements
Identify Net Force Potential Support
Identify Capability Structure
Identify Internal Functions and
IEs of each OODA Component
Identify Component Capability System
Solutions
Build Component Capability Requirements
Identify Capability Configurations enabling Effects
Identify Capability Collection
Identify Net Force Operational Effect Timeliness
requirement
Identify current Net Force Operational Effects that
new Component Capability could ‘contribute’ to
Identify (external) Communications Network
‘Connectivity’ requirements
Populate Operational Effect OODA Loop Time
Budget (Component Capability Only)
Identify Net Force Contribution
to Step 1 Capability Structure
Identify Capability Systems that fulfil
Component Capability Requirements
Build Capability Structure View of
Capability System Configuration Options
Build Capability Structure View of
Capability System Configuration Options
Identify Net Force Operational
Effects Deltas/Differences
Confirm Net Force Availability Requirements
for Component Capability Configurations
Step 2
Identify Net
Force Integration
Requirements
23
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
45
Link 22 Integration Activities
• CNOA - NCAM
* RPDE – Task05 – CNOA Sourced
Identify Message Format Suitability Options for required IE support
Step 3
Identify Network
Options
Identify candidate Communication Network ‘Distance Support Options’
Select IE’s required by Sink CC from Source CC IE Options
Identify Communications Network Bearer Support Options
(technically able to support required Bandwidth)
Identify Environment Support Options
Identify opportunity for IE Simultaneity Support
Modify IE data rate support requirement to accommodate IE
selection and simultaneity determinations
Identify Timeliness parameters for Candidate Network Options
Identify Existing Interface Modifications
Identify additional Communication Enabling Component
Capabilities (Gateways, Forwarders and Relayers)
Identify Timeliness parameters for Candidate Network Options
Apply Existing Interface Constraints to Capability System
Structure
Step 4
Assess Network
Options
Static Analysis
Dynamic Analysis
Review, Consolidate and Recommend
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
• CNOA Integration Framework Assists With A view of what the Net Force will look like and how it will operate;
A means to produce a ‘Capability View’ for Projects;
A way to architect A Net Force;
A way to identify the Capability Elements of a Project that need to be ‘Accessible and Connectable’ for future NCW purposes;
A way to identify what Network Options should be employed for Net Force Connectivity of these NCW Capability Elements;
A way to assess Network Options; and
A way to test NCW viability.
• CNOA NCAM Covers NCWIIS Imperatives 1 through 3
46
Link 22 Integration Activities
* RPDE – Task05 – CNOA Sourced
24
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
Link 22 Generic Issues
• NILE Products Releasability Link 22 and NILE Documentation has constrained releasability
to Nations, Non-NATO
NILE Developed Documentation and NCE Items are released
through Licensing
Require Sponsor or NILE Membership to Access
• Cryptographic Releasability US Controlled Cryptographic Device
Export and Releasability Issues to be considered and factored
• Interoperability NCE Product Versions - SNC
SPC and National Radio Compatibility
Link 22 Tactical Message Implementations – STANAG Variations
Host Implementations of Operational Functions within CONEMP
47
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
Link 22 Extant Products/Developments
48
COMPANY DLP SNC CRYPTO (LLC/MLLC)
SPC Network Management Tools
Test/Integration Tools
Northrop Grumman IT
NGC2P, CLIP
NIL
E P
MO
SU
PP
LIED
(h
as b
een
inco
rpo
rate
d in
to D
LPs
and
sta
nd
alo
ne
cap
abili
ties
)
US
FMS
Cas
e
MLST3, TIGER, MLSG
ATOS-Origin LUCID L22 SCOPE
IBM DLPS INMT
Selex SI/DRS ICAS M-DLP
LMAL iSMART, eSMART
THALES TopLink (DLIP) NEXTW@VE
BAeSYSTEMS CAYMAN AGILE
Ultra-Electronics ADSI, MLP
ATLAS-Elektronik ADLiS
Telefunken-RACOMS
SPC 1920/SPC 1920(e)
Diginext TTU22 NETX22* TACTX, DLGU-22
Tecnobit LINPRO EVALINK, MOVILINK
Rockwell Collins MDM-2X02
GD-UK NETLINK
25
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
Link 22 Extant Products/Developments
• Future Developments
Revised HF Waveform to Achieve Higher Throughput
Enhance HF Waveforms to Achieve 1000NM Range (now
Investigation of IP Like NCE Interface
Development of MLLC to Comply with New US Cryptographic Requirements has entered the development stage
JTRS NCE Incorporation
49
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
50
Link 22 C&IWG
• Communications and Interoperability Working Group
NILE PMO Organised Meeting
Held BI/Annually in NILE Nations
NILE, NATO and Sponsored Nations can attend
Discussion of Issues, Lessons Learned and Future Development to:
– NCE Sub-Systems
– DLP and Host Systems
– Radios
– Interoperability Testing and Demonstration
TIEIO Attend for Australia
26
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
51
TIE IO Link 22 Trial
• TIE IO Link 22 Trial
The aim of the Link 22 trial is to independently:
Inform ADFTA personnel on the capabilities and limitations of Link 22
Allow ADFTA to provide advice on Link 22 implementation
Report on the suitability of Link 22 as a BLOS capability
Gather data to inform the development of a Link 22 requirements
Discover any integration problems or operational issues
Raise the awareness and technical understanding of Link22
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
52
TIE IO Link 22 Trial (cont.)
• TIE IO Link 22 Trial Status
The ADFTA Link 22 Trials Suite has been progressively installed within Lab 6, and includes the following elements:
three SELEX-ES Multi-Data Link Processors (M-DLPs) that have a proven and tested Link 22 capability;
NILE SNC Software will be hosted on each M-DLP, which currently being purchased from the NILE PMO;
three DRS-DS dual channel MX-512PV (v17) DTS with two Link 11/22 processor cards embedded;
Encryption / Bypass translator called a LLC-Simulator (LLC-Sim), only used for laboratory based testing.
More details can be found in the TIEIO MTN Update presentation 1.5b
27
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
53
ADF TDL Documentation
• ADF Published TDL Documentation
Future Concepts and Vision – Force 2020 Future Joint Operating Concept (FJOC)
Doctrine - ADFP 6.0.2 - Information Exchange
Doctrine - ADDP 6.0 – CIS, Concept of Link Employment
Policy – DI(G) CIS 6-5-001 – Tactical Information Exchange Domain
Instructions - ADFCI 6.2.4 – Tactical Information Exchange Domain
Supporting Documents – ADF TIE Interoperability and Requirements Guide
Supporting Documents – ADF TIED Capability Development Plan
2010 to 2020
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
54
Please feel free to ask more questions at the LMA IS&GS Stand
28
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
55
Link 22 NILE PMO & Equipment Supplier
Points of Contact
COMPANY Point of Contact Email
Northrop Grumman IT
Vincenzo Sferra vincenzo.sferra@ngc,com
ATOS-Origin Jose de Vries [email protected]
IBM Tim Bostel [email protected]
Selex SI/DRS ICAS Cosimo de Crescenzo/Jim Hardie
[email protected] [email protected]
LMAL Jason Longdon [email protected]
THALES Richard Bourne [email protected]
BAeSYSTEMS Paul Morris [email protected]
Ultra-Electronics Paul Haylett [email protected]
ATLAS-Elektronik Heinz Marsau-Rierl [email protected]
Telefunken-RACOMS
André Kotlowski [email protected]
Diginext Olivier Colléaux [email protected]
Tecnobit Elia Otazu Benitez [email protected]
Rockwell Collins Sonny Foster [email protected]
GD-UK Gavin Green [email protected]
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
56
Link 22 Fitting Plans – NILE Nations
Platform CAN DEU ESP FRA UK ITA USA CV 1 (2016) 2 QE Class
Carrier (2016-19)
1 Cavour (2010) 1 Garibaldi (TBD)
11 NIMITZ Class (2019-23)
LHD, LHA, LPD
2 LPD (2017) 1 LHD (2017)
3 (2014-15) 8 WASP Class (2019-23) 2 AMERICA Class (2020-23) 11 SAN ANTONIO Class (2019-23
Destroyer 2 HORIZON Class (2014-15) 11 FREMM Class (2015-) 2 JEAN BART Class (2015-16)
6 Type 45 AAW (2016- 19)
1 Mimbelli (2010) 1 DeLaPenne (2011) 2 Horizon Class (TBD)
22 TICONDEROGA Class (2019-22) 65 A. BURKE Class (2019-23) 3 ZUMWALT Class (2021-23)
Frigate 12 Halifax Class (2013-15)
4 F125 Class (2016 –19)
5 F-100 Class (TBD)
5 La Fayette Class (2015-17)
13 Type 23 (2016-19) Type 26(2020)
6 FREMM Class (2013-17)
Submarine 4 S80 Class(2016) 6 BARRACUDA
Class (2016-)
Other 6 BAM ships (2017) 1 BAC ship (2017)
26 FREEDOM class (2020-23) 12 HAMILTON class (USCG) (2020-23) 8 LEGEND class (USCG) (2020-23)
Aircraft Helos (TBD) Helos (TBD/TBC)
Helos: NH-90 (2016-) Fixed Wing: MPA (ATL2) (2016-) E2C (2016-)
Helos: Wildcat(TBD) )
Fixed Wing: E3 Sentry (TBD)
Helos (TBD): NH-90, EH-101 Fixed Wing (TBD): MPA (ATR72), MMA (Poseidon P-6)
Shore Sites 1 Halifax 1 Greding 1 (Wilh.)
1 Madrid 1 Rota (2015)
2 Toulon, Bruz 1 (Mobile)
1 Portsdown 1 Taranto 5 (Dahlgren (2), Wallops Island, Dam Neck, Moorestown) (2018)
29
LOCKHEED MARTIN PROPRIETARY INFORMATION
Lockheed Martin Australia STASYS Pty Limited
57
Link 22 Fitting Plans – Non-NILE Nations
Platform DNK FIN NLD AUS, BEL, GRC, JPN, NOR, PRT, SWE, TUR
Plans to Implement Yes (2015)
Yes (2012)
Yes (2012)
TBD
CV - - - -
LHD, LHA, LPD, FPB - 4 HAMINA-FPB (2015) 4 RAUMA –FPB (2015)
LPD1 (2015) LPD 2 (2015+)
-
Destroyer - - 4 ADCF (2015+) -
Frigate IVER HUITFELT Class (3) (2015)
- 2 M-FF (2012-13) -
Submarine - - 4 Walrus (2013-18)
-
Other ABSALON Class (2) Thetis (1)
2 HÄMEENMAA cl (2015) 3 MCMV (2015)
4 Patrol Ship (2013-15) AOR (2012) JSS (2014)
-
Aircraft TBD - TBD -
Shore Sites TBD 2 MOC (2015) 1 Ref sys
SSSB (2013) -