N0018920R0031 0002.pdf

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 Amendment 0002 is to incorporate changes to the PWS and the 52.212-1 Addendum. This change w ill also revise the Questions and Answ er attachment. All other terms and conditions remain unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 33

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

16C. DATE SIGNED

BY 04-Jun-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 N0018920R0031

X 9B. DATED (SEE ITEM 11)

18-May-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 is extended, X 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

04-Jun-2020

CODE

NAVSUP FLC NORFOLK CONTRACTING

NORFOLK OFFICE

ATTN: T. WATSON

1968 GLIBERT STREET, 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:

N0018920R0031

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been modified:

52.212-1 ADDENDUM

Addendum to FAR provision 52.212-1, Instructions to Offerors

I. GENERAL

In addition to FAR provision 52.212-1, Instructions to Offerors – Commercial Items, and any other instructions contained elsewhere in this solicitation, the following instructions are provided.

Initial proposals and any modifications thereto are to be submitted to the contracting officer via email on or before the closing date and time cited in this solicitation. Hard copy, faxes and/or responses through Navy Electronic Commerce Online (NECO) or any method other than email format are not acceptable.

The proposal shall consist of the following separate volumes:

Volume 1:

Factor 1 – Facilities Security Clearance Factor 2 – Technical o Sub-factor 1: Command, Control, Communications, Computers, Intelligence and Space Warfare (C4IS) Approach o Sub-factor 2: Performance Approach o Sub-factor 3: Management Approach

Volume 2: Factor 3 – Past Performance Volume 3: Factor 4 – Price

Each page of each copy shall be affixed with the following legend:

Source Selection Information - See FAR 2.101 and 3.104

The completion and submission of the items outlined in this section will constitute an offer (proposal) and will indicate the offeror’s unconditional assent to the terms and conditions of this solicitation and any attachments and/or exhibits hereto. Alternate proposals are not authorized. Objections to any of the terms and conditions of the solicitation will constitute a deficiency (see FAR 15.001), which will make the offer unacceptable.

Offerors shall comply with the instructions for the format and content of the proposals contained herein; proposals that do not comply may be considered unacceptable and may be determined to be ineligible for award.

IMPORTANT NOTES:

(1) Offerors shall respond to all requirements of the solicitation. Offerors are cautioned not to alter the solicitation.

(2) In the event that any person who is not a bona fide employee of the offeror participated in the creation, formulation, or writing of any portion of the proposal, a certificate to this effect shall be included in the proposal which shall be signed by an officer of the offeror. Such certificate shall identify the name of the person who is not a bona fide employee, that person’s employment capacity, the name of the person’s firm, the relationship of that firm to the offeror, and the portion of the proposal in which the person participated.

(3) Offerors may submit questions regarding clarification of solicitation requirements via email to Tierra Watson at tierra.watson@navy.mil and Aaron Martin at aaron.b.martin2@navy.mil. It is requested that all questions be received by 12:00 PM EST 28 May 2020 as time may not permit responses to questions received after that date to be prepared and issued prior to the receipt of proposals.

(4) Proposals are to be submitted via email to Tierra Watson at tierra.watson@navy.mil and Aaron Martin at aaron.b.martin2@navy.mil in the volumes, format, and quantities as identified in this section. Proposals are due no later than the closing date and time identified on the front page of the solicitation.

II. REQUIREMENTS FOR PROPOSAL CONTENT

(1) Introduction and Purpose: This section specifies the format that offerors shall use in this request for proposals

(RFP). The intent is not to restrict offerors in the manner in which they will perform the work, but rather to ensure a certain degree of uniformity in the format of the responses for evaluation purposes.

(2) Each volume should contain the following items in addition to the other information required by this solicitation:

The cover should indicate the following:

o Title of the proposal o Volume number (1, 2, or 3) o Solicitation number o Name and address of offeror, point of contact information (name, phone number, and email address), CAGE code, DUNS number, and applicable tax identification number (TIN) o Identification if original or a copy of the proposal o Proposal validity until 16 November 2020

