CVSA to host EOBR listening session

At the request of the Federal Motor Carrier Safety Administration, the Commercial Vehicle Safety Alliance (CVSA) has agreed to host an electronic onboard recorder (EOBR) listening session at the CVSA Workshop in Bellevue, WA, on Thursday, April 26 from 1:30-5:30 p.m. 

The public listening session is designed to solicit information, concepts, ideas, and comments on EOBRs and the issue of driver harassment. The session will allow interested persons to present comments, views, and relevant research that FMCSA should consider in development of the final rule of EOBRs.

Specifically, FMCSA wants to know what factors, issues, and data it should consider as it addresses the distinction between productivity and harassment:

  • What will prevent harassment from occurring?
  • What types of harassment already exist?
  • How frequently and to what extent does harassment happen?
  • How will an electronic device such as an EOBR, capable of contemporaneous transmission of information to a motor carrier, guard against (or fail to guard against) harassment?

Answers and comments on the following may be submitted in written form at the session and summarized verbally, if desired, FMCSA said:

1. In terms of motor carriers’ and enforcement officials’ monitoring or review of drivers’ records of duty status (RODS), what would constitute driver harassment? Would that definition change based on whether the system for recording hours of service (HOS) is paper or electronically based? If so, how?

As a starting point, FMCSA is interested in potential forms of harassment, including but not limited to those that are not prohibited already by current statutes and regulations; distinct from monitoring for legitimate business purposes (e.g., efforts to maintain or improve productivity); facilitated or made possible solely by EOBR devices and not as a result of functions or features that motor carriers may choose to purchase, such as fleet management system capabilities.

The agency also wants to know if this interpretation appropriate? Should it be broader or narrower?

2. Are there types of driver harassment to which drivers are uniquely vulnerable if they are using EOBRs rather than paper logs? If so, what and how would use of an EOBR rather than a paper log make a driver more susceptible to harassment? Are there ways in which the use of an EOBR rather than a paper log makes a driver less susceptible to harassment?

3. What types of harassment are motor carrier drivers subjected to currently, how frequently, and to what extent does this harassment happen? How would an electronic device capable of contemporaneous transmission of information to a motor carrier guard against (or fail to guard against) this kind of harassment? What experience have motor carriers and drivers had with carriers using EOBRs as compared to those who do not use these devices in terms of their effect on driver harassment or complaints of driver harassment?

4. What measures should the agency consider taking to eliminate the potential for EOBRs to be used to harass drivers? Are there specific functions and capabilities of EOBRs that should be restricted to reduce the likelihood of the devices being used to harass vehicle operators?

5. Motor carriers are often responsible for managing their drivers and equipment to optimize efficiency and productivity and to ensure transportation services are provided in accordance with a planned schedule. Carriers commonly use electronic devices, which may include but are not limited to EOBRs, to enhance productivity and optimize fleet operation. Provided such devices are not used to coerce drivers into violating Federal safety regulations, where is the line between legitimate productivity measures and inappropriate oversight or actions that may be construed as harassment?

The listening session will be recorded and a transcript of the session will be placed in the docket for FMCSA’s consideration.

 

Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish