MODUK DEF STAN 21-88: PART 1 PDF

Purpose

The purpose of Def Stan 21-88 is to promulgate system integration policies to be followed for functional integration activities at every stage in a platform or system's lifecycle. The term ‘system' can refer to a single equipment or group of equipment procured within a system boundary. It includes the traditional combat system and mission system1 equipment and equipment on platforms satisfying a less direct war fighting role. The boundary of what is included will differ from platform to platform. Traditionally it has been focussed on weapons, sensors and command and control stopping at the tactical data links communications. Increasingly it includes all communications systems both on and off platform plus platform management systems.

The policies and procedures described in this Def Stan are intended to be scaleable. They can be applied to a single system or a whole platform where the platform or combat/mission system can be large or small. They are also aimed to be procurement and architecture independent and any references to networks are for clarity and do not imply a design solution.

A platform or network will have its own specific roles and responsibility matrix detailing the roles in both organisation and contractual terms. To align with the Maritime Combat System (MCS) organisation the term Platform Approval/Technical Authority is used as the umbrella term to include all platform, network, combat system, design and integration authority roles. Generally the Platform Approval Authority is a Ministry of Defence (MoD) role and the Platform Technical Authority is an Industry role. The work undertaken and the authority held by each organisation will be platform specific and determined at the outset of a programme.

This issue 4 of the Def Stan 21-88 is a completely new issue aimed at addressing the wider integration needs of future platforms as well as reflect the policies in current use in legacy platforms. Previous issues of Def Stan 21-88 are called up and will continue to be used in system contracts pertaining to legacy systems and platforms.