Voting Precincts

Loading
loading...

Voting Precincts

November 5, 2024
mike@standardsmichigan.com
,
No Comments

Today we refresh our understanding of the standard of care for hosting elections in public spaces such as schools, colleges and universities.

In the United States, polling places can be located in a variety of public and private facilities, not just in public schools. While public schools are commonly used as polling places due to their widespread distribution and accessibility, they are not necessarily the largest proportion of polling places nationwide. The specific locations of polling places can vary by jurisdiction and are determined by local election officials. Other common polling place locations include community centers, churches, libraries, government buildings, and private residences.

The selection of polling places is based on factors like accessibility, convenience, and the need to accommodate a specific number of voters within a given precinct or district. The goal is to ensure that voters have reasonable access to cast their ballots on election day. The use of public schools as polling places is widespread but not universal, and the distribution of polling places across various types of facilities can vary from one region to another.

2024 International Building Code Appendix E: Supplementary Accessibility Requirements

NFPA 730 Guide to Premises Security: 2026 First Draft Report | Consultation closes January 3, 2025

“Election Day” 1944″ Norman Rockwell

The political party that claims that “democracy is at stake” today’s election is the same political party that seeks to federalize state election laws, pack the Supreme Court, remove the Electoral College, remove US national borders and abolish voter identification will be voting in today’s off-year elections.   In other words: it wants to abolish democracy.  Its partisans have long since metastasized in education communities where polling places for students, faculty, staff and nearby residents are hosted.

Join us in post-irony America today when we focus only on the safety and environmental condition of these polling places.   Where there is closer agreement.  Catalogs, titles, chapters, sections and passages that inform best practice on this topic:

Can Voters Detect Malicious Manipulation of Ballot Marking Devices?

 

International Code Council

International Building Code

A117 Accessible and Useable Buildings and Facilities

National Fire Protection Association

Life Safety Code

Premises Security

ASHRAE International

Thermal Environmental Conditions for Human Occupancy

Illumination Engineering Society

Designing Lighting for People and Buildings

Security 100

Sacramento County: Polling Place and Vote Center Management

 

Abiit sed non oblitus | Joseph P. Overton

November 5, 2024
mike@standardsmichigan.com
,
No Comments

This content is accessible to paid subscribers. To view it please enter your password below or send mike@standardsmichigan.com a request for subscription details.

Can Voters Detect Malicious Manipulation of Ballot Marking Devices?

November 5, 2024
mike@standardsmichigan.com
, ,
No Comments

 

Can Voters Detect Malicious Manipulation of Ballot Marking Devices?

Matthew Bernhard, et. al

University of Michigan

 

Abstract:  Ballot marking devices (BMDs) allow voters to select candidates on a computer kiosk, which prints a paper ballot that the voter can review before inserting it into a scanner to be tabulated. Unlike paperless voting machines, BMDs provide voters an opportunity to verify an auditable physical record of their choices, and a growing number of U.S. jurisdictions are adopting them for all voters. However, the security of BMDs depends on how reliably voters notice and correct any adversarially induced errors on their printed ballots. In order to measure voters’ error detection abilities, we conducted a large study (N = 241) in a realistic polling place setting using real voting machines that we modified to introduce an error into each printout. Without intervention, only 40% of participants reviewed their printed ballots at all, and only 6.6% told a poll worker something was wrong. We also find that carefully designed interventions can improve verification performance. Verbally instructing voters to review the printouts and providing a written slate of candidates for whom to vote both significantly increased review and reporting rates-although the improvements may not be large enough to provide strong security in close elections, especially when BMDs are used by all voters. Based on these findings, we make several evidence-based recommendations to help better defend BMD-based elections.

 

IEEE provides this article for public use without charge.

Solidity

November 5, 2024
mike@standardsmichigan.com
, , , ,
No Comments

Solidity is a high-level, statically-typed programming language used for developing smart contracts on the Ethereum blockchain. Smart contracts are self-executing contracts with the terms of the agreement between buyer and seller written directly into lines of code. Solidity was specifically designed for the Ethereum platform, and it is the most widely used language for creating Ethereum-based smart contracts.

The code below shows how delegated voting can be done so that vote counting is automatic and completely transparent at the same time.

Photograph by Carol M. Highsmith. Library of Congress,

pragma solidity ^0.7.0;

/// @title Voting with delegation.
contract Ballot {
    // This declares a new complex type which will
    // be used for variables later.
    // It will represent a single voter.
    struct Voter {
        uint weight; // weight is accumulated by delegation
        bool voted;  // if true, that person already voted
        address delegate; // person delegated to
        uint vote;   // index of the voted proposal
    }

    // This is a type for a single proposal.
    struct Proposal {
        bytes32 name;   // short name (up to 32 bytes)
        uint voteCount; // number of accumulated votes
    }

    address public chairperson;

    // This declares a state variable that
    // stores a `Voter` struct for each possible address.
    mapping(address => Voter) public voters;

    // A dynamically-sized array of `Proposal` structs.
    Proposal[] public proposals;

    /// Create a new ballot to choose one of `proposalNames`.
    constructor(bytes32[] memory proposalNames) {
        chairperson = msg.sender;
        voters[chairperson].weight = 1;

        // For each of the provided proposal names,
        // create a new proposal object and add it
        // to the end of the array.
        for (uint i = 0; i < proposalNames.length; i++) {
            // `Proposal({...})` creates a temporary
            // Proposal object and `proposals.push(...)`
            // appends it to the end of `proposals`.
            proposals.push(Proposal({
                name: proposalNames[i],
                voteCount: 0
            }));
        }
    }

    // Give `voter` the right to vote on this ballot.
    // May only be called by `chairperson`.
    function giveRightToVote(address voter) public {
        // If the first argument of `require` evaluates
        // to `false`, execution terminates and all
        // changes to the state and to Ether balances
        // are reverted.
        // This used to consume all gas in old EVM versions, but
        // not anymore.
        // It is often a good idea to use `require` to check if
        // functions are called correctly.
        // As a second argument, you can also provide an
        // explanation about what went wrong.
        require(
            msg.sender == chairperson,
            "Only chairperson can give right to vote."
        );
        require(
            !voters[voter].voted,
            "The voter already voted."
        );
        require(voters[voter].weight == 0);
        voters[voter].weight = 1;
    }

    /// Delegate your vote to the voter `to`.
    function delegate(address to) public {
        // assigns reference
        Voter storage sender = voters[msg.sender];
        require(!sender.voted, "You already voted.");

        require(to != msg.sender, "Self-delegation is disallowed.");

        // Forward the delegation as long as
        // `to` also delegated.
        // In general, such loops are very dangerous,
        // because if they run too long, they might
        // need more gas than is available in a block.
        // In this case, the delegation will not be executed,
        // but in other situations, such loops might
        // cause a contract to get "stuck" completely.
        while (voters[to].delegate != address(0)) {
            to = voters[to].delegate;

            // We found a loop in the delegation, not allowed.
            require(to != msg.sender, "Found loop in delegation.");
        }

        // Since `sender` is a reference, this
        // modifies `voters[msg.sender].voted`
        sender.voted = true;
        sender.delegate = to;
        Voter storage delegate_ = voters[to];
        if (delegate_.voted) {
            // If the delegate already voted,
            // directly add to the number of votes
            proposals[delegate_.vote].voteCount += sender.weight;
        } else {
            // If the delegate did not vote yet,
            // add to her weight.
            delegate_.weight += sender.weight;
        }
    }

    /// Give your vote (including votes delegated to you)
    /// to proposal `proposals[proposal].name`.
    function vote(uint proposal) public {
        Voter storage sender = voters[msg.sender];
        require(sender.weight != 0, "Has no right to vote");
        require(!sender.voted, "Already voted.");
        sender.voted = true;
        sender.vote = proposal;

        // If `proposal` is out of the range of the array,
        // this will throw automatically and revert all
        // changes.
        proposals[proposal].voteCount += sender.weight;
    }

    /// @dev Computes the winning proposal taking all
    /// previous votes into account.
    function winningProposal() public view
            returns (uint winningProposal_)
    {
        uint winningVoteCount = 0;
        for (uint p = 0; p < proposals.length; p++) {
            if (proposals[p].voteCount > winningVoteCount) {
                winningVoteCount = proposals[p].voteCount;
                winningProposal_ = p;
            }
        }
    }

    // Calls winningProposal() function to get the index
    // of the winner contained in the proposals array and then
    // returns the name of the winner
    function winnerName() public view
            returns (bytes32 winnerName_)
    {
        winnerName_ = proposals[winningProposal()].name;
    }
}

Quick Veggie Soup

November 4, 2024
mike@standardsmichigan.com

No Comments

https://studentwellness.uiowa.edu/recipes/soup-recipes

FASB | Revenue Recognition for Grants

November 4, 2024
mike@standardsmichigan.com

No Comments

“The Attributes of the Arts and the Rewards Which Are Accorded Them” | Jean Baptiste Siméon Chardin (1766)

