AWS re:Invent 2020: Connected vehicle repair
AWS re:Invent 2020: Connected vehicle repair
This is a complete connected digital solution that automates the process of scheduling a vehicle service appointment and warranty claim when a vehicle malfunction or fault is detected. It then uses the data collected from the vehicle to drive an augmented reality/mixed media experience to assist the service technician with completing the vehicle repair, allowing the technician to use a mix of computer graphics, video, audio, and voice to interact in real time with a digital twin of the vehicle. It also integrates with supporting applications like dealer management systems.
Learn more about re:Invent 2020 at http://bit.ly/3c4NSdY
Subscribe:
More AWS videos http://bit.ly/2O3zS75
More AWS events videos http://bit.ly/316g9t4
#AWS #AWSEvents
Content
7.52 -> hello i'm david simpson senior solutions
9.28 -> architect at database
10.96 -> today i would like to introduce you to
12.32 -> our builders fair project for re invent
13.84 -> 2020 called connected vehicle repair
16.4 -> connected vehicle repair is a digital
17.92 -> transformation solution that automates
19.52 -> and integrates many of the steps and
20.8 -> processes required to facilitate a
22.48 -> vehicle repair
26.8 -> just to quickly touch on the
27.92 -> presentation agenda we'll start with an
29.84 -> introduction and overview around
31.199 -> connected vehicle repair
32.64 -> we'll talk about the problems we are
34.079 -> trying to solve for and how connected
35.6 -> vehicle repair helps to improve customer
37.28 -> outcomes
38.079 -> describe the functional components of
39.44 -> the solution next we'll walk through a
41.6 -> diagram of the connected vehicle repair
43.12 -> architecture and talk about services
44.8 -> that are used as part of the solution
46.239 -> implementation
47.92 -> finally we'll conclude this presentation
49.36 -> with a series of demo videos that walk
50.96 -> us through a connected vehicle repair
52.399 -> journey from the perspective of several
53.84 -> different stakeholders
54.96 -> such as the vehicle owner and a service
56.84 -> technician during the demos you will see
59.039 -> the applications and use user interfaces
61.039 -> that are part of the connected vehicle
62.399 -> repair solution
66.4 -> so this solution began with thinking
68 -> about what happens when a check engine
69.6 -> light comes on in a car dashboard
71.6 -> they're actually quite a few steps
72.64 -> involved between the vehicle owner
74 -> scheduling the service appointment with
75.28 -> the dealership
76.24 -> to the service department filing a
77.759 -> warranty claim and handling repair
79.36 -> orders with the goal of fixing the
80.64 -> vehicle right the first time
82.159 -> to get the owner back on the road as
83.6 -> quickly as possible
85.28 -> connected vehicle repair helps to
86.72 -> streamline and automate those manual
88.159 -> steps and information exchange
90.24 -> the central idea behind behind the
91.759 -> connected vehicle repair solution is
93.28 -> that when a system fault occurs in the
94.72 -> vehicle we can take it
96 -> take the vehicle's own onboard
97.439 -> diagnostic data known as obd2
100.079 -> codes and use that diagnostic
101.92 -> information as the basis for radically
103.52 -> improving the vehicle repair experience
105.439 -> not just for the customer but for other
107.439 -> stakeholders in the repair process as
109.28 -> well
109.6 -> service technicians customer service
111.52 -> representatives car dealerships and so
113.6 -> on
114.56 -> connected vehicle repair provides a
115.84 -> number of application integrations
117.28 -> designed to improve the experience for
118.719 -> end users
119.52 -> this includes a mobile application for
121.2 -> vehicle owners as well as an augmented
122.88 -> reality or ar application for service
125.119 -> technicians
126.159 -> we will be describing these in more
127.439 -> detail throughout this presentation
129.599 -> the vehicle diagnostic data can also be
131.52 -> used to drive a series of business
132.879 -> processes at the service department
134.4 -> dealership or
135.44 -> original equipment manufacturer
137.28 -> otherwise known as oem
138.64 -> level that is why we have also
140.48 -> collaborated with pega systems an
142 -> individual's partner on connected
143.28 -> vehicle repair
144.239 -> to provide an advanced no code low code
146.879 -> case management solution for managing
148.64 -> warranty claims and repair orders
150.8 -> so now with the connected vehicle repair
152.48 -> solution when a driver sees the check
154.16 -> engine light come on in
155.68 -> in their vehicle becomes a software
157.68 -> driven trigger for engaging with a whole
159.44 -> tool chain of connected services and
161.2 -> applications
162.239 -> designed to make the repair process as
163.84 -> simple and painless as possible
165.44 -> for the vehicle owner as well as the
166.8 -> value chain creator for dealerships and
168.72 -> automobile manufacturers
171.12 -> let's talk about the solution
172.4 -> architecture next
176.4 -> since connected vehicle repair depends
178.159 -> on access to the obd2 code from the
180.08 -> vehicle
180.8 -> iot and data ingest are at the heart of
182.72 -> our solution architecture
184.319 -> to that end we start with the aws
185.92 -> connected vehicle solution on the left
187.519 -> hand side of the diagram
189.28 -> aws connected vehicle solution was
191.04 -> installed on our car when it was
192.239 -> manufactured and uses aws iot services
194.8 -> to send the obd2 diagnostic codes
197.04 -> to the advs cloud for further processing
199.599 -> aws connected vehicle services are able
201.28 -> to support extra large vehicle
202.879 -> fleets securely with low latency and low
205.12 -> overhead
206.159 -> once the obd2 message is ingested it can
208.319 -> be processed using one of the aws iot
210.4 -> processing services to intelligently
212.159 -> route the message and store it for
213.44 -> additional analytics and handling
215.36 -> here we can see that the data from the
216.64 -> vehicles are handled by aws iot core
219.04 -> and an iot rule is used which
220.64 -> conditionally routes the data for
222 -> storage in a time stream time series
223.68 -> database
224.64 -> this information will be used by our
226.08 -> connected vehicle repair mobile
227.599 -> application
228.879 -> we can also land the iot vehicle data
230.799 -> into amazon dynamodb
232.56 -> the solution has the ability to handle
234.159 -> not only obd2
236.239 -> error codes but also vehicle telemetry
238.239 -> data that provides
239.519 -> real-time diagnostic information about
241.439 -> car sensors
242.64 -> this information can then be provided
244.239 -> through connected vehicle repair apis
246.4 -> which are exposed through a combination
247.84 -> of amazon api gateway
249.599 -> amazon cognito for authentication and
251.599 -> authorization and aws alum does supply
254 -> data to the connected vehicle repair
256 -> augmented reality headset application
258.479 -> aws iot core and aws iot analytics can
261.199 -> be used to supply the obd
262.72 -> data to create repair orders and
264.4 -> warranty claims automatically through
265.84 -> the pega systems case management
267.36 -> applications
268.56 -> by using adwords services like kinesis
270.4 -> dynamodb and lambda
272.16 -> we can also keep data in sync between
273.68 -> the pega systems application with other
275.44 -> applications so all business users see
277.44 -> the same view of customer data
279.68 -> now let's jump into the connected
281.04 -> vehicle repair demonstrations
290.08 -> brian is a first-time car owner who
291.759 -> loves driving up to go hiking on the
293.199 -> weekends
294 -> after returning to his parked car from a
295.68 -> hike brian has some issues starting his
297.36 -> car and has noticed the check engine
298.72 -> light is turned on
300 -> based on what brian sees in his
301.36 -> vehicle's dashboard display it looks
302.88 -> like there's something wrong with the
303.919 -> vehicle's electrical system
305.68 -> there's no immediate fix for the issue
307.28 -> but that's okay brian will submit a
308.8 -> request for help through his vehicle's
310 -> media system
311.12 -> the system is connected to aws connected
312.88 -> vehicle solution which uses iot
314.56 -> messaging to transmit the issue to a
316.16 -> customer support system tied to the
317.68 -> vehicle manufacturer
319.44 -> service case is initiated through the
320.88 -> support system on brian's behalf
322.8 -> brian receives a text message on his
324.32 -> mobile phone asking him to schedule an
325.759 -> appointment at his preferred dealership
327.28 -> for service
328.24 -> let's jump to the mobile application to
329.84 -> schedule an appointment and check on the
331.28 -> state of the car using real-time
336.84 -> diagnostics
340.16 -> clicking on the link provided in the
341.44 -> text message launches the mobile
343.039 -> application powered by pega systems and
344.72 -> aws technologies
346.4 -> the mobile application gives brian the
348 -> ability to schedule and review his
349.44 -> service appointment as well as inspect
351.039 -> real-time information
352.08 -> about the health of his car systems
354.24 -> brian decides to book a service
355.52 -> appointment for his favorite dealership
357.039 -> outside boston on the 22nd
359.28 -> the mobile application indicates when
360.8 -> the service department has availability
362.4 -> on that day
363.44 -> all other scheduling details including
365.039 -> information about brian's car and the
366.56 -> check engine light issue
367.68 -> and obd2 codes are included
369.44 -> automatically when the service
370.479 -> appointment is scheduled
372.319 -> so let's hear from andrea and kapil how
374.16 -> the connected vehicle repair mobile
375.759 -> application also supports real-time
377.52 -> vehicle diagnostics
378.88 -> the vehicle owner can use and the aws
381.039 -> technologies behind that
382.24 -> including a way to retrieve obd2 data
384.72 -> you can try at home
386.16 -> here is a vehicle owner facing mobile
388.479 -> application
389.6 -> that is showing real-time performance
391.68 -> and health data
392.88 -> from the car's onboarding diagnostics
395.6 -> obd
396.96 -> the application is created using swift
399.44 -> ui framework
400.8 -> and is using aws appsync service
403.919 -> to get the data from the backend system
407.199 -> let's talk about how the data is
408.88 -> persisted from the car's
410.639 -> obd from the back end powering
413.68 -> this mobile application we make use of
416.319 -> raspberry pi
417.36 -> that uses bluetooth-powered opd device
419.759 -> connected to vehicle's obd port to get
422.08 -> vehicle diagnostic data
424.08 -> a python client runs on raspberry pi and
426.639 -> collects obd data from the car
428.639 -> over bluetooth connection and pushes
430.8 -> that data into aws iot using mqtt
433.759 -> protocol
434.88 -> from there the raw vehicle data is
437.36 -> stored in amazon time stream
439.36 -> using iot rules the appsync service
442.16 -> described earlier provides a managed
444.24 -> graphql interface
445.44 -> to pull the data from timestream and
447.84 -> load that into mobile apps ui
453.039 -> we will now join ignacio the customer
454.88 -> service advisor at the dealership when
456.479 -> brian takes the vehicle in for his
457.919 -> service appointment
459.28 -> because the repair service is managed on
460.88 -> the pegasus platform it can
462.56 -> automatically look for existing
463.84 -> warranties that are active
465.199 -> and ensure that a repair claim is
466.4 -> created against the correct warranty
468.4 -> after seeing that as an electrical
469.68 -> problem ignacio enters information about
471.68 -> the repair in order to start the repair
473.28 -> work with a service technician
475.199 -> from the repair screen ignacio can enter
477.039 -> details about the type of error brian
478.879 -> cars
479.52 -> brian's car has what types of parts need
481.919 -> to be replaced and what service work
483.44 -> needs to be charged for the repair
485.52 -> capturing all this information in one
487.039 -> place is important as warranty claim
488.8 -> auditors that the vehicle manufacturer
490.4 -> will eventually have to review it for
491.919 -> accuracy
493.199 -> pega systems is able to automate much of
494.72 -> the work required in order to help to
496.24 -> ensure
496.8 -> the repair is properly covered under
498.319 -> warranty
502.319 -> since the warranty and repair orders are
503.759 -> managed by pega systems ignacio can also
505.84 -> review any of the details around the
507.28 -> overall case
508.4 -> this includes details about the vehicle
510.16 -> as well as warranties active on the
511.599 -> vehicle
512.32 -> and information about the customer that
513.919 -> brought the vehicle in
515.44 -> ignacio can also gain insight into the
517.44 -> specific steps the repair order
519.2 -> will have to follow to completion now
522.159 -> let's switch to amy the service
523.36 -> technician who is using the connected
524.8 -> vehicle repair
525.6 -> augmented reality application
537.6 -> amy is in the service bay working on
539.2 -> brian's car she launched the ar
540.959 -> application on her ar headset which
542.959 -> provides a three-dimensional digital
544.48 -> twin view
545.279 -> of the vehicle amy is able to view
547.36 -> relevant information about the vehicle
548.959 -> such as the vin number
550.24 -> that is part of the repair order she is
552.72 -> also able to view real-time obd2
555.2 -> diagnostic data right off the car over
557.279 -> aws iot services as she performs her
559.839 -> work
560.64 -> this information is displayed in the
562.24 -> dial gauges on the right hand side of
564 -> the car
565.6 -> once amy has completed the necessary
567.2 -> repairs on brian's car she can sign off
569.12 -> on any repair checklist the dealership
570.959 -> or manufacturer requires in order to
572.48 -> officially complete the repair order and
574.16 -> warranty claim
575.44 -> remember the goal is getting the repair
577.12 -> right the first time
583.839 -> the connected vehicle repair solution
585.36 -> can also be extended in various ways
587.519 -> you can harness the power of its data
588.88 -> collection capabilities to build new
590.32 -> products and applications that derive
592 -> insights from customers and business
593.519 -> processes using machine learning and ai
595.839 -> capabilities
597.44 -> at the top layer is the data lake
599.2 -> solution built on amazon s3 that allows
601.36 -> raw historic data to be collected
602.959 -> transformed or aggregated at this layer
605.519 -> in a curated layer that can also be used
607.839 -> made available to downstream users such
609.6 -> as data scientists and analysts
611.36 -> for exploratory data analysis and
613.2 -> designing predictive maintenance
614.399 -> solutions
615.6 -> you can leverage amazon sagemaker are
617.36 -> fully managed service that provides the
618.8 -> ability to build train
620 -> and build train and deploy machine
621.76 -> learning models for that purpose
624.16 -> one example is a part of our solution
626.48 -> we've done some exploratory analysis and
628.48 -> found that
629.04 -> the top three used obd2
632.079 -> diagnostic codes from our car data sets
634.24 -> that we've been collecting
636 -> first one would be engine rest time
637.68 -> otherwise known as soaking time
639.839 -> second one would be engine coolant
641.44 -> temperature and the third one would
643.2 -> actually be an option to augment our
645.6 -> obd2
646.8 -> obd2 diagnostic data with gps
649.68 -> information to track where and when
651.12 -> certain events occur with the vehicle
653.519 -> an idibos iot rule sends sensor data to
656 -> the amazon kinesis data fire hose
657.839 -> delivery stream
658.8 -> which encrypts and streams raw vehicle
660.56 -> telematics data to an amazon s3 bucket
663.6 -> when amazon kinesis data analytics
665.6 -> application detects an anomaly
667.36 -> the record is sent to amazon kinesis
669.2 -> data streams which invokes an aws lambda
671.2 -> function that parses the record
672.8 -> and stores it in an amazon dynamodb
674.8 -> table
683.04 -> finally ignacio can go back into the
684.72 -> pega systems application to verify that
686.8 -> amy has completed the repair
688.8 -> with this last step the warranty claim
690.64 -> can also be submitted back to the
692 -> vehicle manufacturer
693.839 -> with connected vehicle repair aws and
696.16 -> pega systems help dealerships and oems
698.079 -> deliver better client experiences with
699.68 -> their products
700.56 -> and generate new revenue streams while
702.079 -> rapidly streamlining and connecting
703.76 -> aftermarket processes
709.12 -> i want to take a moment to thank
710.56 -> everyone who helped contribute to this
712.24 -> product
713.279 -> andrea's project rather uh andrea
716 -> sabette
716.72 -> kapil sharda sarita joshi bill connors
719.519 -> jitendedya
720.56 -> and also from pega systems carolyn
722.48 -> rostetter and gabe isco
724.32 -> we wouldn't have been able to build out
725.68 -> this presentation and solution overall
728.16 -> without all of their combined efforts
730 -> i'm greatly appreciative of that
733.68 -> thank you very much that concludes my
741.24 -> presentation
Source: https://www.youtube.com/watch?v=ww4pz5m98zs