# Presentation: 512051

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

- 6.1 Introduction
- 6.2 COACH
- 6.3 CVISN Workshops
- 6.4 Project Room
- 6.5 Regional Conferences
- 6.6 Tri-annual Plan Review and Update

## Introduction

- The methods and tools described here are to allow the Pilot States to take advantage of the expertise and lessons learned from the prototype states to implement the CVISN Pilots. Additionally, best practices in system engineering and project management have are been used to develop Critical Success Factors for the Pilot Program (see section 2.8). The tools and methods described here assist the states to implement the critical success factors.

**Introduction**

## 6. Methods and ToolsIntroduction

_**Lessons Learned**_
- Best Practices
- Critical Success Factors
- MD prototype Lessons Learned
- VA prototype Lessons Learned

_**Pilot State **_
_**Consultants**_

_**CVISN Operational &**_
_**Architectural Handbook**_
_**(COACH)**_

- JHU/APL points of contact assigned to each state

## Introduction

- The Maryland and Virginia lessons learned documentation is available through the CVISN project computer. The lessons learned and the best practices are also being used in the development of the CVISN Operational and Architectural Handbook documentation and the development of the workshops.
**CVISN Operational and Architectural Compatibility Handbook (COACH)**.The COACH is organized into three parts; the CVISN architecture baseline checklists, the CVISN project plan checklists, and the CVISN design baseline checklists. The set of checklist items ( architecture, plan or design) contain the requirements a pilot state needs to consider to implement a CVISN system pilot. Each part of the COACH is associated with one of the CVISN workshops ( described in the following paragraph). Each pilot state completes the appropriate part of the COACH in preparation for a CVISN workshop. The workshop then leads the pilot states through the steps necessary to produce a draft state CVISN architecture baseline, a draft state CVISN pilot project plan or a draft state CVISN design baseline. A baseline is defined as the current accepted and approved technical description for implementation. The architecture baseline is defined prior to the design baseline.

**Introduction**

**Project Room. **A CVISN multimedia Pentium PC with workgroup software and the **CVISN Tool Kit** is provided to each Pilot State to set-up a CVISN Project room. The workgroup software provides a method of communication with FHWA, FHWA contractors and other CVISN Pilot States. The CVISN Tool Kit contains comprehensive CVISN documentation along with lessons learned from the Maryland and Virginia prototypes.
**Workshops. **A series of workshops are provided to all the pilot states to assist them to plan and implement their CVISN Pilots. The scope workshop assists the Pilot States with a project scope assessment and the draft of a high level design. The project planning workshops assist with the draft project plan with measurable milestones. The design workshops assists with the draft system design baseline and subsystem details.** **
**Pilot State Consultants (points of contact).  **A consultant is assigned to each pilot state as a point of contact for CVISN planning and technical assistance. The pilot state consultant will assist each state to implement a CVISN compatible system.
**Regional Conferences. **Regional conferences are held every six months by the Regional “Champion” selected by the Mainstreaming program. The FHWA Regional and Division personnel assist the Regional Champion to coordinate the conferences in each region. The objective of the regional conferences are to share CVISN Pilot State progress and information with the other states and motor carrier associations in each region.
**Pilot Evaluation.** The FHWA provides evaluation support through an independent contractor. The contractor will work with the Pilot States to ensure a valid unbiased evaluation. The contractor will maintain an evaluation data base and perform the analysis needed to establish costs and benefits.

## 6. Methods and Tools CVISN Prototype Lessons Learned 

_**Lessons Learned Facilitated         **_
**             **_**Sessions**_
- 1-2 Maryland Sessions
- 1-2 Virginia Sessions
- APL & RSIS Session
- FHWA Session

_**Lessons Learned Interviews**_
- 2-3 Maryland Interviews
- 2-3 Virginia Interviews
- 2-3 APL & RSIS Interviews
- 2-3 FHWA Interviews

_**Lessons Learned Analysis and Compilation**_

_**Lessons Learned Feedback**_
- Maryland Sessions
- Virginia Sessions
- APL & RSIS Session
- FHWA Session

_**Lessons Learned Incorporation into Pilot**_
- Workshops
- Planning Meetings
- Documented

## 6. Methods and ToolsCVISN Operational and Compatibility Handbook (COACH)

_**COACH Part II**_ **Project Checklists**
**Scope Assessment**
**Master Milestone Schedule**
**Showcase Prototype Plan**
**Procurement Plan**
**Incremental Deployment Plan**
**Training Plan **

