1、Designation: E3147 18Standard Practice forEvaluating DICONDE Interoperability of NondestructiveTesting and Inspection Systems1This standard is issued under the fixed designation E3147; the number immediately following the designation indicates the year oforiginal adoption or, in the case of revision
2、, the year of last revision. A number in parentheses indicates the year of last reapproval. Asuperscript epsilon () indicates an editorial change since the last revision or reapproval.1. Scope1.1 This practice describes procedures for evaluating DI-CONDE compliance of radiographic, ultrasonic and ed
3、dycurrent examination instruments and systems.1.2 This practice establishes no performance limits forexamination systems; if such acceptance criteria are required,these must be specified by the using parties. Where acceptancecriteria are implied herein they are for example only and aresubject to mor
4、e or less restrictive limits imposed by customersand end users controlling documents.1.3 The specific parameters to be evaluated, conditions andfrequency of test, and report data required, must also bedetermined by the user.1.4 This practice may be used for the evaluation of acomplete examination sy
5、stem, including search unit,instrument, interconnections, scanner fixtures and connectedalarm and auxiliary devices, primarily in cases where such asystem is used repetitively without change or substitution. Thispractice is not intended to be used as a substitute for calibrationor standardization of
6、 an instrument or system to inspect anygiven material.1.5 Alternate procedures, such as examples described in thispractice, or others, may only be used with customer approval.1.6 It is expected that the customer sets the requirements forthe level to which this practice be conformed, including thereq
7、uirements for which functionality and DICONDE interop-erability be incorporated for testing.1.7 Two customer types are targeted for usage: a high-levelpurchaser wishing to quickly assess results and a low-levelsystems developer wishing to understand the details about theextent of the results, as dis
8、cussed in Section 5.1.8 The values stated in SI units are to be regarded asstandard. No other units of measurement are included in thisstandard.1.9 This standard does not purport to address all of thesafety concerns, if any, associated with its use. It is theresponsibility of the user of this standa
9、rd to establish appro-priate safety, health, and environmental practices and deter-mine the applicability of regulatory limitations prior to use.1.10 This international standard was developed in accor-dance with internationally recognized principles on standard-ization established in the Decision on
10、 Principles for theDevelopment of International Standards, Guides and Recom-mendations issued by the World Trade Organization TechnicalBarriers to Trade (TBT) Committee.2. Referenced Documents2.1 ASTM Standards:E1316 Terminology for Nondestructive ExaminationsE2339 Practice for Digital Imaging and C
11、ommunication inNondestructive Evaluation (DICONDE)E2663 Practice for Digital Imaging and Communication inNondestructive Evaluation (DICONDE) for UltrasonicTest MethodsE2699 Practice for Digital Imaging and Communication inNondestructive Evaluation (DICONDE) for Digital Ra-diographic (DR) Test Method
12、sE2738 Practice for Digital Imaging and CommunicationNondestructive Evaluation (DICONDE) for ComputedRadiography (CR) Test MethodsE2767 Practice for Digital Imaging and Communication inNondestructive Evaluation (DICONDE) for X-ray Com-puted Tomography (CT) Test MethodsE2934 Practice for Digital Imag
13、ing and Communication inNondestructive Evaluation (DICONDE) for Eddy Current(EC) Test Methods2.2 DICOM StandardsNEMA Standards Publication PS3, Version 3 Digital Imag-ing and Communications in Medicine (DICOM)ACR-NEMA 300-1998 Digital Imaging and Communica-tions in Medicine3. Terminology3.1 Refer to
14、 Terminology E1316 for definitions of terms inthis practice.3.2 Definitions:1This practice is under the jurisdiction of ASTM Committee E07 on Nonde-structive Testing and is the direct responsibility of Subcommittee E07.11 on DigitalImaging and Communication in Nondestructive Evaluation (DICONDE).Cur
15、rent edition approved Feb. 1, 2018. Published February 2018. DOI: 10.1520/E314718.Copyright ASTM International, 100 Barr Harbor Drive, PO Box C700, West Conshohocken, PA 19428-2959. United StatesThis international standard was developed in accordance with internationally recognized principles on sta
16、ndardization established in the Decision on Principles for theDevelopment of International Standards, Guides and Recommendations issued by the World Trade Organization Technical Barriers to Trade (TBT) Committee.13.2.1 application entity (AE)a local or remote DICOM(DICONDE) service.3.2.2 AE titlethe
17、 name of the application entity, forexample, the name of the computer running the local or remoteservice, or other user-defined name of the application entity.3.2.3 connectivitythe ability to establish a connectionbetween two or more systems and exchange messages.3.2.4 DICONDE interconnectivitythe l
18、evel to which twoapplication entities can exchange messages using the DI-CONDE protocol.3.2.5 DICONDE interoperabilityability for two applica-tion entities to exchange composite information objects orinformation about normalized information objects and for eachentity to interpret, view, and present
19、that info in the same way.3.2.6 DICONDE validationthe assurance that the NDEsystem meets the needs of the purchaser and other identifiedstakeholders. It often involves acceptance with external enti-ties.3.2.7 DICONDE verificationthe evaluation of whether theNDE system conforms to the DICONDE standar
20、d. It is oftenan internal process.3.2.8 PS3NEMA DICOM standard publication.3.2.9 SCPa Service Class Provider (SCP) is a device thatacts as a server and “provides” a DICONDE service. SCP typesmost commonly include the storage type (C-STORE orC-MOVE) to accept data that is transmitted from anotherdevi
21、ce and the find type (C-FIND) to respond to searches(queries) for data and fulfill transmission requests. A devicemay serve as both SCP and SCU. Refer to PS3.4 for moreinformation. See Section 5 for diagram.3.2.10 SCUa Service Class User (SCU) is a device thatinitiates DICONDE requests from an SCP.
22、SCU types mostcommonly include the storage type (C-STORE or C-MOVE) toallow sending of data to another device for storage and the findtype (C-FIND) to enable searching and retrieval of stored data.A device may serve as both SCU and SCP. Refer to PS3.4 formore information. See Section 5 for diagram.3
23、.2.11 validation systemthe real-world application entitythat interconnectivity and interoperability is tested against.3.2.12 verification systemthe system that a vendor usesinternally to verify conformance to the DICONDE standard.An example is DVTk: See Appendix X1 and Appendix X2.4. Summary of Prac
24、tice4.1 This practice is intended for use by NDE systemmanufacturers and NDE system purchasers, who need to assessthe technical extent of a systems compliance and conformanceto the DICONDE standard. The procedure is organized in sucha way that the level to which the DICONDE standard issupported is e
25、vident by the last step of the procedure thatpasses. The intent is for a vendor to be able to verifyDICONDE compliance internally and validate DICONDEcompliance with an external system without participating in aconnect-a-thon. It provides concrete examples for how toachieve this without mandating a
26、specific means for verifica-tion and validation. It achieves this by keeping the procedureabstracted from an implementation, and placing an exampleimplementation suggestion in Appendix X1.4.2 The practice is intended to verify and validate all theApplication Entities of interest to the user for the
27、system underevaluation when performing the DICONDE networking evalu-ation. For example, a system under evaluation for DICONDEnetworking interoperability may have more than one Applica-tion Entity: One may be dedicated to responding to searchrequests, and another may be dedicated to receiving imageda
28、ta.5. Significance and Use5.1 This practice describes the recommended procedure forNDE system manufacturers and NDE system purchasers toassess the systems level of compliance and conformance to theDICONDE standard.5.2 The use cases for interconnectivity and interoperabilityare illustrated in Fig. 1.
29、FIG. 1 Illustration of Common SCP and SCU Functions on Two Interoperating DICONDE SystemsE3147 1826. Procedure6.1 Requirements for DICONDE ConformanceThe ven-dor being evaluated under this practice shall submit theirDICOM Conformance Statement (conforming to DICOMPS3.2 - Conformance) to the user eva
30、luating the system. Thevendor shall list the following information from the vendorsDICOM conformance statement.6.1.1 Relevant Network Transfer ServicesList the relevantNetwork Transfer services, that is, NDE modalities, that theuser is interested in evaluating in A1.1.1 of Annex A1(Relevant Network
31、Transfer Services) of this practice. DICOMConformance Statement reference: DICOM ConformanceStatement Overview.6.1.2 Relevant Query / Retrieve Network ServicesList therelevant Query / Retrieve Network Transfer services that theuser is interested in evaluating in A1.1 of Annex A1, RelevantQuery / Ret
32、rieve Network Services. DICOM ConformanceStatement reference: DICOM Conformance Statement Over-view.6.1.3 Relevant Media Services (Import/Export)List therelevant Media services that the user is interested in evaluatingin A1.1.1 (Relevant Media Services) of Annex A1 of thispractice. DICOM Conformance
33、 Statement reference: DICOMConformance Statement Overview.6.1.4 Relevant Implementation Identifying InformationList every relevantApplication Entity that the user is interestedin evaluating in A1.1.4 (Relevant Implementation identifyinginformation) of Annex A1 of this practice. DICOM Confor-mance St
34、atement reference: Heading 4.2 (AE Specification),section 4.2.x (Application entity x), sub-section 4.2.x.2 (Asso-ciation policies), point 4.2.x.2.4 (Implementation identifyinginformation); where “x” refers to the Application Entityidentifier listed in the DICOM Conformance Statement.6.1.5 Relevant
35、ConfigurationList relevant configurationparameters for the system being evaluated in A1.2 of AnnexA1 of this practice. DICOM Conformance Statement refer-ence: Heading 4.4 (Configuration) and section 4.4.2 (Param-eters)6.2 DICONDE VerificationDICONDE media files shallalso conform to DICOM media file
36、requirements. In accor-dance with Part 10 of the DICOM standard, DICONDE fileverification shall ensure the following conformances:6.2.1 The software shall have a conformance statementbased on Part 11 of the DICOM standard in accordance with6.1 of this practice.6.2.2 The software shall support the fi
37、le service as specifiedin PS3.10, Section 8. Verify that this is listed in the confor-mance statement.6.2.3 The software shall meet the requirements of theDICOM file formats specified in PS3.10, Section 7. Verify thatthese requirements are met. Specifically, the file shall:6.2.3.1 Start with a 128-b
38、yte preamble followed by a 4-byteDICOM prefix containing the character string “DICM”.6.2.3.2 Contain the Group 2 required meta information tagsas defined in PS3.10, Section 7.6.2.3.3 Contain all other attribute requirements outlined inthe DICONDE Service Object Pair (SOP) Class, or imagingmodality,
39、for the file.(1) Type 1 attributes must be present with a value defined.(2) Type 1C attributes must be present with a value defined,given that the specified condition is met.(3) Type 2 attributes must be present with at least a0-length value defined.(4) Type 2C attributes must be present with at lea
40、st a0-length value defined, given that the specified condition ismet.6.2.4 The software shall perform the media operationsdefined in PS3.10, Section 8. Verify that these requirements aremet. Specifically, as defined in the conformance statement, theAE may take one or more of the following roles:6.2.
41、4.1 File Set CreatorImplements the M-WRITE opera-tions to create the DICOMDIR file and DICONDE files.6.2.4.2 File Set ReaderImplements the M-READ opera-tions to access files from a DICONDE file set.6.2.4.3 File Set UpdaterImplements the M-READ,M-WRITE, and M-DELETE operations. Note that if an AEneed
42、s to change values in a DICONDE file, this is considereda M-DELETE operation followed by a M-WRITE operation.6.2.5 The software shall support the DICOMDIR file withcontent specified in the Media Storage Directory SOP Class inPS3.3, Section 4. The DICOMDIR is a reserved file ID and thesoftware must g
43、enerate it for all DICONDE file sets residing onstorage media. PS3.10, Annex 1 contains an example DICOM-DIR construction.6.2.6 To ensure these conformances are met, the systemshall be evaluated against its ability to store all the attributesand attribute values and be compared to the required andop
44、tional values for all supported SOP classes by the product.This functionality shall be tested using a validation tool thatcan evaluate the completeness of DICONDE metadata basedon the information object definitions presented in the StandardPractices specified for the required NDT inspection modaliti
45、es.6.2.7 The system shall be evaluated against its ability toread and store all metadata and imagery associated with aninstance of an SOP Class on storage media per PS3.10. Thisfunctionality shall be tested by generating specific media andexamining its contents using a DICONDE verification toolchose
46、n by the individual or individuals tasked with verifyingthat the system under evaluation and has the following capa-bilities:6.2.7.1 Lists all the attributes and attribute values in aDICOM Part 10 file ordered by ascending tag number.6.2.7.2 Compares those values to the required and optionalvalues f
47、or the SOP Class.6.2.7.3 Reports missing or incorrect attributes based onDICONDE elements for the SOP Class.6.2.7.4 Displays a formatted report of all attributes orderedby information module.6.3 DICONDE ImportTo test an imaging systems com-pliance with Part 10 of the DICOM standard, DICONDE filesmay
48、 be acquired from the ASTM web site. DICONDE fileverification shall ensure the following conformances:E3147 1836.3.1 SOP Class definitions for DICONDE shall be down-loaded from ASTM to be used by the verification software toensure that correct information object definitions (IODs) areemployed and te
49、sted in accordance with 6.2.6 and 6.2.7 of thispractice.6.3.2 Sample data files shall be downloaded from ASTM tobe used by the verification software to test the importation ofa Part 10 file by the validation system. The software mustsupport the file service as specified in PS3.10, Section 8. Verifythat this is listed in the conformance statement.6.3.3 Test files can be acquired from the ASTM Interna-tional website by logging into the site, selecting the “MyCollaboration Areas,” and entering “AC15 E07.11 DICONDETask Group on Interoperability” area. The use
