BMC Case Studies Multinational Financial Services Corporation

Edit This Case Study Record

	Multinational Financial Services Corporation BMC

Multinational Financial Services Corporation

BMC

Technology Category	Application Infrastructure & Middleware - API Integration & Management Application Infrastructure & Middleware - Middleware, SDKs & Libraries
Applicable Industries	Finance & Insurance
Applicable Functions	Business Operation
Use Cases	Infrastructure Inspection Predictive Maintenance
Services	Software Design & Engineering Services System Integration
Challenge	A major multinational financial services company was undergoing a digital transformation to meet new customer demands for innovative services. However, the company's mainframe was siloed, operating with Waterfall-based processes and antiquated tools, which caused delays in major projects. The mainframe developers were still using 3270 emulators for coding, which lacked the benefits of modern tools. The mainframe team had no automation in place, requiring multiple people and teams to move code from check-in to deploy and from development to production. There was no automated testing in place to handle online and batch testing, and there was a lack of testing frameworks as well as lack of integration with automated testing tools. The mainframe team had too many disparate systems involved in the process, so a developer/release manager would have to jump from one system to the next. With minimal change management integration, tracking changes end to end was a manual task. Read More
About Customer	The customer is a major multinational financial services company. As part of its digital transformation, the company was looking to meet new customer demands for innovative services delivered through digital means. The company's mainframe was a core part of its operations, with 60 percent of processing and 70 percent of data still residing on the mainframe. This made the mainframe crucial to the company's ability to compete against nimble disruptors. However, the company was facing challenges due to the siloed nature of its mainframe, which operated with Waterfall-based processes and antiquated tools. This was causing delays in major projects and was a hindrance to the company's digital transformation efforts. Read More
Solution	To lead their mainframe team into an Agile/DevOps transformation journey, the Director of Engineering implemented Compuware Topaz Workbench, ISPW—migrating 300 application developers from Micro Focus ChangeMan—and Xpediter. These tools integrate with many of the Continuous Integration/Continuous Delivery (CI/CD) tools the financial services company currently has in its mid-range DevOps toolchain, including Jenkins, Atlassian JIRA, XebiaLabs XL Release, ServiceNow and SonarSource SonarQube. These solutions provided the mainframe team with modern capabilities like a modern development environment with a full-featured Eclipse-based IDE, code completion, syntax highlighting, integration with tools, fully orchestrated deployment and testing built into the pipeline, integration with existing test and scanning tools as part of the pipeline, fully automated change management, and integration with Elastic’s ELK Stack for end-to-end metrics. The mainframe team now uses ISPW and Topaz Workbench for all development work. They use XebiaLabs XL Release for pipeline orchestration. Read More Log in to view content
Contents

Technology Category

Application Infrastructure & Middleware - API Integration & Management

Application Infrastructure & Middleware - Middleware, SDKs & Libraries

Applicable Industries

Finance & Insurance

Applicable Functions

Business Operation

Use Cases

Infrastructure Inspection

Predictive Maintenance

Services

Software Design & Engineering Services

System Integration

Challenge

A major multinational financial services company was undergoing a digital transformation to meet new customer demands for innovative services. However, the company's mainframe was siloed, operating with Waterfall-based processes and antiquated tools, which caused delays in major projects. The mainframe developers were still using 3270 emulators for coding, which lacked the benefits of modern tools. The mainframe team had no automation in place, requiring multiple people and teams to move code from check-in to deploy and from development to production. There was no automated testing in place to handle online and batch testing, and there was a lack of testing frameworks as well as lack of integration with automated testing tools. The mainframe team had too many disparate systems involved in the process, so a developer/release manager would have to jump from one system to the next. With minimal change management integration, tracking changes end to end was a manual task.

About Customer

The customer is a major multinational financial services company. As part of its digital transformation, the company was looking to meet new customer demands for innovative services delivered through digital means. The company's mainframe was a core part of its operations, with 60 percent of processing and 70 percent of data still residing on the mainframe. This made the mainframe crucial to the company's ability to compete against nimble disruptors. However, the company was facing challenges due to the siloed nature of its mainframe, which operated with Waterfall-based processes and antiquated tools. This was causing delays in major projects and was a hindrance to the company's digital transformation efforts.

Solution

To lead their mainframe team into an Agile/DevOps transformation journey, the Director of Engineering implemented Compuware Topaz Workbench, ISPW—migrating 300 application developers from Micro Focus ChangeMan—and Xpediter. These tools integrate with many of the Continuous Integration/Continuous Delivery (CI/CD) tools the financial services company currently has in its mid-range DevOps toolchain, including Jenkins, Atlassian JIRA, XebiaLabs XL Release, ServiceNow and SonarSource SonarQube. These solutions provided the mainframe team with modern capabilities like a modern development environment with a full-featured Eclipse-based IDE, code completion, syntax highlighting, integration with tools, fully orchestrated deployment and testing built into the pipeline, integration with existing test and scanning tools as part of the pipeline, fully automated change management, and integration with Elastic’s ELK Stack for end-to-end metrics. The mainframe team now uses ISPW and Topaz Workbench for all development work. They use XebiaLabs XL Release for pipeline orchestration.

Impact #1	The mainframe team now uses ISPW and Topaz Workbench for all development work, providing a boost in productivity.
Impact #2	Almost no application teams use the TSO ISPF “green screen” today.
Impact #3	Through ISPW, they use Xpediter in test levels.

Impact #1

The mainframe team now uses ISPW and Topaz Workbench for all development work, providing a boost in productivity.

Impact #2

Almost no application teams use the TSO ISPF “green screen” today.

Impact #3

Through ISPW, they use Xpediter in test levels.

Benefit #1	Significant engineering efficiencies gained in the mainframe application delivery processes.
Benefit #2	Enhanced agility in the mainframe application delivery processes.
Benefit #3	Removal of the mainframe as a delivery constraint.

Benefit #1

Significant engineering efficiencies gained in the mainframe application delivery processes.

Benefit #2

Enhanced agility in the mainframe application delivery processes.

Benefit #3

Removal of the mainframe as a delivery constraint.

Download PDF Version

Overview

Multinational Financial Services Corporation

Operational Impact

Quantitative Benefit