B08 Attachment 0001 - CHS 6 PWS.docx

PERFORMANCE WORK STATEMENT FOR

COMMON HARDWARE SYSTEMS AND SERVICES

PERFORMANCE WORK STATEMENT

FOR

COMMON HARDWARE SYSTEMS AND SERVICES

SOLICITATION NUMBER: W15P7T-23-R-001

ARMY CONTRACTING COMMAND (ACC) – ABERDEEN PROVING GROUND (APG)

ABERDEEN PROVING GROUND, MD, 21005

Version 022

31 October 2022

PROGRAM EXECUTIVE OFFICE

COMMAND, CONTROL, COMMUNICATIONS – TACTICAL

Distribution Statement A: Approved for public release. Distribution is unlimited

Table of Contents

1.0 Scope

Common Hardware Systems – 6th Generation (CHS-6) is an Indefinite Delivery Indefinite Quantity (IDIQ) contract for the rapid procurement of total lifecycle system management solutions in support of the U.S. Army (Army), Department of Defense (DoD), and Federal government programs and agencies. CHS-6 provides seamless and consolidated procurement of Commercial Information Technology (CommIT) including, but not limited to, Commercial Off-The-Shelf (COTS) items, Non-Developmental Items (NDI), components, customizable sustainment strategies, non-personal services and continuous technology upgrades. Equipment and services procured under the terms of this contract will be used to support a unified network for Multi-Domain Operations (MDO) and Joint All Domain Command and Control (JADC2). The contractor shall perform to the standards in this Performance Work Statement (PWS).

This PWS establishes the requirements for contractor-provided equipment and services including Task Orders (TO), Delivery Orders (DO), Basic Purchase Orders (BPO), Technology Insertions (TI), system integration/installation, testing, studies, analyses, logistics support, and engineering support. The overall Product Lead Common Hardware Systems (PdL CHS) program goal is to improve interoperability and commonality among operational forces while lowering lifecycle costs by leveraging centralized procurements of CommIT products.

1.0 1.0

1.1 General Information

As per Army Regulation (AR) 25-1 (dated 15 July 2019) and Army Federal Acquisition Regulation Supplement (AFARS), Part 5139 (Acquisition of Information Technology, dated 15 January 2021), PdL CHS is a mandatory source for all CommIT hardware for tactical and operational requirements. PdL CHS supports Army, DoD, and other Federal and Governmental programs and agencies’ requirements to acquire highly flexible, cost-effective, common, and simplified non-developmental Command, Control, Communications, Computers, Combat Systems, Intelligence, Surveillance, and Reconnaissance (C5ISR) solutions that improve interoperability and connectivity on the battlefield while garnering efficient competition to enable the latest CommIT solutions to be integrated for unified network operations. The PdL CHS product office implements CommIT acquisition strategies for programs through seamless and consolidated procurement, support to programs’ sustainment strategies, and technology upgrades to meet programs’ costs, schedules, and performance requirements.

PdL CHS provides this cross-cutting capability allowing individual programs to garner efficiencies through streamlined common hardware configurations while supporting broader strategic goals and initiatives. The PdL CHS product office’s engineering team coordinates across programs to design and configure CommIT to meet specific requirements for transport or ruggedization, and to ensure configuration, obsolescence, and End-Of-Life (EOL) management is maintained. PdL CHS manages a portfolio of solutions including, but not limited to, servers, storages, clients, networking devices, ruggedized platforms, handheld end devices, Operational Transit Cases (OTC), and peripheral devices that meet programs’ unique requirements. PdL CHS also tracks product warranty, failure and repair data, and related sustainment support data. Additionally, PdL CHS works across programs, and with the organic industrial base, to identify effective and efficient sustainment strategies to help programs achieve lifecycle objectives. This contract provides a mechanism to help the Army, DoD, Federal, and other Governmental programs and agencies meet their requirements.

1.2 Order Type

This is an IDIQ contract with Delivery Orders (DO) and BPOs for hardware issued as Firm-Fixed-Price (FFP) requirements. Task Orders (TO) for services will be either FFP, Cost-Plus-Fixed-Fee (CPFF) (Completion or Term), and/or Cost Contract - No Fee. Cost contract – No fee will be associated with travel and materials on TOs.

1.3 Period of Performance (PoP) / Place of Performance

