M6785422R2001-0011.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 this Amendment is to do the follow ing:

1. Update RFP Sections B, C, G, J, L, and M based on posted Q&As. See Q&As for specif ic changes.

2. Increase the Qty under CLINs X015 by 4.00 from 4.00 to 8.00.

3. Increase the Qty under CLINs X016 by 2.00 from 2.00 to 4.00.

4. Extend the proposal due date to 18 October 2022.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 67

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

16C. DATE SIGNED

BY 23-Sep-2022

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 M6785422R2001

X 9B. DATED (SEE ITEM 11)

10-Jun-2022

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

23-Sep-2022

CODE

COMMANDER MARCORSYSCOM

2200 LESTER STREET

QUANTICO VA 22134

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

M6785422R2001

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION B - SUPPLIES OR SERVICES AND PRICES

CLIN 0007

The CLIN extended description has changed from:

The Contractor shall prepare and submit an ECP IAW the instructions of MIL-STD-973, in effect on the date of contract award, SOW paragraph 4.8.5 and CDRL A014, Engineering Change Proposal. To be negotiated at the Task Order level. Ordering Period 1.

To:

The Contractor shall prepare and submit an ECP IAW the instructions of EIA-649, in effect on the date of proposal submission, SOW paragraph 4.8.5 and CDRL A014, Engineering Change Proposal. To be negotiated at the Task Order level. Ordering Period 1.

CLIN 0008

The contractor shall perform sustaining engineering of MCWS-L and MCWS-H assets IAW SOW paragraph 4.8.4.

Sustaining Engineering may be ordered upon review and negotiation of proposals submitted upon the Government's request. To be negotiated at the task order level. Ordering Period 1.

The contractor shall perform sustaining engineering of MCWS-L and MCWS-H assets IAW SOW paragraphs 4.8.4, 4.13.15, and 4.13.16. Sustaining Engineering may be ordered upon review and negotiation of proposals submitted upon the Government's request. To be negotiated at the task order level. Ordering Period 1.

CLIN 0010

The Contractor shall develop an MEO capability through an ECP IAW SOW paragraph 3.8.7 and the PSPECs, Attachments 6 and 7. Ordering Period 1.

The Contractor shall develop an MEO capability through an ECP IAW SOW paragraphs 4.8.7.1, 4.8.8 and the PSPECs, Attachments 6 and 7. Ordering Period 1.

CLIN 0015

The contractor shall perform teardown and evaluation of MCWS-L test assets IAW SOW paragraph 4.13.18.

Ordering Period 1.

The contractor shall perform teardown and evaluation of MCWS-L test assets IAW SOW paragraphs 4.4.1 and

4.13.19. Ordering Period 1.

The pricing detail quantity has increased by 4.00 from 4.00 to 8.00.

CLIN 0016

The contractor shall perform teardown and evaluation of MCWS-H test assets IAW SOW paragraph 4.13.18.

Ordering Period 1.

The contractor shall perform teardown and evaluation of MCWS-H test assets IAW SOW paragraphs 4.4.1 and

4.13.19. Ordering Period 1.

The pricing detail quantity has increased by 2.00 from 2.00 to 4.00.

CLIN 0017

The contractor shall refurbish MCWS-L and MCWS-H test assets IAW SOW paragraph 4.13.18.1. Refurbishment may be ordered upon review and negotiation of proposals submitted after tear down and evaluation IAW DFARS 252.217-7028, Over and Above Work, in a format prescribed by CDRL D013, Technical Report-Study/Services:

Repair Cost Estimate. To be negotiated at the task order level. Ordering Period 1.

The contractor shall refurbish MCWS-L and MCWS-H test assets IAW SOW paragraph 4.4.1 and 4.13.19.1.

Refurbishment may be ordered upon review and negotiation of proposals submitted after tear down and evaluation IAW DFARS 252.217-7028, Over and Above Work, in a format prescribed by CDRL D013, Technical Report- Study/Services: Repair Cost Estimate. To be negotiated at the task order level. Ordering Period 1.

CLIN 0018

CLIN 0019

CLIN 1007

The Contractor shall prepare and submit an ECP IAW the instructions of MIL-STD-973, in effect on the date of contract award, SOW paragraph 4.8.5 and CDRL A014, Engineering Change Proposal. To be negotiated at the Task Order level. Ordering Period 2.

The Contractor shall prepare and submit an ECP IAW the instructions of EIA-649, in effect on the date of contract award, SOW paragraph 4.8.5 and CDRL A014, Engineering Change Proposal. To be negotiated at the Task Order level. Ordering Period 2.

CLIN 1010

The Contractor shall develop an MEO capability through an ECP IAW SOW paragraph 3.8.7 and the PSPECs, Attachments 6 and 7. Ordering Period 2.

The Contractor shall develop an MEO capability through an ECP IAW SOW paragraphs 4.8.7.1 and 4.8.8 and the PSPECs, Attachments 6 and 7. Ordering Period 2.

CLIN 1015

The contractor shall perform teardown and evaluation of MCWS-L test assets IAW SOW paragraph 4.13.18.

Ordering Period 2.

The contractor shall perform teardown and evaluation of MCWS-L test assets IAW SOW paragraph 4.13.19.

Ordering Period 2.

CLIN 1016

The contractor shall perform teardown and evaluation of MCWS-H test assets IAW SOW paragraph 4.13.18.

Ordering Period 2.

The contractor shall perform teardown and evaluation of MCWS-H test assets IAW SOW paragraphs 4.4.1 and

4.13.19. Ordering Period 2.

CLIN 1017

The contractor shall refurbish MCWS-L and MCWS-H test assets IAW SOW paragraph 4.13.18.1. Refurbishment may be ordered upon review and negotiation of proposals submitted after tear down and evaluation IAW DFARS 252.217-7028, Over and Above Work, in a format prescribed by CDRL D013, Technical Report-Study/Services:

Repair Cost Estimate. To be negotiated at the task order level. Ordering Period 2.

The contractor shall refurbish MCWS-L and MCWS-H test assets IAW SOW paragraphs 4.4.1 and 4.13.19.1.

Refurbishment may be ordered upon review and negotiation of proposals submitted after tear down and evaluation IAW DFARS 252.217-7028, Over and Above Work, in a format prescribed by CDRL D013, Technical Report- Study/Services: Repair Cost Estimate. To be negotiated at the task order level. Ordering Period 2.

CLIN 2007

The Contractor shall prepare and submit an ECP IAW the instructions of MIL-STD-973, in effect on the date of contract award, SOW paragraph 4.8.5 and CDRL A014, Engineering Change Proposal. To be negotiated at the Task Order level. Ordering Period 3.

The Contractor shall prepare and submit an ECP IAW the instructions of EIA-649, in effect on the date of contract award, SOW paragraph 4.8.5 and CDRL A014, Engineering Change Proposal. To be negotiated at the Task Order level. Ordering Period 3.

CLIN 2010

The Contractor shall develop an MEO capability through an ECP IAW SOW paragraph 3.8.7 and the PSPECs, Attachments 6 and 7. Ordering Period 3.

The Contractor shall develop an MEO capability through an ECP IAW SOW paragraphs 4.8.7.1 and 4.8.8 and the PSPECs, Attachments 6 and 7. Ordering Period 3.

CLIN 3007

The Contractor shall prepare and submit an ECP IAW the instructions of MIL-STD-973, in effect on the date of contract award, SOW paragraph 4.8.5 and CDRL A014, Engineering Change Proposal. To be negotiated at the Task Order level. Ordering Period 4.

The Contractor shall prepare and submit an ECP IAW the instructions of EIA-649, in effect on the date of contract award, SOW paragraph 4.8.5 and CDRL A014, Engineering Change Proposal. To be negotiated at the Task Order level. Ordering Period 4.

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

STATEMENT OF WORK

STATEMENT OF WORK FOR THE

MARINE CORPS WIDEBAND SATELLITE LIGHT AND HEAVY SYSTEMS

1. Scope of Work This Statement of Work (SOW) sets forth the work required to deliver Marine Corps Wideband Satellite Communications (SATCOM) Light (MCWS-L) and Heavy (MCWS-H) Systems to the United States Marine Corps (USMC). The work includes two separate phases for the MCWS-L and MCWS-H Systems. The first phase is to procure MCWS-L and MCWS-H Test Systems to support a Developmental Test that will include testing and logistics efforts to support the Government’s production decision. The second phase will consist of the production, testing, and delivery of systems to support the USMC’s fielding requirements. The phases will include deliveries of the following, as ordered: technical data, logistics data, training data, training support, fielding support, and sustainment support as well as any technology upgrades or engineering changes needed to maintain the relevance of the MCWS-L and MCWS-H systems.

2. Background The USMC is replacing legacy SATCOM equipment with modernized products that provide a more flexible, modular, scalable, and maneuverable capability. The MCWS-L and MCWS-H Systems will enhance the Marine Air Ground Task Force expeditionary communications capabilities.

2.1 Definitions

The term “MCWS-L System” in this document references the Marine Corps Wideband

Satellite -Light variant The term “MCWS-H System” in this document references the Marine Corps

Wideband Satellite -Heavy variant.

The term “MCWS-L and MCWS-H systems” in this document references both the

Marine Corps Wideband Satellite - Light and Heavy variants.

3. Government Documents The documents listed in this section form a part of this SOW to the extent (i.e. Mandatory Compliance, Guidance Only, or otherwise) indicated, either in this section or as specifically noted elsewhere in this SOW. The version of the document that is listed here shall be used. In the event of conflict between the applicable documents and this SOW, this SOW takes precedence.

Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption applies.

3.1 Military Standards and Specifications – Mandatory Compliance MIL-PRF-32216 Eva valuation of Commerical off the Shelf (COTS)

Manuals and Preparation of Supplemental Data MIL-STD-882E System Safety EIA-649 National Consensus Standard for Configuration

Management MIL-STD-31000B Technical Data Packages MIL-STD-38784B General Style and Format Requirements for Technical

Manuals MCWS-L PSPEC Marine Corps Wideband SATCOM Light System, System

Performance Specification MCWS-H PSPEC Marine Corps Wideband SATCOM Heavy System, System

Performance Specification

3.2 Other Documents

CNSSI 1253 Security Categorization and Control Selection for National

Security Systems DoD 8570.01-M Information Assurance Improvement Program DoDI 8510.01 Risk Management Framework for DoD Information

Technology DoDM 5200.01 Vol 3 DoD Information Security Program, Protection of

Classified Information DoDI 5200.48 Controlled Unclassified Information (CUI) NIST SP 800-171 Protecting CUI in Nonfederal Systems and Organizations

WGS Certification Requirements Wideband Consolidated SATCOM System Expert (WB C- SSE) Terminal Performance Certification Requirements, V3.00, 17 June 2019

WGS Certification Test Procedures Wideband Consolidated SATCOM System Expert (WB C- SSE) Terminal Performance Certification Test Procedures, V3.00, 17 June 2019

