ankn
a5f8fb49ab
Bahn: aisupport, Analyse-O2C-C2S, awesome-bahn-mcp-servers, beam-mcp,
Confluence_Bot, db-planet-mcp-server, O2C-Harness, project-audit,
Projekt-KIQ-HP, teamlandkarte-mcp
Dhive: Jury-Voting
Privat: CV, NoteGraph (NOTE: NoteGraph needs complete redo after consolidation)
Shared: AI-Orchestrator, OrgMyLife, power_skills_and_more
Shared/references: symphony (read-only)
Bahn repos remain available as independent remotes - this monorepo
pulls them in via subtree, the originals are untouched.
188 lines
14 KiB
HTML
188 lines
14 KiB
HTML
<!DOCTYPE html>
|
||
<html lang="de">
|
||
<head>
|
||
<meta charset="UTF-8">
|
||
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
||
<title>O2C + C2S — Architektonische Sicht (Tool-Landschaft)</title>
|
||
<style>
|
||
* { box-sizing: border-box; margin: 0; padding: 0; }
|
||
body { font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', sans-serif; background: #f8f9fa; color: #333; padding: 20px; }
|
||
h1 { margin-bottom: 8px; font-size: 1.6rem; }
|
||
.subtitle { color: #666; margin-bottom: 20px; font-size: 0.9rem; }
|
||
.domain { background: #fff; border-radius: 12px; box-shadow: 0 2px 8px rgba(0,0,0,0.08); margin-bottom: 20px; overflow: hidden; }
|
||
.domain-header { padding: 14px 20px; cursor: pointer; display: flex; justify-content: space-between; align-items: center; }
|
||
.domain-header h2 { font-size: 1rem; }
|
||
.domain-header .arrow { transition: transform 0.2s; color: #999; }
|
||
.domain.open .arrow { transform: rotate(90deg); }
|
||
.domain-body { display: none; padding: 0 20px 16px; }
|
||
.domain.open .domain-body { display: block; }
|
||
</style>
|
||
<style>
|
||
.system { display: grid; grid-template-columns: 200px 1fr 180px; gap: 8px; padding: 8px 12px; margin: 4px 0; border-radius: 6px; background: #fafafa; border-left: 3px solid #ddd; align-items: center; font-size: 0.85rem; }
|
||
.system:hover { background: #f0f7ff; }
|
||
.system .name { font-weight: 600; }
|
||
.system .desc { color: #555; }
|
||
.system .owner { color: #888; font-size: 0.8rem; text-align: right; }
|
||
.cat-o2c { border-left-color: #1976d2; }
|
||
.cat-c2s { border-left-color: #388e3c; }
|
||
.cat-shared { border-left-color: #f57c00; }
|
||
.cat-data { border-left-color: #7b1fa2; }
|
||
.legend { display: flex; gap: 16px; margin-bottom: 20px; flex-wrap: wrap; font-size: 0.85rem; }
|
||
.legend-item { display: flex; align-items: center; gap: 6px; }
|
||
.legend-dot { width: 12px; height: 12px; border-radius: 2px; }
|
||
.gap-note { background: #fff3e0; border: 1px dashed #f57c00; border-radius: 8px; padding: 12px 16px; margin-top: 16px; font-size: 0.85rem; }
|
||
.gap-note h3 { font-size: 0.9rem; color: #e65100; margin-bottom: 6px; }
|
||
.gap-note li { margin: 3px 0; }
|
||
@media (max-width: 800px) { .system { grid-template-columns: 1fr; } }
|
||
</style>
|
||
</head>
|
||
<body>
|
||
<h1>O2C + C2S — Architektonische Sicht (Tool-Landschaft)</h1>
|
||
<p class="subtitle">Stand: 17.06.2026 | Quellen: DB Planet, Confluence, Organigramm-PDFs | Status: Teilweise — zu vertiefen pro Team</p>
|
||
|
||
<div class="legend">
|
||
<div class="legend-item"><div class="legend-dot" style="background:#1976d2"></div>O2C</div>
|
||
<div class="legend-item"><div class="legend-dot" style="background:#388e3c"></div>C2S</div>
|
||
<div class="legend-item"><div class="legend-dot" style="background:#f57c00"></div>Übergreifend</div>
|
||
<div class="legend-item"><div class="legend-dot" style="background:#7b1fa2"></div>Data/Analytics</div>
|
||
</div>
|
||
|
||
<!-- Domäne: Trassenbestellung & Vertrieb -->
|
||
<div class="domain open">
|
||
<div class="domain-header" onclick="this.parentElement.classList.toggle('open')">
|
||
<h2>🚂 Trassenbestellung & Vertrieb</h2><span class="arrow">▶</span>
|
||
</div>
|
||
<div class="domain-body">
|
||
<div class="system cat-o2c"><span class="name">pathOS</span><span class="desc">Zentrales Bestellsystem (Netzfahrplan, GelV, ujBau) — 167 Repos, Microservice-Architektur</span><span class="owner">ART pathOS (53)</span></div>
|
||
<div class="system cat-o2c"><span class="name">TrassenOrder (TraPo)</span><span class="desc">Neuer Testballon für GelV-Portal (UX-first, entkoppelt) — Discovery seit 01/2026</span><span class="owner">pathOS / 5 Pers.</span></div>
|
||
<div class="system cat-shared"><span class="name">TPN (Trassenportal Netz)</span><span class="desc">Bestehendes Portal für Trassenanmeldung — Ziel von Trassenfinder-Übergabe</span><span class="owner">extern (I.NB)</span></div>
|
||
<div class="system cat-shared"><span class="name">Trassenfinder</span><span class="desc">Routensuche, Infrastrukturdaten, Übergabe an TPN — Web-App, zugangsfrei</span><span class="owner">DigiPaLö (11)</span></div>
|
||
<div class="system cat-shared"><span class="name">Infraportal</span><span class="desc">Zentrales Kundenportal (SSO, Nutzerverwaltung, Anliegen einreichen)</span><span class="owner">DigiPaLö (11)</span></div>
|
||
<div class="system cat-shared"><span class="name">DB NetzCockpit (NiCo)</span><span class="desc">Internes Pendant zum Infraportal für DB InfraGO Mitarbeitende</span><span class="owner">DigiPaLö (11)</span></div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Domäne: Abrechnung -->
|
||
<div class="domain">
|
||
<div class="domain-header" onclick="this.parentElement.classList.toggle('open')">
|
||
<h2>💰 Abrechnung & Preisbildung</h2><span class="arrow">▶</span>
|
||
</div>
|
||
<div class="domain-body">
|
||
<div class="system cat-o2c"><span class="name">AC Trasse</span><span class="desc">Trassenpreisabrechnung — Kern-System des ART Abrechnung</span><span class="owner">ART Abrechnung (52)</span></div>
|
||
<div class="system cat-o2c"><span class="name">SAP BRIM</span><span class="desc">SAP-basierte Abrechnungsintegration</span><span class="owner">Team SAP (extern)</span></div>
|
||
<div class="system cat-o2c"><span class="name">APN (Anlagenportal Netz)</span><span class="desc">Vermarktung Serviceeinrichtungen (Gleise, ZA) — Migration TIBCO → Angular/CNP</span><span class="owner">ART APN (36)</span></div>
|
||
<div class="system cat-shared"><span class="name">GretA</span><span class="desc">Grenzlastberechnung — Web-Tool, teilweise zugangsfrei</span><span class="owner">DigiPaLö (11)</span></div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Domäne: Fahrplankonstruktion -->
|
||
<div class="domain">
|
||
<div class="domain-header" onclick="this.parentElement.classList.toggle('open')">
|
||
<h2>📐 Fahrplankonstruktion & Umjahrkonstruktion</h2><span class="arrow">▶</span>
|
||
</div>
|
||
<div class="domain-body">
|
||
<div class="system cat-c2s"><span class="name">SIC OP (Solution Integration Center)</span><span class="desc">Neue Plattform für UjK — Teams Ains, FaMe, Fuse migrieren dorthin</span><span class="owner">ART Uj Konstruktion (153)</span></div>
|
||
<div class="system cat-c2s"><span class="name">IFP (Integrierte Fahrplan Plattform)</span><span class="desc">Legacy-Plattform — wird schrittweise nach SIC OP migriert</span><span class="owner">ART Uj Konstruktion</span></div>
|
||
<div class="system cat-c2s"><span class="name">KonBel</span><span class="desc">Konstruktionsbelegung — Kernsystem Taktfahrplan</span><span class="owner">ART SuN (122)</span></div>
|
||
<div class="system cat-c2s"><span class="name">TAKT</span><span class="desc">Taktfahrplan-System (iTraiN, Infrastruktur-Prüfset)</span><span class="owner">ART SuN – Konnex</span></div>
|
||
<div class="system cat-c2s"><span class="name">TTTneo</span><span class="desc">Neue Trassenbelegung (Legacy-Ablöse) — Projekt + Team Nordstern</span><span class="owner">TTT-Projekt (8) + EKon</span></div>
|
||
<div class="system cat-c2s"><span class="name">strecken.zeit</span><span class="desc">Streckenöffnungszeiten (4.400+ Betriebsstellen) — fachlich Fahrplan & Kapazität</span><span class="owner">Stream 3 (IST: DigiPaLö)</span></div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Domäne: Fahrplan-Veröffentlichung -->
|
||
<div class="domain">
|
||
<div class="domain-header" onclick="this.parentElement.classList.toggle('open')">
|
||
<h2>📢 Fahrplan-Veröffentlichung & Kommunikation</h2><span class="arrow">▶</span>
|
||
</div>
|
||
<div class="domain-body">
|
||
<div class="system cat-c2s"><span class="name">GFD-Z / GFD-I</span><span class="desc">Gemeinsame Fahrplandaten (Zugdaten / Infrastruktur)</span><span class="owner">ART Uj Veröffentlichung (80)</span></div>
|
||
<div class="system cat-c2s"><span class="name">Regelkommunikation</span><span class="desc">Kundenkommunikation Fahrplan (6 Teams)</span><span class="owner">ART KOM (64)</span></div>
|
||
<div class="system cat-c2s"><span class="name">FSTOR</span><span class="desc">Fahrplan-Storage</span><span class="owner">FSTOR-Team (6)</span></div>
|
||
<div class="system cat-shared"><span class="name">PlaTo</span><span class="desc">Planungsparameter-Veröffentlichung + Stellungnahmeverfahren</span><span class="owner">DigiPaLö (11)</span></div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Domäne: Kapazitätsmanagement -->
|
||
<div class="domain">
|
||
<div class="domain-header" onclick="this.parentElement.classList.toggle('open')">
|
||
<h2>📊 Kapazitätsmanagement & Konflikt</h2><span class="arrow">▶</span>
|
||
</div>
|
||
<div class="domain-body">
|
||
<div class="system cat-c2s"><span class="name">CMDP (CM Data Platform)</span><span class="desc">Datenplattform für Kapazitätsmanagement — Teams Crush + Marlin</span><span class="owner">ART CM (44)</span></div>
|
||
<div class="system cat-c2s"><span class="name">InKa (Integrierte Kapazitätsmanagementplattform)</span><span class="desc">Auslastungscockpit, Baucockpit, Segmentierung — Nachfolger Netzmonitor + KatAna</span><span class="owner">ART CM / Team CMDP</span></div>
|
||
<div class="system cat-c2s"><span class="name">Analytics Dashboards</span><span class="desc">Kapazitäts-Dashboards</span><span class="owner">ART CM – Team Analytics</span></div>
|
||
<div class="system cat-c2s"><span class="name">KuK-Systeme</span><span class="desc">Kapazität und Konflikt — 4 Teams (Cortex, Hippocampus, Iris, Thalamus)</span><span class="owner">ART KuK (40)</span></div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Domäne: Infrastrukturdaten -->
|
||
<div class="domain">
|
||
<div class="domain-header" onclick="this.parentElement.classList.toggle('open')">
|
||
<h2>🗺️ Infrastrukturdaten & Betrieb</h2><span class="arrow">▶</span>
|
||
</div>
|
||
<div class="domain-body">
|
||
<div class="system cat-c2s"><span class="name">IDBF (Der Infrastrukturmanager)</span><span class="desc">Portal + API + Datenplattform für Infrastrukturdaten — dbt, CRD, Keycloak</span><span class="owner">ART IDBF (49)</span></div>
|
||
<div class="system cat-shared"><span class="name">iTrace</span><span class="desc">Marktorientierte Infrastrukturentwicklung — Ideen + Maßnahmen + Finanzierung</span><span class="owner">DigiPaLö (11)</span></div>
|
||
<div class="system cat-shared"><span class="name">BAPSI 2.0</span><span class="desc">Baukommunikation Serviceeinrichtungen + Infrastrukturanschlüsse (Import aus BBPneo)</span><span class="owner">DigiPaLö (11)</span></div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Domäne: Bau-Anordnungen -->
|
||
<div class="domain">
|
||
<div class="domain-header" onclick="this.parentElement.classList.toggle('open')">
|
||
<h2>🏗️ Bau-Anordnungen & Regelkommunikation</h2><span class="arrow">▶</span>
|
||
</div>
|
||
<div class="domain-body">
|
||
<div class="system cat-c2s"><span class="name">BBPneo</span><span class="desc">Baubetriebsplanung — BARD-Kernprodukt</span><span class="owner">ART BARD (63)</span></div>
|
||
<div class="system cat-c2s"><span class="name">BARD-Systeme</span><span class="desc">5 Teams (PzE, AST, BaBeDas, FOps, InfraTec) — Bau-Anordnungen</span><span class="owner">ART BARD (63)</span></div>
|
||
<div class="system cat-shared"><span class="name">BAKO</span><span class="desc">Baukommunikation-Tool (Projekt unter Einfachbahn)</span><span class="owner">DigiPaLö</span></div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Domäne: Plattform & Querschnitt -->
|
||
<div class="domain">
|
||
<div class="domain-header" onclick="this.parentElement.classList.toggle('open')">
|
||
<h2>⚙️ Plattform & Querschnitt</h2><span class="arrow">▶</span>
|
||
</div>
|
||
<div class="domain-body">
|
||
<div class="system cat-c2s"><span class="name">C2S Plattform</span><span class="desc">Operations, Core, Enablement, KITE — Self-Service-Tools, CI/CD</span><span class="owner">ART Plattform (47)</span></div>
|
||
<div class="system cat-c2s"><span class="name">QuEST</span><span class="desc">End-to-End System Testing, Qualitätssicherung</span><span class="owner">Team QuEST (17)</span></div>
|
||
<div class="system cat-c2s"><span class="name">Cockpit</span><span class="desc">Solution-Cockpit, Steuerung C2S Portfolio + Performance</span><span class="owner">Cockpit (13)</span></div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Domäne: Data & Analytics -->
|
||
<div class="domain">
|
||
<div class="domain-header" onclick="this.parentElement.classList.toggle('open')">
|
||
<h2>📈 Data & Analytics</h2><span class="arrow">▶</span>
|
||
</div>
|
||
<div class="domain-body">
|
||
<div class="system cat-data"><span class="name">Data Team IWF9 (Ltg. Markus Germany)</span><span class="desc">5 Data Scientists — Abrechnung, Vertriebsdaten, kundenrelevante Daten. Power BI Self-Service. Nicht FINANCE 4 DB.</span><span class="owner">Abteilung IWF9</span></div>
|
||
<div class="system cat-data"><span class="name">Power BI Dashboards (O2C)</span><span class="desc">Organigramme, Value-Team-Übersichten, Auswertungen — Self-Service für Stakeholder</span><span class="owner">Data Team IWF9</span></div>
|
||
<div class="system cat-c2s"><span class="name">CM Business Intelligence</span><span class="desc">BI für Kapazitätsmanagement</span><span class="owner">ART CM – Team BI</span></div>
|
||
<div class="system cat-c2s"><span class="name">CMDP Analytics</span><span class="desc">Analytics Dashboards für CM</span><span class="owner">ART CM – Team Analytics</span></div>
|
||
</div>
|
||
</div>
|
||
|
||
<!-- Lücken -->
|
||
<div class="gap-note">
|
||
<h3>⚠️ Lücken in der architektonischen Sicht — zu vertiefen</h3>
|
||
<ul>
|
||
<li><strong>ART SuN (122 Pers.)</strong> — Welche konkreten Systeme bauen die 8 Teams? KonBel? Welche APIs?</li>
|
||
<li><strong>ART KOM (64 Pers.)</strong> — Welches System/Tool für Regelkommunikation? Welche Schnittstellen?</li>
|
||
<li><strong>ART KuK (40 Pers.)</strong> — Welches System genau? Wie hängt es mit CM zusammen?</li>
|
||
<li><strong>ART Uj Veröffentlichung (80 Pers.)</strong> — Welche Systeme genau? GFD? Andere?</li>
|
||
<li><strong>ART BARD (63 Pers.)</strong> — Neben BBPneo: welche weiteren Tools?</li>
|
||
<li><strong>Schnittstellen zwischen Domänen</strong> — Wer liefert Daten an wen? (z.B. pathOS → AC Trasse, IDBF → Trassenfinder)</li>
|
||
<li><strong>Tech-Stacks pro Team</strong> — Nur für pathOS und APN detailliert bekannt. Rest: GitLab-Analyse nötig.</li>
|
||
<li><strong>DB Planet</strong> — Kein Zugriff von extern (Intranet), manuelle Extraktion nötig.</li>
|
||
</ul>
|
||
</div>
|
||
|
||
<script>
|
||
document.querySelectorAll('.domain').forEach(d => { if(!d.classList.contains('open')) return; });
|
||
</script>
|
||
</body>
|
||
</html>
|