If the ITSM champion doesn’t get involved, the cloud mgmt team will set up their own IT service catalog, CMDB, change, etc and will eventually phase out their role. It is in their best interest to get involved because they already have the solution stack for cloud, CMDB, Sercice catalog that the company needs in cloud. If they sit idly by – they will be replaced or they will cost their company money or, even worse, the cloud team will forget to include those in their deployment and they will have a failed cloud.
The benefits of cloud computing are now well understood and have been proven in the market. Automated, self-service provisioning of on demand, scalable IT resources that cloud computing enables is driving increased IT efficiency, making the business more agile and delivering cost savings in many ways. But, what has also been recognized is that cloud computing is not easy to do right. There have been a lot of false starts in enterprise cloud computing.
So, what’s the difference between bad clouds & good clouds and how can you achieve a good cloud that delivers all the promised benefits to your company and your users?
It really comes down to these key factors:
Governance Compliance ITIL process integration Audit Trails
Cloud is a new way of consuming IT. Automated request & provisioning of IT resources through a self-service interface – it’s still quite scary for some. We see most of our customers have some fear of trusting their data and IT services to the cloud. Customers experience pain here. There are concerns about: Governance Compliance Secure Multi-tenancy Patching Will I have visibility into my services in the cloud? Will I be able to manage server sprawl & drift?
How can IT manage these concerns and deliver a cloud that the business has confidence in?
Screen shot of service catalog. CLM architecture leverages Remedy SRM. Leverages the SRM – if the customer already has a service catalog deployed. Askfor a blackberry or office supplies. Our architecture allows you to plug into that catalog and provide cloud services from that same catalog – VMs, apps, physical servers, databases. Get more ROI from SRM investment. The catalog can become one in the architecture. Avoids them setting up a separate service catalog. Wasted money & time.
Remedy customers get more value out of what they’ve already deployed. Most orgs have separate teams to run the Remdy environment and build the cloud mgmt platform. The cloud mgmt team needs a lot of the work that the Remedy team has already done. Better ROI for Remedy customers. Governance Compliance Audit trail ITIL process
Cloud Goals Improve IT customer satisfaction Reduce the time it takes to provision resources Run 80% of applications in the cloud environment Standardization and global data center consolidaton Ensure existing ITSM governance processes applied to cloud computing Key Use Cases Provide a menu of service offerings to end-users in a service catalog Manage the entire private cloud infrastructure from a single point of control (server, storage, network) Phased expansion to hybrid cloud Implementation Highlights Reduce server deployment from 47 days to 1 week (time required for internal approvals) Run 80% of applications in cloud environment within 2 years
Refer to the VAW flyer for more info!
Value Acceleration Workshop highlights • Exploration of the benefits and requirements of trusted cloud management • Review of cloud strategy and required cloud use cases • Overview of BMC Cloud Lifecycle Management architecture and key capabilities • Technical deep dive into the BMC Cloud Lifecycle Management native Remedy ITSM integration • Identification of next steps to establish trusted cloud management for your business