STANAG 2592
STANAG 2592 NATO geospatial information framework (NGIF)
Defence and NATO-affiliated organisations working to a contract or tender that invokes STANAG 2592 or the AGeoP-11 publication it covers
STANAG 2592 is NATO's ratification agreement committing member nations to implement AGeoP-11 Edition B, the NATO Geospatial Information Framework (NGIF).
- Edition
- 2
- Published
- 2018-10-22
What it is
STANAG 2592 is the NATO Standardization Agreement covering the NATO Geospatial Information Framework (NGIF). This is Edition 2, promulgated 22 October 2018, superseding STANAG 2592 Edition 1.
A STANAG is not the specification
A STANAG is the agreement by which NATO nations commit to implement a standard, not the technical specification itself. STANAG 2592's own text is short and administrative: an aim, an interoperability rationale, and the ratification and reporting machinery. Participating nations "agree to implement the following standard", and the standard named is "AGeoP-11, Edition B" - the publication that actually sets out NGIF's technical content. Anyone working directly with NGIF's data schemas and products needs AGeoP-11's own text, not this cover agreement.
What it commits nations to
The stated aim is to respond to NGIF's interoperability requirements. NGIF "supports the requirement to 'operate off the same map'" set out in NATO Geospatial Policy, MC 0296/3, and it addresses gaps identified in the NATO Geospatial Deficiencies Matrix. It is meant to provide "a coherent set of digital and printed geospatial products for all users", covering operational domains "from the strategic to the tactical levels, across all staff branches", and is designed as "a generic solution to be used by all NATO services and organizations and the force elements of troop-contributing nations".
Who it binds, and how
STANAG 2592 binds nations, not suppliers. It becomes binding through ratification, "as reflected in the NATO Standardization Document Database (NSDD)", and it is "effective upon receipt" for the implementing nations and NATO bodies; partner nations are separately "invited to adopt" it. Implementation is judged complete when the NCS, NFS and the nations concerned have enacted the NGIF artifacts AGeoP-11 references "in their deployed systems and production capabilities", and nations report their ratification, implementation and adoption details to the NSO "in accordance with AAP-03". The STANAG is reviewed at least once every five years, with the outcome recorded in the NSDD.
How it's evaluated
STANAG 2592 describes no certification scheme and no third-party audit. What it describes is nations reporting their ratification and implementation status to NATO, recorded in the NSDD; nobody is "STANAG 2592 certified", and the document never uses that language. Where a contractor's geospatial work does get checked against AGeoP-11's own requirements, the assessor and the evidence required are set by the contract's own quality clause, not by this STANAG.
Standards it references
STANAG 2592 covers AGeoP-11, the Allied Geospatial Publication that carries NGIF's actual technical content. Its "Other Related Documents" also list STANAG 2586, which covers AGeoP-08 (the NATO Geospatial Metadata Profile), and STANAG 2211, which covers AGeoP-21 (geodetic datums, projections, grids and grid references). Nations report their ratification, implementation and adoption of STANAG 2592 under AAP-03.
How we help
STANAG 2592 and the NGIF framework it brings into force are implemented in national geospatial production and systems work, not in a compliance platform: enacting AGeoP-11's artifacts in a deployed system is geospatial engineering work, carried out by specialists against the publication itself.
What ComplyTrain does for that kind of work in general is give an organisation one auditable place to hold the procedures, training records and evidence trail - non-conformances, corrective actions, document control - that a customer's quality representative or a government surveillance visit will ask to see once a contract invokes AGeoP-11 or NGIF.
ComplyTrain does not build, enact or operate a geospatial information framework, and it cannot determine whether a nation's or a contractor's systems meet AGeoP-11's technical characteristics. That work is set by the contract and the customer's quality clause, not by us. Browse the explorer to see what sits alongside STANAG 2592 and AGeoP-11, and talk to us about the evidence trail once you know which ones are in your contract.
Standards it references
- STANAG 2586Background
- AGeoP-08Background
- STANAG 2211Background
- AGeoP-21Background
Questions
Is STANAG 2592 mandatory?
Only for nations that have ratified it, and it reaches a contractor only where a contract or tender invokes AGeoP-11 or NGIF by name. The STANAG itself binds nations, not suppliers, and sets no date reaching a supplier directly.
What is the difference between STANAG 2592 and AGeoP-11?
STANAG 2592 is the NATO ratification agreement; AGeoP-11 Edition B is the publication that actually sets out the NATO Geospatial Information Framework. Ratifying STANAG 2592 is how a nation commits to implement AGeoP-11.
Can a company be certified to STANAG 2592?
No. STANAG 2592 describes nations ratifying and reporting implementation to NATO, recorded in the NATO Standardization Document Database. It describes no certification or audit scheme for a supplier or a product.
What changed between Edition 1 and Edition 2 of STANAG 2592?
The document states that this edition supersedes STANAG 2592 Edition 1, but it does not itself describe what changed between the two editions, and it does not print a date for the earlier edition.
Who is the custodian of STANAG 2592?
The cover names Germany, through Bundeswehr Geoinformation, as the custodian, and the Military Committee Joint Standardization Board's Joint Geospatial Standards working group as the tasking authority supervising the STANAG.