TI Amendment 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 remove 252.225-7011 and extend the question due date. Questions are now due on 14 July 2021 at 2:00pm Central Time.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 11

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

16C. DATE SIGNED

BY 08-Jul-2021

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 W912DY20R0066

X 9B. DATED (SEE ITEM 11)

01-Jul-2021

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 1 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

08-Jul-2021

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:

W912DY20R0066

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION I - CONTRACT CLAUSES

The following have been deleted:

252.225-7011 Restriction on Acquisition of Supercomputers JUN 2005

SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS

The following have been modified:

INSTRUCTIONS TO OFFERORS

L.1 COPIES OF SOLICITATION DOCUMENTS AND AMENDMENTS

Copies of the solicitation are available by INTERNET ACCESS ONLY. All solicitation documents to include amendements will be posted to the www.SAM.gov website. All amendments will be posted to www.SAM.gov. 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.

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 14 July 2021 2: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 only method in order to expedite responses.

Contract Specialist – Primary POC

U.S. Army Corps of Engineers, Huntsville Engineering and Support Center ATTN: Ariel Wilkins P.O. Box 1600, Huntsville, AL 35807-4301 Email: Ariel.S.Wilkins@usace.army.mil

Contracting Officer U.S. Army Corps of Engineers, Huntsville Engineering and Support Center ATTN: Latosha McCoy P.O. Box 1600, Huntsville, AL 35807-4301 Phone: 256-895-1304 Email: Latosha.V.Mccoy@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-20-R-0066 The Bidder Inquiry Key is: 2JT7F6-MU2BIJ The Project Name is: FY2021 TI BOA 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.

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 ten 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 “BOA Level Scope of Work”

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. Offerors must be registered in the System for Award Management (SAM) (http://www.sam.gov).

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

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

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

g. 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.

h. 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.

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

j. 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.

k. 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 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 2 August 2021 at 12:00pm Central Time to the following email addresses: Latosha.v.Mccoy@usace.army.mil and Ariel.S.Wilkins@usace.army.mil. Late proposals will not be accepted. See FAR 52.212-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

CPARS or Past Performance Questionnaires for 5 Projects maximum

L.5.2 PROPOSAL FORMAT

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

Volume I: Technical – 20 single sided pages Volume II: Past Performance – CPARS or Past Performance Questionnaires for 5

Projects maximum.

Note: Content outside these limitations will not be evaluated.

Each volume must be clearly indexed and logically assembled.

Each volume should be contained within one PDF document.

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:

o Margins – Top, Bottom, Left, Right - 1” o Gutter – 0” o From Edge – Header, Footer - 0.5” o Page Size, – 8.5” x 11”

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

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.

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, 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

The Offeror shall provide a Technical Narrative that provides supporting projects, experience, and information to demonstrate acceptability for FACTOR 1: TECHNICAL CAPABILITY 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 65,536 non-accelerator cores or at least 512 nodes.

Element 2 – Manufacturing and Installations: The offeror shall demonstrate its technical ability to manufacture and install HPC systems, (a) which contain an appropriate combination of processor, memory, interconnect, input/output (I/O) subsystems, 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 specific orders may have varying requirements, including a subset of the attributes below—these are meant to be illustrative of an exemplar HPC system.)):

A minimum of 65,536 non-accelerator cores across a range of node types to include a range 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.

256 GB to 4 TB of random access memory per compute node. Single bit correction and multibit error detection are required.

A minimum of 512 compute total compute nodes spanning a range of node types to include a range of supported processor socket counts and nodes with and without support for PCIe devices (e.g. nonvolatile memory express (NVMe) storage, general purpose graphic processing units (GPGPUs)).

Multiple petabyte-scale distinct file systems with all metadata stored on solid state devices, no single point of failure, and protection from double storage device failures (e.g. RAID6).

Aggregate data transfer rates between the compute nodes and each file systems ranging from 20 GB/s to 1 TB/s.

An ability to simultaneously mount multiple file systems on all login nodes and all compute nodes or a subset of file systems on a subset of nodes.

A high number (500,000+) of I/O operations per second (IOPs) using 1, 32, and 128 active cores for the following file operations for each parallel file system: (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 per processor socket and (2) an end-to-end latency that is no greater than 3µ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 higher data rate) for external (i.e. wide-area network [WAN]) connectivity with IPv4 and IPv6 dual-stack functionality.

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

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.

Three-phase power cabinet supply with a preference for a supply voltage of 480V.

A cooling solution in which a minimum of 98% of the heat generated by the system is removed by liquid-cooling.

Login nodes and data transfer nodes which contain the same processor type as the compute nodes to facilitate compiling, data transfer, and other interactive functions, but contain more memory per core, additional 40 Gbps network interfaces, and with support for GPGPUs and/or other accelerators.

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 9 or higher) and (b) a proprietary suite targeting each processor type included in the system.

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

JavaScript and go scripting languages.

Python 3.8 (or higher) must be provided with as many of the following extensions as possible: NumPy, PyMPI, MPI4Py, SciPy, PyTorch, and IPython. Support for Jupyter notebooks is required.

Multiprocessing APIs (including OpenMP), standard computational libraries (including BLAS, BLACS, FFTW, LAPACK, and ScaLAPACK), accelerator computational libraries/compilers (including OpenCL, and OpenACC), performance libraries [including the Performance API (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 GAMES, CTH, HYCOM, AVUS, and FFTW over processor ranges from 8,192 to a minimum of 65,536 processor cores.

Element 3 – Administration and Maintenance: The offeror shall demonstrate 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 four hours. Some orders may require no greater than a 2 hour response).

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:

o 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.

o The number of its staff members with adjudicated tier 5 investigations and a minimum of SECRET level DOD 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.

o The number of its staff members with Information Assurance Technician (IAT) Level II or III certifications (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 computing environment certifications specific to all relevant operating systems, 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 no more than five relevant examples of projects it conducted as a prime contractor within the past three years by submitting the associated recent past performance records (Questionnaires (see Attachment 1) or CPARS). Recent past performance is defined as work it conducted as a prime contractor within the past three years. Relevant examples should

(a) exhibit support for DoD, Federal, State, and Local Government customers, (demonstrated performance at DoD and National Laboratories is preferred), and (b) demonstrate the manufacturing, staging, delivery, installation, 24x7 administration, and 24x7 maintenance of tightly-coupled, commercially- available, production-grade HPC systems which contain at least 65,536 non-accelerator cores or at least 512 compute nodes. The questionnaires shall be completed by the customer, returned to the offeror, and included in Volume II of the proposal.

The offeror is encouraged to provide questionnaires to customers with first-hand experience of relevant work the offeror has performed as a prime contractor. In the event a customer requests, questionnaires may be submitted directly to the Government’s point of contact ariel.s.wilkins@usace.army.mil.

The Government will evaluate no more no more than five relevant examples of projects provided by the offeror but reserves the right to consider past performance information from the following sources:

• PPIRS, CCASS, ACASS, CPARS, and other agency performance history databases

• Written responses to questionnaires submitted directly to the Government by customers of the offeror

• Telephone interviews between the Government and customers of the offeror

• Government personnel who have prior contractual experience with the offeror (e.g.

contracting officer representatives [CORs] and contracting officers [KOs]).

The Government may consider the timing, relevance, and any other meaningful context when analyzing past performance information and may examine general trends in contractor performance. If an offeror has multiple functions or divisions, the Government will only evaluate the past performance of the division or unit submitting a response to the BOA solicitation. The past performance of parent companies, affiliates, or subsidiaries not directly relevant to the response will not be evaluated.

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.”

(End of Summary of Changes)