WGS Certification Process Wideband Consolidated SATCOM System Expert (WB C- SSE) Terminal Performance Certification Process, V1.00, 12 June 2019

MRT TM Master Reference Terminal Technical Manual MCWS-X TM Marine Corps Wideband Satellite - Expeditionary

Technical Manual MIL-STD 464D Electromagnetic Environment Effects Requirements for

Systems DoDI 8551.01 Ports, Protocols, and Services Management (PPSM).

DoD Manual 5220.22 Vol 2 National Industrial Security Program: Industrial Security

Procedures for Government Activities DoD Directive 5220.22-M National Industrial Security Program MIL-STD-130 Identification Marking of United States Military Property MIL-STD-1472H Human Engineering NAVMC 1553.1A Marine Corps Instructional Systems Design/Systems

Approach to Training and Education Handbook MCO 5239.2B Marine Corps Cybersecurity DoD Directive 8140.01 Cyberspace Workforce Management

4. Requirements

4.1 General Requirements

4.1.1 Technical Data

Within this SOW, specific deliverables are referenced by name and reference number after the paragraph containing the requirement for that deliverable. Technical data and information shall be delivered in accordance with (IAW) this SOW, the applicable Contract Data Requirements List (CDRL) DD-1423 form, and the following instructions:

a. The contractor shall concurrently deliver technical data and information per DD- 1423, Blocks 12, 13, and 16 (date of first/subsequent submission/remarks) to all addressees listed in Block 14 of the DD-1423 (distribution and addressees) for each item.

b. Delivery of only part of the data is not acceptable unless specifically authorized by the DD-1423, or unless pre-approved in writing by the Procuring Contracting Officer (PCO).

c. The Government review period provided on the DD-1423 for each item commences upon receipt of all required data by the technical activity designated in Block 6 and 14.

d. The PCO reserves the right to issue unilateral modifications to change the destination codes and addresses for all technical data and information at no additional cost to the Government.

4.2 Program and Data Management

4.2.1 Post Award Conference

The contractor shall attend a Post Award Conference (PAC) within 30 calendar days after contract award at a location mutually agreed upon with the Government. The agenda at the meeting shall include: a complete review of contract documents, program schedule, risk areas and mitigation plans, production schedules, and provisioning and technical requirements. The contractor shall prepare and deliver a conference agenda, presentation material, and conference minutes associated with this event.

(CDRL B001, Conference Agenda) (CDRL B002, Presentation Material) (CDRL B003, Conference Minutes)

4.2.2 Meetings, Events, and Reviews

The contractor shall attend scheduled meetings and programmatic, logistics, training, and test and evaluation events as well as engineering reviews at the contractor’s facilities or other agreed upon location. Contractor personnel who are Subject Matter Experts (SMEs) and are familiar with the issues to be discussed shall also attend those same meetings, events and reviews. The contractor shall have at least one representative present who has the authority to address and resolve issues. The contractor shall prepare and deliver agendas, presentation material, and minutes, when directed. Meetings will either be in person or virtually, upon the Government’s request.

(CDRL B001, Conference Agenda) (CDRL B002, Presentation Material) (CDRL B003, Conference Minutes)

4.3 Reports

4.3.1 Status Reports

The contractor shall deliver monthly status reports documenting the contractor’s progress towards completing contract tasks. The status report shall identify accomplishments completed to date, difficulties encountered, and compare the status achieved to planned goals. In addition to the elements defined in the CDRL, the status report shall include a report on all warranty actions completed.

(CDRL B004, Status Report)

4.3.2 Program Schedule

The contractor shall deliver a program schedule that documents all significant events, milestones, system deliveries, and CDRL deliveries from contract award to completion of the final Period of Performance (PoP). The contractor shall notify the Government, in writing, by a letter to the PCO and the Contracting Officer Representative (COR), of any anticipated or projected work stoppages or delays that may impact scheduled deliveries by five or more business days.

(CDRL B005, Key Events Schedule, Integrated Master Schedule)

4.3.3 Data Accession List

The contractor shall deliver separate Data Accession Lists identifying all data created as a result of the work performed in support of this contract, one for the MCWS-L and the other for the MCWS-H variant. The contractor shall deliver any data created under this contract to the Government on the date specified in the relevant CDRL or otherwise upon request. This will result in a total of two separate CDRL deliverables: one deliverable for the MCWS-L Data Accession List and one deliverable for MCWS-H Data Accession List.

(CDRL A001, Data Accession List)

4.4 MCWS-L and MCWS-H Systems and Requirements

The MCWS-L and MCWS-H systems shall include the hardware, firmware, software, software licenses, cables, transit cases, operator and maintenance manuals, components, and everything else necessary to operate the systems to achieve the requirements defined in the respective MCWS-L and MCWS-H PSPECs, or additional capability that was included in the winning proposal and incorporated by the Government into the final contract.

4.4.1 System Government Test Assets

The contractor shall manufacture and deliver the MCWS-L and MCWS-H systems in accordance with the MCWS-L and MCWS-H PSPECs. The contractor shall deliver the MCWS-L and MCWS-H systems for initial use as assets for Government testing. After completion of the Government testing phase, the contractor shall refurbish these test assets and redeliver them, in the system’s final production asset configuration, by the end of the testing phase.

4.4.1.1 System Government Spares

The contractor shall manufacture and deliver spares, to include consumables, sufficient to support assets.

4.4.2 System Production Assets

The contractor shall deliver MCWS-L and MCWS-H systems in accordance with the PSPECs (Attachment 6 and Attachment 7) and those technical aspects of the contractor’s proposal that surpass the threshold and objective requirements of the PSPECs.

