Scope Page 6 - 1

1
S1 Welcome and Introduction S2 Deployment State
CVISN System Design S3 System Design Guidelines/
Pre-Work Review S4 Panel Discussion S5 Safety
Information Exchange S6 Credentials
Administration S7 Conformance Assurance
Process/Questions S8 Electronic
Screening S9 Scope Workshop Recap S10 Work
Session Consultation S11 State
Presentations S12 Feedback and Next Steps
Session 6 Credentials Administration
2
Session Plan

• Overview Credentials Administration (20 min)
• Conforming with the CVISN Architecture (10 min)
• State, Carrier, and CVISN Core Infrastructure
  Credentials Administration Systems (15 min)
• Example scenario (15 min)
• IRP Registration Supplement, Add Vehicle
• Snapshot updates
• State-to-state fee reconciliation via IRP
  Clearinghouse
• Breakout Plan (10 min)
• Breakout State CVISN system design (120 min)
• LUNCH
• State presentations questions (30 min)
• Total Time 220 min (3 hrs 40 min) 55 min
  lunch

3
Session Objectives

• Understand CVISN operational concepts and
  architectural guidelines related to Credentials
  Administration
• Electronic credentialing via Web Site,
  stand-alone Carrier Automated Transaction (CAT)
  system, fleet management system CAT module
• Use of Web, EDI, XML
• Legacy Modifications (LMs) or Legacy System
  Interfaces (LSIs)
• Credentialing Interface (CI)
• Clearinghouses
• Walk through a credentials administration example
• Make preliminary design decisions about
  credentials administration in your state

4
Credentials Administration

• The Credentials Administration ITS/CVO capability
  area includes
• All aspects of applying for, reviewing, and
  granting CVO credentials paying the associated
  fees
• Credentials include
• International Registration Plan (IRP)
• International Fuel Tax Agreement (IFTA)
• Intrastate Registration
• Carrier Registration
• OS/OW Permits
• HazMat Permits
• Titling
• Electronic Screening Enrollment
• Filing returns on fuel taxes paying the
  associated taxes
• Managing information about credentials and tax
  payment status
• Providing information to roadside enforcement and
  administrative users
• Supporting base state agreements and associated
  fee payment reconciliation

Overview
5
Major components of Credentials Administration

• Electronic credentialing
• Interstate credentials data and fee exchange
• Interagency (within your state) credentials data
  exchange

Overview
6
Electronic Credentialing
Minutes Later...
Review Edit / Validate Upload Process
Payment Credentials Issued
Electronic Application Payment Transmittal
Electronic Credentials Receipt
Increased Handling Capacity / Focus on
Exceptions Increased Accuracy /
Improved Cash Management
Overview
7
FMCSA Policy for Electronic Credentialing

• FMCSA requires that states implement either a
  person-to-computer or a computer-to-computer
  interface.
• FMCSA recommends that states survey their
  stakeholders to determine whether both interfaces
  would be appropriate.
• FMCSA recommends that, in the near term (over the
  next 2 years), carriers and states use X12 EDI
  for computer-to-computer interfaces unless the
  state has evidence that customers support another
  approach.
• FMCSA encourages the exploration of XML as an
  alternative to EDI.

Overview
8
Goals for Electronic Credentialing

• Goals for Smaller Carriers
• Minimal investment and maintenance
• Simple and convenient
• Available to everyone
• Goals for Larger Carriers
• Computer-to-computer interface between state and
  carrier (in addition to person-to-computer
  interface via a Web site)
• Use an open interface standard supported by a
  Standards Development Organization (SDO) or
  technology consortium (versus a proprietary or
  closed interface).
• Allow carriers to have the credentialing function
  integrated into their fleet management software.

Overview
9
Comparison of E-Credentialing Approaches

• Web Site
• Stand-alone Carrier Automated Transaction (CAT)
  System
• Fleet Management System CAT Module

Overview
10
A state Web site approach provides a
person-to-computer interface.
Carrier Or Service Bureau
State
Credentialing Systems with Web Site
World Wide Web
HTML or XML Web standards no credentialing standa
rds 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.
Overview
11
A stand-alone CAT provides a computer-to-computer
interface.
Carrier Or Service Bureau
State
Credentialing Systems
Stand-alone CAT
Internet, Dial-up, or VAN
EDI credentialing standards exist.
Stand-alone CAT
Optional use for state branch offices
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.
Overview
12
A CAT module could be integrated into existing
fleet management systems to provide a
computer-to-computer interface
Carrier
State
Fleet Management System (including CAT Module)
Credentialing Systems
Internet, Dial-up, or VAN
EDI credentialing standards exist.
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.
Overview
13
Strategy for Electronic Credentialing

• FMCSA endorses person-to-computer and
  computer-to-computer solutions for
  e-credentialing
• Person-to-computer solutions Web-site
• Computer-to-computer solutions EDI or XML.
  (Note EDI standards and implementation guides
  are available now. XML is a potential
  alternative.)
• Recommend states design for both in workshop
  process
• Recommend evaluating the market for both among
  their state carrier population via a survey or
  other study mechanism

