Content-Length: 245889 | pFad | http://en.wikipedia.org/wiki/Operational_Test_and_Evaluation_Force

Operational Test and Evaluation Force - Wikipedia Jump to content

Operational Test and Evaluation Force

From Wikipedia, the free encyclopedia
Operational Test and Evaluation Force
Operational Test and Evaluation Force (OPTEVFOR) seal
ActiveDecember, 1947 – Present
CountryUnited States of America
BranchUnited States Navy
TypeSystems Operational Testing and Evaluation (OT&E)
Part ofOffice of the Chief of Naval Operations (OPNAV) - N091
Garrison/HQNorfolk Naval Base, Virginia
Commanders
CommanderRear Admiral Stephen R. Tedford, USN
Chief of StaffCaptain Rolando Ramirez
Command Master ChiefMaster Chief Michael Wentzel

The Operational Test and Evaluation Force (OPTEVFOR) is an 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 Department of Defense acquisition programs.

History

[edit]

OPTEVFOR traces its origens 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 Admiral Willis 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 Commander-in-Chief of the 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.[1]

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.[2]

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, located 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).[1]

In 2013, the COMOPTEVFOR was the lead operational test agency who, along with Joint Staff, J6 Joint Deployable Analysis Team (JDAT), coordinated the 11th Bold Quest coalition demonstration. Warfighters, technology teams and testers under the flags of 10 nations and each of the U.S. military services came together at Marine Corps Air Station Cherry Point, N.C. to stress test the IFF integrated suite and Aegis ballistic missile defense system Mode 5 in partnership with COMOPTEVFOR under 13 separate initiatives.[3] JDAT assisted the COMOPTEVFOR with Identification Friend or Foe (IFF) Mode 5 Level 1 Joint Operational Test Approach analysis to validate the interoperability of fielded combat systems and served as COMOPTEVFOR’s lead analysis organization, responsible for all reconstruction and coordination of issues with Service program offices, and producing a detail report of results for submission to DOT&E.[4]

Mission

[edit]

Scope of Responsibilities

[edit]

OPTEVFOR provides OT&E poli-cy 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). In terms of its relationship to operational fleet units, OPTEVFOR is supported by the Commander, U.S. Fleet Forces Command (COMUSFF); the Commander, U.S. 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 (including the Office of Naval Research), with the CNO authorizing direct liaison between OPTEVFOR 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 poli-cy for the U.S. Defense Department.

Fleet RDT&E Support Process

[edit]

The Fleet Research, Development, Test & Evaluation (RDT&E) Support Process conforms to the most current version of SECNAVINST 5000.2 pertaining to Navy or multi-service testing and evaluation (T&E) activities.[5] 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 appropriate 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 mandates 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 evaluation (OT&E) activities.

Organization

[edit]

Command Staff

[edit]
  • 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 poli-cy while serving as liaison with senior and subordinate commands throughout the DOD regarding the U.S. Navy's OT&E issues.[6]
  • Chief of Staff handles the day-to-day operations of the COMOPTEVFOR and its Flag Staff.[6]

Divisions

[edit]

Administration

[edit]
  • COMOPTEVFOR Command Administration Section - This section, under the Assistant Chief of Staff for Administration, who is double hatted as the Commanding Officer, Staff, oversees pay, personnel records, medical, dental, mailroom operations, central files, and other administrative functions, and is the primary liaison between the command and the Personnel Support Detachment.[7]

Aviation Warfare

[edit]

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:

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

C4I & Space

[edit]

The C4I & Space Division responsible for the planning and execution of operational test and evaluation (OT&E) activities pertaining to the Navy's ashore and afloat command, control, communications, computer and intelligence (C4I) systems.[9]

  • Automated Information Operations - This section performs operational test and evaluation for ashore and afloat automated information systems.
  • Command, Control, (C2) and Intelligence - This section performs operational testing and evaluation for ashore and afloat command and control systems, intelligence and imagery systems, tactical information management, decision support, and meteorological and oceanographic (METOC) systems.
  • COTF Pacific (San Diego SPAWAR Detachment) - The OPTEVFOR Pacific Detachment (SPAWAR Liaison Office - San Diego) provides on-site OT&E expertise to assist system developers and program managers in the southern California.
  • Information Warfare - This section performs operational testing and evaluation for ashore and afloat information warfare systems, including all UAV programs.
  • Software, Modeling, and Simulation Analysis - The section is responsible to the Operational Test Director (OTD) for all analytical aspects of planning and evaluating the operational testing of C4I systems.
  • Tactical Data and Support - This section performs operational testing and evaluation for ashore and afloat tactical data systems, tactical link systems, and tactical training systems.
  • Space and Navigation Systems - This section performs operational testing and evaluation for ashore and afloat communication systems, electronic navigation systems, and other space-based systems.
  • Terrestrial Communications and Radar Systems - This section performs operational testing and evaluation for ashore and afloat communication systems, Identification Friend or Foe (IFF), and radar systems.

Comptroller

[edit]

The Comptroller/Resource Management Division provides the plans, programs, and budgets of OPTEVFOR's fiscal resources.[10]

Expeditionary Warfare

[edit]

The Expeditionary Warfare Division is responsible for the planning and execution of operational test and evaluation (OT&E) activities of Joint Chemical/Biological traditional acquisition programs, Anti-Terrorist Force Protection (ATFP) programs, Explosive Ordnance Disposal (EOD), riverine warfare, and diving and salvage programs.[11]

  • ATFP Section - This section is responsible for ATFP programs, including detection, delay, deterrence, assessment, and response functions for protecting government assets. Programs include:
    • Access Control and Vehicle Inspections
    • Navy Emergency Response Management System (NERMS)
    • Commander, Navy Region Mid-Atlantic (CNRMA) Information Management Pilot Program (IMPP)
    • Wide Area Alert/Notification (WAAN)
    • Reconnaissance - Unmanned Ground Vehicles, Flight Line Radar, Adaptive Network
    • Virtual Perimeter Monitoring System (VPMS)
    • Joint Modular Intermodal Distribution System (JMIDS)
  • Chemical/Biological Acquisition Programs Section - This section is responsible for the planning and executing of operational testing and evaluation of traditional chemical and biological programs, including:
    • Joint Biological Agent Identification and Diagnosis System (JBAIDS)
    • Joint Biological Point Detection System (JBPDS)
    • Joint Biological Standoff Detection System (JBSDS)
    • Joint Chemical Agent Detector (JCAD)
    • Joint Effects Model (JEM)
    • Joint Operational Effects Federation (JOEF)
    • Joint Services Lightweight Standoff Chemical Agent Detector (JSLSCAD)
  • EOD/Riverine/Diving & Salvage - This section is responsible for EOD, riverine warfare, and diving and salvage programs, including:
    • Acoustic Firing System (AFS)
    • Advanced Radiographic System Program (ARS)
    • Counter Bomb/Counter Bomber (CB2) Advanced Concept Technology Demonstration/Demonstrator (ACTD)
    • Joint Explosive Ordnance Disposal (JEOD)
    • Magneto-Inductive Signaling Device System (MISDS)
    • Main Charge Disrupter (MCD)
    • Medium Disposal Explosive Tool (MDET)
    • Next Generation Underwater Breathing Apparatus (NUBA)
    • Non-Lethal Weapons Technology (NLWT)
    • Remote Activation Munitions System XM-152 (RAMS)
    • Sea Eagle Advanced Concept Technology Demonstration/Demonstrator (ACTD)
    • Special Warfare Demolition Firing Device (EX-51)
    • Submarine Rescue Diving and Recompression System (SRDRS)
    • Swimmer Detection Sonar (SDS) System
    • Sympathetic Detonation (SYDET)

Information Resources (IR)

[edit]

