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 4683
STANAG 4683 NATO technical sharable software (NTSS)
Contractors and NATO member-state agencies that develop, share or use NATO's shared ballistics software (NTSS) under AOP-61.
STANAG 4683 sets out how NATO's Technical Sharable Software (NTSS) for ballistic characteristics is developed, shared and used, covered by AOP-61. NATO has not released it publicly; this page describes it from the Czech defence standard that implements it.
- Edition
- 1
- Published
- 2009-09-08
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 4683 is the NATO Standardization Agreement on NATO Technical Sharable Software (NTSS). Edition 1, promulgated on 8 September 2009 under the sponsorship of CNAD, AC/225 NAAG, ICGIF, it covers the publication AOP-61.
NATO has not released STANAG 4683 publicly, so this page describes it from a public national implementation, the Czech defence standard ČOS 051661 (1st edition), which states that it introduces STANAG 4683 edition 1 into Czech use. A national implementation can add national requirements, so treat what follows as the Czech implementation's content, not as NATO's own text.
What the Czech implementation covers
ČOS 051661 describes NTSS as a set of software products designed for applications dealing with technical ballistics. Each NTSS product implements technology found in one or more STANAGs within the remit of NAAG Land Capability Group 3 (LCG-3), Sub-group 2, and the standard gives interior ballistics, exterior ballistics, firing-table generation and 6/7-degree-of-freedom trajectory simulation as example NTSS product areas.
The standard names related documents that NTSS technology draws on: STANAG 4119 (adoption of standard cannon artillery firing table format), STANAG 4355 (the modified point mass and five degrees of freedom trajectory models), STANAG 4367 (thermodynamic interior ballistic model with global parameters), STANAG 4400 (derivation of thermochemical values for interior ballistic calculation), STANAG 4618 (six/seven degrees of freedom guided projectile trajectory model) and STANAG 4655 (an engineering model to estimate aerodynamic coefficients), alongside AOP-61 itself.
Participating nations are responsible for developing and maintaining NTSS software through an NTSS configuration manager, who informs known users of updates, and an AOP is developed and kept current, defining the structure, technology and procedures for each NTSS product area. Any NATO government may hold NTSS software and documentation; sharing of databases is a decision for each NATO government and is granted only against a justified request. A nation that modifies NTSS software for its own needs must report the change to NAAG LCG/3 SG/2 so the standardised baseline stays aligned.
What the Czech implementation requires
ČOS 051661 sets a security marking for every element of NTSS. Source code is marked and handled as NATO RESTRICTED on any medium, and a member state that incorporates NTSS source code into a national application must protect the resulting source code at no less than that level. Object code carrying no debugging information is NATO/PfP UNCLASSIFIED; object code that does carry debugging information is NATO RESTRICTED. Executable code and NTSS documentation are both NATO/PfP UNCLASSIFIED, as are external database files, unless they are embedded in object or executable code, in which case they take that code's marking.
Release is controlled too. A participating state may give NTSS software to another NATO member government without other participating states' prior consent; release to a non-member government, or to a contractor, is subject to further conditions and approval. Any resulting agreement must forbid onward distribution of NTSS technology, information or code without official written authorisation from the responsible government, and must forbid reverse engineering to recover source or object code from executable or object code.
How we help
A supplier bound by STANAG 4683 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 4683 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 Land armaments
- AEP-3.12.1.5AEP-3.12.1.5 military load classification of bridges, ferries, rafts and vehicles
- AEP-64AEP-64 paint systems resistant to chemical agents and decontaminants
- AEP-65AEP-65 test method for paint systems resistant to chemical agents
- AEP-94AEP-94 skin penetration assessment for non-lethal projectiles
- AEP-97AEP-97 multi-calibre manual of proof and inspection for NATO small arms ammunition
- AEP-98AEP-98 precision assessment of non-lethal kinetic energy weapons and ammunition