# Presentation: 304480

## Session 4b 

- S2  State Preliminary Design Review
- S3  State Work/Discussion Sessions
**S4  General Discussion of issues and questions**
- S5  Birds of A Feather design discussions
- S6  State Program Phase Charts Review
- S7  State Work Sessions
- S8	State Presentations
- S9	Feedback & Next Steps

**Session 4b **
**Discussion - **
**EDI, XML, Web**

## Session 4b Discussion - OutlineEDI, XML and the Web: CVISN Interface Design

- Session 4b Discussion - OutlineEDI, XML and the Web: CVISN Interface Design

- CVISN Interface Designs
- Alternatives for Electronic Credentialing
- Strategy for CVISN Interfaces

## Session 4b Discussion - Background MaterialEDI, XML and the Web: CVISN Interface Design

- Comparison of Electronic Credentialing Alternatives
- Simplified Comparison of Person-to-Computer & Computer-to-Computer Interfaces
- Simplified Comparison of Alternatives for Computer-to-Computer Interfaces:  EDI or XML
- More on the Technologies
- What is EDI?
- What is XML?
- When Should You Use XML?
- What Activities Are Ongoing?
- Terminology

## Session 4b: EDI, XML and the Web: CVISN Interface Design

- Session 4b: EDI, XML and the Web: CVISN Interface Design

**The Interface**: Defines the exchange of business information between trading partners.  In CVISN, the  interfaces that exchange data are grouped as carrier-to-state, state-to-CVISN Core Infrastructure systems, and within-state systems.
**The Design**: Must consider State’s business needs as well as long term plans for technology upgrades and services in other areas.  The design is related to the types of entities that exchange data.
**The Technologies**: Must be appropriate to support the design and business needs.

## CVISN Guidelines for Interface Design

## A state Web site approach provides a

**Carrier**

**State**

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

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

**World Wide Web**

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

**Web **
**Browser**

*Comparison of E-Credentialing Approaches*

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

**Notes:**
Electronic commerce in many industries is migrating to the web-site-based solutions.
Web-based capabilities offer less mature electronic credentialing capabilities than EDI, but at a potentially reduced cost. 
Supports carriers with minimal carrier investment 
The current CVISN architecture allows the use of web-based credentialing.

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

- Or Service Bureau

**State**

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

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

**EDI credentialing**
**standards exist.**
*XML credentialing*
*standards could be*
*developed.*** **

**Stand-alone CAT**

**Stand-alone CAT**

- Optional use for state branch offices

**Credentialing **
**Systems**

*Comparison of E-Credentialing Approaches*

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

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

## A CAT module could be integrated into

**State**

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

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

**EDI credentialing**
**standards exist.**
*XML credentialing*
*standards could be*
*developed.*

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

**Credentialing**
**Systems**

*Comparison of E-Credentialing Approaches*

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

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

## Dual Interface: A state could implement both

**Carrier 1**

**State**

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

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

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

**World Wide Web**

**HTML or XML, HTTP**

**Web **
**Browser**

*Comparison of E-Credentialing Approaches*

**PC CAT or CAT Module**

**E-mail or FTP**

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

**Carrier 2**

## Hybrid Interface: A Web site approach could incorporate a one-way computer-to-computer element.

**Carrier**

**State**

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

- Hybrid Interface: A Web site approach could incorporate a _one-way_ computer-to-computer element.

*Transactions are submitted via the web, but the user could request a computer processable response from the state that would enable the carrier to update their database.  This may provide many of the benefits of a full computer-to-computer interface at reduced cost.*

**World Wide Web**

**HTML or XML, HTTP**

*Comparison of E-Credentialing Approaches*

**FMS **
**Database**

**E-mail or FTP**

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

