Systems Research

Database repository using federated databases

Principal Investigators: A. Krishnamurthy, S. Gordon, J. Guiliani, P. Wyckoff
Funding Source: DoD, Army
Duration: 1/1/04 - 5/30/04

Description: Testing is an essential activity in the research, development, acquisition and operation of all DoD weapons and equipment. Many weapon systems are jointly developed across the services (the JSF, for example), and consequently, many of the test facilities are conducting tests on very similar or the same component or system. A component may also be tested at various stages during its lifetime, from development testing during the design of the system, to operational testing (for example, Wind-Tunnel tests of a turbine engine at AEDC, and Flight Tests of the same
engine at Eglin AFB.) Testing is expensive, and there can be great savings if the testing can be coordinated across test facilities and lifecycle stages. The ideal situation is where the test engineer has on-line and immediate access to all the test conditions and test results from previous tests of the component or system. But today, in most cases, the test data and the test conditions are typically stored in individual databases (or even flat files) at the different test locations. Because of concerns with security and increased workload, it is a very difficult task to convince the individual test sites to transfer the test data to a common location, or even to populate multiple databases with the test results. Thus, in order to achieve the goal of providing test engineers with access to data and metadata (i.e. test conditions) about previous tests, we need to find a way of federating these individual databases and deriving a common metadata representation of the tests. The objective of this project is to take a few concrete steps towards this goal by creating a Data Repository of Test Data and Metadata for three users: (a) The Store Separation Database at Arnold Engineering Center; (b) the Vehicle Telemetry Database at the Aberdeen Test Center; and (c) the Flight Performance Database at SIMAF.