BS IEC 61636-2016 Software Interface for Maintenance Information Collection and Analysis (SIMICA)《维护信息采集与分析用软件接口(SIMICA)》.pdf

《BS IEC 61636-2016 Software Interface for Maintenance Information Collection and Analysis (SIMICA)《维护信息采集与分析用软件接口(SIMICA)》.pdf》由会员分享，可在线阅读，更多相关《BS IEC 61636-2016 Software Interface for Maintenance Information Collection and Analysis (SIMICA)《维护信息采集与分析用软件接口(SIMICA)》.pdf（42页珍藏版）》请在麦多课文档分享上搜索。

1、Software Interface forMaintenance InformationCollection and Analysis (SIMICA)BS IEC 61636:2016BSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06National forewordThis British Standard is the UK implementation of IEC 61636:2016. The UK participation in its preparation wa

2、s entrusted to Technical Committee 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 to include all the necessary provisions ofa contract. Users are responsible for its correct ap

3、plication. The British Standards Institution 2016.Published by BSI Standards Limited 2016ISBN 978 0 580 94224 2ICS 25.040.01; 35.060Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy and Strat

4、egy Committee on 30 November 2016.Amendments/corrigenda issued since publicationDate Text affectedBRITISH STANDARDBS IEC 61636:2016IEC 61636 Edition 1.0 2016-11 INTERNATIONAL STANDARD Software Interface for Maintenance Information Collection and Analysis (SIMICA) INTERNATIONAL ELECTROTECHNICAL COMMI

5、SSION ICS 25.040.01; 35.060 ISBN 978-2-8322-3686-4 Warning! Make sure that you obtained this publication from an authorized distributor. IEEE Std 1636 Registered trademark of the International Electrotechnical Commission BS IEC 61636:2016vii Copyright 2013 IEEE. All rights reserved. Contents 1. Over

6、view 1 1.1 General 1 1.2 Scope . 3 1.3 Purpose 3 1.4 Application 3 1.5 Conventions used in this document . 3 2. Normative references 3 3. Definitions 4 4. Backgrounds . 5 4.1 Diagnostic maturation 5 4.2 Relationship to IEEE Std 1232 (AI-ESTATE) 6 4.3 Relationship to IEEE 1636 (SIMICA) component stan

7、dards 6 5. Information model 6 5.1 SIMICA_MODEL . 7 6. Conformance .20 Annex A (informative) Bibliography 21 Annex B (informative) Overview of EXPRESS22 B.1 Schema .22 B.2 Entity 22 B.3 Attribute .23 B.4 Type definition .24 B.5 Subtypes/supertypes .24 B.6 External schema references 25 B.7 Uniqueness

8、 constraints and WHERE clauses 26 B.8 Functions and procedures .27 $QQH however, such implementations may not be portable. Software specifications defined in the SIMICA family of standards will support the interchangeability of information between conformant applications. This will allow a large deg

9、ree of flexibility in implementation of information application architectures that support information reuse and realize various maintenance information services (such as, but not limited to, client-server approaches, service oriented architectures, etc.). 2 IEC 61636:2016 IEEE Std 1636-2013BS IEC 6

10、1636:2016IEEE Std 1636-2009 IEEE Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA) 3 Copyright 2013 IEEE. All rights reserved. 1.2 Scope This standard is an implementation-independent specification for a software interface to information systems containing

11、data pertinent to the diagnosis and maintenance of complex systems consisting of hardware, software, or any combination thereof. These interfaces will support service definitions for creating application programming interfaces (API) for the access, exchange, and analysis of historical diagnostic and

12、 maintenance information. The standard will use the information models of IEEE Std 1232 as a foundation. 1.3 Purpose The purpose of this standard is to specify a software interface for access, exchange, and analysis of product diagnostic and maintenance information. This will address the pervasive n

13、eed of organizations to assess the effectiveness of diagnostics for complex systems throughout the product life cycle. The use of formal information models will facilitate exchanging historical maintenance information between information systems and analysis tools. The models will facilitate creatin

14、g open system software architectures for maturing system diagnostics. 1.4 Application This standard should be applied in the development of software applications that access or provide information relevant to the diagnosis and maintenance of systems. In the event of conflict between this standard an

15、d a component standard in the IEEE 1636 family, the component standard shall take precedence. In the event of conflict between this standard and a related standard such as IEEE Std 1232, the standard as it applies to the information being produced shall take precedence. In the event of any conflict

16、between model comments and lexical definitions, lexical definitions shall take precedence. 1.5 Conventions used in this document Clause 5 presents entity and concept definitions using the EXPRESS language as defined in ISO 10303-11:1994 and uses the following conventions in their presentation: All s

17、pecifications in the EXPRESS language are given in the Courier type font when model elements are represented outside the scope of the model. This standard uses the vocabulary and definitions of relevant IEEE standards. In case of conflict of definitions, the following precedence shall be observed: 1

18、) Clause 3, Definitions; 2) The Authoritative Dictionary of IEEE Standards Terms B12with preference given to versions of those definitions that are attributed to SCC20 standards. 2. Normative references The following referenced documents are indispensable for the application of this document (i.e.,

19、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. For undated references, the latest edition of the referenced document (including any amendments or corrigenda) app

20、lies. 2The numbers in brackets correspond to those of the bibliography in Annex A. 3 IEC 61636:2016 IEEE Std 1636-2013BS IEC 61636:2016IEEE Std 1636-2009 IEEE Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA) 4 Copyright 2013 IEEE. All rights reserved. IEEE

21、 Std 1232, IEEE Standard for Artificial Intelligence Exchange and Service Tie to All Test Environments (AI-ESTATE).3, 4IEEE Std 1636.1-2007, IEEE Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA): Exchanging Test Results and Session Information via the eXte

22、nsible Markup Language (XML). IEEE P1636.2/D3.0 (August 2008), Draft Trial-Use Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA): Exchanging Maintenance Action Information (MAI) via the eXtensible Markup Language (XML).5ISO 10303-11:1994. Industrial automat

23、ion systems and integrationProduct data representation and ExchangePart 11: Description methods: The EXPRESS language reference manual, Geneva, Switzerland: International Organization for Standardization.63. Definitions For the purposes of this standard, the following terms and definitions apply. Th

24、e Authoritative Dictionary of IEEE Standards Terms B1 should be referenced for terms not defined in this clause. This clause defines terms used in the SIMICA set of standards. A clear understanding of the following terms with respect to testability and diagnosability is particularly important in ord

25、er to understand this standard. 3.1 architectural device: In the context of software systems, a means that facilitates the arrangement of software components or model elements to accomplish a specific purpose. 3.2 conceptual information model: An information model that is independent of any particul

26、ar instantiation form, i.e., is never intended to be realized. 3.3 concrete information model: An information model that is specialized to take account of a particular instantiation method or data exchange format. 3.4 diagnostic maturation: The process of monitoring diagnostic system predicted vs. a

27、ctual performance to identify and implement corrective action. The goal is to enhance diagnostic effectiveness throughout the product life cycle. Diagnostic elements that may benefit from the maturation process include (but are not limited to) diagnostic models, system performance models, test progr

28、ams, and even product design improvements. 3.5 information model: A formal description of types of ideas, facts, and processes that together form a model of a portion of interest of the real world and which provides an explicit set of interpretation rules. 3.6 level of indenture: A hierarchical part

29、ition in a physical or functional system decomposition. 3IEEE publications are available from the Institute of Electrical and Electronics Engineers, 445 Hoes Lane, Piscataway, NJ 08854, USA (http:/standards.ieee.org). 4The IEEE standards or products referred to in this clause are trademarks of the I

30、nstitute of Electrical and Electronics Engineers, Inc. 5This IEEE standards project was not approved by the IEEE-SA Standards Board at the time this publication went to press. For information about obtaining a draft, contact the IEEE. 6ISO publications are available from the ISO Central Secretariat,

31、 Case Postale 56, 1 rue de Varembe, CH-1211, Geneve 20, Switzerland/.Suisse (http:/www.iso.ch/). ISO publications are also available in the United States from the Sales Department, American National Standards Institute, 25 West 43rd Street, 4th floor, New York, NY 10036, USA (http:/www.ansi.org/). 4

32、 IEC 61636:2016 IEEE Std 1636-2013BS IEC 61636:2016IEEE Std 1636-2009 IEEE Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA) 5 Copyright 2013 IEEE. All rights reserved. 3.7 system: A) A collection of entities to be processed by applying a top-down, hierarch

33、ical approach. B) A collection of elements forming a collective, functioning entity. C) A collection of hardware or software components necessary for performing a function. 4. Backgrounds 4.1 Diagnostic maturation The process of maturing a system diagnostic design begins in the systems conceptual de

34、sign phase and continues throughout the system life cycle. Generally diagnostic design are demonstrated prior to delivery of the first unit to meet the diagnostic and health management requirements that have been levied. However, once a system is fielded and used in an operational environment, unexp

35、ected and unplanned system level design interactions, operational and environmental stresses, and other influences tend to reveal deficiencies in the diagnostic capabilities. When such deficiencies result in a weapon system readiness or cost of ownership problem, remedial actions must be taken: The

36、performance issue must be clearly characterized in terms of scope, impact, and ownership. Root cause analysis must be performed to identify potential courses of actions, including adjustments, improvements, or refinements to support and operational elements. The resulting courses of action must be d

37、eployed in a manner that is both economically feasible and consistent with product functional and operational requirements. The diagnostic maturation process requires access to design, maintenance, and logistics support information sources. Aggregation of system failure and performance data from dis

38、parate information sources is a multidisciplinary issue, i.e., relevant data exists within the purview of engineering, product support, and other organizations. Each of these organizations is also multifaceted in nature. Engineering organizations, for example, are composed of sub-disciplines such as

39、 design, reliability and maintainability, etc. Compounding the problem is the fact that the data of interest resides in multiple systems each with different owners where it does existand it should be recognized that some data that is desirable to have might not be captured in data systems at all. Th

40、e problem can be reduced by operating with a single, unified conceptual view of the data to be extracted from multiple sources. Therefore, the challenge is how to extract the information of interestheterogeneous system failure and performance datafrom the disparate data systems where it resides. The

41、 idea is to identify the information of interestand in fact, to create an information model so that it is clear what that data is and what it really means in the context of system usage and analysisthen determine the process for obtaining that information. Once data requirements and availability are

42、 determined, one can then begin trying to solve the puzzle of how to integrate the heterogeneous information to be obtained, i.e., how to relate the vital information from any one system to the others that capture related information but using disparate data formats and semantics. Data collection is

43、 a prerequisite for the maturation process, and the product data that is typically required for maturation analysis is generally stored in heterogeneous data systems. This standard will facilitate improved access, retrieval, and integration of the requisite information from these data systems. The i

44、ntent of the SIMICA family of specifications is to provide an implementation-independent specification for a software interface to information systems containing data pertinent to the diagnosis and maintenance of complex systems consisting of hardware, software, or any combination thereof. These int

45、erfaces will support the creation of service definitions for application programming interfaces (API) for the access, exchange, and analysis of historical diagnostic and maintenance information. The use of formal information models will facilitate exchanging historical maintenance information betwee

46、n information systems and analysis tools, supporting the creation of open system software architectures for maturing system 5 IEC 61636:2016 IEEE Std 1636-2013BS IEC 61636:2016IEEE Std 1636-2009 IEEE Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA) 6 Copyr

47、ight 2013 IEEE. All rights reserved. diagnostics. The component standards will further enhance the exchange of instance information between conforming applications through the use of standard exchange formats. More information on the diagnostic maturation process and associated issues can be found i

48、n The Authoritative Dictionary of IEEE Standards Terms B1, Wilmering 2001 B5, and Wilmering, Yuan, and VanRossum 2003 B6. 4.2 Relationship to IEEE Std 1232 (AI-ESTATE) IEEE Std 1232 is an information exchange standard for test and diagnosis. The standard defines the architecture of an AI-ESTATE-conf

49、ormant system, information models for knowledge and data exchange, and a set of standard software services to be provided by a diagnostic reasoner in an open-architecture test environment. Because it provides formal definitions (via information modeling) of the information required for test and diagnosis, it will serve as a basis for information requirements in this standard. The SIMICA information model directly references the IEEE Std 1232s Dynamic Context Model historical records of diagnostic