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

6
goal-state.md
View File

@@ -115,7 +115,7 @@ The plan commits to a **single canonical naming hierarchy** for addressing equip
|---|---|---|---|
| 1 | **Enterprise** | Single root for the whole organization. One value for the entire estate. | **`zb`** — confirmed 2026-04-17 (matches the existing `ZB.MOM.WW.*` namespace prefix used in the codebase; short by design since this segment appears in every equipment path) |
| 2 | **Site** | Physical location. Matches the authoritative site list in [`current-state.md`](current-state.md) → Enterprise Layout. | `south-bend`, `warsaw-west`, `warsaw-north`, `shannon`, `galway`, `tmt`, `ponce`, `berlin`, `winterthur`, `jacksonville`, … |
| 3 | **Area** | A section of the site — typically a **production building** at the Warsaw campuses (which run one cluster per building), or `_default` at sites that have a single cluster covering the whole site. Always present; uniform path depth is a design goal. | `bldg-3`, `bldg-7`, `_default` |
| 3 | **Area** | A section of the site — typically a **production building** at the Warsaw campuses (which run one cluster per building), or `_default` at sites that have a single cluster covering the whole site. Always present; uniform path depth is a design goal. | `bldg-5`, `bldg-19`, `_default` |
| 4 | **Line** | A production line or work cell within an area. One line = one coherent sequence of equipment working together toward a product or sub-assembly. | `line-2`, `assembly-a`, `packout-1` |
| 5 | **Equipment** | An individual machine instance. Equipment class prefix + instance number or shortname. | `cnc-mill-05`, `injection-molder-02`, `vision-system-01` |
@@ -145,8 +145,8 @@ Identical conventions to the existing Redpanda topic naming — one vocabulary,
| Form | Example |
|---|---|
| Text (messages, docs, dbt keys) | `zb.warsaw-west.bldg-3.line-2.cnc-mill-05.spindle-speed` |
| OPC UA browse path | `zb/warsaw-west/bldg-3/line-2/cnc-mill-05/spindle-speed` |
| Text (messages, docs, dbt keys) | `zb.warsaw-west.bldg-5.line-2.cnc-mill-05.spindle-speed` |
| OPC UA browse path | `zb/warsaw-west/bldg-5/line-2/cnc-mill-05/spindle-speed` |
| Same machine at a small site (area placeholder) | `zb.shannon._default.line-1.cnc-mill-03` |
##### Stable equipment identity — path is navigation, UUID is lineage