CVISN for Kansas Program Plan May 2000 Kansas CVISN Program Plan June 2000.

CVISN for KansasProgram Plan May 2000

Kansas CVISNProgram Plan

June 2000


Section 1

CVISN Definition

Table of Content

Executive Summary

Signature Page


CVISN Definition

What is the definition of CVISN? The term CVISN (Commercial Vehicle Information Systems and Networks) refers to the collection of information systems and communications networks that support commercial vehicle operations (CVO). These include information systems owned and operated by governments, motor carriers, and other stakeholders. The Federal Highway Administration (FHWA) CVISN program is not trying to create a new information system, but rather to create a way for existing and newly designed systems to exchange information through the use of standards and available communications infrastructure. The CVISN program provides a framework or “architecture” that will enable government agencies, the motor carrier industry, and other parties engaged in CVO safety assurance and regulation to exchange information and conduct business transactions electronically. The goal of the CVISN program is to improve the safety and efficiency of commercial vehicle operations.

The CVISN Architecture is the CVO part of the National Intelligent Transportation Systems (ITS) Architecture. It includes standards for communications technologies such as electronic data interchange (EDI) and dedicated short range communication (DSRC). These standards are being developed to promote interoperability and efficiency. The Transportation Equity Act for the 21st Century (TEA-21) requires that ITS projects funded from the Highway Trust Fund must be consistent with the National ITS Architecture and applicable standards.

Introductory Guide to CVISNPOR-99-7186

Preliminary Version P.1 May 1999Johns Hopkins University - Applied Physics Lab

1-1


Table of Content

Section 1 CVISN Definition

Table of Content

Executive Summary

Signature Page

Section 2 Mission Statement

Introduction

Organization Structure

Program Goals

Definition of CVISN Level 1 Deployment

Section 3 Program Areas

Entire Work Breakdown Structure

Section 4 Projects

Section 5 Key Features

Network Diagram of Kansas

Section 6 Milestones

Funding

Section 7 Products

Deliverables

Appendix 1 - Coach

2 - Issues/ Decisions

3 - Contact List

4 - Acronyms

1-2


Executive Summary

The Mission of the Kansas CVISN program is to create an information network using advanced technology that will enhance efficiency, safety, compliance and enforcement for commercial vehicle operations. The information network includes the exchange of ideas between the government partners and the motor carrier industry. CVISN initiatives to be undertaken will promote the economic well being of Kansas by facilitating the movement of goods for business and industry. State agencies in Kansas are dedicated to the application of cost-effective intelligent transportation technologies and streamlining existing processes that will improve transportation safety and administrative efficiency of both motor carriers and the state. CVISN is a collection of state, federal and private sector information systems and communication networks that support commercial vehicle operations. Kansas’ CVISN Program consists of three major program areas:

1. Safety Projects

2. Credentials Projects

3. Electronic Screening Projects

Each of these program areas are detailed in this report and specific projects are outlined for implementation as part of the Kansas CVISN program.

Kansas’ CVISN Program is administered by an Inter-Agency Coordinating Group, including the Kansas Department of Transportation, Kansas Department of Revenue, Kansas Highway Patrol, Kansas Corporation Commission, Division of Information Systems and Communications, Kansas Motor Carrier Association, Kansas Turnpike Authority, Federal Motor Carrier Safety Administration and Information Network of Kansas. A combination of State and Federal funding supports the program.

CVISN Champions are System Architect Leo Luttjohann and Program Manager Ken Gudenkauf. Carrier Groups are represented by the Kansas Motor Carriers Association.

1-3


Kansas CVISN Program PlanApproval Signatures

Commitment is key to the success of the Kansas CVISN Program. Through their endorsement this page represents the commitment of the following individuals and their organization and/or agency’s support of this project. - This signature page will be completed after the June CVISN Design Workshop.

. * . Kansas Department of Transportation E. Dean Carlson, Secretary

. * . Kansas Highway Patrol Col. Don Brownlee, Superintendent

. . Division of Information Systems and Communications Donald C. Heiman, Director

. * . Kansas Motor Carrier Association Tom Whitaker, Interim Executive Director

. * . Kansas Corporation Commission John Wine, Commission Chair

. * . Kansas Department of Revenue Karla Pierce, Secretary

1-4

. * . Kansas Turnpike Authority Michael L. Johnston, President/CEO

. . Information Network of Kansas Debra Luling, General Manager

* = Agencies that have previously supported the Kansas CVO Business Plan


Section 2

Mission Statement

Introduction

Organization Structure

CVISN Program Goals



Mission Statement

The mission of the Kansas Intelligent Transportation System for Commercial Vehicle Operations (ITS/CVO) program is to create an information network using advanced technology that will enhance efficiency, safety, compliance and enforcement for commercial vehicle operations

The information network includes the exchange of ideas between the government partners and the motor carrier industry. As new technologies and improved software become available, this cooperative exchange of information will be utilized to evaluate processes and technologies to determine deployment initiatives that improve commercial vehicle operations. Initiatives to be undertaken will promote the economic well being of Kansas by facilitating the movement of goods for business and industry. The design of CVISN allows for national and regional electronic exchange of data and information. State agencies in Kansas are dedicated to the application of cost-effective intelligent transportation technologies and streamlining existing processes that will improve transportation safety and administrative efficiency of both the motor carriers and state.

In March 2000 the Kansas Department of Transportation completed a Statewide ITS Plan (KITS) and have categorized all ITS projects under the “KITS” Planning Process. This plan recognizes CVISN and has defined a program area within the statewide plan to address ITS/CVO activities. The Statewide ITS plan addressed CVO, Rural and Urban ITS projects and focused on mainstreaming ITS into the KDOT business structure. KITS follows the State Transportation Improvement Program (STIP) process. The Statewide ITS plan has an evaluation phase that will occur in 2002.

Introduction

2-1


Inter-AgencyCoordinating Group

C h a irK e n G u d e n ka u f

System Architect

L e o L u tt jo h a n nD IS C & Je re m y F rie se n

Program Adm inistrator/FacilitatorM a tt V o lz

Safety ProjectP ro jec t L ead er

Je re m y F rie se nE d B o rin g

Credentials ProjectP ro jec t L ead er

A l G e rs tn e r

E-Screening ProjectP ro jec t L ead er

K e n G u d e n ka u f

Inform ation TechnologyP rog ram S u p p ort

K D O R /K H P /K D O T

CVISN Program

P rog ram M an ag erK e n G u d e n ka u f

Planning & OutreachUniversity Consortium

P rog ram S u p p ortC T R E & K M C A

CVISN Advisory Com m itteeP rog ram S u p p ort

R e p re se n ta tive s fro md iffe re n t ju risd ic tio n s

Departm ent ofT ransportation

C V IS N E xecu tive S p on sorE . D e a n C a rlso n

CVISN Program Organization

2-2


D ivis ion ofIn form ation S ystem san d C om m u n ication s

(D IS C )

D epartm en t ofA dm in is tration

D ivis ion ofE m ergency

M an agem en t

A dju tan tG en eral

S pec ial O peration sB u reau

F ield O perationsB u reau

A dm in is trativeS ervices B u reau

P ortA dm in is tration

K an sasH igh w ay P atrol

D ivis ion of A viation

D ivis ion ofE n gin eerin g an d D es ign

D ivis ion of P lan n in g& D evelopm en t

D ivis ion of O perations

D ivis ion ofA dm in is tration

D epartm en t ofT ran sportation

D ivis ion ofV eh ic les

D ivis ion ofTaxation

D epartm en t O fR even u e

S afety & C om plian ce

O peratin g A u th ority

Tran sportationD ivis ion

K an sas C orporationC om m iss ion

O ff ice of th eS tate T reasu rer

S ta te of K a ns a sG ove rn or

CVISN Supporting Agencies

2-3

Kansas Turnpike Authority

Kansas Motor Carrier Association

Federal Motor Carrier Safety Administration

Information Network of Kansas


Intelligent

Transportation

Systems (ITS)

Commercial

Vehicle

Operations (CVO)

ITS/CVO

CVISN

International

