Wissam Raffoul
Dr. Wissam Raffoul is an IBRS advisor who specialises in transforming IT groups into service organisations, with particular expertise in IT Service Management (ITSM), process optimisation, outsourcing and cloud strategies, enterprise systems management solutions and business-centric IT strategies. Prior to joining IBRS in August 2013, he was General Manager strategic consulting in Dimension Data advising clients on applying technology to improve business performance. Prior to joining Dimension Data, he was a Vice President in Gartner /META Group and issued various research publications covering service delivery processes, centre-of-excellence models, managing outsourcing vendors, benchmarks, maturity models, IT procurement evolution and supply/demand models. In previous positions, he headed HP ITSM consulting Practice in Australia. He also acted as an infrastructure manager, reporting to the CIO at a number of large organisations in government and in the financial and petrochemical industries.
Conclusion: Artificial intelligence technologies are available in various places such as robotic process automation (RPA), virtual agents and analytics. The purpose of this paper is to provide an AI maturity model in the analytics space. The proposed maturity model can be applied to any type of industry. It provides a roadmap to help improve business performance in the following areas:
- Running the business (RTB): Provide executives with sufficient information to make informed decisions about running the business and staying competitive.
- Growing the business (GTB): Provides information about growing the business in various geographies without changing the current services and products.
- Transforming the business (TTB): Provides information to develop and release new products and services ahead of competitors.
- Workplace Innovation
-
03 December 2018
Conclusion: IT organisations wishing to create value should initiate selling processes to define business needs, establish SLAs for mission-critical systems and provide IT solutions to key business issues. This will result in boosting IT staff confidence and managing business lines’ expectations more effectively.
- As a Service
-
03 November 2018
Conclusion: IT organisations wishing to create value are challenged by long implementation time-scales and inability to change the business perception of IT capability. To address these challenges, IT organisations should adopt an accelerated approach by deploying key processes within a six-month period, to demonstrate service quality and commitment to meet business needs in a rational fashion. Failure to do so will brand IT as a support function, and will make IT desire to earn strategic partner status virtually unachievable.
- As a Service
-
05 October 2018
Conclusion: IT organisations revisiting their service contracts as a result of mergers and acquisitions should establish a federated vendor management arrangement. The rationale is to ensure central consistency while retaining local autonomy to address tactical matters. For example, the central consistency demands leveraging the economy of scale to reduce cost, whilst the local autonomy allows the extension of services scope to cover local requirements without the need to change the local vendor management arrangements. However, the local autonomy should be governed by verifiable policies.
- As a Service
-
05 September 2018
Conclusion: During the last two decades, service desks delivery had the following shortcomings:
- The service desk voice communication channel was characterised by a long waiting time to connect with service desk staff.
- Service desk staff with limited skills minimised the number of issues resolved at the first point of contact.
- There was a lack of online channels and limited self-service offerings, e.g. password reset.
- The service charges were based on the number of incidents that discouraged providers to reduce the number of incidents.
To address these shortcomings, IT organisations should transform to Service Desk-as-a-Service. It should be powered by self-service virtual agents that can identify most of the solutions without the need to connect with service desk officers. The charges should be based on the number of users instead of outages to encourage providers to address outages’ root causes. Online services covering reporting on issues and following up progress should be favoured over voice communication.
- As a Service
-
02 August 2018
Conclusion: Given that multi-Cloud is a combination of public/private Cloud and customised systems governed by in-house and/or outsourced arrangements, end-to-end service level management becomes a critical success factor. IT organisations should implement a complete set of service level practices covering people, processes and systems that allow IT organisations to efficiently deliver services in accordance with service level agreements (SLAs).
The SLAs should span across the full service lifecycle. Service level foundation requires defining the:
- services provided
- metrics associated with these services
- acceptable and unacceptable service levels
- liabilities on the part of the service providers and the buyer, and
- actions to be taken in specific circumstances.
- As a Service
-
02 August 2018
Conclusion: Penalties and incentives are designed to ensure agreed critical service levels are achieved. Penalties are enforced whenever service levels are not met. Incentives are rewarded whenever agreed service levels are exceeded. However, there are cases whereby providers prefer to pay the penalty instead of improving the service level. For example, it is easier to pay a penalty of $10,000 instead of fixing a service issue that might cost $50,000. The purpose of this note is to prevent such situations from occurring and maintain the focus on meeting the service level in all circumstances.
- As a Service
-
05 July 2018
Conclusion: Traditional outsourcing and managed service contracts primarily focus on incident management service levels and give little attention to problem management. For example, incident management service level might be 95 per cent of Severity 2 outages resolved within four hours. In general, a temporary fix is sufficient to meet the incident management service levels. However, this might not prevent the outage from reoccurring because the outage root cause was not addressed. To address this issue, problem management root cause analysis must be used. This necessitates the integration of incident and problem management to govern multi-providers’ activities managing hybrid Cloud1.
- As a Service
-
01 June 2018
Conclusion: Private Cloud1 managed by an as-a-Service contract has become the inevitable replacement of managed services arrangements. The main difference is that an as-a-Service contract is charged on consumption instead of on a fixed price basis and the service levels are tightly linked to end user experience and delivered at a lower price. However, unlike the common perception that Cloud migration is relatively easy, transitioning to private Cloud still requires thorough planning especially whenever the scope covers the full IT functions.
- As a Service
-
05 May 2018
Conclusion: Business continuity and disaster recovery plans are largely developed in isolation. The result is ineffective recovery arrangements that do not meet the fundamental business needs. With the variety of Cloud service continuity solutions, IT organisations should initiate a unified business and IT continuity project to intimately involve business units in defining and deploying complete service recovery facilities, including mitigating the risks such as ransomware attacks and the lack of SaaS escrow1 services. This will tightly couple recovery services to business imperatives. The use of Cloud for service continuity (which was not available eight years ago) will reduce the overall cost of recovery.
- As a Service
-
01 April 2018