How we
build truth.

Sources

RemitScan ingests from five primary source classes. Each ingest is timestamped to nanosecond precision at receipt, and the raw payload is retained in an append-only object store with SHA-256 content addressing.

Inside-Information Platforms (IIPs)

Inside-Information AG · Nasdaq UMM Hub · EEX UMM Hub · JAO. Streaming AMQP/JSON or polled REST. UMM disclosures published by market participants under REMIT Article 4(1).

ENTSO-E Transparency Platform

Production unavailability records (TP items 15.1.A and 15.1.B), filed by TSOs on a 1-minute polling cadence.

TSO direct feeds

Where authorised: Amprion, 50Hertz, TenneT, RTE, REE et al. SFTP/CSV at 15-minute cadence. Used to corroborate, never to substitute.

ACER REMITbase mirror

Hourly REST snapshot of registered organised market places, MPs, and asset registry entries.

Day-ahead price feeds

EPEX, Nord Pool, OMIE. Used solely as input to the materiality price-impact component.

Asset registry

We maintain a canonical asset registry keyed by Energy Identification Code (EIC). 4,926 generation assets across 27 countries are mapped to (a) market participant, (b) primary fuel, (c) bidding zone, (d) TSO, and (e) WGS-84 coordinates with ±1km tolerance.

Where an MP submits an unmapped EIC, the registry is updated within one business day. Mappings are deterministic — no fuzzy matching is used at the registry layer.

Matching engine

The matching engine pairs UMM disclosures with TP unavailability records. The pairing function is:

MATCH(umm, tp_event) ⇔
    asset_eic(umm) = asset_eic(tp_event)             [hard]
  ∧ |start(umm) − start(tp_event)| ≤ Δt              [Δt = 48h]
  ∧ Jaccard(cause_terms(umm), cause_terms(tp_event)) ≥ 0.4
  ∧ |mw_declared(umm) − mw(tp_event)| / mw(tp_event) ≤ 0.20

EIC equality is required. Time tolerance Δt is parameterised per regulator interpretation; the default is 48h to account for late filings within the "without delay" regime. Cause-term Jaccard guards against spurious co-occurrence; the 0.4 threshold was calibrated against a 2024 supervised set of n=12,400 hand-paired records and yields F1 = 0.94.

Materiality scoring

Each unavailability event is scored 0–100 across four components, additive with caps:

Day-ahead price impact component (25 pts) is in development and will be added once the DA price feed is live.

Materiality determines surveillance prioritisation only — it never affects whether a flag is raised, only its display ranking.

Detection rules

Three deterministic rules are live in v1 (DE+FR active tier; watch-tier statistics for the remaining 34 ENTSO-E countries). Two further rules are under development and are not yet emitting flags.

1. AL-RULE-MISSING-UMM — TP event with no matched UMM after 48h. (live)
2. AL-RULE-LATE-UMM — UMM published more than 60 minutes after the TP detection timestamp. (live)
3. AL-RULE-INCONSISTENCY — Matched UMM ↔ TP pair with declared-MW divergence > 5% or cause classification mismatch. (live)
4. AL-RULE-RESTATEMENT — TP record edited > 24h after publication, with no follow-up UMM. (v2 — in development, no flags emitted yet)
5. AL-RULE-OUT-OF-WINDOW — UMM published before any corresponding TP record exists, with no plausible TP delay explanation. (v2 — in development, no flags emitted yet)

Disclosure Quality Index

The DQI is a 0–100 composite per MP, computed as a weighted average over a trailing 90-day window:

DQI is published per MP, per country, and as a sector aggregate. It is recomputed nightly and is fully reproducible from inputs.

Reproducibility & lineage

Every flag carries a lineage manifest enumerating: raw record SHA-256, query manifest SHA-256, calculation step SHA-256, rule version, and detection wall-clock timestamp. Manifests are signed by the publishing pipeline and verifiable offline.

Any reader of a RemitScan evidence pack can replay a flag from raw data using the public AL-RUNNER tool and verify byte-for-byte equivalence.

Limitations

RemitScan does not assert market manipulation. Flags are statistical disclosure-quality indicators; their resolution requires the judgement of operators and regulators with access to non-public information. Sub-100 MW events, behind-the-meter generation, and aggregator-managed virtual assets are out of scope for v2.5.

Data coverage limitations

As of the v2.5 effective date, three known gaps in the ingested source data prevent us from emitting flags we would otherwise be able to emit deterministically. We surface them here rather than in a footnote because they materially affect what the inbox shows today.

Publication timestamp lineage

The IIP-to-Gold writer persists the outage window (start, end) but not the disclosure publication timestamp on the canonical entity. AL-RULE-LATE-UMM therefore uses ingestion receipt time as a proxy, which biases the measured delay upward for any UMM received in a backfill or replay. We treat this as a structural gap and have suspended automated emission of late-UMM flags until publication time is restored on the Gold record. Tracking: AL-ISSUE-GOLD-PUB-TS.

MP attribution coverage

Only 7.8% of UMM disclosures (2,492 / 31,572) currently carry a deterministic publishes_umm relationship back to a market participant entity. The remaining 92.2% are ingested and visible at the asset level but cannot be aggregated into MP-level DQI or attributed in the flag inbox. Coverage is improving as the ACER REMITbase mirror catches up to ENTSO-E registrations.

Owned-by relationship coverage

The ontology supports an owned_by relationship_assertion between asset and market participant; the current row count is zero. AL-RULE-MISSING-UMM, which requires asset→MP attribution to identify the responsible publisher, therefore skips every TP event today. The rule is correct and live; the input data is not yet present.

These three items are the dominant reason a regulator looking at the live inbox today sees fewer flags than the rules would otherwise produce. They are not silenced or filtered — they are not detectable from current Gold-layer state. Each is tracked, dated, and will be reflected in the changelog when resolved.