Displaying items by tag: cloudnative

Originally developed by Denmark-based KMD in 2001 as a mainframe software application, the e-Boks system became more difficult and costly to maintain over time. The original platform also lacked the agility to expand to additional countries at scale and was not agile enough to expeditiously react to business changes. TSRI and KMD were able to modernize the e-Boks application from its original IBM PL/1 legacy code in a monolithic architecture to a modern, multi-tier application in a modern computing environment, running .NET, with no impact on the business and end-user experience. As a result, e-Boks has the potential to save more than 50-60 percent per year in operations and maintenance costs.

Customer: KMD and The Government of Denmark Source & Target Language: PL/1 & JCL to C# Lines of Code: 974,201 (781,893 - PL/1 and 192,308 - JCL) Duration:  6 Months Services: Transformation Blueprint®, Automated Code Transformation, Automated Refactoring, Integration and Testing Support

Deutsche Bank's relatively reliable mainframe infrastructure utilized COBOL and JCL languages running DB2 and VSAM flat-file databases for a variety of their key financial applications. The company’s leadership knew they would need to be cloud-enabled with a modern architecture to stay relevant for its customers and ongoing market needs. Following a successful proof of concept against other well-known industry soluitons, TSRI emerged as the best solution (highest quality output and most advanced architecture) for the full modernization effort of Deutsche Bank’s internal KreditManager application. An application which gives the company’s employees all of the tools they need to handle all of the company’s loan, credit and mortgage applications.

Customer: Deutsche Bank Source & Target Language: COBOL & JCL to Java & Python Lines of Code: 397,222 (383,358 - COBOL, 13,864 - JCL) Duration:  12 Months Services: Automated Code Transformation, Automated Refactoring, Integration and Testing Support, SonarQube Quality Refactoring, Code-Specific Adaptation, Database Migration, Transformation Blueprint®, Application "As-Is" Blueprint®

This case study documents technologies, processes, and methods of the timely and 100% automated conversion of a portion of the VHA (Veterans Health Administration) Information Systems and Technology Architecture (VistA) system, written in 2.1 million lines of MUMPS. The modernized module resulted in object-oriented and highly maintainable Java compatible with the J2EE framework. VistA is the core Electronic Healthcare Recordkeeping (EHR) system for the VHA hospital system, which provides EHR record keeping for more than 4.5 million veterans.

Customer: Veterans Health Administration and SAIC Source & Target Language: Mumps to Java Lines of Code: 300,000 Duration:  5 Months Services: Automated Code Transformation, Automated Refactoring, Integration and Testing Support, Engineering Support, Transformation Blueprint®, Application "As-Is" Blueprint®

Using money from the Technology Modernization Fund (TMF) under the Modernizing Government Technology Act disbursed by the General Services Administration (GSA) of the U.S. government, the Department of Housing and Urban Development (HUD) sought to modernize several of its remaining critical systems on a legacy Unisys mainframe written in COBOL with a flat-file DMS-II database.

Customer: Department of Housing and Urban Development and Salient CRGT Source & Target Language: Unisys COBOL to Java Lines of Code: 1.3 Million Duration:  8 Months Services: Automated Code Transformation, Automated Refactoring, Integration and Testing Support, Enginerring Support, Software Maintenance Agreement, Transformation Blueprint®, Application "As-Is" Blueprint®,

No change in business logic.
Reduction in overhead costs. 
Continuous development during and after migration.

These are a few modernization concepts that Scott Pickett, TSRI’s Vice President of Product Operations and Service Delivery, discussed on his recent appearance on Amazon Web Services’ APN TV channel. 

“TSRI allows for an ability to do automated transformation of not only your language, but your application to the cloud environment, allowing you to bring in skilled, modern technology to your legacy implementations, being able to drive down the cost point associated with ongoing operational costs, and being able to deliver new applications, new functionality, new screens, and new capabilities in that modern language,” he said in his talk. 

So what does that mean, exactly? 

In TSRI’s modernization of a major European bank to the cloud, that meant they modernized approximately 80,000 lines of code at 99.7% automation. In other words, only 384 of those lines of code were hand-written. That's big for a project of this size—but it's huge when you're talking about applications with hundreds of thousands or even millions of lines of code!

For any organization, whether in commercial enterprise organizations like the banking client mentioned above, or in government agencies, modernization reduces risk. 

“You're able to bring a new skill set, new experts that know Java and know CI and CD tools and apply them to your legacy application that's been modernized,” Scott said. “It literally also allows for the ability to drop tens of thousands, and even hundreds of thousands of dollars, off your monthly costs.” 

As Scott also noted in his presentation, “we can not only transform code quickly…because there are very, very few manual changes, but it also means that you can migrate to the cloud and then be able to not have any business logic change associated with that migration.” 

Maintaining business logic is a big deal when it comes to systems that measure their age in decades rather than years and the original programmers have long since moved on. 

One other interesting point Scott brought up is how TSRI’s tools have enabled customers to maintain agility and competitive advantage by providing its clients with the modern, cloud-based applications they need—all while reaching back to its legacy DB2 database that supports the applications that have yet to be modernized. 

Throughout the talk, Scott also pointed to how TSRI has adopted a step-wise model, which modernizes small applications or pieces of an application, tests for validity, then pushes into production before the next applications are transformed. Such a methodology allows the client to continue to develop in the legacy language, maintain a common data set, and minimizes business disruption to almost zero. 

“There’s no big delay. You can continue developing the legacy and we can migrate those legacy applications while the transformations are happening and migrate them into your modern environment,” he said. 

Scott also explains the steps of an automated migration in layman’s terms and how a TSRI transformation integrates cleanly into cloud services like AWS using containerization and microservices. 

We of course don’t want to spoil the presentation by giving everything away, so head over to APN TV and watch for yourself to learn about how automated modernization to the cloud will save your organization time, money, and the headaches from continuing to maintain legacy systems.