- •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 Four. Electronic Documentation Data Base, Data Transfer & Data Control.
10 Introduction
10.1 This Section of this Part of this Defence Standard defines the requirements for the provision of an ED database, the transfer of data between data providers and data receivers and the control of this data. The basis of the ED database will be a CSDB, compliant with Section 3 of this Defence Standard.
11 Data Base Structure
11.1DPDB. A DPDB, if specified in the contract, shall contain the specific DM applicable to the equipment and in compliance with the DMRL.
11.2FPDB. A FPDB, if specified in the contract, shall contain all the necessary links to provide a source for a fully functional IETP for the end user. The format of the FPDB shall maintain compliance with the format of the DPDB as defined in this Part of this Defence Standard.
11.3IETP. An IETP, if specified in the contract, shall incorporate the display package agreed by the project.
12 DM Interchange
12.1 Media
12.1.1'DM shall be exchanged by means of magnetic tape or other agreed media in accordance with MIL-STD-1840, as agreed between the customer and the supplier with the following exceptions:
12.1.2The DTD as referred to in MIL-STD-1840B shall not be sent, if the DTD is already held by the Customer.
12.1.3The Format and Output Specification Instance (FOSI) as referred to in MIL-STD- 1840B shall not be sent.
12.1.4The record header ‘chglvl’ as defined in MIL-STD-1840B shall be set as CHG TYPE=OTHER, REV LEVEL=0, CHG LEVEL=0 and DATE= (Date/Time of generation of the MIL-STD-1840B Declaration file in YYYYMMDD/HHHH:SS format). eg chglvl: OTHER,0,0,19960105/1124:15
12.1.5Media labelling shall be in accordance with MIL-STD-1840B, with the additional minimum requirement to include Delivery Despatch Note (DDN) No. and Security Classification.
12.1.6'For sequential media, file Volume Identification shall be as defined in S1000D.
18
DEF STAN 00-60 (PART 10)/3
12.2 DM Export
12.2.1Prior to export, each DM shall be parsed, by the exporter, against the DTD version used to create that DM, to ensure structural compliance.
12.2.2A DDN detailing the sender, recipient, media identity, despatch data, security classification and any covering remarks, shall be generated to accompany each exchange of data.
12.2.3Each export of DM shall be accompanied by a Configuration Status List (CSL) defining the current issue of all issued DM which are the responsibility of the sender and indicating those DM included in the export.
12.3 DM Import
12.3.1On receipt of the data exchange media, the data file set shall be checked for compliance with the accompanying CSL, to ensure completeness and correctness.
12.3.2Each DM shall be parsed against the appropriate DTD as defined in the DM to ensure structural compliance.
12.3.3For each DM the issue number shall be checked to ensure that it follows sequentially from the existing DM issue number on the DPDB/FPDB.
12.3.4Should any DM fail any of the above checks it shall not be loaded to the DPDB/FPDB and details of the deficiencies shall be reported to the sender.
12.3.5The complete DPDB/FPDB contents shall be checked against the complete CSL to ensure compatibility between the sending and receiving databases.
12.3.6Where the Customer does not hold copies of the DPDB/FPDB and is only receiving transmission of DM for comment/review purposes, clauses 12.3.3, 12.3.4 &12.3.5 above do not apply.
13 Output Deliverable Control
13.1Delivery of any data output to the Customer shall be accompanied by a receipt acknowledgement to be returned by the recipient.
13.2The sender shall monitor the return of the receipt acknowledgements and follow up any non-receipts.
19