DRAFT VX-1 PWS.pdf

PERFORMANCE WORK STATEMENT FOR ANALYTICAL OPERATIONAL TEST AND

EVALUATION SUPPORT SERVICES FOR VX-1

1. Scope. Contractor will provide technical and analytical support to Operational Test and Evaluation Force

(OPTEVFOR)/Air Test and Evaluation Squadron ONE (VX-1) in the definition, conduct and analysis of structured Operational Test and Evaluation (OT&E) of U.S. Naval systems. This support will be required in one or more of the following forms: Documentation Review, Operational Test Design, Test Planning Support, Test Execution, Data Management, Test Operations Support, Test Analysis and Reporting, Test Operations Support, Modeling and Simulation (M&S) Support, Aircraft Coordination, and Program Management Support.

OPTEVFOR/VX-1 is charged with leading the Operational Test (OT) community with highly skilled testers and staff that adapt to change, and provide credible, prompt, warfighting-focused test results to Navy, Marine Corps and Coast Guard forces and acquisition leadership.

1.1. Background. VX-1, based at Naval Air Station (NAS) Patuxent River, MD, is a Major Shore Command charged with OT execution and tactical development and analysis under OPTEVFOR direction. VX-1 is comprised of approximately 50 officers and 250 enlisted personnel executing work on 10 different type/series/models of Naval and Marine Corps aircraft.

1.2. For scoping purposes, a current list of VX-1 evaluation programs being performed are listed below. These programs are current as of time of solicitation and additional programs may be assigned to VX-1 for contractor support under this contract.

1.2.1. MQ-25

1.2.2. E-2D

1.2.3. P-8A

1.2.4. Triton

1.2.5. E130J

1.2.6. SVSI

1.2.7. MH-60R/MH-60S

1.3. Period of Performance. 30 October 2026 through 29 October 2027 (Base Year), 30 October 2027 through 29 October 2028 (Option Year 1), 30 October 2028 through 29 October 2029 (Option Year 2), 30 October 2029 through 29 October 2030 (Option Year 3), 30 October 2030 through 29 October 2031 (Option Year 4), and 30 October 2031 through 29 April 2032 (Dash-8).

1.4. Place of Performance. Unless required to support mission accomplishment, work shall primarily be performed at the customer’s site. If the number of personnel exceeds onsite capabilities, unclassified work will be expected to be performed offsite. The customer location is:

Air Test and Evaluation Squadron ONE 47298 Tate Road, Hangar 305 NAS Patuxent River, MD 20670

While onsite at VX-1, the contractor shall comply with Office of the Chief of Naval Operations (OPNAV) Instruction (INST) 5239 (series), with specific regard to non-government hardware and software.

1.4.1. Travel. Travel can be expected to occur Continental United States (CONUS) and Outside the Continental United States (OCONUS), and will be required throughout the course of this contract.

All travel costs shall be per the Federal Travel Regulations. Invoices shall include actual costs experienced. Airfare shall be based on the lowest available cost for coach or economy in writing, in advance. Travel dates and locations are to be confirmed through the Technical Point of Contact and approved by the Contracting Officer’s Representative (COR) in writing, prior to commencement of any travel.

1.4.1.1. Travel Instructions

1.4.1.1.1. Ensure all Contractors supporting this requirement meet the minimum requirements of the Commander, U.S. Fleet Forces Command/Commander, U.S. Pacific Fleet INST 6320.3B, dated 04 Apr 2014, Medical Screening for U.S. Government Civilian Employees, Contractor Employee’s, and Guests and Visitors Prior to Embarking Fleet Units.

1.4.1.1.2. Any travel OCONUS by the Contractor will need to review the Foreign Clearance Guide at http://www.fcg.pentagon.mil and select the country of intended travel. During OCONUS travel, the contractor shall operate in accordance with International Traffic in Arms Regulation (ITAR) Part 124, approved by US Department of State, Office of Defense Trade Controls. Specific guidance can be found at:

https://www.pmddtc.state.gov/regulations_laws/itar.html.

1.4.1.1.3. The Contractor is not authorized to perform any travel that is not in conjunction with this contract. It is the Department of the Navy policy not to allow a charge of profit or fee on reimbursable items.

1.4.1.1.3.1. The Government will make no reimbursements for a contractor’s local travel (defined as less than 50 miles from the place of performance).

1.4.1.1.3.2. In no instance shall the contractor exceed the amount specified in the contract for travel CLIN expenses.

1.4.1.1.3.3. Locations include CONUS, OCONUS, at-sea locations and any other location, which may be added on a Task Order (TO) basis based on future test requirements.