Trade

Modernization

I

B

C

Commercial

Vehicle

Systems and

Networks

(CVISN)

Architecture

International Border

Clearance Architecture

National ITS Architecture

ITS/CVO Architecture as part of the National Architecture

2-4


ITS/CVO Architecture as part of the National Architecture

TravelerSubsystems

InformationServiceProvider

TrafficManagement

EmissionsManagement

EmergencyManagement

TransitManagement

TollAdministration

Fleet and FreightManagement

CenterSubsystems

Roadside Subsystems

Vehicle

TransitVehicle

CommercialVehicle

EmergencyVehicle

Veh

icle

to

Veh

icle

Com

mu

nic

atio

ns

PersonalInformation

Access

RemoteTravelerSupport

Roadway

Planning

TollCollection

ParkingManagement Commercial

VehicleCheck

Wireless Wide AreaCommunications

Wireline Wide Area CommunicationsD

edic

ated

Sho

rt R

ange

Com

mun

icat

ions

CommercialVehicle

Administration

Vehicle Subsystems

2-5


Program Goals• Improve freight mobility. Reduce administrative burden on motor carriers and state agencies. Increase compliance to motor carrier regulations. Improve safety through reduced congestion. Better use of enforcement and technology resources. Conduct safety inspections on “At Risk” motor carriers. Improve administration of credentials statewide. Preserve infrastructure. Meet Level 1 CVISN Deployment as shown on Page 2-7.

Taking on the CVISN Program sets in motion a mixture of projects that deploy utility and performance in the three major functional areas, as shown in the figure below.

Program Vision,Objectives, and

Strategies

Define Project

Plan Project

ImplementProject

Operate &Maintain

redes

ign

evaluate monito

r

scopeDefine Project

Plan Project

ImplementProject

Operate &Maintain

DefineProject

PlanProject

ImplementProject

Operate &Maintain

2-6

Safety

Credentials

ElectronicScreening



An organizational framework for cooperative system development has been established among state agencies and motor carriers.

A State CVISN System Design has been established that conforms to the CVISN Architecture and can evolve to include new technology and capabilities

All the following elements of three capability areas have been implemented using applicable architectural guidelines, operational concepts and standards:

• Safety Information Exchange

– ASPEN (or equivalent) at all major inspection sites *1

– Connection to SAFER *2

– CVIEW (or equivalent) for snapshot exchange within state and to other states

• Credentials Administration

– Automated processing (i.e. carrier application, state application processing, credential issuance, fuel tax filing) of at least IRP & IFTA credentials; ready to extend to other credentials (intrastate, titling, OS/OW, carrier registration, HAZMAT). Note: Processing does not included e-payment. *3

– Connection to IRP & IFTA Clearinghouses *4

– At least 10% of the transaction volume handled electronically; ready to bring on more carriers as carriers sign up; ready to extend to branch offices where applicable

• Electronic Screening

– Implemented at a minimum of one fixed or mobile inspection site

– Ready to replicate at other sites

*1 Kansas uses ASPEN

*2 Kansas is currently connecting to SAFER

*3 Kansas currently accepts electronic permitting

*4 Kansas is currently using the IRP Clearinghouse

2-7


Section 3

CVISN Program AreasSafety Information ExchangeCredential AdministrationElectronic Screening

Entire Work Breakdown Structure


CVISN Program Areas

• Safety Information Exchange

– CVIEW - Planning

– PRISM - Future

– Accident Reporting - Future

• Credential Administration

– IRP Clearinghouse - Completed

– Permit Batch Processing - Completed

– Internet Application for Permits - Started

– Electronic IRP Applications - Future

– Electronic IFTA Applications - Future

– Electronic IFTA Quarterly Reports - Future

– TRIS - Truck Routing Information System - Started

• Roadside Operations

– Electronic Clearance - Future

3-1

Exchanging safety information is intended toimprove safety performance.Monitor safety performance in safetyassurance programs;Collect driver/vehicle inspection data,carrier compliance information, citation &accident data;Provide safety & credentials snapshots tothe roadside for screening & inspections;Check safety history before grantingcredentials;Share information with other states

CVISN Core Infrastructure

1

2

3

4

5

Legacy SystemsAssociated with

Credentialing


Safety

- SAFETYNET 2000- CAPRI

Kansas CV Roadside CheckStations (Fixed or Mobile)

- Roadside Operations- Screening- ASPEN- Citation & Accident SAFER

MCMIS

EDI

Kansas Administrative Systems

CVIEW

Leg Sys Mods

Leg Sys Mods

LSIs EDI

LSIsEDI or

or

AFF

Interim approachfor ASPEN

1

2 3

4

5

Safety Information Exchange

2 5

3-2CVISN for KansasProgram Plan May 2000

Standardized transactions enable:carriers to file for credentials from their offices,states to process applications automatically,states to exchange information electronically tosupport base state agreements

Standardized transactions support fee paymentsamong payers, payees, and financial institutions(banks).

Credentials Administration

CVIEW

Motor Carrier

IFTA and IRPClearinghouses

(Support base stateagreements)

Credentialing System(e.g., CAT - CarrierAutomated Transaction)

Kansas

EDI

EDI

EDI

EDI: Electronic Data Interchange LM: Legacy Modification LSI: Legacy System Interface SSE: State-Specific Enhancement

Carrier Bank

IRP CHBank

KS.State Bank


Credential or FuelTax Filing

1

3

4

4

LMs

CredentialingInterface (CI)

Server

2

SSE

EDI

CI / LegacyWorkstations

(For manual review or entry ofcredential / tax filing info)

LSIs

or

or

1

2

3

4

4

4

3-3CVISN for KansasProgram Plan May 2000

Roadside electronic screeningfocuses resources on high riskoperators:Identify transponder, carrier,vehicle via DSRC transponder& standard messagesPull in untagged vehicle toidentify carrier & vehicleCheck snapshot informationwhen making screeningdecisionsBefore issuing a citation, checkwith authoritative source forlatest status

1

2

3

4

CVIEW SAFER

CVISN CoreInfrastructure

State Roadside Systems

Sensor/Driver Comm

Screening Roadside Operations

Other StateSystems

DSRC

1

2

3

4

Citation & Accident

Leg Sys Mods

LM

LM

LSI or EDI

LM

MCMISEDI

LSIs

or

34

4

4EDI

3-4

Electronic Screening



Work Breakdown Structure (WBS)

3-5

WBS Task Management as of May 22, 2000 Working Days

Start Finish Resource Names

1 Program Management 730 days 3/10/00 1/30/03 1.1 Project Management 730 days 3/10/00 1/30/03 Ken Gudenkauf1.2 Develop CVISN Program Plan 51 days 3/13/00 5/22/00

2 System Engineering & Integration 730 days 3/10/00 1/30/032.1 Project Management 730 days 3/10/00 1/30/03 Leo Luttjohann

3 Safety Project 321 days 3/10/00 6/15/013.1 Project Management 321 days 3/10/00 6/15/013.2 System Engineering & Integration 321 days 3/10/00 6/15/013.3 Subcontract & Procurement Mgt 321 days 3/10/00 6/15/013.4 CV Information Exchange Window (CVIEW) 221 days 6/5/00 4/19/01

3.4.1 3.4.1 Obtain CVIEW 2.0 and Server/Software 80 days 6/5/00 9/26/003.4.2 Upgrade ASPEN 16 to ASPEN 32, point

connection to CVIEW50 days 10/2/00 12/13/00

3.4.3 Upgrade CVIEW 2.0 to CVIEW 3.0 50 days 10/2/00 12/13/003.4.4 Create interstate snapshot data 30 days 1/2/01 2/12/013.4.5 Merge intrastate snapshot data into CVIEW 30 days 2/12/01 3/26/013.4.6 Roll out to KCC investigators 35 days 3/1/01 4/18/013.4.7 Operations & Maintenance 1 day 4/19/01 4/19/01

3.5 Performance & Registration Info. Syst.Management (PRISM)

40 days 4/20/01 6/15/01