Table of Contents: The table of contents should provide sufficient detail as to allow the important elements to be easily located. The use of tabs and dividers is encouraged.

(3) Requirements for Style: Each offeror shall submit a proposal that clearly and concisely describes and defines the offeror’s response to the requirements contained in the solicitation. Unnecessary elaboration or other presentations beyond that sufficient to present a complete and effective proposal are not desired. Elaborate artwork, expensive paper or bindings, and expensive visual or other presentation aids are neither necessary nor desired. The proposal shall contain all the pertinent information in sufficient detail in the one area of the proposal where it contributes most critically to the discussion of the same information. When necessary, offerors shall refer to the initial discussion and identify its location within the submitted proposal.

(4) Proposal Page Limitations:

Title Page Limit*

Volume 1: Facilities Security Clearance No limit

Volume 1: Technical 30 pages

Volume 2: Past Performance 12 pages

Volume 3: Price No limit

Each volume is limited to the maximum number of pages as defined in the table above. All submission and attachments shall be in Microsoft Office Word, with the exception of Factor I: Facilities Clearance, which may be submitted as a PDF and the Price Proposal, which may include a Microsoft Excel submission. Submissions are page limited to the maximum number of pages as defined below. These page limitations are inclusive of the executive summary and any charts, diagrams, and/or other graphics. Graphics (including tables) in the proposal may use an alternative font with 8-point size type or larger. Each “page” is defined as one sheet, 8 ½" x 11", with at least one inch margins on all sides, using a font with a point size of 12 10 or greater (e.g., "Times New Roman" style with 12 10-point font). Lines shall, at a minimum, be single-spaced in Microsoft Word with Microsoft Word Normal character spacing. Pages shall be consecutively numbered. Multiple pages, double pages, two-sided pages, or foldouts will count as an equivalent number of 8 ½" x 11" pages. The offeror is permitted to submit no more than one page for each of the following, which will not be included in the page count: a cover sheet, list of tables, list of figures, compliance matrix, table of contents, tabs, and dividers. Pages submitted in excess of the page limitations described above will not be evaluated.

*Page limits represent the maximum pages the Government will evaluate and are not construed as de facto standards for the amount of material expected in the proposal.

III. PROPOSAL CONTENT:

Phase 1 – Factor 1 – Facilities Security Clearance: The offeror shall provide proof and verification that it possesses a current facilities clearance level that is commensurate with the requirements at time of proposal submission as identified in section 8.0 (Top Secret Sensitive Compartmented Information) of the PWS. The proof/verification shall be in the form of Defense Security Service (DSS) verification or a letter from the offeror’s corporate officer certifying it possesses a current Top Secret Sensitive Compartmented Information Facilities Clearance. The letter submission from its corporate officer shall include the following:

o CAGE code o Facility name o Physical location/facility o Clearance status/level o Status date/Issue date o Safeguarding level o Authorized access to o Facilities clearance level limitation(s) o Facility security officer and phone number o DSS field office location and phone number

The verification or letter shall be dated within a year of the solicitation’s closing date.

Phase 2

Factor 2 – Technical: This volume shall address the technical factor and sub-factors, and shall include all information required for proposal evaluation. This volume shall exclude any reference to the price aspects of the proposal.

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 following sub-factors:

Sub-factor 1 – Command, Control, Communications, Computers, Intelligence and Space Warfare (C4IS) Approach: The offeror shall provide a technical solution to plan, conduct, and report operational test and evaluation specifically for communication and electronic warfare programs, including, but not limited to, those programs listed in PWS paragraph 1.2.1. The offeror shall include its test strategy discussion for automation.

Execution of the current test strategies are critical to the C4IS Division. The offeror shall provide a technical solution addressing support of maintaining alignment with the current test strategy for DCGS-N, CANES, and other MTA/expedited software capability release strategies in support of operational test and evaluation.

