N0018920R0017-0002.pdf

N5702320COTFD50

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to make changes to the solicitation. Please see the continuation pages.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 40

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 26-Mar-2020

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N0018920R0017

X 9B. DATED (SEE ITEM 11)

12-Mar-2020

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer X is extended, is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

26-Mar-2020

CODE

NAVSUP FLC NORFOLK CONTRACTING

NORFOLK OFFICE

ATTN: C. WALTON

1968 GILBERT ST, SUITE 600

NORFOLK VA 23511-3392

N00189 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0018920R0017

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

AMENDMENT 0002

1. The purpose of this amendment is to make changes to the solicitation.

2. The following paragraphs in the performance work statement are revised:

6.4.3 through 6.20.2.3

3. This amendment incorporates solicitation questions and provided answers.

4. The deadline for receipt of proposals is changed to 20 April 2020 12:00 P.M EST

5. All other terms and conditions remain unchanged.

6. Update Attachment 4, Price Worksheet

(End of text)

QUESTIONS AND ANSWERS - 0002

Questions and Answers

Question 1: Taken together, Performance Work Statement (PWS) paragraphs 5.3 on page 72 and 8.0 on page 80 are confusing. We believe the Government means that all personnel must have a minimum Secret clearance, and certain individuals (to be identified at the task order level) will require Top Secret. Will the Government please clarify?

Answer 1: a. A minimum of SECRET is required for access to COMOPTEVFOR. It is anticipated that a minimum-security clearance of TOP SECRET eligible will be required for personnel supporting this Contract, and this will be identified at the Task Order level, therefore the offeror must be able to provide a contractor (when required at the Task

Order Level. 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 task order solicitation.

b. Summary: The offeror must be able to provide Contractor support “when needed” to support the TS requirement, however SECRET will be required for access and program support.

Question 2: In paragraph 1.11 on page 62, it appears the parenthetical “(NIPR/SIPR)” is inserted in error. Will the Government please clarify?

Answer 2: The mention of NIPR/SIPR is intentional as it refers to: NIPRNet, the Non-

Classified Internet Protocol Router Network or the Secret Internet Protocol Router

Network (SIPRNet). Refers to the deliverables that may be produced on either of the two networks.

Question 3: 3. Concerning the last two paragraphs of Factor 3 on Page 103, if a Past

Performance contract is reported under CPARs, does the offeror still have to provide a Past

Performance Report Form for that contract?

Answer 3: It is up to the Offeror.

Question 4: In Attachment 4, Price Worksheet, the Extended Price columns (cells d4 – d28, g4-g28, etc.) do not automatically calculate Hours * Unit (Hourly) Price. Similarly, the Labor Totals cells (d29, g29, etc.) do not automatically calculate. Does the Government wish for offerors to furnish their own calculations for these cells?

Answer 4: Yes the offeror can furnish their own calculations; however, the contracting office will update Attachment 4, Price Worksheet

Question 5: The Government intends to award a single, IDIQ, firm-fixed-price contract. How will Task orders be issued? Will a task order be issued specific for each System Under Test? Or will a blanket task order be issued for general 50 Division support?

Answer 5: Task orders will be issued as work is identified. The Government anticipates that task orders will be issued for each system under test. The Government does not anticipate issuing a single blanket task order for general 50 Division support.

Question 6: Will the task orders be deliverable based or Level of Effort?

Answer 6: Firm-fixed-price (FFP) task orders will be issued, with cost reimbursable

CLINs for travel, if required.

Question 7: How will Task orders be negotiated? Will the government issue a Request for quote for each task order for the offeror to propose a staffing mix (including labor categories and hours)? Or, will the government award a firm fixed price based on the IDIQ proposed prices and the government’s estimated level of effort required to accomplish the deliverables?

Answer 7: The Government will issue firm-fixed-price (FFP) task orders under this contract, with cost-reimbursement CLINs for travel, if required. The FFP labor will be based on the basic contract’s labor rates incorporated at the time of award. The contractor will propose labor categories, hours, and skill sets to meet the requirements in a task order PWS. The customer may also require certain labor categories in a particular task order PWS. See PWS paragraphs 5 and 5.2. as amended.

Question 8: How much advanced notice will the awardee have prior to a task order being awarded to properly staff the positions, including getting through the COTF check in process

(security and IT).

Answer 8: The Government intends to provide as much notice as practicable in advance of new requirements. As COTF receives notification of new systems under test from its supported customers, COTF intends to engage the contractor regarding future support required through frequent and recurring discussions with the divisional leadership. See

PWS paragraph 2.9.2.

Question 9: Please explain the significance of the amount of labor hours provided in the price worksheet. Is this an estimated level of effort? Is this an historical level of effort? Will the awardee be expected to staff all positions on day one of the IDIQ award?

Answer 9: The hours provided are an estimate based on historical data and anticipated future requirements. The labor categories in the PWS are those skill sets to be utilized during execution of the contract at the task order level. The awardee should be prepared for full performance upon award.

Question 10: PWS Paragraph 5 “Minimum personnel requirements” states:

5.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 task order award.

Can offerors propose additional labor categories on the IDIQ RFP?

Answer 10: No, offerors cannot propose additional labor categories for the solicitation.

Offerors must provide rates only for the labor categories identified in the PWS and

Attachment 4.

If the skill set for a particular task order system under test may be best met by a category not in the basic contract, new proposed labor categories may be added, as appropriate, to the contract via a bilateral modification. Please see para 5.1 of the PWS.

During divisional leadership meetings (see paragraph 2.9.2), the contractor may provide input and insight into skills sets that can be utilized to accomplish future work for incoming systems under test.

Question 11: PWS Paragraph 5 “Minimum personnel requirements” states:

5.2 if the customer does not identify a labor category at the task order 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) they will propose at the task order level to achieve success.

Can the offeror propose labor categories and qualifications other than what is stated in para 6 and 7? If so, do these need to be proposed at the IDIQ level?

Answer 11: No, offerors cannot propose additional labor categories for the solicitation.

Offerors must provide rates only for the labor categories identified in the PWS and

Attachment 4, Price Worksheet.

If the skill set for a particular task order system under test may be best met by a category not in the basic contract, , new proposed labor categories may be added, as appropriate, to the contract via a bilateral modification. Please see para 5.1 of the PWS.

During divisional leadership meetings (see paragraph 2.9.2), the contractor may provide input and insight into skills sets that can be utilized to accomplish future work for incoming systems under test.

Question 12: Please confirm that all offerors must propose the same amount of labor hours

(government provided) in the price worksheet?

Answer 12: Offerors must propose the same amount of labor hours on Attachment 4, Price Worksheet.

Question 13: Please confirm that all offerors must propose the same labor categories

(government provided) on the price worksheet.

Answer 13: Offerors must propose the same labor categories on Attachment 4, Price

Worksheet.

Question 14: Paragraph 7 is titled “Minimum Requirements for All Contactor Personnel.” It then references to other paragraphs (5.3 & 8). The next 6 sub paragraphs (7.1-7.6) are labor categories. Are those 6 labor categories minimum requirements for all contractor personnel, or additional labor categories that should fall under para 6?

Answer 14: The Labor categories in 7.1 thru 7.6 MUST meet the minimum requirements defined in 5.3 and 8.

Question 15: Please clarify the difference between the labor categories defined in paragraphs

6.2-6.20 and the labor categories defined in paragraphs 7.1-7.6.

Answer15: They are all categories you must propose to in your response.

Question 16: Are the Cyber Survivability Materials for the IEF and Test Report considered GFI from 01D?

Answer 16: The information identified by the contractor to support Cyber Survivability will be performed independently and in coordination with a 01D Government representative. The Government representative will work with the supported Program

Office or customer to obtain Government information needed by the contractor to complete the work.

Question 17: In Section 2.1 (Test Design) of Section 2 (Specific Tasking), there are two subsections that seem repetitive. Section 2.1.4. is titled Stakeholder Collaboration (Working

Integrated Product Teams (WIPTs), outreach, etc.), and section 2.1.7 is titled Stakeholder

Collaboration. There is only 1 subtask difference between the two subsections. Was this a copy/paste error? Or was the intent to differentiate between the two subsections?

Answer 17: They are different, please read the PWS

Question 18: RFP Page 43 (c) identifies application of the Service Contract Labor Standards to this requirement; however, no WD was included with the RFP package. Will the Government please confirm whether any of the required LCATs are covered by the SCA, and if so, which ones and under which WD(s)?

Answer 18: Wage Determination will be included in the solicitation amendment.

Question 19: Through what contract administration functions will the Government monitor compliance with 52.219-14 LIMITATIONS ON SUBCONTRACTING (DEVIATION 2019-

O0003) (JAN 2019) during contract execution?

Answer 19: The solicitation contains 52.219-14 LIMITATIONS ON

SUBCONTRACTING (DEVIATION 2019-O0003) (JAN 2019). By submission of an offer and execution of a contract, the offeror certifies that it will comply with this clause.

Question 20: On pages 4 and 5 of the SF 1449 Continuation Sheet, CLIN 0003 has a “total not-to-exceed amount plus burdens” of $2,088,552.26 and CLIN 1003 has a “total not-to-exceed amount plus burdens” of $219,288.28. In the Price Worksheet, the total must-bid unburdened travel amount for years 1-5 is $2,088,552.26 and the Option (52.217-8) is $219,288.28 . When filling out the Price Worksheet submission, if an offeror then applies any applicable General and

Administrative (G&A) and/or Overhead (OH) rates that may be applicable in accordance with

FAR Part 31 and the offeror’s accounting system, then their total will exceed both CLIN 0003 and CLIN 1003. Will the CLIN 0003 and CLIN 1003 not-to-exceed total in the SF 1449

