17-T-0080_Solicitation_Amendment_2.docx
DOCX document 58 KB Posted
- Attached to
- Linux Cluster Federal contract opportunity
- Solicitation number
- N6893617T0080
About this file
17-T-0080 Solicitation Amendment 2
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 17-T-0080_Solicitation_Amendment_6.docx | DOCX document | |
| Industry_Q&A_4-4-17.docx | DOCX document | |
| 17-T-0080_Solicitation_Amendment_5.docx | DOCX document | |
| Q&A.docx | DOCX document | |
| 17-T-0080_Solicitation_Amendment_5.docx | DOCX document | |
| 17-T-0080_Solicitation_Amendment_3.docx | DOCX document | |
| Industry_Questions.docx | DOCX document | |
| SOW.docx | DOCX document | |
| Questions_from_Industry.docx | DOCX document | |
| 17-T-0080_Solicitation_Amendment.docx | DOCX document | |
| 17-T-0080_Solicitation.docx | DOCX document |
Show all 11
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
N68936-17-T-0080
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION C - DESCRIPTIONS AND SPECIFICATIONS
The following have been modified:
STATEMENT OF WORK
STATEMENT OF WORK
FOR
Linux Cluster 16 March 2017
1.0 BACKGROUND
The Naval Air Warfare Center Weapons Division (NAWCWD), China Lake requires the purchase of a Linux-based high performance computing (HPC) cluster computer to execute numerical analyses performed by multiple branches (including codes 476100D, 476200D, and 477400D) in the support of various US Navy and DoD weapons programs.
1.1 SCOPE OF WORK
Modeling and simulation and numerical analyses constitute a significant portion of weapon system research and development efforts. Examples of these numerical analysis efforts include computational fluid dynamics (CFD) analyses of the flowfields around missiles, computational heat transfer analyses of aero-heating and the power dissipation in electronics payloads, computational solid mechanics analyses of the stress and strain response of missile structural members, and detailed modeling of the combustion in rocket and ramjet motors. Completing these simulations requires significant computational resources such as large amounts of memory and fast processor speed. Parallelization (the use of multiple processor cores by one simulation) is typically used to make problems tractable and to greatly reduce the time required to obtain results.
In order to maintain and expand the capability currently at NAWCWD for performing these numerical simulations, a new Linux-based high performance computing cluster is required. This new cluster will utilize the latest advances in processor speed, networking speed, memory, and processing core count.
2.0 APPLICABLE DOCUMENTS
2.1. Clinger-Cohen Act:
The contractor shall conduct analysis of program/project needs, acquisition strategy and program artifacts to identify and capture specific factors required to satisfy the 11 elements of Clinger-Cohen Act (CCA) compliance listed in DODI 5000.02, Enclosure 1, Table 9. Using Microsoft Word, the contractor shall prepare a CCA compliance matrix following the organization and appearance of Table 11 with additional separate columns for the display of artifact: titles, date(s) of approval, page number(s), and paragraph or section number(s). The right-hand column shall include an embedded object permitting the reader to open unclassified artifacts. The column shall identify classified artifacts and shall describe approved classified channels for access of classified artifacts. The contractor shall support the program manager during CCA compliance review and assist in responding to reviewer comments if and when additional supporting information or revisions are required.
2.2. Software Development/Server Procurement:
Any tools developed that will be hosted by the Navy Marine Corps Intranet (NMCI) or run on NMCI workstations will be certified for NMCI and comply with NMCI policy. Additionally, any servers supporting this effort will be transitioned to meet the requirements of the current NAVAIR Server Consolidation effort.
2.3. Cybersecurity:
The contractor shall conduct investigation and analysis of acquisition program artifacts such as but not limited to Initial Capabilities Document (ICD), Capability Description Document (CDD), Capability Production Document (CPD), Navy urgent operational need (UON) and Marine Corps urgent universal need statement (UUNS), joint urgent operational needs (JUONs), threat assessments and acquisition strategies (AS). Knowledge gained from this analysis shall be used when developing the Cybersecurity Strategy (CS) needed to steer and inform the program’s development of a Security Plan (SP) in accordance with DoDI 8510.01, of 12 March 2014
As a minimum, hardware, firmware, software, documentation (data deliverables) and/or Information Technology (IT) services delivered by this contract shall be in compliance with the following References:
0. DoDI 8500.01 Cybersecurity, 14 March 2014
0. DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 12 March 2014, Incorporating Change 1, May 24, 2016.
0. Committee on National Security Systems Instruction 1253, “Security Categorization and Control Selection for National Security Systems,” March 27, 2014, as amended.
0. DoDD 8140.01, Cyberspace Workforce Management, 11 August 2015.
0. DoD 8570.01-M Information Assurance Workforce Improvement Program, 15 August 2004, Certified Current as of 10 November 2015.
The contractor shall conduct investigation and perform analysis including; criticality analysis, threat assessment and vulnerability assessments. All findings and recommendations shall be reported to the government in technical reviews and submitted as written reports or documents as listed in Contract Data Requirements Lists. The contractor shall support government efforts needed for Information systems (IS) (enclaves or major applications), Platform Information Technology (PIT) or PIT systems to successfully categorize the system, achieve favorable assessment for selection, implementation and testing of security controls and authorization (approval to operate) before use or interconnection in an operating environment in accordance with references (a), (b) and (c). This includes IT that is standalone and IT that is connected to other systems, networks or enclaves. Information systems (IS) (enclaves or major applications), Platform Information Technology (PIT) or PIT systems delivered prior to award of this contract but included in the performance of this contract may have been delivered in compliance with Department of Defense Information Assurance Certification and Accreditation Process (DIACAP) and as such shall require transition to Risk Management Framework cybersecurity compliance. Transition planning proposed or performed under this contract shall be in compliance with reference (b) Enclosure 8, Figure 2 and all hardware, firmware and software deliverables shall be capable of receiving Authorization to Operate in accordance with reference (b).
Information technology services shall only be performed by personnel who are qualified and certified in accordance with reference (d). Personnel proposed and/or used in the performance of this contract as certified personnel shall be limited to those whose specifically assigned duties and responsibilities require certification.
All IT procured on behalf of this contract shall meet all DoD/DON and NAVAIR cybersecurity polices. Failure to follow these policies will result in denied access to NMCI, One Net, Integrated Shipboard Network System (ISNS) and other DON, DoD and Joint Networks. These cybersecurity policies are standard across the Department and ensure cybersecurity compatibility and interoperability.
IT systems and or networks operated by contractors pursuant to a NAVAIR contract, regardless of the level of data processed, shall be operated in accordance with the NISPOM.
Approved contractor-owned equipment shall be permitted connections to NAVAIR/DoD networks in order to carry out the performance of this contract. All Contractor-owned hardware and/or software shall meet DoDI 8500.1 Cybersecurity (CS), is subject to validation scanning and must be approved by the NAVAIR site CS Manager prior to connection.
The following specific criteria must be met before the contractor can be connected to any DoD or NAVAIR network in support of this contract. Requirements include:
0. Network Vulnerability Scanning. NAVAIR Deputy CIO for Information Assurance maintains authorized auditing tools and shall provide for firewall/port scans, device discovery scan, vulnerability assessment, and other requirements as required to ensure secure interoperability with DoD networks. The contractor shall be responsible for the remediation of any equipment that fails these audits prior to the connection of the system to the networks; Results of approvals shall be documented via Memorandum of Agreement with the Facility Security officer and the Defense Security Service Representative for that contractor.
0. Extent of Validation Scanning. To prevent scanning of corporate assets, all such networks, equipment and connections shall be physically segregated from any government/contractor corporate networks that are not in direct support of DoD contracts.
0. Circuit Provisioning. Any circuit or connection between NAVAIR and/or DoD site and the contractor site shall be provisioned via the Defense information Security Agency and comply with CJCSI 6211.02D, Defense Information System Network (DISN): Policy and Responsibilities, 24 Jan 2012.
0. Servicing Systems from a Remote Contractor Site. Remote Access Service connections that allow off-station operation and/or administration of contractor owned systems, located at any NAVAIR facility or site, shall not be permitted, with the exception of those systems connecting to the Command via the Outreach Services identified in Section 6, Enterprise Architecture.
e. Memorandum of Agreement and Inter-connection Agreements. A Cybersecurity Memorandum of Agreement (MOA) between the contractor owning the equipment and AIR-7.2.6 shall be developed and signed before the equipment can be connected to NAVAIR networks. Failure to comply with the signed MOA shall be grounds for disconnection from the network.
The contractor shall support the program manager during CCA compliance review and assist in responding to reviewer comments if and when additional supporting information or revisions are required.
2.4. Enterprise Architecture:
1. Contractor Networks and Connections. Contractor-owned and operated networks are prohibited on any Naval Air Systems Command (NAVAIR) facility or site in support of this contract. The contractor may access non- government, external IP space via the NAVAIR-provided Virtual Private Network (VPN) Outreach service or NAVAIR CIO approved Internet Protocol (IP) service.
1. Architecture Compliance. The contractor shall ensure all IT solutions, including database solutions, comply with the appropriate NAE Enterprise Architecture, and are verified by the NAVAIR Enterprise Architect (AIR-7.2.3) prior to build out.
1. Disclosure of pre-existing networks, circuits or connections. Any and all networks, circuits or connections between the contractor and any NAVAIR site related to previous contracts shall be identified in the MOA. Failure to comply and subsequent discovery of an unregistered network, circuit or connection shall be grounds for immediate disconnection.
3.0 REQUIREMENT/SPECIFICATIONS
3.1 The contractor shall provide a plug-and-play Linux-based high performance computing cluster which meets the following specifications:
3.1.1 Head/Storage Node:
One (1) Head/Storage Node shall be provided, with the following specifications:
| Two (2) Intel Xeon E5-2690v4 processors (each with 14 cores, 2.6 GHz) |
| 256 GB DDR4 RAM, 2400 MHz, ECC Registered |
| Thirty-four (34) hard drives (each 6 TB, 7200 RPM), in RAID 6 configuration |
| Two (2) hard drives (each 2TB, 7200 RPM) |
| One (1) Mellanox ConnectX-4 Infiniband adapter card (EDR IB, 100 Gb/s, 100 GbE) |
| One (1) Mellanox ConnectX3 EN dual-port network interface card (10 GigE) |
3.1.2 Head/Graphics Node:
One (1) Head/Graphics Node shall be provided, with the following specifications:
| Two (2) Intel Xeon E5-2690v4 processors (each with 14 cores, 2.6 GHz) |
| 128 GB DDR4 RAM, 2400 MHz, ECC Registered |
| One (1) Nvidia GeForce TITAN X graphics processing unit (12 GB, 3584 CUDA cores) |
| Two (2) solid state hard drives (each 480 GB, SATA III) |
| One (1) Mellanox ConnectX-4 Infiniband adapter card (EDR IB, 100 Gb/s, 100 GbE) |
3.1.3 Compute Nodes:
Forty (40) Compute Nodes shall be provided, each with the following specifications:
| Two (2) Intel Xeon E5-2690v4 processors (each with 14 cores, 2.6 GHz) |
| 128 GB DDR4 RAM, 2400 MHz, ECC Registered |
| One (1) Mellanox ConnectX-4 Infiniband adapter card (EDR IB, 100 Gb/s, 100 GbE) |
3.1.4 High Memory Compute Nodes:
Four (4) High Memory Compute Nodes shall be provided, each with the following specifications:
| Two (2) Intel Xeon E5-2690v4 processors (each with 14 cores, 2.6 GHz) |
| 256 GB DDR4 RAM, 2400 MHz, ECC Registered |
| One (1) Mellanox ConnectX-4 Infiniband adapter card (EDR IB, 100 Gb/s, 100 GbE) |
3.1.5 Ethernet Network:
An Ethernet network connecting all cluster nodes shall be provided, with the following specifications:
| Two (2) Brocade ICX-6450-48 switches (each with 48 ports, upgraded to 10 GbE) |
| Cabling as necessary to connect switches and cluster nodes |
3.1.6 Infiniband Network:
An Infiniband network connecting all cluster nodes shall be provided, with the following specifications:
| Three (3) Mellanox Switch-IB switches (each with 36 ports, EDR, 100 Gb/s) |
| Mellanox EDR Infiniband QSFP passive copper cabling as necessary to connect switches and cluster nodes |
3.1.7 Rack and Power Distribution System:
A rack and power distribution system shall be provided, with the following specifications:
| Rack of sufficient size to hold all cluster components (e.g. nodes, switches) |
| Four (4) Eaton EMO107-10 power distribution units |
Uninterrupted power supply (UPS) system for Head/Storage and Head/Graphics nodes (only), providing minimum of 15 minutes backup power
| One (1) Environment (temperature, humidity) monitoring probe |
| Power cables as necessary to connect all cluster components to power distribution unit |
3.1.8 Software Compatibility:
Cluster shall have demonstrated compatibility (successful, multi-processor operation using the Infiniband network) with the following software packages:
| Star-CCM+ v. 10+ |
| Abaqus |
| ANSYS v. 17 and v. 18 |
CTH v. 10 Sierra Systems v. 4 ALE3D v. 4 SHAMRC v. 8 Intel compiler 2017 (C, C++, Fortran, MPI Libraries) Cheetah v. 8 Gaussian v. 16
3.2 The contractor shall provide, install, and configure a Linux operating system on all cluster nodes, in accordance with the following specifications:
Red Hat Enterprise Linux Server Entry Level (Head/Storage Node and Head/Graphics Node), 1 Year license Red Hat Enterprise Linux Server for HPC (all Compute Nodes), 1 Year license Torque Maui Ganglia Software and/or scripts for cluster management and node provisioning
4.0 DELIVERY
4.1 Delivery
The high performance computing cluster shall be delivered within 3 months after date of award to:
Commander, NAWCWD Attn: Ephraim Washburn, Code 477400D Building 01371 China Lake, CA 93555
5.0 MISCELLANEOUS
5.1 Warranty
The contractor shall provide a standard, extended commercial warranty (3 year parts replacement warranty).
SECTION J - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACHMENTS
The following have been added by full text:
ATTACHMENTS
| DOCUMENT TYPE | DESCRIPTION | PAGES | DATE |
| Attachment 1* | Answers to Industry Questions | 3 | 3/16/2017 |
*Sent under separate cover
(End of Summary of Changes) image1.wmf
File details come from the government source that posted it. Updated .