4.5 Systems Engineering

The contractor shall document, integrate, manufacture, and test the MCWS-L and MCWS-H systems to meet the MCWS-L and MCWS-H PSPECs, and any proposed capability incorporated into the successful offeror’s contract, as delineated in the paragraphs below.

4.5.1 Systems Engineering Technical Reviews

4.5.1.1 Non-Developmental Item Integration Review

The contractor shall participate in the preparation and execution of the Government held Non- Developmental Item Integration Review (NIR). The contractor shall deliver technical data packages for both the MCWS-L and the MCWS-H variants separately to support the NIR events.

The Government shall provide the contractor with a copy of the NIR Technical Review Action Plans (TRAPs) and the Government Requirements Traceability Matrixes (RTMs). The contractor shall deliver the technical data packages at least 30 days prior to the date the Government sets for the NIR; which is tentatively scheduled for 6 months after contract award. The Government will host separate NIRs for the MCWS-L and MCWS-H Systems. Each NIR will verify the proposed design meets the requirements, validate the initial Product Baseline (iPBL), and disclose the test and evaluation strategies to the contractor. The iPBL will identify all common components between the MCWS-L and MCWS-H. The work under this subsection will result in a total of four CDRL deliverables: one CDRL deliverable for MCWS-L Technical Data Package, one

CDRL deliverable for the MCWS-H Technical Data Package, one CDRL deliverable for the MCWS-L Technical Report, and one CDRL deliverable for the MCWS-H Technical Report.

(CDRL A002, Technical Data Package) (CDRL A003, Technical Report – Study/Service, Initial Product Baseline)

4.5.1.2 Test Readiness Review

The Government will conduct separate MCWS-L and MCWS-H Test Readiness Reviews (TRRs) to determine whether the MCWS-L and MCWS-H systems can proceed to Government demonstration and testing. The contractor shall deliver the Wideband Global SATCOM (WGS) certifications (CDRL A007, Spectrum Certification Spectral Characteristics Data) to support the Government requesting access to WGS satellites 90 days prior to the TRRs. The contractor shall participate in the preparation and execution of the Government TRRs as described below and further delineated in the TRR TRAPs.

The Government will provide a copy of the TRR TRAPs to the contractor to assist them in understanding what is required in the iPBL. The contractor shall update and deliver the iPBL.

The contractor shall provide program management and engineering representation during the TRRs via teleconference. This will result in a total of six CDRL deliverables: one CDRL deliverable for the MCWS-L Conference Minutes, one CDRL deliverable for the MCWS-L Technical Data Package, one CDRL Deliverable for the MCWS-L Technical Report, one CDRL deliverable for the MCWS-H Conference Minutes, one CDRL deliverable for the MCWS-H Technical Data Package, and one CDRL Deliverable for the MCWS-H Technical Report.

(CDRL B003, Conference Minutes) (CDRL A002, Technical Data Package) (CDRL A003, Technical Report – Study/Service, initial Product Baseline)

4.5.1.3 Functional Configuration Audit

The contractor shall participate in the preparation and execution of the Government Functional Configuration Audits (FCAs) for both the MCWS-L and MCWS-H. In preparation for the FCAs, the contractor shall deliver artifacts authoritatively demonstrating the delivered MCWS-L and MCWS-H meet the requirements. The Government will provide a copy of the FCA TRAPs and the Government RTMs to the contractor.

(CDRL A002, Technical Data Package)

4.5.1.4 Physical Configuration Audit

The contractor shall host, at the vendor location, Physical Configuration Audits (PCAs) for each variant. At the PCA, the contractor shall verify that the as-built production representative configuration of the MCWS-L and MCWS-H systems are consistent with the product baselines as defined by the MCWS-L and MCWS-H Software Version Descriptions (SVDs), the Final Product Baselines (fPBL) for the MCWS-L and MCWS-H, and the MCWS-L and MCWS-H Systems/Subsystem Design Descriptions (SSDDs). The PCAs shall validate the SVDs, fPBLs, and SSDDs. With the Government chairing the audit, the Government and contractor shall conduct the PCAs jointly, 30 calendar days prior to the contractor conducting a Production Acceptance Test (PAT), and no later than 60 calendar days prior to end of Ordering Period 1. It is intended that the Government will attend in person, rather than via webcam. This will result in a total of six CDRL deliverables: one CDRL deliverable for MCWS-L Systems/Subsystem Design Description, one CDRL deliverable for the MCWS-L Software Version Descriptions, one

CDRL deliverable for the MCWS-L Technical Report, one CDRL deliverable for the MCWS-H Systems/Subsystem Design Description, one CDRL deliverable for the MCWS-H Software Version Descriptions, and one CDRL deliverable for the MCWS-H Technical Report.

(CDRL A004, Systems/Subsystem Design Descriptions) (CDRL A005, Software Version Descriptions) (CDRL A006, Technical Report – Study/Service, Final Product Baseline)

4.5.2 WGS Certification

The contractor shall support the MCWS-L and MCWS-H system certification process for X- Band and Ka-Band operation on the WGS system in accordance with the WB C-SSE Terminal Performance Certification Process. The contractor shall deliver data, conduct tests, deliver test reports, and deliver support to Government testing as required by the WB C-SSE Terminal Performance Certification Process, V1.00, 12 Jun 2019, for phases 0, 1, 2, and 3 of the certification processes. The support requires delivery of CDRLs A007, A008, and A009.

4.5.2.1 Phase 0 WGS Terminal Certification Data

