A01 - PWS Attachment 0001 CHS-5 PWS (dated 19 Jun 2018).docx

PERFORMANCE WORK STATEMENT

FOR

COMMON HARDWARE SYSTEMS AND SERVICES

SOLICITATION NUMBER: W15P7T-17-R-0008

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

ABERDEEN PROVING GROUND, MD, 21005

Version 3

19 June 2018

PROGRAM EXECUTIVE OFFICE

COMMAND, CONTROL, COMMUNICATIONS – TACTICAL

PERFORMANCE WORK STATEMENT FOR

COMMON HARDWARE SYSTEMS AND SERVICES

iii

PROCUREMENT SENSITIVE

FOR OFFICIAL USE ONLY

PART 1: GENERAL INFORMATION

1.0 Scope

1.0.1 Common Hardware Systems – 5th Generation (CHS-5) is an Indefinite Delivery Indefinite Quantity (IDIQ) contract for the rapid procurement of total life cycle system management solutions in support of Army, Department of Defense (DoD), and Federal Government programs and agencies. CHS-5 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 tactical / operational requirements. The contractor shall perform to the standards in this Performance Work Statement (PWS).

1.0.2 This PWS establishes the requirements for contractor-provided equipment and services to include technology insertion (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 tactical programs while lowering life cycle costs through standardization of battlefield Command and Control (C2), leveraging centralized buys of CommIT products.

1.1 General Information

1.1.1 PdL CHS supports Army and other DoD 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 commercial technology solutions to be integrated for tactical or operational use, including integration with the Army’s tactical network. The product office implements CommIT acquisition strategies for programs through seamless and consolidated procurement, support to programs’ sustainment strategies, and technology upgrades to meet programs’ cost, schedule, and performance requirements. PdL CHS provides this cross-cutting capability allowing individual programs to garner efficiencies through streamlined common hardware configurations while supporting broader Army goals and initiatives. The 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. PdL CHS manages a portfolio of C5ISR solutions including, but not limited to, servers, storages, clients, networking devices, ruggedized platforms, hand-held end devices, operational transit cases (OTCs) and peripheral devices that are environmentally tested to 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 Army and other DoD programs meet their tactical requirements.

1.2 Order Type

1.2.1 This is an IDIQ contract with Delivery Orders (DO) for hardware issued as Firm Fixed Price (FFP) or Fixed Price Incentive (FPI) requirements. Task Orders (TO) for services will be either FFP, and/or Cost Plus Fixed Fee (CPFF) (Completion or Term), and/or Cost.

1.3 Period of Performance (PoP) / Place of Performance

1.3.1 The proposed CHS-5 IDIQ contract will have an ordering period of five (5) years, inclusive of a three (3) year base period of performance, along with two (2) one-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 PoP.

1.3.2 The contractor is required to provide world-wide warranty support to hardware sold on the contract. The contractor may be required to provide support to contingency operations Outside the Contiguous United States (OCONUS) to include, but not limited to, Iraq, Afghanistan and Korea as per specific TO requirements. The contractor may be required to provide support to OCONUS locations for the delivery of hardware as per DO requirements.

1.3.3 Technical Expert Status Accreditation (TESA)

1.3.3.0 This contract requires the utilization of Technical Expert (TE) personnel and/or Troop Care (TC) in accordance with (IAW) AER 715-9; the Government will obtain approval by applicable OCONUS authorities for accreditation of employees to fill contract Technical Expert Status Accreditation (TESA) or TC positions.

1.3.3.1 The contractor shall ensure all contract personnel have their TESA applications and resumes approved by the DoD Contractor Personnel Office (DOCPER). Accredited Technical Experts will be authorized to use Government facilities in accordance with TESA policies.

1.3.3.2 A Letter of Instruction (LOI) will be provided by the Government for contractors traveling to Germany, Korea, and other OCONUS locations, as appropriate.

1.3.3.3 Letters of Authorization (LOAs) will be provided by the Government, as appropriate.

1.3.4 The Status of Forces Agreement (SOFA)

1.3.4.0 The contractor shall abide by all SOFA agreements for all OCONUS locations.

1.3.4.1 Specific details will be included in the TO PWS.

1.3.5 Synchronized Pre-Deployment and Operational Tracker (SPOT)

1.3.5.0 Any contractor-required OCONUS travel must be processed through the Synchronized Pre-Deployment and Operational Tracker (SPOT) website or the current process at time of OCONUS travel.

1.3.6 Theater Business Clearance

1.3.6.0 A Theater Business Clearance (TBC) must be approved by the Government prior to travel to a Theater of Operation.

1.4 Contract Management

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

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

1.5.1 The Government may furnish equipment to the contractor for integration on specific DOs/TOs as required. 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 DO/TO.

1.6 Contractor Furnished Equipment (CFE)/Materials

1.6.1 The contractor shall be required to 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.7 Inspections and Acceptance

1.7.1 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 for specific tasks within the PWS.

1.7.2 Material inspection, receiving, and acceptance will be reported on DD Form 250.

1.8 Security

1.8.1 The security requirements are defined in the attached DD Form 254, Contract Security Classification Specification. All facility clearance sponsorships for subcontractors must have Government approval and certification on subcontractors DD Form 254. The Government will provide a DD Form 254 with each TO.

1.8.2 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, such as TESA or Visas, if required. All travel will be in accordance with the DoD Foreign Clearance Guide. Section H of the contract contains further requirements regarding travel. Exceptions for the use of Premium-class travel must be approved in writing by the Procuring Contracting Officer (PCO) or Contracting Officer’s Representative (COR) (if delegated to the COR by the PCO) prior to the departure of travel.

1.8.3 Travel of contractor personnel to OCONUS locations: TOs may require the utilization of TE personnel in the Contiguous United States (CONUS) and OCONUS locations. The contractor must comply with Army Regulations for OCONUS travel in the event that the TO requires OCONUS performance.

1.8.4 Secret Facility Clearance

1.8.4.0 The contractor shall be required to have a SECRET Facility Clearance with SECRET safeguarding requirements. The contractor shall require access to COMSEC information and For Official Use Only (FOUO) information.

1.8.4.1 In performing this contract, the contractor may be required to receive and generate classified material, 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, AR 380-67 and affiliated regulations.

1.8.5 Antiterrorism (AT) and Operational Security (OPSEC) requirements

1.8.5.0 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 COR or to the contracting officer, 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://atlevel1.dtic.mil/at.

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

1.8.5.1 Access and General Protection/Security Policy and Procedures: This standard language text is for contractor employees with an area of performance within an Army controlled installation, facility or area. Contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by 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. The Government will provide an AT/OPSEC review cover sheet with each TO.

1.8.5.2 iWATCH Training: This standard language is for contractor employees with an area of performance within an Army controlled installation, facility or area. The contractor and all associated sub-contractors 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.

http://www.myarmyonesource.com/familyprogramsandservices/iwatchprogram/default.aspx

1.8.5.3 Contractor Employees Who Require Access to Government Information Systems (IS): All contractor employees with access to a Government info 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.

1.8.5.4 Information Security (INFOSEC)

1.8.5.4.1 Access and General Protection/Security Policy and Procedures: This standard language text is for contractor employees with an area of performance within an Army controlled installation, facility or area. Contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by 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, 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.

1.8.5.4.2 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— (1) The Security Agreement (DD Form 441), including the National Industrial Security Program Operating Manual (DoD 5220.22-M); any revisions to DoD 5220.22-M, notice of which has been furnished to the contractor.

1.8.5.4.3 Project Lead (PL) Network Enablers (Net E) Security Classification Guide (SCG): The prime contractor shall comply with all information classification guidance prescribed in the PL Net E SCG. This requirement shall flow down to all subcontractors. The SCG may be viewed in a Government location upon request.

1.8.5.5 OPSEC Standing Operating Procedure/Plan: The contractor shall develop an OPSEC Standing Operating Procedure (SOP)/Plan within 90 calendar days of contract award, 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 will ensure this individual becomes OPSEC Level II certified per AR 530-1.

1.8.5.5.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.8.5.6 Information Assurance (IA)

1.8.5.6.1 Contractor Employees Who Require Access to Government Information Systems: All contractor employees with access to a Government info 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.

1.8.5.6.2 For Information Assurance (IA) / Information Technology (IT) Training: All contractor employees and associated sub-contractor 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 Armytraining requirements in DoD 8570.01, DoD 8570.01-M and AR 25-2 within six months of employment.

1.8.5.6.3 For Information Assurance (IA)/Information Technology (IT) Certification: Per DoD 8570.01-M , DFARS 252.239.7001 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.8.5.7 Contractors Authorized to Accompany the Force: DFARS Clause 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 US Armed Forces deployed outside the US 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.8.5.8 Performance or Delivery in a Foreign Country: DFARS Clause 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 allows the combatant commander to exercise oversight to ensure the contractor’s compliance with combatant commander and subordinate task force commander policies and directives.

1.8.5.9 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.8.5.10 Personnel Security (PERSEC)

1.8.5.10.1 For Contractors Authorized to Accompany the Force: DFARS Clause 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 US Armed Forces deployed outside the US 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.8.5.10.2 For Contract Requiring Performance or Delivery in a Foreign Country, DFARS Clause 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 allows the combatant commander to exercise oversight to ensure the contractor’s compliance with combatant commander and subordinate task force commander policies and directives.

1.8.6 Program Protection/Technology Protection Support Requirements. The prime contractor(s) shall support all Program Protection Plan (PPP) activities. These activities include, but are not limited to: Supply Chain Risk Management (SCRM), Critical Functionality Analysis (CFA) of critical components, Critical Program Information (CPI) Assessment, and implementation of all protection measures via a Program Protection Implementation Plan IAW CDRL A001 as per TO to protect CPI and critical components. This requirement shall flow down to all subcontractors.

1.9 Assignment of Intellectual Property Rights

1.9.1 Data/Software License Rights

1.9.1.0 The Government's rights in non-commercial technical data and software deliverables will be governed by DFARS 252.227-7013 and DFARS 252.227-7014, respectively. The Government's rights in commercial technical data will be governed by DFARS 252.227-7015. Pursuant to the requirements set forth in DFARS 252.227-7017, 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.9.2 Commercial Software Licenses

1.9.2.0 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 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 provision, state or foreign choice of law/jurisdiction provisions, binding arbitration provisions, and injunctive relief provisions.

1.9.3 Delivery Orders

1.9.3.0 For Delivery Order 0001 of this contract, the Government will not award this contract unless the corresponding commercial software license agreements are reviewed and approved by the Contracting Officer. Notwithstanding Delivery Order 0001 under this contract, the Government will not award any DO/TO under this contract unless the corresponding commercial software license agreements are reviewed and approved by the Contracting Officer.

PART 2: APPLICABLE DOCUMENTS

2.0 Applicable Documents

PART 3: REQUIREMENTS

3.0 Requirements

3.0.1 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 Technology Insertions

3.1.1 TI is defined as modification or enhancement of CHS-5 products, or addition of CommIT products to incorporate technology advances which increase the capabilities of the CHS-5 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 TI process begins at Step (a) for items having engineering and design requirements. The TI process begins at Step (d) for items not having engineering and design requirements:

a) Government releases requirements to the contractor.

