N00024-19-R-5503-0011_7.17.2019.pdf

N0002418NR42001

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 this amendment is to clarify the Statement of Work section 3.10.4 Encryption of Data at Rest.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 8

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

16C. DATE SIGNED

BY 17-Jul-2019

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 N0002419R5503

X 9B. DATED (SEE ITEM 11)

30-Apr-2019

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

17-Jul-2019

CODE

NAVAL SEA SYSTEMS COMMAND (HQ)

1333 ISAAC HULL AVE SE

WASHINGTON NAVY YARD DC 20376-2030

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N0002419R5503

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

AN/SLQ-32 (V) 6 FY20-24 PRODUCTION

1.0 SCOPE

This SOW defines the effort required for the production and testing of various configurations of Surface Electronic Warfare Improvement Program (SEWIP) AN/SLQ-32(V)6 electronic support antenna and receiver systems/subsystems.

The AN/SLQ-32(V)6 is configured for installation on Arleigh Burke Class DDGs and includes a Block 2 ES subsystem, a Block 1B3 HGHS subsystem and a Liquid Conditioning Unit (LCU).

The AN/SLQ-32A(V)6 is configured for installation on Zumwalt Class DDGs and includes a Block 2 ES subsystem.

The AN/SLQ-32C(V)6 is configured for installation on Small Surface Combatants including Freedom and Independence Class LCSs and U.S. Coast Guard Offshore Patrol Cutters. It includes a Block 2 ES subsystem and a Liquid Conditioning Unit (LCU).

The contractor shall provide all of the personnel, facilities, equipment and fixtures to manufacture, assemble, test and deliver all AN/SLQ-32(V)6 configurations listed in the table below. All items presented for acceptance shall be manufactured, assembled, and tested in accordance with (IAW) the Technical Data Package (TDP) (Attachment J-6) and GFI Incorporated herein (Attachment J-2). Notwithstanding the nomenclature used, the part numbers and drawing numbers provided shall be considered dispositive in the event a conflict is identified.

AN/SLQ-32(V)6 AN/SLQ-32A(V)6 AN/SLQ-32C(V)6

Block 2 ES Subsystem Drawing Number 8493935G3* 8493945G2 77C736819G4 Block 1B3 HGHS Subsystem Drawing Number 77C734560G1 N/A N/A LCU Single Pump Drawing Number 7392144-01 N/A 7392144-01 *Note: System to be delivered with or without Shelter Structure in accordance with Section B.

If CLIN 9600 and/or 9601 options are exercised, the contractor shall provide sets of Antenna Support Electronics Assembly (ASEA) Drawing 8493970G4 (1 set consists of qty 2 of drawing 8493970G4) in accordance with Section B.

2.0 APPLICABLE DOCUMENTS

The contractor shall use the following documents in support of the requirements of this contract.

2.1 Military Standards

Document Number Title Effective Date MIL-STD-129R Military Marking for Shipment and Storage 24 MAY 2018 MIL-STD-130N Change 1 Identification Marking of U.S. Military Property 16 NOV 2012 MIL-STD-196F Joint Electronics Type Designation Automated System 30 MAY 2018 MIL-STD-881C Work Breakdown Structures for Defense Material Items 19 JUN 2018

2.2 Military Handbooks

Document Number Title Effective Date

MIL-HDBK-61A Configuration Management Guidance 07 FEB 2001 MIL-HDBK-470A Designing and Developing Maintainable Products and Systems 31 MAY 2012 MIL-HDBK-2036 Preparation of Electronic Equipment Specifications 01 NOV 1999 MIL-HDBK-2164A Environmental Stress Screening Process for Electronic Equipment 19 JUN 1996

2.3 Other Government Documents

Document Number Title Effective Date DoDI 8500.01 Cybersecurity 14 MAR 2014 DoD IUID Guide DoD Guide to Uniquely Identifying Items 16 SEP 2015 NAVSEA INST 9400.2 Implementation of Naval Sea Systems Command (NAVSEA) 20 SEP 2016

Afloat Information Assurance and Guidance NAVSO P-6071 Best Practices for Manufacturing Planning MAR 1986 TE000-AB-GTP-020 Government Stress Screening of Hardware 01 JAN 1992

2.4 ASME Standards

Document Number Title Effective Date ASME Y14.24 Types and Applications of Engineering Drawings 01 JAN 2012 ASME Y14.34 Associated Lists 01 JAN 2013 ASME Y14.35 Revision of Engineering Drawings and Associated Documents 29 AUG 2014 ASME Y14.38 Abbreviations and Acronyms for Use on Drawings and 01 JAN 2007

Related Documents ASME Y14.100 Engineering Drawing Practices 14 NOV 2017

2.5 International Organization for Standardization

Document Number Title Effective Date ISO 9001:2015 Quality Management Systems — Requirements SEP 2015 ISO 10007 Quality Management Systems — Guidelines for 01 MAR 2017

Configuration Management – Third Edition

2.6 SAE International

Document Number Title Effective Date SAE EIA-649-B Configuration Management Standard 01 APR 2011 SAE EIA-649-1 Configuration Management Requirements for Defense Contracts 20 NOV 2014

3.0 REQUIREMENTS

The contractor shall manufacture various configurations of the SEWIP AN/SLQ-32(V)6 system IAW the following sections:

3.1 Program Management Support

The Contractor shall assign a qualified Program Manager (PM) who shall have complete responsibility for the planning, execution, control and reporting of all aspects of the program, and for directing in-house and subcontractor efforts. The Contractor shall develop, maintain, and deliver a Contract Work Breakdown Structure IAW CDRL A001. The Contractor shall develop, maintain, and deliver an Integrated Master Schedule (IMS) IAW CDRL A002.

3.2 Information Assurance (IA) Strategy

The Contractor shall implement IA processes IAW DoDI 8500.01, and comply with guidance and technologies described in NAVSEA INST 9400.2. The Contractor shall develop and deliver an Information Support Plan IAW CDRL A003. For the first system produced in each configuration, the contractor shall conduct an IA scan assessment and provide a test report IAW CDRL A004.

3.3 Configuration Management

See C-243-H003, below, for guidance on configuration management. The contractor shall prepare and deliver the Supplier’s Configuration Management Plan prepared IAW CDRL A005.

Participation in the development of Class I and Class II Engineering Change Proposals (ECPs) shall be required.

The Contractor shall support the Class I ECP development during Quarterly Program Reviews (QPR) by reporting and summarizing any issues related to the production of all variants of the AN/SLQ-32 (V)6 system IAW the TDP.

These issues shall be reported as a report, record of meeting minutes IAW CDRL A006. The contractor shall submit Class II ECPs in accordance with CDRL A030 and associated Notice of Revisions (NORs) in accordance CDRL A031.

3.3.1 Request for Variance

In the event that a variance is identified, the Contractor shall prepare and deliver a Request For Variance IAW

CDRL A007.

3.3.2 Diminishing Manufacturing Sources and Material Shortages (DMSMS) The contractor shall identify obsolete components during procurement of material and document the results IAW

CDRL A008.

3.4 Hardware Production Documentation

The Contractor shall prepare and deliver:

1. Contractor’s Quality Assurance Plan prepared IAW CDRL A009.

2. Handling Procedures for Electrostatic Discharge (ESD) Sensitive Devices prepared IAW CDRL A010

3. Counterfeit Prevention Plan prepared IAW CDRL A011.

3.5 Post Award Conference

The Contractor shall schedule and host a Post Award Conference at the contractor’s facility no later than 60 days after award of the contract. The purpose of this conference is to review the initial production plans. The contractor shall prepare and deliver a Post Award Conference meeting agenda IAW CDRL A012 no later than one week before the date of the post award conference. The contractor shall prepare and deliver meeting minutes IAW CDRL A006 no later than one week after completion of the Post Award Conference.

3.6 Quarterly Program Reviews (QPR)

The Contractor shall schedule and host program reviews on a quarterly basis at the contractor’s facility. The purpose of the QPR is to review the production status. The contractor shall prepare and deliver a QPR meeting agenda IAW CDRL A012 no later than one week before the date of the QPR. The contractor shall prepare and deliver meeting minutes IAW CDRL A006 no later than one week after completion of the QPR.

3.7 Production Readiness Review (PRR)

The Contractor shall schedule and host a PRR within 30 days following Government approval of the Supplier’s Configuration Management Plan required in SOW paragraph 3.3 and the Hardware Production Documentation required in SOW paragraph 3.4.

The Contractor shall use the DoD PRR checklist, attached herein as Attachment J-12 to prepare for the PRR. The PRR shall assess the following: manufacturing process readiness, quality management system, production planning, system requirements compliance, inventory management, and supplier management.

The Contractor shall prepare and deliver a PRR meeting agenda IAW CDRL A012 no later than one week before the date of the PRR. The contractor shall deliver meeting minutes IAW CDRL A006 no later than one week after completion of the PRR.

3.8 Engineering and Test Support

The Contractor shall ensure personnel, procedures, equipment, and facilities used for all required tests conform with the approved test procedure(s), which are provided as GFI

3.8.1 Test Readiness Review (TRR)

For each variation, the contractor shall conduct a test readiness review (TRR) 30 days prior to starting the FAT. The contractor shall deliver an agenda IAW CDRL A012 no later than one week before the date of the TRR. The contractor shall deliver meeting minutes IAW CDRL A006 no later than one week after completion of the TRR.

3.8.2 First Article Qualification Test (FAQT)

For each (V)6 variant, the contractor shall conduct a FAQT on the first manufactured unit for each configuration.

The FAQT shall be completed using the approved test procedure(s), which are provided as GFI. The Contractor shall document results of the FAQT and report IAW CDRL A013. Government approval of the FAQT report, or waiver of FAQT requirements, shall be a prerequisite to acceptance of the first manufactured unit for each configuration.

If modification of the approved test procedure is necessary, the contractor shall submit proposed modifications IAW CDRL A014. The Contractor shall own or have access to equipment and facilities capable of testing IAW the approved test procedure(s). The Contractor shall correct all deficiencies found as a result of FAQT.

3.8.3 Physical Configuration Audit (PCA)

The Contractor shall conduct a Government-witnessed PCA. The PCA shall be held after the first production unit has completed FAQT. The PCA shall be conducted at the Contractor facility. The purpose of the PCA is to verify the as-built configuration matches the technical documentation and to validate supporting processes.

The Contractor shall use the PCA Plan delivered as GFI as a baseline. The contract shall update the PCA Plan only as required for successful PCA completion. If updates are made, the Contractor shall deliver a Physical Configuration Audit (PCA) Plan, IAW CDRL A015, and shall conduct the PCA as defined by the Government accepted plan.

The PCA requires major disassembly of the first unit to a level which will allow for verification of all drawing defined configuration items and an in-depth review of the associated Product Drawings/Models and Associated Lists in comparison with the first unit. Any conflict between the Product Drawings/Models and Associated Lists and the first unit shall be identified, documented. Findings and corrective action shall be delivered IAW CDRL A016.

3.8.4 Environmental Stress Screening (ESS)

ESS shall be conducted on all units prior to any system level functional tests IAW the approved ESS Procedures and Implementation Plan, provided here as GFI. The contractor shall submit proposed updates to the Government-provided test procedure IAW CDRL A017. Results of ESS testing shall be documented IAW CDRL A018

3.8.5 Factory Acceptance Test (FAT)

A FAT shall be conducted on all units before delivery. The Contractor shall perform testing IAW the Test Procedure, Factory Acceptance, provided here as GFI. The contractor shall submit proposed updates to the Government-provided test procedure IAW CDRL A019. The Contractor shall document and deliver the results of the FAT IAW CDRL A020.

3.8.6 Failure Analysis/Corrective Action Report (FACAR) Generation A FACAR shall be generated for each configuration item (as defined by EIA-649-1) that fails during any test event.

FACARs shall be generated IAW CDRL A021.

3.8.7 Trouble Report (TR)

The Contractor shall generate and deliver a TR if software or firmware is suspect in a test event failure.

TRs shall be submitted IAW CDRL A022.

3.8.8 As Built Configuration List (ABCL)

The contractor shall submit an ABCL for each delivered unit IAW CDRL A023.

3.9 Cost Reporting

Cost data reports shall be provided IAW CDRLs A024, A025, and A026.

3.10 Detailed Tasks, Cyber Security (All Items)

The Contractor shall implement the security requirements of the clause under Section I of this contract entitled DFARS 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting, and National Institute of Standards and Technology (NIST) Special Publication 800-171.

3.10.1 System Security Plan (SSP)

The Contractor shall develop and submit a Technical Report – Study/Services, POAM and Systems Security Plan (SSP) (CDRL A027) that implements the security requirements of DFARS 252.204-7012.

