DEF STAN 00-60 (PART 10)/3

Section Three. Application of S1000D

8 Introduction

8.1The base specification for this Section of this Defence Standard shall be S1000D as amplified or amended in the following paragraphs.

8.2All statements in S1000D which relate to air vehicles and associated equipment shall apply equally to any equipment unless specifically covered by this Section.

8.3This Section details the application of S1000D and highlights where there are specific differences. Section 3 to Part 11 of this Defence Standard provides general guidance on the application of S1000D.

9 Detailed Application

Introduction. The requirements for the application of S1000D are detailed below. Where S1000D has been expanded or amplified such details are included. Where S1000D can be applied directly this is stated.

9.1 S1000D Chapter 1 Introduction to the Specification

9.1.1S1000D Chapter 1.1 Purpose. As per S1000D.

9.1.2S1000D Chapter 1.2 Background. As per S1000D.

9.1.3S1000D Chapter 1.3 Scope. As per S1000D except Field of Application, which shall read: ‘The specification is designed to cover electronic documentation activities in support of all equipment. This shall include Illustrated Parts Information’.

9.1.4S1000D Chapter 1.4 Updating the Specification. Update of the specification shall be as per S1000D.

9.1.5S1000D Chapter 1.5 Glossary of Terms and Abbreviations. The Glossary of Terms and Abbreviations shall be as per S1000D. Additionally, a glossary of terms and abbreviations as used in this Part of this Defence Standard is contained in annex A to Part 0 of this Defence Standard and shall take precedence over those in S1000D, where differences exist.

9.2 S1000D Chapter 2 - General Rules

9.2.1S1000D Chapter 2.1 Introduction. As per S1000D.

9.2.2S1000D Chapter 2.2 Model Identification(MI) Code. The End Item Acronym Code (EIAC)(DED 096) combined with the Usable On Code (UOC)(DED 501) as defined in the annex C to Part 0 of this Defence Standard, shall replace the S1000D MI Code. The MI Code may however, be required in projects (for example an international procurement or

9

DEF STAN 00-60 (PART 10)/3

collaborative project using this Defence Standard where S1000D is directly employed). In these cases, the first two characters of the EIAC shall be used to accommodate the MI Code, with the last eight characters suppressed (ie blank) and a default UOC of 000 shall be used.

9.2.3S1000D Chapter 2.3 System Difference Code (SDC). The UOC for system level items , as defined in the LSAR, replaces the S1000D SDC. The S1000D SDC may however, be required in projects using this standard (for example in international or collaborative projects where S1000D is directly employed) and in these cases, the character of the UOC shall be used to accommodate the SDC.

9.2.4S1000D Chapter 2.4 Standard Numbering System (SNS). The SNS of S1000D is replaced by the system detailed in annex A to this Part of this Defence Standard.

9.2.5S1000D Chapter 2.5 Writing Rules. The writing rules are as per S1000D, except for the following:

9.2.5.1Language. Where it is intended that DM are to be used for both operator and maintainer, they shall be written to the style, scope and depth required for the operator. If this information is not sufficient for maintenance purposes, then an additional DM covering the required maintenance procedure shall be produced. Performance data shall be quoted in the values indicated on the system displays as displayed to the user.

9.2.5.2References. Repetition of information is to be avoided and exceptionally, where related subject matter is not included in the publications data base, it shall be suitably referenced so that the reader does not overlook important information.

9.2.5.3Conventions. The following conventions shall be used throughout:

(a)Decimals shall be used except where instrumentation or controls are marked in vulgar fractions.

(b)Decimals shall be written using the decimal point (dot) not a comma. Figures of less than one shall be preceded by zero.

(c)Unless otherwise stated, all data shall be presented to the user in the same form as that displayed on the equipment

9.2.6S1000D Chapter 2.6 Illustrations. Specific rules governing non-textual information are detailed in Section 5 of this Part of this Defence Standard.

9.2.7S1000D Chapter 2.7 Warnings, Cautions and Notes. As per S1000D, except for the following:

(a) Responsibilities. The Contractor shall be responsible for ensuring that all hazards are identified and documented in the DPDB and IETP.

10

DEF STAN 00-60 (PART 10)/3

(b) Definitions. Warnings, as per S1000D, with the addition :

‘WARNINGS shall conform to the requirements of the Health and Safety at Work Act 1974, as amended by the Consumer Protection Act 1987, the Control of Substances Hazardous to Health (COSHH) regulations and other legislation in force at contract award’.

