scispace - formally typeset
Search or ask a question

Showing papers presented at "AUTOTESTCON in 1999"


Proceedings Article•DOI•
30 Aug 1999
TL;DR: This paper focuses on ways that COM will be used to transform instrument driver technology, and on the resulting benefits for test systems in general.
Abstract: The Component Object Model (COM) is an object-oriented standard for reusable binary components. COM reusability is based not only on component reuse, but on interface reuse. Client programs access COM objects only through defined interfaces, which may be reused from object to object. Interfaces hide implementation details (encapsulation). Interface reuse and inheritance provide runtime polymorphism. Interfaces can be precisely described with type libraries to development environments, and can be accessed remotely with little additional effort. COM technology has incredible potential for ATE. This paper focuses on ways that COM will be used to transform instrument driver technology, and on the resulting benefits for test systems in general. Runtime polymorphism supports syntactical interchangeability. The SCPI Consortium and the IVI Foundation are currently pursuing technologies that promise to deliver this level of interchangeability to the ATE market. COM will also provide natural solutions for driver deployment/integration, remote access, and a variety of other benefits as well. Ultimately COM will be used "in the box" to combine the functionality of driver and firmware.

27 citations


Proceedings Article•DOI•
30 Aug 1999
TL;DR: This paper introduces AgentLab, a distributed laboratory over Internet based on Java and mobile agents that ensures portability of measurement software, facilitates interoperability with existing I/O drivers and makes if possible to use mobile agents as the building blocks in-the-large.
Abstract: This paper introduces AgentLab, a distributed laboratory over Internet based on Java and mobile agents. Java ensures portability of measurement software, facilitates interoperability with existing I/O drivers and makes if possible to use mobile agents as the building blocks in-the-large. A measurement test is assembled as a collection of actors plus a runtime support, and is mapped onto a mobile agent. The set of the available test methods are kept in an object space. A measurement test is selected, configured, uploaded and launched by the end-user through a combination of Web and Java graphical user interface. The paper describes the AgentLab architecture and reports about its current implementation status.

26 citations


Proceedings Article•DOI•
R.P. Oblad1•
30 Aug 1999
TL;DR: This paper identities the key issues that have made if so difficult to achieve asset interchangeability and a set of rules and principles that must be applied to achieve robustAsset interchangeability.
Abstract: This paper identities the key issues that have made if so difficult to achieve asset interchangeability. Several of the historical attempts to solve the problem of asset interchangeability are described, along with an analysis of the reasons that they did not achieve the expected results. Specific topics that are covered are SCPI, VXIplug&play, IVI, ATLAS, and Measurement Subsystems. Principles associated with the ownership of interfaces will be outlined. Finally, a set of rules and principles will be discussed that must be applied to achieve robust asset interchangeability. Robust is defined as interchangeability that can be "guaranteed" without testing all TPSs against the modified test system.

16 citations


Proceedings Article•DOI•
30 Aug 1999
TL;DR: In this article, the authors presented the results obtained in the application of the impedance measurement technique for the needs of non-invasive sterility tests for two pilot food containers: (1) Tetra Brik Aseptic (TBA) cartons and (2) Stork Food & Dairy Systems (NL) plastic bodies.
Abstract: This paper presents the results obtained in the application of the impedance measurement technique for the needs of non-invasive sterility tests. Two pilot food containers have been chosen: (1) Tetra Brik Aseptic (TBA) cartons and (2) Stork Food & Dairy Systems (NL) plastic bodies. The main characteristics of the TBA cartons are-unstable shape, tolerances in size, packaging laminate comprising paper layer, plastic layers and aluminum foil. The characteristics of the Stork bottles are relatively stable shape and relatively thick walls. An electric model has been developed for the measured impedance. A relation is derived between the resistive component of the measured impedance and the conductivity of the food in TBA cartons. It has been also demonstrated that with the impedance technique it is possible to acquire information about some important properties of the food container during the sterility testing procedure. The microbiological tests with a number of bacterial species proved the potential of this new non-invasive sterility testing technique.

