Intelligent Transportation Systems/

Commercial Vehicle Operations

(ITS/CVO)

Interoperability Test Project

February 2001

Provide comments to:

*Michael T. Kane, JHU/APL*

Mike.Kane@jhuapl.edu

Phone: (240) 228-8746

FAX: (240) 228-6149

If there are any comments or questions about this document, please
address them to:

Johns Hopkins University Applied Physics Laboratory

11100 Johns Hopkins Road

Laurel, MD 20723-6099

Attention: Michael T. Kane (Building 24-E245)

Phone: (240) 228-8746

FAX: (240) 228-6149

E-Mail: Mike.Kane@jhuapl.edu

**Intelligent Transportation Systems/Commercial Vehicle Operations
(ITS/CVO)**

**Interoperability Test Project - Testing Web-based Credential
Applications for CVISN Interoperability**

**Table of Contents**

# 

[**Background 1**](#background)

[Recommendation 1](#recommendation)

[Document Organization 2](#document-organization)

[CVISN Interoperability Defined 3](#cvisn-interoperability-defined)

[IRP Credentialing Process -- Overview
6](#irp-credentialing-process-overview)

[IFTA Credentialing Process -- Overview
7](#ifta-credentialing-process-overview)

[Virginia WebCat Approach 9](#virginia-webcat-approach)

[Kentucky Web IRP Approach 13](#kentucky-web-irp-approach)

[Review of Interoperability Testing for CAT/CI Applications
15](#review-of-interoperability-testing-for-catci-applications)

[End to End Interface Tests 16](#end-to-end-interface-tests)

[Testing Web Applications 20](#testing-web-applications)

[CVISN Interoperability Checklist for Web-based Credential Applications
22](#cvisn-interoperability-checklist-for-web-based-credential-applications)

[References 26](#references)

Appendices:

[Appendix A -- Virginia WebCAT Screen Images
A-1](#appendix-a-virginia-webcat-screen-images)

[Appendix B -- Kentucky Web IRP Screen Images
B-1](#appendix-b-kentucky-web-irp-screen-images)

[Appendix C - End-to-End Web-based Test Procedures
C-1](#appendix-c---end-to-end-web-based-test-procedures)

**Testing Web-based Credential Applications for CVISN Interoperability**

# 

# Background

Intelligent Transportation Systems/Commercial Vehicle Operations
(ITS/CVO) interoperability testing involves verification of interfaces,
data flow and data usage between systems in the Commercial Vehicle
Information Systems and Networks (CVISN) architecture. Numerous tests
have been developed for interoperability testing of credential
administration applications based on Electronic Data Interchange (EDI)
transaction flow between the carrier and the State credential
administration system. The "pair-wise" tests examine the EDI interface
between a Carrier Automated Transaction (CAT) subsystem and the State
Credentialing Interface (CI) subsystem. "End-to-end" tests concentrate
on the application processes and overall results of the data exchange
across many systems. In end-to-end tests, the credential data flow is
from the carrier application, through the State legacy systems, to
SAFER/CVIEW, and finally to the roadside screening and inspections
systems.

Advances in technology and the increased use of the World Wide Web have
led to an alternative approach for the carrier-to-state interface for
credentials applications. Many states are interested in Web-based
credential systems and FMCSA has endorsed this as an acceptable approach
within the CVISN architecture guidelines. To accommodate the changing
technology, JHU/APL was tasked with proposing a testing strategy and
test procedures for Web-based credential processes that could be
incorporated into the CVISN Interoperability Test Suite Package. The
prototype Web-based credentialing systems implemented in the States of
Kentucky and Virginia were examined in order to aid in the development
of the CVISN Web-based testing strategy.

# Recommendation

The current CVISN Interoperability Test Suite Package \[Reference 2\]
provides pair-wise tests for the credentials process that focuses on the
EDI interface between the carrier and State. These tests are not
applicable to Web-based processes where the interface is between a Web
browser and a Web server. The proposed CVISN Web-based testing strategy
focuses on system processes and results of data exchange and not the
individual interfaces between systems. The current CVISN
interoperability end-to-end tests are directly applicable to this
strategy with minimal changes to the procedures and language to
customize them for Web approach. For the Web-based end-to-end tests, the
"EDI correctness" criteria is replaced with an examination of the forms,
invoices and credentials displayed on the browser. A Web application
functionality checklist is added as a first step in the test procedure
in order to document the examination of the displays and verify use of
standard identifiers and required data fields in the credential
applications.

The newly revised Web-based test procedures are included in Appendix C
for FMCSA review. Upon approval of FMCSA, it is recommended that these
procedures be added to the next update of the CVISN Interoperability
Test Suite Package Part 2, Test Cases and Procedures.

# Document Organization

This purpose of this document is to summarize and present the following
information:

-   Interoperability definitions

-   IRP and IFTA credentialing processes

-   Virginia and Kentucky web approaches

-   Example CAT/CI End-to-end test procedures

-   Generic web testing

-   Checklist for Web-based credential tests

-   Screen captures of the Virginia and Kentucky Web sites for CVO
    credentials (Appendices A and B)

-   Recommended CVISN end-to-end interoperability tests for Web-based
    credential applications (Appendix C)

Any questions or comments may be directed to Michael T. Kane at
240-228-8746 or e-mail at mike.kane@jhuapl.edu.

# CVISN Interoperability Defined

JHU/APL has traditionally cooperated with States to conduct
"interoperability testing." Systems are evaluated in terms of
conformance to standards and protocols recommended as part of the CVISN
operational concepts and architecture. CVISN guidelines are provided in
the five-volume CVISN Operational and Architectural Compatibility
Handbook (COACH) \[Reference 1\]. The relevant high-level definitions
are excerpted in the text box below.

Previous interoperability testing efforts have focused on the
computer-to-computer interfaces that transport credential application
and acknowledgement messaging. A typical architecture had carriers
employ a Carrier Automated Transaction (CAT) software application to
provide the user interface. The CAT communicated with the State's
Credentialing Interface (CI) using ANSI X12 EDI transactions. The
evaluation portion of the tests typically involved visual inspection of
the resulting EDI transactions to determine compliance with the
standards.

These tests do not translate well to the emerging Web-based
credentialing applications such as the Virginia WebCAT and Kentucky Web
IRP prototypes. In both of these cases, computer-to-computer traffic
utilizes custom data formats. This necessitates some additions and
modifications to the CVISN test procedures.

The COACH documents provide some general Web implementation conformance
recommendations:

The COACH goes on to specify some additional points related specifically
to credential administration:

***Electronic Credentialing*** is defined as an operational process that
uses software under the applicant's control to send credentials
applications (including fuel tax returns) to the state, and to get
electronic notification of credentials status in return. When feasible,
the credential itself is returned electronically. Electronic payment is
an option associated with electronic credentialing

In addition to the fundamental functions of the credentialing system,
several external interfaces must also be maintained:

# IRP Credentialing Process -- Overview

The International Registration Plan (IRP) and the International Fuel Tax
Agreement (IFTA) credentials generate the most transaction traffic. IRP
is a method of registering fleets of vehicles that travel in two or more
member jurisdictions. Motor carriers that qualify for IRP must register
fleets of vehicles in their base or home jurisdiction. A fleet, for IRP
purposes, is comprised of one or more vehicles that pay registration
fees in multiple states. The base jurisdiction collects the appropriate
registration fees and distributes them to the other jurisdictions in
which the carrier requested apportioned registration. Carriers are
issued one cab card (registration) and license plates(s) for each
vehicle in the fleet. Registration fees are determined by the type of
operation (private, for-hire, or rental) and in general by:

-   The percentage of miles traveled in each member jurisdiction

-   The registered gross weight of each vehicle

-   The number of vehicles in the carrier's fleet.

Many jurisdictions have additional conditions in their rate-calculating
algorithms. There are numerous fields on IRP application forms that
apply to various subsets of the total jurisdictions. Fees can depend on
such diverse attributes as year and make of a vehicle, vehicle type,
fuel type, manufacturers' suggested retail price, etc. Jurisdictions
must collect adequate information to enable computation of fees for all
other member jurisdictions.

IRP distributes registration revenue among the member jurisdictions.
Each member jurisdiction receives its proportional share of registration
fees for each vehicle registered under the IRP fleet. Vehicles
registered under IRP are considered fully registered, for license plate
purposes, in each jurisdiction that receives registration revenue.

**IRP Summary:**

-   Annual application and fee through base jurisdiction;

-   One registration credential (cab card) and one set of plates per
    vehicle;

-   Cab card lists all jurisdictions and weight for each jurisdiction;

-   Carrier must maintain monthly recaps of individual vehicle mileage
    reports;

-   Fleet is set of vehicles with same jurisdictions and registration
    expiration date;

Reference (4) \[Volume I, EDI Implementation Guide for Transaction Set
286 International Registration Plan (IRP) Credential Transactions- ANSI
ASC X12 Version 4 Release 3,

POR-96-6993 V1.0, March 2001\] describes IRP interfacing functionality
(X12 EDI TS 286 and TS 997). Implementation guides are available on the
JHU/APL CVISN Web Site (<http://www.jhuapl.edu/cvisn/downdocs/#edi>).

# IFTA Credentialing Process -- Overview

IFTA is a fuel tax agreement where motor carriers contact only their
base (home) jurisdiction to license for fuel tax reporting in all IFTA
member jurisdictions. The base jurisdiction issues the carrier a license
and vehicle decals that are valid in all IFTA jurisdictions. No IFTA
jurisdiction may require any additional fuel tax licensing requirements.
The carrier makes quarterly tax reports and payments to its base
jurisdiction covering fleet operations in all IFTA jurisdictions. The
base jurisdiction, in turn, distributes tax payments to the other IFTA
jurisdictions, as appropriate. The base jurisdiction also is responsible
for fuel tax auditing. Generally, in IFTA, only a carrier\'s base
jurisdiction may conduct an audit.

A qualified motor vehicle is a motor vehicle that:

-   Travels in two or more IFTA jurisdictions, and

-   Has a gross weight, registered gross weight, or combined gross
    weight in excess of 26,000 pounds; or

-   Has three or more axles on the power unit regardless of gross
    weight; or

-   Is a bus designed to carry 20 or more passengers.

IFTA requires an annual license and vehicle decals. All IFTA licenses
expire December 31. A copy of your license must be carried in each
qualified vehicle. You will be issued a set of two decals for each
qualified vehicle. One decal is placed on each side of the vehicle,
usually on the doors. Decals also expire December 31.

Carriers licensed for fuel tax reporting are required to make calendar
quarterly fuel tax reports. For IFTA carriers, the reports cover travel
for all qualified vehicles in all IFTA jurisdictions. Reports must be
filed within one month of the close of the quarter. Quarterly reports
must be accompanied by any tax payment that may be due. IFTA carriers
make one payment for all IFTA jurisdictions.

Generally, record keeping for fuel tax reporting is the same as for the
International Registration Plan. You are required to maintain individual
vehicle mileage reports and to summarize these reports monthly. In
addition to keeping the mileage information required by the IRP, you
must maintain information on any fuel purchased from a service station,
and any fuel removed from bulk storage. Complete records are required
for all miles of travel including miles outside of the IFTA
jurisdictions. Records must be maintained for four years.

**IFTA Summary:**

-   Quarterly tax payments to base jurisdiction;

-   Quarterly tax reports must include:

-   Distance records \-- Fleet mileage reports;

-   Fuel receipts \-- Record of fuel purchases;

-   Annual license and vehicle decals.

Reference (5) \[Volume III, EDI Implementation Guide for Transaction Set
286 International Fuel Tax Agreement (IFTA) Credential Transactions,
POR-97-6996 V1.0, March 2001\] describes IFTA interfacing functionality.
X12 EDI TS 286 and TS 997 are used for IFTA registration. Implementation
guides are available on the JHU/APL CVISN Web Site
(<http://www.jhuapl.edu/cvisn/downdocs/#edi>). Guidance for use of TS
813, 826, 150 and 151 for tax filing and tax information exchange is
available through the Federation of Tax Administrators (FTA)
\[http://www.taxadmin.org/\] and the Data Interchange Standards
Association (DISA) \[http://www.disa.org/\].

# Virginia WebCat Approach

To register to use the Virginia WebCAT system, a carrier must already
have an account with IRP, IFTA or Virginia Motor Fuel. Once the account
is verified, the WebCAT database is populated with data from the state
IRP or IFTA application. In Virginia, this is the Vehicle Information
System for Tax Apportionment (VISTA), VISTA/RS and VISTA/TS
respectively.

Once properly registered, WebCAT provides the following capabilities:

IRP transactions:

-   Add a Vehicle to your fleet.

-   Add a Jurisdiction to your fleet.

-   Delete a Vehicle from your fleet.

-   Transfer Plates.

-   Change a Weight.

-   Change a vehicle unit number.

-   Obtain replacement credentials.

-   Renew your fleet.

-   Add a new fleet.

-   View, print and pay invoices.

-   View your fleet list.

IFTA and Virginia Motor Fuel Road Tax Transactions:

-   Submit Tax Reports.

-   Make tax and credential payments.

-   Request licenses and decals.

Other WebCAT Capabilities:

-   Allows you to specify whether you would like to receive your
    credentials by mail, or pick them up at any DMV Customer Service
    Center.

-   Allows you to pay for WebCAT transactions via credit card, ACH debit
    or ACH credit.

-   Allows you to update and edit your profile information.

-   Allows a company\'s administrator to add and delete users for their
    company, and to administer log-on security for company employees.

-   Allows individual users to change their passwords.

-   Maintains a historical record of transactions processed.

-   Allows for transaction reports to be generated.

-   Allows you to search for invoices by vehicle unit number.

-   Allows you to delete stored credit card information at any time.

Interfaces with other state systems and CVISN components:

-   VISTA/RS for IRP processing via a custom interface.

-   VISTA/TS for IFTA processing via a custom interface.

-   CVIEW (planned for early 2001).

When a carrier calls up and completes an IRP screen in the web browser,
an IRP transaction is sent to the web server. Transactions are
accumulated and eventually (average delay is ten minutes) forwarded to
the VISTA/RS system via *ftp* in a custom file format. The transaction
is tagged with a status of "Sent." The Lockheed VISTA/RS generates an
invoice and returns it to the WebCAT system (also using a custom
format). The "Add Vehicle" transaction status is changed to "Invoice
Received." The invoice may be viewed as a summary or sorted by
jurisdiction or vehicle. The carrier may submit payment by ACH or credit
card. An "Invoice Payment" transaction is sent to VISTA/RS. Once
processed by VISTA, the transaction status is changed to indicate the
credential status. The carrier may request that the credential be
mailed, picked up at a DMV Customer Service Center or self-issued from
the carrier's inventory. In the latter case, the credential is E-mailed
from the WebCAT system. The carrier is allowed to print the cab card
(format, etc., must be pre-approved by the state) and expend a license
plate from inventory. A similar arrangement is in place for IFTA decals
and licenses.

The VISTA systems handle the interfacing with the IRP and IFTA
Clearinghouses.

The Virginia WebCAT does not currently forward snapshots to CVIEW. The
plan calls for implementation of this feature by the end of the year.
The WebCAT will send a custom file to CVIEW, as opposed to EDI
transactions. When this is done it will be via a flat file from VISTA to
WebCAT for pass through to CVIEW.

There is currently no mechanism to allow carriers to input large batches
of vehicle data at once. The web page interface is the only method for
entering data into the WebCAT system, one vehicle at a time. There is an
"Add Similar" feature, which preloads screens with data from a previous
vehicle transaction that can then be modified.

The Virginia WebCAT uses Active Server Page (ASP) technology. This
implements all of the application logic on the Web Server. The browser
sees vanilla HTML only without any embedded scripting. This ensures
compatibility with the widest variety and versions of browsers. Since
the client end (i.e., the browser) does not perform any non-standard
processing, automating the test procedures is somewhat easier. On the
other hand, ASP dynamically generates the HTML content sent back to the
browser. This makes it difficult to automate test procedures that depend
on a static view of the web page under test. Additional test automation
code would be required to focus decision logic on a combination of
static page content (e.g., text box headings) and dynamic content (e.g.,
transaction status codes).

In terms of usability, some of the status messages produced by the
WebCAT are difficult to understand. For example, when submitting an "Add
Vehicle" transaction, the resulting item is placed in a category
entitled "Transactions not yet Submitted." The first impulse for the
user is to go back and make sure that they submitted the transaction.
What the message is actually intended to convey is that the operating
software has not yet submitted the transaction to VISTA. This situation
could be improved by rewording some of the messages. There is currently
a mixture of messages, some from the perspective of the user (e.g., you
forgot to enter a VIN) and some from the perspective of the operating
software.

The testing conducted by JHU/APL on the Virginia web site consisted of
walking through the process for an IRP Add Vehicle transaction.
Combinations of valid and invalid data were entered on the add vehicle
transaction page. The application correctly identified invalid or
omitted data once the form was submitted. The Virginia site implements
all application logic at the server side of the transaction. There is no
validation code implemented at the browser side. There are several
drop-down selection boxes where a finite set of valid entries can be
enumerated, thus ensuring valid input with no additional code.

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

### Sample "Add Vehicle" Screen

Add Vehicle transactions are accumulated at the web server and forwarded
to VISTA/RS. Virginia personnel indicated that an average delay of about
ten minutes can be expected for the production system. Our test
transaction was eventually forwarded and an IRP invoice was received
with the applicable fee listed for each jurisdiction specified on the
application. A "Pay Invoice" transaction was prepared with dummy credit
card numbers and submitted. This was the limit of the test environment
-- no actual credential was generated, nor any payment processed.

The process of preparing Web application test procedures for inclusion
in the Test Suite Package (Reference 2) should consist of reusing the
End-to-End test data and cases and replacing the "EDI correctness"
criteria with a similar manual examination of the available application
products, i.e., the forms, invoices and credentials. The scenarios
should focus on Level 1 basics and connectivity to other CVISN
components such as CVIEW, SAFER and the roadside.

Appendix A contains a set of representative screens from the Virginia
WebCAT system. The site also contains an elaborate set of on-line help
screens.

Support for IFTA transactions is similar to the IRP handling. No
hands-on testing was conducted by JHU/APL on the IFTA portion of the
Virginia web site.

# Kentucky Web IRP Approach

Once properly registered, Web IRP provides the following capabilities:

IRP transactions:

-   Fleet Inquiry

-   Add Jurisdiction

-   Fleet Renewal

-   Plate Transfer

-   Add New Fleet

-   Add Vehicle

-   Weight Change

-   Plate Replacement

-   Cab Card Replacement

The Kentucky Web IRP requires a large browser plug-in to function
properly: Oracle JInitiator 1.1.7.18 plug-in, 8,538 KB. The site looks
more like a Java application than a standard HTML Web page.

Testing on the Kentucky site involved browsing test data and
transactions that were already present in the database. No new
transactions could be initiated due to limitations of the test
environment. Nevertheless, the nature of the Web IRP application was
evident. The Kentucky system includes functional descriptions of the
current web page right on the page. This should be very helpful to
inexperienced users. Some of the navigation methods are unfamiliar and
deviate from typical web applications. In some cases the user must
double-click within a table row to move on to the next screen. This
might prove confusing at first to the inexperienced user. On the other
hand, once the navigation conventions are understood it may be more
convenient to double click than to single-click-select and then move the
mouse to a separate button to invoke.

![](media/image2.png){width="5.998611111111111in"
height="5.236805555555556in"}

**Sample Add Vehicle Page for Kentucky Web IRP**

The Virginia and Kentucky implementations are very different in look and
feel. Navigation controls, screen contents, carrier/fleet/vehicle
hierarchy depiction and many other concepts are unique to each state
system. Interoperability test procedures will need to be very general in
describing data entry steps and navigation. Each implementation is
likely to be unique making it difficult to compose step-by-step,
detailed instructions for the tester.

Appendix B contains a set of representative screens from the Kentucky
Web IRP system.

# Review of Interoperability Testing for CAT/CI Applications

The Interoperability Test Suite Package (Reference 2) contains the
following tests related to Credential Administration:

Pairwise:

1.  IRP Add Vehicle

2.  IFTA Renewal

3.  IFTA Quarterly Tax Filing

End-to-End:

1.  Carrier Adds Vehicle (IRP Credential)

2.  Carrier Adds Jurisdiction (IRP Supplemental)

3.  Carrier renews IRP Credential

4.  Carrier renews IFTA Credential

5.  Carrier Submits IFTA Quarterly Tax Filing

The tests are characterized as follows in Reference 2:

**All tests, test criteria and expected results focus on the ability of
the carrier system to perform the required EDI transactions.**

That is, the tests concentrated on the correct generation and formatting
of standard EDI transactions. Indeed, the subjects of the tests were
normally the TS-286 transactions that were flowing back and forth
between the components of the systems (TS-813, 150, 151 and 826 for IFTA
tax). In a web-based implementation, the flow of information between the
browser (i.e., the user) and the server (i.e., the combined
functionality of both the traditional CAT and CI) takes place in a
unique, proprietary format for each separate implementation. Any testing
must either be customized for each implementation or more likely be
focused on the resulting generation of invoices and credentials that
would have been created in the form of EDI transactions but are now HTML
pages or other similar web display languages (e.g., Adobe Acrobat PDF
files).

Here is an example end-to-end test definition and procedure excerpted
from Reference 2:

# End to End Interface Tests

> For end-to-end tests, the JHU/APL test facility is not involved, and
> all tests are conducted under non-error conditions. The sections that
> follow are organized by operational scenario; in most sections there
> is one test case per scenario. For scenarios with more than one test
> case, a test matrix is provided.

## Scenario ID ETE-01: Carrier Adds Vehicle (IRP Supplemental)

> *Test Configuration and Initial Conditions*

-   JHU/APL Facility Requirements

```{=html}
<!-- -->
```
-   None.

```{=html}
<!-- -->
```
-   User Facility Requirements

```{=html}
<!-- -->
```
-   Communications established between:

1.  The Carrier's Electronic Credentialing System and the State
    Commercial Vehicle (CV) Administration

2.  CV Administration and the State CVIEW System (CVIEW)

3.  CVIEW and SAFER

4.  Roadside Operations and CVIEW

-   Test Roles

```{=html}
<!-- -->
```
-   The key test roles necessary to execute this test include:

```{=html}
<!-- -->
```
-   Master Test Conductor

-   CV Administration

-   Carrier

-   SAFER

-   CVIEW

-   Roadside Operations

-   Test Analyst

```{=html}
<!-- -->
```
-   Initial Conditions

```{=html}
<!-- -->
```
-   An IRP Initial Registration has previously been processed

Test Summary

The Carrier sends an IRP Supplemental Application "Add Vehicle" to the
CV Administration. The CV Administration processes the application and
returns an invoice notice. The Carrier sends the CV Administration
payment information and following receipt of payment information, CV
Administration sends the credential to the Carrier. The CV
Administration sends a vehicle snapshot segment update to CVIEW. CVIEW
sends a vehicle snapshot segment update to SAFER. CVIEW sends updated
vehicle snapshot data to the Roadside Operations system. The Roadside
Operations System receives the vehicle snapshot.

> *Test Purpose*

The objective of this End-to-End test is to ensure the products involved
in IRP credentialing process work together properly. Specifically, the
test will verify the carrier is able to enter an IRP supplemental
application, adding a vehicle to their fleet, and this new addition is
updated in all applicable databases, including the Roadside Operations
computer.

Acceptance Criteria

-   The Carrier receives the credential from the CV Administration that
    adds the vehicle to the Carrier's fleet.

-   CVIEW updates its database with the new information (vehicle
    snapshot segment update).

-   SAFER updates its database with the new information (vehicle
    snapshot segment update).

-   Roadside Operations receives, updates, and displays the new
    information.

Requirements Tested

The test criteria for credentials-related data flows and electronic
screening are based on standards found in COACH Part 5, and reflect
those requirements that are pertinent to this test case. See COACH Part
5 for a detailed cross reference of test cases to requirements tested.

Data Recording/Reduction/Evaluation Procedures

Examination of messages, databases, and displayed screens will show the
successful receipt of and update of information resulting from the
submission of an IRP Supplemental Application. The Test Analyst will
compare the appropriate database updates to the information entered by
the Carrier in step 1, to insure proper transaction sequencing and data
flow during the test.

Procedure

The Carrier, using test case data set 4.01.01 will input the data for
the supplemental application. Note that some steps are starred (). The
Test Analyst will examine these starred steps for conformance with the
CVISN architecture in post-test evaluation. Operator Actions are
indicated in **BOLD** print, whereas, System Actions are not in bold
print.

> Table 0--1.\
> Test 4.01.01: Master Test Conductor Procedure

+-----+-----------------------------------+--------------------+------+
| S   | System or Operator Action         | Master Test        | Pa   |
| tep |                                   | Criteria           | ss/\ |
|     |                                   |                    | Fail |
+=====+===================================+====================+======+
| 1   | **The Carrier operator enters     | None               |      |
|     | supplemental application          |                    |      |
|     | information "Add Vehicle" into    |                    |      |
|     | their electronic credentialing    |                    |      |
|     | system and sends it to the CV     |                    |      |
|     | Administration.**                 |                    |      |
|     |                                   |                    |      |
|     | Record the following information  |                    |      |
|     | for the added vehicle:            |                    |      |
|     |                                   |                    |      |
|     | Vehicle Identification            |                    |      |
|     |                                   |                    |      |
|     | VIN                               |                    |      |
|     | \_\_\_\                           |                    |      |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                    |      |
|     |                                   |                    |      |
|     | State                             |                    |      |
|     | \_\_\_\                           |                    |      |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                    |      |
|     |                                   |                    |      |
|     | Plate                             |                    |      |
|     | \_\_\_\                           |                    |      |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                    |      |
|     |                                   |                    |      |
|     | -   Credentials                   |                    |      |
|     |                                   |                    |      |
|     |     USDOT                         |                    |      |
|     |     \_\_\_\                       |                    |      |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                    |      |
|     |                                   |                    |      |
|     |     Company                       |                    |      |
|     |     Nam                           |                    |      |
|     | e\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                    |      |
|     |                                   |                    |      |
|     |     IRP Account                   |                    |      |
|     |     Number\_\_\_\_\_\_\_\_\_\_\_  |                    |      |
|     |                                   |                    |      |
|     |     IRP Base                      |                    |      |
|     |     St                            |                    |      |
|     | ate\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                    |      |
|     |                                   |                    |      |
|     |     Jurisdictions and weights     |                    |      |
|     |     \_\_\_\_                      |                    |      |
|     | \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                    |      |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                    |      |
|     | \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                    |      |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                    |      |
|     | \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\ |                    |      |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ |                    |      |
+-----+-----------------------------------+--------------------+------+
| 2   | The CV Administration receives    | None               |      |
|     | the application.                  |                    |      |
+-----+-----------------------------------+--------------------+------+
| 3   | The CV Administration sends an    | None               |      |
|     | invoice notice to the Carrier.    |                    |      |
+-----+-----------------------------------+--------------------+------+
| 4   | The Carrier receives the invoice  | None               |      |
|     | notice.                           |                    |      |
+-----+-----------------------------------+--------------------+------+
| 5   | **The Carrier operator inputs and | None               |      |
|     | sends payment info to the CV      |                    |      |
|     | Administration.**                 |                    |      |
+-----+-----------------------------------+--------------------+------+
| 6   | The CV Administration receives    | None               |      |
|     | payment info.                     |                    |      |
+-----+-----------------------------------+--------------------+------+
| 7   | The CV Administration sends a     | None               |      |
|     | credential return to the Carrier. |                    |      |
+-----+-----------------------------------+--------------------+------+
| 8   | The Carrier receives the          | **Verify the       |      |
|     | credential return.                | credential         |      |
|     |                                   | returned is        |      |
|     |                                   | accurate and the   |      |
|     |                                   | vehicle has been   |      |
|     |                                   | added to the       |      |
|     |                                   | correct fleet.**   |      |
+-----+-----------------------------------+--------------------+------+
| 9   | The CV Administration sends a     | None               |      |
|     | vehicle snapshot segment update   |                    |      |
|     | to CVIEW.                         |                    |      |
+-----+-----------------------------------+--------------------+------+
| 10  | CVIEW updates its database.       | None               |      |
+-----+-----------------------------------+--------------------+------+
| 11  | CVIEW sends a snapshot segment    | None               |      |
|     | update to SAFER.                  |                    |      |
+-----+-----------------------------------+--------------------+------+
| 12  | SAFER updates its database        | None               |      |
+-----+-----------------------------------+--------------------+------+
| 13  | CVIEW fulfills subscription to    | None               |      |
|     | the Roadside Operations System    |                    |      |
|     | and sends the vehicle snapshot    |                    |      |
|     | segment update.                   |                    |      |
+-----+-----------------------------------+--------------------+------+
| 14  | Roadside Operations receives the  | **Verify the       |      |
|     | vehicle snapshot.                 | vehicle snapshot   |      |
|     |                                   | sent by CVIEW is   |      |
|     |                                   | correct.**         |      |
|     |                                   |                    |      |
|     |                                   | Note: The          |      |
|     |                                   | information        |      |
|     |                                   | recorded in step 1 |      |
|     |                                   | shall be used to   |      |
|     |                                   | verify the vehicle |      |
|     |                                   | snapshot.          |      |
+-----+-----------------------------------+--------------------+------+

The actions and test criteria can be reused for web-based testing, but
the evaluation must focus on the resulting web pages, credentials and
other products, not on intermediate EDI transactions. In general, the
End-to-End tests already contain criteria based on the results rather
than the intermediate formats. For example, the "Add Vehicle" test shown
above could be applied as is to a web-based credential application that
had a functioning interface to CVIEW. The opposite is true of the
pair-wise tests in the suite, most of which focus almost exclusively on
the format and content of the EDI messages flowing back and forth
between components of the system.

The following end-to-end tests applicable to credentialing exist:

-   Scenario ID ETE-01: Carrier Adds Vehicle (IRP Supplemental)
    ***\[shown above\]***

-   Scenario ID ETE-04: Carrier Adds Jurisdiction (IRP Supplemental)

-   Scenario ID ETE-05: Carrier Renews IRP Credential

-   Scenario ID ETE-06: Carrier Renews IFTA Credential

-   Scenario ID ETE-07: Carrier Submits IFTA Quarterly Tax Filing

# Testing Web Applications 

There are some general methodologies for testing web applications that
may be applicable to CVISN Interoperability Testing. At some point a
distinction will need to be made about what constitutes testing
application functionality and behavior versus testing interoperability.
Many of the criteria listed below should have been included in routine
testing during the development of the applications.

**Common web testing considerations:**

Client side:

1.  Page layout is consistent throughout application

2.  Browser compatibility with at least Netscape and Microsoft Internet
    Explorer

3.  JavaScript code runs free of errors

4.  Links are valid

5.  On screen controls function correctly

Server side:

1.  ASP, CGI, JSP, Oracle technologies generate correct HTML for return
    to browser

2.  Database interface correctly updates back end data

3.  Business transactions work properly

**CVISN-specific testing considerations:**

Application logic:

1.  Flow of information between browser, server, legacy systems and
    CVISN components;

2.  Required application content (e.g., includes all required IRP
    application data items);

3.  Inventory of reusable tests: types of carriers, types of vehicles,
    renewals, name changes, oddball cases, fundamental cases, boundary
    conditions

4.  Functional testing of each transaction using different sets of valid
    data

5.  Reusable cases for regression testing -- comprehensive coverage

JHU/APL toolkit:

1.  Comprehensive starting point: elaborate EDI-based test procedures

2.  TestDirector tool for managing test data and execution

3.  WinRunner tool for automating testing of web applications with large
    amounts of test data and test cases

Interoperability

1.  Legacy System / IRP Clearinghouse interface

2.  Legacy System / IFTA Clearinghouse interface

3.  Legacy System / CVIEW / SAFER interfaces

Testing of web-based credentialing applications will need to focus on
the products visible at the browser interface:

-   Application Forms

-   Invoices

-   Automated Credentials

Intermediate forms of data will be non-standard until and unless new
standards emerge (e.g., an XML-based equivalent of the current EDI
standards). Testing of interoperability of web-based credential
applications with respect to other CVISN components will need to focus
on the end-to-end exchange of data from the browser through the legacy
systems to CVIEW, SAFER and the roadside.

# CVISN Interoperability Checklist for Web-based Credential Applications

The following checklist can be used to arrive at a subjective
interoperability score for a Web-based IRP implementation. The checklist
includes browser compatibility, use of standard identifiers,
availability of IRP fields, presence of IRP functionality, payment
options and connection to CVIEW. Similar checklists are included in
Appendix C for IFTA applications.

> **Checklist: The Web-based credential application process for IRP:**

-   Supports the following browsers:

    \_\_\_\_ Netscape 4

    \_\_\_\_ Internet Explorer 4

    \_\_\_\_ Internet Explorer 5.5

    \_\_\_\_ Other (list in comments)

-   Utilizes recommended primary identifiers in application data fields:

    \_\_\_\_Carrier \-- US DOT \#

    \_\_\_\_Vehicle \-- Vehicle Identification Number (VIN)

    \_\_\_\_Vehicle \-- State & Plate

```{=html}
<!-- -->
```
-   Accurately displays the appropriate credential application form,

    with all necessary data fields present and input validated.

    (list exceptions in comments):

    \_\_\_\_Yes \_\_\_\_No

```{=html}
<!-- -->
```
-   User interface allows standard credential application functions
    appropriate

    for this credential type. For IRP:

    \_\_\_\_ Add vehicle \_\_\_\_ Add fleet

    \_\_\_\_ Delete vehicle \_\_\_\_ Delete fleet

    \_\_\_\_ Modify vehicle \_\_\_\_ Change address

    \_\_\_\_ Change weight group \_\_\_\_ Renew fleet

    \_\_\_\_ Replace credential \_\_\_\_ Transfer plates (add/delete)

    \_\_\_\_ Add jurisdiction \_\_\_\_ Change OEN (Unit Number)

    \_\_\_\_ Delete jurisdiction \_\_\_\_ Request temporary authority

    \_\_\_\_ Modify weight \_\_\_\_ Other (list in comments)

-   Displays Invoice: \_\_\_\_Yes \_\_\_\_No

```{=html}
<!-- -->
```
-   Supports payment by credit card: \_\_\_\_Yes \_\_\_\_No

    or by ACH: \_\_\_\_Yes \_\_\_\_No

    or other means (list in comments): \_\_\_\_Yes \_\_\_\_No

-   End-to-End process forwards snapshot updates to CVIEW: \_\_\_\_Yes
    \_\_\_\_No

## 

-   CVIEW provides credential information to SAFER and Roadside Systems:
    \_\_\_\_Yes \_\_\_\_No

-   

## **Checklist completed for Virginia WebCAT**

-   Supports the following browsers:

    \_ [√]{.underline} \_ Netscape 4

    \_ [√]{.underline} \_ Internet Explorer 4

    \_ [√]{.underline} \_ Internet Explorer 5.5

    \_\_\_\_ Other (list in comments)

-   Utilizes recommended primary identifiers in application data fields:

    \_[√ \_]{.underline}Carrier \-- US DOT \#

    \_ [√]{.underline} \_Vehicle \-- Vehicle Identification Number (VIN)

    \_ [√]{.underline} \_Vehicle \-- State & Plate

```{=html}
<!-- -->
```
-   Accurately displays the appropriate credential application form,

    with all necessary data fields present and input validated.

    (list exceptions in comments):

    \_ [√]{.underline} \_Yes \_\_\_\_No

```{=html}
<!-- -->
```
-   User interface allows standard credential application functions
    appropriate

    for this credential type. For IRP:

    \_ [√]{.underline} \_ Add vehicle \_ [√]{.underline} \_ Add fleet

    \_ [√]{.underline} \_ Delete vehicle \_\_\_\_ Delete fleet

    \_ [√]{.underline} \_ Modify vehicle \_ [√]{.underline} \_ Change
    address

    \_ [√]{.underline} \_ Change weight group \_ [√]{.underline} \_
    Renew fleet

    \_ [√]{.underline} \_ Replace credential \_ [√]{.underline} \_
    Transfer plates (add/delete)

    \_ [√]{.underline} \_ Add jurisdiction \_ [√]{.underline} \_ Change
    OEN (Unit Number)

    \_\_\_\_ Delete jurisdiction \_\_\_\_ Request temporary authority

    \_ [√]{.underline} \_ Modify weight \_\_\_\_ Other (list in
    comments)

-   Displays Invoice: \_ [√ \_]{.underline}Yes \_\_\_\_No

```{=html}
<!-- -->
```
-   Supports payment by credit card: \_ [√ \_]{.underline}Yes \_\_\_\_No

    or by ACH: \_ [√ \_]{.underline}Yes \_\_\_\_No

    or other means (list in comments): \_\_\_\_Yes \_\_\_\_No

-   End-to-End process forwards snapshot updates to CVIEW: \_\_\_\_Yes
    \_\_[√ \_]{.underline}No

## 

-   CVIEW provides credential information to SAFER and Roadside Systems:
    \_\_\_\_Yes \_ [√]{.underline} \_No

## **Checklist completed for Kentucky Web IRP**

-   Supports the following browsers:

    \_\_[√]{.underline}\_ Netscape 4

    \_\_[√]{.underline}\_ Internet Explorer 4

    \_\_[√]{.underline}\_ Internet Explorer 5.5

    \_\_\_\_ Other (list in comments)

-   Utilizes recommended primary identifiers in application data fields:

    \_\_\_\_Carrier \-- US DOT \#

    \_\_[√]{.underline}\_Vehicle \-- Vehicle Identification Number (VIN)

    \_\_[√]{.underline}\_Vehicle \-- State & Plate

```{=html}
<!-- -->
```
-   Accurately displays the appropriate credential application form,

    with all necessary data fields present and input validated.

    (list exceptions in comments):

    \_\_[√]{.underline}\_Yes \_\_\_\_No

```{=html}
<!-- -->
```
-   User interface allows standard credential application functions
    appropriate

    for this credential type. For IRP:

    \_\_[√]{.underline}\_ Add vehicle \_\_[√]{.underline}\_ Add fleet

    \_\_[√]{.underline}\_ Delete vehicle \_\_\_\_ Delete fleet

    \_\_[√]{.underline}\_ Modify vehicle \_ [√]{.underline} \_ Change
    address

    \_ [√]{.underline} \_ Change weight group \_ [√]{.underline} \_
    Renew fleet

    \_\_[√]{.underline}\_ Replace credential \_\_[√]{.underline}\_
    Transfer plates (add/delete)

    \_\_[√]{.underline}\_ Add jurisdiction \_\_\_\_ Change OEN (Unit
    Number)

    \_\_\_\_ Delete jurisdiction \_\_\_\_ Request temporary authority

    \_\_[√\_]{.underline} Modify weight \_\_\_\_ Other (list in
    comments)

-   Displays Invoice: \_\_[√]{.underline}\_Yes \_\_\_\_No

```{=html}
<!-- -->
```
-   Supports payment by credit card: \_\_\_\_Yes \_ [√ \_]{.underline}No

    or by ACH: \_\_\_\_Yes \_ [√ \_]{.underline}No

    or other means (list in comments): \_\_\_\_Yes \_\_\_\_No

-   End-to-End process forwards snapshot updates to CVIEW: \_\_\_\_Yes
    \_\_[√]{.underline}\_No

## 

-   CVIEW provides credential information to SAFER and Roadside Systems:
    \_\_\_\_Yes \_\_[√]{.underline}\_No

An informal examination was conducted using IRP Schedule A (IRP
Application) and Schedule C (Supplemental Application) forms downloaded
from a few state web sites to determine the degree of commonality across
both paper and web implementations of IRP functions. The table below
contains the results of the examination and indicates that differences
are present between one state's implementation and another.

  ------------------------------ ---------- ------- ------- ------- ------- ------- ----- ------- -----
  Source: IRP, Inc. Information  IRP, Inc.                                                         
  Manual,                                                                                         

  Field Definitions, Rev. July   Info Man   WV.     Fl.     In.     Me.     Va.     Va.   Ky.     Ky.
  19, 1999                                                                                        

                                 5/4/1995   Paper   Paper   Paper   Paper   Paper   Web   Paper   Web

  **Schedule A - Original                                                                          
  Application**                                                                                   

  **or Schedule C - Supplemental                                                                   
  Application**                                                                                   

  **CARRIER**                                                                                      

                                                                                                   

  Account Number -- MD12345      IRP        WV      FL      IN      ME      VA      VA    KY      KY

  Fleet -- 001 or 01             IRP        WV      FL      IN      ME      VA      VA    KY      KY

  Name and Address               IRP        WV      FL      IN      ME      VA      VA    KY      KY

  Mailing Address                IRP        WV      FL      IN      ME      VA      VA    KY       

  Number of Months for Fee       IRP        WV      FL                      VA      VA            KY
  Calculation                                                                                     

  Contact Person                 IRP        WV      FL      IN              VA      VA    KY       

  Phone Number                   IRP        WV      FL      IN              VA      VA    KY      KY

  Supplemental Number                       WV                      ME      VA      VA    KY       

  License/Year                              WV              IN              VA      VA    KY       

  FEI or SS#                                WV      FL      IN      ME      VA      VA    KY       

  US DOT Number                                             IN      ME      VA      VA    KY       

                                                                                                   

  **JURISDICTION**                                                                                 

                                                                                                   

  Weight Schedule                IRP        WV              IN      ME      VA      VA    KY      KY

  ** **                                                                                            

  **VEHICLE**                                                                                      

                                                                                                   

  Unit/Equipment Number          IRP        WV      FL      IN      ME      VA      VA    KY      KY

  Wrecker Indicator (Michigan)   IRP                                                               

  Colorado Mileage               IRP                                                              KY 

  Model Year                     IRP        WV      FL      IN      ME      VA      VA    KY      KY

  Model Make                     IRP        WV      FL      IN      ME      VA      VA    KY      KY

  Vehicle Identification Number  IRP        WV      FL      IN      ME      VA      VA    KY      KY

  Vehicle Type                   IRP        WV      FL      IN      ME      VA      VA    KY      KY

  Axels (trucks) / Seats (buses) IRP        WV      FL      IN      ME      VA      VA    KY      KY

  Unladen Weight                 IRP        WV      FL      IN      ME      VA      VA    KY      KY

  Fuel -- G, D, P, O             IRP        WV      FL      IN      ME      VA      VA    KY      KY

  Gross Weight                   IRP        WV      FL      IN      ME      VA      VA    KY       

  Combined Gross Weight          IRP                FL      IN              VA      VA    KY      KY

  Price of Vehicle               IRP        WV      FL      IN      ME      VA      VA    KY      KY 

  Factory List Price             IRP        WV      FL      IN      ME      VA      VA             

  Date of Purchase               IRP        WV      FL      IN      ME      VA      VA    KY      KY 

  Date of Lease                  IRP        WV                      ME      VA      VA            KY

  Name of Lessor/Owner           IRP        WV      FL      IN      ME      VA            KY       

  Horsepower (buses)             IRP        WV                      ME      VA      VA             

  Title Number                   IRP        WV      FL              ME      VA      VA    KY      KY

  Current License (Plate) Number IRP        WV                      ME      VA            KY      KY

  Title Date                                WV                      ME                             

  Own/Lease                                 WV                      ME              VA            KY 

  New/Used                                  WV                      ME                             

  Date First Added to Fleet                 WV                      ME                             

  Vehicle Color                                     FL                      VA      VA             
  ------------------------------ ---------- ------- ------- ------- ------- ------- ----- ------- -----

# References

The version number and publication dates cited here represent the
versions of the documents that were referenced during the writing of
this report. For the most current versions of these and other documents,
visit the CVISN Web site at <http://www.jhuapl.edu/cvisn/> .

1.  CVISN Operational and Architectural Compatibility Handbook (COACH),
    Parts 1 through 5, POR-97-7067 V1.0, August 2000.

2.  Intelligent Transportation Systems / Commercial Vehicle Operations
    (ITS/CVO) Interoperability Test Suite Package, Parts 1 through 4,
    POR-98-7123 D.2, December 2000.

3.  International Registration Plan Information Manual, May 1995.

4.  Volume I, EDI Implementation Guide for Transaction Set 286
    International Registration Plan (IRP) Credential Transactions- ANSI
    ASC X12 Version 4 Release 3, POR-96-6993 V1.0, March 2001.

5.  Volume III, EDI Implementation Guide for Transaction Set 286
    International Fuel Tax Agreement (IFTA) Credential Transactions,
    POR-97-6996 V1.0, March 2001.

6.  CVISN Guide to Credentials Administration, Preliminary P.2, August
    2000.

# Appendix A -- Virginia WebCAT Screen Images

[https://www.dmv.state.va.us/webcat/](https://www.dmv.state.va.us/webcat/%01)

[![](media/image3.png){width="6.760416666666667in"
height="5.395833333333333in"}](https://www.dmv.state.va.us/webcat/%01)

![](media/image1.png){width="6.220138888888889in"
height="5.896527777777778in"}![](media/image4.png){width="6.75in"
height="5.614583333333333in"}

![](media/image5.png){width="2.0729166666666665in" height="2.53125in"}

![](media/image6.png){width="6.65in" height="7.455555555555556in"}

![](media/image7.png){width="6.175694444444445in"
height="5.804861111111111in"}![](media/image8.png){width="6.625in"
height="4.659027777777778in"}

![](media/image9.png){width="6.445833333333334in"
height="4.575in"}![](media/image10.png){width="6.429861111111111in"
height="1.1166666666666667in"}

# Appendix B -- Kentucky Web IRP Screen Images

![](media/image11.png){width="5.999305555555556in"
height="3.1625in"}![](media/image12.png){width="4.385416666666667in"
height="5.760416666666667in"}

![](media/image13.png){width="5.625in" height="4.979166666666667in"}

![](media/image14.png){width="5.997222222222222in"
height="4.5680555555555555in"}![](media/image15.png){width="5.992361111111111in"
height="4.252777777777778in"}

![](media/image16.png){width="5.995833333333334in"
height="5.465972222222222in"}

![](media/image17.png){width="5.995833333333334in"
height="5.465972222222222in"}

![](media/image2.png){width="5.998611111111111in"
height="5.236805555555556in"}

![](media/image18.png){width="5.999305555555556in"
height="4.985416666666667in"}

![](media/image19.png){width="6.498611111111111in"
height="4.545833333333333in"}

# Appendix C - End-to-End Web-based Test Procedures

# 

**5. End to End Interface Tests For Web-based Credentialing
Applications**

For end-to-end tests, the JHU/APL test facility is not involved, and all
tests are conducted under non-error conditions. The sections that follow
are organized by operational scenario; in most sections there is one
test case per scenario. For scenarios with more than one test case, a
test matrix is provided.

Note: The scenario numbering is not consecutive. This was done to
maintain numbering synchronization with the original end-to-end tests
upon which the web tests are based.

## 5.1 Scenario ID WETE-01: Carrier Adds Vehicle (IRP Supplemental)

*Test Configuration and Initial Conditions*

-   JHU/APL Facility Requirements

```{=html}
<!-- -->
```
-   None.

```{=html}
<!-- -->
```
-   User Facility Requirements

```{=html}
<!-- -->
```
-   Communications established between:

1.  The Carrier's Electronic Credentialing System (Web Browser) and the
    State Commercial Vehicle (CV) Administration (Web Server)

2.  CV Administration and the State CVIEW System (CVIEW)

3.  CVIEW and SAFER

4.  Roadside Operations and CVIEW

-   Test Roles

```{=html}
<!-- -->
```
-   The key test roles necessary to execute this test include:

```{=html}
<!-- -->
```
-   Master Test Conductor

-   CV Administration

-   Carrier

-   SAFER

-   CVIEW

-   Roadside Operations

-   Test Analyst

```{=html}
<!-- -->
```
-   Initial Conditions

```{=html}
<!-- -->
```
-   An IRP Initial Registration has previously been processed

### [Test Case 5.01.01, Carrier Adds Vehicle (IRP Supplemental)]{.smallcaps}

Test Summary

The master test conductor or the test analyst completes the checklist
for Web-based credential applications. The Carrier sends an IRP
Supplemental Application "Add Vehicle" to the CV Administration. The CV
Administration processes the application and returns an invoice notice.
The Carrier sends the CV Administration payment information and
following receipt of payment information, CV Administration sends the
credential to the Carrier. The CV Administration sends a vehicle
snapshot segment update to CVIEW. CVIEW sends a vehicle snapshot segment
update to SAFER. CVIEW sends updated vehicle snapshot data to the
Roadside Operations system. The Roadside Operations System receives the
vehicle snapshot.

*Test Purpose*

The objective of this End-to-End test is to ensure the products involved
in IRP credentialing process work together properly. Specifically, the
test will verify the carrier is able to enter an IRP supplemental
application, adding a vehicle to their fleet, and this new addition is
updated in all applicable databases, including the Roadside Operations
computer.

Acceptance Criteria

-   The Carrier receives the credential from the CV Administration that
    adds the vehicle to the Carrier's fleet.

-   CVIEW updates its database with the new information (vehicle
    snapshot segment update).

-   SAFER updates its database with the new information (vehicle
    snapshot segment update).

-   Roadside Operations receives, updates, and displays the new
    information.

Requirements Tested

The test criteria for credentials-related data flows and electronic
screening are based on standards found in COACH Part 5, and reflect
those requirements that are pertinent to this test case. See COACH Part
5 for a detailed cross reference of test cases to requirements tested.

Data Recording/Reduction/Evaluation Procedures

Examination of messages, databases, and displayed screens will show the
successful receipt of and update of information resulting from the
submission of an IRP Supplemental Application. The Test Analyst will
compare the appropriate database updates to the information entered by
the Carrier in step 1, to insure proper transaction sequencing and data
flow during the test. The checklist for Web-based credential
applications will be included in a summary of results.

Procedure

See Table 5-1 for the Master test procedures. The Carrier, using test
case data set 4.01.01 will input the data for the supplemental
application. Note that some steps are starred (). The Test Analyst will
examine these starred steps for conformance with the CVISN architecture
in post-test evaluation. Operator Actions are indicated in **BOLD**
print, whereas, System Actions are not in bold print.

Table 5--2.\
Test 5.01.01: Master Test Conductor Procedure

+-----------------------------------------------------------------------+
| > **Checklist: The Web-based credential application process for       |
| > IRP:**                                                              |
|                                                                       |
| -   Supports the following browsers:                                  |
|                                                                       |
|     \_\_\_\_Netscape 4                                                |
|                                                                       |
|     \_\_\_\_Internet Explorer 4                                       |
|                                                                       |
|     \_\_\_\_Internet Explorer 5.5                                     |
|                                                                       |
|     \_\_\_\_ Other (list in comments)                                 |
|                                                                       |
| -   Utilizes recommended primary identifiers in application data      |
|     fields:                                                           |
|                                                                       |
|     \_\_\_\_Carrier \-- US DOT \#                                     |
|                                                                       |
|     \_\_\_\_Vehicle \-- Vehicle Identification Number (VIN)           |
|                                                                       |
|     \_\_\_\_Vehicle \-- State & Plate                                 |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   Accurately displays the appropriate credential application form,  |
|                                                                       |
|     with all necessary data fields present and input validated.       |
|                                                                       |
|     (list exceptions in comments)                                     |
|                                                                       |
|     \_\_\_\_Yes                                                       |
|                                                                       |
|     \_\_\_\_No                                                        |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   User interface allows standard credential application functions   |
|     appropriate                                                       |
|                                                                       |
|     for this credential type. For IRP:                                |
|                                                                       |
|     \_\_\_\_ Add vehicle \_\_\_\_ Add fleet                           |
|                                                                       |
|     \_\_\_\_ Delete vehicle \_\_\_\_ Delete fleet                     |
|                                                                       |
|     \_\_\_\_ Modify vehicle \_\_\_\_ Change address                   |
|                                                                       |
|     \_\_\_\_ Change weight group \_\_\_\_ Renew fleet                 |
|                                                                       |
|     \_\_\_\_ Replace credential \_\_\_\_ Transfer plates (add/delete) |
|                                                                       |
|     \_\_\_\_ Add jurisdiction \_\_\_\_ Change OEN (Unit Number)       |
|                                                                       |
|     \_\_\_\_ Delete jurisdiction \_\_\_\_ Request temporary authority |
|                                                                       |
|     \_\_\_\_ Modify weight \_\_\_\_ Other (list in comments)          |
|                                                                       |
| -   Displays Invoice: \_\_\_\_Yes \_\_\_\_No                          |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   Supports payment by credit card: \_\_\_\_Yes \_\_\_\_No           |
|                                                                       |
|     or by ACH \_\_\_\_Yes \_\_\_\_No                                  |
|                                                                       |
|     or other means (list in comments) \_\_\_\_Yes \_\_\_\_No          |
|                                                                       |
| -   End-to-End process forwards snapshot updates to CVIEW:            |
|     \_\_\_\_Yes \_\_\_\_No                                            |
|                                                                       |
| ##                                                                    |
|                                                                       |
| -   CVIEW provides credential information to SAFER and Roadside       |
|     Systems: \_\_\_\_Yes \_\_\_\_No                                   |
+-----------------------------------------------------------------------+

+----+-----------------------------+----------------------------+----+
| St | System or Operator Action   | Master Test Criteria       | Pa |
| ep |                             |                            | ss |
|    |                             |                            | /\ |
|    |                             |                            | Fa |
|    |                             |                            | il |
+====+=============================+============================+====+
| 1  | **The Carrier operator      | None                       |    |
|    | enters supplemental         |                            |    |
|    | application information     |                            |    |
|    | "Add Vehicle" into the      |                            |    |
|    | electronic credentialing    |                            |    |
|    | system and sends it to the  |                            |    |
|    | CV Administration.**        |                            |    |
|    |                             |                            |    |
|    | Record the following        |                            |    |
|    | information for the added   |                            |    |
|    | vehicle:                    |                            |    |
|    |                             |                            |    |
|    | Vehicle Identification      |                            |    |
|    |                             |                            |    |
|    | VIN                         |                            |    |
|    | \_\_\_\_\_\_\               |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    | State                       |                            |    |
|    | \_\_\_\_\_\_\               |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    | Plate                       |                            |    |
|    | \_\_\_\_\_\_\               |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    | -   Credentials             |                            |    |
|    |                             |                            |    |
|    |     USDOT                   |                            |    |
|    |     \_\_\_\_\_\_\           |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     Company                 |                            |    |
|    |     Name\_\_\               |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     IRP Account             |                            |    |
|    |     N                       |                            |    |
|    | umber\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     IRP Base                |                            |    |
|    |     State\_\                |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     Jurisdictions and       |                            |    |
|    |     weights                 |                            |    |
|    |     \_\_\_\_\_\_\_\_\       |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    | \_\_\_\_\_\_\_\_\_\_\_\_\_\ |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    | \_\_\_\_\_\_\_\_\_\_\_\_\_\ |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    | \_\_\_\_\_\_\_\_\_\_\_\_\_\ |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
+----+-----------------------------+----------------------------+----+
| 2  | The CV Administration       | None                       |    |
|    | receives the application.   |                            |    |
+----+-----------------------------+----------------------------+----+
| 3  | The CV Administration sends | None                       |    |
|    | an invoice notice to the    |                            |    |
|    | Carrier.                    |                            |    |
+----+-----------------------------+----------------------------+----+
| 4  | The Carrier receives the    | None                       |    |
|    | invoice notice.             |                            |    |
+----+-----------------------------+----------------------------+----+
| 5  | **The Carrier operator      | None                       |    |
|    | inputs and sends payment    |                            |    |
|    | info to the CV              |                            |    |
|    | Administration.**           |                            |    |
+----+-----------------------------+----------------------------+----+
| 6  | The CV Administration       | None                       |    |
|    | receives payment info.      |                            |    |
+----+-----------------------------+----------------------------+----+
| 7  | The CV Administration sends | None                       |    |
|    | a credential return to the  |                            |    |
|    | Carrier.                    |                            |    |
+----+-----------------------------+----------------------------+----+
| 8  | The Carrier receives the    | **Verify the credential    |    |
|    | credential return.          | returned is**              |    |
|    |                             |                            |    |
|    |                             | **accurate and the vehicle |    |
|    |                             | has**                      |    |
|    |                             |                            |    |
|    |                             | **been added to the        |    |
|    |                             | correct fleet.**           |    |
+----+-----------------------------+----------------------------+----+
| 9  | The CV Administration sends | None                       |    |
|    | a vehicle snapshot segment  |                            |    |
|    | update to CVIEW.            |                            |    |
+----+-----------------------------+----------------------------+----+
| 10 | CVIEW updates its database. | **Verify that the CVIEW    |    |
|    |                             | database is updated        |    |
|    |                             | correctly**                |    |
+----+-----------------------------+----------------------------+----+
| 11 | CVIEW sends a snapshot      | None                       |    |
|    | segment update to SAFER.    |                            |    |
+----+-----------------------------+----------------------------+----+
| 12 | SAFER updates its database  | **Verify that the SAFER    |    |
|    |                             | database is updated        |    |
|    |                             | correctly**                |    |
+----+-----------------------------+----------------------------+----+
| 13 | CVIEW fulfills subscription | None                       |    |
|    | to the Roadside Operations  |                            |    |
|    | System and sends the        |                            |    |
|    | vehicle snapshot segment    |                            |    |
|    | update.                     |                            |    |
+----+-----------------------------+----------------------------+----+
| 14 | Roadside Operations         | **Verify the vehicle       |    |
|    | receives the vehicle        | snapshot sent by**         |    |
|    | snapshot.                   |                            |    |
|    |                             | **CVIEW is correct.**      |    |
|    |                             |                            |    |
|    |                             | Note: The information      |    |
|    |                             | recorded in                |    |
|    |                             |                            |    |
|    |                             | step 1 shall be used to    |    |
|    |                             | verify                     |    |
|    |                             |                            |    |
|    |                             | the vehicle snapshot.      |    |
+----+-----------------------------+----------------------------+----+

## 5.4 Scenario ID WETE-04: Carrier Adds Jurisdiction (IRP Supplemental)

*Test Configuration and Initial Conditions*

-   JHU/APL Facility Requirements

```{=html}
<!-- -->
```
-   None.

```{=html}
<!-- -->
```
-   User Facility Requirements

```{=html}
<!-- -->
```
-   Communications established between:

1.  The Carrier's Electronic Credentialing System and the State
    Commercial Vehicle (CV) Administration (i.e., Web Browser and Web
    Server)

2.  CV Administration and the State CVIEW System (CVIEW)

3.  CVIEW and SAFER

4.  Roadside Operations and CVIEW

-   Test Roles

```{=html}
<!-- -->
```
-   The test roles necessary to execute this test include:

```{=html}
<!-- -->
```
-   Master Test Conductor

-   CV Administration

-   Carrier

-   SAFER

-   CVIEW

-   Roadside Operations

-   Test Analyst.

```{=html}
<!-- -->
```
-   Initial Conditions

```{=html}
<!-- -->
```
-   An IRP Initial Registration has previously been processed

### [Test Case 5.04.01, Carrier Adds Jurisdiction (IRP Supplemental)]{.smallcaps}

Test Summary

The master test conductor or the test analyst completes the checklist
for Web-based credential applications. The Carrier sends an IRP
Supplemental Application to the CV Administration to add a jurisdiction
to an existing fleet. The CV Administration processes the application
and returns an invoice notice. The Carrier sends the CV Administration
payment information. Following receipt of payment information, the CV
Administration sends the credentials to the Carrier. The CV
Administration sends a vehicle snapshot segment update to CVIEW for each
vehicle in the fleet. CVIEW sends the vehicle snapshot segment updates
to SAFER and to the Roadside Operations system. The Roadside Operations
System receives the snapshot.

Test Purpose

The objective of this End-to-End test is to ensure the CVISN computer
systems involved in IRP credentialing work together properly.
Specifically, the test will verify the carrier is able to enter an IRP
supplemental application, adding a jurisdiction to an existing fleet,
and this new jurisdiction information is updated in all applicable
databases, including the Roadside Operations computer for all vehicles
in the fleet.

Acceptance Criteria

-   The Carrier receives the credentials from the CV Administration that
    adds the jurisdiction to their fleet. (cab cards for each vehicle)

-   CVIEW updates its database with the new information (vehicle
    snapshot segment updates: one per vehicle).

-   SAFER updates its database with the new information (vehicle
    snapshot segment update).

-   Roadside Operations receives, updates, and displays the new
    information for the fleet (snapshot segment update).

Requirements Tested

The test criteria for credentials-related data flows and electronic
screening are based on standards found in COACH Part 5, and reflect
those requirements that are pertinent to this test case. See COACH Part
5 for a detailed cross reference of test cases to requirements tested.

Data Recording/Reduction/Evaluation Procedures

Examination of messages, databases, and displayed screens will show the
successful receipt of and update of information resulting from the
submission of an IRP Supplemental Application. The Test Analyst will
compare the appropriate database updates to the information entered by
the Carrier in step 1, to insure proper transaction sequencing and data
flow during the test. The checklist for Web-based credential
applications will be included in a summary of results.

Procedure

See Table 5-2 for the Master test procedure. The Carrier, using test
case data set 4.04.01 will input the data for the supplemental
application. Note that some steps are starred (). The Test Analyst will
examine these starred steps for conformance with the CVISN architecture
in post-test evaluation. Operator Actions are indicated in **BOLD**
print, whereas, System Actions are not in bold print.

Table 5--3.\
Test 5.04.01: Master Test Conductor Procedure

+-----------------------------------------------------------------------+
| > **Checklist: The Web-based credential application process for       |
| > IRP:**                                                              |
|                                                                       |
| -   Supports the following browsers:                                  |
|                                                                       |
|     \_\_\_\_Netscape 4                                                |
|                                                                       |
|     \_\_\_\_Internet Explorer 4                                       |
|                                                                       |
|     \_\_\_\_Internet Explorer 5.5                                     |
|                                                                       |
|     \_\_\_\_ Other (list in comments)                                 |
|                                                                       |
| -   Utilizes recommended primary identifiers in application data      |
|     fields:                                                           |
|                                                                       |
|     \_\_\_\_Carrier \-- US DOT \#                                     |
|                                                                       |
|     \_\_\_\_Vehicle \-- Vehicle Identification Number (VIN)           |
|                                                                       |
|     \_\_\_\_Vehicle \-- State & Plate                                 |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   Accurately displays the appropriate credential application form,  |
|                                                                       |
|     with all necessary data fields present and input validated.       |
|                                                                       |
|     (list exceptions in comments)                                     |
|                                                                       |
|     \_\_\_\_Yes                                                       |
|                                                                       |
|     \_\_\_\_No                                                        |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   User interface allows standard credential application functions   |
|     appropriate                                                       |
|                                                                       |
|     for this credential type. For IRP:                                |
|                                                                       |
|     \_\_\_\_ Add vehicle \_\_\_\_ Add fleet                           |
|                                                                       |
|     \_\_\_\_ Delete vehicle \_\_\_\_ Delete fleet                     |
|                                                                       |
|     \_\_\_\_ Modify vehicle \_\_\_\_ Change address                   |
|                                                                       |
|     \_\_\_\_ Change weight group \_\_\_\_ Renew fleet                 |
|                                                                       |
|     \_\_\_\_ Replace credential \_\_\_\_ Transfer plates (add/delete) |
|                                                                       |
|     \_\_\_\_ Add jurisdiction \_\_\_\_ Change OEN (Unit Number)       |
|                                                                       |
|     \_\_\_\_ Delete jurisdiction \_\_\_\_ Request temporary authority |
|                                                                       |
|     \_\_\_\_ Modify weight \_\_\_\_ Other (list in comments)          |
|                                                                       |
| -   Displays Invoice: \_\_\_\_Yes \_\_\_\_No                          |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   Supports payment by credit card: \_\_\_\_Yes \_\_\_\_No           |
|                                                                       |
|     or by ACH \_\_\_\_Yes \_\_\_\_No                                  |
|                                                                       |
|     or other means (list in comments) \_\_\_\_Yes \_\_\_\_No          |
|                                                                       |
| -   End-to-End process forwards snapshot updates to CVIEW:            |
|     \_\_\_\_Yes \_\_\_\_No                                            |
|                                                                       |
| ##                                                                    |
|                                                                       |
| -   CVIEW provides credential information to SAFER and Roadside       |
|     Systems: \_\_\_\_Yes \_\_\_\_No                                   |
+-----------------------------------------------------------------------+

+----+-----------------------------+----------------------------+----+
| St | System or Operator Action   | Master Test Criteria       | Pa |
| ep |                             |                            | ss |
|    |                             |                            | /\ |
|    |                             |                            | Fa |
|    |                             |                            | il |
+====+=============================+============================+====+
| 1  | **The Carrier enters        | None                       |    |
|    | supplemental application    |                            |    |
|    | information "Add            |                            |    |
|    | Jurisdiction" into the      |                            |    |
|    | electronic credentialing    |                            |    |
|    | system, adding one          |                            |    |
|    | jurisdiction to the fleet,  |                            |    |
|    | and sends it to the CV      |                            |    |
|    | Administration.**           |                            |    |
|    |                             |                            |    |
|    | Note: The existing test     |                            |    |
|    | fleet consists of 2         |                            |    |
|    | vehicles.                   |                            |    |
|    |                             |                            |    |
|    | **Record the following      |                            |    |
|    | information for the two     |                            |    |
|    | vehicles in the fleet, plus |                            |    |
|    | the carrier and fleet       |                            |    |
|    | information. Note the "new" |                            |    |
|    | jurisdiction that is added  |                            |    |
|    | to the fleet.**             |                            |    |
|    |                             |                            |    |
|    | -   Vehicle 1               |                            |    |
|    |     Identification          |                            |    |
|    |                             |                            |    |
|    |     VIN                     |                            |    |
|    |     \_                      |                            |    |
|    | \_\_\_\_\_\_\_\_\_\_\_\_\_\ |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     License Plate Number    |                            |    |
|    |                             |                            |    |
|    |    \_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     License Plate           |                            |    |
|    |     State\_\                |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    | -   Vehicle 2               |                            |    |
|    |     Identification          |                            |    |
|    |                             |                            |    |
|    |     VIN                     |                            |    |
|    |     \_                      |                            |    |
|    | \_\_\_\_\_\_\_\_\_\_\_\_\_\ |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     License Plate Number    |                            |    |
|    |                             |                            |    |
|    |    \_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     License Plate           |                            |    |
|    |     State\_\                |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    | -   Carrier and Fleet       |                            |    |
|    |     Information             |                            |    |
|    |                             |                            |    |
|    |     USDOT                   |                            |    |
|    |     \_\_\_\_\_\_\_\_\_\_\   |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     IRP Account             |                            |    |
|    |     Number\                 |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     IRP Base State          |                            |    |
|    |     \_\_\_\_\_\             |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     Jurisdiction(s)         |                            |    |
|    |     \_\_\_\_\_\             |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     New Jurisdiction:       |                            |    |
|    |     \_\_\                   |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    | -   Registrant Information  |                            |    |
|    |                             |                            |    |
|    |     DBA Name                |                            |    |
|    |     \_\_\_\_\_\_\_\_\       |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     Owner                   |                            |    |
|    |     Name\_\_\_\_\_\_\_\     |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |     Address                 |                            |    |
|    |     \_\_\_\_\_\_\_\_\_\_\   |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    |    **\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    | \_\_\_\_\_\_\_\_\_\_\_\_\_\ |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    | \_\_\_\_\_\_\_\_\_\_\_\_\_\ |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_** |                            |    |
+----+-----------------------------+----------------------------+----+
| 2  | The CV Administration       | None                       |    |
|    | receives the application.   |                            |    |
+----+-----------------------------+----------------------------+----+
| 3  | The CV Administration sends | None                       |    |
|    | an invoice notice to the    |                            |    |
|    | Carrier.                    |                            |    |
+----+-----------------------------+----------------------------+----+
| 4  | The Carrier receives the    | None                       |    |
|    | invoice notice.             |                            |    |
+----+-----------------------------+----------------------------+----+
| 5  | **The Carrier inputs and    | None                       |    |
|    | sends payment info to the   |                            |    |
|    | CV Administration.**        |                            |    |
+----+-----------------------------+----------------------------+----+
| 6  | The CV Administration       | None                       |    |
|    | receives payment info.      |                            |    |
+----+-----------------------------+----------------------------+----+
| 7  | The CV Administration sends | None                       |    |
|    | the credential to the       |                            |    |
|    | Carrier.                    |                            |    |
+----+-----------------------------+----------------------------+----+
| 8  | The Carrier system receives | **Verify the two           |    |
|    | the credentials for both    | credentials returned**     |    |
|    | vehicles. **Carrier         |                            |    |
|    | operator views credential   | **are accurate and the new |    |
|    | information.**              | jurisdiction**             |    |
|    |                             |                            |    |
|    |                             | **has been added to both   |    |
|    |                             | vehicles.**                |    |
+----+-----------------------------+----------------------------+----+
| 9  | The CV Administration sends | None                       |    |
|    | a vehicle snapshot segment  |                            |    |
|    | update to CVIEW for each    |                            |    |
|    | vehicle in the fleet.       |                            |    |
+----+-----------------------------+----------------------------+----+
| 10 | CVIEW updates its database. | **Verify the updated       |    |
|    |                             | information sent**         |    |
|    |                             |                            |    |
|    |                             | **by the CV Administration |    |
|    |                             | has been**                 |    |
|    |                             |                            |    |
|    |                             | **updated in the CVIEW     |    |
|    |                             | database and**             |    |
|    |                             |                            |    |
|    |                             | **is accurate.**           |    |
|    |                             |                            |    |
|    |                             | Note: The information      |    |
|    |                             | recorded in                |    |
|    |                             |                            |    |
|    |                             | step 1 shall be used for   |    |
|    |                             |                            |    |
|    |                             | verifying the accuracy of  |    |
|    |                             | the                        |    |
|    |                             |                            |    |
|    |                             | update.                    |    |
+----+-----------------------------+----------------------------+----+
| 11 | CVIEW fulfills snapshot     | None                       |    |
|    | subscription for SAFER.     |                            |    |
+----+-----------------------------+----------------------------+----+
| 12 | SAFER receives the snapshot | **Verify the updated       |    |
|    | segments and updates its    | information sent**         |    |
|    | database                    |                            |    |
|    |                             | **by CVIEW has been        |    |
|    |                             | updated in the**           |    |
|    |                             |                            |    |
|    |                             | **SAFER database and is    |    |
|    |                             | accurate**.                |    |
|    |                             |                            |    |
|    |                             | Note: The information      |    |
|    |                             | recorded in                |    |
|    |                             |                            |    |
|    |                             | Step 1 shall be used for   |    |
|    |                             |                            |    |
|    |                             | Verifying the accuracy of  |    |
|    |                             | the                        |    |
|    |                             |                            |    |
|    |                             | Update.                    |    |
+----+-----------------------------+----------------------------+----+
| 13 | CVIEW fulfills snapshot     | None                       |    |
|    | subscription for the        |                            |    |
|    | Roadside Operations System. |                            |    |
+----+-----------------------------+----------------------------+----+
| 14 | Roadside Operations         | **Verify the snapshots     |    |
|    | performs subscription       | sent by CVIEW are          |    |
|    | download to the roadside    | correct.**                 |    |
|    | computer.                   |                            |    |
|    |                             | Note: The information      |    |
|    |                             | recorded in                |    |
|    |                             |                            |    |
|    |                             | step 1 shall be used to    |    |
|    |                             | verify                     |    |
|    |                             |                            |    |
|    |                             | the vehicle snapshot.      |    |
+----+-----------------------------+----------------------------+----+

## 5.5 Scenario ID WETE-05: Carrier Renews IRP Credential

Test Configuration and Initial Conditions

-   JHU/APL Facility Requirements

```{=html}
<!-- -->
```
-   None.

```{=html}
<!-- -->
```
-   User Facility Requirements

```{=html}
<!-- -->
```
-   Communications established between:

1.  The Carrier's Electronic Credentialing System and the State
    Commercial Vehicle (CV) Administration (i.e., Web Browser and Web
    Server)

2.  CV Administration and the State CVIEW System (CVIEW)

3.  CVIEW and SAFER

-   Test Roles

```{=html}
<!-- -->
```
-   The key test roles necessary to execute this test include:

```{=html}
<!-- -->
```
-   Master Test Conductor

-   CV Administration

-   Carrier

-   SAFER

-   CVIEW

-   Test Analyst.

```{=html}
<!-- -->
```
-   Initial Conditions

```{=html}
<!-- -->
```
-   An IRP Initial Registration has previously been processed

### [Test Case 5.05.01, Carrier Renews IRP Credential]{.smallcaps}

Test Summary

The master test conductor or the test analyst completes the checklist
for Web-based credential applications. The CV Administration sends a
renewal reminder to the Carrier. The Carrier completes the renewal
application and sends it to the CV Administration. The CV Administration
validates and accepts the application and returns an invoice notice. The
Carrier sends the CV Administration payment information and following
receipt of payment information, CV Administration sends the credential
to the Carrier. The CV Administration sends vehicle snapshot segment
updates to CVIEW for every vehicle in the fleet. CVIEW updates its
database and sends the snapshot segment update to SAFER and the Roadside
Operations System.

Test Purpose

The objective of this End-to-End test is to ensure the CVISN computer
systems involved in IRP credentialing work together properly.
Specifically, the test will verify the carrier is able to enter an IRP
renewal application and the information is updated in all applicable
databases, including the Roadside Operations SAFER system computer.

Acceptance Criteria

-   The Carrier receives the credential from the CV Administration.

-   CVIEW updates its database with the new information (vehicle
    snapshot segment update).

-   SAFER updates its database with the new information (snapshot
    segment update).

-   Roadside Operations receives snapshot segment update.

Requirements Tested

The test criteria for credentials-related data flows and electronic
screening are based on standards found in COACH Part 5, and reflect
those requirements that are pertinent to this test case. See COACH Part
5 for a detailed cross reference of test cases to requirements tested.

Data Recording/Reduction/Evaluation Procedures

Examination of messages, databases, and displayed screens will show the
successful receipt of and update of information resulting from the
submission of an IRP Renewal Application. The Test Analyst will compare
the appropriate database updates to the information entered by the
Carrier in step 3 to insure proper transaction sequencing and data flow
during the test. The checklist for Web-based credential applications
will be included in a summary of results.

Procedure

See Table 5-3 for the Master test procedure. The Carrier, using test
case data set 4.05.01 will input the data for the renewal application.
Note that some steps are starred (). The Test Analyst will examine these
starred steps for conformance with the CVISN architecture in post-test
evaluation. Operator Actions are indicated in **BOLD** print, whereas,
System Actions are not in bold print.

Table 5--4.\
Test 5.05.01: Master Test Conductor Procedure

+-----------------------------------------------------------------------+
| > **Checklist: The Web-based credential application process for       |
| > IRP:**                                                              |
|                                                                       |
| -   Supports the following browsers:                                  |
|                                                                       |
|     \_\_\_\_Netscape 4                                                |
|                                                                       |
|     \_\_\_\_Internet Explorer 4                                       |
|                                                                       |
|     \_\_\_\_Internet Explorer 5.5                                     |
|                                                                       |
|     \_\_\_\_ Other (list in comments)                                 |
|                                                                       |
| -   Utilizes recommended primary identifiers in application data      |
|     fields:                                                           |
|                                                                       |
|     \_\_\_\_Carrier \-- US DOT \#                                     |
|                                                                       |
|     \_\_\_\_Vehicle \-- Vehicle Identification Number (VIN)           |
|                                                                       |
|     \_\_\_\_Vehicle \-- State & Plate                                 |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   Accurately displays the appropriate credential application form,  |
|                                                                       |
|     with all necessary data fields present and input validated.       |
|                                                                       |
|     (list exceptions in comments)                                     |
|                                                                       |
|     \_\_\_\_Yes                                                       |
|                                                                       |
|     \_\_\_\_No                                                        |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   User interface allows standard credential application functions   |
|     appropriate                                                       |
|                                                                       |
|     for this credential type. For IRP:                                |
|                                                                       |
|     \_\_\_\_ Add vehicle \_\_\_\_ Add fleet                           |
|                                                                       |
|     \_\_\_\_ Delete vehicle \_\_\_\_ Delete fleet                     |
|                                                                       |
|     \_\_\_\_ Modify vehicle \_\_\_\_ Change address                   |
|                                                                       |
|     \_\_\_\_ Change weight group \_\_\_\_ Renew fleet                 |
|                                                                       |
|     \_\_\_\_ Replace credential \_\_\_\_ Transfer plates (add/delete) |
|                                                                       |
|     \_\_\_\_ Add jurisdiction \_\_\_\_ Change OEN (Unit Number)       |
|                                                                       |
|     \_\_\_\_ Delete jurisdiction \_\_\_\_ Request temporary authority |
|                                                                       |
|     \_\_\_\_ Modify weight \_\_\_\_ Other (list in comments)          |
|                                                                       |
| -   Displays Invoice: \_\_\_\_Yes \_\_\_\_No                          |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   Supports payment by credit card: \_\_\_\_Yes \_\_\_\_No           |
|                                                                       |
|     or by ACH \_\_\_\_Yes \_\_\_\_No                                  |
|                                                                       |
|     or other means (list in comments) \_\_\_\_Yes \_\_\_\_No          |
|                                                                       |
| -   End-to-End process forwards snapshot updates to CVIEW:            |
|     \_\_\_\_Yes \_\_\_\_No                                            |
|                                                                       |
| ##                                                                    |
|                                                                       |
| -   CVIEW provides credential information to SAFER and Roadside       |
|     Systems: \_\_\_\_Yes \_\_\_\_No                                   |
+-----------------------------------------------------------------------+

+-----+-----------------------------+----------------------------+----+
| S   | System or Operator Action   | Master Test Criteria       | Pa |
| tep |                             |                            | ss |
|     |                             |                            | /\ |
|     |                             |                            | Fa |
|     |                             |                            | il |
+=====+=============================+============================+====+
| 1   | The CV Administration sends | None                       |    |
|     | a renewal reminder to the   |                            |    |
|     | Carrier. Prior to sending   |                            |    |
|     | the renewal reminder, the   |                            |    |
|     | CV Administration will      |                            |    |
|     | verify the correct owner of |                            |    |
|     | the vehicle.                |                            |    |
+-----+-----------------------------+----------------------------+----+
| 2   | The Carrier receives the    | None                       |    |
|     | renewal reminder.           |                            |    |
+-----+-----------------------------+----------------------------+----+
| 3   | **The Carrier operator      | None                       |    |
|     | enters the renewal          |                            |    |
|     | application into the        |                            |    |
|     | electronic credentialing    |                            |    |
|     | system and sends it to the  |                            |    |
|     | CV Administration.**        |                            |    |
|     |                             |                            |    |
|     | Record the following        |                            |    |
|     | information:                |                            |    |
|     |                             |                            |    |
|     | Vehicle Identification      |                            |    |
|     |                             |                            |    |
|     | VIN                         |                            |    |
|     | \_                          |                            |    |
|     | \_\_\_\_\_\_\_\_\_\_\_\_\_\ |                            |    |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|     |                             |                            |    |
|     | State/plate                 |                            |    |
|     | \_\_\_\_\_\_\_\_\           |                            |    |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|     |                             |                            |    |
|     | USDOT number                |                            |    |
|     | \_\_\_\_\                   |                            |    |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|     |                             |                            |    |
|     | Credentials                 |                            |    |
|     |                             |                            |    |
|     | IRP Account Number          |                            |    |
|     | \                           |                            |    |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|     |                             |                            |    |
|     | IRP Base State              |                            |    |
|     | \_\_\_\_\_\                 |                            |    |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|     |                             |                            |    |
|     | Registration Effective Date |                            |    |
|     | \_\_\_\_\_\_\_\_\_          |                            |    |
|     |                             |                            |    |
|     | Registration Expiration     |                            |    |
|     | Date \_\_\_\_\_\_\_\_\_     |                            |    |
|     |                             |                            |    |
|     | -   Jurisdictions/weights   |                            |    |
|     |     \_\                     |                            |    |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|     |     \_\_                    |                            |    |
|     | \_\_\_\_\_\_\_\_\_\_\_\_\_\ |                            |    |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|     |                             |                            |    |
|     |     Registrant Information  |                            |    |
|     |                             |                            |    |
|     |     DBA Name                |                            |    |
|     |     \_\_\_\_\_\_\_\_\_\     |                            |    |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|     |                             |                            |    |
|     |     Owner Name              |                            |    |
|     |     \_\_\_\_\_\_\_\         |                            |    |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|     |                             |                            |    |
|     |     Address                 |                            |    |
|     |     \_\_\_\_\_\_\_\_\_\_\_\ |                            |    |
|     | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
+-----+-----------------------------+----------------------------+----+
| 4   | The CV Administration       | None                       |    |
|     | receives the renewal        |                            |    |
|     | application.                |                            |    |
+-----+-----------------------------+----------------------------+----+
| 5   | The CV Administration       | None                       |    |
|     | validates the application   |                            |    |
|     | by checking the Carrier,    |                            |    |
|     | vehicle, and account data   |                            |    |
|     | for flags and conditions.   |                            |    |
+-----+-----------------------------+----------------------------+----+
| 6   | The CV Administration       | None                       |    |
|     | accepts the renewal         |                            |    |
|     | application from the        |                            |    |
|     | Carrier                     |                            |    |
+-----+-----------------------------+----------------------------+----+
| 7   | The CV Administration       | None                       |    |
|     | calculates the renewal fee. |                            |    |
+-----+-----------------------------+----------------------------+----+
| 8   | The CV Administration sends | None                       |    |
|     | an invoice notice to the    |                            |    |
|     | Carrier.                    |                            |    |
+-----+-----------------------------+----------------------------+----+
| 9   | The Carrier receives the    | None                       |    |
|     | invoice notice.             |                            |    |
+-----+-----------------------------+----------------------------+----+
| 10  | **The Carrier operator      | None                       |    |
|     | inputs and sends payment    |                            |    |
|     | info to the CV              |                            |    |
|     | Administration.**           |                            |    |
+-----+-----------------------------+----------------------------+----+
| 11  | The CV Administration       | None                       |    |
|     | receives and approves       |                            |    |
|     | payment.                    |                            |    |
+-----+-----------------------------+----------------------------+----+
| 12  | The CV Administration sends | None                       |    |
|     | the credential to the       |                            |    |
|     | Carrier. (The cab card      |                            |    |
|     | number is sent to the       |                            |    |
|     | Carrier.)                   |                            |    |
+-----+-----------------------------+----------------------------+----+
| 13  | The Carrier receives the    | **Verify the credential    |    |
|     | new cab card.               | returned is**              |    |
|     |                             |                            |    |
|     |                             | **accurate.**              |    |
|     |                             |                            |    |
|     |                             | Note: The information      |    |
|     |                             | recorded in                |    |
|     |                             |                            |    |
|     |                             | step 3 shall be used for   |    |
|     |                             |                            |    |
|     |                             | verifying the accuracy of  |    |
|     |                             | the                        |    |
|     |                             |                            |    |
|     |                             | credential.                |    |
+-----+-----------------------------+----------------------------+----+
| 14  | The CV Administration sends | None                       |    |
|     | a snapshot segment update   |                            |    |
|     | to CVIEW.                   |                            |    |
+-----+-----------------------------+----------------------------+----+
| 15  | CVIEW updates its database. | **Verify the updated       |    |
|     |                             | information sent**         |    |
|     |                             |                            |    |
|     |                             | **by the CV Administration |    |
|     |                             | has been**                 |    |
|     |                             |                            |    |
|     |                             | **updated in the CVIEW     |    |
|     |                             | database and**             |    |
|     |                             |                            |    |
|     |                             | **is accurate.**           |    |
|     |                             |                            |    |
|     |                             | Note: The information      |    |
|     |                             | recorded in                |    |
|     |                             |                            |    |
|     |                             | step 3 shall be used for   |    |
|     |                             |                            |    |
|     |                             | verifying the accuracy of  |    |
|     |                             | the                        |    |
|     |                             |                            |    |
|     |                             | update.                    |    |
+-----+-----------------------------+----------------------------+----+
| 16  | CVIEW sends a snapshot      | None                       |    |
|     | segment update to SAFER.    |                            |    |
+-----+-----------------------------+----------------------------+----+
| 17  | SAFER updates its database  | **Verify the updated       |    |
|     |                             | information sent**         |    |
|     |                             |                            |    |
|     |                             | **by CVIEW has been        |    |
|     |                             | updated in the**           |    |
|     |                             |                            |    |
|     |                             | **SAFER database and is    |    |
|     |                             | accurate.**                |    |
|     |                             |                            |    |
|     |                             | Note: The information      |    |
|     |                             | recorded in                |    |
|     |                             |                            |    |
|     |                             | Step 3 shall be used for   |    |
|     |                             |                            |    |
|     |                             | Verifying the accuracy of  |    |
|     |                             | the                        |    |
|     |                             |                            |    |
|     |                             | Update.                    |    |
+-----+-----------------------------+----------------------------+----+
| 18  | CVIEW fulfills snapshot     | None                       |    |
|     | subscription for the        |                            |    |
|     | Roadside Operations System. |                            |    |
+-----+-----------------------------+----------------------------+----+
| 19  | Roadside Operations         | **Verify the snapshot sent |    |
|     | performs subscription       | by CVIEW is**              |    |
|     | download to the roadside    |                            |    |
|     | computer.                   | **correct.**               |    |
|     |                             |                            |    |
|     |                             | Note: The information      |    |
|     |                             | recorded in                |    |
|     |                             |                            |    |
|     |                             | step 1 shall be used to    |    |
|     |                             | verify                     |    |
|     |                             |                            |    |
|     |                             | the vehicle snapshot.      |    |
+-----+-----------------------------+----------------------------+----+

## 5.6 Scenario ID ETE-06: Carrier Renews IFTA Credential

***Test Configuration and Initial Conditions***

-   JHU/APL Facility Requirements

```{=html}
<!-- -->
```
-   None.

```{=html}
<!-- -->
```
-   User Facility Requirements

```{=html}
<!-- -->
```
-   Communications established between:

1.  The Carrier's Electronic Credentialing System and the State
    Commercial Vehicle (CV) Administration (i.e., Web Browser and Web
    Server)

2.  CV Administration and the State CVIEW System (CVIEW)

3.  CVIEW and SAFER

4.  Roadside Operations System and CVIEW

5.  ASPEN/ASPEN 32 and CVIEW/SAFER

6.  CV Administration and IFTA Clearinghouse (if applicable)

-   Test Roles

```{=html}
<!-- -->
```
-   The key test roles necessary to execute this test include:

```{=html}
<!-- -->
```
-   Master Test Conductor

-   CV Administration

-   Carrier

-   SAFER

-   CVIEW

-   Roadside Operations

-   ASPEN/ASPEN 32

-   IFTA Clearinghouse (if applicable)

-   Test Analyst

```{=html}
<!-- -->
```
-   Initial Conditions

```{=html}
<!-- -->
```
-   An IFTA Initial Registration has previously been processed

### [Test Case 5.06.01, Carrier Renews IFTA Credential]{.smallcaps}

Test Summary

The master test conductor or the test analyst completes the checklist
for Web-based credential applications. The CV Administration may send an
IFTA renewal reminder to the Carrier. The Carrier completes the renewal
application and sends it to the CV Administration. The CV Administration
accepts and validates the Carrier's renewal application. The CV
Administration assigns decal numbers and sends the credential to the
Carrier. The CV Administration sends a full carrier snapshot segment
update to CVIEW. CVIEW updates its database and sends a carrier snapshot
segment update to SAFER and the Roadside Operations System. (If
applicable, the CV Administration sends the IFTA Clearinghouse the
Carrier's demographic information.) The Roadside Operations System
receives the snapshot. Inspection personnel will use either ASPEN or
ASPEN 32. If using ASPEN, the inspector queries SAFER for a Carrier
Snapshot. For inspectors using ASPEN 32 units, query SAFER or CVIEW for
a Carrier Snapshot.

Test Purpose

The objective of this End-to-End test is to ensure the CVISN computer
systems involved in IFTA credentialing work together properly.
Specifically, the test will verify the carrier is able to enter an IFTA
renewal application and the information is updated in all applicable
databases, including the Roadside Operations computer.

Acceptance Criteria

-   The Carrier receives the credential from the CV Administration.

-   CVIEW updates its database with the new information (snapshot
    segment update).

-   SAFER updates its database with the new information (snapshot
    segment update).

-   Roadside Operations System SAFER updates its database with the new
    information (snapshot segment update).

-   If applicable, the IFTA Clearinghouse receives demographic
    information from the CV Administration.

-   ASPEN/ASPEN 32 receives the correct snapshot from SAFER/CVIEW

Requirements Tested

The test criteria for credentials-related data flows and electronic
screening are based on standards found in COACH Part 5, and reflect
those requirements that are pertinent to this test case. See COACH Part
5 for a detailed cross reference of test cases to requirements tested.

Data Recording/Reduction/Evaluation Procedures

Examination of messages, databases, and displayed screens will show the
successful receipt of and update of information resulting from the
submission of an IRP Renewal Application. The Test Analyst will compare
the appropriate database updates to the information entered by the
Carrier in step 3 to insure proper transaction sequencing and data flow
during the test. The checklist for Web-based credential applications
will be included in a summary of results.

Procedure

See Table 5-4 for the Master test procedure. The Carrier, using test
case data set 4.06.01 will input the data for the supplemental
application. Note that some steps are starred (). The Test Analyst will
examine these starred steps for conformance with the CVISN architecture
in post-test evaluation. Operator Actions are indicated in **BOLD**
print, whereas, System Actions are not in bold print.

Table 5--5.\
Test 5.06.01: Master Test Conductor Procedure

+-----------------------------------------------------------------------+
| > **Checklist: The Web-based credential application process for IFTA  |
| > Registration:**                                                     |
|                                                                       |
| -   Supports the following browsers:                                  |
|                                                                       |
|     \_\_\_\_Netscape 4                                                |
|                                                                       |
|     \_\_\_\_Internet Explorer 4                                       |
|                                                                       |
|     \_\_\_\_Internet Explorer 5.5                                     |
|                                                                       |
|     \_\_\_\_Other (list in comments)                                  |
|                                                                       |
| -   Utilizes recommended primary identifiers in application data      |
|     fields:                                                           |
|                                                                       |
|     \_\_\_\_Carrier \-- US DOT \#                                     |
|                                                                       |
|     \_\_\_\_Vehicle \-- Vehicle Identification Number (VIN)           |
|                                                                       |
|     \_\_\_\_Vehicle \-- State & Plate                                 |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   Accurately displays the appropriate credential application form,  |
|                                                                       |
|     with all necessary data fields present and input validated.       |
|                                                                       |
|     (list exceptions in comments)                                     |
|                                                                       |
|     \_\_\_\_Yes                                                       |
|                                                                       |
|     \_\_\_\_No                                                        |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   User interface allows standard credential application functions   |
|     appropriate                                                       |
|                                                                       |
|     for this credential type. For IFTA Registration:                  |
|                                                                       |
|     \_\_\_\_Add vehicle \_\_\_\_Renewal                               |
|                                                                       |
|     \_\_\_\_Replace credential \_\_\_\_Change OEN (Unit Number)       |
|                                                                       |
|     \_\_\_\_Trip permit \_\_\_\_ IFTA temporary credential            |
|                                                                       |
|     \_\_\_\_Add jurisdiction \_\_\_\_ Other (list in comments)        |
|                                                                       |
| -   Displays Invoice: \_\_\_\_Yes \_\_\_\_No                          |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   Supports payment by credit card: \_\_\_\_Yes \_\_\_\_No           |
|                                                                       |
|     or by ACH: \_\_\_\_Yes \_\_\_\_No                                 |
|                                                                       |
|     or other means (list in comments) \_\_\_\_Yes \_\_\_\_No          |
|                                                                       |
| -   End-to-End process forwards snapshot updates to CVIEW:            |
|     \_\_\_\_Yes \_\_\_\_No                                            |
|                                                                       |
| ##                                                                    |
|                                                                       |
| -   CVIEW provides credential information to SAFER and Roadside       |
|     Systems: \_\_\_\_Yes \_\_\_\_No                                   |
+-----------------------------------------------------------------------+

+----+-----------------------------+----------------------------+----+
| St | System or Operator Action   | Master Test Criteria       | Pa |
| ep |                             |                            | ss |
|    |                             |                            | /\ |
|    |                             |                            | Fa |
|    |                             |                            | il |
+====+=============================+============================+====+
| 1  | The CV Administration may   | None                       |    |
|    | send a renewal reminder to  |                            |    |
|    | the Carrier. Prior to       |                            |    |
|    | sending the renewal         |                            |    |
|    | reminder, the CV            |                            |    |
|    | Administration will check   |                            |    |
|    | for flags or conditions     |                            |    |
|    | indicating problems.        |                            |    |
+----+-----------------------------+----------------------------+----+
| 2  | The Carrier receives the    | None                       |    |
|    | renewal reminder.           |                            |    |
+----+-----------------------------+----------------------------+----+
| 3  | **The Carrier enters the    | None                       |    |
|    | renewal application into    |                            |    |
|    | the electronic              |                            |    |
|    | credentialing system and    |                            |    |
|    | sends it to the CV          |                            |    |
|    | Administration**.           |                            |    |
|    |                             |                            |    |
|    | Record the following        |                            |    |
|    | information:                |                            |    |
|    |                             |                            |    |
|    | Credentials                 |                            |    |
|    |                             |                            |    |
|    | USDOT                       |                            |    |
|    | \_\_\_\_\_\_\_\             |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    | IFTA Account Number         |                            |    |
|    | \_\_\_\_\_\_\_\_\_\_\_      |                            |    |
|    |                             |                            |    |
|    | IFTA Base State             |                            |    |
|    | \_\                         |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    | Jurisdictions/weights       |                            |    |
|    | \_\_\_\_\_\_\_\_\_\_\_\_    |                            |    |
|    | \_\_\_\_\_\_\_\_\_\_\_\_\   |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    | Registration Effective Date |                            |    |
|    | \_\_\_\_\_\_\_              |                            |    |
|    |                             |                            |    |
|    | Registration Expiration     |                            |    |
|    | Date \_\_\_\_\_\_           |                            |    |
|    |                             |                            |    |
|    | Registrant Information      |                            |    |
|    |                             |                            |    |
|    | Company Name                |                            |    |
|    | \_\_\                       |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    | DBA Name                    |                            |    |
|    | \_\_\_\_\_\_\               |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
+----+-----------------------------+----------------------------+----+
| 4  | The CV Administration       | None                       |    |
|    | receives the renewal        |                            |    |
|    | application from the        |                            |    |
|    | Carrier.                    |                            |    |
+----+-----------------------------+----------------------------+----+
|    | Steps 5, 6, and 7 are       | None                       |    |
|    | applicable for states       |                            |    |
|    | electronically connected to |                            |    |
|    | the IFTA CH                 |                            |    |
+----+-----------------------------+----------------------------+----+
| 5  | The CV Administration       | None                       |    |
|    | queries the IFTA            |                            |    |
|    | Clearinghouse for the       |                            |    |
|    | Carrier's account status.   |                            |    |
+----+-----------------------------+----------------------------+----+
| 6  | The IFTA Clearinghouse      | None                       |    |
|    | sends the Carrier's account |                            |    |
|    | status to the CV            |                            |    |
|    | Administration.             |                            |    |
+----+-----------------------------+----------------------------+----+
| 7  | The CV Administration       | **Verify the response      |    |
|    | receives the Carrier's      | returned from the**        |    |
|    | account status form the     |                            |    |
|    | IFTA Clearinghouse.         | **Clearinghouse is for the |    |
|    |                             | correct**                  |    |
|    |                             |                            |    |
|    |                             | **Carrier.**               |    |
|    |                             |                            |    |
|    |                             | Note: The information      |    |
|    |                             | recorded in                |    |
|    |                             |                            |    |
|    |                             | Step 3 shall be used for   |    |
|    |                             |                            |    |
|    |                             | Verifying the accuracy of  |    |
|    |                             | the                        |    |
|    |                             |                            |    |
|    |                             | Response.                  |    |
+----+-----------------------------+----------------------------+----+
| 8  | The CV Administration       | None                       |    |
|    | accepts/validates the       |                            |    |
|    | Carrier's application.      |                            |    |
+----+-----------------------------+----------------------------+----+
| 9  | The CV Administration       | None                       |    |
|    | verifies the credential can |                            |    |
|    | be issued electronically.   |                            |    |
+----+-----------------------------+----------------------------+----+
| 10 | The CV Administration       | None                       |    |
|    | assigns decal numbers and   |                            |    |
|    | creates the credential.     |                            |    |
+----+-----------------------------+----------------------------+----+
| 11 | The CV Administration sends | None                       |    |
|    | the credential to the       |                            |    |
|    | Carrier electronically.     |                            |    |
+----+-----------------------------+----------------------------+----+
| 12 | The Carrier receives the    | **Verify the credential    |    |
|    | credential.                 | returned is**              |    |
|    |                             |                            |    |
|    |                             | **accurate.**              |    |
|    |                             |                            |    |
|    |                             | Note: The information      |    |
|    |                             | recorded in                |    |
|    |                             |                            |    |
|    |                             | step 3 shall be used for   |    |
|    |                             |                            |    |
|    |                             | verifying the accuracy of  |    |
|    |                             | the                        |    |
|    |                             |                            |    |
|    |                             | credential.                |    |
+----+-----------------------------+----------------------------+----+
| 13 | The CV Administration sends | None                       |    |
|    | a carrier snapshot segment  |                            |    |
|    | update to CVIEW.            |                            |    |
+----+-----------------------------+----------------------------+----+
| 14 | CVIEW receives the snapshot | **Verify the updated       |    |
|    | and updates its database.   | information sent**         |    |
|    |                             |                            |    |
|    |                             | **by the CV Administration |    |
|    |                             | has been**                 |    |
|    |                             |                            |    |
|    |                             | **updated in the CVIEW     |    |
|    |                             | database and**             |    |
|    |                             |                            |    |
|    |                             | **is accurate.**           |    |
|    |                             |                            |    |
|    |                             | Note: The information      |    |
|    |                             | recorded in                |    |
|    |                             |                            |    |
|    |                             | step 3 shall be used for   |    |
|    |                             |                            |    |
|    |                             | verifying the accuracy of  |    |
|    |                             | the                        |    |
|    |                             |                            |    |
|    |                             | update.                    |    |
+----+-----------------------------+----------------------------+----+
| 15 | CVIEW sends a snapshot      | None                       |    |
|    | segment update to SAFER.    |                            |    |
+----+-----------------------------+----------------------------+----+
| 16 | SAFER receives the snapshot | **Verify the updated       |    |
|    | and updates its database    | information sent**         |    |
|    |                             |                            |    |
|    |                             | **by CVIEW has been        |    |
|    |                             | updated in the**           |    |
|    |                             |                            |    |
|    |                             | **SAFER database and is    |    |
|    |                             | accurate.**                |    |
|    |                             |                            |    |
|    |                             | Note: The information      |    |
|    |                             | recorded in                |    |
|    |                             |                            |    |
|    |                             | Step 3 shall be used for   |    |
|    |                             |                            |    |
|    |                             | Verifying the accuracy of  |    |
|    |                             | the                        |    |
|    |                             |                            |    |
|    |                             | Update.                    |    |
+----+-----------------------------+----------------------------+----+
|    | Steps 17 and 18 are         |                            |    |
|    | applicable for states       |                            |    |
|    | electronically connected to |                            |    |
|    | the IFTA CH                 |                            |    |
+----+-----------------------------+----------------------------+----+
| 17 | The CV Administration sends | None                       |    |
|    | the IFTA Clearinghouse (CH) |                            |    |
|    | the Carrier's demographic   |                            |    |
|    | information.                |                            |    |
+----+-----------------------------+----------------------------+----+
| 18 | The IFTA CH receives the    | **Verify the Carrier's     |    |
|    | demographic information.    | demographic**              |    |
|    |                             |                            |    |
|    |                             | **information is           |    |
|    |                             | accurate.**                |    |
|    |                             |                            |    |
|    |                             | Note: The information      |    |
|    |                             | recorded in                |    |
|    |                             |                            |    |
|    |                             | step 3 shall be used to    |    |
|    |                             | verify                     |    |
|    |                             |                            |    |
|    |                             | the recap information.     |    |
+----+-----------------------------+----------------------------+----+
| 19 | CVIEW fulfills snapshot     | None                       |    |
|    | subscription for the        |                            |    |
|    | Roadside Operations System. |                            |    |
+----+-----------------------------+----------------------------+----+
| 20 | Roadside Operations         | **Verify the snapshot sent |    |
|    | downloads the subscription  | by CVIEW is**              |    |
|    | (snapshot).                 |                            |    |
|    |                             | **correct.**               |    |
|    |                             |                            |    |
|    |                             | Note: The information      |    |
|    |                             | recorded in                |    |
|    |                             |                            |    |
|    |                             | step 3 shall be used to    |    |
|    |                             | verify                     |    |
|    |                             |                            |    |
|    |                             | the vehicle snapshot.      |    |
+----+-----------------------------+----------------------------+----+
| 21 | **The ASPEN operator        | **Verify the snapshots     |    |
|    | queries SAFER/CVIEW for a   | returned are**             |    |
|    | Carrier and Vehicle         |                            |    |
|    | Snapshot**                  | **correct.**               |    |
|    |                             |                            |    |
|    | Note: ASPEN queries SAFER   | Note: The information      |    |
|    | for a Carrier Snapshot;     | recorded in                |    |
|    | ASPEN 32 queries SAFER or   |                            |    |
|    | CVIEW for a Carrier         | step 3 shall be used to    |    |
|    | Snapshot.                   | verify                     |    |
|    |                             |                            |    |
|    |                             | the vehicle snapshot.      |    |
+----+-----------------------------+----------------------------+----+

## 5.7 Scenario ID ETE-07: Carrier Submits IFTA Quarterly Tax Filing

***Test Configuration and Initial Conditions***

-   JHU/APL Facility Requirements

```{=html}
<!-- -->
```
-   None.

```{=html}
<!-- -->
```
-   User Facility Requirements

```{=html}
<!-- -->
```
-   Communications established between:

1.  The Carrier's Electronic Credentialing System and the State
    Commercial Vehicle (CV) Administration (i.e., Web Browser and Web
    Server)

2.  CV Administration and the State CVIEW System (CVIEW)

3.  CVIEW and SAFER

4.  ASPEN/ASPEN 32 and CVIEW/SAFER

5.  Roadside Operations and CVIEW

-   Test Roles

```{=html}
<!-- -->
```
-   The key test roles necessary to execute this test include:

```{=html}
<!-- -->
```
-   Master Test Conductor

-   CV Administration

-   Carrier

-   SAFER

-   CVIEW

-   Roadside Operations

-   ASPEN/ASPEN 32

-   Test Analyst

```{=html}
<!-- -->
```
-   Initial Conditions

```{=html}
<!-- -->
```
-   An IFTA Initial Registration has previously been processed

### [Test Case 5.07.01, Carrier Submits IFTA Quarterly Tax Filing]{.smallcaps} 

Test Summary

The master test conductor or the test analyst completes the checklist
for Web-based credential applications. The CV Administration may send a
Tax Filing Notification message to the Carrier(non-EDI). The Carrier
receives the filing notice. The Carrier requests the Tax Rate Tables and
Footnotes. The CV Administration sends the tables and footnotes to the
Carrier. The Carrier completes and sends the tax filing to the CV
Administration. The CV Administration validates the tax filing and
computes the tax liability. The CV Administration sends carrier snapshot
segment updates to CVIEW. CVIEW sends a segment update to the SAFER. The
Roadside Operations System receives the carrier snapshot from CVIEW.
Inspection personnel will use either ASPEN or ASPEN 32. If using ASPEN,
the inspector queries SAFER for a Carrier Snapshot. For inspectors using
ASPEN 32 units, query SAFER or CVIEW for a Carrier Snapshot.

Test Purpose

The objective of this End-to-End test is to ensure the products involved
in IFTA

credentialing work together properly. Specifically, the test will verify
the carrier is able to submit their quarterly IFTA tax filing and the
information is updated in all applicable databases, including the
Roadside Operations computer.

Acceptance Criteria

-   The Carrier receives the tax-filing acknowledgement from the CV
    Administration.

-   CVIEW updates its database with the new information (snapshot
    segment update).

-   SAFER updates its database with the new information (snapshot
    segment update).

-   Roadside Operations receives, updates, and displays the new
    information (snapshot segment update).

-   ASPEN/ASPEN 32 receives the correct snapshot from SAFER/CVIEW

Requirements Tested

The test criteria for credentials-related data flows and electronic
screening are based on standards found in COACH Part 5, and reflect
those requirements that are pertinent to this test case. See COACH Part
5 for a detailed cross reference of test cases to requirements tested.

Data Recording/Reduction/Evaluation Procedures

Examination of messages, databases, and displayed screens will show the
successful receipt of and update of information resulting from the
submission of the carrier's quarterly IFTA tax filing. The Test Analyst
will compare the appropriate database updates to the information entered
by the Carrier in step 1, to insure proper transaction sequencing and
data flow during the test. The checklist for Web-based credential
applications will be included in a summary of results.

Procedure

See Table 5-5 for the Master test procedure. The Carrier, using test
case data set 4.07.01 will input the data for the supplemental
application. Note that some steps are starred (). The Test Analyst will
examine these starred steps for conformance with the CVISN architecture
in post-test evaluation. Operator Actions are indicated in **BOLD**
print, whereas, System Actions are not in bold print.

Table 5--6.\
Test 5.07.01: Master Test Conductor Procedure

+-----------------------------------------------------------------------+
| > **Checklist: Web-based credential application process for IFTA      |
| > Quarterly Tax Filing:**                                             |
|                                                                       |
| -   Supports the following browsers:                                  |
|                                                                       |
|     \_\_\_\_Netscape 4                                                |
|                                                                       |
|     \_\_\_\_Internet Explorer 4                                       |
|                                                                       |
|     \_\_\_\_Internet Explorer 5.5                                     |
|                                                                       |
|     \_\_\_\_ Other (list in comments)                                 |
|                                                                       |
| -   Utilizes recommended primary identifiers in application data      |
|     fields:                                                           |
|                                                                       |
|     \_\_\_\_Carrier \-- US DOT \#                                     |
|                                                                       |
|     \_\_\_\_Vehicle \-- Vehicle Identification Number (VIN)           |
|                                                                       |
|     \_\_\_\_Vehicle \-- State & Plate                                 |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   Accurately displays the appropriate credential application form,  |
|                                                                       |
|     with all necessary data fields present and input validated.       |
|                                                                       |
|     (list exceptions in comments)                                     |
|                                                                       |
|     \_\_\_\_Yes                                                       |
|                                                                       |
|     \_\_\_\_No                                                        |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   User interface allows standard credential application functions   |
|     appropriate                                                       |
|                                                                       |
|     for this credential type. For IFTA Tax:                           |
|                                                                       |
|     \_\_\_\_ Display tax rates and credits from State                 |
|                                                                       |
|     \_\_\_\_Submit original filing                                    |
|                                                                       |
|     \_\_\_\_Submit amended filing                                     |
|                                                                       |
|     \_\_\_\_ Print copy of tax return                                 |
|                                                                       |
|     \_\_\_\_ Other (list in comments)                                 |
|                                                                       |
| -   Displays Invoice: \_\_\_\_Yes \_\_\_\_No                          |
|                                                                       |
| ```{=html}                                                            |
| <!-- -->                                                              |
| ```                                                                   |
| -   Supports payment by credit card: \_\_\_\_Yes \_\_\_\_No           |
|                                                                       |
|     or by ACH : \_\_\_\_Yes \_\_\_\_No                                |
|                                                                       |
|     or other means (list in comments): \_\_\_\_Yes \_\_\_\_No         |
|                                                                       |
| -   End-to-End process forwards snapshot updates to CVIEW:            |
|     \_\_\_\_Yes \_\_\_\_No                                            |
|                                                                       |
| ##                                                                    |
|                                                                       |
| -   CVIEW provides credential information to SAFER and Roadside       |
|     Systems: \_\_\_\_Yes \_\_\_\_No                                   |
+-----------------------------------------------------------------------+

+----+-----------------------------+----------------------------+----+
| St | System or Operator Action   | Master Test Criteria       | Pa |
| ep |                             |                            | ss |
|    |                             |                            | /\ |
|    |                             |                            | Fa |
|    |                             |                            | il |
+====+=============================+============================+====+
| 1  | The CV Administration may   | None                       |    |
|    | generate and send a Tax     |                            |    |
|    | Filing Notification message |                            |    |
|    | to the Carrier.             |                            |    |
+----+-----------------------------+----------------------------+----+
| 2  | The Carrier receives the    | None                       |    |
|    | Tax Filing Notification.    |                            |    |
+----+-----------------------------+----------------------------+----+
| 3  | The Carrier system may send | None                       |    |
|    | a request for the Tax Rate  |                            |    |
|    | Tables and corresponding    |                            |    |
|    | Footnotes from the CV       |                            |    |
|    | Administration.             |                            |    |
+----+-----------------------------+----------------------------+----+
| 4  | The CV Administration       | Note: In some states the   |    |
|    | receives the request from   | CV Administration will     |    |
|    | the Carrier.                | send a request to IFTA     |    |
|    |                             | Inc. in response to a      |    |
|    |                             | Carrier's request for the  |    |
|    |                             | current Tax Rate Tables    |    |
|    |                             | and Footnotes during the   |    |
|    |                             | tax filing. Other states   |    |
|    |                             | will store tax rates and   |    |
|    |                             | footnotes obtained from    |    |
|    |                             | IFTA Inc. periodically, or |    |
|    |                             | provide them on a Web      |    |
|    |                             | site.                      |    |
+----+-----------------------------+----------------------------+----+
| 5  | CV Administration sends the | None                       |    |
|    | Tax Rates Tables and        |                            |    |
|    | Footnotes to the Carrier.   |                            |    |
+----+-----------------------------+----------------------------+----+
| 6  | **The Carrier enters the    | None                       |    |
|    | IFTA Quarterly Tax Filing   |                            |    |
|    | Application into the        |                            |    |
|    | electronic credentialing    |                            |    |
|    | system and sends it to the  |                            |    |
|    | CV Administration.**        |                            |    |
|    |                             |                            |    |
|    | Record the following        |                            |    |
|    | information:                |                            |    |
|    |                             |                            |    |
|    | Credentials                 |                            |    |
|    |                             |                            |    |
|    | USDOT                       |                            |    |
|    | \_\_\_\_\_\_\_\_\           |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    | IFTA Account Number         |                            |    |
|    | \_\_\_\_\_\_\_\_\_\_\_      |                            |    |
|    |                             |                            |    |
|    | IFTA Base State             |                            |    |
|    | \_\                         |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    | Jurisdictions/weights       |                            |    |
|    | \_\_\_\_\_\_\_\_\_\_\_\_    |                            |    |
|    | \_\_\_\_\_\_\_\_\_\_\_\_\   |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
|    |                             |                            |    |
|    | Registrant Information      |                            |    |
|    |                             |                            |    |
|    | Contact Name                |                            |    |
|    | \_\_\_\                     |                            |    |
|    | _\_\_\_\_\_\_\_\_\_\_\_\_\_ |                            |    |
+----+-----------------------------+----------------------------+----+
| 7  | The CV Administration       | None                       |    |
|    | receives the IFTA Quarterly |                            |    |
|    | Tax Filing.                 |                            |    |
+----+-----------------------------+----------------------------+----+
| 8  | The CV Administration       | None                       |    |
|    | validates the tax filing.   |                            |    |
+----+-----------------------------+----------------------------+----+
| 9  | The CV Administration       | None                       |    |
|    | calculates the tax          |                            |    |
|    | liability and compares the  |                            |    |
|    | amount submitted by the     |                            |    |
|    | Carrier.                    |                            |    |
+----+-----------------------------+----------------------------+----+
| 10 | The CV Administration sends | None                       |    |
|    | a Tax Filing Acceptance     |                            |    |
|    | notice to the Carrier.      |                            |    |
+----+-----------------------------+----------------------------+----+
| 11 | The CV Administration sends | None                       |    |
|    | a snapshot segment update   |                            |    |
|    | to CVIEW.                   |                            |    |
+----+-----------------------------+----------------------------+----+
| 12 | CVIEW updates its database. | **Verify the updated       |    |
|    |                             | information sent by the CV |    |
|    |                             | Administration has been    |    |
|    |                             | updated in the CVIEW       |    |
|    |                             | database and is accurate.  |    |
|    |                             | The IFTA check flag should |    |
|    |                             | indicate tax payments are  |    |
|    |                             | current.**                 |    |
|    |                             |                            |    |
|    |                             | Note: The information      |    |
|    |                             | recorded in                |    |
|    |                             |                            |    |
|    |                             | Step 6 shall be used to    |    |
|    |                             |                            |    |
|    |                             | verify the accuracy of the |    |
|    |                             |                            |    |
|    |                             | update.                    |    |
+----+-----------------------------+----------------------------+----+
| 13 | CVIEW sends a snapshot      | None                       |    |
|    | segment update to SAFER.    |                            |    |
+----+-----------------------------+----------------------------+----+
| 14 | SAFER updates its database  | **Verify the updated       |    |
|    |                             | information sent**         |    |
|    |                             |                            |    |
|    |                             | **by CVIEW has been        |    |
|    |                             | updated in the**           |    |
|    |                             |                            |    |
|    |                             | **SAFER database and       |    |
|    |                             | accurate.**                |    |
|    |                             |                            |    |
|    |                             | Note: The information      |    |
|    |                             | recorded in                |    |
|    |                             |                            |    |
|    |                             | Step 6 shall be used to    |    |
|    |                             |                            |    |
|    |                             | verifying the accuracy of  |    |
|    |                             | the                        |    |
|    |                             |                            |    |
|    |                             | update.                    |    |
+----+-----------------------------+----------------------------+----+
| 15 | CVIEW fulfills snapshot     | None                       |    |
|    | subscription for the        |                            |    |
|    | Roadside Operations System  |                            |    |
|    | mailbox.                    |                            |    |
+----+-----------------------------+----------------------------+----+
| 16 | Roadside Operations         | **Verify the snapshot sent |    |
|    | downloads the subscription  | by CVIEW is**              |    |
|    | (snapshot).                 |                            |    |
|    |                             | **correct.**               |    |
|    |                             |                            |    |
|    |                             | Note: The information      |    |
|    |                             | recorded in                |    |
|    |                             |                            |    |
|    |                             | step 6 shall be used to    |    |
|    |                             | verify                     |    |
|    |                             |                            |    |
|    |                             | the vehicle snapshot.      |    |
+----+-----------------------------+----------------------------+----+
| 17 | **The ASPEN operator        | **Verify the snapshots     |    |
|    | queries SAFER/CVIEW for a   | returned are**             |    |
|    | Carrier Snapshot** Note:    |                            |    |
|    | ASPEN should query SAFER    | **correct.**               |    |
|    | for                         |                            |    |
|    |                             | Note: The information      |    |
|    | a Carrier Snapshot. ASPEN   | recorded in                |    |
|    | 32                          |                            |    |
|    |                             | step 6 shall be used to    |    |
|    | should query SAFER or       | verify                     |    |
|    |                             |                            |    |
|    | CVIEW for a Carrier         | the vehicle snapshot.      |    |
|    | Snapshot.                   |                            |    |
+----+-----------------------------+----------------------------+----+