Continuation Sheet be adjusted post-award if the winning offeror’s burdened travel bid exceeds

$2,088,552.26 and $219,288.28?

Answer 20: The application of overhead to the Government-provided travel amounts is for evaluation purposes only. For award purposes, the contract will be awarded with the not-to-exceed amounts shown in CLINs 0003 and 1003.

Question 21: The underlying formulas in the Price Worksheet, Column D, rows 4 through 28 and row 32 and in columns G, J, M, P and S are not populated. Is it acceptable for the offeror to add the formulas for accuracy of the data?

Answer 21: Yes the offeror can furnish their own calculations; however, the contracting office will update Attachment 4, Price Worksheet

Question 22: On page 55 of the SF 1449 Continuation Sheet under SECURITY

ADMINISTRATION (SOLICITATION) (SEP 2015), does “cognizant security office” refer to the offeror’s security office or the appropriate oversight Defense Counterintelligence and

Security Agency (DSCA) office?

Answer 22: The Defense Counterintelligence and Security Agency (DCSA) office.

Question 23: On page 55 of the SF 1449 Continuation Sheet under SECURITY

ADMINISTRATION (SOLICITATION) (SEP 2015), it states that the offeror should “provide the (same) information on all proposed subcontractors.” Should this subcontractor information be inserted into the proposal Reps & Certs, or be provided post award?

Answer 23: The offeror should also provide the above information on all proposed subcontractors that will be required to have a security clearance.

Question 24: On page 55 of the SF 1449 Continuation Sheet under NOTICE OF OCI CLAUSE, does the Government require an affirmation statement if no OCI exists among the offeror and its subcontractors? If so, in what Volume of the proposal should this statement be included? and does it count against page limitations?

Answer 24: Prospective offerors are requested to furnish with their proposals, information pertaining to any existing contract between the offeror and the companies engaged in furnishing to the United States Government any services or supplies pertaining to the development, production or analysis of any of the weapon systems, equipment or programs identified in the statement of work of this solicitation or listed below, if any, which may have a bearing on any existing or potential conflict of interest within the meaning of the clause in the Schedule. Such information shall include:

1. The identity of the company

2. A description of the work to be performed under the contract with the company or the relationship between the offeror and the company

3. The dollar amount of the contract or any other ownership interest

4. The period of performance

5. A description of the internal control taken by the offeror to avoid potential organizational conflict of interest, and

6. Any other information requested by the contracting officer.

Question 25: On page 67; para 2.2.8; should this reference to CDRL A001 pertain to test plan products rather than IEF products?

Answer 25: No, please respond to the PWS

Question 26: On page 68; para 2.3.6: should this reference to CDRL A001 pertain to M&S

Answer 26: No, please respond to the PWS

Question 27: On page 70; para 2.5.7.1, should this reference to CDRL A001 pertain to PTIP

Answer 27: No, please respond to the PWS

Question 28: On page 71; para 3.1.3, the abbreviation “MTS” is not defined in the RFP. Please define.

Answer 28: Products supporting TEMP or MTP development, in accordance with section

2 above

Question 29: On page 71; para 3.1.5, was it the government’s intention to caveat this statement by stating “as specified at the Task Order level”?

Answer 29: Yes that is inferred.

Question 30: Beginning on page 73 in the PWS paragraph 6 Additional Qualifications section, the following subparagraphs appear to be presented one level too high, specifically:

6.4.3 should be 6.4.2.3 – Amended

6.6.3 should be 6.6.2.3 - Amended

6.7.3 should be 6.7.2.3 - Amended

6.8.3 should be 6.8.2.3 - Amended

6.9.3 should be 6.9.2.3 - Amended

6.10.3 should be 6.10.2.3 - Amended

6.11.3 should be 6.11.2.3 - Amended

6.12.3 should be 6.12.2.3 - Amended

6.13.3 should be 6.13.2.3 - Amended

6.14.3 should be 6.14.2.3 - Amended

6.15.3 should be 6.15.2.3 - Amended

6.16.3 should be 6.16.2.3 - Amended

6.17.3 should be 6.17.2.3 - Amended

6.18.3 should be 6.18.2.3 - Amended

6.19..3 should be 6.10.2.3 - Amended

6.20.3 should be 6.20.2.3. - Amended

Answer 30: See enclosed revised PWS Amendment 0002

Question 31: On page 76 in the SF 1449 Continuation Sheet under 6.16, Navy Unmanned

Aviation Systems Specialist lists Airborne EW qualifications vice unmanned systems experience. Are these Airborne EW qualifications correct for the Unmanned Aviation Systems?

Answer 31: Yes please respond to the PWS

Question 32: The Proposal Page Limitations section on page 100 lists Volume I: Facilities

Security Clearance and Volume I: Technical as separate hardcopy requirements. Does the

Government desire two separate Volume I documents with two separate cover pages?

Answer 32: No, only one Volume I

Question 33: On page 101 of the SF 1449 Continuation Sheet, under Factor 2 Technical, it states “This volume shall address the technical factor and sub-factors.” The sub-factors are subsequently defined but the “technical factor” is not. What is the “technical factor” to be addressed?

Answer 33: Offerors shall provide, in detail, a technical approach that demonstrates a complete understanding of and the capability to fully implement and execute all requirements of the solicitation and performance work statement (PWS). The offeror’s response shall address each of the identified sub-factors.

Question 34: On page 102 of the SF 1449 Continuation Sheet under Factor 3 – Past

Performance, can the current COMOPTEVFOR OMNIBUS contract be treated as a single past performance example?

Answer 34: Yes

Question 35: Based on the current national emergency declaration for the COVID-19 pandemic, and major disruptions to normal operations for Government, Industry, and their workforces; will the Government consider a two-week extension to this solicitation? Some specific impacts to a normal completion timeline include availability of Government representatives to complete Past

Performance Reports and the ability of the Government to return answers to these RFP questions in time for Industry to consider and incorporate in their proposals.

Answer 35: The deadline for receipt of proposals is changed to 20 April 2020 12:00 P.M

EST

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 15-Apr-2020 12:00 PM to 20-Apr-2020 12:00 PM.

The following have been modified:

LIST OF ATTACHMENTS

1 – DD 254, Contract Security Classification Specification

2 – Past Performance Information Form

3 – Past Performance Report Form

4 – Services Price Worksheet

5 – Wage Determination No.2015-4342 Revision No.14 dated 12/23/2019

(End of Attachments)

PERFORMANCE WORK STATEMENT

1. Scope of Tasking. Contractor will provide technical and analytical support to Commander, Operational Test and Evaluation Force (COMOPTEVFOR) in the definition, conduct and analysis of structured Operational Test and Evaluation (OT&E) of US Navy systems. This support will be required in one or more of the following forms: Documentation Review, Test Planning Support, Operational Test Design, Test Analysis and Reporting, Test Operations Support, Modeling and Simulation Support, and Program Management Support.

COMOPTEVFOR is charged with leading the Operational Test 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 There are five warfare divisions that are supported by competency divisions. The Aviation

Warfare division (Code 50) resides on the 2 nd deck. Code 50 division has a Navy Captain as the division

Director with a senior civil servant as the division Deputy Director.

Aviation warfare division represent the traditional core of the COMOPTEVFOR organization. This is where the Fleet operators reside. The work there allows COMOPTEVFOR to bridge the gap from technical to the tactical, successfully. The aviation warfare division is staffed by uniformed military personnel and Navy government civilians, augmented by a contractor workforce.

There are four competency divisions: Policy and Operations (01A), Test Design (01B), Test Planning and

Analysis (01C) and Cybersecurity Testing (01D). In addition, the Technical Director (00TD) oversees the technical aspects of the Command’s mission. Other support divisions include the Staff Commanding

Officer and Administration (10), Chief Information Officer (CIO) (20), Contracts (01), and the

Comptroller (30). The members of the competency divisions generally work within the test team to ensure that the Commander’s policies are adhered to and that best practices are applied.

1.2. For scoping purposes, a description of Aviation Warfare division and competency are listed below, as well as a current list of their respective evaluation programs being performed. These division program lists are current as of time of solicitation and additional programs may be assigned to COMOPTEVFOR for contractor support under this contract.

1.2.1. The Aviation Warfare Division, Division Code 50 Tests and evaluates all of the Navy and

Marine Corps' aviation acquisition programs warfare systems such as strike/fighter weapons; assault weapons; aviation electronic warfare; air antisubmarine warfare; aviation maintenance; and trainers, under the most operationally realistic conditions possible. The aviation warfare division also coordinates with the following squadrons; VX-1 (Patuxent River, MD), VX-9 (China Lake, CA), VMX-1 (Yuma, AZ) and HMX-1 (Quantico, VA).

1.2.1.1. F/A-18A+/C/D/E/F System Configuration Set (SCS)

1.2.1.2. F/A-18 Active Electronically Scanned Array (AESA) Radar

1.2.1.3. F/A-18 Advanced Targeting and Designating Forward Looking Infrared (ATFLIR) System

1.2.1.4. F/A-18 Shared Airborne Reconnaissance Pod (SHARP)

1.2.1.5. F/A-18 Infrared Search and Track (IRST) System

http://www.ncts.navy.mil/homepages/vx-1 http://www.nawcwpns.navy.mil/~VX9/

1.2.1.6. Advanced Anti-Radiation Guided Missile (AARGM)

1.2.1.7. Joint Direct Attack Munitions (JDAM)

1.2.1.8. AIM-9X SIDEWINDER

1.2.1.9. AIM-120D AMRAAM

1.2.1.10. Joint Helmet Mounted Cueing System (JHMCS)

1.2.1.11. Joint Air to Surface Standoff Missile (JASSM-ER)

