Deloitte Mainframe Modernisation
Organisations across every industry are struggling to modernise core systems to support current business demands, and deliver against the digital strategy roadmap. Mainframe applications often pose a special challenges that relegates modernisation to the “not yet, we’ll do it later” category. Meanwhile run costs, cost of change, and compliance risks continue to rise.
Our Difference – Overcoming the classic blockers
Deloitte Automated Refactoring addresses the five most common concerns around mainframe migration
- Partial automation means code has to be manually converted, creating a long, risky and costly program
- Business disruption from new User Interfaces (UI) and long freeze period
- Developers can’t transition to new Object-Oriented (OO) Languages languages
- Converted code doesn’t perform as well as mainframe
- Migration to ‘modern’ variant of the same language (COBOL, Natural etc) leaves you locked in to vendor and existing.
Automation – Don’t touch the code
Manual intervention in the conversion of code or data immediately introduces uncertainty around understanding of business rules, integrity and performance of the migrated application. This drives increased risk, time and cost – often to the point of program failure. Uniquely, we have developed tools which achieve fully automated conversion, reducing risk, time and cost.
Refactor then modernise - Avoid the big bang
A classic pitfall in mainframe modernisation programs is to plan to upgrade the application as it is migrated. Whether by redesigning the UI, restructuring the application, or extending the functionality by applying a backlog of enhancements. This ‘over reach’ complicates the program, causing time and cost blowouts. Our approach is to first refactor without changing the functionality, so there is only one variable to manage “does the application still do what it used to do?” We create automated regression test suites during the migration, to prove that the refactored application really does do exactly what the original did.
Then, when the code is up and running, you can start to modernise, prioritising the high value initiatives.
By refactoring in phases, the modernisation of migrated code and data assets can run in parallel with continuing migration off the mainframe. This drives rapid time-to-benefit, as early as within six months, and can be done in-house or by other vendors: there is no lock-in to Deloitte.
Proven lower risk - keyhole surgery versus open heart surgery Incremental. Our technology allows phased migration by application layer or by domain, avoiding big bang risks and realising immediate benefits.
No freeze period. Business is not disrupted; your developers can continue to work in the legacy language and our tools will continuously convert the code in the new Integrated Development Environment (IDE), enabling your existing Developers to gain all the productivity benefits of Continuous Integration, Continuous Testing and Continuous Delivery.
Commercial principles - There are two phases to our delivery.
- Discovery and Diagnostic
- Tool-based diagnostic analysis of current code, data, batch processes, interfaces
- Design of future state solution architectures
- Develop migration sequencing and roadmap
- Estimate ROI of refactoring program
- Typically 6-10 weeks duration.
- Fixed price refactoring & migration program
- Refactoring & data migration
- Interface ‘re wiring’
- Automated regression & non-functional testing
- Developer education in new IDE and CI/CD methods
- Duration typically 6-24 months, fixed price.