**Notes:**
In this hybrid model, the carrier uses their Web browser to submit credential application information.  Upon successful completion of the credentialing process, the carrier can request that the state send a computer processable response to use to update the carrier’s database.  
This approach has the low-cost benefits of the Web-site implementation, and the high-value of helping the carrier maintain their credentialing information electronically.
As in all of the Web-site implementations, the browser-to-Web-site interface could use HTML, dynamic HTML, or XML (invisible to the carrier, as long as they use a capable browser).  
The response from the state to the carrier could be based on ANSI X12 EDI, XML, or some other file format.

## Web-Enabled CI System Design

- MD
- Credentialing
- Web
- Site

- Web
- Files

- Data
- Base

- Browser

- Carrier

- MVA DB
- (stored procedures)

- VISTA/RS

- IRP backend
- (future)

- Stand-Alone
- CAT

- Core CI

**Firewall 1**

- IRP CSR
- CAT

- CI UI
- Client

- MD
- CVIEW

- MD Systems

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

**Firewall 2**

**DMZ**

**Notes:**
This illustrates one possible design, and shows the firewalls.

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

- State Systems

- Web & XML-
- Enabled
- Credentialing
- Interface

- IRP

- Stand-Alone
- CAT

**Database**

- IFTA
- Reg

- IFTA
- Tax
- Filing

- CVIEW

**Terminal**
**Server**

- Terminal
- Client

**EDI I/F**

**XML I/F**

- Fleet Management System

**Core CI**

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

- Browser

**Credentialing **
**Web Site**

**Web Database**

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

## Data interface choices implycommunications protocol choices

- State Systems

- Web & XML-
- Enabled
- Credentialing
- Interface

- IRP

- Stand-Alone
- CAT

**Database**

- IFTA
- Reg

- IFTA
- Tax
- Filing

- CVIEW

**Terminal**
**Server**

- Terminal
- Client

**EDI I/F**

**XML I/F**

- Fleet Management System

**Core CI**

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

- Browser

**Credentialing **
**Web Site**

**Web Database**

- Mail protocol: SMTP/POP3

- File transfer: FTP

- Web protocol: HTTP

- Terminal protocol: Telnet

**Notes:**
In this figure, the focus is on the communications protocols.

## Strategy for Carrier-to-State Interface (1 of 2)

- FMCSA _currently_
- requires an ANSI X12 EDI computer-to-computer interface
*	**and also*
- recommends a person-to-computer (i.e., a web site) interface
- In cooperation with states and other stakeholders, FMCSA is evaluating this policy to determine the need for change.

## Strategy for Carrier-to-State Interface (2 of 2)

- It has been recommended that FMCSA:
- _Require_ states implement *either* a computer-to-computer interface or a person-to-computer interface. The state should be able to supply evidence that their customers support this choice.
- _Recommend_ states implement *both* a person-to-computer and computer-to-computer solution.
- _Recommend_ carriers and states use X12 EDI for computer-to-computer interfaces unless the state has evidence that customers support another format.

*Summary*

## Strategy for State-to-Core Infrastructure Interface

- The interface for exchanging snapshot data between the State CVIEW (or CVIEW equivalent) and SAFER is an open standard (EDI) computer-to-computer interface
- The interface between the State and the IRP Clearinghouse is a custom interface as defined in IRP Clearinghouse Jurisdiction System Specification V1.6
- The interface between the State and the IFTA Clearinghouse is EDI
- The interfaces between FMCSA-developed safety-related systems (ASPEN and SAFER, ASPEN and CVIEW, SAFER and SAFETYNET, SAFER and MCMIS, SAFER and Licensing and Insurance) are based on custom interface agreements defined by the system developers and endorsed by FMCSA

## Strategy for Within-State Interfaces

- The CVISN architecture does not specify the types of interfaces to be used among in-state systems.  The state may choose computer-to-computer or person-to-computer solutions to support their business needs.  The state may choose any technology that supports their design choices.
- Computer-to-computer solutions: Custom interface, EDI or XML.
- Person-to-computer solutions: Web-site (HTML, XML)
- The State should consider interface choices that will minimize redundancy of effort and maximize maintainability

## Comparison of Electronic Credentialing Alternatives