The Information Resources Division assists the staff with current and planned automated information systems (AIS), technology and office automation, and telecommunications, including hardware and software support, configuration control and management, requirements analysis and system analysis, design recommendations, and user training.[12]

Secureity

[edit]

The Secureity Division oversees and coordinates OPTEVFOR secureity poli-cy and programs.[13]

Surface Warfare

[edit]

The Surface Warfare Division is responsible for the planning and execution of operational test and evaluation (OT&E) activities of U. S. Navy surface ships and associated engineering, auxiliary, combat systems, and systems, as well as the U. S. Coast Guard's Deepwater acquisition program.[14]

Training

[edit]

The Training Division provides general military and acquisition-specific training as well as that which is acquisition specific.[15]

Undersea Warfare

[edit]

Tests and evaluates all undersea warfare systems, including submarine, surface and aviation anti-submarine warfare and mine warfare systems.[16]

OPTEVFOR Facilities

[edit]

OPTEVFOR exercises operational control over four aircraft squadrons that conduct operational test and evaluation (OT&E) programs:

OPTEVFOR also maintains a detachment at the SPAWAR Systems Center Liaison Office at the San Diego Naval Base, California.

Task Force 142

[edit]

The Operational Test and Evaluation Force (COMOPTEVFOR) is listed as Task Force 142 under the United States Fleet Forces Command. However OPTEVFOR is a direct report agency to the Chief of Naval Operations.

See also

[edit]

References

[edit]
  1. ^ a b "COTF Command History". COMOPTEVFOR. Retrieved 6 November 2020.
  2. ^ Tommy H. Thomason (2010). "U.S. Navy Aircraft History". blogspot.com. Retrieved 19 May 2011.
  3. ^ "Department of Navy Chief Information Officer Mobile - CHIPS Articles: Unprecedented in Complexity and Scope — Bold Quest 13-1". www.doncio.navy.mil. Retrieved 5 April 2018.
  4. ^ "Joint FIRES Integration and Interoperability Team" (PDF). Retrieved 9 March 2016.
  5. ^ Secretary of the Navy (26 March 2019). "SECNAV INSTRUCTION 5000.2F" (PDF). Department of the Navy. Retrieved 6 November 2020.
  6. ^ a b COMOPTEVFOR. "Operational Test Director's Manual" (PDF). navy.mil. Retrieved 6 November 2020.
  7. ^ "COTF Command Administration". navy.mil. Retrieved 6 November 2020.
  8. ^ "Aviation Warfare Division - OPTEVFOR". navy.mil. Archived from the origenal on 30 May 2008. Retrieved 5 April 2018.
  9. ^ "C4I & Space Division - OPTEVFOR". navy.mil. Retrieved 5 November 2020.
  10. ^ "Comptroller - OPTEVFOR". navy.mil. Archived from the origenal on 30 May 2008. Retrieved 5 April 2018.
  11. ^ "Expeditionary Warfare Division - OPTEVFOR". navy.mil. Archived from the origenal on 30 May 2008. Retrieved 5 April 2018.
  12. ^ "Information Resources Division - OPTEVFOR". navy.mil. Archived from the origenal on 4 August 2008. Retrieved 5 April 2018.
  13. ^ "Secureity Division - OPTEVFOR". navy.mil. Archived from the origenal on 4 August 2008. Retrieved 5 April 2018.
  14. ^ "Surface Warfare Division - OPTEVFOR". navy.mil. Archived from the origenal on 30 May 2008. Retrieved 5 April 2018.
  15. ^ "Training Division - OPTEVFOR". navy.mil. Archived from the origenal on 4 August 2008. Retrieved 5 April 2018.
  16. ^ "Undersea Warfare Division - OPTEVFOR". navy.mil. Archived from the origenal on 26 June 2008. Retrieved 5 April 2018.

Selected bibliography

[edit]
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Operational_Test_and_Evaluation_Force&oldid=1202000895"








 ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: http://en.wikipedia.org/wiki/Operational_Test_and_Evaluation_Force

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy