842469570 Zero Trust RFP.docx

HC108424R0013

Section SF 1449 - CONTINUATION SHEET

PWS

PERFORMANCE WORK STATEMENT (PWS)

1. Contracting Officer’s Representative (COR).

Please see DITCO text G1

2. Contract or Task Order Title. DISA’s Zero Trust Compliancy Software Solution

3. Background. DISA requires the ability to provide secure infrastructure and services across the Ecosystem to ensure Mission Partners have the proper security access to their applications. Acquiring Zero Trust Compliancy Software products will upgrade the mainframe environment to support the mission. The Zero Trust Compliancy Software solution will simplify monitoring, incident management, and help decrease time to resolve complex hybrid microservices-based environments. It can be used to modernize applications, which is imperative, and monolithic applications can be transformed to containerized and microservices-based architectures and provide a path forward, bridging DISA’s investments in traditional workloads and modern cloud-based environments.

With constant security threats, the Department of Defense (DoD) must develop, manufacture, and maintain sensitive technologies vital to the defense of the Nation. Safeguarding the technical information used for the design and manufacture of these technologies is critical. Malicious cyber-attacks routinely target the DoD systems. Malicious cyber activity poses opportunities for drawing resources and attention from the core missions. These attacks also complicate the Department's acquisition processes, raising costs for the Government and United States taxpayers. To meet this need, the Government must acquire a Zero Trust Compliancy Software solution, to include web-based installation, scripting, implementation, and customization assistance to ensure a quick and smooth rollout process to upgrade cybersecurity.

DISA’s next generation of IBM Mainframe software systems risk security vulnerability and may not be adequate to provide the proper assurance of availability and capacity to support the customers’ mission requirements. Therefore, DISA must invest in a new software solution to more efficiently host systems that provide a highly available, secure, and robust computing environment. Based on the technical evaluation and the implementation cost, new products will be selected to meet organizational needs and functional requirements. Acquiring IBM Security Verification and z/OS Multi-Factor Authentication Enablement (MFA) product licenses and maintenance in support of the mainframe environment to support our mission. IBM software and support will simplify monitoring and incident management, help decrease time to resolve complex hybrid microservices-based environments. It can be used to modernize applications which is imperative and monolithic applications can be transformed to containerized and microservices based architectures and provide a path forward, bridging DISA’s investments in traditional workloads and modern cloud-based environments. Technical evaluations on mainframe and distributed software products have been conducted throughout the enterprise allowing elimination of functionally equivalent software and the associated duplicative costs. In addition, to maintain network and system availability, investment is required in tools that manage, monitor, and report on events from computing center systems. Replacement of legacy Government Off the Shelf (GOTS) products, as well as, outdated products, is required in order to ensure the DISA computing centers can continue to meet the growing customer base while allowing Mission Partners to meet their mission.

4. Objectives: The objective is to obtain procure a proprietary, brand-name, commercial off-the-shelf IBM Zero Trust Compliancy Software solution for DISA in support of Data Center Mechanicsburg and Data Center Ogden. The requirement includes software licenses, software subscriptions and support required to meet the Zero Zero Trust Compliancy Software solution requirement are as follows:

5. Scope.

The contractor shall provide a Zero Trust Compliancy Software solution for the mainframe terminal emulation and associated products and modernization of DISA’s cybersecurity for 65,000 DoD users, while meeting all Government technical requirements listed in Section 6 of this PWS. All licensed software products shall be of type commercial-off-the-shelf software and meeting Licensed Software requirements listed in Section 6.1 of this PWS. All maintenance support is listed in Section 6.2 of this PWS.

6. Performance Requirements. The Contractor shall provide a solution that meets all the following requirements:

6.1 Task 1 - Provide Licensed Software.

6.1.1 Subtask 1 - Provide Software Licenses. The solution provides continuous licensing of included software for the duration of the listed terms.

6.1.2 Subtask 2 - Provide Physical Software (electronic form). The solution provides current object code versions of computer programs (software), which are free from defect, for the duration of the listed terms.

6.1.3 Subtask 3 - Provide Software Functionality. The solution provides functionality under Security Verification and Multi-Factor Authentication Enablement, meeting Government System Administrator’s (Admin's) acceptance.

Security Verification and Multi-Factor Authentication Enablement provides secure web-to-host access to local and remote mission partners on the Department of Defense Information Networks. The desired outcome is to modernize the mainframe cybersecurity support current and future technology.

Required Capability Areas (CA) Table 1:

CA-1

Create and manage Identifications (IDs) within the 3 zOS Access Control Point(s) (ACP): Resource Access Control Facility (RACF), Time Sharing System (TSS), Access control Facility 2 (ACF2)

CA-2

Create and manage IDs within the z-Virtual Machine (zVM) ACP Virtual Machine secure (VMSecure)

CA-3

Create and manage IDs within the Linux on z environments

CA-4

Capable of automated ID provisioning/deprovisioning within the 3 zOS ACPs (RACF, TSS, ACF2)

CA-5

Offer centralized security database support

CA-6

Provide the ability to do privileged access multifactor authentication (RSA Tokens)

CA-7

Serve as mediation layer between Mainframes and DoD Security Verification solutions (i.e., Radiant Logic Application programming interface (APIs), Sailpoint plugins, etc.)

CA-8

User Self-service password reset, and account unlock

CA-9

Certificate-based authentication, Personal Identity Verification (PIV), Common Access Card (CAC) support; comply with DoD Mainframe Security Technical Implementation Guide (STIG) audit standards *

CA-10

Create and manage IDs within the Multi Host Internet Access Portal (MIAP) internal user account repository (Windows AD) utilized by Microfocus (OpenText) Host Access for the Cloud

6.1.4 Subtask 4 - Provide for Software Usage. The solution provides allowance for Government usage of licensed software (as per 6.1.1).

6.1.5 Subtask 5 - Provide Supplemental Software Materials. The solution provides all supplemental software materials that Contractor routinely makes available as adjuncts to said software products (as per 6.1.2).

6.1.6 Subtask 6 - Provide License Keys. The solution provides all license keys, where required for activation or operation of said software (as per 6.1.2).

6.1.7 Subtask 7 - Provide for Updates. The solution provides non-cost updates to current or earlier versions of said software (as per 6.1.2), downloadable or delivered via email.

6.1.8 Subtask 8 - Provide for Upgrades. The solution provides for all upgrades to new major versions of said software (as per 6.1.2), downloadable or delivered via email.

6.1.9 Subtask 9 - Provide for Continuity of Operations (COOP) Testing. The solution provides allowance for no-cost COOP Testing (non-production) of said software (as per 6.1.2).

6.1.10 Subtask 10 - Provide for Compatibility Testing. The solution provides allowance for no-cost Compatibility & Interoperability Testing (non-production) of said software (as per 6.1.2).

Deliverables

Date

Upon contract award and throughout the life of the contract License confirmation

Terms shall be in accordance with the requirements of the contract

Upon contract award and throughout the life of the contract

Upon contract award and as available throughout the life of the contract

Upon contract award and as available throughout the life of the contract

Upon contract award and as available throughout the life of the contract

Upon contract award and as available throughout the life of the contract

contract award and as available throughout the life of the contract

contract award and as available throughout the life of the contract

Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR.

6.2 Task 2 - Provide Software Maintenance.

6.2.1 Subtask 1 - Provide Technical Support Maintenance. The solution provides continuous software maintenance support for the duration of the listed licenses.

6.2.1.1 Subtask 1 - Provide for Incident Submissions. The solution provides the ability of Government to submit Incidents for support services provided by a dedicated engineer or an equivalent shared group resource. The solution provides that the same engineer is assigned to the Security Verification Project for the entire life of the contract, provided said engineer continues to be found acceptable by Government Cyber Security Project Manager.

6.2.1.2 Subtask 2 - Provide Timed Incident Responses. A 30-minute response time by phone from Business Support engineer for each submitted Severity 1 incident and 4 hours for others.

6.2.1.3 Subtask 3 - Provide for Incident Submission Times. The solution provides the ability to submit said Incidents at times according to level of incident severity: Severity1: 24x7x365; Severity2: during regular Business Hours; Severity3: during regular Business Hours; Severity4: during regular Business Hours, where regular Business Hours are 7:00 AM Eastern Standard Time (EST) through 8:00 PM EST, Monday through Friday.

6.2.1.4 Subtask 4 - Provide for Incident Escalation. The solution provides the ability to escalate submitted Incidents through the Contractor's support management hierarchy: Manager -> Support Center Manager -> Regional Support Director -> Global Support Director.

6.2.1.5 Subtask 5 - Provide Incident Resolution Details and Materials. The solution provides all resulting patches, updates, materials following resolution of submitted Business Support Incidents.

6.2.1.6 Subtask 6 - Provide Annual Product Support Review. The solution provides the same engineer to perform telephonic Remote Premium Support sessions up to 4 days per year for Security Verification troubleshooting, planning, or training, as arranged by Cyber Security Admin.

6.2.1.7 Subtask 7 - Provide Access to Technical Notes Database. The solution provides the ability of Government to remotely search Contractor's Technical Notes database for information to aid in problem resolution.

6.2.1.8 Subtask 8 - Provide for Software Defect Reporting. The solution provides the ability of Government to report software defects to Contractor's Customer Center for Business Support software maintenance support resolution.

6.2.1.9 Subtask 9 - Provide for Software Vulnerability Reporting. The solution provides the ability of Government to report software security vulnerabilities to Contractor's Customer Center for Business Support software maintenance support resolution.

6.2.1.10 Subtask 10 - Provide for Software Enhancement Requests. The solution provides the ability of Government to request product enhancements through Contractor's Customer Center.

6.2.1.11 Subtask 11 - Provide Engineering Services to Implement Solution. Provide for all required engineering services to successfully implement the solution. Included, but not limited to:

· Engineering documents that containing the full solution to satisfy high availability requirements to include the following:

· Hosts

· Function (application, database, web)

· Geographic location

· Number of Logical Partitions (LPARs)

· System requirements

· Network

· Diagram

· Input/Output

· Ports

· Protocols (https, Transport Layer Security (TLS), etc.)

· Specialized Software

· Other software required to support the solution.

6.2.1.12 Subtask 12 - Provide weekly status calls to review incidents and enhancements. The solution provides the ability of Government and the Contractor to track and discuss incidents and enhancements.

Date

Upon contract award and throughout the life of the contract

Upon closure of support incident ticket

Upon contract award, and as changed throughout the life of the contract

Within 30 days of contract award, as initiated by IBM Admin Provides for all required engineering services to successfully implement the solution.

contract award, as initiated by IBM Admin

Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR.

6.3 Task 3 Software Support

IBM support personnel shall assist with z/OS MFA

· MFA create an implementation plan to enable software and assist in planning meeting(s)

· Make required RACF/ACF2/TSS, AT/TLS and ICSF Changes

· Enable the z/OS MFA Server, including interfaces with the Factor server(s)

· Develop RACF/ACF2/TSS changes with the z/OS security team

· Assist the configuration of the MFA Server with the client's z/OS system programmer team

· Shall be available for Q&A about any z security related topics

· Transfer skills to the client.

IBM support for the Zero Trust solution leveraging IBM Security Verify Access (ISVA) and IBM Security Verify Governance (ISVG):

· Review detailed objectives, use cases and requirements for the Zero Trust Compliancy Software solution,

· Conduct design workshops with DISA to solidify solution requirements for an initial Zero Trust Compliancy Software solution Minimum Viable Product (MVP),

· Create a Conceptual Architectural Design to support the MVP solution based on stated requirements and workshops

· Deploy the ISVA and ISVG solution in a single non-production environment,

· Configure the ISVA and ISVG MVP solution to support an ICAM MVP

· Conduct unit testing of the Verify MVP solution,

· Assist DISA to system test the Verify MVP solution and resolve any issues,

· Document the Verify MVP solution in a Deployment Summary,

· Conduct transfer of information sessions to enable DISA personnel on the Verify solutions,

· Assist DISA to deploy ISVA and ISVG in Production and configure according to the documented Design and Deployment Summary.

7. Performance Standards.

Access to mainframe systems must have at least 99.5% up-time with this product.

Successful download/receipt, installation, and execution of installed code in non-production COOP testing environment by IBM Admin.

Successful download/receipt, installation, and execution of installed code in non-production Compatibility & Interoperability testing environment by IBM Admin.

8. Place of Performance. Business and Premium support shall be performed by Contractor support staff. Remote (telephonic) support is to be delivered to the Government (DISA) Mechanicsburg, Pennsylvania and (DISA) Ogden, Utah locations.

Alternate Place of Performance. As determined by the COR, contractor employees may be required to work at an alternate place of performance (e.g., home, the contractor's facility, or another approved activity within the local travel area) in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, government closure due to inclement weather, etc.). Additionally, the contractor may be required to account for the whereabouts of their personnel should this information be requested by the COR. Non-emergency/non-essential contractors should not report to a closed government facility. Contractor shall prepare all deliverables and other contract documentation utilizing contractor resources. To the extent possible, the contractor shall use best efforts to provide the same level of support as stated in the PWS. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer or the contractor may request an equitable adjustment pursuant to the Changes clause of the contract.

9. Period of Performance (PoP). The PoP for this action will be one year from date of award.

10. Security Requirements. The following security requirements shall apply to this effort:

This requirement is UNCLASSIFIED and will result in a firm-fixed-price stand-alone contract. Security requirements are as follows:

References:

1. DISA End User Access Agreement, 11 February 2021

1. DISA Policy Letter, Unauthorized Connections to Network Devices, 11 September 2013

1. DISA Instruction 240-110-8, Information Security

1. DISA Instruction 240-110-36, Personnel Security

1. DISA Instruction 240-110-38, Industrial Security

1. DISA Instruction 240-110-43, Insider Threat Program

1. DISA Instruction 630-230-19, Cybersecurity

1. DoD Manual 5200.01, Vol 1-3 Information Security Program, 24 February 2012

1. DoD Manual 5200.02, Procedures for the DoD Personnel Security Program, 3 April 2017

1. DoD Instruction 5200.48, Controlled Unclassified Information (CUI), 6 March 2020

1. 32 CFR Part 117, “National Industrial Security Program Operating Manual (NISPOM)”, 24 February 2021

1. DoD Manual 5105.21 Sensitive Compartmented Information Administrative Security Manual: Administration of Information and Information Systems Security (remove if not applicable)

1. DoDI 5230.24, “Distribution Statements for DoD Technical Information,” January 10, 2023

10.1 Facility Security Clearance. As this is an Unclassified contract, no Facility Clearance is required.

10.2 Security Clearance and Information Technology (IT) Level. All personnel performing on or supporting a DISA contract/order in any way will be United States citizens and will have obtained approval for a position of Public Trust. No access to Classified Information is required in this contract.

10.3 Security Contacts. DISA Security Personnel can be contacted for Industrial or Personnel Security related issues at (301) 225-1235 or via mail at:

For Center or Directorate-specific security related matters, contact the Directorate or Center Security Manager at:

Security Manager Contact Information:

10.4 Information Security and other miscellaneous requirements.

10.4.1 Contractor personnel shall comply with all local security requirements.

10.4.2 Contractor employees shall be required to comply with all Government security regulations and requirements. Initial and periodic safety and security training and briefings will be provided by Government security personnel. Failure to comply with Government security regulations and requirements shall require the company to provide the Government with a written remediation/corrective action plan; furthermore, failure to comply with such requirements can be cause for removal and the contractor will not be able to provide service on this contract/order.

10.4.3. Contractor employees with an incident report in Defense Information System for Security (DISS) who have had their access to classified suspended will not be permitted to provide to fill positions requiring access to classified information on a DISA contract/order.

10.4.4 The Contractor shall not divulge any information, classified or unclassified, about DoD files, data processing activities or functions, user identifications, passwords, or any other knowledge that may be gained, to anyone who is not authorized to have access to such information.

10.4.5 DISA retains the right to request removal of contractor personnel regardless of prior clearance or adjudication status, whose actions, while assigned to this contract, clearly conflict with the interest of the Government.

10.4.6 The Contractor shall afford the Government access to the contractor’s documentation, databases and personnel used in performance of the contract/order. Access shall be provided to the extent required to carry out a program of IT inspection (to include vulnerability testing), investigation and audit to safeguard against threats and hazards to the integrity, availability, and confidentiality of data or to the function of information technology systems operated on behalf of DISA or DoD, and to preserve evidence of computer crime.

11. Government Furnished Property (GFP)/Government-Furnished Equipment (GFE)/ Government-Furnished Information (GFI). No GFE / GFI will be provided under this contract.

12. Other Pertinent Information or Special Considerations. No special considerations need to be considered, as the technical services to be provided are routine software support services.

c. Identification of Non-Disclosure Requirements. Non-Disclosure Agreements (NDAs) will be signed by each contractor employee assigned to the contract:

The contractor is responsible for ensuring that all personnel on the contract, to include any new personnel, have executed the DISA-provided NDA and that the NDA is current.

Deliverables: Monthly Status Report (The contractor is responsible for identifying that all personnel, to include any new personnel on the contract, have executed the DISA-provided NDA and the NDA is current as of the date of the monthly status report. Monthly status reports shall be sent to the Contracting Officers and CORs.)

d. Packaging, Packing and Shipping Instructions. For purposes of delivery, contact information is as follows:

Gov. POC (COR): Cory Worley, Cory.L.Worley2.civ@mail.mil

IBM Admin:

e. Inspection and Acceptance Criteria. Refer to Performance Standards (Section 7).

f. Property Accountability. N/A

g. Supply Chain Risk Management (SCRM). N/A

13. Section 508 Accessibility Standards.

E201.1 Scope ICT that is procured, developed, maintained, or used by agencies shall conform to the Revised 508 Standards.

E202.5 ICT Functions Located in Maintenance or Monitoring Spaces Where status indicators and operable parts for ICT functions are located in spaces that are frequented only by service personnel for maintenance, repair, or occasional monitoring of equipment, such status indicators and operable parts shall not be required to conform to the Revised 508 Standards.

E206.1 General. Where components of ICT are hardware and transmit information or have a user interface, such components shall conform to the requirements in Chapter 4.

E207.1 General Where components of ICT are software and transmit information or have a user interface, such components shall conform to E207 and the requirements in Chapter 5.

Exception from E207.1 General: Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to the requirements in Chapter 5.

E207.2 WCAG Conformance User interface components, as well as the content of platforms and applications, shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0 (incorporated by reference, see 702.10.1).

Exceptions from E207.2 WCAG Conformance:

1. Software that is assistive technology and that supports the accessibility services of the platform shall not be required to conform to E207.2.

1. Non-web software shall not be required to conform to the following four Success Criteria in WCAG 2.0: 2.4.1 Bypass Blocks; 2.4.5 Multiple Ways; 3.2.3 Consistent Navigation; and 3.2.4 Consistent Identification.

1. Non-Web software shall not be required to conform to Conformance Requirement 3 Complete Processes in WCAG 2.0.

E207.3 Complete Process for Non-Web Software Where non-Web software requires multiple steps to accomplish an activity, all software related to the activity to be accomplished shall conform to WCAG 2.0 as specified in E207.2.

E208.1 General Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6.

E302 Functional Performance Criteria

302.1 Without Vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

302.2 With Limited Vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.

302.3 Without Perception of Color. Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.

302.4 Without Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

302.5 With Limited Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.

302.6 Without Speech. Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

302.7 With Limited Manipulation. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.

302.8 With Limited Reach and Strength. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.

302.9 With Limited Language, Cognitive, and Learning Abilities. ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

502.4 Platform Accessibility Features. Platforms and platform software shall conform to the requirements in ANSI/HFES 200.2, Human Factors Engineering of Software User Interfaces — Part 2: Accessibility (2008) (incorporated by reference, see 702.4.1) listed below:

1. A. Section 9.3.3 Enable sequential entry of multiple (chorded) keystrokes;

1. B. Section 9.3.4 Provide adjustment of delay before key acceptance;

1. C. Section 9.3.5 Provide adjustment of same-key double-strike acceptance;

1. D. Section 10.6.7 Allow users to choose visual alternative for audio output;

1. E. Section 10.6.8 Synchronize audio equivalents for visual events;

1. F. Section 10.6.9 Provide speech output services; and

1. G. Section 10.7.1 Display any captions provided.

1.

503.1 General Applications shall conform to 503.

503.2 User Preferences Applications shall permit user preferences from platform settings for color, contrast, font type, font size, and focus cursor.

Exception from E503.2 User Preferences: Applications that are designed to be isolated from their underlying platform software, including Web applications, shall not be required to conform to 503.2.

503.3 Alternative User Interfaces. Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services.

503.4 User Controls for Captions and Audio Description Where ICT displays video with synchronized audio, ICT shall provide user controls for closed captions and audio descriptions conforming to 503.4.

503.4.1 Caption Controls Where user controls are provided for volume adjustment, ICT shall provide user controls for the selection of captions at the same menu level as the user controls for volume or program selection.

503.4.2 Audio Description Controls. Where user controls are provided for program selection, ICT shall provide user controls for the selection of audio descriptions at the same menu level as the user controls for volume or program selection.

Verify Access Virtual Enterprise Edition

FFP

Software subscriptions (PASSPORT AVANTAGE SITE ID # 7884648) Provide Verify Access Virtual Enterprise Edition in accordance with (IAW) the Performance Work Statement (PWS) dated June 14, 2024. Period of Performance: July 1, 2024 - June 30, 2025 FOB: Destination

MFR PART NR: D1L2PLL

PSC CD: DA10

NET AMT

Verify Governance Enterprise

PASSPORT AVANTAGE SITE ID # 7884648 Provide Verify Governance Enterprise in accordance with (IAW) the Performance Work Statement (PWS) dated June 14, 2024. Period of Performance: July 1, 2024 - June 30, 2025 FOB: Destination

MFR PART NR: D1K1JLL

NET AMT

Verfy Governance Host Adapters

PASSPORT AVANTAGE SITE ID # 7884648 Provide Verfy Governance Host Adapters in accordance with (IAW) the Performance Work Statement (PWS) dated June 14, 2024. Period of Performance: July 1, 2024 - June 30, 2025 FOB: Destination

MFR PART NR: D29GZLL

NET AMT

zSecure CICS Tool Kit V3

Software Licenses Provide zSecure CICS Tool Kit V3 in accordance with (IAW) the Performance Work Statement (PWS) dated June 14, 2024. Period of Performance: July 1, 2024 - June 30, 2025 FOB: Destination

MFR PART NR: 5655ABD

NET AMT

z/Multi-Factor Auth V2

Provide z/Multi-Factor Auth V2 in accordance with (IAW) the Performance Work Statement (PWS) dated June 14, 2024. Period of Performance: July 1, 2024 - June 30, 2025 FOB: Destination

MFR PART NR: 5655MA2

NET AMT

IBM Lab Services for MFA Integration

Provide IBM Lab Services for MFA Integration support in accordance with (IAW) the Performance Work Statement (PWS) dated June 14, 2024. Period of Performance: July 1, 2024 - June 30, 2025 Contractor is authorized to invoice monthly in arrears.

FOB: Destination

MFR PART NR: SERVICES 1

NET AMT

IBM Lab Services for Security Verify

Provide software solution implementation IBM Lab Services for Security Verifyin accordance with (IAW) the Performance Work Statement (PWS) dated June 14, 2024. Period of Performance: July 1, 2024 - June 30, 2025 Contractor is authorized to invoice monthly in arrears.

FOB: Destination

MFR PART NR: SERVICES 2

NET AMT

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

DELIVERY INFORMATION

CLAUSES INCORPORATED BY REFERENCE

CLAUSES INCORPORATED BY FULL TEXT

52.204-24 REPRESENTATION REGARDING CERTAIN TELECOMMUNICATIONS AND VIDEO SURVEILLANCE SERVICES OR EQUIPMENT (NOV 2021)

The Offeror shall not complete the representation at paragraph (d)(1) of this provision if the Offeror has represented that it "does not provide covered telecommunications equipment or services as a part of its offered products or services to the Government in the performance of any contract, subcontract, or other contractual instrument" in paragraph (c)(1) in the provision at 52.204-26, Covered Telecommunications Equipment or Services--Representation, or in paragraph (v)(2)(i) of the provision at 52.212-3, Offeror Representations and Certifications-Commercial Products and Commercial Services. The Offeror shall not complete the representation in paragraph (d)(2) of this provision if the Offeror has represented that it "does not use covered telecommunications equipment or services, or any equipment, system, or service that uses covered telecommunications equipment or services" in paragraph (c)(2) of the provision at 52.204-26, or in paragraph (v)(2)(ii) of the provision at 52.212-3.

(a) Definitions. As used in this provision-

Backhaul, covered telecommunications equipment or services, critical technology, interconnection arrangements, reasonable inquiry, roaming, and substantial or essential component have the meanings provided in the clause 52.204-25, Prohibition on Contracting for Certain Telecommunications and Video Surveillance Services or Equipment.

(b) Prohibition.

(1) Section 889(a)(1)(A) of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L. 115-232) prohibits the head of an executive agency on or after August 13, 2019, from procuring or obtaining, or extending or renewing a contract to procure or obtain, any equipment, system, or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system. Nothing in the prohibition shall be construed to--

(i) Prohibit the head of an executive agency from procuring with an entity to provide a service that connects to the facilities of a third-party, such as backhaul, roaming, or interconnection arrangements; or

(ii) Cover telecommunications equipment that cannot route or redirect user data traffic or cannot permit visibility into any user data or packets that such equipment transmits or otherwise handles.

(2) Section 889(a)(1)(B) of the John S. McCain National Defense Authorization Act for Fiscal Year 2019 (Pub. L.