1.4.1.1.3.4. For planning purposes, any travel location OCONUS must be considered as a possible travel location unless travel restrictions at time of test do not permit entry. Possible OCONUS locations include, but are not limited to the following:

Andros Island, Bahamas, Darwin, Brisbane, Melbourne, Newcastle, Perth, and Sydney, Australia, London, England, Honduras, Singapore, La Spezia, Italy, Guam, Hawaii, Halifax, Nova Scotia, Nanoose, British Colombia, Columbia, Belize, Guatemala, Souda Bay Crete, Mexico and any other location, which may be added on a TO basis, based on future test requirements.

1.5. Personal Services. This is not a personal services TO. The contractors/sub-contractors should be well-educated in respect to “personal services.” No one (Government employee or military) may task the contractor to perform work not listed in the delivery order, nor do the contractors take direction in the performance of their task from anyone other than their corporate manager and/or prime contractor, as appropriate.

1.6. Privity Defined. The legal term that defines the relationship between two parties of a contract, does not exist between the Government and the subcontractor. Therefore, the Prime contractor is responsible for ensuring through its own internal processes, quality work is performed and delivered on time by any subcontractors to meet the objectives of the prime contract. Formal direction to subcontractors flows only through the prime contractor. There can be simultaneous communication between the prime contractor and the subcontractor, but the Government and the subcontractor cannot bypass the prime contractor to communicate directly with each other.

1.7. Automated Data Processing (ADP) Requirements. The Government will provide, if required, the necessary computer, workstation/system access for on-site work.

1.7.1. Those offerors assigned as off-site will not be assigned government furnished ADP assets.

1.7.2. Additionally, the offerors assigned ADP Government Furnished Property (GFP) will be held accountable to respond to the governments ADP inventory requirements conducted semi-annually re-occurring every Mar and Sep to ensure 100% accountability of all ADP assets.

1.7.3. Any offeror not adhering to this call for ADP asset inventory may be directed to forfeit their ADP GFP at no additional cost to the government per FAR 52.245-1.

http://www.fcg.pentagon.mil/fcg.cfm https://www.pmddtc.state.gov/regulations_laws/itar.html

1.8. Common Access Card (CAC)/Public Key Infrastructure, System Authorization Access Request (SAAR-N). All contractor personnel requiring access to Government Information Technology (IT) systems shall have an approved System Authorization Access Request (SAAR-N) form OPNAV 5239/14 (Rev 9/Sep 2011) on file and complete required Annual Information Awareness Training. New employees must submit their SAAR forms upon check in on their first day of work.

1.8.1. SAARN forms shall be submitted to VX-1 Security

1.9. CAC/Local Badges. Contractor CACs and facility specific identification badges will be approved using the Trusted Agent Sponsorship system and issued by the Government to on-site contractor personnel and shall be visible at all times while personnel are at the Government site.

1.9.1. The contractor shall furnish all requested information required to facilitate issuance of identification badges and shall conform to all instructions/guidance required by the facility.

1.9.2. All CACs and identification badges issued to Contractor employees shall be returned to the Government Security Department at the Government site per the instructions/guidance required by your facility following completion of the contract, relocation or termination of an employee, or upon request from the COR.

1.9.3. The Government will provide the contractor access to Government facilities, as required, for performance of tasks under this contract. Contractor personnel shall comply with the instructions/guidance required by your facility.

1.10. Increased Operational Requirements and Contingency Support.

1.10.1. When applicable, contingency services will be estimated for and ONLY used when:

1.10.1.1. An unanticipated requirement or contingency arises due to changes in testing events or operations;

1.10.1.2. Is within scope of the contract/task order and necessary to complete the work required in the task order;

1.10.1.3. Will take the contractor over their normal 40 hour work (5 days) week; and

1.10.1.4. After concurrence via email from the Operational Test Director (OTD) and COR is received.

1.10.1.5. These services are not considered overtime. These services will be included as a total price of the task order, if ordered.

1.11. Receipt and Acceptance of Deliverables. All deliverables (NIPR or SIPR) will be delivered by the Contractor per the Quality Assurance Surveillance Plan (QASP). These delivered items shall be sent in an email by the contractor to the OTD, Assistant Chief Operational Test Director (ACOTD), Chief Operational Test Director (COTD) (and other applicable recipients) and upon receipt, the government will acknowledge receipt via email. Final acceptance by the government shall be considered once the draft document is smooth and has been signed by the responsible signatory (i.e., ACOS or Commander) or the submitted document is accepted at the requisite level as determined by OT&E Manual. This email will facilitate the formal government’s position for the respective product.

