ContainER

Project ContainER will deliver a data-coordination platform that enables industry participants to discover and access data that is mastered by the most suitable data owner. The project is based on the principle of integrating and coordinating existing datasets that already exist across the industry and using modern distributed system architectures to facilitate this. The proposed system architecture design and prototype roadmap will have the aim of creating scalable authentication and access protocols to increase data mobility across the industry.

This approach will:
• facilitate the creation and adoption of modern data exchange standards and APIs
• improve data quality by ensuring parties access data mastered by the most suitable owners
• increase data visibility and provide secure access mechanisms for data owners to share and distribute data in accordance with EDTF principles.

Energy data is currently held in multiple silos across industry bodies, often as part of a code or regulatory requirement. Given the specialist roles being undertaken by such bodies in providing and mastering data within the industry, it makes sense to build a system around the principle of these bodies maintaining ownership and mastering rights for these datasets based on different standards, formats and technologies.

Use cases are then implemented via a ‘Data Service Protocol’ (DSP), which define the data structures and sharing permissions for that use case. The DSPs are a fundamental element of the platform and can be used to implement and enforce elements of the use case governance. User identity and authority are managed through a KYC system that DSPs then utilise to ensure appropriate secure authorisation is provided for each interaction.

To enable data owners to provide secure access to hosted data, a suitable governance model must provide certainty that regulatory and legal requirements are adhered to. We will implement a two-tier model where the platform governance (maintenance and direction of the decentralised protocol) is separated from each individual Data Service Protocol or use case. Their requirements are then enforced via the platform as part of the data access processes.

The proposed approach allows data owners to control and view access to and use of their data. Each use case where data is linked to the system is independently defined and governed; combined with transactional data it is possible to create a clear audit trail and record of access for authorised parties.