3.5.1 Determine System Requirements 20 days 4/20/01 5/17/01 Jackie Miller3.5.2 Secure Funding 20 days 5/18/01 6/15/01 Jackie Miller

3.6 Accident Reporting 40 days 4/20/01 6/15/013.6.1 Determine System Requirements 20 days 4/20/01 5/17/01 Jeremy Friesen3.6.2 Secure Funding 20 days 5/18/01 6/15/01 Jeremy Friesen

4 Credentials Project 740 days 6/1/99 4/25/024.1 Project Management 301 days 3/10/00 5/17/014.2 System Engineering & Integration 301 days 3/10/00 5/17/014.3 Subcontract & Procurement Mgt 301 days 3/10/00 5/17/014.4 Web Based Projects 300 days 3/13/00 5/17/01

4.4.1 Internet Permit Application 75 days 3/13/00 6/26/004.4.2 IRP Web Based Application 75 days 6/27/00 10/11/00 Al Gerstner - KDOR4.4.3 IFTA Web Based Application 75 days 10/12/00 1/31/01 Patricia Platt - KDOR4.4.4 SSRS Web Based Application 75 days 2/1/01 5/17/01 Jackie Miller

4.5 Automated Interfaces 235 days 3/10/00 2/13/014.5.1 Legacy System Interface 65 days 3/10/00 6/9/004.5.2 Permit File Processing - Completed 10/99 1 day 3/10/00 3/10/00 Leo Luttjohann4.5.3 IRP Clearinghouse 1 day 3/10/00 3/10/004.5.4 IFTA Clearinghouse 234 days 3/10/00 2/13/01 Patricia Platt - KDOR4.5.5 IFTA Quarterly Filings 60 days 9/5/00 11/30/00 Patricia Platt - KDOR

4.6 Administrative Processing 740 days 6/1/99 4/25/024.6.1 Truck Routing Information System (TRIS) 740 days 6/1/99 4/25/024.6.2 Single Windows Based User Interface for MC

applications60 days 3/10/00 6/2/00

5 Electronic Screening Project 120 days 6/3/02 11/20/025.1 Project Management 120 days 6/3/02 11/20/02 Ken Gudenkauf5.2 System Engineering & Integration 120 days 6/3/02 11/20/02 Ken Gudenkauf5.3 Subcontract & Procurement Mgt 120 days 6/3/02 11/20/02 Ken Gudenkauf5.4 Decide static locations 120 days 6/3/02 11/20/02 Ken Gudenkauf5.5 Determine transponder administration and

business model120 days 6/3/02 11/20/02 Ken Gudenkauf


Section 4Projects

Commercial Vehicle Information Exchange WindowProject SummaryProject OverviewProcess FlowThread DiagramProject Work Breakdown Structure

Permit Application via InternetProject SummaryProject OverviewProcess FlowThread DiagramProject Work Breakdown Structure

International Registration PlanProject SummaryProject OverviewProcess FlowThread DiagramProject Work Breakdown Structure

International Fuel Tax AgreementProject SummaryProject OverviewProcess FlowThread DiagramProject Work Breakdown Structure

Truck Routing Information SystemProject SummaryProject OverviewProcess FlowThread DiagramProject Work Breakdown Structure

Electronic ClearanceProject SummaryProject OverviewProcess FlowThread DiagramProject Work Breakdown Structure


The Commercial Vehicle Information Exchange Window (CVIEW) is an electronic dataexchange system that will provide carrier, vehicle, and driver safety and credentialinformation to fixed and mobile roadside inspection stations, state agencies, and other thirdparty users. This information will allow roadside inspectors to select vehicles and/or driversfor inspection based on the number of prior inspections of the carrier for which the vehicleand driver is currently operating, as well as carrier, vehicle, and driver safety and credentialhistorical information. It will permit state agencies to perform safety checks before issuingcertain types of credentials and it will support the business needs of third party users such asinsurers obtaining safety data to support their underwriting processes.

CVIEW will be owned by and located in each state that elects to use it as a data exchangemethod. CVIEW is designed to facilitate the exchange of inter- and intrastate safety andcredential information among users and systems within the state as well as among CVISNcore infrastructure systems, e.g., SAFER.

The Federal Motor Carrier Safety Administration (FMCSA) has provided carrier safety datato industry and the public for many years via telephone requests and paper reports. TheCVIEW System makes it possible to offer this information, as well as credential data,electronically. Access will be provided to carrier, vehicle, and driver snapshots, a conciseelectronic record of safety and credential data including identification, size, commodityinformation, safety record, including safety rating (if any) and roadside out-of-serviceinspection data, registration and permit information, and other related data.

Commercial Vehicle Information Exchange Window (CVIEW)Summary Information

4-1


Goal(s)•Provide information to roadside inspection station•Support business needs of users•Facilitate the electronic exchange of safety and credential information

Project Description Provide connection with SAFER, IRP, IFTA and Intrastate Registrations databases

Project ObjectiveProvide roadside inspectors safety and credential information for both interstate and intrastate carriers

Project Documentation

Work Breakdown Task 3.4


4 CVO User Service Bundle4.4 Commercial Vehicle Administration Process

2 Manage Commercial Vehicles

Process Specifications (pspecs)

2.3.3.1 Provide Commercial Vehicle Check station Communications 2.3.3.2 Provide Commercial Vehicle Inspector Handheld Terminal Interface2.3.3.3 2.3.3.4 Carry-out Commercial Vehicle Roadside Safety Screening 2.3.3.5 Carry-out Commercial Vehicle Roadside Inspection2.3.4 Detect Commercial Vehicle 2.3.4 2.3.5 Provide Commercial Vehicle Roadside Operator Interface 2.3.6 Provide Commercial Vehicle Reports

CVIEW Project

4-2


CVIEW Process Flow

4-3

ASPEN

CVIEW State Owned

Legacy Systems

Roadside Inspector

SAFERCVISN Core System

Roadside Inspectors will use the current ASPEN software to access CVIEW. The CVIEW application/server will provide snapshot data from both in-state (legacy) and the National Safety database (SAFER).


CVIEW Thread Diagram (1)

4-4

Record inspections electronically and report them to SAFER and MCMIS via CVIEW (ASPEN-32, SAFETYNET 2000, SAFER/CVIEW 3.0)

KANSAS Roadside Systems

KANSAS Commercial Vehicle Administration Systems

Carrier Systems

Credentialing System

(e.g., CAT)


Systems (National/Regional)

CDLIS

IRPClearinghouse

IFTAClearinghouse

NMVTIS

MCMIS

SAFER

IFTA Registration

LSI

LM

RSPA HazMat

ASAP Analysis Admin/CAPRI

Sensor/Driver Comm

ScreeningLM

Roadside Operations

LSI

LM

ASPEN-32LM

Citation &Accident

LSI

LM

Service Providers

InternetTools

Other CarrierSystems

ASAPMCDC

CredentialingInterface (CI) IFTA Tax

Processing

LSI

LM

Web CAT

Intrastate VehRegistration

LSI

LM

DriverLicensing

LSI

LM

Licensing &Insurance

E-Screening Enrollment

TitlingLSI

LM

SSRSLSI

LM

IRPLSI

LM

HazMatLSI

LM

OS/OWLSI

LM

SAFETYNET2000

LSI

LM

CAPRILSI

LM

Treasury orRevenue

LSI

LM

Other Jurisdictions

Transponder

Carrier CommercialVehicle

CV Info ExchangeWindow (CVIEW)

1A

C

D

EC

B

23


CVIEW Thread Diagram (2)

4-5

1. ISS request is sent to CVIEW.

2. ISS is processed and returned to inspector.

3. Inspection data is sent to CVIEW via ASPEN.

A. Snapshots are updated from SAFER to CVIEW.

B. Snapshots from SAFER are merged with intrastate snapshots and updated to ASPEN (laptops).

C. Inspections are updated to SAFER / other jurisdictions from CVIEW.

D. Hand entered inspections are sent to MCMIS from Safetynet.

E. MCMIS updates to SAFER.


CVIEW WBS

4-6

WBS Task Name Working Days Start Finish Resource Names 3.4 CV Information Exchange Window (CVIEW) 221 days 6/5/00 4/19/01