_**COACH Part I**_  **Architecture Checklists**
**Guiding Principles**
**ITS/CVO Capabilities**
**Institutional Framework**
**Carrier Systems**
**State Systems**
**Core Infrastructure Systems **

_**COACH Part III**_ **Design Checklists**
**Carrier Fleet, On-Board, Communications and Transponder Subsystems**
**State Registration, Fuel Tax, Hazardous  Material, OS/OW, Electronic Clearance, and** **Inspection Subsystems **
**IRP Clearinghouse, CDLIS, IFTA Clearinghouse, HAZMAT Clearinghouse, NMVTIS, MCMIS, and SAFER**

## CVISN Operational and Compatibility Handbook (COACH)

- Each pilot state will complete the checklist as a guide to assist their CVISN implementation and to ensure interstate interoperability. Each of the three parts of the COACH  is associated with a partnership level and a series of workshops.
- In order to keep the checklists short and concise, no explanation or description is provided. The details are provided by one of the reference documents cited at the beginning of each part and section.
**Part I, Architecture Baseline Checklists** are based upon the CVISN architecture. It lists** **all of the requirements necessary to conform to the CVISN architecture. The checklists are organized into six major sections; guiding principles, ITS/CVO capabilities, institutional framework, carrier systems, state systems and core infrastructure systems.
**Part II, Project Plan Checklists** are based upon the model showcase and deployment plans and lists in ten pages all of the requirements necessary to conform with the model showcase and deployment plans. The checklists in this part are also organized into six major sections; scope assessment, master milestones, showcase prototypes, procurement, incremental deployment and training.

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

**Part III, Design Baseline Checklists** are based on the model CVISN design and lists by subsystem all of the associated design requirements. The checklists in this part are organized by the carrier, CVISN core infrastructure, and state subsystems. A short glossary of common CVISN acronyms is provided in Appendix A. A complete definition of CVISN related abbreviations and acronyms are contained in the *Commercial Vehicle Information Systems Network (CVISN) Glossary*.

## 6. Methods and ToolsScope, Planning and Design Workshops

## Scope, Planning and Design Workshops

- The workshop sessions are facilitated by the JHU/APL engineering staff who have assisted the prototype implementations in Maryland and Virginia. Demonstrations of the Maryland and Virginia systems as well as question and answer sessions with state personnel are included in each workshop. The workshops are available to all the pilot states and provide the opportunity for each state to meet their peers from the other pilot states.
- The **Scope Workshop **assists the states to determine the scope of their CVISN pilot and to establish the high level CVISN system design baseline. This workshop is held at JHU/APL within the first 75 days after the selection of the pilot states. The pre-requisites for attendance are designation of the state’s CVISN project manager and CVISN system architect, review and preliminary completion of COACH Part I checklists and preliminary completion of the scope checklist. The COACH checklists and and the scope checklists are to be sent to JHU/APL ten days in advance of the workshop.
- The project manager is the person the state has selected to have overall responsibility for the CVISN Pilot Project. The CVISN system architect is the person the state has selected to have overall technical responsibility of the CVISN implementation.
- Each state is given three seats in the workshop. The expected workshop attendees are the state’s CVISN project manager, CVISN system architect and a member of the state’s information system’s staff. The output of the architecture workshop are a draft architecture baseline and a draft pilot scope assessment. The FHWA Region or Division person

**Scope, Planning and Design Workshops**

- responsible for the CVISN Pilot is also expected to attend.
- The** Project Planning  and Evaluation Workshops **assist the states to establish a CVISN draft project plan with major milestone schedules and evaluation objectives. The workshop is held in two sessions.
- The ***first session*** is held 15 to 45 days after the scope workshop. The pre-requisites for attendance are an approved architecture baseline, an approved scope assessment, review and preliminary completion of the first half of Coach Part II checklists, a preliminary staffing plan, initial meetings of the Carrier Advisory Council and the Inter-Agency Council and a draft list of carriers to participate in the CVISN pilot. The approved architecture baseline, COACH checklists and the staffing plans are to be sent to JHU/APL a week in advance of the workshop.
- Each state is given 3 seats in the workshop. The expected attendees are the state’s CVISN project manager, the CVISN system architect and the CVISN deputy project manager. The output of the first session is a draft CVISN showcase plan with measurable major milestone schedules, staffing plans, dependencies and an preliminary showcase equipment procurement list. The CVISN deputy project manager is the person responsibility for project planning support to the project manager. The FHWA Region or Division person responsible for the CVISN Pilot is also expected to attend.
- The ***second session*** is held 30 days after the completion of the first showcase. The prerequisites for this session are completion of the second half of the COACH Part II checklists and approved showcase plan and design baseline. The output of the second session is a draft CVISN implementation plan, a draft CVISN training plan and a preliminary deployment equipment procurement list.