Overview
14
Electronic CredentialingSummary
Generic State Commercial Vehicle Administration
Systems
Web Site
Service Providers
Carrier Systems
Credentialing Interface (CI)
Internet Tools (e.g. Browser)
EDI (or XML)
Credentialing System (e.g., CAT)
Other Carrier Systems
CV Info Exchange Window (CVIEW)
Electronic Credentialing An operational process
that uses software under the applicants control
to send credentials applications (including fuel
tax returns) to the state, and to get electronic
notification of credentials status in return.
When feasible, the credential itself is returned
electronically. Electronic payment is an option
associated with electronic credentialing.
Using EDI now (potentially XML)
CVISN Level 1
Using Web browser
EDI Electronic Data Interchange using open
standards
Breakout
15
Interstate credentials data exchange (1 of 2)

• Credentials information is passed to the state
  CVIEW (or equivalent). State CVIEW forms
  snapshot segments and updates SAFER for
  interstate snapshots.
• CVISN Level 1
• Data exchanged
• IFTA carrier census information, IFTA account
  information, IFTA check flag and date
• IRP carrier and vehicle census information, IRP
  account information, IRP check flag and date

Overview
16
Interstate credentials fee exchange (2 of 2)

• The IRP and IFTA Clearinghouses support the IRP
  and IFTA base state agreements, respectively.
  The state IRP and IFTA products interact with the
  clearinghouses to accomplish the financial
  reconciliation functions.
• CVISN Level 1
• Data exchanged
• IFTA carrier census information, IFTA account
  information, fuel tax information
• IRP carrier and vehicle census information, IRP
  account information, IRP registration fee
  information

Overview
17
Interagency (within your state) credentials data
exchange

• Credentials information is exchanged within the
  state via CVIEW and/or by direct interaction
  among state systems.
• State CVIEW maintains intrastate snapshots.

Overview
18
Conforming with the Architecture Guidelines for
a Carrier-to-State Web Site

• The State Web Site should only use Web techniques
  supported by the major browsers, Microsoft's
  Internet Explorer and Netscape's Navigator.
• The State Web Site should use the CVISN
  recommended primary identifiers.
• The State Web site should provide end-to-end
  electronic credentialing functionality, including
  invoicing and payment.
• The State Web site should be Section 508
  compliant.
• More information is available in Chapter 6,
  Requirements and Design Guidance, of the CVISN
  Guide to Credentials Administration.

Conforming with the CVISN Architecture
19
Conforming with the ArchitectureEDI Standards

• To conform with the architecture, if the State
  implements X12 EDI interfaces
• The State should accept and respond to EDI X12
  standard transactions with carriers for CV
  credentialing and tax filing (286, 813, 151,
  997).
• A Carrier Automated Transaction (CAT) software
  product (or equivalent) should generate and
  respond to EDI X12 standard transactions with the
  State (286, 813, 151, 997).
• The State should provide invoice data for
  credentials using EDI X12 standard transactions
  (286).
• The State should exchange snapshot data with
  SAFER using EDI X12 standard transactions (285).
• The State should provide tax credits, tax
  calculations, and tax rate information to
  carriers using EDI X12 standard transactions
  (826, 149, 150 not required for Level 1).

Conforming with the CVISN Architecture
20
The ANSI X12 EDI transaction sets directly
associated with electronic credentialing

• TS 149 Notice of Adjustment (state tax
  calculation)
• TS 150 Tax Rate Notification
• TS 151 Electronic Filing of Tax Return Data
  Acknowledgement
• TS 285 CV Safety Credentials Information
  Exchange (snapshots)
• TS 286 Commercial Vehicle (CV) Credentials
• TS 813 Electronic Filing of Tax Return Data
• TS 824 Application Advice
• TS 826 Tax Information Exchange
• TS 997 Functional Acknowledgement
• not required for CVISN Level 1 IFTA tax
  exchanges

Conforming with the CVISN Architecture
21
Conforming with the Architecture

• Several design options that conform to the
  architecture are depicted in Chapter 6,
  Requirements and Design Guidance, of the CVISN
  Guide to Credentials Administration the examples
  do not exhaust the possibilities.

Conforming with the CVISN Architecture
22
State CVA Systems States make design decisions
about the extent of modifications to legacy
systems.

• Legacy systems in the state may require
  modification (LM) to support new CVISN
  functionality and interfaces.
• If it is impractical to modify a legacy system to
  handle the EDI interfaces, a legacy system
  interface (LSI) may be added.

