W912DY18R0025__0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to:

1. Correct the language in Instructions to Offerors, Secton L.5.2 Page Limitation from "Three Client Complete PPQ’s" to "Five Client Complete PPQ’s"

2. Correct language in the SOW, Section 2.1 from "five DSRCs" to "four DSRCs"

3. All other terms and conditions remain unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 12

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

16C. DATE SIGNED

BY 31-Jul-2018

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W912DY18R0025

X 9B. DATED (SEE ITEM 11)

27-Jul-2018

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

31-Jul-2018

CODE

US ARMY ENGINEERING & SUPPORT CENTER

HUNTSVILLE ENGINEERING & SUPPORT CENTER

P.O. BOX 1600

HUNTSVILLE AL 35807-4301

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

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

W912DY18R0025

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been modified:

SECTION C

STATEMENT OF WORK

TECHNOLOGY INSERTION BASIC ORDERING AGREEMENT 2018

July 5, 2018

It is the Government’s intent to award Technology Insertion Basic Ordering Agreements under North American

Industry Classification System (NAICS) code 334111.

1.0 OBJECTIVE.

The primary objective of this Basic Ordering Agreement (BOA) is to provide the High Performance Computing

Modernization Program (HPCMP) with world-class high performance computing capabilities for the United

States Department of Defense (DOD). The BOA holders will be responsible for providing the Government with balanced, commercially- available, production-grade High Performance Computing (HPC) systems, which contain an appropriate combination of processor, memory, disk Input/Output (I/O), interconnect, and Operating

System (OS) capabilities in order to conduct complex, tightly-coupled, large-scale, scientific calculations.

2.0 DESCRIPTION

2.1 Locations.

Requirements for each order will be located primarily at the following four DSRCs and will encompass the unique requirements of each center:

U.S. Navy DSRC, John C. Stennis Space Center, Mississippi

U.S. Army Corps of Engineers, Engineer Research and Development Center (ERDC) DSRC, Vicksburg, Mississippi

Air Force Research Laboratory (AFRL) DSRC, Wright-Patterson Air Force Base, Ohio

Army Research Laboratory (ARL) DSRC, Aberdeen Proving Ground, Maryland

2.2 System Manufacturing Capabilities.

To satisfactorily complete the work, the contractor, who must be an Original Equipment Manufacturer (OEM), must have expert knowledge of federal Government standards and industry recognized national standards for advanced computing and communication technologies. Targeted system attributes at the order level include the following:

A high ratio of peak CPU memory bandwidth to peak CPU floating point capability

2.5 GB to 4 GB of memory per compute core (in special cases, 4GB to 8GB of memory per compute core)

Five distinct file systems with all metadata stored on solid state devices, no single point of failure, and protection from double storage device failure (e.g RAID6): (1) /work1 with at least 125 GB of formatted usable disk storage per core, (2) /work2 with at least 250 TB of formatted usable disk storage, (3) /work 3 with at least 50 GB formatted usable storage per core and the ability to encrypt data consistent with NIST Special Publication 800-131A, (4) /app with at least 1 GB of formatted usable disk storage per core, and (5) /home with at least 8 GB of formatted usable disk storage per core

Aggregate data transfer rates between the compute nodes and each file system as follows:

/work1: 4 MB/s per compute core

/work2: 500 KB/s per compute core

/work3: 500 KB/s per compute core

An ability to simultaneously mount /work1, /work2, /work3, /home, and /app on all login nodes and all compute nodes

A high number of I/O operations per second (IOPs) using 1, 32, and 128 active cores for the following file operations for each scratch file system (i.e. /work, /work2, and /work3): (1) open/create, (2) file stat, (3) #1 and #2 simultaneously, and (4) unlink

A tightly integrated interconnect with (1) each link having at least 100 Gbps of bandwidth and (2) an end-to-end latency that is no greater than 2µs (two microseconds)

A well-tuned operating system (OS) with low jitter, configured in accordance with DISA security technical implementation guides (STIGs)

