Intelligent Transportation Systems (ITS)

Commercial Vehicle Operations (CVO)

**CVISN Operational and Architectural**

**Compatibility Handbook (COACH)**

**Part 1**

Operational Concept and Top-Level Design Checklists

Baseline Version

POR-97-7067 V2.0

**August 2000**

**Note**

> > *The Motor Carrier Safety Improvement Act was signed into law on
> > December 9, 1999. This act established a new FMCSA within the US
> > DOT, effective January 1, 2000. Prior to that, the motor carrier and
> > highway safety program was administered under the Federal Highway
> > Administration (FHWA).*
>
> > *The mission of the FMCSA is to improve truck and commercial
> > passenger carrier safety on our nation's highways through
> > information technology, targeted enforcement, research and
> > technology, outreach, and partnerships. The FMCSA manages the
> > ITS/Commercial Vehicle Operations (CVO) Program, a voluntary effort
> > involving public and private partnerships that uses information
> > systems, innovative technologies, and business practice
> > reengineering to improve safety, simplify government administrative
> > systems, and provide savings to states and motor carriers. The FMCSA
> > works closely with the FHWA's ITS JPO to ensure the integration and
> > interoperability of ITS/CVO systems with the national ITS program.*
>
> **This is a Baseline Issue**
>
> This document has completed internal and external reviews of
> previously published drafts and preliminary versions. All comments
> received to date have been incorporated or addressed.
>
> **Note:** This document and other CVISN-related documentation are
> available for review and downloading by the ITS/CVO community from the
> JHU/APL CVISN site on the World Wide Web. All updates to this document
> will be maintained and published on that site; hardcopies of future
> versions will not normally be distributed. The URL for the CVISN site
> is: <http://www.jhuapl.edu/cvisn/>
>
> Additional review and comments to this document are welcome.
>
> Ms. Theresa G. Nester
>
> The Johns Hopkins University
>
> Applied Physics Laboratory
>
> 11100 Johns Hopkins Road
>
> Laurel, MD 20723-6099
>
> Phone: 443-778-8760
>
> Fax: 443-778-6149
>
> E-Mail: <theresa.nester@jhuapl.edu>

**Change Summary:**

This document is under configuration management by the CVISN
Architecture Configuration Control Board. The list below provides a
brief description of the change request forms (CRFs) processed by the
board that impacted this document. Soon we hope to post the CRFs on the
CVISN Web site referenced above.

**Version V1.0** of the document incorporated revisions related to these
change reports:

-   970116 -- Stakeholder view, system names, flows associated with
    inspection reporting

-   970303 -- Capability names

-   970307 -- Add intrastate vehicle registration where missing

-   970312 -- A baseline update of design drawings to incorporate
    comments received from stakeholders and the CVISN technical team.
    Additional top-level design information has also been added.

-   970710 -- Change groupings on Stakeholder View; add Treasury

-   CRF 220 -- Change inspection reporting/retrieval paths & methods

-   CRF 285 -- Add WebCAT, remove Safety Information System; change CAT
    to Credentialing System (e.g., CAT)

-   CRF 311 -- Clarify ITS/CVO versus CVISN Architecture

-   CRF 493 -- Update COACH Part 1 Chapter 4

-   CRF 356 -- Modifies the way intrastate inspections are reported

-   CRF 529 -- Add Electronic Screening Enrollment to the design

-   CRF 530 -- Add Licensing & Insurance, RSPA HazMat, SSRS; remove UCR

-   CRF 548 -- Primary Carrier ID

-   CRF 549 -- Transponder ID

-   CRF 564 -- Update COACH Part 1 Chapters 1, 3, 5-8

References to the CRFs listed below appear in the text or tables of the
document so that the reader knows how each CRF affected Version V2.0 of
the document

**Version V2.0** of the document incorporates revisions related to these
change reports:

-   CRF 313 -- Disapproved (EDI interface for IRP CH)

-   CRF 632 -- Add general operational concept to COACH to explain CVISN
    Level 1 focus

-   CRF 827 -- Snapshot update views & control, esp. how SAFER & CVIEW
    should handle data from multiple sources

-   CRF 1047 -- Update CVISN to include Archived Data User Service

-   CRF 1048 -- Update CVISN for Web sites and XML for Credentialing

-   CRF 1084 -- Update Design Template and Stakeholder View

-   CRF 1154 -- Simplify and consolidate the COACH Part 1

-   CRF 1155 -- Add conformance requirements

-   CRF 1159 -- Update DSRC references

-   CRF 1164 -- Clarify interface options (EDI, XML, Web, other) for
    Safety

-   CRF 1171 -- Use Snapshots for E-Screening in Automated Process

-   CRF 1172 -- Clarify & complete concepts and requirements for
    E-Screening Enrollment

**CVISN Operational and Architectural Compatibility Handbook (COACH)**

**Part 1 - Operational Concept and Top-Level Design Checklists**

Table of Contents

