TGDC Meeting Presentation July 26 th, 2011 Ian S. Piper Director, Certification Dominion Voting Systems, Inc. TGDC Meeting,

Slides:



Advertisements
Similar presentations
Copyright © 2000 by RT Lawrence Corporation. La Mirada, California, USA. All Rights Reserved. RTLFiRST Upload File Configuration Full control of configuration.
Advertisements

Introduction to OASIS EML (Election Markup Language) Presenter: David RR Webber Oracle Corporation February 8th, 2011
BRIDGE Project Overview of Modules
SERVICE MANAGER 9.2 VIEWS AND REPORTS July, 2011.
Voting Systems.  DS200 – new 2013  DS850 – new 2013  AutoMARK Voting Equipment.
12/9-10/2009 TGDC Meeting Ballot On Demand David Flater National Institute of Standards and Technology
Election Night Results and Reporting Webinar 1. Application Overview Election Results Reporting provides an easy and just-in-time reporting of Statewide.
ETen E-Poll ID – Strasbourg COE meeting November, 2006 Slide 1 E-TEN E-POLL Project Electronic Polling System for Remote Operation Strasbourg.
Commissioners of Elections William Scriber and Donald Wart Sequoia Voting Systems.
IEEE P1622 Meeting, Oct 2011 IEEE P1622 Meeting October 24-25, 2011 Overview of IEEE P1622 Draft Standard for Electronic Distribution of Blank Ballots.
Election Observer Training 2008 Elections Certification & Training Program
TGDC Meeting, July 2011 Review of VVSG 1.1 Nelson Hastings, Ph.D. Technical Project Leader for Voting Standards, ITL
Chapter 3: System design. System design Creating system components Three primary components – designing data structure and content – create software –
EPOCH 1000 File Management Data Logging and Reporting
Train The Trainer Employee Central Administration
Optical Scan Ballot. January Prior to Primary Election Establish Election Precincts Establish Election Precincts Absentee precincts Absentee precincts.
Ballot Processing Systems February, 2005 Submission to OASIS EML TC and True Vote Maryland by David RR Webber.
12/9-10/2009 TGDC Meeting TGDC Recommendations Research as requested by the EAC John P. Wack National Institute of Standards and Technology
TGDC Meeting, Jan 2011 UOCAVA Pilot Projects for the 2012 Federal Election Report from the UOCAVA Working Group Andrew Regenscheid National Institute of.
Improving U.S. Voting Systems The Voters’ Perspective: Next generation guidelines for usability and accessibility Sharon Laskowski NIST Whitney Quesenbery.
TGDC Meeting, July 2011 Overview of July TGDC Meeting Belinda L. Collins, Ph.D. Senior Advisor, Voting Standards, ITL
Practice Insight Instructional Webinar Series Reporting
Automark and Other Optical Scan Voting Systems Allen Stone CMSC-691V2/12/2006.
Voting Systems.  DS200  DS850  AutoMARK Voting Equipment.
Cosmos Security Feature Overview Product Planning Group Samsung IT Solutions Business 12 July 2010.
TGDC Meeting, July 2011 IEEE P.1622 Update John P. Wack Computer Scientist, Software and Systems Division, ITL
October 2003Bent Thomsen - FIT 3-21 IT – som værktøj Bent Thomsen Institut for Datalogi Aalborg Universitet.
COPYRIGHT © 2008 GIDEON TAYLOR CONSULTING. ALL RIGHTS RESERVED GT I-9 Screen Shots – 2008 Saturday, October 03, 2015.
Open Source Digital Voting: Overview of Data Format Definition Positions and Activities JOHN SEBES Chief Technology Officer OSDV FOUNDATION NIST Common.
1 Data List Spreadsheets or simple databases - a different use of Spreadsheets Bent Thomsen.
Secretary of State Voting System Security Standards Juanita Woods Secretary of State Elections Division HAVA Information Security.
IEEE P1622 Meeting, Feb 2011 Common Data Format (CDF) Update John P. Wack National Institute of Standards and Technology
NIST Voting Data Formats Workshop Gaithersburg October, 2009 Parker Abercrombie EML for Open Voting.
IEEE Working Group P1622 Meeting February 24-25, 2013 National Institute of Standards and Technology Gaithersburg, MD.
TGDC Meeting, December 2011 IEEE P1622 Common Data Format Standardization Update John P. Wack National Institute of Standards and Technology
Improving U.S. Voting Systems Interoperability in Election Data and Devices TGDC Meeting July 20 – 21, 2015 Improving U.S. Voting Systems 1 John P. Wack.
TGDC Meeting, December Common Data Format Directions John P. Wack National Institute of Standards and Technology
Campaign Plan Assignment One: District Research GOVT Spring 2015.
5.2 Scope: This standard defines common data interchange formats for event records for voting systems. Voting systems, including election administration.
Title Carolina First Steering Committee October 9, 2010 Online Voting System Design Yinpeng Li and Tian Cao May 3, 2011.
Create Content Capture Content Review Content Edit Content Version Content Version Content Translate Content Translate Content Format Content Transform.
Oct 15-17, : Integratability and Data Export Page 1Next VVSG Training Voting devices must speak (produce records) using a commonly understood language,
TGDC Meeting, July 2010 Report of the UOCAVA Working Group John Wack National Institute of Standards and Technology DRAFT.
Election Technology and Problems in the Field
McGraw-Hill/Irwin The Interactive Computing Series © 2002 The McGraw-Hill Companies, Inc. All rights reserved. Microsoft Excel 2002 Working with Data Lists.
TGDC Meeting, Jan 2011 Help America Vote Act (HAVA) Roadmap Nelson Hastings National Institute of Standards and Technology
TGDC Meeting, July 2010 Report on Other Resolutions from Dec 2009 TGDC Meeting John Wack National Institute of Standards and Technology
TGDC Meeting, July 2010 Report on Logging Requirements in VVSG 2.0 Nelson Hastings National Institute of Standards and Technology
TGDC Meeting, Jan 2011 Common Data Format (CDF) Update John P. Wack National Institute of Standards and Technology
WHY THE vvpat has failed
Microsoft Access 2000 Creating Queries, Reports and Web Pages.
WHAT CONSTITUTES A VOTE? Annual Training for County Election Officials
Support for a Common Data Exchange Format Election Systems & Software IEEE Standards Working Group P1622 Voting Systems Electronic Data Interchange February.
PRESENTATION. Parts of the PCOS (3) Operator LCD Screen with Counter (4) Printer Compartment (5) Transmission Port (9) “RETURN” Button (8) “CAST” Button.
PREPARATIONS FOR VOTING: IN QUEST OF INTEGRITY AND PUBLIC CONFIDENCE by Roy G. Saltman Consultant on Election Policy and Technology
Idaho Procedures M650 GREEN LIGHT OPTICAL SCAN TABULATOR.
1 NPE Election Results Process 3 Scanned Results Slips Results slips must be scanned and the images must be available on the system to enable.
7 th Grade Civics Miss Smith *pgs  Must be ___ years old by a set ____ before the next ________  Voter _________ protects your vote  No one.
Association of World Election Bodies Contents ICT–based Election Management Voter Registration and Identification Voting and Counting Examples.
Election Assistance Commission 1 TGDC Meeting High Level VVSG Requirements: What do they look like? February, 09, United States.
Update: Revising the VVSG Structure Sharon Laskowski vote.nist.gov April 14, 2016 EAC Standards Board Meeting 1.
TGDC Meeting, Jan 2011 Report from Workshop on UOCAVA Remote Voting Systems Nelson Hastings National Institute of Standards and Technology
TGDC Meeting, Jan 2011 UOCAVA Pilot Projects for the 2012 Federal Election Report from the UOCAVA Working Group Andrew Regenscheid National Institute of.
1 Election Day Operations for TSX Counties Prepared and Presented by: Matt Grubbs, Director of Elections/HAVA.
Ballot and Voting Judge Operations and Procedures (Election Day)
The 2016 Presidential Election in Montgomery County, Maryland
CDF for Voting Systems: Human Factors Issues
Election Judge Training for Mail Ballot Elections
Texas Secretary of State Elections Division
Texas Secretary of State Elections Division
Presentation transcript:

TGDC Meeting Presentation July 26 th, 2011 Ian S. Piper Director, Certification Dominion Voting Systems, Inc. TGDC Meeting, July 2011

Next Steps on a Common Data Format A look at the Interoperability Use Case Draft from IEEE P1622 TGDC Meeting, July 2011

Interoperability Interoperability has different meanings for different stakeholders. It’s important to establish a comprehensive overview of interoperability that provides a framework for developing a common data format. From that framework, certain implementation levels can be defined into which the elements of interoperability can be grouped. TGDC Meeting, July

Actors TGDC Meeting, July

Levels of Interoperability 1.Registered voter data, geo-political data, election definition data, blank ballot images, and election results data. 2.Ballot cast records, audit event logs, and ballot definition data (contests/candidates, but without specific ballot layout information). 3.Machine ballot definition data (with specific ballot layout information). 4.Machine configuration data. TGDC Meeting, July

Level 1 Interoperability Historically, data flows have been external to each system. EMS and VRS systems use import and export functions to transfer data between each other and to the State level systems (SES), VRS and EPB use similar functions between each other, and EMS exports blank ballot images for BBDS. However, each system has its own format that requires translation into each of the other systems’ formats. As these systems already have the capacity to interoperate through those import/export functions, it should be feasible for existing systems to be modified to transfer data in a format that complies with this level of interoperability. TGDC Meeting, July

