From the Transportation edition of October 30, 2026
Transit agencies are testing AI's potential, report finds, with broader adoption likely
ASCE Civil Engineering Source, reporting on the American Public Transportation Association AI/ML primer · Transit agencies (association research) · United States
- Publisher
- ASCE Civil Engineering Source
- Original publication
- October 21, 2026
- Source retrieved
- 2026-10-31
What happened
Reporting on APTA's May 2026 primer, which surveyed 32 transit agencies: experimentation or consideration is highest in back office (50 percent), operations (47), customer support (44) and maintenance (41), but in every category only five or fewer surveyed agencies actually use AI tools. The article cites MTA camera enforcement results reported in the primer (bus lane speeds up 5 percent, collisions down 20 percent on average on relevant routes), a $60,000 CTA rail right-of-way intrusion pilot that reached 99 percent accuracy per the contractor, and researchers who say adoption is limited by data silos rather than AI. CapMetro cautions that oversight, pricing models and process quality determine whether uses are sustainable.
Why it matters
Newly relevant because it puts APTA's adoption data and practitioner cautions in front of the engineering audience this month; it supplies the base rate (few agencies in production) against which this week's transit AI announcements should be read.
Evidence and measured results
Secondary reporting on an association survey of 32 agencies (not a random sample) plus interviews; the 99 percent CTA figure is a contractor statement; MTA figures are quoted from the primer without method.
Limitations and uncertainty
APTA primer was published in May; survey size is small; several quantitative claims are secondhand; the article includes event promotion.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-30; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Transit agencies are experimenting widely with AI but few reach production, largely because data is siloed and governance and skills are immature.
- Stakeholders
- Transit agency CIOs and data leads
- Operations and maintenance directors
- Customer experience leads
- Procurement officers
- Discovery questions
- Which repetitive, checkable task would you automate first?
- Where do fare, schedule and AVL data live today?
- How will you monitor accuracy and cost after launch?
- Value hypothesis
- Starting with data integration for a verifiable task gives transit agencies a realistic path from experiment to production.
- Potential engagement
- A bounded data-readiness and use-case selection assessment for one transit agency.
- Unsupported claims
- Broad production adoption across agencies
- Guaranteed collision or speed improvements
- Validated accuracy of contractor-reported pilots
Pre-sales engineering
Role takeaway
- Fit
- Fits agencies needing data integration and evaluation design before scaling AI.
- Architecture and integration
- Integrating fare, schedule, AVL, maintenance and finance data into a governed layer that AI tools can access.
- Prerequisites
- Data inventory across departments
- AI policy and oversight roles
- Evaluation datasets for target tasks
- Constraints
- Small survey sample
- Federal and state compliance requirements
- Usage-based pricing limits
- Security
- Classify customer and operational data; set access controls and logging for AI tools that touch rider data.
- Proof of value
- Accuracy on a held-out set for the chosen task
- Cost per transaction tracked against budget
- False-alarm rate for video analytics
Delivery
Role takeaway
- Work
- Select one operational problem, integrate data, and run a measured pilot with oversight.
- Dependencies
- Departmental data owners
- IT integration capacity
- Procurement terms for usage pricing
- Ownership
- The operating department that owns the target process, with central data governance.
- Skills and adoption
- Train staff to assess AI outputs and to write AI procurement requirements.
- Governance checkpoints
- Use-case approval against agency AI policy
- Pre-launch accuracy review
- Post-deployment performance and cost review
- Acceptance criteria
- Proposed: target task accuracy meets agreed threshold before launch
- Proposed: monthly cost per use within budget
- Risks
- Pilots stall on data access
- Unmonitored customer-facing errors
- Unsustainable pricing
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Researchers identify siloed fare, schedule, finance and HR data as the main constraint, pointing to data integration before model deployment.
Governance
Who approves, reviews and stays accountable for outcomes?
APTA guidance lists governance structures, compliance with state and federal policy, and procurement skills as implementation challenges.
Security and privacy
What data, permissions and controls need testing?
CapMetro names accuracy, security, privacy and data handling as pre- and post-deployment considerations for customer-facing AI.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Training staff to use and assess AI tools and to write AI procurements is a named challenge; accessibility is listed among deployment considerations.
Procurement
What should contracts, pricing and exit terms secure?
CapMetro notes usage-based pricing can make a working use case unsustainable, a direct procurement consideration.
Operating model
Which teams own the service once it runs?
Experts recommend starting from an operational problem rather than from AI, and expect slow change to core agency operations.
Publication history
- 2026-10-30Transportation · Issue 0213 resources
Stable resource ID: asce-apta-transit-ai-primer-adoption-limits