|
|
|
This is a public Wiki page for the InterConnect project. It lists the main technical results of the project and all resources that are needed for integrators to become part of the existing InterConnect semantically interoperable ecosystems, or build their own interoperable solutions.
|
|
|
|
This is a public Wiki page for the InterConnect project. It lists the main technical results of the project and all resources that are needed for integrators to become part of the existing InterConnect semantically interoperable ecosystems, or build their own interoperable solutions.
|
|
|
|
|
|
|
|
[[_TOC_]]
|
|
|
|
|
|
|
|
# Project goals
|
|
|
|
|
|
|
|
<span dir="">Energy and IoT domain convergence through cross-domain semantic interoperability is at the forefront of the InterConnect project.</span>
|
|
|
|
<span dir="">Energy and IoT domain convergence through cross-domain semantic interoperability is at the forefront of the InterConnect project.</span>
|
|
|
|
|
|
|
|
The project aims to establish interoperability framework validating semantic interoperability based on SAREF ontology.
|
|
|
|
|
|
|
|
The project will produce innovative, user centric energy and non-energy services.
|
|
|
|
|
|
|
|
The technological approaches will be validated in 7 large scale pilots in Belgium, France, Germany, Greece, Portugal and The Netherlands also including an overarching use case across all pilots.
|
|
|
|
The technological approaches will be validated in 7 large scale pilots in Belgium, France, Germany, Greece, Portugal and The Netherlands also including an overarching use case across all pilots.
|
|
|
|
|
|
|
|
# Project Organization
|
|
|
|
|
|
|
|
Organization of the project work packages and consortium can be seen [here](https://interconnectproject.eu/consortium/#structure).
|
|
|
|
Organization of the project work packages and consortium can be seen [here](https://interconnectproject.eu/consortium/#structure).
|
|
|
|
|
|
|
|
# Project outcomes and KERs
|
|
|
|
|
|
|
|
Here we list projects key exploitable results (KER) and outcomes that can be used by the wider public. Each KER has its own sub-section including figures, short introductory text and links towards detailed technical documentation, guidelines and software artefacts. The listed KERs are available for 3rd part integrators as complete set of enablers for joining te existing or building the new semantically interoperable ecosystems.
|
|
|
|
Here we list projects key exploitable results (KER) and outcomes that can be used by the wider public. Each KER has its own sub-section including figures, short introductory text and links towards detailed technical documentation, guidelines and software artefacts. The listed KERs are available for 3rd part integrators as complete set of enablers for joining te existing or building the new semantically interoperable ecosystems.
|
|
|
|
|
|
|
|
## InterConnect Ontology
|
|
|
|
|
|
|
|
Here is material on InterConnect ontology...
|
|
|
|
The starting point is the ETSI SAREF or Smart Appliance Reference ontology with its distributions for energy and buildings.
|
|
|
|
|
|
|
|
The project extends this ontology family with concepts specific to the cross-domain semantic interoperability requirements of the project.
|
|
|
|
|
|
|
|
So we have extensions for representing the user information and profiles, Device and sensor information and profiles, forecast and flexibility information which are very important in the scope of the project and finally connection information.
|
|
|
|
|
|
|
|
The project also uses other available ontologies for measurements, time representation and geo locations.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[InterConnect Ontology repository](https://gitlab.inesctec.pt/interconnect-public/ontology)
|
|
|
|
|
|
|
|
## InterConnect Interoperability Framework
|
|
|
|
|
|
|
|
Here is material on the InterConnect Interoperability Framework...
|
|
|
|
The InterConnect delivers an Interoperability Framework capable of bridging the integration gaps “within” and “between” the IoT and the energy domains.
|
|
|
|
|
|
|
|
The Interoperability Framework comprises:
|
|
|
|
|
|
|
|
* **Semantic interoperability layer** (using InterConnect ontology over SAREF) based on distributed enablers interconnecting all resources, platforms and services and enabling them to exchange data and instructions in a uniform and secure manner while relying on widely adopted interfacing technology (RESTful). Exchanged data is not stored or processed anywhere in between communicating parties.
|
|
|
|
* **Service Store** a catalogue of all interoperable services, including knowledge exploring capabilities, service testing sandbox and automated interoperability compliance tests, streamline onboarding of 3rd parties’ services and systems to become part of the InterConnect ecosystem ensuring growth of the interoperable ecosystems and creation of new ones.
|
|
|
|
* **DLT based P2P marketplace enablers** allowing community-based energy and data trading use cases to be implemented in a way interoperable with project’s ecosystem.
|
|
|
|
* Configurable **access control and knowledge handling procedures** so that stakeholders can maintain business logic behind their services.
|
|
|
|
* A **methodology** for building semantically interoperable ecosystem by instantiating and configuring Interoperability Framework enablers within and among digital platforms and services comprising the interoperable ecosystem.
|
|
|
|
|
|
|
|
The Interoperability Framework provides different means for instantiation from centrally hosted facilitator to distributed framework maintained by interoperable ecosystem stakeholders. The result is enabling components (services, devices, digital platforms) to interact with each other without having to know each other’s local native API, but purely based on the knowledge of ontologies and what ontology (category) a component belongs to (e.g., forecaster service). Finally, the knowledge-centric interface made available by the Interoperability Framework, based on SAREF, becomes the interoperable and common vision that links all stakeholders in InterConnect, while not limiting the expressiveness nor the diversity of each party.
|
|
|
|
|
|
|
|
_High level architecture of the InterConnect Interoperability Framework:_
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
_Levels of interoperability provided by the Interoperability Framework:_
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### Service Store
|
| ... | ... | |
