BS IEC 61636-1-2016 Software interface for maintenance information collection and analysis (SIMICA) Exchanging test results and session information via the extensible markup langua.pdf

1、Software interface for maintenance information collection and analysis (SIMICA):Exchanging test results and session information via the extensible markup language(XML)BS IEC 61636-1:2016BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06National forewordThis British Sta

2、ndard is the UK implementation of IEC 61636-1:2016. The UK participation in its preparation was entrusted to TechnicalCommittee EPL/501, Electronic Assembly Technology.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport t

3、o include all the necessary provisions ofa contract. Users are responsible for its correct application. The British Standards Institution 2016.Published by BSI Standards Limited 2016ISBN 978 0 580 94225 9ICS 25.040.01; 35.060Compliance with a British Standard cannot confer immunity fromlegal obligat

4、ions.This British Standard was published under the authority of theStandards Policy and Strategy Committee on 30 November 2016.Amendments/corrigenda issued since publicationDate Text affectedBRITISH STANDARDBS IEC 61636-1:2016IEC 61636-1 Edition 1.0 2016-11 INTERNATIONAL STANDARD Software interface

5、for maintenance information collection and analysis (SIMICA): Exchanging test results and session information via the extensible markup language (XML) INTERNATIONAL ELECTROTECHNICAL COMMISSION ICS 25.040.01; 35.060 ISBN 978-2-8322-3684-0 Warning! Make sure that you obtained this publication from an

6、authorized distributor. IEEE Std 1636.1 Registered trademark of the International Electrotechnical Commission BS IEC 61636-1:2016Contents 1. Overview 11.1 Scope . 21.2 Purpose 21.3 Application 21.4 Precedence. 31.5 Conventions used in this document . 32. Normative references 43. Definitions, acronym

7、s, and abbreviations 43.1 Definitions . 43.2 Acronyms and abbreviations . 54. Test results and session information. 64.1 Background 64.2 Introduction . 64.3 Applicability 64.4 Usage . 74.5 Relationships to other automatic test system (ATS) architectural elements 75. EXPRESS model, EXPRESS-G diagram,

8、 and XML schema names and locations . 96. Conformance 107. Extensibility 11Annex A (normative) XML schemas . 12A.1 TestResults.xsd . 12A.2 TestResultsCollection.xsd. 59Annex B (normative) EXPRESS models . 60B.1 TEST_RESULTS_MODEL 60B.2 TestResults model EXPRESS-G diagrams . 76Annex C (informative) B

9、ibliography 83Annex D (informative) IEEE list of participants.85 viii Copyright 2013 IEEE. All rights reserved. IEC 61636-1:2016 IEEE Std 1636.1-2013 i BS IEC 61636-1:2016SOFTWARE INTERFACEFOR MAINTENANCE INFORMATION COLLECTIONAND ANALYSIS (SIMICA):EXCHANGING TEST RESULTS AND SESSIONINFORMATION VIA

10、THE EXTENSIBLE MARKUPLANGUAGE (XML)25(:25 7KH,QWHUQDWLRQDO(OHFWURWHFKQLFDO explanatory information will be provided, along with examples if additional clarification is needed. The explanatory information shall include information on the intended use of the elements and/or attributes where the name o

11、f the entity does not clearly indicate its intended use. For elements derived from another source type (e.g., an abstract type), only attributes which extend the source type shall be listed; details regarding the base type shall be listed along with the base type. The namespace prefix “c:” identifie

12、s that the type or attribute group is contained in Annex B of IEEE Std 1671TM(Schema-Common.xsd). When referring to an attribute of an XML element, the convention of elementattribute shall be used. In cases where an attribute name is referred to with no associated element, the attribute name shall b

13、e enclosed in single quotes. In tables that describe XML elements, the column “Use” indicates the occurrence constraints for each element. a) “Required” indicates that the element shall appear exactly once. b) “Optional” indicates that the element may appear once or not at all. c) “1” indicates that

14、 the element shall appear at least once and may appear multiple times. d) “0” indicates that the element may appear multiple times, once, or not at all. 3 Copyright 2013 IEEE. All rights reserved. 3 IEC 61636-1:2016 IEEE Std 1636.1-2013BS IEC 61636-1:2016IEEE Std 1636.1-2013 IEEE Standard for Softwa

15、re Interface for Maintenance Information Collection and Analysis (SIMICA): Exchanging Test Results and Session Information via the eXtensible Markup Language (XML) All specifications for the EXPRESS language are given in the Courier type font which includes references to entity and attribute names i

16、n the supporting text. 1.5.2 Word usage In this document, the word shall is used to indicate a mandatory requirement. The word should is used to indicate a recommendation. The word may is used to indicate a permissible action. The word can is used for statements of possibility and capability. 2. Nor

17、mative references The following referenced documents are indispensable for the application of this document (i.e., they must be understood and used, so each referenced document is cited in text and its relationship to this document is explained). For dated references, only the edition cited applies.

18、 For undated references, the latest edition of the referenced document (including any amendments or corrigenda) applies. IEEE Std 1636-2009, IEEE Trial-Use Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA).4, 5IEEE 1636.99-2013, IEEE Standard for Software I

19、nterface for Maintenance Information Collection and Analysis (SIMICA): Common Information Elements. IEEE Std.1671-2010, IEEE Standard for Automatic Test Markup Language (ATML) for Exchanging Automatic Test Equipment and Test Information via XML. 3. Definitions, acronyms, and abbreviations For the pu

20、rposes of this document, the following terms and definitions apply. The IEEE Standards Dictionary Online B2 should be consulted for terms not defined in this clause.63.1 Definitions branch: In an eXtensible Markup Language (XML) document or schema, a specified element and all elements subordinate to

21、 that specified element. component (in eXtensible Markup Language (XML) schema): The generic term for the building blocks that compose the abstract data model of the schema. eXtensible Markup Language (XML) attribute: Name-value pair associated with an XML element. eXtensible Markup Language (XML) d

22、ocument: A (text) data object that conforms to the XML requirements for being well-formed (as defined by W3C). 4IEEE publications are available from The Institute of Electrical and Electronics Engineers (http:/standards.ieee.org/). 5The IEEE standards or products referred to in this clause are trade

23、marks of The Institute of Electrical and Electronics Engineers, Inc. 6IEEE Standards Dictionary Online subscription is available at: http:/www.ieee.org/portal/innovate/products/standard/standards_dictionary.html 4 Copyright 2013 IEEE. All rights reserved. 4 IEC 61636-1:2016 IEEE Std 1636.1-2013BS IE

24、C 61636-1:2016IEEE Std 1636.1-2013 IEEE Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA): Exchanging Test Results and Session Information via the eXtensible Markup Language (XML) eXtensible Markup Language (XML) namespace: A method for distinguishing XML e

25、lements and attributes that may have the same name but different meanings. A URL is used as a prefix to a “local name.” This combination ensures the uniqueness of the element or attribute name. The URL is used only as a way to create a unique prefix and does not have to resolve to a real page on the

26、 Internet. NOTESee Namespaces in XML 1.0 B10 and Schenk and Wilson B117. eXtensible Markup Language (XML) schema: The structure or framework used to define a data record. This includes each fields name, type, shape, dimension, and mapping. framework: A framework is a real or conceptual structure exp

27、ressed as a set of abstract classes. The framework provides a context for the components to be used. instance document: A textual information set grouped for some purpose that is governed by a single XML schema. maintenance: Activity intended to keep equipment (hardware) or programs (software) in sa

28、tisfactory working condition, including replacements, adjustments, repairs, software/firmware updates, and program improvements. Maintenance can be preventative or corrective. (Adapted from MIL-STD-1309D B12.) particle (in eXtensible Markup Language (XML) schema): A kind of component. qualified name

29、 (in XML schema): The complete name of an XML element, attribute, or data type, including the local name and a prefix that identifies the namespace in which the local name is defined/declared. sequence (in XML schema): A compositor for model group schema components which specifies that subordinate e

30、lements in an instance document must correspond, in order, to the specified particles. 3.2 Acronyms and abbreviations AI-ESTATE Artificial Intelligence Exchange and Service Tie to All Test Environments ATE automatic test equipment ATML Automatic Test Markup Language ATS automatic test system DMC Dia

31、gnostic and Maintenance Control ISO International Organization for Standardization MAI maintenance action information SCC20 Standards Coordinating Committee 20 SIMICA Software Interface for Maintenance Information Collection and Analysis TPS test program set UUT unit under test 7Notes in text, table

32、s, and figures are given for information only and do not contain requirements needed to implement the standard. 5 Copyright 2013 IEEE. All rights reserved. 5 IEC 61636-1:2016 IEEE Std 1636.1-2013BS IEC 61636-1:2016IEEE Std 1636.1-2013 IEEE Standard for Software Interface for Maintenance Information

33、Collection and Analysis (SIMICA): Exchanging Test Results and Session Information via the eXtensible Markup Language (XML) URL universal resource locator W3C World Wide Web Consortium XML eXtensible Markup Language 4. Test results and session information 4.1 Background Current automatic test system

34、architectures are implemented with tight coupling between components. This tight coupling inhibits interoperability by requiring components of the automatic test system to be developed specific to that particular architecture. In many cases, this coupling can be reduced by developing the components

35、that operate relative to standard interfaces. This document will facilitate accomplishing several objectives. First, the document will serve as a single source for specifying essential test data with data elements related to the unit under test (UUT), the test station, and the test program. Second,

36、the document will assist the automatic test equipment (ATE) industry to design and create compatible, interoperable tool sets such as data parsers and writers. Third, the standard will assist ATE users of such data (e.g., automotive, semiconductor, aerospace, and military) to process and display tes

37、t results across a variety of systems. This document has been developed as a “component standard” under IEEE Std 1636. SIMICAs purpose is to specify software interfaces for access, exchange, and analysis of product diagnostic and maintenance information. Test results provide a subset of the data nee

38、ded to satisfy SIMICAs requirements. This document also represents the test results component of IEEE Std 1671 (ATML). In defining its overall architecture, ATML references include both IEEE Std 1636 (SIMICA) and IEEE Std 1636.1 (this standard). 4.2 Introduction This documents XML schema and EXPRESS

39、 model provides a standard format for the transport of both quantitative (measured values) and qualitative (pass/fail determination) test results. The design is such that it is possible to store ancillary information such as environmental conditions and system/operator messages. This information, al

40、though not specifically “results,” is intended to permit use of an instance document for a variety of purposes, including statistical analysis and diagnostics. Some examples of this ancillary information include identifying information for the UUT, the test station, and the test program; ambient env

41、ironmental conditions at the time of the test; test equipment calibration data; as well as test program input data and ancillary textual comments. This document establishes a hierarchical structure for results data to permit the grouping of a series of related test results in a single instance docum

42、ent. 4.3 Applicability This document will permit test results data to be shared for a variety of purposes, including statistical analysis, diagnostics, and improvement of the unit under test (UUT) repair process. 6 Copyright 2013 IEEE. All rights reserved. 6 IEC 61636-1:2016 IEEE Std 1636.1-2013BS I

43、EC 61636-1:2016IEEE Std 1636.1-2013 IEEE Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA): Exchanging Test Results and Session Information via the eXtensible Markup Language (XML) 4.4 Usage This document presumes some knowledge of XML and the use of XML sc

44、hemas. A variety of XML software tools are available in a number of computer programming languages. This document makes no presumption regarding the tool(s) being used or the specific test system(s) generating the test result information being captured in an XML instance document. This document desc

45、ribes the TestResults.xsd schema and specifies the EXPRESS information model that conformant instance documents must follow. In general, this document serves as an enhancement to the annotations provided within the XML schema and EXPRESS model files. 4.4.1 XML schema representations Within the body

46、of this document, unless otherwise indicated, all syntax references relate to XML. Refer to XML eXtensible Markup Language (XML) 1.0 B1 for detailed descriptions of XML data formats. 4.4.2 EXPRESS/EXPRESS-G representations This document also uses the EXPRESS information modeling language to represen

47、t the information contained in the XML schema in a way that supports alternative exchange mechanisms and better defines the semantics of the elements of the XML schema. The information models are presented in a lexical form (EXPRESS) as well as in graphical form (EXPRESS-G) to facilitate understandi

48、ng. The EXPRESS language is defined by ISO 10303-11:1994 B9. 4.5 Relationships to other automatic test system (ATS) architectural elements 4.5.1 General In the ATS context, a test is a procedure for evaluating or quantifying the operation of some device or system. The TestResults schema provides a s

49、tandard format for the transport or storage of both quantitative (measured values) and qualitative (pass/fail determination) test results. The XML schema design is such that ancillary information such as environmental conditions and system/operator messages may also be stored in an XML instance document. This information, while not specifically “results,” is intended to permit use of an XML instance document for a