Expand SnowBridge to own ingest + in-process transform; drop dbt

SnowBridge now owns machine-data ingest, in-process .NET transformation,
and direct writes to curated tables in Snowflake. Collapses the previous
ingest/transform split into a single service; no dbt, no external
orchestrator, no Snowflake landing tier. Keeps the in-house .NET pattern
consistent with ScadaBridge and OtOpcUa.

The "Snowflake dbt Transform Layer" roadmap workstream merges into
SnowBridge (7 → 6 workstreams); Year 2 canonical-state-based OEE moves
with it. Canonical model still has three surfaces — the third is
renamed from "dbt curated layer" to "SnowBridge curated layer in
Snowflake"; mechanics unchanged.
This commit is contained in:
Joseph Doherty
2026-04-24 14:53:16 -04:00
parent 22a86974f6
commit 98bf2d0da4
15 changed files with 130 additions and 124 deletions

View File

@@ -8,7 +8,7 @@ A **stable, single point of integration between shopfloor OT and enterprise IT**
## Three Pillars (binary at end of plan)
1. **Unification** — 100% of sites on the standardized stack (OtOpcUa + ScadaBridge + Redpanda + SnowBridge + Snowflake/dbt).
1. **Unification** — 100% of sites on the standardized stack (OtOpcUa + ScadaBridge + Redpanda + SnowBridge + Snowflake).
2. **Analytics / AI Enablement** — machine data in Snowflake with a ≤15-minute analytics SLO; at least one "not possible before" use case in production.
3. **Legacy Retirement** — zero remaining bespoke IT/OT integration paths outside ScadaBridge.
@@ -23,7 +23,7 @@ Layer 4 ScadaBridge (sole IT/OT crossing point)
Enterprise IT (Camstar, Delmia, Snowflake, Power BI, SnowBridge)
```
The plan also declares a **Unified Namespace (UNS)** composed of OtOpcUa + Redpanda + canonical model in `schemas` repo + dbt curated layer, with a 5-level naming hierarchy standard (Enterprise → Site → Area → Line → Equipment).
The plan also declares a **Unified Namespace (UNS)** composed of OtOpcUa + Redpanda + canonical model in `schemas` repo + SnowBridge curated layer in Snowflake, with a 5-level naming hierarchy standard (Enterprise → Site → Area → Line → Equipment).
## Plan Documents
@@ -31,7 +31,7 @@ The plan also declares a **Unified Namespace (UNS)** composed of OtOpcUa + Redpa
|---|---|
| [`current-state.md`](current-state.md) | Snapshot of today's systems, integrations, and pain points |
| [`goal-state.md`](goal-state.md) | Target end-state: architecture, components, success criteria, UNS, canonical model |
| [`roadmap.md`](roadmap.md) | 7 workstreams x 3 years migration grid |
| [`roadmap.md`](roadmap.md) | 6 workstreams x 3 years migration grid |
| [`STATUS.md`](STATUS.md) | Working-session bookmark — where we left off, pending items |
### Component Detail Files