mako-redispatch

Event-sourced process engine for Redispatch 2.0 congestion-management workflows under §§ 13, 13a, 14 EnWG. Part of the mako workspace.

Format boundary

This crate is format-agnostic: workflows and the type router know only the domain enum RedispatchDocumentKind — the same layering as mako-gpke/mako-wim/mako-mabis, which never depend on edi-energy. The canonical DocumentType → RedispatchDocumentKind mapping lives at the transport boundary in makod (redispatch_xml_ingest::document_kind), the only crate that depends on both halves. The mapping is exhaustive, so a tenth XML document type fails compilation instead of silently never routing; makod's tests/redispatch_xml_pipeline.rs proves the full wire path (raw ActivationDocument XML → namespace-checked parse → kind → router → redispatch-aktivierung) and asserts a routing decision for all nine document types (the AcknowledgementDocument is correlation-routed by design).

Regulatory scope

Redispatch 2.0 is mandatory for all German grid operators (ÜNB and VNB) and their connected asset operators (ANB) under BNetzA rulings BK6-20-059, BK6-20-060, and BK6-20-061, effective 2021-10-01. Suppliers (LF) and metering operators (MSB) are out of scope.

Market roles in scope: ANB (Anlagenbetreiber), VNB (Verteilnetzbetreiber), ÜNB (Übertragungsnetzbetreiber), BKV (Bilanzkreisverantwortlicher).

Three-crate architecture

Workflows

Regulatory deadlines

5-minute hard real-time constraint: The makod Redispatch deadline scheduler must poll at ≤ 30-second intervals. Configure a dedicated DeadlineScheduler instance for Redispatch workflows — the standard Werktage-based scheduler used for GPKE/WiM is not sufficient.

IFTSTA PIDs

Redispatch 2.0 IFTSTA messages (confirmed from IFTSTA AHB 2.1 + PID 4.0):

These PIDs route to the redispatch-aktivierung workflow via PidRouter and are registered by RedispatchModule in makod.

Routing

Unlike GPKE/WiM/GeLi Gas (EDIFACT RFF+Z13 Prüfidentifikatoren), Redispatch 2.0 XML documents are routed by RedispatchRouter based on XML document type, not EDIFACT PID. The makod AS4 ingest sniffs XML payloads (first non-whitespace byte <), parses them with redispatch_xml::parse_and_validate, and maps the document type to a RedispatchDocumentKind before routing.

Regulatory basis

Engine module

RedispatchModule implements EngineModule and is registered in makod when DeploymentRoles contains at least one of Marktrolle::Nb, Marktrolle::Unb, or Marktrolle::Anb:

if roles.contains_any(&[Marktrolle::Nb, Marktrolle::Unb, Marktrolle::Anb]) {
    builder.register(Box::new(RedispatchModule));
}

RedispatchModule::configure() wires all 8 workflows into a RedispatchRouter and registers IFTSTA PIDs 21037 / 21038 into the PidRouter.

AcknowledgementDocument routing

AcknowledgementDocument is not registered in the type-based router. Inbound ACKs carry a ReceivingDocumentIdentification field identifying the workflow instance they belong to. The makod dispatcher resolves that correlation key against the ProcessRegistry and delivers the ACK directly to the originating workflow.

Deadline scheduler note

The 5-minute Activation (ACO) deadline requires the DeadlineScheduler to poll at ≤ 30-second intervals. Use a dedicated scheduler instance for Redispatch workflows — the standard Werktage-based GPKE/WiM scheduler is insufficient.

Related crates