The contractor shall deliver X-Band and Ka-Band WGS Terminal Certification Tracking Forms in support of Phase 0 certification efforts for the MCWS-L, MCWS-H Primary (Pri) antenna, and MCWS-H Secondary (Sec) antenna variants separately. This will result in a total of six CDRL deliverables for WGS Phase 0 testing: one CDRL deliverable for MCWS-L X-Band, one CDRL deliverable for MCWS-L Ka-Band, one CDRL deliverable for MCWS-H (Pri) X-Band, one CDRL deliverable for MCWS-H (Pri) Ka-Band, one CDRL deliverable for MCWS-H (Sec) X- Band, and one CDRL deliverable for MCWS-H (Sec) Ka-Band.

(CDRL A007, Spectrum Certification Spectral Characteristics Data, WGS Phase 0 Terminal Certification Tracking Form Data)

4.5.2.2 Phase 1 WGS Terminal Certification Data

The contractor shall deliver WGS X-Band and Ka-Band Terminal Certification Tracking Forms in support of Phase 1 certification efforts for the MCWS-L, MCWS-H (Pri), and MCWS-H (Sec) variants. This will result in a total of six CDRL deliverables for WGS Phase 1 testing. One CDRL deliverable for MCWS-L X-Band, one CDRL deliverable for MCWS-L Ka-Band, one CDRL deliverable for MCWS-H (Pri) X-Band, one CDRL deliverable for MCWS-H (Pri) Ka- Band, one CDRL deliverable for MCWS-H (Sec) X-Band, one CDRL deliverable for MCWS-H (Sec) Ka-Band.

(CDRL A008, Spectrum Certification Spectral Characteristics Data, WGS Phase 1 Terminal Certification Tracking Form)

4.5.2.3 Phase 2 WGS Terminal Certification Data

The contractor shall deliver WGS X-Band and Ka-Band Terminal Certification Tracking Forms in support of Phase 2 certification efforts for the MCWS-L, MCWS-H (Pri), and MCWS-H (Sec) variants. This will result in a total of six CDRL deliverables for WGS Phase 2 testing. One CDRL deliverable for MCWS-L X-Band, one CDRL deliverable for MCWS-L Ka-Band, one CDRL deliverable for MCWS-H (Pri) X-Band, one CDRL deliverable for MCWS-H (Pri) Ka- Band, one CDRL deliverable for MCWS-H (Sec) X-Band, one CDRL deliverable for MCWS-H (Sec) Ka-Band.

(CDRL A009, Spectrum Certification Spectral Characteristics Data, WGS Phase 2 Terminal Certification Tracking Form Data)

4.5.2.4 Phase 3 WGS Terminal Certification Test Support

The contractor shall deliver on-site support at the Aberdeen Proving Ground, Maryland facility if Phase 3 (Government) testing is required by the WB C-SSE. Travel will be reimbursable per SOW paragraph 4.15.

4.6 Product Technical Data Package

The contractor shall deliver MCWS-L and MCWS-H SSDDs separately. Contractor recommended changes shall be approved by the Government prior to making the SSDD update.

The contractor shall deliver updated MCWS-L and MCWS-H SVDs separately. Contractor recommended changes shall be approved by the Government prior to making the SVD update.

This will result in a total of four CDRL deliverables. One CDRL deliverable for MCWS-L Systems/Subsystem Design Description, one CDRL deliverable for MCWS-L Software Version Descriptions, one CDRL deliverable for MCWS-H Systems/Subsystem Design Description, one CDRL deliverable for MCWS-H Software Version Descriptions.

(CDRL A004, Systems/Subsystem Design Descriptions) (CDRL A005, Software Version Descriptions)

4.7 Spectrum Certification

The contractor shall deliver the data necessary for the Application for Equipment Frequency Allocations (Form DD-1494), per the National Telecommunications and Information Administration Manual of Regulations and Procedures for Federal Radio Frequency Management for both MCWS-L and MCWS-H systems separately. This data will be in the form of Equipment Location-Certification Information Database software data files for both MCWS-L and MCWS-H terminal designs separately. This will result in a total of two CDRL deliverables.

One CDRL deliverable for MCWS-L Technical Report and one CDRL deliverable for MCWS-H Technical Report.

(CDRL A010, Technical Report – Study/Services, Equipment Location-Certification Information Database Data File)

4.8 Program Security

All classified material shall be handled, stored, and destroyed in accordance with the National Industrial Security Program Operating Manual (NISPOM) and 32 CFR Part 117. Any classified material that needs to be sent to Marine Corps Systems Command (MCSC) shall be sent through the Classified Material Control Center (CMCC) and packaged in accordance with the NISPOM and DoDM 5200.01 v3. The CMCC address for mailing classified material is:

Outer Envelope:

COMMANDER MCSC

ATTN CMCC

2200 LESTER STREET

QUANTICO VA 22134-5050

OFFICIAL BUSINESS

Inner Envelope:

COMMANDER MCSC

ATTN PMM 162.3

2200 LESTER STREET

QUANTICO VA 22134-5050

4.8.1 Contractor’s System Security

The contractor shall protect Government CUI and Controlled Technical Information (CTI) housed on the contractor’s systems. The contractor shall fully implement the CUI/CTI Security Requirements (Rev. 1), National Institute of Standards and Technology Special Publication (SP) 800-171, for all covered contractor information systems affecting this contract.

4.8.2 Security IPT and Documentation

