Seed UNS hierarchy across 6 sites; rebrand outputs to SCADA IT/OT with ZB template

Lands per-site UNS subtree files (Warsaw West/North, Shannon, Galway, TMT,
Ponce) seeded from OpenText facility docs — Warsaw split confirmed as
numbered = legacy Zimmer = West, lettered = legacy Biomet = North. Renames
project framing from "Shopfloor IT/OT" to "SCADA IT/OT" for accuracy.
Extracts a ZB-branded PowerPoint template from example_powerpoint.pptx and
wires it into the outputs pipeline. Trims deck from 18 to 16 slides
(BOBJ->Power BI transferred to another team, Non-Goals and Asks dropped);
goal-state BOBJ analysis pruned to a stub.

STATUS.md

@@ -1,7 +1,7 @@
 # Plan — Working Session Status
 
-**Saved:** 2026-04-24 (second session of the day)
-**Previous session:** Opus 4.6 (1M context)
+**Saved:** 2026-04-30
+**Previous session:** Opus 4.7 (1M context)
 **Resume with:** start a new Claude Code session in this directory — `CLAUDE.md` and this file provide full context. No session ID needed; the plan is self-contained in the repo.
 
 > This file is a **bookmark**, not a replacement for the plan. The authoritative content lives in `CLAUDE.md`, `current-state.md`, `goal-state.md`, `roadmap.md`, and the component detail files under `current-state/` and `outputs/`. Read this file only to find out where we left off.
@@ -13,7 +13,7 @@ The plan is **substantially complete**. All core documents are populated, archit
 **What happened since the original session (2026-04-15 through 2026-04-24):**
 - Integrated OtOpcUa v2 implementation corrections (19 corrections + hardening addendum: ACL model committed, stability tiers, multi-identifier equipment model, driver list confirmed, cutover ownership assigned outside OtOpcUa)
 - Schemas repo seed contributed by OtOpcUa team at `schemas/` (temporary location)
-- Enterprise shortname resolved to `zb`; Warsaw West buildings confirmed as 5 and 19
+- Enterprise shortname resolved to `zb` (= Zimmer Biomet); Warsaw West = numbered buildings (legacy Zimmer); Warsaw North = lettered buildings (legacy Biomet) — confirmed via OpenText Building Use Descriptions doc + project-owner verbal confirmation 2026-04-30
 - Equipment protocol survey removed (driver list confirmed directly by v2 team)
 - First PPTX generated (18 slides, mixed-stakeholder deck)
 - 7 component diagrams created (OtOpcUa, Redpanda, SnowBridge, ScadaBridge dataflow + topology, Snowflake/dbt — dbt diagram is now stale; next regen will replace)
@@ -66,12 +66,11 @@ The plan is **substantially complete**. All core documents are populated, archit
 
 ## Top pending items (from most recent status check)
 
-All four items from the previous status check have been **advanced to the point where the next move is a real-world action** (management meeting, reporting-team conversation, field survey, or — for legacy — closed outright). The in-room plan work that could be done without external input has been done. The remaining open items are **external dependencies**, not plan-authoring gaps.
+The in-room plan work that could be done without external input has been done. The remaining open item is an **external dependency**, not a plan-authoring gap. The BOBJ → Power BI coordination — previously the other open item — is now formally owned by another team and no longer tracked here.
 
 ### External-dependency items — waiting on real-world action
 
