# System Requirements

2\. System Requirements [2-1](#system-requirements)

2.1 Maryland--Specific Goals [2-2](#marylandspecific-goals)

2.2 Use of COACH for Top-Level Design
[2-2](#use-of-coach-for-top-level-design)

2.3 Operational Concept and Top-Level Design Checklists
[2-4](#operational-concept-and-top-level-design-checklists)

2.3.1 Guiding Principles [2-4](#guiding-principles)

2.3.1.1 ITS/CVO Guiding Principles [2-4](#itscvo-guiding-principles)

2.3.1.2 Fair Information Principles for ITS/CVO
[2-11](#fair-information-principles-for-itscvo)

2.3.1.3 ITS/CVO Interoperability Guiding Principles
[2-13](#itscvo-interoperability-guiding-principles)

2.3.2 Operational Concepts [2-20](#operational-concepts)

2.3.2.1 General [2-20](#general)

2.3.2.2 Safety Information Exchange [2-23](#safety-information-exchange)

2.3.2.3 Credentials Administration [2-24](#credentials-administration)

2.3.2.4 Electronic Screening [2-25](#electronic-screening)

2.3.3 State Institutional Framework
[2-25](#state-institutional-framework)

2.3.4 State Systems Checklists [2-29](#state-systems-checklists)

2.3.4.1 General State Systems Design Requirements
[2-30](#general-state-systems-design-requirements)

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

2.3.4.3 State CV Administration Systems Design Requirements
[2-34](#state-cv-administration-systems-design-requirements)

2.3.4.4 State Electronic Screening Systems Design Requirements
[2-39](#state-electronic-screening-systems-design-requirements)

2.3.5 CVISN Core Infrastructure Systems Checklists
[2-41](#cvisn-core-infrastructure-systems-checklists)

2.4 Interface Specification Checklist
[2-41](#interface-specification-checklist)

2.4.1 Standard Interface Identification
[2-41](#standard-interface-identification)

2.4.2 Standard Data Definitions [2-57](#standard-data-definitions)

2.5 Other Maryland Requirements [2-62](#other-maryland-requirements)

##   {#section .unnumbered}

## Maryland--Specific Goals 

Maryland objectives may be summarized as follows:

-   Improve highway safety and public safety

```{=html}
<!-- -->
```
-   Timely distribution of safety and credential information to
    computers at the roadside

-   Electronic collection of inspection and other data from the roadside
    and distribution to state and national systems

-   Performing electronic screening checks of safety, weight, &
    credentials

```{=html}
<!-- -->
```
-   Make Maryland a better place for motor carriers to do business

```{=html}
<!-- -->
```
-   Electronic application for credentials & tax payment by carriers

-   Interfacing of state systems to the IRP and IFTA clearinghouses

-   Performing electronic screening

```{=html}
<!-- -->
```
-   Improve exchange of data among legacy systems

-   Explore feasibility & benefits of advanced CVO concepts

```{=html}
<!-- -->
```
-   Prototype a short haul electronic clearance capability

-   Prototype the paperless vehicle concept

-   Prototype an automated safety & weight data collection capability

Some detailed objectives that go beyond the CVISN Level 1 goals are:

-   Branch Office CAT for IFTA Registration

-   Network infrastructure upgrades

-   Intrastate vehicle data in snapshots

-   Use of EDI for third-party legacy systems

-   Interfaces with enforcement systems

## Use of COACH for Top-Level Design

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 and by motor carriers.
It is also intended to provide a quick reference for developers of CVISN
Core Infrastructure systems.

The COACH is divided into 5 parts:

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

Part 2 - Project Management Checklists

Part 3 - Detailed System Checklists

Part 4 - Interface Specification Checklists

Part 5 - Interoperability Test Criteria

The completed Parts 1 and 4 of the COACH will be shown in this chapter;
the completed Part 3 will be shown in chapter 3 of this document.

Each table in the COACH checklists 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. This is used
    in the State Systems Checklists and the CVISN Core Infrastructure
    Systems Checklists only.

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

-   Req Level - the compatibility requirement level assigned to this
    compatibility criterion by the FHWA 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.

-   Op Test (operationally tested) Date, IOC (initial operating
    capability) Date, and FOC (final operating capability) Date (section
    2.3.4 only) -- will be left blank in this document

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

    The following conventions are used when filling in the columns to
    illustrate the "firmness" of Maryland'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

## Operational Concept and Top-Level Design Checklists

The COACH Part 1 Operational Concept and Top-Level Design 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.
Completing the COACH Part 1 tables helps the state set the scope of
their CVISN project and define top-level requirements. There are several
types of checklists related to operational concepts and top-level design
(the chapter numbers refer to the COACH Part 1 Operational Concept and
Top-Level Design Checklists):

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

-   Operational Concepts Checklists: compatibility requirements for
    processes \[Chapter 3\]

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

-   CVISN Top-level Design Checklists: top-level compatibility
    requirements for state and carrier system designs. For the CVISN
    Core Infrastructure systems, the checklists show the planned
    capabilities, and provide a place for states to indicate which
    capabilities they intend to utilize. \[Chapters 5 and 6\]

### 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.

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 section.

#### ITS/CVO Guiding Principles

*"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  |                                           |                   |
| vel |                                           |                   |
|     |                                           |                   |
| (   |                                           |                   |
| F/P |                                           |                   |
| /N) |                                           |                   |
+=====+===========================================+===================+
| F   | 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**.         |                   |
+-----+-------------------------------------------+-------------------+
| F   | 2.  The CVISN architecture will enable    |                   |
|     |     **electronic information exchange**   |                   |
|     |     among authorized stakeholders via     |                   |
|     |     open standards.                       |                   |
+-----+-------------------------------------------+-------------------+
| F   | 3.  The architecture **deployment will    |                   |
|     |     evolve incrementally**, starting with |                   |
|     |     legacy systems where practical and    |                   |
|     |     proceeding in manageable steps with   |                   |
|     |     **heavy end-user involvement**.       |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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.                          |                   |
+-----+-------------------------------------------+-------------------+
| F   | 5.  Information technology will support   |                   |
|     |     improved practices and procedures to  |                   |
|     |     **improve CVO credential and tax      |                   |
|     |     administration efficiency** for       |                   |
|     |     carriers and government.              |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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  |                                           |                   |
| vel |                                           |                   |
|     |                                           |                   |
| (   |                                           |                   |
| F/P |                                           |                   |
| /N) |                                           |                   |
+=====+===========================================+===================+
| F   | 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.                             |                   |
+-----+-------------------------------------------+-------------------+
| F   | 2.  **Investment and participation** in   |                   |
|     |     ITS/CVO technology will be            |                   |
|     |     **voluntary**.                        |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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.           |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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**.                       |                   |
+-----+-------------------------------------------+-------------------+
| F   | 5.  Government CVO policies and           |                   |
|     |     regulatory practices will permit safe |                   |
|     |     and legal carriers and drivers to     |                   |
|     |     operate without **unnecessary         |                   |
|     |     regulatory and administrative         |                   |
|     |     burdens**.                            |                   |
+-----+-------------------------------------------+-------------------+
| F   | 6.  Stakeholders will use **technology    |                   |
|     |     and institutional reform** to         |                   |
|     |     implement continuous process          |                   |
|     |     improvement and cost-effective        |                   |
|     |     process re-engineering.               |                   |
+-----+-------------------------------------------+-------------------+
| F   | 7.  The **confidentiality** of            |                   |
|     |     proprietary and other sensitive       |                   |
|     |     stakeholder information will be       |                   |
|     |     preserved.                            |                   |
+-----+-------------------------------------------+-------------------+
| F   | 8.  The United States CVO community will  |                   |
|     |     work to implement **compatible        |                   |
|     |     policies** and architecture and       |                   |
|     |     **interoperable systems** in all      |                   |
|     |     states.                               |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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  |                                           |                   |
| vel |                                           |                   |
|     |                                           |                   |
| (   |                                           |                   |
| F/P |                                           |                   |
| /N) |                                           |                   |
+=====+===========================================+===================+
| F   | 1.  The CVISN architecture will be        |                   |
|     |     **open**, modular, and adaptable.     |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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**.                             |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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.               |                   |
+-----+-------------------------------------------+-------------------+
| F   | 4.  A jurisdiction shall have and         |                   |
|     |     maintain **ownership of any** data    |                   |
|     |     collected by any agent on its behalf. |                   |
+-----+-------------------------------------------+-------------------+
| F   | 5.  The architecture will accommodate     |                   |
|     |     **existing** and near-term            |                   |
|     |     **communications** technologies.      |                   |
+-----+-------------------------------------------+-------------------+
| F   | 6.  The architecture will accommodate     |                   |
|     |     **proven technologies and legacy      |                   |
|     |     systems** whenever possible.          |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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  |                                           |                   |
| vel |                                           |                   |
|     |                                           |                   |
| (   |                                           |                   |
| F/P |                                           |                   |
| /N) |                                           |                   |
+=====+===========================================+===================+
| F   | 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.                              |                   |
+-----+-------------------------------------------+-------------------+
| F   | 2.  After feasibility has been            |                   |
|     |     demonstrated, key architectural       |                   |
|     |     elements will be incorporated into    |                   |
|     |     appropriate national and              |                   |
|     |     international **standards**.          |                   |
+-----+-------------------------------------------+-------------------+
| F   | 3.  The architecture **deployment will    |                   |
|     |     evolve incrementally**, starting with |                   |
|     |     legacy systems where practical and    |                   |
|     |     proceeding in manageable steps.       |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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  |                                           |                   |
| vel |                                           |                   |
|     |                                           |                   |
| (   |                                           |                   |
| F/P |                                           |                   |
| /N) |                                           |                   |
+=====+===========================================+===================+
| F   | 1.  **[Carriers]{.underline} and          |                   |
|     |     [drivers]{.underline} will be         |                   |
|     |     responsible** for the safe and legal  |                   |
|     |     operation of commercial vehicles.     |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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.         |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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.       |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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.                   |                   |
+-----+-------------------------------------------+-------------------+
| F   | 5.  Jurisdictions will use a **safety     |                   |
|     |     risk rating** for all carriers based  |                   |
|     |     on best available information and     |                   |
|     |     common criteria.                      |                   |
+-----+-------------------------------------------+-------------------+
| F   | 6.  Jurisdictions will identify **high    |                   |
|     |     risk drivers** based on best          |                   |
|     |     available information and common      |                   |
|     |     criteria.                             |                   |
+-----+-------------------------------------------+-------------------+
| F   | 7.  Safety programs will provide          |                   |
|     |     **benefits that exceed costs** for    |                   |
|     |     carriers and drivers as well as       |                   |
|     |     governments.                          |                   |
+-----+-------------------------------------------+-------------------+

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

+-----+-------------------------------------------+-------------------+
| Com | Compatibility Criteria                    | Comments          |
| mit |                                           |                   |
| Le  |                                           |                   |
| vel |                                           |                   |
|     |                                           |                   |
| (   |                                           |                   |
| F/P |                                           |                   |
| /N) |                                           |                   |
+=====+===========================================+===================+
| F   | 1.  **Electronic information** will be    |                   |
|     |     used in place of paper documents for  |                   |
|     |     the administration of CVO credential  |                   |
|     |     and tax requirements.                 |                   |
+-----+-------------------------------------------+-------------------+
| F   | 2.  Authorized users will be able to      |                   |
|     |     electronically exchange credential    |                   |
|     |     and tax-related information and funds |                   |
|     |     via **open standards** and            |                   |
|     |     transmission options.                 |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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. |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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  |                                           |                   |
| vel |                                           |                   |
|     |                                           |                   |
| (   |                                           |                   |
| F/P |                                           |                   |
| /N) |                                           |                   |
+=====+===========================================+===================+
| F   | 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.                              |                   |
+-----+-------------------------------------------+-------------------+
| F   | 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."                         |                   |
+-----+-------------------------------------------+-------------------+

#### Fair Information Principles for ITS/CVO 

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

#### ITS/CVO Interoperability Guiding Principles 

"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 | Compatibility Criteria                    | Comments          |
| mit |                                           |                   |
| Le  |                                           |                   |
| vel |                                           |                   |
|     |                                           |                   |
| (   |                                           |                   |
| F/P |                                           |                   |
| /N) |                                           |                   |
+=====+===========================================+===================+
| F   | ***[IGP #1]{.underline}***                |                   |
|     |                                           |                   |
|     | The CVO community will work to implement  |                   |
|     | interoperable ITS/CVO systems in all      |                   |
|     | United States jurisdictions.              |                   |
+-----+-------------------------------------------+-------------------+
| F   | ***[IGP #2]{.underline}***                |                   |
|     |                                           |                   |
|     | The CVO community will work with the CVO  |                   |
|     | communities in Canada and Mexico to       |                   |
|     | implement interoperable ITS/CVO systems   |                   |
|     | throughout North America.                 |                   |
+-----+-------------------------------------------+-------------------+
| F   | ***[IGP #3]{.underline}***                |                   |
|     |                                           |                   |
|     | The CVO community will work to ensure     |                   |
|     | that ITS/CVO systems, where appropriate,  |                   |
|     | are interoperable with other ITS systems  |                   |
|     | (e.g., electronic toll systems).          |                   |
+-----+-------------------------------------------+-------------------+
| F   | ***[IGP #4]{.underline}***                |                   |
|     |                                           |                   |
|     | Interoperable ITS/CVO systems will be     |                   |
|     | achieved through the development,         |                   |
|     | adoption, and adherence to common         |                   |
|     | standards for hardware, systems/software, |                   |
|     | operations, and program administration.   |                   |
+-----+-------------------------------------------+-------------------+
| F   | ***[IGP #5]{.underline}***                |                   |
|     |                                           |                   |
|     | Each jurisdiction will support the        |                   |
|     | national ITS/CVO information system       |                   |
|     | architecture and data exchange standards  |                   |
|     | developed under the Commercial Vehicle    |                   |
|     | Information Systems and Networks (CVISN)  |                   |
|     | program.                                  |                   |
+-----+-------------------------------------------+-------------------+
| F   | ***[IGP #6]{.underline}***                |                   |
|     |                                           |                   |
|     | Transponders shall have a unique          |                   |
|     | identifier.                               |                   |
+-----+-------------------------------------------+-------------------+
| F   | ***[IGP #7]{.underline}***                |                   |
|     |                                           |                   |
|     | Information systems supporting electronic |                   |
|     | screening, credentials administration,    |                   |
|     | and safety assurance will use:            |                   |
|     |                                           |                   |
|     | 7a. US DOT numbers for the identification |                   |
|     | of both interstate and 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 | Compatibility Criteria                    | Comments          |
| mit |                                           |                   |
| Le  |                                           |                   |
| vel |                                           |                   |
|     |                                           |                   |
| (   |                                           |                   |
| F/P |                                           |                   |
| /N) |                                           |                   |
+=====+===========================================+===================+
| F   | ***[IGP #8]{.underline}***                |                   |
|     |                                           |                   |
|     | Commercial vehicle operators will be able |                   |
|     | to use one transponder for power          |                   |
|     | unit-to-roadside communications in        |                   |
|     | support of multiple applications          |                   |
|     | including electronic screening, safety    |                   |
|     | assurance, fleet and asset management,    |                   |
|     | tolls, parking, and other transaction     |                   |
|     | processes.                                |                   |
+-----+-------------------------------------------+-------------------+
| F   | ***[IGP #9]{.underline}***                |                   |
|     |                                           |                   |
|     | Public and public-private DSRC            |                   |
|     | applications will support open standards  |                   |
|     | that are consistent with the national ITS |                   |
|     | architecture.                             |                   |
+-----+-------------------------------------------+-------------------+

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

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

##### ITS/CVO Interoperability Guiding Principles: Operations

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

##### ITS/CVO Interoperability Guiding Principles: Program

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

### Operational Concepts

As stated in the COACH Part 1 Operational Concept and Top-Level Design
Checklists, the Operational Concepts in this section are organized into
4 groups: general, safety information exchange, credentials
administration, electronic screening. Concepts in the "general" category
apply to the other three. The concepts are based on an interpretation of
the guiding principles and the state of existing and emerging
technologies today. The tables show Maryland\'s commitment level.

#### General

+-----+-----------------------------------+--------+-----------------+
| Com | Compatibility Criteria            | Req    | Comments        |
| mit |                                   | Level  |                 |
| Le  |                                   |        |                 |
| vel |                                   | (L     |                 |
|     |                                   | 1/E/C) |                 |
| (   |                                   |        |                 |
| F/P |                                   |        |                 |
| /N) |                                   |        |                 |
+=====+===================================+========+=================+
| F   | 1.  Good business processes can   | L1     |                 |
|     |     be enhanced through improved  |        |                 |
|     |     automated access to accurate  |        |                 |
|     |     information.                  |        |                 |
+-----+-----------------------------------+--------+-----------------+
| F   | 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.    |        |                 |
+-----+-----------------------------------+--------+-----------------+
| F   | 3.  Sometimes it is practical for | L1     |                 |
|     |     authoritative systems to      |        |                 |
|     |     authorize indirect sources to |        |                 |
|     |     assist in the information     |        |                 |
|     |     exchange process.             |        |                 |
+-----+-----------------------------------+--------+-----------------+
| F   | 4.  To enable cross-referencing   | L1 --  |                 |
|     |     and standard look-ups in      | inte   |                 |
|     |     multiple information systems, | rstate |                 |
|     |     a common scheme for           |        |                 |
|     |     identifying carriers must be  | C --   |                 |
|     |     adopted. The Primary Carrier  | intr   |                 |
|     |     ID should be used in          | astate |                 |
|     |     interface agreements (open    |        |                 |
|     |     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.       |        |                 |
+-----+-----------------------------------+--------+-----------------+
| F   | 5.  To enable cross-referencing   | L1     |                 |
|     |     and 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.                           |        |                 |
+-----+-----------------------------------+--------+-----------------+
| F   | 6.  To enable cross-referencing   | L1     |                 |
|     |     and 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.               |        |                 |
+-----+-----------------------------------+--------+-----------------+
| N   | 7.  To enable cross-referencing   | E      | Out of scope.   |
|     |     and 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.                        |        |                 |
+-----+-----------------------------------+--------+-----------------+
| F   | 8.  Standard information exchange | L1 --  |                 |
|     |     is supported via carrier and  | c      |                 |
|     |     vehicle (and eventually       | arrier |                 |
|     |     driver) snapshots.            | &      |                 |
|     |                                   | v      |                 |
|     |                                   | ehicle |                 |
|     |                                   |        |                 |
|     |                                   | C --   |                 |
|     |                                   | driver |                 |
+-----+-----------------------------------+--------+-----------------+
| F   | 9.  Flexible                      | L1     |                 |
|     |     implementation/deployment     |        |                 |
|     |     options are accommodated by   |        |                 |
|     |     the ITS/CVO architecture. As  |        |                 |
|     |     technology changes, so will   |        |                 |
|     |     the architecture.             |        |                 |
+-----+-----------------------------------+--------+-----------------+
| F   | 10. Open standards are used for   | L1     |                 |
|     |     interchanges between public   |        |                 |
|     |     and private systems. In       |        |                 |
|     |     particular, ANSI ASC X12 EDI  |        |                 |
|     |     transactions are used for     |        |                 |
|     |     carrier-state and state-core  |        |                 |
|     |     infrastructure information    |        |                 |
|     |     systems' interactions. DSRC   |        |                 |
|     |     standards for the messages,   |        |                 |
|     |     data link, and physical       |        |                 |
|     |     layers are used for           |        |                 |
|     |     vehicle-roadside              |        |                 |
|     |     interactions.                 |        |                 |
+-----+-----------------------------------+--------+-----------------+
| F   | 11. Enhanced data exchange will   | L1     |                 |
|     |     allow all activities to focus |        |                 |
|     |     resources on high risk        |        |                 |
|     |     operators.                    |        |                 |
+-----+-----------------------------------+--------+-----------------+
| F   | 12. Interoperability is assured   | L1     |                 |
|     |     by a 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.    |        |                 |
+-----+-----------------------------------+--------+-----------------+
| F   | 13. The Fair Information          | L1     |                 |
|     |     Principles 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.                   |        |                 |
+-----+-----------------------------------+--------+-----------------+
| F   | 14. Citations are based on a      | L1     |                 |
|     |     review of real-time           |        |                 |
|     |     conditions and checks with    |        |                 |
|     |     authoritative sources.        |        |                 |
+-----+-----------------------------------+--------+-----------------+

#### Safety Information Exchange 

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

#### Credentials Administration 

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

#### Electronic Screening 

+-----+-----------------------------------+------+-------------------+
| Com | Compatibility Criteria            | Req  | Comments          |
| mit |                                   | L    |                   |
| Le  |                                   | evel |                   |
| vel |                                   |      |                   |
|     |                                   | (L1/ |                   |
| (   |                                   | E/C) |                   |
| F/P |                                   |      |                   |
| /N) |                                   |      |                   |
+=====+===================================+======+===================+
| F   | 1.  Widespread participation in   | L1   |                   |
|     |     electronic screening programs |      |                   |
|     |     is encouraged.                |      |                   |
+-----+-----------------------------------+------+-------------------+
| F   | 2.  Jurisdictions disclose        | L1   |                   |
|     |     practices related to          |      |                   |
|     |     electronic screening.         |      |                   |
+-----+-----------------------------------+------+-------------------+
| F   | 3.  Electronic screening is       | L1   |                   |
|     |     provided for vehicles         |      |                   |
|     |     equipped with FHWA-specified  |      |                   |
|     |     DSRC transponders. See        |      |                   |
|     |     Reference 49.                 |      |                   |
+-----+-----------------------------------+------+-------------------+
| F   | 4.  Credentials and safety checks | L1   |                   |
|     |     are conducted as part of the  |      |                   |
|     |     screening process.            |      |                   |
+-----+-----------------------------------+------+-------------------+
| F   | 5.  Fixed and/or mobile roadside  | L1   |                   |
|     |     check stations are employed   |      |                   |
|     |     for electronic clearance      |      |                   |
|     |     functions, according to the   |      |                   |
|     |     jurisdiction's needs and      |      |                   |
|     |     resources.                    |      |                   |
+-----+-----------------------------------+------+-------------------+
| F   | 6.  Jurisdictions support a       | E    |                   |
|     |     common set of screening       |      |                   |
|     |     criteria.                     |      |                   |
+-----+-----------------------------------+------+-------------------+
| F   | 7.  Screening systems are         | E    |                   |
|     |     interoperable with those in   |      |                   |
|     |     different jurisdictions.      |      |                   |
+-----+-----------------------------------+------+-------------------+

### State Institutional Framework 

As stated in the COACH Part 1 Operational Concept and Top-Level Design
Checklists, 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 table shows
Maryland\'s commitment level.

####  {#section-1 .unnumbered}

+-----+-------------------------------------+-----+--------------------+
| Com | Compatibility Criteria              | Req | Comments           |
| mit |                                     | Le  |                    |
| Le  |                                     | vel |                    |
| vel |                                     | (L  |                    |
| (   |                                     | 1/E |                    |
| F/P |                                     | /C) |                    |
| /N) |                                     |     |                    |
+=====+=====================================+=====+====================+
| F   | 1.  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.                  |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 2.  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;   |     |                    |
|     |     representative of the FHWA      |     |                    |
|     |     Division office; and a motor    |     |                    |
|     |     carrier industry representative |     |                    |
|     |     (invited). See Reference 62 for |     |                    |
|     |     qualification details.          |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 3.  Appropriate and sufficient      | L1  |                    |
|     |     staff, equipment, and State and |     |                    |
|     |     private funding are available   |     |                    |
|     |     to carry out the deployment of  |     |                    |
|     |     CVISN and ITS/CVO services. The |     |                    |
|     |     CVISN project has sufficient    |     |                    |
|     |     priority (i.e., other           |     |                    |
|     |     higher-priority projects are    |     |                    |
|     |     not competing for the same      |     |                    |
|     |     resources).                     |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 4.  A State CVO strategic plan      | L1  |                    |
|     |     and/or business plan exists and |     |                    |
|     |     has been accepted by the FHWA.  |     |                    |
|     |     It outlines the goals,          |     |                    |
|     |     strategies, anticipated         |     |                    |
|     |     benefits and costs,             |     |                    |
|     |     organization, projects,         |     |                    |
|     |     schedules, and resources        |     |                    |
|     |     relevant to achieving the       |     |                    |
|     |     envisioned CVO environment.     |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 5.  A planning and coordination     | L1  |                    |
|     |     process exists which includes   |     |                    |
|     |     all State agencies involved in  |     |                    |
|     |     any aspect of motor carrier     |     |                    |
|     |     safety and regulation.          |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 6.  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.             |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 7.  A process for resolution of     | L1  |                    |
|     |     conflicts among participating   |     |                    |
|     |     agencies exists.                |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 8.  State agencies have a strong    | L1  |                    |
|     |     commitment to customer service  |     |                    |
|     |     and the ability to work with    |     |                    |
|     |     the motor carrier industry in   |     |                    |
|     |     their State.                    |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 9.  State agencies involve the      | L1  |                    |
|     |     motor carrier industry in the   |     |                    |
|     |     planning process.               |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 10. State agencies conduct          | L1  |                    |
|     |     education programs to improve   |     |                    |
|     |     the safety performance and      |     |                    |
|     |     regulatory compliance of motor  |     |                    |
|     |     carriers.                       |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 11. State agencies provide periodic | L1  |                    |
|     |     forums for obtaining            |     |                    |
|     |     suggestions and concerns from   |     |                    |
|     |     the motor carrier industry.     |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 12. State agencies actively pursue  | L1  |                    |
|     |     opportunities for and implement |     |                    |
|     |     business process reengineering  |     |                    |
|     |     projects.                       |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 13. An e-mail system is available   | L1  |                    |
|     |     among agencies.                 |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 14. At least key agency staff       | L1  |                    |
|     |     members have access to the      |     |                    |
|     |     Internet.                       |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 15. The State has adopted an open   | L1  |                    |
|     |     standard (ANSI ASC X12, for     |     |                    |
|     |     example) for electronic data    |     |                    |
|     |     interchange with the public.    |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 16. The State's communications      | L1  |                    |
|     |     infrastructure is sufficiently  |     |                    |
|     |     developed to extend to the      |     |                    |
|     |     kinds of exchanges needed under |     |                    |
|     |     the CVISN Architecture.         |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 17. There are no State legislative  | L1  |                    |
|     |     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.          |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 18. The legislature provides        | L1  |                    |
|     |     adequate resources to support   |     |                    |
|     |     an active ITS/CVO program and   |     |                    |
|     |     deployment of the ITS/CVO       |     |                    |
|     |     services.                       |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 19. The State participates in one   | L1  | Maryland is part   |
|     |     or more regional CVO forums to  |     | of the I-95        |
|     |     assist in developing regional   |     | Corridor Coalition |
|     |     and national interoperable      |     | and other forums.  |
|     |     systems and compatible policies |     |                    |
|     |     and procedures.                 |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 20. The State is willing to provide | L1  |                    |
|     |     timely, electronic information  |     |                    |
|     |     to the planned clearinghouses   |     |                    |
|     |     to support the base state       |     |                    |
|     |     agreements.                     |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 21. The project team has completed  | L1  |                    |
|     |     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.                  |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 22. The State has identified and    | L1  |                    |
|     |     made adequate progress towards  |     |                    |
|     |     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.                      |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 23. Effective procurement plans and | L1  |                    |
|     |     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.               |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 24. Effective subcontract           | L1  |                    |
|     |     management processes are in     |     |                    |
|     |     place and allow timely          |     |                    |
|     |     identification and resolution   |     |                    |
|     |     of performance problems.        |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 25. The CVISN team has a clear      | L1  |                    |
|     |     understanding of the            |     |                    |
|     |     State-specific requirements for |     |                    |
|     |     information technology          |     |                    |
|     |     projects, e. g., whether or not |     |                    |
|     |     a feasibility study is          |     |                    |
|     |     required.                       |     |                    |
+-----+-------------------------------------+-----+--------------------+
| F   | 26. The CVISN team has a clear      | L1  |                    |
|     |     understanding of the            |     |                    |
|     |     State-specific budget cycles    |     |                    |
|     |     and is aware of constraints     |     |                    |
|     |     they impose.                    |     |                    |
+-----+-------------------------------------+-----+--------------------+

### State Systems Checklists

As stated in the COACH Part 1 Operational Concept and Top-Level Design
Checklists, the checklists in this section provide top-level
requirements for the design of state systems. The top-level requirements
are divided into these categories:

-   General

-   CV Administration

-   Safety Information Exchange and Safety Assurance

-   Electronic Screening

#### General State Systems Design Requirements

The general state system design requirements apply to all state systems.
They facilitate interoperability and the exchange of information within
a single state, and across jurisdictions. The item numbers in the
checklist refer to COACH Part 1, Chapter 5 State Systems Checklists. The
table shows Maryland\'s commitment level.

##### General State Systems Design Requirements Checklist

  -----------------------------------------------------------------------------------------------------
  Commit    Item \#     Compatibility Criteria            Req Level  Op     IOC    FOC    Comments
  Level                                                   (L1/E/C)   Test   Date   Date   
  (F/P/N)                                                            Date                 
  --------- ----------- --------------------------------- ---------- ------ ------ ------ -------------
                                                                                          

  F         **5.1.1**   Adopt standard identifiers for    L1                              Need USDOT
                        carriers, vehicles, drivers, and                                  source for
                        transponders to support                                           intrastate
                        information exchange                                              carriers.

  F         1           Adopt standard identifiers for    L1                              
                        interstate carrier, vehicle,                                      
                        driver, and transponder.                                          

  F         2           Adopt standard identifiers for    C                               
                        intrastate carrier, vehicle,                                      
                        driver, and transponder.                                          

  F         **5.1.2**   Use open standards for exchange   L1                              
                        of information with other                                         
                        jurisdictions and with the                                        
                        public.                                                           

  F         1           Use ANSI X12 EDI standards for    L1                              
                        transactions between state                                        
                        information systems and private                                   
                        systems (CV operators, insurance                                  
                        companies, etc.).                                                 

  F         2           Use ANSI X12 EDI standards for    L1                              
                        transactions between state                                        
                        information systems and CVISN                                     
                        Core Infrastructure systems,                                      
                        where available.                                                  

  F         3           Use XML standards for             C                               
                        transactions between state                                        
                        information systems and private                                   
                        systems (CV operators, insurance                                  
                        companies, etc.) (contingent on                                   
                        demonstration of feasibility).                                    

  F         **5.1.3**   Ensure that all information       L1                              
                        transfers, fee payments, and                                      
                        money transfers are authorized                                    
                        and secure.                                                       

  F         **5.1.4**   Exchange safety and credentials   L1                              Snapshots
                        data electronically within the                                    available at
                        state to support credentialing,                                   West
                        safety, and other roadside                                        Friendship
                        functions. Where useful, exchange                                 weigh
                        snapshots.                                                        station.

  F         1           Data for interstate carriers      L1                              

  F         2           Data for interstate vehicles      L1                              

  F         3           Data for intrastate carriers      E                               

  F         4           Data for intrastate vehicles      E                               

  N         5           Data for drivers                  C                               

  F         **5.1.5**   Demonstrate technical             L1                              
                        interoperability by performing                                    
                        Interoperability Tests.                                           

  F         **5.1.6**   Support electronic payments.      E                               
  -----------------------------------------------------------------------------------------------------

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

The Maryland safety information exchange and safety assurance systems
consist of:

-   ASPEN

-   SAFETYNET/AVALANCHE

-   Citation & Accident

-   CV Information Exchange Window (CVIEW)

The Maryland CV safety information exchange and safety assurance systems
will operate at one or more (generally) fixed locations within the
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 item numbers in the
checklist refer to COACH Part 1, Chapter 5. The table shows Maryland\'s
commitment level.

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

  --------- ----------- --------------------------------- ---------- ------ ------ ------ --------------
  Commit    Item \#     Compatibility Criteria            Req Level  Op     IOC    FOC    Comments
  Level                                                   (L1/E/C)   Test   Date   Date   
  (F/P/N)                                                            Date                 

                                                                                          

  F         **5.2.1**   Use ASPEN (or equivalent) at all  L1                              
                        major inspection sites                                            

  F         1           Select vehicles and drivers for   L1                              
                        inspection based on availability                                  
                        of inspector, standard inspection                                 
                        selection system, vehicle                                         
                        measures, and random process, as                                  
                        statutes permit.                                                  

  F         2           Report interstate inspections to  L1                              
                        MCMIS via SAFETYNET                                               

  F         3           Report intrastate inspections to  L1                              
                        SAFETYNET                                                         

  F         4           Submit interstate and intrastate  L1                              
                        inspections for 45-day storage to                                 
                        SAFER.                                                            

  F         5           Periodically check OOS orders     E                               
                        issued in the state to focus                                      
                        enforcement and safety assurance                                  
                        activities.                                                       

  F         6           To assist in inspection, use DSRC C                               
                        to retrieve summary vehicle                                       
                        safety sensor data, if driver                                     
                        allows and vehicle is properly                                    
                        equipped.                                                         

  F         7           To assist in inspection, use DSRC C                               
                        to retrieve driver's daily log,                                   
                        if driver allows and vehicle is                                   
                        properly equipped.                                                

  F         8           Use electronically-generated      C                               
                        driver's daily log, if driver                                     
                        offers as an alternative to a                                     
                        manually-maintained log during an                                 
                        inspection.                                                       

  F         **5.2.2**   SAFETYNET 2000 submits interstate L1                              
                        and intrastate inspections                                        
                        reports to SAFER.                                                 

  P         **5.2.3**   Use CAPRI (or equivalent) for     L1                              MD has its own
                        compliance reviews.                                               preventive
                                                                                          maintenance
                                                                                          program that
                                                                                          accomplishes
                                                                                          compliance
                                                                                          reviews.

  P         1           Report interstate compliance      L1                              
                        reviews to MCMIS via SAFETYNET                                    

  N         **5.2.4**   Collect, store, analyze, and      E                               
                        distribute citation data                                          
                        electronically.                                                   

  N         1           Report citations for interstate   E                               
                        operators to MCMIS via SAFETYNET                                  

  F         **5.2.5**   Collect, store, analyze, and      E                               Will support
                        distribute crash data                                             when
                        electronically.                                                   available.

  F         1           Report interstate crashes as      E                               
                        required to MCMIS via SAFETYNET                                   

  N         **5.2.6**   Compute carrier safety risk       E                               No intrastate
                        rating for intrastate carriers                                    operating
                        based on safety data collected.                                   licensing
                                                                                          req\'d in MD.

  F         **5.2.7**   Identify high risk drivers based  C                               MD
                        in the state through regular                                      participates
                        performance evaluation of various                                 in CDLIS.
                        factors such as license status,                                   
                        points, and inspections.                                          
  --------- ----------- --------------------------------- ---------- ------ ------ ------ --------------

#### State CV Administration Systems Design Requirements

The Maryland Commercial Vehicle administrative systems consist of

-   Interstate & Intrastate Vehicle Registration

-   Fuel Tax Credentialing/Tax Return Processing

-   Credentialing Interface (CI)

-   Titling

-   Treasury or Revenue

-   Oversize/Overweight Permitting

-   Electronic Screening Enrollment

These systems operate at one or more (generally) fixed locations within
Maryland. 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. The item numbers in the checklist refer to COACH
Part 1, Chapter 5. The table shows Maryland\'s commitment level.

##### State CV Administration Systems Design Requirements Checklist

  -----------------------------------------------------------------------------------------------------------
  Commit    Item \#      Compatibility Criteria              Req Level  Op     IOC    FOC    Comments
  Level                                                      (L1/E/C)   Test   Date   Date   
  (F/P/N)                                                               Date                 
  --------- ------------ ----------------------------------- ---------- ------ ------ ------ ----------------
                                                                                             

  F         **5.3.1**    Support electronic credentialing    L1                              2 large carriers
                         (electronic submission of                                           (Rollins &
                         applications, evaluation,                                           Penske) using
                         processing, and application                                         routinely, 4
                         response) for IRP using EDI                                         others
                         standards.                                                          occasionally.

  F         **5.3.2**    Proactively provide updates to      L1                              LSI flat file to
                         vehicle snapshots as needed when                                    CVIEW; CVIEW to
                         IRP credentials actions are taken,                                  SAFER is EDI.
                         using EDI standards.                                                

  F         1            Interface to SAFER for interstate   L1                              
                         vehicle snapshots, using EDI                                        
                         standards                                                           

  F         **5.3.3**    Proactively provide updates to      L1                              USDOT number not
                         carrier snapshots as needed when                                    reliably
                         IRP credentials actions are taken,                                  captured; cross
                         using EDI standards.                                                ref vehicle to
                                                                                             carrier not
                                                                                             established.

  F         1            Interface to SAFER for interstate   L1                              
                         carrier snapshots, using EDI                                        
                         standards                                                           

  F         **5.3.4**    Provide IRP Clearinghouse with IRP  L1                              
                         credential application information                                  
                         (recaps).                                                           

  F         1            Interface to IRP Clearinghouse      E                               This capability
                         using EDI standards.                                                is being
                                                                                             investigated by
                                                                                             an IRP CH
                                                                                             committee.
                                                                                             Change Request
                                                                                             Form 313 in
                                                                                             process.

  F         **5.3.5**    Review fees billed and/or collected L1                              MD in first wave
                         by a jurisdiction and the portion                                   of states to use
                         due other jurisdictions                                             Clearinghouse.
                         (transmittals) as provided by the                                   
                         IRP Clearinghouse.                                                  

  F         1            Interface to IRP Clearinghouse      L1                              This capability
                         using EDI standards.                                                is being
                                                                                             investigated by
                                                                                             an IRP CH
                                                                                             committee.
                                                                                             Change Request
                                                                                             Form 313 in
                                                                                             process.

  F         **5.3.6**    Support electronic state-to-state   L1                              
                         fee payments via IRP Clearinghouse                                  

  F         **5.3.7**    Support electronic credentialing    L1                              
                         (electronic submission of                                           
                         applications, evaluation,                                           
                         processing, and application                                         
                         response) for IFTA registration                                     
                         using EDI standards.                                                

  F         **5.3.8**    Proactively provide updates to      L1                              
                         carrier snapshots as needed when                                    
                         IFTA credentials actions are taken                                  
                         or tax payments are made, using EDI                                 
                         standards.                                                          

  F         1            Interface to SAFER for interstate   L1                              
                         carrier snapshots, using EDI                                        
                         standards                                                           

  F         **5.3.9**    Provide IFTA Clearinghouse with     L1                              IFTA RPC is
                         IFTA credential application                                         MD\'s agent now.
                         information using EDI standards.                                    Clearinghouse
                                                                                             may not accept
                                                                                             EDI.

  F         **5.3.10**   Support electronic tax filing for   L1                              
                         IFTA quarterly fuel tax returns                                     
                         using EDI standards.                                                

  F         **5.3.11**   Provide information on taxes        L1                              FTA RPC is MD\'s
                         collected by own jurisdiction and                                   agent now. RPC
                         the portion due other jurisdictions                                 reports to
                         (transmittals) to the IFTA                                          Clearinghouse in
                         Clearinghouse using EDI standards.                                  legacy format.

  F         **5.3.12**   Download for automated review the   L1                              FTA RPC is MD\'s
                         demographic information from the                                    agent now. RPC
                         IFTA Clearinghouse using EDI                                        reports to
                         standards.                                                          Clearinghouse in
                                                                                             legacy format.

  F         **5.3.13**   Download for automated review the   L1                              
                         transmittal information from the                                    
                         IFTA Clearinghouse using EDI                                        
                         standards.                                                          

  F         **5.3.14**   Retrieve IFTA tax rate information  L1                              
                         electronically from IFTA, Inc.                                      

  F         **5.3.15**   Support electronic credentialing    E                               MD does not
                         (electronic submission of                                           require
                         applications, evaluation,                                           registration for
                         processing, and application                                         intrastate
                         response) for other credentials                                     carriers, except
                         using EDI standards.                                                for flammables
                                                                                             and passenger
                                                                                             carriers.

  F         1            Interstate carrier registration     E                               

  P         2            Intrastate carrier registration     E                               

  F         3            Vehicle title                       E                               

  F         4            Intrastate vehicle registration     E                               

  P         5            HazMat credentialing/permitting, if E                               
                         such credentials/permits are                                        
                         required by state law.                                              

  F         6            Oversize/overweight permitting.     E                               

  F         **5.3.16**   Proactively provide updates to      E                               Already doing
                         vehicle snapshots as needed when                                    daily snapshot
                         credentials actions are taken,                                      updates of IRP
                         using EDI standards.                                                vehicle data.

  F         1            Vehicle title                       E                               

  F         2            Intrastate vehicle registration     E                               

  F         3            Oversize/overweight permitting.     E                               

  F         **5.3.17**   Proactively provide updates to      E                               Need way to map
                         carrier snapshots as needed when                                    MVA vehicle data
                         credentials actions are taken,                                      to carriers.
                         using EDI standards.                                                

  F         1            Interstate carrier registration     E                               

  P         2            Intrastate carrier registration     E                               

  P         3            HazMat credentialing/permitting, if E                               
                         such credentials/permits are                                        
                         required by state law.                                              

  F         4            Oversize/overweight permitting.     E                               

  F         **5.3.18**   Record transponder number and       E                               Just give us a
                         default carrier ID for each vehicle                                 system that does
                         that intends to participate in                                      it.
                         electronic screening.                                               

  F         **5.3.19**   Collect from the registrant a list  E                               
                         of jurisdictions in which the                                       
                         vehicle chooses to participate in                                   
                         electronic screening, and inform                                    
                         those jurisdictions.                                                

  P         **5.3.20**   Allow CV operators,                 E                               We will do this
                         government-operated, or third party                                 when MD usage of
                         systems to submit one or more                                       EDI is more
                         applications in a single                                            mature.
                         transaction.                                                        

  F         **5.3.21**   Provide commercial driver           L1                              MD utilizes
                         information to other jurisdictions                                  CDLIS.
                         via CDLIS.                                                          

  F         **5.3.22**   Evaluate safety performance prior   E                               
                         to issuing credentials (i.e.                                        
                         support PRISM processes or                                          
                         equivalent).                                                        

  F         **5.3.23**   Allow carriers to provide           C                               
                         information for audits                                              
                         electronically.                                                     

  F         **5.3.24**   Provide titling information to      C                               Status of NMVTIS
                         other jurisdictions via NMVTIS.                                     unclear.

  F         **5.3.25**   Provide revoked IFTA motor carrier  C                               
                         information to other jurisdictions                                  
                         via STOLEN.                                                         

  F         **5.3.26**   Accept electronic credential and    C                               Regulatory
                         supporting electronic                                               processes
                         documentation, in lieu of paper                                     outside MD\'s
                         versions.                                                           control need to
                                                                                             change. Example:
                                                                                             IRS requires
                                                                                             HVUT form on
                                                                                             file.

  N         **5.3.27**   Proactively provide updates to      C                               Data privacy
                         driver snapshots as needed when                                     concerns to be
                         credentials actions are taken,                                      resolved.
                         using EDI standards.                                                

                                                                                             
  -----------------------------------------------------------------------------------------------------------

#### State Electronic Screening Systems Design Requirements

The roadside systems in Maryland consist of:

-   Screening System

-   Roadside Operations System

-   Sensor/Driver Communications System

These roadside systems will operate at each fixed or mobile CV check
station within Maryland. 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. The item numbers in the checklist refer to COACH Part 1,
Chapter 5. The table shows Maryland\'s commitment level.

##### State Roadside Systems Design Requirements Checklist

  ----------------------------------------------------------------------------------------------------------
  Commit    Item \#     Compatibility Criteria              Req Level  Op     IOC    FOC    Comments
  Level                                                     (L1/E/C)   Test   Date   Date   
  (F/P/N)                                                              Date                 
  --------- ----------- ----------------------------------- ---------- ------ ------ ------ ----------------
                                                                                            

  F         **5.4.1**   Follow FHWA guidelines for          L1                              
                        Dedicated Short Range                                               
                        Communications (DSRC) equipment.                                    
                        Details below extracted from                                        
                        Reference 49.                                                       

  F         1           \"For the immediate future, all CVO L1                              
                        and Border Crossing projects will                                   
                        continue to utilize the current                                     
                        DSRC configuration employed by the                                  
                        programs. This is the \"ASTM                                        
                        version 6\" active tag.                                             

  F         2           Beginning January 1, 2001, all CVO  E                               
                        and Border Crossing projects will                                   
                        use an active configuration that is                                 
                        backward compatible with the                                        
                        current configuration and yet                                       
                        consists of the following:                                          

  F         2a          \"ASTM version 6\" defines the data E                               
                        link layer.                                                         

  F         2b          The IEEE P1455 application layer    E                               
                        standard and the ASTM 1 active                                      
                        physical layer standard will be                                     
                        implemented.\"                                                      

  F         **5.4.2**   Use snapshots to support screening  L1                              
                        decisions.                                                          

  F         1           Carrier snapshots.                  L1                              

  F         2           Vehicle snapshots.                  L1                              

  N         3           Driver snapshots.                   C                               

  F         **5.4.3**   Implement interoperability policies L1                              
                        as they are developed by ITS                                        
                        America, the American Association                                   
                        of State Highway Transportation                                     
                        Officials, HELP, Inc., MAPS,                                        
                        Advantage CVO, I-95 Corridor                                        
                        Coalition, and the Commercial                                       
                        Vehicle Safety Alliance.                                            

  F         1           See AASHTO\'s Commercial Vehicle    L1                              
                        Electronic Screening                                                
                        Interoperability Policy Resolution,                                 
                        PR-14-97, Reference 63.                                             

  F         **5.4.4**   Provide electronic mainline or ramp L1                              
                        screening for transponder-equipped                                  
                        vehicles, and clear for bypass if                                   
                        carrier & vehicle were properly                                     
                        identified and screening criteria                                   
                        were passed.                                                        

  F         1           For transponder-equipped vehicles,  L1                              
                        identify carrier at mainline or                                     
                        ramp speeds.                                                        

  F         2           For transponder-equipped vehicles,  L1                              
                        identify vehicle at mainline or                                     
                        ramp speeds.                                                        

  F         3           Use WIM or weight history at        L1                              
                        mainline speed or on the ramp in                                    
                        making screening decisions.                                         

  F         4           Record screening event data.        E                               

  N         5           For transponder-equipped vehicles,  C                               
                        identify driver at mainline or ramp                                 
                        speeds.                                                             

  F         **5.4.5**   Verify credentials/safety           L1                              Done via
                        information with authoritative                                      existing
                        source prior to issuing citation.                                   communications
                                                                                            methods.

  F         **5.4.6**   If a vehicle illegally bypasses or  C                               
                        leaves the CV check station, alert                                  
                        law enforcement for possible                                        
                        apprehension.                                                       

  F         **5.4.7**   Report periodically to State safety C                               
                        information system on the                                           
                        activities conducted at each                                        
                        station (e.g. statistics).                                          
  ----------------------------------------------------------------------------------------------------------

### CVISN Core Infrastructure Systems Checklists

The top-level requirements for the design of CVISN Core Infrastructure
systems are divided into these categories:

-   General

-   IRP Clearinghouse

-   IFTA Clearinghouse

-   SAFER

-   CDLIS

-   NMVTIS

-   RSPA

-   MCMIS

-   Licensing & Insurance

-   ASAP

-   CAPRI

Maryland intends to use the capabilities provided by CVISN Core
Infrastructure systems, except RSPA and CAPRI.

## Interface Specification Checklist

The COACH Part 4 Interface Specification Checklists includes several
types of checklists related to interfaces:

-   Standard Interface Identification Tables, identifying the
    standardized interfaces to be used between pairs of products

-   Standard Data Definitions, specifying data format and meaning
    conventions for items common to more than one standard interface

The checklists are intended to be used to indicate with which items the
state agrees, and to provide a mechanism for planning development
activities.

### Standard Interface Identification 

**[ANSI ASC X12 EDI Standard Transaction Sets]{.underline}**

These are the ANSI EDI standards used in CVISN applications. A subset of
these transactions is used to support Level 1 capabilities.

TS 150 Tax Rate Notification

TS 151 Electronic Filing of Tax Return Data Acknowledgement

TS 284 CV Safety Reports (available for non-ASPEN inspection systems)

TS 285 CV Safety & Credentials Information Exchange (snapshots)

TS 286 Commercial Vehicle (CV) Credentials

TS 813 Electronic Filing of Tax Return Data

TS 820 Payment Order/Remittance Advice

TS 824 Application Advice

TS 826 Tax Information Exchange

TS 997 Functional Acknowledgement

**[DSRC-Related Standards]{.underline}**

These ANSI and DSRC open standards are the ones that states implementing
CVISN capabilities should adopt. The DSRC standards are still in the
approval cycle.

ASTM E17.51 Physical & Data Link Layers

IEEE P1455 Message Set

**[Internet Standards]{.underline}**

The interfaces between carrier's Internet browsers and various World
Wide Web applications use Internet standards. See <http://www.w3.org/>
for information about Internet standards.

**[Custom Interface Agreements]{.underline}**

The interfaces between FHWA-developed safety-related systems (ASPEN and
SAFER, ASPEN and CVIEW, SAFER and SAFETYNET, SAFER and MCMIS, SAFER and
Licensing & Insurance) are based on custom interface agreements defined
by the system developers and endorsed by FHWA. Under special
circumstances, FHWA tolerates, but does not encourage, the use of custom
interface agreements for interchanges between systems operated under
different "jurisdictions".

**[Purposes of the Interfaces]{.underline}**

The purposes of the interfaces are explained in the remainder of this
section.

In Figure 2-1, the standard names (e.g., X12 TS 286) have been replaced
with letters. The letters correspond to particular functions as
illustrated in the table that follows.

![](media/image1.wmf)

> Figure 2-1. CVISN Level 1 Interface Functions (Generic)

The checklist table below, Table 2-1, explains the purpose for each
standardized interface shown in Figure 2-1. In addition to the standard
column definitions explained in section 2.2, this table contains these
columns:

-   Label -- identifier

-   Std -- the open standard or custom interface agreement to which the
    label refers and references that contain details of the standard and
    how to implement it

```{=html}
<!-- -->
```
-   Interface Purpose - summary versions of the interface exchanges
    expected, culled from other CVISN documentation

```{=html}
<!-- -->
```
-   From System -- based on the generic design, the system that will
    send the information listed in the Interface Purpose column

-   To System -- based on the generic design, the system that will
    receive the information listed in the Interface Purpose column

There are more interfaces listed in the table than are shown on the
drawings. Those additional interfaces correspond to enhanced or complete
capabilities, as indicated by the "Req Level" column. For details about
implementing the standardized interfaces, review the standards and
implementation guides.

If the 'Req Level" cell is in *italics*, it means that the capability
will be supported during the Level 1 timeframe, but is not yet available
as of October 1999.

There are several connection paths shown for ASPEN and SAFETYNET. They
represent the capabilities planned as the products evolve to more
powerful computers and more sophisticated software. Details of the
evolution paths will be included in the CVISN Guide to Safety
Information Exchange \[Reference 64\].

All of the CVISN Level 1 interfaces are shown in Table 2-1. Those
applicable to Maryland are shown in **bold**.

The categories of interfaces shown in Table 2-1 are:

-   EDI -- Electronic Data Interchange; ANSI X12 standards

-   DSRC -- Dedicated Short-Range Communications; IEEE and ASTM
    standards

-   AFF -- Application File Format; data structured in a format that is
    a precursor to an EDI exchange

-   INT -- Internet; HTML standards

-   CIA -- Custom Interface Agreement; data exchanged according to a
    particular custom interface agreement

Table 2‑1. Standard Interface Identification Table (Maryland Interfaces
in bold type)

+---+---+----+--------------------+---------+---------+---+---------+
| > | > | *  | **Interface        | **From  | **To    | > | **Com   |
|   |   | *S | Purpose**          | S       | S       |   | ments** |
| * | * | td |                    | ystem** | ystem** | * |         |
| * | * | ** |                    |         |         | * |         |
| C | L |    |                    |         |         | R |         |
| o | a |    |                    |         |         | e |         |
| m | b |    |                    |         |         | q |         |
| m | e |    |                    |         |         | t |         |
| i | l |    |                    |         |         | s |         |
| t | * |    |                    |         |         | * |         |
| > | * |    |                    |         |         | * |         |
|   |   |    |                    |         |         | > |         |
| L |   |    |                    |         |         | > |         |
| e |   |    |                    |         |         |   |         |
| v |   |    |                    |         |         | * |         |
| e |   |    |                    |         |         | * |         |
| l |   |    |                    |         |         | L |         |
| > |   |    |                    |         |         | e |         |
|   |   |    |                    |         |         | v |         |
| ( |   |    |                    |         |         | e |         |
| F |   |    |                    |         |         | l |         |
| / |   |    |                    |         |         | * |         |
| P |   |    |                    |         |         | * |         |
| / |   |    |                    |         |         |   |         |
| N |   |    |                    |         |         |   |         |
| ) |   |    |                    |         |         |   |         |
| * |   |    |                    |         |         |   |         |
| * |   |    |                    |         |         |   |         |
+===+===+====+====================+=========+=========+===+=========+
| P | E | TS | Commercial Vehicle | CAT     | CI      | L | L1 =    |
|   | D | 2  | (CV) Credentials:  |         |         | 1 | IRP &   |
|   | I | 86 |                    | CAT     | CI      | ; | IFTA    |
|   | - |    | -   **Submit       |         |         | E |         |
|   | A | R  |     initial/re     | CAT     | CI      |   | E =     |
|   |   | ef | newal/supplemental |         |         |   | other   |
|   |   | 1  |     electronic     | CAT     | CI      |   | cred    |
|   |   | 3, |     application    |         |         |   | entials |
|   |   | 4  |     for            | CAT     | CI      |   |         |
|   |   | 0, |     credentials**  |         |         |   | Trip    |
|   |   | 4  |                    | CAT     | CI      |   | p       |
|   |   | 2, | -   Submit trip    |         |         |   | ermits, |
|   |   | 4  |     permit         | CI      | CAT     |   | IFTA    |
|   |   | 3, |     application    |         |         |   | te      |
|   |   | 45 |                    | CI      | CAT     |   | mporary |
|   |   |    | -   **Notify payee |         |         |   | cred    |
|   |   |    |     of payment     | CI      | CAT     |   | entials |
|   |   |    |     method**       |         |         |   | will    |
|   |   |    |                    | CI      | CAT     |   | not be  |
|   |   |    | -   **Submit       |         |         |   | h       |
|   |   |    |     corrected      | CI      | CAT     |   | andled. |
|   |   |    |     application**  |         |         |   |         |
|   |   |    |                    | CI      | CAT     |   |         |
|   |   |    | -   **Send renewal |         |         |   |         |
|   |   |    |     notice**       |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Return       |         |         |   |         |
|   |   |    |     credentials    |         |         |   |         |
|   |   |    |     data to        |         |         |   |         |
|   |   |    |     applicant**    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Return       |         |         |   |         |
|   |   |    |     temporary      |         |         |   |         |
|   |   |    |     credential**   |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   Return trip    |         |         |   |         |
|   |   |    |     permit         |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Notify payer |         |         |   |         |
|   |   |    |     of fees due**  |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Reject       |         |         |   |         |
|   |   |    |     application**  |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| N | E | TS | CV Credentials:    | CI      | Legacy  | L | L1 =    |
|   | D | 2  |                    |         | admin   | 1 | IRP &   |
|   | I | 86 | -   Pass           | Legacy  | system  | ; | IFTA    |
|   | - |    |     application to | admin   |         | E |         |
|   | B | R  |     legacy system  | system  | CI      |   | E =     |
|   |   | ef |                    |         |         |   | other   |
|   |   | 1  | -   Return         | Legacy  | CI      |   | cred    |
|   |   | 3, |     credentials    | admin   |         |   | entials |
|   |   | 4  |     data           | system  | CI      |   |         |
|   |   | 0, |                    |         |         |   | Trip    |
|   |   | 4  | -   Return         | Legacy  | CI      |   | p       |
|   |   | 2, |     temporary      | admin   |         |   | ermits, |
|   |   | 4  |     credential     | system  | CI      |   | IFTA    |
|   |   | 3, |                    |         |         |   | te      |
|   |   | 45 | -   Return trip    | Legacy  |         |   | mporary |
|   |   |    |     permit         | admin   |         |   | cred    |
|   |   |    |                    | system  |         |   | entials |
|   |   |    | -   Report fees    |         |         |   | will    |
|   |   |    |     due            | Legacy  |         |   | not be  |
|   |   |    |                    | admin   |         |   | h       |
|   |   |    | -   Reject         | system  |         |   | andled. |
|   |   |    |     application    |         |         |   |         |
|   |   |    |                    |         |         |   | A batch |
|   |   |    |                    |         |         |   | file    |
|   |   |    |                    |         |         |   | in      |
|   |   |    |                    |         |         |   | terface |
|   |   |    |                    |         |         |   | will be |
|   |   |    |                    |         |         |   | used    |
|   |   |    |                    |         |         |   | for     |
|   |   |    |                    |         |         |   | IFTA.   |
+---+---+----+--------------------+---------+---------+---+---------+
| P | E | TS | CV Safety &        | Legacy  | CVIEW   | L | L1 =    |
|   | D | 2  | Credentials        | admin   |         | 1 | carrier |
|   | I | 85 | Information        | system  | CVIEW   | ; | &       |
|   | - |    | Exchange:          | (or CI) |         | C | vehicle |
|   | C | R  |                    |         | Legacy  |   |         |
|   |   | ef | -   **Update       | Legacy  | admin   |   | C =     |
|   |   | 1  |     snapshot       | admin   | system  |   | driver  |
|   |   | 3, |     segment**      | system  | (or CI) |   |         |
|   |   | 3  |                    | (or CI) |         |   | Legacy  |
|   |   | 9, | -   Request        |         |         |   | system  |
|   |   | 45 |     carrier,       | CVIEW   |         |   | does    |
|   |   |    |     vehicle, or    |         |         |   | not     |
|   |   |    |     driver         |         |         |   | support |
|   |   |    |     information    |         |         |   | r       |
|   |   |    |     (i.e. request  |         |         |   | equests |
|   |   |    |     a snapshot     |         |         |   | or      |
|   |   |    |     view)          |         |         |   | re      |
|   |   |    |                    |         |         |   | sponses |
|   |   |    | -   Respond to     |         |         |   | from    |
|   |   |    |     carrier,       |         |         |   | CVIEW.  |
|   |   |    |     vehicle, or    |         |         |   |         |
|   |   |    |     driver         |         |         |   |         |
|   |   |    |     information    |         |         |   |         |
|   |   |    |     request or     |         |         |   |         |
|   |   |    |     fulfill        |         |         |   |         |
|   |   |    |     subscription   |         |         |   |         |
|   |   |    |     (i.e. send one |         |         |   |         |
|   |   |    |     or more        |         |         |   |         |
|   |   |    |     snapshots      |         |         |   |         |
|   |   |    |     using a        |         |         |   |         |
|   |   |    |     particular     |         |         |   |         |
|   |   |    |     view)          |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | E | TS | CV Credentials:    | State   | IFTA    | L |         |
|   | D | 2  |                    | IFTA    | Cleari  | 1 |         |
|   | I | 86 | -   **Submit       | Regis   | nghouse |   |         |
|   | - |    |     application    | tration |         |   |         |
|   | D | R  |     data**         |         | State   |   |         |
|   |   | ef |                    | IFTA    | IFTA    |   |         |
|   |   | 1  | -   **Retrieve     | Cleari  | Regis   |   |         |
|   |   | 3, |     demographic    | nghouse | tration |   |         |
|   |   | 4  |     data from      |         |         |   |         |
|   |   | 2, |     Clearinghouse  |         |         |   |         |
|   |   | 45 |     for review**   |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | E | TS | CV Safety &        | CVIEW   | SAFER   | L | L1 =    |
|   | D | 2  | Credentials        |         |         | 1 | carrier |
|   | I | 85 | Information        | CVIEW   | SAFER   | ; | &       |
|   | - |    | Exchange:          |         |         | C | vehicle |
|   | E | R  |                    | SAFER   | CVIEW   |   |         |
|   |   | ef | -   **Update       |         |         |   | C =     |
|   |   | 1  |     snapshot       | SAFER   | CVIEW   |   | driver  |
|   |   | 3, |     segment**      |         |         |   |         |
|   |   | 4  |                    |         |         |   |         |
|   |   | 2, | -   **Request      |         |         |   |         |
|   |   | 45 |     carrier,       |         |         |   |         |
|   |   |    |     vehicle, or    |         |         |   |         |
|   |   |    |     driver         |         |         |   |         |
|   |   |    |     information    |         |         |   |         |
|   |   |    |     (i.e. request  |         |         |   |         |
|   |   |    |     a snapshot     |         |         |   |         |
|   |   |    |     view)**        |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Respond to   |         |         |   |         |
|   |   |    |     carrier,       |         |         |   |         |
|   |   |    |     vehicle, or    |         |         |   |         |
|   |   |    |     driver         |         |         |   |         |
|   |   |    |     information    |         |         |   |         |
|   |   |    |     request or     |         |         |   |         |
|   |   |    |     fulfill        |         |         |   |         |
|   |   |    |     subscription   |         |         |   |         |
|   |   |    |     (i.e. send one |         |         |   |         |
|   |   |    |     or more        |         |         |   |         |
|   |   |    |     snapshots      |         |         |   |         |
|   |   |    |     using a        |         |         |   |         |
|   |   |    |     particular     |         |         |   |         |
|   |   |    |     view)**        |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Update       |         |         |   |         |
|   |   |    |     snapshot       |         |         |   |         |
|   |   |    |     segment**      |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | E | TS | CV Safety &        | R       | CVIEW   | L | L1 =    |
|   | D | 2  | Credentials        | oadside |         | 1 | carrier |
|   | I | 85 | Information        | Ope     | R       | ; | &       |
|   | - |    | Exchange           | rations | oadside | C | vehicle |
|   | F | R  |                    |         | Ope     |   |         |
|   |   | ef | -   **Request      | CVIEW   | rations |   | C =     |
|   |   | 1  |     carrier or     |         |         |   | driver  |
|   |   | 3, |     vehicle        |         |         |   |         |
|   |   | 4  |     information    |         |         |   |         |
|   |   | 2, |     (i.e. request  |         |         |   |         |
|   |   | 45 |     a snapshot     |         |         |   |         |
|   |   |    |     view)**        |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Respond to   |         |         |   |         |
|   |   |    |     carrier or     |         |         |   |         |
|   |   |    |     vehicle        |         |         |   |         |
|   |   |    |     information    |         |         |   |         |
|   |   |    |     request (i.e.  |         |         |   |         |
|   |   |    |     send one or    |         |         |   |         |
|   |   |    |     more snapshots |         |         |   |         |
|   |   |    |     using a        |         |         |   |         |
|   |   |    |     particular     |         |         |   |         |
|   |   |    |     view)**        |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | E | TS | CV Credentials:    | IRP     | State   | * | NOTE:   |
|   | D | 2  |                    | Cleari  | IRP     | L | Change  |
|   | I | 86 | -   **Summarize    | nghouse | System  | 1 | request |
|   | - |    |     fees billed    |         |         | * | in      |
|   | G | R  |     and/or         | IRP     | State   |   | process |
|   |   | ef |     collected by a | Cleari  | IRP     | * | for EDI |
|   |   | 1  |     jurisdiction,  | nghouse | System  | L | int     |
|   |   | 3, |     and the        |         |         | 1 | erfaces |
|   |   | 4  |     portion due to | State   | IRP     | * |         |
|   |   | 1, |     other          | IRP     | Cleari  |   |         |
|   |   | 45 |     jurisdictions  | System  | nghouse | E |         |
|   |   |    |     (nett          |         |         |   |         |
|   |   |    | ing/transmittal)** |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Provide      |         |         |   |         |
|   |   |    |     recaps for     |         |         |   |         |
|   |   |    |     retention      |         |         |   |         |
|   |   |    |     and/or         |         |         |   |         |
|   |   |    |     review**       |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Provide      |         |         |   |         |
|   |   |    |     recaps**       |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | E | TS | Tax Return:        | CAT     | CI      | L |         |
|   | D | 8  |                    |         |         | 1 |         |
|   | I | 13 | -   **File         |         |         |   |         |
|   | - |    |     electronic     |         |         |   |         |
|   | H | R  |     IFTA tax       |         |         |   |         |
|   |   | ef |     return**       |         |         |   |         |
|   |   | 1  |                    |         |         |   |         |
|   |   | 3, |                    |         |         |   |         |
|   |   | 60 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| N | E | TS | Tax Return:        | CI      | State   | L | Appl    |
|   | D | 8  |                    |         | IFTA    | 1 | ication |
|   | I | 13 | -   Pass tax       |         | Tax     |   | File    |
|   | - |    |     return to IFTA |         | Pro     |   | Format  |
|   | I | R  |     tax return     |         | cessing |   | will be |
|   |   | ef |     processing     |         | System  |   | used.   |
|   |   | 1  |     system         |         |         |   |         |
|   |   | 3, |                    |         |         |   |         |
|   |   | 60 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| N | E | TS | CV Safety &        | IFTA or | SAFER   | * | We do   |
| A | D | 2  | Credentials        | IRP     |         | L | it      |
|   | I | 85 | Information        | Cleari  |         | 1 | our     |
|   | - |    | Exchange:          | nghouse |         | * | selves. |
|   | J | R  |                    |         |         |   |         |
|   |   | ef | -   Update         |         |         |   |         |
|   |   | 1  |     snapshot       |         |         |   |         |
|   |   | 3, |     segment        |         |         |   |         |
|   |   | 3  |                    |         |         |   |         |
|   |   | 9, |                    |         |         |   |         |
|   |   | 45 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | E | TS | Tax Information    | IFTA    | State   | L |         |
|   | D | 8  | Exchange:          | Cleari  | IFTA    | 1 |         |
|   | I | 26 |                    | nghouse | Tax     |   |         |
|   | - |    | -   **Send data on |         | Pro     |   |         |
|   | K | R  |     fuel tax       |         | cessing |   |         |
|   |   | ef |     filings among  |         | System  |   |         |
|   |   | 1  |     jurisdictions; |         |         |   |         |
|   |   | 3, |     summarize      |         |         |   |         |
|   |   | 61 |     detailed tax   |         |         |   |         |
|   |   |    |     information    |         |         |   |         |
|   |   |    |     from           |         |         |   |         |
|   |   |    |     individual     |         |         |   |         |
|   |   |    |     returns and    |         |         |   |         |
|   |   |    |     balance        |         |         |   |         |
|   |   |    |     due/owed       |         |         |   |         |
|   |   |    |     (netting and   |         |         |   |         |
|   |   |    |     pre-netting    |         |         |   |         |
|   |   |    |     summaries)**   |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | E | TS | Tax Rate           | CI      | CAT     | E |         |
|   | D | 1  | Notification       |         |         |   |         |
|   | I | 50 |                    |         |         |   |         |
|   | - |    | -   **Send latest  |         |         |   |         |
|   | L | R  |     IFTA tax       |         |         |   |         |
|   |   | ef |     rates**        |         |         |   |         |
|   |   | 1  |                    |         |         |   |         |
|   |   | 3, |                    |         |         |   |         |
|   |   | 59 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| N | E | TS | CV Safety Reports  | CVIEW   | SAFER   | * | (not    |
|   | D | 2  | (Inspection        |         |         | L | shown   |
|   | I | 84 | Report)            | CVIEW   | SAFER   | 1 | on      |
|   | - |    |                    |         |         | * | f       |
|   | M | R  | -   Submit safety  | SAFER   | CVIEW   |   | igures; |
|   |   | ef |     report         |         |         |   | to      |
|   |   | 1  |                    |         |         |   | support |
|   |   | 3, | -   Request safety |         |         |   | no      |
|   |   | 4  |     report         |         |         |   | n-ASPEN |
|   |   | 5, |                    |         |         |   | Ins     |
|   |   | 56 | -   Respond to     |         |         |   | pection |
|   |   |    |     safety report  |         |         |   | s       |
|   |   |    |     request        |         |         |   | ystems) |
+---+---+----+--------------------+---------+---------+---+---------+
| N | E | TS | CV Safety Reports  | no      | CVIEW   | * | ASPEN   |
|   | D | 2  | (Inspection        | n-ASPEN |         | L | is our  |
|   | I | 84 | Report)            | Ins     | CVIEW   | 1 | au      |
|   | - |    |                    | pection |         | * | tomated |
|   | N | R  | -   Submit         | system  | no      |   | ins     |
|   |   | ef |     original       |         | n-ASPEN |   | pection |
|   |   | 1  |     safety report  | no      | Ins     |   | system. |
|   |   | 3, |                    | n-ASPEN | pection |   |         |
|   |   | 4  | ```{=html}         | Ins     | system  |   |         |
|   |   | 5, | <!-- -->           | pection |         |   |         |
|   |   | 56 | ```                | system  |         |   |         |
|   |   |    | -   Request safety |         |         |   |         |
|   |   |    |     report         | CVIEW   |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | ```{=html}         |         |         |   |         |
|   |   |    | <!-- -->           |         |         |   |         |
|   |   |    | ```                |         |         |   |         |
|   |   |    | -   Respond to     |         |         |   |         |
|   |   |    |     safety report  |         |         |   |         |
|   |   |    |     request        |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| N | E | TS | CV Safety Reports  | C       | SA      | C | SDM =   |
|   | D | 2  | (Crash Data)       | itation | FETYNET |   | SAFER   |
|   | I | 84 |                    | &       | 2000    |   | Data    |
|   | - |    | -   Submit         | A       | via     |   | Mailbox |
|   | O | R  |     original       | ccident | CVIEW & |   |         |
|   |   | ef |     safety report  |         | SDM     |   |         |
|   |   | 1  |                    |         |         |   |         |
|   |   | 3, |                    |         |         |   |         |
|   |   | 4  |                    |         |         |   |         |
|   |   | 5, |                    |         |         |   |         |
|   |   | T  |                    |         |         |   |         |
|   |   | BD |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| P | E | TS | Application Advice | r       | sender  | * | CI may  |
|   | D | 8  |                    | eceiver | of 285  | L | not use |
|   | I | 24 | -   Acknowledge    | of 285  |         | 1 | Appl    |
|   | - |    |     successful     |         | sender  | * | ication |
|   | P | R  |     processing of  | r       | of 285  |   | Advice  |
|   |   | ef |     TS 285 update  | eceiver |         |   | Transa  |
|   |   | 1  |     message data   | of 285  |         |   | ctions. |
|   |   | 3, |                    |         |         |   |         |
|   |   | 4  | -   Report errors  |         |         |   |         |
|   |   | 5, |     in processing  |         |         |   |         |
|   |   | T  |     of TS 285      |         |         |   |         |
|   |   | BD |     update message |         |         |   |         |
|   |   |    |     data           |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| ? | E | TS | Tax Rate           | State   | CI      | E | From    |
|   | D | 1  | Notification       | IFTA    |         |   | IFTA    |
|   | I | 50 |                    | Tax     |         |   | website |
|   | - |    | -   Send latest    | Pro     |         |   |         |
|   | Q | R  |     IFTA tax rates | cessing |         |   |         |
|   |   | ef |                    | System  |         |   |         |
|   |   | 1  |                    |         |         |   |         |
|   |   | 3, |                    |         |         |   |         |
|   |   | 59 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
|   | E |    | *reserved*         |         |         |   |         |
|   | D |    |                    |         |         |   |         |
|   | I |    |                    |         |         |   |         |
|   | - |    |                    |         |         |   |         |
|   | R |    |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| N | E | TS | Payment            | payer   | payer's | E |         |
|   | D | 8  | Order/Remittance   |         | bank    |   |         |
|   | I | 20 | Advice :           | state's |         |   |         |
|   | - |    |                    | bank    | State   |   |         |
|   | S | R  | -   Initiate EFT   |         | T       |   |         |
|   |   | ef |     payment        |         | reasury |   |         |
|   |   | 13 |                    |         | or      |   |         |
|   |   |    | -   Report payment |         | Revenue |   |         |
|   |   |    |     received       |         | system  |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | E | TS | Electronic Filing  | State   | CI      | L |         |
|   | D | 1  | of Tax Return Data | IFTA    |         | 1 |         |
|   | I | 51 | Acknowledgement    | Tax     |         |   |         |
|   | - |    |                    | Pro     |         |   |         |
|   | T | R  | -   **Report       | cessing |         |   |         |
|   |   | ef |     errors         | System  |         |   |         |
|   |   | 71 |     encountered    |         |         |   |         |
|   |   | 3, |     when           |         |         |   |         |
|   |   | 57 |     attempting to  |         |         |   |         |
|   |   |    |     process IFTA   |         |         |   |         |
|   |   |    |     tax return     |         |         |   |         |
|   |   |    |     (813)**        |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | E | TS | Electronic Filing  | CI      | CAT     | L |         |
|   | D | 1  | of Tax Return Data |         |         | 1 |         |
|   | I | 51 | Acknowledgement    | CI      | CAT     |   |         |
|   | - |    |                    |         |         |   |         |
|   | U | R  | -   **Pass IFTA    |         |         |   |         |
|   |   | ef |     tax return     |         |         |   |         |
|   |   | 1  |     error          |         |         |   |         |
|   |   | 3, |     message**      |         |         |   |         |
|   |   | 57 |                    |         |         |   |         |
|   |   |    | -   **Pass IFTA    |         |         |   |         |
|   |   |    |     tax return     |         |         |   |         |
|   |   |    |     successfully   |         |         |   |         |
|   |   |    |     processed      |         |         |   |         |
|   |   |    |     message**      |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | E | TS | **Acknowledge**    | all     | all EDI | L |         |
|   | D | 9  |                    | EDI-re  | s       | 1 |         |
|   | I | 97 |                    | ceiving | ending- |   |         |
|   | - |    |                    | systems | systems |   |         |
|   | V | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 1  |                    |         |         |   |         |
|   |   | 3, |                    |         |         |   |         |
|   |   | 58 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| N | E | TS | CV Credentials:    | State   | State   | L | Batch   |
|   | D | 2  |                    | IFTA    | IFTA    | 1 | file    |
|   | I | 86 | -   Submit         | Regis   | Tax     |   |         |
|   | - |    |     application    | tration | Pro     |   |         |
|   | W | R  |     data (complete | System  | cessing |   |         |
|   |   | ef |     or subset;     |         | System  |   |         |
|   |   | 1  |     (demographic   |         |         |   |         |
|   |   | 3, |     information)   |         |         |   |         |
|   |   | 4  |                    |         |         |   |         |
|   |   | 2, |                    |         |         |   |         |
|   |   | 45 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| N | E | TS | Inspection Report  | SAFER   | Law     | * |         |
|   | D | 2  |                    |         | Enfo    | L |         |
|   | I | 84 | -   Fulfill        | Law     | rcement | 1 |         |
|   | - |    |     inspection     | Enforc  | User    | * |         |
|   | X | R  |     report         | User    |         |   |         |
|   |   | ef |     subscription   |         | SAFER   |   |         |
|   |   | 1  |                    | SAFER   |         |   |         |
|   |   | 3, | ```{=html}         |         | Law     |   |         |
|   |   | 4  | <!-- -->           |         | Enforc  |   |         |
|   |   | 5, | ```                |         | User    |   |         |
|   |   | 56 | -   Query for      |         |         |   |         |
|   |   |    |     inspection     |         |         |   |         |
|   |   |    |     report         |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | ```{=html}         |         |         |   |         |
|   |   |    | <!-- -->           |         |         |   |         |
|   |   |    | ```                |         |         |   |         |
|   |   |    | -   Respond to     |         |         |   |         |
|   |   |    |     inspection     |         |         |   |         |
|   |   |    |     query          |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
|   |   |    |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
|   | D | v  | According to draft |         |         |   |         |
|   | S | ar | USDOT policy,      |         |         |   |         |
|   | R | io |                    |         |         |   |         |
|   | C | us | -   For the        |         |         |   |         |
|   |   |    |     immediate      |         |         |   |         |
|   |   |    |     future, all    |         |         |   |         |
|   |   |    |     CVO and Border |         |         |   |         |
|   |   |    |     crossing       |         |         |   |         |
|   |   |    |     projects will  |         |         |   |         |
|   |   |    |     continue to    |         |         |   |         |
|   |   |    |     utilize the    |         |         |   |         |
|   |   |    |     current DSRC   |         |         |   |         |
|   |   |    |     configuration  |         |         |   |         |
|   |   |    |     employed by    |         |         |   |         |
|   |   |    |     the programs.  |         |         |   |         |
|   |   |    |     This is the    |         |         |   |         |
|   |   |    |     ASTM 1 version |         |         |   |         |
|   |   |    |     6, ASTM 2      |         |         |   |         |
|   |   |    |     version 6      |         |         |   |         |
|   |   |    |     active tag.    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   Beginning      |         |         |   |         |
|   |   |    |     January 1,     |         |         |   |         |
|   |   |    |     2001, all CVO  |         |         |   |         |
|   |   |    |     and Border     |         |         |   |         |
|   |   |    |     Crossing       |         |         |   |         |
|   |   |    |     projects will  |         |         |   |         |
|   |   |    |     use an active  |         |         |   |         |
|   |   |    |     configuration  |         |         |   |         |
|   |   |    |     that is        |         |         |   |         |
|   |   |    |     backward       |         |         |   |         |
|   |   |    |     compatible     |         |         |   |         |
|   |   |    |     with the       |         |         |   |         |
|   |   |    |     current        |         |         |   |         |
|   |   |    |     configuration  |         |         |   |         |
|   |   |    |     and yet        |         |         |   |         |
|   |   |    |     consists of    |         |         |   |         |
|   |   |    |     the following: |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | > A. ASTM 2        |         |         |   |         |
|   |   |    | > version 6        |         |         |   |         |
|   |   |    | > defines the data |         |         |   |         |
|   |   |    | > link layer.      |         |         |   |         |
|   |   |    | >                  |         |         |   |         |
|   |   |    | > B. The IEEE      |         |         |   |         |
|   |   |    | > P1455            |         |         |   |         |
|   |   |    | > application      |         |         |   |         |
|   |   |    | > layer standard   |         |         |   |         |
|   |   |    | > and the ASTM 1   |         |         |   |         |
|   |   |    | > version 7 active |         |         |   |         |
|   |   |    | > physical layer   |         |         |   |         |
|   |   |    | > standard will be |         |         |   |         |
|   |   |    | > implemented.     |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | D | IE | CV Electronic      | Tran    | Sc      | E |         |
|   | S | EE | Screening Message  | sponder | reening |   |         |
|   | R | P  | Set                |         | /Driver |   |         |
|   | C | 14 |                    |         | Comm    |   |         |
|   | - | 55 | -   **CV Screening |         |         |   |         |
|   | A |    |                    |         |         |   |         |
|   |   | R  |   Identification** |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 49 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| P | D | IE | CV Screening       | Tran    | Sc      | C |         |
|   | S | EE | Message Set        | sponder | reening |   |         |
|   | R | P  |                    | or      | /Driver |   |         |
|   | C | 14 | All messages       |         | Comm or |   |         |
|   | - | 55 |                    | Sc      |         |   |         |
|   | B |    |                    | reening | Tran    |   |         |
|   |   | R  |                    | /Driver | sponder |   |         |
|   |   | ef |                    | Comm    |         |   |         |
|   |   | 49 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| N | D | IE | CV Border          | Tran    | Sc      | L |         |
|   | S | EE | Clearance Message  | sponder | reening | 1 |         |
|   | R | P  | Set                |         | /Driver |   |         |
|   | C | 14 |                    |         | Comm    |   |         |
|   | - | 55 | -   Trip           |         |         |   |         |
|   | C |    |     Identification |         |         |   |         |
|   |   | R  |     Number message |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 49 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| N | D | IE | CV Border          | Tran    | Sc      | C |         |
|   | S | EE | Clearance Message  | sponder | reening |   |         |
|   | R | P  | Set                | or      | /Driver |   |         |
|   | C | 14 |                    |         | Comm or |   |         |
|   | - | 55 | All messages       | Sc      |         |   |         |
|   | D |    |                    | reening | Tran    |   |         |
|   |   | R  |                    | /Driver | sponder |   |         |
|   |   | ef |                    | Comm    |         |   |         |
|   |   | 49 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | D | AS | **ASTM 2 Data Link | Tran    | Sc      | L |         |
|   | S | TM | Layer (Level 2 in  | sponder | reening | 1 |         |
|   | R | 1  | OSI model)**       | or      | /Driver |   |         |
|   | C | 7. |                    |         | Comm or |   |         |
|   | - | 51 |                    | Sc      |         |   |         |
|   | E | V  |                    | reening | Tran    |   |         |
|   |   | er |                    | /Driver | sponder |   |         |
|   |   | 6  |                    | Comm    |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 48 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | D | AS | **ASTM 1 Physical  | Tran    | Sc      | L |         |
|   | S | TM | Link Layer (Level  | sponder | reening | 1 |         |
|   | R | 1  | 1 in OSI model)**  | or      | /Driver |   |         |
|   | C | 7. |                    |         | Comm or |   |         |
|   | - | 51 |                    | Sc      |         |   |         |
|   | F | V  |                    | reening | Tran    |   |         |
|   |   | er |                    | /Driver | sponder |   |         |
|   |   | 6  |                    | Comm    |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 47 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| ? | D | AS | ASTM 1 Physical    | Tran    | Sc      | E |         |
|   | S | TM | Link Layer (Level  | sponder | reening |   |         |
|   | R | 1  | 1 in OSI model)    | or      | /Driver |   |         |
|   | C | 7. |                    |         | Comm or |   |         |
|   | - | 51 |                    | Sc      |         |   |         |
|   | G | V  |                    | reening | Tran    |   |         |
|   |   | er |                    | /Driver | sponder |   |         |
|   |   | 7  |                    | Comm    |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 55 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
|   |   |    |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | A | ap | Snapshot           | SAFER   | A       | * |         |
|   | F | pl |                    |         | SPEN-32 | L |         |
|   | F | ic | -   **Fulfill      | A       |         | 1 |         |
|   | - | a- |     snapshot       | SPEN-32 | SAFER   | * |         |
|   | A | ti |     subscription** |         |         |   |         |
|   |   | on |                    | SAFER   | A       |   |         |
|   |   | fi | -   **Query for    |         | SPEN-32 |   |         |
|   |   | le |     snapshot(s)**  |         |         |   |         |
|   |   | fo |                    |         |         |   |         |
|   |   | rm | -   **Response to  |         |         |   |         |
|   |   | at |     query**        |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | A | ap | Inspection Report  | A       | SAFER   | * |         |
|   | F | pl |                    | SPEN-32 |         | L |         |
|   | F | ic | -   **Submit       |         | SAFER   | 1 |         |
|   | - | a- |     original       | A       |         | * |         |
|   | B | ti |     inspection     | SPEN-32 | A       |   |         |
|   |   | on |     report**       |         | SPEN-32 |   |         |
|   |   | fi |                    | SAFER   |         |   |         |
|   |   | le | ```{=html}         |         |         |   |         |
|   |   | fo | <!-- -->           |         |         |   |         |
|   |   | rm | ```                |         |         |   |         |
|   |   | at | -   **Query for    |         |         |   |         |
|   |   |    |     inspection     |         |         |   |         |
|   |   | R  |     report**       |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 | -   **Respond to   |         |         |   |         |
|   |   |    |     inspection     |         |         |   |         |
|   |   |    |     query**        |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | A | ap | Snapshot           | SAFER   | SA      | * |         |
|   | F | pl |                    |         | FETYNET | L |         |
|   | F | ic | -   **Fulfill      | SA      | 2000    | 1 |         |
|   | - | a- |     snapshot       | FETYNET |         | * |         |
|   | C | ti |     subscription** | 2000    | SAFER   |   |         |
|   |   | on |                    |         |         |   |         |
|   |   | fi | -   **Query for    | SAFER   | SA      |   |         |
|   |   | le |     snapshot(s)**  |         | FETYNET |   |         |
|   |   | fo |                    |         | 2000    |   |         |
|   |   | rm | -   **Response to  |         |         |   |         |
|   |   | at |     query**        |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | A | ap | Inspection         | SA      | MCMIS   | * | SDM =   |
|   | F | pl | Reports,           | FETYNET | via SDM | L | Safer   |
|   | F | ic | Compliance         | 2000    |         | 1 | Data    |
|   | - | a- | Reviews, Crash     |         | SA      | * | Mailbox |
|   | D | ti | Data, Enforcement  | MCMIS   | FETYNET |   |         |
|   |   | on | Data               | via SDM | 2000    |   |         |
|   |   | fi |                    |         |         |   |         |
|   |   | le | -   **Update       |         |         |   |         |
|   |   | fo |     request        |         |         |   |         |
|   |   | rm |     (upload and    |         |         |   |         |
|   |   | at |     store)**       |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  | -   **Update       |         |         |   |         |
|   |   | ef |     confirmation   |         |         |   |         |
|   |   | 50 |     (confirm       |         |         |   |         |
|   |   |    |     success)**     |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | A | ap | Inspection Report  | A       | SA      | * | SDM =   |
|   | F | pl |                    | SPEN-32 | FETYNET | L | Safer   |
|   | F | ic | -   **Submit       |         | 2000    | 1 | Data    |
|   | - | a- |     original       |         | via SDM | * | Mailbox |
|   | E | ti |     inspection     |         |         |   |         |
|   |   | on |     report**       |         |         |   |         |
|   |   | fi |                    |         |         |   |         |
|   |   | le |                    |         |         |   |         |
|   |   | fo |                    |         |         |   |         |
|   |   | rm |                    |         |         |   |         |
|   |   | at |                    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | A | ap | Snapshot           | CVIEW   | A       | * |         |
|   | F | pl |                    | 3.0     | SPEN-32 | L |         |
|   | F | ic | -   **Fulfill      |         |         | 1 |         |
|   | - | a- |     snapshot       | A       | CVIEW   | * |         |
|   | F | ti |     subscription** | SPEN-32 | 3.0     |   |         |
|   |   | on |                    |         |         |   |         |
|   |   | fi | -   **Query for    | CVIEW   | A       |   |         |
|   |   | le |     snapshot(s)**  | 3.0     | SPEN-32 |   |         |
|   |   | fo |                    |         |         |   |         |
|   |   | rm | -   **Response to  |         |         |   |         |
|   |   | at |     query**        |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | A | ap | Inspection Report  | A       | SAFER   | * |         |
|   | F | pl |                    | SPEN-32 | via     | L |         |
|   | F | ic | -   **Submit       |         | CVIEW   | 1 |         |
|   | - | a- |     original       |         |         | * |         |
|   | G | ti |     inspection     |         |         |   |         |
|   |   | on |     report**       |         |         |   |         |
|   |   | fi |                    |         |         |   |         |
|   |   | le |                    |         |         |   |         |
|   |   | fo |                    |         |         |   |         |
|   |   | rm |                    |         |         |   |         |
|   |   | at |                    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 5  |                    |         |         |   |         |
|   |   | 0, |                    |         |         |   |         |
|   |   | 51 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | A | ap | Inspection Report  | A       | SA      | * | SDM =   |
|   | F | pl |                    | SPEN-32 | FETYNET | L | Safer   |
|   | F | ic | -   **Submit       |         | 2000    | 1 | Data    |
|   | - | a- |     original       |         | via     | * | Mailbox |
|   | H | ti |     inspection     |         | CVIEW & |   |         |
|   |   | on |     report**       |         | SDM     |   |         |
|   |   | fi |                    |         |         |   |         |
|   |   | le |                    |         |         |   |         |
|   |   | fo |                    |         |         |   |         |
|   |   | rm |                    |         |         |   |         |
|   |   | at |                    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 5  |                    |         |         |   |         |
|   |   | 0, |                    |         |         |   |         |
|   |   | 51 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
|   |   |    |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| P | I | In | Equivalent of      | I       | CI      | * | L1 =    |
|   | N | te | Commercial Vehicle | nternet |         | L | IRP &   |
|   | T | rn | (CV) Credentials:  | Tools   | CI      | 1 | IFTA    |
|   | - | et |                    |         |         | ; |         |
|   | A | S  | -   **Submit       | I       | CI      | * | E =     |
|   |   | ta |     initial/re     | nternet |         | E | other   |
|   |   | nd | newal/supplemental | Tools   | CI      |   | cred    |
|   |   | ar |     electronic     |         |         |   | entials |
|   |   | ds |     application    | I       | I       |   |         |
|   |   |    |     for            | nternet | nternet |   | Trip    |
|   |   |    |     credentials**  | Tools   | Tools   |   | p       |
|   |   |    |                    |         |         |   | ermits, |
|   |   |    | -   Submit trip    | I       | I       |   | IFTA    |
|   |   |    |     permit         | nternet | nternet |   | te      |
|   |   |    |     application    | Tools   | Tools   |   | mporary |
|   |   |    |                    |         |         |   | cred    |
|   |   |    | -   **Notify payee | CI      | I       |   | entials |
|   |   |    |     of payment     |         | nternet |   | will    |
|   |   |    |     method**       | CI      | Tools   |   | not be  |
|   |   |    |                    |         |         |   | h       |
|   |   |    | -   **Submit       | CI      | I       |   | andled. |
|   |   |    |     corrected      |         | nternet |   |         |
|   |   |    |     application**  | CI      | Tools   |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Send renewal | CI      | I       |   |         |
|   |   |    |     notice**       |         | nternet |   |         |
|   |   |    |                    | CI      | Tools   |   |         |
|   |   |    | -   **Return       |         |         |   |         |
|   |   |    |     credentials    |         | I       |   |         |
|   |   |    |     data to        |         | nternet |   |         |
|   |   |    |     applicant**    |         | Tools   |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Return       |         |         |   |         |
|   |   |    |     temporary      |         |         |   |         |
|   |   |    |     credential**   |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   Return trip    |         |         |   |         |
|   |   |    |     permit         |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Notify payer |         |         |   |         |
|   |   |    |     of fees due**  |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Reject       |         |         |   |         |
|   |   |    |     application**  |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | I | In | Equivalent of Tax  | I       | CI      | * |         |
|   | N | te | Return:            | nternet |         | L |         |
|   | T | rn |                    | Tools   |         | 1 |         |
|   | - | et | -   **File         |         |         | * |         |
|   | B | S  |     electronic     |         |         |   |         |
|   |   | ta |     IFTA tax       |         |         |   |         |
|   |   | nd |     return**       |         |         |   |         |
|   |   | ar |                    |         |         |   |         |
|   |   | ds |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | I | In | Equivalent of      | CI      | I       | * |         |
|   | N | te | Electronic Filing  |         | nternet | L |         |
|   | T | rn | of Tax Return Data | CI      | Tools   | 1 |         |
|   | - | et | Acknowledgement    |         |         | * |         |
|   | C | S  |                    |         | I       |   |         |
|   |   | ta | -   **Pass IFTA    |         | nternet |   |         |
|   |   | nd |     tax return     |         | Tools   |   |         |
|   |   | ar |     error          |         |         |   |         |
|   |   | ds |     message**      |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   |    | -   **Pass IFTA    |         |         |   |         |
|   |   |    |     tax return     |         |         |   |         |
|   |   |    |     successfully   |         |         |   |         |
|   |   |    |     processed      |         |         |   |         |
|   |   |    |     message**      |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | I | In | Snapshots          | I       | SAFER   | L |         |
|   | N | te |                    | nternet |         | 1 |         |
|   | T | rn | -   **Query for    | Tools   | I       |   |         |
|   | - | et |     snapshot(s)**  |         | nternet |   |         |
|   | D | S  |                    | SAFER   | Tools   |   |         |
|   |   | ta | -   **Response to  |         |         |   |         |
|   |   | nd |     query**        |         |         |   |         |
|   |   | ar |                    |         |         |   |         |
|   |   | ds |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | I | In | Inspection Reports | I       | SAFER   | * | Long    |
|   | N | te |                    | nternet |         | L | term    |
|   | T | rn | -   **Query for    | Tools   | I       | 1 | (reqts  |
|   | - | et |     inspection     |         | nternet | * | level   |
|   | E | S  |     report**       | SAFER   | Tools   |   | E)      |
|   |   | ta |                    |         |         |   |         |
|   |   | nd | ```{=html}         |         |         |   |         |
|   |   | ar | <!-- -->           |         |         |   |         |
|   |   | ds | ```                |         |         |   |         |
|   |   |    | -   **Respond to   |         |         |   |         |
|   |   |    |     inspection     |         |         |   |         |
|   |   |    |     query**        |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | I | In | Tax Rate           | IFTA    | State   | L |         |
|   | N | te | Notification       | Cleari  | IFTA    | 1 |         |
|   | T | rn |                    | nghouse | Tax     |   |         |
|   | - | et | -   **Send latest  |         | Pro     |   |         |
|   | F | S  |     IFTA tax       |         | cessing |   |         |
|   |   | ta |     rates**        |         | System  |   |         |
|   |   | nd |                    |         |         |   |         |
|   |   | ar |                    |         |         |   |         |
|   |   | ds |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
|   |   |    |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | C | cu | **Recaps**         | State   | IRP     | L |         |
|   | I | st |                    | IRP     | Cleari  | 1 |         |
|   | A | om |                    |         | nghouse |   |         |
|   | - | i  |                    |         |         |   |         |
|   | A | nt |                    |         |         |   |         |
|   |   | er |                    |         |         |   |         |
|   |   | fa |                    |         |         |   |         |
|   |   | ce |                    |         |         |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | C | cu | **N                | IRP     | State   | L |         |
|   | I | st | etting/Transmittal | Cleari  | IRP     | 1 |         |
|   | A | om | data**             | nghouse |         |   |         |
|   | - | i  |                    |         |         |   |         |
|   | B | nt |                    |         |         |   |         |
|   |   | er |                    |         |         |   |         |
|   |   | fa |                    |         |         |   |         |
|   |   | ce |                    |         |         |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| ? | C | cu | Snapshots          | SAFER   | ASPEN   | L |         |
|   | I | st |                    |         |         | 1 |         |
|   | A | om | -   Fulfill        | ASPEN   | SAFER   |   |         |
|   | - | i  |     snapshot       |         |         |   |         |
|   | C | nt |     subscription   | SAFER   | ASPEN   |   |         |
|   |   | er |                    |         |         |   |         |
|   |   | fa | -   Query for      |         |         |   |         |
|   |   | ce |     snapshot(s)    |         |         |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr | -   Response to    |         |         |   |         |
|   |   | ee |     query          |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| ? | C | cu | Inspection Reports | ASPEN   | SAFER   | L |         |
|   | I | st |                    |         |         | 1 |         |
|   | A | om | -   Submit         | ASPEN   | SAFER   |   |         |
|   | - | i  |     original       |         |         |   |         |
|   | D | nt |     inspection     | SAFER   | ASPEN   |   |         |
|   |   | er |     report         |         |         |   |         |
|   |   | fa |                    |         |         |   |         |
|   |   | ce | -   Query for      |         |         |   |         |
|   |   | a  |     inspection     |         |         |   |         |
|   |   | gr |     report         |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me | -   Respond to     |         |         |   |         |
|   |   | nt |     inspection     |         |         |   |         |
|   |   |    |     query          |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| ? | C | cu | Inspection Reports | ASPEN   | SA      | L | SDM =   |
|   | I | st |                    |         | FETYNET | 1 | Safer   |
|   | A | om | -   Submit         |         | via SDM |   | Data    |
|   | - | i  |     original       |         |         |   | Mailbox |
|   | E | nt |     inspection     |         |         |   |         |
|   |   | er |     report         |         |         |   |         |
|   |   | fa |                    |         |         |   |         |
|   |   | ce |                    |         |         |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| ? | C | cu | Inspection Reports | ASPEN   | SA      | L |         |
|   | I | st |                    |         | FETYNET | 1 |         |
|   | A | om | -   Submit         |         | via     |   |         |
|   | - | i  |     original       |         | ele     |   |         |
|   | F | nt |     inspection     |         | ctronic |   |         |
|   |   | er |     report         |         | b       |   |         |
|   |   | fa |                    |         | ulletin |   |         |
|   |   | ce |                    |         | board   |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | C | cu | Facsimile request  | SA      | MCMIS   | L | SDM =   |
|   | I | st |                    | FETYNET | via SDM | 1 | Safer   |
|   | A | om | **Facsimile        |         |         |   | Data    |
|   | - | i  | response**         | MCMIS   | SA      |   | Mailbox |
|   | G | nt |                    | via SDM | FETYNET |   |         |
|   |   | er |                    |         |         |   |         |
|   |   | fa |                    |         |         |   |         |
|   |   | ce |                    |         |         |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | C | cu | F-report request   | SA      | MCMIS   | L | SDM =   |
|   | I | st |                    | FETYNET | via SDM | 1 | Safer   |
|   | A | om | **F-report         |         |         |   | Data    |
|   | - | i  | response**         | MCMIS   | SA      |   | Mailbox |
|   | H | nt |                    | via SDM | FETYNET |   |         |
|   |   | er |                    |         |         |   |         |
|   |   | fa |                    |         |         |   |         |
|   |   | ce |                    |         |         |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | C | cu | Snapshot           | Li      | SAFER   | L |         |
|   | I | st |                    | censing |         | 1 |         |
|   | A | om | -   **Update       | &       |         |   |         |
|   | - | i  |     carrier        | In      |         |   |         |
|   | I | nt |     snapshot       | surance |         |   |         |
|   |   | er |     segment**      |         |         |   |         |
|   |   | fa |                    |         |         |   |         |
|   |   | ce |                    |         |         |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| N | C | cu | Driver Status      | CDLIS   | SAFER   | * | In      |
|   | I | st | Report             |         |         | L | terface |
|   | A | om |                    |         |         | 1 | does    |
|   | - | i  |                    |         |         | * | not     |
|   | J | nt |                    |         |         |   | exist   |
|   |   | er |                    |         |         |   | (dial   |
|   |   | fa |                    |         |         |   | in to   |
|   |   | ce |                    |         |         |   | SAFER   |
|   |   | a  |                    |         |         |   | and     |
|   |   | gr |                    |         |         |   | connect |
|   |   | ee |                    |         |         |   | to      |
|   |   | me |                    |         |         |   | CDLIS)  |
|   |   | nt |                    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| N | C | cu | Driver History     | CDLIS   | SAFER   | * |         |
|   | I | st | Report             |         |         | L |         |
|   | A | om |                    |         |         | 1 |         |
|   | - | i  |                    |         |         | * |         |
|   | K | nt |                    |         |         |   |         |
|   |   | er |                    |         |         |   |         |
|   |   | fa |                    |         |         |   |         |
|   |   | ce |                    |         |         |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | C | cu | Snapshot           | MCMIS   | SAFER   | L |         |
|   | I | st |                    |         |         | 1 |         |
|   | A | om | -   **Update       |         |         |   |         |
|   | - | i  |     carrier        |         |         |   |         |
|   | L | nt |     snapshot       |         |         |   |         |
|   |   | er |     segment**      |         |         |   |         |
|   |   | fa |                    |         |         |   |         |
|   |   | ce |                    |         |         |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | C | cu | **Inspection       | MCMIS   | SA      | L | Not     |
|   | I | st | Reports**,         |         | FETYNET | 1 | Com     |
|   | A | om | Compliance         |         |         |   | pliance |
|   | - | i  | Reviews, **Crash   |         |         |   | Reviews |
|   | M | nt | Data, Enforcement  |         |         |   |         |
|   |   | er | Data**             |         |         |   |         |
|   |   | fa |                    |         |         |   |         |
|   |   | ce | -   **Provide past |         |         |   |         |
|   |   | a  |     reports**      |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
| F | C | cu | Inspection         | SA      | MCMIS   | L |         |
|   | I | st | Reports,           | FETYNET |         | 1 |         |
|   | A | om | Compliance         |         |         |   |         |
|   | - | i  | Reviews, Crash     |         |         |   |         |
|   | N | nt | Data, Enforcement  |         |         |   |         |
|   |   | er | Data               |         |         |   |         |
|   |   | fa |                    |         |         |   |         |
|   |   | ce | -   **Provide      |         |         |   |         |
|   |   | a  |     reports**      |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
|   |   |    |                    |         |         |   |         |
|   |   | R  |                    |         |         |   |         |
|   |   | ef |                    |         |         |   |         |
|   |   | 50 |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
|   | C | cu | Sensor data        | Sensor  | Sc      | L |         |
|   | I | st |                    | /Driver | reening | 1 |         |
|   | A | om | Control data       | Comm    |         |   |         |
|   | - | i  |                    |         | Sensor  |   |         |
|   | O | nt |                    | Sc      | /Driver |   |         |
|   |   | er |                    | reening | Comm    |   |         |
|   |   | fa |                    |         |         |   |         |
|   |   | ce |                    |         |         |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
|   | C | cu | Screening          | R       | Sc      | L |         |
|   | I | st | criteria, snapshot | oadside | reening | 1 |         |
|   | A | om | data               | Ope     |         |   |         |
|   | - | i  |                    | rations | R       |   |         |
|   | P | nt | Screening results  |         | oadside |   |         |
|   |   | er |                    | Sc      | Ope     |   |         |
|   |   | fa |                    | reening | rations |   |         |
|   |   | ce |                    |         |         |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
|   | C | cu | Sensor data        | Sensor  | R       | L |         |
|   | I | st |                    | /Driver | oadside | 1 |         |
|   | A | om | Control data       | Comm    | Ope     |   |         |
|   | - | i  |                    |         | rations |   |         |
|   | Q | nt |                    | R       |         |   |         |
|   |   | er |                    | oadside | Sensor  |   |         |
|   |   | fa |                    | Ope     | /Driver |   |         |
|   |   | ce |                    | rations | Comm    |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+
|   | C | cu | Report compliance  | ASAP    | ASAP    | E |         |
|   | I | st | data               | Motor   | A       |   |         |
|   | A | om |                    | Carrier | nalysis |   |         |
|   | - | i  |                    | Data    | Adminis |   |         |
|   | R | nt |                    | Col     | tration |   |         |
|   |   | er |                    | lection |         |   |         |
|   |   | fa |                    |         |         |   |         |
|   |   | ce |                    |         |         |   |         |
|   |   | a  |                    |         |         |   |         |
|   |   | gr |                    |         |         |   |         |
|   |   | ee |                    |         |         |   |         |
|   |   | me |                    |         |         |   |         |
|   |   | nt |                    |         |         |   |         |
+---+---+----+--------------------+---------+---------+---+---------+

NOTE: For CVISN Level 1,

-   The credentials handled by TS 286 include IRP Registration and IFTA
    Registration; future credentials include Single State
    Registration/Unified Carrier Registration, Oversize/Overweight
    Permitting, HazMat Permitting, Vehicle Titling, Intrastate Vehicle
    Registration

-   The snapshots handled by TS 285 include carrier (safety and
    credentials elements), vehicle (safety and credentials elements);
    future snapshots may include driver

-   The safety reports handled by TS 284 include Inspection Results;
    future safety reports include HazMat Incident, Compliance Review,
    and Crash

### Standard Data Definitions

Ideally, there would be a common data dictionary for use throughout all
systems associated with CVISN. That is not practical, since many legacy
systems have different data definitions, and new systems are being
developed by different organizations. Several documents define data
elements that support CVO functions and standards \[References 45, 46,
49, 52, 53, 54\].

The data items listed in this section are common across more than one
interface standard. They are used as "keys" to access information about
the major entities: carrier, vehicle, driver, shipment, and trip. When
systems use common keys, it is possible to match information sets such
as safety and credentials data. The specifications in Table 2-2 define
the key identifier characteristics to be adopted when exchanging
information using the standards. It may be necessary to translate the
identifier from a legacy system into this format when using a standard
to exchange information. In addition to the standard column definitions
explained in section 1.4, this table contains these columns:

-   Entity -- Any person, place, thing, concept, or event that has
    meaning to an enterprise, and about which data can be stored.
    (Example: vehicle)

-   Identifier Name -- the name of the data element that should be
    standard across systems for the entity

```{=html}
<!-- -->
```
-   Identifier Segment -- a list of components that make up the data
    name, including whether the segment should be alphabetic, numeric,
    or alphanumeric

```{=html}
<!-- -->
```
-   Number of Characters -- the maximum length that should be supported
    for each segment

For further information about standard identifiers, see Reference 30.

Table 2‑2. Standard Data Definitions

+----+-------+--------------+----------------+--------+---+---------+
| ** | **Ent | **Identifier | **Identifier   | **     | * | **Com   |
| Co | ity** | Name**       | Segments**     | Number | * | ments** |
| mm |       |              |                | of     | R |         |
| it |       |              |                | Charac | e |         |
| L  |       |              |                | ters** | q |         |
| ev |       |              |                |        | t |         |
| el |       |              |                |        | s |         |
| (  |       |              |                |        | L |         |
| F/ |       |              |                |        | e |         |
| P/ |       |              |                |        | v |         |
| N) |       |              |                |        | e |         |
| ** |       |              |                |        | l |         |
|    |       |              |                |        | * |         |
|    |       |              |                |        | * |         |
+====+=======+==============+================+========+===+=========+
| F  | Motor | Primary      | ID Type        | 3      | L | MD has  |
|    | Ca    | Carrier ID   | (              | (max)  | 1 | adopted |
|    | rrier |              | alphanumeric); |        |   | the     |
|    |       | e.g.,        | if carrier is  | 5      |   | pr      |
|    |       |              | interstate,    | (ISO   |   | incipal |
|    |       | For          | must be USDOT  | -3166) |   | of      |
|    |       | ***i         | type code +    |        |   | using   |
|    |       | nterstate*** |                | 12     |   | USDOT   |
|    |       | carrier:     | Jurisdiction   | (max)  |   | numbers |
|    |       |              | Code, if       |        |   | for all |
|    |       | MCI 12345    | carrier is     | 4      |   | heavy   |
|    |       | A001 (note   | intrastate     | (max)  |   | ve      |
|    |       | that MCI is  | (alphanumeric) |        |   | hicles, |
|    |       | the code     | +              |        |   | int     |
|    |       | used for ID  |                |        |   | rastate |
|    |       | Type USDOT   | Ca             |        |   | as well |
|    |       | \# )         | rrier-Specific |        |   | as      |
|    |       |              | Identifier     |        |   | inte    |
|    |       | e.g.,        | corresponding  |        |   | rstate. |
|    |       |              | to the ID type |        |   | Systems |
|    |       | For          | (              |        |   | are not |
|    |       | ***i         | alphanumeric); |        |   | yet     |
|    |       | ntrastate*** | if carrier is  |        |   | av      |
|    |       | carrier in a | interstate,    |        |   | ailable |
|    |       | state using  | must be USDOT  |        |   | to      |
|    |       | FEIN as the  | number +       |        |   | allow   |
|    |       | Primary      |                |        |   | int     |
|    |       | Carrier ID   | Carrier        |        |   | rastate |
|    |       | for          | terminal ID    |        |   | heavy   |
|    |       | intrastate   | designated by  |        |   | vehicle |
|    |       | carriers:    | carrier        |        |   | owners  |
|    |       |              | (alphanumeric) |        |   | to      |
|    |       | TJ US-CA     |                |        |   | r       |
|    |       | 123456789    |                |        |   | egister |
|    |       | (note that   |                |        |   | easily  |
|    |       | TJ is the    |                |        |   | for US  |
|    |       | code used    |                |        |   | DOT     |
|    |       | for ID Type  |                |        |   | n       |
|    |       | FEIN)        |                |        |   | umbers. |
|    |       |              |                |        |   | MD will |
|    |       |              |                |        |   | adopt   |
|    |       |              |                |        |   | this    |
|    |       |              |                |        |   | a       |
|    |       |              |                |        |   | pproach |
|    |       |              |                |        |   | when it |
|    |       |              |                |        |   | is      |
|    |       |              |                |        |   | tech    |
|    |       |              |                |        |   | nically |
|    |       |              |                |        |   | fe      |
|    |       |              |                |        |   | asible. |
|    |       |              |                |        |   |         |
|    |       |              |                |        |   | For     |
|    |       |              |                |        |   | ide     |
|    |       |              |                |        |   | ntifier |
|    |       |              |                |        |   | cro     |
|    |       |              |                |        |   | ss-refe |
|    |       |              |                |        |   | rencing |
|    |       |              |                |        |   | esp     |
|    |       |              |                |        |   | ecially |
|    |       |              |                |        |   | between |
|    |       |              |                |        |   | IRP and |
|    |       |              |                |        |   | IFTA    |
|    |       |              |                |        |   | s       |
|    |       |              |                |        |   | ystems, |
|    |       |              |                |        |   | adminis |
|    |       |              |                |        |   | trative |
|    |       |              |                |        |   | and     |
|    |       |              |                |        |   | te      |
|    |       |              |                |        |   | chnical |
|    |       |              |                |        |   | steps   |
|    |       |              |                |        |   | are     |
|    |       |              |                |        |   | being   |
|    |       |              |                |        |   | taken   |
|    |       |              |                |        |   | to      |
|    |       |              |                |        |   | capture |
|    |       |              |                |        |   | the     |
|    |       |              |                |        |   | FEIN    |
|    |       |              |                |        |   | for all |
|    |       |              |                |        |   | int     |
|    |       |              |                |        |   | erstate |
|    |       |              |                |        |   | ve      |
|    |       |              |                |        |   | hicles. |
+----+-------+--------------+----------------+--------+---+---------+
| F  | Ve    | Vehicle      | VIN assigned   | 30     | L |         |
|    | hicle | Id           | by             | (max)  | 1 |         |
|    |       | entification | manufacturer   |        |   |         |
|    |       | Number       | (alphanumeric) | 2      |   |         |
|    |       |              |                | (using |   |         |
|    |       | e.g.,        | Country code + | c      |   |         |
|    |       | 1FDKE        |                | ountry |   |         |
|    |       | 30F8SHB33184 | Jurisdiction   | code   |   |         |
|    |       |              | (state or      | from   |   |         |
|    |       | and          | province) code | ISO    |   |         |
|    |       |              | (alphanumeric) | -3166) |   |         |
|    |       | Vehicle      | +              |        |   |         |
|    |       | Plate ID     |                | 2      |   |         |
|    |       |              | License plate  | (using |   |         |
|    |       | e.g., US CA  | ID             | subdi  |   |         |
|    |       | 12345664820M | (alphanumeric) | vision |   |         |
|    |       |              |                | code   |   |         |
|    |       |              |                | from   |   |         |
|    |       |              |                | ISO    |   |         |
|    |       |              |                | -3166) |   |         |
|    |       |              |                |        |   |         |
|    |       |              |                | 12     |   |         |
|    |       |              |                | (max)  |   |         |
+----+-------+--------------+----------------+--------+---+---------+
| F  | T     | Transponder  | Transponder ID | 1 bit  | L |         |
|    | ransp | ID           | Definition     |        | 1 |         |
|    | onder |              | Flag           | 32-bit |   |         |
|    |       | e.g., 0      | (0=current;    | un     | E |         |
|    |       | 123456789    | 1=IEEE P1455)  | signed |   |         |
|    |       |              | +              | i      |   |         |
|    |       |              |                | nteger |   |         |
|    |       |              | *If            |        |   |         |
|    |       |              | Transponder ID | 16     |   |         |
|    |       |              | Definition     | bits   |   |         |
|    |       |              | Flag =         |        |   |         |
|    |       |              | current*, then | 20     |   |         |
|    |       |              | the other      | bits   |   |         |
|    |       |              | segment is:    |        |   |         |
|    |       |              |                |        |   |         |
|    |       |              | Transponder    |        |   |         |
|    |       |              | Serial Number  |        |   |         |
|    |       |              | assigned by    |        |   |         |
|    |       |              | manufacturer   |        |   |         |
|    |       |              |                |        |   |         |
|    |       |              | *If            |        |   |         |
|    |       |              | Transponder ID |        |   |         |
|    |       |              | Definition     |        |   |         |
|    |       |              | Flag = IEEE    |        |   |         |
|    |       |              | P1455*, then   |        |   |         |
|    |       |              | the other      |        |   |         |
|    |       |              | segments are:  |        |   |         |
|    |       |              |                |        |   |         |
|    |       |              | Manufacturer   |        |   |         |
|    |       |              | Identifier +   |        |   |         |
|    |       |              |                |        |   |         |
|    |       |              | Transponder    |        |   |         |
|    |       |              | Serial Number  |        |   |         |
|    |       |              | assigned by    |        |   |         |
|    |       |              | manufacturer   |        |   |         |
+----+-------+--------------+----------------+--------+---+---------+
| F  | D     | Driver       | Country code + | 2      | L |         |
|    | river | Unique ID    |                | (using | 1 |         |
|    |       |              | Jurisdiction   | c      |   |         |
|    |       | e.g.,        | (state or      | ountry |   |         |
|    |       |              | province) code | code   |   |         |
|    |       | US MD        | (alphanumeric) | from   |   |         |
|    |       | B            | +              | ISO    |   |         |
|    |       | 99999999999A |                | -3166) |   |         |
|    |       |              | Driver         |        |   |         |
|    |       |              | specific       | 2      |   |         |
|    |       |              | identifier     | (using |   |         |
|    |       |              | (driver        | subdi  |   |         |
|    |       |              | license        | vision |   |         |
|    |       |              | number)        | code   |   |         |
|    |       |              | assigned by    | from   |   |         |
|    |       |              | jurisdiction   | ISO    |   |         |
|    |       |              | (alphanumeric) | -3166) |   |         |
|    |       |              |                |        |   |         |
|    |       |              |                | 16     |   |         |
|    |       |              |                | (max)  |   |         |
+----+-------+--------------+----------------+--------+---+---------+
| F  | Shi   | Shipment     | Bill of Lading | 12     | C |         |
|    | pment | Unique ID    | number         | (max)  |   |         |
|    |       |              | assigned by    |        |   |         |
|    |       | e.g.,        | the carrier    |        |   |         |
|    |       | 776655443322 | (numeric)      |        |   |         |
+----+-------+--------------+----------------+--------+---+---------+
| F  | Trip  | Trip/Load    | Carrier DUNS   | 9      | E |         |
|    |       | Number       | number as      |        |   |         |
|    |       |              | assigned by    | 6      |   |         |
|    |       | e.g.,        | Dun and        |        |   |         |
|    |       | 123          | Bradstreet     |        |   |         |
|    |       | 456789761231 | (numeric) +    |        |   |         |
|    |       |              |                |        |   |         |
|    |       |              | Trip unique    |        |   |         |
|    |       |              | number as      |        |   |         |
|    |       |              | assigned by    |        |   |         |
|    |       |              | carrier        |        |   |         |
|    |       |              | (numeric)      |        |   |         |
+----+-------+--------------+----------------+--------+---+---------+
|    |       |              |                |        |   |         |
+----+-------+--------------+----------------+--------+---+---------+

Note that jurisdiction refers to a five-character code (XX-XX) for
either country and state, or for country and province; or else to a
two-character code for state or province (depending on context).

## Other Maryland Requirements

Additional specific Maryland requirements for credentialing
administration can be found in the State of Maryland Credentials
Administration Requirements Specifications (CARS) and the MD Commercial
Vehicle Credentialing Top-Level Requirements, References 26 and 38,
respectively.

This Page Intentionally Blank