# Presentation: 793913

## CVISN Pilot Program PlanTable of Contents

**CVISN Pilot Program Plan****Table of Contents**

-    Executive Summary
- 1  Introduction
- 2  CVISN Pilot Program Overview
- 3  FHWA Management Approach
- 4  State Management Approach
- 5  Carrier Management Approach
- 6  Methods & Tools
- A Glossary and References
- B Meeting Agendas
- C Workshop Overviews
- D CVISN Related Information
- Enclosure: CVISN Pilot Program Roadmap

- 1.1 Introduction
- 1.2 CVISN Deployment Strategy
- 1.3 CVISN Pilot Purpose
- 1.4 CVISN Pilot Scope

## Introduction

- The CVISN Pilot Program will provide funding to supplement funds currently being provided by other Federal, state, and private projects as required to enhance or modify existing projects and legacy systems to meet the objectives of the CVISN Pilot.
- The seven pilot states were selected in September of 1996. The selection was based upon applications submitted by the states in response to a **FHWA Request for Application (RFA) on the CVISN Model Deployment Program**. The CVISN State Pilots Projects builds upon the CVISN State Prototype projects and  CVISN core infrastructure projects.
- Maryland and Virginia were selected as the two CVISN prototypes in January of 1996. The Maryland and Virginia prototypes have scheduled multiple showcase operational tests throughout 1996 and 1997. Each showcase builds upon the preceding showcase until the full CVISN capability is completed at selected sites with selected carriers in the state.
- Following the showcases, the CVISN capabilities will be incrementally implemented across the prototype states by selecting, installing, training personnel and supporting a two week operational test at additional sites in the States. In a similar manner additional carriers are added.
- The CVISN infrastructure project developed an overall CVISN architecture which identifies open standards and interfaces for all CVISN systems. Conformance to the CVISN architecture ensures interoperability among CVISN systems. The CVISN infrastructure is also assisting with the development of common CVISN components where there are no existing commercial components.

**Introduction**

**CVISN Pilot Program Plan.** This document describes the plan for the CVISN Pilot Program. It describes the approach to showcasing and implementing the CVISN capabilities across the country by partially funding regional state pilots. The CVISN program work breakdown structure, schedule and critical success factors are described. The roles and responsibilities of the FHWA, the pilot states and the carriers are defined. The processes, methods and tools to support the Pilot Program are presented.** **
**For More Information:** To obtain more information, visit the CVO program Internet World Wide Web home page provided by the Johns Hopkins University Applied Physics Laboratory (JHU/APL) at
**http://www.jhuapl.edu/cvisn/            (all lower case) **
- This includes an on-line copy of the latest version of this document, as well as a file copy that can be downloaded. The *Introduction to Commercial Vehicle Informations System and Networks (CVISN),* which describes CVISN, is available at this site. Other CVISN documentation is also provided.
- Appendix A contains a list of CVISN references.  One of the references is the CVISN Glossary which contains all of the terms and acronyms used in this document. A short glossary of the most common terms is included in Appendix A for convenience.
- If you do not have access to the Internet World Wide Web, you can request additional paper copies of this document or find out more about the CVISN Program by contacting:
- 		John Hardy
- 	E-mail:	john.hardy@jhuapl.edu		Phone:	(301) 953-6000 x7072    		Fax:	(301) 953-6149			Address:	JHU/APL				Laurel, MD 20723 6099
- Please Comment on this Document: You may comment by Fax-ing or e-mailing comments to John Hardy. You may also use the Document Comment Evaluation at the end of this document.

## CVISN Nationwide Deployment Strategy

**1.  Introduction **

- Prototype
- MD & VA

- Pilot (Infrastructure, MD, VA, & 7 states from 7 regions)

- Expansion

- Full Deployment
- (All interested states)

- Plan

- ITS/CVO Plans & Roadmap; CVISN Operational Concept; CVISN Architecture Documentation

- Technology & operational demonstration to illustrate & refine concepts

- Model deployment of EDI, clearinghouses, SAFER, & state systems compatible with CVISN architecture

- Continuing deployment, operation & maintenance; EDI & DSRC standards

- 1994 - 1996

- 1996 - 1997

- 1996 - 1999

