This article is a continuation of my earlier analysis (Part 1 here) where I waded into State Street’s strategy for Technology Infrastructure and IT Capability and Staffing. In this second part of my three part series I will broach the company’s strategy for information risk and security, stakeholder requirements and project return on investment. State Street’s cloud implementation and virtualization initiative is a good example of business strategy/need influencing the firm’s information technology strategy.
State Street: Strategy for Information Risk & Security:
State Street has acquired a substantial client base and houses sensitive financial data that is subjected to regulatory scrutiny. Given the sensitive nature of its data and operations, the cloud infrastructure that the bank chose to implement was that of a virtualized private cloud. Former Chief Innovation Officer Madge Meyer stated, “We’re totally virtualized, our network is a virtual private IP network. Our servers are 72 percent virtualized and our storage is all virtualized for structured/unstructured data” (Burger, 2011). For State Street, a private cloud offers the benefits of a public cloud with the added benefit of being owned and operated by the bank (i.e. exclusive dedication). While no architecture is 100% secure, the risk of an information breach is mitigated as the controlling organization’s data can be completely isolated from the data of another organization.
Additionally, the cloud implementation and virtualization initiative gave rise to shared services that are centrally managed but enforced across the enterprise. This single security framework can be applied across all of the application touch points precluding the need for multiple security frameworks across disparate systems.
State Street: Strategy for Stakeholder Requirements, Testing & Training/Support:
The architecture group within State Street works together with the business to tie together strategic objectives. The idea to embrace cloud implementation (and the additional data functionality it enabled for the bank’s clients) emanated in the architecture group. Thus, the business and the board of directors were key stakeholders in the initiative. The board of directors has a special dedicated technology committee that receives “a complete rundown of the technology strategy and the work that we (IT group) are doing in terms of digitizing the business” (High, 2016). According to Perretta, “They (architecture group) created a proof of concept with an eye toward: Here are the capabilities that our entire organization is going to need, here are the technologies that we can deploy, and here’s how to make them operational” (Camhi, 2014).
State Street started migrating its new cloud applications to production by selecting those with low volume and low complexity and then gradually ramped up to migrating the more complex applications (McKendrick, 2013). Dual pilots of the cloud architecture were conducted using roughly 100 machines. Once favorable results were achieved, a larger pilot consisting of 500 machines was stood up. Approximately 120 use cases were tested in the pilot in order to let the development team understand the failure points of the system (Tucci, 2011a).
The standardization and virtualization aspects of the cloud infrastructure the bank implemented was conducive to agile development. Virtual machines on the cloud allowed development teams to spin up multiple server instances as opposed to physically installing a new box in the legacy non-virtualized environment. Contention between teams waiting for server use is virtually eliminated. “When adding cloud computing to agile development, builds are faster and less painful, which encourages experimentation” (Kannan, 2012). The relative ease at which development and testing servers can be instantiated promotes “spur of the moment” experimental builds that could yield additional innovative features and capabilities.
State Street: Project ROI and Key Success Measures:
Prior to State Street’s cloud infrastructure upgrade initiatives, potential operating cost savings were projected to be $575 million to $625 million by the end of 2014; which State Street is on track to achieve. “The bank had pretax run-rate expense savings from the initiative of $86 million in 2011, $112 million in 2012, and $220 million in 2013” (Camhi, 2014).
When the IT group makes a budget request for substantial investments, they must lay out the potential benefits to the business. Some of the benefits are timely payback, regulatory compliance, data quality improvement and faster development cycle times (providing features and functionality with re-use and less coding). The ultimate aim is to connect the IT strategy to business results in a way that yields advantage for the organization.
In 2011, State Street published a matrix on the advantages of cloud computing vs. traditional IT. The following figure provides insight into State Street’s IT and business unit considerations with respect to making an investment in a fixed or variable cost infrastructure (Pryor, 2011).
|Traditional IT||Cloud Computing|
|Cash Flow||Hardware / software purchased upfront||Costs incurred on a pay-as-you-go basis|
|Risk||Entire risk taken upfront with uncertain return||Financial risk is taken incrementally and matched to return|
|Income Statement Impact||Maintenance and depreciated capital expense||Maintenance costs only|
|Balance Sheet Impact||Hardware / software carried as a long-term asset||Cost incurred on a pay-as-you-go basis|
From a funding perspective, State Street employs the chargeback funding method for its private cloud initiative. Architectural capabilities empower end-users to automatically provision virtualized servers for usage. There are policies in place that determine how long a virtual server may remain instantiated and how much load balancing is performed across the infrastructure. Server usage is monitored, measured and chargeback is calculated based upon end-user processing time. Subsequently, the usage is billed back to the end-user’s respective business unit. “In short, it puts a management layer of software over the virtualized servers and operates them in a highly automated, low touch, fashion” (Babcock, 2011).
Don’t miss part 3 of the analysis:
More Than You Want to Know About State Street Bank’s Technology Strategy Part 3
Babcock, C. (November 9, 2011). 6 big questions for private cloud projects. Information Week. Retrieved from Factiva.
Burger, K. (October, 1, 2011). Riding The Innovation Wave; Technology innovation has been key to State Street Corp.’s success, according to chief innovation officer Madge Meyer — and she’s been willing to take some risks to prove it. Bank Systems + Technology. Retrieved from Factiva
Camhi, J. (2014). Chris Perretta Builds Non-Stop Change Into State Street’s DNA. Bank Systems & technology. Retrieved from http://www.banktech.com/infrastructure/chris-perretta-builds-non-stop-change-into-state-streets-dna/d/d-id/1317880
High, P. (February 8, 2016). State Street Emphasizes Importance Of Data Analytics And Digital Innovation In New Role. Retrieved from http://www.forbes.com/sites/peterhigh/2016/02/08/state-street-emphasizes-importance-of-data-analytics-and-digital-innovation-in-new-role/#a211b1320481
Kannan, N. (August 20, 2012). 6 Ways the Cloud Enhances Agile Software Development. CIO. Retrieved from http://www.cio.com/article/2393022/enterprise-architecture/6-ways-the-cloud-enhances-agile-software-development.html
McKendrick, J. (January 7, 2013). State Street’s Transformation Unfolds, Driven by Cloud Computing. Forbes. Retrieved from http://www.forbes.com/sites/joemckendrick/2013/01/07/state-streets-transformation-unfolds-driven-by-cloud-computing/#408e1acf64cf
Tucci. L. (July, 2011a). In search of speed, State Street’s CIO builds a private cloud. Retrieved from http://searchcio.techtarget.com/podcast/In-search-of-speed-State-Streets-CIO-builds-a-private-cloud