netcdf data in weather and climate applications - recent proceedings
TRANSCRIPT
J. J. Keller & Associates, Inc.
Thomas Bray
Hours of Service and Electronic Logs: Where We
Are and Where We're Going
Hours-of-Service History
⢠1936/1938: Original HOS rules, 12 hours of duty (driving and/or on duty), 9 hour break, 60/70
⢠1939: First changes,10 hour driving added and break changed to 8 hours ⢠1962: 15 hour on-duty limit added ⢠2003/2004: 11, 14, 60/70 with restart for property carriers ⢠2003: New rules challenged by safety groups and ordered vacated ⢠2005: Rules reissued, with changes to split sleeper ⢠2006: New, new rules challenged in court by safety groups, ordered vacated ⢠2008: Rules reissued, with nearly no changes ⢠2009: New, new, new rules challenged in court by safety groups, settlement to
change rules reached in 2010 ⢠2012: Changes result of the challenge/settlement published (which went into full
effect in 2012/2013) ⢠2012: Industry challenges new rules in court ⢠2013: Court rules in favor of FMCSA, rules stand as is with exception of 100 and
150 air-mile drivers exempted from 30-minute break
Hours-of-Service Regulations
⢠Where we are â âLog bookâ basically unchanged since 1960âs â July 2013 changes in full effect
⢠8, 11, 14, 60/70 with restricted restart all in place and being enforced â 8-hour/30-minute break requirement now third most common
HOS violation written on the road â No jump in 60/70 hour violations
⢠10, 15, 60/70 with no restart still in place for passenger-carriers
â Several exemption petitions are in play ⢠Split break rules ⢠30-minute break
Hours-of-Service Regulations
⢠Most recent changes
â Electronic log allowed, if displays all §395.8 information and driver can print on request
â Livestock exception to 8-hour/30-minute break requirement
â Exemption to 30-minute break requirement for âshort-haulâ driver
Hours-of-Service Regulations
⢠Where we are going â According to FMCSAâŚno where (no changes in
foreseeable future, other than occasional exemptions) â According to courtsâŚno where, they ruled already â According to CongressâŚweâll see
⢠Committee action in both Senate and House has led no where to date
â Passenger carriers ⢠FMCSA recently had âlistening sessionsâ about rules ⢠Still an open item
Question for the Group
⢠How long has âautomatic electronic loggingâ been around?
ELD History
⢠1985: First âAOBRDsâ authorized
⢠1988: AOBRDs written into regulations (present §395.15)
⢠2010: EOBR âbad appleâ rule placed in regulations (to take full effect June 2012)
⢠2011 (Feb.): EOBR âuniversal mandateâ proposed
⢠2011 (Aug.): EOBR bad apple rule struck down by court
⢠2014: Supplemental âuniversal mandateâ proposal released (âELDâ proposal)
Where We Are
Automatic Onboard Recording Devices (AOBRDs)
AOBRDs
⢠Simply take the place of the driverâs paper log ⢠Capable of automatically and accurately recording of
HOS (specifically driving time) â Much more accurate than paper logs
⢠Does not affect âlimits and exceptionsâ ⢠Eliminates most common violations (log not current,
form and manner) and reduces driving violations
Whatâs an AOBRDs?
⢠Integrally synchronized with the CMV ⢠Displays information required in §395.15, NOT §395.8 â Not required to print
⢠Downloadable/saveable data file retained for six months in back office
Whatâs an AOBRDs?
A system that produces a Record of Duty Status based on engine/movement data and driver entries
Generally Three Components:
AOBRD connected to engine
Driver Display/Interface Back-Office
Whatâs NOT an AOBRDs?
⢠Many devices today are NOT AOBRDs due to not being connected to vehicle! â Laptop logs â Smartphones â PDAs/Tablets/iPads/iPods
⢠Regulated as paper logs â Must display all of §395.8 information â Officer can ask for printed copy â Must be electronically or physically signed
Where Weâre Going
Electronic Logging Devices
(ELDs)
ELD Proposal
⢠Covers ELD use, ELD technical standards, and retention of supporting documents
⢠Would require all driver that complete logs to begin using ELDs two years after final rule effective â Only exceptions are 100 and 150 air-mile drivers
that only completed logs 8 days (or less) out of last 30 days
⢠ELD would need to be on FMCSAâs ELD registry (yet to be created)
ELD Proposal
⢠No exceptions for:
â Small fleets
â Older vehicles
â âSmallâ vehicles (non-CDL vehicles)
â Passenger carriers
â Driveaway/towaway drivers
â Leased or rented vehicles
â âNon-truckingâ motor carriers
ELD Proposal
⢠System must automatically capture data set: â At startup and shutdown â At each change of duty status â Once per hour wen vehicle is operating â At start and end of âpersonal useâ or âyard timeâ
ELD Proposal
⢠Data set must include: â Date and time â Location (accurate to one mile) â Engine hours and vehicle mileage â Driver logged in â Vehicle identification â Authorized carrier identification
⢠Location to be accurate to 10 miles during personal use
⢠Record must be submitted to carrier within 8 days
ELD Proposal
⢠Technical specifications â System must include unique accounts for all
drivers and support personnel ⢠Driver account must include driverâs license
information
â All users must have user name and password associated with their account
â System must include âunassigned driverâ account ⢠All unassigned driving time must either be assigned or
accounted for
ELD Proposal ⢠Technical specifications
â Must be getting engine, speed, and distance data from the vehicle
â Portable driver devices must be mounted within driverâs reach
â Must use âstandard data output formatâ â System must be able to report out to officers using
multiple formats â Carrier has to be able to make records available to
auditors and have a âbackup copyâ
ELD Proposal
⢠Display must show: â Driverâs name and ELD user name â Miles driven and engine hours â Malfunction and diagnostic status indicators â Record for the driver including:
⢠Change of duty statuses, total driving miles for each driving period, and starting and ending for personal use and yard driving events
â A summary of the driverâs total on-duty and driving time for the current day and previous seven days
â A grid graph view of the current day and the previous 7 days
ELD Proposal
⢠Driver interaction â Driver will have the normal âfour linesâ (driving
time automatically determined) â Driver must manually enter some information â Driver entries to be made when vehicle is
stopped â Driver must notify carrier within 24 hours of
system failure
ELD Proposal
⢠Driver âpromptedâ for entry if: â Log in if vehicle moves with no driver â Duty status if stopped for five minutes (system
to default to on duty if no driver entry) â Location if no position fix at duty change
⢠Driver does NOT have to be prompted when approaching limit
⢠System must have âmuteâ to be used when driver is in the sleeper
ELD Proposal
⢠Driver interaction â Driver must âcertifyâ log when submitting â Driver must âre-certifyâ if any changes are made
to records â All annotations, comments, and changes must be
retained, along with original â Driver MUST be able to get copies of all records
for past 6 months from system or carrier
ELD Proposal
⢠Driver harassment protections â Reinforcing of âno carrier shall require a driver
that is ill or fatigued to driveâ regulations â Updated complaint procedures and fines related
to ELDs â Driverâs right to all data and records â Limits on location accuracy
ELD Proposal
⢠Timeline based on proposal â Now
⢠Comment period on proposal closed, FMCSA reviewing and considering comments
â Late 2014 or 2015 ⢠Final rule published and becomes effective. Two year implementation
period begins
â Late 2016 or 2017 ⢠ELDs required
â Late 2018 or 2019 ⢠AOBRDs that cannot be updated to ELDs that were in use when ELDs
became mandatory would have to be removed from service
2014 2015 2016 2017 2018 2019
Final Rule Published ELDs Required âUn-updateableâ AOBRDs Eliminated
How To Get There
Change Management
Prepare, Implement, Reinforce
How to Get There
⢠Transitioning from paper to electronic takes time and effort â Use disciplined âchange management approachâ â Serious consequences if not done well â âFast and messyâ leads to problems
⢠Will NOT result in instant compliance ⢠Be prepared to deal with data
â Good news: Lots of data to improvement management â Bad news: Lots of data to sort through
⢠Study current state and future state â Will there be a revenue drop? If so, why? â Determine hard and soft ROI
⢠Be prepared for resistance from drivers and supervisors
First step: Preparation
⢠SECURE UPPER MANAGEMENT SUPPORT (all upper managers, not just some, or one)
⢠Determine needs and wants â What is your ideal âfuture stateâ
â Consider âteamâ or âcommitteeâ approach
⢠Start vendor/system search
⢠Initiate regular communications on the progress
⢠Retrain drivers and supervisors on HOS rules and limits
⢠Plan for personnel changes
First step: Preparation
⢠Develop policies and procedures â Data uses
â Disciplinary policy (drivers and supervisors)
⢠Consider personnel redeployment and training â Do not underestimate the amount of training that
will be necessary
⢠Develop hardware and software installation plans
Second Step: The Changeover
⢠Finalize detailed plans for: â Resource allocation â Training of drivers, supervisors, and support personnel â Disciplinary actions â System setting â Installation
⢠Finalize policies and procedures ⢠Continue retrain drivers and supervisors on HOS rules
and limits ⢠Implement ELD system training of drivers, supervisors,
and support personnel
Second Step: The Changeover
⢠Begin with âbeta testâ group â Small group of good drivers and supervisors â Verify data usage, settings, policies, and training â This group will be âmentorsâ during following steps
⢠Expand implementation â Roll out by âlocationâ or âgroup,â depending on where the
âcontrolâ is â Save âproblemâ drivers and supervisors for last batch
⢠Complete implementation â Be prepared for resistance at this point
⢠Continue communications!
Step Three: Reinforce
⢠Be prepared for âsaboteursâ ⢠Monitor and track
â The system â The data and reports â Error/edit rates â Violation rates â Calls for assistance
⢠Follow-up training when needed (counsel and correct, first)
⢠Celebrate and build on successes
Final Considerations
⢠Be prepared for the âcheatersâ â Sharing log ins
⢠Clue: A non-working driver turning miles, working driver missing miles
â Drivers/supervisors using âGhost Driverâ accounts ⢠Clue: âMaintenanceâ and/or other ânon-existent driverâ accounts doing
thousands of miles
â Not logging in or logging out while working/driving ⢠Clue: âUnassigned milesâ account doing thousands of miles
â Supervisor assistance (such as changing on-duty to off-duty) ⢠Clue: Excessive edits
â System tampering ⢠Clue: Diagnostic report from unit (driver) and user âfootprintsâ (supervisor)
surrounding a system or data failure
â Logging off duty for everything ⢠Clue: Very little or no on-duty time in the system
Final considerations
⢠Carriers that are forced to (or choose to) quickly implement have poor success records â High bankruptcy/failure rate â Systemic problems or cause/effect?
⢠âTabling itâ after starting implementation and coming âback to it laterâ creates problems â âWe killed it last timeâŚâ â âTheyâre not serious this time eitherâ
⢠System will very quickly pointing out problems â You will need to be prepared to handle them quickly