mako_redispatch/lib.rs
1//! `mako-redispatch` — Redispatch 2.0 process engine for German grid
2//! congestion management (§§ 13, 13a, 14 EnWG).
3//!
4//! **This crate is a name reservation. Implementation is pending until
5//! `redispatch-xml` (the format/XSD layer) is complete.**
6//!
7//! # Three-crate architecture for Redispatch 2.0
8//!
9//! | Crate | Responsibility | Status |
10//! |---|---|---|
11//! | `edi-energy` | IFTSTA status messages (EDIFACT) | ✅ In workspace |
12//! | `redispatch-xml` | XML/XSD format parsing and validation (ActivationDocument, PlannedResourceScheduleDocument, Stammdaten, …) | ✅ Implemented |
13//! | `mako-redispatch` | Process engine — Workflow impls, PID routing, deadline handling | ⏳ **This crate** |
14//!
15//! # Domain background
16//!
17//! **Redispatch 2.0** entered into force on **1 October 2021** via the
18//! Netzausbaubeschleunigungsgesetz (NABEG) and requires all German grid
19//! operators to coordinate congestion management across transmission and
20//! distribution networks.
21//!
22//! Redispatch 2.0 uses **CIM/IEC 62325-based XML documents** for the primary
23//! data exchange (handled by `redispatch-xml`), and **IFTSTA (EDIFACT)** for
24//! status messages (handled by `edi-energy`). Unlike GPKE/WiM/GeLi Gas, this
25//! process family does not use UTILMD or APERAK.
26//!
27//! # Planned PID range
28//!
29//! PIDs for Redispatch 2.0 workflows will be registered in the `PidRouter`
30//! once the process engine is implemented.
31//!
32//! | Process | Governing document |
33//! |---|---|
34//! | Abruffahrplan Redispatch | BDEW Redispatch 2.0 specification |
35//! | Stammdatenübermittlung | BDEW Redispatch 2.0 specification |
36//! | Verfügbarkeitsmeldung | BDEW Redispatch 2.0 specification |
37//!
38//! # Dependencies (planned)
39//!
40//! When implemented this crate will depend on:
41//! - `mako-engine` — event-sourced workflow runtime
42//! - `redispatch-xml` — Redispatch 2.0 XML format layer
43//! - `edi-energy` — IFTSTA status message parsing