3.4.1 3.4.1 Obtain CVIEW 2.0 and Server/Software 80 days 6/5/00 9/26/003.4.1.1 Setup server and install software 20 days 6/5/00 6/30/00 Jeremy Friesen3.4.1.2 Test Installation 20 days 7/3/00 7/31/00 Jeremy Friesen3.4.1.3 Establish Connection with SAFER 20 days 8/1/00 8/28/00 Jeremy Friesen3.4.1.4 Use existing ASPEN 16 to test connection with CVIEW 2.0 20 days 8/29/00 9/26/00 Jeremy Friesen

3.4.2 Upgrade ASPEN 16 to ASPEN 32, point connection to CVIEW 50 days 10/2/00 12/13/003.4.2.1 Acquire Software from JHU APL 5 days 10/2/00 10/6/00 Jeremy Friesen3.4.2.2 Test Connection to CVIEW 5 days 10/9/00 10/13/00 Jeremy Friesen3.4.2.3 Installation and Training 40 days 10/16/00 12/13/00 Jeremy Friesen

3.4.3 Upgrade CVIEW 2.0 to CVIEW 3.0 50 days 10/2/00 12/13/003.4.3.1 Aquire CVIEW 3.0 Software 5 days 10/2/00 10/6/00 Jeremy Friesen3.4.3.2 Test Installation 5 days 10/9/00 10/13/00 Jeremy Friesen3.4.3.3 Implementation and Training for KHP Troopers 40 days 10/16/00 12/13/00 Jeremy Friesen

3.4.4 Create interstate snapshot data 30 days 1/2/01 2/12/013.4.4.1 Create snapshots from legacy systems 20 days 1/2/01 1/29/01 Leo Luttjohann3.4.4.2 Load Snapshots onto CVIEW 5 days 1/30/01 2/5/01 Leo Luttjohann3.4.4.3 Transfer snapshots from CVIEW to SAFER 5 days 2/6/01 2/12/01 Leo Luttjohann

3.4.5 Merge intrastate snapshot data into CVIEW 30 days 2/12/01 3/26/013.4.5.1 Create snapshots from legacy systems 20 days 2/12/01 3/12/01 Leo Luttjohann3.4.5.2 Load Snapshots onto CVIEW 5 days 3/13/01 3/19/01 Leo Luttjohann3.4.5.3 Transfer snapshots from CVIEW to SAFER 5 days 3/20/01 3/26/01 Leo Luttjohann

3.4.6 Roll out to KCC investigators 35 days 3/1/01 4/18/013.4.6.1 Buy Computers for KCC 10 days 3/1/01 3/14/01 Jackie Miller3.4.6.2 Install and Test ASPEN 32 Software for KCC 5 days 3/15/01 3/21/01 Jackie Miller3.4.6.3 Training of KCC Investigators 20 days 3/22/01 4/18/01 Jackie Miller

3.4.7 Operations & Maintenance 1 day 4/19/01 4/19/013.4.7.1 Handoff to Operations & Maintenance Staff 1 day 4/19/01 4/19/01 Jeremy Friesen


Permit Application via Internet Summary Information

Electronic Filing of Applications, Web/Internet Based and Direct Connection Systems (FTP), provide benefits to both states and carriers, eliminating paperwork, reducing errors and improving workflow. These systems include the processes for accepting and reviewing applications issuing credentials, auditing and reporting. Credentials are the focus of one ITS/CVO user service, Commercial Vehicle Administrative Process, as outlined in the National ITS Architecture

Vehicles that exceed size limits, or are transporting non-divisible loads in excess of gross weight or axle weight regulations, qualify for special hauling permits for each individual load. These permits, which are valid for a limited number of days, specify the route the vehicle must take. Kansas also issues annual permits to eligible carriers.

A permit must be obtained for each State through which the vehicle will travel. In most cases, carriers must obtain an individual permit from each State, although some States have established reciprocity agreements to accept each other’s permits. Special permitting regulations vary widely, and sometimes conflict, among the States.

4-7


Goal(s)

•Accelerate credential process•Use electronic data transfer to improve speed and accuracy

Project Description Provide 24/7 access for motor carriers requesting Kansas legalization permits.

Project ObjectiveImprove access and work flow of permit issuance.


Work Breakdown Task 4.4.1

National ITS Architecture 4 CVO User Service Bundle

4.4 Commercial Vehicle Administration Process



2.1.1 Manage Commercial Fleet Electronic Credentials and Tax Filing2.1.2 Provide Commercial Fleet Static Route2.5.3 Update Permits and Duties Store 2.5.2 Obtain Electronic Credential and Tax Filing Payment

Permit Application via Internet Project

4-8


Permit Application via Internet Process Flow

4-9

Permit Requestor WEB/INTERNET

Application

TRIS (Truck Routing

Information System)

MCCP (Motor Carrier Central Permit)

TRIS will be added when available

Payment will be made via escrow account or credit card.

Permit applications will be process via web based application.


Permit Application via Internet Thread Diagram (1)

4-10

Kansas State Roadside Systems

Kansas State Commercial Vehicle Administration Systems

Carrier Systems



CDLIS

IRPClearinghouse

IFTAClearinghouse

NMVTIS

MCMIS

SAFER

IFTA Registration

LSI

LM

RSPA HazMat


Sensor/Driver Comm

ScreeningLM

Roadside Operations

LSI

LM

ASPENLM

Citation &Accident

LSI

LM

Service Providers

InternetTools


ASAPMCDC



Transponder


IFTA Tax Processing

LSI

LM


LSI

LM

DriverLicensing

LSI

LM


TitlingLSI

LM

SSRSLSI

LM

IRPLSI

LM

TRISLSI

LM

OS/OWLSI

LM

SAFETYNETLSI

LM

CAPRILSI

LM

Treasury orRevenue

LSI

LM


(e.g., CAT)

Kansas CVISN Architecture

Perm

it Issuin

g Locations

KD

OT

, KD

OR

and

KH

P

1

12

4

5

3


Permit Application via Internet Thread Diagram (2)

4-11

1. Carrier sends Permit request to permit clerk or credential interface.

2. If needed, Routing request is sent to TRIS application for verification / changes.

3. Permit is returned to carrier.

4. Permit information is provided via snapshot to CVIEW.

5. If needed snapshot is provided to SAFER.


Permit Application via Internet WBS

4-12

WBS Task Name Working Days Start Finish Resource Names 4.4.1 Internet Permit Application 75 days 6/1/00 9/15/00

4.4.1.1 Development by INK of internet based Permit application. 75 days 6/1/00 9/15/004.4.1.1.1 Developing Requirements 20 days 6/1/00 6/28/00 INK -Joe Blubaugh4.4.1.1.2 Developing Program Specs and Event Schedule 20 days 6/29/00 7/27/00

4.4.1.1.2.1 Develop program specifications and event schedule 10 days 6/29/00 7/13/00 INK -Joe Blubaugh4.4.1.1.2.2 Approval by KDOR of Program Specifications 10 days 7/14/00 7/27/00 Al Gerstner - KDOR

4.4.1.1.3 Software Programming 30 days 7/28/00 9/8/004.4.1.1.3.1 Programming 30 days 7/28/00 9/8/00 INK -Joe Blubaugh4.4.1.1.3.2 Buy chips and soda for programmers 1 day 7/28/00 7/28/00 Leo Luttjohann4.4.1.1.3.3 Testing in house - Alpha version 29 days 7/31/00 9/8/00 INK -Joe Blubaugh

4.4.1.1.4 Hand off to KDOR 5 days 9/11/00 9/15/004.4.1.1.4.1 Implementation and Training for KDOR 5 days 9/11/00 9/15/00 Al Gerstner - KDOR


International Registration Plan (IRP) Electronic Filing Summary Information


The IRP process includes five types of activities:

