FA8650-17-S-6001-Atch1d.pdf
PDF 20 KB Posted
- Attached to
- Science and Technology for Autonomous Teammates (STAT) Federal contract opportunity
- Solicitation number
- FA8650-17-S-6001
About this file
This file contains a test plan format data item description to be used in conjunction with an Air Force Research Laboratory contract for flight and taxi testing. The test plan outlines the contractor's approach for conducting tests on systems or equipment to demonstrate how program objectives will be achieved safely and efficiently. It includes sections for an overview, test item description, method of test, special procedures, test management, mishap procedures, attachments, and additional details for tests involving remote-controlled or autonomous vehicles.
The related federal contract opportunity is a solicitation from the Air Force Materiel Command Research Laboratory seeking proposals to develop and demonstrate autonomy technologies through the Science and Technology for Autonomous Teammates program. Specific areas of interest include command and control across domains, manned-unmanned teaming, and information analytics. The goal is to enable airmen to plan and execute multi-domain missions with manageable workloads through technologies that can ingest and respond to tasks and intent, directions, threats, and unplanned events in an open, reusable, and platform-agnostic manner. Funded efforts will integrate technologies into demonstrations and deliver software, hardware, and documentation to support modeling and simulation for future capability development.
Flight Taxi Format
View the file
Other files for this federal contract opportunity
Show all 50
Science and Technology for Autonomous Teammates (STAT) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
AFRL Flight/Taxi Test Plan Format To Be Used In Conjunction With
DID DI NDTI 80566/T.
Block 3: DESCRIPTION/PURPOSE
3.1 The test plan outlines the plans and test approach/objectives at every level of testing on systems or equipment. It provides the procuring activity with the test concept, objectives, approach, and success criteria.
Block 7: APPLICATION/INTERRELATIONSHIP
7.1 The DID contains the format and content preparation instructions for the data product generated by the specific and discrete task requirements as delineated in the contract.
7.2 This DID is applicable to system and equipment flight and ground tests that include tests, experiments, demonstrations on facilities or aerospace vehicles, where aerospace vehicles are defined as, but not limited to, manned vehicles, R/Cs, uninhabited air vehicles (UAVs), and RPVs.
Block 10: PREPARATION INSTRUCTIONS
10.1 General. The test plan shall document in detail the contractor’s plan for conducting tests and associated ground tests and analyzing the test results to show how the system will satisfy the program objectives in a safe and efficient manner.
10.2 Format. The plan shall be in the contractor’s format.
10.3 Content
10.3.1 Title Page. The title page shall include the following:
a. Title of the test to be conducted
b. Identification of system being tested
c. Contractor’s name
d. Contract number
e. Security classification
f. Distribution statement
10.3.2 Overview. Consists of purpose of test; program discussion; program objectives, metrics, and success criteria; background information; previous related tests (ground tests, simulations, other similar tests); critical technical and safety issues. The plan shall include the following:
10.3.3 Test Item Description. Consists of description of test item; vehicle description (size, shape, dimensions photo or drawing, weight, speeds, payload capacity, instrumentation, payload, power requirements/power available, etc.); vehicle modifications and configuration control process/approval; autonomous flight control system description; other test/support equipment, and any other pertinent parameters.
10.3.4 Method of Test. Consists of detailed test approach and procedures;
instrumentation; data requirements, processing, and analysis; test location (map or photo of area, test area marked on map, test patterns marked on map, location of test personnel and equipment on map); detailed discussion and description of each test (taxi, checkout, ground and flight test descriptions, number of tests/flights, purpose, objective and success criteria of each test/flight, vehicle configuration per flight, airspeeds, altitudes, flight patterns, detailed discussion of how each ground and flight test will be conducted from start to finish, contingency plans, etc.); communications (hand held radios – channels authorized/used, radio and test terminology, identification and responsibilities of test personnel, etc.); deviations requested from test plan; test and safety go/no go lists; test execution success criteria.
10.3.5 Special Procedures. Consists of unique maintenance procedures; test constraints or limitations; security procedures or guidelines to be observed; required special or unique tests.
10.3.6 Test Management. Consists of program schedule; planned test start and end dates;
personnel (identification of personnel and responsibilities of each); required support.
10.3.7 Mishap Procedure and Reporting. Consists of discussion of emergency equipment and services available; discussion of process for handling toxic materials; mishap reporting procedures.
10.3.8 Attachments. Consists of test cards for each individual test; test hazard analyses;
pre and post flight/test checklists; standard operating procedures for test location; flight clearances; agreements with other supporting organizations; frequency management documents, and test results.
10.3.9 Additional sections required for tests involving R/Cs, UAVs, RPVs. radio and transmitter (type and frequency); location of kill boundary on map; flight termination system / procedure (description of system / procedure and how it works, who calls the kill signal); autonomous control system, pilot name and qualifications.
File details come from the government source that posted it. Updated .