C4ISR and Networked Fires

C4ISR and Networked Fires
Precision Strike Association Annual Symposium April 21, 2004 MAJ (P) Dave Bassett PM Software Integration (Provisional) Fort Monmouth, NJ Program Manager’s Intent: Field FCS-equipped Units of Action with Threshold Future Force Capability by the End of the Decade

Outline Program Introduction C4ISR capabilities Networked Fires

FCS Unit of Action Elements One Team Partner Responsibilities
Manned Ground Vehicles Network / Software / C4ISR Command & Control Infantry Carrier Medical Mounted Combat Sys Recon & Surveil. NLOS mortar NLOS Cannon Maint. & Recovery 102 49 60 30 18 24 10 29 General Dynamics / United Defense Battle Command & Mission Execution – Raytheon SOSCOE / Warfighter Machine Interface – Boeing Level 1 Fusion – Lockheed Martin Sensor Data Mgmt / Planning & Prep – GDDS Situation Understanding – Austin Info Systems Network Management – Northrop Grumman Integrated Computer System – General Dynamics Unattended Ground Sensors – Textron Ground Sensor Integration – Raytheon Air Sensor Integration – Northrop Grumman Ground Comm & Air Comm – BAE Systems Unmanned Air Vehicles Logistics & Training LDSS – Northrop Grumman PSMRS – Honeywell Training Support – Northrop Grumman – Dynamics Research Corp – Computer Science Corp Class IV - 2 Northrop Grumman Class III - 12 Class II - 36 Class I - 54 Unmanned Ground Vehicles NLOS LS (LAM, PAM) 60 Intelligent Munition System Trucks 376 81 mm Mortar 12 RAH-66 Comanche 12 AAFARS 2 , HTARS 2 Armed Robotic Vehicle United Defense Mule Lockheed Martin Small UGV iRobot 45 81 78 Auto. Navigation - GDRS Unattended Munitions Non-FCS Elements

FCS Program Master Schedule
FY2002 FY2003 FY2004 FY2005 FY2006 FY2007 FY2008 FY2009 FY2010 FY2011 FY2012 FY2013 CY2002 CY2003 CY2004 CY2005 CY2006 CY2007 CY2008 CY2009 CY2010 CY2011 CY2012 CY2013 MS B MS B Update OIPT PDR NMMDR DCR DRR IOC FOC FRP SRR SFR IPD #1 IPD #2 IBR I IBR II LUT/OE IOT System Development and Demonstration Concept and Technology Development Production and Deployment Science and Technology and CTD leading to future technology insertions and Increments MS B - Milestone B IOT – Initial Operational Test OIPT - Overarching Integrating Process Team FOC – Full Operating Capability IBR - Integrated Baseline Review SRR – System Readiness Review PDR - Preliminary Design Review DCR – Design Concept Review DRR – Design Readiness Review IPD – Initial Production Decision IOC – Initial Operating Capability SFR – System of Systems Functional Review LUT/OE – Limited User Test / Operational Evaluation NMMDR – Network Maturity Milestone Decision Review Network Maturity Milestone Decision Review (NMMDR) – 7/11/2008 Initial Production Decision #1 (IPD #1) – 11/14/2008 Initial Production Decision #2 (IPD #2) – 8/14/2009

Open Software Architecture
C4ISR Overview Information Domain Joint Common Database Common Operating Picture HQ ESO Information Layer “UA Infosphere” Open Software Architecture Logical Database Interoperable export CROP RT Synchronization Computing and Networking Information Management Common Services Planning Fires & Effects Information Ops RSTA C4ISR Mgmt Sustainment Situation Awareness Execution Intelligence Airspace C2 Training & Rehearsal Nontactical Support FIOP Interoperability Domain JTRS EPLRS SINCGARS VHF Link 4A Link 11 Link 16 Reachback Warfighter Interface HHQ XX Battle Command ESO HQ UE/HQ WIN-T Hierarchical Ad-Hoc Network C4ISR Terms of Reference Battle Command - Provides the functions and services to conduct, refine and execute missions Computer System Architecture - Architecture is infrastructure foundation, Open, supports tech insertions over time, and supports application and info mgmt abstraction layer Planning and Preparation - Supports development of plans and the preparation of the Unit of Action to execute them Situation Understanding - builds a sufficient understanding of the situation for that role that seeing first and acting optimally is the most likely outcome Sustainment - Provides status on physical and functional availability on both platforms and soldiers from which readiness can be derived to support Command and Control and Logistics Training - Training provides the capability of immersing the C2 system into an environment indistinguishable from reality with respect to the employed functionality Warfighter Machine Interface - Integrates the FCS warrior’s visualization and interaction needs for data and services across all manned ground vehicles and support equipment MOSAIC MOSAIC stubnet Data Images Voice Video Vetronics UGS Common Vehicle Subsystems Platform Systems Domain EO/IR EO/IR SAR/MTI CROP CROP CROP CROP Network-Centric Warfighting Domain O&O V1.0

System of Systems Common Operating Environment (SOSCOE)
"Approved for Public Release, Distribution Unlimited TACOM 9 Sept 2003"

Domain Application Interfaces with SOSCOE “Family” of APIs
FCS MGV Systems FCS UMV FCS Training FCS Sustainment SoS Common Operating Environment API Services to be exposed to the Domain Applications Common Services Distributed Services The SOSCOE family of Application Interfaces (APIs) provide isolation between the user code (domain Applications) and the SOSCOE services. These isolation APIs allow for the user to be isolated from the implementation of the services such that we can change software over time without having to redo the applications. These APIs are a super set of the WSTAWG OE APIs and APIs developed by the LSI. By defining these APIs early, the FCS industry Partners can develop and test their code is parallel to SOSCOE development. Inter-Service Communication Not exposed To Domain Applications Basic OS Abstraction layer Services OS Services

See First/Persistent ISR
Distributed/Networked Sensors Provides unequaled Situational Awareness down to the Soldier System Enhances survivability through knowing and avoiding enemy fires Enables precision engagement beyond the effective range of the opponent Maintain contact and engagement in detail throughout the mission 03-22

Understand First/Act First/Finish Decisively
CONUS / Higher HQs En Route Planning Rehearsal SATCOM Legend: Interfaces Intra - FCS National ISR Joint ISR Interoperable Joint & Coalition Assets UAV FCS Other Objective Force & Coalition Forces Dismounted Combat Team A NGO NLOS FCS Command C2 Subsystem Networked Fires Using Cooperative Engagements "Approved for Public Release, Distribution Unlimited TACOM 9 Sept 2003"

Networked Fires Process
Networked Fires are comprised of BLOS and NLOS and some LOS (Cooperative Engagement) fires focused to achieve an effect. While the principal applications of Networked Fires will come from NLOS units employing FCS Cannon and NLOS LS systems, BLOS and LOS weapons may be tasked to support Networked Fires. This integrated process consists of the following steps: Step 1: Define/update Attack Guidance. Step 2: Perform ISR Integration Step 3: Detect and locate surface/air targets. Step 4: Provide Intelligence Support to Target Development Step 5: Assign effectors to target. Step 6: Track Targets for Engagement. Step 7: Establish sensor-to-shooter linkages. Step 8: Deconflict mission with air/ground and UE /JIM forces. Step 9: Engage targets Step 10: Conduct Battle Damage Assessment Step 11: Provide re-attack recommendation Conduct Networked Fires-Process consists of a sequence of operational tasks and their associated information exchanges that must be performed to achieve the commander’s intent through the synergistic application of all available lethal and non-lethal effects.

UNCLASSIFIED NLOS-LS Elements LAM PAM Container/Launch Unit CLU Loiter Attack Munition (LAM) NLOS-LS TO BE ONE OF THE “UNATTENDED MUNITIONS” WITHIN THE FCS FAMILY OF SYSTEMS Precision Attack Munition (PAM)

Characteristics/Description:
NLOS-LS System Description Container/Launch Unit Missile Computer & Commo System System Capabilities: Networked, extended range targeting and precision attack of a variety of targets including fleeting high value and both moving and stationary armor Platform independent vertically launched missile system with self contained fire control and communications Automatic/Aided Target Recognition Two-way networked data link Characteristics/Description: FCS UA Core System Transitions Army/DARPA NetFires Demo Program into Development and Production Precision Attack Munition (PAM) 03-35 Loiter Attack Munition (LAM) NLOS

Networked Fires NLOS/BLOS
Class III/IV UAV + JTRS/WNW (3,5,7,9) (4,8) Comm Priority Routine Immediate Flash Flash Override (2) (1,6,10)

