DOCUMENT

1.02 PWS Legacy Follow On.docx

OVERVIEW

Original Source
Contract Opportunity
Date Originally Posted
Nov. 3, 2022, 3:56 p.m.
Type
.docx
Size
0.04MB
Profiled People
None

DOCUMENT PREVIEW

EXTRACTED TEXT

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

Statement of Work (SOW)

F/A-18 LEGACY SOFTWARE CONFIGURATION SETS (SCS) (TEIN S1699)

1.0 Scope. The scope of this acquisition includes analytical, engineering and technical support for IT&E associated with production and post-production acceptancy test planning, execution, reporting, and in-service monitoring of IT&E of the Legacy Software Configuration Set (SCS) 29C* updates for the F/A-18A-D, APG-79(v)4 Radar, and future Follow-On SCS updates. SCS modifications to the baseline SCS Operational Flight Program (OFP) software and associated subsystem modifications require Fleet evaluation/certification prior to Fleet release. The contractor work activities and deliverables are very similar regarding execution of IT&E, and the ITT construct, which this SOW delineates in the paragraphs that follow:

1.0.1 Place of performance: VX-9, China Lake, CA

1.0.2 Period of Performance: 30 September 2022 – 29 September 2023

1.0.3 Travel Requirements: The following travel may be required during the execution of this delivery order:

CLIN 0001: 29C* and the APG-79(V)4

Destination

# ofTrips

# ofTravelers

# ofDays per Trip

Miramar, CA

Beaufort, NC

2.0 Milestones. F/A-18 Legacy Software Configuration Set (SCS) and future Follow-on SCS Updates. Planned milestone events during the period of performance are as follows:

2.0.1 CLIN 0001: 29C*and the APG-79(V)4. Planned milestone events (in support of Government/Military led efforts) during the period of performance are as follows:

(1) 29C* IT&E Test Execution – September 2022 – June 2023

(2) 29C* IT&E Report – June – August 2023

(3) 29C* Fleet briefs – August 2023

2.0.2 CLIN 0002: 31C. Follow-on SCS. Planned milestone events (in support of Government/Military led efforts) during the period of performance.

31C IT&E Planning – April – July 2023

31C IT&E Execution –Beginning August 2023

31C Meetings Quarterly

3.0 Specific Tasking/Deliverables. The contractor shall provide support in preparation for and attendance at periodic technical interchange meetings throughout the performance period. The contractor shall provide systems subject matter expertise to ensure test concepts are adequate to measure system performance and collect data, which can be used throughout the program lifecycle. Tasking on this effort includes complete IT&E execution and reporting of the operational effectiveness and suitability of 29C* system modifications. The contractor shall also provide support for the early involvement OT planning and, Test Evaluation Master Plan and Integrated Evaluation Framework preparation for the 31C system modifications and updates.

3.1 IT&E Integration The contractor shall:

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

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

3.2 Program Document Review. The contractor shall:

3.2.1 Review program documents as required in the task order, provide comments on the issues relevant to IT&E certification for Fleet release, and comment on compliance.

3.3 IT&E Planning. The contractor shall:

3.3.1 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.

3.3.1.1 Collaborate in development/update of OT Master Framework and associated Framework Annex.

3.3.1.2 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.

3.3.1.3 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.

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

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

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

3.3.2 IT&E Execution. The contractor shall:

3.3.2.1 Schedule IT&E events and coordinate IT&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.

3.3.2.2 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 IT&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 IT&E objectives.

3.3.2.3 Alert the OTD to potential anomalies and deficiencies and draft Blue or Gold Sheet by utilizing the OPTEVFOR format.

3.3.2.4 Brief test personnel prior to IT&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.

3.4 Database Design.

3.4.1 The contractor shall provide updates to the government-furnished Test Information Management System (TIMS) using MS Access or other government defined data collection program. The system shall provide interfaces for both: User-customizable forms for test event information entry, queries, and reports; and will allow test information to be pulled from various external sources used in reliability, maintainability, logistics supportability, and availability for the evaluation of the System Under Test (SUT).

3.4.2 The contractor shall assist with entering data into the database(s) from questionnaires and survey sheets. The contractor shall assist in the development and maintenance of questionnaires and survey sheets. User-customizable forms shall support the following:

- Qualitative and Quantitative aircrew and analyst questionnaires.

- Qualitative and Quantitative Training Surveys

- Qualitative and Quantitative Maintenance Surveys

- Aircrew and analyst notes

3.4.3 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 Time in Space Position Information (TSPI) data

- Air and surface threats lists

- Parsed ASCII and binary files

- Aircraft maintenance and flight data

3.4.4 Contractor support shall include the following tasks, which are further defined in subparagraphs below.

- Initial Design and Modification

- Scoring Boards

- Test Report Writing

3.4.4.1 Scoring Boards.

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

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

Import MAFs and BIT data.

Pre-score scheduled MAF data with RMLA analyst.

Assist with BIT Scoring and provide queries and reports as necessary

Pre-score unscheduled MAF data with RMLA 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 RMLA analyst as a check and balance.

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

MAF Scoring Board.

Participate in MAF Scoring Board.

Produce RMLA statistics for the RMLA analyst.

BIT Scoring Board.

Participate in BIT Scoring Board.

Produce BIT statistics for the RMLA analyst.

3.4.4.2 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.

3.4.4.3 Preliminary Test Informatio… Show All