A 40 gigabit Ethernet interface (or better) for external (i.e. wide-area network [WAN]) connectivity with IPv4 and IPv6 dual-stack functionality

A 40 gigabit Ethernet interface (or better) for internal (i.e. local-area network [LAN]) connectivity with IPv4 and IPv6 dual-stack functionality

Use of workload management software with ability to launch jobs using container-based solutions (e.g.

Docker, Shifter, Singularity)

An appropriate number of job scheduling nodes with (a) suitable job scheduling software and (b) adequate memory, processing capability, and redundancy

Use of HPCMP Kerberos and HPCMP Public Key Infrastructure (PKI) authentication software and

HPCMP Secure Shell (SSH) communication software (which will be furnished by the Government)

Adherence to the following power quality standards: CBEMA, ITIC, SEMI F47, IEC 61000-4-11/34

A cabinet supply voltage of 480V (when possible/feasible)

A cooling solution in which at least 98% of the heat generated by the system is removed by liquid-cooling

Login nodes which contain the same processor type as the compute nodes, but contain more memory per core than compute nodes to facilitate compiling and other interactive functions

A test and development system (TDS) which is a smaller version of the base system (i.e. configured with similar hardware, software, file system, and I/O attributes) to allow effective system software testing, user code porting, and base system configuration management

An ability to execute as many software packages listed on the HPCMP’s software web page

