Having an IDS Con­nec­tor is a pre­re­qui­si­te for par­ti­ci­pa­ting in Indus­tri­al Data Space. The Con­nec­tor pro­vi­des the com­mu­ni­ca­ti­on inter­face to other par­ti­ci­pants in the net­work. The Con­nec­tor is not a pre­de­ter­mi­ned hard­ware and soft­ware with spe­ci­fied inter­faces but is a logi­cal ent­i­ty com­po­sed of dif­fe­rent ser­vices or com­pon­ents accord­ing to the task in hand – a com­plex topic and a pre­re­qui­si­te for the tech­ni­cal imple­men­ta­ti­on of Indus­tri­al Data Space. That is why a gui­de­li­ne was deve­lo­ped for mem­ber com­pa­nies and published in Novem­ber 2017 cal­led “Indus­tri­al Data Space – Con­nec­tor in a nuts­hell”.

“Mem­bers can be gui­ded by this, beco­me acquain­ted with the con­nec­tor spe­ci­fi­ca­ti­on and the refe­rence archi­tec­tu­re and begin with imple­men­ta­ti­on”, exp­lains Ralf Nagel of Fraun­ho­fer ISST and Head of the AP2 soft­ware deve­lop­ment, who wro­te the 25-page docu­ment.

The publi­ca­ti­on is divi­ded into three sec­tions:

1. From which com­pon­ents can you assem­ble your own con­nec­tor accord­ing to your indi­vi­du­al requi­re­ments?
2. How can the com­pa­ti­bi­li­ty of the con­nec­tor with other con­nec­tors be che­cked as a sup­ple­ment to cer­ti­fi­ca­ti­on?
3. How can com­mu­ni­ca­ti­on be stan­dar­di­sed in Indus­tri­al Data Space?

It is the third sec­tion that is par­ti­cu­lar­ly important for Ralf Nagel: “Here, I would like to empha­sise that Indus­tri­al Data Space does not deter­mi­ne a stan­dard API for data retrie­val, but descri­bes the indi­vi­du­al data APIs of con­nec­tors through a stan­dar­di­sed infor­ma­ti­on model (meta­da­ta)".

You can find fur­t­her details in the PDF that is avail­ab­le for all mem­bers in the down­load area.