Presentation at the Technology and Maintenance Council on March 20, 2019

2. Technology & Maintenance Council
. . . Turning Experience Into Practice

3. Attention Please
• In accordance with TMC Board Policy, all personal
phones without a silent feature must be turned off
during business sessions.
• If you must use your phone
—please leave the room!

4. Attention Please
• This is an open meeting of the Technology & Maintenance
Council, held in accordance with ATA Antitrust Guidelines
which are listed in your meeting packet.
• Audio or video recordings are not permitted at this session.
However, photography is permissible.
• The opinions expressed in this meeting are those of the
individual and not necessarily the opinion of his/her
company nor of TMC unless stated otherwise.

5. Antitrust/Patent Disclosure
• To minimize the possibility of antitrust problems, the guidelines detailed
in your registration packet should be followed at all TMC meetings, task
force and study group sessions.
• All participants in any group involved in the development of standards or
recommended practices shall disclose, as stated in the antitrust/patent
disclosure guidelines in your registration packet, all patents or patent
applications that are owned, controlled or licensed by the Participant or
Participant’s employer when the Participant reasonably believes such
patent or patent application may become material to the standard or RP
development process.

6. Constructive Comments
Are Always Appreciated!
TMC welcomes your comments, but please make
certain that they are constructive and
appropriate before you turn in your evaluation
sheet?
Thank You for Your Cooperation!

7. Smart Trailers:
Creating Trucking’s
Next
Information Superhighway

8. Fleet
• Enhanced Maintenance
• Cost per Mile
• Road Breakdowns
Trailer OE
• Issues
• Benefits
• Warranty Data
Expert
• How We Got Here
• How It Works
• Standards
Diagnostics
• Learn from Past
• Interface to FMS
• Software Updates

17. Aaron Wood

18. Proven Impacts
• Better control of trailer count
• With tracking we are able to manage our trailer count where we need it and not
carry more trailers than needed
• This results in a lower maintenance cost per trailer
• Reduction in scheduled maintenance performed over the road vs. in
house
• This has reduced our over all spend on DOT’s over the road

19. 80.00%
85.00%
90.00%
95.00%
100.00%
105.00%
Jan-16
Feb-16
Mar-16
Apr-16
May-16
Jun-16
Jul-16
Aug-16
Sep-16
Oct-16
Nov-16
Dec-16
Jan-17
Feb-17
Mar-17
Apr-17
May-17
Jun-17
Jul-17
Aug-17
Sep-17
Oct-17
Nov-17
Dec-17
Jan-18
Feb-18
Mar-18
Apr-18
May-18
Jun-18
Jul-18
Aug-18
Sep-18
Oct-18
Nov-18
Dec-18
TRAILER COUNT
Percent

20. Scheduled Service Outside Versus Inside

21. Mark Ehrlich

22. OEM Perspective – Assembly / Integration
Todays Specs
• Axles
• Bearings
• Doors
• Brakes
• Electrical
TRAILER ASSEMBLY
Smart Specs
• Devices (Sensors)
• Gateway
• Network
• Analytics
• Security
SYSTEM INTEGRATION

23. Devices
•Sensors
Networks
•Cellular
Platform
•Google
•MS
Apps
•Software
•Dashboards
Data
Processing
•Analytics
Storage
•Cloud Servers
Security
•Largest Hurdle
OEM Considerations
• Open platform – full connectivity between
legacy systems
• Tractor Trailer – system level data requires
tractor/trailer communication
• Trailer Birth - OE level integration offers
lowest cost installation
• Monitor vs. Control
• Data ownership
• Monetization
• Unknown Risks

24. OEM Challenges
• Network Effect: Durable purchases lock you in. (i.e. Gateway,
Telcom contract, data security) Open platform, common
standards are needed
• Economy of scale: New partners entering market. Silicon Valley
vs. Casting company. Core competencies are being challenged!
• Economy of scope: New capabilities are available everyday.
Reliability/security has advanced
• Firehose Effect: To scale and provide value, data must be
actionable

25. Customer Value: Value Segments
• Compliance
• Anticipate downtime or machine failures before operations are impacted
• Automated weigh station, collision mitigation
• Operational
• Improve inventory management / utilization
• Maintenance
• Condition Based Maintenance - Streamline repair and maintenance processes
• Fuel
• Dynamic tire inflation, platooning
• Driver
• More efficient use of personnel

26. Inputs to Future Design
• Knowing how our customers use our products is paramount to
our future product design and ultimately business
• Leveraging IoT in our trailers increases quality of incoming data
• Data ownership and security is a concern

27. Wally Stegall

28. In the beginning,
Yesterday’s Trailer in North America

