From Design Development to Production, One STE to Test Them All

Vi T Weaver, Juan E Ramos
{"title":"From Design Development to Production, One STE to Test Them All","authors":"Vi T Weaver, Juan E Ramos","doi":"10.1109/AUTOTESTCON47462.2022.9984774","DOIUrl":null,"url":null,"abstract":"Test equipment used to support engineering design development typically differs from the test equipment used to perform acceptance testing in a production factory. Because the timeframe in which engineering and production test equipment are needed during a product lifecycle is staggered, a program will develop two sets of test equipment for a single product. The primary driver for this strategy results from the long development cycles typically required of production test equipment or Special Test Equipment (STE). This drives the product design engineers to develop their own test benches, or lash-up equipment, so that they can begin integrating and testing their hardware as soon as it arrives. However, what if the barrier for the long STE development cycle were removed? What if a program could deliver test equipment within a 10-month timeframe, from when detailed physical block diagrams and requirements for the product were available to when the test equipment was built and ready to be integrated with the Unit Under Test (UUT)? With the right planning and test strategy, the need for unique engineering test benches would be eliminated. This paper explores the strategy for developing a single STE, which can be used throughout the entire life of a program from development to design verification to production. Additionally, the paper explores the methodology for implementing a 10-month STE development cycle through the use of a common core test capability, composable test capabilities for product unique capabilities, and product artifacts required to interface the test equipment to the product.","PeriodicalId":298798,"journal":{"name":"2022 IEEE AUTOTESTCON","volume":"109 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2022-08-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"2022 IEEE AUTOTESTCON","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/AUTOTESTCON47462.2022.9984774","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
引用次数: 0

Abstract

Test equipment used to support engineering design development typically differs from the test equipment used to perform acceptance testing in a production factory. Because the timeframe in which engineering and production test equipment are needed during a product lifecycle is staggered, a program will develop two sets of test equipment for a single product. The primary driver for this strategy results from the long development cycles typically required of production test equipment or Special Test Equipment (STE). This drives the product design engineers to develop their own test benches, or lash-up equipment, so that they can begin integrating and testing their hardware as soon as it arrives. However, what if the barrier for the long STE development cycle were removed? What if a program could deliver test equipment within a 10-month timeframe, from when detailed physical block diagrams and requirements for the product were available to when the test equipment was built and ready to be integrated with the Unit Under Test (UUT)? With the right planning and test strategy, the need for unique engineering test benches would be eliminated. This paper explores the strategy for developing a single STE, which can be used throughout the entire life of a program from development to design verification to production. Additionally, the paper explores the methodology for implementing a 10-month STE development cycle through the use of a common core test capability, composable test capabilities for product unique capabilities, and product artifacts required to interface the test equipment to the product.
从设计开发到生产,一个STE测试他们所有
用于支持工程设计开发的测试设备通常不同于用于生产工厂进行验收测试的测试设备。由于在产品生命周期中,工程和生产测试设备所需的时间框架是交错的,因此一个程序将为单个产品开发两套测试设备。该策略的主要驱动因素是生产测试设备或特殊测试设备(STE)通常需要较长的开发周期。这促使产品设计工程师开发他们自己的测试台或应急设备,以便他们可以在硬件到达时立即开始集成和测试。然而,如果STE开发周期长的障碍被消除了呢?如果一个程序可以在10个月的时间框架内交付测试设备,从详细的物理框图和产品需求可用到测试设备建成并准备与被测单元(UUT)集成,那会怎么样?有了正确的计划和测试策略,对独特的工程测试平台的需求将被消除。本文探讨了开发单个STE的策略,该策略可以在程序从开发到设计验证再到生产的整个生命周期中使用。此外,本文还探讨了通过使用公共核心测试能力、产品独特能力的可组合测试能力以及将测试设备连接到产品所需的产品工件来实现10个月STE开发周期的方法。
本文章由计算机程序翻译,如有差异,请以英文原文为准。
求助全文
约1分钟内获得全文 求助全文
来源期刊
自引率
0.00%
发文量
0
×
引用
GB/T 7714-2015
复制
MLA
复制
APA
复制
导出至
BibTeX EndNote RefMan NoteFirst NoteExpress
×
提示
您的信息不完整,为了账户安全,请先补充。
现在去补充
×
提示
您因"违规操作"
具体请查看互助需知
我知道了
×
提示
确定
请完成安全验证×
copy
已复制链接
快去分享给好友吧!
我知道了
右上角分享
点击右上角分享
0
联系我们:info@booksci.cn Book学术提供免费学术资源搜索服务,方便国内外学者检索中英文文献。致力于提供最便捷和优质的服务体验。 Copyright © 2023 布克学术 All rights reserved.
京ICP备2023020795号-1
ghs 京公网安备 11010802042870号
Book学术文献互助
Book学术文献互助群
群 号:481959085
Book学术官方微信