GCRI · Labs
現地とラボのテストベッド
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.
作業の進め方。
Testbed operations
Field and lab testbeds · Field lab coast · Campaign 5
Sensor deployment
例示の海岸線
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
図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 システム, biological agents, chemicals, batteries, drones and autonomous machines can harm people outside the lab once trials move to the field. リスクアセスメント 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 structure used for field and lab testbeds, the assumptions it makes and how each is tested.
Ri = f(Hi, Ei, Vi, Ci)ハザード、エクスポージャー、脆弱性、対処能力EAL = ∑k pk · Lk年間確率 pkxt+1 = A xt + B ut + εtA carries the couplings, u the shock, ε the error| 仮定 | 作られる理由 | 検証の方法 |
|---|---|---|
| 一つの事象の中では、ハザードとエクスポージャーは独立している | 損失の積分を扱いやすく保つ | 同時記録に当てはめたコピュラと比較 |
| 結合は動作点の近くで線形である | ショックを A を通じて伝播させる | 線形範囲を超えて摂動を与えて比較する |
| 脆弱性曲線は場所を越えて適用できる | 地域固有の曲線はめったに得られない | 観測された損失がある場合はそれに照らして検証 |
- 入力
- 来歴付きのバージョン管理されたデータセット
- 成果物
- 分布であり、単一の数値ではない
- コード
- モデルカードと試験とともに公開
- 再現
- 同じデータ、コード、環境、シード
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.
何を、どの程度うまく測定しているか。
各指標には、その単位、更新頻度、背後にある出典の種類、値が持つことになるエビデンスのラベルが付いています。値は表示しません：プログラムが自らの権限のもとで値を提供します。
| 指標 | 単位 | 周期 | 出典の種類 | ラベル |
|---|---|---|---|---|
| Technology readiness level at entry and exit | level on a named TRL scale | per trial | Assessment against NASA, EU or ISO 16290 definitions | 申告済み |
| Independent readiness review | percent of readiness claims reviewed outside the team | 年次 | Programme review records | 観測 |
| Operating-environment fidelity | ordinal scale from laboratory to operational | per trial | Test plan against the stated use environment | 推定 |
| Permits in force before start | percent of required permits | per trial | Permit register | 公表統計 |
| Safety incidents and near misses | count per thousand test hours | 月次 | Incident reporting system | 報告値 |
| Participant consent coverage | percent of participants with recorded consent | per trial | Consent records | 観測 |
| Site restoration completed | percent of field sites restored to the agreed condition | per trial | Site closure reports | 報告値 |
エビデンスの出所。
名前の明示された公開データセットと機関の記録。それぞれにライセンス区分があります。合意に基づく出典は、その条件のもとでのみ使用し、再公開することはありません。
| 出典 | 提供するもの | ライセンス区分 |
|---|---|---|
| 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 ラボ 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（欧州委員会） | 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 |
誰が決め、エビデンスが何に役立つか。
ラボ prepares evidence. The decisions below are taken by the authorities named, under their own rules, and never by the platform.
| 誰が決定するか | 質問 | このページが提供するエビデンス |
|---|---|---|
| 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 |
このトピックが生み出す成果物
- 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.
システム 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 システム工学 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.
Where this page’s references lead.
このページの読解の基準となる機関と文書。状態と版は変わります。各リンクは発行機関へ移動します。
質問と回答。
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?
このページからエビデンスを提供する。
報告書 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.
- メールゲートウェイ GW-GCRIこのページから送信するエビデンス、訂正、事例、手法、レビュー、翻訳、プロファイルへの入力。このページのタグが付いて届くため、担当の編集者が受け取ります。
- Zenodoオープンな寄託寄託してコミュニティに提出するORCID iD を使って Zenodo に自分の記録を公開し、そこから Reports コミュニティに提出してください。キュレーターが審査し、DOI は引き続きあなたのものです。
- 報告書GCRI貢献のすべての方法を見る貢献の種類、それぞれの審査方法、受け取るクレジット、ライセンス、決して受け付けないもの。
個人データ、重要インフラの機微な詳細、共有する権利のないものは決して送らないでください。寄稿は利用前にレビューされます。送付によって著作者としての権利や編集上の権利が生じることはなく、スポンサーシップで調査結果を買うことは決してできません。
手法、データセット、または問いを持ち込んでください。
情報提供と問い合わせは本日から受け付けています。問い合わせには参照番号が付き、次の手順が示されます。申請、支払い、計算資源の割り当て、登録は、担当チーム、規約、審査体制が整ってから開始します。
法的文書。
このサイトの地図、データ、図表は、背景と一般的な情報として示すものです。助言、予報、警報ではありません。情報の限界は免責事項とデータに関する注意事項に記載しています。