You are on page 1of 64

Ministry of Defence Defence Standard 02-8 (NES 8)

Issue 1 Publication Date 01 April 2000

Guide For The Preparation Of Statements Of Technical Requirements For The Development Of Systems And Equipment

Incorporating NES 8
Issue 2 Publication Date June 1986

AMENDMENT RECORD Amd No Date Text Affected Signature and Date

REVISION NOTE This standard is raised to Issue 1 to update its content. HISTORICAL RECORD This standard supersedes the following: Naval Engineering Standard (NES) 8 Issue 2 dated June 1986.

Ministry of Defence

Naval Engineering Standard

NES 8

Issue 2 (Reformatted)

June 1986

GUIDE FOR THE PREPARATION OF STATEMENTS OF TECHNICAL REQUIREMENTS FOR THE DEVELOPMENT OF SYSTEMS AND EQUIPMENT

This NES Supersedes NES 8 ISSUE 1

Record of Amendments
AMDT 1 2 3 4 5 6 7 8 9 10 INSERTED BY DATE

NAVAL ENGINEERING STANDARD 8

ISSUE 2 (REFORMATTED) GUIDE TO THE PREPARATION OF STATEMENTS OF TECHNICAL REQUIREMENTS FOR THE DEVELOPMENT OF SYSTEMS AND EQUIPMENT

The issue and use of this Standard is authorized for use in MOD contracts by MOD(PE) Sea Systems and the Naval Support Command

ECROWN COPYRIGHT Published by: Director of Naval Architecture Procurement Executive, Ministry of Defence Foxhill, Bath BA1 5AB
i

ii

NES 8 Issue 2 (Reformatted)

SCOPE
1. This NES is a guide to marshalling the technical requirements that need to be included in an STR. It sets a preferred format, typographical and publishing style. It contains an AnnexGuide to the Content of an STR for a system or equipment. This NES does not give guidance on: a.the procedures to be followed for the development of platform systems and equipment: b.the preparation of: (a) Procurement Specifications for development (that embody an STR) contractually enforced by a Development Contract, or Procurement Specifications for manufacture (that embody a Configuration Definition) contractually enforced by a Production Contract.

2. 3.

(1)

4.

This NES is generally compatible with the requirements of Annex B. Chapter 4 of the Compendium of Guidelines for Project Management published by MOD(PE)/DPPI(PM).

iii

NES 8 Issue 2 (Reformatted)

iv

NES 8 Issue 2 (Reformatted)

FOREWORD Sponsorship
1. This Naval Engineering Standard (NES) is sponsored by the Procurement Executive, Ministry of Defence, Sea Systems. The policies and procedures for the design, or control of the design, for all Sea Systems Controllerate (SSC) sponsored vessels, their machinery, systems and equipment require the Design Sponsor to specify the technical requirements of the task to be undertaken in development in a Statement of Technical Requirements (STR). This STR forms the kernel to the Procurement Specification that states all the requirements to be imposed on a contractor. The Procurement Specification is the basis of a contract that the Director of Contracts negotiates with the Contractor. This NES is to be used as required by SSC Design Sponsors, their agents and contractors, as a guide to those required to prepare an STR to specify a package of work to be undertaken in the development of a design of a vessel, its machinery, systems, equipment and material. It interprets the substance, and supplants the use of DEF STAN 0528NATO Guide to the Preparation of Specifications for the Procurement of Defence Materiel. If it is found to be unsuitable for any particular requirement the MOD(PE) is to be informed in writing of the circumstances. Any user of this NES either within MOD or in industry may propose an amendment to it. Proposals for amendments that are not directly applicable to a particular contract are to be made to the MOD and those directly applicable to a particular contract are to be dealt with using existing procedures or as specified in the contract. No alteration is to be made to this NES except by the issue of an authorized amendment. Unless otherwise stated, reference in this NES to approval, approved, authorized or similar terms, means by the Ministry of Defence in writing. Any significant amendments that may be made to this NES at a later date will be indicated by a vertical side line. Deletions will be indicated by 000 appearing at the end of the line interval. Extracts from British Standards within this NES have been included with the permission of the British Standards Institution.

2.

3.

4.

5.

6.

7. 8.

9.

10.

Conditions of Release General


11. This Naval Engineering Standard (NES) has been prepared for the use of the Crown and of its contractors in the execution of contracts for the Crown. The Crown hereby excludes all liability (other than liability for death or personal injury) whatsoever and howsoever arising (including but without limitation, negligence on the part of the Crown, its servants or agents) for any loss or damage however caused where the NES is used for any other purpose. This document is Crown Copyright and the information herein may be subject to Crown or third party rights. It is not to be released, reproduced or published without written permission of the MOD.
v

12.

NES 8 Issue 2 (Reformatted)

13.

The Crown reserves the right to amend or modify the contents of this NES without consulting or informing any holder.

MOD Tender or Contract Process


14. This NES is the property of the Crown and unless otherwise authorized in writing by the MOD must be returned on completion of the contract, or submission of the tender, in connection with which it is issued. When this NES is used in connection with a MOD tender or contract, the user is to ensure that he is in possession of the appropriate version of each document, including related documents, relevant to each particular tender or contract. Enquiries in this connection may be made of the local MOD(PE) Quality Assurance Representative or the Authority named in the tender or contract. When NES are incorporated into MOD contracts, users are responsible for their correct application and for complying with contracts and any other statutory requirements. Compliance with an NES does not of itself confer immunity from legal obligations.

15.

16.

Related Documents
17. In the tender and procurement processes the related documents listed in each section and Annex A can be obtained as follows: (a) British Standards British Standards Institution, 389 Chiswick High Road, London W4 4AL Directorate of Standardization and Safety Policy, Stan 1, Kentigern House, 65 Brown Street, Glasgow G2 8EX CSE3a, CSE Llangennech, Llannelli, Dyfed SA14 8YP Tender or Contract Sponsor to advise.

(b)

Defence Standards

(c)

Naval Engineering Standards

(d)

Other documents

Note: Tender or Contract Sponsor can advise in cases of difficulty. 18. All applications to Ministry Establishments for related documents are to quote the relevant MOD Invitation to Tender or Contract Number and date, together with the sponsoring Directorate and the Tender or Contract Sponsor. Prime Contractors are responsible for supplying their subcontractors with relevant documentation, including specifications, standards and drawings.

19.

Health and Safety Warning


20. This NES may call for the use of processes, substances and/or procedures that may be injurious to health if adequate precautions are not taken. It refers only to technical suitability and in no way absolves either the supplier or the user from statutory obligations relating to health and safety at any stage of manufacture or use. Where attention is drawn to hazards, those quoted may not necessarily be exhaustive.
vi

NES 8 Issue 2 (Reformatted)

CONTENTS
Page No TITLE PAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FOREWORD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sponsorship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conditions of Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MOD Tender or Contract Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Health and Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONTENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SECTION 1. 1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 1.9 1.10 SECTION 2. 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 SECTION 3. 3.1 3.2 3.3 3.4 CHARACTERISTICS OF A STATEMENT OF TECHNICAL REQUIREMENTS . . . . . . . . . . . . . . What it is . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . When an STR is required . . . . . . . . . . . . . . . . . . . . . To whom it is addressed . . . . . . . . . . . . . . . . . . . . . . . What it can cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . What it is to cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . Clarity of Specification . . . . . . . . . . . . . . . . . . . . . . . Purpose of this NES . . . . . . . . . . . . . . . . . . . . . . . . . . Alternative Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mandatory Features . . . . . . . . . . . . . . . . . . . . . . . . . . Responsibility and Accountability . . . . . . . . . . . . . . SCOPE OF A STATEMENT OF TECHNICAL REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . Accountability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Interactions between Development (of a Design) and Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Depth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Usage of Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Basic Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Usage of Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . Health & Safety at Work . . . . . . . . . . . . . . . . . . . . . . ARRANGEMENT AND CONTENT . . . . . . . . . . . . Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Colour . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vii

i iii v v v v vi vi vi vi vii 1.1 1.1 1.1 1.1 1.1 1.1 1.2 1.2 1.2 1.2 1.3 2.1 2.1 2.1 2.2 2.2 2.2 2.2 2.3 2.3 2.5 3.1 3.1 3.1 3.2 3.2

NES 8 Issue 2 (Reformatted)

3.5 3.6 SECTION 4. 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 4.15 4.16 4.17 4.18 4.19 4.20 4.21 4.22 4.23 4.24 4.25 ANNEX ANNEX ANNEX A. B. C.

Conditions of Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EDITORIAL, TYPOGRAPHICAL AND PRINTING STYLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Guidance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trade Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Page numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Section, Paragraph and Sub-paragraph numbering Additions and deletions . . . . . . . . . . . . . . . . . . . . . . . Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drawings and Figures . . . . . . . . . . . . . . . . . . . . . . . . Tables and Equations . . . . . . . . . . . . . . . . . . . . . . . . . Typographic Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use of Capital Letters . . . . . . . . . . . . . . . . . . . . . . . . . Hyphens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Use of Solidus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Presentation of Numbers . . . . . . . . . . . . . . . . . . . . . . Component Reference . . . . . . . . . . . . . . . . . . . . . . . . Spelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Classification Markings . . . . . . . . . . . . . . . . . . . . . . . Paper Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Punching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RELATED DOCUMENTS . . . . . . . . . . . . . . . . . . . . DEFINITIONS AND ABBREVIATIONS . . . . . . . .

3.2 3.3 4.1 4.1 4.1 4.1 4.1 4.1 4.1 4.1 4.1 4.2 4.2 4.2 4.2 4.2 4.2 4.3 4.3 4.3 4.4 4.4 4.4 4.4 4.4 4.4 4.4 4.5 A.1 B.1

GUIDE TO THE ARRANGEMENT AND CONTENT OF A STATEMENT OF TECHNICAL REQUIREMENTS FOR THE DEVELOPMENT OF A SYSTEM OR EQUIPMENT . . . . . . . . . . . . . . . . . C.1

viii

NES 8 Issue 2 (Reformatted)

1.
1.1

CHARACTERISTICS OF A STATEMENT OF TECHNICAL REQUIREMENTS What it is


a.

An STR is the description of a job or package of work connected with the development of a design of a vessel, its machinery, systems or equipment (materiel) which has to be contracted to someone else. It is a form of specification in that it is required to convey the intent of one person to another in such a way that there is never any doubt as to the meaning of each and every individual requirement.

1.2

When an STR is required


a.

An STR is required only when a development task has to be specified. The final outcome of development is the availability of the minimum package of manufacturing drawings and documentation, including a production test specification, collectively termed the Configuration Definition. This defines unambiguously the system or equipment to be manufactured in sufficient detail to ensure that the design intent is met and is preserved in all future production, and that both functional and mechanical interchangeability are assured. Thus an STR is always required when it is not possible to state a Configuration Definition.

b.

1.3

To whom it is addressed
a.

An STR need not be universally understood, but it is a requirement that it should be understood by those who practise the design and skills associated with the development of the job specified, especially the Contractor.

1.4

What it can cover


a.

An STR can describe any development task associated with total vessel design but the extent of a task covered by a single STR should be limited to that which can be readily managed. Development of a large project may need to be divided into sequential steps such as Feasibility Study, Project Definition etc or materiel divisions such as Systems, Equipment, etc and a separate STR may need to be prepared for each step or materiel division. For the purpose of this NES the development of the design of a total vessel and its machinery is regarded as the deliberate integration of a number of separate systems and equipment thus the STR for the design of a vessel identifies a unique collection of inter-related STRs. For each separate package of development work the STR is to clearly define the limits of the task and the inter-relationships with, and the inter-dependencies on, other associated tasks.

b.

c.

1.5

What it is to cover
a.

Whether simple or familiar, complex or unique, and however accustomed to SSC practices the contractor may be, the job description specified in an STR is to leave nothing unspecified. Although an STR should specify all the requirements, it may be necessary during the development of the design, (especially in cases where a close relationship exists with the contractor or designer either directly or by way of the Overseer or Quality Assurance Representative), to amend the STR either
1.1

b.

NES 8 Issue 2 (Reformatted)

for omissions, or to permit the adoption of a more costeffective solution or both. Only the Design Sponsor may authorize such amendments.
c.

The product resulting from the application of an STR cannot be rejected due to failure to satisfy an assumed or unstated requirement.

1.6

Clarity of Specification a.

The contents of STRs are to be quantified in understandable and realistic terms needing no further interpretation. For example, in specifying equipment to withstand shock, the actual figures to which the equipment will be shock tested are to be specified together with the preferred method of mounting; not by quoting references by which the contractor can, with experience or education, deduce or extrapolate information. Expressions such as hot gases, or cold conditions, are to be avoided and realistic temperatures with limits stated. Reference to Standards, including Naval Engineering Standards, should be specific and clear, not in a blanket form open to doubt and misinterpretation.

b.

1.7

Purpose of this NES


a.

The complexity of vessels and the intricate interrelationships between numerous systems, equipment and the environment make it necessary to have a discipline in the preparation of STRs to assist in the:
(1)

marshalling and selection of those technical requirements to be included in the content of an STR which when implemented, produce materiel which is adequate without being elaborate, which is cost-effective, and is fit for purpose. presentation of the information in format, typographical and printing style to promote uniformity and thereby make use of STRs as easy as possible.

(2)

b.

The purpose of this NES is to stimulate identification of those aspects and features that need to be considered when preparing an STR, and to set down a preferred style including a few mandatory requirements as defined in Clause 1.9.a.

1.8

Alternative Style
a.

If a style already exists which is acceptable to a contractor for specifying a task in the development of a design that embodies the essential content as defined herein, the Design Sponsor is at liberty to adopt that style.

1.9

Mandatory Features
a.

Whatever style is used for the document which specifies the task to be undertaken in a development of a design it is to be called a Statement of Technical Requirements and is to include a number of mandatory features including:
(1) (2) (3) (4)

a front cover with unique reference number, security and privacy identifications etc as specified herein. an authorization page to be signed by the Design Sponsor. a list of all mandatory documents and drawings. other mandatory features as given in the text of this NES.
1.2

NES 8 Issue 2 (Reformatted)

1.10

Responsibility and Accountability


a.

Design Sponsors are to bear in mind that every STR written by SSC personnel, is issued under the delegated authority of DCW and DCWE, who are accountable to the Controller of the Navy for the fitness for purpose of all SSC sponsored vessels, together with their machinery, systems and equipment.

1.3

NES 8 Issue 2 (Reformatted)

1.4

NES 8 Issue 2 (Reformatted)

2.
2.1

SCOPE OF A STATEMENT OF TECHNICAL REQUIREMENTS Accountability


a.

DCW and DCWE are accountable to the Controller of the Navy and are vested with the necessary design authority to make judgements and decisions on all matters of vessel and engineering design necessary to ensure that SSC sponsored vessels and their machinery, systems and equipment meet the appropriate requirements. DCW and DCWE delegate to their Directors and their Staff design authority and accountability for:
(1)

b.

the fitness for purpose of vessels, machinery, systems and equipment procured by the Controllerate. setting design standards for the Controllerate, and writing specifications for vessels machinery, systems and equipment, materials and processes.

(2)

c.

The documents by which SSC staff exercise design authority are:


(1)

Naval Engineering Standards which record the design standards that the SSC has established to be fit for purpose. Statements of Technical Requirements which specify the requirements to be satisfied to achieve fitness for purpose in the process of developing the design of vessels, machinery, systems and equipment (materiel).

(2)

2.2

Interactions between Development (of a Design) and Production


a.

Ideally Development precedes Production in that:


(1)

Development, (in the context of a vessel Development is termed Design) is initiated by defining requirements in the form of an STR and is concluded with the availability of a Configuration Definition. Production, (in the context of a vessel Production is termed Build), is initiated by defining the design in the form of a Configuration Definition and is completed with the availability of a product, ie materiel in the form of a vessel, machinery, system or equipment.

(2)

b.

In practice there are occasions when:


(1)

Development and Production are entirely separate and full scale manufacture cannot be authorized until Development has been completed by the approval and sealing of the Configuration Definition. although planned to be separate, Development and Production unavoidably overlap. by intent, Development and Production overlap, and are programmed as one combined process. the amount of Development is so insignificant that it is not contracted separately but is absorbed in the process of Production.

(2)

(3)

(4)

c.

Regardless of how Development and Production interact, or how small or extensive the Development task, it must always be separately identified and defined in an STR.
2.1

NES 8 Issue 2 (Reformatted)

d.

When only limited Development, to achieve fitness for purpose of existing MOD approved, commercial product, or foreign materiel is necessary, the STR need only cover the changes required. To exercise control over the Development of a new system or equipment, the total task may be broken down into manageable packages (involving possibly Concept Studies, Feasibility Studies, Project Definition, etc), and STRs prepared for each work package.

e.

2.3

Limitations
a.

An STR is not to contain matters such as responsibilities, ordering quantities, programme etc, which are to be included separately in a Procurement Specification of which the STR is an essential part; nor is it to contain conditions of contract, liabilities, etc. Such matters are to be included in the contract that enforces the Procurement Specification.

2.4

Depth
a.

The depth of technical stipulation in an STR can vary from a concise statement of the basic operational parameters through to virtually a complete written definition of the design. It may:
(1) (2) (3)

define only the characteristics required in the final product. also define design requirements. also define the quality assurance requirements that demonstrate fitness for purpose. also define or give guidance concerning the use of standard parts, processes, interfaces, techniques, features. in some cases, define mandatory methods of production, testing and process controls to achieve the required characteristics.

