{"title":"模型命名策略","authors":"Thomas Killam","doi":"10.1109/ISPCE.2016.7492849","DOIUrl":null,"url":null,"abstract":"Paper outlines the issues with compliance model numbering. The paper illustrates the benefits of choosing a Numbering strategy that allows for variations in hardware without the need to choose a model number for each variation. The paper goes on to detail the information that will benefit the manufacturer in developing compliance reports that cover a range of configurations. Additionally I provide some tips on building future updates into the framework of the report when appropriate.","PeriodicalId":107512,"journal":{"name":"2016 IEEE Symposium on Product Compliance Engineering (ISPCE)","volume":"187 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2016-05-16","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"0","resultStr":"{\"title\":\"Model name strategy\",\"authors\":\"Thomas Killam\",\"doi\":\"10.1109/ISPCE.2016.7492849\",\"DOIUrl\":null,\"url\":null,\"abstract\":\"Paper outlines the issues with compliance model numbering. The paper illustrates the benefits of choosing a Numbering strategy that allows for variations in hardware without the need to choose a model number for each variation. The paper goes on to detail the information that will benefit the manufacturer in developing compliance reports that cover a range of configurations. Additionally I provide some tips on building future updates into the framework of the report when appropriate.\",\"PeriodicalId\":107512,\"journal\":{\"name\":\"2016 IEEE Symposium on Product Compliance Engineering (ISPCE)\",\"volume\":\"187 1\",\"pages\":\"0\"},\"PeriodicalIF\":0.0000,\"publicationDate\":\"2016-05-16\",\"publicationTypes\":\"Journal Article\",\"fieldsOfStudy\":null,\"isOpenAccess\":false,\"openAccessPdf\":\"\",\"citationCount\":\"0\",\"resultStr\":null,\"platform\":\"Semanticscholar\",\"paperid\":null,\"PeriodicalName\":\"2016 IEEE Symposium on Product Compliance Engineering (ISPCE)\",\"FirstCategoryId\":\"1085\",\"ListUrlMain\":\"https://doi.org/10.1109/ISPCE.2016.7492849\",\"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 Symposium on Product Compliance Engineering (ISPCE)","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/ISPCE.2016.7492849","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}
Paper outlines the issues with compliance model numbering. The paper illustrates the benefits of choosing a Numbering strategy that allows for variations in hardware without the need to choose a model number for each variation. The paper goes on to detail the information that will benefit the manufacturer in developing compliance reports that cover a range of configurations. Additionally I provide some tips on building future updates into the framework of the report when appropriate.