SES State Election Systems VRS Voter Reg Systems BBDS Blank Ballot Dist Systems EMS Election Mgmt Systems Geo-political Election Definition Registered Voters Geo-political Election Definition Results Reporting Blank Ballot Images Geo-political Election Definition # Registered Voters Voter Turnout Level 1 Data TGDC Meeting, July 2011 EMS Election Mgmt Systems EPB Electronic Poll Books Geo-political Registered Voters Voters who voted Geo-political Election Definition 7

Level 2 Interoperability On a lower level, an EMS can provide data to other external systems, such as: – audit event logs, ballot cast records and election results to Audit Management Systems (AMS), and – ballot contest data to Blank Ballot Distribution Systems (BBDS). In addition to a common data format for audit logs, it would also be beneficial to have a common lexicon for audit log entries through which an analysis of an audit log can be done more efficiently and effectively. TGDC Meeting, July

BBDS Blank Ballot Dist Systems EMS Election Mgmt Systems Contests and Candidates per Ballot Style Level 2 Data AMS Audit Mgmt Systems Audit Event Logs Ballot Cast Records Results Reporting TGDC Meeting, July

Level 3 Interoperability On an underlying level within the EMS, the machine ballot definition data could be provided to BBDS systems. This information can be broken out into three segments that represent the type of ballot output from the BBDS. A.Non scan-able ballot. B.Scan-able ballot C.Scan-able ballot with required formatting. Note that the ability to generate a ballot that a VCD can scan depends on the BBDS printer being capable of producing a ballot that meets the VCD’s ballot specifications. TGDC Meeting, July

BBDS Blank Ballot Dist Systems EMS Election Mgmt Systems Segment A Ballot not scan-able by VCD, but with ordered contests, endorsements, rotations, straight party/recall contest associations, and ballot/precinct IDs. Level 3 Data Segment B Scan-able ballot with Segment A elements plus shape/size/color/position of voting targets, timing marks, control marks and special marks. Segment C Scan-able ballot with Segment B elements plus required font type/size/color, background color, watermark, color striping, and instructional text. TGDC Meeting, July

Level 4 Interoperability At the base level within the EMS, the machine configuration data that is downloaded to the VCDs could be provided to VCDs from other voting systems. This information would provide all the detail required for the machine’s operation. At this level of data interchange, one EMS could create memory devices for the VCDs of another EMS. Although the data on the downloaded memory devices would be interchangeable between VCDs, for election integrity, an EMS would only allow the upload of memory devices it has created. TGDC Meeting, July

EMS Election Mgmt Systems Level 4 Data VCD Vote Capture Devices VCD Vote Capture Devices EMS Election Mgmt Systems TGDC Meeting, July

Machine configuration data would include: Memory media ID Election header information Security and verification data Election data Rejection criteria Ballot sorting options Cast vote records Tally results counters Modem upload phone number Audit logs Level 4 Data For DRE interface devices, the data would also include: Header/footer sizes, number of columns, scaling factors Button type/size/position/justification Flags for voting, rendering, text wrapping Background colors for pages/labels/contests/candidates Instructional text, write-ins, audio, and default volumes TGDC Meeting, July

TGDC Meeting, July 2011