**Intelligent Transportation Systems (ITS)**

**Commercial Vehicle Operations (CVO)**

Commercial Vehicle Information Systems and\
Networks (CVISN) Architecture

**POR-02-7364 V2.0**

**March 2004**

*Prepared for:*

![](media/image1.png){width="1.45625in" height="0.7284722222222222in"}

*US Department of Transportation*

*Federal Motor Carrier Safety Administration*

*400 Seventh Street, SW*

*Washington, DC 20590*

*Prepared by:*

![](media/image2.wmf){width="0.5833333333333334in"
height="0.7555555555555555in"}

*The Johns Hopkins University*

*Applied Physics Laboratory*

*11100 Johns Hopkins Road*

*Laurel, MD 20723-6099*

> > *The Motor Carrier Safety Improvement Act was signed into law on
> > December 9, 1999. This act established a new Federal Motor Carrier
> > Safety Administration (FMCSA) within the US Department of
> > Transportation (DOT), effective January 1, 2000. Prior to that, the
> > motor carrier and highway safety program was administered under the
> > Federal Highway Administration (FHWA).*
>
> > *The mission of the FMCSA is to improve truck and commercial
> > passenger carrier safety on our nation's highways through
> > information technology, targeted enforcement, research and
> > technology, outreach, and partnerships. The FMCSA manages the
> > Intelligent Transportation Systems (ITS)/Commercial Vehicle
> > Operations (CVO) Program, a voluntary effort involving public and
> > private partnerships that uses information systems, innovative
> > technologies, and business practice reengineering to improve safety,
> > simplify government administrative systems, and provide savings to
> > states and motor carriers. The FMCSA works closely with the FHWA's
> > ITS Joint Program Office (JPO) to ensure the integration and
> > interoperability of ITS/CVO systems with the national ITS program.*

As part of the CVISN program, FMCSA defined an initial set of
capabilities that could be deployed incrementally by a state and its
motor carriers. The capabilities focus on electronically exchanging
safety and credentialing information, electronically processing
interstate registration and fuel tax credentials, and implementing
roadside electronic screening at one fixed or mobile site. These
capabilities were originally referred to as "CVISN Level 1"
capabilities, but are now called "Core" CVISN capabilities.

**This is Version 2 of a Baseline Issue**

This document has completed internal and external reviews of previously
published draft versions. All comments received to date have been
incorporated or addressed.

This document is disseminated in the interest of information exchange.
The Johns Hopkins University Applied Physics Laboratory (JHU/APL)
assumes no liability for its contents or use thereof. This report does
not constitute a standard, specification, or regulation. JHU/APL does
not endorse products or manufacturers. Trade and manufacturer's names
appear in this report only because they are considered essential to the
object of this document.

**Note:** This document and other CVISN-related documentation are
available for review and downloading by the ITS/CVO community from the
JHU/APL CVISN site on the World Wide Web. The URL for the CVISN site is:
<http://www.jhuapl.edu/cvisn/>.

Review and comments to this document are welcome. Please send comments
to:

> Ms. Valerie Barnes
>
> JHU/APL
>
> Phone: 717-261-0635
>
> Fax: 717-261-0635
>
> E-Mail: Valerie.Barnes@jhuapl.edu

**CVISN Architecture**

**Table of Contents**

