Remedy platform into BSM booster future management Cloud one step

In 2009 of September, Bowbing, chairman and Global CEO of "BSM", gave us an IT unified management blueprint for how to achieve future cloud computing environments at its China Regional user Conference. Unexpectedly, the BMC is so quick to put the first step of cloud management into practice.

It will grow nearly three times times over the next 5 years, according to a study by IDC, reaching $42 billion trillion by 2012. More importantly, cloud computing spending will grow at a faster rate throughout the forecast period, accounting for 25% of overall IT spending by 2012, which will account for nearly one-third of overall IT spending growth in 2013.

So what role does the BMC's remedy platform play in its BSM closed-loop management? Steve Frankly, "the release of the Remedyit service Management suite becomes the first step in BSM future management of cloud computing environments and becomes a BSM booster." The BSM closed loop includes SRM Service request management, REMEDYITSM, change request because it is likely to be modified, to be installed, this part is automated solution, server automation, network automation, etc. the core of operation is CMS (cmdb+ tools), and it's compliance, Governance and so on. These will be upgraded as part of the cloud environment management in the future. "

What are the advantages and features of an on-demand custom REMEDYITSM suite? Steve that "the BMC's remedy platform version 7.5 has fully supported the ITILV3 standard." It can provide support and service for the management of assets and software, and for change management, release process and so on, even to the stage of self service; the unique flexibility of the REMEDYITSM suite over the SaaS model allows enterprise deployment and implementation to be adjusted as needed, Can let the enterprise in the implementation process obtains a relatively good effect; Remedy can visualize the enterprise to understand best practices, control asset changes; Remedy also supports many tenants, helping many enterprises to achieve a large concentration of the help desk; Remedy generates compliance reports from a lifecycle perspective on the cost, configuration, and it changes of the enterprise's assets. "

ITSM changes need to keep up with business needs

Today's enterprise IT departments are responsible for increasing customer satisfaction and programme availability while effectively reducing costs. However, managing the IT support infrastructure requires investing not only in the system, but also in recruiting, training, and retaining managerial talent. So if these investments can be saved, they can often be used in other business areas and play a greater value.

Also at the IT management level, the evolution of IT management technology has also undergone a variety of changes, from a single network management, the management of a single it component, to system application management and business-oriented service management, enterprises gradually realized that the infrastructure can not only be considered as a specific hardware, but as a service. The same is true of ITSM.

What to consider when migrating to SaaS ITSM

There is also a clear understanding of how to migrate ITSM to SAAS,BMC. The BMC suggests that the enterprise IT department should think about the following issues. For example, does the company have a clear incentive to choose SaaS, and can SaaS meet your needs? What mode do you choose? ITSM when choosing the SaaS delivery model, focus on those aspects and so on.

First, whether the enterprise decides whether to implement ITSM or outsource mode within the enterprise, depending on the type of it, level and cost of the enterprise, the cost comparison of capital budget and Operation Dimension, the possibility of enterprise IT infrastructure expansion, And the degree of customization and integration of other components in the IT infrastructure and management scenarios required by enterprise workflows and processes. When an enterprise considers outsourcing the SaaS model, it should also clarify its various factors. For example, is IT service management ability to have a variety of needs, ITSM unpredictable growth capacity, lack of time, lack of budget, lack of personnel, lack of data security expertise and capacity, etc.

Second, after determining which model to consider, companies should understand the main reasons for choosing SaaS, and these issues are bound to be addressed.

After the enterprise has considered these two aspects, then you need to go back to the first one. Determine the needs of the enterprise for flexible service patterns and find such solutions to be flexible in switching between different modes. As a result, enterprises need to consider not only the flexibility and business protection that SaaS brings, but also the cost of migrating from an enterprise's existing model to SaaS scenarios, especially employee retraining and data migration costs. Therefore, you need to consider the flexibility of transition between different service delivery modes-from presets to hosting, from permanent licensing to short-term licensing, from in-house staff to outsourced staffing.

Finally, you need to understand the main areas that ITSM should focus on when choosing the SaaS delivery Model:

SaaS IT service management solutions should be able to easily and economically integrate with out-of-the-way tools to proactively and automatically find solutions to problems that disrupt critical services. The SaaS IT Service management solution should take full advantage of the current IT asset information stored in the CMDB.

Solutions delivered through SaaS should be able to share data with various applications to authorize, execute, and monitor changes to IT infrastructure. In addition, such scenarios should provide a pre-configured, out-of-the-go, and ITIL compliance capability that includes events, issues, changes, publications, assets, service requests, service levels, and knowledge management processes. Be sure to focus on security issues in the SaaS model and determine different levels of security for different types of data.