b) The contractor shall perform any required engineering and design in collaboration with the Government as defined in Paragraph 3.4.6 of this PWS.

c) The contractor shall submit proposed design solution to the Government.

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

e) The contractor shall provide the Government with a proposal NLT 14 calendar days after receipt of the RFP. The contractor shall also submit any documentation required IAW Paragraph 3.4.4 of this PWS, as applicable.

f) Government evaluates and has discussions, if necessary, with the contractor.

g) Requirement is added to the CHS-5 contract.

3.2 Delivery Orders

3.2.1.0 DOs are the means by which the Government will order hardware on this IDIQ contract. Each DO will be considered a stand-alone delivery requirement and shall meet the schedule in Table 1 below.

3.2.1.1 DELETED.

3.2.1.2 The contractor shall ship hardware procured via the CHS-5 contract (with a signed DD250 or upon release from bonded storage via the signed DD 1149) according to the following timeline for each CHS-5 hardware version after receipt of signed DO; hardware versions are defined in Paragraph 3.4.2:

Table 1: Maximum Period (Calendar Days) to Serialize, Process, and Ship Equipment After Receipt of Each Order

(+120 days for FAT Plan & Procedures, +90 days for FAT Execution, and +Days ARO) Initial Delivery for each Subsequent New Configuration Item (+90 days for FAT Execution and +Days ARO) Days ARO (FAT Completed or Not Required)