The offeror shall describe any risks associated with the implementation of the offeror’s approach to meeting all requirements of this sub-factor; describe techniques and actions to mitigate such risks; and explain how the techniques and actions identified for risk mitigation have been successfully used by the offeror.

Sub-factor 2 – Performance Approach: The offeror shall provide a performance approach that will successfully accomplish the requirements of the solicitation, including the PWS. The offeror shall demonstrate an understanding of and capability to meet all the requirements of the PWS, specifically addressing its approach to the tasks outlined in PWS paragraph 2. Offerors are not limited to any specific performance approach as long as the approach taken meets PWS requirements.

The offeror shall describe any risks associated with the implementation of the offeror’s approach to meeting all requirements of this sub-factor; describe techniques and actions to mitigate such risks; and explain how the techniques and actions identified for risk mitigation have been successfully used by the offeror.

Sub-factor 3 – Management Approach: The offeror shall provide a management approach that demonstrates its ability to perform the requirements of the solicitation, including the PWS, through its management capabilities, expertise, and experience. The offeror shall provide a management plan that clearly details how this effort will be managed within the offeror’s corporate organizational structure, including the roles, responsibilities, authorities, and a brief synopsis of the professional qualification(s)/background(s) of those individuals to be dedicated to this contract effort. The management approach must address the offeror’s ability to provide the personnel with all qualifications described in PWS paragraph 6 and meet the security clearance requirements in PWS paragraph 8.

The offeror shall describe any risks associated with the implementation of the offeror’s approach to meeting all requirements of this sub-factor; describe techniques and actions to mitigate such risks; and explain how the techniques and actions identified for risk mitigation have been successfully used by the offeror

The Factor 2 technical section is limited to thirty pages.

Factor 3 – Past Performance: This section shall address the past performance factor and include all information required for proposal evaluation. This section shall exclude any reference to the price aspects of the proposal.

The offeror shall demonstrate recent and relevant past performance or affirmatively state that it possesses no recent and relevant past performance. Recent past performance is performance that has taken place within the past five years. Relevant past performance is performance under contracts or efforts within the stated period that is the same as or similar to, the scope and magnitude of the work described by this solicitation. In addition, performance data will only be assessed for those references demonstrating at least one year of completed performance prior to the closing date of this solicitation.

To demonstrate its past performance, the offeror shall identify up to three of its most relevant contracts or efforts within the past five years and provide any other information the offeror considers relevant to the requirements of the solicitation. Offerors should provide a detailed explanation demonstrating the relevance of the contracts or efforts to the requirements of the solicitation.

For purposes of this solicitation, a contract is defined as a single contract or a single task order placed under an indefinite-delivery, indefinite-quantity (IDIQ) contract, a Blanket Purchase Agreement (BPA), or a Federal Supply Schedule (FSS). As one of its references of past performance, the offeror may submit a combination of up to three task orders issued from a single IDIQ or FSS contract, or a BPA.

The references will be evaluated in the aggregate in order to allow offerors who may not have the entire scope and magnitude of the requirement under one individual contract or order to still be evaluated for quality if past performance with the full scope and magnitude of the requirement can be demonstrated within the allotted number of references as described above.

If proposed subcontractor past performance is provided as part of the three contracts or efforts, the percentage and type of work to be done by the subcontractor on the solicitation requirement must be stated. The offeror’s proposal shall detail clearly the aspects of the work in the solicitation that the subcontractor is proposed to perform. A reference that does not detail clearly the aspects of the work in the solicitation that the subcontractor is proposed to perform will not be evaluated.

If the prime offeror or intended subcontractor/partner submits a past performance example in which it served as a subcontractor, the prime/subcontractor/partner shall detail clearly the work that it performed and the magnitude

(dollar value) of that subcontracted work only. A reference that does not differentiate between the overall contract effort and the subcontractor effort will not be evaluated.

Subcontractor performance (either the offeror’s own subcontractor experience or proposed subcontractor’s experience) of major or critical aspects of this requirement will be considered as highly as prime contractor past performance information for the offeror.