- 1998 - 2000

- 2000 - 2005

- CVO Mainstreaming
- Regions/States

## 1.  Introduction  CVISN Pilot Program Purpose

**1.  Introduction **** CVISN Pilot Program Purpose**

*To implement the primary CVO user services through a FHWA, State, and industry Partnership in multiple states to demonstrate their technical and institutional feasibility, costs, and benefits and to encourage further deployment.*

- The specific services to be implemented are:
- Safety Information Distribution
- Electronic Credentialing
- Electronic Clearinghouses
- Electronic Clearance

- Implementing these ITS/CVO services leads to:
- Safety
- Simplicity
- Savings

## 1. Introduction

**CVISN Pilot Scope**

- Info Requester

- ITDS

**Commercial / Government**

**Wireline / Wireless Services**

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

**State Systems**

- Registration

-   SAFETYNET

- OS/OW

- ASPEN

- Electronic Clearance

- NCIC

- Shipper

**Carrier Systems**

- Fleet Credentialing

- Fleet Administration

- Freight Administration

- Fleet HAZMAT Mngt

- On-Board Trip Monitoring

- Fleet Maintenance

- Financial Institution

- Fuel Tax

- Credentialing Interface

- CV Information Exchange

- Citation & Accident

- Titling

-  HAZMAT

- On-Board Communication

- On-Board CV Safety

- On-Board Cargo Monitoring

- ASAP

- Safety Info System

- CDL/DL

- UCR

- Capability not required for pilot

## CVISN Pilot Scope

**CVISN Architecture**
- The CVISN architecture (depicted on the preceding page) provides a technical framework for design and development of the CVISN Pilots. The architecture includes three basic types of systems: state systems, core infrastructure systems and carrier systems.
- The CVISN architecture does not describe a specific design. In most cases the specific design will be developed by the stakeholder that owns the system, typically a pilot state or carrier. Each state’s and carrier’s implementation will need to vary depending upon the existing legacy systems and the needs of the State or carrier.
- The CVISN architecture framework provides a means of ensuring interoperability of these various implementations by specifying open data interchange standards and the authoritative sources for electronic CVO credential, tax and safety data.
- FHWA is assisting the development of state and carrier CVISN designs and implementations compatible with the CVISN architecture through the CVISN Prototypes and CVISN Pilots.
**Involve Carriers in Pilot States**
- Each pilot state will establish cooperative agreements with representative carriers based in their state to participate in the pilot.  The carriers will participate in all phases of the pilot, from planning through implementation and operation.  They must commit to enhancing their information systems to implement ITS/CVO user services in a manner compliant with the CVISN architecture.

**CVISN Pilot Scope**

**Build the CVISN Core Infrastructure**
- There are several multi-state data sharing projects currently planned, under development, or operational that are required to support the CVISN pilot.  These are collectively referred to as the CVISN Core Infrastructure.  The current list is shown in the figure, although the final list may contain one or two additional systems.  The CVISN Pilot will augment the current funds for these systems as required to make them compatible with the CVISN architecture and standards
**Prototype & Establish Formal Standards**
- The pilot effort will be used to prototype EDI and DSRC standards in its early stages.  As the pilot proceeds, the project will work through standard development organizations (SDO’s) to get formal, open standards developed that incorporate lessons learned from the prototype and are incorporated into the final releases of the pilot systems.
**Integration of Primary ITS/CVO User Services**
- An important purpose of the pilot is to demonstrate the synergistic effects of providing user services in an integrated way.  Although some states may emphasize some services  by having earlier or more extensive deployment, the goal is to have at least some deployment of each ITS/CVO user service in each pilot state by the end of the pilot.
**Prepare for Full Scale Deployment**
- The CVISN Pilot will help prepare for the full deployment of CVISN in three ways.  First, it will establish the CVISN Core Infrastructure as an operational set of systems.  Future states that wish to implement ITS/CVO services will be able to connect to this infrastructure using documented and proven techniques.  Second, the pilot will support the definition of open DSRC and EDI standards.  Third, the pilot effort will produce a *CVISN Deployment Tool Kit.*  This will be a set of work products and lessons learned organized into a personal computer based set of tools that can easily be distributed to and used by other states.