Skip to content

IT operations and maintenance steering (RUN, MCO, TMA)

Bordeaux and Nouvelle-Aquitaine, remote across France

Releases go well, but what comes after does not keep up: incidents pile up, changes are made in a hurry, and nobody reads the maintenance provider's reports. I step in to take operations back in hand: stabilise production, cut the incident backlog, set up useful ITIL processes (incidents, problems, changes), define SLAs and indicators, and steer your provider on facts. For IT departments, operations managers and consultancies that hold a maintenance contract.

Book a free call

The problem I solve

Degrading operations make no noise at first. The incident backlog grows by a few tickets a week, the same failures come back because nobody has time to find the cause, and changes go through without review because the review takes too long. After a few months, the team does nothing but firefighting and projects wait. The maintenance provider, meanwhile, meets its SLAs on paper, because the SLAs measure response time and not resolution. My role is to make that degradation visible and quantified, then push it back process by process.

How I work

Quantified state of play

Incident backlog by severity and age, recurring incidents, changes made without review, SLAs actually met. At the end of this phase you have a picture of your production that nobody can dispute in a committee.

Useful ITIL processes, not a binder

Incident, problem and change management sized to your organisation: a short form, clear priority rules, a change review that fits in thirty minutes. The process serves the team, not the other way round.

SLAs and indicators that measure resolution

Service levels defined on what matters to users: resolution time, recurrence rate, incidents open for more than 30 days. A weekly dashboard, readable by management, replaces the monthly reports nobody opens.

Incident review and improvement plan

Root cause analysis on recurring incidents, corrective actions tracked to closure, and steering of the maintenance provider on those facts: follow-up committees with written decisions, escalation or renegotiation of scope when the contract does not cover the real need.

Real example

Where this comes from: at EDF, from 2020 to 2022, I steered a demand management application handling around 20,000 tickets a year for a service centre, across an estate of 3,000 to 5,000 workstations and with teams of 2 to 10 people.

Read the case study

Who it is for

  • IT departments whose teams spend their time firefighting at the expense of projects
  • Operations managers who inherit an incident backlog with no history
  • Consultancies that hold a maintenance contract and want to take its steering back in hand
  • Organisations changing maintenance provider that need to frame the transition

What you get

  • A quantified state of play of production: incidents, recurrences, changes, SLAs
  • Incident, problem and change processes sized to your organisation
  • SLAs and a weekly dashboard that measure resolution, not response
  • A regular incident review with a tracked improvement plan
  • Steering of the maintenance provider with committees and written decisions

Frequently asked questions

What is the difference between MCO and TMA?+

MCO (maintien en conditions opérationnelles) is the French term for all the activities that keep a system running: monitoring, fixes, updates, backups. TMA (tierce maintenance applicative) is the contract under which an external provider handles all or part of that maintenance on your applications. The first is steered internally, the second by contract, but with the same indicators.

Do you have to implement all of ITIL?+

No. ITIL describes dozens of practices, and most organisations only need three to stabilise production: incidents, problems, changes. I set those up first, sized to your team. The other practices come later, only if a concrete need justifies them, and never because a framework says so.

Do you work on the client side or the provider side?+

Both. On the client side, I steer the maintenance provider and the operations teams. On the consultancy side, I take over the steering of a maintenance contract that has deteriorated, to bring it back up to standard before the next review with the client. In both cases I work on shared indicators, not one-way reports.

How much does it cost?+

On a quote basis: a daily rate for steering operations over time, or a fixed fee for the quantified state of play and the process set-up. The first call is free: we look at your incident backlog, your organisation and your maintenance contract if there is one.

Operations steering covers organisation and processes. It does not include a technical security audit such as penetration testing.

Production to stabilise

Book a free first call. Come with your incident backlog and your latest maintenance reports: we will see where to start.