1. Market Intelligence Service (MIS) Strategy Standards and Compliance
January
Market Intelligence Service (MIS) Strategy
Standards and Compliance

2. Gemserv and Xoserve collaborating on cross-fuel data products
Background
January
MIS originates from Ofgem’s desire for industry to design its own non-transactional interfaces for retail energy data
Gemserv and Xoserve collaborating on cross-fuel data products
MIS to date has focussed on identifying, prioritising and delivering use cases for specific data products or process enhancements
Leverages existing technologies where appropriate, e.g. ECOES and DES, but isn’t constrained by them
MIS’ key deliverables to date are third party intermediary and Supplier APIs allowing access to retail energy data
Discussions with MRASCo stakeholders and Xoserve over last few months to decide what focus should be in next year
Broad consensus that delivering current use cases has taught us things that inform the strategic position for MIS
There are initiatives being driven by Ofgem which beg questions the MIS should play a role in answering – MIData, Energy Data Taskforce, the consultation on code administration

3. What we have learnt
January
Value in the current use cases, but they are enhancements to as-is, which are increasingly seen as BAU delivery
Delivering use cases and exploring industry data landscape has highlighted more systemic issues with data access
Data is fragmented, governance is complex and no common data sharing standards exist to mitigate the problems
Ofgem recognise this, as evidenced in recent data initiatives focussed on rationalising retail energy data and ref
There is a gap in terms of pan-industry data governance, including consistent standards and practices around data sharing in industry

4. Striking a Balance
January
Users of energy data need consistent data products, that are pre-vetted to ensure they’re interoperable with existing data products
At the moment, there is no consistent set of standards or design authority to ensure that data offerings are consistent.
Users of energy data also need choice – needs are diverse, the domain is large and complex, and competition between data providers will benefit users and ultimately the consumer
At the moment, there is no definitive view of data products available across the industry
Therefore an opportunity to both foster consistency in data products and improve the choice of data products available exists
Balance particularly critical given Ofgem’s ambitions around enabling competition

5. A cross-fuel, industry-wide governance framework for data products
Future Role of MIS
January
A cross-fuel, industry-wide governance framework for data products
Independent of any specific codes
Gathers requirements from user community – connects users to appropriate existing data products and facilitates delivery of new products where needed
Creates standards for data sharing and assures data product compliance with them
“MIS-certified” data products - a whitelist of offerings that adhere to MIS standards
Not itself a data product – a way to give user community a single vehicle for delivering data needs, provide confidence in what they’re using and to avoid “wild west” around data
Not exclusive – open to any data product that meets standards
Would need a MIS delivery and architecture team to administer, which would be separate from specific codes

6. MIS Governance Model
January

7. The design authority for data products across the industry
Architecture Forum
January
The design authority for data products across the industry
Defines and maintains, in consultation with industry, the standards and the data dictionary
Approves designs for new MIS-compliant products or for changes to current products
Passes pre-vetted designs to specific codes or code bodies to implement, if that is needed

8. The vehicle for managing the overall Market Intelligence Service
MIS Team
January
The vehicle for managing the overall Market Intelligence Service
Acts as an interface between potential MIS users and MIS-compliant data products
Manages assurance providers, the product catalogue and MIS events
Sits outside of current codes, which are all focussed on specific parts of operational energy processes
Thereby provides pan-code hub for solving problems with non-transactional data products
Interfaces with the codes in so far as needed to provide MIS-compliant products

9. It would be composed of a number of individual standards, for example:
Industry Standards
January
A set of MIS standards would define to what we are expecting data products under the MIS to conform
Standards establish shared expectations for the way in which MIS data products will be designed and made available to users
They ensure consistency across the suite of products governed under the MIS
It would be composed of a number of individual standards, for example:
Data standards
Security standards
API standards
The standards could be adopted more widely as well – useful in wider industry contexts to define expectations for other data governance, e.g. address “battle of forms” being discussed for REL design and MIData

10. No good having standards if they aren’t adhered to
Assurance Providers
January
No good having standards if they aren’t adhered to
Conformity with the standards would need to be tested and confirmed by an appropriate assurance provider
This would be a precondition of inclusion in the product catalogue and a step in making changes to products already in the catalogue
The assurance provider could be a third party or panel of third parties
Also an option on some form of self assurance, either solely for existing products that are changing or for both new and current
Balance to strike is between robustness and cost/barriers to participation

11. A “Whitelist” of MIS-compliant data products
Product Catalogue
January
A “Whitelist” of MIS-compliant data products
Provides a single repository of everything available through MIS
Hosts a specification of the data products that references standards and the data dictionary

12. Builds upon and enforces the data standards
Data Dictionary
January
Builds upon and enforces the data standards
A centralised repository of information about industry data, e.g. meaning and purpose of the data, metadata.
Can be designed to be human readable and/or a machine readable repository from which potential data providers and users can make immediate use when building or consuming MIS-compliant products, i.e. a metadata repository for MIS
Improves time-to-market and underlying quality for MIS products
Minimises MIS user overheads in integrating MIS-compliant products
As with standards, has wider applicability than just MIS – could be the kernel for a wider standardisation effort in industry (to tie in with Energy Data Taskforce, MIData and Data Working Group).

13. Regular opportunity to identify new demand-led data products
MIS Events
January
Key part of engaging with MIS stakeholders, identifying opportunities and keeping MIS relevant
Engagement forum with MIS Users to showcase new additions to identify improvement opportunities for the MIS
Regular opportunity to identify new demand-led data products
Also provides a forum to showcase innovation, get feedback and build relationships inside the user community

14. Thank you
January
Questions?