{"resourceId":"sanjose-smart-curbs-field-validation-gaps-2025","versions":[{"version":"external-620381050ce4d045eee38a6b088dbaa82be8c0adcc83b5707ebbc9f237762368","resource":{"id":"sanjose-smart-curbs-field-validation-gaps-2025","title":"San José curb pilot exposes gaps between installed equipment and usable evidence","organization":"San José Department of Transportation, Umojo and PlaceWorks","sector":"Municipal curb management","geography":"San José, California, United States","publishedAt":"August 29, 2025","publicationDate":"2025-08-29","eventDate":null,"sourceName":"SMART Program implementation report, U.S. DOT National Transportation Library","sourceLabel":"Government pilot evaluation with vendor coauthors; historical field observations","sourceUrl":"https://rosap.ntl.bts.gov/view/dot/86342/dot_86342_DS1.pdf","evidenceClass":"government-evaluation","outcomeClass":"mixed","topics":["infrastructure","data-security","governance-procurement","accessibility-workforce","operating-model"],"finding":"The pilot integrated curb data but left important detection and validation gaps.","sledRelevance":"New-to-archive U.S. municipal implementation evidence; current deployment status is unverified.","evidence":"In one hour, observers recorded 18 events: nine lasting over four minutes appeared in platform data; nine shorter events did not. Sony outputs lacked city validation; missing IPS APIs prevented validation. The report describes staff capacity strain.","architectureImplications":"Interpretation: Test the entire sensor-to-dashboard path against local event durations, including data freshness and interruptions.","governanceImplications":"Interpretation: Keep unvalidated classifications out of consequential automated decisions.","securityPrivacyImplications":"Interpretation: Minimize imagery retention and test access, deletion and public-data export boundaries.","caveats":"An illustrative session, not a representative accuracy estimate. No causal congestion or safety benefit established. Sensor totals differ across sections; omitted. PDF screenshot failed; text and tables were inspected.","streamIds":["local-government"],"roles":{"sales":"Interpretation: Engage the transportation director, curb operations staff, public works, IT, accessibility representatives and procurement lead. Ask which decisions need timely curb observations and which missed events could misdirect those decisions. Offer a bounded corridor validation and integration assessment before a broader equipment purchase. The value hypothesis is a more defensible operational dataset, not guaranteed revenue, reduced crashes or shorter journeys. Discover existing assets and their approval dependencies. A small locality should assess whether it can maintain and review the proposed sensor estate. The historical pilot illustrates questions to ask; it does not establish a current opportunity or justify extrapolating one observation session.","engineering":"Interpretation: Start with a representative field protocol covering event duration, weather, lighting, user type and location. Compare independently annotated observations against timestamped platform outputs and report missed events separately from classification errors. Prerequisites include lawful sensor access, an agreed data model and operational APIs. Test latency, outages, duplicated records, stale curb rules and retrieval after a vendor change. Assess storage, bandwidth and retention across candidate edge, cloud and hybrid designs; the report is not a comparative hosting benchmark. A proof of value should demonstrate the required end-to-end fidelity before any agent is allowed to change allocations or initiate enforcement.","delivery":"Interpretation: Assign the curb service manager accountability and schedule joint work by field technicians, data engineers, procurement and accessibility staff. Obtain installation approvals, agree vendor interface milestones and train observers on a consistent rubric. Establish a governance checkpoint before operational use and another before expansion. Proposed acceptance requires every critical interface to pass tests, locally agreed recall for each priority event category, bounded reporting latency and a rehearsed manual fallback. These are proposed thresholds, not city results. Monitor data age and seasonal performance after launch. Risks include incomplete vendor delivery, observer workload, privacy objections and policy changes that make an otherwise accurate inventory obsolete."},"retrievedAt":"2026-09-14T03:01:51Z","enrichedAt":"2026-09-14T03:04:19Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Interpretation: Validate whether brief accessible loading activity is represented before using aggregate occupancy for allocation.","procurementImplications":"Interpretation: Tie milestones to working interfaces and field acceptance, not equipment delivery alone.","operatingModelImplications":"Interpretation: Fund a service owner and recurring field-validation capacity.","updateExplanation":"New to the full 274-resource archive checked at offsets 0, 100 and 200, including alternate URLs and related titles. No substantive update or development since the September 12 edition's completed run is claimed.","sourceVerification":{"openedUrl":"https://rosap.ntl.bts.gov/view/dot/86342/dot_86342_DS1.pdf","referenceExcerpt":"In one validation session, staff observed 18 curb events in an hour.","promptVersion":"sled-research-v3.2","model":null,"basis":"agent-reported inspection"}}}]}