(4)

(5)

b.

An STR is to be so complete that the intent is clearly defined and not capable of being misunderstood, but it is not to include irrelevant or superfluous information, or stipulations that do not contribute to the primary intent of the development.

2.5

Form
a.

An STR can be totally descriptive or descriptive and pictorial. The descriptive matter can include tables, formulae etc and the pictorial matter can be conventional design drawings, diagrams of all types, graphs, flow and operational charts, etc, provided all conventions and symbols are beyond misinterpretation and the package of information conveys the totality of the specification.

2.6

Usage of Reports
a.

In cases where development of a design is to be progressed as a result of a Technical Report (eg as the result of a development task in a staged development programme, or of a Defect Report) then such a Report can be embodied into and used as the basis of an STR provided that it is qualified and augmented to fulfil Clause 2.4.b.
2.2

NES 8 Issue 2 (Reformatted)

2.7

Basic Principles
a.

When preparing an STR the basic principles are that it is to:


(1) (2)

be adequate for the intent and no more. be clear and unambiguous and not embody preconceived ideas that could inhibit the development of a solution. stipulate essential requirements. technical requirements including interface

(3)

(4)

be realistic in that requirements must always take into account both the operating implications and cost of material and be so stipulated that they may be complied with and verified in an economic and practical way. make as much use of existing specifications and designs as possible. be contractually enforceable.

(5) (6) 2.8

Usage of Standards
a.

It is Government policy for Government Departments to contribute to and make maximum use of British Standards. If no suitable British Standard exists service interests may be covered by a Defence Standard which may be either general or, in some cases, applicable to only one Controllerate. The SSC may produce an NES if no suitable British Standard or Defence Standard exists. NES are a coherent series of Standards. Their purpose is to provide the basic technical documentation recording the knowledge and needs that are an essential foundation for the procurement and upkeep of Naval Ships, Ship Systems and Equipment and Weapon Systems and Equipment. Their aim is to:
(1)

b.

provide a reference standard for the preparation of documentation associated with initial procurement, in service support, refitting and modernization. record proven design and materiel practices suitable for future use without anomaly or undue duplication. record lessons learned during development and inservice for future guidance. take account of International, National and Commercial Standards; in particular NATO Standardization Agreements (STANAGs), ABCA Navy Standardization Agreements (NAVSTAGs), British Standards (BS), and Defence Standards (DEF STANs). take account of changes in technology and of experience gained in MOD Naval Service and in industry.

(2)

(3)

(4)

(5)

c.

In drawing up an STR the Design Sponsor must make maximum use of Standards and must not cause to be developed any material, process, technique, component, item, equipment or system for which a suitable product or suitable Standard already exists. NES 2 gives a complete index to Naval Engineering Standards, and includes a number of indexes which facilitate identification of and access to all the subject matter in NES and in other selected Standards.
2.3

d.

NES 8 Issue 2 (Reformatted)

e.

Standards must be used in a way which provides a costeffective solution. Referencing and quoting the Standard in an STR not only implies that the Standard is deemed to be adequate and technically suitable for the purpose, but also that the cost of implementing the Standard is acceptable within the expenditure allocated to the product. Standards must not be applied in a way which inhibits innovation. The extent to which Standards are quoted in an STR is dependent on the nature and purpose of the development. The depth of the precise stipulation may vary from merely quoting a Standard in its entirety, to foster an awareness of the scope of such a Standard and the fact that its requirements need to be taken into consideration, to the extreme where a particular requirement of a Standard is to be a mandatory requirement of the STR. In cases where it is desirable for the STR to implement a Standard, and the extent of the information to be used is insignificant when compared with the whole Standard, then it is permitted to extract and repeat the information in an STR and quote the source reference, provided that in such cases no further need is seen for the Standard in the STR. It need not then be quoted as a reference document for the STR. When it is a mandatory requirement to observe an existing Standard, in whole or in part (Clause 2.8.g.) and the full text that is to be observed is not included verbatim in the STR (Clause 2.8.h.) the precise identity of the Standard is to be included in the text of the STR and also listed as a mandatory reference in the Introduction to the STR. Particular care is to be taken when referencing NES because there are few NES that can be quoted without qualification. Many NES contain proposed ways of satisfying requirements when such are stated to be necessary. For instance, NES 627, Requirements for General Application to Rotating Electrical Machinery, includes design practices and techniques for satisfying diverse features of all types and sizes of rotating machines; no one machine can possibly have all the features, and the STR must qualify the NES. The same applies to NES 302, Maintenance Envelopes and Removal Routes, NES 322, Oil PollutionPrevention, NES 102, NES 122, NES 701 and many others. NES 743 Part 1, Bending of Pipes, and NES 156 Part 2, Wood DeckingCaulking Compound, are examples of NES that can be applied without qualification; but even in such cases the Design Sponsor is to ensure that this is confirmed, both in terms of technical requirements and cost of implementation. Many NES carry Check Lists that refer to Clauses in the NES whose applicability to the particular application needs to be determined, or which may require amplification or qualification such as those providing options. Where such an NES is referenced in an STR, the response to the Check List is to be included in the text of the STR and the completed Check List included as an Annex to the STR. In cases where the Design Sponsor knowingly departs from the requirements given in an NES, he must seek the approval of the Sponsor of the NES in accordance with NES 0. In cases where the Design Sponsor and NES Sponsor agree to the specification of a new requirement, such a requirement is to be
2.4

f. g.

h.

i.

j.

k.

l.

m.

n.

NES 8 Issue 2 (Reformatted)

included in the STR and subsequently incorporated in the NES. In cases where the NES Sponsor does not support the proposals of the Design Sponsor, the Design Sponsor is, through his Line Management, to accept responsibility for the departure from the NES.
2.9

Health & Safety at Work


a.

Under the Health & Safety at Work Act 1974, the MOD and its personnel have responsibilities as designers, manufacturers, importers, suppliers, erectors, installers, stockholders and issuers of stores. For the purpose of the Act:
(1)

Work means work as an employed person. The person employed is deemed to include all persons who may during the course of employment, come into contact with the article that has been designed, manufactured, imported, supplied, erected, installed, or issued as stores. Article is seen to be synonymous with product in that it includes components, equipment systems and ships.

(2)

b.

In preparing an STR the Design Sponsor is to be mindful of his duties under the Health & Safety at Work Act and is to give information and include requirements and tests to demonstrate compliance with the Act. In essence, the duties of the designer include, as appropriate, the following:
(1)

Ensuring so far as is reasonably practicable that articles and substances for use at work are safe and without risk to health when properly used. Carrying out or arranging for the carrying out of such testing and examination as may be necessary for the performance of the duty imposed by (1) Ensuring that adequate information will be available in connection with the use of the article at work, about the use for which it is designed and has been tested, and any conditions necessary to ensure safety and absence of risk to health when put to that use. Ensuring that adequate information will be available in connection with the use of the substance at work, about the results of any relevant tests which have been carried out, and any conditions necessary to ensure that it will be safe and without risk to health when properly used. Carrying out or arranging for the carrying out of any necessary research in connection with articles and substances with a view to the discovery and, so far as is reasonably practicable, the elimination or minimization of any risks to health or safety to which they may give rise. Ensuring that any person who erects or installs any article for use at work in any premises where the article is to be used by persons at work is aware that it is his duty to ensure, so far as is reasonably practicable, that nothing about the way in which it is erected or installed makes it unsafe or a risk to health when properly used.

(2)

(3)

(4)

(5)

(6)

2.5

NES 8 Issue 2 (Reformatted)

2.6

NES 8 Issue 2 (Reformatted)

3. 3.1

ARRANGEMENT AND CONTENT Structure


a. The preferred arrangement and content of an STR is to follow, or harmonize with the example included as Annex A to this NES, omitting or adding sections and Paragraphs as appropriate. Essentially every STR is to include: (1) Preliminary pages These are to identify and provide for administrative control of the document. A number of pages are mandatory, and these are indicated in Annex A (2) SECTION 1INTRODUCTION This Section is to set the scene for the development to be undertaken. It is to give background information that indicates how the work package interrelates with other work and can indicate the use that will be made of the information obtained as a result of the development. (3) SECTION 2TECHNICAL INFORMATION In this Section the technical requirements are to be described in such detail as appropriate to the purpose of the STR. In most cases this includes requirements and descriptions relating to performance, design and reliability. (4) SECTION 3QUALITY ASSURANCE REQUIREMENTS This Section should cover the requirements for Quality Assurance plans and organization together with the examinations, tests and trials, to be conducted to demonstrate the acceptability and adequacy of the developed solution to satisfy the STR. (5) SECTION 4MISCELLANEOUS This Section is to include all aspects that do not fall within Sections 1, 2 or 3. c. By regarding a vessel as a complex integration of systems and equipment, the total design requirements for a vessel can be specified by the identification of a unique collection of interrelated STRs. The text of the resultant documentation is to be grouped into Sections, Paragraphs and Sub-paragraphs, sequentially numbered using a decimal system.