The base State accepts and processes IRP applications from the carriers in its jurisdiction, and issues credentials (license plates and cab cards) to certify the right to operate in all IRP jurisdictionsThe Base State collects application and registration fees on an annual basis from the carriers in its jurisdiction, and obtains operating mileage estimates by IRP jurisdiction for each carrier’s fleet.The Base State interacts with other IRP jurisdictions to document carrier operations, and to transfer shares of collected fees to other jurisdictions in proportion to each carrier’s operating mileage.The Base State conducts periodic audits of its carriers. Current IRP rules requires that the Base State audit 15 percent of the carriers in its jurisdiction every 5 years. The audits cover the authenticity of the mileage figures reported by the carrier.Each member State may issue temporary permits to vehicles that are not apportioned for travel in its jurisdiction. These permits are valid for travel during a limited amount of time (typically 2 to 10 days). Depending on the State, these temporary permits may be secured on the spot at weigh stations or ports-of-entry, or in advance by mail, phone, fax, or wire service.

4-13


Goal(s)

•Accelerate the credential process•Move toward a paperless environment•Use electronic data transfer to improve speed and accuracy

Project Description

Provide means of electronic data exchange between state and motor carriers

Project Objective

Meet and exceed CVISN Level 1 requirements






Process Specifications (pspecs) 2.5.1-Manage Commercial Vehicle Trips and Clearances 2.5.2-Obtain Electronic Credential and Tax Filing Payment 2.5.3-Update Permits and Duties Store 2.5.4-Communicate w/ Other Commercial Vehicle Administration System 2.5.5-Manage Commercial Vehicle Credentials and Enrollment 2.5.6-Output Commercial Vehicle Enrollment Data to Roadside Facilities 2.5.7-Process Commercial Vehicle Violations 2.5.8-Process Data Received from Roadside Facilities 5.4.6-Process CV Violations 7.4.1.1-Process Commercial Vehicle Payments

IRP Electronic Filing Project

4-14


IRP Electronic Filing Process Flow

4-15

Fleet Manager /

Service Provider

State Agency / Credential Interface

CVISN Core Systems(Clearinghouse,

SAFER)

State Legacy Systems

Fleet managers will use electronic data exchange, via Web/Internet or File transfers to apply for and accept required operating credentials.

Communications networks will connect to CVISN core systems to provide data exchange reducing work load on state agency and motor carrier.


IRP Electronic Filing Thread Diagram (1)

4-16



Carrier Systems


(e.g., CAT)



CDLIS

IRPClearinghouse

IFTAClearinghouse

NMVTIS

MCMIS

SAFER

IFTA Registration

LSI

LM

RSPA HazMat


Sensor/Driver Comm

ScreeningLM

Roadside Operations

LSI

LM

ASPEN-32LM

Citation &Accident

LSI

LM

Service Providers

InternetTools


ASAPMCDC


Processing

LSI

LM

Web CAT


LSI

LM

DriverLicensing

LSI

LM



TitlingLSI

LM

SSRSLSI

LM

IRPLSI

LM

HazMatLSI

LM

OS/OWLSI

LM

SAFETYNET2000

LSI

LM

CAPRILSI

LM

Treasury orRevenue

LSI

LM

Other Jurisdictions

Transponder



1

2

3

5

4

1a

2a

6

6


IRP Electronic Filing Thread Diagram (2)

4-17

1. Carrier sends application via electronic file or enters data to credential interface.

2. Application is processed.

1a. 2a. Temporary Credential is sent back to carrier

3. CVIEW Snapshot is updated.

4. SAFER Snapshot is updated.

5. Data is sent to IRP Clearinghouse monthly.

6. Data is updated to MCMIS and other jurisdictions.


IRP Electronic Filing WBS

4-18

WBS Task Name Working Days Start Finish Resource Names 4.5.3 IRP Clearinghouse 1 day 3/10/00 3/10/00

4.5.3.1 Programming for IRP Clearinghouse - Completed 6/97 1 day 3/10/00 3/10/00 Leo Luttjohann4.5.3.2 Update File Layout to Provide SAFER Data 30 days 1/2/01 2/12/01 Leo Luttjohann


International Fuel Tax Agreement (IFTA) Electronic Filing Summary Information


The IFTA process comprises five sets of activities:

The Base State accepts and processes IFTA applications from the carriers in its jurisdiction, and issue credentials (fuel tax licenses and vehicle decals) to certify the right to operate in all IFTA jurisdictions.The Base State accepts and processes fuel tax returns on a quarterly basis from the carriers in its jurisdiction, and collects or refunds the net tax balance due for each carrier.The Base State interacts with other IFTA jurisdictions to document carrier operations and fuel tax collections, and to transfer tax funds due to other jurisdictions by carriers in the Base State.The Base State conducts periodic audits of its carriers. Current IFTA rules requires that the Base State audit 15 percent of the carriers in its jurisdiction every 5 years.Each State may issue temporary permits to vehicles that are not licensed for travel in its jurisdiction. Such permits are valid for travel during a limited amount of time (typically 2 to 10 days). Depending on the State, these temporary permits may be secured on the spot at weigh stations or ports-of-entry, or in advance by mail, phone, fax, or wire service.

4-19


Goal(s)

•Accelerate the credential process•Move toward a paperless environment•Use electronic data transfer to improve speed and accuracy

Project Description

Provide means of electronic data exchange between state and motor carriers

Project Objective

Meet and exceed CVISN Level 1 requirements






Process Specifications (pspecs) 2.5.1-Manage Commercial Vehicle Trips and Clearances 2.5.2-Obtain Electronic Credential and Tax Filing Payment 2.5.3-Update Permits and Duties Store 2.5.4-Communicate w/ Other Commercial Vehicle Administration System 2.5.5-Manage Commercial Vehicle Credentials and Enrollment 2.5.6-Output Commercial Vehicle Enrollment Data to Roadside Facilities 2.5.7-Process Commercial Vehicle Violations 2.5.8-Process Data Received from Roadside Facilities 5.4.6-Process CV Violations

7.4.1.1-Process Commercial Vehicle Payments

IFTA Electronic Filing Project

4-20


IFTA Electronic Filing Process Flow

4-21

Fleet Manager / Service Provider

State Agency / Credential Interface

CVISN Core Systems(Clearinghouse,

SAFER)

State Legacy Systems

Fleet managers will use electronic data exchange, via Web/Internet or File transfers to apply for and accept required operating credentials.

Communications networks will connect to CVISN core systems to provide data exchange reducing work load on state agency and motor carrier.


IFTA Electronic Filing Thread Diagram (1)

4-22



Carrier Systems


(e.g., CAT)



CDLIS

IRPClearinghouse

IFTAClearinghouse

NMVTIS

MCMIS

SAFER

IFTA Registration

LSI

LM

RSPA HazMat


Sensor/Driver Comm

ScreeningLM

Roadside Operations

LSI

LM

ASPEN-32LM

Citation &Accident

LSI

LM

Service Providers

InternetTools


ASAPMCDC


Processing

LSI

LM

Web CAT


LSI

LM

DriverLicensing

LSI

LM



TitlingLSI

LM

SSRSLSI

LM

IRPLSI

LM

HazMatLSI

LM

OS/OWLSI

LM

SAFETYNET2000

LSI

LM

CAPRILSI

LM

Treasury orRevenue

LSI

LM

Other Jurisdictions

Transponder



1

2

3

5

4

1a

2a

6

6


IFTA Electronic Filing Thread Diagram (2)

4-23

1. Carrier sends application via electronic file or enters data to credential interface.

2. Application is processed.

1a. 2a. Temporary Credential is sent back to carrier

3. CVIEW Snapshot is updated.

4. SAFER Snapshot is updated.

5. Data is sent to IFTA Clearinghouse monthly.

6. Data is updated to MCMIS and other jurisdictions.


IFTA Electronic Filing WBS

4-24

WBS Task Name Working Days Start Finish Resource Names 4.4.3 IFTA Web Based Application 75 days 1/8/01 4/23/01 Patricia Platt - KDOR


Truck Routing Information System (TRIS) Summary Information

TRIS will be a GIS based routing and bridge analysis system for oversize/overweight permits. The initial phases of deployment will provide the necessary information electronically to the permit clerk for routing any permit load. This enhancement will replace the many paper maps that are currently used to verify routes.

