Government, National Lab, and Shared Testbed Operations

Shared quantum infrastructure has different goals from a single-company platform. It must support research access, education, technology transfer, standards development, security review, and multi-institution collaboration. It is closer to a national facility than a SaaS product.

The NSF National Quantum Virtual Laboratory program is an example of shared infrastructure intended to support use-inspired and application-oriented quantum technology development. Shared testbeds need strong operating models because the user base is broad, the equipment is scarce, and the evidence must often survive public scrutiny. [R151]

Diagram loads as you read

Government, National Lab, and Shared Testbed Operations · Figure 1

View diagram source

flowchart TB
    Facility[Shared quantum facility] --> Access[Access program]
    Facility --> Operations[Operations team]
    Facility --> Safety[Safety and compliance]
    Facility --> Data[Data and evidence]
    Facility --> Education[Training]
    Facility --> Translation[Technology translation]

Shared testbed goals

Diagram loads as you read

Shared testbed goals · Figure 2

View diagram source

flowchart LR
    Testbed[Testbed] --> Research[Research]
    Testbed --> Workforce[Workforce development]
    Testbed --> Standards[Standards and benchmarks]
    Testbed --> Industry[Industry pilots]
    Testbed --> PublicValue[Public value]

A testbed should not optimize only for utilization. It should optimize for learning, reproducibility, safe access, and credible evaluation.

Access model

Diagram loads as you read

Access model · Figure 3

View diagram source

stateDiagram-v2
    [*] --> Application
    Application --> Review
    Review --> Approved
    Review --> Rejected
    Approved --> Onboarding
    Onboarding --> Scheduled
    Scheduled --> Executed
    Executed --> EvidenceReview
    EvidenceReview --> Published
    EvidenceReview --> Restricted

Access review should consider:

technical feasibility;
safety implications;
export-control and data restrictions;
educational value;
benchmark value;
required support level;
expected public output;
conflict with facility maintenance windows.

User tiers

Tier	Description	Support model
exploratory	learning, small experiments	self-service plus office hours
research	peer-reviewed scientific work	assigned research liaison
benchmark	standardized cross-platform evaluation	strict evidence protocol
industry pilot	confidential or semi-confidential workload	data and access controls
facility development	hardware/control improvement	deep engineering collaboration

Diagram loads as you read

User tiers · Figure 4

View diagram source

flowchart TB
    Users[Users] --> Exploratory[Exploratory]
    Users --> Research[Research]
    Users --> Benchmark[Benchmark]
    Users --> Industry[Industry pilot]
    Users --> Facility[Facility development]

Scheduling governance

Diagram loads as you read

Scheduling governance · Figure 5

View diagram source

flowchart LR
    Demand[Access demand] --> Review[Scientific and operational review]
    Review --> Priority[Priority assignment]
    Priority --> Calendar[Facility calendar]
    Calendar --> Execution[Execution window]
    Execution --> Report[Use report]

Shared facilities need transparent scheduling criteria. Hidden priority rules degrade trust.

Evidence policy

Diagram loads as you read

Evidence policy · Figure 6

View diagram source

flowchart TB
    Evidence[Evidence policy] --> Public[Public artifacts]
    Evidence --> Restricted[Restricted artifacts]
    Evidence --> Embargo[Embargoed artifacts]
    Evidence --> Classified[Controlled artifacts]
    Evidence --> Retention[Retention schedule]

Many testbed projects produce mixed evidence: public benchmark summaries, restricted raw data, and confidential partner notes. The evidence model must handle this from the beginning.

Diagram loads as you read

Data-sharing pattern · Figure 7

View diagram source

sequenceDiagram
    participant User
    participant Facility
    participant DataOffice
    participant Repository
    participant Reviewer

    User->>Facility: execute experiment
    Facility->>DataOffice: package artifacts
    DataOffice->>Repository: publish allowed artifacts
    DataOffice->>Reviewer: hold restricted package
    Reviewer-->>User: clearance or redaction request

Safety and compliance overlay

Diagram loads as you read

Safety and compliance overlay · Figure 8

View diagram source

flowchart TB
    Request[Experiment request] --> Safety[Safety review]
    Request --> Security[Security review]
    Request --> Data[Data review]
    Request --> Export[Export-control review]
    Safety --> Gate{All gates clear?}
    Security --> Gate
    Data --> Gate
    Export --> Gate
    Gate -- yes --> Schedule[Schedule]
    Gate -- no --> Remediate[Revise or reject]

Facility KPIs

Do not rely only on uptime.

Diagram loads as you read

Facility KPIs · Figure 9

View diagram source

flowchart TB
    KPI[Testbed KPIs] --> Learning[Learning velocity]
    KPI --> Access[Access fairness]
    KPI --> Repro[Reproducibility]
    KPI --> Utilization[Useful utilization]
    KPI --> Workforce[Workforce trained]
    KPI --> Translation[Transferred methods]

Example KPI table:

KPI	Why it matters
accepted proposals by tier	access mix
completed experiments per maintenance hour	operational leverage
reproducible result percentage	evidence quality
external benchmark submissions	ecosystem value
trained users	workforce outcome
time from proposal to first run	accessibility

Technology transfer

Diagram loads as you read

Technology transfer · Figure 10

View diagram source

flowchart LR
    Research[Research result] --> Package[Reproducible package]
    Package --> Standard[Standard or benchmark]
    Package --> Tool[Open-source tool]
    Package --> Industry[Industry pilot]
    Industry --> Feedback[Operational feedback]
    Feedback --> Research

A shared facility should convert experiments into reusable methods, not only papers.

Operating rule

A shared quantum testbed is successful when it produces reusable evidence, trained users, validated methods, and trustworthy comparisons—not merely when it keeps expensive hardware busy.