- Simplified Comparison of Person-to-Computer & Computer-to-Computer Interfaces
- Simplified Comparison of Alternatives for Computer-to-Computer Interfaces:  EDI or XML

## A Simplified Comparison of Alternative Interfaces: Person-to-Computer vs. Computer-to-Computer

## A Simplified Comparison of Alternatives for Computer-to-Computer Interfaces:  EDI or XML

*With either EDI or XML:*
- Developers need to map data from the legacy format to the interface, and back again.
- All data users need to be able to interpret data coding in a standard way. (e.g., do we abbreviate Quebec as QC or PQ?)

**Notes:**
This discussion focuses on the use of XML to describe file formats, not as a replacement for HTML for Web interfaces. Thus, this discussion is all about computer-to-computer interfaces.

## More on the Technologies

- What is EDI?
- What is XML?
- When Should You Use XML?
- What Activities Are Ongoing?

## What is EDI?

**E**lectronic **D**ata **I**nterchange
- EDI is the electronic exchange of business information in a standard format that **permits computer generation and **_**processing**_** of the message.**
- ANSI X-12 EDI standards and user implementation guides **define the structure and **_**meaning**__ _of computer-to-computer messages passed between trading partners.  EDI transaction sets describe data structure, data type, data interdependencies and data usage.
- X-12 EDI is a standard for data exchange based on a 20 year history of consensus on data semantics.
- EDI is often implemented via the Internet.  By using the Internet to transmit EDI documents instead of VANs, companies can save 60 to 90 percent on communications costs.

## How Would EDI Work in CVISN Design?

- An EDI application consists of: EDI Standard + Implementation Guide + EDI translator + Custom Software
- EDI standards and IGs are available
- Commercial translators are available
- EDI cost is reduced by using the Internet to send and receive data
- EDI is well understood by the e-commerce business community
- EDI is the open standard of choice for CVISN external interfaces

## What is XML?

- XML is a metalanguage for creating a customized mark-up language to describe the **structure and content of documents**.  It is an outgrowth of document publishing and display technologies which is becoming popular in WWW applications.  It is a method, not a standard, for data interchange.
- Similar to HTML, XML uses a set of “tags” to describe document content.  Where HTML describes document _format_, XML describes document _content._
- 	HTML Example:  <tab>  means tab over here on the page
- 	XML Example :   <name> John </name>
- What an XML document does NOT tell you about the data exchanged: data type, data relationships/dependencies, data meaning

## Other XML Technologies and Languages

- Document Type Definition (DTD): Provides rules for using XML to represent documents of a certain type.  Defines the tags used.
- Schema: Goes beyond the DTD and describes meaning, usage, and relationships of data elements.  Schemas are likely to replace DTDs in XML applications within a year or two, but standards are still being developed and tools are not available.
- XML Parser: Checks for well-formed XML document (matching tags, proper nesting). A validating parser checks that document conforms with associated DTD.
- Style sheet: Describes how document is presented or displayed.
- XML Query Language: Notation for addressing and filtering the elements of XML documents.
- XML Pointer and XML Linking Language: Describes how to address a resource and how to associate two or more resources.

## How Do You Get XML to Work?

- For XML to work, you need mutually defined tags for data exchange, as well as industry-specific schemas to give the data meaning.
- Schemas are critical to data verification and processing and are currently under development.
-  Of note, regardless of the technologies used. . .
- To exchange information, developers need to map data from the existing (legacy) format to the interface, and back again.
- You still need custom software to extract and insert data into your applications.

## How Would XML Work in CVISN Design?

- An XML application consists of: XML Standards + XML Document + DTD or Schema + XML parser + Custom Software
- XML standards and many industry schemas are under development
- XML translators and parsers are inexpensive or free; more sophisticated and expensive tools are also available
- XML for within-state (custom application) may be a reasonable choice
- Properly designed XML solution will promote client-side processing, more efficient use of server resources, faster response time
- XML is not necessarily  “easier” for the developer
- XML may be the best thing since sliced bread when it fully matures

