@prefix : . @prefix gn: . @prefix om: . @prefix geo: . @prefix owl: . @prefix rdf: . @prefix xml: . @prefix xsd: . @prefix foaf: . @prefix rdfs: . @prefix time: . @prefix geosp: . @prefix ic-fc: . @prefix ic-s2: . @prefix saref: . @prefix s4bldg: . @prefix s4ener: . @prefix ic-data: . @prefix ic-flex: . @prefix ic-tplg: . @base . rdf:type owl:Ontology ; , "Cornelis Bouter -TNO"@en , "Georg Jung - VITO" ; rdfs:comment """The flexibility ontology module (ic-flex) is by design tightly integrated with SAREF, SAREF4ENER and the following InterConnect modules: power limit (ic-pwlm), incentive table (ic-inc), S2 (ic-s2), data-point (ic-data) and forecast (ic-fc) The main concept of the ic-flex module is the ic-flex:FlexOffer, which allows to represent a flexibility offer (or schedule) as a combination of multiple time-series, data-points and forecasts. It also allows to specify a creation time (ic-data:hasCreationTime), validity period (ic-data:hasEffectivePeriod) and provenance (ic-data:producedBy) for the offer, on top of the creation time, validity period and provenance already specified for the time-series and data-points included in the offer. The additional key aspect captured in the ic-flex module is that a flex offer can also include various categories of flexibility, which are modelled as subclasses of the ic-flex:FlexibilityProfile class, as follows: - Power Profile flexibilty is modelled as s4ener:PowerProfile based on the EEBUS spec - Tariff based flexibility (ic-flex:TariffBased) is implemented using the incentive table (ic-inc) ontology based on the EEBUS spec (note that tariif-based felxibility does note exist in S2) - Power limit flexibility (ic-pwlm:PowerLimit) is implemented using thepower limit (ic-pwlm) ontology based on the EEBUS spec (and compliant also with S2) - Power Envelope flexibility (ic-flex:PowerEnvelope) is implemented using theS2 (ic-s2) that follows the S2 specification (and compliant also with EEBUS) - Demand driven flexibility (ic-flex:DemandDriven) flexibility (ic-flex:PowerEnvelope) is implemented using theS2 (ic-s2) that follows the S2 specification (and compliant also with EEBUS) - Operation mode flexibility (ic-flex:OperationMode) is implemented using theS2 (ic-s2) that follows the S2 specification (and compliant also with S2) - Fill rate based flexibility (ic-flex:FillRateBased is implemented using theS2 (ic-s2) that follows the S2 specification (and compliant also with S2)"""@en . ################################################################# # Annotation properties ################################################################# ### http://purl.org/dc/elements/1.1/creator rdf:type owl:AnnotationProperty . ### http://www.w3.org/2002/07/owl#maxQualifiedCardinality owl:maxQualifiedCardinality rdf:type owl:AnnotationProperty . ################################################################# # Object Properties ################################################################# ### http://ontology.tno.nl/interconnect/datapoint#hasCreationTime ic-data:hasCreationTime rdf:type owl:ObjectProperty . ### http://ontology.tno.nl/interconnect/datapoint#hasEffectivePeriod ic-data:hasEffectivePeriod rdf:type owl:ObjectProperty . ### http://ontology.tno.nl/interconnect/datapoint#producedBy ic-data:producedBy rdf:type owl:ObjectProperty . ### http://ontology.tno.nl/interconnect/flexibility#hasActivationPlan ic-flex:hasActivationPlan rdf:type owl:ObjectProperty ; rdfs:domain ic-s2:FlexibilityInstruction ; rdfs:range ic-data:TimeSeries ; rdfs:comment "The relationship between the ic-s2:FlexibilityInstruction and ic-data:TimeSeries."@en ; rdfs:label "has activation plan"@en . ### http://ontology.tno.nl/interconnect/flexibility#hasCost ic-flex:hasCost rdf:type owl:ObjectProperty ; rdfs:domain ic-s2:FlexibilityInstruction ; rdfs:range ic-data:DataPoint ; rdfs:comment "The relationship between the ic-s2:FlexibilityInstruction and ic-data:DataPoint"@en ; rdfs:label "has cost"@en . ### http://ontology.tno.nl/interconnect/flexibility#hasRecipient ic-flex:hasRecipient rdf:type owl:ObjectProperty ; rdfs:comment "This property can be used to connect a flexibility offer or/and flexibility request to a foaf:agent or saref:Device."@en ; rdfs:label "has recipient"@en . ### http://ontology.tno.nl/interconnect/flexibility#includes ic-flex:includes rdf:type owl:ObjectProperty ; rdfs:comment "This property can be used to connect the flexibility offer and/or flexibility request to the flexibility profile. Additionally, it can be used to specify the ic-data:datapoint, ic-data:timeseries and ic-fc:forecast included in the flexibility offer and/or flexibility request."@en ; rdfs:label "includes"@en . ### http://ontology.tno.nl/interconnect/flexibility#relatesToOffer ic-flex:relatesToOffer rdf:type owl:ObjectProperty ; rdfs:domain ic-s2:FlexibilityInstruction ; rdfs:range ic-flex:FlexOffer ; rdfs:comment "The relationship between the ic-s2:FlexibilityInstruction and the flexibility offer."@en ; rdfs:label "relates to offer"@en . ### http://ontology.tno.nl/interconnect/flexibility#relatesToRequest ic-flex:relatesToRequest rdf:type owl:ObjectProperty ; rdfs:domain ic-flex:FlexOffer ; rdfs:range ic-flex:FlexRequest ; rdfs:comment "The relationship between the flexibility offer and flexibility request"@en ; rdfs:label "relates to request"@en . ### http://ontology.tno.nl/interconnect/flexibility#specifies ic-flex:specifies rdf:type owl:ObjectProperty ; rdfs:domain ic-flex:FlexibilityProfile ; rdfs:range ic-s2:FlexibilityInstruction ; rdfs:comment "The relationship between the flexibility profile and the ic-s2:flexibility instruction."@en ; rdfs:label "specifies"@en . ### http://ontology.tno.nl/interconnect/flexibility#uses ic-flex:uses rdf:type owl:ObjectProperty ; rdfs:comment "This property can be used to respectively connect the incentive based profile and power limit profile to the ic-inc:incentiveTable and ic-pwlm:PowerLimit"@en ; rdfs:label "uses"@en . ################################################################# # Classes ################################################################# ### http://ontology.tno.nl/interconnect/datapoint#DataPoint ic-data:DataPoint rdf:type owl:Class . ### http://ontology.tno.nl/interconnect/datapoint#TimeSeries ic-data:TimeSeries rdf:type owl:Class . ### http://ontology.tno.nl/interconnect/flexibility#DemandDrivenProfile ic-flex:DemandDrivenProfile rdf:type owl:Class ; rdfs:subClassOf ic-flex:FlexibilityProfile ; rdfs:comment "It can be used for systems that are flexible in the type of energy carrier they use but are not capable of buffering or storing energy."@en ; rdfs:label "Demand Driven Profile" . ### http://ontology.tno.nl/interconnect/flexibility#FillRateBasedProfile ic-flex:FillRateBasedProfile rdf:type owl:Class ; rdfs:subClassOf ic-flex:FlexibilityProfile ; rdfs:comment "It can be used for devices that have the ability to store or buffer energy. How energy is stored or buffered does not matter, as long as there is a means to measure how full the storage or buffer is."@en ; rdfs:label "Fill rate based flexibility"@en . ### http://ontology.tno.nl/interconnect/flexibility#FlexOffer ic-flex:FlexOffer rdf:type owl:Class ; rdfs:subClassOf [ rdf:type owl:Restriction ; owl:onProperty ic-data:producedBy ; owl:allValuesFrom [ rdf:type owl:Class ; owl:unionOf ( foaf:Agent saref:Device ) ] ] , [ rdf:type owl:Restriction ; owl:onProperty ic-flex:hasRecipient ; owl:allValuesFrom [ rdf:type owl:Class ; owl:unionOf ( foaf:Agent saref:Device ) ] ] , [ rdf:type owl:Restriction ; owl:onProperty ic-flex:includes ; owl:allValuesFrom [ rdf:type owl:Class ; owl:unionOf ( ic-data:DataPoint ic-data:TimeSeries ic-flex:FlexibilityProfile ic-fc:Forecast ) ] ] , [ rdf:type owl:Restriction ; owl:onProperty ic-data:hasCreationTime ; owl:maxQualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass time:Instant ] , [ rdf:type owl:Restriction ; owl:onProperty ic-data:hasEffectivePeriod ; owl:maxQualifiedCardinality "1"^^xsd:nonNegativeInteger ; owl:onClass time:Interval ] ; rdfs:comment "It allows to represent a flexibility offer (or schedule) as a combination of multiple time-series, data-points and forecasts. For example, we can create a flexibility offer that includes a time-series ex:T-power of power values, combined with a time-series ex:T-costs of associated costs."@en ; rdfs:label "Flex offer"@en . ### http://ontology.tno.nl/interconnect/flexibility#FlexRequest ic-flex:FlexRequest rdf:type owl:Class ; rdfs:subClassOf owl:Thing , [ rdf:type owl:Restriction ; owl:onProperty ic-data:hasCreationTime ; owl:allValuesFrom time:Instant ] , [ rdf:type owl:Restriction ; owl:onProperty ic-data:hasEffectivePeriod ; owl:allValuesFrom time:Interval ] , [ rdf:type owl:Restriction ; owl:onProperty ic-data:producedBy ; owl:allValuesFrom [ rdf:type owl:Class ; owl:unionOf ( foaf:Agent saref:Device ) ] ] , [ rdf:type owl:Restriction ; owl:onProperty ic-flex:hasRecipient ; owl:allValuesFrom [ rdf:type owl:Class ; owl:unionOf ( foaf:Agent saref:Device ) ] ] , [ rdf:type owl:Restriction ; owl:onProperty ic-flex:includes ; owl:allValuesFrom [ rdf:type owl:Class ; owl:unionOf ( ic-data:DataPoint ic-data:TimeSeries ic-flex:FlexibilityProfile ic-fc:Forecast ) ] ] ; rdfs:comment "The flexibility request"@en ; rdfs:label "Flex request" . ### http://ontology.tno.nl/interconnect/flexibility#FlexibilityProfile ic-flex:FlexibilityProfile rdf:type owl:Class ; rdfs:subClassOf saref:Profile , [ rdf:type owl:Restriction ; owl:onProperty ic-flex:specifies ; owl:allValuesFrom ic-s2:FlexibilityInstruction ] ; rdfs:comment """Different control types to describe the energy flexibility that a device has to offer. Charging of an EV for instance, may be controlled by power profile-based control or fill-rate -based control. It is not allowed to mix different control types at the same time, but different control types may be used sequentially. Control Types dictates flexibility instructions. Control Type provides Flexibility options.""" ; rdfs:label "Flexibility Profile" . ### http://ontology.tno.nl/interconnect/flexibility#IncentiveBasedProfile ic-flex:IncentiveBasedProfile rdf:type owl:Class ; rdfs:subClassOf ic-flex:FlexibilityProfile , [ rdf:type owl:Restriction ; owl:onProperty ic-flex:uses ; owl:allValuesFrom ] ; rdfs:comment "The incentive based profile"@en ; rdfs:label "Incentive based profile"@en . ### http://ontology.tno.nl/interconnect/flexibility#OperationModeProfile ic-flex:OperationModeProfile rdf:type owl:Class ; rdfs:subClassOf ic-flex:FlexibilityProfile ; rdfs:comment "It is for devices that have the possibility to control the amount of power they produce or consume, without significant effects on their future flexibility options. These devices are modelled as a state machine, where each state (referred to as an operation mode) has an energy production or consumption associated with it."@en ; rdfs:label "Operation mode profile"@en . ### http://ontology.tno.nl/interconnect/flexibility#PowerEnvelope ic-flex:PowerEnvelope rdf:type owl:Class ; rdfs:subClassOf ic-flex:FlexibilityProfile ; rdfs:comment "It is used for devices that can be influenced to use a minimum and/or maximum amount of power over time. The flexibility manager cannot control the amount of power produced or consumed by the device directly, but it can dictate power limits, which can change over time."@en ; rdfs:label "Power Envelope Profile"@en . ### http://ontology.tno.nl/interconnect/flexibility#PowerLimitProfile ic-flex:PowerLimitProfile rdf:type owl:Class ; rdfs:subClassOf ic-flex:FlexibilityProfile , [ rdf:type owl:Restriction ; owl:onProperty ic-flex:uses ; owl:allValuesFrom ] ; rdfs:comment "The power limit flexibility."@en ; rdfs:label "Power Limit Profile"@en . ### http://ontology.tno.nl/interconnect/flexibility#PowerProfile ic-flex:PowerProfile rdf:type owl:Class ; rdfs:subClassOf ic-flex:FlexibilityProfile ; rdfs:comment "This type of flexibility is typical for devices that perform a task (with a clear start and end) with a corresponding power profile that is known or can be predicted. Their main flexibility comes from the ability to change the start time of that power profile."@en ; rdfs:label "Power profile" . ### http://ontology.tno.nl/interconnect/forecast#Forecast ic-fc:Forecast rdf:type owl:Class . ### http://ontology.tno.nl/interconnect/incentivetable#IncentiveTable rdf:type owl:Class . ### http://ontology.tno.nl/interconnect/powerlimit#PowerLimit rdf:type owl:Class . ### http://ontology.tno.nl/interconnect/s2#FlexibilityInstruction ic-s2:FlexibilityInstruction rdf:type owl:Class . ### http://www.w3.org/2006/time#Instant time:Instant rdf:type owl:Class . ### http://www.w3.org/2006/time#Interval time:Interval rdf:type owl:Class . ### http://xmlns.com/foaf/0.1/Agent foaf:Agent rdf:type owl:Class . ### https://saref.etsi.org/core/Device saref:Device rdf:type owl:Class . ### https://saref.etsi.org/core/Profile saref:Profile rdf:type owl:Class . ### https://saref.etsi.org/saref4ener/PowerProfile s4ener:PowerProfile rdf:type owl:Class ; rdfs:subClassOf ic-flex:PowerProfile . [ owl:maxQualifiedCardinality "1"^^xsd:nonNegativeInteger ] . ### Generated by the OWL API (version 4.5.9.2019-02-01T07:24:44Z) https://github.com/owlcs/owlapi