Nevada DMV outlines multi‑year technology overhaul; mainframe lift drives timeline and cost uncertainty

Nevada Department of Motor Vehicles leadership told a joint meeting of the Assembly Committee on Ways and Means and the Senate Committee on Finance that a multi‑year Department Transformation Effort (DTE) is shifting many customer services online but remains constrained by a 30‑year mainframe codebase that must be migrated or refactored before the project is complete.

The DMV’s director, Tanya Laney, and program lead Molly Lennon described progress on vehicle services rolled out so far and asked legislators to approve ongoing budget requests to continue vendor support, buy security tools and fund a technical independent verification and validation (IV&V) review. "Our transformation efforts intend to modernize legacy systems, thereby improving the efficiency and effectiveness of DMV operations," Lennon's prepared remarks said, and Laney told the committee she had been “thrilled to be here today.”

Why it matters: The department says a mainframe migration is the single greatest technical risk to completing DTE and that uncertainty about how much of the 30‑year code base must be refactored contributed to large shifts in the program’s projected cost. That uncertainty affects projected biennial costs, vendor staffing plans and the timeline for moving credentialing services online.

Key facts and program status - DTE is rolling out vehicle features first; the DMV reported it has processed over 33,000 dealer titles online and more than 10,500 rapid registration applications since August go‑live. Turbo Titles pilots are live in the Sahara and Elko offices, with a fuller expansion slated for April. - The DTE program account (4716) is staffed with 60 defined positions (29 FTE and 31 contractors) and supports nearly 100 vehicle features planned for delivery by fiscal year 2026 Q4, including specialty plates, online registration payments, disabled placard applications and fleet registration. - The department says it expects to begin design of credential products (noncommercial driver licenses and IDs) in fiscal year 2027; credential modernization is planned after vehicle core products are in place. - The DMV previously reported a “worst‑case” planning estimate of roughly $424 million for full transformation, later updated to a current projection of about $287 million; officials said the larger prior figure was a conservative scenario and that estimates will continue to change as mainframe assessment work reveals more detail.

Mainframe migration and MoveIt (budget account 4715) DMV technical staff and the MoveIt division presented a separate budget request (decision unit E300) to migrate the legacy CARs mainframe to an AWS cloud platform. MoveIt administrator Susie Pollard said the state’s Office of the Chief Information Officer (OCIO) is decommissioning mainframe support and that federal partners (AMVA/AAMVA connections) are retiring mainframe operations in January 2028, creating a deadline pressure to move off the current system.

Pollard told the committee the mainframe is at "end of faithful life" and that continued mainframe hosting costs could rise from roughly $3 million per year today to as much as $9 million if DMV became the last agency remaining on state mainframe operations. She said the DMV has completed an in‑depth assessment and will submit an updated budget amendment with final quotes.

Vendor reliance, staffing and transition Molly Lennon and Susie Pollard described a phased plan to ramp down vendor development and shift work in‑house by the end of fiscal year 2027 for vehicle core products. The DMV intends to hire a transition team of roughly 31 people (existing staff plus a small contingent of contractors) to be upskilled to assume program and technical roles. Lennon noted the program depends on continued contractor and vendor knowledge transfer (including work from implementation partner Slalom) and warned that retention and hiring challenges for skilled staff could affect the pace and cost of transition.

Budget items presented to the committee - DTE continuation requests: renewals for Salesforce licensing, MuleSoft middleware, ABBYY OCR, Drawbridge (finance), Nintex (templating), Tableau, AWS services and ongoing implementation support (Slalom and others). (Decision unit E550 and related requests) - One‑time FY26 request for a technical IV&V vendor to validate the future‑state architecture and security tooling. - Security tooling requests for FY26–27 to improve user and platform monitoring. - MoveIt decision units: E300 (mainframe lift/refactor to AWS — budget amendment forthcoming), E301 (request to add an unclassified deputy administrator to reduce silos), E302 (continuation of 4 MSA contractors), E349 (replacement of VxRail on‑premises hardware reaching end of life).

Officials emphasized discussion vs. decision: committee members were presented budget requests and project updates; no formal appropriations or votes occurred during the hearing. DMV leaders said any deviations in cost or timeline would be communicated to the Governor’s Finance Office (GFO) and the Legislative Counsel Bureau as needed.

Concerns raised by legislators Lawmakers questioned wide swings in program cost estimates, the causes of the 2026→2029 shift in planned completion, the degree of reliance on vendors (and on Slalom specifically), and hiring/retention for the in‑house transition team. Assemblymember Watts urged the department to present clearer estimates of ongoing licensing and staffing costs after implementation so the Legislature can anticipate maintenance budgets. Director Laney and Molly Lennon said they would continue to provide updates and that the department had removed a FY25 supplemental highway fund ask after internal adjustments.

What remains uncertain Officials said the exact scope and cost of the mainframe migration remain contingent on the full assessment and that an updated quote and budget amendment for the MoveIt mainframe lift will be submitted to the Legislature. The timeline for credentialing modernization also depends on successful mainframe integrations and IV&V validation.

Provenance: Committee testimony by Director Tanya Laney, Administrator Molly Lennon and Administrator Susie Pollard; on‑record Q&A with Assemblymembers Anderson, Watts and others.