In accordance with DFARS 252.204-7012, the SSP shall implement, at a minimum, all security requirements in NIST 800-171 (Rev. 1) standards 3.1 to 3.14; or ensure that any unimplemented security requirements have been adjudicated by an authorized representative of the DoD CIO to be non-applicable or to have an alternative, but equally effective, security measure in its place. The SSP shall provide proof of such adjudication by DoD CIO.

Further, the SSP shall contain a description of the system boundary, the operational environment, how the specific security requirements are currently implemented, and the relationships with or connections to other systems. The POAM shall detail how and when the Contractor will meet all security requirements of 800-171 that are not fully implemented except for the requirements noted in the specific bullets below, which must be fully implemented in the SSP. The Contractor shall permit the Government to validate information in the SSP every three years, on an ad hoc basis with no notice to the Contractor, other than to coordinate any necessary security requests, but not more than five business days, or upon replacement or rotation of the Government program manager.

The SSP shall:

• Fully implement Multi-factor authentication, including authentication and authorization of users in a manner that is auditable

• Implement FIPS 140-2 validation encryption at a minimum of Level 2

• Employ the principle of least privilege or “need to know”

• Require the Contractor to review, in a manner that can be audited, user privileges at least annually

• Require monitoring and controlling remote access sessions and includes mechanisms to audit the session and methods

3.10.2 SSP and POAM Review

The Contractor shall allow the Government to evaluate the SSP and POAM upon request, including on the Contractor’s site, on an ad hoc basis. The Government will provide sufficient notification, but not more than five business days, to the Contractor to allow for the processing of visit requests to the site, if necessary. The Contractor shall support this evaluation IAW NIST 800-171A.

3.10.3 Subcontractors

The Contractor shall provide the plan to track flow down of covered defense information and to assess DFARS clause 252.204-7012 compliance for these suppliers/subcontractors in the SSP (CDRL A027).

3.10.4 Encryption of Data at Rest

Covered Defense Information (CDI) and Covered Contractor Information Systems (CCIS) are defined within clause 252.204-7012. On all CCISs, the Contractor shall encrypt CDI on mobile devices and mobile computing platforms in accordance with NIST 800-171 Control 3.1.19.

3.10.5 Incident Reporting

The Contractor shall report cyber incidents, as defined in DFARS 252.204-7012, to the Damage Assessment Management Office (DAMO) via the DIB-Net website within 72 hours, per DFARS 252.204-7012. In addition to the reporting requirements above, the Contractor shall deliver all information related to cyber incidents, defined in DFARS 252.204-7012, in a Technical Report – Study/Services, Cyber Incident Report, IAW CDRL A028. The Contractor shall segregate DON CUI from Contractor-owned information, when feasible. Segregation may be implemented through logical isolation, physical isolation, a hybrid approach, or other technological processes to achieve required delivery of compromised data in cyber incidents.

3.10.6 Coordination with NCIS

The Contractor consents to installation by the Naval Criminal Investigative Service (NCIS) of network sensors, owned and maintained by NCIS, on the Contractor's CCIS or other information technology assets when intelligence indicates a vulnerability or a potential vulnerability for the duration of the contract performance period. If NCIS determines that the Contractor’s own sensor capability is adequate, the Contractor consents to cooperation with NCIS on cybersecurity, to include sharing information from its sensor capability and networks.

Both routinely and in response to emergent developments, NCIS engages in outreach efforts to the defense contracting community to coordinate cybersecurity efforts. The Contractor shall regularly monitor and engage with such efforts to ensure that contractor is aware of the most up-to-date cybersecurity information and strategies. As part of these efforts, the Contractor shall consider implementing all recommendations from NCIS for additional hardening (e.g., more stringent configuration settings) of DON critical programs and technologies.

4.0 GOVERNMENT FURNISHED INFORMATION (GFI) AND PROPERTY (GFP)

Government Furnished Information (GFI) and Property (GFP)

The Contractor shall be provided with GFI and GFP for use in the performance of this contract. The GFI inventory list is attached here as Attachment J-2, and the GFP inventory list is attached here as Attachment J-3. The Contractor shall inspect GFI and GFP within 10 working days of receipt. GFI and GFP deficiencies shall be promptly reported IAW CDRL A029.

5.0 PROVISIONED ITEM ORDERS (CLINs 9800, 9801)

