Download
1 / 11
110 likes | 275 Views
Dragonfly Initiation and Planning Request. August 28, 2013. Agenda. Project Purpose Business Objectives Technical Objectives Budget Schedule Scope Lessons Learned Incorporated into this project Questions. Current Status. RFP # 30-333-12-12463 is in progress. Purpose.
E N D
Dragonfly Initiation and Planning Request August 28, 2013
Agenda • Project Purpose • Business Objectives • Technical Objectives • Budget • Schedule • Scope • Lessons Learned Incorporated into this project • Questions
Current Status • RFP# 30-333-12-12463is in progress.
Purpose • Replace the existing, fragile MVD system for Driver and Vehicle transactions, while meeting all 759 of the requirements of RFP #30-333-12-12463.
Business Objectives • Replace the antiquated, fragile MVD system with a robust, reliable system via an on-time, on-budget project delivery. • Decrease the average time per transaction in the Field Office by 20%. • Expand electronic government (self-serve model). • Lead customers to lower-cost service channels. • Balance customer facing with centralized processing services. • Expedite paperless processing. • Simplify business rules • Provide a solution capable of supporting the Visionary Business Model developed by MVD and ITD in 2012. • Provide all the requirements previously developed for RFP #30-333-00-12463 • Provide higher levels of MVD service with the ability to meet new, evolving requirements and operational needs.
Technical Objectives • Provide a solution capable of immediately, or with only slight modification, support the Visionary Business Model developed by MVD and ITD in 2012. • Provide all the technical requirements included in the previous RFP #30-333-00-12463. • Procure a more modular solution with current technologies that can be managed, updated, and replaced without requiring wholesale replacement. • Adhere to national standards for data exchange, security, and interfaces. • Provide open-systems-based architecture (SOA compliant) that is more reliable, flexible, and maintainable. • Manage the risks of implementing and operating the new motor vehicle environment while improving system and data integrity. • Develop and manage a program that enables disaster recovery operations and improves on return-to-service time lines. • Improve the quality and accessibility of information for users with toolset standards, such as Structured Query Language (SQL) and Open Database Connectivity (ODBC), and do so without the involvement of operators or specialists. • Where required in the RFP, fully integrate existing capital and hardware infrastructure that currently exists.
Scope • All mandatory and optional requirements from RFP# 30-333-00-12463 • All driver transactions for MVD Field Offices and Private Retail Agents. • All vehicle transactions for MVD Field Offices and Private Retail Agents. • Customer and Account entities and objects to handle office, public, and third party transaction sources. • All financials including POS and SHARE interfaces. • Set of web services using the same business rules as those for the offices, and exposed for use by third party firms providing TRD-certified User Interfaces for MVD services and data sales.
Incorporation of ‘Lessons Learned’ • Independent technical expert was engaged to perform a technical architecture analysis previous during the clarification phase. This assessment was then incorporated into the contract for the Vendor and the contract for the external PM Team. • TRD strongly prefers a COTS or COT-CRM solution in order to avoid the overselling of a MOTS system as a COTS system. • Contract boilerplate is in progress, but will contain similar language to the ‘three submissions’ language that was so useful previously. • Business and technical architect functions and experience has been added to the specifications for the external PM team. • Additional language is being considered to the boilerplate for schedule and quality performance penalites.
