For research teams and procurement

Arrange research infrastructure work

A practical procurement guide for HPC and AI engagements: qualification, scope, access, deliverables, purchase orders, invoices and handover.

Start with a useful question

Tell me what your team needs to run, what is getting in the way and what decision the work should support. You do not need to diagnose the root cause first. A small, focused engagement can be appropriate even when the surrounding system is large.

Agree the work and its boundaries

A brief qualification conversation establishes system size, relevant workload, software stack, access restrictions, test window and expected deliverable. The written scope names authorized changes, downtime or failure tests, dependencies and exclusions. We also agree who reviews findings and who can accept a change.

You can see sample deliverables before deciding on an engagement. The accepted scope determines the actual report, evidence, implementation work and handover. Fixed-scope fabric, filesystem, scheduler and acceptance services do not require a paid architecture assessment first.

Prepare access without sending credentials

Describe how approved remote or on-site access is arranged. Do not put passwords, tokens, private datasets, controlled technical material or sensitive identifiers into the public contact form. The NDA, access method and any data-handling obligations are agreed before that material is exchanged.

Where the work touches regulated or controlled information, the applicable requirements and permitted handling are part of the written scope. A discussion of a framework is not a statement that every engagement is certified or authorized for that data.

Choose the purchasing route that fits your organization

The ordering page maintains current rates, terms, PO, invoice, deposit and prepayment options. Universities, hospitals and agencies can use their normal purchase-order process. If supplier registration, a quotation, W-9 or insurance documentation is needed, include that requirement in the request.

A submitted purchase order becomes an engagement through the written acceptance described in the ordering terms. Larger builds, work outside a fixed format and additional remediation are scoped and quoted. This guide does not replace those terms or create a new payment policy.

Bring these details to the first conversation

  • The research or operational task and the decision you need to make.
  • Approximate system size and the relevant compute, storage and fabric stack.
  • Symptoms, prior observations and any deadline or maintenance window.
  • Your role, the technical owner and the procurement contact if known.
  • Required access, NDA and data-handling arrangements.
  • The deliverable you need and whether implementation or retesting is in scope.

Leave with an operating handover

The conclusion should make clear what was observed, changed and verified; what remains open; how to roll back; and who owns the supported state. A technical readout helps your team and, where appropriate, vendors work from the same evidence.

Discuss the scope · Explore services · View current rates and ordering · Read the printable capabilities sheet.