MACP-01 guidance for negotiating co-operative armaments MOUs

What it is

MACP-01 (NATO prints it MACP-1), an Allied Acquisition Publication, is guidance and a checklist for the government officials who negotiate a Memorandum of Understanding (MOU) or Programme MOU (PMOU) that sets up a joint armaments programme between NATO nations. It is not addressed to industry. It is addressed to the negotiators: "Memoranda of Understanding (MOUs) are formal written arrangements between governments (or between governments and NATO Agencies) setting forth the conditions under which they intend to co-operate in given areas." Volume I consolidates and supersedes three earlier AACP-1 documents into one publication, and nations record their recommendation to use it through STANREC 4792, a recommendation rather than a ratified commitment. The checklist itself says plainly that its own items "are not mandatory".

That distinction matters because an MOU produced with this guidance is a binding agreement between the signing governments, but MACP-01 imposes nothing on a supplier directly. A supplier only meets what an MOU decided once a Contract implements it: the document notes that its own provisions on disclosure and use of technical information "will in most cases be implemented in Contracts to be let under the MOU". Reading MACP-01 tells you where a defence contract's clauses on intellectual property, quality assurance, security and third-party sales actually come from, not what your own compliance obligations are.

Why a Programme MOU exists

Traditional NATO practice negotiated an MOU phase by phase, which "has often led to time-consuming negotiations when it appeared during the programme that Participants had fundamentally differing assumptions as to how collaboration should have been performed". The Programme MOU concept answers this: it is signed at the earliest suitable opportunity and normally starts with the Feasibility Study phase, covering the programme "at least up to and including the Production phase". A PMOU does not remove the need to negotiate each phase's detail; it only makes renegotiating the basic overall arrangements unnecessary each time.

The 30-item checklist

Section III of MACP-01 lists everything an MOU or PMOU should consider: title page and classification, definitions, introduction, objectives and scope, government organisation, industrial organisation, report requirements, contractual relationship, work-sharing, cost-sharing, financial matters, taxes, contractual arrangements, transfers and exchanges, intellectual property, inspection and quality assurance, standardization/codification/configuration control, management of assets, insurance and indemnification, logistic support, sales and disposals, security and exchange of personnel, release of information and publicity, admission of additional participants, withdrawal and termination, settlement of disputes, amendment, the signature page, and annexes. Guidance and sample legal text follow for 26 of these in turn, and the drafter chooses only what applies to the programme in front of them: negotiators are told the items "are not all necessarily applicable" and can be addressed in a different order than the checklist itself.

Organisation, contracting and work-sharing

A programme can be run through a lead-nation model, an integrated model (an International Programme Office reporting to a Joint Steering Committee), or a fully decentralised model where national structures are left untouched. Contracts can be awarded centrally, by a Contracting Participant acting for everyone or by a NATO Agency, or on a decentralised basis where each Participant contracts for its own work-share. Work is allocated on criteria such as technical merit, cost, and encouragement of multinational industrial collaboration, and a work-share plan is normally approved by the Participants before it is implemented. Cost-sharing can follow equal shares, shares related to industrial benefit or output, or another agreed key.

Disclosure and use of technical information

This is the longest section of the document by a wide margin. It works through ownership of Foreground and Background Information, the rights of use Participants secure for Programme, Defence or Government Purposes, protection of information disclosed in confidence, licensing, and how inventions made under the MOU are handled. Before signing, Participants have to check that "their national disclosure policies and regulations allow disclosure of the [Technical] Information necessary for the execution of the MOU", because the resulting rights and obligations get written straight into the Contracts let under the MOU.

Quality assurance, and what MACP-01 does not cover

Section 13's sample provisions give two options. Where NATO arrangements apply, Participants implement STANAG 4107 (Mutual Acceptance of Government Quality Assurance) directly, and national quality assurance services follow whichever AQAP that STANAG 4108 assigns to the Contractor's work. Where NATO arrangements do not apply, quality control simply follows the host Participant's own national laws and procedures. MACP-01 does not itself specify which AQAP applies, what a quality manual has to contain, or how audits are scheduled; those decisions sit inside the STANAGs and AQAPs it points to, or inside the Contract the MOU produces. Similarly, the document does not set cost-sharing formulas, security classification levels, or export-licence policy; it only tells negotiators what questions each of those areas needs answered.

Duration, withdrawal and disputes

Withdrawal provisions are meant to be adapted to each phase of the programme, from Feasibility Study through Design and Development, Production and In-service Support. Disputes are resolved by consultation between the Participants rather than referred to a tribunal or third party, a principle the document repeats from its opening considerations. Public releases of programme information, such as notices of a Contract award, need co-ordinated approval so one Participant's announcement does not embarrass another.

Standards it references

• AACP-01Background
• AACP-02Background
• STANAG 4107Background