What it is
AAP-20, the NATO Programme Management Framework, is also known as the NATO Life Cycle Model. AAP stands for Allied Administrative Publication, and this one is generic and tailorable: it sets out how a NATO, multinational or national defence acquisition programme moves from an identified capability gap to a fielded system, and eventually to that system's retirement. Nations record their agreement to use it in STANAG 4728, and the current Edition C, Version 1 (October 2015) superseded Edition 2.
AAP-20 is written for the customer side of a programme, not for a supplier. It addresses NATO bodies, Agencies, Groups of Nations and Nation(s) who own a programme and are accountable for delivering the capability it is meant to produce. Industry executes the resulting contracts, but the document is explicit that accountability for the programme never transfers to industry, however much of the day-to-day product life cycle work industry actually carries. A supplier encounters AAP-20 only when a tender, contract, or Programme Memorandum of Understanding (MOU) invokes its structure, and from that point the supplier's own deliverables, reviews and configuration milestones are timed to the customer's stage-gate decisions rather than to the supplier's own project plan.
The seven programme stages
The framework divides a programme into seven stages: Pre-Concept, Concept, Development, Production, Utilisation, Support and Retirement.
Pre-Concept identifies and documents stakeholder requirements and high-level risk. Concept, split into a Study Phase and a Programme Establishment Phase, evaluates alternative technical concepts, including a market survey of off-the-shelf options, and produces preliminary system requirements plus initial Configuration Management, Integrated Logistics Support (ILS) and Obsolescence Management plans. Development fully validates the selected technical solution through detailed engineering and prototyping. Production manufactures and tests the system and runs acceptance tests. Utilisation is where the fielded system is operated, monitored, and has anomalies and failures recorded and resolved. Support runs the logistics, maintenance and support services that keep it operating. Retirement, in a Disengagement Phase followed by a Liquidation Phase, withdraws the system from service and disposes of it against an approved Programme Liquidation Strategy, addressing safety, security and environmental requirements along the way.
Each stage ends with a decision gate and needs a Programme MOU or Stage Approval Document before the next stage can begin. A modification or upgrade made to a system already in Utilisation or Support runs its own miniature version of this same sequence, from a Pre-Concept-style needs assessment through to production of the modification kit, rather than being handled as an informal change.
Decision gates, not certification
AAP-20 describes no accreditation scheme, no certifying body and no external assessor. What decides whether a programme moves forward is a decision gate: a point in the life cycle where past work is checked as mature and validated, future work is agreed, and the outcome, proceed, continue, revert to an earlier stage, hold, or terminate, is documented. That decision is made by the customer, not by a third party, and it can send a programme backward to a preceding stage as a normal outcome, not a failure.
A supplier's deliverables are reviewed against the entry and exit criteria the customer has set for a given gate. Where the document does use the word "certification," it is about the product, an item's safety or environmental certification, or software certified before it is incorporated into a system, never about an organisation being "AAP-20 certified." No such credential exists.
Accelerated fielding for urgent needs
Where the standard stage sequence would be too slow for an urgent operational requirement, AAP-20 describes Accelerated Fielding: fast tracking (compressing or cutting steps and documentation), multi-stage decisions (obtaining approval for more than one stage at once), increased use of off-the-shelf products, and technology insertion into systems already in service. Each comes with its own named risks, from unforeseen performance problems to lost resources from a wrong compressed decision, and none of them lowers the underlying obligation; they change its timing and packaging.
What it assumes, and what it doesn't cover
AAP-20 says plainly that it should be used together with AAP-48, which defines the System Life Cycle Management processes that actually populate AAP-20's stage structure with activities. AAP-20 supplies the skeleton of stages, gates and criteria; AAP-48 supplies what fills it. Beyond that companion document, AAP-20 requires no prior capability or management system: it is a framework to plan a programme within, not a bar to clear first.
The document also keeps a distinction easy to miss: the System-of-Interest itself is tracked separately from "enabling systems," simulators, ground equipment, tools, spare parts, that support the system through its life without performing its operational function. Both have to reach maturity for the programme to succeed, but AAP-20 does not treat them as one thing.
Getting the document
NATO publishes AAP-20 through the NATO Standardization Document Database at no charge. ComplyTrain does not sell it or host a copy; the NSDD listing for AAP-20 is the source.