OTC (Testing Not Required)

IK / SC / TC (Stand-Alone Delivery)

3.2.1.3 The contractor shall deliver all hardware to the contractual CONUS “Deliver to” destination NLT 14 calendar days after Government acceptance formalized via the signed DD250 or upon release from bonded storage via the signed DD 1149. Refer to Table 1 for the maximum allowable number of calendar days to serialize, process, and ship equipment after receipt of signed DO.

3.2.1.4 The contractor shall deliver all equipment to the contractual OCONUS destination at the Government’s request and at additional cost to the Government.

3.2.1.5 Table 1 reflects the minimum acceptable requirement to ship hardware in accordance with the contract. Offerors are permitted to propose alternative timeframes that exceed the minimum schedule requirement.

3.2.1.6 The contractor shall meet or exceed a minimum total monthly throughput capability of 5,000 production units during normal operations. The contractor shall be prepared to meet or exceed a minimum total monthly throughput of 10,000 production units during surge operations. Table 2 depicts the maximum monthly throughput for normal and surge operations by hardware version.

Table 2: Maximum Monthly Throughput – Serialize, Process, and Ship After Receipt of Each Order – during Normal and Surge Operations

(Normal Operations by Hardware Version) Maximum Monthly Throughput (Surge Operations by Hardware Version)