If any of the referenced contracts were performed by an affiliate of the offeror, clearly explain the relationship between the offeror and the affiliate. Describe any resources shared by the offeror and its affiliate.

The offeror shall complete a “Past Performance Information Form” for each reference submitted. The form is an attachment to the solicitation. For additional information regarding a particular reference beyond that which will fit on the form, the offeror may continue onto another sheet of paper. The forms and any continuation sheet(s) for submitted references cannot exceed twelve pages.

In addition to the information requested above, offerors shall contact their past performance references and request that each reference complete the attached “Past Performance Report Form” and e-mail the completed survey form directly to email to Tierra Watson at tierra.watson@navy.mil and Aaron Martin at aaron.b.martin2@navy.mil by the

CLOSING DATE AND TIME OF THIS SOLICITATION.

The Government reserves the right to consider past performance report forms received after the due date of the solicitation, to contact references for verification or additional information, to contact references other than those provided by the offeror, and to obtain information from other data sources.

The past performance section is limited to twelve pages.

Factor 4 – Price Proposal: This volume shall include the completed solicitation documents and a complete and detailed price breakdown with all supporting documentation. The pricing information shall be completed in accordance with the following:

A complete and signed Standard Form 1449, “Solicitation/Contract/Order for Commercial Items” and executed copy of amendments, if applicable.

Unless completed in the System for Award Management, the offeror shall complete the representations and certifications contained in the solicitation. If the offeror has completed all of the representations and certifications required by this solicitation in the System for Award Management, then the offeror need not submit the hardcopy representations and certifications.

For the purpose of preparing a price proposal, the offeror shall assume that the period of performance consists of a five-year ordering period, as well as the potential usage of FAR clause 52.217-8, Option to Extend Services. Offerors shall use the periods established in the Schedule.

This volume shall also include a completed Services Price Worksheet (an attachment to this solicitation), submitted in accordance with the following instructions.

o Separate price information shall be submitted for each year of service, as well as a total summary for the five-year ordering period, as shown in the Services Price Worksheet. Also include pricing for the potential usage of FAR clause 52.217-8, Option to Extend Services. The price for the services shown in this spreadsheet shall include all fully burdened labor required to provide services. The firm-fixed price annual rates proposed in the pricing spreadsheet will be incorporated into the resultant contract.

Travel is anticipated. The Government has included a not-to-exceed travel amount for each performance period. Offerors shall propose the Government-provided not-to-exceed travel amounts in their price proposals and the Services Price Worksheet, plus any applicable burdens. Offerors shall apply 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. Only G&A and/or OH indirect costs are allowable if an offeror’s accounting system automatically applies them. No profit and/or fee are allowed.

If no G&A and/or OH are proposed, the Government will determine that the offeror does not intend to apply these costs to travel during performance.

The price section is not page-limited, but is strictly limited to the requested information and supporting documentation only. No price information shall be contained in any other part of the proposal.

(End of FAR provision 52.212-1 Addendum)

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT FOR ANALYTICAL OPERATIONAL TEST AND

EVALUATION SUPPORT SERVICES FOR COMMAND, CONTROL, COMMUNICATIONS,

COMPUTERS, INTELLIGENCE, AND SPACE WARFARE DIVISION (CODE 60)

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 Command, Control, Communications, Computers, Intelligence, and Space Warfare (C4IS) 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, Modeling and Simulation (M&S) 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 at COMOPTEVFOR that are supported by competency divisions. The warfare divisions include Undersea Warfare (40), Air Warfare (50), C4IS (60), Surface Warfare (70), Expeditionary Warfare/Littoral Combat Ship (80) Division. Each warfare division has a Navy Captain as the division Director with a senior civil servant as the Deputy or a senior civil servant as the division Director and a Navy Commander as the Deputy.

