1. Wisconsin’s Top Level Design CVISN Design Workshop May 30 – June 1, 2001 New Orleans, LA

2. Wisconsin CVISN Objectives Provide efficient application, processing and delivery of motor carrier credentials (e.g. registration, tax payments, permits, etc.) Increase the efficiency and effectiveness of CVO enforcement Enhance safety of commercial vehicle operations

3. Wisconsin Features Staggered IRP registration schedule built around IFTA activities No state HazMat program Deployment of statewide directory for interaction between citizens and state OSOW Permit Unit staff handle many functions that are performed by engineers in other states.

4. Key Strengths Organizational factors Experience in CVISN-related activities Underlying technology infrastructure

5. Organizational Factors Single-agency umbrella for CVO regulation and enforcement DOT Technology Management Council Flexible procurement practices CVO Business Plan used to guide activities – proven valid over time

6. Challenges: Organizational Legislature privacy concerns Biennial budget process timing Securing state matching funds DOT Technology Management Council project prioritization Proposed Department of Electronic Government Multi-vendor environment

7. CVISN-Related Experience MOOSE – MCSAP Out Of Service Enforcement Deployed between WI and MN Snapshots used to determine red-light License plate reader Data sharing between states Standardized data and report formats Timing of data – critical issue

8. CVISN-Related Experience MCES – Motor Carrier Enforcement System Collects information from every contact that State Patrol has with carrier and vehicle Beginning of SAFER-like functionality within the state Operational since 1987 – 14 years of data Available real-time at SWEF

9. CVISN-Related Experience OOPPS – Oversize / Overweight Permit Processing System On-line application for annual permits Limited self-issuance of single-trip permits using table-driven routing Will expand to include on-line renewal of annual permits, automated routing engine, and electronic payment acceptance

10. CVISN-Related Experience Expertise in various information systems technologies that will be useful for CVISN deployment IBM VisualAge for Java JavaBeans and Enterprise JavaBeans IBM DB2 Oracle IBM WebSphere

11. Technology Infrastructure Statewide wideband network Single state mainframe data center Agencies have their own separate LANS Every Safety and Weight Enforcement Facility (SWEF) has had access to most state and federal systems since 1987

12. Technology Infrastructure Mobile Data Computers (MDC) Operational since 1997 Deployed in entire fleet including Motor Carrier Enforcement vehicles and 90+ individual law enforcement agencies Dual Web sites – WisDOT and vendor (The Polk Company)

13. Challenges: Technological Electronic funds transfer and credit card acceptance a work in progress Timing of XML alternative availability affects WisDOT and Polk development plans and strategies Multi-vendor environment Connectivity to Clearinghouses Data scrubbing for routing engine

14. Wisconsin Top Level Design - 4/19/2001 Wisconsin State Roadside Systems Wisconsin Commercial Vehicle Administration Systems Carrier Systems Credentialing System (e.g., CAT) CVISN Core Infrastructure Systems (National/Regional) MCMIS IFTA Clearinghouse IRP Clearinghouse NMVTIS SAFER NCIC / NLETS Compliance Review (e.g., CAPRI) Service Providers Internet Tools (e.g. Browser) Other Carrier Systems Transponder Carrier Commercial Vehicle CI Licensing & Insurance CDLIS DOT Web Site (12) DOJ (14) Crime Files Note: Each LSI also contains a messaging interface component Driver (2) Licensing DMV (7) Revenue Intrastate Veh Reg Titling Authority & Insurance SSRS IRP IFTA SafetyNet2000 MCES Message Interface DOJ Msg Switch PrePass Screening MCES Client ISS LSILSI MIMI LSILSI MIMI LSILSI MIMI MIMI LSILSI LSILSI MIMI LSILSI LSILSI LSILSI MIMI MIMI MIMI OSOW LSILSI MIMI MIMI MIMI CVIEW MIMI LSILSI (1) (3) (4) (5) (8) (9) (10) (11) (13) (8) (15) (16) (17) (18) PrePass Service Center (19) (20) Service Provider Web Site (21)

15. Top Level Design Principles Messaging/Queuing approach to application integration Minimize interfaces to external systems Snapshot updates will be done on transactional basis Minimize Legacy Applications Changes Communication among state legacy systems use existing syntax

16. Key Top Level Design Features Messaging Interface CVIEW PrePass with integrated WIM ASPEN Equivalent Carrier Access

17. Messaging Interface (MI) Communications among state systems handled via the MI Routes transactions between legacy applications, CVIEW, CI & Roadside Employs scripts associated with specific transaction types Provides application connectivity across different hardware/software environments

18. CVIEW CVO Snapshot summary database for both interstate and intrastate carriers Interface to the SAFER system Bi-directional distribution hub between roadside systems and SAFER Interface to PrePass PreView for periodic SnapShot updates

19. PrePass with Integrated WIM Combination of PrePass and mainline WIM for screening PrePass roadside screening computer updated every 80 minutes CVIEW provides periodic Snapshot updates to PrePass PreView Message boards signal pull in/bypass at Menomonie SWEF Uniform roadside architecture proposal – Jim Newton

20. Typical PrePass Roadside Screening Configuration Single Lane Scale 5/21/2001 Advance location reads Truck Transponder ID ICN Signals bypass or pull in Decision to truck transponder 1000 ft4000 ft Gore point WIM scale Scale house Static Scale lane Inspection/ Observation lane Static scale Compliance reader WIM scale

21. ASPEN Equivalent Builds on current MCES functionality Replaces current 3270 configurations at SWEFs with MCES Client Client Provides SWEF access to Snapshots via CVIEW, state source systems and DOJ switch Hope to ultimately link Client to PrePass screening computer

22. Carrier Access Accommodates web and computer to computer access Transactional web access available to limited number of carriers for OSOW today Piloting Polk COVERSnet web access to IFTA Computer to computer access for carriers underway

23. Wisconsin Top Level Physical Design - 4/19/2001 DOA Data Center - DOT portfolio DOT / DSP (Roadside) LAN Authority & Insurance Carrier Systems SAFER CDLIS Licensing & Insurance Driver Licensing IRP Clearinghouse IFTA Clearinghouse Internet Tools MCES Client ISS Firewall Intrastate Veh Reg Titling MCES DMV Revenue IRP Clone DOJ Msg Switch Interface SSRS OSOW Data Base CVIEW CI OSOW Application DOT Web Site MadMan OC3 Ring Firewall BadgerNet OC3 Ring (2) DOT LAN’s - HFSTB (1) DOJ Crime Files Message Switch MCMIS NCIC NLETS CVISN Core Systems Firewall T1’s to all State Agency & law enfor. remote sites (4) T1 (5) Internet (6) DOT / DSP AS/400 MDC Controller DSP Microwave network (7) (8) (10) ( 11 ) (12) Oracle IRP / IFTA SafetyNet2000 (13) Internet (9) (3) (17) (14) (16) (18) PrePass Screening Msg Interface (15) Credential System PrePass Service Center Service Provider Web Site

24. Top Level Physical Design Mapping of applications to data centers and roadside Network infrastructure Middleware plumbing Directory services

25. Application System Mapping DOA OS/390 Mainframe hosts most of portfolio DOT LANs (HPUX/Oracle & NT) DOT AS/400 (mobile data computer controller) DOT NT workstation at SWEFs DOJ Unix message switch

26. Network Infrastructure BadgerNet and MadMan connectivity BadgerNet network topology Protocols Mobile data computers

27. MadMan ATM ring connecting Madison metro area state government HQ locations Connection to other agency HQ’s Connection to BadgerNet Connection to Internet (Napnet) Each agency has its own firewall OC3 speed (155mb)

28. BadgerNet OC3 SONET backbone ring 19 ATM switches provide access to ring Access links from remote locations to ring T1 (1.544mb) minimum speed BadgerNet Backbone & MadMan are ATM Access links are Frame Relay Presence in 1800 locations

29. BadgerNet Network Topology

30. Protocols All BadgerNet connections are IP IP Internet connections to Core,Carrier & vendor systems Exceptions are NCIC/NLETS and CDLIS NCIC/NLETS private T1 running IP CDLIS 256kb Frame Relay running encapsulated SNA over IP

31. Mobile Data Computers (MDC) State Patrol Microwave system provides statewide wireless backbone Proprietary MDC protocol Upgrade to IP planned, however…….. Cellular pilot underway as an interim solution No CDPD in Wisconsin, cellular coverage sparse in northern areas

32. Middleware Plumbing Will employ IBM MQSeries Middleware that the Messaging Interface (MI) will be built on Provides cross platform connectivity between applications Supports hardware platforms ranging from Palms to OS/390 Supports application environments such as CICS, Websphere, Oracle, etc

33. Directory Services Statewide directory services facility in limited production Built on Novell eDirectory (LDAP) Single ID and authentication credentials Allows self registration & maintenance by business partners OSOW first production application using the directory

34. SWEF Of The Future

35. New Component Summary Credential Interface Sole interface for transactions between the state and carriers / carrier agents Receives transactions Sends acknowledgements and products Performs basic editing EDI and XML translations

36. New Component Summary Message Interface Closely integrated with Credential Interface Additional functionality includes Receive and store transactions arriving from carriers and agents Assemble “information packages” Send acknowledgements and products Route updated status to CVIEW Route snapshots from CVIEW to roadside Route selected Snapshots to PrePass Service Center

37. New Component Summary CVIEW Wisconsin CVIEW Built using APL or vendor CVIEW Single interface point with SAFER Summary information database Interstate Intrastate

38. New Component Summary MCES Client ROC functionality Retrieves snapshot data from CVIEW Provides roadside access to state systems ASPEN equivalent Automated inspection reporting

39. New Component Summary PrePass and integrated WIM Voluntary program Electronic clearance Mainline Weigh-In-Motion Separate screening computer PreVIEW connection to CVIEW Future connection to MCES

40. System Change Summary Migration of MCES Client from 3270 terminals to LAN-based workstations LSIs and LMs for all legacy applications Network Connections

41. CVISN Level 1 Compliance Safety Information Exchange ASPEN (or equivalent) at all major inspection sites. We have implemented our MCES (ASPEN equivalent) at all sites Connection to the Safety and Fitness Electronic Record (SAFER) system to provide exchange of interstate carrier and vehicle snapshots among states. We will connect to SAFER via our CVIEW

42. CVISN Level 1 Compliance Safety Information Exchange Implementation of the Commercial Vehicle Information Exchange Window (CVIEW) (or equivalent) system for exchange of intrastate and interstate snapshots within state and connection to SAFER for exchange of interstate snapshots. We will implement a Wisconsin CVIEW for snapshot exchange within the state and connect it to SAFER

43. CVISN Level 1 Compliance Credentials Administration Automated processing (i.e., carrier application, state application processing, credential issuance, and tax filing) of at least IRP and IFTA credentials; ready to extend to other credentials [intrastate, titling, oversize/overweight (OS/OW), carrier registration, and hazardous material (HAZMAT)]. Note: processing does not necessarily include e-payment. We will be deploying Polk’s COVERSnet application to provide automated processing of IRP and IFTA credentials. OS/OW deployment is progressing, with limited self- issuance of permits now in production.

44. CVISN Level 1 Compliance Credentials Administration Connection to IRP and IFTA Clearinghouses. We are connected to the IFTA Clearinghouse and we intend to join the IRP Clearinghouse At least 10 percent of the transaction volume handled electronically; ready to bring on more carriers as carriers sign up; ready to extend to branch offices where applicable. We expect to meet this volume. We are working with Polk to add EDI capabilities.

45. CVISN Level 1 Compliance Electronic Screening Implemented at a minimum of one fixed or mobile inspection site. Ready to replicate at other sites. We have a preliminary agreement with PrePass to implement their screening and clearance system at our Hudson and Menomonie SWEFs

46. Phases & Builds

47. Safety Projects

48. CVIEW

49. USDOT Number

50. Credentials Projects

51. OSOW

52. Electronic Credentialing

53. IRP Clearinghouse

54. Screening Projects

55. PrePass

56. MCES

57. Project Planning

58. CI/MI

59. Phase 6 and Beyond

60. Accept and Process IRP Renewal Applications 4/17/2001 Wisconsin Roadside Systems Carrier Systems Credentialing System (e.g., CAT) CVISN Core Infrastructure Systems (National/Regional) NCIC / NLETS IRP Clearinghouse IFTA Clearinghouse NMVTIS MCMIS SAFER Compliance Review (e.g., CAPRI) Service Providers Internet Tools (e.g. Browser) Other Carrier Systems Transponder Carrier Commercial Vehicle CI/MI Licensing & Insurance CDLIS DOT Web Site IRP LSILSI A,E,F,H,J B,C,G,I,L D,K,N M MCES Client MIMI O PrePass Screening Service Provider Web Site PrePass Service Center Wisconsin Commercial Vehicle Administrative Systems MIMI CVIEW MIMI

61. Issue New Oversize/Overweight Permit 4/19/2001 Wisconsin Roadside Systems Carrier Systems Credentialing System (e.g., CAT) CVISN Core Infrastructure Systems (National/Regional) NCIC / NLETS IRP Clearinghouse IFTA Clearinghouse NMVTIS MCMIS SAFER Compliance Review (e.g., CAPRI) Service Providers Internet Tools (e.g. Browser) Other Carrier Systems Transponder Carrier Commercial Vehicle CI/MI Licensing & Insurance CDLIS DOT Web Site DMV Revenue MCES Client MIMI PrePass Screening OSOW LSILSI G C,D,G,H I B,C,D,E,F,G H A,E,F Service Provider Web Site PrePass Service Center Wisconsin Commercial Vehicle Administrative Systems MIMI MIMI CVIEW

