Transcript for Implementation Plan webinar - August 2019
Thanks, everyone for joining online will start the webinar in about two minutes. We're just waiting for a few more attendees to join the webinar.
You have joined APRA's new Data Collection Solution Implementation Plan webinar for reporting entities. This webinar is about to commence. Please note that the webinar will be recorded and made available after the session.
Good morning, and thank you for joining us for today's webinar for reporting entities on the new Data Collection Solution. This webinar follows the release in July of the updated Implementation Plan. My name is Jane Coad and I am the Readiness lead for the New Data Collection Solution with me here today. We have two other presenters Daniel Hunt who may be familiar to many of you is the business lead for this project. And Natalia is our change lead. We also have James Burke from Vizor software our technical partner for any of the technical questions when we get to Q&A.
The purpose of today's session is to highlight some of the information in the recently released plan and it gives us a chance to address some of the questions that you may have. Natalia will also walk us through a demonstration of some of the features that you'll see in the new solution. And so it's a great opportunity for you to gain an early understanding of the look and the feel of the new solution. We have a full agenda today, which will see on screen the firstly I'd like to take a chance to thank those of you who have provided some questions to cover her head of the session. We will address these areas as much as possible throughout the presentation for any additional questions. Please type them into the question functionality in the webinar. If your question is industry-specific, please include your industry in your question, we do have some dedicated time for Q&A at the end for those questions that we don't get to we will get back to you after the session.
We're also going to do two live polls that we will launch during the session. This will give us a great chance to get some insights from each of you on where you are at in your readiness journey as well as gauging the level of change that may be brought about by the new solution. I'll now hand over to Daniel who will get us started with an overview of where the project team are at with the new solution. Thanks Jane. Hi everybody and thank you for joining us today.
As you can see on the timeline that's now on screen APRA released an update to the Implementation Plan on the 30th July and announced we're extending the implementation timeline which will see a shift in the target date for the external test environment and also for the go-live. The external test environment is now expected to be released in quarter one of 2020 and we expect the go-live of the full solution later in 2020.
So you might ask yourselves, why is the date shifting? Well, since April after has been working closely with Vizor Software and Dimension Data to design the new solution and during this time has been become clear that additional time is needed to transition to the new solution. APRA is managing a wide range of internal and external risks and interdependencies. This is a complex project, replacing a twenty-year-old solution is a large undertaking. So we feel it's right that we take a measured approach to ensure we deliver the secure quality solution we have promised.
Some of the factors of informed our decision are the customization and bespoke features built into D2A which have been identified as we finalize the design. For many of these we've decided to implement work arounds and configuration changes to the vanilla off-the-shelf Vizor product. So as to meet a commitment to minimize impacts to entities are go live, however, in some instances, it's not appropriate or possible and we will be requiring entities to make changes and we'll be discussing these more details shortly.
We've also opted to include an additional module into the solution. They'll provide a single contact repository accessible by APRA and by entities to facilitate entity profile management and future executive accountability reporting.
And throughout this period of design we have been continually consulting with industry through our working groups. We've discussed a range of topics particularly with regard to the strategic direction some of the technical aspects and our approach to implementation of the solution and the feedback that we're getting so far is that reporting entities are supportive of the timeline shift.
What does this mean for APRA and for reporting entities? Well for APRA it means we have more time to work through some of the key changes between D2A and the new solution including working with other government agencies. For instance, the ATO on the myGovID authentication solution. Yes, and for entities the additional time will help us to ensure really good preparation for the transition to the new solution including being able to use the test environment to practice submission and test the business processes that you have. As mentioned, the test environment is expected to be available in Quarter 1, next year. It's really important for all entities to be ready to use the new solution by the go live date so that you're reporting obligations continue to be met. APRA will not grant extensions to entities that are not prepared for transition to the new solution. However, entities should rest assured that D2A will remain available after March 2020 to ensure you can continue to meet reporting obligations whilst the new solution is being finalized and implemented.
We do remain committed to consulting with industry and providing regular updates on further key decisions and providing extra information where we can to help support your preparation. APRA expects to provide an update on the implementation dates for the new solution by October. During this time APRA will continue to provide industry with sufficient information and time to prepare for the new solution. Please make sure you keep up to date on the 'APRA is replacing D2A' webpage which will hold all the latest news and updates.
Now before we dive further into the Implementation PIan, we'd like to pause and launch the first of the two polls we're going to run this session. This poll is to understand where you are in terms of your own internal preparation. So the question we are asking is "My entity is taking steps to prepare for the new Data Collection Solution." Okay, so we're now going to launch the poll and you'll see that we have three options to choose from so if you are just beginning your journey should answer A you maybe have identified your project team or key contact or you may have commenced mobilization and planning activities. So again, the question my entity is taking steps to prepare for the new Data Collection Solution. Just beginning our journey, identified our project or key contact, commence mobilization and planning activities, and we'll just give you 30 seconds or so just to just to think about that and put in your answers.
Okay, that's great. We just look to close the poll now we've had a good number of answers. So just close the poll and then the responses should be displayed on screen for you. So here we go so we can see, you know bit of a mixed bag. We got a number of people there commence mobilization, but it would appear the majority of people are just beginning a journey. So Jane any comment on that? Yes. Look, it's great that we've got those people are on board today because today's session is really a chance for you to get some of the information that you need to begin to prepare your journey. It does give you a bit more of an overview of the Implementation Plan and what's in it, and direct you to some of the information that you will need to kick-off and mobilize your forces - it's great to see. Okay. Well now going to hand back to you Jane to kick us off on the overview of the Implementation Plan.
Thanks, Daniel. I want to go through a few slides in terms of the Implementation Plan and what information and key takeaways we have in there just firstly the implementation plan itself. We structured that in sort of four key areas. What is the new data collection all about? APRA's future direction for data collection, and many people so far has shown some interest in this area, the implementation approach and timing and as Dan mentioned we will be coming back to you with more information on the revised project timelines in October
So you have the information you need to transition to the new solution. And then preparing for the new solution itself and later in the webinar will review some of the key actions that you can take, but the focus of today's session is to talk through some of the key changes called out in the Implementation Plan that may impact your entity.
However, for us a key principle that we are working with is to minimize changes as much as possible for the go live and that's because we want to make the transition as smooth and successful as possible. So before we dive into the changes just let's quickly recap - What's not changing? So your reporting obligations and your schedules and the data that we collect in the existing returns all remain the same. We will continue to consult with industry on any new or revised regulatory collections. We envisage that the availability of the test environment that's going to aide future consultation particularly, I think around data collection design and it will be available going forward for any readiness activities that you may need in terms of any new collections.
You will still be able to submit of course through manual entry XP XML and XBRL and the logic that you're familiar with regard to the validation formulas in D2A will be reproduced in the new solution. Let's now turn to what is changing so over the next few slides. I'd like to highlight the areas of access to the new solution data submission and validation and Daniel's going to jump in and talk a little bit about resubmission processes.
All of this and more can be found in the Implementation Plan itself and more information will become available on APRA’s website. So stay tuned to that one. Most of these changes, we think, are really positive. They do address pain points that were highlighted during the early engagement with industry last year.
So we're quite excited about the new solution going live. So the new solution is web-based portal. It requires no additional software on your end - and I think that's a welcome move away from the D2A client and hopefully it'll make a few of your IT colleagues that little bit happier in terms of their maintenance schedule. We are moving to the myGovID for authentication. There are two components that you should be aware of for myGovID. Individuals within your entities will need to obtain their own unique myGovID credentials and once that's done they can then be linked to your organization.
We have received a number of questions from you regarding my myGovID. particularly around the offshore access and the availability of the app for Android and desktop. It's important that you know, we are working closely with the ATO. They are aware of these requirements and are continuing to work through this. For the most up-to-date information, we encourage you to contact the ATO directly via the support channels on their website. They do include a direct line to speak to someone within the myGovID team. We’ve included a link to their site in this presentation just a little bit later.
You will also have access to the secure testing environment that also will be using myGovID. You'll be able to access the test environment before go live to familiarize yourself with the new solution, as we said it will also be available on an ongoing basis after got go live. Now a big change with a new solution will be the onus and the responsibility of managing user roles and access rests with each entity as well as the business process you will need to support it. This will enable you to have control of your own information and update it quickly and easily.
So APRA have identified the following user roles will be available the new solution. Firstly we have the Principal User. The Principal User will be able to create and manage access for other user types and draft and submit returns. We then have a Secondary User who will be able to draft and upload data into the new solution. However, they cannot submit the return. We have a Service Provider role who will have access to draft, upload and submit returns on behalf of an entity for those of you who use Service Providers to submit data through to APRA and we have a fourth role which is a Corporate Profile User, they will have the ability to edit corporate profile information.
We put these roles in place partly due to the feedback we received last year with some organizations who wish to have those who enter the data to have a secondary check before the data is submitted, hence the use of the Principal and the Secondary User. You can see the roles here define the level of access each user has to draft upload or submit data. There's no limit on the number of users per role, but entities should be aware that granting access to a user enables them to view all submitted data in addition to completing returns. Now we did have a question yesterday on this subject whether or not each entity needs to fill all four roles. The answer to that is no, if you are a smaller entity where you only have either one or two Principal Users, that is all you need to have so you do not have to fill all four of these roles.
Thanks Dan, we will be engaging with you prior to the start of the test environment. We need to collect details of the Principal Users from each of your entities and that'll enable us to provision initial access to the test environment. We also understand that testing may not be completely done by your BAU reporting teams. And so we will reach out to you to validate your Principal Users prior to go live so that you can advise us of any changes - the process for this will communicate to you at a later date. So no action is needed right now to provide us detail.
We’ll now turn to the topic of data submission and validation, which is really at the heart of the new solution as D2A has been in place for a long time, and entities have evolved their own processes to submit data to us. And what we've seen from our engagement with entities, is that there is a wide variety of approaches used. Going forward, manual entry, XBRL and XML will be valid submission methods.
We are keen to take advantage of their new solution to improve reporting and so will no longer accept email, mail or fax as a valid method. Those who currently use these methods will need to get their myGovIDs and start using the new solution for reporting.
As the new solution is a web-based platform copy and paste functionality is only available for single cell values. Entire tables can no longer be copied across now. We understand this may impact some entities more than others, and we do encourage you to take this as an opportunity to enhance your submission processes and look at using other file formats to reduce the manual effort required.
There have been questions around both Microsoft Excel and API submission methods. So I'd like to address both of those. For Excel, we understand that many do prepare data in spreadsheets and some of you then manually copy that into D2A, and to simplify this process, some of you would like to submit the Excel spreadsheet directly to us.
However, following review of this existing collections we have determined that it is not feasible to accept Microsoft Excel files for the existing D2A collections.
As part of ensuring fit for purpose submission methods are used in the future, for data collections, we will consider whether Excel is an appropriate option and on an as-needed basis. As mentioned, and in line with the future of data collection, we do encourage entities to shift from manual to file-based submission methods and we're continuing to continuing to work with a range of Regtechs and software vendors to help facilitate this transition to more automated solution methods.
With regard to API’s as a submission method, additional functionality to allow entities to submit via APIs is planned, but availability of this functionality will be confirmed at a later stage. We are working through the details particularly with the ATO on the rollout of the machine-to-machine credential which is a dependency for the API method.
File extensions in the solution must match the type of file submitted whether it's XML or XBRL. Given the introduction of a secure test environment ahead of go live, entities will be able to practice submission with their chosen file types to ensure they can be accepted in the new solution. Hence we will really encourage you to leverage the test environment to build your own readiness. Natalia in the demonstration will show us some of these aspects as Dan mentioned earlier. There will be a single repository of contacts and accountable persons in the new solution and entities will now be responsible for updating their contact information and adhering to any new executive accountability regime requirements by the new solution. This will allow you to manage and control your own contact information and hopefully making it a little easier to keep your records up to date.
The last change I want to highlight around data submission and validation is APRA’s accepted values. Now in the past, D2A has accepted misspellings synonyms or variations of specific words within XML and XBRL files. But as part of our continued efforts to increase the quality consistency and accuracy of the data that we collect, the new solution will no longer accept words that deviate from APRA's accepted values.
Any values that now fall outside the taxonomy won't pass through the validations in the new solution. So, please ensure that you check in with the accepted values. You'll find those in the mapping files on the “Taxonomy development artefacts” page of APRA’s website.
As an example, on this page in this slide, the first image is showing the accepted value of banking. It's highlighted on this slide and is what you would normally manually select this from a drop down list. This will be the same in the new solution. The second image on the right shows the XML file and this must match the exact APRA value going forward. The new solution will only accept these standard values as highlighted on this slide again, Natalia will pick up on this in the demonstration shortly.
I will now jump over to Dan to take us through resubmission. So with resubmissions the main change here is entities will now be able to request a resubmission, extensions and form exemptions within the solution. Previously, this has been a manual process where you would have had to contact APRA. Resubmission requests made before the return date will be automatically approved and the return will become available for resubmissions immediately. Resubmission requests made after the return date will be assessed by APRA. Now, it's APRA’s intention to migrate up to three years’ worth of entity submitted data to allow for resubmissions. If re-submissions are required, entities will be able to resubmit the forms without needing to re-enter all the data.
Users will still be able to export data from returns into PDF, or download the original file that was uploaded into the solution. For more information on this please refer to the Implementation Plan.
Okay, well now move to preparing for the new solution. Now we've highlighted some of the key changes that you're seeing the new solution. It's important to call out what you can do now to prepare for the transition. Entity readiness really key to the successful implementation of the new solution, and each entity is responsible for managing their own readiness. We've called out four readiness stages, with some specific actions to be completed at each stage. So this should particularly help those that are online who are just starting out in their journey. We're right in the middle of mobilization, the first stage, so that's where we are now and you should be taking some steps to understand and prepare for the transition. Some of the things that you can do is to plan and allocate the resources that you need within your own organizations, complete the D2A form which we will speak to later, and encourage users in your entity to register for myGovID.
And providing additional contacts to us for those in your organization who need to receive communications and further information. We want to make sure the information does land in the right spot so that you can take advantage of that now, and you need to think about provisioning the Principal Users in your organization and being able to being ready to provide those details to APRA when we need it. These activities should be taking place from now right up to the lead-up to the test environment release in quarter one next year. As mentioned more details regarding the revised timelines will be released in October. The other readiness stages testing and familiarization - this is really about accessing the test environment and the availability of the test environment to provide you the opportunity to familiarize yourself with the new solution ahead of go-live.
Pre go-live at this point you should be really on track with your readiness activities and confident in your meeting your go-live requirements.
Some of the things there will be in terms of the training and support and understanding how to get support.
In terms of go live and onwards, that's when all entities will be transitioning from D2A to the new Data Collection Solution. We will continue to monitor entity readiness across the industries and certainly will be working hard to provide the information and the support you need to keep going on your transition journey. I'll now hand over to Natalia to give you a bit of a front row view of your new Data Collection Solution. It's important to note that we are still in early phases of our solution build.
So what we're going to see today might differ slightly from the final solution, but essentially the core processes will stay the same. Now the demonstration is via a taped video, and yesterday we did have some timing issues. So bear with us. We have made some changes overnight, so hopefully this will run quite smoothly. Let's get started.
So what are we covering today? We will cover the following six functionalities: logging in, navigating through the homepage, managing user roles, submissions and validations, viewing submission histories, resubmissions and additional returns. Please note that the screen you're seeing is a recording to minimize any issues with the live demo. However, my walkthrough is live. So please bear with me if there are any lags and delays. So let's get started.
The first step to using the new solution is to log in to the portal, as Jane mentioned the solution is web-based. Therefore you can access the portal through several web browsers that are listed in the Implementation Plan. I'm going to log in as Annette Crouch, who is a fictitious character working for Citigroup who we've selected at random, and we wanted to provide a real example so Citigroup won the draw, and I know we had a few reps from Citigroup who would be joining the session today. So thank you for joining us today. The new solution will use myGovID to authenticate at login, but for the purpose of this demo, we will use a username and password.
So once Anette has logged in, she can select the company she is submitting on behalf on. So if she represented a service provider, she can select the relevant company to submit on behalf of. In this instance, we're going to follow Anette’s journey for Citigroup.
Annette has now successfully logged into the portal on the homepage and is able to see relevant notifications. And in this instance, she has a reminder notification that there's a return available. Entities will receive an automated notification before a return is due on the homepage and via email.
So if we click the notification we can see that we have an economic financial statistics return due on the 15th of August. So if we close that we can explore the rest of the home page, and on the top right screen we have shortcuts to use your account and help features. And on the left hand side is our menu navigation.
As you can see there are several areas Annette is able to navigate through and I'll just flag that there may be some changes to the menu at go live, and for different access for different users. So let's move on to find out how Annette can manage user roles.
Entities will need to assign a Principal User who can delegate access to other users. Annette is a Principal User and this means she'll be able to create and manage other users in her company and has the ability to draft and submit returns.
Other user roles in addition to the Principal User include the Secondary Users, Service Providers and Corporate Profile Users. For more information on user roles refer to the Implementation Plan. So assuming Annette has set up all the users for her company. Let's go through how to submit a return.
In the menu navigation - we select draft return. And from there, we can select the EFS return which is due for completion.
Upon clicking on the return we can see there are various forms with no data. So entities will have the ability to submit data via manual entry or upload via XML or XBRL, replicating the way it is in D2A today. Let's first take a look at manual submissions for Annette, and what you'll need to do is to click edit next to one of the forms.
Annette will be able to manually enter content in each field. Once you click edit. She'll be able to copy and paste into individual cells. However, as this is a web browser.
She will no longer be able to copy large segments of data into the return as in D2A. When keying into each field, you'll need to key in the numbers, as symbols and letters will trigger an input validation warning.
Once we’ve keyed in all the information we’lll scroll down to the bottom and select either validate and save or save as draft.
And for Annette we will save as draft as she would like to return at a later time.
Now that we've input some data we can see the status of the return has changed to in draft.
And next we're going to go through how to submit the data via a file upload.
So Annette will be able to upload a file via XML or XBRL, and for this example, we will demonstrate an XML file upload. We’ll need to select upload data.
And it's important to note that validation rules will be included in the new solution and we we’ll show validations triggered for a file upload that fails because it is the wrong file type a file upload that will fail because it triggers submission level validations. So to upload a file select browse.
So in this scenario Annette has uploaded an incorrect file type and has received an error message because it's a Word document. She will need to upload an XML file with the correct extension. So let's go ahead and do that.
Anette has now uploaded the correct file type and to confirm if the file has passed all validation rules, she can navigate back to the home page and view notifications. For now, I've just gone back to draft returns where we can see the status is valid as it is the correct file type.
Now, let's see what happens if this file has been uploaded but triggers a validation warning when she click submit. So the submission has triggered a warning to explain why the value of assets does not equal the sum of liabilities and Annette will need to provide an explanation by typing in the comments box or uploading a file. For selected validations, entities will need to go back and edit the data, but in this instance, we only need to provide an explanation. So we'll quickly type one in.
And once we finish we can click continue to submit this return to APRA.
So we can see once you click submit that the submission has been accepted and therefore has passed all the relevant validation rules moving along. Let's explore how to access submission history.
So Annette will be able to view past submissions by selecting the submission history in the menu navigation.
And she'll be able to select filter and sort the data as needed as APRA will migrate up to three years of submitted data. For now, there's no data. So let's move on to see how to resubmit a return.
We're not going to demonstrate the entire process today. So to simplify the resubmission for this demo, Annette would click request resubmission next to the relevant return and from this, APRA will be notified of the resubmission and response from APRA would appear in its home page. So, now as a final module, we will go through how to submit an additional return or an ad hoc return.
As a Principal User, Annette will be able to create additional returns. So to do so, we navigate back to the menu and select create return. Entities can submit a return to provide APRA additional information such as audit reports or board meeting minutes. Annette will need to key in the return name select the form set and include an effective date and click create.
Once a return has been created. We will follow the same process used to complete a return and provide additional information.
So here we can select a return type whether it's a request or a submission. And in this case, we're going to select a request and never return extension. We can include additional information such as the return name and the due date.
Once we've done that we can then validate and save and submit the return similar to what I've shared previously and APRA will receive the notification and assess for approval.
So that brings us to the end of this short and quick demo end of Annette’s journey. To summarize, we've covered the six topics below to provide you with a high-level overview of the solution and an indication of the new features and functionalities. We hope you found this demo valuable and will now open the floor to any questions.
So we've got a couple of questions that have come through so far. One of the first questions is can the transcript please be sent to the audience and the answer is yes. We do have a final webinar next week, so once we complete all webinars, we will send out a copy of this recording together with a transcript.
I do note that a couple of people did have some problems being able to see the video. The video is part of the webinar and will be recorded. So you will be able to see the complete demonstration if you missed out on any parts of that today. Thanks Jane. We have a question that's come through on myGovID. So what is myGovID, and will our personal myGovID be used or will we need a different one? myGovID is the Australian government replacement for the old AusKey solution. It is different to the myGov solution. You may already have for ATO or Medicare etc.
Is a different solution and every person who'll be using the new solution will need their own personal myGovID? Great. Thanks. The next question is can one user be in two different user roles. Yeah, I can take that one as well. So yeah, absolutely one user can be in two different roles. Absolutely, and so for large organizations, some of the feedback we had was that different people only had certain rights, but in some small organizations it might be right that you have single or two people who are both Principal Users and Corporate Profile Users for example, so, yes, you don't have to have all the roles and one person can hold more than one role. So you do have the flexibility in the system to work with your own business processes. Perfect.
So this next question similar to this, Jane I might get you to answer this one. Who will APRA reach out to when requesting Principal User information? We will be reaching out to all the entities who will need to be in the new system, so that will include those who are currently using D2A and will probably reach out through another D2A form for example, but for those who aren't using the D2A system we will reach out to you via an alternate mechanism to get that information from you. Thanks Jane/ Another question here. Why can't we continue to use email?
So APRA has made the decision with the new Data Collection Solution to move more towards a single portal for data exchange between APRA and reporting entities. Email submissions that we have accepted in the past actually then requires APRA to take the data and enter it manually into the system and really it's really the responsibility of entities to be ensuring that data has been entered and has been entered correctly. So the decision has been made to move away from the manual submission channels and sure the all entities, the onus on all entities to report their data through to APRA. Thanks Dan. Next question here, when will the D2A form be available for us to provide information on data submission practices as per Implementation Plan guide page 21. Yep. I'll take that one.
So the D2A form is now available for those who are using D2A, and that will be available up until the 30th of August. You will find that in your folder, a form in the ‘DCS Survey Return’ folder in your return list.
Next question on validation rules, can a validation be applied to a draft i.e. before submission? Yes. So as Natalia had demonstrated there are a number of types of validation within the system. So we have the input level validation at the point of when the user enters the information into the number box or the data type validation. Then we also have form level validation and that will be when the user selects the validate and save, and then we also have the submission level validation. So if you did want the rule to be applied you will be selecting the validate and save at the form level and at submission level. Currently, if you're selecting save as draft the processes that you're currently working on the phone, but you're deciding to come back to it later, therefore there will be no validation applied at the save and draft stage.
Importantly there James, there is the ability to validate and save before actually submitting. So an entity can check they can pass the validation rules before submission. Absolutely, yes. Great. Thank you James. Question here on submission history, how do entities access submission history that is beyond three years? So history beyond three years will not be made available in the in the new solution, APRA did a lot of analysis to understand what the level of resubmissions are and concluded that very few resubmissions occur after the three-year period which is why we've gone for the three years of data migration. If entities need or wish to do a resubmission beyond three years, then they should contact APRA where before your history for a period greater than 3 years, then APRA will advise you extract that information from the D2A client before we move to the new solution.
Thanks, Another question here. This is a good opportunity to move away from manual submission who can who can entities contact to find out more about XML and XBRL? Yeah, that's a good question and APRA would agree it is a good opportunity and would encourage entities to look at their practices and processes and maybe move to more automated solutions. At this point in time APRA is not providing a list, though we are working with a number of vendors in this space. But we would encourage you to speak to your peers in your industry also reach out to your industry bodies as they will also be aware of the vendors that are operating in your industry space.
Great. Thanks. I think we just have time for one more question.
A question on the test environment. Will all roles be available in the test environment and will offshore be able to use a test environment? So yes, all roles will be made available in the in the test environment. APRA is not imposing any restrictions on accessing the environment from offshore. However, as we did note earlier at this point in time, the ATO still working through a solution for non-Australian residents who may wish to access the system from offshore. Also, if you have Australian residents offshore that there wouldn't be a problem with obtaining a myGovID either at this point in time. We are still working through the solution for non-Australian residents operating in offshore. Thank you for the questions that have come through, won’t be able to go through all the questions but we will release a copy of this webinar next week together with an updated FAQ and for some of the questions that have come through we will reach out to you directly.
Okay, so we are going to launch a second poll now. At this point, what would like to know now is based on what you've seen and heard to date that's through that's through this webinar and through the documents you've read in advance as well as a demonstration of the new solution. We are really keen to understand the level of change that you anticipate the new Data Collection Solution will bring to your entity. So the question here we have is what level of change do you anticipate the new Data Collection Solution will bring to your entity? Four options to choose from this time. We have significant change, high change, moderate change or low change. So what's the level change you anticipate the new solution will bring? So once again, we'll just give you 30 seconds or so to think about this and put your response in and then we'll come back with the poll response.
We can see a number of responses coming in now, we will just wait just a few more seconds just for those of you who are still considering your answer. Okay, and I think the numbers more or less stopped coming in. So let's close the poll there, please. Okay, and we're going to need responses up on screen. Okay. So again, we've got a response rate across all options, but I see out there in the lead, moderate change, and no change. So Jane, we've got a good number of people saying low and moderate change and a few others were saying, you know high significant change. So you could comment on that.
We are conscious that some change will be brought about by any new solution that you are undertake in, particularly such a large scale transformation as we're doing now. It's important that you know that there will be support available through ongoing communications, availability of the test environment and training materials that would be prepared and provided to you prior to both the test environment and go live. So we will want to reach out to you as much as possible. And for those with the significant change in the high change, I think it's good to note that we are confident that many of the changes that we're making are really positive and will help you help you in terms of your data management processes. Entity readiness really is key to prepare us for the change, so the test environment again familiarizing yourself with that will be really important to make sure that you're all successful but we are here to help and support going through the process.
That's great. Thank you very much. So Jane, I think I'm going to hand back to you as we start to move towards the end of the webinar today. I think you're going to just take us through some next steps. Yes. I'd like to just call out a few next steps and actions that you can take. So here's four things that you can do. Now for those of you are already using D2A, and I'm conscious that many of you online do not use D2A currently so won't need this particular action, but to complete the D2A form that we've put in the DCS survey return folder in your return list, if you could do by the 30th of August. That’s all about collecting some more information on your current practices in D2A, and the forms that you submit to help us to prioritize the functionality and the forms that will be available in the test environment. So that's a great input to us for design decisions.
Please provide some additional contacts, particularly those who are early on their journeys. You might have some new people in your organization that need the information. We want to make sure that it does land in the right place. So please provide us with additional contacts. You can ensure that your users are registering for the myGovID and that will enable us to give them access to both the test environment and the new solution going forward and if you could confirm who your Principal Users might be just internally so that when we need that information, you'll be ready to provide us with that so that we can provision the test environment.
We also are really keen to know how you found the information contained in the updated plan. And indeed with is this webinar today, so please provide some feedback. There is a survey link in the plan itself that you can go to, you could also contact your working group representatives and just to note that on ‘APRA is replacing D2A’ there is contact information and working group representatives in there noted, or you can go to your industry bodies and we're in regular contact with people in your industry bodies as well.
And if you require and would to get further information, then please continue to visit the ‘APRA is replacing D2A’ webpage and also visit the ATO website for more information on myGovID, and we have included the link there on screen which you may wish to jot down if you're not familiar with the solution. You’ll find here all the information you need about the new authentication solution so you're prepared to access APRA’s new Data Collection Solution ahead of the external test environment and go live and please continue to reach out of the project team via the new data collection solution email, which is also an on-screen this point in time. And particularly for some of you who have identified today that you expect a significant or high change with the implementation of the new solution, we would like to hear your views.
So that does bring us towards the conclusion of the webinar today. We do really appreciate you taking the time out to join this call and listening in to ensure you are prepared for the new Data Collection Solution. Thank you again to those of you who submitted questions either in advance or during the webinar session, and we will come back to those individual individuals who sent in questions or feedback that we didn't get a chance to address in this session as mentioned. If you have any additional questions, please reach out to the team, and as I mentioned before the recording of today's webinar will be made available after the session. With that it just leaves me to say thank you, and goodbye.