The practical aspects of TPS resource data discovery

Performing a complete and accurate desktop analysis of a Test Program Set (TPS) with all the supporting data can be an extremely exhaustive experience. True TPS transparency has plagued the world of test and diagnosis for decades. Programs managers and users have a need to know exactly how the TPS works and how the Automatic Test Equipment (ATE) resources are allocated. It is fundamental to automatically make available a total envelope of TPS instrument usage and determine or make suggestions about TPS resource allocation considerations or facts. Exposing TPS facts which are somewhat hidden and providing guidance to aid in the determination of planning and support is important for process improvement. The evaluation of ATE resource allocation for a group of TPSs will aid in ATE design engineering. TPS resource transparency needs to be made available to all high level users and managers. Those who use a TPS and those who manage or oversee TPSs should have the resource data readily available to evaluate the TPS to know things like resource allocation usage and how the resources are used to expose TPS instrument requirements for future development and support. There are many pertinent and critical aspects which pertain to instrument settings and usage. Instrument or resource evaluation for a TPS is a much needed notion to judge test program performance and long term support. ATE resource utilization, selection, and recurrent problems of specific instruments, programming techniques or instrument settings can be revealed. There is a potential to refine the way a unit is tested, how resources are allocated and if resources can be optimized. Optimal resource allocation can potentially lower test time, solve TPS weaknesses, and keep current with technology to reduce long term support costs. An emulator can reveal run-time inefficiencies, range settings, limit levels, check program flow, allow assigning values to TPS variables, etc. The comprehensive information contained in the TPS and supporting data can serve to expose under and over utilized test equipment, proper resource selection, and many other issues which determine the quality of the TPS and ATE resources. Software programmable algorithms could expose facts automatically. A TPS developed by different engineers can and probably will utilize different instruments and/or instrument settings to perform some tests. The optimal use of instrumentation can be seen by RTOK rates, diagnostics, optimal measurements and glitches. There will always be some similarities in a TPS developed by different engineers but optimizing resource allocation is vital. To do an automated analysis of TPS resource usage data does provide valuable information but there can be questions about whether or not the TPS developer allocated the ATE resources properly or optimally. It is a fact, TPS developers vary in skill level and there can be profound differences in how resources are allocated. Relying on improperly allocated resources can produce superfluous results. This paper will cover the practical aspects of TPS Resource data. Also discussed is the availability of resource data and how to derive this data.