Coordinating the Use and Location of Weigh-in-Motion Technology for Kentucky

Martin, Andrew; Keathley, Valerie; Kissick, Jerry; Walton, Jennifer · 2014 · ROSA P / Kentucky. Transportation Cabinet

archive: archived pipeline: cataloged verified

Get this paper ↗ (full text — opens at the source; we link to it, we don't host it)

Summary

This report, commissioned by the Kentucky Transportation Cabinet (KYTC) and conducted by the Kentucky Transportation Center, addresses the need for a coordinated statewide plan to procure, manage, and share weigh-in-motion (WIM) technology. The study was motivated by the fact that multiple KYTC agencies—specifically the Division of Planning, the Division of Motor Carriers, and the Kentucky State Police Commercial Vehicle Enforcement Division—utilize WIM data for distinct purposes, including transportation planning, pavement design, and commercial vehicle enforcement. The authors sought to determine how these agencies could pool limited resources and coordinate efforts to maximize the benefits of expensive WIM equipment while minimizing redundancy. The research methodology involved a comprehensive review of existing literature on WIM data usage and sharing, a survey of state transportation agencies in other states to understand their operational practices, and an analysis of current WIM technologies, costs, and performance metrics. The study also inventoried existing WIM locations across Kentucky, noting that the Division of Planning maintains 35 WIM sites and the Division of Motor Carriers operates 13 weigh stations equipped with WIM scales. The authors examined competing technologies, such as piezoelectric sensors, and evaluated the specific accuracy requirements for enforcement versus planning applications. Key findings indicate that while WIM data is critical for meeting federal reporting requirements (such as the Highway Performance Monitoring System) and enforcing weight laws, there is no formalized data-sharing agreement among Kentucky agencies. Survey results from other states revealed that most WIM sites are located on routes with significant heavy truck travel, and while data sharing practices vary, few states have formalized agreements. In Kentucky, a significant barrier to coordination is the differing accuracy requirements: the Division of Planning accepts less expensive equipment with lower precision for traffic counts, whereas enforcement agencies require high-precision scales with a margin of error of only 2–3 percent for issuing citations. Additionally, the study identified that some existing WIM sites are non-functional due to communication issues, and that data accessibility is hindered by outdated data dictionaries and fragmented storage systems. The report concludes with ten recommendations to improve WIM utilization in Kentucky. Primary suggestions include establishing periodic discussions between the Division of Planning and the Division of Motor Carriers to identify opportunities for shared equipment and costs, particularly for Virtual Weigh Stations. The authors recommend leveraging the KYTC’s DataMart web portal to centralize WIM data access for public and agency users, thereby reducing administrative burdens. Further recommendations involve securing external funding through federal programs, exploring cost-effective pilot technologies like those from Intercomp, updating GIS data dictionaries for better usability, and repairing non-communicating WIM sites to increase data availability. Finally, the report advises commissioning a future study to optimize WIM site locations based on projected traffic patterns and advocating for state appropriations to support WIM maintenance.

Key finding

Kentucky state agencies currently operate WIM systems without formalized data sharing agreements, resulting in fragmented resource use despite clear opportunities for cost reduction and improved enforcement accuracy through interagency coordination.

Methodology

mixed_methods

Provenance

The full processing record for this entry. Every stage of this paper's journey through the pipeline is logged — what ran, with which tool and model, how many attempts it took, and when it last completed. Discovered via bulk_ingest_rosap on 2026-05-23 (6 acquisition events logged).

StageOutcomeToolModelPromptAttemptsCompleted
discover success rosap 2 2026-05-23
archive success 1 2026-05-23
extract success cached 2 2026-06-10
clean success 1 2026-06-01
chunk success 1 2026-06-01
embed success 1 2026-06-02
enrich success 1 2026-05-23
promote success 1 2026-05-23
summarize success llm qwen3.6-27b-prismaquant summ-v5 3 2026-06-10
tag success vector_similarity 24 2026-06-11
verify success 2 2026-06-10

Summary generated by qwen3.6-27b-prismaquant on 2026-06-10; verification: verified.

Topics

Ranked by relevance to this paper. Hover a topic for its definition.