GJB 5882-2006

Classification and codes of product technical documents

产品技术文件分类与代码

Standard Type
GJB
ICS
N/A
CCS
N/A
Status
N/A
Issue Date
2006-12-15
Implementation
2007-05-01
Centralized Committee
国防科技工业标准化研究中心 / Standardization Research Center of National Defense Science and Technology Industry
Issuing Authority
国防科学技术工业委员会 / Commission of Science, Technology and Industry for National Defense

Catalogue

前言 → 1 范围 → 2 规范性引用文件 → 3 术语和定义 → 4 技术文件分类原则与方法 → 5 技术文件类型及代码 Foreword → 1 Scope → 2 Normative References → 3 Terms and Definitions → 4 Principles and Methods of Classification of Technical Documents → 5 Types and Codes of Technical Documents

Scope

This standard specifies the classification principles and methods for technical documents formed during product development and production, and specifies type codes. This standard applies to the information management of technical documents during product development and production.

本标准规定了产品研制,生产过程中所形成的技术文件的分类原则和分类方法,并规定了类型代码。本标堆适用于产品研制。生产过程中技术文件的信息化管理。

Normative References

GJB 9001A

Keywords

技术文件 (technical documents) 分类 (classification) 代码 (codes) 产品研制 (product development) 生产 (production) 信息化管理 (information management)

Application Summary AI generated

This standard is used by organizations involved in product development and production within the national defense science and technology industry. It provides a systematic classification and coding scheme for technical documents, enabling efficient information management. This is crucial for improving document retrieval, ensuring consistency, and maintaining traceability throughout the product lifecycle.

该标准由国防科技工业领域的产品研制和生产单位使用,用于对技术文件进行系统分类和编码。它帮助实现技术文件的信息化管理,提高文件检索和利用效率,确保产品全生命周期中文件的一致性和可追溯性。

AI Summary AI generated

GJB 5882-2006, titled 'Classification and codes of product technical documents', specifies the principles, methods, and type codes for classifying technical documents generated during product development and production. It uses a facet classification approach based on three dimensions: development/production stage, document technical content, and document expression form, without distinguishing between hardware and software. Documents are categorized into six stages: demonstration, concept, engineering development, design finalization, production finalization, and batch production, each assigned a single Latin letter code. This standard facilitates information management of technical documents, enhancing efficiency and consistency.

GJB 5882-2006《产品技术文件分类与代码》规定了产品研制和生产过程中技术文件的分类原则、方法及类型代码。标准采用面分类法,从研制生产阶段、文件技术内容和表达形式三个维度进行分类,不区分硬件和软件产品。技术文件按阶段分为论证、方案、工程研制、设计定型、生产定型和批生产六类,每类用一位拉丁字母代码表示。该标准适用于技术文件的信息化管理,有助于提高文件管理效率和一致性。

Key Sentences extracted from text

1.

本标准规定了产品研制,生产过程中所形成的技术文件的分类原则和分类方法,并规定了类型代码。

2.

本标堆适用于产品研制。生产过程中技术文件的信息化管理。

3.

本标准采用面分类法。分别按产品研制生产阶段。文件技术内容。文件表达形式三个方面对技术文件进行分类。

4.

本标堆对产品的技术文件分类时不区分硬件产品。软件产品。

5.

按产品研制。生产阶段的不同阶段,产品技术文件分为: 论证阶段文件。方案阶段文件。工程研制阶段 (初样,试样或正样) 文件,设计定型阶段文件,生产定型阶段(工艺定型) 文件和批生产阶段文件。

7.

This standard specifies the classification principles and methods for technical documents formed during product development and production, and specifies type codes.

8.

This standard applies to the information management of technical documents during product development and production.

9.

This standard adopts the facet classification method, classifying technical documents according to three aspects: product development and production stages, document technical content, and document expression form.

10.

This standard does not distinguish between hardware products and software products when classifying product technical documents.

11.

According to different stages of product development and production, product technical documents are divided into: demonstration stage documents, concept stage documents, engineering development stage (prototype, sample, or final sample) documents, design finalization stage documents, production finalization stage (process finalization) documents, and batch production stage documents.

Transparency note: The application summary and key sentences on this page were automatically generated by AI from the standard's original text. This content has not been human-verified and should not be used for compliance or regulatory purposes. Always refer to the official standard document from the issuing authority.