{"resourceId":"ncta-lanternn-ai-incident-detection-i485-pilot","versions":[{"version":"external-ddf0ae67f7e35ea0d19e706e68d85f06f48681c4f2a2393c80697900d6a9ade0","resource":{"id":"ncta-lanternn-ai-incident-detection-i485-pilot","title":"Smart Roadway Incident Detection Pilot Program (Valerann Lanternn on I-485 Express Lanes)","organization":"North Carolina Turnpike Authority (NCDOT)","sector":"State DOT / toll authority","geography":"North Carolina, US","publishedAt":"Page last updated October 13, 2026","publicationDate":"2026-10-13","eventDate":"2026-05-01","sourceName":"NCDOT","sourceLabel":"NCTA program page","sourceUrl":"https://www.ncdot.gov/divisions/turnpike/Pages/roadway-incident-detection-program.aspx","evidenceClass":"government-evaluation","outcomeClass":"emerging","topics":["infrastructure","operating-model"],"finding":"The North Carolina Turnpike Authority is piloting Valerann's AI-powered Lanternn platform on the I-485 Express Lanes in Charlotte. Development began in March 2026 and the pilot began in May 2026. Lanternn analyzes NCTA's existing traffic cameras, navigation platforms and third-party data to flag crashes, stopped or slow vehicles, pedestrians, wrong-way drivers and other unusual conditions for Traffic Management Center operators, replacing continuous manual scanning of camera feeds. The page claims earlier detection and faster verification but reports no measured results.","sledRelevance":"A toll authority is testing AI incident detection layered over existing cameras and third-party data rather than new roadside hardware, a pattern other DOT traffic management centers can evaluate.","evidence":"Agency program page describing an active pilot; no detection rates, false-alarm rates, response-time changes or evaluation plan are published.","architectureImplications":"Software fusion of existing camera feeds, navigation-app data and third-party sources into TMC alerts; no new field devices described.","governanceImplications":"Agencies should define how AI alerts are verified by operators and what evaluation will decide whether the pilot continues.","securityPrivacyImplications":"Third-party data sharing and camera-feed access by a vendor platform need data-use terms; the page does not describe them.","caveats":"Self-description of a pilot without outcome data; claims of faster, more accurate detection are unquantified; single corridor.","streamIds":["transportation"],"roles":{"sales":"A toll authority is testing AI incident detection on existing cameras and third-party data, so the buyer conversation is about TMC operator workload and response time, not new hardware. Because NCTA has published no results, the useful offer is helping define the metrics a pilot like this should report: detection lead time, false alarms and operator verification time. Avoid citing faster detection as proven; the page asserts it without numbers.","engineering":"Lanternn fuses existing camera feeds, navigation-platform data and third-party sources into TMC alerts. Engineering checks should cover how feeds are accessed, latency from event to alert, false-positive rates by incident type and how alerts enter the existing ATMS or TMC workflow. Data-sharing terms with navigation and third-party providers matter as much as model accuracy, and the corridor's camera coverage limits what any detection layer can see.","delivery":"Delivery means turning a corridor pilot into an evidence-based decision. Interpretation: set baselines now for detection time and verification effort using historical TMC logs, then compare during the pilot. Ownership sits with NCTA's TMC operations. Delivery should also document how operators handle false alerts and whether alert volume changes staffing needs before any expansion beyond I-485. Results should be shared with NCDOT's other TMCs so any expansion decision rests on published evidence."},"roleDetails":{"sales":{"customerProblem":"TMC operators must scan many camera feeds to spot incidents, which delays detection on express lanes.","stakeholders":["NCTA Traffic Management Center operators","NCTA and NCDOT ITS leadership","Valerann (vendor)","Incident responders"],"discoveryQuestions":["What detection lead time and false-alarm rate will define pilot success?","Which third-party data sources feed the platform, under what terms?","How do operators verify and act on AI alerts today?"],"valueHypothesis":"AI fusion of existing data could shorten incident detection and reduce manual camera scanning, if pilot metrics confirm it.","potentialEngagement":"A bounded pilot-evaluation design: baseline TMC metrics, alert-quality measures and a go/no-go rubric.","unsupportedClaims":["Proven faster or more accurate detection (no data published)","Crash or secondary-crash reductions","Staffing savings"]},"engineering":{"fit":"Fits agencies with camera coverage and a staffed TMC that want detection without new field hardware.","architectureIntegration":"Ingests camera feeds, navigation-platform and third-party data; outputs alerts to TMC operators.","prerequisites":["Camera feed access for the vendor platform","Third-party data agreements","Historical incident logs for baselining"],"constraints":["Single express-lane corridor","Coverage limited by existing cameras","Third-party data availability varies by jurisdiction"],"security":"Vendor access to live camera feeds and external data requires access controls, retention limits and data-use terms.","proofOfValue":["Compare alert timestamps with TMC incident logs","Measure false-positive rate by incident type","Time operator verification per alert"]},"delivery":{"work":"Run the pilot evaluation and decide on expansion based on measured detection and workload results.","dependencies":["Valerann platform","NCTA camera network","Third-party data providers","TMC staff"],"ownership":"NCTA Traffic Management Center operations","skillsAdoption":"Operators need training on alert triage and on recording verification outcomes for evaluation.","governanceCheckpoints":["Evaluation metrics agreed before results are reviewed","Data-sharing terms reviewed","Expansion decision documented"],"acceptanceCriteria":["Proposed: median detection lead time improves versus baseline TMC logs","Proposed: false-alert rate per shift below an agreed threshold","Proposed: all alerts logged with verification outcome"],"risks":["Alert fatigue from false positives","Vendor lock-in on data fusion","Unpublished results limiting accountability"]}},"retrievedAt":"2026-10-31T22:01:38-05:00","enrichedAt":"2026-10-31T22:07:56-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Shifts TMC operator work from continuous camera scanning to reviewing prioritized alerts.","procurementImplications":"Pilot structured as a partnership with a software vendor; scaling would require a procurement decision informed by pilot metrics.","operatingModelImplications":"TMC operators remain responsible for verification and response; the platform changes how incidents are surfaced, not who acts.","sourceVerification":{"openedUrl":"https://www.ncdot.gov/divisions/turnpike/Pages/roadway-incident-detection-program.aspx","referenceExcerpt":"This automated approach detects incidents earlier, verifies them faster and reduces reliance on continuous manual camera monitoring.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}