Carrier Systems
State Systems
Web Site
HTML, XML
LSI
EDI or Non-EDI
EDI or Non-EDI
Credentialing Interface
Non- EDI
EDI
LM
Non-EDI
Legacy System 1 (e.g. IRP)
EDI
EDI
CVIEW
snapshots
snapshots
Carriers Bank
States Bank
State, Carrier CVISN Core Infrastructure
Credentials Administration Systems
23
State CVA Systems The Credentialing Interface
provides a convenient interface within the state
to accept e-credentialing applications from
carriers, and to relay responses from state
systems to carriers.
Carrier Systems
State Systems
Web Site
HTML, XML
EDI or Non-EDI
Credentialing Interface
State Credentialing Systems
EDI
Carriers Bank
States Bank
State, Carrier CVISN Core Infrastructure
Credentials Administration Systems
24
State CVA Systems The State Web Site provides a
convenient interface, particularly for small
carriers.
Carrier Systems
State Systems
Web Site
HTML, XML
Credentialing Interface
State Credentialing Systems
Carriers Bank
States Bank
State, Carrier CVISN Core Infrastructure
Credentials Administration Systems
25
Carrier CVA Systems The Carrier Automated
Transaction (CAT) module allows carriers to apply
for and obtain credentials electronically.
Carrier Systems
State Systems
The Carrier Automated Transaction performs these
functions
Web Site

• Data entry screens for credential applications
  fuel tax filing
• Validate application
• Specify payment method
• Compute fees (some, not all)
• Print applications
• Initiate payments through banks (future)
• Translate to/from EDI/non-EDI transactions
• Send transactions
• Receive transactions
• Acknowledge transactions
• Print credentials, if authorized
• Archive transactions

Credentialing Interface
EDI or Non-EDI
State Credentialing Systems
Other Carrier Admin/Mgt Systems
EDI
EFT
Carriers Bank
States Bank
State, Carrier CVISN Core Infrastructure
Credentials Administration Systems
26
Core Infrastructure CVA Systems The IRP
Clearinghouse processes information received
electronically from states to compute fees
due/owed each jurisdiction, and facilitates
periodic funds transfers.
State A Bank
State A
IRP
IRP Clearinghouse
IRP CH Bank
State B
IRP
State B Bank
State, Carrier CVISN Core Infrastructure
Credentials Administration Systems
27
Core Infrastructure CVA Systems The IFTA
Clearinghouse provides secure access to tax
information for IFTA, Inc clients.
The IFTA Clearinghouse performs these major
functions
State A
286, 826, 997

• Accept data (demographic transmittal) submitted
  by clients (EDI)
• Provide standard reports
• Provide transmittal data entry screens
• Respond to standard ad hoc queries
• Maintain Tax Matrix Reference Table

IFTA
EDI
IFTA Clearinghouse
State B
IFTA
EDI
286, 826, 997
State, Carrier CVISN Core Infrastructure
Credentials Administration Systems
28
Credentials Administration Design
DecisionsWhats reflected in the sample
operational scenario...

• 1. Do you use commercial systems for
  credentialing? Which ones, and for what
  credentials?
• We use the Regional Processing Center (RPC) for
  IFTA.
• 2. Do any of the earlier CVISN states use the
  same system(s)? Does their design look as if it
  would fit your state? (Please see Appendix D of
  the CVISN Guide to Credentials Administration)
• Our system looks very much like State Xs, and
  were modeling our design after theirs.
• 3. Do you plan to build a Credentialing
  Interface? Take another approach that doesnt
  involve a CI?
• We will build a CI. Well start by reviewing
  what State X does, and see what changes we need.

Example Operational Scenario
29
Credentials Administration Design
DecisionsWhats reflected in the sample
operational scenario...

• 4. Will you provide a Web solution?
• Yes, we intend to integrate e-credentialing
  capabilities into our MVA Web site.
• 5. Will you sponsor the development of a CAT or
  CAT module? Do you know what your carriers want?
• We have established a CVISN steering committee
  that includes a mix of carriers. Through the
  trucking associations, we conducted surveys. We
  are going to implement a Web solution first, as
  we believe it will handle 80 of our customers.
  Our smaller carriers think the Web site will
  satisfy their needs, while even the large
  carriers say they will use it for single
  transactions. Our large carriers would like a
  computer-to-computer interface for adding fleets.
  If we can afford it, we will work with one of our
  large carriers and their fleet management system
  developer to add an electronic credentialing
  capability to the FMS package.

Example Operational Scenario
30
Credentials Administration Design
DecisionsWhats reflected in the sample
operational scenario...

• 6. Will you modify all or some of your legacy
  credentials systems to support EDI? Which ones?
• We are working with our vendors on this. The IRP
  system is definitely being upgraded to handle
  EDI. It does not look as though well switch to
  EDI for IFTA, though. We may need to develop a
  legacy system interface (LSI) for IFTA. We are
  also monitoring developments on XML and would be
  interested in participating with other states in
  a working group on using XML in CVO.

Example Operational Scenario
31
Operational Scenario

• Accept and process electronic IRP credential
  applications for supplements (e.g., adding a
  vehicle to an existing account)
• Interact with the applicant electronically, via a
  Web Browser and Web Site
• Maintain snapshots for interstate operators by
  providing credential data for carriers and
  vehicles based in your state to SAFER
• Connect to the IRP Clearinghouse to support the
  IRP base state agreement

Example Operational Scenario
32
Operational ScenarioIRP Supplement, Add
VehicleWeb Site/Web browser configuration

• 1. Carrier enters an IRP credential application
  via a Web browser to a state-based Web Site.
• 2. The Web Site passes it to the Credentialing
  Interface (CI).
• 3. The CI submits a query to its state database
  to perform preliminary checks as part of
  evaluating the application.
