![Effective IT with middleware solutions . Avoiding black hole projects when replacing IT systems 2009-01-20 Cristiano Sadun Head, solutions&architecture TietoEnator Corporation [email_address]](https://image.slidesharecdn.com/EffectiveITwithmiddlewaresolutionsnewtemplate-123503761015-phpapp02/85/Effective-It-With-Middleware-Solutions-New-Template-1-320.jpg)
![Thank you . First Last name Your title (optional) Legal company name Organisational unit [email_address]](https://image.slidesharecdn.com/EffectiveITwithmiddlewaresolutionsnewtemplate-123503761015-phpapp02/85/Effective-It-With-Middleware-Solutions-New-Template-7-320.jpg)
Effective It With Middleware Solutions (New Template)
- 1. Effective IT with middleware solutions . Avoiding black hole projects when replacing IT systems 2009-01-20 Cristiano Sadun Head, solutions&architecture TietoEnator Corporation [email_address]
- 2. The issue (1) Multiple systems with different technologies tend to increase costs Different competence sets to maintain Slower time to market with new functionality Poor quality perception due to not-integrated systems … Direct replacement is a tempting solution, and usually appear viable One product/one vendor Total integration Illusion of predictability and datelines
- 3. The issue (2) Often, a lose-lose proposition both for customer and vendor Dependencies between systems are harder and subtler than expected Even extensive pre-analysis work cannot map them all Certain mission-critical systems prove very hard to shut down, being central to many value chains which would have be to be disrupted/tested at the same time New product captures 90% of the total requirements, but the remaining 10% is critical and hard to implement Historic data or processes (products, offers, customer setups) tend to be in the 10% The result is often a black-hole project – sucking resources and returning little or nothing.
- 4. A different approach Rather than a big-bang replacement, a gentle phase-out of what can be phased out Existing functions/services are initially kept in the existing systems New functions/services are based on orchestrating middleware with adapters for existing systems The specific interfaces for new functions/services are created and reused as necessary Systems can be phased out in a controlled way Billing CRM Product DB … Middleware Adapter Adapter Adapter
- 5. A different approach An initial middleware setup project, together with a pilot change project with a good business case Followed by a set of smaller platform change projects, each with its own business case The program objective is to end with the minimum amount of backend systems which are necessary
- 6. How does this help? Pros: Systems are phased out incrementally, reducing risk New services can be realized on lower-cost technology larger skill pool Legacy costs remain limited to the 10% which can’t be shut down or moved Cost/benefit analyses are more reliable and small projects can be better prioritized with respect to budgets Much lower time to market for new services Cons: Initial cost for middleware platform Need of governance of middleware services Open source
- 7. Thank you . First Last name Your title (optional) Legal company name Organisational unit [email_address]