(*) The contractor shall enter the maximum monthly throughput at contractor’s facility for serialization, processing and shipment within ARO period for each Hardware Version, after receipt of each DO and after FAT is completed or not required. The minimum total monthly throughput during normal operations shall meet or exceed 5,000 production units.

(#) The contractor shall enter the maximum monthly throughput at contractor’s facility for serialization, processing and shipment within ARO period for each Hardware Version, after receipt of each DO and after FAT is completed or not required. The minimum total monthly throughput during surge operations shall meet or exceed 10,000 production units.

3.3 Configuration Changes

3.3.1.0 The configuration change process will be used for End of Sale (EOS) or product component obsolescence (for example, a CPU upgrade) or as requested by the Government. The configuration change documentation shall identify the item that is being changed and the component changes to that item.

3.3.1.1 A new or revised Product Specification shall be submitted with the Configuration Change proposal.

3.3.1.2 The Configuration Change process begins at Step (a) for items having engineering and design requirements. The Configuration Change process begins at Step (d) for items not having engineering and design requirements:

a) Government releases requirements to the contractor.

b) The contractor shall perform any required engineering and design in collaboration with the Government as defined in Paragraph 3.4.6 of this PWS.

c) The contractor shall submit proposed design solution to the Government.

d) Government releases a RFP to the contractor.

e) The contractor shall provide the Government with a proposal NLT 14 calendar days after receipt of the RFP.

f) Government evaluates and has discussions, if necessary, with the contractor.

g) Requirement is added to the CHS-5 contract.

3.4 Hardware Requirements

3.4.1 The following paragraphs define the equipment versions as well as the requirements for program management for the IDIQ base and services to be delivered. A separate listing of product categories and corresponding definitions is provided in Attachment 0006 (CHS-5 Pricing Spreadsheet and Instructions).

