QgenticQgentic
Qgentic / platforms / opres
Qgentic OpRes · PRA and FCA

UK operational resilience reporting, computed from your own timestamps.

Qgentic OpRes builds the records the UK PRA and FCA operational resilience rules ask for: the important business services register, third-party dependency mappings and incident reports. Every impact tolerance breach is calculated from system timestamps, so the assessment is arithmetic.

One report, timestamps to export

Data comes in from your existing GRC tools, every tolerance breach is computed, a named person approves, and the package comes out hashed. It plays in your browser, with nothing to install.

How your data gets in: integration and data.

Who it is for

UK-only firms

UK-only entities, such as building societies, that answer to PRA and FCA rules on third-party mapping, impact tolerances and incident reporting, with no DORA overhead to carry.

PRA and FCA regulated firms

UK banks, insurers, investment firms and FMIs: important business services, tolerance tracking and disruption reporting, with every step auditable.

Groups across the UK and EU

UK OpRes and EU DORA run on one architecture, with one evidence portal across both. See the Preferred Partner models.

What it does, and what stays with you

The PRA and FCA obligations interlock across both rulebooks. Qgentic OpRes takes the data and reporting layer; the decisions stay with your own governance.

Qgentic does this

Reporting and validation

It reads your existing data and builds the service register, third-party mappings and incident reports, checks their integrity, calculates every tolerance breach from the timestamps, and produces the regulatory package for a named person to approve.

These stay with the firm:

Governance

Services and tolerances

Deciding which business services are important, and setting their impact tolerances, is the board's job. Qgentic checks the definitions for consistency and leaves the decisions where they belong.

Testing

Scenario testing

Scenario testing and the annual self-assessment stay with your team. Qgentic tracks real incidents against your tolerances; it does not simulate scenarios.

Incident response

Remediation

Post-incident analysis, remediation planning and the changes that follow are internal processes. Qgentic supplies the incident data those reviews start from.

Scope note

Critical Third Parties (CTPs)

The FSMA 2023 CTP rules apply to designated infrastructure providers, such as the major cloud vendors. A regulated firm filing its own resilience reports sits outside their direct scope.

The outputs become the data your internal testing and regulatory reviews work from. Qgentic prepares the reports; you submit them through the FCA's RegData or Connect, or the PRA's channels.

How a report gets made

  1. IntakeRaw data arrives from your existing GRC platform by REST API, automated file transfer or CSV upload, with no plugin to install.
  2. ComputationIncident durations and tolerance breaches are calculated from system timestamps. A manual override that contradicts them is rejected (rule OPRES-TOL-008).
  3. ValidationDeterministic rules check FRN formats, ISO 17442 LEI checksums, referential integrity across dependencies and the order of events.
  4. Risk flagsHigh-risk configurations are flagged before submission, such as a material arrangement with no exit plan (OPRES-EXIT-011) or a heavily depended-on sub-outsourcer (OPRES-SUB-012).
  5. Approval and exportA named approver signs off the data, and Qgentic produces the hashed package (CSVs, JSON and a manifest) for submission.
How an operational resilience self-assessment is computed Your service inventory, dependency mapping and incident records feed the Qgentic engine. The model reads the service map and summarises test results; code decides the outcome: it recomputes every incident duration from its own timestamps, measures the worst disruption against the stated impact tolerance, and validates FRNs and LEI checksums. A tolerance breach is computed from the timestamps, and a manual override that contradicts them is rejected under rule OPRES-TOL-008. The run then stops at a named person approver, whose name, note and timestamp are written to the audit chain, before the important business services register, third-party register and incident report are exported with a manifest and a SHA-256 hash for every file. § YOUR SYSTEMS § THE QGENTIC ENGINE § THE GATE § THE SUBMISSION PACK Service inventory important business services · 3 in scope Dependency map people, process, tech 4 third parties Incidents + tests raw start/end stamps 2 in the period MODEL READS CODE DECIDES reads the service map extracts dependencies summarises test results drafts the narrative duration from stamps worst vs tolerance FRN + LEI checksums referential integrity A BREACH IS COMPUTED FROM TIMESTAMPS An override the timestamps contradict is refused. OPRES-TOL-008 · no wall clock in the maths 1 tolerance breach found · 2 warnings raised AWAITING APPROVAL A named person signs the report. marta.lindqvist approver · admin The name, the note and the timestamp go on the chain. no self-approval The self-assessment important-business- services.csv third-party-register.csv incident-report.json manifest.json SHA-256 per file rerun it in a year and the same input agrees audit chains VALID FCA PS26/2 and PRA PS7/26: incident and material third-party reporting rules in force 18 March 2027, prepared for the firm to file through that channel.
The breach determination is the whole point, so it is arithmetic: durations are recomputed from the raw start and end stamps and measured against the tolerance you stated, and an override that disagrees with the timestamps is refused. Nothing in the calculation reads the wall clock, so the same input reaches the same answer when an inspector reruns it a year later.

What the code enforces

CheckWhat it does
Breach calculationIncident durations come from the raw timestamps, and a manual change that disagrees is rejected (OPRES-TOL-008).
IdentifiersFRN structures are validated, and every LEI is checked against its ISO 17442 checksum.
Mapping integrityA material arrangement not linked to a business service is an error (OPRES-MAT-007).
Audit chainA hash-chained log of every action; nothing is exported until a person authorises it.

There is no public FRN check-digit algorithm, so validation pairs strict formatting rules with LEI verification to pin the entity down.

What you file

The reports

CSVs for the third-party register and important business services, and JSON for incident reports, formatted to the current regulatory standards. Every file is hashed into a manifest, and nothing is generated until a person authorises it. The dashboard tracks each annual self-assessment deadline.

opres-export: required csv/json files, manifest.json, incident summaries

Filing to the regulator

The PRA and FCA do not currently expose an API for these reports, so the software runs in prepare-only mode: your team uploads the finished outputs to RegData, Connect or the PRA, with proof of how every number was derived.

What it costs

Pilot

£3,500 flat, 4-6 weeks

Your existing registers, shadowed and validated in full. The fee is credited in full against year one.

Cloud

from £1,500 /month, metered

Base tiers: Starter £1,500, Growth £3,750, Enterprise £7,500. The meter counts material third parties, validated reports and finalised submission packages.

Air-gapped

from £24,000 /year, Sealed Site

Runs isolated on your own premises, with no external data transmission. See the air-gapped edition.

Every edition's price is on the pricing page, and consultancies can deliver it through the partner programme. The contract stack: Master Terms, Schedule B (OpRes) and your Order Form.

Frequently asked questions

What defines UK operational resilience reporting?

The continuing evidence obligations the PRA and FCA set (for example in SYSC 15A): firms document their important business services, impact tolerances, third-party dependencies and disruption events.

Who identifies important business services?

The firm's board defines them, based on the potential harm to consumers or to market integrity. Qgentic validates and records those decisions; the decisions stay with the board.

How are impact tolerances managed?

Each tolerance is recorded as a testable limit, usually a duration. Qgentic measures real incident timestamps against it, so breach reporting is a calculation.

How does OpRes differ from DORA?

DORA is EU law built around a reporting format; UK OpRes is PRA/FCA supervision built around impact tolerances. Multinationals run both on one Qgentic engine. See Qgentic DORA.

What specific tasks does Qgentic automate?

Data assembly, deterministic validation, breach calculation and report generation. Policy decisions, scenario testing and remediation stay with the firm.

Why doesn't it submit through an API?

The PRA and FCA do not currently expose an API for these operational resilience submissions. Qgentic runs every step up to the export and prepares the exact files you upload to the regulators' portals.

Operational resilience guides