Battle Command Software Services
GREEN shading: code procured here But resident in SoSCOE (common service) BLUE shading: code procured elsewhere or developed in-house But resident here Level 1 Fusion Resource Constrained Prioritization Manager Fusion Information Broker Element Multi INT Engine Single INT Battle Command & Mission Execution Order, Report & Authorizer Incoming Order Processor Action Requester Task Organization Policy Editor Airspace Control UGV UAV Manned Ground Vehicle Remote Operation UGS Unmanned Payloads Unattended Munitions Space Fires & Effects Notification Conflict WMI Services Report Generator Role Agent Authorizer Collaborator Intelligent Operator Monitor Presentation Tailor Visualizer Builder Task Integration Network Editor Translation Interface (Text-Voice, etc.) WMI Primitives Core APIs Window Control O/S Interface Terminal Emulators Logon Operator Account Situation Understanding Object Refinement Weather Service Situation SU Toolset Threat Process Readiness Battlespace Priority Battle State Assessor Planning & Preparation Rehearsal Services Simulation AAR Terrain Analyzer Objective Planner Sensor Air Defense Fires&Effects Survivability Security Maneuver Plan COA Comms Network Ground Space Ver Sensor Data Manager SDM Kernel (External Control and Sensor Arbitration) Unit of Action Plug-Ins SDM Sensor Framework (Plug-in control and monitoring) SDM Utilities Non-Organic WMI services are procured and integrated to provide a ‘common look and feel’ for warfighter machine interfaces across C2, all manned platforms within the FCS UA. Situation Understanding (SU) services provide the situation understanding functionality for FCS UA. These services support levels 1-4 fusion (object refinement, situation refinement, threat refinement and fusion process refinement), decision aids and automated assistance. Situation understanding provides the primary input and control of the battle space object (BSO) in the Situation Awareness Database (SADB). Object refinement, which is level one fusion, is procured through the C4ISR Sensors, ATR and Level 1 Fusion SSS, S The C2 Planning and Preparation services provide the deliberate and dynamic, real time planning and analysis capability, virtual and constructive simulation capability, and after action reporting capability for FCS. Battle Command and Mission Execution services provide the operators (commanders, staffs and other users), at all levels with collaborative decision-making, policy, report and order generation, and control of tactical and support resources. The Sustainment service is procured by Supportability, and is shown here to illustrate that Sustainment is an integral part of Command and Control and shares many services developed in the four Command and Control procurements TIN Editor is developed as part of Admin Services in SoSCOE Weather Service is procured by C2, but is resident as a SoSCOE core service

Networked Fires for “Deliver Effects”
A Fires and Effects Thread is primarily comprised of Services within BCME and PPS with input from SU. These Services are linked by the Task Integration Networks (TINs). Services are executed IAW Policies. These are rules for automated processing. They control who shoots what, when, on under on specific authority SoS COE provides data and services via publish/subscribe Conflict Control Next WTP Adjust Fires New Weapon/Target Pairing Prioritize Targets 4.3.1 Deconfliction Successful 4.3.3 BDA Not Required Perform Weapon /Target Pairing 4.3.4 4.3.6 4.3.9 Deconflict Mission Prosecute Target Release Sensor /Effector R A A R R O O R X X R R 4.3.2 Build Effectors List 4.3.5 4.3.7 4.3.8 Command Maneuver Assess Effect Determine Next Action Sensor FEC FEC FEC Mnvr S3 NLOS Bn Sensor FEC FEC The execution of the logic of the Services comprising the TIN can occur throughout the network based on the behavior described by the rules set by the POLICY EDITOR. Gain is less message traffic across the network, faster response, and greater mission throughput vice current the model of serial mission processing

Summary FCS subset of UA subset of UE subset of Joint Forces subset of Multinational Forces (FCS -> UA -> UE -> Joint -> Multinational) FCS Family of Systems defined in ORD Multidimensional System of Systems Integration KPP axis: 7 KPPs Systems axis: MGV, UGV, UAV, NLOS-LS, IMS Components C4ISR = C2 + CC + ISR + SOSCOE SOSCOE Software layer in all FCS Family of Systems Eases integration of distributed capabilities C2: 4 areas: WMI, SU, BC PP SOSCOE and C2 software packages enable Networked Lethality Networked Fires key to the employment of FCS

Backups

FCS ISR Philosophy Be flexible and adaptable Decentralize
Use modular payloads Upgrade easily Locate human interface anywhere Decentralize Collection of small sensors Fuse data locally before hierarchically Analysts can be centralized or distributed Tailor sensors Local area and MOUT sensors for platoons Wide-area coverage for Brigade Deploy SIGINT/ESM widely to detect hidden targets Tailor presentation Reconfigure display to consumer Sensor data types published for subscription Focus organic ISR coverage Exploit UE+ assets for wide-area coverage Deploy organic ISR forward Provide timely sensing Update close, critical regions most often Use local resources for fast response Provide quality sensing Correlate to reduce false tracks due to false, redundant detects Match sensor (and system of sensor) accuracy to weapons Blocked approach Block 1 is strongly capability based but guided by Block 2 directions Block 2 will be more top-down

