Implementing a Single Mission DataInterface for Platform/Weapon Integration

March 2004

(formerlyknown as

TPDF)

UNCLASSIFIED

UNCLASSIFIED

Slide 2

What is MIL-STD-3014?

• MIL-STD-3014 IS NOT:– A data link message standard competing with Link-16, VMF, etc.– A stores bus data standard competing with MIL-STD-1760

• MIL-STD-3014 IS:– An available DoD military standard

• “Department of Defense Interface Standard for Mission Data Exchange Format”

– A digital file format for mission-specific programming data• For Precision Weapons

• Also suitable for UAVs/UCAVs, manned platforms, etc.

– An opportunity for transition to Open Systems Architecture• And the future of military communications

• Through mass data transfer integration strategy on links and buses

UNCLASSIFIED

UNCLASSIFIED

Slide 3

Delivers:Steel onTarget!

Putting the “War” in Network-Centric Warfare

Mission(Sortie)Planner

C4ISR

Target &Force Order

CurrentNCW, GIG

& FORCEnetC4ISR Focus:

Speed ofCommand

Delivers: Attack Command

PGM

Bulk Fileby

“Brick”

LaunchPlatform

MissionComputer

DTD

DataLink

Terminal

orData Link

MissionDataFile

OurComplementary

Domain:Speed of Effects

UNCLASSIFIED

UNCLASSIFIED

Slide 4

Paired to Break the Comms Jam…

• MIL-STD-3014– Defines a Digital Data File– A general-purpose standard for content format– Buffered by a standard header

• Describes the file’s source, destination and size

• Mass Data Transfer (MDT) Protocols - send bytes, not data elements– Decouple content from comms protocols

• Channels don’t care about contents of a 3014 file, just size & destination• Senders and receivers don’t care how it gets there, just what’s in it

– If it’s a MIL-STD-3014 file, there’s only one way to get or send it - MDT!• Regardless of the size, source, destination or content

• When they’re paired, every comms channel can use one message– To carry any amount of any content, from any source to any destination – Including MIL-STD-1760 Stores Buses– Including Tactical Data Links

UNCLASSIFIED

UNCLASSIFIED

Slide 5

F-22

Our Model - MIL STD 1760One Hardware/Electrical Interface for all Jets & Weapons!

• Without MIL-STD-1760, our connectors would be an expensive, complex mess!

• Across DoD, our mission data transfer is complex today – We just don’t see it, since there’s no hardware

JASSM JSOW SLAM ER HARM JDAM HARPOON

PYLON WEAPONINTERFACE ELEX

F/A-18A/B/C/DF/A-18E/F

F-15E

F-16 Blk 10-30,40B-1BB-2AB-52H

F-35

WCMD AGM-123 EGBU

Compared to this, MIL-STD-1760was cheap to implement!

UNCLASSIFIED

UNCLASSIFIED

Slide 6

• Airborne Platforms– Store Mission Data– Own-ship Mission Data

• Stores– New and Legacy– Weapons– Sensors

StoresCommsChannel

3014 MDTProtocol

MissionPlanningModule(s)In C4/ControllerNode 30

14

Inte

rfac

e

AirbornePlatform

3014MDT

The MIL-STD-3014 VisionOne Simple Interface for All Mission Data Transfer

“Brick” 3014 MDT DTE

RF C2Links

LinkTerm.

Weapon/Pod Link

3014MDT

3014MDT

Self-Tgtg(Opt.)

301

4 In

terf

ace

3014MDT

3014 MDT3014MDT

3014MDT

3014

MD

T

MC

301

4 In

terf

ace

CommsChannel

3014 MDTProtocol

3014MDT

MIL-STD-1760

MMSI

Fiber, IR,Future…

3014MDT

3014MDT

3014MDT

3014MDT

3014 MDT

3014MDT

UNCLASSIFIED

UNCLASSIFIED

Slide 7

With This Strategy,Evolution is NO PROBLEM!

• 3014 + MDT = a Single Interface

• Faster, cheaper integration– Adding a new weapon? New variant? New data type? More

resolution? New Algorithm? New targeting source? A new radio?– Once you’re using 3014 for data transfer…– NO PROBLEM!

• Greater tactical flexibility– One 3014-capable channel is down?– Once you’re using 3014, switch to another one!– NO PROBLEM!

UNCLASSIFIED

UNCLASSIFIED

Slide 8

Legacy Weapon StrategyDon’t Fix What Isn’t Broken

• Leave the Legacy Weapon Alone– Don’t touch the weapon, its mission planning, or its 1760

interface