• 4. The state database reports the status, i.e.,
  flags and condition to the CI.
• 5. If a satisfactory status is received, the
  application is sent to the IRP system for
  processing via EDI X12 TS 286.
• 6. The IRP system processes the application and
  sends an invoice notice to the CI via EDI X12 TS
  286.
• 7. The CI sends the invoice notice to the Web
  Site and maintains archival/audit copies of all
  transactions.
• 8. The carrier retrieves the invoice notice from
  the state Web Site using a Web Browser.
• 9. The carrier reviews the invoice data and
  verifies that the application data matches the
  intent. The carrier indicates payment method
  information via the Web Browser to the Web Site.

Example Operational Scenario
33
Operational ScenarioIRP Supplement, Add
Vehicle Web Site/Web browser configuration

• 10. The Web Site passes it to the Credentialing
  Interface (CI).
• 11. If a Temporary Authority (TA) is requested,
  the CI releases it to the Web Site.
• 12. The carrier prints the TA from the Web Site.
• 13. If a TA was granted, the CI sends a vehicle
  snapshot segment update to CVIEW via EDI X12 285.
• 14. CVIEW sends updated snapshot data to SAFER
  via EDI X12 TS 285.
• 15. CVIEW sends updated snapshot data to
  Roadside via EDI X12 TS 285.
• 16. SAFER sends updated snapshot data to
  subscribers via EDI X12 TS 285.
• 17. The CI verifies payment method information
  (financial system interfaces are not shown) and
  passes payment approval to the IRP system via EDI
  X12 TS 286.
• 18. The IRP system validates payment amount and
  updates application status to indicate the
  permanent credential granted and notifies the CI
  via EDI X12 TS 286.
• 19. The CI passes the permanent credential to the
  Web Site.
• 20. The carrier prints the Cab Cards from the Web
  Site.

Example Operational Scenario
34
Operational ScenarioIRP Supplement, Add
Vehicle Web Site/Web browser configuration

• 21. The CI updates CVIEW with permanent
  credential information via EDI X12 TS 285.
• 22. CVIEW sends updated snapshot data to SAFER
  via EDI X12 285.
• 23. CVIEW sends updated snapshot data to Roadside
  via EDI X12 285.
• 24. SAFER makes updated snapshot data available
  to subscribers via EDI X12 TS 285.
• A. Daily, the IRP system sends updates to the IRP
  Clearinghouse on IRP registration information and
  fee payments (recaps).
• B. Monthly, the IRP Clearinghouse makes available
  the fee information (pre-netting transmittals) to
  the participating jurisdictions for approval
  and/or correction. States review the information
  interactively using terminals.
• C. The IRP Office and also other participating
  jurisdictions report back to the IRP
  Clearinghouse the approvals or corrections. The
  approvals/corrections are made via terminals.

Example Operational Scenario
35
Operational ScenarioIRP Supplement, Add
VehicleWeb Site/Web browser configuration

• D. The IRP Clearinghouse performs the actual
  netting and makes available corrected/approved
  vehicle and fee actions (post-netting
  transmittal) and netting results (remittance
  netting reports) to the participating
  jurisdictions. The information is reviewed via
  terminals.
• NOTE Functional acknowledgment for all EDI
  messages (except TS 997) is made by responding
  with a TS 997. Content errors in a received TS
  286 are noted by also replying with a TS 286.
  The results of processing an incoming TS 285 are
  reported via TS 824.

Example Operational Scenario
36
Functional Thread DiagramIRP Supplement, Add
VehicleWeb Site/Web browser configuration
Generic State Commercial Vehicle Administration
Systems
IRP Office
Web Site
CVISN Core Infrastructure Systems
(National/Regional)
Service Providers
Carrier Systems
Credentialing Interface (CI)
E-Screening Enrollment
CDLIS
Internet Tools (e.g. Browser)
Credentialing System (e.g., CAT)
IRP Clearinghouse
IFTA Clearinghouse
Other Carrier Systems
NMVTIS
MCMIS
CV Info Exchange Window (CVIEW)
SAFER
Licensing Insurance
Generic State Roadside Systems
Compliance Review (e.g., CAPRI)
Carrier Commercial Vehicle
Transponder
Other Jurisdictions
Example Operational Scenario
37
Breakout Goals

• Set goals and objectives for credentials
  administration in your state
• Make initial design decisions related to
  credentials administration
• Illustrate the actions associated with IRP
  Supplement, Add Vehicle in your state using the
  operational scenario and functional thread
  diagram approach
• Make initial allocation of new functions to
  existing or new computers and networks

Breakout
38
What inputs are needed?What outputs are created?

• Input/Pre-work needed
• COACH Part 1 checklists in 4.1, 4.3
• System Inventory
• IRP
• IFTA Registration
• IFTA Tax Filing
• Keys IDs
• Electronic Interchanges in Use
• Outputs
• Revised COACH checklists
• Goals objectives
• Answers to some key design decisions
• Completed thread diagram
• Updated top-level physical design
• Updated action plan, decision list, issue list

Breakout
39
Breakout Plan120 minutes

• Using your states CVISN system design template
  and network template, and follow the example just
  presented
