City of Boston

TPMS Sensor Technology Pilot

Privacy-First Traffic Analysis for School Transportation

Project Overview

Pilot Duration: October 8-10, 2025 | Location: Blue Hill Avenue near Quincy Street

Through its Office of Emerging Technology, the City of Boston is testing a novel approach to understanding traffic patterns that affect school bus routes using low-cost sensors that capture passive Tire Pressure Monitoring System (TPMS) signals broadcast by vehicle tires to detect and analyze traffic movement.

The Challenge

School buses across Boston Public Schools struggle with on-time arrivals. The city needs better traffic data to optimize routes and signal timing.

The Solution

Low-cost sensors that capture TPMS signals from passing vehicles to measure traffic flow, queue lengths, and intersection wait times.

The Goal

Validate whether this technology can provide actionable traffic data to improve school bus routing and traffic signal timing.

đź”’ Privacy-First Technology

Your Privacy is Protected

This pilot employs fundamentally privacy-protective technology. TPMS sensors broadcast anonymous, rotating identification codes from vehicle tires—they contain no personal information, no license plate data, no GPS coordinates, and cannot be linked to vehicle owners or operators. The City's sensors passively receive these public broadcasts to count and analyze traffic patterns.

What This Technology Does NOT Collect:

What This Technology DOES Collect:

  • Timestamps and signal strength (for traffic flow analysis)
  • Aggregate traffic patterns and vehicle counts
  • How is this different from cameras?

    Unlike camera-based traffic monitoring, TPMS sensors cannot capture images, identify individuals, or track specific people. This approach provides cities with traffic intelligence while avoiding the privacy concerns associated with visual surveillance infrastructure.

    Data Retention & Security

    Can TPMS Data Be Linked to Vehicle Owners?

    No. TPMS IDs are not connected to any government or manufacturer vehicle registration databases. Additionally, these IDs may change when sensors are replaced or serviced. Without external data that Code Metal and the City of Boston do not and will not collect, these signals remain completely anonymous.

    All privacy-related technical documentation is available to the public upon request.

    Detailed Pilot Scope & Technical Information

    â–Ľ

    Research Questions

    This proof-of-concept pilot seeks to answer the following questions in order of priority:

    1. Can TPMS sensors reliably detect and count vehicles in real-world intersection conditions?
      • What is the detection accuracy compared to professional traffic counts?
      • What is the effective range and optimal placement for sensors?
    2. Can we identify school buses by their unique TPMS signatures?
      • Do school buses have distinguishable TPMS signals?
      • If so, can this provide independent verification of GPS data?
    3. Can we extract meaningful traffic metrics from TPMS signal patterns?
      • Queue length estimation (repeated signals from stationary vehicles)
      • Intersection wait times
      • Turning movement counts
      • Vehicle type differentiation (if possible)
    4. Is this technology suitable for supporting Bloomberg Project traffic management goals?
      • Can it provide data useful for signal timing adjustments?
      • Can it measure effectiveness of traffic mitigation measures?
      • Is it cost-effective and scalable compared to alternatives?

    Pilot Timeline

    October 8, 2025

    Deployment and Controlled Testing

    Afternoon: Sensor Installation

    • Deploy 2-5 TPMS sensors at selected locations along Blue Hill Avenue near Quincy Street
    • Sensors positioned to monitor traffic flow while minimizing public visibility
    • Installation must be complete before 6:15am October 9
    • Weather note: Rain expected; assess any impact on installation or sensor performance

    Afternoon/Evening: Controlled Validation Testing

    • Known Vehicle Testing: Multiple drive-by tests using City-owned vehicle with known TPMS signature to establish baseline sensor performance
    • School Bus TPMS Identification: Visit Hoyt Street Bus Lot or King School (2:00pm-3:00pm) to capture TPMS signatures from multiple school buses
    October 9, 2025

    Full-Day Data Collection and Baseline Comparison

    7:00am - 7:00pm: Concurrent Data Collection

    • TPMS sensors collect continuous traffic data
    • Professional traffic counters conduct manual counts at same locations
    • Passive data collection—no active monitoring or intervention

    Priority Time Windows:

    • Morning school arrival: 7:30am - 8:30am
    • Afternoon school dismissal: 2:00pm - 3:00pm

    Professional traffic count will provide ground truth data including total vehicle volumes, turning movement counts, and queue lengths.

    October 10, 2025

    Analysis and Validation Report

    • Retrieve sensors and download datasets
    • Correlate TPMS sensor data with professional traffic count baseline
    • Develop initial models and assess data quality
    • Document technical performance, limitations, and unexpected findings
    • Prepare Phase 1 validation report with Phase 2 recommendations
    • Present findings to City stakeholders

    Success Criteria

    Phase 1 is considered successful if:

    • Sensors reliably detect vehicle presence with measurable accuracy
    • Data shows statistically significant correlation with professional traffic counts
    • Queue length or wait time can be estimated from TPMS signal patterns
    • Data quality is sufficient to inform traffic signal timing decisions
    • No significant technical failures or data loss during the collection period

    Bonus outcomes (not required for success):

    • School buses successfully identified by TPMS signatures
    • High correlation (>80%) between sensor counts and manual counts during peak hours

    The Technology: A Dual Innovation

    This pilot represents two innovations:

    1. The sensing approach itself: Using passive TPMS signals for traffic detection is a novel application of existing vehicle technology that is privacy-friendly, low-cost, and rapidly deployable.
    2. The modular sensor platform: The hardware architecture is designed to be adaptable—the TPMS detection component could theoretically be swapped for other sensor types (GPS, Bluetooth, etc.), creating a flexible platform for various traffic data collection needs.

    Future Vision

    If validated, the City of Boston Bloomberg Team envisions pairing this TPMS sensor technology with existing school bus GPS data to build a predictive model of traffic impacting school buses. This combined approach would provide both the "where buses are" (GPS) and the "what traffic conditions they're encountering" (TPMS sensors), treating the bus fleet as a representative sample of citywide traffic flow. This would enable Boston to identify bottlenecks and optimize traffic light timing along critical routes without the need for expensive new infrastructure.

    Project Responsibilities

    Office of Emerging Technology

    • Project and vendor management
    • Pilot evaluation
    • Site planning and installation support
    • Sensor hardware for the duration of the pilot
    • Data analysis and validation
    • Assist with in-person counts and data verification
    • Feedback summary and final report

    Boston Transportation Department (BTD)

    • Selection of pilot locations
    • Feedback on data quality and accuracy
    • Input on traffic management applications

    Questions or Concerns?

    If you have questions about this pilot program or concerns about privacy, please contact the City of Boston Office of Emerging Technology.

    Project Manager:
    Sam Brenner
    samuel.brenner@boston.gov
    617-519-1976

    All privacy-related technical documentation is available to the public upon request.