Already an Engineering360 user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your Engineering360 Experience

Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.


Generic Soldier Architecture Part 0: Approach

active, Most Current
Buy Now
Organization: MODUK
Publication Date: 28 October 2020
Status: active
Page Count: 36

The overarching scope for this Defence Standard as a whole, is applicable to the range of DCC Soldiers within a Company Group; this includes members of a Fire Team, Section, Platoon and individual Company (which includes a Company Headquarters). Typically, these are Riflemen and Commanders, but the overarching interface requirements and on-the-soldier equipment needs to provide a modular approach to cater for a full range of DCC activities. The requirements for these roles are determined by the operational situation at the time and the application of this Defence Standard will ensure that any equipment is fit for a range of operational requirements, now and in the future. Activities of the DCC soldier also include mounted transit activities, and so integration to platforms needs to be considered to enable the ISS to operate effectively. Due to the diversity of soldier roles, it is anticipated that some specialist roles will not be within scope.

DCC poses a unique challenge in both physical and cognitive demands of the task and environment. Operational requirements of the DCC soldier include: Move, Fight, Communicate, Survive, Plan, Sense and Sustain (FIST Handbook, 2004). As per the "Strategic Trends Programme: Future Operating Environment 2035" publication, the changing character of conflict, extreme environmental conditions, and proliferation of systems with which the soldier must interact complicates these tasks further. Integration of the Head, Torso and Weapon sub-systems is essential for efficient transitions between equipment, platforms and bases.

The GSA Architecture considers requirements for the Joint Forces, Maritime and Air domains to achieve potential future Tri-service and wider NATO compatibility, further driving economies of scale and effective allied campaigns.

This Defence Standard sits alongside the Generic Vehicle Architecture (GVA) and Generic Base Architecture (GBA) as LOSA Defence Standards and contains references to other Defence and Commercial Standards that are considered the authority in their topics. This Defence Standard also requires compliance with several MoD procedures where indicated in the text. This enables commonisation of requirements and allows gained efficiencies in reduction of duplication.

The ISS logical architecture is partitioned into three areas, the Torso, Helmet and Weapon, where the power and data infrastructure and interface requirements have been specified. This nomenclature is for logical description of the likely zones of sub-systems, however this Standard does not restrict designers into physical locations on the soldier. These should be agreed with the project teams when agreeing the logical solution architecture for soldier equipment. The ISS Example Logical Architecture is shown schematically in Figure 6 in Part 0, representing a high-level view of the ISS.

In terms of scope GSA covers physical interfaces, power and data exchange between: -

• All equipment attached to the soldier torso, weapon and helmet sub-systems

• All sub-systems i.e. torso and weapon, torso and helmet and weapon and helmet

• The soldier when embarked in a platform and platform infrastructure

• The soldier in the base and the base infrastructure

The following list of soldier roles is indicative, and may change in future revisions with learning from Delivery Projects. Generally, GSA users can be described as Standard (D), Enhanced (D+) and Advanced (D++). Examples of roles which may fit into these categories are: -

Standard Users (D) require the minimum level of SWPD to receive orders within a Section/Fire team: -

• Rifleman (including Underslung Grenade Launcher (UGL))

• Gunner (General Purpose Machine Gun (GPMG))

• Sharpshooter

• Enhanced Users (D+) require more functionality to assess the operational picture and command the teams: -

• Fire Team Commander

• Section Commander

• Platoon Commander and 2nd in Command (2iC)

• Support Weapons Operator (including machine gun, grenade launcher - Grenade Machine Gun (GMG), etc.)

• Combat medic

• Communication specialist (including Signals)

• Advanced Users (D++) require specialist functionality to support their roles: -

▪ Commanders with added operational needs

• Senior Commander

• Company Commander and 2iC

• Joint Terminal Attack Controller (JTAC)

• Other support roles that could be a mix of user levels: -

• Fire Support Team (FST) - from the Royal Artillery / Mortar Fire Controller (MFC) from the Mortar Platoon

• Sniper

• Anti-tank Platoon Commander

• Assault Pioneer

• Royal Military Police (RMP)

• Dog handler

• Combat Engineers

• Reconnaissance

The current scope of the soldier architecture and this Defence Standard does not cover the following: -

• Requirements for detailed internal sub-system design

• Long range, Radio Frequency, Spectrum dependent systems

• Equipment with a greater power and data requirement than the ISS can provide (could be connected at a lower functionality)

• Specific locations for sub-systems on the soldier, other than the Torso, Helmet and Weapon, such as the Bergen/Rucksack

• Extremely specialised dismounted soldier roles.

Document History

DEF STAN 23-012: PART 0
October 28, 2020
Generic Soldier Architecture Part 0: Approach
The overarching scope for this Defence Standard as a whole, is applicable to the range of DCC Soldiers within a Company Group; this includes members of a Fire Team, Section, Platoon and individual...