## When Should You Use XML?

- Source: Pitts-Moultis, *XML Black Book. *The Coriolis Group, 1999.  ISBN: 157610284X

## When Should You Use XML?

- Source: Pitts-Moultis, *XML Black Book. *The Coriolis Group, 1999.  ISBN: 157610284X

## What Activities Are Ongoing? (1 of 3)

- 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.
- The ebXML initiative is endorsed by leading industries and the ANSI X12 Committee.  Draft standard due out within the year.
- States are implementing Web-based credentialing.

**Notes:**
After going over this material, also mention that FMCSA is conducting a survey of carriers, service providers, states, and fleet management system vendors to try to assess the market/need for standardized computer-to-computer interfaces between carriers and states.  The results of the survey will also shape changes to the architecture.

## What Activities Are Ongoing? (2 of 3)

- FMCSA is exploring the use of XML in computer-to- computer applications for CVISN
- XML interface for IRP credentialing in Maryland
- XML interfaces to SAFER
- Tracking technology development and industry efforts to define data repositories and schemas
- If the prototypes are fruitful, the architecture may be changed.

**Notes:**
After going over this material, also mention that FMCSA is conducting a survey of carriers, service providers, states, and fleet management system vendors to try to assess the market/need for standardized computer-to-computer interfaces between carriers and states.  The results of the survey will also shape changes to the architecture.

## What Activities Are Ongoing? (3 of 3)

- FMCSA has just completed a survey of carriers, service providers, states, and fleet management system vendors to try to assess the market/need for standardized computer-to-computer interfaces between carriers and states.
- The survey results shaped the recommendations to FMCSA, described under “Strategy for Carrier-to-State Interfaces”, for the changes to the architecture.

## Terminology

- CVISN
- Electronic Credentialing
- Computer-to-computer interface
- Person-to-computer interface
- Open Interface Standard
- EDI (Electronic Data Interchange)
- Proprietary Interface
- Local Area Networks (LANs)
- Wide Area Networks (WANs)
- Value-Added Networks (VANs)
- The Internet
- The World Wide Web (WWW or The Web)
- HTML (Hypertext Markup Language)
- XML (eXtensible Markup Language)
- EDI Over the Internet

*Refresher - Terminology*

*Terminology*
*In order to get accurate information from the survey, it is important that we use common terminology.  Definitions are included in the Terminology section after this slide.  Please review the definitions of any terms unclear to you and ask for clarification from the interviewer.*

## Terminology -- CVISN

- Commercial Vehicle Information Systems and Networks (CVISN, pronounced “see vision”)
- 	Refers to the ITS information system elements that support Commercial Vehicle Operations. CVISN includes information systems owned and operated by governments, carriers, and other stakeholders.
- CVISN focuses on three major capability areas
- Safety Information Exchange
- Credentials Administration
- Electronic Screening
- Electronic Credentialing
- 	The process which allows carriers, owners, and drivers to apply for, pay for, and receive credentials electronically.

*Refresher - Terminology*

## Terminology -- Interfaces

- Computer-to-computer interface
- 	How two (or more) computers exchange information.  The computers can be programmed to automatically exchange information electronically.  The computers generate, send, receive, and process data with no (or limited) involvement by a person.
- Person-to-computer interface
- 	How a person and a computer exchange information.  Today, this is typically through a graphical user interface (GUI) in which information is shown to a user on a video monitor in an easy-to-follow way.  GUIs also collect inputs from users through a keyboard and mouse.

## Computer-to Computer Interface Using Open Standards

**Communications**
**Networks**
**(e.g., the Internet)**

**Motor Carrier Applications**

**Application Database**

**Custom Data Extract/Insert**

***Commercial Translator***

**MOTOR CARRIER**

**State Applications**

**Application Database**

**Custom Data Extract/Insert**

**STATE**

**Open**
**Standard**

