diff --git a/documentation/abstract.md b/documentation/abstract.md new file mode 100644 index 0000000000000000000000000000000000000000..7ec77d7af1503e7ae0369d8ae501db6ce6adb8a5 --- /dev/null +++ b/documentation/abstract.md @@ -0,0 +1 @@ +The present document is a technical specification of SAREF4ENER, an extension of SAREF [[2]](#[2]) that was created in collaboration with Energy@Home ([http://www.energy-home.it](http://www.energy-home.it)) and EEBus ([http://www.eebus.org/en](http://www.eebus.org/en)), the major Italy- and Germany-based industry associations, to enable the interconnection of their (different) data models. \ No newline at end of file diff --git a/documentation/acknowledgements.md b/documentation/acknowledgements.md new file mode 100644 index 0000000000000000000000000000000000000000..6bb347228f21483d05eca990c5afa724350aac86 --- /dev/null +++ b/documentation/acknowledgements.md @@ -0,0 +1,5 @@ +The editors would like to thank the ETSI SmartM2M technical committee for providing guidance and expertise. + +Also, many thanks to the ETSI staff and all other current and former active Participants of the ETSI SmartM2M group for their support, technical input and suggestions that led to improvements to this ontology. + +Also, special thanks goes to the ETSI SmartM2M Technical Officer Guillemin Patrick for his help. diff --git a/documentation/creators.md b/documentation/creators.md new file mode 100644 index 0000000000000000000000000000000000000000..acd577cf00e7aab8906d143897a10befdeb745f9 --- /dev/null +++ b/documentation/creators.md @@ -0,0 +1 @@ +- [Laura Daniele](https://www.linkedin.com/in/lauradaniele) ([TNO](https://tno.nl/)) diff --git a/documentation/description.html b/documentation/description.html index e69de29bb2d1d6434b8b29ae775ad8c2e48c5391..01b0f3cefee27593026e8a639fa3ebed9659be50 100644 --- a/documentation/description.html +++ b/documentation/description.html @@ -0,0 +1,82 @@ +

General Overview

+ + +

An overview of the SAREF4ENER ontology is provided in Figure 1, where rectangles containing an orange circle are used to denote classes created in SAREF4ENER, while rectangles containing a faded orange circle denote classes reused from other ontologies, such as SAREF. For all the entities described in the present document, it is indicated whether they are defined in the SAREF4ENER extension or elsewhere by the prefix included before their identifier, i.e. if the element is defined in SAREF4ENER the prefix is s4ener:, while if the element is reused from another ontology it is indicated in the Namespace Declarations section.

+

Arrows with white triangles on top represent the rdfs:subClassOf relation between two classes. The origin of the arrow is the class to be declared as subclass of the class at the destination of the arrow.

+

Directed arrows are used to represent properties between classes.

+

Rectangles that contain a list of values between square brackets denote an enumeration of individuals.

+

Note that Figure 1 aims at showing a global overview of the main classes of SAREF4ENER and their mutual relations. More details on the different parts of Figure 1 are provided below.

+ + +
+ SAREF Overview +
Figure 1: SAREF4ENER overview
+
+ + +

Figure 2 shows the hierarchy of classes and properties defined in SAREF4ENER.

+

Orange circles represent classes of SAREF4ENER, while faded orange circles represent classes that are reused from other ontologies. Object properties - which are properties between two classes - are denoted by blue rectangles, while datatype properties - which are properties between a class and a data type, such as xsd:string or xsd:dateTime - are denoted by green rectangles. Faded blue and green rectangles denote object properties and datatype properties that are reused from other ontologies.

+ + + +
+ SAREF4ENER class and property hierarchy +
Figure 2: SAREF4ENER class and property hierarchy
+
+ + +

Device

+ +

A s4ener:Device is a subclass of a saref:Device, i.e. it inherits the properties of the more general saref:Device and extends it with additional properties that are specific for SAREF4ENER. The s4ener:Device class is shown in Figure 3.

+ +
+ Device class +
Figure 3: Device class
+
+ +

Power Profile and Alternatives Group

+ +

This clause presents the classes of interest for smart energy management. These classes are used to schedule devices in certain modes and preferred times using power profiles to optimize energy efficiency and accommodate the customer's preferences (i.e. use case 2). These classes are s4ener:PowerProfile, s4ener:Alternative, s4ener:PowerSequence and s4ener:Slot, which are shown in Figure 4.

+

A s4ener:PowerProfile is a subclass of a saref:Profile, i.e. it inherits the properties of the more general saref:Profile extending it with additional properties that are specific for SAREF4ENER. The s4ener:PowerProfile is used by a s4ener:Device to expose the power sequences that are potentially relevant for the CEM. A s4ener:Device can expose a s4ener:PowerProfile, which consists of one or more alternative plans (s4ener:AlternativesGroup class). A s4ener:AlternativesGroup consists of one or more power sequences (s4ener:PowerSequence class), and a s4ener:PowerSequence consists of one or more slots (s4ener:Slot class). Inversely, a s4ener:Slot belongs to only and exactly one s4ener:PowerSequence, which, in turn, belongs to only and exactly one s4ener:AlternativesGroup, which, in turn, belongs to only and exactly one s4ener:PowerProfile. A s4ener:PowerProfile belongs to only and exactly one s4ener:Device.

+ + +
+ Power Profile and Alternatives Group +
Figure 4: Power Profile and Alternatives Group
+
+ +

Power Sequence

+ +

The s4ener:AlternativesGroup consists of one or more power sequences (s4ener:PowerSequence class) and, inversely, a s4ener:PowerSequence belongs to only and exactly one s4ener:AlternativesGroup. Figure 5 shows the details of the s4ener:PowerSequence class.

+ + +
+ Power Sequence +
Figure 5: Power Sequence
+
+ + +

Slot

+ +

The s4ener:PowerSequence consists of one or more slots (s4ener:Slot class) and, inversely, a s4ener:Slot belongs to only and exactly one s4ener:PowerSequence. Figure 6 shows the details of the s4ener:Slot class.

+ +
+ Slot +
Figure 6: Slot
+
+ + + +

Load control

+ +

This clause presents the part of SAREF4ENER that defines how to model events used in, for example, a direct load management and power curtailing scenarios (i.e. use case 4). The classes of interest are s4ener:LoadControlEventData, s4ener:LoadControlEventAction, s4ener:LoadControlStateData and s4ener:LoadControlState, as shown in Figure 7.

+

The s4ener: LoadControlEventData class is used to represent overload warning severity level and related load control commands to a device. It is characterized by an event ID and a timestamp that represents the time the event information instance was created or received, and the time period that denotes the period of validity of the event. For example, 5 minutes ago an event was received which says that it shall take effect tomorrow from 14:00 to 15:30. In this event the timestamp is "5 minutes ago" and time period is "tomorrow from 14:00 to 15:30".

+

The s4ener:LoadControlEventAction class expresses the type of actions to be performed as a consequence of a load control event. A s4ener:LoadControlEventAction can be of type "consume" or "produce" to denote consumption or production of energy or power. Values for both consume and produce actions can be s4ener:emergency, s4ener:increase, s4ener:normal, s4ener:pause, s4ener:reduce, s4ener:resume.

+

The s4ener: LoadControlStateData class expresses the data about the state of an event and is characterized by the same event ID used in the s4ener:LoadControlEventData class, as well as a timestamp, and it is associated to the class s4ener:LoadControlState, which can be of type "consume" or "produce" - analogously to a load control event action – and expresses the possible states of a load control event. Values for both consume and produce load control states can be s4ener:eventAccepted, s4ener:eventStarted, s4ener:eventStopped, s4ener:eventRejected, s4ener:eventCancelled, or s4ener:eventError.

+ + +
+ Load control +
Figure 7: Load control
+
+ diff --git a/documentation/diagrams/Device.png b/documentation/diagrams/Device.png new file mode 100644 index 0000000000000000000000000000000000000000..922d229dc38b0afba8217d49dbc279560d048538 Binary files /dev/null and b/documentation/diagrams/Device.png differ diff --git a/documentation/diagrams/Hierarchy.png b/documentation/diagrams/Hierarchy.png new file mode 100644 index 0000000000000000000000000000000000000000..83cf62f62aad70e7dc4b4acb717fe82a2d99ccdd Binary files /dev/null and b/documentation/diagrams/Hierarchy.png differ diff --git a/documentation/diagrams/LoadControl.png b/documentation/diagrams/LoadControl.png new file mode 100644 index 0000000000000000000000000000000000000000..cd31d347ebb8edde30e117379646d2b90df061ad Binary files /dev/null and b/documentation/diagrams/LoadControl.png differ diff --git a/documentation/diagrams/Overview.png b/documentation/diagrams/Overview.png new file mode 100644 index 0000000000000000000000000000000000000000..8aa5a535c035203a1170b566167647cdf668748f Binary files /dev/null and b/documentation/diagrams/Overview.png differ diff --git a/documentation/diagrams/PowerProfile.png b/documentation/diagrams/PowerProfile.png new file mode 100644 index 0000000000000000000000000000000000000000..23439e01c0aad30151cd9b09a420a3500c32de00 Binary files /dev/null and b/documentation/diagrams/PowerProfile.png differ diff --git a/documentation/diagrams/PowerSequence.png b/documentation/diagrams/PowerSequence.png new file mode 100644 index 0000000000000000000000000000000000000000..9ea037cfcafefd6005a38546106182c427d9311f Binary files /dev/null and b/documentation/diagrams/PowerSequence.png differ diff --git a/documentation/diagrams/Slot.png b/documentation/diagrams/Slot.png new file mode 100644 index 0000000000000000000000000000000000000000..e584f63431c1c5e4046ed34e3536020bad0abd7f Binary files /dev/null and b/documentation/diagrams/Slot.png differ diff --git a/documentation/references.html b/documentation/references.html new file mode 100644 index 0000000000000000000000000000000000000000..8dae51972fdd07e221d6bdeee68f13953ad76480 --- /dev/null +++ b/documentation/references.html @@ -0,0 +1,19 @@ +

Normative references

+ + + +

Informative references

+ + diff --git a/ontology/saref4ener.ttl b/ontology/saref4ener.ttl index 49c12a56e5717796375088ff924a64a2d15b4aff..e48205eaff662aa570c4feb9c60a9416f107fb60 100644 --- a/ontology/saref4ener.ttl +++ b/ontology/saref4ener.ttl @@ -18,6 +18,7 @@ vann:preferredNamespaceUri "https://saref.etsi.org/saref4ener/" ; owl:versionInfo "v1.1.2" ; dcterms:created "2015-09-04"^^xsd:date ; + dcterms:issued "2020-06-04"^^xsd:date ; dcterms:creator ; dcterms:description "SAREF4ENER is an extension of SAREF for the Energy domain that was created in collaboration with Energy@Home (http://www.energy-home.it) and EEBus (http://www.eebus.org/en), the major Italy- and Germany-based industry associations, to enable the interconnection of their (different) data models. SAREF4ENER focuses on demand response scenarios, in which customers can offer flexibility to the Smart Grid to manage their smart home devices by means of a Customer Energy Manager (CEM). The CEM is a logical function for optimizing energy consumption and/or production that can reside either in the home gateway or in the cloud. SAREF4ENER is published as an ETSI tecnical specificatoion (ETSI TS 103 410-1)."@en ; dcterms:modified "2016-12-13"^^xsd:date ; @@ -25,6 +26,8 @@ owl:imports ; dcterms:license ; dcterms:publisher ; + dcterms:source ; + rdfs:seeAlso . dcterms:created a owl:AnnotationProperty .