Core standard
Information model, observations, events, identity, time, health, topology, security, and conformance.
Markdown sourceArchitecture Review Candidate · July 2026
Build a compatible energy telemetry implementation
This self-contained publication defines canonical observations, metrics, registry objects, topology, operational health, security, and conformance. It includes the contracts and tools needed to generate an implementation for a new solar plant.
LLM: complete context LLM: solar implementation prompt LLM: resource mapPoint an LLM here
For a model that can read one URL, provide the absolute URL of llms-full.txt together with the solar-plant prompt. For a browsing model, provide this index URL and instruct it to follow the normative documents, schema, and example links.
Read https://ocets.5ya.de/llms-full.txt and
https://ocets.5ya.de/solar-plant-implementation-prompt.txt.
Generate an OCETS 1.1-compatible implementation for my plant.
Do not invent canonical names or change metric semantics.Validation boundary: the included validator proves Registry structure and semantic references. It does not by itself prove that live telemetry has correct units, timestamps, quality, or runtime behavior.
Normative documents
Metric catalogue
Canonical names, units, types, labels, aggregation, state values, and lifecycle metadata.
Markdown sourcePlant Registry specification
Organizations, plants, assets, devices, measurement points, capabilities, topology, and validation.
Markdown sourceArchitecture decisions
Rationale and rejected alternatives behind the normative architecture.
Markdown sourceImplementation resources
Reference implementation guide
Practical collection, MQTT, Telegraf, transformation, deployment, edge health, and alerting guidance.
Markdown sourceNormative JSON Schema
Draft 2020-12 contract for Registry structure and controlled vocabularies.
Example Registry
Validated edge-collector example showing identity, capabilities, measurement points, and topology.
Registry validator
Schema plus cross-reference, tenant, topology, catalogue, profile, and secret checks.
Validator testsTelegraf reference
Main agent/output configuration with canonical collector identity.
Edge inputsMosquitto reference
Authenticated, persistent QoS 1 edge-broker starting point.
New solar plant workflow
| Step | Required result | Primary reference |
|---|---|---|
| 1. Inventory | Plant, assets, devices, measurement points, protocols, units, sample rates, and ownership are known. | Registry |
| 2. Model | A Registry uses stable logical IDs and declares only catalogue capabilities or namespaced extensions. | Schema |
| 3. Validate | The validator returns exit code 0 before collector configuration is generated. | Validator |
| 4. Map | Every vendor field maps to a canonical metric, unit, measurement point, timestamp, quality, and origin. | Metrics |
| 5. Deploy | Collection, buffering, transport, secrets, and time synchronization are configured and tested. | Guide |
| 6. Prove | Captured output and failure tests demonstrate freshness, missing-data, clock, buffer, and recovery behavior. | Conformance |
Published formats
Executive summary · Executive summary PDF · Core standard PDF · Bundle manifest