• One piece of groundside software supports all weapons & platforms– Supports each legacy 1760 “J-weapon” weapon mission file

format– Condenses it to just real data for one mission, in 3014 file format– Formats and transmits via available real-time comms

• One piece of airborne software per platform– One generic 3014 interface – for legacy and future

UNCLASSIFIED

UNCLASSIFIED

Slide 9

What Will MIL-STD-3014 GiveYour Platforms and Weapons?

• Improved Mission Capability– Get full PGM capability, with On- or Off-board Targeting– Get full integration of your stores into the NCW environment

• Push any and all mission data for in-flight updates of all weapons

– A common, general purpose mission data message on each TDL• Very compact file size for each TST mission

• Yet common header format & handling for ALL FILES

• Reduced future integration cost and risk– Like MIL-STD-1760, a common interface for all platforms & stores– The last mission data interface you’ll ever need– Legacy support, flexibility, and easy future expansion

• A long-term-sustainable, evolving solution– Joint Service/Coalition, all autonomous tactical systems

UNCLASSIFIED

UNCLASSIFIED

Slide 10

MIL-STD-3014 StatusPublication in Process - Draft Available Now

• MIL-STD-3014 defines format of digital mission data files• Was reviewed, & edited by Society of Automotive Engineers

– Avionics Standards Committee– Same committee that manages MIL-STD-1760, -1553, & MMSI (for SDB)– Approved by (AS-1B subcommittee) on 17 June 2003

• “Recommended MIL STD” delivered to Government

• Officially released on 20 February 2004– USAF ASC/ENOI is publishing agency

• Lead agency activities

– USN (NAVAIR) NCW Directorate is Responsible Engineering Officer• Technical lead• Web page maintenance• Manages process for updates to registries and text standard

– Web Page access for downloads and requests for additions to registries• http://MIL-STD-3014.navy.mil

UNCLASSIFIED

UNCLASSIFIED

Slide 11

Summary of MIL-STD-3014

• A new joint standard for weapons, platforms, links, msn planning– A mission data interoperability complement to MIL-STD-1760– A basic requirement for extending NCW to Steel-on-Target w/ PGMs

• A Link/Platform/Channel Agnostic ‘Bit Bucket’ for Mission Data– Open, extensible, non-proprietary file format, similar to “.rtf” or “.pdf”– Very compact and efficient

• Provides a single interface for all mission data on platforms & links– Isolates information content from comms channel protocols

• All 3014 files are variable length files with a standard header

• All 3014 files are transmitted using mass data transfer protocol

– Supports any content, source, destination, or channel• Any mix of mission data, in any hierarchical organization

• On-platform and off-platform sources

• Any new or legacy, 1760 or MMSI weapon

• Even uninhabited sensor and weapon platforms

• Wire, fiber, brick and RF channels; it’s always just a file!

• Rapid on-line process for adding new data to standard– Including private data types

UNCLASSIFIED

UNCLASSIFIED

Slide 12

Backup

UNCLASSIFIED

UNCLASSIFIED

Slide 13

3014 Carries Whatever Data You Need

• 3014 is a structured data bucket with a common header• Flexible data types, standard & custom

– Primitives (e.g. latitude)– Concatenated (lat/long/el)– Module (any combo, primitive / concatenated / other modules)

• Add new data types quick & easy with on-line registries• Multiple data types possible in any category

– Mission needs, not comms constraints, drive choice• Example: Need imagery? Why limit to one format?

– Format need may be driven by proprietary algorithms– Support them all – JPEG 2000, NITF 2.1, Modified NITF, even edge map

• All data types registered & controlled– But some are private to support proprietary/classified needs

UNCLASSIFIED

UNCLASSIFIED

Slide 14

Groundside

JFN / TDM

Platform Brick File Integrator

Pltfm Legacy Brick BDF

ChecksumIndex &

Directory

“Weed” Nulls f/ Legacy

BDF

Add Rqd 14R data sets

MDF

Legacy BDF

Create Legacy

BDF

Add 3014 File Header

TAMPS/JMPSWpn MPM/UPC(Unchanged)

Legacy Weapon Message Wrapper

Platform OFP WeaponOFP

SMS

(Unchanged)

Transfer Mission PlansVia Brick & Data Link

176

0

1760 I/F

13R

14R14RBrick I/F

TDL OFPTransfer

Mission Plans

13R

MissionSoftware

MDF

TDL OFPTransfer

Mission Plans

MDF

MissionMemory

DTD

Transfer 1760 Files/ Records/ Blocks

3014 Parser

MDF

Pilot I/F

Rcv MDMs & Assemble MDF Read/Strip

3014 Hdr

13R/14R Messages

