DI-TMSS-82332

S1000D Data Management Requirement List

Specifies the format and content requirements for the S1000D Data Management Requirement List used to initiate Data Module templates in the Navy's Common Source Database.

Approval DateNovember 16, 2020

AMSC NumberN1028

Preparing ActivitySH

Project NumberTMSS 2020-013

OPR—

DTIC Applicable—

GIDEP Applicable—

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The S1000D Data Management Requirement List shall be used to initiate Data Module templates in the Navy's Common Source Database.

This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirements as delineated in the contract.

This DID is applicable to all new contracts and solicitations that acquire S1000D Issues 4.0 and newer based technical documentation.

The DID may also be applicable to technical documentation already in production for major changes and upgrades.

S1000D, referenced in this Data Item Description, can be obtained at www.s1000d.org.

Preparation Instructions

1Reference documentsThe applicable issue of any documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.

2FormatThe Data Management Requirement List shall be presented in a format similar to that of Figure 1 and shall contain the following columns of information.

3ContentThe content of the columns identified below shall follow the requirements of S1000D. All columns listed below are mandatory. The Learn Code (LCN) and Learn Event Code (LEC) columns are populated when applicable; population of all other columns of information is always mandatory. The columns shall contain the Standard Numbering System breakdown as specified in S1000D. The Data Management Requirement List shall contain all the appropriate Data Modules required to generate the applicable technical documentation.

3.1Title DMC ColumnThe text "DMC" shall be entered in the Title DMC column.

3.2Master Naming scheme (MNS) ColumnThe Master Naming Scheme shall be specific to NAVSEA's Common Source Database and shall contain Model Identification Code and shall identify the project to which the data applies.

3.3Model Identification Code (MI) ColumnThe Model Identification Code (MI) identifies the project to which the data applies and shall be the point of reference for all applicability information. The model identification code shall include all related model variants.

3.4System Difference Code (SDC) ColumnThe System Difference Code (SDC) indicates alternative versions of the system and subsystem/sub-subsystem identified by the Standard Numbering System without affecting the type, model or variant identity.

3.5System Code (SC) ColumnThe System Code (SC) is comprised of the material item category code and a code representing the general systems and the basic structure of the Product. This is the first portion of the Standard Numbering System.

3.6Subsystem Code (SSC) ColumnThe Subsystem Code (SSC) is the subsystem portion of the second element of the Standard Numbering System and describes the further breakdown of the system.

3.7Sub-SubSystem Code (SSSC) ColumnThe Sub-SubSystem Code (SSSC) is the sub-subsystem portion of the second element of the Standard Numbering System and describes the further breakdown of the system.

3.8Assy Code (AC) ColumnThe Assy Code (AC) is the third element of the Standard Numbering System. It provides identification for units in complex systems.

3.9Disassembly Code (DC) ColumnThe Disassembly Code (DC) provides the breakdown condition of an assembly to which maintenance information applies.

3.10Disassembly Code Variant (DCV) ColumnThe Disassembly Code Variant (DCV) designates alternative items of equipment or components differing slightly in design but not enough to warrant a change of the system difference code.

3.11Information Code (IC) ColumnThe Information Code (IC) identifies the type of information within a data module.

3.12Information Code Variant (ICV) ColumnThe Information Code Variant (ICV) refines the Information Code to be more specific.

3.13Item Location Code (ILC) ColumnThe Item Location Code (ILC) identifies where the maintenance task will be performed in relation to the equipment/system.

3.14Learn Code (LCN) ColumnThe Learn Code (LCN) describes the type of human performance technology or training information that is in the content of the data module.

3.15Learn Event Code (LEC) ColumnThe Learn Event Code (LEC) identifies which branch of the learn Schema is being used.

3.16Techname ColumnThe Techname identifies the nomenclature of the hardware or function.

3.17Infoname ColumnThe Infoname contains the short description of the information code.

3.18Type ColumnThe Type indicates the data module type to NAVSEA's Common Source Database. This column shall be populated with selections from Table 1. Before using a schema, check the NAVSEA S1000D Tagging and Authoring Guide to ensure that it is supported. The Tagging and Authoring Guidelines can be obtained from https://www.navsea.navy.mil/Home/Warfare-Centers/NSWC-Carderock/Resources/Technical-Information-Systems/Navy-XML-SGML-Repository/DTDs-Schemas/NAVSEA-S1000D-Tools-Repository/.

4Media RequirementThe Data Management Requirement List shall be presented in an electronic file ASCII, comma-delimited file.

References

S1000D https://www.s1000d.org

NAVSEA S1000D Tagging and Authoring Guide https://www.navsea.navy.mil/Home/Warfare-Centers/NSWC-Carderock/Resources/Technical-Information-Systems/Navy-XML-SGML-Repository/DTDs-Schemas/NAVSEA-S1000D-Tools-Repository/

Figures

Figure 1. Example of Spreadsheet Layout

Figure Table 1. Data Module Type Table

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer