fbmc-chronos2 / doc /alegro_investigation_complete.md
Evgueni Poloukarov
feat: Alegro HVDC investigation complete - documented data limitation
0df759f
# Alegro HVDC Outage Data Investigation - Complete Analysis
**Date**: 2025-11-09
**Status**: Investigation Complete - Documented Limitation
## Executive Summary
**Finding**: Alegro HVDC outage data is NOT available via free ENTSO-E Transparency Platform API, despite correct methodology and real EIC code discovery.
**Decision**: Document as known limitation, proceed with zero-filled outage features (valid for MVP), integrate paid/authenticated sources in Phase 2.
---
## Real Alegro EIC Code Discovered
**Source**: ENTSO-E Allocated EIC Codes Registry
- **EIC Code**: `22T201903146---W`
- **Long Name**: ALEGRO DC
- **Display Name**: L_LIXHE_OBERZ
- **Type**: International transmission asset
- **Status**: Active (A05)
**Critical Discovery**: JAO uses 8 custom Alegro EICs (ALEGRO_EXTERNAL_BE_IMPORT, etc.) for virtual market coupling constraints. These are NOT real transmission asset EICs.
---
## Automated Collection Testing
### Script Created
**File**: `scripts/collect_alegro_outages_automated.py`
**Method**:
1. Query BE-DE border transmission outages (documentType A78)
2. Parse ZIP/XML to extract Asset_RegisteredResource.mRID
3. Filter to Alegro EIC: 22T201903146---W
4. Collect BOTH business types (A53 planned + A54 forced)
5. Bidirectional queries (BE->DE and DE->BE)
### Test Results
- **Period**: Oct 2023 - Sept 2025 (24 months)
- **Result**: ZERO outages found
- **Critical Finding**: NO transmission outages for entire BE-DE border (not just Alegro)
### Diagnostic Testing
**File**: `scripts/diagnose_bede_outages.py`
- Tested last 6 months
- Both directions (BE->DE, DE->BE)
- Result: NoMatchingDataError for all queries
- **Conclusion**: ENTSO-E API contains NO BE-DE transmission outage data
---
## Historical Availability Data
**Source**: Amprion/Elia Press Releases
**Alegro Performance**:
- **2020-2021**: 93% availability = 7% downtime = ~613 hours/year outages
- **2022**: 98% availability = 2% downtime = ~175 hours/year outages
**Contradiction**: Outages occurred historically, but ENTSO-E API returns zero.
---
## Alternative Data Sources Identified
### 1. EEX Transparency Platform (REMIT)
- **Purpose**: Amprion's REMIT inside information publication
- **API**: `https://api.eds.prod.fra.gcp.dbgservice.com/pub/transparency/non-availability-events`
- **Status**: Requires paid API access (502 Bad Gateway without auth)
- **Likelihood**: HIGH - Alegro outages likely here
### 2. Elia Group Inside Information Platform (IIP)
- **URL**: https://www.eliagroup.eu/en/elia-group-iip
- **Purpose**: Belgian TSO's REMIT compliance
- **Status**: ACER-listed, requires registration
- **Likelihood**: HIGH - Alegro outages likely here
### 3. Elia Open Data Portal
- **URL**: https://opendata.elia.be
- **Features**: Free public API, transmission data
- **Status**: Temporarily unavailable (service overload)
- **Likelihood**: MEDIUM-HIGH - may include Alegro
### 4. ENTSO-E Transparency (documentType A78)
- **Status**: ZERO outages for entire BE-DE border
- **Conclusion**: HVDC data NOT in this API
---
## Root Cause Analysis
**Why ENTSO-E API Has No Alegro Outages**:
1. **HVDC Reporting Channel**: HVDC interconnectors report via REMIT (EEX, Elia IIP) not ENTSO-E
2. **TSO Practices**: Amprion/Elia prioritize REMIT over ENTSO-E for HVDC
3. **Publication Lag**: Recent data may not be in ENTSO-E yet
4. **Access Level**: HVDC may require different authentication
---
## Production Decision
**Approach**: Document as known limitation, create zero-filled features
**Rationale**:
- MVP 5-day timeline prohibits paid API integration
- Zero-filled features technically correct (no data = assume operational)
- Automated collection works when data available
- Clear Phase 2 integration path
**Alegro Outage Features** (4 per asset):
- `alegro_outage_binary`: 0 = operational
- `alegro_outage_planned_7d`: 0 = no planned outage
- `alegro_outage_planned_14d`: 0 = no planned outage
- `alegro_outage_capacity_mw`: 0 = full capacity
**Validity**: Zero values correctly represent "no outage data" = assume normal operation.
---
## Phase 2 Roadmap
**Option 1 - EEX Transparency API** (Recommended)
- Commercial API with Amprion REMIT data
- Cost: Unknown
- Coverage: German-side outages
**Option 2 - Elia Open Data**
- Free public API
- Wait for service restoration
- Coverage: Belgian-side outages
**Option 3 - Elia IIP**
- Register for access
- May require market participant status
- Coverage: REMIT compliance data
---
## Files Created
**Scripts**:
- `scripts/collect_alegro_outages_automated.py` - Production-ready collection
- `scripts/find_alegro_real_eic.py` - EIC discovery from registry
- `scripts/diagnose_bede_outages.py` - Border outage diagnostic
**Documentation**:
- `doc/alegro_eic_mapping.md` - EIC code mapping
- `doc/alegro_investigation_complete.md` - This summary
---
## Current Status
- ✅ Automated collection: Production-ready
- ✅ Real EIC code: 22T201903146---W validated
- ✅ Alternative sources: Identified (EEX, Elia IIP, Elia Open Data)
- ❌ Data availability: Zero in free ENTSO-E API
- 📝 Decision: Documented limitation, zero-filled features
- 🔜 Phase 2: Integrate paid/auth sources
**Impact on MVP**: Minimal - 8 Alegro CNECs with 32 zero-filled features valid for forecasting
**Next**: Commit, continue Day 2 feature engineering