1\. Introduction [1](#introduction)

COACH Structure [1](#section)

1.2 COACH Part 1 Description [2](#coach-part-1-description)

1.3 COACH Heritage [2](#coach-heritage)

1.4 CVISN System Design [4](#cvisn-system-design)

1.5 How States Should Use This Document
[5](#how-states-should-use-this-document)

2\. Guiding Principles [9](#guiding-principles)

2.1 ITS/CVO Guiding Principles \[Reference 17\]
[9](#itscvo-guiding-principles-reference-17)

2.1.1 ITS/CVO Guiding Principles : Summary
[9](#itscvo-guiding-principles-summary)

2.1.2 ITS/CVO Guiding Principles: General CVO
[10](#itscvo-guiding-principles-general-cvo)

2.1.3 ITS/CVO Guiding Principles: CVISN Architecture
[12](#itscvo-guiding-principles-cvisn-architecture)

2.1.4 ITS/CVO Guiding Principles: CVISN Deployment
[12](#itscvo-guiding-principles-cvisn-deployment)

2.1.5 ITS/CVO Guiding Principles: Safety Assurance
[13](#itscvo-guiding-principles-safety-assurance)

2.1.6 ITS/CVO Guiding Principles: Credentials & Tax
[14](#itscvo-guiding-principles-credentials-tax)

2.1.7 ITS/CVO Guiding Principles: Roadside Operations
[15](#itscvo-guiding-principles-roadside-operations)

2.2 Fair Information Principles for ITS/CVO \[Reference 18\]
[15](#fair-information-principles-for-itscvo-reference-18)

2.3 ITS/CVO Interoperability Guiding Principles \[Reference 19\]
[18](#itscvo-interoperability-guiding-principles-reference-19)

2.3.1 ITS/CVO Interoperability Guiding Principles: General
[18](#itscvo-interoperability-guiding-principles-general)

2.3.2 ITS/CVO Interoperability Guiding Principles: Hardware
[19](#itscvo-interoperability-guiding-principles-hardware)

2.3.3 ITS/CVO Interoperability Guiding Principles: Systems/Software
[20](#itscvo-interoperability-guiding-principles-systemssoftware)

2.3.4 ITS/CVO Interoperability Guiding Principles: Operations
[20](#itscvo-interoperability-guiding-principles-operations)

2.3.5 ITS/CVO Interoperability Guiding Principles: Program
[21](#itscvo-interoperability-guiding-principles-program)

3\. State Institutional Framework [23](#state-institutional-framework)

4\. State Systems Checklists [29](#state-systems-checklists)

4.1 General Operational Concepts and State Systems Design Requirements
[30](#general-operational-concepts-and-state-systems-design-requirements)

4.2 State Safety Information Exchange and Safety Assurance Systems
Design Requirements
[37](#state-safety-information-exchange-and-safety-assurance-systems-design-requirements)

4.3 State CV Administration Systems Design Requirements
[42](#state-cv-administration-systems-design-requirements)

4.4 State Electronic Screening Systems Design Requirements
[51](#state-electronic-screening-systems-design-requirements)

5\. References [57](#references)

# Introduction

The CVISN Operational and Architectural Compatibility Handbook (COACH)
provides a comprehensive checklist of what is required to conform with
the Commercial Vehicle Information Systems and Networks (CVISN)
operational concepts and architecture. It is intended for use by state
agencies with a motor carrier regulatory function. Other readers may
include motor carriers and developers/operators of CVISN Core
Infrastructure systems.

Reference 1, the CVISN Glossary, contains an acronym list as well as
brief descriptions of many commonly used terms.

## ![](media/image1.wmf)

The COACH is divided into 5 parts:

> [Part 1 - Operational Concept and Top-Level Design Checklists]{.mark}

Part 2 - Project Management Checklists

Part 3 - Detailed System Checklists

Part 4 - Interface Specification Checklists

Part 5 - Interoperability Test Criteria

This is the fourth revision to the COACH Part 1 \[see References 2, 3,
and 36 for earlier versions\]. The other parts of the COACH are
available at the Browse and Download Documentation; Architecture section
of the JHU/APL CVISN web site <http://www.jhuapl.edu/cvisn/>. Updated
versions of Parts 3 \[Reference 5\] and 4 \[Reference 6\] will be
published in 2000.

## COACH Part 1 Description

This is Part 1. Part 1 includes several types of checklists related to
operational concepts and top-level design. In accordance with CRF 1154,
this version of the document has been restructured to simplify and
consolidate material as shown below:

-   Guiding Principles: high level strategic guidelines \[Chapter 2\]

-   State Institutional Framework Checklists: compatibility requirements
    for the policies and coordinating activities for states \[Chapter
    3\]

-   CVISN Operational Concepts and Top-level Design Checklists:
    compatibility requirements for processes and top-level compatibility
    requirements for state designs \[Chapter 4\]. In this version of the
    COACH Part 1, the tables that listed the planned or proposed
    capabilities for CVISN Core Infrastructure systems and carrier
    systems have been removed.

The COACH Part 1 checklists are intended to be used to indicate the
scope and depth of CVISN commitment, and to provide a mechanism for
planning development and test activities. Each state should maintain a
filled-in master copy of the COACH.

## COACH Heritage

The first versions of this part of the COACH \[References 2, 3, and 36\]
were derived from other CVISN technical documents:

-   Introduction to CVISN \[Reference 8\]

-   CVISN Operational Concept Document \[Reference 9\]

-   CVISN Architecture Specification \[Reference 10\]

-   CVISN System Design Description \[Reference 11\]

Only the last document in that list is still being maintained. The other
documents have been replaced with some of the volumes in the CVISN Guide
series. Technical guidance about CVISN is now provided in:

-   The CVISN General and Technical Guides

```{=html}
<!-- -->
```
-   Introductory Guide to CVISN \[Reference 12\]

-   CVISN Guide to Top-Level Design \[Reference 13\]

-   CVISN Guide to Safety Information Exchange \[Reference 14\]

-   CVISN Guide to Credentials Administration \[Reference 15\]

-   CVISN Guide to Electronic Screening \[Reference 16\]

```{=html}
<!-- -->
```
-   Other volumes of the COACH \[Reference 4-7\]

-   CVISN System Design Description \[Reference 11\]

-   Electronic Data Interchange standards and implementation guides
    \[References 25, 27-31\]

-   Dedicated Short-Range Communications standards \[References 32-34\]

## CVISN System Design 

The figure below depicts the CVISN System Design - Stakeholder View. CRF
1084, requesting that the diagram be updated to reflect current
terminology and components involved in CVISN, has been applied. Chapter
4 of this document focuses on the State systems. For a brief description
of each system shown on this figure, see the CVISN System Design
Description \[Reference 11\].

Figure 1.4‑2 CVISN System Design - Stakeholder View

![](media/image1.wmf)

## How States Should Use This Document

The COACH summarizes key concepts and architectural guidelines for
CVISN. The COACH focuses on topics important to states. The COACH Part 1
defines the CVISN Level 1 criteria.

To gain a more complete understanding of CVISN, state planners and
designers should read the Introductory Guide to CVISN \[Reference 12\],
other parts of the COACH \[References 4-7\], and the CVISN System Design
Description \[Reference 11\]. This version of the COACH Part 1 is
intended to be a working document that is used for setting requirements
for modifications and enhancements to existing state systems, and for
planning the development of new systems in states. This document will be
used first in the CVISN Scope workshop.

The key concepts and architectural guidelines for CVISN states have been
summarized in this document in a series of checklist tables. Each table
in this document consists of these columns, unless otherwise noted:

-   Commit Level (F/P/N) -- the state's commitment level to the item

> Using the first column of each checklist entry, a **commitment level
> should be filled in** by the state. There are three possible levels of
> commitment:
>
> \(F\) This rating indicates a full commitment. This level means that
> at least 80% of the state's systems involved in the process implied by
> the checklist item are compatible or are intended to be compatible
> with the checklist item statement.
>
> \(P\) This rating indicates a partial commitment. This level means
> that between 50% and 80% of the state's systems involved in the
> process implied by the checklist item are compatible or are intended
> to be compatible with the checklist item statement.
>
> \(N\) This rating indicates no commitment. This level means that less
> than 50% of the state's systems involved in the process implied by the
> checklist item are compatible or are intended to be compatible with
> the checklist statement.

-   Item \# -- a label to identify each row in the table.

-   Compatibility Criteria - summary versions of operational concepts or
    architectural guidelines, culled from other CVISN documentation.

-   Req Level (chapters 3 and 4 only) - the compatibility requirement
    level assigned to this compatibility criterion by the FMCSA CVISN
    project team

    For a state to be "compatible with CVISN," it must implement
    selected items in the checklists. To distinguish those items, the
    CVISN project team has assigned a **compatibility requirement**
    **level** to each checklist item:

> (L1) This rating identifies a CVISN Level 1 compatibility requirement.
>
> \(E\) This rating indicates an enhanced level of CVISN capability.
> These items may require a little longer to complete (3-4 years).
>
> \(C\) This rating indicates a complete level of CVISN capability.
> Satisfying all these provides complete CVISN compatibility. These
> items are expected to require a longer-range (5 or more years) time
> frame.

States are expected to focus initially on checklist items with an *L1*
compatibility requirement level rating. Making a *partial commitment*
indicates that the state will at least demonstrate the feasibility of
that concept or architectural guideline. Making a *full commitment*
indicates that the state will fully implement the concept or
architectural guideline and be ready for the next steps.

> CRF \# - if the item has been changed since the last revision, the
> Change Request Form (CRF) number for the CR that triggered the
> document update will appear in this column. A list of all CRFs
> incorporated in this revision is included on the back of the title
> page.

-   Op Test Date (chapter 4 only) - to be used for planning/tracking by
    the owner of a particular copy of the document; indicates when the
    criterion is to be (has been) operationally tested (op test); may
    refer to a milestone by name rather than a specific date; if plans
    change, this column should be updated accordingly

-   IOC Date (chapter 4 only) - to be used for planning/tracking by the
    owner of a particular copy of the document; indicates when initial
    operating capability (IOC) for the criterion is to be (has been)
    achieved; may refer to a milestone by name rather than a specific
    date; if plans change, this column should be updated accordingly

-   FOC Date (chapter 4 only) - to be used for planning/tracking by the
    owner of a particular copy of the document; indicates when final
    operating capability (FOC) for the criterion is to be (has been)
    achieved; may refer to a milestone by name rather than a specific
    date; if plans change, this column should be updated accordingly

-   Comments -- available for the state to refer to another document or
    plan, note a question, record a clarifying comment, etc.

    If the state maintains its master copy of this document
    electronically, the following conventions are recommended when
    filling in the columns to illustrate the "firmness" of the state's
    plan:

-   *Italics type* : Tentative, not approved by the final decision
    makers

-   Regular type : Approved by the decision makers (or supported by
    consensus)

-   **Bold type** : Completed

States are to fill out the "Commit Level" column for the tables in
chapters 2 (Guiding Principles), 3 (State Institutional Framework), and
4 (State Systems Checklists) prior to attending the CVISN Scope
Workshop. Since the first workshop focuses on *what* the states will do
rather than *when* those actions will be scheduled, it is not necessary
to complete the planning columns (Op Test Date, IOC Date, FOC Date) for
the CVISN Scope Workshop. The remainder of the columns will be completed
as the project progresses.

This Page Intentionally Blank

# Guiding Principles

Statements of principle are being used to document fundamental concepts
and guidelines supported by the CVO community. In addition to the
specific checklists provided in subsequent sections, these guiding
principles provide a top-level checklist of fundamental guidelines for
all CVISN activities. CVO stakeholders should ensure that their actions
are consistent with these principles. No planning columns are included
in the tables for guiding principles since the principles provide
guidance rather than specific details that can be scheduled or measured.

The guiding principles were developed under the auspices of the ITS
America CVO Program Subcommittee \[References 17, 18, 19\]. These
principles continue to be under review by ITS America and the US
Department of Transportation. They will be updated as required to
reflect the consensus of the CVO community. The current principles are
copied verbatim into the tables in this chapter.

## ITS/CVO Guiding Principles \[Reference 17\]

"The ITS America CVO Committee presents this set of guiding principles
which will guide the states and federal government on matters concerning
technology and commercial vehicle operations. This list of 39 guiding
principles was established by the CVO Programs Subcommittee with
representation from National Private Truck Council, ATA, carriers, owner
operators, motorcoach representation, UPS, several state administrative
and regulatory agencies, AAMVA, AASHTO, and Canada. These principles
took two years to create and 100% consensus was reached.

### ITS/CVO Guiding Principles : Summary 

+-----+---+-----------------------------------------+-------------------+
| Com | > | Compatibility Criteria                  | Comments          |
| mit |   |                                         |                   |
| Le  | I |                                         |                   |
| vel | t |                                         |                   |
|     | e |                                         |                   |
| (   | m |                                         |                   |
| F/P | > |                                         |                   |
| /N) |   |                                         |                   |
|     | \ |                                         |                   |
|     | # |                                         |                   |
+=====+===+=========================================+===================+
|     | 1 | A **balanced approach** involving       |                   |
|     | . | ITS/CVO technology as well as           |                   |
|     |   | institutional changes will be used to   |                   |
|     |   | achieve measurable improvements in      |                   |
|     |   | efficiency and effectiveness for        |                   |
|     |   | carriers, drivers, governments, and     |                   |
|     |   | other CVO stakeholders. Specific        |                   |
|     |   | technology and process choices will be  |                   |
|     |   | largely **market-driven**.              |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 2 | The CVISN architecture will enable      |                   |
|     | . | **electronic information exchange**     |                   |
|     |   | among authorized stakeholders via open  |                   |
|     |   | standards.                              |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 3 | The architecture **deployment will      |                   |
|     | . | evolve incrementally**, starting with   |                   |
|     |   | legacy systems where practical and      |                   |
|     |   | proceeding in manageable steps with     |                   |
|     |   | **heavy end-user involvement**.         |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 4 | Safety assurance activities will        |                   |
|     | . | **focus resources on high risks**, and  |                   |
|     |   | be structured so as to reduce the       |                   |
|     |   | compliance costs of low-risk carriers   |                   |
|     |   | and drivers.                            |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 5 | Information technology will support     |                   |
|     | . | improved practices and procedures to    |                   |
|     |   | **improve CVO credential and tax        |                   |
|     |   | administration efficiency** for         |                   |
|     |   | carriers and government.                |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 6 | Roadside operations will **focus on     |                   |
|     | . | eliminating unsafe and illegal          |                   |
|     |   | operations by carriers, drivers, and    |                   |
|     |   | vehicles** without undue hindrance to   |                   |
|     |   | productivity and efficiency of safe and |                   |
|     |   | legal carriers and drivers.             |                   |
+-----+---+-----------------------------------------+-------------------+

### ITS/CVO Guiding Principles: General CVO

+-----+---+-----------------------------------------+-------------------+
| Com | > | Compatibility Criteria                  | Comments          |
| mit |   |                                         |                   |
| Le  | I |                                         |                   |
| vel | t |                                         |                   |
|     | e |                                         |                   |
| (   | m |                                         |                   |
| F/P | > |                                         |                   |
| /N) |   |                                         |                   |
|     | \ |                                         |                   |
|     | # |                                         |                   |
+=====+===+=========================================+===================+
|     | 1 | To the extent possible, ITS/CVO         |                   |
|     | . | technology development and deployment   |                   |
|     |   | will be **market-driven**. The federal  |                   |
|     |   | role in ITS deployment will be limited  |                   |
|     |   | to instances in which a government role |                   |
|     |   | is indispensable and in which the       |                   |
|     |   | technology is proven and reliable.      |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 2 | **Investment and participation** in     |                   |
|     | . | ITS/CVO technology will be              |                   |
|     |   | **voluntary**.                          |                   |
|     |   |                                         |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 3 | The relative benefits of various        |                   |
|     | . | ITS/CVO technology applications and     |                   |
|     |   | investments will be assessed            |                   |
|     |   | quantitatively using **measures of      |                   |
|     |   | effectiveness** and established methods |                   |
|     |   | of quality control.                     |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 4 | Potential ITS/CVO technology            |                   |
|     | . | applications will be evaluated against  |                   |
|     |   | regulatory choices involving            |                   |
|     |   | low-technology and non-technological    |                   |
|     |   | options to ensure applications are      |                   |
|     |   | **cost-effective for both government    |                   |
|     |   | and industry**.                         |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 5 | Government CVO policies and regulatory  |                   |
|     | . | practices will permit safe and legal    |                   |
|     |   | carriers and drivers to operate without |                   |
|     |   | **unnecessary regulatory and            |                   |
|     |   | administrative burdens**.               |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 6 | Stakeholders will use **technology and  |                   |
|     | . | institutional reform** to implement     |                   |
|     |   | continuous process improvement and      |                   |
|     |   | cost-effective process re-engineering.  |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 7 | The **confidentiality** of proprietary  |                   |
|     | . | and other sensitive stakeholder         |                   |
|     |   | information will be preserved.          |                   |
|     |   |                                         |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 8 | The United States CVO community will    |                   |
|     | . | work to implement **compatible          |                   |
|     |   | policies** and architecture and         |                   |
|     |   | **interoperable systems** in all        |                   |
|     |   | states.                                 |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 9 | The United States CVO community will    |                   |
|     | . | work with those in Canada, Mexico, and  |                   |
|     |   | other nations to encourage **compatible |                   |
|     |   | policies** and architecture and to      |                   |
|     |   | implement **interoperable systems**     |                   |
|     |   | throughout North America and, when      |                   |
|     |   | possible, worldwide.                    |                   |
+-----+---+-----------------------------------------+-------------------+

### ITS/CVO Guiding Principles: CVISN Architecture

+-----+---+-----------------------------------------+-------------------+
| Com | > | Compatibility Criteria                  | Comments          |
| mit |   |                                         |                   |
| Le  | I |                                         |                   |
| vel | t |                                         |                   |
|     | e |                                         |                   |
| (   | m |                                         |                   |
| F/P | > |                                         |                   |
| /N) |   |                                         |                   |
|     | \ |                                         |                   |
|     | # |                                         |                   |
+=====+===+=========================================+===================+
|     | 1 | The CVISN architecture will be          |                   |
|     | . | **open**, modular, and adaptable.       |                   |
|     |   |                                         |                   |
|     |   |                                         |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 2 | The architecture will enable **data     |                   |
|     | . | exchange** among systems, a key to      |                   |
|     |   | reaching CVO objectives. Methods used   |                   |
|     |   | to exchange data will ensure **data     |                   |
|     |   | integrity and prevent unauthorized      |                   |
|     |   | access**.                               |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 3 | Data exchange will be achieved          |                   |
|     | . | primarily via **common data             |                   |
|     |   | definitions**, message formats, and     |                   |
|     |   | communication protocols. These enable   |                   |
|     |   | development of interoperable systems by |                   |
|     |   | independent parties.                    |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 4 | A jurisdiction shall have and maintain  |                   |
|     | . | **ownership of any** data collected by  |                   |
|     |   | any agent on its behalf.                |                   |
|     |   |                                         |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 5 | The architecture will accommodate       |                   |
|     | . | **existing** and near-term              |                   |
|     |   | **communications** technologies.        |                   |
|     |   |                                         |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 6 | The architecture will accommodate       |                   |
|     | . | **proven technologies and legacy        |                   |
|     |   | systems** whenever possible.            |                   |
|     |   |                                         |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 7 | The CVISN architecture will allow       |                   |
|     | . | government and industry a **broad range |                   |
|     |   | of options**, open to competitive       |                   |
|     |   | markets, in CVO technologies.           |                   |
+-----+---+-----------------------------------------+-------------------+

### ITS/CVO Guiding Principles: CVISN Deployment

+-----+---+-----------------------------------------+-------------------+
| Com | > | Compatibility Criteria                  | Comments          |
| mit |   |                                         |                   |
| Le  | I |                                         |                   |
| vel | t |                                         |                   |
|     | e |                                         |                   |
| (   | m |                                         |                   |
| F/P | > |                                         |                   |
| /N) |   |                                         |                   |
|     | \ |                                         |                   |
|     | # |                                         |                   |
+=====+===+=========================================+===================+
|     | 1 | The feasibility of the **architecture   |                   |
|     | . | will be demonstrated incrementally** in |                   |
|     |   | simulations, prototypes, operational    |                   |
|     |   | tests, and pilots. There will be        |                   |
|     |   | **heavy end-user involvement** in each  |                   |
|     |   | step of the process.                    |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 2 | After feasibility has been              |                   |
|     | . | demonstrated, key architectural         |                   |
|     |   | elements will be incorporated into      |                   |
|     |   | appropriate national and international  |                   |
|     |   | **standards**.                          |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 3 | The architecture **deployment will      |                   |
|     | . | evolve incrementally**, starting with   |                   |
|     |   | legacy systems where practical and      |                   |
|     |   | proceeding in manageable steps.         |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 4 | **Strong federal leadership** will      |                   |
|     | . | foster voluntary cooperative efforts    |                   |
|     |   | within government jurisdictions and     |                   |
|     |   | among groups of other stakeholders to   |                   |
|     |   | develop systems which are in accord     |                   |
|     |   | with the architecture.                  |                   |
+-----+---+-----------------------------------------+-------------------+

### ITS/CVO Guiding Principles: Safety Assurance

+-----+---+-----------------------------------------+-------------------+
| Com | > | Compatibility Criteria                  | Comments          |
| mit |   |                                         |                   |
| Le  | I |                                         |                   |
| vel | t |                                         |                   |
|     | e |                                         |                   |
| (   | m |                                         |                   |
| F/P | > |                                         |                   |
| /N) |   |                                         |                   |
|     | \ |                                         |                   |
|     | # |                                         |                   |
+=====+===+=========================================+===================+
|     | 1 | **[Carriers]{.underline} and            |                   |
|     | . | [drivers]{.underline} will be           |                   |
|     |   | responsible** for the safe and legal    |                   |
|     |   | operation of commercial vehicles.       |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 2 | Jurisdictions will develop and          |                   |
|     | . | implement **uniform standards,          |                   |
|     |   | practices, procedures, and education    |                   |
|     |   | programs** to improve safety. These     |                   |
|     |   | activities will leverage market forces  |                   |
|     |   | that encourage safety.                  |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 3 | Jurisdictions **will focus** safety     |                   |
|     | . | **enforcement** resources **on high     |                   |
|     |   | risk** carriers and drivers. They will  |                   |
|     |   | remove chronic poor performers from     |                   |
|     |   | operation and help cooperative marginal |                   |
|     |   | performers to improve.                  |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 4 | Jurisdictions will conduct              |                   |
|     | . | **inspections** and **audits** to       |                   |
|     |   | provide **incentives** for carriers and |                   |
|     |   | drivers to improve poor performance and |                   |
|     |   | to collect information for assessing    |                   |
|     |   | carrier and driver performance.         |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 5 | Jurisdictions will use a **safety risk  |                   |
|     | . | rating** for all carriers based on best |                   |
|     |   | available information and common        |                   |
|     |   | criteria.                               |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 6 | Jurisdictions will identify **high risk |                   |
|     | . | drivers** based on best available       |                   |
|     |   | information and common criteria.        |                   |
|     |   |                                         |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 7 | Safety programs will provide **benefits |                   |
|     | . | which exceed costs** for carriers and   |                   |
|     |   | drivers as well as governments.         |                   |
|     |   |                                         |                   |
+-----+---+-----------------------------------------+-------------------+

### ITS/CVO Guiding Principles: Credentials & Tax

+-----+---+-----------------------------------------+-------------------+
| Com | > | Compatibility Criteria                  | Comments          |
| mit |   |                                         |                   |
| Le  | I |                                         |                   |
| vel | t |                                         |                   |
|     | e |                                         |                   |
| (   | m |                                         |                   |
| F/P | > |                                         |                   |
| /N) |   |                                         |                   |
|     | \ |                                         |                   |
|     | # |                                         |                   |
|     | > |                                         |                   |
|     |   |                                         |                   |
|     | \ |                                         |                   |
|     | # |                                         |                   |
+=====+===+=========================================+===================+
|     | 1 | **Electronic information** will be used |                   |
|     | . | in place of paper documents for the     |                   |
|     |   | administration of CVO credential and    |                   |
|     |   | tax requirements.                       |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 2 | Authorized users will be able to        |                   |
|     | . | electronically exchange credential and  |                   |
|     |   | tax-related information and funds via   |                   |
|     |   | **open standards** and transmission     |                   |
|     |   | options.                                |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 3 | The information needed to administer    |                   |
|     | . | tax and credential programs involving   |                   |
|     |   | carriers, drivers, and vehicles will be |                   |
|     |   | **available to authorized officials**,  |                   |
|     |   | on a need-to-know basis.                |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 4 | Individual jurisdictions, or their      |                   |
|     | . | designated agent, will be the           |                   |
|     |   | **authoritative source** of information |                   |
|     |   | on credentials they issue.              |                   |
+-----+---+-----------------------------------------+-------------------+

### ITS/CVO Guiding Principles: Roadside Operations

+-----+---+-----------------------------------------+-------------------+
| Com | > | Compatibility Criteria                  | Comments          |
| mit |   |                                         |                   |
| Le  | I |                                         |                   |
| vel | t |                                         |                   |
|     | e |                                         |                   |
| (   | m |                                         |                   |
| F/P | > |                                         |                   |
| /N) |   |                                         |                   |
|     | \ |                                         |                   |
|     | # |                                         |                   |
+=====+===+=========================================+===================+
|     | 1 | Roadside operations will **focus on     |                   |
|     | . | eliminating unsafe and illegal          |                   |
|     |   | operations by carriers, drivers, and    |                   |
|     |   | vehicles** and will be designed and     |                   |
|     |   | administered to accomplish this in a    |                   |
|     |   | manner that does not unduly hinder the  |                   |
|     |   | productivity and efficiency of safe and |                   |
|     |   | legal motor carriers and drivers.       |                   |
+-----+---+-----------------------------------------+-------------------+
|     | 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."   |                   |
+-----+---+-----------------------------------------+-------------------+

Note: F -- Full Commitment; P -- Partial Commitment; N -- No Commitment

Complete code descriptions are given in section 1.5.

## Fair Information Principles for ITS/CVO \[Reference 18\]

"*These fair information principles were prepared in recognition of the
importance of protecting individual privacy in implementing Intelligent
Transportation Systems (ITS) for Commercial Vehicle Operations (CVO).
They have been adopted by the ITS America CVO Technical Committee.*

*These principles represent values and are designed to be flexible and
durable to accommodate a broad scope of technological, social, and
cultural change. ITS America may, however, need to revisit them
periodically to assure their applicability and effectiveness.*

*These principles are advisory, intended to educate and guide
transportation professionals, policy-makers, and the public as they
develop fair information and privacy guidelines for specific ITS/CVO
projects. They are not intended to supersede existing statutes or
regulations. Initiators of ITS/CVO projects are urged to publish the
fair information principles that they intend to follow. Parties to
ITS/CVO projects are urged to include enforceable provisions for
safeguarding privacy in their contracts and agreements.*

+-----+-----+---------------------------------------+------------------+
| Com | I   | Compatibility Criteria                | Comments         |
| mit | tem |                                       |                  |
| Le  | \#  |                                       |                  |
| vel |     |                                       |                  |
|     |     |                                       |                  |
| (   |     |                                       |                  |
| F/P |     |                                       |                  |
| /N) |     |                                       |                  |
+=====+=====+=======================================+==================+
|     | *   | ***[Privacy]{.underline}***           |                  |
|     | **[ |                                       |                  |
|     | FIP | The reasonable expectation of privacy |                  |
|     | #1] | regarding access to and use of        |                  |
|     | {.u | personal information should be        |                  |
|     | nde | assured. The parties must be          |                  |
|     | rli | reasonable in collecting data and     |                  |
|     | ne} | protecting the confidentiality of     |                  |
|     | *** | that data.                            |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | ***[Integrity]{.underline}***         |                  |
|     | **[ |                                       |                  |
|     | FIP | Information should be protected from  |                  |
|     | #2] | improper alteration or improper       |                  |
|     | {.u | destruction.                          |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | ***[Quality]{.underline}***           |                  |
|     | **[ |                                       |                  |
|     | FIP | Information shall be accurate,        |                  |
|     | #3] | up-to-date, and relevant for the      |                  |
|     | {.u | purposes for which it is provided and |                  |
|     | nde | used.                                 |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | ***[Minimization]{.underline}***      |                  |
|     | **[ |                                       |                  |
|     | FIP | Only the minimum amount of relevant   |                  |
|     | #4] | information necessary for ITS         |                  |
|     | {.u | applications shall be collected; data |                  |
|     | nde | shall be retained for the minimum     |                  |
|     | rli | possible amount of time.              |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | ***[Accountability]{.underline}***    |                  |
|     | **[ |                                       |                  |
|     | FIP | Access to data shall be controlled    |                  |
|     | #5] | and tracked; civil and criminal       |                  |
|     | {.u | sanctions should be imposed for       |                  |
|     | nde | improper access, manipulation, or     |                  |
|     | rli | disclosure, as well as for knowledge  |                  |
|     | ne} | of such actions by others.            |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | ***[Visibility]{.underline}***        |                  |
|     | **[ |                                       |                  |
|     | FIP | There shall be disclosure to the      |                  |
|     | #6] | information providers of what data    |                  |
|     | {.u | are being collected, how they are     |                  |
|     | nde | collected, who has access to the      |                  |
|     | rli | data, and how the data will be used.  |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | ***[Anonymity]{.underline}***         |                  |
|     | **[ |                                       |                  |
|     | FIP | Data shall not be collected with      |                  |
|     | #7] | individual driver identifying         |                  |
|     | {.u | information, to the extent possible.  |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | ***[Design]{.underline}***            |                  |
|     | **[ |                                       |                  |
|     | FIP | Security should be designed into      |                  |
|     | #8] | systems from the beginning, at a      |                  |
|     | {.u | system architecture level.            |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | ***[Technology]{.underline}***        |                  |
|     | **[ |                                       |                  |
|     | FIP | Data encryption and other security    |                  |
|     | #9] | technologies shall be used to make    |                  |
|     | {.u | data worthless to unauthorized users. |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | ***[Use]{.underline}***               |                  |
|     | **[ |                                       |                  |
|     | FIP | Data collected through ITS            |                  |
|     | #   | applications should be used only for  |                  |
|     | 10] | the purposes that were publicly       |                  |
|     | {.u | disclosed.                            |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | ***[Secondary Use]{.underline}***     |                  |
|     | **[ |                                       |                  |
|     | FIP | Data collected by the private sector  |                  |
|     | #   | for its own purposes through a        |                  |
|     | 11] | voluntary investment in technology    |                  |
|     | {.u | should not be used for enforcement    |                  |
|     | nde | purposes without the carrier's        |                  |
|     | rli | consent.                              |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+

Date approved by the Board of Directors: April 22, 1999

**Note: These guiding principles address only issues of privacy and data
control. They do not address all issues related to concepts of
operations or interoperability. These issues are addressed in separate
guiding principles."**

Note: F -- Full Commitment; P -- Partial Commitment; N -- No Commitment

Complete code descriptions are given in section 1.5.

## ITS/CVO Interoperability Guiding Principles \[Reference 19\]

"These interoperability guiding principles were prepared in recognition
of the importance of promoting interoperability in the implementation of
Intelligent Transportation Systems (ITS) for Commercial Vehicle
Operations (CVO). They have been adopted by the ITS America CVO
Technical Committee.

*These principles represent values and are designed to be flexible and
durable to accommodate a broad scope of technological, social, and
cultural change. ITS America may, however, need to revisit them
periodically to assure their applicability and effectiveness.*

*These principles are advisory, intended to educate and guide
transportation professionals, policy-makers, and the public as they
develop interoperability guidelines for specific ITS/CVO projects. They
are not intended to supersede existing statutes or regulations.
Initiators of ITS/CVO projects are urged to publish the interoperability
principles that they intend to follow. Parties to ITS/CVO projects are
urged to include enforceable provisions for assuring interoperability in
their contracts and agreements.*

### ITS/CVO Interoperability Guiding Principles: General

+-----+-----+---------------------------------------+------------------+
| Com | I   | Compatibility Criteria                | Comments         |
| mit | tem |                                       |                  |
| Le  | \#  |                                       |                  |
| vel |     |                                       |                  |
|     |     |                                       |                  |
| (   |     |                                       |                  |
| F/P |     |                                       |                  |
| /N) |     |                                       |                  |
+=====+=====+=======================================+==================+
|     | *   | The CVO community will work to        |                  |
|     | **[ | implement interoperable ITS/CVO       |                  |
|     | IGP | systems in all United States          |                  |
|     | #1] | jurisdictions.                        |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | The CVO community will work with the  |                  |
|     | **[ | CVO communities in Canada and Mexico  |                  |
|     | IGP | to implement interoperable ITS/CVO    |                  |
|     | #2] | systems throughout North America.     |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | The CVO community will work to ensure |                  |
|     | **[ | that ITS/CVO systems, where           |                  |
|     | IGP | appropriate, are interoperable with   |                  |
|     | #3] | other ITS systems (e.g., electronic   |                  |
|     | {.u | toll systems).                        |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Interoperable ITS/CVO systems will be |                  |
|     | **[ | achieved through the development,     |                  |
|     | IGP | adoption, and adherence to common     |                  |
|     | #4] | standards for hardware,               |                  |
|     | {.u | systems/software, operations, and     |                  |
|     | nde | program administration.               |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Each jurisdiction will support the    |                  |
|     | **[ | national ITS/CVO information system   |                  |
|     | IGP | architecture and data exchange        |                  |
|     | #5] | standards developed under the         |                  |
|     | {.u | Commercial Vehicle Information        |                  |
|     | nde | Systems and Networks (CVISN) program. |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Transponders shall have a unique      |                  |
|     | **[ | identifier.                           |                  |
|     | IGP |                                       |                  |
|     | #6] |                                       |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Information systems supporting        |                  |
|     | **[ | electronic screening, credentials     |                  |
|     | IGP | administration, and safety assurance  |                  |
|     | #7] | will use:                             |                  |
|     | {.u |                                       |                  |
|     | nde | 7a. US DOT numbers for the            |                  |
|     | rli | identification of both interstate and |                  |
|     | ne} | intrastate motor carriers.            |                  |
|     | *** |                                       |                  |
|     |     | 7b. Commercial Drivers License (CDL)  |                  |
|     |     | numbers for the identification of     |                  |
|     |     | commercial drivers.                   |                  |
|     |     |                                       |                  |
|     |     | 7c. Vehicle Identification Numbers    |                  |
|     |     | (VIN) and license plate numbers for   |                  |
|     |     | the identification of power units.    |                  |
+-----+-----+---------------------------------------+------------------+

### ITS/CVO Interoperability Guiding Principles: Hardware

+-----+-----+---------------------------------------+------------------+
| Com | I   | Compatibility Criteria                | Comments         |
| mit | tem |                                       |                  |
| Le  | \#  |                                       |                  |
| vel |     |                                       |                  |
|     |     |                                       |                  |
| (   |     |                                       |                  |
| F/P |     |                                       |                  |
| /N) |     |                                       |                  |
+=====+=====+=======================================+==================+
|     | *   | Commercial vehicle operators will be  |                  |
|     | **[ | able to use one transponder for power |                  |
|     | IGP | unit-to-roadside communications in    |                  |
|     | #8] | support of multiple applications      |                  |
|     | {.u | including electronic screening,       |                  |
|     | nde | safety assurance, fleet and asset     |                  |
|     | rli | management, tolls, parking, and other |                  |
|     | ne} | transaction processes.                |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Public and public-private DSRC        |                  |
|     | **[ | applications will support open        |                  |
|     | IGP | standards that are consistent with    |                  |
|     | #9] | the national ITS architecture.        |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+

### ITS/CVO Interoperability Guiding Principles: Systems/Software

+-----+-----+---------------------------------------+------------------+
| Com | I   | Compatibility Criteria                | Comments         |
| mit | tem |                                       |                  |
| Le  | \#  |                                       |                  |
| vel |     |                                       |                  |
|     |     |                                       |                  |
| (   |     |                                       |                  |
| F/P |     |                                       |                  |
| /N) |     |                                       |                  |
+=====+=====+=======================================+==================+
|     | *   | Public and public-private             |                  |
|     | **[ | organizations will support open data  |                  |
|     | IGP | exchange standards for the            |                  |
|     | #   | state-state, state-federal,           |                  |
|     | 10] | state-provincial, and carrier-agency  |                  |
|     | {.u | exchange of safety and credentials    |                  |
|     | nde | information as described in the       |                  |
|     | rli | national ITS architecture.            |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+

### ITS/CVO Interoperability Guiding Principles: Operations

+-----+-----+---------------------------------------+------------------+
| Com | I   | Compatibility Criteria                | Comments         |
| mit | tem |                                       |                  |
| Le  | \#  |                                       |                  |
| vel |     |                                       |                  |
|     |     |                                       |                  |
| (   |     |                                       |                  |
| F/P |     |                                       |                  |
| /N) |     |                                       |                  |
+=====+=====+=======================================+==================+
|     | *   | Jurisdictions will support common     |                  |
|     | **[ | standards for placement of DSRC       |                  |
|     | IGP | transponders on trucks and buses to   |                  |
|     | #   | ensure the safe and cost-effective    |                  |
|     | 11] | use of transponders.                  |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Jurisdictions will support a common   |                  |
|     | **[ | set of recommended practices          |                  |
|     | IGP | concerning the selection, layout, and |                  |
|     | #   | signage of roadside screening sites   |                  |
|     | 12] | (i.e., weigh stations,                |                  |
|     | {.u | ports-of-entry, international border  |                  |
|     | nde | crossings, and temporary inspection   |                  |
|     | rli | sites) to ensure safe operations.     |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Jurisdictions will support a common   |                  |
|     | **[ | performance standard for roadside     |                  |
|     | IGP | electronic enforcement screening and  |                  |
|     | #   | passage of transponder-equipped motor |                  |
|     | 13] | carriers to ensure equity in          |                  |
|     | {.u | enforcement.                          |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Roadside electronic enforcement       |                  |
|     | **[ | screening criteria will include the   |                  |
|     | IGP | following: motor carriers must be     |                  |
|     | #   | enrolled in the jurisdiction\'s       |                  |
|     | 14] | program; must meet the                |                  |
|     | {.u | jurisdiction\'s enrollment criteria;  |                  |
|     | nde | and must meet all legal requirements  |                  |
|     | rli | established by the jurisdiction.      |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Jurisdictions will support quarterly  |                  |
|     | **[ | reviews of carrier qualifications to  |                  |
|     | IGP | ensure that the standards evolve to   |                  |
|     | #   | meet the changing needs of government |                  |
|     | 15] | and motor carriers.                   |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | A jurisdiction will not retain the    |                  |
|     | **[ | identification codes or other data    |                  |
|     | IGP | from the DSRC transponders of passing |                  |
|     | #   | motor carriers who are not enrolled   |                  |
|     | 16] | in the jurisdiction\'s program.       |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Jurisdictions will support a common   |                  |
|     | **[ | performance standard for selection of |                  |
|     | IGP | vehicles and drivers for roadside     |                  |
|     | #   | safety inspection.                    |                  |
|     | 17] |                                       |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Jurisdictions will support a common   |                  |
|     | **[ | performance standard for recording    |                  |
|     | IGP | and reporting roadside safety         |                  |
|     | #   | inspection results.                   |                  |
|     | 18] |                                       |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Jurisdictions will support a common   |                  |
|     | **[ | performance standard for reconciling  |                  |
|     | IGP | disputed roadside safety inspection   |                  |
|     | #   | results.                              |                  |
|     | 19] |                                       |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+

### ITS/CVO Interoperability Guiding Principles: Program

+-----+-----+---------------------------------------+------------------+
| Com | I   | Compatibility Criteria                | Comments         |
| mit | tem |                                       |                  |
| Le  | \#  |                                       |                  |
| vel |     |                                       |                  |
|     |     |                                       |                  |
| (F/ |     |                                       |                  |
| P/N |     |                                       |                  |
+=====+=====+=======================================+==================+
|     | *   | Motor carrier participation in        |                  |
|     | **[ | ITS/CVO roadside electronic screening |                  |
|     | IGP | programs will be voluntary; motor     |                  |
|     | #   | carriers will not be required to      |                  |
|     | 20] | purchase or operate DSRC              |                  |
|     | {.u | transponders.                         |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Motor carriers will have the option   |                  |
|     | **[ | of enrolling in any ITS/CVO roadside  |                  |
|     | IGP | electronic screening program.         |                  |
|     | #   |                                       |                  |
|     | 21] |                                       |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Jurisdictions will support uniform    |                  |
|     | **[ | criteria for enrollment of motor      |                  |
|     | IGP | carriers in ITS/CVO roadside          |                  |
|     | #   | screening programs.                   |                  |
|     | 22] |                                       |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Enrollment criteria will include      |                  |
|     | **[ | consideration of safety performance   |                  |
|     | IGP | and credentials status (e.g.,         |                  |
|     | #   | registration, fuel and highway use    |                  |
|     | 23] | taxes, and insurance).                |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | No jurisdiction will be required to   |                  |
|     | **[ | enroll motor carriers that do not     |                  |
|     | IGP | meet the criteria for enrollment.     |                  |
|     | #   |                                       |                  |
|     | 24] |                                       |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Motor carriers may obtain a DSRC      |                  |
|     | **[ | transponder from the enrolling        |                  |
|     | IGP | jurisdiction or a compatible DSRC     |                  |
|     | #   | transponder from an independent       |                  |
|     | 25] | equipment vendor of the motor         |                  |
|     | {.u | carrier\'s choice.                    |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Each jurisdiction will determine the  |                  |
|     | **[ | price and payment procedures, if any, |                  |
|     | IGP | for motor carriers to enroll and      |                  |
|     | #   | participate in its ITS/CVO electronic |                  |
|     | 26] | screening program.                    |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Jurisdictions shall work to establish |                  |
|     | **[ | business interoperability agreements  |                  |
|     | IGP | among roadside electronic screening   |                  |
|     | #   | programs.                             |                  |
|     | 27] |                                       |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | A jurisdiction will make a motor      |                  |
|     | **[ | carrier\'s DSRC transponder unique    |                  |
|     | IGP | identifier available to another       |                  |
|     | #   | jurisdiction upon written request and |                  |
|     | 28] | authorization by the motor carrier.   |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Jurisdictions will work toward        |                  |
|     | **[ | development of a single point of      |                  |
|     | IGP | contact for motor carriers enrolling  |                  |
|     | #   | in more than one ITS/CVO roadside     |                  |
|     | 29] | screening program.                    |                  |
|     | {.u |                                       |                  |
|     | nde |                                       |                  |
|     | rli |                                       |                  |
|     | ne} |                                       |                  |
|     | *** |                                       |                  |
+-----+-----+---------------------------------------+------------------+
|     | *   | Each jurisdiction will fully disclose |                  |
|     | **[ | and publish its practices and         |                  |
|     | IGP | policies governing, at a minimum:     |                  |
|     | #   |                                       |                  |
|     | 30] | 30a. Enrollment criteria;             |                  |
|     | {.u |                                       |                  |
|     | nde | 30b. Transponder unique identifier    |                  |
|     | rli | standards;                            |                  |
|     | ne} |                                       |                  |
|     | *** | 30c. Price and payment procedures for |                  |
|     |     | transponders and services;            |                  |
|     |     |                                       |                  |
|     |     | 30d. Screening standards;             |                  |
|     |     |                                       |                  |
|     |     | 30e. Use of screening event data; and |                  |
|     |     |                                       |                  |
|     |     | 30f. Business interoperability        |                  |
|     |     | agreements with other programs."      |                  |
+-----+-----+---------------------------------------+------------------+

Date approved by the Board of Directors: April 22, 1999

**Note: These guiding principles address only issues of
interoperability. They do not address all issues related to concepts of
operations or privacy and data control. These issues are addressed in
separate guiding principles."**

Note: F -- Full Commitment; P -- Partial Commitment; N -- No Commitment

Complete code descriptions are given in section 1.5.

# State Institutional Framework

The checklist in this section summarizes the institutional and business
planning steps that states should take to become ready to implement the
CVISN architecture and concepts. The checklist is based on the ideas
outlined in the January 1999 letter from the Director, Office of Motor
Carrier Safety & Technology on CVISN Workshops \[Reference 23\] and the
CVISN Model Deployment Request for Information and Request for
Application \[References 21-22\].

+-----+---+-----------------------------------+-----+------------------+
| Com | > | Compatibility Criteria            | Req | Comments         |
| mit |   |                                   | Le  |                  |
| Le  | I |                                   | vel |                  |
| vel | t |                                   | (L  |                  |
| (   | e |                                   | 1/E |                  |
| F/P | m |                                   | /C) |                  |
| /N) | > |                                   |     |                  |
|     |   |                                   | CRF |                  |
|     | \ |                                   | \#  |                  |
|     | # |                                   |     |                  |
+=====+===+===================================+=====+==================+
|     | 1 | The State has contacted or has    | L1  |                  |
|     | . | plans to contact State and local  |     |                  |
|     |   | transportation officials to       | CRF |                  |
|     |   | explore potential joint-uses of   | 1   |                  |
|     |   | transponders and ensure           | 155 |                  |
|     |   | integration among multiple        |     |                  |
|     |   | applications (i.e., CVO, toll,    |     |                  |
|     |   | traffic probes, parking           |     |                  |
|     |   | management, etc.)                 |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 2 | The State has evaluated or has    | L1  |                  |
|     | . | plans to evaluate the data that   |     |                  |
|     |   | is being collected for CVISN      | CRF |                  |
|     |   | initiatives to determine if other | 1   |                  |
|     |   | State and local transportation    | 155 |                  |
|     |   | entities (e.g., traffic           |     |                  |
|     |   | management center) outside the    |     |                  |
|     |   | CVO community could use the data  |     |                  |
|     |   | which is collected under CVISN    |     |                  |
|     |   | deployment, consistent with data  |     |                  |
|     |   | privacy agreements.               |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 3 | The State has conducted or has    | L1  |                  |
|     | . | plans to conduct outreach to its  |     |                  |
|     |   | motor carrier partners about      | CRF |                  |
|     |   | metropolitan and rural ITS        | 1   |                  |
|     |   | initiatives within the State that | 155 |                  |
|     |   | could provide benefits to its     |     |                  |
|     |   | motor carrier operations.         |     |                  |
|     |   | Examples of these initiatives     |     |                  |
|     |   | include web sites on roadway      |     |                  |
|     |   | weather information systems,      |     |                  |
|     |   | incident management systems, and  |     |                  |
|     |   | traffic management systems.       |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 4 | The State is committed to         | L1  |                  |
|     | . | complete the full cycle of the    |     |                  |
|     |   | workshops, and upon completion,   |     |                  |
|     |   | to begin deployment of the        |     |                  |
|     |   | ITS/CVO systems and services that |     |                  |
|     |   | meet the unique economic,         |     |                  |
|     |   | administrative, and               |     |                  |
|     |   | transportation needs, as outlined |     |                  |
|     |   | in the State ITS/CVO Business     |     |                  |
|     |   | Plan.                             |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 5 | A qualified core project team     | L1  |                  |
|     | . | that will participate in all      |     |                  |
|     |   | three of the workshops has been   |     |                  |
|     |   | identified. This project team     |     |                  |
|     |   | must include the following        |     |                  |
|     |   | individuals: the State's CVISN    |     |                  |
|     |   | project manager; the State's      |     |                  |
|     |   | CVISN system architect; a project |     |                  |
|     |   | facilitator/administrator, who    |     |                  |
|     |   | could be a representative of a    |     |                  |
|     |   | participating State agency or a   |     |                  |
|     |   | consultant working with the       |     |                  |
|     |   | State; operations staff           |     |                  |
|     |   | representing the agencies         |     |                  |
|     |   | responsible for the State's major |     |                  |
|     |   | CVO functional areas (i.e., IRP,  |     |                  |
|     |   | IFTA, safety information systems, |     |                  |
|     |   | roadside safety inspections, size |     |                  |
|     |   | and weight enforcement, and       |     |                  |
|     |   | credentials enforcement); staff   |     |                  |
|     |   | from the State department of      |     |                  |
|     |   | information technology or         |     |                  |
|     |   | comparable information technology |     |                  |
|     |   | units within the State CVO        |     |                  |
|     |   | agencies; representative of the   |     |                  |
|     |   | State Department of               |     |                  |
|     |   | Transportation; representatives   |     |                  |
|     |   | of the FMCSA and FHWA Division    |     |                  |
|     |   | office; and a motor carrier       |     |                  |
|     |   | industry representative           |     |                  |
|     |   | (invited). See Reference 23 for   |     |                  |
|     |   | qualification details.            |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 6 | Appropriate and sufficient staff, | L1  |                  |
|     | . | 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   |     |                  |
|     |   | (i.e., other higher-priority      |     |                  |
|     |   | projects are not competing for    |     |                  |
|     |   | the same resources).              |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 7 | A State CVO strategic plan and/or | L1  |                  |
|     | . | business plan exists and has been |     |                  |
|     |   | accepted by the FHWA (or FMCSA).  |     |                  |
|     |   | It outlines the goals,            |     |                  |
|     |   | strategies, anticipated benefits  |     |                  |
|     |   | and costs, organization,          |     |                  |
|     |   | projects, schedules, and          |     |                  |
|     |   | resources relevant to achieving   |     |                  |
|     |   | the envisioned CVO environment.   |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 8 | A planning and coordination       | L1  |                  |
|     | . | process exists which includes all |     |                  |
|     |   | State agencies involved in any    |     |                  |
|     |   | aspect of motor carrier safety    |     |                  |
|     |   | and regulation.                   |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 9 | The top executives and chief      | L1  |                  |
|     | . | information systems managers of   |     |                  |
|     |   | each involved agency have         |     |                  |
|     |   | endorsed State CVO plans and      |     |                  |
|     |   | given the CVISN project manager   |     |                  |
|     |   | adequate authority.               |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 1 | A process for resolution of       | L1  |                  |
|     | 0 | conflicts among participating     |     |                  |
|     | . | agencies exists.                  |     |                  |
|     |   |                                   |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 1 | State agencies have a strong      | L1  |                  |
|     | 1 | commitment to customer service    |     |                  |
|     | . | and the ability to work with the  |     |                  |
|     |   | motor carrier industry in their   |     |                  |
|     |   | State.                            |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 1 | State agencies involve the motor  | L1  |                  |
|     | 2 | carrier industry in the planning  |     |                  |
|     | . | process.                          |     |                  |
|     |   |                                   |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 1 | State agencies conduct education  | L1  |                  |
|     | 3 | programs to improve the safety    |     |                  |
|     | . | performance and regulatory        |     |                  |
|     |   | compliance of motor carriers.     |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 1 | State agencies provide periodic   | L1  |                  |
|     | 4 | forums for obtaining suggestions  |     |                  |
|     | . | and concerns from the motor       |     |                  |
|     |   | carrier industry.                 |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 1 | State agencies actively pursue    | L1  |                  |
|     | 5 | opportunities for and implement   |     |                  |
|     | . | business process reengineering    |     |                  |
|     |   | projects.                         |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 1 | An e-mail system is available     | L1  |                  |
|     | 6 | among agencies.                   |     |                  |
|     | . |                                   |     |                  |
|     |   |                                   |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 1 | At least key agency staff members | L1  |                  |
|     | 7 | have access to the Internet.      |     |                  |
|     | . |                                   |     |                  |
|     |   |                                   |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 1 | The State has adopted an open     | L1  |                  |
|     | 8 | standard (ANSI ASC X12, for       |     |                  |
|     | . | example) for electronic data      |     |                  |
|     |   | interchange with the public.      |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 1 | The State's communications        | L1  |                  |
|     | 9 | infrastructure is sufficiently    |     |                  |
|     | . | developed to extend to the kinds  |     |                  |
|     |   | of exchanges needed under the     |     |                  |
|     |   | CVISN Architecture.               |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 2 | There are no State legislative    | L1  |                  |
|     | 0 | barriers relative to data         |     |                  |
|     | . | privacy, physical signature       |     |                  |
|     |   | requirements, data exchange among |     |                  |
|     |   | agencies, data exchange with      |     |                  |
|     |   | other states, or other uses of    |     |                  |
|     |   | information technology required   |     |                  |
|     |   | to implement the CVISN concept of |     |                  |
|     |   | operations.                       |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 2 | The legislature provides adequate | L1  |                  |
|     | 1 | resources to support an active    |     |                  |
|     | . | ITS/CVO program and deployment of |     |                  |
|     |   | the ITS/CVO services.             |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 2 | The State participates in one or  | L1  |                  |
|     | 2 | more regional CVO forums to       |     |                  |
|     | . | assist in developing regional and |     |                  |
|     |   | national interoperable systems    |     |                  |
|     |   | and compatible policies and       |     |                  |
|     |   | procedures.                       |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 2 | The State is willing to provide   | L1  |                  |
|     | 3 | timely, electronic information to |     |                  |
|     | . | the planned clearinghouses to     |     |                  |
|     |   | support the base state            |     |                  |
|     |   | agreements.                       |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 2 | The project team has completed    | L1  |                  |
|     | 4 | the ITS/CVO technical training    |     |                  |
|     | . | courses. The first course,        |     |                  |
|     |   | Introduction to ITS/CVO, is       |     |                  |
|     |   | recommended for workshop          |     |                  |
|     |   | participants but can be waived    |     |                  |
|     |   | for personnel with prior ITS/CVO  |     |                  |
|     |   | knowledge and experience. The     |     |                  |
|     |   | second course, ITS/CVO Technical  |     |                  |
|     |   | Project Management for            |     |                  |
|     |   | Non-Technical Managers, and third |     |                  |
|     |   | course, Understanding ITS/CVO     |     |                  |
|     |   | Technology Applications, are      |     |                  |
|     |   | required for the personnel who    |     |                  |
|     |   | will represent each State at the  |     |                  |
|     |   | workshops.                        |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 2 | ~~The State has identified and    | ~~L | No longer        |
|     | 5 | made adequate progress towards    | 1~~ | applicable.      |
|     | . | the resolution of any Y2K         |     |                  |
|     |   | problems among CVO agencies. It   |     |                  |
|     |   | is strongly recommended that      |     |                  |
|     |   | States resolve any Year 2000      |     |                  |
|     |   | computer problems among CVO       |     |                  |
|     |   | agencies before beginning the     |     |                  |
|     |   | workshops.~~                      |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 2 | Effective procurement plans and   | L1  |                  |
|     | 6 | 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. |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 2 | Effective subcontract management  | L1  |                  |
|     | 7 | processes are in place and allow  |     |                  |
|     | . | timely identification and         |     |                  |
|     |   | resolution of performance         |     |                  |
|     |   | problems.                         |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 2 | The CVISN team has a clear        | L1  |                  |
|     | 8 | understanding of the              |     |                  |
|     | . | State-specific requirements for   |     |                  |
|     |   | information technology projects,  |     |                  |
|     |   | e. g., whether or not a           |     |                  |
|     |   | feasibility study is required.    |     |                  |
+-----+---+-----------------------------------+-----+------------------+
|     | 2 | The CVISN team has a clear        | L1  |                  |
|     | 9 | understanding of the              |     |                  |
|     | . | State-specific budget cycles and  |     |                  |
|     |   | is aware of constraints they      |     |                  |
|     |   | impose.                           |     |                  |
+-----+---+-----------------------------------+-----+------------------+

Note: F -- Full Commitment; P -- Partial Commitment; N -- No Commitment

L1 -- CVISN Level 1; E -- Enhanced Level of CVISN capability; C --
Complete level of CVISN capability

Complete code descriptions are given in section 1.5.

This Page Intentionally Blank

# State Systems Checklists

The checklists in this chapter describe operational concepts and
top-level requirements. The tables are divided into these categories:

-   General

-   CV Administration

-   Safety Information Exchange and Safety Assurance

-   Electronic Screening

Operational concepts and top-level requirements in the "general"
category apply to the other three categories.

For each category there are two tables.

-   The first table in each category lists Operational Concepts. The
    concepts are based on an interpretation of the guiding principles
    and the state of existing and emerging technologies today. The
    elements in each table in this section were originally based on the
    Key Operational Concepts sections of the OCD \[Reference 9\].
    Updated versions of the operational concepts are included in the
    CVISN Guide to Top-Level Design \[Reference 13\] and in the CVISN
    Guides to Safety Information Exchange, Credentials Administration,
    and Electronic Screening \[References 14-16\]. This version of the
    COACH reflects the updated concepts.

-   The second table in each category lists top-level requirements for
    the design of state systems. The tables show more detail about what
    "CVISN Level 1" means. The CVISN Level 1 requirements are marked
    with "L1" in the fourth column (Req Level (L1/E/C)). For an overview
    of CVISN Level 1, see the Introductory Guide to CVISN \[Reference
    12\].

## General Operational Concepts and State Systems Design Requirements

The general state system design requirements apply to
**[all]{.underline}** state systems. They facilitate interoperability
and the exchange of information within a single state, and across
jurisdictions. These requirements apply to safety, credentialing, and
electronic screening systems.

CRF 1048 authorized updating CVISN documents to reflect FMCSA's new
policy on credentials administration. The policy change resulted from
analyzing the results of a survey about electronic credentialing
interactions between motor carriers and state information systems (see
Reference 38). The new policy is:

-   FMCSA [requires]{.underline} that states implement either a
    person-to-computer or a computer-to-computer interface.

-   FMCSA [recommends]{.underline} that states survey their stakeholders
    to determine whether both interfaces would be appropriate.

-   FMCSA [recommends]{.underline} that, in the near term (over the next
    \~2 years), carriers and states use X12 EDI for computer-to-computer
    interfaces unless the state has evidence that customers support
    another approach.

-   FMCSA [encourages]{.underline} the exploration of XML as an
    alternative to EDI.

This is a policy regarding CVISN Level 1. If a state chooses to
implement only a person-to-computer credentialing approach, then
implementation of a computer-to-computer interface is considered an
Enhanced capability. Similarly, if a state chooses to implement only a
computer-to-computer credentialing approach, then implementation of a
person-to-computer interface is considered an Enhanced capability. The
tables in this section have been updated accordingly.

The concepts in the following table are based on an interpretation of
the guiding principles and the state of existing and emerging
technologies today. The elements in this table were originally based on
the Key Operational Concepts sections of the OCD \[Reference 9\].
Updated versions of the operational concepts are included in the CVISN
Guide to Top-Level Design \[Reference 13\] and in the CVISN Guides to
Safety Information Exchange, Credentials Administration, and Electronic
Screening \[References 14-16\]. This version of the COACH reflects the
updated concepts.

Table 4.1‑1 General Operational Concepts

+-----+---+----------------------------------+--------+----------------+
| Com | > | Compatibility Criteria           | Req    | Comments       |
| mit |   |                                  | Level  |                |
| Le  | I |                                  |        |                |
| vel | t |                                  | (L     |                |
|     | e |                                  | 1/E/C) |                |
| (   | m |                                  |        |                |
| F/P | > |                                  | CRF \# |                |
| /N) |   |                                  |        |                |
|     | \ |                                  |        |                |
|     | # |                                  |        |                |
+=====+===+==================================+========+================+
|     | 1 | Good business processes can be   | L1     |                |
|     | . | enhanced through improved        |        |                |
|     |   | automated access to accurate     |        |                |
|     |   | information.                     |        |                |
+-----+---+----------------------------------+--------+----------------+
|     | 2 | Authoritative sources are        | L1     |                |
|     | . | responsible for maintaining      |        |                |
|     |   | accurate information. Each       |        |                |
|     |   | jurisdiction participating in    |        |                |
|     |   | ITS/CVO information exchange     |        |                |
|     |   | identifies the authoritative     |        |                |
|     |   | source for each data item.       |        |                |
+-----+---+----------------------------------+--------+----------------+
|     | 3 | Sometimes it is practical for    | L1     |                |
|     | . | authoritative systems to         |        |                |
|     |   | authorize indirect sources to    |        |                |
|     |   | assist in the information        |        |                |
|     |   | exchange process.                |        |                |
+-----+---+----------------------------------+--------+----------------+
|     | 4 | To enable cross-referencing and  | L1 --  |                |
|     | . | standard look-ups in multiple    | inte   |                |
|     |   | information systems, a common    | rstate |                |
|     |   | scheme for identifying carriers  |        |                |
|     |   | must be adopted. The Primary     | C --   |                |
|     |   | Carrier ID should be used in     | intr   |                |
|     |   | interface agreements (open       | astate |                |
|     |   | standards, Internet-based        |        |                |
|     |   | exchanges, and custom interface  |        |                |
|     |   | agreements) to facilitate the    |        |                |
|     |   | exchange of carrier information. |        |                |
|     |   | How the ID is stored internally  |        |                |
|     |   | outside the interface is up to   |        |                |
|     |   | the system implementers. The ID  |        |                |
|     |   | should be based on the USDOT     |        |                |
|     |   | number for both interstate and   |        |                |
|     |   | intrastate carriers. If it is    |        |                |
|     |   | not feasible for the state to    |        |                |
|     |   | use USDOT number as the ID type  |        |                |
|     |   | for all intrastate carriers,     |        |                |
|     |   | then the state should establish  |        |                |
|     |   | some convention for the Primary  |        |                |
|     |   | Carrier ID that will apply to    |        |                |
|     |   | all intrastate carriers in that  |        |                |
|     |   | state.                           |        |                |
+-----+---+----------------------------------+--------+----------------+
|     | 5 | To enable cross-referencing and  | L1     |                |
|     | . | standard look-ups in multiple    |        |                |
|     |   | information systems, a common    |        |                |
|     |   | scheme for identifying drivers   |        |                |
|     |   | must be adopted for interstate   |        |                |
|     |   | and intrastate operators. The    |        |                |
|     |   | Commercial Drivers License (CDL) |        |                |
|     |   | number should be the basis of    |        |                |
|     |   | the Driver ID.                   |        |                |
+-----+---+----------------------------------+--------+----------------+
|     | 6 | To enable cross-referencing and  | L1     |                |
|     | . | standard look-ups in multiple    |        |                |
|     |   | information systems, a common    |        |                |
|     |   | scheme for identifying vehicles  |        |                |
|     |   | must be adopted for interstate   |        |                |
|     |   | and intrastate operators. The    |        |                |
|     |   | Vehicle Identification Numbers   |        |                |
|     |   | (VIN) and jurisdiction plus      |        |                |
|     |   | license plate numbers should be  |        |                |
|     |   | the bases for the identification |        |                |
|     |   | of power units.                  |        |                |
+-----+---+----------------------------------+--------+----------------+
|     | 7 | To enable cross-referencing and  | E      |                |
|     | . | standard look-ups in multiple    |        |                |
|     |   | information systems, a common    |        |                |
|     |   | scheme for identifying           |        |                |
|     |   | international trips must be      |        |                |
|     |   | adopted. The Trip/Load number    |        |                |
|     |   | consisting of DUNS and           |        |                |
|     |   | trip-specific ID should be the   |        |                |
|     |   | basis for identifying            |        |                |
|     |   | international trips.             |        |                |
+-----+---+----------------------------------+--------+----------------+
|     | 8 | Standard information exchange is | L1 --  |                |
|     | . | supported via carrier and        | c      |                |
|     |   | vehicle (and eventually driver)  | arrier |                |
|     |   | snapshots.                       | &      |                |
|     |   |                                  | v      |                |
|     |   |                                  | ehicle |                |
|     |   |                                  |        |                |
|     |   |                                  | C --   |                |
|     |   |                                  | driver |                |
+-----+---+----------------------------------+--------+----------------+
|     | 9 | Flexible                         | L1     |                |
|     | . | implementation/deployment        |        |                |
|     |   | options are accommodated by the  |        |                |
|     |   | ITS/CVO architecture. As         |        |                |
|     |   | technology changes, so will the  |        |                |
|     |   | architecture.                    |        |                |
+-----+---+----------------------------------+--------+----------------+
|     | 1 | Open standards are used for      | L1     |                |
|     | 0 | interchanges between public and  |        |                |
|     | . | private computer systems. Today, | CRF    |                |
|     |   | ANSI ASC X12 EDI transactions    | 1048   |                |
|     |   | are used for some carrier-state  |        |                |
|     |   | information systems'             | CRF    |                |
|     |   | interactions. We anticipate that | 1164   |                |
|     |   | XML will be also used in the     |        |                |
|     |   | future. DSRC standards for the   |        |                |
|     |   | messages, data link, and         |        |                |
|     |   | physical layers are used for     |        |                |
|     |   | vehicle-roadside interactions.   |        |                |
+-----+---+----------------------------------+--------+----------------+
|     | 1 | Enhanced data exchange will      | L1     |                |
|     | 1 | allow all activities to focus    |        |                |
|     | . | resources on high risk           |        |                |
|     |   | operators.                       |        |                |
+-----+---+----------------------------------+--------+----------------+
|     | 1 | Interoperability is assured by a | L1     |                |
|     | 2 | process of architecture          |        |                |
|     | . | conformance checks throughout a  |        |                |
|     |   | project's lifecycle, culminating |        |                |
|     |   | in execution of standardized     |        |                |
|     |   | interoperability tests. If a     |        |                |
|     |   | tested system is changed, the    |        |                |
|     |   | interoperability tests are       |        |                |
|     |   | re-run as part of the            |        |                |
|     |   | re-validation process.           |        |                |
+-----+---+----------------------------------+--------+----------------+
|     | 1 | The Fair Information Principles  | L1     |                |
|     | 3 | 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.        |        |                |
+-----+---+----------------------------------+--------+----------------+
|     | 1 | Citations are based on a review  | L1     |                |
|     | 4 | of real-time conditions and      |        |                |
|     | . | checks with authoritative        |        |                |
|     |   | sources.                         |        |                |
+-----+---+----------------------------------+--------+----------------+
|     | 1 | The Internet is used as a wide   | L1     |                |
|     | 5 | area network for information     |        |                |
|     | . | exchange.                        | CRF    |                |
|     |   |                                  | 1084   |                |
+-----+---+----------------------------------+--------+----------------+
|     | 1 | The World Wide Web is used for   | L1     |                |
|     | 6 | interactions and information     |        |                |
|     | . | exchanges between private people | CRF    |                |
|     |   | and government systems (e. g.,   | 1048   |                |
|     |   | for credentials applications or  |        |                |
|     |   | commercial vehicle regulations). | CRF    |                |
|     |   |                                  | 1164   |                |
+-----+---+----------------------------------+--------+----------------+
|     | 1 | The focus is on sharing data     | L1     |                |
|     | 7 | among safety, credentialing and  |        |                |
|     | . | screening processes. The CVISN   | CRF    |                |
|     |   | Program is structured to         | 632    |                |
|     |   | encourage states to design and   |        |                |
|     |   | deploy these three elements in   |        |                |
|     |   | parallel.                        |        |                |
+-----+---+----------------------------------+--------+----------------+

Note: F -- Full Commitment; P -- Partial Commitment; N -- No Commitment

L1 -- CVISN Level 1; E -- Enhanced Level of CVISN capability; C --
Complete level of CVISN capability

Complete code descriptions are given in section 1.5.

The top-level requirements in the following table apply to the design of
all state systems. The table shows more detail about what "CVISN Level
1" means. The CVISN Level 1 requirements are marked with "L1" in the
fourth column (Req Level (L1/E/C)). For an overview of CVISN Level 1,
see the Introductory Guide to CVISN \[Reference 12\].

Table 4.1‑2 General State Systems Design Requirements Checklist

+----+---+----------------------------+-----+---+---+---+--------------+
| >  | > | Compatibility Criteria     | >   | > | > | > | Comments     |
| Co |   |                            | Req |   |   |   |              |
| mm | I |                            | >   | O | I | F |              |
| it | t |                            |  le | p | O | O |              |
| >  | e |                            | vel | > | C | C |              |
|  L | m |                            | >   |   | > | > |              |
| ev | > |                            |  (L | T |   |   |              |
| el |   |                            | 1/E | e | D | D |              |
| >  | \ |                            | /C) | s | a | a |              |
|  ( | # |                            | >   | t | t | t |              |
| F/ |   |                            | >   | > | e | e |              |
| P/ |   |                            | CRF |   |   |   |              |
| N) |   |                            | >   | D |   |   |              |
|    |   |                            |  \# | a |   |   |              |
|    |   |                            |     | t |   |   |              |
|    |   |                            |     | e |   |   |              |
+====+===+============================+=====+===+===+===+==============+
|    | * | Adopt standard identifiers | L1  |   |   |   |              |
|    | * | for carriers, vehicles,    |     |   |   |   |              |
|    | 4 | drivers, and transponders  |     |   |   |   |              |
|    | . | to support information     |     |   |   |   |              |
|    | 1 | exchange.                  |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Adopt standard identifiers | L1  |   |   |   |              |
|    |   | for interstate carrier,    |     |   |   |   |              |
|    |   | vehicle, driver, and       |     |   |   |   |              |
|    |   | transponder.               |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Adopt standard identifiers | C   |   |   |   |              |
|    |   | for intrastate carrier,    |     |   |   |   |              |
|    |   | vehicle, driver, and       |     |   |   |   |              |
|    |   | transponder.               |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Use the World Wide Web for | L   |   |   |   | See the note |
|    | * | person-to-computer         | 1;E |   |   |   | about CRF    |
|    | 4 | interactions between       |     |   |   |   | 1048 for     |
|    | . | private citizens and state | CRF |   |   |   | cr           |
|    | 1 | information systems.       | 1   |   |   |   | edentialing, |
|    | . |                            | 048 |   |   |   | above.       |
|    | 2 |                            |     |   |   |   |              |
|    | * |                            | CRF |   |   |   |              |
|    | * |                            | 1   |   |   |   |              |
|    |   |                            | 164 |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Use open standards for     | L1; |   |   |   | See the note |
|    | * | computer-to-computer       | E   |   |   |   | about CRF    |
|    | 4 | exchange of information    |     |   |   |   | 1048 for     |
|    | . | with other jurisdictions   | CRF |   |   |   | cr           |
|    | 1 | and with the public.       | 1   |   |   |   | edentialing, |
|    | . |                            | 048 |   |   |   | above.       |
|    | 3 |                            |     |   |   |   |              |
|    | * |                            | CRF |   |   |   |              |
|    | * |                            | 1   |   |   |   |              |
|    |   |                            | 164 |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Use ANSI X12 EDI standards | L1; |   |   |   | See the note |
|    |   | for transactions between   | E   |   |   |   | about CRF    |
|    |   | state information systems  |     |   |   |   | 1048 for     |
|    |   | and private systems (CV    |     |   |   |   | cr           |
|    |   | operators, insurance       |     |   |   |   | edentialing, |
|    |   | companies, etc.).          |     |   |   |   | above; EDI   |
|    |   |                            |     |   |   |   | is           |
|    |   |                            |     |   |   |   | recommended  |
|    |   |                            |     |   |   |   | in the near  |
|    |   |                            |     |   |   |   | term.        |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Use ANSI X12 EDI standards | L1; |   |   |   | See the note |
|    |   | for transactions between   | E   |   |   |   | about CRF    |
|    |   | state information systems  |     |   |   |   | 1048 for     |
|    |   | and CVISN Core             |     |   |   |   | cr           |
|    |   | Infrastructure systems,    |     |   |   |   | edentialing, |
|    |   | where available.           |     |   |   |   | above; EDI   |
|    |   |                            |     |   |   |   | is           |
|    |   |                            |     |   |   |   | recommended  |
|    |   |                            |     |   |   |   | in the near  |
|    |   |                            |     |   |   |   | term.        |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 3 | Use XML standards for      | E   |   |   |   |              |
|    |   | transactions between state |     |   |   |   |              |
|    |   | information systems and    |     |   |   |   |              |
|    |   | private systems (CV        |     |   |   |   |              |
|    |   | operators, insurance       |     |   |   |   |              |
|    |   | companies, etc.)           |     |   |   |   |              |
|    |   | (contingent on             |     |   |   |   |              |
|    |   | demonstration of           |     |   |   |   |              |
|    |   | feasibility).              |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Ensure that all            | L1  |   |   |   |              |
|    | * | information transfers, fee |     |   |   |   |              |
|    | 4 | payments, and money        |     |   |   |   |              |
|    | . | transfers are authorized   |     |   |   |   |              |
|    | 1 | and secure.                |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 4 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Exchange safety and        | L1  |   |   |   |              |
|    | * | credentials data           |     |   |   |   |              |
|    | 4 | electronically within the  |     |   |   |   |              |
|    | . | state to support           |     |   |   |   |              |
|    | 1 | credentialing, safety, and |     |   |   |   |              |
|    | . | other roadside functions.  |     |   |   |   |              |
|    | 5 | Where useful, exchange     |     |   |   |   |              |
|    | * | snapshots.                 |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Data for interstate        | L1  |   |   |   |              |
|    |   | carriers                   |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Data for interstate        | L1  |   |   |   |              |
|    |   | vehicles                   |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 3 | Data for intrastate        | E   |   |   |   |              |
|    |   | carriers                   |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 4 | Data for intrastate        | E   |   |   |   |              |
|    |   | vehicles                   |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 5 | Data for drivers           | C   |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Demonstrate technical      | L1  |   |   |   |              |
|    | * | interoperability by        |     |   |   |   |              |
|    | 4 | performing                 |     |   |   |   |              |
|    | . | Interoperability Tests.    |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 6 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Support electronic         | E   |   |   |   |              |
|    | * | payments.                  |     |   |   |   |              |
|    | 4 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 7 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Receive, collect, and      | E   |   |   |   |              |
|    | * | archive relevant CVO data  |     |   |   |   |              |
|    | 4 | for historical, secondary, | CRF |   |   |   |              |
|    | . | and non-real-time uses.    | 1   |   |   |   |              |
|    | 1 |                            | 047 |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 8 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+

Note: F -- Full Commitment; P -- Partial Commitment; N -- No Commitment

L1 -- CVISN Level 1; E -- Enhanced Level of CVISN capability; C --
Complete level of CVISN capability

Complete code descriptions are given in section 1.5.

## State Safety Information Exchange and Safety Assurance Systems Design Requirements

The state safety information exchange and safety assurance systems are
likely to consist of:

-   Inspection (e.g., ASPEN)

-   SAFETYNET

-   Citation & Accident

-   Compliance Review (e.g., CAPRI (Compliance Analysis Performance
    Review Information))

-   CV Information Exchange Window (CVIEW)

The state CV safety information exchange and safety assurance systems
will operate at one or more (generally) fixed locations within a state.
The systems perform safety information exchange and safety assurance
functions supporting safety regulations. States may form regional
alliances to support these functions. Each state coordinates with other
states, regional alliances, and CVISN Core Infrastructure systems to
support nationwide access to safety information for administrative and
enforcement functions.

The concepts in the following table are based on an interpretation of
the guiding principles and the state of existing and emerging
technologies today. The elements in this table were originally based on
the Key Operational Concepts sections of the OCD \[Reference 9\].
Updated versions of the operational concepts are included in the CVISN
Guide to Top-Level Design \[Reference 13\] and in the CVISN Guide to
Safety Information Exchange \[Reference 14\]. This version of the COACH
reflects the updated concepts.

Table 4.2‑3 Safety Information Exchange and Safety Assurance Operational
Concepts

+-----+---+----------------------------------+------+------------------+
| Com | > | Compatibility Criteria           | Req  | Comments         |
| mit |   |                                  | L    |                  |
| Le  | I |                                  | evel |                  |
| vel | t |                                  | (L1/ |                  |
| (   | e |                                  | E/C) |                  |
| F/P | m |                                  |      |                  |
| /N) | > |                                  | CRF  |                  |
|     |   |                                  | \#   |                  |
|     | \ |                                  |      |                  |
|     | # |                                  |      |                  |
+=====+===+==================================+======+==================+
|     | 1 | Data are collected to quantify   | L1   |                  |
|     | . | the primary measures of          |      |                  |
|     |   | effectiveness related to safety  |      |                  |
|     |   | of CVO (accidents and            |      |                  |
|     |   | fatalities).                     |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 2 | Electronic safety records        | L1   |                  |
|     | . | (snapshots) are made available   |      |                  |
|     |   | at the roadside to aid           |      |                  |
|     |   | inspectors and other enforcement |      |                  |
|     |   | personnel.                       |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 3 | Inspectors use computer          | L1   |                  |
|     | . | applications to capture, verify, |      |                  |
|     |   | and submit intrastate and        |      |                  |
|     |   | interstate inspection data at    |      |                  |
|     |   | the point of inspection.         |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 4 | Safety data are made available   | L1   |                  |
|     | . | electronically to qualified      |      |                  |
|     |   | stakeholders.                    |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 5 | User access to data is           | L1   |                  |
|     | . | controlled (restricted and/or    |      |                  |
|     |   | monitored) where necessary.      |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 6 | Mechanisms are made available    | L1   |                  |
|     | . | for operators to dispute safety  |      |                  |
|     |   | records held by government       |      |                  |
|     |   | systems.                         |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 7 | Compliance reviews are supported | E    |                  |
|     | . | through electronic access to     |      |                  |
|     |   | government-held safety records.  |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 8 | Safety risk ratings are          | E    |                  |
|     | . | determined according to uniform  |      |                  |
|     |   | guidelines.                      |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 9 | Jurisdictions support a standard | E    |                  |
|     | . | set of criteria for inspection   |      |                  |
|     |   | selection.                       |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 1 | A comprehensive safety policy,   | C    |                  |
|     | 0 | including roadside and deskside  |      |                  |
|     | . | activities, is implemented to    |      |                  |
|     |   | improve safety.                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 1 | Carriers are associated with a   | C    |                  |
|     | 1 | base state for safety            |      |                  |
|     | . | information record storage and   |      |                  |
|     |   | credentialing.                   |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 1 | Compliance reviews are supported | C    |                  |
|     | 2 | through electronic access to     |      |                  |
|     | . | carrier-held records.            |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+

Note: F -- Full Commitment; P -- Partial Commitment; N -- No Commitment

L1 -- CVISN Level 1; E -- Enhanced Level of CVISN capability; C --
Complete level of CVISN capability

Complete code descriptions are given in section 1.5.

The top-level requirements in the following table apply to the design of
state safety-related systems. The table shows more detail about what
"CVISN Level 1" means. The CVISN Level 1 requirements are marked with
"L1" in the fourth column (Req Level (L1/E/C)). For an overview of CVISN
Level 1, see the Introductory Guide to CVISN \[Reference 12\].

Table 4.2‑4 State Safety Information Exchange and Safety Assurance
Systems Design Requirements Checklist

+----+---+----------------------------+-----+---+---+---+--------------+
| >  | > | Compatibility Criteria     | >   | > | > | > | Comments     |
| Co |   |                            | Req |   |   |   |              |
| mm | I |                            | >   | O | I | F |              |
| it | t |                            |  Le | p | O | O |              |
| >  | e |                            | vel | > | C | C |              |
|  L | m |                            | >   |   | > | > |              |
| ev | > |                            |  (L | T |   |   |              |
| el |   |                            | 1/E | e | D | D |              |
| >  | \ |                            | /C) | s | a | a |              |
|  ( | # |                            | >   | t | t | t |              |
| F/ |   |                            | >   | > | e | e |              |
| P/ |   |                            | CRF |   |   |   |              |
| N) |   |                            | >   | D |   |   |              |
|    |   |                            |  \# | a |   |   |              |
|    |   |                            |     | t |   |   |              |
|    |   |                            |     | e |   |   |              |
+====+===+============================+=====+===+===+===+==============+
|    | * | Use ASPEN (or equivalent)  | L1  |   |   |   |              |
|    | * | at all major inspection    |     |   |   |   |              |
|    | 4 | sites                      |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Select vehicles and        | L1  |   |   |   |              |
|    |   | drivers for inspection     |     |   |   |   |              |
|    |   | based on availability of   |     |   |   |   |              |
|    |   | inspector, standard        |     |   |   |   |              |
|    |   | inspection selection       |     |   |   |   |              |
|    |   | system, vehicle measures,  |     |   |   |   |              |
|    |   | and random process, as     |     |   |   |   |              |
|    |   | statutes permit.           |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Report interstate          | L1  |   |   |   |              |
|    |   | inspections to MCMIS via   |     |   |   |   |              |
|    |   | SAFETYNET                  |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 3 | Report intrastate          | L1  |   |   |   |              |
|    |   | inspections to SAFETYNET   |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 4 | Submit interstate and      | L1  |   |   |   |              |
|    |   | intrastate inspections for |     |   |   |   |              |
|    |   | 45-day storage to SAFER.   |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 5 | Periodically check OOS     | E   |   |   |   |              |
|    |   | orders issued in the state |     |   |   |   |              |
|    |   | to focus enforcement and   |     |   |   |   |              |
|    |   | safety assurance           |     |   |   |   |              |
|    |   | activities.                |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 6 | To assist in inspection,   | C   |   |   |   |              |
|    |   | use DSRC to retrieve       |     |   |   |   |              |
|    |   | summary vehicle safety     |     |   |   |   |              |
|    |   | sensor data, if driver     |     |   |   |   |              |
|    |   | allows and vehicle is      |     |   |   |   |              |
|    |   | properly equipped.         |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 7 | To assist in inspection,   | C   |   |   |   |              |
|    |   | use DSRC to retrieve       |     |   |   |   |              |
|    |   | driver's daily log, if     |     |   |   |   |              |
|    |   | driver allows and vehicle  |     |   |   |   |              |
|    |   | is properly equipped.      |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 8 | Use                        | C   |   |   |   |              |
|    |   | electronically-generated   |     |   |   |   |              |
|    |   | driver's daily log, if     |     |   |   |   |              |
|    |   | driver offers as an        |     |   |   |   |              |
|    |   | alternative to a           |     |   |   |   |              |
|    |   | manually-maintained log    |     |   |   |   |              |
|    |   | during an inspection.      |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | SAFETYNET 2000 submits     | L1  |   |   |   |              |
|    | * | interstate and intrastate  |     |   |   |   |              |
|    | 4 | inspections reports to     |     |   |   |   |              |
|    | . | SAFER.                     |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Maintain snapshots (or     | E   |   |   |   |              |
|    | * | equivalent information)    |     |   |   |   |              |
|    | 4 | for operators based in the | CRF |   |   |   |              |
|    | . | state and make available   | 827 |   |   |   |              |
|    | 2 | to within-state            |     |   |   |   |              |
|    | . | information systems and    |     |   |   |   |              |
|    | 3 | users.                     |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | For any given snapshot,    | E   |   |   |   |              |
|    |   | there is only one          |     |   |   |   |              |
|    |   | authoritative source (or   | CRF |   |   |   |              |
|    |   | group of authoritative     | 827 |   |   |   |              |
|    |   | sources, such as ASPEN     |     |   |   |   |              |
|    |   | units) for each field in   |     |   |   |   |              |
|    |   | that snapshot.             |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Allow only the             | E   |   |   |   |              |
|    |   | authoritative source to    |     |   |   |   |              |
|    |   | update a snapshot data     | CRF |   |   |   |              |
|    |   | field, with the following  | 827 |   |   |   |              |
|    |   | exception:                 |     |   |   |   |              |
|    |   |                            |     |   |   |   |              |
|    |   | -   A "super user" can     |     |   |   |   |              |
|    |   |     update any field. An   |     |   |   |   |              |
|    |   |     audit trail should be  |     |   |   |   |              |
|    |   |     maintained to record   |     |   |   |   |              |
|    |   |     super user updates.    |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 3 | Validate the sender's      | E   |   |   |   |              |
|    |   | identity through some      |     |   |   |   |              |
|    |   | industry-standard means    | CRF |   |   |   |              |
|    |   | (account ID, IP address,   | 827 |   |   |   |              |
|    |   | password, security keys, . |     |   |   |   |              |
|    |   | . .).                      |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 4 | Reject updates attempted   | E   |   |   |   |              |
|    |   | by any system other than   |     |   |   |   |              |
|    |   | the authoritative source   | CRF |   |   |   |              |
|    |   | or a super user with a     | 827 |   |   |   |              |
|    |   | code explaining why. The   |     |   |   |   |              |
|    |   | rejection transaction      |     |   |   |   |              |
|    |   | should be returned to the  |     |   |   |   |              |
|    |   | sender in a timely         |     |   |   |   |              |
|    |   | fashion. The rejection     |     |   |   |   |              |
|    |   | should be logged for the   |     |   |   |   |              |
|    |   | snapshot system            |     |   |   |   |              |
|    |   | administrator to review.   |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Use CAPRI (or equivalent)  | L1  |   |   |   |              |
|    | * | for compliance reviews.    |     |   |   |   |              |
|    | 4 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 4 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Report interstate          | L1  |   |   |   |              |
|    |   | compliance reviews to      |     |   |   |   |              |
|    |   | MCMIS via SAFETYNET        |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Collect, store, analyze,   | E   |   |   |   |              |
|    | * | and distribute citation    |     |   |   |   |              |
|    | 4 | data electronically.       |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 5 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Report citations for       | E   |   |   |   |              |
|    |   | interstate operators to    |     |   |   |   |              |
|    |   | MCMIS via SAFETYNET        |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Collect, store, analyze,   | E   |   |   |   |              |
|    | * | and distribute crash data  |     |   |   |   |              |
|    | 4 | electronically.            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 6 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Report interstate crashes  | E   |   |   |   |              |
|    |   | as required to MCMIS via   |     |   |   |   |              |
|    |   | SAFETYNET                  |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Compute carrier safety     | E   |   |   |   |              |
|    | * | risk rating for intrastate |     |   |   |   |              |
|    | 4 | carriers based on safety   |     |   |   |   |              |
|    | . | data collected.            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 7 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Identify high risk drivers | C   |   |   |   |              |
|    | * | based in the state through |     |   |   |   |              |
|    | 4 | regular performance        |     |   |   |   |              |
|    | . | evaluation of various      |     |   |   |   |              |
|    | 2 | factors such as license    |     |   |   |   |              |
|    | . | status, points, and        |     |   |   |   |              |
|    | 8 | inspections.               |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+

Note: F -- Full Commitment; P -- Partial Commitment; N -- No Commitment

L1 -- CVISN Level 1; E -- Enhanced Level of CVISN capability; C --
Complete level of CVISN capability

Complete code descriptions are given in section 1.5.

## State CV Administration Systems Design Requirements

The state CV administrative systems are likely to consist of:

-   Interstate & Intrastate Vehicle Registration

-   Fuel Tax Credentialing/Tax Return Processing

-   Credentialing Interface

-   Web Site (CRF 1084)

-   Carrier Registration (SSRS)

-   Driver licensing

-   Titling

-   Treasury or Revenue

-   HazMat Credentialing/Permitting

-   Oversize/Overweight Permitting

-   Electronic Screening Enrollment -- see section 4.4 on Electronic
    Screening (CRF 1172)

These systems operate at one or more (generally) fixed locations within
a state. The systems perform administrative functions supporting
credentials and tax regulations. States may form regional alliances to
support these functions. Each state coordinates with other states,
regional alliances, and CVISN Core Infrastructure systems to support
nationwide access to credentials information for administrative and
enforcement functions.

When building a credentialing system, it is useful to think about the
process of electronic screening enrollment as part of the design
criteria. The requirements for Electronic Screening Enrollment have been
moved to the section on Electronic Screening, since the enrollment would
not occur unless operators wanted to participate in electronic
screening. CRF 1172 authorized this change.

CRF 1048 authorized updating CVISN documents to reflect FMCSA's new
policy on credentials administration. The policy change resulted from
analyzing the results of a survey about electronic credentialing
interactions between motor carriers and state information systems (see
Reference 38). The new policy is:

-   FMCSA [requires]{.underline} that states implement either a
    person-to-computer or a computer-to-computer interface.

-   FMCSA [recommends]{.underline} that states survey their stakeholders
    to determine whether both interfaces would be appropriate.

-   FMCSA [recommends]{.underline} that, in the near term (over the next
    \~2 years), carriers and states use X12 EDI for computer-to-computer
    interfaces unless the state has evidence that customers support
    another approach.

-   FMCSA [encourages]{.underline} the exploration of XML as an
    alternative to EDI.

This is a policy regarding CVISN Level 1. If a state chooses to
implement only a person-to-computer credentialing approach, then
implementation of a computer-to-computer interface is considered an
Enhanced capability. Similarly, if a state chooses to implement only a
computer-to-computer credentialing approach, then implementation of a
person-to-computer interface is considered an Enhanced capability. The
tables in this section have been updated accordingly.

The concepts in the following table are based on an interpretation of
the guiding principles and the state of existing and emerging
technologies today. The elements in this table were originally based on
the Key Operational Concepts sections of the OCD \[Reference 9\].
Updated versions of the operational concepts are included in the CVISN
Guide to Top-Level Design \[Reference 13\] and in the CVISN Guide to
Credentials Administration \[Reference 15\]. This version of the COACH
reflects the updated concepts.

Table 4.3‑5 CV Administration Operational Concepts

+-----+---+----------------------------------+------+------------------+
| Com | > | Compatibility Criteria           | Req  | Comments         |
| mit |   |                                  | L    |                  |
| Le  | I |                                  | evel |                  |
| vel | t |                                  |      |                  |
|     | e |                                  | (L1/ |                  |
| (   | m |                                  | E/C) |                  |
| F/P | > |                                  |      |                  |
| /N) |   |                                  | CRF  |                  |
|     | \ |                                  | \#   |                  |
|     | # |                                  |      |                  |
+=====+===+==================================+======+==================+
|     | 1 | Credential applications and fuel | L1   |                  |
|     | . | tax returns are filed            |      |                  |
|     |   | electronically from CVO          |      |                  |
|     |   | stakeholder facilities.          |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 2 | Internal state administrative    | L1   |                  |
|     | . | processes are supported through  |      |                  |
|     |   | electronic exchange of           |      |                  |
|     |   | application data, safety         |      |                  |
|     |   | records, carrier background      |      |                  |
|     |   | data, and other government-held  |      |                  |
|     |   | records.                         |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 3 | IRP and IFTA base state          | L1   |                  |
|     | . | agreements are supported         |      |                  |
|     |   | electronically.                  |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 4 | Credential and fuel tax payment  | L1   |                  |
|     | . | status information for           |      |                  |
|     |   | interstate operators are made    |      |                  |
|     |   | available electronically         |      |                  |
|     |   | nationally to qualified          |      |                  |
|     |   | stakeholders.                    |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 5 | User access to data is           | L1   |                  |
|     | . | controlled (restricted and/or    |      |                  |
|     |   | monitored) where necessary.      |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 6 | Mechanisms are made available    | L1   |                  |
|     | . | for operators to dispute         |      |                  |
|     |   | credentials records held by      |      |                  |
|     |   | government systems.              |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 7 | Fees and taxes are paid          | E    |                  |
|     | . | electronically.                  |      |                  |
|     |   |                                  |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 8 | Electronic access to             | E    |                  |
|     | . | administrative processes and     |      |                  |
|     |   | information is available from    |      |                  |
|     |   | "one stop shops" in public       |      |                  |
|     |   | sites.                           |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 9 | Credential and fuel tax payment  | E    |                  |
|     | . | status information for           |      |                  |
|     |   | intrastate operators are made    |      |                  |
|     |   | available electronically to      |      |                  |
|     |   | qualified stakeholders           |      |                  |
|     |   | throughout the state.            |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 1 | Carrier audits are accomplished  | C    |                  |
|     | 0 | with electronic support.         |      |                  |
|     | . |                                  |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 1 | The "paperless vehicle" concept  | C    |                  |
|     | 1 | is supported, i.e. electronic    |      |                  |
|     | . | records become primary and paper |      |                  |
|     |   | records become secondary.        |      |                  |
+-----+---+----------------------------------+------+------------------+

Note: F -- Full Commitment; P -- Partial Commitment; N -- No Commitment

L1 -- CVISN Level 1; E -- Enhanced Level of CVISN capability; C --
Complete level of CVISN capability

Complete code descriptions are given in section 1.5.

The top-level requirements in the following table apply to the design of
state credentials-related systems. The table shows more detail about
what "CVISN Level 1" means. The CVISN Level 1 requirements are marked
with "L1" in the fourth column (Req Level (L1/E/C)). For an overview of
CVISN Level 1, see the Introductory Guide to CVISN \[Reference 12\].

Table 4.3‑6 State CV Administration Systems Design Requirements
Checklist

+----+---+----------------------------+-----+---+---+---+--------------+
| >  | > | Compatibility Criteria     | >   | > | > | > | Comments     |
| Co |   |                            | Req |   |   |   |              |
| mm | I |                            | >   | O | I | F |              |
| it | t |                            |  Le | p | O | O |              |
| >  | e |                            | vel | > | C | C |              |
|  L | m |                            | >   |   | > | > |              |
| ev | > |                            |  (L | T |   |   |              |
| el |   |                            | 1/E | e | D | D |              |
| >  | \ |                            | /C) | s | a | a |              |
|  ( | # |                            | >   | t | t | t |              |
| F/ |   |                            | >   | > | e | e |              |
| P/ |   |                            | CRF |   |   |   |              |
| N) |   |                            | >   | D |   |   |              |
|    |   |                            |  \# | a |   |   |              |
|    |   |                            |     | t |   |   |              |
|    |   |                            |     | e |   |   |              |
+====+===+============================+=====+===+===+===+==============+
|    | * | Support electronic         | L1  |   |   |   |              |
|    | * | credentialing (electronic  |     |   |   |   |              |
|    | 4 | submission of              | CRF |   |   |   |              |
|    | . | applications, evaluation,  | 1   |   |   |   |              |
|    | 3 | processing, and            | 048 |   |   |   |              |
|    | . | application response) for  |     |   |   |   |              |
|    | 1 | IRP.                       |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Provide a Web site for a   | L1; |   |   |   | Note: Either |
|    |   | person-to-computer         | E   |   |   |   | Web or       |
|    |   | process.                   |     |   |   |   | computer     |
|    |   |                            | CRF |   |   |   | -to-computer |
|    |   |                            | 1   |   |   |   | interface is |
|    |   |                            | 048 |   |   |   | required for |
|    |   |                            |     |   |   |   | L1.          |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Provide a                  | L1; |   |   |   | Note: Either |
|    |   | computer-to-computer       | E   |   |   |   | Web or       |
|    |   | automated process.         |     |   |   |   | computer     |
|    |   |                            | CRF |   |   |   | -to-computer |
|    |   |                            | 1   |   |   |   | interface is |
|    |   |                            | 048 |   |   |   | required for |
|    |   |                            |     |   |   |   | L1.          |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Use EDI standards to       | L1; |   |   |   | EDI is       |
|    | a | provide a                  | E   |   |   |   | recommended  |
|    |   | computer-to-computer       |     |   |   |   | in the near  |
|    |   | automated process.         | CRF |   |   |   | term for     |
|    |   |                            | 1   |   |   |   | computer     |
|    |   |                            | 048 |   |   |   | -to-computer |
|    |   |                            |     |   |   |   | interfaces.  |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Use XML standards to       | E   |   |   |   |              |
|    | b | provide a                  |     |   |   |   |              |
|    |   | computer-to-computer       | CRF |   |   |   |              |
|    |   | automated process.         | 1   |   |   |   |              |
|    |   |                            | 048 |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Proactively provide        | L1  |   |   |   |              |
|    | * | updates to vehicle         |     |   |   |   |              |
|    | 4 | snapshots as needed when   | CRF |   |   |   |              |
|    | . | IRP credentials actions    | 10  |   |   |   |              |
|    | 3 | are taken.                 | 48, |   |   |   |              |
|    | . |                            | 1   |   |   |   |              |
|    | 2 |                            | 164 |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Interface to SAFER for     | L1  |   |   |   | Today, EDI   |
|    |   | interstate vehicle         |     |   |   |   | is           |
|    |   | snapshots, using available | CRF |   |   |   | available;   |
|    |   | SAFER interface.           | 10  |   |   |   | plans are to |
|    |   |                            | 48, |   |   |   | also provide |
|    |   |                            | 1   |   |   |   | an XML       |
|    |   |                            | 164 |   |   |   | option.      |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Proactively provide        | L1  |   |   |   |              |
|    | * | updates to carrier         |     |   |   |   |              |
|    | 4 | snapshots as needed when   | CRF |   |   |   |              |
|    | . | IRP credentials actions    | 10  |   |   |   |              |
|    | 3 | are taken.                 | 48, |   |   |   |              |
|    | . |                            | 1   |   |   |   |              |
|    | 3 |                            | 164 |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Interface to SAFER for     | L1  |   |   |   | Today, EDI   |
|    |   | interstate carrier         |     |   |   |   | is           |
|    |   | snapshots, using available | CRF |   |   |   | available;   |
|    |   | standards                  | 10  |   |   |   | plans are to |
|    |   |                            | 48, |   |   |   | also provide |
|    |   |                            | 1   |   |   |   | an XML       |
|    |   |                            | 164 |   |   |   | option.      |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Provide IRP Clearinghouse  | L1  |   |   |   | CRF 313 was  |
|    | * | with IRP credential        |     |   |   |   | disapproved; |
|    | 4 | application information    |     |   |   |   | there are no |
|    | . | (recaps).                  |     |   |   |   | plans for an |
|    | 3 |                            |     |   |   |   | EDI          |
|    | . |                            |     |   |   |   | interface    |
|    | 4 |                            |     |   |   |   | with the IRP |
|    | * |                            |     |   |   |   | CH. The IRP  |
|    | * |                            |     |   |   |   | CH interface |
|    |   |                            |     |   |   |   | is specified |
|    |   |                            |     |   |   |   | in IRP CH    |
|    |   |                            |     |   |   |   | documents.   |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Review fees billed and/or  | L1  |   |   |   | CRF 313 was  |
|    | * | collected by a             |     |   |   |   | disapproved; |
|    | 4 | jurisdiction and the       |     |   |   |   | there are no |
|    | . | portion due other          |     |   |   |   | plans for an |
|    | 3 | jurisdictions              |     |   |   |   | EDI          |
|    | . | (transmittals) as provided |     |   |   |   | interface    |
|    | 5 | by the IRP Clearinghouse.  |     |   |   |   | with the IRP |
|    | * |                            |     |   |   |   | CH. The IRP  |
|    | * |                            |     |   |   |   | CH interface |
|    |   |                            |     |   |   |   | is specified |
|    |   |                            |     |   |   |   | in IRP CH    |
|    |   |                            |     |   |   |   | documents.   |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Support electronic         | L1  |   |   |   |              |
|    | * | state-to-state fee         |     |   |   |   |              |
|    | 4 | payments via IRP           |     |   |   |   |              |
|    | . | Clearinghouse              |     |   |   |   |              |
|    | 3 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 6 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Support electronic         | L1  |   |   |   |              |
|    | * | credentialing (electronic  |     |   |   |   |              |
|    | 4 | submission of              | CRF |   |   |   |              |
|    | . | applications, evaluation,  | 1   |   |   |   |              |
|    | 3 | processing, and            | 048 |   |   |   |              |
|    | . | application response) for  |     |   |   |   |              |
|    | 7 | IFTA registration.         |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Provide a Web site for a   | L1; |   |   |   | Note: Either |
|    |   | person-to-computer         | E   |   |   |   | Web or       |
|    |   | process.                   |     |   |   |   | computer     |
|    |   |                            | CRF |   |   |   | -to-computer |
|    |   |                            | 1   |   |   |   | interface is |
|    |   |                            | 048 |   |   |   | required for |
|    |   |                            |     |   |   |   | L1.          |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Provide a                  | L1; |   |   |   | Note: Either |
|    |   | computer-to-computer       | E   |   |   |   | Web or       |
|    |   | automated process.         |     |   |   |   | computer     |
|    |   |                            | CRF |   |   |   | -to-computer |
|    |   |                            | 1   |   |   |   | interface is |
|    |   |                            | 048 |   |   |   | required for |
|    |   |                            |     |   |   |   | L1.          |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Use EDI standards to       | L1; |   |   |   | EDI is       |
|    | a | provide a                  | E   |   |   |   | recommended  |
|    |   | computer-to-computer       |     |   |   |   | in the near  |
|    |   | automated process.         | CRF |   |   |   | term for     |
|    |   |                            | 1   |   |   |   | computer     |
|    |   |                            | 048 |   |   |   | -to-computer |
|    |   |                            |     |   |   |   | interfaces.  |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Use XML standards to       | E   |   |   |   |              |
|    | b | provide a                  |     |   |   |   |              |
|    |   | computer-to-computer       | CRF |   |   |   |              |
|    |   | automated process.         | 1   |   |   |   |              |
|    |   |                            | 048 |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Proactively provide        | L1  |   |   |   |              |
|    | * | updates to carrier         |     |   |   |   |              |
|    | 4 | snapshots as needed when   | CRF |   |   |   |              |
|    | . | IFTA credentials actions   | 10  |   |   |   |              |
|    | 3 | are taken or tax payments  | 48, |   |   |   |              |
|    | . | are made.                  | 1   |   |   |   |              |
|    | 8 |                            | 164 |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Interface to SAFER for     | L1  |   |   |   | Today, EDI   |
|    |   | interstate carrier         |     |   |   |   | is           |
|    |   | snapshots, using available | CRF |   |   |   | available;   |
|    |   | SAFER interface.           | 10  |   |   |   | plans are to |
|    |   |                            | 48, |   |   |   | also provide |
|    |   |                            | 1   |   |   |   | an XML       |
|    |   |                            | 164 |   |   |   | option.      |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Provide IFTA Clearinghouse | L1  |   |   |   |              |
|    | * | with IFTA credential       |     |   |   |   |              |
|    | 4 | application information    |     |   |   |   |              |
|    | . | using EDI standards.       |     |   |   |   |              |
|    | 3 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 9 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Support electronic tax     | L1  |   |   |   |              |
|    | * | filing for IFTA quarterly  |     |   |   |   |              |
|    | 4 | fuel tax returns.          |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 3 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | 0 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Provide a Web site for a   | L1; |   |   |   | Note: Either |
|    |   | person-to-computer         | E   |   |   |   | Web or       |
|    |   | process.                   |     |   |   |   | computer     |
|    |   |                            | CRF |   |   |   | -to-computer |
|    |   |                            | 1   |   |   |   | interface is |
|    |   |                            | 048 |   |   |   | required for |
|    |   |                            |     |   |   |   | L1.          |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Provide a                  | L1; |   |   |   | Note: Either |
|    |   | computer-to-computer       | E   |   |   |   | Web or       |
|    |   | automated process.         |     |   |   |   | computer     |
|    |   |                            | CRF |   |   |   | -to-computer |
|    |   |                            | 1   |   |   |   | interface is |
|    |   |                            | 048 |   |   |   | required for |
|    |   |                            |     |   |   |   | L1.          |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Use EDI standards to       | L1; |   |   |   | EDI is       |
|    | a | provide a                  | E   |   |   |   | recommended  |
|    |   | computer-to-computer       |     |   |   |   | in the near  |
|    |   | automated process.         | CRF |   |   |   | term for     |
|    |   |                            | 1   |   |   |   | computer     |
|    |   |                            | 048 |   |   |   | -to-computer |
|    |   |                            |     |   |   |   | interfaces.  |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Use XML standards to       | E   |   |   |   |              |
|    | b | provide a                  |     |   |   |   |              |
|    |   | computer-to-computer       | CRF |   |   |   |              |
|    |   | automated process.         | 1   |   |   |   |              |
|    |   |                            | 048 |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Provide information on     | L1  |   |   |   |              |
|    | * | taxes collected by own     |     |   |   |   |              |
|    | 4 | jurisdiction and the       |     |   |   |   |              |
|    | . | portion due other          |     |   |   |   |              |
|    | 3 | jurisdictions              |     |   |   |   |              |
|    | . | (transmittals) to the IFTA |     |   |   |   |              |
|    | 1 | Clearinghouse using EDI    |     |   |   |   |              |
|    | 1 | standards.                 |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Download for automated     | L1  |   |   |   |              |
|    | * | review the demographic     |     |   |   |   |              |
|    | 4 | information from the IFTA  |     |   |   |   |              |
|    | . | Clearinghouse using EDI    |     |   |   |   |              |
|    | 3 | standards.                 |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Download for automated     | L1  |   |   |   |              |
|    | * | review the transmittal     |     |   |   |   |              |
|    | 4 | information from the IFTA  |     |   |   |   |              |
|    | . | Clearinghouse using EDI    |     |   |   |   |              |
|    | 3 | standards.                 |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | 3 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Retrieve IFTA tax rate     | L1  |   |   |   |              |
|    | * | information electronically |     |   |   |   |              |
|    | 4 | from IFTA, Inc.            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 3 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | 4 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Support electronic         | E   |   |   |   |              |
|    | * | credentialing (electronic  |     |   |   |   |              |
|    | 4 | submission of              |     |   |   |   |              |
|    | . | applications, evaluation,  |     |   |   |   |              |
|    | 3 | processing, and            |     |   |   |   |              |
|    | . | application response) for  |     |   |   |   |              |
|    | 1 | other credentials.         |     |   |   |   |              |
|    | 5 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Interstate carrier         | E   |   |   |   |              |
|    |   | registration               |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Intrastate carrier         | E   |   |   |   |              |
|    |   | registration               |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 3 | Vehicle title              | E   |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 4 | Intrastate vehicle         | E   |   |   |   |              |
|    |   | registration               |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 5 | HazMat                     | E   |   |   |   |              |
|    |   | credentialing/permitting,  |     |   |   |   |              |
|    |   | if such                    |     |   |   |   |              |
|    |   | credentials/permits are    |     |   |   |   |              |
|    |   | required by state law.     |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 6 | Oversize/overweight        | E   |   |   |   |              |
|    |   | permitting.                |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Proactively provide        | E   |   |   |   |              |
|    | * | updates to vehicle         |     |   |   |   |              |
|    | 4 | snapshots as needed when   |     |   |   |   |              |
|    | . | credentials actions are    |     |   |   |   |              |
|    | 3 | taken.                     |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | 6 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Vehicle title              | E   |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Intrastate vehicle         | E   |   |   |   |              |
|    |   | registration               |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 3 | Oversize/overweight        | E   |   |   |   |              |
|    |   | permitting.                |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Proactively provide        | E   |   |   |   |              |
|    | * | updates to carrier         |     |   |   |   |              |
|    | 4 | snapshots as needed when   |     |   |   |   |              |
|    | . | credentials actions are    |     |   |   |   |              |
|    | 3 | taken.                     |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | 7 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Interstate carrier         | E   |   |   |   |              |
|    |   | registration               |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Intrastate carrier         | E   |   |   |   |              |
|    |   | registration               |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 3 | HazMat                     | E   |   |   |   |              |
|    |   | credentialing/permitting,  |     |   |   |   |              |
|    |   | if such                    |     |   |   |   |              |
|    |   | credentials/permits are    |     |   |   |   |              |
|    |   | required by state law.     |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 4 | Oversize/overweight        | E   |   |   |   |              |
|    |   | permitting.                |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Allow CV operators,        | E   |   |   |   |              |
|    | * | government-operated, or    |     |   |   |   |              |
|    | 4 | third party systems to     |     |   |   |   |              |
|    | . | submit one or more         |     |   |   |   |              |
|    | 3 | applications in a single   |     |   |   |   |              |
|    | . | transaction.               |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | 8 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Provide commercial driver  | L1  |   |   |   |              |
|    | * | information to other       |     |   |   |   |              |
|    | 4 | jurisdictions via CDLIS.   |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 3 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | 9 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Evaluate carrier safety    | E   |   |   |   |              |
|    | * | performance prior to       |     |   |   |   |              |
|    | 4 | issuing vehicle            |     |   |   |   |              |
|    | . | registration renewal (i.e. |     |   |   |   |              |
|    | 3 | support PRISM processes or |     |   |   |   |              |
|    | . | equivalent).               |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | 0 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Allow carriers to provide  | C   |   |   |   |              |
|    | * | information for audits     |     |   |   |   |              |
|    | 4 | electronically.            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 3 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Provide titling            | C   |   |   |   |              |
|    | * | information to other       |     |   |   |   |              |
|    | 4 | jurisdictions via NMVTIS.  |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 3 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Provide revoked IFTA motor | C   |   |   |   |              |
|    | * | carrier information to     |     |   |   |   |              |
|    | 4 | other jurisdictions via    |     |   |   |   |              |
|    | . | STOLEN.                    |     |   |   |   |              |
|    | 3 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | 3 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Accept electronic          | C   |   |   |   |              |
|    | * | credential and supporting  |     |   |   |   |              |
|    | 4 | electronic documentation,  |     |   |   |   |              |
|    | . | in lieu of paper versions. |     |   |   |   |              |
|    | 3 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | 4 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Proactively provide        | C   |   |   |   |              |
|    | * | updates to driver          |     |   |   |   |              |
|    | 4 | snapshots as needed when   |     |   |   |   |              |
|    | . | credentials actions are    |     |   |   |   |              |
|    | 3 | taken.                     |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | 5 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Interface to SAFER for     | C   |   |   |   |              |
|    |   | driver snapshots, using    |     |   |   |   |              |
|    |   | available SAFER interface. |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+

Note: F -- Full Commitment; P -- Partial Commitment; N -- No Commitment

L1 -- CVISN Level 1; E -- Enhanced Level of CVISN capability; C --
Complete level of CVISN capability

Complete code descriptions are given in section 1.5.

## State Electronic Screening Systems Design Requirements

The roadside systems involved in electronic screening consist of:

-   Screening System

-   Roadside Operations System

-   Sensor/Driver Communications System

-   Electronic Screening Enrollment (CRF 1172)

These electronic screening systems will operate at each fixed or mobile
CV check station within a state. The systems perform roadside functions
supporting automated carrier, vehicle, and driver identification and
associated look-ups in infrastructure-supplied data for credentials and
safety checks.

When building an electronic screening system, it is useful to think
about the process of electronic screening enrollment as part of the
process. The requirements for Electronic Screening Enrollment (ESE)
appear in this section on Electronic Screening, since the enrollment
would not occur unless operators wanted to participate in electronic
screening. CRF 1172 authorized this change. The requirements for ESE
should be considered during design of other administrative and
credentialing systems.

The concepts in the following table are based on an interpretation of
the guiding principles and the state of existing and emerging
technologies today. The elements in this table were originally based on
the Key Operational Concepts sections of the OCD \[Reference 9\].
Updated versions of the operational concepts are included in the CVISN
Guide to Top-Level Design \[Reference 13\] and in the CVISN Guide to and
Electronic Screening \[Reference 16\]. This version of the COACH
reflects the updated concepts.

Table 4.4‑7 Electronic Screening Operational Concepts

+-----+---+----------------------------------+------+------------------+
| Com | I | Compatibility Criteria           | Req  | Comments         |
| mit | t |                                  | L    |                  |
| Le  | e |                                  | evel |                  |
| vel | m |                                  |      |                  |
|     | \ |                                  | (L1/ |                  |
| (   | # |                                  | E/C) |                  |
| F/P |   |                                  |      |                  |
| /N) |   |                                  | CRF  |                  |
|     |   |                                  | \#   |                  |
+=====+===+==================================+======+==================+
|     | 1 | Widespread participation in      | L1   |                  |
|     | . | electronic screening programs is |      |                  |
|     |   | encouraged.                      |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 2 | Jurisdictions disclose practices | L1   |                  |
|     | . | related to electronic screening. |      |                  |
|     |   |                                  |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 3 | Electronic screening is provided | L1   |                  |
|     | . | for vehicles equipped with       |      |                  |
|     |   | FHWA-specified DSRC              |      |                  |
|     |   | transponders. See Reference 35.  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 4 | Jurisdictions and/or e-screening | L1   |                  |
|     | . | programs provide a single point  |      |                  |
|     |   | of contact for motor carriers to | CRF  |                  |
|     |   | request enrollment in all        | 1172 |                  |
|     |   | jurisdictions' electronic        |      |                  |
|     |   | screening programs.              |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 5 | If one jurisdiction or           | L1   |                  |
|     | . | e-screening program provides a   |      |                  |
|     |   | transponder to a carrier, it     | CRF  |                  |
|     |   | allows the carrier to use that   | 1172 |                  |
|     |   | transponder in other             |      |                  |
|     |   | jurisdictions' e-screening       |      |                  |
|     |   | programs, and in other           |      |                  |
|     |   | applications such as electronic  |      |                  |
|     |   | toll collection.                 |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 6 | For an enrolled carrier that has | L1   |                  |
|     | . | vehicles equipped with           |      |                  |
|     |   | compatible transponders,         | CRF  |                  |
|     |   | jurisdictions and/or e-screening | 1172 |                  |
|     |   | programs provide a mechanism for |      |                  |
|     |   | participation in electronic      |      |                  |
|     |   | screening using those            |      |                  |
|     |   | transponders.                    |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 7 | Credentials and safety checks    | L1   |                  |
|     | . | are conducted as part of the     |      |                  |
|     |   | screening process.               |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 8 | Fixed and/or mobile roadside     | L1   |                  |
|     | . | check stations are employed for  |      |                  |
|     |   | electronic clearance functions,  |      |                  |
|     |   | according to the jurisdiction's  |      |                  |
|     |   | needs and resources.             |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 9 | Jurisdictions support a common   | E    |                  |
|     | . | set of screening criteria.       |      |                  |
|     |   |                                  |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+
|     | 1 | Screening systems are            | E    |                  |
|     | 0 | interoperable with those in      |      |                  |
|     | . | different jurisdictions.         |      |                  |
|     |   |                                  |      |                  |
+-----+---+----------------------------------+------+------------------+

Note: F -- Full Commitment; P -- Partial Commitment; N -- No Commitment

L1 -- CVISN Level 1; E -- Enhanced Level of CVISN capability; C --
Complete level of CVISN capability

Complete code descriptions are given in section 1.5.

The top-level requirements in the following table apply to the design of
state screening-related systems. The table shows more detail about what
"CVISN Level 1" means. The CVISN Level 1 requirements are marked with
"L1" in the fourth column (Req Level (L1/E/C)). For an overview of CVISN
Level 1, see the Introductory Guide to CVISN \[Reference 12\].

Table 4.4‑8 State Electronic Screening Systems Design Requirements
Checklist

+----+---+----------------------------+-----+---+---+---+--------------+
| >  | > | Compatibility Criteria     | >   | > | > | > | Comments     |
| Co |   |                            | Req |   |   |   |              |
| mm | I |                            | >   | O | I | F |              |
| it | t |                            |  Le | p | O | O |              |
| >  | e |                            | vel | > | C | C |              |
|  L | m |                            | >   |   | > | > |              |
| ev | > |                            |  (L | T |   |   |              |
| el |   |                            | 1/E | e | D | D |              |
| >  | \ |                            | /C) | s | a | a |              |
|  ( | # |                            | >   | t | t | t |              |
| F/ |   |                            | >   | > | e | e |              |
| P/ |   |                            | CRF |   |   |   |              |
| N) |   |                            | >   | D |   |   |              |
|    |   |                            |  \# | a |   |   |              |
|    |   |                            |     | t |   |   |              |
|    |   |                            |     | e |   |   |              |
+====+===+============================+=====+===+===+===+==============+
|    | * | Follow FHWA guidelines for | L1  |   |   |   | See the NPRM |
|    | * | Dedicated Short Range      |     |   |   |   | regarding    |
|    | 4 | Communications (DSRC)      | CRF |   |   |   | DSRC in ITS  |
|    | . | equipment.                 | 1   |   |   |   | CVO,         |
|    | 4 |                            | 159 |   |   |   | Reference    |
|    | . |                            |     |   |   |   | 35.          |
|    | 1 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | For the immediate future,  | L1  |   |   |   | The DSRC     |
|    |   | all CVO and Border         |     |   |   |   | provisional  |
|    |   | crossing projects will     | CRF |   |   |   | standard is  |
|    |   | continue to utilize the    | 1   |   |   |   | defined in   |
|    |   | current DSRC configuration | 159 |   |   |   | the FHWA     |
|    |   | employed by the programs.  |     |   |   |   | sp           |
|    |   | This is the \"ASTM version |     |   |   |   | ecification, |
|    |   | 6\" active tag.            |     |   |   |   | (Reference   |
|    |   |                            |     |   |   |   | 37).         |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Beginning January 1, 2001, | E   |   |   |   |              |
|    |   | all CVO and Border         |     |   |   |   |              |
|    |   | Crossing projects will use | CRF |   |   |   |              |
|    |   | a provisional standard as  | 1   |   |   |   |              |
|    |   | described below. In        | 159 |   |   |   |              |
|    |   | addition, this provisional |     |   |   |   |              |
|    |   | standard will be designed  |     |   |   |   |              |
|    |   | to ensure interoperability |     |   |   |   |              |
|    |   | with the existing legacy   |     |   |   |   |              |
|    |   | equipment used in CVO that |     |   |   |   |              |
|    |   | conforms to ASTM Version   |     |   |   |   |              |
|    |   | 6.                         |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | the new ASTM Physical      | E   |   |   |   | Reference 32 |
|    | a | Layer in the active mode;  |     |   |   |   |              |
|    |   |                            | CRF |   |   |   |              |
|    |   |                            | 1   |   |   |   |              |
|    |   |                            | 159 |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | the existing ASTM Version  | E   |   |   |   | Reference 33 |
|    | b | 6 Data Link layer in the   |     |   |   |   |              |
|    |   | synchronous mode;          | CRF |   |   |   |              |
|    |   |                            | 1   |   |   |   |              |
|    |   |                            | 159 |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | and the IEEE 1455          | E   |   |   |   | Reference 34 |
|    | c | Application Layer.         |     |   |   |   |              |
|    |   |                            | CRF |   |   |   |              |
|    |   |                            | 1   |   |   |   |              |
|    |   |                            | 159 |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Use snapshots updated by a | L1  |   |   |   |              |
|    | * | SAFER/CVIEW subscription   |     |   |   |   |              |
|    | 4 | in an automated process to | CRF |   |   |   |              |
|    | . | support screening          | 1   |   |   |   |              |
|    | 4 | decisions.                 | 171 |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Carrier snapshots.         | L1  |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | Vehicle snapshots.         | L1  |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 3 | Driver snapshots.          | C   |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Implement interoperability | L1  |   |   |   |              |
|    | * | policies as they are       |     |   |   |   |              |
|    | 4 | developed by ITS America,  |     |   |   |   |              |
|    | . | the American Association   |     |   |   |   |              |
|    | 4 | of State Highway           |     |   |   |   |              |
|    | . | Transportation Officials,  |     |   |   |   |              |
|    | 3 | HELP, Inc., MAPS,          |     |   |   |   |              |
|    | * | Advantage CVO, I-95        |     |   |   |   |              |
|    | * | Corridor Coalition, and    |     |   |   |   |              |
|    |   | the Commercial Vehicle     |     |   |   |   |              |
|    |   | Safety Alliance.           |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | See AASHTO\'s Commercial   | L1  |   |   |   |              |
|    |   | Vehicle Electronic         |     |   |   |   |              |
|    |   | Screening Interoperability |     |   |   |   |              |
|    |   | Policy Resolution,         |     |   |   |   |              |
|    |   | PR-14-97, Reference 20.    |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Provide electronic         | L1  |   |   |   |              |
|    | * | mainline or ramp screening |     |   |   |   |              |
|    | 4 | for transponder-equipped   |     |   |   |   |              |
|    | . | vehicles, and clear for    |     |   |   |   |              |
|    | 4 | bypass if carrier &        |     |   |   |   |              |
|    | . | vehicle were properly      |     |   |   |   |              |
|    | 4 | identified and screening   |     |   |   |   |              |
|    | * | criteria were passed.      |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | For transponder-equipped   | L1  |   |   |   |              |
|    |   | vehicles, identify carrier |     |   |   |   |              |
|    |   | at mainline or ramp        |     |   |   |   |              |
|    |   | speeds.                    |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 2 | For transponder-equipped   | L1  |   |   |   |              |
|    |   | vehicles, identify vehicle |     |   |   |   |              |
|    |   | at mainline or ramp        |     |   |   |   |              |
|    |   | speeds.                    |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 3 | Use WIM or weight history  | L1  |   |   |   |              |
|    |   | at mainline speed or on    |     |   |   |   |              |
|    |   | the ramp in making         |     |   |   |   |              |
|    |   | screening decisions.       |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 4 | Record screening event     | E   |   |   |   |              |
|    |   | data.                      |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 5 | For transponder-equipped   | C   |   |   |   |              |
|    |   | vehicles, identify driver  |     |   |   |   |              |
|    |   | at mainline or ramp        |     |   |   |   |              |
|    |   | speeds.                    |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Collect from the carrier a | L1  |   |   |   |              |
|    | * | list of jurisdictions      |     |   |   |   |              |
|    | 4 | and/or e-screening         | CRF |   |   |   |              |
|    | . | programs in which it       | 1   |   |   |   |              |
|    | 4 | wishes to participate in   | 172 |   |   |   |              |
|    | . | electronic screening and   |     |   |   |   |              |
|    | 5 | inform those jurisdictions |     |   |   |   |              |
|    | * | and/or e-screening         |     |   |   |   |              |
|    | * | programs.                  |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Collect from the carrier a | L1  |   |   |   |              |
|    | * | list of jurisdictions      |     |   |   |   |              |
|    | 4 | and/or e-screening         | CRF |   |   |   |              |
|    | . | programs in which each of  | 1   |   |   |   |              |
|    | 4 | its vehicles chooses to    | 172 |   |   |   |              |
|    | . | participate in             |     |   |   |   |              |
|    | 6 | e-screening, and inform    |     |   |   |   |              |
|    | * | those jurisdictions and/or |     |   |   |   |              |
|    | * | e-screening programs.      |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Record transponder number  | L1  |   |   |   |              |
|    | * | and default carrier ID for |     |   |   |   |              |
|    | 4 | each vehicle that intends  | CRF |   |   |   |              |
|    | . | to participate in          | 1   |   |   |   |              |
|    | 4 | e-screening                | 172 |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 7 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Share carrier ID for each  | L1  |   |   |   |              |
|    | * | carrier that intends to    |     |   |   |   |              |
|    | 4 | participate in e-screening | CRF |   |   |   |              |
|    | . | with other jurisdictions   | 1   |   |   |   |              |
|    | 4 | and/or e-screening         | 172 |   |   |   |              |
|    | . | programs as requested by   |     |   |   |   |              |
|    | 8 | the carrier.               |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Via SAFER snapshots        | E   |   |   |   |              |
|    |   |                            |     |   |   |   |              |
|    |   |                            | CRF |   |   |   |              |
|    |   |                            | 1   |   |   |   |              |
|    |   |                            | 172 |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Share transponder number   | L1  |   |   |   |              |
|    | * | and default carrier ID for |     |   |   |   |              |
|    | 4 | each vehicle that intends  | CRF |   |   |   |              |
|    | . | to participate in          | 1   |   |   |   |              |
|    | 4 | e-screening with other     | 172 |   |   |   |              |
|    | . | jurisdictions, e-screening |     |   |   |   |              |
|    | 9 | programs, or other         |     |   |   |   |              |
|    | * | agencies as requested by   |     |   |   |   |              |
|    | * | the carrier.               |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | 1 | Via SAFER snapshots        | E   |   |   |   |              |
|    |   |                            |     |   |   |   |              |
|    |   |                            | CRF |   |   |   |              |
|    |   |                            | 1   |   |   |   |              |
|    |   |                            | 172 |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Accept each qualified      | L1  |   |   |   |              |
|    | * | vehicle already equipped   |     |   |   |   |              |
|    | 4 | with a compatible          | CRF |   |   |   |              |
|    | . | transponder into your      | 1   |   |   |   |              |
|    | 4 | e-screening program        | 172 |   |   |   |              |
|    | . | without requiring an       |     |   |   |   |              |
|    | 1 | additional transponder.    |     |   |   |   |              |
|    | 0 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Enable the carrier to      | L1  |   |   |   |              |
|    | * | share information about    |     |   |   |   |              |
|    | 4 | the transponder that you   | CRF |   |   |   |              |
|    | . | issue with other           | 1   |   |   |   |              |
|    | 4 | jurisdictions, e-screening | 172 |   |   |   |              |
|    | . | programs, or agencies.     |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Verify credentials/safety  | L1  |   |   |   |              |
|    | * | information with           |     |   |   |   |              |
|    | 4 | authoritative source prior |     |   |   |   |              |
|    | . | to issuing citation.       |     |   |   |   |              |
|    | 4 |                            |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | 2 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | If a vehicle illegally     | C   |   |   |   |              |
|    | * | bypasses or leaves the CV  |     |   |   |   |              |
|    | 4 | check station, alert law   |     |   |   |   |              |
|    | . | enforcement for possible   |     |   |   |   |              |
|    | 4 | apprehension.              |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | 3 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+
|    | * | Report periodically to     | C   |   |   |   |              |
|    | * | State safety information   |     |   |   |   |              |
|    | 4 | system on the activities   |     |   |   |   |              |
|    | . | conducted at each station  |     |   |   |   |              |
|    | 4 | (e.g. statistics).         |     |   |   |   |              |
|    | . |                            |     |   |   |   |              |
|    | 1 |                            |     |   |   |   |              |
|    | 4 |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
|    | * |                            |     |   |   |   |              |
+----+---+----------------------------+-----+---+---+---+--------------+

Note: F -- Full Commitment; P -- Partial Commitment; N -- No Commitment

L1 -- CVISN Level 1; E -- Enhanced Level of CVISN capability; C --
Complete level of CVISN capability

Complete code descriptions are given in section 1.5.

# References

1.  JHU/APL, *ITS/CVO CVISN Glossary*, POR-96-6997 V1.0, dated December
    1998.

2.  JHU/APL, *CVISN Operational and Architectural Compatibility Handbook
    (COACH), Part 1 - Operational Concept and Top-Level Design
    Checklists, SSD/PL-97-0236, POR-97-7067 P 1.0, Commercial Vehicle
    Information Systems and Networks (CVISN) Operational and
    Architectural Compatibility Handbook (COACH),* dated March 1997. The
    latest version is available on the JHU/APL CVISN web site
    [http://www.jhuapl.edu/cvisn/\]](http://www.jhuapl.edu/cvisn/)

3.  JHU/APL, *Updates to COACH Part 1: Chapter 5 (State), Chapter 6
    (CVISN Core Infrastructure), and Chapter 7 (Carrier)*,
    SSD/PL-98-0017, dated January 1998.

4.  JHU/APL, *CVISN Operational and Architectural Compatibility Handbook
    (COACH), Part 2 - Project Management Checklists, POR-97-7067 P2.0,
    (Preliminary Version),* September 1999. The latest version is
    available on the JHU/APL CVISN Web site
    <http://www.jhuapl.edu/cvisn/>[\]]{.underline}

5.  JHU/APL, *CVISN Operational and Architectural Compatibility Handbook
    (COACH), Part 3 -- Detailed System Checklists, POR-97-7067 P1.0,*
    May 1999. [\[Note: This document is scheduled to be updated in 2000.
    The latest version will be available on the JHU/APL CVISN Web site
    [http://www.jhuapl.edu/cvisn/\]]{.underline}](http://www.jhuapl.edu/cvo/)

6.  [JHU/APL,](http://www.jhuapl.edu/cvo/) *CVISN Operational and
    Architectural Compatibility Handbook (COACH), Part 4 -- Interface
    Specification Checklists*, *POR-97-7067 D1.0, (Draft),* April 1999.
    \[Note: This document is scheduled to be updated in 2000. The latest
    version will be available on the JHU/APL CVISN Web site
    <http://www.jhuapl.edu/cvisn/>[\]]{.underline}

7.  JHU/APL, *CVISN Operational and Architectural Compatibility Handbook
    (COACH), Part 5 - Interoperability Test Criteria, SSD/PL-99-0470,
    (Draft), dated July 1999*. \[Note: This document is scheduled to be
    updated in 2000. The latest version will be available on the JHU/APL
    CVISN Web site <http://www.jhuapl.edu/cvisn/>[\]]{.underline}

8.  JHU/APL, *Introduction to Commercial Vehicle Information Systems and
    Networks (CVISN),* POR-95-6982, V1.0, March 14, 1997.

9.  JHU/APL, *Commercial Vehicle Information Systems and Networks
    (CVISN) Operational Concept Document*, (Preliminary Issue P.2),
    POR-96-6989, June 1996.

10. JHU/APL, *Commercial Vehicle Information Systems and Networks
    (CVISN) Architecture Specification*, (Preliminary), POR-96-6985,
    February 1996.

11. JHU/APL, *Commercial Vehicle Information Systems and Networks
    (CVISN) System Design Description,* POR-97-6998 V1.0, (Baseline
    Version), March 1999. \[Note: This document is scheduled to be
    updated in 2000. The latest version will be available on the JHU/APL
    CVISN Web site <http://www.jhuapl.edu/cvisn/>[\]]{.underline}

12. JHU/APL, *Introductory Guide to CVISN, POR-99-7186 P.1
    (Preliminary),* May 1999. \[Note: This document is scheduled to be
    updated in 2000. The latest version will be available on the JHU/APL
    CVISN Web site <http://www.jhuapl.edu/cvisn/>[\]]{.underline}

13. JHU/APL, *CVISN Guide to Top-Level Design, POR-99-7187, P.1*,
    May 1999. \[Note: This document is scheduled to be updated in 2000.
    The latest version will be available on the JHU/APL CVISN Web site
    <http://www.jhuapl.edu/cvisn/>[\]]{.underline}

14. JHU/APL, *CVISN Guide to Safety Information Exchange, POR-99-7191,
    D.1*, March 2000. \[Note: This document is scheduled to be updated
    in 2000. The latest version will be available on the JHU/APL CVISN
    Web site <http://www.jhuapl.edu/cvisn/>[\]]{.underline}

15. JHU/APL, *CVISN Guide to Credentials Administration, POR-99-7192,
    P.1*, July 1999. \[Note: This document is scheduled to be updated
    in 2000. The latest version will be available on the JHU/APL CVISN
    Web site <http://www.jhuapl.edu/cvisn/>[\]]{.underline}

16. JHU/APL, *CVISN Guide to Electronic Screening, POR-99-7193, D.1*,
    October 1999. \[Note: This document is scheduled to be updated
    in 2000. The latest version will be available on the JHU/APL CVISN
    Web site <http://www.jhuapl.edu/cvisn/>[\]]{.underline}

17. Intelligent Transportation Society of America, *ITS CVO Guiding
    Principles*, published on the World Wide Web at
    [http://www.itsa.org](http://www.itsa.org/), last updated March 27,
    1998.

18. Intelligent Transportation Society of America, *Fair Information
    Principles for ITS/CVO*, published on the World Wide Web at
    [http://www.itsa.org](http://www.itsa.org/), last updated January
    12, 1999.

19. Intelligent Transportation Society of America,
    *[Interim]{.underline} ITS/CVO Interoperability Guiding Principles*,
    published on the World Wide Web at
    [http://www.itsa.org](http://www.itsa.org/), last updated January
    12, 1999.

20. AASHTO (American Association of State Highway Transportation
    Officials), *Policy Resolution P\$-14-97 Commercial Vehicle
    Electronic Screening Interoperability, AASHTO Transportation Policy
    Book,* January 1999. The document is available on the World Wide Web
    at <http://www.aashto.org/>.

21. FHWA, *Commercial Vehicle Information Systems and Networks (CVISN)
    Model Deployment Program Request for Information*, notice in Federal
    Register April 11, 1996 (volume 61, number 71, 16157)

22. FHWA, *Commercial Vehicle Information Systems and Networks (CVISN)
    Model Deployment Program Request for Application*, notice in Federal
    Register July 5, 1996 (volume 61, number 130, 35300).

23. FHWA, Letter from HAS-20 to States*, Call for New CVISN States -
    What states are interested in CVISN Workshops*, J. Loftus e-mail dtg
    981222 5:10 PM

24. *Reference Deleted*

25. ANSI ASC X12, *Electronic Data Interchange X12 Standards*, Draft
    Version 4, Release 3, (a.k.a. Release 4030), December 1999.

26. JHU/APL, *Commercial Vehicle Information Systems and Networks
    (CVISN) Recommendations for Common Carrier, Vehicle, Driver, and
    Cargo Identifiers,* SSD/PL-99-0388, June 1999.

27. JHU/APL, *EDI Implementation Guide for Commercial Vehicle
    Credentials (Transaction Set 286), Volume I - IRP Credential
    Transactions, ANSI ASC X12 Version 4 Release 3*, POR-96-6993 D.5,
    dated March 2000.

28. JHU/APL, *EDI Implementation Guide for Commercial Vehicle
    Credentials (Transaction Set 286), Volume II -- IRP Interstate
    Credential Transactions*, Draft Version, POR-96-6994 D.2, December
    17, 1996.

29. JHU/APL, *EDI Implementation Guide for Commercial Vehicle
    Credentials (Transaction Set 286), Volume III - International Fuel
    Tax Agreement (IFTA) Credential Transactions, ANSI ASC X12 Version 4
    Release 3*, POR-97-6996 D.4, dated March 2000.

30. JHU/APL, *EDI Implementation Guide for Commercial Vehicle
    Credentials (Transaction Set 286), Volume IV - Oversize / Overweight
    (OS/OW) Credential Transactions*, POR-97-7068 D.3, dated March 2000.

31. JHU/APL, *EDI Implementation Guide for Commercial Vehicle Safety and
    Credentials Information Exchange (Transaction Set 285)*, POR-96-6995
    D.5, dated March 2000.

32. ASTM Preliminary Standard-111-98, Specification for Dedicated Short
    Range Communication (DSRC) Physical Layer using Microwave in the 920
    to 928 MHz band, dated April 1999. For a summary of the standard,
    see <http://www.its.dot.gov/standard/standard.htm>.

33. ASTM Draft Standard for Dedicated, Short Range, Two-Way Vehicle to
    Roadside Communications Equipment, Draft 6, dated 23 February 1996.

34. IEEE Standard 1455-99, Standard for Message Sets for
    Vehicle/Roadside Communications, dated September 1999. For a summary
    of the standard, see <http://www.its.dot.gov/standard/standard.htm>.

35. The U. S. Department of Transportation, Federal Highway
    Administration, *Proposed Rule: Dedicated Short Range Communications
    In Intelligent Transportation Systems (ITS) Commercial Vehicle
    Operations*, 23 CFR Part 945, \[FHWA Docket No. FHWA 99-5844\] RIN
    2125-AE63, published in Federal Register: December 30, 1999 (Volume
    64, Number 250)\], Page 73674-73742. Available from the Federal
    Register Online via GPO Access,
    <http://www.access.gpo.gov/su_docs/aces/aces140.html>
    \[DOCID:fr30de99-43\]

36. JHU/APL, *CVISN Operational and Architectural Compatibility Handbook
    (COACH), Part 1 - Operational Concept and Top-Level Design
    Checklists, SSD/PL-97-0243, POR-97-7067 V1.0, Commercial Vehicle
    Information Systems and Networks (CVISN) Operational and
    Architectural Compatibility Handbook (COACH),* dated March 1999.

37. JHU/APL, *Delivery of Draft Specification for "Active Sandwich"
    Protocol for Dedicated Short Range Communications (DSRC) for
    Commercial Vehicles, SSD-PL-99-0784, with enclosure Draft
    Specification for DSRC for Commercial Vehicles, Version 0.0.1,
    November 1999*, dated December 1999.

38. JHU/APL, *Delivery of CVISN Electronic Credentialing Preference
    Survey Results, SSD-PL-00-0408, with enclosure Electronic
    Credentialing Preference Survey Results*, June 2000, dated July
    2000.