It’s been some time since the last update, but we’ve been making good progress on our journey towards migration from the Government Gateway. During this period we have been working closely with Government Digital Service (GDS) to help inform the Discovery phase for a project examining user needs in ID Assurance for Organisations and Authority Management (IDAFOAM). HMRC was at the forefront of providing subject matter experts and dedicated support to this work, which ensured our customers’ requirements were fully understood.
At the third party software workshop in mid-December, the IDAFOAM team held a user needs session with our regular attendees. Talking to software developers gave the team greater understanding of a wide variety of businesses, agents and users, and particularly what the impact of IDAFOAM might be. The session yielded a number of specific user stories and highlighted the dichotomy between Portal-based interaction with HMRC and submissions made through third party software. A key distinction was in the way authority management in third party software is tailored around the business using the product rather than a generic concept of a user.
Outcomes from the IDAFOAM Discovery were showcased recently and it was positive to see HMRC’s user needs properly reflected in the findings. The IDAFOAM team will now focus on an Alpha stage, which should produce some working prototypes that can be tested with users and iterated ahead of developing a beta release. We will also be contributing to this Alpha stage by designing a proof of concept of an application consuming authenticated tokens to interact with HMRC. This will be demonstrated in a small piece of work using a stubbed-out test version of PAYE Desktop Viewer. We’ll let you know when this gets started and share the findings with you as we progress.
We are also getting our plans in place for the Digital Transaction Engine project to begin. The work has been commissioned and we are trying to secure resource for a Discovery phase that will validate our assumptions around user needs. Upon completing this, we will have a clear understanding of time and resource requirements needed to build a replacement Transaction Engine, and a defined migration path for our core services. Details of what this migration may look like are contained in previous blog posts, but we’ll also keep you updated as work progresses.
There is no workshop in February this time round, but we plan to pick up with them again from 14 March.
If you have any questions about this, just get in touch.