PDP dashboard provider webinar: part 2

Caroline Kyriazis

I think we're good to start Raman

Raman Dhaliwal

Thank you Caroline. Good morning all and welcome to this second webinar. We are running for organisations interested in becoming a dashboard provider in general, and those wanting to work with us during the early test phase of the programme in particular, which some of you may also refer to as the alpha phase of the programme. We will give you a bit of a background to the program, an overview of the architecture and the dashboard interactions. Some key aspects for you to be aware of and what our expectations are uh and then an opportunity for you to ask questions later. So during the session feel free to put your questions uh in the chat field as we go along uh we will try and answer all your questions, but any that we are unable to, we will respond in writing uh via the dashboard provider hub which has been set up on the pension dashboard program website. So i'll start off uh with introductions my name is Raman Dhaliwal i'm head of product for the pensions dashboard program and could I pass you on to Caroline first?

Caroline Kyriazis

Hello, I'm Caroline Kyriazis. I'm communications and Engagement Manager for the programme.

Raman Dhaliwal

Thank you Caroline, James?

James Reardon

Good morning, everyone. I'm James Reardon. I'm the head of technology development for pensions dashboard.

Raman Dhaliwal

Thank you.

Helen Scriminger

Hi, I'm Helen scrimmage. I'm the product owner for central

Raman Dhaliwal

Thank you.

So with that we shall start with our programme vision.

So our vision is to enable individuals to access their pensions information online securely and all in one place, thereby supporting better planning for retirement and growing financial wellbeing. And how are we going to achieve a vision we will do that by delivering the technical architecture necessary for the dashboard service to operate. Making sure that the architecture is secure, efficient, effective and is based on technology that is scalable and extensible. By creating governance arrangements that will protect individuals and support the operation of the dashboards. And finally, by working with stakeholders and users to create a service design for this dashboard service that delivers a very high level of satisfaction for the users of the ecosystem. Thank you, Caroline, can we go to the next three please? Thank you. So just wanted to share the pensions dashboards goals with you. We know that people find pensions confusing. Most people do not connect with their pensions until much later in their working career. The goals of the pensions dashboards are to connect people with all their pensions, presenting information clearly and in plain English. enabling people to understand what they're seeing and signposting them to impartial guidance and or regulated advice. Our aim is to increase people's confidence empowering them to make more informed decisions and choices about their pensions ultimately contributing to their financial well being in retirement. Next slide, please, Caroline. This is a very brief history of how we have got to where where we have back in 2016 Following the Treasury announcements announcement in budget about the Patriots dashboards. There was an industry led project managed by the Association of British Insurers and they were tasked to create a prototype to prove that it is possible for a to connect the users sitting at a desk dashboard to the various pensions that they may have different pension schemes and providers in 37. The prototype project published their findings in 2018. Government launched a consultation and to get views on what would be the best way of delivering this service and also to understand what are the key principles that are important to individuals and to organisations. In 2019, the moneyed pension service started setting up the pensions dashboard programme to develop the central digital architecture and in 2020, over the last year, the dashboard programme team undertook industry consultation which led to the first issue of the data standards. We are working on the next issue of data standards and we also prepared the technical requirements for all the procure an organisation to build the central technical architecture in 2021 Earlier this year, we led the procurement exercise and Capgemini working with Oracle were appointed to develop the architecture. We also define the alpha and beta stages and we have started engagement both with data and dashboard providers. Thank you Caroline. So what we would like to do is just share with you a very high level journey from a user perspective of what the users can expect from a dashboard.

Video

with more than two thirds of people holding multiple pensions, it can be tricky to get a clear and complete picture of your pensions. We set up a pensions dashboards, programme, or PDP. To tackle this challenge. Dashboards will be the place where you can view information about your pensions in a clear and simple format. But it takes a lot to make that happen. You begin your journey by navigating to a dashboard. Then you submit a request to find your pensions information, which is where things get a bit more involved. First, to keep your data safe, and Identity Service confirms that you are who you claim to be. You will be asked to give consent for your information to be used to perform the search on your pensions, and to authorise providers and schemes to send your pensions information to the dashboard for you to view you can withdraw your consent at any time. Now, the pension Finder service takes over. Importantly, it is not a database. More like a switchboard it never holds any personal or pensions data. The pension Finder service sends your request to all pension providers and schemes, which return a unique identifier to the dashboard for each matching pension. Then you can request the pensions information, which the providers and schemes will send directly to the dashboard where only you can access it. Pensions data will need to conform to a new standard. We are developing this standard with feedback from users as well as government and industry stakeholders to ensure it works for everyone involved. To keep your data safe. The governance register will ensure the pensions dashboards, ecosystem meets the required security and performance standards and dashboards will enable you to view your pensions information online securely and all in one place. So you can get a clearer picture of your pensions.

Raman Dhaliwal

Thanks, Caroline. So what is the technical architecture that will support this? I'm going to pass you on to James our head of technology to talk you through that architecture.

James Reardon

Good morning everyone. So I will be taking you through the spaghetti diagram on the left hand side. This is a visual representation of the data user flow through the system. My colleague Helen will then take you through the various API's are involved within that. So if we there are two main sort of user routes through the system, the first one being to find pensions. So this would be where a user accesses a dashboard either for for the first time for as a returning user, but wants to find their pensions. Now in this context dashboard could be an existing pension provider dashboard a mobile application single page application is quite agnostic on that. Because the first thing that actually happens when selecting finally pension is a redirect to the pension dashboards, consent and authorization service. Now if that user is a new user, in that they have not used this service before, they will first need to validate their identification. So at that point, there would be a redirect to an identity service provider who would confirm their identity. Once those attributes have been proved they will be sent back to the consent and authorization service where the user can then supplement that information with additional information that was then passed to pension providers for the purposes of searching for any pensions. So the consent and authorization will create that request to the pension and find and direct that to pension providers via an API and the user will be returned to the pension dashboard. That really is the end of the journey for the fines journey. What then happens in the background is that the data providers will if they do find any matching pensions, we'll create a unique identifier called PII, which is then registered with the consent and authorization service and can be retrieved by the dashboard. That then brings us on to the view stage of the process. So when a user logs in to view their pensions rather than find them. The dashboard will take this PIs which are dereferenced at this point, and will then resolve them to a URL. That URL is based at the provider where the pension asset is held. So the communication in terms of data is directly between the data provider and the dashboard. However, within that process, the data provider will actually consent will actually contact the contact the consent and authorization service to ensure that there is still consent to actually allow the dashboard to view that pension information. So there is an API between the provider and the consent and authorization service for that purpose. If those consents are still in place, then at that point, the dashboard will be able to pull that information from the data provider to display on their dashboard. Hopefully that explains how each of these elements fit together. My colleague, Helen will now take you through the detail of the API's that are involved. Helen?

Helen Scriminger

Hi everyone. So I have planned spaghetti diagram here. And this really shows you the technical components. On the left hand side we've got the API usage the dashboard providers need to implement and on the right. For completeness, we've added the data providers. I don't intend to go through those. So I'll start on the dashboard providers, festival unique dashboard providers need to retrieve any return PII. So there's an API that will pull those PII also, the VI can contain to the endpoint that you need to contact for the view. So there's a method of pulling input information so that you can resolve the VI to the endpoint or pension provider. Then the dashboard will obviously initiate the View API haven't resolved the endpoint, and that's held at a pension provider. And the access and permissions are managed through a protocol called a femur. which sits around those connections to the spaghetti diagram. We have a technical working group that's free for anyone to join. So if any of you would like to come along and get information on more detailed information on the API's, please let us know.

Raman Dhaliwal

We haven't received any questions so far. So please, if you do have any questions to remember to put them in the chat, we will take them now at the end of the session. We have some time set aside for that. And next slide, please, Caroline. So we thought we'd just take you through the activities over the next six months that we have planned and this is sort of the key period with which we are looking at potential dashboard providers to to work with us. So starting with October, so Claire, I'll get back to your question at the end as just sort of going through the timeline. And starting with October. We had planned some webinars. This is also the time when we have started the sort of the selection process off the dashboard providers who we would like who would like to work with us during alpha. The first webinar was earlier this week on the 18th. This is the second webinar they'll still be opportunities to ask questions you can always get in touch with us via the website or the contact details that Caroline will share later on. If you continue to have any concerns questions regarding this.

Raman Dhaliwal

So the deadline for the return of the completed questionnaires which we will send out to organisations who have expressed an interest to work with our steering helper is fifth of November. During the member we will undertake selection exercise to select the successful candidates who will be working with us during the Alpha stages the test stages and we plan to announce the successful candidates by mid December and in December we also want to sort of start thinking of what we want to do during private beta how we select additional dashboard providers to work with us during private beta at which stage we will be using live data during the test phases in alpha. We intend to use dummy data only. If you're working with data. January to March our focus will be most of our focus will be on user research. And that user research will feed into work around the design standards and design guidance. And that is where sort of all organisations who have an exposure who have expressed an interest to be working with us. Our expectation is that this is where we will be working with you to understand how these design design standards and design guidance have an impact on on you as a dashboard. Provider and how we work with you then to agree what these would be. We'd be working very closely with the Financial Conduct Authority as well because they are the ones who will be regulating the dashboard service and we don't expect at this moment or connection as sort of technical connection to the central architecture during this phase. We will keep you informed around when that will happen and how that will happen as we go along. So a lot of this is dependent on the progress that supplier makes in building the central infrastructure that to those who will be working with us and for those who are not we will keep updating everyone via our website. So just coming to Claire's question, at what point will participants be expected to have an operational dashboard that is terrain it betta Claire that is our current assumption at the moment. But as I said, if you're working with us through sort of January, February, March and April, we will know at what stage that expectation is but again, if you as a data provider are not ready, it is not a requirement. There is no deadline for you to be required to be ready to have an operational dashboard. It is dependent on how quickly you will be able to provide one Shavon how many candidates I'll be looking for in the alpha stage. We're looking for about two to three commercial dashboard providers to work with doing alpha to help us understand sort of what how the design standards and guidance have been built. what impact that has on you as an SRE as a dashboard provider and also to help us respond to user research by looking at the prototype that you may have the front end prototype that you may have to do some further research with the users. So two to three at the moment. But we will also be working closely with the money and pensions dashboard team which is slightly different to the pensions dashboard programme it sits in a different part of the organisation. Gary, what approval process will dashboard providers have to go through for onboarding apart from FCA Will there be a kite Mark accreditation stamp for providers? So yes, there will be the FCA process which will be developed and created over the next while during 2022. Is there will there be another Kitemark accreditation stamp? We haven't yet created that or thought a lot about that from our perspective. It is the standards the design standards, which will be a requirement for anyone who wants to be a dashboard provider. But Helen, could I bring you in if there is anything that you are thinking of from the governance perspective?

Helen Scriminger

Yes, we are looking at that. However we need to we need to look talk to the regulators and policy colleagues to make sure that the kite mark is something that they want to proceed with.

Raman Dhaliwal

And Gary The other thing is, this thinking will develop during the next few months. And there will be engagement with organisations who are working with us and even those who are not working with us via the dashboard providers hub on our website. Okay, thank you Caroline.

Raman Dhaliwal

is so the next slide. I am going to ask Helen to talk us through. Thank you Helen.

Helen Scriminger

Okay, so there's just a rundown on what's needed as it to become a dashboard. So it's gonna have a separate, regulated activity under the FCA. Obviously, Anybody wishing to become a dashboard will have to adhere to the FCA rules. But it will as I said be a new authorised activity. It's not currently any regulation in place and this is being developed as we speak. So access to the alpha testing will be undertaken. On the understanding that authorization is not guaranteed or automatic when there was a regime is put in place. And it's expected that once the programme moves from testing into a service using real data, authorization will be mandated.

Raman Dhaliwal

Thank you. Thank you. And next slide please. So, again to the point that you won't have raised earlier so you're seeking two to three dashboard providers who will be working with us during the early phases during Alpha. Working with us will allow you to provide some input into the development of the key processes to support the onboarding and management of the dashboard provider community. So this is about sort of what technical support is needed. How do we make that process as smooth as possible? Service and the design standards which I have already mentioned, that will underpin the presentation of pensions data to users. Also development of regulations and how they are applied by FCA and provide input into the testing of the architecture and gaining insight into the development of the architecture. However, I do want to point out that we will also be sharing findings and knowledge openly via a range of means. The dashboard that I dashboard providers have that I keep referring to definitely is going to be one of those means and potentially other webinars if we feel there is there are a lot of questions that we are getting. Thank you Next slide please, Caroline. So in return we are asking you to be open and collaborative with other dashboard providers and with us in sharing your existing knowledge and research and be able to commit resource to this work that is very important and if possible, be able to at this stage when we are using live data, be able to provide early client these to support the testing and be able to share your dashboard prototype for testing and responding to user research. And finally, we want to make sure that any organisations that we are working with have not had previous authorization by FCA withdrawn. I think that was the last slide Caroline. Is that correct? Yes. So here are a few sort of contact details for you to keep in touch with us. So shall we go to more questions in the chat?