TRIS will be deployed in phases to eventually have the permit route completely selected by the computer software. The data supporting the routing function will include current construction and detour information, which will be available to motor carriers via the Internet. With over 40,000 single trip and over 1300 annual oversize/overweight permits issued in Kansas annually, TRIS will help protect the infrastructure while enhancing safety for permit loads.

4-25


Goal(s)

•Move toward a paperless environment.•Use electronic data transfer to improve speed and accuracy

Project Description

Improve data flow and communications among the varied stakeholders requesting and issuing oversize / overweight permits in Kansas.

Project Objective

Provide GIS enabled routing information for all permit issuing locations.







2.1.1 Manage Commercial Fleet Electronic Credentials and Tax Filing2.1.2 Provide Commercial Fleet Static Route2.5.3 Update Permits and Duties Store 2.5.2 Obtain Electronic Credential and Tax Filing Payment

TRIS Project

4-26


TRIS Process Flow

4-27

Permit Requestor Processing LocationsKDOR, KHP, KDOT, Internet, Batch

TRIS (Truck Routing

Information System)

MCCP (Motor Carrier Central Permit)

Existing Legacy System

A GIS application will assist both permit clerks and motor carriers in routing of oversized / overweight loads.


TRIS Thread Diagram (1)

4-28

Kansas State Roadside Systems

Kansas State Commercial Vehicle Administration Systems

Carrier Systems



CDLIS

IRPClearinghouse

IFTAClearinghouse

NMVTIS

MCMIS

SAFER

IFTA Registration

LSI

LM

RSPA HazMat


Sensor/Driver Comm

ScreeningLM

Roadside Operations

LSI

LM

ASPENLM

Citation &Accident

LSI

LM

Service Providers

InternetTools


ASAPMCDC



Transponder


IFTA Tax Processing

LSI

LM


LSI

LM

DriverLicensing

LSI

LM


TitlingLSI

LM

SSRSLSI

LM

IRPLSI

LM

TRISLSI

LM

OS/OWLSI

LM

SAFETYNETLSI

LM

CAPRILSI

LM

Treasury orRevenue

LSI

LM


(e.g., CAT)

Perm

it Issuin

g Locations K

DO

T,

KD

OR

and K

HP

1

12

4

5

3


TRIS Thread Diagram (2)

4-29

1. Carrier sends OSOW routing request to permit clerk or credential interface.

2. Routing request is sent to TRIS application for verification / changes.

3. Permit with routing is returned to carrier.

4. Permit information is provided via snapshot to CVIEW.

5. If needed snapshot is provided to SAFER.


TRIS WBS

4-30

Task Name Working Days Start Finish Resource Names4.6.1 Truck Routing Information System (TRIS) 740 days 6/1/99 4/25/02

4.6.1.1 Needs Analysis - Completed 130 days 6/1/99 11/29/994.6.1.1.1 Consultant Contracting 5 days 6/1/99 6/7/99 Ken Gudenkauf4.6.1.1.2 Develop Work Orders 10 days 6/8/99 6/21/99 Ken Gudenkauf4.6.1.1.3 Interviews 40 days 6/22/99 8/16/99 Ken Gudenkauf4.6.1.1.4 Developed Report 75 days 8/17/99 11/29/99 Ken Gudenkauf

4.6.1.2 System Requirements 90 days 11/30/99 4/3/00 Ken Gudenkauf4.6.1.3 Modular Deployment 520 days 4/4/00 4/25/02 Ken Gudenkauf


Electronic Clearance Project Summary Information

The use of transponders to identify and electronically check a carrier’s credentialswill provide safety and savings for both the state and carrier.

Safety

Reduced congestion at weigh stations will mean shorter lines of trucks backed up. Law enforcement will be able to concentrate its efforts on high-risk and

uninspected carriers and operators. Fewer trucks pulling in and out of weigh stations reduces accident risk for motor

carrier’s and passenger vehicles.

Savings

Electronic screening will eliminate the need of truckers to stop for unnecessaryweight and safety inspection.

Electronic screening will reduce the number of stops and starts commercialvehicles must make, thus reducing fuel consumption and time idling in lines atweigh stations.

As vehicles keep moving, the flow of goods from manufacturer to distributor toconsumer is streamlined and on time deliveries will improve.

The new technologies are cheaper to install and use than constructing new weighstations. They also improve the efficiency of existing facilities.

Existing highway infrastructure and facilities can be used more effectively. In an era of shrinking budgets, electronic screening technologies allow

government agencies to shift personnel and resources from processing paperworkto other tasks.

4-31


Goal(s)

•Decrease congestion at inspection stations•Reduce unnecessary time expended for CVO enforcement

Project DescriptionProvide means for MCI Stations to electronically verify commercial vehicles at mainline speeds.

Project ObjectiveImprove safety at weight stations by reducing number of trucks exiting and entering highway.


Work Breakdown Task 5.4





2.3.2 Provide Commercial Vehicle Clearance Screening2.3.2.1 Administer Commercial Vehicle Roadside Credentials Database2.3.2.2 Process Screening Transactions

Electronic Clearance Project

4-32


Electronic Clearance Project Process Flow

4-33

Commercial Vehicle (Transponder Equipped)

Electronic Clearance Enrollment

(Authorization/Cancellations)

MCI Stations(Verification and Clearance)

Kansas Legacy Systems (Data Input)

Transponder equipped vehicles can be electronically cleared to bypass a weigh station, reducing congestion and improving safety.


Electronic Clearance Project Thread Diagram (1)

4-34

Kansas Roadside Systems

Kansas Commercial Vehicle Administration Systems

Carrier Systems



CDLIS

IRPClearinghouse

IFTAClearinghouse

NMVTIS

MCMIS

SAFER

IFTA Registration

LSI

LM

RSPA HazMat


Sensor/Driver Comm

LM

Roadside Operations

LSI

LM

ASPENLM

Citation &Accident

LSI

LM

Service Providers

InternetTools


ASAPMCDC



Transponder


IFTA Tax Processing

LSI

LM


LSI

LM

DriverLicensing

LSI

LM



TitlingLSI

LM

SSRSLSI

LM

IRPLSI

LM

HazMatLSI

LM

OS/OWLSI

LM

SAFETYNETLSI

LM

CAPRILSI

LM

Treasury orRevenue

LSI

LM


(e.g., CAT)

A

B

C

1 2 3

3

4

Screening


Electronic Clearance Project Thread Diagram (2)

4-35

1. Transponder equipped unit is read by roadside sensor.

2. Transponder data is transferred to the screening application.

3. Data is sent to weigh station personnel for review.

4. Red light / Green light signal is returned to Transponder.

A. SAFER snapshot data is sent to CVIEW

B. CVIEW merges SAFER and intrastate snapshot data and passes to roadside computer.

C. Data is update in screening selection computer.


Electronic Clearance Project WBS

4-36

WBS Task Name Working Days Start Finish Resource Names 5.4 Decide static locations 120 days 6/3/02 11/20/02 Ken Gudenkauf5.5 Determine transponder administration and business model 120 days 6/3/02 11/20/02 Ken Gudenkauf5.6 Deployment and training 120 days 6/3/02 11/20/02 Ken Gudenkauf


Section 5

Key Features



Key Features of Kansas CVISN Network Design

• Implement CVIEW functions to assist Motor Carrier Inspectors with roadside operations.

• Provide Legacy System interfaces to support interagency needs.

• Provide connectivity to CVISN Core Systems.

• Implement integrated web/internet based applications with state motor carrier systems.

• Integrate technology solutions where applicable to improve Commercial Vehicle Operations.

5-1



KDOR System

KCC System

KHP System

Unknown System Owner

DISC Mainframe

5-2

ExistingUnknown LinkProposed

Motor Vehicle Administration

State Police (Commercial Vehicle Enforcement)

CVISN CoreInfrastructure Systems

Motor Fuel Tax DivisionASPEN

Screening

IRP

Carrier Systems

SAFER/Data Mailbox

MCMIS

IRPClearinghouse

IFTAClearinghouse

CAT