Command from C4ISRConfirmation to C4ISR

Segment & Send MDMs

Send MDF

Link I/F

Accept MDF, (Finish

Assembly?)

Rapid Retarget File Processor

Add CWs/HWs,

Send 13Rs & 14Rs to SMS

Accept(Assign to Sta #)

UNCLASSIFIED

UNCLASSIFIED

Slide 15

Groundside

TAMPS/JMPSWpn MPM

Platform Brick File Integrator

Add to Brick

Native 3014 –One SimpleInterface!

Platform OFP WeaponOFP

SMS

(Unchanged)

Transfer Mission PlansVia Brick & Data Link

176

0

1760 I/F

13R

14R14RBrickI/F

TDL OFPTransfer

Mission Plans

13R

MissionSoftware

MDFCreate and Forward Mission Plans

TDL OFPTransfer

Mission Plans

MDF

MissionMemory

DTDIntegrated

Platform BDF

3014 Parser

MDF

Pilot I/F

Rcv MDMs & Assemble MDF

Create TPDF BDF

MDT 3014 BDF

Accept(Assign to Sta #)

Command from C4ISRConfirmation to C4ISR

Segment & Send MDMs

Identify 3014 File Type & Forward to

TPDF Parser

Read/Strip 3014 Hdr

3014 BDF

Link I/F

Accept MDF, (Finish

Assembly?)

JFN / TDM

Send MDF

3014 BDF

UNCLASSIFIED

UNCLASSIFIED

Slide 16

ApplicationLayer

ApplicationLayerDataAp HdrApplication Protocol

PhysicalLayer

PhysicalLayerBits

Data LinkLayer

Data LinkLayerDataDL Hdr

PresentationLayer

PresentationLayerDataPr HdrPresentation Protocol

SessionLayer

SessionLayerDataSe HdrSession Protocol

TransportLayer

TransportLayerDataTr HdrTransport Protocol

NetworkLayer

NetworkLayerDataNw HdrNetwork

Protocol

3014 and the OSI Comms ModelWhere We Fit in the ‘Seven Layer Cake’

Actual Data Transmission Path

SendingS/W Process

ReceivingS/W Process

Functional Data Transmission PathData

Mission PlanningSoftware

Autonomous System

MIL-STD-3014 Defines the Format of This File

MIL-STD-3014

Platform Software, Channel-Driven

Channel (1760, L

ink-16…)

UNCLASSIFIED

UNCLASSIFIED

Slide 17

Primitive

Primitive

Primitive

Header

Primitive

Module

Primitive

Concatenated

Primitive

Primitive

Primitive

Concatenated

Primitive

Primitive

Module

Module

3014 Modular File StructureCommonality plus Maximum Flexibility

• MIL-STD-3014 Module: a Header plus any mix of elements– All MIL-STD-3014 files are modules

• Scalable from one data element (latitude) to multiple dissimilar mission plans

• All with No null data– Send only what you need to send

Header

Header

ModuleHeader ...

Primitive

...

...

Typical Header Size:14 bytes plus

2 bytes per data element

UNCLASSIFIED

UNCLASSIFIED

Slide 18

3014 Module Header Elements

Mandatory Fields

Optional Fields

CODE TYPE4

CODE SIZE2

CODE KEY(var)

FIELDNAME

Size,Bytes

AUTH TYPE4

AUTH SIZE2

AUTH STAMP(var)

SOURCE SIZE2

SOURCE INFO(var)

NOTE SIZE2

NOTE INFO(var)

Flag Name(bit #)From

HEADERCONTENTS

Field

CODE Flag(Bit 2) = 1

AUTH Flag(bit 3) = 1

SOURCE Flag(bit 4) = 1

NOTE Flag(bit 5) = 1

CREATORTIMESTAMP8

CREATORORG8

CREATORINDIV8

CREATORSERNO8

CREATE Flag(Bit 1) = 1

CLASS CODE2

MODULE SIZE4

HEADER CONTENTS2USER CODE2

ELEMENT COUNT4

ELEMENT LIST(var)

FIELDNAME

Size,Bytes

Index, Bytesfrom File Start

0

2

6

8

10

14

(var)CLASS CODE2CLASS CODE2CLASS CODE2

CLASS CODE2COUNT2

CLASS CODE2COUNT2

CLASS CODE2COUNT2

Element CountDeterminesNumber ofentries in

Element List

MULTIPLEFlagSetsList

Format

MULTIPLE= 0

MULTIPLE= 1

HEADER CONTENTSbits 1-15

Are flags thatreflect presence

Of Optional Header Fields

(or)

Start of Data Elements