Technical Readiness

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.

What is technical readiness?

Technical readiness is about checking to ensure that all the potential risks associated to your existing (legacy) 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?

1. For each legacy system

   1. is this system available externally to TC?

   2. is there an API to interact with the system?

   3. will this system continue to be used or will it be replaced?

   4. are there systems upstream/downstream that rely on this system?

   5. list the technologies associated to the system

   6. will the digital service need to integrate with the legacy system?

   7. will legacy data need to be migrated from one system to another?

Technical readiness workbook

Use the technical readiness workbook to capture answers to 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 requires a technical deep-dive to ensure integration is possible without interfering with existing legacy system features and functions.

System replacement

Legacy systems may need to be replaced. It is necessary to do a complete and thorough analysis of the legacy system to ensure that no features of the the legacy system are overlooked. Users of a legacy should be consulted to get a complete understanding of all the features that are currently being used on the legacy system. All of those features will need to be handled by the new system.

Legacy system as a data source

Legacy systems may store data that is important and necessary for a service to function. It is often necessary in those cases to read data from the legacy system to enable a new service.

 Legacy system is supplied data from a new service

A legacy system can rely on data from another system. If you are replacing a legacy system ensure that other systems that rely on it as a data source can read the required data from the new system.