[1. CVISN ARCHITECTURE 1--1](#cvisn-architecture)

[1.1. Background 1--1](#background)

[1.2. Scope 1--1](#scope)

[1.3. Maintaining the CVISN Architecture
1--1](#maintaining-the-cvisn-architecture)

[2. CVISN ARCHITECTURE 2--1](#cvisn-architecture-1)

[2.1. Architecture Conventions 2--1](#architecture-conventions)

[2.2. Architecture Flow Diagram 2--2](#architecture-flow-diagram)

[2.3. Tables 2--5](#tables)

[3. CHANGE REQUESTS 3--1](#change-requests)

[3.1. Change Requests Incorporated 3--1](#change-requests-incorporated)

[3.2. Change Requests Pending 3--2](#change-requests-pending)

[4. REFERENCES 4--1](#references)

This Page Intentionally Blank

# CVISN ARCHITECTURE

## Background

This document establishes a new baseline for the CVISN Architecture. The
CVISN Architecture baseline was aligned with the National Intelligent
Transportation Systems (ITS) and International Border Clearance (IBC)
Architectures in 2001-2002 \[References 1 -- 3\]. This version of the
CVISN Architecture has been updated to align with Version 5.0 of the
National ITS Architecture \[Reference 4\]. The CVISN Architecture uses
terminology and components that the National ITS Architecture uses.

## Scope

CVISN represents a subset of the National ITS Architecture
\<<http://www.iteris.com/itsarch/>\> \[Reference 4\]. CVISN comprises
the information systems and networks that support commercial vehicle
operations.

A diagram that depicts subsystems, equipment packages, architecture
flows, and terminators represents the CVISN Architecture
\[Figure 2--1\]. Tables in this document provide additional information
about each item shown on the diagram. The architecture reflects the
vision for CVISN over the next few years.

## Maintaining the CVISN Architecture

The CVISN Architecture is under configuration management. There is a
three-tier process for proposing a change to the architecture. First,
the proposed change will be presented to and reviewed by the CVISN
Architecture Configuration Control Board (ACCB). The ACCB is made up of
FMCSA and state representatives, and is staffed by JHU/APL. Change
Requests (CR) are reviewed in regular (monthly) meetings. Once the ACCB
has reached consensus about a proposed change that may also impact the
National ITS Architecture, the CR recommended for approval will be
discussed with the National ITS Architecture team. If the National ITS
Architecture team concurs, in the final stage of the process, the
proposed change will be presented to FMCSA for consideration. If FMCSA
approves the proposed change, it will be implemented in CVISN. At the
next release, it will be implemented in the National ITS Architecture.

If a new user service requires that CVO-related functions be added to
the National ITS Architecture, then existing components may need to be
changed or other components added. The CVISN Architecture team will work
with the National ITS Architecture team to develop the proposed changes
to the architecture, and then go through the CR process with the CVISN
ACCB.

Chapter 3 explains the change requests that are incorporated in this
version of the CVISN Architecture. In Chapter 2, impacted rows are
flagged with the change request number (CR #).

This Page Intentionally Blank

# CVISN ARCHITECTURE

The CVISN Architecture reflects alignment with the National ITS
Architecture using these ground rules:

-   The elements of the physical architecture (subsystems, terminators
    and architecture flows) are aligned. The logical architectures were
    not aligned as part of this process.

-   The scope is limited to CVISN Level 1 functions plus toll,
    international border crossing, other safety functions, and
    Commercial Vehicle Operations (CVO) security. This particular
    version of the CVISN Architecture document reflects the alignment
    with Version 5.0 of the National ITS Architecture. Major changes
    were made to include security functions.

-   Human terminators, except the Commercial Vehicle (CV) Driver, are
    not part of the alignment.

## Architecture Conventions

The CVISN Architecture follows these conventions for naming, styles,
etc.:

1.  The National ITS Architecture naming conventions are used by CVISN
    for aligned architecture flows: flow names are lower case except for
    acronyms.

2.  The National ITS Architecture definitions for aligned subsystems,
    equipment packages, terminators, and architecture flows are used by
    CVISN.

3.  For the alignment process, basic vehicle (Vehicle Subsystem)
    functions were incorporated into the CV realm. The CVISN
    Architecture aggregates the National ITS Architecture's Commercial
    Vehicle and Vehicle Subsystems into a single subsystem named CVSAg.
    In this document we indicate which data are related to the Vehicle
    Subsystem by labeling the aggregated subsystem as CVSAg (VS). If a
    flow is related to the Commercial Vehicle Subsystem, the aggregated
    subsystem is labeled CVSAg (CVS).

4.  Architecture flows are characterized as to whether or not there are
    applicable standards. The four line types used on the flow diagram
    are as follows:

    a.  Wireline (Fixed Point Communications) -- shown as a solid line

    b.  Dedicated Short Range Communication (DSRC) -- shown as a long
        dashed line

    c.  Wide Area Wireless -- shown as a long-short-long dashed line

    d.  Other Transactions -- shown as a dotted line

With the exception of (d), the architecture flow types used by CVISN
match those defined by the National ITS Architecture. These are
designated as "architecture interconnects" by the National ITS
Architecture.

5.  Some architecture flows between humans and subsystems remain in the
    National ITS Architecture but are not shown in the CVISN
    Architecture; the human operator is considered to be part of the
    subsystem in CVISN. The one exception is the Commercial Vehicle
    Driver.

## Architecture Flow Diagram

Figure 2--1 is the CVISN Architecture Flow Diagram. The CVISN
Architecture Flow Diagram depicts the CVO data flow among subsystems and
between CVO subsystems and external entities. The subsystems and
equipment packages shown relate to the processes defined in the National
ITS Architecture's Physical Architecture. The shaded equipment packages
are not part of CVISN Level 1. In this version of this document,
descriptions for all equipment packages shown on the diagram were added
as a new table, Table 4.

Entities external to the ITS information systems are shown in ovals. In
National Architecture terminology, these are "terminators."

Connections and data exchanges shown on the figures are marked with
different line types to differentiate the means of communication used.
The definitions provided below are from the National ITS Architecture
\[Reference 4\].

-   Wireline (Fixed Point Communications): A communication link serving
    stationary entities. It may be implemented using a variety of public
    or private communication networks and technologies. It can include,
    but is not limited to, twisted pair, coaxial cable, fiber optic,
    microwave relay networks, spread spectrum, etc. In Fixed-Point to
    Fixed-Point (FP2FP) communication the important issue is that it
    serves stationary entities. Both dedicated and shared communication
    resources may be used.

-   DSRC: A wireless communications channel used for close-proximity
    communications between vehicles and the immediate infrastructure. It
    supports location-specific communications for ITS capabilities such
    as toll collection, transit vehicle management, driver information,
    and automated commercial vehicle operations.

-   Wide Area Wireless: A communications link that provides
    communications via a wireless device between a user and an
    infrastructure-based system. Both broadcast (one-way) and
    interactive (two-way) communications services are grouped into
    wide-area wireless communications in the National ITS Architecture.
    These links support a range of services in the National ITS
    Architecture including real-time traveler information and various
    forms of fleet communications.

-   Other Transactions: Any of the following National ITS Architecture's
    architecture interconnects -- Physical Interface, Human, Internal
    Vehicle Interface, Contact or Proximity Interface, or Position
    Location Interface.

Symbols for the Emergency Management Subsystem and the Freight Equipment
terminator contain the text string "(2)", indicating that each symbol
appears twice on the diagram. This was done to maintain a semblance of
readability and has nothing to do with functionality.

**Replace this page with 11x17 foldout**

Figure 2--1. CVISN Architecture Flow Diagram

**Replace this page with 11x17 foldout**

## Tables

In the discussion of the tables, a "flow" is comprised of the source,
destination and architecture flow name. "Flow name" is a label for a set
of data elements. A list of the acronyms and abbreviations used in the
tables is given just prior to Table 1.

The tables provided are:

> [Table 1](#table6). CVISN Architecture Flows
>
> [Table 2](#Table2). CVISN Architecture Flow Names and Descriptions
>
> [Table 3](#Table3). Subsystem and Terminator Descriptions
>
> [Table 4](#table4). Equipment Package Descriptions

**ACRONYMS AND ABBREVIATIONS:**

AAS: Alerting and Advisory Systems

ADMS: Archived Data Management Subsystem

BCV: Basic Commercial Vehicle

CV: Commercial Vehicle

CVAS: Commercial Vehicle Administration Subsystem

CVCS: Commercial Vehicle Check Subsystem

CV Driver: Commercial Vehicle Driver

CVOIR: Commercial Vehicle Operations Information Requestor

CVS: Commercial Vehicle Subsystem

CVSAg: Commercial Vehicle Subsystem Aggregated with the Vehicle
Subsystem (this term is used only by CVISN)

CVSAg (CVS): Associated with the CVS part of CVSAg

CVSAg (VS): Associated with the VS part of CVSAg

EA: (Law) Enforcement Agency

EM: Emergency Management Subsystem

EVS: Emergency Vehicle Subsystem

FE: Freight Equipment

FI: Financial Institution

FMS: Fleet and Freight Management Subsystem

IFD: Intermodal Freight Depot

IFS: Intermodal Freight Shipper

ISP: Information Service Provider Subsystem

LDS: Location Data Source

MCMS: Maintenance and Construction Management Subsystem

MUP: Map Update Provider

PMS: Parking Management Subsystem

RS: Roadway Subsystem

TAS: Toll Administration Subsystem

TC: Traveler Card

TCS: Toll Collection Subsystem

TRA: Trade Regulatory Agencies

VS: Vehicle Subsystem

**Table 1** presents a detailed look at each architecture flow contained
in the CVISN Architecture Flow Diagram \[Figure 2--1\].

This table is ordered alphabetically by source and destination. An "X"
in the Std. column indicates that there are standards that apply to the
architecture flow; refer to Version 5.0 of the National ITS Architecture
for the applicable standards \[Reference 4\]. In Version 5.0 of the
National ITS Architecture, many architecture flows are identified as
candidates for future standardization; those are marked as "future" in
the Std. column and CR 2390 applies. The CR \# column indicates any
other applicable Change Requests for the flow. If CR 2390 is listed,
then the architecture flow was added via that change request.

Table 1. CVISN Architecture Flows

  ------------------------------------------------------------------------------------------
  CVISN                                                                          
  Architecture                                                                   
  Flows                                                                          
  -------------- ----------------- ---------------------------------- ---------- -----------
  **Source**     **Destination**   **Flow Name**                      **Std.**   **CR \#**

  AAS            FMS               alerts and advisories              future     CR 2390

  ADMS           CVAS              archive requests                   future     

  ADMS           CVAS              archive status                     future     

  BCV            CVCS              CVO weight and presence                       

  BCV            CVCS              identification information                    

  BCV            CVSAg (CVS)       commercial vehicle measures        future     

  CVAS           ADMS              commercial vehicle archive data    X          

  CVAS           CVCS              border agency clearance results    future     

  CVAS           CVCS              credentials information            X          

  CVAS           CVCS              credentials status information     X          

  CVAS           CVCS              transportation border clearance    future     
                                   assessment                                    

  CVAS           CVCS              trip declaration identifiers       future     

  CVAS           CVCS              safety inspection report           X          

  CVAS           CVCS              safety status information          X          

  CVAS           CVOIR             credentials information            X          

  CVAS           CVOIR             credentials status information     X          

  CVAS           CVOIR             safety status information          X          

  CVAS           EA                accident report                    future     

  CVAS           EA                citation                           future     

  CVAS           EA                violation notification             future     

  CVAS           FI                payment request                               

  CVAS           FMS               accident report                    future     

  CVAS           FMS               border clearance status            future     

  CVAS           FMS               citation                           future     

  CVAS           FMS               compliance review report           future     

  CVAS           FMS               credentials information            X          

  CVAS           FMS               credentials status information     X          

  CVAS           FMS               route restrictions                 future     CR 2390

  CVAS           FMS               safety inspection report           X          

  CVAS           FMS               safety status information          X          

  CVAS           IFS               border clearance status            future     

  CVAS           ISP               route restrictions                 future     CR 2390

  CVAS           MUP               route restrictions                 future     CR 2390

  CVAS           Other CVAS        border clearance status            future     

  CVAS           Other CVAS        credential fee coordination        future     

  CVAS           Other CVAS        credentials information            X          

  CVAS           Other CVAS        credentials status information     X          

  CVAS           Other CVAS        route restrictions                 future     CR 2390

  CVAS           Other CVAS        safety inspection report           X          

  CVAS           Other CVAS        safety status information          X          

  CVAS           TRA               border clearance status            future     

  CVAS           TRA               domestic transportation            future     
                                   information                                   

  CVAS           TRA               transportation border clearance    future     
                                   assessment                                    

  CVCS           CVAS              accident report                    future     

  CVCS           CVAS              citation                           future     

  CVCS           CVAS              daily site activity data           future     

  CVCS           CVAS              border clearance event             future     

  CVCS           CVAS              safety inspection report           X          

  CVCS           CVAS              violation notification             future     

  CVCS           CV Driver         CVO pass/pull-in message                      

  CVCS           CVSAg (CVS)       border clearance data request      X          

  CVCS           CVSAg (CVS)       border clearance event             X          

  CVCS           CVSAg (CVS)       driver log request                 future     []{.mark}

  CVCS           CVSAg (CVS)       electronic lock data request       X          

  CVCS           CVSAg (CVS)       electronic screening request       X          

  CVCS           CVSAg (CVS)       on-board safety request            X          

  CVCS           CVSAg (CVS)       pass/pull-in                       X          

  CVCS           CVSAg (CVS)       request tag data                   future     

  CVCS           CVSAg (CVS)       safety inspection record           future     

  CVCS           CVSAg (CVS)       safety inspection request          future     

  CVCS           CVSAg (CVS)       screening event record             X          

  CVCS           EM                alarm                              future     CR 2390

  CV Driver      CVSAg (CVS)       alert response                                CR 2390

  CV Driver      CVSAg (CVS)       CVO driver initialization                     

  CV Driver      CVSAg (CVS)       driver identity characteristics               CR 2390

  CV Driver      CVSAg (CVS)       trip identification number                    

  CVSAg (CVS)    BCV               safe vehicle disable               future     CR 2390

  CVSAg (CVS)    CVCS              border clearance data              X          

  CVSAg (CVS)    CVCS              commercial vehicle breach          future     CR 2390

  CVSAg (CVS)    CVCS              driver log                         future     

  CVSAg (CVS)    CVCS              electronic lock data               X          

  CVSAg (CVS)    CVCS              on-board safety data               X          

  CVSAg (CVS)    CVCS              safety inspection record           future     

  CVSAg (CVS)    CVCS              screening event record             X          

  CVSAg (CVS)    CVCS              tag data                           future     []{.mark}

  CVSAg (CVS)    CV Driver         alerts                                        

  CVSAg (CVS)    CV Driver         CVO pass/pull-in message                      

  CVSAg (CVS)    CV Driver         trip log information                          

  CVSAg (CVS)    EM                hazmat spill notification          future     

  CVSAg (CVS)    FMS               commercial vehicle breach          future     CR 2390

  CVSAg (CVS)    FMS               driver alert response              future     CR 2390

  CVSAg (CVS)    FMS               driver to fleet request            future     

  CVSAg (CVS)    FMS               freight equipment information      future     CR 2390

  CVSAg (CVS)    FMS               identities                         future     CR 2390

  CVSAg (CVS)    FMS               on-board safety data               X          CR 439

  CVSAg (CVS)    FMS               on-board vehicle data              future     CR 439

  CVSAg (CVS)    FMS               route deviation alert              future     CR 2390

  CVSAg (CVS)    FMS               trip log                           future     CR 439

  CVSAg (VS)     EM                emergency notification             X          

  CVSAg (VS)     EVS               vehicle location                              CR 2390

  CVSAg (VS)     ISP               vehicle probe data                 future     

  CVSAg (VS)     PMS               tag data                           X          

  CVSAg (VS)     RS                vehicle probe data                 X          

  CVSAg (VS)     TC                request for payment                           

  CVSAg (VS)     TCS               tag data                           X          

  EA             CVAS              information on violators           future     

  EA             CVCS              information on violators           future     

  EM             CVSAg (VS)        emergency acknowledge              X          

  EM             CVSAg (VS)        emergency data request             X          

  EM             FMS               disable commercial vehicle         future     CR 2390

  EM             FMS               hazmat information request         X          []{.mark}

  FE             CVCS              freight breach                     future     CR 2390

  FE             CVCS              freight equipment information      future     CR 2390

  FE             CVCS              hazmat environmental factors                  CR 2390

  FE             CVSAg (CVS)       freight breach                     future     CR 2390

  FE             CVSAg (CVS)       freight equipment information      future     CR 2390

  FE             FMS               freight breach                     future     CR 2390

  FE             FMS               freight equipment information      future     CR 2390

  FI             CVAS              transaction status                            

  FI             ISP               transaction status                            

  FI             PMS               transaction status                            

  FI             TAS               transaction status                            

  FMS            AAS               fleet and freight threat           future     CR 2390
                                   information                                   

  FMS            CVAS              audit data                         future     

  FMS            CVAS              credential application             X          

  FMS            CVAS              tax filing                         X          CR 654

  FMS            CVSAg (CVS)       commercial vehicle disable         future     CR 2390

  FMS            CVSAg (CVS)       expected driver identity           future     CR 2390
                                   characteristics                               

  FMS            CVSAg (CVS)       fleet to driver update             future     

  FMS            CVSAg (CVS)       on-board safety request            X          CR 439

  FMS            CVSAg (CVS)       on-board vehicle request           future     CR 439

  FMS            CVSAg (CVS)       trip identification number         future     CR 439

  FMS            CVSAg (CVS)       trip log request                   future     CR 439

  FMS            EM                alarm                              future     CR 2390

  FMS            EM                hazmat information                 X          

  FMS            FE                freight monitoring parameters      future     CR 2390

  FMS            IFD               booking status                     future     CR 2390

  FMS            IFD               intermod CVO coord                 future     

  FMS            IFS               booking status                     future     CR 2390

  FMS            IFS               freight breach                     future     CR 2390

  FMS            IFS               intermod CVO coord                 future     

  FMS            ISP               route request                      X          

  FMS            ISP               toll data request                  future     

  FMS            MUP               map update request                            CR 2390

  FMS            TAS               toll data request                  future     

  IFD            FMS               intermod CVO coord                 future     

  IFS            CVSAg (CVS)       trip identification number         future     

  IFS            FMS               breach response                    future     CR 2390

  IFS            FMS               freight transport booking          future     CR 2390

  IFS            FMS               intermod CVO coord                 future     

  ISP            FI                payment request                               

  ISP            FMS               road network conditions            X          []{.mark}

  ISP            FMS               route plan                         X          

  ISP            FMS               toll data                          future     

  ISP            TAS               toll data request                  future     

  LDS            CVSAg (VS)        position fix                                  

  MCMS           CVAS              current asset restrictions         future     []{.mark}

  MUP            FMS               map updates                                   CR 2390

  Other CVAS     CVAS              border clearance status            future     

  Other CVAS     CVAS              credential fee coordination        future     

  Other CVAS     CVAS              credentials information            X          

  Other CVAS     CVAS              credentials status information     X          

  Other CVAS     CVAS              route restrictions                 future     CR 2390

  Other CVAS     CVAS              safety inspection report           X          

  Other CVAS     CVAS              safety status information          X          

  PMS            CVSAg (VS)        request tag data                   X          

  PMS            CVSAg (VS)        tag update                         X          

  PMS            FI                payment request                               

  RS             CVSAg (VS)        request tag data                   X          

  RS             CVSAg (VS)        vehicle signage data               X          

  TAS            FI                payment request                               

  TAS            FMS               toll data                          future     

  TAS            ISP               toll data                          future     

  TC             CVSAg (VS)        payment                                       

  TCS            CVSAg (VS)        request tag data                   X          

  TCS            CVSAg (VS)        tag update                         X          

  TRA            CVAS              declaration information            future     

  TRA            CVAS              domestic transportation            future     
                                   information                                   
  ------------------------------------------------------------------------------------------

[]{#Table2 .anchor}**Table 2** defines the architecture flow names.
Unless otherwise indicated, all flow definitions are from the National
ITS Architecture Version 5.0 \[Reference 4\].

Table 2. CVISN Architecture Flow Names and Descriptions

+--------------+------------------------------------------------+-----+
| CVISN        |                                                |     |
| Architecture |                                                |     |
| Flow Names   |                                                |     |
| and          |                                                |     |
| Descriptions |                                                |     |
+==============+================================================+=====+
| **Flow       | **Flow Description**                           | *   |
| Name**       |                                                | *CR |
|              |                                                | \   |
|              |                                                | #** |
+--------------+------------------------------------------------+-----+
| accident     | Report of commercial vehicle safety accident.  |     |
| report       | The information may be provided as a response  |     |
|              | to a real-time query or proactively by the     |     |
|              | source. The query flow is not explicitly       |     |
|              | shown.                                         |     |
+--------------+------------------------------------------------+-----+
| alarm        | Information about a Commercial Vehicle or      | CR  |
|              | Freight Equipment breach, non-permitted        | 2   |
|              | security sensitive hazmat detected at the      | 390 |
|              | roadside, route deviation, or Commercial       |     |
|              | Vehicle Driver / Commercial Vehicle / Freight  |     |
|              | Equipment assignment mismatches which includes |     |
|              | the location of the Commercial Vehicle and     |     |
|              | appropriate identities.                        |     |
+--------------+------------------------------------------------+-----+
| alert        | This flow represents the tactile or auditory   | CR  |
| response     | interface with ITS equipment containing the    | 2   |
|              | response by a Commercial Vehicle Driver or     | 390 |
|              | Fleet-Freight Manager that confirms or cancels |     |
|              | an alert.                                      |     |
+--------------+------------------------------------------------+-----+
| alerts       | This flow represents the visual or auditory    | CR  |
|              | interface with ITS equipment containing        | 2   |
|              | specific alerts and messages related to        | 390 |
|              | commercial vehicles (e.g. trucks not advised,  |     |
|              | trucks over 10 tons not allowed on bridge,     |     |
|              | route details). This also includes detected    |     |
|              | route deviations and warning indications       |     |
|              | detected by on-board sensors (e.g., safety)    |     |
|              | and freight equipment sensors (e.g., breach,   |     |
|              | cargo).                                        |     |
+--------------+------------------------------------------------+-----+
| alerts and   | Assessments (general incident and              | CR  |
| advisories   | vulnerability awareness information),          | 2   |
|              | advisories (identification of threats or       | 390 |
|              | recommendations to increase preparedness       |     |
|              | levels), and alerts (information on imminent   |     |
|              | or in-progress emergencies). This flow also    |     |
|              | provides supporting descriptive detail on      |     |
|              | incidents, threats, and vulnerabilities to     |     |
|              | increase preparedness and support effective    |     |
|              | response to threats against the surface        |     |
|              | transportation system.                         |     |
+--------------+------------------------------------------------+-----+
| archive      | A request to a data source for information on  |     |
| requests     | available data (i.e., \"catalog\") or a        |     |
|              | request that defines the data to be archived.  |     |
|              | The request can be a general subscription      |     |
|              | intended to initiate a continuous or regular   |     |
|              | data stream or a specific request intended to  |     |
|              | initiate a one-time response from the          |     |
|              | recipient.                                     |     |
+--------------+------------------------------------------------+-----+
| archive      | Notification that data provided to an archive  |     |
| status       | contains erroneous, missing, or suspicious     |     |
|              | data or verification that the data provided    |     |
|              | appears valid. If an error has been detected,  |     |
|              | the offending data and the nature of the       |     |
|              | potential problem are identified.              |     |
+--------------+------------------------------------------------+-----+
| audit data   | Information to support a tax audit.            |     |
+--------------+------------------------------------------------+-----+
| booking      | Status of the freight transport booking that   | CR  |
| status       | includes the identities of the Commercial      | 2   |
|              | Vehicle and driver who will pick-up the        | 390 |
|              | freight or a request for more information from |     |
|              | the originator.                                |     |
+--------------+------------------------------------------------+-----+
| border       | Notification regarding the granting of         |     |
| agency       | permission for commercial freight shipment to  |     |
| clearance    | enter the U.S.                                 |     |
| results      |                                                |     |
+--------------+------------------------------------------------+-----+
| border       | Trip specific data regarding the movement of   |     |
| clearance    | goods across international borders. Includes   |     |
| data         | trip identification number. May also include   |     |
|              | results from recent border crossing screening  |     |
|              | events.                                        |     |
+--------------+------------------------------------------------+-----+
| border       | Request for trip specific data regarding the   |     |
| clearance    | movement of goods across international         |     |
| data request | borders. Includes trip identification number.  |     |
|              | May also include results from recent border    |     |
|              | crossing screening events.                     |     |
+--------------+------------------------------------------------+-----+
| border       | Reports clearance event data regarding action  |     |
| clearance    | taken at border, including acceptance or       |     |
| event        | override of system decision, and date/time     |     |
|              | stamp.                                         |     |
+--------------+------------------------------------------------+-----+
| border       | Notification regarding the crossing status of  |     |
| clearance    | commercial freight shipment scheduled to enter |     |
| status       | the U.S. Includes portions of border agency    |     |
|              | and transportation agency clearance results,   |     |
|              | as they become available. Recipients may       |     |
|              | include trade regulatory agencies that do not  |     |
|              | receive status information directly from U.S.  |     |
|              | Customs (e.g., other transportation agencies   |     |
|              | with trade related responsibilities, such as   |     |
|              | NHTSA, MARAD, etc.).                           |     |
+--------------+------------------------------------------------+-----+
| breach       | This is an Intermodal Freight Shipper\'s       | CR  |
| response     | response to a breach or tamper event of their  | 2   |
|              | freight equipment. There may be instructions   | 390 |
|              | for handling of the shipment, possible         |     |
|              | re-routing or pickup.                          |     |
+--------------+------------------------------------------------+-----+
| citation     | Report of commercial vehicle citation. The     |     |
|              | citation includes references to the statute(s) |     |
|              | that was (were) violated. It includes          |     |
|              | information on the violator and the officer    |     |
|              | issuing the citation. A citation differs from  |     |
|              | a violation because it is adjudicated by the   |     |
|              | courts. The information may be provided as a   |     |
|              | response to a real-time query or proactively   |     |
|              | by the source. The query flow is not           |     |
|              | explicitly shown.                              |     |
+--------------+------------------------------------------------+-----+
| commercial   | Information describing commercial vehicle      |     |
| vehicle      | travel and commodity flow characteristics.     |     |
| archive data | Content may include a catalog of available     |     |
|              | information, the actual information to be      |     |
|              | archived, and associated meta data that        |     |
|              | describes the archived information.            |     |
+--------------+------------------------------------------------+-----+
| commercial   | Information about a breach or tamper event on  | CR  |
| vehicle      | a Commercial Vehicle or its attached freight   | 2   |
| breach       | equipment which includes identity, type of     | 390 |
|              | breach, location, and time.                    |     |
+--------------+------------------------------------------------+-----+
| commercial   | This flow safely disables a specific           | CR  |
| vehicle      | commercial vehicle.                            | 2   |
| disable      |                                                | 390 |
+--------------+------------------------------------------------+-----+
| commercial   | Commercial vehicle and driver status measured  | CR  |
| vehicle      | by on-board ITS equipment.                     | 2   |
| measures     |                                                | 390 |
+--------------+------------------------------------------------+-----+
| compliance   | Report containing results of carrier           |     |
| review       | compliance review, including concomitant       |     |
| report       | out-of-service notifications, carrier          |     |
|              | warnings/notifications. The information may be |     |
|              | provided as a response to a real-time query or |     |
|              | proactively by the source. The query flow is   |     |
|              | not explicitly shown.                          |     |
+--------------+------------------------------------------------+-----+
| credential   | Application for commercial vehicle             |     |
| application  | credentials. Authorization for payment is      |     |
|              | included.                                      |     |
+--------------+------------------------------------------------+-----+
| credential   | Jurisdiction\'s rates for various credentials  |     |
| fee          | (IRP, IFTA, etc.) that are exchanged between   |     |
| coordination | agencies.                                      |     |
+--------------+------------------------------------------------+-----+
| credentials  | Response containing full credentials           |     |
| information  | information. \"Response\" may be provided in   |     |
|              | reaction to a real-time query or a standing    |     |
|              | request for updated information. The query     |     |
|              | flow is not explicitly shown.                  |     |
+--------------+------------------------------------------------+-----+
| credentials  | Credentials information such as registration,  |     |
| status       | licensing, insurance, check flags, and         |     |
| information  | electronic screening enrollment data. A unique |     |
|              | identifier is included. Corresponds to the     |     |
|              | credentials portion of CVISN \"snapshots.\"    |     |
|              | The status information may be provided as a    |     |
|              | response to a real-time query or as a result   |     |
|              | of a standing request for updated information  |     |
|              | (subscription). This may also include          |     |
|              | information about non-U.S. fleets for use by   |     |
|              | U.S. authorities, and information regarding    |     |
|              | U.S. fleets made available to Mexican and      |     |
|              | Canadian authorities. The query flow is not    |     |
|              | explicitly shown.                              |     |
+--------------+------------------------------------------------+-----+
| current      | Restrictions levied on transportation asset    |     |
| asset        | usage based on infrastructure design, surveys, |     |
| restrictions | tests, or analyses. This includes standard     |     |
|              | facility design height, width, and weight      |     |
|              | restrictions, special restrictions such as     |     |
|              | spring weight restrictions, and temporary      |     |
|              | facility restrictions that are imposed during  |     |
|              | maintenance and construction.                  |     |
+--------------+------------------------------------------------+-----+
| CVO driver   | This flow represents the tactile or auditory   | CR  |
| in           | interface with ITS equipment containing the    | 2   |
| itialization | commercial vehicle driver and vehicle          | 390 |
|              | information. This flow contains inquiries to   |     |
|              | the commercial vehicle managing system.        |     |
+--------------+------------------------------------------------+-----+
| CVO          | This flow represents the visual or auditory    | CR  |
| pass/pull-in | interface with ITS equipment containing a      | 2   |
| message      | message sent to commercial vehicle driver      | 390 |
|              | indicating whether to bypass or requesting     |     |
|              | pull in to inspection/verification stop along  |     |
|              | with inspection results (e.g., LED indicator   |     |
|              | on transponder or variable message sign).      |     |
+--------------+------------------------------------------------+-----+
| CVO weight   | Physical attribute of commercial vehicle that  |     |
| and presence | can be measured (for example, weight, number   |     |
|              | of axles, axle spacing, etc.).                 |     |
+--------------+------------------------------------------------+-----+
| daily site   | Record of daily activities at commercial       |     |
| activity     | vehicle check stations including summaries of  |     |
| data         | screening events and inspections.              |     |
+--------------+------------------------------------------------+-----+
| declaration  | Notification containing information regarding  |     |
| information  | pending commercial freight shipment into the   |     |
|              | U.S.                                           |     |
+--------------+------------------------------------------------+-----+
| disable      | A request that a specific commercial vehicle   | CR  |
| commercial   | should be safely disabled.                     | 2   |
| vehicle      |                                                | 390 |
+--------------+------------------------------------------------+-----+
| domestic     | Real-time or near real-time data regarding     |     |
| tr           | trade transportation activity. Potentially     |     |
| ansportation | categorized by shipper classification,         |     |
| information  | carrier, commodity, etc. Intended for use as a |     |
|              | transportation decision tool.                  |     |
+--------------+------------------------------------------------+-----+
| driver alert | Commercial Vehicle Driver response to a breach | CR  |
| response     | alert for a Freight Equipment breach or tamper | 2   |
|              | event.                                         | 390 |
+--------------+------------------------------------------------+-----+
| driver       | The physical or visible characteristics of a   | CR  |
| identity     | commercial vehicle driver that can be measured | 2   |
| cha          | to uniquely identify a driver. Could be an     | 390 |
| racteristics | Identification Card with a Personal            |     |
|              | Identification Number, biometrics, or visual   |     |
|              | verification by an operator.                   |     |
+--------------+------------------------------------------------+-----+
| driver log   | A daily log showing hours in service for the   |     |
|              | current driver.                                |     |
+--------------+------------------------------------------------+-----+
| driver log   | Request for driver log data.                   |     |
| request      |                                                |     |
+--------------+------------------------------------------------+-----+
| driver to    | Requests from the driver and vehicle for       |     |
| fleet        | routing, payment, and enrollment information.  |     |
| request      |                                                |     |
+--------------+------------------------------------------------+-----+
| electronic   | Notification to roadside (via transponder) of  |     |
| lock data    | the presence and status of electronic cargo    |     |
|              | locks.                                         |     |
+--------------+------------------------------------------------+-----+
| electronic   | Request from roadside for data regarding       |     |
| lock data    | presence and status of electronic cargo locks. |     |
| request      |                                                |     |
+--------------+------------------------------------------------+-----+
| electronic   | Request for identification data to support     |     |
| screening    | electronic screening.                          |     |
| request      |                                                |     |
+--------------+------------------------------------------------+-----+
| emergency    | Acknowledge request for emergency assistance   |     |
| acknowledge  | and provide additional details regarding       |     |
|              | actions and verification requirements.         |     |
+--------------+------------------------------------------------+-----+
| emergency    | A request for additional information or a      |     |
| data request | control command issued by the emergency        |     |
|              | response agency in response to an emergency    |     |
|              | request for assistance from a traveler.        |     |
+--------------+------------------------------------------------+-----+
| emergency    | An emergency request for assistance originated | CR  |
| notification | by a traveler using an in-vehicle, public      | 2   |
|              | access, or personal device or originated by a  | 390 |
|              | transit vehicle operator using an on-board     |     |
|              | device.                                        |     |
+--------------+------------------------------------------------+-----+
| expected     | Driver identification information, e.g.,       | CR  |
| driver       | encrypted PIN codes issued to drivers,         | 2   |
| identity     | encrypted driver biometric parameters.         | 390 |
| cha          |                                                |     |
| racteristics |                                                |     |
+--------------+------------------------------------------------+-----+
| fleet and    | Information about threats detected by          | CR  |
| freight      | commercial vehicle fleet and freight           | 2   |
| threat       | operators. The threats include incidents       | 390 |
| information  | involving commercial vehicles (i.e.,           |     |
|              | hijacking), unusual activities observed by     |     |
|              | commercial vehicle operators (i.e., truck      |     |
|              | parked under a bridge), and incidents          |     |
|              | involving freight equipment (i.e., freight     |     |
|              | equipment tampering).                          |     |
+--------------+------------------------------------------------+-----+
| fleet to     | Updated instructions to the driver including   |     |
| driver       | dispatch, routing, and special instructions.   |     |
| update       |                                                |     |
+--------------+------------------------------------------------+-----+
| freight      | Information about a breach or tamper event on  | CR  |
| breach       | Freight Equipment which includes identity,     | 2   |
|              | type of breach, location, and time.            | 390 |
+--------------+------------------------------------------------+-----+
| freight      | Container, trailer, or chassis information     | CR  |
| equipment    | regarding identity, type, location, brake wear | 2   |
| information  | data, mileage, seal #, seal type, door         | 390 |
|              | open/close status, chassis bare/covered        |     |
|              | status, tethered / untethered status, Bill of  |     |
|              | Lading, and sensor status.                     |     |
+--------------+------------------------------------------------+-----+
| freight      | Parameters to configure the Freight Equipment  | CR  |
| monitoring   | for event reporting and keep alive functions.  | 2   |
| parameters   |                                                | 390 |
+--------------+------------------------------------------------+-----+
| freight      | Booking information for the transport of       | CR  |
| transport    | freight that includes company, contact         | 2   |
| booking      | information, point of origin, pick-up          | 390 |
|              | location, drop-off location, and freight       |     |
|              | equipment identifier.                          |     |
+--------------+------------------------------------------------+-----+
| hazmat       | Sensed characteristics of a vehicle that are   | CR  |
| e            | analyzed to indicate if the vehicle is         | 2   |
| nvironmental | carrying a security sensitive substance, e.g., | 390 |
| factors      | detection of radiation or ammonia compounds.   |     |
+--------------+------------------------------------------------+-----+
| hazmat       | Information about a particular hazmat load     |     |
| information  | including nature of the load and unloading     |     |
|              | instructions. May also include hazmat vehicle  |     |
|              | route and route update information.            |     |
+--------------+------------------------------------------------+-----+
| hazmat       | Request for information about a particular     |     |
| information  | hazmat load.                                   |     |
| request      |                                                |     |
+--------------+------------------------------------------------+-----+
| hazmat spill | This data flow is used by the on-board cargo   | []{ |
| notification | monitoring equipment package to contact        | .ma |
|              | emergency response organizations when the      | rk} |
|              | cargo sensors detect a release of hazardous    |     |
|              | material. This information will include the    |     |
|              | vehicle location discussed above as well as    |     |
|              | identifying the carrier. The information may   |     |
|              | be provided as a response to a real-time query |     |
|              | or proactively by the source. The query flow   |     |
|              | is not explicitly shown.                       |     |
+--------------+------------------------------------------------+-----+
| id           | The physical characteristics of a commercial   | CR  |
| entification | vehicle that can be used to determine a        | 2   |
| information  | vehicle\'s identity, such as a license plate   | 390 |
|              | number, USDOT number, ICC number, bar code,    |     |
|              | etc.                                           |     |
+--------------+------------------------------------------------+-----+
| identities   | Identification information for the Commercial  | CR  |
|              | Vehicle (e.g., license plate number or USDOT   | 2   |
|              | number), Freight Equipment (e.g., container,   | 390 |
|              | chassis, or trailer identification), and       |     |
|              | Driver.                                        |     |
+--------------+------------------------------------------------+-----+
| information  | Information on violators provided by a law     | CR  |
| on violators | enforcement agency. May include information    | 2   |
|              | about commercial vehicle violations or other   | 390 |
|              | kinds of violations associated with the        |     |
|              | particular entity. The information may be      |     |
|              | provided as a response to a real-time query or |     |
|              | proactively by the source. The query flow is   |     |
|              | not explicitly shown.                          |     |
+--------------+------------------------------------------------+-----+
| intermod CVO | Cargo movement logs, routing information, and  |     |
| coord        | cargo ID's.                                    |     |
+--------------+------------------------------------------------+-----+
| map update   | Request for a map update which could include a | CR  |
| request      | new underlying map or map layer updates.       | 2   |
|              |                                                | 390 |
+--------------+------------------------------------------------+-----+
| map updates  | Map update which could include a new           | CR  |
|              | underlying static or real-time map or map      | 2   |
|              | layer(s) update.                               | 390 |
+--------------+------------------------------------------------+-----+
| on-board     | Safety data measured by on-board sensors.      | []{ |
| safety data  | Includes information about the vehicle,        | .ma |
|              | vehicle components, cargo, and driver.         | rk} |
+--------------+------------------------------------------------+-----+
| on-board     | Request for on-board vehicle safety data by    |     |
| safety       | the roadside equipment.                        |     |
| request      |                                                |     |
+--------------+------------------------------------------------+-----+
| on-board     | Information about the commercial vehicle       |     |
| vehicle data | stored on-board (for maintenance purposes,     |     |
|              | gate access, cargo status, lock status, etc.). |     |
+--------------+------------------------------------------------+-----+
| on-board     | Request for on-board vehicle data.             |     |
| vehicle      |                                                |     |
| request      |                                                |     |
+--------------+------------------------------------------------+-----+
| pass/pull-in | Command to commercial vehicle to pull into or  |     |
|              | bypass inspection station.                     |     |
+--------------+------------------------------------------------+-----+
| payment      | Payment of some kind (e.g., toll, parking,     |     |
|              | fare) by traveler, which, in most cases, can   |     |
|              | be related to a credit account.                |     |
+--------------+------------------------------------------------+-----+
| payment      | Request for payment from financial             |     |
| request      | institution.                                   |     |
+--------------+------------------------------------------------+-----+
| position fix | Information, which provides a traveler\'s or   |     |
|              | vehicles geographical position.                |     |
+--------------+------------------------------------------------+-----+
| request for  | Request to deduct cost of service from user\'s |     |
| payment      | payment account.                               |     |
+--------------+------------------------------------------------+-----+
| request tag  | Request for tag information including credit   |     |
| data         | identity, stored value card cash, etc.         |     |
+--------------+------------------------------------------------+-----+
| road network | Current and forecasted traffic information,    | CR  |
| conditions   | road and weather conditions, traffic incident  | 2   |
|              | information, and other road network status.    | 390 |
|              | Either raw data, processed data, or some       |     |
|              | combination of both may be provided by this    |     |
|              | architecture flow. Information on diversions   |     |
|              | and alternate routes, closures, and special    |     |
|              | traffic restrictions (lane/shoulder use,       |     |
|              | weight restrictions, width restrictions, HOV   |     |
|              | requirements) in effect is also included.      |     |
+--------------+------------------------------------------------+-----+
| route        | An alert that indicates a deviation from a     | CR  |
| deviation    | planned route has been detected. The alert     | 2   |
| alert        | will contain the current Commercial Vehicle    | 390 |
|              | location and identity.                         |     |
+--------------+------------------------------------------------+-----+
| route plan   | Tailored route provided by ISP in response to  |     |
|              | a specific request.                            |     |
+--------------+------------------------------------------------+-----+
| route        | Request for a tailored route based on given    |     |
| request      | constraints.                                   |     |
+--------------+------------------------------------------------+-----+
| route        | Information about routes, road segments, and   | CR  |
| restrictions | areas that do not allow the transport of       | 2   |
|              | security sensitive hazmat cargoes or include   | 390 |
|              | other restrictions (such as height or weight   |     |
|              | limits).                                       |     |
+--------------+------------------------------------------------+-----+
| safe vehicle | Control signal disabling or enabling           | CR  |
| disable      | commercial vehicle.                            | 2   |
|              |                                                | 390 |
+--------------+------------------------------------------------+-----+
| safety       | Record containing results of commercial        |     |
| inspection   | vehicle safety inspection.                     |     |
| record       |                                                |     |
+--------------+------------------------------------------------+-----+
| safety       | Report containing results of commercial        |     |
| inspection   | vehicle safety inspection. The information may |     |
| report       | be provided as a response to a real-time query |     |
|              | or proactively by the source. The query flow   |     |
|              | is not explicitly shown.                       |     |
+--------------+------------------------------------------------+-----+
| safety       | Request for safety inspection record.          |     |
| inspection   |                                                |     |
| request      |                                                |     |
+--------------+------------------------------------------------+-----+
| safety       | Safety information such as safety ratings,     |     |
| status       | inspection summaries, and violation summaries. |     |
| information  | A unique identifier is included. Corresponds   |     |
|              | to the safety portion of CVISN \"snapshots.\"  |     |
|              | The status information may be provided as a    |     |
|              | response to a real-time query or as a result   |     |
|              | of a standing request for updated information  |     |
|              | (subscription). This may also include          |     |
|              | information about non-U.S. fleets for use by   |     |
|              | U.S. authorities, and information regarding    |     |
|              | U.S. fleets made available to Mexican and      |     |
|              | Canadian authorities. The query flow is not    |     |
|              | explicitly shown.                              |     |
+--------------+------------------------------------------------+-----+
| screening    | Results of CVO electronic screening activity.  |     |
| event record |                                                |     |
+--------------+------------------------------------------------+-----+
| tag data     | Unique tag ID and related vehicle information. | []{ |
|              |                                                | .ma |
|              |                                                | rk} |
+--------------+------------------------------------------------+-----+
| tag update   | Update data held in tag which can be read by   |     |
|              | another roadside device (Commercial Vehicle    |     |
|              | Check Subsystem, Toll Collection Subsystem,    |     |
|              | etc.).                                         |     |
+--------------+------------------------------------------------+-----+
| tax filing   | Commercial vehicle tax filing data.            |     |
|              | Authorization for payment is included.         |     |
+--------------+------------------------------------------------+-----+
| toll data    | Current toll schedules for different types of  |     |
|              | vehicles as well as advanced toll payment      |     |
|              | information.                                   |     |
+--------------+------------------------------------------------+-----+
| toll data    | Request made to obtain toll schedule           |     |
| request      | information or pay a toll in advance. The      |     |
|              | request can be a subscription that initiates   |     |
|              | as-needed information updates as well as a     |     |
|              | one-time request for information.              |     |
+--------------+------------------------------------------------+-----+
| transaction  | Response to transaction request. Normally      |     |
| status       | dealing with a request for payment.            |     |
+--------------+------------------------------------------------+-----+
| tr           | Notification regarding the granting of         |     |
| ansportation | permission for commercial freight shipment to  |     |
| border       | enter the U.S. Includes directions for         |     |
| clearance    | commercial driver to proceed to nearest        |     |
| assessment   | vehicle weigh and inspection station for       |     |
|              | further review if required.                    |     |
+--------------+------------------------------------------------+-----+
| trip         | Specific identifiers extracted from            |     |
| declaration  | notification containing information regarding  |     |
| identifiers  | pending commercial freight shipment into the   |     |
|              | U.S. Includes carrier, vehicle, and driver     |     |
|              | identification data.                           |     |
+--------------+------------------------------------------------+-----+
| trip         | The unique trip load number for a specific     |     |
| id           | cross-border shipment.                         |     |
| entification |                                                |     |
| number       |                                                |     |
+--------------+------------------------------------------------+-----+
| trip log     | Driver\'s daily log, vehicle location,         |     |
|              | mileage, and trip activity (includes           |     |
|              | screening, inspection and border clearance     |     |
|              | event data as well as fare payments).          |     |
+--------------+------------------------------------------------+-----+
| trip log     | This flow represents the tactile or auditory   | CR  |
| information  | interface with ITS equipment containing the    | 2   |
|              | information entered into the trip log, or      | 390 |
|              | request for update.                            |     |
+--------------+------------------------------------------------+-----+
| trip log     | Request for trip log.                          |     |
| request      |                                                |     |
+--------------+------------------------------------------------+-----+
| vehicle      | Location of a vehicle calculated on-board the  | CR  |
| location     | vehicle.                                       | 2   |
|              |                                                | 390 |
+--------------+------------------------------------------------+-----+
| vehicle      | Vehicle probe data indicating identity, route  |     |
| probe data   | segment identity, link time and location.      |     |
+--------------+------------------------------------------------+-----+
| vehicle      | In-vehicle signage data generated by the       |     |
| signage data | roadway infrastructure indicating either road  |     |
|              | conditions, street names, or special           |     |
|              | information.                                   |     |
+--------------+------------------------------------------------+-----+
| violation    | Notification to enforcement agency of a        |     |
| notification | violation. The violation notification flow     |     |
|              | describes the statute or regulation that was   |     |
|              | violated and how it was violated (e.g.,        |     |
|              | overweight on specific axle by xxx pounds or   |     |
|              | which brake was out of adjustment and how far  |     |
|              | out of                                         |     |
|              |                                                |     |
|              | adjustment it was). A violation differs from a |     |
|              | citation because it is not adjudicated by the  |     |
|              | courts.                                        |     |
+--------------+------------------------------------------------+-----+

[]{#Table3 .anchor}**Table 3** presents the definitions for subsystems
and terminators. Unless otherwise indicated, all definitions are from
National ITS Architecture Version 5.0 \[Reference 4\].

Table 3. Subsystem and Terminator Descriptions.

+-----------------+-----------------------------------------------+----+
| Subsystem and   |                                               |    |
| Terminator      |                                               |    |
| Descriptions    |                                               |    |
+=================+===============================================+====+
| **Subsyst       | **Updated Description**                       | ** |
| em/Terminator** |                                               | CR |
|                 |                                               | \# |
|                 |                                               | ** |
+-----------------+-----------------------------------------------+----+
| Alerting and    | This terminator represents the federal,       | CR |
| Advisory        | state, and local alerting and advisory        | 23 |
| Systems         | systems that provide alerts, advisories, and  | 90 |
|                 | other potential threat information that is    |    |
|                 | relevant to surface transportation systems.   |    |
|                 | This includes systems such as the Information |    |
|                 | Sharing and Analysis Centers (ISACs), the     |    |
|                 | National Infrastructure Protection Center     |    |
|                 | (NIPC), the Homeland Security Advisory System |    |
|                 | (HSAS), and other systems that provide        |    |
|                 | intelligence about potential, imminent, or    |    |
|                 | actual attacks on the transportation          |    |
|                 | infrastructure or its supporting information  |    |
|                 | systems.\                                     |    |
|                 | \                                             |    |
|                 | This terminator also represents the early     |    |
|                 | warning and emergency alert systems operated  |    |
|                 | by federal, state, county, and local agencies |    |
|                 | that provide advisories and alerts regarding  |    |
|                 | all types of emergencies including natural    |    |
|                 | hazards (floods, hurricanes, tornados,        |    |
|                 | earthquakes), accidents (chemical spills,     |    |
|                 | nuclear power plant emergencies) and other    |    |
|                 | civil emergencies such as child abduction     |    |
|                 | alerts that impact transportation system      |    |
|                 | operation and/or require immediate public     |    |
|                 | notification. Note that weather related       |    |
|                 | watches and warnings, such as those issued by |    |
|                 | the National Hurricane Center, are provided   |    |
|                 | by both this terminator and the Weather       |    |
|                 | Service terminator since many alerting and    |    |
|                 | advisory systems and the National Weather     |    |
|                 | Service both provide severe weather and       |    |
|                 | related hazards information.\                 |    |
|                 | \                                             |    |
|                 | The alerts and advisories that are provided   |    |
|                 | by the systems represented by this terminator |    |
|                 | are based on analysis of potential threat     |    |
|                 | information that is collected from a variety  |    |
|                 | of sources, including information collected   |    |
|                 | by ITS systems. The bidirectional interface   |    |
|                 | with this terminator allows potential threat  |    |
|                 | information that is collected by ITS systems  |    |
|                 | to be provided to the alerting and advisory   |    |
|                 | systems to improve their ability to identify  |    |
|                 | threats and provide useful and timely         |    |
|                 | information.\                                 |    |
|                 | \                                             |    |
|                 | The types of information provided by this     |    |
|                 | terminator include general assessments and    |    |
|                 | incident awareness information, advisories    |    |
|                 | that identify potential threats or            |    |
|                 | recommendations to increase preparedness      |    |
|                 | levels, alerts regarding imminent or          |    |
|                 | in-progress emergencies, and specific threat  |    |
|                 | information such as visual imagery used for   |    |
|                 | biometric image processing.                   |    |
+-----------------+-----------------------------------------------+----+
| Archived Data   | The Archived Data Management Subsystem        | CR |
| Management      | collects, archives, manages, and distributes  | 23 |
| (ADMS)          | data generated from ITS sources for use in    | 90 |
|                 | transportation administration, policy         |    |
|                 | evaluation, safety, planning, performance     |    |
|                 | monitoring, program assessment, operations,   |    |
|                 | and research applications. The data received  |    |
|                 | is formatted and tagged with attributes that  |    |
|                 | define the data source, conditions under      |    |
|                 | which it was collected, data transformations, |    |
|                 | and other information (i.e., meta data)       |    |
|                 | necessary to interpret the data. The          |    |
|                 | subsystem can fuse ITS generated data with    |    |
|                 | data from non-ITS sources and other archives  |    |
|                 | to generate information products utilizing    |    |
|                 | data from multiple functional areas, modes,   |    |
|                 | and jurisdictions. The subsystem prepares     |    |
|                 | data products that can serve as inputs to     |    |
|                 | federal, state, and local data reporting      |    |
|                 | systems. This subsystem may be implemented in |    |
|                 | many different ways. It may reside within an  |    |
|                 | operational center and provide focused access |    |
|                 | to a particular agency\'s data archives.      |    |
|                 | Alternatively, it may operate as a distinct   |    |
|                 | center that collects data from multiple       |    |
|                 | agencies and sources and provides a general   |    |
|                 | data warehouse service for a region.          |    |
+-----------------+-----------------------------------------------+----+
| Basic           | This terminator represents the motorized      | CR |
| Commercial      | commercial vehicle platform that interfaces   | 23 |
| Vehicle         | with and hosts ITS electronics. This          | 90 |
|                 | terminator represents a vehicle that is used  |    |
|                 | to transport goods which are operated by      |    |
|                 | professional drivers, typically administered  |    |
|                 | as part of a larger fleet, and regulated by a |    |
|                 | Fleet-Freight Manager. This classification    |    |
|                 | applies to all such vehicles ranging from     |    |
|                 | small panel vans used in local pick-up and    |    |
|                 | delivery services to large, multi-axle        |    |
|                 | tractor-trailer rigs operating on long haul   |    |
|                 | routes.                                       |    |
+-----------------+-----------------------------------------------+----+
| Commercial      | The Commercial Vehicle Administration         |    |
| Vehicle         | Subsystem will operate at one or more fixed   |    |
| Administration  | locations within a region. This subsystem     |    |
| (CVAS)          | performs administrative functions supporting  |    |
|                 | credentials, tax, and safety regulations. It  |    |
|                 | issues credentials, collects fees and taxes,  |    |
|                 | and supports enforcement of credential        |    |
|                 | requirements. This subsystem communicates     |    |
|                 | with the Fleet Management Subsystems          |    |
|                 | associated with the motor carriers to process |    |
|                 | credentials applications and collect fuel     |    |
|                 | taxes, weight/distance taxes, and other taxes |    |
|                 | and fees associated with commercial vehicle   |    |
|                 | operations. The subsystem also receives       |    |
|                 | applications for, and issues special          |    |
|                 | Oversize/Overweight and HAZMAT permits in     |    |
|                 | coordination with other cognizant             |    |
|                 | authorities. The subsystem coordinates with   |    |
|                 | other Commercial Vehicle Administration       |    |
|                 | Subsystems (in other states/regions) to       |    |
|                 | support nationwide access to credentials and  |    |
|                 | safety information for administration and     |    |
|                 | enforcement functions. This subsystem         |    |
|                 | supports communications with Commercial       |    |
|                 | Vehicle Check Subsystems operating at the     |    |
|                 | roadside to enable credential checking and    |    |
|                 | safety information collection. The collected  |    |
|                 | safety information is processed, stored, and  |    |
|                 | made available to qualified stakeholders to   |    |
|                 | identify carriers and drivers that operate    |    |
|                 | unsafely.                                     |    |
+-----------------+-----------------------------------------------+----+
| Commercial      | The Commercial Vehicle Check Subsystem        |    |
| Vehicle Check   | supports automated vehicle identification at  |    |
| (CVCS)          | mainline speeds for credential checking,      |    |
|                 | roadside safety inspections, and              |    |
|                 | weigh-in-motion using two-way data exchange.  |    |
|                 | These capabilities include providing warnings |    |
|                 | to the commercial vehicle drivers, their      |    |
|                 | fleet managers, and proper authorities of any |    |
|                 | safety problems that have been identified,    |    |
|                 | accessing and examining historical safety     |    |
|                 | data, and automatically deciding whether to   |    |
|                 | allow the vehicle to pass or require it to    |    |
|                 | stop with operator manual override. The       |    |
|                 | Commercial Vehicle Check Subsystem also       |    |
|                 | provides supplemental inspection services to  |    |
|                 | current capabilities by supporting expedited  |    |
|                 | brake inspections, the use of operator        |    |
|                 | hand-held devices, on-board safety database   |    |
|                 | access, and the enrollment of vehicles and    |    |
|                 | carriers in the electronic clearance program. |    |
+-----------------+-----------------------------------------------+----+
| Commercial      | This terminator represents the human entity   | CR |
| Vehicle Driver  | that operates vehicles transporting goods     | 23 |
|                 | including both long haul trucks and local     | 90 |
|                 | pick up and delivery vans. This terminator is |    |
|                 | complementary to the Driver terminator in     |    |
|                 | that it represents those interactions which   |    |
|                 | are unique to Commercial Vehicle Operations.  |    |
|                 | Data flowing from the Commercial Vehicle      |    |
|                 | Driver terminator will include those system   |    |
|                 | inputs specific to Commercial Vehicle         |    |
|                 | Operations, such as information back to the   |    |
|                 | Fleet-Freight Manager. Data flowing to the    |    |
|                 | Commercial Vehicle Driver may include system  |    |
|                 | outputs such as commands to pull into a       |    |
|                 | roadside safety inspection facility. Showing  |    |
|                 | the Driver as a terminator includes the user  |    |
|                 | interface devices within the ITS architecture |    |
|                 | boundary. The Commercial Vehicle Driver will  |    |
|                 | be expected to interact with the ITS          |    |
|                 | interface devices designed to provide support |    |
|                 | for their usage.                              |    |
+-----------------+-----------------------------------------------+----+
| Commercial      | The **Commercial Vehicle** **Subsystem** part | CR |
| Vehicle         | resides in a commercial vehicle and provides  | 23 |
| Subsystem       | the sensory, processing, storage, and         | 90 |
| Aggregate       | communications functions necessary to support |    |
| (CVSAg)         | safe and efficient commercial vehicle         |    |
|                 | operations. The Commercial Vehicle Subsystem  |    |
| *\[The          | provides two-way communications between the   |    |
| Commercial      | commercial vehicle drivers, their fleet       |    |
| Vehicle         | managers, attached freight equipment, and     |    |
| Subsystem       | roadside officials, and provides HAZMAT       |    |
| Aggregate       | response teams with timely and accurate cargo |    |
| combines the    | contents information after a vehicle          |    |
| National ITS    | incident. This subsystem provides the         |    |
| Architecture    | capability to collect and process vehicle,    |    |
| Commercial      | cargo information from the attached freight   |    |
| Vehicle and     | equipment, and driver safety data and status  |    |
| Vehicle         | and alert the driver whenever there is a      |    |
| Subsystems; it  | potential safety or security problem. Basic   |    |
| is not a        | identification, security and safety status    |    |
| standalone      | data are supplied to inspection facilities at |    |
| subsystem       | mainline speeds. In addition, the subsystem   |    |
| within the      | will automatically collect and record         |    |
| National ITS    | mileage, fuel usage, and border crossings.    |    |
| A               |                                               |    |
| rchitecture.\]* | The **Vehicle Subsystem** part provides the   |    |
|                 | sensory, processing, storage, and             |    |
|                 | communications functions necessary to support |    |
|                 | efficient, safe, and convenient travel. These |    |
|                 | functions reside in general vehicles          |    |
|                 | including personal automobiles, commercial    |    |
|                 | vehicles, emergency vehicles, transit         |    |
|                 | vehicles, or other vehicle types. Information |    |
|                 | services provide the driver with current      |    |
|                 | travel conditions and the availability of     |    |
|                 | services along the route and at the           |    |
|                 | destination. Both one-way and two-way         |    |
|                 | communications options support a spectrum of  |    |
|                 | information services from low-cost broadcast  |    |
|                 | services to advanced, pay for use             |    |
|                 | personalized information services. Route      |    |
|                 | guidance capabilities assist in formulation   |    |
|                 | of an optimal route and step-by-step guidance |    |
|                 | along the travel route. Advanced sensors,     |    |
|                 | processors, enhanced driver interfaces, and   |    |
|                 | actuators complement the driver information   |    |
|                 | services so that, in addition to making       |    |
|                 | informed mode and route selections, the       |    |
|                 | driver travels these routes in a safer and    |    |
|                 | more consistent manner. Initial collision     |    |
|                 | avoidance functions provide "vigilant         |    |
|                 | co-pilot" driver-warning capabilities. More   |    |
|                 | advanced functions assume limited control of  |    |
|                 | the vehicle to maintain safe headway.         |    |
|                 | Ultimately, this subsystem supports           |    |
|                 | completely automated vehicle operation        |    |
|                 | through advanced communications with other    |    |
|                 | vehicles in the vicinity and in coordination  |    |
|                 | with supporting infrastructure subsystems.    |    |
|                 | Pre-crash safety systems are deployed and     |    |
|                 | emergency notification messages are issued    |    |
|                 | when unavoidable collisions do occur.         |    |
+-----------------+-----------------------------------------------+----+
| CVO Information | This terminator represents any organization   |    |
| Requestor       | requesting information from the CVO           |    |
|                 | Information Exchange network. It typically    |    |
|                 | represents insurance companies requesting     |    |
|                 | safety information on carriers, etc.          |    |
+-----------------+-----------------------------------------------+----+
| Emergency       | The Emergency Management Subsystem represents | CR |
| Management (EM) | public safety, emergency management, and      | 23 |
|                 | other allied agency systems that support      | 90 |
|                 | incident management, disaster response and    |    |
|                 | evacuation, security monitoring, and other    |    |
|                 | security and public safety-oriented ITS       |    |
|                 | applications. The subsystem includes the      |    |
|                 | functions associated with fixed and mobile    |    |
|                 | public safety communications centers          |    |
|                 | including public safety call taker and        |    |
|                 | dispatch centers operated by police           |    |
|                 | (including transit police), fire, and         |    |
|                 | emergency medical services. It includes the   |    |
|                 | functions associated with Emergency           |    |
|                 | Operations Centers that are activated at      |    |
|                 | local, regional, state, and federal levels    |    |
|                 | for emergencies and the portable and          |    |
|                 | transportable systems that support Incident   |    |
|                 | Command System operations at an incident.     |    |
|                 | This subsystem also represents other allied   |    |
|                 | systems including centers associated with     |    |
|                 | towing and recovery, freeway service patrols, |    |
|                 | HAZMAT response teams, and mayday service     |    |
|                 | providers.\                                   |    |
|                 | \                                             |    |
|                 | The subsystem manages sensor and surveillance |    |
|                 | equipment used to enhance transportation      |    |
|                 | security of the roadway infrastructure        |    |
|                 | (including bridges, tunnels, interchanges,    |    |
|                 | and other key roadway segments) and the       |    |
|                 | public transportation system (including       |    |
|                 | transit vehicles, public areas such as        |    |
|                 | transit stops and stations, facilities such   |    |
|                 | as transit yards, and transit infrastructure  |    |
|                 | such as rail, bridges, tunnels, or bus        |    |
|                 | guideways). The subsystem provides            |    |
|                 | security/surveillance services to improve     |    |
|                 | traveler security in public areas not a part  |    |
|                 | of the public transportation system.\         |    |
|                 | \                                             |    |
|                 | This subsystem monitors alerts, advisories,   |    |
|                 | and other threat information and prepares for |    |
|                 | and responds to identified emergencies. It    |    |
|                 | interfaces with other Emergency Management    |    |
|                 | Subsystems to support coordinated emergency   |    |
|                 | response involving multiple agencies. The     |    |
|                 | subsystem stores, coordinates, and utilizes   |    |
|                 | emergency response and evacuation plans to    |    |
|                 | facilitate this coordinated response. As the  |    |
|                 | response progresses, situation information    |    |
|                 | including damage assessments, response        |    |
|                 | status, evacuation information, and resource  |    |
|                 | information are shared to keep all allied     |    |
|                 | agencies appraised of the response. Interface |    |
|                 | with the Transit Management Subsystem allows  |    |
|                 | coordinated use of transit vehicles to        |    |
|                 | facilitate response to major emergencies and  |    |
|                 | to support evacuation efforts. The Emergency  |    |
|                 | Management Subsystem also provides a focal    |    |
|                 | point for coordination of the emergency and   |    |
|                 | evacuation information that is provided to    |    |
|                 | the traveling public, including wide-area     |    |
|                 | alerts when immediate public notification is  |    |
|                 | warranted.\                                   |    |
|                 | \                                             |    |
|                 | The subsystem tracks and manages emergency    |    |
|                 | vehicle fleets using real-time road network   |    |
|                 | status and routing information from the other |    |
|                 | center subsystems to aide in selecting the    |    |
|                 | emergency vehicle(s) and routes that will     |    |
|                 | provide the most timely response. Interface   |    |
|                 | with the Traffic Management Subsystem allows  |    |
|                 | strategic coordination in tailoring traffic   |    |
|                 | control to support emergency vehicle ingress  |    |
|                 | and egress, implementation of special traffic |    |
|                 | restrictions and closures, evacuation traffic |    |
|                 | control plans, and other special strategies   |    |
|                 | that adapt the transportation system to       |    |
|                 | better meet the unique demands of an          |    |
|                 | emergency.                                    |    |
+-----------------+-----------------------------------------------+----+
| Emergency       | This subsystem resides in an emergency        | CR |
| Vehicle (EVS)   | vehicle and provides the sensory, processing, | 23 |
|                 | storage, and communications functions         | 90 |
|                 | necessary to support safe and efficient       |    |
|                 | incident response. The subsystem represents a |    |
|                 | range of vehicles including those operated by |    |
|                 | police, fire, and emergency medical services. |    |
|                 | In addition, this subsystem represents other  |    |
|                 | incident response vehicles including towing   |    |
|                 | and recovery vehicles and freeway service     |    |
|                 | patrols. The Emergency Vehicle Subsystem      |    |
|                 | includes two-way communications to support    |    |
|                 | coordinated response to emergencies in        |    |
|                 | accordance with an associated Emergency       |    |
|                 | Management Subsystem. Emergency vehicles are  |    |
|                 | equipped with automated vehicle location      |    |
|                 | capability for monitoring by vehicle tracking |    |
|                 | and fleet management functions in the         |    |
|                 | Emergency Management Subsystem. Using these   |    |
|                 | capabilities, the appropriate emergency       |    |
|                 | vehicle to respond to each emergency is       |    |
|                 | determined. Route guidance capabilities       |    |
|                 | within the vehicle enable safe and efficient  |    |
|                 | routing to the emergency. In addition, the    |    |
|                 | emergency vehicle may be equipped to support  |    |
|                 | signal preemption through communications with |    |
|                 | the Roadway Subsystem.                        |    |
+-----------------+-----------------------------------------------+----+
| Enforcement     | This terminator represents the systems that   |    |
| Agency          | receive reports of violations detected by     |    |
|                 | various ITS facilities including individual   |    |
|                 | vehicle emissions, toll violations, CVO       |    |
|                 | violations, excessive speed in work zones,    |    |
|                 | etc.                                          |    |
+-----------------+-----------------------------------------------+----+
| Financial       | This terminator represents the organization   |    |
| Institution     | that handles all electronic fund transfer     |    |
|                 | requests to enable the transfer of funds from |    |
|                 | the user of the service to the provider of    |    |
|                 | the service. The functions and activities of  |    |
|                 | financial clearinghouses are subsumed by this |    |
|                 | entity.                                       |    |
+-----------------+-----------------------------------------------+----+
| Fleet and       | The Fleet and Freight Management Subsystem    | CR |
| Freight         | provides the capability for commercial        | 23 |
| Management      | drivers and fleet or freight managers to      | 90 |
| (FMS)           | receive real-time routing information and     |    |
|                 | access databases containing vehicle and/or    |    |
|                 | freight equipment locations as well as        |    |
|                 | carrier, vehicle, freight equipment and       |    |
|                 | driver information. In addition, the          |    |
|                 | capability to purchase credentials            |    |
|                 | electronically shall also be provided, with   |    |
|                 | automated and efficient connections to        |    |
|                 | financial institutions and regulatory         |    |
|                 | agencies, along with post-trip automated      |    |
|                 | mileage and fuel usage reporting. The Fleet   |    |
|                 | and Freight Management Subsystem also         |    |
|                 | provides the capability for fleet managers to |    |
|                 | monitor the safety and security of their      |    |
|                 | commercial vehicle drivers and fleet. The     |    |
|                 | subsystem also supports application for       |    |
|                 | hazmat credentials and makes information      |    |
|                 | about hazmat cargo available to agencies as   |    |
|                 | required. Within this subsystem lies all the  |    |
|                 | functionality associated with subsystems and  |    |
|                 | components necessary to enroll and            |    |
|                 | participate in international goods movement   |    |
|                 | programs aimed at enhancing trade and         |    |
|                 | transportation safety and security.           |    |
+-----------------+-----------------------------------------------+----+
| Freight         | This terminator represents a freight          | CR |
| Equipment       | container, intermodal chassis or trailer and  | 23 |
|                 | provides information to support safe, secure  | 90 |
|                 | and efficient freight operations. This        |    |
|                 | terminator provides equipment safety data and |    |
|                 | status and can alert the appropriate systems  |    |
|                 | of an incident, breach, or tamper event. This |    |
|                 | terminator provides accurate position         |    |
|                 | information to support in-transit visibility  |    |
|                 | of freight equipment.                         |    |
+-----------------+-----------------------------------------------+----+
| Information     | This subsystem collects, processes, stores,   | [  |
| Service         | and disseminates transportation information   | ]{ |
| Provider (ISP)  | to system operators and the traveling public. | .m |
|                 | The subsystem can play several different      | ar |
|                 | roles in an integrated ITS. In one role, the  | k} |
|                 | ISP provides a general data warehousing       |    |
|                 | function, collecting information from         |    |
|                 | transportation system operators and           |    |
|                 | redistributing this information to other      |    |
|                 | system operators in the region and other      |    |
|                 | ISPs. In this information redistribution      |    |
|                 | role, the ISP provides a bridge between the   |    |
|                 | various transportation systems that produce   |    |
|                 | the information and the other ISPs and their  |    |
|                 | subscribers that use the information. The     |    |
|                 | second role of an ISP is focused on delivery  |    |
|                 | of traveler information to subscribers and    |    |
|                 | the public at large. Information provided     |    |
|                 | includes basic advisories, traffic and road   |    |
|                 | conditions, transit schedule information,     |    |
|                 | yellow pages information, ridematching        |    |
|                 | information, and parking information. The     |    |
|                 | subsystem also provides the capability to     |    |
|                 | provide specific directions to travelers by   |    |
|                 | receiving origin and destination requests     |    |
|                 | from travelers, generating route plans, and   |    |
|                 | returning the calculated plans to the users.  |    |
|                 | In addition to general route planning for     |    |
|                 | travelers, the ISP also supports specialized  |    |
|                 | route planning for vehicle fleets. In this    |    |
|                 | third role, the ISP function may be dedicated |    |
|                 | to, or even embedded within, the dispatch     |    |
|                 | system. Reservation services are also         |    |
|                 | provided in advanced implementations. The     |    |
|                 | information is provided to the traveler       |    |
|                 | through the Personal Information Access       |    |
|                 | Subsystem, Remote Traveler Support Subsystem, |    |
|                 | and various Vehicle Subsystems through        |    |
|                 | available communications links. Both basic    |    |
|                 | one-way (broadcast) and personalized two-way  |    |
|                 | information provision is supported. The       |    |
|                 | subsystem provides the capability for an      |    |
|                 | informational infrastructure to connect       |    |
|                 | providers and consumers, and gather that      |    |
|                 | market information needed to assist in the    |    |
|                 | planning of service improvements and in       |    |
|                 | maintenance of operations.                    |    |
+-----------------+-----------------------------------------------+----+
| Intermodal      | A depot operated either by a depot manager or | CR |
| Freight Depot   | an alternate mode freight shipper which       | 23 |
|                 | represents the point of exchange where        | 90 |
|                 | freight is moved from one mode to another.    |    |
|                 | The depot has knowledge about activities that |    |
|                 | may impact travel on roadways such as large   |    |
|                 | groups of trucks entering the highway after   |    |
|                 | unloading a ship or freight train. The depot  |    |
|                 | interfaces to the ITS to coordinate freight   |    |
|                 | movement with Fleet-Freight Managers, gather  |    |
|                 | information on traffic conditions affecting   |    |
|                 | the depot, and to provide information on      |    |
|                 | intermodal freight activities that is         |    |
|                 | pertinent to traffic movement in the          |    |
|                 | surrounding area.                             |    |
+-----------------+-----------------------------------------------+----+
| Intermodal      | This terminator represents organizations that | CR |
| Freight Shipper | engage in the shipment of freight by multiple | 23 |
|                 | means, in addition to road-going trucks. They | 90 |
|                 | enable ITS to move goods on routes that       |    |
|                 | require the use of other modes of             |    |
|                 | transportation such as heavy rail, air, sea,  |    |
|                 | etc. This terminator includes third party     |    |
|                 | logistics providers (i.e., brokers, freight   |    |
|                 | forwarders, etc) that interface with          |    |
|                 | Fleet-Freight Managers to transfer cargo from |    |
|                 | one mode to another. This definition includes |    |
|                 | those responsible for the movement of freight |    |
|                 | across international borders. These entities  |    |
|                 | are responsible for filing required           |    |
|                 | declarations, and have an acute interest in   |    |
|                 | the status of international shipments.        |    |
+-----------------+-----------------------------------------------+----+
| Location Data   | This terminator provides accurate position    |    |
| Source          | information. Systems, which use GPS,          |    |
|                 | terrestrial trilateration, or driver inputs,  |    |
|                 | are all potential examples of Location Data   |    |
|                 | Sources. This terminator contains sensors     |    |
|                 | such as radio position receivers (e.g., GPS)  |    |
|                 | and/or dead reckoning sensors (e.g.,          |    |
|                 | odometer, differential odometer, magnetic     |    |
|                 | compass, gyro, etc.). This terminator implies |    |
|                 | that some additional functionality associated |    |
|                 | with developing an absolute position is       |    |
|                 | outside the system and will not be directly   |    |
|                 | modeled by the logical or physical            |    |
|                 | architecture representations of the system.   |    |
+-----------------+-----------------------------------------------+----+
| Maintenance and | The Maintenance and Construction Management   |    |
| Construction    | Subsystem monitors and manages roadway        |    |
| Management      | infrastructure construction and maintenance   |    |
|                 | activities. Representing both public agencies |    |
|                 | and private contractors that provide these    |    |
|                 | functions, this subsystem manages fleets of   |    |
|                 | maintenance, construction, or special service |    |
|                 | vehicles (e.g., snow and ice control          |    |
|                 | equipment). The subsystem receives a wide     |    |
|                 | range of status information from these        |    |
|                 | vehicles and performs vehicle dispatch,       |    |
|                 | routing, and resource management for the      |    |
|                 | vehicle fleets and associated equipment. The  |    |
|                 | subsystem participates in incident response   |    |
|                 | by deploying maintenance and construction     |    |
|                 | resources to an incident scene, in            |    |
|                 | coordination with other center subsystems.    |    |
|                 | The subsystem manages equipment at the        |    |
|                 | roadside, including environmental sensors and |    |
|                 | automated systems that monitor and mitigate   |    |
|                 | adverse road and surface weather conditions.  |    |
|                 | The subsystem manages the repair and          |    |
|                 | maintenance of both non-ITS and ITS equipment |    |
|                 | including the traffic controllers, detectors, |    |
|                 | dynamic message signs, signals, and other     |    |
|                 | equipment associated with the roadway         |    |
|                 | infrastructure. Additional interfaces to      |    |
|                 | weather information providers (the weather    |    |
|                 | service and surface transportation weather    |    |
|                 | service providers) provide current and        |    |
|                 | forecast weather information that can be      |    |
|                 | fused with other data sources and used to     |    |
|                 | support advanced decision support systems     |    |
|                 | that increase the efficiency and              |    |
|                 | effectiveness of maintenance and construction |    |
|                 | operations.                                   |    |
|                 |                                               |    |
|                 | The subsystem remotely monitors and manages   |    |
|                 | ITS capabilities in work zones, gathering,    |    |
|                 | storing, and disseminating work zone          |    |
|                 | information to other systems. It manages      |    |
|                 | traffic in the vicinity of the work zone and  |    |
|                 | advises drivers of work zone status (either   |    |
|                 | directly at the roadside or through an        |    |
|                 | interface with the Information Service        |    |
|                 | Provider or Traffic Management subsystems.)   |    |
|                 | It schedules and manages the location and     |    |
|                 | usage of maintenance assets (such as portable |    |
|                 | dynamic message signs).                       |    |
|                 |                                               |    |
|                 | Construction and maintenance activities are   |    |
|                 | tracked and coordinated with other systems,   |    |
|                 | improving the quality and accuracy of         |    |
|                 | information available regarding closures and  |    |
|                 | other roadway construction and maintenance    |    |
|                 | activities.                                   |    |
+-----------------+-----------------------------------------------+----+
| Map Update      | This terminator represents a third-party      | CR |
| Provider        | developer and provider of digitized map       | 23 |
|                 | databases used to support ITS services. It    | 90 |
|                 | supports the provision of the databases that  |    |
|                 | are required exclusively for route guidance   |    |
|                 | (navigable maps) as well as those that are    |    |
|                 | used exclusively for display by operators,    |    |
|                 | e.g., Fleet-Freight Managers (restricted      |    |
|                 | routes) and at traveler information points,   |    |
|                 | e.g., kiosks (display maps).                  |    |
+-----------------+-----------------------------------------------+----+
| Other CVAS      | This terminator is intended to provide a      |    |
|                 | source and destination for ITS data flows     |    |
|                 | between peer (e.g., inter-regional)           |    |
|                 | commercial vehicle administration functions.  |    |
|                 | It enables commercial vehicle administration  |    |
|                 | activities to be coordinated across different |    |
|                 | jurisdictional areas. In the Physical         |    |
|                 | Architecture, this terminator is a reciprocal |    |
|                 | Commercial Vehicle Administration Subsystem   |    |
|                 | (CVAS). This terminator encompasses all       |    |
|                 | functions associated with commercial vehicle  |    |
|                 | safety, registration, and operating authority |    |
|                 | for non-U.S. based commercial motor vehicle   |    |
|                 | carriers. The agencies represented herein may |    |
|                 | include Federal, state, provincial, and local |    |
|                 | regulatory entities outside the U.S.          |    |
+-----------------+-----------------------------------------------+----+
| Parking         | The Parking Management Subsystem provides     |    |
| Management      | electronic monitoring and management of       |    |
| (PMS)           | parking facilities. It supports a dedicated   |    |
|                 | short-range communications (DSRC)             |    |
|                 | communications link to the Vehicle Subsystem  |    |
|                 | that allows electronic collection of parking  |    |
|                 | fees. It also includes the instrumentation,   |    |
|                 | signs, and other infrastructure that monitors |    |
|                 | parking lot usage and provides local          |    |
|                 | information about parking availability and    |    |
|                 | other general parking information. This       |    |
|                 | portion of the subsystem functionality must   |    |
|                 | be located in the parking facility where it   |    |
|                 | can monitor, classify, and share information  |    |
|                 | with customers and their vehicles. The        |    |
|                 | subsystem also interfaces with the financial  |    |
|                 | infrastructure and broadly disseminates       |    |
|                 | parking information to other operational      |    |
|                 | centers in the region. Note that the latter   |    |
|                 | functionality may be located in a back        |    |
|                 | office, remote from the parking facility.     |    |
+-----------------+-----------------------------------------------+----+
| Roadway (RS)    | This subsystem includes the equipment         | CR |
|                 | distributed on and along the roadway that     | 23 |
|                 | monitors and controls traffic and monitors    | 90 |
|                 | and manages the roadway itself. Equipment     |    |
|                 | includes traffic detectors, environmental     |    |
|                 | sensors, traffic signals, highway advisory    |    |
|                 | radios, dynamic message signs, CCTV cameras   |    |
|                 | and video image processing systems, grade     |    |
|                 | crossing warning systems, and freeway ramp    |    |
|                 | metering systems. HOV lane management,        |    |
|                 | reversible lane management functions, and     |    |
|                 | barrier systems that control access to        |    |
|                 | transportation infrastructure such as         |    |
|                 | roadways, bridges and tunnels are also        |    |
|                 | supported. This subsystem also provides the   |    |
|                 | capability for environmental monitoring       |    |
|                 | including sensors that measure road           |    |
|                 | conditions, surface weather, and vehicle      |    |
|                 | emissions. In adverse conditions, automated   |    |
|                 | systems can be used to apply anti-icing       |    |
|                 | materials, disperse fog, etc. Work zone       |    |
|                 | systems including work zone surveillance,     |    |
|                 | traffic control, driver warning, and work     |    |
|                 | crew safety systems are also included. To     |    |
|                 | enhance security, safeguard systems such as   |    |
|                 | blast shields, exhaust systems and other      |    |
|                 | automated and remotely controlled systems to  |    |
|                 | protect transportation infrastructure is also |    |
|                 | provided. In advanced implementations, this   |    |
|                 | subsystem supports automated vehicle safety   |    |
|                 | systems by safely controlling access to and   |    |
|                 | egress from an Automated Highway System       |    |
|                 | through monitoring of, and communications     |    |
|                 | with, AHS vehicles. Intersection collision    |    |
|                 | avoidance functions are provided by           |    |
|                 | determining the probability of a collision in |    |
|                 | the intersection and sending appropriate      |    |
|                 | warnings and/or control actions to the        |    |
|                 | approaching vehicles.                         |    |
+-----------------+-----------------------------------------------+----+
| Toll            | The Toll Administration Subsystem provides    |    |
| Administration  | general payment administration capabilities   |    |
| (TAS)           | and supports the electronic transfer of       |    |
|                 | authenticated funds from the customer to the  |    |
|                 | transportation system operator. This          |    |
|                 | subsystem supports traveler enrollment and    |    |
|                 | collection of both pre-payment and            |    |
|                 | post-payment transportation fees in           |    |
|                 | coordination with the existing, and evolving  |    |
|                 | financial infrastructure supporting           |    |
|                 | electronic payment transactions. The system   |    |
|                 | may establish and administer escrow accounts  |    |
|                 | depending on the clearinghouse scheme and the |    |
|                 | type of payments involved. This subsystem     |    |
|                 | posts a transaction to the customer account   |    |
|                 | and generates a bill (for post-payment        |    |
|                 | accounts), debits an escrow account, or       |    |
|                 | interfaces to the financial infrastructure to |    |
|                 | debit a customer designated account. It       |    |
|                 | supports communications with the Toll         |    |
|                 | Collection Subsystem to support fee           |    |
|                 | collection operations. The subsystem also     |    |
|                 | sets and administers the pricing structures   |    |
|                 | and includes the capability to implement      |    |
|                 | road-pricing policies in coordination with    |    |
|                 | the Traffic Management Subsystem. The         |    |
|                 | electronic financial transactions in which    |    |
|                 | this subsystem is an intermediary between the |    |
|                 | customer and the financial infrastructure     |    |
|                 | shall be cryptographically protected and      |    |
|                 | authenticated to preserve privacy and ensure  |    |
|                 | authenticity and auditability.                |    |
+-----------------+-----------------------------------------------+----+
| Toll Collection | The Toll Collection Subsystem provides the    | CR |
| (TCS)           | capability for vehicle operators to pay tolls | 23 |
|                 | without stopping their vehicles using locally | 90 |
|                 | determined pricing structures and includes    |    |
|                 | the capability to implement various variable  |    |
|                 | road pricing policies. Each transaction is    |    |
|                 | accompanied by feedback to the customer       |    |
|                 | indicating the general status of the customer |    |
|                 | account. A record of the transactions is      |    |
|                 | provided to the Toll Administration Subsystem |    |
|                 | for reconciliation and so that the customer   |    |
|                 | can periodically receive a detailed record of |    |
|                 | the transactions.                             |    |
+-----------------+-----------------------------------------------+----+
| Trade           | These agencies include U.S. domestic and      |    |
| Regulatory      | foreign governmental agencies responsible for |    |
| Agencies        | the regulation of trade, and the enforcement  |    |
|                 | of customs and immigration laws. These        |    |
|                 | agencies include U.S. Customs, the U.S.       |    |
|                 | Immigration and Naturalization Service (INS), |    |
|                 | and their counterparts in Canada and Mexico.  |    |
|                 | They may also include secondary trade         |    |
|                 | agencies (e.g., U.S. Food and Drug            |    |
|                 | Administration, U.S. Department of            |    |
|                 | Agriculture, other USDOT departments, etc.),  |    |
|                 | and agencies from other trading nations.      |    |
+-----------------+-----------------------------------------------+----+
| Traveler Card   | This terminator represents the entity that    |    |
|                 | enables the actual transfer of electronic     |    |
|                 | information from the user of a service (i.e., |    |
|                 | a traveler) to the provider of the service.   |    |
|                 | This may include the transfer of funds        |    |
|                 | through means of an electronic payment        |    |
|                 | instrument. The device, like a smart card,    |    |
|                 | may also hold and update the traveler\'s      |    |
|                 | information such as personal profiles or trip |    |
|                 | histories.                                    |    |
+-----------------+-----------------------------------------------+----+

**Table 4** presents the definitions for equipment packages. Unless
otherwise indicated, all definitions are from National ITS Architecture
Version 5.0 \[Reference 4\]. Italics indicate that the equipment package
currently falls outside the scope of CVISN Level 1 but is part of
systems that support commercial vehicle operations; if the equipment
package name is also underlined, it is a candidate for inclusion in
future enhancements of CVISN. This table was added to this document via
CR 2535.

[]{#table4 .anchor}**Table 4. Equipment Package Descriptions.**

+-----------------+-----------------------------------------------+----+
| Equipment       |                                               |    |
| Package         |                                               |    |
| Descriptions    |                                               |    |
+=================+===============================================+====+
| **SUBSYSTEM**   | **Updated Description**                       | ** |
|                 |                                               | CR |
| **Equipment     |                                               | \# |
| Package**       |                                               | ** |
+-----------------+-----------------------------------------------+----+
| **CVAS**        |                                               |    |
+-----------------+-----------------------------------------------+----+
| Credentials and | This equipment package provides               | CR |
| Taxes           | administrative capabilities for commercial    | 23 |
| Administration  | vehicle operations including database         | 90 |
|                 | management and administrator-to-roadside and  |    |
|                 | administrator-to-administrator interfaces.    |    |
|                 | For example, this equipment package would     |    |
|                 | manage the electronic credentials database    |    |
|                 | for a state, perform reconciliation of        |    |
|                 | mileage and fuel taxes (possibly post trip),  |    |
|                 | and interface with roadsides performing       |    |
|                 | credential checks. This equipment package     |    |
|                 | communicates with similar packages in other   |    |
|                 | CVAS locations to exchange credentials        |    |
|                 | database information. Example locations would |    |
|                 | be state agency or regional offices that are  |    |
|                 | involved with commercial vehicle operations.  |    |
|                 | This equipment package also exchanges hazmat  |    |
|                 | route restrictions information, and provides  |    |
|                 | a clearinghouse for this information that     |    |
|                 | then can share the information with Map       |    |
|                 | Update Providers, Fleet and Freight           |    |
|                 | Management subsystems and Information Service |    |
|                 | Providers.                                    |    |
+-----------------+-----------------------------------------------+----+
| CV Data         | This equipment package collects and stores    |    |
| Collection      | commercial vehicle information that is        |    |
|                 | collected in the course of Commercial Vehicle |    |
|                 | Administration Subsystem operations. This     |    |
|                 | data can be used directly by operations       |    |
|                 | personnel or it can be made available to      |    |
|                 | other data users and archives in the region.  |    |
+-----------------+-----------------------------------------------+----+
| CV Information  | This equipment package supports the exchange  |    |
| Exchange        | of safety and credentials data among          |    |
|                 | jurisdiction. The package also supports the   |    |
|                 | exchange of safety and credentials data       |    |
|                 | between agencies (for example, an             |    |
|                 | administrative center and the roadside check  |    |
|                 | facilities) within a single jurisdiction.     |    |
|                 | Data are collected from multiple              |    |
|                 | authoritative sources and packaged into       |    |
|                 | snapshots (top-level summary and critical     |    |
|                 | status information) and profiles (detailed    |    |
|                 | and historical data).                         |    |
+-----------------+-----------------------------------------------+----+
| CV Safety       | This equipment package augments the           |    |
| Administration  | Credentials and Taxes Administration          |    |
|                 | equipment package with safety data. This      |    |
|                 | package ensures that safety criteria are      |    |
|                 | available for automated roadside safety       |    |
|                 | checks. It supports the collection and review |    |
|                 | of carrier safety data and determines the     |    |
|                 | carrier safety rating.                        |    |
+-----------------+-----------------------------------------------+----+
| International   | This equipment package is used by government  |    |
| CV              | agencies such as customs and immigration,     |    |
| Administration  | carriers, and service providers (e.g.,        |    |
|                 | brokers) to generate and process the entry    |    |
|                 | documentation necessary to obtain release of  |    |
|                 | vehicle, cargo, and driver across and         |    |
|                 | international border, report the results of   |    |
|                 | the crossing event, and handle duty fee       |    |
|                 | processing.                                   |    |
+-----------------+-----------------------------------------------+----+
|                 |                                               |    |
+-----------------+-----------------------------------------------+----+
| **CVCS**        |                                               |    |
+-----------------+-----------------------------------------------+----+
| Citation and    | The equipment package documents violations    |    |
| Accident        | and forwards the information to the           |    |
| Electronic      | Commercial Vehicle Administration Subsystem   |    |
| Recording       | for processing as part of the normal          |    |
|                 | credentials processing package.               |    |
+-----------------+-----------------------------------------------+----+
| International   | This equipment package is used by government  |    |
| Border Crossing | agencies such as customs and immigration to   |    |
|                 | check compliance with import/export and       |    |
|                 | immigration regulations to allow release of   |    |
|                 | cargo, vehicle, and driver across an          |    |
|                 | international border.                         |    |
+-----------------+-----------------------------------------------+----+
| Roadside        | This equipment package provides the           |    |
| Electronic      | Commercial Vehicle Check Subsystem the        |    |
| Screening       | capabilities for two-way communication with   |    |
|                 | approaching properly equipped commercial      |    |
|                 | vehicles at mainline speeds, reading tags for |    |
|                 | automated vehicle identification and          |    |
|                 | credential checking. There will be a          |    |
|                 | capability to appropriately screen all        |    |
|                 | vehicles, not just those that are equipped.   |    |
|                 | This equipment package shall be able to       |    |
|                 | process the data from the commercial vehicles |    |
|                 | along with accessed database information to   |    |
|                 | determine whether a pull-in message is needed |    |
|                 | or to generate random pull-in messages with   |    |
|                 | provisions for facility operators and         |    |
|                 | enforcement officials to have manual override |    |
|                 | capabilities. Support shall be provided to    |    |
|                 | both interstate and intrastate carriers.      |    |
+-----------------+-----------------------------------------------+----+
| *[Roadside      | This equipment package monitors roadside      | CR |
| HAZMAT          | remote sensing sensor data deployed to        | 23 |
| Detectio        | collect physical characteristics of security  | 90 |
| n]{.underline}* | sensitive materials. It assesses the          |    |
|                 | likelihood of the presence of security        |    |
|                 | sensitive HAZMAT materials based on remote    |    |
|                 | sensed data as well as other physical         |    |
|                 | information acquired about the CV. It then    |    |
|                 | determines if any detected HAZMAT is          |    |
|                 | authorized. If unauthorized HAZMAT material   |    |
|                 | is detected then it messages the Commercial   |    |
|                 | Vehicle Driver to pull-in. The equipment      |    |
|                 | package may also issue a message to the       |    |
|                 | Emergency Management (Police Dispatch)        |    |
|                 | function with jurisdiction over the location  |    |
|                 | of the incident that the event has occurred   |    |
|                 | including: the location of the incident, and  |    |
|                 | current location of the commercial vehicle    |    |
|                 | and a timestamp, Vehicle ID, Carrier ID,      |    |
|                 | Driver ID, CV Credentials information, HAZMAT |    |
|                 | material or category detected and expected    |    |
|                 | cargo manifest (if known). The CVCS may issue |    |
|                 | a similar message to the TMS agency(ies) with |    |
|                 | jurisdiction over the region of the incident, |    |
|                 | as well as to the CVAS and then to the FMS    |    |
|                 | which manages the vehicle (does not need to   |    |
|                 | be real-time). This might be used to disable  |    |
|                 | the vehicle.                                  |    |
+-----------------+-----------------------------------------------+----+
| Roadside Safety | This equipment package provides the           |    |
| and Security    | Commercial Vehicle Check Subsystem the        |    |
| Inspection      | capabilities for operators to automate the    |    |
|                 | roadside safety inspection process including  |    |
|                 | the support of use of hand held devices to    |    |
|                 | rapidly inspect the vehicle and driver. In    |    |
|                 | addition this equipment package provides the  |    |
|                 | Roadside Check Subsystem the capabilities for |    |
|                 | operators to automate the roadside safety     |    |
|                 | inspection process including the support of   |    |
|                 | automated mainline speed reading of on-board  |    |
|                 | safety data to rapidly screen the vehicle and |    |
|                 | driver. This equipment package shall also     |    |
|                 | provide the capabilities to collect, store,   |    |
|                 | maintain, and provide safety data and access  |    |
|                 | historical safety data after receiving        |    |
|                 | identification from vehicles at mainline      |    |
|                 | speeds or while stopped at the roadside.      |    |
|                 | Results of screening and summary safety       |    |
|                 | inspection can be written back onto the tag.  |    |
|                 | The capabilities to process safety data and   |    |
|                 | issue pull-in messages or provide warnings to |    |
|                 | the driver, carrier, and enforcement agencies |    |
|                 | shall be provided. These capabilities have a  |    |
|                 | prerequisite of the Roadside Electronic       |    |
|                 | Screening equipment package and shall be      |    |
|                 | provided primarily through the utilization of |    |
|                 | an additional safety database. Since a        |    |
|                 | vehicle may cross jurisdiction boundaries     |    |
|                 | during a trip, this equipment package         |    |
|                 | supports the concept of a last clearance      |    |
|                 | event record (aka trip ticket) carried on the |    |
|                 | vehicle s tag. The last clearance event       |    |
|                 | record reflects the results of the roadside   |    |
|                 | verification action. For example, if the      |    |
|                 | vehicle is pulled over in State A and         |    |
|                 | undergoes credential, weight, and safety      |    |
|                 | checks, the results of the clearance process  |    |
|                 | are written to the vehicle s tag. If the      |    |
|                 | vehicle continues the trip and passes a       |    |
|                 | roadside station in State B, the State B      |    |
|                 | station has access to the results of the      |    |
|                 | previous pull-in because it can read the last |    |
|                 | clearance event record written by the State A |    |
|                 | roadside station.                             |    |
+-----------------+-----------------------------------------------+----+
| *Roadside WIM*  | This equipment package allows for roadside    |    |
|                 | high speed weigh in motion. This package can  |    |
|                 | be fixed to a location or mobile. It can      |    |
|                 | include an interface to the credential check  |    |
|                 | package and augment electronic credentials    |    |
|                 | check with electronic weight check or it can  |    |
|                 | be a stand alone package with display.        |    |
+-----------------+-----------------------------------------------+----+
|                 | []{.mark}                                     | [  |
|                 |                                               | ]{ |
|                 |                                               | .m |
|                 |                                               | ar |
|                 |                                               | k} |
+-----------------+-----------------------------------------------+----+
| **CVSAg (CVS)** |                                               |    |
+-----------------+-----------------------------------------------+----+
| *[On-board      | This equipment package provides the           | CR |
| Cargo           | Commercial Vehicle Subsystem the capability   | 23 |
| Monitorin       | to monitor both interstate and intrastate     | 90 |
| g]{.underline}* | cargo safety and security such that           |    |
|                 | enforcement and HAZMAT response teams can be  |    |
|                 | provided with timely and accurate             |    |
|                 | information. In addition, this package        |    |
|                 | provides security alerts in the case of       |    |
|                 | tampering or other cargo security breaches.   |    |
|                 | This includes only the equipment on board the |    |
|                 | cargo container such as a communication       |    |
|                 | device, possibly the addition of a cell-based |    |
|                 | radio, and equipment for the processing and   |    |
|                 | storage of cargo material. This can also      |    |
|                 | include optional sensors for temperature,     |    |
|                 | pressure, load leveling, or acceleration      |    |
|                 | depending upon the items monitored. It is     |    |
|                 | already expected that the cargo location      |    |
|                 | devices such as GPS equipment and an          |    |
|                 | integration processor already exist. These    |    |
|                 | items are presented as part of the On-board   |    |
|                 | Trip Monitoring equipment package.            |    |
+-----------------+-----------------------------------------------+----+
| On-board CV     | This equipment package provides the           | CR |
| Electronic Data | Commercial Vehicle Subsystem the capability   | 23 |
|                 | for two-way data exchange between the vehicle | 90 |
|                 | and the roadside facility with the            |    |
|                 | transmission of information such as status of |    |
|                 | driver, vehicle, and carrier IDs and cargo    |    |
|                 | information. The driver, vehicle and carrier  |    |
|                 | are identified via the tag so that actual     |    |
|                 | weight from roadside mainline weigh-in-motion |    |
|                 | may be checked. This includes only the        |    |
|                 | equipment on the commercial vehicle including |    |
|                 | a processor/tag for identification,           |    |
|                 | especially a HAZMAT identification. The       |    |
|                 | actual reading and processing required for    |    |
|                 | the credential checking and weigh-in-motion   |    |
|                 | will be performed by the roadside.            |    |
+-----------------+-----------------------------------------------+----+
| *[On-board CV   | This equipment package provides the           | CR |
| Safety and      | Commercial Vehicle Subsystem the capability   | 23 |
| Securit         | to collect and process on board vehicle and   | 90 |
| y]{.underline}* | driver safety and security information to     |    |
|                 | monitor the safety and security status. This  |    |
|                 | equipment package also supplies this          |    |
|                 | information to the roadside facilities both   |    |
|                 | at mainline speeds and while stopped for      |    |
|                 | inspections. The capability to alert the      |    |
|                 | commercial vehicle driver whenever there is a |    |
|                 | critical safety or security problem or        |    |
|                 | potential emergency shall also be provided.   |    |
|                 | These capabilities include only the equipment |    |
|                 | on the commercial vehicle including the       |    |
|                 | sensors and processors to monitor the vehicle |    |
|                 | and driver with the information stored on the |    |
|                 | vehicle. When the information is transmitted  |    |
|                 | to the roadside facility or after the trip,   |    |
|                 | it will utilize the communication devices     |    |
|                 | already in place. The package will also       |    |
|                 | support onboard driver safety log maintenance |    |
|                 | and checking.                                 |    |
+-----------------+-----------------------------------------------+----+
| *[On-board      | This equipment package monitors the identity  | CR |
| Driver          | of the commercial vehicle driver and compares | 23 |
| Authenticatio   | it with the planned drivers for the           | 90 |
| n]{.underline}* | commercial vehicle. Any change in driver is   |    |
|                 | sent to the Fleet and Freight Management      |    |
|                 | Subsystem. Notification of any unexpected     |    |
|                 | drivers will also be send to the Fleet and    |    |
|                 | Freight Management Subsystem which, in turn   |    |
|                 | may send a disable vehicle command back to    |    |
|                 | this equipment package to cause the vehicle   |    |
|                 | to stop. On receipt of a disable vehicle      |    |
|                 | message from the Fleet and Freight Management |    |
|                 | Subsystem or on detection of an unauthorized  |    |
|                 | driver, the equipment package will safety     |    |
|                 | disable the CV.                               |    |
+-----------------+-----------------------------------------------+----+
| *On-board Trip  | This equipment package provides the           | CR |
| Monitoring*     | capabilities to support fleet management with | 23 |
|                 | automatic vehicle location and automated      | 90 |
|                 | mileage and fuel reporting and auditing. In   |    |
|                 | addition, this equipment is used to monitor   |    |
|                 | the planned route and notify the Fleet and    |    |
|                 | Freight Management Subsystem of any           |    |
|                 | deviations. This package may also record      |    |
|                 | other special events resulting from           |    |
|                 | communication with roadside equipment. This   |    |
|                 | includes only the equipment on board the      |    |
|                 | vehicle to support this function including    |    |
|                 | the vehicle location devices such as GPS      |    |
|                 | equipment, communication interfaces, a        |    |
|                 | processor to record trip length, and the      |    |
|                 | sensors/actuators/interfaces necessary to     |    |
|                 | record mileage and fuel usage.                |    |
+-----------------+-----------------------------------------------+----+
|                 |                                               |    |
+-----------------+-----------------------------------------------+----+
| **CVSAg (VS)**  |                                               |    |
+-----------------+-----------------------------------------------+----+
| *[Vehicle       | This equipment package determines current     |    |
| Location        | location information and provides this        |    |
| Determinatio    | information to other equipment packages that  |    |
| n]{.underline}* | use the location information to provide       |    |
|                 | various ITS services.                         |    |
+-----------------+-----------------------------------------------+----+
| *Vehicle Mayday | This equipment package shall provide the      |    |
| Interface*      | capability for an in-vehicle manually         |    |
|                 | initiated distress signal with cancel a prior |    |
|                 | issued manual request for help feature. This  |    |
|                 | capability shall include automatically        |    |
|                 | identifying that a collision had occurred     |    |
|                 | using equipment such as collision detection   |    |
|                 | sensors with interface to mayday type         |    |
|                 | equipment that would automatically detect     |    |
|                 | vehicle problems and for some cases,          |    |
|                 | automatically send appropriate distress       |    |
|                 | signals to the Emergency Management           |    |
|                 | Subsystem.                                    |    |
+-----------------+-----------------------------------------------+----+
| *Vehicle Probe  | This equipment package includes capabilities  |    |
| Support*        | for the probe vehicle to identify its         |    |
|                 | location, measure traffic conditions such as  |    |
|                 | link travel time and speed and possibly       |    |
|                 | environmental hazards such as icy road        |    |
|                 | conditions, and transmit these data to either |    |
|                 | the ISP or TMC (Traffic Management Center).   |    |
+-----------------+-----------------------------------------------+----+
| *Vehicle        | This equipment package shall provide the      |    |
| Toll/Parking    | capability for vehicle operators to pay toll  |    |
| Interface*      | without stopping their vehicles and pay for   |    |
|                 | parking without the use of cash. These        |    |
|                 | capabilities shall be provided through the    |    |
|                 | use of equipment such as an active tag        |    |
|                 | interface and debit/credit card interface.    |    |
+-----------------+-----------------------------------------------+----+
|                 |                                               |    |
+-----------------+-----------------------------------------------+----+
| **FMS**         |                                               |    |
+-----------------+-----------------------------------------------+----+
| *[Commercial    | This equipment package provides for the       | CR |
| Vehicle and     | security of the commercial vehicle and the    | 23 |
| Freight         | freight that it carries by detecting breaches | 90 |
| Securit         | such as seals or locks being broken into by   |    |
| y]{.underline}* | unauthorized personnel and/or any other       |    |
|                 | unauthorized tampering. In addition, this     |    |
|                 | equipment package monitors the commercial     |    |
|                 | vehicle driver and compares it with the       |    |
|                 | planned driver for the vehicle. In a similar  |    |
|                 | manner, the driver and vehicle that have been |    |
|                 | assigned to move freight are monitored and    |    |
|                 | compared with the planned assignment for that |    |
|                 | freight. In all cases, any deviations to the  |    |
|                 | planned assignments and any breach or tamper  |    |
|                 | events are reported to the Emergency          |    |
|                 | Management Subsystem.                         |    |
+-----------------+-----------------------------------------------+----+
| Fleet           | This equipment package provides vehicle       | CR |
| Administration  | tracking, dispatch, and reporting             | 23 |
|                 | capabilities to fleet management center       | 90 |
|                 | personnel. It gathers current road conditions |    |
|                 | and traffic information, prepares vehicle     |    |
|                 | routes, and provides a fleet interface for    |    |
|                 | toll collection. It also provides route plan  |    |
|                 | information for network performance           |    |
|                 | evaluation. As part of the tracking function, |    |
|                 | this equipment package monitors commercial    |    |
|                 | vehicle location, compares it against the     |    |
|                 | known route and notifies the Emergency        |    |
|                 | Management Subsystem and Fleet-Freight        |    |
|                 | Manager of any deviations, including HAZMAT   |    |
|                 | route restriction violations.                 |    |
+-----------------+-----------------------------------------------+----+
| Fleet           | This equipment package provides the Fleet and |    |
| Credentials and | Freight Management Subsystem the capabilities |    |
| Taxes           | to purchase credentials and file trip reports |    |
| Management and  | electronically by the fleet managers, to      |    |
| Reporting       | perform automated enrollment at the roadside  |    |
|                 | facilities, and electronically manage the     |    |
|                 | credentials checking by the roadside          |    |
|                 | commercial vehicle inspectors. The electronic |    |
|                 | purchase shall be performed in accordance     |    |
|                 | with developing standards such that a single  |    |
|                 | integrated system for electronic payments     |    |
|                 | might develop ensuring that deployment across |    |
|                 | multiple agency political boundaries is       |    |
|                 | performed without degradation. Inherent to    |    |
|                 | credential management shall be the management |    |
|                 | of the vehicles, with a prerequisite of the   |    |
|                 | vehicle tracking software from the Fleet      |    |
|                 | Administration equipment package.             |    |
+-----------------+-----------------------------------------------+----+
| Fleet HAZMAT    | This equipment package provides the Fleet and | CR |
| Management      | Freight Management Subsystem the capabilities | 23 |
|                 | to enhance the Fleet Administration equipment | 90 |
|                 | package functions by adding HAZMAT tracking.  |    |
|                 | The additional requirements to perform this   |    |
|                 | function include enhanced processing and      |    |
|                 | enhanced fleet management software. In order  |    |
|                 | to effectively track HAZMAT cargo,            |    |
|                 | communication interfaces to Information       |    |
|                 | Service Providers, and Emergency Management   |    |
|                 | Subsystems shall be provided, including       |    |
|                 | additional communication software.            |    |
+-----------------+-----------------------------------------------+----+
| Fleet           | This equipment package provides the           | CR |
| Maintenance     | capability to use vehicle mileage data to     | 23 |
| Management      | automatically generate preventative           | 90 |
|                 | maintenance schedules for each specific       |    |
|                 | vehicle by utilizing vehicle tracking data    |    |
|                 | from the prerequisite tracking equipment      |    |
|                 | package (Fleet and Freight Management). In    |    |
|                 | addition, capability to automatically ensure  |    |
|                 | that proper service personnel are provided    |    |
|                 | information for maintenance activities and to |    |
|                 | record and verify that maintenance work was   |    |
|                 | performed shall be provided.                  |    |
+-----------------+-----------------------------------------------+----+
| Freight         | This equipment package provides the           | CR |
| Administration  | communication necessary to track              | 23 |
| and Management  | cargo/freight from source to destination via  | 90 |
|                 | links to intermodal freight shippers and      |    |
|                 | depots. There are also communication links to |    |
|                 | cargo routing services. As part of the        |    |
|                 | tracking function, this equipment package     |    |
|                 | monitors cargo/freight location and compares  |    |
|                 | it against the known route and notifies the   |    |
|                 | Emergency Management Subsystem of any         |    |
|                 | deviations.                                   |    |
+-----------------+-----------------------------------------------+----+
| *[Manage CV     | This equipment package collects and stores    | CR |
| Driver          | driver identification records including       | 23 |
| Identificatio   | driver issued PINS and/or individual driver   | 90 |
| n]{.underline}* | biometric measurements. The equipment package |    |
|                 | can also manage the storage on individual CVs |    |
|                 | of driver PINs and/or biometric measurements  |    |
|                 | for drivers authorized to operate the CV.     |    |
|                 | Based on information reported by the          |    |
|                 | commercial vehicle, the equipment package     |    |
|                 | will determine if driver is authorized based  |    |
|                 | on the local driver inventory store, and      |    |
|                 | notify the Commercial Vehicle Manager when an |    |
|                 | unauthorized driver is detected. The          |    |
|                 | Commercial Vehicle Manager may override the   |    |
|                 | disable vehicle action. When an unauthorized  |    |
|                 | driver is detected and the system is not      |    |
|                 | overridden, then the equipment package will   |    |
|                 | issue a message to the CVS to safely disable  |    |
|                 | the vehicle. If an unauthorized CV driver is  |    |
|                 | detected then the equipment package will      |    |
|                 | issue a message to the Emergency Management   |    |
|                 | Police Dispatch function with jurisdiction    |    |
|                 | over the location of the incident that the    |    |
|                 | event has occurred. This message will         |    |
|                 | include: the location of the incident,        |    |
|                 | current location of the CV, Vehicle ID,       |    |
|                 | Carrier ID, Driver ID, CV Credentials         |    |
|                 | information, and expected cargo manifest (if  |    |
|                 | known). Also, the equipment package will      |    |
|                 | issue a message to the TMS agency(ies) with   |    |
|                 | jurisdiction over the region of the incident. |    |
+-----------------+-----------------------------------------------+----+

This Page Intentionally Blank

# CHANGE REQUESTS

## Change Requests Incorporated

This section summarizes the changes incorporated into the CVISN
Architecture since it was aligned with the National ITS and IBC
Architectures as documented in References 1, 2 and 3 prior to the
release of Version 5.0 of the National ITS Architecture \[Reference 4\].

-   **CR 439** -- Discrepancy between CVISN and V4 National ITS
    Architecture.\
    In the following request/response pairs, the National ITS
    Architecture dropped the possibility of a DSRC connection between
    FMS and CVSAg in ITS Architecture Version 4.0. In Baseline V1.0 of
    the CVISN Architecture document, the DSRC connection option was
    retained. This was shown as "X?" in the Std column of Table 1 for
    these flows:

    -   on-board safety request/on-board safety data

    -   trip log request/trip log

    -   on-board vehicle request/on-board vehicle data

> In Version 5.0 of the National ITS Architecture, the discrepancy was
> eliminated. Allowance was made for future standardization of the "trip
> log request", "trip log", "on-board vehicle request", and "on-board
> vehicle data" flows. The flow "trip identification number" was also
> added to the set that may be transmitted via either DSRC or wide area
> wireless, with an option for future standardization. Figure 2--1 and
> Table 1 of the CVISN Architecture Baseline Version 2.0 document have
> been updated to align with Version 5.0 of the National ITS
> Architecture.

-   **CR 654** -- National ITS Architecture 4.0 showed no standard for
    \"tax filing\".\
    In the National ITS Architecture Version 4.0, the architecture flow
    named \"tax filing\" was not mapped to any standard. EDI TS 813,
    Electronic Filing of Tax Return Data, is available to carry fuel tax
    return information and should be shown. In Version 5.0 of the
    National ITS Architecture, "tax filing" is mapped to EDI TS 813, so
    Table 1 in the CVISN Architecture has been updated.

-   **CR 2390** -- Update CVISN Architecture to keep pace with changes
    to the National ITS Architecture (Version 5).\
    The most significant Version 5.0 enhancement is the improvement of
    the coverage of transportation security in the National ITS
    Architecture. These improvements include updates to the physical
    architecture, market packages, logical architecture, and supporting
    documentation. Using ITS to Enhance Transportation Security is
    addressed in the following CVO-related areas: Freight and Commercial
    Vehicle, HAZMAT, Wide Area Alerts, and Transportation
    Infrastructure. In addition, guidance is now offered on ways in
    which ITS can be made more secure.

> The diagram and tables in the CVISN architecture have been updated to
> include National ITS Architecture changes to the items listed below.
> Note that only a few of the items include components that are
> typically associated with any state or federal government systems.
> This could minimize the CVISN impact beyond the architecture level, at
> least for now.
>
> Changes made include adding equipment packages, flows, and
> terminators; updating definitions for subsystems, equipment packages,
> flows, and terminators; updating standards indications; and updating
> interconnection types.
>
> []{.mark}
>
> See Reference 4 for details about what is new in Version 5.0 of the
> National ITS Architecture.

-   **CR 2535** -- Add equipment package descriptions to CVISN
    Architecture document.\
    Baseline V1.0 of the CVISN Architecture document does not include
    descriptions of the equipment packages shown on the CVISN
    Architecture Flow Diagram. To make the document more complete,
    descriptions were added as Table 4.

[]{.mark}

## Change Requests Pending

None.

# REFERENCES

1.  JHU/APL, *ITS/CVO CVISN and National ITS Architecture Alignment*,
    D.1, August 2001. (Delivered via SSD-PL-01-0358, 3 August 2001.)

2.  JHU/APL, *Commercial Vehicle Information Systems and Networks
    (CVISN), International Border Clearance (IBC) and National ITS
    Architecture Alignment*, SSD-POR-02-7349 D.2, December 2001.
    (Delivered via SSD-PL-01-0650, 25 March 2002.)

3.  JHU/APL, *Commercial Vehicle Information Systems and Networks
    (CVISN) Architecture*, SSD-POR-02-7364 V1.0, May 2002. (Delivered
    via SSD-PL-02-0307, 22 August 2002.)

4.  The US DOT Joint Program Office, *The National ITS Architecture: a
    Framework for Integrated Transportation into the 21^st^ Century*, V
    5.0, 2003, maintained by Iteris. Available in CD format or on the
    WWW at <http://www.iteris.com/itsarch/>.

[]{#table6 .anchor}This Page Intentionally Blank