The proposed CHS-6 IDIQ contract will have an ordering period of 10 years, consisting of a four (4) year base PoP, with two (2) three-year options, and a delivery period of up to 36-months following the ordering period. Administration of product warranties shall continue after the expiration of the contract PoP.

The contractor shall provide worldwide warranty support to hardware procured on the contract. In addition, the contractor shall provide support to contingency environments in the Continental United States (CONUS) and Outside the Continental United States (OCONUS), as per specific TO requirements. The contractor shall deliver hardware procured to OCONUS locations, as per DO requirements.

1.1 1.2 1.3

1.4 Technical Expert Status Accreditation (TESA)

1.5

1.4.1 The Status of Forces Agreement (SOFA)

The contractor shall abide by all SOFA agreements for all OCONUS locations. Specific details will be included in the individual TO PWS for OCONUS support.

1.4.2 Synchronized Pre-Deployment and Operational Tracker (SPOT) Any contractor-required OCONUS travel must be processed through the SPOT website or the current process at time of OCONUS travel. Website: https://spot.dmdc.mil/privacy.aspx

1.4.3 Theater Business Clearance (TBC)

A TBC must be approved by the Government prior to travel to a Theater of Operation.

1.4.1.1

1.4.4 Contractors Accompanying the Force

The Government may require the contractor to support operations and perform Temporary Duty (TDY) in hazardous duty or eminent danger areas. The contractor shall perform this TDY in accordance with AR 715-9, Operational Contract Support Planning and Management.

1.4.5 Contractors on the Battlefield Provisions

Overseas Contingency Operations (OCO) is anticipated during the life of this contract. During these designated periods, the concept of contractor support on the battlefield will apply to the CHS-6 contract. Civilian contractor support is required for the operation and maintenance of CHS-6 equipment prior to, and during, deployment to contingency operation locations. Contractors on the battlefield provisions shall be in compliance with current requirements for Theatre Business clauses included in the contract.

The Field Manual (FM) 100-10-2, Contracting Support on the Battlefield and FM 3-100.21, Contractors on the Battlefield publications in Paragraph 2.0 of this PWS provide additional information on support to the deployed forces.

1.5 Contract Management

This contract shall be managed in accordance with the “Program Management” paragraph 4.0 of this PWS.

1.6 Government Furnished Equipment (GFE)/Materials (GFM)

The Government may furnish equipment to the contractor for integration on specific DOs/TOs, as required, IAW Federal Acquisition Regulation (FAR) 45, Government Property. Some examples include Communications Security (COMSEC) controlled equipment and Army Golden Master (AGM) Operating Systems. Specific guidance on GFE or GFM will be provided in the PWS for each TO or the instructions for DOs.

The Property Management Plan (PMP) shall be a description of the property management system to be used in managing Government property. The PMP shall be submitted within 60 Days After Contract (DAC) and be in accordance (IAW) with FAR 45.201(c)(4). The Contractor shall submit the Property Management System procedures in accordance with FAR 52.245-1(f), along with the PMP. Changes thereafter to the Property Management System must be approved by the Property Administrator prior to implementation.

The Contractor shall obtain prior written authorization and approval from the KO or designee as applicable for any equipment, material, or supplies purchased to support the performance of any detailed requirement under this contract. The Contractor shall provide three cost estimates or a justification for sole source to the KO or designee for review and/or approval prior to purchase.

The contractor shall submit a Government Property (GP) Inventory Report IAW CDRL B012, Government Property (GP) Inventory Report (DI-MGMT-80441D). This report describes the status and supply data about Government Furnished Property (GFP) and Contractor Acquired Property (CAP) which the contractor has received or acquired under the contract. This report will be used to review the condition, installation, and effectiveness of the GP. This DID is applicable to contracts in which GP has been provided or acquired in support of the contract.

1.7 Contractor Furnished Equipment (CFE)/Materials (CFM)

The contractor shall furnish equipment and/or materials, as required to support TO actions. Specific guidance on GFE/GFM will be provided in the PWS for each TO/DO.

The contractor shall furnish equipment and/or materials for the purpose of First Article Testing (FAT) supporting the initial delivery of each new configuration item procured via the contract.

1.8 Inspections and Acceptance

