# Presentation: 659940

## Session 3

**Operational Concepts**

- S1	Welcome and Introduction
- S2	Introduction to Safety Information Exchange
**S3****	****Operational Concepts**
- S4	System Overview
- S5	CVIEW Networking
- S6	Microsoft Windows NT
- S7	Standard Procedures
- S8	System Configuration
- S9	Change and Problem Tracking
- S10	CVIEW Versions
- S11	Using OpCon
- S12	Laboratory Exercises
- S13	Wrap-up

## Session Plan

- In this session we will cover:
- What services does CVIEW provide?
- What data is stored in SAFER/CVIEW and how is it exchanged?
- Data Description
- Data Flow
- Data Access Methods
- Data Communications
- Data Updates
- How does SAFER facilitate communications between SAFETYNET and MCMIS
- How will SAFER support PRISM

## Session Objectives

- To provide the system operations staff background knowledge of what the system does and how it does it
- This information will help the staff to...
- Understand why specific operations must be performed
- Understand what the various software processes are and how they work together
- Know where to start when trouble-shooting a problem

## CVIEW Data Exchange Services

**CVIEW currently provides users the following data exchange services:**
- Carrier and vehicle snapshot data via user subscriptions
- Online query support for carrier snapshots via application-based e-mail requests
- Snapshot segment updates from state legacy systems, e.g. MD IRP and intrastate vehicle registration data
**Future data exchange services to be provided by CVIEW include:**
- Support for requests to store and retrieve inspection reports via SAFER, i.e. inspection reports won’t be stored directly in CVIEW’s database

## What Data Are Provided To Users?

- CVIEW provides access to summaries of safety and credential data (snapshots) and inspection reports (Version 3) for use by
- Roadside inspectors
- Automated screening equipment
- Access is provided through
- On-line queries
- Subscription services

## Data Stored in SAFER/CVIEW

- Snapshots

## Definition of Snapshot-Related Terms

- Identifiers & Census Data
- Data used to distinguish one carrier, vehicle, or driver from another.
- Historical Safety & Credential Information
- Information that characterizes the past safety performance of the carrier or driver; information about the carrier’s or the vehicle’s credentials, such as registration.
- Check Flags
- Indicator set by the authoritative source to alert users that there has recently (e.g., within a day or a week) been some problem with the associated credential.  Since the check flag does not attempt to reflect up-to-the-minute status, the problem may have been resolved and the flag not yet reset by the source.
- Current Safety Status
- Most recent safety indicators, for instance, out-of-service (OOS) status.

## Data Exchanged through CVIEW but Stored in SAFER

