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.
This commit is contained in:
Joseph Doherty
87
schemas/uns/HIERARCHY.md
Normal file
87
schemas/uns/HIERARCHY.md
Normal file
@@ -0,0 +1,87 @@
|
||||
# UNS Hierarchy — High-Level View
|
||||
|
||||
> **Status: WIP draft (2026-04-30).** Levels 1–3 (Enterprise → Site → Area) drafted across all 6 currently-integrated SCADA sites. Level 4 (Line) and Level 5 (Equipment) pending the per-site discovery walk. Authoritative per-site source files live alongside this document at `<site>.json`. See [`README.md`](README.md) for status, [`QUESTIONS.md`](QUESTIONS.md) for open design questions, [`portal-queries.md`](portal-queries.md) for OpenText / corporate-doc lookups.
|
||||
|
||||
## Hierarchy levels (per `goal-state.md`)
|
||||
|
||||
| Level | Name | Always present | Notes |
|
||||
|------:|------|---------------|-------|
|
||||
| 1 | Enterprise | yes | `zb` (Zimmer Biomet) |
|
||||
| 2 | Site | yes | `warsaw-west`, `warsaw-north`, `shannon`, `galway`, `tmt`, `ponce` |
|
||||
| 3 | Area | yes | `bldg-N` at multi-cluster Warsaw campuses; `_default` at single-cluster sites |
|
||||
| 4 | Line | yes | pending walk (will be `line-1` / `line-2` / process-name) |
|
||||
| 5 | Equipment | yes | pending walk (will be `cnc-mill-05` / equivalent class-counter form) |
|
||||
|
||||
Path serialization: dots in messages and curated-table keys (`zb.warsaw-west.bldg-5.line-2.cnc-mill-05`); slashes in OPC UA browse paths (`zb/warsaw-west/bldg-5/line-2/cnc-mill-05`).
|
||||
|
||||
## High-level — all 6 currently-integrated sites
|
||||
|
||||
```
|
||||
zb (Zimmer Biomet — Enterprise)
|
||||
├── warsaw-west Warsaw West Campus (legacy Zimmer, Warsaw IN, multi-cluster)
|
||||
├── warsaw-north Warsaw North Campus (legacy Biomet, Warsaw IN, multi-cluster)
|
||||
├── shannon Shannon (Ireland, single cluster)
|
||||
├── galway Galway (Ireland, single cluster)
|
||||
├── tmt Zimmer Trabecular Metal Technology (NJ USA, single cluster)
|
||||
└── ponce Zimmer Manufacturing B.V. (ZMBV) (Puerto Rico, single cluster)
|
||||
```
|
||||
|
||||
The Warsaw campuses are physically adjacent in Warsaw, IN; the West/North split traces to the 2015 Zimmer-Biomet merger of two pre-existing sites. The legacy origin shows up durably in the building-naming convention (numbers vs. letters) — see Warsaw expanded view below.
|
||||
|
||||
**Not yet integrated** (and therefore deliberately not in this hierarchy): Berlin, Winterthur, Jacksonville, Dover OH, Statesville NC, Calabasas / Carlsbad CA, Mercedita PR, the NJ TMT subsidiary sites (Allendale, Cedar Knolls, Parsippany), and others. These get added to the hierarchy as they onboard via the standardized stack.
|
||||
|
||||
## Warsaw expanded (worked example)
|
||||
|
||||
```
|
||||
zb
|
||||
├── warsaw-west Warsaw West Campus (legacy Zimmer)
|
||||
│ ├── bldg-2 Bone Cement, Packaging Clean Rooms
|
||||
│ ├── bldg-5 Main mfg facility (Foundry, R&D, Quality)
|
||||
│ ├── bldg-7 Tool Support, Upper Extremity Manufacturing
|
||||
│ ├── bldg-10 Hip and Knee Manufacturing, Packaging Clean Rooms
|
||||
│ ├── bldg-19 Trauma HQ + Trauma/Instrument/Knee&Hip Mfg, Foundry
|
||||
│ └── bldg-20 Sheet Metal, Scrap Salvage, Warehousing
|
||||
│
|
||||
└── warsaw-north Warsaw North Campus (legacy Biomet)
|
||||
├── bldg-a (3 floors; production-vs-non-production TBD)
|
||||
├── bldg-b (2 floors; TBD)
|
||||
├── bldg-c (TBD)
|
||||
├── bldg-d (TBD)
|
||||
├── bldg-e (TBD)
|
||||
└── bldg-i (2 floors; F/G/H gap to verify, TBD)
|
||||
```
|
||||
|
||||
**What an end-to-end path will look like** once Lines and Equipment are walked (illustrative — not yet committed):
|
||||
|
||||
```
|
||||
zb.warsaw-west.bldg-5.line-2.cnc-mill-05.spindle-speed
|
||||
zb/warsaw-west/bldg-5/line-2/cnc-mill-05/spindle-speed (OPC UA form)
|
||||
```
|
||||
|
||||
Each `cnc-mill-05`-style equipment node also carries a stable **UUIDv4** alongside the path, per `goal-state.md` → UNS naming hierarchy. The path is for navigation; the UUID is for lineage across renames or building moves.
|
||||
|
||||
## Single-cluster sites (`_default` Area)
|
||||
|
||||
All four single-cluster sites use the explicit `_default` placeholder at the Area level — the goal-state requires uniform path depth:
|
||||
|
||||
```
|
||||
zb.shannon._default.<line>.<equipment>
|
||||
zb.galway._default.<line>.<equipment>
|
||||
zb.tmt._default.<line>.<equipment>
|
||||
zb.ponce._default.<line>.<equipment>
|
||||
```
|
||||
|
||||
When a single-cluster site grows to justify multiple Areas (e.g., adds a second production building), `_default` is replaced by the new named area in a single PR; the equipment UUIDs stay stable, the path updates in `dim_equipment` as a historical version. See `goal-state.md` → UNS naming hierarchy → "Area placeholder → named area promotion".
|
||||
|
||||
## What's intentionally not here
|
||||
|
||||
- **Non-production buildings.** Areas at multi-cluster sites are production buildings only. Warsaw's offices (bldg-3), distribution center (bldg-4), Z Hotel (bldg-15), residential (bldg-18), airport hangar (bldg-14), etc. do not appear — they don't host equipment that lands in the canonical model.
|
||||
- **Auxiliary / outlying Warsaw buildings** (Cessna, 508 Detroit Street, Armstrong Road properties). Listed in the Real Estate inventory but not classified West/North per the building-naming convention; treated as separate from the main campuses pending walk verification.
|
||||
- **Not-yet-integrated sites.** The plan's design is to grow this hierarchy as sites onboard, not to enumerate the full Zimmer Biomet manufacturing footprint upfront.
|
||||
- **Sub-line groupings (cells, stations, work centers).** The 5-level hierarchy is fixed at Enterprise/Site/Area/Line/Equipment. Cells live below Line, encoded in equipment names (e.g., `cell-3-cnc-mill-05`) per the QUESTIONS.md Q6 default; not added as a 4.5 level unless a real driver appears.
|
||||
- **Product / job hierarchy.** That's Camstar MES territory, not UNS — see `goal-state.md` → UNS naming hierarchy → out-of-scope list.
|
||||
|
||||
## What this doc is and isn't
|
||||
|
||||
- **Is:** a one-page consolidated view of the Enterprise/Site/Area state, suitable for stakeholders who don't want to read the per-site JSON files.
|
||||
- **Isn't:** the source of truth. The per-site `<site>.json` files are. This doc is regenerated from those (currently by hand; a generator may be added later).
|
||||
136
schemas/uns/QUESTIONS.md
Normal file
136
schemas/uns/QUESTIONS.md
Normal file
@@ -0,0 +1,136 @@
|
||||
# UNS Hierarchy — Follow-up Questions
|
||||
|
||||
> **Purpose:** open questions that need answers before the per-site UNS subtree files in this directory can be finalized. Capturing them up front so the hierarchy walk doesn't have to be redone if a convention changes mid-walk. Once a question is answered, fold the answer into the relevant subtree file (and into `goal-state.md` → UNS naming hierarchy standard if the answer changes a global convention).
|
||||
|
||||
## Owner
|
||||
|
||||
The schemas-repo owner team (TBD per `../README.md` open questions). Until ownership is named, these questions sit with the 3-year-plan author.
|
||||
|
||||
## Status legend
|
||||
|
||||
- **OPEN** — needs an answer before the walk produces stable output.
|
||||
- **OPEN — informational** — answer would help but the walk can proceed without it; resolve later.
|
||||
- **DEFERRED** — answered "later" by the goal-state spec; included here so the walk team doesn't reopen it.
|
||||
|
||||
---
|
||||
|
||||
## Site-level questions
|
||||
|
||||
### Q1 — Warsaw North building set (OPEN — blocks `warsaw-north.json`)
|
||||
|
||||
Warsaw North is a campus running per-building clusters (per `current-state.md` → Largest Sites). What is the authoritative list of **production-building numbers** at Warsaw North? (Warsaw West is confirmed as buildings **5** and **19**.) Building numbers are needed before `warsaw-north.json` can be authored — using `_default` would be structurally wrong for a multi-cluster campus.
|
||||
|
||||
**Sub-question:** are non-production buildings on the Warsaw campuses (offices, warehouses, labs, utilities) ever expected to host equipment that lands in the UNS? If yes, the area set widens beyond production buildings. If no (likely), the rule is "Areas at Warsaw campuses = production buildings only" and we capture that explicitly.
|
||||
|
||||
### Q2 — Site shortname conventions (OPEN — informational, blocks `tmt.json` confidence)
|
||||
|
||||
The current draft uses `warsaw-west`, `warsaw-north`, `shannon`, `galway`, `tmt`, `ponce` as site segments. **Are these the canonical shortnames?** Specifically:
|
||||
|
||||
- **TMT** — is this an acronym, and if so should the UNS segment be the acronym (`tmt`) or an expanded form? Site-name uniqueness across the org is the only hard constraint; readability is secondary.
|
||||
- Does the org have an established **site-code system** (e.g., 3-letter site codes used by IT/HR/finance) that the UNS should align with rather than invent its own naming? If yes, switching now is cheap; switching later is not.
|
||||
- **Capitalization in `displayName`** — is "TMT" the right display form, or does it expand to a longer name in stakeholder-facing artifacts?
|
||||
|
||||
### Q3 — Multi-floor / multi-tenant production buildings (OPEN — informational)
|
||||
|
||||
Are any production buildings (Warsaw or otherwise) split across multiple floors with **distinct production processes per floor**? If yes, does floor become an Area-equivalent (i.e., `bldg-5-floor-2`) or a Line-level distinction? Recommendation: keep Area at the building level and let Line names carry floor distinctions when needed (`line-2-mezzanine`) — but worth confirming before the walk.
|
||||
|
||||
### Q4 — Sites not yet integrated (DEFERRED)
|
||||
|
||||
Berlin, Winterthur, Jacksonville, and other unintegrated smaller sites are deliberately not seeded. The walk does not cover them. The site-list volatility note in `current-state.md` applies — wait until each site has firm onboarding scope before authoring its subtree.
|
||||
|
||||
---
|
||||
|
||||
## Line-level questions
|
||||
|
||||
### Q5 — Line naming convention (OPEN — must be settled before walk produces line names)
|
||||
|
||||
Two reasonable patterns appear in the current `goal-state.md` examples:
|
||||
|
||||
- **Numeric** — `line-1`, `line-2`, ... — site-stable, terse, but loses semantic info.
|
||||
- **Process-named** — `assembly-a`, `packout-1`, `injection-2` — readable, but requires a controlled vocabulary so two sites don't end up with `assembly-a` meaning different things in different contexts.
|
||||
|
||||
**Recommended convention to ratify:** allow either form, but **prefer numeric-with-displayName-carrying-process** (`name: "line-2"`, `displayName: "Line 2 — Machining"`). Numeric for the path (machine-stable, site-locally-unique); process info in the displayName (operator-readable). The walk should default to numeric `line-N` and capture the process description in `displayName`.
|
||||
|
||||
**Sub-question:** when a site's existing line numbering (per System Platform / Ignition) is non-contiguous or uses internal codes (e.g., `MX-204`), do we (a) preserve the existing identifier verbatim as the line name (after kebab-casing) or (b) renumber to sequential `line-N` and stash the legacy identifier in displayName? Recommendation: **(a) preserve** — renaming creates lineage churn and breaks operator mental model. Confirm before the walk.
|
||||
|
||||
### Q6 — Line vs. cell vs. work center (OPEN — must be settled before walk)
|
||||
|
||||
The goal-state defines a Line as "a production line **or work cell** within an area." That blurs two concepts:
|
||||
|
||||
- A **line** typically means a full sequence of stations producing a product end-to-end.
|
||||
- A **work cell** is often a smaller grouping (one to a few machines) operating semi-autonomously.
|
||||
|
||||
**Question:** is the UNS Line level `(a)` always the full-line concept (cells live below it, possibly as part of equipment naming), `(b)` always the smallest-named-grouping (so a four-cell line shows up as four UNS lines), or `(c)` whichever the site's own taxonomy uses (which makes the level non-uniform across sites)? Recommendation: **(a) full-line** for uniformity, with cells encoded in equipment names (`cell-3-cnc-mill-05`) — but confirm. Sub-line groupings can also be supported by an optional 4.5-level convention if it ever proves necessary, but we should not introduce that without a real driver.
|
||||
|
||||
### Q7 — Multi-product lines and changeovers (OPEN — informational)
|
||||
|
||||
When a single physical production line runs different products on different shifts or after changeover, does that line stay one UNS Line (recommended — physical reality drives the path) or split into one Line per product (not recommended — would shift paths on every changeover)? Recommendation: **one UNS Line per physical line**, with product association captured at the **canonical event level** (the running work-order / product-id is in the message, not the topic / path). Confirm.
|
||||
|
||||
### Q8 — Lines that span buildings (OPEN — informational)
|
||||
|
||||
If a production flow physically crosses building boundaries on a Warsaw campus (e.g., front-end machining in bldg-5, finishing in bldg-19, joined by manual transport), is that **one logical line spanning two areas** (which the 5-level hierarchy can't directly express — each line lives under exactly one area) or **two coupled lines, one per area**? Recommendation: **two lines, coupled by canonical workorder events** — keep the hierarchy strict and let the event stream carry cross-building flow. Confirm.
|
||||
|
||||
---
|
||||
|
||||
## Equipment-level questions (level 5)
|
||||
|
||||
These don't block the walk's higher-level output but should be settled before equipment names are committed, since the walk also captures equipment instances.
|
||||
|
||||
### Q9 — Equipment leaf naming convention (OPEN — must be settled before walk commits equipment names)
|
||||
|
||||
The goal-state example uses `cnc-mill-05`. Pattern appears to be `{class-shortname}-{counter}`. Questions:
|
||||
|
||||
1. **Counter scope** — is `05` unique within the line, the site, or the enterprise? Recommendation: **unique within the (site, area, line) triple** — the path itself disambiguates across sites. Enterprise-wide uniqueness is provided by the **UUID**, not the leaf name; trying to make leaf names enterprise-unique fights with operator readability.
|
||||
2. **Class-shortname source** — does it come from the equipment-class file's `classId` (e.g., `fanuc-cnc` → `fanuc-cnc-05`) or a class-defined display shortname (`cnc-mill-05`)? Recommendation: a separate `pathShortname` field on the equipment-class definition, distinct from `classId`. Add this to the equipment-class schema once confirmed.
|
||||
3. **Asset-tag-based naming** — some sites have existing physical asset tags on equipment (e.g., `WW-CNC-204`). Should the UNS leaf name preserve that tag (after kebab-casing) or use the class-counter pattern with the asset tag captured as another equipment identifier alongside UUID? Recommendation: **class-counter pattern in the path; asset tag stored as an equipment-level identifier alongside UUID and EquipmentId**. The path is for navigation, the identifiers are for lineage / cross-system joins.
|
||||
|
||||
### Q10 — Mobile or portable equipment (OPEN — informational)
|
||||
|
||||
Some equipment is portable and moves between lines (e.g., a calibration rig, a mobile inspection station). Does it:
|
||||
|
||||
- (a) Get a stable home line and stay on that path even when physically elsewhere?
|
||||
- (b) Get re-pathed each time it moves (UUID stays stable, path changes — supported by the Area-promotion governance pattern in `goal-state.md`)?
|
||||
- (c) Live at `_default` line as "site-level shared equipment"?
|
||||
|
||||
Recommendation: **(a) with a "shared" home line per site** (`_default` line if no better fit) — minimizes path churn. Confirm.
|
||||
|
||||
### Q11 — Non-production equipment (utilities, monitoring, support) (OPEN — informational)
|
||||
|
||||
Compressed-air compressors, chillers, building-monitoring sensors, lab equipment — does this surface in the UNS?
|
||||
|
||||
- (a) Yes, with a `support` or `utilities` line per area: `zb.warsaw-west.bldg-5.utilities.compressor-01`.
|
||||
- (b) Yes, on `_default` line: `zb.warsaw-west.bldg-5._default.compressor-01`.
|
||||
- (c) No — out of UNS scope; surfaced through a separate channel.
|
||||
|
||||
Recommendation: **(a) with a reserved line name** (`utilities`, `support`, `lab`, etc. — short list to be ratified). Out-of-scope is wrong because these *do* feed analytics (energy, OEE-adjacent metrics). `_default` is wrong because that placeholder is reserved for "level not applicable." Confirm and add the reserved line names to the global rules.
|
||||
|
||||
---
|
||||
|
||||
## Cross-level questions
|
||||
|
||||
### Q12 — Lines / equipment shared across sites (OPEN — informational, low-frequency)
|
||||
|
||||
Are there any equipment items that are physically singular but logically shared across multiple sites (e.g., a corporate lab in South Bend whose results feed multiple sites)? If yes, where does it sit in a per-site hierarchy? Recommendation: **path under its physical site; logical sharing handled at the canonical-event consumer level, not in the path**. Confirm if any such cases exist.
|
||||
|
||||
### Q13 — Hierarchy change governance (OPEN — informational, will be settled when ownership is named)
|
||||
|
||||
`goal-state.md` already commits to: Area-placeholder → named-area promotion via PR; UUID stable across path changes; `dim_equipment` in Snowflake retains historical paths. Open: **who reviews and approves a hierarchy change PR?** A site's own SMEs only? A central data-governance group? The schemas-repo owner team alone? Will resolve when the schemas-repo owner team is named.
|
||||
|
||||
### Q14 — Synthetic / aggregate equipment nodes (OPEN — informational)
|
||||
|
||||
Will the UNS ever need to expose **synthetic equipment** — e.g., a virtual "line-level OEE node" that publishes computed metrics derived from the underlying equipment? If yes, does it follow the same path/UUID rules as physical equipment, or sit in a different namespace? Recommendation: **same rules, with equipment-class metadata flagging it as synthetic**; physical vs synthetic is a property of the class, not a hierarchy distinction. Defer the decision until a real synthetic-equipment use case appears (likely with the canonical state vocabulary's OEE work in Year 1–2).
|
||||
|
||||
---
|
||||
|
||||
## How to use this list during the walk
|
||||
|
||||
1. Before starting per-site walks, get answers to **Q1, Q2, Q5, Q6, Q9** — these shape the walk's output schema.
|
||||
2. Q3, Q7, Q8, Q10, Q11 can be resolved by the walk team applying the recommended defaults; raise back to this list only if a site's reality contradicts the default.
|
||||
3. Q12, Q13, Q14 do not block the walk. Resolve later.
|
||||
4. As each question is closed, move it to a **Resolved** section at the bottom (with the resolution and the file(s) updated) so the audit trail is preserved.
|
||||
|
||||
---
|
||||
|
||||
## Resolved
|
||||
|
||||
_(empty — populate as questions are closed)_
|
||||
39
schemas/uns/README.md
Normal file
39
schemas/uns/README.md
Normal file
@@ -0,0 +1,39 @@
|
||||
# UNS Subtrees — initial draft
|
||||
|
||||
> **Status: WORK-IN-PROGRESS draft (2026-04-30).** Initial structural skeleton seeded from the 3-year-plan source files (`current-state.md` enterprise layout + `goal-state.md` UNS naming hierarchy standard) and OpenText facility documentation. Per-site **line and equipment** detail is **not yet populated** — that requires the UNS hierarchy snapshot walk (see `goal-state.md` → "Unified Namespace (UNS) posture → UNS naming hierarchy standard"). See [`QUESTIONS.md`](QUESTIONS.md) for the open questions that block finalization.
|
||||
>
|
||||
> **Quick stakeholder view:** [`HIERARCHY.md`](HIERARCHY.md) — high-level tree across all 6 sites with Warsaw expanded as a worked example.
|
||||
|
||||
This directory holds one JSON file per **integrated site**, declaring the canonical UNS subtree (Enterprise → Site → Area → Line) for that site. Equipment (level 5) is configured per-cluster in OtOpcUa, not declared here.
|
||||
|
||||
## What's drafted
|
||||
|
||||
| Site | File | Source of truth | Notes |
|
||||
|------|------|-----------------|-------|
|
||||
| Warsaw West | [`warsaw-west.json`](warsaw-west.json) | OpenText `Zimmer Warsaw - Building Use Descriptions.docx` + verbal confirmation from project owner (numbered = legacy Zimmer = West Campus) | Six production buildings: `bldg-2`, `bldg-5`, `bldg-7`, `bldg-10`, `bldg-19`, `bldg-20`. Non-production buildings (3, 4, 8, 14, 15, 17, 18) deliberately excluded — Areas are production-only per goal-state. Lines pending walk. |
|
||||
| Warsaw North | [`warsaw-north.json`](warsaw-north.json) | OpenText `Zimmer Biomet Buildings` folder + verbal confirmation (lettered = legacy Biomet = North Campus) | Six lettered buildings: `bldg-a`, `bldg-b`, `bldg-c`, `bldg-d`, `bldg-e`, `bldg-i`. Production-vs-non-production breakdown per building is **not yet known** — all included pending walk. Note F/G/H are absent from the building list; verify whether they exist. |
|
||||
| Shannon | [`shannon.json`](shannon.json) | `current-state.md` other-integrated-sites + "single server cluster covering the whole site" rule | Area = `_default` (single-cluster site). Lines pending walk. |
|
||||
| Galway | [`galway.json`](galway.json) | same | same |
|
||||
| TMT | [`tmt.json`](tmt.json) | same | Area = `_default`. Lines pending walk. **TMT shortname unconfirmed** — see [`QUESTIONS.md`](QUESTIONS.md) Q2. |
|
||||
| Ponce | [`ponce.json`](ponce.json) | same | same |
|
||||
|
||||
The not-yet-integrated smaller sites (Berlin, Winterthur, Jacksonville, others) are deliberately **not seeded** — onboarding shape is still TBD and the site list is volatile per `current-state.md`.
|
||||
|
||||
## What still needs to happen
|
||||
|
||||
1. **Walk integrated sites** to populate the `lines` arrays in each file above. Walk inputs: System Platform IO config, Ignition OPC UA connections, ScadaBridge templates. Walk output: per-site list of production lines with their `name` (kebab-case), `displayName`, and the equipment instances belonging to each line (with stable UUIDs — assigned during the walk, not derived from existing identifiers).
|
||||
2. **Confirm Warsaw North production-vs-non-production breakdown** — the lettered buildings are all in `warsaw-north.json` pending verification of which are actually production. The walk should resolve this; non-production buildings should be removed from the Areas list once identified.
|
||||
3. **Resolve remaining [`QUESTIONS.md`](QUESTIONS.md)** — Q2–Q4 (naming conventions) before authoring real line names, so the walk doesn't have to be redone.
|
||||
4. **Move to a dedicated `schemas` repo** once one is created and an owner team is named. The temporary location under `3yearplan/schemas/` is documented in `../README.md`.
|
||||
|
||||
## Validation
|
||||
|
||||
Each file is validated against [`../format/uns-subtree.schema.json`](../format/uns-subtree.schema.json). Constraints:
|
||||
|
||||
- `enterprise` must equal `zb` across every file (matches `ServerCluster.Enterprise` in OtOpcUa).
|
||||
- `site`, area `name`, and line `name` must match `^[a-z0-9-]{1,32}$` or be the literal `_default`.
|
||||
- `_default` is reserved as the explicit "this level doesn't apply at this site" placeholder, per the goal-state design goal of uniform path depth.
|
||||
|
||||
## Worked examples
|
||||
|
||||
- [`example-warsaw-west.json`](example-warsaw-west.json) — original schema worked example contributed with the seed (uses placeholder bldg-3/bldg-4 — **superseded by the authoritative `warsaw-west.json`** for any actual consumer; kept here for documentation purposes only).
|
||||
12
schemas/uns/galway.json
Normal file
12
schemas/uns/galway.json
Normal file
@@ -0,0 +1,12 @@
|
||||
{
|
||||
"$schema": "../format/uns-subtree.schema.json",
|
||||
"enterprise": "zb",
|
||||
"site": "galway",
|
||||
"displayName": "Galway",
|
||||
"areas": [
|
||||
{
|
||||
"name": "_default",
|
||||
"displayName": "Site (single-cluster — no area distinction)"
|
||||
}
|
||||
]
|
||||
}
|
||||
12
schemas/uns/ponce.json
Normal file
12
schemas/uns/ponce.json
Normal file
@@ -0,0 +1,12 @@
|
||||
{
|
||||
"$schema": "../format/uns-subtree.schema.json",
|
||||
"enterprise": "zb",
|
||||
"site": "ponce",
|
||||
"displayName": "Ponce",
|
||||
"areas": [
|
||||
{
|
||||
"name": "_default",
|
||||
"displayName": "Site (single-cluster — no area distinction)"
|
||||
}
|
||||
]
|
||||
}
|
||||
302
schemas/uns/portal-queries.md
Normal file
302
schemas/uns/portal-queries.md
Normal file
@@ -0,0 +1,302 @@
|
||||
# UNS Hierarchy — Corporate AI Portal Queries
|
||||
|
||||
> **Purpose:** factual lookup questions to send to the corporate documentation AI portal. These are distinct from [`QUESTIONS.md`](QUESTIONS.md) — that file holds *design / convention* questions for a human owner; this file holds *factual* questions whose answers exist in corporate documentation (site directories, ERP plant master, MES, asset register, plant-engineering docs, etc.).
|
||||
>
|
||||
> **How to use:** fire each question at the portal independently. Paste the response under the question (in the **Response** block) as it comes back. Once a question is answered, fold the answer into the relevant subtree file (`warsaw-west.json`, `warsaw-north.json`, etc.) and/or into [`QUESTIONS.md`](QUESTIONS.md) if it resolves a design question.
|
||||
>
|
||||
> **Drafted:** 2026-04-30. **First answers folded in 2026-04-30** from OpenText Content Management CE 25.3 (`livelink.nam.zimmer.com`) browse session — the AI portal does not index OpenText, so this content was extracted via browser automation against folders we have access to (read-only, no downloads).
|
||||
>
|
||||
> **Source convention:** answers tagged `[OpenText: <breadcrumb>]` cite the OpenText folder/document path; `[AI portal]` would be from the corporate AI portal (none yet).
|
||||
|
||||
## Priority
|
||||
|
||||
- **High** — directly unblocks a per-site subtree file (Q1, Q2, Q3, Q6, Q7, Q9).
|
||||
- **Medium** — shapes equipment-leaf walk and naming conventions (Q11–Q15).
|
||||
- **Low** — confirms existing-standards alignment, low risk if unanswered (Q4, Q5, Q8, Q10, Q16–Q19).
|
||||
|
||||
---
|
||||
|
||||
## Site list & site codes
|
||||
|
||||
### Q1 — Site list (High) — SUBSTANTIALLY ANSWERED
|
||||
|
||||
What is the authoritative list of manufacturing sites for the company, including which ones are active vs. planned vs. decommissioned, and which region each one belongs to?
|
||||
|
||||
**Response (partial — corporate-entity folders, not necessarily all manufacturing sites):**
|
||||
Top-level folders at `[OpenText: Enterprise]` representing Zimmer business units / sites:
|
||||
- Zimmer Manufacturing B.V. (ZMBV) - Ponce
|
||||
- Zimmer Shannon
|
||||
- Zimmer TMT (Trabecular Metal Technology)
|
||||
- Synvasive Reno
|
||||
- Zimmer Austin Orthopedic
|
||||
- Zimmer Beijing
|
||||
- Zimmer Biomet Guaynabo (Puerto Rico)
|
||||
- Zimmer CAS
|
||||
- Zimmer Dental
|
||||
- Zimmer Spine
|
||||
- Zimmer Surgical
|
||||
- Zimmer Trauma
|
||||
|
||||
Plus regional/grouping folders: Asia Pacific, Canada, Departments. The **Warsaw, IN headquarters** (with West Campus and North Campus) does not appear at this level — its content lives under `Business Teams > Real Estate and Facilities > Warsaw Real Estate and Facilities`. **Galway is not visible at this level either** — likely under Asia Pacific or another structure.
|
||||
|
||||
**Caveat:** these are *content folders*, not necessarily an authoritative manufacturing-site directory. A real site directory likely lives in HR / IT / ERP master data, not OpenText. The folder list here is best treated as a **lower-bound** of distinct business entities with documentation in OpenText.
|
||||
|
||||
**Update (2026-04-30, post-download of `Global Real Estate Information.xls`, 580 KB, 2014 vintage = pre-Biomet-merger Zimmer-only data):** master "Global Real Estate" worksheet has 198 rows covering 45 country sheets. **Manufacturing-classified sites globally** (filtered on Primary Use):
|
||||
|
||||
| Country | City | Address | Sq Ft | Notes |
|
||||
|---------|------|---------|-------|-------|
|
||||
| Switzerland | Winterthur / Zurich | Sulzer Allee 8 | 251,339 | **Active major site** — plan currently classifies as "not yet integrated"; needs reclassification |
|
||||
| USA | Allendale, NJ | 80 Commerce Drive | 22,654 | **ZTMT Offices / Manufacturing** — TMT is here |
|
||||
| USA | Calabasas, CA | 27030 Malibu Hills Rd | 35,719 | not in plan |
|
||||
| USA | Carlsbad, CA | 1900 Aston Avenue | 44,757 | not in plan |
|
||||
| USA | Cedar Knolls, NJ | 48 Horsehill Road | 23,198 | **ZTMT Offices / Manufacturing** |
|
||||
| USA | Dover, OH | 200 West Ohio Ave | 138,000 | not in plan |
|
||||
| USA | Livingston, NJ | 100 Navlon Ave | 7,500 | not in plan |
|
||||
| USA | Mercedita, PR | Mercedita Plant | 112,800 | **Separate from Ponce** — PR has 2 sites |
|
||||
| USA | Parsippany, NJ | 10 Pomeroy Road | 112,000 | **ZTMT Offices / Manufacturing** — largest TMT site |
|
||||
| USA | Ponce, PR | Parque Ind. El Tuque | 12,054 | matches plan's Ponce |
|
||||
| USA | Statesville, NC | 2021 Old Mountain Rd | 80,001 | not in plan |
|
||||
| USA | Warsaw, IN | (9 addresses, 1,141,003 sq ft total) | — | see Warsaw breakdown below |
|
||||
|
||||
**Warsaw, IN — 9 manufacturing addresses (2014 legacy-Zimmer only; pre-Biomet-merger so does NOT include North Campus lettered buildings):**
|
||||
|
||||
- 1800 West Center St — **552,230 sq ft** (main HQ campus — the numbered buildings 2–20 are on this property)
|
||||
- 508 Detroit Street — 24,820 sq ft (matches "Detroit St" PDFs in OpenText)
|
||||
- 1610 W Armstrong Road — 30,764 sq ft
|
||||
- 1612 Armstrong Road — 20,134 sq ft
|
||||
- 1625 Armstrong Road — 16,378 sq ft
|
||||
- 1639 Armstrong Road — 5,875 sq ft
|
||||
- 320 Hepler Drive — 30,838 sq ft
|
||||
- 400 S. Zimmer Rd — 19,000 sq ft
|
||||
|
||||
Several of these are likely the "Cessna" and "Detroit St" buildings that appeared in the OpenText `Zimmer Biomet Buildings` folder but didn't fit either the numbered or lettered scheme — they are auxiliary Warsaw, IN production buildings outside the main 1800 W Center St campus.
|
||||
|
||||
**Notable absences from this 2014 doc:** Shannon, Galway, Berlin, Jacksonville, and the lettered (Biomet) buildings — all of these are post-2015-merger acquisitions or sites that came in via Biomet.
|
||||
|
||||
**Implication for UNS / plan:** the plan's "Other integrated sites" list (Shannon, Galway, TMT, Ponce) is correct as the SCADA-integrated subset — most other sites in this list are not (yet) on the SCADA system. **However**, two corrections to the plan are warranted:
|
||||
|
||||
1. **Winterthur, Switzerland is a major manufacturing site (251K sq ft active)**, not a "smaller footprint" not-yet-integrated site as `current-state.md` currently classifies it. Onboarding it via the standardized stack is a significantly larger effort than the plan currently implies.
|
||||
2. **TMT is in New Jersey (Allendale, Cedar Knolls, Parsippany)** — three sites totaling 157K sq ft. The plan's `tmt` site shortname is fine but the location is NJ, not Indiana, not Japan (Japan is a separate registration). Mercedita, PR is separate from Ponce, PR.
|
||||
|
||||
---
|
||||
|
||||
### Q2 — Site code system (High)
|
||||
|
||||
Does the company use a standard site-code or facility-code system (for example a 2- or 3-letter code used across IT, ERP, HR, or finance)? If yes, what are the codes for **Warsaw West**, **Warsaw North**, **Shannon**, **Galway**, **TMT**, **Ponce**, **South Bend**, **Berlin**, **Winterthur**, and **Jacksonville**?
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
### Q3 — TMT meaning (High) — ANSWERED
|
||||
|
||||
What does the abbreviation **TMT** stand for as a manufacturing site, and what is its full official name? Where is it located?
|
||||
|
||||
**Response:**
|
||||
**TMT = Zimmer Trabecular Metal Technology, Inc.** — wholly owned subsidiary of Zimmer Holdings, Inc. Also does business as "Zimmer" and "Implex" (a/k/a "Zimmer Trabecular Metal Technology, Inc dba Zimmer and Implex"). Zimmer Biomet Canada is the contracted manufacturer for TMT-listed devices. Registered as a foreign medical-device manufacturer in Japan with establishment number BG30401579(TMT). Source: `[OpenText: Enterprise > Zimmer TMT > ... > TMT ISO (SGS) Certificates / State of NJ... > SGS Reports > Past Reports]` — the SGS audit reports `2023-10-03-AUR-SGSGU-F002993 SIGNED MDSAP...` and `2021-09-27-AUR-SGSGU-F002993 SIGNED MDSAP...`. **Sub-finding:** site has its own dedicated top-level folder `Enterprise > Zimmer TMT` with subfolders for Document Control (57 items), Quality, Sourcing — created by Virendra Atri in 2013, suggesting India-based ownership. **Implication for UNS:** the site shortname `tmt` aligns with the corporate naming; long-form display would be "Zimmer Trabecular Metal Technology" or "Zimmer TMT".
|
||||
|
||||
---
|
||||
|
||||
### Q4 — SAP plant codes (Low)
|
||||
|
||||
What are the **SAP plant codes** (or equivalent ERP plant identifiers) for each of our manufacturing sites?
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
### Q5 — Camstar MES site codes (Low)
|
||||
|
||||
What are the **Camstar MES site codes** in use, and how do they map to the physical sites?
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
## Warsaw campus building maps
|
||||
|
||||
### Q6 — Warsaw West buildings (High) — ANSWERED
|
||||
|
||||
What is the authoritative list of buildings on the **Warsaw West** campus, including building number, building name, primary purpose (production / office / warehouse / lab / utility), and approximate footprint? Specifically, are buildings other than 5 and 19 used for production?
|
||||
|
||||
**Response (partial):**
|
||||
The Warsaw campus has **far more buildings than just 5 and 19.** Authoritative folder `[OpenText: Enterprise > Business Teams > Real Estate and Facilities > Warsaw Real Estate and Facilities > Facility Information > Zimmer Biomet Buildings]` (objId=4638251) contains 31 floor-plan PDFs, one per building/floor. Building inventory:
|
||||
|
||||
- **Numbered buildings**: 2 (1F), 3 (LL/1/2/3), 4 (1/2), 5 (1/2), 7, 8 (1/2), 10, 14 (1&2), 15 (Z Hotel — 4 floors), 17, 18, 19, 20.
|
||||
- **Lettered buildings**: A (3 floors), B (2 floors), C, D, E, I (2 floors). Likely a separate sub-campus — they appeared together earlier under `Asset_Management_Warsaw > BLDG A_009 > BLDG A CASE 6 SHELF 3_01` with a `Mikron_Main Campus Map.pdf` reference, suggesting these may be the **Mikron** facility / older building-letter naming convention.
|
||||
- **Named buildings**: Cessna (1F & 2F), Detroit St-1 floor, Detroit St-2 floor (Detroit Street is in Warsaw, IN, so "Detroit St" buildings are Warsaw addresses, not Detroit).
|
||||
|
||||
**West Campus / North Campus split is real** (parent folder `[OpenText: Real Estate and Facilities]` has both `North Campus Training` and `West Campus Training` subfolders), but the building-to-campus assignment is **not visible from folder names alone** — it lives in the PDFs `Zimmer West Campus.pdf` (161 KB), `Warsaw Facilities Location Map.pdf` (117 KB), and the Excel `Zimmer Warsaw - Building Use Descriptions.xlsx` (12 KB) under `Facility Information`. Opening any of these requires an explicit download permission.
|
||||
|
||||
**Authoritative facilities contact (2019):** Vrushali Pandya, Sr. Facilities Specialist, Facilities Department, 1800 W. Center Street, Warsaw IN 46581 — `Vrushali.Pandya@zimmerbiomet.com`. Sourced from email `[OpenText: 01-Zimmer Warsaw-Establishment No.-18225... > Establishment Registration > Map 3 mile radius > RE List and Map of West Campus Buildings.msg]` (objId=56700739).
|
||||
|
||||
**Implication for UNS:** the original draft assumption of "Warsaw West = bldg-5 + bldg-19" is too narrow. Need either the West Campus PDF or the Building Use Descriptions Excel to finalize. Some "buildings" are office/hotel (Bldg 15 = "Z Hotel"), not production — purpose breakdown is critical before committing to UNS Areas.
|
||||
|
||||
**Resolution (2026-04-30):** project owner confirmed verbally that **numbered buildings = legacy Zimmer = Warsaw West Campus**, and **lettered buildings (A, B, C, …) = legacy Biomet = Warsaw North Campus**. This corresponds to the 2015 Zimmer-Biomet merger of two physically adjacent Warsaw, IN sites. The Building Use Descriptions doc (downloaded 2026-04-30) enumerates the numbered buildings 2–20 with use descriptions:
|
||||
|
||||
| Bldg | Use |
|
||||
|------|-----|
|
||||
| 2 | Printing Services, Bone Cement, **Packaging Clean Rooms** |
|
||||
| 5 | **Main manufacturing facility** (Foundry, Mfg, Packaging, R&D, Quality, Engineering Services, …) |
|
||||
| 7 | Tool Support Center, **Upper Extremity Manufacturing** |
|
||||
| 10 | **Hip and Knee Manufacturing**, Packaging Clean Rooms |
|
||||
| 19 | Trauma Corporate HQ + **Trauma, Instrument, and Knee & Hip Manufacturing, Foundry** |
|
||||
| 20 | Scrap Salvage, **Sheet Metal**, Warehousing |
|
||||
|
||||
Non-production: 3 (Executive offices), 4 (Distribution Center), 8 (Global Events), 14 (Airport Hangar), 15 (Z Hotel), 17 (IRS Offices), 18 (Residential Housing).
|
||||
|
||||
**Resolution applied to `warsaw-west.json`:** Warsaw West Areas = `bldg-2`, `bldg-5`, `bldg-7`, `bldg-10`, `bldg-19`, `bldg-20` (production buildings only; non-production 3, 4, 8, 14, 15, 17, 18 excluded per the goal-state design that Areas at Warsaw campuses are production buildings).
|
||||
|
||||
**Outstanding sub-questions (low priority, not blocking):**
|
||||
- **Cessna** and **Detroit St-1 / Detroit St-2** PDFs were in the same `Zimmer Biomet Buildings` folder but are neither numbered nor lettered. They belong to neither West nor North under this rule. Likely separate auxiliary buildings or a third Warsaw facility — verify during the walk.
|
||||
- **Lettered building purposes** are not yet known (no equivalent of the Building Use Descriptions doc was found for North Campus). All six lettered buildings are included in `warsaw-north.json` pending the walk; non-production ones should be removed once identified.
|
||||
- Lettering jumps from E to I — verify whether F, G, H exist, were demolished, or follow a different naming.
|
||||
|
||||
---
|
||||
|
||||
### Q7 — Warsaw North buildings (High — primary blocker) — ANSWERED
|
||||
|
||||
What is the authoritative list of buildings on the **Warsaw North** campus, including building number, building name, primary purpose (production / office / warehouse / lab / utility), and approximate footprint?
|
||||
|
||||
**Response:**
|
||||
**Lettered buildings (A, B, C, D, E, I) = Warsaw North Campus = legacy Biomet site.** Confirmed verbally by project owner; corresponds to the 2015 Zimmer-Biomet merger of two physically adjacent Warsaw, IN sites. Six lettered buildings visible in `[OpenText: Warsaw Real Estate and Facilities > Facility Information > Zimmer Biomet Buildings]`: A (3 floors), B (2 floors), C (1 floor), D (1 floor), E (1 floor), I (2 floors). Lettering jumps from E to I — F, G, H not visible; verify during walk.
|
||||
|
||||
**Resolution applied to `warsaw-north.json`:** Warsaw North Areas = `bldg-a`, `bldg-b`, `bldg-c`, `bldg-d`, `bldg-e`, `bldg-i` — all included pending verification of which are production vs. non-production (no equivalent of the Building Use Descriptions doc was found for North Campus). Walk should remove non-production buildings.
|
||||
|
||||
---
|
||||
|
||||
### Q8 — Multi-floor production buildings (Low)
|
||||
|
||||
Are any **Warsaw campus production buildings** split across multiple floors with distinct production processes per floor? If so, which buildings and what's on each floor?
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
## Production lines & cells (per site)
|
||||
|
||||
### Q9 — Production line inventory (High)
|
||||
|
||||
What are the named or numbered **production lines** currently operating at each integrated site (Warsaw West buildings 5 and 19, Warsaw North, Shannon, Galway, TMT, Ponce)? Looking for: line identifier, what the line produces, and where it physically sits within the site/building.
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
### Q10 — Existing plant taxonomy (Low)
|
||||
|
||||
Is there an existing **plant taxonomy** or **work-center hierarchy** documented anywhere — for example an ISA-95 model, a Camstar work-center tree, an Ignition project structure, or an Aveva System Platform Galaxy hierarchy — that already defines Site / Area / Line / Cell / Equipment for our sites?
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
### Q11 — Line naming convention in use today (Medium)
|
||||
|
||||
When a single physical production line is described across our internal documentation (engineering drawings, MES, capacity plans), is it named by a **number** (Line 1, Line 2), by a **product or process** (Assembly A, Packout, Injection 2), or by an **internal code** (e.g., MX-204)? Looking for the convention(s) actually in use today.
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
## Equipment naming & asset tags
|
||||
|
||||
### Q12 — Asset-tag format (Medium)
|
||||
|
||||
What is the company's **physical asset-tag format** for production equipment (e.g., the printed/engraved tags on machines)? Looking for: the format pattern, what each segment means, and whether the format differs across sites or equipment classes.
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
### Q13 — Asset register / CMDB (Medium)
|
||||
|
||||
Is there a **central asset register or CMDB** that lists production equipment by site, including asset tag, manufacturer, model, and location (building / line)? What is it called and who owns it?
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
### Q14 — Existing System Platform / Ignition naming (Medium)
|
||||
|
||||
What naming convention is used for production equipment in **Aveva System Platform** (Galaxy object names) and **Ignition** (OPC UA tag paths) today? Are the conventions consistent across sites?
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
### Q15 — FANUC CNC count and locations (Medium)
|
||||
|
||||
How many **FANUC CNC** machines do we have, broken down by site and building? (The FANUC CNC class is the pilot for the new equipment-class template work, so a count by location would shape rollout sequencing.)
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
## Existing standards
|
||||
|
||||
### Q16 — Existing UNS / ISA-95 standard (Low)
|
||||
|
||||
Does the company have an existing **Unified Namespace (UNS)**, **ISA-95 hierarchy**, or **manufacturing data model standard** documented? If so, where is it published and who owns it?
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
### Q17 — Enterprise shortname `zb` confirmation (Low) — ANSWERED
|
||||
|
||||
Is there an existing **enterprise-level shortname or stock-ticker-like abbreviation** used in IT systems, document headers, or domain names that we should align our top-of-hierarchy `zb` segment with? (We're using `zb` today; want to confirm it matches an existing convention rather than introducing a new one.)
|
||||
|
||||
**Response:**
|
||||
Confirmed: `zb` aligns with **Zimmer Biomet** as the company name (the OpenText instance is at `livelink.nam.zimmer.com`; documents are signed off by `@zimmerbiomet.com` email addresses; the corporate signature uses "ZIMMER BIOMET" as the brand). NYSE ticker is `ZBH` but `zb` is a clean two-letter shortname that matches both the legacy "Zimmer" and the post-merger "Zimmer Biomet" brand. **No change needed** — keep `zb` as the top-of-hierarchy enterprise segment.
|
||||
|
||||
---
|
||||
|
||||
### Q18 — Non-production equipment classes (Low)
|
||||
|
||||
Is there a **non-production equipment class list** (compressors, chillers, HVAC, lab equipment) maintained at the corporate level, and which of these surfaces are typically connected to SCADA / monitoring at our manufacturing sites?
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
## Cross-site / shared resources
|
||||
|
||||
### Q19 — Shared resources across sites (Low)
|
||||
|
||||
Are there any **shared production or test resources** (calibration labs, central inspection equipment, mobile test rigs) that are physically located at one site but logically serve multiple sites? If so, list them with their host site.
|
||||
|
||||
**Response:**
|
||||
_(pending)_
|
||||
|
||||
---
|
||||
|
||||
## Resolved
|
||||
|
||||
### 2026-04-30 — first pass against OpenText
|
||||
|
||||
- **Q3 (TMT meaning)** — fully answered. `tmt` site shortname stays; long-form name "Zimmer Trabecular Metal Technology" or "Zimmer TMT".
|
||||
- **Q17 (`zb` enterprise shortname)** — confirmed. `zb` aligns with Zimmer Biomet brand; no change.
|
||||
- **Q1 (site list)** — substantially answered. 2014 Zimmer global real-estate inventory shows 12 distinct manufacturing sites (legacy Zimmer only); plus Biomet-acquired sites (Shannon, Galway, etc.) added in 2015. Reclassifications applied to `current-state.md`: Winterthur is a major site (251K sq ft), not a "smaller footprint" site; TMT is in NJ (3 addresses); Mercedita is separate from Ponce.
|
||||
- **Q6 (Warsaw West buildings)** — fully answered. Numbered buildings = legacy Zimmer = Warsaw West. `warsaw-west.json` updated with 6 production Areas: bldg-2, bldg-5, bldg-7, bldg-10, bldg-19, bldg-20.
|
||||
- **Q7 (Warsaw North buildings)** — fully answered. Lettered buildings = legacy Biomet = Warsaw North. `warsaw-north.json` created with 6 Areas: bldg-a through bldg-e and bldg-i (purposes pending walk; non-production to be removed).
|
||||
|
||||
### Open OpenText follow-ups
|
||||
|
||||
- Source a **current-vintage** manufacturing-site directory (the Real Estate workbook is 2014 and pre-Biomet-merger) — likely lives in SAP / HR, not OpenText.
|
||||
- Optionally search OpenText for "Galway" and "Shannon" specifically since those Biomet-acquired sites are not in the 2014 real-estate workbook.
|
||||
- The `Global Site Pictures` (21 items) folder is unexplored — could yield labeled campus photos useful for verifying the West/North split visually.
|
||||
|
||||
12
schemas/uns/shannon.json
Normal file
12
schemas/uns/shannon.json
Normal file
@@ -0,0 +1,12 @@
|
||||
{
|
||||
"$schema": "../format/uns-subtree.schema.json",
|
||||
"enterprise": "zb",
|
||||
"site": "shannon",
|
||||
"displayName": "Shannon",
|
||||
"areas": [
|
||||
{
|
||||
"name": "_default",
|
||||
"displayName": "Site (single-cluster — no area distinction)"
|
||||
}
|
||||
]
|
||||
}
|
||||
12
schemas/uns/tmt.json
Normal file
12
schemas/uns/tmt.json
Normal file
@@ -0,0 +1,12 @@
|
||||
{
|
||||
"$schema": "../format/uns-subtree.schema.json",
|
||||
"enterprise": "zb",
|
||||
"site": "tmt",
|
||||
"displayName": "TMT",
|
||||
"areas": [
|
||||
{
|
||||
"name": "_default",
|
||||
"displayName": "Site (single-cluster — no area distinction)"
|
||||
}
|
||||
]
|
||||
}
|
||||
32
schemas/uns/warsaw-north.json
Normal file
32
schemas/uns/warsaw-north.json
Normal file
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"$schema": "../format/uns-subtree.schema.json",
|
||||
"enterprise": "zb",
|
||||
"site": "warsaw-north",
|
||||
"displayName": "Warsaw North (legacy Biomet campus)",
|
||||
"areas": [
|
||||
{
|
||||
"name": "bldg-a",
|
||||
"displayName": "Building A (3 floors) — purpose TBD, confirm during walk"
|
||||
},
|
||||
{
|
||||
"name": "bldg-b",
|
||||
"displayName": "Building B (2 floors) — purpose TBD, confirm during walk"
|
||||
},
|
||||
{
|
||||
"name": "bldg-c",
|
||||
"displayName": "Building C — purpose TBD, confirm during walk"
|
||||
},
|
||||
{
|
||||
"name": "bldg-d",
|
||||
"displayName": "Building D — purpose TBD, confirm during walk"
|
||||
},
|
||||
{
|
||||
"name": "bldg-e",
|
||||
"displayName": "Building E — purpose TBD, confirm during walk"
|
||||
},
|
||||
{
|
||||
"name": "bldg-i",
|
||||
"displayName": "Building I (2 floors) — purpose TBD; verify whether buildings F/G/H exist or were skipped in the lettering"
|
||||
}
|
||||
]
|
||||
}
|
||||
32
schemas/uns/warsaw-west.json
Normal file
32
schemas/uns/warsaw-west.json
Normal file
@@ -0,0 +1,32 @@
|
||||
{
|
||||
"$schema": "../format/uns-subtree.schema.json",
|
||||
"enterprise": "zb",
|
||||
"site": "warsaw-west",
|
||||
"displayName": "Warsaw West (legacy Zimmer campus)",
|
||||
"areas": [
|
||||
{
|
||||
"name": "bldg-2",
|
||||
"displayName": "Building 2 — Bone Cement, Packaging Clean Rooms"
|
||||
},
|
||||
{
|
||||
"name": "bldg-5",
|
||||
"displayName": "Building 5 — Main manufacturing facility (Foundry, R&D, Quality)"
|
||||
},
|
||||
{
|
||||
"name": "bldg-7",
|
||||
"displayName": "Building 7 — Tool Support Center, Upper Extremity Manufacturing"
|
||||
},
|
||||
{
|
||||
"name": "bldg-10",
|
||||
"displayName": "Building 10 — Hip and Knee Manufacturing, Packaging Clean Rooms"
|
||||
},
|
||||
{
|
||||
"name": "bldg-19",
|
||||
"displayName": "Building 19 — Trauma HQ, Trauma/Instrument/Knee & Hip Mfg, Foundry"
|
||||
},
|
||||
{
|
||||
"name": "bldg-20",
|
||||
"displayName": "Building 20 — Sheet Metal, Scrap Salvage, Warehousing"
|
||||
}
|
||||
]
|
||||
}
|
||||
Reference in New Issue
Block a user