Treasury:Mainframe DB

IFTA Registration& IFTA TaxProcessing

Sensor/Driver Comm

Accident Reporting

SAFETYNET2000

Licensing& Titling

Intrastate Registration

AAMVAnetFrame Relay

(TCP/IP)

AAMVAnetSNA

Gateway(tokenring)

dial-up

sensors

CDLIS

Roadside Operations

Licensing & Insurance

RSPAHazMat

KTA

Internet

Firewalls

DISC FTP Server

CVIEW

State Communication Systems

DSRC

MCCPOS/OWPermits

SSRS

(Registration)PVD Advalorem Tax

INK

CAPRI


Section 6

Milestones

Funding


Reporting Features on the Work Breakdown Structure

This program will be tracked using Microsoft Project software therefore different reports will be generated throughout the deployment of CVISN. Reporting options include by:

– assignments (who does what, when, to do lists)

– resource (person responsible)

– budget (cash flow, over budget task, over budget resources)

– project summaries (by task, milestones, and working days)

– current activities

– workload (task and resources usage)

– customized reports as needed

As funding and specific dollars are identified and as the procurement process begins Microsoft Project will be used to track activities. The Program Manager will be responsible for maintaining the WBS. This tool allows the WBS to provide key charts, graphs and diagrams related to CVISN program process.

Quarterly update meetings with the Kansas CVISN team will be held to update and monitor program activities.

6-1


Administrative Milestones:CVISN Business draft plan to FHWA November 1997CVISN Business plan completed April 1998CVISN Program Document draft completed May 2000

Training:Introduction to ITS/CVO June 1998ITS/CVO Technical Project Management for Non-Technical

Managers February 1999Understanding ITS/CVO Technology Applications October 1999FHWA - CVO Technology Truck April and September 1998National Architecture Training November 1999

CVISN Workshops Scope workshop November 1999 Planning workshop March 2000 Design workshop June 2000

Technology Milestones:Electronic filing of Permit Applications April 1995, moved to

internet access November 1999Direct dial up access for permit application June 1995IRP Clearinghouse Production Phase June 1997

Targeted Project Milestones:Defined by WBS on Microsoft Project, see page 3-5

Phases and Critical Milestones

6-2


Funding

The Kansas CVISN program will initially rely on established funding sources and seek both federal and state funds for each project. Most new hardware purchases and upgrading present hardware will be funded through the normal agency budgeting process. Also, some CVISN activities will be funded with KDOT’s ITS Set-Aside Program.

Up to this point Congress has earmarked federal funds appropriated for the CVISN program, instead of funding being distributed through the Federal Highway Administration to the states. Kansas recognizes that the competition for these federal funds will continue as more states complete the Design Workshop.

The Information Network of Kansas (INK) will be contacted for the development and programming for the credentials interface for the Permit System, IRP, and IFTA. This deployment method has INK responsible to initially fund the deployment effort and then INK will charge an administrative fee to recover their initial investment.

KHP troopers will be using laptop computers to access the CVISN systems for CVIEW and SAFER to obtain electronic snapshot information for motor carriers at the roadside. Kansas plans to investigate opportunities to use the additional federal funds appropriated to the Motor Carrier Safety Program (MCSAP) for their possible use for portions of related CVISN projects.

Kansas is unable to determine a total cost of the CVISN Level One deployment. As the CVISN program plan continues to evolve, the project costs will be adjusted to reflect current estimates.

6-3


Section 7

Products

Deliverables


Software Products

Microsoft Project Software Output/ Reporting Features CVIEW application Permit Internet Application

Deliverable Projects and Documents

CVO Business PlanCVISN Program PlanCVIEWPermit Applications via the InternetIRP Electronic Filing ProjectIFTA Electronic Filing ProjectTRIS ProjectElectronic Screening Project

Products

7-1


Appendix 1 - Coach Documents

NotesCoach 1Coach 2Coach 3

Appendix 2 - Issues and Decisions

Appendix 3 - Kansas Contacts

Appendix 4 - Acronyms

Appendix


COACH Document Notes

Commitment Level - Filled in by your state to Indicate the degree of commitment to each line item.(F) Full commitment. At least 80% of the activities associated with this checklist item willcomply.(P) Partial commitment. 50% - 80% of the activities associated with this checklist item willcomply.(N) No commitment. Less than 50% of the activities associated with this checklist item willcomply.Being committed implies that there will be a process in place to perform the intended actions.

Taking on the CVISN Program sets in motion a mixture of projects that deploy utility andperformance in the three major functional areas.

"Program" Defined -- A group of related projects managed in a coordinated way to obtainbenefits not available from managing them individually. Programs usually include anelement of ongoing activity. For example, publishing a newspaper is a program; eachindividual issue is a project. CVISN is a program.

"Project" Defined-- A temporary endeavor undertaken to create a unique product orservice. Electronic screening at one weigh station is a project.

A1-1


Coach 1 - Program/ Project Management Checklist

A1-2

CommitLevel

(F/P/N) Intended Actions Preparer CommentsF 1. Establish program executive sponsorship. For example an agency head or chief information

officer; or a group such as an executive-level steering committee.P 2. Empower a Program Manager, dedicated to the program at least 30% of the time on average. More time is

needed in the startup phase, when a team is new, and if there are many simultaneous projects under the CVISNumbrella. (One state with 20 projects has a full-time Program Manager.)

May need to hire a consultant for thisposition as the CVISN projects becomemore numerous or closer toimplementation.

P 3. Engage a System Architect, dedicated to the program approximately 80% of the time on average. Comment same as # 2P 4. Engage a facilitator/scheduler/administrator, dedicated to the program approximately 50% of the time on

average.Comment same as # 2

F 5. When multiple state agencies are involved, establish an inter-agency coordinating council.F 6. Obtain an approved memorandum of agreement among all involved state agencies.F 7. Establish a state carrier advisory council. KMCA fulfills this role.F 8. Recruit interstate, intrastate, and owner-operator carriers to participate in the program before production

deployment (both motor carriers and motor coach companies).Recruit carriers for specific projects asappropriate.

F 9. Where appropriate initiate separate deployment projects under the scope of the CVISN program. Forexample, deployments in disparate domains such as credentials administration vs electronic screening are likelyto be developed by different teams operating as distinct projects.

P 10. Assign a Project Leader for each separate deployment project, dedicated to each project at least 30% of thetime on average. More time is needed in the startup phase.,

Comment same as # 2

P 11. Provide adequate training opportunities to project team members, such as attendance at FHWA's CVISNtraining courses and CVISN workshops.

F 12. Ensure all team members acquire a broad and common understanding of CVISN activities, architecture, anddesign guidance -- for example, by reading the CVISN Guides, and noting lessons-learned by other states.

F 13. Foster a sense of professional fellowship and teamwork. Likely to require teambuilding interventions suchas a partnering workshop; and periodic face-to-face meetings of geographically dispersed teams.

P 14. Adopt the strategy of incrementally developing and deploying products in 3-6 month phases, where eachphase adds additional CVISN capabilities. This is called the “spiral” development model as opposed to the“linear” model. Refer to the CVISN Guide to Phase Planning & Tracking.

F 15. Establish a configuration management process for controlling changes to the system baseline; this typicallyincludes a Configuration Control Board. Utilize state's existing configuration control process whereverpossible.

Handled by KDOR

F 16. Set up a program library; obtain needed references identified in the CVISN Guide to Program & ProjectPlanning.

Handled by KDOR

F 17. Maintain a list of action items, decisions, and issues. (By definition action items require formal closure.)F 18. Delineate needs for external communications with stakeholders (including the state legislature), and with

related projects.F 19. Conduct monthly team meetings and status assessments. Smaller work groupF 20. Track progress versus schedule monthly; strategize accordingly. Smaller work groupF 21. Conduct quarterly stakeholder progress reviews before a wider audience. Regular CVISN groupF 22. Monitor actual costs and resource expenditures relative to estimates.


Coach 2 - Aggregate Program/ Project Planning Checklist

A1-3

CommitLevel