13 citations


Proceedings Article•DOI•
30 Aug 1999
TL;DR: An automated approach is presented that is capable of identifying the triggers of the robustness failures of COTS and legacy software modules and a fault model-the dimensionality model-is used to guide analysis.
Abstract: Software robustness problems may hinder the use of Commercial Off-The-Shelf (COTS) software modules and legacy software modules in mission-critical and safety-critical applications. This research focuses on hardening COTS and legacy software modules against robustness failures triggered by exceptional inputs. An automated approach is presented that is capable of identifying the triggers of the robustness failures. A fault model-the dimensionality model-is used to guide analysis. An experiment is described which demonstrates the feasibility of automating the process of analyzing failure causes and hardening against certain data types in POSIX function calls, for example, NULL pointer values and scalar data types such as INT and FLOAT. The final goal of this research is to provide users a tool to harden COTS and legacy software modules automatically.

13 citations


Proceedings Article•DOI•
30 Aug 1999
TL;DR: An overview of the use of wavelets in electrical and optical testing can be found in this article, where tools and routines for using wavelets are discussed for several programming languages and software packages including C/ATLAS, C, WAVELAB, MATLAB and the MATLAB Wavelet toolbox.
Abstract: Wavelets are very versatile signal-processing tools that can be used in automated testing for noise reduction, edge detection, focus determination of video camera, and multi-scale frequency/time domain analysis of signals. This paper presents an overview of wavelets and discusses how examples of the use of wavelets in electrical and optical testing are explored. Tools and routines for using wavelets are discussed for several programming languages and software packages including C/ATLAS, C, WAVELAB, MATLAB and the MATLAB Wavelet toolbox.

12 citations


Proceedings Article•DOI•
30 Aug 1999
TL;DR: The intent of the 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.
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.

11 citations


Proceedings Article•DOI•
30 Aug 1999
TL;DR: The paper outlines the requirements for a reusable test executive and reusable test programs and the process of creating test program sets (TPS) from generic test programs, using a TPS editor is described.
Abstract: The paper outlines the requirements for a reusable test executive and reusable test programs. The concepts of generic test programs and test program sets are introduced then the process of creating test program sets (TPS) from generic test programs, using a TPS editor is described. Various aspects of implementation are compared between HP VEE and NI LabView.

10 citations


Proceedings Article•DOI•
30 Aug 1999
TL;DR: In this article, the US Army Logistics Integration Agency has funded the development of a "Prognostics Framework" which is generic, open architecture, horizontal technology, and tailorable.
Abstract: US Army Policy is outpacing technology capability in the requirements for systems' prognostics. During the past five years, research and development (R&D) has been ongoing in the area of component prognostic techniques in laboratories, universities, and industry. The R&D has resulted in point solutions to specific items, but in general, they are expensive and provide limited system-level information. The US Army Logistics Integration Agency has funded the development of a "Prognostics Framework". This "Prognostics Framework" is generic, open architecture, horizontal technology, and tailorable. The Prognostics Framework approach will save time, money, and program-specific funds. It is the fastest way to converge various prognostics capabilities into manageable information for the system operators, the maintenance crew, and logistics planners across Army systems. The Prognostic Framework, a system-level prognostic manager, ties-in to logistics infrastructure, (e.g., IETM, logistics planning, mission planning, and spare parts provisioning). Prognostics Framework will be integrated with embedded diagnostics to provide a total "Health Management" capability. This paper will provide the initial information about Prognostics Framework architecture, design approach, and a brief summary of the prognostic mechanisms survey.

9 citations


Proceedings Article•DOI•
30 Aug 1999
TL;DR: The software designers at Hill Air Force Base have developed a voice recognition and speech synthesis system (Voice Control) for use with the F-16 Analog Test Station Sustainment project, which allows for dynamic specification of a grammar set, or legal set of commands.
Abstract: The software designers at Hill Air Force Base have developed a voice recognition and speech synthesis system (Voice Control) for use with the F-16 Analog Test Station Sustainment (FATSS) project. The Voice Control system is reliable, speaker independent, and has a total added hardware price tag of under $50.00 per station. In contrast to traditional voice recognition systems, operator training is not required. OO-ALC has developed a general-purpose internal interface (Voice Control) to the Speech Recognition and Text-To-Speech engines provided by Microsoft. Voice Control can be accessed by any 32-bit Windows software, which has windows messaging capability. This is available to standard programming languages such as LabWindows CVI, Borland or Microsoft C/C++, Visual Basic, or even commercial packages such as Lotus Notes, and Microsoft Word. Through Voice Control, the computer uses both video and voice prompts to request input from the operator. The operator is allowed to enter data and to control the software flow by voice command or from the keyboard or mouse. The Voice Control system allows for dynamic specification of a grammar set, or legal set of commands. The use of a reduced grammar set greatly increases recognition accuracy. The computer voice enables the operator to focus his attention away from the computer screen, which is required for activities such as probing a circuit card and taking readings. When the operator takes readings, the computer, to insure reliable entry, echoes his voice entries. With electronic tuning, speech synthesis allows the operator to hear the resulting reading, enabling him to focus on the circuit card instead of the constantly turning his head to see the computer screen. This paper describes the capability and functionality of the Voice Control system.

9 citations


Proceedings Article•DOI•
30 Aug 1999
TL;DR: This paper will propose an architecture with an open framework for ATS systems based on the emergence of Java as an open-systems, object-oriented computing environment and a vision for a Java-based ATS will be presented.
Abstract: The advent of Sun's Java Platform is the culmination of years of research and evolution in multiple areas of software technology. This paper will propose an architecture with an open framework for ATS systems based on the emergence of Java as an open-systems, object-oriented computing environment. Java blends the features of a platform-independent runtime environment with object-oriented architecture and distributed systems capabilities. The platform offers a unique opportunity to explore maximizing the reuse and integration of a large population of Java-based components to the development of automated test systems. In this paper the goals for such an architecture will be outlined and a vision for a Java-based ATS will be presented. Applying this new technology to automated test applications will enable software developers and their customers to achieve significant cost savings by increasing flexibility and productivity in the engineering of automated test program solutions.

