1.02 Draft Performance Work Statement VX-9.pdf

AIR TEST AND EVALUATION SQUADRON (AIRTEVRON) NINE (VX-9)

Performance Work Statement

EA-18G (TEIN 1787)

1.0 Introduction. This contract will provide for engineering, analytical, and technical support for air warfare system operational test and evaluation (OT&E) specifically, the EA-18G (TEIN 1787).

Services are to be conducted at Air Test and Evaluation Squadron (AIRTEVRON) NINE (VX-9), China Lake, CA.

2.0 Background.

2.1 Title 10 United States Code (U.S.C.) §2399 mandates OT&E of Acquisition Category (ACAT) I and II programs before they proceed beyond low rate initial production (LRIP). OT&E is defined as the field test, under realistic combat conditions, of any item of (or key component of) weapons, equipment, or munitions for the purpose of determining the effectiveness and suitability of the weapons, equipment, or munitions for use in combat by typical military users; and the evaluation of the results of such test. DOD Instruction 5000.2 additionally mandates operational test of acquisition programs on the Director of Operational Test and Evaluation (DOT&E) Oversight list prior to proceeding beyond LRIP, and all acquisition programs prior to Milestone C. SECNAVINST 5000.2 series mandates additional OT&E for lower ACAT-level acquisition programs, post-LRIP acquisition programs, and software changes, if appropriate.

2.2 DOD Directive 5000.1 requires each military department to establish an independent operational test agency, reporting directly to the service chief, to plan and conduct operational tests, report results, and provide evaluations of effectiveness and suitability. SECNAVINST 5000.2 series designates Operation, Test and Evaluations Forces (OPTEVFOR) as the Navy’s independent operational test agency, and assigns OPTEVFOR responsibility for planning and conducting OT&E, reporting results, providing evaluations of each tested system’s operational effectiveness and suitability, identifying system deficiencies, developing tactics, and making recommendations regarding fleet introduction.

OPNAVINST 5450.332 assigns the OPTEVFOR operational control of VX-9. VX-9 is tasked with the OT&E of all USN/USMC tactical aircraft and associated weapons and avionics acquisition programs.

(See Appendix A).

3. Scope. The scope of this acquisition includes analytical, engineering and technical support for OT&E planning, OT&E execution, OT&E reporting, and in-service monitoring of OT&E for EA-18G. This effort requires support services to include: Senior Flight Test Engineer (SFTE), Intermediate FTE (IFTE), Data Management (DM), Data Base Administration (DBA), System Administrator (SA), and Reliability, Maintainability and Availability (RM&A).

SFTE Six or more years of specialized professional experience in developmental or operational test and evaluation of aircraft, weapons, software, or systems.

IFTE Four or more years of specialized professional experience in developmental or operational test and evaluation of aircraft, weapons, software, or systems.

DBA Four or more years of specialized professional experience in the Information Technology field. A minimum experience of three years in database management, computer programming, or design.

SA Support, troubleshoot, and maintain computer servers and networks.

RM&A Work with the software, performance, hardware, maintenance department and aircrew to collect data and system performance metrics in performing systems RMA analyses

3.1

a. Place of performance: VX-9, China Lake, CA

b. Period of Performance: 30 September 2022 – 29 September 2023)

c. Travel Requirements: Contractor may be required to perform travel. All travel must be approved in advance by the PAO and COR. Travel will be reimbursed in accordance with the Joint Travel Regulations (JTR). The following travel may be required during the execution of this delivery order in order to conduct Test flight events, Test Plan Working Group meetings, Test & Evaluation coordination and training.

Destination # of

Trips # of

Travelers # of

Days per Trip Nellis AFB, NV 3 2 7

JPARC, AK 1 3 21

St Louis, MO 3 2 7 Norfolk, VA 1 2 7 Pt. Mugu, CA 4 2 7 Pax River, MD 4 2 7

4.0 Milestones. Planned milestone events during the period of performance are as follows:

