CVFM Meeting Fall 2006 ENS Overview and Demonstration Mark Jensen SAIC Carlton Nettleton SAIC Dan Mu

1
CVFM Meeting Fall 2006 ENS Overview and
DemonstrationMark Jensen (SAIC) Carlton
Nettleton (SAIC) Dan Murray (ATRI)
With Support From
In Cooperation With
2
Agenda

• ENS Overview
• Mark Jensen
• Demonstration of ENS Functionalities
• Carlton Nettleton
• Motor Carrier Perspective
• Dan Murray

3
ENS Project Background

• Grew from the results of the FMCSA-sponsored
  Driver Violation Notification (DVN)
  project(Phase I)
• Analyzed drivers histories and their
  relationship to highway safety
• Identified potential gaps in driver compliance
  with Federal requirements
• Identified significant potential safety benefits
  of ENS system
• Identified potential cost savings for
  jurisdictions and industry
• Defined high-level ENS system requirements
• ENS Phase II Pilot Test sponsored by FMCSA
  based on potential safety benefits

4
ENS Phase II Pilot Test Overview

• Scope 6 Tasks
• Develop study design and performance measures
• Build and test prototype ENS
• Select Pilot States and Motor Carriers
• Develop and deploy prototype system in Pilot
  States
• Conduct Pilot Test
• Evaluate and document results of the Pilot Test
  (by Battelle)
• Sponsor FMCSA/DOT
• Task Manager Chris Flanigan (chris.flanigan_at_dot.g
  ov)
• Project Team
• SAIC (Prime), ATRI, AAMVA, CVSA, and Dr. Brenda
  Lantz (UGPTI)
• Voluntary industry data participant Explore
  Information Services
• Two Pilot States Minnesota and Colorado
• Supported by ENS Working Group
• Independent Evaluation
• Evaluation POC Jeff Jenq (jenqj_at_battelle.org)

5
Deployment Approach for ENS

• Goal Develop a prototype national system based
  on a flexible approach towards data acquisition
• ENS Technology Approach
• Straight-forward intuitive user interface /
  single portal for program registration
• Complex web-based and other information
  processing between states, 3rd Party Data
  Providers and ENS system handled behind the
  scenes
• Can support 3rd Party Data Provider and AAMVA/UNI
  open-source models
• System Build To capabilities being constantly
  assessed for future needs
• Anticipated Real-World Benefits
• Public sector safety benefits realized through
  potential reductions in crashes caused by unsafe
  commercial drivers (convictions, suspensions,
  revocations)
• Private sector motor carrier benefits realized
  through potential liability risk reductions and
  administrative savings

6
Agenda

• ENS Overview
• Mark Jensen
• Demonstration of ENS Functionalities
• Carlton Nettleton
• Motor Carrier Perspective
• Dan Murray

7
System Architecture Overview
8
ENS - Software Architecture
COTS computer components are being used to save
time and costs. Microsoft Operating System is the
selected platform which will support IIS for web
services and a SQL database data
storage. Presentation Layer Screens or graphic
user interface (GUI) required for interacting
with the ENS. Business Logic Layer Software
objects are being designed and programmed to
specifications of the ENS system including
Reports, Notifications, DMV Interfaces, and
Email. Data Access Layer The Data Access layer
contains objects to interface to the database.
9
Use Cases - 1

• Employer
• Register for an account with ENS manually.
• Enroll Driver - manual entry
• Un-enroll Driver
• Edit Driver
• Retrieve Notification
• Request printable version of driver history
  record
• Request to download driver history record
• Reports
• View latest periodic report
• View a report a user specified time frame
• Request printable version of the report
• Request to email report
• Architecturally significant Use Cases

10
Use Cases - 2

• Notifications
• DMV (or third party intermediary) Posts A
  Driver History Record To ENS
• Display list of unread notifications
• Display a driver history record
• Request a printable version of the driver history
  record
• Request to download the driver history record
• Set configurable notification settings
• Architecturally significant Use Cases

11
Software Engineering Activities

• Software Requirements Analysis define
  capability, interface, performance and security
  requirements. ?
• System Design describe the top level hardware
  and software components and how they interact. ?
• Software Architecture partition the software
  into the next level of software components and
  define how they interact. ?
• Detailed Design define the classes, methods,
  and parameters for each software component. ?
• Code and Unit Test translate the detailed
  design into code and test the code. ?
• Integration/System Testing integrate the
  components and ensure they meet the requirements.
  
• Version 1 Test install the system, test it, and
  correct problems.
• Version 2 Pilot Test install final system and
  run Pilot Test.

12
Software Engineering Process
Were Here
13
(No Transcript)
14
Agenda

• ENS Overview
• Mark Jensen
• Demonstration of ENS Functionalities
• Carlton Nettleton
• Motor Carrier Perspective
• Dan Murray

15
Carriers Why They Want ENS
16
Carrier/Driver Recruitment

• Carrier recruitment initially completed
  re-confirming
• Fleets represent TL, LTL, Specialized, Utility,
  O-O
• Carriers originally identified 500-1000 drivers
• Initial goals were 2000 4000
• Test Carriers in Place
• 80 100 drivers in MN
• 50 drivers in CO

17
Carrier Participation Issues

• Data Privacy!!
• FCRA Legal Challenges
• Driver/Data Privacy Acts
• Employer Data sharing
• Memo of Agreement
• Among Parties
• Driver Consent Forms
• New/Unique Forms Needed for ENS
• Other MOAs?
• Evaluation Issues
• Published Research

18
Industry Next Steps

• Concept is a Win-Win
• Safety Opportunities FMCSA Goals
• State and design issues are challenging
• Industry is Clamoring
• Desire Additional Data