Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time

Interface to Third Party Systems

Third-party system components are targeted to deal with transference of produced data for its further processing externally.

🌱 Domibus (Incubated)


:octocat: Git Repository 🐳 Docker Hub 📚 Documentation 🎓 Academy 🎯 Roadmap : TBD

What is Domibus?

Domibus is a sample implementation of a CEF eDelivery Access Point. CEF eDelivery helps users to exchange electronic data and documents with one another in a reliable and trusted way. The CEF eDelivery solution is based on a distributed model called the “4-corner model”. In this model, the backend systems of the users don’t exchange data directly with each other but do this through Access Points. These Access Points are conformant to the same technical specifications and therefore capable of communicating with each other. As a result of this, users adopting CEF eDelivery can easily and safely exchange data even if their IT systems were developed independently from each other.

Why use Domibus?

eDelivery helps to achieve the following goals: Interoperability: Implementing common technical specifications that enable diverse organisations to exchange data and documents. Security: Promoting an atmosphere of trust among all participants in the message exchange network. Scalability and Performance: Enabling the number of participants in the data exchange network to grow as well as the number of exchanged messages. Legal Assurance and Accountability: Promoting a high level of transparency and confidence among all participants in the message exchange network. Re-using CEF eDelivery will accelerate the delivery time of a working document and data exchange network and reduces the cost and risk of creating, maintaining and operating such a network. CEF eDelivery was already tried and tested in multiple domains.

This project is part of FIWARE and has been rated as follows:

  • Version Tested:
  • Documentation:
  • Responsiveness:
  • FIWARE Testing:

🌱 Oliot (Incubated)


:octocat: Git Repository 📚 Documentation 🎯 Roadmap : TBD

What is Oliot?

Oliot-MG is a mediation gateway which translates information from NGSI based IoT platform to EPCIS based IoT platform. This enables capturing state change in FIWARE context broker in the form of EPCIS Events.

Why use Oliot?

To solve the issue of interoperability, multiple companies, organizations, and consortia have started to join and create standards. Currently, the two of the major standards that are widely being considered in the IoT sector are EPCIS and NGSI. Nevertheless, the two standards differ both in data encoding and service interface which create fragmentation from the point of view of data consumers application. Moreover, the two platforms differ in the underlying philosophy of representing and storing IoT data; namely, NGSI is entity-based and EPCIS is event-based. This creates an overhead to analyze and process data coming from the two platforms.

FIWARE - EPCIS mediation gateway is developed to solve the interoperability between NGSI and EPCIS. It translates the entity based data from Orion context broker to EPCIS event. Moreover, enables traceability by capturing state change in FIWARE context broker in the form of EPCIS Event.