2. Specific Tasking. Per the PWS and the basic contract, the contractor shall provide support in evaluating the operational effectiveness and suitability of the System Under Test (SUT) assigned to VX-1 for OT&E, per the format prescribed in OPTEVFOR 3980.2J series, Operational Test and Evaluation Guide (or other governing references listed in paragraph 5 as applicable). The manual maybe found at:

https://www.optevfor.navy.mil/Portals/103/OPTEVFORINST-3980_2J-OTE-Manual-10-20-21- 1%20%281%29.pdf

2.1. Overall Task Guidance. To gain efficiencies and synergy in contract execution, the Government encourages the Contractor to consider:

2.1.1. Flexibility in production. VX-1 produces information which may take many forms. Support teams should be willing to experiment, bring up new ideas or better ways of doing things, but remain willing to execute stated processes when directed.

2.1.2. Present concerns about the validity of the information produced, and value to the end customer (Fleet or Program). Remain willing to defend a contrary position until the government makes a final decision.

https://www.optevfor.navy.mil/Portals/103/OPTEVFORINST-3980_2J-OTE-Manual-10-20-21-1%20%281%29.pdf https://www.optevfor.navy.mil/Portals/103/OPTEVFORINST-3980_2J-OTE-Manual-10-20-21-1%20%281%29.pdf

2.1.3. Remain efficient and economical in production. Strive to produce information as quickly as possible without sacrificing quality, and with the appropriate level of expertise.

2.1.4. Maintain a broad perspective. Awareness of testing outside of a specific program to seek and recommend testing efficiencies and overall kill-chain evaluation opportunities.

2.1.5. Technical competence. Improve Test and Evaluation (T&E) community’s ability to understand, analyze, communicate, and ultimately visualize T&E issues from a warfighter and technical perspective.

2.2. Test Planning Support

2.2.1. The contractor shall assist in the development of Critical Operational Issues (COI) for OT, Developmental Testing assists, Assessment of Operational Capability, Early Operational Assessments, Operational Assessments, Advanced Concept Technology Demonstrations, Observation of Operational Capabilities, Initial OT&E, and Follow-on OT&E, and compile data necessary to draft the tests (both integrated and operational).

2.2.2. The contractor shall assist in the development of Mission-Based Test Design Framework, in conjunction with mission-based COIs, cross-referenced with Navy Mission Essential Task Lists (NMETL) and/or Joint Mission Essential Task Lists (JMETL) for Integrated Testing (IT)/OT.

2.2.3. The contractor shall conduct background research and provide analytical support and recommendations for the development of data collection plans for testing the operational effectiveness and suitability.

2.2.4. The contractor shall draft Test and Evaluation Master Plan (TEMP) comments and TEMP Part IV.

2.2.5. The contractor shall document test planning support information in the Mission Based Test and

Evaluation System (MBTES) or using other tools if applicable, as required.

2.3. Operational Test/Tactics Exercise Design

2.3.1. The contractor shall design and plan test operations in support of IT, OT or Tactics Exercise.

2.3.2. The contractor shall devise test matrices and procedures for IT and OT to satisfy OPTEVFOR testing objectives.

2.3.3. The contractor shall devise test matrices and procedures to satisfy tactic objectives for Tactics

Exercises, particular to the system under evaluation in concert with the applicable Tactics Officer.

2.3.4. The contractor shall determine data collection/reduction/reconstruction requirements (including hardware and software resources necessary for the collection and storage); identify facilities that provide this processing; and prepare appropriate documentation to support the required service(s).

2.3.5. The contractor shall document OT/Tactics exercise design information in the MBTES or using other tools if applicable, as required.

2.4. M&S Analysis Support

2.4.1. The contractor shall provide support in conducting liaison with model proponents, Independent Verification and Validation (IV&V) agents, developing agencies, Navy laboratories, service Cryptologic Agencies, Navy operational commands, other U.S. Government agencies, and hardware/software contractors to ensure M&S OT&E requirements are addressed to permit timely and effective M&S accreditation in support of OT&E.

2.4.2. The contractor shall develop methods and practices for how M&S can be used to supplement IT and OT and help manage testing risk.

2.4.3. The contractor shall provide support in maintaining an M&S database that consists of the version and accreditation status of all M&S used in OT&E.

2.4.4. The contractor shall document M&S analysis in the MBTES or using other tools if applicable, as required.

2.5. Database Development and Management

2.5.1. The following represents (but is not limited to) the type of data collected during these tests:

2.5.1.1. Qualitative Human Factors Data (Text narrative)

2.5.1.2. Quantitative Flight Log Data (Alpha-Numeric)