The contractor shall participate in a multi-disciplinary IPT addressing the MCWS-L and MCWS- H system security. The contractor shall provide a system Security SME familiar with the identification of critical technologies and Critical Program Information, as well as security considerations thereof, to serve as member of a multi-disciplinary IPT. The Government estimates there will be at least two IPT meetings, which will be held in Quantico, Virginia or virtually, if the Government determines that is necessary.

The contractor shall deliver documentation to support the Government Program Protection Plan (PPP) development processes for the MCWS-L and MCWS-H systems. This includes a system decomposition for both the MCWS-L and MCWS-H systems that provides a breakdown of the system to the component level, identifying manufacturer, part numbers, and country of origin for each component. A SME supporting the Security IPT should be prepared to discuss any sensitivities, International Traffic in Arms Regulations restrictions, or system criticalities associated with individual components as they relate to the MCWS-L and MCWS-H systems.

(CDRL A011, Technical Report-Study/Services, PPP Documentation)

4.8.3 Technology Protection

The contractor shall develop, deliver, and implement Program Protection Implementation Plans (PPIP) that are consistent with, and complementary of, the Government PPPs for both the MCWS-L and the MCWS-H variants separately resulting in a total of two CDRL deliverables.

The PPIPs shall identify the protections that the contractor has in place to protect any classified or CUI/CTI information, critical components or technologies, Supply Chain Risk Management concerns, counterfeit prevention, investigations and reports of incidents or compromises.

(CDRL A012, PPIP)

4.8.4 Sustaining Engineering

The contractor shall perform sustaining engineering to support Government engineering and logistics requirements throughout performance of the contract. This support includes performing engineering and logistics investigations and analyses to ensure continued operation and maintenance of the MCWS-L and MCWS-H System. Specific requirements will be negotiated and incorporated into the contract by modification and task order, as applicable, after contract award. This will result in a total of two CDRL deliverables for sustaining engineering. One CDRL deliverable for MCWS-L investigation and analysis report and one CDRL deliverable for MCWS-H investigation and analysis report.

(CDRL A013, Technical Report-Study/Services, Investigation and Analysis Report)

4.8.5 Engineering Change Proposal

The contractor shall deliver Engineering Change Proposals (ECPs) to the Government for review and approval for changes to the final Product Baseline after the PCA. The contractor shall include an update to the program schedule in conjunction with each ECP, incorporating the tasks required to implement the ECP. The contractor may request an engineering change by submitting a proposal for possible negotiation, if the Government deems the change desirable.

The Contracting Officer may ask the contractor to prepare ECPs for engineering changes within the scope of this contract. Upon receipt of a written request from the Contracting Officer, the contractor shall prepare and submit an ECP in accordance with the instructions of EIA-649 in effect on the date of proposal submission.

This will result in a total of two CDRL deliverables per ECP. One CDRL, A014, for the actual ECP and one CDRL deliverable for the IMS applicable to the system being changed by the ECP.

(CDRL A014 Engineering Change Proposal) (CDRL B005, Key Events Schedule—Integrated Master Schedule)

4.8.6 Implementation of Engineering Changes

The contractor shall implement approved ECPs. Implementation includes any manufacturing, software patch disk, integration, and documentation updates required IAW the approved ECP. If the ECP is approved while Systems are in production, the Contactor shall incorporate the required changes into the Systems prior to delivery. In the case of a required retrofit to delivered Systems, the contractor shall deliver modification kits that include all modified components of the MCWS-L and MCWS-H System. If retrofit is required, the contractor shall also deliver a Modification Instruction documenting the installation of the modification kit. Implementation also includes delivery of any updated System documentation, software, technical data, logistics data, manuals (or change pages) defined within this SOW. This will result in a total of four CDRL deliverables. One CDRL deliverable for MCWS-L Software Patch Disk and one CDRL deliverable for MCWS-H Software Patch Disk. One CDRL deliverable for MCWS-L Publications, Technical, Instruction-Type, Preparation of, Modification Instruction and one CDRL deliverable for MCWS-H Publications, Technical, Instruction-Type, Preparation of, Modification Instruction.

(CDRL A015, Software Patch Disk) (CDRL A016, Publications, Technical, Instruction-Type, Preparation of, Modification Instruction)

4.8.7 Future Capabilities

New threshold or objective requirements may be incorporated in the MCWS-L and MCWS-H PSPECs through subsequent modifications, and may become contract requirements, enacted on future task orders, to add the capability on both existing and newly-ordered MCWS-L and MCWS-H systems. These new requirements may be based upon changes in relevant Government policy or directives, changes in operational needs or conditions, or evolutions in the state of the art underlying the requirement. Task orders may require work to incorporate the added capability within existing MCWS-L and MCWS-H inventory and to ensure its operational relevance and interoperability with new MCWS-L and MCWS-H systems. If threshold requirements are added to the MCWS-L or MCWS-H PSPEC during the contract, the SOW will be updated and CLINs added to incorporate this work. Such future modifications or additional requirements are envisioned as prolonging the operational relevance of the MCWS-L and MCWS-H systems and are deemed to be part of the scope of the contract.

4.8.7.1 Future Medium Earth Orbit (MEO) Capabilities

MEO communication capabilities are currently in development by both DoD and industry;

therefore, the Government’s update of the MCWS-L and MCWS-H PSPECs with technical specifications for an MEO communication capability, as a threshold requirement is imminent.

The following MEO specifications are currently listed as objective requirements, but will become threshold requirements when the MEO capability becomes available: MCWS-L PSPEC are 3.1.3, 3.1.12.6, and 3.1.12.7; MCWS-H PSPEC 3.1.3, 3.1.14.6, 3.1.14.7. At that time, the contractor shall add the capability on both previously-delivered and newly-ordered MCWS-L and MCWS-H systems.