We follow a suite of standards developed by the Financial Accounting Standards Board (FASB) — among them, documents that discover and recommend best financial management practice for not-for-profit organizations common in almost all of the US education industry.  At the moment we do not advocate assertively in the FASB suite but we do follow the action as it pertains to the education industry and the activity of the many education industry trade associations whose advocacy activity we do follow.   

Current Standardization Projects

Stakeholders in the US education industry are encouraged to communicate directly with the FASB on any issue:  Accounting Standards Updates Issued 

The FASB suite is a standing item on our colloquia covering education industry accounting practice generally and grant and construction project accounting specifically.

Issue: [17-350]

Category: Finance

Related:

Consortia v. Ad Hoc, v. de Facto standard development platform comparisons 

http://www.fasb.org/academics

Upcoming Meetings


 

Russell Group

November 3, 2024
mike@standardsmichigan.com
, ,
No Comments

This content is accessible to paid subscribers. To view it please enter your password below or send mike@standardsmichigan.com a request for subscription details.

Mortuary Arts

November 1, 2024
mike@standardsmichigan.com
, ,
No Comments

“Marat Assassinated” | Jacques-Louis David 1793

There are several ANSI accredited standards that apply to mortuary science, particularly in the areas of forensic science and medicolegal death investigation. These standards are developed to ensure the highest levels of professionalism, quality, and consistency in the field. Here are some key standards:

  1. ANSI/ASB Best Practice Recommendations: The American National Standards Institute in collaboration with the American Academy of Forensic Sciences has developed various standards, including those related to the handling and processing of human remains. For example, the ANSI/ASB Best Practice Recommendation 094-2021 outlines procedures for postmortem friction ridge print recovery, emphasizing systematic approaches and legal compliance during the process​
    ANSI/ASB Standard 125-2021: This standard focuses on the general requirements for medicolegal death investigation systems. It covers infrastructure, personnel training, and competency requirements to ensure high-quality death investigations. It also references other professional guidelines and accreditation checklists from organizations such as the National Association of Medical Examiners and the International Association of Coroners and Medical Examiners

These standards are integral to maintaining rigorous protocols and ethical practices within mortuary science and related fields. They help ensure that procedures are consistent, legally compliant, and respectful of the deceased, ultimately contributing to the reliability and credibility of forensic investigations. For more detailed information, you can refer to the ANSI and ASB standards documentation available through their respective organizations.

Anatomical Donation

Virtual Gross Anatomy Lab

Standard for Interactions Between Medical Examiner, Coroner and Death Investigation Agencies

Interoperability of Distributed Energy Resources

November 1, 2024
mike@standardsmichigan.com

No Comments

IEEE Standard for Interconnecting Distributed Resources with Electric Power Systems is effectively the global standard for interconnection of distributed resources with large scale electric power systems.  It provides requirements relevant to the performance, operation, testing, safety, and maintenance of the interconnection.  Apart from the power reliability and sustainability zietgeist we have seen in campus bulk power distribution systems, this title is usually referenced in research projects undertaken in university research enterprises.  The standard is intended to be universally adoptable, technology-neutral, and cover distributed resources as large 10 MVA.  To wit:

IEEE 1547-2018 Standard for Interconnection and Interoperability of Distributed Energy Resources with Associated Electric Power Systems Interfaces: This standard — emerging from IEEE Root Project 1547.3 — 2007 asserts first principles for improved performance for distributed energy resources, connected to the grid. NIST funding aided this standard’s development.   Links to related titles, recently released for public consultation, are listed below:

P1547.2/D6.5, August 2023 – IEEE Approved Draft Application Guide for IEEE Std 1547™, IEEE Standard for Interconnecting Distributed Resources with Electric Power Systems

1547.3 Guide for Cybersecurity of DER Interconnected with Electric Power Systems | Comments due May 27

Guide to Using IEEE Standard 1547 for Interconnection of Energy Storage Distributed Energy Resources | Comments Due May 6th

We collaborate with the IEEE Education & Healthcare Facilities Committee on this an related titles.   This committee’s meetings are held 4 times monthly in European and American time zones.  International Electrical Technical Commission titles are items on the standing agenda; a few representative titles are listed in addition to IEEE titles below:

IEC 62746-10-1:2018 Systems Interface Between Customer Energy Management System and the Power Management System – Part 10-1: Open Automated Demand Response: This standard specifies how to implement a two-way signaling system, between utilities and customers, thus allowing utilities to adjust the grid’s load, based on demand. NIST’s David Holmberg and Steve Bushby presented research to the International Electrotechnical Commission (IEC), aiding this US standard’s acceptance as an international one.

IEC 62746-10-3:2018, Systems Interface Between Customer Energy Management System and the Power Management System – Part 10-3: Open Automated Demand Response – Adapting Smart Grid User Interfaces to the IEC Common Information Model: Related to the previous standard, IEC 62746-10-3:2018 defines the interfaces, as well as, the messaging for this two-way signaling system. NIST’s Holmberg and Bushby also facilitated this international standard’s acceptance.

IEEE 21451-001-2017 Recommended Practice for Signal Treatment Applied to Smart Transducers: This guide supports the ability to uniformly processing and classifying data from sensors and actuators in a smart system. The standard enables a common interpretation of data and grid interoperability. NIST personnel served on this standard’s working group, providing NIST research on sensors and actuators.

IEEE 2030.7-2017 Standard for the Specification of Microgrid Controllers: This standard established requirements for controllers, used to sense and manage microgrids. These requirements inform the manufacturing of controllers, and ultimately enable grid interoperability. NIST funding aided this standard’s development.

IEEE 2030.8 Standard for Testing Microgrid Controllers: This testing standard helps verify that microgrid controllers meet these requirements, and, thus, will work as intended. NIST funding aided this standard’s development.

IEEE 1547-2018 Standard for Interconnection and Interoperability of Distributed Energy Resources with Associated Electric Power Systems Interfaces: This standard ushers in a new era of improved performance for distributed energy resources, connected to the grid. NIST funding aided this standard’s development.

To inform a United States position on IEC titles we follow the lead of the USNA/IEC whose activity we also track in the IEEE E&H Committee

Issue: [11-17]

Category: Electric, Energy

Colleagues: Mike Anthony, Bob Arno, Neal Dowling, Peter Sutherland

Standards Coordinating Committee Membership

Microgrids

 

Refrigeration Systems: Cadaver Preservation

November 1, 2024
mike@standardsmichigan.com
,
No Comments

Although specific temperature settings vary, gross anatomy labs are commonly kept at temperatures ranging from 55°F to 65°F (approximately 13°C to 18°C). This range balances the need for specimen preservation and the comfort and safety of individuals working in the lab. The 2022 Edition is widely incorporated by reference into public safety law; design, construction, maintenance operations best practice for laboratory health care occupancies.

ASHRAE 15 Safety Standard for Refrigeration Systems

Purpose:  This standard specifies safe design, construction, installation and operation of refrigeration systems.  It not apply to refrigeration systems using ammonia (R-717) as the refrigerant.

Scope: This standard establishes safeguards for life, limb, health, and property and prescribes safety requirements:

  • Design, construction, test, installation, operation, and inspection of mechanical and absorption refrigeration systems, including heat pump systems used in stationary applications;
  • Modifications including replacement of parts or components if they are not identical in function and capacity; and substitutions of refrigerant having a different designation.

ASHRAE Public Review Drafts

This standard provides safety requirements for refrigeration systems, which are often used in cadaver storage facilities to maintain appropriate temperatures. It includes guidelines on system design, installation, operation, and maintenance to ensure safe and reliable performance.  Student gross anatomy labs are typically kept at lower temperatures. Maintaining a cooler environment in these labs is important for several reasons:

  1. Preservation of Specimens: Lower temperatures help preserve cadavers and anatomical specimens by slowing down the decomposition process. This is crucial for maintaining the quality and usability of the specimens over extended periods.
  2. Control of Odors: Cooler temperatures can help minimize the release of odors from the preservation chemicals used, such as formaldehyde, which can be unpleasant and potentially harmful in higher concentrations.
  3. Health and Safety: Maintaining a lower temperature can reduce the volatilization of formaldehyde and other chemicals, thereby lowering the concentration of potentially harmful vapors in the air. This contributes to a safer environment for students and faculty.
  4. Comfort during Lab Sessions: Students and instructors often wear protective clothing, including lab coats and gloves, which can be uncomfortable in warmer environments. A cooler lab helps ensure comfort during extended periods of study and dissection.

While the specific temperature settings can vary, gross anatomy labs are commonly kept at temperatures ranging from 55°F to 65°F (approximately 13°C to 18°C). This range balances the need for specimen preservation and the comfort and safety of individuals working in the lab.

University of Michigan Mechanical Design Guidelines and General Specifications

Layout mode
Predefined Skins
Custom Colors
Choose your skin color
Patterns Background
Images Background
error: Content is protected !!
Skip to content