How quickly is Return on Investment (ROI) for a migration project realised?
Assuming a two-year migration project, we estimate that clients who remain on the mainframe will obtain their ROI within the first year, whereas those who re-platform during the migration will realise their ROI in the second year of completion.
This analysis has been based on a range of real-life assignments and assumptions. We are happy to discuss these assumptions or apply a more specific analysis to a client’s site.
How does CA Gen migration with Jumar impact the total cost of ownership?
Based on the assumptions above, we estimate the ROI over 10 years is at least 160% for a migration and re-platforming project and in excess of 350% for a migration alone.
What target languages are supported in a migration project?
Java, Angular JS, C#, .Net, COBOL, SQL-Server, Oracle, IMS-DC/CICS and DB2.
What are the advantages of automated versus manual migration?
Automation significantly accelerates large scale programmes of work. Based on work we have carried out worldwide, we estimate that automated migration is 6 times faster and 5 times cheaper than the manual equivalent. However, the saving over manual development (in isolation) far exceeds these figures.
How much of the migration is typically automated?
Jumar MAPS aims to automate the entire conversion. This is, however, dependent on the nature of the target environment and the content of the CA Gen models.
For server-side and batch functionality we will normally achieve 100% automated conversion. For client-side functionality we would aim to achieve 90%+, depending on any non-standard CA Gen functionality and the scope of the new User Interface.
How maintainable is the migrated code?
The migrated code is created in a structured format, tailored to the client’s needs using templates. Code migrated by Jumar has achieved an overall SQALE rating of ‘A’ (the highest category) for software quality including maintainability.
Jumar ensures that the rewritten (migrated) code is hand-maintainable and can continue to be developed and supported using industry standard development environments. This can be demonstrated using a test model or a subset of your own model under NDA.
Any comments or descriptions that are currently within the CA Gen model are included at the relevant points within the converted code. This can include the original CA Gen logic statements so that the transition for ex-CA Gen developers is easier. This feature allows developers to trace back from any point in the native code to the equivalent logic within the original CA Gen application, useful when doing a proof of concept. This can easily be switched on or off.
Additional descriptions and comments can also be quickly added to the original CA Gen model, which can then in turn be added to the newly generated code – an effective way to increase the documentation within the generated code.
Will converted code have dependencies on CA Gen?
The converted code will have no dependence on the CA Gen runtime nor any Jumar proprietary software.
Jumar takes great care not to create any dependencies on any other vendor proprietary run-times, apart from the those needed when supporting standard hand-crafted COBOL, Java or C#/.NET code. For example, Java generated code can be maintained with industry standard IDEs.
What level of internal resourcing is needed to support a migration?
Automation allows your staff to focus on solution definition, QA and regression testing where real business value can be delivered. It also frees up time to train staff in the target environment where necessary.
The transition is typically phased into work packages, with each requiring a different level of input:
- Analysis of CA Gen portfolio, supported by automation – Typically a workshop with your architects and/or CA Gen specialists
- Target environment design following conversion – Collaborative workshops with your architects and designers
- Optional customisation – A short process where Jumar adjusts the tooling to meet specific requirements such as in-house coding standards
- Migration including unit test and quality check – Little to no client input
- Further testing – Your test and deployment team takes the lead here with support from Jumar
Is ongoing licensing for the automation software required?
No. Jumar’s proprietary software is only used during the modernisation/ migration process and is included in the overall price quoted. It does not require Jumar or other proprietary run-time elements.
The code generated for a new migrated application can be maintained using standard development and support tools by anyone with knowledge of the target platform (i.e. COBOL, C#/.NET, Java, Angular JS programmers).
Has this process been proven?
Yes. Jumar has carried out CA Gen modernisation and migration projects in the UK, Continental Europe, North and South America, the Middle East, Asia Pacific and Australia. These projects have already shown a demonstrable reduction in cost and time, compared to a manual equivalent. A selection of case-studies can be found here, alternatively, we can introduce you to our current clients.
Can you demonstrate your automated migration tools?
Jumar is happy to demonstrate its automated migration tools either by using a test model, or a subset of your own CA Gen model (under a non-disclosure agreement or contract of confidentiality).
Demonstrations of this type can first be used to show an application running with its CA Gen dependencies, then (following automated migration) as a standalone application with no such dependency. This demonstrates its ability to run without CA Gen and gives confidence that functional equivalence is possible.
Such demonstrations can also be used to show side-by-side comparisons of the hand-maintainable migrated code and the original CA Gen generated code, which is not designed to be maintainable.
Comparative demonstrations show Immediately noticeable differences such as a new code structure designed for maintainability and meaningful, user-friendly, names instead of long strings of letters and numbers found in CA Gen generated code.
Additionally, a glance at the migrated code shows no references to run-time statements (CA Gen dependencies) as our tooling not only generates the replacement application code but also code to replace run-times.
