New Jersey Statewide and Regional ITS Architectures
Menu
Region Home
Stakeholders
Inventory by Stakeholder
Inventory by Entity
Sausage Diagram
Market Packages by Functional Area
Market Packages by Stakeholder
Market Package Descriptions
Equipment Package Descriptions
Architecture Flow Descriptions
Project Documents
Send Your Comments

 

Equipment Package: On-board Driver Authentication

Description: This equipment package monitors the identity of the commercial vehicle driver and compares it with the planned drivers for the commercial vehicle. Any change in driver is sent to the Fleet and Freight Management Subsystem. Notification of any unexpected drivers will also be send to the Fleet and Freight Management Subsystem which, in turn may send a disable vehicle command back to this equipment package to cause the vehicle to stop. On receipt of a disable vehicle message from the Fleet and Freight Management Subsystem or on detection of an unauthorized driver, the equipment package will safety disable the CV.
Included In: Private Commercial and Fleet Vehicles
Processes: 2.4.3 - Analyze Commercial Vehicle On-board Data
2.4.4 - Provide Commercial Vehicle Driver Interface
2.4.7 - Manage CV On-board Data
2.4.9 - Authenticate Commercial Vehicle Driver
User Service Requirements: 4.0 - COMMERCIAL VEHICLE OPERATIONS
4.1 - COMMERCIAL VEHICLE ELECTRONIC CLEARANCE
4.1.1 - CVEC shall include a Fixed Facility consisting of those structures and equipment to include Ports Of Entry, Inspection Stations, Weigh Stations and Toll Booths.
4.1.1.6 - When making the "Pass/Need To Stop" determination the Fixed Facility shall perform checks on the following:
4.1.1.6(a) - Vehicle/Carrier Safety Information.
4.1.1.6(b) - Vehicle Credentials.
4.1.1.6(c) - Driver Credentials/Status.
4.1.1.6(d) - Vehicle Weight Information.
4.1.1.6(e) - Tax Payment Account.
4.1.2 - CVEC shall include a Vehicle System capability
4.1.2.1 - Vehicle System shall provide the capability to accommodate both interstate and intrastate carriers.
4.1.2.3 - Vehicle System shall provide the capability for each individual vehicle's or carrier's participation in the process to be on a voluntary basis.
4.2 - AUTOMATED ROADSIDE SAFETY INSPECTION
4.2.2 - The ARSI capability shall include a Vehicle System (VS) function.
4.2.2.1 - VS shall provide a processing capability that automates the roadside inspection tasks.
4.2.2.2 - The VS architecture shall provide the capability to be developed and integrated as a phased implementation.
4.2.2.3 - The VS shall include sensors to efficiently check vehicle systems and driver condition.
4.2.2.4 - The VS shall include the capability for continuous updates to vehicle safety records or an "electronic decal/record" on the vehicle.
4.2.2.5 - The VS shall include an on-board safety status monitoring system that is accessible from the roadside.
4.2.2.6 - The VS shall provide an initial automated inspection capability that will expedite and supplement the existing visual and manual inspection processes.
4.3 - ON-BOARD SAFETY AND SECURITY MONITORING
4.3.1 - OBSSM shall include a Fixed Facility (FF) capability for the analysis and control of safety information.
4.3.1.2 - The FF shall provide the capability to provide warnings of any safety problem that has been identified.
4.3.2 - OBSSM shall include a Vehicle System (VS) that is a part of each vehicle.
4.3.2.1 - The VS shall provide the capability to collect and process information to supply those roadside facilities being encountered at mainline speeds with each vehicle's safety status to include the following:
4.3.2.1(a) - Vehicle safety status.
4.3.2.1(b) - Cargo safety status.
4.3.2.1(c) - Driver safety status.
4.3.2.1(d) - Vehicle Identification.
4.3.2.1(e) - Driver Identification.
4.3.2.2 - The VS shall provide the capability to alert the vehicle driver whenever there is a critical safety problem or potential emergency.
4.3.2.4 - The VS shall include a Vehicle Integrity (VI) function.
4.3.2.4.1 - The VI shall monitor on-board sensors to detect a breach or tamper event.
4.3.2.4.2 - The VI shall provide the capability to collect and process vehicle integrity information.
4.3.2.4.3 - The VI shall provide integrity event information to the driver and carrier's dispatch function.
4.3.3 - OBSSM shall include a Freight Security Management (FSM) function
4.3.3.2 - FSM shall include a commercial vehicle driver/commercial vehicle/freight container or trailer Assignment Integrity (AI) function.
4.3.3.2.3 - AI shall include the capability to monitor the identity of the driver.
4.3.3.2.4 - AI shall include the capability to monitor the identity of the commercial vehicle.
4.3.3.2.5 - AI shall include the capability to monitor the identity of the freight container or trailer.
4.4 - COMMERCIAL VEHICLE ADMINISTRATIVE PROCESSES
4.4.1 - CVAP shall include an Electronic Purchase Of Credentials (EPC) function with capabilities that include but are not limited to the following:
4.4.2 - CVAP shall include an Automated Mileage and Fuel Reporting and Auditing (AMFRA) function that includes but is not limited to the following:
4.4.3 - CVAP shall include an International Border Electronic Clearance (IBEC) function.
4.4.3.1 - IBEC provides the capability to electronically clear vehicles crossing international borders with those countries adjacent to the United States. IBEC shall provide the capability to clear the following:
4.4.3.1(a) - Driver Clearance.
4.4.3.1(b) - Cargo Clearance.
4.4.3.1(c) - Vehicle.
4.4.3.2 - IBEC shall have an Electronic Records function that enables certification of border crossing shipment with the verification capabilities to include but not be limited to the following:
4.4.3.2(a) - Verify driver identity.
4.4.3.2(b) - Verify shipper.
4.4.3.2(c) - Verify Nature of cargo.
4.4.3.2(d) - Verify Carrier safety.
4.4.3.2(e) - Verify credential records.
4.4.3.2(f) - Verify Duties Paid.
4.4.3.2(g) - Verify Vehicle Identity.
4.4.3.2(h) - Verify Vehicle Weight.
4.5 - HAZARDOUS MATERIAL SECURITY AND INCIDENT RESPONSE
4.5.0 - ITS shall include a Hazardous Materials (HAZMAT) Security and Incident Response (HSIR) service.
4.5.1 - HSIR shall include a HAZMAT Incident Notification (HIN) function.
4.5.1.1 - HIN shall include the capability to provide enforcement and HAZMAT response teams with timely and accurate information on cargo contents when the vehicle is involved in an incident.
4.5.1.2 - HIN shall be capable of providing the following Information :
4.5.1.2(a) - Time of incident.
4.5.1.2(b) - Location of the incident.
4.5.1.2(c) - The material(s) involved.
4.5.4 - HSIR shall include a HAZMAT Security (HS) function.
4.5.4.3 - HS shall include a Driver Authentication function (DA)
4.5.4.3.1 - DA shall include the capability to store the identities of authorized drivers for a specific trip or set of trips or class of trips.
4.5.4.3.2 - DA shall include the capability to determine the identity of a driver.
4.5.4.3.3 - DA shall include the capability to notify the vehicles dispatch function if an unauthorized driver attempts to operate the vehicle.
4.5.4.3.4 - DA shall include the capability to safely disable a vehicle if an unauthorized driver attempts to operate the vehicle.
4.5.4.3.5 - DA shall include the capability to allow a vehicles dispatch function to safely disable the vehicle.
4.5.4.3.6 - DA shall include the capability to notify public safety if an unauthorized driver attempts to operate the vehicle.
4.5.4.3.7 - DA shall include the capability to notify traffic management if an unauthorized driver attempts to operate the vehicle.
4.6 - FREIGHT MOBILITY
4.6.1 - FM shall include a Commercial Vehicle Fleet Management (CVFM) function.
4.6.1.1 - CVFM shall include the capability for users to provide commercial drivers and dispatchers with real-time routing information in response to congestion or incidents.

Last updated: 02-08-05