(Approved for Public Release, Distribution Unlimited)
Integrator Roles System Engineering Translate top-down requirements to sensors Refine internal interfaces Develop platform-to-sensor interfaces Commonality & Growth Ensure commonality of parts Define standard, public interfaces for modularity Develop design principles to reduce upgrade cost/schedule Test Develop V&V plan Integrate SW and HW Support LSI C4ISR SIL (Approved for Public Release, Distribution Unlimited)

The Infosphere Is Our Domain for Information Management
Worldwide information source access Shared and managed information Controlled access to sensitive information Tools and services for info manipulation Tailored information to each user XX Affordable Data Structures That Use Available Worldwide Databases and Information Fusion In Near Real Time

FCS Interfaces and Interoperability
Maneuver C2 JSF MCTIS C2PC TAOM/MCE JWARN AWACS JDP SIAP FIOP EC-3B SIMACET AMPS/ JMPS AH-64D DCTS DTSS TCO GCCS FIA SECOMP-I TCS GIG TAIS FBCB2 GPS SJFHQ Mounted Warrior CAP Vehicle MCS Teleport JNMS A2C2S IBS/GBS UAH Armed Robotic Vehicle TBMCS Mounted Combat System JTRS SISP Land Warrior I/II Infantry Carrier Vehicle IMS C2 Vehicle MILSATCOM JTAGS WIN-T TES Soldier Network Profiler CBRNRS BLT JDISS Paladin AFCS Mule Recon & Surv Vehicle JSOF C2 Networked Battle Command Multi- Mission Radar JSIPS GMLRS Small Unmanned Ground Vehicle Homeland Defense ATACMS HIMARS Intelligent Munitions System FORCEnet MLRS Firefinder DOE DIA Unattended Ground Sensors DCGS NGIC NSA THAAD AFATDS NLOS Launch System DCGS-A - ASAS NIMA CIA PAM MEADS Patriot National Databases JTAGS Sentinel NLOS Cannon UAV Class I Prophet AMDWS FAADC2 ADSI IMETS JWICS LSDIS NLOS Mortar UAV Class II Networked Fires BATES AFWA FED ISR ADOCS Maint Vehicle UAV Class III Comanche Medical Vehicle JLENS M-109A6 PFED UAV Class IV TLAM LFED/FOS WARSIM Shadow 200 Hunter GCSS-A Predator FTTS Chinook CSSCS Aerial Common Sensor NFCS MFCS Blackhawk C2 Constellation Other Army Systems FCS Complementary Systems FCS Family of Systems Joint Systems/Multi-national Red Text = Increment 2 interface CATT TESS TSV TMIP/MC4 DMLSS ADLER DIMHRS TSV DLS CCTT Rivet Joint LAMD FMTV Netwars OneSAF JSTARS LMSR JSIMS Global Hawk IAS GTN Version 3/31/03 Sustainment

Dependent on players within and outside the Army
Role of the LSI Why a Lead Systems Integrator (LSI)… The Army’s first large scale “system of systems” development, integration across many disciplines and platforms, requires a robust / dedicated organization experienced in large scale systems integration What the LSI does… Trusted Industry member of the FCS Team (ARMY /Defense/ Best of Industry) that has total systems integration responsibility (“top down” development) Provides the Team a “general contractor” focused on integration for resource allocation, subcontract implementation and coordination, and programmatic responsibilities Provides the vital link to the “Best of Industry” including domestic / foreign contractors, Government programs / Labs, and educational institutions What the LSI does not… Does NOT provide hardware solutions to subsystem / element requirements “General Contractor” Y2’s house building analogy Synchronize and influence the piece parts which will become the network Dependent on players within and outside the Army 03-40

What Is “One Team” Trusted Partners Trusted Partners
Army, LSI and Industrial Partners Organizationally Integrated All Executing to the Same Plan All Using the Same Processes and Best Practices All Sharing the Same Timely Data for Control and Corrective Action All Incentivized to Share the Same Destiny Army/DARPA The Army’s LSI Best of Industry Trusted Partners Trusted Partners Key Enabler: Electronic Integration for Geographically Dispersed Team with Site-Specific Systems 03-18

