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 증거 시리즈. 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모든 기여 방법 보기기여 유형, 각각의 검토 방식, 받게 되는 크레디트, 라이선스, 그리고 절대 받지 않는 것.
개인정보, 민감한 인프라 세부 정보, 공유할 권리가 없는 자료는 절대 보내지 마십시오. 기여물은 사용 전에 검토됩니다. 기여물을 보낸다고 해서 저작자 지위나 편집 권한이 부여되지 않으며, 후원으로 조사 결과를 얻을 수 없습니다.
방법, 데이터세트 또는 질문을 가져오십시오.
정보와 문의는 오늘부터 열려 있습니다. 문의에는 참조 번호가 부여되고 다음 단계가 안내됩니다. 신청, 결제, 컴퓨팅 할당, 등록은 해당 팀, 약관, 심사 역량이 갖추어졌을 때만 열립니다.
법률 문서.
이 사이트의 지도, 데이터와 그림은 맥락과 일반 정보로 제시됩니다. 조언, 예보 또는 경보가 아니며, 정보의 한계는 면책 고지와 데이터 고지에 나와 있습니다.