[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-280971-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-280971-en":126},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","pca-doc-system-hardware-spec-rev02-lh-c-review-and-trace-table","PCA Doc - System Hardware Spec Rev02 - LH C - Review and Trace Table","","Vendor trace and review instructions for the PCA System Hardware Specification are organized into a revision-controlled workflow and a structured Applicable TDP Documents inventory. The procedure requires completing and saving review forms with incremented revision numbers, entering reviewer name and date, and compiling a table of TDP document titles, versions, dates, and file names. A Trace Table validates VVSG 2005 requirements by recording whether each requirement is traced, not traced, partially fulfilled, or not tested/supported, and by listing documentation and informational discrepancies.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/presentations/","Presentations",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/pca-doc-system-hardware-spec-rev02-lh-c-review-and-trace-table/280971/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/pca-doc-system-hardware-spec-rev02-lh-c-review-and-trace-table/280971.png","ImageObject",442,249,{"name":42,"@type":43},"Eden","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-10-28","2026-09-16",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",14,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"How does the review form revision number change across reviews?","Question",{"text":63,"@type":64},"The first completed review form uses revision number 01. As newer vendor document versions or additional documents are submitted to close discrepancies, each new examination is saved as a new revision number using Save As before updating names, versions, or file names.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"What information must be entered in the Applicable TDP Documents table?",{"text":68,"@type":64},"List each applicable TDP document by its Title, version, and date, using the Title from inside each document. In the “File name” column, copy the full document file name.",{"name":70,"@type":61,"acceptedAnswer":71},"What do the notations in the Trace Table comments mean?",{"text":72,"@type":64},"“Y” indicates fulfillment, “N” indicates not fulfilled, and “P” indicates partial fulfillment. “NT” means not tested (outside certification review scope), and “NS” means not supported for features not supported in the tested configuration.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},280971,1791725935,{"code":4,"msg":82,"data":83},"success",[84,88,93,97,102,107,112,117,122],{"id":85,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":86,"slug":87},11,90,"presentations",{"id":89,"doc_module":22,"doc_module_name":25,"category_name":90,"show_sort_weight":91,"slug":92},12,"Resumes",80,"resumes",{"id":55,"doc_module":22,"doc_module_name":25,"category_name":94,"show_sort_weight":95,"slug":96},"Invoices",70,"invoices",{"id":98,"doc_module":22,"doc_module_name":25,"category_name":99,"show_sort_weight":100,"slug":101},15,"Posters",60,"posters",{"id":103,"doc_module":22,"doc_module_name":25,"category_name":104,"show_sort_weight":105,"slug":106},16,"Social Media",50,"social-media",{"id":108,"doc_module":22,"doc_module_name":25,"category_name":109,"show_sort_weight":110,"slug":111},17,"Forms",40,"forms",{"id":113,"doc_module":22,"doc_module_name":25,"category_name":114,"show_sort_weight":115,"slug":116},18,"Letters",30,"letters",{"id":118,"doc_module":22,"doc_module_name":25,"category_name":119,"show_sort_weight":120,"slug":121},21,"Paper Templates",5,"papers-templates",{"id":123,"doc_module":22,"doc_module_name":25,"category_name":124,"show_sort_weight":4,"slug":125},158,"General","general-158",{"code":4,"msg":82,"data":127},{"doc_id":79,"user_id":128,"nickname":42,"user_avatar":129,"doc_module":22,"category_id":85,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":135,"language":136,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":12,"update_tm":140,"read_time":30},1374391974468,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","From the Vendor Trace document or declaration, identify all documents that pertain to the System Hardware Specification. Each submitted (Vol. 1, Sect. 1. 1) Technical Data Package document (Vol.2 Sect. 6.6) is reviewed (Vol. 1, Sect. [1.6.2.2](1.6.2.2)) .  \nNote about revisions: The first time a review form is completed, the form revision number is 01. As the review process continues, newer versions of vendor documents, or additional documents, will be submitted to close discrepancies. Each time new versions of documents are examined, the review form is saved with a new revision number. Save the form with the new revision (Save As) before you update the document names, versions and/or file names.  \nEnter your name and date on the new revision.  \nApplicable TDP Documents table: List each applicable TDP document. Put the Title from inside the document in the first column, along with the version and date. Under “File name,” copy the full document file name.  \nTrace Table: Verify whether the vendor correctly documented each applicable VVSG requirement listed in this template. Use the following notations to indicate results:  \n􀁸 Traced column: For each positive finding, enter the document number(s) corresponding to the Applicable TDP Documents Table below, with the section number(s) in each applicable document where the requirement is fulfilled. (Example: Doc. 2, Sec. 1.2)  \n􀁸 Comments column:  \no “Y” indicates that the document(s) fulfill the requirement.  \no “N” indicates that the document(s) do not fulfill the requirement.  \no “P” indicates that the document(s) partially fulfill the requirement  \no “NT”(not tested) indicates documents that are part of the system configuration but outside the scope of this certification review effort (only if not a full cert) .  \no “NS”(not supported) indicates requirements that apply to features that are not supported in the configuration being tested (such as paper ballots) .  \no Explain “P”, “N”, “NT” or “NS” findings here.  \no In addition, use the Comments column to enter any comments that would be helpful throughout the project.  \no Discrepancies:  \n􀁸 List discrepancies in red.  \n􀁸 A Documentation discrepancy is written when a VVSG requirement is not fulfilled or is partially fulfilled in the TDP.  \n􀁸 An Informational discrepancy is written when the issue is outside the scope of the certification; Informational discrepancies are provided to the client but do not preclude certification.  \n􀁸 Enter the discrepancy number of any discrepancies written (from the separate discrepancy report), with a short description in the Comments column.  \n\n| Vendor : | Hart InterCivic | Reviewer(s): | L. Hoppert |\n| --- | --- | --- | --- |\n| Voting System: | Verity 2.2.1 | Review Date: | 2/1/2017; Re-review 2/8/2017 |\n\nApplicable TDP Documents  \n\n| Document Title (from cover pg), version, date | Doc \\# | File name |\n| --- | --- | --- |\n| Verity Operational Guide, Rev B.02, no date | \\#1 | Verity Operational Guide 6640001 B02 |\n| Verity Voting Performance Characteristics, Rev B.01, 10/21/2016 | \\#2 | Verity Performance Characteristics 4005497 B01 |\n\nPCA Doc-System Hardware Spec Rev02_LH_C.doc Page 1 of 7  \nTemplate Version 05-08 Saved 2/8/2017 1:10 PM  \n| Document Title (from cover pg), version, date | Doc \\# | File name |\n| --- | --- | --- |\n| Bills of Materials: Scan, Touch Writer, Print, Ballot Box, Accessible Booth, AutoBallot Kit, Relay Accessory Kit | \\#3 | All Bills of Materials (BOMs) in the \"hardware\" folder-7 files |\n| Verity Scan schematics | \\#4 | 3005368-Scan |\n| Verity Touch Writer schematics | \\#5 | 3005352 folder (Touch Writer) |\n| (No document assigned) | \\#6 |  |\n| Verity Ballot Box schematics | \\#7 | 3005357 folder (BallotBox) |\n| Verity Standard Booth Assembly | \\#8 | 3005358 folder (Standard-Booth) |\n| Verity Accessible Booth Assembly | \\#9 | 3005359 folder (Accessible-Booth) |\n| Verity System Design: Verity Electronics Specification, Rev A. 10, 8/26/2016 | \\#10 | Verity Electronics Specific","cbCaieDPWMfYSubu","https://ap.wps.com/l/cbCaieDPWMfYSubu","pdf",56936,7,"English","# Applicable TDP Documents\n## Applicable TDP Documents table\n# Trace Table\n## Traced column\n## Comments column\n## Discrepancies","[{\"question\":\"How does the review form revision number change across reviews?\",\"answer\":\"The first completed review form uses revision number 01. As newer vendor document versions or additional documents are submitted to close discrepancies, each new examination is saved as a new revision number using Save As before updating names, versions, or file names.\"},{\"question\":\"What information must be entered in the Applicable TDP Documents table?\",\"answer\":\"List each applicable TDP document by its Title, version, and date, using the Title from inside each document. In the “File name” column, copy the full document file name.\"},{\"question\":\"What do the notations in the Trace Table comments mean?\",\"answer\":\"“Y” indicates fulfillment, “N” indicates not fulfilled, and “P” indicates partial fulfillment. “NT” means not tested (outside certification review scope), and “NS” means not supported for features not supported in the tested configuration.\"}]","PCA Doc - System Hardware Spec Rev02 - LH C - Review and Trace Table | PDF",1789563297]