The warfare divisions 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 warfare divisions are 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 the C4IS Warfare division and competency divisions are listed below, as well as a current list of C4IS evaluation programs being performed. This list is current as of time of this solicitation, and additional programs may be assigned to COMOPTEVFOR for contractor support under this contract.

1.2.1. The C4IS Warfare Division (Code 60) Tests and evaluates all ashore and afloat Command, Control, Communications, Computers, Intelligence, Space, Business, and Enterprise Information systems such as radars, radio frequency transmitters/receivers, digital switching networks, identification friend or foe, tactical decision-making systems, intelligence systems, combat direction systems, tactical links, information warfare systems, cryptologic systems, space and satellite systems, and non-tactical automated information systems. The division's main effort is to assist, through early involvement, in the acquisition process conduct tests, and provide timely and accurate evaluations to characterize system performance and resulting capability. Current C4IS test and evaluation programs include, but are not limited to :

1.2.1.1. Command and Control Processor (C2P)

1.2.1.2. Electronic Procurement System (ePS)

1.2.1.3. LINK16

1.2.1.4. LINK Monitoring and Management Tool (LMMT)

1.2.1.5. Maritime Tactical Command and Control (MTC2)

1.2.1.6. NOBLE

1.2.1.6.1. Naval Aviation Maintenance System (NAMS)

1.2.3.6.2 Naval Operational Maintenance Environment (NOME)

1.2.3.6.3 Naval Operational Supply System (NOSS)

1.2.1.7. Surface Electronic Warfare Improvement Program (SEWIP)

1.2.3.7.1 SEWIP Block 2

1.2.3.7.2 SEWIP Block 3

1.2.1.8. Mobile User Objective System (MUOS)

1.2.1.9. Battle Force Tactical Network (BFTN)

1.2.1.10. Enhance Polar Satellite (EPS)

1.2.1.11. Global Broadcasting System (GBS)

1.2.1.12. Digital Modular Radio (DMR)

1.2.1.13. Navy Multiband Terminal (NMT)

1.2.1.14. Protected Tactical Enterprise Service (PTES)

1.2.1.15. Consolidated Afloat Network and Enterprise Services (CANES)

1.2.1.16. Distributed Common Ground System – Navy Increment 1 (DCGS-N Inc 1)

1.2.1.17. DCGS-N Increment 2 (DCGS-N Inc 2)

1.2.1.18. Department of Defense Health Management System Modernization (DHMSM)

1.2.1.19. Naval Maritime Maintenance Enterprise Solution—Technical Refresh (NMMES—TR)

1.2.1.20. Manpower, Personnel, Training, and Education (MPT&E)

1.2.1.21. Naval Integrated Tactical Environment System—Next Generation (NITES Next)

1.2.1.22. Counter Insider Threat Capability (CITC)

1.2.1.23. Computer Network Defense (CND)

1.2.1.24. Shark Cage

1.2.1.25. Navy Cyber Situational Awareness (NCSA)

1.2.1.26. Weather Satellite Follow-On Microwave (WSF-M)

1.2.1.27. United States Naval Observatory—Precise Time and Astronomy (USNO-PTA)

1.2.1.28. Global—Theatre Security Cooperation Management System (G-TSCMIS)

1.2.1.29. Enterprise Resource Planning (ERP)

1.2.1.30. Command and Control Air Operations Suite (C2AOS)

1.2.1.31. Identification Friend or Foe (IFF) Mode 5

1.2.1.32. Shipboard Air Traffic Control Radar (SATR) AN/SPN-50

1.2.1.33. Network Tactical Common Data Links (NTCDL)

1.2.1.34. Nuclear Command, Control, and Communications (NC3)

1.2.1.35. Advanced Off-board Electronic Warfare (AOEW)

1.2.1.36. Spectral

1.2.1.37. Joint Military Global Positioning System (GPS) User Equipment (MGUE)

1.2.1.38. Ship’s Signal Exploitation Equipment Modifications (SSEE Mods)

1.2.1.39. Tactical Cryptologic System (TCS)

