Dataflow: inbound Web API (API key auth) added as a third input to scripts
Topology: API callers shown with two paths — direct to any site cluster
OR routed through central hub to reach sites
- 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
Shows: central 2-node cluster (South Bend), per-building clusters at
Warsaw campuses, single clusters at smaller sites, hub-and-spoke routing
with optional direct site-to-site, co-location on System Platform nodes.
First run of the regeneration pipeline. 18 slides per presentation-spec.md:
title, exec summary, today's reality, vision, three pillars, enterprise
layout, systems, layered architecture (colored boxes), end-to-end data flow,
OtOpcUa, analytics stack, Redpanda EventHub, 3-year roadmap (table),
Year 1 focus, legacy retirement, open coordination items, non-goals,
asks & next steps.
Design: dark navy (#1B2838) for title/vision/closing slides, white for
content, blue (#2980B9) headers, orange (#E67E22) accents.
The OtOpcUa v2 implementation team committed all 8 core drivers from
internal knowledge of the estate, making the formal protocol survey
unnecessary for driver scoping. Removed current-state/equipment-protocol-
survey.md and cleaned up all references across 7 files.
The UNS hierarchy snapshot (per-site equipment-instance walk for site/area/
line/equipment assignments + UUIDs) is now a standalone Year 1 deliverable,
decoupled from protocol discovery. Tracked in status.md and goal-state.md
UNS naming hierarchy section.
Eliminates ~52 TBDs (all placeholder data in the pre-seeded survey rows).