(F/P/N) Intended Actions Preparer CommentsF 1. Review state's ITS/CVO strategic plan and business plan.F 2. Define objectives for CVISN Program.F 3. Derive requirements for deployment projects.F 4. Establish project development standards, such as design margin as a function of development lifecycle.F 5. Define project-specific processes, such as required design reviews, or how to close an action item.F 6. Establish a system design baseline. (See the CVISN Guide to Top-Level Design.)F 7. Create a program Work Breakdown Structure.F 8. Delineate program deliverables, including support documentation and training.F 9. Establish a program organization structure, with clear roles and responsibilities.P 10. Assign each element of the work breakdown structure to an element of the program organization structure.P 11. Develop project-specific "partnering charters" covering four areas: mission statement; communication objectives (e.g.

decision-making at lowest possible level); performance objectives (e.g. complete the project without litigation); issue resolutionsystem (e.g. management levels and timeframes).

F 12. Develop a flexible procurement strategy. Allocate sufficient calendar time for the required steps.F 13. Establish a top-level schedule divided into phases; ensure milestones are measurable.P 14. Outline high-level objectives for each phase; express in a 1-2 page phases chart that explains capabilities from a user's point of

view.F 15. Set the stage for the transition to production use and support; such as database backup and restoration, and a user "help" desk.

F 16. Identify project external dependencies, with their need-by date.P 17. Estimate cost and resource requirements first using summary top-down methods, such as historical analogy and manager's

judgement. This will initiate the process and set targets.F 18. Estimate cost and resource requirements using bottoms-up detailed methods, such as resource-type quantities for each element

of the WBS. This will get 'buy in" from the staff, and validate the top-down estimates.

F 19. Determine potential funding sources and obtain funding commitmentsF 20. Identify both programmatic and technical issues and develop a resolution plan.P 21. Obtain approval, publish, and distribute program plan document. Include completed COACH Part 2 checklists as an

appendix.P 22. Maintain on each project a Project Leader's notebook with up-to-date copies of essential key charts and diagrams.

P 23. Maintain a Program Manager's notebook with up-to-date copies of essential key charts and diagrams.F 24. Once a year or more often, re-figure the estimate-to-completion.


Coach 3 - Aggregate Phase Planning & Incremental Development Checklist

A1-4

CommitLevel

(F/P/N) Intended Actions PreparerComments

F 1. Sustain a system perspective -- a vision of the overall CVISN architecture and deployment strategy.P 2. Plan, develop, and release incrementally, such that at the end of each phase useful end-to-end functionality is delivered in a

way that subsequent phases can build upon.F 3. Choose and format the elements of the phase plan such that they are naturally useful for presenting status. For example,

the list of deliverables could also include columns for dates, current standing, reasons for change.P 4. Employ the rolling wave planning technique, with more detail for the near-term tasks and progressively less detail

for the far-term tasks.F 5. Involve the project staff in the phase planning process, for example in a team-oriented planning session.F 6. Review items on the issues list; resolve to the extent possible.F 7. Close open action items, to the extent possible.F 8. Review items on the decisions list -- as a reminder and to verify they are still relevant and correct.F 9. Set phase objectives.P 10. Flesh out the applicable lowest-level details of the Work Breakdown Structure.P 11. Derive phase requirements; refer to COACH Part 1 checklists and the Program Plan as starting points. Look for

alternative design and development approaches.F 12. Itemize phase deliverables.F 13. Indicate which elements of the system design baseline are to be deployed; update presentation diagrams accordingly.

P 14. Perform studies to determine whether to make, buy, or modify subsystem components. Need evaluatecomponents and maynot require a study.

F 15. Develop a detailed schedule for the work to be accomplished during the current phase. Most effectively done byidentifying and linking activities per the critical path method, utilizing a desktop scheduling tool. The output can be printedas both a

F 16. Identify named individuals who will perform the activities in the detailed schedule.F 17. Update project external dependencies, with their need-by date.P 18. Update the master program phases chart.P 19. Complete the detailed design for all components and interfaces to be developed or modified in the phase. Start with the

top-level design and phase objectives. Use COACH Part 3 checklists as guidance, plus the Scope and Design Workshops.

P 20. Define subsystem and component control and data interfaces. Utilize COACH Part 4 for functional allocation.F 21. Conduct technical reviews in order to catch problems as early as possible in the development life cycle.F 22. Maintain a strict version numbering system for all products.F 23. Maintain stakeholder commitment via visibility into progress by physical demonstrations of useful capability, and by

regular management status reporting.P 24. Define system acceptance criteria; use COACH Part 5 checklists as guidance.P 25. Conduct operational acceptance tests at the end of each phase; specify re-work if necessary.P 26. Conduct a lessons learned session at the end of each phase (as part of planning the next phase).


Issues and Decisions

A2-1

• Design and implementation of CVIEW.

• How do we streamline accident reporting?

• What communication networks will be required?

• One interface for all credentials is desirable.

• Training of Personnel on use of Systems

• Personnel and funding resources•

• Mobile versus Static Enforcement

• Site Determination - Mobile and Static

• To WIM or not to WIM

• Credentialing Interface partnership with INK.

• Well structured existing systems to support enhancements.

• Key agency participation in design.

• Motor Carrier/KTA Buy-In ---- Passive Transponders Currently in Use• 45,500 Commercial Transponders • 6,000 Commercial Accounts


Kansas Contacts

Name Agency Email address

Ken Gudenkauf KDOT [email protected] Luttjohann KDOR [email protected]

Bruce Baldwin FHWA [email protected] Beaver FMCSA [email protected] Blubaugh INK [email protected] Boring KHP [email protected] Davenport KMCA [email protected] Floberg KDOT [email protected] Friesen KHP [email protected] Gerstner KDOR [email protected] Martin KDOR [email protected] Miller KCC [email protected] Platt KDOR [email protected] Volz KDOT [email protected] Whitaker KMCA [email protected] Williams KMCA [email protected] Wiltse KTA [email protected]

A3-1


Acronyms

A4-1

ASAP Automated Safety AssuranceProgram

ITS Intelligent Transportation Systems

ASPEN (not an acronym) KCC Kansas Corporation CommissionAVC Automated Vehicle Classification KDOR Kansas Department of RevenueAVI Automated Vehicle Identification KDOT Kansas Department of

TransportationCA Credential Administration KHP Kansas Highway PatrolCAPRI Carrier Automated Performance

Review InformationKITS Kansas ITS

CDLIS Commercial Drivers License KMCA Kansas Motor Carriers AssociationCOACH CVISN Operational and

Architectural CompatibilityHandbook

KS Kansas

CR Compliance Review KTA Kansas Turnpike AuthorityCVIEW Commercial Vehicle Information

Exchange WindowLM Legacy Modification

CVISN Commercial Vehicle InformationSystems and Networks

LSI Legacy System Interface

CVO Commercial Vehicle Operations MCCP Motor Carrier Central PermitDISC Division of Information Systems

and CommunicationsDSRC Dedicated Short Range

CommunicationMCI Motor Carrier Inspection

EDI Electronic Data Interchange MCMIS Motor Carrier ManagementInformation System

FHWA Federal Highway Administration NMVTIS National Motor Vehicle TitleInformation System

FMCSA Federal Motor Carrier SafetyAdministration

OS/OW Oversize/ Overweight

FTP File Transfer Protocol PRISM Performance & RegistrationInformation System Management

GIS Geographic Information System pspecs process specificationsHAZMAT Hazardous Material SAFER Safety and Fitness Electronic

RecordsIFTA International Fuel Tax Agreement SSE State Specific EnhancementINK Information Network of Kansas SSRS Single State Registration SystemIRP International Registration Plan STIP State Transportation Improvement

ProgramIRP-CH International Registration Plan

ClearinghouseTEA-21 Transportation Equity Act for the

21st CenturyISS Inspection Selection System TRIS Truck Routing Information System

CVISN for Kansas Program Plan May 2000 Kansas CVISN Program Plan June 2000.

Documents

kansas program plan

cvisn architecture

information network

cvisn por

cvisn champions

cvisn initiatives

kansas highway patrol

cvisn design workshop