1 / 20

TRD\MVD Driver-Vehicle System

TRDMVD Driver-Vehicle System. Close Phase Certification Request. Agenda. Purpose of this Multi-project Close Request C-Mod Close IFTAIRP Close Driver-Vehicle Reengineering Close Questions. Purpose of the Close Request.

molly-osborn
Télécharger la présentation

TRD\MVD Driver-Vehicle System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TRD\MVD Driver-Vehicle System Close Phase Certification Request

  2. Agenda • Purpose of this Multi-project Close Request • C-Mod Close • IFTA\IRP Close • Driver-Vehicle Reengineering Close • Questions

  3. Purpose of the Close Request • Four other projects we associated with this main system reengineering projects under the ‘umbrella’ of the DRIVE MVD program. • Point-of-Sale – closed 02/08/2011 • Document Management System – closed 07/24/2013 • C-Mod • IFTA\IRP • During the PCC today, TRD will be placing a close request for: • C-Mod • IFTA\IRP • Driver-Vehicle Reengineering Project

  4. C-Mod Project Close

  5. CDLIS Modernization (C-Mod) Description • The Commercial Driver’s License Information System (CDLIS) is a nationwide computer system that enables state driver licensing agencies (SDLAs) to ensure that each commercial driver has only one driver’s license and one complete driver record. State driver licensing agencies use CDLIS to complete various procedures, including: • Transmitting out-of-state convictions and withdrawals • Transferring the driver record when a commercial driver's license holder moves to another state • Responding to requests for driver status and history • Commercial Drivers License Information System (CDLIS) Modernization 5.2 impacts CDLIS functionality in MVD2.0, mainframe, interfaces and miscellaneous MVD applications • Justification • With the cancellation of the Systems Vendor contract for MVD Reengineering, it became necessary to immediately begin modifications to legacy Driver applications to become compliant with C-Mod mandates by the January 30, 2012 deadline • C-Mod changes for Drivers will be used for the next iteration of MVD Reengineering • Non-compliance with CDLIS Modernization mandates would result in loss of federal funds to state agencies

  6. CDLIS Modernization (C-Mod) Federal Oversight • Because CDLIS Modernization 5.2 was mandated by the Federal Motor Carrier Safety Administration (FMCSA) and partially funded by a federal grant, the department was required to report to and work closely with FMCSA and the American Association of Motor Vehicle Administrators • Quarterly Reports to FMCSA for duration of project • Weekly meetings with AAMVA during development • Daily interaction with AAMVA during testing and implementation • Monthly reporting from AAMVA to FMCSA • CD 31 • Jurisdictions must run MPR Data Quality Validation and Verification (CD31) test within 30 days of the one-year anniversary (June 2013) of implementation date • Submit action plan within 30 days of test

  7. CDLIS Modernization (C-Mod) Budget – Project Came In Under Budget • Certification • Date – 09/27/2011 • Amount - $707,866.35 • Sources • Laws of 2008: Chapter 3, Section 7, Item 5 - $347,866.35 • CDLIS Modernization 2009 Grant - $360,000 • Actual Expenditures • Total - $541,424.99 • Sources • Special Appropriation - $323,029.82 • CDLIS Grant – $218,395.17

  8. CDLIS Modernization (C-Mod) Results • New Mexico Motor Vehicle Systems are 100% compliant with CDLIS Modernization 5.2 mandates • New Mexico was the twenty-third jurisdiction (out of 53) to complete implementation • CD31 Testing • Test results for New Mexico were very positive • Rated in the top-five jurisdictions in the county

  9. IFTA\IRP Project Close

  10. IFTA\IRP Justification • The Agency’s IRP/IFTA system were acquired from, and were maintained by ACS/Xerox on a fully hosted, sole-source contract basis. The ACS/Xerox contract, with all available contract extensions, expired on June 30, 2013. • Because there are a number of vendors in what is now a competitive marketplace for Motor Carrier systems, including IRP and IFTA, the Agency pursued a competitive bid RFP procurement process (RFP#20-333-00-11763) to identify and contract for an IRP/IFTA system solution that meets the Agency’s needs and offers the best value for the Agency.

  11. IFTA\IRP Description • The International Registration Plan (Plan) is a registration reciprocity agreement among states of the United States, the District of Columbia and provinces of Canada providing for payment of apportionable fees on the basis of total distance operated in all jurisdictions. • The International Fuel Tax Agreement (or IFTA) is an agreement between the lower 48 states of the United States and the Canadian provinces, to simplify the reporting of fuel use by motor carriers that operate in more than one jurisdiction. An operating carrier with IFTA receives an IFTA license and one decal for each qualifying vehicle it operates. The carrier files a quarterly fuel tax report. This report is used to determine the net tax or refund due and to redistribute taxes from collecting states to states that it is due.

  12. IFTA\IRP Budget & Actual *Theretainage invoice will be paid in FY14 with the licensing fee for FY14. Project was delivered on-time, on-budget, and with a high customer satisfaction level.

  13. Driver-Vehicle Reengineering CLOSE

  14. D-V Reengineering Need • Implement a modern solution for system that is 30+ years old, resides on mainframe platform, and is increasingly fragile, and therefore, difficult to maintain. • During the time of this project and immediately after cancellation of the project there were several parallel, but much smaller efforts undertaken by TRD to upgrade MVD systems. Some of these projects, like C-MOD, became necessary because of the project cancellation.

  15. D-V Reengineering Project History • Driver-Vehicle Reengineering project commenced 07/23/2010. • A limited amount of deliverables were made by spring of 2011. • The project was cancelled 05/16/2011.

  16. D-V Reengineering Certifications

  17. D-V Reengineering Expenditures EXPENDITURES (000’s)

  18. Delivered

  19. Lessons Learned • The time and expense to have an independent expert analyze the technical architecture of the offered solution, can save the Department from being ‘oversold’ on the degree of COTS\MOTS and necessary modification. • Seek a true COTS package for the solution, and ensure that a selected vendor has a track record of production implementations. • Ensure that systems sold as COTS are truly COTS and not mis-labeled MOTS. • Keep the language regarding tracking the number of times solution elements are submitted for the Department’s approval in the next contract. This language enabled the Department to understand when the project was excessively diverging from schedule, and immediate intervention was required up to and including cancellation of the contract. • Add a Business and Technical architect to the external project team. • Consider placing some language in the next contract for the Department to obtain reimbursement for schedule or quality deterioration. • Ensure that adequate business and IT resources are available for the duration of the project.

  20. Questions

More Related