1.2.1.12. Joint Standoff Weapon (JSOW C-1)

1.2.1.13. Distributed Targeting System

1.2.1.14. Multifunctional Information Distribution System Joint Tactical Radio System (MIDS

JTRS)

1.2.1.15. Long Range Anti-ship Missile (LRASM)

1.2.1.16. USS GERALD R FORD (CVN 78)

1.2.1.17. Advanced Arresting Gear (AAG)

1.2.1.18. Joint Precision Approach and Landing System (JPALS)

1.2.1.19. Joint Mission Planning System - Maritime

1.2.1.20. E-2D Advanced Hawkeye

1.2.1.21. E-6B Block 1 Upgrades

1.2.1.22. T-6B Avionics Upgrade Project

1.2.1.23. T-45

1.2.1.24. CMV-22 Osprey

1.2.1.25. EA-18G System Configuration Set (SCS)

1.2.1.26. Next Generation Jammer (NGJ) Pod

1.2.1.27. EA-6B Improved Capability III (ICAP III)

1.2.1.28. AN/ALQ-99 Low Band Consolidation (LBC)

1.2.1.29. Intrepid Tiger Spiral II Pod

1.2.1.30. Advanced Threat Warning (ATW) Infra-red Countermeasures System

1.2.1.31. Integrated Defensive Electronic Countermeasures (IDECM)

1.2.1.32. AN/APR-39 Radar Signal Detecting Set

1.2.1.33. Radar Warning Receiver (AN/ALR-67(V) 1-2)

1.2.1.34. Common Infra-red Countermeasures (CIRCM)

1.2.1.35. Distributed Aperture Infra-red Countermeasures (DAIRCM)

1.2.1.36. Aircraft Electronic Suite Calendar Year software upgrade

1.2.1.37. AN/AAR-47 IR Warning Receiver

1.2.1.38. AN/ALE-47 IR Countermeasure System

1.2.1.39. MV-22 Osprey

1.2.1.40. CH-53K

1.2.1.41. H-1 Upgrades (AH-1Z/UH-1Y)

1.2.1.42. Presidential Support Aircraft (VH-92)

1.2.1.43. Joint Strike Fighter (JSF), F-35B/C

1.2.1.44. KC-130J

1.2.1.45. AV-8B

1.2.1.46. SDB-II (Small Diameter Bomb)

1.2.1.47. Joint Air to Ground Missile (JAGM)

1.2.1.48. Sustainment Lighting System (SLS)

1.2.2. Test Policy, Operations and Training (Code 01A) ensures OPTEVFOR policy conforms to

Navy T&E Policy; monitors production of T&E products; leads continuous process improvement efforts; coordinates external OT&E inquiries (IG and GAO); manages all government T&E training

(including budget requests); provides T&E editorial support to the command; and plans, analyzes and evaluates the effectiveness of command processes.

1.2.3. Test Design and M&S (Code 01B) is responsible for the Mission Basted Test Design (MBTD) process, M&S technical review, test planning and post-test iterative process analysis support, test design production, Capabilities Based Test and Evaluation coordination, and Targets, Ranges, and Test

Resources coordination.

1.2.4. Test Planning and Analysis Division (Code 01C is responsible for policy, processes and standardization for test planning, test execution, post-test analysis and evaluation (reporting). This includes Lead Test Engineer (LTE) support to the COTF Warfare Divisions and Fleet Resources coordination to support execution of OT&E.

1.2.5. Cybersecurity Division Code O1D OT&E integrates critical cybersecurity testing into the acquisition lifecycle and tests Systems under Test (SUT) per DoDI 5000.02 and DOT&E memo of 01

August 2014. The Warfare division will be responsible for executing acquisition test design, planning support to ultimately provide the Cybersecurity OT&E group (O1D) support in cybersecurity execution and reporting including VXs and VMX. Through a rigorous and iterative test process, Cybersecurity OT&E assists in the development and fielding of more secure and resilient Information

Technology (IT) systems supporting the warfighters. Code 01D Cybersecurity OT&E group includes the following support positions: Technical Director, Future Capabilities and Threat Emulation

Developer, Cybersecurity Test Engineers, Test Design and Analysis Manager, Training and Lab

Manager, Test Team Leads and Certified Ethical Hackers.

1.3. Period of Performance. From 12 Nov 2020 thru 11 Nov 2021 (Base Year), 12 Nov 2021 thru 11 Nov

2022 (Option Year 1), 12 Nov 2022 thru 11 Nov 2023 (Option Year 2), 12 Nov 2023 thru 11 Nov 2024

(Option Year 3), 12 Nov 2024 thru 11 Nov 2025 (Option Year 4), 12 Nov 2025 thru 11 May 2026 (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:

Commander, Operational Test and Evaluation Force

7970 Diven Street

Norfolk, VA 23505-1498

While onsite at COMOPTEVFOR, the contractor shall comply with OPNAVINST 5239 (series), with specific regard to non-government hardware and software.

1.4.1. Travel. Travel can be expected to occur CONUS and OCONUS and will be required throughout the course of this contract. All travel costs shall be in accordance with the Federal Travel Regulations

(FTR). 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 TA and approved by the 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 COMUSFLTFORCOM/COMPACFLTINST 6320.3B, dtd 07Apr14, 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 (DON) 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

(within 50 miles of place of performance).

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

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

1.4.1.1.3.3. Locations include CONUS, OCONUS and at sea locations and any other location, which may be added on a task order 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:

1.4.1.1.3.4.1. 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 task order basis based on future test requirements.

1.5. Personal Services. This is not a personal services Task Order. 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 that is 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 sub-contractor. Therefore, the Prime contractor is responsible for ensuring, through its own internal processes, that quality work is performed and delivered on time, by any subcontractors to meet the objectives of the prime contract. Formal direction to sub-contractors flows only thought 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. ADP Requirements: The Government will provide, if required, the necessary computer, work station/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 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 inventory of ADP assets may be directed to forfeit their

ADP GFP at no additional cost to the government. IAW FAR 52.245-1

1.8. Common Access Card (CAC)/Public Key Infrastructure (Pki), 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 Sep 2011) on file, and complete required Annual Information Awareness Training. New employees must submit their SAAR forms upon check in of their first day of work. Instructions for processing the SAAR-N forms are available at:

http://www.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf.

1.8.1. SAAR-N forms shall be submitted to the CIO Department, specifically the Information Systems

Security Manager (ISSM).

1.9. Common Access Cards (CAC) / Local Badges: Contractor CACs and facility specific identification badges will be approved using the Trusted Agent Sponsorship (TAS) 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 in accordance with the instructions/ guidance http://www.cnrc.navy.mil/publications/Forms/OPNAV_5239_14_SAAR_N.pdf required by your facility following completion of the contract, relocation or termination of an employee, or upon request from the Contracting Officer’s Representative.

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. Any contractor who will be needing a COTF issued security badge is required to conduct a “Check IN” beginning at our main admin department as well as submission of a Work Authorization Memo (WAM).

1.10. Other Direct Costs (ODCs). If Applicable, ODCs consist of test equipment and supplies as required for performance of Task Orders. In no instance shall the contractor exceed the amount specified in the contract for ODC CLIN expenses.

1.11. Contingency Labor Hours. When applicable, Contingency Labor Hours will be estimated for and ONLY used when:

1.11.1. An unplanned requirement is needed,

1.11.2. Is within scope (within para 2.1 thru 2.6) of the Contract but not included in the task order solicitation;

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

1.11.4. and after concurrence via email from the OTD and Command COR is received.

1.11.5. These hours are not to be considered overtime. For these situations, Contingency Labor Hours

(FAR 31.205-7) will be included in the form of hours exclusive of the standard Labor, Travel and

ODC’s.

1.12. Receipt and Acceptance of Deliverables All Deliverables (CDRL’s) (NIPR or SIPR) listed will be delivered by the Contractor in accordance with the Quality Assurance Surveillance Plan (QASP).

These delivered items shall be sent in an email by the contractor to the divisional representatives (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 has made 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 (formerly OTD Manual). This email will facilitate the formal government’s position for the respective product.

2. Specific Tasking. In accordance with the PWS and the basic contract the contractor shall provide support in evaluating the operational effectiveness and suitability of the system under test that has been assigned to

COMOPTEVFOR for OT&E, in accordance with the format prescribed in COTFINST 3980.2 series, Operational Test Director’s Guide (or other governing references listed in paragraph 5 as applicable). The manual maybe found at: http://www.public.navy.mil/cotf/OTD/OTD%20Manual.pdf

2.1. Test Design

2.1.1. Mission Analysis

2.1.1.1. The Contractor shall perform Mission Based Test Design mission analysis in accordance with references (IEF Checklist) and (IEF Template).

2.1.1.1.1. The contractor shall analyze source data to perform Mission Based Test Design mission analysis.

2.1.1.1.2. The contractor shall identify and document the mission areas.

2.1.1.1.3. The contractor shall identify and document system capabilities.

2.1.1.1.4. The contractor shall derive and document operator tasks.

2.1.1.1.5. The contractor shall define and document the operational conditions applicable to the system to be tested.

2.1.1.1.6. The contractor shall document the mission analysis in the Mission Based Test and Evaluation System (MBTES).

2.1.1.1.7. The contractor shall document the mission analysis in an Integrated Evaluation

Framework (IEF) document.

2.1.1.1.8. The contractor shall review the mission analysis during MBTD reviews.

http://www.public.navy.mil/cotf/OTD/OTD%20Manual.pdf

2.1.1.1.9. The contractor shall provide meeting minutes, to include any required comment resolution matrix for issues, to document the results of mission analysis MBTD reviews.

2.1.2. Requirements Analysis

2.1.2.1. The contractor shall perform Mission Based Test Design requirements analysis in accordance with references (IEF Checklist) and (IEF Template).

2.1.2.1.1. The contractor shall analyze source data to perform Mission Based Test Design requirements analysis.

2.1.2.1.2. The contractor shall identify and document measures of system performance, inclusive of critical measures.

2.1.2.1.3. The contractor shall link measures of system performance to subtasks and document this linkage.

2.1.2.1.4. The contractor shall identify and document the data required to quantify the measures of system performance.

2.1.2.1.5. The contractor shall identify and document the data required to quantify the operational conditions applicable to the system to be tested.

2.1.2.1.6. The contractor shall document requirements analysis in the Mission Based Test and Evaluation System (MBTES).

2.1.2.1.7. The contractor shall review the requirements analysis during MBTD reviews.

2.1.2.1.8. The contractor shall provide meeting minutes, to include any required comment resolution matrix for issues, to document the results of requirements analysis MBTD reviews.

2.1.3. Test Design

2.1.3.1. The Contractor shall perform Mission Based Test Design test design in accordance with references (IEF Checklist) and (IEF Template).

2.1.3.1.1. The contractor shall analyze source data to perform Mission Based Test Design test design.

2.1.3.1.2. The contractor shall identify and document the candidate response variables for statistical test design.

2.1.3.1.3. The contractor shall identify and document factors/conditions (with corresponding levels) associated with each response variable or critical measure used in test design.

2.1.3.1.4. The contractor shall participate in and document the statistical test design for candidate response variables and/or critical measures.

2.1.3.1.5. The contractor shall identify and document the test vignettes.

2.1.3.1.6. The contractor shall determine and document the appropriate test method.

2.1.3.1.7. The contractor shall determine and document a test schedule supporting execution of the test design.

2.1.3.1.8. The contractor shall identify and document the expected use of Modeling and

Simulation in the execution of the test design.

2.1.3.1.9. The contractor shall determine and document the resources required to conduct the test.

2.1.3.1.10. The contractor shall determine and document the limitations to test based on known availability of resources and assets to conduct the test.

2.1.3.1.11. The contractor shall develop and document data sheets to support test execution.

2.1.3.1.12. The contractor shall document the test design in the Mission Based Test and

Evaluation System (MBTES).

2.1.3.1.13. The contractor shall provide meeting minutes, to include any required comment resolution matrix for issues, to document the results of test design MBTD reviews.

2.1.4. Stakeholder Collaboration (WIPTs, outreach, etc)

2.1.4.1. The contractor shall make recommendations to the warfare division in accordance with

COMOPTEVFOR processes found in references (IEF Checklist) and (IEF Template).

2.1.4.2. The contractor shall identify and recommend outside organization(s) for participation and inclusion in Test Design activities.

2.1.4.3. When directed, the contractor shall coordinate briefings/meetings in support of

COMOPTEVOFR Test Design activities in accordance with references (IEF Checklist) and (IEF

Template).

2.1.4.4. When directed, the contractor shall participate in briefings/meetings in support of

COMOPTEVOFR Test Design activities in accordance with references (IEF Checklist) and (IEF

Template).

2.1.4.5. When directed, the contractor shall lead briefings/meetings in support of

COMOPTEVOFR Test Design activities in accordance with references (IEF Checklist) and (IEF

Template).

2.1.4.6. The contractor shall provide a trip report (CDRL A00Z) when the activities (1.1, 1.2, 1.3 or 1.4) occur away from the COMOPTEVFOR site in Norfolk, VA.

2.1.5. Document and brief preparation (CDRL A002)

2.1.5.1. The contractor shall prepare and document briefings (CDRL A00z) to include the

Integrated Evaluation Framework, Executive In-Process Review and stakeholder collaboration briefings, as directed.

2.1.5.2. The contractor shall prepare and document briefings (CDRL A00z) to include the Test

Plan, Data Collection Plan, Concept of Test, Test Plan Review Board and stakeholder collaboration briefings, as directed.

2.1.5.3. The contractor shall prepare and document briefings (CDRL A00z) to include the M&S

Requirements Letter, Accreditation Plan, Verification and Validation Report Addendum, Accreditation Letter and stakeholder collaboration briefings, as directed.

2.1.5.4. The contractor shall prepare and document briefings (CDRL A00z) to include the

Evaluation Report, Post-Test Brief, Scoring Board, CEWG Brief, SERB/E-SERB Brief, Data

Analysis Summary and Blue/Gold Sheets, as directed.

2.1.5.5. The contractor shall prepare the Risk/Deficiency cover letter, the DAS, and the Test report per references (OTD Man, Templates, and Best Practice Series).

2.1.6. Test and Evaluation Master Plan (TEMP) Input preparation

2.1.6.1. The contractor shall analyze source data to provide input to the TEMP, to include program schedules, the Integrated Evaluation Framework, applicable policy documents and any other program-provided materials

2.1.6.2. The contractor shall develop and document input to the TEMP IAW the DOT&E TEMP

Guidebook, reference (x).

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

OT.

2.1.7. Stakeholder Collaboration

2.1.7.1. The contractor shall make recommendations to the warfare division in accordance with

COMOPTEVFOR processes found in references (x) and (y).

2.1.7.2. When directed, the contractor shall coordinate briefings/meetings in support of

COMOPTEVOFR Temp Input activities in accordance with references (x) and (Y).

2.1.7.3. When directed, the contractor shall participate in briefings/meetings in support of

COMOPTEVOFR Temp Input activities in accordance with references (x) and (Y).

2.1.7.4. When directed, the contractor shall lead briefings/meetings in support of

COMOPTEVOFR Temp Input activities in accordance with references (x) and (Y).

2.1.7.5. The contractor shall provide a trip report (CDRL A00Z) when the activities occur away from the COMOPTEVFOR site in Norfolk, VA.

2.2. Test Planning

2.2.1. Plan of Action and Milestones (POA&M)

2.2.1.1. The contractor shall develop and document a POA&M for the Test Planning process in accordance with reference (test plan checklist).

2.2.1.2. The contractor shall analyze source data to perform Test Planning POA&M development.

2.2.1.3. The contractor shall obtain and maintain access to the program MBTES database.

2.2.2. Purpose of Test

2.2.2.1. The contractor shall perform the activities associated with development of Purpose of

Test in accordance with reference (test planning checklist).

2.2.2.1.1. The contractor shall analyze source data to perform Test Planning Purpose of

Test development.

2.2.2.1.2. The contractor shall update and document the System Under Test (SUT) and

System of Systems (SoS) descriptions from the Integrated Evaluation Framework for use in the Test Plan.

2.2.2.1.3. The contractor shall identify and document the SUT test configuration.

2.2.2.1.4. The contractor shall identify and document the Developmental Test

(DT)/Integrated Test (IT) contributions to OT.

2.2.2.1.5. The contractor shall identify and document regression test requirements for any

Follow-on OT&E phases, if applicable.

2.2.2.1.6. The contractor shall identify and document changes to the limitations to test.

2.2.2.1.7. The contractor shall update and document the Mission Critical Subsystem

Matrix (MCSM) from the Integrated Evaluation Framework.

2.2.2.1.8. The contractor shall identify and document Scoring Board Guidance.

2.2.2.1.9. The contractor shall document the Purpose of Test activities in a Test Plan document in accordance with reference (test planning checklist or template).

2.2.2.1.10. The contractor shall review the Purpose of Test activities during test plan reviews.

2.2.2.1.11. The contractor shall provide meeting minutes, to include any required comment resolution matrix for issues, to document the results of Purpose of Test plan reviews.

2.2.3. Test Schedule

2.2.3.1. The contractor shall perform the activities associated with development of the Test

Schedule in accordance with reference (test planning checklist).

2.2.3.1.1. The contractor shall analyze source data to perform Test Planning Test Schedule development.

2.2.3.1.2. The contractor shall identify, recommend and document data to be qualified for use in OT.

2.2.3.1.3. The contractor shall develop and document the Test Schedule, to include test events, for each test phase and period.

2.2.3.1.4. The contractor shall document the Test Schedule data in the Mission Based Test and Evaluation System (MBTES).

2.2.3.1.5. The contractor shall document the Test Schedule activities in a Test Plan document in accordance with reference (test planning checklist or template).

2.2.3.1.6. The contractor shall review the Test Schedule activities during test plan reviews.

2.2.3.1.7. The contractor shall provide meeting minutes, to include any required comment resolution matrix for issues, to document the results of Test Schedule test plan reviews.

2.2.4. Detailed Method of Test

2.2.4.1. The contractor shall perform the activities associated with development of the Detailed

Method of Test in accordance with reference (test planning checklist).

2.2.4.1.1. The contractor shall analyze source data to perform Test Planning Detailed

Method of Test development.

2.2.4.1.2. The contractor shall identify and document the data to be collected on each test event.

2.2.4.1.3. The contractor shall develop and document the start and stop criteria for each test event.

2.2.4.1.4. The contractor shall develop and document the GO/NO GO criteria for each test event.

2.2.4.1.5. The contractor shall develop and document the Detailed Method of Test for each test event.

2.2.4.1.6. The contractor shall document the Detailed Method of Test in a Test Plan document in accordance with reference (test planning checklist or template).

2.2.4.1.7. The contractor shall review the Detailed Method of Test during test plan reviews.

2.2.4.1.8. The contractor shall provide meeting minutes, to include any required comment resolution matrix for issues, to document the results of Detailed Method of Test plan reviews.

2.2.5. Data Collection Plan

2.2.5.1. The contractor shall perform the activities associated with development of the Data

Collection Plan in accordance with reference (test planning checklist).

2.2.5.1.1. The contractor shall analyze source data to perform Test Planning Data

Collection Plan development.

2.2.5.1.2.