## Scope, Planning and Design Workshops (continued)

- The** Design Workshops** assist the states to create the CVISN design baseline. The first in a series of design workshops is held within the first four months after the selection of the pilot states. The pre-requisites for attendance are an approved showcase plan, an agreed set of evaluation objectives, selected pilot carriers, preliminary completion of the COACH Part III and a draft list of subsystem alternatives.  The approved showcase plan, COACH checklists and list of subsystem alternatives are to be sent three days in advance of the workshop.
- Each state is given four seats in the workshop. The workshop is composed of half day sessions which go through subsystem functions such as registration, fuel tax and state inspection. The expected workshop attendees are the state’s CVISN system architect and representatives from the state’s lead agency responsible for each of the subsystems being addressed. The output of the design sessions are detailed draft design baselines for each subsystem along with design rationale.
- The workshops will be held in the System Analysis Laboratory at the JHU/APL. The System Analysis Laboratory facilitates interactive development of strategic plans, operational concepts, system architectures and other forums needing to assess alternatives. This laboratory has workgroup software and a network of laptop computers that allow rapid survey, analysis and prioritizing of issues and ideas. Trained facilitators lead the workshops to ensure successful sessions.

**Scope, Planning and Design Workshops (continued)**

- The workshops are primarily for the Pilot States to complete technical and planning material needed for the CVISN Pilots. The workshops are intensive sessions in which ‘real work’ is done. The workshop format is composed of short presentations followed by State breakout sessions and State presentations. FHWA Regional Champions and training personnel are welcome to attend the sessions as observers.

## 6. Methods and ToolsProject Room

_**CVISN Networked PC**_
**Multimedia Pentium System**
**Workgroup software for data  conferencing**
**World Wide Web Access Programs**
**PC Software Package to Modify & Print Documents**

_**CVISN Tool Kit**_
**Prototype State Documents **
- MD & VA System Design
- MD & VA Showcase Plans
- MD & VA Deployment Plans
**Simulations & Models**
**CVISN Documentation**
- CVISN Roadmap
- CVISN Architecture
- CVISN Operational Concept
- EDI & DSRC Standards
- COACH
**Distributed on a Bernoulli or CD**

- When a state is selected as a CVISN pilot state it receives the CVISN Tool Kit and the CVISN PC to setup up the CVISN project room. The project room acts as the repository for the architecture baseline, the design baseline and the project plan. It also serves as the communication hub for data conferencing through the provided workgroup software

## 6. Methods and ToolsTri-annual Plan Review and Update

- Plan Change Proposals/ Plan Updates
- Detailed Work Plan for Next 120 Days
- Architecture and Design Baselines
- Planning and Assessment
- Baseline Change Proposals

- FWHA CVISN
- Pilot Program

***Work Breakdown Structure***
***(Partial)***

***Gantt Schedule***
***(Partial)***

***CVISN System Design***

- Connecticut
- CVISN Pilot

- Kentucky
- CVISN Pilot

- Michigan
- CVISN Pilot

- Clearinghouses

- Electronic
- Clearance

- Colorado
- CVISN Pilot

- Electronic
- Credentials

- Safety
- Information

- Info Requester

- ITDS

- IRP Clearinghouse

**CVISN**
**Core Infrastructure**

- IFTA Clearinghouse

- NMVTIS

- CDLIS

- MCMIS

- SAFER / Data mailbox

- HAZMAT Clearinghouse

**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

- Unified Carrier Register

- 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

- Op Auth

- Capability not required for pilot

## 6. Methods and ToolsRegional Conferences

- Each Mainstreaming designated regional “champion” sponsors a CVISN conference every six months
- FHWA Region and Division provide support
- All states in the region are invited
- Regional CVISN “champion” arranges
- and facilitates conferences
- Regional “champions” participate in Architecture, Project Planning and Evaluation and Design Workshops
- All regional “champions” participate
- in a JHU/APL workshop to plan regional
- conferences

_**Objective**_: Promote CVISN Deployment within regions by sharing CVISN Pilot State progress and information with all states in the region

## This page intentionally blank.