GCRI · Foundry
Operator support
Foundry is designed to run under different installation profiles, and the help an operator needs depends on which one. This page, published by The Global Centre for Risk and Innovation (GCRI), describes how operator support is organised for each profile, the failure modes the design anticipates and where to report a problem. Support for installed environments opens with the agreements that create them. Information and enquiries are open today.
Operator support on the record.
- 01FieldsData and compute, Methods and modelling
- 02STEM methods6 canonical methods applied
- 03Topics8 subject pages
- 04Counterparts1 platforms in shared fields
- 05PublisherThe Global Centre for Risk and Innovation
Four installation profiles.
| Profile | Where it runs | What support covers |
|---|---|---|
| Dedicated managed cloud | A single-tenant environment in a chosen region | Platform operation, updates and incident handling under the agreement |
| Private and on-premises | An institution’s own data centre | Installation guidance, updates and runbooks; the institution operates its infrastructure |
| Field and operational edge | Field and mobile cells that sync when connected | Device setup, deferred synchronisation and reconciliation |
| Disconnected operations | Air-gapped cells with signed export | Controlled transfer, reconciliation and offline runbooks |
What the design expects to go wrong.
Links drop
Field and edge cells keep working offline and reconcile when connected, with conflicts shown, not hidden.
A gate says no
Requests without a policy decision fail closed. Support explains the decision; it never bypasses it.
A source is wrong
Corrections create new versions, and dependent products are traced so their owners can act.
Tickets tied to the affected record.
- 01
Report
A ticket names the system, module and record concerned, so the right runbook is opened.
- 02
Resolve
Runbooks have an owner, an applicability scope and a review date; stale runbooks are flagged before an incident relies on them.
- 03
Record
The resolution and any lesson are kept in the Hub system for the next operator.
Where to report a problem.
General questions go to the contact form. Security vulnerabilities go to the security report form. Errors in published evidence go to the integrity concern form. Each acknowledgement gives a reference and names the next step.
Foundry is not an emergency-dispatch service. In immediate danger, contact your local emergency services.
Questions and answers.
Is there a support desk I can call now?
Who operates a private installation?
Can support override an access decision?
Where are known issues published?
Does support differ by profile?
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.