NB688000-19-02150__JOFOC_signed_Redacted.pdf

DatePhone No.

ting - Not exceeding $ 0,000:

Title

APPROVAL REQUIREMENTS

Date

Advocate - Over $ ,000 but not exceeding $ million:

Title gnature Phone No.

Date

- Over $ million:

Title Signature

NOTE: Use the total cost estimate specified on the front of this document in determining the necessary approvals. Each review must be preceded by lower level approval(s), e.g., over $ million all approvals are required.

DatePhone No.

This contract requires the implementation of a number of technically demanding, detailed modifications and extensions to an existing piece of complex custom software, the ARTIQ experimental control framework, which was developed in previous contracts with a very close collaboration between NIST and M-Labs. The implementation of the various gateware and software modules and capabilities which are the deliverables requires a very detailed understanding of ARTIQ. This includes an understanding of the architecture of ARTIQ, and the various scientific and technical reasons why certain design choices were made; a demonstrated track record of successful major contributions to the ARTIQ system; expertise with the many software tools used in ARTIQ, including Python, Rust, Migen, MiSoC, mor1kx, and LLVM; expertise in FPGA and embedded systems design, including but not limited to high-performance open-source TDC/DTC cores, the mor1kx processor, ARM processors, the wishbone bus architecture, high-performance memory controllers, and MiSoC; and proven ability to work with scientific staff during software development to ensure that new modules are designed for maximum usefulness and robustness in the laboratory environment, and remain well-supported after contract termination.

The ARTIQ experimental framework was developed as a custom software/hardware package for NIST by M-Labs, Ltd. Because they are the developers of ARTIQ, M-Labs is uniquely suited to develop extensions and modifications to ARTIQ. M-Labs alone possesses the full set of required criteria given above, which are absolutely essential to a time-efficient, cost-efficient implementation of the deliverables in this contract.

In the bids for the original ARTIQ contract (SB1341-14-SU-0271 - May 2014) and in responses to a sources sought notification (December 2013), no other potential bidder demonstrated familiarity with the full set of technologies employed in ARTIQ (as listed above). For two subsequent ARTIQ modifications contract (SB1341-15-SE-0363 - September 2015, and SB1341-16-SE-0309 – September 2016), there were no responses from other vendors to the notice of intent to sole source to M-Labs. Furthermore, nobody other than M-Labs, members of our NIST group, and members of research groups at and the have made significant contributions to the existing ARTIQ system, demonstrating understanding of the architecture and design philosophy, and mastery of the necessary technologies to implement features successfully within the ARTIQ framework.

It is in theory possible that other programmers could be contracted to work on ARTIQ, since the source code is not proprietary to M-Labs.

However, because no other potential programmers have the requisite experience either with ARTIQ or with all of the technologies used in ARTIQ, work with such programmers would require them to conduct extensive research to learn about and become familiar with ARTIQ and its included technologies. The amount of time required would depend on the programmer’s existing skills, but we estimate that a minimum of 6 weeks of full-time effort would be required to reach a functional level of expertise required to begin developing the deliverables in this contract.

Furthermore, this learning process for such programmers would require extensive discussions with M-Labs, for which they would be charged for consulting time by M-Labs, and this cost would be passed on to NIST. Such programmers would also require extensive discussions with the NIST group, duplicating effort already performed with M-Labs over the course of ARTIQ development, regarding the scientific rationale for different design choices, our detailed preferences and requirements for software and gateware functionality, and an understanding of the laboratory and connected hardware ecosystem which is operated by ARTIQ. Based on the amount of time already committed to this process by NIST and M-Labs