1 · The Brief — NorthWind wind-farm telemetry

Same skeleton, different domain. A wind operator has 600 turbines, 5 SCADA vendors, and a CMMS that doesn't know what 'gearbox' means.

0/1 done

Theory — the brief

The company

NorthWind Renewables (fictional) runs 600 turbines across 8 wind farms on three continents. Three SCADA vendors, two CMMS systems, one data lake nobody trusts.

The pain

Reliability engineer: "Vendor A calls the part gearbox. Vendor B calls it transmission. Vendor C uses a 7-digit code. My alarm rule has to enumerate all three."

Data lake owner: "Every new turbine model brings new tag names. My dashboards break every quarter."

Asset manager: "I want to ask 'how many gearboxes with vibration > X are installed in farms commissioned before 2020?'. Today that's a two-week consulting engagement."

What's different from MedaCore

Two big shifts shape every later decision:

  1. Telemetry volume. Tens of thousands of observations per minute. We cannot afford OWL 2 DL's exponential worst-case reasoning. OWL 2 EL — polynomial — is the right profile.
  2. Mature reusable standards exist. SOSA/SSN (W3C) for sensors and observations, QUDT for units. Minting our own :Sensor class would be unprofessional. The job is reuse-first.

Module map

Click a node to focus its neighbourhood · drag to pan · scroll to zoom

The modular ontology layout

Three small files, each owl:imports the next. The whole thing sits on top of SOSA/SSN and QUDT — we contribute the domain vocabulary, not yet another sensor framework.

Reading in progress · 0 of 1 activity done