Running head: Assignment 2 build your business case
Assignment 2 build your business case
Assignment 2 : Build your business case
Spring 2019 : Cloud Computing
Professor Boyd Gafford, Ottawa University, Ottawa Kansas
ACME Cloud Services is offering several cloud service options to Macquarie Bank based on their specific requirements that were discussed in Phase 0.
MACQUARIE BANK: Profile Overview
Industry: Financial services
Headquarters: Sydney, Australia
Company size: 13",800 (Macquarie Group employees)
Macquarie is a global financial services provider headquarted in Australia with offices in 28 countries. Macquarie’s Banking and Financial Services Group (BFS) comprises Macquarie’s retail banking and financial services business, providing a diverse range of personal banking, wealth management, and business banking products and services. To develop its new digital banking offering, Macquarie looked beyond the financial services industry to the digital companies leading in customer experience.
· More agile digital banking experience for customers
· Enhance inhouse developed applications and microservices existing in production.
· A highly secure, resilient platform to increase productivity
· Roll out cost benefits and faster ROI
(https://www.redhat.com/en/success-stories/macquarie#, p. 1)
ACME Cloud Business Case
Based on the high-level requirements obtained from the client, ACME provides a strategic business model for considering our many services, based on a WBS (Work Breakdown structure) framework.
Planning checklist (Kearns)
As per our Phase 0 discussions, we projected the cost for Computing vs Storage for MACQUARIE Bank, excluding any staffing, architecture and implementation costs. This projection was done on a general basis without considering any specific cloud deployment model at this point. Figure below. (KPMG)
Key elements (Mcdonald):
Educate the Team
· Hold enterprise level seminar on what ACME cloud can do for existing traditional IT businesses and How we have transformed our various customers. We project a sample transformation curve model for MACQUARIE with or industry knowledge and expertise on their domain.
· We emphasize on how we pilot the change and support further on to stabilize any migration related queries and concerns.
· We can propose different models and different implementations of each model tailored to their competencies.
For their IT team we discuss the following areas first and then build on it iteratively.
· Need a Global Namespace for Data Collection
· File Handle URL + Unique object ID globally
· Configure a deployment model based on client’s preferences
· Need support for rich metadata associated with the data
· Plus metadata query and index based search
· Need HTTP access—browser support
· Data services need to be transparent to the user but extensible and powerful
· Driven by Metadata
· Support for large objects, many objects
· Support for active preservation objects
· Driven by preservation metadata
· Compatibility evaluation of their existing Enterprise level applications (middleware, webservices, servlets etc.)- ACME mostly uses .NET framework
Based on our flavors of implementation models we compare and contrast the total cost of ownership for each model type. One such plan is shared above in this document.
Legal considerations (Mcdonald):
· Transborder data flow
· May generate legal obligations in multiple jurisdictions
· The Right to be Forgotten- many jurisdictions have such laws
· Exporting data may be illegal
· EU Data Protection Directive: does NOT permit transferring personal information to countries that do not provide EU protection levels; The US is one such country
· Expectation of Reasonable security
· Security breaches leading to potential liability
· Only as strong as weakest link
· Electronic evidence and e-recovery
· What constitutes evidence?
· Multiple copies, digital signature, data fragmentation
· Retrieval of data often complicated
· Existing non-cloud contracts insufficient
· License agreement vs service agreement
· Ownership vs use of content
· Mobile devices
· The law applies where you are and where your data is stored
· Hiring skilled personnel for driving the migration and change
· Training employees/staff on change in databases, provisioning, deployment lifecycles ad troubleshooting
· Support from third party vendors
· Maintaining unexpired certificates, licenses and agreements
· Risk assessment and disaster recovery plan with rollback strategy
Use cases (Mcdonald):
· Elastic demand for web based media ( video, eBooks, audio)
· Backup to the cloud
· Restore, recovery, “seed” the backup with hard drive
· Sync of files to the cloud and multiple devices
· Internet drive secondary storage
· Archive/presentation in the cloud
· Including compliance, retention and eDiscovery
· Storage for cloud computing
· Support for legacy storage interfaces key
· Self service storage administration
· Application data
· Business critical applications and supporting applications require temporary and permanent data with various statuses and lifestyles
· Build your own cloud
· Client offers their own email (instant messaging etc) services to their employees
· Enterprise “dropbox” implementations
· Application data implementation
· Develop or acquire a dropbox client for supported devices (iDevice, Android etc)
· Connect back to the mothership (internal enterprise storage) with a standard protocol
· Implement data retention and expiration policies on data
· Create exit plan based on the type of cloud model the client chooses.
Kearns, D. K. (n.d.). pr-17-4029-planning-management-methods-migration-to-cloud-environment.
KPMG, C. a. (n.d.). cloud economics business case.
Mcdonald, A. (n.d.). Building the use cases for the cloud.
redhatmacquarie. (n.d.). https://www.redhat.com/en/success-stories/macquarie#. Retrieved from redhat.