The Government will evaluate the contractor's performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). The QASP serves as the plan for surveillance of performance and identifies the performance indicators, standards, inspections methods and procedures to be used in monitoring performance. It details thresholds for acceptable and unacceptable performance of specific tasks within the PWS.

Material inspection, receiving, and acceptance will be reported on DD Form 250, Material Inspection and Receiving Report.

1.9 Security

The security requirements are defined in Attachment 005 (DD Form 254), Contract Security Classification Specification. All facility clearance sponsorships for subcontractors must meet Government requirements and certification. The Government will provide a DD Form 254 with each TO, as appropriate.

Contractor personnel may require a theatre clearance for some OCONUS locations. The contractor shall be required to prepare/obtain all necessary paperwork, documentation and/or permits that may be required for OCONUS locations as required in the country SOFA. All travel will be in accordance with the DoD Foreign Clearance Guide.

Travel of contractor personnel to OCONUS locations: TOs may require the utilization of Technical Expert (TE) personnel in CONUS and OCONUS locations. In the event that the TO requires OCONUS performance, the contractor shall comply with Army Regulations for OCONUS travel.

1.10 1.11 1.12 1.13 1.14

1.9.1 Secret Facility Clearance

The contractor shall be required to have a SECRET Facility Clearance with SECRET safeguarding requirements. The contractor shall require access to COMSEC information and Controlled Unclassified Information (CUI).

In performing this contract, the contractor may be required to receive and generate classified material, and fabricate, modify, or store classified hardware. The contractor may be required to have a COMSEC account. Contractor personnel performing IT sensitive duties are subject to investigative and assignment requirements IAW AR 25-2, Army Cybersecurity, AR 380-67, Personnel Security Program, and affiliated regulations.

1.9.2 Antiterrorism (AT) and Operational Security (OPSEC) requirements AT Level I Training: This provision/contract text is for contractor employees with an area of performance within a DoD controlled installation, facility, or area. All contractor employees, to include subcontractor employees, requiring access to DoD installations, facilities, and controlled access areas shall complete AT Level I awareness training within 30-calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable.

The contractor shall submit to the Contracting Officer Representative (COR) or to the Procuring Contracting Officer (PCO), if a COR is not assigned, certificates of completion for each affected contractor employee and subcontractor employee within 30-calendar days after completion of training by all employees and subcontractor personnel. AT level I awareness training is available at the following website: https://jko.jten.mil/courses/atl1/launch.html

1.9.3 AT Awareness Training for Contractor Personnel Traveling Overseas This training is required for making Government-provided Area of Responsibility (AOR) training available and capable of being received by U.S. based contractor employees and associated subcontractor employees. AOR-specific AT awareness training will be provided as directed by AR 525-13, Antiterrorism. Specific AOR training content is directed by the combatant commander with the unit Antiterrorism Officer (ATO) being the local point of contact.

1.9.4 Access and General Protection/Security Policy and Procedures This requirement is for contractor employees with an area of performance within a Military controlled installation, facility, or area. Contractor and all associated subcontractor employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by a Government representative). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements, as directed by DoD, Headquarters, Department of the Army (HQDA), and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes. Additional details for these efforts will be outline in each TO PWS.

1.9.5 iWATCH Training This training is for contractor employees with an area of performance within an Army controlled installation, facility, or area. The contractor and all associated subcontractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local developed training will be used to inform employees of the types of behavior to watch for, and instruct employees to report suspicious activity to the COR. This training shall be completed within 30-calendar days of contract award and within 30-calendar days of new employees commencing performance with the results reported to the COR NLT 30-calendar days after contract award. Website: https://www.mepcom.army.mil/Home/Contractors.aspx

1.9.6 Information Security (INFOSEC)

1.9.6.1 Handling of Classified information

TOs that Require Handling or Access to Classified Information. Contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential” or “Secret” and requires contractors to comply with the Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (NISPOM) (DoD 5220.22-M, Standard Data Wipe) and any revisions to DoD 5220.22-M, notice of which has been furnished to the contractor.

1.9.6 1.9.6.1

1.9.6.2 Project Manager Interoperability, Integration & Services (PM I2S) Security Classification Guide (SCG) The contractor shall comply with all information classification guidance prescribed in the PM I2S SCG. This requirement shall flow down to all subcontractors and vendors. The SCG may be viewed in a Government location upon request.

1.9.7 Operation Security (OPSEC) Standing Operating Procedure (SOP)/Plan The contractor shall submit a final OPSEC SOP/Plan within 90-calendar days of contract award, IAW Contract Data Requirements List (CDRL) A007 (Operations Security (OPSEC) Plan DI-MGMT-80943C), to be reviewed and approved by the responsible Government OPSEC officer, per AR 530-1, Operations Security. This SOP/Plan will include the Government's critical information, why it needs to be protected, where it is located, who is responsible for it, and how to protect it. In addition, the contractor shall identify an individual who will be an OPSEC Coordinator. The contractor shall ensure this individual becomes OPSEC Level II certified, per AR 530-1.

OPSEC Training. Per AR 530-1, Operations Security, new contractor employees must complete Level I OPSEC training within 30-calendar days of their reporting for duty. All contractor employees must complete annual OPSEC awareness training.

1.9.8 Information Assurance (IA)

1.9.6.2 1.9.7 1.9.8

1.9.8.1 Contractor Employees Who Require Access to Government Information Systems (IS) All contractor employees with access to a Government information system must be registered in the ATCTS (Army Training Certification Tracking System) at commencement of services, and must successfully complete the DoD Information Assurance Awareness prior to access to the IS and then annually thereafter. ATCTS Website: https://atc.us.army.mil/iastar/

1.9.8.2 Information Assurance (IA) / Information Technology (IT) Training All contractor employees and associated subcontractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoD 8570.01-M, Information Assurance Workforce Improvement Plan and AR 25-2, Army Cybersecurity within six (6) months of employment.

1.9.9 Information Assurance (IA) / Information Technology (IT) Certification Per DoD 8570.01-M, Defense Federal Acquisition Regulation Supplement (DFARS) 252.239.7001, Information Assurance Contractor Training and Certification and AR 25-2, the contractor employees supporting IA/IT functions shall be appropriately certified upon contract award. The baseline certification, as stipulated in DoD 8570.01-M, must be completed upon contract award.

1.9.10 Contractors Authorized to Accompany the Force

DFARS 252.225-7040, Contractor Personnel Authorized to Accompany U.S. Armed Forces Deployed Outside the United States is the governing source for this information. The clause shall be used in solicitations and contracts that authorize contractor personnel to accompany U.S. Armed Forces deployed outside the U.S. in contingency operations; humanitarian or peacekeeping operations; or other military operations or exercises, when designated by the combatant commander. The clause discusses the following AT/OPSEC related topics: required compliance with laws and regulations, pre-deployment requirements, required training (per combatant command guidance), and personnel data required.

1.9.11 Performance or Delivery in a Foreign Country

DFARS 252.225-7043, Antiterrorism/Force Protection for Defense Contractors Outside the US is the source documentation for this clause. The clause shall be used in solicitations and contracts that require performance or delivery in a foreign country. This clause applies to both contingency and non-contingency support. The key AT requirement is for non-local national contractor personnel to comply with theater clearance requirements and allow the combatant commander to exercise oversight to ensure the contractor’s compliance with combatant commander and subordinate task force commander policies and directives.

1.9.12 Handling or Access to Classified Information

The contractor shall comply with FAR 52.204-2, Security Requirements. This clause involves access to information classified “Confidential” or “Secret,” and requires contractors to comply with— (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); (2) any revisions to DoD 5220.22-M, notice of which has been furnished to the contractor.

1.9.13 Personnel Security (PERSEC)

For Contractors Authorized to Accompany the Force. DFARS 252.225-7040, Contractor Personnel Authorized to Accompany U.S. Armed Forces Deployed Outside the United States is the source documentation for these individuals. The clause shall be used in solicitations and contracts that authorize contractor personnel to accompany U.S. Armed Forces deployed outside the U.S. in contingency operations; humanitarian or peacekeeping operations; or other military operations or exercises, when designated by the combatant commander. The clause discusses the following AT/OPSEC related topics: required compliance with laws and regulations, pre-deployment requirements, required training (per combatant command guidance), and personnel data required.

For Contract Requiring Performance or Delivery in a Foreign Country, DFARS 252.225-7043, Antiterrorism/Force Protection for Defense Contractors Outside the US, is the information source. The clause shall be used in solicitations and contracts that require performance or delivery in a foreign country. This clause applies to both contingency and non-contingency support. The key AT requirement is for non-local national contractor personnel to comply with theater clearance requirements and allow the combatant commander to exercise oversight to ensure the contractor’s compliance with combatant commander and subordinate task force commander policies and directives.

1.10 Supply Chain Risk Management (SCRM)

This contract and its associated DO/BPO/TO orders are subject to the Federal SCRM policies and regulations, including the DFARS 252.239-7017 Notice of Supply Chain Risk, 252.239-7018 Supply Chain Risk, 252.246-7007, Contractor Counterfeit Electronic Part Detection and Avoidance System, DoD Instruction 5200.44 Protection of Mission Critical Functions to Achieve Trusted Systems and Networks, Section 806 of the FY2018 National Defense Authorization Act (NDAA) Requirements for Information Relating to Supply Chain Risk, and internal Defense Information Systems Agency (DISA) SCRM Processes and Procedures.

The contractor shall submit a SCRM Plan in accordance with (IAW) CDRL A008 (Supply Chain Risk Management Plan DI-MGMT-82256) to address, at a minimum, Supply Chain Security Controls, as specified in the DO/BPO/TO and described in the Committee on National Security Systems Instruction (CNSSI) 1253 Appendix D (companion publication to National Institute of Standards and Technology [NIST] Special Publication [SP]). The SCRM plan shall describe how the contractor will reduce and mitigate Supply Chain Risk using the security controls outlined below (further described in CNSSI 1253, Appendix D and NIST SP 800-53 Rev 5 dated September 2020 including updates as of 12-10-2020. Security and Privacy Controls for Information Systems and Organizations), as applicable to the CHS contract.

SUPPLY CHAIN RISK MANAGEMENT FAMILY

CONTROL NUMBER

CONTROL NAME

CONTROL ENHANCEMENT NAME

IMPLEMENTED BY

ASSURANCE

· A control or control enhancement that is typically implemented by an organization (i.e., by an individual through nontechnical means) is indicated by an “O” in the implemented by column.

· A control or control enhancement that can be implemented by an organization, a system, or a combination of the two is indicated by an “O/S.”

· A control or control enhancement marked with a “√” in the assurance column indicates the control or control enhancement contributes to the grounds for confidence that a security or privacy claim has been or will be achieved 1.9

1.10.1 SCRM Plan Update

The contractor shall provide an updated SCRM Plan to the COR and Program Manager within five (5) business days whenever there is a change that affects one (1) or more security controls as described in the CNSSI 1253 Appendix D (companion publication to NIST SP). At a minimum, the following events will require an SCRM Update: changes in company ownership, changes in senior company leadership, supplier changes, subcontractor changes, and Information and Communications Technology (ICT).

1.10.2 Program Protection/Technology Protection Support Requirements The Contractor shall provide technical support for the U.S. Government’s Program Protection Plan (PPP) process performed IAW DoDI 5200.39, DoDI 5200.44, AR 70-77 and DA PAM 70-3. The Contractor shall implement all protection measures via a Program Protection Implementation Plan IAW CDRL A001 (Program Protection Implementation Plan DI-ADMN-81306) to protect Critical Program Information (CPI) and critical components.

The tasks listed below shall be performed by the Contractor as described and shall flow down to any sub-contractors engaged by the Contractor:

1. The Contractor shall assist and support the U.S. Government in performing a Critical Functionality Analysis (CFA) on the system.

2. The Contractor shall assist and support the U.S. Government in performing a CPI assessment on the system. The CPI assessment is a structured approach to identify the “technical know-how” in the areas of Concept, Material, Design, Manufacturing, and Integration that enables the hardware and/or software elements to meet the threshold of CPI as defined in DoDI 5200.39. If CPI is identified, the U.S. Government shall prepare a PPP.

3. The U.S. Government shall provide the contractor with written guidance in reference to the implementation of countermeasures to protect CPI. The contractor shall provide a Program Protection Implementation Plan (PPIP) to the U.S. Government within 30 days of receiving countermeasures and provide periodic countermeasure and implementation status to PM via Contract Deliverables.

4. Applicable DFARS Clauses include: DFARS Subpart 204.73 – Safeguarding Unclassified Controlled Technical Information. This clause addresses general procedures; safeguarding controls and requirements; cyber incident and compromise reporting; and DoD damage assessment activities.

1.10.3 Contractor Counterfeit Electronic Part Detection and Avoidance System The contractor shall provide the Government with a counterfeit risk mitigation plan for electronic components IAW CDRL A002 (Counterfeit Prevention Plan (CPP) DI-MISC-81832). The contractor shall update the counterfeit risk mitigation plan to reflect both existing and new threats and vulnerabilities to the supply chain.

1.11 Assignment of Intellectual Property Rights

1.10 1.11

1.11.1 Data/Software License Rights

The Government's rights in non-commercial technical data and software deliverables will be governed by DFARS 252.227-7013 Rights in Technical Data – Non-commercial Items and DFARS 252.227-7014 Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, respectively. The Government's rights in commercial technical data will be governed by DFARS 252.227-7015 Technical Data – Commercial Items. Pursuant to the requirements set forth in DFARS 252.227-7017 Identification and Assertion of Use, Release, or Disclosure Restrictions, Offerors are required to specifically identify Data/Software Rights Assertions related to technical data and software deliverables. As indicated in DFARS 252.227-7017(e), an Offeror's failure to submit, complete, or sign the aforementioned Data and Software Rights Assertions with its offer may render the offer ineligible for award.

1.11.2 Commercial Software Licenses

The Government's rights in commercial software are governed by the licensor's commercial software license agreements (unless the license terms are inconsistent with federal procurement law or do not otherwise satisfy user needs). The Government will not accept any commercial software license terms that conflict with federal procurement law or that do not satisfy user needs. Commercial Software License terms that are unacceptable to the Government include, but are not limited to, indemnification provisions (and other types of provisions that include unauthorized or unbudgeted funding obligations), attorney's fees provisions, state or foreign choice of law/jurisdiction provisions, binding arbitration provisions, and injunctive relief provisions.

1.11.3 Initial Delivery Orders

For the initial Delivery Order, the Government will not award the initial Delivery Order, unless the corresponding commercial software license agreements, if any, are reviewed and approved by the PCO. Notwithstanding the initial Delivery Order under this contract, the Government will not award any TI/TO under this contract, unless the corresponding commercial software license agreements are reviewed and approved by the Contracting Officer.

2.0 Applicable Documents

Applicable documents are cited throughout this PWS and will be cited as necessary in the individual TO, DO or BPO. The most current version of documents at the time of the TO, DO or BPO issuance will take precedence.

1.0 2.0

3.0 Requirements

The contractor shall provide CommIT equipment through the processes defined in this PWS. In addition, the PWS defines the engineering support, configuration management, integrated logistics support, technical assistance and support services, program management, integrated data environment, safety, and quality assurance requirements for the contract.

3.1 Trade Agreements Act (TAA) and Foreign Ownership Control or Influence (FOCI) The contractor shall be responsible for ensuring equipment is TAA-compliant, and that FOCI concerns are addressed when equipment is procured from non-US owned companies.

3.2 Bonded Storage

Bonded storage is a secure building or warehouse, where goods are kept for processing before delivery. Bonded storage is required to be environmentally controlled when the TI explicitly states as such, or when the contractor should reasonably know that environmentally controlled storage is required for the item to ultimately be released from bonded storage in serviceable condition, with no defects or deficiencies caused by being held in storage. Environmentally controlled storage is defined as a physically secure location that can monitor and adjust the humidity and temperature, to avoid damaging sensitive electronic equipment and their components.

The contractor shall have the means to provide and make available via a TO or DO the utilization of a CONUS bonded storage IAW 19 CFR19, Customs Warehouses, Container Stations and Control or Merchandise Therein. Bonded goods shall have a maximum storage period of one (1) year. Release from bonded storage shall be executed via a signed DD Form 1149. Bonded storage will be a FFP CLIN available during the ordering process. Hardware items released from bonded storage shall be in serviceable condition, with no defects or deficiencies caused by being held in storage. Items stored in and released from bonded storage are NOT subject to customs duties, imports or exports.

3.3 Technology Insertion (TI)

A TI is defined as a modification or enhancement of products, or addition of CommIT products to incorporate technology advances, which increase the capabilities of the CHS portfolio, as these advances become available in the marketplace. As capabilities in CommIT mature, the contractor shall propose technology improvements at the request of PdL CHS. The steps below outline the general TI process for V1 products. When there are engineering design support requirements (V1+, V2, V3, Installation Kit (IK), and OTC), refer to PWS section 3.6 (a).