b.

d.

3.2

Cover
a. The layout of information on the cover of an STR is to be generally in accordance with that shown in Annex A and is to include the following information as appropriate: (1) Title The Title is to be as brief as possible, but not so brief as to risk ambiguity. Titles are to embrace the overall content of the STR.
3.1

NES 8 Issue 2 (Reformatted)

(2)

Serial Number Every STR is to be given a Serial Number obtained from Section ME242, who maintain an Index of STRs. The Serial Numbers run consecutively starting at STR 1. Only one number is to be used in the development of any one product.

(3)

Part Number and Sub-title In cases where Development embraces a number of distinct stages (eg Concept, Feasibility, Project Definition, Full Development), or it is convenient to divide Development into a number of self-contained tasks, and a separate STR is prepared for each task, each document of the series is to be given an appropriate sub-title and Part Number, eg Statement of Technical Requirements for an Oil Fuel System, Part 1Feasibility Studies.

(4)

Issue and Date The initial issue is to be Issue 1 and the Serial Number and Date of Issue are to be included on the front cover. When an STR is altered or updated to take account of changed requirements the updated document is to bear a sequential Issue Number, a Date of Issue and be re-authorized. (See Clause 3.4.a.

(5)

Security Markings (a) STRs are to be given Security and Privacy Markings in accordance with MOD Manual 4 and JSP 184 as appropriate to the information disclosed. When an STR quotes, or reproduces extensively, information contained in a classified or privacy marked NES, care must be taken to ensure that the STR does not jeopardize the security of the NES. In cases of doubt the NES Sponsor is to be consulted.

(b)

(6)

Copy Number Copy Numbers are not to be given unless demanded by the security markings, or requested by the Design Sponsor to control distribution.

3.3

Colour
a. The basic colour of the cover and back is to be: BLUE BUFF GREEN PINK for documents with no security classification for documents classified RESTRICTED for documents classified CONFIDENTIAL for documents classified SECRET

3.4

Authorization
a. Every STR is to contain an authorization signed by the Design Sponsor to certify that the document is a true and proper stipulation of the design requirements. A typical format for the page is given in Annex A.

3.5

Conditions of Issue
a. Every STR is to include a Conditions of Issue page similar to that included in the Annex A. The Design Sponsor is to delete or add to these conditions as appropriate.
3.2

NES 8 Issue 2 (Reformatted)

3.6

Contents
a. The arrangement is to be as indicated in Annex C. A listing for the STR: (1) (2) (3) (4) (5) Preliminary pages and their Titles Sections by numbers and Titles Group headings within Sections and relevant Paragraphs Annexes Applicable Drawings

3.3

NES 8 Issue 2 (Reformatted)

3.4

NES 8 Issue 2 (Reformatted)

4. 4.1

EDITORIAL, TYPOGRAPHICAL AND PRINTING STYLE Guidance


a. This section details a preferred style. Rigid adherence to the style is not obligatory but departures from this style are acceptable only if the alternative is established and well known to those to whom the STR is directed.

4.2

Language
a. STRs are to be phrased in language free from ambiguity and in such terms that contractual implications are clear and enforceable. Consistency of terminology is particularly important. Short concise sentences and a minimum of punctuation aid reading and prevent misreading. Where a requirement is mandatory and contractually binding this is to be indicated in the text by the use of appropriate wording. Where a statement is non-mandatory and expresses an aim or recommendation this is also to be indicated by appropriate wording.

b.

4.3

Trade Names
a. Trade names, copyright names or other proprietary names applying exclusively to the product of one Company are only to be used when there is no alternative means of identification.

4.4

Terms and Abbreviations


a. Only common terms and abbreviations as included in acknowledged references are to be used in the text. Uncommon terms and those with a specialized meaning are to be explained in the text or in a footnote or included in the list of definitions. The first time an abbreviation is used in the text it should be placed in parentheses following the word(s) and term(s) written in full.

4.5

Symbols
a. Symbols are to be avoided in the text but may be used in equations and tables.

4.6

Units
a. The International System of Units as established by the International Standardization Organisation is to be used (See BS 5555).

4.7

Page numbering
a. Every page of an STR, including any Annex, is to have a unique page number. Right hand pages are always odd numbers, left hand pages being even numbered. The page numbers are always to be at the bottom centre of each page. Main text and Annex pages are to be numbered in sequence with Arabic numerals. Preliminary pages are to be numbered in sequence with lower case Roman numerals in brackets.

b. c.

4.8

Section, Paragraph and Sub-paragraph numbering


a. Each Section, Paragraph and Sub-paragraph of an STR is to be numbered consecutively with Arabic numerals using a decimal notation. In Annexes the
4.1

NES 8 Issue 2 (Reformatted)

numerals are to be preceded by the Annex reference, eg Annex A, Section 1, Paragraph 1, Sub-paragraph 1A.1.1.1.

4.9

Additions and Deletions


a. Where additions or deletions affecting page sequence are made in circumstances in which it would be uneconomical to reidentify and reissue the remainder of the STR, these pages are to be identified as follows: (1) (2) Additionsby the number of the preceding page being suffixed by a capital letter eg 41, 41A, FIB, etc. Deletionsby composite number on the preceding page eg 14/16 on page 14 to indicate pages 15 and 16 have been deleted.

4.10

Parts
a. Each part of an STR is to be numbered as a separate selfcontained document in accordance with the foregoing requirements.

4.11

Drawings
a. The term drawings is taken to embrace those drawings necessarily part of, but not bound in the cover of, the STR. Such drawings are to be listed as Related Documents and attached to the STR documents in a suitable manner.

4.12

Figures
a. The term figures includes sketches, diagrams, photographs and all forms of pictorial representation included in the text. Such figures are to be generally in accordance with JSP 183, and presented in the portrait mode wherever possible. Figures are to be numbered sequentially, in Arabic numerals throughout the STR. The figure number and title is to be given at the bottom centre of the figure. When figure(s) completely fill a page (ie a page without text) the page is to be numbered in sequence. Figures of the text are to be planned to complement but not to duplicate each other. Figures are to follow as closely as possible to their first reference in the text. Figures are to be up to a size corresponding to the maximum typing area of the ISO A4 size sheet. Figures up to 75% of a page can be inserted within the text. If A4 size is not adequate a vertically folded figure may be included but its size and format must conform to the A3L style sheet defined in JSP 183 and the figure, page and STR numbers are to be visible when the page is folded.

b. c.

d.

e.

4.13

Drawings and Figures


a. b. All drawings and figures are to be prepared in a form suitable for micro-copying. ISO stencils are to be used for headings. Colour is to be used only if essential.

4.14

Tables and Equations


a. Tables and equations are to be presented in accordance with Clauses 4.12.a.to 4.12.e.
4.2

NES 8 Issue 2 (Reformatted)

4.15

Typographic Style
a. The size and style of the typeface, the presentation of headings and the degree of indenting and spacing are to be as this NES.

4.16

Use of Capital Letters


a. In addition to the requirements of English grammar, capital letters are to be used as follows: (1) Initial capital letters are to be used for: (a) (b) (c) (d) Note Trade names and names of proprietary articles. Ship compartment names eg Auxiliary Machinery Room (AMR). Official names of equipment eg Gyro Compass Thermocouple NSN 6685995259879. Mk 19,

Names of major pieces of equipment when used in the particular eg No 1 HP Compressor.

Small specifically referred items such as the starter in No 1 HP Compressor starter shall have lower case initial letters. (e) (f) (g) (2) Specific internal cross references, eg see Part 1 Section 2. Titles and headings. Descriptive titles, eg First of Class, Follow-on-Ships.

Full capital letters are to be used for: (a) (b) (c) (d) Abbreviated titles such as HMS, NES, AMR. Official code names, eg AGOUTI. Acronyms or letter groups used officially as short titles eg RICE (Rationalized Internal Communications Equipment). Names of HM Ships or Class of Ship, eg HMS BROADSWORD, LEANDER Class Frigate.

(3)

Abbreviations and code letters as specified in British Standards or other Standards.

4.17

Hyphens
a. Hyphens are to be inserted as follows: (1) (2) (3) (4) As used in other Standards such as British Standards or in the Concise Oxford Dictionary. In such words as de-energize, co-ordinate, ie where the prefix ends and the root starts with the same vowel. Between two words grouped to form a compound adjective preceding a noun, eg low-voltage battery, change-over switch. In NATO Stock Numbers eg 6625999431534.
4.3

NES 8 Issue 2 (Reformatted)

4.18

Use of Solidus
a. The solidus (ie oblique stroke) when used with quantitative abbreviations always denotes divided by or per and in this context may be used to write fractions and so maintain single line spacing, eg rev/min. Subject to a few exceptions such as A/S (meaning anti-submarine) the solidus is not to be used in word abbreviations.

4.19

Presentation of Numbers
a. Commas are not to be inserted between digits of numbers (eg to indicate thousands). BS 5775 is to be followed but, generally, where there is no decimal point, a four digit number is written without a gap (eg 2345 not 2,345 or 2 345). Numbers of five or more digits are separated into groups of three counting from the decimal sign towards the left and the right. These groups are to be separated by a small space, never by a comma or a point. In numbers smaller than unity a zero should precede the decimal point eg 0.123 not .123. The decimal point is to be in the form of a point on the line.

b.

4.20

Component Reference
a. The rules for component references on circuit diagrams also apply to component lists, ie numbers in component references should be typed on the same line as the letter, not as subscripts, eg P2 not P2.

4.21

Spelling
a. The Concise Oxford Dictionary is to be followed. Technical words not given in this dictionary are to follow the spelling given in Chambers Dictionary of Science and Technology.

4.22

Classification Markings
a. On camera copy the security classification or the privacy marking is to be in 12 Point capital letters.

4.23

Paper Quality
a. b. Materials are to be selected from those listed in JSP 181. Camera copy masters are to be standard A4 or A3 size, best white or good quality white paper of at least 80 g/m2 weight. Oversize sheets ie laymark sheets with dual left and right hand markings are not to be used. The cover is to be card or manilla of weight not less than 157 g/m2.

c.

4.24

Binding
a. STRs are to be bound in one of the following methods: (1) in loose leaf form using either: (a) (b) Ring type stiff cover binder LOXON type binder

Both types of binder are to be in accordance with JSP 181. (2) Stapling.
4.4

NES 8 Issue 2 (Reformatted)

4.25

Punching
a. All STRs are to be punched to the standard four hole format given in JSP 181.

4.5

NES 8 Issue 2 (Reformatted)

4.6

NES 8 Issue 2 (Reformatted)

ANNEX A. A. RELATED DOCUMENTS


a. Reference is made to: Referred to in Clause BS 477B Glossary of terms used in quality Annex C 2.9.6 assurance (including reliability and maintainability) Specification for SI units and recommendations for the use of their multiples and of certain other units Specification for quantities, units and symbols Achievement of reliability and maintainability MOD practices and procedures for reliability and maintainability NATO guide to the preparation of specifications for the procurement of defence material Guide to quality assurance in design Conditions relating to the supply of documentation for NATO codification purposes 4.6.

BS 5555

BS 5775 DEF STAN 0040 DEF STAN 0041 DEF STAN 0528

4.19.a. Annex C 2.9.8 Annex C 2.9.8 Introduction

DEF STAN 0567 DEFCON 117/117A

Annex C 2.9.8 Annex C 4.10.3

Health & Safety At Work Act 1974 JSP 181 JSP 183 JSP 184

2.9.a., 2.9.b. Specifications for Technical Publications for the ServicesPhysical Standards Specifications for Technical Publications for the ServicesIllustration Standards Specifications for Technical Publications for the Security Requirements for Classified Technical Publications Ministry of Defence Security Regulations NATO Requirements for an Industrial Quality Control System Naval Engineering Standards SchemePolicy and Procedures Index of Standards for Ships and Weapons Equipment Provisioning Requirement Sheets for DG Ships Sponsored Equipment 4.23.a.,4.24.a. 4.25.a. 4.12.a., 4.12.e. 3.2.a.

MOD Manual 4 AQAPl(Edition 3) NES 0 NES 2 NES 42

3.2.a. Annex C 3.1.1 2.8.n. 2.8.d. Annex C 4.10.4

NES 43 NES 44

Ancillary Support Equipment, Test Annex C 4.10.5 Equipment and Tools Requirements for Upkeep Annex C 3.2.1, Documentation and Upkeep Evaluations 4.10.4

A.1

ANNEX A.

NES 8 Issue 2 (Reformatted)

NES 48 NES 54

Spares for Type A Support Supply of Information to Determine the Ship Fit of Equipment and Identification of Parts and Spares Requirements for Drawings Electromagnetic-interference and Susceptibility Requirements for Electrical Equipment for MCMV Manufacturers Recommended Spare Parts List List of Assemblies/Sub-assemblies to be provided with Spares Support Recommended List of ASE/CRETE/CUHTS/ CUMTE (NES 43)

Referred to in Clause Annex C 4.10.5 Annex C 4.10.3, 4.10.5 Annex C 4.5.2 Annex C 2.4.5, 3.6.1

NES 722 DG Ships 250B

SSCF 60 SSCF 73A SSCF 107 SSCF 128

RN Equipment Identification Certificate Annex C 4.10.5 Annex C 4.10.5 Annex C 4.10.51 Annex C 4.10.4, 4.10.5

ANNEX A.

A.2

NES 8 Issue 2 (Reformatted)

ANNEX B. B. DEFINITIONS AND ABBREVIATIONS


a. There are no Definitions and Abbreviations for this NES.

B.1

ANNEX B.

NES 8 Issue 2 (Reformatted)

ANNEX B.

B.2

NES 8 Issue 2 (Reformatted)

ANNEX C. C. GUIDE TO THE ARRANGEMENT AND CONTENT OF A STATEMENT OF TECHNICAL REQUIREMENTS FOR THE DEVELOPMENT OF A SYSTEM OR EQUIPMENT

C.1

ANNEX C

NES 8 Issue 2 (Reformatted)

ANNEX C

C.2

NES 8 Issue 2 (Reformatted)

MINISTRY OF DEFENCE CONTROLLERATE OF THE NAVY SEA SYSTEMS CONTROLLERATE

GUIDE TO THE ARRANGEMENT AND CONTENT OF A STATEMENT OF TECHNICAL REQUIREMENTS FOR THE DEVELOPMENT OF A SYSTEM OR EQUIPMENT

C.3

ANNEX C

NES 8 Issue 2 (Reformatted)

ANNEX C

C.4

NES 8 Issue 2 (Reformatted)

SECURITY MARKING

COPY NO

MINISTRY OF DEFENCE CONTROLLERATE OF THE NAVY SEA SYSTEMS CONTROLLERATE

STATEMENT OF TECHNICAL REQUIREMENTS


NO

FOR TITLE

PART

SUBTITLE

ISSUE

DATE

SECURITY MARKING

Cover
C.5 ANNEX C

NES 8 Issue 2 (Reformatted)

ANNEX C

C.6

NES 8 Issue 2 (Reformatted)

AUTHORIZATION
1. This Statement of Technical Requirements (STR) Number has been prepared by Sea Systems Controllerate and stipulates the requirements to be observed when developing This STR does not constitute an order to undertake the development. The management, review and programming requirements associated with the work will be defined in a Procurement Specification that embodies this STR. The conditions, resources and financial arrangements governing the implementation of the Procurement Specification will be the subject of a contract placed by Director of Contracts (D of C). Unless otherwise stated, reference in this STR to any document means the issue and all changes current at the date of authorization of this STR. If this STR is found to be inadequate, restrictive, worthy of amendment to permit a more-cost effective solution, or in any way unsuitable the Design Sponsor is to be informed through D of C.
Signed Design Sponsor Date for DCW/DCWE Published by: MOD(PE) Sea Systems Controllerate Foxhill, Bath

2. 3.

4.

5.

6.

(i)
C.7 ANNEX C

NES 8 Issue 2 (Reformatted)

(ii)
ANNEX C C.8

NES 8 Issue 2 (Reformatted)

CONDITIONS OF ISSUE General


1. This Statement of Technical Requirements (STR) has been prepared for the use of the Controllerate of the Navy (C of N.), Procurement Executive Ministry of Defence (MOD(PE)) and its contractors in the execution of Contracts for the MOD. The MOD accepts no liability whatever whether in contract or in tort (including but without limitation negligence on the part of the MOD, its servants or agents) for any deficiencies in design information where the STR is used for other purposes. The information contained herein is Crown Copyright or may be subject to privately owned rights. It is not to be released, reproduced or published without written permission of the MOD. The MOD accepts no liability whether in contract or in tort in respect of infringements of Third Party Rights.

2.

3.

Health and Safety


4. This STR may call for the use of processes, substances and procedures that may be injurious to health if adequate precautions are not taken. It refers only to technical suitability and in no way absolves either the supplier or the user from statutory obligations relating to health and safety at any stage of manufacture or use. Where attention is drawn to hazards, those quoted may not necessarily be exhaustive.

5.

Tender or Contract Process


6. This STR is the property of the MOD and unless otherwise authorized in writing by the MOD, must be returned on completion of the contract, or submission of the tender, in connection with which it is issued.

(iii)
C.9 ANNEX C

NES 8 Issue 2 (Reformatted)

(iv)
ANNEX C C.10

NES 8 Issue 2 (Reformatted)

CONTENTS AUTHORIZATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CONDITIONS OF ISSUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Health and Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tender or Contract Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

i iii
iii iii iii

1. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Preamble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 Related Documents and Drawings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4 Definitions, Abbreviations, Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1
1.1 1.1 1.1 1.1

2. TECHNICAL REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . .
2.1 Description and Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 Functional CharacteristicsPerformance . . . . . . . . . . . . . . . . . . . . . . . 2.3 Physical and other Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.4 Design and Construction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5 Environmental Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6 Interchangeability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7 Compatibility and Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8 Reliability and Associated Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9 Specimen Paragraphs for Availability, Reliability and Maintainability, (A, R and M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9.1 Equipment Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9.2 Notice for Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9.3 Equipment Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9.4 Equipment Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9.5 Equipment Maintainability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9.6 Equipment Life . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.9.7 Reliability and Maintainability Programme . . . . . . . . . . . . . . . . . . . . 2.10 Operational and Training Aspects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.11 Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.12 Constituents and Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.13 Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2.1
2.1 2.1 2.1 2.2 2.3 2.3 2.4 2.4 2.5 2.5 2.5 2.5 2.5 2.6 2.6 2.6 2.7 2.7 2.8 2.8

3. QUALITY ASSURANCE REQUIREMENTS . . . . . . . . . . . . . .


3.1 Quality Programmes and Plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Tests during Development . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 Type Test Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Production Test Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5 Preliminary Qualification Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6 EMC Testings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7 Test Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8 Test Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9 Nonconformance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1
3.1 3.1 3.1 3.1 3.1 3.2 3.2 3.2 3.2

4. MISCELLANEOUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 Models and MockUps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4 Test and Trial Sites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5 Configuration Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1
4.1 4.1 4.1 4.1 4.1

(v) C.11

NES 8 Issue 2 (Reformatted)

4.6 Design Progress Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7 Design Acceptance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8 Standards Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.9 Installation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.10 Support Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.11 Design Disclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.12 Development Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 4.1 4.1 4.1 4.2 4.2 4.2

(vi) C.12

NES 8 Issue 2 (Reformatted)

1. 1.1

INTRODUCTION Preamble
a. The preamble is to provide relevant background information and is not to be used to state technical requirements, all of which are to be included in later Sections. It can sketch the reasons for undertaking the development task and the use that will be made of the information obtained as a result of the development.

1.2

Scope
a. Scope is intended to identify the extent and limitations of the subject matter covered by the STR. It is to consist of a clear concise description of the subject covered, and state any options, restrictions or exclusions. It can contain information as to the use of the product. The content is to be complete and comprehensive and describe the item covered in terms which can be interpreted without ambiguity by contractors or others familiar with applicable technology and trade practices. The scope is to include reference to the supply of mock-ups, development models, special development rigs and any special facilities to be provided during the development. Details are to be included in Section F Miscellaneous.

b.

c.

1.3

Related Documents and Drawings


a. Documents and drawings to which reference is made in the STR are to be listed, together with the Paragraphs of the STR in which they are quoted, under appropriate headings in the Introduction. Under a heading Mandatory References are to be listed those documents and drawings to which reference is made for the purpose of specifying a mandatory requirement. The identity of these documents and drawings is to be stated in such precision that there is never any likelihood of confusion with a similarly referenced requirement in another issue of the same document or drawing in the form Clause 0123 of NES 456, Issue 7 with Amendment 8. Under a heading References are to be listed those documents and drawings to which reference is made for the purpose of indicating a general requirement for which a precise stipulation is not necessary. The identity of these documents and drawings is to be stated in a manner that identifies the nature of the requirement without recourse to identifying the clause or paragraph of a particular document, eg DEF STAN 0000. It is to be assumed that all related documents and drawings of all References are invoked unless stated to the contrary. The source of supply of all Referenced documents is to be stated. A Paragraph is to be included to the effect that in the event of apparent conflict between the STR and any related reference documents, the STR is to take precedence. In the case of conflict between referenced documents precedence is to be stated.

b.

c.

d. e. f.

1.4

Definitions, Abbreviations, Symbols


a. All uncommon terms and abbreviations or those with specialized meanings, and symbols, are to be listed in this Section. 1.1
C.13 ANNEX C

NES 8 Issue 2 (Reformatted)

1.2
ANNEX C C.14

NES 8 Issue 2 (Reformatted)

2. 2.1

TECHNICAL REQUIREMENTS Description and Purpose


a. The full definition of the equipment is to be given, including references to relevant drawings. A list of the main constituents distinguishing between those which are to be developed and those which are to be supplied from other sources is to be included. A comprehensive description of the equipment is to be given, including the overall purpose and basic parameters which are to be recognized in the design and the anticipated usage. The relationship of the equipment to the overall system of which it is a part, including logic and block diagrams, is to be included. A statement is to be made regarding any hazards which the equipment could encounter. The requirements for mockups, models etc. the scales to which they are to be made, the materials, and the extent to which they are representative of a finalized item, as well as their influence on the development programme, are to be specified, together with the necessary provisions for updating. Special provision relating to drawings or other specific transmission of information is also to be given in this paragraph, or can be included in the Miscellaneous Section.

b.

c. d. e.

f.

2.2

Functional CharacteristicsPerformance
a. These characteristics are to include general and detailed requirements, under appropriate sub-headings, for all the performance requirements, ie what is expected of the equipment. In general, both upper and lower performance limits are to be given. Normally the Section is to include, at least, such considerations as: Qualitative characteristics. Quantitative criteria under stipulated environmental and other conditions, eg range of output performance parameters with associated input parameters. Performance requirements for the various operational phases and modes of system operation, including performance acceptance limits. Dynamic characteristics, eg rate, velocities, movements etc.

b. c. d. e.

2.3

Physical and other Characteristics


a. These characteristics are to include general and detailed requirements relating to the physical properties of equipment together with any other requirements which impinge, directly or indirectly, on those properties. Requirements necessary to ensure physical compatibility with other equipment are to be included.

2.1
C.15 ANNEX C

NES 8 Issue 2 (Reformatted)

b.

The following at least are to be covered:

(1) (2) (3) (4) (5) (6) (7) 2.4

Mass limitations. Dimensional limits, including space for contained materiel, crew space, operational layout ingress, exits and access for maintenance. Durability factors to assure adequate ruggedness. Health and Safety Criteria in relation to explosive, biological, toxic effects, radiological effects. Protective coatings to assure protection from corrosion, abrasion etc. Sealing against adverse environmental conditions. Vulnerability factors.

Design and Construction


a. Minimum and essential requirements that are not determined by the performance characteristics or interface requirements are to be specified. These are to include appropriate design standards, and requirements covering the use of preferred materials, parts, standard commercial components, processes etc. In particular, if compliance with specified International Standards is a requirement, this is to be stated. Maintainability requirements are to be stated, these are to include Upkeep Policy, Overhaul Cycles, Upkeep by Exchange features etc. Specifications requiring or authorizing the use of dangerous, eg toxic, radio active products, must stipulate the need for compliance with the applicable National Safety Codes. Safety requirements are to be specified, to preclude or limit hazards to personnel, equipment or both, including fail safe and emergency operating restrictions, interlocks, and emergency and standby circuits etc. Design and construction requirements pertaining to electromagnetic compatibility are to be stated in terms of the environment which the item has to accept and which it generates, in accordance with DG Ships 250B. Requirements relating to ergonomic suitability of manmachine interfaces for variations of operators size and strength capability are to be given. Human Factors for Designers of Naval Equipment refers. Identification nameplates and markings for stock control, replacement, and repair parts are to be stated. Minimum design construction standards applicable to the class of equipment in question, together with design constraints and standards necessary to assure compatibility of hardware, are to be specified. In formulating the strength and integrity requirements, care is to be taken to distinguish between static and dynamic conditions; where appropriate the requirements for the avoidance of equipment instabilities are to be stated. 2.2

b. c.

d.

e.

f.

g. h.

i.

ANNEX C

C.16

NES 8 Issue 2 (Reformatted)

j.

The requirements for workmanship standards to be achieved in development models, and requirements for the use of production techniques during prototype manufacture, are to be stated.

2.5

Environmental Conditions
a. The environmental conditions and limitations applicable throughout the life of equipment, ie production, transportation, installation, operation, disposal and storage, are to be stated, including:

(1) (2) (3) (4) (5) (6) (7) (8) (9)

Temperature Pressure Humidity Ice and snow Rain, water and salt spray Fog, including sea fog Shock and acceleration levels Vibration, including the vibration during motion or weapon operation Sea state and turbulence

(10) Noise (11) Dust or sand (12) Infestation and attack by micro organisms (13) Radiation including solar radiation (14) Nuclear explosives effects (eg EMP) (15) Electrical, magnetic and electromagnetic effects (eg EMC) (16) Solid particles and fluids (17) Chemicals (18) Contamination by fluids, chemicals etc (19) Flammable or explosive atmospheres.
b. It is important to state these as combinations in cases where the combined effect is more serious than in each separate condition. The duration of exposure, cycles of environmental conditions and rates of variation are also important and are to be specified where applicable. Self induced conditions are to be included when framing requirements for protection against specified environmental conditions.

2.6

Interchangeability
a. The levels at which interchangeability or replaceability are required are to be stated, together with the physical and functional interchangeability 2.3
C.17 ANNEX C

NES 8 Issue 2 (Reformatted)

characteristics relating to the installation of components. The need for jigs, tools and gauges to verify interchangeability is to be stated.

2.7

Compatibility and Interfaces


a. The interfaces between the equipment to be developed and other equipment, or a major sub-system or components, are to be specified in quantitative terms, eg inputs, outputs, accelerations, temperatures, vibration characteristics, loads, speeds, irregular movements etc. Interface characteristics which change as a result of different users or operational modes, are to be clearly identified. Diagrams should be provided to aid interface definition. Physical interface relationships are to be expressed in terms of dimensions with tolerances.

b. c.

2.8

Reliability and Associated Criteria


a. Reliability is an important criterion and is to be stated numerically with confidence levels in terms of mission success or hardware mean time between failures. It may also be appropriate to specify requirements for other factors, such as availability, operational life, shelf life, or life between overhauls. The procedures for assessing such factors are to be specified. The requirements for reliability and life expectancy are to take into account the environment and uses to which the equipment is to be subjected. The overall reliability required is to be apportioned between the separate functional areas so that each may be developed with a view to achieving the desired overall reliability. The reliability can be stated initially as a goal with the lower minimum acceptable requirement. In this case, realistic reliability requirements are to be determined and incorporated later in the STR together with the requirements for any demonstration. The reliability of a product under development is difficult to assess even with a knowledge of the reliability of its components. The apportionment of reliability to sub-assemblies and components is to be given in as much detail as available and the extent to which such data has been used in meeting this requirement is to be defined. Maintainability requirements are to be expressed in quantitative terms, such as:

b. c.

d.

e.

f.

(1) (2) (3) (4)


g.

Time, eg turnround time, time for repair, time between maintenance actions. Rate, eg frequency of preventive maintenance. Complexity, eg number of people and skill levels, variety of support equipment. Weight and dimensional parameters for modular construction and for test equipment access.

Requirements resulting from the proposed use of automatic test equipment for maintenance purposes are to be specified. 2.4

ANNEX C

C.18

NES 8 Issue 2 (Reformatted)

h. i.

Requirements for on board repair by substitution of components, eg replacement of a faulty part or module of an electronic item, are to be defined. The time during which the equipment is to be in an operable state to start a mission, eg the availability, is to be specified.

2.9

Specimen Paragraphs for Availability, Reliability and Maintainability, (A, R and M)


a. The manner in which requirements for A, R and M may be specified depends on the application of the equipment. Typical examples are given below and are taken from specimen paragraphs for the preparation of Staff Requirements Naval. These paragraphs may be amended to take account of multi-mode operation, environmental conditions or the use of existing commercial equipment.

2.9.1

Equipment Usage a. days the equipment will be in During a maximum operational period of hours per day. When not in use, the equipment is to be retained use for in an operational state unless undergoing corrective or preventive maintenance. Note It may be appropriate to specify different usage patterns for each sub-system.

b. 2.9.2

Notice for Use a. The time required to bring equipment to full operational use is not to exceed:

(1) (2) (3) (4)


2.9.3

Mins or Mins or Mins or Mins or

hours from non-operational state hours during daily preventive maintenance hours during weekly preventive maintenance hours during monthly preventive maintenance.

Equipment Availability a. The probability that the equipment will be available, (ie not undergoing corrective maintenance), at any instant during the operational period is to be %. not less than Not applicable to equipment which cannot be repaired at sea. The downtime due to preventive maintenance activities during the operational hours. period is not to exceed Sufficient onboard spares are to be scaled such that the risk of stock-out would be less than %.

Note b. c. 2.9.4

Equipment Reliability a. In respect of failures which are not repairable at sea, the probability that the equipment will survive the maximum operational period at the stated usage %. without failure is to be greater than

2.5
C.19 ANNEX C

NES 8 Issue 2 (Reformatted)

b.

In respect of failures which are repairable at sea during the operational period, hours the probability that the equipment will survive a period of continuous operation without such a failure is to be greater than %. In general, a failure is deemed to occur whenever the level of performance falls below that necessary for the equipment to achieve its operational aims. When doubt exists as to what constitutes a failure, such as is likely to occur in multimode operation, the levels of failure are to be identified.

Note

2.9.5

Equipment Maintainability a. The Median active time (50 percentile) to restore or repair the equipment after failure using specified procedures and resources is not to be greater than minutes. The maximum (95 percentile) active repair time is not to be greater than minutes. Note This format assumes a log normal distribution of active repair times for which a maximum repair time of three times the median repair time for electronic equipment and five or more times the median for mechanical equipment will be applicable (BS 4778 1979 refers).

2.9.6

Equipment Life a. The intended life of the equipment between major overhauls, rebuilding or years. The total expected service life replacement is not to be less than years. from first fit to final disposal of last equipment is

2.9.7

Reliability and Maintainability Programme a. The programme of work to give assurance of, and where appropriate to demonstrate the achievement of the Availability, Reliability and Maintainability requirements is to be formulated in accordance with DEFSTAN 0040. The above is a minimum requirement and it may be necessary to give further guidance on the extent of the R & M programme expected for the purpose of agreeing costs. One or more of the following may be helpful:

Note

(1)

Historical Data Survey. A survey of failure data on similar equipment is to be undertaken including: (a) Brief history of design offered, date entered service, user environment for which designed, total number equipments produced and total time in use to date. Summary of operating experience, known causes of failures and details of modifications.

(b)

(2) (3)

Novel Features Analysis. A listing of the features of the design which are new to Naval service is to be made, with a justification for each. Design Check List. A design check list is to be completed, compiled from DEFSTAN 0041 (Part 4) Section E or from an applicable Naval Engineering Standard. 2.6

ANNEX C

C.20

NES 8 Issue 2 (Reformatted)

(4)

Failure Mode and Effects Analysis. An FMEA is to be carried out in accordance with DEFSTAN 0041 Part 4 Section C on the equipment is defined in. The Equipment Designer is to submit a proposal for the conduct of the FMEA to the Design Sponsor for approval. The proposal should detail the work package necessary to give assurance on the types of possible failure modes, the severity of the effects, the means of detecting failures and the compensating provisions in the design. Criticality Analysis. A Criticality Analysis is to be carried out in accordance with DEFSTAN 0041 Part 4 Section D subsequent to the conduct of an FMEA. The Equipment Designer is to submit a CA proposal to the Design Sponsor for approval. Fault Tree Analysis. A Fault Tree Analysis is to be carried out in accordance with DEFSTAN 0041 Part 4 Section B. The Equipment Designer is to submit an FTA proposal to the Design Sponsor for approval. The proposal should detail the work package necessary to give assurance on the probability of failure of the equipment in a defined mode. Maintainability Analysis. The FMEA is to form a basis for a Maintainability Analysis identifying the corrective maintenance necessary in the event of any failure and where it should be carried out. The analysis is to provide an estimate of the times for all diagnosis and repair actions assuming test equipment, spares and manpower available, using maintainability data from approved sources. Proposals for conducting the Maintainability Analysis are to be submitted by the Equipment Designer to the Design Sponsor for approval. Design Review. Design Reviews are to be conducted in accordance with DEFSTAN 0567 at which documentation on the above R & M activities and other quality assurance aspects are to be presented.

(5)

(6)

(7)

(8)

2.10

Operational and Training Aspects


a. This Paragraph is to give requirements relating to manning, operational and logistic support of the equipment, to the extent that the requirements define or constrain design of equipment. Requirements are to be specified in numerical form and are to include such items as numbers and types of personnel necessary for the operation, maintenance and control of the equipment. Any requirements to be met by the contractor relating to personnel training, or equipment facilities are to be specified.

b.

2.11

Production
a. Requirements for particular manufacturing processes, or production methods are to be specified when the equipment is critically dependent upon them. In other cases, reference to specified processes is to be avoided as it could restrict new developments or inhibit the use of more economic techniques. Requirements on the standard of workmanship are to be stated when it is pertinent to the finished quality of the product. Specific tests are not to be included under this heading, being covered under Quality Assurance Requirements. 2.7
C.21 ANNEX C

b. c.

NES 8 Issue 2 (Reformatted)

2.12

Constituents and Components


a. Vigilance is to be exercised to ensure that the technical requirements for constituents of, and components for, an equipment are adequately specified in identifiable Standards, Specifications or other STRs, or that such requirements are implicit in the STR for the equipment.

2.13

Safety
a. Requirements relating to safety during handling, manufacture, assembly, dismantling, testing, transfer, storage, starting up and maintenance operations are to be stipulated if they are not covered elsewhere in the Statement of Technical Requirements or by standard industrial practice and existing Standards. Restrictions arising out of the emergency operation of equipment (ie the operation of standby circuits and interconnection and any redundant circuits), considered to be necessary for preventing damage or recovery of the item in the event of breakdown, are to be stated.

b.

2.8
ANNEX C C.22

NES 8 Issue 2 (Reformatted)

3.
3.1

QUALITY ASSURANCE REQUIREMENTS Quality Programmes and Plans


a. When AQAP1 (Edition 3) is called up in a contract, the contractor is required to document his intended quality assurance arrangements. Normally a Quality Plan, specific to the contract, which supplements the contractors general system, will be called for in Development Contracts. Management organizations and programming requirements of the Quality Plan are to be included in the Procurement Specification that embodies the STR, not in the STR itself. However, in preparing an STR, the Design Sponsor must bear in mind these administrative requirements and is to include technical requirements that enable achievement of the Quality Plan. Programmes in the Quality Plan are to be co-ordinated and integrated with any programmes or plans required for reliability, maintainability, safety, etc (See Paragraph 2.9.8). Features that may need to be included in the Quality Plan are in Paragraphs 3.2 to 3.9.

b.

c.

d.
3.2

Tests during Development


a. The requirements for formal tests during development are to be stated, they may include: (1) (2) (3) (4) (5) (6) (7) Operational capability verification Engineering evaluation Performance verification Reliability testing Assembly and installation testing Testing to demonstrate any novel features of the design Maintenance Evaluation (See NES 44).

3.3

Type Test Specification


a. The need is to be stated for a Type Test Specification that defines the tests that need to be undertaken during development and audited during the process for acceptance, together with those tests that are to be undertaken as part of the process of acceptance.

3.4

Production Test Specification


a. The need is to be stated for a Production Test Specification that includes tests to ensure compliance with the design intent, (as demonstrated during acceptance by application of the Type Test Specification), during subsequent production runs, and to ensure that both the functional and mechanical interchangeability are maintained.

3.5

Preliminary Qualification Tests


a. The requirements for preliminary qualification tests are to be specified. The responsibilities for the preparation of, or the need to obtain the approval of the 3.1
C.23 ANNEX C

NES 8 Issue 2 (Reformatted)

Quality Assurance Authority for, qualification tests are to be specified if not covered by National procedures.
3.6

EMC Testings
a. The need is to be stated for the equipment to be EMC tested to the requirements of DG Ships 250B and whether an EMP test is to be included.

3.7

Test Equipment
a. Guidance on the test equipment, power sources and environmental conditions are to be given. For certain tests, eg cold, vibration, acceleration, shock, instruction is to be given as to which of the other tests such as functional and accuracy, are to be included as an integral part of the particular test.

3.8

Test Methods
a. Test methods and procedures are normally to be those officially recognized. When this is not possible the methods and procedures used by the manufacturer are to be subject to approval by the Design Sponsor, such powers of approval being delegated, if appropriate, to the official Quality Assurance Representative.

3.9

Nonconformance a. Procedures to be followed when nonconformance with the STR is revealed during the design development process, or when individual items do not attain the required level of performance against correctly applied tests, are to be stated. When such procedures are given in existing documentation, reference is to be made to that documentation.

3.2
ANNEX C C.24

NES 8 Issue 2 (Reformatted)

4.
4.1

MISCELLANEOUS Packaging
a. Methods to be used for dismantling, cleaning, dehydrating, packaging, and protective measures to prevent deterioration are to be stated if they influence the design of the equipment.

4.2

Storage
a. Special provisions to be made for storage and handling are to be stated.

4.3

Models and MockUps


a. Detailed requirements for models and mock-ups are to be stated, giving scale, accuracy, extent and date required.

4.4

Test and Trial Sites


a. Detailed requirements are to be stated for test and trial sites to be hired or constructed, giving purpose, date required, level of manning required and anticipated usage.

4.5

Configuration Definition
a. The Design Sponsor is to state whether the configuration definition, to be provided as part of the development, is to be merely the minimum suitable for the product to be manufactured in the development contractors organization, or whether the configuration definition is to be the minimum necessary for manufacture by any other contractor. The first alternative is to be adopted only after reaching agreement with D of C that the requirement to seek competitive tenders on production orders can be waived. The Design Sponsor is to state the requirements for the quality and extent of the manufacturing drawings to be provided as part of the configuration definition; qualifying NES 722 as necessary.

b.

4.6

Design Progress Information


a. The Design Sponsor is to state the type, quality and quantity of drawings, calculations, specifications etc that need to be supplied to him to enable progress monitoring of the development.

4.7

Design Acceptance
a. The Design Sponsor is to state the Authority who is to apply the Type Test specification, and thereby accept the design presented as satisfying the Statement of Technical Requirements. In the case of more than one Authority, the division of responsibilities is to be stated.

4.8

Standards Information
a. The need for drawings, outline descriptions and interface information to include in a list type NES, or the need to prepare a complete NES, is to be stated.

4.9

Installation Information
a. Requirements for installation drawings, installation specifications, or installation instructions are to be stated. 4.1
C.25 ANNEX C

NES 8 Issue 2 (Reformatted)

4.10

Support Information
a. Requirements are to be stated for drawings, specifications, and documentation that must be provided during (Design) Development as a basis for Support documentation. Intellectual Property Rights (IPR) that may affect the data of 4.10.a. are to be recognized, and reference is to be made to associated Contractual Terms that are (to be) included in the Contract Letter. The supply of data as and when specifically called for by the Ministry, to enable NATO Codification of the equipment and of all parts of it that may be required by MOD to be made RNSTS Items of Supply, is to be identified as a requirement. NES54 and DEFCON 117/117A are to be identified as being relevant to any ensuing Production Contract, and are to be stated as required to be catered for in the Development drawings etc. The Upkeep Policy, Overhaul Cycles, Exchange features, etc. that are required by para 2.4.a to be stated, and are to be reflected in Equipment Requirements Provisioning Sheets (EPRS), SSCF128, (see NES 42), and they are to form part of the definition of the requirements of the Maintenance Evaluation, (see NES 44), of para 3.2.a.7. A requirement is to be stated for recommendations to be provided for (a) a List of Spares, using SSCF73A, (see NES 54 and NES 48), and (b) an associated List of Tools, using SSCF128, (see NES 43). These recommendations are to be compatible with the requirement of para 2.4.a. as expressed in the EPRS, and with the results and Report of the Maintenance Evaluation of para 3.2.a.7. The Forms SSCF73A and SSCF128 are to be completed with Drawing and item data as is available at the then state of Drawing production. Forms SSCF73A are to be associated with General Arrangement Drawings, Pamphlets, etc. that enable the nature and purpose of the items to be recognized from the identifying data that is given on the Forms SSCF73A. Full identification and NATO Codification, (in accordance with NES 54), will not be carried out until Modification State Zero drawings and associated Forms SSCF60/107/73A etc. are available, to identify the intended VesselFit equipment and its parts. Maintenance Envelope drawings are to be produced in accordance with NES 302.

b.

c.

d.

e.

Note

f.
4.11

Design Disclosure a. The need for the contractor to record and retain systematically queries, decisions, records, trials etc conducted during development is to be stated.

4.12

Development Models a. Details of breadboard models, X and Y models and preproduction manufacture required during development are to be stated.

4.2
ANNEX C C.26

Inside Rear Cover

Crown Copyright 2000 Copying Only as Agreed with DStan

Defence Standards are Published by and Obtainable from: Defence Procurement Agency An Executive Agency of The Ministry of Defence Directorate of Standardization Kentigern House 65 Brown Street GLASGOW G2 8EX DStan Helpdesk Tel 0141 224 2531/2 Fax 0141 224 2503 Internet e-mail enquiries@dstan.mod.uk File Reference The DStan file reference relating to work on this standard is D/DStan/69/02/8. Contract Requirements When Defence Standards are incorporated into contracts users are responsible for their correct application and for complying with contractual and statutory requirements. Compliance with a Defence Standard does not in itself confer immunity from legal obligations. Revision of Defence Standards Defence Standards are revised as necessary by up issue or amendment. It is important that users of Defence Standards should ascertain that they are in possession of the latest issue or amendment. Information on all Defence Standards is contained in Def Stan 00-00 Standards for Defence Part 3 , Index of Standards for Defence Procurement Section 4 Index of Defence Standards and Defence Specifications published annually and supplemented regularly by Standards in Defence News (SID News). Any person who, when making use of a Defence Standard encounters an inaccuracy or ambiguity is requested to notify the Directorate of Standardization (DStan) without delay in order that the matter may be investigated and appropriate action taken.