9.2.8S1000D Chapter 2.8 Zoning and Access. As per S1000D for Air Systems. The requirements for other equipment are included in annex B to this Part of this Defence Standard, with Service-specific examples.

9.2.9S1000D Chapter 2.9 Security Classification. S1000D is not applicable. The UK requirements for security classification of DM/Technical Publications and other rules for security will be detailed in the contract.

9.2.10S1000D Chapter 2.10 Quality Assurance. As per S1000D, subject to overall Quality Audit requirements detailed at Section 2 of this Part of this Defence Standard and Part 0 of this Defence Standard.

9.3 S1000D Chapter 3 - Common Source Data Base (CSDB).

9.3.1S1000D Chapter 3.1 Introduction. As per S1000D.

9.3.2S1000D Chapter 3.2 Data Module Code. For this Defence Standard application, the Data Module Code (DMC) shall comprise 32 characters and shall be built up as shown in Figure 1.

XXXXXXXXXX XXX XXX A XX XX XX XX NN XXX X A

MI Code (EIAC)

MI Code (End Item UOC)

SDC (System-level UOC) SNS (Document code MICC)

SNS (Document code SNS) - system sub-system/section sub-sub-system

Disassembly code Disassembly code variant Information code Information code variant Item location code

11

DEF STAN 00-60 (PART 10)/3

(a)Model Identification (MI) Code. For this Defence Standard the MI Code is a thirteen character alpha-numeric which identifies the specific equipment, platform or system to which the DM relates. It comprises EIAC (ten character) and the UOC (three character ) for the end item.

(b)System Difference Code (SDC). For this Defence Standard the UOC for the system level is used as the SDC. The UOC is a three character alphanumeric code.

(c)Standard Numbering System (SNS) Code. For this Defence Standard the Document Code (DC) (DED 802) shall be used as the SNS. The DC comprises seven alphanumeric characters, the first four characters of which are defined in annex A of this Part of this Defence Standard, the last three shall be allocated by the contractor on a project specific basis.

(d)Disassembly Code. The Disassembly Code is a two character alphanumeric code which identifies the breakdown of an assembly, linked to the LSA Control Number (LCN) structure below the SNS level, where maintenance information applies. Where used, the code shall be allocated from 00 through 99 and subsequently A1 to AZ, B1 to BZ, etc.

(e)Disassembly Code Variant (DCV). For this Defence Standard the Alternate LCN (ALC) shall be used as the DCV. The ALC is a two character numeric.

(f)Information Code(IC). The IC structure is as per S1000D.

(g)Information Code Variant (ICV). The ICV is a single alphanumeric character.

(h)Item Location Code (LC). The LC shall be used as per S1000D.

9.3.2.1For S1000D application, the DMC shall comprise 32 characters, with 15 characters suppressed, to map the S1000D DMC as shown in Figure 2.

9.3.2.2S1000D Chapter 3.2 Para 11 Data Module Code for Support and Training Equipment. Not applicable.

9.3.2.3S1000D Chapter 3.2.1 Data Module Coding Summary. For DMC Summaries see annex C to this Part of this Defence Standard.

9.3.2.4S1000D Chapter 3.2.2 Disassembly Principle. As per S1000D.

9.3.2.5S1000D Chapter 3.2.3 Information Codes Definitions for DMs. As per S1000D except as detailed in annex D to this Part of this Defence Standard.

9.3.2.6S1000D Chapter 3.2.4 Item Location Codes. As per S1000D.

9.3.2.7S1000D Chapter 3.2.5 Categories and Sub-categories for Aerospace Ground Equipment and Training Equipment. Not applicable.

12

DEF STAN 00-60 (PART 10)/3

XX&&&&&&&& φφφ Nφφ & XX XX XX XX Aφ XXX A A

MI Code (EIAC)

MI Code (End Item UOC)

SDC (System-level UOC) SNS (Document code MICC)

SNS (Document code SNS) - system sub-system/section sub-sub-system

Disassembly code Disassembly code variant Information code Information code variant Item location code

Figure 2 DMC for S1000D application

9.3.2.8 S1000D Chapter 3.2.6 Example of Data Module Code for Aerospace Ground Equipment. Not applicable.

9.3.3 S1000D Chapter 3.3 Data Module Structure. As per S1000D.