a) The customer defines the requirement(s)

b) Government releases draft Technical Specifications to the contractor

c) Government releases a request for proposal (RFP) to the contractor

d) The contractor provides the Government with a proposal

e) Government evaluates the proposal and has discussions, if necessary

f) Requirement is added to the CHS-6 contract The contractor shall provide the Government with a proposal NLT 10-business days after receipt of the RFP. The contractor shall also submit any documentation required IAW Paragraph 3.10 (Product Specifications) of this PWS, as applicable; as well as all warranty options.

3.3.1 Brand Name or Equal

This PWS allows for the usage of FAR 11.104 Use of Brand Name or Equal Purchase Description. An equal item is a product that meets the same salient physical, functional, and performance characteristics, as the specified brand name product. The functional characteristics shall include all salient technical specifications of the hardware and associated software (for example, the operating system).

3.3.2 Contract Pricing Structure

The Government reserves the right to direct the contractor to provide contract pricing for any number of years within the period of performance of the contract. This request will be a part of the technical specifications submitted to the contractor.

3.4 Delivery Order (DO)

A DO is defined as the means by which the Government will order hardware and/or associated software on the contract. Each DO will be considered a stand-alone delivery requirement. The contractor shall ship hardware and/or associated software procured, via the CHS-6 contract, to the delivery address on the DO with a signed DD Form 250.

The first date of delivery shall be known as the After Receipt of Order (ARO) date. The contractor shall provide the delivery schedule for each DO. This ARO date shall match the corresponding proposed ARO date that was submitted during the TI process. The contractor shall be contractually bound to meet this ARO date. If there are any delays, the contractor shall provide a letter to the Contracting Officer, upon discovery, stating the reason why there is a delay, and provide an updated ARO. If the delay is caused by the OEM/vendor, then this letter shall include a copy of the letter/statement from the OEM/vendor that provides the reason for delay to the contractor. The purchaser of the hardware will be notified of the delay, and will have the right to dispute the delay(s).

The contractor shall have the capability to meet or exceed a monthly minimum quantity of 5,000 hardware items during a 30-day period for all V1, V1+, V2, V3, OTC, and IK/SC/TC during normal operations.

The contractor shall have the capability to meet or exceed a monthly minimum quantity IAW DFARS 252.217-7001 by increasing the quantity of items or services and/or accelerate the rate of delivery called for under this contract by 20% within a 30-day for all V1, V1+, V2, V3, OTC, and IK/SC/TC during surge operations.

The contractor shall ensure that hardware items are ready for Government inspection and acceptance at the contractor’s facility within 10-calendar days of the contractor receiving them from the OEM. The contractor shall deliver all hardware to the contractual CONUS “Deliver to” destination NLT 10-calendar days after Government acceptance is formalized via the signed DD Form 250, or upon release from bonded storage via the signed DD Form 1149, at no additional cost to the Government. The contractor shall deliver all equipment to the contractual OCONUS destination at the Government’s request and at an additional cost to the Government. The additional cost shall be the cost of the shipment.

The Government reserves the right to request, and the contractor shall provide, discounted pricing for procurements above a quantity of 500 each. The Government may combine one or more DOs/BPOs to achieve quantities greater than 500, and the contractor shall provide discounted pricing for those instances.

The Government reserves the right to request to expedite any hardware purchased through the CHS-6 contract, in whole or part. The contractor will coordinate with the OEM and attempt to meet the Government’s request to expedite at no additional cost to the Government. However, the Government will pay for the cost to expedite shipping, if required.

The Government reserves the right to process DOs with a Government Purchase Card (GPC) IAW FAR 13.301. If a price reduction is available for the use of a GPC, the contractor shall provide the Government with the reduced pricing.

3.5 Basic Purchase Order (BPO)

A basic purchase order is defined as a limited scope procurement of hardware items, consisting of only V1 items; see Solicitation Attachment 0013 for further details. BPOs are those orders that do not require the following:

a) Configuration Management (CM)

b) CHS extended or pass-through warranties. Basic purchase procurements are restricted to the Original Equipment Manufacturers (OEM) warranty only

c) EOL management

d) Modifications, integration, kitting, assembly, and/or test activities

e) Follow-on procurements

f) Bonded storage

g) Items requiring an End User License Agreement (EULA), that is not already approved by the DoD (Ref PWS Sec 3.16) Simple elements of program management, including but not limited to order validation, budget authorization, status tracking, inspection of items and maintenance of records will be included with BPOs.

All items can have either a CHS or OEM part number(s) (P/N), depending on if the hardware is already available on the CHS contract (CHS P/N) or not (OEM P/N).

· CHS Part Numbers. The contractor shall utilize a CHS part number when an item(s) is listed in the CHS contract and eligible for the Basic Purchase classification (as identified during the TI process).

· OEM Part Numbers. The contractor shall utilize an OEM part number, when the item has not been listed on the CHS contract and which may be provided by the Government with its RFP. Current market pricing will be used for these hardware items.

The contractor shall ensure that hardware items purchased as a BPO are ready for Government inspection and acceptance within 5-business days of receipt from the OEM.

The Government reserves the right to process BPOs with a Government Purchase Card (GPC) IAW FAR 13.301. If a price reduction is available for the use of a GPC, the contractor shall provide the Government with the reduced pricing.

3.6 Task Orders (TO)

A TO is defined as the means by which the Government will augment or add a customer service(s) in support of hardware procured through the CHS program office. The TOs for services purchased on the CHS contract will vary depending on the size, scope, duration and complexity of the requirements. As such, the contractor must maintain the capability to provide customer services to include, but not limited to, the following:

a) Design and Engineering services applicable to:

i. V1+, V2, V3, IK, and OTC equipment that is productized (designed, engineered, produced, and/or tested) to meet government standards, as specified in Attachment 0002, CHS-6 PWS Appendix A Survivability Reliability and Verification

b) Trade Studies

c) Survivability Testing, IAW PWS 3.12

d) Technical Manual Development and Documentation, IAW PWS 3.8.2.8

e) Training Support, IAW PWS 3.8.2.8

f) Warranty Repairs (Extended IAW PWS 3.18, OOW/OTFWT IAW PWS 3.18.4 - 3.18.6)

g) Field Service Representative (FSR) Support, IAW PWS 3.8.2.8

h) Exercise Support, IAW PWS 3.8.2.8

i) Program Management Reviews for CHS customers, IAW PWS 3.8.2.7

The TO process consists of the following steps:

a) Government releases requirements to the contractor via RFP

b) NLT 10-business days after receipt of the RFP, the contractor shall provide the Government with a proposal

c) Government evaluates the proposal and negotiates with the contractor

d) TO is awarded via CHS-6 When directed by the Government for applicable TOs, the contractor shall perform a Component Failure Analysis (CFA) and subsequent Contractor Performance Inspection (CPI) assessment. The results of these assessments shall be documented in the requiring program office’s PPP. This requirement shall flow down to all subcontractors/vendors.

The contractor shall offer a controlled bonded storage for items procured via the contract upon request by the Government through a TO or DO; reference PWS Paragraph 3.2. Products may be placed into bonded storage for a period NTE 365 days. Hardware items released from bonded storage shall be in serviceable condition, with no defects or deficiencies from being held in storage.

The Government reserves the right to process TOs with a Government Purchase Card (GPC) IAW FAR 13.301.

For OTC suites and kitted solutions (including Transit Cases (TCs), Storage Cases (SCs), and IKs), the contractor shall only ship complete OTC suites or kitted solutions. The Government will not accept partial shipments of OTC suites or kitted solutions, unless otherwise directed via DO.

3.7 Configuration Changes

The configuration change process is used to update the technical specification of an item on contract that has not been previously ordered. In this case, the changes are applied and the CHS part number can be re-used. If an item was previously ordered, the CHS part number cannot be altered. A new CHS part number will need to be generated though the TI process, see PWS paragraph 3.3. The configuration change process is used for End-of-Sale (EOS) or product component obsolescence (for example, a Central Processing Unit [CPU] upgrade), or as requested by the Government. The recommended configuration change documentation provided by the contractor shall identify the item that is being changed and the component changes to that item.

The contractor shall identify a replacement item(s), if available, and provide the recommendation or a path forward to the Government. Upon review and acceptance of the recommendation, follow the steps in TI paragraph 3.3.

3.8 Hardware Requirements

The following paragraphs define the equipment…