Start a free trial
Menu

ALP-10

ALP-10 NATO guidance for integrated life cycle support

Defence contractors, ILS teams and programme offices running integrated life cycle support on a NATO acquisition programme

NATO guidance on integrated life cycle support (ILS), what an acquirer, contractor and programme office plan, analyse and document to keep a defence system supportable from concept through disposal.

Edition
D
Published
2025-06

What it is

ALP-10 is NATO's guidance for Integrated Life Cycle Support (ILS): the management and technical process through which supportability and logistic support considerations are integrated into a system's design and carried through the whole of its life, rather than bolted on once the system exists. It addresses "NATO programmes, NATO Agencies, and Nations" directly (clause 1.2), and inside a programme it is written around the relationship between an acquiring Customer or Buyer and a Contractor or Supplier who carries out the ILS work under contract, coordinated by a dedicated ILS Management function.

The thirteen ILS elements

ALP-10 breaks ILS into thirteen elements: ILS management itself, design interface and supportability analysis, reliability, availability, maintainability, safety and testability (RAMST), maintenance, supply support, support and test equipment, training and training support, technical information, workforce and personnel, packaging, handling, storage and transportation, facilities and infrastructure, IT system support, sustaining engineering, and environmental conditions and recoverability. Each element carries its own recommended standards, processes and outputs across the life cycle; ALP-10 explains what each is for and leaves the detailed format of any specific analysis or report to whichever standard a project selects, tailored to "the size and complexity of the project/program and on the nature of the SOI" (clause 5.2.1).

The seven life cycle stages

ILS is mapped against NATO's own seven-stage system life cycle, taken from AAP-20: Pre-Concept, Concept, Development, Production, Utilisation, Support and Retirement. Pre-Concept is where the Customer identifies and documents stakeholder requirements and high-level risk areas (clause 3.5.1) and opens an initial ILS Plan; Concept turns that into a feasible design solution and a draft Statement of Work. Development runs a sequence of joint design reviews in which Supportability Analysis builds a Candidate Items List and draft Task Inventory, validated through techniques such as FMECA and Reliability Centred Maintenance, and feeds supply support, technical information, training and facilities work in parallel. Production validates the Supportability Analysis dataset against the system actually delivered and revises it where the design has moved on. Utilisation and Support run largely together: the system is operated, performance and failures are monitored, and any gap in how in-service feedback data reaches the people who need it is corrected. Retirement disposes of the system and its supporting infrastructure under security and demilitarisation requirements.

Who is responsible

The Customer or Buyer owns requirements and the ILS Strategy from Pre-Concept onward, and its ILS Plan is what a Contractor's own Integrated Support Plan has to answer, point by point, once tendering begins. ILS Management is "responsible for the development and performance of the ILS programme" (clause 4.3): setting the ILS vision, identifying which of the thirteen elements apply, appointing element managers, developing the ILS Plan, setting change, risk and communication methods, training the ILS team, tailoring processes to the programme, and monitoring progress. Element managers and subject-matter experts then own execution of their own element. Engaging industry is treated as work in its own right: the ILS team has to agree a clear contractual understanding, unambiguous requirements and tailored analyses with a Contractor before work starts, and where more than one nation is buying together, a single point of contact for direction. ALP-10 also names a long list of functions that sit outside ILS but that it depends on: systems engineering, configuration management, obsolescence management, risk management, data management and quality among them.

Data, analyses and documentation

Analyses named throughout ALP-10, such as Failure Modes, Effects and Criticality Analysis, Reliability Centred Maintenance and Level of Repair Analysis, exist to answer specific supportability questions about a system, for example which items should be repaired where, and to feed the Candidate Items List and Task Inventory that structure the rest of the ILS work. Data exchanged between a Customer, Contractor and Suppliers has to be agreed, has to be something every party can actually act on, and has to be traceable to its source. In practice this is settled at a Guidance Conference, typically held within 60 days of contract award, where the parties agree how Supportability Analysis, supply support and technical information data will be interpreted, and the agreement is recorded rather than assumed. ALP-10 does not prescribe a single data format itself; it points to the standard a project has selected, most often the ASD/AIA S-series described below, and leaves the specific report content to that standard.

How conformity is shown

ALP-10 is guidance, not a certifiable scheme: no clause names a body that certifies an organisation against it. Conformity is shown instead through a sequence of joint reviews and audits that gate progress: System Requirements Review, System Functional Review, Preliminary Design Review, Critical Design Review, Test Readiness Review, Functional Configuration Audit and System Verification Review through Development, then a Production Readiness Review and a Physical Configuration Audit in Production, which exists "to determine conformance to the as-built configuration of validated Configuration Items with design documentation and verify the product baseline" (clause 5.3.4.1.2). These are run and reviewed jointly by the Customer and the Contractor. Supportability Analysis data is separately validated "in agreement with the customer" against the delivered system (clause 5.3.4.2), and corrected where it does not match what was actually built.

Quality assurance runs through NATO's own regime rather than a third-party certificate: "In the context of NATO acquisition, QS arrangements must be extended to include external providers, i.e. Government Quality Assurance" (clause 3.6.3.8), tied to STANAG 4107 and its Allied Quality Assurance Publications, which is a national authority's surveillance against a contract, not an accredited body certifying a management system. ALP-10 also describes a System of Interest Maturity Assessment, a questionnaire-based self-assessment a programme's own subject-matter experts run, which is a maturity check on the programme rather than a certification of the supplier. Elsewhere in the document, "certification" means certifying individual trained personnel or calibrating test equipment, not an organisation holding a certificate against ALP-10.

Standards it references

ALP-10 sits under STANAG 4876, which records the agreement of nations to use the publication. It builds on AAP-20 for the seven-stage life cycle model, which ALP-10 explicitly does not tailor itself, and AAP-48 for the process-oriented approach behind its cross-cutting processes. Individual ILS elements point to further standards as background reading: AEP-67 for system assurance and cyber security, ALCCP-01 for life cycle costing, STANAG 4427 and ISO 10007 for configuration management, STANAG 4597 for obsolescence management, STANAG 4728 for systems engineering, STANAG 4107 for the quality basis behind Government Quality Assurance, STANREC 4814 for software management, and STANAG 4370 with AECTP-100 for environmental conditions. Retirement-stage work also names a cluster of civil management-system standards as options: ISO 9001, ISO/IEC 27001, ISO/IEC 27002, ISO 14001, ISO 22301 and ISO 50001, alongside IEC 60812 and IEC 61508.

One family of standards is central to ALP-10 without a catalogue link to point to: the ASD/AIA S-series (SX000i, S1000D, S2000M, S3000L, S4000P, S5000F and S6000T). ALP-10 states that "the following table shows specifications/standards that shall be used during the Life Cycle of a SOI" (clause 5.2.1) and then works through each S-series specification against older alternatives such as MIL-STD-1388 and the UK's Def Stan 00-60 series. ISO/IEC/IEEE 15288, which ALP-10 uses as the basis for its design reviews, and AcodP-1, NATO's codification manual, are cited the same way. We name them here as ALP-10 itself names them, without a page to send you to.

NATO publications are free of charge. ALP-10 is available from NATO's Standardization Document Database; we link to NATO's own listing rather than hosting a copy.

How we help

ALP-10 describes engineering and logistics work, running Supportability Analysis, producing an Integrated Support Plan, sitting design reviews, validating a dataset against a delivered system, and that work is done by an ILS team, not by a compliance platform. ComplyTrain does not perform Logistics Support Analysis, does not produce an Integrated Support Plan or a Supportability Analysis dataset, and does not sit in for a design review or a Government Quality Assurance visit.

What a supplier can evidence around that work is the management system built to hold it: the ILS Plan and its version history, the procedure that defines how the ILS team operates, a record that a Guidance Conference took place and what it agreed, training records for the people staffing ILS roles, and the trail showing a design review or a Physical Configuration Audit happened, who was in the room, and what it found. ComplyTrain gives a supplier a place to hold that documentation, keep it version-controlled, and produce it when a Customer or a Government Quality Assurance representative asks to see it, the same way it supports any management system a supplier runs under contract.

The applicable tier on any given programme, and which standards come with it, is set by the contract and the customer's own quality clause, not by us. If you want to see what sits alongside ALP-10 for a programme you are working, the standards explorer is the place to start, and we are glad to talk through it.

Standards it references

Questions

Is ALP-10 mandatory?

Not on its own. ALP-10 says plainly that NATO and Nations are "encouraged" to use it as directive guidance rather than a mandatory rule, and that it is meant to complement national acquisition policy rather than replace it. What actually binds a supplier is whatever a specific contract, Statement of Work or Contract Data Requirements List says.

What edition is current?

Edition D Version 1, promulgated 24 June 2025, which superseded Edition C Version 1.

Can a company be certified to ALP-10?

No. ALP-10 names no certification scheme or certifying body for an organisation. Conformity is shown through joint design reviews and audits between the Customer and the Contractor, and through NATO's Government Quality Assurance regime under STANAG 4107, which is government surveillance against a contract rather than third-party certification.

What is the difference between ALP-10 and STANAG 4876?

STANAG 4876 is the agreement by which nations record their commitment to use ALP-10; ALP-10 is the guidance document itself, containing the ILS elements, life cycle mapping and roles a programme actually works to.

Do all NATO nations apply ALP-10 the same way?

No. ALP-10 records national reservations against its own text: Canada's does not adopt the thirteenth ILS element, Environmental Conditions and Recoverability, and France's states it will apply ALP-10 on a case-by-case basis rather than in full.