XLA metrics : 8 experience signals that predict adoption and deflection
Learn how XLA metrics help IT leaders go beyond SLAs…
Read more
ITSM Consulting & Implementation by ITIL v4–Certified Engineers
SMC Consulting helps organisations structure and improve IT Service Management (ITSM) by combining ITIL v4-aligned practices with hands-on ITSM platform implementation. We define service management workflows, governance rules, and platform configuration so support teams can operate consistently and measure performance over time.
Scope we typically cover
- ITSM practices: Incident / Service Request / Change / Problem / Knowledge / CMDB
- ITIL v4: certified consultants involved in delivery (practice design, governance, implementation)
- Platform experience: ServiceNow , HaloITSM , Freshservice
They Trust Us
Why ITIL® 4 certification matters for ITSM projects
When consultants share a standard framework, it reduces variation in how processes are defined, configured, documented, and measured. For clients, that translates into clearer delivery and more predictable outcomes.
Less risk
Clearer approvals, controls, and traceability for service operations.
More stability
Consistent workflows and ownership reduce avoidable exceptions.
Faster resolution
Better routing, escalation, knowledge use, and measurable SLAs.
Better alignment with the business
Services, priorities, and reporting are easier to standardise and review.
Meet our ITIL v4 consultants (ITSM delivery)
All SMC consultants involved in ITSM delivery are ITIL® 4 certified. This matters because ITSM results depend on both
good operating design and workable execution inside the tool.
good operating design and workable execution inside the tool.
Hedi El Asmi
Senior IT Consultant | ITIL v4
See certifications
Hedi supports ITSM initiatives from a senior consulting and business analysis perspective: clarifying requirements, mapping operational workflows, defining role responsibilities, and translating service management needs into implementable specifications for ITSM platforms.
Typical ITSM focus areas
- Requirements and workflow specification (incident / request / change)
- Service catalogue structure and request form design
- KPI definitions and reporting requirements
- Operating procedures and documentation
Sara Gutiérrez López
Manager, Support & Delivery | ITIL v4
See certifications
Sara supports ITSM work from a support and delivery management angle: service desk operating model, team execution, handoffs between tiers, service ownership, and governance cadence—critical to ensure process designs are usable in real operations.
Typical ITSM focus areas
- Support operating model (roles, queues, escalation)
- Delivery coordination and governance cadence
- Adoption and operational readiness
- Service performance review routines
Zakaria Makboul
ITSM Implementation Engineer | Process Automation Specialist | ITIL v4
See certifications
Zakaria focuses on implementation: configuring workflows, automating fulfilment steps, integrating operational inputs, and ensuring ITSM processes are executed consistently inside the tool.
Typical ITSM focus areas
- ITSM platform implementation and configuration
- Workflow automation and standardisation
- Integrations and operational tooling alignment
- Data capture rules for reporting quality
Afaf Atraoui
IT Consultant | ITIL v4
See certifications
Afaf supports organisations in translating operational needs into structured requirements, documented workflows, and stakeholder alignment—so platform configuration reflects agreed processes and enables reliable reporting.
Typical ITSM focus areas
- Workflow clarification and documentation (as-is / to-be)
- Process-to-tool alignment (states, rules, ownership)
- Service catalogue structuring (services, request items, templates)
- Data capture rules and governance (mandatory fields, validation, quality)
Marc Abou Abdo
Consultant | ITIL v4
See certifications
Marc supports initiatives by structuring requirements through the ITIL v4 lens and aligning service management with business value. He helps standardise workflows, clarify RACI, define service levels, and improve reporting consistency.
Typical ITSM focus areas
- Requirements aligned with the ITIL Service Value System
- Workflow mapping and standardisation for efficiency
- KPI and reporting requirements tied to business value
- Stakeholder coordination and operational documentation
0 +
years of ITSM
experience
experience
0 +
ITSM implementations across organisations
of different sizes and sectors
- ITSM practice standardisation + reporting governance -> improved SLA visibility and decision-making
- Service catalogue + request workflows -> reduced manual handling and improved fulfilment consistency
- Tool configuration optimisation -> better routing, fewer reassignments, faster resolution
Our ITSM expertise aligned with ITIL v4 best practices
Our ITSM work covers the practices most often required to stabilise and standardise service operations: incident management, service request management, change enablement, problem management, knowledge management, and configuration management (CMDB). For each area, we translate operational requirements into clear workflow rules (states, responsibilities, approvals, exceptions), consistent data capture, and measurable targets.
In practical terms, this means turning ITIL v4 practice concepts into implementable decisions:
- Which states exist (and what triggers state changes)
- Who owns each step (RACI and operational handoffs)
- How exceptions are handled (escalations, major incidents, approvals)
- Which approvals are required (and under what conditions)
- What data must be captured (mandatory fields, validation, data quality)
- How success is measured (KPIs, SLAs, governance cadence)
ITIL v4 for ITSM implementation
ITIL v4 is useful when applied as a practical framework to structure decisions and documentation. On real ITSM projects, it typically shows up as:
- A defined scope per practice (included / excluded)
- Explicit roles (process owner, service owner, resolver groups, change authority)
- Standardised records (incident/change/problem/request fields and mandatory data)
- Measurable rules (SLA timers, pause conditions, breach handling)
- A continual improvement loop (review cadence + backlog + ownership)
SMC Consulting ITSM services
ITSM assessment & baseline
We review the current situation across process, tooling, data quality, and reporting. The output is a backlog and roadmap that can be executed in iterations.
Inputs (typical)
- Ticket exports (3–6 months)
- Current SLA definitions
- Service catalogue list
- Workflow/config overview
Outputs
- Baseline KPIs (where data allows)
- Gaps and prioritised improvements
- Delivery plan / roadmap
ITSM practice design aligned with ITIL v4
We produce operational artefacts for one or more practices:
- Incident management (priority model, escalation, major incident)
- Service request management + service catalogue (taxonomy, forms, fulfilment flows)
- Change management (risk model, approvals, standard changes, PIR)
- Problem management (RCA templates, known errors, linking rules)
- Knowledge management + self-service (templates, governance, search metadata)
- CMDB / configuration management (scope, CI model, ownership, quality controls)
Platform configuration & integrations
Configuration work typically includes workflow/state models, forms, routing rules, SLA/OLA setup, permissions, and integrations:
- SSO / identity
- Collaboration tools
- Monitoring/event intake
- Asset data sources
Related capability: ITSM Automation & Orchestration
What’s included in an ITSM implementation
This is what “implementation” typically includes when we configure or optimise an ITSM platform:
- Workflow/state design per practice (incident/request/change/problem)
- Routing & assignment logic (queues, resolver groups, skills-based assignment where relevant)
- Forms & data model (mandatory fields, validation, category structure)
- SLAs/OLAs (service hours, pause conditions, breach handling, reports)
- Portal & service catalogue (requests, approvals, fulfilment flows, templates)
- Knowledge base structure (taxonomy, ownership, publishing workflow)
- Roles & permissions (agents, approvers, stakeholders, access boundaries)
- Dashboards & KPIs (SLA compliance, backlog aging, resolution times, volume trends)
- Operational governance (cadence, review templates, continual improvement backlog)
- Go-live plan + hypercare (rollout, coaching, stabilisation period)
Reporting, KPIs & governance
We define KPI calculation rules (business hours, pause conditions, exclusions), build dashboards, and set up a review cadence that results in actions (not just charts). If you want a service management reference point beyond ITIL, you can also align governance to ISO/IEC guidance (overview: ISO).
Flexible ITSM platform with a strong service desk core (tickets, SLAs, portal, knowledge, automation) that can be configured quickly and adapted to operational realities.
Designed for organisations that need standardised ITSM practices at scale, with strong governance, extensibility, and integration options.
Known for quick adoption and usability. Covers core ITSM needs (service catalog, workflows, knowledge, approvals, reporting) and supports rapid rollout.
ITSM platforms we
work with
We support ITSM implementation and optimisation across commonly used platforms. Scope typically includes workflows, forms, routing rules, SLAs, permissions, knowledge + portal structure, integrations, and reporting configuration.
Our Blog
NIS2-ready CMDB: the minimum asset data model for cyber-resilience (EU)
Understand how NIS2 CMDB requirements transform your CMDB into a…
Agentic AI in ITSM: 10 service desk workflows you can safely automate in 2026
Explore how agentic AI ITSM will reshape the service desk…
Most frequently asked questions on ITSM and ITIL v4
ITSM is the discipline of managing IT services end-to-end. ITIL v4 is a framework that describes practices and concepts commonly used to structure ITSM work.
It reduces ambiguity in how practices are designed and implemented: clearer roles, workflow rules, data capture standards, SLA logic, and governance—so processes and reporting stay consistent over time.
Often yes. Improvements can focus on workflow rules, queue structure, SLAs, knowledge structure, reporting definitions, governance routines, and data quality within the existing platform.
Typical inputs are ticket exports, SLA definitions, a review of the service catalogue, and a walkthrough of the current platform configuration. Outputs are a baseline, gaps, and a prioritised improvement plan.
We implement CMDB iteratively: define scope boundaries, CI model + relationships, ownership, and quality controls first—then expand based on operational needs (impact analysis, change risk, incident correlation). Related: CMDB
We define SLA targets, service hours, pause conditions, breach handling, and reporting rules so SLA compliance is measured consistently and supports operational decisions.
