# Presentation: 852894

## Florida CVISN Top-Level Design

**Florida CVISN ****Top-Level Design**

## Florida CVISN Top-Level Design Presentation Outline

**Program Organization**
**CVISN Task Team**
**Initial Projects**
**Florida Exceptions to CVISN COACH, Part 1**
**Florida System Interface Standards**
**Network Template**
**Summary of New Systems**
**Top-Level System Designs**
- CVIEW
- Roadside Safety
- Mainline Screening
- Agriculture/Bill of Lading Screening
- IFTA Processing
- IRP Processing
- Oversize/Overweight Permit Processing

## Florida CVISN Top-Level Design Presentation Outline (continued)

**Phase Charts**
**System Testing**
**Major Outstanding Issues**

## Florida CVISN Top-Level Design

**Florida CVISN ****Top-Level Design**

**Program Organization ****and CVISN Task Team**

## Florida State Government AgenciesSupporting CVISN 

## Florida CVISN Program Organization

## Florida CVISNTask Team

**Department of Agriculture and Consumer Services (DACS)**
- Joe Martelli
- Captain Roger Pittman
**Department of Highway Safety and Motor Vehicles (DHSMV)**
- Carl Ford
- David Helton
- Judy Johnson
- Randy Lencyzk
**Department of Revenue (DOR)**
- Jim Gowen
- Hugh Stephens
**Department of Transportation (DOT)**
- Mike Akridge (chair)
- Frank Day
- Captain Marcel Tart

## Florida CVISN Task Team (continued)

**State Technology Office (STO)**
- Paul Grimes
**Florida Highway Patrol**
- Major Kevin Guidry
**Federal Motor Carrier Safety Administration (FMCSA)**
- Richard Gerke
**Florida Trucking Association (FTA)**
- Charles Brantley
**Landstar System, Inc.**
- Dianna White
**McKenzie Tank Lines**
- Jim Kennedy
**Rountree Transport and Rigging**
- Tom Runck
**Watkins Motor Lines**
- Tommy Thomas

## Florida CVISN Top-Level Design

**Florida CVISN ****Top-Level Design**

**Initial Projects**

## Florida CVISN Program Projects – Carrier  Services

**Compliance Help Desk/Service Representative**

- Provide a single point of contact in state government for CVO regulatory policy and procedure information.

- Objective To Be Met
- 1. Streamline or eliminate outdated or inefficient business and enforcement processes.
- 2. Provide one interaction or point of contact in the state for regulatory information.

## Florida CVISN Program Projects – Credentialing (1 of 3)

**Feasibility Study of Electronic Credentialing Needs  **

- Conduct a high-level assessment of requirements for supporting the on-line application for and receipt of CVO credentials in Florida.

- Objective To Be Met
- 1.  Reduce the paperwork and time spent on compliance activities that can be cost-effectively automated.
- 2. Streamline or eliminate outdated or inefficient business and enforcement processes.

**Electronic Payment Options **

- Explore electronic payment options for electronic credentials in Florida.

- Objective To Be Met
- 1.  Reduce the paperwork and time spent on compliance activities that can be cost-effectively automated.
- 2. Streamline or eliminate outdated or inefficient business and enforcement processes.

## Florida CVISN Program Projects – Credentialing (2 of 3)

**Automated Routing and Permitting Software Design and Development**

- Develop software to support the automated processing and issuance of oversize and overweight permits in Florida.

- Objective To Be Met
- 1.  Reduce the paperwork and time spent on compliance activities that can be cost-effectively automated.
- 2. Streamline or eliminate outdated or inefficient business and enforcement processes.
- 3. Improve highway safety.

**Electronic Credentialing Software Design and Development**

- Develop software to support paperless business transactions between the Department of Highway Safety and Motor Vehicles and motor carriers in Florida.

- Objective To Be Met
- 1.  Reduce the paperwork and time spent on compliance activities that can be cost-effectively automated.
- 2. Streamline or eliminate outdated or inefficient business and enforcement processes.

## Florida CVISN Program Projects – Credentialing (3 of 3)

**IFTA Clearinghouse**

- Project will develop the software for connecting to the IFTA Clearinghouse.

- Objective To Be Met
- 1.  Reduce the paperwork and time spent on compliance activities that can be cost-effectively automated.
- 2. Streamline or eliminate outdated or inefficient business and enforcement processes.
- 3. Promote interoperability of screening systems and other technical com-ponents and systems.

## Florida CVISN Program Projects – Electronic Screening

**Electronic Screening at Agricultural Inspection Stations**

- Deploy electronic screening at agricultural inspection stations in Florida based on clearances for the Agricultural Vehicle Inspection Program and the collection of use tax on out-of-state merchandise purchases.

- Objective To Be Met
- 1.  Reduce the paperwork and time spent on compliance activities that can be cost-effectively automated.
- 2. Promote interoperability of screening systems and other technical components and systems.
- 3. Improve highway safety.

**Electronic Screening at Weigh Stations**

- Deploy PrePass electronic screening to allow safe and compliant carriers to bypass weigh stations

- Objective To Be Met
- 1.  Reduce the paperwork and time spent on compliance activities that can be cost-effectively automated.
- 2. Promote interoperability of screening systems and other technical components and systems.
- 3. Improve highway safety.

## Florida CVISN Program Projects – Safety Information Exchange

**Information Systems Inventory**
- (This information is an input to the CVIEW design and development process)

- Conduct a detailed inventory of Florida’s CVO-related hardware and software.

- Objective To Be Met
- 1.  Network information systems to ensure timely interagency communication and critical data sharing.
- 2.  Streamline or eliminate outdated or inefficient business and enforcement processes.
- 3. Network information systems to ensure timely interagency communication and critical data sharing.
- 4. Promote interoperability of screening systems and other technical components and systems.

**Networked Information Systems Design and Development**
- (This information is an input to the CVIEW design and development process)

- Develop a system for the electronic interchange of information among state agencies and between deskside and roadside systems.

- Objective To Be Met
- 1.  Network information systems to ensure timely interagency communication and critical data sharing.
- 2.  Streamline or eliminate outdated or inefficient business and enforcement processes.
- 3. Network information systems to ensure timely interagency communication and critical data sharing.

## Florida CVISN Top-Level Design

**Florida CVISN ****Top-Level Design**

**Florida Exceptions to ****CVISN COACH, Part 1**

## Florida Exceptions to COACH, Part 1

**Florida commits fully to the ITS/CVO Guiding Principles with the following exceptions:**
- CVISN Architecture Principle #4—A jurisdiction shall have and maintain **ownership of any **data collected by any agent on its behalf.
- Florida will maintain ownership of all data except for the screening data collected by PrePass
- Roadside Operations Principle #2—Jurisdictions will support CVO roadside operations programs with **timely, current, accurate and verifiable electronic information**, making it unnecessary for properly equipped vehicles to carry paper credentials.
- DHSMV is reviewing the statutory requirement for paper credentials (e.g. IRP cab cards) to be carried on vehicles (320.0605, F.S.)

## Florida Exceptions to COACH, Part 1

**Florida commits fully to the ITS/CVO Interoperability Guiding Principles with the following exceptions:**
- General Principle #7—Information systems supporting electronic screening, credentials administration, and safety assurance will use:
- US DOT numbers for the identification of both interstate and intrastate motor carriers.
- Florida currently is reviewing whether modifications are required to DHSMV database to capture intrastate data.

## Florida Exceptions to COACH, Part 1

- Hardware Principle #8—Commercial vehicle operators will be able to use one transponder for power unit to roadside communications in support of multiple applications including electronic screening, safety assurance, fleet and asset management, tolls, parking, and other transactions processes.
- Interoperability with toll facilities currently is not possible but is a long-term goal.
- Program Principle #28—A jurisdiction will make a motor carrier’s DSRC transponder unique identifier available to another jurisdiction upon written request and authorization by the motor carrier.
- PrePass does not share its customers’ DSRC transponder unique identifiers.

## Florida Exceptions to COACH, Part 1

**Florida commits fully to the State Institutional Framework with the following exceptions:**
- #1—The State has contacted or has plans to contact State and local transportation officials to explore potential joint use of transponders to ensure integration among multiple applications (i.e. CVO, toll, traffic probes, parking management, etc.)
- Interoperability with PrePass transponders will be addressed later.
- #6—Appropriate and sufficient staff, equipment, and State and private funding are available to carry out the deployment of CVISN and ITS/CVO services.  The CVISN project has sufficient priority.
- CVISN projects are competing for priority among DHSMV projects

## Florida Exceptions to COACH, Part 1

- #21—The legislature provides adequate resources to support an active ITS/CVO program and deployment of the ITS/CVO services.
- Funding is dependant on work program and legislative budget and therefore funding cannot be guaranteed.
- #26—Effective procurement plans and processes are in place to acquire services and equipment needed to support the CVISN project, and the CVISN team is aware of constraints the processes impose.
- All agencies have procurement mechanisms. However, because procurement depends on funding availability, plans are unstable.

