So you’ve managed to reduce your IT budget focused on KTLO (Keep-the-lights-on) by automating a lot of the manual-intensive integration processes using the latest data integration platform.
In doing this, you lowered your upfront TCO through ease-of-use, prebuilt connectivity, reusable logic and rules, and are benefiting from lower ongoing costs through scalability and performance, ease of administration and seamless upgrades.
You found the required staff to manage the myriad of integration challenges all across your IT shop by tapping into the large community of Informatica specialists available and implemented an ICC to mirror companies like T. Rowe Price, HP and Avaya who achieved significant savings through their ICC’s. (This might have come about from your conversation with Gartner whose research on ICC’s convinced you that you could achieve 25% reuse of integration components; 30% savings in integration development time and costs and 20% savings in maintenance costs).
By the way, have you tried the ICC calculator using this data to show how much you could save?
OK, so you did all that and you have a more efficient IT shop with savings enough to rollout that single critical application that you’ve been asked to complete for the last 6 months. Now what?
There are three fundamental issues you face:
- How to migrate the data you need from the old system to the new and ensure you only migrate useful, correct, valid data that the business wants
- How to test that the system is configured correctly and is working before you have a failed migration on your hands
- How to ensure that your application doesn’t balloon over time causing you to have to buy more and more primary storage, more and more database licences and more and more powerful processors to keep the system running efficiently.
The answer of course is to continue using the data integration platform that you have already invested in (or, if you haven’t … invest in the components you need for these three tasks and then redeploy the same technology across other parts of your IT environment to reap the benefits I mentioned above).
Firstly .. you need to correctly define the data that is important to migrate and move it from the legacy application to the new application. Our data integration platform does that through the data quality and data migration components. We declaratively identify the old data structures and do the same for the new enabling you to quickly build mappings into the new system (which incidentally can then be used on an ongoing basis because you’re bound to want to move data into and out of the new system very quickly!).
Secondly you use the Data Subset component from Applimation to test and configure the applications.
Thirdly, once you have the application fully up and running, you use the Data Archive component from Applimation to move inactive data securely from the new application into a secured archive thereby maintaining the mission critical application at a steady state of storage, database licences and performance.
I’ve outlined above a real-case example where the Informatica Data Integration platform is working together with the solutions from our recent acquisition (Applimation) to help drive down costs and deliver greater value to the business.
We are very proud of how we help companies do this.