Depending on the scenario, enterprise architecture projects can be led by different people and groups within an organization. In the first of our three-part series published last week, we discussed a customer case study where enterprise architects drove the need for implementing an EA solution, but this is just one example.
With a powerful enterprise architecture system in place, a variety of groups can lead EA initiatives. For instance, one of our customers is a global financial services company who is one of the largest credit card issuers in the United States. To support its global operations, the organization has 10 different mainframes located throughout the world that are responsible for running the company’s complex business applications.
Recognizing the amount of money and time spent maintaining these mainframes, the IT department decided they needed to consolidate and move the mainframes to a more centralized, lower cost location where they could be better managed. The members of the IT team went through a demanding investigative process to analyze the potential to bring the mainframes back to the U.S. At that time, the mainframe systems were outsourced to another company to be hosted and maintained. After almost four years, the IT team realized that it had not saved any money from this outsourcing initiative.
Realizing the enormous scale of this data and system architecture project and the potential cost savings that the company could achieve, the IT team needed a strong enterprise architecture solution that allowed them to model all of the assets and capabilities of each mainframe in order to better understand the divisions and functions they supported. Using Metastorm ProVision, the team was able to build a portfolio management solution to understand its entire mainframe environment, which includes the hardware, software, applications, communication, support, maintenance and costs.
The first step was to map out the current environment of its mainframes. During this process, the IT team identified close to 500,000 objects in the repository. After the mapping phase the team built out a consolidated model and was able to reduce the number of mainframes from 10 to four. Additionally, the team was also able to consolidate the subsystems (regions) from 30 to less than 10, which considerably lowered redundant messaging. Working with the Metastorm consulting team, the organization has identified two separate data types within the consolidated mainframes, the customer and the supplier. They have also been able to understand and define specific objects. With the unique data linking supported by Metastorm, if an application is moved the team will know what databases, queue requests, transactions, subsystems, data, file transfers, batch jobs, and software that will be affected.
In this particular example, the IT team led the effort to embark on a full-scale enterprise architecture project. Based on the initial estimates, the company expects to see an estimated $40-100 million savings in the first fully operational year.
Tune in next week as we examine another business case where a totally different group within the organization decided to undertake an EA initiative.
- Who Drives an Enterprise Architecture Initiative? Who drives an enterprise architecture initiative? Does it come from…
- Enterprise Architecture still delivers in recessionary times Enterprise Architecture (EA) increasingly covers a broader role in an…
- The Road Ahead for Enterprise & Business Architecture With a new year upon us it’s always exciting to…
Related posts brought to you by Yet Another Related Posts Plugin.