2.5.1.3. Qualitative Training Surveys (Text narrative)

2.5.1.4. Qualitative Maintenance Surveys (Text narrative)

2.5.1.5. Built-in Test Results (Alpha-Numeric)

2.5.1.6. Flight costs (Alpha-Numeric)

2.5.2. The contractor shall provide a database consisting of a backend data server and frontend client application for data collection. Any contractor-provided database would need to be backwards compatible with the current database. Aircrew debriefing data will be entered from paper debriefing sheets and kneeboard cards via the client application by government and contractor personnel.

2.5.3. Aircraft Maintenance data will be accessed via the Naval Aviation Logistics Command Management Information System (NALCOMIS) application and downloaded to the contractor-provided database.

2.5.4. The database support for this specific requirement will be provided for the following functional areas:

2.5.4.1. Configuration Management. The contractor shall ensure any new data which affects the database configuration remains compatible with existing systems at VX-1 by:

2.5.4.1.1. Maintaining the capability for further modifications and enhancements to further improve connectivity and improvement of the current configuration as may be required to meet specific test objectives.

2.5.4.1.2. Fully evaluate and recommend a course of action for all proposed system enhancements, including an assessment of the potential impact on current and planned support operations.

2.5.4.2. System Configuration. The contractor shall configure the database to meet program-specific test information requirements as follows:

2.5.4.2.1. Refine and upgrade the database functions to support program-specific data requirements.

2.5.4.2.2. Extract data outside of the database (i.e., NALCOMIS via a data extraction tool) for inclusion in the database-generated reports as required.

2.5.4.2.3. Extract data from onboard (i.e., aircraft mission planning/recording) sources (via a data extraction tool) which will be included in/with the database generated reports as required.

2.5.4.3. System Administration. The contractor shall administer the database systems as follows:

2.5.4.3.1. Configure and operate the database at VX-1.

2.5.4.3.2. Provide on-site administrative support to test and tactics operations.

2.5.4.3.3. Collect feedback for system and process improvement.

2.5.4.3.4. Provide database anomaly analysis and support to ensure availability on a continuous basis.

2.5.4.4. User Training. The contractor shall provide database training by:

2.5.4.4.1. Detailed instruction and orientation on the use of the database, for VX-1 personnel, as required.

2.5.4.4.2. Assisting and training VX-1 personnel on program-specific database support capabilities.

2.5.4.4.3. Updating user training as additional tasking is included.

2.5.4.5. Test Report Documentation Support. The contractor shall:

2.5.4.5.1. Provide on-site information analysis support to test and tactics operations.

2.5.4.5.2. Provide database expertise for compiling and extracting data from the database.

2.5.4.5.3. Provide written reports based on data collected from the database for inclusion in program-specific Evaluation Report.

2.5.4.5.4. Provide printouts of required data collection points for aircrew briefs.

2.5.4.5.5. Collect flight and ground test data and enter into the automated test information system as required.

2.5.4.5.6. Report any test data voids and apparent anomalies based on analysis of the test information entered into system.

2.5.4.5.7. Assist in reducing the test data into selected reports and preparing an overall evaluation of the effectiveness and suitability of project under evaluation.

2.5.4.5.8. Interface with NALCOMIS for the direct collection of reliability and maintainability data.

2.5.4.5.9. Provide the tracking and reporting of required system performance calculations, as determined by specific projects under test.

2.5.4.5.10. Provide collation and analysis of qualitative data, as determined by specific test.

2.6. Test Operations/Tactics Evaluation Support

2.6.1. The contractor shall attend program review meetings with OTD/Tactics Officer during the timeframe in various locations and provide technical reports.

2.6.2. The contractor shall assist OTD/Tactics Officer as required in briefing test/exercise participants, emphasizing the event objectives and specific data-gathering requirements for each participant.

2.6.3. The contractor shall observe test/exercise events as appropriate with OTD/Tactics Officer, collect test data, and provide technical reports.

2.6.4. The contractor shall attend program review meetings with OTD(s) during the timeframe in various locations and provide asset availability and configuration reports.

2.6.5. The contractor shall track aircraft asset utilization for aircraft assigned to charged effort and devise optimized planning tools.

2.6.6. The contractor shall maintain detailed aircraft configuration records for aircraft assigned to the effort charged.

2.6.6.1. The contractor shall track configuration changes, including initiating aircraft configuration change forms, “pink sheets.”

2.6.6.2. The contractor shall track status on all outstanding pink sheets.

2.6.6.3. The contractor shall track aircraft deficiencies and their effect on upcoming testing, assist squadron in determining required resources to correct aircraft deficiencies.