What does “Network Centric” Buy Us?
With Empowered Self-Synchronization With Planned Synchronization Execution Lost Combat Power Time New Sciences and Warfare VADM A.K. Cebrowski 9/21/98 Approved for Public Release, Distribution Unlimited TACOM 8 Oct 2003

Building the “Best of Industry” Team
C4ISR UAV UGV Logistics Training Support MGV General Dynamics Bloomington, Minnesota Integrated Computer System PKG 26 Raytheon Company Ft. Wayne, Indiana Battle Command and Mission Execution – PKG 18 Dynamic Research Corp Andover, Massachusetts Training Support Package – PKG 27 United Defense ASD & GSD Bloomington, Minnesota Santa Clara, California MGV ARV – PKG 5 General Dynamics Land Systems Sterling Heights, Michigan MGV General Dynamics Robotics Systems Westminster, Maryland ANS – PKG 9 Textron Systems Wilmington, Massachusetts Unattended Ground Sensors – PKG 15 Boeing – McDonnell Douglas Helicopter Co. Mesa, Arizona Warfigther Machine interface Situation Understanding PKG 23 Northrop Grumman Mission Systems Carson, California Network Management – PKG 17 LDSS – PKG 10 iRobot Corp Burlington, Massachusetts SUGV – PKG 8 Honeywell Defense & Electronics Systems Albuquerque, New Mexico PSMRS – PKG 11 BAE Systems / CNIR Wayne, New Jersey Ground Comm.– PKG 24 Air Comm.-PKG 25 Lockheed Martin Missiles & Fire Control Grand Prairie, Texas MULE – PKG 7 Lockheed Martin (Orincon) Defense Corp San Diego, California Level 1 Fusion – PKG 16 Northrop Grumman - ESD Linthicum, Maryland Air Sensor Integrators- PKG 14 Northrop Grumman Systems Corporation San Diego, California Class !V UAV PKG 1 Computer Science Corp Hampton, Virginia Training Support Package- PKG 27 General Dynamics Decision Systems Scottsdale, Arizona Sensor Data Management – PKG 16 Planning and Preparation – PKG 19 Austin Info Systems Austin, Texas Situation Understanding PKG 20 Raytheon Company Plano, Texas Ground Sensor Integrators PKG 12 Northrop Grumman InfoTech McLean, Virginia Training Support Package- PKG 27 03-19

FCS Network Centric Architecture
Joint Common Database Interoperability Key Performance Parameters HQ FSB Joint Interoperability Networked Battle Command Networked Lethality Transportability Sustainability/Reliability Training Survivability HHQ XX SOSCOE Battle Command HQ FSB UE/HQ Hierarchical Ad-Hoc Network WIN-T WNW WNW The FCS-equipped Unit of Action will be a network-centric unit featuring full interactions between its systems to permit integrated operations and realize innovative Concepts of Operation. The system has no hardware, software, or information stovepipes and no hardwired features. It is fully integrated for information dominance and to make maximum coordinated use of the capabilities of its warfighters, its sensors, and its weapon systems. The Warfighter will interface to other UA systems, Joint and Legacy forces through an integrated C2 system that leverages an open system architecture and modern modular, services-based design. All C2 systems will be common to all warfighting systems and will share a common framework to achieve the long-desired goal of an integrated and interoperable system. The Warfighter’s interfaces and C2 systems will be tightly integrated into each FCS vehicle system with its common and modular subsystems through a Vetronics architecture, achieving a system that is integrated top to bottom. FCS is designed for information superiority through an active Information Management System that makes maximum use of all information sources organic and external to the Unit of Action. Each warfighter will be presented with a synchronized and consistent Logical Database that contains a dynamically updated Consistent Relevant Operating Picture (CROP) to support situational awareness and C2 operations. CROP instances will be synchronized across the Unit of Action by the active Information Management System. The system of Information Management components and Logical Databases comprise the information layer – commonly called the “Infosphere” for the Unit of Action. The data structures of the Infosphere are engineered to be conformal to the Joint Common Database so that Unit of Action situation data can be directly exported to Unit of Employment, higher Army and Theater systems along with a Common Operating Picture that interoperates with the common pictures in the Theater Family of Interoperable Operating Pictures (FIOP). The communications backbone of the Unit of Action will be a hierarchical, ad-hoc wideband network centered on the Joint Tactical Radio System (JTRS) using its Wideband Networking Waveform (WNW). The hierarchical IP-based network will be coordinated by the MOSAIC network management system to ensure scalability and efficient low overhead operation within frequency allocation constraints. JTRS will be common to all vehicles in the Unit of Action, ensuring that communications supports completely coordinated operations with collaboration among systems and efficient transport of the required data, images, voice and video communications data for network-centric operations. Dismounted warfighters will use a JTRS-compliant small form factor radio derived from the Small Unit Operations program and will fully participate in the wideband network – not as a appliqué or adjunct net but as a fully participating set of dismounted subnets. Ubiquitous networked communications permit full expression of the commander’s intent at all levels of the Unit of Action. The Unit of Action is designed to be fully interoperable with other Army forces – the Unit of Employment, legacy forces, and Army forces at Theater command – and the full spectrum of Joint/Theater, National, coalition, and interagency forces. The JTRS software-defined radio permits direct communications over most DoD standard radio and link formats, permitting close interoperability with Navy and Air Force units and Special Operations forces. The Unit of Action integrates with Theater entities of all kinds through the WIN-T system. This permits fully interoperable information environments and data communications at higher levels. Ordinary VHF/UHF radio voice and data formats are supported to permit a wide range of communications with civilian, law enforcement international authorities. The Unit of Action is engineered to link into Ethernet LANs and WANs to allow use of civilian, Federal and DoD internets when the opportunity arises. Data Images Voice Video FCS Advantage: Conflict duration: 50-60% Survivability: 60-80% Logistics footprint: 30-70% JTRS FCS Unit of Action / Unit of Employment “Approved for Public Release, Distribution Unlimited”

Defining Program Relationships: Complementary Programs
UA Battlespace FCS Core: Defined as the 19 Systems specifically called out in the FCS ORD, to include current programs that will be integrated directly into the 19 Systems. FCS is responsible for the integration and procurement of these systems into FCS platforms. JTA FIOP* UA SoS JCAD ACS UA Complementary: Those existing systems essential to get the family of systems to work together but are not part of the FCS Core Systems, or to facilitate operation of an individual core system. They will also have applicability outside the FCS Core Systems. Those systems needed to operate or support a system of systems within the UA but not FCS core systems. Unit set fielding implications. DCGS-A LW Block III C130 Core Systems Future Force Capability Javelin Interoperability RAH-66 UA Complementary Systems TSV C17 UE & Above Complementary Systems UE & Above Complementary: Those systems needed to operate or support a system of systems outside the UA. New/ Proposed Systems Future Increments Technology Base * Family of Interoperable Operational Pictures “Approved for Public Release, Distribution Unlimited”

Integrated Simulation & Test
FCS IPTs by % Work Share Systems Engineering, ACE Unmanned Systems Training Integrated Simulation & Test Supportability Program, Business, and Supplier Management C4ISR MGV * Software distributed throughout IPTs

FCS Increment I FCS Increment I

C4ISR Work Packages General Dynamics – Bloomington, Minnesota
Integrated Computer System – PKG 26 Textron Systems - Wilmington, Massachusetts Unattended Ground Sensors – PKG 15 Boeing, Mesa, AZ Warfighter Machine Interface-PKG 23 Raytheon Company – Ft. Wayne, Indiana Battle Command and Mission Execution – PKG 18 Northrop Grumman Mission Systems - Carson, California Network Management – PKG 17 BAE Systems/CNIR – Wayne, New Jersey Ground Comm.– PKG 24 Air Comm.-PKG 25 Lockheed Martin (Orincon) Defense Corp - San Diego, California Level 1 Fusion – PKG 16 Northrop Grumman Sys Corp – Linthicum, Maryland Air Sensor Integrators- PKG 14 General Dynamics Decision Systems – Scottsdale, Arizona Sensor Data Management – PKG 16 Planning and Preparation – PKG 19 Raytheon Network Systems - Plano, TX Ground Sensor Integrators- PKG 12 Austin Info Systems - Austin, Texas Situation Understanding – PKG 20

C4ISR is a Key Enabler for Sustainment
Provides the functions and services to assess and maintain personnel and equipment readiness, support deployment and operations training Provides status on physical and functional availability on both platforms and soldiers from which readiness can be derived to support Command and Control and Logistics Collects observations on consumption, LRU repair and replacement, delivery and receipt C4ISR is a Key Enabler for Sustainment

C4ISR and Networked Fires

Similar presentations

Presentation on theme: "C4ISR and Networked Fires"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

C4ISR and Networked Fires

Similar presentations

Presentation on theme: "C4ISR and Networked Fires"— Presentation transcript:

Similar presentations

About project

Feedback