| ... | ... | @@ -18,7 +18,7 @@ Organization of the project work packages and consortium can be seen [here](http |
|
|
|
|
|
|
|
# Cascade Funding Opportunities
|
|
|
|
|
|
|
|
Here you can find the latest information about the project funding opportunities for European SMEs and Startups: <https://interconnect-opencalls.fundingbox.com/>
|
|
|
|
Here you can find the latest information about the project funding opportunities for European SMEs and Startups: https://interconnect-opencalls.fundingbox.com/
|
|
|
|
|
|
|
|
# Project outcomes and KERs
|
|
|
|
|
| ... | ... | @@ -48,16 +48,16 @@ Table 1 – _Prefixes and namespaces_ of the _external_ ontologies reused by Int |
|
|
|
|
|
|
|
| Prefix | Namespace | Main concepts |
|
|
|
|
|--------|-----------|---------------|
|
|
|
|
| foaf | <http://xmlns.com/foaf/0.1/> | Agent |
|
|
|
|
| geo | <http://www.w3.org/2003/01/geo/wgs84_pos#> | Spatial Thing, geo coordinates |
|
|
|
|
| geosp | <http://www.opengis.net/ont/geosparql#> | Geographical Feature |
|
|
|
|
| schema | <https://schema.org/> | Address, Countries, Postal Codes |
|
|
|
|
| om | <http://www.ontology-of-units-of-measure.org/resource/om-2/> | Quantity, Unit, Measure |
|
|
|
|
| saref | <https://saref.etsi.org/core/> | Device, Function, Command, State, Measurement, Unit of Measure, Feature of Interest |
|
|
|
|
| s4bldg | <https://saref.etsi.org/saref4bldg/> | Building, Building Space, Building Object |
|
|
|
|
| s4city | <https://saref.etsi.org/saref4ener/> | Power Profile, Alternatives, Power Sequence, Slot |
|
|
|
|
| s4ener | <https://saref.etsi.org/saref4city/> | Facility, Administrative Area, City Object |
|
|
|
|
| time | <http://www.w3.org/2006/time#> | Instant, Interval, Duration |
|
|
|
|
| foaf | http://xmlns.com/foaf/0.1/ | Agent |
|
|
|
|
| geo | http://www.w3.org/2003/01/geo/wgs84_pos# | Spatial Thing, geo coordinates |
|
|
|
|
| geosp | http://www.opengis.net/ont/geosparql# | Geographical Feature |
|
|
|
|
| schema | https://schema.org/ | Address, Countries, Postal Codes |
|
|
|
|
| om | http://www.ontology-of-units-of-measure.org/resource/om-2/ | Quantity, Unit, Measure |
|
|
|
|
| saref | https://saref.etsi.org/core/ | Device, Function, Command, State, Measurement, Unit of Measure, Feature of Interest |
|
|
|
|
| s4bldg | https://saref.etsi.org/saref4bldg/ | Building, Building Space, Building Object |
|
|
|
|
| s4city | https://saref.etsi.org/saref4ener/ | Power Profile, Alternatives, Power Sequence, Slot |
|
|
|
|
| s4ener | https://saref.etsi.org/saref4city/ | Facility, Administrative Area, City Object |
|
|
|
|
| time | http://www.w3.org/2006/time# | Instant, Interval, Duration |
|
|
|
|
|
|
|
|
**InterConnect Ontologies**
|
|
|
|
|
| ... | ... | @@ -67,27 +67,27 @@ Table 2 – _Prefixes and namespaces_ of the InterConnect ontologies |
|
|
|
|
|
|
|
| Prefix | Namespace | Main concepts |
|
|
|
|
|--------|-----------|---------------|
|
|
|
|
| ic-data | <http://ontology.tno.nl/interconnect/datapoint#> | Datapoint, TimeSeries, Message, Utility Purpose |
|
|
|
|
| ic-dev | <http://ontology.tno.nl/interconnect/device#> | Device, State, Function |
|
|
|
|
| ic-flex | <http://ontology.tno.nl/interconnect/flexibility#> | Flex Offer, Flexibility Source, Control Type, Power Envelope |
|
|
|
|
| ic-fc | <http://ontology.tno.nl/interconnect/forecast#> | Forecast, Point Forecast, Stochastic Forecast (Gaussian, Quantile, Trajectory), Gaussian Data Point |
|
|
|
|
| ic-inc | <http://ontology.tno.nl/interconnect/incentivetable#> | Incentive Table, Incentive Tiers, Scope and Type |
|
|
|
|
| ic-pwlm | <http://ontology.tno.nl/interconnect/powerlimit#> | Power Limit (Nominal, Contractual and Failsafe) |
|
|
|
|
| ic-tplg | <http://ontology.tno.nl/interconnect/topology#> | Topological Location, Grid Segment, Market Segment, Regulation Zone, Electrical Phases |
|
|
|
|
| ic-uom | <http://ontology.tno.nl/interconnect/units#> | Additional Units of Measure (not considered yet in SAREF) |
|
|
|
|
| ic-user | <http://ontology.tno.nl/interconnect/user#> | User, User Profile, Preference, Priority, Interest, Activity, Time, Location |
|
|
|
|
| ic-data | http://ontology.tno.nl/interconnect/datapoint# | Datapoint, TimeSeries, Message, Utility Purpose |
|
|
|
|
| ic-dev | http://ontology.tno.nl/interconnect/device# | Device, State, Function |
|
|
|
|
| ic-flex | http://ontology.tno.nl/interconnect/flexibility# | Flex Offer, Flexibility Source, Control Type, Power Envelope |
|
|
|
|
| ic-fc | http://ontology.tno.nl/interconnect/forecast# | Forecast, Point Forecast, Stochastic Forecast (Gaussian, Quantile, Trajectory), Gaussian Data Point |
|
|
|
|
| ic-inc | http://ontology.tno.nl/interconnect/incentivetable# | Incentive Table, Incentive Tiers, Scope and Type |
|
|
|
|
| ic-pwlm | http://ontology.tno.nl/interconnect/powerlimit# | Power Limit (Nominal, Contractual and Failsafe) |
|
|
|
|
| ic-tplg | http://ontology.tno.nl/interconnect/topology# | Topological Location, Grid Segment, Market Segment, Regulation Zone, Electrical Phases |
|
|
|
|
| ic-uom | http://ontology.tno.nl/interconnect/units# | Additional Units of Measure (not considered yet in SAREF) |
|
|
|
|
| ic-user | http://ontology.tno.nl/interconnect/user# | User, User Profile, Preference, Priority, Interest, Activity, Time, Location |
|
|
|
|
|
|
|
|
More information about the InterConnect ontologies can be found at the following _Individual pages_.
|
|
|
|
|
|
|
|
1. [Datapoint, Timeseries and Message (ic-data)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-data)
|
|
|
|
2. [Forecast (ic-fc)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-fc)
|
|
|
|
3. [Incentive Table (ic-inc)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-inc)
|
|
|
|
4. [Power Limit (ic-pwlm)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-pwlm)
|
|
|
|
5. [User (ic-user)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-user)
|
|
|
|
6. [Flexibility (ic-flex)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-flex)
|
|
|
|
7. [Units of Measure (ic-uom)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-uom)
|
|
|
|
8. [Topology (ic-tplg)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-tplg)
|
|
|
|
9. [Device and sensor (ic-dev)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-dev)
|
|
|
|
1. [Datapoint, Timeseries and Message (ic-data)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-data)
|
|
|
|
2. [Forecast (ic-fc)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-fc)
|
|
|
|
3. [Incentive Table (ic-inc)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-inc)
|
|
|
|
4. [Power Limit (ic-pwlm)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-pwlm)
|
|
|
|
5. [User (ic-user)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-user)
|
|
|
|
6. [Flexibility (ic-flex)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-flex)
|
|
|
|
7. [Units of Measure (ic-uom)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-uom)
|
|
|
|
8. [Topology (ic-tplg)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-tplg)
|
|
|
|
9. [Device and sensor (ic-dev)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-dev)
|
|
|
|
10. [S2 standard (ic-s2)](https://gitlab.inesctec.pt/interconnect-public/ontology/-/wikis/ic-s2)
|
|
|
|
|
|
|
|
[InterConnect Ontology repository](https://gitlab.inesctec.pt/interconnect-public/ontology)
|
| ... | ... | @@ -162,7 +162,6 @@ _Knowledge Engine as a distributed knowledge network:_ |
|
|
|
|
|
|
|
[Knowledge Engine OpenAPI specification of developer REST API](https://gitlab.inesctec.pt/interconnect-public/knowledge-engine/-/blob/main/openapi-sc.yaml)
|
|
|
|
|
|
|
|
|
|
|
|
### Generic Adapter
|
|
|
|
|
|
|
|
In the InterConnect project we define the following adapters:
|
| ... | ... | @@ -200,10 +199,10 @@ _High level architecture of the Generic Adapter:_ |
|
|
|
|
|
|
|
* **<span dir="">Hyperledger Fabric blockchain configurations</span>**<span dir=""> for different types of P2P marketplaces (different hierarchies, consortium organizations, stakeholders, nodes and channels).</span>
|
|
|
|
* **<span dir="">Smart contract templates</span>**<span dir=""> for different types of orders and transactions to be featured in the marketplace. Smart contracts will include APIs for end user GUIs (web application) and APIs for services for automated P2P trading.</span>
|
|
|
|
* <span dir="">Smart contract templates for generating reports and audits about status of the marketplace and executed transactions - in line with regulatory and business requirements.</span>
|
|
|
|
* <span dir="">Smart contract implemented as semantic interoperability adapter for interfacing with the wider InterConnect Interoperability Framework.</span>
|
|
|
|
* <span dir="">Smart contracts for registering and identifying key actors and resources constituting P2P marketplaces.</span>
|
|
|
|
* <span dir="">Smart Contracts for integration of interoperable services which write data to or read data from the Hyperledger Fabric. This ensures that the P2P marketplaces are integrated with a wider instance of Interoperability Framework.</span>
|
|
|
|
* <span dir="">Smart contract templates for generating reports and audits about status of the marketplace and executed transactions - in line with regulatory and business requirements.</span>
|
|
|
|
* <span dir="">Smart contract implemented as semantic interoperability adapter for interfacing with the wider InterConnect Interoperability Framework.</span>
|
|
|
|
* <span dir="">Smart contracts for registering and identifying key actors and resources constituting P2P marketplaces.</span>
|
|
|
|
* <span dir="">Smart Contracts for integration of interoperable services which write data to or read data from the Hyperledger Fabric. This ensures that the P2P marketplaces are integrated with a wider instance of Interoperability Framework.</span>
|
|
|
|
* **<span dir="">Configurable order matching engine</span>**<span dir=""> for managing regulatory constraints, transaction priorities and conflict resolutions. The ordering engine also chains the smart contract calls performed by services participating in the P2P marketplace.</span>
|
|
|
|
* **<span dir="">White-labelled web application</span>**<span dir=""> for providing interface through which end users place orders. The web application can be instantiated and adapted to specific needs of a community establishing the P2P marketplace.</span>
|
|
|
|
|
| ... | ... | @@ -213,15 +212,13 @@ _InterConnect P2P marketplace enablers:_ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<span dir="">The P2P marketplace can be an energy marketplace or a marketplace for data transactions required for the realization of the community-based use cases. In the scope of the Task 5.4 the following P2P marketplace configurations are implemented and made available for the pilots and 3<sup>rd</sup> party integrators:</span>
|
|
|
|
|
|
|
|
* **<span dir="">Generic P2P marketplace configuration</span>**<span dir=""> that can be easily adapted to specific use cases in energy and IoT domains. This implementation also features a web application for demonstration purposes.</span>
|
|
|
|
* **<span dir="">Specialized configurations</span>**<span dir=""> based on participating pilots (each having specific set of requirements for integration of P2P marketplaces into instances of the Interoperability Framework):</span>
|
|
|
|
* **<span dir="">Dutch pilot</span>**<span dir=""> - IoT data exchange with loyalty tokens realized through P2P marketplace.</span>
|
|
|
|
* **<span dir="">Portuguese pilot</span>**<span dir=""> - flexibility and energy profile trading/aggregation in communities through P2P marketplace instance.</span>
|
|
|
|
* **<span dir="">Belgium pilot from Think E! and VUB</span>**<span dir=""> - P2P energy trading within and between energy communities through instantiated P2P marketplace.</span>
|
|
|
|
* **<span dir="">Dutch pilot</span>**<span dir=""> - IoT data exchange with loyalty tokens realized through P2P marketplace.</span>
|
|
|
|
* **<span dir="">Portuguese pilot</span>**<span dir=""> - flexibility and energy profile trading/aggregation in communities through P2P marketplace instance.</span>
|
|
|
|
* **<span dir="">Belgium pilot from Think E! and VUB</span>**<span dir=""> - P2P energy trading within and between energy communities through instantiated P2P marketplace.</span>
|
|
|
|
|
|
|
|
[P2P marketplace enablers repository](https://gitlab.inesctec.pt/interconnect-public/p2p-marketplace)
|
|
|
|
|
| ... | ... | @@ -240,10 +237,10 @@ _InterConnect P2P marketplace enablers:_ |
|
|
|
* <span dir="">SSA Service endpoint functionality – includes all necessary functionality to interact with the service via the offered (legacy) service API.</span>
|
|
|
|
* <span dir="">SSA mapping functionality – performs mapping of parameter bindings (semantic interface) to service API parameters and vice versa. Can be one-to-one mapping or more complex logic to combine for instance several API calls to complete one binding set.</span>
|
|
|
|
* <span dir="">SSA GA endpoint functionality:</span>
|
|
|
|
* <span dir="">Register the Generic Adapter instance for this service.</span>
|
|
|
|
* <span dir="">Register the Knowledge Base - this creates a smart connector.</span>
|
|
|
|
* <span dir="">Register the Knowledge Interactions (Graph Patterns).</span>
|
|
|
|
* <span dir="">Offer Knowledge Interaction execution.</span>
|
|
|
|
* <span dir="">Register the Generic Adapter instance for this service.</span>
|
|
|
|
* <span dir="">Register the Knowledge Base - this creates a smart connector.</span>
|
|
|
|
* <span dir="">Register the Knowledge Interactions (Graph Patterns).</span>
|
|
|
|
* <span dir="">Offer Knowledge Interaction execution.</span>
|
|
|
|
|
|
|
|
_Knowledge Base with its SSA and GA:_
|
|
|
|
|
| ... | ... | @@ -257,54 +254,63 @@ _Interoperability chain and message sequence chart between two interoperable ser |
|
|
|
|
|
|
|
## Supporting Tools
|
|
|
|
|
|
|
|
Two supporting tools allow complementary action to assess pre-testing and visualisation.
|
|
|
|
Two supporting tools allow complementary action to assess pre-testing and visualisation.
|
|
|
|
|
|
|
|
### SSA Test Tool:
|
|
|
|
The SSA Test Tool is integrated within the Generic adapter's control panel. It is directly accessible via the Generic Adapter local address.
|
|
|
|
Refer to this link for more detailed information.
|
|
|
|
|
|
|
|
The SSA Test Tool is integrated within the Generic adapter's control panel. It is directly accessible via the Generic Adapter local address. Refer to this link for more detailed information.
|
|
|
|
|
|
|
|
### Graph Pattern Visualiser.
|
|
|
|
The Graph pattern visualiser tool is available here. It allows to create a graphical representation of a graph pattern. It allows to identify all the nodes and connection among nodes of the pattern, leading to a better understanding of the data representation. Moreover, it also allows to find and solve loops in the data representation.
|
|
|
|
|
|
|
|
The Graph pattern visualiser tool is available here. It allows to create a graphical representation of a graph pattern. It allows to identify all the nodes and connection among nodes of the pattern, leading to a better understanding of the data representation. Moreover, it also allows to find and solve loops in the data representation.
|
|
|
|
|
|
|
|
## Interoperable DSO interface
|
|
|
|
The DSO Interface serves as a gateway between the DSO and external agents, namely Flexibility Aggregators. It bridges legacy DSO resources and interfaces into the InterConnect semantically interoperable ecosystem.
|
|
|
|
More information about this key exploitable result of the InterConnect project can be found [here](https://gitlab.inesctec.pt/interconnect-public/dsoi).
|
|
|
|
|
|
|
|
## Tutorials
|
|
|
|
The DSO Interface serves as a gateway between the DSO and external agents, namely Flexibility Aggregators. It bridges legacy DSO resources and interfaces into the InterConnect semantically interoperable ecosystem. More information about this key exploitable result of the InterConnect project can be found [here](https://gitlab.inesctec.pt/interconnect-public/dsoi).
|
|
|
|
|
|
|
|
## Tutorials
|
|
|
|
|
|
|
|
**Semantic Interoperability Framework: Overview**
|
|
|
|
[](https://youtu.be/sSXDMCeIw2o)
|
|
|
|
|
|
|
|
**Semantic Interoperability Framework: Technical Integration Overview**
|
|
|
|
[](https://youtu.be/-GCfEj-FAkUo)
|
|
|
|
|
|
|
|
**SAREFization process: Graph Pattern Creation - part 1**
|
|
|
|
[](https://www.youtube.com/watch?v=FM30JOFQDLo&ab_channel=InterconnectProject)
|
|
|
|
|
|
|
|
**SAREFization process: Graph Pattern Creation - part 2**
|
|
|
|
[](https://www.youtube.com/watch?v=l_QI7zoTazQ&ab_channel=InterconnectProject)
|
|
|
|
|
|
|
|
**SAREFization process: Create an SSA - part 1**
|
|
|
|
[](https://www.youtube.com/watch?v=GOUCN0KKpuo&ab_channel=InterconnectProject)
|
|
|
|
|
|
|
|
**SAREFization process: Create an SSA - part 2**
|
|
|
|
[](https://www.youtube.com/watch?v=W7ywyJSNEGs&ab_channel=InterconnectProject)
|
|
|
|
|
|
|
|
# Common European Reference Framework for Energy and Energy Apps
|
|
|
|
|
|
|
|
To be provided by 08.09.2023.
|
|
|
|
The overall goal behind Common European Reference Framework (CERF) for energy is to enable EU member states to be better prepared for energy crisis by empowering consumers to actively participate in solving the energy challenges thus improving grid stability in both proactive and reactive manner. All this by using innovative technologies supplied by the EU projects and organizations. The InterConnect project spearheads the CERF developments based on its experience in building cross domain semantically interoperable ecosystems capitalizing on the key enablers like SIF and DSOi. With these tools the key stakeholders can exchange knowledge in semantically interoperable manner and build energy apps using common enablers to drastically speed up the process of rolling out new consumer facing services.
|
|
|
|
|
|
|
|
{width=718 height=305}
|
|
|
|
|
|
|
|
## CERF for energy based on SIF and DSOi
|
|
|
|
|
|
|
|
InterConnect's approach goes towards building CERF as semantically interoperable ecosystem of key stakeholders. On one side we have public data sources like ENTSO-E transparency platform, and various regional and country specific data services. We also include grid system operators through DSOi and service adapters. From there we get data and grid signals that are fed into recommender systems. The interoperable data flows are facilitated by the SIF. The interoperable recommender services provide day ahead consumption plans, recommendations and eco tips. The consumption plans guide consumers to make meaningful impact onto grid stability while eco tips educate consumers on the best ways how to achieve the recommended consumption reductions. The signals and recommendations are supplied through energy app backend and user interface provided by the mobile or web applications.
|
|
|
|
|
|
|
|
An important feature of SIF and DSOi enabled CERF, is service chaining where data are transmitted among key stakeholders where each service adds mode context and knowledge to the grid signals and recommendations before presenting them to the end users. First, we start with what we call the mandatory energy app system configuration comprising two main services: 1. Grid service capable of providing grid signals to guide consumers; 2. Services that interface directly with end users – energy apps. Next, we add more types of services to the mixture like services from the energy market and retailers, energy management systems on home/building/community level and energy consumption monitoring and profiling services. The goal is to create ecosystem where these services can be chained in custom manner for each instance of CERF and energy app offering. This allows creation of highly customized and specialized energy apps with the same building blocks and capitalizing on the same interoperable data exchange facilitate with the SIF and CERF.
|
|
|
|
|
|
|
|
{width=806 height=385}
|
|
|
|
|
|
|
|
The interactions and integration of the supporting services for the energy app need to follow the InterConnect interoperability framework, as a fundamental building block to ensure that all developments made, independently of the stage, are prone to respect modularity, extensibility, and interoperability. Figure below depicts the supporting architecture that allow current and future developments for CERF instances and energy app demonstrators.
|
|
|
|
|
|
|
|
The WP13 realized the following reference architecture for the energy application and interoperable ecosystem of the CERF. The proposed architecture has two main subsystems (functional groups):
|
|
|
|
|
|
|
|
1. The interoperable CERF for data exchange - brings together results from the InterConnect project (SIF and DSO interface) and outcomes from other initiatives and projects with the mission of enabling trusted, secure, scalable exchange of information in a (semantically) interoperable manner. This is where the interoperable recommender service and data management services for public data sources are deployed. Finally, this is where all interoperable services and platforms from the InterConnect project are integrated.
|
|
|
|
2. The energy app with its backend - the apps running on mobile devices of consumers connect to the backend which serves the apps and provides the interoperable bridge towards the CERF/SIF.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### Data Sources
|
|
|
|
|
|
|
|
#### ENTSO-E Transparency Platform
|
|
|
|
|
|
|
|
|
|
|
|
#### Electricity Maps
|
|
|
|
|
|
|
|
|
|
|
|
### Interoperable Recommender Service
|
|
|
|
|
|
|
|
## Energy App Demonstrators
|
| ... | ... | @@ -317,8 +323,6 @@ To be provided by 08.09.2023. |
|
|
|
|
|
|
|
### Portuguese Pilot
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Useful links
|
|
|
|
|
|
|
|
[InterConnect project website](https://interconnectproject.eu/)
|
| ... | ... | @@ -335,4 +339,4 @@ To be provided by 08.09.2023. |
|
|
|
|
|
|
|
# InterConnect Project Prototypes
|
|
|
|
|
|
|
|
[InterConnect Prototypes](https://gitlab.inesctec.pt/groups/interconnect-public/-/wikis/Project-Prototypes) |
|
|
|
[InterConnect Prototypes](https://gitlab.inesctec.pt/groups/interconnect-public/-/wikis/Project-Prototypes) |
|
|
\ No newline at end of file |