## Florida Exceptions to COACH, Part 1

**Florida commits fully to the General Operational Concepts for Level 1 with the following exception:**
- Item #13—The Fair Information Principle for ITS/CVO will be implemented using a combination of policies, procedures, technology, and training.  Stakeholders will be included in the discussions of the techniques to be used to implement the principles.
- DOR has restrictions on the disclosure of information.

## Florida Exceptions to COACH, Part 1

**Florida commits fully to the General State System Design Requirements for Level 1 without exception.**
**Florida commits fully to the CV Administration Operational Concepts for Level 1 with no exceptions.**
**Florida commits fully to the CV Administration Systems Design Requirements Checklist for Level 1 with no exceptions.**

## Florida Exceptions to COACH, Part 1

**Florida commits fully to the Electronic Screening Operational Concepts with the following note:**
- Item #3—Electronic screening is provided for vehicles equipped with FHWA-specified DSRC transponders.
- Florida notes that this can only take place if the transponder has a recall button to meet PrePass standards.

## Florida CVISN Top-Level Design

**Florida CVISN ****Top-Level Design**

**Florida System ****Interface Standards**

## Top-Level RequirementsCOACH, Part 4

**Florida commits fully to the following standard interfaces: ***(Note--These are the supported interfaces, not exceptions)*
- EDI-D
- State IFTA Registration to/from IFTA Clearinghouse
- EDI-E
- Connectivity between SAFER and CVIEW
- EDI-J
- IFTA or IRP Clearinghouse to SAFER
- EDI-K
- IFTA Clearinghouse to State IFTA Tax Processing System
- EDI-L
- CI to Credential Web Site
- EDI-O
- Citation & Accident to SafetyNet 2000 (via SDM)

## Top-Level RequirementsCOACH, Part 4

- EDI-P
- Receiver of 285 to sender of 285
- Applicable only where EDI is used.
- EDI-Q
- State IFTA Tax Processing System to CI
- EDI-V
- All EDI-receiving systems to all EDI-sending systems
- EDI-X
- Florida will use existing connectivity between law enforcement users and SAFER.
- DSRC
- Transponders for communication between electronic screening operations and vehicle
- PrePass is responsible for all DSRC interfaces
- DSRC-A
- Transponder to Screening/Driver Comm.

## Top-Level RequirementsCOACH, Part 4

- DSRC-B, E, F, G, H
- Transponder or Screening/Driver Comm. To Screening/Driver Comm. or Transponder
- AFF-A
- SAFER to ASPEN and ASPEN to SAFER
- AFF-B
- ASPEN to SAFER and SAFER to ASPEN
- AFF-C
- SAFER to/from SAFETYNET 2000
- AFF-D
- SAFETYNET 2000 to MCMIS and MCMIS to SAFETYNET 2000 (via SDM)
- AFF-E
- ASPEN to SAFETYNET 2000 (via SDM)

## Top-Level RequirementsCOACH, Part 4

- AFF-G
- ASPEN to SAFER
- AFF-H
- ASPEN to SAFETYNET 2000 (via SDM)
- INT-A
- Internet tools to Web Site and Web Site to Internet Tools
- INT-B
- Internet Tools to Web Site
- INT-C
- Web Site to Internet Tools
- INT-F
- IFTA Clearinghouse to State IFTA Tax Processing System
- INT-G
- Internet Tools to E-Screening Enrollment

## Top-Level RequirementsCOACH, Part 4

- CIA-A
- State IRP to IRP Clearinghouse
- CIA-B
- IRP Clearinghouse to State IRP
- CIA-C
- SAFER to ASPEN and ASPEN to SAFER
- CIA-D
- ASPEN to SAFER and SAFER to ASPEN
- CIA-E
- ASPEN to SAFETYNET 2000 (via SDM)
- CIA-F
- ASPEN to SAFETYNET 2000
- CIA-G
- SAFETYNET 2000 to MCMIS and MCMIS to SAFETYNET 2000 (via SDM)

## Top-Level RequirementsCOACH, Part 4

- CIA-J
- CDLIS to SAFER
- CIA-K
- SAFER to CDLIS
- CIA-O
- Sensor Comm to/from Screening
- CIA-P
- Roadside Operations to/from Screening
- CIA-Q
- Roadside Operations to/from Sensor/Driver Comm

## Top-Level RequirementsCOACH, Part 4

**Florida commits fully to the following standard data definitions and Identifier Segments:**
- Motor Carrier
- Vehicle
- Transponder
- Trip
- Updated OS/OW system, however, may require a different methodology for identifying trips/shipments.

## Top-Level Requirements Florida Network Template

- Screen
- Enroll

**Top-Level Requirements ****Florida Network Template**

- Department Highway Safety and Motor Vehicles

- IRP
- IFTA
- Reg

- Firewall

- Titling

- Driver
- License

- CDRS

- CI

- Web

- E-Mail

- Department of Transportation

- Firewall

- Motor Carrier Compliance Office

- Firewall

*DHSMV:*
*IRP / IFTA / Reg -- Moving toward a single Windows NT/Oracle system. Phasing out Unix. CICS application to access Oracle. E-Mail -- Groupwise via CAPMAN. Clearinghouses -- Connect via CAPMAN to AAMVANet.*
*DOT / MCCO:*
*E-Mail -- Moving to Lotus Notes.*
*Frame Relay connects HQ, field/district offices, some weigh stations (others via RAS). FR via CAPMAN also connects other resources like DHSMV, FDLE and FHWA. Officers on the road connect via CDPD.*
*Mix of Windows NT and Novell. Migrating to WinNT only. MCCO has no database servers although DOT uses Oracle. Inspection data stored (in Foxpro tables??) on server.*
*Permits:*
*No automated system, but permits are stored locally on a Windows NT/Oracle system.*
*DOR:*
*No automated system for storing electronic BOL status for enrolled carriers. Firewall only opened for the time necessary to push data out.*
*DCAS:*
*Most inspection stations are not networked or computerized. New systems will be created to handle roadside screening and corresponding enrollment. E-BOL statuses to be exchanged with DOR via CVIEW.*
*Capitol City Metropolitan Area Network:*
*Provides access to Internet and other non-state resources, e.g. AAMVANet. CAPMAN consists of fiber cable and routers to provide a backbone for connecting (eventually) all systems in the Tallahassee area. May one day hook into a state-wide fiber network (FFN) to connect everything.*

- “Dirty” Web Server

- HQ

- District
- Offices

- Tolls,
- Tpike,
- Whouse

- Field
- Offices

- Weigh
- Stations

- Frame Relay

- Permits Office

- OS/OW
- Permits

- Auto
- Routing

- CVIEW

- E-Mail

- Motor Carriers

- Web
- Browser

- CAT

- Dept of Law Enforcement

- FCIC

- Firewall

- Frame Relay

- Frame Relay

- Dept of Revenue

- Firewall

- Firewall

- Elec
- BOL
- Status

- Screen
- System

- Dept of Banking & Finance

- SAMAS

- Firewall

- Insp
- Stations

- CVISN Core Infrastructure Systems

- NCIC

- NLETS

- IRP
- Clearing
- house

- IFTA
- Clearing
- house

- MCMIS

- CDLIS

- L&I

- SAFER

- E-Mail

- NMVTIS

- CAPMAN to AAMVANet SNA

- CAPMAN

- Internet

- Firewall

- EDI in E-mail via
- Internet or VPN

- E-Mail

- PrePass
- Enroll,
- Screen,
- Host

- ASPEN / CDPD

- CAPMAN to AAMVANet SNA

## Top-Level Requirements Summary of New Systems

**CVIEW**
- CVIEW will receive and store information from state and federal systems and provide information to state and federal systems.
**Safety Information Exchange**
- None
**Electronic Screening**
- CVIEW to PrePass for Enrollment and Status Updates
- DOR/Agricultural Screening
- PrePass or In-House
- Enrollment Status Stored in CVIEW

## Top-Level Requirements Summary of New Systems (continued)

**Credential Administration**
- IFTA and IRP
- Web Interface/Application (if not provided by Uniface 7.26)
- Link to “MyFlorida.com”
- CVISN-wide electronic payment system
- Connection to Clearinghouse
- Automated system to download and incorporate quarterly tax rates for all jurisdictions
- Oversize/Overweight Permitting
- Web server to host and screen application
- Routing review system to approve routes
- Manually introduced impediments database to  store temporary restrictions (construction, emergency situations, etc.)
- CVISN-wide electronic payment system

## Florida CVISNTop-Level Design:CVIEW Connectivity to Systems Within Florida

## CVIEW Connectivity to Systems Within Florida:Operational Scenario

**Receive data from state systems**
- Non-relational state systems export data to flat files and transfer these files (via FTP or network copy) to the CVIEW server
- Relational state systems connect to the CVIEW database and transfer data to input tables
- Depending on CVIEW procurement strategy, EDI may be substituted
- CVIEW receives and parses data and updates individual carrier / vehicle snapshots with new information
**Provide data to state systems**
- Send carrier / vehicle snapshot information proactively (via timed data transfer) or reactively (in response to specific query) to state systems

**Notes:**
For credentials-related scenarios, it is often convenient to think of the steps in the operational scenario in three subgroups.
On this and subsequent pages, the groups are highlighted with the colors shown:
Yellow steps support the interaction between the state and the applicant (steps 1-12 and 17-20),
Lavender cross-hatched steps correspond to the maintenance of snapshots (steps 13-16 and 21-24),
Blue steps involve the interaction between the state and the core infrastructure systems (in this case, IFTA Clearinghouse) (steps A-D).
The slide show will skip to the thread diagram.  We will walk through the steps of the operational scenario [use overhead projector to show the list].
In the breakout session, you’ll develop operational scenario steps and a thread diagram for how you intend to automate this same IFTA process.  
Keep the scenario steps at about the same level of detail as in this example.  Each step should “name” the information being exchanged and what format (e.g., EDI TS 286) will be used for the exchange.  Also describe, at a high level, the processing performed.

## CVIEW Connectivity to Systems Within Florida: Functional Thread Diagram

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**CV Info Exchange**
**Window (CVIEW)**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**OS/OW**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**DOR/Agricultural**
**Screening**
**Enrollment**

**SunPass**
**Enrollment**

**DACS/DOR**
**Bill of Lading**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**PrePass Host**

**HVUT**

**STOLEN**

**L**
**S**
**I**

**L**
**M**

**1**

**2**

**3**

**4**

**5**

**6**

**7**

**8**

**Roadway**
**Characteristics**
**Inventory (RCI)**

## CVIEW Connectivity to Systems Within Florida:System Interfaces

**CVIEW Connectivity to Systems Within Florida:****System Interfaces**

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**SunPass**
**Enrollment**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**CV Info Exchange**
**Window (CVIEW)**

**DACS/DOR**
**Bill of Lading**

**OS/OW**

- 2 or 3

- 2 or 3

- 3

- 3

- ?

**DOR/Agricultural**
**Screening**
**Enrollment**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**PrePass Host**

**HVUT**

**STOLEN**

**L**
**S**
**I**

**L**
**M**

**DOR**
**E-Bill of Lading**

- 2 or 3

- 2 or 3

**Connectivity Type**
**1. EDI**
**2. Flat File**
**3. DB Connection**
**4. HTTP**
**5. ASPEN**
**6. Proprietary**
**7. DSRC**
**?. Unknown**

- 2 or 3

**Roadway**
**Characteristics**
**Inventory (RCI)**

## CVIEW Connectivity to Systems Within Florida:Modifications Required to Existing Systems

**An Oracle PL/SQL-based legacy system interface (LSI) must be installed in the CDRS to support sending data to CVIEW**
**If the IRP, IFTA or Vehicle Registration systems require CVIEW data, they must be modified to access the CVIEW database (using views or stored procedures)**
**The intrastate carrier registration system must implement a SQL or flat file interface with CVIEW**
**The citation system must implement a SQL or flat file interface with CVIEW**
**Weigh station operations must be modified to send queries to CVIEW and receive/display the results**

## CVIEW Connectivity to Systems Within Florida:Functions to be Performed by New Systems

**CVIEW will receive and store information from state systems and provide information to state systems**
**Each state system will interact with CVIEW through a legacy system interface (LSI)**
**The Credentialing Interface or Credential Web Interface will manage credential applications received electronically. The CI also will deliver information on completed applications and the credentials issued to CVIEW**

## CVIEW Connectivity to Systems Within Florida:Top-Level Physical Design

_**System**__**	**__** **_**	****	****	****	****	**_**Function**_
- CVIEW                           			Receive and store information from					state systems, responds to queries
- CDRS                      			Repository for IRP, IFTA and					Vehicle Reg data, send data to CVIEW
- OS/OW                            			Manage / store permits, send data					to CVIEW
- Credentialing or Web Interface               		Manage electronic applications, send					new credential data to CVIEW
- E-Screening Enrollment            		Query CVIEW when enrolling new					carriers / vehicles
- Ag Screening Enrollment 			Send enrollment status updates to 					CVIEW
- Weigh Station Operations			Send queries to CVIEW and display					data
- Citation System 				Send data to CVIEW

**Allocation of Functions to Computers**

## CVIEW Connectivity to Systems Within Florida:Top-Level Physical Design

**Description of System/Network Capabilities and Changes**

**CVIEW Connectivity to Systems Within Florida:****Top-Level Physical Design**

**CVIEW****	****	****	****Buy / Build****	****	****     M****	****    ****	****   3**
**LSIs****	****	****	****Buy / Build****	****	****   L - M****	****	****3 - 6**
**	****	****	****(one for each system**
**	****	****	****that communicates**
**	****	****	****with CVIEW)**

## Select a CVIEW implementation strategy
Select a CI or Web implementation strategy
Select an OS/OW implementation strategy
Select an Agricultural Screening strategy
Specify content, format and timing for the information exchange with each state system, i.e. LSIs
Determine parameters to be used for queries, particularly from weigh stations
Determine whether citation data must be stored in CVIEW
Identify keys in each system for matching data to CVIEW snapshots

**Select a CI or Web implementation strategy**
**Select an OS/OW implementation strategy**
**Select an Agricultural Screening strategy**
**Specify content, format and timing for the information exchange with each state system, i.e. LSIs**
**Determine parameters to be used for queries, particularly from weigh stations**
**Determine whether citation data must be stored in CVIEW**
**Identify keys in each system for matching data to CVIEW snapshots**

**CVIEW Connectivity to Systems Within Florida:****Issues**

## Florida CVISNTop-Level Design:CVIEW Connectivity to Systems Outside Florida

## CVIEW Connectivity to Systems Outside Florida:Operational Scenario

**Receive data from federal / third-party systems**
- SAFER sends EDI files attached to e-mail messages
- PrePass sends flat files attached to e-mail messages
- Other federal systems undefined at this time (see issues)
- CVIEW receives and parses data and updates individual carrier / vehicle snapshots with new information
**Provide data to federal / third-party systems**
- CVIEW sends to SAFER EDI files attached to e-mail messages
- CVIEW sends to PrePass flat files attached to e-mail messages
- Other federal systems undefined at this time (see issues)

**Notes:**
For credentials-related scenarios, it is often convenient to think of the steps in the operational scenario in three subgroups.
On this and subsequent pages, the groups are highlighted with the colors shown:
Yellow steps support the interaction between the state and the applicant (steps 1-12 and 17-20),
Lavender cross-hatched steps correspond to the maintenance of snapshots (steps 13-16 and 21-24),
Blue steps involve the interaction between the state and the core infrastructure systems (in this case, IFTA Clearinghouse) (steps A-D).
The slide show will skip to the thread diagram.  We will walk through the steps of the operational scenario [use overhead projector to show the list].
In the breakout session, you’ll develop operational scenario steps and a thread diagram for how you intend to automate this same IFTA process.  
Keep the scenario steps at about the same level of detail as in this example.  Each step should “name” the information being exchanged and what format (e.g., EDI TS 286) will be used for the exchange.  Also describe, at a high level, the processing performed.

## CVIEW Connectivity to Systems Outside Florida: Functional Thread Diagram

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**CV Info Exchange**
**Window (CVIEW)**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**OS/OW**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**DOR/Agricultural**
**Screening**
**Enrollment**

**SunPass**
**Enrollment**

**DACS/DOR**
**Bill of Lading**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**PrePass Host**

**HVUT**

**STOLEN**

**L**
**S**
**I**

**L**
**M**

**1**

**3**

**2A**

**2B**

**2C**

**2D**

**Roadway**
**Characteristics**
**Inventory (RCI)**

## CVIEW Connectivity to Systems Outside Florida: System Interfaces

**CVIEW Connectivity to Systems Outside Florida: ****System Interfaces**

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**SunPass**
**Enrollment**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**CV Info Exchange**
**Window (CVIEW)**

**DACS/DOR**
**Bill of Lading**

**OS/OW**

**DOR/Agricultural**
**Screening**
**Enrollment**

- ?

- 2

***Depends on CVIEW solution chosen by Florida**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**PrePass Host**

**HVUT**

**STOLEN**

**L**
**S**
**I**

**L**
**M**

**DOR**
**E-Bill of Lading**

- ?

- ?

- ?

- 1

**Connectivity Type**
**1. EDI**
**2. Flat File**
**3. DB Connection**
**4. HTTP**
**5. ASPEN**
**6. Proprietary**
**7. DSRC**
**?. Unknown**

**Roadway**
**Characteristics**
**Inventory (RCI)**

## CVIEW Connectivity to Systems Outside Florida: Modifications Required to Existing Systems

**SAFER must establish carrier and vehicle snapshot subscriptions based on Florida’s requirements**
**PrePass must query CVIEW for carrier and vehicle information and process the results during enrollment and when credential statuses change after enrollment**

## CVIEW Connectivity to Systems Outside Florida: Functions to be Performed by New Systems

**CVIEW will receive and store carrier and vehicle snapshots from SAFER. CVIEW will send carrier and vehicle snapshots to SAFER.**
**CVIEW may receive and store data from other federal systems (see issues)**
**CVIEW will respond to carrier and vehicle queries from PrePass. CVIEW will proactively inform PrePass of changes in credential status of enrolled carriers and vehicles.**

## CVIEW Connectivity to Systems Outside Florida: Top-Level Physical Design

**Allocation of Functions to Computers**

**	**_**System**__**	**__** **_**	****	****	**_**Function**_
- 	CVIEW                        	Receive and store information from federal				systems, send updates to SAFER, respond to				queries, proactively inform PrePass of changes				in credential status
-     	PrePass                		Query CVIEW for carrier and vehicle				snapshots, process snapshots from CVIEW
-                                     .                                                                .
- 	SAFER			Receive and store information from many				sources, including Florida.  Send updates via				 subscriptions.  Respond to queries.       Other Federal Systems		Unknown (see issues)

## CVIEW Connectivity to Systems Outside Florida: Top-Level Physical Design

**Description of System/Network Capabilities and Changes**

**CVIEW Connectivity to Systems Outside Florida: ****Top-Level Physical Design**

**CVIEW****	****	****	****         Buy / Build****	****	****     M****	****    ****	****   3**
**SAFER Interface****	****	****          Configure****	****	****   L - M****	****	****   3**
**PrePass Interface****	****          Configure****	****	****     L****	****	****   5**
**Other Federal Systems****	****         (See Issues)****	****     ?****	****	****   ?**

## Determine whether Florida needs to exchange data with other federal systems (CDLIS, NCIC/NLETS, STOLEN, HVUT). If so, determine whether these systems can exchange data and the content, format, timing and security of the exchange. 
Resolve SAFER connectivity issues -- IPSec through Florida firewall, specifications for subscriptions to receive SAFER data, specifications of data to be sent to SAFER and emerging non-EDI transfer options
Determine data to be sent to PrePass to support screening enrollment

**Resolve SAFER connectivity issues -- IPSec through Florida firewall, specifications for subscriptions to receive SAFER data, specifications of data to be sent to SAFER and emerging non-EDI transfer options**
**Determine data to be sent to PrePass to support screening enrollment**

**CVIEW Connectivity to Systems Outside Florida: ****Issues**

## Florida CVISNTop-Level Design:Roadside Safety

## Roadside Safety:Operational Scenario

- Electronically record and transmit roadside safety inspections to SAFER and MCMIS
- Query databases for CDL, credential, past inspections (using CDPD) and vehicle data

**Notes:**
For credentials-related scenarios, it is often convenient to think of the steps in the operational scenario in three subgroups.
On this and subsequent pages, the groups are highlighted with the colors shown:
Yellow steps support the interaction between the state and the applicant (steps 1-12 and 17-20),
Lavender cross-hatched steps correspond to the maintenance of snapshots (steps 13-16 and 21-24),
Blue steps involve the interaction between the state and the core infrastructure systems (in this case, IFTA Clearinghouse) (steps A-D).
The slide show will skip to the thread diagram.  We will walk through the steps of the operational scenario [use overhead projector to show the list].
In the breakout session, you’ll develop operational scenario steps and a thread diagram for how you intend to automate this same IFTA process.  
Keep the scenario steps at about the same level of detail as in this example.  Each step should “name” the information being exchanged and what format (e.g., EDI TS 286) will be used for the exchange.  Also describe, at a high level, the processing performed.

## Roadside Inspection:Functional Thread Diagram

**Roadside Inspection:****Functional Thread Diagram**

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**CV Info Exchange**
**Window (CVIEW)**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**OS/OW**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**DOR/Agricultural**
**Screening**
**Enrollment**

**SunPass**
**Enrollment**

**DACS/DOR**
**Bill of Lading**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Roadway**
**Characteristics**
**Inventory (RCI)**

**Central Data**
**Repos. (CDRS)**

**2**

**3**

**4**

**5**

**6**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**PrePass Host**

**HVUT**

**STOLEN**

**L**
**S**
**I**

**L**
**M**

**1**

**1**

**1**

## Previous Inspection Query:Functional Thread Diagram

**Previous Inspection Query:****Functional Thread Diagram**

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**CV Info Exchange**
**Window (CVIEW)**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**OS/OW**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**DOR/Agricultural**
**Screening**
**Enrollment**

**SunPass**
**Enrollment**

**DACS/DOR**
**Bill of Lading**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Roadway**
**Characteristics**
**Inventory (RCI)**

**Central Data**
**Repos. (CDRS)**

**1**

**2**

**3**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**PrePass Host**

**HVUT**

**STOLEN**

**L**
**S**
**I**

**L**
**M**

## Roadside Safety:System Interfaces

**CV Info Exchange**
**Window (CVIEW)**

**DOR  **
**E-Bill of Lading**

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**SunPass**
**Enrollment**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**DACS/DOR**
**Bill of Lading**

**OS/OW**

**DOR/Agricultural**
**Screening**
**Enrollment**

- 5

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**PrePass Host**

**HVUT**

**STOLEN**

**L**
**S**
**I**

**L**
**M**

- ?

- ?

**Connectivity Type**
- 1. EDI
- 2. Flat File
- 3. DB Connection
- 4. HTTP
- 5. ASPEN
- 6. Proprietary
- 7. DSRC
- ?. Unknown

**Roadside Safety:****System Interfaces**

- ?

**Roadway**
**Characteristics**
**Inventory (RCI)**

## Roadside Safety: Modifications Required to Existing Systems

**Aspen 2.0 will be deployed by August 2001**
**Transition to Safetynet 2000 **
**Complete installation of CDPD for SAFER Connectivity**
- Land-lines will be used where CDPD is unavailable

## Roadside Safety: Functions to be Performed by New Systems

**None**

## Roadside Safety: Top-Level Physical Design

**	**_**System:**_**	****	****	****     **_**Function:**_
**       ****Roadside laptop****	****	****           ****	****Capture vehicle****	****	****	****	****	****	****inspection data****	****	****	****	****	****Aspen/PIQ**
**             ****CVIEW****	****	****	**** ****	****Serves as statewide****	****	****	****	****	****repository for credential****	****	****	****	****	****data.  May be queried by****	****	****	****	****	****roadside inspectors    **

**Allocation of Functions to Computers**

## Roadside Safety: Top-Level Physical Design

**Description of System/Network Capabilities and Changes**

**Roadside Safety: ****Top-Level Physical Design**

**Deploy Aspen 2.0               Upgrade Software****	****     L****	****    ****	****   1**
**SAFETYNET 2000****	****  Upgrade Software****	****     L****	****	****   2***
**CDPD Connectivity****	****Complete Deployment****	****     H****	****	****   5**
**** Currently planned to be completed ahead of schedule***

## Are inspections sent directly to SAFER or are they sent to CVIEW then to SAFER?
Completion of statewide CDPD accessibility is hampered by incomplete infrastructure.
Will PIQ continued to be queried through SAFER or will it now be queried through CVIEW?

**Completion of statewide CDPD accessibility is hampered by incomplete infrastructure.**
**Will PIQ continued to be queried through SAFER or will it now be queried through CVIEW?**

**Roadside Safety: ****Issues**

## Florida CVISNTop-Level Design: Data Verification to Support Enrollment in Mainline Electronic Screening Program

##  Data Verification to Support Enrollment in Mainline Electronic Screening Program:Operational Scenario

**Query data stored in Florida CVIEW and SAFER to support the enrollment of Florida carriers in the mainline electronic screening program.**

## Data Verification to Support Enrollment in Mainline Electronic Screening Program: Functional Thread Diagram

**Data Verification to Support Enrollment ****in Mainline Electronic Screening Program:**** Functional Thread Diagram**

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**CV Info Exchange**
**Window (CVIEW)**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**OS/OW**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**DOR/Agricultural**
**Screening**
**Enrollment**

**SunPass**
**Enrollment**

**DACS/DOR**
**Bill of Lading**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**PrePass CVIEW**

**HVUT**

**L**
**S**
**I**

**L**
**M**

**STOLEN**

**A, C**

**E**

**D**

**B**

**Roadway**
**Characteristics**
**Inventory (RCI)**

## Data Verification to Support Enrollment in Mainline Electronic Screening Program: System Interfaces

