Pocket sized Forward Entry Device P-FED

1. 01/02/03 Pocket sized Forward Entry DeviceP-FED

2. 01/02/03 2 Purpose Background Requirements System Overview Acquisition Strategy Cost Estimates Supported Mission Types Messaging Capabilities Agenda

3. 01/02/03 3 Purpose Provide a status of the P-FED and a description of material to be fielded Present the Fielding Plan Present the Training Plan

4. 01/02/03 4 P-FED Background 1QFY01 Contract Awarded 2QFY02 Initial User Evaluation 1QFY03 Systems Integration Completed 3 QFY03 Material Release Oct 03 Customer Test Conducted at Ft Sill (Army) (2004-CT-FS-PFEDX-A0772) Army had some problems caused by their ConOps Nov 03 Presented to 11th Marines Dec 03 Marines conducted same test with 100% success rate Dec 03 11th Marines conduct live fire testing/training Mar 03 10th Marines conduct live fire testing/training Apr 03 CG MARCORSYSCOM ordered P-FED fielded as soon as possible

5. 01/02/03 5 THDHS Requirements TLDHS Block II as a system is required to: Identify, locate, and designate targets. Communicate with Aircraft, AFATDS, and NFCS. Transmit requests CAS (to include 9 line briefs), calls for artillery support, and naval surface fires. Due to funding constraints,some of the TLDHS Block II components are still under development or are not currently meeting Requirements. Because of this the TLDHS as a system is behind schedule for an undetermined duration

6. 01/02/03 6 An Interim Solution toTHDHS Blk II The Pocket Forward Entry Device (P-FED) software application: Software is Government owned and available through the Army PMIE at Ft Monmouth. Interfaces with Laser Range Finders currently resident in the Fleet. Sending Calls For Fires (CFFs) and all fires related messages to the AFATDS. Provides a capability for Observer to transmit Fire Plans. As an Interim Solution, the P-FED will satisfy the ground fires requirement for automation by employing existing capabilities now.

7. 01/02/03 7 Pocket Sized Windows CE Systems - Hardware Independent - C++ Based - Lightweight - Low Power Provide Core Forward Capabilities Easy-to-Use, Intuitive Graphic User Interface (GUI) Interoperates with AFATDS

8. 01/02/03 8 Compatible with the Following Equipment: - SINCGARS SIP and ASIP: - PLGR - MELIOS MK-7 LASER Ranging Binos - Leica Vector 4 LASER Ranging Binos Uses Standard Two-Way Communications and Messaging: - MIL STD 188-220 - TACFIRE FSK/NRZ - Army VMF/Joint VMF - Bluetooth (wireless) - Sensor Link Protocol (SLP)

9. 01/02/03 9 Pocket sized Forward Entry DeviceP-FED Equipment Ruggedized PDA Internal TACLINK Modem External AA Battery Pack Serial Interface to CLRF Serial Interface to GPS-PLGR Capabilities Digitally request/coordinate fire missions Provide combat information and receive orders and information One data port for CNR communication Based on the USA PFED/FOS systems The Pocket-Sized Forward Entry Device (PFED) will be employed by Forward Observer (FO) Operational Facilities (OPFACs) when size and environmental requirements demand a portable, rugged device with processing capabilities. The PFED will be used by FOs for composing, editing, planning and executing FS operations that require a smaller size, lighter weight device than the Forward Entry Device/Lightweight Forward Entry Device (FED/LFED). Utilize TLDHS ORD, O&O as Requirements Documents Establish MOA w/USA PM IE Establish Abbreviated Acquisition Program Leverage all testing performed by USA, ATEC Procure equipment (~$2M) Utilize TLDHS documents to provide logistics, S&E support Fielding PFED device to Artillery Forward Observers while finalizing the TLDHS full up capabilities. From the ARTY OAG Gents, The AOAG fully supports pursuing PFED as interim FO data entry device....we would also support PFED as replacement for the GDUs. This could potentially fix both ends of the digital fire chain that is currently broken. Request you keep the OAG appraised of funding impacts/shortfalls as we pursue this COA. Continue to work on changing the TLDHS CDD....at least the inclusion of the requirement for a voice activated THS. Thanks Col Pace Based on the USA PFED/FOS systems The Pocket-Sized Forward Entry Device (PFED) will be employed by Forward Observer (FO) Operational Facilities (OPFACs) when size and environmental requirements demand a portable, rugged device with processing capabilities. The PFED will be used by FOs for composing, editing, planning and executing FS operations that require a smaller size, lighter weight device than the Forward Entry Device/Lightweight Forward Entry Device (FED/LFED). Utilize TLDHS ORD, O&O as Requirements Documents Establish MOA w/USA PM IE Establish Abbreviated Acquisition Program Leverage all testing performed by USA, ATEC Procure equipment (~$2M) Utilize TLDHS documents to provide logistics, S&E support Fielding PFED device to Artillery Forward Observers while finalizing the TLDHS full up capabilities. From the ARTY OAG Gents, The AOAG fully supports pursuing PFED as interim FO data entry device....we would also support PFED as replacement for the GDUs. This could potentially fix both ends of the digital fire chain that is currently broken. Request you keep the OAG appraised of funding impacts/shortfalls as we pursue this COA. Continue to work on changing the TLDHS CDD....at least the inclusion of the requirement for a voice activated THS. Thanks Col Pace

10. 01/02/03 10 PFED What it is and isn�t IS Entry Device to AFATDS for Artillery Fire Support Light Weight Touch Screen Driven Simulation mission capable Ready to go Interim Solution Isn�t Multi-role (CAS Device) Graphic Enabled No Battlefield Geometries No MAP support BFSA Tool TLDHS Block III