2.6.6.4. The contractor shall devise aircraft utilization to balance maintenance and operations requirements with test events.

2.6.6.5. The contractor shall coordinate and track instrumentation, aircraft configuration and maintenance actions.

2.6.7. The contractor shall define, document and investigate issues with aircraft assigned to the effort charged, aircraft configurations, and test assets to provide solutions to schedule conflicts.

2.6.8. The contractor shall coordinate IT efforts with other platforms and squadrons for aircraft assigned to the effort charged.

2.6.9. The contractor shall interpret long-range project goals to formulate a weekly schedule plan for all aircraft assigned to the effort charged.

2.6.10. The contractor shall develop, maintain and coordinate weekly and daily flight schedules for all aircraft assigned to the effort charged.

2.6.11. The contractor shall participate in operations coordination meetings with outside entities/squadrons as necessary.

2.7. Test/Tactics Analysis and Reporting

2.7.1. The contractor shall provide technical comment on changes made to the draft test plan /exercise plan during staffing.

2.7.2. The contractor shall perform data reduction and analysis of data to ensure data validity, prior to more-detailed data processing.

2.7.3. The contractor shall correlate data using appropriate statistical techniques to analyze operational effectiveness and suitability tests.

2.7.4. The contractor shall provide follow-up assistance as necessary on reports and briefs.

2.7.5. The contractor shall assist in the development of draft blue/gold sheets in the appropriate

OPTEVFOR and/or VX-1 format.

2.7.6. The contractor shall assist in the development of draft test/tactics evaluation reports in the appropriate OPTEVFOR and/or VX-1 format

2.8. Program Management Support

2.8.1. The contractor shall provide trip reports and monthly reports including progress on assigned tasks, conferences/meetings attended, work plans, and the expenditure of funds and labor hours during the month.

2.8.2. The contractor shall provide support in conducting liaison with developing agencies, Navy laboratories, Navy Operational Commands, other U.S. Government agencies, and hardware/software contractors to ensure requirements are addressed to permit timely and effective testing/evaluation.

2.8.2.1. The contractor shall develop and document input to the TEMP per the Director, Operational Test and Evaluation Guidebook 3.1, https://www.dote.osd.mil/Portals/97/docs/TEMPGuide/TEMP-Guidebook/3.1a.pdf

2.8.2.2. The contractor shall develop and document comments to the TEMP related to or affecting

OT&E.

2.9. Government Training

2.9.1. The Contractor is eligible to take OPTEVFOR provided training, including OTD Basic Course (OBC); Advanced MBTES Course; M&S Course; Test Planning Course; Post Test Iterative Process (PTIP) Course; Reliability, Maintainability, Logistic Supportability and Availability (RMLA) Course; Blue & Gold Sheet Writing Course; Cyber Test Planning Course; and Effective Technical Writing Course. Contractors are encouraged to stay informed on course updates to ensure training currency.

2.9.2. To register for a course, you must request an account through OPTEVFOR’s LMS which can be found on the OPTEVFOR Sharepoint page: https://flankspeed.sharepoint-mil.us/sites/OPTEVFOR/SitePages/01A-Division-Workforce-Development.aspx

2.9.3. The Contractor shall comply with training required at the TO level.

2.9.4. TO will provide training requirements. NOTE: Some TOs may require completion of specific training at date of award due to Program scheduled events.

2.10. Administrative Support

2.10.1. The Contractor shall provide the COR with Monthly Status Reports. Monthly Status Reports should provide sufficient detail and organization to allow OTDs to track progress, performance, and funds expenditure at the program level.

2.10.2. The Contractor shall provide program management input and attendance to leadership meetings as needed to coordinate overall level of effort and support to assigned tasks, conferences/meetings attended, work plans, and the expenditure of funds and/or labor hours during the month.

2.11. Financial Tracking and Support

2.11.1. The contractor shall provide financial tracking for the complete execution of this contract.

Financial status shall be reported to the government in the Monthly Status Report and Annual Summary Report.

3. Deliverables. The Government reserves the right to specify deliverables at the TO level. Data items required from the contractor are specified below. Quantities, delivery dates, and other particulars will be identified in the individual TO issued under this contract.

3.1. Framework Development

3.1.1. The contractor shall provide draft T&E framework input per OPTEVFOR policy. This deliverable is normally due early in program development. Depending on the size and scope of the program, the actual delivery date will be determined by the VX-1 ACOTD.

3.2. Draft TEMP Input

