What is the difference between ITSM and ESM (Enterprise Service Management)?
ITSM organises the delivery of IT services: requests, incidents, changes, service levels, knowledge and the service catalogue. ESM applies the same service management principles to the other functions of the business: human resources, procurement, facilities, finance or any other internal service. Both rest on a shared logic, but the processes and the vocabulary adapt to each line of work.
How do you choose an ITSM tool?
Three criteria settle it: your existing technical estate, your data location constraints, and the administration workload your teams are willing to carry. The choice of ITSM software comes after the catalogue and the commitments have been scoped, otherwise the tool inherits the existing disorder.
Do you already need an ITSM tool to work with BleuLemon?
No. We can work on an existing setup, develop a platform already in place, or support the choice and deployment of a new solution. We start with the processes, the ways of working and the goals. The tool comes afterwards.
Why call on BleuLemon rather than the vendor, or run the project in-house?
Because our work does not stop at configuring the platform. We treat processes, organisation, tooling and adoption as one coherent whole. We can work alongside your internal teams and the vendors, bringing our experience of ITSM and ESM projects and our ability to connect ways of working, processes and technology.
What is a CMDB and what is it for?
A CMDB (Configuration Management Database) records the configuration items of the information system, servers, applications, workstations, contracts, and above all their dependencies. Its real value: measuring the impact of an incident or a change before acting. We keep its scope to the uses agreed during scoping.
What is an IT SLA and how do you define one?
An IT SLA is a commitment on time and quality for a service, with its calculation method and its exclusions. It is defined from your own historical data, not from an external benchmark. Without automated measurement in the tool, an SLA remains a statement of intent.
How long does an ITSM deployment project take?
The duration depends on the scope, the number of services involved, what is already in place and the populations to support. We aim as far as possible for a first release within 90 days. A project that goes too long without a concrete result loses momentum, occupies teams with nothing visible to show, and becomes harder to get adopted.
Where the scope is broader, we therefore prefer to deliver a first working version, measure how it is used and improve it in a second version, rather than trying to cover everything in the first deployment. Delivering quickly is what lets you learn about real usage and stay effective.
Are you ITIL certified?
Yes. Our consultants are certified in ITIL v3 and ITIL 4. We use ITIL as a best-practice framework and a shared vocabulary, not as a recipe to be applied as is. Processes have to stay suited to your organisation, your users and your constraints.
What role does AI play in IT service management?
AI can come in at several levels: helping the user phrase a request, searching the knowledge base for an answer, suggesting a qualification, summarising a history or spotting recurring requests. Its role depends on the process and on how much autonomy the organisation wants to give it. From the scoping stage we define what can be automated, what needs human validation and what must stay in the hands of the teams.
