Corrective maintenance
Defects handled according to agreed priorities and response times.
Not sure which service you need?
Tell us what is blocking you: we tell you which piece solves it.
Advice from Rabat, Morocco
INGENIT Labs
We keep your applications running and evolving, including the ones we did not write.
An application in production needs fixes, security updates and changes. Application maintenance organises that work: agreed priorities, tracked response times, a shared history.
We maintain applications built through our custom software development, and those of other teams after a takeover audit. To strengthen your own team rather than hand over maintenance, see our dedicated development teams.
The essentials
Application maintenance outsourcing, known as TMA (tierce maintenance applicative) in France and Morocco, means entrusting the maintenance of one or more applications to an external provider. It covers three kinds of work: corrective maintenance, which fixes defects; evolutive maintenance, which adds or changes features; and preventive maintenance, which updates components and reduces the risk of failures or security flaws. The contract sets the scope of applications, the service levels (response and resolution times by severity), how requests are submitted and tracked, and the reversibility terms if you change provider. Maintenance can cover an application built by another provider, after a takeover phase.
It suits applications that must stay available and keep evolving without tying up an internal team full time. To prepare a contract, our guide on how to scope an application maintenance contract details the points to settle.
Software that moves forward.
Defects handled according to agreed priorities and response times.
Changes planned at the pace of your business, costed before they start.
Technical updates, dependencies and security patches applied before they become urgent.
Code and hosting audit, priority fixes, then planned maintenance.
A maintenance contract usually covers all three, with different rules for each.
| Corrective maintenance | Evolutive maintenance | Preventive maintenance | |
|---|---|---|---|
| Goal | Restore the intended behaviour | Adapt the application to new needs | Reduce the risk of failures and vulnerabilities |
| Trigger | A reported defect | A business request or a new obligation | An update schedule |
| Examples | A wrong calculation, a frozen screen | A new export, an extra approval step | A dependency update, a security patch |
| Set in the contract | Response and resolution times by severity | A quote before each change | Frequency and scope of updates |
Application maintenance covers applications. For servers, networks and workstations, managed IT services take over.
Code, hosting, documentation and priority risks.
Transition period and team onboarding.
Requests handled according to agreed priorities and times.
Regular reports, steering meetings and an evolution plan.
Yes. We start with an audit of the code, hosting and documentation, then a transition period before taking over maintenance.
Together, in the contract: each priority level has a response time, a resolution time and covered hours. Our guide on scoping an application maintenance contract covers these points.
Both exist. A subscription suits a steady flow of requests, pay-per-intervention suits an application with little activity; the formula is chosen with you during scoping.
Application maintenance covers applications: their code, defects and changes. Managed IT covers infrastructure and workstations: servers, networks, backups, user support. Both can be handed to the same provider.
The contract includes a reversibility phase: handover of the code, documentation and access, then knowledge transfer to your team or to another provider.
Describe your context in a few lines: we come back to you with a first reading.