REQUEST FOR INFORMATION # 2014-08
The Virginia Department of Motor Vehicles 2300 West Broad Street Richmond, VA 23220
REQUEST FOR INFORMATION (RFI) 2014-08 for: Mainframe Transformation Issue Date:
May 30, 2014
Due Date/Time:
July 15, 2014, 3:00 p.m. EST
Response Delivery Method:
E-mail attachment sent to Single Point of Contact
Single Point of Contact:
Betsy Bratton, Lead Contract Specialist Contracts and Procurement Department Phone: 804-367-0544
E-mail Address: Line
[email protected] with “PMT” as Subject
NOTE: This public body does not discriminate against faith-based organizations in accordance with the Code of Virginia, §2.2-4343.1 or against a Supplier because of race, religion, color, sex, national origin, age, disability, or any other basis prohibited by state law relating to discrimination in employment. DMV is committed to increasing procurement opportunities for small, women-owned, and minority-owned (SWaM) businesses, strengthening the Commonwealth’s overall economic growth through the development of its IT suppliers.
RFI
DEPARTMENT OF MOTOR VEHICLES
PAGE 1 OF 16
REQUEST FOR INFORMATION # 2014-08
Table of Contents 1.
Introduction ..................................................................................................................................................... 3 A.
Overview ............................................................................................................................................................ 3
B.
Agency Background............................................................................................................................................ 3
C.
Technology Background ..................................................................................................................................... 4
D.
Purpose .............................................................................................................................................................. 5
E.
Constraints ......................................................................................................................................................... 6
F.
Considerations .................................................................................................................................................... 7
2.
QUESTIONS ...................................................................................................................................................... 8 A.
Overview of the Solution .................................................................................................................................... 8
B.
Overview of the Value of the Solution ................................................................................................................ 8
C.
Assessment ......................................................................................................................................................... 8
D.
Approach for the Solution .................................................................................................................................. 9
E.
Software AG conversion ..................................................................................................................................... 9
F.
interfaces.......................................................................................................................................................... 10
G.
Batch Processing .............................................................................................................................................. 11
H.
Development Needs ......................................................................................................................................... 12
I.
Database Conversion ....................................................................................................................................... 12
J.
Implementation................................................................................................................................................ 13
K.
Costs ................................................................................................................................................................. 14
L.
Experience ........................................................................................................................................................ 14
M.
Challenges ........................................................................................................................................................ 15
3.
Contact Information ....................................................................................................................................... 16
Appendix 1 – Natural Code Breakdown ........................................................................ i Appendix 2 – Interfaces ............................................................................................... ii Appendix 3 – DMV Current Environment Summary .................................................... iii Appendix 4 – Glossary of Terms ................................................................................. iv
RFI
DEPARTMENT OF MOTOR VEHICLES
PAGE 2 OF 16
REQUEST FOR INFORMATION # 2014-08
1. Introduction A.
OVERVIEW The intent of this Request for Information (RFI) is solely to gather information; it is not a formal procurement. Information received may be used for informational and planning purposes. Nothing in this RFI should be construed as intent, commitment or promise to solicit or procure a solution. Responding to the RFI is not a pre-requisite to submitting a proposal for any subsequent procurement, should a formal solicitation be issued. Respondents should not provide any confidential or proprietary information. Information submitted in response to this RFI will become the property of the Commonwealth of Virginia. The Department of Motor Vehicles and the Commonwealth of Virginia will not pay for any information herein requested and provided by Supplier. The Department of Motor Vehicles and the Commonwealth of Virginia will not be liable for any costs incurred by the Supplier related to this RFI. All such costs are Supplier’s sole responsibility. On behalf of the Commonwealth of Virginia, the Department of Motor Vehicles is seeking information to discover market availability to guide its decision making regarding methods and tools for transforming DMV’s legacy mainframe platform to n-tier architecture including the conversion from Adabas to Oracle 11g and legacy code and services.
B.
AGENCY BACKGROUND The Department of Motor Vehicles (DMV) is an agency of the Commonwealth of Virginia. Under the direction of the Secretary of Transportation, DMV administers motor vehicle and tax related laws for the continued benefit of all citizens of the Commonwealth of Virginia. Specifically, DMV administers motor vehicle titling and licensing laws, driver licensing laws, transportation safety laws, tax laws, and other motor vehicle-related laws and regulations as directed by the Code of Virginia and Federal laws. DMV employs approximately 2,000 full and part-time employees to collect transportation revenues, issue numerous types of credentials, and process tax filings for fuels tax, rental tax, and the International Fuels Tax for motor carriers. DMV employees provide services through a network of locations dispersed throughout the state including a centralized Headquarters office, 75 Customer Service Centers (CSCs), 5 Mobile CSCs, and 13 Motor Carrier Service Centers/Weigh Stations (MCSCs). In addition, some services are provided at more than 57 DMV Select offices located throughout the state, run by local governments and private entities under contract with DMV to provide secure, select DMV transactions. DMV Selects are a service alternative to visiting a full-service DMV Customer Service Center and the number may expand. DMV is adding to its fleet of mobile offices, as well.
RFI
DEPARTMENT OF MOTOR VEHICLES
PAGE 3 OF 16
REQUEST FOR INFORMATION # 2014-08
DMV provides a multitude of services to a variety of clients, including Virginia residents, transportation entities, courts, law enforcement agencies, government agencies, motor carriers, grant recipients, motor vehicle dealers, and insurance companies. The primary services provided by DMV involve: •
•
•
Credentialing – This includes the provision of driver testing and licensing, vehicle titling and registration, credentialing of commercial motor carriers, and regulatory licensing functions such as fuel distributors, rental car companies, dealers, commercial driver training schools, driver improvement clinics, and 3rd party testers. Tax processing – This includes support for the calculation, collection, accounting, and reporting statistics for all tax filings (including IFTA, tax on fuel, and tax on motor vehicle rentals) as well as support for an external/taxpayer audit function. Information Provisioning – This includes appropriately disseminating information about 5.3 million drivers and more than 7 million vehicles to external entities. Securing this information and ensuring its integrity are among the most important functions of this agency.
DMV annually issues over 1.7 million driver’s licenses, registers almost 6.4 million vehicles, weighs approximately 17.5 million trucks, and collects over $2.2 billion in revenue. Due to the nature of DMV business processes, DMV requires substantial use of automated systems to support and perform its functions in an efficient manner. The agency needs to incorporate into its operation those technological developments and automated solutions that will enhance the delivery of services to DMV's various transportation clients. C.
TECHNOLOGY BACKGROUND VITA’s IBM mainframe model Z196 running Z/OS is used to execute DMV’s applications. DMV’s application programs are built using the Software AG products ADABAS, Natural, Broker, and COMPLETE. CSS is DMV’s primary information system that is used for storing information on customers, their addresses, their driver history, vehicle registration and titling information as major data categories. The mainframe system is the principle repository of DMV data and business logic. It is accessed directly by employees physically located throughout the state at HQ in Richmond, 75 Customer Service Centers, 3 Call Centers, 5 Mobile Customer Service Units, on-site service employees and weigh stations. Additionally, local government agencies, other state agencies and private companies interface in real-time or batch with the DMV mainframe. The employee access is facilitated through web services and direct 3270 connection to the mainframe via the MPLS network. DMV has a high daily transaction volume; approximately 138,000 customer transactions are performed daily
RFI
DEPARTMENT OF MOTOR VEHICLES
PAGE 4 OF 16
REQUEST FOR INFORMATION # 2014-08
through the various channels. Refer to Appendix A for the mainframe application overview. The DMV Mainframe system is accessed from the Customer Service Centers via a private Frame-Relay network, and from the DMV HQ location via a private DS3 serial connection. Between the hours of 8am-5pm Mon-Fri and 8am-12pm on Saturday, DMV’s Customer Service application supports approximately 1,000 concurrent users performing an average of 70,000 transactions each day. The Virginia Information Technologies Agency (VITA) provides all infrastructure services for in-scope executive level agencies. The Commonwealth Enterprise Solutions Center (CESC) is the Commonwealth of Virginia data center for use to those in-scope agencies. The Virginia Department of Motor Vehicles is an in-scope agency and relies on the VITA provided services. There are a number of sourcing options that exist that allow for public-private partnerships for delivery of business services. Please read more at http://www.vita.virginia.gov/about/. DMV’s current EAI is a service-based architecture utilizing a variety of techniques. The preferred mechanism to interact to DMV’s EAI is via web services. DMV provides high-availability services to the mainframe, databases, and a variety of other DMV systems. Presently DMV utilizes Windows based servers as Presentation, Business Logic, and Data Access servers. DMV Servers are secured based on current industry standards provided by the NSA, SANS Institute, etc, as well as those published by VITA. Servers are designed with standardization across all machines. DMV utilizes both physical and virtual servers (VMWare ESX Server) based on need and activity. DMV’s present enterprise database platform consists of a high-availability Oracle 11g RAC 2 node cluster and a SQL Server failover clusters both utilizing fiber channel storage. The DMV EAI is designed with security and standardization as the core set of principles required to provide maximum uptime to applications and customers. DMV’s present development environment for enterprise applications is based on the Microsoft .NET development platform (VB.NET and C#). D.
RFI
PURPOSE The purpose of this RFI is to assist DMV with project approach decisions and to understand the outcome of the approach: • Rehost mainframe application and data first and then perform code transformation to .NET • Simultaneously rehost mainframe application and data and perform code transformation to .NET DEPARTMENT OF MOTOR VEHICLES
PAGE 5 OF 16
REQUEST FOR INFORMATION # 2014-08
•
Combination of both approaches based upon assessment of applications.
The immediate goal of the mainframe transformation is to reduce or eliminate mainframe costs with a short-term effort that provides a fast ROI. The endstate vision for DMV systems is an application portfolio where all components run in the window’s server n-tier environment with the Oracle 11g database and a .Net codebase. The CSS system has evolved over 20 years starting with Driver, Vehicle and Financial processing. Newer applications include Dealer and Motor Carrier processing. The newer applications might be candidates for immediate code transformation. The older applications contain functionality no longer needed and should be re-written by DMV Staff after they have been rehosted. DMV needs to break its dependence on Natural and Adabas. These are scarce resources in the marketplace and the agency has an aging workforce. In order for DMV to retire Adabas or the mainframe, all system components will need to be on the new platform. These include: • Application code (Predominately Natural with a very small subset of COBOL and Assembler) • Batch / JCL • Print sub-systems • Data warehouse E.
RFI
CONSTRAINTS When responding to the questions in Section 2, please consider the following: • Upgrade DMV’s technology and computing platform without materially impacting business; there can be no prolonged code freeze • ADABAS data must be migrated to Oracle using a solution that will generate the RDMS database • The migration of the Natural/COBOL/Assembler codebase must continue to support on-line and batch processes. DMV is primarily reliant on Natural with a minimal amount of COBOL and Assembler • The migration of the Natural/COBOL/Assembler codebase must continue to support all interfaces, batch and online print. • Migration solution must perform at similar standards to current processing < 3 sec response time • Rehost Mainframe Natural applications, Batch Processing, and Adabas data in Oracle / .Net environment • Have a Common UI for all users (Change all 3270 screen emulation used by– external and Headquarters users) • Ensure Business Continuity throughout the transformation process • Adopt a Configuration Management Process • Still maintain a separate Development, Test, Training, and Production environment DEPARTMENT OF MOTOR VEHICLES
PAGE 6 OF 16
REQUEST FOR INFORMATION # 2014-08
• • F.
RFI
Data Dictionary Ability to Scan the Code Repository
CONSIDERATIONS • Cleanup code (e.g. Date conversion routines, DMVS1 – Refer to Appendix 3.C) • 22 Adabas files have 215 date fields defined as P7/N7 (Cyymmdd). A large number of date conversion sub programs are called to convert the date for viewing/reporting in readable format and then back to Database Storage Format if updating. • Ensure Governance and Standardization over software development, Testing, Implementation • Ensure Quick Recoverability – Backup / Restore / Upgrades • Determine best approach: Rehost then Reengineer or Vice Versa. • Ensure all current integrations / interfaces and batch processing still function in new environment • Simple to use Development and testing tools (Program and Map Editors, Debugging • Library / Separate Program repository for Programmer adhocs against Development/test/Production • Cross Reference tool – allows programmers to quickly identify all related code/Modules that references the Database file, Subprogram the programmer is modifying • Transaction Error Processing – Stores the Transaction Error information • Batch Datasets – ability to View / Update • Vendor’s product and process is licensable to allow DMV staff to use for other systems if desired • Leverage DMV Staff’s Natural expertise and skill sets
DEPARTMENT OF MOTOR VEHICLES
PAGE 7 OF 16
REQUEST FOR INFORMATION # 2014-08
2. QUESTIONS A. OVERVIEW OF THE SOLUTION Based on your understanding of the information provided in this Request For Information, describe your overall approach to Mainframe Modernization of DMV’s Software AG Natural / IBM TSO Shop with heavy use of Broker for Transaction processing and heavy use of Batch IBM/TSO. Submit a detailed statement reflecting your perception of the DMV Mainframe Transformation project and how your proposed products, services, and/or solutions could potentially meet the needs of the Virginia Department of Motor Vehicles. Please provide to the VaDMV a clear understanding of your product(s) and service(s) and how they may fit into our goals. For example, if you are defining a whole, turnkey solution then please provide a clear and concise architectural view of your solution. Provide a summary of the methodology that you would use to implement such a mainframe legacy data migration project. Specify limitations and constraints of the methodology. If you plan to inform us about products that may lend themselves as components of our effort, then please provide an architectural view of our future system, in your concept, and depict how your products would fit into that solution. You should use this section to “orient” the VaDMV as to how your products and services contribute to our end-state vision. Enter your response here, enlarging the box as needed. Reference any attachments.
B. OVERVIEW OF THE VALUE OF THE SOLUTION Describe the value your products, services, and/or solutions will deliver to VaDMV. For example, what is your differentiation in the market as it relates to a transformation / rehosting goal? Enter your response here, enlarging the box as needed. Reference any attachments.
C. ASSESSMENT Describe your Mainframe Modernization Assessment / Discovery process. Explain how the results are used to identify levels of work and which applications would be suited for transformation and which for rehosting. Enter your response here, enlarging the box as needed. Reference any attachments.
RFI
DEPARTMENT OF MOTOR VEHICLES
PAGE 8 OF 16
REQUEST FOR INFORMATION # 2014-08
D. APPROACH FOR THE SOLUTION Does your approach transform the Natural Code and Rehost or does it rehost the Natural code without changing the Natural Code? Describe how your approach will work if functions are implemented through a Phased Approach. Discuss your proposed approach to Database Synchronization if necessary. Provide a summary of any existing industry best practices to implement a mainframe legacy data migration project. If DMV chose a combined approach (Rehost some modules, Transform others), explain how these common routine used by both would be shared. Enter your response here, enlarging the box as needed. Reference any attachments.
E. SOFTWARE AG CONVERSION Describe how your approach handles converting/executing the following Software AG’s Natural Data and Program types: Detail
Answer
LDA’s, PDA’s, AIV’s, GDA’s, Programs, Subprograms, External Subroutings, Copycode, Maps Describe what mapping is available for programmer reference of original Natural object to rehosted /Converted object. (i.e. ADDCUSPA in Natural is ________ module(s) in .net) How much code cleanup would be required in the Natural Environment to prepare the code for conversion / Rehosting? Does your solution provide a standard API for access to migrated Adabas/Natural business logic If using a Natural Emulator – in what language is the Object code built?
RFI
DEPARTMENT OF MOTOR VEHICLES
PAGE 9 OF 16
REQUEST FOR INFORMATION # 2014-08
F. INTERFACES Describe how your approach will replace the following Interfaces and the level of reengineering that would be required: Detail
Answer
Our existing technical architecture relies heavily on the SAG EntireX Broker middleware product for providing real-time integration to our legacy mainframe based Adabas/Natural application. See appendix for inventory of Broker Servers. What would replace this middleware integration software and what changes would be required of client applications? SAG’s Online Complete / 3270 screen emulation. How would your approach limit the development efforts needed for those users still accessing the system via the Complete/3270 Screen emulation? CICS / Cobol: Aamvanet (CDLIS, NDR, SSN Verification, Incoming Requests from other States) NICB, NADA, NMVTIS – refer to Appendix 3 section II. Does your solution support xml based web service integration? Specify how your solution can be extended to web-based applications.
RFI
DEPARTMENT OF MOTOR VEHICLES
PAGE 10 OF 16
REQUEST FOR INFORMATION # 2014-08
G. BATCH PROCESSING Describe your approach to Batch Processing? Detail
Answer
JCL Conversion – Describe how your approach would rehost and execute batch jobs to include: Sorts, Dataset Creation steps Describe what mapping is available for programmer reference of original JCL Member to Script Member object. (i.e. JCL Member DMVxx100 (3 Steps) is ________ module(s) in .net) Batch CYCLE Execution, Monitor and Control (DMV uses Control M (Appendix 3 section V) and an In-House Submitter to Automatically submit jobs within a Batch Cycle) Describe how your approach will convert / submit IBM JCL Batch Job(s) and manage the batch cycles Describe the Batch Scheduler that would be used Production Control manually submits user requested jobs periodically during the day. Describe how this will be handled. Batch Output – DMV has various types of printed output from the Execution of Batch jobs. Describe how these will be handled with your solution. Printed output. Control D – (Appendix 3 section V) output maintained for 1 year for all jobs. (2 separate repositories =1 for Production and the other for Test Batch cycles) Special Forms – Identification of Special forms is indicated within the JCL. How will this be handled to ensure the operators are informed when to load special forms prior to printing? Batch Datasets – DMV currently uses GDG’s and SMS to retain previous versions of a dataset for possible recovery and re-execution of the JOB. (Refer to Appendix 3 section V) Programmers will need to be able to also View / Update / Copy datasets. Describe how your approach will handle this. Describe your solution to DMV’s Batch Interfaces: (Appendix 3 section V.C) EDI – Electronic Mailboxes FTP / Connect-Direct Bulk information processing via Broker Moveit (Automatic File Transfer System) RFI
DEPARTMENT OF MOTOR VEHICLES
PAGE 11 OF 16
REQUEST FOR INFORMATION # 2014-08
H. DEVELOPMENT NEEDS Programming / Testing Environment. Describe how your solution will address development needs of the DMV’s programming groups. Detail
Answer
Change Management – Programs / Batch Jobs Utilities for Programmers / Testers Development tools Debugging tools Cross Reference tools – to find modules that share similar functions that should also be modified. Scan tools to scan the Production Module environment Testing tools to develop and execute test cases, ability to copy / Mask customer information from production to Development, Training, Test Separation of Production Source code from Programmer developed adhocs Establishment and maintenance of Data Dictionary Production problem Error trapping and email notifications
I. DATABASE CONVERSION Describe how your solution will address database conversion from Adabas to Oracle 11g. Detail
Answer
Describe the process to convert Inverted list Adabas Files to a Relational Oracle schema. Describe the process to convert Adabas data types to Oracle data types. e.g. MU/PEs How would your solution handle complex data migration from mainframe Adabas (EBCDIC) to Oracle (ASCII)? Describe any pre-conversion database “clean-up” that is necessary. Specify data types or characteristics that should be modified prior to moving to Oracle.
RFI
DEPARTMENT OF MOTOR VEHICLES
PAGE 12 OF 16
REQUEST FOR INFORMATION # 2014-08
J. IMPLEMENTATION Describe what will be required to implement the proposed products, services, and/or solutions. Detail
Answer
Necessary hardware and software licenses, including quantities Any solution would need to handle growth of our organization. Please describe how your solution handles scalability. Horizontal or vertical or both? Estimated time to implement, including an estimate of calendar time, in months, required to complete the implementation If the solution chosen in Rehosting the Natural Code, what is the process to convert to C# and what additional add-on products are required? Indicate the estimated number of months required for analysis, development (including customization and integration), testing, training, installation, and other transition activities. What skills (rudimentary and specialized, if any) are required to implement the solution? What general documentation and training would be needed by technical staff? If you have provided a methodology or solution, specify with respect to your solution. What advice would you give to organizations planning for transformation, to ensure the new solution is successful? Does any part of your solution require off-shore resources? If yes, to what extent and in what manner. Describe how your solution addresses testing, both functional and conversion? Please provide detail as to the number and skill set for testers both provided through your organization and available at DMV.
RFI
DEPARTMENT OF MOTOR VEHICLES
PAGE 13 OF 16
REQUEST FOR INFORMATION # 2014-08
K. COSTS Describe the approximate costs associated with your solution Detail
Answer
Hardware costs Software costs Integration (Middleware) costs What are the ongoing maintenance needs associated with your solution Costs for services including Project Management, Testing, Development, Installation/Configuration and Travel
L. EXPERIENCE Describe your experience. Detail
Answer
Please describe your experience with projects of similar size, scope and industry focus. Be specific in your response about the scope of these project: Lines of Code, transaction volumes, database records et al Describe the skill sets and competencies of your available resources How reliable is your solution? Provide at least three project summaries and describe the client's business objectives, the scope of work performed and the results delivered Provide a list of three client references that use your product(s) and services to perform a similar business function. Also, please include the contact person’s name and phone number so we may contact them Do your customers include state governments or other governmental customers? If yes, please describe any issues, challenges or characteristics unique to governmental transformation solutions.
RFI
DEPARTMENT OF MOTOR VEHICLES
Use an attachment for complete summaries
PAGE 14 OF 16
REQUEST FOR INFORMATION # 2014-08
M.
CHALLENGES
Transformation Issues or Challenges
RFI
DEPARTMENT OF MOTOR VEHICLES
Likelihood that the Solution will meet desired outcomes (Rate each item as “High” “Medium” or “Low” likelihood, and add any comments you wish regarding how the solution could meet DMV’s needs)
PAGE 15 OF 16
REQUEST FOR INFORMATION # 2014-08
3. Contact Information Please provide your company’s contact information. Enter your response here, enlarging Contact Information the box as needed Company Name Company Mailing Address
Company Website Address Name of Contact Person Contact Person E-mail Address Contact Person Telephone # Is your company interested in being notified when a solicitation (Request for Proposals) is issued? (Reminder: Participation in the RFI process is not a requirement to submit a response to the RFP). Solicitation Notification
Check only one
Yes, please notify me of any subsequent DMV Request for Proposal (RFP) on this topic No, do not notify me of any subsequent DMV Request for Proposal (RFP) on this topic Thank you for responding to this Request for Information.
RFI
DEPARTMENT OF MOTOR VEHICLES
PAGE 16 OF 16
High level Usage Breakdown of CSS PRODUCTION Natural Code
Feb 28, 2014
(Does not include database 100, Audit or Privacy Warehouses)
Copycust/Mask 130 programs 14,600 lines
Online Natural Code 6,480 programs 2,430,000 Lines (PGM, SubPgm, copycode, Subroutine, GDA, PDA, LDA) ** No Helproutines, Maps **
Create and Sub JCLthrough Online Program
Submit Batch Job Will need reengineering for Dynamic Reports (CORR) and Emails 145 programs 65,600 lines
Email or Report to Control D
SSG Utilities 203 programs 81,800 lines
Table Programs 2,190 programs 500,000 lines
Online Integrations (Communications to functions outside the actual Natural Pgm needed to complete the online transaction) Accessed via a ‘CALL’, Bridged Adabas file (54, 98, 164), or Complete (VCIN using APXRTR)
VCIN /NCIC APXRTR, APXNCIC
** # PGMS / LINES PART OF TOTAL ABOVE ** Will need Reengineering 830 Programs – 673,500
PDFENCOD Bar Code – called by 12 programs – some online
CICS
VINA
- called through broker or linked to adabas file
- called through Vinanqna
Finalist Through file 164
NMVTIS – through file 54 and Broker
NADA through broker
AAMVANET through file 98
Broker
Just the specific APC,FPC,PGMS CALLING BROKER Some also Many integrations including – Secure test, Go through Intranet Secure Apps, CICS Extranet Secure Apps CAS, DLCI, DEQ, MySelect, Select, Internet, Ins Mon, LVR, IBR, Driver Alert, NADA, NMVTIS, Medical Review, Overweight Citation, Plate order tracking, QFLOW, RPS, SEX Offender, TEMP TAG, TREDS. VRWS, Hauling Permits, Dashboards, NICB Mech Storage Lien through UCR, VEH Demolish, NICB, Broker WEBCAT, WEIGH STATION,
DMVS1 Called by 365 programs
LexMark Print ?? Reengineer ?? Called by 219 Pgms * Minor Reengineering * ** Might be gone when all are on same UI – using the MySelect Method of Printing
YOUTHFUL DRIVER
ALL BATCH JOBS – to be reengineered off of Control D as well 2,910 programs, 1,044,000 lines
TOTALS: (Does not include Maps, Helproutines) FYI DEFINE PRINTER CALLNAT to USRxxx Sag Routines 266 Online Programs
Online Table Copycust SSG UTILITIES Online Batch submitters Batch
6,480 programs - 2,430,000 Lines 2,190 programs - 500,000 lines 130 programs 14,600 lines 203 programs 81,800 lines 145 programs 65,600 lines 2,910 programs - 1,044,000 lines
Appendix i
DMV Interface Inventory Directionality Broker, Outgoing from Moveit, FTP, Main Connect Incoming from Direct, etx. Main bidirectional
#
Data Category
Interface Name / Batch or Organization or Online Application
Description
1
Audit
BATCH Dashboard Info
Transaction Information extracted from Mainframe and loaded into Datawarehouse in Oracle (RDM)
FTP
Outgoing
2
Credit Card
BATCH Elavon
Batch Report to Evalon - Charge Report
FTP
Outgoing
3
Customer
DMV Connect 47 facilities and growing
Moveit
Incoming
Report
Outgoing
Tape
Dataset
tape
Bidirectional
BATCH
Department of Corrections
Cust w/ failed vision test results Parm U report = Customers w/suspended driv. priv.due to unaccepted vision rpt. Parm F report = Cust w/ failed vision test results Dept of Blind and BATCH Yearly – the reporting period is the prior Vision Impaired calendar year Run from DB197 per run documentation
4
Customer
5
Customer
BATCH Dept of Defense
6 7 8
Customer
BATCH Dept of Health
Listing of Youthful Individuals * Not run recently * Cancer registry
Customer
BATCH Dept of Health
Death Tape
Moveit
Incoming
Customer
Organ donor
FTP
Outgoing
9
Customer
Match interface
DATASET
Bidirectional
10
Customer
BATCH Dept of Health Dept of Social BATCH Services Game and BATCH Fisheries
Transcripts
DATASET
Bidirectional
11
Customer
BATCH Jury Selection
Customer Information - with Valid License
FTP
Outgoing
12
Customer
BATCH Navy Recruiting
Customer Information * not executed recently *
Tape
Dataset
13
Customer
BATCH Personix
Handicap Placard
Connect/Dir
Outgoing
14
Customer
BATCH Selective Service Customer Information
FTP
Outgoing
15
Customer
BATCH
Customer Information - with Valid License
FTP
Outgoing
16
Customer
State Board of Elections BATCH USPS
updates with Zip Codes
FTP
17
Customer
BATCH USPS
Certified Mail
FTP
Incoming Incoming Outgoing
18
BATCH Finalist
Address Validation- EXECUTES Vendor Provided Application
Batch database
Bidirectional
19
CustomerADX CustomerBulk Data
Youthful Driver - Bulk data exchange
BROKER
Bidirectional
20
CustomerDriver
CAIS - Federal BATCH Courts Central Conviction Processing Violations Bureau
Moveit
Incoming
21
CustomerDriver
BATCH
Moveit
Bidirectional
BATCH
Insurance Companies
CAIS Supreme Court of Va
Conviction Processing
Appendix 2 - ii.1
DMV Interface Inventory
22
CustomerDriver
BATCH CDL Drivers
23
CustomerDriver
BATCH
24
CustomerDriver
BATCH
25
CustomerDriver
BATCH
26
CustomerDriver
BATCH
27
CustomerDriver Ins CustomerDriver Ins
28
BATCH BATCH
Fairfax Juvenile Court
MEDICAL SUBMISSION any CDL holder in the state of va has access) individual CDL holders or company’s with multiple CDL driver employees can use Moveit to send us copies of the driver’s CDL Medical Certificate. Customer / License - Juvenile Customers to Fairfax to Schedule Court time for License
Fairfax school bus Receive Customer / name from Fairfax driver return Driver Status Transactions from online processing (OLTF) NDR DMV Transmits back in batch in inquiries received from other states. Transportation Safety Hazmat background check to TSA Administration Insurance (19 companies and growing) (Insurance Companies Processing) Insurance (Insurance verification) - reporting vehicle Companies changes
Moveit
Incoming
Tape exchange
Outgoing
Printed output
Bidirectional
FTP
Outgoing Incoming
SFTP via Unix Cron
Outgoing Incoming
Moveit
Bidirectional
Moveit
Bidirectional
Incoming
29
CustomerDriver Ins
Insurance BATCH Companies (700+) -
Auto Liability Information store to CSS
Some through Moveit, Rest using (EDI) (elect mailbox),
30
CustomerMultiAgency
BATCH EDM - VITA
Transmit Changes to Customer primary information for use with CAS
Connect/Dir
Outgoing
31
Financial
BATCH BANK
Automatic Clearing House - E-Checks
Connect/Dir
Outgoing
32
Financial
CARS BATCH (Collections and Reconcilation)
Financial Informaiton Copy Dept of Accounts Information TO CARS FILE
DATASET
Outgoing
33
Financial
BATCH
Reports
Outgoing
34
Financial
Fuels Use BATCH Tracking
Fuels use tax Historical Tracking system (Formally Motor fuels tracking system) jurisdiction refund data Store TO MC-FUTMASTER-155-A
TSO RECEIVE
Incoming
35 36 37
Financial
BATCH Locality - billing
E - Billing
Moveit
Outgoing
Financial
BATCH State Agency
Financial Information
DATASET
Outgoing
Financial
BATCH State Agency
Debt Setoff File
FTP
Incoming
38
Financial
BATCH State Agency
The external State Agency uses customer informaion Ascertain whether they qualify for a benefit. They Provide SSN - DMV returns DOB.
DATASET
Bidirectional
39 40
Financial
BATCH State Agency
Electronic DC
DATASET
Incominb
Financial FinancialMotor Carrier
BATCH State Agency
Load valid FEINS
FTP
Incoming
TSO RECEIVE
Incoming
41
BATCH
Collection Agencies
IFTA / IRP Provider
Customer / Financial Informaiton
FUELS TAX MONTHLY OUTSTANDING
Appendix 2 - ii.2
DMV Interface Inventory
42 43 44
FinancialMotor Carrier FinancialMotor Carrier FinancialMotor Carrier
45
MISC
46
Motor Carrier Motor Carrier Motor Carrier
47 48
BATCH
IFTA / IRP Provider
Fuels Tax
BATCH
IFTA / IRP Provider
BATCH
IFTA / IRP Provider
ADHOCS (83 BATCH customers, growing) IFTA / IRP BATCH Provider IFTA / IRP BATCH Provider IFTA / IRP BATCH Provider
TSO RECEIVE
Incoming
Extract payment from loc 191
Xerox's Moveit
Outgoing
load FTX-LICENSE-FILE-358-A
Xerox's Moveit
Incoming
Many types of Customer requesting various types of Information - One time or Recurring
Moveit
Outgoing
IFTA/IRP QUARTERLY TAX RETURN ANNUAL RENEWAL (IFTA/IRP) IRP RENEWAL
TSO RECEIVE TSO RECEIVE TSO RECEIVE
Incoming Incoming Incoming
49
Motor Carrier
VISTA /RS supports the International IFTA / IRP Registration Plan (IRP). IRP is a method of BATCH Provider registering fleets of vehicles that travel in two FTP / Moveit VISTA/RS system or more member jurisdictions. Project to web enable Registrations and Payments.
50
Motor Carrier
BATCH
51
Motor Carrier Motor Carrier
52
Other State Agency
SELECT ALL CARRIERS WITH NEW OR CHANGED AUTHORITIES EMAIL NEW/CHANGED AUTH TO WMATC
BATCH State Agency
SCC-DMV MC INTRASTATE INTERFACE
BATCH Weigh Stations
Suspended Carrier DMVFD350 - Certified Mail DMVRD010 - Combine Cust DMVDD010 - Crash Info DMVDD126 - Script images DMVAM108 - Kies DMVDD127 Orders/Notices DMVVD149 - Title Document (online Dealer) DMVVD127 - Abandonded Veh Letters
Email
Outgoing
Outgoing Incoming Outgoing
Moveit
Outgoing
ONBASE LOAD
53
Onbase
BATCH Onbase
54
User Access
BATCH
55
Vehicle
BATCH
56 57 58
Vehicle
Electronic Lien Processing BATCH State Agency
Remote Sense -Emissions Inspection
Expedite Base/MVS MoveIT
Vehicle
BATCH State Agency
Quarterly Customer / Vehicle Information
DATASET
Outgoing
Vehicle Vehicle T&R VehicleBulk Data
BATCH State Agency
Emissions study
Report
Outgoing
BATCH State Agency
Load Rental tax file
DATASET
Incoming
MoveIT
Outgoing
59 60
Localities, city, governments
Parking Ticket Moving to MoveIt for Data Exchange Parking Ticket, Mobile Home Certification Listing) Vehicle Lien Information
BATCH CSR (Cross Sell) Vehicle Information
Batch/Moveit
Bidirectional
Bidirectional Incoming
Appendix 2 - ii.3
DMV Interface Inventory
61
62
VehicleBulk Data
VehicleBulk Data
Vehicle Information
External Client picks up from EGOV Oracle system. (EGOV system retrieves from mf and moves flat files to Oracle)
Outgoing
Vehicle Information
External Client picks up from EGOV Oracle system. (EGOV system retrieves from mf and moves flat files to Oracle)
Outgoing
BATCH POLK
Vehicle Information
External Client picks up from EGOV Oracle system. (EGOV system retrieves from mf and moves flat files to Oracle)
Outgoing
BATCH VADA
Vehicle Information
MoveIT
Outgoing
Moveit
Incoming
Moveit
Outgoing
Moveit
Bidirectional
Moveit /Extranet
Incoming
DATASET
Outgoing
BATCH EXPERION
BATCH NRC
63
VehicleBulk Data
64
66
VehicleBulk Data VehicleLocality VehicleLocality
67
VehicleLocality
RAVE BATCH Registered Active Jurisdiction Control of their Deliquent Fines Veh Users
68
VehicleLocality
BATCH Treasurers
69
VehicleMVDB VehiclePlate Vehicle-Toll Road
65
70 71
BATCH Local Government Parking Tickets / VRWS Stops BATCH Local Government
BATCH Dealer board
Vehicle Reports (133 jurisdictions and growing)
VRWS Stops There is an Externet front end to place and remove VRW stops(via CSSvehiicle) Sales Persons Licenses, Certificates, Reg Cards, Financial Information
BATCH Parking Ticket
Lic Plate Look Ups (24 current users)
Moveit
Bidirectional
BATCH ERC/3M
data exchange - TOLL ROAD CUSTOMERS
Moveit
Bidirectional
Appendix 2 - ii.4
DMV Interface Inventory 72
Vehicle-Toll Road
73
Customer
BATCH VDOT - Fanuial BATCH
Dept of Social Services
data exchange - TOLL ROAD CUSTOMERS
FTPS Via VPN
Bidirectional
Parent Locator
DATASET
Outgoing
Customer
ONLINE Dept of Health
Birth Registry The interface is between mySelect and VDH BROKER/ via a web transaction but it also interfaces Web Service with host, setting up shell records and keeping track of revenue through fiscal..
75
Customer
Dept of Social ONLINE Services
CICS / AAMVANET Through File 98
Bidirectional
76
Customer
ONLINE EVVE
BROKER
Bidirectional
77
CustomerADX
ONLINE QAS
Web Service
Bidirectional
78
CustomerDriver
CDLIS (Commercial ONLINE Driver Licensing Information System)
Customer Information. Driver Information Same as NDR
CICS through file 98 Aamvanet
Bidirectional
79
CustomerDriver
ONLINE DLCI
Driver License Central Issue (CBN)
BROKER
Bidirectional
80
CustomerDriver
ONLINE DLCI (Images)
DMV-Photo (Oracle database CISS)
BROKER / Web Service
Bidirectional
ONLINE NDR
National Driver Registrar - National Database CICS of Driver License Information shared amoung Aamvanet States. DMV makes online inquiries against through file the register when issuing a new original Driver 98 License.
Bidirectional
ONLINE Treds
Accident Processing
BROKER
Bidirectional
Auto Liability verification
BROKER
Bidirectional
Customer Information - Customers using Commonwealth system - authentication against DMV information prior to account establishment.
BROKER
Bidirectional
Spider: a multi-agency web-based inquiry process that accesses various government agency information (including DMV) online to retrieve that agency’s information for assistance with customer eligibility.
BROKER
Bidirectional
ONLINE Table Propagator Propagate CSS Tables to Oracle
BROKER
Outgoing
ONLINE CVIEW
Motor Carrier Overload Payments
BROKER
Bidirectional
ONLINE Fuels Tax
Fuels Tax Refund Processing
BROKER
Bidirectional
74
81
CustomerDriver
82
CustomerDriver CustomerDriver Ins
83 84
CustomerMultiAgency
85
CustomerMultiAgency
86
Misc
87
Motor Carrier Motor Carrier
88
Insurance Monitoring CAS - VITA (Commonwealth ONLINE Authentication system) ONLINE
ONLINE
Virginia State Agency
SSN Verification Vital record certification/verification via Naphsis Address Verification System Address Connected to MySelect and not the Mainframe
Bidirectional
Appendix 2 - ii.5
DMV Interface Inventory
89
Motor Carrier
The Performance and Registration Information Systems Management (PRISM) program was IFTA / IRP developed to meet the challenge of reducing the Provider - PRISM - number of commercial vehicle crashes of a rapidly Performance and expanding interstate carrier population. PRISM issues request to DMV webservice. When it is for Registration ONLINE OLP, EGOV communications to/from CSS-vehicle information for OLP info is via broker. Systems
Management part of FMCSA
Web Service
Bidirectional
Web Service – We access their web service
Bidirectional
BROKER
Bidirectional
PRISM is through Xerox and returns info from its own systems primarily. PRISM comes to DMV for Hauling Permits (EGOV) and OLP (vehicle mainframe)
Motor Carrier
VISTA /TS supports the International Fuel Tax IFTA / IRP Agreement (IFTA). IFTA is a method that ONLINE Provider allows a motor carrier to register and pay VISTA/TS system quarterly motor fuel road tax in the carrier's base state (TS - Tax Services)
91
Motor Carrier
Motor Carrier Management ONLINE Information System (MCMIS)
92
Motor Carrier
ONLINE
93
Motor Carrier
ONLINE UCR -to FMCSA
Unified Carrier Registration transmittals to Federal Motor Carrier Safety Administration
BROKER
Bidirectional
94
Motor Carrier
ONLINE Webcat
WebCat provides Internet access to process vehicle titles, International Registration Plan (IRP) and International Fuels Tax Agreement (IFTA) transactions.
BROKER
Bidirectional
95
Motor Carrier
ONLINE Weigh Station
Citation Tracking processing
BROKER
Bidirectional
96
RPS
Process Mailed In renewals
BROKER
Bidirectional
97
SecuriTest
ONLINE SecuriTest
Web Based Testing - holds many types of Tests
BROKER
Bidirectional
98
SecuriTest
ONLINE
Securitest translations
Translations of Questions
Moveit
Incoming
99
User Access
ONLINE
External Users Online Users
Transaction Information
Complete 3270 Screen
Bidirectional
External Users Businesses
Driver Monitor Businesses can request Monitoring of their Drivers through Extranet - Transcript is produced when Event that is Monitored has occurred (Conviction) Monitor Request Incoming; Transcript - Outgoing - Mailed or FTP'd to Web
Extranet / FTP
Bidirectional
Online Transaction Processing
BROKER
Bidirectional
90
ONLINE
Federal Portal used to access FMCSA data. Requires login
Overrweight Carrier / Financial information Citation Payment
Fairfax Imaging RPS
100
User Access
ONLINE
101
User Access
ONLINE Internet
Appendix 2 - ii.6
DMV Interface Inventory
102 103 104 105
106
User AccessSelect User AccessSelect User AccessSelect User AccessSelect
ONLINE
DMV Select License Agents -
ONLINE EZFleet
ONLINE
Online Transaction Processing
BROKER
Bidirectional
Online Fleet Transaction Processing
BROKER
Bidirectional
BROKER
Bidirectional
BROKER
Bidirectional
BROKER Secure apps
Bidirectional
Salvage dealers/demolishers reporting crushed/demolished to VA DMV (access is via the Extranet though broker to vehicle-host and back)
BROKER
Bidirectional
Emissions Inspection results
BROKER
Bidirectional
Print on Demand Temporary Tag
BROKER
Bidirectional
Local Vehicle Renewals
BROKER
Bidirectional
MySelect (Branch Online Transaction Processing Offices)
ONLINE QFLOW
Customer Info - Used in MySelect
Hauling Permits supports the VA DMV’s Hauling Permits issuance of hauling permits for oversize or Internal interface overweight vehicles.
Vehicle
ONLINE
107
Vehicle
Vehicle ONLINE Demolishment
108
Vehicle
109
Vehicle
110
VehicleCORR
ONLINE Local Government
111
VehicleDealer
Online Vehicle ONLINE Dealer Vendor Systems (CVR )
Vehicle Title, Registration, Customer-add and Temp/Transport Print on Demand processing. (Vendors also produces reports daily and send directly to VSA.)
Complete / 3270
Bidirectional
112
VehicleDealer
Online Vehicle Dealer Vendor ONLINE Systems (DealerTrack)
Vehicle Title, Registration, Customer-add and Temp/Transport Print on Demand processing. (Vendors also produces reports daily and send directly to VSA.)
Complete / 3270
Bidirectional
113
VehicleDealer
Online Vehicle Dealer Vendor ONLINE Systems (TitleTec )
Vehicle Title, Registration, Customer-add and Temp/Transport Print on Demand processing. (Vendors also produces reports daily and send directly to VSA.)
Complete / 3270
Bidirectional
BROKER
Bidirectional
BROKER
Bidirectional
Complete / 3270
Bidirectional
114
VehiclePlate
115
VehiclePlate
116
VehiclePlate
ONLINE State Agency VI (Virginia ONLINE Interactive)
System that reconciles the bill from VCE against DMV plate order information. Information from PLADOS is extracted and Lic Plate sent to mainframe via broker. VCE sends Reconcilation ONLINE bill info as a text file via e-mail to Carolyn, between VCE and who stores on DMV G drive. Bill info gets DMV from G then to mainframe via broker. (Manf plate info that is also used is already on the mainframe.) Plate Number Status Processing (PNS) Plate number ONLINE Inquiry on PNS Record Inquiry Dept of ONLINE Corrections Plate Processing
Manufacture Plate Processing
Appendix 2 - ii.7
DMV Interface Inventory
117 Vehicle-VIN ONLINE NADA
freestanding VSAM file updated every month used for Vehicle Value info by Title Transaction / Mech Storage Lein ** CICS ** COBOL
BROKER
Bidirectional
118 Vehicle-VIN ONLINE NICB VINAssist
** CICS ** COBOL - VSAM FILE NO LONGER UPDATED used for vehicles older than 10 years- CALLED BY VEHMSL AND VEHPPI
BROKER
Bidirectional
119 Vehicle-VIN ONLINE VINA (Assembler) Vin provided - Vehicle Information returned
CALL to Vendor Provided Software that decodes the VIN Returning Vehicle Information
Bidirectional
Automatic license suspensions Customer / Conviction
started task
incoming
120
121
VSP
VSP
ONLINE State Agency
ONLINE State Agency
Complete BROKER National Crime Information Center (NCIC) Bridged file through VCIN Vehicle Information - determine DMV-CSSif vehicle is stolen NETWORKVCIN
122
VSP
ONLINE State Agency
VCIN Vehicle / Motor Carrier / Dealer / Customer information online to the State Trooper
123
VSP
ONLINE State Agency
WEB Service Customer, Sex Offender registry, Title, Vin, Plate Inquiry
124
CustomerADX
ONLINE Finalist
Address Standardization through file 164 ** CICS ** VSAM file updated monthly
125
Vehicle
ONLINE NMVTIS & BATCH
126
Barcode
ONLINE, Neomedia BATCH (PDFENCOD)
ONLINE, Elavon and
127 Credit Card BATCH Protobase
Complete Bridged file DMV-CSSNETWORKVCIN BROKER / Web Service
CICS through file 164 CICS National Motor Vehicle Titling info. Title, MCO, BROKER theft and Brand Data. Used during the Titling through file Processing.DMV Responds to queries from 54other states. Aamvanet CALL to Vendor Bar Code Generator Provided Software All our credit card transactions are cleared through Elavon. Protobase is the backend software for our apps that are integrated to use it, ie, web avr, remit prcsr, a few host based trans. Protobase is being dropped effective 9 30 15. Csc counters use swipe machines w dialup to Elavon. Viawarp is standalone app we also use, it goes direct to Elavon.
Standalone
Bidirectional
Bidirectional
Bidirectional
Bidirectional
Bidirectional
Bidirectional
Bidirectional
Appendix 2 - ii.8
DMV Interface Inventory
128
Motor Carrier
ONLINE IRP / Vista RS
VISTA (Vehicle Information System for Tax Apportionment) - RS- Registration services Get Vehicle Data Request sent to DMV from Vista RS System. This process will be called at the time of Supplement creation for a specific Fleet and Account. As vehicles are added to a supplement within Vista RS, a GET VEHICLE request is sent to DMV requesting vehicle info. The data returned from DMV is compared to the data on Vista RS The user will determine which data will be used.
Broker
Bidirectional
Appendix 2 - ii.9
DMV Current Environment Summary I.
INVENTORY A. Software AG 1. Module Types used at DMV DMV usage includes Maps, Helproutines, Programs, Subprograms, Subroutines, Copycode and heavy use of LDA’s, PDA’s, Globals, and AIV’s. 241 Construct Generated Modules (Return Checks System and SSG Utilitiy Menus) Type Programs Lines of Code Maps Online Table CopyCust SSG Utilities Online Batch Submitters Batch Broker Services Total
4,000 6,300 2,200 130 200 140 2,910 220 16,100
500,000 2,400,000 500,000 15,000 82,000 66,000 1,050,000 100,000 4,713,000* 3,900,000 lines without comments
2. Adabas files used at DMV (Database 195/ 198) Type Programs Adabas Files Unique Data Elements MU/PE’s Production Records* Commands in a week Delete Read by ISN Read Logical Find Add Record Read Physical Histogram
250 6,500 500 500,000,000 3,220,494 23,538,331 234,835,987 44,702,216 7,546,173 58,003,753 171,299,797
* Does not include Privacy and Audit Warehouse
3. Databases used at DMV (Adabas Compression rate 60 – 80%) ID Environment File Size Associator Total Size Comments (GB) Size (GB) (GB) Production 4.7 1.1 5.8 Non-CSS (Refunds only) 100 191 192
Production Production
126.5 87.2
25.9 17.9
152.4 105.1
195 198 197 135
Production Production Production Training
66.5 25.1 68.2 2.7
32.9 5.2 31.4 .8
99.4 30.3 99.5 3.5
175 110 185 105 190
Development Development Test Test DBA Use
7.5 1.5 8.5 1.5 4.8
2.0 .2 2.8 .4 1.2
9.5 1.7 11.3 1.9 6.0
Audit Warehouse Privacy Warehouse (Growing-50gb expected) CSS OLTP CSS Historical Copy of 195 for Adhocs Masked /Copied CSS Production customers CSS Non-CSS CSS Non-CSS
Appendix iii.1
DMV Current Environment Summary
4. CSS Transactional History Store Privacy (400 Million Records – approximately 500,000 loaded daily) Any access to customer information by external parties must be captured and held for 3 years. The information retained is requestor information, Request type and purpose, date, and the specific customer information provided to the external party. Any customer can request a privacy disclosure of who has accessed their information. Retrieval of this information can be for a specific date or a full disclosure of all information provided to external entities for the entire 3 years of history captured. Privacy information is also categorized by type of retrieval. Confidential privacy requests are requests performed by law enforcement when performing confidential inquiries against a customer under investigation. These retrievals are not to be provided back to the customer. Unless specifically marked as confidential, all other external accesses to customer information is classified as normal privacy requests and available to the customer upon request. A unique file is created for every day and kept for 3 years in the Privacy Warehouse; it will not be fully loaded until Sept 2015.
Audit Warehouse - Stores two types of audit information: i. Customer Change Data (500 million records adding 300,000 daily and up to 8 million records on the annual safe driving points update) The system retrieves the Adabas Protection Logs of the before and after images of Adabas files for selected customer information that was changed, stored or deleted. These before/after images are reformatted and stored in the Audit Warehouse along with the User id of the teller, Transaction name, and date/time when this transaction was performed. A unique file is created for every day and kept for 5 years. ii. Teller Transaction History (450 million records adding 300,00 daily) This system provides a high-level audit trail of CSS functions performed against a given customer or by a given teller. The information provided is the Customer Number, Screen id (Transaction) , Date and Time of the Transaction, User id of the teller that performed the transaction, and the work location. The system is populated by capturing the Protection logs from the Online-Transaction file and stripping off records where the screen-id and Transaction customer number are valued. A unique file is created daily and retained five years.
5. Software AG Products Product Natural Adabas Natural Construct EntireX Complete Natural Security Adabas Online System Natural Optimizer Compiler Predict
Version 8.2.3.1 8.2.6.0 5.3.1.1 9.5.1.0 8.2.3.0 8.2.3.1 8.2.6.0 8.2.3.0 8.2.2.1
6. Mainframe IBM Mainframe Operating system: ZOS 1.13 LPar Executing the DMV Applications is configured for 560.8 MIPS. Approximate MIPS DMV applications use during the Work Week: 400 MIPS Appendix iii.2
DMV Current Environment Summary B. Non-Software AG Software
Environment
IBM JCL IBM JCL
Production Production
Volume 1,470 145
Cobol/CICS Cobol/CICS
Database 100 Database 195
Small Small
SAS / Script Expedite Base/ MVS through ADVANTIS
Database 195 Production
50 jobs 10 Jobs
Assembler Assembler Assembler Assembler
Database 100 Production Production Production
Small Small Small Small
Assembler
Production
365 Modules
Detail JCL PDS (7,749 individual Steps) Online programs submitting Batch Jobs (See I.A.1) MVS and SAG Adabas Utility steps included (Sort, Lebgener etc) Refunds/Payroll systems Interface between Natural and CICS for Aamvanet processing Used to produce correspondence in batch Expedite is an electronic mailbox system that you can use to send information to and receive information from trading partners. Expedite Base/MVS provides the interface that makes it possible to use Information Exchange from a z/OS environment. Expedite Base/MVS uses Information Exchange to deliver and receive data, such as electronic data interchange (EDI) data. To communicate with Expedite Base/MVS and transfer data files in and out of Information Exchange, you use application program interface (API) commands. Used at DMV for Electronic Lien processing and Vehicle Insurance Transmittals. Refunds System along with TABFL1, CODES2, DMV015 Cobol Program DMVJ67 calls CODES2 and DMV005 Cobol Program DMVU59 calls TABFL1 Cobol Program DMVN09 calls DMV015 DMVS1 - DMV Developed Assembler routine used for Bidirectional data exchange between the Mainframe online applications and other .net or Web Applications
C. User Types
2,000+ Internal and External Users via Software AG Broker Services to windows .Net 5,000+ Internal and External Users including Online Dealers, via 3270 connections
Appendix iii.3
DMV Current Environment Summary II.
Online Processing A. CICS Integrations Special online processing will require re-work after re-hosting. Communications to these functions will need to remain in place after Rehosting. Reengineer communications protocals . 1. AAMVANET (American Association of Motor Vehicle Administrators) Driver Licensing and Identification (NDR, CDLIS, Social Security Verification) INCOMING is via STARTED BATCH TASK and AMVANTPA Program OUTGOING is via Shared File 98 and CICS / COBOL
Figure 1 AAMVANET /CICS and COBOL Usage
Online Process
AAMVANET / CICS and COBOL Usage at DMV
BATCH COMPLETE
Online Production Complete Vehicle transactions
Online Production Complete DRIVER Transactions – Retrieve / Store Request to File 98
Nmvtis Retrieve / Store Request to File 54
Nmvtis
Broker Server for NMVTIS DMVPT410 – AMVANTPA PROGRAM– CONTINUOUS RUNNING INBOUND PROCESS
Adabas File 98 DMV-CSS-NETWORK
Broker Server for NICB
NICB
UNI – Program Licensed by AAMVANet
AAMVANET Network Interface
Incoming from Other States
NADA
CICS
COBOL – Separate In House Developed Programs Inbound reformats UNI data for Specific Adabas File (98 or 54) / Outbound Read Adabas file (98 or 54) and Reformats data into UNI Format
SSN Verify With SSA
Adabas File 164 – FinalistMaster
BROKER
CICS
NDR
Broker Server for NADA
Adabas File 54 NMVTIS-MASTER
NMVTIS
CDLIS
Online Address edit – retrieve Zip+9
NMVTIS
COBOL – Separate In House Developed Pgms Read its VSAM file
Broker Server for NICB
Broker Server for NADA
VSAM File
VSAM File
VSAM Files
NICB – No longer Updated
NADA – Updated Monthly
Finalist Updated Monthly
Appendix iii.4
DMV Current Environment Summary 2. NADA (National Automobile Dealers Association) New and Used Car Prices for retrieval of Vehicle Blue Book Value from a VSAM file 3. NMVTIS (National Motor Vehicle Titling Information System) The National Motor Vehicle Title Information System (NMVTIS) is designed to protect consumers from fraud and unsafe vehicles and to keep stolen vehicles from being resold. 4. NICB (National Insurance Crime Bureau) Partners with insurers and law enforcement agencies to facilitate the identification, detection and prosecution of insurance criminals . Retrieve VIN information from a VSAM file. Only used by 2 Processes and is being replaced with RL POLK VINACS Software. This function will not need to be carried forward to the new environment. It can be replaced with VINA. 5. FINALIST (Pitney Bowes) Address Verification, Standardization, and Delivery Point validation. Retrieved from a VSAM file. The Finalist product is used both Online and in batch. (3 online programs –7 Batch Programs).
B. CALL Integrations 1. 2. 3. 4.
Bar Coding Credit Card Processing Credit Card Reconciliation VINACS (Return Vehicle Information via entered VIN)
C. SAG EntireX Broker Integrations EntireX Broker is a middleware technology developed by Software AG to address vital software communication issues involved in business process reengineering and open enterprise computing. At DMV, Broker is used for interfacing with applications to include .net with Oracle or Sql Server. A complete list of interfaces is detailed in Appendix 2. Included in this list are: 1. DMVNOW – Internet Processing for the Public 2. mySelect -- Customer Service Center Windows .Net front-end application 3. DLCI – Centralized License Issue (CBN) and Driver License Photo capture at the Customer Service Centers 4. QFLOW – Management of Flow of Customers to Tellers at the Customer Service Centers 5. Securitest -- knowledge Testing at the Customer Service Centers 6. DMVSelect – External License Agent Windows .Net front-end application accessed via FOB 7. Secure Apps -- Intranet / Extranet applications accessed via a PIN or FOB
Appendix iii.5
DMV Current Environment Summary D. SAG Complete Integrations 1. State Police -- This functionality will need to remain in place but re-written in some fashion. Coordination with the State Police is required – they will need to modify their system as well. The diagram that follows describes this critical integration.
Figure 2 Virginia State Police Integration
State Police Processing with DMV DMV Production COMPLETE
Online Process
Vehicle Processes calling
LEGEND NCIC – DMV Requesting Status of Vehicle ALS – Automatic Lic Suspension – VSP to update CSS State Police Queries – VSP requesting Information State Police Web Exchange – VSP Requesting Info – or Updating CSS with Sex Offender indicator
NCIC
Broker Server NCICNQNA
BROKER
BROKER Server NCICBRK
Adabas Files
Adabas File Vehicle stops
APXNCIC – Natural Program
Return NCIC Response
VSP Production COMPLETE
Natural Program to Process Specific Request – Driver Inquiry – Vehicle Inquiry Dealer Inquiry– Motor Carrier Inquiry Transcript request – Stolen Veh/Plate Stops
3. Call program To Process Request
Add/ Remove
4. Store Results
2. Store Request
APXRTR – Online Running NATURAL Controlling Program checking for Incoming Requests 1. Send VSP Query VSP add/remove Stolen stop ALS 7. Send Response or return NCIC Response
Send NCIC Request
Adabas File 98 DMV-CSS-NETWORK-VCIN 5. Retrieve Results
6. Format Buffer For Return
Natural Program to Format Response
ALS
State Police Complete Region–
Adabas File CSS-ALS-HOLD
Maintained by DMV Complete Logon’s
Virginia State Police Web Exchange broker servers
BROKER
State Police Headquarters - System
State Police VCIN Network
NCIC Broker Servers for Each function
Natural Programs to Process: Sex Offender Registry – Update CSS CSS Veh Lookups (Title, Vin, Plate) Dr Lic Inquiry
Web Service – Photo Request
State Troopers
DMVPT140 – Started Task BATCH Automatic License Suspension – Hourly Submitter for DMVDD141 – Puts Customer in Suspension status
CISS Database (Photos)
Adabas Files
Broker Production COMPLETE
Appendix iii.6
DMV Current Environment Summary 1. IBM 3270 Screen Access – In excess of 5,000 external users through 623+ use agreements and more than 2,000 DMV Headquarters users have a direct 3270 screen emulation connection via SAG’s Complete to access specific online functions. SAG’s INPUT using MAP statement is still present in many applications to include those for the External Users, Headquarters staff and Online Dealers. Coordination will be needed with all External users and Online Dealers and, based upon the solution chosen, the “Input Using Map” statement may be removed through code clean up. Some of the external access may be replaced with web-enabled transactions. See Figure 4 Below.
Appendix iii.7
DMV Current Environment Summary III.
Online Utilities and Support Applications A. COPYCUST Utility Process to Copy the Customers information from related files down to the development / test / or training environment. Performs masking on all sensitive information. Utilizes SAG-provided utilities for this function. The functionality will need to remain in place but may be re-written.
Figure 3 CopyCust Utility
CSS-ORDERNOTICE (FILE29)
CSS-EVENTS (FILE 27)
CSSPRECOMPLY (File 42)
DMV-CSSINS-MON (File 91) 1:8 Cust
DMV-CSS-PINMAIL-INFO-336-A Curr and Prior: PHONE-NO MOBILE-NO TEXT-NO EMAIL ADDRESS
CUST-LEGAL-NAM295-A Customer Long Name CSS-USE-AGREE (File 39) Contact Name / Phone Number
CSS-CAISINTERIM (File 64)
Invert #’s Reset contact infol
DMV-CSSOVERLOADPERMIT (File 100) Copies both 1:2 Cust
CSS-MEDICALCERTIFICATE303-A
Cust Name, Address, SSN CSSVETERANID-349-A
Sensitive data present in File
DMV-WEB-RESULTS-179-A CSS-REVBILLREFUND (File 45)
DMV-CSS-FLEET-VEH (file 88)
Cust Name, Address
Copy Name Adx SSN
VRT-EXEMPTION-265-A
LVR-DISCOUNT-277-A SSN
Copy Name Adx
CSS-CUST-AAMVATRANS-236-A
Invert SSN ? Bus - ?
Copy SSN/Name
CSS-CUST-DR-LIC (File 24) Mask Ind (Not ISA)
Copy Name/ssn
Mask Name, Mailing Invert SSN and Foreign Lic , Reset Dwelling- Prior Adx Delete Alias
Copy Name/ssn
DMV-CSS-NETWORKAAMVANET (File 98) LVR-TRANSITION280-A Customer Name, Address
Copy Adx / Name
Prior Cust No including SSN , ,Cust Name
DMV-CSS-PLATEREQUEST (file 97)
Copy Name Adx SSN Reset Priors
CUST-HIST-PRF-DOCS-308-A
DMV-CSS-IDCARD-238-A
CSS-FRHEARING-144-A
Copy Name Adx
DMV-CSS-DR-LIC182-A CSS-DR-LIC-HIST (FILE26)
Copy Name Adx
Copy Adx Cust1 /Cust2
Copy Name Adx
Copy Name Adx
CSS-SR22 (File 37)
CSS-HMEBACKGROUNDCK-APPL-296-A
CSS-IGNITIONINTERLOCK216-A
DMV-CSS-TITLE-VEH (file 93) – NOT ISA Copies All Coowners 1:8 Cust
Name, Prior Name, Phone, Address, Prior Address, SSN
CSS-ESCORTDRIVER-CERTIF-359-A (Phone Number)
DMV-CSS-TEMP-TAG325-A Copies both owners Dwelling Address cust1, Dwelling Address-Cust2
PL-SPECLREQMTCOMPLI-196-A
DMV-CSS-TITLE-VEHACTIVITY (file 89)
Copy Adx Copy Adx
Reg Mailing / Gar Juris
Reg Mailing Address – Gar juris VEH-REG-ELECTRONICNOTIFY-340-A - Email – phone #’s
DMV-CSS-TITLE-VEHHISTORY (File 138) (NOT ISA)
CSS-CUST-STOPINFO-133-A CSS-ALSHOLD-149-A
DMV-CSS-CDLTEST-RESULTS (File 30) CSS-RENEWTRANS-190-A (Less than 1000 records) Name,Address
4/21/
Copy Name
DMV-CSS-HANDICAPPARKING-PERMIT (File 104)
CSS-CUSTNO-HIST (File 41)
Revision Date: 2014
COPY CUSTOMER and DATA MASKING REVIEW
Name, Address
CSS-CDL-NOSHOW-313-A
Reset Reg Mailing Gar Jur 1:8 Cust – the following Address, Customer Name, Mailing Address
Copy Adx/Name DMV-CSSREG-PLATE (File 94)
ELIENADDR-23-A
DMV-CSSREG-PLATEHISTORY (file 86)
LOCALVEHICLEREGISTRATIO N-276-A
IS-VEH-AUTH350-A
IS-VEH-AUTH-HIST352-A Name/Adx
Appendix iii.8
DMV Current Environment Summary B. Online Submission of Batch Jobs Currently there are processes that submit batch jobs to either produce a dynamically generated report or send an email based upon specific conditions. This functionality will need to remain in place but may be re-written.
C. DMVS1 (365 Modules) DMVS1 is a DMV developed routine used for bidirectional data exchange between the CSS Mainframe Online applications and other .net or web applications and the Online Dealer vendor system. This process encodes the data fields to Comma delimited data streams for transport. The receiving application then decodes the data stream back into the data fields for display and processing. The Customer Service application has limited the use of DMVS1 and but it is still in use. Refer to the diagram below for more detail on DMVS1 use. Figure 4 CSS Data Flow
CSS Data Flow for WEB, Online Dealers, and Host Processing
Online Dealer Vendor System (Title and Reg Transactions)
Presentation receive and format data
Format Data (Separate Comma Delimated or Compress into Comma Delimited)
Perform Function
Call DMVS1 Branch Transaction Router
Online Virginia Dealers
Receives data through an Input statement
Routes data, Back to CSC or Broker Appl Based upon Global information
WEB
Broker Complete SERVER Format DATA (Separate Comma Delimated or Compress into Comma Delimited )
Call DMVS1 To Compress Variables into Comma Delimited Array Not 3270
If WEB Communication Type
Initial Web Development used DMVS1 Path Reengineer – remove DMVS1 Call – 365 Programs
3270 Screen / Headquarters , External Users, 5000+ Users
Perform Function – Return results to Display
Separate Comma Delimated Array into Variables
Rehosting Solution will need to Communicate with these users
Input Map Statement in Natural Code -
3270 Screen / HQ, External Users Online Dealers
Appendix iii.9
DMV Current Environment Summary IV.
Online Communications to Direct Print for HQ, Dealers and ISO Internal Application process and a database table (2103) is used for Headquarters users to print Transcripts, Audit Warehouse, and other reports to Specific LexMark Printers. The Printer definition is a combination of the table entry and the print definition setup in a PSS (Application). The application program uses Define Printer Statements to then route the print to these printers. This type of print will need to be reengineered within the Natural Code. Figure 5 Direct Print Communications
Appendix iii.10
DMV Current Environment Summary V.
Batch Processing Detail A. Scheduling DMV currently uses a combination of Control-M and an in-house developed Submitter application. These are used to perform the job scheduling and production control for the batch cycle executing on the IBM OS platform. Jobs are scheduled based predominately upon two types of prerequisites: job prerequisites for cycle submitters and special jobs - date/time prerequisites. Control-M is workload automation (traditionally called batch scheduling) software obtained by BMC Software. It was originally developed for IBM mainframe computers (OS/MVS operating system), but has since expanded and is also available for distributed computing platforms including Unix, Windows, Linux and OpenVMS environments. DMV executes over 1,400 jobs across its many batch cycles to include 500 jobs Daily, Weekly, Monthly, Quarterly, Semi-annual, and Annual batch cycles. Production Control also submits asrequested and Adhoc jobs when needed. The current MVS utilities used within the job stream are:
Sort Iebgener – Copy a sequential dataset IDCAMS – Processing VSAM files Unzip IEFBR14 – Used to delete a sequential dataset
B. Batch Job Types and Volumes Description
Frequency
Processing trigger records e.g. Change of address, court convictions Vehicle renewal notices – mail Vehicle renewal notices – eMail Driver License renewal notices -- mail Driver License renewal notices – eMail Vehicle and Driver Transcript Requests and Bulk Information Requests Miscellaneous Correspondence e.g. Compliance Letters Safe Driving Points updates Reporting Batch Jobs – output to Ctl-D Financial Deposit Transmittals Commissioner of Revenue extracts Locality extracts
Daily
Financial Billing / AR Processing Purge jobs CSS Updates e.g. convictions, data exchanges
Volume 600,000
Monthly Monthly Monthly Monthly Monthly
370,000 100,000 68,000 17,000 4,500,000
Monthly
500,000
Annual Various Daily Semi-annual Various
2-4 times a year Various
8,000,000 700 $8.4 million Extract merges 8 million Registration records, 10 Million Vehicle records, 10 million Customer records, then splits by Jurisdiction and saves to Datasets. Used to provide Property Tax – Vehicle Information to the requesting Localities where the vehicle is garaged. 20,000,000 from transactional and source data files moved to historical files 70 + batch interfaces
Appendix iii.11
DMV Current Environment Summary C. Batch Interface Descriptions Method
Processes
Users
FTP – Connect/Direct
30
MoveIt EDI/Aamvanet EDI
30
Started Task / APXRTR
Started Task / AMVANTPA Finalist - Batch
OnBase
8
Comments Printed output / Shared Dataset 12,000 700
Insurance Companies Electronic Lien Processing VSP – Incoming – Automated License Suspension Incoming Aamvanet Executes a vendor provided Application executed in batch to process address standardization and Delivery point validation in batch
processes automatically format and set up a Mainframe Dataset that Onbase picks up through a Daily Load Script
Appendix iii.12
DMV Current Environment Summary D. Batch Data and Report / Printed Output Handling 1. Print Stock. Batch processing includes printing to special card stock. Current batch jobs identify themselves as one that requires special card stock (CLASS) and specifically, the type of card stock that needs to be loaded into the printer (FORMS) prior to the OCE Printer actually printing the output. Batch jobs running in the windows environment will need to transmit some type of control information to the OCE Printers to indicate special card stock requirements. Special Forms include: Titles Renewal / Registration cards Certificate stock Perforated 3 equal sections Card stock (3 types) Envelopes Labels 2. Generation Data Group (GDG) A collection or group of cataloged datasets having the same name and bearing a chronological relationship to one another. There are roughly 560 unique GDG’s defined within the CSS Production JCL, where up to 250 generations of data is kept. The Purpose of GDG’s is to be able to retrieve a prior generation for reprocessing or having the same troubleshooting 3. SMS (Systems Managed Storage) System-managed storage is the IBM automated approach to managing storage resources. It uses software programs to manage data security, placement, migration, backup resources., recall, recovery, and deletion so that current data is available when needed, space is made available for creating new data and for extending current data, and obsolete data is removed from storage. SMS backup’s datasets so that previous versions of the data are retrievable. At DMV, up to 16 versions of the dataset are available for recovery. DMV is heavily reliant on SMS. 4. Control D All Internal Reports and JOB execution output is stored to Control D and kept for a defined period of time (45 days to 5 years). Users can logon to Control D to View / Print any report output. BMC Control-D for z/OS automates every aspect of report life cycle management from creation through archival and eventual disposal, ensuring reports are efficiently broken down by the user, distributed automatically, viewed online from a web browser, archived to offline storage, and retrieved from archives. System-managed storage is the IBM automated approach
Appendix iii.13
Glossary of Terms Name
Description
Page References
AAMVANet
American Association of Motor Vehicle Administrators Network
RFI - Section 2.F Appendix 1 Appendix 2 # 75,78, 81,125 Appendix 3 II.A, V.C
AMVANTPA
Natural Program running in a started task processing InBound AAMVAnet Transactions from other states
Appendix 3 II.A, V.C
APXRTR
Natural Program running in Complete processing in-bound Appendix 1 / out-bound State Police , NCIC transactions Using VCIN Appendix 3 II.D, V.C
APXNCIC
Natural Program called by APXRTR to process NCIC Transactions
Appendix 1 Appendix 3 II.D, V.C
Audit Warehouse CSS Transactional History Trail – Process PLOGS from Adabas
RFI - Section 2.I Appendix 3 I.3, I.4
CAIS
Court Automated Information System
Appendix 2 #20, 21
CARS
Collections and Reconcilation System
Appendix 2 #32
CAS
Commonwealth Authentication system – Broker Appendix 1 application that accesses Customer Information to develop Appendix 2 #30, 84 Authentication questions for Customer Verification See EDM
CDLIS
Commercial Driver Licensing Information System Accessed via AAMVANet
RFI - Section 2.F Appendix 2 # 78 Appendix 3 II.A
CICS
Customer Information Control System
Appendix 1, Appendix 3 Pg 3,4
Connect Direct
Point to Point File Sharing Client and Protocol
RFI - Section 2.G Appendix 2 # 13, 30,31
Control D
BMC Control-D for z/OS automates every aspect of report RFI Section 2.G life cycle Appendix 3 – V.D
Control M
BMC Control-M for z/OS Job Scheduling
RFI Section 2.G Appendix 3 – V.A
Copycust
DMV Utility used to copy and mask PI data from Production to TEST, TRAIN and DEV environments
Appendix 1 Appendix 3 – III.A
CSC
Customer Service Center – See MySelect
RFI Section 1.B, 1.C
CSR
Cross Sell - Company receiving Vehicle information in Bulk Citizen Services System
Appendix 2 # 60
CSS CVIEW CVR
Motor Carrier Overload Payments system - Uses Broker to Appendix 2 # 87 access the Mainframe Online Vehicle Dealer- Vendor System Appendix 2 # 111
Dealer Track
Online Vehicle Dealer - Vendor System
Appendix 2 # 112
DEQ
Department of Enviromental quality - Vehicle Emissions testing
Appendix 1 Appendix 2 # 108
DLCI
Driver License Central Issue System - (Developed by CBN Appendix 1 – Canadian Bank Note) Appendix 2 # 79, 80 Primary Internet Web Site - Uses Broker to access the Appendix 3 – II.C Mainframe
DMVNOW
Appendix iv.1
Glossary of Terms DMV Select
External License Agents using Windows .net front end application via FOB (Called Select)
DMVS1
DMV Developed Assembler routine used for Bidirectional Appendix 1 data exchange between the Mainframe online applications Appendix 3 – pg III.C and other .net or Web Applications. Also used for Online Dealer processing.
Driver Alert
Application allowing Virginia's businesses to monitor their Appendix 1 drivers. Appendix 2 # 101
EAI
Enterprise Application Integration
EDI (Expedite)
Electronic Mail box system including Translation software - RFI - Section 2.G used for Vehicle E-Liens and Insurance Company Vehicle Appendix 3 - I.B Insurance Transmittals
EDM
Enterprise Data Management. IBM's Initiate, a master data Appendix 2 # 30 management solution. The goal of EDM is to aggregate customer records across agency systems into single unified "golden" records. DMV sends all Customer Changes, Deletes, and Stores to VITA to update the EDM database. CAS uses EDM to search for a customer, before vetting (getting from DMV the KBA questions and challenging the user with them). Credit card transactions Cleared through using Protobase Appendix 2 # 2, 127 Software
Evalon
RFI - Section 1.B Appendix 1 Appendix 3 – II.C
RFI - Section 1.C
E-Lien
Electronic Lien (Titles)
ERC/3M
Toll Road Processing. Elizabeth River Crossings (ERC) is Appendix 2 # 71 a sole-purpose company created to finance, deliver, operate and maintain the Elizabeth River Tunnels Project. Electronic Verification of Vital Events. Record Appendix 2 # 76 certification / verification via NAPHSIS (National Association for Public Health Statistics and Information Systems).. DMV issues birth certificates to Virginia born customers. Customer receiving Vehicle Information in Bulk Appendix 2 # 61
EVVE
Experion
Appendix 2 # 55
Ez-Fleet
Businesses owning fleets of vehicles using Windows .net front-end application for vehicle renewal processing
Appendix 2 # 103
Finalist
Address Verification, Standardization and Delivery Point Validation. Software developed by Pitnet Bowes
Appendix 1 Appendix 2 # 18, 124 Appendix 3 – II.A
FMCSA
Federal Motor Carrier Safety Admin
Appendix 2 # 93
FTP
File Transfer Protocol
RFI - Section 2.G Appendix 2 – Many
GDG
RFI - Section 2.G Appendix 3 – V.D
HQ
Generation Data Group - IBM - Collection of cataloged data sets having the same name and bearing a chronological relationship to one another DMV Headquarters
IBR
Incident based reporting
Appendix 1
Appendix iv.2
Glossary of Terms IFTA / IRP
International Fuel Tax Agreement - Motor Carrier The RFI - Section 1.B International Fuel Tax Agreement (or IFTA) is an Appendix 2 # 41,42,43,44,46,47, agreement between the lower 48 states of the United States 48,49,89,90 and the Canadian provinces, to simplify the reporting of fuel use by motor carriers that operate in more than one jurisdiction. IRP= International Registration Plan - Motor Carriers system for Motor Carrier Registration
IT
Information Technology
LVR
Local Vehicle Registration
Appendix 1
MCMIS
Motor Carrier Management Information System
Appendix 2 # 91
MCSC
Motor Carrier Service Center / Weigh Stations
RFI - Section 1.B, 1.C
Moveit
IpSwitch - Automated File Transfer system
MySelect
Customer Service Centers using Windows .net front-end application
RFI – Section 2.G Appendix 2 – Many Appendix 1 Appendix 2 # 104 Appendix 3 – II.C
NADA
National Automobile Dealer Association
RFI - Section 2.F Appendix 1 Appendix 2 # 117 Appendix 3 – II.A
NCIC
National Crime Information Center
Appendix 1 Appendix 2 # 121 Appendix 3 – II.D
Neomedia
Company providing the PDFENCOD Software
See PDFENCOD
NICB VinAssist National Insurance Crime Bureau Software application called Returns Vehicle Information via Entered VIN VSAM FILE NO LONGER UPDATED used for vehicles older than 10 years
RFI - Section 2.F Appendix 1 Appendix 2 # 118 Appendix 3 , II.A
NDR
National Driver Register - accessed via AAMVAnet
RFI - Section 2.F Appendix 1 Appendix 2 # 25,81 Appendix 3 – II.A
NMVTIS
National Motor Vehicle Titling Information System
RFI - Section 2.F Appendix 1 Appendix 2 # 125 Appendix 3 – II.A
NRC
Customer receiving Vehicle Information in Bulk
Appendix 2 # 62
OCE PRINTER Mainframe Printer – Printing all Batch output including special forms
RFI - Section 2.G Appendix 3 – V.D
Onbase
Hyland Software - Document Imaging system
Appendix 2 # 53
PDFENCOD
PDF Encode – Bar Code Generator Software
Appendix 1 Appendix 2 # 126 Appendix 3 – II.B
P-logs
Protection Logs
Appendix 3 – I
Appendix iv.3
Glossary of Terms POLK
Customer receiving Vehicle Information in Bulk
Privacy System
In-house Developed system to capture and store for 3 years Appendix 3 – I.3, I.4 all Customer related information released to external users
Appendix 2 # 63
Protobase
DMVs vendor provided solution for credit card processing Appendix 2 # 127
QAS
DMVs vendor provided solution for address verification
QFLOW
DMVs vendor provided solution for customer queueing in Appendix 1 the CSCs Appendix 2 # 105 Appendix 3 – II.C
RAVE
Registered Active Vehicle Users
Appendix 2 # 67
RPS
Appendix 1 Appendix 2 # 96
SAS
Remittance Processor - Hardware/software that reads the Renewal notices returned from the customer - accesses broker to update the Mainframe Records Mainframe software used for Correspondence Generation
SCRIPT
Mainframe software used for Correspondence Generation
Appendix 3 – I.B
Secure Apps
Intranet / Extranet applications accedes via PIN or FOB
Appendix 1
Appendix 2 # 77
Appendix 3 – I.B
Appendix 3 – II.C SecuriTest
DMV Knowledge Test solution used in the CSCs and by external entities
Appendix 2 # 97,98 Appendix 3 – II.C
SMS
Systems-Managed Storage (SMS) is a combination of hardware, software, policies, and automated procedures. The purpose of SMS is to manage storage at the dataset level.
RFI - Section 2.G Appendix 3 – V.D
Spider
Multi-Agency web based inquiry process that accesses various government agency information systems.
Appendix 2 # 85
TitleTec
Online Vehicle Dealer – Vendor’s System
Appendix 2 # 113
TREDS
Traffic Records Electronic Data System accessed via Appendix 1 broker to update the customer records with the crash event. Appendix 2 # 82
UCR
Unified Carrier Registration
Appendix 1 Appendix 2 # 93
UNI
Program Licensed by AAMVANet
Appendix 3 – II.A
VADA
Customer receiving Vehicle Information in Bulk
Appendix 2 # 64
VCE
Virginia Department of Corrections
Appendix 2 # 3, 114, 116
VCIN
Virginia Criminal Investigation Network
Appendix 1 Appendix 2 # 121,122 Appendix 3 – II.D
VI
Virginia Interactive
Appendix 2 # 109
Appendix iv.4
Glossary of Terms VINA
Vin - Assembler - Vehicle Information retrieval system
VINACS
RL Polks Vehicle Information retrieval system - replacing NICB Vehicle Information System for Tax Apportionment. RS is Registration Services See IFTA/IRP (This is the Xerox's system to maintain the IRP data. Vehicle Information System for Tax Apportionment. TS is Tax Services See IFTA/IRP (This is the Xerox's system to maintain the IFTA data. Virginia Information Technologies Agency
VISTA/RS
VISTA/TS
VITA
Appendix 1 Appendix 2 # 119 Appendix 3 – II.A
VRWS
Vehicle Registration With-holding System - Localities process the Parking Tickets and Deliquent Taxpayers by placing Stops on the DMV Customer Record.
Appendix 1 Appendix 2 # 65,68
WebCat
In house developed application that allows Motor Carriers Appendix 1 to perform RIP, IFTA and Vehicle Transactions - Accesses Appendix 2 # 94 Broker to update the Mainframe. It is also a front -end to Xerox's VISTA systems
Appendix iv.5