62. Screen Vehicles / Record Inspections & Report to SAFER 4/23/2001 Wisconsin Roadside Systems Carrier Systems Credentialing System (e.g., CAT) CVISN Core Infrastructure Systems (National/Regional) NCIC / NLETS IRP Clearinghouse IFTA Clearinghouse NMVTIS MCMIS SAFER Compliance Review (e.g., CAPRI) Service Providers Internet Tools (e.g. Browser) Other Carrier Systems Transponder Carrier Commercial Vehicle Licensing & Insurance CDLIS CVIEW MCES Client PrePass Screening CI/MI MCES DOJ Msg Switch A,B E Wisconsin Commercial Vehicle Administration Systems LSILSI H,K J C F,G D L PrePass Service Center SAFETYNET2000 I M MIMI MIMI MIMI LSILSI MIMI

63. Key Issues CVIEW and SAFER Interface Specifications EDI vs. XML – we will attempt to decouple and defer development of these pieces Polk COVERSnet software – standards used and available functions Electronic funds transfer and credit card acceptance

64. Key Issues State Requirements State privacy concerns and conflict with open records – debate in legislature Biennial budget process – money Technology Management Council prioritizes projects – resources Ability to read non-PrePass transponders would be dependent upon money and resources Conflict between modal and non-modal divisions

65. Key Issues PrePass connections to state systems National ITS Architecture vs. CVISN Architecture Funding requirements Uniform Roadside Architecture

66.  Thirty minute presentation Friday morning at 8:00  Bring comments and questions

67. Uniform Roadside Architecture National CVISN Data Landscape (4 States Only) LA IFTA System LA IRP Registration System WI IFTA System WI IRP Registration System WI MCSAP Inspection System LA Roadside MS Roadside MS MCSAP Inspection System MS IRP Registration System MS IFTA System FL Roadside FL IRP Registration System FL IFTA System Goal: CVISN data moves from every legacy system to every roadside automatically, on time, and in a usable format. WI Roadside

68. Uniform Roadside Architecture Absence of Any Architecture MS MCSAP Inspection System LA IFTA System WI Snapshot Database LA IRP Registration System WI IFTA System WI IRP Registration System WI MCSAP Inspection System WI Roadside LA Snapshot Database LA Roadside MS Snapshot Database MS Roadside MS IRP Registration System MS IFTA System FL Roadside FL IRP Registration System FL Snapshot Database FL IFTA System Complexity is out of control

69. Uniform Roadside Architecure CVISN Level 1 Architecture SAFER WI CVIEW WI Roadside WI MCSAP Inspection System WI IFTA System WI IRP System FL CVIEW FL Roadside FL IFTA System FL IRP System LA CVIEW LA Roadside LA IFTA System LA IRP System MS CVIEW MS Roadside MS MCSAP Inspection System MS IFTA System MS IRP System Complexity is isolated and manageable Legacy systems are plug-and-play States are plug-and-play Flow of standardized snapshots SAFER Databases

70. Uniform Roadside Architecture Typical Two Vendor Roadside WIM Sensors ASPEN equivalent PrePass Database PrePass Random TID (from truck) Combine Lane Arrows VIN (eventually) To truck receiver PrePass Computer IRD Display WIM result (red/green) Snapshot History (PIQ) WIM Random Combine IRD Computer Vehicle Detector Loops PrePass Display Combo result (red/green) Combine ROC Screening Computer Combo result (red/green) PrePass result (red/green) WIM details Combo result (red/green) Combo result (red/green) + WIM details Combo result (red/green) + WIM details State CVIEW New MCSAP Inspection ROC Display Re-emergence of complexity Synchronization between vendors required for both evaluation and notification Multiple displays/keyboards in scale house Maintainability and extensibility concerns

71. Uniform Roadside Architecture Open Architecture Vehicle detector loops Unified Display ROC Screening Computer TID (vehicle, possibly driver) Standard messages To truck receiver Proprietary Details Standard messages Any Sensor Vendor’s Device Computer Notifier Device Computer To lane signals Databases: Snapshot, Summary, Parameters, Event log To VMS Standard messages Proprietary Details (Driver sees standard messages.) Operator commands (e.g., random %) State CVIEW ASPEN equivalent Axle weights Complexity is isolated and manageable Devices are plug-and-play ROC tracks vehicles and matches events Driver does not receive conflicting messages ROC routes messages between devices ROC protects sensitive data Maintainable and extensible (possibly to other ITS venues) Devices are like Legacy Systems Device computers are like CVIEWs ROC is like SAFER

72. Uniform Roadside Architecture Is It Worth Pursuing? Is URA appealing from a technical point of view? What impact would adoption of URA have on stakeholders? Which forums would be appropriate for considering URA and developing specific standards? ITS America? AASHTO? CVISN level two requirements? Other? Thirty minute presentation Friday morning at 8:00 Bring comments and questions