1. X CVIEW V2.0 E X tensible Commercial Vehicle Information Exchange Window A Microsoft SQL Server 2000 & VB.Net Application Brought to you by the Washington State Department of Transportation

2. VERSION 2.0 IT’S NEW AND IMPROVED! WADOT’s XCVIEW has been completely rewritten – XCVIEW is now a Microsoft SQL Server 2000 and Visual Basic.Net application. This means that the program code to generate and load XML data is much simpler to understand and maintain. There’s a lot less code! SAFER 4.2 XML Compatible – All of the new SAFER 4.2 XML transactions are supported. We plan to support the SAFER XML transaction set as revisions are made by FMCSA.

3. WOW!!! IT'S SO %#@$#& FAST!!! XML Processing is extremely fast with SQL Server 2000 and Microsoft.Net applications! Performance comparison loading 1000 carrier updates: EDI CVIEW: 690 seconds WA's old XCVIEW: 320 seconds WA's new XCVIEW: 9 seconds! Performance is the same both for loading and generating XML Data! Note that performance will vary depending on CPU speed and available memory. Minimum recommended server requirements are: 1GB of memory, 2 GHz processor and 80 GB hard disk.

4. DATABASE INDEPENDENCE Faster loading means more database flexibility and easier database recovery. An entire CVIEW database can be restored from XML data in a matter of hours. This would take days with EDI data. This greatly simplifies database synchronization if a jurisdiction's CVIEW data becomes corrupted and its structure is different from SAFER. It's no longer necessary to restore or initially load a CVIEW database from a SAFER Oracle dump file.

5. XML MEANS BETTER NETWORK PERFORMANCE Zipped XML files are smaller than zipped EDI files. For example: XML data: 10 MB per 50,000 carriers (approx. - does not include Liability and Ins. data) EDI data: 15 MB per 50,000 carriers (approx. - does not include Liability and Ins. data)

6. X CVIEW V2.0 XCVIEW CVIEW DATABASE SAFERSAFER FTP/ XML State Volpe XML Files Legacy Systems E-Screening, Web App’s & Other Systems CVIEW_XML DATABASE XCVIEW VB.Net XML Utilities SQL Server Stored Procedures Scheduled Batch Applications v4.2

7. HOW EXTENSIBLE IS IT? XCVIEW allows a jurisdiction to have a very flexible vision for their CVIEW. “Xnnnn” Tranactions - In addition to the XML transactions defined by FMCSA (in SAFER 4.2), XCVIEW will support additional “Xnnnn” transactions that can be used to load and generate other CVISN data as XML transactions. CVIEW Database Flexibility - The XCVIEW XML utilities use an intermediate database to load and generate XML. This allows a CVIEW database structure to be unique from one jurisdiction to the next. This also means changes to the XML, CVISN applications, or the CVIEW database will have less impact.

8. EXTENSIBILITY (cont.) Any state can become a “customized” regional CVIEW collection point - XCVIEW can be used as a store and forward system for both intrastate and interstate data. Examples of this include: SSRS, foreign CVISN data (Canada and Mexico), Homeland Security, data fields not yet supported by SAFER. Groups of states can accommodate unique regional requirements for some data and, at the same time, be individual SAFER subscribers for nationally shared vehicle and carrier data. WADOT will be using this capability to share information with Canada and other northwest region states.

9. XCVIEW SUPPORT Washington will support XCVIEW. If support is minimal for a state, we plan to provide support at no charge. Oracle support??? The Microsoft XML bulk load interface only supports MS SQL Server 2000. This means that WADOT can no longer provide an Oracle version of XCVIEW. A hybrid XCVIEW with a SQL Server 2000 front end and an Oracle back end may be an alternative for Oracle sites to consider here. Support via other alternatives (pooled fund study?)

10. X CVIEW V2.0 XCVIEW CVIEW DATABASE SAFERSAFER FTP/ XML State Volpe XML Files Legacy Systems E-Screening, Web App’s & Other Systems CVIEW_XML DATABASE XCVIEW VB.Net XML Utilities Oracle SQL Script Scheduled Batch Applications v4.2 SQL Server 2000/ Oracle Hybrid SQL Server 2000 Oracle 8.1.7+

11. IMPLEMENTATION STATUS We’ve just started testing with JHU/APL and want to start testing with other states. If you are interested in testing XCVIEW please contact us (gofortb@wsdot.wa.gov). We plan to have our SAFER 4.2 compatible XCVIEW in production status in April, 2003.

12. CONTACT INFORMATION Bill Goforth CVIEW Systems Developer email: gofortb@wsdot.wa.gov 360-705-7639 Doug Deckert CVISN System Architect email: deckerd@wsdot.wa.gov 360-705-7632 web page: http://cvisn.wsdot.wa.gov/Documentation/Documents_menu2.cfm