UNCLASSIFIED

DB03-124

Fire Control-Node Engagement Fire Control-Node Engagement Technology (FC-NET)Technology (FC-NET)

Deborah A. ButlerAviation and Missile Research, Development, and Engineering Center(256)876-1303deborah.butler@rdec.redstone.army.mil

Deborah A. ButlerAviation and Missile Research, Development, and Engineering Center(256)876-1303deborah.butler@rdec.redstone.army.mil

Implementing FC-NET: Initial ExperiencesImplementing FC-NET: Initial Experiences

15 May 2003 UNCLAS

SIFIED2DB03-124

OverviewOverview

IntroductionIntroduction XD1 Weapon SystemXD1 Weapon System Development EnvironmentDevelopment Environment Implementation DescriptionImplementation Description ConclusionConclusion

15 May 2003 UNCLAS

SIFIED3DB03-124

• “Stove-Pipe” Solutions• Proprietary Solutions• Limited Software Reuse• Non-Interoperable• Large Logistic and O&S Budgets• Non-Scalable• Non-Reconfigurable• Single Weapon Centric• Non-Standards Based

TODAYTODAY

FCS

FCS

Unique Point Designs for Fire Control

Reconfigurable, Flexible, System of Systems

Requires a New Vision for Providing Fire Control Capabilities for Multi-Missions, Weapons, and Platforms.

Requires a New Vision for Providing Fire Control Capabilities for Multi-Missions, Weapons, and Platforms.

The FC-NET Fire Control Architecture is Modular, Distributable, and Scalable to Match the Flexible, Configurable Nature of FCS.

Future Combat SystemsFuture Combat Systems

FC-NETSolutionFC-NETSolution

The Fire Control ChallengeThe Fire Control Challenge

BEYOND LOS NET FIRES

CM

CKEM

LCPK

COMMONMSL

IFFSINCGARS

EPLRSJTRSLNS

FLIRDVOTV

TURRET

UGV

SASPG

UAVSM1

SMIWeapons ControlPlatform Control

COMMS, SA,Targeting,

BIT, TrainingSafety, Security

SMIWeapons ControlPlatform Control

COMMS, SA,Targeting,

BIT, TrainingSafety, Security

15 May 2003 UNCLAS

SIFIED4DB03-124

Fire Control Puts Munitions on Fire Control Puts Munitions on TargetsTargets

Target Acquisition

ECC/GunnerECC/Gunner

Target Selection

Weaponeering

Weapons Assignment

Target Engagement

Damage Assessment

Weapon Weapon SystemSystem

Estimator

Targeting

Tracker

Track DB

Correlator

Weapon Suite

Munition

Launcher

Sensor Suite

Sensor

Acquisition

Tracking

Platform Suite

Platform

PositionOperator

Environment

Manager

WeaponTargetsTargets

The Fire Control System is a Force Multiplier for the Individual SoldierMore Targets, More Quickly, More Accurately!

The Fire Control System is a Force Multiplier for the Individual SoldierMore Targets, More Quickly, More Accurately!

15 May 2003 UNCLAS

SIFIED5DB03-124

Program StatusProgram Status

FC-NET is a DoD Science and Technology Objective FC-NET is a DoD Science and Technology Objective (STO) Program.(STO) Program.

Currently in Year 2 of the 5 Year Program.Currently in Year 2 of the 5 Year Program. Developing a Series of Experimental Weapon Systems toDeveloping a Series of Experimental Weapon Systems to

– Evolve the Capabilities of the FC-NET Architecture– Populate a Set of Fire Control Foundation Classes (FCFC)– Integrate Missile- and Gun-Target Pairing Algorithms– Demonstrate FC-NET Applicability to Future Weapon Systems

Partnering with TARDEC (Detroit Arsenal) for Partnering with TARDEC (Detroit Arsenal) for – Reuse of Existing Integrated Crew Station – User Interface Expertise

Partnering with ARDEC (Picatinny Arsenal) forPartnering with ARDEC (Picatinny Arsenal) for– Gun-Target Pairing Algorithms

15 May 2003 UNCLAS

SIFIED6DB03-124

XD1 Weapon SystemXD1 Weapon System

Vehicle

Platform

LCPK LEU

Launcher(M261)

Launcher(M299)

CMSCMSCMSCMS(4)

FCC

LCPK(19)

...

ICS

CMS LEU

CueingSensor

ConsoleTargetData

Position/AttitudeSensor

XD1 is an Experimental Weapon System Composed of XD1 is an Experimental Weapon System Composed of Both Real Hardware and Simulations of Tactical LRUs.Both Real Hardware and Simulations of Tactical LRUs.

15 May 2003 UNCLAS

SIFIED7DB03-124

Integrated Crew Station (ICS)Integrated Crew Station (ICS)

Using TARDEC’s Vetronics Technology Testbed (VTT) as Using TARDEC’s Vetronics Technology Testbed (VTT) as ICS Provides Real Soldier Machine Interface (SMI) ICS Provides Real Soldier Machine Interface (SMI) Functionality Using Tactical HardwareFunctionality Using Tactical Hardware

VTT Includes Touch Screen, Map Display and Target ListVTT Includes Touch Screen, Map Display and Target List

VTT Provides an Upgrade Path to Next Generation Crew VTT Provides an Upgrade Path to Next Generation Crew Station Technology Being Developed by the Crew Station Technology Being Developed by the Crew Integration and Automation Testbed (CAT) Advanced Integration and Automation Testbed (CAT) Advanced Technology Demonstration (ATD).Technology Demonstration (ATD).

15 May 2003 UNCLAS

SIFIED8DB03-124

Development SystemDevelopment System

DevelopmentServer

Dual 2.4 Ghz XeonTM

2 GB RAM160 GB disk

------------------------Redhat GNU/Linux 7.3

gccCVS

ApacheGNATS

DevelopmentServer

Dual 2.4 Ghz XeonTM

2 GB RAM160 GB disk

------------------------Redhat GNU/Linux 7.3

gccCVS

ApacheGNATS

Windows XPTM PCVNC, ssh, scp

TCP/IP

TCP/IP

TCP/IP

TCP/IP

TargetSystem

TargetSystemTFTP

NFSRLOGIN

Development Client

Windows 2000TM PCVNC, ssh, scp

Development Client

Development Client

Windows 2000TM PCVNC, ssh, scp

15 May 2003 UNCLAS

SIFIED9DB03-124

Free and Open Source ToolsFree and Open Source Tools

fcnetidlfcnetidl Compiler Compiler

– Custom Tool Based on ORBit IDL Parsing Library

– Automatically Generated Approximately 350,000 C++ SLOC

– Generated Code for Client-Server Communications

XD1 Application and FCFC Class Skeletons

DoxygenDoxygen

– Automatically Generated 1282 Page API Description Document

15 May 2003 UNCLAS

SIFIED10

DB03-124

Target SystemTarget System

Fire Control Computer

Radstone VME64 SBC400 Mhz PowerPC 7410

256 MB RAM64 MB Flash4 serial ports10/100 BaseT

UltraSCSIDual redundant 1553 Interface------------------------------------------

LynxOS 3.1.1FCFC

FCNETcommsGNU Common C++WSTAWG OE 2.0

libXML2xmlwrap

Fire Control Computer

Radstone VME64 SBC400 Mhz PowerPC 7410

256 MB RAM64 MB Flash4 serial ports10/100 BaseT

UltraSCSIDual redundant 1553 Interface------------------------------------------

LynxOS 3.1.1FCFC

FCNETcommsGNU Common C++WSTAWG OE 2.0

libXML2xmlwrap

DevelopmentSystem

VTT

M20 Platform

TCP/IP

RS232

CMS LEUTCP/IP

LCPK LEUTCP/IP

TCP/IP

TFTPNFS

RLOGIN

15 May 2003 UNCLAS

SIFIED11

DB03-124

Free and Open Source LibrariesFree and Open Source Libraries

GNU Common C++GNU Common C++

– Provides an Abstract Interface for Serial Ports and TCP/IP Sockets

WSTAWG OE 2.0WSTAWG OE 2.0

– C++ Bindings Developed for TARDEC OE 2.0 Implementation

libXML2libXML2

– Support for XML-Based Configuration Files

xmlwrapxmlwrap

– C++ Wrapper for libXML2

15 May 2003 UNCLAS

SIFIED12

DB03-124

FC-NET SIL Logical ConnectivityFC-NET SIL Logical Connectivity

Simulation ControlEmbedded Simulation

System

VetronicsTechnology

Testbed

VehicleSimulation

LCPK LEU Simulation

Weapon System Simulation

WeaponSystemNetwork

RISC

SIL Network

SIL Network DIS Network

DIS Network

Tactical Interface

Fire Control

Fire Control Computer

Weapon Advisor

Munition Simulation

Battlespace Simulation

Laser Designator Simulation

Simulation Logging

Simulation World View

Mission Simulation

Platform Simulation

CMS LEU Simulation

15 May 2003 UNCLAS

SIFIED13

DB03-124

FC-NET API ImplementationFC-NET API Implementation

Based Upon the FC-NET ArchitectureBased Upon the FC-NET Architecture

Defined in Object Management Group (OMG) IDLDefined in Object Management Group (OMG) IDL

– IDL is Standardized and Compilable

– IDL has Mappings to C, C++, Java, Ada, ...

IDL use Forced Consideration of Implementation IssuesIDL use Forced Consideration of Implementation Issues

Implementation Issues Led to Revisions in ArchitectureImplementation Issues Led to Revisions in Architecture

Language-Independence of IDL Limits Object-Oriented Language-Independence of IDL Limits Object-Oriented ImplementationsImplementations

– No Function Overloading

– No Polymorphism

– Single Inheritance Only

15 May 2003 UNCLAS

SIFIED14

DB03-124

Impact of IDL on ImplementationImpact of IDL on Implementation

Identified and Isolated Commonalities in Position- and Identified and Isolated Commonalities in Position- and Device-Oriented ComponentsDevice-Oriented Components

Developed a Position Class Hierarchy that Incrementally Developed a Position Class Hierarchy that Incrementally Exposes Different Types of Position Information (e.g., Exposes Different Types of Position Information (e.g., Location, Orientation, Acceleration)Location, Orientation, Acceleration)

Developed a Common State Model for all Physical Developed a Common State Model for all Physical Devices (e.g., Launcher, Platform, Munition).Devices (e.g., Launcher, Platform, Munition).

Device State Model is Embedded in a Device Class Device State Model is Embedded in a Device Class Hierarchy Built on Top of the Position Class HierarchyHierarchy Built on Top of the Position Class Hierarchy

15 May 2003 UNCLAS

SIFIED15

DB03-124

Impact of Implementation on Impact of Implementation on ArchitectureArchitecture

Implementation Required Refinement of the Implementation Required Refinement of the Architecture’s Initial Set of Attributes, Services, and Architecture’s Initial Set of Attributes, Services, and NotificationsNotifications

Services, Attributes, and Notifications were Renamed to Services, Attributes, and Notifications were Renamed to Enhance Naming Consistency Across Components.Enhance Naming Consistency Across Components.

Services, Attributes, and Notifications were Added to Services, Attributes, and Notifications were Added to Ease Necessary Component InteractionsEase Necessary Component Interactions

Components were Consolidated to Enhance Components were Consolidated to Enhance EncapsulationEncapsulation

15 May 2003 UNCLAS

SIFIED16

DB03-124

Example Munition Domain Example Munition Domain Component ConsolidationComponent Consolidation

MunitionMunitionPredictor

Physical MunitionDevices

LauncherDomain

MunitionOperator

MunitionDevices

BEFORE

AFTERMunitionPredictor

Physical MunitionDevices

LauncherDomain

Munition

MunitionDevices

15 May 2003 UNCLAS

SIFIED17

DB03-124

FC-NET XD1 Source Code StructureFC-NET XD1 Source Code Structure

FC-NET is Written in ANSI C++FC-NET is Written in ANSI C++

XD1 Application is Built on a Multi-Tiered Foundation of XD1 Application is Built on a Multi-Tiered Foundation of Supporting ClassesSupporting Classes

Every Application Component Runs as an Independent Every Application Component Runs as an Independent ProcessProcess

XD1 Application CodeXD1 Application Code

FC-NET Fire Control Foundation Classes

FC-NET Fire Control Foundation Classes

XD1 Skeleton ClassesXD1 Skeleton Classes

FC-NET Communications Library

FC-NET Communications Library

15 May 2003 UNCLAS

SIFIED18

DB03-124

ConclusionsConclusions

The Architecture is FeasibleThe Architecture is Feasible

Implementing Components as Separate Processes HasImplementing Components as Separate Processes Has

– Eased Assignment of Programming Tasks to Developers

– Reduced Developer Interdependence During Testing

– Eased Construction of Test Clients and Subsystems

– Eased Fault Isolation

Communication Overhead of Separate Processes is Communication Overhead of Separate Processes is Acceptable, Even in Initial ImplementationAcceptable, Even in Initial Implementation

Use of XML Files Provides Flexible, Uniform, and Readable Use of XML Files Provides Flexible, Uniform, and Readable Component Configuration CapabilityComponent Configuration Capability

15 May 2003 UNCLAS

SIFIED19

DB03-124

Contact InformationContact Information

Joel SherrillDirector of Research and Development

OAR Corporation

4910-L Corporate Drive

Huntsville, AL 35805

Voice: 256-722-9985

FAX: 256-722-0985

Joel.Sherrill@OARcorp.com

Deborah A. ButlerFC-NET Program Manager

U.S. Army Aviation and Missile Command

ATTN: AMSAM-RD-MG-NC (Deborah A. Butler)

Redstone Arsenal, AL 35898-5000

Voice: 256-876-1303

FAX: 256-876-9476

Deborah.Butler@rdec.redstone.army.mil