29. Yesterday’s Trailer 1997-2001
PLC4Trucks added to address legal
requirement for warning light in dash with a
requirement for trailer mounted lamp

30. Yesterday’s Trailer Early 2000s
Trailer tracking with load sensing began

31. Yesterday’s Trailer 2010
Reefers begin to add
electronics and
telematics to systems

32. Yesterday’s Trailer 2015
got milk?

33. Emerging Smart Trailer 2016-2019
“Smart” Trailers Announced and Demonstrated
 Great Dane
 Phillips Industries
 Truck-Lite
 Peterson
 Others
So what the heck is a “smart” trailer?

34. J1939-1? 250, 500, FD, XL
Ethernet. Non-Braking
TGU = telematics gateway unit
IVN = in-vehicle network
IVN Tractor
To Trailer 2
IVN Trailer
Command and Control Braking

35. Smart/Safe Tractors Require a Smart Trailer That Is Health
Ready to Enable Condition Based Maintenance
Level JA 6268 Vehicle / Equipment Sensor Health
0 Limited On-Vehicle Warning Indicator
1 Enhanced Diagnostics Using Scan Tools
2 Telematics Providing Real-Time Data
3 Component Level Proactive Alerts
4 Integrated Vehicle Health Management
5 Self Adaptive Health Management

36. Dave Covington

37. Diagnostic Challenges
• What are some diagnostic challenges from the past
(tractor/trailer) that may be avoided in the future on
the trailer?
• Diagnostics not keeping pace with the rapid adoption of
new technology
• Lack of oversight in diagnostic standards

38. Diagnostics Slow to Evolve
SAFETY/AUTONOMY
EMISSIONS
EURO STANDARDS
Rapid
Growth in
New
Technolog
y
Standar
d Info
OEM
Proprietar
y Info
Diagnostic / Communication Standards
J1939, J1587, ISO15765/UDS, KWP2000, GM-
LAN
RP1210
Diagnostic Applications
Vehicle technology is complex and changing rapidly
• Since 1995:
• Avg number of ECUs on commercial truck has risen from 2 to 15
• Avg number of data points on commercial truck risen from 60 to
700+
• Diagnostics have not evolved at nearly the same rate as the
technology complexity
• We are still evaluating a list of faults and data
• Diagnostic tools need to be smarter
• Provide answers not questions
• Tools like machine learning and analytics can lead the way

39. Diagnostic Standards
RP 1210 • TMC nailed it with RP1210 and it has been
an unquestionable success
• Yes, I know it is not a standard
• Most major diagnostic applications use it
• Fleets have pushed compliance
• Diagnostic app providers
• Vehicle interface adapter providers
• The days of needing a box full of cables
and interface boxes is largely a thing of
the past.

40. Protocol Standards—Tractor
• Current standards provide means for proprietary messaging
• Which is highly used
• Why should we care?
• A standards-based diagnostic app would not be able read all the fault codes.
• TSPs, service writer tools, and others can’t get the data you want or they need
• The deeper you get into diagnostics the more proprietary it gets.
• An all makes/models fleet could require up to 30 separate
diagnostic apps

41. Challenges in Data Transfer
from Trailers to Fleet Information Systems
• Broad use of proprietary data
• Almost impossible for TSPs to give you the data you want
• Some requested ops data not on data buses
• Camera data, TPMS, Refrigeration, etc., especially on the trailer
• No common communications bus on trailer other than PLC/J2497
• No easy way to get data from trailer to tractor
• Most tractor/ trailer telematics devices do not speak PLC/J2497
• Difficult for them to get diagnostic status/data from the ABS
• Trailers do not have a built in power source
• There are somewhere between 1.8 to 4 trailers for every tractor
• Could get expensive to outfit all trailers with telematics

42. Possible Solutions for Trailer Data Transfers
• Create a standard that opens up communications between tractor and trailer
• Consider both wired and wireless options (redundancy for autonomy)
• Higher speed communications channels to support vehicle controls and data
exchange
• A standard protocol that supports a secure data exchange
• Select a connector between the tractor and trailer that is reliable and will support
future data growth needs
• Add a standards based communications bus on the trailer that allows for the
addition of non-ABS devices

43. Manage Software Updates
• Historically, software updates required a shop visit, causing many fleets to forego
updates.
• Today, most OEs are able to apply engine updates OTA, but there are limitations.
• Transmissions and brakes have not gained the same level of connectivity, and
therefore still primarily require downtime in a shop to be updated.
• Moving forward, fleets should have the ability to control and monitor remote
software updates from a central portal that is not OE specific.
• Eventually, smart updates could be applied just in time to optimize for the route,
the weather condition, the driver behavior, load, etc.

44. Questions and Answers Are Welcome