{"title":"在基于组件的体系结构中实现AI-ESTATE,第二阶段","authors":"A. Giarla, W.L. Simerly","doi":"10.1109/AUTEST.2000.885625","DOIUrl":null,"url":null,"abstract":"This paper discusses Phase-II of an Air Force funded SBIR R&D project concerned with implementing the IEEE 1232 Standard known as AI-ESTATE in a component based Automatic Test System (ATS). The intent of our Phase-II work is to provide the Air Force with a \"working tool\" that demonstrates the utility of our architectural approach as well as the utility of AI-ESTATE. The intent of our component based approach to ATS design is to provide a de-coupling of the diagnostic reasoner from the rest of the ATS as well as provide for a true open system at a reduced procurement and maintenance costs. AI-ESTATE is used to provide a standardized interface between the reasoner and the other ATS elements as well as provide standardized information and data model formats. The architecture consists of a COTS Test System (VXI package with LabVIEW), four \"domain\" type components: Diagnostic Engine Component (DEC), Application Executive Component (AEC), Test System Component (TSC) and Model Editing Component (MEC) that plug into our \"Interoperable, Connectivity Enabling Framework\" (ICEF) based on COM/DCOM. The four components and framework are discussed in general terms. The DEC implements AI-ESTATE and is further discussed in derail as are the other components. Also discussed are operational uses, diagnostic development, vendor competition and benefits.","PeriodicalId":334061,"journal":{"name":"2000 IEEE Autotestcon Proceedings. IEEE Systems Readiness Technology Conference. Future Sustainment for Military Aerospace (Cat. No.00CH37057)","volume":"189 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"1999-08-30","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"8","resultStr":"{\"title\":\"Implementing AI-ESTATE in a component based architecture, Phase-II\",\"authors\":\"A. Giarla, W.L. Simerly\",\"doi\":\"10.1109/AUTEST.2000.885625\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"This paper discusses Phase-II of an Air Force funded SBIR R&D project concerned with implementing the IEEE 1232 Standard known as AI-ESTATE in a component based Automatic Test System (ATS). The intent of our Phase-II work is to provide the Air Force with a \\\"working tool\\\" that demonstrates the utility of our architectural approach as well as the utility of AI-ESTATE. The intent of our component based approach to ATS design is to provide a de-coupling of the diagnostic reasoner from the rest of the ATS as well as provide for a true open system at a reduced procurement and maintenance costs. AI-ESTATE is used to provide a standardized interface between the reasoner and the other ATS elements as well as provide standardized information and data model formats. The architecture consists of a COTS Test System (VXI package with LabVIEW), four \\\"domain\\\" type components: Diagnostic Engine Component (DEC), Application Executive Component (AEC), Test System Component (TSC) and Model Editing Component (MEC) that plug into our \\\"Interoperable, Connectivity Enabling Framework\\\" (ICEF) based on COM/DCOM. The four components and framework are discussed in general terms. The DEC implements AI-ESTATE and is further discussed in derail as are the other components. Also discussed are operational uses, diagnostic development, vendor competition and benefits.\",\"PeriodicalId\":334061,\"journal\":{\"name\":\"2000 IEEE Autotestcon Proceedings. IEEE Systems Readiness Technology Conference. Future Sustainment for Military Aerospace (Cat. No.00CH37057)\",\"volume\":\"189 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"1999-08-30\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"8\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2000 IEEE Autotestcon Proceedings. IEEE Systems Readiness Technology Conference. Future Sustainment for Military Aerospace (Cat. No.00CH37057)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/AUTEST.2000.885625\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2000 IEEE Autotestcon Proceedings. IEEE Systems Readiness Technology Conference. Future Sustainment for Military Aerospace (Cat. No.00CH37057)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/AUTEST.2000.885625","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Implementing AI-ESTATE in a component based architecture, Phase-II
This paper discusses Phase-II of an Air Force funded SBIR R&D project concerned with implementing the IEEE 1232 Standard known as AI-ESTATE in a component based Automatic Test System (ATS). The intent of our Phase-II work is to provide the Air Force with a "working tool" that demonstrates the utility of our architectural approach as well as the utility of AI-ESTATE. The intent of our component based approach to ATS design is to provide a de-coupling of the diagnostic reasoner from the rest of the ATS as well as provide for a true open system at a reduced procurement and maintenance costs. AI-ESTATE is used to provide a standardized interface between the reasoner and the other ATS elements as well as provide standardized information and data model formats. The architecture consists of a COTS Test System (VXI package with LabVIEW), four "domain" type components: Diagnostic Engine Component (DEC), Application Executive Component (AEC), Test System Component (TSC) and Model Editing Component (MEC) that plug into our "Interoperable, Connectivity Enabling Framework" (ICEF) based on COM/DCOM. The four components and framework are discussed in general terms. The DEC implements AI-ESTATE and is further discussed in derail as are the other components. Also discussed are operational uses, diagnostic development, vendor competition and benefits.