a. IT&E Integration (H16) – 30 September 2022 – 29 September 2023

b. OT&E Planning (H16) – 30 September 2022 – 29 September 2023

c. OT&E Execution (H16) – 30 September 2022 – 29 September 2023

d. OT&E Reporting/AWG/SERB (H16) 30 September 2022 – 29 September 2023

e. OT&E Planning (H18) – 30 September 2022 – 29 September 2023

f. IT&E Integration (H18) – 30 September 2022 – 29 September 2023

g. OT&E Planning (TTNT) – 30 September 2022 – 29 September 2023

h. IT&E Integration (TTNT) – 30 September 2022 – 29 September 2023

i. WIPTs - Quarterly

5.0. Specific Tasking/Deliverables. The contractor shall provide support for the early involvement planning and Framework preparation for the H16 and H18 system update to include TTNT and early involvement meeting attendance supporting the H16 and H18 system update to include TTNT. The contractor shall also complete OT&E execution and reporting of the operational effectiveness and suitability of H16 system updates for integration on to the EA-18G platform.

a. IT&E Integration. The contractor shall:

Participate in the IT&E planning to gain familiarity with the DT&E effort, identify events which are duplicative of planned OT&E events, recommend alterations to DT&E events to include OT&E objectives and vice versa, and assist the OTD in the integration of OT&E and

DT&E.

Participate in IT&E events and collect and analyze data, as appropriate for use in the OT report.

Associated deliverables: A001,A002, A009, A011, A012,& A014.

A001 - Trip Report. The contractor shall prepare a trip report detailing key information issued at the program meeting attended within two working days after returning from the meeting, and deliver the trip report to the OTD, or as prescribed by the delivery order.

A002 - Draft OT&E inputs to the integrated test and evaluation plan. The contractor shall prepare the OT&E inputs as directed in the task order. The format and delivery schedule will be determined by mutual agreement between the DT&E authority and OPTEVFOR, and may be recorded in the delivery order or delivery order modification. The deliverable will include detailed test objectives, and may also include the detailed event.

A009 – Kneeboard cards and surveys. Kneeboard cards and survey sheets for OT&E data collection must appear in the OT&E test plan. However, unanticipated test conditions may necessitate the contractor produce additional kneeboard cards for survey sheets prior to each test event.

A011 – Draft miscellaneous reports. The contractor shall issue draft HMRs (Hazardous material report), TPDRs (technical publications deficiency report), QDR (quality deficiency report), and EIs (Engineering Investigation), and draft HAZREPs on the recently fielded system of interest when warranted by performance discrepancies observed during in-service monitoring. These reports are due within two working days of tasking.

A012 – Daily operations schedule. The contractor shall prepare in accordance to VX-9 Operations Department, a daily operations schedule outlining all squadron flight operations and meeting.

A014 – Preliminary test information database. Provide database setup and/or manipulation to support the data collection and analysis as provided by the OTD and/or test/tactics analyst.

Due no later than 30 days prior to start of test.

b. Program Document Review. The contractor shall review program documents as required in the task order, provide comments on the issues relevant to operational test, and comment on compliance.

c. OT&E Planning. The contractor shall:

Provide draft TEMP inputs and a comment matrix on the remaining parts of the TEMP, derived from Scenarios, COIs and Detailed Test Objectives, and Resource Summary.

Become familiar in detail with the operational and technical characteristics of the system to be tested and program documentation. Conduct test planning, including test logistics and resource management planning. Assist OTD in formulating integrated and operational test plans, as applicable.

Ensure that planning is thorough and complete, and Critical Operational Issues (COI), test scenarios, measures of effectiveness, and measures of suitability are developed in accordance with OPTEVFOR guidance and policy. Ensure that data collection and analysis plans, including instrumentation requirements, can be fulfilled.

Draft concept of operations test briefs in cooperation with the OTD and OTC for presentation to OPTEVFOR, DOT&E, and the program manager.

Ensure that the scheduled OT&E phase is coordinated with other IT&E/OT&E scheduled to occur simultaneously, and that maximum efficiencies in resource usage are achieved.

