Skip to content
Technology transformation expertise firm · ARDIANE Group Innovate, secure, succeed

Glossary

Third-party application maintenance (TMA): definition, forms of maintenance and scope

Domain

Engineering

In brief

Third-party application maintenance (TMA, from the French tierce maintenance applicative) refers, in French usage, to the maintenance of one or more applications entrusted by an organisation to an external provider. Its scope, set by the contract, can combine the correction of defects, functional changes, adapting the application to changes in its environment and preventive work.

Page contents

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.

Insights

Further reading

All insights
IT public procurement, read in the French public procurement code and the CCAG-TIC

IT public procurement contracts are governed by the French public procurement code for their preparation and award, and by the CCAG-TIC for their performance when the contract refers to it. Management Square reads both texts here: definition of needs, division into lots, procedures, contract documents, verifications, ownership of results and reversibility, with what each leaves to the contract.

Read the analysis
Before an acquisition, the questions an IT due diligence asks of the target's information system

An IT due diligence, or acquisition audit of the information system, examines before an acquisition or an equity investment the state of the applications, dependencies, security, contracts and the system's capacity to be integrated or separated. Management Square presents here an investment committee's questions on these subjects, the evidence to request and what each answer changes in the transaction.

Read the analysis
Recognising application obsolescence by its signs, before the deadline is imposed

Application obsolescence refers to the ageing of the components of an application that still delivers its service; Management Square deliberately extends the term here to knowledge of the application and its ability to evolve. The article describes its observable signs, layer by layer, with the risk that each may indicate and the way to respond to it.

Read the analysis

FAQ

Frequently asked questions

Another question? Ask us

What does TMA stand for?

TMA is the French acronym for tierce maintenance applicative, third-party application maintenance. In French usage, the term refers to the maintenance of one or more applications entrusted to an external provider, the third party. Its exact scope is the one set by each contract: it can range from the correction of defects alone to all work on the application.

Which forms of maintenance can a TMA cover?

Usage distinguishes four forms of application maintenance: corrective (repairing an observed defect), evolutive (modifying or adding a function), adaptive (following a change in the technical environment) and preventive (acting before the failure). A TMA can cover all of them or only some, depending on the contract. The ISO/IEC/IEEE 14764:2022 standard adopts a similar breakdown, into five types.

What is the difference between TMA and managed services?

TMA concerns the application software: its code, its defects, its changes. Managed services (infogérance in French), another term of usage, here refers to operations entrusted to a provider: servers, backups, systems administration. The two services can be entrusted to the same provider or to two separate providers, which makes it necessary to write down who handles an incident depending on its origin.

What is reversibility in a TMA contract?

Reversibility is the phase in which the TMA provider hands back to the client, or passes on to another provider, what is needed to take over the maintenance: source code, documentation, request history, knowledge of the business rules. Its terms are set in the contract, before the service starts. It addresses the risk of dependence on the third party.

A project to bring to completion?

A first conversation is enough to understand your challenge, identify the right people and tell you frankly what we can bring.