• Step 1. 10 min. Assign roles. Review update
  COACH Part 1 checklists 4.1, 4.3.
• Step 2. 20 min. Briefly discuss how you perform
  credentials-related functions today. Set the
  near-term goals and objectives for credentials
  administration in your state. Record the goals
  objectives on a flip chart. If necessary for the
  discussion, pick the credentials you want to work
  on.
• Step 3. 30 min. Referring to the CVISN Guide to
  Credentials Administration as needed, discuss
  design alternatives that support your goals and
  objectives (please see page 45). Reach
  preliminary conclusions for as many questions as
  possible. Record actions as needed to answer the
  questions.

Breakout
40
Breakout Plan120 minutes

• Step 4. 30 min. On a flipchart, tailor the list
  of scenario steps presented in this session for
  IRP Supplement, Add Vehicle in your state.
• Step 5. 10 min. Start with a copy of your
  system design template. Label it IRP
  Supplement, Add Vehicle. Connect the boxes with
  directional lines to illustrate the information
  flow for the scenario. Label the lines with the
  step numbers from the scenario.
• Step 6. 10 min. Start with a copy of your
  network template. Label it to match the scenario
  it will support. Review the network template to
  see what new or enhanced processing power or
  connectivity is needed to support the
  interactions for your IRP scenario. As needed,
  add computers or connections to the diagram. If
  a new process is being added to an existing
  computer, list the software application in that
  computers box. If you can, identify the
  communications protocol you will you use for each
  new connection.

Breakout
41
Breakout Plan120 minutes

• Step 7. 5 min. Make sure youve noted all the
  open actions on your action plan and preliminary
  decisions on your decision table. List the three
  most important credentials administration-related
  issues or questions that your state needs
  assistance with.
• Step 8. 5 min. Get ready to present your
  results to the main group. A sample outline
  includes
• Goals and objectives for Credentials
  Administration (step 2)
• Preliminary design decisions for Credentials
  Administration (step 3)
• IRP Supplement, Add Vehicle operational scenario
  and functional thread diagram (steps 4 and 5)
• Physical design diagram for IRP scenario (step 6)
• Actions, decisions, issues (step 7)

Breakout
42
Breakout Plan120 minutes

• Step 8. (continued)
• Assemble the material for the presentation
• If you do it electronically, copy the file onto a
  floppy disk and take it with you to the main
  meeting room.
• Otherwise, make transparencies.
• If necessary, carry flip chart pages with you to
  the main meeting room for reference.
• If you have time, make a copy for each member of
  your team and for the master book.

Breakout
43
As time permits, or after the workshop, finish
the top-level design steps associated with Level
1 functionality. . .

• If you are implementing the complete set of CVISN
  Level 1 credentialing capabilities, then you
  should define each of these scenarios
• Complete an operational scenario and functional
  thread diagram for accepting and processing IRP
  renewal applications
• a. Web Site/Web browser configuration
  (person-to-computer)
• b. CAT or FMS system configuration(computer-to-com
  puter)
• Complete an operational scenario and functional
  thread diagram for accepting and processing IFTA
  credential applications for supplements
• a. Web Site/Web browser configuration
  (person-to-computer)
• b. CAT or FMS system configuration(computer-to-com
  puter)
• Complete an operational scenario and functional
  thread diagram for accepting and processing IFTA
  renewal applications
• a. Web Site/Web browser configuration
  (person-to-computer)
• b. CAT or FMS system configuration(computer-to-com
  puter)
• Complete an operational scenario and functional
  thread diagram for accepting and processing IFTA
  quarterly tax returns
• a. Web Site/Web browser configuration
  (person-to-computer)
• b. CAT or FMS system configuration(computer-to-com
  puter)

Breakout
44
Team Roles

• Facilitator _________________________
• Presenter _________________________
• Scribe _________________________
• Time Keeper _________________________
• CSA _________________________
• Change the roles for each breakout session
• (except facilitator and CSA)

Breakout
45
State Credentials Administration Goals
Objectives
Breakout
46
Credentials Administration Design Decisions

• 1. Do you use commercial systems for
  credentialing? Which ones, and for what
  credentials?
• 2. Do any of the earlier CVISN states use the
  same system? Does their design look as if it
  would fit your state? (Please see Appendix D of
  the CVISN Guide to Credentials Administration)
• 3. Do you plan to build a Credentialing
  Interface? Take another approach that doesnt
  involve a CI?
• 4. Will you provide a Web solution?
• 5. Will you sponsor the development of a CAT or
  CAT module? Do you know what your carriers want?
• 6. Will you modify all or some of your legacy
  credentials systems to support EDI? Which ones?