**Data Verification to Support Enrollment ****in Mainline Electronic Screening Program:**** System Interfaces**

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**CV Info Exchange**
**Window (CVIEW)**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**OS/OW**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**DOR/Agricultural**
**Screening**
**Enrollment**

**SunPass**
**Enrollment**

**DACS/DOR**
**Bill of Lading**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**PrePass CVIEW**

**HVUT**

**L**
**S**
**I**

**L**
**M**

**STOLEN**

**7**

**2**

**6**

**1**

**1**

**Connectivity Type**
- 1. EDI
- 2. Flat File
- 3. DB Connection
- 4. HTTP
- 5. ASPEN
- 6. Proprietary
- 7. DSRC
- ?. Unknown

**Roadway**
**Characteristics**
**Inventory (RCI)**

## Data Verification to Support Enrollment in Mainline Electronic Screening Program:Modifications Required to Existing Systems

**None **

## Data Verification to Support Enrollment in Mainline Electronic Screening Program:Functions to be Performed by New Systems

**State CVIEW**
- Allow State CVIEW query by PrePass for new enrollments, verifications (if allowed)
- Send carrier/vehicle event status updates to PrePass CVIEW for enrolled carriers

## Data Verification to Support Enrollment in Mainline Electronic Screening Program:Top-Level Physical Design

_**System:**_**	****	****	**_**Function:**_
**Prepass CVIEW/Host****	****	****	****Coordinates the collection of****	****	****	****	****	****carrier and vehicle data from FL****	****	****	****	****	****CVIEW and SAFER; makes the****	****	****	****	****	****screening decision based on FL****	****	****	****	****	****criteria**
**Roadside Computer****	****	****	****Stores the screening decision**
**CVIEW/SAFER****	****	****	****	****Provides vehicle and carrier data****	****	****	****	****	****to PrePass CVIEW to support****	****	****	****	****	****enrollment/screening decision**

**Allocation of Functions to Computers**

## Data Verification to Support Enrollment in Mainline Electronic Screening Program:Top-Level Physical Design

**Description of System/Network Capabilities and Changes**

**Data Verification to Support Enrollment ****in Mainline Electronic Screening Program:****Top-Level Physical Design**

**PrePass CVIEW Access        Set-up delivery of ****	****     M****	****	****   ****5****	****	****	****     carrier and vehicle****	****	****	****     data from FL CVIEW****	****	****	****      to PrePass CVIEW**

## CVIEW access
Origin of data to be shared with Prepass--What types of data will be sent from CVIEW, what types of data will be sent from SAFER.

**Origin of data to be shared with Prepass--What types of data will be sent from CVIEW, what types of data will be sent from SAFER.**

**Data Verification to Support Enrollment ****in Mainline Electronic Screening Program:****Issues**

## Florida CVISNTop-Level Design:Mainline Electronic Screening

## Mainline Electronic Screening:Operational Scenario

**Electronically screen and bypass vehicles of enrolled carriers past fixed inspection stations.**

**Notes:**
For credentials-related scenarios, it is often convenient to think of the steps in the operational scenario in three subgroups.
On this and subsequent pages, the groups are highlighted with the colors shown:
Yellow steps support the interaction between the state and the applicant (steps 1-12 and 17-20),
Lavender cross-hatched steps correspond to the maintenance of snapshots (steps 13-16 and 21-24),
Blue steps involve the interaction between the state and the core infrastructure systems (in this case, IFTA Clearinghouse) (steps A-D).
The slide show will skip to the thread diagram.  We will walk through the steps of the operational scenario [use overhead projector to show the list].
In the breakout session, you’ll develop operational scenario steps and a thread diagram for how you intend to automate this same IFTA process.  
Keep the scenario steps at about the same level of detail as in this example.  Each step should “name” the information being exchanged and what format (e.g., EDI TS 286) will be used for the exchange.  Also describe, at a high level, the processing performed.

## Mainline Electronic Screening: Functional Thread Diagram

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**CV Info Exchange**
**Window (CVIEW)**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**OS/OW**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**DOR/Agricultural**
**Screening**
**Enrollment**

**SunPass**
**Enrollment**

**DACS/DOR**
**Bill of Lading**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Roadway**
**Characteristics**
**Inventory (RCI)**

**Central Data**
**Repos. (CDRS)**

**A**

**B**

**C**

**1**

**2**

**3**

**3**

**4**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**PrePass Host**

**HVUT**

**STOLEN**

**L**
**S**
**I**

**L**
**M**

## Mainline Electronic Screening: System Interfaces

**DOR  **
**E-Bill of Lading**

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**SunPass**
**Enrollment**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**CV Info Exchange**
**Window (CVIEW)**

**Roadway**
**Characteristics**
**Inventory (RCI)**

**DACS/DOR**
**Bill of Lading**

**OS/OW**

**DOR/Agricultural**
**Screening**
**Enrollment**

- 6

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**PrePass Host**

**HVUT**

**STOLEN**

**L**
**S**
**I**

**L**
**M**

**Connectivity Type**
- 1. EDI
- 2. Flat File
- 3. DB Connection
- 4. HTTP
- 5. ASPEN
- 6. Proprietary
- 7. DSRC
- ?. Unknown

- 7

**Mainline Electronic Screening:**** System Interfaces**

**1**

**2**

## Mainline Electronic Screening:Modifications Required to Existing Systems

**None**

## Mainline Electronic Screening:Functions to be Performed by New Systems

**None **

## Mainline Electronic Screening:Top-Level Physical Design

**	**_**System:**_**	****	****	****	****   **_**Function:**_
**  ****PrePass CVIEW/Host****	****	****	****      Calculate screening****	****	****	****	****	****      decision and transmit it****	****	****	****	****	****      to roadside screening****	****	****	****	****	****      computer**
**     ****Roadside Computer****	****	****       ****	****      Store screening decision****	****	****	****	****	****      for transmission to****	****	****	****	****	****      transponder; Calculate****	****	****	****	****	****      random “pull-in”**
**       ****Transponder****	****	****	****      Store and transmit****	****	****	****	****	****      identifier; Receive and****	****	****	****	****	****      display the screening****	****	****	****	****	****      decision**

**Allocation of Functions to Computers**

## Mainline Electronic Screening:Top-Level Physical Design

**Description of System/Network Capabilities and Changes**

**Mainline Electronic Screening:****Top-Level Physical Design**

**Screening—Build 1****	****   Deploy PrePass****	****     L****	****	****   1****	****	****	****   at 10 sites **
**Screening—Build 2****	****   Deploy PrePass****	****     L****	****	****   2 ****	****	****	****   at a total of 17 sites **
**Screening—Build 3****	****   Deploy PrePass****	****     L****	****	****   4 **
**	****	****	****   ****at a total of 19 sites **
**Screening—Build 4****	****   Screen vehicles ****	****     L****	****	****   5****	****	****	****   electronically using****	****	****	****   carrier and vehicle ****	****	****	****   snapshots using CVIEW**

## Not screening using mainline WIM today
May add this capability long-term
Implementation of intrastate snapshot capability (Build 4) depends on CVIEW implementation schedule rather than on technology
Must decide if PrePass will have access to CVIEW
Must determine which data will be provided to PrePass through CVIEW and which data will be provided from other sources
Need to develop weight violation algorithm
Possibility of future mobile pre-screening 

- May add this capability long-term
**Implementation of intrastate snapshot capability (Build 4) depends on CVIEW implementation schedule rather than on technology**
**Must decide if PrePass will have access to CVIEW**
**Must determine which data will be provided to PrePass through CVIEW and which data will be provided from other sources**
**Need to develop weight violation algorithm**
**Possibility of future mobile pre-screening **

**Mainline Electronic Screening:****Issues**

## Florida CVISNTop-Level Design:Enrollment in Agriculture/Bill of Lading Electronic Screening Program

## Enrollment in Agriculture/Bill of Lading Electronic Screening Program:Operational Scenario

**Allow carriers to enroll in the Agriculture/Bill of Lading electronic screening program via the Web.  **

**Notes:**
For credentials-related scenarios, it is often convenient to think of the steps in the operational scenario in three subgroups.
On this and subsequent pages, the groups are highlighted with the colors shown:
Yellow steps support the interaction between the state and the applicant (steps 1-12 and 17-20),
Lavender cross-hatched steps correspond to the maintenance of snapshots (steps 13-16 and 21-24),
Blue steps involve the interaction between the state and the core infrastructure systems (in this case, IFTA Clearinghouse) (steps A-D).
The slide show will skip to the thread diagram.  We will walk through the steps of the operational scenario [use overhead projector to show the list].
In the breakout session, you’ll develop operational scenario steps and a thread diagram for how you intend to automate this same IFTA process.  
Keep the scenario steps at about the same level of detail as in this example.  Each step should “name” the information being exchanged and what format (e.g., EDI TS 286) will be used for the exchange.  Also describe, at a high level, the processing performed.