3.4.2 Hardware Version Definition

3.4.2.0 The following paragraphs describe the equipment versions on CHS-5.

3.4.2.1 V1 Equipment

3.4.2.1.1 V1 equipment is any commercially available hardware with attached warranty options, configuration management, and EOL management and not certified by the Government on the CHS-5 contract to the V1+, V2, or V3 standards found in Attachment 0002 [CHS-5 PWS Appendix A (Survivability, Reliability, Verification)].

3.4.2.2 V1+ Equipment

3.4.2.2.1 V1+ equipment (with configuration management, EOL management, and any selected warranty options) is productized (designed, engineered, produced, and tested) to meet Government standards as specified in Attachment 0002 [CHS-5 PWS Appendix A (Survivability, Reliability, Verification)].

3.4.2.3 V2 Equipment

3.4.2.3.1 V2 equipment (with configuration management, EOL management, and any selected warranty options) is productized (designed, engineered, produced, and tested) to meet Government standards as specified in Attachment 0002 [CHS-5 PWS Appendix A (Survivability, Reliability, Verification)].

3.4.2.4 V3 Equipment

3.4.2.4.1 V3 equipment (with configuration management, EOL management, and any selected warranty options) is productized (designed, engineered, produced, and tested) to meet Government standards as specified in Attachment 0002 [CHS-5 PWS Appendix A (Survivability, Reliability, Verification)].

3.4.2.5 Operational Transit Case

3.4.2.5.1 OTCs (to include low, medium, or high complexity) are durable, ruggedized, stackable, mobile transportation cases containing a selection of integrated hardware designed to be fully operational according to Government-provided system specifications. OTCs include configuration management, EOL management, and any selected warranty options. OTCs are productized (designed, engineered, produced, and tested) to meet Government standards as specified in Attachment 0002 [CHS-5 PWS Appendix A (Survivability, Reliability, Verification)] and Table 3 below. A low complexity OTC is defined as an OTC labeled and integrated with one (1) item and cabling harness, a medium complexity OTC is defined as an OTC labeled and integrated with two (2) items and cabling harness, and a high complexity OTC is defined as an OTC labeled and integrated with three (3) or more items and cabling harness. Examples of integrated items include routers, switches, firewall, media converters, servers, uninterruptible power supplies (UPS), power converters and conditioners (PCC), communications equipment, appliances, redundant array of independent disks (RAID), and workstations. OTCs may include, but are not limited to, the following integrated components:

a) 19” standard EIA equipment rack (of varying depths)

b) Shock isolation system to support and protect functional payload

c) Front and rear covers with storage pouches and lid hangers

d) Handles necessary to support lifting requirements

e) Cabling and wiring harnesses

f) Signal entry panels

g) Power entry panels

h) Power components

i) Grounding components

j) Removable rack mount

k) Installation and mounting kits

3.4.2.5.2 The contractor shall ensure OTCs comply with TEMPEST requirements when required by the Government.

3.4.2.5.2.1 OTC cables and/or cable labels and SEPs shall be color-coded per CNSSAM TEMPEST/1-13 when required by the Government.

3.4.2.5.2.2 Parallel cables shall be separated in compliance with the requirements of CNSSAM TEMPEST/1-13 to the maximum extent practicable within the confines of an OTC.

Table 3: Military Standards and Field Manual References for OTC Configurations

3.4.2.6 Installation Kit

3.4.2.6.1 An Installation Kit (IK) is a productized (designed, engineered, produced, and tested) item designed to allow system integrators to deploy CHS V1, V1+, V2, or V3 hardware onto or into deployable systems. IKs also include configuration management, EOL management, and any selected warranty options.

3.4.2.6.2 IKs allow transport and operation of equipment in shelters, wheeled and tracked vehicles. When affixed to the particular item it is designed for, the IK does not significantly increase the physical dimensions of the equipment (i.e.: a 19” rack mountable item of equipment must still fit into a 19” rack).

3.4.2.6.3 IKs may be required for V1+, V2, and V3 equipment to allow for the operation of the V1+, V2, and V3 equipment in wheeled or tracked vehicles as defined in Attachment 0002 [CHS-5 PWS Appendix A (Survivability, Reliability, Verification)], Table A-1 – Vibration. IKs provide the interface between the equipment and the mounting point.

3.4.2.7 Transit Case and Storage Case

3.4.2.7.1 Transit Cases (TC) and Storage Cases (SC) are made of lightweight composite materials and have high-impact absorbing qualities to provide equipment protection, including custom foam inserts.

3.4.2.7.2 TCs and SCs are used for transport and storage of integrated components, accessories, computers, printers, and other commercial IT hardware.

3.4.2.7.3 TCs and SCs include handles which are necessary to support lifting requirements.

3.4.2.7.4 TCs and SCs allow for stacking and have an interlocking rib feature to allow securing of additional stacked TCs and SCs.

3.4.2.7.5 TCs and SCs have seals (gaskets) on the covers and cases to withstand the effects of the harshest environments, they are water tight, and they contain an automatic air pressure relief valve.

3.4.2.7.6 TCs and SCs may be unpopulated or populated with items.

3.4.2.7.7 TCs may be employed in testing in accordance with the FAT paragraph of this PWS.

3.4.2.8 Brand Name or Equal

3.4.2.8.1 This PWS contains equipment identified as a brand name or equal item. An equal item is a product that meets the 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.4.2.9 Trade Agreements Act (TAA) and Foreign Ownership Control or Influence (FOCI)

3.4.2.9.1 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.4.2.9.2 In specific situations where the Government makes equipment selection, then the Government is primarily responsible for providing documentation stating that the equipment selection is TAA-compliant and has FOCI clearance. If the Government does not supply the needed documentation pertaining to TAA compliance, then the contractor shall be allowed to either reject the equipment selection or take responsibility for ensuring compliance.

3.4.3 Survivability Requirements for V1+, V2, V3, OTCs

3.4.3.0 The survivability requirements for V1+, V2, V3, and OTCs are specified in Attachment 0002 [CHS-5 PWS Appendix A (Survivability, Reliability, Verification)].

3.4.4 Product Specifications

3.4.4.0.1 The contractor shall prepare and deliver product specifications for each V1 and storage case item added to the CHS-5 contract and newly configured items that are the result of configuration changes.

3.4.4.0.2 The contractor shall prepare and deliver product specifications for each V1+, V2, V3, IK, and OTC item.

3.4.4.0.3 Technical Data Package (TDP) requirements are addressed in PWS Paragraph 3.4.6, Design and Integration Support.

3.4.4.0.4 The contractor shall prepare and deliver User Guides for CHS items.

3.4.5 Part Number

3.4.5.0.1 Each part number shall identify a unique CI and shall not be tied to a specific warranty option. The contractor shall maintain a warranty database to track the warranty options of each item sold using the item serial number.

3.4.5.0.2 IAW Paragraph 3.6.4.1.1 the contractor shall mark each item delivered under the CHS-5 contract with a label. By exception, at the Government’s discretion an item may not require a label; this exception will be communicated via a TI or DO.

3.4.6 Design and Integration Support

3.4.6.0.1 The contractor shall provide support to review tactical hardware requirements, environmental requirements, develop hardware test plans, Preliminary Design Review (PDR), Critical Design Review (CDR), perform power analyses, create interconnect and wiring configurations, and engineering for integration for CommIT products.

3.4.6.0.2 The most significant design work will be performed for V2, V3, and OTC products. Design work for Integrated V1 solutions, V1+, IKs, transit cases, and storage cases is required, but is not anticipated to be as comprehensive as the V2, V3, and OTC products. Design work shall apply the Human Engineering requirements of MIL-STD-1472G and MIL-HDBK-46855 Notice 1, and Safety requirements contained within Paragraph 3.10 of this PWS.

