AWS IoT FleetWise Documentation

With AWS IoT FleetWise, you can collect vehicle data and organize it in the cloud, making the data easier to analyze and use in applications.

AWS IoT FleetWise helps you efficiently transfer data to the cloud using intelligent data collection capabilities. These capabilities allow you to reduce the amount of data transferred by defining rules for when to collect and transfer data based on configurable parameters (for instance, vehicle temperature, speed, or make and model).

Once the data is in the cloud, you can use it for applications that analyze vehicle fleets. This analysis can help you identify potential maintenance issues or make in-vehicle infotainment systems smarter.

Vehicle data collected through your use of AWS IoT FleetWise is intended for informational purposes only (including to help you train cloud-based artificial intelligence and machine learning models), and you may not use AWS IoT FleetWise to control or operate vehicle functions. You are solely responsible for all liability that may arise in connection with any use outside of AWS IoT FleetWise’s intended purpose and in any manner contrary to applicable vehicle regulations.

Vehicle data collected through your use of AWS IoT FleetWise should be evaluated for accuracy as appropriate for your use case, including for purposes of meeting any compliance obligations you may have under applicable vehicle safety regulations (such as safety monitoring and reporting obligations). Such evaluation should include collecting and reviewing information through other industry standard means and sources (such as reports from drivers of vehicles). You and your End Users are solely responsible for all decisions made, advice given, actions taken, and failures to take action based on your use of AWS IoT FleetWise.

You can use AWS IoT FleetWise to collect and organize data from vehicle vision systems that include cameras, radars, and lidars. It keeps both structured (object list, sensor metadata, vehicle ID) and unstructured (images, video) vision system data, metadata (event ID, campaign, vehicle), and standard sensor (telemetry data) automatically synchronized in the cloud, making it easier for you to assemble a full picture view of events and gain insights.

When collecting vision system data using AWS IoT FleetWise, you can take advantage of the features and interfaces you already use to collect telemetry data. Get started on AWS by defining and modeling a vehicle’s vision sensors, alongside its attributes and standard sensors. Your Edge Agent for AWS IoT FleetWise deployed in the vehicle collects data from standard CAN-based vehicle sensors (engine temperature, fuel pressure), as well as from vehicle sub-systems that include vision sensors like cameras, radars, and lidars. You can use the same event- or time-based data collection campaign to collect data signals from both standard sensors and vision systems.

In the cloud, you see a unified view of your defined vehicle attributes and other metadata, telemetry data, and structured vision system data, with links to view unstructured vision system data in Amazon S3. Timestamps and campaign and event identifiers keep data automatically synchronized across different formats, simplifying its use in downstream applications and analytics.

You can use AWS IoT FleetWise to build virtual representations of vehicles in the cloud and apply a common data format to structure and label vehicle attributes, sensors, and signals. AWS IoT FleetWise is designed to standardize vehicle data modeling using the Vehicle Signal Specification (VSS), so that a signal like speed is represented as “vehicle_speed” and measured in kilometers per hour (km/h). Once the vehicle is modeled, you upload a vehicle network file, such as a CAN database (DBC) file, and AWS IoT FleetWise reads the unique and proprietary data signals sent over the vehicle’s network.

To use the service, you need to create an Edge Agent for AWS IoT FleetWise to facilitate your communication between the vehicle and the cloud. You can develop your Edge Agent by reviewing the instructions in the Edge Agent Reference Implementation for AWS IoT FleetWise and tailoring the sample software code so it meets your requirements. 

You may install your Edge Agent on the vehicle gateway, the telematics control unit (TCU), or other data collection hubs in the vehicle.

You should develop your Edge Agent and test it so it can continually receive data collection schemes from AWS IoT FleetWise and can collect data accordingly for transfer to the cloud. With your Edge Agent, you control every step of the process from creation to installation, and you maintain data ownership and control of proprietary information. 

You are solely responsible for your Edge Agent, including ensuring that your Edge Agent and any updates and modifications thereto are deployed and maintained safely and securely in any vehicles.

With AWS IoT FleetWise, you can deploy cloud-configured data collection schemes to vehicles and update the configuration in the cloud at any point in time as business needs change. For example, if you have a tire monitoring scheme configured to collect tire pressure every 30 seconds, you can update it to collect the data every 60 seconds.

You can use a centralized repository of standardized vehicle sensors and signals for your vehicle models. You can save time by reusing signals when creating new vehicle models.

AWS IoT FleetWise applies the rules you define for transferring only the data signals you want to the cloud. First you define vehicle attributes (for instance, a two-door coupe) and the sensors associated with the vehicle’s make, model, and trim (for instance, engine temperature, vehicle speed, or parking assist system). Then you define rules and events for when to transfer that data, based on parameters such as changes to temperature or speed for a certain vehicle type. Rules-based data collection reduces the volume of unnecessary data transferred to the cloud, thus providing more useful data.

For additional information about service controls, security features and functionalities, including, as applicable, information about storing, retrieving, modifying, restricting, and deleting data, please see https://docs.aws.amazon.com/index.html. This additional information does not form part of the Documentation for purposes of the AWS Customer Agreement available at http://aws.amazon.com/agreement, or other agreement between you and AWS governing your use of AWS’s services.