# Presentation: 777272

## 1  Introduction

***1  Introduction***

**1   Introduction**
**2  Generic CVIEW HW & SW Spec**
**3  Communication Options**
**4  System Installation**
**5  Frequently Asked Questions (FAQ)**
**6  CVIEW Schedule**

**1.1  CVIEW Description**
**1.2  CVIEW Top-level System Design**
**1.3  Key Design Features**
**1.4  Safety Information Exchange**
**1.5  Electronic Screening Support**
**1.6  Credentials Information Exchange**
**1.7  Snapshots**

## CVIEW Description

- 	CVIEW will be owned by and located in each state that elects to use this system as a data exchange method. CVIEW is being designed primarily for the storage of and access to intrastate safety and credential data; however, it will also provide access to interstate safety and credential data that it obtains from the Safety and Fitness Electronic Records (SAFER) System.

- 	The FHWA Office of Motor Carriers (OMC) has provided carrier safety data to industry and the public for many years via telephone requests and paper reports.  The CVIEW System makes it possible to offer this information electronically. Access will be provided to carrier, vehicle, and driver snapshots, a concise electronic record of safety and credential data including identification, size, commodity information, safety record, including safety rating (if any) and roadside out-of-service inspection data, registration and permit information, and other related data.

***CVIEW Description***

## Top-level CVIEW Design

**Information**
**Users**
- Insurer
- Mobile Unit
- Roadside
- SAFETYNET
- Shipper
- HELP
- Advantage CVO
- Carriers
- SAFER
- State Systems
- Clearinghouses
- Others...

**Indirect**
**Sources**
**SAFER**
**Multi-State Systems**
**Clearinghouses**

- Other Government
- Systems

**Commercial / Government**

**Wireline / Wireless Services**

**       ****(e.g., NLETS, AAMVAnet, VANs)**

- Financial Institutions

**Authoritative**
**Sources**
**State Systems**

***Top-level CVIEW Design***

## Key CVIEW Design Features

**Client-server data exchange with limited trusted systems, e.g., SAFER**
**Snapshots for carrier, vehicle, and driver safety and credentials information exchange; exchange of partial snapshots or views are supported**
**Subscriptions for the definition and proactive transmission of user-defined data**
**Division of Functionality:**
**Core Functionality**
**common to all CVIEW Systems**
**encompasses exchange of carrier, vehicle, and driver safety and credential information with SAFER and state legacy systems via X12 EDI 285 transactions; limited client-server communications with trusted systems, .e.g. SAFER, is supported**
**Customized State Functionality**
**Custom modifications to CVIEW via Legacy System Interface (LSI) modules or modifications to the state’s legacy systems via Legacy Modifications (LM) will be required for those States with data processing requirements that are incompatible with CVIEW core functional processing capabilities **

***Key CVIEW Design Features***

## CVIEW Safety Information Exchange

- The state CV Information Exchange Window (CVIEW) system supports the transfer of safety and credentials information (SAFER-style snapshots and reports) within the state and with CVISN core infrastructure elements.  The state CVIEW handles information about intrastate and interstate operators.
- For safety information exchange, CVIEW will interface with state and federal commercial vehicle credential and safety administration-related offices, roadside check stations, and information exchange systems (e.g., CDLIS, SAFER, NLETS, SAFETYNET/AVALANCHE).
- The primary state administrative offices include the designated lead Motor Carrier Safety Assistance Program (MCSAP) agency, SAFETYNET, and other enforcement activities, but this category includes other state agencies that provide or have an interest in commercial vehicle safety information (e.g., vehicle registration, driver licensing, titling, permitting).  These offices exist in each state or region, and share information through various CVISN core infrastructure systems.
- Roadside check stations include those locations with a permanent structure or mobile facility that house elements of the information system (e.g., computers and communication systems) and enforcement and safety inspection personnel

- CVIEW safety data exchange is based on the use of standardized data flows for carrying  summary (snapshot) and detailed (report) safety and credentials information.  These dataflows will provide a consistent basis for automating CVO information exchanges and processing, and to ensure interoperability among existing and developing CVO information systems.  EDI X12 transaction set 285 is used to carry snapshot information.  An EDI X12 transaction set which is TBD will be used to carry safety report information.
- Snapshots convey information about three major entities: carriers, vehicles, and drivers.  To minimize response time to requesters, snapshots will be stored in the CVIEW system. More detailed supersets of standardized dataflows required by the same requesters are known as carrier, vehicle, and driver “reports”. Reports are not stored locally but are available via electronic request to the SAFER system.
- Snapshots are used for screening carriers, vehicles, and drivers at mainline speeds at roadside check stations, for safety inspections, for limited credentials checking and insurance applications, and for industry self-checks.  Different subsets (called “views”) of the snapshot record available in CVIEW for a carrier, vehicle, or driver will support different user systems.

***CVIEW Safety Information Exchange***

## Safety Information Exchange: Standardized EDI transactions make it possible to check safety performance roadside and deskside

*Exchanging safety information is intended to improve safety performance.*
*	**Monitor safety performance in safety assurance programs;*
*	**Collect driver/vehicle inspection data, carrier compliance information, citation & accident data;*
*	**Provide safety & credentials snapshots to the roadside for screening & inspections;*
*	**Check safety history before granting credentials;*
*	**Share information with other states*

**CVISN Core Infrastructure**

- 1

- 2

- 3

- 4

- 5

**Legacy Systems**
**Associated with Credentialing**

**Legacy Systems Associated with Safety**
**- ****Safety Info Sys**
**- SAFETYNET/ AVALANCHE**
**- CAPRI**

**State CV Roadside Check Stations (Fixed or Mobile)**
**- Roadside Operations**
**- Screening**
**- ASPEN**
**- Citation & Accident**

**SAFER/Data Mailbox**

**MCMIS**

**CDLIS**

**EDI**

**EDI**

**285, 997, TBD**

**EDI**

**285, TBD, 997**

**State Administrative Systems**

**CVIEW/**
**Data Mailbox**

**Leg Sys Mods**

**EDI**

**285, 997, TBD**

**285, 997**

**285, 997**

**285, 997, TBD**

**EDI**

- or

- or

- or

**EDI**

**285, 997, TBD**

**EDI**

**Interim approach for ASPEN **

- 1

- 2

- 2

- 3

- 4

- 5

***Safety Information Exchange: Standardized EDI transactions make it possible to check safety performance roadside and deskside***

## Key

**SAFER/Carrier**
**SAFER/Driver-Vehicle**

**SAFER**

** ****Inter- & intrastate carrier, vehicle, & driver data based in that state**

**Interstate carrier, vehicle, & driver data**

**Key**

**Inter- & intrastate carrier, vehicle, & driver data**

***SAFER/CVIEW Data Exchange***

## CVIEW Electronic Screening Support

- For electronic screening, the major CVISN design elements include vehicles, manned fixed or mobile roadside check stations, the state **Commercial Vehicle Information Exchange Window (CVIEW)** system, the state CV safety administration, and various multi-state information systems.
**Vehicles** are equipped with electronic tags (transponders) that support dedicated short range communications (DSRC) and are integrated with an in-cab display (visual and audio) used for driver notification.  Various techniques may be used to store driver and load information on the tag.  Vehicles typically interface with screening equipment at mainline speed and drivers are notified of bypass status via the in-cab device.
**Fixed commercial vehicle roadside check stations** are manned locations with a permanent structure that can house elements of the information system (e.g., computers and communication systems).   The stations are equipped with dedicated short range communications (DSRC) systems for interfacing with tagged vehicles.  License plate readers may be used to identify untagged vehicles.  Fixed sites are usually equipped with some weighing device (weigh-in-motion (WIM) device or a static scale).   A more sophisticated configuration includes a screening WIM device integrated with an automated vehicle classification system to perform weight, size, and length checks, and a static scale to measure weight more precisely when the vehicle is stopped.  If the WIM and automatic

- vehicle classification (AVC) system are located in the roadway on the mainline, then “screening” (making pass/pull-in decisions) can be performed at mainline speed.  Manned fixed sites are likely to be co-located with a safety inspection facility.
**Mobile enforcement units **can be equipped with various combinations of DSRC, automatic vehicle identification (AVI), AVC, and WIM systems.  They are typically positioned in areas where violations are known or suspected to occur.  These units are equipped with tag readers that allow them to interface with vehicle transponders and mobile computers that look up credential and safety records either locally or stored in the infrastructure.
**State administration** systems support electronic screening operations in that they provide CVO data required for electronic clearance.  The results of roadside activities (vehicles that were seen and cleared, seen and stopped, inspected, citations issued, number of vehicles that passed the station, etc.) are provided to the state CV safety administration.
**Core infrastructure systems** such as CDLIS may be queried either directly or indirectly to gather safety, license, and enforcement information about the carrier, vehicle, and driver.
**CVIEW** will provide inter- and intrastate carrier, vehicle, and driver snapshot records, obtained from SAFER and state legacy systems, respectively, to roadside and state administration systems to support electronic screening operations.

***CVIEW Electronic Screening Support***

## Electronic Screening: DSRC is used to identify the carrier, vehicle, & driver; corresponding infrastructure data helps with screening decisions

***Roadside electronic screening focuses resources on high risk operators:***
***	******Identify carrier, vehicle, driver via DSRC transponder & standard messages***
***	******Pull in untagged vehicle to identify carrier, vehicle, driver***
***	******Check snapshot information when making screening decisions***
***	******Before issuing citation, check with authoritative source for latest status***

- 1

- 2

- 3

- 4

**CVIEW/Data Mailbox**

**SAFER/Data Mailbox**

**CVISN Core Infrastructure**

**State Roadside Systems**

**Screening **

**Roadside **
**Operations**

**Other State Systems**

**CDLIS**

**DSRC**

- 1

- 2

- 3

- 4

**Citation & **
**Accident**

**285, 997**

**Leg Sys Mods**

**or**

**EDI**

**285, 997**

**EDI**

**MCMIS**

**EDI**

**285, 997**

**EDI**

**285**

**or**

- 3

- 4

- 4

- 4

- 4

***Electronic Screening: DSRC is used to identify the carrier, vehicle, & driver; corresponding infrastructure data helps with ******screening decisions***

## CVIEW Credential Information Exchange

- The CVISN design elements involved with credentials administration include the Carrier Automated Transaction (CAT), the state Credentialing Interface(CI) system, communications system(s) that facilitates the exchange of information between the carriers and the state, state legacy systems associated with individual credentials, and clearinghouses in the CVISN Core Infrastructure.  The state **Commercial Vehicle Information Exchange Window (CVIEW)** supports the exchange of credentials-related information via snapshots.
- This design allows carriers, owners, and drivers to apply for, pay for, and receive credentials electronically.  It also supports states/regions in the administration of credentials, collecting and distributing funds, and in storing and distributing credentials related data.  The design also establishes standard mechanisms (the snapshots) for states to provide credentials information to enforcement officials and other authorized stakeholders.
- Normally, the elements exchange information with each other through standardized interfaces (public - private, and infrastructure - state) using ANSI ASC X12 Electronic Data Interchange (EDI) transactions.  The elements are virtually linked through government and commercial network services.  Proprietary or sensitive information is protected from inadvertent disclosure through network “firewalls”, business practices, and procedures.

- A **credential** is defined to be the authority granted by the issuing jurisdiction.  Today, most credentials are issued in paper form, with supporting records on file in the issuing jurisdiction’s system.   An **electronic credential** is an electronic record of the credential. The authoritative source for an electronic credential is the issuing agency.  The holder of the credential may be issued an electronic copy that represents the same authority as today’s paper copy.
- A state’s **CVIEW** system facilitates the exchange of electronic credentials among users, e.g., carriers, shippers, insurers, the enforcement community, and others, elements of the CVISN Core Infrastructure, e.g., SAFER, and the state’s information systems.

***CVIEW Credential Information Exchange***

## Credentials Administration:  Standardized EDI transactions enable carriers to obtain credentials and enable states to process the applications and support base state agreements electronically

***Standardized transactions enable: ***
***	******carriers to file for credentials from their offices,***
***	******states to process applications automatically,***
***	******states to exchange information electronically to support base state agreements***
***Standardized transactions support fee payments among payers, payees, and financial institutions (banks).******	***

**CVIEW/Data Mailbox**

**Motor Carrier**

**Clearinghouses**
**(Support base state agreements)**

**286, 813, 820, **
**864, 997**

**Carrier**
**Automated**
**Transaction**
**(CAT) System**

**285, 997**

**286, 820, **
**826, 997**

**State**

**CVISN Core Infrastructure**

**EDI**

**EDI**

**EDI**

**Carrier Bank**

**EDI**

**820, 997**

**EFT**

**820, 997**

**EFT**

**C-house**
**Bank**

**State Bank**

**Legacy Systems**
**Associated with Credential or Fuel Tax Filing**

- 1

- 3

- 4

- 4

**LMs**

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

**286, 813, 820, 864, 997**

- 2

**EDI**

**CI / Legacy **
**Workstations**

**(For manual review or entry of credential / tax filing info)**

- or

- or

**EDI**

**EDI**

**820, 997**

**EDI**

**820, 997**

- 1

- 2

- 3

- 4

***Credentials Administration:  Standardized EDI transactions enable carriers to obtain credentials and enable states to process the applications and support base state agreements electronically***

## Snapshot Data Stored in SAFER/CVIEW

- Notes:
- 1 = Data are current; all other data are historical;
- 2 = State may store in CVIEW or may request SAFER to store

*There are 3 kinds of snapshots: carrier (available now), vehicle, and driver;*
*The use of common identifiers allows agencies and jurisdictions to exchange information;*
*Limited DMV data are included in the snapshots*
*(a) Vehicle apportionment data*
*(b) DMV check flags may also be included.  A check flag is used to indicate a recent problem, but does not attempt to define current status.*
*Each state may include special check flags to alert its roadside officers to some particular problem.*

- 1

- 2

- 3

- 4

- 1

- 2

- 3

- 4

- 4

**Snapshot Data Stored in SAFER/CVIEW**

***Snapshots are assembled & stored to facilitate the exchange of safety & credentials Information among systems.***

## Snapshot Data Passed to the Roadside

- 1

- Notes:
- 1 = Data are current; all other data are historical;
- 2 = State may store in CVIEW or may request SAFER to store

- 1

***A subset of the snapshot data are sent to the roadside for use in electronic screening.  If more data are needed, queries to CVIEW, SAFER, or the authoritative source are issued.***

**Snapshot Data Passed to the Roadside**

## This page was intentionally left blank