12 Tips For Moving From An On-Premises To SaaS ITSM Tool (From A Customer)

Forrester recently published “IT Service Management (ITSM) Case Study: Making The Transition From On Premises To SaaS With BMC” which is available to clients here. For non-clients (or hopefully “future clients”) I thought I’d create a blog on the good practices distilled from the discussion with the BMC client.

The situation … does it sound familiar?

The customer had found itself hamstrung by a highly customized on-premises ITSM tool that was: 1) too costly to run; 2) a poor fit to operational and customer requirements; 3) complicated and cumbersome to use; 4) unable to keep pace with the latest service management thinking; and 5) stranded on an out-of-date version because it would cost too much to upgrade.

The solution …

The customer used a honed set of requirements to select BMC Remedyforce from a shortlist of six SaaS ITSM offerings. In their words, they chose BMC Remedyforce because: 1) it was best suited to the agency's existing and future needs; 2) it was built on the salesforce.com platform; 3) its user experience was similar to (but better than that of) the incumbent Service Desk Express; and 4) it was the most cost effective.

Here's what they did:

  • The initial deployment managed requests and tasks from both customers and internal IT.
  • The customer took advantage of subscription-based licensing's ability to flex with demand.
  • They also used BMC Remedyforce in different scenarios: in internally and externally facing call centers and, in addition to traditional IT support, addressing customer support, app development issues, and human resources (HR).
Read more

Microsoft’s European Fine Comes In An Era Of Browser Diversity

Today the European Commission fined Microsoft €561 million ($732 million) for failing to live up to a previous legal agreement. As the New York Times reported it, “the penalty Wednesday stemmed from an antitrust settlement in 2009 that called on Microsoft to give Windows users in Europe a choice of Web browsers, instead of pushing them to Microsoft’s Internet Explorer.” The original agreement stipulated that Microsoft would provide PC users a Browser Choice Screen (BCS) that would easily allow them to choose from a multitude of browsers.

Without commenting on the legalities involved (I’m not a lawyer), I think there are at least two interesting dimensions to this case. First, the transgression itself could have been avoided. Microsoft admitted this itself in a statement issued on July 17, 2012: “Due to a technical error, we missed delivering the BCS software to PCs that came with the service pack 1 update to Windows 7.” The company’s statement went on to say that “while we believed when we filed our most recent compliance report in December 2011 that we were distributing the BCS software to all relevant PCs as required, we learned recently that we’ve missed serving the BCS software to the roughly 28 million PCs running Windows 7 SP1.” Subsequently, today Microsoft took responsibility for the error. Clearly some execution issues around SP1 created a needless violation.

Read more