GB/T 18975.10-2023 Industrial automation systems and integration—Integration of life cycle data for process plants including oil and gas production facilities—Part 10: Conformance testing (English Version)
Industrial automation systems and integration—Integration of life cycle data for process plants including oil and gas production facilities—Part 10: Conformance testing
Industrial automation systems and integration - Integration of life cycle data for process plants including oil and gas production facilities - Part 10: Conformance testing
1 Scope
This document defines the principles and methods for conformance testing of software implementations of ISO 15926.
It provides guidance for developing test cases and testing procedures that cover the requirements specified in the ISO 15926 series and in different industry usage contexts, e. g. data exchange, use of reference data libraries and interface services.
This document provides guidance in addition to the conformance in the parts of ISO 15926.
Note 1: Guidance on conformance ISO 15926 testing of complex scenarios which represent integrated interoperability is outside the scope of this document.
Note 2: Guidance on the development of software that supports the way of file exchange in the simple scenario which represents unified interoperability is outside the scope of this document.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
conformance testing
process to determine whether an implementation meets the requirements of a standard
3.2
specified requirement
need or expectation that is stated
3.3
functional approach
ordered functional approach that satisfy a need or demand for a demonstration that specified requirements (3.2) are fulfilled
Note: The three functions are selection, determination, and review and attestation.
3.4
software implementation layer
conceptual model that characterizes the software implementation
3.5
information exchange layer
particular conceptual model based on the software implementation layers (3.4) that characterizes the information exchange between computing system
3.6
ontology
formal statement of an understanding of the world
Note 1: An ontology can be represented in any language. It need not be represented in a language specifically designed for ontologies, such as OWL. An ontology can have different representations.
Note 2: An ontology does not specify what data shall be recorded about the world.
Note 3: The ontology defined by this document is principally concerned with the world outside a computer system.
[Source: GB/Z 18975.12-202×, 3.1.3]
4 Principles and methods
4.1 Conformance testing
Conformance testing of software implementations of ISO 15926 (conformance to the ISO 15926 series) shall be performed according to the functional approach, which is described in ISO/IEC 17000.
The testing can be done by first, second and/or third party.
Note: The adoption of ISO/IEC 17060 can build the credibility of conformance testing
4.2 Conformance to the ISO 15926 series
4.2.1 Conformance to ISO 15926-1
Conformance testing of software implementations of ISO 15926 means conformance to ISO 15926-1, if and only if all the requirements stated by the users of a software product and/or the implementer are fulfilled. A statement of conformance shall be prepared to state all means of communicating that the fulfilment of specified requirements has been successfully demonstrated.
ISO 15926-1 describes the activity, activity analysis, and modelling methods. The activity model is shown in Figure 1.
4.2.2 ISO 15926-1 conformance scenarios
Within the ISO 15926-1 activity model, there is a domain and range of scenarios, each of which results in various complexity of the software implementations of ISO 15926:
- scenario of handover, including sending and receiving files conforming to parts of ISO 15926;
- scenario of integration including using software programs that support the full span of design, engineering, construction, operation, and maintenance.
For each scenario, the following information shall be collected and recorded, but not limited to:
- overview (of scenario conformance);
- general (of the scenario of the annex and systems involved);
- procedure (steps of the workflow of handover or integration);
- aspects to be validated (verification);
- detailed validation (verification);
- not in scope (define what is not included in the workflow steps but useful to know).
Conformance testing of software implementations of ISO 15926 shall be executed in accordance with the scenario. Moreover, by applying the functional approach, the scenario shall demonstrate that the commissioned system fulfils specified requirements.
To perform the functional approach, the following activities, but not limited to, shall be conducted:
- selection (of information): planning and preparation activities to collect and produce all information and input needed for the subsequent determination functions;
- determination (gather evidence): developing complete information regarding fulfilment of the specified requirements by the object of conformity assessment or its sample;
- review (of evidence) and attestation (to conformity): constituting the final stage of checking before taking the important decision as to whether the purpose of conformity assessment has been reliably demonstrated to fulfil the specified requirements.
The specific application of the functional approach shall be documented by the conformance testing plan.
An appropriate set of validation and/or verification rules shall be selected and applied by referring to Annexes A, B, C, D, E and E. The candidate set of verification rules shall include, but not be limited to, the following (see Figure 3):
- all applications at layer 1 shall adopt Annex A;
- all applications at layer 2 shall adopt Annex B;
- an applications at layer 3 that claims conformance to ISO/TS 15926-7 and ISO/TS 15926-8 shall refer to Clause 5 for the description of the methodology and adopt the conformance rules given in Annex C:
- an application at laver 3 that claims conformance to ISO/TS 15926-11 shall refer to Clause 6 for the description of the methodology and adopt the conformance rules given in Annex D;
- an application at layer 3 that claims conformance to ISO/TS 15926-12 shall adopt Annex E;
- an application at layer 3 that claims conformance to ISO 15926-13 shall adopt Annex F.
Note: This selection of annexes can be interpreted as conformance clauses used in the ISO 10303 series. Moreover, the particular selection of annex to test the conformance can be described as the conformance class of the particular part of the ISO 15926 series.
4.2.3 Conformance testing in accordance with ISO 15926-1
The software implementation of ISO 15926 consists of four layers. For each selected layer, the specific functional approach in accordance with the following shall be applied.
- Role and scope of the software implementation (layer 1): This is to define the “what” portion of the software implementation of ISO 15926 in terms of the role and scope. Based on the activity model in ISO 15926-1, actual placement of the role and scope will be identified. The conformance testing plan or its equivalent shall be documented. Role and scope shall be examined by referring to Annexes A and B.
- Content of the software implementation (layer 2): The particular content of the software implementation of ISO 15926 shall be defined based on information defined in above layer 1. It is the layer where the particular information and/or product model(s) referring the entities and relationships of ISO 15926-2 and accompanying domain and range of ISO/TS 15926-4 or relent reference data library (RDL) based on ISO/TS 15926-6 (the whole integration model) shall be defined and assessed. Use of context shall be examined by referring Annexes A and B.
- Semantics of the software implementation (layer 3): The particular semantics of the software implementation shall be designed by selecting the preferred combination of the part(s) of the ISO 15926 series. Both the source and target application shall be mapped to the particular information and/or product model(s) defined in the above layer 2. Use of semantic shall be examined by referring to Annexes C to E.
- Syntax and storage of the software implementation (layer 4): The syntax and storage shall be defined by the actual implementation of language and storage of the preferred part(s) of the ISO 15926 series. Conformance testing can test, but not limited to, correct use of syntax, URI, and model which are defined in selected implementation languages.
At each layer, conformance testing of a software implementation of ISO 15926 shall be conducted to see if a particular commissioned system meets the user requirements. Furthermore, depending on the software implementation layer, conformance rules defined in accompanying annexes shall be selected and used to determine the conformance, and reviewed and attested the results as a part of the conformance. See Table 1 for an overall summary.
Standard
GB/T 18975.10-2023 Industrial automation systems and integration—Integration of life cycle data for process plants including oil and gas production facilities—Part 10: Conformance testing (English Version)
Standard No.
GB/T 18975.10-2023
Status
valid
Language
English
File Format
PDF
Word Count
20500 words
Price(USD)
615.0
Implemented on
2024-4-1
Delivery
via email in 1~3 business day
Detail of GB/T 18975.10-2023
Standard No.
GB/T 18975.10-2023
English Name
Industrial automation systems and integration—Integration of life cycle data for process plants including oil and gas production facilities—Part 10: Conformance testing
Industrial automation systems and integration - Integration of life cycle data for process plants including oil and gas production facilities - Part 10: Conformance testing
1 Scope
This document defines the principles and methods for conformance testing of software implementations of ISO 15926.
It provides guidance for developing test cases and testing procedures that cover the requirements specified in the ISO 15926 series and in different industry usage contexts, e. g. data exchange, use of reference data libraries and interface services.
This document provides guidance in addition to the conformance in the parts of ISO 15926.
Note 1: Guidance on conformance ISO 15926 testing of complex scenarios which represent integrated interoperability is outside the scope of this document.
Note 2: Guidance on the development of software that supports the way of file exchange in the simple scenario which represents unified interoperability is outside the scope of this document.
2 Normative references
There are no normative references in this document.
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
conformance testing
process to determine whether an implementation meets the requirements of a standard
3.2
specified requirement
need or expectation that is stated
3.3
functional approach
ordered functional approach that satisfy a need or demand for a demonstration that specified requirements (3.2) are fulfilled
Note: The three functions are selection, determination, and review and attestation.
3.4
software implementation layer
conceptual model that characterizes the software implementation
3.5
information exchange layer
particular conceptual model based on the software implementation layers (3.4) that characterizes the information exchange between computing system
3.6
ontology
formal statement of an understanding of the world
Note 1: An ontology can be represented in any language. It need not be represented in a language specifically designed for ontologies, such as OWL. An ontology can have different representations.
Note 2: An ontology does not specify what data shall be recorded about the world.
Note 3: The ontology defined by this document is principally concerned with the world outside a computer system.
[Source: GB/Z 18975.12-202×, 3.1.3]
4 Principles and methods
4.1 Conformance testing
Conformance testing of software implementations of ISO 15926 (conformance to the ISO 15926 series) shall be performed according to the functional approach, which is described in ISO/IEC 17000.
The testing can be done by first, second and/or third party.
Note: The adoption of ISO/IEC 17060 can build the credibility of conformance testing
4.2 Conformance to the ISO 15926 series
4.2.1 Conformance to ISO 15926-1
Conformance testing of software implementations of ISO 15926 means conformance to ISO 15926-1, if and only if all the requirements stated by the users of a software product and/or the implementer are fulfilled. A statement of conformance shall be prepared to state all means of communicating that the fulfilment of specified requirements has been successfully demonstrated.
ISO 15926-1 describes the activity, activity analysis, and modelling methods. The activity model is shown in Figure 1.
4.2.2 ISO 15926-1 conformance scenarios
Within the ISO 15926-1 activity model, there is a domain and range of scenarios, each of which results in various complexity of the software implementations of ISO 15926:
- scenario of handover, including sending and receiving files conforming to parts of ISO 15926;
- scenario of integration including using software programs that support the full span of design, engineering, construction, operation, and maintenance.
For each scenario, the following information shall be collected and recorded, but not limited to:
- overview (of scenario conformance);
- general (of the scenario of the annex and systems involved);
- procedure (steps of the workflow of handover or integration);
- aspects to be validated (verification);
- detailed validation (verification);
- not in scope (define what is not included in the workflow steps but useful to know).
Conformance testing of software implementations of ISO 15926 shall be executed in accordance with the scenario. Moreover, by applying the functional approach, the scenario shall demonstrate that the commissioned system fulfils specified requirements.
To perform the functional approach, the following activities, but not limited to, shall be conducted:
- selection (of information): planning and preparation activities to collect and produce all information and input needed for the subsequent determination functions;
- determination (gather evidence): developing complete information regarding fulfilment of the specified requirements by the object of conformity assessment or its sample;
- review (of evidence) and attestation (to conformity): constituting the final stage of checking before taking the important decision as to whether the purpose of conformity assessment has been reliably demonstrated to fulfil the specified requirements.
The specific application of the functional approach shall be documented by the conformance testing plan.
An appropriate set of validation and/or verification rules shall be selected and applied by referring to Annexes A, B, C, D, E and E. The candidate set of verification rules shall include, but not be limited to, the following (see Figure 3):
- all applications at layer 1 shall adopt Annex A;
- all applications at layer 2 shall adopt Annex B;
- an applications at layer 3 that claims conformance to ISO/TS 15926-7 and ISO/TS 15926-8 shall refer to Clause 5 for the description of the methodology and adopt the conformance rules given in Annex C:
- an application at laver 3 that claims conformance to ISO/TS 15926-11 shall refer to Clause 6 for the description of the methodology and adopt the conformance rules given in Annex D;
- an application at layer 3 that claims conformance to ISO/TS 15926-12 shall adopt Annex E;
- an application at layer 3 that claims conformance to ISO 15926-13 shall adopt Annex F.
Note: This selection of annexes can be interpreted as conformance clauses used in the ISO 10303 series. Moreover, the particular selection of annex to test the conformance can be described as the conformance class of the particular part of the ISO 15926 series.
4.2.3 Conformance testing in accordance with ISO 15926-1
The software implementation of ISO 15926 consists of four layers. For each selected layer, the specific functional approach in accordance with the following shall be applied.
- Role and scope of the software implementation (layer 1): This is to define the “what” portion of the software implementation of ISO 15926 in terms of the role and scope. Based on the activity model in ISO 15926-1, actual placement of the role and scope will be identified. The conformance testing plan or its equivalent shall be documented. Role and scope shall be examined by referring to Annexes A and B.
- Content of the software implementation (layer 2): The particular content of the software implementation of ISO 15926 shall be defined based on information defined in above layer 1. It is the layer where the particular information and/or product model(s) referring the entities and relationships of ISO 15926-2 and accompanying domain and range of ISO/TS 15926-4 or relent reference data library (RDL) based on ISO/TS 15926-6 (the whole integration model) shall be defined and assessed. Use of context shall be examined by referring Annexes A and B.
- Semantics of the software implementation (layer 3): The particular semantics of the software implementation shall be designed by selecting the preferred combination of the part(s) of the ISO 15926 series. Both the source and target application shall be mapped to the particular information and/or product model(s) defined in the above layer 2. Use of semantic shall be examined by referring to Annexes C to E.
- Syntax and storage of the software implementation (layer 4): The syntax and storage shall be defined by the actual implementation of language and storage of the preferred part(s) of the ISO 15926 series. Conformance testing can test, but not limited to, correct use of syntax, URI, and model which are defined in selected implementation languages.
At each layer, conformance testing of a software implementation of ISO 15926 shall be conducted to see if a particular commissioned system meets the user requirements. Furthermore, depending on the software implementation layer, conformance rules defined in accompanying annexes shall be selected and used to determine the conformance, and reviewed and attested the results as a part of the conformance. See Table 1 for an overall summary.