3.4.6.0.3 The contractor shall support reviews of documentation, hardware and transit case designs by developing and providing documentation, drawings, designs, interface control drawings, vendor parts list, and rough order of magnitude (ROM) costing to the Government for evaluation and consideration prior to the TI or configuration change.

3.4.6.0.4 The contractor shall support the proof of concept designs through PDR and CDR documentation and pre-production units of integrated hardware to support V1+, V2, V3, OTC, and transit case kit products.

3.4.6.0.5 The contractor shall accommodate a site visit by Government personnel or authorized representative in conjunction with PDR and CDR activities, if required by the Government.

3.4.6.0.6 The contractor shall maintain configuration management and specifications for these products, designs and pre-production units to meet tactical requirements, including maintaining parts lists (with OEM / vendor part numbers).

3.4.6.0.7 The contractor shall provide a Developmental Level TDP proposal when required by the Government via applicable TI; the contractor shall deliver the Developmental Level TDP in conjunction with the initial DO for the corresponding CI. Any Government requirements for a Production Level TDP will be accomplished via TO after a CI has been added to the contract. MIL-STD-31000A defines the various TDP levels that may be required: Developmental and Production.

3.4.6.0.7.1 Developmental Level TDPs shall be prepared and delivered IAW CDRL C005:

3.4.6.0.7.1.1 Developmental Design Drawings / Models

3.4.6.0.7.1.2 OEM & Prime Vendor Parts Lists – Subassembly Level

3.4.6.0.7.1.3 Data Lists – Subassembly Level

3.4.6.0.7.1.4 Index Lists – Subassembly Level

3.4.6.0.7.1.5 Wiring Lists – Subassembly Level

3.4.6.0.7.1.6 Power Analysis

3.4.6.0.7.2 Production Level TDPs shall be prepared and delivered IAW CDRL C006:

3.4.6.0.7.2.1 Product Drawings / Models

3.4.6.0.7.2.2 OEM & Prime Vendor Parts Lists – Component Level

3.4.6.0.7.2.3 Data Lists – Component Level

3.4.6.0.7.2.4 Index Lists – Component Level

3.4.6.0.7.2.5 Wiring Lists – Component Level

3.4.6.0.7.2.6 Power Analysis

3.4.6.0.7.2.7 Special Inspection Equipment Drawings, Models, and Associated Lists

3.4.6.0.7.2.8 Special Tooling Drawings, Models, and Associated Lists

3.4.6.0.7.2.9 Special Packaging Instructions Drawings, Models, and Associated Lists

3.4.6.0.8 Integration and design shall support U.S. Army supportability requirements and facilitate lifecycle cost savings in any of the primary integrated logistics support elements

3.4.7 Verification

3.4.7.0.1 Verification requirements shall adhere to the following paragraphs; detailed requirements are provided in Attachment 0002 [CHS-5 PWS Appendix A (Survivability, Reliability, Verification)].

3.4.7.1 Contractor Counterfeit Electronic Part Detection and Avoidance System

3.4.7.1.1 The contractor shall provide the Government with a counterfeit risk mitigation for electronic components IAW CDRL A002.

3.4.7.2 First Article Testing

3.4.7.2.1 V1+, V2, and V3: The contractor shall perform FAT once for each V1+, V2, and V3 CI as specified in Attachment 0002 [CHS-5 PWS Appendix A (Survivability, Reliability, Verification)] to verify that the CHS-5 items satisfy all requirements of this PWS and the product specifications. Any V1+, V2 or V3 items added as a result of a configuration change shall undergo FAT unless specified otherwise in the accepted configuration change. FAT will consist of hardware-specific survivability and reliability verification (visual, mechanical and electrical). In the interest of reducing the test schedule, it is acceptable to subject multiple units into FAT to perform the various tests simultaneously.

3.4.7.2.2 V1 and SC: V1 and SC items are not required to have a FAT performed.

3.4.7.2.3 IK and TCs: IKs and TCs are not required to undergo their own FAT, but will be employed for the FAT of…