{"title":"今天就计划明天的测试数据:让测试数据经得起未来考验的简单技巧","authors":"Tom Armes","doi":"10.1109/AUTEST.2016.7589631","DOIUrl":null,"url":null,"abstract":"The complexity and volume for manufacturing and engineering test data in modern electronics manufacturing is growing every year. The proliferation of formats and structures of data means that test data storage, retrieval and analysis becomes increasingly difficult. Each silo of test data (like subcomponent Supply, R&D, RMA, Manufacturing, and Repair) has different parameters, attributes, and testing procedures than the others. In addition, each business unit within an organization may have different procedures, testing nomenclature, and processes than other business units even if they're making the same products. Question: With these challenges in mind, if you were asked to choose a way to store your data for the next 30 years and make it usable and integrated with enterprise data, how would you do it? And with smart sensors expected to heavily impact manufacturing, how will you be able to gather additional product testing data and make it integrate with legacy data? In this paper and discussion, we'll talk about the available technologies and file formats that Test Engineers should consider when preparing to write out test data from complex manufacturing and engineering test beds. By storing and structuring your test data with the best practices discussed in this discussion track, you'll be able to do efficiently store, quickly analyze, and futureproof your test output to work with other enterprise data.","PeriodicalId":314357,"journal":{"name":"2016 IEEE AUTOTESTCON","volume":"73 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2016-09-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Planning tomorrow's test data today: Simple tips for future-proofing your test data\",\"authors\":\"Tom Armes\",\"doi\":\"10.1109/AUTEST.2016.7589631\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"The complexity and volume for manufacturing and engineering test data in modern electronics manufacturing is growing every year. The proliferation of formats and structures of data means that test data storage, retrieval and analysis becomes increasingly difficult. Each silo of test data (like subcomponent Supply, R&D, RMA, Manufacturing, and Repair) has different parameters, attributes, and testing procedures than the others. In addition, each business unit within an organization may have different procedures, testing nomenclature, and processes than other business units even if they're making the same products. Question: With these challenges in mind, if you were asked to choose a way to store your data for the next 30 years and make it usable and integrated with enterprise data, how would you do it? And with smart sensors expected to heavily impact manufacturing, how will you be able to gather additional product testing data and make it integrate with legacy data? In this paper and discussion, we'll talk about the available technologies and file formats that Test Engineers should consider when preparing to write out test data from complex manufacturing and engineering test beds. By storing and structuring your test data with the best practices discussed in this discussion track, you'll be able to do efficiently store, quickly analyze, and futureproof your test output to work with other enterprise data.\",\"PeriodicalId\":314357,\"journal\":{\"name\":\"2016 IEEE AUTOTESTCON\",\"volume\":\"73 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2016-09-01\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2016 IEEE AUTOTESTCON\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/AUTEST.2016.7589631\",\"RegionNum\":0,\"RegionCategory\":null,\"ArticlePicture\":[],\"TitleCN\":null,\"AbstractTextCN\":null,\"PMCID\":null,\"EPubDate\":\"\",\"PubModel\":\"\",\"JCR\":\"\",\"JCRName\":\"\",\"Score\":null,\"Total\":0}","platform":"Semanticscholar","paperid":null,"PeriodicalName":"2016 IEEE AUTOTESTCON","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/AUTEST.2016.7589631","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Planning tomorrow's test data today: Simple tips for future-proofing your test data
The complexity and volume for manufacturing and engineering test data in modern electronics manufacturing is growing every year. The proliferation of formats and structures of data means that test data storage, retrieval and analysis becomes increasingly difficult. Each silo of test data (like subcomponent Supply, R&D, RMA, Manufacturing, and Repair) has different parameters, attributes, and testing procedures than the others. In addition, each business unit within an organization may have different procedures, testing nomenclature, and processes than other business units even if they're making the same products. Question: With these challenges in mind, if you were asked to choose a way to store your data for the next 30 years and make it usable and integrated with enterprise data, how would you do it? And with smart sensors expected to heavily impact manufacturing, how will you be able to gather additional product testing data and make it integrate with legacy data? In this paper and discussion, we'll talk about the available technologies and file formats that Test Engineers should consider when preparing to write out test data from complex manufacturing and engineering test beds. By storing and structuring your test data with the best practices discussed in this discussion track, you'll be able to do efficiently store, quickly analyze, and futureproof your test output to work with other enterprise data.