See C-217-H001 PROVISIONED ITEMS ORDERS--BASIC (NAVSEA) (OCT 2018). For CLIN 9801, PIO orders will be placed using the parts listed in Attachment J-14. The Government will specify the subset of required parts from Attachment J-14 and at what quantities in each order. The price of each part shall not exceed the maximum part price specified in Attachment J-14. Prices may be downward adjusted as part of a negotiated order between the Contractor and Government.

6.0 DATA (CLIN 9900)

The data to be furnished hereunder shall be prepared IAW CDRL, DD Form 1423.

6.1 Integrated Digital Data Environment (IDDE)

The Contractor shall use the Government-furnished IDDE to transmit unclassified CDRLs and documents. All Contractor source data published in the IDDE shall be in native format unless otherwise specified. The Government IDDE requires PKI/CAC credentials for access, and the contractor shall be responsible for obtaining/maintaining necessary access credentials. Access to the Government IDDE may be obtained from the Contracting Officer’s Representative.

7.0 SECURITY REQUIREMENTS

Contract performance requires the generation, handling, and safeguarding of classified data. The Contractor shall have facilities appropriate for classified document storage and control as identified in Attachment J-1 – Security Classification Specification, DD Form 254. The Contractor shall have personnel cleared for SECRET information required to maintain knowledge of the current, Non-SCI intelligence information (e.g. threat data). Access up to SECRET is required for contract performance. Information/data generated, handled or utilized in performance of this contract shall not be disclosed to any third party (e.g. foreign governments, other corporate entities, etc.) without prior written approval from the Contracting Officer’s Representative.

Facility Security Clearance Required: The contractor is required to maintain a SECRET facility security clearance

Level of Safeguarding for Classified Information/Material Required at Contractor Facility: The contractor is required to maintain a level of safeguarding for classified information/material at the SECRET level

COMSEC: The Contractor requires COMSEC to accommodate the use of secure communications such as Secure Terminal Equipment (STE). The contractor will be required to have access to COMSEC for the STE phone.

Non-SCI: The contractor will require access to non-SCI. This contract contains technology with the purpose of countering threats of potential adversaries.

Controlled Unclassified Information (CUI)(Formerly for Official Use Only Information): The contractor will be required to have access to CUI.

Other: Contractor will require access to a Secure Terminal Equipment (STE) classified phone, not included as GFP.

Receive, Store, and Generate Classified Information: The contractor will assist in modernizing systems that are classified. Techniques to modernize this equipment, testing of this equipment and overall system performance could be classified and the subject to email and written reports. In this capacity, the contractor will generate and be in receipt of classified material. The contractor requires access to classified source data up to and including the SECRET level. Classified material generated in support of this contract shall be classified in accordance with the source material of the Navy Security Classification Guidance. Automated Information Systems (AIS) must be certified and accredited by the Cognizant Security Agency (CSA) prior to processing classified information from

NAVSEA.

Fabricate, modify, or store classified hardware: The contract will fabricate and modify classified component in support of this contract and then store this hardware until completion of all requirements. All classified data and hardware will be protected IAW DoD 5220.22-M, National Industrial Security Program Operating Manual

(NISPOM).

DTIC: In order to use the current contract specifications and applicable documentation, the contractor is required to use the Defense Technical Information Center (DTIC). DD Form 1540 “Registration for Scientific and Technical Information Services” must be completed for registration with DTIC. The contractor may also submit DD Form 2345 “Militarily Critical Technical Data Agreement” (after registration with DTIC) to the Defense Logistics Services Center for access to unclassified, militarily critical technical data from other DoD sources.

Require COMSEC Account: Contractor requires a COMSEC account to accommodate the use of secure communications. The contractor will be required to have access to COMSEC for Government Furnished Equipment (GFE). Contractor will return ALL GFE or Government purchased COMSEC equipment at the closure of the contract.

Operations Security Requirements: Due to the sensitive nature of this contract, the contractor shall develop and submit for approval an Operations Security (OPSEC) Plan. The contractor is required to protect critical information associated with this contract to prevent unauthorized disclosure and will observe OPSEC requirements.

Be authorized to use the Defense Courier Service (DCS): The contractor will require use of the Defiance Courier Service for the transfer of classified material. Only certain classified information qualifies for shipment by DCS.

Prior approval of the KO is required before a prime contractor can authorize a subcontractor to use the services of

DCS.

Receive, Store, or Generate Controlled Unclassified Information (CUI): The contractor will be required to have access to CUI with developers and integrators.

(End of Summary of Changes)