IEEE IEC 61636 pdf download

IEEE IEC 61636 pdf download

IEEE IEC 61636 pdf download Software Interface for Maintenance Information Collection and Analysis (SIMICA)
1.3 Precedence
ln the event of conflict between this document and a normatively referenced standard (see Clause 2), thenormatively referenced standard, as it applies to the information being produced, shall take precedence.
In the event ofconflict between this document and another SIMICA family component standard, this documentshall take precedence.
1.4 Conventions used in this document1.4.1 General
All groups, complex types, simple types, and attribute groups are listed in Annex A. Descriptive informationfor each is provided.
Where there are references to groups, complex types, simple types, and attribute groups within the associatedXML schema orOWLontology(Simica.xsd and Simica.owl), the convention of [name] at [element] is used toindicate where the user can locate the data within either the Simica.xsd or Simica.owl files.
Example: The 1636-2018 download at: https:/lstandards.ieee.orgdownloads indicates the user is to open theSimica.xsd schema at the location provided and find Example for the schema definition.
The namespace prefix “c:”identifies that the type or attribute group associated with this document.
All specifications for OWL and XML within this document are given in the Courier type font and italicized.1.4.2 Word usage
In this document, the word “”shall” is used to indicate a mandatory requirement. The word “should” is used toindicate a recommendation.The word “may” is used to indicate a permissible action.The word “can” is usedfor statements of possibility and capability.
2. Normative references
The following referenced documents are indispensable for the application of this document (i.e., they mustbe understood and used, so each referenced document is cited in text and its relationship to this document isexplained).For dated references, only the edition cited applies.For undated references, the latest edition of thereferenced document (including any amendments or corrigenda) applies.
World Wide Web Consortium, (W3C) extensible Markup Language (XML),1.0 (Fifth Edition) ProposedEdited Recommendation.’
World Wide Web Consortium, (W3C) OWL Web Ontology Language (OWL 2), W3C RecommendationDefinitions, acronyms and abbreviations.
3. Definitions, acronyms, and abbreviations3.1 Definitions
For the purposes of this document, the following terms and definitions apply.TheIEEE Standards DictionaryOnline should be consulted for terms not defined in this clause.2
diagnostic maturation: The process of monitoring diagnostic system predicted versus actual performanceto identify and implement corrective actions. The goal is to enhance diagnostic effectiveness throughout theproduct life cycle. Diagnostic elements that may benefit from the maturation process include (but are notlimited to) diagnostic models, system performance models, test programs, and product design.
ontologies: A formal way to define the structure of knowledge.
system: (A) A collection of entities to be processed by applying a top-down, hierarchical approach(B)Acollection of elements forming a collective,functioning entity (C) A collection of hardware or softwarecomponents necessary for performing a function.
3.2 Acronyms and abbreviations
application program interface
automatic test equipment
automatic test system
globally unique identifier
web ontology language
Standards Coordinating Committee 20
software interface to maintenance information collection and analysis
test program set
universal resource locator
universal unique identifier
unit under test
World wide Web Consortium
extensible markup language
4. Diagnostic maturation
The process of maturing a system diagnostic design begins in the system ‘s conceptual design phase andcontinues throughout the system life cycle.Generally, diagnostic design is demonstrated prior to delivery ofthe first unit to meet the diagnostic and health management requirements that have been levied.However, oncea system is fielded and used in an operational environment,unexpected and unplanned system level designinteractions,operational and environmental stresses, performance characteristics of tests and monitors, andother influences tend to reveal deficiencies in the diagnostic capabilities. When such deficiencies result in asystem readiness/availability or cost of ownership problem, remedial actions shall be taken:

The previous

IEEE C135.90 pdf download

The next

IEEE IEC 63113 pdf download

Related Standards