1.2.1.40. Cryptologic Carry-On Program (CCOP)

1.2.1.41. Integrated Communications and Data System (ICADS)

1.2.1.42. Electronic Chart Display and Information System—Navy (ECDIS-N)

1.2.1.43. Navy—Electronic Chart Display and Information System (N-ECDIS)

1.2.1.44. GPS-Base Positioning, Navigation, and Timing Service (GPNTS)

1.2.1.45. Inertial Navigation System-Replacement (WSN-12)

1.2.1.46. Protected Tactical SATCOM (PTS)

1.2.1.47. Navy Personnel and Pay (NP2)

1.2.1.48. Joint Operational Medicine Information Systems (JOMIS)

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

Navy Test and Evaluation (T&E) Policy; monitors production of T&E products; leads continuous process improvement efforts; coordinates external OT&E inquiries Inspector General and Government Accountability Office; 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- Based 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 support to the COMOPTEVFOR 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 Department of Defense Instruction

5000.02 and Director, Operational Test and Evaluation (DOT&E) Memorandum 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. 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, Analysis Manager, Training and Lab Manager, Test Team Leads and Certified Ethical Hackers.

1.3. Period of Performance. 16 November 2020 through 15 May 2026, inclusive of the 52.217-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 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 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 Technical Assistant 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 Instruction 6320.3B, dated 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 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 Contract Line Item Number (CLIN) and Other Direct Cost (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 (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:

Sasebo, Japan, Naples Italy, Australia, Hawaii, Halifax, Nova Scotia, Nanoose, British Colombia, 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 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. Automated Data Processing (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 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 inventory of ADP assets may be directed to forfeit their ADP

GFP at no additional cost to the government. In Accordance With (IAW) FAR 52.245-1

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

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. 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. 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 required by your facility following completion of the contract, relocation or termination of an employee, or upon request from the Contracting Officer’s Representative. 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. ODCs, Increased Operational Requirements and Contingency Support.

1.10.1. If Applicable, ODCs consist of test equipment and supplies as required for performance of TO. In no instance shall the contractor exceed the amount specified in the contract for ODC CLIN expenses.

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

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

1.10.2.2. Is within scope (within para 2.1 thru 2.7.7) of the contract/task order and necessary to complete the work required in the task order;

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

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

1.10.2.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 Contractor Data Requirement List 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 Operational Test Director (OTD), Section Head, Warfare Division Deputy Director, (and other applicable recipients to include the COR.

Upon receipt, the OTD will send an email to the COR facilitating the formal government’s position for the respective product for timeliness and/or accuracy. The COR will forward a copy of this email to the prime of the TO and the email will become part of the COR folder for that respective TO.

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 SUT that has been assigned to COMOPTEVFOR for OT&E, in accordance with the format prescribed in reference (a), COMOPTEVFORINST 3980.2 series, OTD 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. Overall Task Guidance. To gain efficiencies and synergy in contract execution, the Government encourages the Contractor to consider:

2.1.1. Flexibility in production. COMOPTEVFOR 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 government makes a final decision.

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 T&E community’s ability to understand, analyze, communicate, and ultimately visualize T&E issues from a warfighter and technical perspective.

2.2. Test Design

2.2.1. Mission Analysis

2.2.1.1. The Contractor shall perform MBTD mission analysis IAW Integrated Evaluation Framework

(IEF) Checklist reference (b) and IEF Template reference (c).

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

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

2.2.1.1.3. The contractor shall identify and document system capabilities.

2.2.1.1.4. The contractor shall derive and document operator tasks.

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

2.2.1.1.6. The contractor shall document the mission analysis in the Mission Based Test and

Evaluation System (MBTES).

2.2.1.1.7. The contractor shall document the mission analysis in an IEF document.

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

2.2.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.2.2. Requirements Analysis

2.2.2.1. The contractor shall perform MBTD Design requirements analysis in accordance with references (b) and (c).

2.2.2.1.1. The contractor shall analyze source data to perform MBTD requirements analysis.

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

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

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

2.2.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.2.2.1.6. The contractor shall document requirements analysis in the MBTES.

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

2.2.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.2.3. Test Design

2.2.3.1. The Contractor shall perform MBTD test design in accordance with references (b) and (c).

2.2.3.1.1. The contractor shall analyze source data to perform MBTD.

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

2.2.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.2.3.1.4. The contractor shall participate in and document the statistical test design for candidate response variables and/or critical measures.

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

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

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

2.2.3.1.8. The contractor shall identify and document the expected use of M&S in the execution of the test design.

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

2.2.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.2.3.1.11. The contractor shall develop and document data sheets and test instrumentation (CDRL

A001) to support test execution.

2.2.3.1.12. The contractor shall document the test design in the MBTES.

2.2.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.2.4. Stakeholder Collaboration Working Integrated Product Team (WIPTs), outreach, etc

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

COMOPTEVFOR processes found in references (b) and (c).

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

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

COMOPTEVFOR Test Design activities in accordance with references (b) and (c).

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

COMOPTEVFOR Test Design activities in accordance with references (b) and (c).

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

Test Design activities in accordance with references (b) and (c).

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

2.2.5. Document and Brief Preparation

2.2.5.1. The contractor shall prepare and document briefings (CDRL A001) to include the IEF, Executive In-Process Review and stakeholder collaboration briefings, as directed.

2.2.6. Test and Evaluation Master Plan (TEMP) Input Preparation

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

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

Guidebook, reference (d).

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

OT&E.

2.2.7. Stakeholder Collaboration

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

COMOPTEVFOR processes found in references (a) and (b).

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

COMOPTEVFOR TEMP Input activities in accordance with references (a) and (b).

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

COMOPTEVFOR TEMP Input activities in accordance with references (a) and (b).

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

TEMP Input activities in accordance with references (a) and (b).

2.2.7.5. The contractor shall provide a trip report (CDRL A002) when the activities occur away from

2.3. Test Planning

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

2.3.1.1. The contractor shall develop and document a POA&M for the Test Planning process in accordance with reference (e).

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

2.3.1.3. The contractor shall obtain and maintain access to the program MBTES database to support the test planning process.

2.3.2. Purpose of Test

2.3.2.1. The contractor shall perform the activities associated with development of Purpose of Test in accordance with reference (e) test planning checklist.

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

2.3.2.1.2. The contractor shall update and document the SUT and SoS descriptions from the IEF for use in the Test Plan.

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

2.3.2.1.4. The contractor shall identify and document the Developmental Test /Integrated Test contributions to OT&E.

2.3.2.1.5. The contractor shall identify and document regression test requirements for any Follow-on OT&E phases, if applicable.

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

2.3.2.1.7. The contractor shall update and document the Mission Critical Subsystem Matrix

(MCSM) from the IEF.

2.3.2.1.8. The contractor shall document the Purpose of Test activities in a Test Plan document in accordance with reference (e) and the appropriate test plan templates.

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

2.3.2.1.10. The contractor shall identify test equipment/instrumentation needed for test execution.

2.3.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 reviews.

2.3.3. Test Schedule

2.3.3.1. The contractor shall perform the activities associated with development of the Test Schedule in accordance with reference (e).

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

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

OT&E.

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

2.3.3.1.4. The contractor shall document the Test Schedule data in the MBTES.

2.3.3.1.5. The contractor shall document the Test Schedule activities in a TP document in accordance with reference (e) and the appropriate TP templates.

2.3.3.1.6. The contractor shall review the Test Schedule activities during TP reviews.

2.3.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 TP reviews.

2.3.4. Detailed Method of Test (DMOT)

2.3.4.1. The contractor shall perform the activities associated with development of the DMOT in accordance with reference (e).

2.3.4.1.1. The contractor shall analyze source data to perform DMOT development.

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

2.3.4.1.3. The contractor shall develop and…