Conduct preliminary data rehearsals to ensure data collection can be performed as planned.

Associated deliverables: A002, A003, A004, A005, A006, A008,A009, A010, A011 A002- Draft OT&E inputs to the integrated test and evaluation plan. The contractor shall prepare the OT&E inputs as directed in the task order. The format and delivery schedule will be determined by mutual agreement between the DT&E authority and OPTEVFOR, and may be recorded in the delivery order or delivery order modification. The deliverable will include detailed test objectives, and may also include the detailed event.

A003 – OT&E scenarios, COIs (critical operational issues) and detailed objectives, and resource summary. Draft OT&E scenarios shall be developed from the missions and tactics designated for the host aircraft and threat simulators with support assets. COIs shall be dendritically expanded into detailed test objectives traceable to the governing requirements documents, and mission essential task lists. These elements are further described in the OPTEVFOR Air Warfare Test Planning Checklist. Deliverable is due as specified in the task order; but the typical timeline may be more than one and a half calendar years prior to the scheduled test.

A004 – TEMP part IV/V and comment matrix. The contractor shall provide draft TEMP Part IV/V inputs and a comment matrix on the remaining parts of the TEMP in accordance with SECNAVINST 5000.2 and OPTEVFOR OTD Manual within 10 working days of receiving tasking.

A005– Draft OT&E Framework. The contractor shall prepare a draft OT&E Framework detailing OPTEVFOR test requirements and objectives in accordance with OPTEVFOR directives within 60 days after receiving tasking.

A006– Draft Test Plan. This deliverable shall be produced 60 calendar days after specific task order has been enacted or 180 calendar days prior to the scheduled test, whichever occurs later. Unless otherwise directed in writing, the draft test plan shall follow the format prescribed by the OPTEVFOR OTE manual. Unless otherwise stated by the task order, this deliverable is the highest priority of all defined in the PWS. The accepting authority is deliverable is the DCOTD.

A009– Kneeboard cards and surveys. Kneeboard cards and survey sheets for OT&E data collection must appear in the OT&E test plan. However, unanticipated test conditions may necessitate the contractor produce additional kneeboard cards for survey sheets prior to each test event.

A010– Draft flight clearance request. Flight clearance requests shall be drafted as soon as a need is identified by the program OTD or analyst, in accordance with appropriate NAVAIR Airworthiness instructions, and delivery within two working days to the OTD or as the delivery order requires.

A011– Draft miscellaneous reports. The contractor shall issue draft HMRs (Hazardous material report), TPDRs (technical publications deficiency report), QDR (quality deficiency report), and EIs (Engineering Investigation), and draft HAZREPs on the recently fielded system of interest when warranted by performance discrepancies observed during in-service monitoring. These reports are due within two working days of tasking.

d. OT&E Configuration Management. The contractor shall:

Maintain a record of all aircraft hardware, software and flight clearances used during OT&E that will permit both immediate and historical identification of comprehensive aircraft configuration.

Ensure flight clearance requests are drafted as soon as a new configuration requiring a flight clearance is identified. Liaison with VX-9 maintenance to ensure that each aircraft is properly configured for daily test events.

Associated deliverables: A010, A011 A010– Draft flight clearance request. Flight clearance requests shall be drafted as soon as a need is identified by the program OTD or analyst, in accordance with appropriate NAVAIR Airworthiness instructions, and delivery within two working days to the OTD or as the delivery order requires.

A011– Draft miscellaneous reports. The contractor shall issue draft HMRs (Hazardous material report), TPDRs (technical publications deficiency report), QDR (quality deficiency report), and EIs (Engineering Investigation), and draft HAZREPs on the recently fielded system of interest when warranted by performance discrepancies observed during in-service monitoring. These reports are due within two working days of tasking.

e. OT&E Execution. The contractor shall:

Schedule OT&E events and coordinate OT&E resources. The contractor, in consultation with the OTD, schedules ranges, targets, range resources, aircraft, test personnel, instrumentation, and any other elements required for the successful execution of test events.

Arrange for collection of all required data from each scheduled test event, to include the distribution of all data collection materials, configuration of all instrumentation prior to OT&E events, and recovery of all data during and after the scheduled test events. Oversee the actual collection of data, review the data to ensure it is complete and free of corruption, and perform analysis on the data. Adapt to changing test conditions that mandate the contractor produce kneeboard cards and data collection sheets to ensure required data is captured. Throughout the test, track and monitor the amount of data captured and compare with the data required in the test plan to address test objectives, measure actual test progress versus planned test progress, and monitor actual resources expended versus planned resources expended. Immediately advise the OTD of any gaps or data collection problems that could prevent achievement of OT&E objectives.

Alert the OTD to potential anomalies and deficiencies and draft anomaly messages.

Brief test personnel prior to OT&E events as directed by the OTD. Act as test conductor during test events, monitor test flights at range control or at other suitable test locations to enable on-the-spot flexing to alternate missions, or to make go/no-go decisions. Ensure range assets follow prescribed event sequence, coordinate changes on a real-time basis as needed to the event sequence, and record pertinent observations. Debrief test personnel after each test event as arranged with the OTD.

Associated deliverables: A001, A009, A012, A013, A014, A016 A001 - Trip Report. The contractor shall prepare a trip report detailing key information issued at the program meeting attended within two working days after returning from the meeting, and deliver the trip report to the OTD, or as prescribed by the delivery order.

A009 - Kneeboard cards and surveys. Kneeboard cards and survey sheets for OT&E data collection must appear in the OT&E test plan. However, unanticipated test conditions may necessitate the contractor produce additional kneeboard cards for survey sheets prior to each test event.

A013 – Draft OT&E finial report. The contractor shall produce no later tha 15 calendar days after the official end of test a draft OT&E final report, with content, paragraph structure, and formatting accordance with the OPTEVFOR OTD manual.

A014– Preliminary test information database. Provide database setup and/or manipulation to support the data collection and analysis as provided by the OTD and/or test/tactics analyst.

Due no later than 30 days prior to start of test.

A016– Draft OT&E final report brief. The contractor shall produce no later than two working days after receiving tasking a final report brief, with content, paragraph structure, and formatting in accordance with the OPTEVFOR OTD manual.

f. Database Administration

The contractor shall develop modifications/updates to government-furnished database(s) using MS Access or other government defined database program. The database(s) shall provide interfaces for both: User-customizable forms for data entry; database queries and data mining;

and reports; and interfaces which allow data pull from external data sources used in reliability, maintainability, and availability evaluation of systems under test.

The contractor shall assist with entering data into the database(s) from (but not limited to) questionnaires and survey sheets. The contractor shall assist in the development of questionnaires and survey sheets. User-customizable forms shall support,:

Qualitative and Quantitative aircrew and analyst questionnaires.

Qualitative and Quantitative Training Surveys Qualitative and Quantitative Maintenance Surveys Aircrew and analyst notes

Data which may be pulled from external sources shall include, Video snippets Images External documents such as Microsoft Word, Excel, and Adobe PDF Aircraft and Range Telemetry and TSPI data Air and surface threats lists Parsed ASCII and binary files Aircraft maintenance and flight data

Associated deliverables: A009, A011, A013, A014 A009– Kneeboard cards and surveys. Kneeboard cards and survey sheets for OT&E data collection must appear in the OT&E test plan. However, unanticipated test conditions may necessitate the contractor produce additional kneeboard cards for survey sheets prior to each test event.

A011– Draft miscellaneous reports. The contractor shall issue draft HMRs (Hazardous material report), TPDRs (technical publications deficiency report), QDR (quality deficiency report), and EIs (Engineering Investigation), and draft HAZREPs on the recently fielded system of interest when warranted by performance discrepancies observed during in-service monitoring. These reports are due within two working days of tasking.