9.3.3.1 S1000D Chapter 3.3.1 Identification and Status Section. As per S1000D, except for the following:

(a)Responsible Partner Company is Optional (O).

(b)Skill Levels are Mandatory (M).

(c)Reason For Updating is Mandatory (M).

9.3.3.2S1000D Chapter 3.3.2 Identification and Status Section - Layout. As per S1000D.

9.3.3.3S1000D Chapter 3.3.3 Contents Section. As per S1000D except for the following:

(a) Security Classification (O) - The second paragraph shall read: ‘The security classification tag attributes 1(UNCLASSIFIED), 2(RESTRICTED), 3(CONFIDENTIAL), 4(SECRET) and 5(TOP SECRET), will be applied at the discretion of the project, to the data within a DM in accordance with clause 9.2.9 of Part 10 of Defence Standard 00 - 60.’

13

DEF STAN 00-60 (PART 10)/3

(b)Change Marks are mandatory (M) and Highlights are optional (O).

(c)Description - General - Data will be provided by the Contractor or will be Government Furnished Information (GFI), as stated by the contract. Data may be derived from various sources (eg Use Study, Design Database, LSA/LSAR, existing DPDB) and irrespective of the source, the derived data shall be contained within the DPDB.

(d)Descriptive Data Modules - The scope of the descriptive DM shall encompass all aspects of the system's capabilities, operation, construction and functionality. It shall also include purpose and planning information. The depth shall enable all the actions required of operators and maintainers to be described. In the case of operator information this must be the data to enable a detailed understanding of the system's operation and capabilities, including such areas as emergency procedures and reversionary modes of operation. In the case of the maintainer the construction and functionality must be described at a depth appropriate to the maintenance requirements. Descriptive DM shall not contain procedures.

(e)Procedural Data Modules - The scope of the procedural DM shall encompass all aspects of operation, replenishment and maintenance for the system. The depth shall enable all the actions required of operators and maintainers to be carried out. In the case of operator information this must enable all of the system's capabilities to be exercised, including such areas as emergency procedures and reversionary modes of operation. In the case of the maintainer information, procedures for diagnostic, preventive maintenance and corrective maintenance must be provided to the depth appropriate to the maintenance philosophy.

(f)Identification of Data (M) - The category of information (descriptive or procedural) and the sub-category (capability, operation, construction or functionality) shall be identified using appropriate IC and ICV.

(g)Requirements after Job Completion are mandatory (M).

9.3.4S1000D Chapter 3.4 Interchange of Data Modules. As detailed in Sections 2 and 4 of this Part of this Defence Standard.

9.3.5S1000D Chapter 3.5 Application of SGML. As per S1000D, except for the following:

9.3.5.1 Description of Attribute Lists . As per S1000D except for the changes detailed below:

1(UNCLASSIFIED),

2(RESTRICTED),

3(CONFIDENTIAL),

4(SECRET), 5(TOP SECRET)

14

DEF STAN 00-60 (PART 10)/3

(b) %SECUR; -CONTENT SECURITY MARKING -Declared Value - 1(UNCLASSIFIED), 2(RESTRICTED), 3(CONFIDENTIAL), 4(SECRET),

5(TOP SECRET)

(c) In-order to permit linking using <xref> to <refdm> the following modifications are to be permitted to the S1000D DTD attribute list to the <avee> and <age> elements respectively located in the dmc.ent file.

1 <! ATTLIST avee id ID #IMPLIED>

2 <! ATTLIST age id ID #IMPLIED>

9.3.5.2Document Type Definition (DTD). The DTD shall be as profiled in S1000D and shall be used for land and sea applications.

9.3.5.3SGML Declaration. The generic SGML declaration available within S1000D shall be

used.

9.3.5.4Tag Set. The S1000D tag set as defined in the DTD above shall be used. The tags shown in Table 1 have had their definitions changed for this standard:

Table 1 Revised Tag Set Definitions

15

DEF STAN 00-60 (PART 10)/3

Table 1 - continued

16

9.3.5.5 The Output Specification shall be as detailed at Section 9 of this Part of this Defence Standard.

9.3.6 S1000D Chapter 3.6 Updating of Data Modules. As detailed in Section 4 of this Part of this Defence Standard.

9.4 S1000D Chapter 4 Technical Publications. As per 1000D with the additions and exceptions detailed in Section 9 of this Part of this Defence Standard.

17