Breakout
47
Credentials Administration Design Decisions
Breakout
48
Generic State System Design Template
Use Your States Template
Generic State Commercial Vehicle Administration
Systems
Web Site
CVISN Core Infrastructure Systems
(National/Regional)
Service Providers
Carrier Systems
Credentialing Interface (CI)
E-Screening Enrollment
CDLIS
Internet Tools (e.g. Browser)
Credentialing System (e.g., CAT)
IRP Clearinghouse
IFTA Clearinghouse
Other Carrier Systems
NMVTIS
MCMIS
CV Info Exchange Window (CVIEW)
SAFER
Licensing Insurance
Generic State Roadside Systems
Compliance Review (e.g., CAPRI)
Carrier Commercial Vehicle
Transponder
Breakout
49
Generic Network Template
Use Your States Template
Motor Vehicle Administration
State Police (MCSAP Agency)
Credentialing Interface, All MVA
LSIs, E-Screening Enrollment
Inspections (ASPEN)
Carrier Registration Permitting
CAPRI
Web Site
IRP
Licensing Titling
Intrastate Registration
CVIEW
dial-up
SAFETYNET
Dedicated dial-up
Gateway
Firewall
Dial-up
CVISN Core Infrastructure Systems
SNA
Ethernet Backbone
TCP/IP
AAMVAnet Frame Relay (TCP/IP)
Firewall
SAFER
Carrier Systems
Firewalls
Internet Tools
Licensing Insurance
Internet
Credentialing System
dial-up
CDLIS
Repeater
Gateway (token ring)
AAMVAnet SNA
AAMVAnet CSN (TCP/IP)
MCMIS
sensors
Firewall
IRP Clearinghouse
RF Link
Ethernet Backbone
IFTA Clearinghouse
State Highway Administration
Motor Fuel Tax Agency
Treasury Mainframe DB
IFTA Registration IFTA Tax Processing
Roadside Operations
Sensor/ Driver Comm
Screening
Existing Proposed
Ethernet Backbone
SNA
Breakout
50
Credentials Administration Issues/Questions
Breakout
51
Background Material
52
What is EDI?

• Electronic Data Interchange (EDI) is the
  electronic exchange of business information in a
  format that permits computer generation and
  processing of the message
• Reduces or eliminates paper transactions
• Allows automated processing storing of data
• EDI standards and user implementation guides
  define the structure and meaning of messages
  passed between trading partners.
• American National Standards Institute (ANSI)
  provides an infrastructure for defining
  maintaining open EDI standards.
• Each ANSI standard defines structure for a
  message serving a defined purpose. (There are
  currently about 250 such standards.)
• A common implementation is to couple existing
  systems to an EDI translator software package
  commercial network.

Conforming with the CVISN Architecture
53
EDI Transmissions Consist of Nested Control and
Transaction Segment Information
Communications Transport Protocol
ISA
GS
Functional Group Header
ST
Detail Segments
SE
FUNCTIONAL GROUP
ST
Detail Segments
SE
Transaction Set Trailer
COMMUNICATIONS SESSION
GE
Functional Group Trailer
GS
Functional Group Header
ST
Detail Segments
FUNCTIONAL GROUP
Transaction Set Trailer
SE
GE
Functional Group Trailer
Source EDI X12 Standards, Version 3 Release 6,
published December 1995.
Interchange Control Trailer
IEA
Communications Transport Protocol
Conforming with the CVISN Architecture
54
Actual EDI Transmission(Control and Transaction
Segments Highlighted)
ISA000000000000000000000000ZZLMIMSCVISNZZM
DCVISN9905051149U004010000000400Pgt GSKM
LMIMSCVISNMDCVISN19990505114937X004010 ST2
861 BGN110000000000003719990505114901PTAPP
2167NM1412LockheedMartinIMSN340N.CentralAve
.N3Suite2250N4PhoenixAZ85004USPERICGeral
dHonmaTE6024136013FX602254451SPI9006I
VHL1AP1LMFHLQT14201N9IRP0000012865N9
CF001N9ACF047N9I5980000260DTMABACY1
998DTM00319990504NM1UX2SJMDHL2135
0LMFHLQT0321NM11B2MDCVISNTESTCOMPANYN3
123MAINSTN4MAINVILLEMD13245USANM1312MDCVI
SNTESTCOMPANYN3123MAINSTN4MAINVILLEMD13245U
SAHL31R1LMFHLQT14502N96P00020YNQY
T14W2NM1JU2SJDCMEAWTS44Y
NQYT14530NM1JU2SJGAMEAWTS
44YNQYT14530NM1JU2SJMDMEA
WTS44YNQYT14530NM1JU2SJ
VAMEAWTS44YNQYT14530HL43E0
LMFHLQT20BSN9SUBTESTBUSDTM31819990426M
EAWTEW15000LBMEAWTG45000LBQTYHL45YNQ
YT083YNQNT11150YNQNT17
600YNQYT14522VEHBUSVIN1997NAINTL
BUS6600000NDVIPUR66000D819990402M
DCY1998N12DZZNM1OY1CVISNCAT/CITESTHL51
PY0LMFHLQT11375AMTBAP31.93AMTPD0AMT
BD31.93NM1JU2SJDCQTYM10.06667P1LQ
T11375AMTBAP37.5AMTPD0AMTBD37.5NM1JU2
SJGAQTYM10.06667P1LQT11375AMTBAP5
00AMTPD0AMTBD500NM1JU2SJMDQTYM1
0.8P1LQT11375AMTBAP4.2AMTPD0AMTBD4.2
NM1JU2SJVAQTYM10.06667P1HL61R1L
MFHLQT14502N96P00001YNQYT14W3NM1
JU2SJMDMEAWTS44YNQYT14
530HL76E0LMFHLQT20STN9SUBTESTTRLDTM
31819990426MEAWTEW8000LBMEAWTG18000LBQ
TYR52YNQYT083YNQNT11150YNQ
NT17600YNQYT14522VEHTRAILER1
996NAFRUETRAILER2500000NDVIPUR25000
D819990403MDCY1998NM1OY1CVISNCAT/CITES
TACHL81PY0LMFHLQT11375AMTBAP20.25AMT
PD0AMTBD20.25NM1JU2SJMDQTYM11P1
HL91R1LMFHLQT14502N96P00080YNQY
T14W1NM1JU2SJDCMEAWTS80000LBYN
QYT14530NM1JU2SJGAMEAWTS800
00LBYNQYT14530NM1JU2SJMDMEA
WTS80000LBYNQYT14530NM1JU2SJ
VAMEAWTS80000LBYNQYT14530HL109
E0LMFHLQT20TKN9SUBTESTTR1DTM3181999042
6MEAWTEW15000LBMEAWTG80000LBQTYR53YN
QYT083YNQNT11150YNQYT1
7600YNQYT14522VEHTR451998NAINTL
TR4512500000NDVIPUR125000D819990401
MDCY1998N12DZZNM1OY1CVISNCAT/CITESTACH
L111PY0LMFHLQT11375AMTBAP31.93AMTPD
0AMTBD31.93NM1JU2SJDCQTYM10.06667
P1LQT11375AMTBAP48.34AMTPD0AMTBD48.34
NM1JU2SJGAQTYM10.06667P1LQT11375A
MTBAP752AMTPD0AMTBD752NM1JU2SJMD
QTYM10.8P1LQT11375AMTBAP87.87AMTPD0A
MTBD87.87NM1JU2SJVAQTYM10.06667P1
HL121FL0LMFHLQT09APQTYTO12MOLQT20P
WQTYTO1LQT20BSQTYTO1LQT20TRQTYTO1H
L131PY0LMFHLQT14700AMTYF241.77AMTAD
1530.02AMTFO0AMTPD0AMTBM0AMTBD1530.02
LQT11375AMTFE63.86NM1JU2SJDCQTYMI
0.06667P1LQT11375AMTFE85.84NM1JU2
SJGAQTYMI0.06667P1LQT11375AMTFE1272.25
AMTBAP1272.25NM1UX2SJMDQTYMI0.8P1
LQT11375AMTFE92.07NM1JU2SJVAQTYMI
0.06667P1LQT14733AMTFE16NM1UX2SJ
MD SE2161 GE137 IEA1000000040

EDI messages are text files.
Conforming with the CVISN Architecture
55
Electronic Data Interchange (EDI)
STATE
MOTOR CARRIER
Open ANSI X12 EDI Standards and Implementation
Guides allow motor carriers, states, and other
trading partners to exchange safety and
credentialing information. An EDI interface can
be added to existing systems through some custom
coding and a commercial-off-the-shelf EDI
translator.
Motor Carrier Applications
State Applications
Application Database
Application Database
Custom Data Extract/Insert
Custom Data Extract/Insert
Commercial EDI Translator
Commercial EDI Translator
EDI
EDI
Communication Network (e.g., the Internet)
Conforming with the CVISN Architecture
56
What is XML?

• XML is a metalanguage for creating a customized
  mark-up language to describe the structure and
  content of documents. An outgrowth of document
  publishing and display technologies, XML is
  becoming popular in WWW applications. It is a
  method, not a standard, for data interchange.
• The World Wide Web Consortium (W3C) and OASIS are
  two of the key organizations involved in
  developing XML standards.
• Standards organizations and industry experts are
  working to combine the rich data semantics from
  20 years of EDI history with the emerging XML
  technology for data and document exchange.
• XML is a potential alternative approach for CVO
  information exchange, but there are no guidelines
  at this time for the use of XML in the domain of
  commercial vehicle operations, and no equivalent
  aids to users as the implementation guides for
  EDI.

Conforming with the CVISN Architecture
57
Example of XML
XML messages are text files.
Conforming with the CVISN Architecture
58
Credentials Administration Various approaches
enable different carriers to obtain credentials
and enable states to process the applications
and support base state agreements electronically.

Standardized EDI or Web transactions enable
carriers to file for credentials from their
offices, states to process applications
automatically, states to exchange information
electronically to support base state
agreements states exchange interstate
credentials with other states via SAFER
Standardized transactions support fee payments
among payers, payees, and financial institutions
(banks).
Motor Carrier
1
Credentialing System (e.g., CAT - Carrier
Automated Transaction, or CAT module)
2
Carrier Bank
3
4
5
Web Browser
1
State Bank
5
EDI
1
5
5
5
Legacy Systems Associated with Credential or Fuel
Tax Filing
State
CI / Legacy Workstations
LMs
2
IRP CH Bank
(For manual review or entry of credential / tax
filing info)
Web Site
EDI
or
IFTA and IRP Clearinghouses (Support base state
agreements)
EDI
EDI for IFTA CH
3
or
LSIs
Credentialing Interface (CI)
CVIEW
Other States
4
SAFER
EDI Electronic Data Interchange LM Legacy
Modification LSI Legacy System Interface
EDI
4
Credentials Administration
59
Modifications enhance legacy systems to make
better use of available information and to
improve operations.