4.8.8 MEO Capability Roadmap

The contractor shall deliver a MEO capability roadmap that illustrates the contractor’s plan to meet the MEO capability requirements in the proposed MCWS-L and MCWS-H systems. The MEO capability roadmap shall address the software communications architecture and technical performance MEO requirements delineated in the MCWS-L and MCWS-H PSPEC. This deliverable shall define the plan for the development of MEO ECPs in accordance with paragraphs 4.8.5 and 4.8.6 of this SOW. The MEO capability roadmap shall depict the development steps required to meet the MEO requirements listed in paragraph 4.8.7.1, including software and hardware configuration, in accordance with the contractor’s configuration management practice and this SOW. The MEO capability roadmap shall also identify any risks to cost, schedule, and performance. When the Government provides notification and technical specification of a Government approved pending MEO capability, the contractor shall deliver a MEO capability roadmap update.

CDRL A039 Technical Report/Study-MEO Capability Roadmap

4.8.9 Supply Chain Risk Management

The contractor shall establish a Supply Chain Risk Management process to track critical components to the original equipment manufacturers, parts suppliers, and vendor’s Bill of Materials (BOM) and to the hardware and software configuration items or Lowest Replaceable Unit (LRU) level of indenture. The scope includes Commercial off the Shelf (COTS), Government-off-the-Shelf, and open-source software components (to include systems, subsystems, components, and parts inherited from previous system developments) and modified or newly developed components; and critical components used in manufacturing and in the lifecycle enabling processes, such as: training (e.g., training equipment), maintenance (e.g., test equipment), and logistics support (e.g., LRUs). The contractor shall perform a supply chain risk assessment within 30 days of contract award, and upon any Configuration Management (CM)changes or Engineering Change Proposals (ECPs), and incorporate any supply chain vulnerabilities or risks within the PPIP.

The contractor shall maintain visibility into its supply chain for critical components, anticipate potential risks to that supply chain, and prepare supply chain risk mitigation plans to counter those risks. Potential suppliers of critical components shall be sought to gather cost, schedule, reliability and capacity, and trustworthiness (allegiance/affiliation) information relevant for critical component design and configuration selection among alternate suppliers, to establish a risk reduction strategy for the system supply chain. The contractor shall conduct a critical component make-or-buy analysis if the contractor or Government determines substantial risks are inherent to system operational viability due to limited trusted sources (vendors/suppliers) within the industrial complex. The contractor shall perform a supply chain risk assessment determination for each “high-risk” and “residual risk” critical component and include results within the PPIP traceable to the component and critical function it supports. The contractor shall identify any Foreign Ownership, Control, or Influence (FOCI) that may impact this contract or its subcontracts and identify how they intend to protect and segregate US Government information and technology from any FOCI relationships or concerns. This will result in a total of two CDRL deliverables. One CDRL deliverable for MCWS-L Supply Chain Risk Management and one CDRL deliverable for MCWS-H Supply Chain Risk Management.

(CDRL D001, Supply Chain Risk Management Plan)

4.8.10 Cybersecurity

4.8.10.1 Lifecycle Management

Marine Corps Order 5239.2B establishes an information systems lifecycle management approach to protect critical Marine Corps information. The contractor shall execute to the requirements within this Order.

4.8.10.2 Assessment and Authorization

The MCWS-L and MCWS-H Program will attain and maintain an Authority To Operate (ATO) as required by DoDI 8510.01 Risk Management Framework (RMF) for DoD Information Technology (DoD IT). The contractor shall have knowledge of, support, and perform activities necessary for system Assessment and Authorization (A&A), as directed by the RMF for DoD IT and Marine Corps Enterprise Cybersecurity Manual 018. The current A&A strategy includes attaining an Interim Authority To Test (IATT) and ATO. The System Security Categorization for both MCWS-L and MCWS-H is (Confidentiality {Moderate}), (Integrity {Moderate}), and (Availability {Moderate}). The MCWS-L and MCWS-H will each have separate IATT and ATO authorizations.

4.8.10.3 Cybersecurity Certifications

The contractor shall ensure personnel supporting the MCWS-L and MCWS-H A&A process have appropriate cybersecurity certifications in accordance with Department of Defense Directive 8140.01 and DoD 8570.01-M.

4.8.10.4 System Security Plan

Within 30 days of contract award, the contractor shall make its System Security Plan(s) (SSP(s)) for its covered contractor information system(s) available for review by the Government at the contractor’s facility. The SSP(s) shall implement the security requirements in Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012, which is included in this contract. The contractor shall fully cooperate in the Government’s review of the SSPs at the contractor’s facility.

If the Government determines that the SSP(s) does not adequately implement the requirements of DFARS clause 252.204-7012 then the Government shall notify the contractor of each identified deficiency. The contractor shall correct any identified deficiencies within 30 days of notification by the Government. The contracting officer may provide for a correction period longer than 30 days and, in such a case, may require the contractor to submit a plan of action and milestones (POA&M) for the correction of the identified deficiencies. The contractor shall immediately notify the contracting officer of any failure or anticipated failure to meet a milestone in such a

POA&M.

Upon the conclusion of the correction period, the Government may conduct a follow-on review of the SSP(s) at the contractor’s facilities. The Government may continue to conduct follow-on reviews until the Government determines that the contractor has corrected all identified deficiencies in the SSP(s).

The Government may, in its sole discretion, conduct subsequent reviews at the contractor’s site to verify the information in the SSP(s). The Government will conduct such reviews at least every 3 years (measured from the date of contract award) and may conduct such reviews at any time upon 30 days’ notice to the contractor.

