CELINE Core Ontology: Description back to ToC
The ontology defines the following concept groups:
**Core context and simulation** -- CommunityContext binds a PECO EnergyCommunity to its members, assets, datasets and simulations. Scenario captures assumptions and temporal scope; Simulation and SimulationRun model abstract definitions and concrete executions. DatasetReference is a lightweight pointer to external datasets; instances declare their own conformance via dct:conformsTo and provide access details via DCAT/DCT terms.
**KPI layer** -- KPIDefinition captures named, typed KPI metrics with scope, calculation method, temporal granularity and unit of measure. KPIEvaluation records the computed value for a specific scope entity and time interval. A KPICatalog provides 11 initial REC-relevant KPI entries.
**Controlled vocabularies** -- All closed enumerations are SKOS ConceptSchemes. Every scheme declares its entry points with skos:hasTopConcept and each concept states the inverse with skos:topConceptOf; the schemes are flat, so the two sets coincide.
**Flexibility and settlement** -- FlexibilityRequest is the demand signal; FlexibilityCommitment is a member's pledge to deliver flexibility on specific PODs; FlexibilityCredit is the metered credit earned. FlexibilityEnvelope declares POD-level capability bounds; FlexibilityConstraint encodes activation rules. SettlementRun aggregates credits, applies costs (CostItem), and produces per-member RedistributionResults.
**Grid topology** -- Substation (Primary/Secondary), PowerTransformer, DistributionFeeder model the distribution network. RegulatoryZone represents administrative coverage areas. GridOperator models the DSO. ConnectionPoint generalises the PECO Electric_POD for multi-country portability.
**Asset inventory** -- PVSystem, BatteryStorage, ElectricityMeter, EVCharger, HeatPump are presence-only typed classes. Technical specifications are deliberately omitted; they live in an external catalogue, linked via celine:hasLocalIdentifier. Assets and connection points may reference operational datasources via celine:hasDataset.
**Member classification** -- MemberRole and MemberStatus SKOS vocabularies classify members within their energy community, following the upstream registry single-community-per-member model.
**Forecasts** -- celine:Forecast is a sosa:Observation subclass, not a separate hierarchy: SOSA defines an Observation as the act of a Procedure to estimate or calculate a value, which a computed forecast is, and defines a Procedure as a reusable algorithm or computational method, which is what a forecasting model is. celine:ForecastModel is that Procedure, reached through sosa:usedProcedure, so the model behind a number is answerable after the fact. Prediction bounds (celine:hasLowerBound, celine:hasUpperBound) and the level they cover (celine:hasConfidence) sit on the forecast itself; celine:forecastTargetTime is a literal shortcut for sosa:phenomenonTime, in the same spirit as SOSA's own sosa:hasSimpleResult. Forecasts sharing a celine:ForecastRun are one series. The observable properties are shared with measurement rather than doubled, so forecast and actual compare like with like.
**Energy observation** -- Seven sosa:ObservableProperty individuals name what a REC energy dataset reports: grid import and export, self-consumed energy, collectively shared energy, virtual consumed energy, the self-consumption ratio, and specific PV yield. Each carries a qudt:hasQuantityKind except celine:SpecificPVYield, whose kWh/kWp is energy over power: Energy and DimensionlessRatio are both false and Time reads as a duration, so none is asserted and the unit carries the meaning. The observation structure itself is SOSA's -- one sosa:Observation per quantity per interval, with sosa:hasSimpleResult and qudt:hasUnit -- and only the properties are minted here. Where a quantity also has a KPICatalog concept the two are linked with rdfs:seeAlso and kept distinct: the KPI is a period total or rate, the observable property is a single measurement.
All cross-domain links to PECO, SAREF, SOSA, QUDT and IEC CIM are expressed via skos:closeMatch annotations or lightweight object properties -- no external ontology is subclassed or redefined beyond PECO predicates already imported.