3.2.1. The contractor shall provide draft TEMP, derived from scenarios, COIs and detailed test objectives, and resource summary. This deliverable is normally due not later than 30 calendar days after delivering the draft OT&E scenarios, COIs and detailed test objectives, and shall be consistent with prior test planning deliverables with incorporated government comments.

https://www.dote.osd.mil/Portals/97/docs/TEMPGuide/TEMP-Guidebook/3.1a.pdf

3.3. Draft Test/Tactics Evaluation Plan

3.3.1. The contractor shall draft test plan inputs. The contractor shall prepare the OT&E inputs (both IT and OT) as advised by the OTD prior to 9 months before the test/tactics event (unless agreed upon by the OTD).

3.4. Test Database Support

3.4.1. The contractor shall provide database setup and/or manipulation to support the data collection and analysis as provided by the OTD and/or test/tactics analyst. Due 5 months prior to start of test/tactics evolution and throughout testing and analysis periods.

3.5. Draft M&S Plan

3.5.1. The contractor shall prepare a draft M&S plan detailing OPTEVFOR requirements for IV&V to permit accreditation in support of OT&E objectives, per OPTEVFORINST 5000.1D.

3.6. Test/Tactics Operations Support

3.6.1. Deliverable may take the form of draft comment letters, draft presentations, and spreadsheets to be submitted within 5 working days after receipt of designated documents from government, unless otherwise agreed upon with the OTD.

3.7. Maintain Aircraft Configuration Records for Applicable Aircraft

3.7.1. The contractor shall draft deliverables in VX-1 format to be submitted as required after receipt of designated documents from government (unless agreed upon by the OTD).

3.8. Analysis and Reporting of Data

3.8.1. The contractor shall provide on-site technical data collection, analysis and reporting for each test/tactics event conducted, within 5 days after completion of the event.

3.9. Draft Blue/Gold Sheets and Test/Tactics Evaluation Report

3.9.1. The contractor shall provide draft blue/gold sheets as required within 10 days of identification of risk/deficiency.

3.9.2. The contractor shall provide a draft Test and/or Tactics report in OPTEVFOR/VX-1 format as required within 30 days after the end of test operations. Format will be provided by the Government.

3.10. Draft Briefs

3.10.1. The contractor shall produce a draft(s) in OPTEVFOR/VX-1 format, as required. Format will be provided by the Government for the following types of briefs: Concept of test; test plans; test reports; detachment briefings. Submissions will be based on each specific requirement

3.11. Monthly Progress Reports

3.11.1. The contractor shall prepare a progress, performance and funds expenditure by 15th of the month starting 1 month after contract award date.

3.11.2. Contractor format acceptable.

3.12. Trip Reports

3.12.1. The contractor shall prepare a trip report detailing key information issued at the program meeting attended within 10 working days after returning from the meeting.

3.12.2. Contractor format acceptable.

3.13. Annual Summary Report

3.13.1. The contractor shall prepare a summary report 30 days after each option year has ended with detailed accounting of fund expenditure and program support provided to VX-1 for each task order.

4. Training

4.1.1. OPTEVFOR Training

4.1.1.1. The Contractor is eligible to take OPTEVFOR provided training, including Operational Test Director (OTD) Course, Integrated Evaluation Framework (IEF) Course, Test Planning Course, PTIP Course and RMLA Course. Contractors are encouraged to stay updated on course updates to ensure training currency. (add more training, if needed)

4.1.1.2. Training class availability and registration can be found on the OPTEVFOR public homepage:

https://www.optevfor.navy.mil/Test-and-Evaluation/Register-for-OPTEVFOR-Courses/

4.1.1.3. The Contractor shall comply with training required at the TO level.

4.1.1.4. TOs may/will specify what training is required. NOTE: Some TO may/will require completion of specific training at date of award due to Program scheduled events.

4.1.2. Contract Specific Training

4.1.2.1. Anti-Terrorism Awareness Level 1 (http://jko.jten.mil/)

4.1.2.2. PII (https://securityawareness.usalearning.gov/piiv2/index.htm)

4.1.2.3. Cyber Awareness (https://public.cyber.mil/training/cyber-awareness-challenge/)

4.1.2.4. Combating Trafficking in Persons (https://ctip.defense.gov/)

5. QASP. The Government will monitor the Contractor's performance to ensure compliance with contract requirements, inclusive of the terms and conditions, in accordance with QASP.

6. Minimum Personnel Requirements. The contractor will submit within the proposal at the TO level its proposed labor categories, hours, and skillsets to ensure successful performance of the requirements identified within the PWS. As described in the minimum personnel requirements, relative and comparative emphasis is given where applicable between the testing, analytical, and/or writing competencies within respective labor categories.

6.1. These contractor-proposed labor categories may be in addition to the customer’s required labor categories incorporated into the contract for review and approval prior to performance on any applicable TO award.

6.2. If the customer does not identify a labor category at the TO level during the request for proposal, it will be up to the contractor to determine which labor categories and qualifications to propose (which may include those identified within the contract) at the TO level to achieve success.

6.3. Requirements for All Offerors. All personnel proposed in support of this contract shall:

6.3.1. Possess U.S. citizenship.

6.3.2. A minimum-security clearance of SECRET is required for personnel supporting tasks in any/all divisions. Any personnel proposed to work on any effort shall be eligible for necessary clearances to immediately begin performance at the time of task award. A minimum-security clearance of Top Secret (TS)/TS Special or Sensitive Compartmented Information (SCI) may be required on individual TOs and will be identified on a separate DD254 at time of task order solicitation.

6.3.3. Demonstrated familiarity with MS-Office software.

7. Government Labor Categories

7.1. Program Manager

7.1.1. Ten or more years (within the last 15) of specialized professional experience in developmental or OT&E of tactical aircraft, weapons, software, or systems and/or tactics development and evaluation.

Of the 10 years, 4 years must be in a project or program management capacity. .

7.1.2. Must have current working knowledge of the Navy and multi-service missions, operations, logistics, management, and organizational responsibilities.

7.1.3. Must have working knowledge of the DoD 5000 series, OPNAVINST 5000.42 series, as well as SECNAVINST 5000 series instructions.

7.1.4. Must have demonstrated the ability to interact effectively within the naval community and have a demonstrated ability to communicate the results of the operational analysis to sponsoring activities and decision makers.

7.1.5. Proficient in developing Plan of Actions and Milestones for delivering OT&E products to

OPTEVFOR

7.1.6. Proficient in the use of Microsoft Office products, to include MS Word, Excel, MS Project, and Power Point.

7.2. Senior T&E Specialist

7.2.1. Must have extensive T&E experience (4 of last 6 years), such as IEF development, Test Plan Development, Test Execution, Test Analysis and Reporting, and M&S experience supporting developmental or operational testing. .

7.2.2. Experience in developing M&S Accreditation Packages and Accreditation Letters.

7.2.3. Must possess proficient experience in analysis methodologies.

7.2.4. Must have working knowledge of the DoD 5000 series, OPNAVINST 5000.42 series, as well as

SECNAVINST 5000 series.

7.2.5. Proficient in use of Microsoft Office products, to include MS Word, MS Excel, MS Project, and MS

Power Point

7.2.6. Proficiency in technical writing.

7.2.7. Must have demonstrated the ability to lead effectively and have a demonstrated ability to communicate the results of the operational analysis to sponsoring activities and decision makers.

7.3. Junior T&E Specialist

7.3.1. Must have T&E experience (2 of last 4 years), such as IEF development, Test Plan Development, Test Execution, Test Analysis and Reporting, and M&S experience supporting developmental or operational testing. OPTEVFOR experience desired.

7.3.2. Formal training in or demonstrated experience in developing M&S Accreditation Packages and Accreditation Letters

7.3.3. Must possess proficient experience in analysis methodologies.

7.3.4. Proficient in use of Microsoft Office products, to include MS Word, MS Excel, MS Project and MS

Power Point

7.3.5. Proficiency in technical writing

7.3.6. Must have a demonstrated ability to communicate the results of the operational analysis to sponsoring activities and decision makers.

7.4. Senior Database Manager

7.4.1. Four or more (within the last 8 years) of specialized professional experience in development and management of complex databases. Direct experience in developmental or operational T&E and/or tactics evaluation of aircraft, weapons or systems.

7.5. Junior Database Manager

7.5.1. One year experience in database development and management.

7.6. Aircraft Coordinator

7.6.1. Knowledge and/or expertise with Naval aircraft programs.

7.6.2. Current working knowledge of Naval aircraft maintenance procedures, specifically experience executing maintenance per OPNAV 4790 series.

7.6.3. Current T&E configuration management experience, specifically in management of DoD assets.

8. Additional Qualifications

8.1. Additional qualifications specific to the task order SUT, as referenced in section 1.2 of this solicitation, may be required to successfully complete the tasking.

9. Security Clearance Required. It is anticipated a minimum-security clearance of SECRET eligible will be required for personnel supporting this Contract, and this will be identified at the TO level; therefore, the offeror must be able to provide a contractor (when required at the TO level) with a minimum security clearance of SECRET. However, some task orders may require TS/TS SCI Eligible personnel, which will be identified in the TO’s PWS. Any personnel proposed to work on any effort shall be eligible for necessary clearances to immediately begin performance at the time of task award. Specific security requirements will be identified on a separate DD254 at time of TO solicitation.

10. Acronym List.

ADP Automated Data Processing CAC Common Access Card CLIN Contract Line Item Number COI Critical Operational Issue CONUS Continental United States COR Contracting Officer Representative DoD Department of Defense GFP Government Furnished Property IEF Integrated Evaluation Framework INST Instruction IT Information Technology IV&V Independent Verification and Validation M&S Modeling and Simulation MBTES Mission Based Test and Evaluation System NALCOMIS Naval Aviation Logistics Command Management Information System NAS Naval Air Station OCONUS Outside the Continental United States ODC Other Direct Cost OPNAV Office of the Chief of Naval Operations OPTEVFOR Operational Test and Evaluation Force OPTEVFORINST Operational Test and Evaluation Force Instruction OT Operational Testing OT&E Operational Test and Evaluation OTD Operational Test Director PTIP Post Test Iterative Process PWS Performance Work Statement QASP Quality Assurance Surveillance Plan RMLA Reliability, Maintainability, Logistic Supportability, and Availability SAAR-N System Authorization Access Request SCI Special or Sensitive Compartmented Information SECNAV Secretary of the Navy SUT System Under Test TO Task Order T&E Test and Evaluation TEMP Test and Evaluation Master Plan VX-1 Air Test and Evaluation Squadron ONE

11. References.

11.1. DoD 5000.01 series, The Defense Acquisition System (DoD 5000.01)

11.2. DoD 5000.02 series, Operation of the Defense Acquisition System (DoD 5000.02)

11.3. SECNAVINST 5000.2 series, Implementation and Operation of the Defense Acquisition System and the

Joint Capabilities Integration and Development System (SECNAVINST 5000 series)

11.4. OPTEVFOR Operational Test and Evaluation Manual (OPTEVFORINST 3980.2J)

11.5. OPTEVFORINST 5000.1 series, Use of Modeling and Simulation (M&S) in Operational Test (OT)

11.6. CJCSM 3500.04 series, Universal Joint Task List (UJTL)

http://dtic.mil/cjcs_directives/cdata/unlimit/m350004.pdf

11.7. OPTEVFORINST Policy Series

11.8. Program TEMP

11.9. Program Operational Requirements Document (ORD)

11.10. Navy System Training Plan (NSTP)

11.11. User's Shipboard Logistics Support Summary (ULSS)

11.12. Program Integrated Logistics Support Plan (ILSP)

11.13. DODI 5200.40 series, DoD Information Technology Security Certification and Accreditation Process

(DITSCAP), 1990 http://www.public.navy.mil/cotf/OTD/5200_40.pdf

11.14. DODD 8500.1, Information Assurance (IA), 2002 http://www.dtic.mil/whs/directives/corres/pub1.html

11.15. DODI 8500.2, Information Assurance (IA) Implementation, 2003 http://www.dtic.mil/whs/directives/corres/pub1.html

11.16. OPTEVFORINST 5239.7, Protection of Controlled Unclassified Information (CUI) http://www.dhra.mil/perserec/osg/s2unclas/intro.htm

11.17. Defense Acquisition Guidebook (DAG) series https://dag.dau.mil/Pages/Default.aspx

11.18. CJCJM 3170 series, Joint Capabilities Integration and Development System http://dtic.mil/cjcs_directives/cjcs/manuals.htm

11.19. OPTEVFOR applicable product templates

11.20. Applicable DoD and Department of the Navy T&E Instructions SECNAV M 5000.2 series, Department of Navy Acquisition and Capabilities Guidebook http://doni.daps.dla.mil/SECNAV%20Manuals1/5000.2.pdf

11.21. OPNAV Instruction 3501.2 series, Required Operational Capability And Projected Operational

Environment Statements http://fas.org/irp/doddir/navy/opnavinst/

11.22. DODD 8570.01 M DoD Information Assurance Workforce Improvement Program

11.23. DODD 8140.01 DoD Cyberspace Workforce Management

http://dtic.mil/cjcs_directives/cdata/unlimit/m350004.pdf http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dtic.mil/whs/directives/corres/pub1.html http://www.dhra.mil/perserec/osg/s2unclas/intro.htm http://dtic.mil/cjcs_directives/cjcs/manuals.htm http://doni.daps.dla.mil/SECNAV%20Manuals1/5000.2.pdf http://fas.org/irp/doddir/navy/opnavinst/

11.24. OPTEVFORINST 5239.1 Series OPTEVFOR Cybersecurity Program