Helen Scriminger

So I've answered Martin's one, I think and he said thanks. So that's good. And I've had one question outside of this that alludes to being able to use PUI outside of the dashboard. So we didn't see any reason why you shouldn't, although obviously, the dashboard would not be involved in as resolution endpoints outside of the dashboard. So using the API that identifies the asset is probably the level at which it can be used outside of the dashboard. Please correct me if I'm wrong.

James Reardon

That's correct.

Raman Dhaliwal

Helen, I'm just checking one of the answers you mentioned 40 schemes? Oh, yes.

Helen Scriminger

It's 40,000 schemes.

Raman Dhaliwal

What it would be so equally by the end of next year. Thank you. So Claire has asked him another question. So will the alpha phase work be regularly shared with dashboard providers who are not Alpha participants? That is the A definitely the eighth

Raman Dhaliwal

and Shavon what stayed is the development of the identity service. So she won't we are not developing the identity service. We are going to put an identity provider identity verification provider. We are currently in in the procurement stages of that process.

James Reardon

Yeah, we are procuring and interim identity provider to cover us through alpha and early stages of beta. This is with a view to looking at formulating under the government framework, in future when we go to public beta, but certainly for for the purposes of development, we are procuring a single identity service for the internet.

Raman Dhaiwal

Thank you for that clarification, James. Garry, are we interested. Are we testing? Yes, we will be testing web app. These functions guys. Sorry, James. Helen, do you want to add to that?

James Reardon

I'm sorry, which question Gary's?

Raman Dhaliwal

Gary's question. Are you interested in testing different channels for the dashboard provision like web app based?

James Reardon

I think do during Alpha? Probably not. I think as we as we continue will, we will look at that in more detail. I think really the main influence on that will be on the user research side rather than the technical as the route through the ecosystem will be the same. Whichever the channel dashboard provision is.

Raman Dhaliwal

Thank you. So Mohamed's question, no call for data providers during the alpha phase while dummy data is used. If I understood when I data providers in bold, called upon to influence the design.

James Reardon

I'll pick this one up as well. So data providers are already involved in influence. I spoke through the ecosystem technical working groups that Helen shares but also in that we have seven data providers who are also undergoing alpha at the same time. Yes, using dummy data to start to whilst we test all the connections, but then, once obviously the system is in life and security hardened. We will be using live data.

Raman Dhaliwal

And if I could just reiterate the design of the front end dashboard will be dependent on the user needs. And of course, we are working with data providers to see how best to provide that data. Paul's question who and how do I contact to become involved in the mentioned Technical Working Group? Helen, do you want to take that?

Helen Scriminger

Yeah, just just contact PDP events I think Carolyn contacts page there with an email. That's it, thank you. Event at PDP. Just use that. I just do.

Raman Dhaliwal

I just to clarify for everyone events. [email protected] is if you'd get in touch with us on that email. We will respond to you very quickly. Any final questions?

Raman Dhaliwal

Shavon I may be able to find this one on the website but could you share when you hope to complete the alpha and beta stages and what is your estimated go live date and our alpha stage is ends in April. Is it me, James?

Yeah, we will end on for in May and the first phase of private beta that will start in June. I believe that will take us up to the end of March 2023. Which point we will then go into the second phase of beta

Raman Dhaliwal

private and sort of say I think it may still be private beta.

James Reardon

Yes, but I believe that's where we will start looking at stage onboarding for data providers.

Raman Dhaliwal

So the Go Live will will really depend on the onboarding timetable as well and how the service is doing. Will dashboard providers also be expected to undertake user research or are PDP responsible solely for this? Gary as a dashboard provider, you may want to undertake your own users to see what sort of service you want to provide or what sort of an onward journey you may want to provide. We will definitely undertake user research, but on as a dashboard provider, it's up to you if you want to undertake user research to sort of create a product that suits the needs of the users of your service.

Raman Dhaliwal

And we will be sharing our the findings from our research. I will summarise findings from our research on an ongoing basis.

Raman Dhaliwal

So looks like that is it I can't see anyone typing Caroline, can you?

Raman Dhaliwal

I'd like to say thank you to all of you for attending. And thank you for your interest in becoming a dashboard provider. We are keen to stay engaged with you and we are keen for you to to look at our application and we look forward to hearing from you thank you very much.