A013– Draft OT&E finial report. The contractor shall produce no later tha 15 calendar days after the official end of test a draft OT&E final report, with content, paragraph structure, and formatting accordance with the OPTEVFOR OTD manual.

A014– Preliminary test information database. Provide database setup and/or manipulation to support the data collection and analysis as provided by the OTD and/or test/tactics analyst. Due no later than 30 days prior to start of test

Contractor support shall include the following tasks which are further defined in subparagraphs

(1) through (4) below:

Initial Modification Scoring Boards Test Report Writing Database Administration.

(1) Design and Modification.

Setup Optimized Organizational Maintenance Activity (OOMA) account.

Install OOMA program on NMCI computers.

Import queries and make sure they are working to give correct data.

Determine method for scoring BIT in accordance with the Test and Evaluation Master

Plan (TEMP).

Import some initial Maintenance Action Form (MAF) data to ensure that the expected

RMA metrics are being calculated correctly.

Work with OTD/Analyst to produce RMA/BIT ground rules document.

Obtain Mission Essential Subsystems Matrices (MESM) and populate with proper

Equipment Operational Capability (EOC) codes.

Populate with proper Fault Isolation Detection (FID) codes.

(2) Scoring Boards.

(a) Prior to Scoring Board (can be weekly, bi-weekly, monthly).

Familiarize OTD/Analyst or test team RMA Analyst with database RMA functionality.

Download MAF's from OOMA.

Import MAFs and BIT data.

Pre-score scheduled MAF data with RMA analyst.

Assist with BIT Scoring and provide queries and reports as necessary Pre-score unscheduled MAF data with RMA analyst and add comments, questions, or concerns for scoring board.

Separate pre-scored data from un-scored data to be viewed by test team.

Review pre-scored data with RMA analyst as a check and balance.

Run pre-scoring board MAF report to be distributed to the scoring board team members.

(b) MAF Scoring Board.

Participate in MAF Scoring Board.

Produce RMA statistics for the RMA analyst.

(c) BIT Scoring Board.

Participate in BIT Scoring Board.

Produce BIT statistics for the RMA analyst.

(3) Test Report Writing.

Provide RMA scoring results and reports to the RMA Analyst in order to adjust any MAF data that is determined to be non-relevant.

Contribute RMA calculations and necessary data and reports to the RMA analyst in order to complete the Final Report.

(4) Database Configuration Control and Training. The contractor shall ensure any new data which affects the configuration of the existing test database remains compatible with existing systems at VX-9 by:

Configuration control of various database product lines Verification of integrity of data imported from external sources Databases archival ion a regular periodic schedule; restoration as needed for recovery of corrupt or lost data

Administration of access control lists and user privileges Database upgrades provided as needed.

Provide (as needed) training to all database users.

Provide support for the daily operation and maintenance of the database both on-site and during detached operations at field locations.

4. OT&E Reporting. The contractor shall analyze and summarize all test data, capture results and deficiencies, and assist the OTD in preparing the draft final report. The OTD will determine deficiency levels, establish COI (critical operational issues) resolution, make conclusions on operational effectiveness and suitability, and make all recommendations.

Associated deliverable: A001, A011, A013, A014, A016 A001 - Trip Report. The contractor shall prepare a trip report detailing key information issued at the program meeting attended within two working days after returning from the meeting, and deliver the trip report to the OTD, or as prescribed by the delivery order.

A011 – Draft miscellaneous reports. The contractor shall issue draft HMRs (Hazardous material report), TPDRs (technical publications deficiency report), QDR (quality deficiency report), and EIs (Engineering Investigation), and draft HAZREPs on the recently fielded system of interest when warranted by performance discrepancies observed during in-service monitoring. These reports are due within two working days of tasking.

A013– Draft OT&E finial report. The contractor shall produce no later than 15 calendar days after the official end of test a draft OT&E final report, with content, paragraph structure, and formatting accordance with the OPTEVFOR OTD manual.

A014 – Preliminary test information database. Provide database setup and/or manipulation to support the data collection and analysis as provided by the OTD and/or test/tactics analyst. Due no later than 30 days prior to start of test.

A016– Draft OT&E final report brief. The contractor shall produce no later than two working days after receiving tasking a final report brief, with content, paragraph structure, and formatting in accordance with the OPTEVFOR OTD manual.

5. In-Service Monitoring. The contractor shall conduct on-site monitoring of the effectiveness and suitability of newly fielded systems, reporting regularly to the OTD. Provide advice for the efficient and/or effective operation of newly fielded systems, equipment, or components, at the direction of the OTD. Identify any anomalous behavior, and either submit a draft OPTEVFOR anomaly report, and/or issue a draft QDR, TPDR, or HAZREP as warranted.

Associated deliverables: A001, A011, A015 A001 - Trip Report. The contractor shall prepare a trip report detailing key information issued at the program meeting attended within two working days after returning from the meeting, and deliver the trip report to the OTD, or as prescribed by the delivery order.

A011 – Draft miscellaneous reports. The contractor shall issue draft HMRs (Hazardous material report), TPDRs (technical publications deficiency report), QDR (quality deficiency report), and EIs (Engineering Investigation), and draft HAZREPs on the recently fielded system of interest when warranted by performance discrepancies observed during in-service monitoring. These reports are due within two working days of tasking.

A015 – Draft OT&E anomaly report. Anomaly reports as warranted and directed by the task order shall be drafted in accordance with the OPTEVFOR OTD manual within two working days of receiving tasking.

6. Deliverables. All deliverables shall be delivered in electronic MS Office format unless otherwise indicated. Deliverables shall be delivered to the designated government technical staff member, the VX-9 COR, or VX-9 DCOTD, as indicated in the individual task order. Unless the delivery order indicates otherwise, the Government has two calendar weeks to accept the deliverable, or return it with comments for modification, after which the contractor has two more calendar weeks to incorporate government comments and resubmit for acceptance.

7. Personnel Qualifications Performance on this task order requires skills sets comprising of EA18G system operations, integration, weapons compatibility, mission planning, test flight planning/execution, program management, and technical writing.

8. Security.

All personnel under this contract must hold a SECRET security clearance and be eligible for a TOP SECRET/ Sensitive Compartmented Information (SCI) security clearance meeting Director Central Intelligence Directive (DCID) 6/4 eligibility standards. Performance under this contract shall entail access to classified material and laboratory facilities up to the TOP SECRET Special Access Required (SAR)/SCI level for all contractor personnel. The contractor may be required to handle communications security (COMSEC) material. Additionally, the contractor may be required to handle and generate documents, manuals, presentations, specifications, drawings, magnetic tapes/disk, sketches or schematics that are classified up to and including TOP SECRET SAR/SCI. The contractor shall ensure compliance with security guidance specified in the associated Department of Defense Contract Security Classification Specification (DD-254).

b. During the performance of this contract, access to classified information and documentation will be required. In an effort to preclude the possible compromise of classified data, the contractor shall employ Operations Security (OPSEC) measures to control unclassified information that could be considered mission/program sensitive. The contractor shall comply with OPSEC requirements in accordance with the DD Form 254.

9. Data Rights Agreement. See DFARS 252.227-7013 for proper marking of data deliverables. See Section I of the RFP for a complete list of all data rights clauses that will be incorporated herein by reference to include, but not limited to, 252.227-7017; 252.227-7025; 252.227-7028; 252.227-7037 252.227-7030; see also 252.227-7014. The Government asserts ownership on all deliverables; however, DFARS 252.227-7026 and 252.227-7027 will also be incorporated herein to preserve the Government’s rights for deferred delivery or deferred ordering of technical data or computer software.

10. Services Contract Reporting:

Services Contract Reporting (SCR) requirements apply to this contract. The contractor shall report required SCR data fields using the SCR section of the System for Award Management (SAM) at following web address: https://sam.gov/SAM/.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://sam.gov/SAM/.