Proceedings Article•DOI•
L.A. Orlidge1, E.D. Stoll•
30 Aug 1999
TL;DR: The paper describes the results of the development of the CASS Measurement Hardware Emulator (MHE) using synthetic instruments and shows that Synthetic Instrumentation is sufficiently mature to be included in service life extension programs of legacy ATE, to be inserted in current ATE such as CASS, and to become the basis of next generation ATE architecture, such as NxTest.
Abstract: Synthetic Instrumentation is a class of test devices, including measurers and stimulators, implemented primarily with software and supported with minimal hardware conditioning for the test signals. This philosophy permits frequent reuse of the hardware elements (processors, A/Ds, D/As, signal conditioners and switches) when commanding different instrument functions. Substantially lower purchase cost and life cycle cost per function are therefore achieved. The paper describes the results of the development of the CASS Measurement Hardware Emulator (MHE) using synthetic instruments. The functions developed included: spectrum analyzer, microwave transition analyzer, frequency/time interval counter, waveform digitizer and digital multimeter. Commercial-off-the-shelf elements included a VXI chassis, Slot-0 controller (PC), RF downconverter, two digitizers, and a wideband synthesizer used as the local oscillator. Performance results were largely competitive with existing standalone instruments. AlliedSignal's previous development work and the current MHE results show that Synthetic Instrumentation is sufficiently mature (1) to be included in service life extension programs of legacy ATE, (2) to be inserted in current ATE such as CASS, and (3) to become the basis of next generation ATE architecture, such as NxTest.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: In this paper, Hughes Space Communications applied IEEE Standard 1149.1-1990, The Standard Test Access Port and Boundary-Scan Architecture, to design a structured testing methodology for its HS601 digital global communication satellites.
Abstract: Hughes Space Communications applied IEEE Standard 1149.1-1990, The Standard Test Access Port and Boundary-Scan Architecture, to design a structured testing methodology for its HS601 digital global communication satellites. Previous functional test strategies were being challenged by increasing component density and rapidly increasing manufacturing volume. Structural tests written for ASICs were reusable when testing MCMs, boards, and units. Structural testing resulted in fewer no-fault-found components than previously experienced using functional test strategies. System test access across backplanes was achieved using National Semiconductor's multidrop, addressable 1149.1-based SCAN Bridge. Commercially available enhancements to Teradyne's Victory software were used to address each 1149.7-testable component at each level of the hardware hierarchy. Hughes Space Communications created test management software to manage this test environment. Whenever a test is needed, if is assembled to match the hardware version and the appropriate level of hierarchy. This paper presents the results for a global communications satellite system that uses a test strategy outlined.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: This paper describes an implementation of the Test Foundation Framework that is based upon the Microsoft Component Object Model (COM) and is called TFFCom(R) because it is implemented completely as a coordinated set of COM objects.
Abstract: This paper describes an implementation of the Test Foundation Framework (TFF) that is based upon the Microsoft Component Object Model (COM). The TFF architecture was developed between 1995 and 1998 within the IEEE SCC 20 ABBET (1226) Subcommittee. Several prototypes were created as a part of that effort to prove the technology. The implementation described here is called TFFCom(R) because it is implemented completely as a coordinated set of COM objects.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: A model-based methodology is described, specifically the Test Requirements Model (TeRM), which can be shown to facilitate the transfer of test-related product information between various stages of the life cycle and permits test requirement information to support value-added applications in the engineering process throughout the life Cycle of a product.
Abstract: Test requirements, which are generally collected in multiple disparate formats throughout the life cycle of an electronic product, could be used in various applications that reduce test and development cycle times and increase the confidence in the final test program. Unfortunately, test requirements are seldom captured in a consistent format that may be processed by a computer, thus eliminating the possibility of using such requirements in an engineering application. Additionally, such an approach disallows test requirements captured in one segment of the product life cycle to be reused in subsequent life cycle stages. This paper describes a model-based methodology, specifically the Test Requirements Model (TeRM), which can be shown to facilitate the transfer of test-related product information between various stages of the life cycle. This transportability, in conjunction with an exchange format that can be processed by a computer, permits test requirement information to support value-added applications in the engineering process throughout the life cycle of a product.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: In this article, the authors present a new approach for determining the optimum testability for systems with a long lifetime, opening a path towards effective cost savings for tailor-made systems.
Abstract: Product life-cycle costs outweigh by a significant margin those of product design, manufacture, and purchase. Often, this factor is not taken into account at design time, other than from experience gained on previous programs, at least not in any detail and certainly not by the individual designers. The reasons for this are typically due to the overall "titanic" complexities of this issue. Testability design, is of importance at all levels of the product design, i.e. chip, board, system, and the manufacture, installation and field service. Unfortunately, testability design is not taught to any detail in the educational establishments, and the need for "suitable" levels of testability is not often appreciated There are still many misunderstandings as to the capabilities of the various test methods and their likely impact upon the overall economics of product manufacture and maintenance previous work has demonstrated that the effective selection of testability methods can seriously reduce the cost of manufacturing test for chips, boards and systems. Some work has also been done to analyze aspects of field service of a particular type of consumer product. In this paper we present a new approach for determining the optimum testability for systems with a long lifetime, opening a path towards effective cost savings for tailor-made systems.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: Research performed in the development of COTS based test program sets capable of testing various avionics systems installed in operational aircraft was to determine the best course of action to allow the aircraft technician to troubleshoot and verify faults encountered during normal operation.
Abstract: This paper details research performed in the development of COTS based test program sets capable of testing various avionics systems installed in operational aircraft. The basis of this program was to determine the best course of action to allow the aircraft technician to troubleshoot and verify faults encountered during normal operation. This was accomplished by first developing an expert knowledge database covering problems and faults encountered by experienced aircraft technicians. The test system, dubbed the Avionics Test System (ATS), allows end-to-end performance testing of any avionics system from the installed antenna to the operator interface, visual or aural. The ATS gives the aircraft technician the ability to test the functions of the avionics systems using real-world performance criteria. The ATS end-to-end test capability tests all segments of the avionics systems giving a positive indication of faults in a real-world environment. With a graphical user interface, the technician's inputs are button presses vs. keystrokes allowing for incremental environment use. A wireless remote control capability provides the technician the ability to perform the majority of tests while seated in the cockpit or at a user station.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: The DoD Automatic Test System (ATS) Executive Agent Office (EAO) objective is to leverage technology to significantly reduce total ownership cost and the NxTest software architecture will meet the objectives by providing an open systems approach to the system software.
Abstract: The DoD has achieved success with recent Automatic Test Equipment (ATE) families, as evidenced by the Navy's Consolidated Automated Support System (CASS) and the Army's Integrated Family of Test Equipment (IFTE) programs. However, as these Systems age, the increased requirements for technology insertion due to instrument obsolescence and the demands of advanced electronics are becoming evident. Advances in test technology promise to yield reduced Total Ownership Costs (TOC) for ATE which can incorporate the new technology. The DoD Automatic Test System (ATS) Executive Agent Office (EAO) objective is to leverage technology to significantly reduce total ownership cost. Several objectives have been identified including use of synthetic instruments, support for legacy Test Product Sets (TPSs) and more efficient ways of developing TPSs. The NxTest software architecture will meet the objectives by providing an open systems approach to the system software. This will allow for the incorporation of commercial applications in the TPS development and execution environments and support current advances in test technology.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: This paper highlights the upgrade of the F-16 IAIS ATE to an open system architecture and details the actual degree of TPS transportability achieved and addresses the open architecture from the view of future hardware and software technology insertion.
Abstract: Upgrading legacy ATE while retaining the existing Test Program Set investment is a technical and economic challenge to the military and commercial test industry. The replacement of legacy ATE with commercial ATE, however, is only the start of the problem. Once an ATE is upgraded, the problem remains with constantly emerging technology that promotes rapid obsolescence. An upgrade to an open commercial architecture reduces this effort. This paper identifies one ATE, the F-16 Improved Avionics Intermediate Shop (IAIS), that has undergone a metamorphosis into a next generation open commercial architecture. Guiding this development were standard software and hardware interfaces that form an open system architecture. Through the implementation of this architecture, the new commercial-based IAIS increased its ability for future technology insertion and demonstrated its capability to execute the existing TPSs without modification. This paper highlights the upgrade of the F-16 IAIS ATE to an open system architecture and details the actual degree of TPS transportability achieved. Specifically, it identifies the processes and key attributes that were invaluable in reaching this high level of success and addresses the open architecture from the view of future hardware and software technology insertion.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: The development of a Virtual Interface Bus (VIBus) which consolidates multiple industry standard communication interface protocols into one driver/manager for a laptop or hand held PC application and solves two major existing problems.
Abstract: There is a growing demand in the automatic test industry for downsized and portable test systems. As a result, laptop and hand held PCs are now becoming more common in the test arena. However, there is a need to standardize and simplify both hardware and software interfaces between the laptop PC, test equipment, and the unit under test. This paper describes the development of a Virtual Interface Bus (VIBus) which consolidates multiple industry standard communication interface protocols into one driver/manager for a laptop or hand held PC application. The development was directed to incorporate the requirements of the IEEE-488, RS-422, Mil-Std-1553, and RS-232 bus protocols into a driver/manager that can be integrated into weapon system test platforms using portable PCs. The successful completion of the project solves two major existing problems: (1) A VIBus software driver/manager allows any of the communication interfaces to be used seamlessly; (2) All of the required interface protocols can be included in a standard laptop PC simultaneously. The solution involves the development of a PCMCIA bus expander that allows many COTS PCMCIA interface cards to be used without removing and replacing cards. The VIBus driver/manager selects the appropriate interface card and drivers as called for by a particular test or data retrieval program, or at the direction of a user.

Proceedings Article•DOI•
A. Purcell1•
30 Aug 1999
TL;DR: In this paper, the authors discuss motivations for replacing replacement and then look at the attributes of three candidate GPIB replacements: USB, network I/O, and IEEE 1394.
Abstract: This paper discusses motivations for replacing replacement and then looks at the attributes of three candidate GPIB replacements: USB, network I/O, and IEEE 1394 The paper then summarizes the Instrumentation & Industrial Control protocol (IICP) for IEEE 1394

Proceedings Article•DOI•
30 Aug 1999
TL;DR: For the purpose of this paper, the author relies heavily on his extensive US Navy ATE and TPS experience, as well as on previous studies performed on using BIT to fault diagnose UUT failures on US Naval Air weapon systems.
Abstract: This paper addresses using information derived from Built-in-Test (BIT) to fault diagnose Units Under Test (UUTs), wherever possible This philosophic approach to diagnostic testing is not new It has been studied over the past 20 years under the visor of "Integrated Diagnostics", but it has yet to be truly implemented in a "real life" military diagnostic test environment The mindset of Test Program Set design engineering, along with customer and contractor management alike, remains "complete diagnostic testing based upon single catastrophic component failure modes" If we are to generate cost efficient Test Program Sets (TPSs) under reduced military budget constraints, this will have to change! The test engineer must be encouraged to use methodologies to speed up development time and decrease TPS run times Using present technology, this is possible now, and as the technology matures, will become a truly viable approach in the future For the purpose of this paper, the author relies heavily on his extensive US Navy Automatic Test Equipment (ATE) and Test Program Set (TPS) experience, as well as on previous studies performed on using BIT to fault diagnose Unit Under Test failures on US Naval Air weapon systems

Proceedings Article•DOI•
30 Aug 1999
TL;DR: In this paper, the problem of determining parameters of the Giles-Atherton model used for defining hysteresis curves of magnetic materials was analyzed and a method for parameter determination was proposed.
Abstract: The problem of determining parameters of the Giles-Atherton model used for defining hysteresis curves of magnetic materials was analyzed. Results obtained by numerical simulation of hysteresis curves of the ferromagnetic, hard magnetic core and anisotropic materials have been given. The hysteresis curve obtained is in good agreement with the curve defined for these materials in the PSpice program packet. The proposed method for parameter determination enables simulation of any magnetic material, which has a characteristic R, Z or F-shaped hysteresis curve.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: In this article, the authors discuss the methods and techniques for identifying and managing the risks involved with automatic test systems development, and present a set of techniques to identify and manage these risks.
Abstract: Risk is the possibility of suffering loss. In a development project, the loss describes the impact to the project which could be in the form of diminished quality of the end product, increased costs, delayed completion, or failure. This paper discusses the methods and techniques for identifying and managing the risks involved with automatic test systems development.

Proceedings Article•DOI•
C. Puls1•
30 Aug 1999
TL;DR: As PXI continues to grow, it is important to understand its relationship to VXI, and a solid understanding of both architectures will help test engineers in the new millennium to properly configure systems using PxI, VXi, or both.
Abstract: Instrumentation has evolved in many ways over the past several decades. Standards such as GPIB and VXI made open, multi-vendor test systems possible and personal computer technology stretched overall capabilities and ease-of-use. Test technology for the new millennium now includes CompactPCI with PXI extensions. PXI directly couples PC technology with traditional instrument capabilities found in VXI to result in broader measurement and automation capabilities. Advanced measurement technology combined with the fast processing capabilities of today's PCs result in performance gains of more than 10X when comparing PXI to older architectures. As PXI continues to grow, it is important to understand its relationship to VXI. A solid understanding of both architectures will help test engineers in the new millennium to properly configure systems using PXI, VXI, or both.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: The Structured Architecture Test System is the culmination of several years of study to define a more structured approach to integrating VXI, PXI VME, IEC, RFI subset standards into a cohesive system solution, which reduces customization/augmentation, test program development, and interface costs, while increasing competition.
Abstract: The Structured Architecture Test System (SATS) is the culmination of several years of study to define a more structured approach to integrating VXI, PXI VME, IEC, RFI subset standards into a cohesive system solution. This is done primarily to preserve test program rehostability, equipment reconfigurability, and technology evolution requirements. It further reduces customization/augmentation, test program development, and interface costs, while increasing competition. Fundamental design is being developed through industry participation to assure product viability and long-term commitments to the standard. VXI Associates with government support will assist in completing the necessary coordination, funding, and standard's process. The program is actively seeking instrument suppliers to develop modules meeting the standard.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: The application of concurrent engineering during development of the F-16 Analog Test Station Sustainment (FATSS) project is discussed and how these principles can easily be applied to other development efforts are discussed.
Abstract: During the planning stage for development of a new test station or upgrade, one becomes very aware that there are many tasks to accomplish in a short period of time. It is often important to maintain a short development cycle while accomplishing both hardware and software tasks such as hardware selection and driver development. Concurrent engineering allows for a simultaneous activity of hardware and software personnel during test station development. This paper will discuss the application of concurrent engineering during development of the F-16 Analog Test Station Sustainment (FATSS) project and how these principles can easily be applied to other development efforts.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: An overview of the current and future directions of the AI-ESTATE standards is presented, and the concerns of document organization, information modeling, service versus API specification, and other issues raised by the AI -ESTATE community are addressed.
Abstract: We present an overview of the current and future directions of the AI-ESTATE standards. We address the concerns of document organization, information modeling, service versus API specification, and other issues raised by the AI-ESTATE community. We also discuss the vision of the AI-ESTATE subcommittee in its work to integrate the AI-ESTATE information models and projects such as testability/diagnosability assessment and test/maintenance feedback.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: The U.S. Navy and Lockheed Martin celebrated the delivery of the 400/sup th/ consolidated automated support system (CASS) station as discussed by the authors, which is now fielded on every United States carrier and shore-based Aircraft Intermediate Maintenance Department (AIMD) location, marine air logistics support sites, navy organic sites and five FMS countries.
Abstract: This year, the U.S. Navy and Lockheed Martin celebrated the delivery of the 400/sup th/ consolidated automated support system (CASS) station. CASS is now fielded on every United States carrier and shore-based Aircraft Intermediate Maintenance Department (AIMD) location, marine air logistics support sites, navy organic sites and five FMS countries. This paper provides a snapshot of CASS progress to date, summarizes realized cost savings, and presents a glimpse into the CASS future. To fulfill its expanded DoD role and to remain current with evolving ATE technologies, pre-planned product improvements have been continually introduced since its inception.

Proceedings Article•DOI•
30 Aug 1999
TL;DR: How the database provides recording and retrieval of comprehensive hardware and software configurations of measurement test scans is described, including its advantages and limitations.
Abstract: A sophisticated low-cost Configuration Management Database (CMD) has been developed for the Active Array Measurement Test Bed (AAMTB) at the Crane Division, Naval Surface Warfare Center, Crane Indiana. By choosing three flexible COTS programs that feature object-oriented models, a common programming language, and ODBC compliance, the software development and project cost was minimized. This paper describes how the database provides recording and retrieval of comprehensive hardware and software configurations of measurement test scans. Details of our database structure, including its advantages and limitations are also presented.