Operational Test and Evaluation Force
Operational Test and Evaluation Force (OPTEVFOR) seal
Active	December, 1947 – Present
Country	United States of America
Branch	United States Navy
Type	Systems Operational Testing and Evaluation (OT&E)
Part of	Office of the Chief of Naval Operations (OPNAV) - N091
Garrison/HQ	Norfolk Naval Base, Virginia
Commanders
Current commander	Rear Admiral David A. Dunaway

The Operational Test and Evaluation Force (OPTEVFOR) serves as independent and objective agency within the United States Navy for the operational testing and evaluation (OT&E) of naval aviation, surface warfare, submarine warfare, C4I, cryptologic, and space systems in support Navy and U.S. Department of Defense acquisition programs.

Background
OPTEVFOR traces its origins to the final months of World War II when the need arose for an effective means to combat Japanese kamikaze attacks. On 2 July 1945, the Composite Task Force, U.S. Atlantic Fleet, was formed to develop tactics and evaluate equipment to counter the Kamikazes. This force was commanded by Vice AdmiralWillis A. Lee, USN, and consisted of miscellaneous types of combatant ships and drone aircraft.
Following the end of World War II, the Composite Task Force was consolidated with other fleet units doing development work and in December 1947, was re-designated as the Operational Development Force (OPDEVFOR), with the force commander flying his flag on the USS Adirondack (AGC 15), as an operational command reporting to Commanderic-Chief of te U.S. Atlantic Fleet. In 1949, the command moved ashore to the Norfolk Naval Base. With its expanding OT&E responsibilities, a subordinate liaison command, located the San Diego Naval Base, created to serve as a liaison with the U.S. Pacific Fleet.
VX-6 was one of six air development squadrons formed by the United States Navy beginning in 1946 to develop and evaluate aircraft tactics and techniques. These squadrons were initially directed by the Operational Development Force, which was redesignated in May 1959 as the Operational Test and Evaluation Force (OPTEVFOR). These six squadrons were initially designated as VX-1 (tail code XA), VX-2 (tail code XB), VX-3 (tail code XC), VX-4 (tail code XF), VX-5 (tail code XE) and VX-6 (tail code XD). On 1 January 1969, the surviving Air Development Squadrons (VX-1, VX-4, VX-5 and VX-6) became Air Test and Evaluation Squadrons. Their designations were changed to VXE-1, VXE-4, VXE-5 and VXE-6. Their tail codes of these squadrons were changed to JA, JF, JE and JD, respectively.^[1]
In May 1959, the command was renamed Operational Test and Evaluation Force (OPTEVFOR) to reflect more accurately its increased responsibilities regarding weapon systems and tactics testing and evaluation (T&E). In 1960, the OPTEVFOR headquarters moved to its present location, mocated off Terminal Boulevard near the U.S. Atlantic Fleet headquarters.
Due to Congressional and DOD initiatives to improve the defense acquisition process, in 1971, OPTEVFOR was designated the Navy's sole (OT&E) agency, with greater involvement in the research and development (R&D) process and production decision-making process. In keeping with these expanded responsibilities, the Force Commander (COMOPTEVFOR) began reporting directly to the Chief of Naval Operations (CNO).

Mission
Scope of Responsibilities
COMOPTEVFOR provides OT&E policy direction, technical and procedural guidance, and financial support for the independent and objective testing and evaluation of the systems and tactics at the direction of the Chief of Naval Operations (CNO). For operational control of fleet units, COMOPTEVFOR reports to the Commander, U.S. Fleet Forces Command (COMUSFLTFORCOM); the Commander Pacific Fleet (COMPACFLT); and the Commander, U.S. Naval Forces Europe (COMUSNAVEUR). It also closely follows all R&D programs within the Navy and its laboratories, with the CNO authorizing direct liaison between COMOPTEVFOR and the heads of development agencies involving all technical matters for Navy research, development, testing, and evaluation. Evaluation of systems are done by personnel with technical experience with the equipment being tested and evaluated. Finally, OPTEVFOR coordinates operational test and evaluation (OT&E) activities with the operational test agencies of the other U.S. military services as well as the DOD Director of Operational Test and Evaluation, who establishes operational test policy for the U.S. Defense Department.

Fleet RDT&E Support Process
The Fleet Research, Development, Test & Evaluation (RDT&E) Support Process^[2] conforms to the most current version of SECNAVINST 5000.2 pertaining to Navy or multi-service testing and evaluation (T&E) activities.^[3] It recommends that T&E requests for fleet commander support be made in writing, via CNO-OPNAV (N091/N912), nine (9) month prior to the actual testing activity. The Fleet RDT&E Support Process defines the appropriiate formats for request for T&E activities. Fleet RDT&E Support Process defines the levels of fleet commander support as follows:

• Dedicated support, which precludes employment of the supporting unit(s) in other missions.
• Concurrent support, which permits employment of the supporting unit(s) in activities other than RDT&E support, but could have an operational impact upon unit employment.
• Not-to-interfere-basis (NIB) support, which permits RDT&E operational employment of the supporting unit(s) without significant interference with primary mission accomplishment.

The Fleet RDT&E Support Process also mandates that all T&E requests be submitted and updated on a quarterly basis beginning nine (9) months prior to the quarter that the T&R activity in order to provide adequate scheduling for the fleet command, and manates that CNO-OPNAV (N091/N912) be promptly notified of any cancellations. The Fleet RDT&E Support Process defines prioritization of fleet commander support for T&E activities as follows:

• Priority One - Fleet commander support of a T&E activity takes precedence over normal fleet operations.
• Priority Two - Fleet commander support of a T&E activity takes precedence within normal fleet operations.
• Priority Three - Normal fleet operations take precedence over fleet commander support of a T&E activity.

Finally, the Fleet RDT&E Support Process also defines unscheduled RDT&E support requirements, including the appropriate format for Emergency Fleet Support Requests. The Commander, Operational Test and Evaluation Force (COMOPTEVFOR) is designated as the RDT&E fleet-support scheduling agent for CNO (N091), including all at-sea operational test and evauation (OT&E) activities.

Organization
Command Staff

• Commander Operational Test and Evaluation Force (COMOPTEVFOR) is designated by Chief of Naval Operations to be the sole OT&E authority for the United States Navy, with responsibility for establishing OT&E policy while serving as liaison with senior and subordinate commands throughout the DOD regarding the U.S. Navy's OT&E issues.

• Deputy Commander/Chief of Staff handles the day-to-day operations of the COMOPTEVFOR and its Flag Staff.

• Assistant Chief of Staff for Administration reports to the Deputy Commander/Chief of Staff, providing oversight to the Flag Staff and OPTEVFOR's non-operational programs.^[5]
•  

Divisions
Administration

• COMOPTEVFOR Command Administration Section - This section oversees pay, personnel records, medical, dental, mailrrom operations, central files, and other administrative functions, and is the primary liaison between the command and the Personnel Support Detachment.^[6]
• Facility - This section maintain the headquarters facility, its grounds, and equipment within the OPTEVFOR headquarters area.
• Logistics and Supply - This section provides support for all supplies, equipment, and maintenance needs of the Staff, including all travel and vehicular issues.
•  

Aviation Warfare
The Aviation Warfare Division is responsible for the planning and execution of operational testing and evaluation (OT&E) activities pertaining to the Navy and Marine Corps' aviation acquisition programs. Testing of these programs are done at the following field activities:

• VX-1 - Naval Air Station Patuxent River at Patuxent River, Maryland
• VX-9 - Naval Air Weapons Station China Lake at China Lake, California
• VX-9 Detachment - Marine Corps Air Facility Quantico at Naval Air Station Point Mugu at Point Mugu, California
• HMX-1 - Quantico, Virginia.

These programs include strike/fighter, assault weapon, airborne electronic warfare, air-based anti-submarine warfare, aviation maintenance, and trainer systems.^[7]

• Air C4I & Trainer Systems - This section is responsible for E-2C airborne early warning systems and related trainer programs, including:
  • C-2A(r) Greyhound Block Upgrade/Service Life Extension Program (SLEP)
  • E-2C Combined Engagement Capability (CEC)
  • E-2C Mission Computer Upgrade (MCU) Program
  • Joint Primary Aircraft Training System (JPATS)
• Air Electronic Warfare Programs - This section is responsible for Navy and Marine Corps aviation airborne early warning (AEW) programs, including:
• EA-6B Block 89A Aircraft Upgrade
• EA-6B Improved Capability III (ICAP III)
• AGM-88 High Speed Anti-Radiation Missile (HARM)
• AGM-158 Joint Air-to-Surface Standoff Missile (JASSM)
• Joint Standoff Weapon (JSOW B/C)
• AIM-9X Evolved Sidewinder
• AIM-120 Advanced Medium-Range Air-to-Air Missile (AMRAAM)
• Joint Direct Attack Munitions (JDAM)
• Standoff Land Attack Missile Expanded Response (SLAM-ER)
• Active Electronically Scanned Array (AESA)
• Advanced Tactical Airborne Reconnaissance System (ATARS)
• Traffic Alert and Collision Avoidance System (TCAS)
• Air Weapons Systems – This section is responsible for air-to-ground missile, air-to-air missiles, and mission planning programs, including:
• Avionics and Support Systems - This section is responsible for all aviation maintenance programs, including:
• CVN-21
• Joint Strike Fighter (JSF)
• Carrier and Amphibious Support - This section is responsible for all assault support helicopters, combat support helicopters, and fixed-wing and rotary-wing ASW aircraft, combat search and rescue (CSAR) aircraft, airborne mine warfare programs, and the V-22 Osprey.
• Carrier Strike - This section is responsible for all F/A-18 Hornet, F/A-18E/F Super Hornet, and related programs.
• Future Programs – This section works closely with requirements officers, program offices, and contractors on future projects and systems, including:
• Modeling, Simulation and Analysis - This section provides analytical support and technical advice on modeling and simulation issues for operational testing throughout the Aviation Warfare Division.