- •Preface
- •Section One. General
- •0 Introduction
- •1 Scope
- •2 Related Documents
- •3 Definitions
- •4 Abbreviations
- •Section Two. Electronic Documentation Process
- •5 Introduction
- •6 In-Process Review
- •7 Quality Audit
- •Section Three. Application of S1000D
- •8 Introduction
- •9 Detailed Application
- •Section Four. Electronic Documentation Data Base, Data Transfer & Data Control.
- •10 Introduction
- •11 Data Base Structure
- •12 DM Interchange
- •13 Output Deliverable Control
- •Section Five. Non-Textual Information
- •14 Introduction
- •15 Detailed Requirements
- •16 Attaching Parts
- •Section Six. Parts Information
- •17 Introduction
- •18 Preparation of Parts Information (General)
- •19 Provision of Parts Information
- •Section Seven. Operator Information
- •20 Introduction
- •21 Scope of Information
- •22 Information Requirements
- •23 Checklists
- •24 Identification of DM
- •Section Eight. Maintenance Information
- •25 Introduction
- •26 General
- •27 Preventive Maintenance
- •28 Maintenance Resource
- •Section Nine. Publications Output
- •29 Introduction
- •30 Publication Production Mechanism
- •Table 1 Revised Tag Set Definitions
- •Table 2 Spares Lists DM Information Requirements
- •Table 3 Material Item Category Code (MICC)
- •Table 4 Material Item Sub-Category Code (MISCC)
- •Table 5 Major Zone Identification Numbers
- •Table 6 Sub Zone Identification Numbers
- •Table 7 Zone Identification Numbers
- •Table 8 Major Zone Identification Number.
- •Table 9 Sub Zone Identification Number
- •Table 10 Zone Identification Numbers
- •Table 11 Equipment Zone Identification Numbers
- •Table 12 Equipment Sub Zone Identification Numbers
- •Table 13 LRU Zone Identification Numbers
- •Figure 1 Data Module Code
- •Figure 2 DMC for S1000D application
- •Figure 3 Major Zones
- •Figure 4 Major Zones
- •Figure 5 Sub Zones
- •Figure 6 Zones
- •Figure 7 Access Codes
- •Figure 8 Major Zones
- •Figure 9 Sub Zones
- •Figure 10 Zones
- •Figure 11 Equipment Zones
- •Figure 12 Equipment Sub Zones
- •Figure 13 LRU Zones
- •Figure 14 Data Module Codes for Military Systems and Associated Equipments
DEF STAN 00-60 (PART 10)/3
Section Nine. Publications Output
29 Introduction
29.1 Technical Publications as specified in the contract shall be in the format of either paper technical publications or an IETP as defined in AECMA S1000D except for the following :
30 Publication Production Mechanism
30.1 Publication Construction
30.1.1 Paper. The FPDB, for a paper publication, shall be neutral and independent of the delivery software. It shall contain a hierarchical document structure as specified by the Publications Module comprising:
(a)The required DM from the DPDB.
(b)Generated data. (Front matter, Back matter, Table of Contents (TOC), List Of Applicable Publications (LOAP), index, , list of illustrations, highlights, references, glossary, warnings etc, symbols, mod list, spares lists, support equipment, Special Tools and Test Equipment (STTE)).
30.1.2 IETP. Reference to CSDB in S1000D Chapter 4 is to be read as DPDB.
30.1.2.1FPDB, for an IETP-Linear (IETP-L), shall be neutral and independent of the delivery software and shall contain a hierarchical document structure as specified by the Publications Module as detailed in S1000D.
30.1.2.2FPDB, for an IETP-Database (IETP-D), shall be neutral and independent of the delivery software and shall contain a database document structure as specified by the Publications Module as detailed in S1000D.
30.1.2.3FPDB, for an IETP-Integrated (IETP-I), shall be neutral and independent of the delivery software and shall contain the same elements as an IETP-D FPDB with the addition of links to external databases and systems.
30.1.3 The final end user deliverable publication shall be constructed from the FPDB.
30.2 Output Specification
30.2.1 General
30.2.1.1 The Contractor shall produce and exercise version control on any output specification required for the production of technical publications. The output specification and the procedure by which this is achieved shall be made available to the Customer.
27
DEF STAN 00-60 (PART 10)/3
30.2.2 IETP Process Stages and Types. The IETP shall conform to S1000D together with the following requirements.
30.2.2.1 Change Marks. It will be Publisher's responsibility to ensure that Change Marks are appropriately displayed on the publication delivered to the user according to the following rules:
(a)For Data Modules coded 'Changed' Change Marks shall be as specified in the Data Module.
(b)Data Modules coded 'New', 'Revised' or 'Reinstated' shall show a Change Mark against the entire Data Module.
(c)The space left by 'Deleted' Data Modules shall be appropriate indicated by Change Marks.
(d)The Publisher must process Data Module Change Marks by considering all the changes to a Data Module since the last publication output of each specific publication. NB. Data Modules' Reason Codes and Change Marks only reflect changes from the previous issue. The Data Module preparer cannot consolidate changes in ignorance of the Output Publication issue standard.
(e)The above shall not apply to the initial issue of each Output Publication which shall not contain any Change Marks.
30.2.2.2 Presentation and Formatting. The presentation of textual aspects of the IETP shall conform to requirements specified at annex E to this Part of the Defence Standard.. In addition the IETP designer shall maintain a consistent user interface throughout the data presentation. The principles detailed in S1000D shall apply except for that symbols and icons shall be consistent throughout the IETP.
28
DEF STAN 00-60 (PART 10)/3
ANNEX A
Document Codes
A.1 General
A.1.1 The Standard Numbering System (SNS) of S1000D is replaced by the document codes detailed in this annex and appendices A to E.
A.1.2 Five separate sets of alphanumeric document codes have been developed to replace the SNS detailed in S1000D, covering the categories of Ship, Electronic/Automated Software, Aircraft/Missile, Surface/Primary Vehicle and Ordnance. These are denoted by the Material Item Category Code (MICC) in table 3.
Table 3 Material Item Category Code (MICC)
CODE |
DESCRIPTION |
DEFINITION |
A |
Ship |
The ship system refers to the complex of equipment |
|
System |
(hardware/software), data, services and facilities |
|
|
required to attain the capability of operating or |
|
|
supporting the operation of naval weapons, or |
|
|
performing other naval tasks at sea. |
B |
Electronic/ |
The electronic/automated software system element |
|
Automated Software |
refers to the complex of equipment (hardware/ |
|
System |
software), data, services and facilities required to |
|
|
develop and produce an electronic, automated, or |
|
|
software system capability such as command and |
|
|
control system, radar system, communications system, |
|
|
information system, sensor system, navigation/ |
|
|
guidance system, electronic warfare system, support |
|
|
system, etc. The decision rule to differentiate between |
|
|
the Electronic/Automated Software System and other |
|
|
defence materiel is : When the item is a stand alone |
|
|
system or used on several systems, but not accounted |
|
|
for in these other systems, the electronic/automated |
|
|
software system category will be used. When the |
|
|
opportunity to collect lower level information on |
|
|
electronic and software exists, regardless of which |
|
|
defence materiel category code is selected the |
|
|
structure and the structure and definitions under this |
|
|
code apply. |
|
|
|
A-1
DEF STAN 00-60 (PART 10)/3
ANNEX A (CONTINUED)
|
|
Table 3 - concluded |
|
|
|
CODE |
DESCRIPTION |
DEFINITION |
C |
Aircraft System/ |
The aircraft system refers to the complex of equipment |
|
Missile System |
(hardware/software), data, services and facilities |
|
|
required to attain the capability of employing those |
|
|
fixed or moveable wing, rotary wing, or compound |
|
|
wing, manned/unmanned air vehicles designed for |
|
|
powered or unpowered (glider) guided flight. |
|
|
The missile system refers to the complex of |
|
|
equipment(hardware/software) data services and |
|
|
facilities required to develop and produce the |
|
|
capability of employing a missile weapon in an |
|
|
operational environment to produce the destructive |
|
|
effect on selected targets. |
D |
Surface |
The surface vehicle system refers to the complex of |
|
Vehicle |
equipment (hardware/software), data, services and |
|
System |
facilities required to develop and produce a vehicle |
|
|
system with the capability to navigate over the surface. |
|
|
Surface vehicle category includes vehicles primarily |
|
|
intended for general purpose applications and those |
|
|
intended for mating with specialized payloads. This |
|
|
category also includes cargo and logistics vehicles, |
|
|
mobile work units and combat vehicles. It also |
|
|
includes combat vehicles serving as armoured |
|
|
weapons platforms, reconnaissance vehicles, |
|
|
howitzers and amphibians. |
E |
Ordnance |
The ordnance system refers to the complex of |
|
System |
equipment (hardware/software) data services and |
|
|
facilities required to develop and produce the |
|
|
capability for applying munitions to a target. It |
|
|
includes the munitions (nuclear, biological, chemical, |
|
|
psychological and pyrotechnic) and the means of |
|
|
launching or firing the munitions. It includes torpedo |
|
|
systems, bombs, combined effects munitions, sensor |
|
|
fuzed weapons, towed/man-portable guns and |
|
|
ammunition. Excluded are aerospace guided missiles, |
|
|
land, sea and air delivery vehicles. |
A.1.3 The document code is further broken down into seventeen functional areas, under the Material Item Sub-Category Code (MISCC) detailed in table 4. This code forms the first character of the SNS.
A-2