# Presentation: 495553

## CVISN Guides

- Management Guides
*Introductory Guide to CVISN *
*CVISN Guide to Program and Project Planning*
*CVISN Guide to Phase Planning & Tracking*
- Technical Process Guides
*CVISN Guide to Top-Level Design*
*CVISN Guide to Integration & Test*
- Technical Application Guides
*CVISN Guide to Safety Information Exchange*
*CVISN Guide to Credentials Administration*
*CVISN Guide to Electronic Screening*

## Improved credentials administration should make government and business more efficient.

**Carriers**

**State CV**
**Administration**
**Systems**

**Clearinghouses**

**Other States**

**Application**

**Renewal Notice**
** ****and Data**

**Invoice**

**Payment/Notice of Payment**
**(via EFT or other)**

**Credential**

**Details**

**Summary of**
**fees due/**
**owed**

**State-to-clearinghouse ****details from approved applications/tax returns;**
**Clearinghouse-to-state ****report on info processed, including summary of fees due from/owed to state);**
**IRP CH also supports state-to-state payments**

**Apply for credentials**
**File tax returns**
**Make payments**

**Process applications and tax returns**
**Evaluate**
**Issue credentials**
**Accept electronic payments**

**IFTA and IRP CH support base state agreements**
**IRP CH also supports electronic funds exchange between states**

## Vision:  Electronic Business Transactions

**Carrier**

**Base State**

**Shipper, Bank, Insurer,**

**Lessor, Service Bureau**

**Standard**

**Electronic**

**Data Interchange**

**(EDI)**

_**Transactions**_

**Credentials, Taxes, **

**Safety Records,**

**HAZMAT, Insurance,**

**Shipments,**

**Payments**

**Interstate Transactions**

**Canada**

**Mexico**

**WIRELINE Wide Area Communications**

## Functional Thread Diagram:IRP Supplement, Add Vehicle  CVIEW updates SAFER (MD Design using VISTA/RS Product and InterCAT) 

**Generic State Roadside Systems**

**Generic State Commercial Vehicle Administration Systems**

**Carrier Systems**

**CVISN **
**Core Infrastructure**
**Systems**
** ****(National/Regional)**

**CDLIS**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**RSPA HazMat**

**ASAP Analysis **
**Admin/CAPRI**

**Service Providers**

**Internet**
**Tools**

**Other Carrier**
**Systems**

**ASAP**
**MCDC**

**CV Info Exchange**
**Window (CVIEW)**

**Credentialing**
**Interface (CI)**

**Transponder**

**Carrier Commercial**
**Vehicle**

**Web CAT**

**Licensing &**
**Insurance**

**E-Screening**
** ****Enrollment**

**Other Jurisdictions**

- 1

- 5

**VISTA/RS**

- 15

- 8

- 14

- 4

- A

- BCD

- 9, 16

- 10, 17

- 12,
- 19

**Credentialing **
**System **
**(e.g., CAT)**

- 2, 3

- 6

- 7

- 13

**IRP Office**

**IRP**
**Clearinghouse**

- B

- C

- D

- 11, 18

## CVISN Guidelines for Interface Design

## A state Web site approach provides a person-to-computer interface.

**Carrier**

**State**

**Credentialing**
**Systems with**
**Web Site**

**World Wide Web**

**HTML or XML, HTTP**
- Web standards;
- no credentialing
- standards used

**Web **
**Browser**

*States can provide electronic credentialing using a Web site.  The carrier would access the Web site using a commercial browser (e.g., Netscape) and manually enter the required data. *

- Credentialing
- Web
- Site

- Web
- Files

- Data
- Base

- Carrier

- MVA DB
- (stored
- procedures)

- Browser

- Core
- Credentialing
- Interface

- IRP Office
- CAT

- CI UI
- Client

- State
- CVIEW

- Example Web-Enabled CI System Design

- State Systems

**Legend**:
- solid blue arrows indicate
- access through firewall

**DMZ**

- IRP
- backend

- Stand-Alone
- CAT

**Firewall 2**

**Firewall 1**

## The standard CVISN Level 1 credentials administration interfaces illustrated using the generic state system design

**Generic State Commercial Vehicle Administration Systems**

**Carrier Systems**

**Service Providers**

**Internet**
**Tools**

**Other Carrier**
**Systems**

**ASAP**
**MCDC**

**CV Info Exchange**
**Window (CVIEW)**

**Credentialing**
**Interface (CI)**

**Web CAT**

**E-Screening**
** ****Enrollment**

**X12 TS **
**286, 997**

- KEY

- Open standards directly associated with electronic credentialing
- Interfaces associated with other aspects of Credentials Administration
- (maintaining snapshots, supporting base state agreements via
- clearinghouses)
- Internet standards used to support electronic credentialing

**X12 TS 151, **
**286, 813, 997**

**X12 TS 151, **
** ****813, 997**

**CVISN **
**Core Infrastructure**
**Systems**
** ****(National/Regional)**

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**RSPA HazMat**

**ASAP Analysis **
**Admin/CAPRI**

**Licensing &**
**Insurance**

- CR in process:

**X12**
**TS **
**285,**
**824,**
**997**

**X12 TS **
**285, **
**824, 997**

**X12 TS **
**286, 997**

**X12 TS **
**286, 997**

**X12 TS **
**826, 997**

**X12 TS **
**285, 824, **
**997**

**X12**
** ****TS **
**285, **
**824, **
**997**

**X12 TS **
**286, 997**

**Credentialing **
**System **
**(e.g., CAT)**

- CR in
- process:

**SAFER**

## EDI Interface Specifications

- ANSI ASC X12 Standards

- Application-Specific Implementation Guides & Code Directories, e.g., TS 286
- 	Vol. I - IRP					(Vol. II - IRP Interstate)
- 	Vol. III - IFTA (Credentials & Interstate)	Vol. IV - OS/OW
- 	(Vol. V - Intrastate Registration)		FHWA Code Directory

- Jurisdiction-specific
- business rules

- Review Baseline Specifications & jurisdiction-specific information

- COACH Part 4, Interface Specification Checklists (“The Big Picture”)

- Jurisdiction’s existing database designs

- To be published by each State beginning in 1999

***Jurisdiction-specific Motor Carrier E-Credentialing EDI Interface Control Document (ICD)***
***(www.state.<mystate>.us/.../MC EC EDI ICD)***

## Telecommunications & Network Specifications

- Network Technology Specifications (e.g., ISDN, frame relay)

- Networking Services (e.g., Internet provider, AAMVAnet)

- Jurisdiction-specific
- policies & procedures

- Review Baseline Specifications & jurisdiction-specific information

- Protocol Standards (e.g., SNA, TCP/IP)

- Jurisdiction-specific network design

- To be published by each State beginning in 1999

***Jurisdiction-specific Motor Carrier E-Credentialing EDI Interface Control Document (ICD)***
***(www.state.<mystate>.us/.../MC EC EDI ICD)***

## A stand-alone CAT (PC CAT) provides a computer-to-computer interface.

- Or Service Bureau

**State**

- A stand-alone CAT (PC CAT) provides a computer-to-computer interface.

**Internet,**
- Dial-up, or VAN

**EDI credentialing**
**standards exist.**

**Stand-alone CAT**

**Stand-alone CAT**

- Optional use for state branch offices

**Credentialing **
**Systems**

*A carrier would enter vehicle information using the stand-alone CAT, where it would be stored locally.  The stand-alone CAT would exchange credentialing information with the state using standards. *

**Notes:**
The current CVISN Architecture specifies the use of ANSI X12 EDI for a computer-to-computer interface.  EDI standards have been developed for e-credentialing.  ANSI maintains the standards, and APL is maintaining the guidance for how to use them for CVO applications.  
The use of a stand-alone PC CAT was a good first step to establishing EDI standards for a computer-to-computer interface.  It solved the “chicken & egg problem” of carriers not wanting to invest in software until states were ready, and vice versa.  It allowed states to make a relatively small investment in developing a CAT in parallel with the development of a CI.
The initial implementation of the architecture was the Carrier Automated Transaction (CAT) residing on a PC.  A state would accept electronic transactions to the Credentialing System (through the Carrier Interface (CI)) using EDI standards.  Kentucky, Maryland and Minnesota are implementing or have implemented such an interface.  A state could also make the PC CAT available for carriers on a walk-up basis at a state’s branch offices.
The PC CAT solution may be most useful as an interim step during the next couple years until CAT modules become commonly available as part of Fleet Management System packages.
APL is starting to explore using XML in place of EDI.  Based on the prototype activities and the survey results, FMCSA may decide to direct APL to develop XML usage  guidelines.

## A CAT module could be integrated into

**State**

- A CAT module could be integrated into
-  existing fleet management systems to provide a computer-to-computer interface

**Internet, **
- Dial-up, or VAN

**EDI credentialing**
**standards exist.**

**Fleet Management System (including CAT Module)**

**Credentialing**
**Systems**

*CAT credentialing capabilities are integrated in carrier Fleet Management Systems (FMS) that already contain carrier and vehicle related information needed for credentialing and use EDI for financial information. The CAT module in the FMS would exchange credentialing information with the state using standards. *

**Notes:**
Typically medium and large size carriers have fleet management software (FMS) systems that support many of the tasks associated with their operations.  These systems often exchange financial and billing information using EDI standards.  They also contain inventory information on the carrier’s fleet of vehicles.  
Incorporating CAT capabilities into the FMS would allow the motor carriers to leverage their existing investment in FMS systems by automating and integrating the credentials administration process with other business functions. 
FMS systems may be “home grown”, if the carrier is large enough, or they can be purchased from software vendors.  Software vendors may see that including automated credentialing capabilities provides a  marketing advantage, and develop the CAT capabilities as part of their product.  However, it will not be cost effective for a software vendor to develop the software until a sufficient number of states commit to using automated credential transactions using standards; then the development costs can be spread over their customer base. 
Integrating credentialing into FMS systems is consistent with CVISN Architecture for computer-to-computer interface, if EDI standards are used. From state’s point of view, this is compatible with PC CAT.

## A CAT module could be integrated into

**State**

- A CAT module could be integrated into
-  existing fleet management systems to provide a computer-to-computer interface

**Internet, **
- Dial-up, or VAN

**XML credentialing**
**guidelines could be developed.**

**Fleet Management System (including CAT Module)**

**Credentialing**
**Systems**

*CAT credentialing capabilities are integrated in carrier Fleet Management Systems (FMS) that already contain carrier and vehicle related information needed for credentialing. The CAT module in the FMS would exchange credentialing information with the state using XML toolset. *

**Notes:**
Typically medium and large size carriers have fleet management software (FMS) systems that support many of the tasks associated with their operations.  These systems often exchange financial and billing information using EDI standards.  They also contain inventory information on the carrier’s fleet of vehicles.  
Incorporating CAT capabilities into the FMS would allow the motor carriers to leverage their existing investment in FMS systems by automating and integrating the credentials administration process with other business functions. 
FMS systems may be “home grown”, if the carrier is large enough, or they can be purchased from software vendors.  Software vendors may see that including automated credentialing capabilities provides a  marketing advantage, and develop the CAT capabilities as part of their product.  However, it will not be cost effective for a software vendor to develop the software until a sufficient number of states commit to using automated credential transactions using standards; then the development costs can be spread over their customer base. 
Integrating credentialing into FMS systems is consistent with CVISN Architecture for computer-to-computer interface, if EDI standards are used. From state’s point of view, this is compatible with PC CAT.

## Dual Interface: A state could implement both

**Carrier 1**

**State**

**Credentialing**
**Systems with **
**Web Site**

- Dual Interface: A state could implement both
-  a Web site and a computer-to-computer interface.

*This approach gives carriers a choice of options.  It provides the benefits of both interface types, at additional cost to the state.*

**World Wide Web**

**HTML or XML, HTTP**

**Web **
**Browser**

**PC CAT or CAT Module**

**E-mail or FTP**

**EDI / XML / **
**other file format**

**Carrier 2**

## Keep the same “back end” processes, regardless of the external interfaces for credentialing

- State Systems

- Web & XML-
- Enabled
- Credentialing
- Interface

- IRP

- Stand-Alone
- CAT

**Database**

- IFTA
- Reg

- IFTA
- Tax
- Filing

- CVIEW

**Terminal**
**Server**

- Terminal
- Client

**EDI I/F**

**XML I/F**

- Fleet Management System

**Core CI**

**C**
**A**
**T**

- Browser

**Credentialing **
**Web Site**

**Web Database**

**Notes:**
In this figure, the focus is on credentialing interfaces.
There are at least three choices for interfaces: EDI or XML file exchanges, or an interactive Web interface.
The first choice shown is the stand-alone CAT.  The CAT exchanges information with the state’s Credentialing Interface.  The carrier (or service provider) owns or leases the CAT product, and data are stored on the carrier’s (or service provider’s) system.
The second approach is for the carrier to access electronic credentialing services through a Terminal Client.  In this approach, the CAT is owned or leased by whoever owns the Terminal Server (the state or a service provider).
Both CAT-based approaches use EDI.
The third approach is a Web site solution.  The carrier uses his browser to access the state’s Web site for electronic credentialing.  A combination of HTML, XML, dynamic HTML, and/or XHTML may be used.
The fourth approach shown is for the carrier to use a fleet management system that has built-in electronic credentialing support.  The interface could be either XML or EDI.
Regardless of the interface used to interact with the carrier, the processing of the carrier-provided inputs should be the same in the CI and the legacy credentialing systems.

## States are encouraged to implement CVISN Level 1 capabilities incrementally in a series of steps using a structured process

**Write**
**State CVISN**
**Program Plan**

**1B**

**Establish Funding & Contracts**

**1C**

**Develop State**
**Top-Level Design**

**1A**

**Notes:**
TIME: 1 minute
In the first workshop (Scope Workshop) you started to develop a preliminary top-level system design.
In this workshop (Planning Workshop) you will begin the planning process, and will develop pieces of a program plan.  
States are encouraged to implement CVISN Level 1 capabilities incrementally in a series of steps using a structured process.
A phase is a period of time defined for planning purposes to allow incremental delivery of a complex system.  
“Phase n” refers to multiple phases, each 3-6 months long.  
The first phase is devoted to system design and project planning.  
Each subsequent phase focuses on delivering a coordinated set of product versions (a.k.a. releases) that incrementally build to the overall CVISN Level 1 capability.  
For each phase, states are encouraged to update the Program Plan and System Integration Schedule.
In this Planning workshop, we focus on step 1B - developing a program plan.  You will also begin to think about the contracting process for procuring products and services.

## Each state develops a top-level design by addingCVISN capabilities to existing systems

*   *

*   *

- Each state develops a top-level design by addingCVISN capabilities to existing systems

**Notes:**

Use this as an overhead transparency, pointing to it as you move through the description of each step.

Walk through the details of the process for Phase 1A, using the explanatory text on the next several pages.
Even though the steps are shown as sequential, the process actually involves a great deal of feedback and iteration.
Throughout the process, identify issues, actions and decisions.
Publish the final results as a State CVISN Design Description.

## A planning process is necessary to plan the work and communicate among team members.

**Create the Work Breakdown Structure**

**Define the Organization**

*   *

*   *

**Define the Processes**

**Assign the Work to Organizations**

**Define Milestones & Schedules**

**1**

**2**

**3**

**4**

**5**

**6**

***Plan Program and Projects***

***Feedback & Iteration***

**Estimate Costs & Resources**

**7**

**Notes:**
TIME: 5 minutes.
Walk through the steps.  The details for each one are shown on the next several pages.  Recommend that you NOT show those slides.  Just hit the high points of each one as you present this slide.
Be sure to emphasize the iterative nature of the planning process
Step 1 - You defined program objectives as part of setting the Scope for CVISN in your state.  In this step, you should also identify the initial projects that will be part of CVISN in your state.  (Pre-Work A: Top-Level Design; Workshop Sessions 3, 9)
Step 2 - The WBS decomposes the tasks to be done in a product-oriented hierarchical representation. We’ll start by developing the first three levels.  The projects you’ve identified should appear at the 2nd or 3rd level, and you’ll add details in later sessions. (Workshop Sessions 3, 4, 5, 6, 9)
Step 3 - Show the two organizational dimensions (the agencies supporting the program, and the reporting lines essential to program success) on two different organization charts. (Pre-Work D: State Agencies; E: Program Organization; Workshop Sessions 3, 9) 
Step 4 - Your program should have defined processes (i.e., descriptions about how you will do business) for the activities you want to be common across all projects.  (Pre-Work B: Coach Part 2; G: State process descriptions; Workshop Sessions 3, 9)
Step 5. Assigning work to organizations  is often called “mapping the WBS to the org chart.”  The assignments must be made for every part of every level of the WBS.  Another part of assigning work is making decisions about alternative approaches to accomplishing work.  The “Build or Buy” decision-making process involves deciding what tasks or products will be accomplished or developed by state staff, and what tasks or products will be procured.  In this step you’ll develop a procurement strategy. (Pre-Work E: Program Organization; F: Signed MOA; Workshop Sessions 3, 4, 5, 6, 7, 9) 
Step 6 - In program planning, at this scheduling step, you define the integrated capabilities you intend to demonstrate in phases, and identify critical milestones that will help you measure progress towards completing those phased program objectives.  (Pre-work C: How existing plans affect CVISN; G: State process descriptions; Workshop Sessions 3, 4, 5, 6, 9) 
Step 7 - Estimate costs and resources.  (Do this step after the workshop.) Cost estimates included in the program plan are usually based on rough ideas of the effort and procurement required to accomplish each item in the WBS.  Include a written rationale called the basis of estimate.  The basis of estimate indicates whether the estimate is based upon past experience, analogy, expert judgment, or further breakdown of the item.  Match known funding sources to the estimated program needs.  
The next viewgraph projected is on page 3-30.

## The final phase of program organization is to obtain funding and contract for necessary products and services.

**Prepare Funding Request Documents**

**Obtain Funding Commitments**

**Prepare Technical Specifications**

**Issue RFP**

**Evaluate Proposals**

**1**

**2**

**3**

**4**

**5**

**6**

***Fund & Contract***

***Feedback & Iteration***

**Award Contracts**

**7**

- The final phase of program organization is to obtain funding and contract for necessary products and services.

**Notes:**
Of all the responsibilities the Program Manager has, obtaining and maintaining funding is probably the most important.
The funding and contracting processes are state-specific, and you know them well.
In this workshop, we’ll spend a little time (in session 7)  talking about planning procurement activities, and you’ll work on developing a procurement strategy.
Other than that, we won’t focus on these steps.

## Each state develops detailed designs and implementssystems adapted to its unique requirements

*   *

- Each state develops detailed designs and implementssystems adapted to its unique requirements