Data providers timeline and steps to connection

Organisations that provide data to the pensions dashboards ecosystem will include pension providers, schemes, trusts, third party administrators (TPA) and integrated service providers (ISPs). All of these data providers need to take a series of steps to prepare for connection to dashboards.

Timeline

The diagram below outlines the key milestones that relate to data providers and how they relate to the programme phase plan.

Data providers steps to connection

We’ve set out what data providers need to do to connect to dashboards within each phase of the programme in our steps to connection below.

You can find out more about the programme phases for more about programme activity or view the full programme timeline for more on the responsibilities of different ecosystem participants, within each programme phase.

Preparation phase one

This is the set-up phase of the Pensions Dashboards Programme. As indicated in the diagram there are three significant milestones in this phase for data providers:

  • the staging Call for Input, which will provide additional detail on the proposed timings and order of staged onboarding to dashboards
  • retirement income guidance update, which will provide guidance around reporting estimated retirement income on initial dashboards
  • architecture supplier onboarding, when PDP contracts the technical architecture supplier

The information below describes what data providers need to do to prepare to connect to dashboards during this phase.

Find data

Perform an audit of the required data items. Understand what data gaps exist and how you will plan to fill them.

Identify what key data is held in a non-digital format. Understand how you will input this information into your core database to ensure this can be accessed digitally.

Understand how your data cleanse activities for dashboards can complement your other data cleanse projects. Where possible, this may reduce your overall effort in cleansing data.

View data

Perform an audit of the required data items to understand any challenges in providing an accurate pension value to display on dashboards.

Identify what key data is held in a non-digital format. Understand how you will make this data digitally available.

Understand how your data cleanse activities for dashboards can complement your other data cleanse projects. Where possible, this may reduce your overall effort in cleansing data.

Understanding dependencies

Identify who you will need to engage with in your preparation. Typically this will involve your pension administrator (in-house or third party) and/or your system software provider. It could also include external additional voluntary contribution (AVC) providers, where you do not hold full details of the AVC entitlement.

Connecting to the ecosystem

Begin considering how you will connect to the pensions dashboards ecosystem via open standard APIs and the security protocol for user managed access (UMA).

You may need to discuss this with your software provider or administration provider to understand their proposed approach.

Preparation phase two

This is the develop and test phase of the Pensions Dashboards Programme. As indicated in the diagram there are several significant milestones in this phase for data providers:

  • consultation on the regulatory framework, when DWP and FCA consult on regulations and rules relating to dashboards and staging
  • identity supplier onboard, when PDP contracts the identity service supplier
  • technical guidance to support data provider technical development, when PDP publishes a full set of technical standards and ecosystem governance information
  • early testing with volunteer providers

The information below describes what data providers need to do to prepare to connect to dashboards during this phase.

Find data

Determine the matching approach you will use to process a find request. This will involve determining which personal data fields you will compare, such as name, date of birth and National Insurance number for example, to validate a positive match. We suggest you work with your software provider and/or administrator to help identify the best approach.

Perform an audit of the data fields used to perform the matching process, to understand what gaps may be present.

Consider your approach to partial matches. We will provide further guidance on our approach to partial matches during this phase.

Consider how you will continue to monitor the accuracy and presence of find data.

View data

Consider your approach to the following questions:

• will pension values be provided on demand or via a stored value
• where annual benefit statements are provided, is information stored within a database to allow this value to be returned to dashboards

An industry working group is considering the basis for providing Estimated Retirement Income (ERI), PDP will monitor the findings of the group and align where necessary. In the event there is any change to the existing basis, we would recommend that you consult with your software provider and/or administration provider to understand any required changes to the underlying software.

Understanding dependencies

In this phase, you should have gained a full understanding of what dependencies exist with external third parties and with them, begin to plan how you will connect to the ecosystem.

Connecting to the ecosystem

Begin considering how you will connect to the ecosystem (dashboards). Is your administration digitally enabled and can it support the open API and security requirements for connecting to the ecosystem or will you require an alternative Integrated Service Provider (ISP) or middleware solution to connect?

Assess the impact of the potential traffic from the ecosystem and its effect on the performance of your core systems, bearing in mind that you will get a find request from every pension owner who requests to find their pension. Current estimates are 6 – 9 million users annually.

Consider whether a middleware ISP solution provides any advantage in protecting against this? What solution has your software provider or third party administrator proposed for connecting into the ecosystem?

In the event you use an ISP/middleware solution how much work may be needed in mapping required data items to any ISP/middleware solution?

Preparation phase three

This is the voluntary onboarding and ongoing test phase of the Pensions Dashboards Programme. As indicated in the diagram the significant milestones in this phase for data providers include:

  • voluntary onboarding
  • regulatory framework in place, when the full set of regulations, standards and guidance from government, the regulators and PDP are all in place

The information below describes what data providers need to do to prepare to connect to dashboards during this phase.

Find data

Any required data cleansing or work required to fill missing data items should now be progressing.

Ongoing data validation and audit of key data fields should be maintained over the period prior to connecting with the ecosystem.

You will have agreed an approach for how you will deal with partial matching.

View data

By this stage, any required data cleansing or work required to fill missing or non-digital data items should now be progressing.

Ongoing data validation and audit of key data fields should be maintained.

How to report on ERI will have been agreed and you will be able to comply with this.

Understanding dependencies

Plans are in place and are aligned with your anticipated staging date.

Connecting to the ecosystem

You have agreed an approach for connecting to the ecosystem and are working with your software provider and/or third party administrator to plan the implementation and testing of the chosen solution.

As further details of the model for compulsory onboarding become available, consider when you are due to connect and how this may impact on your planning and the implementation approach you may have agreed with third parties. Do your current plans provide sufficient time to prepare or are there elements of your preparation you need to realign to ensure you are ready?

Consider the potential possibility and advantages of voluntarily connecting prior to your compulsory staging date, with your software provider and/or third party administrator.

Any required data mapping to facilitate any ISP/middleware solution has been planned and is progressing.

Preparation phase four

This is the staged onboarding phase of the Pensions Dashboards Programme. As indicated in the diagram the significant milestone in this phase for data providers is:

  • staged compulsory onboarding commences, when data providers start to connect to dashboards in the order specified by the regulations and rules

The information below describes what data providers need to do to prepare to connect to dashboards during this phase.

Find data

You are confident in your ability to provide all the required data items.

Any non-digital data has now been loaded on to your core systems and is now digital.

You have an agreed matching basis. This has been tested and assessed through the testing of your find functionality prior to your agreed staging date.

View data

You are confident in your ability to provide all the required data items.

Any non-digital data has now been loaded on to your core systems and is now digital.

You have an agreed basis for providing ERI and this has been tested and assessed through the testing of your view functionality prior to your agreed staging date.

Understanding dependencies

Plans are progressing and been validated against your confirmed staging date.

Connecting to the ecosystem

Your implementation plans should be in progress and aligned with your staging date.

Together with your software provider and/or administration provider your plan will include testing of find and view functionality prior to your staging date.

You have familiarised yourself with the onboarding process and have all the necessary information and support in place to begin onboarding.

You have assessed the additional workload that may be created from your customers using the dashboard and identified the most appropriate channels to deal with queries arising from the ecosystem.

For more information that relates to our data providers timeline plan, please see our programme timeline and programme phases.