OS/OW Permit
Service Provider
Intra-State Veh Registration


CAT (other vendor)


IRP Registration
CAT Carrier Automated Transaction
1
Credentialing Interface (CI)
Legacy Systems
IFTA Registration
149, 150, 151, 286, 997
149, 150, 151, 286, 997
150, 286, 813, 997
150, 286, 813, 997
Legacy Mods (LM)
or
SQL or ODBC
IFTA Qrt Tax
OS/OW
Intra-State Veh Reg
2
Legacy systems in the state may require
modification (LM) to support standardized
information exchange, electronic credentialing,
improved safety assurance programs, etc. New
application plug-ins, legacy system interfaces
(LSIs), will be added only if EDI is impractical
for data exchange between systems within the state
1
IRP Reg
IFTA Reg LSI
or
286, 826, 997
285, 824, 997
State CVIEW
IFTA Clearinghouse
2
IRP Clearinghouse Clearinghouses
State, Carrier CVISN Core Infrastructure
Credentials Administration Systems
60
The Credentialing Interface provides a convenient
interface within the state to accept electronic
credentialing application inputs from carriers,
and to provide responses from state systems to
carriers.
The Credentialing Interface Uses EDI ASC X12
standards for external interfaces, Does
preliminary syntax checks on received
transactions, Routes applications to the
appropriate state credentialing system, Routes
responses to the carrier.
1
Carrier Automated Transaction
Credentialing Interface (CI)
2
1
Service Provider
3
2
CAT
User Input
150, 286, 813
4
A state may choose to extend the CI to perform
other functions (e.g., snapshot updates) that are
allocated to other systems in the generic design.
4
1
149, 150, 151, 286
3
or
4
149, 150, 151, 286
Legacy System
or
Leg Sys Mod
1
286, 813
Note all EDI messages acknowledged
with a 997.
State, Carrier CVISN Core Infrastructure
Credentials Administration Systems
61
As the state Web-enables its credentialing
processes, it can re-use the core Credentialing
Interface and legacy systems.
Carrier
State Systems
Firewall 2
Firewall 1
Credentialing Web Site
DMV Database
Data Base
Browser
IRP
Stand-Alone CAT
IFTA Registration
Core Credentialing Interface
Web Files
IFTA Tax Processing
State CVIEW
CI User Interface Client
Legend solid blue arrows indicate access
through firewall
Credentials Administration Systems
62
Keep the same back end processes, regardless of
the external interfaces for credentialing
State Systems
Web XML- Enabled Credentialing Interface
Stand-Alone CAT
IRP
Terminal Server
C A T
EDI I/F
Terminal Client
IFTA Reg
XML I/F
Credentialing Web Site
Fleet Management System
Web Database
IFTA Tax Filing
Core CI
Browser
Database
CVIEW
Credentials Administration Systems
63
The IRP Clearinghouse processes information
received electronically from states to compute
fees due/owed each jurisdiction, and facilitates
periodic funds transfers.

• List RECAPS available (Pre-Netting Notification)
• Summarize vehicle fee info from RECAPS and list
  balance due/owed each jurisdiction (Post-Netting)

The IRP Clearinghouse performs these major
functions Accepts RECAPS input from
jurisdictions, Computes balance due/owed to/from
each jurisdiction, Facilitates monthly funds
transfer, EFT supporting
2
STATE A Bank
Funds Transfer
1
Help Desk
STATE A IRP System
2
Send detailed data (RECAP) from paid-for IRP
applications
1
IRP Bank
IRP Clearinghouse
3
3
Funds Transfer
STATE B IRP System
STATE B Bank
2
based on information provided by IRP, Inc.
CVISN Core Infrastructure
64
The IFTA Clearinghouse Central repository
provides access to confidential tax information
for IFTA, Inc clients.

• Responds to standard ad hoc queries
• Transmittal data entry screens
• Tax Matrix Reference Table maintenance
• Accepts data (demographic transmittal)
  submitted by clients (EDI)
• Provides standard reports

VISTA Jurisdiction
IFTA Clearinghouse Central Repository
Query/Response, Extract of demographic
information (286) and transmittals (826)
Daily Update via X12 286 and 826,
Query/Response
Single Jurisdiction System
RPC Jurisdiction
Daily Update via X12 286 and 826
based on information provided by RSIS
CVISN Core Infrastructure
65
The IFTA Clearinghouse Web Site will provide
public access to non-confidential tax information.
IFTA, Inc Client User
IFTA Clearinghouse Web Site

• IFTA information
• IFTA manuals
• Tax Rate Matrices
• IFTA news calendar of events
• IFTA related sites e-mail
• Search capability

Public User
based on information provided by RSIS
CVISN Core Infrastructure
66
This Page Intentionally Blank