11. 01/02/03 11 TED Acquisition Strategy Utilize applicable parts of the TLDHS ORD, O&O as requirements documents. (Artillery component) Establish MOA w/USA PM IE Establish Abbreviated Acquisition Program Leverage all testing performed by USA, ATEC Procure equipment (~$2M) Utilize TLDHS documents to provide logistics, S&E support. Utilize TLDHS funds to procure and life-cycle maintenance. Utilize NSWC, Crane as integration agent, life-cycle logistics manager. Fielding PFED device to Artillery Forward Observers while finalizing the TLDHS Block III full up capabilities. Establish an AAP � MCCDC agrees that interim solution is possible. MCOTEA concurs that no operational testing is required other than a Marine Corps performed. LUT From the ARTY OAG Gents, The AOAG fully supports pursuing PFED as interim FO data entry device....we would also support PFED as replacement for the GDUs. This could potentially fix both ends of the digital fire chain that is currently broken. Request you keep the OAG appraised of funding impacts/shortfalls as we pursue this COA. Continue to work on changing the TLDHS CDD....at least the inclusion of the requirement for a voice activated THS. Thanks Col Pace Establish an AAP � MCCDC agrees that interim solution is possible. MCOTEA concurs that no operational testing is required other than a Marine Corps performed. LUT From the ARTY OAG Gents, The AOAG fully supports pursuing PFED as interim FO data entry device....we would also support PFED as replacement for the GDUs. This could potentially fix both ends of the digital fire chain that is currently broken. Request you keep the OAG appraised of funding impacts/shortfalls as we pursue this COA. Continue to work on changing the TLDHS CDD....at least the inclusion of the requirement for a voice activated THS. Thanks Col Pace

12. 01/02/03 12 Acquisition Strategy Block 1: Close Air Support (Laser range Finder/THS/PRC-113) Threshold Objective a) Determine Target Location a) Night Vision capable - Range b) PRC-148 interface/procurement - Azimuth - Vertical Angle b) Digitally Handoff Information - F/A 18, DCS 2000 - AV8B, ATHS II Block 1: Close Air Support (Laser range Finder/THS/PRC-113) Threshold Objective a) Determine Target Location a) Night Vision capable - Range b) PRC-148 interface/procurement - Azimuth - Vertical Angle b) Digitally Handoff Information - F/A 18, DCS 2000 - AV8B, ATHS II

13. 01/02/03 13 Acquisition Strategy, Block II Block 2: CAS & ARTY (Laser range Finder/THS/PRC-148/Laser Designator) Threshold Objective a) All previous threshold requirements a) Laser designate targets b) Interoperable with AFATDS Block 2: CAS & ARTY (Laser range Finder/THS/PRC-148/Laser Designator) Threshold Objective a) All previous threshold requirements a) Laser designate targets b) Interoperable with AFATDS

14. 01/02/03 14 Pocket sized Forward Entry DeviceP-FED

15. 01/02/03 15 $$$ UNIT COST ESTIMATES $$$ Block I is Digital CAS with F/A-18 and AV-8B. Begin Fielding December 2002 AAO � 381 VIPER II is being fielded by PTS-180 program. MEF I is fielded. (50 / Month is delivery rate) Plain text communications demonstrated in July with both aircraft. Block II Artillery entry device into AFATDS. Fielding Mid-FY03 Laser Designator, Something like GLTD II (Qnty 75) Digital Precision Strike Suite Block III � Native Application on C2PC Open Architecture capable of operating. Fielding FY04 NSFS, AFAPD Thermal LRF/Designator Precursor to Joint Fire Precision Control software for FIOPBlock I is Digital CAS with F/A-18 and AV-8B. Begin Fielding December 2002 AAO � 381 VIPER II is being fielded by PTS-180 program. MEF I is fielded. (50 / Month is delivery rate) Plain text communications demonstrated in July with both aircraft. Block II Artillery entry device into AFATDS. Fielding Mid-FY03 Laser Designator, Something like GLTD II (Qnty 75) Digital Precision Strike Suite Block III � Native Application on C2PC Open Architecture capable of operating. Fielding FY04 NSFS, AFAPD Thermal LRF/Designator Precursor to Joint Fire Precision Control software for FIOP

16. 01/02/03 16 $$$$ TOTAL COST ESTIMATES $$$$ Material Cost is 10,910 per unitMaterial Cost is 10,910 per unit

17. 01/02/03 17 Supported Mission Types TLDHS Supported Missions Registration FFE/Adjust Fire Joint Tactical Air Request Immediate Suppression/Smoke SEAD Copperhead Priority Target FPF FASCAM Check Fire PFED Supported Missions FFE/Adjust Fire Immediate Mission Smoke Mission FPF Check Fire

18. 01/02/03 18 Message Capabilities for PFED Block 1: Close Air Support (Laser range Finder/THS/PRC-113) Threshold Objective a) Determine Target Location a) Night Vision capable - Range b) PRC-148 interface/procurement - Azimuth - Vertical Angle b) Digitally Handoff Information - F/A 18, DCS 2000 - AV8B, ATHS II Block 1: Close Air Support (Laser range Finder/THS/PRC-113) Threshold Objective a) Determine Target Location a) Night Vision capable - Range b) PRC-148 interface/procurement - Azimuth - Vertical Angle b) Digitally Handoff Information - F/A 18, DCS 2000 - AV8B, ATHS II

19. 01/02/03 19 TLDHS Message for FFE/Adjust

20. 01/02/03 20 QUESTIONS ??