## Enrollment in Agriculture/Bill of Lading Electronic Screening Program:Functional Thread Diagram

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**CV Info Exchange**
**Window (CVIEW)**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**OS/OW**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**DOR/Agricultural**
**Screening**
**Enrollment**

**SunPass**
**Enrollment**

**DACS/DOR**
**Imaging**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Roadway**
**Characteristics**
**Inventory (RCI)**

**Central Data**
**Repos. (CDRS)**

**PrePass Host**

**HVUT**

**L**
**S**
**I**

**L**
**M**

**STOLEN**

**3**

**3**

**2**

**1**

**2**

**4**

## Enrollment in Agriculture/Bill of Lading Electronic Screening Program: System Interfaces

**Enrollment in Agriculture/****Bill of Lading Electronic Screening Program:**** System Interfaces**

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**CV Info Exchange**
**Window (CVIEW)**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**OS/OW**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**DOR/Agricultural**
**Screening**
**Enrollment**

**SunPass**
**Enrollment**

**DACS/DOR**
**Imaging**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Roadway**
**Characteristics**
**Inventory (RCI)**

**Central Data**
**Repos. (CDRS)**

**PrePass Host**

**HVUT**

**L**
**S**
**I**

**L**
**M**

**STOLEN**

**4**

**3**

**3**

**Connectivity Type**
- 1. EDI
- 2. Flat File
- 3. DB Connection
- 4. HTTP
- 5. ASPEN
- 6. Proprietary
- 7. DSRC
- ?. Unknown

## Enrollment in Agriculture/Bill of Lading Electronic Screening Program:Modifications Required to Existing Systems

**None **

## Enrollment in Agriculture/Bill of Lading Electronic Screening Program:Functions to be Performed by New Systems

**On-line application for enrollment**
**Link to “MyFlorida.com” **
**Record enrollment decisions and upload decisions to CVIEW **

## Enrollment in Agriculture/Bill of Lading Electronic Screening Program:Top-Level Physical Design

_**System:**_**	****	****	****	**_**Function:**_
- 	“MyFlorida.com” server			E-mail link
- 	TBD					On-line application
- 	DACS Server				Front and back end 						enrollment via web 						application.  Record						enrollment decisions.
- 	DOR Server				Front and back end 						enrollment via web 						application.  Record						enrollment decisions.

**Allocation of Functions to Computers**

## Enrollment in Agriculture/Bill of Lading Electronic Screening Program:Top-Level Physical Design

**Description of System/Network Capabilities and Changes**

**Enrollment in Agriculture/****Bill of Lading Electronic Screening Program:****Top-Level Physical Design**

**Presence on ****	****	****       Connectivity****	****	****    L****	****                  3****“MyFlorida.com”****	**
**Development of ****	****	****        Build new****	****	****   H****	****	****    4**
**on-line application**
**Development of ****	****	****        Build new****	****	****   H****	****	****    4****enrollment database**

## Develop and advertise manual enrollment process, which would be replaced by automated system later.
Develop a MOU with carriers to certify that their shipments typically do not involve agricultural products.
Review administrative rules to allow for suspension or revocation of program privileges. 
Interface with U.S. Customs Service and USDA to identify animal and food products shipped into Florida via airport or water port.
Develop “after-the-fact” tracking capability of international shipments.
Allow DACS to track where a potentially contaminated shipment went.
Allow for the electronic submission of plant and animal industry bills of lading.

**Develop a MOU with carriers to certify that their shipments typically do not involve agricultural products.**
**Review administrative rules to allow for suspension or revocation of program privileges. **
**Interface with U.S. Customs Service and USDA to identify animal and food products shipped into Florida via airport or water port.**
**Develop “after-the-fact” tracking capability of international shipments.**
- Allow DACS to track where a potentially contaminated shipment went.
**Allow for the electronic submission of plant and animal industry bills of lading.**

**Enrollment in Agriculture/****Bill of Lading Electronic Screening Program:****Issues**

## Florida CVISNTop-Level Design:Agriculture/Bill of Lading Electronic Screening Program

## Agriculture/Bill of Lading Electronic Screening Program:Operational Scenario

**By-pass enrolled and screened carriers past Agricultural inspection stations, for both roadside Agriculture inspections and Bill of Lading Program.  **

## Agriculture/Bill of Lading Electronic Screening Program:Functional Thread Diagram

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**CV Info Exchange**
**Window (CVIEW)**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**OS/OW**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**DOR/Agricultural**
**Screening**
**Enrollment**

**SunPass**
**Enrollment**

**DACS/DOR**
**Imaging**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**PrePass Host**

**HVUT**

**L**
**S**
**I**

**L**
**M**

**STOLEN**

**1**

**2**

**3**

**4a**

**A1**

**3**

**4b**

**A2**

**Roadway**
**Characteristics**
**Inventory (RCI)**

## Agriculture/Bill of Lading Electronic Screening Program:System Interfaces

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**CV Info Exchange**
**Window (CVIEW)**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**OS/OW**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**SunPass**
**Enrollment**

**DACS/DOR**
**Bill of Lading**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**PrePass Host**

**HVUT**

**L**
**S**
**I**

**L**
**M**

**STOLEN**

**Agriculture/Bill of Lading ****Electronic Screening Program:****System Interfaces**

**7**

**Connectivity Type**
- 1. EDI
- 2. Flat File
- 3. DB Connection
- 4. HTTP
- 5. ASPEN
- 6. Proprietary
- 7. DSRC
- ?. Unknown

**?**

**3,6**

**2**

**6**

**Roadway**
**Characteristics**
**Inventory (RCI)**

**DOR/Agricultural**
**Screening**
**Enrollment**

## Agriculture/Bill of Lading Electronic Screening Program:Modifications Required to Existing Systems

**Out-of-Agency funding will be required to upgrade data connection to T-1 or preferably fiber optics  **

## Agriculture/Bill of Lading Electronic Screening Program:Functions to be Performed by New Systems

**CVIEW stores enrollment status of each carrier and  transmits updates to either PrePass or the Agriculture Station Operations Center.**
**Vehicles will be identified, screened and bypassed based on criteria established by DOR and DACS.**
**Screening events will be recorded for reporting purposes.**

## Agriculture/Bill of Lading Electronic Screening Program:Top-Level Physical Design

**DACS Server ****	****	****	****   Connect to CVIEW****	****	****	****	**
**Agriculture Screening****	****	****   Screen Vehicles**
**at Inspection Sites**
**DOR Server****	****	****	****   Connect to DACS****	****	****	****	****   Server**
**	****	****   ****Transponder****	****	****	****   Store and transmit****	****	****	****	****	****   identifier; Receive and****	****	****	****	****	****  display the screening****	****	****	****	****	****  decision**

**	**_**System:**_**	****	****	**_**Function:**_

**Allocation of Functions to Computers**

## Agriculture/Bill of Lading Electronic Screening Program:Top-Level Physical Design

**Description of System/Network Capabilities and Changes**

**Agriculture/Bill of Lading ****Electronic Screening Program:****Top-Level Physical Design**

**Roadside DACS/DOR ****	****         Build New/****	****	****     H****	****    ****	****   4****screening computer****	****         Buy**
**Upgrade communications        Buy****	****	****     H****	****	****   4**
**Infrastructure to T1 or fiber**

## Florida Administrative Rule and Law Changes
Renovations of current Department of Agriculture and Consumer Services inspection sites. 
Funding

**Renovations of current Department of Agriculture and Consumer Services inspection sites. **
**Funding**

**Agriculture/Bill of Lading ****Electronic Screening Program:****Issues**

## Florida CVISNTop-Level Design:IFTA Processing

## IFTA Processing:Operational Scenario

- Accept and process electronic IFTA Tax Returns, Renewals and Decals
- Interact with the applicant electronically, via a Web Browser and Web Site
- Maintain snapshots for interstate operators by providing credential data for carriers and vehicles based in your state to SAFER
- Connect to the IFTA Clearinghouse to support the IFTA base state agreement

**Notes:**
For credentials-related scenarios, it is often convenient to think of the steps in the operational scenario in three subgroups.
On this and subsequent pages, the groups are highlighted with the colors shown:
Yellow steps support the interaction between the state and the applicant (steps 1-12 and 17-20),
Lavender cross-hatched steps correspond to the maintenance of snapshots (steps 13-16 and 21-24),
Blue steps involve the interaction between the state and the core infrastructure systems (in this case, IFTA Clearinghouse) (steps A-D).
The slide show will skip to the thread diagram.  We will walk through the steps of the operational scenario [use overhead projector to show the list].
In the breakout session, you’ll develop operational scenario steps and a thread diagram for how you intend to automate this same IFTA process.  
Keep the scenario steps at about the same level of detail as in this example.  Each step should “name” the information being exchanged and what format (e.g., EDI TS 286) will be used for the exchange.  Also describe, at a high level, the processing performed.

## IFTA Processing:Functional Thread Diagram

**State Roadside Systems**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Other Carrier**
**Systems**

**CVISN **
**Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**NMVTIS**

**MCMIS**

**SAFER**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**SunPass**
**Enrollment**

**DACS/DOR**
**Bill of Lading**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**1,5**

**2,5 **

**3**

**4**

**5**

** ****6**

**4,6**

**4**

**8**

**9**

**10**

**11**

**A, C**

**B, D**

**Internet**
**Tools**
**(e.g., Browser)**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**Web Site**

**Screening**
**(PrePass)**

**Agricultural**
**Station**
**Operations**

**Agricultural**
**Screening**
**(DACS/DOR)**

**L**
**M**

**OS/OW**

**Central Data**
**Repos. (CDRS)**

**L**
**S**
**I**

**L**
**M**

**CV Info Exchange**
**Window (CVIEW)**

**DOR/Agricultural**
**Screening**
**Enrollment**

**Other ****Jurisdictions**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**STOLEN**

**HVUT**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA Processing:****Functional Thread Diagram**

**Roadway**
**Characteristics**
**Inventory (RCI)**

## IFTA Processing:System Connectivity

**DOR  **
**E-Bill of Lading**

**IFTA Processing:****System Connectivity**

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**SunPass**
**Enrollment**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**CV Info Exchange**
**Window (CVIEW)**

**DACS/DOR**
**Bill of Lading**

**OS/OW**

**DOR/Agricultural**
**Screening**
**Enrollment**

- 3

- 3

- 3

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**Other ****Jurisdictions**

**HVUT**

**STOLEN**

**L**
**S**
**I**

**L**
**M**

- 3

- 4

**Connectivity Type**
- 1. EDI
- 2. Flat File
- 3. DB Connection
- 4. HTTP
- 5. ASPEN
- 6. Proprietary
- 7. DSRC
- ?. Unknown

**Roadway**
**Characteristics**
**Inventory (RCI)**

- 2

## IFTA Processing:Modifications Required to Existing Systems

**Upgrade to version 7.26 of Uniface (will be web-enabled).**

## IFTA Processing:Functions to be Performed by New Systems

**Develop Web Interface/Application (If not provided by version 7.26 of Uniface.) **
**Develop link to “MyFlorida.com” **
**CVISN-wide electronic payment system (still being considered).**
- Several options currently exist
**Create automated system to download and incorporate quarterly tax rates for all jurisdictions.**

## IFTA Processing:Top-Level Physical Design

**“****MyFlorida.com” server****	****	****Main link**
**Uniface ****	**** ****	**** ****	****	****House on-line application  **
**DHSMV internal server****	****	****Run process/application **
**CVISN-wide electronic****	****	****Accounting/Payment****payment system**
**DHSMV legacy  (CDRS)****	****	****Long-term data system (Oracle) ****	****	****	****	****repository**

**            **_**System:**_**	****	****	****	**_**Function:**_

**Allocation of Functions to Computers**

## IFTA Processing:Top-Level Physical Design

**1) Presence on****	****	****	****Connectivity****	****      L****	**** ****	****   3     ****    “MyFlorida.com” **
**2) Set-up internal ****	****	**** Build new****	****      H****	****                 3**
**    ****web server to support****    IFTA web application ****	****	****	****	****	****	**

**Description of System/Network Capabilities and Changes**

**IFTA Processing:****Top-Level Physical Design**

## Pending completion of feasibility of e-credential study
May impact timing and priority of projects
Considering whether there should be a link to “MyFlorida.com” 
Need to develop a “Commercial Vehicle” links page on “MyFlorida.com”
Proposed decentralization of credentialing functions to tax collectors, regional DOT/DHSMV sites, or others  will affect priority of all projects
Looking to develop a CVISN-wide payment option
Reconciliation issue with the State Treasurer’s Office

- May impact timing and priority of projects
**Considering whether there should be a link to “MyFlorida.com” **
**Need to develop a “Commercial Vehicle” links page on “MyFlorida.com”**
**Proposed decentralization of credentialing functions to tax collectors, regional DOT/DHSMV sites, or others  will affect priority of all projects**
**Looking to develop a CVISN-wide payment option**
- Reconciliation issue with the State Treasurer’s Office

**IFTA Processing:****Issues**

## Florida CVISNTop-Level Design:IRP Processing

## IRP Processing:Operational Scenario

- Accept and process electronic IRP credential applications for supplements and Renewals
- Interact with the applicant electronically, via a Web Browser and Web Site
- Maintain snapshots for interstate operators by providing credential data for carriers and vehicles based in your state to SAFER
- Connect to the IRP Clearinghouse to support the IRP base state agreement

**Notes:**
For credentials-related scenarios, it is often convenient to think of the steps in the operational scenario in three subgroups.
On this and subsequent pages, the groups are highlighted with the colors shown:
Yellow steps support the interaction between the state and the applicant (steps 1-12 and 17-20),
Lavender cross-hatched steps correspond to the maintenance of snapshots (steps 13-16 and 21-24),
Blue steps involve the interaction between the state and the core infrastructure systems (in this case, IRP Clearinghouse) (steps A-D).
The slide show will skip to the thread diagram.  We will walk through the steps of the operational scenario [use overhead projector to show the list].
In the breakout session, you’ll develop operational scenario steps and a thread diagram for how you intend to automate this same IRP process.  
Keep the scenario steps at about the same level of detail as in this example.  Each step should “name” the information being exchanged and what format (e.g., EDI TS 286) will be used for the exchange.  Also describe, at a high level, the processing performed.

## IRP Processing:Functional Thread Diagram

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**CV Info Exchange**
**Window (CVIEW)**

**CVISN **
**Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**OS/OW**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**DOR/Agricultural**
**Screening**
**Enrollment**

**SunPass**
**Enrollment**

**DACS/DOR**
**Bill of Lading**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**1**

**2,6 **

**3**

**4**

**7**

** ****8**

**4,8**

**5**

**13**

**14**

**15**

**Other ****Jurisdictions**

**16**

**A, C**

**B, D**

**B, D**

**L**
**S**
**I**

**L**
**M**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**STOLEN**

**HVUT**

**Roadway**
**Characteristics**
**Inventory (RCI)**

## IRP Processing:System Connectivity

**DOR  **
**E-Bill of Lading**

**IRP Processing:****System Connectivity**

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**SunPass**
**Enrollment**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**CV Info Exchange**
**Window (CVIEW)**

**DACS/DOR**
**Bill of Lading**

**OS/OW**

**DOR/Agricultural**
**Screening**
**Enrollment**

- 3

- 3

- 3

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**Other ****Jurisdictions**

**HVUT**

**STOLEN**

**L**
**S**
**I**

**L**
**M**

- 3

- 4

**Connectivity Type**
- 1. EDI
- 2. Flat File
- 3. DB Connection
- 4. HTTP
- 5. ASPEN
- 6. Proprietary
- 7. DSRC
- ?. Unknown

**Roadway**
**Characteristics**
**Inventory (RCI)**

- 2

## IRP Processing:Modifications Required to Existing Systems

**Upgrade to version 7.26 of Uniface (will be web-enabled).**

## IRP Processing:Functions to be Performed by New Systems

**Develop Web Interface/Application (if not provided by version 7.26 of Uniface) **
**Develop link to “MyFlorida.com” **
**CVISN-wide electronic payment system (still being considered).**
- Several options currently exist

## IRP Processing:Top-Level Physical Design

**Allocation of Functions to Computers**

**“****MyFlorida.com” server****	****	****Main link**
**Uniface ****	**** ****	**** ****	****	****House on-line application  **
**DHSMV internal server****	****	****Run process/application **
**CVISN-wide electronic****	****	****Accounting/Payment****payment system**
**DHSMV legacy  (CDRS)****	****	****Long-term data system (Oracle) ****	****	****	****	****repository**

**	**_**System:**_**	****	****	**** **_**Function:**_

## IRP Processing:Top-Level Physical Design

**IRP Processing:****Top-Level Physical Design**

**	****	****Level of Effort****	****Phase**_**System**__**	**__**Activity**__**	**__**(L, M, H)**__**	**__**(1-10)**_

**1) Presence on****	****	****	****Connectivity****	****      L****	**** ****	****   9     ****    “MyFlorida.com” **
**2) Set-up internal ****	****	**** Build new****	****      H****	****                 9**
**    ****web server to support**
**    ****IRP web application ****	****	**

## IRP Processing:Issues

**Question of allowing carrier to view its history**
**Due to online processing constraints the number of vehicles allowed for a particular transaction will be limited; however, this limit has not yet been established.**
**Certain regulatory issues related to the verification of items such as HVUT, insurance, etc. by way of paper documentation must be resolved prior to electronic IRP renewal transaction being fully completed to the point of credential issuance.**
**Projected date for participation in IRP clearinghouse is 2001. **

## Florida CVISNTop-Level Design:Oversize/Overweight Permitting

## Oversize/Overweight Permitting:Operational Scenario

**Electronically accept oversize/overweight permit application for both blanket and trip permits**
**System will include “error-check” and screening functions**
**Electronically review and approve (for certain thresholds) oversize/overweight routes for trip permits**
**Accept electronic payment for both blanket and trip permits**
**Provide “up-front” route information to carriers for pre-trip and bid planning**

**Notes:**
For credentials-related scenarios, it is often convenient to think of the steps in the operational scenario in three subgroups.
On this and subsequent pages, the groups are highlighted with the colors shown:
Yellow steps support the interaction between the state and the applicant (steps 1-12 and 17-20),
Lavender cross-hatched steps correspond to the maintenance of snapshots (steps 13-16 and 21-24),
Blue steps involve the interaction between the state and the core infrastructure systems (in this case, IFTA Clearinghouse) (steps A-D).
The slide show will skip to the thread diagram.  We will walk through the steps of the operational scenario [use overhead projector to show the list].
In the breakout session, you’ll develop operational scenario steps and a thread diagram for how you intend to automate this same IFTA process.  
Keep the scenario steps at about the same level of detail as in this example.  Each step should “name” the information being exchanged and what format (e.g., EDI TS 286) will be used for the exchange.  Also describe, at a high level, the processing performed.

## Oversize/Overweight Permitting: Functional Thread Diagram

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**CV Info Exchange**
**Window (CVIEW)**

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**DOR  **
**E-Bill of Lading**

**L**
**S**
**I**

**L**
**M**

**OS/OW**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**DOR/Agricultural**
**Screening**
**Enrollment**

**SunPass**
**Enrollment**

**DACS/DOR**
**Bill of Lading**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Roadway**
**Characteristics**
**Inventory (RCI)**

**Central Data**
**Repos. (CDRS)**

**PrePass Host**

**HVUT**

**L**
**S**
**I**

**L**
**M**

**STOLEN**

**1,5**

**2**

**3,****4**

**A**

**6**

## Oversize/Overweight Permitting:System Interfaces

**DOR  **
**E-Bill of Lading**

**Oversize/Overweight Permitting:****System Interfaces**

**State Roadside Systems**

**Screening**
**(PrePass)**

**L**
**M**

**Weigh Station**
**Operations**

**L**
**S**
**I**

**L**
**M**

**State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**
**(e.g., Browser)**

**Other Carrier**
**Systems**

**Driver**
**Licensing**

**L**
**S**
**I**

**L**
**M**

**Credentialing **
**System **
**(e.g., CAT)**

**Credentialing**
**Interface (CI)**

**Agricultural**
**Station**
**Operations**

**Intrastate Carrier **
**Reg (USDOT#)**

**L**
**M**

**Web Site**

**L**
**S**
**I**

**Titling**

**L**
**S**
**I**

**L**
**M**

**Intrastate Vehicle**
**Registration**

**L**
**S**
**I**

**L**
**M**

**IFTA**

**L**
**S**
**I**

**L**
**M**

**IRP**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**Controller**

**L**
**S**
**I**

**L**
**M**

**SAFETYNET**

**L**
**S**
**I**

**L**
**M**

**Compliance **
**Review**
**(e.g., CAPRI)**

**L**
**S**
**I**

**L**
**M**

**SunPass**
**Enrollment**

**Agricultural**
**Screening**
**(DACS/DOR)**

**SunPass**
**Operations**

**L**
**M**

**L**
**S**
**I**

**Citation**

- L
- S
- I

- L
- M

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**S**
**I**

**L**
**M**

**L**
**S**
**I**

**L**
**M**

**Central Data**
**Repos. (CDRS)**

**CV Info Exchange**
**Window (CVIEW)**

**Roadway**
**Characteristics**
**Inventory (RCI)**

**DACS/DOR**
**Bill of Lading**

**OS/OW**

**DOR/Agricultural**
**Screening**
**Enrollment**

- ?

- 3

**CVISN Core ****Infrastructure**
**Systems**
** ****(National/****Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Licensing and**
**Insurance**

**Compliance**
**Review**
**(e.g., CAPRI)**

**NCIC/**
**NLETS**

**PrePass Host**

**HVUT**

**STOLEN**

**L**
**S**
**I**

**L**
**M**

- 4

**Connectivity Type**
- 1. EDI
- 2. Flat File
- 3. DB Connection
- 4. HTTP
- 5. ASPEN
- 6. Proprietary
- 7. DSRC
- ?. Unknown

- 3

- ?

## Oversize/Overweight Permitting:Modifications Required to Existing Systems

**Link from RCI and PONTIS to the OS/OW (route review) system.**
**Incorporate RCI and PONTIS into routing decision.**

## Oversize/Overweight Permitting:Functions to be Performed by New Systems

**Web server to host and screen application. **
**Routing review system to approve routes (within certain threshold)--weight, height, length, width, inner-bridge, etc.**
**Manually introduced impediments database will allow temporary restrictions (construction data, emergency situations, road closures, special events, detours, etc.) to be included in the routing review process.**
**Electronic Payment System--to be developed CVISN-wide.  **

## Oversize/Overweight Permitting:Top-Level Physical Design

**           **_**System:**_**	****	****	****	**_**Function:**_
**“****MyFlorida.com”****	****	****	****	****Entry Portal**
**Web Server****	****	****	****  ****	****Host On-line Application ****	****	****	****	****   ****	****and Screen Applications****	**
**RCI****	****	****	****	****	****Roadway Characteristics****	**** ****	****	****	****	****	****Inventory**
**PONTIS****	****	****	****	****	****Bridge inventory and information**
**Manual Impediments Database****	****	****Construction, Emergency, Special ****	****	****	****	****	****Event Data, Etc.**
**OS/OW System ****	****	****	****	****Review routes, approve and issue**** ****	****	****	****	****	****permits, generate approved routes,****	****	****	****	****	****send permit information to CVIEW**
**CVISN Electronic Payment System ****	****	****Payment for permits**

**Allocation of Functions to Computers**

## Oversize/Overweight Permitting:Top-Level Physical Design

**Description of System/Network Capabilities and Changes**

**Oversize/Overweight Permitting:****Top-Level Physical Design**

**“****MyFlorida.com”****	****	****            Establish link****	****    L****	****	****   3**
**RCI****	****	****	****            Upgrade and****	****    H****	****                   4-5****	****	****	****            link to permit system     ****	**
**PONTIS****	****	****	****            Link to permit system    L****	****  ****	****   4**
**Manual Impediments****	****            Build new****	****	****     M****	****	****   4****Database**
**OS/OW System****	****	****            Build new ****	****	****     H  ****	****	****   3-5**

## Who will modify RCI data base and when will this occur.
Specifications for Web Server
Modifications to OS/OW system may require new LAN Server
Web based Permitting system must begin development soon

**Specifications for Web Server**
**Modifications to OS/OW system may require new LAN Server**
**Web based Permitting system must begin development soon**

**Oversize/Overweight Permitting:****Issues**

## Florida CVISN Top-Level Design

**Florida CVISN ****Top-Level Design**

**Section 4.0:**
**Phase Charts and ****System Testing Strategy**

## Florida CVISNProgress Toward Level 1

**Electronic Screening**
- Level 1 Achieved
**Safety Information Exchange**
**ASPEN**
- Level 1 Achieved
**CVIEW**
- Level 1 will be Achieved with the Deployment of a CVIEW in Phase 3
**Credentials Administration**
- Level 1 will be Achieved with the Delivery of IFTA and IRP Web-Based Applications in Phases 3 thru 9

## Florida CVISNProgram Phases

**Phase 1:****	****	****	****January 2001-September 2001**
**Phase 2:****	****	****	****October 2001-December 2001**
**Phase 3:****	****	****	****January 2002-March 2002**
**Phase 4:****	****	****	****April 2002-June 2002**
**Phase 5:****	****	****	****July 2002-September 2002**
**Phase 6:****	****	****	****October 2002-December 2002**
**Phase 7:****	****	****	****January 2003-March 2003**
**Phase 8:****	****	****	****April 2003-June 2003**
**Phase 9:****	****	****	****July 2003-September 2003**

## Phases 1 to 3:January 2001 to March 2002

## Phases 4 to 6:April 2002 to December 2002

## Phases 7 to 9:January 2003 to September 2003

## System Testing

**Florida will conduct unit, integration and acceptance tests on all software developed as part of its CVISN Program.**
**Following acceptance of each system, a pilot test or parallel run will be conducted.   Accordingly, system testing and pilot tests/parallel runs span the Program phases.**

## Program-wide Issues

**Funding**
**Resources**
**Electronic Payment System**