Jason Fox added a comment - 29/Jan/19 3:13 PM - edited Email sent: I’m writing in response to your query about how to bring company data into a FIWARE based solution. The central component of FIWARE is the Context Broker which sends and receives data via a well defined Interface known as NGSI. In order to insert data from another format into the context broker you will need To transform the input into the NGSI format somehow. There are several ways you could do this dependent upon what the "data” is and how you wish to interact with it.: It is possible to create entities directly - there is a swagger definition which can be used to generate library stubs: https://swagger.lab.fiware.org/?url=https://raw.githubusercontent.com/Fiware/specifications/master/OpenAPI/ngsiv2/ngsiv2-openapi.json Use of such a library is described in the following Tutorial: https://github.com/Fiware/tutorials.Accessing-Context For state data coming from IoT Devices there a series of IoT Agents available which will take data from a series Of well-known device format and transform it into NGSI Entities. For more information look at the catalogue entry on IoT Agents: https://github.com/Fiware/catalogue/tree/master/iot-agents There are also third-party tools available for generating context date (for example using Node RED) https://flows.nodered.org/node/node-red-contrib-fiware-orion If the data is complementary to the existing context entities, then it would be better to subscribe to the data via an NSGI subscription, Such data resides outside of the context broker and is available via a pre-existing REST API but can be retrieved as if it were within The context broker. https://github.com/Fiware/tutorials.Subscriptions An example of the relevant code can be found here: https://github.com/Fiware/tutorials.Step-by-Step/tree/master/context-provider/controllers/proxy The key to these interactions is to ensure that the data has a well defined Data Model, typically based on an industry standard schema, A series of such data models can be found below: https://github.com/Fiware/dataModels If your industry follows the schema provided from an alternative source that would also work, the key is to try to define common terminology.