Definition of third-party application maintenance
Third-party application maintenance, abbreviated in French as TMA, refers to the maintenance of one or more applications entrusted by an organisation to an external provider: the third party. It begins once the application is in service and lasts as long as the contract that organises it.
The term belongs to French usage. Its scope is the one set by each contract: a TMA can be limited to the correction of defects, or bring together all work on the application. Two contracts bearing this name can therefore cover different services.
Why entrust the maintenance of an application to a third party
An organisation may turn to it for several reasons: keeping its teams on new projects, finding skills it no longer has on an older technology, or writing response and correction times into a contract.
The trade-off lies in knowledge. A provider that maintains an application on its own becomes the custodian of that knowledge: its business rules, its weak points, the history of its fixes. Two phases address this when the contract provides for them: knowledge acquisition at the start, reversibility at the exit.
Corrective, evolutive, adaptive, preventive: the forms of maintenance
| Form | What it covers | What triggers it |
|---|---|---|
| Corrective | Repairing an observed defect | An incident, a wrong result |
| Evolutive | Modifying or adding a function | A request from the business |
| Adaptive | Keeping the application usable when its environment changes | A system version upgrade, a modified interface |
| Preventive | Acting before the failure | A latent fault, spotted before it causes an incident |
This breakdown into four forms is a classification of usage. The ISO/IEC/IEEE 14764:2022 standard (Software engineering, Software life cycle processes, Maintenance) offers a similar one. According to its scope, as read on the record of the Estonian Centre for Standardisation (EVS), it establishes definitions for the various types of maintenance. The public extract of the standard, read on 12 November 2026 in the iTeh Standards catalogue, distinguishes five: corrective, preventive, adaptive, perfective and additive. It classes the last three as enhancements.
The word “evolutive” does not appear in this list. In our reading, it covers the perfective and additive types.
TMA, managed services and projects: not to be confused
TMA concerns the software. Operations (backups, recovery, systems administration) are a different trade, referred to here as managed services (infogérance) when they are entrusted to a provider. The ISO/IEC/IEEE 14764 standard draws the same line: its scope excludes operations functions.
Nor is TMA an engagement model. It can be bought on a fixed-fee basis, on a time-and-materials basis or in a mixed form, a distinction covered in our article fixed fee or time and materials.
Finally, a large-scale change falls outside maintenance. The extract of the standard notes that larger changes may require a new development effort. A contract can set this threshold; beyond it, the request is run as a project.
Example: a claims management application moved to TMA
Take an insurer whose claims management application was developed in-house. The original team moves on to other projects, and the maintenance is entrusted to a provider.
Four requests then arrive. An indemnity calculation that is wrong for certain policies: corrective maintenance. A new field requested by the claims handlers: evolutive. A change in the format of a data feed exchanged with accounting: adaptive. A query that slows down as volumes grow, reworked before it blocks the claims handlers: preventive, and a way of containing technical debt. A fifth request, the rewriting of the settlement module, exceeds the contract threshold: it becomes a project.
An application is all the easier to maintain when its handover has been prepared from the design stage, the subject of our page on custom software development. When maintenance is no longer enough to make it evolve, the question becomes one of application modernisation.