(https://centers.hpc.mil/software) as possible

At least two suites of high-level language compilers: (a) GNU Compiler Collection (version 6.3 or higher) and (b) a proprietary suite

At least two implementations of MPI with at least one being compliant with the MPI-3.1 standard

Javascript and go scripting languages

Python 2.7 must be provided with NumPy, PyMPI, MPI4Py, SciPy, PyTorch, Keras, theano, and

IPython extensions; Python 3.6 (or higher) must be provided with as many of the following extensions as possible: NumPy, PyMPI, MPI4Py, SciPy, PyTorch, Keras, and IPython.

Multiprocessing APIs (including OpenMP), standard computational libraries (including BLAS, BLACS, FFTW, LAPACK, and ScaLAPACK), accelerator computational libraries/compilers

(including CUDA, OpenCL, and OpenACC), performance libraries (including PAPI), and an integrated development environment

Application performance instrumentation tools (including at least one code profiler that interfaces with

PAPI and at least one tool that provides MPI messaging statistics)

A high level of system reliability (i.e. a high overall effectiveness level and a low number of user/job interrupts).

A high level of performance on high performance applications and libraries such as ALEGRA, AVUS, CTH, FFTW, GAMESS, and HYCOM over processor ranges from 8,192 to 65,536 processor cores.

For each file system, a high level of performance for MDTEST using 64, 128, 192, and 256 compute nodes (which are distributed evenly across the standard compute node racks)

2.3 Administration and Maintenance.

The BOA holders shall be responsible for system administration and 24 hours per day, 7 days per week system maintenance (over five one-year options at the individual order level) and (therefore) must ensure that (1) the monthly system effectiveness level does not fall below 97%, (2) the monthly number of user/job interrupts does not exceed the maximum allowable (which is determined by dividing the number of nodes in the base system by one hundred), (3) the response time for remedial maintenance is less than two hours (in all instances), (4) new software is tested and ready for operation prior to implementation on the base system, and (5) software/hardware security vulnerabilities are addressed in a timely manner.

3.0 SECURITY REQUIREMENTS

Since HPCMP systems will be placed (predominantly) at DOD facilities, BOA holders must have sufficient personnel with SECRET level clearances for the purposes of system installation, capability testing, effectiveness level testing, administration, and maintenance. All personnel requiring administrative access to any system and/or supporting network/security component must have an adjudicated tier 5 background investigation., a clearance commensurate with the classification of the system, Information Assurance Technician (IAT) Level II or III certification (see http://iase.disa.mil/eta/iawip/content_pages/iabaseline.html and http://iase.disa.mil/eta/iawip/content_pages/summary_wf_requirements.html), and IA certifications specific to all relevant operating systems.

4.0 PUBLIC AFFAIRS

The BOA holder shall not publicly disclose nay data generated or reviewed under this contract. The BOA holder shall refer all requests for information concerning projects to the Contracting Officer for comment. Prior to release, any publication articles shall be coordinated and approved by the Contracting Officer.

5.0 SUBMITTALS

All submittal requirements will be identified at the order level. These may include but are not limited to: safety plans, quality control plans, project schedules, testing plans, testing results, and closeout documentation.

6.0 REPORTING REQUIREMENTS

All reporting requirements will be established at the order level. Typical reporting requirements are on a monthly basis however, each order will identify the specific requirements for that procurement.

7.0 POINTS OF CONTACT

The POCs for the BOA level are listed below. Other POCs may be identified at the individual order level. The

Contracting Officer shall always be included on all correspondence related to this BOA and all orders.

7.1 Contracting Officer:

Leo R. Ludovici

256-895-1443

Leo.R.Ludovici@usace.army.mil

7.2 Contract Specialist:

Kendra Taylor

256-895-7704

Kendra.N.Taylor@usace.army.mil

SECTION L

SECTION L – INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 COPIES OF SOLICITATION DOCUMENTS AND AMENDMENTS

Copies of the solicitation are available by INTERNET ACCESS ONLY. All solicitation documents will be posted to the FedBizOpps website (www.fbo.gov). All amendments will be posted to FedBizOpps. It shall be the contractor’s responsibility to check the websites for any amendments. The Offeror shall submit in the proposal all requested information specified in the solicitation to be eligible for a BOA.

http://iase.disa.mil/eta/iawip/content_pages/iabaseline.html http://iase.disa.mil/eta/iawip/content_pages/summary_wf_requirements.html mailto:Leo.R.Ludovici@usace.army.mil mailto:Kendra.N.Taylor@usace.army.mil

L.2 JOINT VENTURE /MENTOR-PROTÉGÉ PROPOSAL REQUIREMENTS

When proposing as a joint venture, all members of the joint venture shall sign the SF 33 unless a written agreement by the joint venture is furnished with the proposal designating one firm with the authority to bind the other member(s) of the joint venture. In addition, a copy of the joint venture agreement shall be submitted with the proposal in Volume IV. Failure to comply with the foregoing requirements may eliminate the proposal from further consideration. If this is an

8(a), HUBZone, or Service-Disabled Veteran-Owned joint venture, the Offeror shall ensure that it complies with the applicable requirements of 13 CFR Part 124, 13 CFR Part 125, and 13 CFR Part 126 respectively. The joint venture shall include a copy of its SBA approval of the joint venture arrangement, if applicable.

When proposing as part of a Mentor-Protégé Agreement, include a copy of the agreement and the Small

Business Administration approval of the agreement in Volume I.

L.3 COMMUNICATIONS CONCERNING THE SOLICITATION

a. Questions and/or comments relative to these documents shall be submitted by 10 August 2018

4:00 pm Central Time in order to provide the Government sufficient time to adequately consider the comment or take appropriate actions prior to receipt of offers. Bidder Inquiry is the preferred method in order to expedite responses.

Contract Specialist – Primary POC

U.S. Army Corps of Engineers, Huntsville Engineering and Support Center

ATTN: Kendra Taylor

P.O. Box 1600, Huntsville, AL 35807-4301

Phone : 256-895-7704

Email: kendra.n.taylor@usace.army.mil

Contracting Officer

U.S. Army Corps of Engineers, Huntsville Engineering and Support Center

ATTN: Leo Ludovici

P.O. Box 1600, Huntsville, AL 35807-4301

Phone: 256-895-1443

Email: leo.r.ludovici@usace.army.mil

b. Technical inquiries and questions relating to this solicitation shall be submitted via Bidder Inquiry in ProjNet at

(https://www.projnet.org). To submit and review inquiry items, prospective offerors will need to use the Bidder

Inquiry Key presented below and follow the instructions listed below the key for access. A prospective offeror who submits a comment /question will receive an acknowledgement of their comment/question via email. Another email to the same address will notify the prospective offeror once the reply is available for viewing.

***Please Note: Offerors shall only submit one question per inquiry. All inquiries containing multiple questions shall be rejected.

The Solicitation Number is: W912DY-18-R-0025

The Bidder Inquiry Key is: FN5SGT-7Q8WD4

The Project Name is: Technology Insertion BOA 2018

Instructions for future ProjNet Bidder Inquiry Access:

1. For future access to ProjNet, you will not be provided any type of password. You will utilize your Secret

Question and Secret Answer to log in.

2. From the ProjNet home page linked above, click on Quick Add on the upper right side of the screen.

mailto:kendra.n.taylor@usace.army.mil mailto:leo.r.ludovici@usace.army.mil

3. Identify the Agency. Select agency USACE.

4. Key. Enter the Bidder Inquiry Key listed above.

5. Email. Enter the email address you used to register previously in ProjNet.

6. Click Continue. A page will then open asking you to enter the answer to your Secret Question.

7. Enter your Secret Answer and click Login. Once this is completed you are now logged into the system.

The Bidder Inquiry System will be unavailable for new inquiries twelve calendar days before proposal due date in order to ensure adequate time is allotted to form an appropriate response to inquiries and amend the solicitation if necessary.

Offerors are requested to review the specification in its entirety, and review the Bidder Inquiry System for answers to questions prior to submission of a new inquiry.

The ProjNet call center operates weekdays from 8AM to 5PM U.S. Central Time Zone (Chicago) or by appointment for OCONUS. The telephone number for the Call Center is 1-800-428-HELP. Email to staff@rcesupport.com.

Proposals will NOT be disclosed to the public through the Bidder Inquiry System or ProjNet. Information concerning the status of the evaluation or award will NOT be available through the Bidder Inquiry System or

ProjNet.

c. All communications concerning this solicitation (including, but not limited to, questions, management/technical issues, pricing issues, administrative issues, and proposal issues) are governed by the provisions of 41 U.S.C. 423, which prohibits the knowing disclosure or acquisition of any proposal information or source selection information prior to the BOA awards. In accordance with 41 U.S.C. 423(e)(1), (2), and (3), listed are the various sanctions and/ or penalties available for violations of the above-referenced prohibitions: (1) Criminal penalties up to and including imprisonment for five years; (2) Civil penalties up to $50,000 fine per each violation per individual

(Government or ESCO) and $500,000 fine per each violation per ESCO or firm, plus twice the amount of compensation received or offered for the prohibited conduct; and (3) Administrative actions up to and including cancellation of the Federal agency procurement, rescission of a Federal agency contract, suspension or debarment of the ESCO, and dismissal from Federal Government employment.

L.4 GENERAL REQUIREMENTS

a. Proposals are requested to address the requirements in the statement of work (SOW) entitled

“Technology Insertion BOA 2018”

b. It will be the offeror’s responsibility to ensure that its proposal complies with the latest version of the solicitation. All amendments must be acknowledged to be eligible for award.

c. Proposals should be submitted on the most favorable terms, reflecting the best possible offer, since a less than optimal initial proposal could result in the exclusion of the proposal from further consideration without discussion.

d. Offerors must be registered in the System for Award Management (SAM)

(http://www.sam.gov).

e. Proposals must demonstrate that the offeror has a complete understanding of the requirements.

f. Proposals must presume the Government has no previous knowledge of the offeror’s capabilities.

g. Proposals must provide sufficient details to permit a complete and accurate evaluation from a technical, financial, and past performance perspective.

mailto:staff@rcesupport.com http://www.sam.gov/

h. The Government will not make any assumptions regarding information not presented in the offeror’s proposal (with the exception of certain information that will be acquired by the Government in order to conduct past performance evaluations). It is the offeror’s sole responsibility to clearly address all

SOW requirements in its proposal.

i. The offeror is cautioned that (1) "parroting" requirements and (2) statements of intent to perform do not reveal the offeror's understanding of the requirements or its ability to deliver the necessary services and/or products.

j. The inclusion of general/generic sales material should be avoided.

L.5 PROPOSAL FORMAT AND SUBMITTAL REQUIREMENTS

L.5.1 PROPOSAL SUBMISSION

a. All offerors shall be required to submit a proposal with the minimum content as specified herein.

Proposals without the minimum content may be rejected.

b. Proposals are due 20 August 2018 at 4:00pm Central Time to the following email addresses:

Leo.R.Ludovici@usace.army.mil and Kendra.N.Taylor@usace.army.mil. Late proposals will not be accepted. See FAR 52.215-1, Instructions to Offerors, for rules concerning the submission of late proposals.

c. A complete proposal will consist of two volumes: technical and past performance

d. The offeror must provide electronic copies of each volume; hardcopies will not be accepted.

e. Each volume must comply with the requirements below:

Contents and Limitations for Each Volume

Volume Contents Limitations

1. Technical Capability

Element 1: American OEM Status

Element 2: Manufacturing and Installation

Element 3: Administration and Maintenance

20 pages (when printed)

2. Past Performance Past performance questionnaires 3 questionnaires maximum

f. Offeror must be registered in the System for Award Management (SAM) to receive a BOA. The

SAM website is http://www.sam.gov. SAM has replaced the old Central Contractor Registration system http://www.ccr.gov.

g. Proposals must set forth full, accurate, and complete information as required by this solicitation

(including attachments/exhibits). The penalty for making false statements in a proposal is prescribed in 18 U.S.C. 1001.

mailto:Tezra.J.Hamilton@usace.army.mil mailto:Christopher.M.Barnett@usace.army.mil http://www.sam.gov/ http://www.ccr.gov/

h. Offerors shall submit their best proposal initially as the Government intends to make awards without discussions (except clarifications, as described in FAR 15.306(a)). The Government reserves the right to conduct discussions, should the Contracting Officer deem it necessary.

L.5.2 PROPOSAL FORMAT

Page Limitation – Only information contained within the respective limits below will be evaluated:

Volume I: Technical – 20 pages

Volume II: Past Performance – 3 PPQs

Note: Content outside these limitations will not be evaluated.

Each volume must be clearly indexed and logically assembled.

Each volume must include (1) a title page, (2) a table of contents, and (3) a list of tables/figures.

The header of each page must contain (1) the solicitation name “TI BOA” (2) the offeror’s name, and (3) the date.

The bottom right corner of each page must contain (1) the volume title, (2) proposal revision number, and

(3) page number.

Portable Document Format (PDF) is preferred; Microsoft Excel may be used for spreadsheets.

Times New Roman 12 pt. font must be used.

Hyperlinks must not be placed in the proposal.

Each volume must comply with the limitations in table above (contents and limitations).

Page Setup Parameters shall be:

Margins – Top, Bottom, Left, Right - 1”

Gutter – 0”

From Edge – Header, Footer - 0.5”

Page Size, – 8.5” x 11”

Page Size spreadsheets, table, charts, etc. may be 11” x 17” but counts as 2 pages per side.

The following additional restrictions apply:

Each paragraph shall be separated by at least one blank line.

Font type: Times New Roman; font size:12, font size for headers and footers may be increased to 14 or reduced to 10

Font size for spreadsheets, tables, charts, etc. may be reduced to font size 8

The use of hyperlinks in proposals is prohibited.

Page Limitation – Only pages within the respective page limits as follows will be evaluated:

Volume I: Technical - 20 Pages, ten sheets (double sided) or twenty sheets (single sided)

Volume II: Past Performance – Three Client Complete PPQ’s

Note: Proposal Cover; Cover letter; the Table of Contents; glossaries or indices; Title Page; the List of

Tables/Figures, or Acronyms; Separator Tabs; Cross-Reference to the Solicitation Paragraphs; past performance reference sheets, subcontractor commitment letters, questionnaires and supporting past performance documents, and cost or pricing data in support of the price proposal are excluded from page count. Pages that exceed the required page limitations will not be evaluated. Additional pages will be removed from back to front of the proposal, and will not be evaluated by the Government.

L.6 PROPOSAL CONTENT

Proposals must be responsive to and comply with the terms of the solicitation in order to be eligible to receive an award. The Government will reject any proposal determined to be materially non-responsive or that does not conform to the terms of the solicitation. To be eligible to receive an award, proposals submitted in response to this solicitation shall consist of the contents required in the sub-paragraphs described below:

The content must be organized into volumes as specified.

VOLUME I – FACTOR 1: TECHNICAL CAPABILITY (This applies to the Prime offeror only. Key element information will be submitted and evaluated at the individual order level.)

Element 1 – American OEM Status: The offeror shall demonstrate its status as an American OEM by providing sufficient examples of large, balanced, commercially-available, production-grade HPC systems that the offeror successfully manufactured in the United States and installed, administered, and maintained within the past three years. The offeror shall additionally explain how these examples constitute a viable HPC product line. For reference, a “large” system contains at least 50,000 non-accelerator cores.

Element 2 – Technical Capability: The offeror shall describe its technical ability to manufacture and install HPC systems, (a) which contain an appropriate combination of processor, memory, interconnect, disk input/output (I/O), and operating system (OS) capabilities in order to execute complex, tightly-coupled, large-scale, scientific calculations in support of approximately 300 active users and (b) which possess the following (note that a given order under this BOA will likely include a subset of these exemplar requirements):

A minimum of 50,000 non-accelerator cores across a range of node types to include a rnage of supported processor socket counts and nodes with and without support for PCIe devices (e.g NVMe storage, GPGPUs).

A high ratio of peak CPU memory bandwidth to peak CPU floating point capability

2.5GB to 4GB of memory per compute core (in special cases, 4GB to 16GB of memory per compute core)

Five distinct file systems

/work1 a distinct, highly-available, parallel file system (a) which has at least 125 GB of formatted usable disk storage per effective compute core, (b) which has a full duplex I/O bandwidth between the compute nodes and /work1 of at least 4 MB/s per effective compute core, and (c) which is capable of accessing more than 3 billion file system objects at a sustained rate of 250,000 IOPs

/work2 a distinct, highly-available, solid-state parallel file system (a) which has at least

250 TB of formatted usable disk storage, (b) which has a full duplex I/O bandwidth between the compute nodes and /work2 of at least 500 KB/s per effective compute core, and (c) which is capable of accessing more than 1 billion file system objects at a sustained rate of 250,000 IOPs

/work3 a distinct, highly-available, solid-state parallel file system (a) which has the ability to encrypt data consistent with NIST Special Publication 800-131A which has at least 50 GB of formatted usable disk storage per effective compute core, (b) which has a full duplex I/O bandwidth between the compute nodes and /work3 of at least 500 KB/s per effective compute core, and (c) which is capable of accessing more than 1 billion file system objects at a sustained rate of 250,000 IOPs

/home a distinct, highly-available, parallel file system (a) which has at least 8 GB of formatted usable disk storage per effective compute core, (b) which has a full duplex I/O bandwidth between the compute nodes and /home of at least 200 KB/s per effective compute core, and (c) which is capable of accessing more than 500 million file system objects

/app a distinct, highly-available, parallel file system (a) which has at least 1 GB of formatted usable disk storage per effective compute core, (b) which has a full duplex I/O bandwidth between the compute nodes and /app of at least 30 KB/s per effective compute core, and (c) which is capable of accessing more than 500 million file system objects

An ability to mount /work1, /work2, /home, and /app simultaneously to all login nodes, all data transfer nodes, and all compute nodes

A tightly integrated interconnect

At least 200 Gb/s of peak injection bandwidth for each node

An end-to-end latency that is no greater than 2µs (two microseconds)

A well-tuned operating system (OS) with low jitter, configured in accordance with DISA security technical implementation guides (STIGs)

A 40 gigabit Ethernet interface (or better) for external (i.e. wide-area network [WAN]) connectivity with

IPv4 and IPv6 dual-stack functionality

A 40 gigabit Ethernet interface (or better) for internal (i.e. local-area network [LAN]) connectivity with

IPv4 and IPv6 dual-stack functionality

An ability to launch jobs using container-based solutions (e.g. Docker, Shifter)

Use of HPCMP Kerberos and HPCMP Public Key Infrastructure (PKI) authentication software and

HPCMP Secure Shell (SSH) communication software (which will be furnished by the Government)

An appropriate number of job scheduling nodes with (a) suitable job scheduling software and (b) adequate memory, processing capability, and redundancy

An appropriate number of administration nodes with adequate memory, processing capability, and redundancy

An appropriate number of login nodes with adequate memory, processing capability, and visualization capability (via GPGPUs)

An appropriate number of data transfer nodes with adequate memory, processing capability, and network connectivity

Adherence to the CBEMA and ITIC power quality standards

A cabinet supply voltage of 480V (when feasible)

A cooling solution in which at least 98% of the heat generated by the system is removed by liquid-cooling

A test and development system (TDS) which is a smaller version of the base system and is configured with the same hardware and software as the base system to allow (a) effective system software testing, (b) user code porting, and (c) base system configuration management

An ability to execute as many software packages listed on the HPCMP’s software web page

(https://centers.hpc.mil/software) as possible

At least two suites of high-level language compilers: (a) GNU Compiler Collection (version 6.3 or higher) and (b) a proprietary suite

At least two implementations of MPI with at least one being compliant with the MPI-3.1 standard

Javascript and go scripting langauges

Python 2.7 must be provided with NumPy, PyMPI, MPI4Py, SciPy, PyTorch, Keras, theano, and IPython extensions; Python 3.6 (or higher) must be provided with as many of the following extensions as possible:

NumPy, PyMPI, MPI4Py, SciPy, PyTorch, Keras, and IPython.

Multiprocessing APIs (including OpenMP), standard computational libraries (including BLAS, BLACS, FFTW, LAPACK, and ScaLAPACK), accelerator computational libraries/compilers (including CUDA, OpenCL, and OpenACC), performance libraries (including PAPI), and an integrated development environment

Application performance instrumentation tools (including at least one code profiler that interfaces with

PAPI and at least one tool that provides MPI messaging statistics)

A high level of performance for ALEGRA using 1024, 2048, 5120, and 10240 non-accelerator compute cores

A high level of performance for AVUS using 6144, 8192, 12288, and 16384 non-accelerator compute cores

A high level of performance for CTH using 8192, 16384, 32768, 65,536 and 98,304 non-accelerator compute cores

A high level of performance for GAMESS using 1024, 2048, 3072, and 4096 non-accelerator compute cores

A high level of performance for HYCOM using 4087, 8160, 16342, and 32701 non-accelerator compute cores

A high level of performance for FFTW using 8192, 16384, 32768, and 65536 non-accelerator compute cores

A high level of performance for TENSORFLOW using one and eight accelerators for each of two input sets.

For each file system, a high level of performance for IOR using 64, 128, 192, and 256 compute nodes

(which are distributed evenly across the standard compute node racks)

For each file system, a high level of performance for MDTEST using 64, 128, 192, and 256 compute nodes

(which are distributed evenly across the standard compute node racks)

A high level of system reliability (i.e. a high overall effectiveness level, low number of user/job interrupts, and low number of system-wide interrupts).

Element 3 – Administration and Maintenance: The offeror shall describe its ability to provide system administration and 24x7 system maintenance for large, balanced, commercially-available, production-grade HPC systems such that

The monthly system effectiveness level does not fall below 97%

The monthly number of system-wide interrupts does not exceed the maximum allowable (which is determined by (a) dividing the number of compute nodes in the system by 1000, (b) truncating any fractional portion of the quotient, and (c) adding 1)

The monthly number of user/job interrupts does not exceed the maximum allowable (which is determined by (a) dividing the number of compute nodes in the system by 100, (b) truncating any fractional portion of the quotient, and (c) adding 1)

The response time for remedial maintenance is less than two hours in all instances

New software is tested and ready for operation prior to implementation on the base system

Software/hardware security vulnerabilities are addressed in a timely manner.

The offeror shall additionally discuss

The number of its staff members with SECRET level clearances which are located within 50 miles (i.e. 1 hour) of each of the HPCMP’s four DSRCs for the purposes of system installation, capability testing, effectiveness level testing, administration, and maintenance.

The number of its staff members with TOP SECRET level clearances which are located within 50 miles

(i.e. 1 hour) of each of the HPCMP’s four DSRCs for the purposes of system installation, capability testing, effectiveness level testing, administration, and maintenance.

The number of its staff members with Information Assurance Technician (IAT) Level II or III certifications which are located within 50 miles (i.e. 1 hours) of each of the HPCMP’s four DSRCs for the purposes of administrative level system access.

VOLUME II – FACTOR 2–PAST PERFORMANCE

The offeror shall provide relevant examples of work it conducted as a prime contractor within the past three years.

Greater relevance ratings are given for examples which demonstrate the following:

The manufacturing, staging, delivery, and installation of large, balanced, commercially-available, production-grade HPC systems relative to contracted quality standards and schedules

The development of project plans to facilitate integration of large, balanced, commercially-available, production-grade HPC systems into DoD facilities

The administration and 24x7 maintenance of large, balanced, commercially-available, production-grade

HPC systems.

The offeror is encouraged to provide questionnaires to customers with first-hand experience of any relevant work the offeror performed. The questionnaires shall be completed by the customer, returned to the offeror, and included in Volume II of the proposal. The Government shall accept no more than five questionnaire responses per offeror.

NOTE: In the case of an offeror without a record of relevant past performance or for whom information on past performance is not available or so sparse that no meaningful past performance rating can be reasonable assigned, the offeror may not be evaluated favorably or unfavorably on past performance. Therefore, the offeror shall be determined to have unknown (or “neutral”) past performance. In the context of acceptability/unacceptability, a neutral rating shall be considered “acceptable.”

L.7 PRE-PROPOSAL CONFERENCE

Pre-Proposal Conference – Technology Insertion Basic Ordering Agreement (BOA) 2018

The Government intends to hold a pre-proposal conference with industry to facilitate maximum participation in the

BOA process. Vendors are limited to no more than three (3) attendees to ensure site space is adequate. We plan to hold a group session touching on the technical requirements, steps required to successfully become a BOA holder, and what to expect from the Government for each annual order. Following a recess for lunch, the Government will allow vendors to schedule breakout sessions with the Government with a time limit of 45 minutes. The breakout sessions will be scheduled on a first come, first served basis. Please RSVP all vendor attendees breakout session requests with the Contract Specialist by 5 Aug 2018 so that security accommodations can be made.

Please note that all questions, before, during, and after the conference shall be entered into ProjNet as specified in section L.3(b) of the RFP. Questions asked during the conference, both during the group session and breakout sessions may not be able to be immediately answered. The Government will record all questions entered via ProjNet and respond formally by posting the questions and answers to FedBizOpps (FBO) to ensure all vendors are afforded equal access to information. Please also note that the information available in the group session and breakout sessions will be limited to the information provided via FBO and contained in the RFP Letter and BOA documents.

The Government will not discuss any information not already posted to FBO.

Conference Details as follows –

Conference

Type

In-person & virtual

Date 7 Aug 2018

Time Group Setting: 0900-1100 CST

Lunch Recess: 1100-1230 CST

Breakout Sessions: 1300-close (as )

Location Huntsville Engineering and Support Center

4910 University Square

Suite 4, Large Conference Room

Huntsville, AL 35816

WebMeeting

Information

Meeting Link:

https://usace.webex.com/usace/j.php?MTID=mf29168325a7f821f1181f3612b68fb75

Meeting Number: 263 060 438

Audio Connection: 1-877-4029753

Access Code: 2212408

(End of Summary of Changes) https://usace.webex.com/usace/j.php?MTID=mf29168325a7f821f1181f3612b68fb75