Scope Page 3 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 3 System Design Guidelines/ Pre-Work
Review
2
Session Plan

• CVISN Architecture overview (10 min)
• Key concepts information exchange, standard IDs,
  Web, EDI, DSRC (15 min)
• How to steps (20 min)
• Breakout Plan (15 min)
• Breakout (90 min)
• Review and, if necessary, complete Pre-Work
• Start Action Plan, Decision Table, State System
  Change Summary
• LUNCH
• State presentations questions (30 min)
• Total Time 170 min (2 hrs, 50 min) 55 min
  lunch break

3
Session Objectives

• Understand the cornerstone CVISN operational
  concepts and architectural guidelines
• Snapshots for routine data exchanges
• Standard identifiers
• Use Web standards for person-to-computer
  exchanges
• Use EDI standards for computer-to-computer
  exchanges
• Use DSRC standards for vehicle-to-roadside
  exchanges
• Outline the steps for completing your states
  CVISN system design
• Establish the framework for completing your
  states CVISN system design

4
The CVISN architecture and model system design
provide a technical framework for all
stakeholders to develop interoperable systems.
This view of the CVISN System Design groups
systems according to major stakeholder groups,
functions, and operators. It illustrates how many
subsystems owned by different stakeholders can be
viewed as parts of one large system, i.e., CVISN.
Each subsystem must be designed with a view
toward how it fits into the whole system if
interoperability is to be attained. This view of
the CVISN System Design shows individual systems
in the stakeholder categories. The actual system
names for each stakeholder will differ, but
functions are fairly common with the names shown
here.
Support CVISN Level 1 functions
CVISN Architecture overview
5
The CVISN Architecture Flow Diagram and related
data dictionary were used as the foundation for
developing interface standards.
payment request
transaction status
Financial Institution
credentials status information, credentials
information, credential fee
coordination, safety inspection report, safety
status information, INTERNATIONAL BORDER
CROSSING DATA
credential application, tax filing, audit data,
INTERNATIONAL BORDER CROSSING DATA
credentials information, credentials status
information, safety status information, citation,
accident report, INTERNATIONAL BORDER CROSSING
DATA, compliance review report, safety
inspection report
safety status information, credentials status
information, credentials information
Financial Institution
CVO Information Requestor
payment request
INTERNATIONAL BORDER CROSSING DATA, daily
site activity data, citation, accident
report, safety inspection report, violation
notification, CUSTOMS IMMIGR INFO REQUEST
information on violators
citation, accident report, violation
notification
transaction status
route plan, traffic advisories, toll data
archive requests, archive status
Information Service Provider Subsystem
vehicle probe data
commercial vehicle archive data
route request, toll data request
Enforcement Agency
toll data request
Archived Data Management Subsystem
toll data
INTERNATIONAL BORDER CROSSING DATA, safety
status information, credentials information,
credentials status information, safety
inspection report, CUSTOMS IMMIGR INFO
RESPONSE
information on violators
toll data
Toll Administration Subsystem
toll data request
transaction status
Financial Institution
commercial vehicle measures
payment request
identification information, CVO weight and
presence
driver to fleet request
COMMERCIAL VEHICLE SUBSYSTEM AGGREGATED WITH THE
VEHICLE SUBSYSTEM
fleet to driver update
on-board safety request trip log
request, on-board vehicle request
screening event record, electronic screening
request, safety inspection record, CV BORDER
CLEARANCE MESSAGE SET, LOCK MESSAGE
SET, pass/pull-in, on-board safety
request, driver log request, safety inspection
request
VEHICLE SUBSYSTEM
On-board CV Electronic Data
Vehicle Toll/Parking Interface
on-board vehicle data, trip log, on-board safety
data
On-board Trip Monitoring
intermod CVO coord
position fix
Vehicle Mayday Interface
Location Data Source
On-board Cargo Monitoring
screening event record, LOCK MESSAGE
SET, on-board safety data, driver log, safety
inspection record, CV BORDER CLEARANCE
MESSAGE SET
intermod CVO coord
Vehicle Probe Support
On-board CV Safety
tag data
Toll Collection Subsystem
request tag data, tag update
Intermodal Freight Depot
emergency notification, hazmat spill
notification
request tag data, vehicle signage
data vehicle probe data
CVO driver initialization
payment
request tag data, tag update
request for payment
Intermodal Freight Shipper
CVO pass/pull-in message
emergency acknowledge, emergency data request
alerts, trip log information, CVO pass/pull-
in message
hazmat information
Traveler Card
Emergency Management Subsystem
tag data
Roadway Subsystem
hazmat information request
National Std Files (EDI, flat file, XML,
etc.) National Std Vehicle Roadside
(DSRC) Other Transaction
Driver
Financial Institution
payment request
Parking Management Subsystem
transaction status
Note Capitalized flow names indicate old flows
that have not yet been aligned.
CVISN Architecture overview
6
CVISN Level 1 Deployment Summary

