We are turning the final corner and can see the homestretch!
This week was filled with hard work and lots of progress.
Member Data and Ticket Delivery Rules
We have successfully replicated 15,000 tickets in the new system with over 99% accuracy. All exceptions have been identified and validated. While we are working on the final small adjustments required, we can say that the ticket creation and notification system is ready for cutover.
Open for Business
The production environment log in portal has been opened up for pre-registration. If you haven't created a user profile yet, see the document attached for the link and instructions.
After further testing, the dev team was able to identify a bug. We are waiting for internal user access to the production environment to test the fix again. We hope that this is the end of the mysterious missing Cancel tickets, but if it is not, we will keep at it until we find the answer.
Daily Summaries / Audits - we will not be able to deliver nightly audits by FTP at cutover, but we will have that available very soon after. In the meantime, audits can be delivered by email. If you need to provide an email address to us, please send it through to firstname.lastname@example.org and we can set you up for a couple of weeks with email copies.
Positive Response - we will continue to test this module until we feel it is ready for release and we have an API for members to upload ticket responses back to the system. Then we will begin the rollout to members, which includes scheduled webinars and documentation. Look for that to start about 2-3 weeks after cutover so we can focus on the post-cutover issues that come with any change this size.
We are finalizing cutover day checklists and will post those and push them out through all communication channels early next week. For now, be aware that the external web links from our current system will be shutdown at 4pm (local time for each province) on January 31. That will allow us to clear any tickets still waiting to be processed prior to switching over to the new system.
We will have a cutover team onsite with Pelican developers and a tech from Amazon Web Services during the cutover process and will remain 'eyes on' for several days as we monitor for any unforeseen technical issues. We have increased our Support staff for the weekend and for the first week or two post-cutover to handle any questions or concerns from members or the public.
That is all for now. We will post another update on Monday evening. Stay tuned.