Defining DIP Manager data and how it can be shared

What is the issue?

The DIP Manager has an operational need to access and use Common Block data (transactional data). However, the DIP Supplement and DIP Subsidiary Documents (DSDs) do not explicitly define what information is included in DIP Manager Data, and it is unclear whether Common Block data is contained within it. This is an issue because there is a lack of clarity on what data the DIP Manager can access and use.

Furthermore, there is no existing mechanism in the DIP Supplement or DSDs to facilitate the sharing of Common Block data (or DIP Manager Data) with Code Bodies; the DIP Supplement and DSDs currently support only one-off data sharing, not the continuous data flows now being requested. This is an issue because without the ability to share this information continuously, Code Body assurance functions will be affected.

What is the proposed solution?

In order to resolve the ambiguity of what information can be accessed and shared it is proposed that the DIP Supplement and DSDs:

• Clarify in the DIP Rules that, due to the transactional nature of data contained in the Common Blocks (headers) and the operational need for the DIP Manager to access this data for ongoing service management and issue resolution, such data shall be defined as DIP Manager Data.

• Establish a mechanism within the DIP Rules for the sharing of DIP Manager Data —including data from Messages’ Common Blocks—with relevant stakeholders, such as Code Bodies. This mechanism should also provide a clear legal basis (based on data protection requirements) for the DIP Manager to share personal information, such as MPAN data, where necessary and appropriate.