4.8.10.5 Compliance to NIST 800-171

a. The contractor shall fully implement the CUI Security Requirements (Requirements) and associated Relevant Security Controls (Controls) in NIST Special Publication 800-171 (Rev. 1) (NIST SP 800-171), or establish a SSP(s) and POA&Ms that varies from NIST 800-171 only in accordance with DFARS clause 252.204-7012(b)(2), for all covered contractor information systems affecting this contract.

b. Notwithstanding the allowance for such variation, the contractor shall identify in any SSP and POA&M their plans to implement the following, at a minimum:

(1) Implement Control 3.5.3 (Multi-factor authentication). This means that multi-factor authentication is required for all users, privileged and unprivileged accounts that log into a network. In other words, any system that is not standalone should be required to utilize acceptable multi-factor authentication. For legacy systems and systems that cannot support this requirement, such as CNC equipment, etc., a combination of physical and logical protections acceptable to the Government may be substituted.

(2) Implement Control 3.1.5 (least privilege) and associated Controls and identify practices that the contractor implements to restrict the unnecessary sharing with, or flow of, covered defense information to its subcontractors, suppliers, or vendors based on need-to-know principles.

(3) Implement Control 3.1.12 (monitoring and control remote access sessions) - Require monitoring and controlling of remote access sessions and include mechanisms to audit the sessions and methods.

(4) Audit user privileges on at least an annual basis.

(5) Implement:

i. Control 3.13.11 (FIPS 140-2 validated cryptology or implementation of NSA or NIST approved algorithms (i.e. FIPS 140-2 Annex A: AES or Triple DES) or compensating controls as documented in a SSP and POAM); and,

ii. NIST Cryptographic Algorithm Validation Program (CAVP) (see https://csrc.nist.gov/projects/cryptographic-algorithm-validation-program).

(6) Implement Control 3.13.16 (Protect the confidentiality of CUI at rest) or provide a POA&M for implementation which shall be evaluated by the Navy for risk acceptance.

(7) Implement Control 3.1.19 (encrypt CUI on mobile devices) or provide a plan of action for implementation which can be evaluated by the Government Program Manager for risk to the program.

4.8.10.6 Security Controls

The contractor shall implement CNSSI 1253 technical security controls applicable to MCWS-L and MCWS-H systems as specified in the PSPECs, SSP and in accordance with the DoD implementation guidelines found on the RMF Knowledge Service at (https://rmfks.osd.mil/login.htm).

4.8.10.7 Applications for Use

All COTS applications required to provision and configure the MCWS-L and MCWS-H systems shall be approved for Marine Corps use within the Department of the Navy Application and Database Management System (DADMS). The contractor shall deliver the information needed to obtain the software approval in the DADMS systems.

4.8.10.8 Security Requirements Traceability Matrix

The contractor shall deliver Security RTMs (SRTMs) for both the MCWS-L and the MCWS-H variants separately, and the SRTMs shall include applicable Defense Information Systems Agency (DISA) Security and Technical Implementation Guides (STIGs). Applicable DISA STIGs shall be based on the contractor provided material solution. This will result in a total of two CDRL deliverables. One CDRL deliverable for MCWS-L Technical Report and one CDRL deliverable for MCWS-H Technical Report.

(CDRL A017, Technical Report – Study/Services, SRTM)

4.8.10.9 Authorization Boundary Diagram

The contractor shall deliver Authorization Boundary Diagrams in the following formats: .vsdx, .pptx, and .jpg for both the MCWS-L and the MCWS-H variants separately. The diagram shall depict all MCWS-L and –H hardware and external/internal interfaces provided by the contractor’s material solution. This will result in a total of two CDRL deliverables. One CDRL deliverable for MCWS-L Technical Report and one CDRL deliverable for MCWS-H Technical Report.

(CDRL A018, Technical Report – Study/Services, Authorization Boundary Diagram)

4.8.10.10 Hardening and Configuration

The contractor shall harden and configure MCWS-L and MCWS-H Systems in accordance with DISA STIGs, to include automated Security Content Automated Protocol (SCAP) and manual settings for both the MCWS-L and the MCWS-H variants. Applicable STIGs shall be based on the contractor provided material solution. The contractor shall deliver STIG checklists in .ckl format. The contractor shall deliver SCAP scans results in XCCDF.xml format. This will result in a total of four CDRL deliverables. One CDRL deliverable for MCWS-L Technical Report;

one CDRL deliverable for MCWS-L STIG report; one CDRL deliverable for MCWS-H Technical Report; one CDRL deliverable for MCWS-H STIG report.

(CDRL A019, Technical Report – Study/Services, SCAP files) (CDRL A020, STIG Report, STIG Checklist)

4.8.10.11 Vulnerability Scans

The contractor shall perform Assured Compliance Assessment Solution (ACAS) vulnerability scans. The contractor shall deliver ACAS scans results in .nessus format for both the MCWS-L and the MCWS-H variants separately. This will result in a total of two CDRL deliverables. One CDRL deliverable for MCWS-L Technical Report and one CDRL deliverable for MCWS-H Technical Report.

(CDRL A021, Technical Report – Study/Services, ACAS Scan files)

4.8.10.12 STIG Mitigation and Remediation

The contractor shall deliver technical guidance on remediation and mitigation of all open findings from DISA STIGs. The contractor shall incorporate open STIG findings into the Government provided Plan of Action and Milestones (POA&Ms) in .csv format for both the MCWS-L and the MCWS-H…