• CVISN is the collection of information systems
  and communications networks that provide support
  to commercial vehicle operations (CVO).
• The definition of CVISN Level 1 has been
  baselined to allow definition of a specific set
  of initial capabilities that can be deployed by a
  state and its motor carriers. In the future,
  additional capabilities may be added to CVISN.
• Interface standards either exist or are being
  developed to support CVISN Level 1 capabilities.

CVISN Architecture overview
7
A reminder - CVISN Level 1

• An organizational framework for cooperative
  system development has been established among
  state agencies and motor carriers.
• A State CVISN System Design has been established
  that conforms to the CVISN Architecture can
  evolve to include new technology capabilities.
• All the elements of 3 capability areas (below)
  have been implemented using applicable
  architectural guidelines, operational concepts,
  standards
• Safety Information Exchange
• ASPEN (or equivalent) at all major inspection
  sites
• Connection to SAFER to provide exchange of
  interstate carrier and vehicle snapshots among
  states
• Implementation of CVIEW (or equivalent) system
  for exchange of intrastate snapshots within state
  and connection to SAFER for exchange of
  interstate snapshots
• Credentials Administration
• Automated processing (i.e., carrier application,
  state application processing, credential
  issuance, fuel tax filing) of at least IRP IFTA
  credentials ready to extend to other credentials
  (intrastate, titling, OS/OW, carrier
  registration, HazMat). Note Processing does not
  necessarily include e-payment.
• Connection to IRP IFTA Clearinghouses
• At least 10 of the transaction volume handled
  electronically ready to bring on more carriers
  as carriers sign up ready to extend to branch
  offices where applicable
• Electronic Screening
• Implemented at a minimum of one fixed or mobile
  inspection site
• Ready to replicate at other sites

CVISN Architecture overview
8
Cornerstone concepts in CVISN lay the groundwork
for information exchanges (page 1 of 2)

• Exchange snapshots of carrier and vehicle
  safety and credentials information to improve CV
  safety and processes. Using standard snapshots
  simplifies the definition of new interfaces.
• Use primary identifiers in information exchanges
  for carriers, vehicles, transponders, drivers,
  international trips, shipments so that
  different agencies/systems within the same state
  can find the records they need to share (and
  likewise across state boundaries).

Key concepts
9
Cornerstone concepts in CVISN lay the groundwork
for information exchanges (page 2 of 2)

• Use World Wide Web (WWW or Web) standards for
  person-to-computer interchanges so that private
  businesses can use any commercial browser to
  interact with a public agency Web site.
• Use standard electronic data interchange (EDI)
  transactions for computer-to-computer
  interchanges so that public agency systems and
  private businesses can exchange information using
  open standards, and so that the information can
  be processed by the computers. XML may prove to
  be a viable alternative for some EDI
  transactions.
• Use Dedicated Short Range Communications (DSRC)
  standard transponders, readers, and message sets
  so that a vehicle can take advantage of ITS
  services without changing equipment when
  traveling across many states.

