Partners save 15% on every standard

Valid

GB/T 42381.130-2023Data quality - Part 130: Master data: Exchange of characteristic data: Accuracy (English PDF)

数据质量第130部分：主数据：特征数据交换：准确性

Open the GB/T 42381.130-2023 preview as PDF

Preview — first pages of GB/T 42381.130-2023 (full document: 14 pages)

This is a limited preview

Buy now to download the full PDF (14 pages)

Issued by

SAMR; SAC

Level / Type

National · Recommended

Issue date

September 7, 2023

Implementation date

April 1, 2024

Scope

GB/T 42381.130-2023 is the English-translated version of 数据质量第130部分：主数据：特征数据交换：准确性.

GB/T 42381.130-2023 is Part 130 of the Chinese data quality series, and covers the accuracy of master data exchanged as characteristic data. Master data - the part catalogues, material properties and product characteristics passed between an OEM and its suppliers - is exchanged constantly and trusted implicitly, and a wrong value in it propagates into design, purchasing and manufacturing before anyone notices. Accuracy here is a property that must be stated and evidenced rather than assumed, which is what the standard provides machinery for. It sets the accuracy data model, the data accuracy statement, assertion and records, and the conformance requirements, with a normative annex on document identification and informative annexes giving information to support implementation and the code used in the examples. It took effect on 1 April 2024.

Document preview — GB/T 42381.130-2023

National Standard of the People's Republic of China

ICS: 25.040.40
Classification: N10

Issued by: State Administration for Market Regulation; Standardization Administration of the PRC

1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviated terms
5 General
6 Accuracy data model

Foreword

This document is an optional addition to GB/T 42381.120 and specifies requirements for representation and exchange of information about accuracy of master data that consists of characteristic data.

Note 1: ISO 8000-110 specifies that such data be represented as property values. ISO 8000-120 provides additional requirements for property values when data provenance information needs to be captured.

This document does not specify a complete model for characteristic data, nor does it specify an exchange format for characteristic data with data accuracy information.

Note 2: This is done in other standards that reference this document, e.g. ISO/TS 22745-40.

The following are within the scope of this part of this document:

- requirements for capture and exchange of data accuracy information in the form of statements and assertions of data accuracy;

- conceptual data model for data accuracy information in the form of statements and assertions of data accuracy.

The following are outside the scope of this document:

- requirements for data accuracy;

Note 3: The requirements for data accuracy depend on many factors, e.g. the kind of data, how the data are being used, industry, and needs of the partners exchanging the data. It is not possible to state general requirements for data accuracy.

- exchange format for data accuracy information;

- scheme for registering and resolving organization identifiers and person identifiers;

- accuracy of data that are not characteristic data represented as property values;

- syntax of identifiers;

- resolution of identifiers.

Some of the requirements in this document can apply to exchange of data that is not master data which consists of characteristic data represented as property values.

Annex A specifies the identification of this document in the information system.

Annex B gives the information to support implementations.

1 Scope

This document is an optional addition to GB/T 42381.120 and specifies requirements for representation and exchange of information about accuracy of master data that consists of characteristic data.

This document does not specify a complete model for characteristic data, nor does it specify an exchange format for characteristic data with data accuracy information.

Note 2: This is done in other standards that reference this document, e.g. ISO/TS 22745-40.

The following are within the scope of this part of this document:

- requirements for capture and exchange of data accuracy information in the form of statements and assertions of data accuracy;

- conceptual data model for data accuracy information in the form of statements and assertions of data accuracy.

The following are outside the scope of this document:

- requirements for data accuracy;

- exchange format for data accuracy information;

- scheme for registering and resolving organization identifiers and person identifiers;

- accuracy of data that are not characteristic data represented as property values;

- syntax of identifiers;

- resolution of identifiers.

Some of the requirements in this document can apply to exchange of data that is not master data which consists of characteristic data represented as property values.

Annex A specifies the identification of this document in the information system.

Annex B gives the information to support implementations.

2 Normative references

The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

ISO 8000-2 Data quality- Part 2: Vocabulary

ISO 8000-120 Data quality - Part 120: Master data : Exchange of characteristic data: Provenance Note: GB/T 42381.120-2023 Data quality - Part 120 : Master data : Exchange of characteristic data : Provenance (ISO 8000-120:2016, IDT)

2 Normative references

ISO 8000-2 Data quality- Part 2: Vocabulary

3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 8000-2 apply.

3 Terms and definitions

For the purposes of this document, the terms and definitions given in ISO 8000-2 apply.

4 Abbreviated terms

UML: Unified Modeling Language

XML: Extensible Markup Language

4 Abbreviated terms

UML: Unified Modeling Language

XML: Extensible Markup Language

5 General

A data provider may declare the accuracy of data through either a statement (see Clause 7) or an assertion (see Clause 8).

5 General

A data provider may declare the accuracy of data through either a statement (see Clause 7) or an assertion (see Clause 8).

6.1 Referenced types and entities

The following types and entities are used by the accuracy model:

- ISO_6523_identifier, defined in ISO 8000-120;

- date_and_time, defined in ISO 8000-120;

- property_value_assignment, defined in ISO 8000-120.

6.1 Referenced types and entities

The following types and entities are used by the accuracy model:

- ISO_6523_identifier, defined in ISO 8000-120;

- date_and_time, defined in ISO 8000-120;

- property_value_assignment, defined in ISO 8000-120.

6.2 Diagram

The UML class diagram for the accuracy model is given in Figure 1.

Note: The entity property_value_assignment is the intersection point between this data model and the target data model: the model of data for which accuracy information is to be recorded. When the data model in Clause 6 is integrated with the target data model, this entity needs to be replaced with the appropriate entity from the target data model.

An accuracy_event is an event for which data accuracy information is recorded.

Attribute definitions:

details: the details of the accuracy_event.property

Note 1: This could include the text of the statement or assertion of accuracy.

event_type: the kind of accuracy_event.

The value shall be one of the following:

- statement: a statement of accuracy was provided for the property value;

- assertion: an assertion of accuracy was provided for the property value.

method: accuracy_method used to record the accuracy for the accuracy_event.

organization_ref: the unambiguous identifier of the organization and possibly the subdivison of the organization that performed the event, conforming to the structure defined in ISO/ IEC 6523-1 and assigned in accordance with ISO/IEC 6523-2.

person_ref: the identifier assigned by the organization to the person who performed the event.

Note 2: The identifier need only be unique within the organization.

Note 3: The format of the identifier is not specified in this document.

when: the point in time at which the event took place.

Each accuracy_event has as its method zero, one, or many accuracy_method objects. Each accuracy_ method is the method for exactly one accuracy_event.

Each accuracy_event records the accuracy for exactly one property_value_assignment. Each property_ value_assignment has its accuracy recorded by one or many accuracy_event objects.