# Scenarios
In this section, we cover the six key scenarios that are common in many connected mobility implementations. We describe how they influence the design and architecture of your connected mobility application, also referred to as *connected mobility platform* in this whitepaper. We present the assumptions made for each of these scenarios, the common drivers for the design, and a reference architecture for how these scenarios could be implemented.
**Topics**
+ [CM-S01 Vehicle and user provisioning](cm-s01-vehicle-and-user-provisioning.md)
+ [CM-S02 Vehicle connectivity management](cm-s02-vehicle-connectivity-management.md)
+ [CM-S03 Vehicle data management and insights](cm-s03-vehicle-data-management-insights.md)
+ [CM-S04 Connected mobility core services](cm-s04-connected-mobility-core-services.md)
+ [CM-S05 Connected mobility supported systems](cm-s05-connected-mobility-supported-systems.md)
+ [CM-S06 Customer experience management](cm-s06-customer-experience-management.md)
# CM-S01 Vehicle and user provisioning
Vehicle Provisioning links the Telematics Control Unit (TCU) with the Vehicle Identification Number (VIN). Vehicle Provisioning also enables secure and automatic provisioning of security certificates and installation of latest firmware. Such activities are performed before the vehicle leaves the factory or upon swapping of the TCU. End of Line (EOL) processes involve configuration and validation of the Telematics Control Unit which includes: setup the certificate for identity of the vehicle, provision the SIM with the Mobile Network Operator, and set the state of the vehicle in the Connected Mobility Platform. User Provisioning involves activating the Connected Mobility services for the customer in the Customer Relationship Management (CRM) and the Billing systems, and activate the SIM in the Mobile Network Operator (MNO) systems which allows the customer to actually use the service. The following are user stories in the Vehicle and User Provisioning scenario:
## User stories
**CM-S01-UC01 Vehicle provisioning at the factory: **Configuration of the Telematics Control Unit to set up the certificate for identity of the vehicle. The Connected Mobility Systems also maps the TCU with the VIN number in this step. All of this can be automatically initiated when the vehicle is started and the TCU registers itself to the provisioning service.
**CM-S01-UC02 Mobile Network Operator (MNO) integration:** The Telematics Control Unit (TCU) comes with a Subscriber Identity Module (SIM) which is used to transmit or receive data or SMS on the mobile network. As part of the vehicle provisioning process the API of the MNO is invoked to register the SIM. When the vehicle is delivered to the owner, the Connected Mobility service activation process will activate the SIM. Throughout the lifecycle of vehicle ownership, the vehicle owner may buy Mobility services like Entertainment, Wi-Fi Hotspot etc. which will require integration with the MNO to activate data packs. Troubleshooting any network connection issues will require integration with MNO’s APIs to get the status and any health metrics
**CM-S01-UC03 Driver profile management:** When the user is provisioned, a Connected Mobility Platform may allow save and restore of one or more driver preferences per vehicle, such as seat adjustments, temperature preferences, media setting, data sharing preferences etc. These profiles may be portable to any vehicle owned or rented by the customer as long as they have an active Connected Mobility subscription.
**CM-S01-UC04 Application and configuration updates: **Update latest software and configurations in vehicles' electronic control units (ECUs) by sending continual and reliable updates. These updates provided by customers should:
+ Have an audit trail of the update.
+ Comply with security standards (such as Uptane).
+ Comply with regulations (such as A-SPICE, UNR156, and ISO24089).
+ Ensure safety of vehicle and occupants while installing updates by conducting checks (for example, vehicle operating status).
+ Provide scalability to any number of vehicles.
+ Have the ability to target a subset or fleet of vehicles.
## Reference architecture
![\[Vehicle provisioning reference architecture\]](http://docs.aws.amazon.com/wellarchitected/latest/connected-mobility-lens/images/vehicle-provisioning-reference-architecture.png)
** Figure 1: CM-S01-a: Vehicle provisioning reference architecture **
1. Embedded in-vehicle devices with a unique identity principal (X.509 certificate) publish telemetry via MQTT to AWS IoT Core. To minimize in-vehicle software, only libraries necessary to connect to AWS IoT Core are implemented. The certificate is pre-installed in the vehicle during the End of the Line process.
1. The connection is made to AWS IoT Core through a private Access Point Name (APN) provided by the MNO and utilizing the customer’s own AWS IoT Core endpoint. All traffic is sent over MQTT protocol secured using mTLS.
1. Upon connecting to AWS IoT Core with the private certificate, the Lambda validates the Gateway and creates the IoT Thing and IoT Policy. Each vehicle ECU should have a unique certificate and potentially a unique IoT policy associated with it allowing only what is needed for the ECU to communicate to AWS.
1. Associate the Telematics Control Unit (TCU) with the Vehicle Identification Number (VIN). The vehicle is registered. The VIN is obtained from the telemetry data (see \$11).
1. Use the Mobile Network Operator (MNO) API to register the Subscriber Identity Module (SIM).
1. Vehicle Management application allows the connected vehicle operations center to manage any discrepancy or out of band process during the vehicle registration.
1. Encryption at rest on the server-side is available in all the services with encryption keys managed in AWS Key Management Service (AWS KMS).
![\[Reference architecture diagram for user provisioning\]](http://docs.aws.amazon.com/wellarchitected/latest/connected-mobility-lens/images/user-provisioning-reference-architecture.png)
** Figure 2: CM-S01-b: User Provisioning reference architecture **
1. User Provisioning can be performed either through self service by vehicle owner using an application, assisted through intermediaries (for example, Dealers, and Contact Center) or options through the vehicle.
1. Encryption at rest on the server-side is available in all the services with encryption keys managed in AWS Key Management Service (AWS KMS).
10A. Assign Driver to Vehicle and manage one or manage preferences per vehicle.
10B. Entitlement management helps ensure that user permissions are assigned based on user subscription and entitlements.
10C. Consent management is used to document, audit, and manage users consent to terms and conditions.
# CM-S02 Vehicle connectivity management
Vehicle connectivity management helps ensure resilient, secure, bidirectional connection between the vehicle and the cloud. It enables high throughput data transfer, low latency events and supports communication across all devices, in both low latency local area and wide area network connection. The following user stories are supported in Vehicle Connectivity Management.
## User stories
**CM-S02-UC01 Connectivity:** The ability of the vehicle to connect and exchange data with its surroundings, such as city infrastructure, the driver, passengers, pedestrians, and other vehicles, is commonly referred as V2X. The ability of the vehicle to connect and exchange data with the cloud is referred to as V2C (Vehicle to Cloud) or C2V (Cloud to Vehicle). Connectivity to these external systems should be secure and data should be relevant to satisfy real time vehicle functions.
To achieve these objectives, vehicle connectivity management should be able to provide the following:
+ Be able to withstand connection drop and re-establish connection.
+ Provide connectivity state and vehicle state in the cloud.
+ Keep the vehicle network connected for extended periods while the vehicle is switched off.
+ Ability for the connected vehicle to connect to the cloud Region that is in its geo-proximity and if it's not available, then it can failover to the alternate Region selected by the customer.
+ Perform secure authentication and authorization.
+ Ability to failover to a different network provider in case the Mobile Network Operator (MNO) service degrades.
+ Ability to receive and act upon predictive Quality of Service (QoS) notifications from the MNO.
+ Ability to run commands with low latency to ultra-low latency. Low latency is typically latency within 2–3 secs round trip and ultra-low latency is typically less than 200ms round trip. Remote commands and [tele-operations](https://www.mdpi.com/2076-3417/11/21/9799) are example use cases for running with low latency and ultra-low latency respectively.
**CM-S02-UC02 Messaging:** Vehicle Connectivity Management should be able to deliver messages to an individual vehicle or to a fleet of vehicles. To ensure relevant messages are sent, there should be capability to control message expiration and set message priority. It becomes essential to provide message delivery functionality that ensures to deliver message at-least once and provide traceability of the message generation. In certain instances, such as running remote commands, there should be the ability to wake the vehicle. Such capability should balance between low battery usage and latency in responding to the commands. Some common mechanisms include extended discontinuous reception ([eDRX](https://www.everythingrf.com/community/what-is-edrx)) failing over to shoulder tap in the case where the vehicle goes into deep sleep. The Vehicle Connectivity Management should also have the ability to serialize and deserialize messages over the air.
## Reference architecture
![\[Reference architecture diagram for vehicle connectivity management.\]](http://docs.aws.amazon.com/wellarchitected/latest/connected-mobility-lens/images/vehicle-connectivity-mgmt-refarch.png)
** Figure 3: CM-S02 Vehicle connectivity management reference architecture **
1. The connected vehicle acts as an IoT device, with a unique identity principal (X.509 certificate). AWS IoT Core is used for communication from edge-to-cloud to collect, analyze, and act upon the sensor data gathered from the vehicle.
1. The connection is made to AWS IoT Core through a private cellular network using the customer's own AWS IoT Core endpoint. All traffic is sent over the MQTT protocol secured using mTLS.
1. Upon connection, AWS IoT Core publishes the vehicle's connected state to the Connect Topic. This reserved topic is where connection events are published automatically upon connection.
1. The vehicle connection state is stored in the database for implementing observability solutions.
1. Messages published from the cloud use the Vehicle State AWS Lambda function to check connected state.
1. If the device is in a disconnected state, the vehicle state Lambda function invokes Amazon SNS, which will send an SMS to the dialable MSISDN on the SIM on the TCU to indicate that a command is waiting and to wake up and subscribe to command topics.
1. Messages are published based on vehicle connectivity state. Messages can also be expired by the MQTT Broker if it is not delivered on time. If the vehicle is connected, the command payload is published using the Command MQTT topic in AWS IoT Core that the vehicle has subscribed.
1. Critical system messages sent from the cloud to the vehicle can be stored, processed, and delivered when the vehicle comes back online.
1. AWS IoT Device Defender sends device audit and violation findings (such as unusual device behavior or software and configuration vulnerabilities) to AWS Security Hub CSPM, where security findings from other AWS services and AWS Partner products are aggregated and normalized. Security Hub CSPM sends findings to EventBridge, which routes them to a remediation workflow implemented in a vehicle security operations center.
1. The vehicle can use the AWS Encryption SDK using keys in AWS KMS for client-side encryption. The ECU can get temporary API credentials from the IoT credential provider to call AWS KMS APIs. You can also implement your own key management system for encryption keys.
# CM-S03 Vehicle data management and insights
Connected vehicles have hundreds of controllers and sensors producing thousands of individual data elements for operating, and conveying the state of a vehicle. Vehicle data management helps vehicle manufacturers to harness data as an asset, to drive sustained innovation and create actionable insights and improve their customer experience. Vehicle manufacturers are seeking cost-effective ways to simplify the process of collecting data from vehicles that are connected to the cloud help power insights and improve vehicle performance while maintaining the highest levels of confidentiality and security. There are regulations (such as CCPA and GDPR) related to data privacy and data sharing that require customers to provide data lineage and data governance capabilities.
## User stories
**CM-S03-UC01 Telemetry:** Automakers collect a variety and large volume of data that is configurable based on rules and filters to support business needs, such as predictive maintenance, location-based services, and insurance claims. In the next generation of vehicles, with expansive amounts of data continuously ingested at high rates from the vehicle, there are multiple verticals that would want to access the vehicle's data, including insurance, municipalities, and content providers. With automakers monetizing the vehicle data, managing the balance between cost, customer experience, data privacy, and revenue realized important.
When determining the backend architecture for the vehicle's payload, there are a few key concepts to keep in mind, namely size and frequency. Automakers could operate a hybrid approach to ingestion, with support for both high-frequency as well as low-frequency data ingestion. This hybrid approach allows automakers to optimize their cost while maximizing the data monetization potential for the most valuable data attributes from the vehicle.
The telemetry collection system should be able to withstand a sudden connection loss and maintain data integrity. The majority of telemetry data is time series data. To maximize the value of this data, processing and visualization of this data is a key capability needed to help create valuable insights and build new solutions to support those insights. Time series data differs from traditional vehicle sensor data in that it's used to perform queries in time windows across differing time frames.
**CM-S03-UC02 Data management and governance:** Vehicle manufacturers and vehicle owners need to establish data governance standards for collection, storing and dissemination of data and adhere to local rules and regulations (such as CCPA and GDPR). Vehicle owners and manufacturers need a consent management system to control, share, and delete data that supports meeting local, national, and international data privacy regulations and protects privacy of consumers.
**CM-S03-UC03 Data sharing and neutral servers:** Neutral servers are servers operated and financed by operators not connected with vehicle manufacturers. Such servers can be used by vehicle manufacturers to make vehicle data readily discoverable and accessible to interested vendors with necessary security and privacy controls.
**CM-S03-UC04 Insights and generating value from connected vehicle data:** Vehicle manufacturers would like to generate value for their customers from the connected vehicle data acquired throughout the lifetime of the vehicle, for example:
+ Provide Usage Based Insurance (UBI) dependent upon driver behavior, distance driven, and so on.
+ Provide subscription-based value-added service, such as Feature on Demand through over-the-air (OTA) update.
+ Increasing advertising reach and targeted advertising.
+ Independent service stations would like to access vehicle data and fault codes to repair and maintain vehicles.
+ Smart maintenance scheduling to reduce maintenance cost, increase fleet availability, and deliver a differentiating customer service.
+ Drive vehicle optimization, efficiency, and early detection of deviations from normal operating condition using ML algorithms and advanced simulations on a digital twin of the vehicle in the cloud.
## Reference architecture
![\[Reference architecture diagram for vehicle data management and insights.\]](http://docs.aws.amazon.com/wellarchitected/latest/connected-mobility-lens/images/vehicle-data-mgmt-and-insights-refarch.png)
** Figure 4: CM-03: Vehicle data management and insights reference architecture **
1. The connected vehicle, with a unique identity principal (X.509 certificate), has hundreds of sensors to collect data. AWS IoT FleetWise Edge Agent collects, stores, and organizes data from vehicle. Based on the campaign defined in AWS IoT FleetWise, the agent decodes signals from the vehicle and sends data payloads through AWS IoT Core.
1. The vehicle can communicate using OEM chosen protocols, such as MQTT and HTTPs, and use AWS services, such as AWS IoT Core and Amazon API Gateway. Vehicles can send video streams to the cloud using Amazon Kinesis Video Streams.
1. Improve data relevance by creating time- and event-based data collection campaigns that send the exact data you need to Amazon Timestream or Amazon S3.
1. By using purpose-built data processing components, vehicle manufacturers can generate data ready for consumption, organized by subject areas, segments, and profiles.
1. AWS Lake Formation makes it easier to centrally govern, secure, and globally share data. A data lake can be used to store and analyze multiple data types from wide variety of sources. Use AWS Glue Data Quality to measure and monitor the data quality and take corrective actions.
1. Enable different user personas from fleet aggregators to data scientists, analysts, and vehicle owners.
1. You can use Amazon SageMaker AI improve ADAS/AV models to optimize vehicle design for performance and efficiency. Insights from structured and semistructured data can be gathered by using Amazon Redshift. Utilizing Quick and other analytics platforms to continually improve vehicle quality, safety, and autonomy using near real time data from AWS IoT FleetWise.
# CM-S04 Connected mobility core services
Vehicle manufacturers can deliver value-added services to fleet operators and vehicle operators that helps them improve the vehicle operating experience, such as remote lock or unlock, remote vehicle monitoring, usage-based insurance, and improve experience throughout the vehicle lifecycle.
## User stories
**CM-S04-UC01 Companion mobile app for vehicle operators:** Vehicle manufacturers can provide a companion mobile app to vehicle operators to remotely interact with the vehicles and view on demand vehicle information. Some examples are:
+ Send remote commands to their vehicle to lock/unlock, start/stop their vehicle.
+ Send destination and waypoints to the in-vehicle navigation system.
+ Get EV charging status.
+ Get diagnostic information, such as tire pressure, battery charge or fuel status, and oil life.
+ Autonomous capabilities such as summoning the vehicle or parking.
**CM-S04-UC02 Predictive service:** Analyze component usage and provide predictive maintenance guidelines to help uptime and manage the service experience.
**CM-S04-UC03 Driver and passenger safety:** Connected vehicle platforms are designed to provide seamless communication between vehicles and remote applications to receive alerts of hazardous situations, enable more time to react, help prevent accidents and automate emergency call in the event of an accident. Automakers should implement redundancies in handling safety use cases to avoid any single point of failures.
**CM-S04-UC04 Vehicle security:** With connected vehicles capability to remotely operate the vehicle and the amount of personal data collected and stored in the cloud, it becomes essential to provide guardrails to prevent bad actors from using these new attack surfaces. Authorities are rolling out cybersecurity regulations like WP.29 Cybersecurity Vehicle Regulation Compliance regulation and related automotive standards such as ISO/SAE 21434 standard to mitigate the cybersecurity risks posed to vehicles.
**CM-S04-UC05 Diagnostics:** Send real-time and scheduled diagnostic reports to the customer regarding the vehicle health like oil life, tire pressure, battery health, and fuel or charge status. Call centers and repair centers can also automatically find the reason for the vehicle breakdown.
**CM-S04-UC06 Location-based services:**
+ Fleet operators and vehicle operators receive breakdown assistance by easily calling local roadside assistance in case of a vehicle breakdown. Mobile repair centers have the ability to get the accurate location of the vehicle to ensure efficient service to vehicle operators.
+ Capability to set up geofencing to ensure vehicle safety by preventing unauthorized vehicle use.
+ Location specific offers from merchants.
## Reference architecture
![\[Reference architecture diagram for connected mobility core services.\]](http://docs.aws.amazon.com/wellarchitected/latest/connected-mobility-lens/images/connected-mobility-core-services-refarch.png)
** Figure 5: CM-S04 Connected mobility core services reference architecture **
1. The connected vehicle, with a unique identity principal (X.509 certificate), has hundreds of sensors to collect data. AWS IoT FleetWise Edge Agent collects, stores, and organizes data from vehicle. Based on the campaign defined in AWS IoT FleetWise, the agent decodes signals from the vehicle and sends data payloads through AWS IoT Core.
1. Adding location awareness to apps enables an enhanced experience, such as sending real-time messages, and information and service based on user location (for example, repair centers have the ability to get the accurate location of the vehicle to ensure efficient service to vehicle operators).
1. Amazon Location Service features, such as maps, trackers, and geofence collections, are used to send geolocation data to track and follow the vehicle location. Events are initiated on Amazon EventBridge when the vehicle enters or exits a geofence and notifies vehicle and fleet operators.
1. Applications that are latency sensitive, such as tele-operations or Cellular V2X applications, can be deployed at the edge. AWS Wavelength could be used to deploy such applications.
1. Applications developed with AWS Amplify and AWS AppSync are used by vehicle operators and owners to create messages and business rules for geofences and notify events to the users.
1. A vehicle can initiate a call to the emergency response center, such as when it detects a hard impact or airbag deployment. Emergency services can be dispatched even if the driver is unresponsive.
1. Amazon Connect starts the automatic contact flow for the call and based on the nature of the call can be attended by the call center agent, road side assistance, or virtual voice assistant.
1. Critical details, such as the speed at impact, the number of airbags deployed, vehicle operation status, and even video footage, can be transmitted to the operator.
1. The solution also integrates with roadside service assistance providers and shares any relevant data for assistance.
1. Collect real time telemetry, analyze performance and component usage metrics to provide prescriptive guidance to vehicle owners.
1. The Request/Response messaging pattern in AWS IoT Core is a method to track responses to client requests in an asynchronous way. For vehicle remote commands, this enables the publisher to specify a topic for the response to be sent for a particular message, ensuring proper messaging to the customer on success or failure of the command state. Using the Message Expiry feature of AWS IoT Core, the vehicle operator could specify how long to attempt the remote command before expiring the message.
# CM-S05 Connected mobility supported systems
Connected mobility is a foundational component in enabling systems such as autonomous driving, battery health management, and fleet management. These downstream systems have stringent Quality of Service (QoS) requirements related to performance and resiliency, which the connected mobility platform has to satisfy. Thus, vehicle manufacturers have to give careful consideration while designing and developing such platform. Following are some examples of supported systems enabled by connected mobility platform.
## User stories
**CM-S05-UC01 Autonomous driving:** Vehicle manufacturers can use sensors to gather and generate data about condition of the vehicle and surrounding environment. Vehicle manufacturers can use the connectivity management platform developed by them to share such data among the fleet of connected vehicles and send data to other systems.
**CM-S05-UC02 Fleet management: **Fleet operators aim to reduce fleet operation cost, improve operational efficiency such as optimizing fleet routes, fleet utilization, driver support and reduce fleet disruption using centralized monitoring of vehicles and real time operational insights. To help achieve these objectives, fleet operators desire flexible and extensible data ingestion pipeline to capture near real time and historical data from the fleet. Further, they also desire tailored insights to visualize the health and status of the fleet and rely on connected mobility platform to achieve the same.
**CM-S05-UC03 Battery health management: **Fleet operators and vehicle owners aim to improve the efficiency and safety of their fleet operations by monitoring the battery health, improve battery performance, predict battery issues and extend lifespan of the battery. To achieve these objectives, they must collect and transfer Battery Management System (BMS) parameters to the cloud and rely on data gathered through connected mobility platform.
** CM-S05-UC04 Charging station ecosystem: **Vehicle manufacturers and charging station operators rely on Vehicle Connectivity and Data Management capabilities to provide value added solutions such as vehicle charging status, direction to nearest charging station, and remotely monitor charging station.
**CM-S05-UC05 Navigation, traffic, and travel management:** Vehicle drivers aim to improve mobility by reducing travel times, make informed decision regarding routes and modes of transportation and receiving real time events and hazards around them. Data gathered through connected mobility platform enables these functionalities.
**CM-S05-UC06 Tele-operation:** Vehicle connectivity management functionalities are utilized by fleet operators to remotely monitor vehicles using video feed from onboard cameras and in special circumstances control the vehicles.
# CM-S06 Customer experience management
Insights from vehicle data help provide a personalized in-cabin experience, which can also be portable to other vehicles. Vehicle Manufacturers can also use such data to predict customer's needs at different touch points throughout the vehicle lifecycle and provide a more seamless experience to address those needs.
## User stories
**CM-S06-UC01 Driver experience:** By monitoring inside and outside the vehicle, vehicle manufacturers can recommend changes to improve their customer’s driving experience and safety. Vehicle manufacturers can also provide customized infotainment options based on operator’s previous behavior. Allow the driver to take their profile to other vehicles they own or rent, subject to their approval and affirmative consent.
**CM-S06-UC02 Contact center:** Automakers need omni-channel customer service infrastructure that streamlines the customer support process and makes it simple for agents to resolve customer inquiries faster.
**CM-S06-UC03 Emergency response:** Vehicle drivers would like to automatically receive help from emergency services should the vehicle experience an accident.
**CM-S06-UC04 Retention, renewal, and churn:** Predict the customer propensity to renew their subscription and create a personalized marketing campaign.
**CM-S06-UC05 Service experience:** Improve vehicle service experience based on data-driven analytics and machine learning to help OEMs build innovative applications. For example, if the connected vehicle data shows a trend of extreme tread wear, then the system can recommend a tire replacement on the infotainment screen, provide a capability to shop for new tires and schedule a service appointment with a few clicks.
## Reference architecture
![\[Reference architecture diagram for customer experience management.\]](http://docs.aws.amazon.com/wellarchitected/latest/connected-mobility-lens/images/customer-experience-refarch-a.png)
** Figure 6: CM-S06-a Customer experience management reference architecture **
![\[Reference architecture diagram for customer experience management.\]](http://docs.aws.amazon.com/wellarchitected/latest/connected-mobility-lens/images/customer-experience-refarch-b.png)
** Figure 7: CM-S06-b: Customer experience management reference architecture **
1. Gather customer interaction and sentiment from source systems such as clickstreams, call center logs, vehicle sensor data, social sentiment etc.
1. Ingesting data across customer touchpoints into marketing data lake using variety of protocols.
1. Provide rich experience in the car, lifelike conversational services for vehicle breakdown, emergencies, vehicle-related questions, notifications, and concierge services. Vehicle manufacturers can use speech analytics powered by machine learning to access live call transcripts, understand customer sentiment, and identify call reasons in near-real time.
1. Transform raw data into consumption ready data using purpose-built data processing components and transformation libraries.
1. Analytics layer natively integrated with consumption ready data for quality and trend analysis. Customer sentiments can be analyzed using Contact Lens for Amazon Connect. Amazon Comprehend can also be used to perform post call analysis to gain further insights about the customer call.
1. For convenience and concierge services, use Amazon Alexa features. For example, an electric vehicle driver can use voice commands to learn the best route that will provide minimum charging time while enabling the driver to enjoy their favorite food while they wait.
1. Activate multiple customer channels such as mobile push, voice, and email for targeted marketing communications.
1. The companion application provides real time vehicle information, personalization and push notifications.
1. Use AWS IoT Device Management to implement OTA management through AWS IoT jobs data and use AWS IoT Fleet Indexing to manage state, connectivity, and device violations and to organize, investigate, and troubleshoot your fleet of devices.