8/18/2019 4586 Presentation
1/44
www.cdlsystems.com
STANAG 4586 – Enabling
Interoperability
Terry Bandzul
CDL Systems LtdCalgary, Canada
8/18/2019 4586 Presentation
2/44
www.cdlsystems.com
Presentation Overview
• NATO STANAG 4586 Overview
• STANAG 4586 Goals
• Interoperability Concepts
• STANAG 4586 In Action
8/18/2019 4586 Presentation
3/44
www.cdlsystems.com
Current Problems
• UAV products - “stovepipe” designs
• Little to no standardization between systems
• Proprietary telemetry and sensor data
streams
• No capability to interoperate
8/18/2019 4586 Presentation
4/44
www.cdlsystems.com
• Conceived in 1998 tostandardize UAV ControlSystem (UCS) interfaces tohelp enable UAV
interoperability
• NATO Specialist Teamformed from industry andgovernment to develop the
standard• USN (PMA-263) is
STANAG 4586 custodian
STANAG No. 4586
Edition 1
NORTH ATLANTIC TREATY ORGANIZATION
(NATO)
NATO Standardisation Agency (NSA)
STANDARDISATION AGREEMENT(STANAG)
SUBJECT: Standard Interfaces of UAV Control System(UCS) for NATO UAV Interoperability
Promulgated on
Chairman, NSA
NATO Project Group 35 (PG/35)
Background
8/18/2019 4586 Presentation
5/44
www.cdlsystems.com
NATO Project Group 35 (PG/35)
Background
• Lead efforts to achieve UAV interoperability in Joint,Coalition Operations
• Lead efforts for UAV Autonomous Operations
8/18/2019 4586 Presentation
6/44
www.cdlsystems.com
STANAG 4586
STANAG 4586 is an Interface Control Definition (ICD)
STANAG 4586 Defined two new interfaces
- Data Link Interface, DLI- GCS Air Vehicle interface
- Command and Control Interface, CCI
- GCS Command Control Interface
• Non-existent• Considered essential foundation for interoperable UAV
systems
8/18/2019 4586 Presentation
7/44
www.cdlsystems.com
UAV Interfaces & Standards
C4I Nodes
Data Link
STANAG 7085
A i r V e h i c l e & P a y l o a d C 2
P a y l o a d D a t a
Imager y
D ig i ta l Messages
Tactical Messages
STANAG 5500: ADatP-3
Payload Data
STANAG 7023 Primary Imagery
STANAG 4545 Secondary Imagery
STANGA 4607 GMTI Radar Data
STANAG 4609 Motion Imagery
GroundControl Station
Focus of
STANAG 4586
8/18/2019 4586 Presentation
8/44
www.cdlsystems.com
STANAG Key Development
Principles
• Data Link Interface (DLI) Messages are air
vehicle and payload independent – Vehicle/Sensor specific messages are allowed
• Command and Control Interface (CCI) is
C4I System/Node independent
– Leverage existing Standards, e.g. STANAG 5500(USMTF)
8/18/2019 4586 Presentation
9/44
www.cdlsystems.com
STANAG 4586
NATO addressing “technical issues” to enable
interoperability, these include;
– DLI and CCI interface definitions
– Functional architecture definition
– System, subsystem component identification
• defines a “common” set of data elementsCommon Data Elements
8/18/2019 4586 Presentation
10/44
www.cdlsystems.com
“Common” Data Elements
Implementation Guide:
provides the comprehensive description of the
intention of each message and data element
in the DLI interface, and makesrecommendations on a common approach
for implementation – Removes ambiguity
8/18/2019 4586 Presentation
11/44
www.cdlsystems.com
Command & Control
Interface (CCI)
• STANAG 4586 provides an interface
profile that defines the specific choices
applicable to UAVs within each standard,
thereby ensuring interoperability.
GCS
C4I Nodes
ADat-P3
USMTF
STANAG 4545
ETC.
UAV/C4I INTERFACE PROFILE
8/18/2019 4586 Presentation
12/44
www.cdlsystems.com
STANAG 4586
In addition, STANAG 4586:
• uses standards, existing and developing
– specifies other standards where possible
– non-proprietary in nature
– if shortfalls in standards, request updates. ie;
CRD, extended CRD
– not redefining standards• defines relationship between the standards
8/18/2019 4586 Presentation
13/44
www.cdlsystems.com
Allied Force Interoperability
Achieve interoperability
between NATO allied forces
Common view of Interoperability
STANAG focus:
8/18/2019 4586 Presentation
14/44
www.cdlsystems.com
Interoperability Ideal
A UAV overhead a compliant GCS, for whichit has not been “natively” developed, could
be passed for control to this compliant
station with the vehicle being safely
controlled to 100 percent of its requiredcapabilities
Ideal goal of interoperability
8/18/2019 4586 Presentation
15/44
www.cdlsystems.com
Multi Vehicle, Modular
Networked Operations
Allows individual addressing of specific Systemcomponents
- the generic interface anticipates that there will be multiple Vehiclesconnected to multiple CUCSs in a networked or standaloneconfiguration, addressing a shared data link resource, or multiple datalinks
8/18/2019 4586 Presentation
16/44
www.cdlsystems.com
Interoperability
US Army
Class IV UAV
US NavyTactical UAV
United Kingdom
Watch Keeper
Italian
Predator
• Concept of Operations (CONOPS) and Doctrine “Neutral”
•Supports evolving CONOPS and Doctrine
8/18/2019 4586 Presentation
17/44
www.cdlsystems.com
CONOPS
Control a single vehicle, of a
specific type
What is the advantage to usingSTANAG 4586 ?
- Sharing the asset
- considering futureexpandability
8/18/2019 4586 Presentation
18/44
www.cdlsystems.com
CONOPS
Multiple vehicles,
single type,
simultaneously
Multiple Data LinksSingle Common
Data Link
8/18/2019 4586 Presentation
19/44
www.cdlsystems.com
CONOPS
Many vehicle types, controlled serially from acommon GCS
Multiple Data Links
- One at a time
Common Data Link - one at a time
8/18/2019 4586 Presentation
20/44
www.cdlsystems.com
CONOPS
Multiple vehicles, multiple
types simultaneously
Additional requirements
– Co-location versus networked
operation
– DLI across RF link
Multiple Data Links
Common Data Link
8/18/2019 4586 Presentation
21/44
www.cdlsystems.com
Scalable Interoperability
• Not always requirement to control 100% of
vehicle capabilities
– Expensive undertaking
• Only control functionality required to be
interoperable
– five Levels of Interoperability defined within
the standard
8/18/2019 4586 Presentation
22/44
www.cdlsystems.com
Levels of Interoperability
• Level I: Indirect receipt/transmission of UAVrelated payload data.
• Level II: Direct receipt of ISR/other data where“direct” covers reception of the UAV
payload data by the UCS when it hasdirect communication with the UAV.• Level III: Control and monitoring of the UAV payload
in addition to direct receipt of ISR/other data.
• Level IV: Control and monitoring of the UAV,less launch and recovery.
• Level V: Control and monitoring of the UAV, pluslaunch and recovery functions
8/18/2019 4586 Presentation
23/44
www.cdlsystems.com
Modular Control
Modular Architecture
- functional separation• situation awareness
• AV mission execution andmonitoring
• Payload – monitor, control• Data Links – monitor, control
Scalable
8/18/2019 4586 Presentation
24/44
www.cdlsystems.com
STANAG 4586 In Action
• VCS-4586, Common User Interface for
range of controlled vehicles
8/18/2019 4586 Presentation
25/44
www.cdlsystems.com
VCS STANAG 4586
Applications
• US Army One System
– RQ-7B Shadow 200 - AAICorp
– Warrior – GA ASI
• Barracuda (RIB) – MeggittDefence Systems Canada
• Grasshopper – Advanced
Subsonics• Raven – AeroVironment
• Golden Eye – Auroa
• Aerosonde - AAI Corp.
• Grasshopper - AdvancedSubsonics & Xiphos
• Silver Fox - Advanced Ceramics
• Scan Eagle - Boeing
• Kingfisher & Other - BAESystems
• RTB (Research Test Bed) - CAE /CDL Systems
• Blade - Ultra
Grasshopper Shadow 200 Warrior
Silverfox
Scan Eagle
Kingfisher
AerosondeBlade
Hammerhead
8/18/2019 4586 Presentation
26/44
www.cdlsystems.com
Mini UAV to MALE
• Currently, how is it that the sameCUCS software can be used to controlvehicles as diverse as a mini UAV anda MALE?
• VSMs are key, but not 100% of theanswer
• STANAG 4586 is scalable inimplementation, from a singleoperator, single laptop for a miniUAV, to dual operator workstationsfor MALE UAVs.
•STANAG 4586 is configurablethrough VSM messages and/or throughconfiguration files
8/18/2019 4586 Presentation
27/44
www.cdlsystems.com
VCS-4586
Common User Interface
• Configuration Messages are used to request air
vehicle and payload configuration information.
– Expected range of vehicle parameters
– Applicability of generic parameters to vehicle
– Availability of generic parameters from vehicle
– Extensibility of parameters
• The CUCS uses this information to configure thedisplays for the Air Vehicle/ payload.
8/18/2019 4586 Presentation
28/44
www.cdlsystems.com
HCI - Configurable Elements
Message #1201: Display Unit Request
The CUCS uses the Display Unit Requestmessage to identify the display units that the VSM
is required to use in Remote Displays.
Examples:
• Distance
• Altitude• Speed
• Temperature• Mass/Weight
• Angles• Pressure
Message #1202: CUCS Resource Report
Used to communicate to the VSM the resourcesavailable within the CUCS for managing remotedisplays to be presented at the CUCS.
Examples:
• JAVA Engine Available
• PDF Reader Available• X Window Server Available
• X Window Display Number
• X Window Screen Number • Display Window Horizontal Width
Message #1303: Field Configuration Command
This message is used by the CUCS to configure
any GUI components associated with a formattedDLI message field, where the state of the field maybe altered in accordance with the contents of thismessage.
This message is sent from the VSM to the CUCSwhenever the controllable state of a field or an
enumeration within a field changes thus identifyingthe allowable states of control at the VSM for thespecified parameter.
Examples:
Altitude Command Type
Heading Command
Speed Type
Altitude Type
Antenna Type
Flight Mode
(over 30)
8/18/2019 4586 Presentation
29/44
www.cdlsystems.com
Parameter Ranges
CUCS supports full STANAG parameter ranges,
But Configures the displays to suit the selected
vehicle
Altitude scale
modified
8/18/2019 4586 Presentation
30/44
www.cdlsystems.com
Parameter Applicability
CUCS must be capable of supporting allgeneric functionality,
but is expected to remove functionality
unsupported by the controlled vehicle
Flight modes
removed
8/18/2019 4586 Presentation
31/44
www.cdlsystems.com
Vehicle Logic
CUCS can not know the control logic for allvehicles,
therefore the VSM identifies the current state
of vehicle parameters
Mission mode
unavailable
8/18/2019 4586 Presentation
32/44
www.cdlsystems.com
Parameter Extensibility
Ability to extend generic capabilities with vehiclespecific capabilities, for specific parametersthrough the DLI mechanism,
for tight integration into a single application
- for operator ease of use
- for flight criticality or flight safety
Added custom Flightmode -> Roll
8/18/2019 4586 Presentation
33/44
www.cdlsystems.com
Private Messaging
Ability to integrate generic capabilities with vehiclespecific capabilities, using privately defined DLImessages,
to tightly integrate into a single application
- for operator ease of use
8/18/2019 4586 Presentation
34/44
www.cdlsystems.com
Configured Panel
Compliant
Configured
8/18/2019 4586 Presentation
35/44
www.cdlsystems.com
What Interoperability Means
• UAV control systems can be developed to meet“national” requirements
• UAVs for Country A may use one user interface,
regardless of UAV type; UAV controllers forCountry B could be using a completely differentuser interface, even though they may be operatingthe same UAVs
• UAV operated by Country A can be handed off toCountry B, even though the ground stations aredissimilar
8/18/2019 4586 Presentation
36/44
www.cdlsystems.com
What Does S4586 Do for Me?
• Reduces Costs - Capital and O&M• Simplifies C4ISR Systems Integration
• Reduces Logistics Tail
• Decouples UAV development from GCS Integration
• Supports National GCS Development with own
CONOPS and Training
• In Coalition Operations, STANAG 4586 Supports
Multinational Partners Sharing Data from multipleUAVs from multiple countries.
8/18/2019 4586 Presentation
37/44
www.cdlsystems.com
Acquisition of UAV Systems
STANDARDIZED INTERFACE DECOUPLES
THE GCS & AIR VEHICLE
STANAG 4586 StandardGCS/Air Vehicle Interface
The acquisition of air vehicles can
occur independent of other elements
of the UAV system (eg. the GCS).
The GCS can be sustained, upgraded
and produced in multiple
configurations independent of the
other elements of the system.
Ground
Control Station
8/18/2019 4586 Presentation
38/44
www.cdlsystems.com
Interoperability Does Not Mean
• Common User Interface for All Users
– French Operator does not sit in a German
shelter
• Common Training – Train for your own system
8/18/2019 4586 Presentation
39/44
www.cdlsystems.com
Trends Affecting STANAG
• Bandwidth Reduction – Common Protocol viaRF Link
• Trend toward network-centric CONOPS
- SOA (service-oriented architecture) – provideservices to the network.• Trend toward increasing system autonomy
- Autonomy messages added to the STANAG 4586,operators become system supervisors
• Trend toward collaboration among systems- Ship to ship messaging and interactions
8/18/2019 4586 Presentation
40/44
www.cdlsystems.com
Conclusions
• STANAG 4586 Edition 2 is ready.
• STANAG 4586 is implementable.
• STANAG 4586 is implemented on several realUAVs.
• A common User Interface per User is achievable.
UAV interoperability is now possible.
Is Interoperability possible?
8/18/2019 4586 Presentation
41/44
www.cdlsystems.com
STANAG 4586: Enabling
Interoperability
THANK-YOU
8/18/2019 4586 Presentation
42/44
www.cdlsystems.com
A NATO UAV System
GROUND
CONTROL
ELEMENT
C
C
I
AIR VEHICLEELEMENT
PAYLOAD ELEMENT
Air DataTerminal
Payload Data
Ground DataTerminal
ExternalC4I
Systems
Control
Status
AIR COMPONENT
GROUNDCOMPONENT
DLITasking
Status
DataDissemination
7085
7023, 4545,4607, 4609D
a t aL i nk
STANAG 4586STANAG 4586
O P E R A T
O R
8/18/2019 4586 Presentation
43/44
www.cdlsystems.com
STANAG 4586 Goals
• Interoperability amongst Allied Forces
• Diverse Concepts of Operations
• Network Centric Operations.
Secondary considerations:
• Common ground control station per user vrs Scalability
• One operator, many vehicles
• Modular design
8/18/2019 4586 Presentation
44/44
www.cdlsystems.com
Interoperability - ONE System
QuickTime™ and aTIFF (LZW) decompressor
are needed to see this picture.
US Army TUAV Project
Office has introduced
“ONE System” to fly:
• Shadow 200 – (AAI Corp.)
• Hunter
– (Northrop Grumman)
• Sky Warrior
– (General Atomics - ASI)
Based on the VCS by CDL Systems Ltd.
Top Related