**Open standards and supporting documentation allow motor carriers, states, and other trading partners to exchange safety and credentialing information.**
**An open standard interface can be added to existing systems through some custom coding and, perhaps, a commercial-off-the-shelf translator.**

***Commercial Translator***

**Open**
**Standard**

*Comparison of E-Credentialing Approaches*

**Open**
**Standard(s)**

## Terminology -- Standards

- Open Interface Standard
- An interface definition that has been developed and adopted by a standards development organization (SDO) such as ANSI or IEEE, and that is published and available to the public for use.
- EDI (Electronic Data Interchange)
- Often used as a shorthand for American National Standards Institute (ANSI) Accredited Standards Committee (ASC) X12 EDI.  EDI is an example of an open interface standard that is widely used for the electronic exchange of business information in a format that permits computer generation, exchange, and processing of  messages.
- EDI standards and user implementation guides define the structure and meaning of computer-to-computer messages passed between trading partners.

*Refresher - Terminology*

## Terminology - EDI Over the Internet

- EDI transactions can now be sent over the Internet instead of over a VAN.
- VANs were the common method of EDI transmission until the past few years.
- Internet EDI has attracted a lot of attention because of its ability to dramatically lower the cost of EDI communications.  By using the Internet instead of VANs to transmit standardized EDI transaction sets, companies can save 60 to 90 percent on communications costs.

*Refresher - Terminology*

## Terminology -- Proprietary Interface

- Proprietary Interface
- 	An interface definition that has been developed by one or more companies for use in their private or commercial systems and is not available for public use.
- 	Use of a proprietary interface can cause a customer to be “locked in” to a specific vendor.

## Terminology -- Networks

- Local Area Networks (LANs)
- 	Networks designed for geographically local areas, such as a building or a campus.
-  Wide Area Networks (WANs)
- 	Networks consisting of LANs of various protocols, supporting myriad media and architectures, and spanning cities, countries, and continents.
- Value-Added Networks (VANs)
- 	VANs often bundle other services with wide area network (WAN) connectivity.  Services can include automatic error detection and correction; protocol conversion (for example, from EDI format to legacy system format); or message storing and forwarding.  AAMVANET is an example of a VAN.

## Terminology -- The Internet and the Web

- The Internet
- Worldwide public, cooperative, self-sustaining system of computer networks.  The Internet can support both computer-to-computer and person-to-computer interfaces.
- The World Wide Web (WWW or The Web)
- All the resources and users on the Internet that are using the Hypertext Transfer Protocol (HTTP).  The Web is the most widely used part of the Internet.
- A browser is an application program that provides a way to look at and interact with all the information on the World Wide Web. A Web browser uses the Hypertext Transfer Protocol (HTTP) to make requests of Web servers throughout the Internet on behalf of the browser user. Two widely used browsers are Netscape Navigator and Internet Explorer.

*Refresher - Terminology*

## Terminology -- Web Languages

- HTML (Hypertext Markup Language)
- 	The set of "markup" symbols or codes inserted in a file intended for display on a World Wide Web browser. The markup tells the Web browser how to display a Web page's words and images for the user.
- XML (eXtensible Markup Language)
- 	A flexible way to create common information formats and share both the format and the data on the World Wide Web, intranets, and elsewhere.
- 	Particular applications are defined through three elements:  Document Type Description (comparable to a data base schema), Stylesheets (to explain how to present information to the user), and Links between resources (for example, between index and content).

**Notes:**
XML can be used to define how to display a web page’s words and images, but can also be used to define how to process the contents of messages exchanged through the Web or elsewhere.

## Terminology -- Web Languages (concluded)

- Similarities
- Both XML and HTML contain markup symbols to describe the contents of a page or file.
- Differences
- HTML, however, describes the content of a Web page (mainly text and graphic images) only in terms of how it is to be displayed and interacted with.  XML describes the content in terms of what data is being described.  XML is "extensible" because, unlike HTML, the markup symbols are unlimited and self-defining.

*Refresher - Terminology*