The US State Government was struggling to provide quick services to the proliferating needs of US citizens at various state-level DMV offices. The DMV needed more resources, due to ever-increasing vehicles purchased and growing number of drivers in the states. Manual operations, on the other hand could contribute to more errors which in turn increases the work load. The existing Mainframe application was not able to cope up with the problems and Government agencies faced pressure to provide a long term and effective solution to the US citizens.
In the US, a state-level Government Agency, i.e., the DMV or the Department of Motor Vehicles administers vehicle registration and driver licensing. The driver's licenses are often the de facto identification card for many purposes, and DMV of various states are responsible verification of the identity. DMVs also provide identification number for vehicles, which is crucial to prevent automobile-related crimes. The core requirements of our clients were to automate, upscale and digitally manage all driver licenses, financials, financial responsibility, hearings, inventory, dealers, and inspection Stations. This will transform their services and allow smooth and robust provisioning for better compliance checks, performance measures, customer service, and fraud prevention mechanisms.
The State Government Officers desired that the DMV application should be carried out in two well-defined phases. The system must co-exist with some crucial parts of the out-going existing application. The phased implementation also required that the existing Mainframe application to be in synchronization with new system on some critical entities during the implementation of Phase 2 till the entire system is commissioned after completion of Phase 3. Every state has over 50 Access databases which supported complementary functionality to the Existing Mainframe based system. The new system needed to encompass the functionality provided by these systems.
The CoMET or Comprehensive Motor Enabling technology is used to modernize and automate the functions and processes of the DMV, mainly registering vehicles, issuing Driving Licenses, Driver Compliance, Driver Safety, Driver Testing, Driver/Client Management, Vehicle Management, Vehicle Safety Management, Fleet Management, Inventory Management, Financial Management, and advanced Reporting and Analytics. Its implementation is a transaction-based solution with work flow steps, where in, the customers and users provide the information to fulfill the requirement of the system. Transaction is based on a sequence of events that are built around the business process required to accommodate the activities of a DMV customer or an external agency to achieve the required DMV based results. We carried out state wise implementation across various US States including State of Vermont, State of Rhode Island, State of Idaho, State of Michigan, and State of Texas.
Our strategy of this architecture was designed to meet the architectural objectives, goals and the constraints outlined above. Our strategies are as follows:
It is done to provide configurable and plug-in software components. The key areas of the architecture that will benefit from this approach are:
Through the use of Windows Workflow Foundation (WWF), business processes can be client-defined and easily updated and deployed with minimal software development required.
With the use of Microsoft Communication Foundation (WCF), the transport layer between the client and the business services can be defined and stored in a configurable file format. The WCF provides DMV the capability to configure for any transport mechanism requirement without major impacts to the software application layers.
It provides a workflow configurable solution. The extension of this framework allows the functional team to define the DMV workflow requirements and through configuration tools implement the changes to the DMV with minimal or no development requirements.
It will integrate with the business model and extend validations, exceptions, and change the business model behavior.
The primary approach is to use the Integration Capabilities of SQL server. SQL server integration services are used for Integration purposes. The integration needs of the DMV project for Vermont/Rhode Island do not justify an elaborate Enterprise Architecture Integration due to cost and time considerations. The DMV data was either pushed or pulled via ftp. So the best approach was a batch process via ftp/Integration Services to expeditiously process the information into the DMV. The new version of SQL Server 2005 provided improved features for Integration Services, Scheduling, and .NET integration. Additionally, after studying all the interfaces as well as the needs of data synchronization, SL service brokers were also evaluated. The decision is taken after completion of the requirements analysis phase.
This framework allows the use of new and updated features such as security, caching, data providers, SQL Server integration, etc. This framework, along with the new published application, blocked by Microsoft shortens the development lifecycle and provides more design extensibilities.
This application block involves the use of Caching, Cryptography, Data Access, Exception Handling, Logging, & Security. These off the shelf frameworks provide the foundation for the development teams and architects to provide a more robust framework for DMV.
new features provided by SQL Server 2005 and the .NET 2.0 Framework. One of these features is the use of event patterns with caching.
The DMV follows an n-tier architecture approach using the latest design & development tools and frameworks. In addition to the tool sets, parallel development efforts focus on the following:
These designs are the foundation to the DMV and consist of the workflow, UI navigation, UI composition, business rules, and etc. frameworks.
The prototype follows the direction of the customers’ requirements and the changes as directed by the Seasia Consulting Business Analyst.
This approach also provides the business domain logical relationships and collaborations.
During the iteration process of the DMV, the main goal of the project process is to maintain data integrity on the Mainframe. This data migration effort needs to maintain integrity until the final deployment of the DMV and there is no longer a need for data from the existing mainframe application. SQL service Broker is evaluated to use for data synchronization between legacy and the new Application.
The Software Development Lifecycle (SDLC) processes of Seasia Consulting are followed by all the disciplines of the DMV. We have a deep knowledge base of DMV and great expertise in creating frameworks for DMV functionality in the past. DMV is used to harness the current design frameworks from previous DMV implementations. The following list of frameworks is refactored:
This is the Center Stage solution and the first phase of the POS deployment is the standalone deployment. The final deployment is a seamless integration between the DMV and POS of the Center Stages product.
|Windows 2003 Active Directory Server||2||
Seasia, a CMMi Level 5 Certified Company, offers a bouquet of services to automate, digitize, and modernize your business network. An authorized partner of Hewlett Packard (HP), and Google, we are a global leader in providing next-gen consulting and digital services for business transformation. Our strong clientele across 50+ countries leverage our wide range of customized services to suit their business needs. At Seasia, we are committed to delivering high-quality solutions to build a long-lasting alliance. Our clients trust us as we empower them by: