# Presentation: 860019

## Session 8

- 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 8**
**Electronic Screening**

## Session Plan

- Overview: Electronic Screening (21 min)
- Existing Screening Programs (12 min)
- Screening Factors (5 min)
- Example Screening Scenario (12 min)
- Breakout Plan (5 min)
*BREAK (15 min)*
- Breakout: State CVISN System Design (120 min)
- State Presentations & Questions (30 min)
- Total Time = 220 min (3 hrs, 40 min), including 15-minute break

**Notes:**
E-Screening Overview
Physical View
Information Systems View
Components
DSRC
ROC
Screening Computer
Benefits
E-Screening Enrollment
Leave this up as an overhead

## Session Objectives

- Understand CVISN operational concepts and architectural guidelines related to Electronic Screening:
- Electronic screening components
- Using snapshot-based screening to evaluate both safety and credentials information
- Interoperability
- Walk through an electronic screening example
- Make initial design decisions related to electronic screening

**Notes:**
Be sure to point out that the functional thread diagram shown here is AN EXAMPLE.  There are different approaches to electronic screening, and they should make their diagram reflect the approach they intend to use.  The CVISN Guide to Electronic Screening should include other examples. 
Emphasize snapshot-based screening

## E-Screening Operational Scenario:Fixed Site

**4.  Compliance reader interrogates tag to verify vehicle has been cleared to Bypass.  **

**2.  WIM/AVC data and infrastructure data (Carrier & Vehicle Snapshots) are processed to determine clearance status (Bypass).  **

**3.  DSRC sends clearance status (Bypass) to the tag.  Driver is signaled by tag LEDs.**

- _Acronyms_
- AVC - Automatic Vehicle Classification
- DSRC - Dedicated Short Range Communication
- IFTA - International Fuel Tax Agreement
- IRP - International Registration Plan
- OOS - Out of Service
- SAFER - Safety and Fitness Electronic Records
- SafeStat - Safety Status
- WIM - Weigh In Motion

*Overview*

- E-Screening Operational Scenario:Fixed Site

**A.  Carrier & Vehicle Snapshots are downloaded from SAFER to the roadside system.  Snapshot data includes Safety (SafeStat, OOS) and Credential (IRP, IFTA) information.  **

**Notes:**
STATE:  This is a reminder from the Intro to ITS/CVO Training.
Quickly walk through the scenario to remind students what screening is.
Possible DSCR Readers:  Clearance, Compliance, Ramp, Static Scale
Clearance is granted as a result of screening

## Electronic Screening Definitions & Functions

- 	A selection mechanism to make efficient use of limited fixed weigh station and inspection resources
**Electronic Screening:**
- 	Application of technology to the screening process to make an informed decision whether further examination of a vehicle is required
**The Electronic Screening capability area provides for:**
- Screening vehicles that pass a roadside check station based on identifiers read from the transponder, correlated with safety and credentials information from snapshots;
- Using snapshots updated by a SAFER/CVIEW subscription in an automated process to support screening decisions;
- Identifying overweight, oversize, and improperly credentialed vehicles;
- Determining whether a safety inspection or verification of credentials is required & taking appropriate actions.

*Overview*

## Interoperability Principles establish the guidelines for electronic screening

- All the general principles (e. g., voluntary; interoperable across US and North America; CVO systems interoperable with other ITS systems; common standards for hardware, systems/software, operations, and program administration) apply to e-screening.
- Others define more targeted principles specific to roadside electronic screening:
- Single transponder
- Screening criteria
- Enrollment
- Price & payment
- Sharing transponder information

## Screening-Specific Interoperability Principles:Details

- Commercial vehicle operators will be able to use one transponder for power unit-to-roadside communications in support of multiple applications including electronic screening, safety assurance, fleet and asset management, tolls, parking, and other transaction processes.
- Roadside electronic enforcement screening criteria will include the following: motor carriers must be enrolled in the jurisdiction's program; must meet the jurisdiction's enrollment criteria; and must meet all legal requirements established by the jurisdiction.
- Motor carrier participation in ITS/CVO roadside electronic screening programs will be voluntary; motor carriers will not be required to purchase or operate DSRC transponders.
- Motor carriers will have the option of enrolling in any ITS/CVO roadside electronic screening program.
- Jurisdictions will support uniform criteria for enrollment of motor carriers in ITS/CVO roadside screening programs.
- Enrollment criteria will include consideration of safety performance and credentials status (e.g., registration, fuel and highway use taxes, and insurance).