- Inspection Reports (stored for a 45 day period)
- Census information about an inspected driver
- Carrier ID information (USDOT#, ICC#)
- Cargo information
-  Vehicle ID information (Make, Model, Yr., Plate/State...)
- Hazardous material Information (if applicable)
- Brake Adjustment Information
- Vehicle Violation Information

## How is Data Exchanged Between SAFER and Other Systems and Users?

- Several systems provide data to and retrieve data from SAFER. These include:
- Motor Carrier Management Information System (MCMIS)
- Roadside Systems
- ASPEN Application
- Past Inspection Query (PIQ) Application
- Inspection Selection System (ISS) Application
- Roadside Operations Computer (ROC) Application
- SAFETYNET Systems
- CVIEW Systems
- Licensing & Insurance System

## SAFER/MCMIS: Safety Data Exchange

## SAFER/MCMIS: Safety Data Exchange

- Flow 3 - SAFER sends inspection data to MCMIS via the SAFER Data Mailbox system
- Flow 7 - Compliance Review data, crash data, enforcement data, and manually generated inspection reports are sent from SAFETYNET to MCMIS via the SAFER Data Mailbox system
- Flow 8 - MCMIS generates carrier safety snapshot data and sends it to SAFER on a weekly basis

## SAFER/Roadside: Safety Data Exchange

## SAFER/Roadside: Safety Data Exchange

- Flow 1 - represents the transmission of vehicle and/or driver inspection data from the ASPEN client or equivalent, to SAFER via the SAFER Data Mailbox (SDM) where it is stored for a forty-five day period
- Flow 2 - Previously stored inspections can be retrieved from SAFER via the Past Inspection Query (PIQ) application, which also interacts with SAFER via the SDM
- Flow 9 - Via the subscription process, SAFER transmits safety snapshot data to the Inspection Selection System (ISS) application
- Flow 10 - SAFER could send snapshot data to the Roadside Operations Computer (ROC); however, there are no ROC subscriptions currently defined on the SAFER system

## SAFER/SAFETYNET: Safety Data Exchange

## SAFER/SAFETYNET: Safety Data Exchange

- Flow 4 - SAFER sends inspection data to the state’s SAFETYNET system via the SAFER Data Mailbox (SDM)
- Flow 5 - Compliance Review data, electronically recorded using CAPRI, crash data, enforcement data, and manually generated inspection reports are sent to SAFETYNET from other sources within the state
- Flow 6 - Compliance Review data, crash data, enforcement data, and inspection reports are transmitted from SAFETYNET to MCMIS via the SDM on SAFER

## SAFER/CVIEW/Roadside: Safety Data Exchange

## SAFER/CVIEW/Roadside: Safety Data Exchange

- Flow 1 - represents the transmission of vehicle and/or driver inspection data from the roadside, via the ASPEN client or equivalent, to a state’s CVIEW system
- Flow 2 - CVIEW doesn’t store the inspection data but rather passes it through to SAFER, where it is stored for a forty-five day period
- Flows 3 & 4 - represent the return of one or more inspection reports from SAFER through CVIEW to the roadside in response to a query from a user via the Past Inspection Query application (PIQ)
- Flow 13 - Via the subscription process, SAFER sends safety and credential snapshot data to CVIEW
- Flow 14 - Via the subscription process, CVIEW sends data it received in Flow 13 to the roadside operations computer (ROC)
***	******(Note, Flows 1 - 4 are future CVIEW capabilities that will be incorporated in Version 3.0 of the software)***

## SAFER/CVIEW/Roadside: Credential Data Exchange

## SAFER/CVIEW/Roadside: Credential Data Exchange

- Flow 1 - represents the transmission of registration and fuel tax information from state legacy systems, via legacy system interfaces (LSIs), to the state’s CVIEW system
- Flow 2 - Via the subscription process, CVIEW sends SAFER interstate credential data received from the state to make it available across jurisdictional boundaries
- Flow 3 - CVIEW receives interstate credentials data (obtained from the Clearinghouses (future) and the Licensing and Insurance system) from SAFER
- Flow 4 - CVIEW sends inter- and intrastate credentials data to the roadside

## How Does CVIEW Provide Data To Users?

- Access is provided through
- On-line queries
- Subscription services

## Access to CVIEW: Online Queries

**CVIEW Data Mailbox**
**System**

**Send Data**
**Request**

**Retrieve Mail Message; **
**Extract Requested Data**

**Retrieve Requested Data**
**(Inspection Reports;**
**Carrier Snapshots)**

**(1)**

**(2)**

**(4)**

**CVIEW System**

**Send Mail Message **
**With Requested Data**

**(5)**

**MCSAP Inspector**

**SAFER System**

**(3)**

**Data Request; Carrier Snapshot**
** ****or IR returned**

## Online queries are based on the use standard e-mail data exchange (Simple Mail Transfer Protocol (SMTP) for sending e-mail; Post Office Protocol (POP3) for retrieving e-mail
Each CVIEW user is provided two personal mailbox accounts: one for on-line queries and a second, to receive subscription data
Via a client application, users send requests for data to CVIEW, i.e. make online queries, via CVIEW’s input mailbox 
CVIEW retrieves and processes the request     . If the data request is for an inspection report or for a carrier snapshot that is missing from CVIEW’s database, CVIEW issues a request for the data to SAFER, which is returned to CVIEW via an RPC link
CVIEW returns the requested data to the user’s via the user’s personal on-line query mailbox      which is read by the client application
Currently, online queries for carrier snapshots are supported; support for vehicle inspection reports to be available in Version 3

- Each CVIEW user is provided two personal mailbox accounts: one for on-line queries and a second, to receive subscription data
- Via a client application, users send requests for data to CVIEW, i.e. make online queries, via CVIEW’s input mailbox
- CVIEW retrieves and processes the request     . If the data request is for an inspection report or for a carrier snapshot that is missing from CVIEW’s database, CVIEW issues a request for the data to SAFER, which is returned to CVIEW via an RPC link
- CVIEW returns the requested data to the user’s via the user’s personal on-line query mailbox      which is read by the client application
- Currently, online queries for carrier snapshots are supported; support for vehicle inspection reports to be available in Version 3

- Access to CVIEW: Online Queries

**(1)**

**(2)**

**(4)**

**(5)**

**(3)**

## Access to CVIEW: Subscription Processing

**Subscription**
**Mailbox**

**User**
**Mailboxes**

**CVIEW Data Mailbox**
**System**

**CVIEW Operator stores **
**subscription definition in **
**CVIEW for processing**

**User’s application retrieves **
**data from subscription mailbox**

**(1)**

**(3)**

**CVIEW System**

**CVIEW stores processed **
**data in subscription mailbox**

**(4)**

**CVIEW**
**User**

**Manually Request a **
**Subscription**

**(2)**

## Access to CVIEW: Subscription Processing

- A subscription is a manually generated request for CVIEW to provide one or more users a specific set of data using a specified format and delivery rate
- A user defines a subscription via a CVIEW System Operator     , who stores the definition in CVIEW for subsequent processing
- CVIEW processes the subscription data for each user and stores it in their individual subscription mailbox
- A user with a client application such as ASPEN, retrieves data from their personal subscription mailbox based on the data format and delivery rate specified in the subscription
- Currently, subscriptions for carrier and vehicle snapshots are supported

**(1)**

**(2)**

**(3)**

**(4)**

## Views

- A view is a collection of data elements in a carrier, vehicle, or driver snapshot
- A view can be comprised of all data elements in a snapshot, i.e. a Full View, or a subset of those data elements
- Views are created to address the data exchange requirements of specific user groups. For example, the Inspection Selection System (ISS) View is used by roadside inspectors that use the ISS application
- Views are used by CVIEW to define the data elements it sends to and receives from external users and systems

## Data Formats

- CVIEW supports several different types of data formats. These include:
- Electronic Data Interchange (EDI) - a format for exchanging data based on ANSI X12 standards; supports computer-to-computer interfaces
- Application File Format (AFF) -  a format for exchanging data, which is based on ANSI X12 standards but does not require the use of an EDI translator; supports computer-to-computer interfaces
- Custom Interface Agreement (CIA) - non-standardized data formats that typically supports data exchange between CVIEW and a client
- Legacy System Interface (LSI) - non-standardized data formats that typically supports data exchange between CVIEW and a legacy system

## Data Communication Methods

- CVIEW supports several different communication methods for exchanging data. These include:
- E-mail - based on Simple Mail Transfer Protocol (SMTP) for sending mail to CVIEW and Post Office Protocol (POP3) for retrieving mail from CVIEW
- Remote Procedure Calls (RPC) - A communications standard that supports data exchange among remotely distributed applications. CVIEW uses RPCs to support one type of carrier data exchange with SAFER
- File Transfer Protocol (FTP) - used to support exchange of LSI flat files from legacy systems to CVIEW

## How and When Does CVIEW Receive Data From External Systems?

- Today, CVIEW 1.6.8 receives carrier and vehicle subscription data from SAFER on a weekly and daily basis, respectively.
- Starting with CVIEW 2.3, Virginia’s CVIEW system will sends SAFER periodic updates of vehicle IRP and carrier and vehicle E-screening data. SAFER will forward that information, via subscription processing, to any other state CVIEW system interested in receiving that data.

## SAFETYNET 2000 Interface

- May - Aug 2000 - SAFETYNET 2000, Beta testing; Windows NT and 95 support; Oracle RDBMS; enhanced communications including SAFER connectivity

## Slide 30

## PRISM Interface

- PRISM = Performance & Registration Information Systems Management
- SAFER has been providing electronic data exchange support to the PRISM Pilot Project since April, 1996
- Carrier snapshot updates, formatted as a PRISM Data View,  provided to three of the original PRISM Pilot States weekly;
- Design work for batch and interactive communications via the SAFER Central Site is in progress

## NCS

- SNA

- NLETS

- Gateway

- IE

- SAFER
- Data Mailbox

- TCP/IP

- PRISM

- Architecture
- Overview

- SAFER:Prism
- Central
- Site

- b

- a

- t

- c

- h

- inter-
- active

- State
- Police
- Systems

- SNA

- SNA

- MCMIS

- (FMCSA)

- SNA

- TCP/IP

- TCP/IP or Dial-up

- TCP/IP or
- Dial-up

- TCP/IP
- via FTS2000 link