Why technical readiness?
Technical readiness requires a thorough look at your existing service systems to identify issues that might occur in moving to a digital service. The technical readiness workbook will offer examples of what issues may be involved and options you may consider to solve them.
What is technical readiness?
Technical readiness is about checking to ensure that all the potential risk items associated to your systems are being considered and managed. It starts through awareness. Is your team aware of the issue and do you have understanding of the impacts.
For each legacy system
is this system available external to TC?
is there an api to interact with the system?
will this system continue to be used?
are there system upstream/downstream that rely on this system?
list the technologies associated to the system
will the digital service need to integrate with the legacy system?
Use the technical readiness workbook
Use the technical readiness workbook to capture your preliminary thoughts of key technical readiness topics.
Access the technical readiness workbook here
What types of issues might technical readiness uncover?
Legacy systems integration
Legacy systems may be used to process and do service processing and fulfillment . In order to not interfere or disrupt service processing and fulfillment it may be preferred to have a digital form write content directly to a legacy system upon submission. While this may be possible, this type of integration work would require a technical deep-dive to ensure integration is possible without interfering with existing legacy system features and functions.
Case #2 -
Case #3 -
Add Comment