R&D Contracting, Bldg 7, 2530 C Street, WPAFB OH 45433-7607

A -- COMBAT FLIGHT MANAGEMENT TECHNOLOGY RESEARCH PROGRAM - NOTICE: THIS ANNOUNCEMENT IS IN TWO PARTS. THIS IS PART 1 OF 2. SOL PRDA 96-05 FIK POC Edward J. Caulfield, Contract Negotiator, (513) 255-5901 Lawrence W. Kopa, Contracting Officer, (513) 255-5901. A--NOTE: THIS ANNOUNCMENT IS IN TWO PARTS: THIS IS PART PART 1 OF 2. INTRODUCTION - Wright Laboratory (WL/FIKA) is interested in receiving proposals (technical and cost) on the research effort described below. Proposals in response to this PRDA shall be submitted within 45 days of the date of this announcement by 1500 hours Eastern Time to Wright Laboratory, Directorate of R&D Contracting, Building 7, 2530 C Street, Area B, Attn: Mr. Ed Caulfield, WL/FIKA, Wright-Patterson AFB OH 45433-7607. This is an unrestricted solicitation. Small businesses are encouraged to propose on all or any part of this solicitation. Proposals submitted shall be in accordance with this announcement. Proposal receipt after the cutoff date and time specified herein shall be treated in accordance with restrictions of FAR 52.215-10, copy of this provision may be obtained from the contracting point of contact. There will be no other solicitation issued in regard to this requirement. Offerors should be alert for any PRDA amendments that may be published. Offerors should request a copy of the WL guide entitled ''PRDA and BAA Guide for Industry.'' This guide was specifically designed to assist offerors in understanding the PRDA/BAA proposal process. Copies may be requested from the contracting officer cited above. B--REQUIREMENTS: (1) Technical Description: The purpose of this effort is to develop and integrate off-board information fusion, in-flight mission planning, trajectory generation with flight control coupling, and pilot-vehicle interface technologies into a flight management system to demonstrate reduced workload and increased situation awareness for single-seat fighter pilots flying air-to-surface missions, enabling maximum exploitation of off-board information. This effort is also to mature the technology for low-risk and affordable transition to existing and future systems. Offerors must plan for at least three major tasks in this effort. The first major task, System Analysis, will include a review of mission requirements, technology availability, and any other information necessary to define functional requirements, interface requirements, and the preliminary system design. The contractor should accomplish a mission level analysis, with validated scenarios, to determine potential improvements in survivability and lethality due to CFM technology integration. Campaign level outcomes should then be extrapolated. The System Analysis task is expected to last approximately nine months. The second major task, Development and Integration, will develop and integrate the system into ''hot-bench'' simulation to verify system functionality. Development and integration is expected to take approximately 33 months. The third major task is Evaluation and Demonstration. The contractor shall select appropriate metrics and conduct one or more piloted simulation evaluations to measure system performance, pilot workload, and pilot acceptability. The contractor shall show mission effectiveness in terms of lethality and survivability. The contractor shall demonstrate the maturity of the system by using hardware and software that, as close as practical, approximates a fielded configuration. The last task is expected to take 18 months. (a) System objectives: Software will be in Ada, unless otherwise approved. Offerors will define and provide a baseline system for off-board information fusion. In-flight mission planning, flight control automation, and cockpit controls and displays will be developed and integrated with the baseline off-board information architecture to allow automatic plan generation, when appropriate, for pilot acceptance. (b) In-flight mission planner objectives: The mission planner must be compatible with use of the Air Force Mission Support System (AFMSS) ground based mission planner. It will initially accept an AFMSS prepared plan and the data required to re-plan. As off-board information indicates a changed threat or target, the planner will assess the new information for relevance, and prepare a new plan for pilot acceptance. New plans will also be generated based on deviations from the accepted plan, and on pilot command. Plan generation must require no more than five seconds. The in-flight planning system needs to be highly automated to involve less manual input than the ground-based AFMSS. Mission plans should take into account the best available wind information (forecast or observed). The planner should create a whole plan terminating with a landing at the primary recovery base. The pilot should have the ability to tailor the behavior of the system in terms of the allowable airspeed, altitude, fuel used, time required, steer-point locations, and other flight parameters for any segment, as well as primary and alternate target(s) and recovery base. The pilot should be able to insert planned delays at any point for contingency time and fuel usage. The planner should continually calculate ''bingo'' fuel. The pilot should be able to select either detection avoidance navigation or threat avoidance navigation (DAN/TAN) priority. Normally, the system should plan, in order of priority, to: 1) execute the Air Tasking Order (ATO) while meeting the pilot's and all other flight restrictions, 2) land at the primary recovery base with at least the pilot's selected minimum fuel remaining, 3) do so with minimum threat exposure, and 4) use minimum fuel. Plans for mission abort, and diversion to an alternate recovery base should be continuously maintained. (c) Trajectory generation and flight control automation objectives: Flight trajectories for combat tasks will be generated for the mission planner to assemble into an overall plan and for coupling to the flight controls. Such tasks should include: orbiting, holding, high, medium, and low altitude (terrain masking) threat avoidance navigation, sensor use for target search and acquisition, Maverick missile delivery, bomb (un-guided, inertially guided, and laser guided general purpose and cluster bomb) deliveries (dive, level, and loft) against single and multiple aimpoints, laser target illumination, and target area egress. Full time automatic ground collision avoidance should be available. Auto-throttle commands should provide control commands to meet speed and timing constraints, or to maintain a desired mach. Flight control automation will couple the auto-pilot to the mission plan for hands-off flying to reduce pilot workload and allow the pilot to devote more attention to target recognition, sorting, and aimpoint selection, as well as defensive situation awareness. A pilot-directed auto-pilot mode should allow for automatic altitude (AGL and MSL) and speed control, but with manual steering, for reduced workload when there is no desired trajectory available for automatic following. Flight safety critical components must be reliable in order to maintain pilot trust and to insure that no system failure will result in commands that would cause aircraft loss. (d) Pilot-vehicle interface objectives: Advanced pilot vehicle interface technologies, such as a helmet mounted display with synthetic (computer rendered) terrain imagery, speech recognition, and color displays, should be included to increase pilot situation awareness and allow low effort pilot control. The interface to the flight planner must be designed so that new mission plans are easily understood, easily modified if necessary, and easily implemented by the pilot. Interfaces between the pilot and the flight control system must allow for automatic trajectory following without confusion about what it is doing and what it is about to do. The pilot must be able to easily monitor the system, quickly ascertain the validity of an automatic solution, and manually intervene at any time for any reason, while maintaining the option of resuming the plan or generating a new plan. (2) Program Reviews: The kick-off meeting will be held at WPAFB, and all subsequent meetings will be at contractor facilities. Each major task will end with a program management review. Technical interchange meetings will be held approximately every six months. Informal project engineer visits will be more frequent and as necessary to monitor progress. (3) Deliverable Items: Data and Reports: The following list is provided as a guide. Offerors should select data items appropriate to their proposed effor: Scientific and Technical Reports, Final Report, DI-MISC-80711/T, HE Progress Report (HEPR), DI-HFAC-80741A/T (annual), HE Test Plan (HETP), DI-HFAC-80743A/T (Each Evaluation), HE Test Report (HETR), DI-HFAC-80744A/T (Each Evaluation), HE Design Approach Document-Operator (HEDAD-O), DI-HFAC-80746/T, System/Subsystem Specification (SSS), DI-IPSC-81431/T, Interface Requirements Specification (IRS), DI-IPSC-81434/T, System/Subsystem Design Description (SSDD), DI-IPSC-81432T, Interface Design Description (IDD), DI-IPSC-81436/T, Software Requirements Specification (SRS), DI-IPSC-81433/T, Software Version Description (SVD), DI-IPSC-81442/T, OPSEC Plan, DI-MGMT-80934, Status Report, DI-MGMT-80368/T (quarterly), Contract Funds Status Report, DI-FNCL-81468/T, Contractor's Billing Voucher, DI-MISC-80711/T, Project Planning Chart, DI-MGMT-80507A/T, Funds and Man-Hour Expenditure Report, DI-FNCL-80331/T, Presentation Material, DI-ADMN-81373/T, Data Accession List, DI-MGMT-81453/T, Still Photo Coverage, DI-MISC-80169, Technical Videotape Presentation, DI-MISC-81275/T, (4) Security Requirements: TEMPEST requirements will apply. The contractor may require access to classified information at the secret level. Generation of classified material for this solicitation effort is authorized only on equipment approved for classified processing by Air Force TEMPEST authorities. A Contract Security Classification Specification, DD Form 254, will be required in any resultant contract award. (5) Other Special Requirements: International Traffic in Arms Regulation applies. THIS IS THE END OF PART 1. (0092)

Loren Data Corp. http://www.ld.com (SYN# 0001 19960402\A-0001.SOL)