Management review that actually improves the business
Learn how to run an ISO 9001 Clause 9.3 management review that turns evidence into decisions, with the right inputs, actionable outputs, and a cadence that fits your risks.
STANAG 5516
STANAG 5516 tactical data exchange - Link 16
Makers and integrators of Link 16 terminals and of NATO ISR systems that store, stream or exchange Link 16 data.
STANAG 5516 is the NATO agreement on tactical data exchange over Link 16. NATO has not released it publicly; this page describes it from public NATO publications that cite it.
- Edition
- 9
- Published
- 2024-04-30
NATO has not released this STANAG publicly. It is NATO UNCLASSIFIED, and organisations that need it obtain it through their national standardization authority.
What it is
STANAG 5516 is the NATO agreement on tactical data exchange over Link 16. Edition 9, promulgated on 30 April 2024 under DPC, DPC, CaP1, TDL CaT, covers the publication ATDLP-5.16. NATO has not released STANAG 5516 publicly, so this page describes it from public NATO publications that cite it.
Where it is cited
AEDP-02 describes it in one passage: "STANAG 5516 provides guidelines on how to ensure interoperable use of Link 16 Tactical Data Links (TDLs) to disseminate information." It adds that "Link 16 employs the Joint Tactical Information Distribution System (JTIDS) and Multifunctional Information Distribution System (MIDS) data link terminals", and describes Link 16 itself as a frequency-hopping, jam-resistant, high capacity data link.
The other citations treat STANAG 5516 as the format of Link 16 data exchanged between NATO ISR systems. AEDP-05 notes that the NSIL_STREAM entity is enumerated to deliver products formatted as STANAG 4609 (video), STANAG 4607 (GMTI) and STANAG 5516 (TDL) over IP networks, with TDL carrying the NATO AGS Capability Testbed (NACT) header. AEDP-17 says Link 16 data will be made available as binary data files in accordance with STANAG 5516 with the addition of the NACT header, and cites STANAG 5516 as the specification for the activity (0 to 127) and platform (0 to 63) numbers that together define the identity of a track. AEDP-18 requires that downloaded Link 16 stream data "MUST consist of STANAG 5516 formatted binary data containing all messages in the time range satisfying the query", that each message include a NACT header, and that there be no padding bytes between messages.
These publications cite older editions (AEDP-12 Edition 8, AEDP-17 and AEDP-18 Edition 4). AEDP-18 also points to a MAJIIC2 Link 16 implementation guide, DOP-MAJIIC-068, which can be requested from the STANAG 4559 Custodian.
How we help
A supplier bound by STANAG 5516 through a contract holds the obtained text through its national authority. In ComplyTrain you record the requirements that apply to you as your own requirements, give each an owner, and keep the evidence that shows you meet them against each one.
Request access to this standard
Tell us how you need to work with STANAG 5516 and what you need from it. We will come back to you about what ComplyTrain can do.
Thank you. Your list is on its way to your inbox, and we will come back to you on what working with these standards in ComplyTrain involves, usually within one business day.
What ComplyTrain does
One system for the whole compliance programme. Start with the module you need most.
Forms & Follow-up
Collect information the same way every time, and decide in advance what happens next.
Controls & Assurance
Know whether your controls are operating, not just whether a policy says they exist.
Project Planner
Turn the compliance work you already know about into a plan with owners, dependencies and dates.
Product Compliance
Know what you can offer, and hold the evidence behind every configuration you offer it in.
Reporting & Analytics
Eight built-in reports across every module, scheduled, delivered, and filed where the evidence lives.
Media Monitoring
The sector news that matters to your organisation - read and rated by AI, and delivered as a scheduled digest in your own language.
Grants & Tenders
AI reads the tender pack and pulls out the requirements, deadlines and rules - then helps you draft the response from your own approved content, with you reviewing every step.
Stakeholder/Vendor Management
One current register of the suppliers and partners you depend on - each risk-assessed, re-assessing itself on schedule, and wired straight into your risk register.
Requirements Management
See every requirement you face - across every standard, plus your own contracts and policies - traced to the documents, evidence and processes that satisfy it.
Risk Management
Identify, score, treat and review your risks in one place - with AI to help anyone run a proper assessment, and a defensible trail behind every decision.
Training Management
Assign training, prove it was understood, and hold the competence records an auditor asks for.
Document Control
Draft compliance documents with AI, keep every version under control, and export them beautifully branded - all in one place.
Quality Management
Audits, corrective actions, processes and approvals in one quality system, organised around ISO 9001.
Latest from ComplyTrain
ISO 9001 audit: what happens, stage by stage
The types of ISO 9001 audit, what Stage 1 and Stage 2 each check, how nonconformities are graded and closed, and how to prepare for your first certification.
Three partners, three Member States, one evidence base
The EDF consortium rule is usually quoted as three entities from three Member States. It has a second limb about control that the word independent quietly hides, and two exceptions that disapply it entirely.
Other standards in Communication and information systems
- AComP-5639AComP-5639 protected core networking static environment specifications
- AComP-5640AComP-5640 protected core networking deployable specifications
- ADatP-4774ADatP-4774 confidentiality metadata label syntax
- ADatP-4778ADatP-4778 metadata binding mechanism
- ADatP-5636ADatP-5636 NATO Core Metadata Specification
- ADatP-5644ADatP-5644 web services messaging profile