Repository navigation
Business model
github-actions[bot] edited this page Oct 20, 2026
·
1 revision
CH must learn to sell outcomes, not just equipment. The data in this environment is what makes those offers possible. Real hydro OEMs already do this, which gives the case study credible anchors.
| OEM | Offering | Signal for CH |
|---|---|---|
| Andritz Hydro | Metris DiOMera monitoring; long-term O&M with KPI guarantees (Cerro del Águila, Peru) | Outcome-based contracts are possible in hydro |
| Voith Hydro | OnCare.Health, OnCare.Acoustic, expert health assessments | Product + platform + expert subscription |
| GE Vernova | Hydro APM with edge analytics on the most critical plants (EDP: 23 plants, ~5.5 GW) | Tiered coverage by asset criticality |
-
CH Connect (bundled with new units): remote visibility, digital nameplate (
_meta/Nameplate), data export. -
CH Monitor (subscription per unit): alarms (
Events/Alarm), monthly health report, expert review. - CH Predict (subscription + expert retainer): vibration analytics on the waveforms, residual models, remaining useful life, spare-parts forecast.
- CH Assure (outcome-based): availability or rough-zone KPIs with bonus/malus, on-site smart spares, field-service SLAs.
- Data ownership: under the EU Data Act, users of connected products have data access rights (since 12 September 2025), and products placed on the market after 12 September 2026 must offer access by design. CH may only use non-personal product data under an agreement with the customer.
- Third-party data sales: only with customer consent; anonymised fleet benchmarks are more realistic than raw data.
- Servitization paradox: service investments often raise costs before returns arrive.
- Outcome risk: CH's KPIs depend on how the customer operates. In scenario C the dispatcher parks a unit in the rough zone: who pays for the bearing and runner life it costs?
- Culture: an engineering-first company must learn service delivery, and sales incentives tied to equipment sales must change.
- Copper Canyon Dam and all its figures are demo assumptions; real values are OEM- and site-specific.
- The vortex-rope magnitude used for calibration (a 600 MW prototype study) still needs a confirmed citation.
- OEM benefit figures are vendor marketing claims; the Data Act summary is not legal advice.
- Source on the Data Act: Travers Smith.
Start
Understand
- Copper Canyon Dam
- Architecture
- Customer data vs. machine-builder data
- Example Unified Namespace
- Failure modes
- RCA demo walkthrough
- RCA with Claude: a guide for engineers
Use
- Dam SCADA
- CH asset viewer
- Instructor station
- Node-RED and MQTT Explorer
- Namespace
- Interface reference
- Configuration
For vendors
Contribute