dohertj2/3yearplan
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix ScadaBridge topology: bldg-5/19, no site-to-site, direct API access

Browse Source 
- Warsaw West buildings corrected to 5 and 19 (was generic 3/7)
- Removed site-to-site direct routing (doesn't exist)
- Added external API callers with direct access to any site cluster
- Updated UNS hierarchy examples to use real building numbers
- Fixed current-state.md routing topology description
This commit is contained in:
Joseph Doherty
2026-04-17 14:40:29 -04:00
parent a73305d54d
commit 3ad275c11e
4 changed files with 14 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
current-state.md
View File

@@ -105,7 +105,7 @@ SCADA responsibilities are split across two platforms by purpose:
- _TBD — other databases written to besides batch tracking, and any additional consumers not listed here. **Enumeration of internal Web API endpoints is not tracked here** because ScadaBridge's Web API client is generic/configurable (see Capabilities); specific IT↔OT Web API crossings that need migration live in `current-state/legacy-integrations.md`. **Notification destination teams are similarly not enumerated** because they're contact-list-driven and transport-agnostic (see Capabilities) — the list of actual recipients lives in ScadaBridge's configuration, not in this plan._
- **Routing topology:**
- **Hub-and-spoke** — ScadaBridge nodes on the **central cluster (South Bend)** can route to ScadaBridge nodes on other clusters, forming a hub-and-spoke network with the central cluster as the hub.
- **Direct access** — site-level ScadaBridge clusters can also be reached directly (not only via the hub), enabling point-to-point integration where appropriate.
- **Direct API access** — external API callers can reach site-level ScadaBridge clusters directly (not only via the hub) using ScadaBridge's inbound Web API. **No direct site-to-site routing** exists between ScadaBridge clusters — inter-site traffic routes through the central hub.
- **Data locality (design principle):** ScadaBridge is designed to **keep local data sources localized** — equipment at a site communicates with the **local ScadaBridge instance** at that site, not with the central cluster. This minimizes cross-site/WAN traffic, reduces latency, and keeps site operations resilient to WAN outages.
- **Deployment status:** ScadaBridge is **already deployed** across the current cluster footprint. However, **not all legacy API integrations have been migrated onto it yet** — some older point-to-point integrations still run outside ScadaBridge and need to be ported. The authoritative inventory of these integrations (and their retirement tracking against `goal-state.md` pillar 3) lives in [`current-state/legacy-integrations.md`](current-state/legacy-integrations.md).
- _TBD — resource impact of co-location with System Platform at the largest sites; whether any additional downstream consumers exist beyond those listed above; whether the notification capability will be extended to support Microsoft Teams (not currently implemented)._