Commit Graph

11 Commits

Author SHA1 Message Date
Joseph Doherty
98bf2d0da4 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.
2026-04-24 14:53:16 -04:00
Joseph Doherty
22a86974f6 Finalize digital-twin scope as two ACL-based patterns
Plan's digital-twin scope is now exactly (1) environment-lifecycle
promotion via ACL flip on write authority and (2) safe read-only
consumption for KPI / monitoring systems — both delivered by
already-committed architecture. Removes the meeting-prep brief and the
management-delivered use-cases source document; canonical model and
state vocabulary stand as pillar-2 work on their own.
2026-04-24 14:13:10 -04:00
Joseph Doherty
7d44802517 Add inbound Web API to ScadaBridge diagrams
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
2026-04-17 14:51:53 -04:00
Joseph Doherty
ca5da81ed0 Add Delmia DNC (direct Web API) to ScadaBridge dataflow diagram 2026-04-17 14:41:33 -04:00
Joseph Doherty
3ad275c11e Fix ScadaBridge topology: bldg-5/19, no site-to-site, direct API access
- 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
2026-04-17 14:40:29 -04:00
Joseph Doherty
a73305d54d Add ScadaBridge topology diagram — clusters, routing, data locality
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.
2026-04-17 14:35:41 -04:00
Joseph Doherty
ab73382679 Simplify EventHub diagram: merge ScadaBridge + store-and-forward 2026-04-17 14:33:34 -04:00
Joseph Doherty
eb61d07ffd Add 5 component data-flow diagrams (Mermaid source + PNG)
- otopcua-dataflow: equipment → drivers (8, with stability tiers) → namespaces → ACL → consumers
- redpanda-eventhub: site ScadaBridge → store-and-forward → central cluster (topics + retention tiers + schema registry) → enterprise consumers
- snowbridge-dataflow: source adapters (Historian/Redpanda) → governed selection + approval workflow → Snowflake landing
- scadabridge-dataflow: OtOpcUa inputs → scripts/templates → multiple outputs (Redpanda, Web APIs, DB, email, equipment writes, Camstar)
- snowflake-dbt-dataflow: landing → staging → curated layer (dim_equipment, fact_state_transitions, mart_oee) → Power BI / AI/ML / ad-hoc
2026-04-17 14:24:45 -04:00
Joseph Doherty
658de96849 Generate first PPTX: 18-slide mixed-stakeholder deck
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.
2026-04-17 13:49:55 -04:00
Joseph Doherty
bed8c8e12b Remove equipment protocol survey — driver list confirmed by v2 team
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).
2026-04-17 11:54:46 -04:00
Joseph Doherty
ec1dfe59e4 Initial commit: 3-year shopfloor IT/OT transformation plan
Core plan: current-state, goal-state (layered architecture, OtOpcUa,
Redpanda EventHub, SnowBridge, canonical model, UNS posture + naming
hierarchy, digital twin use cases absorbed), roadmap (7 workstreams x 3
years), and status bookmark.

Component detail files: legacy integrations inventory (3 integrations,
pillar 3 denominator closed), equipment protocol survey template (dual
mandate with UNS hierarchy snapshot), digital twin management brief
(conversation complete, outcome recorded).

Output generation pipeline: specs for 18-slide mixed-stakeholder PPTX
and faithful-typeset PDF, with README, design doc, and implementation
plan. No generated outputs yet — deferred until source data is stable.
2026-04-17 09:12:35 -04:00