Design Page 4a 1

1
S1 Welcome and Introduction 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 4a Discussion - CVIEW
2
Session 4a Discussion - CVIEWOutline (1 of 2)

• What is CVIEW?
• CVIEW Functions
• Who would use CVIEW?
• Why use CVIEW?
• Must every state have a CVIEW?
• What is an equivalent system?
• Cant we just put all data into SAFER?
• What are the development options for a state that
  elects to use CVIEW?

3
Session 4a Discussion - CVIEWOutline (2 of 2)

• What minimum hardware is required to run the APL
  CVIEW Version 2?
• What about additional optional components beyond
  that minimum configuration?
• What COTS products are required to run the APL
  CVIEW Version 2?
• How can states find out more about the APL CVIEW?
• APL CVIEW Version Delivery Schedule
• Can a state get a copy of the APL CVIEW?
• Is a CVIEW consortium feasible? What model might
  work?

4
What is CVIEW?

• A state-based software system providing
  standardized safety and credentials data exchange
  and storage
• The states single point of access with SAFER
• Terminology
• CVIEW is a generic term.
• The APL CVIEW is derived from SAFER and is
  available free-of-charge to states.
• Several states and vendors are developing their
  own brands of CVIEW.

5
The State CVIEW handles the exchange of safety
and credentials information within the state, and
with other jurisdictions via SAFER
State Credentials Taxes Administration
SAFER
1
2
3
4
4
3
2
Commercial Vehicle Information Exchange Window
(CVIEW)
1
2
3
4
4
3
2
1
State Safety Administration
State Roadside CV Check
6
CVIEW Functions (1 of 2)

• Provide for the electronic exchange of
• interstate carrier and vehicle safety and
  credential data between state source systems,
  users, and SAFER
• intrastate carrier and vehicle safety and
  credential data between state source systems and
  users
• Serve as the repository for a state-selected
  subset of
• interstate carrier and vehicle safety and
  credential data
• intrastate carrier and vehicle safety and
  credential data
• Support safety inspection data reporting
  retrieval by roadside enforcement personnel

7
CVIEW Functions (2 of 2)

• Provide inter- and intrastate carrier and vehicle
  safety and credential data to the roadside to
  support electronic screening and other roadside
  operations
• Perform electronic exchange using
• Electronic Data Interchange (EDI) standards
• Non-EDI standards, the selection of which is
  system-dependent
• New open standard methods of information exchange
  (e.g., XML) as they become available and are
  requested by users
• May allow the general public to access data
  without the security risk of providing a direct
  connection to sensitive legacy systems , if the
  state so elects

8
Who would use CVIEW?

• A single state electing to use CVIEW as a data
  exchange method
• A consortium of states electing to use a single
  CVIEW as a data exchange method

9
Why use CVIEW?

• Facilitates access to intrastate carrier and
  vehicle information
• Gives the state better control of its intrastate
  data with respect to privacy issues
• Allows states greater control and increased
  flexibility regarding the interfaces with state
  legacy systems
• Improved performance for access to state-stored
  snapshots and reports
• Allows a state to more easily include state
  specific fields and functions

10
Must every state have a CVIEW?

• The CVISN architecture calls for every state to
  have a CVIEW or an equivalent system or set of
  systems to perform CVIEW functions (as listed on
  pages 6, 7).

11
What is an equivalent system?

• The simple answer is, a system (or systems) that
  performs the CVIEW functions can be considered a
  CVIEW equivalent.
• Several options come to mind
• Using an integrated CVO database where snapshots
  are a subset of the data (Indiana approach)
• Using a merged CI CVIEW (not just collocated on
  the same machine, but actually merged)
• Several states using a common CVIEW

12
Cant we just put all data into SAFER?

• Maybe . . .
• Support for intrastate data is contingent on
  assigning USDOT numbers
• Safety ratings for intrastate operators are not
  planned before 2002
• Commitment to support credential data is
  uncertain
• Support for state-specific fields (e.g., vehicle
  emissions data) is uncertain

13
What are the development options for a state that
elects to use CVIEW?

• Use the APL CVIEW as-is with no modifications
  (using the existing EDI interfaces)
• Start with the APL CVIEW as a baseline
• Start with the Cambridge Systematics Incorporated
  version as a baseline
• Conduct an open procurement
• Build it in-house from scratch

14
What minimum hardware is required to run the APL
CVIEW Version 2?

• Compaq ProLiant 6000 - Pentium III XeonTM Model
  6/500-2S (1024K Cache) includes
• two Pentium III XeonTM 500MHz with integrated
  1024-KB level two cache
• over one Gigabyte of ECC EDO memory
• five 18.2-GB Pluggable Wide-Ultra SCSI-3 10K
  Drives
• the approximate cost for the hardware for one
  total server system is 22K
• Note This model is being transitioned to the
  Compaq ProLiant ML570 model in 2000.

15
What about additional optional components, beyond
that minimum configuration?

• To improve the performance of your APL CVIEW
  System, JHU/APL recommends that you consider
  using two servers.
• Note The Volpe SAFER System uses five servers.
• To further improve performance (reliability,
  capacity for more users, external communications
  options, enhanced operations and maintenance
  support) we recommend that you also consider the
  additional optional components, as defined in an
  Excel spreadsheet located on the JHU/APL CVISN
  Web site. The cost of these additional optional
  components is approximately 20K.
• Note The additional optional components include
  processor, power supply, drive cage, modems,
  internal DLT drive, external DAT 8 cassette
  autoloader, UPS, printer, fast Ethernet switch.

16
What COTS products are required to run the APL
CVIEW Version 2? (1 of 2)

• Operating System
• Microsoft Windows NT Server 4.0 Service Pack 6a
  with the necessary number of Client Access
  Licenses (CALs)
• Database
• Oracle7 Workgroup Server for Windows NT Version
  7.3.3.4.0
• EDI Translator
• Mercator Execution Engine API for Windows NT
  Server (Intel) Version 1.4.2

17
What COTS products are required to run the APL
CVIEW Version 2? (2 of 2)

• SMTP/POP3 Mail Server
• Microsoft Exchange Server Standard Edition 5.5
  Service Pack 2
• SMTP/POP3 Application Programming Interface (API)
• Distinct Visual Internet Toolkit Run-Time Version
  3.0
• The approximate cost for the software for one
  server system is 27K

18
How can states find out more about the APL CVIEW?

• You can go to the JHU/APL CVISN Program Web Site,
  located at
• http//www.jhuapl.edu/cvisn/
• Scroll down to Browse and Download Documentation
  area click on CVIEW
• You can contact James H. Polaha (CVIEW Project
  Manager) at
• James.Polaha_at_jhuapl.edu
• [phone]

19
APL CVIEW Version Delivery Schedule
20
Can a state get a copy of the APL CVIEW?

• Yes, any state or agency/company representing a
  state may request a copy of the APL CVIEW code
  (both source and executable).
• Please direct all inquires and requests to
• James H. Polaha at JHU/APL
• [phone]
• James.Polaha_at_jhuapl.edu

21
Is a CVIEW consortium feasible? What model
might work ?

• A group of states might take any of several
  approaches to a common CVIEW
• Develop a common set of requirements and build
  one CVIEW that all member states put data into
  and get data from (like the IFTA Regional
  Processing Center).
• Develop a common set of requirements and build a
  CVIEW that all member states replicate and
  operate for themselves.
• One state goes first, and develops a CVIEW that
  all member states agree will meet most of their
  needs. The development state provides the source
  code to all member states to tailor or use as
  they wish.
• No doubt there are other options, too!