-1. **BOBJ → Power BI coordination with reporting team.** Plan position documented in `goal-state.md` → Strategic Considerations → **Enterprise reporting: BOBJ → Power BI migration (adjacent initiative)** — three consumption paths analyzed, recommended position stated (Path C with Path A as strategic direction), eight questions and a four-bucket decision rubric included. **Action needed:** schedule the coordination conversation with the reporting team; bring back a bucket assignment. Once a bucket is assigned, update `goal-state.md` → Enterprise reporting and, if the outcome is Bucket A or B, update `roadmap.md` → SnowBridge to include reporting-shaped curated tables.
-2. **UNS hierarchy snapshot walk.** The protocol survey has been **removed** — the OtOpcUa v2 implementation team committed the core driver list (8 drivers) based on internal knowledge, making a formal protocol survey unnecessary for driver scoping. What remains is the **UNS hierarchy snapshot**: a per-site equipment-instance walk capturing site / area / line / equipment assignments and stable UUIDs, which feeds the initial `schemas` repo hierarchy definition and canonical model. See `goal-state.md` → **Unified Namespace (UNS) posture → UNS naming hierarchy standard**. **Action needed:** assign a walk owner; walk System Platform IO config, Ignition OPC UA connections, and ScadaBridge templates across integrated sites within Q1–Q2 of Year 1; capture equipment instances at site/area/line/equipment granularity (not protocol — that's already resolved). The canonical model v1 cannot be published without the initial hierarchy snapshot. **Sub-blocker:** the UNS hierarchy's enterprise-level shortname is currently a placeholder (`ent` in goal-state.md); the real shortname needs to be assigned before the initial hierarchy snapshot can be committed to the `schemas` repo.
+1. **UNS hierarchy snapshot walk.** The protocol survey has been **removed** — the OtOpcUa v2 implementation team committed the core driver list (8 drivers) based on internal knowledge, making a formal protocol survey unnecessary for driver scoping. What remains is the **UNS hierarchy snapshot**: a per-site equipment-instance walk capturing site / area / line / equipment assignments and stable UUIDs, which feeds the initial `schemas` repo hierarchy definition and canonical model. See `goal-state.md` → **Unified Namespace (UNS) posture → UNS naming hierarchy standard**. **Initial structural draft seeded 2026-04-30** at `schemas/uns/` — per-site subtree files for Warsaw West (with confirmed buildings 5 and 19), Shannon, Galway, TMT, and Ponce (single-cluster sites with `_default` area). Warsaw North is **not yet drafted** because the campus building set is unknown — that's the primary blocker. Lines and equipment are pending the walk across all sites. Follow-up questions captured in [`schemas/uns/QUESTIONS.md`](schemas/uns/QUESTIONS.md). **Action needed:** (a) answer Warsaw North's building set (Q1) so `warsaw-north.json` can be drafted; (b) ratify naming-convention questions Q2, Q5, Q6, Q9 so the walk's output schema is stable; (c) assign a walk owner; (d) walk System Platform IO config, Ignition OPC UA connections, and ScadaBridge templates across integrated sites within Q1–Q2 of Year 1 to populate `lines` and equipment instances. The canonical model v1 cannot be published without the populated hierarchy. **Resolved sub-blocker:** the enterprise shortname is `zb` (no longer a placeholder).
 ### Closed since last status check
 
 All closed items below were worked through the same 2026-04-15 session. Grouped roughly chronologically.
@@ -93,7 +92,8 @@ All closed items below were worked through the same 2026-04-15 session. Grouped
 
 **Adjacent initiatives:**
 
-- ~~**BOBJ → Power BI coordination framing.**~~ **Advanced 2026-04-15.** The coordination question was flagged but no plan position existed; now documented as a new Strategic Considerations subsection in `goal-state.md` with three paths, recommended position, and eight questions for the reporting team. Still open: actually having the coordination conversation (tracked above as item #1).
+- ~~**BOBJ → Power BI coordination framing.**~~ **Advanced 2026-04-15.** The coordination question was flagged but no plan position existed; now documented as a new Strategic Considerations subsection in `goal-state.md` with three paths, recommended position, and eight questions for the reporting team.
+- ~~**BOBJ → Power BI coordination conversation.**~~ **Closed 2026-04-30.** Coordination is being handled by another team — no longer an open action item for this plan. Plan's posture is unchanged: the SnowBridge curated layer in Snowflake is shaped to serve Power BI cleanly if and when the reporting team chooses to point there. If that team's decision lands on Path A or C and reporting-shaped curated tables are needed, fold those requirements into the SnowBridge workstream at that time. Resolution recorded in `goal-state.md` → Strategic Considerations → Enterprise reporting → Coordination ownership.
 
 **Output generation pipeline:**
 
@@ -105,10 +105,10 @@ Items that can wait, design details that close during implementation, and delibe
 
 1. Start a new Claude Code session in this directory. `CLAUDE.md` and this file provide full context.
 2. Skim this file to re-orient (~2 minutes).
-3. Pick one of the three external-dependency items above — or whatever has become most pressing.
-4. If you've had the Power BI coordination conversation with the reporting team, bring the answers and I'll fold them into the plan.
-5. If a funded physics-simulation / FAT initiative has materialized (out of current plan scope), say so and I'll reuse the meeting brief for a scoping conversation.
-6. If the UNS hierarchy walk has been run, bring the data and I'll populate the initial hierarchy snapshot in the `schemas` repo.
+3. Pick the open external-dependency item above — or whatever has become most pressing.
+4. If a funded physics-simulation / FAT initiative has materialized (out of current plan scope), say so and I'll reuse the meeting brief for a scoping conversation.
+5. If the UNS hierarchy walk has been run, bring the data and I'll populate the initial hierarchy snapshot in the `schemas` repo.
+6. If the other team's BOBJ → Power BI decision lands on Path A or C and reporting-shaped curated tables are needed, bring the requirements and I'll fold them into the SnowBridge workstream.
 7. To regenerate outputs: `regenerate presentation` (PPTX), `regenerate longform` (PDF, not yet run), or `regenerate outputs` (both). See `outputs/README.md` for the full checklist.
 8. To hand off a component to an implementation agent, check `handoffs/` for existing handoff docs or ask me to create one.