- No jurisdiction will be required to enroll motor carriers that do not meet the criteria for enrollment.
- Motor carriers may obtain a DSRC transponder from the enrolling jurisdiction or a compatible DSRC transponder from an independent equipment vendor of the motor carrier's choice.
- Each jurisdiction will determine the price and payment procedures, if any, for motor carriers to enroll and participate in its ITS/CVO electronic screening program.
- Jurisdictions shall work to establish business interoperability agreements among roadside electronic screening programs.
- A jurisdiction will make a motor carrier's DSRC transponder unique identifier available to another jurisdiction upon written request and authorization by the motor carrier.
- Jurisdictions will work toward development of a single point of contact for motor carriers enrolling in more than one ITS/CVO roadside screening program.
***Reference***: Intelligent Transportation Society of America, _*Interim*_* ITS/CVO Interoperability Guiding Principles*, published on the World Wide Web at _[http://www.itsa.org](http://www.itsa.org/)_, last updated January 12, 1999.

**Notes:**
Investment and participation in ITS/CVO technology will be voluntary.
The CVO community will work to implement interoperable ITS/CVO systems in all United States jurisdictions.
The CVO community will work with the CVO communities in Canada and Mexico to implement interoperable ITS/CVO systems throughout North America.

## Various components are utilized according to site requirements and goals

- DSRC Readers and Antennas
- Weigh In Motion (WIM)
- Automatic Vehicle Classification (AVC)
- Vehicle Tracking Loops
- Automatic Signing (variable message signs and traffic signals)
- Roadside Operations Computer (ROC)
- Screening Computer

*Overview*

**Notes:**
This just summarizes the components already discussed on diagram of the walk-through.

## E-Screening uses the safety & credentials information in snapshots and real-time measurements to make the screening decision.

***Roadside electronic screening focuses resources on high risk operators:***
***	******Identify transponder, carrier, vehicle via DSRC transponder & standard messages***
***	******Check snapshot information when making screening decisions***
***	******Inform Driver via transponder***
***Notes:***
***Pull in untagged vehicle to identify carrier & vehicle; can still use snapshot to help make inspect/not inspect decision***
***Before issuing a citation, check with authoritative source for latest status***

- 1

- 2

- 3

- E-Screening uses the safety & credentials information in snapshots and real-time measurements to make the screening decision.

**CVISN Core Infrastructure**

**State Roadside Systems**

**Screening **

**Roadside **
**Operations**

**Other State Systems**

**DSRC**

- 1

- 3

- 2

**Leg Sys Mods**

**or**

**EDI**

**MCMIS**

**EDI**

**or**

**EDI**

**CVIEW**

**SAFER**

*Overview*

**Notes:**
This diagram is conceptual, and doesn’t show exactly what happens in some states today.  For instance, in the HELP PrePass model, the Screening System at the roadside works from a list of pre-cleared transponder IDs.  Hopefully, the PrePass system will use snapshot data to help make the pre-clearance decision.
STATE: We have already discussed how safety and credentials information are assembled into snapshots and distributed to the roadside by SAFER and CVIEW.
As shown in this figure, functions associated with electronic screening are distributed among three roadside systems 
Screening System (more detail on page 10)
Screening decision
Screening messages
Roadside Operations System (more detail on page 9)
Interface to CVIEW and other information systems
Station operator interface
Traffic flow and control
Sensor & Driver Communications System
Vehicle measures
Driver signaling 
STATE:  We will walk through the information flow in detail later using a thread diagram.

## Emerging Dedicated Short-Range Communications (DSRC) standards support near- and long-term goals (1 of 2)

- In the near-term, FHWA has issued this policy guidance:
*	**For the immediate future, all CVO and Border Crossing projects will continue to utilize the current DSRC configuration, which is an ASTM version 6 active tag. *

*Overview*

## Emerging Dedicated Short-Range Communications (DSRC) standards support near-term and long-term goals (2 of 2)

- FHWA issued a Notice of Proposed Rulemaking (Federal Register 30 December 1999) that would require:
*	**All CVO and Border Crossing projects to use an active configuration that is backward compatible with the current configuration and yet consists of the following “sandwich” protocol:*
*ASTM PS-111-98 (v7) defines the frequency (physical) layer,*
*ASTM v6 defines the data link layer,*
*IEEE Std 1455-1999 defines the application layer.*
- 	Mark IV has announced development of the T3 transponder that will support the sandwich protocol.

*Overview*

**Notes:**
Might want to refer to the specification for the sandwich tag (should be a copy on the reference table):

## E-Screening Components:Roadside Operations

- Process snapshots and control site traffic.
- Interface to CVIEW – get snapshot data
- Support legacy operator interfaces (Static Scale, CDLIS, NLETS, Traffic Flow)
- Control “pull around back” messages and signal lights
- Interface to Screening component (send criteria, get screening results, get sensor data, send snapshot summaries)
- Interface to report activities from other roadside systems to infrastructure, and vice versa
- On request, retrieve report data and display
- Process snapshot data into local database
- Track position of each vehicle moving through the station
- Allow operators to set/view screening criteria
- Display sensor data to operator
- Display snapshot data to operator
- Display vehicle position data to operator (e.g. mainline, ramp, scale lane, inspection area)

***The Roadside Operations component performs these functions:***

- E-Screening Components:Roadside Operations

**Roadside **
**Operations**

**L**
**M**

**CVIEW**

**CDLIS**

**285, 284, 824, 997**

- Existing sensor data,
- Existing message control

- Non-EDI to report station activities;
- State’s option to also use for snapshots and safety reports

- Snapshots, safety reports

- Driver check

- Snapshot summaries,
- Screening criteria,
- Sensor data;
- Screening results

*Overview*

**Notes:**
This slide shows a set of functions typically allocated to the Roadside Operations component.  
The Roadside Operations component gets snapshots from CVIEW, and pre-processes the data to boil it down to simple pull-in/bypass recommendations for the Screening component.  
The Roadside Operations component also provides the user displays for the site personnel.  

## E-Screening Components:Screening

- Make pass/pull-in decision.
- Interface to sensor/driver communications system
- Interface to Roadside Operations system (get snapshot summaries, send sensor data, send screening results)
- Sort vehicles on mainline or ramp, using: sensor data, snapshot data, availability of inspector, operator configuration selections
- Output screening results to tag via DSRC (includes driver notification)
- Control screening messages and signal lights
- Configure screening based on operator control (via Roadside Operations system) data

***The Screening component performs these functions:***

- E-Screening Components:Screening

**Screening **

**L**
**M**

- Existing sensor data,
- Existing message control

- New sensor data;
- Bypass or pull-in;

**DSRC**

- Snapshot summaries,
- Screening criteria,
- Sensor data,
- Screening results

*Overview*

**Notes:**
This slide shows a set of functions typically allocated to the Screening component.  
The Screening component makes the bypass/pull-in decision using a combination of screening factors (weight/size, safety and credentials data from snapshots, random choice)
The screening computer is an non-staffed position (as contrasted with the ROC).

## Electronic Screening Offers Benefits to both States and Carriers

- More efficient carrier operations and movement of freight, since safe and legal operators will be pulled in less often
- Reduced traffic flow in and out of weigh stations
- Improved safety and credentials compliance statistics to support policy decisions, rule making, and program development

- Electronic Screening Offers Benefits to both States and Carriers

*Overview*

**Notes:**
More focused vehicle inspections should lead to increased compliance
Statistics will be generated as more vehicles are enrolled and have transponders

## The Plan: Electronic Screening Enrollment collects & shares data about carriers & vehicles that want to participate in electronic screening.

- Carrier

- E-Screening
- Enrollment
- (May be Transponder
-  Administrator)

- SAFER

- CVIEW

- CVIEW

- E-Screening
- Enrollment
- (May be Transponder
-  Administrator)

- Carrier

***Enrollment request & data***
***Snapshots & snapshot segment updates***
***Snapshots for roadside use***

**1**

**3**

**2**

**1**

**1**

**2**

**2**

**2**

**2**

**3**

**3**

***Enrollment data are shared across jurisdictions and screening programs through snapshots***

***Carrier based in state A***

***Carrier based in state B***

*Overview*

**Notes:**
1.  The Enrollment Request is made by the carrier to a state or a transponder administrator.  The Request includes a list of all states in which the carrier wants to be screened electronically.  In the generic design, this interaction occurs via the Web.
2.  Through snapshots, the request is recorded and shared among all states requested.  Only the states in which the carrier wants to be screened electronically receive the transponder ID.
3.  At the state’s option, the E-Screening Enrollment process may evaluate the request, and accept or reject the carrier.  The Enrollment Responses may be recorded in snapshots and used at the roadside.  The transponder ID is included in the snapshots for the states the carrier requested.
Note: States may elect to share a common enrollment administrator.
The enrollment request is used to control which states see the transponder ID in the snapshot.
The enrollment responses may be used at the roadside to identify the carriers and vehicles that are enrolled in that state’s electronic screening program.
Note: Line 2 going from pink state’s ESE directly  to SAFER has been proposed; capability not yet approved.

## Electronic Screening: Enrollment and ParticipationHow this is addressed in the CVISN Architecture

- For a vehicle to benefit from electronic screening, some information must be gathered in advance.
- “Electronic screening enrollment” is the process of the carrier requesting to participate in electronic screening, and the state/program evaluating the carrier.
- During electronic screening enrollment, the cross-references between transponders, vehicles, and carriers are recorded in the snapshots.  Particular programs may also need to collect financial information.
- Then when an enrolled vehicle approaches a weigh station, bypass criteria are assessed, and the electronic screening decision is made.

*Overview*

**Notes:**
Recall that one tenet of the guiding principles is voluntary participation.
The Electronic Screening Enrollment process can be used to 
limit participation based on set criteria (the PrePass Premier Carrier approach) for pre-clearance
or simply to collect some basic information so that bypass decisions can be made in real-time based on the latest information

## There are two multi-state electronic screening programs, and other more localized approaches

- Screening Programs
- HELP (Heavy Vehicle Electronic License Plate), Inc./ PrePass - public/private non-profit corporation
- NORPASS (North American Preclearance and Safety System) - public/private non-profit corporation
- Oregon Green Light
- More localized approaches
- All are voluntary programs that use advanced technology.
- All share common goals:
- Safer commercial vehicle travel
- Save time and money
- PrePassTM and NORPASS have negotiated a one-way interoperability agreement where NORPASS vehicles may be eligible for clearance at PrePassTM sites.

*Existing Screening Programs*

## HELP PrePass

- Operational sites in Alabama, Arizona, Arkansas, California, Colorado, Florida, Illinois, Indiana, Iowa, Mississippi, Montana, Nebraska, Nevada, New Mexico, Ohio, Oklahoma, Tennessee, West Virginia, Wyoming.
- PrePass Service Center manages pre- and post-enrollment verification of carriers, provides transponders for vehicles.  Status of each enrolled carrier is checked (at least quarterly) against safety and credentials records and updated PrePass status records are passed to roadside sites.  The PrePass Service Center is a SAFER snapshot subscriber and is beginning to use snapshots to check carriers.
- Venture capital is used to deploy the PrePass system.  The carrier pays a fee for every time a vehicle receives a green light.  The fees are used to retire the venture capital debt.

*Existing Screening Programs*

**Notes:**
Updated per telecon with Jim Gentner Sept. 2001

## HELP PrePass (continued)

- Only the transponder ID is read from the tag.
- A list of carriers who choose to participate _and_ meet the jurisdiction’s criteria is shared with PrePass jurisdictions.  The Board of Directors (one government and one motor carrier official from each member jurisdiction) that oversees PrePass has established a data privacy policy to not share transponder ID or event data because of the voluntary nature of participation.
- HELP, Inc. retains clearance event data for internal business purposes only, and purges data following the normal monthly billing cycle.

*Existing Screening Programs*

**Notes:**
If court order, will segregate event data and provide to enforcement

## NORPASS

*Existing Screening Programs*

- Operational sites in Kentucky, Georgia, Idaho, Utah, and Washington.
- NORPASS Transponder Administrator manages enrollment of carriers, enrolled vehicle list, and periodic validation of carrier status.  Provides transponders, if needed.  Carriers enrolling in NORPASS jurisdictions contact the Transponder Administrator, which will then process enrollment in all the NORPASS jurisdictions in which the carrier wishes to be electronically cleared.  NORPASS intends to use SAFER/CVIEW snapshot data.

**Notes:**
From Crabtree, NORPASS in 2001
Operational sites are now in Kentucky, Georgia, Idaho, Utah, and Washington.
Connecticut may join NORPASS
Prior event data is no longer used, even in the former I-75 states.

## NORPASS (continued)

*Existing Screening Programs*

- States pay an annual membership fee to support NORPASS.  Carriers pay an annual administrative processing fee covering all NORPASS states, based on power units involved; no additional fees for clearance events.
- Only the transponder ID is read from the tag.
- Data about enrollment is shared with jurisdictions.
- The Transponder Administrator does not retain any data on clearance events.

## Oregon Green Light

- Operational sites in Oregon.
- Oregon DOT administers the distribution of transponders. Carriers are free to use the Oregon transponder in any/all other systems they choose.  Oregon intends to use SAFER snapshot data.
- No fees for carriers.
- Only the transponder ID is read from the tag.
- Weigh station event data collected automatically and manually is used for regulatory functions by Oregon enforcement officials.  Event data is also available to FMCSA officials and other states.

*Existing Screening Programs*

**Notes:**
From:	David.J.MCKANE@odot.state.or.us , Monday, September 18, 2000 4:47 PM
Oregon has 21 Green Light sites.  We also have one downhill speed information system at one of our sites.  This allows us to display a message to a truck driver via a variable message sign.  The message communicates to the driver and recommends a safe speed to decent a steep grade.  The speed is calculated by the weight and configuration of the truck.
ODOT  provides it's own transponder administration.  Carriers are free to use the Oregon transponder in any/all other systems they choose.  Obviously, the must agree to the conditions of the other system operators.  
Currently, Oregon includes in its bypass criteria the carriers safety fitness rating and safestat score.  Carriers with an unsatisfactory SFR are not allowed to bypass a weigh station.  Carriers with a safestat score over 150 are not allowed to bypass.  We are currently programming our software to include driver and vehicle out-of-service and ISS scores in the safety check.
There is no fee to motor carriers for the Green Light program.
Oregon Green Light sites can only read the transponder ID code.  If you are enrolled in Green Light, the transponder ID code will be associated with a license plate.
Weigh station event data collected automatically and manually is used for regulatory functions by Oregon enforcement officials.  Event data is also available to FMCSA officials and other states.

## Electronic Screening in Maryland

- MD has implemented electronic screening at Perryville site.
- Enrollment policy and fees are TBD.
- Transponder ID, Carrier ID, and Vehicle ID are read from tag.  IDs are correlated with snapshot data as input to the real-time screening decision.
- MD plans to share enrollment data through snapshots with jurisdictions designated by the carrier.
- MD uses JHU/APL-developed CVIEW, ROC and screening software to be developed by JHU/APL.  All software developed is in public domain.
- MD is currently participating in the I-95/Interagency Group CVO/ETC Interoperability project, where Mark IV Fusion transponders will be issued for use in both MD E-Screening and E-ZPass ETC.

*Existing Screening Programs*

**Notes:**
These were developed as model sites for the CVISN program and concepts
The key elements of these implementations:
Snapshot based screening
Capable of using vehicle and carrier ID’s if these are stored on the tag

## Failure on any single screening algorithm componentresults in pull-in condition

*Screening Factors*

- Failure on any single screening algorithm componentresults in pull-in condition

- Weight & Size
- Within legal or permitted limits
- History (being considered at some sites)
- Safety
- History
- Out-of-Service Status
- Credentials
- Taxes & fees
- Registration & permits
- Random pull-in factor

**Notes:**
In order to make efficient use of fixed weigh station and inspection resources, DSRC equipment allows a facility to identify the vehicle 
A typical configuration includes a screening WIM device integrated with an automated vehicle classification system to perform weight, size, and length checks, and a static scale to measure weight more precisely when the vehicle is stopped.  If the WIM and automatic vehicle classification (AVC) system are located in the roadway on the mainline, then “screening” (making pass/pull-in decisions) can be performed at mainline speed. 
The transponder ID (or, in the future, carrier and vehicle IDs) is correlated with safety and credentials data from the infrastructure, specifically with snapshot data.  In some programs, the evaluation is made at a central site periodically, and a list of “pre-cleared” vehicles or transponder IDs is passed to the roadside sites.
The bypass may be granted using a decision algorithm based on a number of factors such as credentials, weight information measured at a previous facility or safety histories.  This screening allows the facility to concentrate its resources on vehicles with delinquent fees, improper credentials, poor safety histories or otherwise seen as high risk.

## Screening FactorsSnapshot Record Types

*Screening Factors*

- Screening FactorsSnapshot Record Types

- Carrier
- IDs, census
- Safety
- Credentials
- Vehicle
- IDs, census
- Safety
- Credentials
- Driver  (future, optionally)
- IDs, census
- Safety
- Credentials

**Notes:**
Note: This slide builds.  First, the text comes up, then the key and the icons appear. 

The next page (hidden) shows category summaries for each snapshot.
Refer them to the snapshot white paper for more details.

## Screening Factors

*Screening Factors*

## Each Roadside Check Station is likely to have a unique design

- Each station’s design is unique because of:
- Policy & practice differences from state to state
- Traffic flow, volume, & number of lanes
- Available site space
- Legacy system characteristics
- Existing proprietary solutions
- Vintage of roadside and communications equipment
- Resources available for making changes

*Example Operational Scenario*

**Notes:**
This is the first slide in the section on the Example Operational Scenario.
Pick a couple of these to focus on.
EXAMPLE: Perryville, MD southbound site is located across the I-95 interstate from a toll plaza on the northbound side.  The toll plaza is equipped with DSRC for e-toll collection.  This requires that great care be taken in the DSRC configuration on the southbound side to avoid interference. 
There are tools to model weigh station design
Weigh Station Simulation (WESTA) developed by  Mitretek
The weigh station simulation model built by the Center for Transportation Research and Education at Iowa State University based on JHU/APL’s initial modeling efforts.  

## Screening Design Decisions: What’s reflected in the sample operational scenario...

- Screening Design Decisions: What’s reflected in the sample operational scenario...

- 1.	What agency has the lead for electronic screening in your state?
- The Commercial Vehicle Enforcement folks are leading our electronic screening efforts.  They are responsible for activities at the weigh stations.
- 2.	Do you already belong to or will you join an existing screening program?  Which one?
- We are setting up our own state specific system.  We will work with PrePassTM and NORPASS to establish interoperability agreements.  We will read carrier and vehicle IDs from the transponder.
- 3. What is your enrollment philosophy?  How will you share enrollment information with other programs?
- We let any carrier that is willing to participate enroll.  We will share enrollment information through snapshots.

*Example Operational Scenario*

**Notes:**
Talk about why these decisions were made.

## Screening Design Decisions: What’s reflected in the sample operational scenario...

- 4.	What screening factors do you use/will you use?  Will you screen using both carrier and vehicle data?
- We screen based on weight, safety history, credentials (IRP and IFTA to start).  Random selection also enters in.  We will use both carrier and vehicle data.
- 5.	Which site will you upgrade first to handle electronic screening?
- We are starting with a site on our main North-South interstate.
- 6.	Will you put WIM on the mainline?  On the ramp?  Both?
- We’ll use WIM on the mainline.
- 7.	At the first site, what new equipment do you need to support electronic screening?  What upgrades of existing equipment do you need?
- We will install WIM and AVC equipment, along with DSRC readers.  We’ll probably have to upgrade the on-site computers.

*Example Operational Scenario*

## Operational Scenario

- Screen vehicles electronically using snapshots
- Update screening decision-making data by loading snapshot updates
- Evaluate each vehicle
*NOTE: What follows is a generic scenario.  *
*Scenario details differ for particular screening programs.*

*Example Operational Scenario*

**Notes:**
For screening-related scenarios, it is often convenient to think of the steps in the operational scenario in two subgroups.
On this and subsequent pages, the groups are highlighted with the colors shown:
Yellow steps support the preparation for electronic screening: updating screening decision-making data by loading and processing snapshot updates (steps A-C),
Lavender cross-hatched steps correspond to the evaluation of each tagged vehicle as it approaches the weigh station (steps 1-4),
The slide show will skip to the thread diagram.  We will walk through the steps of the operational scenario [use overhead projector to show the list].
In the breakout session, you’ll develop operational scenario steps and a thread diagram for how you intend to perform the electronic screening process.  
Keep the scenario steps at about the same level of detail as in this example.  Each step should “name” the information being exchanged and what format (e.g., EDI TS 285) will be used for the exchange.  Also describe, at a high level, the processing performed.

## Operational scenario:Screen vehicles electronically using snapshots

- Operational scenario:Screen vehicles electronically using snapshots

- A - C are steps that occur ~ daily for the site
- A.	SAFER sends subscription updates to the state CVIEW for interstate carrier and vehicle snapshots, based on state-specified subscriptions. These snapshots are sent as TS 285 transactions. CVIEW maintains the intrastate snapshots.
- B.	CVIEW distributes carrier and vehicle interstate and intrastate snapshots to roadside sites, also based on specified subscriptions.  These are also sent as TS 285 transactions.
- C.	Enrolled carriers and vehicles are identified from the snapshots.  Site operators may interact with Roadside Operations to control local screening criteria, which will be based on the snapshot information.  The resulting carrier and vehicle specific screening “scores” or values are sent to the new screening system.  This is a local interface that is not subject to standards.

*Example Screening Scenario*

**Notes:**
Note: Intrastate data feed to CVIEW is not shown.
Note: Steps A & B are the same as the last steps of the inspection reporting scenarios done in the safety breakout yesterday.

Read through the steps, referring to the thread diagram.  

## Operational scenario:Screen vehicles electronically using snapshots

- Operational scenario:Screen vehicles electronically using snapshots

- 1 - 4 are steps that occur in real time for each vehicle
- 1.	Transponder ID, carrier ID, and vehicle ID are transmitted from the DSRC transponder on board the Commercial Vehicle to the Sensor/Driver Communications interface using ASTM version 6 and IEEE Std 1455-1999 CMV Screening Identification message.
- 2.	IDs are sent to Screening component.  IDs are correlated with carrier and vehicle snapshot data.  A screening decision is made.
- 3.	The screening decision is communicated back to the driver, again using the ASTM version 6 standards and the IEEE Std 1455-1999 message set.
- 4.	Screening information is communicated back to Roadside Operations for use by site staff.  This may be a non-standard interface.

*Example Screening Scenario*

## Functional Thread Diagram:Screen vehicles electronically using snapshots

**Generic State Roadside Systems**

**Generic State Commercial Vehicle Administration Systems**

**Carrier Systems**

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

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

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Compliance **
**Review **
**(e.g., CAPRI)**

**Service Providers**

**Internet Tools**
**(e.g. Browser)**

**Other Carrier**
**Systems**

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

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

**Transponder**

**Carrier Commercial**
**Vehicle**

**Web Site**

**Licensing &**
**Insurance**

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

- Functional Thread Diagram:Screen vehicles electronically using snapshots

*Example Screening Scenario*

**Notes:**
Note: This slide builds.  First, the yellow letters come up, then the lavender cross-hatched numbers.

## Breakout Goals

- Describe how you screen today (either manually or electronically)
- Set goals and objectives for electronic screening in your state
- Make initial design decisions related to electronic screening
- Illustrate electronic screening in your state using operational scenario and functional thread diagram
- Make initial allocation of new functions to existing or new computers and networks

*Breakout*

## What inputs are needed?What outputs are created? 

- Input/Pre-work needed:
- COACH Part 1 checklists in 4.1, 4.4
- System Inventory (optional)
- Roadside Operations
- Screening
- Keys & IDs
- Transponder Usage
- 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*

## Breakout Plan120 minutes

- Using your state’s CVISN system design template and network template, and following the example just presented, do the following:
**Step 1. **~10 min.  Assign roles.**  **Review & update COACH Part 1 checklists 4.1, 4.4.
**Step 2.** ~20 min.  Discuss how you perform screening today.  Set the near-term goals and objectives for electronic screening in your state.  Record the goals & objectives on a flip chart.  If necessary for the discussion, pick a particular site.
**Step 3.** ~30 min.  Referring to the Electronic Screening Design Decisions (please see pages 43-44), discuss design alternatives that support your goals and objectives.  Reach preliminary conclusions for as many questions as possible.  Record actions as needed to answer the questions.

*Breakout*

**Notes:**
The Breakout Plan slides build by bringing up each paragraph separately.
If the group clearly understood the instructions for the previous breakout or gets restless as you begin to go through these instructions, then go through the instructions very quickly, and skip showing the overheads.
There are several pages in this section that will be shown as overhead transparencies, instead of using computer projection.

For step 1, show the Team Roles (page 41).

For step 2, show the blank page for recording goals and objectives (page 42).

For step 3, show the list of Electronic Screening Design Decisions and the blank page for recording answers (page43-44)

## Breakout Plan120 minutes

**Step 4**. ~30 min.  On a flipchart, tailor the list of scenario steps presented in this session for electronic screening at your site.
**Step 5.** ~10 min.  Start with a copy of your system design template.  Label it “Screen vehicles at _____________ electronically using snapshots”.   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 electronic screening 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 computer’s box.  If you can, identify the communications protocol you will you use for each new connection.

*Breakout*

**Notes:**
Explain step 4

For step 5, show the Generic State Design Template (page 45)

For step 6, show the Generic Network Template (page 46)

## Breakout Plan120 minutes

**Step 7.** ~ 5 min.  Make sure you’ve noted all the open actions on your action plan and preliminary decisions on your decision table.  List the three most important screening-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 Electronic Screening (step 2)
- Preliminary design decisions for Electronic Screening (step 3)
- Electronic screening operational scenario and functional thread diagram (steps 4 and 5)
- Network diagram for electronic screening scenario (step 6)
- Actions, decisions, issues (step 7)

*Breakout*

**Notes:**
For step 7, remind them to continue building on the lists they’ve already started.  Show them the blank issues chart on page 47.

Explain step 8

## Breakout Plan120 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*

**Notes:**
Explain step 8

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

- Review the screening factors you want to use.  Review the slide labeled Snapshot Data Stored in SAFER/CVIEW.  Identify what system or component will supply each factor to the algorithm and element from the snapshot.  Also review the snapshot white paper.  Complete the Snapshot Data Sources tables from the Safety Session for carrier and vehicle snapshots by identifying which source systems will provide each type of snapshot data.
- At each site you are upgrading to handle electronic screening, where will you put readers? (Advance - Identify carrier and vehicle; Clearance - Transmit bypass/pull-in decision; Ramp or scale - Identify vehicle on ramp WIM or static scale; Compliance - Detect illegal bypass; Exit - Clear pull-in flag; Write event data)
- Complete an operational scenario and functional thread diagram for electronic screening enrollment.

*Breakout*

**Notes:**
Emphasize the need to review the snapshot white paper

## Team Roles

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

*Breakout*

## State Electronic Screening Goals & Objectives

*Breakout*

## Electronic Screening Design Decisions

- 1.	What agency has the lead for electronic screening in your state?
- 2.	Do you already belong to or will you join an existing screening program?  Which one?
- 3. What is your enrollment philosophy?  How will you share enrollment information with other programs?
- 4.	What screening factors do you use/will you use?  Will you screen using both carrier and vehicle data?
- 5.	Which site will you upgrade first to handle electronic screening?
- 6.	Will you put WIM on the mainline?  On the ramp?  Both?
- 7.	At the first site, what new equipment do you need to support electronic screening?  What upgrades of existing equipment do you need?

*Breakout*

## Electronic Screening Design Decisions

*Breakout*

## Generic State System Design Template

**Generic State Roadside Systems**

**Generic State Commercial Vehicle Administration Systems**

**Carrier Systems**

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

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

**CDLIS**

**IRP**
**Clearinghouse**

**IFTA**
**Clearinghouse**

**NMVTIS**

**MCMIS**

**SAFER**

**Compliance **
**Review **
**(e.g., CAPRI)**

**Service Providers**

**Internet Tools**
**(e.g. Browser)**

**Other Carrier**
**Systems**

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

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

**Transponder**

**Carrier Commercial**
**Vehicle**

**Web Site**

**Licensing &**
**Insurance**

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

*Breakout*

**Use Your State’s Template**

## Generic Network Template

- Motor Vehicle Administration

- State Highway Administration

- CVISN Core
- Infrastructure Systems

- Motor Fuel Tax Agency

- State Police (MCSAP Agency)

- Inspections
- (ASPEN)

- IRP

- Carrier Systems

- SAFER

- MCMIS

- IRP
- Clearinghouse

- IFTA
- Clearinghouse

- Credentialing
- System

- Carrier
- Registration &
- Permitting

- Treasury:
- Mainframe DB

- IFTA Registration
- & IFTA Tax
- Processing

- SAFETYNET

- Licensing
- & Titling

- Intrastate
- Registration

- AAMVAnet
- Frame Relay
- (TCP/IP)

- AAMVAnet
- SNA

- Gateway
- (token
- ring)

- sensors

- CDLIS

- Licensing &
- Insurance

- Web Site

- Firewalls

- Gateway

- Credentialing Interface,
- All MVA LSIs,
- E-Screening Enrollment

- CVIEW

- Dedicated dial-up

- Dial-up

- Existing
- Proposed

- dial-up

- dial-up

- TCP/IP

- Ethernet Backbone

- SNA

- Ethernet Backbone

- SNA

- Ethernet Backbone

- Firewall

- Firewall

- Internet

- Internet Tools

- RF
- Link

- Roadside
- Operations

- Sensor/
- Driver Comm

- Screening

- Repeater

- AAMVAnet
- CSN
- (TCP/IP)

- Firewall

- CAPRI

**Use Your State’s Template**

*Breakout*

## Electronic Screening Issues/Questions

*Breakout*

## Background Material:DSRC Standards

## Electronic Screening Interoperability: Background on Standards

- Electronic Screening Interoperability: Background on Standards

*Overview*

**Notes:**
DSRC is used to provide data communications between a moving vehicle and the roadside equipment to support the screening process.  
This is accomplished by means of a transponder mounted in the cab of the vehicle, and a reader and antenna mounted at the roadside.  
The tag contains identifiers specific to the vehicle.  In some cases, only the transponder ID is used.  In other cases, carrier and vehicle IDs are retrieved.  The screening computer uses the ID(s) as part of the overall screening algorithm, and then uses audio and visual indicators on the tag to communicate the screening decision back to the driver.  
Layer 1 - Physical:
Frequency
Modulation
Bandwidth
Carrier on/off ratio
Antenna polarization
Power
SNR
Bit rate 
Layer 2 - Data Link
TDMA frame definition
Slot control and allocation (to handle multiple transponders in read zone)
Link transmissions necessary to read/write data (including activation and acknowledgments)
Data packaging 
Error detection and recovery
Layer 7 - Application 
Transponder command
Transponder memory page management
Memory page definition
Message definition
Access control

## ITS Applications of DSRC

*Overview*

**Notes:**
This slide shows many of the ITS applications of DSRC, with the selected uses (the ones US DOT is focused on for CVO)  highlighted in red.  

## Background Material:Interoperability

## Interoperability: What does it mean?

- Interoperability: What does it mean?

- Technical interoperability is achieved when different types of systems or products cooperate to accomplish a shared functions (e.g., a DSRC transponder and roadside reader).
- Operational and programmatic interoperability address the use of consistent practices and approaches to ITS/CVO activities.

*Overview*

**Notes:**
EXAMPLE:
Consider a traffic light.  If I put in a light that has red, blue and green lights instead of red, yellow and green, is is technically not-interoperable.  Or if I put the red light on the bottom instead of on the top.
On the other hand, if it is a standard traffic signal, but as a policy I say that green means stop and red means go, my policies are not interoperable.  
Or if one state allows right turn on red and another one doesn’t, the policies are not interoperable.
Or if one issues traffic citations if any part of my car is in the intersection when the light changes to red and another doesn’t as long as part of my car is out of the intersection.

## Interoperability: Why should you care?

- Without technical interoperability, your state’s reader may not be able to read my transponder
- Without operational interoperability, under identical data and measurement conditions, State A may stop me, but State B may let me bypass
- Without programmatic interoperability, even though technical and operational interoperability have been achieved,  a state may not have enough information to let me bypass

*Overview*

**Notes:**
Assume you are a state and I am a motor carrier...

## Interoperability issues are being addressed by various groups

- ITS America CVO Policy Committee
- Contact Fred Daly (ITSA)
- fdaly@itsa.org or 202-484-4662
- American Association of State and Highway Transportation Officials (AASHTO) Highway Transport Subcommittee
- Contact Leo Penne (AASHTO)
- lpenne@aashto.org or 202-624-5813
- Commercial Vehicle Safety Alliance ITS Committee
- Contact Steve Keppler CVSA
- stevek@cvsa.org or 301-564-1623

*Overview*

**Notes:**
Also some suggestion for a base state working group approach.
No consensus about how to achieve interoperability...
There are potentially degrees of interoperability.  For example, for basic interoperability: 
DSRC transponders are interoperable
Programs (HELP, NorPass, ...) exchange tag Ids
But, programs use different enrollment criteria, charge differently, and use varying screening criteria
This still allows carriers to participate in all states using a single tag, even though there are some variations
This is similar to the situation in programs like IRP and IFTA where states follow one basic program but have some variations state-to-state
Note that interoperable does not necessarily mean uniform or identical

## Background Material:E-Screening Operational Scenario

## Operational Scenario:Mobile Site

**1. Vehicle approaches site where mobile unit is located.  WIM/AVC determines vehicle gross weight, number of axles, axle weight, axle spacing.   For a tagged vehicle, DSRC identifies carrier and vehicle (driver: future).  **

**LPR**
**SSWIM**

*VMS*

- Inspection Area Parking

**2.  WIM/AVC data and infrastructure data  (Carrier, Vehicle, Driver Snapshots) are processed to determine clearance status (bypass).  Data are sent to the mobile van.**

**3. DSRC sends clearance status (Bypass) to the tag.  Driver is notified.  Cleared vehicles are permitted to continue without any delay. **

- Screening System
-      WIM/AVC
-       DSRC

**Operational Scenario:****Mobile Site**

- _Acronyms_
- AVC - Automatic Vehicle Classification
- DSRC - Dedicated Short Range Communication
- WIM - Weigh In Motion
- LPR - License Plate Reader
- SSWIM - Slow Speed Weigh In Motion