Key concepts
10
To support all three capability areas, snapshots
are assembled stored by SAFER and CVIEW to
facilitate the exchange of safety credentials
information among systems.

• There are 3 kinds of snapshots carrier
  (available now), vehicle (available now), and
  driver (not yet available, but proposed for the
  future).
• The use of common identifiers allows agencies and
  jurisdictions to exchange information
• Identifiers, census/demographic information,
  safety history summary, and credentials
  information are included in snapshots
• Limited DMV data are included in the snapshots
• Vehicle apportionment data
• Credentials check flags are included. A check
  flag is used to indicate a recent problem, but
  does not attempt to define current status.
• More on snapshots in Session 5. . .

Key concepts
11
Primary Identifiers used for CVISN Level 1make
it possible to exchange information.
Major CVO Information Users
Sample questions that motivate standard IDs
Major Entities
Carrier MCI 12345 A001 (Note MCI is the code for
ID Type USDOT )
Inspector
What is this carriers safety record?
CV Administrative Offices
Vehicle 1FDKE30F8SHB33184 US CA 12345664830M
Is this vehicle registered in my jurisdiction?
Is this transponder enrolled in my electronic
screening program?
Electronic Screening Site
Transponder 0 123456789
Enforcement Officer
Driver US MD AB9999-999-9999A
Is this drivers license valid?
Key concepts
12
Primary Identifiers used for other functionsmake
it possible to exchange information.
Major CVO Information Users
Sample questions that motivate standard IDs
Major Entities
Emergency Response
Tell me what is in this shipment that has been
involved in an accident.
Shipment 776655443322
Border Crossing Station
Has Customs/Immigration cleared this trip?
Trip/Load 123456789 761231
Key concepts
13
The CVISN architecture connects subsystems via a
combination of WWW, EDI and DSRC interface
standards
Computer-computer (C-C) standard interface (EDI,
XML) Person-computer (P-C) standard interface
(HTML, XML) DSRC standard interface
KEY
CV ADMINISTRATION CENTER SUBSYSTEM
EMERGENCY MGT
P-C
C-C
P-C
C-C
EMERGENCY MGT
C-C
CVO Info Requester
Intermodal Freight Shipper
P-C
PARKING MGT

C-C
ROADWAY
TOLL COLLECTION
C-C
P-C
Intermodal Freight Depot
COMMERCIAL VEHICLE CHECK ROADSIDE SUBSYSTEM
P-C
DSRC
DSRC
C-C
COMMERCIAL VEHICLE SUBSYSTEM Aggregated with the
VEHICLE SUBSYSTEM
DSRC
DSRC
Key concepts
14
Standard EDI transaction sets support
computer-to-computer exchange without the need to
negotiate unique interface agreements.
Key concepts
15
DSRC standards define how commercial vehicles and
roadside readers should communicate.

• IEEE 1455-1999, ...a standard for exchanging
  vehicle/roadside information, providing for
  bi-directional wireless message transmission and
  device control compatible with but independent of
  the ASTM efforts.
• ASTM ver 7
• ASTM PS 105-99, Standard Specification for DSRC -
  Data Link Layer, ...Specification for the
  protocol (data link) communications. Supports
  both synchronous and asynchronous modes for
  operations.
• ASTM PS 111-98, Standard Specification for
  Dedicated Short Range Communications (DSRC)
  -Physical Layer, ...Specification for the RF
  characteristics (physical layer) for DSRC
  operating in the range of 902-928 MHz. Supports
  both active and backscatter transponders.
• ASTM ver 6
• ASTM Standard for Dedicated, Short Range, Two-Way
  Vehicle to Roadside Communications Equipment,
  Draft 6, 23 February 1996.

These make up the Active Sandwich Protocol.
More on this in Session 8.
Key concepts
16
States are encouraged to implement CVISN Level 1
capabilities incrementally in a series of steps
using a structured process.
Scope Workshop
Planning Workshop
How To steps
17
The CVISN implementation process as presented in
the workshops

• The first phase (1A, 1B, 1C) is devoted to system
  design and program project planning. The first
  2 workshops are related to this phase.
• Each subsequent phase focuses on delivering a
  coordinated set of product versions (a.k.a.
  releases) that incrementally build to the overall
  CVISN Level 1 capability.
• For each phase, states are encouraged to update
  the Program Plan, State CVISN System Design, and
  System Integration Schedule.

How To steps
18
Each state develops a top-level design by adding
CVISN capabilities to existing systems(Phase 1A)
The CVISN Guide to Top-Level Design describes
this process in detail.
Characterize Current System Design
1
Identify New Operational Concepts
2
Top-Level Design
Make Master Design Network Templates
3
Feedback Iteration
Define Several Key Scenarios
4
Summarize System Interfaces
5
Summarize System Changes
6

How To steps

19
Steps in the Top-Level Design Process

• 1. Characterize your current system design.
  (Pre-Work B C D E)
• 2. Identify where your current and planned
  operational concepts and design are and are not
  compatible with CVISN. (Pre-Work A, COACH Part
  1 F)
• 3. Make a proposed master state system design
  template. Include all the systems in your state
  that support CVO. Start by reviewing the generic
  template and tailoring it to your state.
  (Pre-Work G)
• Make a proposed master network design template.
  Include all the computers and networks that
  support the systems on your system design
  template. Start with the state system design
  template, and review the generic network
  template, tailoring them to your state.
  (Pre-Work H)

How To steps
20
Steps in the Top-Level Design Process

• Think about the key operational scenarios you
  want to affect during the CVISN program.
• See Chapter 5 in the CVISN Guide to Top-Level
  Design, for a list of Level 1 scenarios.
  Identify threads of activity corresponding to
  those operations.
• Use the COACH (CVISN Architecture and Operational
  Compatibility Handbook) checklists as reminders
  of what your state intends to do.
• Use a copy of your states CVISN system design
  template to illustrate what systems will interact
  to support the operational scenario. We call
  this drawing a functional thread diagram.
  (Workshop sessions 5, 6, 8).

• Do this by drawing lines between boxes to show
  how your states systems, the carriers systems,
  and the CVISN core infrastructure will interact
  to support the operational scenario.
• Label the lines with the steps in the operational
  scenario.
• Use arrowheads to indicate flow direction.

How To steps
21
Steps in the Top-Level Design ProcessExample of
Functional Thread Diagram to Depict Operational
Scenario

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
How To steps
22
Steps in the Top-Level Design Process

• 5a. Summarize system interactions using three
  copies of your state system design template,
• one for Carrier-Related Interfaces,
• another for Interfaces within the State,
• and a third State Interfaces with CVISN Core
  Infrastructure.
• On each of these system design interface summary
  drawings, indicate whether legacy system
  interfaces (LSIs) or legacy modifications (LMs)
  will be required for the functions being
  supported.
• 5b. Reflect the operational scenarios on your
  network template. Show which computers will
  connect, and what networks and protocols will
  support those connections. (Workshop Sessions 5,
  6, 8, 10)

How To steps
23
Steps in the Top-Level Design Process

• 6. Identify the scope of the system
  changes/additions needed to become (more)
  compatible with CVISN to support the operational
  scenario.
• Consider issues such as connectivity,
  interfaces, system capacity, data compatibility,
  process/policy changes, institutional barriers,
  etc. (Workshop Sessions 5, 6, 8, 10)

How To steps
24
Breakout Goals

• Establish the framework for assessing the scope
  of the CVISN Program in your state
• Start the lists youll keep building throughout
  the workshop
• Review/Create the Proposed CVISN System Design
  template and Network Template for your state.
  These will also be used throughout the workshop.

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

• Inputs
• All Pre-Work
• Blank tables
• Sample templates
• Outputs
• Action Plan
• Decision Table
• State System Change Summary
• State Proposed CVISN System Design template
• State Proposed Network Template

Breakout
26
Breakout Plan90 minutes

• Step 1. 5 min. Assign roles and make sure that
  all decisions, actions, and system change
  highlights will be recorded in your Action Plan,
  Decision Table, and State System Change Summary.
  Decide who will maintain the master State CVISN
  System Design template throughout the workshop.
  Decide who will update the Network template to
  show the emerging Top-Level Physical System
  Design throughout the workshop.
• Step 2. Review/complete the Pre-Work. Dont let
  indecision slow you down too much.
• A. 5 min. Review Pre-Work Status Summary.
  Verify that everyone has all Pre-Work. Deal with
  any outstanding questions or issues.
• B. 20 min. Review the COACH checklists,
  highlighting where the state is not committed to
  CVISN Level 1 items. Summarize your goals and
  objectives, comparing them to the CVISN Level 1
  high-level description on page 3-7.

Breakout
27
Breakout Plan 90 minutes

• Step 2. Review/complete the Pre-Work.
  (continued)
• C. 30 min. Review the Current Systems State
  System Design template and Network template.
  Review the Proposed CVISN System templates. If
  you know you need to add a system, add it. If
  you know you need to change one, include a
  legacy modification (LM) box. If you think you
  need to build a new interface to connect with a
  legacy system, include a legacy system
  interface (LSI) box. If you arent sure, record
  an action. If you make decisions about what to
  change/not change, record a decision.
• D. 15 min. Review the Keys/Identifiers Used in
  Your Databases against the recommended standard
  identifiers (please see pages 3-49 through 3-51
  for details). Note any potential problems.
• Step 3. 5 min. Update the State System Change
  Summary by entering every state system you wound
  up with on the Proposed State CVISN System Design
  template.

Breakout
28
Breakout Plan 90 minutes

• Step 4. 10 min. Make copies (at least 5 of
  each transparencies, pages in a file, or
  hardcopies, whichever you think you will use) of
  your templates for use in later sessions. Record
  issues or questions about CVISN Level 1, the
  workshop process, or the templates for discussion
  in the main session. Get ready to present your
  results to the main group. A sample presentation
  outline is shown on page 3-47 (and in the
  template file for this session, given to the
  Facilitator on Day 0). Plan on 10 minutes to
  report.
• 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
29
Team Roles

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

Breakout
30
Action Plan WorksheetState _________________,
Page __ of __
Breakout
31
Action Plan WorksheetState _________________,
Page __ of __
Breakout
32
Key to Action Plan Tables Columns(tailor to
suit you, if needed)

• No. sequential number to keep track of actions
• Type interface issue (I), operating procedure
  issue (OP), policy issue (PO), system
  capacity/design issue (S)
• System name of the system in your state that
  the question is related to
• Question/Status statement of the issue or
  question to be addressed may turn into the
  answer when the issue is closed
• Due specific date, or schedule milestone
• Assigned to who (specific persons name, if
  possible) the action is assigned to

Breakout
33
Decision TableState _________________, Page __
of __
Breakout
34
Decision TableState _________________, Page __
of __
Breakout
35
State System Change SummaryState
_________________, Page __ of __
Breakout
36
State System Change SummaryState
_________________, Page __ of __
Breakout
37
State System Change SummaryState
_________________, Page __ of __
Breakout
38
State System Change SummaryState
_________________, Page __ of __
Breakout
39
Issues/Questions about CVISN Level 1, the
workshop process, the templates, . . .
Breakout
40
Pre-Work Status Summary (partial)
Breakout
41
State CVISN Goals and Objectives
Breakout
42
State CVISN Goals and Objectives (Continued)
Breakout
43
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
44
State System Design Template - Instructions

• The state system design template will be used to
  illustrate operational scenarios. This diagram
  is the one that the CVISN Model Deployment states
  found most useful for team communications.
  Everyone can see his or her own functional area
  on this diagram. The template can be used in
  many different ways, as you learned in the
  Understanding ITS/CVO Technology Applications
  course. In the Scope workshop, youll use this
  template for illustrating both operational
  scenarios and system interfaces. Make one diagram
  for your Current State System Design, and another
  for your Proposed State System Design.
• Include all the major functions in your state
  that support CVO. There should be exactly one
  box representing each major function. Start by
  reviewing the generic template, then tailor it to
  your state. Recall your program objectives, and
  the answers you gave when completing the COACH
  Part 1 tables. Remove functions that dont
  relate to your CVISN program. Add a box for each
  major function that is missing.
• The generic state system design template reflects
  the generic CVISN state design. The CVISN System
  Design Description explains more about the
  generic design. The small LSI and LM boxes on
  the generic state system design template refer to
  Legacy System Interfaces and Legacy
  Modifications. The state chooses whether to
  modify the legacy system (LM - legacy
  modification) to support EDI (and other new
  functions and interfaces), or to create a Legacy
  System Interface (LSI) to deal with the
  EDI-to-native form interface. Many CVISN Model
  Deployment states are implementing a mix of LSIs
  and LMs.
• In this template, it is not important to group
  the functions that are handled within the same
  computer, nor to show how systems are connected
  through networks

Breakout
45
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
46
Network Template - Instructions

• The network template shows how your state
  allocates the major functions to computers, and
  how those computers are connected using various
  kinds of network technologies. Make one diagram
  for your Current Network configuration, and
  another for your Proposed Network configuration.
• To make your master network template, review the
  generic network template. Tailor the generic
  network template to your state. Start by
  including all the computers and networks that
  support the systems you included in your current
  systems inventory. Next, be sure that the
  existing major functions on your system design
  template are allocated to some computer on the
  network and design template. As necessary, add
  computers and network components. If you dont
  know what kind of computer or what networking
  technology youll use, put in a placeholder. The
  drawing will mature as you work through the
  design process.
• This template is used to show network
  connections, as well as the allocation of
  software products to computers. Proposed new
  computers and network connections can be added.
  As you make decisions, show which network
  protocols youve selected for each segment. The
  diagram can be used to verify how two or more
  systems are connected physically, and where
  network translations are needed. It can also
  show where potential bottlenecks exist.
• On the network template, each small box
  represents a computer system. The state should
  show all the computer systems that support (or
  will support) the CVISN program functions. List
  the major functions (software applications)
  handled by that computer inside the box. Group
  the small boxes into large boxes according to the
  state agency or facility that is responsible for
  the computers. Show LANs and WANs as lines
  connecting the computers.
• We recommend that you adopt some convention for
  distinguishing between existing and proposed
  computers and connections. For instance, you
  might make existing computers white, and new ones
  shaded. You might show existing connections as
  solid lines and new ones as dashed. Different
  dashed line types can be used to indicate
  different network protocols, if you like.
• Every function box on your state system design
  template should be allocated to some computer on
  this template. This includes each of the
  individual LSI boxes. Often for
  credentials-related products, the LSIs are small
  applications running on the same computer as the
  Credentialing Interface. LMs are modifications
  to existing systems, and usually are not shown as
  separately allocated functions on the network
  template.

Breakout
47
Sample Presentation

• Characterize current state design
• Current State System Design Template
• Current State Network Template
• Brief verbal description
• Summarize CVISN program goals
• Preliminary proposed state design
• Proposed State System Design Template
• Proposed State Network Template
• Brief verbal description
• If you have recorded actions, decisions, and
  information about system changes, then present
  the initial Action Plan, Decision Table, State
  System Change Summary
• Issues or questions

Breakout
48
Background Material
49
Standard identifiers are intended to facilitate
the process of exchanging information about
carriers, vehicles, drivers, shipments, and
international trips.
Support CVISN Level 1 functions
Key concepts
50
Standard identifiers are intended to facilitate
the process of exchanging information about
carriers, vehicles, drivers, shipments, and
international trips.
Support CVISN Level 1 functions
Key concepts
51
Standard identifiers are intended to facilitate
the process of exchanging information about
carriers, vehicles, drivers, shipments, and
international trips.
Support CVISN Level 1 functions
Key concepts
52
This Page Intentionally Blank