PERFSOO08R0056.doc
DOC document 85 KB Posted
- Solicitation number
- N00421-08-R-0056
View the file
Other files
Show all 33
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
N00421-08-R-0056
STATEMENT OF OBJECTIVES
FOR THE
AIRBORNE SYSTEMS TRAINING AND RESEARCH SUPPORT
AIRCRAFT REPLACEMENT
8 APRIL 2008
1.0 Overview
The primary goal of the program is to provide the United States Naval Test Pilot School with replacement asset or assets to conduct a ground and flight training syllabus to test and evaluate multiple sensor, integrated systems. The purpose of this Statement of Objectives (SOO) is to provide the basic objectives for the replacement aircraft in lieu of a Government Statement of Work. This approach provides the potential offerors the flexibility to propose cost effective and innovative solutions in meeting the objectives. This SOO is to be used by potential offerors to develop an appropriate Statement of Work, Provisioning Technical Documentation (PTD), Provisioning Parts List (PPL), Transition Plan, Contract Work Break Down Structure (CWBS) as required, Contract Data Requirements List (CDRLs), and other documents that support and define the offerors proposed effort.
1.1 Background
Since the mid-1990’s the two NP-3D Airborne Systems Training and Research Support (ASTARS) aircraft have been an integral part of the U.S. Naval Test Pilot School (USNTPS) Airborne Systems ground and flight training syllabus. It was designed to expose test pilots, Naval Flight Officers, and test engineers to a highly integrated avionics system as well as support instruction in the test and evaluation of individual navigation and tactical sensors through the use of installed instrumentation. Its configuration is similar to the centralized architecture used in next-generation aircraft such as the F-22 and Joint Strike Fighter. All processing is performed in multiple commercial rack-mounted off-the-shelf personal computers. Multi-Function Displays (MFDs) are emulated using Cathode Ray Tube (CRT) and Liquid Crystal Display (LCD) video monitors with added bezel buttons. Aircraft configuration currently includes a mock strike-fighter cockpit student station equipped with multi-function hand controllers, as well as an instructor station equipped with similar controls and displays. Current sensor suite includes a multi-mode X-band radar (APG-66(V)2), a turret-mount EO/IR (Electro-Optic/Infrared) sensor (Wescam MX-15) and an Inertial Navigation System (INS) with Global Positioning System (GPS) aiding. A Head Up Display (HUD) is simulated using a cockpit-mounted camera with overlaid symbology. The system also includes a digital moving map with full continental U.S. coverage. The current NP-3D inventory is used during approximately 35 weeks per year and accumulates 300 flight hours annually.
The current NP-3D aircraft are two of the oldest in the U.S. Navy, and therefore have become increasingly more difficult to support as similar aircraft are retired and parts support has significantly decreased. At the same time, inflationary pressures have increased the cost to maintain and operate these aircraft at a time when budgets continue to shrink. Finally, the large size of the NP-3D provides space for growth potential far beyond what is necessary.
1.2 Contract Objectives
The goal of the ASTARS Aircraft Replacement program is to provide performance based requirements that give the contractor program and management authority to meet system demand requirements, improve availability, reliability, and manage obsolescence. Baseline design goals should include:
1.2.1 Provide an integrated system of sensors, controls, and displays typical of current and future tactical aircraft.
1.2.2 Provide support and instrumentation systems typically employed in developmental test aircraft.
1.2.3 Allow complete control of entire sensor suite from either of two operator stations.
1.2.4 Allow instructor monitoring of all student actions.
1.2.5 Allow continuous ground operation with no overheating.
2.0 Program Objectives
2.1 General Aircraft Requirements
2.1.1 Crew
2.1.1.1 No more than 2 pilots required.
2.1.1.2 No non-pilot flight crew (flight engineer, observer, etc.) required.
2.1.1.3 During systems training within local restricted areas, one pilot seat may be occupied by a test pilot student under instruction.
2.1.1.4 Seating to accommodate a minimum of 4 students and 2 instructors (including the two operator stations).
2.1.2 Support
2.1.2.1 All aircraft modifications, to include installation of any provided GFE, will be accomplished by the contractor.
2.1.2.2 Use government provided fuel when supporting USNTPS missions.
2.1.2.3 Contractor use other than support to USNTPS curriculum normally restricted to maintenance and ferry flights (no ASTARS system operation). All other flights require specific approval from the Commanding Officer, USNTPS.
2.1.2.4 Aircraft sustainable with equipment in the current Navy inventory (no special government ground support equipment required).
2.1.2.5 Maintain all GFE in accordance with applicable instructions.
2.1.2.6 Aircraft available to USNTPS use 40 weeks per year, non-contiguous.
2.1.3 Performance
2.1.3.1 Instrument rated aircraft
2.1.3.2 Power and cooling budget for all ASTARS sensor systems (including radar) to operate simultaneously during ground and airborne operation.
2.1.3.3 Adequate power and cooling to operate all systems and sensors (including the radar) continuously for at least 3 hours on the ground with no overheating and no additional ground support equipment.
2.1.3.4 Endurance to operate at normal cruising speed for at least 4 hours, with sufficient Instrument Flight Rules (IFR) reserve.
2.1.3.5 Capable of carriage of high-density information system or external advanced range data system pod to support Atlantic Test Range time, space, and position information data.
2.2 Navigation System
2.2.1 Include a Global Positioning System aided navigation system.
2.2.2 At least two independent navigation systems.
2.2.3 Capability to look at time and position information from each system concurrently.
2.2.4 Instrumentation to allow for recording raw navigation and sensor data to digital media for student post-flight analysis.
2.3 Operator Stations
2.3.1 Two operator stations with all the following items required at each station.
2.3.2 Seating for one student to operate all controls and displays, and one seat for an instructor or student observer.
2.3.3 Seating with adequate design and restraint to be manned for all phases of flight.
2.3.4 Station configuration not required to look like a specific tactical aircraft cockpit though all in-flight operation must be accomplished while seated at the operator station.
2.3.5 Cabin configuration to allow for instructor oversight of each of the student stations with no obstructions.
2.3.6 At least four multifunctional displays or equivalent functionality.
2.3.7 Two hand control units to control all sensor and display functions.
2.3.8 Communications system at each operator station with the following:
2.3.8.1 Hot microphone or voice actuated internal communication system (ICS) to the instructor and other students using ASTARS.
2.3.8.2 Selectable ICS capability for student and instructor communication to the pilot(s).
2.3.8.3 ICS available with power on aircraft.
2.3.8.4 UHF/VHF radio transmit and receive capability with selectable channels from the operator stations.
2.4 Data Recorders
2.4.1 Capable of recording at least three video inputs.
2.4.2 Capable of being loaded, unloaded, and accessed during flight.
2.4.3 Selection of parameters to be recorded capable of being changed (new or different parameters selected) in flight.
2.4.4 Capable of recording ICS and radio communications.
2.4.5 Instrumentation to display and record data parameters (e.g., radar, navigation, mission data, etc.).
3.0 Support
3.1 Additional Software and Hardware Requirements
3.1.1 Software to use an open architecture.
3.1.2 Hardware to be reconfigurable to the maximum extent possible.
3.2 Configuration Management
3.2.1 Update software configurations, hardware configurations, and users’ manuals and provide a copy to the Commanding Officer, USNTPS, within two weeks of any changes.
3.3 Technical Publications
3.4.1 Source code to be provided to the government (as applicable).
3.4.2 Provide access to all source code for system integration.
3.4.3 Provide an interface design description for all systems.
3.4.4 Maintain and provide to USNTPS staff a copy of all software and hardware configurations.
3.4.5 Maintain and provide to USNTPS staff a copy of all users’ manuals pertinent to training system operations.
3.4 Technical Training
3.4.1 Provide initial training to USNTPS instructor staff personnel on system operation.
3.4.2 Provide refresher and new instructor staff personnel training on system operation at least yearly, or as major changes are incorporated in the system.
PAGE
ASTARS SOO 03072008.doc
File details come from the government source that posted it. Updated .