GCRI · Labs
Field and lab testbeds
A testbed is a controlled place to try something before it meets the world: a laboratory rig, a pilot plant, a field trial plot, a living lab in a neighbourhood, a regulatory sandbox. Testbeds carry risks of their own, to staff, participants, sites and neighbours, and their evidence is only as useful as the match between test and conditions of use. This page sets out how testbeds are designed, permitted, made safe and read, and who decides when a result may move on.
How the work runs.
Testbed operations
Field and lab testbeds · Field lab coast · Campaign 5
Sensor deployment
illustrative coastline
Sensors
| S-01 tide | 94 | 0.2 | Nominal |
| S-04 salinity | 91 | 0.4 | Recalibrate |
| S-07 wave | 91 | 0.2 | Nominal |
Sensor vs reference
Fig.Testbed operations: example names and illustrative values, not a record or a live system.
Field and lab testbeds: how the risk develops.
Test environments, safety and site permissions. The dossier below sets out how the risk develops, what is measured, where the data come from, how it is modelled and who decides.
The test is not the world
Laboratory conditions remove the variability of real sites, users and maintenance. A technology that performs on a rig may fail in heat, dust, intermittent power or untrained hands. The gap between test and operating environment is what readiness levels try to name.
Hazards travel with the experiment
Pressurised systems, biological agents, chemicals, batteries, drones and autonomous machines can harm people outside the lab once trials move to the field. Risk assessment has to follow the experiment to each new site and each new configuration.
Permission is layered
Field work can need landowner consent, environmental and planning permits, aviation or radio authorisations, biosafety approval and community agreement. A missing permission can halt a trial midway or make its data unusable.
Living labs involve people
When a trial runs in homes, streets, wards or workplaces, residents become participants. Consent, data protection, benefit sharing and exit arrangements decide whether the evidence is ethical and whether the community will host another trial.
How field and lab testbeds is modelled, measured and tested.
The model, its assumptions, its data and its uncertainty, in the form a scientist or engineer would check. Structures follow published methods. The values drawn are illustrative, not findings.
Model, equations and assumptions
The model structure used for field and lab testbeds, the assumptions it makes and how each is tested.
Ri = f(Hi, Ei, Vi, Ci)hazard, exposure, vulnerability and coping capacityEAL = ∑k pk · Lkover events k with annual probability pkxt+1 = A xt + B ut + εtA carries the couplings, u the shock, ε the error| Assumption | Why it is made | How it is tested |
|---|---|---|
| Hazard and exposure are independent within an event | Keeps the loss integral tractable | Compare with a copula fit on joint records |
| Couplings are linear near the operating point | Lets shocks propagate through A | Perturb beyond the linear range and compare |
| Vulnerability curves transfer between places | Local curves are rarely available | Validate against observed losses where they exist |
- Inputs
- versioned datasets with provenance
- Outputs
- distributions, never single numbers
- Code
- released with the model card and tests
- Reproduction
- same data, code, environment and seed
Testbeds test technology in each domain’s real conditions.
Testbed results feed the Labs Evidence series. Readiness is described with TRLs, which measure maturity, not suitability.
- Testbed sites with owners’ terms.
- Negative results.
What is measured, and how well.
Each indicator carries its unit, its cadence, the kind of source behind it and the evidence label a value would carry. No values are shown: a programme supplies them under its own authority.
| Indicator | Unit | Cadence | Source type | Label |
|---|---|---|---|---|
| Technology readiness level at entry and exit | level on a named TRL scale | per trial | Assessment against NASA, EU or ISO 16290 definitions | DECLARED |
| Independent readiness review | percent of readiness claims reviewed outside the team | annual | Programme review records | OBSERVED |
| Operating-environment fidelity | ordinal scale from laboratory to operational | per trial | Test plan against the stated use environment | ESTIMATED |
| Permits in force before start | percent of required permits | per trial | Permit register | Published statistics |
| Safety incidents and near misses | count per thousand test hours | monthly | Incident reporting system | REPORTED |
| Participant consent coverage | percent of participants with recorded consent | per trial | Consent records | OBSERVED |
| Site restoration completed | percent of field sites restored to the agreed condition | per trial | Site closure reports | REPORTED |
Where the evidence comes from.
Named public datasets and institutional records, each with its licence class. Sources by agreement are used only under their terms and never republished.
| Source | What it gives | Licence class |
|---|---|---|
| ESFRI roadmap and landscape analysis | European research infrastructures, their scope and access conditions | Free access, attribution |
| MERIL portal (European Science Foundation) | Inventory of European research infrastructures open to external users | Free access, terms of use |
| European Network of Living Labs member directory | Living labs, their domains and contact points | Free access, terms of use |
| Testing and Experimentation Facilities (European Commission, Digital Europe Programme) | Sector testbeds for artificial intelligence in manufacturing, health, agri-food and cities | Public programme records |
| CORDIS (European Commission) | Funded projects, pilot sites, deliverables and reported readiness | Free and open, CC BY |
| Global BioLabs (King’s College London and George Mason University) | Mapped high-containment laboratories and their biosafety governance | Free access, attribution |
| National permit and incident registers | Field-trial permits, release authorisations and reportable incidents | By agreement with each authority |
Who decides, and what the evidence serves.
Labs prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| Who decides | The question | Evidence this page serves |
|---|---|---|
| Institutional biosafety and safety committees | Whether an experiment may run at a given containment level or field site | Hazard assessment, containment design, training and incident records |
| Environmental, aviation and spectrum regulators | Whether a field release, flight or transmission may be authorised | Test plan, site description, mitigation and monitoring arrangements |
| Programme managers at funding agencies | Whether a technology has earned the next readiness gate and its funding | Readiness evidence per level, independent review, fidelity statement |
| Host communities and landowners | Whether to host a trial, on what terms, and how it ends | Plain-language trial description, data use, benefits and restoration plan |
Outputs this topic produces
- Test plans stating the operating environment, the hazards and the exit criteria for each readiness level
- Permit and safety registers kept with the trial record
- Readiness assessments with evidence attached to each level claimed
- Site agreements and closure records for field and living-lab trials
What experts ask before a test begins.
- How close are the testbed’s conditions to the real setting where the result will be used?
- What can be controlled, what can only be observed, and what is unknown?
- What could go wrong for people, equipment or the environment, and how is it contained?
- Who owns the site and the data, and who has granted permission to use them?
- How will the testbed be returned to its original state when the work ends?
Why the gap between test and reality matters.
The value of a testbed lies in control: it removes or fixes some sources of variation so that the effect of interest can be seen. The cost of control is realism. A water treatment process that works in a laboratory may fail with real source water that varies by season; a forecasting tool that performs well on historical data may degrade when the system changes. Engineers call this the validity trade-off, and it is never eliminated, only managed.
Field testbeds narrow the gap but bring new risks. They involve communities, landowners, operators and regulators, each with legitimate interests. They can disrupt services, collect personal data or affect ecosystems. Safety cases, consent and permissions are therefore part of the science, not administration around it.
Systems engineering offers a staged path: component tests, integrated tests in simulation, limited field trials and wider pilots, with criteria for moving between stages.
How testbeds are characterised.
- 01
Testbed description
A record of the environment, instruments, calibration, boundary conditions and known deviations from the target setting.
- 02
Hazard and safety analysis
Structured identification of failure modes and controls, drawing on systems engineering practice. It reduces but does not remove residual risk.
- 03
Simulation and digital models
Virtual testbeds that allow many runs at low cost. Their results are only as good as the model’s validation.
- 04
Readiness staging
Explicit criteria for moving from bench to simulation to field. Staging helps decisions but readiness levels are coarse and can hide important differences.
A testbed result shows performance under the tested conditions. Generalising beyond them requires further evidence and is reported as a separate claim.
How it is studied, and what the methods cannot say.
- 01Systems engineeringRequirements to verification traceability · Stage-gate readiness reviewsApplied here
- 02Uncertainty quantification and model validationMeasurement uncertainty budgets · Sensitivity analysis of simulation modelsApplied here
- 03Probability and statisticsSample size and power planning · Meta-analysis with bias assessmentApplied here
- 04Causal inference and impact evaluationRandomised pilots and stepped rollouts · Quasi-experimental programme evaluationApplied here
Where this page’s references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Questions and answers.
What does a technology readiness level measure?
What is a living lab?
Who is responsible for safety in a field trial?
Is a regulatory sandbox an exemption from the law?
Does Labs own testbed sites?
Can a company test a product in a Labs testbed?
Are simulation testbeds treated differently?
Contribute evidence from this page.
Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- EmailGateway GW-GCRISend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Bring a method, a dataset or a question.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Legal documents.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.