Presentation on theme: "On board device basics Prepared by: Jim Angel PeopleNet"— Presentation transcript:
1 On board device basics Prepared by: Jim Angel PeopleNet Dave Kraft QualcommTom Cuthbertson XATA
2 DisclaimersThe content of this presentation reflects the experience and views of the individual preparers of this material. This presentation is intended to provide a basic level of understanding about electronic HOS capabilities as are widely implemented in the US. The materials are not intended to provide any representations for products and services. They also should not be considered as a definitive reference of requirements and system performance capabilities.The Federal Motor Carrier Safety Administration (FMCSA) does not endorse or recommend any specific products and services for electronic driver logs and related systems. FMCSA is not responsible for the factual content of the presented materials, nor that the representation of device capabilities are consistent with regulations.
3 Training Outline Electronic HOS Defined Basic Configuration On-Board DevicesElectronic HOS Support SystemsThree Basic OptionsDriver ConvenienceCarrier ConvenienceInspection Process
5 On board device today AOBRD 395.15 Final rule in 1988 GPS not yet availableEngine Control Module (ECM) not yet availableCurrently confused in the market with anything that provides any type of electronic informationLaptopTachographSmart Phone (395.8 app)Etc.Defined as: “an electric, electronic, electromechanical, or mechanical device capable of recording driver's duty status information accurately and automatically.Market has driven requested features such as:Communication to/from driver and carrierEngine monitoringMPG reportingAutomated fuel tax reportingGPS location informationDriver HOS alertsCarrier compliance toolsDriver performance
6 What is an onboard device now? Device features expanded greatly over last decadeReport and monitor MPGECM data and fault codesIntegration with routing and dispatch softwareNavigation, with turn by turn directionsElectronic Hours of ServiceSupport system web sites for real time informationCompliance and payroll reportsand much moreQualcomm MCP 200XATA TurnpikePeopleNet BLU 2
11 Vehicle System overview Device RequirementsRegulationUnique ID for all driversVehicle synchronization for drive recordingBasic duty status event recordingBasic display requirementsSensor failure detection / alertMarket Driven CapabilitiesGrid-graph and other added display featuresGPS and map database (for automatic location recording)Wireless log synchronization between on- board system and host support system (for compliance management)On-board device and driver ID authenticated at host systemUnique driver/co-driver ID and loginECM /GPS used to detect vehicle movement for automated start and stop of driving timeDriver makes manual entries for non- driving duty status eventsDevices vary in appearance and featuresonly defines data for inspection display and not standard formatsWireless transmission to support systems
12 Vehicle system – Issues for Mandated electronic logging systems Certification:Hardware technology has many options subject to performance requirementsSelf-certification = no standard approach to testingBuyer beware without 3rd party certificationEnforcement Interface:No standard formats to support manual roadside inspectionsLimited access to information about annotations, sensor failures, log data gaps/exceptions, and position detailsData transfers via USB or Wi-Fi hotspots (802.11) are not necessarily to be trustedSecurity Controls: (requirements not specified)System integrity verified with installation and data diagnosticsDriver ID and vehicle device ID validated by support systemTrusted uploads from support system to maintain current logs for drivers
14 Support system overview Support System Capabilities395.15Logs submitted within 13 daysBasic log data record contentLog data retained for 6 monthsArchive in location separate from deviceCarrier Driven EnhancementsLogs submitted near real-timeLog archive with structured data recordsArchive in cloud services model with access controls by service providerAnnotation features with audit trail and update to on-board unitHOS displays/alertsWeb portal for driver access functionsSecurity features of providers ensure data is secure and privateSupport system must not allow data alteration or deletionWeb portal access and features provide compliance management and log data reviewsDriver log archives available for inspection access with similar presentation to a paper log
15 Support system – Issues for Mandated electronic logging systems Certification:Support system often has many features beyond what is required in the ruleCertification complexity of large scale systemsEnforcement Interface:Incomplete specifications for data formatting and transfer protocolsData transfers via USB or CD-ROM for investigations are not necessarily to be trustedData transfers from support system via web services have not been identified for use with investigationsSecurity Controls:(requirements not specified)Trusted data transfers between vehicle system and support system via wireless networksSupport system access controls for log reviews and correctionsSupport system access controls for controlled issuance of driver IDsTechnical access controls to prevent manipulation of log archivesUpdate of vehicle system software in trusted manner
16 Electronic HOS Functionality Logs are typically synchronized with support system in near real time:There can be an combination of the following: at each time of duty status change, end of day and/or beginning of dayEnsures carrier management reviews and log corrections are updated timely in 7 & 8 day logsAffords slip seat operations or shift operations to have up to date logs without paper for each driverLogs automatically follow driver to different truck
17 basic optionsEOBR systems have significant differences in terms of overall technical architecture and operational models . . .
18 Primary systems design Common features:Majority of devices today have wireless connectivity via cellular/satellite or bothNear real-time communication between carrier and driverGPS, and automated locations for duty status changeAuto duty status change based on vehicle movementBasic Options:Fleet management system – system mounted in vehicleHandheld device and smart phone system – ECM interface box in vehicle but display units can operate outside vehicleDevices that only do electronic driver logs – not really used today or not really compliantLap-topTachographSmart Phone (395.8 app)Etc.
19 Fleet management system System features:Electronic HOS is an applicationTurnkey system approach for hardware/servicesTelematics servicesIntegrated GPS trackingIntegrated vehicle data monitoring servicesLog archive servicesCarrier portal for records and compliance mgmtOther applications and services also availableSecurity:Requires driver loginSoftware updates controlled by provider, and only given by support tech, or OTA, (Over the Air) serviceData access only through the HOS applicationData auto archivedSecure Web-based access to correct or edit logsSecure driver Web access for logs review and entry of non-driving eventsSecure auto data sync with host system and device
20 Handheld Device & Smart Phone Systems System features:Electronic HOS is an applicationDevice & wireless services may be purchased separatelyAdditional “black box” for vehicle interfaceIntegrated GPS trackingLog archive servicesCarrier portal for records and compliance managementOther applications and services also availableSecurity:Requires driver loginSystem security features to manage unique driver ID.Software and update controlled by end userProprietary data protection appliedData auto archivedSecure Web-based access to correct or edit logsSecure driver Web access for logs review and entry of non-driving eventsSecure auto data sync with host system and device
21 Driver ConvenienceEOBR systems have significant differences in terms of overall technical architecture and operational models . . .
22 Driver features Current HOS available time Proactive warnings when time in last hourEnter/View/annotate duty status (no driving)Enter/Edit load & trailer dataDisplay summary, graph and detail viewsDisplay 24 hour and 7 & 8 day log viewsReview/Approve logsGenerate log report/fax for inspection (if needed)Auto duty status change based on start and stopPeopleNet SafeModeQualcomm Screen
23 Carrier ConvenienceEOBR systems have significant differences in terms of overall technical architecture and operational models . . .
24 Carrier features Current HOS available Enter/View/Edit duty status Load planningHOS complianceEnter/View/Edit duty statusViolations alert and reporting availableHOS alerts when drivers running out of timeDisplay 24 Hour and 7 and 8 day log viewsReview/Approve logsPrint logs for driver or for auditMultiple reports tied to HOS for payroll, and driver utilizationDriver behaviorProductivityMany others that assist in carrier and vehicle management
25 Roadside inspection process EOBR systems have significant differences in terms of overall technical architecture and operational models . . .
34 summaryCarriers using on-board devices for a lot more than HOS complianceRoutingDispatch PlanningPayrollCarrier complianceViolation reportsAbility to print, fax, or drivers logs to enforcement, roadside or in a CRVoluntary adoption is growing for more reasons than HOSElectronic HOS providers actively provide and participate in training enforcement on displays for inspection
35 Jim Angel PeopleNet Dave Kraft Qualcomm Tom Cuthbertson XATA Thank youJim Angel PeopleNetDave Kraft QualcommTom Cuthbertson XATA