This schema is specified in IEEE Std 1636.1-20XX, "IEEE Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA): Exchanging Test Results and Session Information via the eXtensible Markup Language (XML)" This schema is a World Wide Web Consortium (W3C) Extensible Markup Language (XML) binding of the SIMICA TestResults component defined in IEEE Std 1636.1-20XX,"IEEE Standard for Software Interface for Maintenance Information Collection and Analysis (SIMICA): Exchanging Test Results and Session Information via the eXtensible Markup Language (XML)." The purpose of this schema is to allow the creation of IEEE Std 1636.1-20XX TestResults instance documents. This schema uses the W3C XML Schema definition language as the encoding. This allows for interoperability and the exchange of ATML component instances between various systems. This schema shall not be modified but may be included in derivative works. Copyright (c) 2011 Institute of Electrical and Electronics Engineers, Inc. USE AT YOUR OWN RISK This shall be used as the base type for any XML schema attribute or element that represent permitted values for a test outcome. In use, “Passed” shall indicate the results of a test were within specified limits. “Failed” shall indicate that the results of a test were not within specified limits. “Aborted” shall indicate that a test did not complete. This shall be used as the base type for any XML schema attribute or element that represent permitted UUT repair codes. The Action complex type shall be used to identify specific data related to any action(s) performed; either in/during the execution of a test, or as part of the repair process. This element shall be used to identify descriptive information for the parent element. This element shall be used to identify any events, such as system or operator messages. This shall be used to identify an particular event. This element shall be used to identify test parameter data. This element shall be used to identify a particular test parameter. This element shall be used to identify data associated with non-test actions. This element shall be used to identify environmental conditions which are related to a test. This element shall be used to identify the environmental data which is pertinent to a particular test. Date and time associated with the environmental data. This attribute should be used where the time the data was recorded is significant within the overall context of a particular test. This element shall provide a specific extension point for use cases that require elements not provided in the basic structure. This element shall provide a specific extension point for use cases that require elements not provided in the basic structure. A descriptive or common name for the Action. The value of “ID” shall be unique within the context of the containing XML instance document. A user-friendly textual name for the Action. A user defined textual “type” that will describe the non-test action. The monitary cost value associated with performing the action. An indication that the Action occurred during a simulated test. The beginning date and time of the action. The ending date and time of the action. The reference ID of the TestGroup, Test, or SessionAction that was executed to generate the test result. This complex type shall identify non-result data or system/operator messages generated during a test. This element shall be used to identify textual message(s). This element shall be used to identify data value(s). This element shall be used to identify reference(s) to external items (e.g., documents). A descriptive or common name for the Event. The value of “ID” shall be unique within the context of the containing XML instance document. A user-friendly textual name for the Event. An enumeration of 0-4 inclusive that shall indicate a severity level for the Event. It shall be presumed that a value of 0 indicates least severe. Successive values shall indicate increasing levels of severity with 4 indicating most severe. An identification of the source of the Event (e.g., operator or test system). The date and time of the Event occurrence. This complex type shall be used to identify test outcomes (i.e., Passed, Failed, or Aborted). Shall contain one of the following enumerations: “Passed”, “Failed”, or “Aborted”. In use, “Passed” shall indicate the results of a test were within specified limits. “Failed” shall indicate the results of a test were not within the specified limits. “Aborted” shall indicate that a test did not complete normally. A adjective providing additional descriptive data for the value attribute. For example, (…value=“Failed” qualifier=“High” …). In the case of (…value=“Aborted” …), qualifier shall provide essential descriptive or explanatory information regarding the reason for the test not completing normally. This complex type shall be use to identify test input parameters. Parameters are generally described as configuration or input values for a test. This element shall be used to identify unstructured, unrestricted textual descriptions of the Parameter. This element shall be used to identify structured, restricted textual descriptions of the Parameter. This element shall be used to identify the any referential data. A typical example would be a reference to a document or location where run-time test parameters are stored. This would be useful in cases where such parameters are not permitted in the TestResults XML instance document due to security reasons. A descriptive or common name for the Parameter. The value of “ID” shall be unique within the context of the containing XML instance document. A user-friendly textual name for the Parameter. The date and time associated with the Parameter. This shall be used where the time of application of a parameter is significant within the overall context of a test. This element shall be used as the base type for any element representing a subcomponent of a UUT. The description that corresponds to the reference designataor abbreviation. The abbreviation of the reference designator. Defines the type of the UUT being indicted (e.g. WRA, SRA, Component, etc). This complex type shall be used to capture the type of repair(s) conducted. This element identifies the code and description used to describe the type of repair action taken. This element identifies the subcomponent of the UUT that was the cause of a test failure. This element identifies the specific item repaired when the serial number of the item is not known. This element identifies the specific item repaired when the serial number of item is known. This element shall be used to identify the procedure required to perform a repair. Indicates whether or not the repair was performed as part of preventative maintenance. This element shall be used as the base type of any element defining a specific repair action to perform (or already performed) in the maintenance of the item. A adjective providing additional descriptive data for the value and code attributes. The type of repair action that was taken. The application specific code for the value attribute. This complex type shall be used to identify all relevant information related to a single test. This information includes input parameters, system or operator events, calibration values, and an outcomes. Outcome shall represent a summary outcome of all subordinate Test elements. Each subordinate Test elements may have a separate and distinct Outcome. This element shall be used to identify the test outcome of a test (i.e., Passed, Failed, or Aborted). This element shall be used to identify operational calibration information when it is necessary to record calibration values for the test equipment associated with the execution of a test. This element shall be used to identify comparison limits that apply to all test and/or test groups. This element shall be used to identify the limits against which test data (tr:TestData) is compared to in order to arrive at a test outcome (tr:testOutcome). This element shall be used for the recording of results and other information related to a single iteration of a test. This information includes transforms (of raw measurement data) or the test limits against which results are measured to determine outcomes. “1” shall indicate that the test represents a test entry point. A user-defined description of the operating mode of the test equipment for this test. This complex type shall be used to identify a grouping of related tests, test groups, or session actions. TestGroup provides a hierarchical structure for the aggregation of test results data within an Test Results XML instance document. TestGroup is recursive; that is, a TestGroup optionally contains subordinate TestGroup elements. The TestGroup structure shall be used to contain a collection of multiple iterations of a single test, or a related set of tests that the user desires to be reported or captured as a unit. When multiple Test, TestGroup, or SessionAction elements appear, the order of appearance of these elements should correspond to the time sequence order in which the test(s) or action(s) occurred. When the optional Outcome element appears, it shall represent a summary outcome of all subordinate TestGroup elements. Each subordinate TestGroup element may have a separate and distinct Outcome. This element shall be used to identify a single test. This element shall be used to identify a related set of single tests. This element shall be used to identify the actions that occurred during a test session that are not actual test results. This element shall be used to identify the completion status of the test action (e.g., done or aborted). Shall indicated either "Done" or "Aborted". A user-friendly textual enhancement of the value attribute string. This complex type shall be used to capture test result data, comparision limits, indited components, and data transforms required to evaluate raw test results data. This element shall be used to identify the qualitative result of evaluating collected test data against quantitative limits This element shall be used to identify any descriptive information for the TestResult. This element shall be used to identify the indictments on the UUT as a result of performing tests. This element shall be used to capture data from the test equipment. This data may be either raw data or post-processed data. It is presumed that a transform will be provided for raw data. The date and time associated with when the test data was aquired from the test equipment. This element shall be used to identify test limits for which to compare against to determine a outcome. This element shall be used to identify the limits against which TestData is compared to arrive at an outcome. Within an XML instance document, these limit values shall only apply to the TestResults branch containing this element. This element shall be used to identify any transform that may be required to produce meaningful results from raw data. This element shall provide a specific extension point for use cases that require elements not provided in the basic structure. A descriptive or common name for the TestResult. The value of “ID” shall be unique within the context of the containing XML instance document. A user-friendly textual name for the TestResult. This element shall be used to identify information regarding the personnel associated with the performance of the testing. This element shall be used to identify the customer representative whom is witnessing testing or will be signing off on the test results. This element shall be used to identify the quality assurance representitive whom will be signing off on the test results. This element shall be used to identify the operator performing the testing of the UUT. This element shall be used to identify any repairs made to the UUT prior to performing test(s) on the UUT and is used in the diagnostic process. This element shall be used to identify a particular repair made to the UUT prior to the performance of test(s). This element shall be used to identify references which are external to an TestResults XML instance document. References shall be any items relevant to a particular test, test group, or complete test program; as defined and required by the user. This element shall be used to identify a particular externally referenced item. This element shall be used to identify the quantitative and/or qualitative results, as well as non-test session data; collected during execution of a test or group of tests. This element shall be used to identify the physical location at which the test results were collected. This element shall be used to identify an XML instance document conformant with the ATML Test Description standard (IEEE Std 1671.1). This Test Description XML instance document defines the test(s) that shall be directly associated to the test(s) identified within the Test Results XML instance document. This element shall is to be used to identify the specific test program which was used to generate the results data in the TestResults XML instance document. This element shall be used to identify data associated with non-test actions. This element shall be used to identify the specific test station or equipment upon which the test(s) was/were conducted. This element shall be used to uniquely identify the UUT upon which the test(s) is/are performed. This element shall be used to identify a work order related to, or authorizing, the testing of the UUT. This element shall provide a specific extension point for use cases that require elements not provided in the basic structure. The name of the instance document. Example: Acme Widget Test Results The TestResults element shall be a container for all information entities utilized in the collection of the results of testing a UUT on (or within) a particular test station, executing a particular set of tests. This root element serves as the parent element for all other elements within the Test Results XML schema. This element shall be used to identify the information for the subcomponent of the tested UUT, that is the most likely cause of a test failure. Identifies the code and description used to describe the type of recommended repair. The subcomponent of a UUT this is the most likely cause of a test failure. This element shall provide a specific extension point for use cases that require elements not provided in the basic structure. The test group that the test program recommends using when retesting the UUT. The date and time that the indictments were made.