Skip to content

GCRI · Quantum Technologies

Data and technical methods

The public technical tools of Quantum Technologies: the models and data behind them, how to reproduce a view and the uncertainty it carries.

01Indawo yokusebenzela

The workspace for data and technical methods.

Umbhobho

Data and technical methods · Workspace WS-82 · Example interface, not a record

One stage waitingGCRI · Quantum Technologies

Stages

  1. Ingest5 sources
  2. Validateschema · licence
  3. Transformversioned
  4. ModelPhysics
  5. Testheld-out
  6. Releasewith limits

Artefacts

Crypto inventoryv3.7VulaASSESSED
Testbed calibration logsv3.2VulaKUQWALASELWE
Skills surveyv5.1VulaSURVEY
Standards trackerv5.9VulaPublished statistics

Compute quota

share used vs alert level

CPU hours27 used of 80 used limitStorage82 used of 90 used limitGPU hours17 used of 70 used limit
Pipeline.Illustrative interface; not live data.

Quantum Technologies · Pipeline. Pipeline: example names and illustrative values, not a record.

02Izixhobo

What is published here.

Iimephu

Released maps

Open the released maps

Models

Reviewed models and scenarios

Open the reviewed models

Iimeko-mfanekiso

Sector scenarios

Open the sector scenarios

03Fitness for purpose

What every quantum tool should state about itself.

Quantum tools serve security teams planning migration and analysts assessing capability claims. A specialist checks the hardware metrics and conditions, the date of each claim and its peer-review status. Tools rest on quantum technology and cybersecurity and support the post-quantum cryptography and quantum computing topics. Inventory templates for cryptographic dependencies are the most used tool; capability summaries are updated only when peer-reviewed evidence changes.

  • Hardware metrics and conditions.
  • Date of capability claims.
  • Peer-review status.
04Inkqubo yokusebenza

Indlela inkqubo eqhuba ngayo.

Process explorer · Process

Data and technical methods: Layers to published map

7 steps4 stages1 gate

Inkqubo yokusebenza

Data and technical methods: Layers to published map

Layers enter with their rights, are aligned, analysed and checked for uncertainty, then released after public-safe review; a map is a governed spatial claim.

  1. 01 Data

    1. 01Source layers with their rightsDataset · NXS-GRX (canonical data, provenance and risk)Spatial views of The Global Risks Index (NXS-GRX) products sit under the boundary licence gate. Rights classification sets how a layer may be used.
  2. 02 Lungelelanisa

    1. 02Coordinate reference and boundary versionRecord · NXS-EOP (earth observation and digital twins)The area of interest preserves its coordinate reference system, polygon validity and observation support. Boundary versions are kept.
    2. 03Harmonise units, variables and timeStepUnit metadata, conversion records and transformation logs are required. Alignment is an evidence event, not hidden preprocessing.
  3. 03 Analyse and check

    1. 04Analyse with a recorded processing recipeModel · GIS teamA processing recipe records parameters, calibration, inputs and output lineage. The analysis methods are named in each product’s own record.
    2. 05Spatial uncertainty checkGateSpatial uncertainty is recorded and affects downstream use. A high-uncertainty polygon may suit internal review, not public-safe release.
  4. 04 Papasha

    1. 06Spatial metadata bundleRecordThe bundle records boundary type, jurisdiction, geometry version, projection, resolution, source, time window, uncertainty and access class.
    2. 07Public-safe release of the mapDecisionThe output record names the redactions, uncertainty and public-safe reviewer. A map is a governed spatial claim, never merely a picture.

Spatio-temporal intelligence · Data protocols: semantic, jurisdictional and temporal intelligence · NXS-EOPDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The pages cited are design doctrine.

05Build environment

Working with the tools.

Analysis runs in Foundry for authorised projects. Public pages show released views only, each with its time and space reference and its rights.

06Imithombo

Where this page’s references lead.

Amaqumrhu namaxwebhu eli phepha elifundwa ngokuthelekiswa nawo. Imeko neenguqulelo ziyatshintsha; ikhonkco ngalinye liya kwiqumrhu elikhuphayo.

07Amaphepha

Pages in Data and technical methods.

08Imibuzo

Imibuzo neempendulo.

Can I use the data?
Each released view states its licence and terms. Data that is not released is not available through these pages.
IingxeloNikela

Faka ubungqina obuvela kweli phepha.

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.

GCRIIitekhnoloji zeQuantumItekhnoloji Ekhula NgokukhawulezaImbono Yexesha Elizayo
Iitekhnoloji zeQuantum

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.